EDGEPROBE ADVANCED

DTV MONITORING PROBE

User Manual
Firmware Version 4.1

c/o ENENSYS Technologies Tel: +33 (0)1 70 72 51 70

6 rue de la Carrière Fax: +33 (0)2 99 36 03 84
CS 37734 sales@test-tree.com
35577 Cesson-Sévigné – France support@test-tree.com
COMPANY IDENTIFICATION

TestTree c/o ENENSYS Technologies

6 rue de la Carrière, CS 37734
35577 Cesson-Sévigné, France

SAFETY INSTRUCTIONS

Warning
Do not open the metal housing for any reason, since high voltage may be present. Do not replace the
fuse of the power supply unit. Contact TestTree’ Technical Support at support@test-tree.com.
Risk of electric shock.
Compliance
This equipment has been tested and found to comply with the limits for a Class A digital device, pursuant to Part
15 of the FCC Rules. These limits are designed to provide reasonable protection against harmful interference
when the equipment is operated in a commercial environment. This equipment generates, uses, and can radiate
radio frequency energy and, if not installed and used in accordance with the instruction manual, may
cause harmful interference to radio communications. Operation of this equipment in a residential area
is likely to cause harmful interference in which case the user will be required to correct the interference
at his own expense.
The FCC/CE compliance label is situated on the underside of the equipment.
Any changes or modifications to this equipment not expressly approved by TestTree may cause harmful
interference and void the FCC authorization to operate this equipment.
Grounding
This equipment must exclusively be connected to an electrical circuit that is:
- Provided with a ground fault circuit interrupter (GFCI) complying with IEC 364 and NFC15-100 regulations.
- Compliant with the voltage characteristics specified by the NF EN 50160 standard.
The reliability of the grounding system must be checked before mounting the product in the rack, especially in
case of diverting system.
Disposal
In compliance with the European Directive 2002/96/CE relative to the management of Waste Electrical and
Electronic Equipment (WEEE) implemented as of August 13, 2005, this product may not be disposed of with
regular household waste.
All products concerned by this directive are marked with the symbol on the left.
The end owner of this product is responsible for either:
- Transferring the product to an authorized treatment facility where the product components,
recognized to present a hazard to the environment and/or public health, will be recycled and
recovered properly, or
- Consulting with the manufacturer for appropriate product waste management according to the terms of the
manufacturer.

EdgeProbe Advanced - User Manual – 4.1 – 2 / 120

ENVIRONMENTAL INFORMATION TEST MONITORING
Product dimensions: height 45 mm / 1.7 in, width: 440 mm / 17.3 in, depth: 240 mm / 9.4 in
Product weight: up to 4.5 kg (depending on the HW options)
Format: 1 RU, width 19 in
Operating temperature: -20 to 55 °C / -4 to 131 °F
Storage temperature: -20 to 70 °C / -4 to 158 °F
Humidity: 0 to 95%, non-condensing
Maximum operating altitude: 2000m

ELECTRICAL INFORMATION
Authorized voltage range: 100 – 240 VAC ±10%, 50/60 Hz
The power primary contains two fuses: T 3.15 A, 250 V.
The product provides one or two (depending on the HW options) physical power supply CEI 320 connectors,
which must be available to reach for disconnection means.

POWER CONSUMPTION
25W

MOUNTING IN RACK
This equipment shall be mounted in a 19” rack. It should be appropriately secured to the rack using screws, in
order to avoid eventual dangerous situations caused by an abnormal mechanical overload. A space of ½ U is
recommended between equipment to ensure proper cooling.

POWERING UP
Plug the power cable into the power receptacle on the product's rear panel. Then, connect the other end of the
cable to the main power.
Please note that an eventual power overload may damage the security fuses and the power cables. The
electrical characteristics of the other equipment mounted in the rack must be taken into consideration.

POWERING DOWN
The product may have more than one power connectors. Disconnect all power connectors from the power
supply in order to power down the unit.

INPUT/OUTPUT SPECIFICATION
Please refer to the EdgeProbe Advanced User Manual available for download on the ENENSYS Privileged
Area website (privileged.enensys.com) or on the EdgeProbe’s remote web GUI (“About” menu).

EdgeProbe Advanced - User Manual – 4.1 – 3 / 120

 TABLE OF CONTENTS
COMPANY IDENTIFICATION ...................................................................................................................................................... 2
SAFETY INSTRUCTIONS ............................................................................................................................................................ 2
ENVIRONMENTAL INFORMATION TEST MONITORING ............................................................................................................... 3
ELECTRICAL INFORMATION....................................................................................................................................................... 3
POWER CONSUMPTION........................................................................................................................................................... 3
MOUNTING IN RACK .............................................................................................................................................................. 3
POWERING UP ...................................................................................................................................................................... 3
POWERING DOWN................................................................................................................................................................. 3
INPUT/OUTPUT SPECIFICATION ................................................................................................................................................ 3
1 INTRODUCTION .....................................................................................................................................................7
1.1 PRODUCT OVERVIEW ................................................................................................................................................. 7
1.2 PC/LAPTOP MINIMUM REQUIREMENTS......................................................................................................................... 9
1.3 PACKING LIST ........................................................................................................................................................... 9
2 WALK AROUND ...................................................................................................................................................10
2.1 FRONT PANEL ........................................................................................................................................................ 10
2.2 REAR PANEL .......................................................................................................................................................... 11
2.3 WHERE TO PLACE THE PROBE AT THE TX SITE? .............................................................................................................. 13
3 QUICK START .......................................................................................................................................................14
3.1 FIRST EDGEPROBE CONNECTION ................................................................................................................................ 14
3.2 GRAPHICAL USER INTERFACE .................................................................................................................................... 15
3.2.1 Menu ............................................................................................................................................................. 15
3.2.2 Configuration and Monitoring ...................................................................................................................... 16
3.2.3 Status ............................................................................................................................................................ 16
3.3 GETTING THE USER MANUAL .................................................................................................................................... 16
3.4 GETTING THE CURRENT FIRMWARE VERSION ................................................................................................................ 17
3.5 INSTALLING A FIRMWARE UPGRADE ............................................................................................................................ 17
3.5.1 Web GUI upgrade .......................................................................................................................................... 17
3.5.2 FTP upgrade .................................................................................................................................................. 17
3.6 LOADING A DEVICE CONFIGURATION ........................................................................................................................... 18
4 DEVICE SETTINGS ................................................................................................................................................19
4.1 CONTROL IP ADDRESS ............................................................................................................................................. 19
4.2 DATA IP ADDRESS ................................................................................................................................................... 20
4.3 WEB GUI REFRESH PERIOD ...................................................................................................................................... 21
4.4 LOCAL DATE AND TIME ............................................................................................................................................. 21
4.4.1 Checking the current time configuration....................................................................................................... 21
4.4.2 System date & time ....................................................................................................................................... 22
4.4.3 NTP date & time ............................................................................................................................................ 22
4.5 SNMP NMS TRAP RECEIVER ................................................................................................................................... 23
4.6 REFERENCE CLOCK FOR SFN MONITORING ................................................................................................................... 23
4.7 DEVICE ALARMS ..................................................................................................................................................... 24
4.8 INTERNAL MEMORY MANAGEMENT ............................................................................................................................ 25
4.8.1 Log files configuration ................................................................................................................................... 26
4.8.2 Trend files configuration ............................................................................................................................... 26
4.8.3 Record files configuration ............................................................................................................................. 27
5 CONFIGURE MONITORING...................................................................................................................................30
5.1 CONFIGURE ALARM PROFILES ................................................................................................................................... 31
5.1.1 General alarm settings .................................................................................................................................. 32
5.1.2 RF Alarm settings .......................................................................................................................................... 34
5.1.3 ASI input Settings .......................................................................................................................................... 36

EdgeProbe Advanced - User Manual – 4.1 – 4 / 120

 5.1.4 IP input Settings* .......................................................................................................................................... 36
5.1.5 ETR 101 290 Priority 1 Settings ..................................................................................................................... 37
5.1.6 ETR 101 290 Priority 2 Settings ..................................................................................................................... 38
5.1.7 ETR 101 290 Priority 3 Settings ..................................................................................................................... 39
5.1.8 BTS Settings* ................................................................................................................................................. 41
5.1.9 T2-MI Settings ............................................................................................................................................... 42
5.1.10 MIP Settings .............................................................................................................................................. 43
5.1.11 Advanced Settings .................................................................................................................................... 44
5.1.12 SFN Settings .............................................................................................................................................. 45
5.1.13 Echoes Settings ......................................................................................................................................... 46
5.1.14 Multiplex-Services Settings ....................................................................................................................... 46
5.1.15 OneBeam Settings .................................................................................................................................... 47
5.1.16 EWS Settings ............................................................................................................................................. 47
5.2 CONFIGURE CHANNELS ............................................................................................................................................ 49
5.2.1 Managing channels ....................................................................................................................................... 50
5.2.2 Creating Scanning list .................................................................................................................................... 54
5.2.3 Selecting the monitoring operating mode .................................................................................................... 56
5.3 CONFIGURE OUTPUT* ............................................................................................................................................. 56
5.4 CONFIGURE TRANSCODING....................................................................................................................................... 58
5.4.1 TRANSBOX first connection and IP configuration .......................................................................................... 59
5.4.2 Transcoding configuration via EdgeProbe ..................................................................................................... 60
5.4.3 TRANSBOX & Transcoding alarms on EdgeProbe .......................................................................................... 61
5.5 GENERAL MONITORING CONFIGURATION ..................................................................................................................... 61
6 MONITORING VIEWS ...........................................................................................................................................62
6.1 OVERVIEW ............................................................................................................................................................ 62
6.2 ALARM VIEW......................................................................................................................................................... 66
6.2.1 Alarm Trigger, Counter, Log line and Trap mechanism .................................................................................. 68
6.3 MONITORING VIEW ................................................................................................................................................ 70
6.3.1 Channel ......................................................................................................................................................... 70
6.3.2 SFN Drift ........................................................................................................................................................ 73
6.3.3 Carrier Frequency Drift .................................................................................................................................. 74
6.3.4 Echoes ........................................................................................................................................................... 75
6.3.5 QoS ................................................................................................................................................................ 76
6.3.6 T2-MI ............................................................................................................................................................. 77
6.3.7 Multiplex-Services ......................................................................................................................................... 78
6.3.8 OneBeam....................................................................................................................................................... 81
6.3.9 SCTE 35 .......................................................................................................................................................... 82
6.3.10 Data Storage ............................................................................................................................................. 83
6.3.11 GNSS ......................................................................................................................................................... 84
6.3.12 Logs Events ............................................................................................................................................... 85
7 ADMINISTRATION................................................................................................................................................86
8 GENERAL INFORMATION .....................................................................................................................................87
9 NMS INTEGRATION ..............................................................................................................................................89
10 UPDATES AND PRIVILEGED AREA .........................................................................................................................91
11 TROUBLESHOOTING ............................................................................................................................................92
11.1 DEVICE STATUS AND ALARMS..................................................................................................................................... 92
11.1.1 Power LED ................................................................................................................................................. 92
11.1.2 Run LED ..................................................................................................................................................... 92
11.1.3 Web GUI connection ................................................................................................................................. 93
11.1.4 *GNSS LED ................................................................................................................................................ 93
11.1.5 Temperature ............................................................................................................................................. 93

EdgeProbe Advanced - User Manual – 4.1 – 5 / 120

 11.1.6 NTP Server, date/time synchronisation ..................................................................................................... 95
11.1.7 1PPS synchronization ................................................................................................................................ 95
11.1.8 10MHz synchronization ............................................................................................................................ 96
11.1.9 *GNSS 1PPS synchronization .................................................................................................................... 96
11.1.10 NMS traps ................................................................................................................................................. 97
11.2 MONITORING ALARMS............................................................................................................................................. 97
11.2.1 RF input ..................................................................................................................................................... 97
11.2.2 SFN Drift .................................................................................................................................................... 99
11.2.3 TS_sync ..................................................................................................................................................... 99
11.2.4 Multiplex-Services ................................................................................................................................... 100
12 EQUIPMENT RETURN FOR REPAIR ..................................................................................................................... 101
13 CONTACT INFORMATION ................................................................................................................................... 102
14 APPENDIX .......................................................................................................................................................... 103
14.1 ETR ALARMS LIFECYCLE ......................................................................................................................................... 103
14.2 SCANNING RECOMMENDATIONS .............................................................................................................................. 108
14.2.1 Scanning functioning .............................................................................................................................. 108
14.2.2 Alarms lifecycle and scanning time ......................................................................................................... 109
14.2.3 Conclusion: recommended scanning time .............................................................................................. 110
14.3 SFN SYNCHRONIZATION MEASUREMENT ................................................................................................................... 111
14.3.1 DVB-T SFN measurement ........................................................................................................................ 111
14.3.2 DVB-T2 SFN measurement ...................................................................................................................... 112
14.3.3 ISDB-T/Tb SFN measurement .................................................................................................................. 113
14.3.4 T2-MI Network delay measurement ....................................................................................................... 115
14.4 QOS MONITORING PARAMETERS.............................................................................................................................. 116

EdgeProbe Advanced - User Manual – 4.1 – 6 / 120

1 INTRODUCTION

1.1 PRODUCT OVERVIEW

EdgeProbe Advanced is a standalone product that provides monitoring of DTV network and
transmission.
Running at the transmission sites, the EdgeProbe Advanced monitors IP/ASI streams at the IRD
output and at the modulator input; as well as RF signals at the satellite distribution reception and at
the output of the DTT transmitter.
At the Head-End, the EdgeProbe Advanced monitors the TS/T2-MI/BTS/OneBeam
(SingleIllumination) transport over IP/ASI/satellite RF before leaving over the distribution link.
Combined with a Network Monitoring System, EdgeProbe Advanced turns into a powerful network
diagnosis tool allowing service providers to highlight global trends and to anticipate potential failures
as well as providing statistics on the services. The EdgeProbe GlobalViewer provides a centralized
view over the network’s quality.

EdgeProbe Advanced is able to continuously monitor DTV signals over RF, ASI or IP inputs.
EdgeProbe Advanced is able to continuously log all measured values in a permanent file and to send
SNMP traps if parameter values get out of the defined range. For troubleshooting, a web based
remote interface (GUI) allows access to all parameters from RF to baseband transport.
EdgeProbe Advanced provides monitoring of the signal at different levels:
• Transmission: RF Monitor and Synchronization Monitor (RF SFN Drift, Carrier Frequency
Offset and Drift) check the status of the transmitter. The Channel Impulse Response Monitor
allows to check the on-field reception quality as well as the gap filler/retransmission quality.
• Distribution: T2-MI, BTS and OneBeam (SingleIllumination) Monitor allows to check the

EdgeProbe Advanced - User Manual – 4.1 – 7 / 120

 conformance of the distribution link (over satellite RF, ASI, IP): before leaving the Head-End
and on the transmission site before modulation. Also, the T2-MI Network Delay can be
measured on TX site before the modulator input.
• Transport Stream: TS Monitor allows to check the conformance of the MPEG-2 TS to ETR
101 290 (priorities 1, 2 & 3) and the Quality of Service (SAE/SDE).

TS processing
The T2-MI PLP extraction enables both T2-MI encapsulation check and extracted PLP TS validation.
The Service Plan option provides the means to check the description of your multiplexes and verify
your regional services: min/max bitrates, Service and PID presence check.
The OneBeam (SingleIllumination) monitoring allows to monitor & verify the DVB-T2 information
into the DTH stream: T2-MI Marker and the In-Band PIDs information.
The dual CI slot supports service descrambling of up to two 1CA systems at the same time.
TS services can be displayed on a screen via the *HDMI output ports.
Combined with the *TRANSBOX, the EdgeProbe can provide service streaming over low
bandwidth network links, for third party systems for confidence monitoring.

TS retransmission over ASI/IP output

With its ASI-output it can also be used as a powerful rebroadcasting receiver, with the capacity to
“mute” the retransmission depending on the input signal’s quality (BER thresholds for “mute”
criteria).
The IP-Forward* over the dedicated data port, provides the gateway from RF to IP networks: the
analyzed TS (or extracted PLP TS) can be streamed to third party QoE analysis systems.

Monitoring modes: Single Channel and Round-Robin

EdgeProbe Advanced is able to continuously monitor one DTV signal over RF or ASI or IP input
within one Monitoring Unit (up to 4x Monitoring Units can be installed within a 1RU device).
The Scanning feature provides a powerful tool for multiple channels sequential monitoring (round-
robin sequence). Multiple frequencies/PLPs can be monitored using a configurable round-robin
scanning mode; which maintains the monitoring context between two sequential monitoring rounds.

Hardware options
The 32GB internal memory (by Monitoring Unit) enables up to 6 months of storage for logs, trends
(RF measured values) and TS stream recordings.
The internal GNSS receiver can provide an internal 1PPS reference clock signal necessary for
synchronization measurements (SFN Drift, Frequency Offset and Drift, Network Delay): 1PPS source
independent from the modulator for a reliable SFN synchronization measurement.
The EdgeProbe Advanced can also be equipped with an additional redundant power supply source.

1
*Feature unavailable in firmware version 4.1, contact us for availability

EdgeProbe Advanced - User Manual – 4.1 – 8 / 120

1.2 PC/LAPTOP MINIMUM REQUIREMENTS

TestTree EdgeProbe Advanced embeds a web server to provide a friendly and easy to use web based
Graphical User Interface (GUI). Only a web browser is needed to setup and monitor EdgeProbe
Advanced. It runs on Chrome, Mozilla and Internet Explorer web browsers.
The EdgeProbe Advanced GUI relies on FLASH technology; therefore, Adobe Flash Player shall be
installed prior using the application. Adobe Flash Player can be downloaded at the following address:
http://www.adobe.com/products/flashplayer
Minimum Requirements: Adobe Flash Player 11
Note: Web browsers tend to use as much memory as they can. It is therefore recommended to close the web
browsers' windows when they are not needed. As flash application offers rich user experience, any computer
with 512 MB RAM and at least PIV can run EdgeProbe Advanced GUI. The screen resolution should be set at
least to 1280x1024 pixels.

1.3 PACKING LIST

Before proceeding, please check that the box contains all of the following items:
• 1x EdgeProbe Advanced device
• 1x Power cable
• Quick Start installation guide

If any item is missing or has defects, do not install the device and contact our Technical Support team
via email support@test-tree.com.

EdgeProbe Advanced - User Manual – 4.1 – 9 / 120

2 WALK AROUND

2.1 FRONT PANEL

EdgeProbe Advanced offers a simple front panel with the following information:
Dual CI slot

LED: GNSS status LED:

- Power - Power
- Run - Run
- Unit 1 monitoring status - Unit 3 monitoring status
- Unit 2 monitoring status - Unit 4 monitoring status
- -
EdgeProbe Advanced Quad (4 monitoring Units) front panel contains: LED U1&U2, GNSS, LED U3&U4.
EdgeProbe Advanced Dual (2 monitoring Units) front panel contains: LED U1&U2, GNSS, inactive LED
U3&U4.
• 1x POWER led common for U1&U2 (or U3&U4):
o If the device is equipped with one Power Supply (“Redundant Power Supply” option
deactivated):
▪ LED is GREEN if the Power Supply operates properly
o If the device is equipped with two Power Supply Units (“Redundant Power Supply” option
activated):
▪ LED is GREEN if both Power Supplies operate properly
▪ LED turns ORANGE if one Power Supply stops functioning but the other Power Supply
operates properly
• 1x RUN led common for U1&U2 (or U3&U4):
o LED turns GREEN if both U1&U2 (or U3&U4) are ready to operate
o LED turns RED if at least one U1&U2 (or U3&U4) is not ready to operate
• 1x UNIT led:
o LED is GREEN when the equipment operates properly without any alarm
o LED turns ORANGE if at least one alarm (monitoring or device alarm) with Warning level is
currently raised
o LED turns RED if at least one alarm (monitoring or device alarm) with Critical level is
currently raised
o LED is OFF if the corresponding Unit is not ready to operate
• 1x GNSS led:
o If the device contains the “Internal GPS” option:
▪ LED is OFF if the device alarm “GNSS Signal Presence” is disabled
▪ If the “GNSS Signal Presence” is enabled:
• LED is GREEN the GPS receiver is locked. The internal 1PPS signal is generated
• LED turns RED if the GPS receiver is not locked. The internal 1PPS signal is not

