Happy New Year !!! ... may it be healthy and prosperous.
A thread of a user brought to light what I consider a real bug in the Software.
Using the Motor Cut-Off security feature, by assigning a switch and a value (e.g. -110%) should ALWAYS without any exception pull down the thottle signal to the assigned value.
When using a sequencer that raises the throttle signal to any other value than it should simply not work/react as the cut-off sets the limit here in process chain.
But it does !!!
The sequencer seems to override the throttle cut-off, and this to me is in final a security issue.
It shall be published as soon as possible and of cause be fixed.
As a long term Jeti user I expect the throttle-cut-off to be the MASTER and override any other throttle value, no means what input/function/switch ... OFF is OFF!
Too many dicks on the dance floor.
Too many dicks!
Folgende Benutzer bedankten sich: IG-Modellbau, Hermann