cu and kermit hang with new modem

[Russ Conklin_1]

I've added a new modem (connected via a pci mux card) via sam and it created /dev/cul2a2, /dev/ttyd2a2, and /dev/cua2a2. I also edited /etc/uucp/Devices and added the line:
ACU cul2a2 - 9600 hayes

At this point I'm able to use cu and kermit to 'connect' to the modems, but when I do connect nothing happens. With cu, I can't even type in 'at' to see if I get an 'ok' back.
Here is what I do with Kermit:
(/) C-Kermit>set line /dev/cul2a2
(/) C-Kermit>set speed 9600
/dev/cul2a2, 9600 bps
(/) C-Kermit>set modem hayes
(/) C-Kermit>c
Connecting to /dev/cul2a2, speed 9600.
The escape character is Ctrl-\ (ASCII 28, FS)
Type the escape character followed by C to get back,
or followed by ? to see other options.
?Carrier required but not detected.
***********************************
Hint: To CONNECT to a serial device that
is not presenting the Carrier Detect signal,
first tell C-Kermit to:

SET CARRIER-WATCH OFF

***********************************

(/) C-Kermit>

Any help would be appreciated.

[Michael Steele_2]

My notes indicate a different device for /etc/uucp/Devices:

ACU /dev/ttyd2a2 - 9600 hayes

And to dial out with 'cu' to a phone nearby, for instance:

cu -h -l /dev/ttyd2a2 2125551212

Should see:

connected
AT
OK?

ATE1
OK?

[John Dvorchak]

The first thing that I noticed is that Kermit is telling you that it is not detecting a carrier and to "SET CARRIER-WATCH OFF". I think that would be an excellent place to start.

Then you can check function of the modem when you get a solid connection through Kermit. Don't forget that the modem may not respond verbaly if it is set to "Not" echo or "No Responce codes" although a new out of the box modem would problably echo back whatever is typed.

Good luck

[Russ Conklin_1]

I've also tried ACU /dev/ttyd2a2 - 9600 hayes
cu -h -l /dev/ttyd2a2 dir
and I get the connected message but then I can't type anything else in (i.e. the at).

I've also tried the set carrier-watch off with kermit and then I can connect, but again, I can't even type at. It doesn't accept any input from me at all except for the control characters.

Any other ideas?

Thanks for all your help already.

[Michael Steele_2]

Some mux ports aren't dial out. Try this doc:

http://docs.hp.com/hpux/pdf/J3592-90001.pdf

What part number for mux and modem?

[Darren Prior]

Hi Russ,

This sounds like it could be a cabling problem to me. Can you post the specific mux card you have, along with the part numbers of the cables/adaptors you have between the mux card and the modem itself.

As for the device files; using cul2a2 for dialout is fine, however you shouldn't use ttyd2a2 as this is specifically a dial in device file (hence the 'd' in the name.)

It might also be useful for you to post a lssf of the device file.

regards,

Darren.

[Russ Conklin_1]

The PCI mux64 card is A6749-60101 and is attached to a J2485-60010 PM16-DB port module. I'm using the TERMIO-00 driver. The OS is 11i by the way.

Here is the lssf output:
# lssf /dev/cul2a2
pci_mux0 card instance 2 port a2 callout at address 0/1/1/0 /dev/cul2a2

and from ioscan:
tty 2 0/1/1/0 pci_mux0 CLAIMED INTERFACE PCI Serial (113f0
868)
/dev/cua2a10 /dev/tty2a1 /dev/tty2a4
/dev/cua2a2 /dev/tty2a10 /dev/tty2a5
/dev/cua2a3 /dev/tty2a11 /dev/tty2a6
/dev/cul2a10 /dev/tty2a12 /dev/tty2a7
/dev/cul2a2 /dev/tty2a13 /dev/tty2a8
/dev/cul2a3 /dev/tty2a14 /dev/tty2a9
/dev/diag/mux2 /dev/tty2a15 /dev/ttyd2a10
/dev/diag/mux2_1 /dev/tty2a16 /dev/ttyd2a2
/dev/diag/mux2_2 /dev/tty2a2 /dev/ttyd2a3
/dev/mux2 /dev/tty2a3

Hopefully this will be of some help!

[Darren Prior · Accepted solution]

Hi Russ,

Thanks for supplying the info.

Can you confirm that you've installed the PCI mux software - though I suspect the device wouldn't be claimed if you hadn't.

The following document is a useful reference for cabling your mux: http://docs.hp.com/hpux/onlinedocs/5966-8703/5966-8703.html

Have a look at the Port to Device cabling/DB-25 port module section for pinouts if you're making your own cable.

For an HP cable you should be using HP40242M.

regards,

Darren.

[Russ Conklin_1]

Should I be using cables for "full modem control - terminal or printer" or the pinouts for "modem cables"? I only ask because the software that needs the modem, says to set up the modem as a terminal *not* as a modem. I'm a little unclear as to what that means. How do you set up a modem as a terminal?

Also, what mux software are you referring to? I installed TERMIO-00 as the driver but that is all. I searched software.hp.com and TERMIO was the only software listed for A6749.

Thanks for all your help!

[Darren Prior]

Hi Russ,

You'll need the "modem cable" rather than the "full modem control - terminal or printer" cable.

I'm not sure about your software's insistence on setting up a modem as a terminal. A terminal requires a getty in inittab, and a tty device file; a modem may require a getty in inittab if you need to accept incoming calls - but not if it's only used for outgoing calls. Also a modem has a greater number of device files created; though you could get away with just having the tty. Are the instructions specific for HP-UX?

The PCI Mux software is supplied on the Application cds; I don't believe it needs a codeword (as it's no use without the mux!) As your ioscan showed the driver as pci_mux0 it looks like it is installed; though it's worth running:

swlist -l fileset -a state | grep -i mux

to check its' status.

regards,

Darren.

[Michael Steele_2]

Any modem cable will work as long as the pin assignments match:

2-------------2
3-------------3
7-------------7
4-------------4
5-------------5
6-------------6
20------------20

There are 9 pin to 9 pin and 25 pin to 9 pin and 25 pin to 25 pin.

Avoid null modem cables.

Regarding "...setup as a terminal not a modem..." I can only imagine setting the baud rate, flow control, etc. Both have these settings. (* Perhaps the tech writter was without knowledge? *)