Noritsu ошибка 6073 synchronous sensor error

CNC SYSTEM

OSP-P300S/P300L

ALARM & ERROR LIST

(1st Edition)

Pub No. 5921-E (LE37-006-R1) Nov. 2011

5921-E P-(i)

SAFETY PRECAUTIONS

SAFETY PRECAUTIONS

The machine is equipped with safety devices which serve to protect personnel and the machine itself from hazards arising from unforeseen accidents. However, operators must not rely exclusively on these safety devices: they must also become fully familiar with the safety guidelines presented below to ensure accidentfree operation.

This instruction manual and the warning signs attached to the machine cover only those hazards which Okuma can predict. Be aware that they do not cover all possible hazards.

1.Precautions Relating to Installation

(1)Please be noted about a primary power supply as follows.

Do not draw the primary power supply from a distribution panel that also supplies a major noise source (for example, an electric welder or electric discharge machine) since this could cause malfunction of the CNC unit.

If possible, connect the machine to a ground not used by any other equipment. If there is no choice but to use a common ground, the other equipment must not generate a large amount of noise (such as an electric welder or electric discharge machine).

(2)Installation Environment

Observe the following points when installing the control enclosure.

Make sure that the CNC unit will not be subject to direct sunlight.

Make sure that the control enclosure will not be splashed with chips, water, or oil.

Make sure that the control enclosure and operation panel are not subject to excessive vibrations or shock.

The permissible ambient temperature range for the control enclosure is 5 to 40°C (41 to 104°F).

The permissible ambient humidity range for the control enclosure is relative humidity 50% or less at 40°C (104°F) (no condensation).

The maximum altitude at which the control enclosure can be used is 1000 m (3281ft.).

2.Points to Check before Turning on the Power

(1)Close all the doors of the control enclosure and operation panel to prevent the entry of water, chips, and dust.

(2)Make absolutely sure that there is nobody near the moving parts of the machine, and that there are no obstacles around the machine, before starting machine operation.

(3)When turning on the power, turn on the main power disconnect switch first, then the CONTROL ON switch on the operation panel.

5921-E P-(ii)

SAFETY PRECAUTIONS

3.Precautions Relating to Manual/Continuous Operation

(1)Follow the instruction manual during operation.

(2)Do not operate the machine with the front cover, chuck cover, or another protective cover removed.

(3)Close the front cover before starting the machine.

(4)When machining the initial workpiece, check for machine operations, run the machine under no load to check for interference among components, cut the workpiece in the single block mode, and then start continuous operation.

(5)Ensure your safety before rotating the spindle or moving a machine part.

(6)Do not touch chips or workpiece while the spindle is rotating.

(7)Do not stop a rotating part with hand or another means.

(8)Check that the condition of hydraulic chuck jaws as mounted, operating pressure, and maximum permissible revolving speed.

(9)Check the condition and location of the cutting tool as mounted.

(10)Check the tool offset value.

(11)Check the zero offset value.

(12)Check that the SPINDLE OVERRIDE and FEEDRATE OVERRIDE dials on the NC operation panel are set to 100%.

(13)When moving the turret, check the software limits for X- and Z-axes or the locations of limit switch dogs to prevent interference with the chuck and tailstock.

(14)Check the location of the turret.

(15)Check the location of the tailstock.

(16)Cut workpieces with a transmitted power and torque within the permissible range.

(17)Chuck each workpiece firmly.

(18)Check that the coolant nozzle is properly located.

4.On Finishing Work

(1)On finishing work, clean the vicinity of the machine.

(2)Return the ATC, APC and other equipment to the predetermined retraction position.

(3)Always turn off the power to the machine before leaving it.

(4)To turn off the power, turn off the CONTROL ON switch on the operation panel first, then the main power disconnect switch.

5921-E P-(iii)

SAFETY PRECAUTIONS

5.Precautions during Maintenance Inspection and When Trouble Occurs

In order to prevent unforeseen accidents, damage to the machine, etc., it is essential to observe the following points when performing maitenance inspections or during checking when trouble has occurred.

(1)When trouble occurs, press the emergency stop button on the operation panel to stop the machine.

(2)Consult the person responsible for maintenance to determine what corrective measures need to be taken.

(3)If two or more persons must work together, establish signals so that they can communicate to confirm safety before proceeding to each new step.

(4)Use only the specified replacement parts and fuses.

(5)Always turn the power off before starting inspection or changing parts.

(6)When parts are removed during inspection or repair work, always replace them as they were and secure them properly with their screws, etc.

(7)When carrying out inspections in which measuring instruments are used — for example voltage checks — make sure the instrument is properly calibrated.

(8)Do not keep combustible materials or metals inside the control enclosure or terminal box.

(9)Check that cables and wires are free of damage: damaged cables and wires will cause current leakage and electric shocks.

(10)Maintenance inside the Control Enclosure

a.Switch the main power disconnect switch OFF before opening the control enclosure door.

b.Even when the main power disconnect switch is OFF, there may some residual charge in the MCS drive unit (servo/spindle), and for this reason only service personnel are permitted to perform any work on this unit. Even then, they must observe the following precautions.

MCS drive unit (servo/spindle)

The residual voltage discharges two minutes after the main switch is turned OFF.

c.The control enclosure contains the NC unit, and the NC unit has a printed circuit board whose memory stores the machining programs, parameters, etc. In order to ensure that the contents of this memory will be retained even when the power is switched off, the memory is supplied with power by a battery. Depending on how the printed circuit boards are handled, the contents of the memory may be destroyed and for this reason only service personnel should handle these boards.

5921-E P-(iv)

SAFETY PRECAUTIONS

(11)Periodic Inspection of the Control Enclosure

a.Cleaning the cooling unit

The cooling unit in the door of the control enclosure serves to prevent excessive temperature rise inside the control enclosure and increase the reliability of the NC unit. Inspect the following points every three months.

Is the fan motor inside the cooling unit working?

The motor is normal if there is a strong draft from the unit.

Is the external air inlet blocked?

If it is blocked, clean it with compressed air.

6.General Precautions

(1)Keep the vicinity of the machine clean and tidy.

(2)Wear appropriate clothing while working, and follow the instructions of someone with sufficient training.

(3)Make sure that your clothes and hair cannot become entangled in the machine. Machine operators must wear safety equipment such as safety shoes and goggles.

(4)Machine operators must read the instruction manual carefully and make sure of the correct procedure before operating the machine.

(5)Memorize the position of the emergency stop button so that you can press it immediately at any time and from any position.

(6)Do not access the inside of the control panel, transformer, motor, etc., since they contain highvoltage terminals and other components which are extremely dangerous.

(7)If two or more persons must work together, establish signals so that they can communicate to confirm safety before proceeding to each new step.

5921-E P-(v)

SAFETY PRECAUTIONS

7.Symbols Used in This Manual

The following warning indications are used in this manual to draw attention to information of particular importance. Read the instructions marked with these symbols carefully and follow them.

5921-E P-(i)

INTRODUCTION

INTRODUCTION

Before using this NC unit, read this manual thoroughly in order to ensure correct use.

This manual explains how to use and maintain the control so that it will deliver its full performance and maintain accuracy over the long term.

You must pay particular attention to the cautions given in this manual; read them carefully and make sure you fully understand them before operating the NC.

5921-E P-1

SECTION 1 CLASSIFICATION OF ALARMS

SECTION 1 CLASSIFICATION OF ALARMS

Alarms related with the OSP are classified into five types such as Alarm P, A, B, C and D.

1-1. Alarm Classifications

As indicated above, the object numbers and messages to be used are determined by the machine specifications.

5921-E P-3

SECTION 1 CLASSIFICATION OF ALARMS

