The Clock Connect Log provides insight into what’s happening on your clocks at any time. Whether you want to confirm an employee’s punch or view who accessed the menu, the log has your answers.
The log is only for the selected clock. It displays the most recent activity at the end of the file. When you select Refresh Log, all the newest entries load, and you’ll see the bottom of the log, where the latest entries display.
Once you’ve created the log, you can either:
Use the Clock Functions in the Log to identify when an activity occurred on the clock.
Are you looking for information about when something was done on the clock, such as verifying when an employee punched? This section identifies the log entry for the activity, which you can use to search the log.
Use the Clock Connect Terms to troubleshoot errors.
This is a list of all the terms found in the Clock Connect log.
When you want to know what something from the log means, you can lookup the term here. The listing is in alphabetical order, so you can quickly find what you’re looking for .
This is only applicable for clients with uFace 800 clocks using Clock Connect.
How to Create the Clock Connect Log File
Step 1: Open Clock Connect on the Avanti Self-Service Portal (ASSP).
Unsure where to find Clock Connect? Enter Clock into Search on the New Avanti Experience, and it’ll direct you to the right place.
Step 2: On the Log File tab, select the Clock ID of the clock.
Step 3: Update the number of Minutes, Hours, or Days to ensure the log spans the correct timeframe.
Step 4: Select View Log File.
Once the log displays, you can save the log by copying the text into a file, such as a Word document.
Great! You’ve created the log.
Clock Functions in the Log
Are you looking for log entries for a specific function on the clock, such as when someone accessed the clock menu? This section identifies what the log entries look like for each clock process.
Once you’ve identified the text, you can search the log file using (ctrl + F) to find the relevant entries in the log.
Last Connection to the Clock
The final log entry is the Last Heartbeat, which displays the date and time of the most recent communication between Avanti and the clock. You can find this at the end of the log file.
Getting Users From the Clock
Getting all users from the clock creates four entries, plus an entry for each person enrolled. It also lists each employee using fingerprint identification.
Depending on the employees enrolled on the clock, getting employees may take up to an hour.
The 1st entry has QueryAllUsers in Log Reason, then Command DATA QUERY USERINFO in the Log String.
The 2nd and 3rd entry has CommandSent in Log Reason, verifying that the clock received the request.
Next, there’s a set of entries with SaveUser in Log Reason. There’s an entry for each employee on the clock.
If the employee is unassigned to identity on the clock, Saved unassigned enrollment PIN= displays in the Log String.
If an Avanti employee is assigned, Saved user data PIN=10 EmpNo: Name: displays in the Log String.
Additional entries display for each fingerprint on the clock. SaveFingerprint displays in Log Reason. Saved fingerprint template PIN= displays in Log String.
The last entry displays CommandCompleted in Log Reason and DATA QUERY USERINFO in Log String.
Sending Users To the Clock
Sending employees to the clock creates an entry for each employee. The Log Reason displays Command Sent.
The Log String displays their: PIN, Name, Password, and Card Number. Pri is 0 if the employee has check-in/out access and 14 if the employee has menu access.
Sending an Employee to the Clock
The 1st set of entries have CommandSent in Log Reason and sends a request to:
Delete the user, fingerprint, and face, displaying: DATA DELETE USERINFO PIN= in the Log String.
Update the user, fingerprint, and face, displays: DATA UPDATE USERINFO PIN= in the Log String.
The 2nd entry also has CommandSent in Log Reason, with OK in the Log String, indicating the clock received the request.
The last set of entries displays CommandCompleted in Log Reason, with the user’s information.
If the clock couldn’t complete a request, the Log Reason is DeviceCmdResponse, and the Log String explains why the request failed.