Quatech DSP-200/300 - Manual

DSP-200/300 Client Driver for DOS

In order to use the DSP-200/300 Client Driver, the system must be configured with Card and Socket Services software. Card and Socket Services software is not provided with the DSP-200/300 but is available from Quatech.

Client Driver Installation

The following procedure is used to install the DSP-200/300Client Driver:

1. Copy the Client Driver from the DSP-200/300 distribution diskette onto the system's hard drive.
2. Using an ASCII text editor, open the system's CONFIG.SYS file located in the root directory of the boot drive.
3. Locate the line(s) in the CONFIG.SYS file where the Card and Socket Services software is installed.
4. AFTER the line(s) installing the Card and Socket Services software, add the following line to the CONFIG.SYS file: DEVICE = drive:\path\ DSP230CL.SYS options where options are the DSP-200/300 Client Driver command line options discussed on the following pages.
5. Save the CONFIG.SYS file and exit the text editor.
6. Insert the DSP-200/300 into one of the system's PCMCIA slots.

7. Reboot the system and note the message displayed when the DSP-200/300 Client Driver is loaded. If the Client Driver reports an "invalid command line option", correct the entry in the CONFIG.SYS file and reboot the system again. If the Client Driver reports "Card and Socket Services not found", a version of Card and Socket Services must be installed on the system or the DSP-200/300 Enabler program must be used to configure the adapter. If the Client Driver reports the desired adapter configuration, the installation process is complete and the DSP-200/300 may be removed and/ or inserted from the system as desired. On each insertion into the PCMCIA socket, the DSP-200/300 will be automatically reconfigured according to the command line options.

Command Line Options

The DSP-200/300 Client Driver accepts up to eight command line arguments from the user to determine the configuration of theDSP-200/300. If any arguments are provided, the Client Driver will attempt to configure any DSP-200/300s with the options specified in the order they are entered on the command line. Each argument must be enclosed in parenthesis and must be separated from other arguments by a space on the command line. Within each argument, any or all of the following parameters may be specified using a comma (no spaces) to separate each parameter:

Baddress specifies a the base I/O address of the DSP-200/300in hexadecimal. This address must reside on an even 8-byte boundary. If this option is omitted, a base address will be assigned by Card and Socket Services.

Iirq specifies the interrupt level (IRQ) of the DSP-200/300in decimal. irq must be one of the following values: 3, 4, 5, 7, 9, 10, 11, 12, 14, 15, or 0 if no IRQ is desired. If this option is omitted, an interrupt level will be assigned by Card and Socket Services.

Ssocket specifies which PCMCIA socket the DSP-200/300must be inserted into for this configuration argument to be used. socket must be in the range 0 - 15. If this option is omitted, the configuration argument will apply to DSP-200/300s inserted into any socket. Odriver specifies RS-422/485 output driver enable option for the DSP-200/300 port. The DSP-200/300’s port may be configured for either full duplex or half duplex operation with this option. If this option is omitted, the default setting is the RS-422/485 port is configured for full duplex operation with the RS-422/485 output drivers always enabled. In half duplex mode, the RS-422/485 transmitter may be enabled and disabled via the RTS (request to send) or DTR (data terminal ready) signals. Both RTS and DTR are controlled through the Modem Control Register of the 16750. See the Hardware Information section for more information.

Figure 3. DOS Client Output Enable Options.

H instructs the client driver to enable the RTS-CTS modem control handshake on the RS-422/485 port. When modem control handshaking in enabled, the 16C750 UART’s RTS and CTS signals are connected to the RS-422/485 auxiliary channel. The auxiliary channel may then be used for handshaking between the DSP-200/300’s port and a peripheral device. When modem control handshaking is disabled, the RTS and CTS signals from the 16C750 UART are looped back to each other. If this option is omitted, the default setting is RTS-CTS modem control handshake disabled. See the Hardware Information section for more information.

2.1.2.1 Example 1 DEVICE = C:\DSP-200\ DSP230CL.SYS

In example 1, no command line arguments are specified. The Client Driver will configure a DSP-200/300 inserted into any socket with a base address and IRQ assigned by Card and Socket Services. The DSP-200/300 RS-422/485 output drivers will always be enabled, and RTS-CTS modem control handshaking will be disabled.

2.1.2.2 Example 2 DEVICE = C:\DSP-200\DSP230CL.SYS (b290,i11)

In example 2, a single command line argument is provided. The Client Driver will attempt to configure a DSP-200/300 inserted into any socket with a base address of 290H and IRQ 11. If address 290H or IRQ 11 is unavailable, the DSP-200/300 will not be configured. If the Client Driver can successfully configure the DSP-200/300unit, the RS-422/485 output drivers will always be enabled, and RTS-CTS modem control handshaking will be disabled.

2.1.2.3 Example 3 DEVICE = C:\DSP-200\DSP230CL.SYS(s0,b300,i5,o2)

In example 3, a single command line argument is provided. The Client Driver will attempt to configure a DSP-200/300 inserted into socket 0 with a base address of 300H and IRQ 5. If address 300H or IRQ 5 is unavailable, the DSP-200/300 will not be configured. In addition, if a DSP-200/300 is inserted into any other socket, it will not be configured. If the Client Driver can successfully configure the DSP-200/300, the RS-422/485 output drivers will be enabled and disabled via the RTS signal, and RTS-CTS modem control handshaking will be disabled.

2.1.2.4 Example 4 DEVICE = C:\DSP-200\DSP230CL.SYS(i5,h,b300)

In example 4, a single command line argument is provided. Because the parameter order is not significant, the Client Driver will attempt to configure a DSP-200/300 inserted into any socket with a base address of 300H and IRQ 5. If address 300H or IRQ 5 is unavailable, the DSP-200/300 will not be configured. If the Client Driver can successfully configure the DSP-200/300, the RS-422/485 output drivers will always be enabled, and RTS-CTS modem control handshaking will be enabled on the RS-422/485 port’s auxiliary channel.

2.1.2.5 Example 5 DEVICE = C:\DSP-200\DSP230CL.SYS (b300,i5) (i10) ( )

In example 5, three command line arguments are provided. The Client Driver will first attempt to configure a DSP-200/300 inserted into any socket with a base address of 300H and IRQ 5. If address 300H or IRQ 5 is unavailable, the Client Driver will proceed to the second command line argument and attempt to configure the card with a base address assigned by Card and Socket Services and IRQ 10. If IRQ 10 is also unavailable, the Client Driver will proceed to the third command line argument and attempt to configure the DSP-200/300 with a base address and an IRQ assigned by Card and Socket Services. If the Client Driver can successfully configure the DSP-200/300, the RS-422/485 output drivers for will always be enabled, and RTS-CTS modem control handshaking will be disabled.

2.1.2.6 Example 6

DEVICE = C:\DSP-200\DSP230CL.SYS (b300,i5) ( ) (i10)

In example 6, the three command line arguments of example 5 have been rearranged. The Client Driver will first attempt to configure a DSP-200/300 inserted into any socket with a base address of 300H and IRQ 5. If address 300H or IRQ 5 is unavailable, the Client Driver will proceed to the second command line argument and attempt to configure the card with a base address and IRQ assigned by Card and Socket Services. Since the second command line argument includes all available address and IRQ resources, the third command line argument will never be reached by the Client Driver. It is the user's responsibility to place the command line arguments in a logical order.

2.1.2.7 Example 7

DEVICE = C:\DSP-200\DSP230CL.SYS (s0,b300,i5) (s1,b340,i10)

The type of configuration shown in example 7 may be desirable in systems where more than one DSP-200/300 is to be installed. In this example, the Client Driver will attempt to configure a DSP-200/300 inserted into socket 0 with a base address of 300H and IRQ 5. If the DSP-200/300 is inserted into socket 1, the Client Driver will attempt to configure it with base address 340H and IRQ 10. This allows the user to force the DSP-200/300's address and IRQ settings to be socket specific which may simplify cable connections and software development. As in the previous examples, however, if the requested address or interrupt resources are not available, the DSP-200/300 will not be configured.

