EngineDriver
EngineDriver copied to clipboard
Testing Engine Driver on ESU MC II
I now have had the opportunity to try out the Engine Driver 1.17 on my ESU MC II. I have no problems when using the ESU throttle, it seams to work as intended.
The only small problem I have discovered, which is no problem at all, I think. The ESU app have the same fault, but the Engine Driver app works better.
When turning the throttle knop over the limited off 126 speed steps, and then pressing the stop button, the throttle knop will not go back to zero, but get stock on 126 speed step. Pressing the stop button once more, and then it go back to zero speed. Doing the same thing on the ESU app it will just stay on 126 speed step.
Hope you can use this information test. Regards, Sonny Hansen
Sonny,
Thanks for the clear issue statement - I've been able to verify this behaviour.
I think that it's related to the conversion routine for control knob position to speed-step in the ESU provided library that we make use of in EngineDriver.
The last few degrees of a fully clockwise knob position appear to be 'out-of-range'.
I'll take a closer look to see if there's something we can do
@mattharris or @SonnysHansen is this still a problem?
Yes! I am now using v2.19-51
Den 31-05-2018 kl. 02:30 skrev mstevetodd:
@mattharris https://github.com/mattharris or @SonnysHansen https://github.com/SonnysHansen is this still a problem?
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/JMRI/EngineDriver/issues/187#issuecomment-393362685, or mute the thread https://github.com/notifications/unsubscribe-auth/AO7fz41aR4bYnl3HPrMCRLwSXv_bwqZBks5t3zmWgaJpZM4Sbcmz.
I'll try to find some time to dig a bit further but, as previously mentioned, I think it's related to how the ESU library handles this situation.