Car model: BMW 120i e87 2005

Symptom:

Engine management light showing error P0365 bank 1 sensor B which I know is the camshaft sensor for the exhaust side.

Tool I used:

Autel MaxiSys Pro

What I did:

Recently changed the part and the code returned about 10mins after I started the car and now is constantly on regardless how many times I clear the code. Swapped over the sensors from the inlet side and the code remains P0365 exhaust side. I’ve already checked the wires ports and plugs and even ran a continuity test from the plug down to the ECU to see if there was a break in the connections which there isn’t. I did a test to see if I am receiving a signal to the ECU and I am with various voltage changes on my multimeter. Ranging from 12v all the way to 4.5 but not any lower and is rapid changing, however considering that the engine was running on not manually rotated makes this understandable.

Very little amount of oil in the plugs regardless I cleaned them with contact cleaner and compressed air and by plugs I mean the exhaust sensor. I took the time to check all other plugs including the vanos solenoids and the inlet cam sensor. The DME had no oil, all looks good. I was using an Autel MaxiSys Pro device at the time to scan the codes.

In other news, I decided to rip of the rocker cover and hey hey, top guide was broken for the chain so I decided to get myself the kit and and equipment needed and did the timing chain job over the week and all is well in that section. I did check the timing and everything to align the timing slides on perfectly so the timing wasn’t out however…..

Once I started the car for the first 10 seconds no exhaust camshaft error but It returned immediately after this and now will not go away again.

Other diagnostics I have now done:
– borrowed my friends carly device so I can monitor live data on the move whist screen recording which I hope you guys can help me crunch. The live data shows an accurate representation of my inlet and exhaust camshaft position which proves its definitely not the camshaft sensor or wiring at fault here. Both are inline with the strokes of the engine when manually rotated as well.
– swapped over the disk which the camshaft sensors take a reading off as they are exactly the same according to the BMW manual I was using and the same error persists.
– over head inspection of the stem of the valves not displaying any issues
– compression test ( why the hell no, I was lost and just kept diagnosing) #PASS

***** forget to mention, on the carly device I get a input and output camshaft sensor reading in degrees. The inlet sensor moves from 120 degrees down slightly where as the exhuast camshaft does not and stays fixed at 120 degrees permanently, any idea what this means or where I should be looking.

Finally! SOLVED……

I removed the exhaust camshaft pulley to effectively check the condition as I had the snapped timing chain guides. What I think had happened was the guide plastic pieces may have gotten trapped where the cam teeth are and knocked it out of alignment internally which the engine was running obviously at engine running revs. This in turned caused the pulley to be wedged internally. This was diagnosed by very literally disassembling the pully using all the incorrect tools.

The screws required to disassembling the pulley are a 5 point star shaped bit which I did not have access too, and neither could find anywhere in DIY stores or automotive. However nothing some serious force wouldn’t solve with a little custom tool also known as grinding down a larger torque piece till it fit. Anyways disassembling was diffeficult as was re assembly, nothing replaced but just wedged components where the spring was. The same pulley was then placed back into the car and tested and lord behold rotation was occurring, camshaft senor error was gone.

P0365 also known as camshaft bank 1 sensor B can be cause by the pulley being damaged and is worth while look into, I can’t find an effective test to conduct on the pulley but they are available online new/used and should be changed.

Tips for anyone with the same issue

1. Pull up live data on a OBD reader which allows you to test and check if the DME is receiving data from the camshaft sensor and check for the degree of fluctuations within the camshaft pulley which idles at 120 degree.

2. No rotation or no signal will give a more accurate representation of where to look. Should only 1 VVT pulley be moving then you know the issue is the pulley not the motor.

Credits to @ Jr940.

Autel MS908P Details:

https://www.uobdii.com/wholesale/autel-maxisys-pro-ms908p-diagnostic-system-with-wifi.html

The post BMW 120i E87 camshaft sensor p0365 with Autel MaxiSys Pro appeared first on UOBDII Official Blog.

Car model and year:

2007 ML350 186k Miles

Symptom:

Had 56 DTCs and a leaking crankshaft seal

Benz scanner to use:

Went through the DTCs and most were typical BS transient ones or very old ones, I deleted them with my scan tool (Launch X431 ProS Mini), and only a SRS one returned in 200 miles of driving.

What I tried to do:

attempted to replace the OEM type seal that was flimsy and that didn’t lend itself to insertion by conventional means (tapping it in and home with a soft-faced dead blow hammer) without buggering it up (as he did). But at times maybe I bury the facts under superfluous information.

Went to start the seal w/ a hammer, then used the factory crank bolt, a nut, and a BIG washer against the seal to press it in.

Please follow all the instructions:

Understand that the bolt calls for a high tightening torque.
Please follow all the instructions to a t. If you do not, your engine will be damaged.

R&I Crankshaft Pulley 272 Eng. #1.pdf

https://mega.nz/file/9cQQBaqJ#OxhBDh76xhgEs2ZPIMuO65pHh5ojBR8oMGEsZGNSg2o

R&I Crankshaft Pulley 272 Eng. #2a.pdf

https://mega.nz/file/oBAG1CbR#2TREvpXaKQhkeUlaQvZm7iHIyw7EvAYO0gqqkXPK8tk

R&I Crankshaft Pulley 272 Eng. #2.pdf

https://mega.nz/file/0BRGwCAR#LJQmZ42Mcru0gPyzLyVPZHEpsmwH9zsDyKDOzEbZnYk

R&I Crankshaft Pulley 272 Eng. #3.pdf

https://mega.nz/file/wRBUgYLI#C5POGz_t9Rsd0MnLzNeMp72fhWcTeKgDFmHFnzO6WGw

R&I Crankshaft Pulley 272 Eng. #3a.pdf

https://mega.nz/file/NJRyGIYA#qy40afvPU-LjRUyYEqL2rTtplIHTDarFdXP3HuxYfrM

R&I Crankshaft Pulley 272 Eng. #4.pdf

https://mega.nz/file/hRBkRYZB#KIpstxVchzndTn1Fsc1mNlU7cMalY1bwM1D2npZ5GYQ

Finally! The leak is stopped!

The proper harmonic balancer holding tool was purchased and used for bolt/pulley removal.
To remove the bolt, a socket with a 1/2″ breaker bar and a 5ft pipe was used to loosen bolt. (I was amazed the 1/2″ didn’t break)
The illustration in my post was the method he used to insert the seal once it was started using the bolt and washer to suck it in.
A torque wrench was used to achieve 200ft/lb, and an angle gauge between the breaker bar and the socket was used for the final torque (Though 350ft/lb +/- 50 using
a 5ft extension pipe and a spring scale hooked to the end of the breaker bar and pulled to 70 pounds on the scale should be adequate with Blue Locktite on the threads
as was originally found on he threads was found elsewhere as an ascetical gouge.)

That text should have read 150ft/lb, not 200ft/lb (the 150ft/lb he used is close to 147ft/lb or 200mn– Actually 150 ft/lb is 202nm actually) plus 90deg w/ Blue Locktite

The “200” came from what he told me and I should have gotten the units (nm) right by typed ft/lb from habit.

The 1/2″ torque wrench I loaned him only goes to 150ft/lb, and he set it to 150. there is tolerance with everything and 2.2nm off is no big deal, especially given torque wrenches have tolerances
and mine has been well treated but not calibrated since new.

The leak is stopped.

Hope it helps!

The post 2007 ML350 leaking crankshaft seal fixed with X431 ProS Mini appeared first on UOBDII Official Blog.

I bought a £60 used Win 10 Tablet/Laptop, installed Virtual Box, installed his image, got a mongoose cable from the OBD Shop (that arrived in 2 days), plugged it in as per the following instructions, said yes to the new hardware box for the mongoose, all OK, started SDD, stumbled around a bit then programmed the injectors, read the codes back and all good.So once again thank you ever so much for making this so nice and easy!

Credits to @TheMindBuddah instructions blow:

The reason we use XP for the VM is because it was built for Windows XP, and as you have experienced browser based.(this is the reason it is slow, not the OS). You will not get the mongoose drivers to work (or SDD) under windows 10. The two systems are totally different at the core. You can install natively on windows 7 under XP compatibility mode. But as a VM your just increasing the workload on people’s systems running two OS’s on possibly older hardware. This is why XP is a better OS for a SDD VM.

(There are trimed versions of Windows 7 that you could try to save space, but I’ll leave that for you to try)

SDD 130 is known to have issues with IDS and that is the reason most garages kept IDS 125 when dealing with the older cars.

Every case off issues from my SDD not working has been from the User. I really don’t know how I could have made it any simpler? Everything is there from auto flashing of mongoose firmware (one off, if not the biggest issue i found with connection issues was because off new cables being loaded for SDD 145)

Both 130 and 138 work well for what they are. Free and garage level diagnostic software in an easy to use package that many people have been using for up to 2 years before I posted here including myself.

IDS 125 as stated was just made into a VM. Any crashing could well be inherited from the software, VM or natively it could well be the same.

“Additionally, setting the date works without dependency on host OS, so that is a big plus. It is annoying to have to set the clock on main machine due to limitation VirtualBox.”

There is a Auto Bat file that sets the date automatically installed in my Image for version 130. Look in the \Documents and Settings\<User Name>\Start Menu\Programs\Startup folder (been a while!). Its just a text file! Open it up in a text editor and see how easy it is to auto set date and time!

“The WinBox installation you provided seems like it doesn’t have IDS installed at all, as it doesn’t start.”

SDD 130 is known to have issues with IDS and that is the reason most garages kept IDS 125 when dealing with the older cars.

“I also tried v156, and it worked fine”
The issue with later versions is that JLR realized that if all the needed files to do high level changes and repairs to your car were included in what could be possible hacked versions of their software. So that is why the most important files for programming are download as and when needed. Justifying the paid monthly subscription. I think 138 was the last version where everything was contained in the complete install.

“I am just playing with VmWare image IDS and the CPU is working at about 5%, idling essentially.”

Now that is interesting. Have always used Virtualbox so not tried any other VM software. Is this with a modern CPU or something a little older?

“I could post VMWare image online for you to try?”
Unfortunately don’t have much call to use SDD that often, but post to the forum (With warnings its a work in progress and you take no responsibility if anyone use’s the software!). Let people test it in real work environments as more options is better than just mine. They will give you feed back and help to improve it.

Land Rover & Jaguar JLR SDD VMware Images Download Free:

https://mega.nz/#!dFVF3CqD!wPsCBxQWmAhkgumPkqSCEImJ4GTDTiRc1vOXkDRgWi8

Activated, not tested with interface.

Please use Vmware 15 , when open first time click I moved.

VMware v15 download:  https://mega.nz/%23F!5Zsw0KLI!GI88kqwLmRJo8iiOA4i0FA

Latest vmware 15 pro with activation included.

Free for all.

The advantages are simply that you don’t have to spend hours installing on old past their prime laptops with dodgy batteries liable to die while your flashing something on your car. Also i have included Mongoose toolkit in the VM that will auto flash the correct firmware into your cable for the version of SDD your using.

These can be ran on any system that can also run Oracle’s Virtualbox. That includes Windows, OSX and Linux machines. You don’t need a particular beefy laptop either.

How to install JLR SDD VMWare image?

1. Install your version of Virtual-box. Virtual-box for Windows PC or OSX for Apple Mac
2. Go to file and Import Appliance and select one of the two images you downloaded
3. Sit back, maybe put the kettle on.
4. You can now if you want, right click on the image and create a clone. So you have a backup.
5. Double click the file that now appears called WinXPJLR 130 or WinXPJLR 138 (which ever one you used). It should now load up windows XP in a window2. How to use JLR SDD in a VMwarea. You should now have a window running XP. If you are using Version 130. A black window will appear. That is the auto script to set the date and time to 01/08/2012 each time you start it. It needs that date for the password and account to work. Just click in the black box and press a key.
6. Any windows boxes that pop up to search for hardware. Just cancel. Its looking for the drivers of hardware you don’t have. Ignore.
7. Plug your mongoose into the car and the other end into the laptop. Turn the ignition of your car to position 2. Go to devices on the top of the image, USB and select the mongoose. Should be Drews!
8. Now one of two things will happen. It will automatically detect the mongoose and update the firmware on the device or not. If not then double click on the icon for Mongoose JLR Configuration.

