2017-06-02, 04:19 PM
Edit openplotter.conf file and remove the value of variable sensors:
[I2C]
sensors =
[I2C]
sensors =
MPU-9255
|
2017-06-02, 04:19 PM
Edit openplotter.conf file and remove the value of variable sensors:
[I2C] sensors =
2017-06-04, 09:22 AM
Hello,
Thank ! That has solved the start issue of OpenPlotter. Still the same mystery about RTIMULib
2017-06-04, 07:35 PM
We can't change the files imu/check_sensors.py and openplotter as you did in your github fork at the moment. Otherwise other users could get errors when selecting 9255 with the old rtimulib.
So redo these changes to 0.11.9. When you then select 9255 the errors shouldn't come again.
It works!!!
So I can definitely say that there are remains of an RTIMU lib in the system. You need to remove all the RTIMUlib files in usr/lib/... but ALSO all the python files hidden everywhere (usr/lib/python2.7, usr/lib/python3.4, usr/lib/python3 , also in usr/local/lib/python/...). After what I reinstalled RTIMU (and I added python3 setup.py install). Now when I open openplotter, the good file is created, also with the i2c-detect.py creating "detected-....ini". The value of the magnetic heading and the pitch are now visible and working in SignalK. (But they (+temperature + pression + humidity) are not send to NMEA183 at the moment, only GPS data ) @sailoog : I would be you, I would maybe generate a new NOOB without the corrupted old files. That is maybe why you say that RTIMULib is not stable. And it would speed up the process of reinstalling the system after some experimentation.
2017-06-13, 04:45 PM
congratulations
corrupted old files? they are not corrupted, they work right for the repo they belong. I think the original RTIMULib is stable. We need to test other forks that add support for more IMUs but we need to check this very well. I prefer to keep the self-update system until the stable version and not force users to burn another SD. I am sure we can start testing another RTIMUlib fork and delete old files on every major update before compiling the new fork. Could you make a list of files to delete? we could trace the code to search for exactly all files but you have already done some work. Thanks!
2017-06-13, 08:02 PM
Here you have what I just did with a clean installation (And I persist, a noob version of the Beta would save one or two hours of update ). I cannot promise I haven't forgotten a files or broken some functions.
Is that normal that you have files named with 7.2.1 and others with 8.0.0? That's why I am talking about old files. Code: sudo rm /usr/lib/libRTIMULib.so
Thanks a lot
There is something weird here... When you do "sudo make -s install" all target files will be replaced only if there are changes on it (file modification date) and there is not option to force overwriting. This should work, but Python installation only will replace files if the package version is upper. Look at this: this is the version of the original code: https://github.com/RTIMULib/RTIMULib2/bl...n/setup.py and this is the version of the forked code: https://github.com/Nick-Currawong/RTIMUL...n/setup.py both are 8.0.0 so when you do "python setup.py -q install" nothing is installed but you do not realize because you are installing in silent mode " -q". My theory is that if you edit the version on the forked code to 8.1.0, it will work. You can also force updating doing "python setup.py install --force". I have no time to try this now but if you still have energies to test this, report please. Do not use silent modes, type: "sudo make install" "sudo python setup.py install" instead of: "sudo make -s install" "sudo python setup.py -q install" to see what is going on.
I won't do a complete reinstallation for now. It is way to long to do the initial update (more than 2 hours).
However I deleted all the RTIMU files. For all the files not included in "usr/local" I had an error : "file does not exist". Which prove that the 7.2.1 is old and deprecated files. Then I installed RTIMU from your git (the one in your "update dependencies.py" script. Logically, the .ini files were without MPU9255. Then I just intalled the git from Nick (no cleaning of any file and not updating the version number). and the MPU9255 was back and working. I am not a programmer and I don't understand everything. But according to me, the python script is updating even if the version number is the same. And the files not in usr/local should be manually deleted in your next update to "clean" the system. edit: I have updated my repo with all the changes that should fix and add MPU9255, for when you decide to switch to new version of RTIMULib. https://github.com/maxencep02/openplotter/commits/beta
2017-06-14, 08:25 PM
I think I got it. An old version of RTIMULIb is installed on Raspbian by default. Actually the Sensor Hat uses this library. If you want to delete old files you should type:
sudo apt-get remove --purge librtimulib-dev librtimulib-utils librtimulib7 python-rtimulib python3-rtimulib Then I think the last test should be: Burn a fresh OP and update to latest version. run: sudo apt-get remove --purge librtimulib-dev librtimulib-utils librtimulib7 python-rtimulib python3-rtimulib install RTIMULib from Nick repo test If this works we do not need to start a new image, just remove old packages on update sequence, choose a RTIMULib fork from Nick or others and add your code.
2017-06-15, 03:27 PM
Hi,
Your solution works and it is most probably the cleanest one. |
« Next Oldest | Next Newest »
|