2013+ Ford Escape Forum banner

1 - 11 of 11 Posts

·
Registered
Joined
·
11 Posts
Discussion Starter #1
Let me preface this by saying I have searched through here and Google but didn't find a similar scenario so I am posting this for help.

So I got a 2018 FE SEL 2WD last month and the winters already here, I will was looking into options for installing remote start and I came across the fordpass app which is supposed to have that feature (occasionally buggy I read). And so I downloaded the app and registered the car with the VIN and after setup I proceeded to test it, the doors unlock and lock without an issue, but when try to start the engine, the car goes through the motions (doors lock, lights blink) three times and then nothing. On the phone I get an error message saying "warning... Vehicle failed to start"
75969



I searched in here and the most common recommendation was to do a sync master reset, delete and reinstall app, add car again.
I did all of the above but the other 2 functions work (so I know vehicle connect works), however the remote start fails every time.

Could this be a trim issue (does remote start work with SEL or only titanium), but if this is the case, the app should have made that explicitly clear, it's got the VIN number so it knows the car and should know what its capable of.
I tried to reach the Ford guide but no one picks up in 30 minutes, so I thought I'd reach out and see if anyone has experience with this.
 

·
Premium Member
Joined
·
1,481 Posts
Let me preface this by saying I have searched through here and Google but didn't find a similar scenario so I am posting this for help.

So I got a 2018 FE SEL 2WD last month and the winters already here, I will was looking into options for installing remote start and I came across the fordpass app which is supposed to have that feature (occasionally buggy I read). And so I downloaded the app and registered the car with the VIN and after setup I proceeded to test it, the doors unlock and lock without an issue, but when try to start the engine, the car goes through the motions (doors lock, lights blink) three times and then nothing. On the phone I get an error message saying "warning... Vehicle failed to start"
View attachment 75969


I searched in here and the most common recommendation was to do a sync master reset, delete and reinstall app, add car again.
I did all of the above but the other 2 functions work (so I know vehicle connect works), however the remote start fails every time.

Could this be a trim issue (does remote start work with SEL or only titanium), but if this is the case, the app should have made that explicitly clear, it's got the VIN number so it knows the car and should know what its capable of.
I tried to reach the Ford guide but no one picks up in 30 minutes, so I thought I'd reach out and see if anyone has experience with this.
Welcome to the forum. First consider putting your vehicle information in your signature line. Second, WRT, the start problem, I think it has happend to me. I do not use the app that much for that service. The fact that it locks your doors means its got the correct vehicle. Only thing I can suggest is try and hold the button on the app start a little longer. As I recall, it is a little sensitive in that area. Also, go to the settings on your car's information screen. As I recall, there may be a setting there.
Sorry I could not be of more help.
 

·
Registered
Joined
·
4 Posts
Let me preface this by saying I have searched through here and Google but didn't find a similar scenario so I am posting this for help.

So I got a 2018 FE SEL 2WD last month and the winters already here, I will was looking into options for installing remote start and I came across the fordpass app which is supposed to have that feature (occasionally buggy I read). And so I downloaded the app and registered the car with the VIN and after setup I proceeded to test it, the doors unlock and lock without an issue, but when try to start the engine, the car goes through the motions (doors lock, lights blink) three times and then nothing. On the phone I get an error message saying "warning... Vehicle failed to start"
View attachment 75969


I searched in here and the most common recommendation was to do a sync master reset, delete and reinstall app, add car again.
I did all of the above but the other 2 functions work (so I know vehicle connect works), however the remote start fails every time.

Could this be a trim issue (does remote start work with SEL or only titanium), but if this is the case, the app should have made that explicitly clear, it's got the VIN number so it knows the car and should know what its capable of.
I tried to reach the Ford guide but no one picks up in 30 minutes, so I thought I'd reach out and see if anyone has experience with this.
It's not a trim issue.
I use Fordpass Remote Start with my 2018 SE.
It should work with any trim that has SYNC 3.
SYNC 3 is included with all 2018 SEL and Titanium models.
It is an option for the 2018 SE.

It works most of the time.
Having a strong WIFI or data signal is important.

