Ardupilot stops working very often (software crash?)
Problem:
When I switch to waypoint-mode (ch5 100%) the MUX-LED lights up and the servos starts reacting (OK).
BUT, very often (about 40% of the case) the yellow STAT-LED goes off as soon as I enter WP-mode and everything stops working! No servo response att all.
If I then switch OFF the autopilot the MUX-LED goes off and the yellow STAT-LED always starts flashing again.
I can repeat this process many times and sometimes the STAT-LED keeps flashing, but suddenly it stops in autopilot/WP-mode! I guess the program crashes for some reason.
It seem to be very unstable! Does anyone have any idea what it might be?
I'm using the red ardupilot board (without the shield). I have XY- and Z-sensors, EM406 GPS. The board is powered from the ESC.
I'm having the same problem even if I unplug the GPS, Sensors and servos.
Software loaded:
ArduPilot_Easyglider_V246
Tested so far with success:
- GPS navigation on the ground. Flash a LED when you hit a waypoint. WORKS OK!
- Stabilization. Rudder and elevator responds to XY-sensor. WORKS OK! (only tested inside and the result are very unpredictable)
Regards
Tommy
When I switch to waypoint-mode (ch5 100%) the MUX-LED lights up and the servos starts reacting (OK).
BUT, very often (about 40% of the case) the yellow STAT-LED goes off as soon as I enter WP-mode and everything stops working! No servo response att all.
If I then switch OFF the autopilot the MUX-LED goes off and the yellow STAT-LED always starts flashing again.
I can repeat this process many times and sometimes the STAT-LED keeps flashing, but suddenly it stops in autopilot/WP-mode! I guess the program crashes for some reason.
It seem to be very unstable! Does anyone have any idea what it might be?
I'm using the red ardupilot board (without the shield). I have XY- and Z-sensors, EM406 GPS. The board is powered from the ESC.
I'm having the same problem even if I unplug the GPS, Sensors and servos.
Software loaded:
ArduPilot_Easyglider_V246
Tested so far with success:
- GPS navigation on the ground. Flash a LED when you hit a waypoint. WORKS OK!
- Stabilization. Rudder and elevator responds to XY-sensor. WORKS OK! (only tested inside and the result are very unpredictable)
Regards
Tommy
Replies to This Discussion
-
AdminPermalink Reply by John C. on -
I'd open up a serial terminal, and post the serial output while you're switching between modes. You'll be able to tell a lot more.
-
3D RoboticsPermalink Reply by Chris Anderson on -
We haven't seen that problem with others. I'd suspect a low voltage situation or weak solder joint. Can you try to replicate the problem with the shield off, to eliminate those connections?
-
Permalink Reply by Nippy on -
Thanks for the replies!
I'v measured the voltage to 5.1V. Changed the ESC but the problem remains.
I do not have the shield.
How do I monitor ther serial port? I looked in the Arduino Serial port, but only gets garbage.
Is there any useful debugging switch I can activate in the code?
Here are some pictures of the board.
Maybe I should resolder some connections...
- Attachments:
-
-
top.jpg, 474 KB -
bottom.jpg, 213 KB
-
-
3D RoboticsPermalink Reply by Chris Anderson on -
You need to set the Arduino serial monitor to the same baud rate as your GPS. If you set the GPS to 1 (SIRF) in the config file, that's 57600 baud.
-
3D RoboticsPermalink Reply by Chris Anderson on -
BTW, are you using the shield?
-
DeveloperPermalink Reply by Mark Colwell on -
Re-solder CH2 signal out pin as it did not flow well... Also re-heat all 6 inputs pins, they look messy but are probably working fine.. all others look good. Are you only using one channel for now??
-
DeveloperPermalink Reply by jasonshort on -
Check your radio is sending out the correct PWM for the control switch. If it fluctuates, it could be reboot the board. Most radios have end point control. On my Futaba 7C I had to adjust this to get my channel 5 switch to output the correct PWM range. Bad GPS values from the config tool could also cause a hang and reboot. Reload your mission.
Also you really need to connect Ch2 input or your setup won't work in a plane.
Jason
-
Permalink Reply by Nippy on
-
Problem solved!
Firts I resoldered the joints - I think they improved, but the problem was still there.
I should have mentioned that I'm short on pigtails, so I had only CTRL and IN1 connected.
But now I stole a pigtail and connected IN2 aswell. The moment i touched signal IN2 with the wire from the RX channel#2 the yellow STAT started to blink! It had "crashed" but now started to live!
So, I soldered IN2 and now it's stable as a clock!!!
I can recreate the situation I had by just disconnecting the IN2 from the receiver.
Strange, but I'm happy! :-)
Thanks!
/Tommy
-
DeveloperPermalink Reply by Mark Colwell on -
Now just avoid the ground....
-
AdminPermalink Reply by Thomas J Coyle III on -
Nippy,
From the distant past, Jordi indicated that the Ardupilot software, after initialization, looks for receiver servo command signals on the three inputs on the Ardupilot board. I believe that the software will loop looking for the input servo signals from the receiver and will not continue through the rest of the program.
I have had this happen with only the CNTL input connected. The board will appear to be hung, the mode led will not flash. Then just moving the board around will cause some random noise on the servo input pins that fools the program into believeing it is seeing real servo signals and it will continue through the rest of the program.
Just a thought.
Regards,
TCIII
Social Networking
Top Content
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
-
Japan ArduCopter Group
58 members
-
ArduCopter User Group
1356 members
-
Nitro-powered Arduplane …
15 members
-
ArduPlane User Group
721 members
-
Andropilot Users Group
203 members
Advertisement
© 2013 Created by Chris Anderson.
Powered by
