OpenPlotter project

[conachair]

Originally Posted by SYVoyager

Hi petter5,

What I did to rule a possible faulty power supply out was to connect the Pi3 to a high quality lab. power supply. No result after searching the web a suggestion was mentioned to add boot_delay=1 to the config.txt file. Again no result. Like I said earlier booting the Pi3 with another firmware Raspian or UBUNTU MATE gives a perfect result.

Any suggestions are welcome!!

If you are seeing a rainbow screen then it's very likely your power supply, to check for sure measure the voltage between the ground and 5v gpio pins.

https://m.youtube.com/watch?v=MWbOKSX5JGE

Sent from my SGP511 using Tapatalk

[Abgreenbank]

For those of you that are waiting for your new pi3 , when you setup I found I could not pair a Bluetooth keyboard with the blueman gui bluetooth manager. So if you installed blueman, uninstall it and just used bluetoothctl, and it will pair fine. It would not pair using bluetoothctl when blueman was installed.
Maybe this is why blueman is not installed on the latest noobs just pi-Bluetooth.

Regards

Ab


Sent from my iPad using Cruisers Sailing Forum

[Sailoog]

Originally Posted by SYVoyager

Hi petter5,

What I did to rule a possible faulty power supply out was to connect the Pi3 to a high quality lab. power supply. No result after searching the web a suggestion was mentioned to add boot_delay=1 to the config.txt file. Again no result. Like I said earlier booting the Pi3 with another firmware Raspian or UBUNTU MATE gives a perfect result.

Any suggestions are welcome!!

OpenPlotter v0.6.0 and v0.7.0beta are based on raspbian 2015-11-21. If you can run without problems the current raspbian 2016-02-26, you will not have problems with the future OpenPlotter v0.7.0 stable.

[Sailoog]

Originally Posted by svlittlewing

Testing V0.7.0 on a Pi 2. It looks real good - lots of progress! I did want to pass along three issues I ran into. Wish I could contribute to fixing them - but I'm just getting started. Hope this helps.

BMP180 sensor is recognized as I2C sensor (Thanks!) , but temps at -185 C and pressure at .9865 hPa are reported . The multiple DS18B20's (Thanks again!) all report correctly at 70.5F to 70.7F

When closing the NMEA Inspector window - the following errors are raised:
Exception in thread Thread-2:
Traceback (most recent call last):
File "/usr/lib/python2.7/threading.py", line 810, in __bootstrap_inner
self.run()
File "/usr/lib/python2.7/threading.py", line 763, in run
self.__target(*self.__args, **self.__kwargs)
File "/home/pi/.config/openplotter/output.py", line 267, in refresh_loop
wx.CallAfter(self.refresh_data)
File "/usr/lib/python2.7/dist-packages/wx-3.0-gtk2/wx/_core.py", line 16708, in __getattr__
raise PyDeadObjectError(self.attrStr % self._name)
PyDeadObjectError: The C++ part of the MyFrame object has been deleted, attribute access no longer allowed.

Exception in thread Thread-1:
Traceback (most recent call last):
File "/usr/lib/python2.7/threading.py", line 810, in __bootstrap_inner
self.run()
File "/usr/lib/python2.7/threading.py", line 763, in run
self.__target(*self.__args, **self.__kwargs)
File "/home/pi/.config/openplotter/output.py", line 164, in parse_data
if frase_nmea and self.pause_all==0:
File "/usr/lib/python2.7/dist-packages/wx-3.0-gtk2/wx/_core.py", line 16708, in __getattr__
raise PyDeadObjectError(self.attrStr % self._name)
PyDeadObjectError: The C++ part of the MyFrame object has been deleted, attribute access no longer allowed.

When closing the AIS waterfall window the following errors are raised:
Found Rafael Micro R820T tuner
[R82XX] PLL not locked!
Exact sample rate is: 1000000.026491 Hz
invalid command name "1930453080_on_timer"
while executing
"1930453080_on_timer"
("after" script)
Traceback (most recent call last):
File "/home/pi/.config/openplotter/waterfall.py", line 193, in <module>
main()
File "/home/pi/.config/openplotter/waterfall.py", line 186, in main
wf.start()
File "/home/pi/.config/openplotter/waterfall.py", line 163, in start
pyl.show()
File "/usr/lib/python2.7/dist-packages/matplotlib/pyplot.py", line 155, in show
return _show(*args, **kw)
File "/usr/lib/python2.7/dist-packages/matplotlib/backend_bases.py", line 184, in __call__
self.mainloop()
File "/usr/lib/python2.7/dist-packages/matplotlib/backends/backend_tkagg.py", line 71, in mainloop
Tk.mainloop()
File "/usr/lib/python2.7/lib-tk/Tkinter.py", line 413, in mainloop
_default_root.tk.mainloop(n)
AttributeError: 'NoneType' object has no attribute 'tk'

