APNDAS-0109-Fox Splicer R3.0

Application Note
DASDEC™ - Fox® Splicer™ Integration
Introduction
The Fox Splicer is a Cisco product, and
is often called the DCM. FOX, along with
Cisco, have developed an IP network
API that allows an external EAS
DASDEC and weather alert system to
initiate alert text crawls with the FOX
Splicing System (Splicer). The Splicer
provides the ability to overlay a text crawl
over HD programming, when spliced to
either local or network. The DCM can
also be switched away from on-air audio
to a second input audio stream. In this
way, EAS text can be inserted over the
video and replacing the audio from
another input device to the DCM.
By integrating the DASDEC system with
the FOX Splicer, a broadcast station
Figure 1 Simple block diagram of Fox Splicer and DASDEC interfacing.
eliminates the need for a separate character generator as well
as maintains the highest quality FOX HD signal during alerts.
The DASDEC interfaces with the Splicer using a Net-CG
interface whose configuration is explained in this application note.
Interfacing with Fox Splicer
•
IMPORTANT NOTE: The DASDEC must have a valid “Plus” license in order to interface with the Fox
Splicer. For DASDEC v2.0 or higher it is labeled Plus Package. For DASDEC v1.86 or lower it is labeled
TV Plus. The “Plus” Package is included in any MultiStation™ unit.
1. Log onto the DASDEC box either remotely or locally from the web browser interface. The default is “Admin” as the User Name and “dasdec” as the password. (note: User Name and Password are case-­‐sensitive) Admin
●●●●●●
Figure 2 DASDEC login screen
Digital Alert Systems
A division of Monroe Electronics
585-765-1155 | fax 585-765-9330
100 Housel Ave. | Lyndonville | NY | 14098
www.digitalalertsystems.com
Revision: 3.0 Publication: APNDAS-109
Copyright © 2011 Digital Alert Systems, a division of Monroe Electronics Inc. Information
herein is considered accurate at the time of publication. We constantly strive to improve our
products and services therefore some specifications are subject to change without notice.
DASDEC, MultiStation, and EAS-Net are trademarks of Digital Alert Systems and Monroe
Electronics. All other trademarks are property of their respective owners.
Digital Alert Systems
Application Note
2. Go to Setup>Net Alerts> Net CG 3. Enable Net CG for Forwarding and Originating alerts, by placing a check in the boxes as shown in Figure 3. Figure 3 Enabling network based CG's
4. Click on Add Net CG Client Interface Figure 4 Adding a new Network based Character Generator client.
5. Naming the device is optional however it helps to keep track of the device. Moreover if using more then one Splicer (e.g. a primary and backup) giving them separate names avoids confusion. If no name is entered the DASDEC assigns a default name Client x where “x” is an increasing numeric value. In the example shown in Figure 5 below we use “FoxSplicer” as the name. Figure 5 Naming the Net CG client and enabling the interface
®
DASDEC™ - Fox Splicer™ Integration
Page 2 of 8
Digital Alert Systems
Application Note
6. It is also important to select (check) the “ENABLE Client Interface” box to turn on the newly added client. Deselecting (unchecking) this box will turn off this interface without deleting the other settings. 7. Continuing further down the screen under the “Select a protocol option” click the Fox Splicer/DCM radio button.
Figure 6 Selecting the Fox Splicer/DCM protocol
8. Scrolling down the screen in the Remote CG Net Host IP address box enter the IP address of the Splicer1. The example of Figure 7 the Splicer has an IP address of 10.110.123.121. Your configuration will most likely be different (see Footnote 1 page 3). 9. Leave the default /trigger/media/alert in the Path Component field as shown. 10. Set port number to 80. 11. Enter Robot in both the User and Password fields. This is case sensitive. Figure 7 Setting IP and default parameters for Splicer
12. Unless there is a need to independently define specific FIPS and/or EAS codes for activating the Splicer then leave the All FIPS code trigger and All EAS codes trigger boxes selected as shown in Figure 8. This will match the Setup >Decoder > Forwarding settings Figure 8 Selecting FIPS and EAS event codes.
1
Fox recommends using IP addressing of 10.110.XXX.121 for Splicer A and 10.110.XXX.198 for Splicer B, where XXX is the Splicer ID found
on the ROSA PC GUI. For a station with a Splicer ID of 86, enter only 86, not 086. (Refer to your Splicer manual for more information).
®
DASDEC™ - Fox Splicer™ Integration
Page 3 of 8
Digital Alert Systems
Application Note
13. An optional GPI (from the Splicer) can be used to signal the DASDEC when the Splicer is in, or out-­‐of-­‐network. Using this logic the Ethernet communication to the Splicer is gated based on the DASDEC’s input state. As an example by selecting the GPI Filter Configuration for “Designated GPI’s must be Closed” the communication to the Splicer configured above will only occur if the GPI input state is closed ie, the Splicer is In-­‐Network. Conversely, if the Splicer were out-­‐of-­‐network the Ethernet communication to the Splicer would be inhibited. The selection example can be seen in Figure 9. Figure 9 Setting the Optional GPI for triggering communications
Note: This
requires
additional port
configuration(s)
not explained in
this document.
In a similar fashion each NetCG client or serial port on the DASDEC can be gated using a GPI Filter Configuration setting. Using this feature as a logic flip-­‐flop the DASDEC can trigger the Splicer when it’s in-­‐network and control other CG’s – either network or serial controlled – when out-­‐of-­‐network. IMPORTANT NOTE: The input GPI used MUST NOT be assigned any Programmable GPIO Input Action function. Check Setup > GPIO and verify the wired input is set to “None” as the example shown in Figure 10 below. (THIS IS AN EXAMPLE ONLY – any available GPI can be used.) Figure 10 Using Optional GPI input be sure the used input is set to “None”. (Example shows setting for GPI input 1).
14. After setup is complete click Accept Changes. Figure 11 Accept Changes when done
**If using more than one Fox Splicer continue, otherwise skip to Network Setup**
®
DASDEC™ - Fox Splicer™ Integration
Page 4 of 8
Digital Alert Systems
Application Note
15. To add another Fox Splicer Select Duplicate Net CG Client Interface as shown in Figure 12, naming the additional unit(s) is optional, but highly recommended. In this example it is FoxSplicer2. Figure 12 Duplicating a Net CG interface. Naming each is recommended, though optional.
16. You should only need to change the IP address to the additional unit(s). All other settings remain the same. Set the Remote CG Net Host IP address to the IP of the second Splicer. The IP address 10.24.123.198 shown in Figure 13 is only an example – your IP address will most likely be different. (Be sure to use the IP address of the second Splicer – see Footnote 1 on Page 3). 10.24.123.198
Figure 13 Adding IP address of second Splicer. (Address 10.24.117.200 is an example only.) 17. Click Accept Changes when done Figure 14 Accept Changes when done.
Network Setup It is good network practice to configure the DASDEC with static routing information to ensure the TCP/IP
communication link to network based devices such as the Fox Splicer(s) is well defined. Setting static routing
configurations to the DASDEC ensures it is able to communicate without complex routing and name resolution
through a network. The following outlines setting the DASDEC for static routing.
1. Go to Setup > Network > Configuration page as shown in Figure 15. Figure 15 DASDEC Network Configuration page
2. It’s always advisable to have a secondary Network Interface Connection (NIC) set up to link with the Splicer. Select the proper Network Interface on the pull down menu that ®
DASDEC™ - Fox Splicer™ Integration
Page 5 of 8
Digital Alert Systems
matches the network to which the Splicer is connected. Depending on the DASDEC model and options there may be more than one Ethernet Network Interface. See Table 1 DASDEC Network Interface Options for more information. Application Note
Network Name
Main Network Interface
2
nd
Network Interface
DASDEC-I
Integrated
USB –
Ethernet
Dongle
rd
N/A
th
N/A
3 Network Interface
4 Network Interface
3. Enable the network port by clicking (selecting) the DASDEC-II
Integrated
Integrated
Option
Integrated
Option
Integrated
Option
Table 1 DASDEC Network Interface Options
check box that matches the physical network port on which the Splicer is connected. (See Figure 16 for a representation of the port Figure 16 DASDEC-II Physical port assignments.
numbers). The example in Figure 17 corresponds to using the second NIC port. 4. Following Fox recommendation the address for the DASDEC port should be 10.110.xxx.170, where xxx is the Splicer ID as referenced in Footnote 1 on Page 3 and shown in the Figure 17 example. It is also recommended the Netmask be set at 255.255.255.254, however we have found 255.255.255.0 to work. The hostname can be changed. Figure 17 Setting DASDEC Second Network Interface port to communicate with Splicer.
5. Click Accept Changes / Restart Network when done. Figure 18 Accept Changes will restart the network. Logging in again may be necessary.
6. The DASDEC will restart the network connections and, after approximately a minute, you may have to log in again to continue. 7. Return to the Setup > Network > Configuration page scrolling down to the static route section where you can set different static routes to provide a dedicate communication path between the DASDEC and the Splicer. ®
DASDEC™ - Fox Splicer™ Integration
Page 6 of 8
Digital Alert Systems
Application Note
8. Clicking the Add Static Route button adds additional routing selections. Select a Static Route and enable it by selecting (clicking) the Enable box. See Figure 19. 9. Enter the IP Address for the Splicer in the IP Address field or, as shown in the Figure 19 example, setting the last octet to zero allows communication with all 10.24.123.xxx traffic. (IMORTANT: The third octet shown as “123” in this example should be the Splicer ID number used in all the previous settings.) 10.24.123.0
10.110.123.161
Figure 19 Adding static routing information. IP address are shown as examples only.
10. Enter the Netmask, and any Gateway address for this Fox Splicer network. Again Fox recommends the Netmask be set at 255.255.255.254 and we have found 255.255.255.0 to work while the Gateway should be set at 10.110.xxx.161 where xxx is the previously noted Splicer ID (See Footnote 1). 11. Be sure to select the corresponding Network Interface with the pull-­‐down menu. 12. When this is complete click Accept Static Route Changes/Restart Network, to accept changes. Configuring the GPOs As depicted in Figure 1 the Fox Splicer requires three connections from the DASDEC; one Ethernet and two GPO’s –
activate (GPO-1) and deactivate (GPO-2). The example below assumes the Splicer is using the standard GPIO
2
connections on the DASDEC.
1. Go to the Setup > GPIO > Main GPIO page. 2. Select “Momentarily at start of EAS Audio Playout” for GPI Output 1 Relay is closed and “Momentarily at end of EAS Audio Playout” for GPI Output 2 Relay is closed as shown in Table 2 and Table 3. ** If using
MultiStation™
continue, otherwise
setup is complete **
Table 2 GPO 1 set for "Momentarily at start
of EAS Audio Playout"
2
Table 3 GPO 2 set for "Momentarily at end of
EAS Audio Playout"
The settings are the same if using the optional internal EXP-GPIO board or either network based GPI/O options.
®
DASDEC™ - Fox Splicer™ Integration
Page 7 of 8
Digital Alert Systems
Application Note
MultiStation setup with Fox Splicers If the DASDEC is configured for MultiStation operation there are additional settings required to associate the Splicer
with the appropriate station(s). This section describes how to link the Splicer(s) with the station(s).
1. Go to the Setup > Decoder > Forwarding tab as shown in Figure 20. Figure 20 Setting up Decoder Forwarding
2. From the MultiStation Interface Configuration section use the pull down menu to select the station to associate with the Fox Splicer. In the example from Figure 21 the station name is ABCD. (Note the * next to the name indicates a station is enabled.) Figure 21 Selecting a station in the MultiStation Interface Configuration
3. From the table selections near the middle of the page is a section titled Active Orig/Fwrd Net CG Clients and immediately below is the list of available devices available this station. Selecting the previously named “FoxSplicer” will associate this device with this station. (Select more then one Splicer by holding down the Ctrl key and clicking.) Figure 22 Table of mapping devices to stations
5. When you have finished with the selection(s) click on the Submit Selection Settings as shown in Figure 23 to save the station information. Figure 23 Click Submit Selection Settings when complete.
®
DASDEC™ - Fox Splicer™ Integration
Page 8 of 8