To write a value to a server in the devices the format is:

/Devices/[DeviceNodeName]_Servers/[ServerName]→[setValue]

For example, to set the integer value 2 to a server called ModbusWord under the ModbusTCP node use:

/Devices/ModbusTCP_Servers/ModbusWord->setIntValue(2);

TransSECS is thread safe and so you can create threads in a script. Here's an example that creates a thread before setting the value of a Modbus server.

var Thread = Java.type("java.lang.Thread");
var Runnable = Java.type("java.lang.Runnable");
 
// declare our thread
this.thread = new Thread(new Runnable(){
  run: function () {
      /Devices/ModbusTCP_Servers/ModbusWord->setIntValue(2);
      print("printed from a separate thread");
  }
});
 
// start our thread
this.thread.start();

Set a value to a field in a message and send the message

var TransSecsController = Java.type("com.ergotech.transsecs.secs.TransSecsController"); 
secsInterface=TransSecsController.findController("PLCTool");  // the name of your project
 
// find the message
var message = secsInterface.getMessageBean("MessageName");
message.setElementName(15);  // "ElementName" is the name you gave the element in TransSECS
message.sendMessage();      

Here's a more concreted example. In an S2F42/S2F50 reject response set the CPName to indicate which parameter is in error:

  //function to send a host command reply with an invalid parameter
 function sendBadParamReply(paramName) {
   reply = secsInterface.getMessageBean("HostCommandRejectedBadParam");
   reply.setCPName(paramName);
   reply.sendMessage();      
  } //end of function to send HostCommandRejectedBadParam

A function to set the HCACK on an S2F42/S2F50 message. Note that the HCACK is a little strange. In TransSECS all byte types (SECS format 10) take an array, so here we have to create an array.

 //function to send a simple host command reply 
 function sendSimpleReply(hcack) {
   reply = secsInterface.getMessageBean("HostCommandReply");
   reply.setHCACK(Java.to([hcack],"byte[]"));
   reply.sendMessage();      
  } //end of function to send HostCommandReply

Register for Connection Status Notification in TransSECS Host Application

In a GEMHost application the TransSECS controller publishes the status of the connection.

To register for this, add a “Startup Trigger” from the “Demo Servers”

Register for the notification in the “script” field. Here the notification is just printed to the display.

var TransSecsController = Java.type("com.ergotech.transsecs.secs.TransSecsController");
var ConnectionStatusListener = Java.type("com.ergotech.transsecs.secs.host.ConnectionStatusListener");
 
print("Startup Trigger");
 
host=TransSecsController.findController("GEMHost");
 
// create the connection status listener
var connectionStatusListener = new ConnectionStatusListener() {
 
   connectionStatusChanged : function (connectionStatus, comment) {
       print ("Current Connection Status " + connectionStatus + " Status String \"" + comment + "\"");        
   }
};
 
// add this to the host  
host.addConnectionStatusListener(connectionStatusListener);
print("Connection Status Trigger Registered");

The details of the connection status are described here

Sending a List to PLC Registers

If a message is received from the host contains a list of variable length it's easy to split this list and place it in registers on the PLC.

In TransSECS, give the list a name, here “SlotIDList” and mark it as Publish. Do not set a Device and Tagname.

In a tag-based PLC, such as an Ethernet-IP PLC. You can write to elements of an array tag.

If your device is called “EIPPLC” and you want to write the values to an array “StringArray” using the server “SlotIDList” then the code would look like this:

for (id =0 ; id < incomingValue.size() ; id++ ) {
  /Devices/EIPPLC_Servers/SlotIDList->setVariableName("StringArray["+id+"]"); // set the element
  /Devices/EIPPLC_Servers/SlotIDList->setStringValue(incomingValue.get(id).getStringValue());  // send the value
}
/Devices/EIPPLC_Servers/NumberOfSlotIds->setIntValue(incomingValue.size());  // set the list length

The last line of the script puts the length of the list into a server called “NumberOfSlotIds”. After receipt, the PLC should set the “NumberOfSlotIds” variable to an invalid list length (eg -1, or 100000) so that it will change when the message is next received.

For a register-based PLC, such as a FINs PLC and a device called “FINSPLC” the equivelent code would be:

var baseRegister = 100;
var stringLength = 8;
for (id =0 ; id < incomingValue.size() ; id++ ) {
  /Devices/FINSPLC_Servers/SlotIDList->setAddress("" + (baseRegister + stringLength*id));
  /Devices/FINSPLC_Servers/SlotIDList->setStringValue(incomingValue.get(id).getStringValue());
}
/Devices/FINSPLC_Servers/NumberOfSlotIds->setIntValue(incomingValue.size());