You should see your mongoose in the white panel in the configuration menu. Select it and flash firmware.

(It will send the right firmware to be compatible with the version of SDD you are using. If you use a different version of SDD. It will flash whatever one you need)

1. Now if you want to you can change the resolution of the virtual XP just like normal windows. I have set it at a low 800×600 so it is compatible on everyone’s screen resolution. So right click on the window and adjust to your own laptops specifications. If you press RIGHT CONTROL BUTTON and C for scaled mode or RIGHT CONTROL BUTTON and F for full screen mode.
2. Now double click on JLR SDD. It should now load up Internet explorer (yes it is browser based!!). If it fails to load, close the browser and stop the application. Double click again Jaguar SDD, and it will load.
3. If you are confronted with the password screen only with Version 130. Which sometimes happens? It is below

(Also there is a password.txt on the VM images desktop with it)

USER ID – JLR9A8172

Password – L538X760

Then press identify

1. You should be now confronted with the vehicle identification number (VIN) screen. If read is greyed out. Then your mongoose is not talking to the car.

Is it plugged into the car and laptop?

Is the car ignition in position 2?

Did the mongoose configuration tool flash the firmware?

Did you activate USB in the image?

If you followed all my steps to the vehicle identification number (VIN) screen. The read option should be coloured. Select it and it will retrieve your VIN, and then you’re on your own adventurer! Good to know: it’s risky!!!

Enjoy!

The post JLR SDD 156 145 138 130 win XP / 7 /10 test reports + guide appeared first on UOBDII Official Blog.

Guide to Read EEPROM Chip Data by Xtool X100 Pad 3, It need to work with Eeprom adapter. Step by step as the following:

XTool X100 Pad Elite (Pad 3) Review and Unboxing

Connect the Eeprom chip to the Xtool x100 pad3 eeprom adapter, and then connect the main cable. connect the power supply, be sure to connect the power supply adapter before operating.

Enter Xtool X100 Pad3 main interface, click diagnosis then click other service.

Choose eeprom adapter, choose eeprom program

Choose eeprom chip model then read eeprom data.

Name the data file and save it.

Back to Xtool X100 Pad3 main interface, You can check the the file in Report—File management—adapter.

Xtool X100 Pad 3 Read EEPROM Data Video:

The post How to use Xtool X100 Pad 3 Read EEPROM Data appeared first on UOBDII Official Blog.

Xtool X100 Pro2 key programmer supports online update to have the newest software version. Please follow the next parts to upgrade in step by step.

Browse http://www.xtooltech.com/, click on “Supports”, then “XtoolPro2”, start to download “TP200Installer_v1.0.1.5.rar”.

Finish downloading the software, start to install.

Xtool pro2 connect to computer with usb cable.

Open “TP200”, input the S/N and password to login.

For the S/N, please open Xtool pro2, enter “Options”, then “About”, then you will see the login password and serial number.

Select All car makes, then click on “Upgrade” until success.

Note: if you can’t choose the model after logging in, it means that your software is already the latest version and no need to upgrade.

You are free to reset any of the following languages and click on “upgrade”:

English, Spanish, French, Portuguese, Deutsch, Russian, Polish, Italian.

Job is done.

XTool X100 Pro2 Update Video Guide:

More Xtool X100 Pro2 key programmer Details:

https://www.uobdii.com/wholesale/xtool-x100-pro2-auto-key-programmer.html

The post How to update Xtool X100 Pro2 key programmer? appeared first on UOBDII Official Blog.

Digimaster 3 Digimaster III  Odometer Correction Tool FAQs:

Q: Can digimaster3 change kilometers to 2009 Mercedes CLS 320 CDI (facelift model)?

A: Yes, via OBD. Select CLS Class->W219-2011 option to do.

Q: Does it need filter to adjust mileage for Benz w212 by digimaster 3?

A: Yes, it needs. The filter is disposable, and one filter only can be used for one car. You cannot remove it once installed.

Q: I want to correct odometer for 2010-2015 and 2016 Mercedes Vito ezs, does digimaster 3 support this car till 2016?

A: VITO belongs to 9S12, it’s supported by digimaster 3.

Q: Can I adjust mileage for the following cars by digimaster 3? Need filter?

ML164 and ML166 also bmw X5 E70 European and American models.

F 15 American models

A: ML164 and ML166 belong to Benz, can use digimaster 3 via OBD

BMW chassis F15 belongs to FEM, should use ACDP instead of digimaster3

bmw X5 E70 belongs to CAS3, D3 supports

Q: Does Digimaster 3 support 2015BMW X5 odometer correction?

A: No, it belongs to FEM type, digimaster3 doesn’t support. You can use Mini ACDP.

Note: BMW F series have CAS4 and FEM types, if it’s CAS4, digimaster 3 is ok. If it’s FEM, Mini ACDP is ok.

Q: Is it possible to reset mileage for 2010 lincoln mkz by digimaster 3?

A: Yes.

Q: Will digimaster 3 correct odometer on a 2007 ssangyong actyon?

A: Yes, the 93C56 chip is supported.

Q: Does Digimaster 3 support 2013 Audi A6 mileage adjustment?

A: Audi A6 till 2012 is supported, but year 2013 is not supported.

Q: Correct odometer for 2002 Audi TT, digimaster 3 can?

A: Yes, select the TT-2009 option and adjust via OBD.

Q: Can Digimaster 3 reset mileage for vw passat 2017 TDi? and 2016?

A: it doesn’t support 2017 passat so far. For year 2016, you should dismantle the dashboard to check CPU model, some are supported.

Q: Can I adjust mileage on my VW Passat 2015 with digimaster3?

A: Yes, via OBD.

Q: Does digimaster 3 adjust mileage for 2008 Nissan Pathfinder via OBD?

A: No, you need to dismantle the dashboard of Nissan

Q: Can Digimaster 3 correct odometer for Infiniti fx50 2009?

-Yes, it can.

Q: MG 6 Tse 2012 model odometer correction, is digimaster 3 ok?

A: Yes, but you should check the chip type. If it’s 35080 chip, you need to adjust via dashboard and BCM.

Q: I use digimaster 3 to adjust mileage for my Honda Odyssey, and it prompts “Write data succeed!” Does it mean correct odometer successfully?

A: Yes.

Q: Does it support durango 2018 odometer correction?

A: desolder dashboard to check chip type, the 8 feet chip is supported.

Q: Digimaster3 adjust mileage on a Peugeot 308 1.6 hdi 2008/09 via OBD?

A: No, Peugeot is not supported via OBD. You need to dismantle dashboard and BSI

Q: 2015 chrysler grand Cherokee mileage adjustment with digimaster3?

A: It needs to dismantle dashboard. 93 series storage chip is ok.

Q: 2013 Prius, 2008 Toyota Tundra, 2016 Nissan Sentra?

A: Yes, digimaster 3 supports.

Q: Does digimaster3 support Toyota RAV4 2018 Fujitsu mb91f060BS cpu odometer correction?

A: Yes, it does.

Q: Will digimaster3 adjust mileage on Subaru WRX 2015-2019? And 2020?

A: 2015-2019 is ok, but for year 2020 Subaru, it needs to dismantle dashboard, as long it’s not CPU is ok.

Q: How about Mitsubishi Colt 1.5DID 2007/2008?

A: Yes, Digimaster3 supports.

Q: Mitsubishi 2008 lancer evo mileage adjustment? Digimater 3 can?

A: Yes, it needs to dismantle dashboard and chip.

Q: I have 2019 Ford F250, holden / gmc acadia 2019 model and Ford Fiesta 2018, can digimaster 3 adjust mileage for them?

A: No, these car models should be encrypted CPUs and cannot be supported.

The post Digimaster 3 Odometer Correction Tool FAQs appeared first on UOBDII Official Blog.

Question: now I need to change the engine ECU on it. Engine number n45b16a, need to syn cas module with engine ecu, ISN code from cas module to engine ecu, how to proceed it with Yanhua mini ACDP?

Answer:

This ISN is BMW N45 (ME1721), Yanhua mini ACDP is able to do, please prepare:

1) Yanhua Mini ACDP basic module, $159

2) Module3 + authorization, $179

3) BMW DME adapter X8, $34.99

Yanhua ACDP BMW-DME-Adapter X8 Bench Interface Board for BMW E chassis N45(ME1721)/N46(MEV1721) DME ISN read/write and clone. No need to open DME shell, no need to drill hole on DME, no need to plug wire.

Procedure:

Please enter “BMW” -> “DME ISN” -> “Bench mode read /write DME ISN” -> “Exx” -> “N45 (ME1721)”

Question: I have got the isn from the new ecu, and now I need to get the isn from the cas. I got it through obd. I can read the eeprom file icp through the bench mode, but I don’t know how to reverse write the isn from dump/file.

Answer:

ECU cloning is to read the data of the original ECU and write it into the new ECU. The reading and writing interface is the same.

Yanhua Mini ACDP Device and parts:

https://www.uobdii.com/producttags/yanhua-mini-acdp.html

The post How to read write BMW DME N45 ISN using Yanhua Mini ACDP? appeared first on UOBDII Official Blog.

Have 2013 Hyundai i40, the key starts the car, put the buttons don’t work, so I’m going to use the OBDSTAR X300 PRO4 to program the key.

Put into the OBD port.

Select from vehicle.

Europe.

i40 is here.

I can “Select from type”, then “Remote”.

16pin obdii connector.

Type 1.

Program remotes.

It says “Switch ignition on and then switch ignition off and remove key, press ENTER to continue.

Press LOCK or UNLOCK for more than 1 sec.

Program success, whether to program next one?

Press [Enter] to continue.

Esc and it displays ” Program complete”.

Power off OBDSTAR X300 PRO4.

Unplug the OBD2 cable and to test the remote.

You see it is working

Okay, very good programmer OBDSTAR X300 PRO4.

The post OBDSTAR X300 PRO4 programs Hyundai i40 remote successfully appeared first on UOBDII Official Blog.

Credits to all DK members who shared their Autel IM608 key programmer test reports on what work and not work.

Autel MaxiIM IM608/IM508 Key Programming Guide

Autel IM608 success:

2013 Volvo S60
Add proxy key success
remove KVM & CEM
read on bench
renew locked used key with xhorse key tool
add key via obd with bench data
45min job start to finish

2. My autel im608 is great! Really enjoy the Volkswagen programming functions, and it has some decent scanning abilities as well. looking forward to where they go in the future.

3. Using IM508 , good tool for VW MQB and BMW FEM and BDC programming
4. Toyota smart key AKL, 2000 E320 W210, on bench, 13 minutes. fd’s done on bench.

5. Mercedes EIS passwordcalculated successful by Fd.

6. BMW x5 Diesel 2015 BDC key program, fast, super fast

7. Jeep Compass 2018read pin and programmed proximity key 5 min job

8.

Autel IM508
last 3 days:
Fiat Grande Punto 2006, success, read PinCode , instant pin code calculation
Alfa Romeo 147 2007, success, read pincode after reading eeprom (10min)
Skoda Octavia 2007. success , read pin code , read dash eeprom

Success – Programming Freelander ’09 Key insert module.
Took 5 minutes after spending hour pissing around with JLR dealer kit. LOLs this game

10. Yes I confirm this also. No problem using a mobile phoneto get internet access on the IM600/IM608. Never had a problem with this.
11. 2019 Honda CR-V proxy
    Add key 2 minutes
12. so far ive been impressed with im608, like us every tool has an off day , but so far its done all I’ve thrown at it , to the point il try it on a lot more that I normally use other tools for . I’m sure at some point it will fail on something it shouldn’t , all do , but so far its proven to be a worthwhile addition
13. First Mercedes with my im608.. 2012 sprinter instant calculation2 minute job max.
14. Toyota verfire key programmed and Nissan ignition fault identified ..

15. Had this tools a couple of years now. Autel IM600, bought when it was totally new and unknown. And almost no one sold.
    So the price was lower for a short while, at that time. So I took the chance.
    With updates it’s getting better.
    But at the beginning, I wasn’t that pleased with it.
    But it has saved me a couple of times, when no other tool I have would not do it.And also,it’s nice to have a good diagnostic tool as well.
    That means something, it’s a must in this business.
