Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Testing Engine Driver on ESU MC II #187

Open
SonnysHansen opened this issue Mar 4, 2018 · 4 comments
Open

Testing Engine Driver on ESU MC II #187

SonnysHansen opened this issue Mar 4, 2018 · 4 comments
Assignees

Comments

@SonnysHansen
Copy link

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

@mattharris mattharris self-assigned this Mar 4, 2018
@mattharris
Copy link
Member

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

@mstevetodd
Copy link
Contributor

@mattharris or @SonnysHansen is this still a problem?

@SonnysHansen
Copy link
Author

SonnysHansen commented May 31, 2018 via email

@mattharris
Copy link
Member

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants