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
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
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
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
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
