Ford Automobiles Forum banner
21 - 40 of 146 Posts
Discussion starter · #21 ·
IDS is not very limited if you have engeenering code. But I agree UCDS is a very powerful software that is very user friendly. The reason ecus get bricked is conbination of bad VCM clones and users not knowing what they are doing but with UCDS this risk is very small.
 
Compare to what was few years ago in IDS unfortunately it is limited, even with engineering code and fully activated. Best example : try activate acc with IDS...
I will make easy for you, simply no chance...
With elmconfig or UCDS 5 min and job done.
Try activate autolock with IDS- again no chance as ford remove this option from IDS, in earlier versions you could edit xml file and was possibility to have this option in IDS now no chance.
With elmconfig or UCDS 2min.
I could do that all night, but there is no point, I will keep saying that for most things other software is better than IDS, IDS is only good for some kind of dealer procedures, where some of them are already available in UCDS ;)
 
Hope it's OK to resurrect this thread?

I just got a 2012 S-Max 140 and would like to do this. I'm wondering if I should be getting CAN cable, ELMconfig, Forscan, VCM, IDS etc and/or UCDS in general (hence I started a general thread in the diagnostics section) but also specifically for this mod - is there a concensus on whether UCDS is now the way to go for this, or ELMconfig/IDS?

I understood from the UCDS forum that doing this with the electronic handbrake, which I have, left a residual error code in the handbrake module - would the ELMconfig/IDS method in the OP here have the same issue? Maybe it's solved now for UCDS method anyway?

Any help appreciated.
 
Hi Liam

I had the same question but according to this post... basically you need UCDS.

It can be done with IDS interface and ELMconfig but everyone seems to go the UCDS route.

I suppose it's all down to which is cheapest? There are VCM/IDS units on the bay though for about ÂŁ70

There are also the fake UCDS units as mentioned above that are a bit cheaper... even though they are not the latest versions they do seem to work as normal, certainly for older vehicles like ours.

Not sure about the error code they talk about, I don't have the electronic brake.

Hope it's OK to resurrect this thread?

I just got a 2012 S-Max 140 and would like to do this. I'm wondering if I should be getting CAN cable, ELMconfig, Forscan, VCM, IDS etc and/or UCDS in general (hence I started a general thread in the diagnostics section) but also specifically for this mod - is there a concensus on whether UCDS is now the way to go for this, or ELMconfig/IDS?

I understood from the UCDS forum that doing this with the electronic handbrake, which I have, left a residual error code in the handbrake module - would the ELMconfig/IDS method in the OP here have the same issue? Maybe it's solved now for UCDS method anyway?

Any help appreciated.
 
Does the Forscan need to read at 500k baud?

Tried Elmconfig and that wont connect at 500k, gives an error.

Forscan app seems to connect to the car, but i only had a quick look

at it. Didnt connect to any modules etc.

Time for my original F-Super to retire :)
 
Mines stuck at 38400, wont work past that even with Forscan.

Think its a dud one.

Will be sending it back for a refund.
 
Change the config to the correct engine code (DW10C 150) , write to IPC / BCM.

In service functions reinit PCM and presto 163 hp..

Will check this weekend and maybe do a more easy to follow guide.
OK so do I load (play button) the BCM module then change the configuration?

I looked at the PCM but the asbuilt data is all hex code?

any help would be very much appreciated :)
 
I thought the Forscan guys also had an IDS when they did the upgrade?

Had a quick look and just followed link after link until it stops saying you need to be

registered. Gave up then.

They did say the UCDS? where you loaded the Kuga data was a bit of a dodgy fix, not exactly worded that way. But translation was a bit odd. Screwy?
 
21 - 40 of 146 Posts