回复： Re: [Tinyos-help]: No message was outputed when using Oscilloscope and

[Renee Azhen]

You are so greatful, Michael, you guy are so experienced in this area, I am thankful to your help so much.
   
  I search in the Mailing List Archive(Is this the help list in general you mensioned??), and find another guy once had the same problem, and he told that the telosb baud rate is 57600, not 19200. and I made this changet, all things goes all right:)
   
  I am quite understand the baud rate here, in my mind, baud rate means the number of times a signal in a communications channel changes state or varies. so here, why using 57600 and 19200 so different??
   
  really appreciated your help
  Sam

Michael Schippling <schip at santafe.edu> 写道：
  First try using MOTECOM=serial at COM9:telosb or "tmote"
since I think 19.2 is the wrong baud rate and the platform
name may also select some message parsing "features".
But I would expect to see some garbage from Listen even
with the wrong settings.

I believe Oscope blinks an LED when it transmits. Do you
see any action on the mote? If you have access to the Boomerang
code from ex-Moteiv, there is a set of Count demos, one being
CountUart which eliminates a lot of excess baggage when testing.
I don't think there is an equivalent in the regular apps.

The SENSORBOARD thing is specific to micaX's so you can safely
do nothing when using telos's. Oscope and other demos use
platform/msp430/DemoSensorC.nc which is connected to ADC port
10 (INTERNAL_TEMPERATURE), which provides almost no interesting
data, but at least does something...

And, no, neither you nor most anybody else needs SerialForwarder.
The Port Busy message usually means that some other program has
that port open. You may still have a Listen running or something.
With the MOTECOM setting as shown above, Listen should connect
directly to the right USB port, on Windows anyway (assuming that
motelist shows that COMx for your device). I think there was some
FTDI driver stuff that had to be installed to get to the USB.
I did for tmotes anyway...

Also...I hope you are looking at the help list in general
because all my sends to yahoo's get bounced right away...

MS



Renee Azhen wrote:
> dear all,
> mine using is tinyos 1.x, I have uploaded the apps/Oscilloscope code 
> into to a telosb platform, and then use Command java 
> net.tinyos.tools.Listen to start the Listening program, but only
> $ java net.tinyos.tools.Listen
> serial at COM9:19200 : resynchronising
> no more info was outputted.
> 
> when using "motelist", only COM9 was connectted to a node, so I set
> export 
> MOTECOM=serial@*COM9*:192 
> 00
> 
> in the tutorial Lesson 6, there is word:
> Remember to set the SENSORBOARD option in apps/Oscilloscope/Makefile 
> 
> to either micasb or basicsb depending on the type of sensor board you have.
> my sensor node is a telosb node, I don't know whether it is because is 
> neither micasb either basicsb, there was no output message.
> 
> Could you help me? I will really be thanksful for your help
> thanks
> Sam
> 
> ------------------------------------------------------------------------
> 天生购物狂，狂抢购物券，你还等什么！ 
> 
> 
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> Tinyos-help mailing list
> Tinyos-help at millennium.berkeley.edu
> https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

-- 
Platform: WinXP/Cygwin
TinyOS version: 1.x, Boomerang
Programmer: MIB510
Device(s): Mica2, MicaZ, Tmote
Sensor board: homebrew

_______________________________________________
Tinyos-help mailing list
Tinyos-help at millennium.berkeley.edu
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help


       
---------------------------------
天生购物狂，狂抢购物券，你还等什么！ 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://www.millennium.berkeley.edu/pipermail/tinyos-help/attachments/20071217/9d2e0ff9/attachment.htm