Re: LIDAR Sensor has arrived!
 

I assume you have the correct wires connected per the datasheet and are using the correct pins on the MXP?
I added an execution counter to the lidar class' update() method to ensure the code was properly executing (and output this counter to the SmartDashboard). Could you do this as well as a form of troubleshooting?

Re: LIDAR Sensor has arrived!
 

What port in Linux are you referring to? What is the dev path you are using?

Re: LIDAR Sensor has arrived!
 

Based on discussion with NI, I'm led to believe the problem may be specific to Java and not the controller itself. NI claims their ADXL345 accelerometer works just fine with I2C when using LabView modules, but I can't get the accelerometer to work with the onboard port either when using Java.

https://decibel.ni.com/content/thread/26778

Re: LIDAR Sensor has arrived!
 

Can you try in C++ as well (either the accelerometer or the LIDAR). Java and C++ share a lot of code, and that might help pinpoint where the issue is.

Re: LIDAR Sensor has arrived!
 

Verified to have the same error.

Re: LIDAR Sensor has arrived!
 

We picked up one of these... it seems very sensitive to glossy/reflective surfaces. Much more so than the lidar system we yanked from a Neato vacuum robot. Not sure what others are seeing. We haven't dived into the sample code yet beyond running it.

Re: LIDAR Sensor has arrived!
 

We have 2 of these and played with them today with LabVIEW. We have been unable to get them to work with the native I2C port on the roborio. However, we have them working just fine on the MXP expansion I2C with identical code. We've pinned them out, swapped the lasers themselves, and still have zero luck with the native port.

The native port DOES know the sensor is connected. We received read and read/write errors stating that the device is busy. This is different that the 'resource not found' error we get when the device is not plugged into to power or not plugged into the I2C.

On the MxP I2C port we are reading then writing in alternating 20 ms loops. We lowered the timing of these loops incrementally until we started getting errors. At 10 ms polling we receive all zeros, at 15 ms we receive data, so 20 ms is where we are (50 hz). We average 5 loops in a moving average filter and the data looks very good.

I know we can improve this by doing the write then checking for the ready bit, but this worked just as well and gave us a resolution we're happy with. Plus after 6 hours of banging our head against the native port we were already pretty frustrated.

We have noticed that when the sensor was aiming at the ceiling and our flourescent lights we got highly inaccurate results.

Re: LIDAR Sensor has arrived!
 

How would one program the LIDAR Sensor for use via DIO in Java?

Man I wanted one of these and I don't even have a reason...
Any cool uses for them I have a couple ideas but none of them are viable this year cause auto too short...

Re: LIDAR Sensor has arrived!
 

I don't know that you can. It's designed to work via PWM output or I2C. The I2C implementation should be pretty similar to the arduino example on their website. The PWM setup will likely just be reading analog input values but don't quote me on that.

Re: LIDAR Sensor has arrived!
 

Two possible methods:

1. Use a low pass filter and read through analog (less programming but requires a resistor and capacitor connected to the output, or
2. Directly measure the pwm pulse and convert the timing to distance (more programming, but the sensor just drops in and works)

I plan on eventually writing up a pwm based class due to the problems teams have had with this sensor and the onboard i2c port.

Re: LIDAR Sensor has arrived!
 

I wanted one of these period. I don't care if we use it.

Re: LIDAR Sensor has arrived!
 

Please correct me if I'm wrong, but there appears to be a bug in this file. You are calling updater.scheduleAtFixedRate(), which would be fine if you didn't already have a while() loop inside your TimerTask. Since you have a while loop, the run() function will never exit, so essentially your timer is useless and is acting like just a Thread object to run this function in the background indefinitely. The 'period' argument isn't being used, so the sensor will be polled every 10ms.

Also, since it came into the discussion, our team is using Java and we have been able to successfully use our RoboRio I2C port for a MaxBotix ultrasonic sensor, but not for the LIDAR sensor. Trying to use the LIDAR gives us write and read errors.

Re: LIDAR Sensor has arrived!
 

Hello all, a while ago our team posted that we were able to successfully collect data from the Lidar sensor using LabVIEW. Today I'm posting the code we're using to collect the data, as well as pictures of the placement of these VI's in the robot project. Feel free to use them as needed.

Re: LIDAR Sensor has arrived!
 

Do you know if more than one LIDAR-Lite can be connected via CAN through the MXP's can bus?

The LIDAR-Lite appears to have a fixed slave address - 0xC4.

LIDAR-Lite Spec

Why would they not make it configurable? Seems like that would prevent one from being able to use multiple LIDAR-Lites on the same I2C bus.

Maybe I'm missing something. The LIDAR's slave address must be configurable somehow. :confused: