...
| Code Block | ||
|---|---|---|
| ||
{
"exchanged_data":{
"name":"SAMPLE",
"version":"1.0",
"datapoints":[
{
"label":"TS1",
"pivot_id":"ID114562",
"pivot_type":"SpsTyp",
"protocols":[
{
"name":"iec104",
"address":"45-672",
"typeid":"M_SP_TB_1",
"gi_groups":"station"
},
{
"name":"tase2",
"address":"S_114562",
"typeid":"Data_StateQTimeTagExtended",
"gi_groups":"station"
}
]
},
{
"label":"TM1",
"pivot_id":"ID99876",
"pivot_type":"DpsTyp",
"protocols":[
{
"name":"iec104",
"address":"45-984",
"typeid":"M_ME_NA_1"
},
{
"name":"tase2",
"address":"S_114562",
"typeid":"Data_RealQ"
}
]
}
]
}
} |
IEC 104 south plugin (client/master)
IEC 104 Protocol stack configuration
The IEC 104 protocol stack configuration specifies communication parameters and is a collection of entries containing information about OSI Transport and OSI Application layers objects.
Each entry is comprised of attributes that describe the object. All the configuration data are structured using JSON.
Each entry shall be mapped with the corresponding configuration function in the chosen implementation protocol library.
Attributes definition
...
maximum ASDU size in transmission direction, if set to "0" => maximum possible value is automatically used.
...
remove, process, default = remove
remove: the time stamp will be removed from the information object
process: the time stamp will be processed on regular basis and additionally marked as 'not synchronized'
...
Configuration JSON structure
| Code Block | ||
|---|---|---|
| ||
{
"protocol_stack":{
"name":"iec104client",
"version":"1.0",
"transport_layer":{
"redundancy_groups":[
{
"connections":[
{
"srv_ip":"192.168.0.10",
"port":2404,
"conn":true,
"start":true
},
{
"srv_ip":"192.168.0.11",
"port":2404,
"conn":true,
"start":false
}
],
"rg_name":"red-group-1",
"tls":false,
"k_value":12,
"w_value":8,
"t0_timeout":10,
"t1_timeout":15,
"t2_timeout":10,
"t3_timeout":20
},
{
"connections":[
{
"srv_ip":"192.168.0.12",
"port":2404,
"conn":false,
"start":false
},
{
"srv_ip":"192.168.0.13",
"port":2404,
"conn":false,
"start":false
}
],
"rg_name":"red-group-2",
"tls":false,
"k_value":12,
"w_value":8,
"t0_timeout":10,
"t1_timeout":15,
"t2_timeout":10,
"t3_timeout":20
}
]
},
"application_layer":{
"orig_addr":0,
"ca_asdu_size":2,
"ioaddr_size":3,
"startup_time":180,
"asdu_size":0,
"gi_time":60,
"gi_cycle":false,
"gi_all_ca":false,
"gi_repeat_count":2,
"disc_qual":"NT",
"send_iv_time":0,
"tsiv":"REMOVE",
"utc_time":false,
"comm_wttag":false,
"comm_parallel":0,
"exec_cycl_test":false,
"startup_state":true,
"reverse":false,
"time_sync":false
}
}
} |
IEC 104 datapoint representation
This is the Datapoint representation of an IEC 104 ASDU.
| Code Block | ||
|---|---|---|
| ||
{
"data_object":{
"do_type":"M_SP_TB_1",
"do_ca":18325,
"do_oa":0,
"do_cot":3,
"do_test":false,
"do_negative":false,
"do_ioa":6468178,
"do_value":1,
"do_quality_iv":true,
"do_quality_bl":false,
"do_quality_ov":false,
"do_quality_sb":false,
"do_quality_nt":false,
"do_ts":1653484330239,
"do_ts_iv":true,
"do_ts_su":false,
"do_ts_sub":false
}
} |
Multiple type ids for IEC 104 ASDUs in the monitor direction
As stated in the IEC 104 60870-5-101:2003 standard document §7.2.4 COMMON ADDRESS OF ASDUs: "The information object address may be specified independently from the ASDU (type identification) which transmits the particular information object. Information objects may be transmitted with the same information object addresses using different ASDUs, for example, as a single-point information with or without time tag."
Based on Table 15 – ASDUs in the monitor direction which may transmit objects with equal information object addresses, the following rules shall be implemented:
Any check against type ids should be considering the following combinations table:
...
Example: any transmitted ASDU with type id M_SP_* type id is considered as valid if the exchange data configuration of a given datapoint specifies one the type id: M_SP_NA_1, M_SP_TA_1, M_SP_TB_1 and M_PS_NA_1
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.
TLS configuration
The CS 104 standard can also be used with TLS to realize secure and authenticated connections.
3 parameters are needed to set up the TLS secured connection:
- private key file
- server certificate
- root certificate (CA)
Fledge's certificate store allows certificates to be stored and used by the south plugins.
| Code Block | ||
|---|---|---|
| ||
{
"tls_conf:": {
"private_key": "server-key.pem",
"server_cert": "server.cer",
"ca_cert": "root.cer"
}
} |
IEC 104 north plugin (server/slave)
IEC 104 redundancy server modes
Multiple redundancy groups
The MZ Automation lib60870 server provides 3 different modes regarding the support of redundant connections and events queue handling:
- The default mode (CS104_MODE_SINGLE_REDUNDANCY_GROUP) allows only a single active client connection.
- The second mode (CS104_MODE_CONNECTION_IS_REDUNDANCY_GROUP) allows multiple active client connections.
- The third mode (CS104_MODE_MULTIPLE_REDUNDANCY_GROUPS) allows multiple active client connections while preserving events when no client is connected.
In the case of this design, the south plugin will be implemented with CS104_MODE_MULTIPLE_REDUNDANCY_GROUPS server mode.
This mode allows multiple active client connections while preserving events when no client is connected. In this mode clients can be assigned to specific redundancy groups. The assignment is based on the IP address of the client. A redundancy group can have multiple simultaneous connections but only one of these connections can be active. The number of activated connections is restricted by the number of redundancy groups. Each redundancy group has a dedicated event queue.
It can be set with the CS104_Slave_setServerMode function:
| Code Block | ||
|---|---|---|
| ||
CS104_Slave_setServerMode(slave, CS104_MODE_MULTIPLE_REDUNDANCY_GROUPS); |
Multiple redundancy groups example
...
In this example, 2 control centers, center A and B, are establishing communication with the server.
Both centers have an active and a stand-by gateway for failover management.
Center A has two simultaneous connections, one active and one stand-by, assigned to redundancy group 1.
Center B has only one active connection, assigned to redundancy group 2.
IEC 104 Protocol stack configuration
The IEC 104 protocol stack configuration specifies communication parameters and is a collection of entries containing information about OSI Transport and OSI Application layers objects.
Each entry is comprised of attributes that describe the object. All the configuration data are structured using JSON.
Each entry shall be mapped with the corresponding configuration function in the chosen implementation protocol library.
Attributes definition
...
maximum ASDU size in transmission direction, if set to "0" => maximum possible value is automatically used.
...
Configuration JSON structure
| Code Block | ||
|---|---|---|
| ||
{
"protocol_stack":{
"name":"iec104server",
"version":"1.0",
"transport_layer":{
"redundancy_groups":[
{
"connections":[
{
"clt_ip":"192.168.0.10"
},
{
"clt_ip":"192.168.0.11"
},
{
"clt_ip":"10.152.1.10"
},
{
"clt_ip":"10.152.1.11"
}
],
"rg_name":"red-group-1"
},
{
"connections":[
{
"clt_ip":"192.168.0.10"
},
{
"clt_ip":"192.168.0.11"
},
{
"clt_ip":"192.168.0.12"
},
{
"clt_ip":"192.168.0.14"
},
{
"clt_ip":"10.152.1.10"
},
{
"clt_ip":"10.152.1.11"
},
{
"clt_ip":"10.152.1.12"
},
{
"clt_ip":"10.152.1.13"
}
],
"rg_name":"red-group-2"
}
],
"srv_ip":"0.0.0.0",
"port":2404,
"tls":false,
"k_value":12,
"w_value":8,
"t0_timeout":30,
"t1_timeout":15,
"t2_timeout":10,
"t3_timeout":20
},
"application_layer":{
"ca_asdu_size":2,
"ioaddr_size":3,
"asdu_size":0,
"asdu_queue_size":100,
"time_sync":false,
"cmd_exec_timeout":20000,
"cmd_recv_timeout":5000,
"accept_cmd_with_time":1,
"filter_orig":false,
"filter_list":[
{
"orig_addr":1
},
{
"orig_addr":2
}
]
}
}
} |
IEC 104 datapoint representation
This is the Datapoint representation of an IEC 104 ASDU for a command.
| Code Block | ||
|---|---|---|
| ||
{
"command_object":{
"co_type":"type_id",
"co_ca":"ca",
"co_oa":"oa",
"co_cot":"cot",
"co_test":"istest",
"co_ioa":"ioa",
"co_value":"value",
"co_qu":"pulse",
"co_se":"Select/Execute",
"co_ts":"time_marker"
}
} |