Firmware, vehicle database and subscription: what must be current before a key job
Before a key-programming job, confirm three separate things: the tool firmware can run reliably, the vehicle database contains the exact platform and function, and the account or subscription authorizes any required online service. Updating one of those items does not prove the other two are current or that the vehicle is supported.
Firmware defined: firmware is software that operates the device or interface. Vehicle database defined: a vehicle database is the tool’s coverage, menu, and procedure data. Subscription defined: a subscription or entitlement is the authorization that may permit updates or server-dependent functions.
What must be updated before key programming?
Read the planned function first. A tool can have current tablet firmware yet lack the needed vehicle coverage. A current database can show a function that needs a valid account session. A valid subscription can authorize a download but not make an incompatible VCI speak a newer protocol. Record tool model, VCI model, installed database version, update date, account status, vehicle year, market, and exact module before connecting to a write operation.
Autel’s official support information describes sign-in, activation-code redemption, and subscription handling as separate account actions. Autel’s update instructions are a direct source for that vendor’s account workflow. They do not establish coverage for a specific vehicle.
Firmware, database, and entitlement compared
| Item | Question to answer | Evidence | What it cannot prove |
|---|---|---|---|
| Firmware | Can tablet and VCI operate reliably? | Installed version and release note | Vehicle function coverage |
| Database | Does the exact vehicle menu exist? | Year, region, system, function path | Online authorization |
| Subscription | Is a required service permitted? | Account and entitlement status | Correct key or module selection |
| Procedure | Is the requested action documented? | Named operation and warnings | Successful real-world key function |
A useful preflight is five minutes of read-only work: power the device, confirm the interface connection, open the exact vehicle family, verify the current menu’s year and market, and read the support note for the chosen function. If the job requires online access, test the account before vehicle security access begins. Do not update a tablet or database while a vehicle is in the middle of a programming routine.
Why a current update can still show no function
Coverage can be limited by region, engine or keyless configuration, gateway, VCI hardware, or the operation type. “2019 model supported” does not mean every 2019 market variant, all-keys-lost path, and remote function are supported. An authorization message can represent entitlement, while an absent menu can represent database or compatibility; preserve the exact wording instead of collapsing both into “needs update.”
Equally, an update cannot repair poor supply voltage, a non-responding module, or a wrong key. Internet-dependent functions should be separated from the local vehicle link before troubleshooting begins.
Worked readiness check with numbers
For one planned add-key task, record 6 items: vehicle VIN, model year, market, module part number, tool database release, and VCI firmware release. Add 4 checks: battery support connected, exact menu visible, entitlement signed in if required, and all retained keys inventoried. Ten recorded facts make a later refusal diagnosable. A single phrase—“tool updated”—contains none of them.
Ford’s PATS aid uses named security-access and key-code procedures, reinforcing that the selected function matters as much as software state. The PATS/RKE Dealer Aid remains specific to its covered vehicles, so do not import its timing or erase behavior elsewhere.
Common readiness mistakes
- Updating at the vehicle during an active session: prepare device maintenance beforehand.
- Choosing by brand only: confirm year, market, architecture, and module.
- Assuming subscription means coverage: inspect the exact menu.
- Assuming a database menu means entitlement: test account requirements before security access.
- Ignoring VCI firmware: interface capability can be the limiting component.
- Using an update as a substitute for diagnosis: verify power, network, and module communication independently.
Boundary and validation
Software readiness does not authorize protected functions or compensate for missing vehicle documentation. If the requested operation is not clearly supported, do not select a similar vehicle menu as an experiment. Preserve vehicle state and obtain the correct procedure.
After any authorized result, test lock, unlock, engine authorization, and passive entry separately. Record which of the four functions passed, the database release, and the exact operation used; a green update indicator is not a functional vehicle test.
Change control for tool updates
Write down the version before and after an update and read the release note for the exact function. If the update changes a menu or warning, repeat only read-only identification checks before a vehicle write. Keeping this small change record prevents a later operator from attributing a coverage difference to the car when the database itself changed.
Maintain device charging, interface firmware, and account access as workshop preparation, not an emergency repair at the car. A key job should begin with a stable known tool state and a verified vehicle path.
If a database update changes supported wording, save the previous and new release numbers. Support coverage is an explicit claim that can be checked; it should never be inferred solely from a newer date on the tablet home screen.
When a software release is not current, schedule its installation and confirm normal operation away from the vehicle. Verify that the interface reconnects, the correct regional database is selected, and the account page is available before beginning a protected key procedure.
Where the device provides a support matrix, save the exact row or function name with the job record. That is more reliable than interpreting a broad marketing claim as a promise that every key procedure is available.