Whenever I have consistent no start issues reinstalling the app fixes it.
 

·
Registered
Joined
·
11 Posts
Discussion Starter #4
Thanks Ralph7up and Dee60, for confirming it's not a trim issue. On Reddit there are a couple of posts that suggest it be a fault that is triggered when the engine is turned off with the transmission not in park. I have a scheduled appointment at the dealers in 2 weeks and they've agreed to look into this. I will report back with any updates.
 

·
Registered
Joined
·
227 Posts
Have you checked your Remote Start settings in the driver display? You may have the "Start" portion disabled, which would leave the Doors Lock/Unlock still functioning.
In any case, on the app, press and hold the Vehicle Start button for about two seconds to be sure that the ring around the button starts rotating. Mine takes a l l l o o o n n n g g g time to start and send a confirmation back to the app; much longer than the Dronemobile® system installed on my '09 Mariner.
 

·
Registered
Joined
·
11 Posts
Discussion Starter #6
Have you checked your Remote Start settings in the driver display? You may have the "Start" portion disabled, which would leave the Doors Lock/Unlock still functioning.
In any case, on the app, press and hold the Vehicle Start button for about two seconds to be sure that the ring around the button starts rotating. Mine takes a l l l o o o n n n g g g time to start and send a confirmation back to the app; much longer than the Dronemobile® system installed on my '09 Mariner.
With respect to pushing and holding the app buttons, yes I am holding it for a few seconds, the app actually prompts you if you let go too quickly.

Now I just accessed the in display remote start setting and played about with the options, toggling quiet start, as well as system, qnd even restoring all to default. And with every settings change, I attempt to remote start with the app but it still fails.

Thanks for the suggestions though.
 

·
Registered
Joined
·
227 Posts
With respect to pushing and holding the app buttons, yes I am holding it for a few seconds, the app actually prompts you if you let go too quickly.

Now I just accessed the in display remote start setting and played about with the options, toggling quiet start, as well as system, qnd even restoring all to default. And with every settings change, I attempt to remote start with the app but it still fails.

Thanks for the suggestions though.
One other thing- the key must be removed from the ignition and all doors closed, same as on my Mariner, or it won't remote-start.
 

·
Registered
Joined
·
6 Posts

·
Registered
Joined
·
11 Posts
Discussion Starter #9
Check out the info at https://ford.oemdtc.com/3799/engine-shuts-off-immediately-after-remote-start-with-or-without-dtc-p1594-stored-in-body-control-module-bcm-2016-2018-ford-escape-focus-transit-connect.

My 2018 SE would only remote start about half of the times I attempted it. Sometimes, the app would say it started and other times I would get the failed to start message. Since the dealer applied this update, it has started consistently.
Thanks , I believe this is what was referenced on Reddit. I've got a dealer appointment for next week so we'll see how it goes.


Chrisgb,
To ensure i was meeting the criteria for remote start, I made sure i did the tests from multiple locations, including indoors with home wifi.
 

·
Registered
Joined
·
11 Posts
Discussion Starter #10
Follow up post. This is now resolved.

Some background. I bought this car from auction because it had a damaged passenger's side front door and was a steal at the price. Door was replaced without any issues.
Long story short, the dealer wanted 150CAD just for diagnosis and this did not include the cost of fixing it.

Now from Eyet60's link above and from a reading around it appears to need a reprogramming of the Body Control module and so i figured I had 3 possible paths to take

1. There is the excellent forscan which is free to use (Windows), i would get a cheap ELM cable to try to clear any DTCs which might be present in the Body CM. (cost 20 dollars) maybe this would fixed the issue. If this fails

2. The company VXDIAG offers a VCX Nano cable for Ford/Mazda and it ships with version of Ford IDS. This is of course what the dealer has access to, I would see if i could fix any failures from scenario 1 above or attempt to update the BCM if this is required (based on the FSA posted above) - estimated cost 130CAD, but scary as hell given the numerous BCM horror stories i have been reading online.
3. Cough up an estimated 300CAD plus taxes for the dealer to fix this (150CAD plus taxes if i can get them to do the BCM update without running the diagnosis).

