Perform a comprehensive diagnostic scan of the Rivian EDV 500's vehicle systems using Rivian diagnostic software to identify fault codes, system status, and component health.

Warnings

Tools required

Preparation

1. Park vehicle on level surface and engage electronic parking brake
2. Ensure vehicle is in Park mode and powered off completely
3. Verify 12V battery voltage is above 12.4V; connect battery maintainer if voltage is low
4. Obtain vehicle VIN, current mileage, and customer concern description
5. Ensure diagnostic laptop has latest Rivian Service Toolkit software installed and updated
6. Verify stable internet connection for diagnostic software authentication and TSB access
7. Clear workspace around driver's seat area for laptop placement and cable routing

Procedure

1. 1

   Locate OBD-II diagnostic port
   Open driver's door and locate the OBD-II diagnostic port underneath the dashboard on the left side of the steering column. Remove any protective cover if present. The EDV 500 uses a standard 16-pin connector located above the hood release lever.
2. 2

   Connect diagnostic interface
   Connect the J2534 pass-through interface securely to the vehicle's OBD-II port. Ensure connection is fully seated and locking tabs engage properly. Connect the USB cable from the interface to your laptop. Wait for the interface to power up and establish connection (LED indicators should show power and communication status).
3. 3

   Launch Rivian Service Toolkit
   Open Rivian Service Toolkit software on the laptop. Log in using authorized service credentials. Select 'New Vehicle Session' and allow the software to establish communication with the vehicle. The software will automatically detect the vehicle VIN and configuration. Verify displayed VIN matches the vehicle being serviced.
4. 4

   Perform initial vehicle identification
   In RST, navigate to Vehicle Identification screen. Confirm all vehicle details including model year (2025), variant (EDV 500), battery configuration, and software versions for all detected modules. Document the current software versions for Gateway, BMS (Battery Management System), VCU (Vehicle Control Unit), and both motor control units. Note any calibration mismatches flagged by the system.
5. 5

   Execute global system scan
   Select 'Global System Scan' from the main diagnostic menu. This will interrogate all vehicle control modules including: Gateway, Vehicle Control Unit, Battery Management System, Front Motor Control Unit, Rear Motor Control Unit, Brake Control Module, ADAS systems, Body Control Module, HVAC controller, and charging system controller. Allow scan to complete fully, typically 3-5 minutes. Do not interrupt power during this process.
6. 6

   Review and document fault codes
   Once scan completes, review all Diagnostic Trouble Codes (DTCs) displayed. For each code, document: module name, DTC number, fault description, status (current/pending/history), occurrence count, and freeze frame data. Pay special attention to any HV system faults (P1xxx codes), battery isolation faults, motor control errors, and charging system faults. Use RST's built-in code descriptions and recommended actions.
7. 7

   Check high voltage system status
   Navigate to Battery Management System module in RST. Review HV battery pack status including: total pack voltage, individual cell group voltages, cell voltage delta (should be under 50mV), pack temperature readings, State of Charge (SOC), State of Health (SOH), insulation resistance values (should exceed 500 ohms/volt), and contactor status. Document any values outside normal parameters or yellow/red warning flags.
8. 8

   Verify motor system parameters
   Access both Front and Rear Motor Control Unit modules separately. Review motor temperatures, resolver/encoder status, inverter temperatures, phase current balance, and motor performance parameters. Check for any torque limiting conditions, thermal derating flags, or communication errors between VCU and motor controllers.
9. 9

   Inspect charging system data
   In the Onboard Charger and DC Fast Charge Controller modules, review charging history, pilot signal status, charge port lock mechanism operation, inlet temperature sensors, and any charge fault counters. For fleet vehicles, verify charge scheduling and location-based charging parameters are correctly configured.
10. 10

    Evaluate ADAS and safety systems
    Check all Advanced Driver Assistance System modules including Forward Collision Warning, Automatic Emergency Braking, Lane Keeping Assist, and camera/radar sensor modules. Review calibration status and verify no pending calibration requirements. Document any camera or radar blockage faults that may require cleaning or recalibration.
11. 11

    Review live data streams
    Select relevant control modules based on customer concern and view live data PIDs (Parameter IDs). Monitor real-time sensor values, switch states, and system commands. For intermittent concerns, use data logging function to record extended sessions. Typical parameters to monitor: accelerator pedal position, brake pedal position, vehicle speed, torque requests, actual torque delivery, and any relevant environmental sensors.
12. 12

    Check for Technical Service Bulletins
    Within RST, access the TSB (Technical Service Bulletin) database. Enter the vehicle VIN to automatically filter relevant bulletins. Review any open campaigns, software updates, or known issues related to documented fault codes or customer concerns. Document applicable TSB numbers and recommended corrective actions.
13. 13

    Generate diagnostic report
    Use RST's report generation function to create a comprehensive diagnostic summary. Include: all fault codes with freeze frame data, system health status for all modules, software version inventory, relevant live data snapshots, and applicable TSBs. Save report to vehicle file and export PDF copy for customer documentation. Include screenshots of critical data if anomalies were found.
14. 14

    Clear codes if appropriate
    Only after documenting all faults and determining root cause, clear diagnostic codes if appropriate for diagnostic process. Do not clear codes if: they relate to safety systems without repair completion, battery isolation faults are present, or codes are needed for warranty documentation. After clearing, perform a quick re-scan to verify codes do not immediately return, which would indicate an active fault condition.

Reassembly

1. Properly disconnect diagnostic interface from OBD-II port and store cables
2. Replace any OBD-II port protective cover if equipped
3. Ensure no tools or equipment left in vehicle cab
4. Close all vehicle doors and verify interior lights shut off properly

Verification

• Verify diagnostic software successfully logged out of vehicle session
• Review all documented fault codes and diagnostic data for completeness
• Ensure diagnostic report has been saved to both local system and vehicle service file
• Confirm any critical safety-related faults have been communicated to vehicle owner/fleet manager
• If codes were cleared, verify vehicle completes self-check cycle without immediate fault return
• Test vehicle readiness by powering on and confirming no warning lights illuminate on instrument cluster beyond those associated with documented faults

More procedures for this vehicle