Answer:

• PC running Windows 2000/XP Professional with a 10/100baseT network card(NIC)
• Audia units
• Audia software
• 10/100baseT Ethernet switch with sufficient ports for both Ethernet(control) and CobraNet (audio) connections
• Enough Cat5 “straight-through” Ethernet cables for both Ethernet connections and CobraNet connections to all devices.

Answer:

• Windows NT/2000/XP Pentium II 300MHz or faster PC with at least 64MB RAM and a 10/100baseT network card(NIC)
• Audia unit
• Audia software
• Cat5 “cross-over” Ethernet cable (supplied with unit)

Answer: Cat5 Ethernet cables can be used for a maximum of 100 meters between any two Ethernet devices. Ethernet switches are also available with fiber optic ports which can extend the distance up to 2 km using multimode fiber, or even longer using single mode fiber.

Answer: When connecting a PC to an Audia unit, a “cross-over” Cat5 Ethernet cable is used. “Cross-over” Ethernet cables have their pins swapped (pin 1 to pin 3, pin 2 to pin 6, pin 3 to pin 1). You can easily identify these by looking at the RJ-45 connectors. If the wiring is different at each end, it is a "cross-over" cable.

Answer: When connecting a PC and Audia in a networked system, “straight-through” Cat5 Ethernet cables are used to connect from PC to Ethernet switch port and from Audia unit to Ethernet switch port. “Straight-through” Ethernet cables are wired pin to pin. You can easily identify these by looking at the RJ-45 connectors. If the wiring is identical on both ends, you have a “straight-through” cable.

Answer:

For Windows XP Professional users:

Using Category View:

1. Click on the Start button, and then click on Control Panel.
2. In Control Panel, under Pick a Category, click on Network and Internet Connections.
3. Under or pick a Control Panel icon, click on Network Connections.
4. Under LAN or High-Speed Internet, right-click on your network connection; and then click Properties.
5. In the This connection uses the following items box, click on Internet Protocol (TCP/IP) and then click on Properties.
6. Select Use the following IP address and enter the required IP address and subnet mask.
7. Click on OK. In the Local Area Connection Properties dialog box, click on OK.

1. Click on the Start button, and then click on Control Panel.
2. Double-click on Network Connections. The Network Connections window opens.
3. Under LAN or High-Speed Internet, right-click your network connection; and then click on Properties.
4. In the This connection uses the following items box, click on Internet Protocol (TCP/IP) and then click on Properties.
5. Select Use the following IP address and enter the required IP address and subnet mask.
6. Click on OK. In the Local Area Connection Properties dialog box, click OK.

1. Click on the Start button, click on Settings, and then click on Control Panel.
2. In Control Panel, double-click Network and Dial-up Connections.
3. Right-click on your local area connection; and then click on Properties.
4. In the Components checked are used by this connection box, click on Internet Protocol (TCP/IP), and then click on Properties.
5. Select Use the following IP address and enter the required IP address and subnet mask.
6. Click OK. In the Local Area Connection Properties dialog box, click OK.
7. Close the Network and Dial-up Connections window.

1. Open Network Connections by clicking the Start button, clicking Control Panel, clicking Network and Internet, clicking Network and Sharing Center, and then clicking Manage network connections.
2. Right-click the connection that you want to change, and then click Properties.
3. Click the Networking tab. Under This connection uses the following items, click on Internet Protocol Version 4 (TCP/IPv4).
4. Click Use the following IP address and enter the required IP address and subnet mask.
5. Click OK. In the Local Area Connection Properties dialog box, click OK.
6. Close the Network Connections window.

Answer:

Within Audia software and connected to the Network:

1. From the top menu, select File, choose Network, and select Perform Audia Device Maintenance.
2. Click to select desired Audia device from Device List.
3. Click on Set IP Address.
4. Click Yes to proceed at the dialog prompt warning that audio will be stopped.
5. Enter desired IP address and subnet mask. Enter Default Gateway if required.
6. Click OK to close Set IP address dialog and to acknowledge the changes.
7. Click OK to allow device to restart.
8. Close the Device Maintenance window.

Answer: No. Each device in a system including PC and Audia units must have a unique IP address.

