OSP-700L
OSP-700L Alarm P-2
ALARM P
********************************************************************************
900 SVP start conditions uncertain
900 SVP start conditions uncertain
Conditions for the SVP hardware/SVP software are not met, so the SVP cannot start.
Index: Axis
Character-string: None
Code: XYYZZZZ
X=1: Hardware-related conditions are not met.
YY=1: SVP board is not installed.
ZZZZ: 0000
YY=2: SVP status error.
ZZZZ: SVP status
YY=3: SVP hardware system bus error.
ZZZZ: System bus status
X=2: SVP data-related conditions are not met.
YY=1: Selected sync signal number is incorrect.
ZZZZ: Designated sync signal number
YY=2: Designation of sync offset time is incorrect.
ZZZZ: Designated sync offset time
X=3: Software-related conditions are not met.
YY=1: SVP software is not installed.
ZZZZ: 0000
YY=2: Servo parameters are not installed.
ZZZZ: 0000
Probable Faulty Locations:
1 SVP hardware for the axis
2 NC control software
3 NC specifications
901 SVP processing trouble
901 SVP processing trouble
A fault indicated by the following code occurred in the SVP.
Index: Axis
Character-string: None
Code: XYYZZZZ
X=1: Time out
SVP did not respond within 20 seconds after start-up. Cause requires detailed investigation.
Since the SVP itself cannot detect it, the start-up program is unexecutable.
YY=00
ZZZZ=000000
X=2: Double bus error
Another bus error occurred in the SVP during bus error exception processing.
High probability of SVP hardware failure.
YY indicates "System bus status".
ZZZZ=000000
X=3: SVP command execution
In the SVP, the diagnosis result of the CPU command execution diagnostic function is incorrect.
High probability of CPU failure.
YY indicates "Diagnostic result".
ZZZZ=000000
X=4: SVP fault detected by NC control software.
Some trouble occurred in the SVP.
Probable Faulty Locations:
1 SVP hardware for the axis
2 SVP software for the axis
3 NC control software
902 SVP CON APA deviation
902 SVP CON APA deviation
The deviation between CON and APA exceeded the specified allowable value.
CON/APA deviation is
(|[Calculated value written to SVP] - [Current position read from SVP]|)
This deviation is monitored on the NC control software side.
Normally, DIFF can be monitored on the SVP side; however, if a fatal error occurs in the SVP
and DIFF cannot be monitored, control will be lost. Therefore, this deviation is controlled on the control software side.
Index: Axis
Character-string: None
Code: Hexadecimal value of the absolute value of deviation [basic unit]
Probable Faulty Locations:
1 SVP for the axis
903 SVP error
903 SVP error
The NC software detected a system error notification signal generated by the SVP hardware.
For details, refer to the NC control software specification or the specification
corresponding to the installed SVP version.
Index: Axis
Character-string: None
Code: Alarm data
Probable Faulty Locations:
1 SVP software for the axis
904 SVP exception processing
904 SVP exception processing
A fatal error occurred during SVP software processing.
Index: Axis
Character-string: Detected error
“# 1”.........Bus error
“# 2”.........Address error
“# 3”.........Illegal instruction error
“# 4”.........Zero divide error
“# 5”.........CHK instruction error
“# 6”.........TRAPV instruction error
“# 7”.........Privilege violation error
“# 8”.........Trace error
“# 9”.........1010 emulation error
“# 10”.........1111 emulation error
“# 11”.........Unassigned area error
“# 12”.........Coprocessor protocol violation
“# 13”.........Format error
“# 14”.........Uninitialized interrupt
“# 15”.........Spurious interrupt error
“# 16”.........Interrupt error
“# 17”.........INT7 error
“# 18”.........Debugger break alarm
“# 19”.........INT2 loop error
“# 20”.........INT5 loop error
“# 21”.........Speed command calculation delay alarm
“# 22”.........TRAP error
“# 23”.........Floating-point coprocessor error
“# 24”.........PMMU error
“# 25”.........User interrupt error
“# 26”.........Processor board version error
“# 27”.........Memory test error
Code: Except for the following 2 "character-strings", the CPU program counter
value when the error occurred is displayed.
When the character-string is ”# 26”, the SVP hardware ID is displayed. When the character-string is ”# 27”, the memory address when the error was detected is displayed.
Probable Faulty Locations:
1 SVP board
2 SVP software
905 SVP APA pattern data
905 SVP APA pattern data
Pattern errors in the position data read from the position detector occurred consecutively.
Example) Code displays 8000
Convert to octal number
8000 (hexadecimal) -> 100000 (octal)
The E8 unit is 5 bits, so the 6th bit is ignored
Since all bits are 0, it can be determined that detector data is not being output.
Index: Axis
Character-string: None
Code: Pattern of read position data (upper bits of APA)
Probable Faulty Locations:
1 Position detector for the axis
2 SVP hardware for the axis
3 Timing signal of NC system
906 SVP APA speed
906 SVP APA speed
Since the position detector value (RAPA) changes as the motor rotates, the amount
of change in the position detector value is checked at fixed intervals.
The feedrate of each axis is compared with the normal rapid traverse rate. If the speed is abnormally fast
or the value changes abnormally due to a defective position detector, this alarm is issued
when the amount of change per unit time consecutively exceeds a specified allowable value.
Index: Axis
Character-string: None
Code: Hexadecimal value of the amount of change in the position detector value [basic unit/speed control period]
However, the following values have special meanings.
FFFFFFFF = Linear axis overtravel.
FFFFFFFE = Rotary axis overtravel (360 deg).
Or finite axis is negative.
FFFFFFFD = Finite axis overtravel.
Probable Faulty Locations:
1 Detector for the axis, or detector connection cable
2 Motor for the axis
3 D/U for the axis
4 SVP hardware for the axis
907 SVP CON speed
907 SVP CON speed
When an axis reaches the target value and stops, the target value, calculated value, and current position match.
However, after a new axis movement command is commanded, calculation of the new target value starts and
the calculated value (RCON) is computed. At the same time, the amount of change in this calculated value
is monitored at fixed intervals; if the amount of change varies abnormally for some reason and exceeds the
specified allowable value, this alarm is issued.
Index: Axis
Character-string: None
Code: Hexadecimal value of the absolute value of the speed command [detector unit/speed control period]
However, the following values have special meanings.
FFFFFFFF = NC protocol violation (timing specification).
FFFFFFFE = Speed command is greater than the overflow alarm level.
Or greater than the alarm detection level.
FFFFFFFC = SVP internal command position exceeds the detector assigned stroke.
Probable Faulty Locations:
1 Servo parameters for the axis
2 NC control software
3 SVP hardware for the axis
908 SVP DIFF over
908 SVP DIFF over
When an axis reaches the target value and stops, the target value, calculated value, and current position match.
However, after a new axis movement command is commanded, calculation of the new target value starts and
the calculated value (RCON) is computed. At this time, the current position follows the calculated value
with a certain delay. This delay amount (|[calculated value] - [current position]|) is called
following error. If this error amount exceeds a specified allowable value, this alarm is issued.
Index: Axis
Character-string: None
Code: Hexadecimal value of the absolute value of DIFF [detector unit]
Probable Faulty Locations:
1 Machine load is heavy due to defective ballscrew or bearing on the axis.
2 Detector, motor, or D/U for the axis
3 Servo parameters for the axis
4 SVP hardware for the axis
909 SVP servo amp
909 SVP servo amp
A fatal error occurred in the servo amplifier.
Index: Axis
Character-string: None
Code: YYZZ
YY = Internal error status
ZZ = Servo amplifier IF status
Probable Faulty Locations:
1 D/U for the axis
910 SVP APA check data
910 SVP APA check data
The upper bits read from the position detector do not match the upper bit data obtained after incremental calculation.
Example) Code displays 14E914A9
Convert to octal number (for F- and E-type detectors, the upper E8 unit uses octal carry)
12351 12251
Detected bit data Calculated data
Since the 3rd digit differs by 1, it can be determined that the cause of the error is the 3rd digit or the 2nd digit that outputs the carry signal (phase shift in gear coupling).
Index: Axis
Character-string: None
Code: YYYYZZZZ
YYYY = Hexadecimal value of upper bits read from the detector
Probable Faulty Locations:
1 Position encoder of the axis
2 SVP board of the axis
3 System synchronization signal section
Measures:
Convert the code to an octal number.
When all digits are shifted such as 12345, 23456, etc. ... The SVP board is defective in many cases.
When only the 1st digit is shifted such as 12345, 12344, etc. ... Defective MPR or bearing is suspected in many cases.
When occurring on multiple axes ... Defective synchronization signal section on the TFP board/SVP board is suspected in many cases.
911 SVP speed command over
911 SVP speed command over
The speed command value calculated on the SVP side consecutively exceeded the allowable value.
Note that the allowable value is the speed command overflow warning level.
Index: Axis
Character string: None
Code: Hexadecimal number of the absolute value of the speed command value when the error was detected [encoder units/speed control period]
Probable Faulty Locations:
1 Machine load is heavy.
2 Treat this in the same manner as the "SVP DIFF overflow" warning.
912 SVP servo data setting
912 SVP servo data setting
Servo data that the SVP cannot support was received. This warning is issued when the servo data set by the NC side has an abnormal value or cannot be received by the servo processor side.
If this warning occurs during maintenance servicing, it indicates that the compatibility between the servo parameter file and the SVP software does not match.
Index: Axis
Character string: None
Code: Servo data number
= 21 ......... Kv value
= 22 ......... Hardware servo coefficient
= 23 ......... Acceleration/deceleration coefficient
= 26 ......... HB control acceleration/deceleration coefficient
= 2B ......... Inductosyn special pitch
= 39 ......... Backlash compensation
= 3A ......... CON speed limit
= 3B ......... Gear ratio mantissa (linear)
= 3C ......... Gear ratio exponent (linear)
= 3D ......... Gear ratio (rotary)
= 41 ......... V-AMP output filter constant group
= 4F ......... New speed detection G1
= 50 ......... New speed detection G2
= 51 ......... New speed detection HPF constant
= 52 ......... New speed detection LPF constant
= 53 ......... Constant for 1st-stage acceleration/deceleration
= 54 ......... HB control constant
= 57 ......... Constant for 2nd-stage acceleration/deceleration
= 58 ......... Notch filter constant group
= 62 ......... Encoder resolution specification
= 71 ......... Amplifier communication baud rate
= 86 ......... DIFF.MIN (DIFF-G variable)
= 87 ......... DIFF.MAX (DIFF-G variable)
= 88 ......... ATTF calculation constant
= 89 ......... Integration limit value
= 100 ......... FLSUD switching timing error
= 101 ......... 1st-stage switching timing error
= 102 ......... 2nd-stage switching timing error
= 103 ......... exp switching timing error
= 104 ......... QITGMD switching timing error
= 105 ......... Interpolation method error
= FFFF ......... No permission
= FFFE ......... Infinite rotary axis
= FFFD ......... Infinite axis
= FFFC ......... Gear ratio
= FFFB ......... Speed control period
Probable Faulty Locations:
1 Servo parameter file of the axis
2 Control software such as NC
3 SVP software of the axis
913 SVP Belt is broken
913 SVP Belt is broken
A broken belt was detected on an SVP belt-driven axis.
Index: Axis
Character string: None
Code: Hexadecimal number of the load torque when the broken belt was detected.
914 SVP F-TYPE encoder error
914 SVP F-TYPE encoder error
The 1-revolution error compensation data cannot be set.
Index: Axis
Character string: None
Code: Indicates the cause why setting is impossible
1 Data read impossible
2 Data checksum error
4 Data overflow
5 Error compensation data zero point not returned
Probable Faulty Locations:
1 Position encoder of the axis
915 SVP full closed loop error
915 SVP full closed loop error
An error occurred in the deviation between the full-closed loop and semi-closed loop.
Index: Axis
Character string: None
Code: Number of times error was detected
Probable Faulty Locations:
1 Separate type position encoder or Inductosyn of the axis is faulty
2 Excessive backlash on the axis
3 Belt slip/broken belt on the axis
4 Combined compensation amount for the axis is not set or set improperly.
5 Position loop gain of the axis is improper (too high).
916 SVP F-TYPE encoder with shaft error
916 SVP F-TYPE encoder with shaft error
Setting of the rotation error compensation data for the F-type encoder with shaft is not possible.
Index: Axis
Character string: None
Code: Indicates the cause why setting is impossible
1 Data read impossible
2 Data checksum error
4 Data overflow
5 Error compensation data zero point not returned
Probable Faulty Locations:
1 Position encoder of the axis
917 SVP F with shaft APA pattern data
917 SVP F with shaft APA pattern data
The pattern of the position data read from the position encoder with shaft was consecutively faulty.
Index: Axis
Character string: None
Code: Pattern of the read position data (APA high order).
Probable Faulty Locations:
1 Position encoder of the axis
2 SVP hardware of the axis
3 Timing signal of the NC system
918 SVP cannot plant error offset data
918 SVP cannot plant error offset data
In the extended pitch error compensation specifications, the SVP memory capacity for storing data is insufficient.
Index: Axis
Character string: None
Code: None
Probable Faulty Locations:
1 SVP board controlling the axis
2 Extended pitch error compensation data or extended pitch error compensation file of the axis
919 SVP encoder application (MOTOR SHAFT)
919 SVP encoder application (MOTOR SHAFT)
The model of the position encoder mounted on the motor does not satisfy the requirements of the encoder resolution specification data.
Index: Axis
Character string: None
Code: None
920 SVP encoder application (WITH SHAFT)
920 SVP encoder application (WITH SHAFT)
The model of the position encoder mounted on the shaft does not satisfy the requirements of the encoder resolution specification data.
Index: Axis
Character string: None
Code: None
921 SVP collision detection
921 SVP collision detection
A collision between the SVP drive mechanism and an object was detected.
Index: Axis
Character string: None
Code: YYYYZZZZ
YYYY ... Average motor output torque
ZZZZ ... Average motor acceleration
922 SVP SA overload
922 SVP SA overload
The protection curve set on the SVP control software side was exceeded, and the servo amplifier overheated.
Index: Axis
Character string: None
Code: YYYYZZZZ
YYYY ... gamma of the detected overload protection curve
ZZZZ ... theta [n] at overload detection
Probable Faulty Locations:
1 Servo amplifier of the axis
923 SVP SA communication error
923 SVP SA communication error
Index: Axis
Character string: None
Code: Value indicating the cause of the error
1 ... Parity error occurred in the SVP.
2 ... Transmitted data does not match received data.
3 ... Servo amplifier ID is incorrect, reception is disabled.
4 ... Transmission from the servo amplifier did not arrive.
5 ... Parity check error occurred in the servo amplifier.
Probable Faulty Locations:
1 Servo amplifier of the axis
↑0607 key to here
924 SVP SA version error **↓Start from here**
924 SVP SA version error
When checking the version according to the amplifier version management specifications, it was found that the version of the actually installed servo amplifier is higher than the version supported by the SVP software.
Index: Axis
Character string: None
Code: Version data
10000000 ... BL-D is equipped, but BL-D is installed.
XXYYZZ:
XX: SVP version
YY: Servo amplifier version supported by the SVP
ZZ: Servo amplifier version
Probable Faulty Locations:
1 Servo amplifier of the axis
925 SVP SA motor cable overcurrent
925 SVP SA motor cable overcurrent
The servo amplifier detected excessive current flowing through the motor power cable.
The alarm LED "IOCM" on the servo amplifier illuminates.
Index: Axis
Character string: None
Code: None
Probable Faulty Locations:
1 Servo amplifier of the axis
926 SVP SA inverter bridge short circuit
926 SVP SA inverter bridge short circuit
A short circuit in the servo amplifier inverter bridge circuit was detected.
The alarm LED "IOCS" on the servo amplifier illuminates.
Index: Axis
Character string: None
Code: None
Probable Faulty Locations:
1 Servo amplifier of the axis
927 SVP SA overheating
927 SVP SA overheating
Overheating of the servo amplifier was detected.
The alarm LED "SVTH" on the servo amplifier illuminates.
Index: Axis
Character string: None
Code: None
Probable Faulty Locations:
1 Servo amplifier of the axis
928 SVP SA power circuit overvoltage
928 SVP SA power circuit overvoltage
Overvoltage was detected in the power supply circuit of the servo amplifier.
The alarm LED "HV" on the servo amplifier illuminates.
Index: Axis
Character string: None Code: None
Probable Faulty Locations:
1 Servo amplifier of the axis
929 SVP SA power circuit low voltage
929 SVP SA power circuit low voltage
Low voltage was detected in the power supply circuit of the servo amplifier.
The alarm LED "LV" on the servo amplifier illuminates.
Index: Axis
Character string: None
Code: None
Probable Faulty Locations:
1 Servo amplifier of the axis
930 SVP SA regenerative resistor overheat
930 SVP SA regenerative resistor overheat
Excessive power consumption of the servo amplifier regenerative resistor was detected.
The servo amplifier alarm lamp "DROH" lights.
Index: Axis
Character-string: None
Code: None
Probable Faulty Locations:
1 Servo amplifier of the axis
931 SVP SA control circuit power voltage
931 SVP SA control circuit power voltage
The voltage supplied to the servo amplifier control circuit was detected to deviate from the specified voltage.
The servo amplifier alarm lamp "VR" lights.
Index: Axis
Character-string: None
Code: None
Probable Faulty Locations:
1 Servo amplifier of the axis
932 SVP SA error
932 SVP SA error
Some error occurred in the servo amplifier. For details, refer to the specifications corresponding to the installed SVP
or servo amplifier version.
Index: Axis
Character-string: None
Code: None
Probable Faulty Locations:
1 Servo amplifier of the axis
933 SVP board version error
933 SVP board version error
The SVP hardware version is not the specified version.
Index: Axis
Character-string: None
Code:
1 = SVP hardware ID is not 1.
Probable Faulty Locations:
1 SVP board controlling the axis
934 SVP control error
934 SVP control error
An error occurred in SVP control. For details, refer to the specifications corresponding to the installed SVP version.
Index: Axis
Character-string: None
Code: Alarm data
Probable Faulty Locations:
1 SVP software of the axis
935 SVP data file read
935 SVP data file read
Data could not be read from the MSU file at NC startup.
Index: None
Character-string: None
Code: 1: The MSU file does not exist.
2: Sector DB0 of the MSU file is not ’PBU1’.
3: No end code in the MSU file.
Measures to Take:
● Re-create the MSU file.
● Re-install the control floppy disk.
936 SVP data file data address
936 SVP data file data address
The installation address of the PBU file "MSU**....PBU" for the servo processor is
an invalid servo processor address.
Index: None
Character-string: None
Code: Indicates the faulty installation address.
Probable Faulty Locations:
Defective MSU file (number of axes does not match specifications, MSU file creation error, etc.)
Measures to Take:
Re-create the MSU file.
937 SVP data file check
937 SVP data file check
1) In the servo data file MSU0*-**-*.PBU, the following item is incorrect.
1. The rotary axis/linear axis specification in the MSU file differs from the specification defined in the specification code file.
2) The definition of the number of control axes differs from the definition of the number of additional axes.
The number of actually installed axes is less than the defined number of axes.
Index: None
Character-string: None
Code: XYYZZ
When X = 1: Servo data file differs from specification code
YY = 00: X-axis
= 01: Y-axis
= 02: Z-axis
= 03: 4th axis
= 04: 5th axis
ZZ = 00: Linear axis
= 01: Rotary axis
When X = 2: Additional axis definition in specification code differs from number of additional axes
YY = Number of additional axes
ZZ = NC specification code No. 14
Measures to Take:
1) Check the servo data file or specification code file, and correct it.
2) Match the additional axis definition in the specification code file with the number of additional axis names.
—————————————–aaaaaaaa
938 VAC start
938 VAC start
At power-on, an error occurred in the VAC communication protocol.
Code: XXXXYYYY
Error code Error description
XXXXYYYY
1001FFFF The operation to establish the VAC data loop was not completed within 20 seconds.
1002**** A communication error occurred during the operation to establish the VAC data loop.
The lower 2 bytes indicate the error status. (Refer to Appendix)
2001FFFF Communication timeout error occurred on the 1st data file transfer command during 1st data file transfer.
2002**** Communication error occurred on the 1st data file transfer command during 1st data file transfer. The lower 2 bytes indicate the error status. (Refer to Appendix)
2101FFFF Communication timeout error occurred on the 1st data file transfer request during 1st data file transfer.
2102**** Communication error occurred on the 1st data file transfer request during 1st data file transfer. The lower 2 bytes indicate the error status. (Refer to Appendix)
2103**** Unrequested data was sent from VAC in response to the 1st data file transfer request during 1st data file transfer. The lower 2 bytes indicate the sent data.
2201FFFF Communication timeout error occurred during transfer of 1 sector of the 1st data file during 1st data file transfer.
2202**** Communication error occurred during transfer of 1 sector of the 1st data file during 1st data file transfer. The lower 2 bytes indicate the error status (Refer to Appendix).
2301FFFF Communication timeout error occurred during reception check of 1 sector of the 1st data file during 1st data file transfer.
2302**** Communication error occurred during reception check of 1 sector of the 1st data file during 1st data file transfer. The lower 2 bytes indicate the error status.
(Refer to Appendix)
2303**** Unrequested data was sent from VAC during reception check of 1 sector of the 1st data file during 1st data file transfer. The lower 2 bytes indicate the sent data.
24002310 NG command retry error (3 times) occurred during reception check of 1 sector of the 1st data file during 1st data file transfer.
4001FFFF Communication timeout error occurred on the VAC initialization data transfer command during VAC initialization data transfer.
4002**** Communication error occurred on the VAC initialization data transfer command during VAC initialization data transfer. The lower 2 bytes indicate the error status.
(Refer to Appendix)
4101FFFF Communication timeout error occurred on the VAC initialization data transfer request during VAC initialization data transfer.
4102**** Communication error occurred on the VAC initialization data transfer request during VAC initialization data transfer. The lower 2 bytes indicate the error status.
(Refer to Appendix)
4201FFFF Communication timeout error occurred during VAC initialization data transfer.
4202**** Communication error occurred during VAC initialization data transfer. The lower 2 bytes indicate the error status (Refer to Appendix).
4301FFFF Communication timeout error occurred during reception check of VAC initialization data transfer.
4302**** Communication error occurred during reception check of VAC initialization data transfer. The lower 2 bytes indicate the error status (Refer to Appendix).
4303**** Unrequested data was sent from VAC during reception check of VAC initialization data transfer. The lower 2 bytes indicate the sent data.
5001FFFF Communication timeout error occurred on the synchronization establish command during synchronization establishment.
5002**** Communication error occurred on the synchronization establish command during synchronization establishment. The lower 2 bytes indicate the error status. (Refer to Appendix)
5101FFFF Communication timeout error occurred on the synchronization establish request during synchronization establishment.
5102**** Communication error occurred on the synchronization establish request during synchronization establishment. The lower 2 bytes indicate the error status. (Refer to Appendix)
5201FFFF During synchronization establishment, previous transmission was not completed in synchronization signal transmission.
5202**** Communication error occurred in synchronization signal transmission during synchronization establishment. The lower 2 bytes indicate the error status. (Refer to Appendix)
5301FFFF Synchronization establish response was not returned from VAC during synchronization establishment.
5302**** Communication error occurred during reception check of synchronization establish response during synchronization establishment. The lower 2 bytes indicate the error status. (Refer to Appendix)
5401FFFF During inter-axis synchronization, previous transmission was not completed in inter-axis synchronization command.
5402**** Communication error occurred on the inter-axis synchronization command during inter-axis synchronization. The lower 2 bytes indicate the error status. (Refer to Appendix)
5501FFFF During inter-axis synchronization, previous transmission was not completed in inter-axis synchronization request.
5502**** Communication error occurred on the inter-axis synchronization request during inter-axis synchronization. The lower 2 bytes indicate the error status. (Refer to Appendix)
5601FFFF During inter-axis synchronization, previous transmission was not completed in inter-axis synchronization (A) transmission.
5602**** Communication error occurred in inter-axis synchronization (A) transmission during inter-axis synchronization. The lower 2 bytes indicate the error status. (Refer to Appendix)
5701FFFF During control ready, previous transmission was not completed in control ready command.
5702**** Communication error occurred on the control ready command during control ready. The lower 2 bytes indicate the error status. (Refer to Appendix)
1FFFF During control ready, control ready completion notification was not returned from VAC.
2**** During control ready, communication error occurred in control ready completion notification check. The lower 2 bytes indicate the error status. (Refer to Appendix)
FF0000** The control status of the control ready completion notification sent from VAC is alarm status. The lower 1 byte indicates the VAC alarm number.
FE0000** The self-diagnostic data of the control ready completion notification sent from VAC is not $55. The lower 1 byte indicates the sent self-diagnostic data.
F001**** An error occurred in the read/write test of the communication buffer.
The lower 2 bytes indicate the error relative memory address.
F002**** A communication LSI error occurred in the read/write test of the communication buffer.
The lower 2 bytes indicate the error status. (Refer to Appendix)
Appendix) Error status
bit 15: Double transmission error
bit 14: Double reception error
bit 13: Framing error
bit 12: CRC error
bit 11: Parity error
Probable Faulty Locations:
●SPC6 board
939 VAC data file read
939 VAC data file read
940 Time sharing task control
940 Time sharing task control
Time sharing task cannot be controlled.
Index: None
Character-string: None
Code: Hexadecimal number of supervisory stack No. 8 at interrupt occurrence.
Probable Faulty Locations:
●Main board PTM (programmable timer) malfunction.
●Software defect.
941 Real time task control
941 Real time task control
When the real-time task control interrupt is ON, supervisory status continues
until the next real-time task control interrupt occurs, disabling real-time task control.
Index: None
Character-string: None
Code: Hexadecimal number of supervisory stack data No. 8 when interrupt is ON.
Probable Faulty Locations:
●Timing board (or axis processor) defect.
●Software defect.
942 Real time task loop error
942 Real time task loop error
943 Main processor name incorrect
943 Main processor name incorrect
944 Slave processor name incorrect
944 Slave processor name incorrect
945 Memory board / battery life
945 Memory board / battery life
946 TFP illegal
946 TFP illegal
947 TFP data file read
947 TFP data file read
948 TFP Field net communication error
948 TFP Field net communication error
949 IO DIAGNOSTICS data file read
949 IO DIAGNOSTICS data file read
950 IO MACRO data file read
950 IO MACRO data file read
951 SMP illegal
951 SMP illegal
952 Processor Board not equip
952 Processor Board not equip
953 Machine control processor start
953 Machine control processor start
At power-on, EC-P does not operate normally, generating an exception alarm.
Index: None
Character-string: None
Code: XXYY
XX: EC-P exception alarm code
YY: EC-P alarm data
Probable Faulty Locations:
EC-P board defect
954 Peripheral processor start
954 Peripheral processor start
At NC startup, the external processor does not respond after a predetermined time (20 sec) has elapsed.
Index: None
Character-string: None
Code: XY
X=1...EC processor
=2...Axis processor
=3...Servo processor
=4...SUB-CPU
Y=Internal sequence at startup
Probable Faulty Locations:
●Hardware defect
●Initialization data for each processor (PBU file data)
Program Example:
None
Operation Example:
None
Measures:
●Check the initialization data of the processor indicated by the alarm code.
●Check hardware.
●Based on the alarm code, check which external processor is involved or check the timing counter.
955 Spec. code: data file
955 Spec. code: data file
Code: AXXYYZZ
A: 1No spec code protection file
2 Attributes/sector size of spec code protection file
2 Machine serial number mismatch in spec code protection file
3 Machine model name mismatch in spec code protection file
4 Spec code data mismatch in spec code protection file
XX: Mismatched byte position of spec code in spec code protection file
YY: Mismatched data of spec code in spec code protection file
ZZ: Spec code data in spec code protection file (before change)
956 Backup data file read
956 Backup data file read
Backup file (MAU, MDU, MBU) does not exist. File type is different, or file
length is different.
MBU0(4)-**-*.PBU (Backup file for interactive mode)
MDU0(7)-**-*.PBU (For system parameters)
MAU0(7)-**-*.PBU (For general data/parameters)
Index: None
Character-string: None
Code: 1: MAU or MBU (only in interactive mode) does not exist.
2: Type of MAU or MBU is not 'PBU1'.
3: Length of MAU or MBU is too long.
Length of MAU or MBU is too short.
11: MDU does not exist.
12: Type of MDU is not 'PBU1'.
13: MDU is too long.
14: MDU is too short.
21: Although MRU does not exist, the additional head rotation compensation spec code is active.
Or although MRU exists, the additional head rotation compensation spec code is inactive.
31: Although MVU does not exist, the high-precision VAC (Type A) spec code is active.
Or although MVU exists, the high-precision VAC (Type A) spec code is inactive.
Probable Faulty Locations:
1. When NC was operating normally before alarm occurrence
The PBU file was deleted, or contents of the PBU file were corrupted.
2. When alarm occurs without operating even once after control floppy disk installation
PBU file type mismatch, or PBU file missing.
957 Graphic Backup data file read
957 Graphic Backup data file read
958 Pitch compensate data file read
958 Pitch compensate data file read
Although pitch error compensation specification or Inductosyn compensation specification is provided, the pitch error compensation data (MAT0...POL) file does not exist in non-volatile
memory at power-on.
Index: None
Character-string: None
Code: FFFFFFFF: Compensation data file does not exist.
Codes other than above: Error in compensation data size in compensation data file.
Probable Faulty Locations:
Pitch error compensation data file
Measures:
Reinstall the control floppy disk.
959 IGF Specification unmatching
959 IGF Specification unmatching
960 IGF Backup data file read
960 IGF Backup data file read
961 IGF illegal
961 IGF illegal
962 CCP Loader file load
962 CCP Loader file load
When communication for DNC-C specification is ON, the load module file for the CCP loader
cannot be loaded.
Index: None
Character-string: None
Code: 1...No CCP loader software (CLA*.LOB).
2...CCP loader software is not 'LOB1'.
3...Error in load address information of CCP loader software.
4...CCP loader cannot be read normally.
5...Collation check mismatch after loading CCP loader.
Probable Faulty Locations:
●Defective creation of the load module file "CLA*.LOB" for the CCP loader
●When Code = 4: Software defect.
●When Code = 5: CCP board defect.
963 CCP Application file load
963CCP Application file load
When communication for DNC-C specification is ON, the load module file for the CCP application
cannot be loaded.
Index: None
Character-string: None
Code: 1...No CCP software (CBA*.LOB).
2...CCP software is not 'LOB1'.
3...Error in load address information of CCP software.
4...CCP software cannot be read normally.
5...Collation check mismatch after loading CCP software and setting area.
964 CCP Parameter file load
964 CCP Parameter file load
When communication for DNC-C specification is ON, data cannot be read from the backup files (MHU, MIU).
Index: None
Character-string: None
Code: 1...Online changeable data file (MHU*.PBU) does not exist.
Or communication parameter data file (MIU*.PBU) does not exist.
2...Type of online changeable data file is not 'PAR1'.
Or type of communication parameter data file is not 'PAR2'.
Probable Faulty Locations:
●Defective creation of online changeable data file "MHU*.PBU" or communication parameter
data file "MIU*.PBU"
965 Configuration file format error
965 Configuration file format error
966 Configuration file open error
966 Configuration file open error
967 Array limit check table is bad
967 Array limit check table is bad
When setting the array limit table for array-type system variables according to the spec code, the system variable number to be set
exceeds the table range.
Index: None
Character-string: None
Code: None
Measures:
In MMSC
Check CQARCKT1 and CQARCKT2.
Verify whether the code at alarm occurrence is registered in the table as a system variable number.
968 No specification
968 No specification
In I-MAP, although pattern machining cycle specification is not provided, the POL file for additional milling cycle
or full circle cycle is present.
Index: None
Character-string: None
Code: 1: No pattern machining cycle specification, but full circle and additional pattern cycles are present.
2: No pattern machining cycle specification, but additional pattern cycle is present.
Measures:
Recheck specifications.
969 Memory size is not same
969 Memory size is not same
Operation buffer length does not match actual installed RAM capacity.
[Table] Actually installed RAM and operation buffer correspondence table
Mounted RAM Operation buffer Operation buffer spec code
512K 80m PSCOD24.12z =0
1M 160 " bit0: ON
320 " bit1: ON
2M 640 " bit2: ON
1280 " bit3: ON
2560 " bit4: ON
Index: None
Character-string: None
Code: 1 only
Probable Faulty Locations:
- Actually installed RAM and operation buffer do not match the above table.
Measures to Take:
- Change the spec code.
- If the spec code is correct, change the RAM capacity according to the above table.
Up to here 0609
From here starts
970 Synchronous axis specification code
970 Synchronous axis specification code
Setting error in the spec code specifying the synchronous axis.
1. More than 6 axes including slave axes.
2. Rotary axis is specified as synchronous axis.
Index: None
Character-string: None
Code: For 1 digit: In the case of 1. above
Total number of axes including slave axes
For 2 digits: In the case of 2. above
Axis index specifying the rotary axis
60: 4th axis
80: 5th axis
Probable Faulty Locations:
- Spec code error
Measures to Take:
- Recreate the spec code.
Related Specifications:
Synchronous axis specification
971 Cache data / initialization error
971 Cache data / initialization error
An error occurred during cache data operation initialization processing.
Index: None
Character-string: None
Code: XYYYY
X=1: Occurred in "Initialize 1st Master" macro program
X=2: Occurred in "Initialize Nth Master" macro program
YYYY=0001: TRAP transition info error
YYYY=0010: Error termination
972 SVP INDEXING high-speed indexing over
972 SVP INDEXING high-speed indexing over
973 SVP INDEXING low-speed indexing over
973 SVP INDEXING low-speed indexing over
974 SVP INDEXING unclamp time over
974 SVP INDEXING unclamp time over
975 SVP INDEXING clamp time over
975 SVP INDEXING clamp time over
976 SVP INDEXING positioning direction
976 SVP INDEXING positioning direction
977 SVP INDEXING incorrect command
977 SVP INDEXING incorrect command
978 SVP INDEXING servo data setting
978 SVP INDEXING servo data setting
979 SVP INDEXING servo amp motion error
979 SVP INDEXING servo amp motion error
981 SVP LE sum check error
981 SVP LE sum check error
982 SVP LE data error
982 SVP LE data error
983 SVP LE incre. abso. error
983 SVP LE incre. abso. error
984 SVP LE comparator AD error
984 SVP LE comparator AD error
985 SVP LE face rotation error
985 SVP LE face rotation error
986 SVP LE initial transfer data error
986 SVP LE initial transfer data error
987 SVP LE application error
987 SVP LE application error
988 Cache data operation error termination
988 Cache data operation error termination
An error occurred during cache data operation.
Index: None
Character-string: None
Code: XYYYY
X=1: Cache data operation registration processing
X=2: Cache data operation read processing
YYYY=0001: TRAP transition info error
YYYY=0020: Invalid argument value
YYYY=0021: Registering already registered variable
YYYY=0022: Variable registration table full, cannot register
YYYY=0040: Invalid argument value
YYYY=0041: No read variable name
YYYY=0042: Read length mismatch
YYYY=0043: Data type mismatch
989 CPU information table data incorrect
989 CPU information table data incorrect
990 Task making error
990 Task making error
Task creation failed.
Index: None
Character-string: Task name
Code: XXXXYYYY
XXXX: Task ID that failed to create
YYYY=1...Task ID error (target task already exists)
=2...No TCB area (number of tasks exceeds 16)
0610 up
From here starts down
991 Task information table data incorrect
991 Task information table data incorrect
Task information table value is 0.
Index: None
Character-string: None
Code: XXYYZZZZ
XX: Master processor number where error was detected
=1...1st master board
=2...2nd master board
=3...3rd master board
=4...4th master board
=5...5th master board
=6...6th master board
YY=1...Application info 1st table
=2...Application info 2nd table
=3...Application info 3rd table
=4...Application info 4th table
=5...Application info 5th table
ZZZZ: Table index value
992 PLC backup data file reading
992 PLC backup data file reading
996 PLC axis data file
996 PLC axis data file
997 PLC monitor backup data file reading
997 PLC monitor backup data file reading
998 PLC sequence program load
998 PLC sequence program load
999 Synchronous taps’s data file read
999 Synchronous taps’s data file read