Hi Mikael,

the shorter (30 bytes) messages are beacons.
This message type is also defined in C:\cygwin\opt\moteiv\tos\lib\MultiHopLQI\MultiHop.h as BeaconMsg and is sent every MHOP_BEACON_PERIOD to spread some informations about the network. (see ...\moteiv\tos\lib\MultiHopLQI\MultiHopLQIM.nc for usage)

The other (to many) bytes is the data-element of the MultiHop message, which
contains the payload. In case of Delta the payload can be a BeconMsg or DeltaMsg.
(TOS_Msg.data->TOS_MHopMsg.data->BeaconMsg or
TOS_Msg.data->TOS_MHopMsg.data->DeltaMsg )

So the message format for Delta application is:

Byte                    TOS_Msg
01                        length
02                        fcfhi
03                        fcflo
04                        dsn
05-06                   destpan
07-08                   addr
09                        type
10                        group
/*----- the next group of elements is stored in TOS_Msg.data ---------------*/
11-12                  sourceaddr
13-14                  originaddr
15-16                  seqno
17-18                  originseqno
19                        ttl
20                        id
/*-----  the next group of elements is stored in TOS_MHopMsg.data --------*/
           DeltaMsg            BeaconMsg
21        seqno                  parent
22        seqno                  parent
23        seqno                  cost
24        seqno                  cost
25        reading                hopcount
26        reading                hopcount
27        parent                 timestamp
28        parent                 timestamp
29        neighborsize        timestamp
30        retransmissions    timestamp
31        neighbors
32        neighbors
34        neighbors
35        neighbors
36        neighbors
37        neighbors
38        quality
39        quality
40        quality
41        quality
42        quality
43        quality

Regards,
            OLE


----- Original Message ----- From: "Mikael Ifversen" <[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Sunday, November 26, 2006 3:24 PM
Subject: [Tinyos-help] Boomerang -Delta packet structure


Hi,
I'm monitoring the data packets from the Delta app in boomerang with Listen.java. Most packets are of length 20bytes, then a few shorter packets of 14bytes are popping up.
1. What is the purpose of the shorter packet?
2. Can anyone clarify the packet structure below, since it seems that there are a couple of bytes to many?

The struct of the standard header is defined here: C:\cygwin\opt\moteiv\tos\lib\CC2420Radio\AM.h - 11bytes long where the 11th byte is the data, meaning only the first 10bytes constitutes the header. The struct of the MultihopMsg is defined here: C:\cygwin\opt\moteiv\tos\lib\MultiHopLQI\MultiHop.h - also 11bytes long and is consistent with Multihop message of 10bytes found at: http://www.moteiv.com/support/tmote-message-format.html

20 01 08 0C FF FF FF FF 08 7D 01 00 01 00 0B 00 0B 00 FC 21 0A 00 00 00 5E 0B FF
FF 03 00 FF FF FF FF FF FF FF 7F FF 7F FF 7F  packet length: 42
20 01 08 0D FF FF FF FF 08 7D 01 00 01 00 0C 00 0C 00 FC 21 0B 00 00 00 5F 0B FF
FF 03 00 FF FF FF FF FF FF FF 7F FF 7F FF 7F  packet length: 42
14 01 08 0E FF FF FF FF 07 7D 01 00 01 00 0D 00 0D 00 01 00 FF FF FE FF FF 00 00
00 00 00  packet length: 30
20 01 08 0F FF FF FF FF 08 7D 01 00 01 00 0E 00 0E 00 FC 21 0C 00 00 00 5E 0B FF
FF 03 00 FF FF FF FF FF FF FF 7F FF 7F FF 7F  packet length: 42.

So what is exactly the rest of the package?
Thanks,
Mikael
_______________________________________________
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

Reply via email to