KE2010.Instruction Manual.Ver.2.01,Rev.08 - 第1334页

251 E691002 “Writ ing-in buf fer of flush memory does not get useable” [Cause] ‘W riting-in’ buf fer did not get useable when check ing its s tatus af ter a ‘writing-in’ com m and to flush m em or y was issued. • Flush m…

100%1 / 1361
250
E690028 “Resistance can no be measured. Please check if probe shuts
down properly”
[Cause] The tester overflowed data when measuring the resistance.
• The object(component) of the measurement is not contacting the probe.
• The contact between the object(component) of the measurement and the
probe is not good.
• The resistance of the object(component) of the measurement is exceeding the
measurement range.
• The Component Verification is broken.
[Treatment] • Please check and see if the object is contacting the probe well. If not, please
adjust the position of the object to contact the probe properly.
• Please check the object.
• If the error occurs when the contact is good, there is a possibility that the
Component Verification unit is broken. Please contact our technical service
dept. for information.
E690029 “Volume can not be measured. Please check if probe shuts down
properly”
[Cause] The tester overflowed data when measuring the condenser capacity.
• The object(component) of the measurement is not contacting the probe.
• The contact between the object(component) of the measurement and the
probe is not good.
• The resistance of the object(component) of the measurement is exceeding the
measurement range.
• The Component Verification is broken.
[Treatment] • Please check and see if the object is contacting the probe well. If not, please
adjust the position of the object to contact the probe properly.
• Please check the object.
• If the error occurs when the contact is good, there is a possibility that the
Component Verification unit is broken. Please contact our technical service
dept. for information.
E690030 “Voltage can not be measured. Please check if probe shuts down
properly”
[Cause] The tester overflowed data when measuring the diode polarity.
• The object(component) of the measurement is not contacting the probe.
• The contact between the object(component) of the measurement and the
probe is not good.
• The resistance of the object(component) of the measurement is exceeding the
measurement range.
• The Component Verification is broken.
[Treatment] • Please check and see if the object is contacting the probe well. If not, please
adjust the position of the object to contact the probe properly.
• Please check the object.
• If the error occurs when the contact is good, there is a possibility that the
Component Verification unit is broken. Please contact our technical service
dept. for information.
E691001 “Input/Output buffer status of CCL-48M does not get ready”
[Cause] The input/output buffer status of the backup table counter(CCL-48M) does not get
ready.
• Backup table counter is broken.
[Treatment] • Please turn off the power supply and re-boot your machine.
• If the error occurs even after the re-boot, there is a possibility that the Safety
board is broken. Please contact our technical service dept. for information.
251
E691002 “Writing-in buffer of flush memory does not get useable”
[Cause] ‘Writing-in’ buffer did not get useable when checking its status after a ‘writing-in’
command to flush memory was issued.
• Flush memory is broken.
[Treatment] • Please turn off the power supply and re-boot your machine.
• If the error occurs even after the re-boot, there is a possibility that the Safety
board is broken. Please contact our technical service dept. for information.
E691003 “Deleting cue of flush memory does not get useable”
[Cause] ‘Deleting’ cue did not get useable when checking its status after a ‘deleting’
command to flush memory was issued.
• Flush memory is broken.
[Treatment] • Please turn off the power supply and re-boot your machine.
• If the error occurs even after the re-boot, there is a possibility that the Safety
board is broken. Please contact our technical service dept. for information.
E691004 “WSM(Write State Machine) of flush memory does not get ready”
[Cause] ‘WSM’ did not get ready when checking its status after a command to flush
memory was issued.
• Flush memory is broken.
[Treatment] • Please turn off the power supply and re-boot your machine.
• If the error occurs even after the re-boot, there is a possibility that the Safety
board is broken. Please contact our technical service dept. for information.
E691005 “Write-in voltage range error occurred in flush memory control”
[Cause] An error occurred while checking the ‘Write-in’ voltage status after a command to
flush memory was issued.
The process was aborted since the ‘write-in’ voltage is too low.
• Flush memory is broken.
[Treatment] • Please turn off the power supply and re-boot your machine.
• If the error occurs even after the re-boot, there is a possibility that the Safety
board is broken. Please contact our technical service dept. for information.
E691006 “Write-in error occurred in flush memory control”
[Cause] An error occurred while checking the ‘device protecting’ status after a command
to flush memory was issued.
The process was aborted since the master lock bit, block lock bit, and RP# lock
were detected.
• Flush memory is broken.
[Treatment] • Please turn off the power supply and re-boot your machine.
• If the error occurs even after the re-boot, there is a possibility that the Safety
board is broken. Please contact our technical service dept. for information.
E691007 “Write-in error occurred in flush memory control”
[Cause] An error occurred while checking the ‘Write-in’ status after a command to flush
memory was issued.
An error occurred while writing data in.
• Flush memory is broken.
[Treatment] • Please turn off the power supply and re-boot your machine.
• If the error occurs even after the re-boot, there is a possibility that the Safety
board is broken. Please contact our technical service dept. for information.
252
E691008 “Command sequence error occurred in flush memory control”
[Cause] An error occurred while checking the status after a command to flush memory
was issued.
A command sequence error occurred.
• Flush memory is broken.
[Treatment] • Please turn off the power supply and re-boot your machine.
• If the error occurs even after the re-boot, there is a possibility that the Safety
board is broken. Please contact our technical service dept. for information.
E691009 “Lock Bit Set error occurred n flush memory control”
[Cause] An error occurred while checking the ‘lock bit set’ status after a command to flush
memory was issued.
An error occurred while setting the master/block lock bit.
• Flush memory is broken.
[Treatment] • Please turn off the power supply and re-boot your machine.
• If the error occurs even after the re-boot, there is a possibility that the Safety
board is broken. Please contact our technical service dept. for information.
E691010 “Lock Bit Clear error occurred in flush memory control”
[Cause] An error occurred while checking the ‘lock bit clear’ status after a command to
flush memory was issued.
An error occurred while clearing the lock bit.
• Flush memory is broken.
[Treatment] • Please turn off the power supply and re-boot your machine.
• If the error occurs even after the re-boot, there is a possibility that the Safety
board is broken. Please contact our technical service dept. for information.
E691011 “The check word for the common data of flush memory is
abnormal”
[Cause] The type of the common data that is saved in the flush memory is irregular.
The common data is not saved in the flush memory.
• Flush memory is broken.
[Treatment] • Please re-start the application.
• Please re-install or version up the application.
• If the error occurs even after the treatments above were performed, please
contact our technical service dept. for information.
E691012 “The checksum for the common data of flush memory is abnormal”
[Cause] The common data that is saved in the flush memory is irregular.
The common data of flush memory is broken.
• Flush memory is broken.
[Treatment] • Please re-start the application.
• Please re-install or version up the application.
• If the error occurs even after the treatments above were performed, please
contact our technical service dept. for information.