Support
Detailed adapter and vehicle support information
- Installation
- Using a Tactrix with Windows
- Supported Adapters
- Supported Vehicles
- Issues/Troubleshooting
Installation
Using a Tactrix with Windows
Atlas uses it's own built-in device driver for the Tactrix OpenPort 2.0. When using Atlas with a Tactrix in a Microsoft Windows environment, the adapter should appear in Device Manager as a Communications Port (COM*) under the Ports (COM & LPT) device category.
Atlas will not be able to successfully communicate with the adapter if it appears under the Vehicle PassThru Interfaces category as a Tactrix Openport 2.0 J2534 Vehicle Interface.
The Tactrix drivers must be uninstalled in order to proceed.
Driver Removal Steps
- Right click on Tactrix Openport 2.0 J2534 Vehicle Interface
- Select Properties
- Click the Driver tab in the Properties window
- Select Uninstall Device
- Restart your PC upon uninstaller completion
Supported Adapters
Atlas supports the following adapters and hardware through custom cross-platform device drivers that are built directly into Atlas. The listed adapters should work out of the box with no additional configuration required.
| Device | Platform | Connection | Type | Datalogging |
Flashing |
|---|---|---|---|---|---|
| Tactrix OpenPort 2.0 | Wired (USB-Mini B) |
OpenPort |
120Hz |
1~5 minutes |
|
| OBDLink MX+ | Wireless (Bluetooth 3.0) |
STN |
30Hz |
15~30 minutes |
|
| OBDLink EX | Wired (USB-A) |
STN |
60Hz |
5~20 minutes |
|
| Veepeak OBDCheck BLE+ | Wireless (Bluetooth LE) |
ELM327 |
20Hz |
30~60 minutes |
NAMR is always interested in expanding support to new adapters and hardware. If you have a device you’d like to see supported and isn’t listed here, please check our current hardware requests on GitHub and see if a ticket already exists for the device in question. If one doesn’t exist yet, consider opening a new adapter or hardware request.
Supported Vehicles
If a vehicle is supported, it may not be complete. Please report any missing tables or desired exposed tables to our GitHub project as a new issue.
| Make | Model (Chassis) |
Year | Variant | Notes |
|---|---|---|---|---|
| Subaru | WRX (VB) | 2025 | ||
| Subaru | WRX (VB) | 2024 | Currently in closed beta (2024.2) | |
| Subaru | WRX (VB) | 2022-2023 | ||
| Subaru | WRX (VA) | 2015-2021 | ||
| Subaru | WRX STi (VA) | 2015-2021 | ||
| Subaru |
BRZ (ZD8) |
2021+ | ||
| Toyota | GR86 (ZN8) | 2021+ | ||
| Toyota | NXP-based | 2022+ | ||
| Honda | NXP-based | 2022+ |
Issues/Troubleshooting
Atlas is a relatively new software project, and while we strive to provide an easy to use and trouble-free product, errors may still arise. In this event, users are urged to check our currently known issues. If this is a new issue, please open a support ticket on our GitHub or drop by the NAMR Atlas Community on Discord.