2020-03-14, 04:05 PM
I promised some update if I knew more:
- after getting an error of wrong ID (112) I replaced the MPU with another MPU9250
(exchanging the cheap noname MPU by a Sparkfun worked here).
- I hardcoded on every spot i2c-bus = 2 (as required by my hardware)
- the RTIMULib still uses some autoconfiguration, where a default i2c-bus of 1 is assumed
after setting the RTIMULib.ini the RTIMU also works correctly.
After these changes most Openplotter scripts work.
Since I have to give a password for sudo I needed some changes in sudoers to get everything working without auth.
And I did not use Openplotter by the book, but after openplotter-i2c-read and openplotter-pypilot-read were running
the configuration tools worked as well.
The problems with the IMU became visible after the umpteenth reinit when using pypilot_boatimu without options.
Most changes for openplotter-i2c where pretty straightforward replacements of the i2c-bus in python.
Configuring RTIMU made openplotter-pypilot work (and one changed i2c-bus in a i2cdetect call).
The reason to still ask you to implement the a configurable i2c port is that those features should be upstreamed when possible (and my coding style is quite bad).
Through it all I got one other feature request:
For pypilot the data needs to be obtained in realtime, when using the IMU in compass-only mode, could the measurement frequence drop to perhaps once every 1-10 seconds?
I think after accuracy powersaving gets more important for compass-only. Or perhaps this was allready requested?
- after getting an error of wrong ID (112) I replaced the MPU with another MPU9250
(exchanging the cheap noname MPU by a Sparkfun worked here).
- I hardcoded on every spot i2c-bus = 2 (as required by my hardware)
- the RTIMULib still uses some autoconfiguration, where a default i2c-bus of 1 is assumed
after setting the RTIMULib.ini the RTIMU also works correctly.
After these changes most Openplotter scripts work.
Since I have to give a password for sudo I needed some changes in sudoers to get everything working without auth.
And I did not use Openplotter by the book, but after openplotter-i2c-read and openplotter-pypilot-read were running
the configuration tools worked as well.
The problems with the IMU became visible after the umpteenth reinit when using pypilot_boatimu without options.
Most changes for openplotter-i2c where pretty straightforward replacements of the i2c-bus in python.
Configuring RTIMU made openplotter-pypilot work (and one changed i2c-bus in a i2cdetect call).
The reason to still ask you to implement the a configurable i2c port is that those features should be upstreamed when possible (and my coding style is quite bad).
Through it all I got one other feature request:
For pypilot the data needs to be obtained in realtime, when using the IMU in compass-only mode, could the measurement frequence drop to perhaps once every 1-10 seconds?
I think after accuracy powersaving gets more important for compass-only. Or perhaps this was allready requested?