1-2-1. Alarm Codes

In this manual, alarm codes are explained using such as «X», «XX», and «XXYY».

Explanation is given in the following methods:

(1)The alarm code indicated in this text can be used directly as the key to find the contents of error.

(2)The alarm code indicated in this text should first be converted into bit expression (pattern), which is then used as the key to find the contents of error.

In the case of 2), the procedure to convert the alarm code into bit pattern is shown below.

1-2-2. Bit conversion method

LE37006R0100300060001

5921-E P-5

5921-E P-6

5921-E P-7

5921-E P-8

5921-E P-9

5921-E P-10

SECTION 2 ALARM P

0700 NC start-up error

An error occurred when NC started up.

[Object] None

[Character-string] None

[Code]

0x10000000: NC Configuration read error 0x10003000: Spec code read error 0x20000000: ServoLink board initializing error 0x3XXX00YY: NC data file read error

XXX:

0x002: HD backup status file 0x004: Parameter data file 0x008: Machine data file 0x010: PLC backup data file 0x020: PLC-HMI data file 0x040: Alarm History data file 0x080: PLC AXIS data pbu file

0x100: POT TOOL data pbu file (M/C only) 0x200: MOP TOOL Tool data file (M/C only) 0x400: MOP TOOL Parameter file (M/C only) 0x800: Thermal deviation compensation data file

YY:

0x01: File read open error 0x02: File read error 0x03: Version check error 0x04: Check sum error

0x05: Double check sum error 0x06: Backupped Memory error 0x07: File write open error 0x08: File write error

0x40000000: Axis information initializing error -More than 8 axis

0x50000000: PLC data file read error -Read failed M code data file

0x60000000: I/O Initializing error -PLC variable backup file read error -I/O forced data file read error

0x70000000: ServoLink Initializing error 0x80000000: Operation buffer get error 0x90000000: PBU data file read error 0xA0000000: Shared memory size definition error 0xA1XXXXXX: AlarmService start error

XXXXXX: Error code of AlarmService library function 0xA2400002: Alarm History read error 0xA3000000: Thread monitor initializing error

0xA9000000: Initialization processing of the safety logic was not completed within 20 seconds 0xA9000001: Axis construction definition file open error

0xA9000002: Axis construction definition file read error 0xA9000003: Axis construction definition file mismatch 0xFFFFFFFF: Debug information file read error

0701 P100-Menu initialization failure

An error occurred in P100-Menu while system startup.

[Object] None

[Character-string] None

[Code]

1:NC Control file was not found.

2:PLC Control file was not found.

3:NC-HMI was not found

5921-E P-11

SECTION 2 ALARM P

4:3D real sim file was not found.

5:MacMan file was not found.

6:Version mismatch between P100-Menu and PLC Control

7:Version mismatch between P100-Menu and MacMan

8:Version mismatch between P100-Menu and NC Control

11:Conf-P100-menu read error

12:An error occurred at RTOS

13:An error occurred at UPS Service

21:NC Control start failure

22:Error in obtaining shared objects

23:PLC Control start failure

24:NC-HMI start failure

25:3D real sim start failure

26:MacMan start failure

101:Startup sequence 0x10 receive failure

200:Startup sequence 0x10 send failure

201:Startup sequence 0x20 receive failure

300:Startup sequence 0x20 send failure

301:Startup sequence 0x30 receive failure

400:Startup sequence 0x30 send failure

401:Startup sequence 0x60 receive failure

500:Startup sequence 0x60 send failure

501:Startup sequence 0x70 receive failure

600:Startup sequence 0x70 send failure

601:Startup sequence 0x7C receive failure

700:Startup sequence 0x7C send failure

701:AlarmService start failure

702:Activation sequence 0x80 receive failure

[Probable Faulty Locations]

1.Execution file name failure 2.Data file name failure 3.RTOS failure

4.UPS function failure 5.Software failure 6.Software Version failure

0702 Power failure upon start-up

[Object] None

[Character-string] None

[Code] None

[Probable Faulty Locations]

1.Power failure during while system startup 2.Power shutoff during while system startup

0703 Load information file not found

A load information file was not found.

[Object] None

[Character-string] None

[Code] None

0704 File load error

An object file was not loaded correctly.

[Object] None

[Character-string]

5921-E P-12

SECTION 2 ALARM P

None

[Code]

1:A file was not found

2:The attribute of file was not correct.

3:The load address information of file was not correct 4:An error occurred when file was loaded

FFFFFFFF:The details of alarm was displayed by message from OS

0705 Default scheduling table error

A default scheduling table error was detected.

[Object] None

[Character-string] None

[Code]

0x00010001: RTIN default scheduling table error (element number) 0x00010002: RTIN default scheduling table error (end element) 0x00020001: TSMN default scheduling table error (element number) 0x00020002: TSMN default scheduling table error (initial attribute)

[Probable Faulty Locations] 1.NC software failure

0706 Backup data file error

Error occurred when load/save the backup file.

[Object] None

[Character-string] None

[Code] XXXXYYYY

XXXX

0x0002:HD backup status file 0x0004:Low speed NC backup data file 0x0008:High speed NC backup data file 0x0010:PLC backup data file 0x0020:PLC-HMI data file 0x0040:Alarm history data file 0x0080:PLC axis data file

0x0100:POT TOOL data file

0x0200:MOP TOOL Tool data file (M/C only) 0x0400:MOP TOOL Parameter data file (M/C only) 0x0800:Thermal deviation compensation data file

YYYY

1:File read open error 2:File read error 3:Version check error 4:Check sum error 5:Double check sum error

6:Backup memory check error 7:File write open error

8:File write error

0707 DTL link/unlink error

An error occurred in DTL link or unlink.

[Object] None

[Character-string] None

[Code]

1:RTIN refresh error

5921-E P-13

SECTION 2 ALARM P

2:TSMN refresh error

[Probable Faulty Locations]

1.Hardware failure 2.Software failure

0708 RT thread stack overflow

Stack overflow of RT thread was detected.

[Object] None

[Character-string]

Occurred RT thread name

[Code] None

[Probable Faulty Locations] 1.NC software failure

0709 Hardware exception

Hardware exception was occurred.

[Object] None

[Character-string]

Occurred RT thread name

[Code]

Hardware exception code 0x5555: CPU Diagnose error 0x8100:Divide by 0 error

0x8101:Unexpected Single Step Interrupt 0x8102:Unexpected NMI 0x8103:Unexpected Debug Interrupt 0x8104:Overflow error

0x8105:Array Bounds error 0x8106:Invalid Opcode error 0x8107:NPX Device not present 0x8108:Double Fault error 0x8109:Unknown Device error 0x810A:Invalid TSS error 0x810B:Segment not Present error 0x810C:Stack Fault error 0x810D:General Protection error 0x810E:Page Fault error 0x8110:Unknown Device error 1 0x8111:Alignment error

[Probable Faulty Locations] 1.Hardware failure 2.Software failure

[Note]

Alarm information is also displayed also in the console window.

0710 System call error

An error occurred in the INtime system call.

[Object] None

[Character-string]

Occurred RT thread name

[Code] XXXXYYYY

XXXX:INtime system call code

YYYY:Return value or status of INtime system call [Probable Faulty Locations]

5921-E P-14

SECTION 2 ALARM P

NC software failure

[Note]

Alarm information is also displayed also in the console window.

0711 AlarmService library error

An error occurred in the AlarmService library function.

[Object] None

[Character-string] Occurred thread name

[Code]

XXYYYYYY

XX:AlarmService library function code YYYYYY:AlarmService library function error code

[Probable Faulty Locations] NC software failure

[Note]

