Getting Started Guide
Welcome to the UDS Simulator. This guide will walk you through the first 5 minutes of your diagnostic journey, from powering up the virtual ECU to reading live vehicle data.
1. Access the Simulator
Navigate to the Simulator dashboard from the top navigation bar.
2. Power & Ignition
Ensure the system is ready for communication:
- Check the ECU Power indicator. It should be green.
- Verify the Ignition (KL15) status. If it’s red, toggle it to “ON”.
- The ECU starts in the Default Diagnostic Session (0x01).
The simulator mimics real vehicle behavior. If the ignition is off, most services will return “Conditions Not Correct” or result in no response.
3. Your First Request: Session Control (0x10)
Let’s elevate the diagnostic session to unlock advanced features.
- Locate the Service Selector in the Request Builder panel.
- Select DiagnosticSessionControl (0x10).
- Choose Extended Diagnostic Session (0x03) as the sub-function.
- Click the “SEND REQUEST” button.
Observe the Terminal
Watch the terminal output for the following frame exchange:
Request
10 03> Tester requests Extended Session transition.
Response
50 03 00 32 01 F4> ECU Positive Response (SID 0x10 + 0x40 = 0x50).
The status bar should now display “Session: EXTENDED”.
4. Reading Live Data (0x22)
Now that we are in an extended session, let’s read the current vehicle speed.
- Change the Service Selector to ReadDataByIdentifier (0x22).
- Select “Vehicle Speed” from the DID list (Identifier
0x0101). - Click “SEND REQUEST”.
- Observe the Live Cluster — the speedometer should reflect the value read from the ECU.
Request
22 01 01> Read Data Identifier for Vehicle Speed.
5. Staying Connected (0x3E)
In non-default sessions, the ECU expects a “heartbeat” to remain unlocked. This is handled by Tester Present (0x3E).
- If you stop sending requests for more than 5 seconds, the S3 Timer will expire.
- The ECU will automatically reset to the Default Session.
- You can enable “Auto Tester Present” in the settings to maintain the connection automatically.
6. Instrument Cluster Dashboard
The Cluster Dashboard (/cluster) is a real-time automotive instrument cluster that mirrors live ECU data visually — the same view a technician would see on a real vehicle.
Navigate to it via the Cluster tab in the top navigation bar.
What the dashboard shows:
- Speedometer & RPM gauges — dials update live from
0x22DID reads (e.g.0x0101Vehicle Speed) - Telltale warning lights — engine, ABS, battery, oil, temperature, and brake indicators reflect active DTC state
- PRND gear selector — shows the currently reported gear position
- Protocol State panel — displays the active UDS session and ECU connection status
Use the Cluster Dashboard to visually confirm that your diagnostic reads are producing the correct vehicle state. If the speedometer doesn’t move after a 0x22 request, check that you are in an Extended Session and the ECU is powered on.
7. Report Analysis
The Report Analysis page (/report) processes your diagnostic session traces — request/response pairs and telemetry — into a structured, filterable report.
Navigate to it via the Report tab in the top navigation bar.
Key capabilities:
- Demo scenarios — load pre-built traces (standard session, security attack, fuzzing) to explore the interface without a live session
- Import — upload a JSON diagnostic log from a previous session
- NRC filtering — drill into Negative Response Codes to identify failure patterns at a glance
- Export — download results as JSON; CSV and PDF export are available on premium plans
After finishing a diagnostic session in the simulator, open the Report page to review success rates, spot unexpected NRCs, and share findings with your team.
Next Steps
Now that you’ve mastered the basics, explore the detailed protocol specifications:
- 0x10 Diagnostic Session Control
- 0x27 Security Access
- 0x31 Routine Control
- Cluster Dashboard — Visualize live ECU data in a real instrument cluster
- Report Analysis — Analyze and export diagnostic session results