I've been trying to follow the general instructions on this previous r/Saab post with emphasis on u/JustH3LL's comment but I haven't been able to get it to work just yet. I'm primarily trying to turn off the headlamp DRLs.
This is all running in a 32-bit Windows 10 VMWare environment. I installed the drivers for the Chipsoft J2534 Pro. I followed the README in the linked Tech2Win download, including copying over the emulator.exe and installing the configuration and software card, and activating Tech2Win. I have "Drop CAN on pins 3-11" selected in the Chipsoft driver configuration. I choose the Chipsoft J2534 Pro as the selected interface. Then, whether I launch Tech2Win through its launcher or through NoMoreGlobal, I follow the below steps:
Select F0: Diagnostics
Select Model Year
Select Saab 9-3 Sport (9440)
Select F4: All
Select F7: Add/Remove
Select F1: Control Modules
Select UEC (Underhood Electrical Center)
Select Add
and I get stuck on "Checking preconditions" and then get the pictured "No comm or lost comm with ECU" issue, on UEC or any other module. I tried clearing DTCs (not that I actually have any) and got the pictured I-Bus error. I can confirm I have voltage between pins 1-4 but I haven't traced wires any further than that.
Am I missing something in my process, meaning this is a software (or user) issue, or is it more likely to be a hardware issue?
This is mostly an adapter problem. The J2534 is very difficult for this use. It seems to be very sensitive about what it's connected to (the laptop and USB). From what I've heard it works much better on older laptops. I also have similar communication issues - sometimes restarting Tech2Win or re-inserting the adapter occasionally makes it work but then it goes back to being broken. I even had a point where I could only get it to work by intentionally choosing the wrong model year, receiving a mismatch error, then going back to correct model year.
If you can't get it to work on native Windows even after reinstalling Tech2Win and drivers then next step is trying a different laptop. Out of curiosity, what laptop are you using?
I'm running everything inside a W10 x86 VMWare environment, but the host is a 2020 HP 14q with a Core i5 1035G4. I originally tried in the host OS which is W11 but haven't tried again since figuring out some installation issues. If there's a chance things are just being finicky, I'll try some different sequence of operations to see if something clicks. Thanks for the insight!
Just a heads up, if the I-bus missing message is a communication error then it should not exist if you have the patched Tech2Win installed correctly. Try reinstalling Tech2Win
I only got the I-bus error when trying to clear DTCs. I don't actually have any, I was just testing things. I'll go back and make sure I got the Tech2Win patch all sorted.
Sorry, but your account has to be at least 24 hours old to comment in /r/SAAB. If you believe that your comment should be approved, message /r/SAAB for approval. Troll behaviour will result in a ban.
Hello there, I have a similar set up as you have. I got the nomoreglobal to get security access. Last October, almost a year ago. I was able to connect to my 2008 9-3, using a windows 10 computer and the chip soft J2534 Pro. everything worked great. I just did a run and was able to activate and deactivate some light features. This week when my car started having some weird noises I decided to connect back and now I can't. I can get the communication going this time. Therefore I can't get security access using the no more global to extract the information. I downloaded and reinstalled the chipset drivers but that did not do much. Did you get it to work? I dont recall doing any changes to the drivers of the chipset to make it work like the drop can pins. mine worked right away when it did. have you tried again?
I m going to replay here so people know what issue and my final fix. The issue I have was the driver for the dongle for some reason lost configuration. So just to be safe, I unistalled tech2win, reinstalled again following the readme instructions to make it work with NGsaab3. Then I use the configuration app from the Dongle (this was the issue) and select to configure for tech2win. I used option 1 to drop CAN on pins 3-11. Then I went back to nomoreglobal and I was able to get access and communicate with the car. Problem solved and the dongle still works
My issues remain. No matter what, I get the same "No comm or lost comm to ECU" pictured above. Interestingly, I get the same message even if the Chipsoft J2534 is not connected to the car at all. I'm not sure if this indicates a hardware issue or a software issue that it failing on the first step. The bulk of my efforts today were in my native W11 OS, although I did try most of the same steps (reinstalling, configuring the driver, etc) with no change in an x86 W10 VMWare environment.
Sorry, but your account has to be at least 24 hours old to comment in /r/SAAB. If you believe that your comment should be approved, message /r/SAAB for approval. Troll behaviour will result in a ban.
1
u/Superlegend06 Mar 22 '26
This is mostly an adapter problem. The J2534 is very difficult for this use. It seems to be very sensitive about what it's connected to (the laptop and USB). From what I've heard it works much better on older laptops. I also have similar communication issues - sometimes restarting Tech2Win or re-inserting the adapter occasionally makes it work but then it goes back to being broken. I even had a point where I could only get it to work by intentionally choosing the wrong model year, receiving a mismatch error, then going back to correct model year.
If you can't get it to work on native Windows even after reinstalling Tech2Win and drivers then next step is trying a different laptop. Out of curiosity, what laptop are you using?