ECMO VMC100 Retrofit with Carousel/Toolchanger

i have only sense 0 and sense 1 linked. sense 0 is index and sense 1 is the sensor on the slotted disc. i use index configuration.

strobe is everytime high. i dont know to what i need it to llink. sense 1 and strobe together?!

The issue is in the hal... i delete the hal with failures ... not that someone use it and wondering...

You might want to insert the carousel in one of these loops.
(depending on the style of the toolchanger)

Often you will have
This is not always the case, though.
The tool-prep handshake is typically used with random toolchangers, where there is a tool swapper. If you need to put away the current tool first, then tol-prep will be looped, and the logic will be in the tool-change handshake.

You should probably toggle "tool changed" from your tool-change ngc file. That ensures that the system stops if there is a failure in the tool change routine.

You can link both sense0 and strobe with something like:

Though I think that strobe defaults to high, so can often be left unconnected.

yes strobe is always high thats why i never connect it. now i hae connect it with sense-01 which is the counter.

the stuff about linking into tool-prep stuff i would done when everything works... but fromm there i am far away.. on the table with switches it works.. on the machine... it shoots over.. or stops in the middle ... cant discribe .. its terrible... thats why i was thinking to debounce via hardware like its original.. original control works flawless.

Maybe the real sensors have a different polarity to your bench test setup?
Halscope should help understand what is going on, if you scope the inputs and the carousel.0.state (with reference to:
github.com/LinuxCNC/linuxcnc/blob/2.9/sr...s/carousel.comp#L309

you mean that i need a rising instead falling edge? or a falling instead a rising?

this i must check... when exact the state change....

Wrong infos! Dont want people to go on the wrong path!

Deleted message because of wrong informations!

I debounce the signals... with a schmitttrigger like from the original controller.

Still issue with state 9.