Alarm information is also displayed also in the console window.

0712 AlarmService internal error (exception)

An error occurred inside of AlarmService.

[Object] None

[Character-string] «ALMS»

[Code]

AlarmService internal error code

[Probable Faulty Locations] NC software failure

[Note]

Alarm information is also displayed also in the console window.

0713 AlarmService error

P100-Menu detected AlarmService error.

[Object] None

[Character-string] None

[Code] None

[Probable Faulty Locations] 1.NC software failure

0714 Blue screen

Blue screen (kernel stop error) occurred.

[Object] None

[Character-string] None

[Code] None

[Probable Faulty Locations] 1.Win32 application failure 2.Windows failure 3.Windows driver failure

0719 HXCP thread error

5921-E P-16

SECTION 2 ALARM P

An abnormal condition of HXCP thread was detected.

[Object] None

[Character-string] None

[Code] None

[Probable Faulty Locations] 1.NC software failure

0720 AlarmService internal error

An error occurred inside of AlarmService.

[Object] None

[Character-string] «ALMS»

[Code]

AlarmService internal error code

[Probable Faulty Locations]

1.NC software failure 2.P100-Menu failure

0721 DeviceNet error

Error occurred on DeviceNet.

[Index] None

[Character-string] CH* SC$

* : Channel number where the error occurred. S : Sequence counter

[Code] XXYYZZZZ

XXSlave station MacID where the error occurred

YYSlave station

0x00 Normal or nonexistent slave station

0x46 Duplicate MacID error

0x48 Communication stop

0x49 Discrimination information was not compatible with scan list 0x4D Data size was not compatible with scan list

0x4E No response in the connection check.

0x4F Other slave stations are nonexistence on network 0x50 Idle condition

0x53 Error received in the connection check

0x54 Timeout occurred in the connection check

0x56 Turn into the idle mode 0x5B Bus off

0x5C Network power supply off

( XXXX became 0xFFFF,if its not caused by slave station, such as communication delay.) ZZZZ Scanner error status

bit 0 Memory check error bit 1 Scan list initialize 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(single) bit 9 Input data reception error(dowble)

bit10 Output data transmission error(single) bit11 Output data transmission error(dowble)

5921-E P-17

SECTION 2 ALARM P

bit12 Slave station communication delay error(single) bit13 Slave station communication delay error(dowble) bit14 Bus off

bit15 Diagnostic information access error

[Probable Faulty Locations]

1)Hardware failure 2)Software failure

0723 DeviceNet I/O data link file read

The NC failed to read DeviceNet IO data link file.

[Code]

I/O data file load status (in hexadecimal) 2 ->File open error (no file)

3 ->File read error (no data)

4 ->File attribute error (not «PBU1»)

5 ->File close error

6 ->File size error (too small)

7 ->File size error (too large)

100->Wrong PLC machine type

200->Wrong PLC class

300->Wrong file version

1002 ->DN SCAN LIST CHANGE FILE OPEN ERROR

1003 ->DN SCAN LIST CHANGE FILE READ ERROR (NO DATA)

1004 ->DN SCAN LIST CHANGE FILE ATTRIBUTE ERROR (NO ‘PBU1’) 1005 ->DN SCAN LIST CHANGE FILE CLOSE ERROR

1006 ->DN SCAN LIST CHANGE FILE SIZE ERROR (SIZE SMALL)

0725 M code data file

Establishment data of reading M-code file is bad.

[Code]

1->The denial data is bad.

[Character string]

The number is M-code which is established bad data.

[Measures to Take]

Please correct the bad data of M-code.

0726 Safety speed data error

The safety speed data was in abnormal state in the machine without the CE marking safety speed monitor.

[Index]

Axis name or none (spindle)

[Character-string] None

[Code]

X

X=1:The guard number of the safety speed data was outside the range from -0 to 9.

[Measures to Take]

Change the safety speed monitor data file for axis control. Relevant specifications:Without CE mark safety speed monitor type

[Related Specifications]

Without CE mark safety speed monitor type

0727 MCS firmware doesn’t support POS2 unit

This alarm occurs when the firmware ROM version of the NC axis/ machine(PLC) axis MIV unit is not 511 or later when the new POS unit is installed.

[Character-string] None

[Code] None

5921-E P-18

SECTION 2 ALARM P

0728 FL-net error

An error occurred during startup of the FL-net card.

[Object] None

[Character-string] None

[Code]

Y000XXX

Y:0

XXXX: 7F00:System error

7F01:Flash memory error 7F02:DRAM test error 7F03:NICE test error 7F04:EEPROM sum check error 7F05:CPU BUS error 7F06:illegal Instruction

Y:1

XXXX:

0004:Timeout error for 4 sec or longer Y:F

XXXX:

FFFF: FL-net card is not mounted

[Probable Faulty Locations] FL-net card is defective.

0729 Non-responsive software detected.

Non-answered software was detected.

[Object] None

[Character-string] None

[Code]

NT Process name

[Probable Faulty Locations] NC software failure

0731 R Spec. error

It is the illegal of «R SPEC».

[Index] None

[Code]

1:»NON R SPEC» of NC is OFF, and «R-SPEC» of SVDN-ID is OFF. 2:»NON R SPEC» of NC is ON, and «R-SPEC» of SVDN-ID is ON.

3:When there are 2 SVDN-boards in the machine, «R-SPEC» of one board is ON, other is OFF. 4X:»NON R SPEC» of NC is OFF, and «R-SPEC» of SVDN-ID is ON, and Restriction-Spec is ON.

0732 Unable to execute lost motion compensation

0735 MCS DD encoder link error

An error occurred in the encoder communication link.

[Object]

Axis name or none (spindle)

[Character-string] None

[Code] XXYYZZZZ

The DD encoder (slave sensor) has become undetectable.

5921-E P-20

SECTION 2 ALARM P

[Object]

Axis name or none (spindle)

[Character-string] None

[Code] XXYYZZZZ

XX= Positional data status bit7 : Error bit (1:error)

bit6 : Absolute position sensor margin error.(0:Normal, 1:Warning) bit5 : Gap-Warning (1:Gap-small,Toggle:Gap-big)

bit4 : Inclination-Warning (1:CCW-big, Toggle:CW-big) bit3 : Auto set mode (0:Normal, 1:Auto mode)

bit2 : Communication error (Toggle by detecting)

bit1,0: Error bit number of absolute position code.(It is indicated by 2bits.)

YY= Alarm code

01: Stop command has stopped. 02: Control parameter error

04: Absolutization error

05: Initialization speed too high 08: Auto-set-data error

0D: Speed too high

0E: Synchronization error

20:Absolutization mismatch (Only Format-5)

21:Communication-error of Master-sensor (Only Format-5) 3E: Code-error by Absolute-position-sensor

3F: Check-errotr by Absolute-position-code

40:Inclination-error (for plus)

41:Inclination-error (for minus)

42:Gap is narrow

43:Gap is wide

ZZZZ= 0000 fixed

This alarm occurs only at ICB-H.

[Probable Faulty Locations] DD encoder (slave sensor)

0738 MCS DD encoder initialization failure

An error occurred in the initialization of the DD encoder.

[Object]

Axis name or none (spindle)

[Character-string] None

[Code] XXYYZZZZ

XX= Encoder link initialization sequence number (1B) at the time of the error detection

0:Reset

1:Network address setting

2:Request to send the basic information for communication

3:Change of communication software version

4:Acquisition of device information

5:Parameter change

6:Position detection start

7:AT mode start

YY= Error content (1B)

0:Communication error

1:Transmission start time over

2:Transmission finish time over

3:Reception finish time over

4:Abnormal response address

5:Abnormal response code

