Hello:
Finally, I was able to run Rhinoview on Windows 10. I believe the issue was using the wrong baud rate (I think). After I installed D2XX driver and set the baud rate at 15625, it worked. I honestly believe it would have run had I used 15625 baud rate as opposed to what had been suggested in the installation right up of 7812, in the first place. However, I did not want to uninstall D2XX driver and try it to see if my claim is actually right!
In any case, I thank you very much for your support. I, however, urge you to spend a few minutes to draft a short document stating these little details (i.e., different baud rates for 8 valve and 16 valve, etc.) so that your customer would not have to spend so much time to get the software running.
Thanks again!
Zack.
__________________
91 Sidekick JX, 8V, S. Carolina Car, 2 dr, 3 speed Auto Trani, Halifax, NS, Canada
The bad data rate simply logs each time there is no valid response from the ECU.
The baud rate is 15625 for an 8V Track/kick and 7812 for a 16V, there may have been a misunderstanding or have you changed vehicle?
On the Windows 10 laptop you will find that the FTDI driver package actually contains two different drivers, the virtual comport driver and the direct driver, both of those drivers are initialised when you plug in the device. The driver that is used by RhinoView appears under 'Universal Serial Bus Controller' as a 'USB Serial Converter'
__________________
1984 Suzuki SJ413K pick up, 1.6 16V Baleno engine 2000 Suzuki Vitara 1.6 8V, many mods 2004 Suzuki Ignis 1.5VVT 4Grip 2006 Suzuki Jimny 1.3VVT JLX+ and many more.
I got it working on Win 7! The only thing I did was turning the car on! I thought the "bad data rate" was an issue with the connection (yes, at that stage I had the ignition on, but the engine was not running).
Now I will work on Win 10 laptop and will let you know whether I could connect once I install the FTDI driver.
Cheers,
Zack
__________________
91 Sidekick JX, 8V, S. Carolina Car, 2 dr, 3 speed Auto Trani, Halifax, NS, Canada
For your information, This is what my Surface 3 (Win 10) shows. At this stage, I had not installed the FTDI driver.
As for the baud rate of 15625 I am surprised! I have tried every possible baud rate to get it working. I went through my notes from 7 years ago and found the following recommendation. I am not sure whether it was from you or so meone else (it was from a person named: James Holland). That had worked for me then and the last time I used Rhinoviw of my Win 7 laptop. It was suggested:
"Under 'Comms' you should select 'baud rate' and set that to 7812. If you still can't connect then you should check the voltages on the diagnostic connector using a voltmeter, you should have 12V between pin 16 and 4 or 5 and 5V between pins 9 and 4 or 5."
The DLL is not a driver, its a piece of software that provides a standardised interface to the driver. You mentioned the D2XX driver and the D2XX direct driver, they are using two different names for the same driver, you will need the Windows driver that you have circled
The FTDI driver is usually included with Windows these days so no installation is normally required, it should be just plug and play. You may have another issue but you need to ensure that you have the drivers installed.
A video is a good idea, I will give that a try, I haven't sold any interfaces for a couple of years because I have been working away from home but I do have some more coming now.
On your windows 7 laptop you will need to select the Com Port and set the baud rate to 15625 if its an 8V Sidekick.
__________________
1984 Suzuki SJ413K pick up, 1.6 16V Baleno engine 2000 Suzuki Vitara 1.6 8V, many mods 2004 Suzuki Ignis 1.5VVT 4Grip 2006 Suzuki Jimny 1.3VVT JLX+ and many more.
Thank you very much for the quick response. However, I think I did not explain my situation properly. I am going to try it again.
CASE 1
=====
The 7-8-year-old version resides on my Windows 7 laptop. This is what I had used 4 years ago when I had to use the software. It worked then. My question is that, looking at the picture I enclosed in my previous thread, where it shows apparently the cable is connected to the car and software sees it, why does it not work?
______
I went to my old laptop because I spent over an hour to get your V1.2, which comes with its own driver, working on my Surface 3-pro (Win 10). Apparently now I have to install another driver, instead of the one that was included in v1.2 zip file.
My question is that why do I have to download the driver from https://www.ftdichip.com/Drivers/D2XX.htm when you have already enclosed a driver in the V1.2 zip file?
You mentioned the drivers on that website are the same?! I cannot understand it - why would then they have all the ones showed in the picture attached here?
I have downloaded the one that I have circled in red in the picture because my Surface is 64 bit - is that OK?
And yes, I downloaded the instruction - it is ONLY 38 pages long! I was hoping NOT to spend my time to read 38 pages in order to install a driver - I hope you would appreciate it!
To be honest, I could install the Mercedes Star diagnostic software (Chinese version), which is supposedly a very sophisticated and complicated software to install. I could install it in 1/10 of the time I have had to spend getting Rhinoview working. How I could do it? No, I am not that smart, but the vendor made a nice 2 minute 53 sec. tutorial video available to me.
But which one would I download for 91 Zuke, the D2XX or D2XX Direct
It seems one needs a computer science degree to use this software. It would have been very nice if you could prepare an installation tutorial for use of the software/cable. God knows that I have expended over four frustrating hours to get this Cable connected in a total of three times I have had to use the cable.
With respect!
Zack
Zack D2XX DriversD2XX Drivers
Its the same driver, its just the way they have headed the sections that is confusing. Have you read the help file that is included in the download?
__________________
1984 Suzuki SJ413K pick up, 1.6 16V Baleno engine 2000 Suzuki Vitara 1.6 8V, many mods 2004 Suzuki Ignis 1.5VVT 4Grip 2006 Suzuki Jimny 1.3VVT JLX+ and many more.
Newer versions of RhinoView don't use the virtual comport so the SDL interface is plug and play. I haven't tested the old software on Windows 10, that version you have there must be seven or eight years old at least . You need the ft2xx dll and the ftdi driver which can be downloaded here: https://www.ftdichip.com/FTDrivers.htm
__________________
1984 Suzuki SJ413K pick up, 1.6 16V Baleno engine 2000 Suzuki Vitara 1.6 8V, many mods 2004 Suzuki Ignis 1.5VVT 4Grip 2006 Suzuki Jimny 1.3VVT JLX+ and many more.
But which one would I download for 91 Zuke, the D2XX or D2XX Direct
It seems one needs a computer science degree to use this software. It would have been very nice if you could prepare an installation tutorial for use of the software/cable. God knows that I have expended over four frustrating hours to get this Cable connected in a total of three times I have had to use the cable.
With respect!
Zack
Zack D2XX DriversD2XX Drivers
__________________
91 Sidekick JX, 8V, S. Carolina Car, 2 dr, 3 speed Auto Trani, Halifax, NS, Canada
Thank you for the response. 1. Where would I get the FTDI driver, because the FTD2XX.dll included in Ver 1.2 zip file did not work!
2. The version I had working on my Windows 7 tablet stopped working as well (I believe it was Ver 1) As you can see, the software is seemingly connected to the car (the car was on at that stage). When I press the "conn" again, I get the message "Port is already open". What is going on? This was working the last time I used it!
There is no installation, you just need to copy the files to your computer. For a 91 Sidekick you need to select 7812 baud, you need to have the FTDI driver installed.
__________________
1984 Suzuki SJ413K pick up, 1.6 16V Baleno engine 2000 Suzuki Vitara 1.6 8V, many mods 2004 Suzuki Ignis 1.5VVT 4Grip 2006 Suzuki Jimny 1.3VVT JLX+ and many more.
Could you please tell us how to install v. 1.2 (I know how to install it, but do I need to do anything extra to get the software communicating with my 91 Zuke?)
I find this forum very frustrating as most of the questions I have asked have NOT been answered!
Thank you, Zack
-- Edited by Zackman on Tuesday 23rd of June 2020 06:18:35 PM
__________________
91 Sidekick JX, 8V, S. Carolina Car, 2 dr, 3 speed Auto Trani, Halifax, NS, Canada
I have tested RhinoView v1.2 on a Windows 10 tablet. It appears to work OK if run as an administrator, to do this right click (or long press) on the RV icon and select 'Run as administrator'.
__________________
1984 Suzuki SJ413K pick up, 1.6 16V Baleno engine 2000 Suzuki Vitara 1.6 8V, many mods 2004 Suzuki Ignis 1.5VVT 4Grip 2006 Suzuki Jimny 1.3VVT JLX+ and many more.