Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!zaphod.mps.ohio-state.edu!sol.ctr.columbia.edu!emory!hubcap!ncrcae!sauron!nncrcae!wescott
From: wescott@Columbia.NCR.COM (Mike Wescott)
Newsgroups: comp.sys.ncr
Subject: Re: 32-600 HPSIO HELP?!?!?!: what is "threshold on overrun tally error"
Message-ID: <1990Oct12.184451.2985@nncrcae.Columbia.NCR.COM>
Date: 12 Oct 90 18:44:51 GMT
References: <1990Oct11.165115.4811@holos0.uucp>
Sender: usenet@nncrcae.Columbia.NCR.COM
Organization: E&M-Columbia, NCR Corp, W Columbia, SC
Lines: 21

In article <1990Oct11.165115.4811@holos0.uucp> wdh@holos0.uucp (Weaver Hickerson) writes:
> Does anybody know what "threshold on overrun tally error" means?

It means that some number (the threshold) of overrun events (hpsio
not getting characters out of uart before they're clobbered by more
characters arriving) have occurred.  It will happen more frequently
at higher baud rates.  It can be avoided if you can get H/W flow
control working.  If IRTS (see termio(7) or stty(1)) is set then
the uart will be programmed to automagically drop RTS when an overflow
condition is imminent.

> Could we have a defective HPSIO board here, bad port or something?

Possible, but this isn't evidence of that kind of problem.

> Is a block length of 1210 too large for these handy-dandy HPSIO's?

Nope.
--
	-Mike Wescott
	 mike.wescott@ncrcae.Columbia.NCR.COM