Advanced Search

In a terminal, what does
xrandr
Return for available resolutions?

Hi everyone!

i'm quite new to linuxcnc and have some basic knowledge about linux, i don't want to compile a kernel and that stuff, installing specific packages are nit a problem...

at the moment i'm using a raspi 5 image from linuxcnc download page.
I have some resolution problems with my 7" touchpad, it loads the one and only available resolution 1920x...
i would like to have another resolution, my problem is that the "normal" things for raspi do not worl with debian image.

2 Questions:
- how do i do that with the linuxcnc debian image ?
- should i switch to the image provided here with raspios ?

i'm using the raspi together witth mesa ethernet card

thanks a lot

Lars

royka wrote:

Alright, I assumed you would have one since you have an rpi image builder. But likely it uses a prebuild from Debian that seems to be patched already.

Yes, I built the Pi images for Linuxcnc you find on the downloads page. I shared my repo for the builder on this thread earlier. Bear in mind the pi5 was released just after we released Linuxcnc 2.91 and at the time pi5 support was patchy in the upstream builder. I've since updated the builder and it has been tested on the Pi5 and the shortcomings are reported to be gone.

We actually build the kernel .deb from the official Raspberry pi kernel repo and wrap Debian around it and build a compressed image. The 6.12  kernel should be supported by the builder. You should give it a go. As its cross compiled, building the kernel will be quicker than  it can ever be on a Pi and the kernel as well as an optional img (which we compress) is built.

probably possible, here are a few rpi/ i2c driver samples i have saved 

github.com/bosston88/LinuxCNCRPi/blob/ma...hive/i2c%20example.c
github.com/bosston88/LinuxCNCRPi/blob/master/mcp3421.c
github.com/bosston88/LinuxCNCRPi/blob/master/si7021.c
github.com/thgerner/hal_mcp23017

royka wrote:

@rodw Can you confirm that it's the same with the Raspberry or is that kernel source already patched?
 

Sorry, I have no Idea. I don't have a Pi5.
Did you find the code Linuxcnc uses for this check in Git?
 

Can you please try this later version of the linuxcnc image
drive.google.com/file/d/16xQfd_zXuXXKXqO...IY0/view?usp=sharing
I believe the screen issues are solved because the underlying Pi code had some fixes

did you found a way to set resolution?

thanks in advacnce

tommylight wrote:

Out of curiosity, how much is a RPI and a good touchscreen these days?
Wondering as i got a Lenovo X1 Carbon Yoga for 120 and a Lenovo Yoga Y370 for 220, bot work for LinuxCNC with Mesa, both have 120Hz touchscreens, very high quality ones, very good keyboards, and both do over 4-6 hours on batteries.

RaspberryPi was $50 locally, the touchscreens $80-100ish Canadian pesos from Amazon. So a shade > US$100 for both. I can't vouch for the "good" WRT reliability the resolution/sharpness is decent not ipad quality but quite acceptable for a CNC machine.

@rodw Can you confirm that it's the same with the Raspberry or is that kernel source already patched?

I noticed that the patch only works when VMCORE_INFO=y which gets selected by:
 - CRASH_DUMP [=y] && ARCH_SUPPORTS_CRASH_DUMP [=y] && KEXEC_CORE [=y] 
 - PROC_KCORE [=y] && PROC_FS [=y] && MMU [=y]

Is really necessary for LinuxCNC to check that /sys/kernel/realtime or will checking for "PREEMPT_RT" in uname -v be enough?

No idea if there is a driver for I2C in LinuxCNC, maybe searching on github project page would show if there is anything about it there.

I'm not sure about axis, but I think it's compatible with most resolutions, but if you're able to find a 1920x1080 display you'll have more choice of user interfaces. For a smoother experience a Raspberry Pi 5 is a better choice.

I'm looking for a suitable small 7-10" touchscreen display for use with LinuxCNC (lor a lathe). I plan to uses a RaspberryPI 4 that has a HDMI interface. The display will be positioned so that my eyes will be quite close ~12" from the display.

This one is cheap enough not sure if 1024x600 is compatible with axis?
www.amazon.ca/gp/product/B0CPM15T7H/ref=...o00_s00?ie=UTF8&th=1

or this one; 1920x1200

www.amazon.ca/Wstirhy-Portable-Kickstand...y%2Caps%2C160&sr=8-9


I have read there are some compatibility issues with some displays, so if anyone can recommend a display that is known to work well, please share the details.

Thanks

I see there are previous threads about this, but things change with time and releases, so better to ask then chase my tail.

I previously setup LinuxCNC - Axis on a desktop PC for my mill, works great now I want to do the same for my lathe using a RaspberryPi4 Model B (4GB RAM, 32GB SD)

How do I go about this?  Some form of instructions would be very helpful.
Link to whatever version I should use?
Does the install prompt what type of machine this will be used (Mill, lathe etc)?
I ordered a A MESA 7i96S, not sure when it will get here.

Any helpful hints are welcome.

Thanks in advance.


 

Hello #MyFirstPostHere,I am trying to attach a BME280 sensor to a Raspberry Pi 4B to monitor environmental variables (temperature, pressure, and humidity). The sensor is connected to the 3.3V, GND, GPIO2, and GPIO3 pins. It works flawlessly when running Raspbian OS (64-bit), and I can retrieve readings via the terminal.However, when trying to use it with LinuxCNC, I encountered multiple errors.Upon checking the I2C buses with the command, I foundand, but I was expecting, as seen in Raspbian OS.I was wondering if there is a solution for this? Is it possible to get this sensor working on LinuxCNC?Please feel free to ask for any additional information.

I was typing up a post to ask for help getting LinuxCNC 2.9.2 running on a Raspberry Pi 4 B attached to a Raspberry Pi 7 inch Touch Display, when I finally figured out the solution. Thought I'd still make the post for helping others or possibly even future me if I have to rebuild this system one day.

The Pi Touch uses DSI for connecting to a Raspberry Pi and seems LinuxCNC doesn't have the required settings enabled in the config.txt by default. Not really a surprise as its probably an unusual pairing of hardware and OS.

The solution was adding the below text to config.txt