16. 2010 VW golf add key success, add OEM remote success.
17. AutelIM508do BMW f series keys and Mercedes keys with xp400.
18. Done first Merc today with 608
    2002 C-class W203 spare key Read password through IR in 2 minutes as experiment went back in through working key in EIS calculated pin in under 5 minutesWhile in there popped boot to see if function worked through OBD

    This will be tool of choice for MB spares and use VVDI for AKL

19. Mercedes W209done on bench as a test first calc 35mins 2nd try 10 mins
    Lot of cables to connect to do these

For AKL MB is better to have G-BOX.

20. Pulled immo code on 2006 Jeep Cherokee
    and added key in 2 minutes
    MVP, Xtool pad, Obdstar, SKP900 and everything else I threw at it wouldn’t pull pin
21. Autel IM608 is capable of doing cas4 through obd if you have a good battery support. And they’re close to release Vauxhall Vivaro 2016> akl obd, they’ve done a successful test a few weeks ago
22. . I have my hopes for the BMW software. Which is primarily what I fell into.The coding software on the diag side isn’t horrible but it isn’t great. It’s user friendly but doesn’t let you get crazy. I don’t have BMW explorer or autohex just because they are huge money and it was easier to meddle my way through the German.ISN reading has gotten better and faster.

    If you go into restore flash over obd you can see they have a straight ZUSB reflash under development.

    And it does have the j2534 that I’ve had really good luck using with standard tools, even if it took a lot of long nights getting setup.

    Not bad for a tool I bought to read pin codes from chyslers.

    The xp400 pro is under dev that is supposed to have even more functionality. The apb113 for pcfxxxx like what vvdi prog has. Hopefully the gen 2 will unlock the pin code reading function in the xp400 windows software.

    I imagine autohex or explorer will give you the ability to read working hours or powerclass without having to go to standard tools. Or change UIF entry without having to use a hex editor.
    Those are other things that the IM607 could definitely take advantage of.

    But to what I think your point is, where does the scope of what a key programmer should need to do to be viable. I already feel like it goes above and beyond. If you are programming a key, why would you need to change CAS ISN, or write ISN in boot mode, and backup flashes for DME and such things.

Autel IM608 failure:

1. Autel IM608 wouldn’t program a Renault master 2015 wouldn’t read pin, Lonsdor K518Sand RET programmed ok.
2. bench mode reading the isn of msd gives security error now (Yanhua mini acdp+ module 3+ Bench interfaceworks)
   trying to get that fixed lots of logs ive been sending and talking to support
3. Failed – Volvo XC60
   – once found file it read … says module can’t be deciphered.
4. I have Maxisys Elite, when doing newer cars . It doesn’t have parameter reset even with IM608
5. Skoda Superb 2011….
   Left laptop at home so –
   IM608- kept saying failed then reported no internet. Went into advanced option and same
   SmartPro – Crashed so gave up. Coded remote as always on VAG.Ended up cloning using VVDI2hand tool – FUNNY internet access succeeded where IM608 didn’t.
6. Done a few Mercs now very impressed. Yes its good for add key but if calculation is longer than 20 minutes don’t waste your time – do it on bench or use other tool. Totally agree use im608for spare keys AKL on bench with VVDI Prog& VVDI MB.

To be upgrading…

The post Autel IM608 key programmer reviews success & failure appeared first on UOBDII Official Blog.

XTool X100 Series Key Programmer includes basic handhold key programmer X100 pro and the update version X100 pro2, also has latest all-in-one key programmer Xtool X100 pad, pad2, pad2 pro, X100 Pad3. What’s the different and how to choose Xtool x100 key programmer. Let’s check the comparison table first:

Xtool X100 PAD3 vs. X100 PAD2 PRO vs. X100 PAD2 vs. X100 PAD vs. X100 Pro2 vs. X100 Pro

Function	X100 PAD3	X100 PAD2 PRO	X100 PAD2	X100 PAD	X100 Pro2	X100 Pro
Image
Price	$959	$888	$699	$399	$229	$199
Immobilizer	√	√	√	√	√	√
ECU reset	√	√	√	√	×	√
ABS exhaust	√	√	√	√	×	√
OBD2 diagnostic	√	√	√	√	√	√
EEPROM adapter	√	√	√	√	√	√
Code /Clean reader	√	√	√	√	×	√
Electronic power steering	√	√	√	√	×	√
Meter mileage adjustment	√	√	√	√	√	√
Maintenance light reset	√	√	√	√	×	×
Throttle matching	√	√	√	√	×	×
Tire pressure reset	√	√	√	√	×	×
EPB electronic brake	√	√	√	√	×	×
Exhaust aftertreatment	√	√	√	√	×	×
Headlight adjustment	√	√	√	×	×	×
Diagnostic	√	√	√	×	×	×
Suspension	√	√	√	×	×	×
Battery matching	√	√	√	×	×	×
4 system diagnostic	√	√	√	×	×	×
Windows initialization	√	×	×	×	×	×
Seat match	√	×	×	×	×	×
Cylinder	√	×	×	×	×	×
Airbag repair	√	×	×	×	×	×
Gearbox match	√	×	×	×	×	×
VW 4th and 5th IMMO	√(when working together with KC100 adapter that in the package)	√(when working together with KC100 adapter that in the package)	No (need to buy one extra KC100 Adapter)	×	×	×
Toyota Lexus All Keys Lost	√ (buy extra Xtool KS-1 Smart Key Emulator)	√(buy one extra Xtool KS-1 Smart Key Emulator)	√ (buy extra Xtool KS-1 Smart Key Emulator)	×	×	×
Update	Update directly via the internet using Wifi or wired connection.	One-click update via wifi	One-click update via wifi	One-Click Update Online	Upgrade via web-based download	Upgrade via web-based download
Language	English, Spanish, French, Turkish, Indonesian, Thai and Portuguese	English, Spanish, French, Turkish, Indonesian, Thai, Portuguese…	English, Spanish, French, Turkish, Indonesian, Thai, Portuguese	English, French, Spanish, Polish, Norwegian, Russian, Persian, Arabic, and Hindi	Chinese (Simplified), Chinese (Traditional), English, Spanish, French, Portuguese, German, Russian, Polish, Italian	English and Malaysian

In functions / features/ hardware configuration: Xtool X100 PAD3> X100 PAD2 PRO> X100 PAD2> X100 PAD> X100 Pro2> X100 Pro.

In price: X100 Pro< X100 Pro2< X100 PAD< X100 PAD2< X100 PAD2 PRO< Xtool X100 PAD3

How to choose Xtool X100 Key Programmer?

According to the function you need. If you just need basic immo function, X100 Pro2 is a good choice. If you need extra special service function,and all system diagnosis, the X100 Pad series key programmer can meed the demand. If you need VW 4th and 5th IMMO functions, X100 Pad2 pro is your choose, if you need more special function such as Gearbox match,seat match,airbag repair, X100 Pad3 is the best choice which is the most powerful X100 series key programmer.

Xtool X100 PAD3 vs X100 PAD2 Pro

2020 Best Car Key Programmers Reviews

The post XTool X100 Series Key Programmer Comparison appeared first on UOBDII Official Blog.

OBDSTAR Tablet Key Programmer Upgrade Announcement of July 2020:

Obdstar Tablet Key Programmer includes: Obdstar X300DP Plus Pad2, Obdstar X300 Pro3 key master, Obdstar X300 DP Pad key master

IMMO

BMW

1. Optimized software of CAS2/3 Synchronize DME V30.38

BYD

1. Optimized software of BYD “original key program and clear” V30.42

CHERY

1. Combined Cowin and Jetour with Chery V30.55

2. Combined STEC IMMO pincode input menu into specific function V30.55

3. Optimized STEC pincode reading function V30.58

4. Optimized Tiggo key programming software V30.58

CHRYSLER/DODGE/JEEP

1. Increased AFRICA: GRAND VOYAGER 2009-2014 FOBIK, REMOTE V33.09

2. Increased AUSTRALIA: 300/300C 2019- PROXIMITY V33.09

3. Increased MIDDLE EAST: PACIFICA 2018 PROXIMITY V33.09

4. Increased USA-CANADA: VOYAGER 2020 PROXIMITY V33.09

5. Increased ASIA: CHARGER 2019- PROXIMITY; DURANGO 2003-2006 BLADE; DURANGO 2015 PROXIMITY;RAM 2002-2005 BLADE/REMOTE V33.09

6. Increased AUSTRALIA: RAM 2009-2012 FOBIK V33.09

7. Increased SOUTH AMERICA: NEON 2016-2018 BLADE V33.09

8. Increased AFRICA: CHEROKEE 2008-2012 FOBIK; COMPASS 2007-2014 BLADE; LAREDO 2008-2010 FOBIK; RUBICON 2007-2009 BLADE V33.09

9. Increased ASIA: COMPASS 2007-2016 BLADE; PATRIOT 2007-2016 BLADE; WRANGLER 2007-2018 BLADE; WRANGLER 2018-2019 PROXIMITY; WRANGLER 2020 PROXIMITY V33.09

10. Increased AUSTRALIA: CHEROKEE 2014-2018 FOBIK V33.09

11. Increased SOUTH AMERICA: COMPASS 2019-2020 PROXIMITY V33.09

12. Increased USA-CANADA: CHEROKEE 2008-2012 FOBIK V33.09

13. Optimized software of JEEP Renegade 2015-2017 Proximity V33.09

14. Optimized software of JEEP Renegade 2018-2019 Proximity_key programming and clearance V33.09

DFFENGSHEN

1. Increased A60 Blade 2016- V30.41

2. Increased A60-HR16, MR20 Smart Key V30.41

3. Increased A60-A16, AX3, AX4, AX5, AX7, E70, MX5S V30.41

4. Increased German V30.41

5. Optimized AX3 (DFM A14T MT62.1) V30.41

6. Optimized AX4 Smart Key programming software V30.41

7. Optimized AX5 Smart Key programming software V30.41

8. Optimized AX7 Smart Key programming software V30.41

9. Optimized AX4 Smart Key programming software V30.41

10. Optimized A60-A16 Smart Key programming software V30.41

11. Optimized E70 Smart Key programming software V30.41

12. Optimized E70 Smart Key programming software V30.41

13. Optimized MX5 Smart Key programming software V30.41

14. Optimized the Menu V30.41

DFLIUZHOU

1. Optimized the Menu V30.35

2. Increased B11 Pincode reading function V30.35

3. Increased B12 Pincode reading function V30.35

4. Increased BH5/BH5 LV/BH5A Pincode reading function V30.35

5. Increased BX5/BX5A Pincode reading function V30.35

6. Increased BX3 Pincode reading function V30.35

7. Increased S50(BS3) Pincode reading function V30.35

8. Increased SX5/X5 Pincode reading function V30.35

9. Increased SX6 Pincode reading function V30.35

10. Increased T5L Pincode reading function V30.35

11. Increased XV Pincode reading function V30.35

12. Increased other series Pincode reading function V30.35

13. Increased CM7/CV7/CM7A Pincode reading function V30.35

14. Increased CM7 series Pincode reading function V30.35

15. Increased S500 series Pincode reading function V30.35

16. Increased F600L series Pincode reading function V30.35

17. Increased German language V30.35

FORD

1. Increased ECOSPORT S.AMERICA BLADE 2020 V34.08

2. Increased ECOSPORT USA PROXIMITY 2019-2020 V34.08

3. Increased ESCAPE USA BLADE 2019-2020 V34.08

4. Increased ESCAPE USA PROXIMITY 2020 V34.08

5. Increased EXPEDITION 2020 Smart Key V34.08

6. Increased US region EXPLORER 2020 BLADE V34.08

7. Increased EXPLORER 2020 Smart Key V34.08

8. Increased F150 2019-2020 smart keys V34.08

9. Increased F250-750 SUPER DUTY BLADE 2020 V34.08

10. Increased F250-750 SUPER DUTY PROXIMITY 2020 V34.08

11. Increased FUSION USA PROXIMITY 2019-2020 V34.08

12. Increased KUGA 2019-2020 smart keys V34.08

13. Increased MUSTANG 2020 BLADE V34.08

14. Increased RANGER EUROPE BLADE 2019-2020 V34.08

15. Increased TRANSIT 2020 BLADE V34.08

16. Increased TRANSIT CUSTOM EUROPE BLADE 2020 V34.08

17. Increased Lincoln Aviator 2020 Smart Key V34. 09

