Hello Guest it is May 14, 2021, 03:16:12 AM

Author Topic: Mach4 builds released, release notes file updated  (Read 1747 times)

0 Members and 1 Guest are viewing this topic.

Build 3206 and 3233 were major updates that added new probing utilities, PMC (programmable
logic controller), and many updates to make lathe mode fully functional.

Mach4 build was released 21 November 2016. Build 3233 can be downloaded here:


or here:


The release notes have been updated here:


Our complete archive of previous downloadable Mach4 installer releases is here:


Steve Stallings
Steve Stallings
For PMDX product support, please use PMDX forum or direct email for quickest response. We do not use this forum as our primary product support site.
Re: Mach4 builds released, release notes file updated
« Reply #1 on: December 27, 2016, 12:57:06 PM »

Anyone else having issues with this build?

My centre bore script just hangs randomly, usually fairly close to the start even when debugging.

I also seem to have lost the ability to incrementally jog?

Running with a PMDX-411 and the latest drivers.
Re: Mach4 builds released, release notes file updated
« Reply #2 on: December 29, 2016, 08:45:10 AM »
I too had thought the inc jog wasn't working. I did find that there is a keyboard plugin that has some settings you can check & possibly change.
While in the Disable mode go to Configure, Plugins, Keyboard Inputs - Newfangled Solutions, you will see they have it set up to use the (Ctrl) key + arrow and page up or down keys for incremental moves.

Hope that helps

Re: Mach4 builds released, release notes file updated
« Reply #3 on: January 06, 2017, 04:35:01 PM »
I too find that keyboard jogging behaves strangely with version 3233.

By default, the keyboard plugin disables jogging following start up. After  keyboard jogging is  enabled, say by clicking the Notification bar icon, I find that the arrow keys, which should cause normal jogging,  have no effect. Ctrl-arrow, for incremental jogging, does work however. Both are correctly set in the keyboard plugin, so would be expected to take their respective actions.

I have found that the simple work around to this is to modify the first run of the PLC script so that the keyboard plugin is enabled rather than disabled following start up. This ensures correct operation of all keyboard jogging functions.

I am using Windows 7 (32 bit with CSMIO-IP/A and 64 bit with Simulator) and the keyboard plugin is dated 4 November 2016.