Hello Guest it is February 28, 2026, 09:17:46 PM

Recent Posts

Pages: 1 2 3 4 5 6 7 8 9 10
1
General Mach Discussion / Re: i/o boards
« Last post by arturod on February 27, 2026, 07:41:38 AM »
The PoKeys is great.  Especially because the plugin has all the built-in functions that you can think of for a panel.  The downside is that the I/Os go pretty much directly to the pins of the microcontroller, so you really have to know what you are doing to connect all the pins and functions.  We used to make and support all kinds of I/O boards for the Pokeys boards, but stopped producing them as the demand was low.

Arturo Duncan
https//cnc4pc.com




2
Modbus / Re: Hitachi X200
« Last post by Peter Homann on February 26, 2026, 06:45:36 PM »
Good to hear.  Modbus in Mach3 is rock solid.

Cheers

Peter.
3
Modbus / Re: Hitachi X200
« Last post by Ian baldwin on February 26, 2026, 12:17:49 AM »
15 years later and this still works! Just got my x200 VFD set up with modbus in mach 3  ;D ;D ;D ;D
4
General Mach Discussion / i/o boards
« Last post by fast89 on February 25, 2026, 05:59:06 PM »
What is everybody using for i/o boards to interface a control panel full of buttons and switches to mach3. I've been using Pokeys usb for many years but I'm really getting tired of the problems. (very susceptible to noise and randomly stops working.) Recently had it open the collet mid operation with a bar feeder. Bad things happen.
5
Mach4 General Discussion / Re: Servo ready input ess , howto block cyclestart
« Last post by DAAD on February 25, 2026, 12:22:45 AM »
Thanks for the reply.

Yes i have inputs from the servo drive already in ESS.
Atm i have put some code in the screen script to prevent cycle start if one drive is not ready, but my machine is out for a couple of day's so did not have the possibility to test what i've done.

If you have some code, it would be appreciated.

Adam
6
Mach4 General Discussion / Re: Servo ready input ess , howto block cyclestart
« Last post by cncmagic on February 24, 2026, 07:26:06 PM »
do you have inputs that indicate the drive is ready? if you have these wired either as separate inputs to the ESS or as a string from one servo to the next. You can then write some code that looks for these inputs and won't allow the system to start if they are not high. I've done something similar and will post the coding I used shortly.  Bob :o
7
Hi everyone,

I’ve been working on a project called ALIG (Advanced Laser Imaging Generator), a standalone CAM tool specifically designed for high-speed laser raster engraving.

I decided to start this project because popular software like LightBurn or LaserGRBL do not accurately account for hardware latency (the tiny delay between the motion controller command and the actual laser firing). This often results in the "sawtooth" effect or blurred vertical edges, especially when pushing the machine to its speed limits.

The Latency Problem Solved
ALIG is built around a dedicated Latency Calibration Engine:
- Visual Offset Calculation: Generate specific test patterns to measure your machine's response time in milliseconds.
- Predictive G-Code Simulation: The internal parser factors in your machine's specific latency to provide a high-fidelity visual preview. You can see exactly how the timing offset will affect the physical engraving before you even start the job.

Key Features for Mach4 Users:
- M67 Analog Support: Full support for M67 commands (Analog Output) for fluid, jitter-free power transitions without stopping the motion buffer.
- S-Command Compatibility: Also supports standard S-commands for GRBL, Marlin, and FluidNC.
- Smart Clustering: Reduces G-code size by quantizing grayscale levels (2-256 steps), preventing "buffer starvation" on motion controllers.
- Zero-Installation: It’s a standalone portable .exe. No Python environment setup required.

Interface Demo (GIF):

Download & Feedback
ALIG is currently in v0.98b and is free to use. I’m looking for feedback from the Mach community.

GitHub Repository & Download: https://github.com/MoMo830/AliG

I'd love to hear your thoughts, especially if you've struggled with laser alignment issues at high speeds.

Happy engraving,

Alexandre "MoMo"
8
Wishlist / Wishlist Board
« Last post by paul.stephens on February 20, 2026, 02:59:26 PM »
Welcome to the Wishlist Board

The Wishlist board is the official place to propose and discuss feature ideas for the MachPro product line. This forum helps our team understand what the community values most and provides a central location for collecting, reviewing, and prioritizing suggestions.

How to use this board

  • Submit feature requests you would like to see added or improved in MachPro.
  • Explain the use case behind your request (what you’re trying to achieve and why it matters).
  • Include helpful details such as workflow impact, hardware/software context, and any relevant examples.
  • Comment on existing requests to show support, add clarity, or suggest alternatives.

Please keep posts constructive, specific, and focused on improving the MachPro experience.

Thank you for contributing your ideas and helping shape future development.
9
MachPro General Discussion / Re: MachPro
« Last post by paul.stephens on February 20, 2026, 02:18:32 PM »
Thanks,

I'll take a look when I get the chance!
10
MachPro General Discussion / Re: Registers
« Last post by paul.stephens on February 20, 2026, 01:56:50 PM »
If some API calls are working in IPC and others are not, then it may be a port conflict with Windows.

You can reserve the Mach IPC port range one line commands.  One is for TCP and the other is for UDP. 
 
These are for the Mach API over IPC.
netsh int add excludedportrange protocol=tcp startport=48000 numberofports=200 store=persistent
netsh int add excludedportrange protocol=udp startport=48000 numberofports=200 store=persistent
These commands reserve the port range 48000 to 48199 for both TCP and UDP. 
 
These are for the Screen IPC.
netsh int add excludedportrange protocol=tcp startport=48500 numberofports=200 store=persistent
netsh int add excludedportrange protocol=udp startport=48500 numberofports=200 store=persistent
These commands reserve the port range 48500 to 48699 for both TCP and UDP. 
 
A reboot may be required to get Windows to let go of the ports. 
Pages: 1 2 3 4 5 6 7 8 9 10