kmcvay@icgnu.UUCP (Ken McVay [1B Systems Management]) (08/14/90)
I am having a problem getting a T1000 Telebit to connect properly with a
Trailblazer Plus over standard telephone lines.
The T1000 is running on tty1A, on a 386 clone running SCO XENIX 2.3.2. The
Devices file shows:
ACU tty1A - 9600 T1000
and the corresponding Dialers entry is:
# Telebit T1000 Modem
#
T1000 W-P "" ATS0=0Q0\r\c OK\r ATDT\T\r\c FAST
&T1000 W-P "" +++\dAT&E1\r\c OK\r ATQ1\r\c
The modem registers look like this:
E1 F1 M0 Q4 T V1 W0 X1 Y0 &P0 &T4 Version FA1.00
S00=001 S01=000 S02:128 S03=013 S04=010 S05=008 S06=002 S07=040 S08=002 S09=006
S10=007 S11=070 S12=050 S18=000 S25=005 S38=020
S45=000 S47=004 S48=000 S49=000
S50=000 S51:255 S52:001 S53=000 S54=000 S55=000 S56=017 S57=019 S58=003 S59=000
S60=000 S61=150 S62=003 S63=001 S64:001 S65=000 S66=000 S67=000 S68=255
S90=000 S91=000 S92=000 S94=001 S95=000
S100=000 S101=000 S104=000
S111:030 S112=001
S121=000 S255=001
The system being called works with everything else it talks to, but there are
no other TB's calling _in_ for comparison, so there could be a problem there
as well. dialTBIT has never worked, and the TB+ is run from Dialers and
nvram:
#
E1 F1 M0 Q0 T V1 W0 X3 Y0 &P0 &T4 Version BA5.01
S00=001 S01=000 S02=043 S03=013 S04=010 S05=008 S06=002 S07=040 S08=002 S09=006
S10=007 S11=070 S12=050 S18=000 S25=005 S38=000
S41:001 S45=000 S47=004 S48=000 S49=000
S50=000 S51:254 S52:002 S54:003 S55=000 S56=017 S57=019 S58:002 S59=000
S60=000 S61:100 S62=003 S63=001 S64=000 S65=000 S66=000 S67=000 S68=255 S69=000
S90=000 S91=000 S92=000 S94=001 S95:002 S96:000
S100=000 S101=000 S102=000 S104=000 S105:000
S110:000 S111:030 S112=001
S121=000 S130=002 S131:001 S255:001
The TB+ is set up to answer the line at 2400 baud, then bump up to 9600. When
the T1000 connects, CONNECT FAST is received, and a break is sent to bump thje
TB+ to 9500. The result is streaming garbage ("^@^@^@^@^@" etc) and a failed
connect.
By creating a 2400-baud Device and Dialers entry for the T1000, and calling
a 2400-baud modem on the other system (instead of the TB+) I can connect
successfully and move the mail et al, but I can't seem to get the two
'Blazers to talk to each other correctly. Both modems are running via standard
(dumb) serial ports.
I don't have a manual for the T1000, and am unfamiliar with it. Are the
register settings available the same ones used in the TB+ and T2500?
Any and all suggestions appreciated :-)neal@mnopltd.UUCP (08/15/90)
->
->I am having a problem getting a T1000 Telebit to connect properly with a
->Trailblazer Plus over standard telephone lines.
->
->The T1000 is running on tty1A, on a 386 clone running SCO XENIX 2.3.2. The
->Devices file shows:
->
->ACU tty1A - 9600 T1000
->
->The system being called works with everything else it talks to, but there are
->no other TB's calling _in_ for comparison, so there could be a problem there
->as well. dialTBIT has never worked, and the TB+ is run from Dialers and
->nvram:
I just know I going to get stomped on for this but, why haven't you used the
dialTBIT? Did it need to get compiled?
I just plugged in
ACU tty2a - 19200 dialTBIT
and it ran like koolaid downhill. There are some special things you can
do with yer phone numbers like a "P" on the end forces PEP, etc; you gotta
scan the source for the details. The neat thing about dialTBIT versus the
Dialers stuff is you can customize the parameters for each site you dial.
Also it will initialize the modem via
dialTBIT -z /dev/tty2a 19200
and you can see what is going on via the -x9 argument.
AND OF COURSE IT ISN'T STANDARD SYS V SO IT DRIVES EVERYONE ELSE CRAZY !!!
(the one decent thing they left in sco unix........)
------------------------------------------------------------------------------
Neal Rhodes MNOP Ltd (404)- 972-5430
President Lilburn (atlanta) GA 30247 Fax: 978-4741
emory!mnopltd!neal
------------------------------------------------------------------------------steve@nshore.uucp (Stephen Walick) (08/16/90)
As quoted from <102@mnopltd.UUCP> by neal@mnopltd.UUCP: +--------------- | ->I am having a problem getting a T1000 Telebit to connect properly with | ->a Trailblazer Plus over standard telephone lines. | -> | -> ....dialTBIT has never worked, and the TB+ is | ->run from Dialers and nvram: | | I just know I going to get stomped on for this but, why haven't you used the | dialTBIT? Did it need to get compiled? +--------------- Not from me, another T1000 Telebit user. I've already "email"ed a reply, very similiar to yours, but did note one thing that I found *very* impor- tant.... SCO's dialTBIT script is for the "Trailblazer" and uses S registers that are not known to the T1000, viz., the "S111= " register (about file com- pression) does not appear on the T1000. I had to comment those references in the setup and in the script itself or I would run into "mucho" problems. -- Stephen J. Walick, Asst Sysop of the < XBBS > program at NCoast.ORG uunet!ncoast!nshore!steve nshore!steve@ncoast.org
barton@holston.UUCP (Barton A. Fisk) (08/17/90)
In article <1990Aug16.010504.10895@nshore.uucp>, steve@nshore.uucp (Stephen Walick) writes: > As quoted from <102@mnopltd.UUCP> by neal@mnopltd.UUCP: > +--------------- > | ->I am having a problem getting a T1000 Telebit to connect properly with > > > SCO's dialTBIT script is for the "Trailblazer" and uses S registers that > are not known to the T1000, viz., the "S111= " register (about file com- > pression) does not appear on the T1000. I had to comment those references > in the setup and in the script itself or I would run into "mucho" problems. All I had to do was make a copy of the dialHA24 source (call it dialT1000) and make a very few modifications: 1. Modify the setup string to whatever your needs are. Note that you can run in coventional (Hayes AT command) mode and still issue enhanced commands via the ~ construct in your setup string. 2. Anywhere you see the reference to B2400, add a line similar to that using the same syntax except make it B9600. 3. Add a line or two to the sources that will recognize the result string that the TB+ or whatever modem sends back and associate that with the B9600 string. The sources are pretty plain about that. 3. Edit the supplied makefile if you like to output the desired filename and such. I am sure there are better, more eligant ways of doing this, but "it works for me", and has for several months. Hope this helps. Bart -- uucp: holston!barton
neal@mnopltd.UUCP (08/17/90)
->
->As quoted from <102@mnopltd.UUCP> by neal@mnopltd.UUCP:
->
->+---------------
->| ->I am having a problem getting a T1000 Telebit to connect properly with
->| ->a Trailblazer Plus over standard telephone lines.
->| -> ....dialTBIT has never worked, and the TB+ is
->| ->run from Dialers and nvram:
->| I just know I going to get stomped on for this but, why haven't you used the
->| dialTBIT? Did it need to get compiled?
->+---------------
->
->Not from me, another T1000 Telebit user. I've already "email"ed a reply,
->very similiar to yours, but did note one thing that I found *very* impor-
->tant....
->
->SCO's dialTBIT script is for the "Trailblazer" and uses S registers that
->are not known to the T1000, viz., the "S111= " register (about file com-
->pression) does not appear on the T1000. I had to comment those references
->in the setup and in the script itself or I would run into "mucho" problems.
Thanks for the warning, but I just looked at the manual for the T1000 and it
does show S111... perhaps you mean s110? I do notice that it is not in the
manual although the rev 1.3 dialTBIT.c does try to set it. I also notice
that it appears to be unsettable in the T1000, eg:
ats110=4
OK
ats110?
000
------------------------------------------------------------------------------
Neal Rhodes MNOP Ltd (404)- 972-5430
President Lilburn (atlanta) GA 30247 Fax: 978-4741
emory!mnopltd!neal
------------------------------------------------------------------------------steve@nshore.uucp (Stephen Walick) (08/22/90)
As quoted from <105@mnopltd.UUCP> by neal@mnopltd.UUCP: +--------------- | ->As quoted from <102@mnopltd.UUCP> by neal@mnopltd.UUCP: | -> | ->+--------------- | ->| ->I am having a problem getting a T1000 Telebit to connect properly with | ->| ->a Trailblazer Plus over standard telephone lines. | ->| -> ....dialTBIT has never worked, and the TB+ is | ->| ->run from Dialers and nvram: | ->| | ->| I just know I going to get stomped on for this but, why haven't you used | ->| the dialTBIT? Did it need to get compiled? | ->+--------------- | -> | ->SCO's dialTBIT script is for the "Trailblazer" and uses S registers that | ->are not known to the T1000, viz., the "S111= " register (about file com- | ->pression) does not appear on the T1000. I had to comment those references | ->in the setup and in the script itself or I would run into "mucho" problems. | | Thanks for the warning, but I just looked at the manual for the T1000 and it | does show S111... perhaps you mean s110? I do notice that it is not in the | manual although the rev 1.3 dialTBIT.c does try to set it. I also notice | that it appears to be unsettable in the T1000, eg: | ats110=4 | OK | ats110? | 000 +--------------- Whoops -- you're very correct. Sorry for the mis-information to any and all readers of these news groups who may have been misled. Indeed, the "S111" register is "File Tranfer Protocol Support" and I had intended to refer to the "S110" register. However, since my last follow-up, I have had personal contact with other T1000 users who happen to have an "older" model whose S-registers were *NOT* the same as my own, and that fact demonstrated by both the Model number on the label and the corresponding manual. Hence, *CAUTION* should be taken, even when speaking about T1000 TBIT modems. The same T1000 may be identified by a different "Product Identification String", which can be found in the "S49" register. This can be determined by an "ATI0" <retn>. On my own T1000, the "ATI0" returns "968" or a "Model T1SA" and the manual accompanying it is "90062-02 Rev. E". It definitely does *NOT* have register "S110" which is "Trailblazer" spe- cific referring to it's "Compression Mode". Again, apologies for mis-information, and regards.... Steve Walick -- Stephen J. Walick, Asst Sysop of the < XBBS > program at NCoast.ORG uunet!ncoast!nshore!steve nshore!steve@ncoast.org