X6 failure in 2D dynamic HST

[left coast lefty]

I glitched an expensive copper piece yesterday using X6. I downloaded it Monday and quickly liked the much faster Verify. Ran 2 programs OK, then the Toolpath and verify looked good, but it overcut in at least 3 places.

Sorry if this was touched on in another thread.

 

this is on a Toshiba laptop with Win 7, 64 bit. i7 processor

2D HST SCREWUP.MCX-6

[Leigh @ Kodiak]

Like you say, it looks good in verify and backplot. Where exactly did the overcuts happen? Are your programed feeds and speeds the same as what you ran on the machine?

[left coast lefty]

It bumped into the outer pocket slightly (.06 inch), then into one of the bosses, then again into the outer pocket at which point the tool broke, so I'm not sure how far it was going to go. I tried to check the code, but I have no evidence that anything is wrong with the machine. Also, the same program ran fine in X5 today.

[Thee Rickster ™]

Almost sounds like the toolpath has decided not to compensate offset for the cutter

[K2csq7]

Also, the same program ran fine in X5 today.

If you post the program with X5 & X6 then do a file compare you will see the differences, help ya narrow it down...

[gcode]

did you check to make sure your converted X6 post was outputting good code???

[Thee Rickster ™]

Gcode

 

does that mean the conversion tool for the post update has a bug that needs fixin?

 

If you post the program with X5 & X6 then do a file compare you will see the differences, help ya narrow it down...

 

Kieth where in mastercam would you find this file compare tool?

 

Any 3d surface path would be impossible to compare

 

I dont think i can take a chance on scraping a whole mold base because of this.

[left coast lefty]

I ran two similar programs without a hitch. I was running a .04 stepover, I had to increase it in order to attach the file here. It ran a huge amount of code before it screwed up. All the dimensions were good, except for the overcuts, so it wasn't an offset issue.

[gcode]

Gcode

 

does tat mean the conversion tool for the post update has a bug that needs fixin?

 

 

 

Kieth where in mastercam would you find this file compare tool?

 

Any 3d surface path would be impossible to compare

 

 

no... sometimes when you attach a new post to the control def.. the control def reverts to default arc settings .... as in R's instead of IJK's

[Thee Rickster ™]

OK,

 

I dont think i have ever changed those settings so I will scratch that off my worry list.

[Joe788]

Sorta sounds like your machine is just under/over shooting corners. It's pretty rare to see interpolation moves that don't match the backplot.

 

Are your toolpath filter settings different between your X5 file and your X6 file? This will display basically the same in backplot, but the NC control may read through one set of code faster or slower, causing a gouge?

[Leigh @ Kodiak]

If you email me a zip2go file I will try posting it with your machine,control and post and see if anything looks out of whack. Posting it with the generic haas post and nothing looks odd in Cimco backplot. A .06" gouge should easily show up in backplot.

 

[email protected]

[left coast lefty]

Leigh--e-mail sent. Thanks!

[CamMan1]

If you have Cimco Edit you can run the code thru backplot. I posted it out and looked at it in Cimco backplot and it looked fine

[left coast lefty]

Thanks guys, I appreciate the help. Bottom line is the same program that failed in X6 worked in X5. I did not change a thing. I would think that rules out machine error. I checked the Control Def. and it is the same.

[Zoober]

I use ExamDiff compare program.

Compare two 30 meg programs down to the character, Without breaking a sweat. Best compare program I've ever used. For around $35 US

[Joe788]

Thanks guys, I appreciate the help. Bottom line is the same program that failed in X6 worked in X5. I did not change a thing. I would think that rules out machine error. I checked the Control Def. and it is the same.

 

Have you tried comparing the two different posted programs in the free Cimco that's included with Mastercam? Just do "File Compare".

[K2csq7]

Have you tried comparing the two different posted programs in the free Cimco that's included with Mastercam? Just do "File Compare".

+1^ I use it anytime I change a program, just to make sure the only changes are the ones I wanted.... works great.

[Zoober]

Cimco is fine for a limited number of differences.

But for huge files, it just errors out too many differences.

I don't know what cimco's limit is, but it is too small for dynamic and surface progs.

I have done 100 meg files in ExamDiff.

[Joe788]

Yeah it finds every single little difference, which can be overwhelming. I just feel like Lefty's X6 program probably posted differently due to different machine/control def settings, or different toolpath filter settings, causing the machine to react differently to a toolpath that should be the same.

 

In all my years of using Mastercam, I've never had the post output interpolation moves that don't match the backplot, other than issues with using R instead of IJK.

[Zoober]

Yes it does find every difference.

BUT......

You can also set up ignores to ignore certain differences like N numbers, white spaces, comments, or anything else you wish to ignore differences of.

You can even ignore the ignores.

[mig]

I glitched an expensive copper piece yesterday using X6. I downloaded it Monday and quickly liked the much faster Verify. Ran 2 programs OK, then the Toolpath and verify looked good, but it overcut in at least 3 places.

Sorry if this was touched on in another thread.

 

this is on a Toshiba laptop with Win 7, 64 bit. i7 processor

Can you shaw , where exactly you have this problems ?

To me looks like you can have just cutter deflection.

[left coast lefty]

Many thanks to all who chimed in. I have done a file compare, and the code is very different. I cannot find any differences in the Control def, there are no "R's" or anything that looks suspicious. If something changed it must be pretty obscure, because I updated to X6 as instructed. Are there any specific areas in the Control def (or Machine def) that are known to have issues when updated?

[Joe788]

Is the code significantly longer, or shorter, or about the same?

[gcode]

Have you enabled the advanced filter in X6 ... and made sure the settings are the same