FORUM CTRLX AUTOMATION
ctrlX World Partner Apps for ctrlX AUTOMATION
Dear Community User! We are updating our platform to a new
system.
Read more: Important
information on the platform change.
08-22-2024 08:20 AM
Hello,
Recently i configured 2 differents access to symbol configuration because i have one for WebIQ and the other one for communication with the client control software.
Since this configuration (taht is working well), everytime i start the ctrlX PLC engineering software and open the latest program, all the symbol configuration is resetted.
It's very frustating to set this every time i work on this project. Is this bug know ? how can i fix that ?
See attachment for example, all checkbox are empty and the message telling me that configured signatures are not available for my library.
Versions :
CtrlX PLC APP : 1.20.4
CtrlX PLC Engineering : 1.20.7 based on Codesys 3.5.19.60
CtrlX WORKS : 1.20.11
Best Regards,
Vincent
09-05-2024 07:14 AM
As we did not face such issue please send us your project archive and have a test with the latest ctrlX WORKS version 1.20.11 you can find in the ctrlX Store area in our collaboration room.
09-13-2024 09:20 AM
After taking a look to your project I can confirm that the message appears. In general this happens if a variable e.g. as part of a structure was at some point declared to be part of thy symbol configuration and afterwards got deleted in the IEC code. Therefore the button to remove such variable declarations from the symbol configuration is available.
We will check why these declared variables are not longer visible in the symbol configuration but still recognized as available and also why the warning is appearing again after closing and opening the project.
could you give us some of the paths where the variables have been in the program code?
I could not recognize any further "reset" of the symbol configuration. So any settings done was still there after closing and opening the project.
10-07-2024 10:35 AM
As an update, we got in contact with our supplier CODESYS and created some tickets corresponding to the behaviour mentioned by you. Thanks for bringing this up.
Are there news or more information from your side?