One more quick update
I’ve just completed a third laptop and wanted to confirm that the adobe file below worked for
Win 10 64
Win 7 64
I used the original adobe file for the 32 bit.
Win 7 32

All three launch the emulator from the desk top shortcut.

I have also completed the solder mod on both micropods
I did them before I got the laptops working so I don’t know if they would have worked without the modification.

Great project, super interesting. thank you to all of you who have already completed your own installations and we’re really great in sharing the wealth of knowledge.

Super easy, just follow the steps.

Now I just need to read the DRB Manual.

 

Sticky ?

 

Ok. One more update. I’m goal was to come up with a real compact solution that I could travel with
Local buy and sell (Kijiji) Dell Venue 11 Pro 5130 $40.00
Win 10
32 bit
intel Atom
“tablet” with optional detachable keyboard
loaded the adobe air for 32 bit and followed all the steps
it worked
super portable table with 9 hour battery life

BEST PART IS THAT THE TABLET IS A TOUCH SCREEN. Just press the DRB button no mouse required. Size of an iPad. Perfect tool

 

Thanks - that's a fabulous update. I'm going to have to start looking for one of those Windows tablets!

 

My Dell Venue tablet arrives today, so I'm going to try to follow in your footsteps.
One question: What edition of Windows 10 did you use (Home, Pro)?

 

Update on my experience installing the emulator on the Dell Venue 11 Pro tablet .... it works!

I used Windows 10 Home, 32 bit OS and all the files on the CD/DVD included with the device. Apparently, there is already a digital license installed on these devices, which originally came with Windows 8.1 so I just needed a bootable Windows 10 media and the Windows 10 drivers from Dell's support website.

A couple of odd things occurred during the emulator installation steps which are worth noting:

After installing the DRBIII Emulator stub, I was prompted for and successfully installed the updates. I seem to recall getting a 404 error the last time I did this, which told me the servers were no longer responding.
During the update process, it also installed the Enhanced DRBIII emulator stub.
Apparently, it was a newer version than the one provided on the CD because I received a warning that the newer version was already installed, so I skipped the step of trying to install the one provided in the CD.

Installing the K-Line stub went as expected.

So, it all just worked and I'm very happy to have a compact solution that I can easily take on the road to help other XF owners in the area.

Thanks for the hint, UrbanE !

 

Try it in the car, and be sure it reads everything. Most of the new Micropods need the hardware fix.

 

I did try it in the car but only a few module scans. 'seemed fine.
My Micropod is at least 3 years old so it's probably ok.

 

Okay, a few questions while I have a few bucks to spend.

1) I have a laptop & can buy & install the software. Can it be installed on a flash drive?
2) I want to be able to check codes, reset the computer and minor things (no brake bleeding, hehe). I still need the Autel to actually help to reset the TPMS, right?
3) Big question… We have a 2003 Toyota Tacoma, 2005 Crossfire & a 2021 Hyundai Kona, will the software work on them? Or, am I better off buying a true scanner than the Autel for the Crossfire TPMS? I’m looking at bang for the buck. Thanks!

 

I can try to answer some of your questions...

1) I initially tried this. I was able to install Windows and the applications on an external flash drive but it was way too slow to be usable. I ended up installing it on an extremal SSD, connected via esata and booted from that device when wanting to use the emulator (also remembering to disable network access). I've since re-installed the emulator on a Dell Venue tablet, dedicated to that use.

2) You will need some device to 'chirp' the new sensors. In a previous post, someone mentioned using an Autel TS601. In my case, I want back to where I had the new sensors installed, along with the tires and they triggered it while I operated the emulator. I believe the device was some sort of Autel. I've heard that a strong magnet can also do the job but I have no firsthand experience.

3) I doubt that the emulator with work with anything other than a Chrysler. There are only a few vehicles to choose from when you start the emulator. I believe the other is a Sprinter van. Someone more knowledgeable will need to answer that question.

 

