TCIII comments

Results 123 comments of


                                            TCIII

Empirical testing suggests that the lidar.py part range data output may not be accurate

I then proceeded to go through the same exercise with a RPLidar A1M8-R6 (firmware 1.29). As before, when I looked at the data from the scan with the target positioned...

Empirical testing suggests that the lidar.py part range data output may not be accurate

The above empirical testing definitely validates the Adafruit RPLidar library functionality and the fact that both the A1M8 and the A2M8 Slamtec RPLidars function as intended by the Manufacturer. It...

Empirical testing suggests that the lidar.py part range data output may not be accurate

@Ezward, Because of the ambiguity of where the 0/360 degree reference is on the Slamtec RPLidars, I believe it is in our best interests to reach a consensus on where...

Empirical testing suggests that the lidar.py part range data output may not be accurate

@Ezward, "So that is 266/0.136532068 = 1948 measurements per second. That surprises me because the marketing material says the device can do 8000 measurements per second." I suspect that the...

Empirical testing suggests that the lidar.py part range data output may not be accurate

@Ezward, I don't agree that the "forward angle is at 180 degrees" for the following reasons: Based on the following angle/range data, captured by your lidar_test.py program, when using a...

Empirical testing suggests that the lidar.py part range data output may not be accurate

@Ezward, That is a good summation. I agree with the Lidar physical mounting references. I look at it this way: The A1M8 angle/range data recorded the target at 0 degrees...

Empirical testing suggests that the lidar.py part range data output may not be accurate

@Ezward, Excellent work to say the least. I tried your stream_lidary.py program and it worked flawlessly and returned results similar to yours.

Updating DC to 4.2.1 will break the Robo HAT MM1 configuration

@DocGarbanzo, Thanks for the response, much appreciated.

Updating DC to 4.2.1 will break the Robo HAT MM1 configuration

@DocGarbanzo, I had the same issue with all three of my Rpis too (two 3B+ and one 4B 4GB).

Fatal error in actuator.py when run on NVIDIA Nano

Good observation Chris, however the DC software had to have known the processor configuration or it wouldn't have issued the "RuntimeError: This module can only be run on a Raspberry...