A Mach3 system using an Ethernet NVEM six-axis V1 controller exhibits three related motion hazards: soft limits appear to follow work coordinates, limit approach has no controlled slowdown, and Run From Here introduces an unsafe preliminary move. A separate test with Mach3 R3.043.022 and an AKZ250 USB controller did not reproduce the coordinate-switching fault, so isolate the motion controller before changing the machine design.
System and Observed Faults
| Item | Evidence | Engineering consequence |
|---|---|---|
| Control PC | 2005 PC running Windows XP | Record this configuration when comparing software and controller behavior. |
| Motion controller | Ethernet NVEM six-axis V1 | Controller-specific motion handling is a hypothesis requiring testing. |
| Axis hardware | DM542 drivers and Nema23 motors rated 3 N/m | No motor or drive fault is established by the reported symptoms. |
| Limit switches | Simple microswitches wired NC | The same switch may serve homing and limit functions, but operation must be verified on this controller. |
| Soft limits | Correct at machine origin; changing to work coordinates can trigger a stop | Mach3 appears to evaluate displayed work coordinates instead of retaining the machine-coordinate limits. |
| Limit approach | No reported slowdown | The machine may reach the configured boundary without a progressive approach. |
| Program restart | Preliminary move appears relative although coordinates are absolute | The move can command travel outside the available stroke. |
Separate Coordinate Display from Machine Position
Use the operating sequence supported by the evidence: establish the machine origin, establish the work origin, and then load the machining program. Soft-limit validation must remain consistent when the display changes between machine and work coordinates.
A comparison system running Mach3 R3.043.022 with an AKZ250 USB controller retained correct soft-limit behavior while switching between machine and work coordinates. This does not prove an NVEM defect, but it narrows the fault to the NVEM integration, its driver or plugin, its configuration, or a version-dependent interaction. The installed Mach3 version and NVEM software versions remain unknown and must be recorded before drawing a final conclusion.
Run a Controlled Soft-Limit Test
- Record the installed Mach3 version and the NVEM driver or plugin version. Preserve the current configuration before changing settings.
- Home the machine and confirm that the displayed machine position corresponds to the established machine origin.
- Enable soft limits and jog each axis within the accepted machine-coordinate envelope without approaching a physical switch at speed.
- Set a work origin, switch the display to work coordinates, and repeat the same low-speed jog test. Do not change the machine position merely to change the displayed coordinate system.
- If the coordinate-system switch alone triggers the safety response, disable production motion and repeat the test with the same Mach3 configuration on another supported controller, if available. The reported AKZ250 result provides a comparison point but not a universal controller specification.
Do not treat toggling soft limits off and on as a repair. It only restores movement after the controller believes the machine is outside the accepted area; it does not correct the coordinate evaluation fault.
Control Homing, Limit Approach, and Program Restart
The evidence supports using one physical sensor for both homing and limit detection without an additional homing-in-limit parameter on the tested system. That behavior is not confirmed for the NVEM installation. Verify at low speed that homing can contact the NC switch, establish the origin, and move away without leaving the axis locked.
The AKZ250 comparison system slows progressively near the limits, with the approach distance configured in Mach3. The NVEM system does not show this behavior. Confirm whether the NVEM driver implements the Mach3 approach-distance setting before relying on it; otherwise, treat controlled limit approach as unsupported.
For a mid-program restart, re-home before resuming and inspect the modal state at the selected restart point. Avoid beginning within an inherited special motion mode such as G02 or G03. Review the preliminary move in a non-cutting test because the reported NVEM behavior can interpret that move incorrectly and command an out-of-travel position.
Assess Probe Inputs and Software Options
The proposed 3D work probe and tool probe each expose NC, NO, and probe-ready signals. The evidence does not establish whether NC and NO must be connected simultaneously or are alternative contact outputs. Before selecting a controller, determine which signals the probing sequence actually consumes, then compare that requirement with the NVEM controller's documented available inputs.
Mach3 can implement custom probing through macros and modified screens. The required sequence must establish the work reference from the table, then measure tool length and diameter and apply the corresponding corrections. No evidence confirms that the current NVEM has enough usable inputs or supports every required probing action.
The available information is insufficient to choose between CSMIO M and S, recommend migration to Mach4, confirm simCNC macro complexity, or identify a Fusion 360 post-processor. Make that decision only after documenting the required probe signals, input capacity, supported probing commands, and controller-specific motion behavior.
Verification and Acceptance Criteria
Accept the configuration only when soft limits remain unchanged across machine and work-coordinate displays, every axis homes and releases its shared NC switch correctly, limit approach behaves as configured, and a dry-run restart cannot generate an out-of-stroke preliminary move. For probing, verify each selected signal independently before allowing a macro to update work or tool corrections.
FAQ
Why do Mach3 soft limits trigger after switching to work coordinates?
The reported NVEM system appears to evaluate the changed work-coordinate display incorrectly. Mach3 R3.043.022 with an AKZ250 USB controller did not reproduce the fault, so record versions and isolate the NVEM driver, plugin, configuration, or controller behavior.
Can one NC switch handle both Mach3 homing and limits?
Yes on the tested comparison system, where the same sensor handled homing and limit detection without an extra parameter. Verify contact, origin capture, and switch release at low speed because this behavior is not confirmed for the NVEM installation.
Can Mach3 control a 3D work probe and a tool probe?
Mach3 can implement the sequence with custom macros and modified screens. First determine whether each probe uses NC, NO, probe-ready, or a subset of those signals, then confirm that the controller provides enough compatible inputs.