Answer: As long as each device on the network has a unique IP address, any PC running the Audia software can connect to, control, and monitor an Audia system from any location on the network. This can be useful in a large building with several meeting rooms throughout, each with a dedicated Audia system. A central AV control room can connect to any room to make changes, adjust levels, etc. In fact, both Audia software and daVinci control software allow multiple PCs to connect to the same Audia system at once, with control and status information being mirrored between all PCs.

Answer: No. Audia can be on networks with different subnets. Audia does ship from the factory with an IP address of 192.168.1.101 though. That means any PC connecting to Audia for the first time must have an IP address with a subnet of 192.168.1. Once connected, you can then change the IP address of Audia. You will then need to change the IP address of your PC to be on the same subnet that Audia is.

Answer: Biamp does not recommend specific brands or models of Ethernet switches. The only requirement is that a 10/100BaseT Ethernet switch be used.

Answer: An Audia outputs its IP settings (and other helpful information) through the serial port when it boots up. Establish a serial connection by connecting your PC com port to the Audia serial port using a straight through serial cable. Open a terminal emulator such as Hyper Terminal on your PC, and enter the correct communication settings. Next, power-cycle the Audia and the IP settings will be displayed on the Terminal Emulator window upon boot-up.

Answer: Connect to your Audia via serial or Telnet, and send the command “GET X MACADDRESS” (without quotes), where X is the Device ID of your unit. The unit will respond with its MAC address. If connecting via serial to a single unit system, you may replace X with a 0.

Answer:

Latency depends entirely upon the amount and signal flow of DSP being used as well as number of CobraNet hops. Originally, each CobraNet hop added 5⅓ msec latency. Audia now supports lower latency CobraNet. Depending on your setting, CobraNet latency can be set to either 5⅓, 2⅔, or 1⅓ msec per CobraNet hop (see CobraNet section below for more details.) Latency through a single Audia unit with nothing more than a straight path between input (A/D) and output (D/A) will be around 2.67 msec. Each DSP block a signal travels through will add approximately ⅓ msec latency. During compilation, Audia will calculate the longest latency through the system and automatically apply delay to any shorter audio paths so that all audio outputs synchronized. This feature can be disabled by going to Tools, selecting Options, selecting the Compile tab and deselecting both Global and Local Delay Equalization options.

Answer:

Once an Audia layout (.dap) has been compiled and the configuration uploaded to the desired device(s), the only changes that can take place in real time are adjustments of object parameters. Any changes to the layout must take place offline, be compiled, and then uploaded to the Audia device.

Answer: The largest matrix than can be configured is 40x40.

Answer:

No. Audia can handle multi-channel audio, but it does not currently have a surround sound decoding/encoding feature.

Answer:

Each AudiaFLEX is capable of delivering a maximum of 120 watts. When adding Power Amplifier blocks to the Layout, we’re able to select the output power for each amplifier channel. Available settings are 5, 10, 20 and 30 watts per channel; or 10, 20, 40 and 60 watts per PA-2 card if using the Mono-bridged option.

Answer:

Each Audia unit has 50 seconds of memory allocated for delay purposes. That delay memory can be allocated in any combination of delays throughout the system layout as long as the 50 seconds in not exceeded. Also, be aware that each input channel of a matrix mixer with delay consumes 1 second of delay and will contribute to the 50 seconds total of maximum delay in a single Audia unit.

Answer:

A great way to design a large matrix like a 32x200 is with the use of CobraNet input and output blocks.

Step 1:
Create a drawing with 32 (4 8-input blocks) analog input channels. Route those input channels directly to 4 CobraNet output blocks. Assign Each CobraNet output block to a separate multicast bundle number. Next, route each analog input channel to a 32x32 matrix mixer. Then take the outputs of the matrix to 32 analog (4 8-output blocks) outputs.

Step 2:
Drop down 4 CobraNet input blocks onto the drawing. These input blocks will be assigned the same multicast bundle numbers of the CobraNet output blocks. Run each CobraNet channel to a 32x32 matrix mixer. Then take each matrix mixer output and run to 32 analog (4 8-output blocks) outputs.

Continue repeating step 2 until you have the number of outputs you need.

Because we're using multicast CobraNet bundles, we distribute all 32 audio channels to the inputs of each matrix. Now we can assign each matrix cross point as needed to route audio to each output channel.

Answer:

Yes, providing the Audia system isn’t password protected, or that you know the pertinent password. A copy of the Layout file is stored by the system, and is downloaded to your computer upon connection.

