thad@cup.portal.com (Thad P Floryan) (04/14/90)
While slurping the latest uumap.tar.Z (UUCP maps) from UUNET.UU.NET, I
"found" the following in the "telebit-info" directory as UNIXPC.setup.Z
and, since it's from Telebit, felt this posting would be beneficial.
Thad Floryan [ thad@cup.portal.com (OR) ..!sun!portal!cup.portal.com!thad ]
========================================================================
Telebit Corporation Revision 1.02 01 APRIL 1990
========================================================================
SETUP INSTRUCTIONS FOR TELEBIT MODEMS AND THE ATT UNIX PC
The following examples should allow easy initialization of a TELEBIT
modem for use with UUCP on the UNIX PC and ATT 3b1 computers.
1. MODIFY /usr/lib/uucp/L-devices:
Add this entry to your L-devices file. Fill in the correct port #
DIR tty000 0 9600
2. CONFIGURE MODEM
In order to configure your TELEBIT modem correctly, it is best to start
by resetting the modem to factory settings. Please consult your TELEBIT
modem reference manual for the proper modem resetting procedure.
With the modem now reset, connect to the modem with the "cu" command below:
cu -s 9600 -l tty000
and configure the modem with the command string below:
AT &f S51=4 S52=2 S53=1 S54=1 S58=2 S66=1 S110=1 S111=30 S45=0 Q4 &W <CR>
This string (the spaces are optional, if you prefer to remove them) will:
- 1st (&F) recalls factory defaults (start with known configuration).
- 2nd (S51=4) sets up the serial port to 9600 baud.
(Set S51=5 and make appropriate L.sys, L-devices changes
to run at 19200 baud)
- 3rd (S52=2) says drop the connection when DTR is dropped to the mode
m
and reload the modem's stored EEPROM values (do a soft reset).
- 4th (S53=1) turns on DSR when the modem is ready to accept commands,
and turns on DCD when carrier is detected.
NOTE: S53 maps to registers S130 and S131 in Release B_5.00,
GA1.00, FA2.00, and above firmware. If S53 is not
present in your modem firmware, be assured that its
settings will map to the proper registers.
- 5th (S54=1) tells the modem to pass Breaks through to remote host.
- 6th (S58=2) tells the modem to use hardware (RTS/CTS) flow control.
- 7th (S66=1) locks the interface speed to whatever S51 is set to
(unless you want to modify gettydefs).
- 8th (S110=1) enables data compression between TELEBIT modems.
If desired, S110=0 will disable this feature.
- 9th (S111=30) enables UUCP "g" protocol support in the TELEBIT modem
.
- 10th (S45=0) disables remote access.
When the modem is reset, remote access is enabled to
allow easier customer support from TELEBIT. This is not the
case when the modem is originally shipped from the factory.
Remote access is not necessary for this application.
- 11th (Q4) enables partial quiet mode so getty won't see "CONNECT"
message but dialout is still verbose)
- 12th (&W) writes these new values into the current EEPROM bank (1/2)
.
This saves the new values as the modem's power on defaults, for
either bank A or B, until you change them again.
- 13th (<CR>) terminates the command to the modem.
After this, when you want to talk directly to the modem, use "cu"
to talk at 9600 bps. Remember to "disable tty000" before using "cu"
to prevent getty from confusing your responses with a login.
NOTES: (1) S58 sets the type of flow control to be used by the
modems serial I/O port. It is highly recommended that
RTS/CTS (hardware) flow control (S58=2) be used whenever
possible. Please consult your systems manuals for
instructions on proper software and hardware
configurations for RTS/CTS flow control. Some hardware
systems or operating systems may not be capable of this
function.
(2) S92 governs the sequence of modulation tones issued
upon auto answer. To reverse the answering sequence,
set S92=1, this will solve any "slow modem" connection
problems caused by the issuance of PEP tones. ALL
incoming PEP modems should have S50=255 set to connect
using PEP.
(3) If you would like to limit dialin/dialout connection
access to high-speed (PEP mode), add "S50=255" to the
above script to force the modem to use only the PEP mode.
To allow dial OUT to slower speed modems, modify the
L.sys script to:
hostname Any ACU 9600 ATE1S50=0DTNNNNNNN gin:--ogin: Uyoursysname ssword: XXX
XXXXX
3. Running at 19,200 bps:
Once you have UUCP working at 9600, you may want to run the
serial interface at 19200 bps. To do this, you should modify the
L-devices, L.sys, and /etc/inittab files accordingly, but you
won't be able to use "cu" or the terminal emulator because they
don't understand that speed. Also, you will have to modify the
file /etc/gettydefs. Just change the two occurrances of "B19200"
to "EXTA" to fool it into giving you the speed you want.
The use of a rotary or autobaud in getty is not recommended due to the
modems ability to lock interface speed (S66=1). The modem can then
arbitrate a slow modem connection to the hard-set interface speed without
the need for interface speed matching.
If a rotary/autobaud getty is used, don't forget to set your getty to
include 19200 in its cycle. You may have it trying 19200 first and moving
to 2400 on the 1st receipt of a break and to 1200 on the second receipt of
break. The order of the cycle is not important so long as the calling
system knows to send breaks until it sees the login sequence.
NOTE: It is highly recommended that TELEBIT modems be connected to the
serial I/O ports most closely attached to the cpu. Use of serial
I/O multiplexors may limit modem speed to 9600 bps or lower due to
flow control, cpu/bus interrupt, or memory buffer problems.
4. MODIFY /usr/lib/uucp/L.sys:
Modify L.sys file entry for a baud rate of 9600, since you have
locked the modem interface speed to 9600. Don't copy this literally.
Modify the info for your application. Also note that this is ONE line
of data, not two.
hostname Any ACU 9600 ATE1DTNNNNNNN gin:--ogin: Uyoursysname ssword: XXXXXXX
X
NOTES:
hostname = THEIR System name
NNNNNNNNNN = THEIR System phone number
Uyoursysname = Your UUCP account on THEIR machine
XXXXXXXX = Your UUCP passwd on THEIR machine
The "chat" script is the most common point of wasted connection time and
login failure. Be sure to test this entry rigorously to verify a successful
login in the fastest time possible.
5. TEST UUCP:
UUCP can now be tested by issuing the following command.
/usr/lib/uucp/uucico -r1 -x4 -shostname
Upon success or failure of the UUCP session, the status file must be
removed before another UUCP session can be started with the above command.
rm /usr/spool/uucp/STST.hostname
You should now be able to run UUCP between two machines attached to your
modems just as you always have with slower modems. Enjoy the new world of
high speed UUCP "g" via TELEBIT modems.
Michael Ballard/Cerafin E. Castillo
Telebit Corporation
1315 Chesapeake Terrace
Sunnyvale, CA 94089
1-800-TELEBIT
UUCP: {ames, uunet, sun, pyramid, decwrl}!telebit!modems
INTERNET: modems@telebit.com