-
Notifications
You must be signed in to change notification settings - Fork 17
Still not sure how to fix the "Descriptor length mismatch" A1M8-R6 firmware issue #25
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
Comments
What firmware revision do you have? It was updated to work with version 1.29 in #17. It's possible your unit has something newer that added new features or broke compatibility. |
Hi Melissa, I bought it on digikey, and it's branded as a DF Robot product. The only info I can find in the specification is: Not sure how to verify firmware revision unfortunately. |
The one I have is from Adafruit and is stuck on firmware 1.27. I think I was able to check that using the SLAMTEC software. You might want to see if that software works with yours. Without more information, this can be difficult to troubleshoot. Some other possibilities I can think of might be it needing to be updated for the Python version (though unlikely) or your environment setup. |
Ok thanks, I'll give the SLAMTEC software a go, next time I try. Will probably leave it for a day or two. |
Well, indeed it is 1.29. The Firmware program refuses to upgrade/downgrade to 1.27. From what I can see on various forums, it might be an issue of USB not providing enough power. But I've tried with a USB3 port, so it's probably not that. Hmm. Dunno. Anyway I'll close the issue. Probably a power issue.
|
Followup: I connected the motor to a dedicated 5V instead of the USB. Still, same error message. Damn. $99 spinning plastic. |
Followup: I ran frame_grabber.exe and it works! Ha. Ok, now to try work out how to compile VS 2010 code missing various libraries, in 2022. |
A followup that might help someone work it out eventually... So I got the RPLidar SDK compiling (with this fix). And came back to this code, and tried again, and managed to get past a null byte, which seems to be the error, for v1.29
So now I'm getting a stream of data.
When running the simple test. So, anyhow, that seems to be the v1.29 issue. Some null bytes. FYI. |
Thanks for finding this. Would you like to submit a PR with the fix? I could at least test and verify it runs on the older 1.27 firmware (which unfortunately doesn't appear to be upgradeable). |
I also get a crash later, randomly, so I'll need to look at that too. Seems fine to just catch and drop the exception though. But if/when I get the visualisation working over a network, I'll submit a PR with a proper fix. ( The quick fix above is pretty hacky, and might swallow legitimate exceptions. )
|
I might see if getting a more recent RPLIDAR would have the latest firmware now |
I had the same error trying to run the readme example and I solved this by doing so: When you create the object RPLidar like below, the default baudrate is 115200: You probably need to set baudrate to 256000 like this: |
I see other users are asking this still, and their questions are just being closed.
But it would be nice to use the RPLidar (A1M8-R6)
The results of running the example (all required python libs installed)
Any ideas? Thanks
The text was updated successfully, but these errors were encountered: