Dear Mazid H Chowdhury, I think your port cannot be /dev/ttyS0. It is because there are two ports created for mica2/micaz. One is for programming a mote with smaller number and other to communicate with the mote with larger number. For example in my case progamming port is /dev/ttyUSB0 and for serial communication I use /dev/ttyUSB1. I think in your case the right port will be either /dev/ttyS1 or /dev/ttyUSB1.
best regards, ---- Faisal Aslam Ph.D. candidate University of Freiburg http://cone.informatik.uni-freiburg.de/people/aslam/ Michael Schippling wrote: > The mica2/Z thing in MOTECOM also selects the header format > and my belief is that T1 defaults to the mica2 struct for serial. > But I think Listen would complain if it was getting the wrong fmt. > > I think motelist only works with USB connected devices. > > What basestation adapter are you using? The MIB510 has a silly-switch > that cuts off communication in one direction. There are sporadic > posts on this list that explain... > > MS > > Mazid H Chowdhury wrote: > >> Thnx MS, >> >> Actually I am using VMWare + XUbuntos in WindowsXP. So my port is - >> /dev/ttyS0. >> I've been using this port for uploading my programs. >> Also regardless of whatever I write (mica2 or micaz) the baudrate >> would be the same (57600). >> and about motelist, I have tried it earlier but it always gives 'No >> device found' result. >> But I can flash my motes anyway. >> >> I have waited like 30 minutes for some result to show up but nothing >> happened after the >> message - >> serial@/dev/ttyS0:57600: resynchronizing >> >> Anymore advice please? >> >> MazidH >> >> NB: I am also searching for some c/c++ code that can give me a GUI or some >> means >> to get raw data or processed data sent by motes. I don't have that >> much of Java knowledge. >> I am using Serial Gateway for this purpose. >> >> >> On Thu, Jul 2, 2009 at 6:44 PM, Michael Schippling<[email protected]> wrote: >> >>> Make sure you are using the right port number. COM1 or >>> ttyS0 is the default serial port on most Widows systems >>> and is often connected to a modem. If you are using >>> a USB interface to the mote you may be able to use >>> a "motelist" program to see what ports are in use. >>> >>> Also it's likely that you need to use "mica2" instead >>> of "micaz" as the usual T1 behavior is to translate >>> serial messages into the base level tos/types/AM.h format. >>> >>> MS >>> >>> >>> Mazid H Chowdhury wrote: >>> >>>> Hello all, >>>> >>>> I have compiled the Oscilloscope by following the Lesson 6 >>>> (http://www.tinyos.net/tinyos-1.x/doc/tutorial/lesson6.html). >>>> >>>> At the Listen tool point, I don't get the expected result that are >>>> provided in the document. >>>> >>>> I use the commnad as - >>>> >>>> $java net.tinyos.tools.Listen -comm serial@/dev/ttyS0:micaz >>>> >>>> The result is - >>>> serial@/dev/ttyS0:57600: synchronizing >>>> >>>> and then its just blocked at this point without any activity. I don't >>>> know why I don't get the expected 'received' and 'sent' raw data >>>> visualization. >>>> >>>> Thanx in advavance for anybodie's help. >>>> >>>> MazidH >>>> _______________________________________________ >>>> Tinyos-help mailing list >>>> [email protected] >>>> https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help >>>> > _______________________________________________ > Tinyos-help mailing list > [email protected] > https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help > > _______________________________________________ Tinyos-help mailing list [email protected] https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
