Goto Section: 11.32 | 11.34 | Table of Contents

FCC 11.33
Revised as of
Goto Year:1996 | 1998
Sec. 11.33  EAS Decoder.

    (a) An EAS Decoder must at a minimum be capable of decoding the EAS 
protocol described in Sec. 11.31, provide the EAS monitoring functions 
described in Sec. 11.52, and the following minimum specifications:
    (1) Inputs. Decoders must have the capability to receive at least 2 
audio inputs from EAS monitoring assignments, and one data input (RS-
232C with standard protocol and 1200 baud rate). The data input may be 
used to monitor other communications modes such as Radio Broadcast Data 
System (RBDS), NWR, satellite, public switched telephone network, or any 
other source that uses the EAS protocol.
    (2) Valid codes. There must be a means to determine if valid EAS 
header codes are received and to determine if preselected header codes 
are received.
    (3) Storage. Decoders must provide the means to:
    (i) Record and store, either internally or externally, at least two 
minutes of audio or text messages. A decoder manufactured without an 
internal means to record and store audio or text must be equipped with a 
means (such as an audio or digital jack connection) to couple to an 
external recording and storing device.
    (ii) Store at least 10 preselected event and originator header 
codes, in addition to the eight mandatory event/originator codes for 
tests and national activations, and store any preselected location codes 
for comparison with incoming header codes. A non-preselected header code 
that is manually transmitted must be stored for comparison with later 
incoming header codes. The header codes of the last ten received valid 
messages which still have valid time periods must be stored for 
comparison with the incoming valid header codes of later messages. These 
last received header codes will be deleted from storage as their valid 
time periods expire.
    (4) Display. A visual message shall be developed from any valid EAS 
header codes received. The message will include the Originator, Event, 
Location, the valid time period of the message and the local time the 
message was transmitted. The message shall be in the primary language of 
the broadcast station or cable system and be fully displayed on the 
decoder and readable in normal light and darkness.
    (5) Indicators. EAS decoders must have a distinct and separate aural 
or visible means to indicate when any of the following conditions 
occurs:
    (i) Any valid EAS header codes are received as specified in 
Sec. 11.33(a)(10).
    (ii) Preprogrammed header codes, such as those selected in 
accordance with Sec. 11.52(d)(2) are received.
    (iii) A signal is present at each audio input that is specified in 
Sec. 11.33(a)(1).
    (6) Program Data Retention. The program data must be retained even 
with power removed.
    (7) Outputs. Decoders shall have the following outputs: a data port 
or ports (RS-232C with standard protocol and 1200 baud rate) where 
received valid EAS header codes and received preselected header codes 
are available; one audio port that is capable of monitoring each decoder 
audio input; and, an internal speaker to enable personnel to hear audio 
from each input.
    (8) Decoder Programming. Access to decoder programming shall be 
protected by a lock or other security measures and be configured so that 
authorized personnel can readily select and program the EAS Decoder with 
preselected Originator, Event and Location codes for either manual or 
automatic operation.
    (9) Reset. There shall be a method to automatically or manually 
reset the decoder to the normal monitoring condition. Operators shall be 
able to select

[[Page 592]]

a time interval, not less than two minutes, in which the decoder would 
automatically reset if it received an EAS header code but not an end-of-
message (EOM) code. Messages received with the EAN Event codes shall 
disable the reset function so that lengthy audio messages can be 
handled. The last message received with valid header codes shall be 
displayed as required by paragraph (a)(4) of this section before the 
decoder is reset.
    (10) Message Validity. An EAS Decoder must provide error detection 
and validation of the header codes of each message to ascertain if the 
message is valid. Header code comparisons may be accomplished through 
the use of a bit-by-bit compare or any other error detection and 
validation protocol. A header code must only be considered valid when 
two of the three headers match exactly. Duplicate messages must not be 
relayed automatically.
    (11) A header code with the EAN Event code specified in 
Sec. 11.31(c) that is received through any of the audio inputs must 
override all other messages.
    (b) Attention Signal. EAS Decoders at broadcast stations shall have 
detection and activation circuitry that will demute a receiver upon 
detection of the two audio tones of 853 Hz and 960 Hz. To prevent false 
responses, decoders designed to use the two tones for broadcast receiver 
demuting shall comply with the following:
    (1) Time Delay. A minimum time delay of 8 but not more than 16 
seconds of tone reception shall be incorporated into the demuting or 
activation process to insure that the tones will be audible for a period 
of at least 4 seconds. After July 1, 1995, the time delay shall be 3-4 
seconds.
    (2) Operation Bandwidth. The decoder circuitry shall not respond to 
tones which vary more than &177;5 Hz from each of the 
frequencies, 853 Hz and 960 Hz.
    (3) Reset Ability. The decoder shall have a means to manually or 
automatically reset the associated broadcast receiver to a muted state.
    (c) Decoders shall be capable of operation within the tolerances 
specified in this section as well as those in Sec. 11.32 (b), (c) and 
(d).
[ 59 FR 67092 , Dec. 28, 1994, as amended at  60 FR 55999 , Nov. 6, 1995]


Goto Section: 11.32 | 11.34

Goto Year: 1996 | 1998
CiteFind - See documents on FCC website that cite this rule

Want to support this service?
Thanks!

Report errors in this rule. Since these rules are converted to HTML by machine, it's possible errors have been made. Please help us improve these rules by clicking the Report FCC Rule Errors link to report an error.
hallikainen.com
Helping make public information public