Stewart Audio FLX family amplifiers

To update the Steward Audio FLX family units, please follow the procedure below.

Audinate Version V3.10.4.1

Update for all units.

Corrected Issues:

  • The firmware corrects a loss of audio between Dante based devices after an extended static operating period (typically > 1 month)

Update procedure (unzip files first after download)(login needed):

  1. Install the DanteFirmwareUpdateManager-3.10.0.9
  2. Update the ult-01-004-3.10.4.1 firmware version.

Please note that the above steps need to be done in sequence, otherwise the device will fail.

Stewart Audio AV-25NET and AV-25NET+amplifiers

To update the Steward Audio AV-25NET and NET+ units, please follow the procedure below.

Audinate Version V3.10.4.1

Update for all units.

Corrected Issues:

  • The firmware corrects a loss of audio between Dante based devices after an extended static operating period (typically > 1 month)

Update procedure (unzip files first after download)(login needed):

  1. Install the DanteFirmwareUpdateManager-3.10.0.9
  2. Update the ult-01-002-3.10.4.1 firmware version.

Please note that the above steps need to be done in sequence, otherwise the device will fail.

Configure a Cisco Small Business Series Switch for Swisscom TV

Task description:

Using Swisscom TV in small environments is rather easy, just connect all Swisscom TV boxes into the Swisscom router and you are ready to go.
Looking to larger installs, specially in the residential area, this setup structure is often not an option as the complete in-house network is managed by a IT company or it has a network structure which does not follow the Swisscom guidelines.

The Cisco Small Business line of switches works usually very well for residential installations, for Swisscom TV they need a special configuration.

As specifications can change, this howto may only be a guideline, is has no intention to be absolutely correct.

Environment:

  • Swisscom router which connects to port 6 of the switch
  • Swisscom TV box on port 7  and 8 of the switch
  • VLAN 20 is used for all Swisscom TV data
  • Cisco SG300-10, firmware 1.4.0.88 (or higher)
  • IPv4 is used

Setup:

  1. Log in to the switch and go to VLAN Management -> VLAN Settings, create a VLAN for the Swisscom devices
    croppercapture1138 
  2. Assign the ports to the VLAN
    croppercapture1139
  3. Under Multicast -> Properties  activate and select the VLAN in the drop down. Activate for IPV4 the forwarding method IP Group Address
    croppercapture1140
  4. In Multicast -> IPv4 Multicast Configuration ->IGMP Snooping activate IGMP Snooping Status and IGMP Querier Status
    croppercapture1141
     
  5. Select VLAN 20 and hit Edit for additional settings
    croppercapture1142
  6. Multicast -> IPv4 Multicast Configuration -> IGMP VLAN Settings.
    Select the VLAN 20 and set accordingly
    croppercapture1143
     
  7.  If the switch still is flooded an additional setting can be done under Multicast – Unregistered Multicast.
    croppercapture1144
    Activate filtering of all unregistered multicast.

Howto add conventional door intercoms into Control4 using Symetrix

This howto bases on this environment:

  • Control4 system with EA-5, OS 2.8.2
  • Control4 touch panel Wall-10 and TT7
  • Universal SIP Doorstation driver (intercom_universal_doorstation)
  • Symetrix Radius EX with 2 Line VoIP Interface Card
  • Control4 driver for Symetrix matrixes, available on this website
  • Door intercom with analog audio in/out,  contact and a relay for control (Nothing brand specific)

Task description:

Existing buildings do often have intercom systems built in which are most likely not integrate into a SIP system like Control4. Various brands and techniques, often country specific manufacturers, old installations are already present in the field. Nevertheless Control4 customers are living in such buildings and want to integrate the door communication into the Control4 system.

Analog interfaces to get/send the audio and I/O’s are often available for this kind of installations, or can be engineered with very little effort. Using these possibilities Symetrix can act as interface between that analog and the SIP world of Control4

Architecture:

CropperCapture[986]

Control4 setup

Add the appropriate driver from the library. If a doorstation interface is wished take the Universal SIP Doorstation driver, else the Universal SIP Phone and add it to the project.

CropperCapture[990]

Make sure to set username and password for the SIP accounts, later on we have to insert that into the Symetrix config too, so write it down. Afterwards go to Actions and press Idle State.
If a camera is present add it to the system and select it as alternative camera, select the door interface buttons to be active and insert the text that should appear on the Navigators

CropperCapture[988]

CropperCapture[987]

CropperCapture[989]

Go to Agents and make sure all devices are in idle state an there is a group with a number defined which we will use as group to call on a doorstation event, for example group 22

CropperCapture[991]

Symetrix setup

Insert the VOIP card and make sure that its recognized by the unit. Open the design on the Radius EX by double clicking on it. Two new modules appear, both named with 2 Line VoIP Interface.

CropperCapture[992]

Minimum configuration is to connect the 2 VoIP modules to input/output as shown above. For sure other modules can be connected, such a supermodules or other to get a smarter config…

A double click to the bigger one of the two 2 Line VoIP Interface will bring up the VoIP module interface to manually take/do calls. Insert there the group we will call on C4, in our example group number 22. Also right click the number in front (marked in red) and assign a control number, 9000 in this example. Do the same for the button Call/End with another control number 9001

CropperCapture[1047]

To continue our setup, press Configuration Settings, a new window open with the status messages of our running VoIP configuration

CropperCapture[994]2

