Community Tip - Visit the PTCooler (the community lounge) to get to know your fellow community members and check out some of Dale's Friday Humor posts!
X
We just installed Creo 2 M210 and it has Moduleworks. I ran a test and it stops at the tap cycle and I can't figure out why. Has anyone else ran into this? Also is there any help or training type stuff online somewhere?
I've tested a little bit Moduleworks provided with Creo 3.0 M100, and I didn't notice problems with tapping cycles. Do you use standard tapping cycles ?
Unfortunately, I don't think there is any kind of help for moduleworks. I think it has been implemented a bit to early. It remains quite buggy, so I'm still working with M080 which is provided with Vericut... much more efficient solution from my point of view.
What might be happening is it might be seeing the tapping as a collision with the stock. if you click on the view menu and uncheck stop at collision it might run through the rest of the program.
I had to do that with a couple of jobs.
the thing I miss with moduleworks that Vericut did well is the cut material used to be associated with the tool color now with Moduleworks it's all is the same rust red color. It's hard to tell what cutter left stock on and where.
Thanks, I did not have the stop turned on. What I did was temporarily suspend the tap cycle and it ran through it no problem. I was just testing an existing program that had run fine on the machine. I didn't really mess with it to much, Thanks for the help I am sure these other tips will get used in the future.
