Holder Collision not reported

MIKEFITZ · 2010-05-13 19:17:18

Hey all. Has anyone had a problem in which Collision Detection is on, a holder hits the stock, it turns red, but there is no message displayed in the logger, and the collision indicator light at the bottom of the graphics area stays green?

GavinP · 2010-05-13 20:08:03

File, Properties, Tolerance (tab), Minimum Error Volume = ??

Is it 0 ?

dwiehr · 2010-05-18 14:56:57

I have similar situation where tools will hit with shank and remove a LOT of material, show it in red and not report anything . The minimum error volume is set to 0. The attached image played until it finally threw an error at current position. To put the image into perspective, the part size is 2.86"x1.87"x.75". It appears that when the tool is cutting in an axial or helical movement is when we see this happen. It seems to catch it quickly when it happens in a radial movements as where the tool has stopped in the image. I hope the image works for this.

Dave

GavinP · 2010-05-18 15:57:08

File, Properties, Tolerance (tab), Cut Tolerance = ??

dwiehr · 2010-05-18 17:11:58

Cut tolerance is set to .005. I tried it at .001 and .0025 and it did detect the tool shanking a lot sooner but at a significant (unacceptable) slowdown of playback. This is the setting we have been using for years without problems till sometime after the release of v7. I'm not sure of what release though. I really hope you don't tell me that I have to increase the cut tolerance to catch these errors. There's got to be another way.

Thanks,
Dave

SergeV · 2010-05-18 17:46:31

Please send you files to Technical support. This is not normal

MIKEFITZ · 2010-05-18 17:47:29

This is just a guess, but I was told by some of the computer guys here at work that upgrading the video card would probably work to speed up the sim and thereby allow you to run a higher tolerance...unfortunately, vericut is the only serious thing i do on computers, and i wouldn't know the first thing to tell you about specs for a video card, but the way these guys explain it to me it sounds like that could help a bit, if you can afford to drop the dough.

dwiehr · 2010-05-18 18:10:15

Mike - thanks for the idea, but we are already running pretty high end Nvidia Quadro cards, although my particular PC is probably the oldest one here at work. It keeps pace with the other 32 bit machines. I really wish I had a 64 bit workstation. Sorry to hi-jack your thread, although I'm thinking that our two issues may be somehow related.

I'm going to send my file to CGTech and let them look them over. I'm hoping it is something simple. This is one of them issues that we have been living with for a while, while we try and tweak out other bigger issues. We are getting really close now, so I'm tackling the smaller stuff now.

Dave

MIKEFITZ · 2010-05-18 18:46:07

No worries Dave... it was worth a shot. I asked my computer guy what was in my comp, he said a mid-level Nvidia, which I hear is a pretty good brand. I don't know much more about it though. The only other thing I can think of for a shank hit is, if it's shanking out in Vericut, but not on the machine, or vice versa, is that the tool might be drawn wrong. Other than that, I've got no idea. Does your simulation alarm in the same spot every time? For example, if you restart Vericut, does it still give the same result? Sometimes I'll get some B.S. errors that go away if I restart....again, just a guess. Good Luck!

SergeV · 2010-05-18 21:11:15

Dave,

I have done a quick test to see what is happening with your files. We will investigate the reason of the shank collision not being detected, but in the meantime I have a solution.

If you separate your shank from the cutter and define the shank portion as a holder, then the collision will be detected immediatly.

Again, this is temporary solution, but a safe one

SergeV · 2010-05-21 16:19:13

We found the real problem. In FastMill cutting mode, the shape of the shank was not considered in the collision. This is now being fixed and will work the same collision detection will occur with or without FastMill.

Meantime, an easier workaround than rebuilding the tools is to disable FastMill and the collisions will be detected.

In the Project Tree, select the Setup branch
in the Configure Setup panel, un-check the FastMill checkbox
Save your Project.

dwiehr · 2010-05-21 16:52:55

SergeV - Thanks for the update. This is good news. Hopefully a fix can be out sometime soon. The FastMill fix is definitely an easier fix than remodeling all our tools... albeit very slow playback. We can deal with that till the update is released. Thanks again!

Dave

VERICUT Users' Forum

#1 2010-05-13 19:17:18

Holder Collision not reported

#2 2010-05-13 20:08:03

Re: Holder Collision not reported

#3 2010-05-18 14:56:57

Re: Holder Collision not reported

#4 2010-05-18 15:57:08

Re: Holder Collision not reported

#5 2010-05-18 17:11:58

Re: Holder Collision not reported

#6 2010-05-18 17:46:31

Re: Holder Collision not reported

#7 2010-05-18 17:47:29

Re: Holder Collision not reported

#8 2010-05-18 18:10:15

Re: Holder Collision not reported

#9 2010-05-18 18:46:07

Re: Holder Collision not reported

#10 2010-05-18 21:11:15

Re: Holder Collision not reported

#11 2010-05-21 16:19:13

Re: Holder Collision not reported

#12 2010-05-21 16:52:55

Re: Holder Collision not reported

Board footer