Questions & Answers - Questions récentes tagguées gwr

Remote start status (eg. Wiper Interrupt) when GWR (Dark Blue A8) is configured for RAP pulse per Function 32 Mode 3?

Thu, 06 Aug 2020 21:49:57 +0000

Product: EVO-ONE
Vehicle: 2010 Toyota Tacoma (Standard 40-bit Key)
Configured per Fortin application note

I am looking for a signal (negative or positive) to indicate that the EVO-ONE has remote started the vehicle and that it is currently running. Ultimately looking to slave features such as wiper inhibit, defrost, etc. I understand that the Dk. Blue A8 "GWR" configured as Function 32 - Mode 1 or Mode 2 would be exactly what I need however I am required to configure GWR as Mode 3 for "Autolight shutdown" per the installation guide for my vehicle. I haven't looked at the signal with a scope or logic analyzer to confirm but it sounds like it will pulse ground only at the end of the remote start run but otherwise float high impedance.

I have scoured all documentation I can find but am wondering if there is another pin which may have an undocumented setting or alternative function which could be used for this?

I suppose in this case, I could force GWR line back to Mode 1 and then program a microcontroller to then mimic the RAP signal needed for Autolight shutdown -- but -- hoping there is a trick I am missing.

09 Sierra 1500 EvoAll GMT4 with Easyguard E002 PKE and remote starter issues with GWR

Fri, 15 May 2020 18:33:16 +0000

2009 GMC SIERRA SLT 1500 standard key installation GUIDE 59001

EvoAll w/ GMT4 T Harness: SN 001A07 112374

Firmware 70.39

Hardware: 7.0

Remote Starter and PKE Easyguard E002

I believe I am having issues with the PKE module's GWR (-) output. Initially I wired the PKE GWR out with EvoAll GWR in Dk. Blu wire. But doing so caused an "SERVICE THEFT DETERRENT" error to appear on my Dash Display. I was also not able to remote or key start my engine. Meanwhile the EvoAll showed solid RED and YELLOW led indicators with flashing Blue. It was as if the EvoAll was not working as Bypass Immobilizer. I figured the PKE module's ignition was not delayed long enough for the GWR to notify the EvoAll to bypass the immobilizer. I tested that theory by manually grounding the GWR input to see a RED led on the EvoAll then remote or key start the engine. This test showed that the engine was able to key and remote start. Does anyone have any way or any idea how to fix this GWR out from the PKE module? any ideas on how to provide a ground for the EvoAll GWR before attempting to remote start? Or ideas on how i could delay the ignition/start long enough for the GWR input and EvoAll bypass the immobilizer? Or just any way i could remedy this issue.

Thank you all in advance and i hope to hear some ingenius ideas/options from you all soon. Thanks again.

Kia forte don't crank exterior lights flash

Sun, 06 Dec 2015 16:42:10 +0000

When pressing on the remote the exterior lights flash like the car would like to start but nothing happen. Constated that the 3 light of the fortin coupe dosen't light, except the yellow light of the ignition when key is on but engine off. The only information I got from the troubleshoot was the verify the power ground of the module, ground and 12v is there.

All other options work fine on it. Saw three fuses under the dash and nothing blown. Need more infos the continue troubleshoot thanks.

The module installed is fortin evo-all

-Eric

GWR signal putting vehicle into IGN state

Tue, 06 Oct 2015 18:11:07 +0000

Hi

Vehicle is a 2014 Ford Focus manual trans. Installing AdvancedKeys (AK) Smart Keyless Entry + Push Start System along with EVO-ALL.

While switching the vehicle into ACC state with the push button, the AK push start module provides GWR signal to GWR (dark blue wire) of EVO-ALL. This is enabling EVO-ALL as immobilizer bypass (RED led turns ON) and EVO-ALL is actually putting the vehicle into IGN state instead of user-intended ACC state. This is creating a conflict.

Can EVO-ALL be setup in a way to workaround this behavior?

Thank you!