Moxa CP-132S [42/45] General troubleshooting

CP-132 Series Troubleshooting

6-2

General Troubleshooting

1. The MOXA PCI board cannot be detected by the MOXA driver while installing the driver.

Hardware causes and solutions:

a. The board is not installed or missing (absent). Please install it.

b. The board is not properly plugged in the system. If that is the case, re-plug the board in a 32-bit PCI slot

this time. Sometimes the slot for plugging the board is malfunctioned. In this case, try other slots until

you find a good one.

c. The motherboard does not have an available IRQ for the CP-132 Series board. Please enter BIOS and

make sure there are available IRQ in PCI/PnP settings.

2. The MOXA board and driver are activated but cannot transfer (transmitting/receiving) data.

Hardware Causes and Solutions:

a. Check if cable wiring is connected correctly. Please refer to the “Connection Cable and Cable Wiring”

chapter for correct cable connection.

b. The cable or the board are probably defective. Please try other ports, cables or boards to verify it. Or use

PComm Diagnostic utility testing MOXA boards and port conditions. If Diagnostic reports error, replace

the malfunctioned faulty components.

Software Causes and Solutions:

a. Smartio CP-132 Series board will check the line status (CTS) before transmitting data if the RTS/CTS

flow control feature is set to Enable in the configuration or application program. Please refer to the

Connection Cable and Cable Wiring chapter for proper wiring and check the line status of the suspected

port using the diagnostic LED indicators on the mini tester.

b. The board controlling application might not be correctly written according to the corresponding API of

the operating system. To verify the problem, please run another existing and known good application or

the utilities provided by Moxa. Such as Pcomm Terminal emulator or HyperTerminal under Windows NT

and Windows 95/98.

Windows NT

This section is specific for troubleshooting under Windows NT. For general problems and solutions, please see

the previous section, “General Troubleshooting”.

1. After the system reboots, the error message “Another driver in the system, which did not report

its resources, has already claimed the interrupt used by xxx.” appears in the Event Log.

This indicates the MOXA board is found, but the IRQ is conflicting with another adapter. Please check the

PCI BIOS IRQ settings first and then select an IRQ that is available.

2. After the system reboots, the error message “Cannot find any configured MOXA

Smartio/Industio Series board!” appears in the Event Log.

Please make sure the PCI board is seated firmly in the expansion slot.

3. The COM number of the Industio CP-132 Series conflicts with others.

The COM numbers of different boards happen to be the same. Try to change the COM number mappings.

4. Windows NT system panic (blue screen).

The possible reason is an IRQ or memory conflict with other ISA Bus adapters, like LAN and SCSI boards,

or the system BIOS. Please refer to the corresponding problem in the previous section, “General

Troubleshooting”, for solutions.