...
Following the detection of its non-renewal, it is positioned to "questionable" and the "OldData" detail is positioned in the gateway flag is to true and sent to the controlling centers only once through the north service.
When a new measured value is received again from the station, the measured value is then sent with its new value with the corresponding quality and tstimestamp.
It's the reception of the first message for a measured value that triggers the non-renewal monitoring functionality.
Measured values cycling OK:
...
Measured values cycling failed:
Configuration
| Attribute | Description | Expected values | Mandatory |
|---|---|---|---|
| check_period | cycling check period, in seconds | default = 30 | Yes |
Configuration JSON structure
...
- PIVOTTM.GTIM.MvTyp.q.DetailQuality.oldData is set to "true"
- PIVOTTM.GTIM.MvTyp.q.Validity is set to "questionable"
- PIVOTTM.GTIM.MvTyp.q.Source is set to "substituted"
- PIVOTTM.GTIM.MvTyp.t.SecondSinceEpoch is set to current gateway timestamp
- PIVOTTM.GTIM.MvTyp.t.TimeQuality is set to the quality of the timestamp of the gateway (optional). PIVOTTM.GTIM.TmOrg is set to "substituted"
- PIVOTTM.GTIM.TmValidity.stVal is set to to the quality of the timestamp of the gateway"valid"
- PIVOTTM.GTIM.Cause.stVal is set to "3" (Spontaneous)
If it's impossible to obtain timestamp quality the timestamp of the gateway from Fledge :is unreliable then:
- PIVOTTM.GTIM.MvTyp.t.TimeQuality.clockFailure is set to "true"
- The value valid is used for PIVOTTM.GTIM.TmValidity.stVal, is set to "invalid"
If the timestamp of the gateway is is not synchronized with the external UTC time then:
- PIVOTTM.GTIM.MvTyp.t.TimeQualityattribute are not used..clockNotSynchronized is set to "true"
- PIVOTTM.GTIM.TmValidity is set to "invalid"