Not even having the telos code available I should just STFU...
But in general, the source moteID is not included in the mica
message header so I'd assume similar for telos. Therefore you
need to put it in the data packet itself, as does Oscope. If
it's not in the TelosADC data then you need to mo
I'm not really sure if you answer solves my problem...
I'm using the TelosADC program - as far as I can see it does have the
facility to take in an ID but I may be mistaken. I am tryin gto give
it an ID like OscopeMSH does.
Thanks again
Colin
On 3/1/06, Michael Schippling <[EMAIL PROTECTED]> wr
That command should assign to the moteID.
The groupID is usually set in the makefile. They
are two different things.
If either of them are changing from message to message
you may be parsing the messages wrong. If the tmote
uses tos/types/AM.h as its TOS_Msg header on the host
side then the grou
Hi
I'm trying to assign each of the modules that I am using a unique ID
so that when the data comes in from the serial port I can tell which
of them it is.
I have tried doing what it says in the tutorial but this does not seem
to work as when I examine the data, the group ID value is consantly
chan
