After doing some investigation I changes the ACK_BYTE1 and ACK_BYTE2 variables to
ACK_BYTE1 = 0xc3, ACK_BYTE2 = 0x21, This seems to solve my problem. I'm guessing that the spi from the radio is, at some point, sending over 0xBA and 0x83 and fooling the CC1000SendReceiveP.nc. Is there a reason that the ACK bytes have been set to these values or are they just arbitrary values? Thanks, Ian On 3/15/07, Ian Welch <[EMAIL PROTECTED]> wrote:
I'm having some troubles with Packet Ack. I have set up a node to send out a packet and wait 50ms for an Ack. After 50ms has passed the wasAcked(msg) function is called, if it returns TRUE do nothing, if it returns FALSE resend the packet and restart the one shot timer for 50ms. It keeps looping until the packet is acked. My problem is if I have the node send out a packet, with no other nodes powered on, after a random number of retries wasAcked() returns TRUE, as if an ack was received???? Am I missing some underlying code here that automatically sets the msg->ack bit to true if some condition is met? I looked in CC1000SendReceiveP.nc but did not find any answers. Thanks, Ian
_______________________________________________ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help