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.