Door lock control from Compustar remote does not work when remote started

Question

It seems my original post was lost.

I have an evo-all configured with a compustar cm7200s + drone. Everything works as expected except the following.

- Doors will not lock/unlock with Compustar remote is the vehicle is remote started / Subaru remote works

- Auto lock on ignition or tach does not work if remote started

I have checked all wires as instructed and they are all correct.

 

Comments

Currently the Lt Blue & White/Red (A20 & D6) are connected to the connector side of the cut door lock data wire and the White/Green (D4) is connected to the other side of the cut wire.

Answer 1

I'll have to open a report for this at the moment. Locking and unlocking should definitly work all the time.

• Does the blue led flash on the EVO when using the compu remote or the oem remote while the car is started?
• While the car is started, if you pulse a ground on either the purple or purple/white anlog inputs of the evo-all, do the door locks function then?

 

First and foremost, master reset evo, update to 79.32, reprogram and try the door locks.

 

Comments

call us directly if you stil have issue with 79.32

---

OK, I finally found a moment to check the items you requested. Replies below.

- 79.32 after reset and reprogram. No change

- The blue led does not flash with either remote when remote started.

- If pulsing the purple or purple/white I can hear the relay in the unit but the locks do not lock/unlock and no blue led.

I rechecked the door lock connections and they match as noted above. I checked with compustar regarding the port used for the evo-all and they want the evo-all on the gray port with option 4-11 set to option 2. The drone is connected to the black port. All is configured as it should be.

They do state that 4-11 option sets the port for Fortin communication but they do not state which protocol they are using specifically.

Rick

---

For the datalink protocols, we typically use the default ADS option in the compustar and enable option F2 (ap-ofa datalink) in the EVO-ALL.

 

I am wondering if can-bus did not program. This is easy to program on its own.

Disconnect th evo-all.

• Press and hold programming button.
• Insert power and release when led is blue
• Insert remaining connectors.
• Turn ignition on. Blue led will turn off and should start flashing soon after.

---

WIll try but question. If the can-bus didn't program would I be getting tach signals?  This info is definately being passed in the default mode.

---

Good point!, tach, foot brake, and all other features would also not be functional.

---

At the moment option F2 is off. I have tried it before but in order for it to work I needed to switch to the black port on the Compustar. However, even when the remote start worked the door locks still did not when configured this way.

To me it appears that the problem goes deeper. Compustar may have changed their communication related to the door locks and caused a problem with the evo-all.

Seems at the moment that unless I wire the door locks directly from the Compustar there is no solution from the evo-all.

Any other solutions?

---

Don't use the grey port on the compustar, use the black one. Setting the EVO-ALL to option F2 allows proper communication with the compustar using their ADS protocol.

 
For both the door lock data cut and immo data cut, double check that they are using the right wires from teh red connector of the EVO. Key data would still bypass correctly even if using the wrong relay from the evo.

 
Had engineering re-enable an old door lock firmware, 0.53. Feel free to try that one.