Diesel Diagnostics

Back to Forum

Post a Response

Ford Fusion 1.4 TDCi 2004 - Non-start after calibration update & mileage increasing - Unresolved #

Posted by Matt Booth on January 8, 2013, 8:33 pm

Year of Manufacture *: 2004
Engine Size and Code *: 1.4 TDCI
( Optional ) Scanner Used: Ford VCM2
( Optional) Fault Codes: None

Hi,
We carried out a calibration update on this vehicle. This completed sucessfully but after a road test a fault appeared of P1639 Vehicle ID Block Not Programmed Or Corrupt and the vehicle wouldn't rev more than about 3k. I've seen this before where the axle and tyre size aren't programmed correctly after an update and sure enough these were wrong so I programmed them in.

The car will now not start at all. The PATS light comes on when you turn the key on and then goes out as it should. There are no fault codes.

Even more strange is the mileage is ticking up when the ignition is switched on!

How can changing the tyre/ratio parameters have such an effect???? I haven't had chance yet to check for the feed going to the starter but it seems strange that it ties in with the mileage.

The update was at the request of the customer whilst it was being serviced - Ex ford chap thinks he knows best. To be fair I've done updates for various reasons before and never had this.

Any ideas?
Thanks!
Matt

UPDATE - Possible bug in IDS software, anyone experienced?

Posted by Matt Booth <iframe src='https://members.boardhost.com/ukautotalk8/info/user=ukat3028' width='330' height='300' border=0 style='border:none;'> on January 9, 2013, 11:07 pm, in reply to "Ford Fusion 1.4 TDCi 2004 - Non-start after calibration update & mileage increasing #"
Matthew Booth

Well I flashed the PCM again and that sorted the mileage issue. Tried following through the PATS module initialization procedure but I just got the message "Diagnostics" on the dash after entering incode and the IDS screen went back to the main PATS menu. I believe I should be presented with a screen to select what it is I wish to initialize with the PATS (PCM, fuel pump etc).

In the process I tried erasing all keys and relearning them which went fine. The PATS light now stays solid for about a minute when I switch the ignition on and then flashes code 3-2 which for tech say is an issue with synchronization to the fuel pump. Also, when I try to crank I get fault code P1621 Wrong code word received.

I'm reloading the IDS software with older version 80 in the hope the option was bug free then or that my main install may be corrupt.

I'm sure I just need to initialize the PCM to the PATS to crack this.

Matt

Re: UPDATE - Possible bug in IDS software, anyone experienced?

Posted by Ian Slattery <iframe src='https://members.boardhost.com/ukautotalk8/info/user=UKAT1196' width='330' height='300' border=0 style='border:none;'> on January 10, 2013, 9:11 pm, in reply to "UPDATE - Possible bug in IDS software, anyone experienced?"
Ian Slattery

Hi Matt

Sounds like you are having a nightmare with this one. I have never had this problem but i will put a few ideas your way.

If memory serves me right does it not give you the option screen first before it asks for the in code.

What in code calculator are you using as i have had problems with cytoworks codes being wrong.
Are you using the longer code for module initialization [different reason for access]

Maybe try telling it its had a new cluster before trying to match them up. hth

Regards Ian

Re: UPDATE - Possible bug in IDS software, anyone experienced?

Posted by Matt Booth <iframe src='https://members.boardhost.com/ukautotalk8/info/user=ukat3028' width='330' height='300' border=0 style='border:none;'> on January 10, 2013, 10:00 pm, in reply to "Re: UPDATE - Possible bug in IDS software, anyone experienced?"
Matthew Booth

Thanks for the reply Ian, this one is definately breaking me!!!

It does indeed have an option screen before the incode. The screen lists options (rough order):

Erase all keys
Program new key
Enable/Disable hire mode
Module initialization
Exit

I'm using an incode calculator on autokeyprog.com
I'm assuming it's codes are good as they work to erase and program keys and I don't get an error to say they're wrong (I assume I would).

What do you mean by the longer code for module initialization? From what I've done so far I've found that there seems to be no rhyme or reason for it giving me either a single 6 character code or a double length code. I did notice the reason for access but the incode calc just asks for the outcode not a reason for access.

The website says...
Supported features:
•Module initialization;
•Key programming;

Does cryptoworks usually calculate a different code if you select a different reason for access??

At the moment I'm just loading V79 onto a fresh install of windows incase the bug lies in the latest version.

Thanks again
Matt

Re: UPDATE - Possible bug in IDS software, anyone experienced?

Posted by Ian Slattery <iframe src='https://members.boardhost.com/ukautotalk8/info/user=UKAT1196' width='330' height='300' border=0 style='border:none;'> on January 11, 2013, 8:09 am, in reply to "Re: UPDATE - Possible bug in IDS software, anyone experienced?"

Hi Matt

I think its a different code on later fords[longer] for module initialization.

You may have to use the official way [ have you got a etis account? ].

Give me ring on 0161 746 8067 if you want to know how to get them.

Regards Ian

Re: UPDATE - Possible bug in IDS software, anyone experienced?

Posted by Matt Booth <iframe src='https://members.boardhost.com/ukautotalk8/info/user=ukat3028' width='330' height='300' border=0 style='border:none;'> on January 12, 2013, 9:44 pm, in reply to "Re: UPDATE - Possible bug in IDS software, anyone experienced?"
Matthew Booth

Hi Ian,

Thanks for the hints. I registered on etis and noticed there was a technical help number for 'complex' faults. Hoping they would be more useful than the blue oval club number I gave them a call.

The chap, whilst sounding very knowledgeable, couldn't come up with any ideas. The code gen i'm using is providing the correct codes as the ids complains when you enter a wrong code. He concluded that the pats in the dash is working fine as I can program and erase keys. The issue lies with communication between the dash and PCM - although a network test completes successfully.