Common Problems

Generic Client Drivers: Many Card and Socket Services packages include a generic client driver (or SuperClient) which configures standard I/O devices. If one of these generic client drivers is installed, it may configure the DSP-200/300 causing the DSP-200/300 client driver to fail installation. In these cases, the user should do one of the following:

1. Modify the operation of the generic client driver to disable the configuration of modem/serial port cards. Consult the Card and Socket Services documentation for availability and details of this feature.
2. Place the DSP-200/300 client driver before the generic client driver in the CONFIG.SYS.

Available Resources: One function of the Card and Socket Services software is to track which system resources (memory addresses, I/O addresses, IRQs, etc.) are available for assignment to inserted PCMCIA cards. Sometimes, however, the Card Services software assumes or incorrectly determines that a particular resource is used when it is actually available. Most Card and Socket Services generate a resource table in a file (typically in the form of an .INI file) which the user can modify to adjust the available system resources. Consult the Card and Socket Services documentation for availability and details of this feature.

Multiple Configuration Attempts: Some Card and Socket Services have a setting which aborts the configuration process after a single configuration failure (such as a request for an unavailable resource). The user should change this setting to allow for multiple configuration attempts. Consult the Card and Socket Services documentation for availability and details of this feature.

Older Versions of Card and Socket Services: Some versions of Card and Socket Services dated before 1993 do not support general purpose I/O cards. If after careful installation of the Client Driver the DSP-200/300 does not configure or operate properly, an updated version of Card and Socket Services may be required. Card and Socket Services software is available from Quatech.

DSP-200/300 Enabler for DOS

For systems that are not operating PCMCIA Card and Socket Services software, the DSP-200/300 DOS Enabler may be used to enable and configure the adapter. This Enabler, DSP230EN.EXE, will operate on any DOS system using an Intel 82365SL or PCIC compatible PCMCIA host adapter including the Cirrus Logic CL-PD6710 /6720, the VLSI VL82C146, and the Vadem VG-365 among others.

The DSP-200/300 Enabler does not support automatic configuration of adapters upon insertion, more commonly referred to as "Hot Swapping". This means the adapter must be installed in one of the system's PCMCIA sockets before executing DSP230EN.EXE. If more than one adapter is installed in a system, the Enabler must be executed separately for each adapter. Furthermore, DSP230EN.EXE should be executed to release the resources used by the adapter before it is removed from the PCMCIA socket. Since PCMCIA adapters do not retain their configuration after removal, any adapter that is removed from the system must be reconfigured with the Enabler after re-inserting it into a PCMCIA socket.

Command Line Options

To configure a DSP-200/300 in the system, the Enabler requires one command line argument from the user to determine the configuration of the card. This argument must be enclosed in parenthesis and within the argument, any or all of the following parameters may be specified using a comma (no spaces) to separate each parameter:

Ssocket specifies which PCMCIA socket the DSP-200/300 must be inserted into for this configuration argument to be used. socket must be in the range 0 - 15. This option is required if the 'R' option is not used.

Baddress specifies the base I/O address of the DSP-200/300 in hexadecimal. This address must reside on an even 8-byte boundary. This option is required if the 'R' option is not used.

Iirq specifies the interrupt level (IRQ) of the DSP-200/300 in decimal. irq must be one of the following values: 3, 4, 5, 7, 9, 10, 11, 12, 14, 15, or 0 if no IRQ is desired. This option is required if the 'R' option is not used.

Waddress specifies the base address of the memory window required to configure the DSP-200/300. Set address = D0 for a memory window at segment D000, address = D8 for a memory window at segment D800, etc. Valid settings for address are C8, CC, D0, D4, D8, and DC. If this option is omitted, a memory window at segment D000 will be used.

