topblog Ivoire blogs


How to use digimaster 3 to change the mileage of Toyota

Digimaster 3 also is called Digimaster III with 1080 Tokens or shortly D3 is new developed odometer correction master. It works with various types of adapter you can easily achieve odometer correction, Audio decoding, airbag resetting, engine ECU resetting, IMMO, programming key for Benz &BMW etc.

Here is the detailed instruction for how to use digimaster 3 to change the mileage of Toyota.

1) Find the basic information about the mileage changing.

2) Now the car you want to change the mileage is Toyota camry, the cable you need to use is OBP adapter. Find OBP adapter in toolbox then choose meter system.

3) choose Japan&korea

4) choose "Toyota"

5) choose camry

6) Now screen is shown C46, then it means you need to move the dash board and find this C46 chip. (When you use this digimaster 3 to change the mileage for other cars, you see the same prompt like this, it means you need to find the same chip the menu prompt)

This remind you the place of this chip. The chip is dip 93c4, fidn this chip, and deal with this chip, make sure that chip pins should not be short-circuit or the pin is damaged.

This is the 93c46 chip moved from the board.

7) Inset the chip and connect OBP rightly (pay attention the direction of 93C46 chip)

8) click next step, read the mileage of this chip (mileage of this chip is 80KM), and choose "Yes" to enter mileage changing.

9) directly input the mileage "4567km" and click "OK"

Information is successfully writed.

After you change the mileage, read the mileage and check modification is consistent.

confirm the mileage you changed is 4567KM.

More information:

07:02 Publié dans Blog, Shopping, Web | Lien permanent | Commentaires (0)



INPA error IFH-0009 No Response usually means a break down (or lack of) communication between the vehicle itself, and the laptop. More often than not, IFH-0009 errors in INPA are caused by the following reasons.

The hardware for INPA can be:
EDIABAS OBDII interface;

1) Poor quality, or incorrectly wired interfaces. IFH-0009 errors are the most common in D-Can+K usb interface leads. Often these low-quality can be badly constructed, incorrectly wired, or contain the wrong chip set drivers or come with no drivers at all!. Whilst not all Chinese interfaces are poor quality, buying cheap imported leads is a gamble and when problems occur the seller probably won’t be interested. It is therefore important that you buy an interface lead from a good quality, reputable Vendor.

2) Wrong or Incorrect Interface Drivers. Again, mass produced interfaces can often contain cd’s with the wrong chipset drivers or come with no CD at all. Without the correct (latest) USB drivers, your interface lead will not install under windows properly. Our software package comes complete with a popular driver which is compatible with most Chinese and Western produced USB Interfaces, which will often work if the one supplied from your interface lead vendor doesn’t or hasn’t been included.

3) Incorrectly configured interface lead. Again, one of the most common problems with USB type leads. When installing a D-Can or Usb Interface lead, you will need to reconfigure the Windows based com port settings, so that the USB lead, appears to replicate an old RS-232 serial port. To replicate the port correctly, you need to change the existing Com port setting of the USB interface within Windows to Com Port 1 and change the latency setting to ‘1′ and check any ‘Fifo’ box

4) Incorrectly wired interface. Once again, there is no set standard as to the wiring pin configurations used within D-Can + K interfaces, by the various manufacturers. Some interface leads have pin 8 disconnected, some have pin 8 physically linked (bridged) to Pin 7, and some have pin 7 & 8 connected individually with no bridge link. If you still have problems connecting to the vehicle, and still get ‘IFH’ style errors then you should open the OBD Socket of the lead and check the pin wiring to see which type of interface you have. You should consider trying your interface lead, with the following configurations….

i) Pin 8 joined to Pin 7 using a small wire link

ii) Pin 8 physically disconnected

iii) Pin 7 and Pin 8 individually connected to their own pins with no link.

More often than not, one of these configurations will work with your vehicle, I recommend trying it with pins 7 & 8 linked together first, as this is by far the most popular vehicle configuration.

Also don’t assume that once you have found the pin 8 solution which works with one vehicle, that it will automatically work with a different model. If you have more than one D-Can equipped vehicle, you may need to obtain a second interface lead and configure ‘pin 8′ differently.

