Retrofitting a 1986 Maho MH400E

Thanks a lot for the reply! I sent you a connection request since I guess that's how we can exchange PMs on the forum.

It would be really nice to use the control panel and/or pendant from the Philips, though I don't have any idea if that's really a good idea on the LinuxCNC front. I like how it has all the necessary stuff as discrete buttons and you can do a lot with the pendant in hand (which you actually have to since it's a tool room machine). By comparison, the modern pendants I see on sale on ebay etc. seem rather limited.

One thing that's a definite "must-preserve" function is a physical tool release button that can't be pressed by accident.

I have only read the available UIs wiki briefly so there's a lot of digging I still need to do.

Glemigobles wrote: One thing that's a definite "must-preserve" function is a physical tool release button that can't be pressed by accident.

I would interlock the tool release switch in HAL, so that the spindle has to be not turning and the machine door has to be open.

(and even with those interlocks I once managed to drop the Renishaw probe out onto the bed)

This is a manual tool change machine, with hydraulic kick out of the 40 Taper tooling. The MH400E has no interlocks on the splash guarding. As a tool room machine, it will often be necessary to remove guards to fit outsized work.

I currently only have the tool release pinned to a front panel button, without any software interlock, so I could test stuff. You guys just reminded me that I was intending to look at the schematic to see if MAHO had implemented a hardware inhibit on the tool release if the hardware spindle_stopped is not active.

...Just checked, looks like there is no hardware inhibit, so I'll have to do a software inhibit in the HAL.

I haven't implemented the tool changing set up yet. I was going to do it like this...


Andy, how did you implement the tool release inhibit in your HAL? I have the physical input "Spindle_Stopped" coming in, which is currectly netted into the gearbox.comp as an inhibit for the gear change. As it is an input, I am allowed to reuse that already netted signal as an inhibit for the toolchange aren't I?


We already discussed using the original Phillips keyboard (can't find that thread). As I understand it, you can not net buttons from a single keyboard to both HAL functions and to user space keystrokes.
forum.linuxcnc.org/10-advanced-configura...ace-component#114374
Given Gmoccapy, I really dont think there is must benefit trying to keep the Phillips keyboard other than nostalgia.

The MAHO pendant doesn't have a jog wheel. I'd have though that is the single most attactive feature on a pendant. Mine will have E-Stop, Tool release, a 4 way rotary switch for jog axis selection, another 4 way rotary switch for jog increment, and a jog wheel. I think I'll also add an external connector to the pendant to plug in a touch probe or tool height setter. Since the MAHO is so small, all other functions are on the touch screen or the user panel buttons, and thus within easy reach.

Mark

Hi Mark,

ive done the tool change inhibit with a and2:

addf and2.0 servo-thread

net wzloesen <= hm2_5i25.0.7i77.0.0.input-19 and2.0.in1
net toolrelease and2.0.out => hm2_5i25.0.7i77.0.0.output-02

under the part # ---manual tool change signals---
i added the and2.0in0 to the following line:

hal_manualtoolchange.change and2.0.in0

this way, the tool release is only possible if the machine is waiting for tool change, so the spindle is not moving at this moment.

Thanks Bernd, how do change a tool if there is no program running, does the Gmoccapy tool change button activate this pin? For example if you are just setting up and want to mount a touch probe?
Mark

RotarySMP wrote: Andy, how did you implement the tool release inhibit in your HAL? I have the physical input "Spindle_Stopped" coming in, which is currectly netted into the gearbox.comp as an inhibit for the gear change. As it is an input, I am allowed to reuse that already netted signal as an inhibit for the toolchange aren't I?

Looking through my configs, I seem to have written a specific HAL component for the job.

forum.linuxcnc.org/49-basic-configuratio...indle?start=10#26750

But note that the command to compile and install is now sudo halcompile.... rather than sudo comp....