Is it possible to pull a spindle fault input into MASSO? The same as XYZ faults. I almost killed things when i took a deep cut and overloaded the spindle, which turned off. I was able to manually stop the MASSO, but would have been quicker to take the fault output from the spindle driver directly.
Spindle fault input?
- Thread starter patchlead
- Start date
So do you have a fault/alarm output on the spindle drive?
If so then yes we can add spindle alarm input to the MASSO software just like the axis drive alarm inputs.
If so then yes we can add spindle alarm input to the MASSO software just like the axis drive alarm inputs.
Ok then we can add this to the MASSO, I have added your request to our list.
Also does your drive have an output for either 0-10v or 0-20ma for spindle load, we were also thinking to add this to the MASSO software so that you can see a bar on the screen with spindle load.
Also does your drive have an output for either 0-10v or 0-20ma for spindle load, we were also thinking to add this to the MASSO software so that you can see a bar on the screen with spindle load.
Ok, I have checked with the team, we will add the spindle alarm input to the MASSO in the next few days and will email you the software for testing at your end.
If you are running a gcode program then any of those alarms will put the controller in feedhold. please check again with a running gcode file.
We have added the spindle alarm input (see below) and have released the software (v3.31beta) as the guys were doing some work on the alarms logic. Regarding your question that the motion was not stopping on alarms, I have confirmed and it was disabled for some tests and has now been enabled in this version again.
Hope this helps resolve your issue with spindle overloading, please give it a try and let us know if it works as per your requirments.
Hope this helps resolve your issue with spindle overloading, please give it a try and let us know if it works as per your requirments.
V3.31 installed findings as follows.
Overall thanks.
I'm not going into the ramping debate here, but if the fault could say active, if the input is still active through a homing sequence, I think that will sort this input out nicely.
- Spindle Fault activation will cause manual entered G1, G0 hauls the spindle and XYZ movement without ramping (thanks)
- Spindle Fault activation will cause jogging inputs and spindle to stop with ramping
- Spindle Fault activation will cause running code to stop, and XYZ + spindle to stop
- After Spindle Fault activation, rewind and start program are locked until a homing sequence is run.
- Homing while in spindle fault causes the fault to clear and function to return, even if fault is still active. I'm not sure if this is good.
Overall thanks.
I'm not going into the ramping debate here, but if the fault could say active, if the input is still active through a homing sequence, I think that will sort this input out nicely.
I am glad that that we were able to add this feature, hope it helps. For ramping, its in the development list now, some things are easier to implement and some take more time.
Regarding your last point "homing while in spindle fault causes the fault to clear and function to return", can you please explain more what is happening.
Regarding your last point "homing while in spindle fault causes the fault to clear and function to return", can you please explain more what is happening.
- If the spindle fault is triggered, the system stops. correctly . But If you run a homing sequence to try to clear the fault (only way i have found to try to clear the software) while the spindle is still in fault physically, the software starts to ignores the active fault input. It clears the fault alarm in the software and activates all functions. From now on, the spindle fault input is ignored until you fix the fault, and rehome. In my instance allows me to start running code again without a working spindle.
does that help?
Hi Guy's I am a new to this forum but I have another request for this feature
It is possible to add the same alarm when the input RPM drop to Zero RPM or under a low valus than desire target?
the reason why I went that, I don't have an output fault with my type of spindle
Thanks
It is possible to add the same alarm when the input RPM drop to Zero RPM or under a low valus than desire target?
the reason why I went that, I don't have an output fault with my type of spindle
Thanks
If there is no outputs from your spindle or spindle driver, the only option is an external control system to watch the spindle.. This could be as simple as an optical rpm counter attached somehow, and then use that to send an alarm..
but you will have to decided if it is worth the extra setup... or get a new driver, with a fault output...
but you will have to decided if it is worth the extra setup... or get a new driver, with a fault output...
The software is designed in a way that when an alarm occurs then it will stop the motion and flash an alarm on the screen. After this you should first fix the issue that triggered the alarm and then home the machine. Even if the alarm is still coming from the drive then after homing the alarm is ignored because the signal needs to change its state either from LOW to HIGH or HIGH to LOW to trigger the next alarm.
Regarding the feebback from an RPM sensor, this can be added to MASSO software as we already have an encoder input on the MASSO for displaying the spindle RPM.
Now the main question will be what value do you set for alarm. For example if we try to run the spindle at 3000 RPM and the RPM will not be exactly 3000 and will change depending on the spindle motor and cutting tool load. How much percentage in RPM drop we should set in software to trigger the alarm, 10%, 20% ...???
Now the main question will be what value do you set for alarm. For example if we try to run the spindle at 3000 RPM and the RPM will not be exactly 3000 and will change depending on the spindle motor and cutting tool load. How much percentage in RPM drop we should set in software to trigger the alarm, 10%, 20% ...???
that's a very open question with as many answers as MASSO's sold.. ?
For me, a 2 prong solution.
- selectable presets in the set up menus (tools??).
- each of the 30 tools have different characteristics, tool load can be just another one.
- each of the 30 tools have different characteristics, tool load can be just another one.
- and a slider on the run screen which defaults to the selected preset as the starting point.
- this would read and update with which ever tool is running.
- this would read and update with which ever tool is running.
Yes it is a wide topic with lots of variables, that is why we said that adding logic is very easy to check if the RPM is below some required number and alarm if low but defining this value to check against will depend on a lot of things and not sure if it can be set as a fixed percentage.
If lets say we set it to alarm below 10-30% of the required RPM then at least in case of spindle failure the system can alarm and stop everything.
If lets say we set it to alarm below 10-30% of the required RPM then at least in case of spindle failure the system can alarm and stop everything.
I Patchlead
I have a output but is only a output rpm signal like 4 pulls/rotation
this is the kit
NVBDH+ With Hall https://www.cafr.ebay.ca/itm/ER8-40...047597?hash=item41ce5c92ad:g:tPkAAOSw7GRZE9mD
thanks
even 4 pulses per rev should be fine if you just want to monitor the RPM. Is there an output on the drive to get these pulses?