If you don’t own a soldering iron, or if you don’t feel confident about soldering electrical connectors, then there are adaptors available which will bridge pins 7 & 8 together, without any need to open the OBD socket or solder.

5) Incomplete Versions of INPA. There are many versions of Inpa around, many of which are incomplete or simply lack the various configuration files in which to work correctly. If you try all of the above and the IFH-0009 problem still remains, then you will need to consider buying and installing the full version of Inpa which includes Ediabas and BMW Standard Tools

Real case solved by one of solutions above:
1. I have a 2004 325ci

2. I purchased the ebay cable here. It is an under-the-dash OBD to USB cable.

3. It came with what was described as INPA 5.02 and EDIABAS 6.4.7. You have to install BMW Tools first, and then update. (Updating INPA, it shows a check mark next to INPA 5.01 "update," and loading INPA, it says version 5.00 at the top bar.) I also installed NCSExpert.

4. I am using windows XP SP3 32 bit. Firewall disabled, no anti-virus. No other software is installed. (I've had the same problem using Win 7 and Vista).

5. C:Ediabasbin is in the path.

6. Installed the USB cable and set the COM port to 1. Latency is set to 1ms. There is no option to use FIFO buffer.

7. Ediabas.ini has STD:OBD as interface. It is also set so loadwinxp = 1

8. OBD.INI is in C:ediabasbin and system32. COM port is set to 1 and hardware = USB (when hardware = OBD the battery circle is black even when not plugged into the car).

9. When loading INPA, I get black battery and ignition when plugged in and starting car.

10. I can successfully read the ECU. I can read and clear errors.

11. When trying to read any other module, I get the IFH 0009 No Response From Control Unit.

How to solved:
I took about the connector and pins 7 and 8 are indeed soldered together!

I verified that both pins 7 and 8 had voltage and that the connection from the chassis wires to the obd plug under the dash were solid.

I then looked closely at pin #8 on the OBD/USB wire and noticed that it was bent slightly. It was not lining up in the pin #8 slot! I straightened it out and it worked!

07:07 Publié dans Blog, Shopping, Web | Lien permanent | Commentaires (0)


Ford IDS works well on Windows XP, 7, 10,VMware, iPhone...

Hi, all IDS users. Ford VCM/ VCM2 software nowadays, you know, has been tested by some vcm users that IDS can be worked fine on almost laptops with different operation system, and even iPhone mobiles.

IDS V94 works well on Win 10:
My IDS is still working fine on windows 10,
IDS was installed on the panasonic toughbook i5 with windows 7
then the laptop got the upgrade to windows 10 with no reported problems,
this laptop is full of my everyday crap and i never turn off the security when i connect to van.
maybe i’ve just been lucky as i don’t know to much about computers,
all the bosch stuff is there and calibrations .
i accidentaly updated to the v94 once from ford then system restored the laptop to previous setting
and it ran saying it was v94 with no problems with licence or anything

IDS V97.01 works well on W10 Pro 64bit:
I have IDS V97.01 working with W10 Pro 64bit 

IDS works well on Win 7 family:
I had it working fine on my old works w7 machine but had to give that one back,  Got it on my own family w7 one too and no probs, and now got another w7 one for doing my own work stuff and looking to upgrade to w10 but holding off just now.

IDS V86 works well on Win 7 64 bit:
I tried to run a native copy of v86 using the same VCM, but directly on win7 x64
No problems, everything works sweetly.

IDS works well on Windows XP:
My ids is on an old shitter with xp and I don't let it connect to internet 

IDS V90.01 works well on VMware running Win XP PRO:

The VMware image works nicely, it includes a patched version of ids v90 running on xp pro.
However, it wants to update the firmware in my vcm2 so i'll try with v86 before doing that. I don't want to brick the vcm2 so it won't work with ids v86

IDS V86 works well on iPhone mobile:
For all I use it really, I'm quite happy just running v86 on my iPhone.
Fast enough and hardly any problems.
 get an IDS app


06:46 Publié dans Blog, Shopping, Web | Lien permanent | Commentaires (0)