2022-05-29, 08:09 PM
Hi,
Digging up this thread a bit. I'm having similar issue to many users in this thread which is strange.
My configuration is the following :
Raspberry Pi 3 with the following image : https://pypilot.org/download.php?Down=im..._16.img.xz
When I run pypilot_boatimu I have the following output :
I know connection is well made because I find the MPU on the i2c bus with :
And I also tried with the address 0x68.
This is really strange that we are many with the same problem. Do you guys have any news on this ?
Thanks
Digging up this thread a bit. I'm having similar issue to many users in this thread which is strange.
My configuration is the following :
Raspberry Pi 3 with the following image : https://pypilot.org/download.php?Down=im..._16.img.xz
When I run pypilot_boatimu I have the following output :
Code:
imu process 4290
pypilotServer process 4292
failed to load pypilot.conf not enough values to unpack (expected 2, got 1)
server setup has 3 pipes
made imu process realtime
Using settings file RTIMULib.ini
Settings file not found. Using defaults and creating settings file
Failed to open SPI bus 0, select 0
Using fusion algorithm Kalman STATE4
ERROR: No IMU Detected 228.716127516
warning, failed to make calibration process idle, trying renice
imu rate set to rate 20
setting initial gyro bias [-1.566, -0.837, 0.119]
server add socket ('127.0.0.1', 40534)
server add socket ('127.0.0.1', 40536)
calibration loaded, starting 4289
server, remove socket ('127.0.0.1', 40536)
server add socket ('127.0.0.1', 40538)
server, remove socket ('127.0.0.1', 40534)
server, remove socket ('127.0.0.1', 40538)
server add socket ('127.0.0.1', 40540)
server, remove socket ('127.0.0.1', 40540)
I know connection is well made because I find the MPU on the i2c bus with :
Code:
tc@pypilot:~/i2c-tools$ sudo i2cdetect -y 1
0 1 2 3 4 5 6 7 8 9 a b c d e f
00: -- -- -- -- -- -- -- -- -- -- -- -- --
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
60: -- -- -- -- -- -- -- -- -- 69 -- -- -- -- -- --
70: -- -- -- -- -- -- -- --
And I also tried with the address 0x68.
This is really strange that we are many with the same problem. Do you guys have any news on this ?
Thanks