[zooloader]

Hi Guyz,

We have been using Tool Load Monitoring with our Multus without too many problems.

Now that we have repeat work coming in, we don't want to use the Auto Set(?, sorry I can't remember exactly what it's called) to set the load levels, each time a new batch comes in.

It would be preferable to leave the control in Monitoring mode, using the limits that were set from the original run.

Is there a way of setting the limits from within the program, now we know what they are?

Thanks, Dave.

[budgieW]

Dave,

Write the load monitor values into the nc code using the below variables at each tool change. You can always use page 1 with this method

Or write each page\Part

VLMZB[2]=16 ( PART NUMBER 2 ) ( Z BASE LOAD )
VLMZ1[2]=18 ( PART NUMBER 2 ) ( Z FIRST LIMIT )
VLMZ2[2]=20 ( PART NUMBER 2 ) ( Z SECOND LIMIT )


VLMXB[8]=19 ( PART NUMBER 8 ) ( X BASE LOAD )
VLMX1[8]=21 ( PART NUMBER 8 ) ( X FIRST LIMIT )
VLMX2[8]=23 ( PART NUMBER 8 ) ( X SECOND LIMIT )


VLMMB[8]=19 ( PART NUMBER 8 ) ( M BASE LOAD )
VLMM1[8]=21 ( PART NUMBER 8 ) ( M FIRST LIMIT )
VLMM2[8]=23 ( PART NUMBER 8 ) ( M SECOND LIMIT )

And so on

[zooloader]

Thanks budgieW,

that looks just like what I need!

However, I'm curious to know more about this Page 1, you've mentioned. I've not heard of it before (nothing new there).

I imagined just putting a huge lump of that code at the start of each prg, or spread throughout at the start of each tool.

Does the Page 1 offer a more elegant "out of sight" option, or is my imagination running away from me??

Thanks, Dave.

[OkumaWiz]

You can also use the Data PIP function to create a TOP file to "save" your setups which can include Tool info (including Load Monitor info) Parameters, and Offsets (Zero Sets).

Very handy....

Best regards,

[budgieW]

Dave,

I am not sure what you are asking here. Page/Part 1 is the first page in the load monitor screen. There are 64 pages I just keep overwriting page/part 1 as I am too lazy to page through to find the one that has gone off.

[zooloader]

ooohh, I see! Yes it gets tedious searching through the prg to find the # and then go back to find the right page.


Thanx OkumaWiz, that does sound handy! I'll look into that as well.


Hopefully the machine's ready to run tomorrow (after having the turret off and it's seals replaced AGAIN) so I can play with it.

Dave.

[Edster]

Dave,

Write the load monitor values into the nc code using the below variables at each tool change. You can always use page 1 with this method

Or write each page\Part

VLMZB[2]=16 ( PART NUMBER 2 ) ( Z BASE LOAD )
VLMZ1[2]=18 ( PART NUMBER 2 ) ( Z FIRST LIMIT )
VLMZ2[2]=20 ( PART NUMBER 2 ) ( Z SECOND LIMIT )


VLMXB[8]=19 ( PART NUMBER 8 ) ( X BASE LOAD )
VLMX1[8]=21 ( PART NUMBER 8 ) ( X FIRST LIMIT )
VLMX2[8]=23 ( PART NUMBER 8 ) ( X SECOND LIMIT )


VLMMB[8]=19 ( PART NUMBER 8 ) ( M BASE LOAD )
VLMM1[8]=21 ( PART NUMBER 8 ) ( M FIRST LIMIT )
VLMM2[8]=23 ( PART NUMBER 8 ) ( M SECOND LIMIT )

And so on

Will this work on an okuma captain with the p200 control? I looked through the manuals and couldn't find anything about setting the load monitors in the program. The special functions manual has a bunch of info about the load monitors but nothing about setting the levels in the program.

[Algirdas]

must work, sure
nothing about setting the levels in the program
o yes, these Jinglish manuals.
There are relevant variables described and somewhere else there is description how to set them in the part program text.

[Edster]

The programming manual had info about setting variables from the program, I just didn't see anything for vlmon listed. I also looked at the list of variables in the manual near the g and m code lists, and I only found vlmon. I didn't find a list of the variables to set the loads from the program for different axes.

I'm going to try the ones budgieW listed monday and see if they work. I'm also curious as to what the variables for the spindle load, subspindle load, and the subspindle W axis would be.

[budgieW]

VLMZB[2]=16 ( PART NUMBER 2 ) ( Z BASE LOAD )
VLMZ1[2]=18 ( PART NUMBER 2 ) ( Z FIRST LIMIT )
VLMZ2[2]=20 ( PART NUMBER 2 ) ( Z SECOND LIMIT )

The second last letter is the axis so above we are looking at Z

[Edster]

Makes sense. Spindle would probably be an S. The w axis for the subspindle would probably be W. But what would the sub spindle be called?

[budgieW]

VLMB2 is the sub spindle

[Edster]

Works perfect! This will save a lot of entering and re-entering limits. Thanks everyone! :cheers:

[OkumaWiz]

Try this for fun:

DATA PIP

Output
TYPE "MD1:LOAD.TOP" > WRITE (or any other name)

OUTOUT DATA IS?

TYPE "T12,T13,T14" > WRITE

You now have an editable load monitor text file in your MD1: directory.

This can be saved with every job and "input" before you run the job.

Dirt simple and much easier than all the typing. Even if you do want to enter them in your program, this file can be printed out to keep you from having to go back and forth with the editor so much.

Best regards,

[zooloader]

Thats cool OkumaWiz,
I tried using that earlier when you suggested, but I couldn't figure out what or where was getting input or output.
You've cleared that up for me now.
I added all my loads budgieW style yesterday and it took me friggin ages, even with copy and paste!

[D.WAL]

Hi

I find data pip the best way to save & reload zero offsets,load monitor settings & parameters for every programmed job I run repeatedly.
Does anyone know if these top files can be loaded automaticlly like a sub. program call ?

Thanks

[Algirdas]

I include zerro offsets in part program at very start of text.
VZOFZ is z axis zero offset
VZOFX is x axis zero offset
VZSHZ is z axis zero shift
VCHKZ is chuck barrier "CZ"
The same could be done with load monitor variables

[budgieW]

You can also check that the load monitor is actually on from the program. Add the below code to check the status of the button

(LOAD MONITOR ON)
(IF[VORD[001C] EQ 0]NALM8)

NALM8
VUACM[1]='LOAD MONITOR OFF'
VDOUT[992]=2