About Sgilk

Sgilk · ‎09-29-2023

This is the correct current function of Device Bridge. You cannot write directly to the Datalayer tags created for the write back function. You can only write out to the PLC from within the Device Bridge collector logic. I’ve requested that this process is changed to allow direct Datalayer write to the write back tags but haven’t received a timeline on this functionality.

Sgilk · ‎09-28-2023

Hello, In order to utilize these libraries, you will need to execute the script on the Python runtime script engine. These are not available in the browser based interpreter of the IDE.

Sgilk · ‎09-28-2023

Hello, There are tons of options for you here depending on your needs. My first suggestion would be InfluxDB as an off the shelf database solution. You can also persist data within your application by plugging into the active-solution slot of ctrlX OS. App Data Persistence Of course you can always create or package your own database solution in a snap.

Sgilk · ‎09-27-2023

Yes, this is also possible using the scheduler configuration within the ctrlX OS. I do still think the load on the datalayer is much too high based on the application you are describing. I would suggest looking for the root cause of this.

Sgilk · ‎09-26-2023

At this point, it will be difficult for me to troubleshoot without the configuration and code of your other system apps. Based on the screenshots you showed, my bet would be there is a piece of PLC code that is polling the datalayer intensively. What is the update rate on the WebVisu variables? You could take a backup and then uninstall the PLC application to see if that is where the problem is originating.

About Sgilk

Re: Tags get created as Read-Only?

Re: Error while writing data for variables in datalayer from Python

Re: About database Access

Re: CtrlX X3 Core 2 stock at 100% Load

Re: CtrlX X3 Core 2 stock at 100% Load