ETC plunger lift controllers have an error handling mechanism to deal with software errors in a graceful fashion. More minor errors might prevent a setting from being entered or show a partial number on the screen. More severe errors that cannot be handled appropriately will cause the controller to be restarted. This may appear as if the controller went to close since this is always the state the controller starts in.
When an error occurs, the controller software saves these errors and associated data in an error log. To view the error log:
- Press install
- Navigate to and select “System“
- Scroll down to the bottom of the menu past “Reset Error Log“
- If you do not see this screen, the log is empty.
- Any screens after this will appear with an error type and associated data.
There are a few different types of errors that will be logged by the plunger lift controller.
Assert Fail (ASSRT)
This is used to catch conditions that should always be true. If the statement is not true, the system does not know how to handle it, so the controller is restarted.
System Definition Fail (SYSDEF)
A system definition error typically indicates that an internal queue was overflowed. This will result in operations being ignored or data being dropped.
Check Fail (CHK)
This is the least severe of all error messages and typically means that a value could not be fully displayed in the available field on a screen.
Whenever you have discovered errors in the operation of the controller, you should:
- Copy down any errors that are found in the error log.
- Note the controller configuration.
- Note what was being done on the controller when the issue occurred.
- Note the serial number and version number of the controller that experienced the issue.
- Detail instructions on how to repeat the issue if possible.
- Reset the Error Log to keep track of what is new.
- Report the issue to ETC by submitting a ticket.