EdgeProbe Advanced - User Manual – 4.1 – 10 / 120

 generated
o LED is OFF if the “InternalGPS” option is deactivated. The internal 1PPS signal is not
generated
• 2x DVB-CI slots: up to 2x CAM support, available if the “DualCiSlot” option is activated

2.2 REAR PANEL

The rear panel features all physical interfaces used to connect the EdgeProbe Advanced to the
network (for management: monitoring and configuration), and to process the incoming RF, ASI or IP
signal sources.
Depending on the Hardware options, the rear panel can contain 2 or 4 Monitoring Units (EdgeProbe
Advanced Dual or Quad):

•  Ground connector, 1PPS and 10MHz inputs (2x BNC female 50 Ω)

•  Monitoring Unit 3 and Unit 4 – optional
•  GNSS input, Monitoring Unit 1 and Unit 2
•  1x Power receptacle and 1x Optional Redundant Power receptacle (100-240VAC +/-
10%, 50/60Hz). The second Power supply is installed on the equipment if the
“RedundantPowerSupply” option is purchased.
• 1x HW trigger per chassis: common for all the Monitoring Units

EdgeProbe Advanced QUAD – rear panel detail:

Redundant Power

HW trigger PSU2 PSU1

   

IP Control & Reset U3&U4 IP Control & Reset U1&U2

EdgeProbe Advanced DUAL – rear panel detail:

Redundant Power
HW trigger
PSU2 PSU1

  

IP Control & Reset U1&U2

EdgeProbe Advanced - User Manual – 4.1 – 11 / 120

HW trigger1 dry relay detail:

Detail of Monitoring Unit 1 and Unit 2:

 Unit 2  Unit 1 

• Each Monitoring Unit 1  and Monitoring Unit 2  have:

o 1x RF input (N-type female 50 Ω or F-type 75 Ω) for receiving RF signals
o 1x ASI input/output (BNC female 75 Ω):
▪ Input of the MPEG-2 TS baseband signal to monitor
▪ Output of the monitored MPEG-2 TS: RF in to ASI out
o 1x Gigabit Ethernet DATA* interface (RJ45):
▪ Input of the MPEG-2 TS baseband signal to monitor
▪ Output of the monitored MPEG-2 TS: RF/ASI in to IP out
o 1x Optional HDMI output:
▪ Output one service of the monitored MPEG-2 TS
•  RESET,1x CONTROL Ethernet, 1x GNSS:
o 1x Gigabit Ethernet control interface (RJ45) for WEB GUI and SNMP access to Monitoring
Unit 1 and Unit 2
o 1x Reset button: press 3 or 15s for reset; after reset command press, the corresponding
Monitoring Unit LEDs will restart (light off/on)
▪ IP address reset: press 3 sec to reset the control and data IP address to the default
values:
• Control: U1 10.5.120.101/16, U2 10.5.120.102/16, U3 10.5.120.103/16, U3
10.5.120.104/16
• Data: U1 10.5.120.111/16, U2 10.5.120.112/16, U3 10.5.120.113/16, U3
10.5.120.114/16
▪ Factory reset: press 15 sec
o 1x Optional GNSS antenna input (SMA-type female - 50 Ω) for the internal GPS receiver
which can generate the 1PPS signal; the internal GPS receiver is installed on the

1 *HW trigger, TS over IP input monitoring features unavailable in firmware version 4.1, contact us for availability

EdgeProbe Advanced - User Manual – 4.1 – 12 / 120

 equipment if the “InternalGPS” option is purchased

Note: The EdgeProbe Advanced Quad is equipped with two Gigabit Ethernet control interfaces and two the
Reset buttons. Each pair Unit 1&Unit 2 and Unit 3&Unit4 has its own Gigabit Ethernet control interface and
Reset button.

2.3 WHERE TO PLACE THE PROBE AT THE TX SITE?

Connecting the EdgeProbe to its own off air antenna on the transmission site is not a good solution
because signal is not stable near the TX.
The RF cable feeding the EdgeProbe RF input may be connected:
- directly on the back of the transmitter where usually a directional coupler is placed, as seen in
the picture below:

- at the modulator’s “monitor” RF output

The EdgeProbe max supported input level is -5dBm.

EdgeProbe Advanced - User Manual – 4.1 – 13 / 120

3 QUICK START

3.1 FIRST EDGEPROBE CONNECTION

EdgeProbe GUI is web based. A PC must be connected directly or via a switch to the Gigabit Ethernet
Control interface of the EdgeProbe equipment.
Note: Each EdgeProbe Advanced monitoring unit has its own web GUI available at its specific IP address.

1. Use an Ethernet cable (RJ45 plug) to connect the EdgeProbe Advanced “IP Control” port
directly to a PC (or via a network switch).
2. Plug the power cable into the power receptacle on the back panel. Then, connect the other
end of the cable to main power. Allow the EdgeProbe Advanced 1’30’’ to initialize and start.
3. Once the front panel Run LED has turned GREEN, the EdgeProbe WEB GUI can be
accessed: each monitoring unit has its own IP control address and its own WEB GUI access.
4. By default, the EdgeProbe Advanced is configured with the following IP address:
• On Ethernet Control for unit 1, 2, 3 and 4:
o Unit 1: 10.5.120.101 / 255.255.0.0
o Unit 2: 10.5.120.102 / 255.255.0.0
o Unit 3: 10.5.120.103 / 255.255.0.0
o Unit 4: 10.5.120.104 / 255.255.0.0
• On Ethernet Data for unit 1, 2, 3 and 4:
o Unit 1: 10.5.120.111 / 255.255.0.0
o Unit 2: 10.5.120.112 / 255.255.0.0
o Unit 3: 10.5.120.113 / 255.255.0.0
o Unit 4: 10.5.120.114 / 255.255.0.0

5. Connect a PC to the EdgeProbe Advanced Control Ethernet interface (one Control interface
for Unit 1 and 2, a second Control interface for Unit 3 and 4) and set the IP address of the PC
to 10.5.x.y / 255.255.0.0.
6. Open a Web browser (Chrome or Firefox are recommended) in order to display the web-based
graphical user interface, using the control interface address: http://10.5.120.101 (or .102, .103,
.104)
7. As products embed a web server, no software needs to be installed on the PC except Adobe
Flash Player; the EdgeProbe web interface is based on Flash technology. Adobe Flash Player
can be downloaded at the following address: http://www.adobe.com/products/flashplayer
8. Once you are connected to the web interface, you can configure the device and the monitoring.
Please refer to the paragraph “4 Device settings” for the device configuration and to paragraph
“0
9. Note:
- TS maximum bitrate for recording: 65Mbps for DVB-S/S2, 50Mbps for DVB-T/2, 60Mbps for DVB-C2.

EdgeProbe Advanced - User Manual – 4.1 – 14 / 120

EdgeProbe Advanced - User Manual – 4.1 – 15 / 120
TS Manual Record Control via remote SNMP commands

The MIB OIDs indicated below must be used in order to control a TS recording.
All SET action on these OIDs are ignored if the “ExtendedMemory” option is disabled or if the Manual
Record Control mode is set to “EdgeProbe Web GUI” only.
An ongoing TS recording will be automatically stopped if the maximum allocated size for the TS record
files has been reached.

10. Configure monitoring” for the monitoring configuration.

testMonitoringLine > edgeprobe > configuration > recordConfig OIDs

L recordActivate boolean, read/write
L recordPrefix string, read/write
L recordAllocatedSpace integer, read/write
SET {1} -> 512MB, SET {2} -> 1GB, SET {3} -> 5GB
SET {4} -> 10GB, SET {5} -> max available space
F manualRecordControl
L manualRecordControlEdgeProbeGUI boolean, read/write
L manualRecordControlSNMP boolean, read/write
L manualRecordStartStop integer, write:
SET {1} -> stop TS recording, SET {2} -> start TS recording
L manualRecordDuration integer [seconds], read/write
SET {0} -> disable the Default Record Duration
SET {value > 0} -> enable the Default Record Duration and
automatically stop an ongoing TS recording after the configured
duration elapsed

EdgeProbe Advanced - User Manual – 4.1 – 16 / 120

3.2 GRAPHICAL USER INTERFACE

EdgeProbe Advanced GUI is user-focused, meaning TestTree strives to provide one straightforward
and easy to use application without any useless monitoring parameters.
The web interface is divided into 3 different parts:
• Menu selection (upper part) 
• Configuration/Monitoring (center part) 
• Status (lower part) 

3.2.1 MENU

The menu panel allows you to browse the different configuration and monitoring panels.

• Overview: this panel provides a summary of the status the monitored channels.
• Alarm View: this panel provides a detailed view of the status of monitored channels.
• Monitoring: this panel provides real-time display of measured parameters for the monitored
channel.
• Settings: this panel is intended for configuring the monitoring feature of the device (channels,
round robin channels list, RF threshold, …)
• Device: this panel is intended for configuring the device settings (IP address, …)
• Admin: enables user access management on the product
• About: this panel provides information on the device features: serial number, options, software
version…

EdgeProbe Advanced - User Manual – 4.1 – 17 / 120

3.2.2 CONFIGURATION AND MONITORING

The Configuration panels: Settings, Device, Admin, allow to define the channels to be monitored
and the threshold for the monitored parameters, as well as to configure the device’s connection and
monitored parameters. Refer to paragraphs “4 Device settings” and “0
Note:
- TS maximum bitrate for recording: 65Mbps for DVB-S/S2, 50Mbps for DVB-T/2, 60Mbps for DVB-C2.

EdgeProbe Advanced - User Manual – 4.1 – 18 / 120

TS Manual Record Control via remote SNMP commands

The MIB OIDs indicated below must be used in order to control a TS recording.
All SET action on these OIDs are ignored if the “ExtendedMemory” option is disabled or if the Manual
Record Control mode is set to “EdgeProbe Web GUI” only.
An ongoing TS recording will be automatically stopped if the maximum allocated size for the TS record
files has been reached.

Configure monitoring” for details about the configuration panels.

The Monitoring panels, Overview, Alarm View, Monitoring, present the analysis results. Refer to “6
Monitoring views” for details about the monitoring panels.
testMonitoringLine > edgeprobe > configuration > recordConfig OIDs
L recordActivate boolean, read/write
L recordPrefix string, read/write
L recordAllocatedSpace integer, read/write
SET {1} -> 512MB, SET {2} -> 1GB, SET {3} -> 5GB
SET {4} -> 10GB, SET {5} -> max available space
F manualRecordControl
L manualRecordControlEdgeProbeGUI boolean, read/write
L manualRecordControlSNMP boolean, read/write
L manualRecordStartStop integer, write:
SET {1} -> stop TS recording, SET {2} -> start TS recording
L manualRecordDuration integer [seconds], read/write
SET {0} -> disable the Default Record Duration
SET {value > 0} -> enable the Default Record Duration and
automatically stop an ongoing TS recording after the configured
duration elapsed

EdgeProbe Advanced - User Manual – 4.1 – 19 / 120

3.2.3 STATUS

The status bar gathers the status on the health of the device itself: internet connection, input status,
features state (enabled/disabled) …

    

 Activity & Time: provides indication on the activity of the EdgeProbe Advanced web connection
and local time on the device
 Input status: indicates the input used by the current monitoring task and the state of the input.
 Active tools: indicates which tools are enabled:
o TS over IP output forward,
o TS record,
o Monitoring mode: Round-robin or Single Channel
o System date/time synchronization
 Device Alarms: provides status of alarms specific to the device.
 Profile management: Allows loading and saving configuration of the device.

3.3 GETTING THE USER MANUAL

The User’s Manual provides detailed information on the configuration and monitoring provided by the
EdgeProbe Advanced. It can be accessed directly via the web GUI. To download the User’s Manual:
1. From the web GUI, select the “About” tab.

2. Click on the icon, this will open your default web browser and download the User Manual
on your computer.
The User Manual is also available on our Privileged Area website: http://privileged.enensys.com,
please refer to paragraph “10 Updates and Privileged Area” for details regarding the Privileged Area
website.

EdgeProbe Advanced - User Manual – 4.1 – 20 / 120

3.4 GETTING THE CURRENT FIRMWARE VERSION

The current name, location, serial number and firmware version of the EdgeProbe Advanced are
available in the “About” menu, in the “Information” box. Name and locations can be changed by the
operator.

3.5 INSTALLING A FIRMWARE UPGRADE

There are two possibilities for the EdgeProbe Advanced firmware upgrade:
• Via the GUI, “About” menu, “Device Update” tab
• Via FTP transfer of the update file
Note:
EdgeProbe Advanced Dual contains 2 monitoring Units  2 Units have to be upgraded.
EdgeProbe Advanced Quad contains 4 monitoring Units  4 Units have to be upgraded.
An eventual active stream record is automatically stopped if a firmware upgrade is performed.

3.5.1 WEB GUI UPGRADE

To upload a firmware upgrade file on one EdgeProbe Advanced monitoring Unit:

1. Go to the “About” menu.
2. Click “Select update” in the “Device update” box.
3. Select the appropriate *.upd file from the file selection dialog box.
4. Then click “Update”.
Please note that EdgeProbe Advanced reboots automatically at the end of the update process. If this
is not the case, the web browser window needs to be recharges (Ctrl + F5).

The latest firmware upgrade files are available on our Privileged Area website:
http://privileged.enensys.com, please refer to the paragraph “10 Updates and Privileged Area” for
details regarding the Privileged Area website.

3.5.2 FTP UPGRADE

To upload a firmware upgrade file on the EdgeProbe Advanced remotely via a FTP connection:
1. Open a FTP connection to the device (via FTP client applications such as FileZilla,
WinSCP,…):
• Host: IP address of the EdgeProbe monitoring unit to upgrade
• Username: updates
• Password: nn6
2. Copy the firmware upgrade file on the distant unit. The device will automatically detect the new

EdgeProbe Advanced - User Manual – 4.1 – 21 / 120

 firmware copy and start the upgrade. The upgrade process takes two to three minutes to
complete.
Note: While accessing the EdgeProbe Advanced via FTP, all web GUI manipulations are forbidden.

3.6 LOADING A DEVICE CONFIGURATION

The EdgeProbe Advanced configuration (input channels, alarm profiles, parameters thresholds) can
be saved in order to be reloaded on other devices. The configuration file does not contain the IP
address of the control & data interfaces.
In the bottom status bar, use the “Save Profile” button in order to save the *.conf file.

A configuration file (*.conf) can be loaded on the EdgeProbe Advanced in two manners:
1. Via the GUI, bottom status bar, “Load Profile” button:

2. Via FTP transfer of the configuration file:

• Open a FTP connection to the device:
▪ Host: IP address of the EdgeProbe monitoring unit to apply configuration on
▪ Username: profiles
▪ Password: nn6
• Copy the configuration file on the distant unit. The device will automatically detect the
new configuration file and apply it.

EdgeProbe Advanced - User Manual – 4.1 – 22 / 120

4 DEVICE SETTINGS

4.1 CONTROL IP ADDRESS

To setup the control IP address using the web interface:

1. Select the Device tab of the menu bar.

2. Change the IP address, Network Mask and Gateway parameters to match the IP configuration
you need and validate by clicking on the validation button (✓). You can also cancel your
modification by clicking on the cancel button ( ).

3. Before applying the modification, a confirmation message will be displayed.

Once the modification is done, the web browser will be reloaded automatically from the new IP
address. A popup will be displayed until this refresh occurs.

EdgeProbe Advanced - User Manual – 4.1 – 23 / 120

 4. Once your new setting is validated, you can test the new configuration by sending a Ping
request to other equipment.

The potential results are:

• “Ping OK: {X} ms”: the EdgeProbe Advanced has been able to ping the address,
response took {X} milliseconds be received
• “Timeout”: no response to the ping. There is no equipment at the specified IP address
or the IP configuration is not valid.
• “Error”: the IP address of the other equipment is not a valid IP address.

4.2 DATA IP ADDRESS1

To setup the data IP address using the web interface:

1. Select the Device tab of the menu bar.

2. Change the IP address, Network Mask, Gateway and negotiation parameters to match the
IP configuration you need and validate by clicking on the validation button (✓). You can
also cancel your modification by clicking on the cancel button ( ).
The IP data port of the EdgeProbe must be connected in the network containing the IP streams to be

1
*Feature unavailable in firmware version 4.1, contact us for availability

EdgeProbe Advanced - User Manual – 4.1 – 24 / 120

analyzed. The data IP address must be configured in the same subnetwork as the unicast/multicast
data streams.
Important note: the IP data and control should be configured in different networks. Configuring both data and
control on the same LAN might cause random connection loss behaviors: web GUI control, IP data streams,
NTP communication, SNMP trap receiver communication might be randomly routed between the two physical
control and data interfaces.

4.3 WEB GUI REFRESH PERIOD

To change the GUI Refresh period using the web interface

1. Select the Device tab of the menu bar.

2. Change the Refresh delay value and validate by clicking on the validation button (✓). You can
also cancel your modification by clicking on the cancel button ( ).

In order to reduce the bandwidth used for the EdgeProbe control, the refresh delay may be increased.

4.4 LOCAL DATE AND TIME

In order to log the date and time of events on your network, the EdgeProbe Advanced embeds an
internal Real-Time Clock (RTC) which is used for all scheduling, logs, statistical files and SNMP traps
timestamp. It is possible to use either the RTC time directly, either to synchronize the RTC with a NTP
(Network Time Protocol) server. The NTP server will ensure that all devices on your network will be
synchronized as well as the accuracy of the date and time.
Important note: the date and time value of the internal RTC are not saved when the EdgeProbe Advanced is
restarted (power off / power on cycle or product reboot).
Important note: for DVB-T2/ISDB-T/Tb SFN monitoring (RF SFN Drift, T2-MI Network Delay), the
EdgeProbe local date and time MUST be synchronized against a NTP server using a 1PPS reference
signal.

4.4.1 CHECKING THE CURRENT TIME CONFIGURATION

Information on current date and time and RTC settings are available in the status bar.

Time source and synchronization

Current date and time status

• Current date and time are displayed in the format: YYYY-MM-DD HH:MM:SS
• Time source is “NTP Server” or “System”
• When time source is NTP server, the status led at the right indicates:
o Green LED: NTP server has been reached and synchronization is done

EdgeProbe Advanced - User Manual – 4.1 – 25 / 120

 o Red LED: NTP server has not been reached or synchronization failed

4.4.2 SYSTEM DATE & TIME

To set the EdgeProbe Advanced with system date and time:

1. Open a web browser at the actual IP address of the
EdgeProbe Advanced (displayed on the front panel).
2. Select the Device tab of the menu bar.
3. Select “System” check box. Enter the date and time

or click the System Time button to

automatically retrieve the system time from the PC
accessing the GUI. Validate with ✓ button or cancel
with  button.

Note: Date is in the format YYYY/MM/DD

The icon presets the field Date and Time with the current time of the System

The icon opens a calendar to pick up the current date

4.4.3 NTP DATE & TIME

To set the EdgeProbe Advanced for NTP server