6:Parameter error

ZZZZ = Data (2B)

If YY = 0,

The encoder link error status C2ERR at the time of error detection appears.

If YY = 1, 2 or 3,

5921-E P-21

SECTION 2 ALARM P

The transmitted frame information QC2MTINF appears.

If YY = 4,

The network address of the responding device appears.

If YY = 5,

Alarm code + positional data status

Refer to MCS DD Encoder error (alarm 1136).

If YY = 6,

Parameter number at which the error is detected

1:Reception of insufficient number of parameters

2:Basic information for communication being incompatible

3:Multi-turn detection range over

4:Communication protocol version being incompatible

5:Positional data format being incompatible

6:Abbreviated data mode being incompatible

However, when abnormal voltage is detected at the encoder fuse XXYY = $FFFF fixed

ZZZZ = Detected voltage value of the encoder fuse (12[V] = $9980) Normal range: 10.6[V] to 13.8[V]

Allowable range: $8800 to $B000 This alarm occurs only at ICB-H.

[Probable Faulty Locations] DD encoder

Encoder link cables and connectors Inverter unit control board

0739 MCS DD encoder (slave sensor) initialization failure

An error occurred in the initialization of the DD encoder (slave sensor).

[Index]

Axis name or none (spindle)

[Character-string] None

[Code] XXYYZZZZ

XX= Encoder link initialization sequence number (1B) at the time of the error detection

0:Reset

1:Network address setting

2:Request to send the basic information for communication

3:Change of communication software version

4:Acquisition of device information

5:Parameter change

6:Position detection start

7:AT mode start

YY= Error content (1B)

0:Communication error

1:Transmission start time over

2:Transmission finish time over

3:Reception finish time over

4:Abnormal response address

5:Abnormal response code

6:Parameter error

ZZZZ = Data (2B)

If YY = 0,

The encoder link error status C2ERR at the time of error detection appears.

If YY = 1, 2 or 3,

The transmitted frame information QC2MTINF appears.

If YY = 4,

The network address of the responding device appears.

If YY = 5,

Alarm code + positional data status

Refer to MCS DD Encoder error (alarm 1136).

If YY = 6,

Parameter number at which the error is detected

1:Reception of insufficient number of parameters

2:Basic information for communication being incompatible

3:Multi-turn detection range over

The combination of NC-software and PLC-software was wrong. Or, the combination of specification-code was wrong.

5921-E P-23

SECTION 2 ALARM P

[Object] None

[Character-string] None

[Code]

1:PLC-software is not effective for the specification of «TOOL OFFSET 999» 4:It can’t be combined with spindle command unit 0.1.

5:Overlapped PLC axis number

[Probable Faulty Locations]

(1)Mistake of select for specification-code (2)Mistake of select for PLC-software-version

0752 VDU communication error

An error occurred in the VDU(Vibration Detect Unit) communication link, disabling the VDU from detecting acceleration.

[Object]

Axis name or none (spindle)

[Character-string] None

[Code] XXYYZZZZ

XX= FF [HEX] (fixed)

YY= 00 [HEX] (fixed)

ZZZZ = VDU link error status at the time of error detection. (Each bit represents the kind of communication error.)

bit 15 Undefined bit 14 Undefined bit 13 Undefined

bit 12 1: Error in communication with VDU(AT mode) bit 11 1: Error in communication with VDU(MT mode) bit 10 1: Transmission loop error in AT (auto) mode

bit 9 1: Data over error in data receiving part of interface bit 8 Undefined

bit 7 Undefined

bit 6 1: Modulation code error bit 5 1: CRC error

bit 4 1: Format error

bit 3 1: Double transmission error bit 2 1: Double reception error bit 1 1: Modulation code error

bit 0 1: Time-out error [Probable Faulty Locations]

—VDU

—Encoder link cables

—VFA unit

0753 VDU detected error

The VDU(Vibration Detect Unit) has become unable to detect acceleration data.

[Object]

Axis name or none (spindle)

[Character-string] None

[Code]

XXYYZZZZ

XX = VDU error status

5921-E P-24

SECTION 2 ALARM P

YY= VDU alarm code

01:Stop command halt

02: Control parameter error

07: User parameter check sum error 0E: Synchronous miss error

15:Acceleration sensor signal error (X axis)

16:Acceleration sensor signal error (Y axis)

17:Acceleration sensor signal error (X and Y axis) ZZZZ= 0 (fixed)

[Probable Faulty Locations]

— VDU

0754 VDU initialization failure

An error occurred in initialization of VDU(Vibration Detect Unit).

[Object]

Axis name or none (spindle)

[Character-string] None

[Code] XXYYZZZZ

XX= Encoder link sequence number at the time of error detection

0:Reset

1:Network address setting

2:Request of basic information on communication

3:Change of communication version

4:Acquisition of device information

5:Parameter change

6:AT (auto) mode start

YY= Error content

0:Communication error

1:Transmission start time over

2:Transmission finishes time over

3:Reception finishes time over

4:Abnormal response address

5:Abnormal response code

6:Parameter error

ZZZZ = Additional data If YY=0,

the encoder link error status C2ERR at the time of error detection appears. If YY=1, 2, or 3,

the transferred frame information C2MTINF appears. If YY=4,

the network address of the responding device appears. If YY=5,

the received frame information C2RXINF appears. If YY=6,

the number of parameter that caused the alarm appears. 1 = Not all the necessary parameters are received.

2 = Basic information on communication is incompatible.

4 = Protocol version on communication is incompatible. [Probable Faulty Locations]

—VDU

—Encoder link cables

—VFA unit

0755 SIO link error

An error occurred in the SIO link.

[Object] None

[Character-string] None

5921-E P-25

SECTION 2 ALARM P

[Code]

During steady processing FFFFFFFF:

Recieved the same data from MFU twice XXXXYYYY:

XXXX: command & data length 0303: recieved error with frame 0

YYYY:The second byte of reception data 1303: recieved error with frame 1

YYYY:The second byte of reception data 05FF: Error status besides 0

YYYY:Error status During setup processing XXYYZZZZ:

XX:frame

YY:command 00: reset

01: intelligence

02: time-out time setting 05: file-transfer

ZZZZ:error cause

0007: Data reception response is not sent within 0.15 second after data transmission. 0008: Data transmission does not end within 0.15 second.

0009: Communication error occurred after reception of data.

000A: Communication error occurred while the NC was waiting for data reception. 000B: Communication error occurred while the NC was waiting for data transmission. 000C: Data transmission was attempted during data transmission.

000D: Data transmission was attempted in the state of communication error. 000E: An error command was received.

000F: Transmission command and reception command were not same.

[Probable Faulty Locations]

1.SSIO card 2.Safety module 3.I/O slave

0756 PSC optical scale encoder error

An error was detected by the position encoder of optical scale.

[Character-string] None

[Code] XXYYZZ

XX:Value of the J-type endoder and value of the optical scale are too different. bit1:It is too different by a negative sign.

bit0:It is too different by a positive sign. YY:Pulse count value of optical scale

bit0:A-phase pulse and B-phase pulse have changed at the same time. ZZ:The amplitude of the optical scale signal is wrong.

bit1:The amplitude of B-phase is wrong. bit0:The amplitude of A-phase is wrong.

[Probable Faulty Locations]

—Breakdown of optical scale

—Breakdown of optical scale cable

[Measures to Take]

—Exchange of optical scale

—Exchange of optical scale cables

0757 MF-SAFETY Error

An error was detected by the MF-SAFETY.

[Object] None

[Character-string] None

5921-E P-26

SECTION 2 ALARM P

[Code]

0x1000XXXX->CPU Exception was occurred in the MF-SAFETY XXXX->Exception number

