[comp.sys.hp] Trailblazers on HP9000/840 running HP-UX 2.1

jimmy@cogent.UUCP (Turnando Fuad) (04/28/89)

Request for help to anyone using HP9000/840 running HP-UX 2.1 with Trailblazers.

Our trailblazers slows down drastically (to less than 1200 baud) when 
transmitting at 19,200 baud.  The register settings on the Trailblazer is at 
its correct settings and all. I have talked to Telebit and they can't really 
figure it out, I have talked to HP support but they are a little reluctant to
pursue the matter because Trailblazers is not in their modems support list. The
problem started to occur after our update from HP-UX 1.2 to 2.1.  
All help will be greatly appreciated.

Turnando Fuad ( Jimmy )
Cogent Software Solutions                          
...pacbell!cogent!jimmy
...uunet!lll-winken!cogent!jimmy                    

-- 
Jimmy Fuad 					   
Cogent Software Solutions                          
...pacbell!cogent!jimmy
...uunet!lll-winken!cogent!jimmy                    

rjn@hpfcdc.HP.COM (Bob Niland) (04/29/89)

re: "...HP9000/840 running HP-UX 2.1 with Trailblazers."

> Our trailblazers slows down drastically (to less than 1200 baud) when 
> transmitting at 19,200 baud.

re: a working HDB UUCP / USR HST setup

This is on a Series 300 running HP-UX 6.5.  I routinely get ~10,000 bps
(1000 bytes/sec) UUCP throughput between my home and work systems (pseudo'd
as "hphome" and "hpmain" in the examples below).  Note that I am using UUCP
'f' protocol, which:
	* Enables Xon/Xoff pacing between modem and host
	* Increases send/ack packet size ratio, so the "fast end/slow end"
	  don't swap on each packet, which would clobber performance.
        * Converts some (perhaps all) binary data to encoded ASCII to
	  prevent false Xons and Xoffs.

File: /usr/lib/uucp/Devices
---------------------------
ACUHAYES culd0 cuad0 19200 hayes
ACUHAYES culd0 cuad0 9600 hayes
ACUHAYES culd0 cuad0 2400 hayes
ACUHAYES culd0 cuad0 1200 hayes
Direct ttyd0 0 19200 direct
Direct ttyd0 0 9600 direct
Direct ttyd0 0 2400 direct
Direct ttyd0 0 1200 direct

File: /usr/lib/uucp/Systems   {edited}
---------------------------
<sysname> <time>[;<retry>] <sysname> <speed> - <logininfo>
hpmain Any;5 ACUHAYES,f 19200 2263800- "" @@ gin:-BREAK-gin:-@-gin:-BREAK-gin:-@-gin:-BREAK-gin:-@-gin: hphome ssword: !passwd!
hpmain Any;5 ACUHAYES,f 19200 2263800- "" @@ gin:-BREAK-gin:-@-gin:-BREAK-gin:-@-gin:-BREAK-gin:-@-gin: hphome ssword: !passwd!
hpother Any;5 ACUHAYES,f 19200 2293600- "" @@ gin:-BREAK-gin:-@-gin:-BREAK-gin:-@-gin:-BREAK-gin:-@-gin: hphome ssword: !secret!

