I am having a lot of trouble communnicating with my ACM Quad.  Since I switched over to ACM, I can't communicate with it.  I keep getting bad packet or readpacket read errors in mavlink.  The XBEE doesn't work at all but the USB occasionally works.  I rechecked all connections and am getting 4.95V on my power from the power board.  I reloaded all drivers (labview, USB, etc., and tried reloading the firmware (several times).  I switched my receiver from AR6100 to AR7010 (spektrum) and back.  On the rare occasion I get the motors from beeping at 4 CPS (my other problem), I can't arm them.  I tried manually setting the ESCs to no avail.  Every now and then, I'll get a readout from the sensor display in mavlink but then it locks up and I have to restart it (mavlink).  When I ran the motor test one time I thought things were looking good, motors 0 and 1 (front right and back left - x config) don't spin up, even though they do when I manually set ESC.  I'm getting the fast flash blue for receiver and the GPS eventually goes solid.  I've tried reseting the ARM as I open communications too.  Please, any advice would be greatly appreciated. 

Tags: USB, XBEE, communications, error, packet, read, telemetry

Views: 1073

Reply to This

Replies to This Discussion

Hi,

You may have already done these, but it must be mentioned.

*Make sure/verify (I would set it in your APM_config.h) the APM is configured to the baud rate of your xbees, or vise-versa.

*Make sure to reset the EEPROM and reset factory settings.

Good luck!

Thanks John - I'll try the settings in apm_config.h - I think that may solve my Xbee problem.  I still have the general communications problem with usb though.  I have resetted factory settings several times (no less than 5) and have different results when I boot up.  It's getting frustrating as I had most things working with Ardupirates (which doesn't seem to work any more now) then switched to ACM (latest and greatest).  I think the mavlink read packet errors are an indication of something wrong but I can't seem to find a resolution there.  I'm concerned that even if I get teh XBee working, I may have errors there as well. 
I also cannot connect with usb. I never tried xbee yet. I tried multiple svn versions and loaded code from APM Planner. I can setup with CLI mode with usb no problem. When I try to setup sensors with switch forward Mavlink reports
CommsServer listern accept
CommsServer listern wait
MAVLink readpacket read error: NetSerial Timeout on read
bps 0 loss 0 left 0
Mavlink Bad Packet (crc fail) len 0 crc 65535 pkno 0
MAVLink readpacket read error: NetSerial Timeout on read
bps 0 loss 0 left 0
This happens on my xp netbook and win7 desktop.
Thanks Steven - that's exactly what I'm getting. 

Hi,

In Arduino, or any other serial terminal configured to the correct baud rate of the APM's USB port, what is the output? Is it consistent using this method? Is it just the MAVLink connection that's being a pain?

Thanks- let us know.

Hi all,

seems that I've the same problems.

Same MAVlink errors like Steven.

CLI Mode over USB works error free. so setup was done very quick.

But after switching to flightmode (and repower the system) MAVlink comm errors (over USB).

Default Firmware AC2 with + configuration APM2560

 

Are you sure you're switching the Mission Planner baud rate to 115200 for USB? I can't replicate this problem on my machine.

And are you using the HK GCS?

Hi Chris

I used the the AC2Setup of the Mission Planer.

In Setupmode all ok, in Sensor mode error messages like steven.

So baudrate shouldn't be the problem.

Maybe the flightmode is the problem. maybe one of the busses (i2c,spi) working not well

in our configuration and slow down the software so much that mavlink will produce timeouts?

 

Hi Chris-

 

I am switching to 115200 for USB and attempting to do the same for XBee.  USB works with the errors that Steven mentioned.  I (and I believe many others) are getting the same result.  I've tried otehr baud rates and resetting and reloading.  I've put 30 hours into this in the past four days.  I'm never getting to the GCS as I'm not completing setup becasue of the communications problem.  The mavlink program errors out about every 15 minutes, requiring reset.  This is happening on three different machines similarly (xp and windows 7).

I realize it's hard to diagnose if you can't duplicate the prblem.  I'd be happy to send screen prints, diagrams, blood tests ;), or whatever else may help you. 

I'm having the same problem with Arducopter 2.0 Beta 3. First I had problems with Xbee, so putting that aside I tried using the USB connection.

I changed GCS_PORT to 0 in APM_config.h (and commented out the 3 lines between ifndef in config.h that set the GCS_port to 3 based on Chris's comments above those lines).

When I start up ArdupilotMegaPlanner, it works on ArduCopter Initial Setup. The CLI on Initial Settings also works.

Then I click on "Raw Sensor". It asks me to move the slider <away from rc connections>.

Then MAVLink opening fails and I see "MAVLink readpacket read error: NetSerial timeout on read" and eventually a CommsServer Shutdown.

I restart ArdupilotMegaPlanner and go to Initial Settings and verify that the CLI still works.

I get the same MAVLink timeout on GCS MAVLink and PID Config - AC2.

 

So it appears that I can't get MAVLink to work on USB. I verified that (a) Baud rate on the USB COM port is 115200 and and matches the settings in "Options" on APM planner (b) "Set RTS on Close" is turned on in the Advanced port settings in Device Manager.

Anything else I can try?

 

There should be no need to change any code at this point. The latest versions of AC2 have MAVLink running automatically on both the USB and Xbee ports.

Are you loading the code from the Mission Planner?

Are you restarting the APM board after you move the slider switch?
Yes - The first time I uploaded the code from Mission Planner, the XBee didn't work and it wasn't responding to the throttle correctle, so I reset, cleaar eeprom, reloaded, other similar problems started, including the communications problem.  I've uploaded the firmware at least a half dozen times, very few with exactly the same results but never entirely successful.  Xbee hasn't worked since I switched to ACM and mavlink has worked to varying degrees of success.

RSS

Social Networking

Contests

Season Two of the Trust Time Trial (T3) Contest has now begun. The fourth round is an accuracy round for multicopters, which requires contestants to fly a cube. The deadline is April 14th.

A list of all T3 contests is here

Groups

Advertisement

© 2013   Created by Chris Anderson.   Powered by

Badges  |  Report an Issue  |  Terms of Service