Odriver specifies RS-422/485 output driver enable option for theDSP-200/300. The DSP-200/300’s port may be configured for either full duplex or half duplex operation with this option. If this option is omitted, the default setting is the RS-422/485 port is configured for full duplex operation with the RS-422/485 output drivers always enabled. In half duplex mode, the RS-422/485 transmitter may be enabled and disabled via the RTS (request to send) or DTR (data terminal ready) signals. Both RTS and DTR are controlled through the Modem Control Register of the 16750. See the Hardware Information section for more information.

Figure 4. DOS Enabler Output Enable Options.

H instructs the enabler to enable the RTS-CTS modem control handshake on the RS-422/485 port. When modem control handshaking in enabled, the 16C750 UART’s RTS and CTS signals are connected to the RS-422/485 auxiliary channel. The auxiliary channel may then be used for handshaking between the DSP-200/300’s RS-422/485 port and a peripheral device. When modem control handshaking is disabled, the RTS and CTS signals from the 16C750 UART are looped back to each other. If this option is omitted, the default setting is RTS-CTS modem control handshake disabled. See the Hardware Information section for more information .

Before removing a DSP-200/300 from its PCMCIA socket, the Enabler should be executed to free the system resources allocated when the card was installed. For this operation the Enabler provides on additional command line option:

R instructs the enabler to release the resources previously allocated to the DSP-200/300 . When the 'R' option is used, any settings specified by the 'B', 'I', 'O', and 'H' options are ignored.

2.2.1.1 Example 1 DSP230EN.EXE

In example 1, no command line argument is specified. The Enabler will report an error and display the proper usage of the command.

2.2.1.2 Example 2 DSP230EN.EXE (s0,b300,i5)

In example 2, the Enabler will configure the DSP-200/300 in socket 0 with a base address of 300H and IRQ 5 using a configuration memory window at segment D000. The DSP-200/300 unit's RS-422/485 output drivers will always be enabled, and RTS-CTS modem control handshaking will be disabled.

2.2.1.3 Example 3 DSP230EN.EXE (i10,h,b340,s1)

In example 3, the Enabler will configure the DSP-200/300 in socket 1 with a base address of 340H and IRQ 10 using a configuration memory window at segment D000. The DSP-200/300's RS-422/485 output drivers will always be enabled, and RTS-CTS modem control handshaking will be enabled on the RS-422/485 auxiliary channel.

2.2.1.4 Example 4 DSP230EN.EXE (s0,b300,i3,wd8)

In example 4, the Enabler will configure the DSP-200/300 in socket 0 with a base address of 300H and IRQ 3 using a configuration memory window at segment D800. The DSP-200/300's RS-422/485 output drivers will always be enabled, and RTS-CTS modem control handshaking will be disabled

2.2.1.5 Example 5 DSP230EN.EXE (o1,i5,b340,s1)

In example 2, the Enabler will configure the DSP-200/300 in socket 1 with a base address of 340H and IRQ 5 using a configuration memory window at segment D000. The DSP-200/300's RS-422/485 output drivers will be enabled and disabled via the DTR signal, and RTS-CTS modem control handshaking will be disabled

2.2.1.6 Example 6 DSP230EN.EXE (s0,b300,i5,r)

In example 6, the Enabler will release the configuration used by the DSP-200/300 in socket 0 using a configuration memory window at segment D000. The base address and IRQ parameters are ignored and may be omitted.

2.2.1.7 Example 7 DSP230EN.EXE (s1,r,wcc)

In example 7, the Enabler will release the configuration used by the DSP-200/300 in socket 1 using a configuration memory window at segment CC00.

Common Problems

Memory Range Exclusion: The Enabler requires a region of high DOS memory when configuring aDSP-200/300. This region is 1000H bytes (4KB) long and by default begins at address D0000H (the default address may be changed using the "W" option). If a memory manager such as EMM386, QEMM, or 386Max is installed on the system, this region of DOS memory must be excluded from the memory manager's control. Consult the documentation provided with the memory manager software for instructions on how to exclude this memory region.

Furthermore, some systems use the high memory area for BIOS shadowing to improve overall system performance. In order for the Enabler to operate, any BIOS shadowing must be disabled in the address range specified for the configuration window. BIOS shadowing can usually be disabled through the system's CMOS setup utility.

