Advanced Search

I keep meaning to write a documentation section about toolchangers, as they are a frequent cause of problems, but despite being the author of the carousel component, I don't actually have a toolchanger on my own machines.

This would be a complete bodge, but what happens if you just double the pocket number before sending it to the carousel component?

Can you describe exactly what feedback pins you have from the toolchanger hardware, and how they behave during a change?

I've looked again at the probe basic sim options...

Firstly, when I launch linuxcnc and the configuration selector comes up, under Sample Configurations > sim there are entries for other guis but none for probe basic. (It seems like that is where I should find the sim).

Instead under My Configurations there is:
probe_basic
> pb_required_ini_settings
> probe_basic

I think the last one is what you are referring to as the sim.

(I also have the probe_basic config I've been trying to get working but saved under a different name).

When I run that thing we are calling the "sim" it shows me the probe_basic screen and gives no errors. On the main page I can move the virtual spindle with the jog buttons.

However, I can't load a tool onto the spindle and all of the probe operations are greyed out.

Edit: I deleted the pb_required_ini_settings file and that option disapeared from the configuration selector. I also managed to load the probe into the spindle in the sim (which stopped the the probe operations being greyed out). However probe operations failed due to not hiting anything before the maximum distance. (which I guess is expected because it is a sim)?

So, I think the sim is working. Am I supposed to test more than this? If so, what?

I would be curious to see if the problem also exists with the v2 macros, but I don't know if they even work at all on 2.9 (it will depend on the Linux version more than the LinuxCNC version I think)

This feels like a problem with the embedded tab handling in the GUI rather than directly with the lathe macros, though it is entirely possible that, through ignorance, I am doing something wrong in the handler code.

Keyboard jogging issue
www.forum.linuxcnc.org/38-general-linuxc...elocity-fluctuations

The logic looks fairly simple, and is here:
github.com/LinuxCNC/linuxcnc/blob/2.9/sr...otion/control.c#L716

That only fails if "if (emcmotStatus->probing) {" (line 691) is false.

The confusion here is that I don't see any change in state in your motion.probe-in channel, it doesn't actually appear to be bouncing (or maybe only not in the plotted example?)

I don't know for sure that "SET_MOTION_ERROR_FLAG(1);" (line 726)drives motion.coord-error but it might be worth plotting that too.