There's two parts to the answer... I think the simple version is that "7d 5d" is the "escaped" value of "7e", which is probably what your groupID is really. The TOS protocol escapes 7e's because they are used as the message sync bytes (I believe there's another value that's escaped as well) it's probably all in the ocatavetech doc at: http://www.octavetech.com/pubs/TB5-01%20Deciphering%20TinyOS%20Serial%20Packets.pdf Also remember that the values are little-endian, so "01 00" is actually integer for 0x0001.
The not-so-simple version is that the message struct you see on the host side is (probably) from tos/types/AM.h -- this is the one that is used for UART and mica2 radio messages. What's actually on the micaz air is defined in tos/platforms/micaz/AM.h and is translated by TOSBase, unless you hack it somehow. MS selvaraj wrote:
Hi, I programmed a mote with TOSBase and another with CountToRfm (node id = 10). I compiled raw_listen.c under tools/src and I get the following display. My question is that it does not conform to the message type outlined in the lesson 6 of tinyos1.x tutorial. But, I could see the group id (7d), source node id (0a), counting sequence etc., correctly but not in appropriate places as in lesson 6. How do I infer the data? what is the actual micaz AM message format? ----- TOSBase]# /opt/tinyos-1.x/tools/src/rl /dev/ttyS0 57600 /dev/ttyS0 input_stream opened 7e 42 ff ff 04 7d 5d 04 01 00 0a 00 82 6e 7e 7e 42 ff ff 04 7d 5d 04 02 00 0a 00 5e f5 7e 7e 42 ff ff 04 7d 5d 04 03 00 0a 00 ea 83 7e 7e 42 ff ff 04 7d 5d 04 04 00 0a 00 c7 d2 7e ---- I welcome replies clarifying my doubt. Selvaraj _______________________________________________ Tinyos-help mailing list [email protected] https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
_______________________________________________ Tinyos-help mailing list [email protected] https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
