JET Master Tutorial: Getting Started Guide
The Short Answer
Getting started with JET Master takes four steps: connect and select your VCI, connect to the vehicle and read the VIN, run a full-module fault scan, and then — with a saved backup in place — begin exploring CCF editing. This tutorial walks through each step so your first session with JLR's capable engineering tool ends in confidence, not confusion.
The tutorial assumes your software is installed and licensed. If you are still choosing between licence tiers, the JET Master vs JET Pro guide covers the differences before you buy.
Step 1: VCI Configuration
JET Master needs to know which interface it is talking to before anything else works. Connect your VCI by USB, confirm the drivers installed, then open the software's VCI configuration menu and select your device — SX-DOIP or JLR ENET for DoIP vehicles, a J2534 passthru driver for SX-CAN-era CAN vehicles. Save, and the software is linked to your hardware.
We recommend the SX-Tool JLR diagnostic interface for universal coverage across both network generations. Whatever you use, the rule is the same: configure the VCI first, and never assume last session's selection survived an update or a laptop change.
Step 2: Connect to the Vehicle and Read the VIN
Connect the VCI to the vehicle's OBD port, switch the ignition on, and click Read VIN. JET Master identifies the vehicle, its model year and key systems automatically — a successful VIN read confirms you have a stable, correctly configured connection before you touch anything else. Never skip this verification step.
The VIN read does more than prove connectivity: it anchors every later function to the correct vehicle definition. If the returned VIN does not match the car in front of you, stop and investigate — mismatched identity data is how configuration errors begin. You can cross-check what a VIN should decode to with our free JLR VIN decoder.
Step 3: Run a Full-Module Fault Scan
With the vehicle identified, open the diagnostics tab and read all modules. JET Master polls every control unit on the network and returns the full DTC picture — including manufacturer-specific codes that generic OBD scanners never see. This global scan is the correct baseline for any job: diagnose from the whole vehicle, not one module.
Save or screenshot the results before clearing anything. Stored and pending codes, freeze-frame data and module software levels are evidence — and on complex JLR platforms, the relationship between codes across modules is often the diagnosis itself. Clear codes only when you have captured the full picture.
Step 4: First Steps in CCF Editing
The CCF — the vehicle's configuration file — is where JET Master's real power lives, and where discipline matters most. Read the CCF from the vehicle, then immediately save that original file somewhere safe before changing anything. Only then browse parameters, make your changes, and write back. The backup you saved is your way home if anything goes wrong.
For your first edits, choose simple, reversible parameters and verify each change behaves as expected before moving on. The deeper methodology — parameter families, platform differences and safe workflow — is covered in our CCF editing guide. Treat CCF work like surgery: preparation and backups first, then the incision.
Where to Go Next
This getting-started path — VCI, VIN, global scan, backed-up CCF work — is the foundation every advanced JET Master workflow builds on. From here, live data, service routines and module programming open up quickly. Invest the time in the fundamentals now and the complex jobs become routine rather than risky.
A few habits are worth forming from the very first session, because they are much easier to build early than retrofit later. Always work with a battery stabiliser connected for any write operation, not just full module flashes. Keep a folder structure for saved files — original CCFs, session logs, scan reports — named by VIN and date, so every vehicle has an audit trail you can return to months later. And treat every write as reversible only if you hold the backup: the discipline of "read, save, then edit" should be automatic before your fingers touch the write button.
It also pays to understand where JET Master sits relative to the dealer toolchain. Pathfinder and TOPIx Cloud remain the source for official guided procedures and calibration files; JET Master is where the engineering work happens — the CCF edits, used-module commissioning and feature work the dealer tools do not offer. Most professional users run both, each for what it does best. If your background is SDD-era and you are moving into DoIP vehicles, that dual fluency is exactly the skill set the current job mix rewards.
When you are ready to extend the same workflow to vehicles that are not in your workshop, the SX-LINK remote diagnostics setup carries JET Master sessions over the internet — the same discipline, at any distance.
Finally, a word on support. Every new user hits the same early questions — driver quirks, a VCI that will not enumerate, a CCF parameter whose label differs between model years — and the difference between a stalled evening and a solved one is access to people who have seen it before. SX-Tool's support is staffed by working technicians rather than script readers, and the tutorial library grows from real support cases. Use both without hesitation: asking early is faster than guessing, and the platform's depth rewards every hour you invest in it.
Frequently Asked Questions
Which VCI should I use with JET Master? SX-DOIP is the recommended choice for modern DoIP vehicles; a J2534 passthru device covers CAN-era platforms through SX-CAN. Whichever you use, select it explicitly in the VCI configuration menu before connecting to a vehicle.
Does JET Master work on pre-2017 vehicles? Yes — coverage spans both JLR network generations: CAN-based vehicles handled through the passthru/SX-CAN path, and DoIP vehicles from around 2017 through ENET or SX-DOIP. The software selects the appropriate communication path for the identified vehicle.
What happens if I write a bad CCF to the car? This is exactly why step four demands a saved original first. With the backup on disk, you restore the known-good file and the vehicle returns to its prior state. Without it, recovery becomes a much longer job — the backup is non-negotiable.
Do I need a battery stabiliser connected to the vehicle? For reads and CCF edits, a healthy battery is usually sufficient. For module programming and flashing, a proper stabilised power supply is mandatory — voltage dips mid-flash are the classic cause of bricked modules, remote or local.
Can I run JET Master sessions remotely? Yes. Paired with SX-LINK, the full JET Master workflow runs on a vehicle anywhere with internet access, using the same encrypted connection described in our SX-LINK documentation. The vehicle-side user only connects the kit to the OBD port and Wi-Fi.
Get the Tool and Get Started
JET Master is the SX-Tool engineering suite for serious JLR diagnostics, coding and programming. Specifications, licence options and current pricing are on the JET Master product page, and the SX-Tool team can advise on the right VCI pairing for the vehicles you see most.