Digi 002 Lost connection-Help Please!

[Bantom]

I was working on a session just fine and all of a sudden a warning came up that my 002 had lost connection with PT. I closed down the session and rebooted my CPU and rebooted my 002 and I can't get pro tools to recognize it again. I have been reading about the power harness issue and i don't think it is that as all of the lights still light up and it says Digi 002 in the track windows as normal and I can hit buttons as normal and use the aux feed as normal, I just can't get it to see my session anymore. Any help would be great. I am in the middle of a big project (of course) and I really need my 002 back.

[JazzyJ]

Check cables and firewire ports.

If you have a different firewire buss (a different card etc) then try that.

You haven't put your spec down (as is suggested by the forum) so you limit your chances of help immediately.

Hardware & Software?????

[The Dougfather]

If your suffering from the power harness issue then you physically won't be able to load your sessions because you'll get 'Hardware not found' and theres where it will end.

The 002 may appear fully operational at a glance but it's the ability to establish the firewire connection that is the issue.

Defo check out cables and firewire ports, try another PC/Mac if you can.

[albee1952]

You might also try reseating the harness connectors several times each(to scrape thru the oxidation that builds up on the pins). With the rack, there are 3 connections(and its really simple). With the mixer, there are 4 connections and its more involved due to the location of the PSU(bolted to the bottom pan) and the 4th connection which is sort of hidden under the firewire PCB.

[jhamrick]

On my 003 I once had this issue. During the launch of ProTools I held down the "N" key on the MAC keyboard and chose my interface when prompted to do so. Interface was recognized.

If a resource problem with that one session, open protools and choose new session, in the new session change resource settings to higher buffer. Close the new session and re-try opening the session that was having problems...