Quote:
Originally Posted by jtgh
I noticed this same number is used in the OBD2 protocal too, (legacy equipment supports that , so they used it. even today on new cars)
notes, my special rs232 card allows the illegal baud rates as does realterm.
a perfect match.
the "comes-with", IBM clone style DELL UART can NOT generate this queer baud. the ubiquitous N16550a is useless at 15625. Com1 and Com2.
One nice thing ,the realterm proggy will tell you , if the baud is legal.
just plug in the card, and try it, it will say," illegal setting to com1." if true.
OBD1 , for Suzuki, coming soon and free of charge. (cept hardware)
cheers.
|
OBD2 is 10200 baud. The old MUT protocol was 15625.
I'm surprised that the Dell chip cannot generate odd baud rates, are you sure that that is not a problem with a windows driver. I have software that can drive the UART directly at any baud rate. I use standard Windows rates and ASCII serial transfer because it means that any software (is Hyperterminal) can be used as a back up. I will also be using my software for OBD2 and for reprogramming also so it is preferrable to have my own protocol to an active interface. I will publish details and if there is any demand then I will produce a batch of scanners. I figure that most people will want to buy rather than build so they may as well buy from the guy that did the groundwork.
I wrote datalogger software some time ago but two hard disc crashes in two weeks meant that I lost a fair bit of the code. The basic framework is still there and I started creating my own gauges too. If you like I will send you this, it is written in Borland Builder 6.
