OSP-P200L-P20L
OSP-P200L-P20L Chapter 7 Error
5001 IGF data undefined
Eeoelale7124 When the [IGF] or [Easy Modeling IGF] function key is pressed, no IGF data is received from the PLC, generating an alarm.
[Remedy]
Check whether the PLC is set to generate IGF expert data via the NC parameter screen when the power is turned on.
5002 Load information file not found
The load information file cannot be found when loading tool parameter setting information.
Or, instructions matching the load information file do not exist.
[Character-string]
Applicable file name
[Probable Fault Cause]
Installation failure, media transfer error, specification code error
[Action to Take]
Reinstall.
Overwrite installation via FD.
5200 Main program running
Eeoelale7125 An attempt was made to select a program during main program execution. Or, an attempt was made to change the shape in cam turning specification mode.
[Character-string]
None
[Code]
1-> Attempted to select a program
2-> Attempted to select a schedule program
3-> Attempted to perform sequence number search
4-> Attempted to perform restart
7-> Attempted to execute shape change (cam turning specification)
[Remedy]
Select the program after NC reset.
5201 No main program file
Eeoelale7126 The main program file cannot be found.
[Character-string]
None
[Code]
1
[Probable Fault Cause]
Operation error
[Remedy]
• Correctly define the main program file name.
• If the file does not exist, create it.
5202 No main program name
Eeoelale7127 The main program name to be loaded cannot be found.
[Character-string]
None
[Code]
1
[Probable Fault Cause]
Operation error
[Remedy]
• Correctly define the main program file name.
• If the file does not exist, create it.
5203 No subprogram
Eeoelale7128 The subprogram designated by the part program cannot be found.
Or, although a G-code or M-code macro command was specified in the part program, the corresponding subprogram is not set on the *G-CODE MACRO M-CODE MACRO* setting screen in parameter setting mode.
[Character-string]
Subprogram name not found
[Code]
1
[Probable Fault Cause]
Program creation error.
[Remedy]
Create the required subprogram.
[Reference Manual]
Operation Manual.
5204 Subprogram name
Eeoelale7129 Erroneous subprogram name or subprogram name not found.
[Character-string]
Call record buffer
[Code]
1-> The subprogram name cannot be found in the call record buffer.
2-> The program name exceeds 5 characters including "O".
[Probable Fault Cause]
• Program error
(1) N100 CALL
(2) N100 CALL OABCDE
[Remedy]
Check the program and designate the subprogram call command correctly.
[Related Specifications]
Subprogram specification
5205 Schedule program running
Eeoelale7130 The operation specified below was attempted during schedule program execution.
* Program select
* Schedule program select
* Sequence number search
* Restart
Or, an attempt was made to change the shape in cam turning specification mode.
[Character-string]
None
[Code]
1-> Attempted to select a program
2-> Attempted to select a schedule program
3-> Attempted to perform sequence number search
4-> Attempted to perform restart
7-> Attempted to execute shape change (cam turning specification)
[Probable Fault Cause]
Operation error
[Remedy]
Reset the NC first before attempting the operations above.
5206 No schedule program file
Eeoelale7131 The schedule program file cannot be found.
[Character-string]
None
[Code]
1
[Probable Fault Cause]
Operation error
[Remedy]
• Correctly define the schedule program name.
• Or, if invalid, create a schedule program.
5207 Program search
Eeoelale7132 During the sequence number search operation, the definition block with the specified sequence number was not found.
The program search command was issued while an alarm was active.
[Code]
1-> The main program is not loaded or an alarm has occurred.
2-> The specified sequence name was not found.
[Probable Fault Cause]
Program error or operation error
[Remedy]
• Check whether an alarm has occurred.
• Check whether the main program has been loaded.
• Check whether the specified sequence number exists.
• Check the specified sequence name and the sequence name in the program.
5208 Schedule program search
Eeoelale7133 The selected schedule program cannot be found.
[Character-string]
None
[Code]
1
[Probable Fault Cause]
Operation error
[Remedy]
Use the DIR command to confirm that the required schedule program is in memory. Then select the program again.
5209 Program end code
Eeoelale7134 The program end code is not defined at the end of the file.
[Character-string]
None
[Code]
1-> No end code in main program (M02, M30)
2-> No end code in subprogram (RTS)
3-> No end code in subprogram within MSB
[Probable Fault Cause]
Error during program creation
[Remedy]
Check the end code of the main program or subprogram. In the above example, since the RTS end code was not designated, it must be specified.
5210 Program stack overflow
Eeoelale7135 The number of subprogram names called by CALL or MODIN commands, or maker subprograms in the main program, subprogram, or maker subprogram exceeds 128.
[Character-string]
None
[Code]
1
[Probable Fault Cause]
Program error
[Remedy]
• Delete unnecessary subprograms.
• Create a program that takes this limit into consideration.
5211 Program buffer overflow
Eeoelale7136 The program is too large to be stored in the program buffer.
[Code]
1-> The program is too large. Or, the subprogram registered in the library is larger than the library program buffer capacity.
2-> The MSB is too large.
3-> The MSB cannot be used due to memory capacity limitations.
[Probable Fault Cause]
Defective program
[Remedy]
• Create a program within the program buffer capacity (standard: 30m).
• If the alarm occurs when registering a library program, re-specify and expand the library program buffer capacity.
5212 No edit data
Eeoelale7137 When starting editing using the R option to recover edit data, there is no data in the edit buffer.
[Character-string]
None
[Code]
None
[Probable Fault Cause]
Operation error
[Remedy]
Recovery is impossible.
5213 Edit buffer move range
Eeoelale7138 During edit buffer move operation, the move range was exceeded.
[Character-string]
None
[Code]
XXXXXXXX-> Data end point
5214 Edit buffer overflow
Eeoelale7139 The edit buffer is full.
[Character-string]
None
[Code]
XXXX-> The destination address in the edit buffer is outside the edit buffer area
[Probable Fault Cause]
Operation error
[Operation Example]
Attempted to edit a program exceeding the edit buffer capacity.
[Remedy]
Edit a program within the program buffer capacity (standard: 30m).
5215 Record buffer overflow
Eeoelale7140 During program editing, the editing operation cannot be performed due to erroneous file data.
* The number of characters in a block exceeds the buffer memory limit.
[Character-string]
A record that caused the error, or none
[Code]
1-> Error when reading a record from the edit buffer.
2-> Error when reading a record from the screen buffer.
[Probable Fault Cause]
Erroneous program editing operation
[Program Example]
Refer to the above example.
[Remedy]
Correct the file as necessary.
5216 Record buffer move range
Eeoelale7141 During edit buffer move, the move range was exceeded.
[Character-string]
None
[Code]
1-> Move end point < Move start point
2-> Move to reverse point of record buffer
[Probable Fault Cause]
Normally, this error does not occur.
[Remedy]
• After pressing the edit execute key, edit the program again.
• Recovery is possible via the option R command.
5217 Sequence number designation
Eeoelale7142 In the sequence number allocation command, there is an operand error.
[Code]
1 -> The start sequence number or the sequence number increment value is 4 digits or more.
2 -> No separating comma
3 -> Operand is empty.
4 -> Format error in operand area.
[Probable Fault Cause]
Operation error
[Remedy]
Input the operand correctly.
[Reference Manual]
Operation Manual
5218 Sequence number overflow
Eeoelale7143 During sequence number allocation, the sequence number exceeded 3 digits.
[Character-string]
None
[Code]
Hexadecimal value of the allocated sequence number
[Probable Fault Cause]
• Too many sequence numbers to allocate.
• The sequence number increment value is too large.
[Remedy]
Designate the start sequence number and the increment value taking sequence numbers into consideration.
5219 Display buffer overflow
Eeoelale7144 The screen buffer used for editing is full.
[Character-string]
None
[Code]
None-> No screen area record in screen buffer.
[Probable Fault Cause]
This alarm does not normally occur.
5220 Tape vertical check
Eeoelale7145 In TV check of reading one block of tape, data in the block is odd.
[Character-string]
None
[Code]
XX-> Data error causing tape TV check
[Probable Fault Cause]
Error during tape punching
[Measures to Take]
Correct the tape TV data.
5221 No tape data
Eeoelale7146 No data although verify was attempted.
[Character-string]
None
[Code]
None
[Probable Fault Cause]
Error during tape punching
[Measures to Take]
Correct the tape.
5222 Tape parity check
Eeoelale7147 Tape parity mismatch
[Character-string]
None
[Code]
XX-> Data causing parity error
[Probable Fault Cause]
Error during tape punching
[Measures to Take]
Check the tape
5223 Tape file name
Eeoelale7148 Incorrect tape file name - invalid character used, too many characters, etc.
[Character-string]
Command file name
[Code]
5-> Number of characters in the file is more than 19.
6-> File name and extension are not separated by ”,”.
7-> First character of file name or extension is not an alphabetical character.
[Probable Fault Cause]
Tape punching error
[Measures to Take]
Read data from a tape with correctly punched file name.
5224 Tape read verify
Eeoelale7149 Mismatch between tape information and file information
[Character-string]
None
[Code]
XXYY
XX-> Verify error in memory information
YY-> Verify error in tape block information
[Probable Fault Cause]
Tape read operation error
[Measures to Take]
Check the tape and read data again.
5225 Tape end code mismatch
Eeoelale7150
Tape end code does not match that defined by parameter (bit) No. 1, bit 3
5226 Tape illegal code
Eeoelale7151 A special code is punched on the tape.
The following settings are available by optional parameter (bit) No. 1, bits 6 and 7:
Bit 7 Bit 6
0 0 Special code is read as is.
0, 1 1 Error occurs when special code is used.
1 0 Special code is ignored.
The following settings can be made by optional parameters.
Optional parameter (external I/O)
Tape special code alarm
Ignore tape special code
No. 7 No. 6
0 0 Special code is read as is.
0, 1 1 Error occurs when special code is used.
1 0 Special code is ignored.
[Character-string]
None
[Code]
XX-> Data causing error
[Probable Fault Cause]
Erroneous data (code not used in EIA or ISO system was read).
[Measures to Take]
Check tape punch data to see if there is any code not accepted in EIA or ISO code system.
5227 Tape data
Eeoelale7152 Error in tape reading or verify
[Character-string]
None
[Code]
Frequency of error occurrence in hexadecimal number
[Probable Fault Cause]
Incorrect tape data (code not used in EIA/ISO system was used; parity error)
[Measures to Take]
Check punch data; see if there is any code not used in EIA or ISO system.
5228 Invalid EIA code
Eeoelale7153 During file punch and read operations, a character not usable in EIA code was found. ($, *, =, [, ], etc.)
[Character-string]
None
[Code]
XX-> Data causing error
[Probable Fault Cause]
Data error
[Measures to Take]
Check whether codes other than those in EIA system are used. For codes not defined in EIA system but frequently used, corresponding bit patterns can be set in parameter (bit) No. 26 to No. 30.
By setting bit patterns for special codes, reading or punching them will not cause an error.
5229 Input file name mismatch
Eeoelale7154 Input file name does not match specified file name
[Character-string]
Tape file name (input file name)
[Code]
None
[Probable Fault Cause]
File name on tape does not match input file name specified for read or verify operation.
[Measures to Take]
Specify input file name correctly.
5230 No file data
Eeoelale7155 An attempt was made to read a tape containing no file data.
Tape format:
The tape being read does not conform to the format shown above, and does not contain section (5).
[Character-string]
None
[Code]
None
[Probable Fault Cause]
• Error in creating NC tape.
• A tape as shown below was created and read.
[Measures to Take]
Create the tape correctly.
5231 File record read
Eeoelale7156 When reading a file to load it into program buffer or during program punch output operation, the designated command cannot be executed due to file data error.
[Character-string]
None
[Code]
1-> One record contains more than 156 characters
2-> During file read, end of file does not match end of record
[Probable Fault Cause]
File editing error
[Measures to Take]
Correct erroneous data
5232 File attribute
Eeoelale7157 When option A is specified for COPY command, input or output file is not a contiguous file (part program).
[Character-string]
None
[Code]
1-> Input file is not a contiguous file.
2-> Output file is not a contiguous file.
[Probable Fault Cause]
Error in specifying input/output file for copy
[Measures to Take]
Check file names and specify correct file name (part program).
5233 System data
Eeoelale7158 During execution of transfer command, an error occurred in SP service routine file operation.
[Character-string]
None
[Code]
XXYYYYYY
XX:
1-> NC received EOF without reading even one character from file.
2-> For indirect data transfer, file buffer size is not 2048 bytes.
3-> NC received EOF while reading data from file.
5-> NC attempted to open write-protected file in continuous output mode.
6-> Contradiction among 4 kinds of input parameters requesting file open: file open mode (D2), direct/indirect transfer (file buffer address =0/≠0), OSP/IBM format file attribute.
(Refer to error check table of input parameters in file open operation.)
9-> An incorrect device name was specified.
10-> An incorrect file name was specified.
11-> Directory file was not found.
12-> An attempt was made to execute PUT command to a file opened in input mode, or GET command to a file opened in output mode.
YYYYYY-> Return address to check routine causing error
5234 Extension
Eeoelale7159 For a file registered in an IBM format device, extension is not SS, SU, MI, SD, or blank.
[Character-string]
File name
[Code]
None
[Probable Fault Cause]
Operation error
[Measures to Take]
Use only permitted extensions.
5235 Device name
Eeoelale7160 Incorrect device name is specified.
Or device name specified for rename is different from source device name.
[Character-string]
Specified device name or none
[Code]
1-> Device names before and after rename do not match properly
None-> Cases other than ”code 1″.
[Probable Fault Cause]
• Input device name is misspelled
• Specified device name is not permitted.
• Specified device name is different from source device name (RENAME command)
[Measures to Take]
Refer to Operation Manual.
In rename operation, a device name that does not require renaming was specified.
5236 RS232C channel in use
Eeoelale7161 Specified RS232C channel is currently used for another task.
[Character-string]
None
[Code]
1->CN0: (TT:)
2->CN1:
3->CN2:
4->CN3:
[Probable Fault Cause]
Operation error
[Measures to Take]
Use another RS232C channel or wait until the task using this RS232C channel is completed.
5237 RS232C device read
Eeoelale7162 Reading from RS232C device is impossible, or RS232C device error occurred.
[Character-string]
None
[Code]
FFFFFF-> No data can be read from RS232C device.
XX-> Error
[Probable Fault Cause]
Defective RS232C device or line fault
[Measures to Take]
Check the RS232C device.
Check the settings of RS232C-related NC parameters.
Check the line.
5238 RS232C terminal not ready
Eeoelale7163 In communication via RS232C interface in PIP or DNC mode, DR signal was interrupted for the period set by parameter (parameter (word) No. 34 - No. 38).
(Optional parameter (RS232C) RS232C busy time
[Character-string]
None
[Code]
0 – 3 (RS232C device signal)
[Probable Fault Cause]
• Power to the mating station is not turned on.
• Fault in the RS232C interface of the mating station or OSP.
• Defective communication cable
[Measures to Take]
• Check and turn on the power to the mating station.
• Check the RS232C interface of the mating station or OSP.
• Check the communication cable.
5239 RS232C read buffer overflow
Eeoelale7164 Read buffer overflow occurred in PIP or DNC with DC code.
[Character-string]
None
[Code]
None
[Probable Fault Cause]
• Data transmission from the peripheral device did not stop even though DC3 was sent from the CNC.
• Defective RS232C interface on the peripheral device or CNC.
• Communication cable fault
[Measures to Take]
• Check whether data transmission from the peripheral device stops upon sending the DC3 code.
• Check the RS232C interface of the peripheral device or CNC.
• Check the communication cable.
5240 RS232C ready interrupt timeout
Eeoelale7165 During communication in PIP or DNC mode, data transmission from the peripheral device was interrupted for the period set by parameter.
[Parameter]
Parameter (word) No. 34 - No. 38
Optional parameter (RS232C) RS232C busy time
[Probable Fault Cause]
• Defective RS232C interface on the peripheral device or OSP.
• Communication cable fault
[Measures to Take]
• Check the RS232C interface of the peripheral device or OSP.
• Check the communication cable.
5241 DC code
Eeoelale7166 In DC code control communication, a DC code other than the expected reception wait DC code was received.
[Character-string]
None
[Code]
X -> Received DC code
[Probable Fault Cause]
Error in the peripheral device or RS232C interface.
[Measures to Take]
Check the RS232C interface or peripheral device.
5242 DNC device
Eeoelale7167 The RS232C device number set by parameter is incorrect (not 0 - 3). However, in actual setting, numbers other than 0 - 3 are not accepted and the alarm does not occur.
[Parameter]
Optional parameter word No. 46
Optional parameter (DNC-A) DNC input/output device number
[Probable Fault Cause]
• Setting of parameter word No. 46.
• Setting of DNC input/output device number.
[Measures to Take]
Change the setting value to a value within 0 - 3.
5243 DNC verify
Eeoelale7168 A DNC verify error occurred during verification.
[Character-string]
None
[Code]
2 -> Received NC data still exists even though the file has ended.
1 -> The file still exists even though received NC data has ended.
Other -> Character number where a mismatch was found by comparing the received data with the file
[Probable Fault Cause]
• NC program data contents
• An incorrect program was used for verify operation.
[Measures to Take]
• Correct the program data contents.
• Check the program (or file) name to be verified.
5244 DNC backup file
Eeoelale7169 In DNC mode output and verify, when a backup file name was specified to store its file name and the extension was omitted, the backup file name was not found.
[Character-string]
None
[Code]
None
[Probable Fault Cause]
Operation error
[Measures to Take]
Specify the file name to be output or verified.
[Related Specifications]
DNC-C
5245 DNC no such NC program
Eeoelale7170 The NC program requested in DNC mode (input or verify command) on the host computer was not found.
[Character-string]
Requested file name
[Code]
None
[Probable Fault Cause]
Operation error
[Measures to Take]
Request the program again after confirming the current file name on the host computer.
[Related Specifications]
DNC-C
5246 DNC file name mismatch
Eeoelale7171 During input and verify in DNC mode, the file name requested by the host computer did not match the received file.
[Character-string]
Received file name
[Code]
None
[Probable Fault Cause]
Processing error on the host computer
[Measures to Take]
Check processing operations on the host computer.
[Related Specifications]
DNC-C
5247 DNC setting condition
Eeoelale7172 A contradiction occurred during DNC-C communication parameter setting diagnosis.
Setting Criteria
TM6 < TM1
TM7 < TM1
TM1 < TM9
TM4 < TM2
TM3 < TM1
TM5 < TM1
(For TM*, refer to the DNC-C Instruction Manual.)
[Character-string]
None
[Code]
None
[Probable Fault Cause]
Operation error
[Measures to Take]
Set data satisfying the conditions specified above.
[Related Specifications]
DNC-C
5248 DNC communicating
Eeoelale7173 An attempt was made to execute an unexecutable command during transmission with the host computer.
[Character-string]
None
[Code]
1 -> An attempt was made to execute any of the following commands during NC program reverse transfer in stand-alone mode.
Program select
Schedule program select
Cursor-move sequence number search
Schedule program search
Animation standard/enlarged scale setting
Restart
[Probable Fault Cause]
Operation error
[Measures to Take]
Wait until reverse transfer is completed.
(Wait until the data communication lamp turns off.)
[Related Specifications]
DNC-C
5249 DNC response wait timeout
Eeoelale7174 For input, verify, data input, and data verify operations, the text response from the host computer could not be obtained within the interval set by parameter (word) No. 57.
[Character-string]
None
[Code]
1 -> No text response
2 -> A data number that cannot be specified was specified in all-data input or data verify operations.
[Probable Fault Cause]
The host computer response time exceeded the range set in parameter No. 57.
[Measures to Take]
• Reset the timer data in parameter No. 57.
• Reset the timer data in parameter No. 52.
[Related Specifications]
DNC-C
5250 FMS link mode
Eeoelale7175 In automatic operation mode with DNC-C2 or C3 specifications, an attempt was made to perform any of the following operations:
– Program select
– Schedule program select
– Sequence number search
– Cursor-move sequence number search
– Restart
– Schedule program search
– Animation scale setting
[Character-string]
None
[Code]
None
[Probable Fault Cause]
Operation error
[Measures to Take]
Change the operation mode to stand-alone or interrupt mode, then perform the desired operation again.
5251 DNC transmission disabled
Eeoelale7176 An attempt was made to perform batch transfer of NC programs when DNC-C was not ready for transmission.
[Character-string]
None
[Code]
1 -> Attempted during communication alarm.
2 -> DNC communication is OFF.
3 -> Interrupt mode is not established. (Only for DNC-C3 specification)
4 -> Ready status is not established. (Only for DNC-B specification)
[Probable Fault Cause]
Operation error
[Measures to Take]
1 -> Reset the communication mode.
2 -> Turn the communication switch ON, then turn the power on again.
3 -> Select interrupt mode.
4 -> Wait until ready status is established.
[Related Specifications]
DNC-B, C
5252 Buffer operating
Eeoelale7177 When buffer operation is turned ON or buffer operation is in DNC-B mode, an attempt was made to perform any of the following operations (common to protocols A and B):
a) NC program batch transfer. (Disabled only for remote operation)
b) Sequence number search
c) Cursor-move sequence number search
d) Schedule program sequence number search
e) Schedule program select
f) Program select (only for protocol A remote operation mode (2))
g) Animation standard/enlarged scale setting
h) When program select was executed in protocol A remote operation mode (2), a main program name or subprogram name had already been designated.
[Character-string]
None
[Code]
1 -> An attempt was made to execute a).
2 -> An attempt was made to execute b) - f).
3 -> An attempt was made to execute h).
4 -> An attempt was made to execute g) in remote operation.
[Probable Fault Cause]
Operation error
5253 DNC setting disabled
Eeoelale7178 A communication parameter that is disabled for the DNC-C specification was set.
[Character-string]
None
[Code]
None
[Probable Fault Cause]
Operation error
[Measures to Take]
The set parameter cannot be used for the DNC-D specification.
[Related Specifications]
DNC-C
5254 DNC data type
Eeoelale7179 In DNC-C mode data input, data output, and data verify operations, a data number that cannot be designated was specified.
[Character-string]
None
[Code]
None
[Probable Fault Cause]
Operation error
[Measures to Take]
Designate a data number in the range of 0 - 5 that is permitted by the selected specification.
[Related Specifications]
DNC-C
5255 DNC data range
Eeoelale7180 In DNC-C mode data input, data output, and data verify operations, incorrect data was designated when requesting or transmitting data.
[Character-string]
None
[Code]
1 -> Data designation format error
2 -> More than one range was designated for the same data (same turret).
3 -> The following condition was not satisfied:
1 ≤ start number ≤ end number ≤ maximum number
4 -> Turret B data was designated in single-saddle mode.
[Probable Fault Cause]
Operation error
[Measures to Take]
Enter the correct format number and the correct data number.
[Related Specifications]
DNC-C
5256 Input data overflow
Eeoelale7181 The input data size is too large or too small.
[Character-string]
None
[Code]
XXXXXXXX-> Hexadecimal representation of the set maximum/minimum value.
When an incremental limit is set, the incremental value is displayed.
For common variables, an operation error status is displayed.
[Probable Fault Cause]
Operation error
[Measures to Take]
Enter a numerical value within the allowable range.
5257 Number of digits
Eeoelale7182 Incorrect data setting on the data setting screen.
For integer and real data, the number of set digits exceeds 8.
Note that only APA offset data can be set up to 9 digits.
[Character-string]
None
[Code]
Acceptable number of digits
1-> Bit data contains a decimal point.
[Probable Fault Cause]
Data setting error
[Measures to Take]
• Set data correctly.
• The number of digits must be within the allowable range.
5258 Numerical data
Eeoelale7183 Incorrect data setting on the data setting screen.
Characters other than ”0″ and ”1″ are included in parameter bit data.
Characters other than numerical values are included in integer data and real data.
Real data contains two or more decimal points.
[Character-string]
Character causing the error, or none
[Code]
XX-> ASCII code of the character in error (bit string, decimal number with decimal point)
1-> An illegal character is contained in data other than bit strings or decimal numbers with decimal points
[Probable Fault Cause]
Data setting error
[Measures to Take]
• Set data correctly.
• Set correct numerical values.
5259 Decimal point
Eeoelale7184 A decimal point is specified in data that must be an integer, or the decimal point position is improper.
[Character-string]
None
[Code]
Specified decimal point position
[Probable Fault Cause]
Operation error
[Measures to Take]
Enter data correctly.
5260 Command execution impossible
Eeoelale7185 ADD or CAL command cannot be executed for the set data.
[Character-string]
None
[Code]
1-> An attempt was made to execute the ADD command.
2-> An attempt was made to execute the CAL command.
[Probable Fault Cause]
Operation error
[Measures to Take]
Use another command such as the SET command to set data.
5261 CAL command
Eeoelale7186 Incorrect operation in calculating data using the CAL function.
[Character-string]
None
[Code]
1-> The CAL command was executed during main program execution.
[Probable Fault Cause]
Operation error
[Measures to Take]
Wait until program execution is completed or the NC is reset, then calculate again.
5263 Data calculation
Eeoelale7187 An error occurred during numerical calculation of input data.
[Object]
None
[Character-string]
Character string containing an error
[Code]
Refer to the Operation Manual.
[Probable Fault Cause]
An incorrect formula was entered.
5264 Table data
Eeoelale7188 This alarm indicates an abnormality in NC integer data, which is not caused by normal NC operations.
[Character-string]
None
[Code]
None
[Probable Fault Cause]
Software error
5265 Stroke limit over
Eeoelale7189
An error occurred when setting user parameter variable limit data (work coordinate system, machine coordinate system) in the machine coordinate system. The set position exceeded the stroke end limit position.
When variable limit data is set in the work coordinate system, the set data is first converted to the limit value in the machine coordinate system; after conversion, the set position is outside the stroke end limit position.
[Character-string]
None
[Code]
Excess amount expressed in hexadecimal
[Probable Fault Cause]
Data setting error
[Measures to Take]
Check the stroke end limit value and change the variable limit data so that it is within the axis stroke range. In the above example, the variable limit position exceeds the stroke end limit by 3 mm.
5266 Page number setting
Eeoelale7190 When retrieving the required data number on the data check display screen, a negative value or a value with a decimal point was entered as the item number or page number.
[Character-string]
None
[Code]
None
[Probable Fault Cause]
Operation error
[Measures to Take]
Enter a correct number.
5267 Output command
An output command format error occurred, or the set value exceeds the symbol size.
[Character-string]
None
[Code]
1-> Specified symbol was not found.
2-> Set value is larger than the symbol size.
3-> Format is specified incorrectly. (The set value and symbol are not separated by a comma ”,”.)
4-> Format is specified incorrectly. (No symbol name was entered.)
[Probable Fault Cause]
Operation error
[Measures to Take]
Enter a correct output command.
5268 Time data
Eeoelale7192 Incorrect time data was specified.
[Character-string]
None
[Code]
1
[Probable Fault Cause]
Error in time data specification
[Measures to Take]
Specify time data correctly.
Specify hours:minutes:
6:12 (6 hours 12 minutes)
Specify hours:minutes:seconds
2:6:28 (2 hours 6 minutes 28 seconds)
[Related Specifications]
NC operation monitor, tool life management, etc.
5269 File name stack overflow
Eeoelale7193 When executing part program selection, the number of files specified in the index program selection exceeds 8.
This is checked when the main program is loaded.
[Character-string]
None
[Code]
1
[Probable Fault Cause]
Three or more subprograms of the index program are registered.
5270 Program executing
Eeoelale7194 During program execution, an attempt was made to switch between enlarged and standard modes of the graphic display.
[Character-string]
None
[Code]
1
[Probable Fault Cause]
Operation error
[Measures to Take]
Change the display mode after resetting the NC.
[Related Specifications]
Graphic
5271 Auto area setting executing
Eeoelale7195 An error occurred while reading the part program when the auto scale function was set on the graphic display standard screen.
[Character-string]
None
[Code]
1-> Not in auto mode; alarm occurred; independent A/B mode; program not found.
2-> NC reset button was pressed during auto area setting.
[Probable Fault Cause]
Operation error
[Measures to Take]
Execute auto area setting under conditions where setting is permitted.
[Related Specifications]
Graphic
5272 Scale factor too large
Eeoelale7196 An attempt was made to set a scale factor outside the graphic display range of 50 to 1/50.
[Character-string]
None
[Code]
XXXXXXXX-> The point corresponding to the scale setting in hexadecimal.
[Probable Fault Cause]
Operation error
[Measures to Take]
The scale setting range is as follows:
Standard page
1/50 – 2
Enlarged page
1/50 – 50
Set the scale within the range shown above.
[Related Specifications]
Graphic
5273 Pitch error compensation data file not found
Eeoelale7197 The pitch compensation data file was not found on the specified device, or the file size was different when the pitch error compensation data was backed up.
[Character-string]
None
[Code]
1-> Pitch error compensation data file not found
2-> Pitch error compensation data file size is different
[Probable Fault Cause]
Operation error
[Measures to Take]
Write the compensation data again after re-loading the pitch error compensation data file into memory.
5274 NC LOB memory load
Eeoelale7198 An error occurred when attempting to read and load an object file from memory during program operation.
[Character-string]
Read character string or none
[Code]
1-> Load file was not found.
2-> File attribute is not LOB1.
3-> Load address is incorrect.
[Probable Fault Cause]
• Although the specification code corresponding to paper tape was converted and the data input/output function was set, the corresponding software does not exist.
• C-MOS memory is damaged.
[Measures to Take]
• LCM->LOB, paper tape conversion
LCM ->LOB, paper tape input/output
• Re-install the control software.
• Replace the C-MOS memory.
5275 Restart command
Eeoelale7199 Restart command error for sequence restart operation in auto mode. (See codes below.)
[Character-string]
None
[Code]
1-> Command value is greater than 99999999.
2-> No sequence number or block counter is specified.
3-> Number of repetitions exceeds 9999.
4-> Character other than comma ”,” is specified after sequence number or block counter.
[Probable Fault Cause]
Operation error
[Measures to Take]
Enter data according to the specifications in the instruction manual.
5276 Tool data displaying
Eeoelale7200 An error occurred during tool layout processing.
[Character-string]
None
[Code]
1-> Not in auto mode; alarm state; independent A/B mode; main program and schedule program not selected.
2-> Error during tool layout processing, or control reset.
[Probable Fault Cause]
Mode setting error or program not selected.
[Measures to Take]
Tool layout processing is permitted in auto mode, after program selection, and not in independent A/B mode.
5277 Gauging data printing
[Character-string]
None
[Code]
1
[Remedy]
Do not print any part programs while measured data is being printed out.
5278 MS-DOS
Eeoelale7202 In the floppy disk input/output function (MS-DOS format), an error indicated by the following code occurred.
[Character-string]
Varies depending on the displayed code.
[Code]
1-> The designated command character (function) is not found.
2-> Command syntax error
3-> MS-DOS file format error.
The file name exceeds 8 characters or the file extension exceeds 3 characters.
An undefined code was used for pathname designation.
The pathname exceeds 47 characters.
4-> No device is designated, or designated in an incorrect format.
5-> The designated path is not found.
6-> The OSP file name is designated incorrectly.
The file name exceeds 16 characters or the file extension exceeds 3 characters.
An invalid character is used in the file name definition.
7-> The output file name for copy is not designated, or ”*” or ”? “ is used.
8-> An option code is set incorrectly.
9-> The file is not in MS-DOS format.
A-> The output file is a system file or a hidden file.
B-> An attempt was made to copy between OSP files or between MS-DOS files.
C-> The MS-DOS format file cannot be opened.
D-> The floppy disk has insufficient storage space.
E-> The file name contains an invalid character.
[Probable Fault Cause]
Designation error
[Remedy]
1-> Enter the command character using the function key.
2-> Correct the command.
3-> Enter the pathname and the MS-DOS file name correctly.
4-> Designate the device name.
5-> Enter the pathname correctly and check if the designated path (directory) exists.
6-> After copying, enter the OSP file name correctly.
7-> Enter the output file name correctly.
8-> Enter the applicable option code correctly.
9-> Use a floppy disk in MS-DOS format.
A-> Change the output device name used for copying.
B-> Change the device name used for copying.
C-> Since the MS-DOS format disk is defective, format it again.
D-> Prepare a new floppy disk or delete files.
E-> Do not use MS-DOS format files whose file names contain kana or kanji (Japanese or Chinese characters).
5279 System link mode
Eeoelale7203 In the automatic system operation mode, an attempt was made to perform program selection, program search (including cursor search), restart, schedule program selection, or schedule program search.
[Character-string]
None
[Code]
None
[Probable Fault Cause]
Operation error
[Remedy]
Select the independent operation mode.
5280 Y-axis control mode
Eeoelale7204 An illegal operation indicated by the following code was attempted in the Y-axis control mode.
[Character-string]
None
[Code]
None-> YS/X-axis angle data was set or calculated without selecting the Y-axis control mode.
5-> Automatic determination was performed in the graphic display area in the Y-axis control mode.
6-> Tool allocation was performed in the Y-axis control mode.
5281 Spindle control parameter
Eeoelale7205 An error occurred when rewriting the spindle control parameter or the M-tool spindle axis parameter.
[Character-string]
None
[Code]
None
[Probable Fault Cause]
• The spindle or M-tool spindle stop command was not issued during main program execution.
• The manual feed mode was selected.
• Sequence reset during machining.
• Emergency stop is active.
• The C-axis rotation command was designated.
5283 Check screen command
Eeoelale7206 To display the variable contents on the first page of check data, the address of that variable must be set.
An error occurred when setting the address.
[Character-string]
None
[Code]
1-> The check number is a number other than 1 to 9.
2-> The address number and the address are separated by a comma.
3-> The address to be checked exceeds the maximum address.
4-> For non-bit data, the address is an odd number.
5-> The designated address exceeds its valid range.
[Probable Fault Cause]
Operation error
[Remedy]
Check the data referring to the displayed alarm code, and set the data correctly again.
5284 Category code mismatch
Eeoelale7207 When selecting a tool category code for the ATC second position, its category code is different from the code designated for the first position.
[Character-string]
None
[Code]
None
[Probable Fault Cause]
Operation error
[Remedy]
Set the category code so that there is no inconsistency between the first position and the second position.
5285 No X-axis data
Eeoelale7208 In the sub-spindle mode, X-axis machine origin offset was performed. Or, in the spindle-off mode, an attempt was made to perform X-axis machine origin offset on the A-side.
[Character-string]
None
[Code]
None
5286 No Z-axis data
Eeoelale7209 In the spindle-off mode, an attempt was made to perform Z-axis machine origin offset on the A-side.
[Character-string]
None
[Code]
None
5287 No Y-axis data Eeoelale7210
Eeoelale7211 An attempt was made to set or calculate Y-axis overload monitor data on the B-side.
[Character-string]
None
[Code]
None
5288 No CT-axis data
Eeoelale7211 An attempt was made to set CT-axis data where no CT-axis data exists.
[Character-string]
None
[Code]
None
5289 No B-side data
Eeoelale7212 An attempt was made to set, add, or calculate data that does not exist on the turret B-side.
[Character-string]
None
[Code]
None
5290 No C-axis data
Eeoelale7213 In the zero point setting mode, tool data setting mode, and parameter setting mode, an attempt was made on the data setting screen to set the category for data that does not require C-axis data setting.
[Character-string]
None
[Code]
None
[Probable Fault Cause]
Operation error
[Remedy]
Do not set the category code for data that does not require C-axis data setting.
[Related Specifications]
Multitasking machine
5291 No M-axis data
Eeoelale7214 An attempt was made to set the load monitor data for the M-axis on the turret B-side.
[Character-string]
None
[Code]
None
[Probable Fault Cause]
Operation error
5292 No W-axis data
Eeoelale7215 In the zero point setting mode, tool data setting mode, and parameter setting mode, an attempt was made on the data setting screen to set the category for data that does not require W-axis data setting.
[Character-string]
None
[Code]
None
[Probable Fault Cause]
Operation error
[Remedy]
Do not set the category code for data that does not require W-axis data setting.
[Related Specifications]
Tow-along tailstock
5293 Tool type command
Eeoelale7216 An attempt was made to execute the tool type command on a page other than the tool shape selection page.
[Character-string]
None
[Code]
None
[Probable Fault Cause]
Operation error
[Remedy]
Execute the tool type command after displaying the tool shape selection screen.
[Related Specifications]
Graphic display
5294 Initialization command
Eeoelale7217 An attempt was made to execute the initialization command even though the tool life management *** TOOL INFO TABLE *** is not displayed.
[Character-string]
None
[Code]
3
[Probable Fault Cause]
Operation error
[Remedy]
Designate the initialization command on the tool life management *** TOOL INFO TABLE *** screen.
[Related Specifications]
Tool life management
5295 Tool registration
Eeoelale7218 A tool number not registered in the tool group was designated.
[Character-string]
None
[Code]
Hexadecimal value of designated tool number
[Probable Fault Cause]
Operation error
[Remedy]
Designate a tool number already registered in the tool group, or register the tool number to be designated in the tool group.
[Related Specifications]
Tool life management
5296 No Inductosyn data
Eeoelale7219 On the Inductosyn joint compensation data setting screen, an attempt was made to set joint compensation data for an impossible axis (an axis not using Inductosyn).
[Character-string]
None
[Code]
None
[Remedy]
Set the data only for the axis using Inductosyn.
5297 Gauging calculation command
Eeoelale7220 The calculation command for the gauging process is incorrect.
[Character-string]
None
[Code]
None-> The tool offset page is not selected.
2-> The cursor is not at the tool offset position.
4-> The designated sensor contact surface number is other than 1 or 2.
[Probable Fault Cause]
Operation error
[Remedy]
Display the tool offset page, position the cursor at the required tool offset position, and then enter the command correctly.
[Related Specifications]
Tool gauging
5298 Monitor time setting
Eeoelale7221 The set value exceeds the setting range, or a different format was used.
[Character-string]
Set data
[Code]
None-> An attempt was made to set data outside the setting range.
Others-> Incorrect format
[Probable Fault Cause]
Operation error
[Remedy]
Check that the format is correct or check the setting range, then set the data again.
5299 Monitor in execution
Eeoelale7222 The monitor time was set during actual program execution.
[Probable Fault Cause]
Operation error
[Remedy]
Set the monitor time while the program is not being executed.
5300 ATC magazine tool registration
Eeoelale7223 Invalid tool data was set on the *ATC MAGAZINE INFORMATION* or *ATC TOOL INFORMATION* setting screen in tool data setting mode.
[Code]
1-> Tool data was set in a magazine pot defined as an empty pot.
2-> Tool data was set in an occupied pot.
3-> Tool data was set although the designated tool type cannot be mounted on the turret.
4-> With the TOOL-ID specification, a tool with tool type LL is set on a turret other than the rotary tool mounting turret.
[Remedy]
Determine the cause of the error from the code above, and register the tool data again.
[Probable Fault Cause]
ATC Instruction Manual
5301 ATC tool number input format
Eeoelale7224 Invalid tool data was entered on the *ATC MAGAZINE INFORMATION* or *ATC TOOL INFORMATION* setting screen in tool data setting mode.
[Code]
1-> The tool number was designated with a negative number.
2-> The tool number was designated with a decimal number.
3-> Tool data was not delimited correctly with commas.
4-> The tool type code is not L, M, DT, S, or ML.
5-> The tool diameter code is not B, BR, or E.
[Remedy]
Determine the cause of the error from the error code, and enter the tool data correctly again.
[Probable Fault Cause]
ATC Instruction Manual
5302 ATC tool number duplicate setting
Eeoelale7225 The same tool number was used for more than one tool on the *ATC MAGAZINE INFORMATION* or *ATC TOOL INFORMATION* setting screen in tool data setting mode.
[Code]
1-> The same tool number was set for a tool already mounted at the prep station, turret, magazine, sub arm, or change arm.
[Probable Fault Cause]
ATC magazine information, ATC tool information
5303 ATC sequence number cannot be forced
Eeoelale7226 An attempt was made to set a sequence number that is not in the ATC sequence flow.
[Character-string]
None
[Code]
None
5305 File format
Eeoelale7227 Format error in verify command or paper tape data read using input command in data input/output function.
[Character-string]
1-> Record (block) in file
2-> File name does not begin with an alphabetical character, or data uses too many digits.
3-> No data identifier (Tn, On, or Pn) at the beginning of data.
4-> No data number (Nn) before or after the record data identifier.
5-> Paper tape data contains invalid data.
6-> Turret designation is not allowed in 2-spindle mode.
7-> Data identifier (Tn, On, or Pn) is incorrect.
8-> Data number (Nn) is incorrect.
[Remedy]
Correct the erroneous record data.
5306 Data designation
Eeoelale7228 An incorrect data identifier was defined when designating data to be output using the data input/output function.
[Character-string]
Defined data identifier
[Code]
1-> Incorrect command format
2-> Data identifier is not T, O, or P.
3-> The designated data identifier number is not contained in the data to be output.
5307 Input data overflow
Eeoelale7229 Too large or too small data was input to the NC unit using the data input/output function.
[Character-string]
Erroneous record
[Probable Fault Cause]
• Data output punch error
• Output data setting error
[Remedy]
• Correct the erroneous output data and punch again.
• Then, have the NC read the paper tape.
5308 Stroke limit over
Eeoelale7230 Variable limit data input using the data input/output function exceeded the stroke limit.
5309 Time data
Eeoelale7231 Erroneous time data was input using the data input/output function.
[Code]
1-> [hours:minutes] data error.
2-> [hours:minutes:seconds] data error.
[Probable Fault Cause]
Tape error or tape reader error
[Remedy]
Check the paper tape. If the tape is faulty, check the punching and punch the tape again.
If not, check the tape reader and read the paper tape into the NC again.
5312 Output data overflow
Eeoelale7232 Data output using the data input/output function was too large.
[Probable Fault Cause]
Data setting error
[Remedy]
Set the data again.
5313 Output data underflow
Eeoelale7233 Data output using the data input/output function was too small.
[Probable Fault Cause]
Data setting error
[Remedy]
Set the data again.
5314 Schedule program select impossible
Eeoelale7234 A schedule program was selected and started in linked operation mode.
5315 In receive control mode
Eeoelale7235 A sequence search or restart command was issued in receive control mode. Or, sequence search was attempted during remote buffer operation. Schedule program select or schedule program search was executed without specifying an operation file name.
5316 Setting impossible during turret indexing
Eeoelale7236 Turret control parameters were changed during turret indexing.
[Remedy]
Change turret control parameters after turret indexing is completed.
5317 Remote buffer operation mode
Eeoelale7237 The sequence search function was activated during remote buffer operation.
Schedule program select or schedule program search was executed without specifying an operation file name.
5318 ATC tool information
Eeoelale7238
5319 No YS-axis data
Eeoelale7239 Illegal YI-axis data was designated.
[Code]
None-> Load monitor data has been set for YI-axis B-side.
1-> Backlash, encoder offset, encoder connection compensation, or in-position data has been set.
[Probable Fault Cause]
Operation error
5320 Transfer file name designation
Eeoelale7240 Transfer file name was designated incorrectly.
[Character-string]
Designated file name
[Code]
1-> An output file name was designated.
2-> Punching failed because the designated file name was not found.
3-> No file was sent although a file name was designated for read operation.
5321 Library capacity overflow
Eeoelale7241 The designated library program buffer capacity exceeds the program capacity of the machine specifications.
5322 Library stack overflow
Eeoelale7242 The number of subprograms registered in the library program exceeds 65.
5323 No subprogram file
Eeoelale7243 The specified subprogram file to be registered was not found in the library program.
[Character-string]
File name not found
5324 Registered program
Eeoelale7244 An already existing subprogram name was registered as a library program.
5325 MSB automatically registered at power-on
Eeoelale7245 The subprogram name registered in the library program is identical to a subprogram name in the MSB file.
5326 Part name input
Eeoelale7246 An alarm occurred when setting or checking the part name.
[Code]
1-> An existing part name was set by a machining parameter.
2-> No part name was set in the part table where the cursor is positioned.
3-> The part name set by the machining parameter was not found in the part table where the cursor is positioned.
4-> The part name to be set does not exist.
[Probable Fault Cause]
No part name is set in the part table indicated by the cursor. Or, the part name set by the machining parameter does not match that in the part table.
[Remedy]
• Set the part name in the part table.
• Match the part name set by the machining parameter with that in the part table.
5327 Continuous machining schedule program
Eeoelale7247 The NC received a program name that cannot be converted into the part program to be machined by the PSELECT command from the schedule program.
[Code]
1-> The part program name designated by the PSELECT command from the schedule program is not WT1.MIN through WT20.MIN.
2-> Although the schedule program issued a PSELECT command, the part name designated in the part table is not set, or the set part name does not exist in the part program.
[Probable Fault Cause]
• Error in the schedule program.
• No part name is set in the designated part table.
• The part name in the part table does not match the part name set by the machining parameter.
[Remedy]
• Correct the part program.
• Match the part name in the part table with the part name set by the machining parameter.
5328 Continuous machining part table copy
Eeoelale7248 An invalid operation was attempted using the line copy/insert function.
1-> Line insert was executed although the buffer was empty.
2-> Parameters were changed after line copy and before line insert.
3-> Line copy or insert was executed without positioning the cursor on the part table.
4-> An invalid number was entered for the line number defining the line to be copied.
[Probable Fault Cause]
Operation error during line copy or insert
[Remedy]
• Insert lines without changing parameters after line copy.
• Position the cursor on the part table before line copy or insert.
• Define the line number to be copied within the range of 0 to 19.
5329 MCS timeout
Eeoelale7249 When an MDR command was entered, the corresponding axis or corresponding channel communicated using MCS, and the communication was not completed within 10 seconds.
5330 Program select illegal mode
Eeoelale7250 An attempt was made to select a program in a mode other than independent automatic mode.
[Code]
0 -> An attempt was made to select a program in a mode other than independent automatic mode.
1 -> For the program select special specification, program selection was performed using a function key.
5337 Common variable name setting error
Eeoelale7612 Concerning common variable name setting, an error occurred in variable name setting, or the variable name is incorrect. Or, the variable name was not found during variable name search.
[Code]
1-> The set variable name has more than 5 characters.
2-> The set variable name already exists, or the same variable name was set.
3-> The variable name is identical to a system variable name.
4-> Variable name consisting of numbers only is set.
5-> Variable name is not registered.
5338 TCP/IP protocol illegal
Error occurred during initial TCP/IP protocol execution at power on.
[Object]
None
[Character-string]
None
[Code]
XX
XX=22-> Parameter error
=06-> TCP/IP protocol initial timeout
=08-> DNC-T specification OFF (for specified NC)
=11-> DNC-T specification fragment OFF (in parameter file)
=02-> Parameter file open error
=09-> Parameter file read error
=13-> Parameter file close error
[Probable Fault Cause]
Hardware failure or API software
[Measures to Take]
Check hardware or software.
5339 DNC-RT path name
Erroneous file name was specified in program select by DNC-RT.
[Object]
None
[Character-string]
None
[Code]
X
X=1-> File name error
=2-> Extension error
=3-> Combination of device name, path name, and file name exceeds 120 characters.
[Probable Fault Cause]
Command line
[Measures to Take]
Check the command line.
5340 DNC-RT program select
[Object]
None
[Character-string]
None
[Code]
800000XX: Communication error number
YY: Application error number
XX=6F-> Insufficient buffer in TCP/IP driver
72-> TCP/IP description error
73-> TCP/IP parameter error
74-> No free board in shared memory
75-> Unconnected status
7B-> Ignore error
7D-> ftp_ms_open error and termination
7E-> ftp_ms_close
7F-> ftp_ms_type
80-> ftp_ms_user
81-> ftp_ms_pass
82-> ftp_ms_acct
83-> ftp_ms_dele
84-> ftp_ms_fopen
85-> ftp_ms_fopen_uni
86-> ftp_ms_net_drecv_f
87-> ftp_ms_net_dsend_f
88-> ftp_ms_fclose
89-> ftp_ms_error
8A-> ftp_ms_chdir
8B-> ftp_ms_mkdir
8C-> ftp_ms_rmdir
8D-> ftp_ms_pwd
8E-> ftp_ms_cdup
8F-> ftp_ms_dopen
90-> ftp_ms_dread
91-> ftp_ms_dclose
97-> IP address error
98-> No IP address
99-> Timeout abort
9A-> Remote host connection broken
9B-> Initialization of TCP/IP board OS (MORE) terminated abnormally
9C-> Initialization of packet driver of TCP/IP board or TCP/IP module terminated abnormally
9D-> Initialization of TCP/IP board TELNET client module terminated abnormally
9E-> Initialization of TCP/IP board TELNET server module terminated abnormally
9F-> Initialization of TCP/IP board FTP module terminated abnormally
A0-> Initialization of TCP/IP board socket interface module terminated abnormally
A1-> Initialization of TCP/IP board terminated abnormally
YY=13-> Illegal channel number
16-> Invalid parameter for initialization
Not started, or invalid program name
11-> Already started
06-> TCP/IP board initialization timeout
(TCP/IP board not running)
Cannot rename device, cannot unprotect device, cannot apply device, unknown (unsupported) command
0D-> Communication board not mounted
02-> Program not found
08-> Execution error
[Probable Fault Cause]
Application error, file name
[Measures to Take]
Check communication hardware, software, or program select format.
5341 Thermal deformation compensation in progress
Eeoelale7610 Thermal deformation parameter was set although the thermal deformation compensation function is already active.
[Probable Fault Cause]
1-> Operation error
[Measures to Take]
Set the thermal deformation parameter after setting compensation execution SW to “NO”.
5342 Setting condition
YES is not set on the selected sensor.
Or NO is set as the 1st temperature channel on the selected sensor channel.
[Probable Fault Cause]
1-> Operation error
[Measures to Take]
1) Select a sensor number for which YES is set.
Or set YES on the sensor channel to be selected.
2) Change the channel of the selected sensor to the 1st temperature channel.
5344 Data expansion impossible
Cam profile expansion was executed while executing the main program.
[Character-string]
None
[Code]
1
[Probable Fault Cause]
Operator error
[Measures to Take]
Reset the NC before executing cam profile expansion.
5345 Cam execution data file load
Designated machine file was not found when loading file.
[Character-string]
None
[Code]
1
[Probable Fault Cause]
Operator error
[Measures to Take]
Check if the cam execution data file exists when displaying directory.
5346 No cam execution data
Cam execution data does not exist in RAM when saving file.
[Character-string]
None
[Code]
1-> Cam execution data to be saved does not exist in RAM.
2-> File name of file to be saved is not specified.
3-> File extension of file to be saved is not specified.
4-> File extension of file to be saved is COF.
[Probable Fault Cause]
Operator error
5347 No cam definition data file
Specified cam definition data file (LSF file) does not exist in MD1 when expanding cam profile.
[Character-string]
None
[Code]
1
[Probable Fault Cause]
Operator error
[Measures to Take]
Check if the cam definition data file exists when displaying directory.
5348 Cam definition data file format
Format error in cam definition data file (LSF file).
[Character-string]
None
[Code]
1-> No data in cam definition data file (LSF file).
2-> No ’XCAM’ at the beginning of file.
[Probable Fault Cause]
Error occurred when creating cam definition data file (LSF file).
[Measures to Take]
Correct cam definition data file (LSF file).
5349 Cam execution data format
[Character-string]
None
[Code]
1-> ’CAM1’ is not written in area 0.
2-> ’@8C’ in area 0 is not ’$0000’.
4-> Cam execution data file (command data) is incomplete.
5-> Cam execution data file (command data) is too large.
6-> Cam execution data file (command data) is too small.
7-> Cam execution data file (compensation data) is incomplete.
8-> Cam execution data file (compensation data) is too large.
9-> Cam execution data file (compensation data) is too small.
C-> Extension of synchronized mode A file is not ’EXF’.
[Probable Fault Cause]
Error occurred when creating cam execution data file.
[Measures to Take]
Create cam execution data file again.
5350 Synchronized mode execution impossible
Any of correction mode, profile expansion mode, or file load mode is set to ON in synchronized mode.
[Character-string]
None
[Code]
1-> This correction mode is set to ON in synchronized mode.
2-> This profile expansion mode is set to ON in synchronized mode.
3-> This file load mode is set to ON in synchronized mode.
[Probable Fault Cause]
Operator error
[Measures to Take]
Set any of these modes to ON after completing synchronized mode.
5351 No cam execution data file name
There is no file name for the cam execution data file (EXF file) under FCALL in the program.
[Character-string]
None
[Code]
1
[Probable Fault Cause]
Program error
[Measures to Take]
Write a file name for the cam execution data file (EXF file) under the FCALL command in the program.
5352 Too many cam execution data files
More than 16 types of cam execution data files (EXF files) are specified with the FCALL command in the program.
[Character-string]
None
[Code]
1
[Probable Fault Cause]
Program error
[Measures to Take]
Review the program.
Reduce the number of files under the FCALL command in the program to 16 or fewer.
5353 Too many FCALL commands
Cam execution data file (EXF file) is called 129 or more times with the FCALL command in the program.
[Character-string]
None
[Code]
1
[Probable Fault Cause]
Program error
[Measures to Take]
Review the program.
Reduce the number of files under the FCALL command in the program to 128 or fewer.
5354 No cam execution data file
Cam execution data file (EXF file) specified by the FCALL command was not found in MD1 when selecting the program.
[Character-string]
None
[Code]
None
[Probable Fault Cause]
Program error
Review the program.
Check the initial storage in MD1.
5355 Cam execution data parameter mismatch
The parameter in the cam execution data file does not match the machine parameter.
[Character-string]
None
[Code]
1-> Spindle PG pulse count mismatch.
2-> Spindle PG resolution mismatch.
3-> XS-axis resolution mismatch.
[Probable Fault Cause]
Operator error
[Measures to Take]
Check each machine parameter.
5356 Cutting parameter table
There is an illegal command in the cutting parameter table.
[Code]
1-> The UCMS or UCME command was executed alone.
2-> A command other than VCMT was executed between UCMS and UCME.
3-> Illegal VCMT command format.
5357 Spindle APA not determined
The spindle dynamic position (value: CD) is not determined.
[Measures to Take]
Determine the spindle dynamic position.
5358 Chuck coordinate system mismatch
The chuck barrier data (CX/CZ) not divided on the machining ST side will be calculated.
5368 Sensor channel auto-setting
An attempt was made to change the sensor channel setting even though the sensor selection parameter "AUTO SELECT" was already set to "YES".
[Probable Fault Cause]
1-> Operation error
[Remedy]
Set the sensor selection parameter "AUTO SELECT" to "ON" before attempting to change the sensor channel setting.
5371 No B-axis data
Setting or calculation of the B-axis overload monitor data was performed on the B side.
[Character-string]
None
[Code]
None
5373 Initial program load
An error occurred while reading the initial 16 sectors of the program selected for B, S, or M method operation.
[Character-string]
None
[Code]
XXXXYYYY
XXXX-> Physical sector number where error occurred.
YYYY-> Error number (number in error table)
[Measures to Take]
Follow the instructions in the error table.
5374 DNC-DT path name
Program selection via DNC-DT failed due to an incorrect file name.
Total characters of device name, path name, and file name exceed 120.
[Object]
None
[Character-string]
None
[Code]
1: Incorrect file name
2: Incorrect file name extension
3: Exceeds 120 characters
[Probable Fault Cause]
Command line
[Measures to Take]
Check the command line.
5375 DNC-DT program select
An alarm occurred when selecting a program via DNC-DT.
[Object]
None
[Character-string]
None
[Code]
XX: Application error number
8000000YY: Communication error number
XX=6F: Insufficient buffer capacity in TCP/IP driver
XX=72: Descriptor sent to TCP/IP driver is incorrect
XX=73: Parameter sent to TCP/IP driver is incorrect
XX=74: No free port in shared memory
XX=75: Not connected
XX=7B: Abort command ignored
XX=7D: "ftp_ms_open" terminated abnormally
XX=7E: "ftp_ms_close" terminated abnormally
XX=7F: "ftp_ms_type" terminated abnormally
XX=80: "ftp_ms_user" terminated abnormally
XX=81: "ftp_ms_pass" terminated abnormally
XX=82: "ftp_ms_acct" terminated abnormally
XX=83: "ftp_ms_delete" terminated abnormally
XX=84: "ftp_ms_fopen" terminated abnormally
XX=85: "ftp_ms_fopen_uni" terminated abnormally
XX=86: "ftp_ms_net_drecv_f" terminated abnormally
XX=87: "ftp_ms_net_dsend_f" terminated abnormally
XX=88: "ftp_ms_fclose" terminated abnormally
XX=89: "ftp_ms_abort" terminated abnormally
XX=8A: "ftp_ms_chdir" terminated abnormally
XX=8B: "ftp_ms_mkdir" terminated abnormally
XX=8C: "ftp_ms_rmdir" terminated abnormally
XX=8D: "ftp_ms_pwd" terminated abnormally
XX=8E: "ftp_ms_cdup" terminated abnormally
XX=8F: "ftp_ms_dopen" terminated abnormally
XX=90: "ftp_ms_dread" terminated abnormally
XX=91: "ftp_ms_dclose" terminated abnormally
XX=97: IP address error
XX=98: No IP address
XX=99: Interruption timeout
XX=9A: Disconnection command from remote host
XX=9B: OS (MORE) initialization of TCP/IP board terminated abnormally
XX=9C: Initialization of packet driver or TCP/IP module on TCP/IP board terminated abnormally
XX=9D: Initialization of TELNET client module on TCP/IP board terminated abnormally
XX=9E: Initialization of TELNET server module on TCP/IP board terminated abnormally
XX=9F: Initialization of FTP module on TCP/IP board terminated abnormally
XX=A0: Initialization of packet line interface module on TCP/IP board terminated abnormally
XX=A1: Initialization of TCP/IP board terminated abnormally
YY=13: Incorrect channel number
YY=16: Parameter error initialization; program not started; incorrect program name
YY=11: Program already started
YY=06: TCP/IP board initialization timeout (TCP/IP board cannot operate); device cannot be renamed; device cannot be unprotected; device cannot acquire file system information;
unknown command (not supported)
YY=0D: Communication board not installed
YY=02: Program not found
YY=08: Execution failed
YY=17: Option L was specified, but a file with the same name exists in MD1; and the file is protected, so it cannot be deleted.
YY=18: Failed to open file when creating file in MD1: by specifying option L.
YY=19: Failed to close file when creating file in MD1: by specifying option L.
YY=20: Failed to move file when creating file in MD1: by specifying option L.
YY=21: Failed to delete file when creating file in MD1: by specifying option L.
[Probable Fault Cause]
Application error, incorrect file name
[Measures to Take]
Correct the communication hardware, software, or program selection method.
5376 DNC-DT preload error
Buffer processing error in DNC-DT.
[Object]
None
[Character-string]
None
[Code]
100-> Hardware error (hard disk, etc.)
XXYYZZ
YYZZ
XX=
6F-> Insufficient buffer capacity in TCP/IP driver
72-> Abnormal descriptor sent to TCP/IP driver
73-> Abnormal parameter sent to TCP/IP driver
74-> No free port in shared memory
75-> Not connected
7B-> Abort ignored
7D-> ftp_ms_open abnormal end
7E-> ftp_ms_close abnormal end
7F-> ftp_ms_type abnormal end
80-> ftp_ms_user abnormal end
81-> ftp_ms_pass abnormal end
82-> ftp_ms_acct abnormal end
83-> ftp_ms_delete abnormal end
84-> ftp_ms_fopen abnormal end
85-> ftp_ms_fopen_uni abnormal end
86-> ftp_ms_net_drecv_f abnormal end
87-> ftp_ms_net_dsend_f abnormal end
88-> ftp_ms_fclose abnormal end
89-> ftp_ms_abort abnormal end
8A-> ftp_ms_chdir abnormal end
8D-> ftp_ms_pwd abnormal end
8F-> ftp_ms_dopen abnormal end
90-> ftp_ms_dread abnormal end
91-> ftp_ms_dclose abnormal end
97-> IP address error
98-> No IP address
99-> Interrupted due to timeout
9A-> Connection command from remote host
9B-> OS (MORE) initialization of TCP/IP board abnormal end
9C-> Initialization of packet driver or TCP/IP module on TCP/IP board abnormal end
9F-> Initialization of FTP client module on TCP/IP board abnormal end
A0-> Initialization of packet line interface module on TCP/IP board abnormal end
A1-> TCP/IP board initialization abnormal end
YY=
10-> Buffering task started
20-> Buffering process initialization
30-> Buffering request
40-> Obtain the number of completed buffer operations
50-> Acquire buffer file
60-> Obtain the remaining count in buffer file table
70-> Buffering stop
80-> Unlock buffer file
90-> Buffering request
A0-> Unlock buffer file
B0-> File transfer error
ZZ=
FF-> Communication error
02-> File not found
03-> Buffering task not started
05-> No transfer completed file
Previous buffer processing not completed
0D-> Write-protected file
0E-> Buffer task start execution parameter error
11-> File already exists, buffer task already started
13-> File device naming error
16-> Illegal initialization parameter
Not started
Illegal program name
5900 Axis designation
[Probable Fault Cause] Eeoelale7251
An additional parameter or point data number selection cannot be set.
5901 No inch specification
[Probable Fault Cause] Eeoelale7252
This specification is not selected.
5902 Data range overflow
Eeoelale7253 When setting parameters, registration, or point data, setting range overflow occurred
[Probable Fault Cause]
Operation error
5903 Playback impossible
Eeoelale7254 A playback write operation was attempted on a parameter for which playback write is not allowed.
[Probable Fault Cause]
The file is corrupted.
5904 File operation
Eeoelale7255 File operation failed.
[Probable Fault Cause]
The file is corrupted.
5905 Input data
Eeoelale7256 Input data is incorrect.
[Probable Fault Cause]
Operation error
5906 Setting impossible
Eeoelale7257 Setting operating parameters or registration is impossible.
[Probable Fault Cause]
Operation error
5907 Check address
[Probable Fault Cause] Eeoelale7258
Operation error
5908 Number of decimal points
Eeoelale7259 More than one decimal point was entered.
[Probable Fault Cause]
Operation error
5909 Decimal point position
Eeoelale7260 The number of digits to the right of the decimal point is incorrect.
[Probable Fault Cause]
Operation error
5910 No decimal point specification
Eeoelale7261 A decimal point was entered even though the decimal point specification is not selected.
[Probable Fault Cause]
Operation error
5911 Decimal point setting impossible
Eeoelale7262 A decimal point was entered for a parameter that cannot use a decimal point.
[Probable Fault Cause]
Operation error
5912 Check address
Eeoelale7263 In order to display the variable contents on the check display page, the address of that variable must be set.
An error occurred during setting.
[Character-string]
None
[Code]
1-> The check number is a number other than 1 to 9.
2-> The address number and address are separated by a comma.
3-> The address to be checked exceeds the maximum address.
4-> The address is an odd number for non-bit data.
5-> Address designation exceeds its valid range.
[Probable Fault Cause]
Operation error
[Measures to Take]
Check the data referring to the displayed alarm code, and set the data again.
5913 MCS time out
Eeoelale7264 When the MDR command was input, the corresponding axis or channel communicated via MCS, and communication was not completed within 10 seconds.
8101 Command syntax
Eeoelale7561 Abnormal command
DATA API: Input data does not match the designated numerical format.
CMD API: An inappropriate file name was designated when selecting a ladder file.
An abnormal selection code was designated when searching for a ladder identifier.
[Measures to Take]
Contact your local service center.
8102 Option
Eeoelale7562 Selection code error. The associated command does not contain the designated selection code.
[Measures to Take]
Designate a permissible selection code.
8103 Input data overflow (PLC)
Eeoelale7563 Input data exceeds the permissible data input range.
[Measures to Take]
Set the data within the permissible input range.
8104 Invalid identifier
Eeoelale7564 An illegal identifier name was designated. Or, an unused label was designated.
[Measures to Take]
Designate a correct identifier name or an available label.
8105 Illegal label
Eeoelale7565 An incorrect label character string was designated. (Before being searched, the designated label cannot be treated as a label.)
[Measures to Take]
Designate a correct label character string.
8106 File data
Eeoelale7566 File data is abnormal and cannot be read.
[Character-string]
Target file name
[Code]
101: File read error
[Measures to Take]
Contact your local service center.
8107 File open
Eeoelale7567 The file cannot be opened due to a failure such as a file open error or the designated file does not exist.
[Character-string]
Target file name
[Code]
2002: No file
[Measures to Take]
Contact your local service center.
8108 File write
Eeoelale7568 File write error
[Character-string]
Target file name
[Code]
101: File write error
[Measures to Take]
Contact your local service center.
8109 PLC data version mismatch
Eeoelale7569 File versions of PAPB*.CNS, PSPC*.CNS, and PSPD*.CNS do not match.
[Measures to Take]
Contact your local service center.
8110 Identifier data overflow
Eeoelale7570 Too many identifiers for the PLC monitor to process.
[Code]
1: Identifier information 1 contains too many data blocks.
2: Identifier information 2 contains too many data blocks.
[Measures to Take]
Contact your local service center.
8111 PLC data format
Eeoelale7571 File formats of PSPB*.CNS, PSPC*.CNS, and PSPD*.CNS do not match.
[Measures to Take]
Contact your local service center.
8140 Program module not found
Eeoelale7572 Ladder monitor or program call designated a program name (PGO), but such a program does not exist.
[Measures to Take]
Designate a correct program name (PGO).
8141 Function module not found
Eeoelale7573 Ladder monitor or program call designated a function module name (FMO), but such a program does not exist.
[Measures to Take]
Designate a correct function module name (FMO).
8142 Invalid program module number
Eeoelale7574 Ladder monitor or program call designated a program number (PGO), but such a program number does not exist.
[Measures to Take]
Designate a correct program number (PGO).
8143 Invalid function module number
Eeoelale7575 Ladder monitor or program call designated a function module number (FMO), but such a function module number does not exist.
[Measures to Take]
Designate a correct function module number (FMO).
8153 Input data out of range
Eeoelale7576 The designated input data exceeds the permissible setting range.
[Measures to Take]
Designate input data within the setting range.
9000 Not time data ”H:M”
Eeoelale7265 Enter the time in hours:minutes format.
For example, to set 1 hour 59 minutes, enter 1:59.
[Measures to Take]
Set the time in the correct format.
For example, to set 1 hour 59 minutes, enter 1:59.
9001 Character string other than sequence name entered
Eeoelale7266 A character string other than a sequence name (or sequence number) was entered in an operation such as sequence number search or restart.
[Measures to Take]
Enter a character string for a sequence name or sequence number.
9002 Not time data ”H:M:S”
Eeoelale7267 Enter the time in hours:minutes:seconds format.
For example, to set 1 hour 59 minutes 30 seconds, enter 1:59:30.
[Measures to Take]
Set the time in the correct format.
For example, to set 1 hour 59 minutes 30 seconds, enter 1:59:30.
9003 Characters other than numerical values, signs, and four arithmetic operations using () cannot be entered
Eeoelale7268 A simple calculation formula can be used to set, add, or calculate this parameter value.
Characters that can be used in this formula are parentheses (up to 5 nesting levels), +, -, /, * (four arithmetic operations), +/- (sign), and real numbers. However, the entered formula
contains other characters or variables.
[Measures to Take]
Enter the formula using only parentheses (up to 5 nesting levels), +, -, /, * (four arithmetic operations), +/- (sign), and real numbers.
9004 Illegal character string
Eeoelale7269
9005 Cannot divide by 0
Eeoelale7270 A simple calculation formula can be used to set, add, or calculate this parameter value.
Characters that can be used in this formula are parentheses (up to 5 nesting levels), +, -, /, * (four arithmetic operations), +/- (sign), and real numbers. However, the entered formula
contains division by zero.
[Measures to Take]
Enter a correct calculation formula.
9006 Max. 5 nesting levels for ()
Eeoelale7271 A simple calculation formula can be used to set, add, or calculate this parameter value.
Characters that can be used in this formula are parentheses (up to 5 nesting levels), +, -, /, * (four arithmetic operations), +/- (sign), and real numbers. However, the entered formula
contains parentheses with 6 or more nesting levels.
[Measures to Take]
Ensure that the nesting level of parentheses in the formula is 5 or less.
9007 Missing ‘)’
[Measures to Take] Eeoelale7272
A simple calculation formula can be used to set, add, or calculate this parameter value.
Characters that can be used in this formula are parentheses (up to 5 nesting levels), +, -, /, * (four arithmetic operations), +/- (sign), and real numbers. However, the entered
[Action]
Put a right parenthesis in the formula.
9008 Too many ‘)’
Eeoelale7273 A simple calculation formula can be used to set, add, or calculate this parameter value.
The characters that can be used in this formula are parentheses (up to 5 levels of nesting), +, -, /, * (four basic arithmetic operations), +/- (sign), and real numbers. However, the entered formula
contains an extra right parenthesis.
[Action]
Delete the extra right parenthesis from the formula.
9009 Cannot calculate during operation
Eeoelale7274 The calculation function cannot be used to change the parameter you are attempting to calculate while the program is running.
[Action]
Wait until the program ends or reset the NC before calculating.
9010 Cannot edit without selecting main program
Eeoelale7275 An attempt was made to edit a program by pressing [F6] (EDIT) without selecting a main program from the main program window displayed in automatic operation mode.
Program editing cannot be performed by pressing [F6] (PROGRAM EDIT) when no main program is selected.
[Action]
Select a main program, and then edit the program by pressing [F6] (EDIT).
9011 Cannot edit without selecting schedule program
Eeoelale7276 An attempt was made to edit a schedule program by pressing [F6] (EDIT) without selecting a schedule program from the schedule program window displayed in automatic operation mode.
Program editing cannot be performed by pressing [F6] (PROGRAM EDIT) when no schedule program is selected.
[Action]
Select a schedule program, and then edit the schedule program by pressing [F6] (EDIT).
9012 Character string not found
Eeoelale7277 The [F6] (FIND) function called by pressing [F9] (FIND/REPLACE) in file edit mode cannot find the specified character string.
Alternatively, the [F7] (REPLACE) function called by pressing [F9] (FIND/REPLACE) in file edit mode cannot find the specified
character string in the range from the cursor position to the end of the file.
9013 Cannot use ’?’ in replacement string
Eeoelale7278 The wildcard character ”?” is used to specify the character string to be searched and replaced by the [F7] (REPLACE) function called by pressing [F9] (FIND/REPLACE) in file edit mode. The character
”?” cannot be used to specify the string to be replaced.
[Action]
Remove ”?” from the character string and retry [F7] (REPLACE).
9014 Device name error
Eeoelale7279 An incorrect device name was entered in the device change window that appears in the window for selecting a main program or schedule program.
[Action]
Enter a correct device name.
Example: MD1:, FD0:, FD1:, FD2:, FD3:
9015 Please specify at least 1 selection item
Eeoelale7280 An attempt was made to close the menu switch window used for screen switching while non-display was selected for all screens (by unchecking all check boxes that toggle between display and non-display).
The menu switch window is used to switch screens between display and non-display; hiding all screens or disabling screen display is not allowed.
[Action]
Make sure that the check boxes in the menu switch window are set for at least one screen.
9016 Buffer overflow, cannot continue copy
Eeoelale7281 During line copy, the selected copy range exceeds the remaining buffer size.
9017 Illegal file name entered
Eeoelale7282 The file name format punched on the paper tape is incorrect.
[Action]
An OSP format file name can be used: main file name.extension.
Here,
Main file name: Starts with an alphabetic character, followed by up to 15 alphanumeric characters or hyphens (-)
Extension: Starts with an alphabetic character, followed by 1 or 2 alphanumeric characters or hyphens (-)
9018 Only numbers can be entered
Eeoelale7283 Parentheses nested up to five levels, +, -, /, * (four basic arithmetic operations), or +/- (sign) cannot be used to specify this parameter.
[Action]
Enter a numerical value.
9019 Find function can only be used for numbers
Eeoelale7284 Only numerical values can be entered to activate the find function, which allows the cursor to jump to the specified parameter number.
[Action]
Enter a parameter number as a numerical value to specify the jump target.
9020 Decimal point cannot be used
Eeoelale7285 Entering a decimal point is not allowed.
[Action]
Enter an integer.
9021 File protected
Eeoelale7286 This error occurs in any of the following cases:
1) A protected file was selected for the following processing:
– File edit
– File rename
– File delete
2) A protected file was selected for saving.
3) A protected file was selected as the copy destination.
[Character String]
In case 1): Selected file name (absolute path)
In case 2): Entered file name
In case 3): Copy destination file name (absolute path)
[Action]
In any case, cancel the file protection before performing the required processing.
9022 No received data within ready wait time
Eeoelale7287 When attempting to read or verify data via the RS232C interface, the OSP does not receive data within the preset time.
The ready wait time (described later) may be too short. Alternatively, the settings in the mating device may differ from the settings of the NC optional
parameters (tape puncher interface) appearing in the screen switch menu displayed in parameter setting mode (especially RS232C communication parameters). Alternatively, the communication cable is connected incorrectly.
The preset time can be changed by the setting in B5. The ready wait time is on page 3/3 of the tape puncher interface screen.
Enter ”CONTROL D” to display the RS232C check screen. Investigate the cause and take action by checking this screen and the tape puncher interface parameters.
[Action]
Recheck the wiring and communication parameters between the OSP and the mating device. A cross cable can be used as the communication cable.
9023 Cannot transmit within ready wait time
Eeoelale7288 When attempting to punch data via the RS232C interface, the OSP cannot transmit characters within the preset time.
The ready wait time (described later) may be too short. Alternatively, the settings in the mating device may differ from the settings of the NC optional parameters
(tape puncher interface) appearing in the screen switch menu displayed in parameter setting mode (especially RS232C communication parameters). Alternatively, the communication cable is connected incorrectly.
The preset time can be changed by the setting in B5. The ready wait time is on page 3/3 of the tape puncher interface screen.
Enter ”CONTROL D” to display the RS232C check screen. Investigate the cause and take action by checking this screen and the tape puncher interface parameters.
[Action]
Recheck the wiring and communication parameters between the OSP and the mating device. A cross cable can be used as the communication cable.
Select parameter setting mode and press [F8] (SCREEN CHANGE). Then, select NC optional parameters (long word, word, bit) from the screen switch window menu. The OSP can transmit data only when all the
following parameters are set to ON. Initially they are set to ON (check = 1), but verify whether any problem exists.
CN0: … NC optional parameter bit No.8 bit 1 (M)
NC optional parameter bit No.15 bit 1 (L)
CN1: … NC optional parameter bit No.13 bit 1 (M)
NC optional parameter bit No.16 bit 1 (L)
CN2: … NC optional parameter bit No.14 bit 1 (M)
NC optional parameter bit No.17 bit 1 (L)
CN3: … NC optional parameter bit No.21 bit 1 (M)
NC optional parameter bit No.18 bit 1 (L)
CN4: … NC optional parameter bit No.22 bit 1 (M)
NC optional parameter bit No.19 bit 1 (L)
9024 File being written
Eeoelale7289 The file cannot be opened in read mode in the following cases:
– The specified file is being written to by another function.
– The specified file is being read or written by a READ/WRITE command.
Processing examples for lathe:
– Main program or schedule program is being selected by an external program.
– Gauging data file is being created in MD1.
– Main program is being selected by the schedule program.
Processing examples for machining center:
– Program is selected by DNC-C
– Operating file from DNC-C host computer
– Schedule program
– Registered schedule program for updating is selected by the schedule auto update function.
– Program is selected by PPC
– Program is selected by external device
[Action]
Terminate the above functions before opening the file.
9025 Specified file in use, cannot write
Eeoelale7290 The file cannot be opened in write mode in the following cases:
– The specified file is being written to by another function.
– The specified file is being read by another function.
– The specified file is being read or written by a READ/WRITE command.
Processing examples for lathe:
– Main program or schedule program is being selected by an external program.
– Gauging data file is being created in MD1.
– Main program is being selected by the schedule program.
Processing examples for machining center:
– Program is selected by DNC-C
– Operating file from DNC-C host computer
– Schedule program
– Registered schedule program for updating is selected by the schedule auto update function.
– Program is selected by PPC
– Program is selected by external device
[Action]
Terminate the above functions before opening the file.
9026 RS232C DSR signal OFF
Eeoelale7291 Data I/O was attempted via the RS232C interface while the DSR signal (pin 6) of the OSP was OFF. The cause may be a wiring error, an operation
error of the mating device, or a data setting error of communication parameters.
Enter ”CONTROL D” to display the RS232C check screen. Investigate the cause and take action by checking this screen and the tape puncher interface parameters.
[Action]
Recheck the wiring between the OSP and the mating device and place the mating device in the ready state before retrying data I/O. A cross cable can be used as the communication cable.
To set the OSP communication parameters, select the parameter setting mode and select NC optional parameter (tape punch interface) from the screen selection menu.
9028 RS232C open
Eeoelale7292 The selected RS232C channel is busy. To change the channel, select the parameter setting mode, select NC optional parameter (tape punch interface) from the screen selection menu, and set the required channel number at the device name on page 3/
3. Enter ”CONTROL D” to display the RS232C check screen. Investigate the cause and take measures by viewing this screen and checking the tape punch interface parameters.
[Code]
NCOS error message (hexadecimal)
Bit 31-28 27-24 23-20 19-16 15-12 11-8 7-4 3-0
0000 0000 0000 0000 0000 0000 0000 0000
[Measures]
Wait until the currently used function terminates or change the RS232C channel number above.
9031 RS232C cannot send Xon/Xoff within 150ms
Eeoelale7293 OSP cannot send DC3 (Xoff) when stopping data transmission or verify because the RS232C interface reception buffer is full, or OSP cannot send DC1 (Xon) when restarting data read or verify after stopping.
Alternatively, OSP cannot send DC2 or DC4 for punching.
OSP CS input is not ON. The cable wiring may be faulty or the mating device is not in the ready state. Enter ”CONTROL D” to display the RS232C check screen. Investigate the cause and take measures by viewing this
screen and checking the tape punch interface parameters.
[Measures]
Recheck the wiring between the OSP and the mating device, or place the mating device in the ready state. A cross cable can be used as the communication cable.
Select the parameter setting mode and press [F8] (screen change). Then, select NC optional parameter (long word, word, bit) from the screen change window menu. OSP can send data only when all of the following
parameters are set to ON. Initially, they are set to ON (check = 1), but determine whether any problem has occurred.
CN0: … NC optional parameter bit No. 8 bit 1 (M)
NC optional parameter bit No. 15 bit 1 (L)
CN1: … NC optional parameter bit No. 13 bit 1 (M)
NC optional parameter bit No. 16 bit 1 (L)
CN2: … NC optional parameter bit No. 14 bit 1 (M)
NC optional parameter bit No. 17 bit 1 (L)
CN3: … NC optional parameter bit No. 21 bit 1 (M)
NC optional parameter bit No. 18 bit 1 (L)
CN4: … NC optional parameter bit No. 22 bit 1 (M)
NC optional parameter bit No. 19 bit 1 (L)
9034 RS232C reception error
Eeoelale7294 A parity error, overrun error, or framing error occurred in RS232C, or an overflow occurred in the reception buffer (data reception buffer) used by the OSP. However, these errors
are not caused by processing delay of E100. Enter ”CONTROL D” to display the RS232C check screen. Investigate the cause and take measures by viewing this screen and checking the tape punch interface parameters. A parity error or framing error will occur if incorrect data (baud rate or RS232C
stop bits) is set in B1 to B4 on page 3/3 of the NC optional parameter (tape punch interface) screen. If this error occurs only once in a long time, the cause may be external noise or a board fault.
[Code]
NCOS error message
[Measures]
– If this error occurs once in a long time
Shorten the cable length or use a reliable optical cable adapter and cable.
– If this error occurs frequently
Select from the screen change menu to display the NC optional parameter (tape punch interface) screen and recheck the data setting of B1 to B4 (baud rate or RS232C stop bits) on page 3/3 of the screen.
9037 RS232C cannot send within ready wait time
Eeoelale7295 When attempting to punch through the RS232C interface, the OSP does not send any character within the preset time. The mating device ready time is too short (described later), or the parameter data set on the tape punch interface screen selected from the screen change
menu (especially the RS232C communication parameters) differs from the data set for the mating device. Communication cable connection is
incorrect.
The wait time can be changed by setting data in B5. The ready wait time is on page 3/3 on the tape punch interface screen. Enter ”CONTROL D” to display the RS232C check screen. Investigate the cause and take measures by viewing this screen and checking the tape punch interface parameters.
[Measures]
Recheck the wiring and communication parameters between the OSP and the mating device. A cross cable can be used as the communication cable.
Select the parameter setting mode and press [F8] (screen change). Then, select NC optional parameter (long word, word, bit) from the screen change window menu. OSP can send data only when all of the following
parameters are set to ON. Initially, they are set to ON (check = 1), but determine whether any problem has occurred.
CN0: … NC optional parameter bit No. 8 bit 1 (M)
NC optional parameter bit No. 15 bit 1 (L)
CN1: … NC optional parameter bit No. 13 bit 1 (M)
NC optional parameter bit No. 16 bit 1 (L)
CN2: … NC optional parameter bit No. 14 bit 1 (M)
NC optional parameter bit No. 17 bit 1 (L)
CN3: … NC optional parameter bit No. 21 bit 1 (M)
NC optional parameter bit No. 18 bit 1 (L)
CN4: … NC optional parameter bit No. 22 bit 1 (M)
NC optional parameter bit No. 19 bit 1 (L)
9038 RS232C only ISO tape code with 7-bit character length (A1,2)
Eeoelale7296 On the tape punch interface screen selected from the screen change menu in parameter setting mode, to allow the data setting of “B. RS232C character = 7 bits”, ensure that “A1. Tape
code = ISO” and “A2. ISO/EIA data read automatic discrimination = None”.
If the above settings are not made, this error occurs because the EIA code requires 8 bits to represent its code data.
[Measures]
Before setting ”B. RS232C character = 7 bits” on the tape punch interface screen, set ”ISO” at “A1. Tape code” and set ”None” at ”A2. ISO/EIA data read
automatic discrimination”.
9039 Device name specified by parameter does not exist
Eeoelale7297 A nonexistent device was specified for reading, punching, or verifying using the parameter input/output function, and the execution command was executed.
For example, OTHERS is selected as the device, ”ABCD” is entered as the device name, and then OK is pressed.
[Measures]
Specify an existing device name.
9040 Illegal input command
Eeoelale7298 An incorrect command was entered using the view/change function on the MCS diagnosis or memory diagnosis screen.
[Measures]
Enter a correct command.
For example, MDR, MDW, CA, etc.
9041 Cannot jump
Eeoelale7299 In a jump operation, any of the following data was entered as the line number.
– A number less than 0
– Non-numeric value
– Non-integer number
[String]
Line number entered to jump to
[Measures]
Enter a positive integer as the line number.
9042 Cannot select during program execution
Eeoelale7300 During main program execution, [F7] (QUIT SELECT) was selected in the main program edit mode on the main program window, or during schedule program execution, [F7] (QUIT SELECT) was selected in the schedule program edit mode on the schedule program window.
[Measures]
Wait until the currently running program terminates, and then select [F7] (QUIT SELECT).
9043 Copy destination file name cannot contain '*' character
Eeoelale7301 The file name specified as the copy destination contains a wildcard character.
[String]
File name specified as the copy destination (absolute path)
9044 File already exists, cannot rename
Eeoelale7302 The file name specified as the renamed file name already exists.
[String]
Renamed file name
9045 File does not exist
Eeoelale7303 This error occurs in any of the following cases:
1) During file copying, a file name containing a directory is specified as the copy source, but the file cannot be found in the specified directory.
2) During file deletion, a file name containing a directory is specified, but the file cannot be found in the specified directory.
3) During file verification, the files specified as ”Verify 1″ and ”Verify 2″ cannot be found.
4) A file name is specified during file copying, deletion, protection, or unprotection, but the target file cannot be found.
[String]
In the case of 1), copy source file name (absolute path)
In the case of 2), file name to be deleted (absolute path)
In the case of 3), file names specified as ”Verify 1″ and ”Verify 2″ (absolute path)
In the case of 4), target file name
9046 File name cannot contain '*' character
Eeoelale7304 The file name specified for saving the file contains a wildcard character.
[String]
Entered file name
9047 Buffer overflow, cannot continue deletion
Eeoelale7305 The specified line deletion range exceeds the remaining buffer size.
9048 Cannot search empty string
Eeoelale7306 A search/replace operation was executed without specifying a character string to be searched.
9049 Cannot append file
Eeoelale7307 In direct edit mode, the file currently being edited was specified as the file to be appended.
9050 Specified file is being displayed or edited
Eeoelale7308 The file specified for editing is currently being edited or displayed by another function.
9051 Cannot directly edit 2 files at the same time
Eeoelale7309 An attempt was made to directly edit a file while directly editing another file.
9052 Specified file is program running in B or S
Eeoelale7310 Selects a program running under operation method B or S. However, the OSP cannot cancel such program selection.
9053 File capacity over, editing impossible
Eeoelale7311 The size of the lathe program file or normal program file exceeds the edit buffer size.
During editing in the lathe program and normal program edit mode, the program capacity exceeds the edit buffer size.
9054 Directory
Eeoelale7312 This error occurs in any of the following cases:
1) A directory was designated as a file name during file save.
2) An attempt was made to perform quick copy or quick delete by selecting a directory or parent directory.
3) During file delete, while the device currently in use is DNC-P/T, a directory was designated as the file name to be deleted. Or, during verify, a directory was designated for Verify 1 and Verify 2.
4) An attempt was made to perform quick rename or quick protect/unprotect by selecting the parent directory.
[Character-string]
In case 1), None
In case 2), Selected file name (absolute path) or parent directory
In case 3), Input file name (absolute path)
In case 4), Parent directory
9055 Directory not found
Eeoelale7313 The specified directory does not exist.
[Character-string]
Path name
9056 Invalid device or path name
Eeoelale7314 This error occurs in any of the following cases:
1) DNC-P/T device was specified for the following operations:
– File save
– New file
– Rename
– File protect/unprotect
– File verify
– Directory change to select another file or add a file
2) The device name cannot be obtained from the device name input field because the field is empty.
3) A character string that is not a device name was entered in the device name input field during quick copy operation (another copy).
4) An attempt was made to display a directory without entering a file name or file extension on the directory display (another display) screen.
5) When attempting to change the directory in order to select another file or add a file, the file name input field is blank.
6) A nonexistent path was entered for quick copy, quick delete, copy, delete, read, punch, or verify. Or, no path exists on the directory display screen (for updating directory via function key).
[Character-string]
1) to 3), 6): Path name
4) and 5): None
9057 Invalid file name or path name
Eeoelale7315 This error occurs in any of the following cases:
1) Target file name is not specified in the following operations:
– File name for file save
– File name for new file
– Source file name for file copy
– File name to be deleted in file delete
– File name for file protect/unprotect
– New file name during rename
– File name of Verify 1 or Verify 2 during file verify
2) During quick copy (another copy), both the device name input field and the file name input field are blank.
3) Directory was changed during file creation.
4) The new file name entered during file rename:
– Contains a space.
– Contains a device name (colon).
– Is a directory.
– Contains a wildcard character “*”.
5) Although the file name needs to be changed when copying files because the source file name already exists at the copy destination, the file name input field is blank. The copy destination file name entered during quick copy:
– Contains a wildcard character “*”.
– Contains a device name (colon).
6) The old file name entered during file rename contains a wildcard character “*”.
7) The file name entered in Verify 1 or Verify 2 during file verify contains a wildcard character “*”.
8) The specified directory contains a wildcard character “*”.
9) The specified file name contains a wildcard character “*”.
[Character-string]
In cases 1) and 2): None
In case 3): Input file name
In case 5): Copy destination file name
In case 6): File name before rename
In case 7): File name at Verify 1 or Verify 2
In case 8): Path name
In case 9): File name
9058 Cannot display device information
Eeoelale7316 An attempt was made to display device information when the device is DNC-P/T.
[Character-string]
Device name
9059 Cannot initialize
Eeoelale7317 The specified device cannot be initialized.
[Character-string]
Device name
9060 Cannot condense memory
Eeoelale7318 The memory of the specified device cannot be condensed.
[Character-string]
Device name
9061 Clear file name or set directory
Eeoelale7319 Although multiple source files were specified during file copy, the copy destination file is a single file (not a directory).
[Character-string]
Copy destination file (absolute path)
9062 Same file
Eeoelale7320 The copy source file name is identical to the copy destination file name.
[Character-string]
Copy destination file name (absolute path)
9063 Cannot change device name or directory name
Eeoelale7321 The new file name specified during rename contains a device name or directory name.
The new file name specified during rename and copy contains a device name or directory name.
[Character-string]
Input file name
9064 Cannot verify non-text file
Eeoelale7322 A binary file was specified at Verify 1 or Verify 2 during verify.
[Character-string]
File name at Verify 1 or Verify 2 (absolute path)
9065 Not sequence name or number
Eeoelale7323 Data other than a sequence name or block counter value was entered in the sequence restart window.
[Action]
Enter a sequence name or block counter value.
9066 RS232C channel in use
Eeoelale7324 The RS232C interface channel number CN*: (*=0 to 4) following the message is in use by another command.
The same device name (RS232C interface channel number) is used for program operations executed by [F12] (RS232C) and for setting zero points, tool data, and parameters using the parameter input/output function (normally assigned to [F6]).
To set the device name, select parameter setting mode, press [F8] (Display Change), and select NC optional parameter (tape puncher interface) from the displayed menu.
The channels used by other commands are explained below:
– When the same channel number is set at the device name in NC optional parameter (gauging result display), measurement results are sent to the printer via RS232C.
– Data communication is executed according to programmed READ/WRITE statements using the same RS232C interface channel.
– An attempt was made to perform a program operation (RS232C) simultaneously with setting zero points, tool data, and other parameters using the parameter input/output function.
[Action]
Change the device name or use the channel after the function currently in use is completed.
To change the device name, select parameter setting mode, press [F8] (Display Change), and select NC optional parameter (tape puncher interface) from the displayed menu.
9067 Cannot input decimal point, character string, negative number
Eeoelale7325 A character string that is not a numeric value or a negative number was entered.
[Action]
Enter a positive integer.
9068 Input data overflow
Eeoelale7326 The data set at the parameter indicated by an asterisk (*) exceeds the setting range. The erroneous word is indicated in ” ”.
[Sub-information]
Auxiliary information
[Character-string]
Character string for abnormal word command
Setting range: (P*Q*’xxxxxxxxxxxxxxx’)
[Action]
Check the command indicated in ” ”, correct the unit or setting value, and re-send the command. Data in MD1: cannot be corrected by editing data in program operation mode.
9069 Disk not initialized
Eeoelale7327 1) The floppy disk designated as the device (for selecting the main program or schedule program) is not initialized in OSP format. The designated floppy disk or memory is in another format (MS-DOS, EXORMACS, or IBM).
2) The VD1 data in the floppy disk or memory is corrupted.
[Action]
• Check the floppy disk format. If it is not in OSP format, change it to OSP format using the INIT function in program operation.
• Check the VD1 (sector 0) data in the floppy disk or memory.
9070 Cannot start interactive dialogue
Eeoelale7328
9071 Over 155 characters in 1 line
Eeoelale7329 The line length that can be read by the parameter input/output function or by program operation (RS232C) is limited to 155 characters. If this limit is exceeded, the OSP cannot read the line. The abnormal line is indicated by the character string following the error message. The cause may be that the line feed code (LF) was omitted or is a code other than LF.
[Character-string]
Abnormal line
[Code]
None
[Sub-information]
P**’ abnormal line’
If the P number is not determined, P** does not appear. The sub-information appears only when using the machining parameter input/output function.
[Action]
Correct the displayed character string line.
9072 File (device) busy
Eeoelale7330 A new file cannot be read because the file input/output function is being used for other purposes.
[Character-string]
None
[Code]
None
9073 Cannot edit during DNC remote buffer operation
Eeoelale7331 During remote buffer operation via DNC-RT (lathe) or DNC-DT (machining center), the (main or schedule) program selected in the operation mode cannot be edited.
[Character-string]
None
[Code]
None
[Action]
Edit the program file used as the transfer data source.
9074 Cannot select directory
Eeoelale7332 A program was selected while the directory was displayed on the window for selecting a main program or schedule program.
[Character-string]
None
[Code]
None
[Measures]
Select a file from the displayed directory before selecting the program.
9075 Illegal device name only TC:, TCA: - TCH: can be set.
Eeoelale7333 For remote buffer operation via DNC-RT (lathe) or DNC-DT (machining center), a device other than TC:, TCA: to TCH: was selected on the window for selecting a main program or schedule program.
[Character-string]
None
[Code]
None
[Measures]
For remote buffer operation via DNC-RT (lathe) or DNC-DT (machining center), TC:, TCA: to TCH: must be selected as the device. Select the proper device.
9076 RS232C IF not open, cannot send DC code
Eeoelale7334 Because the communication interface was not open (not initialized) for some reason, the OSP could not send DC code, causing a transmission failure. Software trouble is suspected.
[Character-string]
None
[Code]
Type of DC code not sent
1… DC1
2… DC2
3… DC3
4… DC4
[Measures]
Contact your local service center.
9077 Input character string is not hexadecimal
Eeoelale7335 The input character string is not a hexadecimal number.
[Character-string]
None
[Code]
None
[Measures]
Input data in hexadecimal character format (0 to 9, A to F).
9078 Output file name cannot be specified for multi-file transfer
Eeoelale7336 An output file name was specified during multi-file transfer.
[Character-string]
None
[Code]
None
[Measures]
In multi-file transfer, no output file name can be specified.
9079 Multi-file transfer is valid only under DC code control
Eeoelale7337 Multi-file transfer was attempted without selecting DC code control as the flow control method.
[Character-string]
None
[Code]
None
Select DC code control as the flow control method before performing multi-file transfer.
9080 Valid start or end number
Eeoelale7577 The start number or end number is outside the allowable range.
[Measures]
Specify an appropriate start number and end number, or leave the start number or end number field blank (all specified).
9081 Cannot search - DNC remote buffer mode
Eeoelale7578 Sequence search is invalid for the program (main or schedule) selected in operation mode during remote buffer operation via DNC-B.
9082 Sequence number command
Eeoelale7579 The start sequence number or increment value specified during sequence number distribution is incorrect.
[Code]
1-> The start sequence number or increment value is greater than a 4-digit number.
3-> The start sequence number or increment value is not specified.
4-> Other errors other than the above
[Probable Fault Cause]
Operation error
[Measures]
Input a correct value.
9083 Language menu cannot be displayed
Eeoelale7580 The display language can be selected from the language menu. However, for some reason, this language menu cannot be formed.
[Code]
100 -> The language information file (CF0: \DATA\MD0ATXT\) does not exist in the predefined storage area (SFLDA01*.PBT).
101 -> The language switch information file (CF0: \FL\) does not exist in the predefined storage area (SFLDB01*.CNT).
102 -> The header line of the language switch information file does not match.
103 -> The language combination information file (CF0: \FL\) does not exist in the predefined storage area (SFLDC01*.CNT).
104 -> The header line of the language combination information file does not match.
9084 Please input DECI, HEXA or ‘character’
Eeoelale7581 The input character or character string is not a decimal number, $ plus hexadecimal number, or a character enclosed in single quotes (’).
[Measures]
Input a decimal number in the range of 0 to 255, a hexadecimal number in the range of $00 to $FF, or a character enclosed in single quotation marks.
9085 Invalid text command
Eeoelale7582 Program input/output or verify was attempted in DNC-C DNC mode when communication parameter 'NCP' was OFF.
[Measures]
When inputting, outputting, or verifying a program in DNC-C DNC mode, set the communication text parameter ”NCP” to ON.
9086 Please input integer up to 8(Group No.) or 4(Serial No.) digits.
For machines with TOOL-ID specifications, an illegal number was designated for data input, data output, group number check, or serial number in the DNC-C function.
[Measures]
Input an integer of up to 8 digits for the group number.
Input an integer of up to 4 digits for the serial number.
9087 Can not display maximum file size exceeded currently.
When the lathe is switched to automatic operation mode for the first time, maker subprogram registration and main program selection are initialized. Files exceeding the specified size can only be viewed after initialization is completed.
If an attempt is made to view a file exceeding the specified size after NC start-up before the machine is switched to automatic operation mode, this error occurs.
[Character-string]
Specified file name
[Measures]
If the machine has not been switched to automatic mode after starting the NC, switch to automatic mode before viewing a file exceeding the specified size.
9089 THE EDIT BUFFER OVERFLOWED AT THE DIVISION.
An overflow occurred in the edit buffer when executing the A/B turret division with the lathe division function.
[Code]
1: The size between the preceding block and the first block including G13 or G14 exceeds the specified size.
2: The size from the first block including M02 or M30 exceeds the specified size.
9090 Invalid main program name.
The program name entered in the main program name column on the file save window is not composed of alphanumeric characters up to 5 digits starting with ”O”.
[Character-string]
Input character string
[Measures]
Enter alphanumeric characters up to 5 digits starting with ”O” for the main program name.
9091 P No. not find.
a) No P code exists at the cursor position.
b) The P code consists of more than 5 characters.
c) No synchronized P code exists in the unhighlighted TEDIT.
[Character-string]
a) None
b) P code
c) None
[Measures]
a) Move the cursor to the P code or add a P code at the cursor position.
b) Edit the P code to be within 5 characters.
c) Add the P code to the unhighlighted TEDIT.
9093 Can not edit – Not selected user sub program.
An attempt was made to edit a user subprogram using ”F7: User subprogram edit” without selecting a user subprogram.
[Probable Fault Cause]
1) An attempt was made to edit a user subprogram using ”F7: User subprogram edit” on the main program screen in automatic operation mode without selecting a user subprogram from the main program selection. When no user subprogram is selected, editing user subprograms with ”F7: User subprogram edit” is not possible.
2) An attempt was made to edit a user subprogram using ”F7: User subprogram edit” on the schedule program screen in automatic operation mode without selecting a user subprogram from the main program selection. When no user subprogram is selected, editing user subprograms with ”F7: User subprogram edit” is not possible.
[Measures]
Before editing the selected user subprogram with ”F7: User subprogram edit”, select the user subprogram on the main program selection screen.
By selecting a schedule program, the main program and user subprograms are selected. Only after completing the above operation can the selected user subprogram be edited with ”F7: User subprogram edit”.
9095 APA TRACE
Failed to generate the APA trace data file.
[Character-string]
‘NOT LOCAL ADDRESS’: The area corresponding from the initial address of the trace buffer designated in ”BUFFER ADDRESS” to the buffer data size set in ”DATA SIZE” does not exist in the DRAM of the UCMB.
‘DATA SIZE’: The buffer data size designated in “DATA SIZE” is 0.
‘FILE SESSION’: This device cannot generate a data file due to operation by another function.
[Measures]
When the character string is ’NOT LOCAL ADDRESS’:
If the trace buffer is in the DRAM of the UCMB, designate ”BUFFER ADDRESS” or ”DATA SIZE”. If the trace buffer is not in the DRAM of the UCMB, set
‘SYSTEM’ to ”ADDRESS CHOICE”.
When the character string is ’DATA SIZE’:
Set ’DATA SIZE’ correctly.
When the character string is ’FILE SESSION’:
Execute this operation after the operation of this device by the other function is completed.
9096 THE EDIT BUFFER OVERFLOWED AT THE COMBINATION.
An overflow occurred in the edit buffer when executing combination after dividing turrets with the lathe division function.
9098 Invalid input number.
When designating the turret division/edit function number, the data entered for the numeric part other than ”P” is not a positive integer of up to 4 digits.
[Measures]
Enter a positive integer of up to 4 digits for the numeric part other than ”P”.
9099 Buffer overflow. Can not cut anymore.
Selected block range exceeds the cutting buffer size.
9103 Completely identical
Source directory and destination directory are identical.
[Character-string]
Full path of specified directory.
9104 Cannot execute this directory
The [UP ↑] key was pressed even though there is no parent directory.
9105 Can not edit/list IGF files.
Attempted to edit or list an IGF data file (*.IGF/*.IDM).
IGF data files are used for Advanced One-Touch IGF.
9106 RS232C SSU firmware mismatch.
SSU hardware does not match the driver.
[Measures]
Replace the SSU.
9108 RS232C Can not use the OSP format floppy disk.
OSP format floppy disk cannot be used for the RS232C file input/output function.
9109 The number of characters before G13/G14 block is over.
Overflow occurred in the edit buffer during A/B turret splitting using the lathe split function.
Specified size between the previous block and the first block containing G13 or G14 was exceeded.
9110 The number of characters after M02/M30 block is over.
Overflow occurred in the edit buffer during A/B turret splitting using the lathe split function.
Specified size from the first block containing M02 or M30 was exceeded.
9111 Can not copy directory to a file.
A file with the specified name already exists at the directory copy destination.
9400 Cannot execute command during reset
Eeoelale7338 Tool layout command or auto scaling command for 2D/3D animation was issued during NC reset. Because these commands require program analysis, the NC uses a processing method that issues processing requests between tasks.
However, if the NC is reset, processing of these commands continues under the condition that all requests issued between tasks have been completed. This means that a deadlock may occur (depending on the timing of NC reset and command execution). This error occurs to prevent such a deadlock.
[Measures]
• Do not execute a tool layout command or auto scaling command for 2D/3D animation during NC reset.
• Do not press the function keys for the above commands repeatedly. If pressed, the second command will be executed during the NC reset caused by the first command, which may cause this error to occur.
9401 No valid area, reset origin or stroke end limit
Eeoelale7339 The values set for the origin and stroke limits have no valid range.
[Measures]
Check the set values of the origin or stroke limits.
9402 Output data not designated, cannot execute output
Eeoelale7340 Attempted to output although output data was not specified in the individual settings for data output by D-PIP.
[Measures]
Specify at least one output data block before triggering data output by D-PIP.
9403 Reading UGC data, cannot execute command
Eeoelale7341 A command to generate UGC (User Graphic Command) data was executed while the NC was reading UGC data required for drawing animation.
Reading and waiting for UGC data cannot be performed simultaneously.
[Supplement]
If a UGC data generation command is executed immediately after an NC reset, a conflict may occur between the processing for reading UGC data for tool redraw and the processing for waiting for UGC data according to the command, causing a deadlock. This error occurs to prevent such a deadlock.
This error may also occur if a tool layout or auto scaling command is executed immediately after the same command has terminated normally. This is because the NC is reset when checking M02 during program analysis by command execution.
[Measures]
• Do not execute any command to generate UGC data immediately after an NC reset.
• Do not execute the same command immediately after completing a command to generate UGC data. More specifically, after NC reset or command completion, wait about 5 to 10 seconds before executing such a command. The above error will then not occur.
• The wait time should be between 5 and 10 seconds, because the time required for internal processing varies depending on the selected specifications.
9404 D-PIP optional bit parameter data bit count invalid
Eeoelale7342 In the input for D-PIP, the number of bits of the value specified in optional parameter bit is not 8.
[Character-string]
Line where D-PIP error occurred
[Measures]
Set "8" as the number of bits specified in optional parameter bit before inputting data in the D-PIP file.
9405 D-PIP bit data contains character other than "0" or "1"
Eeoelale7343 In the input for D-PIP, the data specified in optional parameter bit contains a character, symbol, or number other than 0 or 1.
[Character-string]
Line where D-PIP error occurred
[Measures]
Set the bit data to "0" or "1" before inputting data in the D-PIP file.
9406 Warm-up operation preparing, cannot execute command
Eeoelale7344 Attempted to execute any of the following operations while the warm-up program was running:
– Main program select
– Schedule program select
– Execute tool layout command
– Select auto scale for 2D animation on standard scale window
– Select auto scale for 3D
[Measures]
Wait for the warm-up program to complete, or stop the warm-up program by NC reset, and then execute the above command.
9407 File operating, cannot execute command
Eeoelale7345 The following commands cannot be executed during file operation (such as data writing):
– Main program select
– Schedule program select
– MSB load
– Automatic library program load after first power-on
– Automatic program load after first power-on
– Input, output, or verify D-PIP file data
– Register library program
– Initialize library program
– Exclude a library program
– Exclude all library programs
[Character-string]
None
[Code]
None
[Measures]
Complete or stop data writing or other file operations currently in progress, and then execute the above command.
9408 Illegal program name input
Eeoelale7346 INPUT ____ (____ = A to Z, 0 to 9)
An incorrect format was used to input a main program or subprogram name on a screen (such as main program select window, library program registration window) or G/M code macro window.
Program name format:
O + up to four alphanumeric characters
[Character-string]
None
[Code]
None
[Measures]
Input the program name in the specified format.
9409 Loader program not found
Eeoelale7583 Attempted to transfer data from loader to NC when no loader data exists.
[Measures]
Have the loader read the loader program before transferring the program.
9410 Robot program not found
Eeoelale7584 Attempted to transfer data from robot to NC when no robot data exists.
[Measures]
Have the robot read the robot program before transferring the program.
9411 Spindle mode mismatch
Eeoelale7585 Attempted to calculate ZA-, WA-, Ys-, Yi-, or Zb-axis movement when the spindle mode selected on the operation panel differed from the spindle mode selected for the turret. (This alarm applies only to LT-series new and old lathes).
[Measures]
Match the spindle mode selected on the operation panel with the spindle mode selected for the turret.
9412 No valid range, re-enter origin offset A or stroke end limit
Eeoelale7586 The data setting range is not defined for the data attempted to be set because an inappropriate value was set as starting point A or stroke end limit A.
[Measures]
Check the values set as starting point A and stroke end limit A.
9413 No valid range, re-enter origin offset B or stroke end limit
Eeoelale7587 The data setting range is not defined for the data attempted to be set because an inappropriate value was set as starting point B or stroke end limit B.
[Measures]
Check the values set as starting point B and stroke end limit B.
9414 M-axis in use, cannot execute command
Eeoelale7588 Setting, adding, or calculating the origin offset value (system parameter) for the T-axis while the NC was controlling the M-axis of an NC turret equipped with a T/M axis switching mechanism.
[Measures]
Select the T-axis before setting, adding, or calculating the T-axis origin offset value.
9415 Loader transfer impossible
Eeoelale7589 Attempted this operation when data transfer was prohibited.
[Code]
1: Program transfer from NC to LDR
2: Program transfer from LDR to NC
3: Program verify
4: Data transfer from NC to LDR
5: Data transfer from LDR to NC
6: Data verify
[Measures]
Set the EC input to allow data transfer.
9416 Robot transfer impossible
Eeoelale7590 Attempted this operation when data transfer was prohibited.
[Code]
1: Program transfer from NC to RBT
2: Program transfer from RBT to NC
3: Program verify
4: Data transfer from NC to RBT
5: Data transfer from RBT to NC
6: Data verify
[Measures]
Set the EC input to allow data transfer.
9417 Address out of range
Eeoelale7591 Data or program cannot be transferred from NC to LDR because the file size is larger than the communication buffer size.
(Here, during program transfer, communication buffer refers to the work buffer; during data transfer, communication buffer refers to the data transfer buffer)
[Code]
File size
9418 Loader data changed
Eeoelale7592 Error occurred during data transfer from NC to LDR or from LDR to NC.
[Code]
Error code converted into BCD data
9419 Loader data change
Eeoelale7593 Error occurred during data transfer from NC to RBT or from RBT to NC.
[Code]
Error code converted into BCD data
9800 Only numeric value can be used; decimal point is not allowed
Eeoelale7347 A character specified as an input value is not a numeric value (including a decimal point).
[Measures]
Enter numeric characters.
9801 Trigger address not set
Eeoelale7348 A trigger address is not set before setting trigger address conditions.
[Measures]
Set a trigger address before setting trigger address conditions.
9802 Trigger condition has no reference value, cannot be set.
Eeoelale7349 A reference value cannot be set because reference value setting conditions are not satisfied.
A reference value can be set only when the trigger signal is not a bit identifier and the trigger condition is set to “= EQU”.
[Measures]
• Change the trigger signal to a word or long word.
• Set the trigger condition to ”= EQU” before setting a reference value.
9803 Identifier range exceeded
Eeoelale7350 The specified identifier address is out of the processing range.
The address range may be exceeded or auxiliary information may be abnormal.
[Measures]
• Create and install a correct auxiliary information file.
• Specify an identifier address within the processing range.
9804 Input data overflow
Eeoelale7351 The input data is too large or too small.
[Measures]
Enter a correct value.
85007 Illegal code detected in specification code. V-FKEY startup terminated.
An incorrect executable file path is specified. Or the specified executable file does not exist.
[Code]
1: An incorrect executable file path is specified. Or the specified executable file does not exist.
[Measures]
1: Check the executable file path specification in the vertical function key setting file (LVFKA####.INI/MVFKA####.INI).
Or check whether the executable file of the setting file exists.
85008 Insufficient physical memory capacity.
Physical memory capacity is insufficient.
[String]
Function name
[Code]
Capacity of currently installed physical memory (MB, decimal)
[Measures]
Add memory.
99101 Bus error
Eeoelale7371 NMI is input to the CPU of FWMB.
[Code]
The abbreviation indicates the cause of NMI. As shown below:
SysBus:
System bus error occurred.
SBParity:
System bus parity error occurred.
CycOver:
Cycle over error occurred.
ECC:
ECC 2-bit error occurred.
Protect:
Protection error occurred.
Parity:
Common memory parity error occurred.
[Probable Fault Cause]
• FWMB and related hardware
• Control software
[Measures]
Find the board accessed by the CPU of FWMB. Replace the faulty board and check whether the above error still occurs. If the error still occurs, replace the FWMB and check if the condition
improves.
99102 Illegal write address
Eeoelale7372 An address error occurred while the CPU of FWMB was accessing memory for writing. Its direct cause is that the CPU of FWMB executed the following operation:
– Read an instruction from an odd address.
– Read word data from outside the word data area.
– Read long word data from outside the long word data area.
– Read data in H’80000000-FFFFFFFF logical space in user mode.
[Code]
Address accessed by the CPU of FWMB
[Probable Fault Cause]
• FWMB
• Control software
[Measures]
Replace FWMB and check whether the above error still occurs.
99103 Illegal read address
Eeoelale7373 An address error occurred while the CPU of FWMB was accessing memory for reading. Its direct cause is that the CPU of FWMB executed the following operation:
– Read an instruction from an odd address.
– Read word data from outside the word data area.
– Read long word data from outside the long word data area.
– Read data in H’80000000-FFFFFFFF logical space in user mode.
[Code]
Address accessed by the CPU of FWMB
[Probable Fault Cause]
• FWMB
• Control software
[Measures]
Replace FWMB and check whether the above error still occurs.
99104 Illegal instruction
Eeoelale7374 The CPU of FWMB caused an exception for a general illegal instruction error.
Its direct cause is that the CPU of FWMB executed the following operation:
– Decoded an undefined instruction not in a delay slot.
– Decoded a privileged instruction not in a delay slot in user mode.
[Probable Fault Cause]
• FWMB
• Control software
[Measures]
Replace FWMB and check whether the above error still occurs.
99105 Slot illegal instruction
Eeoelale7375 The CPU of FWMB caused an exception for a slot illegal instruction. Its direct cause is that the CPU of FWMB executed the following operation:
– Decoded an undefined instruction in a delay slot.
– Decoded an instruction rewriting the PC in a delay slot.
– Decoded a privileged instruction in a delay slot in user mode.
[Probable Fault Cause]
• FWMB
• Control software
[Measures]
Replace FWMB and check whether the above error still occurs.
99106 FPU exception
Eeoelale7376 An exception occurred in the FPU of FWMB.
[Code]
FPSCR register value of FPU
[Probable Fault Cause]
• FWMB
• Control software
[Measures]
Replace FWMB and check whether the above error still occurs.
99107 Undefined exception
The CPU of FWMB detected an undefined exception. The undefined exceptions are: TLB miss exception, TLB invalid exception, initial page write exception, and TLB protection exception.Eeoelale7377
[Code]
Vector number corresponding to the detected exception.
[Probable Fault Cause]
• FWMB
• Control software
[Measures]
Replace FWMB and check whether the above error still occurs.
99108 Undefined TRAPA
The CPU of FWMB detected an undefined TRAPA.Eeoelale7378
[Code]
Vector number corresponding to the detected TRAPA.
[Probable Fault Cause]
• FWMB
• Control software
[Measures]
Replace FWMB and check whether the above error still occurs.
99109 Undefined interrupt
Eeoelale7379
The CPU of FWMB detected an undefined interrupt.
[Code]
Vector number corresponding to the detected interrupt.
[Probable Fault Cause]
• FWMB
• Control software
[Measures]
Replace FWMB and check whether the above error still occurs.
99110 GDP interrupt
Eeoelale7380
Exception error occurred in GDP.
[Probable Fault Cause]
• FWMB
• Control software
[Measures]
Replace FWMB and check whether the above error still occurs.
99111 Illegal break
A break exception occurred even though no breakpoint was set.Eeoelale7381
[Probable Fault Cause]
• FWMB
• Control software
[Measures]
Replace FWMB and check whether the above error still occurs.
99201 Kernel
Eeoelale7382 The kernel operating the FWMB detected an error.
[Code]
Details of the error are described by a combination of four numbers: type, ercd, inf1, and inf2. type shows the error type in binary. Details of each type number
are described below. The other three numbers are described in hexadecimal.
0: Error in kernel creation information.
ercd: Error code of kernel creation information.
inf1: Error descriptor
inf2: Error number
-1: Context error occurred in ext_tsk.
ercd: Error code of ext_tsk
inf1: Address calling ext_tsk
inf2: Undefined
-2: Context error occurred in exd_tsk.
ercd: Error code of exd_tsk
inf1: Address calling exd_tsk
inf2: Undefined
-4: Context error occurred in vsys_clk.
ercd: Error code of vsys_clk
inf1: Address calling vsys_clk
inf2: Undefined
-5: Context error occurred in ret_svc.
ercd: Error code of ret_svc
inf1: Address calling ret_svc
inf2: Undefined
-6: Context error occurred in vret_sig.
ercd: Error code of vret_sig
inf1: Address calling vret_sig
inf2: Undefined
-7: Context error occurred in vrst_tsk.
ercd: Error code of vrst_tsk
inf1: Address calling vrst_tsk
inf2: Undefined
-8: Overflow occurred in stack.
ercd: Stack number
inf1: Address where overflow occurred in stack
inf2: Stack pointer at this moment
-16: Undefined interrupt/exception occurred.
ercd: Vector number
inf1: Address where exception/interrupt occurred
inf2: SR at this moment
[Probable Fault Cause]
• FWMB
• Control software
[ Measures to Take]
Replace the FWMB and check if the above error still occurs.
99202 Jump to near address 0
Eeoelale7383 The CPU of the FWMB operates near address zero.
[ Probable Fault Cause]
• FWMB
• Control software
[ Measures to Take]
Replace the FWMB and check if the above error still occurs.
99203 Internal
Eeoelale7384 An error occurred in the FWMB firmware.
[ Code]
Internal value
[ Probable Fault Cause]
• FWMB
• Control software
[ Measures to Take]
Replace the FWMB and check if the above error still occurs.
99204 Panel driver
Eeoelale7385 An abnormality occurred in the panel driver.
[ Code]
Internal value
[ Probable Fault Cause]
• FWMB
• Control software
[ Measures to Take]
Replace the FWMB and check if the above error still occurs.
99205 Monitor
Eeoelale7386 An abnormality occurred in the monitor.
[ Code]
Internal value
[ Probable Fault Cause]
• FWMB
• Control software
[ Measures to Take]
Replace the FWMB and check if the above error still occurs.
99206 Pipe driver
Eeoelale7387 An abnormality occurred in the pipe driver.
[ Code]
Internal value
[ Probable Fault Cause]
• FWMB
• Control software
[ Measures to Take]
Replace the FWMB and check if the above error still occurs.
99207 SCI driver
Eeoelale7388 An abnormality occurred in the SCI driver.
[ Code]
Internal value
[ Probable Fault Cause]
• FWMB
• Control software
[ Measures to Take]
Replace the FWMB and check if the above error still occurs.
99208 I/O manager
Eeoelale7389 An abnormality occurred in the I/O manager.
[ Code]
Internal value
[ Probable Fault Cause]
• FWMB
• Control software
[ Measures to Take]
Replace the FWMB and check if the above error still occurs.
99209 Chardisp driver
Eeoelale7390 An abnormality occurred in the Chardisp driver.
[ Code]
Internal value
[ Probable Fault Cause]
• FWMB
• Control software
[ Measures to Take]
Replace the FWMB and check if the above error still occurs.
99210 Forced trap
Eeoelale7391 The CPU of the FWMB is rebooted by a forced reset from outside the FWMB.
[ Probable Fault Cause]
• FWMB
• Control software
[ Measures to Take]
Replace the FWMB and check if the above error still occurs.
99301 Memory crash
Eeoelale7392 FWMB memory corruption is detected.
[ Code]
The abbreviation indicates the damaged memory type. The meanings of abbreviations are shown below:
[ Probable Fault Cause]
FWMB
[ Measures to Take]
Replace the FWMB.
99302 Unexpected board status
Eeoelale7393 An error was detected in the register value of the FWMB.
[ Code]
The abbreviation indicates the error type. The meanings of abbreviations are shown below:
MSTP:
Receiving the MSTP signal.
SNMI:
Sending the SNMI signal.
NMI:
NMI detected.
Slave shared memory parity:
A parity error occurred in the shared memory during slave mode operation.
Slave system bus protection:
A protection error occurred during slave mode operation.
Slave system bus data parity:
A data parity error occurred during slave mode operation.
Abbreviation Memory type
SharRAM Shared memory
LocalRAM Local memory
VRAM Video RAM
FROM Flash ROM
Slave system bus address parity:
An address parity error occurred during slave mode operation.
[ Probable Fault Cause]
FWMB and related hardware
[ Measures to Take]
Replace the FWMB and check if the above error still occurs. If the condition does not change, replace other hardware.
99303 Cannot open keyboard
Eeoelale7394 Keyboard initialization failed. This error occurs when the control panel is faulty, the FWMB is faulty, or the cable between the operation panel and the FWMB is defective. In the case where the operation panel power supply and the
main power supply are powered by different power sources, this error may also occur if the power-on timing of the operation panel is delayed after turning on the main power supply.
[ Probable Fault Cause]
FWMB, operation panel, or cable between operation panel and FWMB.
[ Measures to Take]
If different power supplies are used, turn on the power to the operation panel immediately after turning on the main power supply and check if the above error still occurs. If the same power supply is used, replace
the FWMB, the operation panel, or the cable connecting the operation panel and the FWMB, and check if the above error still occurs.
99304 Cannot receive UCMB’s SW
Eeoelale7395 The FWMB cannot receive the switch signal from the UCMB.
[ Probable Fault Cause]
FWMB and related hardware
[ Measures to Take]
Replace the FWMB and check if the above error still occurs. If the above error still occurs, replace the UCMB. If the condition does not improve after replacement, replace the related hardware.
99305 Cannot rendezvous with SBP
Eeoelale7396 The FWMB cannot start up with the SBP.
[ Probable Fault Cause]
FWMB and related hardware
[ Measures to Take]
Replace the FWMB and check if the above error still occurs. If the above error still occurs, replace the UCMB. If the condition does not improve after replacing these boards, replace the related
hardware.
99306 Illegal command
Eeoelale7397 The FWMB detected an unknown command.
[ Code]
Detected command
[ Probable Fault Cause]
• FWMB and related hardware.
• Control software
[ Measures to Take]
Replace the FWMB and check if the above error still occurs. If the above error still occurs, replace the UCMB. If the condition does not improve after replacing these boards, replace the related
hardware.
99307 Program exit
Eeoelale7398 The program ended at the FWMB.
[ Code]
Error code and the task ID that ended first.
99308 No CompactFlash
Eeoelale7399 The CompactFlash was removed from the FWMB.
[ Probable Fault Cause]
FWMB, CompactFlash
[ Measures to Take]
Check the installation state of the CompactFlash to see if it is securely mounted on the FWMB. If it is securely mounted, replace the FWMB and check if the above error still
occurs. If the above error still occurs, replace the CompactFlash or FWMB.
99309 No font
Eeoelale7400 The specified font does not exist.
[ Code]
Searched font language
[ Probable Fault Cause]
FWMB
[ Measures to Take]
Replace the FWMB and check if the condition improves.
99401 Syntax error
Eeoelale7401 The monitor command contains a syntax error.
[ Probable Fault Cause]
Input command
[ Measures to Take]
Check the syntax of the monitor command.
99402 Invalid argument
Eeoelale7402 The monitor command contains an invalid argument.
[ Probable Fault Cause]
Input command
[ Measures to Take]
Check the argument used in the monitor command.
99403 Invalid option
Eeoelale7403 The monitor command contains an invalid option.
[ Probable Fault Cause]
Input command
[ Measures to Take]
Check the option used in the monitor command.
99404 Invalid command
Eeoelale7404 The input command is not a monitor command.
[ Probable Fault Cause]
Input command
[ Measures to Take]
Enter the correct command.
99405 Too many arguments
Eeoelale7405 The monitor command contains too many arguments.
[ Probable Fault Cause]
Input command
[ Measures to Take]
Reduce the number of arguments in the monitor command.
99406 Internal error
Eeoelale7406 An error occurred within the monitor command.
99407 Time out
Eeoelale7407 Execution of the monitor command was suspended due to a timeout.
[ Probable Fault Cause]
Hardware monitored by the monitor command
[ Measures to Take]
Check whether the device (or other hardware) monitored by the monitor command is faulty.
99408 No memory space
Eeoelale7408 Execution of the monitor command was suspended because there is no memory space.
[ Probable Fault Cause]
Input command
[ Measures to Take]
If the argument length can be changed, reduce the number of arguments.
99409 CPU error
Eeoelale7409 The specified monitor command cannot run on this CPU.
99410 No such file
Eeoelale7410 The specified file does not exist.
99411 Load address error
Eeoelale7411 There is no address to be loaded.
99412 File system error
Eeoelale7412 An error was detected in the file system.
[Probable Fault Cause]
File system
[Measures to Take]
If the CompactFlash was inserted or removed while power was on, turn off the power and then turn it back on. Check whether the above error still occurs. If the above
error still occurs, check the file system of the relevant storage device.
99451 No font
Eeoelale7595 Font data required for code set file or language information does not exist.
[Probable Fault Cause]
Control software
[Measures to Take]
Check the control software.
99452 No code set file
Eeoelale7596 The code set file does not exist in the CompactFlash.
[Character-string]
Name of code set file
[Probable Fault Cause]
Control software
[Measures to Take]
Check the control software.
99453 Code set file has no language
Eeoelale7597 The language identifier indicated by the code does not exist in the code set file.
[Code]
Language identifier
[Probable Fault Cause]
Control software
[Measures to Take]
Check the control software.
99454 Code set file has no language code set
Eeoelale7598 There is no code description related to the language identifier indicated by the code in the code set file.
[Code]
Language identifier
[Probable Fault Cause]
Control software
[Measures to Take]
Check the control software.
99455 Not enough VRAM for font
Eeoelale7599 Not enough free space in video memory for loading fonts.
[Probable Fault Cause]
Control software
[Measures to Take]
Check the control software.
99456 Not enough memory for font
Eeoelale7600 Not enough free space in the memory area used for controlling fonts.
[Probable Fault Cause]
Control software
[Measures to Take]
Check the control software.
99457 Not enough memory for font tag
Eeoelale7601 Not enough free space in the memory area used for controlling font tags.
[Probable Fault Cause]
Control software
[Measures to Take]
Check the control software.
99458 Illegal font header in font data or insufficient memory
Eeoelale7601 Insufficient memory area for font tag control.
[Probable Fault Cause]
Control software
[Measures to Take]
Check the control software.
99459 Illegal block length in font data
Eeoelale7601 Insufficient memory area for font tag control.
[Probable Fault Cause]
Control software
[Measures to Take]
Check the control software.
99460 Illegal bitmap boundary in font data
Eeoelale7601 Insufficient memory area for font tag control.
[Probable Fault Cause]
Control software
[Measures to Take]
Check the control software.
99461 Illegal font table in font data or insufficient memory
Eeoelale7601 Insufficient memory area for font tag control.
[Probable Fault Cause]
Control software
[Measures to Take]
Check the control software.
99462 No HLB in ROM (v2.0)
Eeoelale7601 Insufficient memory area for font tag control.
[Probable Fault Cause]
Control software
[Measures to Take]
Check the control software.
EEeeooeellaallee77660056
99463 File operation trouble
Eeoelale7607 An error occurred during CompactFlash non-operation.
[Probable Fault Cause]
The CompactFlash is not properly installed or hardware related to FWMB CompactFlash is damaged.
[Measures to Take]
Check whether the CompactFlash is properly installed. Replace FWMB.
99500 Value out of range
Eeoelale7413 Variable type conversion failure.
[Character-string]
“REAL to INT”: Real to integer type conversion
“REAL to SINT”: Real to short integer type conversion
“REAL to BYTE”: Real to byte type conversion
“INT to SINT”: Integer to short integer type conversion
“INT to BYTE”: Integer to byte type conversion
“SINT to BYTE”: Short integer to byte type conversion
[Probable Fault Cause]
Control software
99501 No such resource file
Eeoelale7414 Resource file does not exist.
[Code]
Project ID
[Probable Fault Cause]
Control software
99502 Resource file closed, not opened
Eeoelale7415 Resource file is closed.
[Probable Fault Cause]
Control software
99503 Resource file already opened
Eeoelale7416 Resource file is already open.
[Code]
Project ID
[Probable Fault Cause]
Control software
99504 No more resource files
Eeoelale7417 No more resource files can be opened.
[Code]
Project ID
[Probable Fault Cause]
Control software
99505 Resource conversion type ID mismatch
Eeoelale7418 Resource type conversion failure.
[Character-string]
“STR”: Conversion to character-string type.
“RESRCARRAY”: Conversion to resource array type
“STRARRAY”: Conversion to string array type
“REALARRAY”: Conversion to real array type
“INTARRAY”: Conversion to integer array type
“SINTARRAY”: Conversion to short integer array type
“BYTEARRAY”: Conversion to byte array type
[Probable Fault Cause]
Control software
99506 String is not a number
Eeoelale7419 String value conversion failure.
[Character-string]
Specified character-string
[Probable Fault Cause]
Control software
99507 Unknown message box
Eeoelale7420 The destination of the message sent from the remote server is not a message box.
[Code]
Destination resource ID
[Probable Fault Cause]
Control software
99508 Failed to initialize MUTEX
Eeoelale7421 MUTEX initialization failure.
[Character-string]
Function name
[Code]
MUTEX resource ID
[Probable Fault Cause]
Control software
99509 Failed to lock MUTEX
Eeoelale7422 MUTEX locking failure.
[Character-string]
Function name.
[Code]
MUTEX resource ID
[Probable Fault Cause]
Control software
99510 Failed to unlock MUTEX
Eeoelale7423 MUTEX unlocking failure.
[Character-string]
Function name
[Code]
MUTEX resource ID
[Probable Fault Cause]
Control software
99511 resfile_def: Resource file already exists
Eeoelale7424 The resource file to be created already exists.
[Code]
Project ID.
[Probable Fault Cause]
Control software
99512 ittask_ creation failed
Eeoelale7425 Thread initialization failed.
[Character-string]
“TOO MANY”: Too many threads.
“OS ERROR”: Thread creation error.
[Code]
Thread resource ID
[Probable Fault Cause]
Control software
99513 Thread not initialized, cannot run
Eeoelale7426 Thread cannot be started because it is not initialized.
[Code]
Thread resource ID
[Probable Fault Cause]
Control software
99514 Thread start failed
Eeoelale7427 Thread start failed.
[Character-string]
ittask start function return value
[Code]
Thread resource ID
[Probable Fault Cause]
Control software
99515 pipe_get: Illegal image packet
Eeoelale7428 The correct image code is not recorded in the data header received through the pipe.
[Code]
Received image code.
[Probable Fault Cause]
Control software
99517 pipe_put: Packet too large
Eeoelale7429 Received packet size exceeds buffer capacity.
[Code]
Received packet size.
[Probable Fault Cause]
Control software
99518 EFRPC channel not specified for project
Eeoelale7430 Project executes remote procedure call, but no server is specified for remote procedure call.
[Code]
Project ID
99519 efrpc_open: Illegal channel type
Eeoelale7431 Unsupported channel type is specified.
Pipe or socket can generally be specified as communication channel. However, depending on the environment, you cannot specify both of them or either of them.
Another possibility is a channel type other than those specified above.
[Code]
Code indicating specified channel type
99520 efrpc_clnt: MUTEX error
Eeoelale7432 In efrpc open function, efrpc call function, efrpc reserve function or efrpc release channel function.
[Character-string]
“init”: MUTEX initialization failure.
“lock”: MUTEX lock error.
“unlock”: MUTEX unlock error.
[Code]
PPXXXX
PP: Process or channel ID
XXXX: Return value of sysexl_preset, sysexl_lock, or sysexl_unlock function.
99521 efrpc_call: Unknown VARSIG in argument
Eeoelale7433 An unknown variable identifier was specified when an argument was converted into a packet on the client side of the remote procedure call.
[Code]
Method or function ID
[Probable Fault Cause]
Control software
99522 efrpc_call: Unknown dedicated packet
Eeoelale7434 An unexpected dedicated packet was returned from the server during a remote procedure call.
[Code]
ID of the returned dedicated packet
[Probable Fault Cause]
• Control software
• Communication program error.
• Control software version mismatch between client and server.
99523 efrpc_call: Returned unknown VARSIG
Eeoelale7435 The value identifier returned from the server differs from that requested by the client, or an unspecified value identifier was returned.
[Character-string]
“Mismatch”: The value identifier returned from the server differs from that requested by the client.
None: An unspecified value identifier was returned.
[Code]
Function or method ID
99524 efrpc_check_message: Unexpected packet type
Eeoelale7436 A dedicated packet other than a message was received when a message should have been received.
[Code]
Code identifying the dedicated packet
[Probable Fault Cause]
Control software
99525 efrpc_check message: VARSIG mismatch
Eeoelale7437 The received message variable identifier is an unexpected value.
Normally, a message composed of integer, byte, character string, and character string array and its variable identifier is 065B, hexadecimal.
[Code]
Received variable identifier
[Probable Fault Cause]
Control software
99526 Illegal channel ID
Eeoelale7438 An incorrect channel ID was specified while calling the following functions:
efrpc_open, efrpc_send_break, efrpc_set_command, efrpc_reserve_channel, efrpc_try_reserve_channel,
efrpc_unreserve_channel, efrpc_close, efrpc_trap, efrpc_connect, efrpc_wait_connect, efrpc_service,
efrpc_send_message, efrpc_check_message_send, efrpc_check_break
[Character-string]
Function name
[Code]
Channel ID specified as an argument
99527 efrpc_put: Unread data remains
Eeoelale7439 Data transfer was attempted even though unread data remained in the efrpc_put function.
[Character-string]
Function name
99528 Insufficient RPC packet
Eeoelale7440 Insufficient data was received, or more than required was requested in the efrpc_get function.
[Character-string]
Function name
99529 EFRPC: Channel already opened
Eeoelale7441 The efrpc_open or efrpc_connect function attempted to reopen an already opened remote procedure call channel.
[Character-string]
Function name
[Code]
Channel ID
[Probable Fault Cause]
Control software
99530 efrpc_bind: Illegal channel type
Eeoelale7442 An unsupported type was specified in the efrpc_bind function.
Pipes or sockets can usually be specified for communication channels. Depending on the environment, however, neither or only one of them can be specified.
Another possibility is a channel type other than those specified above.
[Code]
Code indicating channel type
99531 efrpc_bind: Channel not bound
Eeoelale7443 An attempt was made to connect from a client to a channel that is not open, is already connected to a client, or is opened as a client.
[Code]
Channel ID
[Probable Fault Cause]
Control software
99532 efrpc_bind: Channel not connected
Eeoelale7444 Service was attempted for a channel not yet connected to a client.
[Code]
Channel ID
[Probable Fault Cause]
Control software
99533 efrpc_service: Unknown dedicated RPC
Eeoelale7445 An unspecified dedicated packet was sent from the client.
[Code]
Code identifying the dedicated packet
[Probable Fault Cause]
Control software
99534 efrpc_service: Unknown VARSIG in argument
Eeoelale7446 An unspecified value identifier was used for the argument identifier sent from the client.
[Code]
Method or function ID
[Probable Fault Cause]
Control software
99535 efrpc_service: Returned unknown VARSIG
Eeoelale7447 An unspecified variable identifier was used as the return value type requested by the client.
[Code]
Method or function ID
[Probable Fault Cause]
Control software
99536 efrpc_open: Cannot get host information
Eeoelale7448 Failed to convert the host name to an IP address when connecting to the EBIFRY RPC channel.
[Character-string]
Host name to connect
99537 efrpc_open: Cannot open socket
Eeoelale7449 The socket channel could not be opened when connecting to EBIFRY RPC.
[Code]
Error value of socket function
99538 efrpc_open: Cannot connect socket
Eeoelale7450 The socket could not be connected to the host when connecting to EBIFRY RPC.
[Code]
Error value of connect function
99539 socket_get: Header read error
Eeoelale7451 Failed to read the header on the EFRPC socket channel.
This error also occurs when the connected socket is closed.
[Code]
Error value of read function
99540 socket_get: External host may be closed
Eeoelale7452 Zero bytes of data were read when reading data from the socket.
The connected system may have closed the socket.
[Code]
Error value at that moment
99541 socket_get: Illegal image packet code
Eeoelale7453 The image packet code read from the socket was an unexpected image code.
[Code]
Read image code
99542 socket_get: Packet buffer too small
Eeoelale7454 The size of the packet sent from the connected socket exceeds the packet buffer size.
[Code]
Packet buffer size
99543 socket_get: Read error
Eeoelale7455 An error occurred when reading data from the socket.
[Code]
Error value of read function
99544 socket_get: Checksum error
Eeoelale7456 The checksum of the data received from the socket does not match.
Normally, checksums are not calculated in communication with the EBIFRY RPC socket.
[Code]
Socket descriptor that caused this error
99545 socket_put: Packet size too large
Eeoelale7457 The size of the packet sent through the socket is too large.
[Code]
Size of packet to be sent
99546 socket_put: Header write error
Eeoelale7458 An error occurred when sending the packet header to the socket.
[Code]
Error value of write function
99547 socket_put: External host may be closed
Eeoelale7459 Zero bytes of data were written when writing data to the socket. The connected system may have closed the socket.
[Code]
Error value at that moment
99548 socket_put: Write size error
Eeoelale7460 Failed to write data to the socket.
[Code]
Error value of write function
99549 socket_bind: WSA startup failed (Win32)
Eeoelale7461
This error occurs only in a Windows NT environment (it does not occur in the E100 system).
Failed to call WSAStartup function.
99550 socket_bind: Cannot create socket
Eeoelale7462 The server failed to create a socket.
[Code]
Error value of socket function
99551 socket_bind: Failed to bind port
Eeoelale7463 Failed to assign a port number to the socket.
[Code]
Error value of bind function
[Probable Fault Cause]
Control software
99553 efrpc_call: Illegal recursive call
Eeoelale7464 While waiting for a remote procedure call, the program attempted to make another remote procedure call.
[Code]
Method or function ID that attempted to make a remote procedure call
[Probable Fault Cause]
Control software
99554 efrpc_unreserve: Channel not reserved
Eeoelale7465 An attempt was made to call the efrpc_unreserve function for a channel that is not reserved for use.
[Character-string]
Function name
[Code]
Channel ID
[Probable Fault Cause]
Control software
99555 Array subscript out of GET range
Eeoelale7466 The array subscript is out of range.
[Character-string]
“BYTE”: Byte array.
“SINT”: Short integer array.
“INT”: Integer array.
“REAL”: Real number array.
“RESRCARRAY”: Resource array.
[Code]
Subscript
[Probable Fault Cause]
Control software
99556 Array index out of SET range
Eeoelale7467 Array index is out of range.
[Character-string]
“BYTE”: Byte array.
“SINT”: Short integer array.
“INT”: Integer array.
“REAL”: Real number array.
“RESRCARRAY”: Resource array.
[Code]
Index
[Probable Fault Cause]
Control software
99557 Null ID
Eeoelale7468 The specified resource or array does not exist.
[Character-string]
Function name
[Code]
None (if character-string is ridw_adr)
Index (if character-string is ridw_adr)
[Probable Fault Cause]
Control software
99558 Illegal project ID
Eeoelale7469 An invalid project ID is specified.
The specified resource ID contains an invalid project ID.
[Character-string]
Function name
[Code]
If character-string is not ridw_adr: then
PP: Project ID.
If character-string is ridw_adr: then
PPCCLLLL: Resource ID.
PP: Project ID.
[Probable Fault Cause]
Control software
99559 Illegal category ID
Eeoelale7470 The specified resource ID contains an invalid category ID.
[Character-string]
Function name
[Code]
PPCCLLLL: Project ID.
PP: Project ID.
CC: Category ID.
LLLL: Local ID.
[Probable Fault Cause]
Control software
99560 Illegal local ID
Eeoelale7471 The specified resource ID contains an invalid local ID.
[Character-string]
Function name
[Code]
Resource ID
[Probable Fault Cause]
Control software
99561 Illegal type ID
Eeoelale7472 Failed to disconnect resource. The resource type ID is invalid.
[Character-string]
Function name
[Code]
Resource ID
[Probable Fault Cause]
Control software
99562 Unavailable ID
Eeoelale7473 An unavailable resource ID was specified.
[Character-string]
Function name
[Code]
Resource ID
[Probable Fault Cause]
Control software
99563 ID specifies function/method
Eeoelale7474 An invalid resource ID was specified. The specified ID represents a function or method.
[Character-string]
Function name
[Code]
Resource ID
[Probable Fault Cause]
Control software
99564 Insufficient memory
Eeoelale7475 Available memory area is insufficient.
[Character-string]
Function name
[Code]
Project ID
[Probable Fault Cause]
Control software
99565 Insufficient resource table entries
Eeoelale7476 Free space in resource table entries is insufficient.
[Character-string]
Function name
[Code]
Project ID
[Probable Fault Cause]
Control software
99566 Failed to obtain virtual memory
Eeoelale7477 Failed to secure virtual memory space.
[Character-string]
Function name
[Code]
Project ID
[Probable Fault Cause]
Control software
99567 Cannot open file (write)
Eeoelale7478 Failed to open file in write mode.
[Character-string]
Function name.
[Code]
Project ID
[Probable Fault Cause]
Control software
99568 Cannot open file (read)
Eeoelale7479 Failed to open file in read mode.
[Character-string]
Function name
[Code]
Project ID
[Probable Fault Cause]
Control software
99569 Cannot obtain file status
Eeoelale7480 Failed to obtain file information.
[Character-string]
Function name
[Code]
Project ID
[Probable Fault Cause]
Control software
99571 Project already exists
Eeoelale7481 The specified project already exists.
[Character-string]
Function name
[Code]
Project ID
[Probable Fault Cause]
Control software
99572 Resource too large
Eeoelale7482 The size of the created resource is too large.
[Character-string]
Function name
[Code]
Project ID
[Probable Fault Cause]
Control software
99573 Corrupted external resource file
Eeoelale7483 The specified external resource file contains invalid data.
[Character-string]
Function name
[Code]
Project ID
[Probable Fault Cause]
Control software
99575 resFile_create_resrc: Resource type ID is empty
Eeoelale7484 The resource type ID is empty.
[Character-string]
Function name
[Code]
Project ID
[Probable Fault Cause]
Control software
99577 resFile_ext: Not a resource file
Eeoelale7485 An invalid resource file was specified.
[Character-string]
Function name
[Code]
Project ID
[Probable Fault Cause]
Control software
99578 Coerced dialog format resource file
Eeoelale7486 An invalid resource file was specified.
[Character-string]
Function name
[Code]
Project ID
[Probable Fault Cause]
Control software
99579 Old EBIFRY format resource file
Eeoelale7487 An invalid resource file was specified.
[Character-string]
Function name.
[Code]
Project ID
[Probable Fault Cause]
Control software
99580 Unrecognized format resource file
Eeoelale7488 An invalid resource file was specified.
[Character-string]
Function name
[Code]
Project ID
[Probable Fault Cause]
Control software
99581 resfile_ext: Cannot process code type
Eeoelale7489 Character code that cannot be processed is included in the specified resource file.
[Character-string]
Function name
[Code]
Project ID
[Probable Fault Cause]
Control software
99582 Illegal operation on static resource file
Eeoelale7490 An attempt was made to perform invalid processing on a static resource file.
[Character-string]
Function name
[Code]
Project ID
[Probable Fault Cause]
Control software
99583 Illegal operation on read-only resource file
Eeoelale7491 An attempt was made to perform invalid processing on a write-protected resource file.
[Code]
Project ID
[Probable Fault Cause]
Control software
99584 resrc_ref_count: Reference counter overflow
Eeoelale7492 An overflow occurred in the resource reference counter.
[Character-string]
Function name
[Code]
Resource ID
[Probable Fault Cause]
Control software
99585 resrc_ref_count: Unavailable resource
Eeoelale7493 An unavailable resource was specified.
[Code]
Resource ID
[Probable Fault Cause]
Control software
99586 resrc_change_size: No more memory
Eeoelale7494 Failed to change the resource size because memory is insufficient.
[Code]
Resource ID
[Probable Fault Cause]
Control software
99587 resrc: Dynamic resource has memory map
Eeoelale7495 Failed to disconnect resource
[Code]
Resource ID
[Probable Fault Cause]
Control software
99589 func_adr: No such function ID
Eeoelale7496 A non-existent function was used.
[Code]
Function ID
[Probable Fault Cause]
Control software
99590 method_adr: No such method ID
Eeoelale7497 A non-existent method was used.
[Code]
Method ID
[Probable Fault Cause]
Control software
99591 Method type ID mismatch
Eeoelale7498 The method type ID does not match.
[Character-string]
Method name.
[Code]
Method type ID
[Probable Fault Cause]
Control software
99592 push_vm: Too many nestings
Eeoelale7499 The number of nestings exceeded its limit.
[Probable Fault Cause]
Control software
99595 No exception event caught
Eeoelale7500 Exception handler routine was not opened.
After dumping the EBIFRY stack to the console area, starting the process from address Oxbad00bad stops the system that caused the address exception.
[Probable Fault Cause]
Control software
99596 Illegal code set
Eeoelale7608 An invalid character code set was specified.
[Character-string]
Specified character code set
[Probable Fault Cause]
Control software
99600 Too many open files
Eeoelale7501 No more files can be opened. The total number of files that can be opened at a time is 4.
[Character-string]
Specified file name
[Measures to Take]
Wait until another file operation is completed. Close the file under direct edit (or file list).
99601 File (device) in use
Eeoelale7502 A new file operation cannot be started because input/output operation of another file is in progress.
[Character-string]
File name or device name for which file operation was rejected
[Measures to Take]
Wait until another file operation is completed. Close the file under direct edit (or file list).
99602 File (device) in use
Eeoelale7503 A new file operation (read) cannot be started because input/output operation of another file is in progress.
[Character-string]
File name that could not be operated
[Measures to Take]
Wait until another file operation is completed. Close the file under direct edit (or file list).
99603 Cannot open file
Eeoelale7504 Failed to open the file.
[Character-string]
File name of the file that could not be opened
[Measures to Take]
If the file is protected, cancel the protection.
99604 File operation failure (block insertion)
Eeoelale7505 Failed to write the file (block) in direct edit mode.
[Character-string]
File name being operated
[Code]
Position or size of the block attempted to be inserted
[Probable Fault Cause]
Free space on the device has run out.
[Measures to Take]
End direct edit, delete unnecessary files to free up more space, and then start editing again.
99605 File operation failure (move)
Eeoelale7506 Failed to modify the file pointer during file direct edit or large file listing.
[Character-string]
File name to be operated
[Code]
Position to which the file pointer moved (block number)
99606 File operation failure (position access)
Eeoelale7507 Failed to obtain the pointer during file direct edit or large file listing.
[Character-string]
File name being operated.
99607 File operation failure (block deletion)
Eeoelale7508 Failed to delete the block during direct edit.
[Character-string]
File name being operated
99608 File operation failure (get block capacity)
Eeoelale7509 Failed to obtain block capacity for file direct edit or large file listing.
[Character-string]
File name being operated
99609 File read failure
Eeoelale7510 Failed to read data from the file.
[Character-string]
File name being operated
99610 File operation failure (block write)
Eeoelale7511 Failed to write data to the file.
[Character-string]
File being operated.
99611 Too many open directories
Eeoelale7512 No more directories can be opened. The total number of directories that can be opened at a time is 4.
[Character-string]
Directory name being operated
[Measures to Take]
Wait until the current directory operation is completed.
99612 Directory (device) in use
Eeoelale7513 Directory operation cannot be started because input/output of another file is in progress.
[Character-string]
Directory name being operated
[Measures to Take]
Wait until another file/directory operation is completed.
99613 Too many open printers
Eeoelale7514 No more printers can be opened. The total number of printers that can be opened at a time is 4.
[Character-string]
Name of printer device to be opened
99614 Printer open failure
Eeoelale7515 Failed to open the printer.
[Character-string]
Printer device name.
99615 Invalid printer filter specified
Eeoelale7516 An invalid printer filter was specified.
[Character-string]
Printer device name
[Code]
Specified filter code
99616 Character string printout failure
Eeoelale7517 Failed to output the character string to the printer.
[Character-string]
Printer device name
99617 Data printout failure
Eeoelale7518 Failed to output data to the printer.
[Character-string]
Printer device name
99618 Printer close failure
Eeoelale7519 Failed to close the printer.
This error usually occurs when the form feed code cannot be output.
[Character-string]
Printer device name.
[Code]
None: Test method.
1: Normal.
99619 File copy operation canceled
Eeoelale7520 File copy operation was interrupted (canceled) during copying.
This is not an error.
The copy destination file is deleted.
[Character-string]
Copy source file name
99620 Illegal device initialization
Eeoelale7521 Cannot initialize the specified device.
[Character-string]
Device name
99621 Invalid device specified for memory condensation
Eeoelale7522 Cannot condense the specified device memory.
[Character-string]
Device name
99640 Invalid format for initialization
Eeoelale7523 The specified format is not applicable.
[Character-string]
Device name
99650 File cannot be protected
Eeoelale7524 The specified file has a high protection level, such as a system program, and cannot be a target of protection.
[Character-string]
File name that caused this error
[Measures to Take]
Do not specify a file for which protection is not allowed.
99651 Write-protect
Eeoelale7525 An attempt was made to write to or delete a write-protected file.
[Character-string]
File name that caused this error.
[Measures to Take]
• Create a file with another file name.
• Cancel the file protection.
99652 Invalid file number
Eeoelale7526 An invalid file number was specified.
[Character-string]
File name that caused this error
[Probable Fault Cause]
Control software
99653 Invalid file attribute
Eeoelale7527 An invalid file attribute was specified.
[Character-string]
File name that caused this error
[Probable Fault Cause]
Control software
99654 Invalid device name
Eeoelale7528 An invalid device name was specified.
[Character-string]
File name (device name) that caused this error.
[Probable Fault Cause]
• Device name is misspelled.
• Specified device name is not allowed for the operation.
[Measures to Take]
Specify the correct device name.
99655 Invalid directory pointer
Eeoelale7529 The directory pointer is invalid.
[Character-string]
File name (directory name) that caused this error
[Probable Fault Cause]
Control software
99656 Invalid file name
Eeoelale7530 An invalid file name (device name) was specified.
[Character-string]
File name (device name) that caused this error
[Probable Fault Cause]
• File or directory name is misspelled.
• Specified file or device name is not allowed for the operation.
[Measures to Take]
Specify the correct file name.
99657 Invalid file pointer
Eeoelale7531 The file pointer is invalid.
[Character-string]
File name that caused this error
[Probable Fault Cause]
Control software
99658 Too many open directories
Eeoelale7532 No more directories can be opened. The total number of directories that can be opened at a time is 4.
[Character-string]
File name (directory name) that caused this error.
[Measures to Take]
Wait until another directory operation is completed.
99659 Too many open files
Eeoelale7533 No more files can be opened. The total number of files that can be opened at a time is 4.
[Character-string]
File name that caused this error
[Measures to Take]
• Wait until another file operation is completed.
• Close the file under direct edit (or file list).
99660 Directory not found
Eeoelale7534 The specified directory does not exist.
[Character-string]
File name (directory name) that caused this error
[Probable Fault Cause]
Directory name is misspelled.
[Measures to Take]
Specify the correct directory name.
99661 File not found
Eeoelale7535 A nonexistent file was specified.
[Character-string]
File name that caused this error
[Probable Fault Cause]
File name is misspelled.
[Measures to Take]
Specify the correct file name.
99662 Insufficient storage space
Eeoelale7536 There is not enough free space to create files and directories.
[Character-string]
File name [directory name] that caused this error
[Measures to Take]
• Delete unnecessary files.
• Initialize the device.
99663 Device mismatch before and after change
Eeoelale7537 In a rename operation, the device specified by the old file name is different from the device specified by the new file name.
[Character-string]
(File name before rename)-> (File name after rename)
[Probable Fault Cause]
Device name is misspelled.
[Measures to Take]
Specify the correct device.
99664 File or directory already exists
Eeoelale7538 The specified file or directory already exists.
[Character-string]
File name (directory name) that caused this error
[Probable Fault Cause]
File or directory name is misspelled.
[Measures to Take]
• Specify another name.
• Delete or rename existing files or directories.
99665 Invalid directory name
Eeoelale7539 An invalid directory name was designated.
[Character-string]
File name (directory name) causing this error
[Probable Fault Cause]
Misspelling of directory name.
[Measures to Take]
Designate a correct directory name.
99666 Not MS-DOS format.
Eeoelale7540 Designated device is not in MS-DOS format.
[Character-string]
File name (directory name) causing this error
[Probable Fault Cause]
• A floppy disk of non-MS-DOS format (OSP format) is set in the floppy disk drive.
• Misspelling of device name.
[Measures to Take]
• Replace the floppy disk with an MS-DOS-formatted floppy disk.
• Designate a correct device name.
99667 Directory not empty
Eeoelale7541 The designated directory is not empty.
[Character-string]
File name (directory name) causing this error
[Probable Fault Cause]
Misspelling of directory name.
[Measures to Take]
• Empty the directory.
• Designate a correct directory name.
99668 Root directory cannot be deleted
Eeoelale7542 Attempted to delete the root directory.
[Character-string]
File name (directory name) causing this error
[Probable Fault Cause]
Misspelling of file or directory name.
[Measures to Take]
Designate a correct file or directory name.
99669 Directory in path name does not exist
Eeoelale7543 An element of the designated file or directory path structure is not a directory.
[Character-string]
File name (directory name) causing this error
[Probable Fault Cause]
Misspelling of file or directory name.
[Measures to Take]
Designate a correct file or directory name.
99670 Invalid file name.
Eeoelale7543 A non-ASCII character was designated for a DNC-DT file name.
[Character-string]
Error in designated file name.
[Probable Fault Cause]
The designated file name to be renamed, copied, or edited contains a non-ASCII character.
[Measures to Take]
Name the file using ASCII characters only.
99671 Directory deletion failed
Failed to delete directory.
[Character-string]
Full path of the designated directory.
99672 Directory copy failed
Failed to copy directory.
[Character-string]
Full path of the designated directory.
[Code]
9: Attempted to copy beyond the maximum hierarchy level that can be copied.
99673 Invalid parameter(file name).
The file name is invalid according to the OSP file naming rules.
99674 Can not operate except text files.
Attempted to edit a non-text file in program operation mode.
99675 Floppy disc read/write.
Reading from or writing to the floppy disk was not completed successfully.
99676 Floppy disc access sector over.
Attempted to access a sector that does not exist.
99677 Floppy ready.
Floppy disk is not ready.
99678 Floppy disc write protect.
Cannot write to floppy disk.
99679 Different devices.
Different devices were designated before and after renaming.
[Character-string]
(File name before change) ->(File name after change)
[Probable Fault Cause]
Misspelling of device name.
99680 Invalid device name.
An incorrect device name was designated.
[Character-string]
File (device) name where the error occurred
[Probable Fault Cause]
1) Misspelling of device name.
2) The device name is not allowed to be designated for operation.
99681 Invalid file name.
An incorrect file (device) name was designated.
[Character-string]
File (device) name where the error occurred
[Probable Fault Cause]
1) Misspelling of file name or directory name.
2) The file name or device name is not allowed.
99682 Device full.
There is not enough space to create a file or directory.
If the maximum number of files that can be stored in the root directory is reached, an error will occur even if there is enough space on the DOS (FAT) format floppy disk.
[Character-string]
File (directory) name where the error occurred
99683 Windows error
Windows returned an error.
[Character-string]
Windows return error message.
[Probable Fault Cause]
The cause of the error varies depending on the error message returned by Windows.
1) Not allowed. ’file name’
– Files under the device or copy directory are protected.
– Exceeded the file storage range under the root directory of the copy destination device.
2) No space left in device. ’file name’
– No space left in device to copy or store data.
3) No such file or directory. ’file name’
– The designated file was not found.
99684 Device not ready.
The designated device is not ready for use.
[Character-string]
Device name
[Probable Fault Cause]
• When the device name is US0: or US1:, the USB storage device is not mounted, or the USB storage device was removed after the USB removal procedure.
• When the device name is FD0:, the built-in floppy disk drive was inadvertently removed via the USB device removal procedure.
• The USB storage device cannot be recognized properly.
[Measures to Take]
• When the device name is US0: or US1:, mount the USB storage device again.
• When the device name is FD0:, turn on the power again.
• Restart the USB device by pressing the [USB Restart] key or [F7] (USB Restart) in the vertical function diagnostic keys. (OSP-P200A only)
99685 The protection file exists under the directory.
The directory cannot be deleted because protected files exist under this directory.
[Character-string]
Protected file name (including path name)
99686 The protection directory exists under the directory.
The directory cannot be deleted because protected directories exist under the designated directory.
[Character-string]
Protected directory name (including path name)
99700 Binary file cannot be edited/displayed
Eeoelale7544 A binary file was designated for direct editing or listing.
Attempted to append a binary file during direct file editing.
[Character-string]
Designated file name
[Probable Fault Cause]
• A binary file was designated for direct editing or listing.
• Attempted to append a binary file during direct file editing.
99701 Direct edit disabled
Eeoelale7545 The file attempted to be edited exceeds the edit buffer capacity.
[Character-string]
Designated file name
[Probable Fault Cause]
Attempted to directly edit a file exceeding the edit buffer capacity in lathe program or normal program edit mode.
99703 Designated file is being edited or displayed
Eeoelale7546 The file designated for editing is currently being edited or listed.
The file attempted to be saved under the same file name is currently being edited or listed.
[Character-string]
Designated file name
[Code]
1: The text editor cannot write to a file that is being edited or listed in another operation.
[Probable Fault Cause]
The same file is being edited or listed by more than one file operation at the same time.
99704 Copy or delete disabled while editing other file.
Eeoelale7547 The same file is being copied or deleted by another file operation. (Conversely, when a file is being used in another file operation, it cannot be copied or deleted.)
[Probable Fault Cause]
The file is being copied or deleted by another file operation.
[Measures to Take]
Complete the copy or delete operation in the other file operation.
99705 Input data overflow
Eeoelale7548 Input data is too large or too small.
A real number other than an integer was entered in an integer field.
Input data contains characters other than numeric characters (such as letters).
[Character-string]
Input character-string
[Code]
7: Out of setting range.
63: The set value does not have such a data type.
[Probable Fault Cause]
Operation error
[Measures to Take]]
Enter a value within the setting range.
99706 Internal error.
Eeoelale7547 An error occurred during internal processing of the control software.
[Code]
1: Failed to hide the designated foreground screen.
B: Failed to insert a character-string when editing file (text editor).
C: Failed to insert a character-string when editing file (text editor).
[Probable Fault Cause]
Control software
99780 Cannot create GC
Eeoelale7549 Cannot create GC (graphics context).
[Code]
GRAFPORT resource ID
[Probable Fault Cause]
Control software
99781 Cannot create image
Eeoelale7550 Cannot create image.
[Probable Fault Cause]
Control software
99782 Cannot create window
Eeoelale7551 Cannot create window.
[Code]
Window resource ID
[Probable Fault Cause]
Control software
99783 Failed to initialize text editor
Eeoelale7552 Text editor initialization failed.
[Code]
Text editor resource ID
[Probable Fault Cause]
Control software
99784 File name mismatch
Eeoelale7553 The file name being edited does not match the file name saved in direct edit mode.
[Character-string]
File name in direct edit mode
[Probable Fault Cause]
Control software
99785 Illegal logger file format
Eeoelale7554 An invalid logger file was designated.
[Character-string]
Character-string in the raw logger file designated for the first time.
[Probable Fault Cause]
Control software
99786 Logger file includes unknown record
Eeoelale7555 Designated logger file includes an unknown record.
[Code]
Unknown record number.
[Probable Fault Cause]
Control software
99787 No such registration path
Eeoelale7556 Designated registration path does not exist.
[Character-string]
Registration path
99788 Not a registration key
Eeoelale7557 A registration entry is included in part of the registration path, or a registration entry with the same name already exists.
[Character-string]
Registration path
[Probable Fault Cause]
Control software
99789 Not a registration entry
Eeoelale7558 A registration key with the same name as the registration key to be created already exists, or a registration key was designated instead of a registration entry.
[Character-string]
Registration path
[Probable Fault Cause]
Control software
99790 Registration depth too deep
Eeoelale7559 Registration path exceeds the maximum number of hierarchy levels.
[Character-string]
Registration path
[Probable Fault Cause]
Control software
99791 Sequence number overflow
Eeoelale7609 When assigning sequence numbers, the sequence number became 4 digits or more.
[Code]
Sequence number to be assigned (hexadecimal)
[Probable Fault Cause]
• There are many sequence numbers to be assigned.
• Sequence number increment value is too large.
[Measures to Take]
Taking into account the sequence numbers to be assigned, designate the starting sequence number and increment value.