Sutron Corporation Satlink Operations & Maintenance Manual, Rev 8.04.2 11/3/2016 pg. 127
A note about timestamps in the repeat Tx data: The timestamps are the same as if the Tx were
made at the provided time, rather than indicating the true age of the data. This meas that the
sensor data in the Tx is exactly the same as that of the Tx made in real time (which is 2016/6/20
23:00:30 in the example above). It is the caller's responsibility to handle the timestamps.
Why not have the timestamps indicate the true age of the data:
Unlike re-transmissions which are initiated by the logger, these repeat Tx data
transmissions are initiated by someone who knows the timestamps of the missing data.
Some systems will find it easier to integrate data that is in an unmodified format.
Most data formats (including SHEF and Pseudobinary B) do no support timestamps that
indicate very old data.
Note that append data is NOT provided in a repeat transmission!
The capture below illustrates the difference that the REPEAT option has on the TXFORM
command. Note that no date was issued with the REPEAT command, meaning it uses the current
time as the time of Tx. Note the lack of append data.
>TX1 TXFORM
Tx data would look like this
:BATT 2 #10 11.347 11.423 11.385 11.377 M M :TEMP 2 #10 26.00 25.25
25.75 26.00 M M :BL -1.00 :PWR -1.0/-1.0
Current message is 108 bytes (00:00:04 seconds) out of 2218 bytes
(00:01:00 seconds)
Available space is 2110 bytes
In that message, sensor data is 83 bytes
Worst case SENSOR data (excluding append) is 138 bytes (00:00:05
seconds)
Worst case available space is 2080 bytes
2 meas are active; 2 are marked for tx
>TX1 TXFORM REPEAT
:BATT 2 #10 11.347 11.423 11.385 11.377 M M :TEMP 2 #10 26.00 25.25
25.75 26.00 M M
