If the DeltaMsg is in fact what is stuffed into the "data" area of
your MultiHop dump, then you may have found your sensor reading.
Since the first 4 bytes of that message are called "seqno", do
you see those bytes incrementing?
Without actually working on your system I can't really figure
out what is going on. I now have a tickle-memory that there were
two message types coming from the Delta application, but I never
bothered to decode them, and a cursory look at the program doesn't
reveal what other messages are being used.
Your CountUart Listen dump looks correct to me, so you must be getting
_some_ kind of good data. But I have no explanation why you only see
the 0x65 type message, or what it represents.
Sorry, but I guess you have some in depth compu-archeological digging
to do in the source tree. Adding "PFLAGS += -v" to the makefile will
give you an _extensive_ list of source files being compiled...Or you
could try using the Oscilloscope program as an example since it may
be more straight-forward.
MS
Saif A. Al-Hiddabi wrote:
I did compile the CountUart and I get the following from the listen
04 00 00 00 00 00 7E 00 04 7D 00 5F 00 01
04 00 00 00 00 00 7E 00 04 7D 00 60 00 01
04 00 00 00 00 00 7E 00 04 7D 00 61 00 01
So I do see changes in the third column from the right. But why this is not
the case with Delta, by the way the "log" output do reflect the temperature
ADC Counts since
1193897839449 Message <MultiHopMsg>
[sourceaddr=0x1]
[originaddr=0x1]
[seqno=0x6d8]
[originseqno=0x6d8]
[ttl=0x0]
[id=0x21]
[data=0xde 0x5 0x0 0x0 0xa7 0xb 0x7e 0x0 0x3 0x0 0x7e 0x0 0xff 0xff 0xff
0xff 0x0 0x0 ]
Since (ba7) is 2983 and this is the scope reading. Unfortunately I can not
see this in the listen command which produce only
08 00 00 00 00 00 7E 00 65 7D 00 00 01 00 00 00 00 00
08 00 00 00 00 00 7E 00 65 7D 00 00 01 00 00 00 00 00
08 00 00 00 00 00 7E 00 65 7D 00 00 01 00 00 00 00 00
...
Any help?
SAIF
-----Original Message-----
From: Michael Schippling [mailto:[EMAIL PROTECTED]
Sent: Wednesday, October 31, 2007 11:01 PM
To: Saif A. Al-Hiddabi
Cc: 'Tinyos-Help'
Subject: Re: Where is the sensor reading in the received message?
In response to both of your recent messages....
There should be no difference between Listen results and display results,
if one changes the other should as well. So I can't explain why you don't
see any new data in the Listen output...
However the Listen output doesn't match the "log" output you show,
beyond what might be a source address of 1. My recent experience with
tmote messages indicates that the first 10 bytes are the telos/AM.h
header, so the bytes after the '7D' should be the payload. Assuming that
such payload is supposed to be a DeltaMsg from
moteiv/apps/Delta/Delta.h
then you are not getting enough bytes -- you should be getting more than
14 but are only getting 8. And the fields listed in the Multihop log do
not match the names of the DeltaMsg. Also the message type shown in the
Listen output is 0x65 but the delta message type is 33 (0x21).
So again I have no clue about what you are seeing...
I found that using the CountUart demo app (if you can get it to compile)
provided a more straight-forward connection between message and Listen
behavior...
MS
Saif A. Al-Hiddabi wrote:
I understand now the ADC count, thank to you. I tried [EMAIL PROTECTED]:tmote
and
I do get cleaner messages of the following structure
08 00 00 00 00 00 7E 00 65 7D 00 00 01 00 00 00 00 00
08 00 00 00 00 00 7E 00 65 7D 00 00 01 00 00 00 00 00
08 00 00 00 00 00 7E 00 65 7D 00 00 01 00 00 00 00 00
...
But this message continues with the same numbers and letters and nothing
change regardless of tmote temperature. When I use the Trawler I notice
the
change in the temperature significantly in the graph and the ADC counts.
Is
there any difference between what is displayed by the "listen" and what is
plotted by the Trawler? I mean where is the measurements and what bytes
the
Trawler is plotting? Is there a different way to look for the Delta
message
structure (i.e. different from what is shown above by listen command) what
I
should I do?
Regards,
SAIF
----------------------------------------------------------------------------
----
I logged this packet that is going to Trawler from Delta and I obtained
the
following
1193897839449 Message <MultiHopMsg>
[sourceaddr=0x1]
[originaddr=0x1]
[seqno=0x6d8]
[originseqno=0x6d8]
[ttl=0x0]
[id=0x21]
[data=0xde 0x5 0x0 0x0 0xa7 0xb 0x7e 0x0 0x3 0x0 0x7e 0x0 0xff 0xff 0xff
0xff 0x0 0x0 ]
Which bytes representing the temperature measurement in the above packet?
Thanks
SAIF
----------------------------------------------------------------------------
-
-----Original Message-----
From: Michael Schippling [mailto:[EMAIL PROTECTED]
Sent: Wednesday, October 31, 2007 5:01 PM
To: Saif A. Al-Hiddabi
Cc: 'Tinyos-Help'
Subject: Re: Where is the sensor reading in the received message?
Try [EMAIL PROTECTED]:tmote for your MOTECOM, I believe it will
select some special parsing for tmote messages. At least it let
me receive Delta msgs with Listen.
You'll have to go look at the Delta message structure to see which
bytes are of interest, I don't know offhand.
As to the 3000 value...I think we're talking a 12bit ADC whose max
value would be 4096 (if I remember any binary math....). So it's about
3/4 of the full scale reading. You might google info about calibrating
the sensor, but in general you can say 3000 is your room-temp-plus-
tmote-heat and go from there.
MS
Saif A. Al-Hiddabi wrote:
Hi:
I am new to using Tmote and started by testing the Delat application that
came with the quick start guide. I can see the internal temperature in
the
Trawler scope measured with DC counts (approx 3000) (I do not know what
ADC
count mean?) but I see changes in this value if I pass the Tmote near a
heat
source :) Now I tried to see the message that the Tmote is sending
through
COM4 port so I typed in the cygwin
$ export [EMAIL PROTECTED]:57600
$ java net.tinyos.tools.Listen
And I get the following
TOS_Msg length is invalid: header_length=5,real_length=18 ... modifying
msg
to fit
Received message:08 00 00 00 00 00 7E 00 65 7D 00 00 01 00 00 00 00 00
08 00 00 00 00
TOS_Msg length is invalid: header_length=5,real_length=18 ... modifying
msg
to fit
Received message:08 00 00 00 00 00 7E 00 65 7D 00 00 01 00 00 00 00 00
08 00 00 00 00
And it continues like this.
My question is where is the temperature reading in this message? And why
the
numbers/letters in this message are not changing if the temperature
around
the Tmote is changing? I tried to read the Tmote message (i.e. the
temperature) using another program that can read serial message from COM4
but I am getting this
7E 42 08 00 00 00 00 00 7D 5E 00 65 7D 5D 00 00 01 00 00 00 00 00 0D 31
7E
7E 00
7E 42 08 00 00 00 00 00 7D 5E 00 65 7D 5D 00 00 01 00 00 00 00 00 0D 31
7E
7E 00
And it continues like this? So how to retrieve the sensor measurement
from
such message?
I appreciate your help..
Thanks
SAIF
_______________________________________________
Tinyos-help mailing list
[email protected]
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
