hexadecimal issues

Some miscreant, probably Charlie, injected "hexadecimal" calculations into our civilized discourse the other day. Lo and behold, I was on the Spaceweather website and came across info on a "NanoSail-D" space device, some sort of satellite or space explorer or data gatherer. So there's your sailing content--"sail." In space. And it transmits a signal that ham operators or anybody with >400 mhz FM receivers can get. There was an explanation of how to decode the data and it involved hexadecimal notation, as follows: Solar sail "NanoSail-D" data transmission > The values in each field are coded in a 'Little Endian by Pairs' > fashion, also known as > Middle Endian. In this coding, each pair of ASCII characters form a > byte and those bytes are written from MSB to LSB. For example, the > Ejection Time field in the beacon example of Section 1 is decoded as > follows: > Raw in Hex Raw in Dec Computation Value > C8 A1 01 -> 200 161 1 -> 200*160 + 161*162 + > 1*164 -> 106952 > Ejection Time in the example packet is 106952 seconds Sorry; I couldn't resist. Chris Campbell

Chris, why didn't you say so before. Cheers Charlie From: Ca… [at] yahoogroups.com [mailto:Ca… [at] yahoogroups.com] On Behalf Of Chris Sent: Friday, January 21, 2011 11:13 AM To: Ca… [at] yahoogroups.com Subject: [Cal_Boats] hexadecimal issues Solar sail "NanoSail-D" data transmission The values in each field are coded in a 'Little Endian by Pairs' fashion, also known as Middle Endian. In this coding, each pair of ASCII characters form a byte and those bytes are written from MSB to LSB. For example, the Ejection Time field in the beacon example of Section 1 is decoded as follows: Raw in Hex Raw in Dec Computation Value C8 A1 01 -> 200 161 1 -> 200*160 + 161*162 + 1*164 -> 106952 Ejection Time in the example packet is 106952 seconds Sorry; I couldn't resist. Chris Campbell

I freely admit to being a miscreant, but George is miscreant. On 01/14/2011 03:06 PM, Elwers, George A. wrote: You're just using the wrong units of measurement. For instance, my friend says he's 40. Of course, that hexadecimal. In base ten he's 64. Cheers Charlie From: Ca… [at] yahoogroups.com [mailto:Ca… [at] yahoogroups.com] On Behalf Of Chris Sent: Friday, January 21, 2011 11:13 AM To: Ca… [at] yahoogroups.com Subject: [Cal_Boats] hexadecimal issues Some miscreant, probably Charlie, injected "hexadecimal" calculations into our civilized discourse the other day. Lo and behold, I was on the Spaceweather website and came across info on a "NanoSail-D" space device, some sort of satellite or space explorer or data gatherer. So there's your sailing content--"sail." In space. And it transmits a signal that ham operators or anybody with >400 mhz FM receivers can get. There was an explanation of how to decode the data and it involved hexadecimal notation, as follows:

I meant to say that George is "miscreanter". From: Ca… [at] yahoogroups.com [mailto:Ca… [at] yahoogroups.com] On Behalf Of Husar, Charlie [USA] Sent: Friday, January 21, 2011 11:32 AM To: Ca… [at] yahoogroups.com Subject: RE: [Cal_Boats] hexadecimal issues (Chris Again) I freely admit to being a miscreant, but George is miscreant. On 01/14/2011 03:06 PM, Elwers, George A. wrote: You're just using the wrong units of measurement. For instance, my friend says he's 40. Of course, that hexadecimal. In base ten he's 64. Cheers Charlie From: Ca… [at] yahoogroups.com [mailto:Ca… [at] yahoogroups.com] On Behalf Of Chris Sent: Friday, January 21, 2011 11:13 AM To: Ca… [at] yahoogroups.com Subject: [Cal_Boats] hexadecimal issues Some miscreant, probably Charlie, injected "hexadecimal" calculations into our civilized discourse the other day. Lo and behold, I was on the Spaceweather website and came across info on a "NanoSail-D" space device, some sort of satellite or space explorer or data gatherer. So there's your sailing content--"sail." In space. And it transmits a signal that ham operators or anybody with >400 mhz FM receivers can get. There was an explanation of how to decode the data and it involved hexadecimal notation, as follows:

