I found this:

forum.linuxcnc.org/qtpyvcp/58735-probe-b...ing-no-tool-selected
and installed pyside-tools package, it's work! thanks.


Tim

m6 Toolchange by hand, with a fixed toolsetter. I am not sure, but it works fine as long as the tool has not much more length then the tool before. Example: a 4mm mill with a length of 25mm first, then a 6mm mill with 50mm length, bumm joint 2 (z) exceed positive limit, what makes me wonder, the cnc has a z range about 240mm, the workpiece is 45mm high. After the error, w
hen i go to the home position(not homing!), it works.

hello everyone:

I was installed the debian13+linuxcnc2.9.8 ISO image from linuxcnc.org. and installed qtpyvcp and probe basic used method below:
kcjengr.github.io/probe_basic/debian_13_...develop_install.html
but, it can't start 

 

Thank you

Tim

how are you setting the tool lengths?

The download links on the bottom of this page:
linuxcnc.org/downloads/
are a bit misleading. The top links link to bookworm packages, while the lower ones point to trixie.

The downloaded files don't have the release name in them. That confused me because the python versions etc... didn't fit. Took me a while to notice that I had the wrong packet.

If LinuxCNC is running and you have no watchdog bite (red LED on 7I96S)
and halcmd setp hm2_7i96s.0.ssr.00.out-00 true does not activate SSR0's LED,
Then its likely that the 7I96S has been damaged.

Do any SSR outputs work?

I'm aware of it. I have one error driving me nuts, i think it has nothing to do with probe basic, maybe you have an idea. The exceed joint 2 (it is z) positive error. Read all i could find about it, nothing helped. I don't see any reason for this error, it is always plenty of room to the positive limit, then if i go to the home position, it is working. In a bigger cnc job, this often stops the job when changing to a longer tool and i can start over. Very annoying.
Michael

I have spindle CW and CCW signals connected to out-04 and out-05. Both works fine.

I want control spindle water cooling with relay and Mesa output. I have connected relay to PB3 pins 13 and 14. When I try to control the relay, nothing happens and Mesa output led not switch on.
I bought cnc router used, so I'm not sure, what Mesa configuration I have. I have read Mesa's pinout and it shows HOSTMOT2 and I can find line
TB3-13,14              11   IOPort       SSR              0        Out-00          (Out)
If I try to control output by command "halcmd setp hm2_7i96s.0.ssr.00.out-00 true" and read state by command "halcmd show pin hm2_7i96s.0.ssr.00.out-00" state changed from false to true. Still, output led not lights up and relay not change the state.
I'm totally stucked with this and have no idea what could be wrong.
 

Hallo Martin

I am Otto, I also got a Knuth Mark Super CNC - Busy Trying to get running

I am battling throug a Re-install today of gplus 450

Just a Question - After Sorting out You Gplus 450 - Is It Stable and Working Now ??
My machine Original was windows 2000 - previous owner Installed Windows XP SP3 Buils 2600
(What are You Running - Windows Version ??)


Wishing You a Good Day

Regards Otto from Cape Town

 

It could work, after lots of testing, I think the noise papagno is experiencing is mostly caused by the servo thread spiking above 1ms, so widening the cycle time could certainly help.
The main reason why Debian 10 does not grind in his case, is mostly because Debian 10 with kernel 4.19 gets lower latency, and this is pretty universal IMO, Debian 13 Kernel 6.12 has overall worse latency, although with system setup tooling that you can get from Rodw, the latency can be improved a lot.
There is only one slight latency regression with the new linuxcnc-ethercat, the modulo operation that I currently must use to do phasing is causing slightly more latency on the servo-thread, and I want to fix that, I am preparing patches to modify Linuxcnc to expose a function to allow proper native phasing, so that I can lighten up linuxcnc-ethercat to match the older performance for both positive and negative refClockSyncCycles modes. Previously I was undecided if going that path, or using Sascha Ittner method/hack of moving ecrt_master_application_time out of lcec_main, but I found that Sascha's hack causes issues with papagno's hardware, I tried this with built binaries from Sittner repo, with refClockSyncCycles -1 nothing would move, therefore I am now convinced the proper path is to have a native linuxcnc phasing function, this will require updating both linuxcnc, and rebuilding linuxcnc-ethercat against the new linuxcnc-dev headers, hopefully the patches will be ready and merged soon, will try to keep you guys updated on the progress here, I know there are people following in the background

Yes I didn't update qtdragon_hd yet. I didn't realize that is what you were using.

Could you explain what this means? It creates and uses the ~/nativecam directory. It requires the correct SUBROUTINE_PATH in your LinuxCNC INI file to be fully functional. I've created some programs, but they don't run. I think there are problems with OWord. Axis doesn't show any errors, but when I run the code generated by ncam in QTDragon, it says it can't find the macros or OWord.

Quite a few people have used 500 Hz servo thread instead of normal 1000 Hz on Raspberry Pi etc so I wonder how much of a difference it really makes? Ethercat would still be doing its thing internally. You'd have to test.