Online mode gives mainly 'Too many monitoring variables' messages, and no access to variables.
Background info:
===========
I'm working on an CodeSys application where recipe data is stored in several ARRAYs of STRUCTs. As we have lots of recipe data, there's quite some entries in the arrays, and quite some fields in the structs.
Recipe data can be modified both locally (with CodeSys visualisation) or 'remotely' (with an PC application via OPC).
Environment:
=========
I'm using CoDeSys 2.3.3.6 in combination with Advantech WinCE based IPCs.
Issue/Question:
==========
How does the option 'Surpress monitoring of complex types' work. I can't notice any difference when this option is selected.
Is it possible to have monitoring of variables turned off by default, rather than having to specify '{flag nowatch}' for each and every (array/struct) variable.
Can you confirm that the exporting of symbol file entries only has to do with OPC, and has nothing to do with online monitoring? If there is some relation, can you explain this a bit?
Thanks in advance,
Arie N. Verheul
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
background: depending on the type of hardware, the buffer size for communication between PLC and PC is limited.
As the CoDeSys monitoring data is cyclus consistent (all data you see belong to one PLC cycle), they are written to a buffer. If data exeeds buffer size (typically 5000 bytes for small PLC), you get this error message.
But there is help:
Since version 2.3.3, CoDeSys monitors as much as it can and for the rest it shows instead of a monitoring message "too many monitoring data". No message box any more. Please update.
'Surpress monitoring of complex types'
CoDeSys can monitor A[i]. In case of an array of struct this can be time consuming, and can even rise cycle time of a PLC cycle. Therefore there is an option to switch it off.
Online mode gives mainly 'Too many monitoring variables' messages, and no access to variables.
Background info:
===========
I'm working on an CodeSys application where recipe data is stored in several ARRAYs of STRUCTs. As we have lots of recipe data, there's quite some entries in the arrays, and quite some fields in the structs.
Recipe data can be modified both locally (with CodeSys visualisation) or 'remotely' (with an PC application via OPC).
Environment:
=========
I'm using CoDeSys 2.3.3.6 in combination with Advantech WinCE based IPCs.
Issue/Question:
==========
How does the option 'Surpress monitoring of complex types' work. I can't notice any difference when this option is selected.
Is it possible to have monitoring of variables turned off by default, rather than having to specify '{flag nowatch}' for each and every (array/struct) variable.
Can you confirm that the exporting of symbol file entries only has to do with OPC, and has nothing to do with online monitoring? If there is some relation, can you explain this a bit?
Thanks in advance,
Arie N. Verheul
background: depending on the type of hardware, the buffer size for communication between PLC and PC is limited.
As the CoDeSys monitoring data is cyclus consistent (all data you see belong to one PLC cycle), they are written to a buffer. If data exeeds buffer size (typically 5000 bytes for small PLC), you get this error message.
But there is help:
Since version 2.3.3, CoDeSys monitors as much as it can and for the rest it shows instead of a monitoring message "too many monitoring data". No message box any more. Please update.
CoDeSys can monitor A[i]. In case of an array of struct this can be time consuming, and can even rise cycle time of a PLC cycle. Therefore there is an option to switch it off.
Standard is not to switch it off.
Should not be necessary with the latest version.