So i got the Forscan and a cable with a manual HS/MS CAN switch, hooked it up to the car and sure enough there was a stored Code: B1492 - Fuel Cutoff Event

Status:
  • DTC Present at Time of Request
  • Malfunction Indicator Lamp is Off for this DTC
I tried clearing the code and it just would not disappear. I searched online and sure enough there were plenty of references to DTC B1492 affecting Ford Escapes involved in some types of crashes. This code is stored in the BCM and will cannot be erased. Further search suggested the BCM crash status would need to be reset using a Full featured diagnostic software (IDS and a couple of others i had never heard about before last night, but not Forscan or Focccus).
So I ordered the Vxdiag cable, went to their website and downloaded a copy of IDS v116 (I will not go into details about this aspect). The cable arrived a few minutes ago (along with a mini car inverter i bought to power my laptop battery from the running car just in case i had to be there for a while, given that the laptop is old and can barely hold an hour of charge, i didn't want to be surprised by a failed laptop).
I hooked up the IDS, set it up and it took all of 2 minutes to reset the BCM crash status. I shut down the car, took out my phone and tested the remote start feature from the app and this time around it worked with no issues.

There are quite a few folks who have posted about this issue around the internet but no one posted their solution, so i wanted to make sure this was not another unresolved thread left hanging for the next guy/gal who wants to fix this issue (apparently the B1492 code is responsible not only for a failed remote start, but also a failure of the auto stop/start ecoboost function in some cars.)
 

·
Premium Member
Joined
·
1,481 Posts
Follow up post. This is now resolved.

Some background. I bought this car from auction because it had a damaged passenger's side front door and was a steal at the price. Door was replaced without any issues.
Long story short, the dealer wanted 150CAD just for diagnosis and this did not include the cost of fixing it.

Now from Eyet60's link above and from a reading around it appears to need a reprogramming of the Body Control module and so i figured I had 3 possible paths to take

1. There is the excellent forscan which is free to use (Windows), i would get a cheap ELM cable to try to clear any DTCs which might be present in the Body CM. (cost 20 dollars) maybe this would fixed the issue. If this fails

2. The company VXDIAG offers a VCX Nano cable for Ford/Mazda and it ships with version of Ford IDS. This is of course what the dealer has access to, I would see if i could fix any failures from scenario 1 above or attempt to update the BCM if this is required (based on the FSA posted above) - estimated cost 130CAD, but scary as hell given the numerous BCM horror stories i have been reading online.
3. Cough up an estimated 300CAD plus taxes for the dealer to fix this (150CAD plus taxes if i can get them to do the BCM update without running the diagnosis).

So i got the Forscan and a cable with a manual HS/MS CAN switch, hooked it up to the car and sure enough there was a stored Code: B1492 - Fuel Cutoff Event

Status:
  • DTC Present at Time of Request
  • Malfunction Indicator Lamp is Off for this DTC
I tried clearing the code and it just would not disappear. I searched online and sure enough there were plenty of references to DTC B1492 affecting Ford Escapes involved in some types of crashes. This code is stored in the BCM and will cannot be erased. Further search suggested the BCM crash status would need to be reset using a Full featured diagnostic software (IDS and a couple of others i had never heard about before last night, but not Forscan or Focccus).
So I ordered the Vxdiag cable, went to their website and downloaded a copy of IDS v116 (I will not go into details about this aspect). The cable arrived a few minutes ago (along with a mini car inverter i bought to power my laptop battery from the running car just in case i had to be there for a while, given that the laptop is old and can barely hold an hour of charge, i didn't want to be surprised by a failed laptop).
I hooked up the IDS, set it up and it took all of 2 minutes to reset the BCM crash status. I shut down the car, took out my phone and tested the remote start feature from the app and this time around it worked with no issues.

There are quite a few folks who have posted about this issue around the internet but no one posted their solution, so i wanted to make sure this was not another unresolved thread left hanging for the next guy/gal who wants to fix this issue (apparently the B1492 code is responsible not only for a failed remote start, but also a failure of the auto stop/start ecoboost function in some cars.)
GREAT READ! Thank you for posting! Good day. I learned something new.
 
1 - 11 of 11 Posts
Top