18. Increased Lincoln Corsair 2020 Smart Key V34. 09

19. Increased Lincoln MKT 2020 Smart Key V34. 09

20. Increased Lincoln MKZ 2018-2020 Smart Key V34. 09

21. Increased Lincoln Nautilus 2019-2020 Smart Key V34. 09

22. Increased Lincoln Navigator 2020 Smart Key V34. 09

23. Increased PATS1/2/3/4/5/6 BLADE V34.10

24. Increased ECOSPORT USA 2018-2019 BLADE V34.10

25. Increased FIGO AFRICA 2018- BLADE V34.10

26. Increased KA AFRICA 2002-2008 BLADE V34.10

27. Increased RANGER AFRICA 2016-2019 BLADE V34.10

28. Increased RANGER AFRICA 2018-2019 PROXIMITY V34.10

29. Increased ECOSPORT AUSTRALIA 2012-2017 BLADE V34.10

30. Increased ECOSPORT AUSTRALIA 2017-2019 PROXIMITY V34.10

31. Increased ECOSPORT AUSTRALIA 2018-2019 BLADE V34.10

32. Increased ENDURA 2018- PROXIMITY V34.10

33. Increased ESCAPE AUSTRALIA 2018-2019 PROXIMITY V34.10

34. Increased RANGER AUSTRALIA 2018-2019 BLADE V34.10

35. Increased RANGER AUSTRALIA 2018-2019 PROXIMITY V34.10

36. Increased TRANSIT AUSTRALIA 2017-2019 BLADE V34.10

37. Increased TOURNEO CONNECT 2018-2019 PROXIMITY V34.10

38. Increased TOURNEO CUSTOM EUROPE 2016- BLADE V34.10

39. Increased TRANSIT CONNECT EUROPE 2018-2019 PROXIMITY V34.10

40. Increased RANGER S.AMERICA 2019 BLADE V34.10

41. Increased TRANSIT CONNECT USA-CANADA 2018-2019 BLADE V34.10

42. Increased TRANSIT CONNECT USA-CANADA 2018-2019 PROXIMITY V34.10

43. Optimized Software of FIESTS_EUROPE_2012-2017_PROXIMITY_All key lost V34.10

44. Optimized Software of Old Mondeo BLADE All key lost V34.10

45. Optimized Software of TRANSIT CONNECT_EUROPE_BLADE_-2006 all key lost V34.10

46. Optimized Software of New Mondeo-2017 Type 1_All Key Lost_Read Flash V34.10

47. Optimized Software of F-150_BLADE_2011-2014 Key Programming V34.10

48. Optimized Software of FORD_BLADE_Escape_Add Key and all key lost V34.10

49. Optimized Software of FORD_BLADE_Mondeo_Type 2_Add Key V34.10

GEELY

1. Optimized Geely STEC Key programming function V30.67

2. Optimized EMGRAND GS key programming software V30.67

3. Optimized the menu  V30.67

GM

1. Optimized software of EXCELLE GT/XT 2017- no proximity all keys lost V32.13

2. Optimized Lacrosse 2005-2009 no proximity system V32.13

3. Optimized the menu of GL8 Proximity V32.13

4. Increased GL8 Proximity 2019- 2.0T Type 2 V32.13

5. Optimized REGAL_No Proximity_2000-2005_All key lost V32.14

6. Optimized Software of BUICK_ENCORE_2012-2018_PROXIMITY V32.14

7. Optimized software of GL8_2019-_2.0T_Proximity_key programming V32.14

8. Optimized Software of Buick Regal 2017- Smart key programming V32.16

9. Increased pincode reading function for Shanghai Pan-Asia V32.16

10. Increased Key Number reading function of Buick Excelle 2015-2017 Proximity/No Proximity V32.16

11. Increased Buick Enclave 2020 Proximity V32.19

12. Increased Cadillac CTS 2020 Proximity V32.19

13. Increased Chevrolet Captiva Africa 2013-2017 Proximity V32.19

14. Increased Chevrolet Blazer USA-CANADA 2019- Proximity V32.19

15. Increased Chevrolet Spark USA-CANADA 2020 BLADE V32.19

16. Increased Chevrolet CORVETTE STINGRAY USA-CANADA 2017-2019 Proximity V32.19

17. Optimized Software of Chevrolet USA-CANADA V32.19

18. Optimized Software of CAMARO Proximity V32.19

19. Optimized Software of SILVERADO 1500 BLADE and Proximity V32.19

20. Optimized Software of SUBURBAN Blade V32.19

21. Optimized Software of Tahoe Blade V32.19

22. Optimized Software of Cadillac USA-CANADA: ESCALADE Proximity V32.19

23. Optimized Software of GMC USA-CANADA: ACADIA Proximity V32.19

GREATWALL

1. Optimized software of HavalH6_2013-2018_BCM_Remote_Type 1 V31.78

2. Optimized software of GreatWall C50_2012_STEC_BCM_Remote_Type 1 V31.78

3. Optimized software of Haval H6_2012_BCM_Delphi BCM_Remote_Type 1 V31.78

JAGUAR

1. Optimized the Help info Menu V10.02

JMC

1. Increased Yu Sheng S330 Blade key programming(Bypass Pincode) V30.24

2. Optimized software of Yu Shen Smart Key Programming V30.24

KIA

1. Optimized Software of Manual select Model_K2 (QBC) _2011 -_IMMO _Type1 (CAN) V31.01

2. Optimized The Menu (Give warning once select the Advanced Functions) V31.01

3. Optimized software of Manual select system_IMMO_Type 5 V31.01

4. Optimized 46 Blade Pincode reading function V31.02

5. Optimized Manual Select Model_Proximity_No Slot_Type 2 V31.02

6. Optimized 46 Proximity Pincode reading function V31.02

7. Optimized Manual Select Model_NORTH AMERICA_STINGER(CK)_2018-2019_PROXIMITY V31.02

8. Optimized KX1_2018-2019_Proximity_Type 2 V31.05

9. Optimized Manual Select System_BLADE_Type 13 V31.05

10. Optimized Manual Select System_BLADE_TYPE 14 V31.05

11. Optimized Manual Select System_REMOTE_16PIN_TYPE 8 V31.05

12. Optimized Read Pincode_Proximity_4A Smart Card V31.05

LANDROVER

1. Optimized Range Rover Proximity programming software V31.15

2. Optimized Software Version Judgement V31.15

3. Optimized the Help info V10.03

LUFENG

1. Increased Simens Pincode reading function and X5 pincode reading function. V31.04

2. Optimized the Menu, Include the Simens pincode function in specific function, won’t be listed seperately. V31.04

MAXUS

1. Optimized software of MAXUS G10_Body Control System  V30.33

2. Optimized Software of MAXUS V80_ -2017_BCM_V80 V30.33

NISSAN

1. Increased X-TRAIL (T32) AUSTRALIA 2013- TYPE 2 V32.01

2. Increased X-TRAIL (T32) EUROPE 2014- TYPE 2 V32.01

3. Improved X-TRAIL (T32) EUROPE 2014- PROXIMITY V32.01

HNMAZDA

1. Increased M3/M5/M6/S5 PIN CODE reading function V30.62

2. Increased German language V30.62

3. Optimized the Menu, Include the Simens pincode function in specific function, won’t be listed seperately. V30.62

4. Optimized STEC pincode reading function V30.63

5. Optimized FAMILY system V30.63

HYUNDAI

1. Optimized EUROPE_ATOS_2004-_BLADE V31.03

2. Optimized Manual Select System_Blade_Type4 V31.03

3. Optimized Manual Select System_PROXIMITY_Without Card Slot_TYPE 5(CAN) V31.03

4. Optimized Manual Select System_PROXIMITY_Without Card Slot_TYPE 1 V31.03

5. Optimized 46 Smart Card Pincode Reading Function V31.03

6. Optimized Manual Select System_Blade_Type9_IM_VENUE_4A V31.05

7. Optimized Manual Select System_Remote_16 PIN_Type8__RM_HD_CAN_4A V31.05

8. Optimized Manual Select System_Proximity_Type 3_IM_SANTAFESMART_4A V31.05

9. Optimized Read Pincode_Proximity_4A Smart Card V31.05

10. Optimized 46 Blade Key Pincode Reading Function V31.05

RENAULT/DACIA

1. Optimized Software of CLIO_2006-2012_Proximity(Card) V30.09

2. Optimized the Menu V30.09

3. Increased Advanced Function including

ECU LEARNING:

CAPTUR, CLIO II, CLIO III, CLIO IV, DUSTER, DOKKER, ESPACE III, ESPACE IV,

FLUENCE, KANGOO, KOLEOS, LAGUNA I, LAGUNA II, LAGUNA III, LATITUDE, LOGAN, LODGY, MASTER, MASTER III, MEGANE II, MEGANE III, MODUS, MOVANO, PRIMASTAR, SAFRANE, SANDERO, SCENIC II, SCENIC III, SYMBOL, THALIA, TRAFIC, TRAFIC II, TWINGO I, TWINGO II, VELSATIS, VIVARO, WIND

CLEAR IMMO CODE:

CAPTUR, CLIO III, CLIO IV, MEGANE III, MODUS, SCENIC III, TWINGO III

4. Increased Renault(Indian) LODGY_TYPE 2_With PIN

ROEWE

1. Optimized the menu V31.72

2. Update mutual prompts when reading pincode V31.72

3. Optimized software of MG 2019 Roewe RX3 – Proximity Programming V31.72

4. Optimized 2004 MG TF software  V31.72

TRAUM

1. Increased S301 and D50 pin code reading V30.11

2. Optimized the Menu

SUZUKI

1. Optimized software of VITARA_BLADE_S.AMERICA_2016- V30.68

2. Optimized China Suzuki_Vitara_Type 3 V30.68

3. Optimized China Suzuki_Vitara_Type 1_type 2 V30.68

4. Optimized Swift_Blade_Europe_2005-2007_diesel_immo_India_type 1 V30.68

5. Optimized Software of 8digit Pin Calculator V30.68

TOYOTA

1. Optimized software of USA 2017-2018 COROLLA_Program Smart Key, Erase Smart Key V32.24

2. Optimized software of USA 2010-2016 PRIUS_Program Smart Key V32.24

3. Optimized software of Remote_Type 2_Remote Programming V32.24

XENIA

1. Optimized R7_Smart Key System_ Program ECU V30.09

ZOTYE

1. Optimized the menu layout, and increased help index V30.63

2. Increased Pincode reading function for two groups of Z500 proximity V30.63

3. Increased German Language V30.63

4. Increased 4digits pincode reading function for Z300, Z360 V30.63

5. Increased DAIMA X5, DAIMA X7, SR7, SR9, T300, T500, T600, T700, Z700  Proximity Pincode reading V30.63

CITROEN/PEUGEOT/DS

1. Optimized software of BSI KOX V31.19

2. Optimized software of BSI_Q0X V31.20

3. Increased the function of reading the version V31.20

4. Increased the function of erase fault code V31.20

5. Increased the file size judgement function when recover the data V31.20

FORD

1. Optimized Edge 2015- Color Screen Mileage software V30.88

GM

1. Increased Chevrolet TRAILBLAZER 2019 V31.04

2. Increased Buick ENCLAVE 2020 V31.04

3. Optimized chevrolet suburban 2003-2006 mileage software V31.04

LANDROVER/JAGUAR

1. Increased Discovery Sport 2016 Cluster Calibration V30.98

2. Improved Evoque 2015- Software V30.98

3. Improved Jaguar XJ 2016 Software V30.98

MITSUBISHI

1. Optimized Software of ATTRAGE 2014 Smart Key V30.65

2. Optimized Software of Eclipse Cross Smart Key Programming V30.65

3. Optimized L200_Blade_2015- Key Programming Procedure V30.65

4. Increased Eclipse Cross 2019- Blade V30.65

OBD-II

1. Updated the TEXT BASE V30.21

2. Increased German, Italian, Vietnamese and Hebrew V30.21

Oil Service Reset

Newly Increased:

1. Increased Great Wall Wingle7, PAO; HAVAL F7X, H9 2020; VV7 2020 of WEY; NEW ENERGY: C30(CH041E), C30 EV, ORA IQ-420, ORA-R2 V32.25

2. Modified procedure of C30EV (non-rent) V32.25

