Question
Question on if bug in ProE Manufacturing crashes your CNC machines what can you do about it? Rant..
Good morning,
I am running into a situation where when I went to WF5 M220 and in
the couple months I have crashed my vertical CNC machine. First time milling
aluminum with a 2" inserted cutter running at a little over 200 ipm the tool
was at the bottom of a pocket and the code tells it to feed right into a
part. It totally destroyed my spindle on the mill. I had to replace the
spindle and all PTC can say that they will submit it as a SPR to R&D. that
happened in May of 2013 case number #C11370982. The next problem happened in
January of 2014 where it destroyed my mold core that I spent 32 hours of
machining case number #C11839437. The latest one is February 25, 2014 where
the tool went thru my part at 1" depth and snapped the pull stud seized up
the taper inside the spindle. The weird thing was on this last one I ran
through gouge and vericut with a 2" cutter before I release the program to
the floor and it was fine. While running the program we ran out of Y axis
travel so I swapped the tool to a 1" and shrink the window smaller to
compensate the new tool. I figure that I did not change nothing else just to
run gouge check and skip the Vericut because it takes almost 20 minutes to
recode the code for Vericut. I was in a rush and since gouge check said it
was fine I paid for it again case number #C11875717.
All of these showed no gouges when ran through gouge check but if you zoom
into it you can see the extra move that cause the crashes. The last incident
did show in the embedded ncl Vericut but was fine in gouge check.
My question is with all these crashes that my company ends up paying to fix
the damages that was cause by ProE and all I get is "We will send it to R&D
and get back to you on it". I feel that I am doing all there quality testing
for them and I use their software at my own risk. At the moment everybody in
the shop are scared to run a program since I cannot explain to them why the
other crashed and the only thing I can say is "a bug in ProE".
What can I do?
I figure like if I buy a car and it takes off on its own and crashes into a
building not once but three times so far and that I can prove that it is not
the user and it is the car. Should I be responsible for all the damages that
the car caused?
I am frustrated with ProE right now. I love using it but lately I feel like
they are not doing better with their quality. If it keeps up I know
management will tell me to look at other CAM packages, I don't want to
because our engineering department uses ProE to design and it will suck to
use a translator to convert ProE parts to another CAM system.
Son Nguyen
108 w. 2nd Street
Assaria, KS. 67416
(785) 667-7763 ext. 3477
This thread is inactive and closed by the PTC Community Management Team. If you would like to provide a reply and re-open this thread, please notify the moderator and reference the thread. You may also use "Start a topic" button to ask a new question. Please be sure to include what version of the PTC product you are using so another community member knowledgeable about your version may be able to assist.
I am running into a situation where when I went to WF5 M220 and in
the couple months I have crashed my vertical CNC machine. First time milling
aluminum with a 2" inserted cutter running at a little over 200 ipm the tool
was at the bottom of a pocket and the code tells it to feed right into a
part. It totally destroyed my spindle on the mill. I had to replace the
spindle and all PTC can say that they will submit it as a SPR to R&D. that
happened in May of 2013 case number #C11370982. The next problem happened in
January of 2014 where it destroyed my mold core that I spent 32 hours of
machining case number #C11839437. The latest one is February 25, 2014 where
the tool went thru my part at 1" depth and snapped the pull stud seized up
the taper inside the spindle. The weird thing was on this last one I ran
through gouge and vericut with a 2" cutter before I release the program to
the floor and it was fine. While running the program we ran out of Y axis
travel so I swapped the tool to a 1" and shrink the window smaller to
compensate the new tool. I figure that I did not change nothing else just to
run gouge check and skip the Vericut because it takes almost 20 minutes to
recode the code for Vericut. I was in a rush and since gouge check said it
was fine I paid for it again case number #C11875717.
All of these showed no gouges when ran through gouge check but if you zoom
into it you can see the extra move that cause the crashes. The last incident
did show in the embedded ncl Vericut but was fine in gouge check.
My question is with all these crashes that my company ends up paying to fix
the damages that was cause by ProE and all I get is "We will send it to R&D
and get back to you on it". I feel that I am doing all there quality testing
for them and I use their software at my own risk. At the moment everybody in
the shop are scared to run a program since I cannot explain to them why the
other crashed and the only thing I can say is "a bug in ProE".
What can I do?
I figure like if I buy a car and it takes off on its own and crashes into a
building not once but three times so far and that I can prove that it is not
the user and it is the car. Should I be responsible for all the damages that
the car caused?
I am frustrated with ProE right now. I love using it but lately I feel like
they are not doing better with their quality. If it keeps up I know
management will tell me to look at other CAM packages, I don't want to
because our engineering department uses ProE to design and it will suck to
use a translator to convert ProE parts to another CAM system.
Son Nguyen
108 w. 2nd Street
Assaria, KS. 67416
(785) 667-7763 ext. 3477
This thread is inactive and closed by the PTC Community Management Team. If you would like to provide a reply and re-open this thread, please notify the moderator and reference the thread. You may also use "Start a topic" button to ask a new question. Please be sure to include what version of the PTC product you are using so another community member knowledgeable about your version may be able to assist.