The AEM CD7 dash is one of the many full colour TFT dashes on the market. It has built in support for many aftermarket ECUs and a fully configurable CAN system. This article shows two ways that it can be used.
In both, we will just use the CAN1 connection on the dash. The dash actually has 2 CAN busses, but we will just use the first one in this example.
In terms of physical connection, all the pins we need are found on the 4 pin DTM connector. The colors are as follows:
Note that here, the standard red/black are used for power and ground, and white/green are the CAN pair, unlike the Racepak where they use red/green for power and ground, and white/black for the CAN pair. The best thing about standards is that there are so many to choose from.
Using the Haltech V2 Protocol
The first method is to use the Haltech V2 protocol. The Adaptronic Modular ECUs can emulate the Haltech V2 protocol which allows it to be used with any dash that supports the Haltech, with the exception of the Haltech IQ3 simplicita, but if you want to use that dash, then please read the article or watch the video on how to use the Racepak dashes.
Firstly, the Haltech protocol specifies a bit rate of 1 Mbps, but both the ECU and the dash allow you to choose different bit rates. So to be correct, the ECU should be set to 1 Mbps, and the termination should be set to “on”. If you’re using the secondary CAN port on a Modular ECU that supports a second CAN port, the termination is always on and can’t be disabled.
Secondly, the dash must be configured using the AEM Dash Design software. To do this, load your dash configuration and then go to Setup -> Display.
In the Setup editor, go to CAN Receive.
Select the following settings:
Then select the “Import CAN…” button
Select the Haltech V2 AEMCAN template:
And select “replace” when it asks you if you want to override the new channels.
Send this to the dash using the “Upload to Display” or Ctrl+U and the two devices will now talk to eachother.
The following lists the Haltech channels as implemented in Modular firmware 0.145 and notes for them. Note that the full CAN spec is Haltech’s intellectual property, so if you want a full description of Haltech’s protocol, please do not ask us. This is just to describe individual channels, which ones are available and anything weird or unusual with how it is interpreted by the AEM dash:
Adding Target Lambda:
Next go to the Scalars tab, find AFRTarget_scalar and set it to 0.001 with an offset of zero. The Haltech lambda is divided by 1000, so a value of 1000 means stoichiometry.
Using the Adaptronic Native Protocol
The second method, which is a little bit more work to set up but gives much better control, is to use the Adaptronic native protocol. Rather than try to map all of the Adaptronic variables to the AEM variables, these are just given the same names as in the Adaptronic software.
The way to import them all is to do as follows. First we must clear the existing channels, which will probably be set up for the AEM ECU:
The standard DBC files are available in this article. If you have enabled specific other channels to be output, you can also generate the DBC file from the software.
In the standard DBC filenames, the following terms have the following meanings:
The unit scaling is done in the CAN importation because the dash is not unit-aware. The following suffices are used for different unit combinations:
If you have selected some additional CAN channels to be output in the software, then you can generate a DBC file from the software. When doing this, you must select the output units for scaling for AFR/Lambda, mph / km/h, PSI / kPa and Celcius / Fahrenheit.
Adaptronic Full Imperial AFR
Adaptronic Full Imperial Lambda
Adaptronic Full Metric AFR
Adaptronic Full Metric AFR PSI
Adaptronic Full Metric Lambda
Adaptronic Standard Imperial AFR
Adaptronic Standard Imperial Lambda
Adaptronic Standard Metric AFR
Adaptronic Standard Metric AFR PSI
Adaptronic Standard Metric Lambda
Big thank you to @Aaparkah.300 – Aaron Parker for lending us the dash for testing.