3. Optimized Hyundai/Kia software V32.25

4. Optimized Changan software V32.25

5. Optimized BMW Operation notice after oil reset V32.25

6. Increased Help info V10.02

7. Increased BMW E, F, G chassis Autonomous service Interval function V32.27

EPB 

1. DFFENGSHEN: E70(280) V30.71

2. DFFG: S560, 580 V30.71

3. MG: EZS(ZS11E) V30.71

4. ROEWE: RX3, RX8, RX3, EI5, I5 V30.71

5. HNMAZDA: F7, V70/FAMILY V30.71

6. HANTENG: X5, X5 EV, X7, X7S, X7PHEV V30.71

7. LANDWIND: XIAOYAO, X5, X7, X7(2017) V30.71

8. DAIHATSU: R7 V30.71

9. CHANGAN: CS75(PHEV) V30.71

10. BISU: T3, T5 V30.71

11. Chery: Ariza EX/GX, Tiggo 8, Tiggo 5X(T19) V30.71

12. SVAY: X70, G01 V30.71

13. FAW HONGQI: H5 V30.71

14. CHANGFENG LEIBAO: CS9, CS9EV, CS10, MATTU V30.71

15. GREATWALL: F5, VV6, H9 V30.71

16. JETOUR: X70, X70S, X90 V30.71

17. ZOYTE: SR7EV, T300, T300EV, T800, Z500EV, Z560, Z360 V30.71

18. WAGON: E100, E200, 530, 560, 730 V30.71

19. BRILLIANCE: V6 V30.71

20. FORD: ESCAPE V30.71

21. LINCOLN: CONTINENTAL, MKC, MKX, MKZ, NAUTILUS V30.71

22. CHANGAN FORD: F-150, ESCAPE, KUGA, TAURUS V30.71

23. JEEP: B1-Renegade(2015-2018), BQ-Renegade(2015-2018), U-Renegade(2015-2018), L-Cherokee(2014-2019), K8-GrandCommander(2019), 4-Compass(2019),  V30.71

24. CHRYSLER: UF-CHRYSLER-200 (015-2018) V30.71

25. VOLVO: S90(2017-2020), S90L(2017-2020), V60(2019-2020), V60 CROSS COUNTRY(2019-2020), XC40(2018-2020), XC90(2016-2020), V90(2017-2020), V90 CROSS COUNTRY(2017-2020) V30.71

26. BENZ: A Series 177, B Series247, CLS Series167, 257(ESP213), CLA Series118, EQC Series293, GLA Series247, 253, GLC Series253, GLE Series167, GLS Series167, X Series290 AMG V30.71

27. BENZ COMMERCIAL CAR: X447/448, Sprinter907,910 V30.71

28. DONGFENG PEUGEOT: 301, 308_TX9, 3008(P84), 4008, 5008(P85) V30.71

29. DONGFENG CITROEN: C4 AIRCROSS(A88C)  C5 AIRCROSS  C5 III   C6(CHINA)  DS7 V30.71

30. LAND ROVER: DISCOVERY SPORT(2018-), DISCOVERY(DISCOVERY 5), EVOQUE(2018-), EVOQUE(CHINA)(2016), RANGE ROVER SPORT(2017-(2016), RANGER ROVER VELAR(2018-) V30.71

31. JAGUAR: E-PACE(2018-), F-PACE(2018-(2017), F-TYPE(2018-), I-PACE(2019-), XE(2018-(2017), XF(2018-(2017), XJ(2016-(2013-2015) V30.71

32. HYUNDAI: G90(HI)(2020), GRANDEUR(IG)(2017-2020), GRANDEUR HYBRID(IG HEV)(2018), I30(PDE)(2019-2020), KONA EV(OS EV)(2019), NEXO(FE)(2018-2019), PALISADE(LX2)(2020), SANTE FE(2019-2020), TUCSON(2015-2020) V30.71

33. KIA/USA: CADENZA(VG)(2014-2017), CADENZA(YG)(2014-2017), K900(RJ)(2019-2020), SOUL(SK3)(2020), SOUL(SK3 EV)(2020), SPORTAGE(QL)(2016-2020) V30.71

34. KIA/EUROPE: CADENZA(VG)(2012-2017), CADENZA(YG)(2017-2019), CARENS(RP)(2014-2019), CEE’D(JD)(2013-2018), K900(RJ)(2019-2020), SOUL(SK3/SK3A)(2019-2020), SOUL(SK3 EV)(2020), SPORTAGE(2016-2019), TELLURIDE(2020) V30.71

35. KIA/KOREAN: CARENS(RP)(2014-2018), K7 HEV(YG HEV)(2017-2018), K9(RJ)(2019), SPORTAGE(QL)(2016-2019) V30.71

36. BJHYUNDAI: KONA ELECTRIC(2019), SONATA 9, New Santa fe (2015-2019), Ling(2019), Fista(2018-2019), 4th SANTA FE (2019) V30.71

37. DFYDKIA: K3(BDC)(2019-2020), K5(JFC)(2015-2019), 5 HEV(JFC)(2018), K5 PHEV(JFC)(2017-2019), KX5(QLC)(2016-2019) V30.71

38. MAZDA: AXELA 1, AXELA 2, AXELA  V30.71

39. ENVISION 2019 V30.72

40. REGAL 2014-2019 V30.72

41. LACROSSE 2018-2020 V30.72

42. VERANO 2019-2020 V30.72

43. GL8 ES AVENIR：2017-2019 V30.72

44. GL8 LUXURY MPV：2015-2019 V30.72

45. ENCORE 2020 V30.72

46. ATS：2014 V30.72

47. ATSL：2018-2019 V30.72

48. CT6：2019-2020 V30.72

49. XT4：2019-2020 V30.72

50. XT5：2019 V30.72

51. XTS：2014-2020 V30.72

52. SRX：2014-2016 V30.72

53. BLAZE: 2020 V30.72

54. Equinox 2019 V30.72

55. CRUZE 2016-2020  V30.72

56. SPRINGO EV: 2014  V30.72

57. CAPTIVAL: 2014-2017  V30.72

58. VOLT 2013  V30.72

59. MALIBU 2016-2020 V30.72

The post Obdstar Tablet Key Programmer Update in July 2020 appeared first on UOBDII Official Blog.

Topic: Ford PCM Replacement – How To Write a VIN on an USED PCM Module with Autel IM608 J2534

I would like to share with you how I program a Vin number to a used Ford PCM module. The client is was stranded with no resolutions as the IM608 could not do the Vin Programmable Module Installation procedure.

Normally to do this procedure all you need to do is click programming and look for a programmable module installation (PMI) which is a sequence in that the software will save all the original PCM’s information in our tool ,then prompt you when to put the replacement module on it. Next itwill then transfer all the information to the replace module With this specific vehicle which is a 2001 Ford F-250 it does not have this functionality on the Autel IM608 so to do this procedure will be using J2534 with the OEM subscription in a Windows 10 laptop.

Product ID: Maxi JVCI J2534 (IM608)

Vehicle: 2001 Ford F250

Procedure / Problem: Not able to write VIN on used PCM Module with the IM608.

Tap “Diagnosis” on IM608.

Programmable module installation.

Prepare:

1. MaxiFlash J2534
2. Ford Day Subscription
3. Programmable module installation

Problem:

The main PCM is through away, and there is no way for us to extract that information to transfer it over. So I am being optimistic .

So we go to the Ford subscription and what you see here is nothing, the software is just looping, it doesn’t give me any option to even program it. You know we’re just basically doing the same thing. We did this for about 20 minutes and it just kept on asking us to do this, weren’t getting anywhere.

So I give a recommendation. What I want you to do id to turn off the ignition. Because when you do this it pulls the all software, the PCM is new, there’s no communication, there’s no power being sent to the PCM, so I think it’s like a blank module, then after we power is, then turn off the ignition, we’ve gonna run the forward software, then follow the prompts to enter VIN, then continue to follow the prompts to finish the programming procedure.

So that’s exactly what we did.

After turning on the ignition, it says enter the VIN. We can go ahead and then enter then VIN and then follow the procedure. And the next step would be to do the tear tag information, you don’t need to put the PCM part number there, you can go straight to the tare information and put that into the slot. You just follow the prompts. The last step is to check the VIN and then write the mileage on.

So the VIN has been changed this is original VIN, where it says odometer that’s where we can write the original mileage, yeah you’re done. 

What I want you guy to learn from today:

1. If the scanner doesn’t have the “Programmable module” installation,”

If The Scanner Doesn’t Have the “Programmable Module Installation, ” feature, Use Fords DEM Software To Complete The Programming Task.

2. Always Try To Keep The Original Module When Replacing it With A Used Module.
3. To Write The VIN on A Used Module,(When Original PCM is Not Present) Turn Off The Ignition, Then Run The Ford Software.
4. Having A Consultant Increases Success Rate When Facing Complex Situations.

If you want to order Autel IM608, go to

https://www.uobdii.com/wholesale/autel-maxiim-im608.html

The post Autel IM608: how to write a VIN on a used PCM module with the J2534? appeared first on UOBDII Official Blog.

Very pleased with SD Connect C4 when plugging it into my van (2002 311 CDI LWB UK spec) to run a ‘quick test’, first attempt and found everything simple to navigate.

Questions: where does the multiplexer get power from as a battery icon appeared in the little window on the multiplexer and a warning !Check Batteries! after this appeared an error screen appeared on the laptop screen along the lines of communication had been disrupted (i was checking the block heater at the time) due to low voltage.

I had the van idling in the driveway with 14.2v in the top right of laptop screen so wanted to know as to how if atall i charge the multiplexer, the laptop had 82% battery life when the ! Check batteries! appeared on the multiplexer.

Possible reason:

Multiplexers SDConnect C4 Chinese production is peculiar, randomly appearing, battery charge error. The error is accompanied by the message “Insert / check batteries” “batteries can not be charged” on the instrument display.

This stops the batteries from charging. This error can be caused by two reasons.

1. wear or not the corresponding capacity of the installed batteries.
2. a chaotic error caused by the feature of the circuit design of the multiplexer. Revision of the device circuitry eliminates the second reason. As a result, the battery charge error will appear only due to the “fault” of the batteries themselves.

How to solve ” Check Batteries!” error?

Review 1:

I am pretty sure that the consensus view is to run it without batteries and ignore the warning on the display.

BTW: you should always connect an external power supply to your van while using Star.

Another thing to watch out for is to NOT use a 12v-to-laptop adapter powered by the Sprinter when you’re using a diagnostic device that also connects to the Sprinter.

Many 12v-to-laptop devices have a “common positive” .. the battery’s +12v is fed directly to the laptop via a wire.
The 12v-to-laptop adapter then creates the laptop’s desired 18v by pushing the *negative* feed “down” an addition 6 volts …
If the SD Connect C4 diagnostic device expects to be able to connect the laptop’s signal “ground” (or 0v or negative) directly to the Sprinter’s 0v/negative/frame smoke can happen… you’ve suddenly got the power adapter fighting the two “negatives'” 6 volt difference across the diagnostic device.

You can avoid this problem by letting the laptop only use its internal battery, or by using a 120vac adapter to power the laptop.(or the 12v-to-laptop plugged into a totally separate external battery).

Review 2:

Try to use mux on lan(without wireless card inserted),and you will have no more ‘check batteries’ error on display.
seems that error came from heating the wifi card and not correctly drainage from hot air.

Added to this, using mux without wifi card save around 0.4v consumption, xentry will see around 0.4v more voltage,so safer voltage for programming,etc… I dont have wifi card installed, better work always with lan, i dont see too much work in connecting just a cable when making a work.

i think heat with wifi card is a problem because card itself is heating adding to the heat that pcb’s itself produces, with no card installed less heat inside the mux and heat can go exit through the free slot of card, making a grill on the grey plastic piece will help allowing heat to go out of mux, surely extending its life.

Review 3:

I’ve used my (Chinese clone C4) MUX from the first beginning without batteries.
After some time I inserted rechargeable batteries just because I had the same idea as mentioned a few times above -> The voltage drop/peak when starting/stopping the cars engine is not good for the electronic components of the mux. The same problem occurs when disconnecting the mux from the car.

But as I did not remove the rechargeable batteries after use I noticed that some of the inserted batteries went dead after a while. This was (my personal opinion) because of the continuous battery drainage that pulled the voltage so low the batteries eventually got broken.

I always had with empty batteries often because the device was in standby mode and in the course of time were empty, I have considered a solution and indeed an on and off switch after the device goes down in standby mode, I turn it off thus it can not consume power and keep the batteries.

Another solution I’m thinking about is when not in use connecting the mux to a power source (battery charger). This way the batteries are always getting charged but I’m not sure if this is a good idea?

And I never use the WiFi connection because I’m afraid for connection losses during updating work on the car.
Just my humble opinion in this matter.

Good to know:
1). When testing the Mercedes Benz cars:

All sdconnect c4 don’t need the battery.

2). When updating sdconnect c4 firmware:

– Only the best sdconnect C4 plus DoIP  does not need the battery:

图片1（服务器找C4）

– The other sdconnect c4 firmware update needs to install the battery.

SD Connect C4 battery installation instructions here:

Easy Guide on how to install MB SD C4 Batteries

Credits to @ gcs190 who shares “How to Update SD Connect without batteries“:

If you need to update an SD Connect and you do not have batteries or the power supply/charging circuit is damaged, you only have to edit the toolkit.ini file, modifying the following lines so that the supply and/or battery voltage is lower to the real (it would be enough to set them to zero)

Obviously make sure you have a stable and sufficient external supply.

[SoftwareUpdate]

Voltages necessary for SDconnect firmware updates. These values are only for the pre-check of the toolkit, the values will be checked by the update process again

MinUpdateVoltageVBatt=7200
MinUpdateVoltageVExt=11000

A reboot is required for the new settings to take effect (Probably a Tkserver restart is enough)

Good luck!

The post How to fix SD Connect C4 “Check Batteries” Problem? appeared first on UOBDII Official Blog.

Question: I installed Ista D 4.22, but I run into issues when I try to connect with the car using Scanmatik 2 PRO. I tried to select from Ista settings interface J2543 Passthrough or Ediabas.ini , but no success. I have the confirmation from somebody that i need to use Ediabas selection and PTTbmw software , but I’m stuck, I can’t get it to run.

Possible reasons and solutions:

Option 1.

Use only PTTbmw software 2.1.0.0. others version not work fine…

After installing PTTbmw software 2.1.0.0 drivers need to edit ediabas.ini and on the interface need to set for passthru so need to have: interface=std:passthrud
If interface is good must works in this way for sure.

Add a note:

It’s more complicated than just putting
interface =std:passthrud

I’ve done that and it’s only getting 12v battery voltage on pin 16. When running identification on ista, my cardaq LEDs are blinking but ista says it can’t talk to car and tell me to put ignition pad to on.

On easyconnect, the software see battery voltage on terminal 30 but not terminal 15 voltage. So I guess it’s picking up direct voltage from pin 16 but no protocol / communication take place between passthru device and car.

PS: Terminal 30 is on pin 16 and the ignition (terminal 15) is over CAN on F and G series. On E series it is on pin 1.

Option 2. make K+Dcan cable usable with Ista

Using a K+Dcan cable… but it worked straight away…

Step 1

Connect INPA K+DCAN Cable with the computer to install driver.

Open “Device Manager” then “USB Serial Port (COM3)” Properties.

Select  “Port Settings” and “Advanced…”

Set the COM Port Number to 9 and Latency Timer to 1. Click on “OK”.

Step 2

Open C:/EDIABAS/BIN/EDIABAS.INI with Notepad. Check for “Interface=STD: OBD”.

Set “TCP Port=6801”.

Open C:/EDIABAS/BIN/OBD.INI and check for “OBD Port=COM9”.

Step 3

Plug INPA K+DCAN Cable into the car and the computer to run BMW ISTA software. Click on the Setting button.

Choose “VCI Config” tab and “Ediabas standard settings (ediabas.ini)” option then click the OK button.

Go back to main menu and click on “Operations”.

Choose “Read out Vehicle Data” tab and click on “Complete identification”.

Now wait the vehicle identification process complete.

For someone who need the link for download Ista 4.24:

https://www.uobdii.com/wholesale/latest-bmw-icom-hdd.html

The post How-to guide to make scanmatik usable with Ista? appeared first on UOBDII Official Blog.

I have 2008 335xi- N54, I am experiencing a 2acb/2acc on my 335xi which has the same JB layout. I’m seriously thinking of replacing the JB and hopefully that fixes it.

I did have some water damage due to a water pump failure that got coolant in the ECM box. No blown fuse or corrosion so it’s down to the the JB or DME.

Symptom and car info:
1) 2008 335xi- N54
2)I have access to MHD and BimmerGeeks ProTool
3) I currently do not have access to a multi-meter, have one at work but our state is under a Shelter-In-Place order so I can’t really leave the house.
4) The engine will CRANK but NO START,
5)
-Water pump was replaced and verified functioning
-wipe and dry out the coolant from the ECM box
-removed the JB4
-check for corroded and wet connector pins, no corrosion but I noticed a little moisture inside the left DME connector, dry out the pins and wipe the female connector, put all connectors back to stock with JB4 harness completely removed
-flashed DME back to stock BIN
-Checked all fuses in fuse box 3x times (no blown fuses),
-Replace the I01068 black relay after being told that was the DME relay.

6) Whether any codes OTHER than 2ACB & 2ACC; Those are primarily the only two codes I get consistently, I ran several code check throughout each start attempt, here are the last two:

2ACB
2ACC
2E85 – BSD message, electric coolant pump: missing

2ACB
2ACC
2CFB DME, Throttle-valve adaptation value (this may be caused by me pressing the throttle during start up)
2D09 DME Throttle (this may be caused by me pressing the throttle during start up)
2E85 – BSD message, electric coolant pump: missing

A little back story on how this all happened. My water pump failed and overheat the car. Coolant oversprayed the engine bay and got into my ECM box (did not know this until after the fact). Initially, the car ran normally after the water pump and battery was replaced. The next day, the car would only crank but not start. I start experiencing random electrical issues, first the JB4 would no longer connect, the board was replaced and again the car started up immediately. Then as I had the car off and updating some settings in the the app, it lost connection and random clicks of various electrical systems were turning on/off.

I was then told to remove the JB4 completely and flash my custom tune back to stock via MHD. In the mist of flashing, the MHD app lost connection and no longer connecting to either MHD or Protools. Another round of search brought me to a coder who did a DME recovery for me. Now I am again able to connect via MHD/ProTools. This is where I am now. So please feel free to have me try anything, I’m not super skilled with electrical diagnostics but am very mechanically inclined so bear with me.

Symptom:

To restate the observations from the prior post:
1) It appears that the DME Relay is NOT being activated
2) If DME is NOT activated, the dashboard lights as normal when turning ignition ON, Radio, Blower, Wipers, Windows, Seats, and Starter all work as normal, BUT
3) The Engine will NOT fire, as the Sensors (Crankshaft & Camshaft) that time the DME pulse of Spark & Injectors are NOT powered, and the DME itself cannot function. Also, the LP Fuel Pump does NOT run. It still has Power Supply to the DME sufficient to have a Scan Tool connect & read Memory.

So the two recurring codes indicate, consistent with the symptoms you describe, that your DME Relay (K6300 on the TIS schematic linked in the prior thread, which happens to be the correct Schematic for your 2008 335xi with N54) is NOT being activated to Supply Power to general DME functions, and to power the Sensors mentioned above.

Proper Diagnostics would suggest that you use a Multimeter (OR a test light would also work) to CONFIRM that the DME Relay is NOT being activated. Here are wiring diagrams, Installation Locations, and Connector Views to help you determine WHAT is NOT getting Power Supply (12V+ on multimeter or test light).

Here is the wiring diagram that shows how the DME is always powered by the 10 Amp fuse F4. I would begin by using a multimeter or test light to confirm power at ONE of the two F4 sockets with the fuse removed. That is Battery power (NOTE the “30” above the fuse symbol indicating “Terminal 30” or Battery [unswitched] power).
https://www.newtis.info/tisv2/a/en/e90-335xi-lim/wiring-functional-info/power-train/engine-electronics-quality-control-valve-msv/voltage-supply/control-unit-power-supply/vMifIQL

F4 ONLY supplies control system power, and NOT power for other DME functions. NOTE that the DME “turns itself on” in that the Red/Gray wire from Pin #13 of Connector X60005 of the DME provides a ground signal to the K6300 DME Relay electromagnet. NOTE that Red/Gray wire passes through Pin #5 of Connector X60551 on the way from the DME to the Relay. That Connector X60551 is in the E-box as shown below, and that is the easiest location to test, particularly since you have the E-box open.

