Documentation

Before installing CaRPM - DeepScan, ensure your system meets these requirements:

On first launch, a setup wizard helps personalize your experience:

CaRPM - DeepScan supports three connection types. Select your scanner type on the Connection tab, choose your port/adapter, and click Connect.

Bluetooth is the most popular connection method. CaRPM - DeepScan offers two ways to connect:

Wired USB scanners provide the most reliable connection with no pairing required.

WiFi scanners connect over your local network via TCP socket.

When the connection is lost unexpectedly (scanner powered off, vehicle turned off, Bluetooth range exceeded), CaRPM - DeepScan automatically attempts to reconnect using exponential backoff:

• First attempt after 2 seconds
• Second attempt after 4 seconds
• Third attempt after 8 seconds

After 3 failed attempts, auto-reconnect stops and you'll need to reconnect manually. The status bar shows the reconnection countdown. You can disable auto-reconnect in Settings > App Settings.

The Connection tab is your starting point. It provides three radio buttons to select your scanner type (Bluetooth, Wired/USB, WiFi), a scanner/port dropdown, baud rate selector, and Connect/Disconnect buttons.

After connecting, the tab displays your connection status (green LED), ELM version (e.g., “v1.5a”), and the detected OBD protocol (e.g., “ISO 15765-4 CAN”). WiFi mode shows IP/port fields and a “Scan Network” button for auto-discovery.

A PuTTY-style terminal for direct communication with the ELM327 scanner. Type any AT or OBD command and press Enter to send.

Color coding:

• Blue [TX] — Commands you send
• Green [RX] — Responses received
• Red [ERR] — Errors
• Gray [INFO] — System messages

Features: Use ↑/↓ arrows to navigate command history. Click Export to save the terminal log to Excel. Click Monitor to toggle passive CAN monitoring (AT MA mode).

The Dashboard gives you a one-click overview of your vehicle's diagnostic health.

Vehicle Info: Displays VIN, decoded year/make/model, detected protocol, and MIL (Malfunction Indicator Lamp) status.

Health Score Gauge: A circular gauge (0–100) that summarizes vehicle health. Green (80–100) = healthy, Yellow (50–79) = attention needed, Red (0–49) = critical issues.

Scan Vehicle: One-click button that reads stored, pending, and permanent DTCs across all modules. Results appear as summary badges (Stored, Pending, Permanent counts) and a compact DTC table.

Clear DTCs: Clears all diagnostic trouble codes and resets the MIL light. The “Open DTCs Tab” link switches to the full DTCs view for detailed analysis.

The DTCs tab provides a detailed, module-grouped view of all diagnostic trouble codes.

Summary badges at the top show counts for Stored, Pending, Permanent, and Total codes. A Clear All DTCs button is available on the right.

Module tree: DTCs are organized in a hierarchical tree view grouped by module (Engine, Transmission, ABS, etc.). Each module node shows its count. Expand to see individual codes with their type and description.

Color coding by category:

• Red — Powertrain (P codes)
• Yellow — Chassis (C codes)
• Cyan — Body (B codes)
• Blue — Network (U codes)

Access all standard OBD-II modes and manufacturer-specific modes in one place.

Standard Modes (01–0A): Select a mode from the dropdown. For Mode 01 (Current Data), the app auto-discovers which PIDs your vehicle supports and presents them as checkboxes. Select PIDs and click Read to query values. Results appear in a response table showing PID name, raw hex, decoded value, and unit.

Additional modes include: Mode 02 (Freeze Frame), Mode 03/07/0A (Stored/Pending/Permanent DTCs), Mode 04 (Clear DTCs), Mode 05 (O₂ Sensor Monitor with voltage display), Mode 06 (On-Board Monitoring with PASS/FAIL results), and Mode 09 (Vehicle Information including VIN and Calibration IDs).

Manufacturer Modes (21/22):

Enthusiast+ Real-time PID graphing with up to 8 simultaneous channels.

Channel setup: Each channel has a colored indicator dot, a PID dropdown (populated with supported PIDs after connecting), and a live value display. Select a PID from the dropdown to activate a channel. Set to “Off” to deactivate.

Three view modes:

• Graphs — 4×2 grid of individual time-series plots (default). Each plot shows the last 60 seconds of data with auto-scaling Y-axis.
• Dials — 4×2 grid of circular arc gauges with animated needles, showing min/max/mean statistics for each channel.
• Merge — All active channels overlaid on a single plot for direct comparison.

