One needs to know the platform and TOS version to make a full determination because the structures differ in various fun ways. However the first line of data appears to be standard T1 serial format with 5 bytes of header, matching to tos/system/types/AM.h, and 11 bytes of payload, which should match to whatever message struct is assigned the 0x0D type. I don't know what the second line, or subsequent lines that don't start with FF FF, represent. Though the 02 00 and 00 00 lines seems to have the same message format with different addresses and payload sizes.
My general decoding algorithm is to find the sync mark, which Listen removes and uses to trigger a newline. Then determine the header type and match the various fields byte by byte, in low-byte-first order for larger ints. Unless of course someone has used the nx types, for which it's high byte first, but not in the headers... Easy, no? MS [email protected] wrote: > Hello > I m working with the protocol AODV(implemented in /contrib/hsn). > I have 4 motes: > one SINK with in ID=0 , one Base Station with ID=1 and the 2 others > have successively ID=2 and ID=4. > I have executed Listen to show the packets that are coming from motes > (ID=2;ID=4) to Sink_Node.So i have obtained this result: > FF FF 0D 7D 0B 02 00 00 02 01 00 01 00 00 00 00 > 02 00 0E 7D 07 00 00 00 02 00 00 00 > FF FF 0D 7D 0B 04 00 00 02 01 00 01 00 00 00 01 > 00 00 09 7D 1D 02 01 02 00 03 15 00 19 00 00 00 00 00 00 00 00 00 00 > 00 00 00 00 00 00 00 00 00 00 00 > FF FF 0D 7D 0B 04 01 00 04 01 00 01 00 00 00 00 > 04 00 0E 7D 07 00 01 00 04 00 00 00 > FF FF 0D 7D 0B 02 02 00 04 01 00 01 00 00 00 01 > 00 00 09 7D 1D 04 02 04 00 03 15 00 19 00 00 00 00 00 00 00 00 00 00 > 00 00 00 00 00 00 00 00 00 00 00 > 00 00 09 7D 1D 02 03 02 00 03 15 01 19 00 00 00 00 00 00 00 00 00 00 > 00 00 00 00 00 00 00 00 00 00 00 > 00 00 09 7D 1D 04 03 04 00 03 15 01 19 00 00 00 00 00 00 00 00 00 00 > 00 00 00 00 00 00 00 00 00 00 00 > 00 00 09 7D 1D 02 04 02 00 03 15 02 19 00 00 00 00 00 00 00 00 00 00 > 00 00 00 00 00 00 00 00 00 00 00 > 00 00 09 7D 1D 04 04 04 00 03 15 02 19 00 00 00 00 00 00 00 00 00 00 > 00 00 00 00 00 00 00 00 00 00 00 > 00 00 09 7D 1D 02 05 02 00 03 15 03 19 00 00 00 00 00 00 00 00 00 00 > 00 00 00 00 00 00 00 00 00 00 00 > 00 00 09 7D 1D 04 05 04 00 03 15 03 19 00 00 00 00 00 00 00 00 00 00 > 00 00 00 00 00 00 00 00 00 00 00 > 00 00 09 7D 1D 02 06 02 00 03 15 04 19 00 00 00 00 00 00 00 00 00 00 > 00 00 00 00 00 00 00 00 00 00 00 > 00 00 09 7D 1D 04 06 04 00 03 15 04 19 00 00 00 00 00 00 00 00 00 00 > 00 00 00 00 00 00 00 00 00 00 00 > 00 00 09 7D 1D 02 07 02 00 03 15 05 19 00 00 00 00 00 00 00 00 00 00 > 00 00 00 00 00 00 00 00 00 00 00 > 00 00 09 7D 1D 04 07 04 00 03 15 05 19 00 00 00 00 00 00 00 00 00 00 > 00 00 00 00 00 00 00 00 00 00 00 > 00 00 09 7D 1D 02 08 02 00 03 15 06 19 00 00 00 00 00 00 00 00 00 00 > 00 00 00 00 00 00 00 00 00 00 00 > 00 00 09 7D 1D 04 08 04 00 03 15 06 19 00 00 00 00 00 00 00 00 00 00 > 00 00 00 00 00 00 00 00 00 00 00 > 00 00 09 7D 1D 02 09 02 00 03 15 07 19 00 00 00 00 00 00 00 00 00 00 > 00 00 00 00 00 00 00 00 00 00 00 > 00 00 09 7D 1D 04 09 04 00 03 15 07 19 00 00 00 00 00 00 00 00 00 00 > 00 00 00 00 00 00 00 00 00 00 00 > > I have identified the header of these messages ; but my problem is how > can I identify the payload?? > I m trying to understand the different programs implemented in > /contrib/hsn/tos to pick out the payload shown in this case. > I need our help. > Thanks > > _______________________________________________ > Tinyos-help mailing list > [email protected] > https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help _______________________________________________ Tinyos-help mailing list [email protected] https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
