Thanks Tom, yes, when I assume it's seconds, I get uptime numbers like 22+02:22:54, which is 22 days, 2 hours, and some minutes/seconds.
Yes, it is in seconds. The latest software release was early may, so that is a uptime that can be expected.
Rob
Interesting to me was that the uptime is a 4-byte integer in host byte order, whereas the parameter numbers and length field are 2-byte short integers in network byte order. Seems inconsistent.
Reverse engineering the protocol was a bit of a challenge. I couldn't find it documented in sufficient detail anywhere and wound up decoding the protocol format from the hex dump and decoding that wireshark provided. - Brian
On Tue, May 30, 2017 at 05:18:08PM +0200, Rob Janssen wrote:
Yes, it is in seconds. The latest software release was early may, so that is a uptime that can be expected. Rob