Micropod 2 clone working on DRB iii emulator

What’s DRB iii emulator?

DRB iii emulator will emulate Your micropod2 to the DRB-III Diagnostic Scanner ,That special for older model Chrysler, Jeep, and Dodge from 1998-2007 Year,Which is Non-CAN system.
Here DBRIII funtions manual.
You also will need a High Quality micropod 2 clone or VCI POD,some parts of micropod 2 clone wont working well on DRBIII .
Here You can download Witech 1.0 and DRB iii emulator

How to get Enhanced DRB III Emulator to work:

• 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 ,Then The DRBIII emulator will open and give you the choice to select several different vehicles.

Note: The vehicle must be connected in order to launch the DRB III Enhanced Emulator.

Micropod 2 clone DRBIII emulator Questions :

1. I did have DRBIII functionality, but only for the engine and transmission module (CAN bus), and no other modules (K Line).
2. I bought a micropod ii ,it works but only communicate with PCM modules ,others modules always error .

Answer : You need do Micropod 2 clones board modification:

Some Micropod 2 clones have a circuit board flaw. There is a chip variously marked as “27 TI MAP”, “55 TI MAP”, “65 TI MAP”, etc. that has a pin which should be connected to ground but isn’t. This flaw stops the PCI bus from being accessible. The result is that the PCM can be seen but not other modules.Fixing this required some delicate soldering. There are a couple of different ways, but I decided to solder a wire from pin four of the chip to a point where there is ground.

Here is the board before modification. The red box is the pin that needs grounding.