component compile problem

andypugh wrote:

What is the actual encoding scheme? How many position do you have?
Possibly you have a one-sensor-per-pocket scheme that I have not been aware of previously.

No, hang on

That is exactly what "single" means. So you were right the first time. Which leaves the question of why it wasn't working.

Was the encoding type all that you changed?

You can see the sequence by opening sim->axis->axis
estop-off then turn on and home

Machine-show HAL configuration
Then select the watch tab and add the iocontrol.0 pins

You will see that
T4 sets the tool-prepare pin true, and sets the tool-prep-number to 4
(in the sim tool-prepare is linked direct to tool prepared, so the leds just flash once)
Then on M6 tool-change is set to 1 and the system waits for hal_manualtoolchange to set tool-changed to 1
Then tool-prep-number goes to 0 and tool-number goes to 4.

Do you have T re-mapped for lathe-style tool-changing?

It almost looks like carousel is stuck, and the fact that I don't see a parity pin might indicate that you are not using the latest version. (And the earlier version did have a way to get stuck)

Showing neither fwd nor rev but at the same time not asserting "ready" is a bit suspicious.

There is a HAL parameter which shows where the carousel state machine currently is.

If you don't know about remapping the you probably haven't done it.

It is possible to configure LinuxCNC so that a T0202 command calls a G-code subroutine that does:

G43 H02 (tool offset)
G43.2 H10002 (add wear offset)
M6 T02

This makes LinuxCNC behave a bit more like most lathes, where the M6 command is not needed to cause a tool change.

If your system has such a remap then it would be in the INI file in the [RS274NGC] section. But you would know if you had put it there.

What state is the carousel state machine in?

There is a Weiler lathe in Stuttgart working really well with the carousel component. I know that it works, I have made parts on the lathe.

Skidloaders1 wrote:

carousel.0.state value = 0

That's odd.

github.com/LinuxCNC/linuxcnc/blob/master...s/carousel.comp#L200

It should never be in state 0 if enable is true.

Does the carousel respond to jog buttons? (You can create fake jog buttons with sim_pin )

What is enable connected to? Is that changing state on tool-change?