Mazak Post Processor errors

[HillJack]

I having a problem with our mazak mill post processor in v8. I adds "NEL.MC8" in place of "G00" throughout the program. It's a large 3-d surfacing file. We have tried several different things to get rid of it, but aren't getting anywhere. Any suggestions? Thanks, Shawn

 

[Andreas Stute - InterCAM]

Hi,

send your request to CAMaix, they are the big Mazak gurus.

[email protected]

 

Andreas

 

[HillJack]

Thanks for the info. I'll give them a shout. Shawn

[Dean Lindblad]

Does "NEL" happen to be the last three letters of your file name? I have seen the same thing happen when the file and path name get up close to 120 characters long. If so, try shortening the name and see what comes out then.

[HillJack]

Dean,

This is how my program begins:

 

O0000 PROG (4900.NC)

G90 G80 G40 G00 G54

N10 T1 T0M6

S4500 M03

NEL.MC8 X11.8185 Y-.4408

G43 H1 Z6.5

It doesn't do it on the smaller 2D programs, just the larger 3D. Could it be something in the data? Shawn

 

[Dean Lindblad]

Shawn,

The name I was referring to is the .MC8 geometry filename. If your file is named something like "channel.mc8" the "NEL.MC8"could be coming from there. Their seems to be a weird bug in Mastercam that allows this to happen when the entire path and filename approach 120 char. long. I've seen it happen with my mpfadal post. When I shortened the filename the problem went away.

[HillJack]

Dean,

That was it! I shortened the file name and re-posted it and it went away. The last word in the file name was "panel" so that's where the "nel.mc8" was coming from. I wonder if Mastercam knows about that? Thanks a bunch Dean. If I had a Christmas Card List, I put you on it! Shawn

[Guest CNC Apps Guy 1]

Please note: When you find "anomalies" in the software (that you can reproduce) call you dealer and send an e-mail to [email protected] That is the best way to know that Mastercam knows about it.

When e-mailing QC, tell them what Operating System you're running, CPU specs, RAM, Video Card Manufacturer, what other software you have running in the background and most importantly how to reproduce the "problem".

James Meyette