This plugin can be used to convert IEC 104 ASDU objects to FledgePower pivot model objects.
The filter implements the Fledge Filter plugin interface (see filter_plugins).
See Plugins configuration design for examples and details.
The "config" parameter of "plugin_init" call shall include :
exchanged_data" category with the same content as provided to the IEC104 south plugin. This section is mandatory so that the filter plugin can convert the PIVOT type from IEC 104 type.Notes :
alternate_mapping_rule" option in its parameters.The "plugin_ingest" call will convert each "reading" of "reading_set" as follow:
"exchanged_data.datapoints.label"{'<Root> key' : {...}} . The content of object under '<Root> key' is given below.The <Root> key of PIVOT object is:
Reading key | Content |
|---|---|
| PIVOTTS.GTIS | Tele Signal |
| PIVOTTM.GTIM | Tele Measurement |
| PIVOTTC.GTIC | Not supported yet |
<type> conversion table:
| CDC Class | IEC 104 Type ID | Type ID with timetag | Alternative format type id |
|---|---|---|---|
| SpsTyp | M_SP_NA_1 | M_SP_TA_1,M_SP_TB_1 | M_PS_NA_1 |
| DpsTyp | M_DP_NA_1 | M_DP_TA_1,M_DP_TB_1 | M_EP_TA_1,M_EP_TD_1 |
| MvTyp | M_ME_NA_1 | M_ME_TA_1,M_ME_TD_1 | M_ME_ND_1 |
| MvTyp | M_ME_NB_1 | M_ME_TB_1,M_ME_TE_1 | |
| MvTyp | M_ME_NC_1 | M_ME_TC_1,M_ME_TF_1 |
The content under <Root> will convert the IEC 104 data objet to a pivot object as follow:
Key | Type | Default Value | iec104.data_object.<...> | Note |
|---|---|---|---|---|
<Root>.Cause.stVal | Integer | do_cot | See Cause of Transmission | |
<Root>.Confirmation.stVal | Boolean | false | do_negative | |
<Root>.ComingFrom | String | "iec104" | do_comingfrom | iec104 |
<Root>.Identifier | String | do_id | exchanged_data.datapoints.pivot_id | |
<Root>.<type> | {CDC} | do_type | exchanged_data.datapoints.pivot_type (see | |
| Boolean | false | do_quality_ov = true | |
<Root>.<type>.q.test | Boolean | false | do_test | |
<Root>.<type>.q.operatorBlocked | Boolean | false | do_quality_bl | |
<Root>.<type>.q.Source = "substituted" | String | "process" | do_quality_sb = true | "process" | "substituted" |
<Root>.<type>.q.Validity = "invalid" | String | "good" | do_quality_iv = true | "good" | "invalid" | "reserved" | "questionable" |
<Root>.<type>.t.SecondSinceEpoch | Integer | do_ts | ||
<Root>.TmOrg | String | do_ts_org | "genuine" | "substituted" | |
<Root>.TmValidity = "invalid" | String | "good" | do_ts_iv = true | "good" | "invalid" | "reserved" | "questionable" |
| String | "good" | do_quality_nt = true | "good" | "invalid" | "reserved" | "questionable" |
<Root>.SpsTyp.stVal | Boolean | do_value | ||
<Root>.DpsTyp.stVal | String | do_value | intermediate-state | off | on | bad-state | |
<Root>.MvTyp.mag.f | Float | do_value | Float 32 | |
<Root>.MvTyp.mag.i | Integer | do_value | Int 32 |
Rule 1: if the incoming IEC104 data object has not the attribute or has the default value then we don't have to create the corresponding attribute in the pivot object.
Rule 2: If the received pivot object has not an expected attribute then we create the attribute of the protocol specific datapoint with default value.
Rule 3: Case when ASDU timestamp is not received:
STATION => (ASDU) IEC104 SOUTH => (IEC104 DP) IEC104TOPIVOT =>(PIVOT DP) PIVOTTOIEC104 => (IEC104 DP) IEC104 NORTH => (ASDU) CENTER
A the IEC104TOPIVOT step:
If the received ASDU is without timestamp Then
We create a pivot object With timestamp = current system time
And <>.TmOrg.stVal = substituted
On the PIVOTTOIEC104 step:
We create an IEC104 datapoint with timestamp and do_ts_sub = true
IEC104 NORTH step:
If the Datapoint configured in the exchanged data has not IEC104 timestamp typeid
Then we create an ASDU with a typeid with no timestamp
If the Datapoint configured in the exchanged data has IEC104 timestamp typeid
Then we create an ASDU with a timestamp typeid, ASDU timestamp = do_ts And subtituted = do_ts_sub