TANDBERG E5714 DSNG Voyager, Reference Manual

Page: 313 / 314

EDH Capability for E57xx Encoders
Reference Guide: E57xx DSNG and DENG Voyager Encoder Page I-3
ST.RE.E10076.3
I.1 EDH Capability for E57xx Encoders
Table I.1 contains EDH capability for different mux firmware versions. To
find the mux firmware version for a particular Encoder refer to
Summary
Screen/More/Advanced/Setup/System/Build Menu
.
Table I.1: EDH Capability Matrix for E57xx Encoders
Mux F/W V14 and below Mux F/W V15
Base Card
Not Modified
Base Card
Modified
Base Card H/W Mod Strike 11 and below Base Card H/W Mod
Strike 12 and above
Software
versions 2.0.0
and above
(excluding 3.0.1)
EDH does not work, no errors
reported
•
Software aware that EDH
is not supported
EDH works, but unreliably
•
EDH support only partially implemented in
software
EDH works, but unreliably
•
EDH support only
partially implemented
in software
Software
versions 3.0.1
and above
EDH does not work, no errors
reported
•
Software aware that EDH
is not supported
•
Various EDH status flags
available in the menus (all
inactive)
•
UES (Unknown Error
Status) flags active
EDH works partially, converts edh errors to
eda, does not report all errors
•
Gennum chip modifies EDH data in
incoming SDI stream
•
If EDH is not present in incoming stream,
Gennum chip inserts it; therefore the
Encoder thinks EDH was there all along.
Error detection in this case is unreliable as
the CRCs and checksums are calculated
AFTER the errors have occurred.
•
If EDH is present in incoming stream (the
most likely scenario) the Gennum chip
detects CRC and checksum errors (edh),
turns those errors into edas and
recalculates CRCs. In this case the Encoder
reports the wrong type of errors, which
would make fault-finding very confusing for
an operator trying to find a fault in the SDI
chain.
EDH works as per
specifications