I tried to test some different modes and frankly nothing else comes to my mind anymore other than to put a heavy 40A relay to a main power line and attach a servo to it, so I could map it to one of taranis switches so in a case of malfunction or lost orientation I would be able to kill drone in the air or on the ground and stop props _immediately_.

Any other option I tried - a combination of 'land' mode with throttle cut off, an improved failsafe on remote switch off - none of that cuts power feed to props immediately, and quite often it leads to horrible results, like if in loiter mode drone suddenly gets to a GPS free zone or glitch, and starts something erratic, or flips over and tries to destroy everything around spinning props at full power ignoring remote commands to cut throttle input to zero.

I had only 3 incidents like that and I know now what it is, but it does not make my platform any safer.

What do you do for a physical kill switch? Do you have one built? If yes, how was it done?

Please respond.

Views: 4486

Reply to This

Replies to This Discussion

AC3.3 will have two Aux Switch functions which will do what you want.  Called Emergency Stop, and Motor Interlock, both can be used to immediately command the motors to full stop, no matter what mode it is in.

Great news, I was not aware of that. I will build new Tarot 690 project on PX4 but current one - a quad - I want to keep on the APM that is running 3.2. version.

As I understand 3.3 will not ever work on APM and will not have any (limited) port for APM, ever, is it correct?

Would it be possible to retrofit this functionality into old 3.2 build to make it available for APM platform?

That's correct, no 3.3 on APM.  I suppose one could hack the feature into 3.2, but it's a fairly pervasive change that would take a bit of work.

Would you consider to do a feature stripped version of 3.3 to run on APM?
It seems a bit extreme to completely drop off platform that is still capable to serve quads quite ok?

But, i understand, if not, then not.

Other question i had, in case if you can explain - on 3.2 in super simple loiter mode if drone gets too close to you - for some reason it inverts directions of all controls. If i land, disarm, step a bit back, arm back in same super simpler loiter mode - it flies ok like nothing happened. It does not happen 100% every time but often enough to make a pattern. Is there any way to prevent that?


I installed current version of 3.3 on the AUAV board, I do not see those modes in the MP list.

What are the codes for them?

I also see CH7_opt - CH12_opt parameters - do all of them work or are they only reserved for future use?

I believe this would be a very useful thing to backport into 3.2.x for APM.

How would one go about identifying the code that's changed?

I am wondering about this too.

This is implemented in Arducopter, and will be in the px4 stack w/in days. 
Be sure your copy of Mission Planner updated to the latest, and the options should be there.

Sweet. So I should be able to see options with X8R via smart port? 

Yes, depending on which channel you want to use... 
I don't have my copter/mission planner here to look at, so this might not be exactly correct..

In mission planner, go to the config/tuning tab, and then extended tuning, and you can set it to be on channel 6 or 7 via a simple drop down menu.. 
If you want it on a higher channel, you go to the full parameters list, search for ch## (lets say channel 12, search for ch12_opt, and it will list the options.. I think it's 31, but check first.

Ok. I have a kill switch project for the landing leg to land on moving vehicle in concert with IR Lock. 

Reply to Discussion



Season Two of the Trust Time Trial (T3) Contest 
A list of all T3 contests is here. The current round, the Vertical Horizontal one, is here

© 2020   Created by Chris Anderson.   Powered by

Badges  |  Report an Issue  |  Terms of Service