X5 2D Dynamic Core mill

[Tinhman]

Good morning Guys,

Another head up on X5.

2d Dynamic Core mill, the Z depth keeps changing on me and off exact 1 x dia of your tool.

Please watcth out for this. My vericut saved my day.

hope it helps.

[gcode]

Please send a sample of this to [email protected].

[Tinhman]

Will do

[Chris Rizzo]

Another thread on this.

Let us know what qc says. I run these toolpaths quite a bit and have not seen it, but this is a bit disconcerting.

[neurosis]

Same here. I use it very often and have not seen this issue yet. This is the second or third time ive seen someone say that there is an issue.

 

just out of curiosity, are you using depth cuts and or island facing when you get this issue?

[Bob W.]

I have been burned by this twice but the depth discrepancies were small (too shallow) so the parts weren't scrapped. The operations were clean when posted and the posted depths did not match the depths programmed in the operations. I sent to QC and they did see the discrepancy but couldn't figure it out. This is very frustrating because I use dynamic mill a lot and it was bulletproof in X4...

[Bob W.]

Same here. I use it very often and have not seen this issue yet. This is the second or third time ive seen someone say that there is an issue.

 

just out of curiosity, are you using depth cuts and or island facing when you get this issue?

 

The issues I ran into were during area clearance with no depth cuts. I was programming a part that was very similar to one I had done int he past so I saved a copy of the file, imported new geometry, reassigned all chains, reset depths, and regenerated. Everything went clean but the dynamic mill still didn't post correctly.

[neurosis]

Does the verifier show the difference in z depth? We dont have vericut in our shop so if this happens then we are more than likely going to get bit out at the machine. Our boss doesnt understand "there is a bug in the software" He only understands that a part was scrapped.

[Bob W.]

I believe verify did show it but the error was small (.015") so unless I was really looking for it I would miss it.

[Tinhman]

Done, i just sent the file to QC.

Yes, it did show in back plot and verify.

[frostfritt]

The issues I ran into were during area clearance with no depth cuts. I was programming a part that was very similar to one I had done int he past so I saved a copy of the file, imported new geometry, reassigned all chains, reset depths, and regenerated. Everything went clean but the dynamic mill still didn't post correctly.

 

Bob,

Try to add a stock to leave and regenerat again. That work for me.

 

/frostfritt

[Bob W.]

IT JUST HAPPENED AGAIN! Posted a clean op that was to machine to 1.000" deep and it machined to .955" deep. Better too shallow than too deep I guess. Regenerating once left it at the same depth of .955 and regenerating a second time put it down at 1.000" where it should be.

[neurosis]

Is the operation using the depth of the chain that you are selecting? Incrementally or otherwise? There has to be some explanation to what is going on (a bug sure) but I cant imagine that it changes the numbers randomly. With the new bells and whistles this operation has being able to use island depths and faces, I wonder if it is some how using the chain geometry to set its depth some how.

 

I need to get more free time to play with this. I still have not see this happen but its starting to worry me.

[Bob W.]

HA! I played around with it and I finally got it to repeat.

[Bob W.]

I machine molds that have identical features, just different sizes. What I will do is import the new geometry, create a WCS at the reference feature and change all operations to this new WCS (edit selected operations - edit common parameters - planes), then regenerate. All operations are programmed to absolute depths and upon regenerating they all went to the correct depth except the dynamic milling.

[neurosis]

Was anyone ever able to get this reported as a bug? I am starting to notice this happening quite a bit now. Mostly the z depths have been on the shallow side but they are not being driven at the numbers that are set in the z depth fields. My z depths have been off as much as .05 from the numbers set in the z depths on three separate dynamic paths in the same part.

[Bob W.]

I reported it as a bug and they were able to repeat the problem so hopefully there will be a fix in the near future.

[K2csq7]

Does anyone seeing this problem have a Min/Max program depth output in the post, if so does it reflect the bad depths?

[neurosis]

I dont use the min/max depth output in the post but I would assume that it would. It shows up in verify and in back plot. For some reason the the tool path does not reflect the numbers being entered in the z depth fields. This is a huge issue! I hope that it gets fixed right away.

[Mike Whitten CAD/CAM Contractors]

I have also gotten this issue several times. It was off by about .05 shallow. No depth cuts were used. I can't find any pattern to it, it just happens.

[Chipmakr]

I have been bitten by this numerous times this week. With a 1/2" tool I had Z-.450" in the input box that backploted and posted at Z-.150. With a 1/4" tool I had a Z-.100"in the input box backplotted and posted at Z-.050. I had a couple of others variations of this problem too, but you get the picture. Sometimes just opening it up and then regenerating fixes it sometimes it doesn't.

 

I sent the file to my reseller and will forward it on to QC now. This needs to be fixed quickly.

[neurosis]

this is bad enough that is should be released as a patch. at least the values are always off in a positive direction. this can cause some real issues for finishing tools.

 

the first time this happened to me we missed it in verify and caught it at the machine. we were milling two sides of a part. one side posted fine and the other did not. It mashed our finisher. I double checked the values and they were identical for both sides of the part. i had to open the operation and regen several times before it fixed the issue.

[Chipmakr]

I recieved a reply from the QC inbox asking for more infromation about my file, has anyone heard anything from MC about a fix for this?

[neurosis]

I havent sent a file in but I have made them aware that there was an issue. I have not heard anything back. I am not sure how serious they took me.

 

I may have to create a file and see if I can re-produce this. So far it has been hard to determine what causes it so it is not easy to reproduce.

[Tinhman]

This is from CNC software. i am sorry guys i did not buy it.

 

-------------------------------------------------

You’re using a custom WCS as your toolplane and you defined a new origin. What you see as an absolute depth in the parameters is not going to match what is output in the NC file.

---------------------------------------------------

 

I used absolute mode, so the depth that i entered in the mastercam parameter should match with the value in my program.