4 wires need to be connected to set up the device. These are the switched 12V (+), GND (Ground, -), CAN High (CANH) and CAN Low (CANL). Connect the CAN High and CAN Low wires to the CAN bus of your ECU, the exact pins are in the ECU section below.

Important! The CANH and CANL wires should be run as a twisted pair to ensure signal integrity and the total wire length should not exceed 1.5 meters.

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

Connect to CAN 0 of the ECU, the bus the Data Set 3 stream is sent on. This works with the M84 and the hundred series (M400, M600, M800, M880); the pins are in the pinout of your model. The M1 series is not supported yet.

The Data Set 3 stream runs at 1 Mbit/s.

The CAN bit rate is only adjustable on the DashCAN Apex, so this ECU needs an Apex interface.

Open ECU Manager and go to General Setup, Communications, CAN Setup.

Set CAN 0 Data to Data Set 3 and CAN 0 Address to 1520 (0x5F0). This is the standard MoTeC telemetry set that third-party dashes and loggers read.

Send the setup to the ECU. DashCAN reassembles the stream from the consecutive messages on 0x5F0 and checks its CRC, so a message lost on the Bluetooth link never shifts the readings.

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: MoTeC
• CAN Bus baud rate: 1000000 (1 Mbit/s)

Select MoTeC here. The app expects the Data Set 3 stream on 0x5F0 at 1 Mbit/s, so the CAN bit rate in the app has to be 1 Mbit/s as well.

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.