Open kevlam2706 opened 5 years ago
One of myself or @Zinka010 can probably deal with this one.
The lidar code is not yet on master but is on the rcvi_laser branch. I had a question before North Bay on writing a regression test for it. Robert On Tuesday, April 2, 2019, 11:56:24 a.m. EDT, Kyle Anderson notifications@github.com wrote:
One of myself or @Zinka010 can probably deal with this one.
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.
Would this be a FluidConstant that can be changed in network tables or simply a value that could be easily read on it?
@Zinka010 it should just be something put to SmartDashboard. Every tick you would simply have to run
SmartDashboard.putNumber(someNumber);
with someNumber
being the distance that our lidar code determines in feet.
This might be for @robertlucyshyn and @RachelLucyshyn. Get the LIDAR reading and publish it to a networktable value (and possibly a smartdashboard value) for driver monitoring. The vision Pi could use the distance value to annotate the images it saves. This could be a good sanity check of the vision distance calibration.