Socket Numbers: The Enabler requires the DSP-200/300's socket number to be specified on the command line and the DSP-200/300 must be inserted into the socket before the Enabler is invoked. Some vendors number their sockets from 1 to N while other vendors number their sockets from 0 to N-1. For theDSP-200/300 Enabler, the lowest socket number in the system is designated socket 0.

Card and Socket Services Software: In order to use the DSP-200/300 Enabler for DOS, the system MUST NOT be configured with Card and Socket Services software. If a Card and Socket Services software is installed, the Enabler may interfere with its operation and with the device(s) it controls. For systems configured with Card and Socket Services, the DSP-200/300 Client Driver is the recommended method of configuration.

Installing a DSP-200/300 Under Windows 95/98/ME

1. Insert the DSP-200/300 into any available PC Card socket.
2. The first time a new PC Card type is installed the New Hardware Found window opens. After this first installation Windows 95/98/ME will automatically detect and configure the card. If the New Hardware Found window does not open, then skip to the next section, “DSP-200/300 Resource Settings".
3. The New Hardware Found window provides several options to configure the DSP-200/300 card. Click the "Search for the best driver for your device" option button. Click "NEXT" to continue.
4. An "Install from Disk" dialog box should appear. Insert the Quatech COM CD file, select the correct drive letter and path, and click "OK". Windows 95/98/ME will browse the path for the aforementioned files.
5. During the installation process, it may be required to supply the computer with the Windows 95/98/ME CD or installation CDs. Insert the CD and click "OK". The DSP-200/300 PC Card should now be configured. With the default configuration, the DSP-200/300's interrupt status register will be enabled, the 16C750 UART’s scratchpad register will be disabled, the RS-422/485 output drivers will always be enabled, and RTS-CTS modem control handshaking will be enabled. In the future, Windows 95/98/ME will automatically recognize and configure the DSP-200/300 in this default configuration.

DSP-200/300 Resource Settings in Windows 95/98/ME

Windows 95/98/ME maintains a registry of all known hardware installed within the computer. Inside this hardware registry Windows 95/98/ME keeps track of all the computer's resources, such as base I/O addresses, IRQ levels, and DMA channels. In the case of a PC Card (PCMCIA) type board, Windows 95/98/ME configures the new hardware using free resources it finds within the hardware registry, and updates the registry automatically.

To view and/or edit hardware devices in Windows 95/98/ME use the system Device Manager. To access Device Manager double click the System icon in the Windows 95/98/ME control panel, or click the My Computer icon on the Windows 95/98/ME desktop with the right mouse button and select Properties from the pull down menu. Consult Windows 95/98/ME on-line help for details on the use of the Device Manager.

Viewing Resource Settings with Device Manager

1. Start the Windows 95/98/ME Device Manager.
2. Double click on the hardware class Quatech Comm Adapters to list hardware devices in the class.
3. The DSP-200/300 “parent device” belongs to this hardware class. The device name for the DSP-200/300 is Quatech DSP-200/300: Dual RS-422/RS-485 Serial Port PC Card.
4. Open the Properties dialog for the DSP-200/300 device, then click the Resources tab to view the Input/Output Range and Interrupt Request resource allocations.
5. Double click the hardware class Ports (Com and LPT). Each Quatech Communications Port listed in this class is a “child device” of the DSP-200/300 “parent device.”
6. Open the Properties dialog for a COM port, then click the Resources tab to view the Input/Output Range and Interrupt Request resource allocations. These will match those of the “parent device.”
7. Record the COM Port device names (COM1, COM2, etc.) for the DSP-200/300. These names are required by Windows 95/98/ME applications when accessing particular ports.

Changing Resource Settings with Device Manager

