2017-04-21, 07:31 PM
(2017-04-21, 05:22 PM)Sailoog Wrote:(2017-04-21, 03:05 PM)eabarrow Wrote: I just did a new install last night (ruined an SD card, for some reason), and I noticed that the updater took me to version 11.
That's quite an update! It took 20 minutes or so to do all the compilation and everything else.
Can you please give us some insight into why the major version change, and what changes are in this release?
It was a major update because some dependencies need to be updated. This is how version numbering works:
https://sailoog.gitbooks.io/openplotter-...ating.html
And you will be able to see all changes here:
https://github.com/sailoog/openplotter/b...ANGELOG.md
If you have not updated your system for long time, there will be lot of task to do but next update will took less time.
This time we needed a major update due to an important update of signal k node server and signal k specification. This is good news because signal k is close his final stable version and we are working hard to be ready when this happens.
I've been away for a while, but 2 days ago I installed 0.10.0 and upgraded to 0.10.2 - wow - big changes! Nice! And I really like the update process. This morning, I saw that 0.11.0 had been released - updated, then updated to 0-.11.1. Update process was a breeze - really a nice process Sailoog! All local setting retained!
The only problem I've run into on both version 0.10.2 and 0.11.1 is that I am unable to see 1w sensors or I2C sensors on either NMEA0182 diagnostc or SignalK diagnostic.
1w - I have 6 DS18b20's sensors setup and can see them at the at the os level.
I2C's - I have an MPU-9150, BMP180, and HTU21D. they show up on I2C tab and I can see the calibration output of the MPU-9150.
I noticed the 1W and I2C were started in the OP startup screen.
Is there anything I can check on my side? Any help appreciated.