public inbox for linux-serial@vger.kernel.org
 help / color / mirror / Atom feed
From: "Neil Everton" <neil@gemini-it.com>
To: "Linux-Serial@Vger. Kernel. Org" <linux-serial@vger.kernel.org>
Subject: [OT(ish] Duplicate Character between modems
Date: Fri, 2 Aug 2002 21:41:09 +0100	[thread overview]
Message-ID: <HMEGLNIPFGJPACKIEKLFGEJJEPAA.neil@gemini-it.com> (raw)

Hi,
	My apologies for sending this here, but I reckon you guys are probably the
best bet I have of finding a solution to my problem (esp. as it indirectly
relates to serial programming)

	I'm currently porting an application from DOS to Linux (RH7.2 with Cyclades
Cyclom-Y (hi henrique!!)).

	My issue is this, if I send down the modem ;
"ABCDEFGHI"
	the receiving end (very infrequently) receives
"AABCDEFGHI"
	This is caught by the check digit routine and the line is NAK'd ready for a
re-transmit. It will usually work the second or third time. This has found a
bug in the 3rd party transmitting software, but they're taking the attitude
of the existing system works, so you fix your end !!! (the bug if your
interested is after sending a NAK they drop the connection, instead of
waiting for 5 retries)

	The existing DOS system uses old modems such as Pace Linnet (1200 baud) and
an even older modem called a Compact which you cannot do anything with, no
init string, no RING or CONNECT message, just straight into getting the
data.

	The new system is using 3Com Courier V.everything modems. I can replicate
the problem on other modems as well, so it's not a courier issue. We have to
disable any error correction, compression (except MNP), and set the flow
control to hardware. As far as I can see I've disable pretty much
everything, but I still occasionally get these duplicated characters. It
used to be quite bad and then I realised that the Courier set the flow
control on both the transmit and receive stacks seperately. Once I'd set the
flow control to hardware for both stacks it made the issue a lot better, but
I still get it.

	I can normally get this issue (at home) at least every 3rd order, luckily
it's not so bad at the clients end. My home setup incidentally doesn't have
a cyclades card, but I've sniffed at the modem connection and I definatly
don't send the duplicate characters to the modem, they're adding in between
the modems.

	The modem I'm sending on is a generic 56k modem, but we're getting the
issue on 300 baud modems, with the Courier set to only connect at 300. The
connect message is simply 'CONNECT' so should be giving no error correction,
compression, etc. it should be a standard V21 connection. There might be an
issue with fast modems connecting at V21 I'm not aware of, but I'm at a
loss. My client is also concerned with the issue (understandably) and are
also in the 'it works on the existing system' mentality.

Any help/pointers/advice gratefully received
Regards
Neil Everton


             reply	other threads:[~2002-08-02 20:40 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-02 20:41 Neil Everton [this message]
2002-08-03 21:31 ` [OT(ish] Duplicate Character between modems rich+ml
2002-08-05  9:05   ` Neil Everton
2002-08-05 18:26     ` rich+ml
  -- strict thread matches above, loose matches on Subject: below --
2002-08-02 22:54 Ed Vance
2002-08-05 16:06 Ed Vance

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=HMEGLNIPFGJPACKIEKLFGEJJEPAA.neil@gemini-it.com \
    --to=neil@gemini-it.com \
    --cc=linux-serial@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox