003 Console Problems

[philip888]

Windows 7 64 Bit Latest drivers.

I am using the firewire connection on my Giga board. Had a 003 R and never had issues.

The 003 does not lose connectivity. But it forgets where it is.

I will use the Zoom button to zoom no problem. Then come back to zoom and it starts nudging. It gets stuck on nudge Even when Bank is selected.

Have not had the thing long enough to describe more of what does not seem write.

Would having a firewire card help this?

I notice also that when this behavior starts that I loose keyboard functionality.

Is this caused by a CRAPPY driver or is it my system?

Any help and or suggestions would be greatly appreciated.

Philip

[philip888]

Can anyone shed any light on this behavior?

Anyone experienced with the 003 Console?

[albee1952]

Running a similar setup here without issues(also with the on-board FW). It may be worth trying another FW driver. There are 3 resident drivers. Go to Device Manager and select the FW card, then choose Update Driver>Browse my computer>Let me choose from a list. Of the 3 choices, the one working here is the TI Compliant driver.

[philip888]

Originally Posted by albee1952

Running a similar setup here without issues(also with the on-board FW). It may be worth trying another FW driver. There are 3 resident drivers. Go to Device Manager and select the FW card, then choose Update Driver>Browse my computer>Let me choose from a list. Of the 3 choices, the one working here is the TI Compliant driver.

Ok buddy I will give it a shot thanks.

Do I change the driver while the 003 is on and conected?

[sunburst79]

Originally Posted by philip888

Ok buddy I will give it a shot thanks.

Do I change the driver while the 003 is on and conected?

I never had a problem changing it while on. I would think at worst you would see the windows New Hardware wizard run and may have to reboot. My recollection is that it simply switches drivers. Last time I messed with the driver was when I updated to PT9 the first time.

Losing the keyboard has me raising a eyebrow as its unlikely related to a FireWire issue since its USB or PS2. Next time it happens you might want to check the Device Manager window and see if its unloaded any of the device drivers. You also should make sure that you've disabled USB power saving on your USB root ports in Device Manager.

Have you installed any new hardware or moved and device connections that might be causing a IRQ error?

[albee1952]

Should be fine with it connected. I can't even remember the last time I disconnected(and NEVER EVER do this with things powered ON). Hot-patching FW with 002 or 003 can fry the FW circuit in the unit, the post in the computer or even both!!!(yes, I learned the hard way)

[philip888]

I Swapped the driver updated to the latest firmware.

Things were going ok but then I got the Blue Screen of Death. Rebooted The the session locked up again. The 003 lock up. It is very strange.

The firewire cable I have is a 13 and 1/2 feet. I bought it from OWC great company.

Am I supposed to have the straight Digi firewire cable? Is there a difference?
It seems like the 003 is falling asleep at the wheel and will not wake up.

I have no significant hardware changes from when I used the 003r.

Thanks for giving me some suggestions.

[sunburst79]

Originally Posted by philip888

I Swapped the driver updated to the latest firmware.

Things were going ok but then I got the Blue Screen of Death. Rebooted The the session locked up again. The 003 lock up. It is very strange.

The firewire cable I have is a 13 and 1/2 feet. I bought it from OWC great company.

Am I supposed to have the straight Digi firewire cable? Is there a difference?
It seems like the 003 is falling asleep at the wheel and will not wake up.

I have no significant hardware changes from when I used the 003r.

Thanks for giving me some suggestions.

Maybe try another cable? I'm fairly sure the standard FW400 cable length is 3 meters. Or just over 15foot. Its possible that your cable being near the limit is aggravating an issue. Remember the unit is not hot swappable. What's the FW LED doing during all this? Any DAE errors warning about connectivity being lost. If the unit was truly losing the FW connection for any length of time I would expect the see DAE errors.

Could this be something as simple gunked up or sticky control or switch on the 003?

[albee1952]

The only FW cable that ever failed on me was the one that came with my 002! 14.5' is the maximum length and I have a pair of those that have never been a problem. What version of PT are you running? If its 9 or 10, be aware that the driver for the rack version(002/003) is different than the driver for the controller version

[philip888]

Originally Posted by albee1952

The only FW cable that ever failed on me was the one that came with my 002! 14.5' is the maximum length and I have a pair of those that have never been a problem. What version of PT are you running? If its 9 or 10, be aware that the driver for the rack version(002/003) is different than the driver for the controller version

Thanks Jason. Yea I am running the correct console driver. I am on PT 10.3.4.

I am trying a different Firewire cable at the moment.

I did a complete uninstall and reinstall this morning.

No lock ups yet with the different cable but things don't seem right.

For instance If I select a clip or (region) and select Nudge in Transport Modes then push the the transport arrows it selects each track instead of nudging the clip.

The unit is very clean this is not being caused by dirty contacts.

I may not have something set correctly I don't know.

Just got the thing.