josephnfoley
New member
I have my spindle VFD alarm output connected to a masso input and configured as "Spindle Motor Alarm". When there is a fault with the VFD such as power failure this triggers the alarm in masso which feed holds the running program immediately. There are two issues I suggest need to me resolved.
One - The spindle fault only triggers a feed hold on the rising edge, that is to say it will halt the program When the alarm occurrs but it does Not prevent a new program from being started. If there is a fault on the VFD Before the program is started, Masso ignores the fault and begins the cycle. During my tests the machine would have plunged the stationary cutter into the work had I not manually stopped it.
Two - This is of lesser importance however the only way to reset the motor fault in masso is to home the machine, I would suggest to change this so that it can be reset by cycling the E-Stop. The E-Stop cycle can be configured to require a homing after if this is a desired requirement however in my case I would prefer to simply cycle the E-Stop and continue with the job (obviously having rectified the issue. I suggest that only hard limits or homing switch activations should require a re-homing after and any other alarms related to the spindle etc should be reset by E-Stop cycling. (For clarity, when I say to cycle the E-Stop I mean to press the E-Stop and release it again as you would on initial startup).
I look forward to hearing peoples' thoughts on this.
One - The spindle fault only triggers a feed hold on the rising edge, that is to say it will halt the program When the alarm occurrs but it does Not prevent a new program from being started. If there is a fault on the VFD Before the program is started, Masso ignores the fault and begins the cycle. During my tests the machine would have plunged the stationary cutter into the work had I not manually stopped it.
Two - This is of lesser importance however the only way to reset the motor fault in masso is to home the machine, I would suggest to change this so that it can be reset by cycling the E-Stop. The E-Stop cycle can be configured to require a homing after if this is a desired requirement however in my case I would prefer to simply cycle the E-Stop and continue with the job (obviously having rectified the issue. I suggest that only hard limits or homing switch activations should require a re-homing after and any other alarms related to the spindle etc should be reset by E-Stop cycling. (For clarity, when I say to cycle the E-Stop I mean to press the E-Stop and release it again as you would on initial startup).
I look forward to hearing peoples' thoughts on this.
