-
Notifications
You must be signed in to change notification settings - Fork 4
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
5090 partly compatible #5
Comments
Could you send me the output of the command
Thanks! |
Hola podrias agregar las fuciones de fregado y progrmas para las congas 5000....por favor....espero que no sea mucha molestia.....cualquier cosa me avisa |
This works quite well but the update including the charging base includes a bogus robot position. Maybe the schema doesn't match completely for the 5090. It can be seen in above screenshot where Robot x is way below map precision or on the map where the robot jumps to map origin from time to time. This can be fixed by ignoring the robot coordinates in handle_map_update if abs(schema.robotPoseInfo.poseX) + abs(schema.robotPoseInfo.poseY) + abs(schema.robotPoseInfo.posePhi)) is below, say, 6e-39. I can set up a pull request if this is the way to handle this but I'd prefer to decode all data correctly. |
it returns <Status: error>
but it seems to show most other information correctly, and also the "locate" action works.
happy to help troubleshooting.
The text was updated successfully, but these errors were encountered: