All Collision Check Macro

igor · 2014-05-16 18:33:03

Hello everyone,

I need some help about this topic,
It would be great if we could be sure all "Machine Collisions Detection" are toggled "On".
Many times here, the other programers, start the simulation without look this thing, and after ready, all the program need to be simulated again with right conditions.
The same happens with the field "Check Collisions Between" in "Collisions" at project tree.

I would see a macro like "CollisionCheckAll" and it Override Value
= 1 - All collision will be checked
= 0 - No collision will be checked

And even with that, we can choose stop or not the simulation at a collision in "Start Menu".

An observation, there is a CollisionCheckOnOff macro, but this only makes sense if you want to turn off the collision check at a specific point, cause this macro is ignored when collision detection is toggled "Off".

If anyone know how can I do that, and tells me how, I would be greatful, however I don't find nothing like that in my searches.

Thankful for the attention,
Best regards,

Last edited by igor (2014-05-16 18:35:32)

MustaphaC · 2014-05-19 07:46:59

If at least one collision pair is defined and collision detection is turned off, when the simulation is started VERICUT will generate this message: "Warning: Collision Detection has been turned off.". This should be sufficient for the NC programmer to turn it ON and restart the simulation?

igor · 2014-05-19 16:41:30

Yeah, I think so, but my boss doesn't....rs

Lesley M · 2015-07-01 12:24:06

Hello,

is there any news on this topic?

We have exactly the same problem as Igor explained.
Programmers sometimes don't see that the Machine Collision Detection has been turned off.
We all know the potential consequences ...

What Mustapha explains works indeed, but this warning message is only given once, at the start op the simulation.
We use multiple setups in combination with IP files. For each setup individually the Machine Collision Detection can been turned off.
I would prefer VERICUT to repeat this warning at every setup. Would that be possible?

On the other side, a macro turning the Machine Collision Detection on would still be very useful.
We could call this macro in the events at the start of processing to make sure the the Machine Collision Detection are on.

Kind regards,
Lesley

igor · 2015-07-02 16:47:14

Lesley,

I didn't receive any information about this, but, some weeks ago I was searching for other topic and I found 2 macros that could help:

CollisionOnCutPart
CollisionCheckOnOff

I use both for control the collision, but the settings in Machine and Project tree must be "On"...

For control the flags of machine collision and project tree, I am making a VBA macro that writes the mch and vcproject files with all the standards settings...

but, now I need another related topic...

I asked cgtech BR for a enhacement...I would like a macro that controls the near miss error...Cause many times Vericut reports some errors like:

"Error: Holder "Holder1" of the tool "10007" loaded in component "Tool" exceeded near miss tolerance (1.5) with "Fixture" at line: (917) N3225 G0 G64 Z=R10"

As example, yesterday I simulated a Tool that machines the Cam Bore of a engine block, but this tool has cutters and guides, and all time of this simulation, vericut send messages like that above, but this exceed near miss don't make sense in tools like that....I really need a macro or tool that I could turn off or on this verification.

Lesley M · 2015-07-03 10:50:47

Igor,

we are also thinking about making our own macro's to check or set some critical standard settings in VcProjects.
This allows to do almost anything, but after changing the VcProject file, it needs to be re-opened in VERICUT...

About the near miss problem: can't you put the near miss to zero between tool and fixture?

Lesley

igor · 2015-07-03 13:07:43

Lesley,

With VBA you can open the vcproject file and search for "<Collision Detect="on" Ignore="active">" and change "on" for "off" and so on....and I think it's possible to automate when open the vericut file, runs this macro...

And about near miss, That's is the problem, I don't want put zero cause in this way, all warnings will be "hidden" and I just want in specific tools turn off this check. Again, I know this seems to be redudant, in the way I can stop the simulation at this tool, flag off the box of near miss, and run the tool. But the others programmers don't have sufficient knowledge to do this.....

Verifun · 2015-07-04 00:04:11

igor wrote:

Lesley,
...and I think it's possible to automate when open the vericut file, runs this macro...

Not sure about that... that would have to happen before launching vericut... or before pushing file open.... is that what you meant?

Last edited by Verifun (2015-07-04 00:04:49)

igor · 2015-07-06 13:07:37

I thought it is possible to start a macro by Vericut batch file....It's just an ideia, I don't know if it really works...

Or runs a macro that search for all vcproject files and changes this settings, every 30, 60 minutes - but this will cause some problems, like process time, and that problem still could happen.

Lesley M · 2015-07-07 09:29:10

Hi Igor,

It is possible to start an exe file from a bat file:
"C:\...\... .exe"

You can also give it some arguments:
"C:\...\... .exe" %1 %2 %3 %4
(where %1 could be the path to the first file you drag-dropped on the bat file)

I'm not sure it's the best way but that's how I do it in some other applications.

Kind regards,
Lesley

DaveF · 2016-01-05 17:06:37

Interesting topic discussed at the lunch table at may VUE’s.

What other managers say …. “ I can only trust half the users to run Vericut”
I like your idea of a macro. Seems like it will solve the problem.

I have three suggestions you can use today.

1. Many companies deploy a double check. That means a coworker or specialist will check Programmer A’s vericut when A is done. I spent a few years spending half my time as the double checker. It amazes me how much is missed. I did a training initiative to solve a lot of that problem.

2. What I always do when running Vericut, is use a check list. I do this in excel with check boxes for Autodif, Machine sim, Collision check, Optipath, recheck after OP, etc.

3. There is a Vericut Free module meant to solve this exact problem….( Problem = Can’t rely on the programmers to check all they are supposed to). That tool is the Custom Interface. To see what I am talking about… Go into help, Vericut Menus and Features+ File Menu + the Custom Interface.
Basically …the Custom Interface allows you to create a Go-By set of panels you customize to take the Vericut user step by Step thru Vericut tasks.

Dave

VERICUT Users' Forum

#1 2014-05-16 18:33:03

All Collision Check Macro

#2 2014-05-19 07:46:59

Re: All Collision Check Macro

#3 2014-05-19 16:41:30

Re: All Collision Check Macro

#4 2015-07-01 12:24:06

Re: All Collision Check Macro

#5 2015-07-02 16:47:14

Re: All Collision Check Macro

#6 2015-07-03 10:50:47

Re: All Collision Check Macro

#7 2015-07-03 13:07:43

Re: All Collision Check Macro

#8 2015-07-04 00:04:11

Re: All Collision Check Macro

#9 2015-07-06 13:07:37

Re: All Collision Check Macro

#10 2015-07-07 09:29:10

Re: All Collision Check Macro

#11 2016-01-05 17:06:37

Re: All Collision Check Macro

Board footer