Advanced Search

# Abilitazione PWM: attivo quando lo spindle è "on" (M3/M4)
net spindle-enable motion.spindle-on => hm2_[MESA](BOARD).0.pwmgen.00.enable

# Comando velocità in RPM dal planner
net spindle-speed-cmd-rpm motion.spindle-speed-out => hm2_[MESA](BOARD).0.pwmgen.00.value

I would in addition, check the above signals and pins to try and trace backwards
to find out  why  you don't have PWM enable and value set properly.

How can I perform this kind of verification?
I was able to add the two variables you mentioned into HALShow, but when I start the spindle or run M3 S12000, nothing changes in those values. What am I missing?

No worries, and you are welcomed, always.

happy to help! for what you are trying to do it shouldn't be too difficult. really you just need to map out the motion you will want the tool to make in relation to your tool setter, and build out that code in gcode so you know what it looks like and add in the probing motion where G1 would normally go, then review the rest of the probing routines to see what to do with the probed points captured during motion and write up a small equation to calculate the tools diameter and send it to the tool table diameter column. this is all information available in the docs in the gcodes section.

Hi,

  Is someone actively developing MTConnect support? If someone is working on this, maybe I could join the effort?  My goal would be to establish MTConnect similar to Haas, and perhaps also the MDC support for Q commands. 

P.S. Some of you might remember my previous project: installing LinuxCNC on a Cincinnati 10HC2500 HMC.

Tero

Apologies for Clumsy writing on my part,
I understand the issue and thanks for the clarification Tommy.

Not a missing connection, Andy pointed to a missing 0 :
error showsit should be

Plan is for a closed loop system
Used the pncconf only havent changed anything yet

So far its working now the rest ill have to do by testing 
Thanks for the help again

i have tied 3 times but i now think some of my faults are regarding www.forum.linuxcnc.org/9-installing-linu...cnc-in-november-2025
and so

That link says modbus. also the price is more than 3 full ethercat ac servo kits.

But still neat.

I'm 4200km from vancouver.

Are you intending on using encoder feedback?

If not (and this is an open loop step/dir system), you should not connect
the encoder pins (  like hm2_7i95.0.encoder.00.position ) to the axis feedback
signals (like x-pos-fb )

And vice versa, if you ARE intending to use encoder feedback, you should not connect
the steogen pins (  like hm2_7i95.0.stepgen.00.position ) to the axis feedback
signals (like x-pos-fb )

 

Thanks Andy, I'll go hunting for that missing connection and report back.

ok that worked.
But it gives me a different error now, i do understand what it wants from me but thats it (total beginner here Sorry)

Debug file information:
Note: Using POSIX realtime
./Sindre_Mill.hal:86: Signal 'x-pos-fb' can not add OUT pin 'hm2_7i95.0.encoder.00.position', it already has OUT pin 'hm2_7i95.0.stepgen.00.position-fb'
7346

File is attached
if there is any other file you kneed let me know
Thanks

I posted it ti the gethub, hopefully they can help me get this thing going..

The problem is that the 'imp' python module has been removed from newer versions of python, Code that use it should be ported to use 'importlib' instead.
There have been other reports about this. Since Probe Basic is an external project it might be worth filing this as an issue on their Github page:
github.com/kcjengr/probe_basic/issues