- Mon Feb 06, 2017 7:27 am
#193267
Hi,
Bought both of 2 of these from Sparkfun. They're on the same I2C bus driven by a Raspberry Pi Zero and B2+ (V1.2 = B3 - wireless - bluetooth). I2C baudrate is 400kbps which both support. The zero version works beautifully. The B2+ has I2C errors after a few samples (<1s at IMU sampling of 500Hz).
The Zero is running on a 1.5A switching regulator. The B2+ is running from a 2.4A battery bank.
Swapping the LiDARs between the two, and it's always the B2+ which always causes the I2C errors.
Both a running identical code. The Zoe cable to the LiDAR is about 2"; to the B2+ it's 6". The latter uses UTP to remove noise.
Any ideas / suggestions what might be the cause - I've seen a few mentions of the pulseflow version doing this, but the only solution was to use the LiDAR PWM option which I'd like to avoid if at all possible - so much easier to use I2C to connect to RPi's.
Further details are on http://blog.pistuffing.co.uk/category/quadcopter/
TIA
Bought both of 2 of these from Sparkfun. They're on the same I2C bus driven by a Raspberry Pi Zero and B2+ (V1.2 = B3 - wireless - bluetooth). I2C baudrate is 400kbps which both support. The zero version works beautifully. The B2+ has I2C errors after a few samples (<1s at IMU sampling of 500Hz).
The Zero is running on a 1.5A switching regulator. The B2+ is running from a 2.4A battery bank.
Swapping the LiDARs between the two, and it's always the B2+ which always causes the I2C errors.
Both a running identical code. The Zoe cable to the LiDAR is about 2"; to the B2+ it's 6". The latter uses UTP to remove noise.
Any ideas / suggestions what might be the cause - I've seen a few mentions of the pulseflow version doing this, but the only solution was to use the LiDAR PWM option which I'd like to avoid if at all possible - so much easier to use I2C to connect to RPi's.
Further details are on http://blog.pistuffing.co.uk/category/quadcopter/
TIA