The entrance slide gate at our Longview, Texas facility had been stuck half-open for a few weeks. A gate that won't close is not a cosmetic problem at a storage facility: it is the security perimeter, and "stuck half-open" means it isn't doing its one job. The diagnostics display showed error code 50, which meant nothing to us at the time.
The normal move is to call a gate company, wait for the truck, and pay a few hundred dollars (for our market, a visit like this runs about $500) for a technician to spend an hour on something that turns out to be mechanical. Instead, we opened the operator's cover, pointed a phone at the control board and the model tag, uploaded the photos to Claude, and fixed it ourselves the same day. Total parts cost: zero. This post walks through exactly how that went, with the actual transcript, and ends with the part we now do after every repair: the AI turned the whole thread into an illustrated training manual for our property manager.
One prompt, with photos
The opening message set the tone for the whole exchange: photos of the open control box plus the model tag, and a request to do the homework properly before touching anything.
You: I'm trying to diagnose why my gate here is failing. It's been stuck in the half-open position for a few weeks now. I've just opened it up to see the control panel, and I've also given you the model number. Start by thinking deeply about this particular model. Do online research on it: find its manuals, its operations, error codes, and system configurations. Then look up error code 50 and help me troubleshoot how we can get it working again. Claude: I've pulled and stored the full installation/service manual for this operator... Error Code 50 = Run-Distance Error. "Gate unbalance detected." In plain terms: when you set the limits, the operator memorized the exact travel distance between open and close. Error 50 fires when the gate stops short of the learned distance or the effort is wildly different than expected, which is exactly why it parks half-open and quits. This is almost always mechanical, not an electronics fault.
From the board photo and the FCC ID on the tag, it identified the operator family, found the factory manual, and translated a two-digit error code into a physical explanation. Then it prescribed the test a good technician would start with: disconnect the drive and push the gate through its full travel by hand, feeling for the bind. And it kept us oriented inside the machine, because knowing what to do is useless if you can't find the switch:
You: Where is the reset switch? This is a slide gate. Claude: On your slide unit it's not on the logic board. It's a separate toggle switch on the front of the operator housing, behind a small sliding access door... Don't confuse it with the AC POWER switch (the black rocker on the left side of your open box). That one only kills AC power; it does not reset the operator and does not cut battery power. You: Where is the BACKDRIVE switch? Claude: It's a small slide switch on the main logic board itself, labeled MANUAL and SECURE... For your stuck-gate push test, set it to MANUAL. That disengages the drive so the gate rolls freely by hand.
Working the error ladder: 50, then 38, then 91
With the bind cleared and the gate rolling free, we re-learned the travel limits from the board (MOVE GATE arrows, SET OPEN, SET CLOSE) and cycled the gate so it could auto-learn its force. And then came the part that sold us on this way of working. Real repairs aren't one fix; they're a ladder of new, smaller problems, and the AI treated each one as information instead of failure:
You: It opened and then snapped into position, but it sounded a bit weird, like it shouldn't have done that, and then it automatically opened again. Now it's showing error code 38. I think I can reset the limits again to fix that, but tell me: what does error code 38 mean? Claude: Error 38 = "Hard Stop Limit." The gate ran into a physical hard stop right at or before where the operator expected its programmed limit... The good news: this actually means progress. Your earlier error 50 (gate stopping short) is gone. The gate is now traveling its full distance freely. It's just going too far into the physical stop. Re-set the limits, but this time stop the gate a few inches short of the physical stop, not jammed against it. You: I've set the reversal force to minimum. It showed error code 91. Claude: Error 91 = "Force reversal"... and the cause here is the change you just made. At minimum, the operator has almost no force budget, so the normal effort it takes to move your gate reads as "hitting an obstruction." Bring the dial back up toward the middle, cycle the gate, and stop raising it as soon as it reaches both limits cleanly. Then re-run the obstruction test to confirm it still reverses on contact. Don't crank it to max to silence the error; that would defeat the reversal protection.
Note what it refused to do, twice: let us mask a mechanical problem by turning up the force, and let us finish without the obstruction test (block the closing gate with a solid object; it must reverse on contact). That test is the anti-entrapment protection on a gate the public walks past every day, and the AI treated it as non-negotiable. Error 70 popped up during testing too, and Claude correctly identified it as the close-direction photo eye doing its job while we waved things through the beam.
A few cycles later: full travel in both directions, clean stops at both limits, reverses on contact, no codes on the display.
You: Cool, everything is working properly now. No error code displayed. Do I need to do anything more, or just put the cover back on? Claude: Nice work. You diagnosed and fixed that yourself. Just a few quick things before the cover goes back on... Run the obstruction test. Quick-check your photo eyes. Set the BACKDRIVE switch back to SECURE (for a security gate you want SECURE so nobody can shove the gate open during a power outage). Test a remote with a normal open-close cycle so you know real-world commands work, not just the test buttons.
Then one more prompt, and it wrote the manual
The entire diagnostic thread, every photo, every error code, and the exact repair sequence were sitting in one conversation. So we asked for the thing a service company never leaves behind:
You: Can you use these photos to create a full training document, with all the error codes we encountered, for my property manager? Talk about taking off the casing and the location of all the buttons and switches. Draw on the photos to indicate things. Turn it into a doc. Claude: Here's the full training document for your property manager: a 15-page Word file with all six photos annotated. Equipment ID, safety section up front (including the key point that the AC switch doesn't cut battery power), removing the casing step by step with the cover bolts marked, the front access panel annotated, the control board map with numbered markers and a matching legend table, a dedicated table for the four codes we hit (50, 38, 70, 91) with cause and fix, the exact repair sequence we followed, and a full code reference appendix.
"Draw on the photos" is literal: Claude annotated our phone pictures itself, marking the two cover bolts, mapping thirteen numbered controls on the board, and labeling every component inside the housing.
The collaboration ran both ways, which is our favorite exchange in the whole thread. Claude had been upfront that it couldn't pinpoint one small switch at the photo's zoom level, so we told it where the switch was. It didn't just take our word for it:
You: For the BACKDRIVE switch: it's the small switch underneath the three stacked blue rectangles, sandwiched between the two white plugs. Claude: That settles it, and you're right. The board's own silkscreen reads "BACKDRIVE" right above that metallic slide switch, tucked under the blue relays between the white plugs. Good catch. One helpful note for the doc: the little green item immediately to its left, between the plugs, is actually a fuse, so I'll make sure the training doc distinguishes the two.
It zoomed into the full-resolution board photo, read the silkscreen printed on the circuit board to confirm our correction, caught that the neighboring component was a fuse someone might confuse for the switch, and updated the manual's board map with a thirteenth marker.
That manual went to our on-site property manager and into the company repository. It records the exact equipment down to the board number and serial, how to open the casing (in the exact step order we dictated), how to read the error history, the four codes we encountered with causes and fixes, the limit and force procedure, a monthly safety checklist, and when to stop and call the installer. The next person who touches that gate starts from page one of a manual instead of from zero. The knowledge from one afternoon is saved to our corpus forever.
The error codes, for anyone who lands here from a search
| Code | What it means | What actually fixes it |
|---|---|---|
| 50 | Run-distance error ("gate unbalance"): the gate didn't travel its learned distance | Find and clear the mechanical bind (track debris, rollers, chain), then re-learn the limits |
| 38 | Hard-stop limit: the gate rammed its physical end stop | Re-set the limits so the gate stops a few inches short of the stops |
| 70 | Close photo eye triggered while closing | Usually normal (the eye doing its job); realign the lenses only if the path was clear |
| 91 | Force reversal: resistance exceeded the force setting | Set reversal force to a middle value, then re-run the obstruction test |
For a LiftMaster CSL24UL DC pad-mount slide gate operator; condensed from the factory manual and our repair. Full details live in the training guide described above.
The math, and the real point
The direct math is easy: a roughly $500 service visit avoided, zero dollars in parts, and a security gate back in service the same day instead of whenever the truck could come. The next day we did it again for a second, older operator at the property (a different fault: a bent bracket had let its limit-drive chain go slack, fixed with a crowbar) and that repair became its own 12-page report the same way.
But the real point is what this does to the economics of running physical property. Aging equipment used to mean a rolodex of specialists and a service premium on every hiccup. Now the diagnostic expertise is on demand: it reads the model tag from a photo, pulls the exact factory manual, translates the error codes, walks you through the machine switch by switch, holds the safety line, and then writes down everything it learned for the next person. Every repair makes the operation smarter instead of just poorer.
This gate fix happened during the same stretch of weeks in which AI rebuilt our Dothan website, took over our Google Ads, and started running our vendor RFPs. Same pattern every time: point the AI at ground truth, let it do the tedious expert work, keep a human on the trigger, and save the output back into the company's knowledge base.
Equipment: LiftMaster CSL24UL DC pad-mount slide gate operator (plus an older Elite SL3000UL, the second gate). Transcript excerpts are from our actual Claude conversation of May 22, 2026, lightly trimmed, with our own prompts cleaned up for spelling and grammar (they were dictated at a gate in the Texas sun). All photos are ours, taken during the repair; annotations were drawn by Claude for the training manual. A moving gate can cause serious injury: cut power before opening an operator, never raise the reversal force to push through a sticking gate, and always re-run the obstruction test after any adjustment.