Answer:

Audia has 4 password levels:

Designer level allows access to system layout and configuration, component setting, storing/recalling presets, and password assignments.
Technician level allows access to component setting and storing/recalling presets.
User level allows recall of presets. Level control and meter dialogs can be minimized for user level access as well.
Guest level allows access to layout viewing only.

To create passwords, you must be connected to a system.
From the top menu, choose Tools and then select Passwords. Click on Set to enter desired passwords, and click OK when done.

The next time someone attempts to connect to the system, they will be prompted to enter a password before allowed to connect.

Answer:

When doing a teleconference or video-conference, it's necessary to create a mix minus. A mix minus allows us to send all audio minus the incoming telephone/video conference audio to the hybrid or CODEC input. By creating a mix minus, we reduce feedback loops as well as echoes that are inherent with Telco system delays.

Choose an auto mixer and enable the direct outputs. You will also need to use a standard mixer as well. Route all audio including incoming telephone/video conference audio to the auto mixer inputs. Next, route all audio except the telephone/video conference audio from the auto mixer direct outputs to the standard mixer inputs. The auto mixer main output will route to an output for local audio distribution. This will include all audio sources including the telephone/video conference audio. The output of the standard mixer will route to the input of the hybrid or CODEC. This feed will include all audio sources minus the incoming telephone/video conference audio.

What’s more, by using a Matrix mixer rather than a Standard mixer block, we will be able to create several independent Mix-minus mixes, to feed a multi-channel reinforcement system for instance.

Answer:

An Auto mixer’s direct output presents the signal directly from its relative input, not mixed with the other auto mixer inputs.
The signal at the direct output can be post gate-pre NOM, or post gate-post NOM. This option can be selected on a per channel basis from the Channel Settings control dialog, which is accessed through the auto mixer’s control dialog, right-clicking on the cross point button, and selecting Edit Channel Setting.

Answer:

The Mix Minus combiner allows the control data of multiple independent auto mixers to be combined. Control data includes NOM Attenuation and ATS (Adaptive Threshold Sensing) information. Please note that the maximum number of open mics information is not shared and remains unique to each auto mixer.
By connecting the mix output of different auto mixers into the Mix Minus Combiner, and selecting these signals into the same Mix Minus Combiner group, we can create larger auto mixers from multiple smaller ones. This is useful in Mix Minus situations, or when auto mixers must be placed into multiple Audia devices.

Answer:

The maximum number of open mics must be set on a per mixer basis, as that data is not shared between the auto mixers.

Answer: No. The threshold is determined automatically and dynamically by the Adaptive Threshold Sensing (ATS) method. Please refer to the July 07 Tech Newsletter for more details, available at http://www.biamp.com/tech_news.php

Answer:

Within Audia software:
From the main menu, choose Tools, then choose Options and select the Display tab
Under DSP Block Information Field select Display device assignment

The device number will then be displayed on each DSP block.

Answer: For this application, we will typically use a Ducker block. Simply connect your music source to the Ducker’s normal input, and the Paging Mic source to the Sense input (identified by an S). Once the signal connected to the Sense input reaches the threshold, the music will be attenuated by the amount set in the Ducking level field (40dB by default). Please note that if we want to have the Sense signal present at the output of the Ducker, we must enable the Mix Sense button.

Answer:

Custom blocks allow the placement of several DSP blocks and associated signal flow into a single common block. This allows to keep the layout looking neater, to save large portions of a layout for later access, or to keep certain portions of the layout out of view or private from other users.

To create a Custom Block:

1. From the main menu, select Custom Blocks and click on Create Custom Block document. The Create custom DSP block window will appear
2. Select the required number of audio and logic I/O needed in the new custom block. Click on OK when done, and a new Layout page will open. This is the custom block document.
3. Blocks labeled APT (audio pass through) and LPT (logic pass through) will be displayed. These are the audio and logic I/O through your custom block selected in the previous dialog
4. Drag and drop objects into you custom block or copy and paste items from an existing DAP file as required. Make all necessary interconnections for the desired signal flow.
5. When done, go to Custom Blocks, and click on Merge into Custom Block. All components in the custom block layout will then be merged into a single block. This can now be imported and placed into a DAP file.

Once a Custom Block has been placed into a DAP file, you can open it to view what’s inside and adjust any of the component parameters. You cannot add or delete items from the custom block once it has been placed in a DAP. You can only add and delete items within the Custom Block Document.