synchronization:
1. Open a web browser at the actual IP address of the
EdgeProbe Advanced (displayed on the front panel).

2. Select the Device tab of the menu bar.

3. Select “NTP” check box. Enter the NTP server IP

address, the polling interval and the Time Zone.
Validate with ✓ button or cancel with  button.

Important note: for DVB-T2/ISDB-T/Tb SFN monitoring (RF SFN Drift, T2-MI Network Delay), the
EdgeProbe local date and time MUST be synchronized against a NTP server using a 1PPS reference
signal.

EdgeProbe Advanced - User Manual – 4.1 – 26 / 120

4.5 SNMP NMS TRAP RECEIVER

EdgeProbe Advanced supports SNMP v1, v2, v2c

protocols for integration into a Network Monitoring
Systems. It is able to generate traps when an alarm is
raised. It needs to be configured with the trap receiver
IP address.
You can configure up to 5 traps receivers:
1. Open a web browser at the actual IP address
of the EdgeProbe Advanced.
2. Select the Device tab of the menu bar.
3. Select the trap receiver you want to configure
in the combo box.
4. Check the box to enable the selected trap
receiver.
5. Enter the IP address and the community string
of the trap receiver
a. The community string will be applied on
trap messages only
6. Select the SNMP type (V2C or V2V-INFORM).
7. Validate with ✓ button or cancel with  button.

EdgeProbe Advanced allows defining some common parameters for the trap receivers:
• Some parameters linked to the SNMP type V2C INFORM:
o The “Delay”: if the traps acknowledge is not received during this period, the trap is
repeated.
o The “Max repetitions”: maximum number of time the trap is repeated
• Heartbeat trap repetition: repetition period of the trap ALIVE.

4.6 REFERENCE CLOCK FOR SFN MONITORING

EdgeProbe Advanced provides synchronization measurement: SFN Drift, Frequency Offset and Drift.
The 1PPS and 10MHz reference signal sources can be configured in the web interface, via the Device
tab  Reference clock panel.

Three options are available:

- External PPS&10MHz:
o 1PPS source: 1PPS signal present at the device’s specific input
o 10MHz reference clock: 10MHz signal present at the device’s specific input
- External PPS:
o 1PPS source: 1PPS signal present at the device’s specific input
o 10MHz reference clock: signal generated by the EdgeProbe’s internal oscillator

EdgeProbe Advanced - User Manual – 4.1 – 27 / 120

 - Internal GNSS 1PPS (available if the “InternalGPS” option is activated):
o 1PPS source: 1PPS signal generated by the internal GNSS receiver
o 10MHz reference clock: signal generated by the EdgeProbe’s internal oscillator
Important note: for DVB-T2/ISDB-T/Tb SFN monitoring (RF SFN Drift, T2-MI Network Delay), the
EdgeProbe local date and time MUST be synchronized against a NTP server using a 1PPS reference
signal.

4.7 DEVICE ALARMS

EdgeProbe Advanced provides Device Alarms management. Eight device alarms are available:
- Temperature
- NTP Server
- External PPS Presence: presence of the 1PPS signal at the device’s specific input
- External 10MHz Presence: presence of the 10MHz signal at the device’s specific input.
- Internal GNSS 1PPS presence: presence of the 1PPS signal generated by the internal GNSS
receiver.
- GNSS signal presence: presence of the GNSS antenna signal at the device’s specific input,
and at least 4 satellites are in use. Alarm available only on Unit 1 and only if the “InternalGPS”
option is activated.
- Power Supply 1: available if the “RedundantPowerSupply” option is activated. Indicates if the
1st power supply is running.
- Power Supply 2: available if the “RedundantPowerSupply” option is activated. Indicates if the
2nd power supply is running.
It is possible, when an alarm is raised, to:
- record a log event describing the alarm
- generate a SNMP trap to a network monitoring system
Each alarm can be assigned a specific alarm level: “Critical”, “Warning”, “Info”. This level helps
filtering events in the log file.
To access the Devices Alarms management, select the “Device” tab of the Menu.

EdgeProbe Advanced - User Manual – 4.1 – 28 / 120

4.8 INTERNAL MEMORY MANAGEMENT

EdgeProbe Advanced provides Internal Memory Management functionalities if the

“ExtendedMemory” option is activated; which can be configured in the web interface, via the Device
tab  Memory Management panel.
Each EdgeProbe Advanced monitoring unit is equipped with a 32 GB storage, where three types of
files can be stored: logs, trends, TS records.
Logs files contain the list of events: alarm triggers on/off. Trends files contain the list of RF parameters
measured values. Records files contain the monitored MPEG-2 TS packets in a .ts file format.
Note:
- The file download is forbidden during a stream recording. The stream recording is also forbidden during
a file download.
- TS maximum bitrate for recording: 65Mbps for DVB-S/S2, 50Mbps for DVB-T/2, 60Mbps for DVB-C2.
- The stream record is automatically stopped if a firmware update is launched via the GUI.

EdgeProbe Advanced - User Manual – 4.1 – 29 / 120

4.8.1 LOG FILES CONFIGURATION

Log files contain the list of events: alarm triggers on/off. The Logs tab gives access to the log files
configuration:
- Activate/Deactivate logs storing.
- Prefix: custom prefix for the log file name:
o By default, log files are named:
log.[date_time].csv
o If “Prefix” is configured, the file name will be
[prefix]_log.[date_time].csv
- Allocated space: maximum storage allocated for the
logs files, up to 1 GB. When this limit is reached, the
logs recording is automatically stopped.
- File size max: maximum storage allocated for a
single logs file, up to 2 MB. When this limit is
reached, the current logs file is achieved and a new
one will be created.
- Day mode: a new logs file will be automatically
created at 00:00:00 upon date change.

4.8.2 TREND FILES CONFIGURATION

Trend files contain the list of RF parameters measured values. The Trends tab gives access to the
log files configuration:
- Activate/Deactivate trends storing.
- Prefix: custom prefix for the trend file name:
o By default, log files are named:
trend.[date_time].csv
o If “Prefix” is configured, the file name will be
[prefix]_trend.[date_time].csv
- Allocated space: maximum storage allocated for
the logs files, up to 1 GB. When this limit is
reached, the trends recording is automatically
stopped.
- File size max: maximum storage allocated for a
single trends file, up to 2 MB. When this limit is
reached, the current trends file is achieved and a
new one will be created.
- Record period: the RF parameters values will be
logged in the trends file every “record period”
interval.

Trend file size indication: o 1 week of trend file = 52.2 MB

- For 1 measure/second record period: - For 1 measure/min record period:
o 1 minute of trend file = 5.3 KB o 1 hour of trend file = 5.3 KB
o 1 hour of trend file = 318 KB o 1 day of trend file = 127 KB
o 1 day of trend file = 7.4 MB o 1 week of trend file = 895 KB

EdgeProbe Advanced - User Manual – 4.1 – 30 / 120

4.8.3 RECORD FILES CONFIGURATION

Record files contain the monitored MPEG-2 TS packets in a file format. The Records tab gives
access to the log files configuration:
- Activate/Deactivate recordings storing.
- Prefix: custom prefix for the record file name:
o By default, log files are named: record.[date_time].csv
o If “Prefix” is configured, the file name will be
▪ [prefix]_record.[date_time].csv
- Allocated space: maximum storage allocated for the
logs files. From 512MB up to 10GB or the entire
internal memory card’s capacity (30GB). When this
limit is reached, the TS recording is automatically
stopped.
- Currently used: indicates the memory space already
used by the exiting files.
- Manual Record Control: set the manner in which a
TS recording will be controlled (start/stop commands):
via the web GUI controls or via the SNMP commands.
o When “EdgeProbe GUI” enabled (default
setting): only the web GUI start/stop command
button will control a recording; all eventual
commands made via SNMP are ignored.
o When “Remote SNMP” enabled: only the
SNMP start/stop commands (SET the
corresponding OID) will control a recording;
the web GUI controls are disabled.
o When both “EdgeProbe GUI” and “Remote
SNMP” are enabled: a TS recording can be
controlled (start/stop) by both web GUI and
SNMP commands.
- Default Record Duration: an ongoing recording can be manually stopped via the web GUI
Stop control or via the SNMP (SET the corresponding OID), or can be automatically stopped
by the EdgeProbe after a user predefined duration of time
o Enable: the EdgeProbe will automatically stop the recording at the end of the
predefined duration of time after a record start.
o Duration: set the record duration (in seconds).

c/o ENENSYS Technologies Tel: +33 (0)1 70 72 51 70

6 rue de la Carrière Fax: +33 (0)2 99 36 03 84
CS 37734 sales@test-tree.com
35577 Cesson-Sévigné – France support@test-tree.com
TS Manual Record Control via the web GUI

The Record (TS Mode) button from the bottom status bar must be
used in order to control a TS recording.
This button is disabled if the “ExtendedMemory” option is disabled or if the Manual Record Control
mode is set to “Remote SNMP” only.
An ongoing TS recording will be automatically stopped if the maximum allocated size for the TS record
files has been reached.

Record command status

The “ExtendedMemory” option is disabled.
If the “ExtendedMemory” option is enabled: the records storing function is
deactivated or the Manual Record Control mode is set to “Remote SNMP”
only.

The “ExtendedMemory” option is enabled, the Manual Record Control >

“EdgeProbe web GUI” is enabled: a new TS recording can be started. Press
the button to start a TS recording.

The “ExtendedMemory” option is enabled, the Manual Record Control >

“EdgeProbe web GUI” is enabled: a TS recording is ongoing. Press the
button to stop the recording.

The “ExtendedMemory” option is enabled, the Manual Record Control >

“EdgeProbe web GUI” is enabled: the TS recording storage quota (max
allocated storage) has been reached. Change the Max allocated storage
limit or remove existing TS recordings in order to free the storage available
space.

Note:
- TS maximum bitrate for recording: 65Mbps for DVB-S/S2, 50Mbps for DVB-T/2, 60Mbps for DVB-C2.

EdgeProbe Advanced - User Manual – 4.1 – 32 / 120

TS Manual Record Control via remote SNMP commands

The MIB OIDs indicated below must be used in order to control a TS

recording.
All SET action on these OIDs are ignored if the “ExtendedMemory” option is disabled or if the Manual
Record Control mode is set to “EdgeProbe Web GUI” only.
An ongoing TS recording will be automatically stopped if the maximum allocated size for the TS record
files has been reached.

testMonitoringLine > edgeprobe > configuration > recordConfig OIDs

L recordActivate boolean, read/write
L recordPrefix string, read/write
L recordAllocatedSpace integer, read/write
SET {1} -> 512MB, SET {2} -> 1GB, SET {3} -> 5GB
SET {4} -> 10GB, SET {5} -> max available space
F manualRecordControl
L manualRecordControlEdgeProbeGUI boolean, read/write
L manualRecordControlSNMP boolean, read/write
L manualRecordStartStop integer, write:
SET {1} -> stop TS recording, SET {2} -> start TS recording
L manualRecordDuration integer [seconds], read/write
SET {0} -> disable the Default Record Duration
SET {value > 0} -> enable the Default Record Duration and
automatically stop an ongoing TS recording after the configured
duration elapsed

EdgeProbe Advanced - User Manual – 4.1 – 33 / 120

5 CONFIGURE MONITORING
EdgeProbe Advanced allows monitoring, in single channel or in multiple channel mode (sequential
round-robin), of:
- RF transmission signals: DVB-S/S2/S2X, DVB-T/T2, DVB-C/C2 and ISDB-T/Tb; (DVB-S2X:
contact us for availability support@test-tree.com)
- ASI MPEG-2 TS streams
- IP MPEG-2 TS streams (local or multicast IP address, VLAN support)
The configuration of channels, mode and alarm settings are available through the “Settings” tab of
the top menu.

This tab provides a sub-menu:

• Channel Management: settings for channels: list of channels, Scanning list for multiple
channels monitoring and selection of the channel monitoring mode.
• Alarm Profiles: settings for alarms: enable/disable alarms, thresholds, trap management,
relay management, log management.
• Output: enable/disable/configure the TS stream forward over IP output.
• Transcoding: configure the Transcoding functionality: Service extraction and audio/video
transcoding performed by the coupled TRANSBOX device.1
• General: choose the signal level measure unit: dBm or dBµV.

1 Transcoding function working on DVB-T/T2, DVB-C/C2, ISDB-T/Tb EdgeProbe Advanced. Contact us for availability
support@test-tree.com on DVB-S/S2/S2X EdgeProbe Advanced.

EdgeProbe Advanced - User Manual – 4.1 – 34 / 120

To setup a monitoring, you will have to:
1. Define the alarms that will be analyzed on the input signal: their threshold and behavior (trap
generation, logging, …):
• Settings  Alarm Profiles
2. Define the channel(s) to be monitored (RF signals, MPEG-2 TS baseband streams over ASI
or over IP inputs):
• Settings  Channel Management  Single channel Configuration
3. If applicable, define the list of channels of the Scanning feature (multiple channels can be
sequentially monitored in a Round-Robin mode):
• Settings  Channel Management  Multiple Channel Configuration
4. Define the monitoring mode (single channel or multiple channel (Round-Robin)) and start the
monitoring:
• Settings  Channel Management  Channel Selection
All these steps are described within the following paragraphs.

5.1 CONFIGURE ALARM PROFILES

EdgeProbe Advanced provides Alarm Profiles management. An alarm profile can be defined and
then associated to a channel for monitoring. EdgeProbe allows defining different alarm profiles (alarm
templates) for specific input channels.

Note: EdgeProbe Advanced supports up to 16 alarm profiles.

An alarm on EdgeProbe Advanced allows to monitor a parameter at RF or baseband level or content

level. It is possible, when an alarm is raised, to:
- record a log event describing the alarm,
- generate a SNMP trap to a network monitoring system,
Each alarm can be assigned a specific alarm level: “Critical”, “Warning” or “Info”. This level helps
filtering events in the log file.
To access the Alarm Profiles management, select the “Settings” tab of the Menu and then the “Alarm
Profiles” sub menu.

The Alarm Profiles view provides the “Profiles Management” tab, which allows the creation and
configuration of alarm templates. Each alarm profile (template) will allow setting up alarms for:

- RF - ETR 101 290 Priority 3 - SFN

- ASI - T2-MI - Echoes
- IP - BTS - Multiplex-Services
- ETR 101 290 Priority 1 - MIP - OneBeam
- ETR 101 290 Priority 2 - Advanced

EdgeProbe Advanced - User Manual – 4.1 – 35 / 120

Note: Depending on the monitored channel type (input type RF, ASI, IP, input standard), only the applicable
alarms are computed and displayed; in order to avoid raising non relevant alarms even if they are maybe active
in the profile that has been applied to the monitored channel.
For example, when monitoring an DVB-T2 RF signal, the ASI or IP related alarms are not applicable, therefore,
they will not be computed.

5.1.1 GENERAL ALARM SETTINGS

Each alarm managed by EdgeProbe Advanced has the following configuration options:
- “Display”: display the alarm in the “Alarm View” and show the related events in the “Logs
event” panel.
- “Trap”: if checked, a SNMP trap will be generated when the alarm is raised
- “RelayOut”: if checked, the dry relay will be driver when the alarm is raised (grayed because
not available in the current version)
- “Log Level”: defines the severity of the alarm (Info, Warning or Critical).

Note: The relay port is not present on the current EdgeProbe Advanced device. Please refer to the Support for
further information.

In the case of ETR 101 290, T2-MI, BTS and OneBeam monitoring, many errors can be detected
in a short period of time. In order to avoid flooding the Network Monitoring System with alarm on/off
traps, EdgeProbe Advanced provides an alarm trigger on occurrence mechanism, by using two
additional alarm parameters: “Nb Errors” and “Over Last”:
- An alarm will be raised (triggered ON) if an error occurred at least “Nb Errors” times during a
period of “Over Last”.
- An alarm will be triggered OFF if there is no more error during a period of “Over Last” seconds.

Please refer to the appendix paragraph “14.1 ETR alarms lifecycle” for detailed uses cases illustrating
the ETR alarms lifecycle.

c/o ENENSYS Technologies Tel: +33 (0)1 70 72 51 70

6 rue de la Carrière Fax: +33 (0)2 99 36 03 84
CS 37734 sales@test-tree.com
35577 Cesson-Sévigné – France support@test-tree.com
In the case of RF monitoring, the monitored signal can fluctuate around the threshold value, so many
errors can be raised during a short period. In order to prevent from flooding the Network Monitoring
System, EdgeProbe Advanced provides a Hysteresis mechanism:
- An alarm will go OFF if the monitored value’s is in the interval [min + Hysteresis value, max –
Hysteresis value].

All these parameters pertain to an “Alarm Profile”, so it is possible, for example, to enable SNMP trap
generation for a specific parameter in one profile and disable it in another profile.

Note: After any changes in the settings, do not forget to validate them or cancel them. Validate with ✓ button
or cancel with  button

EdgeProbe Advanced - User Manual – 4.1 – 37 / 120

5.1.2 RF ALARM SETTINGS

RF settings for an alarm profile are available through the RF tab of the Alarm Profiles.

Parameter Standard Description Range

Demod Locked all Status of the demodulation front-end. Locked Not applicable
means:
- a valid RF DTV signal is received
- Selected PLP is present
- MPEG-TS stream is successfully decoded
An alarm is raised if the status goes to unlocked.
MER mode DVB-T The MER measure for DVB-T can be computed in two modes:
- TX sites: when the EdgeProbe is installed on TX sites and the RF signal
comes from the modulator output
- Echoes: when the EdgeProbe is installed in reception sites with strong
echo conditions (multipath and destructive echoes), and the RF signal
comes from off-air antenna. This measure mode requires a 2 minutes
initialization period. Therefore if in Scanning (Round-robin) mode, the
scanning duration should be superior to two minutes.
Signal Level 1 (Gap) all Signal level variation of the RF signal compare to Expressed in dBm.
the “Reference Signal Level”.
Range: -6dBm to
An alarm is raised if the value goes below “min” +6dBm
settings or above “max” settings.
Symmetrical intervals
are not mandatory.
Signal Level 2 (Gap) all Signal level variation of the RF signal compare to Expressed in dBm.
the “Reference Signal Level”.
Range: -6dBm to
An alarm is raised if the value goes below “min” +6dBm
settings or above “max” settings. Typically used to
zoom in the fluctuation of the signal’s level. Symmetrical intervals
are not mandatory.
SNR All except Signal to Noise Ratio of the RF signal. Expressed in dB
DVB-
S/S2/S2X An alarm is raised if signal level goes below “min” Range: 0 to 40dB
settings.
CNR DVB- Carrier to Noise Ratio of the RF signal. Expressed in dB
S/S2/S2X
An alarm is raised if signal level goes below “min” Range: 0 to 40dB
settings.
MER 1 All except Modulation Error Rate of the RF signal. Expressed in dB
DVB-
S/S2/S2X An alarm is raised if the value goes below “min” Range: 0 to 42dB
settings or above “max” settings. Typical values for
a warning alarm.
MER 2 All except Modulation Error Rate of the RF signal. Expressed in dB
DVB-
S/S2/S2X An alarm is raised if the value goes below “min” Range: 0 to 42dB
settings or above “max” settings. Typical values for
a critical alarm.
Eb/N0 DVB- Eb/N0 of the RF signal. Expressed in dB
S/S2/S2X
An alarm is raised if signal level goes below “min”
settings.
Link Margin DVB- Link Margin of the RF signal. Expressed in dB
S/S2/S2X
An alarm is raised if signal level goes below “min”

EdgeProbe Advanced - User Manual – 4.1 – 38 / 120

 settings.
