Differences
This shows you the differences between two versions of the page.
Next revision | Previous revision | ||
writing_gem_state_variables_to_device_servers [2024/02/06 16:48] wikiadmin created |
writing_gem_state_variables_to_device_servers [2024/02/06 18:41] (current) wikiadmin |
||
---|---|---|---|
Line 1: | Line 1: | ||
- | =====Writing | + | =====Monitoring |
- | GEM state variables are calculated and maintained automatically by the internal GEM state model so you should never manually change these. However these values are accessible and can be written (to be read only) to a holding register or tag in your device. | + | GEM state variables are calculated and maintained automatically by the internal GEM state model so you should never manually change these. However these values are accessible |
====GEM Control State (Modbus Example)==== | ====GEM Control State (Modbus Example)==== | ||
Line 9: | Line 9: | ||
{{: | {{: | ||
- | In the configuration, | + | In the configuration, |
{{: | {{: | ||
+ | |||
+ | In the TransSECS Devices project, configure the ControlState VID to use this newly defined register to store its value. | ||
+ | |||
+ | Click on ControlState (under VIDs) and select ModbusTCP for the Device, and the TagName " | ||
+ | |||
+ | {{: | ||
+ | |||
+ | Now when you build and run the deployment you will see the value of the tool's ControlState in the 4x1 register. | ||