1. Start the Windows 95/98/ME Device Manager.
2. Double click on the hardware class Quatech Comm Adapters to list hardware devices in the class.
3. The DSP-200/300 “parent device” belongs to this hardware class. The device name for the DSP-200/300 is Quatech DSP-200/300: Dual RS-422/RS-485 Serial Port PC Card.
4. Open the Properties dialog for the DSP-200/300 device, then click the Resources tab to view the Input/Output Range and Interrupt Request resource allocations.
5. Several predefined Basic Configurations have been included for the DSP-200/300 (see Figure 5. DSP-200/300 Basic Configuration Table). The Basic Configurations provide many combinations of the operating modes and options listed below. See the Hardware Information section of this manual for complete descriptions. RS-422/485 output drivers enable option: The DSP-200/300’s ports may be
   configured for either full duplex or half duplex operation with this option. The default setting is the RS-422/485 ports are configured for full duplex operation with the RS-422/485 output drivers always enabled. In half duplex mode, the RS-422/485 transmitter may be enabled and disabled via the RTS (request to send) or DTR (data terminal ready) signals, or set to enable only when data is being transmitted (auto-toggle). Both RTS and DTR are controlled through the Modem Control Register of the 16750. When the Use Automatic Settings check box is enabled Windows 95/98/ME will attempt to configure the DSP-200/300 in the order listed in the Basic Configurations table.

** Handshaking indicates RTS routed to AUXOUT, AUXIN routed to CTS, and TCLK routed to RCLK. Loopback indicates RTS routed to CTS, AUXIN routed to AUXOUT, and TCLK routed to RCLK. Clocking indicates RTS routed to CTS, AUXIN routed to RCLK, and TCLK routed to AUXOUT.

*** Any indicates variable value; this value may or may not be user selectable depending on platform.

6. Select a Basic Configurations that displays "No conflicts" in the bottom display region titled Conflicting Device List from the drop down list. Some applications may not be able to access ports higher than COM4. To use the DSP-200/300 PCMCIA serial ports with these applications you might be forced to remove other serial communications devices from your system
7. To modify the Interrupt Request setting click the resource name and click the Change Setting button. An Edit Resource window will open up. Inside this window click on the up/down arrows to the right of the Interrupt Request value. This scrolls you through all of the allowable resources for your hardware. Pay attention to the conflict information at the bottom of the window. Do not select a value that causes a conflict with any other installed hardware.
8. If any changes have been made to the DSP-200/300’s configuration the card will automatically be reconfigured to the new resources specified. Any time a PCMCIA card of this type is inserted Windows 95/98/ME will attempt to configure the card at these resource settings. Click the Use Automatic Settings box to reset this card type for automatic configuration.

Frequently Asked Questions

Basic Configuration List Not Available: A problem noted on some systems is after a basic configuration has been manually selected the basic configurations list for the DSP-200/300 is no longer available. The solution to this problem is to check the “Use Automatic Settings” box and allow Windows 95/98/ME to reconfigure the DSP-200/300 card. The basic configurations list should once again be visible.

Base I/O Address Resource Modification Not Allowed: The DSP-200/300 is configured to allow only a fixed number of base I/O addresses. To change the I/O address resources for the DSP-200/300 select another “Basic Configuration”. Refer to the Basic Configurations table for a list of the availabe I/O address resources for the DSP-200/300

Installing a DSP-200/300 Under Windows 2000.

1. Insert the Quatech COM CD into an available CD-ROM.
2. Insert the DSP-200/300 into any available PC Card socket.
3. You will be prompted tosearch for the correct driver. Choose the drive where the quatech COM CD is located and select “Browse” from the ‘Files Needed’ window.

4. Double click ‘Serial Port Adapters’

5. Double click ‘Drivers’

6. Double click on ‘Windows 2000, XP, for PCI, PCMCIA, ISA’

7. Click on ‘qserbrd’ and select open.

8. Select ‘OK’ at the ‘Files Needed’ window

9. The same process as above in steps 1-9 will apply for the next file ‘qserpt.inf’. In step 7 be sure to choose ‘qserpt.inf’ and select ‘Open’.

DSP-200/300 Resource Settings in Windows 2000

