The ArduCopter & ArduPilot Mega telemetry kit utilizes the Xbee Pro 2.4 GHz 63mw modules; this is the kit for use in the UK, EU and other parts of the world where the 900 MHz Xbee’s can’t be used due to mobile phones using the same frequency. This telemetry kit supports two way communication with the mission waypoint read and write functions in both Michael Oborne's Mission planner and HappyKillmore’s GCS on both the latest APM and ACM codes. This means no more USB cables & landings to connect the ArduPilot to a laptop in the field, you are able to view live telemetry data as your airframe progress through the mission, you can load a new mission on the fly while your UAV circles above you and execute that new mission without having to land! The range of operation has been tested out to half a mile with no loss in connection, connection has been found to drop off at 3/4 of a mile. Included in the kit are all the items you need to have a fully functioning telemetry system: 2 x Xbee Pro’s series 1 (1 x whip antenna 1 x RPSMA). Ground and airframe adaptor boards (2 x XteamBee's). Antenna (RPSMA High gain 4.9 dBi). Connecting cables for both the GCS and airframe.
The kits is available two forms: Either as a pre soldered, fully programmed and tested kit, so they are completely plug and play or in a self built kit, for those of you who like to build your own. The kits are now in stock at www.buildyourowndrone.co.uk The 2.4Ghz Pro series 2 Xbees (firmware XBP24-ZB, XBP24-B) do not work with the DIY Drones Xtreme Bee boards. Please use Sparkfun Xbee explorer boards. Instructions: Build the Xtream Bee’s: The XtreamBee boards need to be built, this involves some soldering and is not complicated if you are experienced with soldering, however a word of warning here, when soldering the female headers, don’t use too much solder! The male pins of the Xbee modules will not fit into the female headers if any excess solder runs down inside the holes on the PCB, it will fill the female headers with solder, this is not good! When the soldering of the female header connections is complete you will have to solder the connection pins for the FTDI / telemetry cable to the APM and the computer. To enable the to way communication in the GCS’s you will need to hold the CTS line high, this is done with a solder bridge from the VIN line to CTS line. This modification is required on both XtreamBee boards with FTDI connectors, it is not needed with the USB GCS XtreamBee board now supplied in the kit. When you have completed the construction of the XtreamBee boards set both slide switches to master mode, you can now add the first Xbee module to the XtreamBee, you will see that there is an white outline of the Xbee on the board for orientation, please ensure you select the correct orientation to save the XBee unit from being damaged! Before adding any power to the board make sure that the Antenna on the RPSMA Xbee is attached and screwed all the way on, powering the unit without the antenna being fitted or incorrectly fitted will cause the unit to fail! Install the Xbee’s and Program: When the Xbee is fitted to the XtreamBee and the antenna has been connected power the first board using the supplied FTDI cable, note the orientation of the lead colours (see image above), the black wire needs to go to the pin marked “BLK” on the top side of the board or “GND” on the underside. If this is placed correctly you cannot get the other connections incorrect! The Xbee’s come set at a data rate of 9600, this needs to be changed to the higher rate of 57600. To do this you will need to use a free program called X-CTU Down Load Here: In "PC Settings" select the comport that the XBee is connected to, then go to the tab marked "Modem Configuration". Always select the update firmware option, click "Read", change the rate in the box shown above and then click "Write". When you have changed the rate on the first board, remove the first Xtream Bee and switch over with the other, program the second one in the same way and to the same rate as the first. The set up of the Xbee’s are now completed! Adding the Telemetry to APM: On the APM you will see that there is a total of four connection ports marked "Teleport", (if you don't have the male pins to solder to the teleport for fitting the telemetry cable they can be found here) which will need to be connected to the airframe part of the telemetry kit. There are two pins for the power and two for the communication. Once again if you look at the XtreamBee you will see there is a “5v+”, “GND”, “In” and “OUT”. With the supplied APM telemetry cable you will find one end has 4 connections and the other has 5, the 4 goes onto the APM and 5 onto the XtreamBee, match the two ends to the corresponding pins and the APM is ready to send telemetry data to the GCS. How to get the data: To start using the telemetry, power the APM first which will power the airframe Xbee, power the GCS Xbee second, then load the Mission Planner or HK’s GCS select the correct comport and speed (57600) and click connect. You will now have your telemetry up and running! Always select disconnect in the GCS before removing power from either of the units, I have found that on odd occasions if you just unplug one unit / switch the power off without disconnecting in the GCS you can lock a unit, this is easy to solve by reprogramming the XBee again, but to avoid it reverse the connection process. Tests: Use of 2.4 GHz Radio and Telemetry together: This kit has been tested both in the field and in a lab environment to check for any clashes or interference between the RX/TX of the radio equipment operating on the same frequency as the Xbee’s, no conflicts have been found to exist. The Xbee units on power up look at the frequencies available in the channel they have assigned, they will then select the one which has the least amount of noise, this is called DSSS in the world of Xbee’s, the DSSS operates in a very similar way to that of the 2.4 GHz radios with frequency hopping, which means we can fly more than one aircraft at a time and still use the same 2.4 GHz band as the pilot standing right next to us. The field tests conducted were first with the radio on “range Check” which is a very low power setting, the Xbee was set to full power and placed on top of the RX and APM, the TX was taken to the minimum recommended distance and some way beyond, at which point there was still a solid lock and smooth operation of all the connected servos. The second field test was conducted in a wide open space, where once again the Xbee was set to full power and was left on top of the APM and RX, the TX was in normal “flight Power” mode and was taken to approx 1.3 miles away with line of sight, there was no loss of connection to the servos, they still operated as if there was not a telemetry kit working right next to the RX. The radio I used throughout all of the field testing was a Futaba T7C, I have also released three full test kits to customers to try with additional radio equipment, all non Futaba, some of the radios tested were $60 specials while others were top end systems, all tests conducted have proven to be successful with no loss in control at any time and easy to use telemetry from the box. While no concerns or issues have been identified with the telemetry kit and the radio systems when tested in the field or lab, it's highly recommend that a “range check” be carried out before committing to flight, if you can maintain a solid RX / TX lock at lowered powers on the ground beyond the minimum distance recommended then flight should not be an issue. Regards Martin www.buildyourowndrone.co.uk |
Comments
How was this problem solved? I have a similar setup. APM 2.5 with XBEE 2.4 802.15.4 firmware 10ED. The Xbees comunicate properly through any terminal program and with an Arduino Uno, but will not communicate via the telemetry port on the APM 2.5 to X-CTU or to the mission planner. I have read some solutions to solder pins to the UART2 port, but I would prefer to not add extra pins so the APM will continue to fit in its case. Thanks for any suggestions.
I have two Series 2 Pro 2.4Ghz xbees. I have a sparkfun USB adaptor for the GCS and both a sparkfun and DIY drones adaptor (without CTS soldered to 5v) for the aircraft.
I configured them using this tutorial: http://www.seeedstudio.com/wiki/Zigbee_Networking_with_XBee_Series_...'s_Products
just incase that link goes, I upgrade from XBP-24B to XBP-24ZB firmware on both xbees. I set one as coordinator AT (GCS) and the aircraft xbee as router AT. I made use the PAN ID were both 0 and set the destination address of one to the serial number of the other and vice versa (there is a comment in these comments which explains that in more detail). After this I did a loop back range test using the jumper provided with APM2.5 (thanks for that). This didn't work, so I checked my settings again and found that one of my PAN ID's was still on 234. I changed this and then the range check worked perfectly.
I then set the baud rates (decided to leave this till now so as to only require the minimum amount of changes prior to range testing) to 57600 and tried to connect via mission planner.... no luck. I decided to try swapping the switch on the DIY drones adaptor from master to slave. At which point everything works!
My question is:
Is this a known 'kinda works but something bad is going to happen' set up or can I sit back and relax knowing that all is well? My reasoning behind swapping the switch is that I have set my aircraft xbee to 'router AT' and is therefore a slave to the 'coordinator AT' at the GCS.
please
about APM 2.5 and connecting the xbee 2.4
and i bought this http://store.fut-electronics.com/11XBp24bZ7pIT-004.html
waiting for answer.
Well, thank you all, problem solved.
No one to help me out here?
Not working here, i have the impression, that the ''missionplanner'' get no connection with the xbee module.???
i changed it on the apm side and it worked with me.
Thanks for your comment, how can you switch tx and rx, when the xbee is on a usb board/cable, on the apm2.0 side i have tryed that, no succes so far.
i had the same problem, but after switching the tx and rx wires it was solved!!
Hi to you all, i'm out off options here, and need help with the xbee 2.4 pro 802.15.4 firmware 10EC.
I configured both the modules as coordinator with baud-rates 57600. Both modules could communicate properly and perfectly with the x-ctu program. The loopback test gave me 100% result. so the xbee's are working fine together.
But when i want to connect true the missionplanner (latest version, com port and baud rate matching the xbee) via usb cable, I get no connection. not a blink on the xbee adapter board. Only the power led lid up.
What can I do to make it work please, read a lot on this forum, but still no solution found so far, please help me out here ! please, please, please.