Hi, first time post long time lurker. Looking forward to learning where I’ve gone wrong.

I recently purchased and installed Machpro and I am looking forward to using it with my CNC knee mill. However, I have yet to get it fully functioning. The profile I’m running was imported from Mach4, where it was working fine. After running the homing sequence the first thing I tried was fire off a simple XY move (G01 X1 Y1 F10) via the MDI button. But nothing moves and I get an error in the status box stating “Axis A must be homed before running G-code”. I thought I could get by without the MDI but the error pops up while running a g-code file and when I was setting up my auto tool setter.
 
Nowhere in my settings is Axis A, or Motor 3, enabled. And in settings under Safety Check - Ignore Axes Homing Safety Check I have tried both “3” and “3-5”.
I went so far as to make an entirely new profile from scratch. That profile is throwing errors for a door interlock safety and a low coolant switch, neither of which I have. And for the record they are disabled in the settings section and no inputs were ever set for them. Also for the record, the motors are working as I can home and jog to my hearts content.

It won't let me attach files but below is the diagnostics log.

2026-07-06 12:57:49.419

• [I    ] - Logging Enabled.

2026-07-06 12:57:51.134

• [I    ] - Cycle Start Button Pressed  Line

2026-07-06 12:57:51.135

• [I    ] - Function: SetStopStatus():  completed successfully, called by: SetStopStatusAll(), (inst = 0) ?

2026-07-06 12:57:51.135

• [I    ] - Function: SetStopStatusAll():  completed successfully (inst = 0) ?

2026-07-06 12:57:51.135

• [I    ] - Function: ResetAllOverrideAxes():  completed successfully (inst = 0) ?

2026-07-06 12:57:51.135

• [I    ] - Function: ResetEndOfProgramOutput():  completed successfully (inst = 0) ?

2026-07-06 12:57:51.135

• [I    ] - Function: LaserPointerCycleStartCheck():  completed successfully (inst = 0) ?

2026-07-06 12:57:51.135

• [I    ] - Function: GetSoftLimits():  completed successfully, called by: CycleStartSoftLimitRecovery(), (inst = 0) ?

2026-07-06 12:57:51.135

• [I    ] - Function: CycleStartSoftLimitRecovery():  completed successfully (inst = 0) ?

2026-07-06 12:57:51.136

• [I    ] - API: mcCntlMdiExecute(inst = 0, commands = 'G01 X1 Y1 F10') (unknown caller)

2026-07-06 12:57:51.136

• [I    ] - Force home check failed: axis A is not homed.

2026-07-06 12:57:51.136

• [I    ] - API: mcCntlMdiExecute() Force home check failed! Returned MERROR_NOT_NOW.

2026-07-06 12:57:51.136

• [I    ] - Error: The operation could not be completed at this time. Return Code: MERROR_NOT_NOW (-18), Function: ExecuteMDI(), Called by: xpcall(), File: [C], Line: -1  Line

2026-07-06 12:57:51.136

• [I    ] - Error: The operation could not be completed at this time. Return Code: MERROR_NOT_NOW (-18), Function: _CycleStart(), Called by: pcall(), Line: -1  Line

2026-07-06 12:57:57.682

• [I    ] - Logging Enabled.

Any help is appreciated! Thank you!

I'm having the same issue with my upgrade from Mach4 Hobby to MachPro.
My install is running an ESS motion controller.
What is yours?
Wondering if there is something amiss in that department.
Cheers
Phil

Sorry to hear you're in a similar boat. Yes, I've got an ESS with an MB3. My guess is there's something going on where the import profile doesn't get it quite right.

I found a work around I'm not proud of but my machine is working. I gave up hunting settings and just enabled Motor3 and assigned it to the a axis, made sure it was set to "home in place" and then assigned some unused output ports on the ESS to the motor. Learning from a different issue I believe there's some setting buried in the config --> settings that is associated with the a axis, but not labelled as such, that would make the program think it needs an a axis.



Cheers,

Yep, I've done the same thing.
On digging a bit deeper, there are suggestions that it could be directly associated with the screen design.
Further research required.
Cheers
Phil