I thought it made me more of a dweeb, but miscreant is ok, too. I guess they're not mutually exclusive. George From: Husar, Charlie [USA] Sent: Fri 1/21/2011 8:32 AM To: Ca… [at] yahoogroups.com Subject: RE: [Cal_Boats] hexadecimal issues (Chris Again) I freely admit to being a miscreant, but George is miscreant. On 01/14/2011 03:06 PM, Elwers, George A. wrote: You're just using the wrong units of measurement. For instance, my friend says he's 40. Of course, that hexadecimal. In base ten he's 64. Cheers Charlie From: Ca… [at] yahoogroups.com [mailto:Ca… [at] yahoogroups.com] On Behalf Of Chris Sent: Friday, January 21, 2011 11:13 AM To: Ca… [at] yahoogroups.com Subject: [Cal_Boats] hexadecimal issues Some miscreant, probably Charlie, injected "hexadecimal" calculations into our civilized discourse the other day. Lo and behold, I was on the Spaceweather website and came across info on a "NanoSail-D" space device, some sort of satellite or space explorer or data gatherer. So there's your sailing content--"sail." In space. And it transmits a signal that ham operators or anybody with >400 mhz FM receivers can get. There was an explanation of how to decode the data and it involved hexadecimal notation, as follows:

Wow, and all along I thought C8 A1 01 was 13271297. You learn something every day. Allen On Fri, Jan 21, 2011 at 8:13 AM, Chris <cc… [at] lsnm.org> wrote: > > > Some miscreant, probably Charlie, injected "hexadecimal" calculations into > our civilized discourse the other day. > > Lo and behold, I was on the Spaceweather website and came across info on a > "NanoSail-D" space device, some sort of satellite or space explorer or data > gatherer. So there's your sailing content--"sail." In space. And it > transmits a signal that ham operators or anybody with >400 mhz FM receivers > can get. There was an explanation of how to decode the data and it involved > hexadecimal notation, as follows: > > Solar sail "NanoSail-D" data transmission > > > The values in each field are coded in a ‘Little Endian by Pairs’ fashion, > also known as > Middle Endian. In this coding, each pair of ASCII characters form a byte > and those bytes are written from MSB to LSB. For example, the Ejection Time > field in the beacon example of Section 1 is decoded as follows: > > > Raw in Hex Raw in Dec Computation Value > C8 A1 01 -> 200 161 1 -> 200*160 + 161*162 + 1*164 > -> 106952 > Ejection Time in the example packet is 106952 seconds > > > Sorry; I couldn't resist. > > Chris Campbell > > > >

On 1/21/2011 11:38 AM, Husar, Charlie [USA] wrote: > > I meant to say that George is "miscreanter". How is that expressed in hexadecimal terms? Chris Campbell

Allen, this is why software engineers walk around with their fingers doing "Hook-em Horns" signs while twisting their hands back and forth. Endians are, at a minimum, confusing. Cheers Charlie From: Ca… [at] yahoogroups.com [mailto:Ca… [at] yahoogroups.com] On Behalf Of Allen Edwards Sent: Friday, January 21, 2011 12:10 PM To: Ca… [at] yahoogroups.com Subject: Re: [Cal_Boats] hexadecimal issues Wow, and all along I thought C8 A1 01 was 13271297. You learn something every day. Allen On Fri, Jan 21, 2011 at 8:13 AM, Chris <cc… [at] lsnm.org<mailto:cc… [at] lsnm.org>> wrote: Some miscreant, probably Charlie, injected "hexadecimal" calculations into our civilized discourse the other day. Lo and behold, I was on the Spaceweather website and came across info on a "NanoSail-D" space device, some sort of satellite or space explorer or data gatherer. So there's your sailing content--"sail." In space. And it transmits a signal that ham operators or anybody with >400 mhz FM receivers can get. There was an explanation of how to decode the data and it involved hexadecimal notation, as follows: Solar sail "NanoSail-D" data transmission The values in each field are coded in a 'Little Endian by Pairs' fashion, also known as Middle Endian. In this coding, each pair of ASCII characters form a byte and those bytes are written from MSB to LSB. For example, the Ejection Time field in the beacon example of Section 1 is decoded as follows: Raw in Hex Raw in Dec Computation Value C8 A1 01 -> 200 161 1 -> 200*160 + 161*162 + 1*164 -> 106952 Ejection Time in the example packet is 106952 seconds Sorry; I couldn't resist. Chris Campbell