M-Audio Biport 2x4s [44/48] Interface trouble shooting

Trouble-Shooting

If you are having problems using your BiPort 2x4s, it is probably a good

idea to re-read this manual and make sure you have properly installed

the interface. If you can’t find the source of your difficulty then check the

following typical fixes:

Interface Trouble-Shooting

SYMPTOM: The diagnostic program’s Internal Hardware Test reports

“FAIL — Interface Not Found.”

SOLUTION 1: The Serial Port, IRQ and/or Address settings in the

diagnostic program probably do not match the actual IRQ and Address

setting of your serial port. Set them to the correct value(s).

SOLUTION 2: Make sure the BiPort is properly connected to your

computer, and to the proper COM/Serial port. If your PC COM port is

conflicting with your modem, try the other COM port. For Macs, the

modem port is more desirable than the printer port.

SYMPTOM: The diagnostic program’s Transmit/Receive Test fails.

SOLUTION: Either you forgot to install the MIDI loopback cable, or

the ports you’ve physically looped-back have not been properly speci-

fied in the diagnostic program. This test transmits MIDI data out one

port and then verifies that it can be properly read into another.

SYMPTOM: The diagnostic program’s SMPTE I/O Test fails.

SOLUTION: You may have forgotten to connect the board’s SMPTE In

connector to the SMPTE Out connector using a 1/4” phone cable. This

test uses the cable to write SMPTE back into the unit and verify that it

can be properly read.

SYMPTOM: The diagnostic program passes all tests except for the

“Receive Interrupt” test.

SOLUTION: The IRQ setting in the diagnostic program probably does

not match the IRQ setting of your serial port. Make sure they are set to

the same value. If this does not alleviate the problem then your port is

probably using another IRQ than you think it is, or you have another

peripheral using the same IRQ (See the Installation and Diagnostics sec-

tions).

SYMPTOM: My computer can’t find the interface when I run my

sequencer program.

SOLUTION 1: You don’t have the Windows driver properly installed,