Message: 5
Date: Tue, 10 Jan 2006 08:14:14 -0800
From: David Gay [EMAIL PROTECTED]
Subject: Re: [Tinyos-help] Micaz UART message length problem
To: TINYOS HELP tinyos-help@millennium.berkeley.edu
Message-ID:
[EMAIL PROTECTED]
Content-Type: text/plain; charset=ISO-8859-1
You would
over the serial port are almost certainly
in mica2 format, I'm not sure what to trust as far as strength
goes.
Date: Wed, 11 Jan 2006 01:37:39 -0800
From: Jeongyeup Paek [EMAIL PROTECTED]
Subject: Re: [Tinyos-help] Micaz UART message length problem
To: Michael Schippling [EMAIL PROTECTED]
Cc
On 1/9/06, Michael Schippling [EMAIL PROTECTED] wrote:
As a followup to my previous whine about trying to upgrade to TOS1.1.14...
The _reason_ I was so brazen, was that I just started trying to use the
micaz's
(to continue on my radio communications testing pogrom). With TOS1.1.7 I
was
As a followup to my previous whine about trying to upgrade to TOS1.1.14...
The _reason_ I was so brazen, was that I just started trying to use the micaz's
(to continue on my radio communications testing pogrom). With TOS1.1.7 I
was getting errors in message length at the host, even though the 'Z
Just to be sure,
http://www.google.com/search?hs=v16hl=enlr=client=operarls=enq=deciphering+tinyos+serial+packetsbtnG=Search
From the text:
The raw data packet uses an escape byte of 0x7D. This is needed in case
a byte of
payload data is the same as a reserved byte code, such as the frame
good pointI will double check it. The escaping should be
handled in the Listen code, but it could be the result of version-foo.
thanks
MS
Sankar Gorthi wrote:
Just to be sure,
http://www.google.com/search?hs=v16hl=enlr=client=operarls=enq=deciphering+tinyos+serial+packetsbtnG=Search
