Questions & Answers

2007 civic + compustar cm6200 + evo all = no start/crank/ignition

0 votes
installed a 6200 + blade ads into my girlfriend's 2011 civic without a hitch...fortin is giving me grief.

remote start fob was successfully programmed and will operate door locks;  but no start - no crank....no switched ignition...nothing....   I also noticed that the fob won't update the door lock status if i change door lock position with oem fob - this is something that occurs in my girlfriend's car.

evo all is connected to cm6200 via 4 pin datalink connector and evo all was programmed successfully no problem (got to flashing blue lights with key in run position).  only 1 programming procedure so pretty hard to mix it up with another.

option 4-11 is set to fortin protocol (setting 2) in cm6200....i have verified this with op500

As per connection 4 diagram of evo all install manual i have cm6200 connector CN2 pin 11 (poc5, black) connected to evo all 20 pin connector pin 8 (dark blue) for ground while running and i have verified that POC5 for CN2 pin 11 is set to 0 (GWR) via OP500.

I did come across some apparent situations with other vehicles where evo all 20 pin connector pin 1 yellow was mistakingly connected to vehicle ignition wire (ignition barrel 7 pin connector pin 2 yellow), but can't find any evidence of that when installing evo all in 06-11 civic.

the only thing i can think of is whether or not it's worth trying to loathingly purchase the flashlink updater and switch cm6200 to ads protocol and do the same with the evo all? Other than that i'm at a loss...???
asked Sep 15, 2014 in Honda by brian koven (130 points)

2 Answers

+1 vote

"I did come across some apparent situations with other vehicles where evo all 20 pin connector pin 1 yellow was mistakingly connected to vehicle ignition wire (ignition barrel 7 pin connector pin 2 yellow), but can't find any evidence of that when installing evo all in 06-11 civic."

 

Hum ignition wire is not yellow on a 06-11 civic

ignition blue

acc orange

start yellow

 

answered Oct 9, 2014 by Robert T (85,190 points)
0 votes

Hello Brian,

remote start fob was successfully programmed and will operate door locks;  but no start - no crank....no switched ignition...nothing....   I also noticed that the fob won't update the door lock status if i change door lock position with oem fob - this is something that occurs in my girlfriend's car.

Key bypass or not, IGNITION should be coming on. No ignition means the compu is not sending ignition. Which 99% of the time would mean the unit is in Valet mode. From the top of my head, i am pretty sure those years of Honda, the vehicle will crank but not start the key is not bypassed. The fact you are not getting any ignition or crank I'd be poking at the compu with a multimeter to see where the problem is.

Also... If you installed their Anti-Grind / Starter-Kill relay, make sure the starter wires are not reversed.

 

The LEDs on the EVO are there to help you diagnos.

  • RED LED : unit received ground-while-running
  • YELLOW LED : unit received ignition
  • BLUE LED : anything data

 

Receiving door lock status when using the OEM Remote is something that most likely will not work since OEM Remote Monitoring is not an available feature for the 06-11 Civic. Vehicles compatible with OEM Remote Monitoring can be found here. https://fortin.ca/en/features/oem_remote_monitoring.html  This feature is also something which need to be turned on in the EVO.

 

This feature has only been out about 2 years therefore it is untested on older vehicles. This means, it may work on some vehicles that are not listed. Quick way to know if OEM Remote Monitoring is available for your car would be to look at the BLUE LED on the EVO when doing lock and unlock on the OEM remote. If the LED flashes, then it may be possible to get OEM Remote Monitoring. If the LED does not flash, OEM remote monitoring is not available at all.

 

the only thing i can think of is whether or not it's worth trying to loathingly purchase the flashlink updater and switch cm6200 to ads protocol and do the same with the evo all? Other than that i'm at a loss...???

You can use the Fortin protocol with the CM6200 but make sure you are using the right port on the compustar. Some of their install guides pointed to the wrong data port.  In the case that the Compu really does not want to respond to the Fortin protocol, you will want to try a different protocol such as the AP/OFA protocol (which does require the Flash-Link to enable in the EVO).

 

I did come across some apparent situations with other vehicles where evo all 20 pin connector pin 1 yellow was mistakingly connected to vehicle ignition wire (ignition barrel 7 pin connector pin 2 yellow), but can't find any evidence of that when installing evo all in 06-11 civic.

95% ot the time the Yellow wire of the EVO needs to detect ignition.

answered Sep 15, 2014 by Robert T (297,670 points)
Hi rob Wow...thanks for the quick reply...can't say thanks enough as this unknown is eating away at me...and I want to get this settled before winter comes. Unless I'm missing something it can't be valet mode as it will indicate so on the fob with a "zzzzz" indicator when enabled? I removed the antigrind relay as the car has it built in ( tried it personally). The only led information I receive is the yellow led turns on when I switch the ignition on with the key...otherwise nothing at all at any time. You can use the Fortin protocol with the CM6200 but make sure you are using the right port on the compustar. Some of their install guides pointed to the wrong data port." By this you mean port as in physical jack that the data link cable is plugged into? There are only 2 possible ports of same size and pint. ..one for data link and one for shock sensor. Otherwise I'd like to know more about this possibility. I've ordered an flu 100....should hopefully be here tomorrow. .. if I don't hear back on anything discussed today I'll follow up concerning that when able.
HI Rob,

so finally got around to toying with the install using the flashlink updater.

You were correct - i tried the oem remote update and it did NOT work.

However, what concerns me even more is that I updated the evo all from firmware version 4 something to the 2nd newest beta 73.15 or something like that and i tried having both the evo all and the compustar on fortin protocol and both set to ads protocol and i still get the same result - nothing.  no ignition, no crank, no led activity...nothing???

what the???
...