I am new to ArduPlane.
I have a bench setup with APM1 hardware, IMU OilPan, APM Planner-1.1.87, RC Receiver, ESC but without the plane.
I have ArduPilot-2.34 running on APM1. I am able to connect to the APM1 hardware using the APM Planner. I calibrated the RC control input channels.
I do not see any attitude indication in the Artificial Horizon (APM Planner->FlightData) when I move the APM1 hardware. Raw Sensor readings of Roll, Pitch are zero.
However, when I run "test imu" on the APM Planner terminal, it says "Init IMU" and I start getting text readings on the console for Pitch, Roll and Yaw varying from -10 to +10 as I move the hardware.
I also tried loading parameter files bixler.param and easystar.param. There is still no indication on the attitude display.
I tried loading older versions of the code from 2.32. There is still no indication on the attitude display.
For testing I downloaded and installed ArduCopter-2.5.4 on the same hardware with same setup. The Attitude indication on Artificial horizon works well.
The Artifical Horizon in this case displays "Disarmed".
Please help me resolve this issue.
what board type do you have?
or apm1 2560
Thanks for the reply.
I use APM1 with 2560
Found the same problem listed on another thread:
The problem in brief:
- MissionPlanner-1.1.87 with APM1 + ArduPlane-2.34 = No HUD (Attitude Indicator)
- MissionPlanner-1.1.87 with APM1 + ArduCopter-2.5.4 = HUD Ok
Wondering if there is a difference between ArduCopter and ArduPlane in the way the data from the APM1 is routed over the USB COM port to the Mission Planner.
Or If there are any conditions MissionPlanner checks before it displays attitude. And these conditions are met by ArduCopter but not ArduPlane?
I had the same problem until I discovered it's not a real problem, just different behaviour between Arducopter and Arduplane.
When connecting via the USB port with the Arducopter application, the real time streams will be enabled. With Arduplane it appears that the real time streams are only enabled on the Xbee port when the switch on the side is in the away from edge position. If you hook up an OSD or use an Xbee everything should work ok for you.
Hi Peter !!!
Problem Solved !!! Your suggestion was of great help !!! I can now proceed with my plans !!!
I do not have Xbee or an OSD. As you suggested I flipped the switch to "fly" position (away from the edge, toward the GPS connector). I connected APM1 hardware to APM Planner the HUD indicates motion as I move the hardware !!!
Thanks again !!!
Interesting. I thought we had disabled that slider switch by default in 2.34. I'll check with the team to find out what's going on.
I am facing the same problem again ... just when I thought that it was solved !
I was using the pre-compiled ArduPlane-2.34 binaries through APM Planner for the hardware checks as well as for HIL simulation. The HIL works very well with the autopilot flying the aircraft through the waypoints that I defined. After this success I was integrating the setup with the plane. That's when I started facing the problem again.
After the recent upgrade APM Planner now downloads the 2.40 binary and not the 2.34.
With ArduPlane-2.40 my HUD/Attitude indicator is not working irrespective of whether the switch is in Fly / CLI position. I can connect to the hardware via MAVLink 1.0 (USB). I can also perform "test imu" with the results same as what I described earlier. But there is no attitude indication.
I also tried connected to the APM1 hardware using 3DR radio. Connection was ok. Again no attitude indication. Switch was in "Fly" position.
Since the 2.34 binary is not downloaded by APM Planner now, I compiled and loaded the 2.34 code using Arduino-022. I was surprised to see:
a. In "Fly" switch position I am not able to connect to APM1 ... says serial link slow.
b. In "Fly" switch position - I am not able to connect even using 3DR radio.
c. In "CLI" switch position - connection ok - no attitude indication.
d. The 2.34 code compiled in HIL mode works fine.
I again tested with ArduCopter-2.6. The attitude indication works fine. So I think there is no problem with the hardware.
Any ideas? Please help me resolve this problem. Wish to get the autopilot in air asap !!!