Adding MPU9250 OP 2 beta

[Ranur]

I'm stuck here as well have a basic question. Do the MPU-9250 need to attached directly to the Rpi OR can I attach it to a ESP8266 and transfer the data over signal K? this is possible - GREAT! And if so - how?! Right now I think I have attached it in the I2C setup, but it does not show up as detected in pypilot.

It gets set up in Pypilot and no i would not have it connected via wifi ie esp32 or esp8266. I just set my up on rpi4 Pypilot saw the mpu.

Question was more related ro possibility rather than preference. I am wondering if it is POSSIBLE to connect the MPU to an esp8266 and still get valid yaw/roll//pitch sent via signal K to OP.

[jim321]

it need's to be connected on the i2c bus of the machine thats running pypilot.
pypilot controls it basically i read somewhere that theirs to much lag trying to do it wireless

[Ranur]

it need's to be connected on the i2c bus of the machine thats running pypilot.
pypilot controls it basically i read somewhere that theirs to much lag trying to do it wireless

Thanks for the clarification Jim!

[Ranur]

Still playing around with this. Disconnected from esp8266 and connected directly tog GPIO on Pi. Pypilot can är aand calibrate, but the 9250 doesn't show up in I2C and I guess that's why I can not get yaw, roll, and pitch as Signal K data. Any pointers?

EDIT:
By adding the info from the Pypilot installera and adding a UDP connection to signal k it seems to be working. Is this the proper way of am I duplicating Signal K data now?

[Surfer2010]

Hello,


I do have the same problem, the MPU 9250 is connected by I2C using the MarineControlServer and is shown by OpenPlotter I2C adress interface at 69 (a0 connected to vcc) but Pypilot is constantly showing "auto discovery" not showing this sensor.

Any help would be great