Re: data specs

* Sawada999:
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?

It makes sense, but it seems you have scrambled the original spec.

It seems "Messages sent" is a 4-byte quantity, and so is "Minutes up".

It may be that what is specified is the order in which to send those bytes. That order then depends on whether you start at the top or at the bottom. Ask the guy.


Cheers, & hth.,

- Alf

--
A: Because it messes up the order in which people normally read text.
Q: Why is it such a bad thing?
A: Top-posting.
Q: What is the most annoying thing on usenet and in e-mail?
.

Relevant Pages

  • 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. ... pattern but am not getting the meaning. ... first, and the same for Sent, but only guessing: ...
    (comp.programming)
  • 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)