...
| Attribute | Description | Expected values | Mandatory |
|---|
| do_type | message type | TSCE, TSCG, TMA, TMN, ACK_TC, MOD10 | YES |
| do_address | message address |
| YES |
| do_value | value |
| YES |
| do_valid | validity | valid = 0 or invalid = 1 | YES |
| do_ts | time code | 10 ms fraction in the 10 min modulo | YES |
| do_ts_iv | timestamp invalid | valid = 0 or invalid = 1 | YES |
| do_ts_c | loss of chronology | lost = 0 else = 1 | YES |
| do_ts_s | ts not synchronized | synchronized = 0 else = 1 | YES |
Example for a TSCE:
| Code Block |
|---|
|
{
"data_object":{
"do_type":"TSCE",
"do_address":325,
"do_value":1,
"do_valid":1,
"do_ts":80,
"do_ts_iv":0,
"do_ts_c":0,
"do_ts_s":0
}
} |
Example for a TMA:
| Code Block |
|---|
|
{
"data_object":{
"do_type":"TMA",
"do_address":71,
"do_value":-15,
"do_valid":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.