FKI Tech Info

Auditor Operation
Tubes
Door
Drops
Users
Reports

Auditor Software
Programming
CPU Versions
CPU Reset
Door Slam
Sled Test
Error Messages

Auditor Service
Power
CPU Board
Driver Board
Doors
Door Sensor
Vending
Input Sensors
Output Sensor
Sensor Board
Validators
Incorrect Totals
Keypad
Display
Printer
Key Switches
Parts List

27 Series
Operation
Programming
Troubleshooting
Parts List

Auditor Autobank - Operation

Running Reports

1. Press REPORTS
2. Enter a valid USER NUMBER and press ENTER. (Versions older than 2.2 do not use USER NUMBERS).
3. Enter a valid PIN number for the specified USER NUMBER and press ENTER.
4. Operators with report permission: Enter the number of the report to run and press ENTER.
5. Except for Reports 106 or 109, simply take the printout. In the case of the reports 106 or 109, you must also enter the start and end dates and times to bracket the report period.

Regular Reports

Users Reports 03-99: These are user reports showing transactions conducted since last Z report. Users without general report permission can still print shift reports.
X Net Cash Report 101: Prints total of operator activity since last Z report. Part of the Daily X Report 110.
Z Net Cash Report 102: Same as Report 101, but zeros the totals. Part of the End of Day Z Report 111.
X Operator Group Report 103: Prints report of activity by operator since last Z report. Part of the Daily X Report 110.
Z Operator Group Report 104: Same as Report 103, but zeros the totals. Part of the End of Day Z Report 111.
Cash on Hand Report 105: Prints totals of all cash in safe including money in drops and column totals. This report is included in the 110 and 111 daily reports.
Audit Report 106: This report prints all activity in the log within the time bracket specified. This report is used for investigations and, in some cases, troubleshooting.
Configuration Report 107: This report shows how the safe is configured. Configuration includes date, time, delays, time locks, column values and access, and various miscellaneous parameters. Each line number on this report corresponds to the Programming Config Option that sets the printed parameter.
Enrolled Users Report 108: This report prints a list of enrolled user numbers and associated permissions. On older software versions (V1.95) this report also printed the PIN numbers.
Validator Error Report 109: This report prints a list of validator error activity within the time bracket specified.
Daily Grand X Report 110: Master X report that includes Reports 101, 103, and 105. Normally performed immediately before running the Report 111.
Daily Grand Z Report 111: Master Z report that includes Reports 102, 104, and 105. Ends the business day.

Diagnostic 126 Report

This report is used to check the memory condition of the CPU. If the safe is not entering data in the correct locations in memory, it will likely cause incorrect totals to show on reports and may cause any number of other unusual symptoms. If the results of this report show the memory is bad, the safe needs a CPU Reset. If the report results are good, the problem may be a faulty CPU or other component, or operator error.
A. Check the Transaction Number. If it is less than 10620:
   1. Start Page must be 00. If it is anything else, reset the safe.
   2. Divide the Transaction Number by 885. The answer, rounded up, should equal the number of "dirty" statements. If not, reset the safe.
   3. "Clean" statements, if any, should come after the dirty statements. If not, reset the safe.
B. If the Transaction Number is 10620 or higher:
   1. All clean/dirty statements should read dirty. If not, reset the safe.
   2. Divide the Transaction Number by 10620. The answer, rounded down, should equal the start page number. If not, reset the safe.
C. Ignore the Record Number.
D. The True/False statement at the top only indicates whether the 111 Report has been run this day. It has nothing to do with whether the safe needs a reset.