Topics

1

Mach4 General Discussion / Macro will not jog mill

« on: November 20, 2023, 02:09:46 PM »

It's my first Lua attempt, and a macro looked less challenging than a Lua panel.  I to code this -

After homing, I use the bit like an edge finder (turning it manually as I jog) and set the X and Y zero.  I then jog X and Y by 1/2 the bit diameter using the MDI (hopefully after raising the Z) and zero Z and Y again.  I verify that the cutter is centered over the corner of the workpiece. 

When I step through this code in the debugger, it works.  The axes jog and the work coordinates are zeroed.

function m1250()
   local inst = mc.mcGetInstance()
   local AxisJog = .125
   -- Jog controller 0 in the X and Y axes.
      mc.mcJogIncStart(0, 0, AxisJog)
      mc.mcJogIncStart(0, 1, AxisJog)
   -- Set the position of the X axis by changing the fixture offset.
      mc.mcAxisSetPos(0, 0, 0)
      mc.mcAxisSetPos(0, 1, 0)
end

if (mc.mcInEditor() == 1) then
   m1250()
end

When I run this from the MDI (m1250) on the CNC (or the Mach4-Demo), the coordinates zero, but the machine does not jog.
I think this tells me the macro is being compiled.  It is enabled.

I have deleted the mcLua.mcc file and restarted Mach4.

I suspect this has something to do with the Mach4 core versus the GUI, but I'm at a loss.

Can anyone suggest how to make the jog command work?

Thank you in advance for suggestions.


(I would guess the work coordinates could be changed without jogging, but I would like to move the machine to the new (0,0) to get visual confirmation.)

2

Mach4 General Discussion / Issues after reinstall of Mach4

« on: July 09, 2023, 01:15:52 AM »

My router ran flawlessly for two years.  Recently I had an issue with the tool path tool path progress stopping when Gcode was loaded.  Tech support could not resolve it and suggested a reinstall.  I reinstalled (v4300 to v5036), put all the settings back, and here are my issues.

Mach4 stops when executing a line with G90, G91, or G94.  G90.1 and G91.1 cause no problems.  Same results with the MDI.   Any ideas why they won't execute? These are common commands.   After removing them, I let the machine cut air for several minutes (with my mouse over the stop button) and it appeared to work fine except ...

Here's a bigger mystery to me.  The Z and Y axes move correctly.  When the X-axis is instructed to move 10 inches, the displayed machine coordinates change by 10 inches.  However, the displayed work coordinates change by about 15 inches and the actual motion is about 7 inches (appears to be a reciprocal relationship).  I have an x-soft limit set at 29 inches and could move the WCS X past 44 inches (at which point the machine coordinate was almost 29).  If the motor counts per unit (which I checked) were off in the setup, I would expect both coordinate systems to be wrong.  How can the displayed work coordinates move a different amount from the machine coordinates?  What do I check to resolve this?  I have no idea what to check.

Lastly, my estimated tool path does not appear in the tool path window nor do the soft limits.  I have not tried to solve this issue other than to do a few clicks.  I think that the first two issues might be related to this. 

I have a Pokeys57cnc control board connected by ethernet.

Thank you for any suggestions.