Sale ends todayGet 30% off any course (excluding packages)
Ends in --- --- ---
I've gotten stuck trying to get my Aim MXL2 dash to read the canbus of a Haltech R3. Physically it's just connecting a blue and white wire so unless there's something I'm missing that should be fine. In Aim software I've tried selecting all 3 of the Haltech can protocols and none worked. I even used a protocal someone on this forum uploaded. In Haltech NSP I have Haltech Can system enabled under Connections and Supported Dash enabled. In the Aim software it never gets data for the ecu stream. At this point I don't know what the next step would be. Any help would be appreciated.
Try swapping CAN +/- its amazing how often these are inadvertently swapped. Or spend time verify continuity from the wires back to the correct device connector pins.
Is there anything else on the CAN bus? If so, is it's baud rate 1Mbit/s to be compatible with the Haltech?
The MXL2 has a built in terminating resistor, the Haltech is switchable. Could there be other terminating resistors installed on the CAN bus? There should only be two for correct operation per the spec.
I think you should be using the "CAN_V2" or "CAN_V2_40" protocols.
Next step -- use a CAN sniffer or oscilloscope to verify the R3 is sending data on the bus that is wired. That has to happen first.
I can't believe the solution was so simple.
Verified the wires, swapped the just for fun (gotta love deutch connectors), tried all the can options again.
I decided to check everything again. Turns out when Haltech NSP software converted basemap from the Elite 2500 to the Nexus R3 it chose CAN2 for the wiring output.