@branko wrote:
The monitoring script has been completely changed and released in the 2.1.000 hotfix. I'll explain here what the changes are and why we had to change it.
First of all, the reason for the change. We have decided to reduce the payload size in order to support low-bandwidth or low-data cap connections in remote areas. A single data point is now around 34 bytes as opposed to around 230 bytes in the previous version. Unlike the previous version, the data is transmitted in binary (although it is still stored in readable JSON format).
The new data format consist of the following fields:
- start marker (OHD, short for Outernet Heartbeat Datagram)
- device ID (128-bit identifier reasonably unique to each receiver)
- timestamp (4 bits, low-resolution creation time relative to previous heartbeat datagram)
- tuner vendor ID (16-bit)
- tuner model ID (16-bit)
- tuner preset ID (5 bits, finger preset of the tuner settings used to identify the satellite in use)
- signal lock (1 bit)
- service lock (1 bit)
- signal strenght (4 bits)
- SNR/quality (5 bits)
- bitrate (6 bits)
- carousel count (5 bits)
- carousel status (31 bits for tracking up to 31 carousels, on/off for each)
- end marker (DHO, reverse of the start marker)
The source code can be found on GitHub if you have concerns about what we collect and what we do with it. The monitoring script is in readable format on your receiver.
NOTE: Monitoring can be disabled by removing the file
/mnt/persist/monitoring.yes. To do that, SSH into your device and run the following command:sudo rm /mnt/persist/monitoring.yesThere is no need to restart your device. Monitoring will stop collecting and transmitting data as soon as you remove the file.
Posts: 3
Participants: 3