Guest
21
M31 Motion Controller / Re: VFD
« Last post by paul.stephens on February 16, 2026, 01:07:01 PM »We currently have 200+ active tickets in support. We take them in order as we receive them.
Recent Posts
22
M31 Motion Controller / Re: VFD
« Last post by edcross on February 16, 2026, 10:03:17 AM »I am sure glad you are on this forum , i am not getting much response from support . On the drive problem i got a db25 board and just connected my G540 , no movement i will go over the settings . What should it list as the control source in the config window.
Thank you
Ed
Thank you
Ed
23
M31 Motion Controller / Re: VFD
« Last post by paul.stephens on February 16, 2026, 09:43:53 AM »You will need a SOURCE wiring Configuration for your VFD.
In such wiring mode, remove the jumper between +24 V and OP. Connect +24 V to
the common port of external controller (J5 FE on the M31) and meanwhile connect OP to COM. If external
power supply is applied, remove the jumper between CME and COM.
This will be your forward signal:
VFD+24v → J5 FE M31
VFD DI1 → J5 FC M31
This will be your Speed adjustment:
VFD AI1 → J5 10v
VFD GND → J5 0v (Verify this is the correct ground by reading your VFD manual)
https://www.ivdc.com/cnc/SVD-P%20user%20manual-NEW.pdf
In such wiring mode, remove the jumper between +24 V and OP. Connect +24 V to
the common port of external controller (J5 FE on the M31) and meanwhile connect OP to COM. If external
power supply is applied, remove the jumper between CME and COM.
This will be your forward signal:
VFD+24v → J5 FE M31
VFD DI1 → J5 FC M31
This will be your Speed adjustment:
VFD AI1 → J5 10v
VFD GND → J5 0v (Verify this is the correct ground by reading your VFD manual)
https://www.ivdc.com/cnc/SVD-P%20user%20manual-NEW.pdf
24
MachPro General Discussion / MachPro
« Last post by cd_edwards on February 15, 2026, 03:10:25 PM »For anyone thinking about upgrading to MachPro there are still issues being worked on. I have problems with reading Registers from m-code scripts. For me, and the RC ATC this is a problem I need to solve as I need a removable dust boot. As far as the program, it's nice... There are definitely QOL improvements over Mach4 and way beyond Mach3. ESS support appears to be working extremely well. Definitely some niggling little bits that need work at this time though. It is unforunate that Mach4 is being EOL'd at this time though. Maybe a discount given to those that already own Mach4 might be an option. I've spoken to Carl Eldridge on the phone and he seems like a great guy. I wish them ALL the success the in world on this endevour.
As far as the hardware I can't speak to it, but with all the ESS and cnc4pc parts I have kicking around, there was no way I could justify moving to the M-31.. Ethercat would be really nice, but it's also out of my budget as a hobbyist. Right now I'm working on my fourth CNC build in 15 years. I will be moving it over to MachPro once a few features are working. RC ATC, maybe script debug, IPC would be nice so that remote control is possible (almost working).
I would like to see them finish Mach4 so it's more usable. IPC on my win10 and win11 computers fail. This affects wxprobe screen which does not work at all for me. They have this great probing screen that's useless as it won't detect probes at all. :shrug:
anyways, if anyone has ideas on why mcGetRegister() fails in a m-code script, I'm all ears. return code can be -17 or -27(??) occasionally, and sometimes 0 for rc. always 0 for value.
As far as the hardware I can't speak to it, but with all the ESS and cnc4pc parts I have kicking around, there was no way I could justify moving to the M-31.. Ethercat would be really nice, but it's also out of my budget as a hobbyist. Right now I'm working on my fourth CNC build in 15 years. I will be moving it over to MachPro once a few features are working. RC ATC, maybe script debug, IPC would be nice so that remote control is possible (almost working).
I would like to see them finish Mach4 so it's more usable. IPC on my win10 and win11 computers fail. This affects wxprobe screen which does not work at all for me. They have this great probing screen that's useless as it won't detect probes at all. :shrug:
anyways, if anyone has ideas on why mcGetRegister() fails in a m-code script, I'm all ears. return code can be -17 or -27(??) occasionally, and sometimes 0 for rc. always 0 for value.
25
M31 Motion Controller / VFD
« Last post by edcross on February 14, 2026, 10:32:12 AM » Vfd Soyan Power Svd Ps2 2gb 220v single phase . Does any one have info or diagram to connect to Machpro M-31..
Thanks
Ed
Thanks
Ed
26
Spanish / Usar comandos Rest API
« Last post by Sergi on February 13, 2026, 12:50:08 PM »Hola buenas tardes,
Hay forma de usar comandos Rest (Get/Post) desde Mach3? He probado varias formas que si funcionan en Vb pero no en Mach3 ya que creo que es porque le faltan librerías y da error.
Gracias de antemano.
Hay forma de usar comandos Rest (Get/Post) desde Mach3? He probado varias formas que si funcionan en Vb pero no en Mach3 ya que creo que es porque le faltan librerías y da error.
Gracias de antemano.
27
Mach SDK plugin questions and answers. / Re: MPG and Jog ignoring metric units
« Last post by Userli on February 13, 2026, 11:03:23 AM »I should have added that the increments are set to 1. The GUI exposes the same problem when jogging.
28
Mach SDK plugin questions and answers. / MPG and Jog ignoring metric units
« Last post by Userli on February 13, 2026, 10:32:16 AM »I'm developing a MACH4 plugin for a pendant, which uses MPG and JOG movements. MACH4 is configured to use metric, including jog units and I set mcJogSetUnitsMode(m_inst, axisId, MC_UNITS_METRIC) in addition.
Still when using mcJogIncStart or mcMpgMoveCounts the device moves 1 inch (i.e. 25.4mm) instead of 1 mm per unit passed to the methods.
I tested this on versions 6778 and 6693.
Is this a bug or am I missing a configuration?
Still when using mcJogIncStart or mcMpgMoveCounts the device moves 1 inch (i.e. 25.4mm) instead of 1 mm per unit passed to the methods.
I tested this on versions 6778 and 6693.
Is this a bug or am I missing a configuration?
29
M31 Motion Controller / Re: M 31 stepper wiring
« Last post by edcross on February 13, 2026, 10:07:08 AM »Thanks Paul , I'll give it a try
Ed
Ed
30
M31 Motion Controller / Re: M 31 stepper wiring
« Last post by paul.stephens on February 13, 2026, 08:49:40 AM »Hi Ed,
For your G540, you will need to break out your DB25(Parallel port) and connect the following pin wires to the following connectors.
X Axis
DB25 Pin 2 → M31 MTR0 S+
DB25 Pin 3 → M31 MTR0 D+
Y Axis
DB25 Pin 4 → M31 MTR1 S+
DB25 Pin 5 → M31 MTR1 D+
Z Axis
DB25 Pin 6 → M31 MTR2 S+
DB25 Pin 7 → M31 MTR2 D+
A Axis
DB25 Pin 8 → M31 MTR3 S+
DB25 Pin 9 → M31 MTR3 D+
Below is your manual for reference:
https://www.geckodrive.com/wp-content/uploads/2023/04/G540-MANUAL-REV8.pdf
You can use a Ohm meter to test continuity on your pins if needed to find which wire is which pin.
Alternatively, they make DB25 Breakout Boards.
Thanks,
Paul
For your G540, you will need to break out your DB25(Parallel port) and connect the following pin wires to the following connectors.
X Axis
DB25 Pin 2 → M31 MTR0 S+
DB25 Pin 3 → M31 MTR0 D+
Y Axis
DB25 Pin 4 → M31 MTR1 S+
DB25 Pin 5 → M31 MTR1 D+
Z Axis
DB25 Pin 6 → M31 MTR2 S+
DB25 Pin 7 → M31 MTR2 D+
A Axis
DB25 Pin 8 → M31 MTR3 S+
DB25 Pin 9 → M31 MTR3 D+
Below is your manual for reference:
https://www.geckodrive.com/wp-content/uploads/2023/04/G540-MANUAL-REV8.pdf
You can use a Ohm meter to test continuity on your pins if needed to find which wire is which pin.
Alternatively, they make DB25 Breakout Boards.
Thanks,
Paul