Skip to Content
Documentation03 · Data collectionProtocol pluginsProtocolsSECS HSMS master
On this page

SECS HSMS master

SECSMaster exchanges SECS/GEM messages over HSMS, handles transactions, and receives active device messages.

Open the plugin

Enter “Development Configuration → Collection Configuration”, create a device and select “SECSMaster” in “Collection Plugin”.

Supported channels and data types

Channel typePre-configuration check
TCP ClientConfirm network reachability of the device IP, port, and gateway to the device.

Optional data types: Boolean, Byte, Int16, UInt16, Int32, UInt32, Int64, UInt64, Float, Double, String

This list describes types allowed by the plugin editor. Address width, arrays, string length and read/write restrictions still follow this page; it does not mean that every address supports every type.

Plugin properties

Protocol parameters

SettingDescription
Session IDDefault: 0; Range: 0~65534; Fill in: text input. Sets the session ID used for protocol communication.

Running parameters

SettingDescription
Control transaction T6Default: 5000; Range: 1~2147483647; Fill in: digital input. Sets the control transaction T6 used when the plugin is run.
Select Session T7Default: 10000; Range: 1~2147483647; Fill in: Numeric input. Sets the selection session T7 used when the plugin is run.
Fragmented reception T8Default: 5000; Range: 1~2147483647; Fill in: digital input. Sets the shard receive T8 used by the plugin runtime.

Address rules

  • Address Description
  • s=1;f=3;w; send main message and wait for S1F4
  • s=6;f=11; Subscription device active S6F11
  • s=1;f=13;w;<List Length="0" /> carries SECS-II XML data

Special methods

MethodPurposeParameters
TestLinkAsyncPerform link testNo parameters
ExchangeMessageAsyncExchange SECS-II messagesaddress=s=1;f=3;w;
ReadStatusVariableNamesAsyncRead GEM status variable namesstatusVariableIds=1,2,3

Device debug

Enter “Development Configuration → Collection Configuration”, select the current device then open “Protocol Debug” at the top of the workspace.

Dedicated debugging page

The protocol debug page provides link and message operations and status-variable queries.

SECSMaster: Link and messages

SECSMaster: GEM status variables

Debugging notes

Test the HSMS/SECS-II link first; message exchange requires write permission and secondary confirmation, SVID query remains read-only.

Functions

FunctionPurpose
LinktestRun an HSMS Linktest to confirm that the session is available without sending a business-control message.
Message exchangeSend an S/F message with optional SECS-II data; wait for the secondary message when w is present.
Status-variable namesQuery GEM status-variable names by SVID list.
Active-message monitoringCheck that configured S/F variables update when the equipment reports an event.

Verify the configuration

  1. Run Linktest and confirm that the HSMS session is available.
  2. Enter approved test SVIDs such as 1,2,3, read their names, and compare them with the equipment documentation.
  3. Exchange a message with a confirmed read-only meaning and verify the expected S/F secondary message.
  4. For active-message variables, trigger one approved test event and confirm that the matching S/F address updates.
  5. Do not send a business message whose meaning has not been confirmed to a production device.

Troubleshooting

  • Linktest fails: Check TCP address, port, session ID, and HSMS Select state.
  • The connection drops soon after it opens: Check T6, T7, and T8 timeout settings.
  • SVID query fails: Confirm that the equipment is in communication state, the SVID exists, and GEM permissions allow the query.
  • Message exchange times out: Check S/F, the w flag, T3 transaction timeout, and whether the equipment should return a secondary message.
  • Active message does not update a variable: Check the S/F address, session ID, and message log.
SECS-I masterSNMP manager