yea I can recieve data/ readings from the motes and they r displaying fine on th oscilloscope window, I have used temp, phot and currently using mic with 200Hz sampling rate, and there is no problem in receiving the data.
Which is making the things more complex that if I am able to get data then why cant I send it?
As I said before groupID is same no mismatch. I was looking at the bugs section on sourceforge i found this (http://sourceforge.net/tracker/index.php?func=detail&aid=1211727&group_id=28656&atid=393934 ) , i dont know is it the problem in my case too. But I changed the code according to this patch nothing worked not even receiving.
can someone look more deeper into this to find the problem, I did but couldnt find anything helpful.
thanx
Manu
On 1/13/06, Michael Schippling <[EMAIL PROTECTED]> wrote:
Whoa....very odd. It sounds like it should be working fine.
I have to admit that I never actually used the Oscope Reset message
so I can't actually swear that it is right, but the code looks identical
to that which I use to send messages to my re-Motes.
You have discovered one hidden feature of GenericComm, whereby messages
coming over both the Radio and the UART are routed to the same handler.
When you plugged your OscopeRF mote directly into the programmer that
seems to prove that the Reset message is being sent from the host to MIB.
Given the above, then TOSBase should be passing the message on to the
radio and out to re-Motes. The message is addressed as BCAST
so it should be received and handled by all the re-Motes. Could
you have a group-ID mismatch? That's the only other thing I can
think of...
Oh yeah, you don't say if you are getting data FROM the Oscope Mote...
I assume so, which would mean that the base and re-Mote agree on
radio parameters. Otherwise the bets are off and you should examine
you build settings for TOSBase and the Oscope mote. Also the TOSBase
LEDs should flash when messages are sent, do you see any action there?
Perhaps you should start with the BroadCastInject program as
a paradigm instead? At least it sounds like it is working.
beyond this I would have to lay hands upon the actual hardware
so I don't think I can be of more help...
sorry
MS
Manu Gupta wrote:
>
>
> Hi ,
> back to the oscopereset problem, as I have discussed this problem
> before, but it still remains unsolved.
> As Micheal suggested before I checked the handerID, there is no mismatch.
> Now let me state the problem again, when we issue a reset command using
> Oscilloscope java application, it didnt work for the motes running
> oscilloscopeRF application, but it worked for non RF oscilloscope
> application.
> Sender.java is sending the commands to the motes, so I printed the reset
> msg that is been sent, everything i.e moteID, address, handlerID and the
> msg are correct. But still the motes dont get reset.
> So to check I made a samll change in OscilloscopeRF/OscilloscopeM.nc for
> toggling green LED when a reset msg is received, I found that the mote
> is not receiveing the msg.
> Next I directly attached the mote with RF application on the programming
> board which is connected to the laptop via serial port, then I ran the
> oscilloscope application, well its quite obvious that I wont get any
> readings, but if I send a msg the mote should be able to acknowledge it
> and this time it did, by toggling the green LED. So for oscilloscope
> aplications when the motes are hardwired reset command is working.
>
> Now to make sure radio is working properly I did hardware check, it
> worked fine, also I used this application called BraodCastInject, which
> send simple commands(Led on and Off) over radio via TOSBase to the motes
> which have an application named SimpleCmd running, it worked fine, I was
> able to turn on and off the Leds.
>
> Now what I understand is that there is a problem at receiving on the
> motes side (when using OscilloscopeRF), radio is working and the TOSBase
> apllication too, but somehow OscilloscopeRF application on the motes is
> not responding to the reset msg.
>
> so can anyone suggest what could be the problem and how to solve it?
>
> thanx
> Manu
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> Tinyos-help mailing list
> [email protected]
> https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
--
Luv Manu
_______________________________________________ Tinyos-help mailing list [email protected] https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
