Help with FireWire Drivers Audio Interface

[herman_hdz]

OK Darryl than you

Additional question:

I ran :$ ioreg -c IOFireWireController -r <show up>
+-o IOFireWireController <class IOFireWireController, id 0x100000233, registered, matched, active, busy 0 (24 ms), retain 31>
| {
| "FireWire Self IDs" = <807fc856>
| "IOPowerManagement" = {"DriverPowerState"=1,"MaxPowerState"=2,"CurrentPo werState"=1}
| "FireWire Generation ID" = "1"
| }
|
+-o IOFireWireLocalNode <class IOFireWireLocalNode, id 0x100000296, registered, matched, active, busy 0 (24 ms), retain 34>
+-o IOFireWireUserClientIniter <class IOFireWireUserClientIniter, id 0x100000297, !registered, !matched, active, busy 0, retain 25>
+-o IOFireWireUserClientIniter <class IOFireWireUserClientIniter, id 0x100000310, !registered, !matched, active, busy 0, retain 25>
+-o IOFireWireIP <class IOFireWireIP, id 0x100000311, registered, matched, active, busy 0 (0 ms), retain 28>
+-o fw0 <class IOFWInterface, id 0x100000313, registered, matched, active, busy 0 (0 ms), retain 31>
+-o IONetworkStack <class IONetworkStack, id 0x100000298, registered, matched, active, busy 0 (0 ms), retain 33>
+-o IONetworkStackUserClient <class IONetworkStackUserClient, id 0x1000002b1, !registered, !matched, active, busy 0, retain 26>

so what is the difference if a ran $ ioreg -c IOFireWireDevice -r ??

[herman_hdz]

OK Darryl than you

Additional question:

I ran :$ ioreg -c IOFireWireController -r <show up>
+-o IOFireWireController <class IOFireWireController, id 0x100000233, registered, matched, active, busy 0 (24 ms), retain 31>
| {
| "FireWire Self IDs" = <807fc856>
| "IOPowerManagement" = {"DriverPowerState"=1,"MaxPowerState"=2,"Curren tPo werState"=1}
| "FireWire Generation ID" = "1"
| }
|
+-o IOFireWireLocalNode <class IOFireWireLocalNode, id 0x100000296, registered, matched, active, busy 0 (24 ms), retain 34>
+-o IOFireWireUserClientIniter <class IOFireWireUserClientIniter, id 0x100000297, !registered, !matched, active, busy 0, retain 25>
+-o IOFireWireUserClientIniter <class IOFireWireUserClientIniter, id 0x100000310, !registered, !matched, active, busy 0, retain 25>
+-o IOFireWireIP <class IOFireWireIP, id 0x100000311, registered, matched, active, busy 0 (0 ms), retain 28>
+-o fw0 <class IOFWInterface, id 0x100000313, registered, matched, active, busy 0 (0 ms), retain 31>
+-o IONetworkStack <class IONetworkStack, id 0x100000298, registered, matched, active, busy 0 (0 ms), retain 33>
+-o IONetworkStackUserClient <class IONetworkStackUserClient, id 0x1000002b1, !registered, !matched, active, busy 0, retain 26>

so what is the difference if a ran $ ioreg -c IOFireWireDevice -r ??

[Darryl Ramm]

Originally Posted by herman_hdz

OK Darryl than you

Additional question:

I ran :$ ioreg -c IOFireWireController -r <show up>
+-o IOFireWireController <class IOFireWireController, id 0x100000233, registered, matched, active, busy 0 (24 ms), retain 31>
| {
| "FireWire Self IDs" = <807fc856>
| "IOPowerManagement" = {"DriverPowerState"=1,"MaxPowerState"=2,"CurrentPo werState"=1}
| "FireWire Generation ID" = "1"
| }
|
+-o IOFireWireLocalNode <class IOFireWireLocalNode, id 0x100000296, registered, matched, active, busy 0 (24 ms), retain 34>
+-o IOFireWireUserClientIniter <class IOFireWireUserClientIniter, id 0x100000297, !registered, !matched, active, busy 0, retain 25>
+-o IOFireWireUserClientIniter <class IOFireWireUserClientIniter, id 0x100000310, !registered, !matched, active, busy 0, retain 25>
+-o IOFireWireIP <class IOFireWireIP, id 0x100000311, registered, matched, active, busy 0 (0 ms), retain 28>
+-o fw0 <class IOFWInterface, id 0x100000313, registered, matched, active, busy 0 (0 ms), retain 31>
+-o IONetworkStack <class IONetworkStack, id 0x100000298, registered, matched, active, busy 0 (0 ms), retain 33>
+-o IONetworkStackUserClient <class IONetworkStackUserClient, id 0x1000002b1, !registered, !matched, active, busy 0, retain 26>

so what is the difference if a ran $ ioreg -c IOFireWireDevice -r ??

This has just detected that there is a Firewire controller present, or thought to be present by OS X. The things plugged into the Firewire bus are Devices not Controllers. This really does not really prove that the Firewire bus or even its controller is working properly. And all the !registered, !matched thingies are normal anyhow.

Darryl

[Darryl Ramm]

BTW in all these tests i just want to make sure you are using the same known to work power supply connected to the Mbox Pro and the Mbox Pro front panel LEDs light up properly when you are connecting to the iMac.

Darryl

[rickymix]

After beating my head against the wall for a week with 6085 errors I finally discovered that the MBox Pro gen3 is NOT FW800 compatible! FW400 works fine. Also the FW ports on the back of the MBox provide no FW power, you need a drive plugged into the wall. Not sure if that helps your situation, but you mentioned FW800.

[Darryl Ramm]

Originally Posted by rickymix

After beating my head against the wall for a week with 6085 errors I finally discovered that the MBox Pro gen3 is NOT FW800 compatible! FW400 works fine. Also the FW ports on the back of the MBox provide no FW power, you need a drive plugged into the wall. Not sure if that helps your situation, but you mentioned FW800.

Many people are running the Pro with a FW800 to FW400 adapter. If you tried an adapter or adapter cable you might want to try a different one/brand. Sonnet make one that is well regarded. Things also get more complicated if you are chaining devices, were you?

Darryl

[rickymix]

Thanks Darryl. My MacBook laptop only has 1 FW(800) port, forcing me to daisy-chain.
So I went to Apple and bought a Thunderbolt-to-FW800 connector, and set up my rig with the FW800 (5400-RPM) external G-drive connected through the laptop's Thunderbolt port and the MBox-Pro3 connected through the laptop's FW800 port via a FW800 > FW400 adapter.
My ProTools is running rock-solid now! If I run into problems in the future due to heavier track counts/VI's/Plugs etc, I'll upgrade to a 7200-RPM external hard-drive, but for now I'm up and running without a glitch.
I only wish that AVID would make this info much more obvious in the basic FAQs on the MBox-3 line; particularly that the MBox-3s are FW400 ONLY and will NOT run properly on the same FW buss as a FW800 device. Also that there is no FW-buss power coming out of the FW400 ports on the back of the MBox units. Hard-drives daisy-chained there MUST have their own DC power supply.

[Darryl Ramm]

The Mbox 3 Pro are *not* Firewire 400 only, many users are using them fine with Firewire 800 to 400 adapters or adapter cables. You may have had problems but we have no information about what specific cables/adapters you have tried, or what chaining orders and with what specific FW800 disk drives, or even what system you are on. All that information might describe one specific configuration that does not work.