Detect Flats values not being imported

[Thad]

When importing operations from other MCX files, do you think the Detect Flats values in the Cut Depths parameters should be imported too? I think they should, but they don't. I was going to report this to QC but wanted to get your opinions first.

 

Thad

[Thad]

Don't tell me I'm the only one who imports operations from other toolpaths?

 

Thad

[Kannon]

I would have to say everyone is missing your post Thad so I will give ya a

BUMP:

 

cause we know Keebler will respond even if he dont have a answer.

[John13]

I don't have an answer and am not going to reply just for the sake of replying. I have too much to do.

 

 

Sorry Thad, I don't import operations.

[beej]

Sorry, Thad, but I haven't used the old 3d paths since the HSM paths came out 2 versions ago.

 

But if I were still plowing with horses I would probably agree with you.

[mayday]

dont import Thad

buy American

[Midwest]

quote:

---

dont import Thad

buy American [Wink]

---

LOL @ MayDay

 

 

[Midwest]

I did some last week, but i blew away the geometry and kept the tool paths then imported the new geometry and picked the new surfaces / solids and depths, and regenerated........... didn't mess with the Detect Flats option. Sorry

 

 

Had to make 16 inserts for a mold that used similar tool paths.

 

 

[3R!< W3NG3R]

Thad, I would have to agree with you. I found that when importing ops from other files, you do have to go over it with a fine tooth comb.

[Troy Gossett Indepak Inc.]

Thad,

 

I agree with you when you import ops w/geo the detect flats limits should come through, but when importing without geo, the expectation is you will reselect new geo for the imported ops.

[Thad]

Thanks for your replies.

 

From QC...

 

quote:

---

I have logged this as bug number cnc00030522.

---

Thad