Checking Connectivity by Periodically Sending S1F1 Messages

It's often useful to send a message periodically to ensure that the connection between the host and tool is still good. This approach can be applied to either host or tool, but is more commonly used at the host. If a TransSECS host detects a problem with the connection, that is, it can't send the message, it will automaticallyclose the existing connection and reform the connection to the tool. All you need to do is send this “ping” messages to ensure a reliable link.

This example uses the “GEMHost” example in TransSECS Devices.

Add the Devices node if it doesn't already exist by clicking on the “GEMHost” node and choosing “Add Devices”

DemoServers node (if it doesn't already exist) by right-clicking on the “Devices” node and selecting “DemoServers”.

Add a “ClockTrigger” by right-clicking on the “DemoServers” node:

Select the “ClockTrigger” node:

And change the “Timebase” to be how often you want to send your S1F1 message, here we choose every 10 seconds.

Right-Click on the “GEMHost” node and add an S1F1 message. Here it's called “AreYouThere” but you can use any name. In the “Device Name” drop-down choose “DemoServers” and in the “Tag Name” dropdown choose “ClockTrigger” - the node that you have just created.

Build and run the project. You can run it against your own tool, or the StandAloneGEMTool example. When you do, you'll see S1F1 messages sent.

  • periodicmessagesending.txt
  • Last modified: 2021/06/17 18:41
  • by wikiadmin