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. http://diydrones.com/forum/topics/hex-decided-to-leave-and-never-come-back
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 http://www.diydrones.com/xn/detail/705844:Comment:1009087
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:
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 - http://www.diydrones.com/xn/detail/705844:Comment:1007583
Watch dog added to shutdown motors if main loop feezes for 2 seconds (Randy) -
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.
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 - http://diydrones.com/forum/topics/fly-aways-the-failsafe-and-the-9x
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.