Login Register

Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Rhino software and ALDL Cable...WIN!
#24
My guess what he is saying is :
1: you need to buy my full kit, no mix and match now, and is wise.
2: Ok now we know he still sells a kit, but you need to get on the list, it built to order, like I said there are no over the counter tools for this car sold
before USA OBD2, 1996 or in canada 1998. zero. tools sold in any auto store nor from the top commercial maker SNAPON. even at $10,000 bucks, nada.


no need, to do that, there are vast ways to do all this given PC's or better laptops from 1984 to today, and are totally radially different now.
OBD1 is a deep and complex topic, truly endless (not only the PC limits but not all Suzuki use the same sensors, oops)

that is why here in the USA we ended that old junk in 1996, with OBD2, we invented it here. and is copied now world wide,under other names.
a standard tool that fits call cars.
then consider THIS obd1 , it only works on this suzuki but not all OBD1 suzuki;s and for sure the first one. (no SDL port)
this topic is not simple at all. but do ask, have lots of examples.
I should make a OBD1 faq page, (trouble is it be near endless, it is in my head but,,,,im old almost 70 now)
why not just pay him what he wants. that is what id do... get a working package in a box.
but most don't they see $10 OBD2 on fleabay and go why pay $50 for a OBD1. answer, is , "this is all there is now"!
Suzuki owners are skin flints, (love yah) but is a fact, nobodies going to get rich selling oBD1 that fits JUST one car, and not all in class (G16). its not going to happen.


(04-29-2017, 02:43 AM)DETN8R Wrote: Thanks Fix Kick! I don't have time to digest everything you said and I'm certainly willing to try to make the cable work but here is the response I got from James at Rhinoview

"My interfaces use a direct USB connection, other manufacturers interfaces will not be recognized by the software because they are only designed to use the virtual com port. Many years ago I did have some software that used the VCP but I moved away from that, because it was too slow and unreliable, that software is no longer supported. I cannot provide support for other manufacturers interfaces.

...
(comments by me, this so true,, there is not just one VCP maker, now or do they work the same way or use the same drivers)
He is saying that he did it the correct way, IMO ,HE DID!

There are several different USB protocols. The FTDI chip can communicate with a PC as either a Virtual Com Port device or as a Bulk Transfer Device. The VCP protocol relies on an FTDI driver communicating through the Windows Serial API which hasn't been properly supported since Windows 98, it requires manual configuration, is slow and is prone to 'hanging' if the cable is momentarily unplugged. The Bulk Transfer protocol is a 'proper' USB protocol and supports automatic detection and re-connection, in addition I get three times the data transfer rate which gives a much better resolution when datalogging. You need the D2XX driver from FTDI, it used to be supplied separately to the VCP driver but these days there is only one download that installs both drivers.
I have been working away for six months but I will be building another batch of interfaces next week, the interface will work with your 95

regards
James"
http://www.fixkick.com
Reply


Messages In This Thread
RE: Rhino software and ALDL Cable - by fixkick - 09-09-2014, 06:15 PM
RE: Rhino software and ALDL Cable...WIN! - by mpo - 10-09-2014, 12:39 AM
RE: Rhino software and ALDL Cable...WIN! - by mpo - 10-09-2014, 08:08 PM
RE: Rhino software and ALDL Cable...WIN! - by mpo - 10-10-2014, 06:53 PM
RE: Rhino software and ALDL Cable...WIN! - by mpo - 10-11-2014, 07:52 AM
RE: Rhino software and ALDL Cable...WIN! - by fixkick - 04-29-2017, 03:02 AM
RE: Rhino software and ALDL Cable...WIN! - by mpo - 05-04-2017, 12:23 AM
RE: Rhino software and ALDL Cable...WIN! - by mpo - 05-04-2017, 07:24 AM

Forum Jump:


Users browsing this thread: 1 Guest(s)