Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Serial Comm. with BOSCH-Tester

0 views
Skip to first unread message

cRayFiSh

unread,
Dec 1, 1999, 3:00:00 AM12/1/99
to
hi,

i have massive problems to communicate to a car - smoke tester (BOSCH
ETT8.21).
it uses serial communication, but i'm not able to do it. maybe somehas
has experience
with the bosch serial protokoll.
the description of the protokoll says, that first byte has to be 82h
(header), the second
byte is the command to the tester. but i'm only able to write strings on
serial port, so
how to manage that?
if anyone can help reply here or write me so that we can discuss that
out.

thx 4 reading
cRayFiSh


Walter Petermann

unread,
Dec 1, 1999, 3:00:00 AM12/1/99
to dead...@gmx.de

Ray (?),

if you can write to the serial port, why can't
you write 82h then write the control code?

Also, with Labview you can read and write to the
serial port, although it might not be necessary for
your application.

Walter

Alan Brause

unread,
Dec 1, 1999, 3:00:00 AM12/1/99
to
Hello,

You will need to create an array of U8 (or what ever data structure your
protocol requires)
with the proper values in each element. (82h, first element, commmand value,
second element, etc)
After you assemble the array use Byte Array to String to convert it so you
can pass it to the serial
port write vi.
Use String to Byte Array to convert it back to an array after you get a
reply from serial port read vi.
The convert primitives are in the Functions palette=>Numeric=>Conversion.
I use this method to send modbus messages to a controller over the serial
port.

Regards,

Alan Brause


cRayFiSh <u12...@fh-harz.de> wrote in message
news:3844ED02...@fh-harz.de...

Wolf-Dieter Wall

unread,
Dec 3, 1999, 3:00:00 AM12/3/99
to

cRayFiSh wrote:

> hi,
> ...


> with the bosch serial protokoll.
> the description of the protokoll says, that first byte has to be 82h
> (header), the second
> byte is the command to the tester. but i'm only able to write strings on
> serial port, so

> how to manage that?...

I think you could build up a string that contains exactly the sequence of
commands you need.
no U8 or whatever. I'd use a string. Pop up on it with the right mouse
button and select "hex display"
then just type in whatever sequence of hex bytes you like. If you need some
ascii text inside of the command just select "\codes display" from the right
pop up menu. It will work just like a "C" string. You can think of it as of
a vector of int8 (or char)

--
Wolf-Dieter Wall <wdw...@masmec.com>

0 new messages