2014 Ford Explorer Sport PTS

Question

I have purchased a cm6000 and evo-all. I noticed the guide only goes up to 2013. I entered the vehicle info in the flash link updater and updated the evo firmware. Wondering if the latest recommended firmware will support this vehicle. Build date 01/14. Or should I wait for a definite install guide to be released. Thanks

Answer 1

Hi Darren,

 

The 2014 Explorer would be the same installation. The guide will not be updated until it is final. The latest firmware for Ford should be fine.

 

A little tip for the programming.

• After step 6, remove the key from the keyport for about 30 secs before going onto step 7.

 

Comments

Thanks Robert, I will update once I get the install completed

---

Hi Robert,

After getting to step 6, I removed the key from the port as you suggested. I put it back in and continued to step 7 after 30 seconds or so. when moving to step 8, the red led turns off a few seconds after the blue on comes on before I hit the ignition x2. Does step 7-8 have to be done quickly once both red and blue led's are on?  After I continue all other programming steps (led's function as indicated in the guide) and use the dcryptor process and reinstall the evo as indicated, I get no key detected when I attempt to remote start. I reset the evo and reinstall, still same problem.

I initially was using the datalink connection method but decided to hard wire the connections after repeated failed start attempts.

I have approximately 2.5volts on both CAN wires I've double and triple checked all my conncections with the guide. Initially I had loaded firmware 71.14, but today the flashlink updater downgraded to 71.12.  EVO service #001A06254869.

I don't have any CAN (blue led) activity when trying to use the r/s lock/unlock, I get constant yellow led (ignition) when vehicle is running. When I attempt to r/s, the red led comes constant then the blue flashes and goes off. then I get the "no key detected" fault. This repeats 3 times until the r/s gives me a no start error. Seems to me like there is a comunication (firmware) issue. Am I missing something?

Thanks

---

Hi Darren,

 

I'll try to cram as much as i can in this comment to reduce the back-n-forth.

Three quick points to check.

1. Remove option 12 in the EVO.  It's currently turned On.
2. If you did the Driver Door pin connection, make sure the connection is not reversed. Green/Red of the EVO should be going  connector side.
3. Make sure the Lt.Blue/Black wire of the EVO is also on the connector side of the cut.

---

Here are some tests you will need to do with firmware 71.12.

Test 1:

Ground the (-)Ground-when-running of the EVO (RED LED will turn on), then manually push on the brake and then push on the vehicles PTS button. Does the car start this way?

 

Test 2:

Start the vehicle normally and once started ground and then remove the ground from the EVOs ground-when-running. Did anything happen?

---

I don't have any CAN (blue led) activity when trying to use the r/s lock/unlock,

The led should flash whenever it receives commands or when its sending data/commands. The Cans may not be programming properly.  A quick way to know would be to program only the Can-bus to the EVO, which is very easy to do.

• With a key in the vehicle. Start the programming but release on Blue.
• plug in all connectors to the EVO
• turn ingition On, blue led should start flashing
• turn ingition off and test door locks, brake status etc directly from the 20-pin connector.

I get constant yellow led (ignition) when vehicle is running.

This is normal. Yellow LED will turn on whenever ther is ignition. When remote starting, it will only turn on when ignition is present and the car is started.

When I attempt to r/s, the red led comes constant then the blue flashes and goes off. then I get the "no key detected" fault.

This is also normal operation; besides for the no "key detected" fault. :)

 

---

Hi,

sorry for the delay. I tried to program the CANS, but after turning on the ignition the blue  led did not flash as described. Also performing test 1 I got the the key detected error. Test 2 did not do anything. I'm beginning to wonder if I have a dud module or they changed the CAN wiring on this build and I'm not connected to the correct CAN .  The blue led flashes when I lock or unlock the doors with the factory remote or proximity sensor.  Nothing with the remote starter remote or brake pedal.  Can I just tie into CAN at the obdII connector?

---

You can use the Can wires at the OBD-ii as well; they will be the same colors.

The blue led flashes when I lock or unlock the doors with the factory remote or proximity sensor.  Nothing with the remote starter remote or brake pedal.

The LED will flash whenever it receives a command when programmed correctly. 

---

Seems as though the unit is not programmed corrrectly. Do a master reset on the EVO (this will also turn any options you previously turned on back to Off). Program only the Can-Bus and test all functions including remote start (with a key in the vehicle). Once this works go back and follow the regular programming procedure.

 