Custom Block documents can be saved and accessed at any time. This is especially important if you think you may want to add or delete items from it at some point. Once a custom block has been merged and imported into a DAP, it can be placed in the processing library and brought into any DAP.

Custom blocks can also be password protected by right clicking on it, choosing Properties, and entering a password under the Custom Block Password field of the DSP Attributes tab.

Answer:

You can have up to 24 channels of amplification (12 PA-2 cards) on a single AudiaFLEX unit, providing that the total power count does not exceed 120 watts.

Answer:

Instance IDs are unique identifying numbers assigned to each DSP block during the compilation process. You need to know them when creating a daVinci custom control panel, or if controlling an Audia system via Telnet or RS232.

Answer:

When creating a daVinci control panel, or programming a third party remote control device, you must know the instance ID of the block to be controlled. To check the instance ID of a specific DSP block, right click on that block, select Properties, and choose the DSP Attributes tab. The instance ID will be displayed there.

Alternately, you can choose the Object ID Inspector from the Tools menu. The Object ID Inspector will display a list of all DSP blocks and associated instance IDs within the compiled layout.

Yet another way to check instance ID is to press and hold Ctrl + A, point the mouse to the desired DSP block, and left click. The instance ID for that block will be displayed in the lower left corner of the Audia software.

By default, Audia will not reassign Instance ID numbers to DSP blocks whenever the layout is changed and compiled. It will only add additional Instance ID numbers. This function can be disabled by choosing Tools, then Options, selecting the Compile tab, and turning the Reassign Instance IDs option On.

Answer:

Audio will come back up in whatever state it was when powered down. It does not automatically mute when powered down.

Answer:

Yes. For best performance and to benefit from all features, both software and firmware need to be upgraded to their latest versions. Please check http://www.biamp.com/downloads.php for the most current software and firmware releases.

Answer:

Within the Audia software, and connected to the network:

1. Go to File, and select Perform Audia Device Maintenance.
2. Click on Upgrade Firmware, and browse to the location of the new firmware file. This will have a .jam extension.
3. Select the correct .jam file, and click on OK.
4. Please ensure that all details are correct, and click on Yes. The firmware will now be upgraded, which can take a few moments. Please do NOT disconnect or turn off the Audia at this point.
5. Once the new firmware is uploaded, click on OK to restart the device.

Answer:

The CDI file exists so that control screens can be moved and the data sent to the Audia without having to send the entire DAP file again. Therefore, even if control screens are not used a CDI file is generated. This comes in handy when you position a control screen while on line and want to keep it there. You can do this without having to resend the DAP file by simply moving the control screen, going to File, selecting Network and then clicking on Send Control Dialog Layout Information.

Answer:

The EXPI/EXPO front panel LCD display and rotary encoder are used to setup the device. Push the front panel encoder to get into the Menu. Turn the encoder until Bundle Number is displayed. Push the encoder once to enter the sub-menu and push it again to enter edit mode. Rotate the encoder to move the cursor along the display, push it to edit a number and push it again to confirm selection. Once the desired number is entered, navigate the cursor to the exit arrow, and push the encoder to exit.

Answer:

Audia can be remotely controlled with a PC running Audia or daVinci software, by the dedicated Audia remote controls (see below for more info on the Audia remotes) or by third party controllers using RS-232 or Telnet.

Audia software has several controls options such as level controls and preset recalls that can be password protected and accessed by users using a PC.

daVinci software allows the creation of visually rich custom control panels. For more information on daVinci software, please go to http://www.biamp.com/davinci.php

Audia Text Protocol allows for control and monitoring of Audia’s parameters via RS-232 or Telnet.

Answer:

Yes. By using the Command String block, a text string of the programmer's choosing can be automatically sent out the serial port when its logic node is activated. This string can be either in ASCII format, Hex, or a combination of both.
Logic events can be generated from an auto-mixer logic output, preset recall, event scheduler block, etc. (see the Audia Manual for more details).

Answer:

Yes. By using the ~ character, we’re telling Audia that the next two characters are in hexadecimal notation. For example, to send the character (0x0A), we must enter “~0A” in the Command String block.

Answer:

Yes. You will need to know the protocol of the equipment to be controlled, and have the correct cable. Audia transmits data on pin #2 of its 9-pin serial connector, with pin #5 being ground.

