[comp.dcom.modems] UUPC via an MCS2400 -> Trailblazer, no connection ?

G.Eustace@massey.ac.nz (Glen Eustace) (05/07/91)

A modem whizz I am not, so if the following problem is trivial then
someone can shoot me.  But before they do can they tell me what is
happenning so I can die in peace.

I am trying to setup a uucp connection between my home and my work.
I have a PC with what I believe to be the most recent version of the
UUPC software and an MCS2400 internal modem.  At work we have a
Pyramid 9815 with an internally mounted Trailblazer modem.

This is the problem, as best as I can describe it.

I have a terminal emulator that doesn't know really know about modems
at all, from memory it sets DTR or DSR or something high all the time
so that it can talk to the modem.  I have the Baud rate set to 2400
and connect by typing ATDT 505701.  The modem at work answers with
the following sounds, please bear with me....

Ssshhhhh    ( for about 1 sec )
silence     ( for about .5 sec )
Ssshhhhh    ( for about 1 sec )
High pitch beep ( for about 1 sec )
Lower pitch beep ( for about .5 sec )

I then get the CONNECT 2400 message.  I can now login and do whatever
I wanted...

Using the UUPC software with a systems entry of DIR rather than
HAYES, I have put the dial code in the Send Expect sequence, so far
so good.  The sequence is ATZ OK ATDT505701 "CONNECT 2400" ... Now
for the weird part.  The Trailblazer answers with the following...

Ssshhhh    ( for about 1 sec )
silence    ( for about .5 sec )
faint click

No connection!  It seems that one or other of the modems is hanging
up the line but I can't tell which or why.  If I now try the terminal
emulator I can successfully connect.

I have got a successful connection from the modem on a couple of
occassions but they are very much the exception.  I have examined the
uuio logfile and it does not indicate that any setup other than that
mentioned is occurring.  They only thing I can't see is the RS232
signals.  Could the problem be in this area, and if so what ?

Any assistance with this problem would be very much appreciated.


-- 
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Glen Eustace, Systems Software Manager | EMail: G.Eustace@massey.ac.nz
 Computer Centre,  Massey University,  Palmerston North,  New Zealand
Phone: +64 63 69099 x7440, Fax: +64 63 505 607,       Timezone: GMT-12

root@zswamp.uucp (Geoffrey Welsh) (05/07/91)

In a letter to All, Glen Eustace (G.Eustace@massey.ac.nz ) wrote:

(To all people having difficulty connecting to TrailBlazers with 'normal' 
modems)

(1) *disable* voice answer detect, if there is any on your modem.

(2) Use a fairly large S7 value, 10-15 seconds longer than normal.

(3) Use S9=12 to prevent false carrier detect on PEP tones.

   These usually help; they've worked for me on Everex, USRobotics, and Hayes 
modems.
 

--  
Geoffrey Welsh - Operator, Izot's Swamp BBS (FidoNet 1:221/171)
root@zswamp.uucp or ..uunet!watmath!xenitec!zswamp!root
602-66 Mooregate Crescent, Kitchener, ON, N2M 5E6 Canada (519)741-9553
"He who claims to know everything can't possibly know much" -me