Kevin Finisterre, DIYDroneSafety and Drone Savant persona

forum PM: "Just know that the 'imaginary' group you represent isn't so imaginary at all. But I guess you already know that" - silent DIYDrones user

This topic was setup in order to move degenerative conversation points away from the "Hex decided to leave and never come back" thread to a more appropriate location.

The original post wording stated that it "should be used as a sounding board to discredit the abrasive  comments made by myself and others that operate the DIYDroneSafety website, twitter feed, and the Drone Savant forum persona. Either take it off list or put it here... It appears as if we need a special topic to discuss WHY some people feel the need to be abrasive around here in order to get critical safety issues fixed. Some claim slander, damage, abusive behavior, libel etc., while others claim simply claim awareness and safety from half truths and lies by omission..."

^--- This was simply a conversation starter which had wonderful results.  Discussing the "need to be abrasive" really was not the point. This comment nails the actual point

I think there are specific and real issues, which Kevin is raising.  Most of his complaints about the code are at least valid, even if not easily solved.  His complaints about the documentation are also valid, and are easily solved.

Traditionally the following topics have produced some contention amongst the ranks of developers, moderators and end users. As such user understanding, vs. documentation, vs. code has been confusing at best and at times unsafe: 

PPM Encoder

Watchdog functionality for code lockup situations

Powering the APM with cheap ESC's via input rail (brownout problems)

These topics are *NOW* being actively investigated in a variety of forms and are producing valuable information. 

Safety Watchdog -

Watch dog added to shutdown motors if main loop feezes for 2 seconds (Randy) - 

Brownouts -

We're going to be shipping a stand-alone power supply (and voltage/current sensor) that will ensure that brownouts never happen. Hopefully in a few weeks. 

PPM Encoder logic explained -

With the discovery that the Turnigy 9x radios using original receivers and firmware, would act in a non-standard way and completely drop the throttle signal during fail-safe (same effect as a broken wire). The detection of single channel loss became a real problem, and a patch was made to detect single channel loss (throttle only) at the expense of some jitter and stick resolution.

New Original Paparazzi & APM PPM (servo2ppm?) logic flaw brought to light

Olivier found and documented some very real and very serious problems with the original Paparazzi PPM Encoder used by APM 1.x. What Olivier found and proved by extensive testing, was that that PWM channel sequences from certain R/C receivers would confuse the Paparazzi PPM Encoder. Resulting in the throttle channel (among others) locking up.

