VERICUT Users' Forum

moudy

Member

Registered: 2004-11-11

Posts: 19

Catch a word without an address?

Can Vericut catch a word without an address and then throw an error?
If I have a line..
G1 -1.234 Y5.6 F7.
I would like Vericut see that the word -1.234 has no address and throw an error.

Thanks

SergeV

Senior Member

From: Irvine, CA

Registered: 2004-10-08

Posts: 507

Website

Re: Catch a word without an address?

Hi Clayton,

The control in VERICUT is based on a Word/Address format. When a line is read, the line is separated in word and value pairs.

Your line would read G[1 -1.234] Y[5.6] F[7.].  So by default, there is no mechanisms to detect this type of errors, but there might be a way around it.

If you never use spaces between the words and addresses, there might be a work around. The worst that would happen is to get false errors in VERICUT, which is not as bad as an error on the machine.

Setup > Control > Adv. Options
Substitute tab
Add
Input Text = _1 (space 1)
Output Text = Error
--- repeat for 0 to 9 and for -0 to -9
OK

Setup > Control > Word Format
Add
word= Error, type = Macro
OK

Setup > Control > Word/Address
Register
Edit > Add/Modify
word= Error, Range = *
Macro name = ErrorMacro
Override Text = Forgot something?
Add

With this, everytime it will encounter a value with a space before, an error will be output to the logger.

moudy

Member

Registered: 2004-11-11

Posts: 19

Re: Catch a word without an address?

Serge,

Unfortunately all of our programs have spaces in them so this would not be an option.

If I'm interpreting what you have told me correctly (obviously not) then Vericut sees the G word as G-.234. If this is true why do I not get and error of undefined word?

Thanks
Clayton

SergeV

Senior Member

From: Irvine, CA

Registered: 2004-10-08

Posts: 507

Website

Re: Catch a word without an address?

I opened vericut.usr (the default part), Setup > Control > MDI: G1 -1.234 I get the error "G-0.234 is not supported"

With G and M codes you are covered because the last condition G * will call the macro Unsupported.  But if you have X1 -1.234, then you will only get a wrong motion but no errors because X-0.234 is a valid expression.

But in most cases having a wrong value will have a detectable effect in VERICUT like a collision, a gouge or an error message, which can be traced back in the log file.