Again we have to go a step further by pressing VoIP Web Admin to be launched on the preferred interface, most probably on the AV Network
A new browser window opens with the effective SIP configuration pages. First set the IP of the VoIP module to a decent one.

CropperCapture[999]

Jump over to the SIP settings and set the codec priority, G722 does provide the best quality

CropperCapture[1045]

Afterwards set up the SIP accounts with username and password noted before.

CropperCapture[996]CropperCapture[997]CropperCapture[998]Once all setup is done the left side status messages should display Registered on the setup lines

Jumping back to the VoIP module interface we can try to do a call and as well to take calls. Try both ways to ensure to get audio both ways

Triggering a call on contact closure

Connect the contact lines from the 3rd party doorstation to a Control4 controller and insert a Single Contact using Composer, in Connections connect it to the hardware where the cables are connected. Using the matrix driver (well if it is not present in the project its now time to drop it in and do all settings that it runs, see the driver manual on ho to do this) we enter the 2 control numbers 9000 and 9001 as raw subscriptions

CropperCapture[1047]

And in programming we setup up that the contact closure does send out the control numbers

CropperCapture[1052]

If a end of call is provided by the doorstation the control number 9001 can be sent in the same style with the value 65535 to end the call

As alternative also an analog input from Symetrix can be used and trigger directly the control number.

Open the door

A single relay can be added and connected to a hardware relay, wire the cables to the doorstation relay input. To open a door with the door interface buttons simply add a task in programming which closes the relay

CropperCapture[1053]

Don’t forget to open it after a few seconds, otherwise the door will be open forever.

Enjoy

How to activate and check the Control4 Directors log for debug reasons

Follow these steps to get the Directors logs if support ask for it.

  1. Start Control4 System Manager,  all Programs -> Control4 -> Composer x.x.x -> System Manager. (If the System is not on site, first Connect with Composer to it)
  2. Select your Controller in the list and press connect
    CropperCapture[1003]
  3. Go to the Logging tab and select the Level trace for Director
    CropperCapture[1004]
  4. Once the log level has changed open Windows Explorer
  5. Insert into the address line \\IP.of.your.Controller and press enter. The Samba share of the Controller does show up
    CropperCapture[1005]
  6. Navigate to \log\debug and find director.log
    CropperCapture[1006]
  7. After debugging deactivate the log by setting the log Level to default using System Manager

NGTC-BIBOB-PoE firmware update procedure

To update the NGTC-BIBOB-PoE, Atterotech unDIO2x2 based, units, please follow the procedure below.

Audinate Version V4.1.1

unDIO2x2 MCU Release Notes

Feature enhancements:

  • Improves the minimum network latency from two milliseconds to one millisecond.

Corrected Issues:

  • The firmware fixes a couple of uncommon control protocol issues.

Update procedure (unzip files first after download)(login needed):

  1.  Install the AtteroTech-McuFirmwareUpdate
  2.  Install the DanteFirmwareUpdateManager-3.10.0.9
  3. Update the unDIO2X2-U_app_3_0_0 firmware with the Dante Firmware Update Manager to Version 3.
  4. Update the unDIO2x2.0800.8004.3.1 with the AtteroTech-Mcu Firmware Update Software.
  5. Update the unDIO2X2-C_app_4_1_1 firmware with the Dante Firmware Update Manager to Version 4.

Please note that the above steps need to be done in sequence, otherwise the device will fail.

Audinate Version V4.3.0

Update for all units that are running V4.1.1.

Corrected Issues:

  • The firmware corrects a loss of audio between Dante based devices after an extended static operating period (typically > 1 month)

Update procedure (unzip files first after download)(login needed):

  1. Install the DanteFirmwareUpdateManager-3.10.0.9
  2. Update the unDIO2x2_app_4_3_0 firmware version C or U.

Please note that the above steps need to be done in sequence, otherwise the device will fail.

 

NGTC-BIB4-PoE firmware update procedure

To update the NGTC-BIB4-PoE, Atterotech unD4I based, units, please follow the procedure below.

Audinate Version V4.0.0

unD4I MCU Release Notes
Feature enhancements:
• #1777 – Upgraded application firmware to support new features available in
Audinate’s Ultimo firmware version 2.1.1.18.
Corrected Issues:
• #2052 – Corrected Ethernet switch configuration settings which could cause random switch failures causing the unD4I to stop receiving audio and not be
discovered on the network.
• #2104 – Corrected network message handling for messages greater than
128 bytes.
• #2164 – Corrected an issue that prevented production device Dante firmware
from being updated.

Update procedure (unzip files first after download)(login needed):

  1. Install the AtteroTech-McuFirmwareUpdate
  2. Install the DanteFirmwareUpdateManager-3.10.0.9
  3. Update the unD4I-U_app_3_0_0 firmware with the Dante Firmware Update Manager to Version 3.
  4. Update theunD4I.0800.8004.3.3 with the AtteroTech-Mcu Firmware Update Software.
  5. Update the unD4I-C_app_4_0_0 firmware with the Dante Firmware Update Manager to Version 4

Please note that the above steps need to be done in sequence, otherwise the device will fail.

Audinate Version V4.3.0

Update for all units that are running V4.0.0.

Corrected Issues:

  • The firmware corrects a loss of audio between Dante based devices after an extended static operating period (typically > 1 month)

Update procedure (unzip files first after download)(login needed):

  1. Install the DanteFirmwareUpdateManager-3.10.0.9
  2. Update the unD4I_app_4_3_0 firmware version C or U.

Please note that the above steps need to be done in sequence, otherwise the device will fail.