This forum uses cookies
This forum makes use of cookies to store your login information if you are registered, and your last visit if you are not. Cookies are small text documents stored on your computer; the cookies set by this forum can only be used on this website and pose no security risk. Cookies on this forum also track the specific topics you have read and when you last read them. Please confirm whether you accept or reject these cookies being set.

A cookie will be stored in your browser regardless of choice to prevent you being asked this question again. You will be able to change your cookie settings at any time using the link in the footer.

Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
MPU-9250 not detected
#31
Can you simply run the pypilot_boatimu script from the console?

It should give an output showing the sensor or better error message. Ensure pypilot and no other service accessing the device is run. It should work on either 0x68 or 0x69
Reply
#32
It appears that my MPU9250 is detected. However, I'm facing other issues. Something about "bind failed" and "failed to read IMU" doesn't look to be too good. Running i2cdetect -y1 returns a result at 68. Shouldn't I also be seeing another? I'm concerned that I might be one of those poor saps who reveived an incomplete module Angry.

I hope that somebody might be able to decipher the following and perhaps lead me down the road to a successful install...

Code:
Detected MPU9250/MPU9255 at standard address
IMU Name: MPU-925x
min/max compass calibration not in use
Using ellipsoid compass calibration
Using accel calibration
MPU-925x init complete
imu process failed to keep time 0.48403546400004416 1611.37877089 1611.862660615 1611.86273541 1611.862805428
pypilot_server: bind failed; already running a server?
failed to read IMU! 1612.46334929.06407425683304 heading 250.55594938302625
Detected MPU9250/MPU9255 at standard address
IMU Name: MPU-925x
min/max compass calibration not in use
Using ellipsoid compass calibration
Using accel calibration
I2C read error from 12, 16 - Failed to read compass fuse ROM
ERROR: IMU Init Failed, no inertial data available 1612.463997374
imu process failed to keep time 0.3076851910000187 1612.463344883 1612.770943353 1612.77098763 1612.771029741
IMURead failed!

I'm runing pypilot 3.2.11 with OpenPlotter 3.5.0 on a Pi 4b

(2023-03-28, 11:10 PM)HeviiSailor Wrote: It appears that my MPU9250 is detected. However, I'm facing other issues. Something about "bind failed" and "failed to read IMU" doesn't look to be too good. Running i2cdetect -y1 returns a result at 68. Shouldn't I also be seeing another? I'm concerned that I might be one of those poor saps who reveived an incomplete module Angry.

Yet I do see 2 data sources from Pypilot in SignalK:
  • navigation.attitude (populated)
  • navigation.headingTrue (also populated)
Reply
#33
(2023-03-28, 11:10 PM)HeviiSailor Wrote: It appears that my MPU9250 is detected. However, I'm facing other issues. Something about "bind failed" and "failed to read IMU" doesn't look to be too good.

I'm not familiar with OpenPlotter but "bind failed" might indicate that you're launching two instances of pypilot, which could explain why the second one is not able to access the MPU.
Reply
#34
also me I have a smimilar issue wth bind failed...

Failed to open SPI bus 0, select 0
Using fusion algorithm Kalman STATE4
BŁĄD: Nie wykryto IMU 378.787526965
pypilot_server: wiązanie nie powiodło się; masz już serwer?

if I go to Web control I see details for IMU. Wondering if Web control doesnt disturb here?

Ps.

not actual, I solved the issue Smile
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)