Questions & Answers

2015 Forester starts with OEM fob, but can not shutdown; auto window up/down broken.

0 votes
I installed Evo-one yeasterday on my 2015 Subaru Forester Premium.

It starts thje car with OEM fob, but can not shutdown. I also noticed driver auto window up/down function is broken - it can not fully open/close window with a short press. I have to press and hold window up/down buttons to open/close the window completely. I checked and double checked the installation according to GUIDE #57211 and can not find anything wrong. I did not connect A15/A16 (Hood and lift gate), as I do not care about alarm and can not find 6-pin connecter for lift gate. Please advice what is wrong and how to fix it.
posté Mai 29, 2018 dans la catégorie Subaru par rvdbos (130 points)

1 Réponse

0 votes
Auto rollup and rolldown will sometimes be needed to be reprogrammed following the instructions in the owner's manual of the vehicle after a possible loss of power due to the installation being performed if certain connectors or the vehicle's battery or power source is disconnected.

 

Most windows are reprogrammed by rolling up the window and once it reaches the top, release and pull up quickly once to program auto roll-up and for roll down, push the window control down until window is fully rolled down then push and release the window control once. (Please consult the owner's manual for possibly a different procedure)

As for the OEM remote monitoring, if you are in the USA, this function will not be functional when the vehicle is running, this is a limitation of the vehicle itself not accepting the signals from the OEM remote. (see note on fortin.ca)

If you are in Canada, please double check the datadoorlock wire as this is where we receive the signals from the oem remotes when the vehicle is running.
répondu Mai 30, 2018 par J M (64,060 points)
I resolved auto window roll up/roll down (actually, it fixed itself overnight somehow and works this morning, no idea why).

As for "vehicle itself not accepting the signals from the OEM remote" while running, this is obviously not true. OEM key fob operates just fine even if vehicle is running - it clicks, beeps, opens/closes doors as it should. Vehicle is accepting the signals. Problem is EVO-ONE is not responding to these signals.

Car is in US, but obviously produced in Japan. Not sure how it is different for US market. You mention some "note on fortin.ca". Do you have a link?
The signals we need is no longer provided is the issue. and as Derek posted, you can click on that and read the warning, which was put there for this specific reason which is region dependent.

Thank you,
...