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:
  • 1 Vote(s) - 5 Average
  • 1
  • 2
  • 3
  • 4
  • 5
OpenPlotter 4 roadmap
(2024-03-17, 11:33 AM)PaddyB Wrote:
(2024-03-15, 01:45 AM)PaddyB Wrote: Thnx though it seems rock solid, it's just that opencpn running on the Pi won't send to peer.

Not sure if this should be in bugs or not but for now... http response -1 is about communication errors between machines, I'll keep digging for now, just to recap >> with opencpn running on  a laptop, android tablet 6 openplotter V4 on a Pi4 the laptop & tablet will seed to peer to each other but not the Pi. 

https://www.cruisersforum.com/forums/f13...ost3881110

Not sure if this is related but I was having an issue with an Yachta wind sensor communicating with SignalK. I tried the hostname of the sensor first "windsensor-0.local" but that wouldn't work for me. With a little help from Newbie 1979 I tried using the WLAN Client IP and that did work for a bit. After a while, it kept dropping the connection while using the SignalK data connections.

Ended up connecting to the sensor in NodeRed with a TCP node and then sending it TCP to 10110. Has been rock solid since.

Seems like there is some type of compatibility issue with SignalK and the Pi5. Lots of weird stuff going on with network connections.
Reply
(2024-03-23, 01:52 PM)Sailoog Wrote: My waveshare touchscreen stop working after a system update (kernel 6.6.20) and when I connect headless I can not even start OpenCPN flatpak, it crashes immediately if the monitor is still connected. If I disconnect the touchscreen and connect headless, OpenCPN flatpak works OK.

I will try to get a Raspberry official touchscreen.

What is your touchscreen model?

Could you try disconnecting the monitor and connecting by remote desktop?

I ended up switching back to the deb package and then using the twofing package which seems to work.  

The touchscreen is this one, https://amzn.eu/d/7VIBc9G. It's 10.1" with hdmi input, and touchscreen via a usb connection.
Reply
About the SignalK (npm) update issue reported here: https://forum.openmarine.net/showthread....6#pid29066
I have created a new image, on a 32 GB SD card, using "2023-12-29-OpenPlotter-v4-Starting-beta-64bit-img" created by "Raspberry Pi imager" on a Rpi.
On the new image I changed localization settings like Timezone(ETC+1), keyboard (SE), wifi country(SE) and nothing more.
I also updated the system by "update" and "full-upgrade"
The I ran "Signal k Installer" and got the same result as before. Each update attempt, e.g.: "npm GET 200 https://registry.npmjs.org/socket.io.parser", is timed out as before.

Any advices what to test next?

/Håkan
Reply
(2024-03-26, 10:16 AM)rogerl Wrote:
(2024-03-23, 01:52 PM)Sailoog Wrote: My waveshare touchscreen stop working after a system update (kernel 6.6.20) and when I connect headless I can not even start OpenCPN flatpak, it crashes immediately if the monitor is still connected. If I disconnect the touchscreen and connect headless, OpenCPN flatpak works OK.

I will try to get a Raspberry official touchscreen.

What is your touchscreen model?

Could you try disconnecting the monitor and connecting by remote desktop?

I ended up switching back to the deb package and then using the twofing package which seems to work.  

The touchscreen is this one, https://amzn.eu/d/7VIBc9G. It's 10.1" with hdmi input, and touchscreen via a usb connection.

Sorry I do not understand this: "I ended up switching back to the deb package and then using the twofing package which seems to work."

I think most of the flatpak errors are permissions issues trying to access host resources (filesystem, graphical environment...). I will do some test using this flatpak app: https://flathub.org/apps/com.github.tchx84.Flatseal

This is a graphical permission manager for any installed flatpak app, try granting full permissions and see if the error persists.
Reply
(2024-03-26, 10:36 AM)Hakan Wrote: About the SignalK (npm) update issue reported here: https://forum.openmarine.net/showthread....6#pid29066
I have created a new image, on a 32 GB SD card, using "2023-12-29-OpenPlotter-v4-Starting-beta-64bit-img" created by "Raspberry Pi imager" on a Rpi.
On the new image I changed localization settings like Timezone(ETC+1), keyboard (SE), wifi country(SE) and nothing more.
I also updated the system by "update" and "full-upgrade"
The I ran "Signal k Installer" and got the same result as before. Each update attempt, e.g.: "npm GET 200 https://registry.npmjs.org/socket.io.parser", is timed out as before.

Any advices what to test next?

/Håkan

I will try to reproduce that.
Reply
Hi all,
after some years using OP2 then OP3, I would like to follow the evolution and I am testing OpenPlotter 4. My first concern is the disappearance of the Network manager in OpenPlotter menu. I was using the function "add ethernet port to AP" to manage the connection of the Raspberry operating OP to the Tinypilot by eth0 (on IP 10.10.10.167). With this new release, I don't know how to manage it. Did have you some idea to help me? Many thanks.
Eric
Reply
Not sure about ethernet but when I plug my phone into a Pi USB port and set6the phone to share data over USB the Pi creates a connection and shares it automatically. Try just plugging it in and having a look at the networks icon top right maybe?
Reply
Tank you for your help, PaddyB. Connection of my phone over USB is working fine for me too.
Finally, the connection by eth0 is working fine, I had made a stupid mistake in the configuration of Pypilot!
Reply
(2024-03-26, 06:31 PM)Erickalon Wrote: Tank you for your help, PaddyB. Connection of my phone over USB is working fine for me too.
Finally, the connection by eth0 is working fine, I had made a stupid mistake in the configuration of Pypilot!

Cool Cool
Always nice to hear of a happy ending  Big Grin
Reply
(2024-03-26, 11:03 AM)Sailoog Wrote:
(2024-03-26, 10:36 AM)Hakan Wrote: About the SignalK (npm) update issue reported here: https://forum.openmarine.net/showthread....6#pid29066
I have created a new image, on a 32 GB SD card, using "2023-12-29-OpenPlotter-v4-Starting-beta-64bit-img" created by "Raspberry Pi imager" on a Rpi.
On the new image I changed localization settings like Timezone(ETC+1), keyboard (SE), wifi country(SE) and nothing more.
I also updated the system by "update" and "full-upgrade"
The I ran "Signal k Installer" and got the same result as before. Each update attempt, e.g.: "npm GET 200 https://registry.npmjs.org/socket.io.parser", is timed out as before.

Any advices what to test next?

/Håkan

I will try to reproduce that.
On the same RPi5 but a Raspberry image I tried to install SignalK
Method used:
1. In RPi inbound program installer I installed nodejs and npm.
2. sudo npm install -g npm@latest >> Works fine. Some files updated.
3. sudo apt install libnss-mdns avahi-utils libavahi-compat-libdnssd-dev -y >> All was already installed.
4. sudo npm install -g --unsafe-perm signalk-server -y  >> Worked.
5. Then I could setup and start SignalK wo problem

On the Openplotter image:
1. nodejs was installed. npm not, so I selected that and Apply.
2. Didn't worked. The command was "swallowed" but nothing happened. I'd to close the hanged terminal.
3. All deps. was already installed.
4. Didn't worked.
Reply


Forum Jump:


Users browsing this thread: Coyote24, 2 Guest(s)