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]> wrote:
> That command should assign <number> 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 group field should be the groupID from
> DEFAULT_LOCAL_GROUP in your makefile. Not all messages
> contain the moteID, but, e.g., the first field of OscopeMsg
> in OscopeMsg.h is sourceMoteID, which should be the <number>
> you assigned.
>
> Was that the question?
> MS
>
>
> Colin Couper wrote:
> > 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
> > changing.
> > Is this a bug or am doing something wrong?
> >
> > I'm giving them an ID with the following command
> >
> > make tmote install.<number>
> >
> > Thanks in advance
> >
> > Colin
> >
> > _______________________________________________
> > Tinyos-help mailing list
> > [email protected]
> > https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
>

_______________________________________________
Tinyos-help mailing list
[email protected]
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

Reply via email to