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

Troubleshooting Guide
333
If removing other devices from the bus solves the problem, it is likely that there is a problem with either one of
the devices you removed or with one of the cables connecting the devices. You’ll need to isolate the problem
component.
If removing the other devices from the bus does not fix the problem, check the next possibility.
THE FIREWIRE CABLE IS NOT CONNECTED OR BAD
Check the simple thing first; is the unit connected? If the FireWire status LED on the front panel is not on
and/or there is no information listed in the Box Info pane in MIO Console, confirm that the FireWire cable
is plugged in firmly at both ends.
Metric Halo provides two high-quality overspec’ed FireWire cables for use with Mobile I/O and we recommend
you use them. For various reasons you may decide to use other cables than the ones provided by Metric Halo.
Under ideal circumstances all FireWire cables will provide years of service. However, cables will and do go
bad. Cable failures can be difficult to track down. If you are experiencing problems with connecting or bus
powering Mobile I/O you should try swapping the cable with another known-good cable.
If the FireWire cable is not the source of the problem, check the next possibility.
THE FIREWIRE HARDWARE HAS BEEN DAMAGED
If all else fails, it may be that the FireWire hardware on either the Mobile I/O or the computer has been
damaged. While this is an exceptionally rare occurrence, it is a possibility. The FireWire hardware can be
damaged in the following ways:
1. If you insert a FireWire cable into a port upside down, it will damage the FireWire port and/or the
connector. It is difficult to insert the connector upside down, but it is possible to force it. Never force
a FireWire connector!
2. It requires significant pressure, but it is possible to force a FireWire connector over a male XLR connector
pin. If you do this, the connector will be shorted and it will destroy the port on the other end. Again,
never force a FireWire connector.
3. Some devices that are bus-powerable and conform to the IEEE1394 standard will return power to the
remote FireWire port if a power ground fault occurs. If the remote port is protected against this situation,
nothing will happen. If the device does not use bus power, nothing will happen. But, if the device is
fully compliant, uses bus power, and the remote device is not protected and supplies a high enough
voltage on the bus, the remote device port will self-destruct.
If the FireWire hardware on the computer has been damaged, it will not communicate with any FireWire
devices. Be sure that you are not checking this case with a bad cable, as a bad cable can make it seem like the
FireWire hardware has failed since it will consistently keep devices from connecting properly to the computer.
If the computer is damaged, you will need to contact the manufacturer for a repair or, as a stopgap measure, you
can use a third-party FireWire adapter card. Metric Halo also recommends the use of a third party FireWire hub
between the computer and any FireWire devices. Any potential issues will damage the hub, not the computer,
saving time and money in the long run.
If the FireWire hardware on the Mobile I/O has been damaged the MIO will not communicate with any other
devices. In this case, please contact Metric Halo support for help in getting your Mobile I/O hardware repaired.
NO OUTPUT FROM MOBILE I/O
If the output meters of your interface show activity but you hear no audio, you can reset the outputs of a single
box or all connected boxes from MIO Console's Utilities menu: