Door Reader Programming in Houston, TX 77024

Your reader does not read a card. It reads a number.

Hold a fob to a reader and three separate pieces of programming have to agree before the door moves. The credential holds an encoded number. The reader picks it up and transmits it in a specific wire format. The panel receives it, decides which format it is looking at, and checks the result against a database. Any one of those three can be right while the other two are wrong, and the door still stays locked.

They are configured with three different tools, often by three different people, years apart. Homeowners in Bunker Hill and Piney Point routinely inherit a gate reader from the builder, a keypad from a locksmith and a panel from a security company that has since changed hands. Nothing is broken. Nothing agrees either.

• On the credential: the technology (125 kHz proximity, 13.56 MHz smart card, phone credential), the encoded number, and on encrypted cards a site key only your system holds.
• On the reader: output protocol, address if it is a supervised reader, keypad behaviour, LED and beeper behaviour, tamper reporting, read range.
• On the panel: which formats it will accept, which facility codes are valid, which reader belongs to which door, and what happens on a bad read.

So we pull the event log first. A dead reader produces no event at all; a misconfigured one produces a very specific complaint that usually names the problem.

Bit formats, facility codes, and the word ‘invalid’ in your event log

The most common credential format in Houston is still 26-bit Wiegand: an 8-bit facility code, a 16-bit card number and two parity bits. That is the entire payload — 255 usable facility codes in existence and roughly sixty-five thousand card numbers under each one. Cards carrying identical numbers have been printed continuously, all over the country, for decades.

Larger 35-bit and 37-bit formats exist because of that, and are usually issued against a code registered to a single customer. They are also why a perfectly good card is refused after a panel swap: a panel told only about 26-bit truncates a 35-bit read into nonsense and logs it as an unknown format.

When a format is unknown the panel usually still records the raw read — a bit count and a string. That bit count is the fingerprint: it tells us whether we are looking at a standard 26-bit card, a proprietary format, a keypad burst being mistaken for a card, or a reader dropping bits on a long cable run.

The fob on your key ring can be copied in about four seconds

A 125 kHz proximity credential broadcasts its number to anything that asks. No encryption, no mutual authentication — the reader cannot tell an original card from a blank bought online, and handheld duplicators that read one and write the other sell openly. If the drive gate, the pool gate and the side door all trust a 125 kHz fob, the security of the property is the security of whoever has handled that fob, including a vendor who had it in a pocket for an afternoon.

13.56 MHz is not automatically better: the older MIFARE Classic generation has a publicly broken cipher and is copied nearly as easily. The meaningful line is whether the credential performs a mutual authentication using a key that lives only in your system and in your readers.

Migration is rarely a rip-out. Most current readers accept an old prox card and an encrypted card at the same time, so we enrol everybody on the new credential, run both for a defined window, then switch the legacy format off. The hardware usually stays.

An estate changes people far more often than it changes hardware

A property off Memorial Drive or Voss can see a housekeeper, a weekly lawn crew, a pool service, a trainer, a caregiver and a remodelling crew on site for eleven weeks. That is not a security problem by itself. It becomes one the moment they all carry the same unlabelled black fob, because then the log cannot tell you who came through the pedestrian gate at 6:40 on a Tuesday, and revoking one person means collecting every fob on the property.

One credential per person, always

Individual credentials cost almost nothing and are the whole reason the system exists. Vendors get their own, named in the database by company and person, and can be bound to the window they actually work in — a landscaping credential simply is not valid at eleven at night. Deeper schedule work is covered on the 77024 access schedule page.

Deleting a person is not deleting a credential

This is the most misunderstood part of access software. In many platforms the cardholder record and the credential assigned to it are separate objects. Delete the person and the credential can survive as an unassigned but still-valid number, or be re-issued to somebody else with the old permissions attached. When a fob is not returned we void the credential number itself, test it at a live reader, and check the log for the event that proves it is now refused.

Memorial City and Town & Country: when the building already issues the badge

The eastern end of 77024 is a different job. Professional, dental and medical suites along the Katy Freeway service road sit inside buildings that already run access control for the garage, the after-hours lobby and sometimes the elevator. That system belongs to the landlord, runs on the landlord’s format and facility code, and is administered by a property manager who has never heard of your suite door.

There are two honest options, and the right one depends on what management will put in writing.

• Share the building credential. Your suite reader is programmed to accept the base-building format, so one badge covers garage, lobby and your door. Better for staff, and it needs the building’s format details and their consent — some buildings hand both over, some will not release the facility code at all.
• Issue your own. Your suite runs its own credential on its own format and staff carry two cards. Unglamorous, works everywhere, and a hire or a termination is handled in your office the same hour instead of on the property manager’s next badge-office day.

Inside a clinical suite the programming question is rarely the front door. It is the records room, the sample storage and the back corridor the cleaning crew uses at nine at night — separate access groups on the same card, far cheaper to get right at commissioning than to untangle after an audit.

What we actually program on a 77024 call, and what moves the estimate

1. Inventory: every reader, what it is mounted to, the panel it lands on and which port it occupies. Plenty of systems out here have a reader wired to a door it is not labelled for.
2. Pull the event log and present a known-good credential at each opening, so we work from evidence instead of guesswork.
3. Identify the credential technology and bit format from a sample card and from the raw reads in the log.
4. Set the reader itself: output protocol, address on supervised readers, keypad mode, LED and beeper behaviour, tamper reporting, and read range where two readers sit close together.
5. Rebuild the credential database — one record per person, correct encoded numbers, access groups that match how the property is actually used.
6. Test every opening in both directions, including request-to-exit and door-held events, confirm a revoked card is genuinely refused, and hand over administrator credentials in your name with a printed credential list and the format details.

What changes the number

How many openings are in scope; whether the drive gate is included; whether drawings and a credential list exist or nothing was ever written down; whether you stay on the current credential or migrate to an encrypted one; whether the site sits inside an incorporated village with its own permitting expectations, or inside a leased building with contractor and insurance rules. We quote each opening as a line item after seeing it, and the on-site estimate is free.

Mistakes that bring a technician back

• Two readers on the same narrow frame, closer than the manufacturer allows, producing ghost reads that look like a bad card.
• A reader screwed straight onto a steel jamb without the metal-mount spacer, detuning the antenna until read range nearly disappears.
• Printed card numbers entered into the database instead of encoded ones.
• No documented administrator account, so adding a housekeeper needs a service call instead of two minutes at your own desk.

Related services

Frequently asked questions