Windows 2000 maintains a registry of all known hardware installed within the computer. Inside this hardware registry Windows 2000 keeps track of all the computer's resources, such as base I/O addresses, IRQ levels, and DMA channels. In the case of a PC Card (PCMCIA) type board, Windows 2000 configures the new hardware using free resources it finds within the hardware registry, and updates the registry automatically.

To view and / or edit hardware devices in Windows 2000 use the system Device Manager.

To access Device Manager double click the System icon in the Windows 2000 control panel, or click the My Computer icon on the Windows 2000 desktop with the right mouse button and select Properties from the pull down menu. Click on the Hardware tab then click on the Device Manager. Consult Windows 2000 on-line help for details on the use of the Device Manager

Windows 2000 handles the DSP-200/300 as a "parent/child device". v The DSP-200/300 is the "parent device" and is listed under the hardware class Quatech Multiport Serial Devices in the device manager v Each serial port is a "child device" of the "parent device" DSP-200/300 (Quatech PCMCIA Serial Port). There are 2 child COM ports for the DSP-200/300 (Quatech PCMCIA Serial Port) which are listed under the hardware class Ports (Com & LPT).

Viewing Resource Settings with Device Manager

1. Start the Windows 2000 Device Manager.
2. Double click on the hardware class Quatech Multiport Serial Devices to list hardware devices in the class.

3. The DSP-200/300 “parent device” belongs to this hardware class. The device name for the DSP-200/300 is Quatech DSP-200/300 PCMCIA Two-Port RS-422/RS-485 Serial Adapter. (Figure 10)
4. Open the Properties dialog for the DSP-200/300 device, then click the Resources tab to view the Input/Output Range and Interrupt Request resource allocations. Examine and remember the Input/Output Range, then close the properties window.
5. Double click the hardware class Ports (Com and LPT). Each Quatech PCMCIA Serial Port listed in this class is a “child device” of the DSP-200/300 “parent device.”

6. Use the COM Port device names (COM5, COM6, etc.) to access any of the particular serial ports on the DSP-200/300. These names are required by Windows 2000 applications when accessing particular ports.

Changing Resource Settings with Device Manager

1. Start the Windows 2000 Device Manager. To access Device Manager double click the System icon in the Windows 2000 control panel, or click the My Computer icon on the Windows 2000 desktop with the right mouse button and select Properties from the pull down menu. Click on the Hardware tab then click on the Device Manager. Consult Windows 2000 on-line help for details on the use of the Device Manager
2. Double click on the hardware class Quatech Multiport Serial Devices to list hardware devices in the class. (Figure 10)
3. The DSP-200/300 “parent device” belongs to this hardware class. The device name for the DSP-200/300 is Quatech DSP-200/300 PCMCIA Two-Port RS-422/RS-485 Serial Adapter. (Figure 10)
4. Open the Properties dialog for the DSP-200/300 device (Figure 12), then click the Advanced tab to view the clock rate settings.

5. Click the RS-422/485 tab to view the transmitter enable and connector pinout option.

6. Click the Resources tab to view the Input/Output Range and Interrupt Request resource allocations. If options that are not available on the preceding pages are required, a different basic configuration will have to be selected. To do this, de-select the Use Automatic Settings box and choose the basic configuration that corresponds to the set of options required.

** Handshaking indicates RTS routed to AUXOUT, AUXIN routed to CTS, and TCLK routed to RCLK. Loopback indicates RTS routed to CTS, AUXIN routed to AUXOUT, and TCLK routed to RCLK. Clocking indicates RTS routed to CTS, AUXIN routed to RCLK, and TCLK routed to AUXOUT.

*** Any indicates variable value; this value may or may not be user selectable depending on platform.