Master Reset Procedure:

1. Hold down programming button while plugging in datalink connector.
2. Let go of button when LED is RED.
3. Push and hold button again until all three LEDs start to alternate.
4. Disconnect unit, she is now reset.

 

Programming Only Can-Bus:

1. Hold down programming button while plugging in datalink connector.
2. Let go of button when LED is BLUE.
3. Plug in remaing connectors
4. Push 2x on the vehicles PTS button
5. Wait... Blue LED will start to flash
6. Turn off ignition

 

If door locks do work using the remote starter, try grounding either the Purple or Purple/Whtie wires from the 20-pin of the EVO. These are the lock-unlock inputs. Same with all the status' wires such brake, can be tested on the outputs of the 20-pin connector.

 

With only can-bus programmed, you should be able to also test remote starting by leaving a key in the car. This will show if the EVO is applying brake and "pushing" on the vehicles PTS button.  You should be seeing the brake lights turn On when the EVO receives (-)Ground-while-Running.

---

I reset the evo, the CAN programming procedure worked this time. Grounding the purple wire with the doors closed activates accessory power, grounding the purple/white sends CAN data but nothing happens. I'm not a professional installer but have done quite a few over the years and have never had problems like this before with your products, I'm considering picking up a new evo.

---

I reset the evo, the CAN programming procedure worked this time. Grounding the purple wire with the doors closed activates accessory power,

Problem found....  the EVO thinks the car is a key model. Which is why you are seeing the accessory pop on. The white/black wire on the key model normally connects to the vehicles lock wire. Hence you seeing accessory pop on when grounding the purple wire.

I'm not a professional installer but have done quite a few over the years and have never had problems like this before with your products, I'm considering picking up a new evo.

The problem is actually the firmware right now and not the EVO. It seems to be learning in the wrong mode thinking the car is a key model. Firmware - 0.79 will lock the EVO in push-to-start mode.

 

 

---

I only see 0.78 beta, I'll give it a shot.

 

it seems to be working somewhat now. R/s lock /unlock now working. Unit starts but stops with key in vehicle, possible a tach relean for the starter. I have to reflash my starter then reprogram evo correctly to set up the bypass.

---

0.78 yes, 0.79 is typo on my part.

 

This may sound a little odd, but, engineering is telling me you may have to program the EVO using the latest firmware, then once programmed and DCryptor finalized, flash back down to 0.78.

Unit starts but stops with key in vehicle, possible a tach relean for the starter. I have to reflash my starter then reprogram evo correctly to set up the bypass.

If you are using datalink with the compustar, you will have to turn the AP/OFA datalink option back on in the EVO (leave the Compustar in ADS protocol). The master reset turned all options back to default.

 

---

Success!

I thought I was going nuts, I have been tinkering with this install for months here and there when I had time.  Thanks for your patients. I have everything just about dialled in now. I figured early on that it might have been a firmware issue.  I have since gone back to datalink and adjusted the communication proto calls.  Everything is working good.  I will keep an eye out for any issues with the firmware.  As far as firmware: That was initially the procedure I followed , I did a DCryptor cycle after I flashed down but everything is working.  I had to relearn tach on my starter, that's why it would stall.

Thanks again for the support!

---

Exceeellent ! and thank you for your patience. Prerelease plans can be a stress sometimes but there is always a solution.

---

Hi, after using the r/s for a few weeks I have noticed that sometimes the vehicle won't start. The r/s will make 3 attempts to start the car by default. It seems that the timing of the r/s and evo might be off a bit (if possible). Seems like the evo is not activated long enough for the activation of the starter or vice versa in some cases. Sometimes it starts on the first attempt, sometimes the third or not at all. Wondering if changing the tach or crank time would have any effect on this or not because the start command is thru data.

---

The Red/blue wire on the EVO is normally a (+)Start input in non datalink installs. I would try wiring this to the remote starter (+)Starter.  Remote starter start signals are directly related to how ever the tach is programmed. Testing the start output on the remote start, will also help identify is there`s a problem with tach.

---

Hi, I have made the connection - same result. It starts every time with the key in the vehicle. I wonder about flashing to the latest firmware then running dcryptor and flashing back down will help like you mentioned in an earlier post.