Jump to content


Show
Photo

Killed My Bus... Oops!


  • Please log in to reply
5 replies to this topic

#1 jeebowhite

jeebowhite

    Resident Loon

  • Super Mod
  • 14,814 posts
  • Name: James
  • Ford Model: Sea Grey Mondeo MKIV 1.8TDCi 140ps Zetec
  • Year: 2007
  • Location: Kent
Contributor

Posted 05 March 2013 - 10:22 AM

Well, had an interesting drive home yesterday, all was well, popped along to screwfix to grab myself a bottle jack and got back in the car.

 

Stuck the key in, twizzled the key, started the engine, slammed the car to drive then reverse then chaos was released...

 

Rev needle was dancing, speedo was dancing, TRANSMISSION FAILURE, followed by STEERING ASSIST FAILURE, and a flashing then blank screen.... woops!

 

Car was still drivable and was in reverse, then tried to point it to drive and it just flopped...

 

Disconnected the battery for a couple of minutes, put it back on and all behaved itself... I am 99.9% sure that the problem was my own making, in that I started everything an did everything before the car was ready to!

 

Error Codes: Communication BUS failures all over as apparently it lost communication with the CAN system...

 

U1000
U0097
P193B
P1936
P1935
P1934
P0500
U1900
U0001

 

Cleared the codes down and they havent occurred again but Out of curiosity, anyone else experienced a similar issue?



Have something to contribute?

Sign in or register to start a topic...

Sign up to FOC Premium Membership To Remove These Ads

#2 alexp999

alexp999

    Ford Enthusiast

  • Moderator
  • 1,579 posts
  • Name: Alex
  • Ford Model: Focus 2.0 TDCi 163PS Titanium X
  • Year: 2012
  • Location: Dorset
Contributor

Posted 05 March 2013 - 12:19 PM

Sounds like a right "Computer says no" moment.

 

I haven't had a total failure like that, but the USB functionality completed locked up on my car, only way to fix it, was to take the usb out, turn everything off, lock the car, give it 10 mins then try again and all was well.

 

That is the problem with such heavy reliance on computers in modern day cars, hopefully it was a one off for you and there aren't any more problems.



#3 jeebowhite

jeebowhite

    Resident Loon

  • Super Mod
  • 14,814 posts
  • Name: James
  • Ford Model: Sea Grey Mondeo MKIV 1.8TDCi 140ps Zetec
  • Year: 2007
  • Location: Kent
Contributor

Posted 05 March 2013 - 01:28 PM

I think it wasnt just a case of "computer says no" I think it was "computer says [insert expletives in a very long list!!!!]"

 

yeah, I hope so. I know if I take the car to the garage they say no fault found. But, I might just give them a call as a heads up, so that if it does happen again, and I still have a months warranty left, at least they are aware...



#4 jeebowhite

jeebowhite

    Resident Loon

  • Super Mod
  • 14,814 posts
  • Name: James
  • Ford Model: Sea Grey Mondeo MKIV 1.8TDCi 140ps Zetec
  • Year: 2007
  • Location: Kent
Contributor

Posted 30 April 2013 - 08:32 AM

Finally managed to pin this problem down!!! and of all the unlikely culprits... it was the OBDII bluetooth scanner, and the Torque Pro app!

 

I set it up yesterday as I have started checking in journey my error codes, I then decided to switch over to live data view and watch a few of the sensors. Pulled up at shell, and popped a tank of fuel in, paid and got back into the car, key in the ignition, all dials move except fuel gauge - then the fun started

 

"Engine System Failure"

"Transmission Failure"

"Water In Fuel"

"Steering Assist Failure"

 

My car no longer surprises me, so I sat and looked at it for a few moments, reset it, same game... Tried to read the DTC Codes, but the adapter couldn't be seen by the phone. Checked the OBDII adapter and there was a flashing red light...

 

Ignition is still on, so I pulled the OBDII adapter out... All of a sudden, all gauges return to normal, all fine. Restarted car, all works fine. So it got me thinking, last time this happened, the car was connected to my phone, Torque Pro was running and it did exactly the same thing.

 

If you see any unexpected behavior in your car and you use an adapter similar to this, then start by disabling the app on the phone and restart the car, if that fails, disconnect the OBDII adapter and try again. one of these will most likely resolve the issue!



#5 stooge75

stooge75

    Too much time on the boards

  • True Ford Enthusiast
  • PipPipPipPip
  • 654 posts
  • Ford Model: Mondeo tdci zetec
  • Location: Angus

Posted 10 May 2013 - 12:39 PM

beware of cloned elm327 cables.they can cause damage



#6 jeebowhite

jeebowhite

    Resident Loon

  • Super Mod
  • 14,814 posts
  • Name: James
  • Ford Model: Sea Grey Mondeo MKIV 1.8TDCi 140ps Zetec
  • Year: 2007
  • Location: Kent
Contributor

Posted 10 May 2013 - 02:35 PM

Yaah, this one thankfully isnt a cable, but if it is a cloned bluetooth, its weird it worked fine on the Cee'd for a couple of years, but it doesn't like the focus!



Have something to contribute?

Sign in or register to start a topic...


Not what you're looking for?

Register now, we have a huge community of enthusiasts to answer any questions you might have



0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users