0x1100XXXX->NMI was occurred in the MF-SAFETY XXXX->NMI code

bit15->An error was occurred bit9 ->Voltage drop for CPU1

bit8 ->Watchdog timer overflow in CPU0 bit1 ->Voltage drop for CPU0

bit0 ->Watchdog timer overflow in CPU1 0x1200XXXX->CPU bus error was occurred in the MF-SAFETY

XXXX->CPUID

bit15->CPUID (0:CPU0, 1:CPU1) 0x130000XX->No response in CPU1 request

XX->CPU1 request number

0x170000XX->Normal process in the MF-SAFETY did not end within a specific period. XX->End time of normal process (1bit=62.5us)

0x1800XXXX->An Error was detected by the MF-SAFETY XXXX->Error Code

bit15->MFU I/O unit error bit14->MFU I/O Bus parity error bit12->Synchronization error

bit11->Wrongly set synchronous signal timing 0x19000000->Stack overflow in the MF-SAFETY CPU 0x1A00XXXX->Illegal address is in the label table

XXXX->Index of label table

0x1B000000->NC starts up with software update mode in the MF-SAFETY 0x1C0000XX->Mode setting is mismatch between NC and MF-SAFETY

XX->Mismatch location 01->MF-SAFETY mode setting is wrong 02->NC mode setting is wrong

[Probable Faulty Locations] MF-SAFETY MF-SAFETY mode setting NC mode setting

I/O unit in MFU

[Measures to Take]

Replace the MF-SAFETY unit Replace the I/O unit in MFU

Switch(SW1) of the MF-SAFETY turns off Update the MF-SAFETY software (safety logic)

0758 Safety I/O Error

An error occurred in Safety IO link (SIO link) or in safety I/O unit.

[Object] None

[Character-string] None

[Code]

0x20000000->Safety transmission data was mismatch between CPU0 and CPU1while initialization of SIO link 0x21XX0000->Command was not received while initialization of SIO link

XX->Expecting command 00->Reset Command

01->Information gathering Command

02->Time-out time setting Command

0x22XXYYYY->Communication error was occurred while initialization of SIO link XX->Expecting command

00->Reset Command

01->Information gathering Command

02->Time-out time setting Command YYYY->SIO controller error status

bit15->An error was occurred bit10->Reception buffer size setting was too big bit9 ->Disconnection error

5921-E P-27

SECTION 2 ALARM P

bit8 ->Modulation code error bit7 ->CRC error

bit6 ->Format error

bit5 ->Double transmission error bit4 ->Double reception error

bit3 ->Parity error was occurred when SIO controller read transmission buffer bit2 ->Parity error was occurred when CPU read transmission buffer

bit1 ->Parity error was occurred when CPU read reception buffer bit0 ->Time-out error

0x23XXYYYY->Error command was received while initialization of SIO link XX->SIO link slave address which error was detected

YYYY->Error status

bit15->An error was occurred bit10->Reception buffer size setting was too big bit9 ->Disconnection error

bit8 ->Modulation code error bit7 ->CRC error

bit6 ->Format error

bit4 ->Double reception error

bit3 ->Parity error was occurred when SIO controller read transmission buffer bit2 ->Parity error was occurred when CPU read transmission buffer

bit1 ->Parity error was occurred when CPU read reception buffer bit0 ->Time-out error

0x24XX00YY->Illegal command was received while initialization of SIO link XX->Expecting command

XX->Reception command

0x25XX0000->Safety IO slave information did not match the scan file list XX->Mismatch frame offset

0x2F000000->SIO link was disconnected

0x31000000->The command was not received within a specific period 0x3200XXXX->Communication error was detected by the MF-SAFETY

XXXX->SIO controller error status bit15->An error was occurred

bit10->Reception buffer size setting was too big bit9 ->Disconnection error

bit8 ->Modulation code error bit7 ->CRC error

bit6 ->Format error

bit5 ->Double transmission error bit4 ->Double reception error

bit3 ->Parity error was occurred when SIO controller read transmission buffer bit2 ->Parity error was occurred when CPU read transmission buffer

bit1 ->Parity error was occurred when CPU read reception buffer bit0 ->Time-out error

0x33XXYYYY->Error command was received in SIO link safety frame XX->SIO link slave address which error was detected YYYY->Error status

bit15->An error was occurred bit10->Reception buffer size setting was too big bit9 ->Disconnection error

bit8 ->Modulation code error bit7 ->CRC error

bit6 ->Format error

bit4 ->Double reception error

bit3 ->Parity error was occurred when SIO controller read transmission buffer bit2 ->Parity error was occurred when CPU read transmission buffer

bit1 ->Parity error was occurred when CPU read reception buffer bit0 ->Time-out error

0x34XX0000->Safety protocol could not be established on the SIO link XX->slave address

0x35XXYYZZ->Could not communicate safety SIO frame, after established safety protocol XX->slave address

YY->

00->Reset command was received

01->Unexpected command was received

02->Undefined command was received

03->Connection ID was in err

04->CRC error

5921-E P-28

SECTION 2 ALARM P

08->FailSafeData command was received ZZ->Reception safety data

0x36000000->Safety transmission data was mismatch between CPU0 and CPU1 0x37XX0000->Safety frame was not renewal

XX->slave address

0x3FXXYYZZ->Safety physical output data was mismatch between CPU0 and CPU1 XX->Index of physical output

YY->Output data in CPU0 ZZ->Output data in CPU1

0x41X000YY->An error was occurred in MFU I/O unit X->Slot number

YY->I/O unit error status <MF-EC1>

bit7->Overcurrent Protection circuit was worked in output circuit bit6->Overcurrent protection was occurred in input circuit bit4->I/O bus check error

bit2->Data was mismatched between order and monitor bit1->A parity error was occurred when I/O bus1 was written bit0->A parity error was occurred when I/O bus0 was written <MF-P2A16S>

bit6->Overcurrent protection was occurred in input circuit bit5->Self-check error

bit4->I/O bus check error <MF-P2M2S>

bit7->Overcurrent Protection circuit was worked in output circuit bit6->Overcurrent protection was occurred in input circuit bit4->I/O bus check error

bit2->Data was mismatched between order and monitor bit1->A parity error was occurred when I/O bus1 was written bit0->A parity error was occurred when I/O bus0 was written

0x42XYZZWW->MFU I/O unit input of CPU0 and CPU1 was mismatched longer than a specific period X->Slot number

Y->I/O unit safety input number (1-4) ZZ->Input data in CPU0

WW->Input data in CPU1

0x43XYZZWW->MFU I/O unit written data was mismatch between CPU0 and CPU1 X->Slot number

Y->I/O unit safety output number (1-4) ZZ->Output data in CPU0 WW->Output data in CPU1

[Probable Faulty Locations]

SIO link cables I/O unit in MFU MF-SAFETY I/O data file SIO slave unit

[Measures to Take]

Replace the SIO link cables Replace the MFU I/O unit Replace the MF-SAFETY unit Update the I/O data file Replace the SIO link slave unit

0759 Safety Servo Link Error

An error occurred in Safety Servo Link.

[Object] None

[Character-string] None

[Code]

0x50000000->Safety transmission data was mismatch between CPU0 and CPU1 in initialization of Servo link 0x51XX0000->Frame from slave was not received in initialization of Servo link

XX->axis ID

0x520XYYYY->Communication error was occurred in initialization of Servo link X->Servo link channel number

5921-E P-29

SECTION 2 ALARM P

YYYY->Servo controller error status bit15->An error was occurred bit11->Protect error

bit9 ->Disconnection error bit8 ->Modulation code error bit7 ->CRC error

