Warning for RPM

sporter · 2008-08-07 06:36:38

Is there a way of getting a warning in the Vericut log if any tool is programmed above a certain RPM, and to show the actual programmed RPM with the warning?

Cheers.

SergeV · 2008-08-07 16:07:33

Yes, it is possible.

In Tool Manager, it is possible to set cutting limits to each cutter. The parameters available are:

Minimum/Maximum Cut Feedrate
Maximum Cut Depth
Maximum Volume Removal Rate
Maximum Chip thickness
Maximum Surface Speed
Minimum/Maximum RPM

Look in the Help, Help on VERICUT, Training sessions, Session 30 for the step-by-step on how to detect cutting limits

p-cnc · 2008-08-08 13:31:03

SergeV,

Look in the Help, Help on VERICUT, Training sessions, Session 30 for the step-by-step on how to detect cutting limits

Do We need * OptiPath Lisense * for this option ?

I followed the training sessions, But it didn't show any warning.

______

SergeV · 2008-08-08 16:01:22

You do not need an OptiPath license. any user can define the limits and check them during the simulation.

Did you turn on the "Check Cutting Limits" in the Motion window? Pressed Apply before exiting the Motion window?

sporter · 2008-08-09 05:36:51

Thanks for that.

As most of our tools are created using the CatV interface, we would have to go through that every time we create a project. Or can CatV somehow pull that from a Catia tool catalogue?

I was looking for something more general if possible. I would just like a warning in the log every time vericut reads an RPM above 12000 in the NC code, with a message along the lines of -

"18000 RPM programmed for Tool 1 - Balanced holder needed!!"

Cheers.

DaveF · 2008-08-09 16:15:30

Hey Simon, Howzagarn?

I am just looking into this so I don't know all the how to's but,
you can merge Optipath records, from a template, when running CATV

Hopefuly, one of our friends at CGTech will provide a little detail. :twisted:

Otherwise, I will resort to RTFM.

PS ya gonna fly accross the puddle for the SOCAL RUG?

sporter · 2008-08-11 01:15:16

G'day Dave,

RTFM. That's for people with way too much time...

I've ran the trip to your RUG past my financial controller, and she said "No". (or words to that effect)

Cheers.

zac · 2008-08-11 11:28:48

If you are using MachineSim then it would be better and relatively easy to do that check there.

SergeV · 2008-08-11 16:16:07

If you are simulating G-Codes, you can change your controls to check the value passed to S.

Configuration > Word/Address
Expand under Registers
Expand S *

Select the macro ActiveSpindleSpeed, right-click Add/Modify

Under the conditions, select Add (not the bottom Add)

In the Condition column, click to get the pull down, select S
In the Conditional value column, type >12000
Now, press the bottom Add (do not close the window)

Delete the macro name ActiveSpindleSpeed
Type "error" to search for the error macro, in the list, select ErrorMacro

In the Override Text field, type: {$} RPM programmed - Balanced holder needed!!
Press the bottom Add, and then Close

The expression "{$}" will pass the current value of S to the text message

Save your control file.

sporter · 2008-08-12 12:48:45

That's what I've been trying (apart from the {$} bit). But it doesn't seem to be working?

I end up with a new sub heading under the 'S *', after (M 13 14).

(S >12000)
```|__ ErrorMacro
````````|____ Text= {$} RPM programmed - Balanced holder needed

But it doesn't seem to do anything. What could I be doing wrong :?:

Cheers.

SergeV · 2008-08-12 15:36:10

When VERICUT encounters a word/value pair like S15000, it looks in the registers from top to bottom for a matching condition. Once the condition is met, it executes the referenced macro(s)and goes to the next word/value pair on the line.

In your case, VERICUT encounteres the S * (S with anything) first and therefore never gets to S>12000. If you drag-and-drop the S>12000 above the S *, then it will consider it. Don't forget that you still need to activate the spindle with the error.

(S >12000)
```|__ ErrorMacro
```|````|____ Text= {$} RPM programmed - Balanced holder needed
```|__ ActiveSpindleSpeed

(S *)
```|__ ActiveSpindleSpeed

Why the difference?
I think that you added the >12000 to the Range field instead of adding a condition. but both methods will work.

sporter · 2008-08-13 13:16:56

I originally added >12000 as a condition, This created a new subheading of "S >12000" containing the error macro and message within the expanded "S*", but after the sub headings of "G65 66 66.1", "M3 4" and "M13 14", ( which are already within S*).

This didn't seem to work.

I then created a new register S >12000 by using the range field. Then added the condition to that. And placed this new register above the S* register.

This now gives me an error message and everything looks good

But will vericut now ignore the "S *" stuff, as it gets to the "S>12000" first while looking down the register list from top to bottom?

Cheers.

PS. I'm using the fan15m control thats in setup2 of the default project to practice with if, thats any help. The 1st pic below is what I started with and doesn't work. The 2nd one seems to work OK.

SergeV · 2008-08-13 23:36:31

In you NC program, you probably have "M3S12000", so in the first case, it looks for S * (any values) with M3 or M4 on the same line. Once it finds it it doesn't go further.

In your second attemps, Since you have the >12000 in the Range, you do not need the condition. Remove the condition S>12000, it should show "* *"

Then, copy and paste the conditions you see under under S *

sporter · 2008-08-19 13:31:15

After locking myself away in a dark room for a few hours, I came up with this.

It seems to do the trick. But I'm still not sure what all the 4119 and 4319 variables are for?

Thanks for all your help.

Cheers.

SergeV · 2008-08-20 02:31:50

On the Fanuc control, the value of the Spindle speed is stored in the variable #4119 and #4319.

the value could be ten used for calculation in the NC program.

example:

S1000M3
#500= #4119 * 1.1

S#500 (Spindle speed is now 1100 RPM)

VERICUT Users' Forum

#1 2008-08-07 06:36:38

Warning for RPM

#2 2008-08-07 16:07:33

Re: Warning for RPM

#3 2008-08-08 13:31:03

Re: Warning for RPM

#4 2008-08-08 16:01:22

Re: Warning for RPM

#5 2008-08-09 05:36:51

Re: Warning for RPM

#6 2008-08-09 16:15:30

Re: Warning for RPM

#7 2008-08-11 01:15:16

Re: Warning for RPM

#8 2008-08-11 11:28:48

Re: Warning for RPM

#9 2008-08-11 16:16:07

Re: Warning for RPM

#10 2008-08-12 12:48:45

Re: Warning for RPM

#11 2008-08-12 15:36:10

Re: Warning for RPM

#12 2008-08-13 13:16:56

Re: Warning for RPM

#13 2008-08-13 23:36:31

Re: Warning for RPM

#14 2008-08-19 13:31:15

Re: Warning for RPM

#15 2008-08-20 02:31:50

Re: Warning for RPM

Board footer