I have searched the forum for VFD programming, and all I have found is settings for the BuildBotics controller. Are any of the settings different between the two controllers?
I have been using my Elite with an HY 110v 1.5kw VFD and spindle, but I have been controlling it from the VFD. I finally got around to ordering the cabling to have the Masso control the spindle. I believe everything is wired correctly, but I am not an electrician. From info here, and out on the other interwebs, I thought that the only changes needed to be made to the VFD was changing PD001 and PD001 from 0 to 1, but no luck. I changed a few other settings while I was trying to troubleshoot, so I figured I’d set it back to default and start from the beginning.
yes, the settings are different because the buildbotics-derived Onefinity controller of the Original/X-50/PRO Series controls VFDs with Modbus via a RS-485 serial communications interface (two-wire interface), while the MASSO G3 Touch of the Elite Series unfortunately does not support Modbus and has to control the VFD through a programmable input terminal for FWD/REV/STOP spindle and a analog 0–10 V voltage line for SPEED (FREQUENCY). Therefore the settings for “source of RUN commmand” and “source of frequency/speed control” must be set differently depending on which CNC controller you have. Luckily nearly all VFDs I know support both methods.
Regarding wiring, here is a table that shows the wiring when using the spindle control cable:
Thinking about upgrading to Masso from an X-50 machine (Buildbotics controller, RS485 connections). I use a 2.2kW spindle and a Hitachi S1 VFD. There are a lot of similarities for that VFD and the Omron MX2 VFD. I’d like to understand what to connect before even buying Masso because the process intimidates me. I’ve watched these two videos, but they use a different VFD than mine (with different labels on connections).
Putting all this together, I think I have to connect the items below (Masso terminal on the left, my VFD on the right):
0-10 V Speed input — AI2
Ground — COM (I have two COM connections, one already bridged to PW)
Pin 4 — Also COM? GND? (HY uses the term DCM)
Pin 5 — S1? (HY uses the term FWD) Since I won’t run in reverse, I didn’t think I needed S2.
The videos also describe programming changes in the VFD specific to that maker. When I set up the CNC, I had to tell it to accept the Modbus that Masso doesn’t use. I think one such parameter is the “Running Command Channel” which has been set to “2-Communication” but now should be “1-Terminal” (right?) Also, “Frequency Command” has to be set to AI2 since it will connect to the Masso.
the difference between the buildbotics-derived Onefinity Controller and the MASSO G3 is that you have no Modbus over serial line support. Instead, the MASSO controls the VFD/spindle SPEED over the analog voltage interface and RUN/STOP/CCW over a programmable VFD terminal. Mainly the table in this page applies, with the following pin names: “O” is “AI2” (=the analog voltage input) and “1” is “S1”, “2” is “S2” (=the programmable terminals for CW RUN/STOP and CCW RUN/STOP). The bridge must be changed from PW to +24V instead of PW to COM.
All VFDs that I know offer a analog voltage (Volts) or analog current (Ampères) speed control as fallback, and programmable terminals for RUN CW/STOP and RUN CCW/STOP, so this way of controlling a VFD practically always works.
The settings inside the VFD are always called something like “Source of RUN command” and “Source of SPEED command” or “Source of FREQUENCY command” and for the Original and Pro Series, you had to set both to “Modbus Serial Interface”, which now with the MASSO has to be changed to the analog voltage input and the programmable terminal respectively. You need to assign one programmable terminal for RUN/STOP and if you need counter-clockwise rotation (which is the case if you want to use RapidChange ATC (Onefinity offer) – not necessary on “normal” ATC spindles like this one) another programmable terminal. The programmable terminal 1 must be assigned to clockwise run, and the the terminal 2 to counter-clockwise run.