Click Start Graphing to begin polling at 250ms intervals. Use Clear to reset all buffers. Export PDF generates a document with graph screenshots and data summary.

Professional+ Import and execute batches of diagnostic commands from Excel files.

Import: Click “Import Excel” to load a command set. The expected format is 3 columns: Command (hex, required), Module (label like ECM/TCM/ABS, optional), Delay (milliseconds between commands, optional). Click “Sample Format” to download a template.

Execution: Click “Run All” or select specific rows and click “Run Selected.” A progress bar shows completion percentage. Results appear row-by-row in the results table with command, module, raw response, decoded value, status, and elapsed time.

Fault Summary: After execution, a summary panel groups detected fault codes by module for quick analysis. Click “Export PDF Report” to generate a branded diagnostic report from the results.

Professional+ For advanced users who need direct control over OBD/UDS communication parameters.

Configuration fields:

• Protocol — Select from 13 OBD protocols or “Auto”
• Header — Set the CAN/ISO header address (e.g., 7E0 for engine ECU)
• Receive Address — Filter responses by address (optional)
• Service — Select a UDS service or enter a custom hex command
• Sub-function / DID — Additional parameters (service-dependent)

The app automatically sends the required AT setup sequence (reset, echo off, set protocol, set header, set filter) before your diagnostic command. Responses show raw hex with color-coded interpretation. A request/response history table logs all commands for review.

Professional+ Guided manufacturer-specific diagnostic procedures for 30+ vehicle brands.

How it works:

Example procedures: Steering angle sensor calibration, electronic throttle reset, DPF regeneration, brake/ABS bleeding, injector coding, oil service reset, transmission adaptive reset, and more.

Developer+ Passive CAN bus capture tool for monitoring all traffic on the OBD-II bus.

How it works: Super Miner sends the AT MA (Monitor All) command to passively listen to CAN frames without sending any requests. This captures inter-module communication visible through the OBD-II port.

The circular buffer holds up to 50,000 frames. Click Export PCAP to save in Wireshark-compatible format (libpcap with DLT_CAN_SOCKETCAN encapsulation).

Professional+ Maintain per-VIN customer records with service history tracking.

Left panel: A searchable list of all vehicle profiles. Search by VIN or customer name. Click “+ Add Vehicle” to create a new profile manually, or profiles are auto-created when a new VIN is decoded.

Right panel: Detailed form showing VIN, year, make, model, engine, customer name, customer phone, and freeform service notes. Below the form, a session history table shows all diagnostic sessions linked to this vehicle with date, port, command count, and DTC count.

Developer+ Two tools in a vertical split: the Python Scripting Console (top) and the Custom PID Builder (bottom).

Python REPL: An embedded Python console with a pre-injected obd namespace for direct scanner communication. Type commands at the >>> prompt and press Enter. Output is color-coded: blue for input, green for output, red for errors, cyan for info. Navigate command history with ↑/↓ arrows.

Custom PID Builder: Define custom OBD-II PIDs with name, mode, PID code, unit, min/max range, byte count, and a decode formula. A formula test dialog lets you enter sample bytes and verify the decoded result before saving. Custom PIDs automatically appear in Graph tab channel dropdowns.

Browse, search, export, and compare all recorded diagnostic sessions.

Summary badges at the top show total sessions, commands logged, DTCs recorded, and date range.

Left panel: Session list table with ID, start/end times, port, VIN, protocol, command count, and DTC count. Click a session to view its details.

Right panel: All command/response pairs for the selected session with timestamps, command descriptions, module names, raw hex, decoded values, status, and timing. A technician notes field at the bottom allows you to add freeform notes to any session.

Export options: Excel, CSV, JSON per session. Export PDF Report generates a branded scan report. Export Pack Professional+ creates a ZIP with PDF + CSV + VIN JSON. Compare lets you select two sessions (Ctrl+click) to diff side-by-side.

Open Settings with Ctrl + , or from the File menu. The Settings dialog contains three sections: License/Profile, Shop Branding, and Application Settings.

Profile section displays your current tier and expiration date. To activate a license:

An Upgrade button opens the pricing page in your browser if you're on a lower tier.

Professional+ Configure your shop's branding for PDF scan reports and customer exports.

