Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

HNZ Protocol stack configuration

The HNZ protocol stack configuration specifies communication parameters and is a collection of entries containing information about OSI Transport and OSI Application layers objects.

...

The present specification corresponds to the HNZ B1/TR mode working on a TCP/IP connection.

Attributes definition

AttributeDescriptionExpected valuesMandatory
namethis identifies the protocol stackiec104client, iec104server, tase2client, tase2server, 61850client, 61850server, etc...Yes
versionversion number of the configuration file2 digits x.y => x = major change, y = minor changeYes
connectionsarray of connections
Yes
connections.srv_ipIP address to remote IEC 104 serverIP addressYes
connections.portport number to remote IEC 104 serverdefault = 6001No
remote_station_addrremote server station address6 bitsYes
Inacc_timeouttimeout before declaring the remote server unreachable (DF.GLOB.TS)default = 180 (seconds)No
max_sarmmax number of SARM messages before handing over to the passive path (A/B)default = 30No
repeat_path_Amax number of authorized repeats for path Adefault = 3No
repeat_path_Bmax number of authorized repeats for path Bdefault = 3No
repeat_timeouttime allowed for the receiver to acknowledge a frame, after this time, the sender repeats the frame.default = 3000No
anticipation_rationumber of frames allowed to be received without acknowledgement default = 3No
test_msg_sendtest message code in sending directiondefault = 1304No
test_msg_receivetest message code in receiving directiondefault = 1304No
gi_schedulescheduled time for General Interrogation sendingdefault = 99:99 (disabled)No
gi_repeat_countrepeat GI for this number of times in case it is incompletedefault = 3No
gi_timetime to wait for General Interrogation (GI) completiondefault = 255 (seconds)No
c_ack_timetime to wait before receving a acknowledgement for a control commanddefault = 10 (seconds)

Configuration JSON structure

Code Block
languagejs
{
   "protocol_stack":{
      "name":"hnzclient",
      "version":"1.0",
      "transport_layer":{
         "connections":[
            {
               "srv_ip":"192.168.0.10",
               "port":6001
            },
            {
               "srv_ip":"192.168.0.11",
               "port":6002
            }
         ]
      },
      "application_layer":{
         "remote_station_addr":12,
         "inacc_timeout":180,
         "max_sarm":30,
         "repeat_path_A":3,
         "repeat_path_B":3,
         "repeat_timeout":3000,
         "anticipation":3,
         "test_msg_send":"1304",
         "test_msg_receive":"1304",
         "gi_schedule":"99:99",
         "gi_repeat_count":3,
         "gi_time":255,
         "c_ack_time":10
      }
   }
}

HNZ datapoint representation

This is the Datapoint representation of an HNZ message.

...

NB: if an attribute is not required, then it is not put in the output data object, which means that the output object structure always fits the protocol model object type.

HNZ command representation

This is the command representation of an HNZ message.

...

NB: if an attribute is not required, then it is not put in the output data object, which means that the output object structure always fits the protocol model object type.

Path exploration

In redundant network configuration or generally in cases where several communication paths exist between one client and one server, the path checking exploration mechanism allows the client to try all the paths one by one without making any difference between them. The client uses the first available path. On disconnection this procedure starts again from the beginning.