Connect the CAN bus wires from the ECU to the OBD connector. To connect them you will need 2 pins which are missing from the OBD connector. The easiest way is to get an OBD connector from a scrap dealer and reuse the legs in it.

In the OBD connector, connect the CANH wire to pin 6 and the CANL wire to pin 14. It is important that this pair of wires has to be a twisted pair, as this will ensure signal integrity, and the total length of the wires should not exceed 1.5 meters. The pins the wires come from on the ECU side are in the ECU section below.

Note: Some cars (e.g. Skoda Octavia RS) may have a CAN bus in the OBD connector, but it is not connected to the engine control unit, so you have to wire it in this case too!

For further help on wiring, please visit the Technical Help page.

The EMU PRO has two CAN buses. CAN1 is fixed at 1 Mbit/s, CAN2 is configurable and defaults to 500 kbit/s. The pins are in the EMU PRO pinout.

Wire the OBD or Wire-In interface to CAN2 at 500 kbit/s. An Apex can sit on either bus, as long as you set the same bit rate in the app.

Connect to the ECU with the EMU PRO software and open the CAN stream settings of the bus DashCAN is wired to (CAN2 for the OBD and Wire-In interfaces).

Enable the EMU stream. The EMU PRO uses the same CAN data structure as the EMU Black, so the frames are the same 0x600 to 0x607 that DashCAN decodes. Leave the base ID at 0x600.

Note the bit rate of that bus (CAN2 defaults to 500 kbit/s), you will set the same in the app. Save the settings to the ECU.

Download the "DashCAN - Ignitron ECU" app to your iOS or Android phone/tablet. You can do this by simply scanning the QR code below, or click the following links.

The store listing still carries the original name, but the app works with every ECU on this page.

After installing the app, launch it and then approve all the permission requests and turn on Bluetooth, otherwise the app will not work properly!

Open the app, go to Settings and then the CAN bus page.

• Protocol: CAN
• ECU: ECU Master EMU PRO
• CAN Bus baud rate: 500000 (500 kbit/s), unless you set a different CAN-Bus speed in the ECU software

Select ECU Master EMU PRO here, not ECU Master EMU. The decoded channels are the same, but the app then expects the bit rate of the EMU PRO bus you wired.

The baud rate has to match the bit rate your ECU broadcasts at. On the DashCAN OBD and Wire-in interfaces it is fixed at 500 kbit/s and the selector stays greyed out, on the DashCAN Apex you can pick it.

120 Ohm termination: leave it off when you tap into a bus that already works (a factory bus, a Haltech CAN hub, a Syvecs plug and play kit). Turn it on only when DashCAN and the ECU are the only two devices on the bus and nothing else terminates it. The switch needs hardware version 1.07 or newer.

If everything is done correctly the app connects to the DashCAN interface automatically. Start the engine and watch the RPM gauge: as soon as it follows the engine, the CAN side is working and you are ready to log.

If every gauge stays at zero, work through this list:

1. Bit rate. The CAN Bus baud rate in the app has to match the speed your ECU broadcasts at. This is the most common cause.
2. ECU choice. The ECU selected in Settings decides how the frames are decoded. Two ECUs can use the same message IDs with completely different content.
3. CAN High and CAN Low swapped. Swap the two wires and try again.
4. Broadcast not enabled. Go back to the ECU Configuration step and confirm the setting was saved to the ECU, not just changed on screen.
5. Termination. Try the 120 Ohm switch in the other position.

Still nothing? Contact us with your car, your ECU and its firmware version, and which DashCAN product you have.