Fortin EVO-ONE w/ T-Harness. Regular (non-intel key)
Summary:
1) I am trying to determine why I only get cranking & starting when the key is in the barrel
2) I suspect I'm not getting or decoding CAN data in the EVO-ONE.
Details:
I have installed the unit and, updated both bypass and remote start firmware via flashlink. I've also set the following options in remote start: 32.3, 2.3, 8.2. My first issue appeared when pairing the RF remote kit (RF442W). I had to manually apply +12V to the black (foot pedal brake) wire after 5 button presses in order to enter the "add remote" option. I thought brake status came over CAN bus.
After issuing a remote start command, the red light on the Fortin comes on, the dash lights up, and hear relays clicking in the engine bay but no cranking. It fails after two attemps and flashes the 4x light code = no tack feedback. Same result with GWR wire grounded.
If I put the key in the ignition barrel and re-attempt the test, this time the vehicle starts, but then shuts down after 3 seconds with the same no tachometer feedback error code. If I change the tachometer setting via flashlink (20.4), the vehicle will stay running. I have tried 20.1, 20.4, 20.5, 20.6
I pulled out my 2CH oscilloscope and probed the CAN pins (6 & 14). There is clearly data on the bus, though the CAN L signal has significantly higher capacitance (signal does not have hard edges like CAN H).
According to the install guide, doors/trunk/brake/tach/etc should be coming into the EVO-ONE via CAN bus. I'm worried that I either have a fortin or vehicle CAN bus problem. For what it's worth, I disconnected the CAN bus wires into the EVO-ONE and got the same result. Additionally, I suspect there is another reason as to why I don't get cranking without the key in the barrel. Any additional steps or guidance appreciated.
