I'm having issues trying to decode a XBee API packet. I start decoding it, but I'm not sure what my actual analog data should be. Several of them look like:
7E - start
00 - length byte 1
12 - length byte 2
83 - API identifier
56 - source address byte 1
78 - source address byte 2
43 - RSSI value bytes
00 - option byte
05 - sample quantity byte
02 00 - channel indicator 0000 0010 0000 0000 (A0 is active) (IO header) (I'm not sure if this is right)
last byte is chechsum
I'm using the XBee series 1 using XB24 firmware. I have a Lilypad temperature sensorbased on the MCP9700.
Every time I try to get the ADC data I get a huge number like 51228675.
The doc also says if any of the DIO lines are the first two bytes are the DIO sample. Why do I get "03 FF" or "E8 03" and sometimes "00 00" if I don't have any of the DIO lines active?
Schematic: Lilypad Temperature Sensor (pin S) --> Xbee (pin AD0)
Any help is greatly appreciated trying to find the sensor output.
kynix05
19 Apr 2017, 09:39 ( Updated at: 19 Apr 2017, 16:05 )
I'm having issues trying to decode a XBee API packet. I start decoding it, but I'm not sure what my actual analog data should be. Several of them look like:
So far I have:
I'm using the XBee series 1 using XB24 firmware. I have a Lilypad temperature sensorbased on the MCP9700.
Every time I try to get the ADC data I get a huge number like 51228675.
The doc also says if any of the DIO lines are the first two bytes are the DIO sample. Why do I get "03 FF" or "E8 03" and sometimes "00 00" if I don't have any of the DIO lines active?
Schematic: Lilypad Temperature Sensor (pin S) --> Xbee (pin AD0)
Any help is greatly appreciated trying to find the sensor output.
@kynix05