SaabCentral Forums banner

1 - 20 of 236 Posts

·
Registered
Joined
·
1,697 Posts
Yes they have been around on aliexpress along with mdi clones for sometime.
Nearly asked the same question on the mongoose cable thread as that has developed a following despite its relative cost.

Both options are now lower in price than the clone Tech2 however I reckon may only be viable for the later candi equipped cars.

Be nice to have a more robust alternative to the clone tech2.

Needs someone to dip their toe and report back
 

·
Registered
Joined
·
5,427 Posts
Discussion Starter #3
Well I'm going to give it a go. I ordered one direct from VXDIAG for $129 shipped. I already have Tech2Win setup and Saab GlobalTIS. With any luck this will work out and be a very inexpensive alternative to either a clone Tech2 at around $300 or the Mongoose at $480-$490.

When I get it I will report my findings.
 

·
Registered
Joined
·
1,697 Posts
There are some threads running over on MHH auto - the software is a vmware clone (XP) running on Win 7.

Some demo install videos on youtube

How to install VXDIAG GM GDS2 Diagnostic Tool:
https://www.youtube.com/watch?v=lxrBUgIks3s

How to install VXDIAG GM Tech2Win11.27:
https://www.youtube.com/watch?v=fgptweo2x24

As to getting in running with Saab and in my case european vehicles time will tell..........

30% of the price of a Tech2 Clone with potentially much better performance......... it has to be the way forward if the software side can be sorted.

May need a much higher spec laptop though as a downside to run a VM with any speed within the 64bit Win7.
 

·
Registered
Joined
·
5,427 Posts
Discussion Starter #5
The tech2win install will run under a normal XP install and I already have a version running that has the same 42 day never expires mod. I also already have SaabglobalTIS running as well. I have it installed in a parallels VM on my Retina MacBook Pro. I'm hoping that all I'll really need to do is install the specific software and drivers for the VCX nano.

We will see....
 

·
Registered
Joined
·
5,427 Posts
Discussion Starter #6
Just a quick update on this. It will not be shipping out until around Feb 15th due to the Chinese Spring Festival and many companies basically shut down for the holiday.

They are offering the special price of $99 for the USB only version and $109 for the USB/wifi version until Feb 14th. $20 shipping on top of that for either unit. They say they have a 30 day return policy with buyer responsible for shipping back to them.

I am hopeful that this will work out and be a decent alternative at a low cost.
 

·
Registered
Joined
·
163 Posts
I just got one in the mail yesterday... I'll keep you all up-to-date if it works, but it might be a few days.
 

·
Registered
Joined
·
5,427 Posts
Discussion Starter #8
I just got one in the mail yesterday... I'll keep you all up-to-date if it works, but it might be a few days.
I'll be very interested in your results. Are you running a native XP laptop or a VM? or Win7/8?
 

·
Registered
Joined
·
163 Posts
So just a quick update. I've only had a few minutes to play around.

Installed the drivers/Tech2Win under Windows 10 x64 (no virtual machine) and everything installed just fine, though it didn't copy over the included Tech2Win memory cards. It installs GM MDI manager even though opening it comes up with "Not Connected to MDI" and doesn't do anything else. I set up a SAAB NAO V9.250 bin for Tech2Win and it'll launch and navigate the Tech 2 menus, and I can see the indicators for data flow from the vehicle to the "MDI" and from the "MDI" to the computer.

However, when trying to access features, I either get an i-bus error or it says wrong vehicle detected. The wipers occasionally come on and I hear the SID chime. Hopefully it's a simple setting I have to change. The default COM port was set to 9600 baud. Tried changing it to 57600 with no change.

If I were to get this working, we know we can use the existing methods to get security access, and therefore will have a complete Tech2 solution for cheap... it's just a matter of getting it working.
 

·
Registered
Joined
·
5,427 Posts
Discussion Starter #10
Glad to see some progress. I know from the Mongoose thread there is a bit about disabling the low speed CAN communication that is just a check box in that software.

I hope to get mine in the week after the 14th. I got the version with wifi and can also be used via USB. Which version did you get?
 

·
Registered
Joined
·
1,697 Posts
My worry is that this device will only support later vehicles.
This is an issue with the mongoose cable afaik apart from being too expensive...well in europe anyhow.
I asked a few questions over on MHH and the replies have so far only state 2010 onwards.
 

·
Registered
Joined
·
163 Posts
My worry is that this device will only support later vehicles.
This is an issue with the mongoose cable afaik apart from being too expensive...well in europe anyhow.
I asked a few questions over on MHH and the replies have so far only state 2010 onwards.
I'm fairly certain since this is basically along the lines of the Mongoose/MDI we'll never see support for the older vehicles.

Anyways, a few things:

The software installs the MDI apps, but the device never appears in the MDI manager (not sure if it should, though). However, using the "J2534 Configuration Application," there's a tab for "ALLScanner - VXDIAG" that you can check boxes for enabling monitoring.

