For FANUC Series 30*-MODEL AFor FANUC Series 30*-MODEL A
OPERATOR’S MANUAL
B-66264EN/01
Page 2
• No part of this manual may be reproduced in any form.
• All specifications and designs are subject to change without notice.
The export of this product is subject to the authorization of the government of the country
from where the product is exported.
In this manual we have tried as much as possible to describe all the various matters.
However, we cannot describe all the matters which must not be done, or which cannot be
done, because there are so many possibilities.
Therefore, matters which are not especially described as possible in this manual should be
regarded as ”impossible”.
This manual contains the program names or device names of other companies, some of
which are registered trademarks of respective owners. However, these names are not
followed by or in the main body.
Page 3
B-66264EN/01DEFINITION OF WARNING, CAUTION, AND NOTE
DEFINITION OF WARNING, CAUTION, AND NOTE
This manual includes safety precautions for protecting the user and
preventing damage to the machine. Precautions are classified into
Warning and Caution according to their bearing on safety. Also,
supplementary information is described as a Note. Read the Warning,
Caution, and Note thoroughly before attempting to use the machine.
WARNING
Applied when there is a danger of the user being
injured or when there is a danger of both the user
being injured and the equipment being damaged if
the approved procedure is not observed.
CAUTION
Applied when there is a danger of the equipment
being damaged, if the approved procedure is not
observed.
NOTE
The Note is used to indicate supplementary
information other than Warning and Caution.
•Read this manual carefully, and store it in a safe place.
s-1
Page 4
Page 5
B-66264EN/01PREFACE
PREFACE
This manual describes the models indicated in the table below.
For descriptions about the FANUC Series 0, 15, 16, 18, 20, and 21,
refer to "FANUC MACRO COMPILER Programming Manual" (B66102E).
In the text, the abbreviations indicated below may be used.
Model nameAbbreviation
FANUC Series 30i-MODEL A30i -ASeries 30i
FANUC Series 300i-MODEL A300i-ASeries 300i
FANUC Series 300is-MODEL A300is-ASeries 300is
This software can run on Microsoft Windows. This manual does
not describe the basic operation procedures for Windows. It does not
explain editors either.
Other companies' products mentioned in the manual
*Microsoft, Windows, and MS-DOS are the registered trademarks
of Microsoft Corp.
The other product names mentioned in the manual are the trademarks
or registered trademarks of the respective owners.
p-1
Page 6
Page 7
B-66264EN/01TABLE OF CONTENTS
TABLE OF CONTENTS
DEFINITION OF WARNING, CAUTION, AND NOTE................................ s-1
The FANUC Macro Compiler/Executor function stores programs
created using custom macros (macro programs) in FLASH ROM
(called F-ROM in the following) so that machine tool builders can
implement their own conversational screens.
The FANUC Macro Compiler for
compiler utility to implement the Macro Compiler/Executor function
for Series
market.
This manual describes the procedures ranging to transferring macro
programs to Series
macro compiler utility.
For the syntax rule for creating macro programs, refer to the “FANUC
Series
PROGRAMMING MANUAL (B-63943EN-2).”
30i/300i/300is-A on personal computers available on the
30i/300i/300is-A via the memory card by using the
30i/300i/300is-AMacro Compiler / Macro Executor
FANUC Series 30i-A is a macro
- 1 -
Page 10
1.GENERALB-66264EN/01
1.1 FEATURES
(1) The symbolic macro compiler function allows macro programs
to be coded in symbolic format, and also allows comments to be
coded.
(2) A program that references macro variables in array format can be
created.
(3) Compile list output makes macro program development,
debugging, and maintenance much easier.
(4) A linker (linkage editing) function is employed which allows
partial compilation and also facilitates the development and
maintenance of macro programs common to several models.
- 2 -
Page 11
B-66264EN/011.GENERAL
1.2 Overview
The Macro Compiler/Executor function of FANUC Series
3
30i/300i/300is-A allows Series 30i/300i/300is-A users to develop
their own macro program in a macro language, convert it into the
macro MEM file format with the macro compiler, and execute a
macro program developed by the macro executor function of Series
30i/300i/300is-A. (See the conceptual diagram on the next page.)
The Macro Compiler utility allows the users to develop and compile a
macro program and write it to the macro MEM file by using a
personal computer.
The macro compiler utility enables macro program development,
compilation, and writing to a macro MEM file on a personal
computer.
The macro compiler utility functions are listed below.
(1) Macro compiler
•Symbolic macro program analysis
•Macro program compilation
•Object program output
•Reference list/compile list output
(2) Macro linker
• Linkage editing of specified object programs and macro
executor/compile parameters
•ROM-format file output
•Link list output
(3) Memory card format conversion
• Converting macro programs to a format capable of
accepting write from a memory card
The macro compiler utility is distributed with a 3.5-inch (2HD) floppy
disk.
The utility does not provide functions such as those for editing macro
programs, and saving and restoring programs to and from floppy
disks.
- 3 -
Page 12
1.GENERALB-66264EN/01
(Obj
)
LINK
Control
file
(xx.LNK)
MLINK30I
Text E d i t or
MACRO
Linker
Program
(Sourcefile)
MCOMP30I
MACRO
Compiler
Program
Macro
(xx.REL)
Macro
file
(F30ia_xx.MEX)
* Create a macro program using an editor. (An editor is
not supplied.)
* The macro program (source file) must be in text format.
* The macro compiler generates an object file. It also
creates reference and compile lists at the same time as
the object file.
* The object file is linked based on a link control file to
generate a ROM-format file. The editor creates the link
control file.
* FANUC supplies a macro library.
Macro
Library
file
(xx.ROM)
ROM
format file
MCARD30I
Memory Card
(xx.MEM)
Memory Card
Reader
/Writer
Memory
Card
* The ROM-format file contains macros in binary form
output by the linker.
* The ROM-format file is converted into the memory card
format, sent to the CNC via the memory card, and
executed on the CNC.
Fig. 1.2 MACRO compiler utility function conceptual diagram
- 4 -
Page 13
B-66264EN/012.EQUIPMENT CONFIGURATION
2 EQUIPMENT CONFIGURATION
(1) Personal computer (IBM PC/AT series)
Main memory640K bytes or more
OSMicrosoft Windows95/98/NT/Me/2000/XP
Hard disk
Floppy disk drive3.5"Floppy Drive. (2HD)
CAUTION
1 The macro compiler utility software is installed on
hard disk. This software occupies a hard disk space
of about 1M bytes. In addition, developed macro
programs and list files/object files generated at
compile time are output as files on hard disk. So the
size of hard disk depends on the macro programs
developed.
2 The macro compiler utility software and macro
executor are distributed with a 3.5-inch (2HD)
floppy disk. A 3.5-inch floppy disk drive is needed to
install the system and executor files.
3 Only IBM PC/AT compatible machines are
supported. NEC PC98 Series are not supported.
About 1M bytes is required for install the system
(Caution 1)
- 5 -
Page 14
3.SYSTEM INSTALLATION (SETUP)B-66264EN/01
3 SYSTEM INSTALLATION (SETUP)
The FANUC Macro Compiler software is distributed with the two
3.5-inch (2HD) floppy disks titled "FANUC Series 30i Macro
Compiler system floppy disk" and "FANUC Series 30i Macro Library
system floppy disk".
To use the software, load the software to the hard disk from the
system floppy disks.
- 6 -
Page 15
B-66264EN/013.SYSTEM INSTALLATION (SETUP)
3.1 INSTALLING THE FANUC MACRO COMPILER (FOR Series
30i) SYSTEM
This section describes how to install the FANUC Macro Compiler
(for
Series 30i) software on the hard disk.
Procedure
Insert the FANUC Series 30i Macro Compiler system floppy disk into
the floppy disk drive, click [Start], and then click [Run].
Enter the following command line in [Open] and then click <OK>.
?:\MCOMP\MSETUP <in> <out>
? :: Name of the drive containing the Macro Compiler system
floppy disk
("MSETUP.BAT" is in the "MCOMP" directory on the
system floppy disk.")
<in> : Specify the name of the drive containing the Macro Compiler
system floppy disk.
<out> : Specify the drive name of the hard disk to hold the system.
Example of installing the Macro Compiler
This example assumes that the system floppy disk is inserted into
drive A: and the system is to be installed on hard disk drive C:.
When the command line above is entered and then executed, the
following directories are created on drive C: and the system software
and sample programs are copied to them.
C:\MCOMP30I
\TOOL
\MEX
\USR
\SAMPL
- 7 -
Page 16
3.SYSTEM INSTALLATION (SETUP)B-66264EN/01
Explanation of the directories
(a)\MCOMP30I\TOOL
FANUC Macro Compiler system software, batch files, document
files, and so forth are stored under this directory.
MCOMP30I.EXE, MLINK30I.EXE, MCARD30I.EXE :
System software
ERROR.DOC : Compilation error code table
SYSTEM.DEF : Symbol definition file in English (for
$INCLUDE)
(b) \MCOMP30I\MEX
Library file is stored under this directory.
This is performed as described in Section 3.2, "INSTALLING
THE FANUC MACRO LIBRARY".
(c) \MCOMP30I\USR
Under this directory, create directories used to develop macro
programs.
C:\MCOMP30I
\ TOOL
\ MEX
\ USR
\ SAMPL
(d) \MCOMP30I\USR\SAMPL
Under this directory, the files including such a link control file,
compiler/link result files, and program files as described in
Appendix C are stored. Use these files as reference information
for development.
- 8 -
Page 17
B-66264EN/013.SYSTEM INSTALLATION (SETUP)
3.2 INSTALLING THE FANUC MACRO LIBRARY (FOR Series
30i)
This operation loads the executor file under the library directory of
the FANUC Macro Compiler installed by the operation of Section
3.1.
Insert FANUC Macro Library system floppy disk for Series 30i into
the floppy disk drive, click [Start], and then click [Run].
Enter the following command line in [Open] and then click <OK>.
?:\MCR_LIB\ESETUP <in> <out>
? :: Name of the drive containing the Macro Library system
floppy disk.
("ESETUP.BAT" is in the "MCR_LIB" directory on the
system floppy disk.")
<in> : Specify the name of the drive containing the Macro Library
system floppy disk.
<out> : Specify the drive name of the hard disk holding the system.
Example of installing the Macro Library
Enter the command line above and then click <OK> to store the
library files in C:\Mcomp30I\Mex.
3.3 PATH SETTING
All system software is stored in the \MCOMP30I\TOOL directory.
So the PATH setting must be made from System in Control Panel.
- 9 -
Page 18
3.SYSTEM INSTALLATION (SETUP)B-66264EN/01
3.4 COMPILER SERIES
There are four types of FANUC Macro Compiler systems. One type is
for
FANUC Series 30i. The other three types are provided for the
systems shown below.
<1> For FANUC Series 0/Series 16/Series 18/Series 20/Series 21
<2> FANUC Series 15-A/15-B
<3> FANUC Series 15i-A
These Compiler systems are for the respective series only. Compiling
the same macro program using these compiler systems generates
different object codes. For this reason, be sure to use the execution
files (macro compiler/linker/memory card converter) and library files
suitable to the development model.
If multiple systems are to be installed on the same personal computer,
it is recommended that a separate directory be used for each CNC
series.
For the FANUC Macro Compiler system for FANUC Series
0/15/16/18/20/21, see the FANUC MACRO COMPILER
PROGRAMMING MANUAL (B-66102E).
CNC seriesMacro compilerMacro linker
30i
0/16/18/20/21
15-A/15-B
15i-A
MCOMP30IMLINK30IMCARD30I
MCOMP0MMCARD
MCOMP15
MCOMP15IMLINK15IMCARD15I
*This manual provides information only on Series 30i.
MLINK
Memory card
format converter
MMCARD15
- 10 -
Page 19
B-66264EN/014.FUNCTIONS
4 FUNCTIONS
- 11 -
Page 20
4.FUNCTIONS B-66264EN/01
4.1 MACRO COMPILER (MCOMP30I)
The Macro Compiler can compile macro programs created in the text
file format. The Macro Compiler outputs an object file for the macro
linker, reference list file, and compile list file.
Source Fi le
Macro
(xx.SRC)
Procedure
Program
Ob ject Fi le
Object
MCOMP30I
Program
(xx.REL)
Reference List File(xx.REF)
Compile List File (xx.LST)
MACRO COMPILER
1 O0001;
2 #100=#101+10;
Any of the following methods can be selected, but this manual uses
method (2) for description.
(1) Click [Start] and then click [Run].
Enter the following command line in [Open] and then click
<OK>.
MCOMP30I file-spec [parameters]
(2) Click [Start], click [Programs], and then click [Command
Prompt]. Execute the command by entering it at the DOS
prompt.
Change the current directory to the folder in which the source
program is stored by using the CD command, and then execute
the following command line.
C:\xxxxx\xxxxx> MCOMP30I file-spec [parameters]
(xxxxx\xxxxx: Current directory)
*The following descriptions assume the source program to be
compiled is stored in C:\.
*1file-spec
This specifies a macro program source file. The extension of a
source file name must be .SRC. Source files to be compiled can
be specified in three ways:
(1) Compilation of a single file
C:\> MCOMP30I ABC Þ Compiles ABC.SRC.
(2) Compilation of multiple cards by using a wild card
C:\> MCOMP30I ABC*
Þ Compiles all files whose names start
with ABC and have the
extension .SRC.
- 12 -
Page 21
B-66264EN/014.FUNCTIONS
r
(3) Selective compilation according to link control file
specification
C:\> MCOMP30I @ABC
Þ Compiles all files specified in the
link control file (file name:
ABC.LNK). (For details on the link
control file, see Section 4.2,
"MACRO LINKER".)
CAUTION
As described in Section 3.4, even if the same macro
program is compiled, the Macro Compiler for Series
30i creates an object file different from an object file
created by the Macro Compiler for Series
0/15/16/18/20/21. Select the compiler that matches a
development model.
*2[parameters]
This specifies compile conditions.
-NR : Outputs no object file. If this parameter is omitted, an
object file with the extension .REL is output.
-L2 : Outputs no reference list file. If this parameter is omitted,
a reference list file with the extension .REF is output.
-L3 : Outputs a macro program file. If this parameter is omitted,
no macro program file is output. A macro program file is
output with the extension .PRG.
-PR : Makes no symbolic macro program analysis. Specify this
parameter when a program coded in standard macro
program format is to be compiled. No reference list file is
output. Even if this parameter is not specified, a macro
program can be compiled without trouble. However, this
parameter can save time required to make a symbolic
macro program analysis and can also save space for
reference list file output.
-Fo : Specifies a destination to which an
object file is output.
-Fr : Specifies a destination to which a
reference list file is output.
-Fl : Specifies a destination to which a
compile list file is output.
-Fp : Specifies a destination to which a
macro program file is output.
See "Specifying
the destinations to
which the compile
outputs files"
given later.
- 13 -
Page 22
4.FUNCTIONS B-66264EN/01
Macro program source file
A macro program source file must be created in text file.
The Macro Compiler can compile a macro program coded in symbolic
format.
For detailed information, see Chapter 5.
The Macro Compiler can also compile a program coded in standard
macro program format. In this case, specify the command parameter PR. This parameter can save time required to make a symbolic macro
program analysis and can also save space for reference list file output.
NOTE
Be sure to use .SRC as the extension of a file name.
Object file
An object file output by the compiler is subject to processing by the
macro linker. The name of an object file is the same as the source file
name, except that the extension .REL is assigned to the object file.
Reference list file
The reference list file is a list file output from macro program analysis
processing. A source program, errors, error codes, symbol name cross
reference information are listed. The name of a reference list file is
the same as the source file name, except that the extension .REF is
assigned to the reference list file.
Compile list file
A compile list file is output as a result of macro program compilation
after symbolic macro program analysis. A source program, errors,
error codes, variable cross reference information, object file size
information, and so forth are listed. The name of a compile list file is
the same as the source file name, except that the extension .LST is
assigned to the compile list file.
Macro program file
By specifying the command parameter -L3, a macro program after
symbolic macro program analysis processing can be preserved as a
file. The name of a macro program file is the same as the source file
name, except that the extension .PRG is assigned to the macro
program file.
Specifying the destinations to which the compiler outputs files
The directory of the destinations to which the compiler outputs files
can be specified as desired according to compiling conditions.
-Fo : Specifies a destination to which an object file is output.
-Fr : Specifies a destination to which a reference list file is
output.
-Fl : Specifies a destination to which a compile list file is
output.
-Fp : Specifies a destination to which a macro program file is
output.
- 14 -
Page 23
B-66264EN/014.FUNCTIONS
Execution example
C:\> CD MCOMP30I\USR\SAMPL
→Change the current directory to the folder in which the source
program is stored.
C:\MCOMP30I\USR\SAMPL>MCOMP30I *.SRC
→Compile all .SRC files.
Execution result
(The result is output to the current directory because no destination is
specified.)
When the following command line is executed, the object file is
output to C:\MCOMP30I\USR\OBJ and the compile list file to
C:\MCOMP30I\USR\LST.
According to the specification in the link control file created
beforehand, the macro linker links the object file and library file
compiled by the Macro Compiler and creates a ROM-format file and
link list file.
Link control FileROM Format File
Procedure
Link
Control
(xx.LNK)
Objec t File
Object
Program
(xx.REL)
ROM
MLINK30I
Macro
Library
file
(F30IA_XX.MEX)
File
(xx.ROM)
Link List File(xx.MAP)
MACRO LINKER
prog. Size.
1 O0001 00100H
2 O0002 00200H
Any of the following methods can be selected, but this manual uses
method (2) for description.
(1) Click [Start] and then click [Run].
Enter the following command line in [Open] and then click
<OK>.
MLINK30I file-spec [parameters]
(2) Click [Start], click [Programs], and then click [Command
Prompt]. Execute the command by entering it at the DOS
prompt.
Change the current directory to the folder in which the object file
is stored by using the CD command, and then execute the
following command line.
C:\xxxxx\xxxxx> MLINK30I file-spec [parameters]
(xxxxx\xxxxx: Current directory)
*The following descriptions assume the object file is stored in C:\.
*1file-spec
This specifies a link control file created in a specified format
beforehand.
- 16 -
Page 25
B-66264EN/014.FUNCTIONS
*2[parameters]
This specifies link conditions.
-NR : Outputs no ROM-format file. If this parameter is omitted,
a ROM-format file with the extension .ROM is output.
-NL : Outputs no link list file. If this parameter is omitted, a
link list file with the extension .MAP is output.
-Fm : Specifies the destination to which a link list file is output.
See the subsection describing specification of the
destination.
-Fr : Specifies the destination to which a ROM-format file is
output
Link control file
The link control file specifies a library file name, compile
parameters, and object file names subject to linkage. As with a source
file, a link control file must be created in text file.
In a link control file, a library file name, compile parameters, and
object file names subject to linkage are defined using keywords. A
comment line can be provided by using /*.
The link control file is also used as the control file for selective
compilation of the Macro Compiler. (See (3) "Selective compilation
according to link control file specification" in "Procedure" in Section
4.1, "Macro Compiler".) This function is useful when all programs to
be linked are compiled.
CNC= : CNC library file name. F30iA_??.MEX for Series
30i (??: version number)
P9999= : Compile parameters (No.9000 to 9199)
FILE= : Object file name
(Multiple object files can be specified with each
name delimited by a comma.)
P-CODE_NUMBER=: P-CODE number (01 to system
maximum path number)
A P-CODE numbers is specified when
multiple P-CODEs are loaded.
NOTE
1 Be sure to use .LNK as the extension of the link
control file.
2 The number of P-CODEs that can be loaded in the
CNC must be equal to or less than the maximum
path number. A P-CODE number must be equal to or
less than the maximum path number.
3 When P-CODE_NUMBER is not specified, the
following error occurs.
“ERROR : Can not find SYSTEM define “
- 17 -
Page 26
4.FUNCTIONS B-66264EN/01
Sample link control file
/*
/*MACRO COMPILER UTILITY LINK FILE (SAMPLE)
/*
/*FOR F30I-A
CNC=\MCOMP30I\MEX\F30iA_01.MEX
P-CODE_NUMBER=01
/* Compile Parameter
P9000=00010000/* P-CODE Size 1MB
P9010=100/* M-Code Sub call O9001
P9038=8000/* Conversational Macro program
/*Execution-Macro program
FILE=FRANGE_MAIN,FRANGE_SUB1,FRANGE_SUB2,FRANGE_SUB3
FILE=SHAFT1,SHAFT2
/*Conversational- Macro program
FILE=SCREEN
The example above is for P-CODE file 1. The compile parameters
(Nos. 9000, 9010, and 9038) are set and the object files
(FRANGE_MAIN.REL, FRANGE_SUB1.REL,
FRANGE_SUB2.REL, FRANGE_SUB3.REL, SHAFT1.REL,
SHAFT2.REL, and SCREEN.REL) are linked.
The specification of 0 is assumed for those compile parameters that
are not specified in the link control file.
Link list file
The link list file is output by the linker, and a library name, compile
parameters, compile program list and size information, erroneous
program numbers, error codes, ROM-format file size information and
so forth are listed.
The name of a link list file is the same as the link control file name,
except that the extension .MAP is assigned to the link list file name.
Specifying the destinations to which the macro linker outputs files
The directory of the destinations to which the macro linker outputs
files can be specified as desired according to linking conditions.
-Fm : Specifies a destination to which a link list file is output.
-Fr : Specifies a destination to which a ROM-format file is output.
Example
Assume that the object file is stored in C:\MCOMP30I\TEST.
Executing
C:\MCOMP30I\TEST >MLINK30I SAMPL –FmMAP –FrD:\MCOMP\LNK
generates SAMPL.MAP in C:\MCOMP30I\TEST \MAP and
SAMPL.ROM in D:\MCOMP\LNK.
- 18 -
Page 27
B-66264EN/014.FUNCTIONS
Checking the size of ROM format file at linking macro
A ROM format file that is created by linking is checked for its size
whether it is overflown or not. The size of ROM format file is set by
compile parameter Nos. 9000 and 9001.
If a prepared ROM format file may exceed the size that was set by
compile parameter Nos. 9000 and 9001 as a result of linking, an
following error is produced when the macro linker is executed.
ERROR : ROM size over
Bit No.
No.#7#6#5#4#3#2#1#0
Compile parameter
9000M3MBM2MBM1MBM512M256
Compile parameter
Execution example
9001M4MB
M4MBM3MBM2MBM1MBM512M256
4.0MB100000
3.0MB010000
2.0MB001000
1.0MB000100
512KB000010
256KB000001
C:\> CD MCOMP30I\USR\SAMPL
→Change the current directory to the folder in which the object file
is stored.
C:\MCOMP30I\USR\SAMPL>MLINK30I SAMPL
Execution result
(The output file is output to the current directory because no
destination is specified.)
- 19 -
Page 28
4.FUNCTIONS B-66264EN/01
4.3 CONVERSION TO A MEMORY CARD FORMAT
(MCARD30I)
Convert a ROM-format file created by the macro linker (MLINK30I)
to the memory-card format file (MEM format file) which can be
loaded from the memory card using the boot function.
Any of the following methods can be selected, but this manual uses
method (2) for description.
(1) Click [Start] and then click [Run].
Enter the following command line in [Open] and then click
<OK>.
MCARD30I file-spec [parameters]
(2) Click [Start], click [Programs], and then click [Command
Prompt]. Execute the command by entering it at the DOS
prompt.
Change the current directory to the folder in which the source
program is stored by using the CD command, and then execute
the following command line.
C:\> MCARD30I file-spec
*1file- spec
Specify the name of a ROM-format file to be converted without
using an extension. A MEM format file having the same name as
the ROM-format file and the extension .MEM is created.
- 20 -
Page 29
B-66264EN/014.FUNCTIONS
Execution example
C:\> CD MCOMP30I\USR\SAMPL
→Change the current directory to the folder in which the object file
is stored.
C:\MCOMP30I\USR\SAMPL>MCARD30I SAMPL
Execution result
- 21 -
Page 30
5.SYMBOLIC MACRO PROGRAMB-66264EN/01
5 SYMBOLIC MACRO PROGRAM
Format
A macro program is to be created according the rule described below.
(1) A macro program must start with address O. Address % must be
specified at the end of the file. Multiple programs can be coded
in a single file. At this time, the start of each program can be
identified by address O. Data after address %, if any, is ignored.
When multiple programs are coded, address % must be coded at
the end.
O0001 #101=1;
G00 X#101;
:
O0002 G243 X0 Y0 (ABS);
#500=#501+#502;
:
%
(2) One line can contain only one block. The end of block (EOB) is
represented by a semicolon (;). All data after a semicolon on a
line is regarded as a comment.
#100=#101; COMMENT
G00 X123. Y234. ; G01; → "G01 ;" after ; is regarded as
comment.
(3) All data after /* is regarded as a comment. A line starting with /*
is regarded as a comment line; such a line is not compiled.
/* comment→ Compiler ignores this line as comment line.
/* comment
/*
O0001 ;
/* comment→ Compiler ignores this line as comment line.
G00 ...;
;/* comment→ Blank block containing only ; is created.
M99;
%
- 22 -
Page 31
B-66264EN/015.SYMBOLIC MACRO PROGRAM
Programming using symbolic names
A symbolic name can be defined for a variable, expression, or
character string to allow programming using symbolic names. A
symbolic name can be defined as described below.
- Symbolic name definition
@xxxx yyyyyy
xxxx: Symbolic name
String of alphanumeric characters beginning with an
alphabetic character
Maximum 32 characters
yyyyyy : Definition character string
Maximum 80 characters
After a symbolic name is defined, the symbolic name used in a
program is replaced by the corresponding definition character string.
Program
O0001 ;
CURSOR ON ;
COUNT1 = COUNT1+1 ;
RETURN ;
Meaning
#8505 =1 ;
→
#100 = #100+1 ;
- Symbolic name for sequence number
A symbolic name can be assigned to a sequence number as described
below. In above Item, a symbolic name is just used for a definition
character string. On the other hand, a symbolic name for a sequence
number is regarded as a sequence number when it is coded at the start
of a block, and is regarded as a jump (GOTO) destination number
when it is coded at a position other than the start of a block.
Definition of symbolic name for sequence number
>xxxx 9999
xxxx : Symbolic name for sequence number
String of alphanumeric characters beginning with an
alphabetic character
Maximum 32 characters
9999 : Number
After a symbolic name is defined, the symbolic name used in a
program is replaced by the corresponding sequence number.
- 23 -
Page 32
5.SYMBOLIC MACRO PROGRAMB-66264EN/01
Example
/* SYMBOL DEFINE
@COUNT1#100
>JUMP1100
>SKIP200
/*
Program
Meaning
O0002 ;
GOTO JUMP1 ;
IF[COUNT1 LE 0]GOTO SKIP ;
SKIP ;
JUMP1 M99 ;
GOTO 100 ;
→
IF[#100 LE 0]GOTO 200 ;
N200 ;
N100 M99 ;
- Automatic conversion of hiragana and kanji codes
(Hiragana and kanji, when coded in quotation marks and parentheses
as ('
Compiler codes by coding.‘’)
(‘
Kanji and hiragana must be coded using full-size characters, and
alphanumeric characters, spaces, special symbols must be coded using
half-size characters.
'), can be auto-matically converted to internal Macro
’) % (*3929 3671 3872 3439 2437 245E 2439*)
- Reference to external file ($INCLUDE control statement)
By using the $INCLUDE control statement, a program, symbol
definition, and so forth contained in a separate file can be referenced.
With this function, definitions and processing common to multiple
programs can be specified in a separate file so that each program file
can reference those definitions and processing.
Example
-Program file
/*
INCLUDE \MCOMP30I\TOOL\SYSTEM.DEF
/*
Program
Meaning
O0003 ;
CMACRO1 =5 ;
RETURN ;
→
#8500 =5 ;
M99 ;
-Include file (\MCOMP30I\TOOL\SYSTEM.DEF)
@CMACRO1 #8500/* Conversation MACRO - 1 MAIN
@RETURN M99/* Return to main program.
- 24 -
Page 33
B-66264EN/015.SYMBOLIC MACRO PROGRAM
- Array variable coding
Variables can be used as a one-dimensional array by using a simple
coding method.
Coding method
#999 <expression>
999 : Number of first variable in array
By this coding method, variables can be referenced or written to as
array data with an index indicated by the expression and starting with
the variable specified in 999.
Example
#100<#101> is equivalent to #[100+#101].
- Reference list page eject control ($EJECT control statement)
By using the $EJECT control statement, reference list page eject
operation can be freely controlled.
Example
Program file
/*
$EJECT
/* → Advances reference list page.
O0003 ;
:
- Determination of an operation result
Only an operation expression can be specified as the condition of the
IF or WHILE statement. The execution of the IF or WHILE statement
is controlled depending on whether the operation result is equal to 0.
Format :
Example
The left macro instructions are equivalent to the right macro
instructions.
WHILE [#100] DO1 → WHILE [ #100 NE O ] DO1 ;
: :
END1 ; END1 ;
IF [#100+#101] GOTO123; → IF [[#100+#101] NE 0] GOTO123;
IF [SIN[#1]] THEN #1=0 ;→ IF [SIN[#1] NE 0] THEN #1=0 ;
WHILE[operation-expression] DOx ;
ENDx ;
IF[operation-expression] GOTO xxx ;
IF[operation-expression] THEN <Macro statement> ;
- 25 -
Page 34
5.SYMBOLIC MACRO PROGRAMB-66264EN/01
- Logical operations, AND and OR
Multiple conditions can be specified in an IF statement. The
conditions ANDed or ORed control the execution of the IF statement.
An AND is represented with an && sign and OR with an || sign. Up to
three ANDs or ORs can be specified in a single IF statement.
However, an AND and OR must not be specified together in a single
IF statement.
IF[<condition>&&<condition>&&<condition>&&<condition>]THEN <MACRO stmnt>; → OK
IF[<condition> || <condition> || <condition> || <condition>] GOTO xxx; → OK
IF[<condition> && <condition> || <condition>] GOTO xxx; → NG
The syntax of an IF statement has been enhanced. Structured
programming is possible using IF/THEN/ELSE/ENDIF.
The following shows the formats of syntactically valid IF statements.
(1) IF [...] GOTO 999 ;
(2) IF [...] THEN Macro-st ;
(3) IF [...] THEN Macro-st ;* Macro-st
ELSE Macro-st ; Macro statement
(4) IF [...]THEN ; * Statement
Statement ; Macro or NC statement
:
ENDIF ;
(5) IF [...] THEN ;
Statement ;
:
ELSE ;
Statement ;
:
ENDIF ;
(a) When only a single macro statement is to be executed, the macro
statement can be specified immediately after THEN/ELSE as
shown in (2) and (3).
IF[#100 EQ 0] THEN #101 = 1;
ELSE #101 = 2;
- 26 -
Page 35
B-66264EN/015.SYMBOLIC MACRO PROGRAM
(b) When an instruction to be executed is an NC statement or
multiple instructions to be executed, the NC statement or
multiple instructions must be specified between the THEN/ELSE
line and ENDIF line as shown in (4) and (5).
IF[#100 EQ 0] THEN ;
G01 X100 Y200 ;
ENDIF ;
When instructions with THEN and ELSE must be executed as
shown in (5), the IF statement can be specified by combining the
formats in (a) and (b).
IF[#100 EQ 0]
THEN #101 = 1;
ELSE ;
#101 = 2 ;
G00 X#103 ;
ENDIF ;
-Up to ten levels of nesting of the IF statement are allowed.
Example
The following is an example of three levels of
nesting, but up to ten levels of nesting are
allowed.
IF[...] THEN ;
IF [...] THEN ;
Statement ;
:
ELSE ;
IF[...] THEN ;
Statement ;
ENDIF ;
ENDIF ;
Statement ;
:
ELSE ;
Statement ;
:
ENDIF ;
3rd
level
2nd
level
1st
level
- 27 -
Page 36
5.SYMBOLIC MACRO PROGRAMB-66264EN/01
CAUTION
When only a single macro statement is to be
executed, the macro statement can be specified
immediately after THEN/ELSE. In this case, no
ENDIF statement is usually required. However, an
ENDIF statement is required when IF [...] THEN
Macro-st ; is specified just before ELSE or ENDIF
of the previous nesting as shown below:
IF[...] THEN ;
IF [...] THEN Macro-st ;
IF [...] THEN Macro-st ;
ENDIF ; ← The ENDIF line is required
ELSE ; because is specified just
before ELSE or ENDIF of
the previous nesting.
IF [...] THEN Macro-st ;
IF [...] THEN Macro-st ;
ENDIF ; ← The ENDIF line is required
ENDIF ; because is specified just
before ELSE or ENDIF of
the previous nesting.
- 28 -
Page 37
B-66264EN/016.SYMBOL DEFINITION FILE
6 SYMBOL DEFINITION FILE
When the system is installed, a symbol definition file for Series 30i is
stored under the directory \MCOMP30I\TOOL. For macro program
creation, the user should make full use of the symbolic names defined
in the file for variables.
Symbol definition file for Series 30i
File name: \MCOMP30I\TOOL\SYSTEM.DEF
To use this file, use the external file reference function described in
Item in Chapter 5, “SYMBOLIC MACRO PROGRAM”.
Usage example
$INCLUDE \MCOMP30I\TOOL\SYSTEM.DEF
For details, see Appendix C, “COMPILE/LINK EXAMPLE”.
For information about the defined symbols, see Appendix A,
“SYMBOL DEFINITION”.
- 29 -
Page 38
7.HOW TO VIEW REFERENCE LIST/ COMPILE LISTB-66264EN/01
7 HOW TO VIEW REFERENCE LIST/
COMPILE LIST
A source program coded using symbolic macro programs is converted
by the Macro Compiler to a program in custom macro format for
compile processing. The Macro Compiler outputs two types of list
files: one for a reference list, and the other for a compile list.
Since conversion processing is performed, the comment lines and
symbol definition lines in a source program are not listed. For this
reason, a reference list and compile list output two types of line
numbers to identify a compile error in a source program.
(1) Reference list
A source program coded using symbolic macro programs, cross
reference data of used symbols, error messages from conversion
processing, and so forth are output in a reference list.
Line number “S-Line” : Source program line number
“G-Line”: Line number after conversion
(2) Compile list
A program converted to a program in custom macro format, cross
reference data of used variables, compile error messages, and so
forth are output in a compile list.
Line number “G-Line” : Line number after conversion
“P-Line” : Line number for each program number
In the example below, the compile list has an error on G-Line
0002; the same G-Line 0002 in the reference list and the line 4 in
the source program have this error.
The table below indicates the error codes that may occur in compile
processing.
Compile Error Codes
Error codeMeaning
0000Compiled OK.
0201Too many program.
0202No program.
1001Find out period,on BLOCKDEL number.
1002BLOCKDEL number not match 1-9.
1003Find out program number,in unsuitable spot.
1004Find out SEQ number,in unsuitable spot.
1005NC statement default.
1006Find out not EOB code,MACRO statement after.
1007Not find '=',on MACRO statement.
1008DO-END nest too deep.
1009Not find Relational OP,on IF statement.
100aNot find GOTO,pair of IF statement.
100bNot find bracket,on IF statement.
100cFind out not EOB code,GOTOm after.
100dFind out not EOB code,DOm after.
100eFind out not EOB code,ENDm after.
100fNot agree END statement number to pair of DO.
1010Not find END,pair of DO.
1011Not find DO right of WHILE.
1012Not find ']' ,on WHILE[•••].
1013Illegal statement,NC or MACRO ?
1014Not find DO, pair of END.
1015Program NO. missmactch,directory to program.
1016Not find program NO. on top of the program.
1017Syntax ERR:THEN-END.
1018Syntax ERR:SETVN.
1019Syntax ERR:DEFADD.
101aSyntax ERR:POPEN.
101bSyntax ERR:PCLOS.
101cSyntax ERR:BPRNT.
101dSyntax ERR:DPRNT.
101eSyntax ERR:PGN.
1025Too many THEN statement.
1027No EOB code after ccall_statement.
1028IF statement, Nest too deep.
1029Logical AND and OR, Mixed up on if statement.
1030No ENDIF found on if then statement.
1031Too MANY condition statement (Max = 4).
1033Unsuitable ELSE found on if statement.
1034Unsuitable ENDIF found on if statement.
1035Unsuitable THEN found on if statement.
1201Nest of bracket,over 5 hold.
1202Not find ']',on #[•••].
1203Not find ']',on [•••].
1204Not find '[',on ATAN[•••]/[•••] of below the line.
1205Not find '/',on ATAN[•••]/[•••].
1206Not find ']',on ATAN[•••]/[•••] of above the line.
1207Not find ']',on [•••].
1208Illegal token function.
1209Illegal token function,left of <•••>.
120aIllegal token func,on <ad>[f] or <ad>-[f] or GOTO [f].
120bDimension Error.
1401Too many number,Max 9 hold.
1402Illegal period, after.
1403Too many macro digit,Max 6 hold.
1404Right of #,must have figure or '['.
1405Too many program NO.,Max 8 hold.
1406Too many sequence NO.,Max 8 hold.
1407Not find '[',on func [•••].
1408Not find '[',on IF[•••] or WHILE[•••].
1409Too many 'm',on DOm or ENDm.
140am of DOm•ENDm,not agree 1-3.
140bFind out non figure code on right of DO or END.
140cIllegal function code.
140dToo long func-code,Max 5 character.
140eNot find EOR on file.
140fFind out illegal code.
1410Too many string length, Max 255.
1411Too many hex code, max 4 hold.
1412Illegal hex code.
1413Find the undefind code.
1414Not close by '*)',on (*•••*).
1415Find the illegal string between '(' to ')'.
1416Find the illegal string between ',' to ';'.
1417Find the illegal string between '@' to '@'.
1418Not close by '@',on @•••@.
1419Too many hex code, max 2 hold.
1420Illegal length or character in Hex Image String.
1421Illegal 'O','N' number.
1601STACK over flow.
1602Location value size over flow.
- 50 -
Page 59
B-66264EN/01 APPENDIX B.COMPILE ERROR CODE TABLE
Compile Error Codes
Error codeMeaning
1603Amount of address over 50.
1604Too larg macro number,Max 6 hold.
1605MACRO number not >=0.
1606MACRO number period illegal.
1607Too long GOTO number,Max 8 hold.
1608GOTO number with period illegal.
1681Too many GOTO statement.
1682SEQ number not found.
1683Too many WHILE statement.
1684GOTO SEQ number duplicate.
1801P-CODE size over the ROM size.
1900'%' not find or illegal.
2000Push on key \"RESET\".
2001NC program Read ERR.
8000program number ERR.
8001ASCII to compiler code convert error.
9999missmatch err_code !!
- 51 -
Page 60
C.COMPILE/LINK EXAMPLEAPPENDIXB-66264EN/01
C COMPILE/LINK EXAMPLE
The compile/link example described below is created under the
directory
C:\MCOMP30I\USR\SAMPL
when the macro compiler utility system is installed.
Details of sample:
Times required for instruction execution by each of the
conversational macros are measured:
1. #100 = #101+#102 ;
2. #100 = #101 AND #102 ;
3. #100 = SIN [#101] ;
The number of test operations is set beforehand in the common
variable (#500). Time required for looping by the number of test
operations by the WHILE instruction is measured by the timer
variable (#3001). Then time required for the same number of loops by
the WHILE instruction containing an instruction subject to
measurement is measured. Thus the difference between two
measurement times is the execution time of the instruction subject to
measurement.
(1) Programs created
File name = MAIN.SRCMain source program file
File name = SUB1.SRCSubprogram source file
File name = MAIN.REFMain program reference list file
File name = MAIN.LSTMain program compile list file
File name = MAIN.RELMain program object file
File name = SUB1.REFSubprogram reference list file
File name = SUB1.LSTSubprogram compile list file
File name = SUB1.RELSubprogram object file
(2) Macro liner
File name = SAMPL.LNKLink control file
File name = SAMPL.MAPLink map list file
File name = SAMPL.ROMROM-format file
- 52 -
Page 61
B-66264EN/01 APPENDIX C.COMPILE/LINK EXAMPLE
Main program source fileFile name : MAIN.SRC
/*
/* SAMPLE Program.
/*
/* Conversation MACRO Execution-Time Test Program.
/* (Vol 01.00 2003.04.10)
/*
/*
/* ( MAIN Program )
/*
/*
/* Symbol define.
/*
/* System common symbole FILE Include.
/*
$INCLUDE C:\MCOMP30I\TOOL\SYSTEM.DEF
/*
/*
@LOOPCT #500 /* TEST Loop count.
@TIMESAV #501 /* No-operatinon Time save.
@TSTTIME #502 /* Measured Time save.
/*
/*
@COUNT #100 /* Loop counter work.
@WORK #100 /* Work regster.
/*
/*
>LOOP 100 /* GOTO Sequense No. define.
>FIN 999
/*
/*
$EJECT
/*
/* No. O1000 : Main program.
/*
O1000;
NUMREAD; Numeric data input.
CURSOR OFF; Cursol OFF
DISPLAY X0 Y0 B0 ('EXECUTION TIME TEST'); "MENU" display.
X2 Y2 ('1.#101=#102+#103');
X2 Y3 ('2.#101=#102 AND #103');
X2 Y4 ('3.#101=SIN[#102]');
;
LOOP DISPLAY X8 Y11 B1 (SELECT TEST NO.);
IF [KEYCODE NE INPUT]GOTO FIN; "INPUT" key push ?
IF [KEYDATA LT 1]GOTO FIN; 0 < DATA < 3 chk.
IF [KEYDATA GT 3]GOTO FIN;
---------- Object List ------------------------------------------------------
FILE NAMEPROGSIZE
MAIN.REL000010000000FAH
00001001000091H
SUB1.REL000011000000A3H
000012000000A7H
0000130000009CH
---------- ROM FILE SIZE ----------------------------------------------------
SIZE = 10000H ( 64KB )
Select type : 256K
Used size = 5771HB
Free size = 3A88FHB
- 77 -
Page 86
D.BOOT SYSTEMAPPENDIXB-66264EN/01
D BOOT SYSTEM
- 78 -
Page 87
B-66264EN/01 APPENDIX D.BOOT SYSTEM
D.1 OVERVIEW
The Boot System load the CNC system software (Flash RAM →
DRAM), then starts it so that software can be executed.
The Boot System provides the following maintenance functions for
the CNC:
(1) Registering a file in Flash ROM
Reads a file from a Memory card, in FAT format, into Flash
ROM.
(2) Checking a file (series and edition) in Flash ROM
(3) Checking a file (series and edition) in Memory card
(4) Deleting a file from Flash ROM
(5) Deleting a file from Memory card
(6) Saving a file in Flash ROM to a Memory card
(7) Batch saving and restoration of files of parameters and programs
backed up by battery (SRAM area), to and from a Memory card
(8) Formatting of a Memory card
This manual describes the activation of the Boot System, as well as
the screen displays and operation for the functions listed above.
CAUTION
1 This control unit supports the use of a Memory card as an input/output device. The
following Memory cards are available:
SRAM Memory card
Flash card
Flash ATA card
See the order list for details of the supported Memory card types.
2 On a Memory card, only those files that are in the root directory can be accessed for
display, reading, and writing. Those in subdirectories cannot be used.
3 The time required to read or write each data item varies depending on the Memory
card type, the status of use, and other factors.
4 For Flash cards, only those recommended by FANUC can be accessed for writing.
For reading, they can be usually be used in the same way as SRAM cards as long as
the FAT format is used.
When using a Flash card, note that the card capacity decreases by 128 KB.
A Flash memory card does not allow deletion of files one at a time. It is necessary to
delete all files on the card at a time.
5 For Flash ATA cards, only those recommended by FANUC are available.
6 When formatting a Flash ATA card, use the quick formatting method, which clears
the file allocation table and the directory information on the root directory. An
unformatted Flash ATA card cannot be used without being formatted with a personal
computer.
- 79 -
Page 88
D.BOOT SYSTEMAPPENDIXB-66264EN/01
D.1.1 Displaying the Power ON Sequence
(1)
RAM TEST :END
(2)
ROM TEST :END [60W1A]
(3)
DRAM ID :xxxxxxxx
(4)
SRAM ID :xxxxxxxx
(5)
FROM ID :xxxxxxxx
*** MESSAGE ***
(7)
LOADING CNC DATA-1xxxxxx/xxxxxx
END
RAM TEST :END
(2)
ROM TEST :ERROR
*** MESSAGE ***
ROM PARITY ERROR:NC BASIC. HIT SELECT.
(6)
Processing is stopped in the event of an
error
SELECT key → SYSTEM MONITOR
[SELECT][ YES ][ NO ][ UP ][ DOWN ]
Details of display items
(1) WORK RAM test results are displayed. In the event of an error,
however, the sequence is not displayable, and LED indication is
conducted without error display.
(2) BOOT ROM parity test results are displayed. During normal
operation, the series and edition are displayed. In the event of an
error, processing is stopped.
(3) The ID of the DRAM MODULE installed in the CNC is
displayed.
(4) The ID of the SRAM MODULE installed in the CNC is
displayed.
(5) The ID of the FROM MODULE installed in the CNC is
displayed.
(6) The CNC BASIC software in Flash memory is checked for
validity and, in the event of an error, an error is displayed. In the
event of an error, clicking the [SELECT] soft key allows you to
select the SYSTEM MONITOR screen.
(7) This message indicates that the CNC BASIC software is being
transferred to Flash memory to DRAM.
- 80 -
Page 89
B-66264EN/01 APPENDIX D.BOOT SYSTEM
D.1.2 Starting the Boot System
In ordinary system activation, the Boot System automatically transfers
files from Flash ROM to DRAM in the background.
The user is not aware of this operation. However, the Boot System
must be operated manually, from menu screen, when maintenance is
to be carried out or when the Flash ROM does not contain a required
file.
(1) In system maintenance, for example, to replace a file in Flash
ROM
Operation : Turn the power on by simultaneously pressing the
two soft keys at the right end. If no soft keys are provided as
with a touch panel, use MDI numeric keys 6 and 7.
1234567
After an FROM ID and other items are displayed on the CNC
screen, releasing the key brings you to the SYSTEM MONITOR
screen.
(2) When the Flash ROM does not contain a file required to start the
CNC
Immediately after the CNC is turned on, the Boot System starts
transferring files from Flash ROM to DRAM. If, for some reason,
a file required to start the CNC (NC BASIC) is not in Flash
ROM or has been destroyed, the Boot System is automatically
started.
D.1.3 System Files and User Files
The Boot System organizes files in Flash ROM into two main
groups : system files and user files. These two file types have the
following characteristics :
System files
CNC and servo control software provided by FANUC
User files
PMC sequence program (ladder), P-CODE macro program, and other
user-created files
- 81 -
Page 90
D.BOOT SYSTEMAPPENDIXB-66264EN/01
D.2 SCREEN CONFIGURATION AND OPERATING
PROCEDURE
When the Boot System is first started, the MAIN MENU screen is
displayed. This screen is described below :
MAIN MENU screen
SYSTEM MONITOR MAIN MENU60W1 - 01
(1)
1.END
(2)
2.USER DATA LOADING
(3)
3.SYSTEM DATA LOADING
(4)
4.SYSTEM DATA CHECK
(5)
5.SYSTEM DATA DELETE
(6)
6.SYSTEM DATA SAVE
(7)
7.SRAM DATA BACKUP
(8)
8.MEMORY CARD FORMAT
(9)
*** MESSAGE ***
SELECT MENU AND HIT SELECT KEY.
(10)
[SELECT][ YES ][ NO ][ UP ][ DOWN ]
(1) Screen title. The series and edition of
the BOOT SYSTEM are displayed at
the right end.
(2) Function for terminating the Boot
System and starting the CNC.
(3) Function for writing data to Flash ROM.
(4) Function for writing data to Flash ROM.
(5) Function for checking the edition of a
file in ROM.
(6) Function for deleting a file from Flash
ROM or Memory card.
(7) Function for making a backup copy of
the data stored on the Memory card.
(8) Function for backing up and restoring
the SRAM area
(9) Function for formatting a Memory card.
(10) Simple operating instructions and error
messages are displayed.
Operating procedure
Basic operation
Press the [UP] or [DOWN] soft key to select the desired function.
After positioning the cursor to the desired function, press the
[SELECT] soft key. Before executing a function, the system my
request confirmation from the operator by having him/her press the
[YES] or [NO] soft key.
Position the cursor.
[ UP ]
[ DOWN ]
Execute the
function
Select a function
[SELECT]
Select END
Check the selection
[ YES ]
[ NO ]
Return to original
state
- 82 -
Page 91
B-66264EN/01 APPENDIX D.BOOT SYSTEM
D.2.1 USER DATA LOADING/SYSTEM DATA LOADING Screen
Description
This screen is used to read a system or user file from a Memory card
into Flash ROM.
The USER DATA LOADING screen is used to load ROM data from
a Memory card to Flash memory.
The SYSTEM DATA LOADING screen is used to check the contents
of the ROM card installed in a Memory card and then load ROM data
from the Memory card to Flash memory.
Screen configuration
SYSTEM DATA LOADING
(1)
MEMORY CARD DIRECTORY (FREE[KB]: 5123)
(2)
1 G001A_B1.MEM 1048704 2003-01-01 12:00
(3)
2 G001A_B2.MEM 1048704 2003-01-01 12:00
3 END
(4)
(1) Screen title.
(2) The size of the free space of the
Memory card is displayed.
(3) A list of files in the Memory card is
displayed.
*** MESSAGE ***
SELECT MENU AND HIT SELECT KEY.
(5)
[SELECT][ YES ][ NO ][ UP ][ DOWN ]
Operating procedure
(4) Returning to the MAIN MENU.
(5) Message
(1) Position the cursor to the file to be read from the Memory card
and written to Flash ROM. Then, press the [SELECT] soft key.
-A single page can list up to ten file names.
-If the Memory card contains ten or more files, the
remaining files are displayed on another page.
To display the next page, press the
To display the previous page, press the
soft key.
soft key. The
END option is displayed on the last page.
The END option is displayed on the last page.
(2) When you select a file from the USER DATA LOADING screen,
you are prompted for confirmation.
SYSTEM DATA LOADING
MEMORY CARD DIRECTORY (FREE[KB]: 5123)
1 G001A_B1.MEM 1048704 2003-01-01 12:00
2 G001A_B2.MEM 1048704 2003-01-01 12:00
3 END
*** MESSAGE ***
LOADING OK ? HIT YES OR NO.
[SELECT][ YES ][ NO ][ UP ][ DOWN ]
- 83 -
Page 92
D.BOOT SYSTEMAPPENDIXB-66264EN/01
(3) When you select a file from the SYSTEM DATA LOADING
screen, a ROM data confirmation screen is displayed for
confirmation.
(4) To start loading, press the [YES] soft key. To cancel, press the
[NO] key.
*** MESSAGE ***
LOADING FROM MEMORY CARD xxxxxx/xxxxxx
[SELECT][ YES ][ NO ][ UP ][ DOWN ]
(5) When loading terminates normally, the system displays the
following message. Press the [SELECT] soft key. If an error
occurs, see C.3
*** MESSAGE ***
LOADING COMPLETE.
HIT SELECT KEY.
[SELECT][ YES ][ NO ][ UP ][ DOWN ]
- 84 -
Page 93
B-66264EN/01 APPENDIX D.BOOT SYSTEM
D.2.2 SYSTEM DATA CHECK Screen
Description
This screen is used to list files in Flash ROM or Memory card,
together with the corresponding numbers of management units in each
file and the series and edition of the software.
Screen configuration
SYSTEM DATA CHECK
(1)
1.FROM SYSTEM
(2)
2.MEMORY CARD SYSTEM
(3)
3.END
(4)
*** MESSAGE ***
SELECT MENU AND HIT SELECT KEY.
(5)
[SELECT][ YES ][ NO ][ UP ][ DOWN ]
(1) Screen title.
(2) Select the FROM SYSTEM screen.
(3) Select the MEMORY CARD SYSTEM
number of management units
constituting each file appears in
parentheses to the right of the filename.
(3) Returning to the MAIN MENU.
(4) Message
- 85 -
Page 94
D.BOOT SYSTEMAPPENDIXB-66264EN/01
Screen configuration (MEMORY CARD SYSTEM screen)
SYSTEM DATA CHECK
(1)
MEMORY CARD DIRECTORY (FREE[KB]: 5123)
(2)
1 G001A_B1.MEM 1048704 2003-01-01 12:00
(3)
2 G001A_B2.MEM 1048704 2003-01-01 12:00
3 END
(4)
(1) Screen title.
(2) The size of the free space of the
Memory card is displayed.
(3) A list of files in the Memory card is
displayed.
(4) Returning to the MAIN MENU.
*** MESSAGE ***
SELECT FILE AND HIT SELECT KEY.
(5)
[SELECT][ YES ][ NO ][ UP ][ DOWN ]
(5) Message
Operating procedure
(1) Select either the FROM SYSTEM or MEMORY CARD
SYSTEM screen.
(2) Select the file that you want to confirm (for example, "NC BAS-
1 (0008)").
(3) For the selected file, the management unit numbers are listed,
together with the series and editions of the management units.
After checking the listed data, select the [SELECT] soft key to
return to the file selection screen.
HIT SELECT KEY.
[SELECT][ YES ][ NO ][ UP ][ DOWN ]
(1) Screen title.
(2) The following items are displayed for
each management unit:
- Series
- ROM number and edition
- Internal management-unit number
If a check result cannot be displayed, a
"@" is displayed.
- 86 -
Page 95
B-66264EN/01 APPENDIX D.BOOT SYSTEM
Others (Parity information for the system file and user file)
The NC BAS-1, DGD0SRVO, and other system files in Flash ROM
contain parity information in each management unit. If the file name
field or parity field on the check screen contains a non-ASC II
character or an "@", the Flash ROM may have been destroyed or a
damaged file may have been read. Re-read the data from the Memory
card.
The PMC1, and other user files do not contain parity information in
each management unit. A non-ASCII character or an "-" may appear
in the series/edition information. In this case, it does not indicate that
the file has been damaged.
- 87 -
Page 96
D.BOOT SYSTEMAPPENDIXB-66264EN/01
D.2.3 SYSTEM DATA DELETE Screen
Description
This screen is used to delete a user file from Flash ROM or Memory
card.
Screen configuration
SYSTEM DATA DELETE
(1)
1.FROM SYSTEM
(2)
2.MEMORY CARD SYSTEM
(3)
3.END
(4)
*** MESSAGE ***
SELECT MENU AND HIT SELECT KEY.
(5)
[SELECT][ YES ][ NO ][ UP ][ DOWN ]
(1) Screen title.
(2) Select the FROM SYSTEM screen.
(3) Select the MEMORY CARD SYSTEM
The number of management units
constituting each file appears in
parentheses to the right of the filename.
(3) Returning to the MAIN MENU.
(4) Message
- 88 -
Page 97
B-66264EN/01 APPENDIX D.BOOT SYSTEM
Screen configuration (MEMORY CARD SYSTEM screen)
SYSTEM DATA DELETE
(1)
MEMORY CARD DIRECTORY (FREE[KB]: 5123)
(2)
1 G001A_B1.MEM 1048704 2003-01-01 12:00
(3)
2 G001A_B2.MEM 1048704 2003-01-01 12:00
3 END
(4)
(1) Screen title.
(2) The size of the free space of the
Memory card is displayed.
(3) A list of files in the Memory card is
displayed.
(4) Returning to the MAIN MENU.
*** MESSAGE ***
SELECT FILE AND HIT SELECT KEY.
(5)
(5) Message
[SELECT][ YES ][ NO ][ UP ][ DOWN ]
Operating procedure
(1) Select either the FROM SYSTEM or MEMORY CARD
SYSTEM screen.
(2) Select the file you want to delete.
(3) The following message is displayed for confirmation.
*** MESSAGE ***
DELETE OK ? HIT YES OR NO.
[SELECT][ YES ][ NO ][ UP ][ DOWN ]
(4) Click the [YES] soft key to start reading. Click [NO] to cancel
reading.
*** MESSAGE ***
EXECUTING
ADDRESS xxxx:
[SELECT][ YES ][ NO ][ UP ][ DOWN ]
(5) Upon normal termination, a message such as that shown below is
displayed. Click the [SELECT] soft key. In the event of an error,
see the list of error messages and corrective actions, given later.
*** MESSAGE ***
DELETE COMPLETE. HIT SELECT KEY.
[SELECT][ YES ][ NO ][ UP ][ DOWN ]
Others (System files and user files on SYSTEM DATA DELETE screen)
The system files are protected from accidental deletion. User files,
however, are not protected. Protected system files can be overwritten
from the USER DATA LOADING / SYSTEM DATA LOADING
screen.
- 89 -
Page 98
D.BOOT SYSTEMAPPENDIXB-66264EN/01
D.2.4 SYSTEM DATA SAVE Screen
Description
This screen is used to write a user file in Flash ROM to a Memory
card. Only user files can be saved from Flash ROM to a Memory card.
System files cannot be saved.
The number of management units
constituting each file appears in
parentheses to the right of the filename.
(3) Returning to the MAIN MENU.
*** MESSAGE ***
SELECT FILE AND HIT SELECT KEY.
(4)
[SELECT][ YES ][ NO ][ UP ][ DOWN ]
Operating procedure
(4) Message
(1) Select the file you want to save.
(2) The system displays the following confirmation message :
*** MESSAGE ***
SYSTEM DATA SAVE OK ? HIT YES OR NO.
[SELECT][ YES ][ NO ][ UP ][ DOWN ]
(3) To start saving, press the [YES] key. To cancel, press [NO].
*** MESSAGE ***
STORE TO MEMORY CARD
[SELECT][ YES ][ NO ][ UP ][ DOWN ]
- 90 -
Page 99
B-66264EN/01 APPENDIX D.BOOT SYSTEM
(4) When saving terminates normally, the system displays the
following message. Press the [SELECT] key. The names of files
written to the Memory card are listed. Check the file names by,
for example, making a note of the list.
*** MESSAGE ***
FILE SAVE COMPLETE. HIT SELECT KEY.
SAVE FILE NAME : PMC1.000
[SELECT][ YES ][ NO ][ UP ][ DOWN ]
Others (System files and user files on SYSTEM DATA SAVE screen)
The SYSTEM DATA SAVE function provides a safeguard against
free copying of the system files.
User files, however, are not protected.
Files saved from Flash ROM to a Memory card have the following
names :
Header ID in Flash ROMFile name in Memory card
PMC1.xxx
PMC1
PD010.5M
PD011.0M
→
PD010_5M.xxx
→
PD011_0M.xxx
→
"xxx" is replaced by one of 32 numbers "000", "001", ,,, and "031".
For example, if you attempt to save the file "PMC1 " from Flash
ROM to a Memory card, it will be saved with a name of "PMC1.000"
if no file with a name of "PMC1.000" is found on the Memory card. If,
however, that file is saved to a Memory card that already contains a
file named PMC1.000, the saved file is named PMC1.001. As files are
added, the extension is incremented up to a maximum of PMC1.031.
Any no-longer used numbers in the sequence of the extension
numbers are used in as cending order. If two or more files having
identical names but different extension numbers are normally saved to
the Memory card, check the file names displayed subsequently.
- 91 -
Page 100
D.BOOT SYSTEMAPPENDIXB-66264EN/01
D.2.5 SRAM DATA BACKUP Screen
Description
This screen is used to collectively save and restore parameters,
programs, and other data, retained after the CNC power in SRAM is
turned off, to and from a Memory card.
Screen configuration
SRAM DATA BACKUP
(1)
1.SRAM BACKUP ( CNC -> MEMORY CARD )
(2)
2.RESTORE SRAM ( MEMORY CARD -> CNC )
3.END
(3)
(1) Screen title.
(2) Menu
(3) Returning to the MAIN MENU.
(4)
(5)
(6)
SRAM FILE SIZE : 1MBYTE
SRAMBAK.001
*** MESSAGE ***
SET MEMORY CARD NO.001
ARE YOU SURE ? HIT YES OR NO.
[SELECT][ YES ][ NO ][ UP ][ DOWN ]
*** MESSAGE ***
SELECT MENU AND HIT SELECT KEY.
[SELECT][ YES ][ NO ][ UP ][ DOWN ]
Operating procedure (Backing up data)
(1) Select "1.SRAM BACKUP" The following confirmation
message is displayed. Click [YES] to start backup.
(2) If the data cannot be saved entirely onto a single Memory card, a
message such as that shown below is displayed. With the power
still on, insert the second Memory card and click the [YES] key.
Press the [NO] key to cancel saving.
(4) The SRAM file size is displayed.
(Displayed after a processing option is
selected.)
(5) The name of the file currently being
saved or loaded is displayed. (Displayed
after a processing option is selected.)
(6) Message
*** MESSAGE ***
SET MEMORY CARD NO.002
ARE YOU SURE ? HIT YES OR NO.
[SELECT][ YES ][ NO ][ UP ][ DOWN ]
(3) In this way, you can divide SRAM data onto a maximum of 999
Memory card for backup.
- 92 -
Loading...
+ hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.