I'm cc'ing this back to the help list...
Assuming you are using TOS1.x -- did you see that great suggestion
that we add a sig with all our version stuff to the end of each message? --
The Oscope message structure is in: apps\Oscilloscope\OscopeMsg.h
and the sourceMoteID is indeed what it says. However if you are getting
the same ID from different motes you probably didn't install different
IDs when you downloaded. Do something like this: make X install.N
where X is your platform and N is the ID to use on that mote.
MS
Alessandro Turella wrote:
Michael Schippling ha scritto:
At first glance it looks to me that there is some confusion of "channel"
and "moteID", or actually non-confusion as I don't see where the moteID
gets used, in the net/tinyos/oscope/GraphPanel.java method
oscopeReceived().
A quick way to see if it'll work would be to change the channel number
in each re-Mote, but a re-wank of the received code is probably in order.
MS
Hi Michael,
thanx for your answer,
In my mind i thought that any mote sends his identifier inside the
message, but i can't find where it is too!
can you explain me in which class it is? i cut off any graph instance, i
preferred to get data in a table, but i need to know the mote they come
from!!
in Your opinion, have i to search in the java class or in the nesC files
for the structure of the message?
while debugging i saw that any message received has the same structure
(of course), they have 5 fields:
this is a typical message (kept in Oscilloscope.java - in
messageReceived event):
[version=0x0]
[interval=0x100]
[id=0x1]
[count=0x1d3]
[readings=0xff .......etc]
Is the "id" field the one which can switch the provenance of a message?
because of i have 2 motes sending but the ID is the same for each
message(ID=1).
How can i do what you wrote? (..to change the channel number in each
re-Mote, but a re-wank of the received code is probably in order) (what
do you mean with "re-wank"?)
Thanx
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Scanned with Copfilter Version 0.84beta2 (ProxSMTP 1.6)
AntiVirus: ClamAV 0.91.1/3911 - Fri Aug 10 22:44:41 2007
AntiVirus: F-PROT 4.6.7 Engine version: 3.16.15
SIGN.DEF 10 Aug07 - SIGN2.DEF 10 Aug07 - MACRO.DEF 10 Aug07
by Markus Madlener @ http://www.copfilter.org
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Scanned with Copfilter Version 0.84beta2 (ProxSMTP 1.6)
AntiVirus: ClamAV 0.91.1/3911 - Fri Aug 10 22:44:41 2007
AntiVirus: F-PROT 4.6.7 Engine version: 3.16.15
SIGN.DEF 10 Aug07 - SIGN2.DEF 10 Aug07 - MACRO.DEF 10 Aug07
by Markus Madlener @ http://www.copfilter.org
--
Platform: WinXP/Cygwin
TinyOS version: 1.x, Boomerang
Programmer: MIB510
Device(s): Mica2, MicaZ, Tmote
Sensor board: homebrew
_______________________________________________
Tinyos-help mailing list
[email protected]
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
