-
Notifications
You must be signed in to change notification settings - Fork 46
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
AtomMain 2.8.1 has broken Encoder Values #17
Comments
Please try Atom2.8 |
That is more reliable but also sometimes gives me -1 for encoder values. I currently workaround it by trying to read the value up to 3 times which is more robust. However, this interferes with timing. |
The reason for |
I'm technically using the code you're using for teaching in the MainControl application. This code has the same issue with Atom 2.8. It is not visible because some of the next measurements will have correct values and -1 are ignored when commanding. How can I make sure that I do not send too fast? BTW: I'm programming on the Basic controller directly adapting the MainControl application |
I am sorry, maybe I didn't find out. where you get the
here? |
Yes, this function seems to return -1. |
OK. The reason is that valid data cannot be read. I think you just need to skip API will only throw out the possible existence of wrong data, and the user will deal with this situation.😊 |
Possibly relates elephantrobotics/pymycobot#17 |
In 2.8.1 Atom Main, the encoder values are not updating or just wrong.
The following code will not show correct encoder values:
It can also be reproduced by flashing the latest MainControl app into Basic and trying to record and replay a motion. The replaying will not work and move to random poses instead of the expected track.
The bug seems to have been introduced with 2.8.1. Version 2.8 is working properly.
The text was updated successfully, but these errors were encountered: