Hello Guest it is October 13, 2026, 07:56:09 PM

Recent Posts

Pages: « 1 2 3 4 5 6 7 8 9 10
91
MachPro General Discussion / Re: MachPro and Galil
« Last post by paul.stephens on September 14, 2026, 09:25:26 AM »
The Mach4 Galil plugin will not work for MachPro.

Modules,  Wizards, and PMC's can move over - assuming the dependencies are there and available for the object to move over. 

Any plugins will need to be compiled for 64bit applications in order to function.
92
MachPro General Discussion / Re: Plate Alignment
« Last post by paul.stephens on September 14, 2026, 09:20:29 AM »
Here is our documentation we have on plate alignment:

If you're using the GUI funcitons
https://support.machmotion.com/books/cnc-software/page/machpro-plate-alignment-and-transform-functions

If you're using the Gcode:
https://support.machmotion.com/books/cnc-software/page/machpro-g-code-and-m-code-reference#bkmrk-g68-%E2%80%93-coordinate-s

Let me know if you have any questions or issues.
93
M31 Motion Controller / Uninstall Machpro
« Last post by edcross on September 14, 2026, 07:24:08 AM »
How do i uninstall Machpro , so i can do a fresh install . It is not listed in the program section of the control panel ??
94
I’m troubleshooting an intermittent tool-setter input issue on a Mach4 mill and would like some advice from users who have dealt with similar signal-state problems.

The machine is running Mach4 with a dedicated I/O controller. The tool setter is a normally-open 24 V input. Under normal conditions, the input changes state immediately when the tool touches the setter, and the probing macro completes correctly.

The problem appears after using Cycle Stop or Reset during a probing operation. On roughly 1 out of 15–20 interrupted cycles, Mach4 still reports the probe input as active even after the physical switch has opened. Power-cycling the I/O controller clears the condition, but restarting the whole machine is obviously not a practical solution.

Current observations:

Input voltage: 24 VDC
Normal input response: approximately 20–30 ms
Mach4 build: current 2026 installation
Occurrence: approximately 5–7% of interrupted probing cycles
No visible mechanical sticking in the tool setter
The problem does not occur consistently during normal probing
The I/O controller's diagnostic screen sometimes shows the input correctly changing state while Mach4 still appears to see it as active

Before changing the hardware, I want to determine whether this could be related to Mach4 signal polling, PLC scripting, the probing macro, or how the input state is handled after Reset/Cycle Stop.

For those using Mach4 with a 24 V tool setter or probe input:

Is there a recommended way to force-refresh or verify an input state after Cycle Stop?
Would you troubleshoot the signal through the Mach4 Diagnostic/Input Signals screen first, or inspect the PLC/probing macro?
Is there a known difference between resetting the motion controller and resetting the Mach4 signal state?
What logging or diagnostic information would be most useful to capture when the fault occurs?

I’d prefer to identify the software/I/O state first rather than simply adding delays or replacing working hardware. Any practical troubleshooting steps or examples from a similar Mach4 setup would be appreciated.
95
MachPro General Discussion / Re: MachPro upgrade questions
« Last post by Tweakie.CNC on September 14, 2026, 01:14:10 AM »
At Steve's suggestion & with Craig's approval this thread has now been moved to the 'MachPro General Discussion' section.

Tweakie.
97
MachPro General Discussion / Screen Edit not saving.
« Last post by joeaverage on September 13, 2026, 07:45:52 PM »
Hi,
I've just started migrating from Mach4Hobby to MachPro.

One of the small changes I want to make is to have a <Zero (axis)> button alongside each DRO, much like the Mach4 screen set I am so familiar with.

With the scree editor open  I have located the  text axis label, "X" for example. Rather than delete it I've 'kicked it out' of the veiwable window by nominating
its location at1005, rather than at 05, when it is viewable. That works and when saved it sticks for the next MachPro session.

What does not work is when I drag the <Zero X> button from 1017 to 017. The button displays and I can try to save the screen edit but when a new screen is
drawn the button is absent. I've tried dozens of variations on editing the screen and the attempt to save it without being able to get the edit to permanently save.
The AI coach suggests that I use <F5> to ensure that a new Lua script is generated prior to saving.....and it seems that it does not work.

