# 8r 920 PCI COMMUNICATION

**URL:** <https://forums.digi.com/t/8r-920-pci-communication/7837>\
**Category:** USB Devices\
**Created:** [March 29, 2006, 1:49pm UTC](https://forums.digi.com/t/8r-920-pci-communication/7837 "2006-03-29T13:49:19Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![ktizifa](https://avatars.discourse-cdn.com/v4/letter/k/6f9a4e/32.png) [@ktizifa](https://forums.digi.com/u/ktizifa)\
**Post date:** [March 29, 2006, 1:49pm UTC](https://forums.digi.com/t/8r-920-pci-communication/7837/1 "2006-03-29T13:49:19Z")

</div>

I recently installed an acceleport 8r 920 PCI card into an HP rp3410 server running HP UX 11i version 1 I downloaded the driver 40001526\_d.tar from the digi support download site. The driver configured successfully and device files were created and entries also updated in the /etc/inittab file .I can login and work on any of the eight port on the card.

One of the devices I have to connect to the digi is a security encryptor which uses a straight thru (null) modem cable. This device is currently working OK on an identical server which has a digi 8p card installed.

My problem is that when I start the same application on this server as on the working server, it fails and report that the port to which the device is connected is ‘busy’ .When I make a loopback test (using DPA utility) on the 8r 920 card it also displays ‘port busy’. The signals DTR RTS CD DSR all change sign to + when connected and - when disconnected, except for DTR AND RTS which don’t change. What could I be missing? Are the drivers correct?

---

<div class="post-metadata">

**Author:** ![michaelt](https://sea2.discourse-cdn.com/flex016/user_avatar/forums.digi.com/michaelt/32/92_2.png) [@michaelt](https://forums.digi.com/u/michaelt)\
**Post date:** [April 6, 2006, 5:42pm UTC](https://forums.digi.com/t/8r-920-pci-communication/7837/2 "2006-04-06T17:42:43Z")

</div>

It sounds like your settings are correct, but the application you’re running on the port is taking exlusive control of the port (thereby blocking other things accessing the port at the same time). There is no port setting that will change this behavior, as its at an ioctl/programming level with the application. I believe that’s what is going on. Best bet would be to call Tech Support about this one though.