LDPC Iteration DVB-T2/C2 Number of iteration of the LDPC decoder. Expressed as a count
An alarm is raised if the value goes below “min” Range 0 to 100
settings or above “max” settings.
Experimental values
LDPC iteration depends on the hardware showed that a
implementation and cannot be compared to other maximum of 22
systems. iterations allows a
signal recovery. A
superior value results
in errors in the
transport stream.
Pre-LDPC BER DVB- Bit Error Rate before the LDPC correction.
T2/C2/S2
An alarm is raised if the value goes below “min”
settings or above “max” settings.
Post-LDPC BER DVB- Bit Error rate after the LDPC correction.
T2/C2/S2
An alarm is raised if the value goes below “min”
settings or above “max” settings.
This is also the BER before BCH.
Post-BCH FER DVB-T2/C2 Frame Error rate after the BCH correction.
An alarm is raised if the value goes below “min”
settings or above “max” settings.
PER DVB-S2 Packet Error rate after the BCH correction.
An alarm is raised if the value goes below “min”
settings or above “max” settings.
Pre-Viterbi BER DVB-T/S Bit Error Rate before the Viterbi correction.
An alarm is raised if the value goes below “min”
settings or above “max” settings.
Post-Viterbi BER DVB-T/C/S Bit Error Rate after the Viterbi correction.
An alarm is raised if the value goes below “min”
settings or above “max” settings.
This is also the BER before RS.
Post-RS PER DVB-T/C Packet Error Rate after RS correction.
An alarm is raised if the value goes below “min”
settings or above “max” settings.
Post-Viterbi BER ISDB-T/Tb Bit Error rate after the Viterbi correction.
Layer A
An alarm is raised if the value goes below “min”
settings or above “max” settings.
Post-Viterbi BER ISDB-T/Tb Bit Error rate after the Viterbi correction.
Layer B
An alarm is raised if the value goes below “min”
settings or above “max” settings.
Post-Viterbi BER ISDB-T/Tb Bit Error rate after the Viterbi correction.
Layer C
An alarm is raised if the value goes below “min”
settings or above “max” settings.
Post-RS PER DVB-T/C Packet Error rate after the RS correction.
An alarm is raised if the value goes below “min”
settings or above “max” settings.
Post-RS PER ISDB-T/Tb Packet Error rate after the RS correction.
An alarm is raised if the value goes below “min”

EdgeProbe Advanced - User Manual – 4.1 – 39 / 120

 Layer A settings or above “max” settings.
Post-RS PER ISDB-T/Tb Packet Error rate after the RS correction.
Layer B An alarm is raised if the value goes below “min”
settings or above “max” settings.
Post-RS PER ISDB-T/Tb Packet Error rate after the RS correction.
Layer C An alarm is raised if the value goes below “min”
settings or above “max” settings.
DC Constellation DVB-T Detects the MER degradation of the DC
Degradation component.
An alarm is raised if the DC MER degradation
(compared to the general MER) is superior to the
“max” setting.
DC MER degradation = general MER – MER of the
DC
This alarms allows to detect IQ mismatch behavior
that may arrive on modulators using direct
modulation mechanism.
Carrier Frequency DVB-T/T2, Drift of the central carrier frequency.
Drift ISDB-T/Tb
An alarm is raised if the value goes below “min”
settings or above “max” settings.

5.1.3 ASI INPUT SETTINGS

ASI settings for an alarm profile are available through the ASI tab of the Alarm Profiles.

Parameter Description Range

ASI sync Status of the ASI synchronization Not applicable
An alarm is raised if the ASI input is inactive.

5.1.4 IP INPUT SETTINGS*1

IP settings for an alarm profile are available through the IP tab of the Alarm Profiles.

Parameter Description Range

IP Input Data If IP input monitoring is activated, an alarm is raised if Not applicable
no data is received by the IP data port.

1
*Feature unavailable in firmware version 4.1, contact us for availability

EdgeProbe Advanced - User Manual – 4.1 – 40 / 120

5.1.5 ETR 101 290 PRIORITY 1 SETTINGS

ETR 101 290 Priority 1 settings for an alarm profile are available through the ETR1 tab of the Alarm
Profiles.
The parameters are expressed as <Number><Indicator> as defined in ETR 101 290 §5.2.1. Please,
refer to ETR 101 290 document for exact definition of the parameters. PDF file available here1.

Parameter Description Range

1.1 TS_sync_loss Loss of synchronization with consideration of Not applicable
hysteresis parameters
1.2 Sync_byte_error Sync_byte not equal 0x47 Not applicable
1.3 PAT_error_2 Program Association Table Repetition time in ms
PID 0x0000 does not occur at least every 0,5 s Range: 50 to 5000ms
a PID 0x0000 does not contain a table_id 0x00 ETR recommended value:
(i.e. a PAT) 500ms
Scrambling_control_field is not 00 for PID
0x0000
1.4 Continuity_count_error Incorrect packet order a packet occurs more Not applicable
than twice lost packet
1.5 PMT_error_2 Program Map Table Repetition time in ms
Sections with table_id 0x02, (i.e. a PMT), do not Range: 50 to 5000ms
occur at least every 0,5 s on each
program_map_PID which is referred to in the ETR recommended value:
PAT 500ms

Scrambling_control_field is not 00 for all

packets containing information of sections with
table_id 0x02 (i.e. a PMT) on each
program_map_PID which is referred to in the
PAT
1.6 PID_error Referred PID does not occur for a user specified Repetition time in ms
period
Range: 1000 to 80000ms
ETR recommended value:
1000ms

Please refer to the appendix paragraph “14.1 ETR alarms lifecycle” for detailed uses cases illustrating
the alarms lifecycle.

1 http://www.etsi.org/deliver/etsi_tr/101200_101299/101290/01.03.01_60/tr_101290v010301p.pdf

EdgeProbe Advanced - User Manual – 4.1 – 41 / 120

5.1.6 ETR 101 290 PRIORITY 2 SETTINGS

ETR 101 290 Priority 2 settings for an alarm profile are available through the ETR2 tab of the Alarm
Profiles.
The parameters are expressed as <Number><Indicator> as defined in ETR 101 290 §5.2.2. Please,
refer to ETR 101 290 document for exact definition of the parameters. PDF file available here1.

Parameter Description Range

2.1 Transport_error Transport_error_indicator in the TS-Header is Not applicable
set to "1"
2.2 CRC_error Cyclic Redundancy Check Not applicable
CRC error occurred in CAT, PAT, PMT, NIT, EIT,
BAT, SDT or TOT table
2.3a PCR_repetition_error Program Clock Reference Repetition time in ms
Time interval between two consecutive PCR Range: 0 to 5000ms
values more than 40 ms
ETR recommended value:
40ms
2.3b PCR_disc_indicator_error The difference between two consecutive PCR Repetition time in ms
values (PCRi+1 – PCRi) is outside the range of
0...100 ms without the discontinuity_ indicator Range: 0 to 10000ms
set ETR recommended value:
100ms
2.4 PCR_accuracy_error PCR accuracy of selected program is not within Repetition time in ms
±500 ns
Range: 0 to 50000ms
ETR recommended value:
500ms
2.6 CAT_error Conditional Association Table Not applicable
Packets with transport_scrambling_control not
00 present, but no section with table_id = 0x01
(i.e. a CAT) present
Section with table_id other than 0x01 (i.e. not a
CAT) found on PID 0x0001

Please refer to the appendix paragraph “14.1 ETR alarms lifecycle” for detailed uses cases illustrating
the alarms lifecycle.

1 http://www.etsi.org/deliver/etsi_tr/101200_101299/101290/01.03.01_60/tr_101290v010301p.pdf

EdgeProbe Advanced - User Manual – 4.1 – 42 / 120

5.1.7 ETR 101 290 PRIORITY 3 SETTINGS

ETR 101 290 Priority 3 settings for an alarm profile are available through the ETR3 tab of the Alarm
Profiles.
The parameters are expressed as <Number><Indicator> as defined in ETR 101 290 §5.2.3. Please,
refer to ETR 101 290 document for exact definition of the parameters. PDF file available here1.

Parameter Description Range

3.1.a NIT_actual_error Network Information Table Interval time in ms
Section with table_id other than 0x40 or 0x41 or Range: 0 to 100ms for min
0x72 (i.e. not an NIT or ST) found on PID and 1000 to 30000ms for max
0x0010.
ETR recommended value:
No section with table_id 0x40 (i.e. an 25ms for min and 10000ms
NIT_actual) in PID value 0x0010 for more than for max
10 s.
Any two sections with table_id = 0x40
(NIT_actual) occur on PID 0x0010 within a
specified value (25 ms or lower).
3.1.b NIT_other_error Interval between sections with the same Interval time in ms
section_number and table_id = 0x41
(NIT_other) on PID 0x0010 longer than a Range: 1000 to 30000ms for
specified value (10 s or higher). max
ETR recommended value: is
10000ms for max
3.2 SI_repetition_error Repetition rate of SI tables outside of specified limits. The SI tables taken into
consideration: all the SI tables mentioned in the ETR3 alarm configuration menu,
plus the following:
- NIT other min error: range: 0 to 100ms, ETR recommended value is 25ms
- SDT other min error: range: 0 to 100ms, ETR recommended value is 25ms
- EIT other PF min error: range: 0 to 100ms, ETR recommended value is
25ms
- TOT error: range: 0 to 120000ms for min and 5000 to 120000ms for max,
ETR recommended value: 25ms for min and 30000ms for max
- BAT error: range: 0 to 50000ms for min and 2000 to 50000ms for max, ETR
recommended value: 25ms for min and 10000ms for max
- CAT max error: range: 100 to 100000ms, ETR recommended value is
10000
- PMT min error: range: 0 to 100ms, ETR recommended value is 25ms
3.4 Unreferenced_PID PID (other than PAT, CAT, CAT_PIDs, Interval time in ms
PMT_PIDs, NIT_PID, SDT_PID, TDT_PID,
EIT_PID, RST_PID, reserved_for_future_use Range: 400 to 1000ms for
PIDs, or PIDs user defined as private data max
streams) not referred to by a PMT within 0,5 s ETR recommended value: is
500ms for max
3.5.a SDT_actual_error Service Description Table Repetition time in ms
Sections with table_id = 0x42 (SDT, actual TS) Range: 0 to 100ms for min
not present on PID 0x0011 for more than 2 s. and 500 to 30000ms for max
Sections with table_ids other than 0x42, 0x46, ETR recommended value:
0x4A or 0x72 found on PID 0x0011. 25ms for min and 2000ms for

1 http://www.etsi.org/deliver/etsi_tr/101200_101299/101290/01.03.01_60/tr_101290v010301p.pdf

EdgeProbe Advanced - User Manual – 4.1 – 43 / 120

 Any two sections with table_id = 0x42 max
(SDT_actual) occur on PID 0x0011 within a
specified value (25 ms or lower)
3.5.b SDT_other_error Interval between sections with the same Interval time in ms
section_number and table_id = 0x46 (SDT, other
TS) on PID 0x0011 longer than a specified value Range: 1000 to 30000ms for
(10s or higher). max
ETR recommended value: is
10000ms for max
3.6.a EIT_actual_error Event Information Table Repetition time in ms
Section '0' with table_id = 0x4E (EIT-P, actual TS) Range: 0 to 100ms for min
not present on PID 0x0012 for more than 2 s and 500 to 30000ms for max
Section '1' with table_id = 0x4E (EIT-F, actual TS) ETR recommended value:
not present on PID 0x0012 for more than 2 s 25ms for min and 2000ms for
max
Sections with table_ids other than in the range
0x4E - 0x6F or 0x72 found on PID 0x0012.
Any two sections with table_id = 0x4E (EIT-P/F,
actual TS) occur on PID 0x0012 within a
specified value (25ms or lower).
3.6.b EIT_other_error Interval between sections '0' with table_id = 0x4F (EIT-P, other TS) on PID 0x0012
longer than a specified value (10s or higher);
- EIT_P max repetition: range: 100 to 100000ms, ETR recommended value
is 10000
Interval between sections '1' with table_id = 0x4F (EIT-F, other TS) on PID
0x0012 longer than a specified value (10s or higher)
- EIT_F max repetition: range: 100 to 100000ms, ETR recommended value
is 10000
3.7 RST_error Running Status Table Repetition time in ms
Sections with table_id other than 0x71 or 0x72 Range: 0 to 100ms for min
found on PID 0x0013.
ETR recommended value is
Any two sections with table_id = 0x71 (RST) 25ms
occur on PID 0x0013 within a specified value (25
ms or lower).
3.8 TDT_error Time and Date Table Repetition time in ms
Sections with table_id = 0x70 (TDT) not present Range: 0 to 100ms for min
on PID 0x0014 for more than 30 s and 500 to 120000ms for max
Sections with table_id other than 0x70, 0x72 ETR recommended value:
(ST) or 0x73 (TOT) found on PID 0x0014. 25ms for min and 30000ms
for max
Any two sections with table_id = 0x70 (TDT)
occur on PID 0x0014 within a specified value (25
ms or lower).

Check the appendix paragraph “14.1 ETR alarms lifecycle” for detailed uses cases illustrating the
alarms lifecycle.

EdgeProbe Advanced - User Manual – 4.1 – 44 / 120

5.1.8 BTS SETTINGS*1

BTS settings for an alarm profile are available through the BTS tab of the Alarm Profiles.

Parameter Description
Enable BTS Analysis Enable or Disable the BTS analysis
IIP Timing This alarm is checked when in SFN network only:
network_synchronization_information.
synchronization_id = 0
An alarm is raised if the successive IIP Packet timestamps are not self-consistent.
IIP Structure TS Error For each IIP transport packet (carried on PID 0x1FF0) in the transport stream, the
following checks are performed:
- The transport_packet_header should comply with TS 101 191 [i.14] clause 6,
table 1,and ISO/IEC 13818-1 [i.1] clause 2.4.3.2, tables 2 and 3
- The synchronization_time_stamp and the maximum_delay should be in the
range of 0x0 to 0x98967F
- The CRC_32 field should match the CRC calculated for the MIP data
If at least one of these conditions is not fulfilled, an alarm is raised.
IIP Presence Extra The IIP Presence alarm check that the IIP is inserted into the transport stream only
once per multiplex frame.
An IIP Presence Extra alarm is raised if the IIP is inserted into the transport stream
more than once per multiplex frame.
IIP Presence Missing The IIP Presence alarm check that the IIP is inserted into the transport stream only
once per multiplex frame.
An IIP Presence Missing alarm is raised if no IIP is found in one multiplex frame.
IIP Continuity Error An alarm is raised if a discontinuity is detected on the TMCC TSP_counter value.
The check takes into consideration the following points:
- Comparison of the decoded TSP_counter value of the received TSP with the
TSP_counter value of the previous TSP
- The case of receiving the first TSP of a transmission, for which no specific
TSP_counter value is required
- The case of start of the multiplex frame, for which TSP_counter value is 0
IIP TMCC Packet Count Error An alarm is raised if an inconsistency is detected between the multiplex frame size
computed from IIP and the multiplex frame size counted using the TSP counter.
IIP TMCC Layer Packet Count An alarm is raised if an inconsistency is detected between the TS packet count for a
Error layer in a multiplex frame and the TS packet number for a layer computed from IIP
parameters.

1
*Feature unavailable in firmware version 4.1, contact us for availability

EdgeProbe Advanced - User Manual – 4.1 – 45 / 120

5.1.9 T2-MI SETTINGS

T2-MI settings for an alarm profile are available through the T2-MI tab of the Alarm Profiles.
Please, refer to ETR 101 290 document for exact definition of the parameters. PDF file available
here1.

Parameter Description
Enable T2-MI Analysis Enable or Disable the T2-MI analysis
Enable analysis on PLP ID Enable the PLP extraction, and indicate the ID of the PLP to monitor: both the
T2-MI encapsulation (T2-MI alarms below) and the extracted PLP TS (ETR1/2/3)
will be monitored.
If the PLP extraction is active, and the IP forward (IP output) is also enabled, the
output TS is the extracted PLP TS; otherwise the output TS is the entire T2-MI.
Auto extract from PSI tables Extract automatically the T2-MI PID from the PSI tables or indicate the T2-MI PID
Extract T2-MI PID info (in decimal) number.
T2MI valid This alarm is raised if no stream is received, or a non-valid T2-MI stream (no BB
frames) is received.
T2MI PLP missing If PLP extraction is activated, this alarm will raise if the indicated PLP ID is not
found in the input T2-MI.
T2MI packet count This error indicates a discontinuity of T2-MI packets.
Comparison of the decoded packet_count value of the received T2-MI packet
with the packet_count value of the previous packet.
Incorrect packet order, a packet occurs more than twice, lost packet.
T2MI CRC The CRC32 check indicates if the content of the respective T2-MI packet is
corrupted.
It is calculated across all other bits in the packet (both header and payload plus
any padding).
T2MI packet type T2MI_packet_type_error_1
Two of the various packet types are mandatory for each T2 frame: L1-current
data, DVB-T2 Timestamp.
If L1 repetition, in-band signalling (IBS) or Time-Frequency-Slicing (TFS) is
indicated in the L1-current data, an L1-future packet should also be present.
If any of these packet_type is not present in each T2 frame, a
T2MI_packet_type_error_1 is signalled.
T2MI packet payload The number of BB-frames (packet_type 0x00) relating to a PLP in a given T2
frame should match the value of PLP_NUM_BLOCKS signalled in the dynamic
signalling of both the L1-current and L1-future (when present).
The signalled values of frame_idx and superframe_idx for BB-frame packets
should be consistent with the time interleaver parameters specified in the
configurable signalling of the L1-current.
T2MI payload The T2MI_payload_error is signalled if the decoded plp_id in T2-MI packets with
packet_type 0016 is not included in the list (L1 post_signalling/ configurable) of
plp_id for the T2-MI signal.
Comparison of the decoded plp_id of T2-MI packets with packet_type 0016 with
list of possible values.

1 http://www.etsi.org/deliver/etsi_tr/101200_101299/101290/01.03.01_60/tr_101290v010301p.pdf

EdgeProbe Advanced - User Manual – 4.1 – 46 / 120

 T2MI frame length The T2 frame length derived from parameters signalled in L1 is not longer than
250 ms.
The error is indicated if the T2 frame length derived from L1 signalling
parameters is over 250 ms.
T2MI transmission order The T2MI_transmission_order_error is signalled if the packet_types are in a
wrong ordering and position inside a T2 frame.
T2MI DVB-T2 Timestamp The T2MI_DVB-T2_Timestamp_error signals a wrong timestamp inside a
superframe.
The T2MI_DVB-T2_Timestamp_error is signalled if at least one T2_timestamp
has a different value than the other DVB-T2 timestamp inside a single
superframe_(superframe_idx).
T2MI DVB-T2 Timestamp The T2MI_DVB-T2_Timestamp_discontinuity signals a non-increasing timestamp
discontinuity (not relevant with null timestamps).
The T2-MI timestamps are compared for subsequent superframes and the error
is indicated if the difference is not equal to the duration of the superframe.
T2 Stream consistency The T2MI_DVB-T2_Signalling_consistency_error signals an error in the
consistency of T2- MI packets.
The error is indicated if one or more of the following conditions are met:
• Illegal parameter combinations for PP, FFT size and guard interval in SISO or
MISO mode are signaled
• ISSY is not enabled when it should be
• Superframe does not include minimum of 2 T2 frames

5.1.10 MIP SETTINGS

MIP (Megaframe Initialization Packet) settings for an alarm profile are available through the MIP tab
of the Alarm Profiles.

Parameter Description Range

MIP Presence Check that the MIP packet is inserted into the Not applicable
transport stream only once per megaframe.
Applicable for DVB-T/T2 RF input signals
monitoring.

