Fairbanks FB3000 Highway System Application - Manual (Page 84)

7/08 84 51188 Rev. 1
Section 8: Service & Maintenance
8.1. STEPS TO WRITING ERROR CONDITION FILES
1. An Error Condition formats a file name as described below.
2. The initiating application then checks for a pre-existing error file name.
2a. If none is found, the error file is written.
2b. If it does exist, the error file is not written.
─ This allows the Error Notification Application to control the frequency of
repeating errors (such as Load Cell Failure and Float Switch On) by
deleting the error file when it is ready to check for a continued error.
2c. The error files are written to the “Errors” directories using the
“Data/Ready” file writing scheme.
3. In the case of a multiple terminal installation, each terminal will report its own
errors.
4. An additional key and value is added to the [Data] section to identify the
terminal.
8.2. ERROR FILE FORMAT
[Error]
Description = xxxxxxx (description of error)
[Data] yyyy = zzzz (keys and values specific to the error, as
many lines as needed)
 IMPORTANT PRECAUTION 
Before handling the FB3000 boards or other system components,
the certified service technician must always be properly grounded.
• Electrostatic Discharge (ESD) severely damages all computer components.
• Remove the anti-static packaging only when the parts are ready for
installation.
• Handle the boards by their edges, and avoid touching their components.