FAULT OVERVIEW• Fault is unexpected condition that had bad effect to the process • Whether it cause a major problem or minor • Depending on the application, it may not make all faults
Trang 1DAY 4
SESSION 3
Trang 2FAULT OVERVIEW
• Fault is unexpected condition that had bad effect to the
process
• Whether it cause a major problem or minor
• Depending on the application, it may not make all faults to shut down your entire system
• It can use a fault routine to clear a specific fault and let at least
some of the system continue to operate
• And also can be used to monitor a minor fault which is will not
shutdown the controller
Trang 3FAULT CONDITION
• According to the effect/severity caused by the fault it can be
classify to two condition
• Major Fault
• Minor Fault
• Major Fault is a fault condition that severe enough for the
controller to shutdown
• Minor Fault is a fault condition isn’t too severe for the
controller to shutdown
Trang 4MAJOR FAULT CONDITION
• By what does it caused, Major Fault can be classified to three
condition
• First is execution fault of an instruction
• Second is system fault including power loss, IO failure, task
watchdog,mode change, and motion axis
• The last is user defined error or fault
Trang 5MINOR FAULT CONDITION
• Minor Fault classify as the Minor system Fault and Minor
instruction Fault
• System Fault
• Periodic Task Overlap
• Load from nonvolatile Memory
• Problem with serial port
• Low Battery
• Instruction Fault
Trang 6MONITORING MINOR SYSTEM
FAULT
• Periodic Task Overlap: Monitoring the 6 bit from FAULTLOG
object MinorFaultBits Attribute
• Load from Nonvolatile memory: Monitoring the 7 bit from
FAULTLOG object MinorFaultBits Attribute
• Problem with the serial port: Monitoring the 9 bit from
FAULTLOG object MinorFaultBits Attribute
• Low Battery: Monitoring the 10 bit from FAULTLOG object
Trang 7MONITORING MINOR
INSTRUCTION FAULT
• Monitoring Minor Instruction Fault involving S:MINOR ,Minor
Fault Flag status register, for the Minor Fault Condition
• When S:MINOR set, which that mean an Minor Fault happened,
detail fault information is catch by GSV command
Trang 8CLEAR FAULT VIA MENU
• Saat processor mengalami fault, harus dicarikan dan dikoreksi
penyebabnya sebelum mencoba menghilangkan fault
• Jika penyebab belum ditemukan, processor akan berperilaku
yang tidak diharapkan.
• Jika processor MicroLogix 1000 atau ControlLogix 500
mengalami fault, harus dihilangkan fault-nya sebelum program
jalan Untuk menghilangkan fault pada processor, pilih Comms
> Clear Fault.
FAULTED
Trang 9CLEAR FAULT VIA STATUS
DISPLAY
Trang 10STATUS DISPLAY(1)
Trang 11STATUS DISPLAY(2)
Trang 12CONTROLLOGIX I/O ERROR(1)
• Karakter xx dalam kode menyatakan nomor slot dalam
hexadecimal(h)
• Jika slot secara eksak tidak bisa ditentukan,karakter xx menjadi
1F
• Kebanyakan fault I/O dapat direcoveri, dengan cara
mendisable slot(xx) yang bersangkutan pada user fault
routine
• Jika tidak didisable, processor akan fault pada akhir scan
• Modul I/O yang rusak dapat menyebabkan processor
mengindikasikan bahwa error ada pada slot 1 meskipun modul
Trang 13MAJOR AND MINOR CODE
Trang 14MAJOR FAULT TYPE AND CODE (1)
Trang 15MAJOR FAULT TYPE AND CODE (2)
Trang 16MAJOR FAULT TYPE AND CODE (3)
Trang 17MINOR FAULT TYPE AND CODE (1)
Trang 18MINOR FAULT TYPE AND CODE (2)
Trang 19SESSION 4