A few months ago we established a partnership with ZP Engineering to work on the integration of CopperLan in pro-audio links. We now have a demo platform based on their PicoDM3 Audio interface. We use it to demonstrate how a Firewire-based multichannel audio product can benefit from all CopperLan goodies.

Adding CopperLan to the PicoDM3 was done by ZP Engineering themselves, using our network plugin. This plugin approach allows the developers or proponents of a given connectivity to add CopperLan support to their system all on their own.
This is how standard or custom links can be easily integrated into the CopperLan fused pool of connectivity without having to modify/update the existing CopperLan Virtual Network code that runs on a computer.

By design, CopperLan is versatile enough to conform to any type of link (point-to-point, networked, master/slave) and we do not favor any one over any other.
This is why we continue to look at expanding CopperLan to other transports. The next developments are already under way.
First, we plan a small board that will add CopperLan capability to AES50 products (in this case, based on a ZP Engineering AES50 solution).
Secondly, we follow very closely the Ethernet AVB progresses towards standardization, and we should be able to make some announcement in 2010.

For more info about these specifications: www.aes50ta.org, www.avnu.org