OpenPlotter 4 roadmap

[SVKitten]

A very impressive start on the road to Pi5 migration.

A couple of early observations in case others who are more knowledgeable can replicate or solve what I'm seeing.

1.  In headless mode the VNC runs really (unusably) slow.  The Pi4 solution of commenting out two lines in the /boot/config.txt file

#dtoverlay=vc4-kms-v3d
#max_framebuffers=2

causes no image to be presented by VNC on the Pi5.

2.  SignalK seems a little unstable.  I have a a pretty KIP dashboard which is solid on the Pi4 (not disconnects/reconnects) but is constantly glitching on the Pi5.



Currently testing on the bench but hope to get the Pi5 connected to some real data, afloat later this week.

1. 
Are you using Wayland or X11 server? and client?
I am using RealVNC Viewer 7.8.0 client in Ubuntu and works really well for both Wayland and X11 servers.
You should not edit /boot/config.txt at all.

2.
No problem here. Try real data and report please.

Using the headless image linked from the top of this thread.  Works fine through VNC with an HDMI plugged in but not when properly headless.

Using RealVNC on WIn11 v6.2 so I can update that. 

Pi5 using X11 as default in the image.  Agree on the config.txt but it did cure the same problem on the Pi4.

So it seems that Chromium is the cause of the slow response of SignalK in headless mode.  Firefox runs just fine.

Will keep testing and try to iron out the wrinkles.

An update on progress with the headless image I've been using from 24/12/2023 on the Pi5.  

1.  My issue with an apparently glitchy SignalK was that the Security, Setting,  Remember Me timeout was set to 3 minutes.  My Pi4 install was set to 1d.  Changing this on the Pi5 cures the disconnect/reconnect problem.  Simple!

2.  In common with other VNC users, I had problems with Pi5 hardware acceleration and window sizing when no monitor was connected to the HDMI port.  
The solutions proposed by others are to either use a "dummy" HDMI plug or edit the /boot/cmdline.txt file by adding  video=HDMI-A-1:1920x1080@60D  to the end of the text.  
The latter worked for me with a perfect VNC connection each time.  Both Chrome with acceleration enabled and OpenCPN with acceleration ticked work great with not HDMI monitor connected.

Currently connected to:
  - WiFi GPS uBlox M10 via an ESP32 running SensESP. No issues
  - WiFi connected NMEA2000 gateway, Sailor Hat firmware on dev ESP.  No issues on the bench but need to connect on the boat with many more live inputs.
  - OpenCPN route data via UDP.  No issues

Have been doing some very rough and ready power consumption observations between Pi4 & 5.  The Pi5 looks very favourable as it is barely ticking over unless panning/zooming which it does really quickly then settles down to a very low idle.  I hope to borrow a current logging power supply and conduct some more definitive measurements.

Had a lovely short sail on Saturday but given the pressure of daylight didn't get the Pi5 connected.  I hope to try this weekend with a two-day trip on the Solent.  Not much wind forecast so a fine time to fiddle with the Pi5 in the warm, below.

Thanks to all for the ongoing work to make this a world-class solution for leisure boating.  I hope my stumbling progress helps others.