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

v1.8-beta23 : NMX motors move 4x entered value #21

Open
jbrookfi opened this issue Mar 18, 2018 · 1 comment
Open

v1.8-beta23 : NMX motors move 4x entered value #21

jbrookfi opened this issue Mar 18, 2018 · 1 comment

Comments

@jbrookfi
Copy link

jbrookfi commented Mar 18, 2018

Note> This was not observed with v1.7.7. I have not installed any of the intervening builds.

When using the webapp to set keyframes. it is possible to set a value, in degrees, for the movement of the motor. However the actual movement seems to be 4x the entered value e.g. if I specify 5deg for the PAN axis and press the left (resp. right) arrow, the actual motion is 20 deg.
I did select NMX as the type in the pull-down.
When running a timelpase, the motor seems to be moving correctly. as it reaches the keyframe in the prescribed time. So this problem seems to be limited to the keyframe setup dialog. BT is being used for the communications between the NMX and the View.

Jeremy Brookfield

@elijahparker
Copy link
Member

This sounds like it might be an issue with the microstepping setting for that motor on the NMX. The VIEW doesn't actually set this, so you'll want to check it in the Dynamic Perception app. I need to check to see what the default should be -- I'm not sure at the moment. Also, just so you're aware, if you're using the NMX with bluetooth, I highly recommend updating the VIEW to the latest firmware as I've many bugfixes and improvements to the NMX driver and motion system.

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

2 participants