Does any one know a solution to the problem shown in the attached picture.?
Using the latest version Arducopter 2.0.36 and the APM Planner 1.0.36.
Reuploaded the code several times. The board seems to work correctly in CLI mode but no Mavlink connection possible in fly mode.
Checked and double checked com port settings and drivers.
Tried it with and without ESCs, with and without rc receiver, with external 5V power supply and only with USB, with and without GPS module connected.
I can not figure out the problem at the moment.
Which Windows version are you using?
unable to get it to work either, Have tried everything possible. Works fine in CLI but will not connect in Fly mode. Currently using ver 1.0.46 of APM and the newest ARM for Fixed Wing
Joshua: look in the terminal window when it's restarting in flight mode. Does it pass the IMU calibration test? Or do the "****"s just go on forever?
Yeah, in the IMU calibration passes and the STARS do stop.
I can also load the firmware for Arducopter and connect via USB in the flight data screen just. Its only the fixed wing code that is giving me problems.
This exactly what came up.
myview width 1008 height 942
this width 1024 height 1056
myview width 1920 height 942
this width 1936 height 1056
listening for client - 1 client at a time
HUD 1 hz
And yes, the CLI switch is in flight mode.
Yeah (Mavlink Bad Packet <crc fail> len 0 crc 65535 pkno 0 MAv Data: len 0 btr 0)