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
New OpenPlotter v0.10.0alpha release
#1
Information 
Hi OP user,

We have published a new image:


http://www.sailoog.com/en/blog/download-...lpha-noobs

The bad news:

Signal K is suffering changes and they are affecting to most features of OpenPlotter. We have already rewrite some of them but others need still work. This is why this last image is still alpha.

The good news:

The main feature of this new image is a self-updating system. You will be able to apply all changes we are doing until you get an stable system without having to burn a new image: https://sailoog.gitbooks.io/openplotter-...ating.html

Thanks to all for your patience.
Reply
#2
(2017-04-12, 05:48 PM)Sailoog Wrote: Hi OP user,

We have published a new image:


http://www.sailoog.com/en/blog/download-...lpha-noobs

The bad news:

Signal K is suffering changes and they are affecting to most features of OpenPlotter. We have already rewrite some of them but others need still work. This is why this last image is still alpha.

The good news:

The main feature of this new image is a self-updating system. You will be able to apply all changes we are doing until you get an stable system without having to burn a new image: https://sailoog.gitbooks.io/openplotter-...ating.html

Thanks to all for your patience.
I have the new version running and have applied all updates. Now on 0.10.2 alpha

The networking seems bust. I can't open diagnostics in the NMEA0183 or Signal K tabs, or anywhere for that matter. 
My I2C sensors seem to have been recognised but not 1W
I have an I2C GPS hat and that is appearing on ttyS0. I did chmod on that to 666 as usual, 

but the odd thing is that if I do "cat ttyS0" I get a lost of messages "$GPTXT,01,01,01,NMEA unknown msg*58" - never seen that before. 

Chris
Reply
#3
Does the self-updating function retain configuration settings, where possible?
Reply
#4
(2017-04-13, 02:19 PM)Saqqara Wrote: Does the self-updating function retain configuration settings, where possible?

Absolutely
Reply
#5
(2017-04-13, 12:29 AM)Littlechay Wrote:
(2017-04-12, 05:48 PM)Sailoog Wrote: Hi OP user,

We have published a new image:


http://www.sailoog.com/en/blog/download-...lpha-noobs

The bad news:

Signal K is suffering changes and they are affecting to most features of OpenPlotter. We have already rewrite some of them but others need still work. This is why this last image is still alpha.

The good news:

The main feature of this new image is a self-updating system. You will be able to apply all changes we are doing until you get an stable system without having to burn a new image: https://sailoog.gitbooks.io/openplotter-...ating.html

Thanks to all for your patience.
I have the new version running and have applied all updates. Now on 0.10.2 alpha

The networking seems bust. I can't open diagnostics in the NMEA0183 or Signal K tabs, or anywhere for that matter. 
My I2C sensors seem to have been recognised but not 1W
I have an I2C GPS hat and that is appearing on ttyS0. I did chmod on that to 666 as usual, 

but the odd thing is that if I do "cat ttyS0" I get a lost of messages "$GPTXT,01,01,01,NMEA unknown msg*58" - never seen that before. 

Chris

Please open a terminal, type openplotter and try to open a diagnostic window from openplotter interface. If the terminal returns an error paste it here.

An I2C GPS detected as serial? no much sense. I think you don't need to set 666, just add ttySO to NMEA 0183 tab and it should work.
Reply
#6
(2017-04-13, 04:35 PM)Sailoog Wrote:
(2017-04-13, 12:29 AM)Littlechay Wrote:
(2017-04-12, 05:48 PM)Sailoog Wrote: Hi OP user,

We have published a new image:


http://www.sailoog.com/en/blog/download-...lpha-noobs

The bad news:

Signal K is suffering changes and they are affecting to most features of OpenPlotter. We have already rewrite some of them but others need still work. This is why this last image is still alpha.

The good news:

The main feature of this new image is a self-updating system. You will be able to apply all changes we are doing until you get an stable system without having to burn a new image: https://sailoog.gitbooks.io/openplotter-...ating.html

Thanks to all for your patience.
I have the new version running and have applied all updates. Now on 0.10.2 alpha

The networking seems bust. I can't open diagnostics in the NMEA0183 or Signal K tabs, or anywhere for that matter. 
My I2C sensors seem to have been recognised but not 1W
I have an I2C GPS hat and that is appearing on ttyS0. I did chmod on that to 666 as usual, 

but the odd thing is that if I do "cat ttyS0" I get a lost of messages "$GPTXT,01,01,01,NMEA unknown msg*58" - never seen that before. 

Chris

Please open a terminal, type openplotter and try to open a diagnostic window from openplotter interface. If the terminal returns an error paste it here.

An I2C GPS detected as serial? no much sense. I think you don't need to set 666, just add ttySO to NMEA 0183 tab and it should work.

HI,

Yes sorry I2C was a brain fart. It is a serial GPS on a HAT. ttyS0 is added to the 0183 tab. 

I ran OP from the command line as you suggested. I get no errors while the OP window is open, still can't get any of the diagnostics windows to open. 

Nothing useful appeared after I closed the OP window other than what I knew
Code:
Failed to open /dev/ttyS0: Permission denied
Failed to initialize Interface GPS
Reply
#7
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?
Reply
#8
(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.
Reply
#9
(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.
Reply
#10
We are fixing actions now but I2C is the next on the list. However, 1W sensors have already been revised and are working right for me. Have you defined them on 1W tab? if yes, you should see them on SK diagnostic window.

Please open a terminal, type openplotter, define your 1W sensors on 1W tab again and watch for any error on the terminal.
Reply


Forum Jump:


Users browsing this thread: 2 Guest(s)