If you are receiving data FROM the OscopeRF Mote, then you should be
able to send the reset TO it. Along with the nodeIDs and such, make
sure the HandlerID is the same on both sides (this identifies what
message you are using and selects the method to run at the receiver).
The only other thing I can think of is that the CRC value is incorrect,
but if you are using more or less straight demo app code that shouldn't
be the case.
You can try using the direct UART Oscope version (with the target Mote
in the programmer and no radio) to see if your message is still missing.
And also go back to app/MicaHWVerify to see if the radios are really
working right.
otherwise I'm clueless too
MS
Manu Gupta wrote:
Hi,
thanx for the nice suggestion.
I wasnt working on it for a while, now I am back.
I looked into the Reset function on my system and found that when I am
sending a reset command to Motes, its not reaching them.
I checked that the command reach the base station (as can be seen by
blinking of red light), but its not getting fowarded to the motes.
I made a small change in the Reset function in nesC (Where we are just
resetting the counter) I called Blink green light whenever the motes
receive a command. But it never blinked. I checked all the addresses
(broadcasting, nodeID, groupID) and they are same everywhere.
Can any one suggest where the problem is ??
Thanx
Manu
On 12/8/05, *Michael Schippling* <[EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>> wrote:
sorry, I don't know about MoteIF, but if you look at the impl of
the reset message in OscilloscopeM.nc you see that it just resets
the reading number:
/**
* Signalled when the reset message counter AM is received.
* @return The free TOS_MsgPtr.
*/
event TOS_MsgPtr ResetCounterMsg.receive(TOS_MsgPtr m) {
atomic {
readingNumber = 0;
}
return m;
}
What you probably want to do is get the timers started at the same
time, which I suppose you could do by moving the:
call Timer.start(TIMER_REPEAT, 125);
to the reset message. There's probably some nice way to restart
the timer but that would require a lot of code archeology to find.
Also it's likely that the timers will not all start at exactly
the same time, and will drift anyway. Depending on what your
objective is, there may be some more robust distributed way of
designing it...
MS
Manu Gupta wrote:
> Hi,
> then what MoteIF is doing? according to the documentation it is
> used to send and receive msgs to an from motes. And this is used in
> reset class to send a reset msg to the motes.
> If the oscoperesetmsg is an arbitrary method, then how to make a
> function which will act as a software Reset for the motes. So if
I start
> motes at different time and the use this s/w reset it will start
them
> again and the motes will be synchronized.
>
> thanx
> Manu
> On 12/6/05, *Michael Schippling* <[EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>
> <mailto: [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>>> wrote:
>
> It's an arbitrary function conveniently labeled so as to make
> it look like it does something useful. If you look at the impl
> in O'scope all it does is reset the message counter.
>
> You can, of course, make it do something more interesting...
> MS
>
>
> Manu Gupta wrote:
> >
> > Hi,
> > I have some question regarding OscopeResetMsg.java.
> Tutorials say
> > that when u send a reset msg to motes using this mentioned
class, it
> > resets them.
> > so my question is reset in what sense, as in reset the
timer
> on the
> > motes or reset the ADC acquisition i.e motes starts all
over again.
> > When I am braodcasting the reset msg, it looks from
the graph
> that
> > they are getting reset, but if you see the x axis i.e last
sample
> > number, it is not getting reset.
> > Also if you start 2 motes with some delay from each
other and
> then
> > use reset command to synchronize them, they r not
> getting synchro, as
> > seen from the lastsample number readings.
> > can someone throw some light, where is the problem or
where i
> am goin
> > wrong.
> > thanx
> >
> > Manu
> >
> >
> >
>
------------------------------------------------------------------------
>
> >
> > _______________________________________________
> > Tinyos-help mailing list
> > [email protected]
<mailto:[email protected]>
> <mailto:[email protected]
<mailto:[email protected]>>
> >
>
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
>
>
>
>
> --
> Luv Manu
--
Luv Manu
_______________________________________________
Tinyos-help mailing list
[email protected]
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
