As of October 2026, our instant VATS-OFF covers 1986 to 1993 GM memcal calibrations on two verified masks — $8D on the 1227727 and 1227730 tuned-port computers and $DA3 on the 16159278 LT1 — for $150 per file, or $250 mail-in if you cannot read the chip yourself. It changes one enable bit and the checksum that goes with it. Whether that fixes your car depends on a question most people skip: is the computer actually the thing refusing to run the engine?
This post is the long answer. It covers what the Vehicle Anti-Theft System was, where in the chain it can fail, which of those failures live in the chip, and what a read has to look like before we will touch it.
What VATS was, in one paragraph
General Motors fitted the Vehicle Anti-Theft System to its performance cars from the mid 1980s. The visible part is the resistor pellet set into the blade of the ignition key. A theft-deterrent module measures that pellet when the key is turned, compares it with the value the car was built to expect, and if the two agree it does two things: it allows the starter to engage, and it sends the engine computer a fuel-enable signal. The engine computer, for its part, watches for that signal and withholds injector pulses if it does not see one.
That last sentence is the whole reason a chip change can matter. The computer is one of two places the system can say no, and it is the only one that lives in software.
The chain, and where a memcal fits in it
A cranks-but-will-not-fire complaint on one of these cars has four candidate causes, and only one of them is in the chip.
| Where the fault is | What you see | Fixed by a VATS-OFF file? |
|---|---|---|
| Key pellet worn or contacts dirty | Intermittent no-crank, security lamp, starts after a wait | No — a key or lock-cylinder repair |
| Theft module or its wiring failed | No-crank, or cranks with no injector pulse | Only the injector-pulse half; the starter side is separate wiring |
| Engine transplanted into a vehicle that never had the module | Cranks, no injector pulse | Yes — this is the classic case |
| Computer calibration never used VATS | Whatever the real fault is | No — there is nothing in the chip to disable |
The third row is why this product exists. A tuned-port or LT1 engine moved into a truck, a street rod or an older chassis arrives without the theft module, the key and the lock cylinder it was built to talk to. The computer is healthy and is doing exactly what it was programmed to do: waiting for a signal that nothing in the new vehicle can send. Our engine swap immobiliser guide sets out the same decision across the other platforms we cover.
The fourth row is the one that costs people money elsewhere. Some calibrations that run on the same computer part numbers never consult the anti-theft input at all. A file service that accepts the upload, flips a bit that was already off, and charges for it has sold nothing. Our calculator checks for this before payment, and when it finds a calibration with no active VATS it says so in plain words — the no-start is most likely in the key pellet or the theft module, it is not fixed in the chip, and you are not charged.
The families the instant path covers
Coverage here is by mask, not by model. A mask is the identifier for the program a calibration runs on, and it decides where the anti-theft enable bit lives. Two cars with the same engine can run different masks, and one computer part number can run more than one.
As of October 2026 the instant path accepts:
- $8D — the mask used by the 1227727 and 1227730 computers on tuned-port 5.0 and 5.7 litre engines, in Camaro, Firebird and Corvette applications from the 1986 to 1993 range.
- $DA3 — the mask on the 16159278 computer used with the LT1 in Camaro, Firebird and Trans Am applications.
A calibration that does not match a mask we have verified against real files is refused before payment and routed to mail-in for manual review. That includes any LT1 Corvette calibration on a mask we have not yet confirmed, and the earlier, smaller chips: a 16,384-byte read belongs to the 27C128-era memcal, which is not supported in the instant path yet.
That is a deliberately narrow list. It is the same principle as our coverage matrix, which tracks every ECU family with a separate status rather than a single supported flag: we would rather refuse a file than guess at one, because a guess on a thirty-year-old chip is a car that does not start and a customer who has no idea why.
What a valid read looks like
The memcal is a small removable carrier in the computer that holds the calibration chip. The chip is a 27C256, a 32-kilobyte EPROM, and a correct read of it is exactly 32,768 bytes. This is not one of the access levels in our bench, boot and OBD read methods guide — it is older than all three. There is no diagnostic-port read on these computers. The chip comes out of the car and goes into a programmer.
Three things go wrong at this step, and the calculator tests for each of them.
The wrong device selected. A 65,536-byte file is the single most common bad upload. It means the programmer was set to 27C512 rather than 27C256, and it read the chip twice over. Select the right device and read again; nothing is wrong with the chip.
A chip that is not making contact. These parts are three decades old and have usually been pulled from a carrier they were soldered into. Oxidised or bent pins produce a read that completes without an error and contains repeating blocks where real data should be. The tell is that two reads of the same chip do not match each other. Read it three times and compare the files. All three should be identical; if they are not, clean the pins, reseat the chip fully and try again.
A file that does not add up. A genuine calibration is internally consistent: it carries a checksum over its own contents. A read off a chip with poor contact fails that test and cannot pass it by accident. We check it before anything else is offered.
A tool that reports success has told you it finished, not that it produced a good file. Our upload-rejection post covers the same distinction on modern controllers, and it applies with more force here because the hardware is older.
“The programmer will happily read a chip that is sitting crooked in the socket and tell you it went fine. Three reads that match are worth more than any message on the screen.” — File-service desk, ECU Flash Cartel
What changes in the file, and what does not
When a file passes, the change is small enough to state completely: the anti-theft enable bit is cleared, and the calibration checksum is recalculated so the computer accepts the result. Your own calibration is preserved. If the chip you sent has a previous owner's fuel or spark changes in it, they come back untouched.
Before a processed file is released, our own check confirms that the only bytes which differ from your upload are the anti-theft byte and the checksum. If anything else has moved, the file is not delivered. That rule exists because the alternative — handing back a file that is nearly right — is worse than handing back nothing.
Keep the original read. It is the only artefact that puts the chip back exactly as it was, and our return ECU to stock post makes the case for treating that file as the most valuable thing in the job.
Writing it back
The instant path ends with a file. Getting that file onto a chip is your side of the work.
An original memcal chip is ultraviolet-erasable, which means it has to be erased under a UV lamp before it can be reprogrammed. Many people burn the new file to a fresh chip instead and keep the original untouched in a drawer, which is the approach we would take: it costs a few dollars and it preserves a known-good part. Either way, verify the burn against the file before the chip goes back into the carrier, and seat the memcal firmly. A carrier that is not fully home produces symptoms that look exactly like a bad calibration.
If you do not own a programmer and have no wish to, the mail-in route is the same work done at our bench for $250: we read the chip, process the file and burn the result.
What VATS-OFF will not do
It will not make the starter engage on a car whose theft module is refusing to release it. The module controls the starter through its own relay circuit, and the computer has no part in that. On a transplant this rarely matters, because the new vehicle has its own starting circuit. On an original car with a failed module, a chip change addresses fuel and leaves the crank side exactly where it was.
It will not repair a worn key pellet or a broken wire in the steering column. Those are the common failures on an original car, and they are repairs to hardware.
It will not help a later GM vehicle. The systems that followed work differently and are married to the vehicle through the body computer; on a modern GM the route is a programming session through the manufacturer's own application, which our GM session guide covers. Reaching for a chip-era answer on a network-era car is one of the more reliable ways to waste a weekend.
If you are not certain which of those you are looking at, our security light, no start diagnosis post sorts the question into branches before you spend anything.
Ownership, and why we ask
Disabling an anti-theft function is a security-relevant operation, and we treat it as one on every make. We require proof of ownership for any operation that touches an immobiliser chain and we decline the request when it is not forthcoming. On these cars that is rarely a difficult conversation — the typical customer has a title, a build thread and an engine on a stand — but the rule is the same whether the car is a 1989 or a 2019.
Vehicle theft is not an abstract concern. The Insurance Institute for Highway Safety publishes theft-claim data by model precisely because immobiliser design changes theft rates in ways that show up in insurance losses. A service that removes an anti-theft function without asking who owns the car is contributing to that number.
A worked example
A common job: a 5.7 litre tuned-port engine from a late-1980s Firebird, going into an older pickup. The harness is in, the engine cranks strongly, and there is no injector pulse.
The owner pulls the memcal and reads the chip. The first upload is 65,536 bytes and is refused with the reason given: the programmer was set to the wrong device. The second is 32,768 bytes, passes the read-quality and checksum tests, and is identified as an $8D calibration with VATS active. That is the verdict that matters — the computer really is waiting for a signal the truck cannot send.
Payment is $150, the processed file comes back in seconds, and the release check has confirmed that two bytes changed. The owner burns it to a fresh chip, verifies, refits the memcal, and the engine fires.
The whole exchange turns on the verdict before payment. Had the same owner uploaded a calibration with no active VATS, the answer would have been that the chip is not the problem — and the afternoon would have gone into the wiring instead of into a file that changed nothing. A swapped ECU that will not start has several possible causes, and the immobiliser is only the most famous of them.
Standards and the legal position
There is no pass-thru interface in this story. SAE J2534 — the standard that makes independent programming of modern controllers possible — postdates these cars, which is exactly why the work is done on a chip rather than through a connector.
We do not provide emissions defeat, delete files, or services intended to bypass emissions laws. Our services exist for tuning preparation, diagnostics, repair, motorsport, and off-road use where legally permitted. Customer is responsible for confirming legal use in their location and application.
An anti-theft change is not an emissions change, and this file alters nothing that affects what leaves the tailpipe. The federal Clean Air Act still governs the rest of the calibration and the hardware on the engine, and an engine transplant brings its own registration and inspection rules that vary by state. Those are the owner's to confirm.
The short version
VATS-OFF is one bit and a checksum on a 27C256 memcal, $150 instant or $250 mail-in, for $8D calibrations on the 1227727 and 1227730 and $DA3 on the 16159278. It fixes a computer that is withholding fuel because the anti-theft signal is gone, which is the engine-swap case. It does not fix a key, a module, a starter circuit or a calibration that never used VATS — and for that last one, the calculator tells you before you pay. Read the chip three times, upload the file at the VATS-OFF calculator, and let the verdict decide what you do next.