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.

Connect to the CAN output of the K-Pro4 or FlashPro. The CAN pins of your unit are in the Hondata documentation, so check them before you cut anything.

The bit rate is a setting in K-Manager or FlashPro Manager (250 kbit/s, 500 kbit/s or 1 Mbit/s). Set it to 500 kbit/s for the OBD and Wire-In interfaces; with an Apex you can match any of the three in the app.

Open K-Manager (K-Pro4) or FlashPro Manager and go to Parameters, Multiplexer / Digital Output.

Set CAN Output to Hondata. This is Hondata's own broadcast on IDs 0x660 to 0x669, the same stream the AiM and ECUMaster dashes read, and DashCAN decodes it as it comes. The "MoTeC" option is the same layout, but pick Hondata so the settings match this guide.

Set the CAN bit rate on the same page to the value your interface uses (500 kbit/s unless you have an Apex set to something else), then upload the calibration 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: Hondata
• CAN Bus baud rate: 500000 (500 kbit/s), unless you set a different CAN-Bus speed in the ECU software

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.