I'm trying to understand the packet format of a PC app that interacts with a tmote; the format for messages to the tmote seem to contain an additional byte.
I installed a serial port sniffer so I could see the raw traffic. The PC app sends for example the following packet to the mote: 7E 41 0E 1C 00 00 00 00 00 FF FF 03 7D 5D 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 17 AC 7E I think the address (FF FF) should begin with the 9th byte but it is the 10th. What puzzles me is the 4th byte (1C); why is it there? This is different than the packet format I'm getting from the mote: 7E 42 01 00 00 00 00 00 7D 5E 00 08 7D 5D 00 69 06 7E Here the address (7D 5E = FE) begins with the 9th byte as it should. This corresponds to the documentation I've found on-line: http://cents.cs.berkeley.edu/tinywiki/index.php/Packetizer_Protocol and http://www.octavetech.com/pubs/TB5-01%20Deciphering%20TinyOS%20Serial%20Pack ets.pdf. I note that the message type to the mote is ack-requested (41), which perhaps accounts for the extra byte. But I haven't been able to locate any doc on that. Thx, Bill ------------------------- Bill Leal Computer Science and Engineering The Ohio State University 395 Dreese Laboratories 2015 Neil Avenue Columbus, OH 43210-1277 Fax: +1-815-301-8202
_______________________________________________ Tinyos-help mailing list [email protected] https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
