Lidar-Lite Help Please

[slibert]

Originally Posted by Bpk9p4

any chance you could post a wiring diagram of how you had it wired?

Lidar Lite Pinout is on page 8 of this datasheet: http://www.robotshop.com/media/files...32i500s011.pdf

RoboRio onboard I2C pinout is displayed on the silkscreen of the robot itself.

Simply connect RoboRio -> Lidar Lite:

GND -> Signal/Power Ground
3.3V -> POWER_IN
SCL -> I2C Clock (SCL)
SDA -> I2C Data (SDA)

My V1 sensor worked fine w/the 3.3V power pin from the RoboRIO onboard I2C connector - but you could provide it 5V power instead from one of the 5V RoboRio power rails (or the VRM) and that should work too.

[Bpk9p4]

thanks. Some people were saying you need a pull up resist to get it to work. Sounds like you got it to work without one?

[RyanN]

Originally Posted by Bpk9p4

thanks. Some people were saying you need a pull up resist to get it to work. Sounds like you got it to work without one?

The roboRIO has 2.2k pull-up resistors on the I2C pins as mentioned on page 15 of the User Manual.

[khannasusa]

Hi All

Thanks for all your posts and replies. Here is the final update from our experiments -

we looked at the example from Marvin T MARS Team 2614. Thanks "sraque".

There are Lidar Open and read VIs and they work as-is. Also we have our Lidar connected to I2C on NavX via MXP ports on roborio

I have attached 2 images for open and read snippets from our Begin.vi and Lidar controller VIs.

--sk

[Bpk9p4]

Looks like you forgot to post the begin. Could you post it

[sraque]

Originally Posted by khannasusa

Hi All

Thanks for all your posts and replies. Here is the final update from our experiments -

we looked at the example from Marvin T MARS Team 2614. Thanks "sraque".

There are Lidar Open and read VIs and they work as-is. Also we have our Lidar connected to I2C on NavX via MXP ports on roborio

I have attached 2 images for open and read snippets from our Begin.vi and Lidar controller VIs.

--sk

You are welcome. I could not figure out from your post if it is now working or not. If not, connect to the main roborio i2c port, not MXP. From last year, there were issues with the MXP i2c port. They may have been fixed this year, but I do not know.

[Bpk9p4]

I have tried both of your code and i keep getting the same error saying

<b>Complete call chain:</b>
i2clib_writeread.vi
WPI_I2CRead.vi
Lidar Read.vi
Simple Digital Output.vi
ERROR -1 i2clib_write.vi<ERR>
Device or resource busy


<b>Complete call chain:</b>
i2clib_write.vi
WPI_I2CWrite.vi
Lidar Read.vi
Simple Digital Output.vi
ERROR -1 i2clib_writeread.vi<ERR>
Device or resource busy

Has anyone seen this error before. Bellow is my code and a picture of the error log

Error log: http://imgur.com/II5VMzV
main code: http://imgur.com/CKZ7Dzk
open code: http://imgur.com/CKZ7Dzk
read code: http://imgur.com/UD1j4qk

wiring
Power: 3.3 on-board from the i2c port
Ground: on-board from the i2c port
SDA: on-board from the i2c port
SCL: on-board from the i2c port

[Richard100]

Need to see your Open code. The links for Open and Main both show main code.

Is you roboRIO I2C power jumper set to 3.3 V for the On-Board I2C interface?