About XDAB Question

Zhangye,

You may also want to take a look at the full section on this located in  the Nion Hardware manager online manual
go Here: http://www.peaveyoxford.com/kc/
Then navigate to here:
NION Hardware Manual » Using XDAB clusters with VLANs and CobraNet

Where you put your conductors and XDAB masters will be a function of the audio and clock paths. i.e which devices in which VLANs must exchange audio data and how the CobraNet clock is propagated.
As a rule, you can't have a NION in an XDAB cluster that is a performer in a VLAN who's CobraNet conductor does not derive its audio clock from the XDAB master in the cluster.
The clock source can be one or twice removed but it is important to insure that everything is synced up properly. It can be a little confusing if the basic concept is not understood.
Again, take a look at the "Using XDAB clusters with VLANs and CobraNet" in the Hardware manual and make sure you understand the concept of following the clock paths to inure there is no clock contention between the XDAB cluster clock domain and the CobraNet VLAN clock domains.

Zhangye, I assume you are referring to the last example "Follow The Clock – A Bad Example"

The NION marked (1) is the XDAB master for the cluster. But it is a performer in VLAN 1.
The NION  marked (2) is the clock source for the CobraNet network in VLAN 1. But it is a slave in the XDAB cluster.
So NION 2 is supplying the audo clock to all CobraNet devices in its VLAN segment, including NION 1 which is the XDAB master.
So there is a clock circle with no clear audio clock source.
NION 2 is getting its audio clock from NION 1 via XDAB, which is getting its clock from NION 2 via CobraNet which is getting its clock from NION 1 via XDAB which is getting its clock from NION 2 via Cobranet and on and on an on in a circle with no definitive clock source.

If the NION (1) were changed to be both the Conductor and the Master then this would work.  Even better would be to put the conductor in a device outside of the cluster that itself is not in a cluster, i.e. a single device.

Eureka! You have got it!

The point is to get the clock to travel through the system from one single point that is the master of the whole system. This master should not be influenced by an outside source. So, in one cluster, there is an XDAB Master AND all the CobraNet Conductors for each CobraNet VLAN. The other clusters will still have an XDAB Master since there must be a Master for each XDAB stack, but they will ALL be performers on the CobraNet network.

Nope