When you click on links to various merchants on this site and make a purchase, this can result in this site earning a commission. Affiliate programs and affiliations include, but are not limited to, the eBay Partner Network.
Troubleshooting & Technical Questions & ModificationsHave technical or modification questions about the Crossfire?
Find out the answer, or give advice in here!
Finally I added the jumper to the via, I practised before I attempted it, when you see how small the jumper is in length it is a bit intimidating. I modified the tip of the iron, tinned the via and used a 28 AWG tinned copper wire. It ain't pretty but hopefully it will do the job. The jumper was L shaped for holding when it was fitted and trimmed flush when soldered in place.
If I can ask a question. Which specific point on the board that is being soldered to is considered the "via". I do not see a marking on the board with that name. thanks
I continue to use Win 7 Professional 64 bit and no soldering modification. Working fine on 2018 through 2025 Micropod II. That is just my experience. Have software and will send you a disc if you need one, for free. Just message me.
Thanks for the offer. I just ordered a micropod and I will see what comes with it. (e.g. software disk). I dug up an older HP laptop and reinstalled an operating system. I test loaded some software that was posted and it seemed to take it. The you tube site I visited talks about three DRB software packages (Base, enhanced, K line).
I installed the micropod software that came with the module from OBDtools on an older HP (tank) portable with Win 10. It did not work and was extremely slow
I then installed the software on a newer (2018 Lenovo) with Windows 11. I had the same problems as UrbanE in the DRBIII software button not showing up on the emulator. I installed it may times utilizing advice from the vendor, You Tube and various posts on this forum (thanks everybody).
Slow methodical installation
Certain versions of Adobe Air
Plug in sequence
etc.
I could get it to think it was a later model Chrysler with the emulator, but never got the DRBIII button.
Finally, I used the short cut method to activate the DRB software directly and it supposedly did not show up in the registry
So I started fresh. I had an old Dell 8 Windows 10 pad. Did the install again.
I got to the place where the DRBIII button almost showed up (said it needed to be updated and hung up on the DRB III update (enhanced) process. After a very long wait, I bailed.
Again it communicated with the Crossfire, but DRBIII would not fire up. I could see the topology of an 2017 Alfa Romeo 4c, so it appears that the base Wi Tech software works and the module is working.
I had hope that the Adobe Air version fix would work.
I then tried the DRBIII short cut fix on the Dell 8. Was not found in the registry.
I think the main problem is the DRB III software. There are a few to many files (Apps and MSI's) in the provided software (CD) as compared with previously described efforts.
DRB stub snapshot of the provided DRBIII software on the CD
DRB
Enhanced DRB
K line
This is compounded by the confusing Microsoft install, modify and repair software. Sometimes it is hard to determine what is installed (app and registry).
I almost thought I had it beat when the "update" button showed up in the DRBIII button place (but it would not update).
Venting a little bit......
All I want to do right now is check some sensors on the convertible top (easily with DRBIII software).
I think the 8 inch Dell pad with Windows 10 will work (based on the Dell 11" tablet with Windows 10 working on the forum).
Just have to get by the DRBIII install problem.
Then I can worry about the K line and soldering issue.
I installed the micropod software that came with the module from OBDtools on an older HP (tank) portable with Win 10. It did not work and was extremely slow
I then installed the software on a newer (2018 Lenovo) with Windows 11. I had the same problems as UrbanE in the DRBIII software button not showing up on the emulator. I installed it may times utilizing advice from the vendor, You Tube and various posts on this forum (thanks everybody).
Slow methodical installation
Certain versions of Adobe Air
Plug in sequence
etc.
I could get it to think it was a later model Chrysler with the emulator, but never got the DRBIII button.
Finally, I used the short cut method to activate the DRB software directly and it supposedly did not show up in the registry
So I started fresh. I had an old Dell 8 Windows 10 pad. Did the install again.
I got to the place where the DRBIII button almost showed up (said it needed to be updated and hung up on the DRB III update (enhanced) process. After a very long wait, I bailed.
Again it communicated with the Crossfire, but DRBIII would not fire up. I could see the topology of an 2017 Alfa Romeo 4c, so it appears that the base Wi Tech software works and the module is working.
I had hope that the Adobe Air version fix would work.
I then tried the DRBIII short cut fix on the Dell 8. Was not found in the registry.
I think the main problem is the DRB III software. There are a few to many files (Apps and MSI's) in the provided software (CD) as compared with previously described efforts.
DRB stub snapshot of the provided DRBIII software on the CD
DRB
Enhanced DRB
K line
This is compounded by the confusing Microsoft install, modify and repair software. Sometimes it is hard to determine what is installed (app and registry).
I almost thought I had it beat when the "update" button showed up in the DRBIII button place (but it would not update).
Venting a little bit......
All I want to do right now is check some sensors on the convertible top (easily with DRBIII software).
I think the 8 inch Dell pad with Windows 10 will work (based on the Dell 11" tablet with Windows 10 working on the forum).
Just have to get by the DRBIII install problem.
Then I can worry about the K line and soldering issue.
I tri
Brother, trust me when I say, I feel your pain. It took me months to get it to launch.
Stay at it, it should lork
as per previous, I know it runs on windows 10
i have it running on four different laptops and they all work.
3 -Dell
1-HP
The pc should stay offline once this is installed, if not. the device will update (I think 2.0) and it will break it from working. You can downgrade it with the right software
It turned out that the software (Wi tech and DRBIII) had loaded up correctly enough for the DRB III to fire up from the DRB III shortcut. (This is all I need).
So the instructions are all correct for loading the software on to the machine (in this case a Dell 8 tablet running Windows 10).
What was wrong was the instructions for calling the DRBIII program directly in the shortcut. I went back to basics on the syntax for the shortcut. The instructions in the previous forum post called in the shortcut the DRBIII program one name, yet the MSI installer in my CD disk called the DRBIII (enhanced) app another name. So the shortcut was calling for a program in the registry that did not exist.
To fix it, I essentially renamed the DRBIII program in the directory the same name that was embedded in the shortcut. Once the shortcut called the "right" program, the shortcut worked and I entered the DRBIII emulator.
I played with it enough to see that it was reading the OBD port and scanning correctly.
So my recommendation is to install the software (in this case Windows 10 on a tablet) as stated on the CD (and forums) and create the startup folder with the "correct name" of the DRB III advanced program. As stated in various posts, plug in the OBD2 port first, then the computer.
I have not "futzed" enough with the combinations of software to determine if you have to "tickle" the Witech software (launch) to be sure the "server" is running before you hit the DRBIII shortcut.
Then you need to start the DRB III shortcut.
The DRB III software looks like it is working (in a different window). I have not gone far enough into the application to understand about the K line and the possible soldering, but I have the K line software module installed and it is not complaining.
So I have no DTC codes with all the modules scanned, but I need to figure out how to use all the diagnostic routines to check sensors.
The first thing I am using the DRBIII software for is the convertible top. It gives me some good statistics on how many times the top operated correctly, but I need to debug a sensor or (hopefully a sync problem).
So, it is on to DRB III education.
One thing that I have discovered is that with an additional memory card (32 gig), I can download a significant amount of Crossfire documentation from the Crossfire forum onto the Dell Tablet....all in one place.
Thanks for all the folks in the present (and past) in getting me over this hump and hopefully future humps!!!!!!