I was thinking about an idea of a redundant UAV with 2 x APMs, 2 x RXs, Dual Servos/surfaces, 2 x ESCs and 2 x motors. The plane should be designed so that it could fly with only one motor if needed.

The idea of functionality:

  • If something in APM(A) network fails or works not well the plane would automatically switch to APM(B) network.
  • If one of the servos fails there would always be another servo and another surface to control the steering.
  • If one ESC or engine fails there would still be another to go.
  • If one RX fails the system could use the (B) network.

How the system detects a failure?

  • (If both APMs had the same planned route and the working APM(A) detects that the plane has drifted too far away from desired flight path it would automatically switch to standby mode and let APM(B) network do the job?
  • If APM(A) network RX looses signal the failsafe would automatically switch the board to standby and let the other network take the control.
  • The idea would be that the other network would always be in active mode and the other one would be in standby mode.

I hope you could give some additional ideas to this draft philosophy of a Dual APM plane....

Views: 1674


Developer
Comment by John Arne Birkeland on June 22, 2012 at 12:25am

A agree with all your points Matthew. My point is that in the context of this thread, I don't see how a second autopilot would have realistically helped in any of those situations.

Comment by Lorentz on June 22, 2012 at 2:14am

@Matthew

"The greatest risks are electrical connector faults, radio failure and mostly my own flying capabilities"
I totally agree

At the risk of going off topic:

- although unpleasant, accidents and near misses are the best source of knowledge for increasing safety and reliability
- proper design and dimensioning of linkages, spars, required servo forces, strength is bare minimum except for foamies (perhaps)
- reliability is paramount, reliable components are believed to be so if inspected, maintained and replaced before failure (think MTBF)
- AFAIK connectors are one of the biggest source of failures

Possible countermeasures :

#1 inspection ? manitenance ?
#2 proper dimensioning ?
#3 proper dimensioning ?
#4 diverse radio link ? redundancy wouldn't have helped: same radios, same SW error
    diverse backup system (autopilot) ? provided autopilot SW is reliable enough
#5 training ?

Still, I'd put the effort to the reduce the riskiest hazards, considering risk as probability of hazard X severity of damage.

Comment by Veikko Vierola on June 22, 2012 at 3:55am

I was just thinking that total dual system would have a backup for almost every problem. If the plane is not staying on its flight path the 2nd network could still be able to do that. For example if APM(A) network has a lost elevator connector output, the APM(B) network still connects to the servos normally. Of course in this case you'll have a bit more wires going to the servos. But maybe I could reduce the amount of wires by using direct cppm connection to APM from RX?

Comment by Lorentz on June 22, 2012 at 5:05am

@Veikko

 

I was just thinking that total dual system would have a backup for almost every problem.

That's true, except for common cause / common mode failures and systematic failures.

If the plane is not staying on its flight path the 2nd network could still be able to do that.

Yes, we only need to tell the failed / wrong network from the good one and a mean to switch the controls from the bad network to the good one.

For example if APM(A) network has a lost elevator connector output, the APM(B) network still connects to the servos normally.

Good point, even better with redundant servos that default to central position when PWM signal is missing.

Still not sure if the risk of loose connectors is worth a second APM instead of replacing connectors with soldering.

Of course in this case you'll have a bit more wires going to the servos.

But maybe I could reduce the amount of wires by using direct cppm connection to APM from RX ?

I saw somewhere here on diydrones a post regarding servos with daisy-chain serial connection that would reduce wires and, more important, connectors. Also direct PPM connection from RX to APM may help reducing wires / connectors.

Comment by Veikko Vierola on June 22, 2012 at 6:08am

@Lorentz

Do you mean Futaba S-Bus system?

Comment by Lorentz on June 22, 2012 at 8:11am

yes, that one !

Comment by Veikko Vierola on June 22, 2012 at 12:21pm

Isn't the Futaba S-Bus system just a normal bus that feeds cppm data and the servos are capable of decoding the cppm individually?

Comment by Zachary Eldridge on June 22, 2012 at 12:32pm

Think about this servo on the right gives out in flight your system is going to be flaw. I would be put dual servos with that setup. Over two APMS are still over killed. Two servos no so much since they are running on the same signal and one servo fails the other will handle the slack. APM is pretty smart device if that goes down it goes to RTL and failsafe mode automatically.

Comment by james sowell on June 22, 2012 at 6:32pm
Comment by Lorentz on June 23, 2012 at 12:51am

@ Veikko

I admit that I don't know the details of S-Bus protocol, but it could be as simple as forwarding the CPPM signal to all servos and having them decoding.

Being bare CPPM signal sensitive to disturbance, I suspect they implemented a serial protocol with error detecting mechanisms.

Another nice solution could be I2C protocol as implemented in OpenServo

Comment

You need to be a member of DIY Drones to add comments!

Join DIY Drones

Social Networking

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

Advertisement

© 2013   Created by Chris Anderson.   Powered by

Badges  |  Report an Issue  |  Terms of Service