Advanced Search

I think I will go max to 3 meter
I don’t have a 3D printer.
I could put some pulleys in series to get a better gear ratio.
What ratio would you recommend?

And to see if it's worth to look further, how is the latency with isolcpus=5 ?
If it's good enough, what's in your armbianEnv.txt?
You installed the spi overlay by editing as in:
forum.linuxcnc.org/media/kunena/attachme...k3399-spi-spidev.txt

And installed with: sudo armbian-add-overlay rockchip-rk3399-spi-spidev.dtso

royka wrote:

It is available: packages.debian.org/trixie/arm64/python3.12

Did you try to install with: sudo apt install linuxcnc-uspace ?
Otherwise first: sudo apt install python3.12

I was trying to install linuxcnc using .deb file, thats why I enounter the python 3.12 issue.
however in  your recent image I couldnt enable the spi again, even with changing the spidev status in dtb files to "okay"

You might try out Flex GUI it has a touch screen example and it quite flexible.

 

JT

OP:
Note that it is not advisable to use email addresses as your user name or even to expose them in a post. There are scam bots that search the web for exposed addresses to target.

@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?

Fantastic. Thanks very much. So for anyone else looking, here is a visual.

Maybe it is sending the output to stderr not stdout. This should direct both to the file:

I fixed the formatting.

Maybe you want to file this as an issue or as a pull request on github?

Hi Guys,

I think I found a bug in the probe_routines.py for versa probe. When Trying to probe from outside from 4 sides in the current setup I was not able to make it working. ( I always had to probe very end X+ and Y+ with adequate searching  distance). Not sure if this is happening only for me but but this was pretty anoying because even I found center I couldn't from ceter position run routine again to double check.

Someone might find this helpful i adjusted probe_routines.py file (/usr/lib/python3/dist-packages/qtvcp/widgets/probe_routines.py)
github.com/LinuxCNC/linuxcnc/blob/master...ts/probe_routines.py

line 1089replace with:line 1054replace with:

my understanding so far was the THCAD-2 can be used but you have to add the HV resistor for ir to work and the THCAD-300 does not need the external resistor in my application;

Means not for use with HF/HV pilot arcs.
-
NOT advice:
The thing is it can be used but requires open the plasma source and wiring it at the rectifier output. Any place else risks letting out the magic smoke. I have THCAD 10 and 300 wired to HF start, probably over 10 or 15 of them.

"The 300V version of the THCAD has all input divider resistor on board and can connect directly to the plasma voltage of touch start type torches only."

this was the section of the description on the Mesa site that confused me.

I had also tried, same problem

Maybe add a debug output to the autostart command:

... >> /home/axel/autostart_log.txt