Thank you guys for all that detailed hints and glues !
I turned out that this was cable problem :-/
After changing the cable everything went well !
Thanks !
Harald
Jim Wagner wrote:
Harald -
One other clue you can use is to change the display font of the edit
field. If the returned
data has the high bit set, then, often, what is displayed will change
with the font because
different fonts make different assumptions about those high 128 "ASCII"
characters.
Yea, i know that they are not truly ACII because ASCII is not defined
above decimal
value 127, but we know what this means, right?
My experience in this area has generally been that this sort of problem is
caused by one of several things (most of which have been previously
described):
1. incorrect baud rate
2. incorrect number of data bits
3. incorrect number of stop bits (esp if you choose 2 and incoming
has 1)
4. wrong parity (esp choosing any kind of parity when incoming has
none; this
will cause characters to be missed).
Much (very much) more rare causes include:
1. poor/missing ground connection in serial cable
2. high noise level (not likely if good copy on "terminal")
3. incorrect hand-shake
Similar to Tom's suggestion, for diagnostic purposes, I tend to print
the decimal values of
the characters, comma delimited, Hex or binary work, also. If you can
get a predictable
message from the remote device (such as when it is reset or first turns
on), this also helps
to figure things out in combination with a numeric value display.
When you say that it is readable on a terminal, is this on the SAME
machine that your RB
app is running? If not, try to set up a terminal program on the SAME
machine to check that
the connections on that machine are all OK.
One possibility is that you are NOT setting the serial port parameters
correctly. You might think,
for example, that you have the correct baud rate when you don't. Are you
explicitly setting all of
the parameters for that port?
Jim
On Jun 26, 2006, at 12:29 PM, Tom Keene wrote:
Convert the incoming data to hexadecimal or binary and
compare that with a chart of ASCII codes. Then you know
what the data is that you are receiving.
On Jun 26, 2006, at 12:00 PM,
[EMAIL PROTECTED] wrote:
Subject: Serial Communications - Encoding ?
From: Harald Schneider <[EMAIL PROTECTED]>
Date: Mon, 26 Jun 2006 16:25:36 +0200
Hi,
I use a Serial control, which collects incoming data via its
DataAvailable() event. The result of .ReadAll() is appended to a
Editbox. The problem: Instead of ASCII Text, I see only squares and
other trash ...
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives of this list here:
<http://support.realsoftware.com/listarchives/lists.html>
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives of this list here:
<http://support.realsoftware.com/listarchives/lists.html>
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives of this list here:
<http://support.realsoftware.com/listarchives/lists.html>