Simply type the correct commands onto Command String blocks, and have logic events triggering the strings when required.

Typical implementations of this include automatically controlling a video camera with the logic nodes of an auto mixer, or turning a projector on/off when audio is sensed on a particular input.

Please note that this method is restricted to one way communication only, as Audia will only react to incoming ATP commands. Commands on any other format will result in an error message.

Answer:

For every command string sent to Audia, Audia will return a confirmation. If you attempt to send a string before Audia has sent a reply, errors may occur. Make sure you have received a reply before sending Audia a string. In most cases, Audia should send a reply nearly instantaneously. Keep in mind that things like very large preset recalls can take longer.

Answer:

Audia can communicate at a baud rate of 9600, 19200, 38400, 57600 or 115200. Factory default is 38400. To change the baud rate of Audia, connect to the network with the Audia software, select Device Maintenance, select the Audia device you wish to change, and select Serial Port/ATP Settings. Choose the appropriate baud rate, and click OK to confirm the change.

Answer:

CobraNet is a licensed technology developed by Peak Audio, Inc. that allows for reliable, real-time transmission of un-compressed digital audio over standard 100Base-T Ethernet networks.

The basic unit of transmission between CobraNet devices is called a bundle. Each bundle can include up to 8 individual audio channels.

CobraNet bundles can be either multicast or unicast. Multicast bundles are sent to all CobraNet devices on the network. Unicast bundles are sent to one CobraNet device only. Each bundle is assigned a specific bundle number. Bundles 1-255 are always multi-cast. Bundles 256-65, 279 are unicast.

Audia uses CobraNet either implicitly or explicitly. Implicit use occurs when multiple Audia units are networked together to create a single large system. The seamless routing of digital audio among Audia unit in the system occurs implicitly through the CobraNet connections.

Explicit CobraNet connections occur when the need to route digital audio to a 3rd party CobraNet device occurs. In this case, the user would select a CobraNet input or output block within the Audia software and select the appropriate bundle number.

More info on CobraNet can be obtained at www.cobranet.info

Answer:

Typically, each Audia transmits 32 channels of digital audio via CobraNet on 4 'bundles' of 8 channels. Each Audia device can simultaneously send and receive 4 bundles with up to 8 audio channels in each bundle. This gives us a maximum of 64 channels of CobraNet through an Audia unit (32in/32out).

Audia software now utilizes the concept of "flexible CobraNet bundles". Flexible bundles can comprise any number of channels in the range of one to eight. Their size is adjusted automatically by the compiler on a case by case basis according to the number of channels passed between different Audia devices in the system. Accordingly, the total number of bundles that can be used in any Audia device is larger, up to sixteen, but depends upon the number of channels being transferred. The table below gives some guidelines about the communication bandwidth of an Audia device when using flexible bundles. Columns Rx and Tx indicate the absolute maximum number of channels that can be received or transmitted. Column Rx / Tx gives the maximum number of channels that can be received and transmitted at the same time.

Answer:

CobraNet connections between units of a networked system can be viewed by choosing Tools and then Options, selecting the Display tab and making sure ‘Display CobraNet connections’ is enabled. CobraNet signal flow will then be displayed in the chosen color.

Answer:

No. Each CobraNet output bundle must have a unique bundle number. In the case where two bundles are assigned the same number, whichever bundle starts transmitting first will be the one that is received by the CobraNet input.

Answer:

Starting with software version 3.0, Audia supports three CobraNet latency settings; 5⅓ msec, 2⅔, msec, and 1⅓ msec. To set the default latency setting for every new Audia design, go to Tools and then Options, select the Compile tab and choose the desired CobraNet latency from the drop down menu next to ‘Default CobraNet latency’ . Every time you create a new Audia layout, the software will use this setting.

To change the latency of an existing file, go to Tools and then Equipment Table. In the Equipment Table window, choose the desired latency from the drop down menu. This will affect the current DAP file only.

Please be aware, when using Audia with reduced latency CobraNet you will need to be using current Audia firmware as well as current CobraNet firmware. If interfacing with any external CobraNet equipment (something other than Audia) all devices will need to be set to the same latency setting. In the case of an EXPI or EXPO, you will need to enter the latency manually through the front panel controls to match the latency settings of the DAP file.