bit6 ->Format error

bit4 ->Double reception error

bit3 ->Parity error was occurred when Servo controller read transmission buffer bit2 ->Parity error was occurred when CPU read transmission buffer

bit1 ->Parity error was occurred when CPU read reception buffer bit0 ->Time-out error

0x53XX0000->The response was not received within a specific period XX-axis ID

0x54XX0000->Safety protocol could not be established on the Servo link XX->axis ID

0x55XXYYZZ->Could not communicate safety Servo frame, after established safety protocol XX->slave address

YY->

00->Reset command was received

01->Unexpected command was received

02->Undefined command was received

03->Connection ID was in err

04->CRC error

08->FailSafeData command was received ZZ->Reception safety data

0x56000000->Safety Servo transmission data was mismatch between CPU0 and CPU1 0xFFFFXXXX

XXXX->world clock after the put a safety protocol

[Probable Faulty Locations] Servo link cables MF-SAFETY

Servo link slave unit

Axis construction definition file

[Measures to Take]

Replace the Servo link cables Replace the MF-SAFETY unit Replace the Servo link slave unit

Update the axis construction definition file

0782 Magnetic encoder speed detection error

The difference between speed feed back value and current frequency of Magnetic encoder was always observed, and there was a difference in excessive.

[Object] Axis

[Character-string] None

[Code] XXXXYYYY

XXXX=speed reference value(2B) YYYY=speed detect value(2B)

[Probable Faulty Locations] Magnetic encoder

[Corrective Action]

Change Magnetic encoder

0783 MCS Rotary encoder 5 initialization failure

It failed in initialization of Rotary encoder 5(Others).

[Object] Axis

[Character-string] None

5921-E P-30

SECTION 2 ALARM P

[Probable Faulty Locations]

Rotary encoder 5(Others).

[Corrective Action]

Change Rotary encoder 5(Others).

0784 MCS Rotary encoder 5 error

Illegal data was detected in Rotary encoder 5(Others).

[Object] Axis

[Character-string] None

[Probable Faulty Locations] Rotary encoder 5(Others).

[Corrective Action]

Change Rotary encoder 5(Others).

0785 MCS Rotary encoder 4 initialization failure

It failed in initialization of Rotary encoder 4(HEIDENHAIN).

[Object] Axis

[Character-string] None

[Probable Faulty Locations]

Rotary encoder 4(HEIDENHAIN).

[Corrective Action]

Change Rotary encoder 4(HEIDENHAIN).

0786 MCS Rotary encoder 4 error

Illegal data was detected in Rotary encoder 4(HEIDENHAIN).

[Object] Axis

[Character-string] None

[Probable Faulty Locations]

Rotary encoder 4(HEIDENHAIN).

[Corrective Action]

Change Rotary encoder 4(HEIDENHAIN).

0787 MCS Rotary encoder 3 initialization failure

It failed in initialization of Rotary encoder 3(HEIDENHAIN).

[Object] Axis

[Character-string] None

[Probable Faulty Locations]

Rotary encoder 3(HEIDENHAIN).

[Corrective Action]

Change Rotary encoder 3(HEIDENHAIN).

0788 MCS Rotary encoder 3 error

Illegal data was detected in Rotary encoder 3(HEIDENHAIN).

[Object] Axis

[Character-string]

5921-E P-31

SECTION 2 ALARM P

None

[Probable Faulty Locations]

Rotary encoder 3(HEIDENHAIN).

[Corrective Action]

Change Rotary encoder 3(HEIDENHAIN).

0789 MCS Rotary encoder 2 error

Illegal data was detected in Rotary encoder 2(INA-BEARING).

[Object] Axis

[Character-string] None

[Code]

XXXXYYYY

XXXX= Content of illegal data

000A[HEX] : illegal data of A aspect voltage 000B[HEX] : illegal data of B aspect voltage

YYYY= Illegal data

XXXX=000A[HEX] : A aspect voltage value XXXX=000B[HEX] : B aspect voltage value

[Probable Faulty Locations]

Rotary encoder 2(INA-BEARING).

[Corrective Action]

Change Rotary encoder 2(INA-BEARING).

0790 MCS Rotary encoder 1 initialization failure

It failed in initialization of Rotary encoder 1.

[Object] Axis

[Character-string] None

[Code]

XXYYZZZZ

Same with the alarm No. 0865 «MCS Encoder initialize failed»

[Probable Faulty Locations] Rotary encoder 1 Motor encoder

Encoder link cable & connector Control base of Inverter Unit

[Corrective Action]

Exchange & check on thing Above Unit

0791 MCS Rotary encoder 1 error

Illegal data was detected in Rotary encoder 1.

[Object] Axis

[Character-string] None

[Code] XXYYZZZZ

XX= Rotary encoder status bit7 alarm

bit6 communication error

8X The output amplitude is normal.

9X Output amplitude smallness AX Output amplitude bigness BX Output amplitude too small YY= Rotary encoder alarm code

5921-E P-32

SECTION 2 ALARM P

00 Unstart

01 Stop command stop

02 The control parameter is illegal.

0E Synchronous mistake

0F The excitation output is illegal.

11B face Ad offset Voltage decrease

12A face AD offset voltage decrease

13A and B face AD offset voltage decrease

15B face AD offset voltage decrease

16A face Ad offset voltage rise

17A and B face AD offset voltage rise

25B face signal amplitude is excessive

26A face signal amplitude is excessive

27A and B face signal amplitude is excessive.

29The signal amplitude is underestimates. 2D B face signal amplitude is underestimates. 2E A and signal amplitude is underestimates.

2F A and B face signal amplitude is underestimates.

80-FF CPU illegal

ZZZZ= Rotary encoder position data Positional data of each pitch

[Probable Faulty Locations] Rotary encoder 1

[Corrective Action]

Change Rotary encoder 1

0792 MCS Linear scale 4 initialization failure

It failed in initialization of Linear scale 4(Others).

[Object] Axis

[Character-string] None

[Probable Faulty Locations] Linear scale 4(Others).

[Corrective Action]

Change Linear scale 4(Others).

0793 MCS Linear scale 4 error

Illegal data was detected in Liner scale 4(Others).

[Object] Axis

[Character-string] None

[Probable Faulty Locations] Linear scale 4(Others).

[Corrective Action]

Change Linear scale 4(Others).

0794 MCS Linear scale 3 initialization failure

It failed in initialization of Linear scale 3(HEIDENHAIN).

[Object] Axis

[Character-string] None

[Probable Faulty Locations] Linear scale 3(HEIDENHAIN).

[Corrective Action]

Change Linear scale 3(HEIDENHAIN).

5921-E P-33

SECTION 2 ALARM P

0795 MCS Linear scale 3 error

Illegal data was detected in Liner scale 3(HEIDENHAIN).

[Object] Axis

[Character-string] None

[Probable Faulty Locations] Linear scale 3(HEIDENHAIN).

[Corrective Action]

Change Linear scale 3(HEIDENHAIN).

0796 MCS Linear scale 2 initialization failure

It failed in initialization of Linear scale 2(HEIDENHAIN).

[Object] Axis

[Character-string] None

[Probable Faulty Locations] Linear scale 2(HEIDENHAIN).

[Corrective Action]

Change Linear scale 2(HEIDENHAIN).

0797 MCS Linear scale 2 error

Illegal data was detected in Liner scale 2(HEIDENHAIN).

[Object] Axis

[Character-string] None

[Probable Faulty Locations] Linear scale 2(HEIDENHAIN).

[Corrective Action]

Change Linear scale 2(HEIDENHAIN).

0798 MCS Linear scale 1 initialization failure

It failed in initialization of Linear scale 1(MITUTOYO).

