Re: data specs
- From: Sawada999 <nospam@xxxxxxxxxx>
- Date: Fri, 29 Feb 2008 17:09:30 GMT
Alf P. Steinbach wrote:
* 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
I didn’t scramble the data, it’s as received.
I’m just trying to get up to speed on terminology. I’m a self-employed, self-taught, lone-wolf programmer with 35 years experience but this is the 1st time I’ve ever worked with anyone on a project. I always do womb-to-tomb. Since I’ve never had a conversation about my craft, I really don’t speak the language. I thought maybe this was something so basic any programmer worth his salt would understand the spec, if not I have no problem asking.
I’ve spent a lot of time this week learning new-to-me terminology.
Thanks for the response.
.
- References:
- data specs
- From: Sawada999
- Re: data specs
- From: Alf P. Steinbach
- data specs
- Prev by Date: Re: Compiler Loop Unswitching
- Next by Date: Re: Compiler Loop Unswitching
- Previous by thread: Re: data specs
- Next by thread: hacker challenge - traverse a list
- Index(es):