Advanced Search

Nice! Thanks for sharing.

Thanks for sharing.

Translation

I set the orientation of the spindle with m19, it worked well, but I have a problem that as much as I put the same degree every time, it finds different positions of the spindle, for example I give m19r0 it finds a point and stops, but I do the same command again and it does not find the same point it goes to another point and stops, that is it keeps changing the degree 0 of place, sometimes it does it several times in the same place, out of nowhere it goes to another point and if I do it a few more times it stays there. At that point, out of the blue it changes the point again, can you help?

Translated with DeepL.com (free version)
[/code]

It does not really matter. Each pin has a matching pin ending in -not that is always the inverse of the main pin.
so you can choose which pin you use to set the default position to be on or off.

There have been a few threads about switching a rotary axis to spindle mode and back. Currently there is no standard solution that fits all scenarios.
This might give you an entry point:
forum.linuxcnc.org/26-turning/55148-lath...g-and-milling#319940

Thanks for sharing.

Thanks for sharing.

please post your config folder (compress and attach)

Your issue seems to come from your custom mcodes (M300, M500, M600).
Generally we don't want to have toolchange related stuff run on gcode load and the way to make sure it isn't is to check the 'task' parameter which returns 0 on load and 1 during actual gcode execution:

Hello everyone,
I have installed the Probe Basic Lathe version 2.9.4.

1. The simulation works fine, when I want to change a tool I get a popup window and can confirm the tool number - the tool number in each tab changes without error.

When I install it for the 7i96s configuration, I can open it - turn it on - the stepper motors work in MAN mode - referencing also works, but when I want to change the tool, nothing happens and the system freezes. 
I get the message: can`t issue mid unless machine is on, homed and idle.

2. When I want to use the macros in the conversation tab - change values and start - nothing happens.

How can I fix these problems?

Sounds like something for a custom homing component:
linuxcnc.org/docs/devel/html/man/man9/homecomp.9.html

Yes, indeed. However since the drops seem to be random, I am not sure if it is related.

The manual also states that no frequency measurement is possible if the counter is blocked by the gate, but that in this case the period can be measured regardless.

And further: If an encoder signal is only present at input A/A and the frequency/period is to be measured, the terminal must be set to “Enable FWD count” in CoE 0x8000:03 [} 155].

   

Nice! Thanks for sharing.