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

252 E691008 “Command sequence error occurred in f lush memory control” [Cause] An er ror occ urred while check ing the status after a c om m and to flush m em or y was issued. A com m and sequence er ror oc curred. • Flu…

100%1 / 1361
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.
253
E691013 “The data version for the common data of flush memory is
abnormal”
[Cause] The version of the common data that is saved in the flush memory and the
version of the application are clashing with each other.
• The application was versioned up.
[Treatment]
E691014 “The data length for the common data of flush memory is abnormal”
[Cause] The data length of 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.
E691015 “The data kind for the common data is abnormal”
[Cause] Data type parameter is invalid.
[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.
E906001 “Memory allocation error”
[Cause] The working space can not be saved.
[Treatment] Please increase some more memory available to save the working space.
E906002 “Shared memory open error”
[Cause] The shared memory could not be open.
[Treatment] Please shut down the your machine and re-start it.
E906011 “Measurement result exceeds limit value. Check the MS parameter”
[Cause] An assemblage position offset of a measured head exceeded the limit value. The
limit is: -9.9999 through 9.9999
[Treatment] System error
Please check the MS parameter.
E906021 “Return to home has not yet been completed”
[Cause] The axis has not yet been returned to home.
[Treatment] Please perform the Return to home with ORIGIN switch.
E906022, “Servo is in the free state”
[Cause] The axis could not move since the servo is not locked.
[Treatment] Please lock the servo with S-FREE switch.
E906031 “Selected device is not install. Please reselect other device on HOD”
[Cause] You could not go into the teaching mode since the device selected by HOD has