Hi *,
I'm currently developing an application which involves a basestation sending
out
beacon messages which are to be received by free nodes. Upon reception, a free
node knows that it is in range of a certain basestation and restarts a timer.
If
the timer fires (the interval is 2.5 times the beaconing interval), the node is
considered out of range. Pretty simple, I would say.
However, a fair amount of time when I switch off my basestation (and thus only
1
free node is on), my free node still receives beacon messages!? Although no
other node is on, let alone transmitting.
So my question is, where do these 'ghost' messages could come from? I was
thinking multipath, but I doubt it since it happens over an interval of over
half a minute. Or some messages which are delivered to my application but which
are not removed from some reception buffer and thus reappear later, but again I
doubt it since this is not happening all the time...
My code which handles the reception is:
event message_t* AMReceiveCommandMsg.receive(message_t* msg_in, void* payload,
uint8_t len) {
if (len == sizeof(CommandMsg)) {
CommandMsg* cmdMsg = (CommandMsg*)payload;
if (cmdMsg->type == 2) { //this is a beaconing message
connected = TRUE;
call BeaconTimer.startPeriodic(beacon_interval);
}
}
return msg_in;
}
I think this is standard as in the tutorials, so I don't see a problem here.
I'm using TinyOS 2.0.2 on micaz.
Does somebody have an idea where I can search for a solution to this?
Best regards,
Klaas
_______________________________________________
Tinyos-help mailing list
[email protected]
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
