Start your EVOTECH request in under a minute.
Troubleshooting Access Control in Brookshire, Step by Step
A door that will not unlock, a gate that opens for nobody or for everybody, a badge that works at one entrance and not the next: each symptom has a short list of causes, and a methodical check finds the right one faster than rebooting and swapping parts. This is the diagnostic path EVOTECH follows on Brookshire systems, from warehouses on the I-10 frontage to gates at the end of long drives off FM 359, including the checks a facility manager can safely make before calling.
Three questions that split almost every fault
Before touching a wire, answer three questions. Together they point to the right part of the system in most cases.
- One opening or many? A fault at every door points to something they share: the controller, its power supply, the network, the software or a schedule. A fault at a single door points to that door’s reader, lock, wiring or the door itself.
- Did the system record the attempt? Look up the time of the failed entry in the event log. What the log says, or fails to say, narrows the search more than any other clue.
- Did the lock try to move? Stand at the door while someone presents a valid credential. A click or hum from the strike, or a change in the maglock, means the system decided to unlock and the problem lies between the lock and the door. Silence means the decision, or the power, never reached the lock.
What the event log is telling you
| Log shows | Most likely area | Next check |
|---|---|---|
| Access granted, door stayed locked | Lock power, lock hardware or the door itself | Measure voltage at the lock during the unlock; look for side pressure on the latch |
| Access denied for a valid user | Permissions, schedule, an expiration date or a disabled credential | Check the person’s access level, the door’s schedule and the controller clock |
| Unknown credential or invalid format | Card format or facility code mismatch, often after a new batch of cards | Compare the new cards’ format with what the controller is set to accept |
| No event at all | Reader not communicating, reader unpowered, or controller offline | Check the reader’s LED and beep, its wiring, and the controller’s online status |
| Forced or held-open alarms with nobody there | Door position switch out of alignment or failing | Check the gap between switch and magnet with the door fully closed |
If a cloud-managed portal shows the controller offline, the doors may still be deciding correctly on their own; the missing entries usually appear once the connection returns.
Measure power at the lock, not at the panel
Low voltage at the lock is the most common reason a door clicks but will not release, and it hides because the supply reads normal at the panel. The loss happens in the wire. Brookshire properties are especially prone to it because gates, sheds and outbuildings often sit on long runs far from the panel.
A worked example: a 12-volt strike drawing half an amp at the end of a 300-foot run of 18-gauge wire receives roughly two volts less than the supply puts out, because the current travels about 600 feet of conductor out and back. Add an aging battery and a couple of corroded splices, and the strike falls below the voltage it needs to pull in.
How a technician checks it:
- Measure at the lock terminals while the lock is energized, never with it idle.
- Compare that reading with the power supply output at the same moment.
- Load-test the standby battery. A battery can show normal voltage at rest and collapse the instant a lock draws current. Sealed lead-acid batteries in access panels commonly need replacing every three to five years, and sooner inside a hot metal building.
- Check the fuse or resettable protection on each output, which trips silently when a lock or cable shorts.
Supply sizing and battery choices are covered on our Brookshire access control power supply page.
Mechanical problems that masquerade as electronic failures
Plenty of calls that arrive as a broken reader end at the door. Brookshire’s buildings add some particular causes:
- Preload on the strike. When a door is pressed against its strike by a tight weatherseal, a sagging hinge or air pressure, the strike’s keeper cannot swing free. In a large warehouse, exhaust fans and open dock doors can push or pull a personnel door hard enough to cause this. Test by pushing the door toward its closed position while badging; if it then releases, preload is the culprit.
- Frames that move with the soil. The expansive clay common across this part of Texas swells when wet and shrinks in drought, and slab movement can shift a frame until the latch no longer lines up with the strike. The fault often appears in late summer and fades after heavy rain.
- Maglock alignment and surface. A magnetic lock holds only when its armature plate sits flat against the magnet. Rust, grime, paint or a bent bracket weakens the bond, sometimes enough that the door opens with a firm tug.
- The gate operator. If the log shows the gate was told to open, the fault is in the operator: its limits, its own battery, its obstruction sensors, or a manual release left engaged.
Doors that unlock, alarm or open on their own
Unexpected behavior is usually the system obeying an input nobody remembered:
- Request-to-exit sensors mounted above a door detect motion and unlock it for people leaving. Aimed badly, they react to someone walking past a glass door, a forklift passing, or warm air from an HVAC diffuser.
- Fire alarm release. Doors wired to release on a fire alarm signal unlock whenever that signal trips, including during alarm testing or a fault on the fire panel. Any work on that connection is coordinated with the fire alarm contractor.
- Clock drift. A controller that sat without power long enough to drain its clock backup, or that has the wrong time zone, runs every schedule at the wrong hour. Doors unlocking an hour early after a daylight-saving change are the classic sign.
- A forgotten override. A holiday unlock or a manual keep-open command from months ago can still be active. The software lists active overrides, and clearing them is often the whole fix.
When a controller or reader drops off the network
Communication faults appear as missing log entries, a portal marking the controller offline, or readers that blink but never report. The usual causes on Brookshire sites:
- A new router or internet provider. Swapping equipment often changes the controller’s network address or blocks the outbound connection a cloud platform needs. Reserving the controller’s address in the router prevents a repeat.
- PoE budget. Readers and controllers powered over Ethernet can push a switch past its power budget when cameras join the same switch, and the device that loses power first is not always the newest one.
- RS-485 wiring. Links between the controller and reader interfaces need twisted pair, termination at the ends of the line and a single shield ground. Mistakes cause intermittent faults that come and go with heat and electrical noise from nearby motors.
- Remote gate links. A wireless bridge or cellular modem serving a far gate can lose signal to vegetation growth, an antenna knocked out of alignment by high wind, or a lapsed data plan.
- Reader protocol settings. A replacement reader must match the controller’s interface, Wiegand or OSDP, and for OSDP the correct address and speed. A mismatch leaves a working reader that the controller never hears.
Where do-it-yourself checks should stop
A facility manager can safely read the log, confirm schedules and permissions, push a door closed while badging, watch the reader’s light and listen for its beep, and check whether a gate operator is in manual mode. Stop and call a technician when the fix involves:
- Opening a power supply connected to 120-volt power
- Any connection to the fire alarm system
- Anything that changes how people exit, including maglock release devices
- Gate operator adjustments; the UL 325 standard’s entrapment protection exists because a moving gate can seriously injure someone
- Programming changes you lack administrator rights for, or a system whose login only the original installer holds
How EVOTECH runs a Brookshire troubleshooting call
- Phone intake. We ask which openings are affected, what the log shows, what changed recently, and whether the property is secure right now.
- Scheduling. Brookshire sits just west of Katy along I-10 and is part of the area we serve from our Katy/Houston base. Call to confirm scheduling for your address.
- Diagnosis on site, following the path on this page: event log, lock movement, voltage under load, mechanical alignment, then communication.
- Findings before fixes. We explain what failed and why, and separate the immediate repair from anything that should be planned later.
- Verification. Each repaired opening is tested with a credential, an exit from the inside and a held-open test, and we confirm the matching log entries.
What affects the cost of a troubleshooting call: how many openings are involved, whether the system is documented and we have administrator access, distance to gates and outbuildings, parts such as batteries, locks or readers, and any after-hours work. Systems installed by other companies are fine to bring to us; a missing admin login simply adds time. When the question becomes repair versus replacement, our Brookshire access control repair page covers that decision.
Request an access control troubleshooting visit in Brookshire
Related services
Frequently asked questions
The reader beeps and flashes green but the door stays locked. What does that mean?
Every badge stopped working at once this morning. Where do we start?
A new batch of cards will not work, but the old cards do. Why?
Our gate opens by itself at odd times. Is someone hacking it?
How long will our batteries keep the doors working in an outage?
Get the fault found, not guessed
Book an on-site estimate in Brookshire. We follow the diagnostic path, explain what failed, and itemize the repair before any work begins.
Book a Consultation
Ready for EVOTECH to help?
Before you leave, send the quick version. We will review the page you came from and reply with the clean next step.