Atlas Documentation
This book organizes software documentation for Atlas, covering features and tools inside the program.
Table Editor
Using the Table Editor
Table Editor
The Table Editor is a critical view in Atlas. Using the Table Editor, you can change calibration lookup tables and modify ECU behaviors resulting from their computed values. Most, if not all, recalibration done on your ECU will happen from within the Table Editor, so it is crucial to understand its capabilities and how to navigate around it.
Menu Bar
The Live Editing Status Area on the right-hand side of the Menu Bar shows you the current state of live editing in the Table Editor. If a red "LIVE" box appears, then any changes you make in the Table Editor will be immediately reflected on the ECU, so be careful when making changes. Sometimes, you might see a yellow "Resync" label. Click this label to redownload the ECU's table copy so you can return to a LIVE session, but beware: any local changes will be lost.
For more information and diagnostics on Live Editing, see the documentation page:
Toolbar
The Toolbar has a series of quick actions that you can perform such as exporting the table data, and performing mathematical operations on selected cells, such as adding values or averaging them.
The Calibration Area on the right-hand side of the Toolbar allows you to quickly change the Table Editor between different calibrations in your project. Most of the time, you only want to edit Global Calibration, which has its own dropdown in the Atlas Toolbar outside the Table Editor in the main Atlas window. However, you can change each Table Editor independently as you work.
Keep in mind that when the Global Calibration changes, any Table Editors that are currently selected to that calibration will also update to the newly selected Global Calibration. Any Table Editors that have selected a different calibration than the Global Calibration will not track the Atlas Global Calibration as it changes, unless the Global Calibration being changed from agrees with the Table Editor's calibration.
Table Area
X Axis / Y Axis
The axes for the table are listed alongside the table contents and scroll with the table cell data as you pan/scroll through it. Right-click on an axis's header to edit its contents. Be very careful! Atlas will allow you to edit any Axis, even if it might be dangerous. Editing axes can cause unintended behavior in the ECU; we recommend double-checking with our community (i.e. Discord) before editing axis data in your ECU, unless you know what you're doing.
Table Cells
The Table Cells for the table is the large area in the center of the Table Editor. In this area, you can perform several actions and modify table cell data unless the currently selected calibration is marked as read-only.
When Table Cells change, they will flash a certain color depending on what has been updated. Cells flash yellow when they have updated the calibration (or "ROM") only, as in the case with offline work, but flash green when the data has also been updated on the online ECU in a live session.
Action | Keystroke(s) | Description |
Enter Cell Data | Type any number | Enter cell data by first selecting cells you want to edit, then type a number and press Enter/Return to have the entire selection update to the entered value. |
Undo | Ctrl+Z (Cmd+Z) | Undo the last edit. |
Redo |
Ctrl+Y (Cmd+Y) | Redo the last undone edit. |
Add |
Shift+(+) | Type the "+" character (Shift and the "+" key together) to start adding a value to the current selection. Tip: use a negative number to quickly subtract a value. |
Multiply | Shift+8 | Type the "*" character (Shift and the "8" key together) to start multiplying the current selection by a coefficient. |
Divide | / | Type the "/" character to start dividing the current selection by a coefficient. |
Interpolate | i |
Type the "i" key to immediately interpolate the current complex selection. Interpolation behaves differently than other actions. Selected cells will be treated as anchors and will be unchanged, but any cells in between the anchors will be interpolated according to the Table Editor's current interpolation algorithm. |
Selection in the Table Editor can either be Simple or Complex. The following table breaks down these two selection modes:
Simple Selection | Complex Selection |
Click and drag to make a simple selection. Use Ctrl/Cmd + A together to quickly select the entire table. |
Start with a simple selection (or one cell), and hold Ctrl/Cmd while clicking other areas of the table to produce a complex selection. Complex selections are a key feature with Interpolation. |
Interpolation
Interpolation in the Table Editor
Interpolation is a feature in Atlas that allows you to effectively smooth table cell data. Using interpolation, you can create gradients that prevent the ECU from suddenly "jumping" in values, helping to avoid detonation and create a smoother driver experience across a map.
Interpolation relies on Complex Selections for more advanced calibration editing. Due to the internal algorithm being based on complex selections, Interpolation enables you to quickly design a map in fewer interactions with the editor and speeds up your workflow.
Basics
Horizontal/Vertical Smoothing
Take the following table as an example, it is an ignition timing table will all values set to 0:
Let's begin by selecting an area of the table and setting the values to 5 degrees:
Holding down the Ctrl/Cmd key on our keyboard, we will click on another cell, such as 2.34g/rev x 2000RPM:
A Complex Selection has now been started. As you can see, a duplicate-sized column has now been selected in the area we clicked. Now, press the "i" key on the keyboard to immediately interpolate the empty space between the two highlighted columns:
As we can see, the table has been interpolated in the empty space, smoothing from 5.00 degrees to 0.00 degrees. The highlighted columns did not change, as they are treated as anchors in the interpolation algorithm.
Corner-Based Interpolation
A typical use-case for interpolation is interpolating corners of a table. In this example, we'll interpolate 4 corners and create a blended map between them.
Selecting the 4 corners desired for interpolation by holding the Ctrl/Cmd key and clicking on each anchor of the area to interpolate, press the "i" key to immediately interpolate the area of the box using the anchors as waypoints for the operation:
Advanced
Smoothing with a Waypoint
By selecting multiple columns (or rows), we can create a way-pointed interpolation. The values under the 0.94 g/rev column will be unchanged, and will instead be used to interpolate the values to the left and right as they approach the other anchors at 0.63 g/rev and 2.03 g/rev.
Multiple Waypoints
In a very common scenario, you may want to create a map from a series of waypoints as shown. In this example, we select each cell using the Cmd/Ctrl key and use the "i" key to quickly interpolate between each of the waypoints.
Reverting to Another Calibration
If you would like to revert your changes in the current calibration to another calibration, you can always Apply a different calibration by clicking Edit -> Apply different calibration...
The default selection in the Select Calibration dialog box will always be the Base Calibration you set for the current calibration, if applicable, for faster reverting:
The calibration will be updated. Note that only selected cells will be changed. In this case, Ctrl/Cmd+A was used to select the entire table before the operation took place:
Flashing
Flashing a Calibration
Introduction
2023+ WRX MT Users
If you are using Atlas 2024.4 or earlier, recovery is not possible on these ECUs. Atlas 2025.1 and later resolves this issue upon first programming with the ECU.
In order for a calibration (tune) to be recognized completely by a vehicle, you need to transfer and permanently store it in the vehicle's flash memory, or ROM. For this to take place, you need to instruct Atlas to perform the "flashing" process with the vehicle. Flashing is an easy process, but it is possible for it to fail if careful steps are not taken. Please ensure the following is true for your scenario:
- The vehicle has ample battery capacity remaining to supply the electrical system in your vehicle for at least 30 minutes (we recommend turning off headlights/auxiliary electrical components) - don't try to flash a vehicle if it hasn't been started and driven for a long period of time (allowing the alternator time to charge the battery again).
- Your laptop/computer/etc. has ample battery capacity as well to avoid shutdown for at least 30 minutes.
- The vehicle is parked, stationary in a safe location such that anything to go wrong, recovery procedures can be run without interruption.
- Ideally, is connected to a high-amperage battery charger supplying the battery itself with current. Flashing will work without a battery charger connected, but we strongly recommend using one whenever possible to avoid flashing interruptions that can cause your ECU to enter recovery mode.
- The connection you can make with the OBDII port is firm and does not risk being accidentally unplugged with your position in the vehicle (i.e. shifting, moving around) and how it relates to any wires running to the OBDII port.
Vehicle Connection
To reflash, Atlas needs to be connected to the target vehicle. Please see our supported adapter page for full details.
Tactrix OpenPort 2.0 "Connection failed" Error
Sometimes, the OpenPort 2.0 can lose sync with the computer running Atlas. Make sure you always first connect the adapter to your computer running Atlas. Then, connect the OBD2 end of the Tactrix to the vehicle's OBD2 port, often located underneath the trim in the steering wheel area. Doing this in the reverse order can sometimes cause the Tactrix to incorrectly synchronize with your computer and Atlas.
Procedure
Atlas does not support reprogramming ECUs that are actively programmed by other 3rd-party, aftermarket tuning products in order to respect and honor their confidentiality agreements with their customers. Please "unmarry" the ECU from the aftermarket solution first, in order to return it to a factory state, before proceeding.
Make sure the vehicle is in its "Accessory Mode" mode, with the engine not running, but the gauges active. You may see a Check Engine light in this mode.
For key ignition vehicles, turn the key to the "ACC" position to enter this mode.
For push-to-start vehicles, push the ignition button twice with no pedal input (Clutch or Brakes) to enter this mode.
First, make sure you have selected your desired calibration to flash by selecting it in the Active Calibration dropdown menu in the upper-right part of Atlas. Then, click the Flash button,
After a brief period, you will be greeted with this prompt,
- Make sure the Calibration listed is the one you want to flash
- Make sure the Vehicle listed is the one you want to flash
- If you are flashing a new tune, we strongly recommend checking Reset Learned Parameters.
There is no turning back or any chance to interrupt the reprogramming once you click Yes. Make sure you are positive before continuing with reprogramming!
We recommend double-checking your sitting position, reducing any risk to an unplug scenario at this time, and laptop battery charge at this time. When you are ready, click Yes.
The flash data will be reprogrammed to the ECU. Typically, for fast flashes, this can take anywhere from 10 seconds to 5 minutes. Depending on your adapter's capabilities and speed, this may take longer. If necessary, Atlas will automatically enter Recovery Mode to recover the ECU with the selected calibration, and the process may start over.
Once the process completes, you will be greeted with the Reprogramming Complete screen:
Turn off the vehicle's ignition in order to completely shut down the vehicle. Click OK.
Atlas will now be waiting for the vehicle to return to its Access mode it was previously in. Allow the vehicle 10 seconds to fully shut down any internal electrical components that may still be in a flashing state, and return the vehicle to Accessory mode.
Atlas will then clear any non-persistent diagnostic trouble codes (DTC) that were accidentally tripped by any vehicle components during the flashing process, and the flashing process is complete!
Fast Flashing
Atlas supports "fast flashing" a vehicle, but only if the target ECU supports this. If the vehicle supports fast flashing, this will automatically take place.
Fast flashing, in most cases, will apply to any programming event with the vehicle, including first programming (sometimes referred to as "marriage").
Recovery Mode
For more details on following through with a recovery process, see our flash recovery procedures page.
Description
Most vehicles have a manner in which you can recover the ECU should the flashing be incomplete. For the Subaru WRX (2015+), for example, your bootloader (never reprogrammed by Atlas) has logic which runs on start that will attempt to see if the flash had been correctly programmed. It does this by looking at the first and last sections of your programmed ROM to see if certain data it expects to be present are in place. As flash data is sent in a ordered fashion, it is unlikely that both sections will ever be correct if the reprogramming is ever interrupted. If these sections are not correct, your ECU will enter recovery mode. In recovery mode, your ECU cannot operate the vehicle, but instead is waiting for a new ROM to be uploaded.
If, for example, power is lost to the ECU while flashing (low battery/etc.), this is the mode you will more than likely end up in. If Atlas fully supports your vehicle and your ECU also has a recovery mode that Atlas can interact with, Atlas will handle interacting with your ECU in this recovery mode.
Bricked ECUs
Please first see our flash recovery procedures page, as Atlas 2025.1 and later ships with a brick protection feature in most supported models. It is exceedingly difficult to truly brick an ECU with Atlas.
Please reach out to NAMR if your ECU is "bricked", or in other words it cannot communicate when recovery mode is expected. We offer a service to attempt recovery on capable ECUs in this more challenging state with specialized tooling at merely the cost of shipping as a courtesy to support our community.
Flash Recovery
Introduction
Description
Most vehicles have a manner in which you can recover the ECU should the flashing be incomplete. For the Subaru WRX (2015+), for example, your bootloader (never reprogrammed by Atlas) has logic which runs on start that will attempt to see if the flash had been correctly programmed. It does this by looking at the first and last sections of your programmed ROM to see if certain data it expects to be present are in place. As flash data is sent in a ordered fashion, it is unlikely that both sections will ever be correct if the reprogramming is ever interrupted. If these sections are not correct, your ECU will enter recovery mode. In recovery mode, your ECU cannot operate the vehicle, but instead is waiting for a new ROM to be uploaded.
If, for example, power is lost to the ECU while flashing (low battery/etc.), this is the mode you will more than likely end up in. If Atlas fully supports your vehicle and your ECU also has a recovery mode that Atlas can interact with, Atlas will handle interacting with your ECU in this recovery mode.
Bricked ECUs
Atlas Recovery Feature
Due to the nature of the Atlas brick protection feature, CAN bus devices on the car will not be able to communicate with the ECU and will likely light up your car's dashboard warning lights like a Christmas tree. This is fine, and should resolve after a complete flash and key cycle.
Supported Models:
- Subaru USDM 2022 WRX MT
- Subaru USDM 2023 WRX MT
Atlas 2025.1 now ships with a brick protection feature. Due to its position within the bootloader, this feature is always accessible, even if the programming was incomplete or the tune contained bad code. Atlas will always try to reprogram the bootloader first, so even if it was your first time flashing the vehicle and it has ended up bricked, there is a good chance the feature is already installed.
To access this feature on an ECU that has been flashed previously by Atlas , first turn off the vehicle. Then, press and hold the Cruise Cancel switch on your steering wheel. Wait approximately 30 seconds. While holding this button, enter accessory mode:
- For key ignition vehicles, turn the key to the "ACC" position to enter this mode.
- For push-to-start vehicles, push the ignition button twice with no pedal input (Clutch or Brakes) to enter this mode.
The Cruise Cancel button can now be released.
This will activate an Atlas recovery feature in your ECU's bootloader, and the ECU will immediately enter recovery mode. At this point, you can follow the procedures in this document. This feature can be activated at any time under any circumstances as long as the vehicle has battery power. To cancel this recovery mode if the ECU is not bricked, simply key cycle the car.
If the above does not work and you have flashed the ECU with Atlas before, it is possible either the bootloader is truly bricked (see Unusual Circumstances).
Unusual Circumstances
Please reach out to NAMR if your ECU is "bricked", or in other words it cannot communicate when recovery mode is expected. We offer a service to attempt recovery on capable ECUs in this more challenging state with specialized tooling at merely the cost of shipping as a courtesy to support our community.
Procedure
Make sure the vehicle is in its "Accessory Mode" mode, with the engine not running, but the gauges active. You may see a Check Engine light in this mode.
For key ignition vehicles, turn the key to the "ACC" position to enter this mode.
For push-to-start vehicles, push the ignition button twice with no pedal input (Clutch or Brakes) to enter this mode.
To enter Recovery Mode in Atlas, use the main menu to click Help -> Enter Recovery Mode.
You will be asked what vehicle is being recovered; select it from the list and click OK,
First, make sure you have selected your desired calibration to flash by selecting it in the Active Calibration dropdown menu in the upper-right part of Atlas. Then, click the Flash button,
You may be asked again which vehicle is being recovered; select the vehicle again from the list and click OK.
After a brief period, you will be greeted with this prompt,
- Make sure the Calibration listed is the one you want to flash
- Make sure the Vehicle listed is the one you want to flash
- If you are flashing a new tune, we strongly recommend checking Reset Learned Parameters.
There is no turning back or any chance to interrupt the reprogramming once you click Yes. Make sure you are positive before continuing with reprogramming!
We recommend double-checking your sitting position, reducing any risk to an unplug scenario at this time, and laptop battery charge at this time. When you are ready, click Yes.
The flash data will be reprogrammed to the ECU. Typically, for fast flashes, this can take anywhere from 10 seconds to 5 minutes. Depending on your adapter's capabilities and speed, this may take longer. If necessary, Atlas will automatically enter Recovery Mode to recover the ECU with the selected calibration, and the process may start over.
Once the process completes, you will be greeted with the Reprogramming Complete screen:
Turn off the vehicle's ignition in order to completely shut down the vehicle. Click OK.
Atlas will now be waiting for the vehicle to return to its Accessory mode it was previously in. Allow the vehicle 10 seconds to fully shut down any internal electrical components that may still be in a flashing state, using the ignition key or push-to-start button, once again return the vehicle to Accessory mode.
Atlas will then clear any non-persistent diagnostic trouble codes (DTC) that were accidentally tripped by any vehicle components during the flashing process, and the flashing process is complete!
Cloning an ECU
Introduction
In order to avoid risking damaging or "bricking" your OEM ECU, you may instead choose to clone your OEM ECU to another, spare ECU that you have purchased. However, you will run into issues with this without cloning the ECU, as the OEM ECU in your vehicle has keys that permit the ECU to authorize with your electrical system. One of these keys is the key used for immobilizer authorization. Without at least these keys in agreement, the vehicle will not start. This documentation page assumes you have an OEM ECU that is correctly trained/paired to the vehicle from factory (or a dealership/service specialist) as a cloning source, and a spare ECU to clone to.
Cloning an ECU involves downloading the region of memory in your ECU that holds these authorization keys. This section is smaller than and separate from your calibration (or tune) and is called EEPROM. You can download an EEPROM file and save it for later, or upload it to another ECU immediately after downloading it from the factory ECU.
Atlas does not support cloning or reprogramming ECUs that are actively programmed by other 3rd-party, aftermarket tuning products in order to respect and honor their confidentiality agreements with their customers. Please reach out to the vendors supplying those products to clone and support those modified ECUs, or "unmarry" the ECU from the aftermarket solution first before proceeding.
Cloning is relatively easy, but please ensure the following is true for your scenario:
- The vehicle has ample battery capacity remaining to supply the electrical system in your vehicle for at least 30 minutes (we recommend turning off headlights/auxiliary electrical components) - don't try to flash a vehicle if it hasn't been started and driven for a long period of time (allowing the alternator time to charge the battery again).
- Your laptop/computer/etc. has ample battery capacity as well to avoid shutdown for at least 30 minutes.
- The vehicle is parked, stationary in a safe location such that anything to go wrong, recovery procedures can be run without interruption.
- Ideally, is connected to a high-amperage battery charger supplying the battery itself with current. Flashing will work without a battery charger connected, but we strongly recommend using one whenever possible to avoid flashing interruptions that can cause your ECU to enter recovery mode.
- The connection you can make with the OBDII port is firm and does not risk being accidentally unplugged with your position in the vehicle (i.e. shifting, moving around) and how it relates to any wires running to the OBDII port.
Vehicle Connection
To reflash, Atlas needs to be connected to the target vehicle. Please see our supported adapter page for full details.
Tactrix OpenPort 2.0 "Connection failed" Error
Sometimes, the OpenPort 2.0 can lose sync with the computer running Atlas. Make sure you always first connect the adapter to your computer running Atlas. Then, connect the OBD2 end of the Tactrix to the vehicle's OBD2 port, often located underneath the trim in the steering wheel area. Doing this in the reverse order can sometimes cause the Tactrix to incorrectly synchronize with your computer and Atlas.
Step 1: Downloading EEPROM
Make sure the vehicle is in its "Accessory Mode" mode, with the engine not running, but the gauges active. You may see a Check Engine light in this mode.
For key ignition vehicles, turn the key to the "ACC" position to enter this mode.
For push-to-start vehicles, push the ignition button twice to enter this mode.
First, ensure the OEM ECU is connected to the vehicle. If it is not, disconnect the battery before replacing and installing the OEM ECU. Reconnect the battery after physically reinstalling and fully reconnecting the ECU.
Then, using the main menu in Atlas, click ECU -> Download Section:
You will be asked which section is being downloaded. Select EEPROM, and click OK:
The EEPROM will be downloaded from the ECU, please wait for this to finish.
When the process has completed, save the downloaded binary data to a file on your computer:
Step 2: Uploading EEPROM
Make sure the vehicle is in its "Accessory Mode" mode, with the engine not running, but the gauges active. You may see a Check Engine light in this mode.
For key ignition vehicles, turn the key to the "ACC" position to enter this mode.
For push-to-start vehicles, push the ignition button twice to enter this mode.
Ensure the spare ECU is connected to the vehicle. Disconnect the battery before replacing and installing the spare ECU. Reconnect the battery after physically reinstalling and reconnecting the spare ECU.
Then, using the main menu in Atlas, click ECU -> Flash Section:
Select an EEPROM binary file that was previously downloaded from another ECU:
You will be asked which section is being uploaded. Select EEPROM, and click OK:
The EEPROM will be uploaded to the ECU. Wait for the process to finish:
Once the process completes, you will be greeted with the Upload Complete screen:
Turn off the vehicle's ignition in order to completely shut down the vehicle. Click OK.
Atlas will now be waiting for the vehicle to return to its Accessory mode it was previously in. Allow the vehicle 10 seconds to fully shut down any internal electrical components that may still be in a flashing state, and return the vehicle to Accessory mode.
Flash Support Table
Atlas Flash Support
USDM WRX Manual Transmission Support
Vehicle Year, Market, and Model |
Flash Support See: Flashing Page |
Recovery Support See: Flash Recovery |
"Brick" Recovery Support See: Flash Recovery |
2015 USDM Subaru WRX MT | Atlas 2025.1 or later | Atlas 2025.1 or later | In Progress |
2016 USDM Subaru WRX MT | Atlas 2025.1 or later | Atlas 2025.1 or later | In Progress |
2017 USDM Subaru WRX MT | Atlas 2025.1 or later | Atlas 2025.1 or later | In Progress |
2018 USDM Subaru WRX MT | Atlas 2025.1 or later | Atlas 2025.1 or later | In Progress |
2019 USDM Subaru WRX MT | Atlas 2025.1 or later | Atlas 2025.1 or later | In Progress |
2020 USDM Subaru WRX MT | Atlas 2025.1 or later | Atlas 2025.1 or later | In Progress |
2021 USDM Subaru WRX MT | Atlas 2025.1 or later | Atlas 2025.1 or later | In Progress |
2022 USDM Subaru WRX MT | Atlas 2024.4 or later | Atlas 2024.4 or later | Atlas 2025.1 or later |
2023 USDM Subaru WRX MT | Atlas 2024.4 or later | Atlas 2025.1 or later | Atlas 2025.1 or later |
2024 USDM Subaru WRX MT | In Progress | In Progress | In Progress |
Calibrations
Sharing Calibrations
Importing a Calibration/Tune
Atlas is Free and Open!
Atlas, as an open tuning platform, encourages sharing calibrations (tunes) within the community. At NAMR, we have a strong stance against Atlas locking tunes. When you import a calibration, you always have the ability to read it and modify it if you choose.
Import a Calibration
To flash a calibration to your vehicle after importing it, see Flashing a Calibration.
To import a calibration, first open Atlas. Then, ensure you have the same project opened that was used to export the calibration. Projects are specific to the vehicle you are tuning, such as the VB WRX or the VA WRX.
Once you have opened a project, use the File -> Import -> Atlas Calibration menu item to select an *.acf file and load the calibration data into Atlas. Once loaded, Atlas will automatically switch the project's active calibration to the imported tune so you can begin flashing and/or working immediately.
Export a Calibration
To export a calibration to share with others, first right-click the calibration in the Calibration tree. Then, using the "Export ROM..." option, save the calibration to a *.acf file and share that file with the recipient.
Datalogging
Project Tree
Support
Detailed adapter and vehicle support information
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 |
3~5 minutes |
|
OBDLink MX+ | Wireless (Bluetooth 3.0) |
STN |
30Hz |
15~30 minutes |
|
OBDLink EX | Wired (USB-A) |
STN |
60Hz |
15~30 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) | 2024+ | ||
Subaru | WRX (VB) | 2022-2023 | ||
Subaru | WRX (VA) | 2015-2021 | Tested on MY2018 Currently in closed beta |
|
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.