Power Supply and Hardware Status Diagnostics
The eSSL C3-200 operates on a recommended power supply of 12V DC, 1.5A. If the controller board fails to power up or the RUN indicator light remains unlit or unresponsive, verify the incoming DC voltage directly at the controller power input terminals using a calibrated multimeter. Insufficient supply voltage below the 12V DC threshold or reverse DC polarity will prevent the 32-bit 400 MHz processor from booting.
Ensure that peripheral loads, such as electronic strikes, magnetic locks, or multiple external readers, are not pulling power directly from the controller logic terminals in excess of the rated 1.5A capacity. If heavy inductive loads cause voltage drops, isolate lock power supplies using dedicated auxiliary power lines rather than bridging off the logic board power terminals.
TCP/IP and RS-485 Network Communication Faults
Communication failure between the C3-200 controller and the central access management server typically manifests as an offline device status across TCP/IP or RS-485 communication channels. For Ethernet-based TCP/IP drops, review local network parameters to ensure no IP address conflicts exist on the local subnet. Verify that management server communication ports are not filtered or blocked by network firewalls or managed network switches.
When utilizing RS-485 multi-drop communication buses, check that the RS-485 polarity is correctly maintained throughout the daisy chain. A single inverted line or improper bus termination can disrupt data transmission across the serial loop. If optional Wi-Fi hardware is deployed, confirm signal strength and local network gateway routing.
Wiegand and RS-485 Card Reader Interface Errors
The C3-200 supports up to 8 readers, accommodating either 4 RS-485 readers or 4 26-bit Wiegand readers across its 2 controlled doors. When readers emit power beeps but fail to register credentials or return invalid card reads, review the data wiring terminations immediately:
- Reversed Data Lines: Ensure Wiegand DATA0 and DATA1 lines are not transposed. Swapping these conductors causes unreadable data streams or unparsed credential packets.
- Cable Distance and Interference: Excessive cable runs without proper shielding can degrade 26-bit Wiegand pulse signals. Keep reader transmission distances within standard specifications.
- Reader Protocol Compatibility: Verify that connected credentials and reader heads output the standard 26-bit Wiegand format or compatible RS-485 protocol recognized by the controller firmware.
Form-C Lock Relay and Input Sensor Troubleshooting
The controller provides 4 onboard Form-C relay outputs (2 relays dedicated to door locks and 2 relays for auxiliary outputs) along with 6 onboard inputs (2 request-to-exit push button inputs, 2 door status sensor inputs, and 2 auxiliary inputs). When locking mechanisms fail to release or remain permanently unlocked, execute the following operational checks:
| Symptom | Probable Cause | Diagnostic & Corrective Action |
|---|---|---|
| Lock remains continuously energized | Inverted relay contact configuration | Verify lock type wiring. Fail-safe (power-to-lock) devices require NC (Normally Closed) and COM terminals; fail-secure (power-to-unlock) devices require NO (Normally Open) and COM terminals. |
| Relay clicks but lock does not drop | Insufficient lock driving voltage | Form-C relays provide dry contacts only. Ensure an external power source is correctly wired in series with the lock circuit. |
| Door status registers open permanently | Magnetic reed switch fault or wiring open | Inspect door status input terminals. Confirm magnetic reed contact is correctly aligned and closes the circuit when the door rests shut. |
| Exit push button fails to trigger relay | Open circuit or incorrect contact type | Ensure exit device is wired across dedicated exit inputs using normally open (NO) momentary dry contacts. |
Offline Buffer and Memory Diagnostics
The controller architecture utilizes 128 MB Flash Memory and 32 MB RAM, providing capacity for up to 30,000 cardholders and an offline transaction buffer of up to 100,000 log events. If the controller stops logging events or rejects recognized credentials during network outages, confirm whether the 100,000 transaction event threshold has been reached without being polled by the software. Synchronize the controller with the access management software over TCP/IP to clear historical transaction logs and refresh cardholder access privileges into the onboard flash memory.
