Path: utzoo!utgpu!water!watmath!uunet!labrea!bloom-beacon!tut.cis.ohio-state.edu!mailrus!ames!ubvax!lll-winken!lll-tis!pacbell!gladys!rbdc!andy
From: andy@rbdc.UUCP (Andy Pitts)
Newsgroups: unix-pc.general
Subject: Re: (Long) Why can't I get PCOMM to work with my Trailblazer?
Summary: Maybe this will help.
Message-ID: <559@rbdc.UUCP>
Date: 13 Sep 88 08:21:07 GMT
References: <454@kosman.UUCP>
Reply-To: andy@rbdc.UUCP (Andy Pitts)
Organization: Red Barn Data Center, Winston-Salem, NC.
Lines: 89

In article <454@kosman.UUCP> kevin@kosman.UUCP (Kevin O'Gorman) writes:
>
>Is there anyone listening who knows how to use PCOMM in this
>configuration?  Emmet, I know you're out there somewhere!!
>
>
>What happens now is that the 'blazer never shows DTR, and the
>call times out. That's using dialer entry 2.
>[...]

Do you have the Telebit plugged into tty000 or tty002?  Entry 4 in the file
below will hook you direct to tty000, entry 2 will hook you to tty002.  If
this is true, the Telebit will never show DTR if you use any entry but 4
because you are talking to the wrong port.

> [...]
>---
>Kevin O'Gorman ( kevin@kosman ) voice: 805-984-8042
>  Vital Computer Systems, 5115 Beachcomber, Oxnard, CA  93035
>

It is hard to debug something like this remote control because I don't know
how the rest of your system is configured.  However here are the obvious
problems I see.

>EEPROM settings:
>E0 F1 M1 Q3 T V1 X1     Version BA4.00
          ^^
This prevents the modem from sending result codes.  Pcomm requires them.
You need to set Q0 in pcomm's init string.

>[...]
>
>Pcomm support files:
>DIR_1=kosman;;19200-N-8-1;F;tty002
>DIR_2=ds;1 (201) 833-0261;1200-E-7-1;F;ds
>DIR_3=mydata;984-9643;1200-N-8-1;F;me
>DIR_4=;;9600-E-7-1;F;tty000
>
>TTY_1=tty002;DIRECT;0
>TTY_2=tty000;TELEBIT-SLOW;9600
       ^^^^^^
Should be tty002 ????

>TTY_3=tty000;TELEBIT-FAST;9600

Same note.

>MODEM_1a=DIRECT;;;;
>MODEM_1b=Y;;;;;;
>MODEM_1c=;;;
>MODEM_2a=TELEBIT-SLOW;%AAAAAATS66=0S51=255S52=2S50=0S95=0!;%AAAAAATS64=1S92=0S7
                                                                         ^^^^^
Note: S92 has no meaning when dialing out.  It only affects how the Telebit
answers.

>=50DT;!;~~+++~~ATDTH0!
                  ^^
Should be ~~+++~~ATH! (you don't realy want to dial out again do you?)

>MODEM_2b=Y;CONNECT 300;CONNECT 1200;CONNECT 2400;;;
>MODEM_2c=BUSY;ERROR;NO CARRIER;
>MODEM_3a=TELEBIT-FAST;%AAAAAATS50=255!;%AAAAAATS64=1S92=0S7=50DTW;!;~~+++~~DTH0!

Same notes as above.

> [...]

For TELEBIT-SLOW try the following:
Init string:		%AAAAAATQ0S50=0S51=255S66=0!
Dial string:		%AAAAAATDTW
Hang up string:		~~+++~~ATH!

For TELEBIT-FAST try the following:
Init string:		%AAAAAATQ0!
Dial string:		%AAAAAATS50=255S111=xxDTW
					    ^^
					    Set this to your favorite file
					    transfer protocol.
Hang up string:		~~+++~~ATH!

Check youy TTY setup and make sure you have the Telebit on the right port
and the Init speed is 9600.

I hope this helps.
-- 
Andy Pitts andy@rbdc.UUCP  : "The giant Gorf was hit in  one eye  by a stone,
bakerst\                   : and that eye  turned  inward  so  that it looked
kd4nc   !gladys!rbdc!andy  : into his mind and he died of what he saw there."
pacbell/                   :   --_The Forgotten Beast of Eld_, McKillip--