Hi PLCnext experts,
I’m trying to get system information from GDS, but I don’t have a good list of available information. From this page, I could know Arp.Plc.Eclr/DEVICE_STATE.CPU_LOAD_ALL_CORES existed and accessible via GDS, but I couldn’t figure out what other information is available. Also, device info / status requires identifiers to access, but I don’t have good list of identifiers.
If you have pointers, could you share?
Thanks!
_I 'm trying to get system information from GDS, but I don’t have a good list of available information._Unfortunately there is no complete list of system GDS ports available.
Many system GDS ports used to appear in the „GDS Ports“ window of PLCnext Engineer, but I don’t see these in the latest version - I’ll check why that is.
There have also been many requests for an RSC service that implements a GDS port „browser“. This is on the to-do list for the developers, but it is not currently scheduled.
_device info / status requires identifiers to access, but I don 't have good list of identifiers._You can get all the available identifiers for these services in the Info Center, here:
RSC Device Interface Services The RSC Device Interface Services provide a range of functions for accessing properties of the operating system and the controller hardware. You can call the information with the following interfaces and defined parameters. The following headers are required to use the service; integrate these headers via #include, if necessary:
Thanks Martin for the quick response!
Let me try to use device info / status API to collect info.
The link you provided is now 404. It is also references in the help file.
Is it moved to a new location?
404 error (plcnext.help)
Yes, sorry, the Info Center was revamped recently and most of the old links are now broken.
Here is the new link to the same information:
RSC Device Interface Services The RSC Device Interface Services provide a range of functions for accessing properties of the operating system and the controller hardware. You can call the information with the following interfaces and defined parameters. The following headers are required to use the service; integrate these headers via #include, if necessary: