This shows you the differences between two versions of the page.
| Both sides previous revision
Previous revision
|
|
transsecs_vids [2022/07/21 08:07]
wikiadmin |
transsecs_vids [2024/02/06 17:08] (current)
wikiadmin |
| |
| |
| The //OnlineOfflineState// and //LocalRemoteState// are the most important variables. According to the standard you must provide a way (physical or logical button) for the operator to toggle between online/offline and local/remote. When //OnlineOfflineState// is offline there is no SECS communication. When //OnlineOfflineState// is online the host can successfully request to go online. When //LocalRemoteState// is local the host can monitor the tool but not send commands that will cause motion or control the tool in any way. The GEM spec is ambiguous as to what to do if the host sends a request to control the tool while in online local. If you set the //SxF0InOnlineLocal// to true, then the tool will return an SxF0 message (for example an S2F0 response to an S2F41 message). The state of the tool is report in the //ControlState// and //LastControlState// variables. | The //OnlineOfflineState// and //LocalRemoteState// are the most important variables. According to the standard you must provide a way (physical or logical button) for the operator to toggle between online/offline and local/remote. [[ModbusDevicesExample_OnlineOffline_LocalRemote|TransSECS Devices example of using Modbus 0x (Coil) Registers]] for these VIDs. |
| | |
| | When //OnlineOfflineState// is offline there is no SECS communication. When //OnlineOfflineState// is online the host can successfully request to go online. When //LocalRemoteState// is local the host can monitor the tool but not send commands that will cause motion or control the tool in any way. The GEM spec is ambiguous as to what to do if the host sends a request to control the tool while in online local. If you set the //SxF0InOnlineLocal// to true, then the tool will return an SxF0 message (for example an S2F0 response to an S2F41 message). The state of the tool is reported in the //ControlState// and //LastControlState// variables. |
| |
| //MDLN// and //SOFTREV// are required by GEM and report in the S1F2 (as well as other places). The //MDLN// is a description of the tool and the //SOFTREV// the software revision number. These you should populate approriately. Until recently both //MDLN// and //SOFTREV// were limited to 6 characters. The recent standards now allow for 20 characters. You can put the parameter <file>SOFTREV.20Char=true</file> in the ErgoTechConfiguration.properties file and this will extend the variable to be 20 characters (allowed by the latest standards). However, it's possible that many older hosts expect that string to be only 6 and will fail on a 20 character value so I would not (yet) recommend that you make this change and TransSECS defaults to 6 characters. | //MDLN// and //SOFTREV// are required by GEM and report in the S1F2 (as well as other places). The //MDLN// is a description of the tool and the //SOFTREV// the software revision number. These you should populate approriately. Until recently both //MDLN// and //SOFTREV// were limited to 6 characters. The recent standards now allow for 20 characters. You can put the parameter <file>SOFTREV.20Char=true</file> in the ErgoTechConfiguration.properties file and this will extend the variable to be 20 characters (allowed by the latest standards). However, it's possible that many older hosts expect that string to be only 6 and will fail on a 20 character value so I would not (yet) recommend that you make this change and TransSECS defaults to 6 characters. |