The above configurations still work. But I have version 2 of the settings that provide some protection against the VFD being in STOP mode and/or the connection between the onefinity controller and the VFD dropping (a scenario could be that the control cable between the Onefinity Controller and the VFD disconnects such that the Controller commences a program without the Spindle being in operation.
Changes to Onefinity Controller:
- status-read → Address: 0. This will send regular communication to the VFD “Drive Control Command” in register 1 (0 in our case as there is one digit difference between all VFD registers and the Onefinity Controller addresses (presumably one is 0 -based and the other is 1-based). This change supports the VFD controller parameter change P-36, Index 3 in Purpose 3 below
Changes to VFD Parameters
Purpose 1: Check to see if the motor is enabled
If it is enabled, the Relay across terminals 10 & 11 goes from “Normally Open” to “Normally Closed”. P-18 to 0 which is “Motor Enabled”. The other setting options are active when the VFD indicates “Stop” Which is not good enough as the controller is unable to communicate to the VFD in this state.
Purpose 2: Check to see if output frequency is less than minimum
Set P-25 to 6 to output a digital signal when the frequency is less than the value set by P-19. Set P-19 to 25 (25% or less of max frequency). That is, activated then the spindle isn’t spinning at min RPM (6000 rpm, this was guessed from the forums. I am waiting to hear back from 3DTEK about the minimum RPM for the spindle they supplied me)
Purpose 3: Poll to see if the RJ45 / Controller is connected and./or the controller is sending a valid RTU signal (ie “tool-type” has been set correctly in the Onefinity Controller Tool tab:
Set P-36 Index 3 - to 3 and set a value of 1000 (others are available). This is will capture when a signal (a command write to register 1 (or 0 in our case when using the Onefinity / Buildbotics controller) is not received from the controller to the VFD within 1 second (ie a disconnect). This will cause the VFD drive to “STOP”. It automatically goes to run when the RJ45 cable to the controlled is reconnected. Make sure the controller is always sending the VFD a signal used I set Onefinity Controller configuration “status-read” a read command to Register 1 (or 0 in our case when using the Onefinity / Buildbotics controller (see above)
Purpose 4: Ability to Reset the VFD from “STOP”
Set P-15 to 5. This allows digital input on terminal 3 to be connected to the “Normally-Open” push switch that is used to create a momentary Open rising edge signal that signals “START” drive according to the setting 5 for P-15 (see the diagrams in the manual)
Wiring Changes
-
Normally Open push button switch across terminals 1 and 3 to allow resetting of “STOP” drive status and enable the drive. Supported by parameter change P-15 in Purpose 4 above
-
Light or sound output device across terminals 10 and 11 to take advantage of the parameter changes Purpose 1 above.
-
Light or sound output device across terminals 8 and 9 to take advantage of the parameters changes described in Purpose 2 above
I hope this makes sense