You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We only support the I2C interface at the moment, but one issue we have is that no I2C messages are available if there is no object visible. This makes it difficult for us to know if the sensor is healthy or not. For example, we can't tell the difference between whether the sensor is disconnected vs attached but no objects are visible.
I'll pass this on to Thomas Stone who is responsible for the IRLock sensor as well.
The text was updated successfully, but these errors were encountered:
I'm one of the lead developers of ArduPilot (www.ardupilot.org) which I think is the most widely used open source drone software and we use a modified version of the Pixy for "precision landing". http://ardupilot.org/copter/docs/precision-landing-with-irlock.html.
We only support the I2C interface at the moment, but one issue we have is that no I2C messages are available if there is no object visible. This makes it difficult for us to know if the sensor is healthy or not. For example, we can't tell the difference between whether the sensor is disconnected vs attached but no objects are visible.
I'll pass this on to Thomas Stone who is responsible for the IRLock sensor as well.
The text was updated successfully, but these errors were encountered: