On Sun, Feb 6, 2011 at 2:12 PM, Nicole Chiesi <nicole.chi...@gmail.com> wrote: > I have just a question . It is written in the tep 123 that "Together, the > origin, seqno and collect_id fields denote a unique *origin packet.*" . > However if we want to analyse the CollectionDebugMessage , it is seen that > after every 255 messages sent or received , the sequence number restarts. So > e.g If I want to analyse a node 1 , if it sends data more than 255 packets > then , it is bound to have two or more messages with same origin and > sequence number. So , analysis of the CollectionDebugMessage is bit out of > hand here for me. It is such that , the msg_origin in the CtpDebugMsg.h is a > 16 bit , while the originseqno of ctp data frame which writes to it is 8 bit > . If I make the ctp data frame to 16 bit as well then I can analyse the > CollectionDebugMessage . I was wondering if I change the bit of the data > frame affects the performance of ctp. > Another question is , if I am to avoid that , how can I go about analysing > the CollectionDebugMessage?
It is fine to increase the size of the sequence number to 16 bits to make your analysis easier. Otherwise, you will need to write code to detect sequence number wrap around. - om_p _______________________________________________ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
