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
IMU starange behavior
#1
Hi, does somebody have idea where to look.

I am working to get my ICM-20948 work on Rpi5

However I am not sure issue related to Rpi5

Periodically, EXACTLY once in a minute it turns over my boat :-) and get back to normal.

Nothing in pypilot log related to IMU

Video is here
https://photos.app.goo.gl/Zn4dJecmBaBuyoxw7
[Image: Zn4dJecmBaBuyoxw7]
Reply
#2
yikes. If you stop the pypilot service and run pypilot from the console directly is there any output?

Maybe another service is trying to access i2c? Do you have a pi4 or other pi to compare? Can you run 'pypilot_scope' and plot the sensors output to see if it is compass, accel, gyro or all?
Reply
#3
(2024-03-04, 05:26 AM)seandepagnier Wrote: yikes.    If you stop the pypilot service and run pypilot from the console directly is there any output?

Maybe another service is trying to access i2c?    Do you have a pi4 or other pi to compare?    Can you run 'pypilot_scope' and plot the sensors output to see if it is compass, accel, gyro or all?

On rpi5 
I tried to run as app, the same story. No suspicious output, all loos good in log. I tried to run pypilot_boatimu it has sensors data in output, data is “jumping” every minute there too.

I tried to run the same sensor on pi4.
After each system restart it does this turn over couple times on rpi4, then stops. 
[update] after several reboots stopped strange behavior on Rpi4, but when i come to rpi5 continue again


First moment I thought it is the sensor problem, but after it stopped to do turning it looks more like sw.
Reply
#4
I added debug output to boatIMU.py (line 484) and print raw data from IMUread() command, it looks like IMUread gives wrong data.

log is here:
https://drive.google.com/file/d/1_z9Vfdo...drive_link


Any ideas where to look?

PS. On rpi4 it did cople rotates, then set to normal, even after reboots, it still good.

(2024-03-05, 03:28 AM)partyvi Wrote: I added debug output to boatIMU.py (line 484) and print raw data from IMUread() command, it looks like IMUread gives wrong data.

log is here:
https://drive.google.com/file/d/1_z9Vfdo...drive_link


Any ideas where to look?

PS. On rpi4 it did cople rotates, then set to normal, even after reboots, it still good.

[UPDATE}
try other IMU - L3GD20H/LSM303DLHC

behaviour is EXACTLY the same, exactly once per minute boat doing kind of turn over.
Reply
#5
Boat turn over mystery resolved!!!!!

Issue was in OP plugins, by default they update time every 60 seconds.
And in the moment of time update boat did this turn over, looks like something wrong there.

I switched off "set system time" plug-in - problem with IMU get solved. (at least for now)
I will need to figure out how to set time after power off without internet, however RTC battery can be connected to Rpi5

syslog in the moment of turn over.
Mar 04 22:27:33 openplotter sudo[7507]: pi : PWD=/home/pi/.signalk ; USER=root ; COMMAND=/usr/bin/date --iso-8601 -u -s 2024-03-05T04:27:33.000Z
Mar 04 22:27:33 openplotter sudo[7506]: pi : PWD=/home/pi/.signalk ; USER=root ; COMMAND=/usr/bin/date
Mar 04 22:27:33 openplotter systemd-journald[332]: Time jumped backwards, rotating.
Mar 04 22:27:33 openplotter sudo[7507]: pam_unix(sudoConfusedession): session opened for user root(uid=0) by (uid=1000)
Mar 04 22:27:33 openplotter sudo[7506]: pam_unix(sudoConfusedession): session opened for user root(uid=0) by (uid=1000)
Mar 04 22:27:33 openplotter sudo[7506]: pam_unix(sudoConfusedession): session closed for user root
Mar 04 22:27:33 openplotter sudo[7507]: pam_unix(sudoConfusedession): session closed for user root
Reply
#6
why is this only on the pi5 though?
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)