cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Showing results for 
Search instead for 
Did you mean: 

Default tool path can cause collisions

YLocatelli
11-Garnet

Default tool path can cause collisions

Hello,

I am using Creo Pamaretric version 7.0 and I noticed that in Creo NC the toolpaths that the system generates can cause collisions. Even though the elements in the categories (Reference model, workpiece and fixture) are defined correctly, the default tool path created in Creo NC can cause collisions with a part or the environment. It is as if the system only takes into account the part to be machined and not the rest. Many CAM programs do not generate toolpaths if this could cause a collision. If this is the case, the calculation stops automatically and finds another solution. 

 

Is there any function or option to optimize the toolpaths and avoid collisions?

 

Thank you and best regards.

1 ACCEPTED SOLUTION

Accepted Solutions
BR84
12-Amethyst
(To:YLocatelli)

Hi there,

this behavior is one of two huge bugs in the cam module. /second are crashes with the patterns, patterns of fixtures, etc/

I have a walk around it by playing material removal simulation with colors.

It became so important for me, that there is a mapkey with a custom button in the ribbon for that...

 

have a good day.

 

!* material removal simulation
mapkey genmr ~ RButtonArm `main_dlg_cur` `PHTLeft.AssyTree` `node38`;\
mapkey(continued) ~ PopupOver `main_dlg_cur` `PM_PHTLeft.AssyTree` 1 `PHTLeft.AssyTree`;\
mapkey(continued) ~ Open `main_dlg_cur` `PM_PHTLeft.AssyTree`;\
mapkey(continued) ~ Close `main_dlg_cur` `PM_PHTLeft.AssyTree`;\
mapkey(continued) ~ Command `ProCmdNccheck@PopupMenuTree` ;\
mapkey(continued) ~ Open `main_dlg_cur` `maindashInst0.Precision`;\
mapkey(continued) ~ Close `main_dlg_cur` `maindashInst0.Precision`;\
mapkey(continued) ~ Select `main_dlg_cur` `maindashInst0.Precision` 1 `Very High`;\
mapkey(continued) ~ FocusIn `UI Message Dialog` `ok`;~ Activate `UI Message Dialog` `ok`;\
mapkey(continued) ~ Activate `main_dlg_cur` `chkbn.MW_DASH_COMPARE.0` 1;\
mapkey(continued) ~ Activate `MW_DASH_COMPARE.2.0` `PH.refresh`;\
mapkey(continued) ~ Activate `main_dlg_cur` `maindashInst0.PlayPath`;

View solution in original post

2 REPLIES 2
BR84
12-Amethyst
(To:YLocatelli)

Hi there,

this behavior is one of two huge bugs in the cam module. /second are crashes with the patterns, patterns of fixtures, etc/

I have a walk around it by playing material removal simulation with colors.

It became so important for me, that there is a mapkey with a custom button in the ribbon for that...

 

have a good day.

 

!* material removal simulation
mapkey genmr ~ RButtonArm `main_dlg_cur` `PHTLeft.AssyTree` `node38`;\
mapkey(continued) ~ PopupOver `main_dlg_cur` `PM_PHTLeft.AssyTree` 1 `PHTLeft.AssyTree`;\
mapkey(continued) ~ Open `main_dlg_cur` `PM_PHTLeft.AssyTree`;\
mapkey(continued) ~ Close `main_dlg_cur` `PM_PHTLeft.AssyTree`;\
mapkey(continued) ~ Command `ProCmdNccheck@PopupMenuTree` ;\
mapkey(continued) ~ Open `main_dlg_cur` `maindashInst0.Precision`;\
mapkey(continued) ~ Close `main_dlg_cur` `maindashInst0.Precision`;\
mapkey(continued) ~ Select `main_dlg_cur` `maindashInst0.Precision` 1 `Very High`;\
mapkey(continued) ~ FocusIn `UI Message Dialog` `ok`;~ Activate `UI Message Dialog` `ok`;\
mapkey(continued) ~ Activate `main_dlg_cur` `chkbn.MW_DASH_COMPARE.0` 1;\
mapkey(continued) ~ Activate `MW_DASH_COMPARE.2.0` `PH.refresh`;\
mapkey(continued) ~ Activate `main_dlg_cur` `maindashInst0.PlayPath`;

YLocatelli
11-Garnet
(To:BR84)

Hi BR84,

 

Thanks for your answer, I will test this method by coloring the material removal simulation.

 

Have a nice day.

Announcements