Hello Guest it is June 20, 2021, 08:04:44 PM

Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - devinw

Pages: 1 2 »
So, I've been cutting all kinds of stuff on my router with multiple programs (1 per tool), but now that I got the basic Mach4 manual tool change working, I am trying some programs with 2 tools. Both times I've had the same problem where the program pauses and says to load tool 2, so I do so, then find the top of the part with the new tool using jogging, using a piece of .3mm shim and then offsetting .3mm and hitting Zero Z, but then when I resume the program, the height is off, too high.

The program is supposed to cut all around a 2mm thick panel and go Z-2.1 (I opened the Gcode and verified), but I watched while the prgram was running and it was at some weird number like Z -1.2475. I don't know why it would do that. Even if I had forgotten to re-zero, wouldn't the program still just go to Z-2.1 and then have the offset be all screwed and possibly crash? Where the hell did it get -1.2475 from? It's not even in the code.

Any help much appreciated!

Well, Trevor over at Newfangled helped me build a new profile and the settings retain now. Apparently the profiles that come with  the PMDX-411 driver are backdated and missing some things, so beware of those following instructions from PMDX starting with their PMDX profile as a basis. I would start with the Mach4-Mill profile in the version of Mach4 you have just installed.

Also, Trevor confirmed the "Apply" button being grey in the Tools tab is a bug, and they are going to work on it. It still saves settings to hit "OK" instead of Apply thouh.

Like the title says, if I change ANYTHING In the tools tab of config, the "apply" button remains greyed out. If you hit ok and come back, none of the settings stay. This is the case in numbers field like "Max tools" or the radio buttons. All the other tabs work and save fine. What the hell am I doing wrong?

Mach4 General Discussion / Re: spindle dwell before run
« on: August 04, 2020, 12:34:42 PM »

This might help in the understanding.
Go to the bottom to get the newest version.


Thanks! I will read that . Much appreciated

Mach4 General Discussion / Re: spindle dwell before run
« on: August 04, 2020, 11:35:13 AM »

I ended up making a custom m3.
This has some extra things in it for my machine but it might help.


Code: [Select]
function m3()
local inst = mc.mcGetInstance()
--Get Spindle On and Spindle Auto handles
local hSpin = mc.mcSignalGetHandle(inst, mc.OSIG_SPINDLEON)
local hreg = mc.mcRegGetHandle(inst, 'iRegs0/SpindleAuto')
--Get spindle on state
local SpinOn = mc.mcSignalGetState(hSpin)
--Get Spindle Auto value
local SpinVal = mc.mcRegGetValue(hreg)
if (SpinVal == 0) then
mc.mcSignalSetState(hSpin, 0)
--wx.wxMessageBox('Spindle OFF')
if (SpinOn == 0) then
mc.mcSignalSetState(hSpin, 1)
--wx.wxMessageBox('Spindle ON')
if (mc.mcInEditor() == 1) then

Nice, I'm sure that works, but that is pretty advanced for me lol. I'm gonna have to read up a LOT to even understand what's going on there :D.

Windows 7 Embedded (standard) 32 bit.


Aha. That's probably the difference. This PC had Win 10 64bit. Came with the PC. Windows 10 is bloat city compared to 7, which was already bloated! But, 7 is also getting pretty old and not even supported by MS anymore.

Mach4 General Discussion / Re: spindle dwell before run
« on: August 03, 2020, 02:52:49 PM »
In a situation where you don't have feedback to mach4 of the actual RPM coming from the VFD, how do you make sure the spindle waits to spool up before moving? Do you check that "override" option only? I tried this last night and my code still just started ripping before the spindle was even ready.

Mach4 General Discussion / Re: Won't generate tool paths
« on: August 03, 2020, 11:37:14 AM »
Well, I don't know what I did, but it seems to work for now. I even ran some code. Fingers crossed.

I have a dual core Atom (with on chip graphics) running my machine in conjunction with an Ethernet SmoothStepper
and its run flawlessly for five years.

I don't know why Mach seems to consume that much CPU power, on my installation it seldom gets to 5% and I've never seen it go beyond 10%.


Wow, that's nuts. What OS you on? I wonder why I would have such wildly different results? It was a brand new computer out of the box too, with virtually every extraneous thing I could turn off shut down in Win 10.

Cool, yeah, thanks. After a full reboot and and power cycle, it seems OK for now. I was setting up limit switches and motors and all that so stopping and starting the machine a lot. Hopefully it will remain ok.

Pages: 1 2 »