[Object] Axis

[Character-string] None

[Code] XXYYZZZZ

Same with the alarm No. 0865 «MCS Encoder initialize failed»

[Probable Faulty Locations]

Rotary encoder 1 Motor encoder

Encoder link cable & connector Control base of Inverter Unit

[Corrective Action]

Exchange & check on thing Above Unit

0799 MCS Linear scale 1 error

Illegal data was detected in Liner scale 1(MITUTOYO).

[Object] Axis

[Character-string]

5921-E P-34

SECTION 2 ALARM P

None

[Code]

XXYYZZZZ

XX= Liner scale 1 status bit7: alarm

bit6: communication error

bit2: communication error(every detection)

bit0: alarm code distinction bit (bit0=1: An alarm occurred in MITUTOYO scale.) YY=Liner scale 1

case of XX=88 bit7: over speed

bit6: communication error bit5: EEPROM error bit4: CPU error

bit3: electric capacity error bit2: photo electron error bit1: digit match error bit0: initialize error

case of XX=80

43:MITUTOYO scale no response

44:MITUTOYO scale ID error case of XX=C0

00-3F: Gateway receive error

46:REQ time over error

ZZZZ= Liner scale 1 position data position data of every 2mm pitch

[Probable Faulty Locations] Linear scale 1

[Corrective Action] Change Linear scale 1

0800 Spindle D/A control data file read

The NC failed to read the spindle D/A control data file.

[Code] XY

X: Gear set number (The number where the error occurred first.X does not appear if Y = 1 to 6.) Y=1 -> No data file

Y=2 -> Data file type is not PBU1. Y=3 -> Larger data file size

Y=4 -> Improper data file size

Y=5 -> Gear set number does not match the data file size. Y=6 -> Gear set number is not any of 1 to 4.

Y=7 -> Motor speed limit or spindle speed limit is 0. Y=8 -> Max spindle speed is 0.

[Probable Faulty Locations]

Spindle D/A control data file creation error

[Measures to Take]

Create a correct spindle D/A control data file.

0801 TCP/IP board detected error

During activation of DNC-T1, T2, T3,or DT function, a CPU error occurred on TCP/IP board

[Index] None

[Character-string] None

[Code] XXYYZZ

XX…Board status in hexadecimal

bit7 bit6 bit5 bit4 bit3 bit2 bit1 bit0

RUN HALT CPUOFF 0 SNMI 0 0 0 YY…Bus error status in hexadecimal

bit7 bit6 bit5 bit4 bit3 bit2 bit1 bit0

0806 MOP-Tool tool data PBU load

5921-E P-36

SECTION 2 ALARM P

The backup file (MMTUAuu.PBU) is not found, or its type or size is wrong.

[Code]

3->The tool data PBU file (MMTUAuu.PBU) is not found in MD0:.

4->The tool data PBU file (MMTUAuu.PBU) does not start from «PBU1» or has an improper file length (not $125 sectors).

[Probable Faulty Locations]

1)If the alarm occurred during NC operation, the PBU file has been deleted or its data has been destroyed.

2)If the alarm occurred without NC operation after installation of control floppy disk, the PBU file type was wrong or no PBU file was stored in the memory.

[Measures to Take]

1)If the alarm occurred during NC operation, reinstall the control floppy disk. 2)If the alarm occurred before NC operation, create a correct control floppy.

0807 ACP panel status receipt error

The ACP board received an abnormal operation panel status.

[Code]

XX (operation panel status data) bit7->Invalid panel status bit6->Operation panel CPU error

bit3 to 5->Software version applied to operation panel firmware bit0 to 2->Operation panel type

0808 Speed change ratio failure

On the machine with high speed profiling function,an improper speed change ratio is set on X, Y, Z, or Caxis or a wrong type of position encoder is used.

[Code]

1->Xaxis speed change ratio is set with a code. 2->Yaxis speed change ratio is set with a code. 3->Zaxis speed change ratio is set with a code. 4->Caxis speed change ratio is set with a code.

5->Xaxis speed change ratio exceeds the setting range. 6->Yaxis speed change ratio exceeds the setting range. 7->Zaxis speed change ratio exceeds the setting range. 8->Caxis speed change ratio exceeds the setting range. 9->A wrong type of position encoder is used.

[Probable Faulty Locations]

Speed change ratio data in the servo data PBU file,or encoder type

[Measures to Take]

Correct the servo data PBU file.

0810 NC I/O data file read

The NC failed to read I/O data file.

[Code]

I/O data file load status (in hexadecimal) 2->File open error (no file)

3->File read error (no data)

4->File attribute error (not «PBU1»)

5->File close error

6->File size error (too small)

7->File size error (too large)

100->Wrong PLC machine type

200->Wrong PLC class

300->Wrong file version

0812 MCS initialization error

An error occurred in initialization of MCS when the power was supplied.

[Index]

None or axis name

[Character-string] Varies with the code.

5921-E P-37

SECTION 2 ALARM P

[Code] XXXXYYYY

XXXX:Kind of generated alarm

YYYY:Further information on the alarm (Varies with XXXX.)

XXXX

FFFF…YYYY is 00UV. Where, U: Faulty channel number — 1 0= Channel 1

1= Channel 2 2= Channel 3

V: Cause of alarm (V=1 indicates that servo link mode has not been established.) FF01…Memory error occurred in read/write test of the servolink I/O buffer.

YYYY= 0 (always)

Character-string shows the address where the error occurred.

FF00…Communication LSI caused an error in read/write test of the servo link I/O buffer. YYYY= Error status

Character-string shows the address where the error occurred. F000…

YYYY=bit 7:Same ID number used bit 6:Improper ID number bit 5:Missing ID number

bit 4:Too many CH4 controllers bit 3:Too many CH3 controllers bit 2:Too many CH2 controllers bit 1:Too many CH1 controllers bit 0:

With this error, connection data appears in the screen center.

EF00…The servo link does not connect with all the required axes or connects with an improper axis. YYYY= ID number of required axis controller

Character-string shows the problem axis name.

With this alarm, connection data appears in the screen center. EE00…An error occurred in downloading an optional file.

High-order digit of

YYYY shows the cause while low-order part is an error code.

If high-order digit=

1:File is not in OSP format.

2:File attribute is not contiguous.

3:File opening error. Low-order part is an error code.

4:Error in initial data reading. Low-order part is an error code.

5:File does not start with «MCS1».

6:File name is not followed by «OPFS».

7:The number of file sets is 0.

8:Data reading error. Low-order part is an error code.

9:File data has a sector length of 0.

A:The number of bytes transferred is 0.

B:File data has a sector length smaller than the number of bytes transferred.

C:Data reading error. Low-order part is an error code.

ED00…An error occurred when manual mode is switched to auto mode. High-order digit of

YYYY shows the cause while low-order part is an error code. High order digit=1: World clock does not start. EC01…Time difference occurred in setting CH1 timer.

YYYY is the difference.

EC02…Time difference occurred in setting CH2 timer. YYYY is the difference.

EC03…Time difference occurred in setting CH3 timer. YYYY is the difference.

D001…In buffering the initial data in AT (auto) receive mode, the software synchronization bit does not come on within 3 seconds.

YYYY is always 0.

D002…In buffering the initial data in AT (auto) receive mode, the buffer A received a wrong format code. Two low-order characters of

YYYY are the received format code.

D003…In buffering the initial data in AT (auto) receive mode, the buffer B received a wrong format code in the first block. YYYY is the received format code.

D004…In buffering the initial data in AT (auto) receive mode, the buffer B received a wrong format code in the second block. YYYY is the received format code.

