grisanti@plains.NoDak.edu (Ames Grisanti) (08/01/90)
The original problem was that I wanted to connect a uVAX II to a PACX for access to other computers on the network. I was previously using a 2400 baud modem to dial-up the network. A 9600 baud PACX line became available so an attempt was made to connect to this by one of the uVAX serial ports. The problem being that the 9600 baud line needed a break signal followed by a carriage return to 'wake up'. Previously I was using kermit-32 for the modem connection as it made for easy file transfers to/from the other systems. This would no longer work since kermit-32 is not capable of sending a break. Hence my previous post. Several people responded to my question about connecting a uVAXII to a PACX by serial port. Most suggestions involved trying to reprogram the PACX connection from the communications processor. Since this solution depends on the particular PACX hardware involved most people asked for more information. This is a good solution and an attempt was made to get the system communicating by reconfiguration of the PACX port connected to the uVAX. After some experimentation which involved 3 HRS on the phone with the campus network manager we could get the system to talk by setting the PACX to 'wake up' on DTR plus a carriage return. The PACX still responded intermittently. So we decided to try another (simpler) solution which was suggested by Aaron Leonard (leonard@arizona.edu). He uses a program in FORTRAN to send the break signal out prior to executing kermit. Then one simply pressed <CR> after connecting to the proper port with kermit. The source code for break.for may be gotten by anonymous FTP from ARIZONA.EDU - directory UA_SOURCE:[BREAK]. After changing the parameter in the FORTRAN source to use the proper terminal line (TXA0 in my case) the program was compiled and a DCL command file was used to execute the break program before kermit. The DCL file I used follows: $ allocate txa0 ! grab port connected to pacx $ run sys$system:break ! send break to TXA0 for pacx wake up $ ! run kermit and connect to pacx $ run sys$system:kermit connect txa0 $ run sys$system:break ! send two breaks on exit from kermit $ run sys$system:break ! to disconnect pacx $ deallocate txa0 ! let go of TXA0 Of course the user must have the proper privileges set in order to allocate devices. And the port used to connect to pacx should have the proper settings (set term txa0/speed=9600...etc./perm). This method of connection works well and required no reprogramming of the PACX communications processor. If anyone would like more info on doing this please E-mail me with questions. Thanks to all those who helped me with suggestions. Ames Grisanti [grisanti@plains.NoDak.edu -- Internet] [grisanti@plains or ndsuvax -- Bitnet ] [uunet!plains!grisanti -- UUCP ]