M19 and spindle-index-enable issues

Constantly forcing index-enable low would explain the issue with G33.1 in the post above:
forum.linuxcnc.org/10-advanced-configura...sues?start=20#282461

Have you tried using spindle synchronized motion (eg g33 or g33.1)?

Just so we are on the same page here is my version:
 

What makes me wonder is why  constantly forcing index-enable low does not cause a problem for you.
 
You are right. I haven't used G33.1 yet. Will test it soon. 
But from the looks of it, this is not easily solveable --> need to disconnect the index somehow...

EDIT: Could we write a switch component that passes the signal in both directions (similar to mux2 but bidirectional... ) ?

EDIT2: The easiest solution for this is to probably just install a optical sensor as a second index signal... and then use this for indexing in M19 or for G33.1 ?

the index-enable pin is of type 'io' which _is_ bidirectional. All you need to do is move the line 'index-enable = 0; ' inside the 'if (enable)' block as in my version (or possibly just remove it as the user in the post I linked above.

Thanks for that.

Will test it this weekend.

Dave

As to why adding 16 to the mode doesn't work...

I guess that the problem comes if the orient.0.mode pin is connected to spindle.N.orient-mode, I didn't realise that the P number had a limit check on it.

If it is controlled by a "setp" in the HAL then it should be fine (with the spindle.N.orient-mode pin left unconnected)

That means that you can't change the mode with the P command in M19. I don't know if that is really a problem, though?