Questions & Answers

Why is PATS signal not recognized on 2000 Crown Victoria?

+1 vote
Installed an EVO-ALL on my 2000 Ford Crown Victoria along with a Compustar CS800-S. Double and triple checked all my wiring. I am using the D2D connection between the 2 modules, I have A1 tied into Brown/Pink at ignition switch which has power in RUN and START. A8 tied to Black GWR wire on the CS800. A10 and A20 tied to Grey/Orange and White/Light Green respectively on the connector halfway up the column(not at the cylinder). No other connections made on Evo-all.

Door locks and trunk work as designed and the vehicle cranks as expected. I was also able to program the EVO-ALL as described in the PROGRAM 1 section:

-Enter programming mode with D2D connection and then plug in Connector A. Cycle first key for 3 seconds(the yellow light also turns on at this point and stays on with the red.)

-Remove key and cycle same key again.Red light flashes 10 times and both lights turn off.

-Remote start. Vehicle cranks but theft light flashes and no start.

 

Everything seems to have gone smoothly except when trying to remote start, the theft light flashes and engine does not start. The red light on the evo all does light up during remote start and turns of when I depress the brake pedal. I disconnected the RX and TX and performed remote start with the key in the cylinder(but off) and the engine started. Reconnected RX and TX and provided dedicated ground on the GWR wire and still no start.

 

Ideas?
posté Jan 20, 2014 dans la catégorie Ford par Orionsax7 (230 points)
modifié Jan 20, 2014 par Orionsax7

1 Réponse

+1 vote

First thing first, do not try to reprogram the module if it did program.

I'd be curious to know if by cutting the vehicles Tx wire and leaving the Light Bleu/Black (A10) wire of the EVO on the vehicle side, if the vehicle remote starts.

répondu Jan 20, 2014 par Robert T (300,020 points)

No other ideas?

Honestly, 2000 Ford tells me the vehicle is not accepting the EVO even if the EVO is programming just fine. This may happen when all empty key slots are taken up in the BCM, which happens when people go to make some spare keys.


I was curious about the yellow LED for these reasons.

  • With the latest firmwares such as 71.11, we turn on the yellow led when ignition is on AND vehicle is started
  • With older firmwares such as 4.06/4.18, there should be a yellow LED on anytime 12v is present on the yellow wire.

If you have some aluminium foil handy, a quick and easy test would be to wrap one of the factory keys in aluminium foil and try starting the car with it while the the (-)ground-while-running of the EVO is grounded.

  • As soon as ground the (-)G-w-R, the RED led will turn on
  • Stick the aluminium foiled key in the barrel and try to start the car. Watch those LEDs to see what happens.

 

You would want to try this test with and without the modification on the Tx wire I made you do earlier.


I thought about the number of programmed keys also. I am a Ford tech and have access to a scan tool so I erased all the keys and programmed only my two keys. Then I reset the evo all by holding the button, releasing on red, holding again til leds alternating and unplugged. This way I could start from the beginning with only two keys programmed. I programmed the evo all (now at 4.06) and the red light flashes 10 times same as before. Try the remote start and the same thing still happens. The yellow led does not come on during remote start even though I verified there is power on the yellow wire. The only time the yellow led ever came on was during the programming of the evo all. Then I tried the foil. I used enough foil around the key so the car would not start with the key. I grounded the GWR and the red led turns on, cycled the foil key and the yellow led does not turn on. When turning the key on, the red led flickers for a split-second and then stays on again, but no yellow led. I checked again and made sure that there is power on the yellow wire all the way to the evo all. Maybe a bad module?

I wish there was an upvote button for comments, good test and explanation you did there.

Maybe a bad module?

Possible, but I honestly doubt it. There is one more thing to try out that engineering just told me and wanted you to try; the Red/Blue wire is a (+)Start input used to bump the EVO out of some firmware routines when installs also require Can-Bus connections. Even though the 2000 Crown Vic does not require any Can-Bus connections, the EVO may need to bumped out of a routine. Connecting that Red/Blue wire to the (+)Starter on the car/remote starter would fix that.

  • Again, you want to try that with and without that Tx wire split open.

One more little thing. I know you already tested the remote starter with the key in the barrel, but what about if the key is upside down in front of the barrel? Meaning, plastic end towards key hole as to not activate the key-sense.


 

First I tried the key backwards with plastic end next to ignition lock cylinder and attempted remote start. It did recognize the key and started right up. Then I put the Red/Blue (A9) to the start circuit of the vehicle/remote start. Tried to remote start a few times. Yellow led still did not turn on and the vehicle did not start, theft light flashing. I did notice that when the ignition turns on during remote start, the red led seemed to flicker a little more before going solid again but besides that, no change. As a tech myself, I know what its like to have poor customer information so I'm trying to be as detailed as possible without being confusing! Thanks for your help so far. I am becoming a little frustrated but mostly curious as to what the issue could be. :)

Email me your contact info at robert.tamilio@ifar.ca

I'm running out of ideas besides for using another module or just sticking a key in a box.

As a tech myself, I know what its like to have poor customer information so I'm trying to be as detailed as possible without being confusing!

Your doing a great job at it!

Thanks for your help so far. I am becoming a little frustrated but mostly curious as to what the issue could be. :)

Ford/Lincoln seem to always have the same problem coming back to haunt installers when it comes to transponder bypass.

...