Touch Plate Explanation please

In cases like this it is often useful to start your config from the terminal. So open a terminal window and type (make sure the path is correct for your system) and then see if there are any errors in the terminal window:
$ linuxcnc linuxcnc/configs/Router/Router.ini

So this way, one thing I found is this:
Looks like you edited your file with something else than a plain text editor.

So open "custom_postgui.hal" up in gedit and choose Save As end then for "Line Ending" at the bottom of the window :

Then:
You are loading to classicladders. I'm not even sure that is allowed but maybe its ok. custom.clp doesn't load for me at all.
So may be try to change
loadusr classicladder --nogui custom.clp
to
loadusr classicladder custom.clp
as this will load a window with the ladder gui so you can see what is happening when you try stuff.

[edit]
looks like this:

Ok your path is different:
Go to ~/linuxcnc/configs/Router

type ls and you should see all the files just like in your screenshot.

then try
and that should start your machine config.

[edit]
As for what you're seeing:

"CLinB0" is this in your custom_postgui.hal : net remote-z-axis-touchoff classicladder.0.in-00 <= pyvcp.z-axis-touchoff
"CLinB1" is: net mode halui.mode.is-mdi => classicladder.0.in-01
"CLinB2" is: #net in_pos motion.motion-inpos => classicladder.0.in-02 (so this will never turn to true because it's commented out!)
"CLoutB0" is: net z-touchoff classicladder.0.out-00 => halui.mdi-command-00
"CLoutB1" is: net z-zero classicladder.0.out-01 => halui.mdi-command-01
"CLoutB2" is: #net rapid-away classicladder.0.out-02 => halui.mdi-command-02 (which is also commented out for some reason)

The whole diagram is fairly easy to understand. Its just like an electric circuit:

-| |- is a normally open switch, so it needs to go TRUE to let the signal pass from left to right.
-|/|- is a normally closed switch, so it needs to be FALSE to let the signal pass from left to right.
-( ) is an output
-(S) means if the signal reaches it all the way from the left side of the window is sets the corresponding output to TRUE
-(R) means if the signal reaches it all the way from the left side of the window it set the corresponding output to FALSE
then you also have some timer blocks that create delays and such.

The nice thing is you can watch what happens as you press the buttons.
Have a look if those lines in your "custom_postgui.hal" should really be commented out (the leading #).

Sounds correct to me.


I guess you have already found this:
linuxcnc.org/docs/html/gcode/g-code.html





Touch_OFF_Button.clp (I deleted the empty rungs so its nice and compact): If you are in MDI mode (CLinB1) and press the button on the screen (CLinB0) it automatically steps through the MDI commands 1,2 and 3 one after the other with short delays in between.






Just for general housekeeping: I would comment out loading that ladder at the bottom in Router.hal as I don't see it doing anything useful. But maybe you know why it is there?

I did observe that LinB1 does not close unless I operate as above?

You mean it does not close unless you do a manual G92.2 first? It should turn on as soon as you enter MDI mode.

Just checked and sure enough just switching to the MDI window does not turn halui.mode-is-mdi pin on. It only turns on after a command has been issued, that is ANY command followed by the enter key.
Now this seems to be a quirk of the axis GUI because in gmoccapy, which I use, halui.mode-is-mdi comes on as soon as I change into the MDI tab in the GUI.