About CtrlXplorer

As ctrlX AUTOMATION is an evolving ecosystem it is always hard to give a fix paper with possible communication protocols. Even there are already a lot. You can for sure have a look to our ctrlX STORE to check the available communication apps e.g. by filtering. A very good start to have a look to our "Collection of how to videos, blogs and examples for ctrlX AUTOMATION". Including tons of information like e.g.: Communication Portfolio in ctrlX AUTOMATION [DOCU] Control to Control Communication (C2C) - Overview [DOCU] Data exchange between controls C2C – ctrlX Data Layer Remote Connection [DOCU] Also as it is an open platform based on snap container technology, everybody could bring their own communication interfaces. See our SDK for ctrlX AUTOMATION on GitHub. ... View more

Important Updates: As this is a PLC project, developed by a customer, the source project configurations were inspected and the issue was found to be located in the Symbol Configuration. Most likely the customer developed the PLC project on a lower version of the CtrlX PLC Engineering software. That was the reason for the DL_INVALID_ADDRESS error when subscribing to a PLC Datalayer node via ServiceToService token. Solution: The issue was resolved by deleting the old Symbol Configuration and setting up a new one with the following addittional settings checked: Special thanks to @nickH for helping to identify the issue! I am marking this topic as closed. 🙂 ... View more

Hello @MauroRiboniMX , Thank you all for your insights regarding the issue. After further investigation and experimentation, I tried installing the snap as devmode in Ubuntu 20.04 and discovered that indeed there is an issue with the socket creation. It seems that certain permissions or configurations are missing within the snap environment, causing these problems to occur. In light of these difficulties and to avoid further complications with sockets, I have decided to change my approach for Inter-Process Communication (IPC). Instead of utilizing sockets, I will be transitioning to using shared memory. Shared memory offers a robust and efficient means of communication between processes, and it circumvents some of the challenges encountered with socket permissions and configurations within the snap environment. Once again, I appreciate all the support! P.S. I will be closing the ticket now. ... View more