Attaching a 888 to legacy

[murray656]

So I'm not sure what I'm doing wrong, so thought I'd ask if the chain is correct.

I'm trying to connect a 888/24 to a 192, and not getting any kind of indication that the 888/24 is receiving signal.

I have a 192 connected to 888/24 via the legacy port. Single connection cable (not Y cable). Clock BNC cable from 192 Out to 888/24 In, 888/24 Out to 192 In.

In Hardware, I set the peripheral #1 for the 192 to be a 888/24. In I/O I assigned outputs 9 - 16 to the 888/24.

ISSUE: I don't see any signal in the 888/24. No output in channels 9 - 16.

TRIED: Reconnecting everything. Checked cable connections on 888/24 and 192.

Any ideas what the issue is?

Murray

[crizdee]

could run digi test and see if a firmware upgrade is needed!
Thats all i can think of, if all the cables are ok which they seem to be as its showing in the hardware setup.

[murray656]

Yeah, ran a digi test as well. Everything was updated.

When you say "they seem to be showing in the hardware setup", what does that mean?

Thanks
M

[murray656]

Is there a way the legacy port may have died or I may have messed something up?

The strange thing is, when in hardware setup, when you click "identify", I KNOW I saw the 888/24 light up when highlighted in the peripheral section. Now it doesn't do anything.

When I run the DigiTest, at the very end of the result, it shows that a secondary peripheral is found, so I'm guessing that's the 888/24. I've seen a couple recent posts about the legacy port not working on 8, and a specific boot up sequence, could this be my issue??

Would bad BNC cables have anything to do with this? Any help from you folks running 888/24's this way would be GREATLY appreciated.

Thanks!!
Murray

[s.d. finley]

Use the loop sync out of the 192 into the sync in the 888. Not the WC out from 192. 192 is the loop master. This worked for me when I had a digital 192 and adat bridge.

[JFreak]

Originally Posted by s.d. finley

Use the loop sync out of the 192 into the sync in the 888. Not the WC out from 192. 192 is the loop master. This worked for me when I had a digital 192 and adat bridge.

NO!

Loop sync delivers the regular 1x clock that is needed for the current HD hardware. Whenever you set up a legacy device, the WC output changes to TDIF mode (256x sync) which is what the legacy interfaces require. So be sure to use the WC output to 888|24 input, AND be sure that you DO NOT loop it back to 192 WC input. This clock must not be looped back.

There's also something strange in the powering up order. If you power up HD interface first and legacy interface last, it will not work. But if you power up the legacy interface first and wait until it's fully booted, and only then power up the new stuff, then it will magically start working.

[murray656]

Thanks JFreak,

So in that configuration, you have to use the internal clock? I was hooked up to a Big Ben, but that requires a full loop or it gets messed up.

Just to be sure, you are saying that the OUT on the 888/24 does not connect to anything?

[Craig F]

Originally Posted by murray656

Thanks JFreak,

So in that configuration, you have to use the internal clock? I was hooked up to a Big Ben, but that requires a full loop or it gets messed up.

Just to be sure, you are saying that the OUT on the 888/24 does not connect to anything?

only a second 888 if you have one

[murray656]

So there is no way to hook up the Big Ben into the mix when using a 888/24?

[John_Toolbox]

Not familiar with the Big Ben, but I believe that it will output both regular 1x wordclock and the 256x superclock that the 888 needs. So rather than clock the 888 from the 192, why not connect the 888 directly to the big ben. Then you can loop back the output of the 192. Both interfaces will now be slaved to the same clock source (the big ben), so this should be fine.