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

A3 crash with scan_mode Sensitivity #79

Open
winf opened this issue Nov 1, 2018 · 7 comments
Open

A3 crash with scan_mode Sensitivity #79

winf opened this issue Nov 1, 2018 · 7 comments

Comments

@winf
Copy link

winf commented Nov 1, 2018

crash
However ,scan_mode with stability is working.

@winf
Copy link
Author

winf commented Nov 1, 2018

disable angle_compensate could resolve this

@winf
Copy link
Author

winf commented Nov 1, 2018

maybe “ attribute((packed)) ” in rplidar_cmd.h #line204 cause this behave.
https://stackoverflow.com/questions/8568432/is-gccs-attribute-packed-pragma-pack-unsafe

@ramonvp
Copy link

ramonvp commented Feb 11, 2019

Hi! Any news on this? I am also experiencing the same crash. It does not happen if you modify the launch file and use "Standard" as scan_mode instead of "Sensitivity"

@niralber
Copy link

same problem. disable angle_compensate solves the problem. but I don't know why and assume the accuracy is affected by this...

@cjmahieu
Copy link

cjmahieu commented Feb 27, 2019

I found that both the Standard and Express mode work. However I would like the Sensitivity mode to work as well..

Disabling angle compensate prevents the crash from happening but makes the scan data unusable as shown below:

image

(With express / standard option it looks as follows:)

image

EDIT:

What i reported above was using the package installed via aptitute (i.e. ros-kinetic-rplidar-ros).
Using the version from this git repositoy I was able to run at 'Sensitivity' level if I turned of angle compensation.

Proof below:
image

@ameykasar
Copy link

Had the same problem. Editing the scan mode in launch file (as mentioned above) helped.
The problem went away completely when I switched to another USB cable. Digging more I found out the cable was not capable of providing enough stable power for the sensor.
Observe the laser does not light up when you get the error as the power is not sufficient.

TLDR: CHANGE USB CABLE/ CHECK POWER DELIVERED TO THE SENSOR

@deb0ch
Copy link

deb0ch commented Mar 25, 2019

Looks a lot like Slamtec/rplidar_ros#1 and fixed by Slamtec/rplidar_ros#10 (although I'm not comfortable with the arbitrary number chosen to extend the buffer).

I suspect this repo is deprecated now that the Slamtec one is there so this is FYI

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

6 participants