I use âm66_wait_for_inputâ command to achive that. It check for 30 sec if âauxiliary 4â detect that the vfd is running. If so, it continu. if not it display a message and wait for cycle start to be press.
I first connected the multi-output (FA and DCM) of my vfd and G3 TTL input 17 configure as âAuxiliary 4â.
vfd FA connected to G3 TTL input 17
vfd DCM connected to G3 GND
Then I added these lines at the beginning of my GCODE just after the first Sxxxx M3.
MSG Waiting for spindle to start (30 sec max)
M66 P4 L3 Q30000 S2
MSG Please start VFD (Press cycle-start to resume)
M00
MSG
What level of safety, or what functionality, would you like to see?
Initial thoughts are having the VFD signal control a relay that is part of E Stop circuit, or alternatively have it as a configurable input on Masso - one that may not stop everything, and would allow it to be cleared (with or without rehoming would need to be decided/determined depending on your choice).
A bit of homework for me and my Masso, Optidrive (vfd) and post processors.
Iâll tell if i get it to work.
Desired Outcome:
Spindle and bit dont plunge into work piece if the vfd is not operational. Pause to allow me to switch the vfd on.
I dont want it to respond to "is spindle spinning " as some operations dont hve a spinning spindle, such as drag knife, diamond engraver and pen plotter.
You,ll notice that (in response to your outcome) that you can enable/disable each spindle check operation individually for each NC Program. Another precision, each spindle check operation is configurable and do not need any intervention if condition is met before the defined timeout value is reach. But if the timeout value is reach before condition is met then youâll have to press 'Cycle Start to continue).
Hi, @blaghislain. It feels like youâre my post-processor person.
Is the following fixable?
When I run two toolpaths from F360, say pocket followed by contour, with the same tool but with different spindle speeds, the machine pauses; with the spindle and coolant still on, a message pops up on the screen waiting for user engagement.
It looks like the post-processor is inserting code that, atleast for me, is unwanted.
because you are using the âMASSO Onefinity Community Editionâ (check your NC Program POST in fusion - ref red rectangle in my image).
because the post property option âSpindle Running Check Enableâ is Checked. (see green rectangle in my image).
This community edition require that your VFD is connect to masso controler ( see github Readme ) so the masso controler is able to detect if the spindle is running or not and will continu automatically or stop if manual intervention is required.
If your VFD IS NOT connected to masso, I recommend to use native onefinity masso post processor instead.
If your VFD IS connected to masso, I recommend to uncheck post properties options (see green rectangle) related to spindle start and stop.