Are you saying you have some nodes designated repeaters and others designated sensors?
If so, the simplest way is to set ranges of nodes at the timer start in SurgeM. e.g. if ( TOS_LOCAL_ADDRESS > 20 && TOS_LOCAL_ADDRESS < 40 ) call Timer.start(x,x); Otherwise, you will simply be wasting time comparing with each timer fire. Motes do not have to be consecutively numbered, so simply assign numbers in that range to sensor nodes. The various MultiHop protocols in TOS 1.x function on their own, and will pass messages within the correct group ID without an application running on top. It is also theoretically possible to control motes using Bcast. The GUI Java app never did that for me, and I never attempted other ways of making Surge bend to my will. If you haven't done so already, label your motes somehow. It makes assigning IDs much simpler. If your more comfortable with NesC and TinyOS, you can move to running separate applications on some nodes as routers and others as sensors, but TOSSIM doesn't allow that, so you have to work in hardware, as it were. However, a very simple application-on top of the routing layer, in place of Surge, with debugging code & Bcast-would be a good exercise. Also: you need to read through the documentation more. On Mon, March 12, 2007 5:14 am, Paul said: > Hi > > I am using surge as my application. How can I tell it such that only > particular nodes transmit data. I tried to check if the > TOS_LOCAL_ADDRESS == desiredNodeId in SendData() but it doesnt work. > desiredNodeid can be more than 1 address. > > -- > Cheers, > Paul > _______________________________________________ > Tinyos-help mailing list > [email protected] > https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help > -- The difference between the right word and the almost right word is really a large matter- it's the difference between a lightning bug and the lightning. -Twain _______________________________________________ Tinyos-help mailing list [email protected] https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
