CarSolutions Admin
Sign in with your admin account.
Sign in with your admin account.
| Username | Email verified | Created |
|---|
| Username | Approved | Access | Tier | Expires | Valid | Last login |
|---|
Skips self-registration, CAPTCHA, and the approval queue - useful for phone/in-person sales.
Reusable templates - apply one to a user in one click instead of typing a tier/expiry by hand.
| Name | Tier | Duration (days) |
|---|
Upload a new client installer here and every customer's app updates itself silently on next launch.
The version must match the ClientInfo.Version baked into that build. Current published latest:
—
| Version | File | Size | Mandatory | Uploaded |
|---|
The whole system — accounts, licences, the coding catalogue, firmware, client installers and logs — lives in one database file. Download a backup anytime, and use Restore to load a backup onto this server (this is also how you migrate a server: download on the old one, restore on the new one).
Warning: this replaces every account and setting on this
server with the ones in the uploaded file, then restarts the server. The current database is kept as a
.replaced-*.bak next to it. Only restore a file you downloaded from a CarSolutions server.
These colors restyle the entire client — every screen, including diagnostics. Changes are baked into the client when you build & ship a new version (run protect-and-package.ps1, then upload the installer under Client updates).
Shown on the sign-in screen. Baked into the client at build time (no logo = the text wordmark is used).
| # | Key | Name | Vehicles | Years | Price | Active | File |
|---|
ClearVehicleFaults() / ClearModulesFaults() / ClearObdFaults() itself.
Build the coding as ordered steps - no code. Each coding step: pick the control module (dropdown or type the hex address), whether it's SFD-protected, then the coding type and its value. Long coding writes DID 0x0600; Adaptation uses the channel DID you type. Firmware/Dataset flash a catalog package (upload it in "Firmware & datasets" first). Steps run top to bottom; each reads the current value first so the log shows before/after. Mark a module SFD protected and the coding checks it up front: if SFD is locked anywhere, it stops with a message asking you to unlock SFD (with your tool) first, then re-run - nothing is changed until every SFD module is unlocked.
Upload any file and organise it into folders (e.g. VW / ID4 / 6C). Use New folder to create empty folders up front (no file needed); click a folder to open it, or use the breadcrumb / Up to go back. Search looks across all folders. Independent of the coding catalog and firmware packages.
Upload a .frf and it's parsed automatically — the flash blocks (addresses, sizes, data) are read from the file, so you can leave the address/routine fields blank for a .frf. (Tick "Raw image" only if you upload a pre-extracted image instead.) Link a package to a coding feature so the client downloads it, updates the module, then erases its local copy.
Two files (bootloader + firmware)? Just pick both in the upload form below - the firmware in "Firmware / dataset" and the bootloader in "Bootloader" - give it one name, and upload. They're packed as one entry (bootloader flashed first, then firmware). The operator picks the single entry and clicks flash. (You can still add more follow-up files later with the Files button on a row.)
| Name | Kind | Module | Make/Model | Target | Parsed | Size | Active |
|---|
Upload the ARBEITSDATEI_ERS_IA.xml that ODIS/Service 42 gives you and everything is unpacked automatically: the .frf, its .sig signatures, the ZDC name/version, the login code and the coding value. No manual extraction, no separate .sig, and the module's dataset name gets written on flash. (Pick Make/Model; the control unit is auto-selected from the file when recognised.)
The delivered file name is what the feature's script reads via GetAttachedFileBytes(name) - it also gets a "name.meta" sidecar with the address/routines above.
| Feature | Package | Delivered as |
|---|
Everything recorded for a car in one place - coding runs, firmware flashes, firmware downloads and full DTC reads. Search by VIN, or leave blank to see the most recent activity across all cars. Click "View" on a DTC read to see every fault code (raw code, VW code, status and description).
| Type | VIN | Detail | Result | Date |
|---|
The VW fault-code database (extracted from ODIS) that turns a car's raw codes into the correct VW codes and descriptions. Build dtc_db.json with the extractor, gzip it, and upload it here - it loads straight into the server, no client update needed.
Set up email so the app can send activation links, password resets and newsletters. New sign-ups only get an activation email once this is enabled.
Email all approved customers (who haven't unsubscribed) about big updates or client issues. Send a test to yourself first — then send for real. Each real email gets a personal unsubscribe link. HTML is allowed in the message.
Customers requesting a coding they aren't entitled to yet - approving one grants the entitlement immediately, so only approve once you've actually been paid through your normal process.
| VIN | Feature | Price | Requested |
|---|
| Feature | Granted | Notes |
|---|
Forces the next lookup for this VIN to re-query NHTSA/Vincario instead of using a previously cached result - useful after a decode-logic fix, like removing a bad cached answer.