Hello Guest it is February 23, 2026, 11:40:07 PM

Recent Posts

Pages: 1 2 3 4 5 6 7 8 9 10
1
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"
2
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.
3
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!
4
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. 
5
MachPro General Discussion / Re: MachPro
« Last post by cd_edwards on February 20, 2026, 01:37:51 PM »
Sure. Here is a profile I've been using for testing. It's not right for a machine, but it does allow testing such as lua scripts etc.
6
MachPro General Discussion / Re: MachPro
« Last post by paul.stephens on February 20, 2026, 01:32:41 PM »
Would you be able to send a profile or just an .ini as well?
7
General Mach Discussion / Tangential Knife Control Configuration
« Last post by mlsilva on February 20, 2026, 12:39:26 PM »
Hi everyone, I hope you're all doing well!

I'm building a 4-axis (XYZA) CNC machine for fabric cutting. I haven't yet decided which software I'll use, but from what I've seen in videos online, Mach3 seems to meet my needs well.

I need to control the A-axis (4th axis) as a tangential knife.

Could someone show me how this configuration is done in Mach3?
8
MachPro General Discussion / Re: MachPro
« Last post by cd_edwards on February 20, 2026, 11:28:18 AM »
Here is my lua script which is causing me problems. mc.mcRegGetHandle() mc.mcRegValue() never returns values that are definitely in the registry. I had a couple of Mach engineers logged into that system to see what the issue was. handle return code is -17. and a 0. Value returns and error because a handle of 0 doesn't exist.

anyways, it's just a method of dropping a dust shoe and picking it up again from a RapidChange ATC. I know RapidChange is working on there wizard/scripts and MachPro as well.

9
MachPro General Discussion / Re: MachPro
« Last post by paul.stephens on February 20, 2026, 11:06:18 AM »
Hi,

Would you be able to send me your Mcode script?

In MachPro, Mcodes are handled a bit differently than what you may be used to. We use a file called UserMCodeModule for custom or modified MCodes. We are working on getting documentation on how this is done and what available API's can be used as there are a lot more than just what is available on the Mach core API list now.

First thing on that list before we get that information out is having the new APIs documented. We are working on that process now.

When it comes to Mach4, I will be working on doing some bug fixes to try and provide a stable and solid product. There will just be no new planned features for the product.  This will take some time however.
10
MachPro General Discussion / Re: "Upgrading" from Mach4 to MachPro
« Last post by paul.stephens on February 20, 2026, 10:55:52 AM »
Currently, we don't support the old analog drives on MachPro. We are mostly trying to push into EtherCAT systems due to their reliability, safety, and functionality. At this time, the choices would be a Galil motion controller or a competitor like Centroid. At some point in the future, we may get Galil as a supported or certified motion controller, but there is no current ETA for that.

Current drives supported on MachPro when doing positional movements.
  • EtherCAT
  • Step and Direction - Differential - Open or closed loop
  • Step and Direction - Single ended - Open or closed loop (Can be done, not recommended due to reliability)

Current drives supported on MachPro when doing velocity movements. (Like a VFD)
  • EtherCAT
  • Step and Direction - Differential - Open or closed loop
  • Step and Direction - Single ended - Open or closed loop (Can be done, not recommended due to reliability)
  • +-10v Analog
  • Serial / Modbus
  • PWM
Pages: 1 2 3 4 5 6 7 8 9 10