Advanced Search

You cannot run an MDI_COMMAND when the controller is in estop. Try a python hal component that invokes your external program instead:
www.linuxcnc.org/docs/stable/html/hal/halmodule.html

@Endian,

Ever thought about writing components in c code instead of halcompile code?
I bet writing in c will relax your code. You can also ask DeepSeek to write c code, then
compile it with cmake, and you are off.
I have old examples, if interested.

I don't see any memory allocation for multiple instances of the component at the moment.
If you like at threads.c you can see RTAPI... is used for setting up multiple threads.

Okay I got it... But how to customize them to not hard code them ... any ideas which will be readable after some time?

Thank you all...

Thank you mate! Exactly what i was looking for.

As Andy pointed out, those two variables are shared among all instances.It wasn't so easy to just "variable" before the lower lines so you might have to rework that a bit.

I included the pinout file if you want to use it as a starting point for a different configuration.

Note that having all muxed encoders is a little odd as non-muxed encoder show up as 2
encoders each, with only one being useable so the encoders are:

7I89 0..7
7i76 8 (9)
7I78 10 (11)

Aliased encoder in parens

I keep meaning to add the capability of supporting both encoder types
simultaneously to the driver, but there always seems to be something of
higher priority...
 

If you want the coolant on al the time the spindle is on, add:

net spindle-enable => hm2_5i25.0.7i76.0.0.output-02

If you want the normal gcode controlled coolant, add:

net coolant-flood  => hm2_5i25.0.7i76.0.0.output-02

or

net coolant-mist   => hm2_5i25.0.7i76.0.0.output-02


As far as the spindle scaling goes, OUTPUT_SCALE must be 24000
If that does not work, the are errors elsewhere that must be fixed.

What a legend, flashed and looking good now, thank you . 

I'll get on with the hal mods to get the encoder inputs "wired" up and see

[ Damn.  I edited the post to clarify some wording, and now the code blocks are broken.  I'm not going to try to fix them.  :-/  ]

I'd like to run an external program after an e-stop event.  I thought it was going to be easy.

I have the program (which goes into the background, so there's no delay) in M101.  M101 works when I invoke it via MDI.

I have a g-code snippet which invokes M101:
[/code][/code][/code]

I edited the file to switches but no change at all...

I do not know what should be that reason of overflowing datas between components defineted by counts/names

only different component name is helping to split that computing stuff - but it is highly non-efective way to do that

Kieran wrote:

How's the rigidity of the harmonic drive? 

My 4th axis is based on a 32-size HD reducer, and I've not had any problems with stiffness.  It has a 6" faceplate and is on a 1-1/2 riser, so I can swing approximately 8" diameter parts or stock.  Note that the reducer is mounted in a steel frame/housing - not aluminum - to increase rigidity.

I've never machined 8"dia stock, but I have drilled 3"-4" off the rotary centerline.  1/2" drill in mild steel with no torsional deflection noted - at least not enough to cause the hole to be non-perpendicular or out-of-round.

I expect a 40-series reducer would be fine for a 6" or 8" rotary axis... and perhaps 5hp-10hp spindle class machine?  Like a Tormac 1100/1500, VF-2, or Fadal 3016... but not VF-6 unless you baby the rotary axis.  Probably be fine on any 30-taper machine.

I think this is a post with a kinematic for such a lathe configuration:
forum.linuxcnc.org/show-your-stuff/53476...rical-mapping#307444

Good day hivemind.

I've been struggling with getting my mill up and running. It's running from an Mesa 5i25 / 7i76 (par port) controller, Leadshine HBS86H driver / 86HBM80C-1000 motor (closed-loop) at 70VDC; 1000PpR. And a BEST FC300-2.2G-S2-B4 VFD.
Attached is a zip with the config files.
Eventually i got it mostly functioning.
I got my homing to work.
Got my pendant (old XHC HB04) to work and operate the axis/spindle/feed.
I reserved a few inputs to add limit switches (at end of stroke). Might want to add extra past-home limits too to prevent overshoots. Setting the homing sensors to act as home and limit (PNCConf option) just gave errors when running LinuxCNC( can't start, limit switch active or something along those lines).

What is left:
Speed!. we want it....
I have a high speed spindle on a VFD (0-10v input, no feedback (jet?)). 24000rpm@400hz. No problems there.
When i turn the spindle on, the speed on screen reads as 300rpm at 100% and the VFD runs up to it's 400Hz max. Turning down to 50%, the VFD goes to 200hz and 12000RPM. But the screen reeds 150rpm.
The speed bar under the speed and % reeds " 0                0                  6000"
And the "at speed" dot doesn't turn green. I do have that output from the VFD connected to the board.

How do I get the display to show the true RPM?
Can the 0-10v output from the VFD be connected to the 7i76 as speed feedback?
*****************
Next question:
I also have a relay on TB6-output2 to which the spindle coolant pump is wired. How do I get that 'programed' to turn it on when the spindle is running? (and perhaps add a function to the pendent to manually turn it on/off too?).

TIA,
Niels

Hi all,

For info.
The distro is updated to use Debian 13 and linuxcnc scurve + ethercat.
There where some problems to get ethercat running on linuxcnc, these are now solved.

repository.qtpyvcp.com/repo/linux-distro/

The debian-disk.img.7z is to use directly in qemu vm.
The debian-raw.img.7z is to be copied to usb.
 

So nothing i can do against it right now? :/