-
Notifications
You must be signed in to change notification settings - Fork 41
Scanner Connection Error Code: 1 #28
Comments
As you can certainly hear when the lidar starts up, the speed of the MRS1104 is set to the target speed. Possibly your version of the MRS1104 takes a very long time to reach the set speed at the first. Therefore, this does not seem to be a fundamental problem of the lidar driver. It may make sense to contact the SICK service department in this regard. In my experience, the MRS1104 should actually start up after 45 seconds at the latest. You can also patch the max. default waiting time to another value (e.g. 120 secs.) by replacing the following entry: |
Sorry @michael1309, I did not explain before that the first thing I tried to change it was this parameter I used up to 3 minutes and it didn't work. Thats why I came across the solution in the code that I put at the end of my comment. I contacted the SICK department in France already and he is aware of all the procedures we have done to get the MRS1000 connected with ROS 2. I am still waitig for a better solution. |
Hello @MonteiroMarcos , we have just tried to reproduce your problem with a MRS1104. sick_scan2/config/sick_mrs_1xxx.yaml Lines 8 to 9 in 6ea289a
In future versions of this software we will change this to the ros coordinate system. This is not relevant for your start problem. We had reproducible problems when we started the driver too fast after power on of the scanner. 0 sec-> power on 46 sec --> ros driver is started |
Hello @michael1309, |
Thanks for your friendly feedback. |
How to do fix this. Thanks you |
@Loctangba We recommend to use https://github.com/SICKAG/sick_scan_xd for all lidars supported (see https://github.com/SICKAG/sick_scan_xd#supported-hardware). Please don't hesitate to report issues there in case of problems. |
The ROS 2 Driver connection
I am using the MRS1000 on ROS2, the sick_scan2 connection is not working when I launch sick_mrs_1xxx.launch.py for the first time. Relaunching it I am able to connect, I need to relauch twice at least to establish a connection.
Sensor Model: MRS1000
Version: 2.2.1
Serial Number: 21050060
I worked on a workaround solution to loop 5 times to start a communication, but it is not the best solution:
I think there is a problem around the LMCstartmeas procedure.
The text was updated successfully, but these errors were encountered: