Quote:
Originally Posted by nickbrickmaster
RobotPy is 2016.2.0 on robot and driver station.
Is this a bug in robotpy or am I messing up somewhere?
Thanks for the help.
|
It very well could be a bug in RobotPy, the i2c interface isn't particularly well tested -- though, I was able to talk to the
NavX device via I2C without any issues.
What value are you passing in for 'port' to the I2C constructor? I ask because I see that in HAL it
checks to see if port < 0, and returns -1 if so -- which wouldn't set errno (and perhaps why you're seeing the 'success' message). I'll add a check for that so it can't happen in the future...
This error also reminds me of
this bug that someone reported for WPILib.