The Keri PXL Controller is a specialized access hardware panel that serves as the “brain” for securing doors and gates in Keri Systems Entraguard.
HOW KERI PXL CONTROLLER MANAGES DATA?
The controller stores user and system information locally in its non-volatile RAM (supported by a lithium battery with a 5-year life). Basically, this ensures the door remains functional even if the connection to the central PC is lost.
- Cardholder Data: It can manage up to 65,000 unique card/tag holders.
- Access Rules: It stores up to 32 distinct time zones and holiday schedules.
- Hardware config: It stores activation and expiration dates for individual users.
The controller acts as a black box for activity.
- Storage: It maintains a local buffer of at least 3,600 transactions (events like “Access Granted,” “Door Forced,” or “Request to Exit”).
- FIFO Logic: When the memory is full, it operates on a “First In, First Out” basis, overwriting the oldest data with new events until the software polls the controller to download the logs.
The move data between the readers, other controllers, and the management software, it uses several standards:
- RS-485: The primary networking protocol for connecting multiple controllers (up to 256 doors per site) over long distances (up to 16,000 feet).
- Wiegand: A universal industry standard used to receive data from third-party proximity readers or keypads.
- TCP/IP: While native to RS-485, it uses the LAN-520 adapter to transmit data over standard Ethernet networks.
The data on a PXL controller is typically managed through one of two software platforms:
- Doors.NET: The modern, SQL-based framework for professional-grade environments.
- Doors32: The legacy software (often used with windows XP/7/10) for simpler, smaller installations.
HOW TO FIX A KERI PXL CONTROLLER DATA UPDATE ERROR?
It is reported that one of the controllers is not updating the user’s data in Keri Systems Entraguard. Normally, this type of failure may be that we have to check network problems, and then we will see the procedure to fix it.
To fix it we are going to open the Keri PXL System Client application
Enter the credentials
Then go to >> Setup
Go to >> Hardware Setup
Then we go to >> ALL
Then we select with right click on the panel with the error
And click on >> Update Network
Go to Live Events and validate that you are executing the command
Keri pxl Systems also provides extensive support services, including installation assistance, technical support, training, and troubleshooting. Also, their access systems are backed by a network of authorized dealers and installers who are trained in the company’s products and services.
Once the update is finished, we validate that we can enter new users and update them and
that everything is working correctly, this will solve the error.
WHY DOES THIS DATA UPDATE ERROR OCCUR?
This error usually pops up because of a “handshake” failure between your computer and the controller hardware.
Communication Timeouts (The LAN-520)
Modern PXL systems typically rely on a LAN-520 adapter to establish a network connection, yet this hardware often encounters communication hurdles. Specifically, when a network becomes congested or the adapter faces a “micro-burst” of unmanageable data, the Doors.NET or Doors32 software stops awaiting a response and triggers a data update error. To resolve this issue, you can often restore the connection by power cycling the LAN-520 adapter or verifying that a firewall isn’t blocking Port 10001. By addressing these connectivity gaps first, technicians can quickly clear the error and resume standard system operations.
Software Conflicts (The "Dual Master" Problem)
Software conflicts often arise during a transition from Doors32 to Doors.NET because both programs may attempt to communicate with the controller simultaneously. Since the hardware allows only one “master” to manage the data flow at a time, this competition inevitably triggers a sync error. To prevent this collision, you must fully disconnect Doors32 by selecting “Operate” and then “Net Disconnect” before you attempt any updates within the Doors.NET environment. Taking this simple step ensures a clear communication path and allows the new software to maintain exclusive control over the controller.
RAM Corruption
Unexpected power loss during a previous update can scramble the controller’s internal RAM, essentially causing the hardware to lose its ability to communicate with the software. Because the device “forgets” its operational logic, you must perform a RAM Reset using the physical jumpers on the circuit board to trigger a factory reset. This procedure clears the corrupted memory and restores the “brain” to a clean state, which finally allows the software to push a fresh, successful data update.
Daisy-Chain Interference (RS-485 Issues)
Technicians often wire PXL controllers together in a long daisy-chain configuration, which creates a single point of failure for the entire line. If a loose wire occurs at a middle unit, such as Controller #3, every subsequent device in the chain will fail to receive the update. To diagnose this break in communication, you should inspect the TxD and RxD LEDs directly on the circuit board during a sync attempt. If these lights remain solid or dark rather than flickering, you have confirmed that the data signal is not reaching that specific panel, indicating a physical connection issue further up the line.