When using 5⅓ or 2⅔ msec CobraNet latency, you will be able to send 32 channels of audio and receive 32 channels of audio from any Audia device. When using 1⅓ msec CobraNet latency, the channel count will be reduced. Please see question: “How many channels of CobraNet does Audia use?” for more details.

Answer:

No, Biamp does not recommend specific brands or models of Ethernet switches to use with CobraNet. Any switch capable of Ethernet traffic at 100Mbps should work without problems.

Answer:

You may do so only under certain circumstances. To ensure trouble-free performance, it’s strongly recommended to use a dedicated network for CobraNet.

Answer:

There are several things you can do to troubleshoot a connection problem.

Please verify the IP address of your PC has been set correctly by typing ‘ipconfig” (minus quotes) at a Command Prompt and hit the Enter key. The current IP settings of your NIC will be displayed. If you’re unsure how to do open a DOS prompt, please go to How do I start a Command Prompt?

Please verify your connection by typing “ping” (minus quotes) at a Command Prompt, followed by a space and the IP address of the Audia and hit the Enter key. If the ping replies from the specified IP address, you have a verified connection from your PC to the Audia. If the ping doesn’t get a reply, it could be due to not having the correct IP address of the Audia, your PC and the Audia having different subnets, a bad CAT5 cable or a problem with your Ethernet switch. Please verify all connections and IP settings, and try again.

Answer:

Ok, don’t panic. There’re still a few things to try:

Check to ensure you only have a single Local Area Connection enabled within Windows. If more than one exists, you must disable those that aren’t being using by the Audia software. Right click on the ones what will not be used and select Disable.

Check that the right NIC is selected in the Audia software. Go to Tools, then Options and select the Network tab. Verify that the Default Network Interface Card currently selected is the correct one.

If your PC has a firewall installed (oftentimes part of a virus protection application) you will not be able to discover an Audia device with the Audia software. The firewall must be disabled. If you can PING a device successfully yet still not connect through Audia software; that usually indicates a firewall is running and blocking traffic between Audia and your PC.
Please note the Windows XP service pack 2 comes with a Firewall installed. If this is enabled, you will not be able to connect to an Audia. To disable the firewall go to the Start button, click on Control Panel, and open Windows Firewall. Ensure the firewall is turned Off.

Another option is to use TCP Discovery method. To do this, go to Tools, then Options and select the Network tab. Under Network Device Discovery Method, click to select TCP User Supplied Device List and then click on Edit Device List.
If there are no entries in the table, click the Add button. Double-click the space under Subnet Address and enter the first three octets of the IP address of the unit you wish to connect to (e.g. 192.168.1). Then click Edit Nodes and highlight the final octet of the device(s) you wish to connect to (e.g. 101). Then click OK all the way back out to the Audia desktop and connect.

Answer:

You most likely have a preset set as Power-Up default. This means that a preset will be recalled when Audia powers up. This is useful for when you want to ensure the Audia system will power-up with specific settings, but not if you want Audia to remember settings as they were when last switched off.

You can change this behavior by going to Presets, and selecting Create/Edit/Recall.

Answer:

Go to the Windows Start menu, select Run and type "command" or “cmd” (minus quotes) in the ‘Open’ field and click on OK.

Alternatively, go to the Windows Start menu, click on All Programs, select Accessories, and click on Command Prompt.

Answer:

An Audia outputs its IP settings (and other helpful information) through the serial port when it boots up.

Establish a serial connection by connecting your PC com port to the Audia serial port using a straight through serial cable. Open a terminal emulator such as Hyper Terminal on your PC, and enter the correct communication settings. Next, power-cycle the Audia and upon boot-up the IP settings will be displayed on the Terminal Emulator window.

Answer:

The default communication settings are:

Baud rate: 38400
Data Bits: 8
Parity: None
Stop Bits: 1
Flow Control: None

Answer:

A computer with a serial port or serial adapter with a Terminal emulation program like HyperTerminal installed and a straight through 9-pin d-sub serial cable.

Please note that Microsoft has removed HyperTerminal from Windows Vista. If you need to connect to an Audia via serial, you will have to install a Terminal Emulation program on your PC.

Answer:

HyperTerminal is a useful tool that comes with Windows and can be used for RS-232 purposes.

To open HyperTerminal and connect to Audia:

