basic problem i am having is that my Telemetry setup wont communicate with my APM.

hardware:

Software:

  • Mission Planner 1.2.67 
  • init ArduCopter V2.9.1b

My first problem was that the Xbee would not even communicate with themselves before ever connecting to the APM. Turns out that if you have the "Xbee explorer adapter" from sparkfun you have to edit your Xbee firmware to correct pullup resister parameters  (this is a whole other issue). Once i fixed that i was able to have my Xbees range tested and all worked out correct. I connected my APM to the PC via usb and made sure that my firmware and updates are ok and all went fine.  The problem is that when i connect my Xbees to the APM @ 57K at the correct port (USB is not connected so not to conflict with telemetry) it wont connect. My Adapter board on the PC side has LEDs (TX/RX) that don't light up indicating to me that there is nothing coming from the mission planner software to even try and connect. Have I missed something that needs to be configured on the Mission planner side that i have not realized? I am at a complete loss.

Views: 2359

Reply to This

Replies to This Discussion

I was having similar issues until I realised my APM was doing funny things to my airside Xbee by sending it data before it was ready. I don't think it was bricked, as I could still plug it in and connect to it using XCTU, but it certainly wasn't working properly.

I restored it using the steps here and then set the telemetry startup delay parameter (TELEM_DELAY) to 10. This forces the APM to wait 10 seconds after boot up before it starts spitting data out to the Xbee. Seems to work now.

I have changed the parameter (TELEM_DELAY) to 10 and am still having the same issue. It's as though when i press connect on mission planner nothing is happening. My XBee shows no sign of trying to connect. Error: "No Heartbeat Packets Received".

Here are the things i check:

  1. I check the communication of Xbees with a range test by shorting the Tx and Rx on the aircraft side. This works.
  2. I check the firmware on both Xbees to be sure that the baud rates are correct.
  3. I check the baud rate on the PC to make sure its also at 57600. I have changed the PC baud rate many times to check other rates.
  4. I check voltages on all V+ inputs and outputs relating to networking.
  5. I have checked the SERIAL3_BAUD and i have it at 57 :57600.
  6. I have forced my USB port to give more voltage for my Xbee.

I have even changed the baud rate on all network devices and tested again with the same results. I will test my Xbees through arduino but nothing on my Xbees have failed other than having to unbrick them when i made some mistakes. 

Whenever you had this issue was your Xbee on the PC side not sending data?

From memory my PC side Xbee would light up when trying to connect, but not the airside one.

The fact that range test works for you means that the PC->Xbee1->Xbee2 link is working. Something is falling over between Xbee2 and APM.

Sorry, I have no idea what this could be. Hopefully someone else has some suggestions.

Did someone resolve this? Any inputs are appreciated as I am facing the same problem but with Pixhawk and XBee Pro S1 not communication. The two Xbee modules communicate directly with each other when connected via PC.

Reply to Discussion

RSS

© 2017   Created by Chris Anderson.   Powered by

Badges  |  Report an Issue  |  Terms of Service