EdgeProbe Advanced - User Manual – 4.1 – 47 / 120

5.1.11 ADVANCED SETTINGS

Advanced settings (Quality of Service parameters) for an alarm profile are available through the
Advanced tab of the Alarm Profiles.
The purpose of the Service_Availability_Error (SAE) parameter is to identify severe distortions and
interruptions of the service under certain receiving conditions. This parameter is related to loss of
service.
Service Availability Errors (SAE): Count the number of errors for the following parameters over a
defined time interval Delta Τ: TS_sync_loss, PAT_error, PMT_error.
The purpose of the Service_Degradation_Error (SDE) parameter is to identify severe degradation
under certain receiving conditions. This parameter is related to the level of strong impairments to the
service.
Service Degradation Errors (SDE): Count the number of errors for the following parameters over a
defined time interval Delta Τ: CRC_error, PCR_error, NIT_error, SDT_error.
These parameters are defined in ETR 101 290 §5.5.1 and §5.5.2. Please, refer to ETR 101 290
document for exact definition of the parameters; PDF file available here1, or to the appendix paragraph
“14.4 QoS monitoring parameters”.
Parameter Description Range
SAE_R The Service_Availability_Error_Ratio is Range: 0 to 100%
calculated as the percentage of time for which
the SAE exceeds a pre-defined threshold.
SDE_R The Service_Degradation_Error_Ratio is Range: 0 to 100%
calculated as the percentage of time for which
the parameter exceeds a pre-defined threshold.
SAE_T SAE pre-defined threshold. Range: 0 to 600
SDE_T SDE pre-defined threshold. Range: 0 to 600

http://www.etsi.org/deliver/etsi_tr/101200_101299/101290/01.02.01_60/tr_101290v010201p.
pdf

EdgeProbe Advanced - User Manual – 4.1 – 48 / 120

5.1.12 SFN SETTINGS

SFN synchronization settings for an alarm profile are available through the SFN tab of the Alarm
Profiles. The SFN synchronization measurement detects the RF transmission time synchronization,
which is crucial in SFN transmission networks.
Also, the network delay can also be measured for a T2-MI TS over ASI input monitoring (both relative
and absolute T2-MI timestamp methods).
Parameter Description Range
DVB-T over RF input
Reference delay Expected (known) delay of the RF frame Range: -9 999 999.9 to
transmission. 9 999 999.9 µs
SFN Drift The RF frame transmission delay (SFN Delay) Range: -500 to 500 µs
is computed as the difference between the
actual transmission time and the transmission
time indicated in the MIP packet.
An alarm is raised if the SFN Drift (drift of the
SFN Delay) value goes below the min or above
the max value.
DVB-T2/ISDB-T/Tb over RF input
SFN Drift The SFN Drift is computed as the difference Range: -500 to 500 µs
between the actual transmission time (of the RF
frame) and the theoretical transmission time
(deterministic value, as dependent on the RF
frame duration, therefore dependent on the RF
modulation parameters).
An alarm is raised if the SFN Drift value goes
below the min or above the max value.
T2-MI TS over ASI input
Maximum Network Delay (MND) The network MND configured on the T2GW Range: 0 to 60000 ms, default
value 1000ms
Time offset May be used for relative timestamp systems, Range: 0 to 99 s, default
where the MND and the T2-MI timestamp values value 0s
are relative to the 1PPS signal. Time offset is a
known network delay exceeding 1s (multiple of
1s)
Network delay The measured Network delay for the T2-MI Range: 0 to 60000 ms
packets, computed as the difference between
the actual reception time and the T2GW
emission time (computed based on the T2-MI
timestamp and MND information).
An alarm is raised if the measured Network
delay value goes below the min or above the
max value.

Please refer to the appendix paragraph “14.3 SFN synchronization measurement” for details
concerning the SFN synchronization mechanism and measurements.
Note: For DVB-T2 only, the T2-Frame drift measurement is not valid if FEF frames are present in the T2 stream.
Important note: for DVB-T2/ISDB-T/Tb SFN monitoring (RF SFN Drift, T2-MI Network Delay), the
EdgeProbe local date and time MUST be synchronized against a NTP server using a 1PPS reference
signal.

EdgeProbe Advanced - User Manual – 4.1 – 49 / 120

5.1.13 ECHOES SETTINGS

The Channel Impulse Response monitoring applies for DVB-T/T2 and ISDB-T/Tb RF input signals.
Channel Impulse Response settings for an alarm profile are available through the Echoes tab of the
Alarm Profiles.

Parameter Description
Enable Echoes Analysis Enable or Disable the Echoes analysis
Echo values An alarm is raised if at least one echo is detected outside of the defined echoes
parameters: level, delay.
Echoes list Echoes list for which the presence should be tested. One echo is defined by:
- Index
- Signal level (in dB)
- Signal Gap and Hysteresis
- Delay (in µs)
- Delay Gap and Hysteresis
- Name
Signal Gap and Hysteresis, Delay Gap and Hysteresis are fixed values, the same for all
defined echoes.
Up to 15 echoes can be monitored.
An alarm is raised if at least one of the configured echoes to monitor exceeds the
predefined thresholds (signal level gap, delay, TII identification)
During the time the alarm state is ON, other echoes to monitor might be in error (eg: a
second Echo goes out of its monitoring thresholds; an Echo comes back in the alarming
thresholds but another one is missing…), therefore, each time another echo is in error,
the alarm counter is increased +1, and a trap is sent to the NMs (if “trap” enabled).

The alarm Echo list can also be set via the Monitoring -> Echoes menu, by clicking on the respec-
tive echoes displayed in the Echoes graph. Please refer to paragraph “6.3.4 Echoes” for further de-
tails.

5.1.14 MULTIPLEX-SERVICES SETTINGS

Multiplex-Services settings for an alarm profile are available through the Multiplex-Services tab of
the Alarm Profiles.

Parameter Description Range

Multiplex name Name of Multiplex. Not applicable
TS Id Presence An alarm is raised if the TS id value the TS Id of the input stream. Range: 0 to 65 535
Services Missing Duration of the Service Missing test. Range: 0 to 9s
An alarm is raised if at least one of the configured Sid is not detected
in the input stream during the predefined duration of time.
During the time the alarm state is ON, other Services to monitor
might be in error (eg: a second Service goes missing; a missing
Service is detected but another one is missing…), therefore, each
time another Service is in error, the alarm counter is increased +1,
and a trap is sent to the NMS (if “trap” enabled).

EdgeProbe Advanced - User Manual – 4.1 – 50 / 120

 Service list Service ID list for which the presence should be tested Range: 1 to 65 535
PIDs Missing Duration of the PIDs Missing test. Range: 0 to 9s
An alarm is raised if at least one of the configured PID numbers is not
detected in the input stream during the predefined duration of time.
During the time the alarm state is ON, other PIDs to monitor might be
in error (eg: a second PID goes missing; a missing PID is detected
but another one is missing…), therefore, each time another PID is in
error, the alarm counter is increased +1, and a trap is sent to the
NMS (if “trap” enabled).
PID list PID number list for which the presence should be tested Range: 0 to 8161
Unscrambling An alarm is raised if at least one Video PID is in scrambled state Not applicable
while its TS signalization indicates unscrambled state
(transport_scrambling_control = 0).

5.1.15 ONEBEAM SETTINGS

OneBeam is an ENENSYS proprietary solution enabling to share the satellite link for both DTH and
DTV distribution. OneBeam technical solution consists in inserting specific DTV distribution
information in specific PIDs of the DTH signal:
- T2-MI Marker PID: containing information that will enable the T2-MI reconstruction on the
transmission site (DTH reception site)
- In-Band PID: containing information on the PLP and service structure of the T2 multiplex that
is recreated on the transmission site (DTH reception site); used in case different TX sites need
to recreate T2 multiplex with different service and/or PLP structure
OneBeam settings for an alarm profile are available through the OneBeam tab of the Alarm Profiles.

Parameter Description
Enable T2-MI Analysis Enable or Disable the T2-MI analysis
T2-MI Marker PID Indicate the number of the PID containing the OneBeam information necessary
to recreate the T2-MI stream.
In Band PID Indicate the number of the PID containing the OneBeam information necessary
to recreate the T2 multiplex structure (PLP and services).
T2-MI Marker PID Presence This alarm checks the presence of the T2-MI marker component. An alarm is
raised if the T2-MI Marker PID is missing from the input stream.
T2-MI Marker PID Continuity This alarm has a similar behavior than the ETR 101 290 1.4
Counter Continuity_count_error, but focused on the T2-MI Marker.
T2 Frame Delimiter Consistency This alarm checks that the current bitrate (at the input of the T2Edge DTH) is the
same as the output bitrate of T2Gateway-DTH.This verifies if the satellite
modulator has added stuffing packets which could alter the behavior of the
T2EdgeDTH.
T2 Frame Consistency This alarm checks that T2 frame delimiter is present for each T2 frame. This
allows checking if all necessary information is available to rebuild the T2MI
stream at the TX site.
In-Band PID Missing This alarm checks the presence of the In-Band PID. An alarm is raised if the In-
Band PID is missing from the input stream.

5.1.16 EWS SETTINGS

EdgeProbe Advanced - User Manual – 4.1 – 51 / 120

EWS (Emergency Warning System) settings for an alarm profile are available through the EWS tab
of the Profile Configuration.

Feature not yet available. Please contact the Support team for further information, support@test-
tree.com.

EdgeProbe Advanced - User Manual – 4.1 – 52 / 120

5.2 CONFIGURE CHANNELS

To access the Channels Settings management, select the “Settings” tab of the Menu and then the
“Channel Management” sub menu.

The Channel Management panel provides:

- Single Channel Configuration  for creating the list of channels and their parameters
- Multiple Channel Configuration  for defining the list of channels for the Scanning feature
- Channel Selection  for selecting the monitoring mode; Scanning or single channel moni-
toring




EdgeProbe Advanced - User Manual – 4.1 – 53 / 120

5.2.1 MANAGING CHANNELS

The EdgeProbe Advanced can monitor the following type of input channels:
- RF input channels of type DVB-S, DVB-S2, DVB-T, DVB-T2, DVB-C, DVB-C2, ISDB-T/Tb;
contact us for DVB-S2X availability support@test-tree.com
- IP input channels
- ASI input channels

Note: The EdgeProbe support LNB control and powering over the RF input connector.

A DVB-S RF channel is defined by the following parameters:

• Name
• Satellite Frequency (MHz)
• LNB Frequency (MHz)
• Symbol Rate (MBd)
• Band (Low or High)
• Polarization (Horizontal or Vertical)
• Reference Signal Level
• Profile (alarm template)
• Description

A DVB-S2 RF channel is defined by the following parameters:

• Name
• Satellite Frequency (MHz)
• LNB Frequency (MHz)
• ISI Id
• Symbol Rate (MBd)
• Band (Low or High)
• Polarization (Horizontal or Vertical)
• PLS (None, Root, Gold)
• PLS code (code for Root, nb iterations for Gold)
• Reference Signal Level
• Profile (alarm template)
• Description
Note: If there are multiple Streams in the DVB-S2 RF signal, a channel must be defined for each Stream.

A DVB-T RF channel is defined by the following parameters:

• Name
• Frequency (between 50 and 900 MHz)
• Bandwidth (6, 7 or 8 MHz)
• Reference Signal Level
• Hierarchical Mode
• Profile (alarm template)
• Description

EdgeProbe Advanced - User Manual – 4.1 – 54 / 120

A DVB-T2 RF channel is defined by the following parameters:
• Name
• Frequency (between 50 and 900 MHz)
• Bandwidth (1.7, 6, 7 or 8 MHz)
• Reference Signal Level
• PLP Id
• T2 Profile (T2-Base, T2-Lite)
• Profile (alarm template)
• Description
Note: If there are multiple PLPs in the DVB-T2 RF signal, a channel must be defined for each PLP.

A DVB-C RF channel is defined by the following parameters:

• Name
• Frequency (between 42 and 1002 MHz)
• Bandwidth (8 MHz)
• Reference Signal Level
• Profile (alarm template)
• Description

A DVB-C2 RF channel is defined by the following parameters:

• Name
• Frequency (between 42 and 1002 MHz)
• Bandwidth (6 or 8 MHz)
• Reference Signal Level
• PLP Id
• Profile (alarm template)
• Description
Note: If there are multiple PLPs in the DVB-C2 RF signal, a channel must be defined for each PLP.

EdgeProbe Advanced - User Manual – 4.1 – 55 / 120

An ISDB-T/Tb RF channel is defined by the following parameters:
• TS type: ISDB-T or ISDb-Tb
• Name
• Frequency (between 50 and 900 MHz)
• Bandwidth (6, 7 or 8 MHz)
• Reference Signal Level
• Profile (alarm template)
• Description

An *1IP MPEG-2 TS channel is defined by the following parameters:

• Name
• Type of IP address (local or multicast)
• IP address
• Port
• VLAN presence
• VLAN ID
• Profile (alarm template)
• Description
Note: The IP data port of the EdgeProbe must be connected in the network containing the IP streams to be
analyzed. The data IP address must be configured in the same subnetwork as the unicast/multicast data
streams.

No particular configuration is required for an ASI channel. For each ASI channel, an alarm profile
should be provided.

5.2.1.1 CREATE A NEW CHANNEL(S)

Example with a DVB-T2 channel:

1. Click on the icon to create a new entry
2. Enter the parameters of the channel
Name: user defined name of the channel. This name will be used as an identifier of the channel
in the GUI
Frequency: frequency in MHz of the channel (resolution is 1Hz). For example “626” or
“626.166”
Bandwidth: bandwidth of the channel. Possible values are 6, 7 and 8MHz.
Reference Signal Level: expected signal level value (possibility to adjust it later on the
monitoring panel)
Plp Id: the Physical Layer Pipe you want to monitor.
Profile: alarm profile previously defined (see §5.1)
Description: user defined text
3. Restart to step 0 if you want to create another channel else go to next step
4. Validate with ✓ button or cancel with  button

1
*Feature unavailable in firmware version 4.1, contact us for availability

EdgeProbe Advanced - User Manual – 4.1 – 56 / 120

5.2.1.2 MODIFY EXISTING CHANNELS

1. Modify the wanted parameter(s) of the channel(s)

2. Validate with ✓ button or cancel with  button

Note: when a parameter of a channel is modified, EdgeProbe Advanced restart the monitoring process, even if
Scanning mode is used.

5.2.1.3 DELETING EXISTING CHANNELS

1. Select the channel you want to delete

2. Click on the icon to delete the channel
3. Restart to step 1 if you want to delete another channel else go to next step
4. Validate with ✓ button or cancel with  button

Note: if you delete a channel used in Scanning, the channel will also be deleted from the Scanning list and the
monitoring will be restarted.

EdgeProbe Advanced - User Manual – 4.1 – 57 / 120

5.2.2 CREATING SCANNING LIST

Scanning provides a round-robin scan of different channels with a single unit. Scanning configuration
is available in the “Settings” tab of the Menu and the “Channel Management” sub menu.
Note: Before defining a Scanning list, it is necessary to define all channels (refer to §5.2.1)

5.2.2.1 ADDING CHANNEL(S) TO THE SCANNING LIST

1. Click on the icon to create a new entry

2. Select the channel name using the combo box
3. Define the duration (in seconds) of the monitoring for this channel
4. Restart to step 0 if you want to add another channel else go to next step
5. Validate with ✓ button or cancel with  button

EdgeProbe Advanced - User Manual – 4.1 – 58 / 120

The scanning duration must have a minimum value, which depends on the analysis type:
Alarm
RF & Multiplex ETR Base ETR Advanced (QoS)
Bitrate
DTT and high bitrate 12s 27s 1m10s
Low bitrate 22s 37s 1m20s

Please refer to the appendix paragraph “14.2 Scanning recommendations” for details regarding the
recommended scanning durations.

Note:
- A same channel can appear as many times as needed in the list
- A different duration can be defined for each channel of the list
- A maximum number of 32 channels can be added in the list
- A channel can be added while Scanning monitoring mode is active. The Scanning monitoring will then be
restarted upon validation

5.2.2.2 MODIFY EXISTING LIST

1. Modify the wanted parameter(s) of the channel(s)

2. Validate with ✓ button or cancel with  button
Note: when the list is modified, EdgeProbe Advanced restart the Scanning monitoring.

5.2.2.3 DELETING AN ENTRY FROM THE LIST

1. Select the channel you want to delete

2. Click on the icon to delete the channel
3. Restart to step 1 if you want to delete another channel else go to next step
4. Validate with ✓ button or cancel with  button
Note: when the list is modified, EdgeProbe Advanced restart the Scanning monitoring.

EdgeProbe Advanced - User Manual – 4.1 – 59 / 120

5.2.3 SELECTING THE MONITORING OPERATING MODE

EdgeProbe Advanced can work in single channel monitoring or Scanning monitoring.

Mode selection is done in the “Settings” tab of the Menu and the “Channel Management” sub
menu.

1. Select operation mode

o Single Channel mode: select the channel name to monitor
o Scanning mode: select “Round-Robin”
2. Validate with ✓ button or cancel with  button
The operating mode is displayed in the status bar . Monitored channel status is also displayed in
the status bar . If the Scanning mode has been selected, it displays the current monitored channel.

 

5.3 CONFIGURE OUTPUT*1

To access the Output management, select the “Settings” tab of the Menu and then the “Output”
sub menu.
Feature available on DVB-T/T2, DVB-C/C2, ISDB-T/Tb EdgeProbe Advanced. Contact us
(support@test-tree.com) for availability on DVB-S/S2/S2X EdgeProbe Advanced.

The “IP output” functionality enables the MPEG-2 TS stream (monitored from the RF, ASI or IP input)
to be forwarded on the IP data port of the EdgeProbe Advanced (IP Forward function). VLAN tagging
is supported.
If the analyzed TS is a T2-MI stream, and the PLP extraction is active, the output TS will be the
extracted PLP TS and not the full T2-MI TS.

The Output tab provides the “Output Management” panel for enabling the IP output mode and con-
figure the IP address, port and if applicable the VLAN ID and priority.

1
*Feature unavailable in firmware version 4.1, contact us for availability

EdgeProbe Advanced - User Manual – 4.1 – 60 / 120

Note: The IP output (IP Forward) functionality is by default disabled if the Transcoding option is activated on
the EdgeProbe.

EdgeProbe Advanced - User Manual – 4.1 – 61 / 120

5.4 CONFIGURE TRANSCODING1

Combined with the TRANSBOX, the EdgeProbe can provide live service extraction and transcoding
of the analyzed multiplex.
The TRANSBOX external device is entirely controlled by the EdgeProbe via the CONTROL IP
connection: service to transcode, transcoding settings, transcoded stream destination…
The TS (MPTS or SPTS) stream analyzed by the EdgeProbe (from RF, ASI or IP inputs) is forwarded
to the TRANSBOX via the DATA IP connection.
The TRANSBOX performs service extraction and audio/video transcoding. The transcoded SPTS
(reduced bitrate) is then sent to the destination.

In order for an EdgeProbe unit to control a TRANSBOX unit, the Transcoding option must be activated
on the EdgeProbe. The IP output (IP Forward) functionality of the EdgeProbe is by default disabled if
the Transcoding option is activated.
The TRANSBOX is SNMP compatible. The TRANSBOX MIB provides basic access to the device.
The configuration and transcoding status information is available via the EdgeProbe MIB (the
EdgeProbe equipped with Transcoding option, that is controlling the TRANSBOX).

1 Feature available on DVB-T/T2, DVB-C/C2, ISDB-T/Tb EdgeProbe Advanced. Contact us (support@test-

tree.com) for availability on DVB-S/S2/S2X EdgeProbe Advanced.