• Shop Name — Your business name (appears in report header)
• Shop Address — Your business address
• Shop Phone — Contact phone number
• Logo — Browse for a PNG or JPEG image (recommended 200×100px). A preview shows below the path field. Click “Clear” to remove.

Branding data is stored locally in your configuration file and never sent to our servers.

• Auto-reconnect — Toggle automatic reconnection on unexpected disconnect (default: on)
• Baud Rate — Default serial baud rate: 9600, 38400, 115200, or 500000 (default: 115200)
• Theme — Switch between Dark (Tokyo Night) and Light themes

Window size and position are automatically saved when you close the application.

Professional+ Generate professional, branded diagnostic reports in PDF format.

Report contents:

• Shop branding header (logo, name, address, phone — if configured in Settings)
• Vehicle information (VIN, year, make, model, protocol)
• Health score summary
• All DTCs grouped by module with color-coded categories
• Complete command log with timestamps and responses
• Technician notes
• Report generation timestamp

Generate from: Data tab > Export PDF Report, Command Sets tab > Export PDF Report, or Graph tab > Export PDF.

Professional+ One-click export that generates a ZIP archive containing everything a customer needs:

• PDF scan report — Branded with your shop info
• CSV command log — Full diagnostic data
• VIN info JSON — Vehicle identification details (year, make, model)

Access from Data tab > Export Pack.

Developer+ Export CAN frames captured by Super Miner in Wireshark-compatible format.

The export uses libpcap format with DLT_CAN_SOCKETCAN encapsulation. Open the resulting .pcap file in Wireshark for protocol analysis, filtering by CAN ID, and detailed frame inspection.

Access from Super Miner tab > Export PCAP after stopping a capture session.

A step-by-step guide to setting up your ELM327 scanner for the first time.

Diagnostic Trouble Codes (DTCs) are fault codes stored by your vehicle's on-board computer when it detects an issue.

Reading DTCs:

Understanding DTC types:

• Stored — Confirmed faults. The vehicle has detected this condition multiple times.
• Pending — Conditions detected once but not yet confirmed. May clear on their own.
• Permanent — Cannot be cleared by the user. Require the vehicle to pass the related monitor test to auto-clear (typically 40+ drive cycles).

Clearing DTCs: Click Clear DTCs on the Dashboard or DTCs tab. This sends the Mode 04 clear command and resets the MIL light.

Enthusiast+ Monitor up to 8 vehicle parameters simultaneously in real-time.

Professional+ Execute manufacturer-specific diagnostic procedures safely.

Developer+ Automate diagnostics with the embedded Python REPL.

The Script tab provides a Python console with a pre-injected obd namespace for direct scanner interaction:

Available API:

• obd.send(command, timeout_ms=5000) — Send any AT or OBD command, returns a response dictionary with raw, lines, error, and error_message fields.
• obd.connected — Boolean indicating connection status.
• obd.protocol — String with the detected OBD protocol.
• obd.version — ELM327 firmware version string.
• obd.help() — Show all available methods and properties.

Developer+ Define your own OBD-II PIDs with custom decode formulas.

Located in the lower half of the Script tab, the Custom PID Builder lets you create PIDs that appear in Graph tab channel dropdowns.

Fields per custom PID:

• Name — Display label (e.g., “Turbo Boost Pressure”)
• Mode — OBD mode in hex (e.g., 01, 22)
• PID — PID code in hex
• Unit — Display unit (e.g., “kPa”, “RPM”, “°C”)
• Min / Max — Value range for gauge display
• Byte Count — Number of response bytes to expect
• Formula — Decode expression using A, B, C, D as response bytes

Formula examples:

• A - 40 — Single byte with offset (temperature)
• (A * 256 + B) / 4 — Two-byte value with scaling
• A * 0.392157 — Single byte with decimal scaling

Supported functions: abs, int, round, float, min, max, HEX2BIN, B(n). Use the Test button to enter sample bytes and verify your formula before saving.

Developer+ Capture and analyze raw CAN bus traffic for research and reverse engineering.

Professional+ Automate batch diagnostic scans with imported Excel command files.

Excel format (3 columns):

The loader also accepts code-style wrappers like commands.add("18 00 FF 00") and extracts the hex automatically.

Professional+ Build a customer database with per-VIN service history.

Professional+ For expert users who need to communicate with specific ECU modules using custom protocol parameters.

* Free tier: Limited to 2 vehicle makes, 2 models, and 5 Special Function executions.