Digital Alert Systems DASDEC-II MANUAL - Manual (Page 112)

106
Digital Alert Systems: DASDEC User Manual
4.10.6 Net CG
This page allows configuration of up to five client targets for running alert crawls. The Net CG units must support
Ethernet and be connected to the same LAN as the DASDEC II. As in the other Net Alert pages, use the Alert
Forwarding and/or the Encoder Originated Alert toggles to enable/disable the use of Net CG clients when alerts
are forwarded and/or originated.
Addition/duplication/deletion, configuration, and enable/disable for each client interface are handled just like the
other Net Alert interfaces described in the previous chapters.
The first option is to choose a Client Interface Name. This is to name the CG to reduce confusion between
multiple devices.
ENABLE Client Interface
Check this box in order to enable the specific client that you have selected to edit, or just created.
Select a Protocol Option
Select the CG that pertains to your situation. The list of compatible Network CGs are, COMPIX NewsScroll,
COMPIX Autocast, Simple Chyron Intelligent IF, Raw Chyron IntelIF & ChyTV, Simple ChyTV IF, CODI Net
CG, Cayman Graphics, Fox Splicer/DCM, Inovonics RDS730.
Remote CG Net Host IP and Port
In this field, type the IP address and the port of the CG that is on the same network connection that your
DADEC is on.
All FIPS codes trigger. Check to enable all alerts, regardless of FIPS codes, to trigger a crawl on the target
CODI. Uncheck to only allow alerts for specific FIPS areas to trigger the crawl. When unchecked, you can
select from the Encoder FIPS pool or the Forwarding FIPS pool to add the list of allowed FIPS that trigger
this CODI alert send. After a set of FIPS codes have been selected, use the
button to add the selections to the filter list (labeled as the Streaming CODI CG Net client FIPS List). Alerts
to these locations will be sent to the remote CODI.
All EAS codes trigger
If enabled, all EAS codes will trigger the Net CODI client interface. Set the checkbox to enable/disable EAS
code filtered trigger control. If disabled, then the alert EAS code is filtered for a specific match as a way to
control whether or not the target CODI is triggered. If All EAS is disabled, select EAS codes from the
provided lists and add to the client EAS list. If the EAS code of an active forwarded/originated alert matches
any of these EAS, the alert will be sent using the Net CODI client. With careful use of this feature, and with
multiple clients, one DASDEC II can serve many different cable regions at the same time.
When you finish making changes, click to save the configuration.
4.10.7 Net GPIO: Configure NET GPIO Clients
This sub-page under Setup > Net Alerts is a standard feature on a DASDEC II to allow remote, LAN connected
GPIO relays and inputs to be associated to active alerts. The DASDEC II supports the Titus Technology WR-300
module with four relays (the same hardware as the Monroe Electronics R190 Hub Controller), the Control-by-
Web Web-Relay Quad with four relays (the same hardware as the Monroe Electronics R190A Hub Controller)
and Web-Relay Dual module with two relays and two inputs. This interface page provides for creating,
duplicating, deleting and configuring client connections for up to eight LAN positioned relays. This type of
hardware provides an inexpensive and convenient way to expand the contact closures relays of the DASDEC II.
Since these relays can be placed on a LAN, and controlled by the DASDEC II remotely, they can be used to
trigger actions during alerts without extra wiring. Configuration is much like the other Net Alert pages. Up to 8
clients can be configured and active at a time.