Biometric Sensor Response and Fingerprint Identification Errors
The eSSL PT100 relies on an Infrared Auto-sleep Optical Sensor running Fingerprint Algorithm version 10 to eliminate buddy punching and log verified personnel. If the optical sensor fails to activate upon contact, ensure the contact surface is free from dust, oil films, or condensated moisture. The auto-sleep infrared mechanism requires adequate contact reflection; excessively dry fingers can cause missed reads. Guards should apply firm, even pressure centered squarely across the optical prism.
If the device consistently reports identification failure on the 1.44-inch color LCD display:
- Confirm that the guard profile is successfully enrolled within the unit's 500-fingerprint template memory.
- Clean the optical sensor prism using a soft, lint-free cloth lightly moistened with isopropyl alcohol; abrasive cleaners must never be used.
- Re-enroll personnel who present worn, scarred, or dry fingerprints under standard operating temperatures between -10°C and 40°C.
RFID Tag and Checkpoint Detection Diagnostics
The built-in radio frequency reader is engineered specifically for 125 kHz EM proximity cards and RFID tags, supporting up to 1,000 card IDs. When the terminal fails to register an installed patrol watchstation tag, verify that the physical checkpoint uses 125 kHz EM technology. High-frequency 13.56 MHz smart cards or tags are incompatible with the reader.
Check for physical RF shielding and interference at the checkpoint location:
- Ensure 125 kHz checkpoint tags are not mounted directly onto unshielded metallic surfaces, structural steel, or electrical conduit, which detunes the RF field and blocks signal transmission. Install non-metallic spacers behind the tags if mounted on metal.
- Verify that the guard presents the terminal within direct reading range of the tag without physical obstruction.
- Confirm that total active patrol IDs do not exceed the 1,000-card capacity limit programmed via the dedicated patrol software.
USB Client Communication and Memory Buffer Overflow
The PT100 stores up to 30,000 log records in internal memory and transfers data via a direct USB Client connection. When the host PC running dedicated patrol management software or SDK fails to detect the terminal:
- Check the physical USB Client interface connection between the 0.22 kg handheld terminal and the workstation.
- Verify that the correct communication drivers are configured in device manager and match the port assigned inside the dedicated patrol software.
- Inspect the terminal memory status on the 1.44-inch color LCD display. If the 30,000-log capacity threshold is reached, old records must be extracted and cleared through the software to restore open storage for ongoing rounds.
Power Diagnostics and Charging Behavior
The terminal operates from a 5V DC, 800 mA external power supply and is equipped with a 2,000 mA Lithium Battery (they are not included) designed to provide up to 7 days of standby power. If the device fails to turn on or loses power prematurely:
- Verify that the charging source consistently delivers 5V DC at a minimum of 800 mA. Undervoltage USB ports cannot properly replenish the 2,000 mA Lithium Battery (they are not included).
- Connect the reader to the power source and inspect the 1.44-inch color LCD display to verify the charging indicator status.
- Allow sufficient charging time if the battery (they are not included) has been fully depleted, especially after extended patrol cycles or storage.
Environmental and Enclosure Inspection
The eSSL PT100 features a compact 162 mm x 52 mm x 46 mm form factor rated to IP65 for dust resistance and water resistance. If deployment takes place in heavy rain or industrial processing environments, ensure the USB port cover and casing seams remain properly sealed. Operating outside the specified -10°C to 40°C ambient temperature range may degrade optical scanner responsiveness and impact operational performance.
