Frequently Asked Questions

After seeing the same questions asked repeatedly, we figured it was time to keep a record that could answer most (if not all) of the questions they have about Atlas, our upcoming GM port injection controller. You can be assured these answers are truthful and accurate as opposed to what you'll find floating around on the internet.

When will it be available?

We had been targeting a release in September of 2024, but unfortunately this may drift into October 2024 depending on how quickly a couple of aspects can be made production ready (mostly the UI and the deployment of the HP Tuners patch).

How much will it cost?

Currently, we anticipate that retail cost will start at $2000. We will offer both single and dual widebands as an add-on priced at $500 and $1000 respectively. These widebands are the AFX3 made by ECM, and they utilize CAN data to communicate with the controller. They use a custom configuration to our specifications to run them at very fast update rates along with transmitting diagnostic data to monitor the health and validity of the widebands.

I want to get on the list! Can I preorder it?

No, we aren't doing preorders and we are not making a list. This will be first come, first served once we announce the release for sale. Preorders and lists just invite bad attitudes.

How does it work?

We can't quite share the details yet, but we only intercept two physical sensors: the crank sensor and the cam sensor. The only reason we have to intercept these is the update rate of crank position over CAN would be too slow to reliably synchronize the injection events at higher rpm.

So and so already gets info from the CAN network. You aren't doing anything new! Right?...

There is a marked difference between grabbing what's available on the main vehicle CAN bus... and creating your own CAN definitions based on memory variables. Tons of people out there tap into the main CAN bus and grab tons of basics like pedal position, throttle position, ethanol content, wheel speed, etc. We go much further so we can get data nobody else does. We also speed the network up to 160Hz which is twice as fast as the stock CAN networks.

Do I need widebands?

No, you don't need widebands. The system is extremely reliable, and because it is physics based, you aren't going to end up with massive drifts due to operating condition changes like ethanol content or fuel pressure. The controller has built in support for single or dual bank widebands if you want closed loop. In single wideband operation, all eight cylinders are trimmed based off of the wideband feedback. In dual operation, trimming is bank specific. If you opt for widebands, you can log them directly in HP Tuners without a ProLink.

Can I log the controller in HP Tuners?

Yes, the controller is supported in HP Tuners and will show up as a supported device in VCM Scanner. There are a number of parameters you can log. We are working on an in-car expansion device for the OBD2 port that will display data on the dash (we are debating whether we want this to be configurable).

What are you waiting for?!?!

There are a few things that need to happen to bring this product to fruition. It's really easy to just dump a product to market when you repurpose somebody else's architecture, software environment, and hardware. To do something truly right required doing every part of this from scratch.

Patent Application - This is the primary reason we can't talk about how it works in any useful detail. Once the US Patent Office confirms our application, we can begin to decipher just how and why our system is as sophisticated as we have eluded to.

Board Manufacturing - We've been tweaking some bits on the board, and we only do small runs at a time. We're waiting to submit a large production order until we know that a board doesn't need manual modifications after assembly.

GUI Completion - The controller relies on a web page interface to access, update, and edit anything. It will create it's own wifi network, and once you log in, you will do everything through a web page. Development of this couldn't happen until after the core firmware for control was complete. The board has two processors that each fulfill a job; one for the web interface and one for the actual control. Getting the two to communicate in real time as well as allowing one to reflash the other has been time consuming. This is one of those pitfalls of not operating in somebody else's software environment. We also just wanted complete wireless capability.

HPT Patch Deployment - This is another big one. The controller relies on an operating system patch from HP Tuners. We have been tweaking what this patch does, and we are presently waiting for an update after our latest round of data analysis. Once we give the go ahead, they will have to roll this code change out for every operating system and incorporate it into VCM Editor.

Who is involved? What are they doing?

DSX Tuning is responsible for the concept, integration, coordination, and ultimately the sale and support of the controller. We also manufacture the cases and wire harnesses. This was an idea that was first thought of in 2018, but it took a long time to gain the knowledge and confidence to execute the whole thing.

HP Tuners agreed to work with us to provide an option for deploying a code patch that allows us to modify and enhance the CAN structure in the factory ECU so the ECU can talk to the port controller and give it pertinent information in real time. This eliminated the need for tying into sensors, and this gives us access to far more information than what is available on a standard broadcast stream.

There are three others involved in this endeavor. First, we have the hardware provider who designed the board and has been working with the board house for mass production. Next we have a coder for the ESP32 who is responsible for the web interface, reflashing, and some CAN integration. Last is a firmware developer for the STM32 which is handling the actual control algorithm and the hardcore CAN integration.