Hats off to developers like R_Lefebvre and people Monroe for stepping up (even if begrudgingly in Monroe's case) to help get to the bottom of these potentially serious safety issues -

When you are "The largest amateur Unmanned Aerial Vehicle (UAV) community", it doesn't matter what everyone else is doing. "Well they have flyways too" aren't the words of someone leading the head of the pack. Well can do better and deserve it. 

Stay Vigilant. 

Views: 5779

Replies are closed for this discussion.

Replies to This Discussion


I have asked the Moderators to decide what to do about this issue. I am sure that a decision will be forthcoming.



Hi Monroe,

I did get Chris to close-out the lost hex thread as it was definitely getting pissy. As a moderator I can close down a thread that is getting out of control. However I always ask for comments on the Moderator's Forum before doing so.

On another topic, I feel that you should continue as a moderator as you are a voice of sanity in what seems to be an occasional insane wilderness.



There are some moderators that think that freedom of speech means you can post what ever you like, can I remind all who post there under the terms of service freedom of speech does not extend to posting "in a manner that is libelous or defamatory, or in a way that is otherwise threatening, abusive, violent, harassing, malicious or harmful to any person or entity, or invasive of another's privacy;"

I stand to be corrected but I think folks posting on here own their own words and are entitled to them and must be prepared to justify them.

Things do need to be removed when people are plain offensive though but I know often before some people are warned or stuff is removed there are many many many discussions. 

If I have to chip in about the problems slightly tongue in cheek, two of them can be solved by not using cheap gear. They should be thought about though. I am not a developer, I am a re-kitter of airframes.

Well if the world was a fair place we would all consider ourselves down the pub in front of a roaring fire with a decent ale in hand. Obviously in America you are at a distinct disadvantage right there. More so when I say a wholesome slice of bread and hunk of real cheese are aiding gentle discussion. 

The point I am trying to make and we all know is that people on forums are far far far ruder than they would be to anybody in real life. Often saying something to somebody that you would never dare to another face to face even if you had had a barrel of beer.

So why don't we all try and change that and make this the most polite place about. Remember please and thank you and encourage jokes in posts.

Life is too short to argue.

If there is a safety issue it should be properly documented, as I am sure it is and will be. 

I agree with Gary, if you post own the responsibility for its accuracy, relevance and legality. However, the site also has a responsibility to monitor and maintain a respectful place for community discussion. Moderators need to monitor what is possible, and respond to member concerns about the postings that don't get moderated.

There must be some statistical formula that says if one person is upset in a group of 30000 then there are probably X number of other people who are also upset but not saying anything. 

I just suggested ignoring this discussion but I am a moderator (not as active as some) so I feel I have a responsibility to be proactive when I can. 

I do not believe there is a need to discuss why people need to be "slanderous", or disrespectful in order to communicate what may be valid concerns.

There are existing forums for all of the concerns. Discuss them there and leave out personal comments, or if you are really upset feel free to not use the technology till issues are resolved.

Even better, help in solving the issues. 

Sorry for typos, I am on my Playbook and it is being difficult. 


SO, I'd like to hear from the Mods / Devs...are there specific and real issues here?  This seems to me to be a set of rants that could be easily remedied with a mention in the documentation.  Perhaps a "Best Practices" section that says, "Hey, it is pretty likely a bad idea to do X...or some users have reported Y problem, we believe this can be avoided by doing the following...or even Turnigy 9X radios are inexpensive, and ok for beginners with very small budgets, but sometimes you DO get what you pay for."

I know documentation is the LEAST sexy job in these projects but it COULD be the MOST important.

I wish this whole conversation, and the majority of the previous one in the lost hex thread would die a quick death, just like the psycho convict did in tonights Walking Dead.  Machete to the skull.  I'm cursing myself for adding to the drivel.

The great thing about this board has been the COMMUNITY.  Since it started up, there has been an ebb and flow of awesome people coming in here and adding awesome shit to the functionality of the 3DR hardware.  FOR FREE.

You cannot complain about work that people are doing FOR FREE. 

Take the code, use it, augment it.  Fix the shit you think is broken.  (Thanks again GPL!)  Test and provide constructive feedback if you want.

Or don't.  Go use some other variant that has its own set of issues.  No one is forcing anyone to be here, and repetitively ranting doesn't help fix things.  It detracts from the community and disenfranchises not only the new guys who just see people bickering and trolling, but also those that have been here forever and done everything they can to make a reliable product for us laymen to enjoy.  FOR FREE.  

You're going to crash.  You're going to lose stuff.  It's happened to every single one of us.  If you wanna play, you're gonna pay.

If we could have harnessed the thought power and keystrokes that went into all of this BS, not only would we have the best AP....we would have world peace and fed every hungry child in the world.


I agree with John C, this issue went far beyond a NO ONE IS LISTENING TO ME response. I wish as well that this whole conversation was put to rest - yes the issue is being looked at, and yes the people contributing are contributing for FREE. So we should not be ranting, flaming, and slandering towards this project. It is DIY, if you want a commercial autopilot pay for one otherwise deal with the issues that come up in the DIY market. We are all well aware of what can happen, RC itself has potential to be dangerous - I have seen many many dozens of fingers cut - even severed off due to lack of safety. Humans make mistakes! I am more worried at my flying field about the unskilled pilots that fly their then my APM 2.5 cutting my hands or flying away and hurting someone. I mean honestly, can we just enjoy this great project. Look how far it has come in the past 3 years. I remember the days of ardupilot version 1. It was 90% test and fail and 10% flying, but everyone got through it and here we are today. So all we can hope for is the continued improvement over time, doesn't matter that 3DRobotics and Udrones are selling it, it is still DIY driven. So to blame them because they went commercial and suddenly they owe us more responsibility is not logical, the boards all work. The code may need tweaking - changes etc...over time and this should just be expected in the DIY World. Let us not make the community developers and volunteers seem un-appreciated or worse ridiculed. You all are doing great work, as my father used to tell me. Take in one ear and send out the other, blah - blah - blah. What did you say ? Thanks for the hard work everyone the system is outstanding, and I can tell you from experience I have had more successes then failure through out the course of this DIY project.

Can't we just ignore Drone Savant? He's pretty much ruined his cred here. Replies just encourage. 

Scott, I think there are specific and real issues, which Kevin is raising.  Most of his complaints about the code are at least valid, even if not easily solved.  His complaints about the documentation are also valid, and are easily solved. 

I understand why he's got to where he is, his level of frustration.  But I don't completely sympathize.  Part of the problem is that a lot of his frustration stems from the fact that he thinks much of the problem is intentional, rather than just "organizational confusion".  Take for example his mention of how to power the ESC.  Craig says one thing, Chris says another.  Kevin thinks Chris is being intentionally misleading.  I think he probably just isn't aware of the issue.  I don't know how Chris does everything that he does in a day.  I can see how it would be very easy to lose track of some details.  Yet he wants to be helpful and posts something on the forum.  If the info is wrong, does it mean his intentions were bad?  I don't think so, but Kevin does.

I also believe that the developers of the project need to try and make it as safe as possible, and there have been a few areas that need improvement.

So as I say, I think most of the issues are valid, and I understand why he's upset.  He's very correct in saying that until he started jumping up and down screaming, nobody was listening.  People were told to put things in the issues list, and they did, but nobody acted on it, or at least nobody was seen to act on it.  

But as I've explained to Kevin before, this is an open source project, and wrong or right, developers work on what they want to work on.  You DO need to convince one to do what you want.  And this sort of behaviour isn't the way to get it done.  The only thing this ranting is doing is making other users aware of the problem.  But I don't see any evidence that other developers are going to want to work on the issues he is ranting about.

But Kevin used to have a much better method to do that, when he had priveledges to update the wiki.  However, he threw that all away when he broke very clear TOS rules.

The other problem that I have no sympathy for, is that he sees comments from some people, and assume that the whole community believes the same thing, just because nobody else stepped up to refute it.  I don't get that at all.  You get one guy who doesn't work for 3DR and isn't a dev, saying his friend was flying unsafely, and he acts like we all said it, and then rants and raves when somebody else (like Chris) flies the same way.  

Anyway, at the end of the day, I hate that it's come to this.  All of this does look bad on us.  And then Chris is stuck in a bad spot because if he bans somebody, or deletes these posts, a whole other group of people start complaining about censorship and coverups.  It's a no-win situation.

Ditto - yes he has....



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

© 2019   Created by Chris Anderson.   Powered by

Badges  |  Report an Issue  |  Terms of Service