Utilisateur

Hello, 

I recently upgraded my compustar CM7000 + Evo-All setup for an EVO-ONE since the take over only works with an Evo-One. Old wiring was 100 stripped and redone according to the Evo-One guide. Everything seems to work fine except for one thing : the take-over procedure. At first, as soon as the driver door was opened, the engine would shut off. I was advised that the take-over only works on the 4.11 firmware. After downgrading to the 4.11 firmware and re-programming the module (and re-decrypting with decryptor), the engine keeps running when the driver side door is open (which is a good thing), but when pressing on the brake pedal, the engine shuts down almost every time. Only twice in about 20 remote starts did it not shut down and the take over succeded I followed the take over procedure that is described in the guide (at the end of the guide), but it fails almost every time. Here is step by step what I do :   

1. Stay 10 feet away from the car and lock it   

2. Send the remote start command. (Which always succeeds)   

3. Walk toward the car, unlock it with the OEM remote (also tried remote starter remote and button on door handle), enter the car (with the OEM keyfob/remote on me) and close the door and make sure to never touch the brake pedal while doing so.   

4. Press on the PTS button once. (At this point, the headunit (radio) powers on, the steering wheel lock disengages, etc)   

5. I press on the brake pedal and as soon as I do so, the engine shuts down.   

    

Only as soon as the brake pedal is pressed does the engine die. I made sure all options in the module reflecting this behavior were disabled. I also tried pushing the PTS button more than once, but to no avail. All subsequent presses on the button do nothing at all. What am I missing? I am hoping to make this work as the take over is the only reason why I purchased the Evo-One. Any help is most welcome! All the wiring was checked twice with a multimeter and it is wired as expected.  

    

Thank you

 Hello,

After installing an Evo-All module alongside the Compustar CM7000 (FT-7000AS-CONT) via Data-Link. The remote start procedure does not seem to function properly. However everything else works like it should (door/trunk locking/unlocking, OEM remote monitoring, etc.). I have re-checked 100% of the connections and I am pretty sure that everything is wired correctly. This being said, I am still facing a couple of issues :

1. CAR NEVER STARTS ON FIRST ATTEMPT (DOESN'T EVEN CRANK)
Wether I have a remote in the car or not (in order to bypass my non-functionning DCryptor bypass - see videos below), the car never starts on the first attempt. It doesn't even crank. I have donet the tach-learning procedure before every test and have tried datalink and wire-to-wire (only for the tach wire). The remote starter confirms it learned the tach (one siren chirp). However, in all cases the issue remains. If I unplug the remote starter's main harness (to cut power to the remote starter) to reset the tach and launch the remote start sequence, the car will crank but won't start. After the tach is learned correctly, the car won't crank on the first attempt, but at least it will start correctly on the second attempt. I tried the 76.28 and 76.29 firmware versions.

2. DCRYPTOR BYPASS NOT FUNCTIONING AS IT SHOULD
I completed the DCryptor process but am still facing issues with the module not starting the car. When I have a remote with me in the car, the remote starter will start the car on the second attempt (for some unknown reason... - see #1). However, when I leave the remote away from the car, the car doesn't start. It cranks for not even half a second and chokes (for the 2nd and 3rd attempt - on the 1st attempt nothing happens).

See video here (with remote in car) : https://youtu.be/Ay_T8PGaT0o
See video here (without remote in car) : https://youtu.be/0MWcJJd_FPo

3. ENGINE STOPS RUNNING WHEN DOOR OPENS EVENTHOUGH THE SETTING IS NOT ENABLED IN THE FLASHLINK MANAGER.
When starting the car, if I open a door, the remote starter shuts off the engine eventhough the setting is not enabled in the module's settings. What could this be due to?

4. OEM REMOTE NOT WORKING WHILE CAR STARTED
One the car is remote started, the OEM remote becomes completely unresponsive eventhough the "C1 - OEM Remote Monitoring" option is enabled (see 1st video above).

5. NO TAKEOVER ON CIVIC 2016-2018 WITH EVO-ALL?
When starting the car, I have a 15 minutes countdown on my remote. If I start driving the car within these 15 minutes and arrive to destination within the 15 minutes, there is no way for me to stop the engine from running by pressing the PTS button, it only shuts off the infotainement unit. Only after 15 minutes will the engine shut off if I press on the PTS button. My only way to turn off the car is from the remote starter's remote... From my understanding there is no takeover procedure for the 2016-2018 PTS Honda Civic with the Evo-All. Is that correct? Would my only option be to shut off the remote started engine (whether by opening the door or pressing on the brake pedal) and starting the engine again via the PTS button before starting to drive?

Any idea on what may be causing this unexpected behavior?

Thank you vey much for your support!

Hello,

After installing an Evo-All module alongside the Compustar CM7000 (FT-7000AS-CONT) via Data-Link. The remote start procedure does not seem to function properly. However everything else works like it should (door/trunk locking/unlocking, OEM remote monitoring, etc.). I have 2 issues so far :
 

1. DCRYPTOR BYPASS NOT WORKING
After following the DCryptor procedure, the car still doesn't start. The Fortin module's LEDs come on and there is a message on the car's cluster screen saying "To start, hold remote near start button" but the car never even cranks in an attempt to start the car. I have completed the DCryptor process and followed the tach learning procedure more than once and have done it right before posting this question. The remote starter confirms it learned the tach (one siren chirp). I am running out of ideas as of why this is still not working.

See video here : https://youtu.be/_8UwYm0bJns

2. CAR ONLY STARTS ON THIRD ATTEMP (WITH KEYFOB IN THE CAR CABIN SINCE DCRYPTOR BYPASS IS NOT WORKING)
Since the DCryptor process doesn't seem to have successfully replicated the presence of the keyfob in order to start the car, I tried initiating the remote start sequence with the keyfob laying on the passenger seat in the car. When doing this, I don't get the "To start, hold remote near start button" message that I am getting when trying to start the car kithout the keyfob in reach. However, the lights come on on the infotainment unit and on the instrument cluster. With the EVO-ALL in sight (I can see the LEDs) and hearing the ignition relay clicking when sending the ignition voltage through, I can tell it's trying to start the car but it never cranks. Only on the third attempt does it successfully start the car (about 40-45 seconds after initiating the remote start sequence).

See video here : https://youtu.be/X-e0DKywDHo

Any idea on what may be causing this unexpected behavior?

Thank you vey much for your support!