brad@optilink.UUCP (Brad Yearwood) (08/03/89)
We have a Trailblazer+ (BA4.00 ROM) which seems to have trouble dialling out
to 2400 baud modems from our Sun 3/280. The modem is set up for shared
dial-in/dial-out.
If I tip to the TB+ at 2400 then type AAAAATS50=3DT<number>, the modem returns
"NO CARRIER". It appears to disconnect and go back on hook immediately
after the other end answers.
This behavior exists on attempts to connect to two different systems, one
nearby and one distant.
Our full register configuration is:
E1 F1 M1 Q6 P V1 X0 Version BA4.00
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
S45=255 S47=004 S48=000 S49=000
S50=000 S51=254 S52=002 S53=003 S54=003 S55=000 S56=017 S57=019 S58=000 S59=000
S60=000 S61=045 S62=003 S63=001 S64=000 S65=000 S66=000 S67=000 S68=255
S90=000 S91=000 S92=001 S95=000
S100=000 S101=000 S102=000 S104=000
S110=001 S111=030 S112=001
S121=000
Any clues or similar experiences?
Brad Yearwood
Optilink Corp. {pyramid, tekbspa, pixar}!optilink!brad
Petaluma, CA
(707) 795-9444lyndon@cs.AthabascaU.CA (Lyndon Nerenberg) (08/09/89)
In article <2002@optilink.UUCP> brad@optilink.UUCP (Brad Yearwood) writes: >If I tip to the TB+ at 2400 then type AAAAATS50=3DT<number>, the modem returns >"NO CARRIER". It appears to disconnect and go back on hook immediately >after the other end answers. >Any clues or similar experiences? This plagued me for the first couple of days after we installed our first TB's. The solution is to set register 50 to 0, not 3. It seems that setting for an explicit baud rate (other than PEP) causes the TB to be *extremely* picky about what it see's at the remote end. Enabling the autobaud feature (S50=0) results in very reliable connections at low speed. -- Lyndon Nerenberg VE6BBM / Computing Services / Athabasca University {alberta,decwrl,ncc}!atha!lyndon || lyndon@cs.AthabascaU.CA It's 2:00 A.M.; Nobody looks ugly.