Retrofitting a 1986 Maho MH400E

The Hyd start button SH1 is a dual pole switch, so you just need to wire the second set of contacts to a MESA input pin, and then net that to the Gmoccapy top button, or the equivelent HAL pin if using a different GUI

Note, for Gmoccapy this needs to be in the custom.postgui.hal to work. I also used the SH1 switch when I was trying to work out how to get this to work



net [give it a name] [hm2..bla-bla..input.oX] gmoccapy.v-button-0

Put a block of wood under Z, cause if you drop that down onto the end stop, it will be a PITA to crank it back up.

I tested my X and Y encoders first with an allen key on the end of the ball screws.

I also didn't change the MAHO Estop circuit. My Estop chain has a jumper on the pendant connection, but this will then connect to the Pendant E-Stop once finished.
Mark

Thanks again for bearing with me, I'm a terrible newbie in all this. The switch has three sets of pins, though one set is for the light (which doesn't work anyway). The other connected set has one wire going down into the conduit to the machine and another that's connected to the E-stop. So I assume I just need to wire one pin to one input pin on either Mesa card. I'll test it out.

The wiring of the 3SH1 is on MAHO sheet 07 and 23. It shares a wire with the EStop circuit (152),with the other wire making a circuit to 154. Note that the 1xx series terminals are 110VAC. whereas MAHO's convention for 24VDC are 2XX or 3XX numbers . This why I used 4XX for 5VDC circuits I added, and 5XX for 12VDC .

WARNING - Do not connect those existing terminal 152 or 154 through to your MESA! That HYD start / ESTOP release circuit of the MAHO is 110VAC

The switch is easy to disassemble and the bulb is replaceable. The bulb is powered through the X1/X2 connections.

The unused contacts on that switch 3SH1 are terminals 22 and 23, so if you run a +24VDC wire from 204, through those contacts, and input it to a MESA Input, you will have that second circuit I detailed above. To get things up and running, I'd suggest you just add a couple of ugly wires out the back of the control panel to the electrical cabinet.

A more elegant option is to take a closer look at that cable which the E-Stop wiring is in. It is a 12x0.75mm cable, but only 5 or seven of its wires are used. On my machine, the spares were blanked and there are numbers printed on them, so you can match them up at both ends. Make sure you make notes on your schematics of any changes you make, or you are going to in a bad place in three weeks/months/years when you need to modify, maintain etc.

The wired (in a brutal and ugly fashion ) SH1 button works, in that it's connected to the gmoccapy interface. It either refuses to release the estop when your code for external estop is present, or if I use the software estop hal code from a sample configuration it changes state and allows me to "power on" the machine. I use quotation marks because it doesn't really enable the drives or cause the relay to remain switched after I let go of the button.

This config also has other problems but they are trivial in view of the path to further progress (software estop button changes state each time 3SH1 is pressed, from on to off and back again; it's configured as a not input).

As you mentioned above, there are a few lines of code in your config for starting up the machine (machine-is-on), setting connections between hal pins and the relevant Mesa pins on the 7i84. But I couldn't find anything that would tie the machine-is-on signals to the GUI machine start button. I'm probably missing something again. How is LinuxCNC supposed to know that pressing the power on software button should send a machine-is-on signal through the outputs to the drives? Or do the drives energise when they get power and I wired the 19K2 relay wrong somehow (there are two wires in the terminal you wrote about, but it's still the same terminal)?

My brain is disintegrating. It's only when you start messing around in such a machine when its complexity hits home. Individually, the components are relatively simple and I can understand how they're supposed to work if I put my mind to it, but taken together there's so much stuff that can produce an undesirable outcome it's simply staggering.

That whole start up thing was also a challenge for me.
You are making good progress. That 3SH1 now causes a state change is correct. The start button behavior is correct, in isolation. To make the system work correctly you additional elements.

I wonder why the e-stop_latch is not working for you. It is a hal.comp, so you need to "loadrt" it and "Addf" it.

Following the advice of Nobert, who wrote Gmoccapy, his suggestion is to avoid one huge HAL file, and break up the HAL into smaller, modular hal files.

So in your main HAL Add:
Then make a new file with that name and add:
Once that it done, test it. Pushing 3SH1 should release estop on the MAHO and LinuxCNC, but as soon as you release the button, both should fall back into E-Stop.
Next you need control of the latching relay 19K1.

How is LinuxCNC supposed to know that pressing the power on software button should send a machine-is-on signal through the outputs to the drives?

That is this part.

Get this working, and test your E-Stop before anything else. ,
The following should all drop the machine into E-Stop:
Pushing the mushrooms.
Each of the axis over travel switches.
The LinuxCNC E-Stop
etc.

By the way, I checked yesterday, and have no connection with 7i77 TB5-1, so that is an error in my schematic. I'll need to trace how I wired 19K2, just to make sure.