I know know that there is a relation to MAX_RETRIES in CtpForwardingEngine.h

There is written:

/*
 * The number of times the ForwardingEngine will try to
 * transmit a packet before giving up if the link layer
 * supports acknowledgments. If the link layer does
 * not support acknowledgments it sends the packet once.
 */

So I am really wondering why these packets are sent so many times. This 
cannot be efficient?

> Hi,
>
> I use CollectionSenderC and CollectionC of the ctp package to send my 
> data to the sink node.
> I just use a timer to send a message each second and the node with id 
> zero receives it.
> I only use two sensors.
> Unfortunately, I always receive the packages many times, as you can see 
> below. The sending
> does not answer with any errors and I only send the next message when 
> the channel is not
> busy. This becomes also clear by looking at the sequence number.
>
> What is the reason for this multiple receivings?
>
>
> Sender:
>
> SEND
> RESULT 0
> SEND DONE SEQ NR 5
> SEND
> RESULT 0
> SEND DONE SEQ NR 6
> SEND
> RESULT 0
> SEND DONE SEQ NR 7
> SEND
> RESULT 0
> SEND DONE SEQ NR 8
> SEND
> RESULT 0
> SEND DONE SEQ NR 9
>
>
> Receiver:
>
> RECEIVE SEQ NR 5
> RECEIVE SEQ NR 5
> RECEIVE SEQ NR 5
> RECEIVE SEQ NR 5
> RECEIVE SEQ NR 5
> RECEIVE SEQ NR 5
> RECEIVE SEQ NR 5
> RECEIVE SEQ NR 5
> RECEIVE SEQ NR 5
> RECEIVE SEQ NR 5
> RECEIVE SEQ NR 5
> RECEIVE SEQ NR 5
> RECEIVE SEQ NR 5
> RECEIVE SEQ NR 5
> RECEIVE SEQRECEIVE SEQ NR 6
> RECEIVE SEQ NR 6
> RECEIVE SEQ NR 6
> RECEIVE SEQ NR 6
> RECEIVE SEQ NR 6
> RECEIVE SEQ NR 6
> RECEIVE SEQ NR 6
> RECEIVE SEQ NR 6
> RECEIVE SEQ NR 6
> RECEIVE SEQ NR 6
> RECEIVE SEQ NR 6
> RECEIVE SEQ NR 6
> RECEIVE SEQ NR 6
> RECEIVE SEQ NR 6
> RECEIVE SEQ NR 6
> RECEIVE SEQ NR 6
> RECEIVE SEQ NR 6
> RECEIVE SEQ NR 6
> RECEIVE SEQ NR 6
> RECEIVE SEQ NR 6
> RECEIVE SEQRECEIVE SEQ NR 7
> RECEIVE SEQ NR 7
> RECEIVE SEQ NR 7
> RECEIVE SEQ NR 7
> RECEIVE SEQ NR 7
> RECEIVE SEQ NR 7
> RECEIVE SEQ NR 7
> RECEIVE SEQ NR 7
> RECEIVE SEQ NR 7
> RECEIVE SEQ NR 7
> RECEIVE SEQ NR 7
> RECEIVE SEQ NR 7
> RECEIVE SEQ NR 7
> RECEIVE SEQ NR 7
> RECEIVE SEQ NR 7
> RECEIVE SEQ NR 7
> RECEIVE SEQ NR 7
> RECEIVE SEQ NR 7
> RECEIVE SEQ NR 7
> RECEIVE SEQRECEIVE SEQ NR 8
> RECEIVE SEQ NR 8
> RECEIVE SEQ NR 8
> RECEIVE SEQ NR 8
> RECEIVE SEQ NR 8
> RECEIVE SEQ NR 8
> RECEIVE SEQ NR 8
> RECEIVE SEQ NR 8
> RECEIVE SEQ NR 8
> RECEIVE SEQ NR 8
> RECEIVE SEQ NR 8
> RECEIVE SEQ NR 8
> RECEIVE SEQ NR 8
> RECEIVE SEQ NR 8
> RECEIVE SEQ NR 8
> RECEIVE SEQ NR 8
> RECEIVE SEQ NR 8
> RECEIVE SEQ NR 8
> RECEIVE SEQ NR 8
> RECEIVE SEQRECEIVE SEQ NR 9
> RECEIVE SEQ NR 9
> RECEIVE SEQ NR 9
> RECEIVE SEQ NR 9
> RECEIVE SEQ NR 9
> RECEIVE SEQ NR 9
> RECEIVE SEQ NR 9
> RECEIVE SEQ NR 9
> RECEIVE SEQ NR 9
> RECEIVE SEQ NR 9
> RECEIVE SEQ NR 9
> RECEIVE SEQ NR 9
> RECEIVE SEQ NR 9
> RECEIVE SEQ NR 9
> RECEIVE SEQ NR 9
> RECEIVE SEQ NR 9
> RECEIVE SEQ NR 9
> RECEIVE SEQ NR 9
> RECEIVE SEQ NR 9
> RECEIVE SEQ NR 9
>
> _______________________________________________
> 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

Reply via email to