as a lawyer you (should) know best about such things and the law. Actually Jeti knows about this problem, which could serieously harm persons/users, because the rely on the function that a motor-off-switch ist definitely OFF. And I guess, it's no big thing for Jeti to implement. Many, many users are using electric engines and they alls are affected by this problem. So the target group is big and not just a niche, wehere nobody cares for
But I also absolutely together with you, that these transmitters, their possibilities and the support of Jeti is outstanding!
P.S.: Lieber schnell in der Luft als langsam am Boden
the TX is doing that what the user does. If a user reversed his elevator "wrong direction" and than crashes after taking OFF; is this a problem of TX producer ? No, it is user problem. Lot of users even do not use a "safty switch" ......
And actually you can see that with a LUA APP you can get all this what you want to have.
As you see this "idea/videos" to improve perhaps the "safty switch" was in 15 Minutes yesterday on the table of the software person. If there will be a modification or not I can not say. That is Jeti decision; we will see.....
But even now it is not a "safty issue" and has nothing to do with "lawyer job"....
And at the end:
could you explain me why for more then 3-4 years there was nothing to hear about this ? Jeti never got any infos/wishes etc. Also in all other forums around the world nothing to hear .....
..... and if you are already optimizing, then please make sure that even if the motor safety switch is switched off, the motor will not start if the servo direction is inadvertently reversed.
It can't happen with Graupner.
Letzte Änderung: 14 Dez 2017 12:23 von PW. Begründung: gelöscht/Thema
as this is the "Comments for Jeti" category in the forum, I would like to suggest to continue the general discussion not here but in the thread
jeti is aware of the problem and has responded on the spot by mail to PW and me.
they are looking for the best solution and evaluate wether a fix for the next FW release will be impemented.
da dies hier die kategorie "Comments for Jeti" ist, würde ich vorschlagen, dass die generelle diskussion nicht hier sondern im thread
weiter geführt wird.
jeti ist informiert und hat unmittelbar PW und mir per mail geantwortet,
man schaut jetzt nach der besten lösung und evaluiert was der beste weg ist um dann zu entscheiden, ob eine änderung im nächsten FW release implementiert wird.