topblog Ivoire blogs

25/09/2018

How to: Ford IDS reprograms PCM using different calibration files

Confirmed! There is a way to use IDS software to reprogram the Ford PCM using different calibration files. Just make sure you have the correct one - mainly from a van/vin that has same turbo & injectors.

 

This is how to remap using Ford IDS cracked software.

This is based on my experience (Ford Transit Custom 2.2 125ps), UK based vehicle mapped from 125 to 155ps.

YOU DO IT AT YOUR OWN RISK. YOU ARE RESPONSIBLE YOURSELF FOR ANY HARM OR DAMAGE THAT YOU SUFFER AS A RESULT. INCLUDING LOSS OF WARRANTY. I MIGHT NOT BE ABLE TO ASSIST IN CASE OF ISSUES.

Things needed:

- basic IDS knowledge (a lot of guides can be found here: http://blog.obdexpress.co.uk/ use the Search button)

- IDS with programming capability (VCM2 SP177-C1, VXDIAG Nano or similar) - cracked will do

- Your own VIN and PCM Calibration number to revert back in case of issues

- Reference vehicle details - (the hard bit - but can be found online) - needed to get the calibration numbers to use; in my case this was Ford Transit Custom 2.2, 155ps

The basic process is:

VERY IMPORTANT!!! - MAKE SURE YOU CAN RE-PROGRAM YOUR VEHICLE WITH YOUR OWN CALIBRATION NUMBERS (BEFORE TRYING ANY OTHER ONES). FOLLOW THIS PROCEDURE USING YOUR OWN VIN AND PCM NUMBER - THIS IS WHAT YOU WILL NEED TO DO IF THINGS DONT WORK!!!!

1) get VIN and PCM calibration number from your reference vehicle

2) run IDS software without physically connected to Vehicle

3) run Vehicle identification which will obviously fail and continue to manual vehicle identification

4) in manual vehicle identification enter the PCM calibration number - read on below about it

5) when asked enter the reference VIN and odometer value (any)

6) now you can navigate to Module Programming (PM not PMI) and program PCM but DONT PLUG IT TO YOUR VEHICLE YET

7) you should be asked to re-enter the VIN (enter the one from the reference vehicle)

8) you will get an warning of a low voltage

9) connect the cable to your vehicle and follow the instructions on the screen

10) after the programming is finished (takes around 10 min on mine) - you will need to reset all adaptation values as the current ones will be invalid (this is very important)!! - MAF, Injectors, Turbo

11) go for a drive - if it has any issues (no turbo, complete lack of power, or no start) - run the same procedure with your own VIN and PCM numbers.

Now, the reference vehicle should be of similar spec to yours. To minimise any issues I made sure the following components are the same before trying to program its calibrations to mine:

- injectors

- turbo

- pcm HW

All of the part numbers can be checked in ECAT for your vehicle and the referenced one. You will need VIN to do so.

You can search google images for vehicle registration numbers and get the VIN using ETIS Online. You need the VIN to get part numbers in ECAT (injectors, turbo, pcm). If the numbers match (dot to dot) run both the VINs through ETIS Online and check modules HW numbers. Make sure the HW number of PCM is the same and other modules are not far off.

The alternative way of finding reference VIN is just using ETIS Online - just experiment entering VIN that is next to yours (serial number). My reference vehicle was 1 serial number below my VIN

Once you happy with your reference vehicle - we can move on and find the calibration numbers for it.

Go back to ETIS Online and write down the SW number for PCM (calibration numbers). It will be in the following format: BK21-14C204-BNU. The last character is the revision of the calibration - BK21-14C204-BNP was before BK21-14C204-BNU and BK21-14C204-BNU was before BK21-14C204-BNV.

