PnCConf Setup issue with the Spindle

The error in PnCConf (this has been fixed in later versions) is this:

net spindle-vel-cmd-abs => hm2_5i25.0.7i76.0.0.spinout

net spindle-vel-cmd-rpm-abs <= motion.spindle-speed-out-abs

Note the the actual physical HAL pin is unconnected do to a net name error (the missing rpm in the top line)


The ENA and DIR outputs are simple switches.
so for example if your VFD needs a +24V signal to enable, you would wire the ENA signal like this:

+24V --> ENA+ -->ENA- -->VFD Enable input

if your VFD needed a signal to be grounded to enable you would wire the ENA pins like this:

VFD Enable input --> ENA+ --> ENA- --> GND

Your explanation of the switch makes sense now. You indicated a simple switch earlier, but it now makes sense to me. I guess switch means switch. Thank you for your patience.

I am still a bit confused about the spindle error...Not surprising given my history of questions.

I have read the explanation of net in the Basic HAL tutorial, but I don't think I understand well enough to explain what is going on with the net command. Does the net command do the following with the line in question: spindle-vel-cmd-rpm-abs (linuxcnc code signal) is "sent to" the Mesa card analog out.

Are you indicating PnCConf has a error in creating a connection to the intended signal name "spindle-vel-cmd-rpm-abs" since PnCConf creates "spindle-vel-cmd-abs"?

• If this is the case, I assume I should edit my hal file with the correction...net spindle-vel-cmd-rpm-abs => hm2_5i25.0.7i76.0.0.spinout?
• If the above is the case, can I add this command to my custom.hal file? Will it assign it correctly since it is the last connection made to the 7i76...spinout?

Yes (your version of) PnCConf has mis-matched net names so the desired connection
from motion.spindle-speed-out-abs to hm2_5i25.0.7i76.0.0.spinout is not made
(Note that net names are completely arbitrary, they are really just a wire or signal names )
so

net blue_wire => hm2_5i25.0.7i76.0.0.spinout
net blue_wire <= motion.spindle-speed-out-abs

will work

but
net blue_wire => hm2_5i25.0.7i76.0.0.spinout
net red_wire <= motion.spindle-speed-out-abs

is legal but does not connect the desired pins

I changed the .hal file to reflect "net spindle-vel-cmd-rpm-abs => hm2_5i25.0.7i76.0.0.spinout"
I now have the spindle turning in linuxcnc with manual and MDI controls. I also changed my wiring to utilize the switches on the the spindle connector. Works perfectly! Thanks

I also have an encoder (1000ppr, A,B, with index). It shows positional changes and speed inside of PnCConf (Though it is wrong at this point... I will setup the scale later). But, when I use linuxcnc I show no speed when the spindle runs. I assume there is another wrong signal connection. Is this the case when looking at my above hal file?

Thank you.

The measured spindle speed goes through a scale (from RPS to RPM), absolute and low pass filter function, ending up as
the signal spindle-fb-rpm-abs-filtered but this is not connected to anything else in the base hal file. you may have to look at
the gui specific hal file section

Thank you. Grasshopper will give it a shot.