NaN

[NaN]

Hi @Britgirl, thanks for the feedback!
I just double checked, the Raspberry Pi OS seems to be set to X11 mode by default (I tried to change it and it was already set up like this).

The magic keyboard is directly connected to the iPad where the NoMachine client runs (it is built into the cover of the iPad). When connecting via a NoMachine Windows client I initially got the same effect, but when activating “grab the keyboard” the modified keys work in FreeCAD – so it is a solution for Windows clients indeed!
Unfortunately that “grab the keyboard” option doesn’t seem to be available in the iPad client on first sight(?)
Strange thing is: I can type inside applications on the remote Raspberry Pi and even use Shift to e.g. generate capital letters, press Ctrl+C/V for copy and paste etc. Just Shift+mouse move or Ctrl or Alt + mouse move don’t seem to be supported. Could it be that NoMachine doesn’t transfer the modifier keys like Shift/Ctrl/Alt per se but only combinations as soon as another non-modifier key is pressed when not in “grab the keyboard” mode? That would explain it.
When connecting any keyboard directly to the Rasperry Pi the modifier keys also work as expected in FreeCAD.

P.S.: Unexpectedly 3D benchmark results are a lot better with the default [Removed] server than with NoMachine. (E.g. 3dmark2 results are < 100 for NoMachine and ~800 for [removed].) Subjectively FreeCAD works equally smooth for my simple models with both solutions, so I will likely continue to use NoMachine, which offers more options. Might be an indicator that there is room for improvement though 🙂

P.P.S.: Got rid of the power warning (and black screen with  [removed]) when powering the Raspberry Pi from the iPad via USB cable (which is a neat mobile setup that extends the iPad with full Linux capabilities). The solution was to downclock and undervolt the Raspberry Pi.
Perhaps one can get away with less downclocking (I essentially halfed the max frequencies) – just wanted to verify that I am turning on the right knob and that is conceptually solves the problem. FreeCAD is still fast enough in that setting though, so might leave it like this. Less power draw is also good for battery.
People who already have a Raspberry Pi 4 and use it solely for their iPads probably don’t have to upgrade to a RPi 5. If one buys a new RPi anyways one can also get the Pi5 though. When downclocked for use as “co-processor” on the iPad it is still at least not slower than the Pi4. And it can be clocked up when a power plug outlet is within reach.

Settings to downclock and undervolt the RPi in /boot/config.txt:
# Tell the DVFS algorithm to increase voltage by this amount (in µV; default 0).
over_voltage_delta=-10000

# Set the Arm A76 core frequency (in MHz; default 2400).
arm_freq=1200

# Set the VideoCore VII core frequency (in MHz; default 800).
gpu_freq=400

[NaN]

Regarding the WaylandModes key – this was probably spurious correlation. I changed that key and a system update was running in the background. After reboot NoMachine worked, so I attributed it to the WaylandModes key change.

But my guess now is that the system update has changed from Wayland to X11 as default. Have manually switched back to Wayland now and tried all three WaylandModes options – without success. So X11 seems to be the way to go for now (and then the value of WaylandModes doesn’t matter, for obvious reasons).

So good news might be that the newest Raspberry Pi OS might be configured right for NoMachine out of the box – at least I didn’t manually change to X11 at any time. (Well, I installed various libraries and dev tools, including all the stuff needed to compile the latest FreeCAD version – perhaps that has pulled some package that led to a config change?)

When getting the 54 error a first step might be to do a “sudo apt update && sudo apt upgrade” first, then reboot and then if it still doesn’t work check the first posting of Britgirl with the instructions to disable Wayland in case it is still enabled after that.

[NaN]

After changing WaylandModes egl,drm,compositor

to

WaylandModes egl,compositor,drm

in /etc/NX/etc, I don‘t get this error anymore and the connection at least starts.

But I have two other problems related to keyboard:
First, the Magic Keyboard doesn‘t work when I apply any changes to the settings during the startup of the session (e.g. set a custom resolution etc.) Only if I set everything up and click „do not ask again“, so the session starts without any questions asked it seems to work.

Even then I have the problem that in FreeCAD the Shift, Control and Option keys are not detected in Touchpad mode: Usually when setting the input scheme to touchpad one can move the design by pressing Shift at the same time as moving the mouse (no mouse button has to be clicked). And when pressing Option it should rotate the view.
One can use keyboard commands (0,1,2 etc.) to change the view to front/back/left/right etc. – but often one needs more fine grained control.

(With [removed] as viewer and the onboard [removed] server turned on all this works without problems (including Touchpad mode in FreeCAD). There I have the problem that the screen turns completely black once I start FreeCAD when I power the Raspberry PI 5 from the iPad. (It works when using an external power supply). Perhaps the power consumption gets too high once the GPU jumps in? NoMachine provides more fps for e.g. video streaming though, so if it would work nicely it would be preferrable to [removed].)

Any ideas how I could get the control keys to work in FreeCAD?

P.S.: Using a German layout on the Raspberry Pi. But the Shift/Control etc. keys are at the same position as for the US layout.

[Author]

Posts