I considder myself an above average troubleshooter, infact, I enjoy the process and off course the reward at the end, but after 3 days of trying and reading every forum and manual on the subject I am giving up.
This the problem:
1. I am not able to get the Arducopter to communicate with my USB based Zigbee, or with my Ardustation.
2. I have loaded the serial test code, but I am only able to see Port:0 which is the direct USB connection. I can see the "IC" light on the FTDI to Zigbee interface blinking, but nothing is received at the other Zigbee which is connected to the PC via the zigbee USB port interface.
I have been able to do the following:
1. Have 2 Zigbees comunicate with each other via X-CTU (terminal) and whatever I type in terminal A is displayed in Terminal B and visa versa. (see attached drawing)
2. To eliminate the Zigbees I have created a crosover cable between the USB to Zigbee connector at the PC and the FTDI to Zigbee interface at the Quad and now I see "Port:3" showing on the X-CTU (terminal). (see attached drawing).
3. When I have the USB to Zigbee connected and I start to enter data in X-CTU terminal, I can see the "RSSI" LED light up on the Zigbee installed on the Quad.
Strange as it may seems: If i test the components individually they check out but the moment I plug them in it fails to function.
1. Quad - APM 1280 v1.0 + IMU Oilpan + GPS, Mag
2. Ardocopter 2_0_49
3. Baudrate: 5700
4. Zigbee: XBEE Pro 24-B
Thank you in advanced for your help.
load a different function set/firmware for your radios, something point-to-multipoint rather than mesh. Make sure both versions match, the VIDs match, etc.
I don't have these model of modules, so I can only give an example. Some of my modules are XBP09-DM, but I reload them as XPB09-DP. If you contact Digi, they will (eventually) respond with why the mesh-based products are "unsuitable" as they have put it, for streaming data at this rate.
You *can* configure multiple radios such that you can use one ground station module, and two airborne modules, so no worries about that. As for the loss of packet relay features from mesh communication, I'm afraid there is more work to be done before Xbee mesh networking, in any form, can be leveraged by us. :(
Thank you I will try the point to point configuration. at this point in time I only need point to point.
load XBee Pro 802.15.4 and configure as shown in the link in Martint's post, and I think it will work for you.
Can you link to the Xbees you're using? What frequency are they?
We only support the Xbees in the official DIY Drones telemetry kit, which are 900Mhz, but other Xbees can usually work with a bit of fiddling.
Thank you for the links. I must admit that I have not seen that thread which almost certainly describes the problem that I am facing, but at the same time confirms that the XBP24 2S is more troublesome.
I might have to digg deep again and go for the P2P version for now.
Thanks for your help.
Yes, I am able to make them communicate with each other using two USB interfaces if that is what you refring to.
I am using the Xbee Pro S2 (XBP-24) 2.4GHz which Mike correctly pointed out as being mesh and not P2P network versions.
Great to hear you have tracked down a way forward, I have never done it but I think Mike has given you a great way forward, the firmware can be swithed out on these units, so flashing the xbees to the 2.4 settings shown in my blog post should give you P2P and a much easier life!
If you get stuck drop me a mail and we wil see if we can get you running!
Thank you pointing me to your blog which I find very informative. After reading your blog I found out that I did not have the bridge on my FTDI CTS board,
I have attempted to load XBee Pro 802.15.4 function set, but in all cases it tell me that the selected function set is not supported. I have the XBee Pro 50mW 2.4 GHz Series 2.5 w/Chip Antenna, is this roughly the same as yours?
That is true, the information is rather sparse, but I am logging my progress and hopefully this will be used by someone else.
I have the DIYDrones FTDI interface.