Hey guys,

 

I am just wondering if it matters when the gps is unplugged when putting the ardupilot into fly-by-wire mode? Should i power the ardupilot up with gps plugged in and then disconnect or should I power it on with no gps attached?

 

If it makes any difference here are my parts:

Easystar Glider

Ardupilot Arduino ATMega328 Board (red board)

Shield V2 kit (blue board)

EM-406A USGlobalSat GPS

Spektrum Dx6i transmitter, Spektrum AR6110e reciever

Attopilot XYZ sensors (from DIYdrones)

Electrifly C-55 Mini ESC

 

Also, what LEDs should be on when the Ardupilot is in fly-by-wire mode?

 

I am at the point with my UAV project where it is almost time for a test flight, and I want to ensure that I am doing things correctly! I intend to take the advice of the Ardupilot manual and hook up the throttle directly for the first test flight of autopilot. I assume thins is the best first step in the testing process? Any suggestions on the safest sequence of events to test my Ardupilot?

 

Thanks for any help in advance!

 

Jeff.

Tags: ardupilot, by, fly, wire

Views: 25

Reply to This

Replies to This Discussion

Permissions don't permit access to throttle test ans mode switch test. Others ok
With the version 2.5, I am wondering how we "tell" Ardupilot where to go and the plane will steer itself towards the destination as if it were flying via Autopilot.

Can anyone elaborate on what fly-by-wire mode does?
In fly by wire in 2.5 you just fly via RC, but the plane translates that into computer-controlled paths. Just like fly-by-wire in a real plane. It goes where you point it, but much more smoothly than if you were flying totally manually.

Stabalization mode, on the other hand, just tries to keep the plane level. Awesome for landing!
Thanks for the explanation Chris,

That makes sense, however right now I have no control over rudder or elevator when in fly-by-wire. I disconnect the GPS, power on the board, and switch to Autopilot1 or Autopilot2, but have no control with the transmitter over any control surface unless I am in manual mode. Is there an adjustment in the h file (gain?) that I may need to consider?

Would you recommend using 2.5 regardless of if I want fly-by-wire mode? I am only interested in it as a first step in testing... full waypoint autopilot is the goal! Are there any drawbacks of using 2.5?
Ok, how much Ardupilot is necessary for fly-by-wire mode? Can that can be done with JUST the ArduPilot and one IR sensor? If its just stabilization enhanced flight, that would be great for my speed addicted buddies that fly over 100mph as well.
If all you want is stabilization, I'd recommend an FMA Co-pilot (original, not the overbuilt II)
Well, the way I'm understanding it, the FMA just levels out the plane when you let off the sticks and the ArduPilot does the same thing in stabilizatione mode. Now the fly-by-wire is a whole different animal, correct? This is computer assisted control that removes all the human twitchiness. I haven't fully wrapped my brain around it, but it sounds like the fly by wire mode would be fantastic for low pass speed runs. you have tio get really low to do a radar clock or doppler recording, and at 120mph, I don't like holding the radr gun when the plane seems barely under control and flying right toward me.
Seems like it could potentially be a whole new niche for the ArduPilot.
That's correct.
Well we decided to give the plane a try.. we took it out and unfortunately had some trouble with our transmitter. The antenna had come apart from the board inside the transmitter and thus we had no range, so the the plane went up and then came down after about 5 seconds once range was lost.

We fixed the transmitter, but the bigger problem is that the ardupilot board seems to be damaged. Only the red power LED lights come on no matter what we do (bind plug in, out, gps in, out... the plane did go down into some snow (we are in canada) and after inspection, I noticed some strange corrosion on the sheild board solders.

Could we have fried the board? Is there a way to reset everything?
I have no communication with Ground Station or with Config Tool, which worked 100% before. I also now get an error message when trying to re-load the easy_star_24 code from arduino.
That does indeed sound fried. Maybe snow caused a short? That's why we make the boards so cheap--it's easy to get another one and the expensive stuff (GPS, thermopiles) are pretty tough.
To our relief everything started to work again! I cleaned the corrosion off the sheild solders and let everything just sit for a while. One thing that has been frustrating throughout this build is the lack of consistency, but nonetheless I am glad things seem to be working.

Time to head out for another test flight, this time with a transmitter that works.

Another question: In the Config tool where you set altitude, what exactly does Alt (to hold) indicate? With over terrain checked, the altitudes show up as negative which is def not correct, perhaps the data website does not include info on Canadian territory? We have "set manually checked", so do those altitudes tell it to stay that distance above the home alt hold? And what does Alt (ref) refer to?.. I am unable to edit it.

RSS

Contests

Season Two of the Trust Time Trial (T3) Contest has now begun. The third round was a reliablilty/aerial photography round for both planes and copters, which is now closed. Stay tuned for the next round, beginning soon.

A list of all T3 contests is here

 

© 2012   Created by Chris Anderson.

Badges  |  Report an Issue  |  Terms of Service