I didn't understand why I attached the file 3 times, I saw that the file was attached, but a few minutes later it was automatically deleted.
Printable View
I didn't understand why I attached the file 3 times, I saw that the file was attached, but a few minutes later it was automatically deleted.
Your file name should not start with O but your sub program CALL should.
MAIN.MIN
Code
CALL O123
M2
SUBPRGM.SUB
O123
Code
RTS
Hi all,
Does anyone out there have any further input/insight on this programming issue?
I would appreciate any help I can get.
Thanks
The forum is very strange. I cannot attach files and cannot view all posts in the thread so I copy them for you.
To execute a part program in the automatic operation mode, the program to be executed must be
selected.
All programs stored in memory have file names. The required main program is selected from the
stored part programs, then the subprograms called by this main program are selected and the programs are stored in the operation memory of the NC.
To select a part program, follow the procedure below:
(1) Select [F1] (MAIN PRG_OPER) from the function menu.
(2) Select [F1] (PROGRAM SELECT) from the pop-up function menu.
The MAIN PROGRAM SELECT pop-up window is displayed.
Fig.5-
(3) Designate the desired main program file in the main program file list.
The list can be scrolled using the page keys or the up/down cursor keys.
To change the display pattern of the list, select [F2] (FILE NAME) or [F3] (SORT) from the popup
function menu.
The respective changes to the list contents are as follows.
• FILE NAME: The file name pattern for list display is changed.
• SORT: The order of file names is changed on the basis of the file names, size or date.
(4) From the subprogram file list, designate the subprogram file called in the main program. Use
the left/right cursor keys to select the input area.
If not designating a subprogram file, specify “NOT SELECT”.
(5) Input the main program name in the program name input area.
(6) Select the running method, program size, whether subprogram/branch is included, whether
auto scale is used for animation, and whether the material is drawn in animation.
The RUNNING METHOD, PROGRAM SIZE, and SUB PROGRAM/BRANCH selection buttons
allow you to set the required parameters by a method other than the usual parameter setting
method as shown below. For details, refer to the table on the next page.
Running method Program size Sub program/branch
Method A = Normal - (Not selectable)
Method B = Large Included
Method S = Large Not included
(7) With the AUTO SCALE (ANIM) button, select whether the animation drawing range is automatically
adjusted to the material size (EFFECT) or not (INEFFECT) when the NC reads the material
data to be animated.
With the MATERIAL DRAW (ANIM) button, select whether the material is automatically drawn
(EFFECT) or not (INEFFECT) on the animation screen when a program is selected and the animation
material data is read.
The table below shows the relationship between the running method and the program size.
Attachment 434740
Attachment 434742
hy, at 1st i thought that you have a register problem, but, after reading the reply from mr wizard, i believe that there is a syntax error : inside your code replace "CALL 6601" with "CALL O6601"; i believe that this code is inside a *.min file
is not a must to have the soubroutine inside a *.sub file; you may also keep it inside a ssb / min file ... just sayingQuote:
O6601 is the subprogram filename and is registered as such in the library as O6601.SUB
those A & B selection methods are for other things ... kindly :)Quote:
I have tried running this program in "A-Mtd" and "B-Mtd" and get the same problem.
ps : most filenames that i use for ssb files, begin with "o" or "res", depending if the soubroutine is designed for machining, or as a general resource; i don't use e100
Hi all,
Thanks for your help. I have a lot of info to sort now and will try these thing once to machine is back online a it's still down for service.
I hope I have no troubles like the last few days with following this thread. I've filed a ticket with industry forum as I've been not able to view all posts for the last few days.
I'll let you know what happens when the machine is back up and I can try these options
Cheers
Hi all,
Problem solved. We finally got our machine back online last week. Our coolant issue is fixed ( FINALLY! ) and the machine is good to go.
Okuma Wiz...thanks for your help. I put my subprograms in with the main and sent it all together. Presto! Program is good to go.
Almost forgot..I used running method A with this program.
I like this machine already. I've never worked on an Okuma before and this is a pretty good size horizontal mill. I'm starting to get used to the control also. It's very user friendly.
It's built like a tank,fast as a bullet,and quiet as a mouse.
Thanks to all others who guided me in the right direction. I'm looking forward to see what this thing is really capable of.
Cheers
hy, please, what was the issue ?Quote:
Our coolant issue is fixed
i guess you could switch to B and leave it like that for a loooooooooooong time :)Quote:
Almost forgot..I used running method A with this program.
Use caution if it's high pressure coolant through. Some of those machines will get damaged because the HP coolant will act like a hydraulic cylinder and tear up the rear bearings by hydraulic thrust overload. Newer designs remedied this effect, but older ones had the issue. HP meaning 1000 PSI and above...check your spindle design to be sure.