i’m testing a pic18f2620 to Tx to a Rx xbee pin. the pic/xbee node is setup with the DH&DL address of the coordinator and both are set to API=1 mode and set at 9600 baud.
however, the coordinator isn’t receiving packets from the pic/xbee node.
with this simple setup, shouldn’t the node be able to send the data as it is received from the pic to the coordinator?
or do i have to prefix pic Tx data with the 3 byte xbee header before the pic Tx’s?
Not in API =1 mode! For this you must send to the XBee a complete and correct API frame (see the XBee document). If the frame is not perfect the XBee silently ignores the frame.
There isn’t any “3 byte xbee header”. In API command mode it is an API FRAME that is sent.
What I believe you want is called transparent mode which is API = 0. Then and serail data into one XBee exits the other XBee.
transparent if you follow the user manual and on-line crib sheets on how to pair up two XBees for serial data. Or for many clients, use AT commands to select destination address. Or for peer to peer (no coordinator), use API mode.
waltr:
There isn’t any “3 byte xbee header”. In API command mode it is an API FRAME that is sent.
yes, i didn’t state it correctly.
so transparent mode i’ll configure. beats me but i get hung up on the API mode
thanks
stevech:
transparent if you follow the user manual and on-line crib sheets on how to pair up two XBees for serial data. Or for many clients, use AT commands to select destination address. Or for peer to peer (no coordinator), use API mode.
as i mentioned to waltr i get hung up on the API mode.
i need to use a coordinator, so one can use transparent mode, and AT commands? say, versus API mode and building a frame on the pic prior to Tx to the xbee?