Replies to This Discussion

Permalink Reply by Sergio Luis de Almeida on March 13, 2012 at 6:44pm

I had similar problems with my Xbee bought at Digikey.
With X-CTU, one card is recognized correctly and had no problems, since the other (which will in model aircraft) was not recognized.

I installed the firmware XBP09-DP forced and still did not work.
Then I realized that the "Function Set" was "232 Adaptor", I changed to "Xbee PRO 900" and after that everything worked.

• ▶ Reply

Permalink Reply by Cliff-E on March 13, 2012 at 6:57pm

You're not connected. You need the RSSI leds on both on. What is the function set (in xctu) loaded on your xbees?

You can always run the serial port test app, though it will blow away your firmware and you'll need to reload. Yes, in xctu, make sure the is modem XBP09-DP and the function set is  XBEE-PRO 900 and version is the latest number (1061).

I run digimesh on sparkfun boards, which works fine here (if you want to convert, let me know)--it's XBP09-DM/XBEE-PRO DIGIMESH 900/8062. If you have the XbeePro 900 or digimesh, you can load the digimesh firmware (same transceiver)--digimesh is a bit slower but more robust and easy to setup.

• ▶ Reply

Permalink Reply by Shaun Bell on March 13, 2012 at 9:30pm

I'm showing XBP09-DP and function is XBEE-PRO 900 1061.  I've got a couple of 2.4 xbee units, I'll give those a try.

• ▶ Reply

Permalink Reply by Cliff-E on March 14, 2012 at 11:00pm

You could try reflashing both units to XBP09-DM/XBEE-PRO Digimesh/8062 (just remember to cycle power on each unit then run a connection test at 9600) power them up using defaults (vid-999, 9600baud) and see if the RSSI leds come up. If that works you can go change the baud and vid and just run digimesh.

Best way to test is plug each unit into a USB i/o board and run xctu on one and hyperterminal on another and see the echos if you type in one terminal.

The rssi leds need to be both lit for anything to work.

• ▶ Reply

Permalink Reply by Shaun Bell on March 15, 2012 at 3:14pm

Thanks Cliff!  I'll give that a try tonight.

• ▶ Reply

Permalink Reply by Romp on March 25, 2012 at 9:57am

Any luck yet? I'm having the same issue.

• ▶ Reply

3D RoboticsPermalink Reply by Chris Anderson on March 25, 2012 at 10:03am

Make sure you're using the latest MP (1.1.56)

• ▶ Reply

Permalink Reply by Ian forbes on March 13, 2012 at 9:51pm

Shot in the dark, I am as newb as you, but I too can read a wiki and follow directions. No one helped me on my xbee issues, maybe I can at least share your woes.. HAH

 

I have had nothing but problems with my xbees, so I feel for you.  Mine acted quirky at first blue flickering oddly and red flash from time to time, leds would dim at odd times, was a loose ground wire on the  harness that came with it.  The pin crimper cut some of the straqnds and it was hanging on by a thread. Check the ground pins, pop the wire loose carefully inspect one at a time while you are powered down, I found mine (came with DIY adapters) had a bit of a loose ground and I bricked one of them the first round, I powered down put a new pin connector and it worked till it died a day later...

I think I am running the same setup xbees from digikey, are the adapters from DIY?  Mine worked great for a few days and then poof just stopped, checked and reflashed but I get nothing but solids on the drone side adaptor. I have only one usb and no ftdi cable to connect to the drone side, but both xbees are flashed properly according to ctx. 

 

 I have ordered a new adapter, if it isn't the adapter then it is something going on the apm side.  I will watch to see if you get this resolved, seems like general problems for us xbee "newbs".

• ▶ Reply

Permalink Reply by Ian forbes on March 25, 2012 at 11:36am

I have now gone to a third xstream adaptor on the drone side. 

 I have now purchased an ftdi to usb cable and a second usb adaptor to troubleshoot connection outside the APM software.  Both time it was indeed my Drone side adaptor.  The first one totally bricked (I mean hardware BRICK not software), the adaptor showed nothing but solid led, second one would try to connect, and get a sys ID error. Would not connect/read in x ctu even after unbrick attempt. 

The new adaptor connects just fine, so I know I was doing it right, and I know it was the adaptor.  Would seem inlikely to happen to the same person twice in a row.  If the usb adaptor will read the settings, and baud is set correctly and vin is correct and versions read corect vid usb on both xbees, I would try getting a new adaptor, and while your at it get the ftdi cable and an extra usb adaptor. You will need it eventually. 

 

So far Mine has now worked 4 days in a row (YEA!), but I also changed my wiring from the wiki to a distributed system.

 

 

• ▶ Reply

Permalink Reply by Earl on March 25, 2012 at 12:28pm

I connect my Xbee at 38kb by setting the serial3_BAUD in parms to 38. Also have Xbee's programmed to 38kb. For whatever reason 57kb doesn't work.

My one end point Xbee is on com4 at 38kb on a laptop.(Win8)

Another Xbee on APM2 on telemetry port is set to router. It is at 38kb also

3rd Xbee is in my er9x transmitter set as end point. Its baud is 38kb also.

Here is some pics.

Mission Planner 1.1.56 configuration screen.

See SERIAL3_BAUD circled in red ?

I am using XBP24-DM on all 3 set to 38kb. I use X-CTU to set the Xbee's up.

I have heard the APM2.0 programmed with 57kb has a library problem with 57kb. The speed seems a little off so it doesn't work. I have not confirmed this yet.

57kb on the laptop nor in the er9x TX seems to decode at 57kb.

Earl

BTW I am using Windows 8 Consumer Review !

The biggest problems are DRIVERS. You must disable driver signing to get most drivers to load. Took a while to figure that out !

• ▶ Reply