I've committed fixes to VirtualizeTimerC and VirtualizeAlarmC to
tinyos-2_0_devel-BRANCH.
Both components would fail if an alarm/timer was overdue. An overdue
Timer in VirtualizeTimerC would only affect that particular virtual
timer. An overdue Alarm in VirtualizeAlarmC would affect all
Hi,
I've executed BlinkToRadio application with two telosb motes for about 3
hours after adding one line of code in VirtualizeTimerC.nc.
These two motes are still operating correctly without event timer.fired()
getting lost.
It seems that the bug's been fixed.
Thank you.
Inyong Park
Whoah, it
Boomerang has no significant changes from the 2.x timer stack. We are
actively looking into this issue, now. - Cory
On 7/23/06, Philip Levis [EMAIL PROTECTED] wrote:
On Jul 23, 2006, at 11:37 AM, Jonathan Hui wrote:
After a little testing, it looks like the radio stack is still alive.
I
On Jul 22, 2006, at 6:31 AM, [EMAIL PROTECTED] wrote:
Hi,
I've implemented BlinkToRadio application on telosb with tinyos 2.0.
Two telosb motes send packets to each other using BlinkToRadio
application.
Packets are sent in event Timer.fired() in BlinkToRadio application.
I found something
Could be a bug in the radio stack. Note that only one of two motes stops...
-Joe
On 7/23/06, Philip Levis [EMAIL PROTECTED] wrote:
On Jul 22, 2006, at 6:31 AM, [EMAIL PROTECTED] wrote:
Hi,
I've implemented BlinkToRadio application on telosb with tinyos 2.0.
Two telosb motes send packets
On Jul 23, 2006, at 11:37 AM, Jonathan Hui wrote:
After a little testing, it looks like the radio stack is still alive.
I modified BlinkToRadio to maintain two timers (1ms and 1s period),
both of which attemps to send a message on each fire event. After a
few moments, the 1ms timer will fail to
Hi,
I've implemented BlinkToRadio application on telosb with tinyos 2.0.
Two telosb motes send packets to each other using BlinkToRadio application.
Packets are sent in event Timer.fired() in BlinkToRadio application.
I found something wrong in telosb operation.
If TIMER_PERIOD_MILLI(packet
