🚀 go-pugleaf

There is another factor, which is quite significant, aside from the software
issues.

In a PC, the USB interface is a 'Host Controller'; the USB 1.x standard
prohibits
two Host Controllers on the same bus - which is what you are attempting.

There is a new provision in USB 2.0 for 'on-the-go' connections,
which is meant for PDA-PC connections.
In any case, whenever I've needed a computer-computer connection,
I've found that conventional mechanisms (TCP/IP, UDP or serial) are by far
the simplest to implement,
physically and programmatically.

Norm

"Graham Reeds" <grahamr@omnieng.co.uk> wrote in message
news:407e8f82@newsgroups.borland.com...
> > Hi, but can't i use the builder as it is to write a code that
> > for example send the character 0xA2 throught the USB? or can't
> > i write a code that read byte from the USB? must i use
> > additional components beside what i already have in the builder
> > right now?
>
> Not without a lot of programming, no.  I looked into USB and decided
against
> it.  You have to weigh the cost of the component versus the cost of your
> time writing/debugging and the time it holds the project up.
>
> > Also, what is the advantage in the speed when using USB and not
> > RS-232 communication? is there a big different between this two
> > types?
>
> Like I said, our app never required huge amounts of data, and we already
had
> written a fairly effective RS-232 component which I just tightened up a
> little (a 2 second timeout for realtime comms - no way!).
>
> G.
>
>