The 12V+ side of the relay electromagnet coil, and the other side of the contacts are BOTH ALWAYS powered by Battery power, or “Terminal 30”, also known as Kl.30 (Klemmen is German word for Terminal), so if you apply a ground to that Red/Gray wire, the relay should “CLICK” if it still works, and the engine should fire when the Starter cranks the engine. Here is a more complicated schematic of the Junction Box, which shows ALL of the relays & fuses. What is important here for YOUR understanding is Kl.30 (Terminal 30 or Battery Power), Kl.87 (Terminal 87 powered by operation of K6300 DME Relay, and K6300 itself, and WHY its operation is important.
https://www.newtis.info/tisv2/a/en/e…ule/1VnXpW4emV

Even if you don’t have a multimeter or test light to check for 12V+ (in reference to Chassis Ground), you can STILL do a test to determine if the K6300 DME Relay works. What you have to do is apply a ground (any wire or conductor contacting good chassis ground) to the Red/Gray wire. There are several ways you can do that. The simplest is to locate the Red/Gray wire and stick a pin in it (penetrate the insulation and contact the wire inside), and then ground the pin. If you hear the relay click (located INSIDE the JB just above the Terminal 30g relay you replaced), then you have found the CAUSE of your problem (but you STILL have to locate the reason for NO ground signal & correct it). A corroded Connector Pin at the DME, at the JB, OR at X60551 itself, are the most likely causes if the Relay clicks when ground applied.

A more elegant way to ground the Red/Gray wire is to locate that wire inside the E-box, at Pin #5 of Connector X60551. Here is the TIS Installation Location for those two connectors, each at rear of E-box:
https://www.newtis.info/tisv2/a/en/e90-335xi-lim/wiring-functional-info/functional-wiring-diagrams/09-vehicle-electrical-system/front-fuse-relay-module/1VnXpW4emV

Since you got coolant in the E-box, that Connector, or moisture in the DME itself, are the most likely causes of your issue.

I would suggest reviewing the above so that you understand how to Activate/test the relay and then try that & let us know what you find. So you can understand WHY operation of that relay is necessary, here are circuits for Fuse 39 (Ignition coils), Fuse 37 (Camshaft Sensors), and Fuse 11 (Crankshaft Sensor), ALL of which are powered from Terminal 87, powered by the DME Relay (K6300):
https://www.newtis.info/tisv2/a/en/e90-335xi-lim/wiring-functional-info/power-train/engine-electronics-quality-control-valve-msv/ignition/uuem8HV

https://www.newtis.info/tisv2/a/en/e90-335xi-lim/components-connectors/components/f-fuses/f54-fuse/i1ukJnB

https://www.newtis.info/tisv2/a/en/e90-335xi-lim/components-connectors/components/f-fuses/f11-fuse/iE4uiI1

I’m NOT familiar with ProTool, but if it can do most of the things INPA can do, you MAY be able to quickly determine if Terminal 87 (KL.87) is active or not when ignition is ON, just by connecting to the DME (MSD80 for your N54) and reading the voltage that way.

INPA is “Factory Level” software developed by the German-speaking guys who designed & built our BMW’s, so one would expect that if they found a way to display or control component data/function, ProTool COULD be designed to do the same. It’s just a matter of WHAT particular functions BimmerGeeks has developed to date.

With INPA, one can see KL.87 voltage displayed on a Status screen, as shown in the first bar graph on the top left of the 1st attached jpg. OR one can turn KL.87 on/off by activating or deactivating the DME Main Relay, as shown in the 2nd attached jpg. I have translated (in red) the pertinent parts of the German “Labeling” in those two screens. INPA allows a knowledgeable user to quickly conduct MANY tests that would require one to identify and access a particular connector, and “Backprobe” a connector or otherwise use a multimeter to measure voltage, continuity, resistance, etc. You can do all this just by connecting the laptop to the OBD II Socket and seeing the data, and/or controlling the component, on your computer screen. You just have to know what data can be viewed, and what screen to use to view it, or to control a component.

Keep in mind that the DME supplies a ground signal to the DME Relay to complete the Relay’s electromagnet coil circuit and close the relay contacts. The reason it is called “Terminal 87” is that Terminal or Pin #87 of a standard automotive relay is the Power Supply Terminal when the relay contacts are CLOSED, and Terminal 30 of that relay is Battery Power, to which Terminal 87 is connected when the contacts close.

I don’t know WHAT Documentation, instructions, or List of Functions ProTool has, or what support BimmerGeeks provides. I would encourage you (and anyone using ProTool) to share such information. ANY decent Scan Tool, or Diagnostic Software, is capable of doing a LOT more than just reading Fault Codes. It should also have the capability to (1) Read Parameters or input values such as Sensor signals or various voltage values, AND (2) Allow Activation of motors, valves, relays, etc.

The DME can only activate the DME Relay IF connections are intact between Pin #13 of Connector X60005 and the Relay coil, AND the DME is operational. Please let us know WHAT you are able to determine ProTool can do to (1) display Terminal 87 Voltage, and/or (2) Activate the DME Relay to power Terminal 87.

Reply from the issuer:

I completely spaced out that I have INPA installed on my laptop. I’m not verse with INPA navigation but I was able to locate the kl.87 activation via Component Triggering > Actuator activation 1 > Clamp 87/mail relay DME. However, once I got into this section and attempt to turn ON, I get what appears to be an initialization error/ no component response error as seen below. After attempting this, my LPFP is now running constantly. Disconnected and cycled the ignition and LPFP is quiet again.

I also located the MWB1 and was also getting the same initialization error, second screenshot.

Upon additional research, with the cable that I had, I found that I had to modify the ediabas.ini file and update the port from 3000 to 6801. Once I did that, I was able to connect to the LIVE DATA portion and display the MWB1, see 3rd screenshot, it does not look like my KL.87 is getting any voltage. I also attempted to activate the relay but after trying to turn it ON, it errors out ultimately with NO RESPONSE FROM CONTROL UNIT.

Further advice:

Good job getting the INPA data. I assume Ignition was ON when those screens were saved, and if so, that confirms that the DME is NOT “turning itself on” by activating the DME Main Relay (K6300) to power Terminal 87 (0.2V won’t cut it ;-). That explains “Crank but NO Start/Fire”, but we still don’t know if the relay is bad, there is a wiring fault in the “Activation ground wire (Red/Gray wire) and its connectors, or if there is an issue with the DME.

If I were dealing with that situation, my next step would be to try to apply a ground to the Red/Gray wire inside the E-box, at Pin #5 of Connector X60551. Here is the TIS Installation Location for that connector, at rear of E-box:

Here is the wiring diagram showing the Red/Gray wire from Pin #13 of Connector X60005 of the DME to Pin #5 of X60551. That wire NEVER leaves the E-box. THEN there is another Red/Gray wire from Pin #5 of X60551 (same size & color wire) that goes OUT of the E-box to the chassis wiring harness that runs to the JB (Junction Box) Connector X11010. It is THAT wire going to the JB to which you want to apply a ground (at Pin #5 of connector X60551 in the E-box):
https://www.newtis.info/tisv2/a/en/e90-335xi-lim/wiring-functional-info/power-train/engine-electronics-quality-control-valve-msv/voltage-supply/control-unit-power-supply/vMifIQL

I’ve never had to open my E-box, so I can’t provide any more tips than that, but hopefully the TIS wiring diagram and “Installation Location” are sufficient to solve the puzzle. I did test the DME Main Relay Activation function on my MSV80 DME, 328xi today. With radio off & quiet cabin, I could hear a low level “click” from the JB area when activating the relay, and the voltage value went from 0 to 12.2 when KL.87 was active. So hopefully when you apply ground to Pin #5 of X60551:
1) You will hear a click from the JB;
2) See 12+ Volts Value in KL.87 bar graph using INPA Messwertblock 1;
3) Have engine fire when Starter is cranked (OK to leave ground applied for that purpose, but disconnect it AFTER test Start & engine shutdown).
4) Be aware that there MAY be some short within the E-box given the history of coolant ingress, so be ready to remove jumper if any sparking, etc.
5) If you have NOT already done so, I would recommend thorough inspection of the DME and all components in the E-box, with use of a heat gun, heat lamp, or at least incandescent light bulb for radiant heat for 12 to 24 hours (to evaporate moisture), along with disconnection & inspection of connector pins & sockets, particularly X60005. Use Electronic Contact Cleaner to clean pins/ sockets if any corrosion is found. Water-damaged electronics can OFTEN be “resuscitated” by thorough drying and cleaning.

Reply from the issuer:

Okay, I think we are getting somewhere!

I have some wiring logic backwards but I have this figured out. I was able to find continuity on the WHITE/GREY wire!

Here are the results:
1. X60005 female connector Pin #13 goes to the X60551 FEMALE connector Pin #5 which is also WHITE/GREY. I was testing the male side of the X60551 connector thinking that wire never leaves the E-Box but that is not correct. The WHITE/GREY wire travels out of the E-BOX and comes back into the FEMALE connector of the X60551. See pics.

2. The WHITE/GREY wire continues on the male side of the X60005 connector Pin #5 and it actually loops into the X6011 male connector at Pin #5 then from there it changes wiring color to RED/GREY!! Sneaky! I’ve verified it by testing continuity from X60005 pin 13 to X6011 Pin #5 on the male side, just before it switches to RED/GREY.

So at this point, I think I am ready to apply ground.

Advice:

To simply test the DME Main Relay (K6300) to see if it functions, ALL you have to do is apply a ground, EITHER at X11010/Pin#1, OR at X60551/Pin#5 (latter assuming continuity between X60551 & X11010 ;-). Since the Relay coil is powered by Terminal 30 (Battery Power), you do NOT need ignition ON. If you get voltage at one of the sockets for fuse F37, then the relay is working (click is optional ;-). Here is F37 & K6300 circuit, simplified:

https://www.newtis.info/tisv2/a/en/e90-335xi-lim/components-connectors/components/f-fuses/f54-fuse/i1ukJnB

I have read your last post, and what I would suggest is to FIRST test for operation of the Relay ONLY, as described above. Do this with X60005 disconnected from the DME & Ignition OFF. IF you get relay click and 12V+ at F37, when you do this, then remove ground jumper, reconnect X60005 and all OTHER disconnected Connectors, and then apply ground at X60551/Pin#5, check for 12V+ at terminal 87 using INPA, and if good to go, Crank the Starter & see if it fires.

Finally, The car is alive!!!

Seriously have no idea how and what I did that I didn’t do before.

I plugged all of the connectors back on the JB/JBE. Hooked up and tested the DME Relay, had my wife touch the ground as I was literally in front of the JB. Heard the click several times confirming the location of the sound. It was definitely the K6300 clicking.

Next, plug the DME back in and opened INPA. Load the LIVE Data > MWB1 and instantly saw voltage on the KL87. I was like, no f**ing way, hit the start button and it started right up!!

Ran the codes, which still showed 2ACB/2ACC along with a bunch of other codes. I went ahead and clear them an now no codes!! I’m so happy and yet so dumbfounded on why it didn’t start when I replaced the DME and now it does. Only thing was maybe re-seating an assortment of connectors and fuses fixed it.

Credits to @Ov3rrun and @gbalthrop

Best inpa cable only 18usd:

https://www.uobdii.com/wholesale/bmw-inpa-k-can-best-quality.html

The post How to fix BMW 335xi water pump failure with INPA? appeared first on UOBDII Official Blog.

Review 1: Have Tech Stream, not used Carista

Tech Stream software is free. The cable is about 15usd.

For the Tech Stream software free download source and driver installation guide, here you can go:

Toyota TIS Techstream 15.00.026 14.30.023 V14.20.019 Free Download & Win7 Setup

I have not used Carista.

Review 2: Each one has their pros and cons

Tech stream is probably better if you want to get into serious levels of servicing. 
but for just basic customizing might be better with carista.
its cheaper and easier to use.

Although I am really bitter about carista charging you for the adaptor then the app, their system works pretty good.
I have it and have done some mods to my friends FRS and to my girlfriends mom’s camry (plus clear codes)
Will be using it on the tacoma for some customizing when I get in next month.
Used it on my VW (to see how it was) and figured it sucks, but then again I own the VW software as well and have gotten extremely familiar with it.

If you don’t know what you’re doing you can also screw things up with tech stream. from what I understand with Carista you can’t as it doesn’t go deep enough, and its very user friendly.

If all you want to do is reset oil change reminders, and do some customizing, go with carista. Even the free version of carista does some scanning just doesn’t go in depth into SRS or ABS levels, along with some other things. But it will let you do the basics of things you’ll likely have to do.

Review 3: TS cable is worth it

Just recently received the TS cable and software. I thought I would’ve needed to create a virtual machine on my Windows 10 laptop, but didn’t need to. Followed the instructions to setup and I was in. Disabled the seatbelt chime and confirmed the REV1 update was performed. Looked like other things to tinker with too, so it was worth it.

I’m sure the Carista route is easier, but the TS route wasn’t too complicated.

No virus’s or malware here.

Purchased techstream from

https://www.uobdii.com/wholesale/cheapest-mini-vci-for-toyota-single-cable.html

I did the customary seat belt alarm turn off, TSB update, and have cleared ECU/TCU memory (vehicle will need to learn trims/transmission learning again, takes some driving). I know there’s logging capabilities, DTC reading and clearing, PIDS to monitor.

Below is the version I’m running with instructions.

https://blog.uobdii.com/toyota-tis-techstream-v12-20-024-download-and-setup-on-win7/

This is exactly what I did. Scroll to techstream 12-20-024 cracked. Download that version and follow the install instructions (exactly as written) a little lower under TS install windows 7, works for other windows versions. Make sure after installed you click setup>select vim>select obd cord you’re using. Get that far and should be good.

Review 4: full list of settings available on the Carista

I posted a full list of settings available on the Carista app in my build.
Here’s what you can do:

Doors / Windows / Remote

Blink turn signals when locking/unlocking with remote
*YES* / NO

Beep when locking/unlocking with remote
*YES* / NO

Volume of beep when locking/unocking with remote
OFF / 1 / 2 / 3 / 4 / 5 / 6 / *MAX*

Warn (beep) when door can’t be locked because it’s still open
*YES* / NO

Warn (beep) when sunroof is still open when locking doors
*YES* / NO

Panic function on remote
*ENABLED* / DISABLED

Re-lock doors automatically if you unlock, but don’t open a door
*YES* / NO

Re-lock doors automatically if you unlock, but don’t open a door within…
30 SECONDS / *60 SECONDS* / 120 SECONDS

Unlock doors via remote
DRIVER’S DOOR ON 1ST PRESS, ALL ON 2ND / *ALL DOORS ON 1ST PRESS*

Unlock doors via physical key
*DRIVER’S DOOR ON 1ST PRESS, ALL ON 2ND* / ALL DOORS ON 1ST PRESS

Unlock doors via smart key (door handle button)
*DRIVER’S DOOR ON 1ST PRESS, ALL ON 2ND* / ALL DOORS ON 1ST PRESS

Auto-lock all doors
DISABLED / *WHEN SHIFTING INTO GEAR* / WHEN VEHICLE STARTS MOVING

Auto-unlock all doors
DISABLED / *WHEN SHIFTING INTO PARK (P)* / WHEN DRIVER’S DOOR IS OPENED

After locking with smart key, don’t allow re-opening within…
0.5 SECONDS / 1.5 SECONDS / 2.5 SECONDS / *5 SECONDS*

Smart key location to start car
FRONT SEATS / *ANYWHERE IN VEHICLE*

Instruments / Display / Dings

Engine start indicator
*ON* / OFF

Display odometer after ignition is turned off for…
30 SECONDS / 1 MINUTE / 10 MINUTES / *OFF*

Key-in-ignition ding sound
*SLOW* / MEDIUM / FAST

Ding when headlights are left on
YES / *NO*

Seat belt warning ding (driver)
ENABLED / *DISABLED*

Seat belt warning ding (front passenger)
ENABLED / *DISABLED*

Lane-change turn signal auto-flasher count
OFF / 3 FLASHES / *4 FLASHES* / 5 FLASHES / 6 FLASHES / 7 FLASHES

Remote low battery warning
*ON* / OFF

Rear parking sensor range
NARROW / *WIDE*

Mute parking sensor when stationary for more than 3 sec.
YES / *NO*

Parking sensor beep volume
1 / 2 / *3* / 4 / MAX

Activate parking sensors in neutral (N)
*YES* / NO

Enable rear parking sensors when in neutral or forward gear
REAR / REAR CORNER / *OFF*

Dash display mode
*ALL* / UNDISP

Lights

Daytime running lights
*ON* / OFF

Coming-home lights duration
OFF / 30 SECONDS / *60 SECONDS* / 90 SECONDS

Auto headlights activation threshold
*DARKEST* / DARKER / NORMAL / LIGHTER / LIGHTEST

Instrument lights dimming sensitivity
DARKEST / DARKER / *NORMAL* / LIGHTER / LIGHTEST

Instrument lights restoring sensitivity
DARKEST / DARKER / *NORMAL* / LIGHTER / LIGHTEST

Dim interior lights after…
7 SECONDS / *15 SECONDS* / 30 SECONDS

Turn on interior lights when you shut off engine
*YES* / NO

Turn on interior lights when you unlock doors
*YES* / NO

Turn on interior lights when smart key in range
*YES* / NO

Interior light control
*ENABLED* / DISABLED

Heater & A/C

Temperature dial calibration
-2°C / -1°C / *NORMAL* / +1°C / +2°C

Auto-increase blower speed when front defroster is on
YES / *NO*

Auto-turn on A/C when AUTO button pressed (if needed)
*YES* / NO

Deactivate front defroster when AUTO button pressed
*YES* / NO

Open vents to outside air when ignition is turned off
*YES* / NO

Fan speed reaches its target…
SLOWLY / *NORMALLY* / FAST

To be upgrading…

MINI VCI cable + techstream software only 15usd:

https://www.uobdii.com/wholesale/cheapest-mini-vci-for-toyota-single-cable.html

The post Carista or TIS Techstream for Toyota tacoma appeared first on UOBDII Official Blog.

Installing GM MDI software under windows xp, I keep getting message that  “file C:\Program Files\GM MDI Software\Dynamic Link Libraries\bvtx-vci-helper.dll cannot be found”, installation software stops working, weirdest thing is that file exists in mentioned folder.

Solution:

I Had to move to version 8.3 which works on most of my machines,
this downgrade solved the problem, it seems that ver 8.3 works with .net 4.0 but 8.5 requires .net 4.5 which don`t exist for xp.

Here is the source of GDS V8.3.103.39:

https://www.uobdii.com/wholesale/gm-mdi-gds2-tech-2-win-software.html

Remark:

I had same error message on xp installing 8.3 version and solution was install c++ redist. 2010 package and all solved ok.

GM MDI Device: https://www.uobdii.com/wholesale/gm-mdi-2-with-wifi-card.html

The post Fixed! GM MDI software 8.5 xp 32bit bvtx-vci-helper.dll missing appeared first on UOBDII Official Blog.

Xhorse Brand new Chip Programmer Mini Prog is comming, It is portable and support multi-function. It has different test head and support different adapters and cables. It work with Xhorse app Via Wifi and Bluetooth.You can use it anywhere anytime.

Xhorse Mini Prog Functions:

Repair multiple modules
Data local & cloud storage
Edit Data on Xhorse App
Read&Write EEPROM data and MCU data
Directly Read & Write Data free from soldering chips
More Functions Coming Soon

Mini Prog Review:

The Xhorse handheld MINI Prog programming pen is an independent device for reading and writing data. It can store data without relying on a PC. For most 8-pin ICs, you can use a pressure contact to read and write data. Various special models will also be equipped with corresponding adapter, such as BMW CAS adapter, Porsche BCM adapter without soldering, Land Rover adapter, etc. . . . . (These adapter boards are also expected to work with VVDI PROG,VVDI Key Tool Plus). Built-in battery and wireless data transmission, no need for external power supply and U disk to transfer data.

In terms of security, the hand-held programming pen is preset with a pin detection function: before reading data, it will detect whether the pin is in normal contact, to avoid the possibility of unreadable or lost data due to unclean pin processing. Backup function of data will also be added-when the data is successfully read, the system will automatically back up the data to the memory or cloud storage according to the operating time to avoid data loss caused by the lack of backup data.If you use the MINI Prog programming pen to read the data, the data is automatically uploaded to your cloud account. Using the VVDI MAX, you can directly read the data write start without switching the device back and forth on the computer.

The post Xhorse Mini Prog Chip Programmer Review appeared first on UOBDII Official Blog.

Hi guys, this article shares the test reports on working DBR III emulator for Chrysler Crossfire 2005 including TPMS Relearn 2007 Roadster and ABS bleeding, then how to get the DRBIII Emulator software setup for Micropod 2.

Car model and year: Chrysler Crossfire 2005 European with RDB III definitely

Working emulator for Crossfire:

Bought Micropod 2 Clone which works with the Enhanced DRB 3 Emulator. Cost is about $170 (Chinese dealer said only windows XP or Windows 7 (32 bit) would work, my laptop came with a Solid State Drive with Windows 7 Professional (64 bit) installed. Turns out my laptop with Windows 7 Professional (64 bit) works just fine.).

Used this product on 2005 srt6 coupe and 2007 ltd roadster (us versions). It takes some work to get the software set up. But once you do, it works fine.

I have only used the emulator to perform a TPMS Relearn (2005 SRT6) and diagnose a defective air bag control module (2007 Roadster). I have tested some other diagnostic functions, but I am not very familiar with its additional capabilities. I think it will perform many other DRB III functions.

Attached is a DRB III manual:

Actually, many users have successfully used the DRB III emulator with Micropod II.

Question 1: does that work and does it include the ABS bleed?

Answer : Page 90 references the ABS (Section 11) in the DRB III Manual, page 11.2. I ran the emulator on my 2005 SRT6 Coupe today and tested the ABS function. Attached is a printout of all the ABS functions and the options for testing and diagnostics under each of those functions. Unfortunately, I did not find any option to bleed the brakes. Page 90 of the manual indicates Brake Bleeding is located in the ABS Section under Miscellaneous Functions. However, when running the emulator in Crossfire mode only the following options are listed under Miscellaneous Functions: 1) Erase Zero PT-Offset Error, 2) Relearn Steering Angle.

Images: ABS bleeding with DRB lll Enhanced Emulator and Micropod ll

Question 2:

What exactly do I need to purchase to have the Enhanced DRB 3 Emulator up & running? Need to get the 2 new TPMS wheels sensors (installed on Driver-Side) communicating with TPMS Module & turn of the TPMS warning light.

Answer:

You will need this:
1) Good computer knowledge

2) A laptop with a clean Windows XP or Windows 7 installation on it. Nothing else. Networking and Updating turned off.

3) A MicroPod 2 wiTech 17.04.27 for Chrysler Diagnostics and Programming

(A CD with most of the software you need, along with the MicroPod 2 and USB cable comes with, here wiTech v17.03.10 free download mega)

I initially made the mistake of purchasing the emulator software separately for about $250, because I thought that was necessary. Fortunately I never opened the package and was able to get a refund. It is not necessary to purchase any admegaditional software.

Looks like the Micropod II, with all the software and cable, is now on sale for $139. I paid about $170.

4) Follow the last paragraph instructions on: Windows 7 Pro 32bit install DRBIII Emulator for Micropod 2

5) A TPMS tool to “chirp” the sensors so the vehicle can read them (I use the Autel TS601)

6) Perform a TPMS Relearn sequence using DRB III Emulator. Chirp each wheel when requested by the emulator. (Takes about 5 minutes)

***I have run the sequence to perform a TPMS relearn using the DRB lll Enhanced Emulator and Micropod ll. The attached file shows the sequence I followed along with a snapshot of each displayed screen from the Laptop.

Images: TPMS Relearn 2007 Roadster with DRB lll Enhanced Emulator and Micropod ll

I stopped at this point, because I am not performing a relearn at this time. Please note: magnets are not required when performing activation of the wheel sensor using a TPMS tool.

Someone tested and reported: In fact, I did not need to buy the “TPMS tool” to trigger the sensors. I went back to Discount Tire, who installed the new Dill sensors and they were happy to do it for me while ran the DRB III emulator to trigger the learning sequence. I happily drove home with no TPMS light – first time since I bought it from the original owner earlier this year!

I followed this instruction to install DRBIII Emulator for Micropod 2 on Windows 7 Pro 32bit and it worked perfectly:

1: Start with a fresh install of Windows 7 Pro 32-bit.

2: Install all the necessary drivers for your laptop.

3: Set the clock to the current date and time. (It didn’t work when set to 01/01/2017)

4: Connect to WiFi and performed all necessary Windows Updates.

5: Copy the “wiTECH_Install_17.03.01” folder to the desktop.

6: Install the provided version Adobe AIR.

7: Install the provided version of Java.

8: Install wiTECH 17.03.01.

9: After you have finished installed everything, when you get popup messages from Windows Firewall to allow or block any applications, click “Allow”.

10: When you get a popup for AdobeAIR and Java to update, click cancel and do NOT update either AdobeAIR or Java.

11: Open “My Computer” and in the upper left of the window, click on “Organize” and then select “Folder and search options”.

12: Click on the “View” tab and under “Hidden files and folders” select the radio button for “Show hidden files, folders and drives”. Also, uncheck the option for “Hide protected operating system files (Recommended)” and then at the top of the window, click the “Apply to Folders” button.

13: Navigate to “C:\ProgramData\wiTECH\jserver\data\core\stubs” and you will find three installers.

14: Install the DRBIII Emulator stub.

15: Wait for a popup to appear that states the security certificate isn’t valid and click “OK” to allow the software update to proceed. Another popup will appear and the software update will run. After it completes, close the wiTECH window if it opens.

16: Install the Enhanced DRBIII emulator stub.

17: Again, wait for a popup to appear that states the security certificate isn’t valid and click “OK” to allow the software update to proceed. Another popup will appear and the software update will run. After it completes, close the wiTECH window if it opens.

18: Install the K-Line stub.

19: Again, wait for a popup to appear that states the security certificate isn’t valid and click “OK” to allow the software update to proceed. Another popup will appear and the software update will run. After it completes, close the wiTECH window if it opens.

20: Connect the MicroPod2 to the vehicle, then connect it to the computer.

21: A popup window will appear to install software. Click “OK”.

22: After it finishes, start wiTECH 17.03.01 and wait for the screen to show up with the MicroPod2 and IP address of it. You will see a “Launch DRBIII” button in the lower right corner. Ignore it as they do not properly open the emulator.

23: Create a shortcut on the desktop and enter the following into the “Path” field.

http://localhost:9876/launchExternalApp?appName=drb_iii_enhanced_emulator&locale=eng_ENG&deviceIp=172.22.22.22

24: Disable the LAN and WLAN network connections and never connect to the internet again.

25: Click on the shortcut and you’re set! The DRBIII emulator will open and give you the choice to select several different vehicles.

Enjoy!

MicroPod 2 wiTech 17.04.27 for Chrysler Diagnostics and Programming 139usd only

https://www.uobdii.com/wholesale/witech-micropod-2-diagnostic-tool-for-chrysler.html

The post Working DBR III emulator for Chrysler Crossfire 2005 appeared first on UOBDII Official Blog.

How to use Launch X431 ProS Mini to activate the PCM Aux input on 2018 Porsche 991.2 ?

Car model and year: 2018 Porsche 991.2

Purpose: activate the PCM Aux input

Porsche diagnostic scanner:

with Launch X431 V+ Pros Mini

was able to activate the Aux setting without any problems.

Look at the screenshots for X431 ProS Mini activating the Aux input on PCM 4.0
First go to the system PCM/CDR. Search for “Aux”. Select Aux_IN

Change Aux_IN to “On”

I also added a Aux cable to the green connector on the back of my PCM. It connects to Pins 1 (Ground), 2 (Right) and 7 (Left).

Enjoy!

www.uobdii.com

The post Launch X431 Pros Mini activates 2018 Porsche 991.2 Aux input appeared first on UOBDII Official Blog.