D005…In buffering the initial data in AT (auto) receive mode, the buffer B received a wrong format code in the third block. YYYY is the received format code.

D006…In buffering the initial data in AT (auto) receive mode, the buffer B received a wrong format code in the fourth block. YYYY is the received format code.

5921-E P-38

SECTION 2 ALARM P

D007…In buffering the initial data in AT (auto) receive mode, the buffer B received a wrong format code in the fifth block. YYYY is the received format code.

D008…In buffering the initial data in AT (auto) receive mode, the buffer B received a wrong format code in the sixth block. YYYY is the received format code.

D009…In buffering the initial data in AT (auto) receive mode, the buffer B received a wrong format code in the seventh block. YYYY is the received format code.

D00A…In buffering the initial data in AT (auto) receive mode, the buffer B received a wrong format code in the eighth block. YYYY is the received format code.

D010…In buffering the initial data in AT (auto) receive mode, the received self-diagnostic data is not $55. YYYY is the received diagnostic data.

D011…In buffering the initial data in AT (auto) receive mode, the buffer A received the bit data which is wrong at bit No. 0 and No. 1.

YYYY is the received data.

D012…In buffering the initial data in AT (auto) receive mode, the buffer A received the bit data which is wrong at bit No. 2 and No. 3.

YYYY is the received data.

D013…In buffering the initial data in AT (auto) receive mode, the buffer A received the bit data which is wrong at bit No. 4 and No. 5.

YYYY is the received data.

D080…Initial data buffered in AT (auto) receive mode includes wrong data at ID data No. 441C. YYYY is the received data.

D081…Initial data buffered in AT (auto) receive mode includes wrong data at ID data No. 2428. D090…Initial data buffered in AT (auto) receive mode includes wrong data at ID data No. 4405.

YYYY is the received data.

D091…Initial data buffered in AT (auto) receive mode includes wrong data at ID data No. 4404. YYYY is the received data.

D092…Initial data buffered in AT (auto) receive mode includes wrong offset data for compensating positioning points. YYYY is the received data.

[Probable Faulty Locations]

—Inverter unit (Check the LED of the inverter unit.)

—Improper ID number set in MCS

—Specification code setting error

—Erroneous connection with MCS

0813 MCS Communication error

When the power was supplied, an error occurred in communication with MCS.

If servo link information is displayed at the center of the screen, judge the cause by taking into consideration the message in the servo link information.

[Index] None

[Character-string]

[command name]-[channel No.]-network address (controller No.)

[Code] XXXXYYYY XXXX:

1…The NC received the data that the NC had broadcasted. YYYY: information of the received frame

2…Data is received from a station other than the slave station that broadcasted the data. YYYY: information of the received frame

3…The received data size is 2 bytes or less. YYYY: always 0

4…Data is received from a station other than the slave station that sent the date. YYYY: information of the received frame

5…The NC received the data that the NC had transmitted in a way other than broadcasting. YYYY: information of the received frame

6…Data is received from a the station of which network address is 0. YYYY: information of the received frame

7…Data reception response is not sent within 1 or 0.1 second after data transmission. YYYY: Always 0

‘SI’ command is specified before at least one MCS is normally activated in the link or before the power is supplied. Open the box and check the LEDs of all the MCS units connected to the error-caused channel.

Normal units are indicated with ’22’.

8…Data transmission does not end within 0.1 second. YYYY: Always 0

9…Communication error occurred after reception of data.

5921-E P-39

SECTION 2 ALARM P

YYYY: Error status

A…Communication error occurred while the NC was waiting for data reception or immediately after data transmission. YYYY: Error status

B…Communication error occurred while the NC was waiting for data transmission. YYYY: Error status

C…Data transmission was attempted during data transmission. YYYY: NC operation status

D…Data transmission was attempted in the state of communication error. YYYY: Error status

E…An error command was received.

Two high-order digits of YYYY are a code (45: exception; 41: alarm; 57: warning; 54: error) while low-order digits are the number.

[Refer to the shake-hand communication error list (5-10) in external specification for MCS controller function.] 100…The received first 2 bytes are improper as a response to the transmitted data.

YYYY: Received first 2 bytes

101…The received data size is improper as a response to the transmitted data.High-order digits of YYYY is the received data size while the low-order half is a normal value.

102…Data No. 1 attached to the received data is improper. YYYY: Two high-order bytes of the data judged to be improper SI command: slave station connection No.

AS command: slave station connection No.

ID command: communication code + auxiliary code 103…Data No. 2 attached to the received data is improper.

YYYY: Two high-order bytes of the data judged to be improper SI command: cumulative relay time

ID command: data ID

104…Data No. 3 attached to the received data is improper. YYYY: two high-order bytes of the data judged to be improper ID command: reserved

105…Data No. 4 attached to the received data is improper. YYYY: Two high-order bytes of the data judged to be improper ID command: ID data (4 bytes or less)

106…Data No. 5 attached to the received data is improper. YYYY: Two high-order bytes of the data judged to be improper SI command: The number of controllers

ID command: ID data (8 bytes)

200…Data sizes differ from those specified with ID numbers. Faulty software

[Probable Faulty Locations]

—Inverter unit (Check the LED of the inverter unit.)

—FCP board

—MCS connection error

—MCS connection cable is faulty

—Faulty software

0814 MCS data file corrupt

When the power was supplied, an error occurred in reading or transferring the servo link data file. Or, the data file includes abnormal data.

[Character-string]

[axis name] [device name] [file name] or none

[Code]

XYZZAAAA

X: Axis kind; Y: Rough classification; ZZ: Minute classification; AAAA: Data X:1= NC-controlled axis

2= spindle

3= PLC-controlled axis

Y:0= Error in reading servo data file ZZ:

01= Error occurred in retrieval of the file. AAAA=error code

AAAA indicates that the data file does not exist at 000B: or the required axis data does not exists in the file. 02= File attribute is not contiguous.

03= File is not in OSP format.

04= File opening error. AAAA=error code 05= File data reading error. AAAA=error code 06= File does not start with «PBU1».

0816 PLC initialization error

5921-E P-41

SECTION 2 ALARM P

An error was detected in the checking process for activating the PLC.

[Index] None

[Character-string] None

[Code]

XX

=1…NC-PLC synchronous parameter is not found.

[Measures to Take]

Consult the machine maker.

0817 MCS error

An error occurred under the control by MCS.

[Index]

Axis name or none

[Character-string] None

[Code] XXZZAAAA XYZZ: 0 AAAA:

1= Processing does not end within 5 seconds after MCS reset 1. 2= Processing does not end within 5 seconds after MCS reset 2.

3= Processing does not end within 5 seconds after PLC reset processing 1. 4= Processing does not end within 5 seconds after PLC reset processing 2. X: 1 to 3

X: Channel number

YZZAAAA: Communication error status [Probable Faulty Locations]

—Faulty MCS controller

—Faulty servo link on FCP board

—Faulty software

0818 ADP initialization failure

An alarm occurred while the AD conversion processor board was initialized after power ON.

[Object] None

[Character-string] None

[Code]

X

X=1:Synchronous counter value remains 1.

X=2:A system alarm occurred when the synchronous counter value was 1. X=3:Synchronous counter value remains 3.

X=4:A system alarm occurred when the synchronous counter value was 3.

[Probable Faulty Locations]

1 ADP(AD conversion processor board)

[Measures to Take]

Replace the ADP(AD conversion processor board).

[Related Specifications]

Thermal deviation compensation

0820 Machine data file read

At power on, the machine data file (GNCUB*.PBU) cannot be read from memory (sector device MD0A:) correctly.

[Object] None

[Character-string] None

0823 AXIS CONSTRUCTION DATA setting error