TASCAM FW-1082 not working on brand new MacBook Pro

[blackafrica]

I just got a brand new MacBook Pro running 10.6.6 and it is not being recognized by my TASCAM FW-1082 control surface (or vice versa). The "Firewire" light on the FW-1082 is not lighting up and I can not get the device to interact with my computer at all.

I have downloaded the latest driver for the FW-1082.

The Firewire 400 cable is running out of the FW-1082 to a Firewire 400 --> 800 converter and into the Firewire 800 port on the MacBook Pro.

Is anyone else having this problem? Has anyone found a work-around?

Any ideas will be very much appreciated...

 

[Fishrrman]

"Any ideas will be very much appreciated..."

I don't have a 1082, but just some thoughts...

First, connect the 1082, get everything powered up.

Next, open Apple System Profiler (look in your Utilities folder for "System Profiler")

With System Profiler open, look on the left side under "hardware". You should see "firewire". Click on it one time.

What does it say in the right window?

If it doesn't show any connections at all, it MIGHT be your cables. I'd suggest a firewire "9-to-6-pin" cable from "monoprice.com":
http://www.monoprice.com/products/subdepartment.asp?c_id=102&cp_id=10301

If it DOES show the presence of the 1082 "on the bus", but the 1082 doesn't seem responsive, it MIGHT be the drivers.

Finally, does the 1082 have it's own power supply? Are you using it?

Again, don't have one of these myself, and can only offer some thoughts.

 

[blackafrica]

Next, open Apple System Profiler (look in your Utilities folder for "System Profiler")

With System Profiler open, look on the left side under "hardware". You should see "firewire". Click on it one time.

What does it say in the right window?

The right window reads out:

FireWire Bus:

Maximum Speed: Up to 800 Mb/sec

Unknown Device:

Manufacturer: 0x22E
GUID: 0x22EFFD8593FDB
Maximum Speed: Up to 400 Mb/sec
Connection Speed: Up to 400 Mb/sec
Sub-units:
Unknown Unit:
Unit Software Version: 0x800003
Unit Spec ID: 0x22E


Thanks for the help, Fish

 

[blackafrica]

Problem resolved!

I rebooted my machine in 32 bit (by holding down 3 and 2 during restart) and then ran the firmware updater and it recognized it! Everything seems to work normally now...