acucap problems

From: Stuart Kreitman <skk_at_benelux.pa.dec.com>
Date: Fri, 17 Nov 1995 11:09:47 -0800 (PST)

Mgrs:

I'm trying to get tip to treat my modem as an autodialer.
Its a Practical Peripherals PM14400FXMT, V.32bis, AT command
set. The host is Alphastation 200 4/233, Digital Unix 3.2c.

Running genvmunix today.

Ordinary tip works fine. The init files are hooked together
ok:

                /etc/remote

lat:dv=/dev/tty00:br#19200:pa=none:pn=18006986559:at=ppi:du

                /etc/acucap

ppi|Practical Peripherals PM14400FXMT:\
        :db:cr:hu:ls:re:ss=\dAT\r:sr=OK:sd#250000:di=ATDT:dt=\r:\
        :dd#50000:fd#500:rs=,:os=CONNECT:ds=\d+++\dATZ\r:ab=\d+++\dATZ:

since the "db" (debug) flags is in the acucap entry, I get a log
of the dialout session.

3 problems that I notice are:

1) TIP mistakes the modem's response to the "ss" string as an
echo of "ss" rather than "sr". I can get around this by
setting ss=\nAT\n:sr=\nAT\n, Still, the response "OK"
should be issued.

2) In gathering the response, TIP says "read - would block"
I presume this is the central problem.

3) TIP reports that it has carrier when it certainly doesn't.
When supposedly dialing the number, nothing much happens at
the modem, neither does TIP wait for carrier. It just blasts
right on through.

I'll go off and collect a clean log of this. Are there kernel
parameters relevent to the tty's, like there used to be in Ultrix?

thanks for any help

Stuart Kreitman
Received on Fri Nov 17 1995 - 22:16:53 NZDT

This archive was generated by hypermail 2.4.0 : Wed Nov 08 2023 - 11:53:46 NZDT