Re: data specs




"Sawada999" <nospam@xxxxxxxxxx> wrote in message
news:P_Vxj.1367$ES.1048@xxxxxxxxxxx
Hi,

I'm reading specs written by an engineer defining data to be transmitted.
I could ask him but prefer not to show the extent of my ignorance.

The definition looks like this:

op code payload
-------------------------------
0x83 Minutes Up [31:24]
Minutes Up [23:16]
Minutes Up [15:8]
Minutes Up [7:0]
Messages Sent [31:24]
Messages Sent [23:16]
Messages Sent [15:8]
Messages Sent [7:0]

0x83 seems obvious(hex 83) but what does the rest mean? I can see the
pattern (8 bits / byte) but am not getting the meaning. Does this make
sense to anyone else?


Maybe Minutes Up is a 32-bit value, sent a byte at a time with bits 31:24
first, and the same for Sent, but only guessing:

83H U U U U S S S S

Total 9-byte sequence

--
Bart


.



Relevant Pages

  • data specs
    ... I'm reading specs written by an engineer defining data to be transmitted. ... I could ask him but prefer not to show the extent of my ignorance. ... I can see the pattern but am not getting the meaning. ...
    (comp.programming)
  • Re: data specs
    ... I'm reading specs written by an engineer defining data to be transmitted. ... I could ask him but prefer not to show the extent of my ignorance. ... That order then depends on whether you start at the top or at the bottom. ... Cheers, & hth., ...
    (comp.programming)
  • Re: data specs
    ... I'm reading specs written by an engineer defining data to be transmitted. ... I can see the pattern but am not getting the meaning. ... I hadn't considered that data could have been LSB first (backwards in my mind) so it makes sense to specify. ...
    (comp.programming)
  • Re: data specs
    ... I'm reading specs written by an engineer defining data to be transmitted. ... I can see the pattern but am not getting the meaning. ... (32bit compiler / CPU?) ...
    (comp.programming)