1. Connect your PC serial port to the Audia serial port using a straight-through 9-pin serial cable.
2. Click on the Windows Start button, click on All Programs.
3. Select Accessories, then Communications and click on HyperTerminal.
4. When prompted, enter a name for the connection, and click on OK.
5. Under the pull-down menu labeled ‘Connect Using’ select the location of your RS-232 Comm. Port and click on OK.
6. Under Comm port Properties, enter the correct communication settings.
7. HyperTerminal should now be ready to use. Please note that HyperTerminal does not echo typed characters by default. If you want to enable this function, please go to File, then Properties and select the Settings tab. Click on the ASCII Setup button, and enable ‘Echo typed characters locally’.

Answer:

You can use the Telnet client which comes as part of Windows.

To open a Telnet session with Audia:

1. Please ensure your PC and Audia are on the same subnet, and are connected either through an Ethernet switch or directly using a CAT5 cross-over cable.
2. Click on the Windows Start button, click on Run.
3. At the Open: prompt, type telnet XXX.XXX.XXX.XXX, where XXX.XXX.XXX.XXX is your Audia’s IP address.
4. Click on OK. A Telnet session should open, displaying ‘Welcome to the Biamp Telnet Server”.

Please note that not all versions of Windows Vista have the telnet client installed by default. Please refer to the Microsoft documentation on how to install the service, or you can choose to install an alternative telnet client of your choice.

For more information on the Audia line of programmable audio processors or to download the configuration software, please visit our web site at http://www.biamp.com. If you need a question answered or product/design assistance, call 1.800.826.1457 (US and Canada) or 503.641.7287.

Answer:

Up to 32 devices can be connected to a single Audia. An Audia system that uses multiple Audia units can have up to 32 RCB devices connected to each Audia in the system.

Answer:

No. Each remote is powered directly from the Audia it is wired to. No local power source is needed.

Answer:

You must use a two pair shielded cable. Biamp recommends Gepco UNC220, Liberty LLinx or equivalent. Use the data pair for Hi and Low, power pair for + and -.

You may also use Cat5 cable for wiring RCB devices. When doing so, please observe the following wiring scheme:

Orange....+
Brown ....+
Orange/White....-
Brown/White....-
Green....Hi
Green/White....Low
Blue....Ground
Blue/White....Ground


 

Answer:

All RCB device programming takes place within the Audia software. Drag and drop blocks are provided for the Volume 8, Select 8, Volume/Select 8, Logic Box and Voltage Control Box. Once a system is designed and compiled, each RCB object will be assigned a device number. After connecting to the Network with the Audia software, the Equipment Table will provide a section for RCB devices where serial numbers can be assigned to each RCB device that is part of your system configuration. After assigning serial numbers, simply send the configuration. This will upload all Audia and RCB programming to the required devices.

Answer:

If your presets have already been created, select a Remote Preset Button block within the Audia software and place it in your layout. Then open the block, right click on the buttons, and assign the desired preset to each button. Next, connect lines from the nodes of the Select 8 block to the nodes of the Remote Preset Block. Each node on the Select 8 represents one select function of the Select 8, numbered 1-8 from left to right. Finally, upload the configuration to the Audia unit.

When a Select 8 is configured to recall presets, an LED will light to indicate which preset is currently recalled. When recalling a different preset, the first LED will turn off and the new one will become illuminated.

Answer:

This can be done by using flip flop gates. Fan-out of each output node of the S8 to a Flip Flop gate and to a remote preset button node. When programming presets, include the flip flop gates for all preset buttons of that group into the preset. The flip flop state for the preset you are programming must have its Set button on. The flip flop gates for the other presets of that group must have their Set button off. Save each preset in this manner.

As long as a flip flop state button is on, that will cause the S8 LED to remain on. In this manner, one group can recall a preset and the flip flop will cause its LED to light. A second group can then recall a preset and its flip flop will cause its LED to light without affecting the first. You will then have recalled two presets and have two LEDs lit indicating the two presets.

Answer:

Yes. Simply wire from the S8 to the logic input node of a ducker. Make sure your audio source is running into the normal input of the ducker (upper input node.) Enable Logic In on the ducker’s control dialog. Press and hold the button on the S8 to trigger the ducker to duck the signal. Release the button and the audio signal returns to normal.

If you’d like the Select 8 button to function in a latching manner (press once to duck, press again to un-duck) wire a flip flop gate between the S8 and the ducker.