7. Select a Basic Configuration that displays "No conflicts" in the bottom display region titled Conflicting Device List from the drop down list.
8. Windows 2000 should have chosen an available Interrupt Request setting automatically when the I/O address range was configured by a Basic Configuration selection. This default Interrupt Request setting should not need changed as long as "No conflicts" is displayed in the bottom display region titled Conflicting Device List. If you are satisfied with Windows 2000 selection then skip the next step.
9. To modify the Interrupt Request setting click the resource name and click the Change Setting button. An Edit Resource window will open up. Inside this window click on the up/down arrows to the right of the Interrupt Request value. This scrolls you through all of the allowable resources for your hardware. Pay attention to the conflict information at the bottom of the window. Do not select a value that causes a conflict with any other installed hardware.
10. If any changes have been made to the DSP-200/300’s configuration the card will automatically be reconfigured to the new resources specified. Any time a PCMCIA card of this type is inserted Windows 2000 will attempt to configure the card at these resource settings. Click the Use Automatic Settings box to reset this card type for automatic configuration

Installing DSP-200/300

To allow easy configuration of the DSP-200/300 the Quatech Device Manager for Windows NT has been written for the hardware. This configuration utility supports the DSP-200/300 only in block addressing mode.

To begin the installation, open Windows Explorer and search for the ‘Setup.exe’ command to install the Quatech Device Manager. <See following Windows Explorer figure.> (D:\Serial Port Adapters\Drivers\Windows NT 4.0 for PCI, PCMCIA,ISA). Once the installation is complete an icon will be placed on the desktop.

Windows NT Explorer

1. Locate and double click the Quatech Device Manager icon on the desktop

Device Manager Icon on Desktop

2. Click the ‘Add’ button at the bottom of the Quatech Device Manager Window

3. Follow the steps for the ‘Add Quatech Hardware Wizard’.

4. Complete the final steps of the installation, shut down Windows NT and then insert the PCMCIA Card and re-boot the computer. Additional help is available online

The DSP-200/300 PC Card should now be configured. In the future, Windows NT will automatically recognize and configure the DSP-200/300.

Auxiliary Channel Configuration

An auxiliary channel is provided which allows for handshaking between the DSP-200/300 port and a peripheral device. This auxiliary channel may be configured in one of two ways: v RTS-CTS handshake enabled. v handshaking is disabled.

Auxiliary Channel: RTS-CTS Handshaking.

The RTS-CTS handshake may be enabled so that RTS (request to send) is the auxiliary output signal on AUX OUT+ (pin 1) and AUX OUT- (pin 6). Similarly, CTS (clear to send) is the auxiliary input signal on AUX IN+ (pin 5) and AUX IN- (pin 9). This configuration is shown below.

Figure 9. Auxiliary Channel RTS-CTS Handshaking

Auxiliary Channel: Handshaking Disabled.

The DSP-200/300 ports may be configured so that the RTS-CTS handshake is disabled. This is the default configuration. In this configuration, RTS and CTS from the 16C750 UART will be looped back to each other. In addition, the auxiliary output and input signals will be looped back to each other. This configuration is shown below:

Figure 10. Auxiliary Channel Handshaking Disabled

Half Duplex Operation

The DSP-200/300’s ports may be configured for either full duplex or half duplex operation. By default, the RS-422/485 ports are configured for full duplex operation with the RS-422/485 output drivers always enabled.

In half duplex mode, the RS-422/485 transmitter may be enabled and disabled via the RTS (request to send) or DTR (data terminal ready) signals. Both RTS and DTR are controlled through the Modem Control Register of the 16750.

Figure 11. RS-422/485 Driver Enable Options

If RTS is selected as the signal to enable the output drivers, setting 'bit 1' of the Modem Control Register (to logic '1') will enable the output drivers and clearing 'bit 1' of the Modem Control Register (to logic '0') will force the outputs into a high impedance state.

Similarly, if DTR is chosen as the signal to enable the output drivers setting 'bit 0' of the Modem Control Register (to logic '1') will enable the output drivers and clearing 'bit 0' of the Modem Control Register (to logic '0') will force the outputs into a high impedance state.

Selection of half duplex mode operation is dependent upon the configuration software and/or the operating system used. Each of these, however, ultimately control the half duplex mode by accessing the PCMCIA Configuration Register on the DSP-200/300.

Termination Resistors

No termination resistors are provided on the DSP-200/300 ports. Both output and input signals are connected only to the external connector. Any termination which is required must be added externally.

Figure 12. RS-422/485 Termination