LogTool – Production Log Validation & Analysis

Problem

Each tested device generates a TXT log on the production server. After a production batch is completed, the relevant log files need to be reviewed to confirm that every device in the expected serial-number range has a recorded test result.

Checking this manually across many TXT files was time-consuming and made it easy to overlook a missing device. The correct log files also need to be collected for all production days connected to the batch before the batch can be checked properly.

Solution

I developed LogTool as a desktop application that works directly with folders containing downloaded production TXT logs. The application reads and parses the files, detects batch and serial information, and provides dedicated tools for converting logs, locating batches, and checking whether devices are missing from an expected serial-number range.

This makes it possible to perform the batch check from one interface instead of manually opening and comparing individual log files. If a device is shown as missing, the production record can be investigated and the device can be tested again when necessary before the logs are checked once more.

How It Is Used in Production

LogTool is used after each completed production batch as a final check that the expected device logs are present. The relevant TXT files first need to be downloaded from the production server for all days when work was carried out on the batch.

1. Download the relevant TXT log files from the production server
2. Make sure logs from every production day connected to the batch are included
3. Open LogTool and select the folder containing the downloaded TXT files
4. Use Missing Devices to check the expected serial-number range for the completed batch
5. Investigate any serial number that is still reported as missing
6. If necessary, run the device through the test fixture again and repeat the log check

Key Features

• Convert Logs — converts downloaded TXT logs into a structured Excel workbook
• Missing Devices — checks a batch and serial-number range to identify expected devices with no matching log
• Find Batch — searches the selected log files for a specific production batch
• Preview — shows a quick preview of converted or batch-search results before creating the Excel output
• Automatic detection of batch, serial number, timestamps, and test results from raw log files
• Structured Excel output for easier review, filtering, and production follow-up
• Standalone Windows application designed for use without a Python development environment
• Server Import is included as an experimental function but is not yet finished or approved for normal production use

Current Status & Development

The main functions used for production follow-up are already in active use, especially Missing Devices, Find Batch, Convert Logs, and Preview.

Server Import is still under development and should not currently be used for normal production work. Its purpose is to eventually retrieve the required log files directly from the server so that downloading them separately is no longer necessary.

• Missing Devices is the primary function used for completed-batch checks
• Find Batch can be used when searching for a particular production batch
• Convert Logs and Preview support review and structured Excel output
• Server Import remains experimental and is not part of the current production procedure
• Some debugging information may still be visible while the application continues to be refined

Tools Used

Result

LogTool reduced the amount of manual work needed to review production logs and made completed-batch checks much easier to perform. Instead of manually opening and comparing many individual TXT files, the relevant logs can be checked from one application.

The Missing Devices function provides a clearer way to confirm that every expected serial number in a completed batch has a corresponding test record, while Find Batch and the Excel export functions make investigation and follow-up faster when additional review is needed.