Remote MPU9255

[ddelorme]

3-5ms lag would be ok, but is the lag constant like it is from i2c?

I don't really recommend a wireless imu, instead it would be easier to use a second raspberry pi zero running tinypilot in remote client.

I it jumps around a bit depending where people are in the boat, humidity and what ever can interfere with the wifi signal. It is mounted at the top of the mast so it is approximately 40 - 50 feet from the RPI and threw a few layers of fibreglass. I am using UDP so if i miss one i get the next in 100ms I did not see a drop in the testing and watching it eats time. The slowest part is displaying the data in SK or Opencpn they dont like to display data that fast. Kip was a bit smother..   With the ESP32. masthead unit I did some tests with my phone and could pick up the esp32 from a few hundred feet away.  I Sent 3.3 volts to the davis and used a shorter line in the build but it work with the long one too.
I really don't think an IMU would work as they are little *(cky to work with it seems. I have 2 esp32 in a drawer but they are the clunky non breadboard types. maybe i will wire one up and see.
I will do a test.

Code:

pi@openplotter:~ $ ping 10.10.10.101
PING 10.10.10.101 (10.10.10.101) 56(84) bytes of data.
64 bytes from 10.10.10.101: icmp_seq=1 ttl=255 time=2.93 ms
64 bytes from 10.10.10.101: icmp_seq=2 ttl=255 time=2.08 ms
64 bytes from 10.10.10.101: icmp_seq=3 ttl=255 time=2.09 ms
64 bytes from 10.10.10.101: icmp_seq=4 ttl=255 time=2.37 ms
64 bytes from 10.10.10.101: icmp_seq=5 ttl=255 time=3.45 ms
64 bytes from 10.10.10.101: icmp_seq=6 ttl=255 time=2.04 ms
64 bytes from 10.10.10.101: icmp_seq=7 ttl=255 time=2.37 ms
64 bytes from 10.10.10.101: icmp_seq=8 ttl=255 time=2.24 ms
64 bytes from 10.10.10.101: icmp_seq=9 ttl=255 time=2.21 ms
64 bytes from 10.10.10.101: icmp_seq=10 ttl=255 time=2.68 ms

That is between  and esp8266 and a rpi running openplotter  @ 1 meter not much lag. It was sending data at the time to the rpi.