Hello Omprakash, In the READMe.txt under apps/tests/TestNetwork there is the following expression;
"There are scripts on net2 website to parse the debug messages sent by the nodes." i couldn't find them. Could you send me if there are any such scripts, please? And how to run them to parse CollectionDebug messages? Actually, in the MultihopOscilloscope application, UARTDebugSenderP component is also wired. (Wired to CollectionC) Using Listen application i can see those debug messages and can only parse them by looking the enumerations defined in CollectionDebugMsg.h file. In the TestNetwork application i couldn't see such a difference in terms of using UARTDebugSenderP (TestNetwork application also uses Dissemination it doesn't matter for the parsing problem i have been faced to. ).There is somehow a connection and it sends uart the messages.... What i really need is the perl script to parse the enumerations ... Also i couldn't find where TestNetwork application looks whether the node is the root node or not before sending CollectionDebug messages to the uart. it should send uart messages after checking RootControl.isRoot() or using a global root flag or something like that, otherwise how can a remote node can send uart messages!... Could you help me with this issue ? Thanks in advance, -- Akif On Fri, Mar 27, 2009 at 9:12 AM, Omprakash Gnawali <[email protected]> wrote: > On Thu, Mar 26, 2009 at 12:06 PM, Mehmet Akif Antepli > <[email protected]> wrote: > > Hi, > > > > I am sure that they are sending messages because when i just start > MsgReader > > with the following command, > > > >>>java net.tinyos.tools.MsgReader MultihopOscilloscopeMsg > > > > oscilloscope_t structure fields are parsed and shown on the console. > > (MultihopOscilloscopeMsg is the MIG generated file!) > > > > Also, > > > > java net.tinyos.tools.Listen application shows raw data on console. > > > > But what i want is not only the field values of oscilloscop_t but also > the > > fields of CollectionDebugMsg structure. > > You might want to look into apps/tests/TestNetwork to see an example > that enables those log messages. > > > Actually, i also want to see the field values of ctp_header_t, > > ctp_router_t,... structures all in the ctp library! > > In Receive.receive, you should locate the CTP header in msg. Right now > it just grabs the payload and sends it over the UART so you are not > logging the headers. > > - om_p >
_______________________________________________ Tinyos-help mailing list [email protected] https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
