Advanced Search

@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

Usually a good idea to share the errors you are getting. Saves people trying to help a lot of time.

machinedude wrote:

the only thing i noticed was that the THCAD-300 seems to be for only scratch start HF machines?

Scratch start has no HF nor HV pilot arc, it needs to be dragged on material to fire.
THCAD 300 would work fine for your plasma (i use them on HF/HV start despite warning all not to do that, it just needs to be wired in the right spot), and so will any THCAD, just get 2 of 1MOhm resistors rated at 2W or 5W and wire one on each arc voltage wire.

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.

Rod  i did some digging and found out that this Machine has been done with THCAD before. the person that did this has some YouTube videos and i found this image on here. this is basically the exact same setup i was going to do minus the THCAD since i was not sure on that part; I watched the videos and in the video he said the THCAD-300 would have been a better choice with this machine. the only thing i noticed was that the THCAD-300 seems to be for only scratch start HF machines? this machine has a 1:1 ratio but has the blow back start so which would be better the THCAD-2 or the HTCAD-300 ?
 

tommylight wrote:

Right click on the bar, choose preferences, then check "auto hide". Works on any task bar.
Also, USB C should work with a USB C to A adapter, but in your case only with USB A 3.n version, not with USB 2 versions.
USB 1, 1.1, 2 use 4 pins, USB 3 uses 9 pins, Type C uses 18 pins, but some are for monitor signals .... so is the USB C used for monitor and touch? If yes, then no adapter works. Cr@p, only recalled this while typing.
 

The instruction pamphlet goes on an on about the virtues of using a full featured USB-C port because no HDMI connection is required, video, touch sound all over that single connection, however Pi does not have USB-C.

The instructions then go on to state if you connect the ports in a particular order that you can get the touch working in tandem with the HDMI port but I have tried all combinations and perhaps this might work on a Windows machine (I doubt it), but looks like I need to find another touchscreen, one that does not rely on a USB-C port for the touch signals.
Thanks