Hello Guest it is December 01, 2021, 02:28:21 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 - RGUERI1

Pages: 1
1
JoeAverage,
I've eliminated the M40 and M41 calls, from the G-Code, until I can get it probing more than 3-points without getting the Underrun Error. So at this current point, I'm just probing and not writing to any file. As I'm typing this, I'm wondering if that is part of the problem. Last week when I was working on it, the M40/M41 calls were still in the code and I was getting the error at random probe points. Sometimes it would successfully probe 5-10 points and then hang up. However, now it consistently errors out at point #1 or #3. Not sure why it's chosen those two spots but I haven't successfully probed more than three points in the last 30+ attempts.
I'll put them back in and see if anything changes.
Thanks

2
Been away from my machine for a while. I've updated to the 3805 build, as well as the latest dev build, and now I'm getting an "Error(7) Motion Underrun." I have tried to reinstall profiles, adjust millisleep setting, manually perform G31 through the MDI, changed computers and adjusted buffer settings in the PMDX-424 performance config tab, all to no avail.
Currently I get the error consistently on the 3rd-4th probe. I am also using the modified M40 and M41 scripts for parameter logging.
This is getting very frustrating and I seem to have hit a dead end.
Has anyone had success in creating a probe level map file? I have also tried the auto generated probe file from "G-code ripper", "Autoleveller AE" and "Autoleveller AL." I have even manually typed the G31 commands in, through the MDI.
I am currently at a loss. Any help would be appreciated.

4
Can someone direct me to the 3805 version? The website's latest download is still 3804.

5
JimDingus,
Thanks, I'll try it out.

6
I am having similar issues with my setup. It is a PMDX-424 and Mach4 with latest build 3804.
I think that I corrected the  "Can't transition from MDI running to stop" issue by adjusting the wx.milliSleep value to 70. However, now I'm getting a touch, retract, set tool1 offset and then a LUA error. (see below)
Any thoughts?
Thanks


Mach4 History readout:

Z axis is performing a touch move.
Z axis is moving to a requested machine position.
Tool 1 Height Offset Set: -19.7255
Lua: Error while running chunk C:\Mach4Hobby/Modules/mcTouchOff.lua:1178: attempt to compare nil with number stack traceback: C:\Mach4Hobby/Modules/mcTouchOff.lua:1178: in function 'frameMainOnUpdateUI'
       C:\Mach4Hobby/Modules/mcTouchOff.lua:912: in function <C:\Mach4Hobby/Modules/mcTouchOff.lua:911>




7
Mach4 General Discussion / Re: GO TO WORK ZERO - ERROR
« on: September 19, 2017, 06:04:21 AM »
Craig,
Sorry, haven't had time to respond. Your last post describes exactly how my machine was responding, and now that you mention it, that's exactly why.

Daryl,
Glad to hear you've got it working.

I've got a big name tag engraving project, I'm starting on. I'll let y'all know how it goes.

Rustin

8
Mach4 General Discussion / Re: GO TO WORK ZERO - ERROR
« on: September 17, 2017, 06:01:02 PM »
Craig,
Thanks for the info on saving the profiles. It looks like there will be plenty "tweaks" and I definitely don't want to lose them!

9
Mach4 General Discussion / Re: GO TO WORK ZERO - ERROR
« on: September 17, 2017, 05:59:03 PM »
I got it figured out, with the following code in the screen editor:

GoToWorkZero()
local inst = mc.mcGetInstance()
mc.mcCntlMdiExecute(inst, "G00 G90 G53 Z0\nG00 X0 Y0\nG00 Z0")


I found a couple issues, the first being the "--" at the beginning, which ignores anything following! However, I had to add the "G90" as well, to switch to absolute mode.
Not sure if I need to put a "G91" at the end, to go back to Incremental, or is that automatic for jogging?


10
Mach4 General Discussion / Re: GO TO WORK ZERO - ERROR
« on: September 17, 2017, 05:28:07 PM »
joeaverage,
What is the correct code, Just deleting the "A0" command? I get another error after I delete it. Also, what is the reason for going to "Z0" twice?
Any help would be appreciated.
Thanks
Rustin

Pages: 1