Advanced Search

I will do that most likely on today and inform you about the result.

I remember when i installed Debian 12 last year, i had also the rtai version installed, but maybe i had wrong bios settings at that time and went back to this current installed version (i had a picture of my latency test and and top reads this):

x86-64 on host debian 17.Feb2025
Kernel-release=6.3.0-rt11-linuxcnc
Kernel-version=#2 SMP PREEMPT_RT Mon May1 17:18:20 AEST 2023

So, maybe installing the rtai version will solve the latency spikes. Should i do a fresh install or just download and install the rtai version?

Do not double post, please, it makes it very hard for us to follow what has been already answered. Thank you.
-
That seems like a video signal issue, for sure, so try another HDMI cable if you can, and/or see the RPI forums for what settings you need to have in config for your monitor setup.
-
Just in case that is a RPI3 and you are using the "composite" analog output, see what your monitor can accept, be it PAL or SECAM or NTSC.

I installed the image from the download page and installed it on a RPi 4B and have an issue I can't figure out. I can get in and the image works, but the login screen is at a resolution that the little monitor I have doesn't support and it is skewed. You can make it out and get past this, and then reset the display setting once to the desktop, but if the Pi goes to sleep, or on next boot, the login screen resets the resolution back to the one my monitor can't support. How can I set both the login screen and the main window resolution to a specified setting.

Here is what the login screen looks like:
https://photos.fife.usercontent.google.com/pw/AP1GczOETd3dhYUDRgXHYTnzpp9TKRjkmYnq6D6_pN9r6YUqH3WpGP2bGTfXxA=w1121-h840-s-no?authuser=0 

Thank you!

cmorley fixed it: that NGCGUI_SUBFILE_PATH was only documented under the linuxcnc.org/docs/html/gui/qtvcp-widgets...cp:widgets:qt-ngcgui because, well, that's where it should be since it's only for Qt.

tommylight, thank you very much, but I think it must be able to see it: since in fact I did "ls -al ... " from the maker user, and there it is. And now, it looks like the program is working. That might've been the problem, but just for future google travelers, in my case it was not.

Thanks again!!

   

I would not use classic ladder for this function as it is not real time, but rather use
the "comp" component to compare the analog voltage to your constants.
The "comp" component also has a hysteresis function like a normal switch
so you will not get a noisy signal near the trip point.