Path: utzoo!attcan!uunet!tektronix!orca!tekecs!Zaephod!darylm From: darylm@Zaephod.gwd.tek.com (Daryl V. McDaniel) Newsgroups: comp.dcom.modems Subject: Trailblazer Bugs (was Trailblazer, Misc) Summary: S7 is fast, jerkey PEP and MNP, switch interaction problems Message-ID: <9999@tekecs.TEK.COM> Date: 17 May 88 14:44:54 GMT References: <10273@ulysses.homer.nj.att.com> <10277@ulysses.homer.nj.att.com> <3749@cbmvax.UUCP> <613@wb3ffv.UUCP> <4403@dasys1.UUCP> Sender: nobody@tekecs.TEK.COM Reply-To: darylm@illian.UUCP (Daryl V. McDaniel) Organization: Micronetics, Aloha, Oregon Lines: 61 In article <4403@dasys1.UUCP> manes@dasys1.UUCP (Steve Manes) writes: >I've been installing Telebit support into 'cu' clone source this week and >... >Both are brand-new with 4.0 ROMs. Trouble #1: the S7 register, on >outdial, times out way faster than the value I've given it. For instance, >S7=60 times out closer to half that value. To log in to the other >Trailblazer using PEP and with the answer modem set to S92=1, I have to set >the calling modem to as high as S7=254 to have a good chance of staying on >line long enough to lock with the trailing-end PEP answer tones. >... I have encountered the same problem. It seems the first time an outgoing call is placed after power cycling the modem the timeout is correct. Every time after that it is about half or even less. So far, I have been able to get by with S7=180 > >Trouble #2: logging in at PEP with 9600 baud (under Xenix) produces a REAL >spasmodic display... more than I would assume with packetization. >... I haven't tried this with PEP (I use PEP at 19200 , and then ONLY for uucp) but I have noticed a distinct "jerkiness" using MNP with 2400-baud operation. Also, 80% of the time uucp will fail with a MNP 2400-baud connection. >+----- >+ Steve Manes >+ decvax!philabs!cmcl2!hombre!magpie!manes Magpie BBS: 212-420-0527 >+ SmartMail: manes@magpie.MASA.COM And now for some "new" information. There appears to be an interaction problem with some of the switch settings. Telebit is aware of this problem, I just want to ensure that everyone else out there knows. This is with V4.0 ROMs. If S0 is set to some value greater than 0 (we use 3) AND S92=1 AND (Q6 | Q7) when placing an outgoing call the modem will hang up as soon as it detects carrier. Once the problem was identified the fix was easy (for us anyway). Since we are using a BSD4.3 derived uucp I added "S0=0" to the chat scripts in L-devices for all entries associated with the telebit. When the call is completed, uucico drops DTR to the modem causing the EEPROM values to be reloaded. This resets S0 and all other switches modified by the chat script to their default values. BTW. I really like the "smart" DTR and DSR features of the TB+. These features allow us to use the TB+ for both dial-in and dial-out without having to modify any of the software for which we DON'T have source code. Since the OS our machine has doesn't support acucntrl or any of the neat IOCTLs recently discussed in comp.unix.wizards for opening a port when DCD is not present, the TB+ (or mechanical port switches) were our only solution. -_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_ Daryl V. McDaniel (503) 224-7056 Micronetics; Aloha Research Group 4730 S.W. 182nd Ave. ...tektronix!nosun!illian!darylm Aloha, Oregon 97007 WUI Telex: 6972206