Reply with QuoteProblem solved =o)
OKUMA MA40 HA variables
Hello, all =o)
I'm new to this forum and this is my first posting.
We've reicently bought an OKUMA MA40 HA horisontal with 2 pallets and are shooting in the dark on this one.
It seems that there should be a main program in the machine with variables that connects "palett 1" to "program 1.min" & "palett 2" to "program 2.min".
There is no such program in the machine, does anyone here know what it should look like?
Thanks
Magnus
Similar Threads:
Problem solved =o)
Could you post the core of the problem, and the solution?Originally Posted by Magnus Sweden
It would help me.
Robert
littlerob
these programs are not really necessary if you utilise a library file and register a user M-code to shuttle in or check if a certain pallet in in the machining area
These pallet1.min and pallet2.min would best be used when scheduling programs
reply if you want more info
we have MX40-HA with 2 pallets and use M201 for palete #1 and M202 for #2
M code subs.
Ahhh, nice idea.
I use an IF/GOTO type statement for a pallet check/change at the start of my programs which requires a few edits if it's the opposite pallet needed.
I'll be using M201/M202 as from Monday. Thanks Superman.
ChattaMan.
pallet machines-Library file
Merry Xmas for all
attachment for all OKUMA's with pallets
G-codes and M-codes extras for many OKUMA machines
G111= tool measure
G112= tool re-measure
G113= tool breakage detection
G114= tool measure
M201= call in pallet#1,continue if pallet#1 is current
M202= call in pallet#2,continue if pallet#2 is current
M203= empty tool from spindle
M204= call WARMUP cycle for machine
M205= empty thru tool coolant line with air blow
all these codes should be set in "parameter set" page of control
G111 = OTOOL
G112 = OTOL1
G113 = OBREK
G114 = OTOL2
M201 = OPAL1
M202 = OPAL2
M203 = ONOT
M204 = OWARM
M205 = OM50O
they then operate like a "CALL" statement
ie M205 = CALL O5o0 ( air blow )
or M204 = same as loading the WARM.MIN file ( turn on m/c - MDI 'M204' will warm-up the spindle )
M201 = is PALLET1 in machine? NO. well bring it in, only if "W.LOAD FINISHED" button is pressed
To all the very best of this festive season
Hello, again!
This is how we did:
We made a .SDF program called AUTO.SDF and typed the following into it:
( ** schemaprogram ** )
NA10 PSELECT PM60.MIN ( ** PALLETCHANGE)
NA20 IF[VPLTK NE 1]NCK ( ** IF NOT PALETT 1 GO TO NCK)
NA30 PSELECT PROGRAM1.MIN ( ** PROGRAM 1)
NA40 PSELECT PM60.MIN ( ** PALLETCHANGE)
NCK IF[VPLTK NE 2]NEND ( ** IF NOT PALETT 2 GO TO NEND)
NA50 PSELECT PROGRAM2.MIN ( ** PROGRAM 2)
GOTO NA10 ( ** LOOP)
NEND END ( ** END)
There must be a palletchanging program.
Make a file called PM60.MIN and write the following:
%
( ** PALLETCHANGE ** )
M60
M2
%
Transfer these programs to the machine:
AUTO.SDF
PROGRAM1.MIN
PROGRAM2.MIN
PM60.MIN
The main program to run in the machine is now AUTO.SDF. One can change programs for the pallets in this program. It solved our problem for now, time will tell if we need any changing ;-)
Merry X-mas all!
Superman Hero
Superman..you are a Superman.
Sorry Magnus for hijacking your thread but I need to hang on to Supermans attention!!
Tried the M201/M202. Worked a treat
This is our first HMC and our first Okuma. This was the first library file I have registered on the control. I needed to enter a "buffer size" to be able to store the .LIB file. I understood from the manual it had to be sufficient for the number of Bytes the programs used. I found the manual to be rather like the Fanuc manuals....they tell you how to do it but not why you need to do it. I don't like doing something without really knowing why.
So...what is the purpose of the "buffer size"?
ChattaMan
Hi Magnus,
The file "MX40HA.LIB" is registered, and resides permanently in the control with all these codes registered in "parameter set" page of control
( check your manuals "OSP7000M operation manual, pub#3754-E, section 12-23 Library Program Registration, page 347)
G111 = OTOOL
G112 = OTOL1
G113 = OBREK
G114 = OTOL2
M201 = OPAL1
M202 = OPAL2
M203 = ONOT
M204 = OWARM
M205 = OM50O
In your running program, "M201" will check if pallet#1 is in m/cing area and will only continue when it is
When finished m/cing then "M202" to call in the other pallet
an example with a few other macros included
$TEST.MIN%
(...)
(...)
()
N1 G21
N2 G0 G17 G40 G90
N3 G15 H0
N4 G30 P1
()
N5 T3
N6 M201 ( pallet #1 )
( 3.0BALL CBD 2FLUTE 4FLUTELENGTH 6SHANK 18OUT )
( TOOL - 3 ; D3 ; H3 ; TOOL DIA. - 3. )
N7 T3 M6
N8 G15 H1
N9 B0. M15
N10 G0 X366.4 Y22.775
N11 S8500 M3
N12 M50 ( thru tool coolant )
N13 G56 H3 Z80.
...
...
...
N107 G0 Z80.
N108 M9
N109 M5
N109 M205 (clear coolant lines )
N110 G17
N111 G15 H0
N112 G30 P1
N113 M202 ( pallet #2 )
N114 M203 ( empty spindle )
N115 / GOTO N1 ( continuous cycle )
N116 M30
%
Note!!
SDF schedule files not required for day to day work,
but are useful when laying out jobs on different pallets
( SCHEDULE.SDF )
N1 PSELECT PROGRAM1.MIN
N2 PSELECT PROGRAM2.MIN
N3 PSELECT PROGRAM3.MIN
( PROGRAM1.MIN = OP.1 = PALLET 1)
( PROGRAM2.MIN = OP.2 = PALLET 1)
( PROGRAM3.MIN = OP.3 = PALLET 2)
GOTO N1
END
ChattaMan, g'day
got 1/2 way through writing this post when yours popped up,
figured that this post was very interesting to you
so I put it up for all to see
This would be of interest to all OKUMA pallet machines
"buffer size" refers to a small section of control memory reserved for your .lib files, sub-routines, macros and the like.
I am not sure what value to input, but a starting point would be the size in bytes plus a bit of the .lib file ( say 5000 bytes or a bit more )
We got our m/c with some of this in place and now full on programming, some things are better forgotten
Buffer size
Superman, ayup.
Ok I'll just except it, that...it just, is!
Looked at schedule files but left it alone. We have all the gubbins for an FMS but it's not set up yet, so are just running two pallets. Got full simultanious B axis and Turncut function. Didn't realise how useful turncut would be but seem to use it on every new job!
This is the first job I used it on......
"http://video.google.co.uk/videoplay?docid=5641232019650543372&ei=vxVQSaHqOIv KiQL7is3KCw&q=turncut&hl=en-GB"]Turncut
Turn bore with tapers and rads, scroll face, turn O/D with corner rad.
ChattaMan, neato
swap? your code ( a look see ) for mine, you've already got mine
always wanted to know how to sync the spindle to XYZ
also have a good look at my .lib file
M205 , thru coolant line air blowout
M204 , spindle warm-up cycle ( no need to select WARM.MIN just <MDI> M204 )
G113 = tool breakage detection, if tool length alters by "PLE1=value" it alarms
good for production if ckecking a drill before tapping, also after tapping
Swapsies
Yeah no problem sharing code. Don't know if you can sync the spindle without turncut function! Once you've initialised the turncut you just program as on a lathe, with X & Z. Have a look at the attached prog. I used turncut for the flanges, as on the vid, also a 4.7mm face groove with 0.2mm and 0.5mm corner rads and a back bore.
Also attached are(normally .SSB files but changed to .TXT to upload on here)......
...macro for helixing holes/counterbores with a flat bottom (also useful for chamfer/deburr)
...macro for parallel internal threadmill
...macro for NPT/BSPT internal threadmill
There's lots more to learn with this control. There's just not enough hours in a day!
Oooops
Forgot to attach prog for above post. Doh!
Re: OKUMA MA40 HA variables
Is there any chance you could help me with the syntax for registering the lib files? I'm not sure exactly what I'm doing wrong, but we just got a new (used) MX40-HA and I downloaded your .lib file and copied it to MD1: but I keep getting syntax errors when trying to register the library. The machine didn't come with a manual and all of our other machines have different controls, so I'm not really sure how much help those manuals would be. To be honest, I'm not positive which control this machine actually has, as it is labeled OSP700L, which I'm fairly certain is a lathe control, but it could just be a screen swapped in to the machine.
The trouble we're having is that we have different setups on each pallet, and using an M60 with less experienced operators is begging for a bad crash. Any help you guys could offer would be very much appreciated.
Re: OKUMA MA40 HA variables
I agree that using M60 (on it's own) is an accident waiting
- haven't got access to anything Okuma now,,,,, but memories
I seem to remember that you have to assign the sub-routine name to a user M & G codes ....as well as registering the .lib file
ie go to the user G code for G111 to G119 and have each equal a sub-routine that is in a registered .lib file that is in bubble memory
& also do the same for the M codes
when registering the .lib file ,,,you will be asked haw much space is to be reserved for this file, ----needs to be a little larger than the .lib file ( number of characters + number of lines)
Here is a link to PDF of the "OSP7000M operation manual, pub#3754-E,
see --- section 12-23 Library Program Registration, page 347
-after it loads onto your PC, do a Save AS, to put it on your computer
Re: OKUMA MA40 HA variables
It was right at the end of my shift, but that got me over the hump. The library directory hadn't been initialized, so as soon as I did that everything else worked great. The macros are all registered, but I had to leave a note for the day shift guy to change the programs accordingly.
Now that I have the macros registered, do you happen to know if we can delete the .lib files from MD1:? None of our other machines still have the .lib files, so I assume that safe to do.
Re: OKUMA MA40 HA variables
I believe that the registered .lib file must remain in bubble memory....so I would protect them, so they cannot be deleted or modified by sticky fingers
- check each sub fully, they also utilise G30P(numbers) for retracts
- I also think the M201 / M202 pallet-change uses other G30 positions, including the B rotate to ZERO before indexing
make sure they are set to the correct P numbers, it also depends on the company that commissioned the machines to use the same G30s, same order of axis execution ( ie Z, then XYB ( or even just B )
you may have programs like PALLET1.MIN or PALLET2.MIN , they may have the numbers you need to compare.
Once you get the .lib working, those then do not need to be kept in the control
Re: OKUMA MA40 HA variables
Sorry for interruption. Maybe somenoe have Programming Manual for this machine with OSP-U100M? scans, photos, pdf, jpg whatever in english would be great
Re: OKUMA MA40 HA variables
Any OSP programming manual for 7000M, U100, P100, P200 would be of use...as programming code would be nearly identical, links are with the control names ( they open to a PDF of the manual )Sorry for interruption. Maybe somenoe have Programming Manual for this machine with OSP-U100M? scans, photos, pdf, jpg whatever in english would be great
- for correct operation of your machine, you would need the machine specific Operation Manual
Last edited by Superman; 09-11-2014 at 05:27 AM.
Re: OKUMA MA40 HA variables
Thanks!