EdgeProbe Advanced - User Manual – 4.1 – 62 / 120

5.4.1 TRANSBOX FIRST CONNECTION AND IP CONFIGURATION

Before configuring the Transcoding functionality via the EdgeProbe web GUI, the control/data
connection between the EdgeProbe and the TRANSBOX have to be established, meaning that the
TRANSBOX control/data IP addresses have to be configured and connected in the same control/data
network as the EdgeProbe.
The first TRANSBOX connection is similar to the first EdgeProbe connection:
• Use an Ethernet cable (RJ45 plug) to connect the TRANSBOX “IP Control” port directly to a
PC (or via a network switch).
• Plug the power cable into the power receptacle on the back panel. Then, connect the other
end of the cable to main power. Allow the TRANSBOX 1’30’’ to initialize and start.
• Once the front panel Run LED has turned GREEN, the TRANSBOX WEB GUI can be
accessed: each transcoding unit has its own IP control address and its own WEB GUI access.
• By default, the TRANSBOX is configured with the following IP address:
• Unit 1: 10.5.120.101 / 255.255.0.0
• Unit 2: 10.5.120.102 / 255.255.0.0
• Connect a PC to the TRANSBOX Control Ethernet interface and set the IP address of the PC
to 10.5.x.y / 255.255.0.0.
• Open a Web browser (Chrome or Firefox are recommended) in order to display the web-based
graphical user interface, using the control interface address: http://10.5.120.101 (or .102)
• Once you are connected to the web interface, you can configure the TRANSBOX control IP
address, to match the EdgeProbe control network, via the Device menu  Control Interface
panel
• And the TRANSBOX data IP address to match the EdgeProbe data network, via the Device
menu  Data Interface panel.

EdgeProbe Advanced - User Manual – 4.1 – 63 / 120

5.4.2 TRANSCODING CONFIGURATION VIA EDGEPROBE

To access the TRANSBOX configuration menu, select the “Settings” tab of the Menu and then the
“Transcoding” sub menu.

The following parameter need configuration:

- Control:
o TRANSBOX control IP address: must be in the same control network as the
EdgeProbe control port; for TRANSBOX command and settings
- Data Transcoding:
o IP Address and Port of the TS multiplex forwarded between the EdgeProbe and
TRANSBOX; the TRANSBOX will listen to this @IP/port to retrieve the TS to transcode
▪ Must be in the same data network as the EdgeProbe data port. Unicast mode
is supported
▪ VLAN support
o Video forward IP Address and Port: destination that will receive the extracted and
transcoded Service (SPTS) from the TRANSBOX. Unicast mode is supported
▪ VLAN support
o Transcoding configuration:
▪ Video resolution: CIF, DCIF, 2CIF, 4CIF
▪ Audio bitrate: 32 kbps to 192 kbps; all audio tracks are transcoded
▪ Timeout: transcoding duration between 30 and 600 seconds
▪ Maximum TS Bitrate: the max bitrate of the transcoded SPTS, between 1 and
10 Mbps
• If the max value set cannot be obtained given the previous video and
audio settings, for a specific Service, an alarm will be raised upon
transcoding start (“TRANSBOX Configuration” alarm, detailed in the
following paragraph “5.4.3 TRANSBOX & Transcoding alarms on

EdgeProbe Advanced - User Manual – 4.1 – 64 / 120

 EdgeProbe”)

The transcoding functionality is entirely configured in this panel, but the Transcoding launch com-
mand is made via the Monitoring menu  Multiplex-Services sub menu, details in paragraph
“6.3.7.1 Transcoding command”.

5.4.3 TRANSBOX & TRANSCODING ALARMS ON EDGEPROBE

TRANSBOX status and Transcoding alarms available in the EdgeProbe interface, and are configured
through the Transcoding tab of the Settings menu.

Parameter Description
Running An alarm is raised if the EdgeProbe cannot connect to the TRANSBOX via the control
network.
Config An alarm is raised if the transcoding configuration is inconsistent: audio and video constraints
(bitrate, resolution) cannot be obtained at the desired SPTS bitrate.
SID Not Found An alarm is raised if the TRANSBOX does not find the service to extract and transcode
(identified by SID) in the multiplex transferred by the EdgeProbe.
Input Stream An alarm is raised if the TRANSBOX does not detect an input multiplex coming from the
EdgeProbe via the data network.
Overflow An alarm is raised if the additional components (Service components such as HbbTV data,
Multiplex EIT) cannot be integrated in the transcoded stream because of the SPTS bitrate
limitation.

5.5 GENERAL MONITORING CONFIGURATION

To access the General monitoring configuration parameters, select the “Settings” tab of the Menu
and then the “General” sub menu.

The signal level measure unit can be configured to dBm or dBµV.

EdgeProbe Advanced - User Manual – 4.1 – 65 / 120

6 MONITORING VIEWS
The EdgeProbe Advanced monitoring information is structured in three panels:
- Overview: global and synthetic view of the monitored channels alarms.
- Alarm View: exhaustive list of all the alarms: related to the monitored channels and to the
device.
- Monitoring: real time graphical display of different measurements.

6.1 OVERVIEW

To access, select the “Overview” menu in the main menu.

Overview displays a summary of all channels of the Scanning list. If single channel monitoring is
used, it displays the monitored channel.
The monitored channel is highlighted with green background  while the other channels appear with
a grey background.

 

For each channel, two type of information is displayed:

- Channel identification information: depending on the type of the monitored channel(s)
(DVB-S/S2, DVB-T/T2, DVB-C/C2, ISDB-T/Tb, IP, ASI)
- General monitoring information: alarm status on three levels of monitoring:
o Transmission: alarms regarding the physical input type (RF, IP, ASI, SFN, Echoes)
o Transport Stream: ETSI TR 101 290 Priority 1, 2 & 3, MIP packet, T2-MI, BTS,
OneBeam
o Content: alarms regarding a more detailed TS monitoring (QoS, Service/PID

EdgeProbe Advanced - User Manual – 4.1 – 66 / 120

 presence…)
For each alarm, the colored rectangle indicates the number of alarm condition raised since the
counters has been reset and the current status of the alarm conditions. Code is described in the table
below.

No alarm condition has been raised

An alarm condition has been raised but is no longer present

An alarm condition has been raised and is still present

The analysis is disabled, and all alarms are disabled; applicable for T2-MI,
SFN, Echoes, OneBeam

The analysis is disabled, but at least one alarm is enabled: the last known
alarm status is displayed (green, red, orange, counter number) but the
button is faded; applicable for T2-MI, SFN, Echoes, OneBeam
The analysis is enabled, but all alarms are disabled; applicable for T2-MI,
SFN, Echoes, OneBeam

Note: to quickly access to the details of alarms, click on the counter inside the colored button. This will open
the Alarm View for this channel.

The general monitoring information includes the following alarms:

Transmission
RF Current alarm status and number of alarm conditions raised for RF input monitoring:
Demod Locked, Signal Level, MER, SNR, BER parameters, Carrier Frequency drift,
DC Constellation Degradation
ASI Current alarm status and number of alarm conditions raised for ASI input
monitoring: ASI Sync
IP Current alarm status and number of alarm conditions raised for IP input monitoring:
IP Input Data
SFN drift Current alarm status and number of alarm conditions raised for SFN
synchronization monitoring: SFN Drift or T2 Frame Drift
Echoes Current alarm status and number of alarm conditions raised for Echoes monitoring:
Echoe Values
Transport Stream
ETR1 Current alarm status and number of alarm conditions raised for ETSI TR 101 290
Priority 1
ETR2 Current alarm status and number of alarm conditions raised for ETSI TR 101 290
Priority 2
ETR3 Current alarm status and number of alarm conditions raised for ETSI TR 101 290
Priority 3
T2-MI Current alarm status and number of alarm conditions raised for T2-MI monitoring
BTS Current alarm status and number of alarm conditions raised for BTS monitoring.
Available only on EdgeProbe Advanced ISDB-T/Tb version.
OneBeam Current alarm status and number of alarm conditions raised for OneBeam
monitoring

EdgeProbe Advanced - User Manual – 4.1 – 67 / 120

 MIP Current alarm status and number of alarm conditions raised for MIP monitoring
Content
Advanced Current alarm status and number of alarm conditions raised for the Advanced tests
Multiplex Current alarm status and number of alarm conditions raised for the Multiplex
monitoring (TS ID/Service/PID presence, Unscrambling)
Transcoding Current alarm status and number of alarm conditions raised by the ongoing
Transcoding (TRANSBOX related alarms)

The channel identification information includes the following information:

For a DVB-S, DVB-T, DVB-C or ISDB-T/Tb channel:
Input Source of the channel (RF, ASI or IP)
Frequency Frequency of the channel in MHz
Network ID Network ID extracted from the MPEG TS transport stream (Network ID field of the
NIT table)
Services Number of services present in the MPEG-TS
Alarm profile Name of the alarm profile
Last Alarm Date and time of the last raised alarm
Last Scan Date and time of the last scan
This field is only present when the scanning is activated and the channel is not
being currently scanned
Scanning Elapsed time since the start of the scan
This field is only present for the monitored channel.

For a DVB-S2 channel:

Input Source of the channel (RF, ASI or IP)
Frequency Tuned Frequency of the channel in MHz (Satellite Frequency – LNB Frequency)
Network Id Network ID extracted from the MPEG TS transport stream (Network ID field of the
NIT table)
Services Number of services present in the MPEG-TS
Last Alarm Date and time of the last raised alarm
Last Scan Date and time of the last scan
This field is only present when the scanning is activated and the channel is not
being currently scanned
Alarm profile Name of the alarm profile
Scanning Elapsed time since the start of the scan
This field is only present for the monitored channel.

For a DVB-T2 channel:

Input Source of the channel (RF, ASI or IP)
Frequency Frequency of the channel in MHz
PLP Count Number of PLP detected for this RF frequency

EdgeProbe Advanced - User Manual – 4.1 – 68 / 120

PLP id PLP id of the channel
Network Id Network ID extracted from the MPEG TS transport stream (Network ID field of the
NIT table)
Services Number of services present in the MPEG-TS
Last Alarm Date and time of the last raised alarm
Last Scan Date and time of the last scan
This field is only present when the scanning is activated and the channel is not
being currently scanned
Alarm profile Name of the alarm profile
Scanning Elapsed time since the start of the scan
This field is only present for the monitored channel.

For an ASI channel:

Input Source of the channel (RF, ASI or IP)
Network ID Network ID extracted from the MPEG TS transport stream (Network ID field of the
NIT table)
Services Number of services present in the MPEG-TS
Alarm profile Name of the alarm profile
Last Alarm Date and time of the last raised alarm
Last Scan Date and time of the last scan
This field is only present when the scanning is activated and the channel is not
being currently scanned
Scanning Elapsed time since the start of the scan
This field is only present for the monitored channel.

For an IP channel:
Input Source of the channel (RF, ASI or IP)
Network ID Network ID extracted from the MPEG TS transport stream (Network ID field of the
NIT table)
Services Number of services present in the MPEG-TS
Alarm profile Name of the alarm profile
Last Alarm Date and time of the last raised alarm
Last Scan Date and time of the last scan
This field is only present when the scanning is activated and the channel is not
being currently scanned
Scanning Elapsed time since the start of the scan
This field is only present for the monitored channel.

EdgeProbe Advanced - User Manual – 4.1 – 69 / 120

6.2 ALARM VIEW

To access the Alarm View panel, select the “Alarm View” menu in the main menu or click on an alarm
counter in the Overview.

Alarm View displays the exhaustive alarm list: both device (EdgeProbe, eventually TRANSBOX) and
monitoring channel alarms. You can select the device/channel using the “Channel Selection”.
Monitored channel alarm list:

EdgeProbe Advanced - User Manual – 4.1 – 70 / 120

 

EdgeProbe device alarm list:

EdgeProbe Advanced - User Manual – 4.1 – 71 / 120

TRANSBOX device alarm list:

The “Alarms” panel provides the current state of all alarms for the selected channel.

Reset all counters of alarm for the selected channel. Please note that this only
resets alarm counters, not current state of the alarms.

For each alarm, the following information is provided:

 


 Indicates if the alarm display is enabled (appears in green) or disabled (appears in grey) for this
alarm; if the alarm is enabled, the alarm states will be indicated in the log files
 Indicates if traps are enabled (appears in green) or disabled (appears in grey) for this alarm
 Current status of the alarm (Green = no alarm raised, Orange = alarm has been raised but is no
longer active, Red = alarm condition has been raised and is still active)
 Alarm counter: number of alarm conditions raised since the last counter reset
 Reset counter button to reset this alarm counter to 0. Please note that it does not affects the alarm
state.

6.2.1 ALARM TRIGGER, COUNTER, LOG LINE AND TRAP MECHANISM

An alarm changes state from OFF  ON if the error conditions meet the alarm configuration (min,
max thresholds, hysteresis, NbErrors, OverLast…) depending on the alarm type; as seen previously
in paragraph “5.1 Configure Alarm Profiles”.
An alarm changes state from ON  OFF when the error conditions no longer meet the same alarm
configuration.
When an alarm changes state from OFF  ON the alarm’s counter is increased by one (+1); the
counter is unchanged when the state changes from ON  OFF.
This is the functioning for all EdgeProbe alarms, except 3 alarms: “Echo values”, “Services Missing”
and “Pids Missing”, because:

EdgeProbe Advanced - User Manual – 4.1 – 72 / 120

 • For these particular alarms one or more elements to monitor are configured (one or more
echoes, Service IDs, PID numbers)
• When at least one element to monitor is in error, the alarm state changes from OFF  ON and
counter +1
• When all elements are no longer in error, the alarm state changes from ON  OFF and counter
does not change
• During the time the alarm state is ON, other elements to monitor might be in error (eg for PID
Missing alarm: a second PID not present; PID not present comes back but another one is
missing…), therefore, each time another element is in error, the alarm counter is increased +1
Each time the alarm state changes from OFF  ON, ON  OFF or counter +1 (even during alarm
state ON), the event is written in the log file, and traps are sent to the NMS if the ‘trap’ function is
enabled.

EdgeProbe Advanced - User Manual – 4.1 – 73 / 120

6.3 MONITORING VIEW

To access the Monitoring View panel, select the “Monitoring” menu in the main.

The monitoring information displayed in this menu concerns the currently monitored channel only.
Channel view displays real-time values of RF measurements and the modulation.
SFN view displays real-time values of the SFN Drift measurement.
Frequency view displays real-time values of the Carrier Frequency Drift measurement.
Echoes view presents a real-time graphical display of the Channel Impulse Response.
QoS view displays real-time values of Service Availability Error and Service Degradation Error.
T2-MI view displays real-time values of T2 L1 current information (L1 pre and L1 post signaling).
Multiplex- Services displays real-time information regarding the service plan of the multiplex: bitrate
chart and PID/service structure tree.
OneBeam view displays real-time values of T2 L1 current information (L1 pre and L1 post signaling)
extracted from the specific OneBeam PID.
SCTE 35 view lists the occurrence of a SCTE 35 PID (more precisely the occurrence of the “splice
info” table).
Data Storage view displays the list of files stored on the internal memory: log files list, trend files list,
record files list.
GNSS view displays real-time information regarding the GPS and Glonass signal status.
Logs Events view displays real-time the logs information.

6.3.1 CHANNEL

Channel monitoring panel displays real-time RF measurement values as well as the RF signal
modulation parameters.

EdgeProbe Advanced - User Manual – 4.1 – 74 / 120

For a DVB-S2 channel:

For a DVB-T2 channel:

For a DVB-T channel:

EdgeProbe Advanced - User Manual – 4.1 – 75 / 120

For a DVB-C channel:

For an ISDB-T/Tb channel:

EdgeProbe Advanced - User Manual – 4.1 – 76 / 120

6.3.2 SFN DRIFT

Important note: for DVB-T2/ISDB-T/Tb SFN monitoring (RF SFN Drift, T2-MI Network Delay), the
EdgeProbe local date and time MUST be synchronized against a NTP server using a 1PPS reference
signal.

The EdgeProbe Advanced SFN measurement for a DVB-T system indicates the following parameters:
• SFN Delay: time to receive RF signal
• SFN Drift: variation of the SFN Delay

The EdgeProbe Advanced SFN measurement for a DVB-T2/ISDB-T/Tb system indicates the following
parameters:
• SFN Drift: the difference between the RF frame actual reception time t and the theoretical
reception time Tk.
• Reference time: a T0 reception time of the first RF frame considered as a reference.

EdgeProbe Advanced - User Manual – 4.1 – 77 / 120

The EdgeProbe Advanced SFN measurement for a T2-MI TS over ASI input indicates the following
parameters:
- Network Delay: difference between the actual reception time and the T2GW emission time
(computed based on the T2-MI timestamp and MND information); added to the eventual Time
Offset used for relative timestamps systems.
- Time to Transmit: difference between the MND and the Network Delay (not considering the
eventual Time Offset used for relative timestamp systems).

Please refer to the appendix paragraph “14.3 SFN synchronization measurement” for details
concerning the SFN synchronization mechanism and measurements.
Important note: for DVB-T2/ISDB-T/Tb SFN monitoring (RF SFN Drift, T2-MI Network Delay), the
EdgeProbe local date and time MUST be synchronized against a NTP server using a 1PPS reference
signal.

6.3.3 CARRIER FREQUENCY DRIFT

The Carrier Frequency Drift monitoring applies for DVB-T/T2 and ISDB-T/Tb RF input signals.
The Frequency view provides a real-time display of the Frequency Drift value:

The “Reset reference” button will re-initialize the computation of the drift of the frequency.
When the monitoring begins, the Carrier Frequency Drift computation requires an initial delay (about
60s) before any value is displayed. To provide a precise and reliable drift value, the computation
mechanism uses the last minute worth of measure to compute the drift.

EdgeProbe Advanced - User Manual – 4.1 – 78 / 120

6.3.4 ECHOES

The Channel Impulse Response monitoring applies for DVB-T/T2 and ISDB-T/Tb RF input signals.
The echoes view provides a real-time graphical view of the Channel Impulse Response. The echoes
alarm settings (delay, level) are represented by a rectangle placed in the graph according to the
configuration.

The Echoes display offers the following quick access configuration:

- Click on a non-monitored echo (in yellow) offers the possibility to configure an echo alarm
without having to pass through the Settings  Alarm Profiles  Echoes panel. The echo
alarm configuration made in this monitoring view is associated to the alarm profile active for
the current channel being monitored.

- Click on a monitored echo (green or red rectangle above the echo) offers the possibility to
remove the echo alarm without having to pass through the Settings  Alarm Profiles  Ech-
oes panel. The echo alarm configuration made in this monitoring view is associated to the
alarm profile active for the current channel being monitored.

EdgeProbe Advanced - User Manual – 4.1 – 79 / 120

The echoes alarms are configurable via the Settings  Alarm Profiles panel  Echoes tab (see also
paragraph “5.1.13 Echoes Settings”). In order to avoid the frequent alarm trigger on/off, accepted
variation thresholds can be configured for both echo level (±2.5dB by default) and echo time delay
(±5µs by default).

6.3.5 QOS

The service performance is well defined by:

Service Availability Errors (SAE): Count the number of errors for the following parameters over a
defined time interval Delta Τ: TS_sync_loss, PAT_error, PMT_error.
Service_Availability_Error_Ratio: the percentage of time for which the parameter exceeds a pre-
defined threshold.

Service Degradation Errors (SDE): Count the number of errors for the following parameters over a
defined time interval Delta Τ: CRC_error, PCR_error, NIT_error, SDT_error.
Service_Degradation_Error_Ratio: the percentage of time for which the parameter exceeds a pre-
defined threshold.
Please refer to the appendix paragraph “14.4 QoS monitoring parameters” for more details concerning
the QoS parameters.