Has anyone had any similar experience?

Craig
98
MachPro General Discussion / Re: MachPro upgrade questions
« Last post by Steve Stallings on September 12, 2026, 09:31:54 PM »
You are posting in the Mach4 section of this forum. You might get more attention to your questions if you posted in the section for:

    Machsupport Forum
    /
    MachPro
    /
    MachPro General Discussion

99
MachPro General Discussion / Re: MachPro upgrade questions
« Last post by joeaverage on September 12, 2026, 05:49:28 PM »
HI,
WTF happened to the ScreenLoad script?

In Mach4 you could open it and edit it, and it included the SignalLibrary  table.......but now the script is not much more than a dozen lines. When you chase the modules that are loaded
according to those lines they are all compiled.....you cannot read nor edit them. WTF???? How is anyone supposed to add signals in to the Signal Library table?

Is this a means that MachLabs have used to exclude users from reading/editing their own software installation?

Craig.
100
MachPro General Discussion / Re: MachPro upgrade questions
« Last post by joeaverage on September 12, 2026, 05:34:23 PM »
Hi,
OK, I tried copying my current Mach4Hobby screen set (Mywx6Copy.set) into the screens folder of MachPro.
In MachPro's Veiw tab I can see and load the imported screen set, and the screen loads with errors, namely a lot of Lua scripts are missing.
The screen does load, and it looks to be identical to that same veiw in Mach4Hobby....BUT......many of the buttons and functions are greyed out,
so the screen set is not usable as is.

I seem to recall that there was something like an Export function in Mach4 that allowed you to export not only the screen set but also the Lua code snippets
that made it work, but do you think I can find it! If anyone can remember how that is done, I'd appreciate a reminder.

Moving on.......

I downloaded and opened a small Gcode file in MachPro, and tried to run it.

First thing that happened is that MachPro complained and errored out that the machine has violated SoftLimits. I tried turning SoftLimits off and still could not clear the error warning
and therfeore could not get the code to run. This rather suggests that SoftLimits MUST be enabled and set up otherwise you cannot run any code? Does this sound correct?

The I tried setting up SoftLimits, and because this is not hooked to my machine I wanted to manually jog to the SoftLimits locations and thus populate the SoftLimits table....but I cannot jog!!!!
I reverted to manually populating the SoftLimits table in the Control Plugin/Homing-SoftLimits tab, in the same mannere as I would in Mach4Hobby.  Thus I eventually was able to get
SoftLimits to work and thus am able to run the Gcode file.

This brings me to the fact that I cannot manually jog. In Mach4Hobby there was a jog window with the familiar X+, X-, Y+  etc buttons. Pressing said buttons caused the machine to jog.
In that same window you could set jog speed, jog increment, jog mode (absolute/velocity) etc........but there is no such screen or window that I can find in MachPro standard three axis screen set.
Surely it must be possible to jog in MachPro from the screen or keyboard?

I thought then.......'I know, I'll read the manual'......always a last resort, but guess what the manual is  the Mach4 manual, it has nothing about the new MachPro screen set.
WTF???? MachPro is a new version of otherwise familiar software, but the manual describes the PREVIOUS version........not much f******ing help!.

MachLabs need to, if not update but include, instructions for the screen set that they have created.

As far as I can tell ALL the documentation that is included IS the same documentation from Mach4. In the sense that MachPro is an evolution of Mach4 that's OK, but what about documentation
describing those changes that occur in MachPro???

I have built a manual wired jog pendant and have been using it for several years on my Mach4Hobby machine. It is very much how I touch off and otherwise set the machine up. Each of the wires is hooked
via my breakout board/ESS combo to input signals to Mach4. Each Mach input has an entry in the Signal Library table, and each of those entries calls scripts in the ScreenLoad script that enact
the jogging. I presume there must be a similar functionality in MachPro.......but where is it? Where is the documentation describing it?

At the moment I cannot use MachPro. I need my machine to function, and I cannot get MachPro to even match the functionality that Mach4Hobby has.

Craig
Pages: « 1 2 3 4 5 6 7 8 9 10