| **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. |
| **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.** |
| [](https://docs.motorsportsresearch.org/uploads/images/gallery/2024-11/OvY1SvSPwuUofrWl-screenshot-2024-11-07-at-2-43-41-pm.png) | [](https://docs.motorsportsresearch.org/uploads/images/gallery/2024-11/sK1dsTJLM518lDUK-screenshot-2024-11-07-at-2-45-08-pm.png) |
**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: 1. 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). 2. Your laptop/computer/etc. has **ample battery capacity** as well to avoid shutdown for at **least 30 minutes**. 3. The vehicle is **parked,** stationary in a **safe location** such that anything to go wrong, recovery procedures can be run without interruption. 4. 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. 5. 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](https://docs.motorsportsresearch.org/books/atlas-documentation/page/supported-adapters "Supported Adapters") for full details. ##### Tactrix OpenPort 2.0 "Connection failed" Error [](https://docs.motorsportsresearch.org/uploads/images/gallery/2024-11/mgniBpOIo9UmzmeE-image.png) 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. #### ProcedureAtlas 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, [](https://docs.motorsportsresearch.org/uploads/images/gallery/2024-11/6rOwQ0m1mblIR0re-image.png) After a brief period, you will be greeted with this prompt, [](https://docs.motorsportsresearch.org/uploads/images/gallery/2024-11/3JDwtqdyixN0eZuJ-image.png) 1. Make sure the **Calibration** listed is the one you want to flash 2. Make sure the **Vehicle** listed is the one you want to flash 3. 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.** [](https://docs.motorsportsresearch.org/uploads/images/gallery/2024-11/F2uPLqUpH3JeE7HA-image.png) 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: [](https://docs.motorsportsresearch.org/uploads/images/gallery/2024-11/NibElgW5jA0J4oXG-image.png) Turn off the vehicle's ignition in order to completely shut down the vehicle. Click **OK.** [](https://docs.motorsportsresearch.org/uploads/images/gallery/2024-11/FGn9Z0WD6OvXS7O6-image.png) 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](https://docs.motorsportsresearch.org/books/atlas-documentation/page/flash-recovery). ##### 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](https://docs.motorsportsresearch.org/books/atlas-documentation/page/flash-recovery), 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.
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. #### ProcedureMake 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**. [](https://docs.motorsportsresearch.org/uploads/images/gallery/2024-11/RqGRjVwL9u4MDd0f-image.png) You will be asked what vehicle is being recovered; select it from the list and click **OK**, [](https://docs.motorsportsresearch.org/uploads/images/gallery/2024-11/mCY6p2RYTNT9Gha9-image.png) 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, [](https://docs.motorsportsresearch.org/uploads/images/gallery/2024-11/6rOwQ0m1mblIR0re-image.png) 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, [](https://docs.motorsportsresearch.org/uploads/images/gallery/2024-11/3JDwtqdyixN0eZuJ-image.png) 1. Make sure the **Calibration** listed is the one you want to flash 2. Make sure the **Vehicle** listed is the one you want to flash 3. 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.** [](https://docs.motorsportsresearch.org/uploads/images/gallery/2024-11/F2uPLqUpH3JeE7HA-image.png) 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: [](https://docs.motorsportsresearch.org/uploads/images/gallery/2024-11/NibElgW5jA0J4oXG-image.png) Turn off the vehicle's ignition in order to completely shut down the vehicle. Click **OK.** [](https://docs.motorsportsresearch.org/uploads/images/gallery/2024-11/FGn9Z0WD6OvXS7O6-image.png) 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: 1. 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). 2. Your laptop/computer/etc. has **ample battery capacity** as well to avoid shutdown for at **least 30 minutes**. 3. The vehicle is **parked,** stationary in a **safe location** such that anything to go wrong, recovery procedures can be run without interruption. 4. 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. 5. 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](https://docs.motorsportsresearch.org/books/atlas-documentation/page/supported-adapters "Supported Adapters") for full details. ##### Tactrix OpenPort 2.0 "Connection failed" Error [](https://docs.motorsportsresearch.org/uploads/images/gallery/2024-11/mgniBpOIo9UmzmeE-image.png) 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 EEPROMMake 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**: [](https://docs.motorsportsresearch.org/uploads/images/gallery/2024-11/rUqjtFqpcWEXovQ5-image.png) You will be asked which section is being downloaded. Select **EEPROM,** and click **OK**: [](https://docs.motorsportsresearch.org/uploads/images/gallery/2024-11/ntCi9dWG5ymtlpbV-image.png) The EEPROM will be downloaded from the ECU, please wait for this to finish. [](https://docs.motorsportsresearch.org/uploads/images/gallery/2024-11/gzgu2909PfFHrTBK-image.png) When the process has completed, save the downloaded binary data to a file on your computer: [](https://docs.motorsportsresearch.org/uploads/images/gallery/2024-11/ltXSasu33FWmHBix-image.png) #### Step 2: Uploading EEPROMMake 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**: [](https://docs.motorsportsresearch.org/uploads/images/gallery/2024-11/UMZkJSjuoAKiHyOs-image.png) Select an EEPROM binary file that was previously downloaded from another ECU: [](https://docs.motorsportsresearch.org/uploads/images/gallery/2024-11/fY4VqSwE1uNXE80t-image.png) You will be asked which section is being uploaded. Select **EEPROM,** and click **OK**: [](https://docs.motorsportsresearch.org/uploads/images/gallery/2024-11/UEL8xS8m2iey6GNQ-image.png) The EEPROM will be uploaded to the ECU. Wait for the process to finish: [](https://docs.motorsportsresearch.org/uploads/images/gallery/2024-11/fFMyTPvCESR3O4vu-image.png) Once the process completes, you will be greeted with the **Upload Complete** screen: [](https://docs.motorsportsresearch.org/uploads/images/gallery/2024-11/h63prcZw6prLb28N-image.png) 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](https://docs.motorsportsresearch.org/books/atlas-documentation/page/flashing-a-calibration) | **Recovery Support** See**:** [Flash Recovery](https://docs.motorsportsresearch.org/books/atlas-documentation/page/flash-recovery) | **"Brick" Recovery Support** See**:** [Flash Recovery](https://docs.motorsportsresearch.org/books/atlas-documentation/page/flash-recovery) |
| 2015 USDM Subaru WRX MT | Atlas 2025.1 or later | Atlas 2025.1 or later | Atlas 2025.1 or later |
| 2016 USDM Subaru WRX MT | Atlas 2025.1 or later | Atlas 2025.1 or later | Atlas 2025.1 or later |
| 2017 USDM Subaru WRX MT | Atlas 2025.1 or later | Atlas 2025.1 or later | Atlas 2025.1 or later |
| 2018 USDM Subaru WRX MT | Atlas 2025.1 or later | Atlas 2025.1 or later | Atlas 2025.1 or later |
| 2019 USDM Subaru WRX MT | Atlas 2025.1 or later | Atlas 2025.1 or later | Atlas 2025.1 or later |
| 2020 USDM Subaru WRX MT | Atlas 2025.1 or later | Atlas 2025.1 or later | Atlas 2025.1 or later |
| 2021 USDM Subaru WRX MT | Atlas 2025.1 or later | Atlas 2025.1 or later | Atlas 2025.1 or later |
| 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 |
To flash a calibration to your vehicle after importing it, see [Flashing a Calibration](https://docs.motorsportsresearch.org/books/atlas-documentation/page/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. [](https://docs.motorsportsresearch.org/uploads/images/gallery/2024-12/qkTUlSlcTUnGNOvr-image.png) #### **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. [](https://docs.motorsportsresearch.org/uploads/images/gallery/2024-12/uHpyw0Ug65vubBTi-image.png) # Datalogging # Atlas Datalogging Basics #### Introduction Tuning your car, ultimately, is a scientific endeavor. Without accurate data, you have little if anything to inform your decisions (inputs) to your tune as you reform it to meet your goals. **Data-logging** is an important method to receive feedback from the ECM (engine control module) for your engine's current condition and performance as it relates to your calibration (tune) on the vehicle. Typically, a **datalog** is the recording of a series of values (or *parameters*) that are read (or *polled*) from the vehicle at a specific interval, or *polling rate*. Parameters included in a data log might be, for example, the engine speed (RPM), rate of mass air entering the intake tract (mass airflow, or MAF), ignition advance (or ignition timing), the air-fuel target ratio (or commanded AFR), coolant temperature, camshaft phase/timing, and so on. Each of these *parameters* are requested at once by your tuning software, such as Atlas, at a certain frequency schedule typically measured in polls-per-second or hertz (Hz). The higher the polling rate, the higher the precision is in the time domain for logged values. The ECM records these values to Atlas by first briefly pausing the execution of the ECM logic, reading every value requested, and assembling all requested parameters in a single **frame** that is transmitted back to Atlas over the vehicle's communication system (typically the CAN bus). Atlas then records the date and time that the individual frame was received and adds it to the list of frames, which together form the recording. The same system that is used to display gauges in Atlas is used for data-logging. The difference is these received (polled) frames are recorded for later viewing, as opposed to gauges which only use any given frame to update the gauge's corresponding parameter value and throw away the received data after it has been displayed on screen. #### Atlas Gauges The Atlas workflow separates parameters (things we define for you) as objects you can parameterize and log, called **gauges**. In Atlas, gauges -- though each based their own parameters -- are what are used for recording, not parameters themselves. You can customize gauges to your preference, including their theme, style, alarms (i.e. flashing), and scaling limits. To further help you organize your workspace, your customized gauges are grouped into something called a **gauge set**, or a collection of your gauges. To access your gauge sets, look to the right of Atlas. If the panel is closed, you will notice a vertical strip of tabs, one of which is called **Gauges**. Click this to open your gauges and gauge sets.| [](https://docs.motorsportsresearch.org/uploads/images/gallery/2025-02/0GVHiuTrYl5GtALC-screenshot-2025-02-27-at-3-49-39-pm.png) | [](https://docs.motorsportsresearch.org/uploads/images/gallery/2025-02/RscRGxBPS2wG4mtl-screenshot-2025-02-27-at-3-48-02-pm.png) |
| [](https://docs.motorsportsresearch.org/uploads/images/gallery/2025-02/jVEV1IIbICgdhr1f-screenshot-2025-02-27-at-3-51-19-pm.png) |
|
To open the Data Logging window, press **Control + D** (**Cmd+D** on MacOS) or click the  button in the Atlas toolbar.
The Atlas Datalogger makes recording and viewing datalogs easy. At a high level, these are the headline features of the Atlas data logging ecosystem and why we think you should use it: - Snappy, hardware-accelerated, optimized data and graphics pipeline based on OpenGL capable of easily presenting and navigating logs in excess of 30 minutes in length at any polling rates. You can load up our data-logger with well over 100,000 data-points on commodity hardware with next-to-zero screen lag on battery power. - Community-friendly unencrypted Atlas Datalog Format (\*.ADL file) that flexibly allows you to share your compressed logs for opinion and review with our community members. - Track grouping and splitting that saves your grouping preferences for future logs. - Easily export CSVs that can be imported into websites like [https://datazap.me/](https://datazap.me/). - End-to-end 64bit nanosecond resolution from the recording, to the saved format (.ADL), to the rendered view. - 32-bit floating point resolution for all parameters. - Automatic unit conversion to your Atlas preferences (see File -> Atlas Settings). - Live viewing while recording is on-going. - Tailored interpolation style for the time axis based on the individual precision of each logged parameter. - Automatic Y axis scaling and grouping for all parameters in a track. Parameters in a track with equivalent units will automatically be scaled relative to each-other, while other units will not. - Strong emphasis on a dark theme and designed to reduce judder and flashing to make it easier on your eyes when you're tuning late at night. - Design & create your own analytical/mathematical formulas to mix any data-logged parameters together, and add them post-recording as their own tracks with full support for all actions across the data logger. - Quickly generate beautiful 3D scatter plots and histograms from any logged data for deeper analysis. #### Main Layout [](https://docs.motorsportsresearch.org/uploads/images/gallery/2025-02/IIRqqMSTDFXi3mYu-screenshot-2025-02-27-at-3-13-41-pm.png)| **Area** | **Description** |
| **Menu** | Access actions in the Data Logging window, such as loading and saving datalogs, exporting CSVs, changing the view of the displayed log, and generate tables and charts. |
| **Toolbar** | Offers quick actions such as recording a new datalog and navigating around the current log. |
| **Time** | Shows the currently shown timespan, in seconds, for the visible portion of the current log, and also a time delta if a marker has been placed. |
| **Tabs** | Allows you to open multiple logs at once and quickly switch between them. Each log occupies its own tab. |
| **Tracks** | A datalog is comprised of parameters in tracks. Tracks are stacked vertically on top of eachother in the datalogger, and by default are sorted alphabetically. These tracks may optionally be grouped together by control + clicking them and right-clicking them to group them. |
| **Hovered** | As the cursor is moved (or "scrubbed") across the log horizontally, a marker is shown that interpolates the value at the hovered location for all tracks. |
| **Clicked** | When an interesting point in the log is identified, click once with your mouse to place down a *marker.* Markers are useful to keep yourself aligned in the datalogger. |
| **Legend** | A legend is shown in each track to indicate which parameters are shown in the track. Each label's vertical position corresponds to the vertical positioning of all values shown next to each marker as you scrub your mouse or place a marker to make it an easy way to reference which value is which in a grouped track. |
| **Ticker** | A ticker is shown at the bottom of the log to help keep you oriented and referenced to the timing of events in your log. All logs start at 0 (zero) seconds and extend for the duration of the recording to the right. |
| **Naming** | **Description** | **Example** |
| *Table* or *Base Table* | The value immediately after performing table lookup and any associated blending has been applied. For example, in the case of Subarus, this would be the result of all associated TGV and AVCS blending has been calculated on a given 4- or 5-dimensional map. | Ignition - Primary - Base Table |
| *Base* *Base Final* *Final* | For different stages of a pipeline, *Base* and its corresponding *Base Final* may be used to distinguish distinct book-ends of a pipeline operation. For example, when combining ignition timing, there may be a "Combine Base" and a corresponding "Combine Final". It is also possible for parameters to be named simply as "Base" and "Base Final" Generally, these values are intended to capture a value **before** (Base) and **after** (Base Final) the ECU performs any of the following calculations: - Switching between two or more inputs corresponding to different possible scenarios (i.e. throttle behaviors such as aggressive start, tip-in, or deceleration) - Compensation (either summing, subtracting, or scaling) due to conditions such as atmospheric effects or driver inputs. - Blocking of certain values based on conditions (i.e. knocking or driver inputs) - Mixing of different values (i.e. averaging or weighing), but not to include blending of higher-dimensional maps such as those using AVCS and TGVs as higher-dimensional axes. | Idle - Target Airflow - Base - Base Idle - Target Airflow - Base - Base Final |
| *Corrected* | For referential data in the ECU, and especially for the Mass Airflow (MAF) sensor, *Corrected* is used to name the corrected value of some base parameter, and is generally used by the ECU instead of a corresponding base parameter for its own calculations. | Airflow - MAF - Mass Airflow Corrected (g/sec, uint) |
| *Primary* *Secondary Alternate A, B, C,* etc. | These are placeholder names that names a parameter whose behaviors and relevance have been yet-uncharacterized. | |
| *Target* | *Target* is used to name a parameter that the ECU will reference through some other proportional/integral control system; this is also knows as the **set-point** in closed loop control systems. Targets are not commanded to the hardware electrically. A target might be, for example, the target **airflow** used to determine the commanded throttle position. Note that in this example, the target isn't commanded to the hardware, but the throttle position references the target and is commanded instead. Another example would be **boost**. Boost pressure cannot be commanded; instead, the waste-gate position is 'Commanded' by using the boost target and target torque as a wastegate position table that is then adjusted through its own closed (or open) loop control system, referencing the 'Main Boost Target' table as the set point. Targets may themselves be split into their own *Target* *Base* and *Target Final* sub-parameters. In these cases, *Target Final* will be the target that is referenced by the ECU for closed loop control, while *Target Base* is left in the definitions for diagnostic purposes and will likely be marked as **advanced**. | Idle - Target Airflow - Target Base (g/sec, ushort) Idle - Target Airflow - Target Final (g/sec, ushort) Fuel - Targets - Closed Loop - Target Final (λ, ushort) |
| *Commanded Final* | For parameters that involve digital to analog conversion (DAC), such as ignition timing and fuel pulse width, *Commanded Final* references the last available value before the ECU physically commands the associated hardware elements to take action. No other modifications or alterations of the value takes place in the pipe-line after this point. In the case of ignition timing, this would be the amount of time referenced to determine a timer delay for ignition spark from the MCU. For direct injection fuel platforms, this would be the pulse width of the signal sent to the injectors through any associated amplification hardware present on the ECU. | Fuel - Pulse - Commanded Final Ignition - Commanded Final Airflow - Turbo - Wastegate - Position Commanded Final |
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**. [](https://docs.motorsportsresearch.org/uploads/images/gallery/2025-01/b8C5UtWCL05Q9CFr-image.png) The Tactrix drivers must be uninstalled in order to proceed.
#### Driver Removal Steps 1. Right click on **Tactrix Openport 2.0 J2534 Vehicle Interface** 2. Select **Properties** 3. Click the **Driver** tab in the Properties window 4. Select **Uninstall Device** 5. 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](https://www.tactrix.com/index.php?page=shop.product_details&flypage=flypage.tpl&product_id=17&category_id=6&option=com_virtuemart&Itemid=53&redirected=1&Itemid=53) |    | Wired (USB-Mini B) | OpenPort | [](https://docs.motorsportsresearch.org/uploads/images/gallery/2025-01/jGEqrptnLbZgcPnx-image.png) 120Hz | [](https://docs.motorsportsresearch.org/uploads/images/gallery/2025-01/C0voro3BJVNjvvW1-image.png) 1~5 minutes |
| [OBDLink MX+](https://www.obdlink.com/products/obdlink-mxp/) |    | Wireless (Bluetooth 3.0) | STN | [](https://docs.motorsportsresearch.org/uploads/images/gallery/2025-01/UjmrqmyMWszFwlZu-image.png) 30Hz | [](https://docs.motorsportsresearch.org/uploads/images/gallery/2025-01/abdEoo0QDcEL0tSY-image.png) 15~30 minutes |
| [OBDLink EX](https://www.obdlink.com/products/obdlink-ex/) |    | Wired (USB-A) | STN | [](https://docs.motorsportsresearch.org/uploads/images/gallery/2025-01/fP10WL4rWsZxzB3H-image.png) 60Hz | [](https://docs.motorsportsresearch.org/uploads/images/gallery/2025-01/C0voro3BJVNjvvW1-image.png) 5~20 minutes |
| [Veepeak OBDCheck BLE+](https://www.amazon.com/dp/B076XVQMVS) |    | Wireless (Bluetooth LE) | ELM327 | [](https://docs.motorsportsresearch.org/uploads/images/gallery/2025-01/UBjwPYZU87bMl9Vr-image.png) 20Hz | [](https://docs.motorsportsresearch.org/uploads/images/gallery/2025-01/5tAP2uHHMfYwFrx6-image.png) 30~60 minutes |
| 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+ |   |