About nickH

Hi Garrian, The ctrlX CORE is really flexible and suits a lot of use cases. The flexibility comes by using the App Technology. You can choose between many different applications from the ctrlX Store and install the Apps which you need for your usecase. The Apps vary from classic PLC-Runtimes, EtherCAT Master, OPC UA Client and Server or IoT Apps like Node Red, Mosquitto Broker, InfluxDB and many more. The ctrlX CORE is also perfect for IoT Use cases with Apps like Node Red, InfluxDB or IoT Dashboard (Grafana). Do you have some experience with Node Red? I think in Node Red it's easy to subscribe to data (which comes from a OPC UA Client App for example), process this data, display the data and send it further (e.g. with Mqtt or to a database).   Here is some more information which can help you: Basic How-Tos to get started How Tos and example applications about IoT  Influencer Videos, which can also give you some ideas what you can do with the ctrlX CORE   And feel free to ask me, when you got some further questions.  Best regards, Nick ... View more

Hi @nickH  Yes, I've realized that these warnings don't affect the build. Thank you for your reply. Félix ... 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 @Sgilk , It run in the ctrlx, but receive incorrect information, and there is no possibility to automate sd storage just with plug and play, because it require name of the SD. We continue work with API rest. thank you ... View more