Retrofitting a 1986 Maho MH400E

I haven’t study in depth those drawings so I can’t understand 100%. Today after work I will study them so I can fallow your logic.

Sorry for my poor description. Hopefully a picture helps. This is the part I meant. When I modified MAHO schematic sheet 12, I just copied the existing wiring from the Phillips, where there are these "Vorschubfreigabe" inputs back into the I/O board.


It is not clear to me what logic generates this "Axis enabled" signal within the relay board, but I would guess it is the NC Ready chain.

As far as I can see, the Indramat has no output of "drives are enabled". The only thing it gives is "Indramat ready" which is hardwired into the NC Ready chain.



There is no point wasting three input pins telling LinuxCNC 3x the same information. If we feed something back here, do we need to feeback that "INDRAMAT Ready" signal to LinuxCNC? . If we don't, a failed indramat would break the "NC-READY" chain, but there is nothing informing LinuxCNC that the drive stopped, other then lack of motion or following errors.

Hello, I have studied the drawings and if I understand correctly the controller doesn’t sense the estop. The estop exist only on wire. The question is not were to get the servo enable back to controller, but how to sense that the estop has depressed and everything is ready for the start button.
John

Also if we need to deactivate the servos by pressing agent the start button then we needs to change the wiring a lot. The manufacturer have put a lot of effort to let the control off the estop and activate to relays and wires, for reliability and safety reasons probably. It is wise not to change that.
We can connect a 110 volt relay after the s1 estop and feed a contact to LinuxCnc so the estop on the monitor light on when the hard button estop releases. And press the estop to deactivate the servo.
What is your opinion?
John

Hi John,

I agree that we shouldn't change the E-Stop chain. [edit] removed incorrect signal path.

Today I lobotomised my MAHO.




Mark

When you press estop the 7k1 goes off, but when you release the estop then the 7k1 is not becomes on again, you have to press start. So the 7k1 is not reflect the actual state of estop button
John

Good point. However I was thinking some more about this last night, and thinking about the standard wiring of E-Stop sense as MAHO did it.



E-Stop deenergises that whole 24V rail.


So we have been overthinking it. It is correct on my revised sheet 12, we just need to feed the E-Stop signal on 28x2-4 into the LinuxCNC.
Mark

So we take this not-aus and feed it to 7i77 and use this to energize <estop reliese> and <drive enable> on in linux?
John

I still want to split E-Stop from drive enable. So the NOT-AUS signal will be fed into the 7i77 for E-Stop release, but I ordered a 24V rail mount relay yesterday, and will put that in the drive enable circuit as you drew in this post:
forum.linuxcnc.org/12-milling/33035-retr...h400e?start=50#99472
Mark

So to start the machine first we release the estop (in the screen nothing happens at this stage) than we keep press the hard button next to estop icon on Gmoccapy (wired to 3sh1) until the machine (and LinuxCnc) exits from estop and after this, we press the drive enable button and the servos activates.
This is very attractive idea but the machine wil nod get out of estop because the 7A1 (indramat ready) is not going to energize and the 19k1 is not going to energize either, so after we release the button the machine will deactivate again.
John