Wildguzzi.com
General Category => General Discussion => Topic started by: rodekyll on June 15, 2016, 01:10:05 PM
-
I'm trying to help get a member set up with a computer that will run the guzzidiag. My work method is to discover the requirements for the tool and then find the computer that runs it. So I need to know:
permittable opsys
port type
32/64-bit considerations?
min RAM
video requirements?
comm adapter chipset specs?
anything I might have not considered.
I know there's a topic dedicated to this, but a quick look says I can't sort through 20 pages of opinions to decode the actual basic requirements. So if someone could just spell it out . . .
thanks
-
Rodekyll:
As i understand guzzidiag it does not really install anything to your computer it is a free standing program.
I have it installed on an old off lease HP running Windows 7 that I bought from Tiger Direct for $199.00.
Bought the cables from Lonetec as recommended, downloaded the drivers as recommended & all installed & worked well.
It seems to me that GuzziDiag really does not need anything special, no hi power 'puter or great tech skill.
I would be willing to bet that any laptop running XP to Windows 10 will work fine with no mods needed.
I am no geek & only know computers as far as I need to know them to exist in todays world.
I don't have a smart phone, never used GPS & can just keep all the computers & printers in my business running by persistence.
-
I've been using the vdsts for my 15M and since it's working well, I haven't followed the guzzidiag topics. I'm therefore not familiar with the requirements. If a generic (Toshiba) tablet laptop (portege M750) running W7, minimal memory and USB ports will do it, then we have a winner.
-
I've been using the vdsts for my 15M and since it's working well, I haven't followed the guzzidiag topics. I'm therefore not familiar with the requirements. If a generic (Toshiba) tablet laptop (portege M750) running W7, minimal memory and USB ports will do it, then we have a winner.
You got it - I've run it on as little as a Win10 32-bit tablet (Atom processor) with 2GB RAM, 32 bit, but my preferred Guzzidiag device is a ThinkPad i5 laptop with 8 GB RAM, Win8.1 64-bit. The real trick is getting a cable set from a reputable source that doesn't use the cheap Chinese clones for the USB-serial-ODBII interface. The cables you have now likely will be just fine.
-
. The cables you have now likely will be just fine.
Cables from the vdst have been tried with no success from what I have read.
Beetle recommends the cables from Lonetec & downloading his drivers for the cables, there is a link in the thread for them. When I installed the cables I had to direct it to the drivers I downloaded about 3 times before it actually found them & installed them.
Only took a couple weeks to get the cables from London.
-
There was also a link for the cables on Amazon, not lonelec but they worked fine.
I'm using some brand of kindle sized tablet running Win 8.X. For GD it works fine, have not tried Tunerpro on it. When I do it will be on my desktop pc.
Tom
-
Well..as you can see, it doesn't take much. It's not installed. You can just put it on the desktop, drop the driver files in it, and you're done.
-
Here's a link to the FTDI chip based USB to OBD-II cable:
https://www.amazon.com/gp/product/B003ZKKMLE/ref=oh_aui_search_detailpage?ie=UTF8&psc=1
And here is the OBD-II to Fiat 3 pin cable:
https://www.amazon.com/Goliton®-OBD2-Connector-Diagnostic-Adapter/dp/B0053NRLHE/ref=pd_bxgy_263_2?ie=UTF8&psc=1&refRID=Y0QXMBZPW9KWYDVKS6SA
I have the above cables. Both have been used with GuzziDiag successfully.
NOTE: With the OBD-II to Fiat 3-pin, make sure to check if the positive alligator clip is indeed the positive cable. The reviews state that some of the cables came with the booties switched.
Oh and GuzziDiag will run on just about anything. I have run it on 7-year old hardware though Windows directly, via a LiveCD boot of Ubuntu off USB and from an Ubuntu virtual machine running on a Windows host. In all cases GuzziDiag worked without a hitch.
-
:thumb:
This is what we needed -- simple, direct information on what is working. Thanks, guys!