Launching the GM NAO bin an choosing, say, a 2006 Caddy CTS 2.8 allows me to view live engine data (OF COURSE CYLINDER 3 IS MISFIRING! :evil:). So the tool's definitely legit and should work...

...however, so luck running the SAAB bin. Every time it tries to connect the car goes nuts and flashes lights/beeps/whatever. Won't communicate. If this is related to the Mongoose Low Speed CAN issue, then we're boned until driver is changed to have similar functionality. So close, but so far away at this point.
 

·
Registered
Joined
·
5,427 Posts
Discussion Starter #13
Well that's interesting. I will be running on an XP VM through Parallels on a MacbookPro. It will be awhile before it gets here so keep plugging away at it.

I would think any 2003+ 9-3 will essentially be the same in terms of this tool possibly working. Maybe the NG9-5/9-4X are what is considered 2010+?

But those typically would not use Tech2Win I would think...
 

·
Registered
Joined
·
163 Posts
Yeah, should work on any 2003+ 9-3. NG9-5 and 9-4X likely work with GDS2 or whatnot.

I tried installing everything into an XP VM, but I had an issue where the MDI driver install would have you try to register the MDI by plugging it in. Since it's not an MDI, this fails and it rolls back the software install. In my native Windows 10 install (and the video posted), the same screen pops up for a second and disappears automatically... I'm sure this has something to do with the automated install script that has you install everything.

The COM port speed thing I noted in an earlier post won't affect anything, really- that port is just for communicating with the tool for firmware updating and whatnot. When Tech2Win is launched a new port is created for actual diagnostic stuff.

It's nice that I can actually do some light diagnostic/monitoring stuff using the GM NAO bin that I can't do with, say, a cheap BT OBDII adaptor like live misfire/timing advance/whatnot, until we somehow convince them to update the driver to support SAAB I feel like we're stuck with a half-useful product. For what it's worth, I emailed the manufacturer and pointed out the issue (and how there's a workaround for the Mongoose) and asked them to look into it as there are many people who would kill to have a cheap, usable Tech2Win solution for their SAAB.

I should probably join up with MHH and see what else can be found out...
 

·
Registered
Joined
·
5,427 Posts
Discussion Starter #15 (Edited)
Well I was surprised when I came home today to find that the unit I ordered had been delivered. A bit snowy here today and the next few days so not sure I'll get much chance to play with it yet. But I have installed the VX manager and the GM and pass thru drivers. Not sure if both are needed.

I have a Tech2Win version installed already, not sure if I'll need the version that shipped with it.
 

·
Registered
Joined
·
5,427 Posts
Discussion Starter #16
Well I uninstalled the previous Tech2Win as it did not have the MDI manager installed. I installed the versions that came with the VXDIAG. Hopefully I will get to try it tomorrow sometime.
 

·
Registered
Joined
·
163 Posts
Well, keep us updated. Worst case scenario we know the device/drivers need more work. At least we can rule out if I got a bum unit, though.
 

·
Registered
Joined
·
5,427 Posts
Discussion Starter #18 (Edited)
Some minor progress. While I have not been able to try it out in the car yet. (EDIT - This is incorrect, it does not show up in the MDI Manager)> I have been able to get the interface to show up in the MDI Manager. The solution seems to be when setting up the Saab bin you need to create a new "button" in the configuration settings and make sure the interface is set to "search" and not a com port number.

I also had to launch the J2534 configurator directly from its own .exe icon. I then found the same tab for the ALLSCANNER-VXDIAG. Not sure if this is completely needed but some more testing should determine that

I have created a separate "button" for each of our 2 Saabs- one labeled "2004 Saab" and one "2008 Saab". When launching Tech2Win now the MDI manager shows a USB device as the interface and after accepting the MDI icon on the bottom of the Tech2Win screen shows the same interface after launching.

I hope to connect to the car before I drive to work in the morning to see if I can get communication established. I feel very positive that it will work. After I get it working "hopefully" and doing a few settings changes I'll experiment with the WiFi connection method.
 

·
Registered
Joined
·
163 Posts
Man, I didn't even think to check MDI Manager after opening Tech2Win (which creates the new serial device I mentioned above). Maybe there's something there that can get us working...
 

·
Registered
Joined
·
5,427 Posts
Discussion Starter #20
It definitely appears to be the low speed CAN/I-bus issue causing most of the issues. I keep getting an Ibus error on pin 1 (I-bus Missing) which is the single wire low speed CAN bus. I'm going to try the interface on another GM vehicle and I'll have my daughters 08 9-3 here over the weekend to confirm the same error I'm getting on the 04 vert. We are very close to having this work I believe. If the same type of fix can happen for this driver like the Mongoose which allows control of the Pin 1 I-bus we should be good.

Here's hoping anyway.
 
1 - 20 of 236 Posts
Top