Answer:

The TI-2 card functions as a complete telephone interface for AudiaFLEX. The TI-2 has two discreet channels of telephone interface that can be programmed independently of one another. The TI-2 can function as a hybrid, allowing far end audio to be brought into your Audia system, routed and processed any way desired. It also allows audio to be transmitted from the AudiaFLEX back into the telephone line to the far end site.

The TI-2 also provides DTMF decoding capability. This allows a remote site to call into an Audia system and then hit the touch-tones (DTMF tones) to trigger logic control within the Audia. Uses of this include preset recall, system mute/unmute, or page routing.

Possible uses of the AudiaFLEX with the TI-2 include telephone conferencing, telephone paging, and remote access/control.

Answer:

Any standard analog (POTS) telephone line can be interfaced with the TI-2. Proprietary digital telephone lines cannot interface directly to the TI-2.

Answer:

Yes, simply wire the external telephone in parallel with the TI-2. In fact, the TI-2 input connector provides a parallel set of connections for this purpose.

Answer:

A TI-2 has two discreet channels of telephone interface, each with a 4 pole Phoenix connector. Looking at the card from the back of the Audia, the pin-out is as follows:

Connector 1 (top):
Pin 1: Channel 1 Tip
Pin 2: Channel 1 Ring
Pin 3: Channel 1 Tip (parallel)
Pin 4: Channel 1 Ring (parallel)

Connector 2 (bottom):
Pin 1: Channel 2 Tip
Pin 2: Channel 2 Ring
Pin 3: Channel 2 Tip (parallel)
Pin 4: Channel 2 Ring (parallel)

Answer:

There are a number of different ways to dial with the TI-2 depending on your requirements and preferred methods.

The Audia software provides a dialing interface for the TI-2. The software dialer functions similar to a mobile phone. You enter the entire phone number then press Send and the TI-2 goes off hook automatically and dials. Speed dial numbers can be saved to the dialer and simply activated with a single button push.

A dialer can be created in daVinci software, and can be used to control a TI-2 as part of a custom control panel. Speed dial numbers can also be made available to the user in this way.

3rd party remote control system can activate dialing as well. There are two different methods of dialing using 3rd party controls. The first method involves sending a control string that includes the entire phone number to dial. Simply send that string and the TI-2 will go off hook automatically and dial the entire number.

An alternate method using 3rd party controls requires you to send a string to take the TI-2 off hook and then send a string for each individual digit. This method would allow a control system to emulate a standard telephone set.

Another method would be to use an external telephone that is wired in parallel to the TI-2 to dial. Take the external phone off hook and dial the number. When appropriate, the TI-2 will need to be brought off hook to join the call. At that point, the external telephone can hang up.

Finally, Audia logic inputs (e.g. Select 8, Logic Box and VCB) can interface with the dialer to provide remote control dialing capabilities.

Answer:

The TI-2 can be taken on/off hook using RS232/Telnet control strings (TIHOOKSTATE attribute) or using a Logic input (Select8, Volume/Select8, Logic Box, Voltage Control Box) The TI-2 Rx block includes a logic input labeled HS (hook state). Sending a logic Hi to this logic node will take the TI-2 off hook. Sending a logic Lo will place the TI-2 on hook.

Answer:

Add a Logic State block to your Layout file, and connect its logic node to the HF node on the TI-2 Dialer block.

Using the correct ATP command, the Logic State can be turned on; effectively initiating the Hook Flash procedure.

Please remember a second command is needed to turn the Logic State block back to off, otherwise any subsequent Hook Flash will not be performed. Alternatively, you can fan out the logic out of the Logic State, pass it through a Logic Delay block, and have it recall a preset which turns the Logic State off. This way only one command is needed from the third party controller per Hook Flash.

Answer:

Check your instance ID numbers. Remember, each channel of TI-2 includes five discreet DSP blocks (Tx, Rx, Dialer, DTMF decode, Control/Status.) Each of these blocks has a unique instance ID number. Check the protocol documentation to make sure which DSP block the attribute you are programming for is associated with.

Answer:

Be sure to check for proper gain structure by checking your input and output meters. Ensure your microphone inputs have proper preamp gain adjusted. It's not uncommon to have your input gain set +42dBu or higher to get proper input level for any incoming microphone audio.