EdgeProbe Advanced - User Manual – 4.1 – 80 / 120

6.3.6 T2-MI

The T2-MI monitoring view displays real-time values of T2 L1 current information (L1 pre and L1 post
signaling).

The “Jumbo T2MI” parameter indicates the presence (Yes/No) of a Jumbo T2-MI input stream, which
is an ENENSYS proprietary T2-MI stream format.
A Jumbo T2-MI stream unlocks the limitation of FEC blocks number per T2-Frame in order to transport
a total PLP bitrate that is superior to the theoretical bitrate allowed by the T2-MI standard (L1
parameters). A Jumbo T2-MI stream’s bitrate can go up to 100 Mbps.
The Jumbo T2-MI support is conditioned by the presence of the “JumboT2MI” software option.
If the PLP extraction is enabled (“Enable analysis on PLP” active), the ETR290 priority 1/2/3
monitoring is made on the extracted PLP TS; otherwise on the full T2-MI TS.

EdgeProbe Advanced - User Manual – 4.1 – 81 / 120

6.3.7 MULTIPLEX-SERVICES

Multiplex- Services view displays real-time information of the analyzed multiplex: provider, LCN,
net/overall bitrate information, service bitrate, components bitrate and type…

EdgeProbe Advanced - User Manual – 4.1 – 82 / 120

6.3.7.1 TRANSCODING COMMAND1

If the EdgeProbe contains the “Transcoding” software option and is combined with a TRANSBOX
device, the Multiplex-Services panel is equipped with controls enabling the Transcoding function
command.
Please refer to paragraph “5.4 Configure Transcoding” for details regarding the Transcoding function
configuration.

The “TRANSBOX Status” alarm is a combination of all the TRANSBOX device specific alarms; if at
least one TRANSBOX device specific is raised, “TRANSBOX Status” is red.

In the Service list view, a Transcoding control button is added next to each Service; in order
to command the Transcoding of this specific Service.
This control button can have the following states:

1 Feature available on DVB-T/T2, DVB-C/C2, ISDB-T/Tb EdgeProbe Advanced. Contact us (support@test-

tree.com) for availability on DVB-S/S2/S2X EdgeProbe Advanced.

EdgeProbe Advanced - User Manual – 4.1 – 83 / 120

 No ongoing Transcoding, TRANSBOX is ready, a Transcoding sequence
can be launched for this particular Service

SID 257 transcoding control pressed:

- Transcoding start command launched to TRANSBOX
- transcoding will be launched after a 10s initial delay
corresponding to the time the Multiplex is forwarded and the
TRANSBOX will evaluate if the transcoding configuration (audio
bitrate, video resolution, TS bitrate) can be fulfilled on the
desired Service

Ongoing Transcoding for this SID 257:

- TRANSBOX Status OK: transcoding configuration accepted,
the Service is extracted from the Multiplex, the extracted and
transcoded SPTS is forwarded to destination
- Transcoding countdown indicated: transcoding will
automatically stop when the Timeout is reached
- Transcoding can be manually stopped before the Timeout
Ongoing Transcoding of another Service of the Multiplex; Transcoding
cannot be launched for this specific Service while the current Transcoding
has not finished

SID 257 transcoding stopped

SID 257 transcoding control pressed, but the transcoding configuration

cannot be fulfilled:
- TRANSBOX Status NOK
- Transcoding countdown indicated: transcoding will
automatically stop when the Timeout is reached
- Transcoding can be manually stopped before the Timeout

EdgeProbe Advanced - User Manual – 4.1 – 84 / 120

6.3.8 ONEBEAM

The OneBeam monitoring view displays the T2 L1 information (L1 pre and L1 post signaling) extracted
from the T2-MI Marker PID, and also the T2 multiplex PLP and service structure extracted from the
In-Band PID.

EdgeProbe Advanced - User Manual – 4.1 – 85 / 120

6.3.9 SCTE 35

SCTE 35 view lists the occurrence of the “splice info” table on a SCTE 35 PID. The presence of this
monitoring view is enabled by the “Scte35Monitoring” option.

EdgeProbe Advanced - User Manual – 4.1 – 86 / 120

6.3.10 DATA STORAGE

Data Storage view displays the list of files stored on the internal memory: log files list, trend files list,
record files list. Existent files can be downloaded or deleted.

For the log and trend recording, the current information is written in the “log.csv” (“trend.csv”) current
working file. Once the storage configuration has been fulfilled (size, day mode), the file is achieved
into a “log.archieveDate_archieveTime.csv” (trend.archieveDate_archieveTime.csv”) file.
Regarding the TS recordings, the file created is named “Rec.StartDate_StartTime.ts”.
Use the Record (TS Mode) button from the bottom status bar in order to start/stop the TS recording.
An ongoing TS recording will be automatically stopped if the maximum allocated size for the TS record
files has been reached.

Record command status

The “ExtendedMemory” option is disabled.
If the “ExtendedMemory” option is enabled, the records storing function is
deactivated.

The “ExtendedMemory” option is enabled, a new recording can be started.

Press the button to start a TS recording.

The “ExtendedMemory” option is enabled, a TS recording is ongoing. Press

the button to stop the recording.

The “ExtendedMemory” option is enabled, the TS recording storage quota

(max allocated storage) has been reached. Change the Max allocated
storage limit or remove existing TS recordings in order to free the storage
available space.

EdgeProbe Advanced - User Manual – 4.1 – 87 / 120

 Note:
- The file download is forbidden during a stream recording. The stream recording is also forbidden during
a file download.
- Stream record capacity: 50Mbps (DVB-T2 signals), 60Mbps (DVB-C2 signals).
- The stream record is automatically stopped if a firmware update is launched via the GUI.

6.3.11 GNSS

*1GNSS view provides real-time information about the GNSS receiver status, measures and the
satellites signal levels. The different GPS and GLONASS satellites are identified by their PRN and
their signal levels are updated in real-time.

A minimum of 4 satellites in use is required to lock the internal GNSS receiver.

The localization and GPS date and time are also displayed. Please note that this information is not
used by the EdgeProbe.

1
*Feature unavailable in firmware version 4.1, contact us for availability

EdgeProbe Advanced - User Manual – 4.1 – 88 / 120

6.3.12 LOGS EVENTS

The logging default storage is limited to 1000 lines. If this limit is exceeded, the oldest lines will be
deleted in order to add new ones.
If it is necessary to save all logging events, the log memory management must be enabled; see “4.8
Internal memory management” paragraph for configuration and “6.3.10 Data Storage” paragraph
for log files retrieval.

EdgeProbe Advanced - User Manual – 4.1 – 89 / 120

7 ADMINISTRATION
From the Admin menu, the operator can enable authentication on the EdgeProbe Advanced and
assign the relevant login/password to access to the product.

Two type of users can be defined:

• Administrator: The user 'Administrator' can have access in read and write mode over all the
panels of the EdgeProbe Advanced.
• User: The user 'User' can have access in read mode only over all the panels of the EdgeProbe
Advanced.
When the authentication is enabled:
• Only the 'Administrator' user can assign login password to both users.
• A panel window with login and password fields is popped-up for each new access to the GUI.
• A login/password shall be entered to access to the EdgeProbe Advanced GUI.

EdgeProbe Advanced - User Manual – 4.1 – 90 / 120

8 GENERAL INFORMATION
The “About” panel provides general information about the EdgeProbe device:
• User-defined parameters such as name and location: which appear in the web browser tab
name
• Device parameters such as serial number and firmware version
• Options activated (Options panel)

For more information about firmware update availability, please contact TestTree support team
(support@test-tree.com).

Use icon to access to ENENSYS TestTree Privileged Area website. Furthermore, as an

ENENSYS TestTree customer, we also strongly advise you to ask for login and password to access
our Privileged Area website.

EdgeProbe Advanced - User Manual – 4.1 – 91 / 120

Use icon to open EdgeProbe Advanced user manual. Please note that PDF reader must be
installed on your computer.

Use icon to identify the EdgeProbe Advanced (the LED on the front panel will start blinking for
10 seconds).

Use icon to download a zip file with the MIB files.

Use icon the reboot the EdgeProbe Advanced.

EdgeProbe Advanced - User Manual – 4.1 – 92 / 120

9 NMS INTEGRATION
The EdgeProbe Advanced provides a MIB object which enables the integration with a NMS (Network
Management System) via SNMP; for device configuration and data monitoring.

The device’s MIB files can be downloaded from the “About” panel, using the icon. The MIB
archive file contains three MIB files:
- “ENENSYS-ENTERPRISE-MIB”
- “ENENSYS-MONITOR-MIB”
- “ENENSYS-EDGEPROBE-MIB”: integrates also the “ENENSYS-ENTERPRISE-MIB” and the
“ENENSYS-MONITOR-MIB” MIBs, has the following structure:
“alarmCurrentTable” contains a list of the alarms that are currently active on the device.
“alarmTable” contains the list of the alarms
available on the device (details and alarm status).
“alarmAdvancedConfig” contains all the device’s
alarms (device and monitoring alarms), with a
pure informative usage, allowing to retrieve each
alarm’s ID.
“logTable” provides access to the device’s event
logs.
“plateform” file contains the device’s parameters:
device (name, location…), network (IP@, default
GW, network mask…), date&time, temperature,
GPS status and clock reference.

EdgeProbe Advanced - User Manual – 4.1 – 93 / 120

 “testMonitoringLine” provides access to the
device’s monitoring configuration (“configuration”
file) and monitoring parameters (“statistics” file –
alarm status and values of the monitored
parameters).
“edgeprobe” -> “configuration” gives access to all
the alarm parameters configuration: configuration
can be made on the active alarm profile (the alarm
profile of the channel being currently monitored)
“edgeprobe” -> “statistics” gives access to the
device’s monitoring parameters (values and alarm
status), which are mainly structured in table
format with values corresponding to the monitored
channel. If in Scanning – Round Robin mode, the
tables contain the status & values corresponding
to each channel defined in the Round Robin
sequence:
- “rf”: RF parameters structured by standard
- “etr”: ETR290 parameters structured by
priority level
- “sfnDriftTable”: for DVB-T/T2 SFN
monitoring
- “multiplex”: TS, Service and PID parameters
- “carrierFrequencyOffsetTable”: for Carrier
Frequency drift monitoring
- “bts”: BTS monitoring alarms

EdgeProbe Advanced - User Manual – 4.1 – 94 / 120

