I need to know whose error this is...

[venom51]

so I can blame the correct offender.

Tue - 23:56:08 ---Error on line: 882 - Internal error <DoOEMButton>
Tue - 23:56:08 ---Error on line: 854 - Internal error <DoOEMButton>
Tue - 23:56:12 ---Error on line: 854 - Internal error <DoOEMButton>
Tue - 23:56:12 ---EStop Button Pressed.
Tue - 23:56:23 ---Error on line: 854 - Internal error <DoOEMButton>

[DaveCVI]

I don't know what is causing the errors, but I'll help figure it out with you.

That looks like a script error (maybe), possibly a MSM script since the line numbers are in the 800s and MSM is about the only mach package I know with scripts that large.

Let's start with:
1) what version of mach are you running?
2) what version of windows ?
3) what version of MSM?
4) where are those error messages showing up? In the history (lasterrors) log file?
5) Can you cause this to happen, or is it intermittent?
6) what were you doing when the error(s) occur?

Dave

[venom51]

Mach 3 Version R3.043.066
Windows 7 32-bit
Dual Quad core Xeon machine 8 gigs of Ram <---yes I know it can only address 4 in a 32 bti OS.
MSM V2.09
Error message shows up in the LAstError.log file.
Seems to be pretty consistent while trying to drill 4 simple holes. Standard drill cycle.

Also I'm getting some odd issue while probing. Occasionally the probe will not traverse the hint distance and prematurely drop down to probe the edge of the part before it has reached the distance required. No false triggers on the probe when it happens.

[DaveCVI]

Mach 3 Version R3.043.066
Windows 7 32-bit
Dual Quad core Xeon machine 8 gigs of Ram <---yes I know it can only address 4 in a 32 bti OS.
MSM V2.09
Error message shows up in the LAstError.log file.
Seems to be pretty consistent while trying to drill 4 simple holes. Standard drill cycle.

Is this happening while running a gcode program?
What is the source of the gcode? (A mach wizard perhaps?)
Has this code ever been run successfully before?
If so, what has changed (I'm searching for clues)?

Can this be narrowed down to a short test case along the lines of "these 3 lines of gcode make the error happen"?
I'm puzzled since the error refers to a button action and those happen from screen control events (press a button) rather than from running gcode...
Is there a screen button in use that corresponds to when the error happens?

Also I'm getting some odd issue while probing. Occasionally the probe will not traverse the hint distance and prematurely drop down to probe the edge of the part before it has reached the distance required. No false triggers on the probe when it happens.

First thought is that this sounds like a separate problem since I assume no probing is going on while drilling holes - so I suggest concentrating on the error messages first and we'll come back to this one.

Dave

[DaveCVI]

I forgot to ask:
Is your machine using a Parallel port or SS USB or SS Enet or some other motion control device?
Dave

[venom51]

Entirely right. The probing issue is one I can work around and it can wait.

Machine is on a parallel port. The Mach diag tool looked good when I ran it at 65k. I backed it down to 45k as I'll never run the machine faster than feed rates that will produce.

I'll set back up tonight and document the usage pattern when it happens. Normally it's load G-code, Probe the part for zero, start program, tool change and measure TLO, and start drilling. Last night when it happened the table hung and missed a couple step so I hit the stop button and then the estop. I re-homed the axis that hung and rewound the code and re-ran the code. That seems to be when it starts to happen.

I've also seen the MDI stop working after issuing a tool change and won't work again until either hitting the estop and or issuing another M6.

[venom51]

Well...I couldn't make it happen tonight. I have to finish up the project tomorrow so if it does it I'll be sure to document.

[DaveCVI]

OK, we'll pick this up again when there are some more clues to follow.
Dave