I tried disconnecting the PCM before starting the PCM replacement programming so that IDS could not inhale the existing data in the PCM. I was presented with a few configuration options just before programming took place but after programming I still couldn't initialize the PCM to the PATS.

I found out today that the vehicle previously had been been recovered for non starting with no root cause found, it just started working. So I believe my issues to be related to the previous starting issue.

I have another guy coming Monday with the older VCM (we use the VCM2) so that we can eliminate hardware issues. If that doesn't work and once I've thoroughly checked the wiring I think I'm going to go down a new PCM route. I also noted that the N/S/F looks like it's had a bump previously and the PCM is located just behind the headlight so it may have been stressed at some point.

If all fails it's out with the petrol and matches

Have a good Weekend!
Matt

Re: UPDATE - Possible bug in IDS software, anyone experienced?

Posted by Ian Slattery <iframe src='https://members.boardhost.com/ukautotalk8/info/user=UKAT1196' width='330' height='300' border=0 style='border:none;'> on January 13, 2013, 10:44 am, in reply to "Re: UPDATE - Possible bug in IDS software, anyone experienced?"
Ian Slattery

Hi Matt

I don't know from what year they started doing different reasons for access, meaning different codes.

Like you say i would expect ids to tell you its the wrong code.

I had a 09 connect that lost the pats information after a re flash and i used the calculator you are using [Its great for keys] to initialize the pcm it did the same as yours [If my memory is correct, a little bit dodgy]. When i got the cytoworks working and filled the full form out including reason for access it produced a longer code 5 to 6 digits and that worker OK.

I tried to match a cluster on a 08 focus using cytoworks [including reason for access] and it kept telling me the wrong code. So i had to get the code officially from ford using my etis membership. Let me know if you need to know how to do it.

All i am saying for £15 for a code it is worth a try. I would offer you access to cytoworks but as usual mine is not working at the moment.

You probably know this but most fords can have a secondhand pcm programmed.

Regards Ian

Re: UPDATE - Possible bug in IDS software, anyone experienced?

Posted by Matt Booth <iframe src='https://members.boardhost.com/ukautotalk8/info/user=ukat3028' width='330' height='300' border=0 style='border:none;'> on January 13, 2013, 11:12 am, in reply to "Re: UPDATE - Possible bug in IDS software, anyone experienced?"
Matthew Booth

Thanks Ian. The chap coming monday uses cryptoworks so i'll see what luck he has. I will take your advice and try the etis way though. I'd rather not put a PCM on it or pay someone else to come do the PATS when I've invested in the gear!

I've got the 9 digit code to call them for the incode so I'll do that.

Am I right in saying the incode request form will ask for the owners address? If so i'll make sure to get it before hand so i'm not waiting.

Cheers
Matt

Re: UPDATE - Possible bug in IDS software, anyone experienced?

Posted by Lee Mackintosh <iframe src='https://members.boardhost.com/ukautotalk8/info/user=UKAT1348' width='330' height='300' border=0 style='border:none;'> on January 13, 2013, 11:38 am, in reply to "Re: UPDATE - Possible bug in IDS software, anyone experienced?"
Lee Mackintosh

I've used this free pats incode calculator a few times in the past but not for a few months now to program keys and it worked perfectly fine.

http://www.autokeyprog.com

You'll need to register with them to activate your account.

Re: UPDATE - Possible bug in IDS software, anyone experienced?

Posted by Carl ford <iframe src='https://members.boardhost.com/ukautotalk8/info/user=UKAT1822' width='330' height='300' border=0 style='border:none;'> on January 13, 2013, 8:31 pm, in reply to "Re: UPDATE - Possible bug in IDS software, anyone experienced?"

I use cryptowork if you want a incode give me a call tomorrow on 01522 528537 and I can sort you an incode.

Regards
Carl

Unresolved #

Posted by Matt Booth on January 15, 2013, 9:05 pm, in reply to "Re: UPDATE - Possible bug in IDS software, anyone experienced?"
Message modified by board administrator January 25, 2013, 6:33 pm

Lee - yeh that's the website i've been using which seems to work well.

Carl - Thanks thats a kind offer. As it happens the chap that came out with his VCM was using cryptoworks (dongle not online version) but it rejected all the codes it generated which was strange.

As advised by Ian (and thank you for your continued help through this!!) I requested a code from ford which was a pain but at least I have everything set up for future requests now. Unfortunately the code gave the same response as I had been getting previously - the dash showed 'diagnostic' but the IDS returned to the main PATS screen. I also tried the details for that request on the aforementioned website which generated the same code so worth book marking.

I've double checked wiring, connections and fuses and I'm still quite confident that the PCM is faulty. I even found the exact unit in a vehicle in a local breakers for £50+VAT BUT......

The customer's dad was a mechanic in his previously life and suggested we change the PCM, instrument cluster, keys and locks. Yes this 'should' get the thing running but at great expense and with the wrong approach. We declined to carry out this work and went with their suggestion to recover the vehicle to the dads garage. So the car will be picked up by the customer and taken 100 miles for someone else to guess.

Trouble is the customer was fine all the time we were explaining our process and outcome but he would return later having googled stuff or speaking to the dad and have a new found fight in him.

I put in a lot of hours without the intention of charging a massive bill but wanting to understand the fault and get the thing right for the customer so this outcome is incredibly frustrating. Even now we haven't charged the customer for any time spent on it. Hopefully we'll retain him as a customer in the future.

Thanks again everyone for your help.

Matt

« Back to index

[ Diesel Diagnostics ]

Copyright © uk autotalk