[iyonix-support] Re: USB to serial converter driver available?

In message <Marcel-1.53-1126103845-d07pErr@xxxxxxxxxxxxxxxxxxxxxx>
          Chris Evans <chris@xxxxxxxxxxxxxxx> wrote:

> On Sun 25 Nov, Thomas Milius wrote:
> > 
> ...
> > 
> > Regarding all aspects I came to the conclusion that it would make sense
> > to buy me an OBD2-Interface and use it from my Iyonix. I am thinking of
> > buying an OBD-DIAG 4000 adapter, which provides OBD access even for new
> > cars on one side and an USB connection on the other side. USB connection
> > is provided by fitting an USB to serial convert chip within the interface
> > because the OBD chip uses a serial interface.
> 
> Is there no way to connect directly to the serial interface?
> 

May be. But it must be sold at Germany at a place where I can buy it.

It seems that all newer OBD interfaces are not simply electronic converters
but provide a certain "intelligence". They must be therefore documented and
this is not always the case. For the ODB-Diag 4000 a wiring diagram is
avaible and the chips seems to be documented very well even the USB to serial
converter seems to be freely programmable and may be therefore contain some
unwanted surprises.

And at last there seems to be a trend at newer interfaces that they are sold
with USB for it seems that laptops are no longer providing an serial
interface. OBD-Interfaces are typically used in conjunction with laptops at
garages. Might be that simple USB to serial converters may cause trouble.
Some OBD modes are starting with 5 Baud and then are switching to 10400 Baud.
Ok the OBD chip might hide this problems by an internal buffer but I am not
sure for I have no expierence with this technology. So I thought that if I am
buying such an interface and try to make it working then it should be an
uptodate device. The OBD-Diag 4000 seems to be on state of the art and there
is a couple of similar devices like the OBD-Diag 3000 for older cars (which
would be enough for my ten years old car but I think I should also look at
the present car technology) and the OBD-Diag 4000X for persons which are
liking to tune/destroy their car by a mouse click (as I read: "this interface
is only for experienced people which are knowing what they are doing ...").

If I could manage it to adapt the ODB-Diag 4000 for RISC OS then there are a
couple of open source OBD-programs available which could be ported easily and
will support this interface even this programs might be realtively poor. On
the other side these programs might give programming hints.

I personally must say that I am the opinion that in this case a big
impressive coloured GUI is not so important as the knowledge of the
protocols.

For myself I must also buy an interface which I could easily use at a PC
(which I would have to borrow from a friend/neighbour) to get the new engine
control unit working during the next weeks. However such an interface is not
for a single action. Unfortunately it seems that cars are getting more and
more complex and garages are seeming to have also some trouble with this. So
it might be useful to make usage of such a tool at home for an first
overview.

> IIRC USB drivers that require data in non full data block sizes is a big
> problem!
>  

Many thanks for the hint. I shall keep an eye on this.

> ...
> > 
> > Is there a driver for the Castle USB stack for USB to serial interfaces?
> > 
> > Did anyone got an USB-Modem working on the Iyonix?
> 
> I've not heard of either of the above:-(
> 

:-(. Ok looks like a long way to go but perhaps it will be succesfull and a
couple of useable side effects will come out.

I shall give it a try and buy an ODB-Diag 4000. Lets see what will come out.

Best Regards

Thomas Milius
---
To alter your preferences or leave the group, 
visit http://www.freelists.org/list/iyonix-support
Other info via http://www.freelists.org/webpage/iyonix-support

Other related posts: