OSP-U10L Chapter 3 Alarm P-1

LC37-003 P-19
SECTION 3 ALARM P

0721 Local area network error
Eeoelale2110 An abnormality occurred in the local area network.
[Index]
None
[Character-string]
CH* SC$
*: Channel number where abnormality occurred
$: Sequence counter
[Code]
XXYYZZZZ
XX: MacID of slave station where abnormality occurred
YY: Slave station XX error status
0x00: Normal or nonexistent slave station
0x46: Duplicate MacID error
0x48: Communication clogging
0x49: Identification data does not match scan list
0x4D: Data size does not match scan list
0x4E: No response in connection check
0x4F: Other slave station not on network
0x50: Idle state
0x53: Error received in connection check
0x54: Timeout in connection check
v0x6 : Transition to idle mode
0x5B: Bus off
0x5C: Network power supply off
(If the error is not caused by a slave station, such as a communication delay, XXYY becomes 0xFFFF.)
ZZZZ: Scanner error status
Bit 0: Memory check error (during memory initialization)
Bit 1: Scan list initialization error
Bit 2: Scan list mismatch error (MacID)
Bit 3: Scan list mismatch error (input data)
Bit 4: Scan list mismatch error (output data)
Bit 5: Duplicate MacID error
Bit 6: Network power supply status error
Bit 7: Memory parity error
Bit 8: Input data reception error (unidirectional)
Bit 9: Input data reception error (bidirectional)
Bit 10: Output data transmission error (unidirectional)
Bit 11: Output data transmission error (bidirectional)
Bit 12: Slave station communication delay error (unidirectional)
Bit 13: Slave station communication delay error (bidirectional)
Bit 14: Bus off
Bit 15: Diagnostic information access error
[Probable Fault Cause]
Hardware failure
Software failure
0722 FCP board error
Eeoelale2111 FCP board is in an abnormal state.
[Character-string]
AAAABB
AAAA: Name of task being executed
BB: Program module being executed
[Code]
VWXXYYZZ
V=1 indicates FCP-DN board
W=0
XXYYZZ is identical to the code displayed for Alarm P809.
W=1 indicates OS error.
XX=00 PLT0 task
XX=01 PLT1 task
LC37-003 P-20
SECTION 3 ALARM P
XX=09 PLSY task
XX=10 PLR2 task
XX=20 PLR3 task
YYZZ= (Description)
YYZZ=0001 Task forced abort failed
YYZZ=0002 Task startup failed
YYZZ=0003 Task restart failed
YYZZ=0004 Task restart failed within 1.6 ms wait time
W=2 indicates memory check error
XXYYZZ indicates start address of check area.
0723 I/O data set file read
Eeoelale2112 NC failed to read I/O data set file.
[Code]
I/O data set file load status (hexadecimal).
2-> File open error (no file).
3-> File read error (no data).
4-> File attribute error (not 'PBU1' file).
5-> File close error.
6-> File size error (smaller).
7-> File size error (larger).
100-> Machine model error for PLC.
200-> PLC level error.
300-> File version error.
0800 Spindle D/A control data file read failure
Eeoelale2001 NC cannot normally read spindle D/A control data file.
[Code]
XY
X: Gear range number (first gear range number where error occurred; X does not appear when Y=1 to 6.)
Y=1-> No data file
Y=2-> Data file type is not PBU1.
Y=3-> Data file size is too large.
Y=4-> Data file size is inappropriate.
Y=5-> Number of gear ranges and data file size do not match.
Y=6-> Gear range number is other than 1 to 4.
Y=7-> Motor limit speed or spindle limit speed setting is zero.
Y=8-> Spindle maximum speed setting is zero.
[Probable Fault Cause]
Error during spindle D/A control data file generation
[Measures to Take]
Create a correct spindle D/A control data file.
0801 TCP/IP board error
Eeoelale2002 A CPU error occurred on the TCP/IP board during operation of DNC-T1, T2, T3, or DT function.
[Index]
None
[Character-string]
None
[Code]
XXYYZZ
XX… Board operating status represented in hexadecimal
Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0
RUN HALT CPUOFF 0 SNMI 0 0 0
YY… Bus error status represented in hexadecimal
Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0
0 0 0 0 PROT DAI LOOP ECC
ZZ… Always 0
LC37-003 P-21
SECTION 3 ALARM P
[Probable Fault Cause]
TCP/IP board hardware failure
Firmware error on TCP/IP board
0802 Installation information file not found
Eeoelale2003 The user software generation system cannot find installation information file matching specification code.
Or the file described in the installation information file is not found.
[Character-string]
File name in question
[Probable Fault Cause]
Error during software installation
Error during software generation
Or specification code error
[Measures to Take]
Reinstall software or regenerate installation floppy disk.
0803 File installation error
Eeoelale2004 The user software generation system cannot find software matching specification code.
[Character-string]
Software file name in question
[Code]
1-> Ended without loading any character files.
3-> File ended during file loading.
9-> Device name setting error
10-> File name setting error
11-> File does not exist. 11 or FFFFFFFF
[Probable Fault Cause]
Error during software installation
Error during software generation
Specification code error
[Measures to Take]
Reinstall or regenerate control floppy disk.
0804 MSB file mismatch
Eeoelale2005 The MSB file for IMAP-B and conversational program B does not satisfy NC software requirements.
[Code]
1-> MSB file for IMAP-B and conversational program B is incompatible with NC software.
[Measures to Take]
Use an MSB file of version B or higher to run IMAP-B or conversational program B.
0805 MOP-TOOL parameter PBU file loading error
Eeoelale2006 The backup file (MMTUB*.PBU) is not found, or its type or size is incorrect.
[Code]
1-> Parameter PBU file (MMTUB*.PBU) is not in MD0:.
2-> Parameter PBU file (MMTUB*.PBU) does not start with "PBU1" or file length is inappropriate (not $18 sectors).
[Probable Fault Cause]
If the alarm occurs during NC operation, the PBU file might have been deleted or corrupted.
If the alarm occurs before the NC runs after control floppy disk installation, the PBU file type might be incorrect or it might not be stored in memory.
[Measures to Take]
If the alarm occurs during NC operation, reinstall control floppy disk.
LC37-003 P-22
SECTION 3 ALARM P
If the alarm occurs before the NC runs, create a correct control disk.
0806 MOP-TOOL tool data PBU file read error
Eeoelale2007 The backup file (MMTUA*.PBU) is not found, or its type or size is incorrect.
[Code]
3-> Tool data PBU file (MMTUB*.PBU) is not found in MD0.
4-> Tool data PBU file (MMTUB*.PBU) does not start with "PBU1" or file length is inappropriate (not $125 sectors).
[Probable Fault Cause]
If the alarm occurs during NC operation, the PBU file might have been deleted or corrupted.
If the alarm occurs before the NC runs after control floppy disk installation, the PBU file type might be incorrect or it might not be stored in memory.
[Measures to Take]
If the alarm occurs during NC operation, reinstall control floppy disk.
If the alarm occurs before the NC runs after control floppy disk installation.
0807 ACP panel status reception error
Eeoelale2008 ACP board received an abnormal operation panel status.
[Code]
XX (Operation panel status data)
Bit 7-> Panel status invalid
Bit 6-> Operation panel CPU error
Bits 3 to 5-> Firmware version number for operation panel
Bits 0 to 2-> Operation panel type
0808 Gear ratio data error
Eeoelale2009 In a machine equipped with high-speed contouring function, gear ratio data for X-axis, Y-axis, Z-axis, or C-axis is incorrect, or type of encoder used is incorrect.
[Code]
1-> X-axis gear ratio data code setting.
2-> Y-axis gear ratio data code setting.
3-> Z-axis gear ratio data code setting.
4-> C-axis gear ratio data code setting.
5-> X-axis gear ratio data is out of setting range.
6-> Y-axis gear ratio data is out of setting range.
7-> Z-axis gear ratio data is out of setting range.
8-> C-axis gear ratio data is out of setting range.
9-> Incorrect type of encoder used.
[Probable Fault Cause]
Gear ratio data in servo data PBU file or type of encoder used is incorrect
[Measures to Take]
Modify servo data PBU file.
0809 FCP error
Eeoelale2010 FCP board status is abnormal.
[Character-string]
AAAABB
AAAA: Name of task being executed
BB: Program module number being executed (hexadecimal)
[Code]
XXYYZZ
XX=01-> Transmitting module stopped.
XX=02-> Exception error
XX=03-> Double bus error
YY=01-> Bus error
YY=02-> Address error
YY=03-> Illegal instruction
LC37-003 P-23
SECTION 3 ALARM P
YY=04-> Zero divide
YY=05-> CHK instruction error
YY=06-> TRAPV instruction error
YY=07-> Privilege violation error
YY=08-> Trace error
YY=09-> Line 1010 emulator error
YY=0A-> Line 1111 emulator error
YY=0B-> Unassigned vector error
YY=0C-> Spurious interrupt error
YY=0D-> Interrupt error
YY=0E-> TRAP instruction error
YY=0F-> User interrupt error
ZZ:
Bit 7-> System bus error
Bit 6-> System bus parity check error
Bit 5-> Loop timeout error
Bit 4-> Protection error
Bit 3-> Loop error
Bit 2-> Loop error cancel
Bit 1-> Memory parity check error
Bit 0-> Always 0
0810 FCP I/O data file read error
Eeoelale2011 The NC cannot read the I/O data file.
[Code]
I/O data file loading status (hexadecimal)
2-> File open error (no file)
3-> File read error (no data)
4-> File attribute error (not "PBU1" type)
5-> File close error
6-> File size error (too small)
7-> File size error (too large)
100-> Incorrect PLC machine type
200-> Incorrect PLC category
300-> Incorrect file version
0811 FCP I/O link communication error
Eeoelale2012 A communication error occurred on the I/O link of the FCP board.
[Code]
WXYYZZZZ
W=1-> FCP board channel number where error occurred (fixed to 1)
X=1-> Optical cable disconnection or not connected
X=2-> HSCC initialization error
YY:
Bit 7-> Double transmission error
Bit 6-> Double reception error
Bit 5-> Framing error
Bit 4-> CRC error
Bit 3-> Parity check error
Bit 2-> Disconnection command detected
Bit 1-> Timeout error
Bit 0-> Undefined
ZZZZ:
Bit 15-> Error detected at slave station
Bit 14-> Undefined
Bit 13-> Undefined
Bit 12-> Start bit error
Bit 11-> Stop bit error
Bit 10-> Undefined
Bits 9, 8-> Duplicate station number
Bits 7 to 0-> Slave station number where error occurred (Master station: $00)
LC37-003 P-24
SECTION 3 ALARM P
0812 MCS startup
Eeoelale2013 An error occurred during MCS initialization at power-on.
[Index]
Axis name or none
[Character-string]
Varies depending on code
[Code]
XXXXYYYY
XXXX: Type of alarm occurred
YYYY: Alarm information (varies depending on XXXX.)
XXXX
FFFF…YYYY=00UV, U: Faulty channel number - 1
0= Channel 1
1= Channel 2
2= Channel 3
V: Indicates cause of fault (V=1 indicates servo link mode is not yet established.)
FF01…. Indicates a memory error occurred during a read/write test of the servo link I/O buffer memory.
YYYY=0 (Fixed)
Character-string indicates the address where the error occurred.
FF00… Indicates a communication LSI error occurred during a read/write test of the servo link I/O buffer memory.
YYYY indicates the error status.
Character-string indicates the address where the error occurred.
F000…YYYY= Bit 7: Same ID number is used
Bit 6: Incorrect ID number
Bit 5: No ID number
Bit 4: Too many controllers on CH4
Bit 3: Too many controllers on CH3
Bit 2: Too many controllers on CH2
Bit 1: Too many controllers on CH1
Bit 0:
Link data appears in the center of the screen when this error occurs.
EF00… Indicates the servo is not connected to all requested axes, or is connected to an unrelated axis. YYYY= ID number of requested axis controller
Character-string indicates the name of the faulty axis. Link data appears in the center of the screen when this error occurs.
EE00… Indicates an error occurred while downloading an option file.
The upper digits of YYYY indicate the cause, and the lower digits indicate the fault code.
If upper digits =
1: File is not in OSP format.
2: Invalid file attribute.
3: File open error. Lower digits indicate the fault code.
4: Raw data read error. Lower digits indicate the fault code.
5: File does not start with "MCS1".
6: File name does not follow "OPFS".
7: Number of files is set to 0.
8: Data read error. Lower digits indicate the fault code.
9: A sector length in the file data is 0.
A: Number of transmitted bytes is 0.
B: A sector length in the file data is less than the number of transmitted bytes.
C: Data read error. Lower digits indicate the fault code.
ED00… Indicates an error occurred when switching from manual mode to auto mode. The upper digits of YYYY indicate the cause, and the lower digits indicate the fault code.
Upper digits=1: World clock not started.
EC01… Indicates an error in the CH1 timer. YYYY is the difference value.
EC02… Indicates an error in the CH2 timer. YYYY is the difference value.
EC03… Indicates an error in the CH3 timer. YYYY is the difference value.
D001… Indicates the software synchronization bit signal was not received within 3 seconds when receiving buffered raw data in auto mode. YYYY is always 0.
D002… Indicates an illegal format code was received in buffer A when receiving buffered raw data in auto mode. Lower two digits of YYYY are the received format code.
D003… Indicates an illegal format code was received in the first segment of buffer B when receiving buffered raw data in auto mode.
YYYY is the received format code.
D004… Indicates an illegal format code was received in the second segment of buffer B when receiving buffered raw data in auto mode.
YYYY is the received format code.
D005… Indicates an illegal format code was received in the third segment of buffer B when receiving buffered raw data in auto mode.
YYYY is the received format code.
D006… Indicates an illegal format code was received in the fourth segment of buffer B when receiving buffered raw data in auto mode.
YYYY is the received format code.
LC37-003 P-25
SECTION 3 ALARM P
D007… Indicates an illegal format code was received in the fifth segment of buffer B when receiving buffered raw data in auto mode.
YYYY is the received format code.
D008… Indicates an illegal format code was received in the sixth segment of buffer B when receiving buffered raw data in auto mode.
YYYY is the received format code.
D009… Indicates an illegal format code was received in the seventh segment of buffer B when receiving buffered raw data in auto mode.
YYYY is the received format code.
D00A… Indicates an illegal format code was received in the ninth segment of buffer B when receiving buffered raw data in auto mode.
YYYY is the received format code.
D010… Indicates the self-diagnostic data received when receiving buffered raw data in auto mode was not $55. YYYY is the received self-diagnostic data.
D011… Indicates bits 0 and 1 in the "bit" data received in buffer A when receiving buffered raw data in auto mode are faulty.
YYYY is the received data.
D012… Indicates bits 2 and 3 in the "bit" data received in buffer A when receiving buffered raw data in auto mode are faulty.
YYYY is the received data.
D013… Indicates bits 4 and 5 in the "bit" data received in buffer A when receiving buffered raw data in auto mode are faulty.
YYYY is the received data.
D080… Indicates the buffered raw data with ID 441C in auto receive mode is faulty. YYYY is the received data.
D081… Indicates the buffered raw data with ID 2428 in auto receive mode is faulty. YYYY is the received data.
D090… Indicates the buffered raw data with ID 4405 in auto receive mode is faulty. YYYY is the received data.
D091… Indicates the buffered raw data with ID 4404 in auto receive mode is faulty. YYYY is the received data.
D092… Indicates the offset data for point compensation in the buffered raw data in auto receive mode is faulty. YYYY is the received data.
[Probable Faulty Locations]
Inverter unit (Check the LED display on the inverter unit.)
Faulty MCS ID setting.
Faulty specification code setting
Faulty connection to MCS
0813 MCS communication error
Eeoelale2014
An error occurred during communication between NC and MCS at power-on.
If the servo link information is displayed in the center of the screen, the cause of the communication error can be determined based on the provided information.
[Index]
None
[Character-string]
[Command name] – [Channel number] – Network address (controller number)
[Code]
XXXXYYYY
XXXX:
1…NC received data transmitted by itself.
YYYY: Received frame information
2…Public data transmitted by a non-slave station was received.
YYYY: Received frame information
3… Received data size is 2 bytes or less.
YYYY: Normally 0
4… Received data sent from a station other than the slave station.
YYYY: Received frame information
5… NC received data that was broadcast by the NC.
YYYY: Received frame information
6… Received data sent from a station with station number 0.
YYYY: Received frame information
7… No response from the data receiver within 0.1 s after sending data (after 1 s). YYYY: Normally 0. "SI" command was specified before at least one MCS started up normally or before power-on
during link connection. Open the electrical cabinet link connection and check the LED display on the inverter unit; the display is ’22’ when the link connection is normal.
8… Data sending has not completed after approx. 0.1 s. YYYY is normally 0.
9… Communication error occurred after receiving data. YYYY indicates error status information.
A… Communication error occurred while NC was waiting for data reception or immediately after data transfer completion. YYYY indicates error status information.
B… Communication error occurred while waiting for data transmission. YYYY indicates error status information.
C… Attempted to send data while data transmission was in progress. YYYY indicates NC operation status information.
D… Attempted to send data in a state where a communication error had already occurred. YYYY indicates error status information.
E… An erroneous command was received. When the lower byte is numeric, the upper two digits of YYYY indicate code (45: Abnormality, 41: Alarm, 57: Warning, 54: Error)
[Refer to the handshake communication alarm table (5-10) in the MCS Controller Function External Specifications.]
100… An error occurred in the first 2 bytes of the response information for the received transmission data. YYYY: First 2 bytes received
LC37-003 P-26
SECTION 3 ALARM P
101… Received data size does not match the response requirement of the sent data. When the lower byte of YYYY indicates the normal value, the upper byte indicates the received data size.
102… The 1st data attached to the received data is erroneous. YYYY: Upper 2 bytes of the data judged to be erroneous. SI command: Slave link No.
AS command: Slave link No. ID command: Communication code + auxiliary code
103… The 2nd data attached to the received data is erroneous. YYYY: Upper 2 bytes of the data judged to be erroneous. SI command: Relay time value.
ID command: Data ID
104… The 3rd data attached to the received data is erroneous. YYYY: Upper 2 bytes of the data judged to be erroneous. ID command: Reserved data
105… The 4th data attached to the received data is erroneous. YYYY: Upper 2 bytes of the data judged to be erroneous. ID command: ID data (4 bytes or less)
106… The 5th data attached to the received data is erroneous. YYYY: Upper 2 bytes of the data judged to be erroneous. SI command: Controller number.
ID command: ID data (8 bytes)
200… Data size differs from that specified by the ID number. Software error
[Probable Faulty Locations]
Inverter unit (Check the inverter unit LED.)
FCP board
MCS link connection error
MCS link cable
Software error
0814 MCS data file
Eeoelale2015 An error occurred when reading or transferring the servo link data file after power-on, or erroneous data is present in the data file.
[Index]
[Character-string]
[Axis name]
[Device name]
[File name]
or None
[Code]
XYZZAAAA
X: Axis type; Y: Major classification; ZZ: Minor classification; AAAA: Data
X: 1=NC control axis
2=Spindle
3=PLC control axis
Y: 0=Error when reading servo data file
ZZ:
01=Error on file recovery. AAAA=Error code
AAAA indicates 000B: File does not exist, or required axis data is not present in the file.
02=File attribute mismatch.
03=File format is not OSP format.
04=Error on file open. AAAA=Error code
05=Error on file data read. AAAA=Error code
06=File does not start with "PBU1".
07=File name does not follow "M1".
08=Corresponding axis data exceeds the maximum data value set in the file before data transfer.
09=Error on file close. AAAA=Error code
0A=Data group size exceeds 8 sectors. AAAA=Number of data sectors
0B=Error on data read. AAAA=Error code
0C=Pre-designated data group number is not contained in data file.
0D=Data serial numbers do not match.
0E=Data types do not match.
0F=Total number of data groups does not match.
10=Error on file close. AAAA=Error code
11=Servo data for existing NC axis does not exist in data file.
Y: 1=Error found during servo data file check
ZZ:
01=NC axis control data file for heavy workpiece machining specification not found.
LC37-003 P-27
SECTION 3 ALARM P
02=Axis specification (linear axis, rotary axis) does not match the inverter unit. AAAA=Axis specification data
03=Acceleration/deceleration method mismatch.
04=Synchronous sensor not provided.
05=Data group number error (spindle group number outside 1 to 32). AAAA=Data group number
06=Erroneous data not conforming to system specifications found in speed constant characteristic data.
Upper 2 bytes of AAAA indicate axis number, and lower 2 bytes indicate error content.
Upper bytes AA:
00->X-axis
01->Y-axis
02->Z-axis
03->4th axis
04->5th axis
Lower bytes AA:
11->FT1max=0
12->FT1max ＜ FT1min
13->FT1max=FT1min and T1max ＜ T1min
14->FT1max ＞ FT1min and T1max ＜ T1min
21->FT2max=0 (FT2max is determined by internal calculation.)
22->FT2max ＜ FT2min
23->FT2max=FT2min and T2max ＜ T2min
24->FT2max ＞ FT2min and T2max ＜ T2min
07=NC axis servo data for NC control specification for heavy workpiece machining not found.
[Probable Faulty Locations]
Axis data file error
0815 PLC real-time task cycle error
Eeoelale2016 Real-time task indicated by the character string was not completed within the scheduled processing time.
[Target]
None
[Character-string]
AAAABB
AAAA->Task name being processed when cycle error was detected.
BB->Program module number being executed (hexadecimal)
[Code]
XXXXXXXX->Program counter value when cycle error was detected (hexadecimal)
[Probable Faulty Locations]
Level 2 and Level 3 tasks in PLC program were not completed within the specified time.
Synchronization signal timing error
Synchronization signal frequency error
0816 PLC initialization error
Eeoelale2017 An error was detected while checking PLC operation start sequence.
[Index]
None
[Character-string]
None
[Code]
XX =1… NC - PLC synchronization parameter was not found.
[Measures to Take]
Contact the machine tool builder.
LC37-003 P-28
SECTION 3 ALARM P
0817 MCS abnormality
Eeoelale2018 An error occurred during MCS control processing.
[Index]
Axis name or None
[Character-string]
None
[Code]
XXZZAAAA
When XXZZ=0
AAAA:
1=Processing did not complete within 5 s after MCS reset 1.
2=Processing did not complete within 5 s after MCS reset 2.
3=Processing did not complete within 5 s after PLC reset 1.
4=Processing did not complete within 5 s after PLC reset 2.
X: 1 to 3
X: Channel number
YZZAAAA: Communication error status
[Probable Faulty Locations]
MCS controller
Servo link error on FCP board
Software error
0818 ADP start
Eeoelale2019 An alarm occurred during the initialization process of the AD converter processor board after power-on.
[Target]
None
[Character-string]
None
[Code]
X
X=1: Synchronous counter value remains unchanged at 1.
X=2: System alarm occurred when synchronous counter is 1.
X=3: Synchronous counter value remains unchanged at 3.
X=4; System alarm occurred when synchronous counter is 3.
[Probable Faulty Locations]
ADP board (AD converter processing board)
[Measures to Take]
Replace ADP board (AD converter processing board)
[Related Specifications]
Thermal deformation compensation
0820 Machine data file read error
Eeoelale2020 Machine data file (GNCUB*.PBU) cannot be read properly from memory (MD0A:) after power-on.
[Target]
None
[Character-string]
None
[Code]
1->File is not stored in memory, or file name is different.
2->File type is not "PBU2".
3->File DB size is too large.
4->File DB size is too small.
[Probable Faulty Locations]
Machine data PBU file is not stored on the provided system floppy disk.
LC37-003 P-29
SECTION 3 ALARM P
Incorrect procedure when loading PBU file from floppy disk into NC memory (COPY command cannot be used)
Memory fault
[Measures to Take]
Check the control floppy disk containing the machine data file (GNCUB*.PBU)
Reinstall control floppy disk
Replace memory card
0821 Spindle gear ratio data error
Eeoelale2021
Gear ratio data used for spindle speed control in the servo data file (SVGU*.PBU) is incorrect.
1) When gear ratio is set by ratio code, ratio code is not $2F-$3F.
2) When gear ratio is directly designated, data is not 0-2048 or (7200).
3) When using the high-speed CAM grinding function, the gear ratio is set with a ratio code.
4) When using the high-speed CAM grinding function, data is not 0 to 2048 or (7200).
[Object]
None
[Character-string]
None
[Code]
1-> Gear ratio data is set with gear ratio code
2-> Gear ratio data is set directly
3-> X-axis gear ratio data is set with code.
4-> C-axis gear ratio data is set with code.
5-> X-axis gear ratio data is out of setting range.
6-> C-axis gear ratio data is out of setting range.
[Probable Fault Cause]
Error in the gear ratio data in the servo data PBU file (SVGU*.PBU).
[Measures to Take]
Correct the gear ratio data in the servo data PBU file.
0822 Pulse handle data file read error
Eeoelale2022 After power-on, the pulse handle paired data extension file (GNCUD*PBU) cannot be read from memory (MD0:).
[Object]
None
[Character-string]
None
[Code]
1-> The file is not in memory, or the file name is different.
2-> File type is not "PBU3".
3-> File DB size is too large.
4-> File DB size is too small.
[Probable Fault Cause]
The pulse handle paired data extension file is not stored on the accessory NC system floppy disk.
Error in the operating procedure when loading the PBU file from the floppy disk into NC memory (the COPY command cannot be used).
Memory failure
[Measures to Take]
Check the control floppy disk containing the pulse handle paired data extension file (GNCUD*.PBU).
Reinstall the control floppy disk.
Replace the memory board.
LC37-003 P-30
SECTION 3 ALARM-P
0823 Axis configuration data setting error
Eeoelale2023 Error in setting the axis configuration data set according to the axis configuration number.
[Code]
XY
X=1-> In the system axis configuration setting, "2" appeared before "1" was set.
Y=2-> When enabling the axis by "bit data" of the control axis (PLC->CNC bit data U), one of the configuration setting items is set to 0.
Y: Set value of the axis configuration number.
[Probable Fault Cause]
Error in axis configuration setting
[Measures to Take]
Correct the axis configuration setting corresponding to the alarm code.
0824 Unit connection error
Eeoelale2024
Unit connection does not match the axis configuration setting.
The configuration number of the axis connection does not match the set axis configuration number.
[Code]
Set value of axis configuration number
[Probable Fault Cause]
Unit connection error
[Measures to Take]
Correct the unit connection corresponding to the alarm code.
0825 Axis configuration name not set
Eeoelale2025 An axis name is not set for the configured axis.
[Code]
Set value of axis configuration number
[Probable Fault Cause]
Axis name is not set for the configured axis.
[Measures to Take]
Set a name for the axis corresponding to the alarm code.
0826 Axis configuration data file read error
Eeoelale2026 The axis configuration data setting file (SAXD*.PBU) does not exist in MD0:.
[Code]
1
[Probable Fault Cause]
Axis configuration data setting file error
[Measures to Take]
Create the axis configuration data setting file in MD0:.
Or read an existing axis configuration data setting file into MD0:.
0827 Control axis absent
Eeoelale2027 Control axis bit data (PLC->NC bit data U) is 0.
[Code]
Set value of axis configuration number
[Probable Fault Cause]
PLC control program
[Measures to Take]
Change the PLC control program.
LC37-003 P-31
SECTION 3 ALARM-P
0828 Linear feed axis number error
Eeoelale2028
The axis specified by the linear feed axis number (PLC->->NC word data WU) is not a finite linear axis.
Linear feed axis number is 0 or greater than 7, or an infinite linear axis in test mode is not set in the axis configuration setting file.
[Code]
Linear feed axis number
[Probable Fault Cause]
PLC control program
[Measures to Take]
Change the PLC control program.
0829 SPMC program load error
Eeoelale2029 Error occurred when loading the Super Master Card (SPMC) program.
[Code]
XYYZAAAA
X: Module number of the input program