Try to fix the wrong pressure and temperature readings clicking the buton Reset in I2C sensors tab.

Do not worry about inspector and waterfall errors when closing, they are normal because we are killing process by brute force while they are working. Once restarted inspector an waterfall windows will work as expected.

Thanks for reporting!

[Sailoog]

Originally Posted by Abgreenbank

For those of you that are waiting for your new pi3 , when you setup I found I could not pair a Bluetooth keyboard with the blueman gui bluetooth manager. So if you installed blueman, uninstall it and just used bluetoothctl, and it will pair fine. It would not pair using bluetoothctl when blueman was installed.
Maybe this is why blueman is not installed on the latest noobs just pi-Bluetooth.

Regards

Ab


Sent from my iPad using Cruisers Sailing Forum

Thanks for the advice. Do you think that pi-bluetooth will work with bluetooth dongles or just with internal RPI3 bluetooth?

[Timpe]

Originally Posted by Sailoog

Is this at the beginning of ellipsoid calibration or at the end?

This is at the end of the ellipsoid calibration.

[Abgreenbank]

Not sure but there is a choice of adapter in the bluetoothctl menu, so can't see why not.
My pi2 and dongle and proper power supply is on the boat and I'm not, so can't check, however I certainly can't load open plotter with a 1amp power supply, even installing from noobs shows a power issue but just gets going.
Just emailed you to see if you have any USB nmea connectors ?

Regards
Alistair


Sent from my iPad using Cruisers Sailing Forum

[Abgreenbank]

Oh forgot, I enabled the experimental open gl driver and ran Glx gears and had a nice steady 60 frames/sec, only 30 frames/sec without OpenGL driver, so looks reasonably good speed.

Ab


Sent from my iPad using Cruisers Sailing Forum

[conachair]

Has anyone booted headless with hardware acceleration enabled? I just tried on a pi2 and 3 but it wouldn't show an access point, works fine with hardware accel turned off in the old raspi config.


Sent from my SGP511 using Tapatalk

[bcn]

Two questions as we are preparing the S-63 plug-in for ARM:

- Openplotter 0.7 is using OCPN 4.2 - right?
- and wxWidgets 3.0 - right?

Thanks

Hubert

[Sailoog]

Originally Posted by bcn

Two questions as we are preparing the S-63 plug-in for ARM:

- Openplotter 0.7 uses OCPN 4.2 - right?
- and wxWidgets 3.0 - right?

Thanks

Hubert

Hi Hubert!

Glad to see you here.

Yes, well... 0.6.0 and 0.7.0beta not but 0.7.0 stable will come with OCPN 4.2 and all the required packages wx included.

[bcn]

Ok, so we will prepare a version for O 4.2/wxW 3.0...

[Sailoog]

Originally Posted by Timpe

This is at the end of the ellipsoid calibration.

Ok thanks, I will check this ASAP.

[Sailoog]

Originally Posted by conachair

Has anyone booted headless with hardware acceleration enabled? I just tried on a pi2 and 3 but it wouldn't show an access point, works fine with hardware accel turned off in the old raspi config.


Sent from my SGP511 using Tapatalk

Do you mean OpenGL accel or overclocking?

[o-charts]

Just published at the OpenCPN forum:

The S-63 plug-in is available now for an additional architecture:

ARMhf

to install from Launchpad

https://launchpad.net/~opencpn/+archive/ubuntu/opencpn

System requirements are OPCPN 4.2 and wxWidgets 3.
This is our standard S-63 PI install for RaspberyPi devices running Raspian(Jessie).

A reminder: same as for all the other architectures be aware that the encrypted chart sets you receive from your chart providers have to be present on the system when running the plug-in: so no swapped removable media please.

As there are a very big variety of ARM based systems our testing possibilities are limited: before purchasing an UserPermit or licensing charts please install the plug-in, run the integrated fingerprinter and observe if a .fpr file has been created successfully.