Having issues on anything other than MANUAL
having issues now using code 2.5.04. Therefore, I thought that I possibly had too much going on at once to test properly so I took out all but basic things for the Ardupilot. So I tried to fly my e* again and only had the Ardupilot, V2 shield, XYZ sensors, em406, XBee 900. When in manual everything is ok and has no issues. Once I turn on AUTO, FLY_BY_WIRE or STABLIZE the servos start glitching. By glitching I mean everything just goes haywire turning left right up down basically out of control. So I have now pulled the stuff out of the plane to try to do more testing with the equipment. The best I can think of is there maybe is some kind of RF interference going on somewhere.
On the board I have the black wires for the servo cables facing the outside on both connections to the board and have triple checked all other things I can in the wiki and still every time the servos are glitching. I also just tried briefly with the 2.6 code and still having the problem. My ESC did not come with a torrid on there could this be what is adding the issues? Also the other thing I have noticed is that once the ardu board is on anything other than manual the servos do not seem to have as much throw in them. I have tried to do the airframe test as I have seen that it has you test the radio and
servos for limits but I never have it ask me to move my sticks it just boots quickly and starts through the test. The last thing I notice is that occasionally after the ardu has been running for little bit the program I guess you could say hiccups. The data stream pauses come in even if using xbee’s or having the ftdi directly plugged in. It is not consistent and happens in all modes.
http://diydrones.com/forum/topics/looking-for-input-on-my-layout
This link will show you the layout I used on my plane, it was a post I did before final assembly. If there are other pictures needed or you need to see any files please let me know and I will happily post them. Sorry for the long post just wanted to give as much info as I can and thanks for your help and time.
Replies to This Discussion
-
Permalink Reply by wilsonj on -
Hi Chris,
I'd like to confirm that some Futaba radios put out 2.8v on the signal line. I believe this is probably the cause of both Jeremy and my problems.
The optocoupler in amp mode should solve this.
-
Permalink Reply by eobin on -
Hi,
My System Specs:
- Hardware: Ardu Pilot Mega
- IMU/Stabiliser: Oil Pan Shield
- APM : 1.064 version
- Airframe: Piper Cub , Electric R/C Aircraft, (Flies real smooth)
- Remote: Airtronics SD 10 G
- Mode Switch: Ratchet Knob Control for Mode Shifts
I have the same problem. When I connect it to my Netbook, It works fine in all modes with my Airtronics SD10G remote. But it does not work when I take off my USB connection to my Netbook(After "Disconnecting" from the APM Software). It does not even get a GPS lock with out my USB connection. I think it could be the following.
- Power Supply: I use a 4 X AA battery pack to power my Receiver and that is the source to the Ardupilot Mega Unit
- RF interference: Not very likely(But the glitches I have are enough to take my Aircraft off)
- Code Bug: I dont think so, but any info are welcome.
All/Any Suggestions welcome
:) Cheers,
George
- ‹ Previous
- 1
- …
- 3
- 4
- 5
- Next ›
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
-
Moderators
24 members
-
ArduRover User Group
185 members
-
Documentation Editors
51 members
-
ArduPlane User Group
686 members
-
ArduCopter Italian Group
87 members
Advertisement
© 2013 Created by Chris Anderson.
Powered by
