Metric Halo Mobile I/O - Manual (Page 332)

332
F. Troubleshooting Guide
COMPUTER DOES NOT SEE MOBILE I/O
If you attach Mobile I/O to your computer, and the computer is unable to communicate with the Mobile I/O
hardware there are five basic possibilities for the source of the problem:
1. The Mobile I/O is not powered up
2. The Software is not installed properly
3. The FireWire bus did not reset correctly
4. The FireWire cable is not connected or bad
5. The FireWire hardware has been damaged
MOBILE I/O IS NOT POWERED UP
The first thing to check is that the Mobile I/O is, in fact, powered up.
If Mobile I/O is powered up and booted properly, the Power, Sample Rate, and Locked front panel indicators
will be illuminated. If these indicators are not illuminated, the Mobile I/O is not powered properly or the unit’s
firmware has been corrupted. If you determine that you are powering Mobile I/O properly and the indicators
are not illuminated, you will need to contact Metric Halo support.
If you are bus powering the Mobile I/O, there is a possibility that you have overloaded the power rating
of the power source. Please see the troubleshooting section “Not enough power on the Bus” for details on
troubleshooting this problem.
If the Mobile I/O is properly powered, then check the next possibility.
SOFTWARE IS NOT INSTALLED PROPERLY
In order for the computer to properly communicate with the Mobile I/O, the various components of the driver
software need to be installed correctly. If the software is not installed correctly, the communication between
the computer and Mobile I/O will fail in various ways. If the MobileIODriver.kext is not properly installed in
the /System/Library/Extensions folder of your computer, you will not be able to use the Mobile I/O for audio
and you will not be able to control the sample rate or clock source of the Mobile I/O with the computer.
• The symptom of this is that the Front Panel FireWire indicator is illuminated, but the Mobile I/O does
not appear as a Sound Output device in the Sound panel of the “System Preferences” application, nor
does it appear in the Apple Audio/MIDI Setup Application.
• To correct this condition, make sure the MobileIODriver.kext file is installed correctly, reboot and then
reconnect the Mobile I/O to the computer. If the software is installed properly, check the next possibility.
THE FIREWIRE BUS DID NOT RESET CORRECTLY
When a device is plugged into the FireWire bus, a FireWire bus reset occurs automatically. The bus reset
interrupts bus activity and reconfigures the bus so that all devices on the bus become aware of all the other
devices on the bus. Sometimes the reset does not complete successfully, and the bus becomes partially hung.
In this case, the “FireWire” indicator on the front panel of the Mobile I/O will not be illuminated. When the
“FireWire” indicator on the front panel is not illuminated, the Mobile I/O cannot transport audio over the
FireWire bus.
Generally, this condition can be fixed by disconnecting the Mobile I/O from the bus and reconnecting it.
If the disconnect/reconnect cycle does not fix the problem, another device on the bus may be interfering with
the proper operation of the bus. If you have other devices on the bus, try disconnecting them from the bus
and only using the Mobile I/O.