
Get vehicle monitors and diagnostic scan tool results in under 15 seconds, saving you valuable time.

Access deeper insights with 90%+ OEM coverage, including advanced B, C, U, & P codes that other tools miss.

Comprehensive diagnostics for a wider range of vehicles with 138 OEM protocols covered, ensuring no vehicle goes unchecked.
Find quick answers for dealers, auctions, inspectors, managers, and integration partners using CarDr and OBDIQ. This page explains how scanning works, what CarDr reports can show, where to download the app, how to view completed scans, how the manager portal works, and where to go for support, sample reports, and integrations.
CarDr is a vehicle diagnostics and condition-reporting platform built for dealers, auctions, inspection teams, fleet users, warranty and underwriting workflows, and automotive software partners.
CarDr is built for multiple user groups, including used-car dealers, franchise dealers, auctions, field inspectors, managers, service operations, fleet teams, and platform partners that want diagnostic data inside their own applications.
Yes, you do. Therefore, please ensure you have an active internet connection before using the app to get the best and most accurate results.
CarDr.com is billed month-to-month. Moreover, there are no long-term contracts or commitments.
For all billing-related questions, please email support@cardr.com.
Alternatively, you may call and speak to a live agent at 800-932-1120 OP.2, Monday to Friday, 7am CT to 7pm CT.
CarDr.com accepts all major credit cards, debit cards, and ACH withdrawal.
iPhone devices running iOS 16 and above and Android phones running Android 8 and above are supported.
You can view your completed scans on both the mobile application and the desktop web portal.
Furthermore, your scan history stays synced across devices for convenience.
There is no additional charge for adding users.
Currently, a CarDr Admin can add users through the web portal.
However, dealership managers will also receive this access soon as part of an upcoming update.
CarDr combines the OBDIQ mobile app, the ULTRA OBD adapter, cloud services, sample report outputs, and manager tools. The platform is designed to deliver faster scans, broader OEM protocol coverage, deeper module access, and clearer reporting than basic generic OBD readers.
Many scans complete in about 15 seconds, although actual scan time varies by vehicle. Some vehicles have more ECUs and require more communication time than others.
Depending on the workflow and vehicle, CarDr reports can include VIN and vehicle details, current and historic DTCs, advanced B/C/U/P codes where supported, code reset information, emissions readiness, repair estimates, recalls, and condition-report style outputs.
The current FAQ page states support for iPhone devices on iOS 16 and above, and Android phones on Android 8 and above.
The current website FAQ states that CarDr is billed month-to-month and does not require a long-term contract.
The current website FAQ states there is no additional charge for adding users.
Have a compatible iPhone or Android phone, Bluetooth turned on, mobile data turned on, the OBDIQ app installed, your login credentials ready, the vehicle started, and the ULTRA adapter fully seated in the OBD port.
Typical field flow: turn on Bluetooth and mobile data, open OBDIQ and allow permissions, sign in, start the vehicle, plug in ULTRA, tap Advanced Scan, enter mileage, and tap Continue.
Yes. For the auction inspector workflow, the vehicle should be started before scanning unless a site-specific process tells users otherwise.
Stay within about 5 feet of the active ULTRA adapter during the scan. Leaving the area or moving too far away can interrupt communication.
Yes, but concurrent scans should be separated. A practical field rule is to keep active scan vehicles roughly 15 feet apart and avoid Bluetooth congestion around the active device.
On first launch, users should allow the requested app permissions. If Bluetooth-related permissions are denied, the app may not connect properly to the ULTRA adapter.
Review results on the main results screen, tap Complete to save the scan, then open Scan Results to view the saved report and share or reference it as needed.
Code-clearing functions should be used carefully and only under the correct workflow. On vehicles with aftermarket programming or custom settings, clearing codes may remove stored settings or custom programming.
Inspectors use CarDr to make the inspection process fast and comprehensive, to access deeper code coverage including advanced B/C/U/P codes, and to improve consistency across a broad set of OEM protocols.
Turn on Bluetooth and mobile data, open OBDIQ and sign in, start the vehicle and plug in ULTRA, tap Advanced Scan, enter mileage, continue, review results, tap Complete, and open the saved scan.
Check that Bluetooth is on, app permissions were allowed, the phone is within about 5 feet of the adapter, and the app is reopened if needed.
Make sure the vehicle is started and the ULTRA adapter is fully seated in the OBD port, then retry Advanced Scan.
Some vehicles simply take longer because there can be 100 or more ECUs to read. Wait for completion and do not unplug the adapter during the scan.
The scan may not have been fully saved. Tap Complete, confirm the save, then open Scan Results and select the saved report.
Field users should follow normal site support escalation and then contact support@cardr.com if the issue continues.
Managers can use the CarDr web portal at prods.obdiq.com with their manager credentials.
Managers can view scan reports, track inspections by inspector, search scans by VIN, search by location, look up arbitration vehicles by VIN, and filter scans by date.
Yes. The revised manager guide describes filtering by location, user or inspector, VIN, vehicle make, model, and year.
The guide describes Snapshot, Customer Summary, and Full Scan Report views. Snapshot provides a quick code list and overview. Customer Summary adds repair cost and code descriptions. Full Scan Report provides the most detailed scan output.
Completed scans can be viewed in the mobile app and in the web portal, with scan history synced across devices.
Yes. The manager portal is intended for viewing and printing scan reports, and CarDr also provides sample report pages and secure diagnostic links in broader workflows.
Yes. The CarDr SDK/API page describes both cloud-based APIs and ULTRA adapter plus SDK options for deeper embedded workflows.
Yes, for some use cases. The cloud API offering is positioned for VIN decode, DTC lookup, predicted component failure, code reset detection, repair estimation, emissions readiness, and condition-report outputs without requiring hardware in every workflow.
The SDK page states support for iOS, Android, and React Native.
The SDK/API page is written for developers, DMS providers, auctions, inspection platforms, dealership software, warranty apps, reconditioning workflows, and fleet services.
The site describes no integration, minimal integration, partial integration, and full integration options depending on whether a partner wants a branded app experience, link-based reporting, API access, or embedded SDK workflows.
The current FAQ page directs billing-related questions to support@cardr.com and lists phone support at 800-932-1120, option 2, Monday to Friday, 7am CT to 7pm CT.
The current website FAQ states that a CarDr admin can add users through the web portal.
Users can download OBDIQ from the Apple App Store and Google Play, or start from the CarDr app page on cardr.com/app/.
Useful entry points include the home page, app page, sample reports page, sign-up page, SDK/API page, the manager portal, and the inspector training video.

Diagnose vehicles instantly using the CarDr OBDIQ App.
Get faster, deeper, and wider vehicle diagnostics with real-time insights—built for dealers, technicians, and auto professionals.
View a sample OEM-level diagnostic report generated by CarDr.
Download the complete CarDr brochure with features, benefits, and use cases.
Explore detailed technical specifications, compatibility, and system requirements.