Advanced Search

github.com/LinuxCNC/linuxcnc/blob/master...cripts/axis.py#L1881

I think it exists in canon, but last time I looked at this canon wasn't availalable in standalone python code. (or I failed to work out how to use it)

However it is available in remap code. So if you remap the S word (spindle start) you could check the extents at that point, add on the tool length, and decide if the spoilboard will be spoiled....

Actually I'd like to know why bash isn't /usr/bin/bash . As far as I'm aware all the build scripts for the image reference/usr/bin/bash and there was no issue when in the qemu environment.

Once again posting your code would help rather than fumbling around in the dark.

Maybe a more-fun project would be to make the 9-axis blending work with LinuxCNC.

github.com/LinuxCNC/linuxcnc/tree/Tormach_9_axis

This was just an experiment to see what happens if you replace the LinuxCNC tp folder with the Tormach one.

I haven't even bothered trying to compile it, the point is to examine all the points of difference by looking at the diff:

github.com/LinuxCNC/linuxcnc/pull/3524

I have configured a hydraulic tailstock on a CNC lathe. It has 2 valves (in/out) and 2 proximity sensors (min/max). I want to use M-codes to control the tailstock, but I can't get M66 to work. M64 and M65 do work properly. I've attached the sensor inputs to motion.digital-in-00 and 01. I can see the signals changing low/high in halshow. But when I try to test this functionality with a small G-code file, it keeps waiting on the M66 line.

It keeps waiting on line M66 P1 L4 Q10. Even if I manually turn the sensor on/off, it doesn't do anything. But when I use this line in MDI, it works without problems. When I use MDI I can see the gmoccapy interface "freeze" when I execute this line. It "unfreezes" when the sensor is operated.

Why doesn't my G-code work?

Elipsoids sounds like a difference in dynamic motion between the X and Y axes. The two probably have different masses, and will have diferent limits.
You may need to reduce the accelerations in the INI to something that both joints can follow. If that makes things circular again then you can maybe look at tuning to improve dynamic resonse, but you will still need to set the accel limits to whatver the slower joint can manage,

Im in the same boat, going to need to tune my a6 servos soon. did you get the tuning software to work? I havnt messed with it much but I couldn't get my win10 desktop to talk to the servo drive. I will have to fire up my laptop, as my desktop now has win11. Im kinda hoping there is an easy way to send parameters to the drives through the linuxcnc computer through the ethercat. I will say I have messed with a Haas VF11 mill, and I was able to move its big y axis ball screw by hand a few degrees. I dont think you can really get rid of all the "mushyness" in a servo.

Does this exist as an alternative plug-in interpreter for LinuxCNC?

LinuxCNC already supports this, though the only alternative that currently exists is called canterp and just passes canonincal commands straight through.

I don't know how much traction you will get with a new G-code dialect, not even well-supported alternatives to G-code like STEP-NC have made much of a dent.

If it's a plug-in interpreter for existing LinuxCNC then I would support it's inclusion in principle.

Are you committed to supporting it for the next 20 years or so?

Sounds interesting project

Will be looking out for build progress etc as this interests me , I have a few machines with old controls , they are no more than fancy plc inside with custom hydraulic servo valve control boards

All travel distances read by from transducers .. so I can see hal and ladder maybe few custom hal comps to drive valves all you need , so a nice gui you can see parameters , live data like injection pressures so can tweak mold run . Load and save part setup is key

Hope you make progress on this

The thing is that true/false has nothing to do with it. I tried 1/0, the result is the same. But I'll try the path to bash.