Assuming that you have your CLASSPATH set so you
can get to .../opt/tinyos-1.x/tools/java, and a
MOTECOM environment variable that points to the
right serial port, like: [EMAIL PROTECTED]:mica2
You should be able to run them with:
java net.tinyos.tools.Listen
I doubt that there is any place to look for information
besides the source code...though Listen is mentioned in
the tutorials I think.
MS
Liangping Ma wrote:
Michael,
Thanks for your help. But I still got the same error
message, although I changed micaz to mica2 in the
command line.
Also how do you run Listen and ListenRaw? I found some
related files under
/opt/tinyos-1.x/tools/java/net/tinyos/tools:
...
Deluge.class Listen.class Send.class
Deluge.java Listen.java Send.java
DelugeAdvMsg.class ListenRaw.class
SimpleCmdMsg.class
DelugeAdvMsg.java ListenRaw.java
...
I tried to find some messages about how to use them
but did not find the right ones. Is there a location
caching all the syntaxes of all commands used by
tinyos?
Thanks in advance.
- Liangping
--- Michael Schippling <[EMAIL PROTECTED]> wrote:
You might try using Listen and ListenRaw to get
closer to the hardware.
And a simpler program like CntToLedsAndRfm to
minimize complexity...
Also, I don't know about xListen but it's probably
the same, you need
to use mica2 not micaZ in the MOTECOM variable when
using Listen. This
is because the regular TOSBase translates 'Z
TOSMsg's to UART TOSMsg's
which is what "mica2" expects to parse. If you
search back on the list
you should find a trace of my struggle with micaz's
in this regard.
MS
Liangping Ma wrote:
Hi everyone,
I have been bugged by the problem shown in the
title.
I was following Section 5 "Test Applications and
Drivers for Sensor and Data Acquisition Boards" in
the
"Getting Started Guide". The mote is micaz, the
sensor
board is MDA300, and the programming board is
MIB510.
I tried testing xlisten over an RF link. I
configured
the two motes per the instruction, and set up the
connection:
-------- -------------
| MDA300 | | MICAz (base)|
-------- -------------
| MICAz | | MIB510 |
-------- --------------<------->com1 of
PC
The first MICAz was programmed under
/XSensorMDA300,
and the second one was programmed under /TOSBase
with
node id 0. After I typed the xlisten command,
there
was no output. But if I switched on and off the
MICAz
radio attached to the MDA300, I saw the following
output. Unfortunately, the information received
was in
error. It seemed to me that the RF link was OK,
because the serial port received some signal.
$ xlisten -r -p -c -b=micaz -s=com1
xlisten Ver:$Id: xlisten.c,v 1.2 2005/06/21
01:36:06
pipeng Exp $ Using params: [baud=0x1001] [raw]
[parsed] [cooked]
com1 input stream opened
7e42ffff007d5d1d81000100000000000000000000000000000000000000000000000000001
429 [39] mda300 error: unknown packet_id (0)
MDA300
Error: unknown packet id (0)
7e42ffff007d5d1d81000100000000000000000000000000000000000000000000000000001
429 [39] mda300 error: unknown packet_id (0)
MDA300
Error: unknown packet id (0)
I also tried using -b=57600, but the output was
the
same.
Thanks in advance.
- Liangping
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam
protection around
http://mail.yahoo.com
_______________________________________________
Tinyos-help mailing list
[email protected]
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
_______________________________________________
Tinyos-help mailing list
[email protected]
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
