Recent Posts

71

Promote and discuss your product / Re: E_CNC WHB04B v1.1.1 – Professional WHB04B Solution for Mach4 and MachPro

« Last post by Srato on July 21, 2026, 10:28:19 AM »

E-CNC WHB04B for Mach4 – Version 1.1.2 Released

Hello everyone,

A new update for the E-CNC WHB04B Wireless Pendant for Mach4 is now available.

What's new in v1.1.2
Added configurable Continuous Jog rates (2%, 5%, 10%, 30%, 60%, 100% and Lead) through ConfigUI.
Continuous Jog rates are now stored in the configuration file and automatically applied by the Bridge.
Minor internal improvements and bug fixes.

This update gives users more flexibility to fine-tune continuous jogging according to their machine and personal preferences, while maintaining full compatibility with existing installations.

As always, thank you to everyone using and supporting the E-CNC WHB04B project. Your feedback continues to help improve the software.

More information:
https://e-cnc.pt

72

Mach4 General Discussion / MOVED: Custom motion plugin: Home()/Purge() never called + Motor Tuning graph broken on

« Last post by Tweakie.CNC on July 21, 2026, 12:44:40 AM »

This topic has been moved to Mach SDK plugin questions and answers..

https://www.machsupport.com/forum/index.php?topic=49614.0

73

MachPro General Discussion / Re: BUG? Axis A not homed... but I have no A axis

« Last post by phil@highside.co.nz on July 20, 2026, 02:46:42 PM »

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

74

Mach SDK plugin questions and answers. / Re: Custom motion plugin: Home()/Purge() never called + Motor Tuning graph broken on

« Last post by mtl on July 20, 2026, 12:21:15 PM »

Mach3. Sorry, this seems to have landed in the Mach4 board by mistake - I meant to post it under "Mach SDK plugin questions and answers." Could a moderator move it there if possible? Thanks for the reply.

75

MachPro General Discussion / Re: BUG? Axis A not homed... but I have no A axis

« Last post by Sunkistist on July 20, 2026, 12:19:21 PM »

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,

76

Mach SDK plugin questions and answers. / Re: Custom motion plugin: Home()/Purge() never called + Motor Tuning graph broken on

« Last post by Bill_O on July 20, 2026, 09:23:23 AM »

I know nothing about what you are doing but I do have one question.
Are you using Mach3 or Mach4?

77

MachPro General Discussion / Re: BUG? Axis A not homed... but I have no A axis

« Last post by phil@highside.co.nz on July 20, 2026, 05:32:28 AM »

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

78

Mach SDK plugin questions and answers. / Custom motion plugin: Home()/Purge() never called + Motor Tuning graph broken on

« Last post by mtl on July 18, 2026, 03:30:39 PM »

Hi all,

I've written a custom external motion device plugin (USB/serial connected, our own hardware) based on the official BlankMovement SDK template. The following is confirmed working:

- JogOn/JogOff are called correctly, and we drive real motion via Engine->Axis[a].Jogging
- Notify() receives real events (EX_SPINON, EX_MOTORTUNED, etc.)
- Our device is continuously, actively connected and communicating (verified via constant serial traffic)

Two things are NOT working:

1. Home() and Purge() are NEVER called - not via a real click on "Ref All Home", not via programmatically simulating DoButton(22-25), and not by setting Engine->Homing / Engine->AutoHome to true ourselves.

2. The Motor Tuning screen draws a normalized (0-1) graph and won't accept entered values, but ONLY for axes that are Enabled on the Motor Outputs screen. For a disabled axis, the screen behaves completely normally.

Question: Is there an undocumented step/flag/sequence in InitControl/PostInitControl/Update that we're missing, which is required for Mach3 to treat a plugin as a "fully authorized" real motion device for Home and Motor Tuning purposes? The SmoothStepper FAQ mentions this is related to "continuous communication with the board," but we already have that - and these two features still don't work.

Additional question: Beyond this specific issue - the official BlankMovement SDK template is just a skeleton and doesn't include a full working example where Home/Jog/Motor Tuning genuinely work end to end. Does anyone know of a publicly available, fully working open-source example plugin? A reference like that would have prevented this kind of "undocumented requirement" issue from the start.

Thanks in advance for any pointers.

79

MachPro General Discussion / Re: ESS Spindle Setup

« Last post by lmarti13 on July 18, 2026, 09:44:25 AM »

I did, but the spindle didn't work.  Maybe it was because I was on an old version of the plugin, before the spindle change in v278.  Anyway, once I remapped the spindle PWM to the proper output name, it is working.

Most likely I did something wrong... ;o)

80

MachPro General Discussion / Re: ESS Spindle Setup

« Last post by cd_edwards on July 18, 2026, 09:28:09 AM »

you didn't use the MachPro import Mach3/Mach4 setting when installing MachPro?