Advanced Search

Doesn't even look like the current hal file would run
as there are two different signals connected to
hm2_7i76e.0.7i76.0.0.spinout:

net pdnt.spindle-speed-abs => hm2_7i76e.0.7i76.0.0.spinout
#net spindle-vel-cmd-rps-abs => hm2_7i76e.0.7i76.0.0.spinout
net pdnt.spindle.is-on => hm2_7i76e.0.7i76.0.0.spinena
net spindle-cw => hm2_7i76e.0.7i76.0.0.spindir
net spindle-vel-cmd-rpm-abs <= spindle.0.speed-out-abs => hm2_7i76e.0.7i76.0.0.spinout

I would first get things running in the usual way by adding

net spindle.0.on => hm2_7i76e.0.7i76.0.0.spinena

commenting out

net pdnt.spindle.is-on => hm2_7i76e.0.7i76.0.0.spinena

and uncommenting:

#net spindle-enable             <=  spindle.0.on

When this is working I would look into the pendant spindle control options

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