USR HST Switch Settings:
------------------------
  The physical switches of the HST mimic the USR2400, which, in turn,
  emulated the Hayes 'Smartmodem' 1200.  These should be old friends to you
  datacomm hackers out there.  "UP"=off=open "DOWN"=on=closed

  SW    HOST  TERM  Function and comments

  QUAD    UP    UP  Pins 2&3 not swapped.  This should not be necessary if
		    you are using a proper DTE cable.  In the case of 98642A
		    Port 0, any straight-thru male-to-male will do.  I am
		    using the 92219S supplied with the MUX.  If you have a
		    cable in which 2/3 are incorrect, you probably have
		    other equally serious pin-out problems.

  1       UP    UP  DTR normal.  All HP terminals and properly configured
		    host connections should assert Data Terminal Ready.  I
		    suspect that if you jam DTR high, the host computer
		    loses its expected method of telling the modem to hang
		    up in some circumstances.

  2       UP    UP  Verbal (rather than numeric) result codes sent.  'Dialers'
		    is expecting verbal codes.  Terminal users find them
		    easier to grasp than numbers.  Dialers will override this
		    to "verbal" ("V1") in any case.

  3     DOWN  DOWN  Send result codes.  'Dialers' expects them, and they make
		    terminal life easier, too.  Dialers overrides this to
		    "send" ("Q0").

  4       UP    UP  'AT' commands echoed in modem-local mode.  You need this
		    on a real terminal to see what you are typing.  'Dialers'
		    issues an E0 command to turn it off, and so doesn't care.

  5       UP  DOWN  Auto-answer enabled for host, disabled for terminal.
		    This is the only case where HOST and TERM differ (so
		    far).

  6       UP    UP  Carrier Detect controlled by modem.  This is what causes
		    'getty' to run at login time.  If you set it DOWN for
		    "always-on" you probably won't be able to dial-in.  A
		    real terminal, on the other hand, probably doesn't care.
		    'cu' does, however.  If you jam CD high, the modem may
		    be unable to tell the host computer that the session has
		    died (e.g. remote user disconnected without logging out).

  7       UP    UP  Single-line phone (RJ-11C).  Check your phone.

  8     DOWN  DOWN  'AT' commands recognized.  'Dialers' insists.  A case
		    where the terminal end might wish to disable AT is if
		    auto-dialers are illegal or inoperative on your phone
		    system.  Are you still using a crank telephone?

  9       UP    UP  <pause>+++<pause> puts modem in command mode AND drops
		    carrier.  DOWN does not drop carrier, and this can put a
		    'cu' connection into a weird state.  UP will let you
		    know right away that you goofed and blew the connection.

  10      UP    UP  Load configuration from NRAM at power-up (rather than
		    use factory defaults).  If you insist on using DOWN, you
		    might as well skip the next section :-)

USR HST Configuration Settings:
------------------------------
ATI0
964

OK
ATI1
059     56      9419

OK
ATI2
OK

OK
ATI3
00:22:04

OK
ATI4
USRobotics Courier 9600 HST Settings....

   C=1  E=1  F=1  M=1  Q=0  V=1  X=0  B=1
   BAUD=19200  PARITY=N  WORDLEN=8
   DIAL=TONE   ON HOOK    TIMER

   &A1  &B1  &G0  &H2  &I5  &K1
   &M4  &N0  &P0  &R1  &S1  &Y1

   S00=000  S01=000  S02=043  S03=013
   S04=010  S05=008  S06=002  S07=045
   S08=002  S09=006  S10=007  S11=070
   S12=050  S13=000  S14=000  S15=000
   S16=000  S17=000  S18=000  S19=000
   S20=003  S21=010  S22=017  S23=019

OK
ATI5
USRobotics Courier 9600 HST NRAM Settings....

   DIAL=TONE   M=1  X=0  F=1  B=1
   BAUD=19200  PARITY=N  WORDLEN=8

   &A1  &B1  &G0  &H2  &I5  &K1
   &M4  &N0  &P0  &R1  &S0  &Y1

   S02=043  S03=013  S04=010  S05=008
   S06=002  S07=045  S08=002  S09=006
   S10=007  S11=070  S12=050  S13=000
   S15=000  S19=000  S21=010  S22=017
   S23=019

   STORED PHONE #0: 
                #1: 
                #2: 
                #3: 

OK
ATI6
Chars sent                   392        Chars received            148041
Chars lost                     0
Octets sent                  392        Octets received           103001
Blocks sent                  371        Blocks received             2343
Blocks resent                 11

Retrains Requested             0        Retrains Granted               0
Line Reversals                 0        Blers                          0
Link Timeouts                  0        Link Naks                      0

Data Compression        On
Equalization            Long
Fallback                Enabled
Speed                   9600/300

Disconnect Reason is Loss of Carrier

OK
ATI7
USRobotics Courier 9600 HST Configuration Profile:

Product type            External
Custom chip             U100
Clock freq              14.976
Options                 Standard

Supervisor date         03/07/88
Supervisor rev          4
Transmitter rev         2
Receiver rev            2

I have a register-by-register narrative for the HST, but thought it a bit
long to post.

Regards,                                              Hewlett-Packard
Bob Niland                                            3404 East Harmony Road
ARPA: rjn%hpfcrjn@hplabs.HP.COM                       Fort Collins
UUCP: [hplabs|hpu*!hpfcse]!hpfcla!rjn                 CO          80525-9599