Advanced Search

Thank you RotarySMP. You certainly are an inspiration!

That's really interesting. I had no idea hal "scripts" are actually Tcl. Thank you for the neta function. I did just quickly test it out and indeed it appears to work.

Why do you say that debugging hal files would be difficult? From where I'm standing, debugging usually starts by checking why one input (or output) is not what its expected to be. The following step is to check what is connected to that input. To do that we can use the "show sig" command, which will then display all pins connected together. So I already see which (other) pin is driving that signal, and the name of the signal has little significance.

Is there some normal use case I'm not thinking about? I'm not saying that named nets are bad, I'm just questioning why there is no inbuilt automatic naming of nets. Is it just that nobody has done it, or is there some more fundamental argument against (supporting) automatic naming of nets?

You might try setting the Z axis velocity the same as the joint 2 velocity (125):

[AXIS_Z]
#MAX_VELOCITY = 25.0
MAX_VELOCITY = 50.0
#MAX_ACCELERATION = 750.0
MAX_ACCELERATION = 1000.0
#MIN_LIMIT = -100.0
#MAX_LIMIT = 0.01
MIN_LIMIT = -100.0
MAX_LIMIT = 100.0

[JOINT_2]
TYPE = LINEAR
HOME = 0.0
FERROR = 50
MIN_FERROR = 50
#MAX_VELOCITY = 25.0
MAX_VELOCITY = 125.0
#MAX_ACCELERATION = 750.0
MAX_ACCELERATION = 1750.0
P = 50.0
I = 0.0
D = 0.0

Is the Y properly calibrated?

What hole processing does Pronest have?
What diameter hole are you cutting?
What material and thickness?

Its suggested to slow cut velocity to about 60% for holes.

Ok, I didnt realize this, because the Probe Basic GUI and the VFD switched the ENA/FWD Output if I give some MDI S command. I can see that in the GUi, my relai clicks, the VFD switches to Run. But the Pin says the truth...

I don't fully understand why this Enable command should come only from the XHC-WHB-04 pendant (set pdnt....) and not from the PB Gui - I would like to enable the spindle over the pendant but more in an OR funktion not only with the pendant.
I have to say that all these spindle commands weren't made by myself but from someone else who wanted to help me out in the past. And I couldn't test it in real life, because my VFD wasn't connected until now.

How should I change the settings so that it works with GUI and pendant? can you give me some hints, please?
Thanks for your support!
Hanno

Looks like someone has started one...
forum.linuxcnc.org/qtvcp/53092-qtdragon-...ortrait-mode-monitor