The original DRB III was THE Chrysler (and Dodge, Jeep, Plymouth, etc.) dealership diagnostic tool for something like a decade, until 2007 when it was replaced by newer technology. So the DRB III Enhanced Emulator being discussed here can do a LOT of Chrysler brand 2007 and earlier vehicle diagnostics / settings, but NOT other brand vehicles. It includes some generic OBD function which is all about emissions, but in that mode may do no more than the $20 generic OBD units. DRB III is all about servicing Chrysler vehicles from a while ago.

Special historical aside: When the original DRB III was retired in 2007 the new dealership diagnostic tool had to include a DRB III Emulator for older vehicles. Like my 2007 minivan which depends on DRB III software for many specialized tasks. What was NOT updated at the time was software / hardware to deal with the Chrysler / Mercedes "combination" vehicles like Crossfire and Sprinter van. Those required an additional Multiplexer "cable" (with a sizable box on it) to communicate between the CAN in Crossfire (and Sprinter) and the DRB III, along with special software cards which plugged into the DRB III. With the Chrysler - Daimler 2007 divorce those features were not included in the new dealership Emulator system, so the original DRB III and Multiplexer and Crossfire software card were still required to service Crossfire. Only something like half the USA Chrysler dealerships were ever authorized to sell Crossfire, so a lot of dealerships never bought the special Crossfire tools (like Multiplexer and Crossfire software card). Then with the DRB III going obsolete for other Chrysler vehicles, the hardware was forgotten, lost, walked off, etc. Not until 2017 was an Enhanced DRB III Emulator updated into the dealership wiTECH system - which finally included Crossfire (and Sprinter) capability!

With the various ownership changes of Chrysler the Enhanced Emulator software got out, along with the microPOD II being cloned in China. Hence we can make these systems to keep Crossfire alive and functioning. The DRB III never had anything like the capabilities of native Mercedes dealership systems, but did need to take care of main vehicle features. Since the Crossfire TPMS has nothing in common with Mercedes, it was a Chrysler system crammed into SLK architecture, the DRB III Emulator is the only access for that. Same for a few other things, like the convertible top, later changes to the more elaborate airbag system in 2007 Crossfire, perhaps a few other items.

When TPMS sensors must be triggered for the TPMS Relearn process (initiated only via DRB III) a fancy TPMS tool is not required. While the original factory TPMS sensors needed a magnet to trigger, that method went away for more modern sensors. The universal trigger is now a low frequency radio signal which can be sent from a pretty cheap single purpose device. Reading the code transmitted by the sensor (which includes the sensor ID) takes a more elaborate TPMS tool, but it could be an outdated tool version no longer up to date for new cars.

Congratulations and thanks for the people in this thread sharing tools to keep Crossfires doing their things!

 

Thank you again for your input, what would we do without it. We would be running around in circles for sure.

 

Actually, it was a good history lesson. Some of it is not 100%, but the broad strokes are right, and it gives insight into how we came to be able to get this inexpensive tool to use on our cars. Without this evolution, we would be out in the cold on certain aspects of our cars.

 

Have an '04 Crossfire and collect scanners. Have Windows, Linux, IOS, and Android systems available. Build PCs as a hobby/ Been through the thread but got a bit confused as to exactly what I need. Please list parts/software and sources I need. Windoze preferred.
Thank you.

ps have Windows 7 available but prefer later versions.

 

It is all covered in this thread.

 

Many things are covered and my brane overheated. All I am asking for is a simple list. I do have a Windows 7 tab but prefer a Win 10 tab with touch..
For example I found Adobe Air but seems to be for Android only. Also when I try to download the Chrysler software I get "The file you are trying to download is no longer available".
Please help.

 

This post should tell you all you need to know to get it working; https://www.crossfireforum.org/forum...tml#post928667
That's what I followed to get my first one running.

Although Windows 7 Pro 32bit is part of the 'success recipe' others have had success with other Windows versions.

 

Is this the correct device ? https://www.obdii365.com/search/?q=M...7.04.27&DirID=
Do I also need the hard disk ?

 

No bunny nose ?

 

See post #197
use that adobe file
if running 64 bit
win 7
or Win 10

If you need specifics PM me