Versions Compared

Key

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

...

Code Block
languagejs
{
   "data_object":{
      "do_type":"type_id",
      "do_ca":"ca",
      "do_oa":"oa",
      "do_cot":"cot",
      "do_test":"istest",
      "do_negative":"isnegative",
      "do_ioa":"ioa",
      "do_value":"value",
      "do_quality":"quality_desc",
      "do_ts":"time_marker",
      "do_ts_valid":"isinvalid",
      "do_ts_sum_time":"isSummerTime"
   }
}

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:

Type IDType ID with timetagAlternative format type id
M_SP_NA_1M_SP_TA_1,M_SP_TB_1M_PS_NA_1
M_DP_NA_1M_DP_TA_1,M_DP_TB_1M_EP_TA_1,M_EP_TD_1
M_ST_NA_1M_ST_TA_1,M_ST_TB_1
M_BO_NA_1M_BO_TA_1,M_BO_TB_1
M_ME_NA_1M_ME_TA_1,M_ME_TD_1M_ME_ND_1
M_ME_NB_1M_ME_TB_1,M_ME_TE_1
M_ME_NC_1M_ME_TC_1,M_ME_TF_1
M_IT_NA_1M_IT_TA_1,M_IT_TB_1

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

draw.io Diagram
bordertrue
diagramNamefp_path_exploring
simpleViewerfalse
linksauto
tbstyletop
lboxtrue
diagramWidth343
revision3

...