I recently purchased the XBee Pro programmable dev kit (XBP24-BZ7B-DK). I followed the getting started instructions found in the document titled “Getting Started Guide - XBee-PRO® ZB Programmable Development Kit”. I was able to get all the devices recognized by windows, load the unlocked boot loader and load the sample application called App32Transparent without any problems.
I am having problems getting all the X-CTU software features to work with the programmable (S2B) modules through the USB or serial interface though. For example, on the PC Settings tab of the X-CTU software, if I select the Digi PKG-U serial port and configure it for 9600 baud/HW Flow control/8 data bits/no parity/1 stop bit and then press the Test / Query button, I get a failure message saying that communication with the device failed. I know the device is working because if I go into the terminal tab I can go through the menus provided by the App32Transparent. If I connect to the X-Stick module’s serial port that came with this dev kit I have no problems with the Test / Query button and I am also able to read the firmware settings of all the XBee Pro S2B modules over the air.
At this point all I am trying to do is conduct a range test with these devices and I haven’t been able to find a clear document which describes how to do this. I purchased the programmable dev kit because at a later point I plan on customizing these modules more, but right now I just want to qualify the range.
The getting started document for the non-programmable XBee pro modules (http://ftp1.digi.com/support/documentation/90002009_a.pdf ) talks about setting up a range test, but it also seems incomplete and doesn’t appear to work on this setup.
Here is the current configuration of my XBee network:
Unit 1 - XStick (Network Coordinator)
Unit 2 - XBee Pro S2B (connected to serial adapter board):
Firmware = XBP24BZ7 - ZIGBEE ROUTER AT - 2270
MY (16 bit network address) = 1735
DH (Destination High Address) = 0
DL (Destination Low Address) = 8EF9
Unit 3 - XBee Pro STB (connected to USB adapter board):
Firmware = XBP24BZ7 - ZIGBEE ROUTER AT - 2270
MY (16 bit network address) = 8EF9
DH (Destination High Address) = 0
DL (Destination Low Address) = 1735
You are using the programmable which has API firmware. Unfortunately XCTU doesn’t support the range test for API mode. Additionally the programmable has an extra processor that is stopping the data from reaching the radio.
The manual states “To send data to the loopback cluster ID on the data endpoint of a remote device, set the CI command value to 0x12. The SE and DE commands should be set to 0xE8 (default value). The DH and DL commands should be set to the address of the remote (0 for the coordinator, or the 64-bit address of the remote). After exiting command mode, any received serial characters will be transmitted to the remote device, and returned to the sender.”
In order to perform a range test, you will need to do the following items to the radio connected to the computer.
Second module doesn’t need to be reprogrammed nor does it need the red loopback connector.
[list=1]
[li]Put the programmable connected to the computer into a bypass mode by sending the “B” command in the programmable bootloader menu.
[/li][list=a]
[li]Bypass mode allows direct communication with the Ember
[/li][li]Otherwise a program must be written and loaded that takes care of telling the radio what to transmit.
[/li][/list=a]
[li]Use XCTU Modem configuration tab to reprogram one module
[/li][list=a]
[li]Make sure baud rate is correct since Resetting module will not work, since it will reset the programmable processor and exit bypass mode.
[/li] If the request to reset the module comes, click cancel, and verify the baud rate. Also make sure that the programmable processor is in bypass mode.
(9600 or 115200 baud are the most common)
[li]Click “Load” button
[/li][li]Open attached profile “programmable_AT_LoopbackOnly.pro”
[/li][li]If desired for quicker turnaround time Change ATDH and ATDL to match Serial number of the other radio.
[/li][li]Change the ID if desired to be on the same network as the other units.
[/li][li]Change the Firmware Version # if desired
[/li][li]Click “Write” button
[/li][li]This profile changes the module to AT mode and ATCI = 12 (loopback testing)
[/li][/list=a]
[li]Plug power into the second module
[/li][li]You are now ready to run a loopback test.
[/li][list=a]
[li]Click on Range Test Tab
[/li][li]Click “Advanced” Button
[/li][li]Check the box for “Packet Delay”
[/li][li]Set the Min and Max packet delay to 4000mS
[/li] (This can be reduced to 1000mS if ATDH and ATDL have been set to the specific destination radio address.)
[li]Set the “Data receive timeout” to 15000mS
[/li][/list=a]
[/list=1]
After finishing the loopback test return the module to the original state by
[list=1]
[li]Put the programmable connected to the computer into a bypass mode by sending the “B” command in the programmable bootloader menu. (If not already in bypass mode)
[/li][li]Use XCTU Modem configuration tab to reprogram the module
[/li][list=a]
[li]Make sure baud rate is correct since Resetting module will not work
[/li][li]Click “Load” button
[/li][li]Open attached profile “programmable_API_Restore.pro”
[/li][li]Change the ID if desired to be on the same network as the other units.
[/li][li]Change the Firmware Version # if desired
[/li][li]Click “Show Defaults” button
[/li][li]Click “Write” button
[/li][/list=a]
[/list=1]
You can contact digi for additional support if needed.