Page 38 of 44
10 Maintenance and Troubleshooting
Hardware Maintenance
Routine maintenance checks should be performed on the unit to avoid any risk of hardware problems. The EZ3-
TouchPLC Modular is designed to be a very rugged controller so that just a few checks periodically will help keep it up
and running.
The key points to be checked include:
Ambient operating conditions
Wiring and connections
Maintaining the Ambient Operating Conditions
Keeping the EZ3-TouchPLC Modular unit's environment within specified operating conditions is the best method to
minimize the maintenance.
1. Always ensure that ambient temperature inside the cabinet is within EZ3-TouchPLC Modular unit's
temperature ratings.
2. If any other equipment inside or outside of the cabinet is producing heat, employ cooling methods like a
blower fan to reduce 'hot spots' around the EZ3-TouchPLC Modular.
3. Periodically inspect and clean if there are any air filters on the cabinet. Ensure that the unit is free from dust,
humidity and corrosive gases.
Error Checking Process
The EZ3-TouchPLC Modular performs a standard diagnostic routine during each CPU scan. This is called the error-
checking step. The primary task of this step is to identify various types of CPU and I/O failures. We classify these
errors/failures broadly into two categories: Fatal and Non-Fatal.
Fatal Errors
These errors are the ones that lead to the system failure. During the CPU scan if a fatal error is detected, PLC is
automatically switched out of Run mode and all I/O points are disabled. Some instances of fatal errors include:
Wrong parity value, Programming errors, etc. The EZ3-TouchPLC Modular will not go into Run Mode from Program
if it detects a fatal error.
Non-Fatal Errors
These errors just need your attention and are not detrimental to PLC operation. Unlike fatal errors, the PLC will
continue in Run mode despite an occurrence of non-fatal errors. When you identify such errors, you can proceed
with an orderly shutdown and take the required corrective action. An example of non-fatal error is – a minor
programming error.