Re: Comport problem (reply to Mark and Nils)

From: E.G. (eg_at_nomail.dk)
Date: 01/17/04 

Date: Sat, 17 Jan 2004 10:23:39 +0100

Thank you for your replies.

"Mark G. Zeringue" <mark@zclient.com> wrote in message
news:40085090$1@newsgroups.borland.com...
> Stay with the latest AsyncPro version. I use this extensively and it
> works fine for me. I would first look at your code on how you are
> processing the received data.

I'm using TP vers. 4.06. (Is there a newer version?)
I've been using an infinite loop with CharReady and GetChar since I started
making comport apps. a couple of years ago with no problems. I stayed away
from the triggers 'cause I liked to control the flow myself and it really
hasn't been giving me any problems at all. Actually it's only my newest
installations (last 2-3 months) on new computers that have failed - and not
all of them.

"Nils Haeck" <n.haeckno@spamchello.nl> wrote in message
news:400862d5@newsgroups.borland.com...
> Could be a BAUD rate or cable problem.. Check the batteries / trigger
> crystal on the sending equipment. Check loopback pin connections, bridges
> in cables, and on serial boards (if applicable). Also make sure there's no
> grounding problem, or cheap faulty converter in the link, or switch to
> RS422 if cable length > 10 m.
>
> Also, changing handshake using stopbits and parity on both sides may solve
> this, or going to another baudrate at both sides.

But I've tried several TP versions and other components too. I still get
extra chars.
I've tried compiling in D5 and D6 and on different OSs (WinXP, Win2K Server,
Win2K Prof.). It used to work, so maybe my new computer / delphi version was
the problem.

I don't know what half of the component settings are for, so I tried them
all: different baud rates, data bit values, stop bit values, parities, buf
sizes, hw flow options, sw flow options, RS485 mode, Tapi mode, MSR shadow,
etc. etc.

Then I happened to get hold of a comport service I made about a year ago,
that has been running perfectly ever since I installed it, but when I try it
on one of these computers that gives me extra characters it fails too.
That has made me try changing cables (all 3m long) and trying other ports,
but I guess I knew that wasn't the problem, 'cause I don't get these extra
chars when I use the HyperTerminal app. on the same computer.

"Nils Haeck" <n.haeckno@spamchello.nl> wrote in message
news:400862d5@newsgroups.borland.com...
> Another thing to check is if you perhaps have a bug in your
> software considering clearing of buffers (and it accidentally
> reads out a value twice).

That was also a thought I had, but why would the same app work on one
computer and not on the other!

"Mark G. Zeringue" <mark@zclient.com> wrote in message
news:40085090$1@newsgroups.borland.com...
> Another possibility is to look at using the TapdDataPacket
> component. This hooks up to your comport and allows you to
> sepecify how to capture the received data. If say your incoming
> data uses a STX and an ETX, the DataPacket fires an event passing
> the complete received data set.

I've come to the conclusion that it must be a an OS/driver upgrade or maybe
the comport manufacturer has made some hardware changes and HyperTerm.
ignores these changes (or change them back automatically) which my app.
doesn't. So thank you, Mark, for the advice about the TapdDataPacket. I will
try that.

"Nils Haeck" <n.haeckno@spamchello.nl> wrote in message
news:400862d5@newsgroups.borland.com...
> Personally, I use TSerial5 from Rick Crowther, and I'm very happy with
> it.. Once things run, they keep running (and I know how important that is,
> working in automotive industry). However, it seems the support for it has
> stopped.

Thanx, I will try that too :o)

E.G.

Relevant Pages

  • Disabling debug info through serial port
    ... I want to stop WinCE from using the comport for debug info. ... (CE5.0 x86 standard PC) ... Do I need to re-install the SDK for my app to notice the change in debug.cpp? ...
    (microsoft.public.windowsce.platbuilder)
  • Re: Comport problem
    ... > I'm having problems with extra characters when my app reads data from a ... capture the received data. ... If say your incoming data uses a STX and an ETX, ...
    (borland.public.delphi.thirdpartytools.general)