135u5 / tinyos-main

Automatically exported from code.google.com/p/tinyos-main
1 stars 0 forks source link

rfxlink (rf230/rf212) BaseStation stuck on sending #18

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?
1. Compile/Download BaseStation for one mote 
2. Compile/Download Oscilloscope for a remote mote
3. Send an update, sample interval, from host through BaseStation to remote mote

_What is the expected output?
I expect to see BaseStation toggle the send LED once.
And the message sent to remote motes.
Remote mote to change its sample rate

_What do you see instead?
Message is received in the remote mote - sample rate changes.
But BaseStation fails to recognize that.
It will resend the message over and over at a high rate
(radio & error indication blinking fast)
No more updates / parameter changes will get through.

What version of the product are you using? On what operating system?
TinyOS r5427 and later on Fedora 14

Please provide any additional information below.

Patch attached

Description of the bug
the error return from SubSend was lost, later code would assume failure unless 
acknowledged... Probably works when retry is enabled.
With this change clients will actually see if message was sent, failed in some 
way or canceled

PS
  The BaseStation code is not well behaved. Resending is retried without delay.
  And it will never give up in cases like this...

Original issue reported on code.google.com by rogjo...@gmail.com on 18 Feb 2011 at 8:30

Attachments:

GoogleCodeExporter commented 8 years ago

Original comment by philip.l...@gmail.com on 21 Feb 2011 at 8:17

GoogleCodeExporter commented 8 years ago
Thanks Roger for the bug report. Based on your patch a fix was committed to the 
repository. It works for us.

Original comment by mmar...@gmail.com on 13 Mar 2011 at 8:41

GoogleCodeExporter commented 8 years ago
How to apply this patch?

Original comment by rdprav...@iith.ac.in on 20 Apr 2012 at 2:11

GoogleCodeExporter commented 8 years ago
No need to apply it, it has been committed already to the mainline. Use the 
latest SVN source and it should work. 

Original comment by mmar...@gmail.com on 20 Apr 2012 at 3:16