Propeller - XBEE - addressing issue
macHVD@gmail.com
Posts: 1
Here's the situation:
On 1 side a RealBasic application that sends info via XBEE - TX frames 64Bit addressing
on the other side an XBEE connected to a propeller chip. I use API frames.
I try to send data frames towards the propeller via my RealBasic application but nothing arrives on the propeller side if I use the address of the receiving XBEE in my frame
However if I do a broadcast frame the propeller does receive the information.
What I tried so far:
- 64 bit addressing
- 16 bit addressing
- API non escaped
- API escaped
- switch the XBEE modules
- Broadcast frame (works)
- Node discovery (works)
- hook in a logic analyser to make sure something is passed to the propeller.
Frame contents:
64 Addressing : 7E00 1200 0100 13A2 0040 3226 A201 5432 3035 3132 3588
Broadcast : 7E00 1200 0100 0000 0000 00FF FF01 5432 3035 3234 3876
Does anyone have a clue what I could check since I don't anymore
On 1 side a RealBasic application that sends info via XBEE - TX frames 64Bit addressing
on the other side an XBEE connected to a propeller chip. I use API frames.
I try to send data frames towards the propeller via my RealBasic application but nothing arrives on the propeller side if I use the address of the receiving XBEE in my frame
However if I do a broadcast frame the propeller does receive the information.
What I tried so far:
- 64 bit addressing
- 16 bit addressing
- API non escaped
- API escaped
- switch the XBEE modules
- Broadcast frame (works)
- Node discovery (works)
- hook in a logic analyser to make sure something is passed to the propeller.
Frame contents:
64 Addressing : 7E00 1200 0100 13A2 0040 3226 A201 5432 3035 3132 3588
Broadcast : 7E00 1200 0100 0000 0000 00FF FF01 5432 3035 3234 3876
Does anyone have a clue what I could check since I don't anymore