When entering the calibration in IDS you will need to use any but the latest (otherwise IDS won't let you upgrade).

You can check the calibration revisions here: https://www.fordtechservice.dealerconnec...roduct=IDS

just enter the SW parts and try changing the revision number. You will quickly figure out what revisions are available.

Fingers crossed

 

 

Source:http://blog.obdexpress.co.uk/2018/09/25/ford-transit-cust...

22/09/2018

2014 Ford Fusion Remote Programming: Otosys IM100 or IM600?

Customer puzzle:

Can I use Otosys Im600 to program a smart to my car? Ford Fusion year 2014

 

Obdexpress.co.uk customer service:

Yes, yours is in the list. You can make it.

Btw, if your car is listed in the AuroDiag Otosys IM100 or IM600 car list, try again and you will have success.

 

Here is the test report of Otosys IM600 on you model, 2014 Ford Fusion…

 

The car

otosys-im600-ford-fusion-2014-1

 

The blade key to be programmed

otosys-im600-ford-fusion-2014-2

 

Selected the car: 2014 Ford Fusion

Ford – Manual selection – USA – Fusion – 2013-2018 (IT’S 2014)

otosys-im600-ford-fusion-2014-3

 

otosys-im600-ford-fusion-2014-4

 

otosys-im600-ford-fusion-2014-5

 

otosys-im600-ford-fusion-2014-6

 

otosys-im600-ford-fusion-2014-7

 

otosys-im600-ford-fusion-2014-8

 

otosys-im600-ford-fusion-2014-9

 

Otosys Im600 started to add a remote

(the same as Otosys IM100)

Blade key – Immobilizer (CAN) – Add keys

otosys-im600-ford-fusion-2014-10

 

otosys-im600-ford-fusion-2014-11

 

otosys-im600-ford-fusion-2014-12

 

Had to learn and erase keys before add a new keys

otosys-im600-ford-fusion-2014-13

 

otosys-im600-ford-fusion-2014-15

 

otosys-im600-ford-fusion-2014-15

 

otosys-im600-ford-fusion-2014-16

 

otosys-im600-ford-fusion-2014-17

 

otosys-im600-ford-fusion-2014-18

 

otosys-im600-ford-fusion-2014-19

 

otosys-im600-ford-fusion-2014-20

 

Failed to learn keys…

Then tried again

otosys-im600-ford-fusion-2014-21

 

otosys-im600-ford-fusion-2014-22

 

otosys-im600-ford-fusion-2014-23

 

otosys-im600-ford-fusion-2014-24

 

otosys-im600-ford-fusion-2014-25

 

otosys-im600-ford-fusion-2014-26

 

otosys-im600-ford-fusion-2014-27

 

otosys-im600-ford-fusion-2014-28

 

Success! Managed to learn keys: 2 and programmed a new key

Now keys: 3

Job’s done!

If you interested in Auro IM600,pls contac with:

3. Skype: obd2express.co.uk

4. WhatsApp: +86-18750906257

 

Who Like This Article Also Viewed:

18/09/2018

How to use VXDIAG Nano GM solve ‘Service Active Handing’ warning

This is the most cost-effective way for ‘Service Active Handing’ warning to pull such codes right out of the box.

 

Will work right out of the box without a GM subscription, since the GDS2 version you get with it, does not connect to GM, so the “VM” GDS2 program does not need a GM subscription to work.

So with it, it will give you the DTC codes to begin with, and you can go into the code directed modules to check them to see what the problem is, what needs to be replaced or corrected.

So once you have GDS2 running and the GM Nano connected to the car and PC, step one is to go into to vehicle diagnostic, and use read vehicle wide DCT and id information. This will list the Dtc to start with.

Now back out of that menu, and go into module diagnostic, and depending which module the DTC code pointed you at, go in that module to read it’s data/trouble shoot the problems.

Again so long as you don’t need a brand new module that will need to be initially firmware vin flashed to lock it to the car, or need to get into a security menu to say learn a fob into the car (both part of the SPS program, not the GDS2 program), you don’t need a subscription to GM.

If you do need to use the SPS program, then you can get at least a three day subscription to GM, and it will load the needed subscription locked programs to your computer as you use them (your VM GDS2 program will be locked away in it own little folder safe, independent of the programs that the subscription programs that will be downloaded to your machine, and will only work while you have an active subscription to GM).

Really, check around in your area to see Who has a Clone MDI with Vm GDS2 to give you a hand. This will not only give you chance to see how the device and GDS2 is used, but will make short work of figuring out the problem of the car. Trust me, once you see the what GDS2 can do with the car, you will want it for yourself as well.

On the Corvette C6’s, by going through just the voltages of each module, I can tell where there is a electrical problem, before the problem causes a lose of communication down the line instead.

Hence if the ECM has a voltage of 14.3 with the reast of the modules , yet the RCDLR has a voltage of say 13.4V, know that there is either a bad connection to the module, ground point problem, or that the board has a cold solder joint that needs to be re-soldered; before it starts to cause DTC problems isntead.

On the F55 module, again a snap to catch problems before they happen to start throwing DTC codes, since I can check ever sensor for it’s voltage too. Hence say three of the level sensor are reading 2.1 volt, but one is reading 1.2 volts, you know it has a problem that needs to be resolved before it causes DTC codes next.

VXDIAG Nano GM obdexpress.co.uk

 

http://www.obdexpress.co.uk/service/how-to-solve-service-...