Hello Guest it is March 28, 2024, 02:20:26 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 3 »
11
During my trying to troubleshoot my spindle sped PWM not working (which turned out to be user error), I clicked the box in the PMDX plugin config to allow the PMDX-411 to update firmware. It reported that the new version was the exact same one as before, but I let it update anyway. The update went off without issue.

Now, whevenever I jog (key or arrow mode), it instantly hits a Motion Underrun error. I tried maxing the buffers out and it made no difference. I have been running this machine for over a year now and never saw this issue before so I don't think there's anything wrong with the PC. Literally the only thing I did was let this firmware update run. Any ideas?

12
To be fair though, it makes no sense that the "spindle RPM" box on the main screen lets you type a number in, but it does nothing. It had been long enough of a time gap that I had forgotten about all the quirk in Mach4 and how truly bad ArtSoft is at making intuitive and clean UIs. Sorry guys, it's true. You need to hire someone to help you make your UIs :).

13
Nm, fixed it. User error. :-/

14
So, I have a PMDX-411 SmartBob going to Gecko G540 with Mach4 and out of the blue the spindle is not getting a PWM signal. I have ruled out the VFD and my Gecko G540 and just today I probed pin 14 of the SmartBob with my o-scope in situ (with everything connected, Mach4 booted up, etc..) and I always get 0 volts regardless of if I'm sending a spindle on and speed or not.

Now I know this is the issue, but I technically have no way to prove that Mach4 is actually telling the SmartBob to send the PWM on pin 14. I only know that I'm not getting that signal. So, is there a way I can confirm that the software is indeed sending the signal?

I ask mainly because I've had ZERO success trying to contact PMDX for help with this (are they even still in business?) and am feeling like I'm kind of stranded here with this thing.

Thanks for any help!!

15
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!

16
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.

17
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?

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

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


https://www.machsupport.com/forum/index.php?topic=43260.msg279695#msg279695


Thanks! I will read that . Much appreciated

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

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

Bill

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')
else
if (SpinOn == 0) then
mc.mcSignalSetState(hSpin, 1)
wx.wxMilliSleep(5500)
--wx.wxMessageBox('Spindle ON')
end
end
end
if (mc.mcInEditor() == 1) then
m3()
end

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.

20
Hi,
Windows 7 Embedded (standard) 32 bit.

Craig

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.

Pages: « 1 2 3 »