We ran into a problem where the libdistanceSensorDriver was not getting downloaded to the Roboio. We fixed the problem by editing the Rev2mDistanceSensor.json and set "sharedLibary" to True for this library. The Gradle build then copied the file to the Roborio. Not sure this was the correct method but it did work. Others may be having this issue.

As part of the porting for 2020, please change the include file path for I2C.h. It should be <hal/I2C.h> rather than <HAL/I2C.h>. I am able to compile things using the library successfully on Windows (case-insensitive filenames) but not on linux.

In file included from /home/hauser/sciborgs-2020/robot-2020/robot/src/subsystems/the_robot/trenchController.h:49:0,
                 from /home/hauser/sciborgs-2020/robot-2020/robot/src/subsystems/the_robot/TheRobotSetup.cpp:32:
/home/hauser/.gradle/caches/transforms-2/files-2.1/deb540110fe5084595fa2d5c06e4659b/DistanceSensor-cpp-0.0.6-headers/rev/Rev2mDistanceSensor.h:38:10: fatal error: HAL/I2C.h: No such file or directory
 #include <HAL/I2C.h>
          ^~~~~~~~~~~
compilation terminated.

Having a working vendordep.json for 2020 for this library and having it work on linux would greatly simplify our development and continuous integration tooling. Thanks.

Originally posted by @chauser in #6 (comment)

It would be cool if we could change the I2C address of the sensor so it would be possible to use several of them.
There is a function called VL53L0X_SetDeviceAddress that seems to allow to do it.

Need to make this work for 2020 image.

A RobotPy user would like us to support this sensor, but the provided vendor json doesn't point at valid artifacts.

Hello. Can we add a parameter to the constructor of the Rev2mDistanceSensor class to to override the I2C address? We figured out a way to change the address of the device at power-up so this would be useful to enable multiple devices on the same I2C bus.

When compiling for x86, compiler errors out since call to function abs() is ambiguous. Current workaround is to cast args in abs() as double for the x86 build. The compiler for the x86 build uses include -D__WINDOWS__ which is used with #ifdef to create a separate call to abs() for x86 only. For native roboRIO builds abs() is left untouched.

2m Distance Sensor depends on libDistanceSensorDriver.so, which is the compiled VL53L0X vendor driver. This is copied over to the roboRIO when a LabVIEW project is run, but any function calls made to this library will fail due to it not being found if a user has only used LabVIEW for the 2m Distance Sensor.

If a project is created in C++/Java using the 2m Distance Sensor, the gradle deploy process copies this shared library over, gives it the proper permissions and runs ldconfig to link the library. After doing this, any LabVIEW project can use the shared library.

This is currently noted as a workaround for installing LabVIEW, but should be fixed so users do not have to load a C++/Java project to their roboRIO before running LabVIEW.

Add details on how to download and install this as a vendor dependency and install for FRC.

I'm looking to wire up the 2m sensors to a Raspberry Pi for an 8th grade intro to engineering class. Any tips or sample code for reading the sensor via Python?