10 UPDATES AND PRIVILEGED AREA
A Privileged Area (http://privileged.enensys.com) is available for the TestTree clients, which provides
access to the products general documentation, User Manuals, software upgrades.
In order to have access to the Privileged Area, you will have to register on your first connection. A
serial number of your TestTree equipment will be required in order to validate the account and the
access rights (depending on the purchased Support Service). You will then receive a notification in-
forming you that your account has been activated.

EdgeProbe Advanced - User Manual – 4.1 – 95 / 120

11 TROUBLESHOOTING

11.1 DEVICE STATUS AND ALARMS

11.1.1 POWER LED

Alarm/Problem
Power LED is OFF Severity: Critical
Affected systems: EdgeProbe
Indicates that the EdgeProbe power supply is no longer working.
End user impact: No
Action
Check that power supply cable is properly connected. If the power supply issue is confirmed, an
RMA procedure will be applied on the device, please refer to paragraph “12 Equipment return for
repair”.

11.1.2 RUN LED

Alarm/Problem
Run LED is RED  at least one UnitX LED is
Severity: Critical
OFF
Affected systems: EdgeProbe
Indicates that at least one (among the two units Unit1&Unit2 or Unit3&Unit4) EdgeProbe
monitoring unit is not running.
End user impact: No
Action
An RMA procedure will be applied on the device, please refer to paragraph “12 Equipment return
for repair”.

EdgeProbe Advanced - User Manual – 4.1 – 96 / 120

11.1.3 WEB GUI CONNECTION

Alarm/Problem
Web GUI connection not stable, or not available Severity: Critical
Affected systems: EdgeProbe
Indicates that the EdgeProbe control is not stable or lost.
End user impact: No
Action
Check the status of the front panel LEDs. Please refer to paragraphs “11.1.1 Power LED” and
“11.1.2 Run LED”.
Proceed to IP address reset: press 3s the rear panel reset button.
Connect to the EdgeProbe control using the default IP address. Reconfigure the necessary
control and data IP address.
The EdgeProbe control and data interfaces must be configured in different networks. Configuring
both data and control on the same LAN might cause random connection loss behaviors: web
GUI control, IP data streams, NTP communication, SNMP trap receiver communication might be
randomly routed between the two physical control and data interfaces.

11.1.4 1*GNSS LED

Alarm/Problem
GPS LED is RED = GNSS signal presence Severity: Major
alarm is ON
Affected systems: EdgeProbe
Indicates that the internal GNSS receiver is not locked on the external GPS signal connected to
the EdgeProbe GPS input.
End user impact: No
Action
Check that the external GPS signal source is valid and correctly connected to the EdgeProbe
GPS input (view the GNSS receiver state in the Monitoring menu  GNSS tab).
If the issue persists while a valid GPS signal is correctly connected to the EdgeProbe, an RMA
procedure will be applied on the device, please refer to paragraph “12 Equipment return for
repair”.

11.1.5 TEMPERATURE

Alarm/Problem

1
*Feature unavailable in firmware version 4.1, contact us for availability

EdgeProbe Advanced - User Manual – 4.1 – 97 / 120

Temperature Severity: Major
Affected systems: EdgeProbe
Shows the EdgeProbe instant temperature on the hardware board level and indicates that the
max temperature threshold, set in the Device menu  General tab  Device Alarms panel, has
been reached.
End user impact: No
Action
Change the max temperature threshold and check air cooling system. If the EdgeProbe fans do
not seen to start, even if the max temperature threshold is set to a lower value, an RMA
procedure will be applied on the device, please refer to paragraph “12 Equipment return for
repair”.

EdgeProbe Advanced - User Manual – 4.1 – 98 / 120

11.1.6 NTP SERVER, DATE/TIME SYNCHRONISATION

Alarm/Problem
NTP Server presence Severity: Minor
Affected systems: EdgeProbe
Indicates that the EdgeProbe time synchronization with the NTP server has failed. .
End user impact: No
Action
Check that the NTP server and the EdgeProbe are correctly connected to the same IP control
network.
Check the IP control configuration of the EdgeProbe in the Device menu  General tab 
Control interface panel.
Check that the EdgeProbe can ping the NTP server, ping available in the Device menu 
General tab  Control interface panel.
Check and/or change NTP server settings in the Device menu  General tab  Date & Time
panel.
The EdgeProbe control and data interfaces must be configured in different networks. Check that
the IP data interface is configured into a different network than the IP control interface: Device
menu  General tab  Data interface panel.

11.1.7 1PPS SYNCHRONIZATION

Alarm/Problem
External PPS Presence Severity: Major
Affected systems: EdgeProbe
Indicates that the external 1PPS signal connected to the EdgeProbe 1PPS input is no longer
detected.
End user impact: No
Action
Check that the external 1PPS signal source is valid and correctly connected to the EdgeProbe
1PPS input. Adapt the SFN synchronization source accordingly in Device menu  General tab 
SFN reference clock panel.
If the issue persists while a valid 1PPS signal is correctly connected to the EdgeProbe, an RMA
procedure will be applied on the device, please refer to paragraph “12 Equipment return for
repair”.

EdgeProbe Advanced - User Manual – 4.1 – 99 / 120

11.1.8 10MHZ SYNCHRONIZATION

Alarm/Problem
External 10MHz Presence Severity: Minor
Affected systems: EdgeProbe
Indicates that the external 10MHz signal connected to the EdgeProbe 10MHz input is no longer
detected.
End user impact: No
Action
Check that the external 10MHz signal source is valid and correctly connected to the EdgeProbe
10MHz input. Adapt the SFN synchronization source accordingly in Device menu  General tab
 SFN reference clock panel.
If the issue persists while a valid 10MHz signal is correctly connected to the EdgeProbe, an RMA
procedure will be applied on the device, please refer to paragraph “12 Equipment return for
repair”.

11.1.9 *1GNSS 1PPS SYNCHRONIZATION

Alarm/Problem
Internal GNSS 1PPS Presence Severity: Minor
Affected systems: EdgeProbe
Indicates that the internal 1PPS signal generated by the internal GNSS receiver is no longer
present (correctly generated), and that the internal GNSS receiver is not locked on the external
GPS signal connected to the EdgeProbe GPS input
End user impact: No
Action
Check that the external GPS signal source is valid and correctly connected to the EdgeProbe
GPS input (view the GNSS receiver state in the Monitoring menu  GNSS tab). Adapt the SFN
synchronization source accordingly in the Device menu  General tab  SFN reference clock
panel.
If the issue persists while a valid GPS signal is correctly connected to the EdgeProbe, an RMA
procedure will be applied on the device, please refer to paragraph “12 Equipment return for
repair”.

1
*Feature unavailable in firmware version 4.1, contact us for availability

EdgeProbe Advanced - User Manual – 4.1 – 100 / 120

11.1.10 NMS TRAPS

Alarm/Problem
NMS trap receiver is not receiving alarm traps
NMS system cannot GET/SET MIB OID Severity: Critical
parameters
Affected systems: EdgeProbe
Indicates that the IP connection between the NMS system and the EdgeProbe is not available.
End user impact: No
Action
Check that the NMS system and the EdgeProbe are correctly connected to the same IP control
network.
Check the IP control configuration of the EdgeProbe in the Device menu  General tab 
Control interface panel.
Check the IP configuration of the NMS trap receiver in the Device menu  General tab  Trap
Receivers panel.
Check that the EdgeProbe can ping the NMS trap receiver, ping available in the Device menu 
General tab  Control interface panel.
The EdgeProbe control and data interfaces must be configured in different networks. Check that
the IP data interface is configured into a different network than the IP control interface: Device
menu  General tab  Data interface panel.

11.2 MONITORING ALARMS

11.2.1 RF INPUT

Alarm/Problem
RF unlock Severity: Critical
Affected systems: EdgeProbe
Indicates that the EdgeProbe is no longer locked on the RF input signal.
End user impact: No
Action
Check the EdgeProbe RF input configuration in the Settings menu  Channel Management tab
 Single Channel Configuration: RF standard DVB-T/DVB-T2/DVB-C/DVB-C2, frequency,
bandwidth, PLP ID.
Check that the RF cable is correctly connected between the RF source and the EdgeProbe RF
input.
Connect the same RF source cable the RF input of the different EdgeProbe monitoring units and
check the RF lock status.
If the issue persists while a valid RF signal (-90 to -5 dBm) is correctly connected to the

EdgeProbe Advanced - User Manual – 4.1 – 101 / 120

EdgeProbe RF input, an RMA procedure will be applied on the device, please refer to paragraph
“12 Equipment return for repair”.

EdgeProbe Advanced - User Manual – 4.1 – 102 / 120

11.2.2 SFN DRIFT

Alarm/Problem
SFN Drift value missing or
Severity: Major
Carrier Frequency Drift value missing
Affected systems: EdgeProbe
Indicates that the EdgeProbe is no longer measuring the SFN delay of the RF input signal.
End user impact: No
Action
Check that the SFN reference clock configuration in the Device menu  General tab  SFN
reference clock panel, corresponds to the type of synchronization signals connected to the
EdgeProbe: External 1PPS signal, Internal 1PPS signal (via the external GPS signal and the
internal GNSS receiver).
Check the state of the 1PPS signal presence alarms: “Internal GNSS 1PPS Presence” or
“External PPS Presence”.
For DVB-T standard, check the MIP packet presence alarm. In DVB-T, the SFN measure relays
on the MIP packet analysis.
Connect the same RF source cable the RF input of the different EdgeProbe monitoring units and
check the SFN drift value presence.

11.2.3 TS_SYNC

Alarm/Problem
1.1 TS_sync_loss alarm is ON when
Severity: Critical
analyzing IP input stream
Affected systems: EdgeProbe
Indicates that the EdgeProbe is not receiving the TS over IP input stream.
End user impact: No
Action
Check that the EdgeProbe IP data port and the TS over IP source are correctly connected in the
same local data network.
Check the IP data configuration in the Device menu  General tab  Data interface panel.
Check that the EdgeProbe can ping the TS over IP source device, ping available in the Device
menu  General tab  Data interface panel.
Check the EdgeProbe IP input configuration in the Settings menu  Channel Management tab
 Single Channel Configuration: IP, local or multicast IP address, IP address and port, VLAN ID.
If the TS over IP is a multicast stream, check that IGMP protocol is supported by routers/switch
from the local data network.
Connect the same IP source cable the IP data input of the different EdgeProbe monitoring units
and check the TS_sync_loss alarm status.

EdgeProbe Advanced - User Manual – 4.1 – 103 / 120

Check that the TS over IP source stream does not actually present a TS_sync_loss issue, by
analysing the same IP source on a PC running VLC media player application.
If the issue persists while a valid TS over IP stream is correctly connected to the EdgeProbe IP
data input, an RMA procedure will be applied on the device, please refer to paragraph “12
Equipment return for repair”.

11.2.4 MULTIPLEX-SERVICES

Alarm/Problem
Multiplex – Services view does not display the
available services and bitrate is set to 0 Severity: Major
Mbit/s
Affected systems: EdgeProbe
Indicates that the EdgeProbe is no longer extracting the service list from the analyzed TS.
End user impact: No
Action
Check that the input signal (RF, IP, ASI) is valid and correctly connected to the EdgeProbe input.
Check that the “Service Plan” software option is active: available in the About menu  Options
panel.
In case of RF input signals: check the signal level value, the RF lock and TS_sync_loss alarms.
A low signal level (generally inferior to -70 dBm) may prevent the demodulator to extract the
signal’s TS.

EdgeProbe Advanced - User Manual – 4.1 – 104 / 120

12 EQUIPMENT RETURN FOR REPAIR
In case of problems with one of TestTree products, please report it to our Technical Support team via
email (support@test-tree.com). Your request should specify the Serial Number as displayed on the
bottom label of the equipment, with a description of the defect, reference of Purchase Order if
possible, and your full details.

Upon receiving your request, a support engineer will get in touch with you in order to surely identify
the source of your problem. If equipment has to be returned for repair, a RMA1 number will be provided
to you. You will need to indicate it on the shipping box of the faulty equipment, and add it in your
communication with our support team.
Customer to TestTree shipping is the responsibility of the Customer. TestTree to Customer shipping
is the responsibility of TestTree. Except eventual custom SLA agreement.
The equipment will be shipped back along with a repair report.

1 Returned Material Authorization

EdgeProbe Advanced - User Manual – 4.1 – 105 / 120

13 CONTACT INFORMATION
TestTree
c/o ENENSYS Technologies
6 rue de la Carrière
CS 37734
35577 Cesson Sévigné CEDEX
FRANCE

Tel: +33 (0)1 70 72 51 70

Fax: +33 (0)2 99 36 03 84

Technical support email: support@test-tree.com

EdgeProbe Advanced - User Manual – 4.1 – 106 / 120

14 APPENDIX

14.1 ETR ALARMS LIFECYCLE

This paragraph presents a few detailed uses cases for the ETR and OneBeam alarms lifecycle. For
these use cases, only two alarm parameters are taken into consideration:
• Nb Errors (N): number of errors that must be detected during the OverLast period in order to
trigger the alarm start
• OvertLast (T): the duration an alarm remains active after the error stop has been detected.

Figure 1 ETR alarms: use case 01

EdgeProbe Advanced - User Manual – 4.1 – 107 / 120

 Figure 2 ETR alarms: use case 02

EdgeProbe Advanced - User Manual – 4.1 – 108 / 120

 Figure 3 ETR alarms: use case 03

EdgeProbe Advanced - User Manual – 4.1 – 109 / 120

 Figure 4 ETR alarms: use case 04

Figure 5 ETR alarms: use case 05

EdgeProbe Advanced - User Manual – 4.1 – 110 / 120

 Figure 6 ETR alarms: use case 06

Figure 7 ETR alarms: use case 07

EdgeProbe Advanced - User Manual – 4.1 – 111 / 120

14.2 SCANNING RECOMMENDATIONS

14.2.1 SCANNING FUNCTIONING

When analyzing a new input channel, the time measurement is triggered by the “start” command:
• Manually: by selecting the input channel via the GUI,
• Automatically: in scanning mode when passing from an input channel to another.

Figure 8 Analysis start: lock time and initialization phase

During initialization, the lock time is generally inferior to 1s, and the time interval before the first alarms
can be generated depends on the input bitrate (a certain amount of data must be available in order to
correctly compute the different signal parameters, such as BER, MER…).
For example, for a 24Mbps DVB-T signal in France, the initialization phase can take up to 5s before
the first alarms can be generated. This duration increases for a smaller bitrate.

Figure 9 Alarm lifecycle during scanning: alarm duration < channel scanning time
For alarms with a non-null “OverLast” parameter:
• T0: error detection
• T0 + 500ms (trigger timeout): alarm start trigger
• T1: error stop detection
• T1 + OverLast: alarm stop trigger

After detecting the error stop, the alarm is still active because of the OverLast parameter. An error is
considered no longer present only if it does not reoccur during the OverLast duration. Therefore, the
alarm stop is triggered only after the OverLast duration.

EdgeProbe Advanced - User Manual – 4.1 – 112 / 120

 Figure 10 Alarm lifecycle during scanning: alarm duration > channel scanning time
In case the channel’s scanning time ends before the OverLast times out, when re-analyzing again the
channel, the alarm stop will be triggered only after the entire OverLast duration times out.

14.2.2 ALARMS LIFECYCLE AND SCANNING TIME

Hereafter, a list of values recommended for the scanning time, depending on the alarm type.
RF alarms
RF alarms can be triggered after 5s, for a 24Mbps bitrate.
The minimum scanning time recommended is 7s.
Multiplex alarms
Multiplex alarms can be triggered at the same time as the RF alarms.
However, the “Service Missing” alarm is triggered if the service is not present during Xs (parameter
set in the “Alarm Profiles”). Therefore, the minimum scanning time recommended is 7s + Xs.
ETR alarms
All ETR alarms (Level 1, 2, 3) have a configuration parameter “Nb Errors” which represents the
number of times the ETR error has to be detected, during the OverLast duration, before the associated
alarm start can be triggered. For the following, this parameter is supposed to be set at its minimum
value 1.
The majority of the ETR errors are triggered if certain elements have a repetition interval which is
higher than an “error timeout” duration. For example, the Nit_actual_error alarm is triggered if the NIT
is not present for more than 10s. Therefore, in order to have an alarm start trigger, the scanning time
must be superior to the maximum between the “error timeout” and the initialization phase duration.

Scanning time > MAX ( MAX(error timeout), initialization phase duration)

Moreover, the majority of the ETR alarms have a non-null OverLast parameter, which is also the
duration an alarm remains active after the error stop has been detected. Therefore, the scanning time
must be superior to the sum between the maximum OverLast and the initialization phase duration;
otherwise the alarm stop will never be triggered.

Scanning time > MAX ( MAX(error timeout), initialization phase duration)

+
MAX (OverLast) + initialization phase duration

EdgeProbe Advanced - User Manual – 4.1 – 113 / 120

For default values:
OverLast = 30s, Initialization phase duration = 5s (for 24Mbps bitrate), Max trigger timeout = 10s 
Scanning time: 40s
Recommended values:
OverLast = 10s, Initialization phase duration = 5s (for 24Mbps bitrate), Max trigger timeout = 10s 
Scanning time: 20s
QoS alarms
In order to have the Threshold related alarms, the same configuration as for the ETR alarms is
recommended. The OverLast parameter does not apply to the alarms taken into consideration for the
SAE/SDE parameters.

Scanning time > MAX (error timeout) + initialization phase duration

In order to have the Ratio related alarms, a minimum scanning time of 1m10s is recommended. Ratio
related alarms are computed over periods of several minutes.
Delta Threshold must be superior to the maximum trigger timeout configured for the parameters (NIT,
SDT, PMT, PAT) included for the SAE/SDE parameters.

14.2.3 CONCLUSION: RECOMMENDED SCANNING TIME

Minimum values recommended for the scanning time depending on the bitrate and the measured
parameters:
Alarm
RF & Multiplex ETR Base ETR Advanced (QoS)
Bitrate
DTT and high bitrate 12s 27s 1m10s
Low bitrate 22s 37s 1m20s
(initialization + error
(7s + Xs)
timeout + OverLast)

Important notes:

• The scanning time must not be inferior to the minimum error timeout (ETR, ServiceMissing).
• The scanning time must not be inferior to the OverLast.
• Delta Threshold must be superior to the maximum error timeout configured for the parameters
(NIT, SDT, PMT, PAT) included for the SAE/SDE parameters.

EdgeProbe Advanced - User Manual – 4.1 – 114 / 120

14.3 SFN SYNCHRONIZATION MEASUREMENT

SFN operation requires precise signal synchronization between all the transmitters of each SFN cell.
SFN problems are usually caused by a temporal shift in the DVB-T or DVB-T2 frame actual
transmission time compared to other transmitters in the other SFN cells.
The most common origins of these SFN synchronization problems are:
• A defect in the transport stream feeding the transmitter.
• Faults in the transmitter distribution network. With many devices between the T2Gateway
(DVB-T2) or MIP Inserter (DVB-T) and the transmitters, both equipment and network failures
(faults) could introduce time shifts into the stream. SFN errors might occur if these time shifts
exceed the maximum network delay.
• A modulator that has errors or faults in time synchronization, usually caused by problems with
the time reference such as GPS signal. These errors would cause a temporal shift in the
transmission compared to the reference.
• Modulator loss of synchronization with the transport stream feed to the transmitter (the case
of buffer underflow or buffer overflow).
• Modulator frequency drift. If the center frequency were to drift, due to a fault or some other
cause, after some time (usually a few hours) the frequency drift of the modulator will cause a
temporal shift of the transmission time of the DVB-T or DVB-T2 frame.
• Defective DVB-T/T2 transmitter.
• Faulty GPS receiver.

14.3.1 DVB-T SFN MEASUREMENT

For a DVB-T system, the SFN synchronization is achieved by inserting a MIP (Mega-frame
Initialization Packet) packet in each mega-frame. The MIPN carries a STP (Synchronization Time
Stamp) value, which indicates the starting point of the first packet of the mega-frame N+1; starting
point computed as the difference between the latest pulse of the "one-pulse-per-second" (1PPS)
reference and the actual start time1.
This synchronization mechanism is specified by the ESTI TS 101 191 document. Please refer to this
technical specification document for details.
The EdgeProbe Advanced SFN measurement for a DVB-T system indicates the following parameters:
• External PPS presence: 1PPS signal required as the STS value depends of the pulse of the
"one-pulse-per-second" reference.
• MIP presence.
• SFN Delay: time to receive the mega-frame, see Figure 11:
SFN Delay = [Trec monitoring point mega-frame N – STS mega-frame N (from MIPN-1)]
• SFN Drift: variation of the SFN Delay.

1 ETSI TS 101 191

EdgeProbe Advanced - User Manual – 4.1 – 115 / 120

 Figure 11 Functional description of the SFN synchronization 1

14.3.2 DVB-T2 SFN MEASUREMENT

For SFN synchronization in a DVB-T2 system, the T2-MIP packet is used by a retransmission site to
create a SFN cell on a frequency f 0 from a DVB-T2 RF signal received on a frequency f 1. The
timestamp carried by the T2-MIP provides time synchronization for the repeater (frequency f0), not for
the transmitter (frequency f1).
The T2-MIP packet does not have a deterministic position in the transport stream; its position depends
on the T2 Gateway implementation.
The SFN Drift cannot be computed using the T2-MIP packet.
The TestTree solution for SFN monitoring in DVB-T2 consists in computing the T2-Frame Drift.

T2 Frames
N N+1 ……. N+k N+k+1 N+k+2

Clock

T0 T1 Tk Tk+1 Tk+2

If a T2-Frame is received at time T0, then arrival time of next T2-Frame will be T0 incremented by the
duration of a T2-Frame, which is known.
The T2-Frame Drift algorithm:
• At startup of the SFN Drift process, gets the reception date T 0 (from a real-time clock) of T2-
Frame N and permanently store it. This value represents the reference time. Each reception
date of a T2-Frame can be computed as follows:

1 ETSI TS 101 191

EdgeProbe Advanced - User Manual – 4.1 – 116 / 120

 Tk= T0+k * Durationframe; k ∈ N

• When a new T2-Frame is received, the reception time t can be expressed as:
t= T0 + m * Durationframe + δt
m ∈ N; δt ∈ R and δt < Durationframe

δt is the sum between the uncertainty of the measurement and potential error on SFN
synchronization. δt is the SFN drift value.
• The SFN Drift to monitor is then expressed as:
SFNdrift = Modulo [(t - T0) / Durationframe]

The EdgeProbe Advanced SFN measurement for a DVB-T2 system indicates the following
parameters:
• External PPS presence: 1PPS signal for synchronization, time reference.
• TS lock status.
• RF Drift: the difference between the T2-Frame real reception time t and the theoretical
reception time Tk.
• Reference time: a T0 reception time of the first T2-Frame considered as a reference.

Note: For DVB-T2 only, the T2-Frame drift measurement is not valid if FEF frames are present in the T2 stream.

14.3.3 ISDB-T/TB SFN MEASUREMENT

The ISDB-T system does not deliver the IIP packet as a DVB-T system would deliver the MIP packet.
IIP packets present in multiplex frame are suppressed by the modulator. Therefore, the RF
synchronization of an ISDB-T/Tb signal is computed using the same method as the DVB-T2 RF signal
synchronization, which consists in computing the RF Frame Drift.

RF Frames (OFDM frame)

N N+1 ……. N+k N+k+1 N+k+2

Clock

T0 T1 Tk Tk+1 Tk+2

If a RF Frame is received at time T0, then arrival time of next RF Frame will be T0 incremented by the
duration of a RF Frame, which is known.
The RF Frame Drift algorithm:
• At startup of the SFN Drift process, gets the reception date T0 (from a real-time clock) of OFDM
frame N and permanently store it. This value represents the reference time. Each reception
date of a OFDM frame can be computed as follows:
Tk= T0+k * Durationframe; k ∈ N

EdgeProbe Advanced - User Manual – 4.1 – 117 / 120

 • When a new RF Frame is received, the reception time t can be expressed as:
t= T0 + m * Durationframe + δt
m ∈ N; δt ∈ R and δt < Durationframe

δt is the sum between the uncertainty of the measurement and potential error on SFN
synchronization. δt is the SFN drift value.
• The SFN Drift to monitor is then expressed as:
SFNdrift = Modulo [(t - T0) / Durationframe]

The EdgeProbe Advanced SFN measurement for a ISDB-T/Tb system indicates the following
parameters:
• External PPS presence: 1PPS signal for synchronization, time reference.
• TS lock status.
• RF Drift: the difference between the RF Frame real reception time t and the theoretical
reception time Tk.
• Reference time: a T0 reception time of the first RF Frame considered as a reference.

EdgeProbe Advanced - User Manual – 4.1 – 118 / 120

14.3.4 T2-MI NETWORK DELAY MEASUREMENT

The T2-MI network delay can be measured when the stream is received over the ASI input.
Unlike a DVB-T system, the DVB-T2-MI T2 timestamp packet does not indicate the time when the
packet leaves the T2GW, but the time when the RF frame should be transmitted by the modulator.
The T2-MI T2 timestamp can be:
- Absolute timestamp indicates the absolute time of transmission of the T2 Superframe in
seconds since 01-Jan-2000 at 00:00:00 (date of transmission of the first T2 Superframe).
- Relative timestamp indicates the date of transmission of the T2 Superframe relative to the next
1PPS pulse and is modulo 1s.
Also, the MND (Maximum Network Delay) value is not included in the T2 timestamp packet. Therefore,
the T2-MI network delay measure is possible if the MND value is pre-configured by the user.

Network Delay = (Treception – Tgw)* + Toffset

 Time to Transmit = T2timestamp – Treception
*different Treception/T2timestamp scenarios are taken into consideration

where
Treception: time when Probe receives the Superframe
T2timestamp: extracted from the T2 timestamp packet
MND: user defined value (via web GUI)
Toffset: user defined offset, multiple of 1s, by default 0s (to be used in RELATIVE timestamp mode:
allows to compensate the modulo 1s if the network’s known latency is superior to 1s)

EdgeProbe Advanced - User Manual – 4.1 – 119 / 120

14.4 QOS MONITORING PARAMETERS

The following QoS paramaters are also defined in ETR 101 290 §5.5.1 and §5.5.2. Please, refer to
ETR 101 290 document for exact definition of the parameters. PDF file available here.
Service Availability Errors (SAE): Count the occurrence of error messages for the following
parameters over a defined time interval Delta Τ: TS_sync_loss, PAT_error, PMT_error.
For each time interval Delta Τ, the following parameters are computed (which correspond to the
derivation of the increasing function related to the occurrence of the concerned error messages):
TS_sync_loss (ΔΤ) = TS_sync_loss (T) - TS_sync_loss (Τ−ΔΤ)
PAT_error (ΔΤ) = PAT_error (T) - PAT_error (Τ−ΔΤ)
PMT_error (ΔΤ) = PMT_error (T) - PMT_error (Τ−ΔΤ)
Then Service_Availability_Error value is calculated:
Service_Availability_Error = Max [TS_sync_loss (ΔΤ), PAT_error (ΔΤ), PMT_error (ΔΤ)]
IF (SAE > max threshod)  SAE_T alarm is raised

and display the results over an appropriate period (SAE Ratio Period), e. g. 10 minutes, and calculate
Service_Availability_Error_Ratio as the percentage of time during which the SAE_T alarm is
raised.
IF (Service_Availability_Error_Ratio% > max threshold%)  SAE_R alarm is raised

Service Degradation Errors (SDE): Count the occurrence of error messages for the following
parameters over a defined time interval Delta Τ: CRC_error, PCR_error, NIT_error, SDT_error.
For each time interval Delta Τ, the following parameters are computed (which correspond to the
derivation of the increasing function related to the occurrence of the concerned error messages):
CRC_error (ΔΤ) = CRC_error (T) - CRC_error (Τ−ΔΤ)
PCR_error (ΔΤ) = PCR_error (T) - PCR_error (Τ−ΔΤ)
NIT_error (ΔΤ) = NIT_error (T) - NIT_error (Τ−ΔΤ)
SDT_error (ΔΤ) = SDT_error (T) - SDT_error (Τ−ΔΤ)
Then Service_Degradation_Error value is calculated:
Service_Degradation_Error = Max [CRC_error (ΔΤ), PCR_error (ΔΤ), NIT_error (ΔΤ), SDT_error (ΔΤ)]
IF (SDE > max threshod)  SDE_T alarm is raised

and display the results over an appropriate period (SDE Ratio Period), eg. 10 minutes, and calculate
Service_Degradation_Error_Ratio as the percentage of time during which the SDE_T alarm is
raised.
IF (Service_Degradation_Error_Ratio% > max threshold%)  SDE_R alarm is raised

EdgeProbe Advanced - User Manual – 4.1 – 120 / 120