[HELP] sending data API mode 64bit address from XBEE wifi to XBEE 802.15.4

i am currently doing a project using xbee wifi.

i am now successfully sending the string data between xbee wifi to another xbee wifi and between xbee 802.15.4 to another xbee 802.15.4.

the problem that i facing now is how to send a string data using api mode from xbee wifi to xbee 802.15.4 (64bit address mode)…

is there any procedure or step need to be set before send the data between those two different xbee…

if we read the manual, it mention about it can be done, but i fail to do so.

thanks in advance.


Both the xbee works on two different protocols. So, both cannot communicate with each other over RF.

Hi, I’m really sorry to hi-jack your post but can someone tell me how to post a new thread. I have no tab or anything else that I can find to get me started.

Many thanks.

Wah… thank you so much for this answer… yup its clearer now… and i now understand what is really happen…

thanks you so much…

p.s sorry for the delay… very busy this week forgot to see this forum…
any ways thanks again…


Both the xbee works on two different protocols. So, both cannot communicate with each other over RF.

thanks for replying my post…
you got the point… yup this is maybe the cause i cannot send the data between :
XBEE WIFI -> XBEE 802.1.4
XBEE 802.1.4 -> XBEE WIFI


by referring to page 33 in Xbee WIFI manual

TX64 and RX64 API frames

The intent of the XBee transmit and receive 64-bit API frames is to provide a standardized set of API frames to use for a point to multipoint network—a closed network of XBee Wi-Fi modules. These frames are compatible with the XBee 802.15.4 module.

from this what can i say is this XBEE WIFI can transmit using TX64 to XBEE 802.15.4…

correct me if i am wrong…

It’s stating that the API frame format is identical to the one used on the 802.15.4 XBee. The actual communication over the wireless link is different, though, so you can’t transfer data between a Wi-Fi XBee and an 802.15.4 XBee.

What Tom says is completely true.

This happens because of the different network protocols implemented at lower network layers (Physical and MAC layer) in both modules.

The XBee 802.15.4 module uses the IEEE 802.15.4 standard
The WIFI module uses the IEEE 802.11 standard

I hope this is clearer now :slight_smile:

The API formats are identical may be due to existing serial communication code can be used by changing only the serial number. So, that extra development can be reduced to transfer data with higher data rate.

This documentation is copyright © 2010 by Parallax Inc. By downloading or obtaining a printed copy of this documentation or software
you agree that it is to be used exclusively with Parallax microcontrollers. Any other uses are not permitted and may represent a violation of
Parallax copyrights, legally punishable according to Federal copyright or intellectual property laws. Any duplication of this documentation
for commercial uses is expressly prohibited by Parallax Inc. Duplication for educational use is permitted, subject to the following
Conditions of Duplication: the text, or any portion thereof, may not be duplicated for commercial use; it may be duplicated only for
educational purposes when used solely in conjunction with Parallax microcontrollers, and the user may recover from the student only the
cost of duplication.

This text is available in printed format from Parallax Inc. Because we print the text in volume, the consumer price is often less than typical
retail duplication charges.

XBee and XBee Pro are registered trademarks of Digi International Inc. Bluetooth is a registered trademark of Bluetooth Inc. Sig. Propeller
and Spin are trademarks of Parallax Inc. BASIC Stamp and Boe-Bot are registered trademarks of Parallax, Inc. If you decide to use any
trademarks of Parallax Inc. on your web page or in printed material, you must state that (trademark) is a (registered) trademark of (owner)
upon the first appearance of the trademark name in each printed document or web page. Other brand and product names herein are
trademarks or registered trademarks of their respective holders.

Digi has tried to standardize the API structure to allow more flexibility when developing with the XBee radios. This allows for different XBee radios to be swapped in and out of applications without having to make drastic changes to application code.

Example: Application developed for the United States using the XBeePro 900MHz module…New customer in Europe wants this product, but 900MHz isn’t allowed. By using a standardized API, the XBeePro 868 module can be used instead.

owh… understand… it just an API standard where when user want to change their system using different xbee, there is no need to change the API setting…