Académique Documents
Professionnel Documents
Culture Documents
ISDB-T/Tb
User Manual
Revision 3.1
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 ENENSYS’ Technical Support at
support@enensystest.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 TESTSYSTEMS 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.
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
Power consumption
20W
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).
Before proceeding, please check that the box contains all of the following items:
• 1x EdgeProbe Advanced device
• 1x Power cable
If any item is missing or has defects, do not install the device and contact our Technical
Support team via email support@enensystest.com.
EdgeProbe Advanced offers a simple front panel with the following information:
• 1x Power led:
o If the device contains one Power Supply (“RedundantPowerSupply” option
deactivated):
LED is green if the Power Supply operates properly
o If the device contains two Power Supplies (“RedundantPowerSupply” 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: LED turns green if equipment is 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 with Warning level has raised
o LED turns red if at least one alarm with Critical level has raised
• 1x GPS led:
o LED is green if the “InternalGPS” option is activated and the GPS receiver
is locked. The internal 1PPS signal is generated
o LED turns red if the “InternalGPS” option is activated and the GPS receiver
is not locked. The internal 1PPS signal is not generated
o LED is OFF if the “InternalGPS” option is deactivated. The internal 1PPS
signal is not generated
The rear panel features all physical interfaces used to connect the EdgeProbe Advanced
to the network for controlling and monitoring it, to process the incoming RF, ASI or IP.
Depending of the options, you can have up to 4 units:
Unit 2 Unit 1
• Unit 2 with:
o 1x RF input (N-type female – 50 Ω) for receiving RF signals
o 1x ASI input/output (75 Ω, BNC female):
Input for MPEG-2 TS baseband signal
Output for the analyzed MPEG-2 TS
o 1x Gigabit Ethernet data interface (RJ45):
MPEG-2 TS input and output (IP forward of the analyzed stream)
• Unit 1 with:
o 1x RF input (N-type female – 50 Ω) for receiving RF signals
o 1x ASI input/output (75 Ω, BNC female):
Input for MPEG-2 TS baseband signal
Output for the analyzed MPEG-2 TS
o 1x Gigabit Ethernet data interface (RJ45):
MPEG-2 TS input and output (IP forward of the analyzed stream)
Connecting the EdgeProbe to its own antenna on the TX is not a good solution because
signal is not stable near the TX. The best is to connect the RF cable of the EdgeProbe
directly on the back of the transmitter where normally you have a directional coupler, as
seen in the picture below:
Use an Ethernet cable (RJ45 plug) to connect EdgeProbe Advanced's “Control” port to
the control network.
1. Plug the power cable into the power receptacle on the back panel. Then, connect
the other end of the cable to main power.
2. Use the On/Off switch to power the EdgeProbe Advanced. Allow the EdgeProbe
Advanced 1’30’’ to initialize and start.
3. 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
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…
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 “5 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.
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.
Device Alarms: provides status of alarms specific to the device.
Profile management: Allows loading and saving configuration of the device.
The User’s Manual provides detailed information on the configuration and monitoring
provided by the EdgeProbe Advanced. It can be accessed from the embedded web server.
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’s Manual on your computer.
You can also get the User’s Manual from our Privileged Area website:
http://privileged.enensys.com
The current name, location, serial number and firmware version used on the EdgeProbe
Advanced are available from the “About” tab in the “Information” box. Name and
locations can be changed by the operator.
There are two possibilities for the EdgeProbe Advanced firmware upgrade:
• Via the GUI, “About” tab, “Device Update” tab
• Via FTP transfer of the update file
Please refer to the paragraph “12 Updates and Privileged Area” for details regarding the
new firmware versions retrieval.
Note: An eventual active stream record is automatically stopped if a firmware upgrade is launched
via the GUI.
To upload a firmware upgrade file on the EdgeProbe Advanced remotely via a FTP
connection:
1. Open a FTP connection to the device. Please refer to the ENENSYS TESTSYSTEMS
support team in order to obtain the FTP credentials (support@enensystest.com).
2. Copy the firmware upgrade file in the “updates” distant folder. The device will
automatically detect the new 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 GUI manipulations are forbidden.
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. 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 ( ).
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.
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.
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.
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).
Information on current date and time and RTC settings are available in the status bar.
• 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:
The icon presets the field Date and Time with the current time of the RTC
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
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.
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 GPS 1PPS presence: presence of the 1PPS signal generated by the
internal GPS receiver.
- GPS signal presence: presence of the GPS antenna signal at the device’s specific
input; available if the “InternalGPS” option is activated and only on Unit 1.
- Power Supply 1: available if the “RedundantPowerSupply” option is activated.
- Power Supply 2: available if the “RedundantPowerSupply” option is activated.
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.
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.
Logs files contain the list of events: alarm triggers on/off. The Logs tab gives access to
the log files configuration:
- Activate/Deactivate logs storing.
- 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 Trends
Trends files contain the list of RF parameters measured values. The Trends tab gives
access to the log files configuration:
- Activate/Deactivate trends storing.
- 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.
Records 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.
- Allocated space: maximum storage allocated for the logs files, up to 10 GB or
the internal memory card’s capacity. When this limit is reached, the TS recording
is automatically stopped.
- Currently used: indicates the memory space already used by the recordings files.
- Logs: containing events logs. In the Logs tab, activate the logs storing, configure
the allocated space for this type of files and the maximum file size. By activating
the “Day mode” parameter, a new log files will be systematically created at
00:00:00 upon date change.
- Trends: containing the RF parameter measurements. In the Trends tab, activate
the trends storing, configure the allocated space for this type of files and the
maximum file size.
- Records: containing TS stream recordings. In the Records tab, activate the
records storing, configure the allocated space for this type of files. Use the Record
(TS Mode) button from the bottom status bar in order to start/stop the TS
recording.
Use the Record (TS Mode) button from the bottom status bar in order to start/stop a
TS recording. An ongoing TS recording will be automatically stopped if the maximum
allocated size for the TS record files has been reached.
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:
o RF
o ASI
o IP
o ETR 101 290 Priority 1
o ETR 101 290 Priority 2
o ETR 101 290 Priority 3
o T2-MI
o MIP
o Advanced
o SFN
o Echoes
o Multiplex-Services
o EWS (future use)
For each alarm managed by EdgeProbe Advanced, user can enable the alarm, enable
SNMP trap and dry relay. It can also define the alarm severity.
- “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 monitoring, many errors can be raised in a short period of
time. In order to prevent from flooding the Network Monitoring System with alarm on/off
traps, EdgeProbe Advanced provides an alarm trigger on occurrence mechanism:
- An alarm will be raised if an error occurred at least “Nb Errors” times 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.
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 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
RF settings for an alarm profile are available through the RF tab of the Alarm Profiles.
ASI settings for an alarm profile are available through the ASI tab of the Alarm Profiles.
IP settings for an alarm profile are available through the IP tab of the Alarm Profiles.
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.
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
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.
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
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.
Check 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
T2-MI settings for an alarm profile are available through the T2MI tab of the Alarm
Profiles.
Please, refer to ETR 101 290 document for exact definition of the parameters. PDF file
available here1.
1 http://www.etsi.org/deliver/etsi_tr/101200_101299/101290/01.03.01_60/tr_101290v010301p.pdf
MIP (Megaframe Initialization Packet) settings for an alarm profile are available through
the MIP tab of the Alarm Profiles.
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 here, or to
the appendix paragraph “14.4 QoS monitoring parameters”.
SFN settings for an alarm profile are available through the SFN tab of the Alarm
Profiles.
Please refer to the appendix paragraph “14.3 SFN synchronization measurement” for
details concerning the SFN synchronization mechanism and measurements.
Channel Impulse Response settings for an alarm profile are available through the Echoes
tab of the Profile Configuration.
Multiplex-Services settings for an alarm profile are available through the Multiplex-
Services tab of the Profile Configuration.
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 for further information.
To access the Channels Settings management, select the “Settings” tab of the Menu
and then the “Channel Management” sub menu.
The EdgeProbe Advanced can monitor the following type of input channels:
- RF input channels of type DVB-T, DVB-T2, DVB-C, DVB-C2, ISDB-T
- IP input channels
- ASI input channels
No particular configuration is required for an ASI channel. For each ASI channel, an
alarm profile should be provided.
Note: when a parameter of a channel is modified, EdgeProbe Advanced restart the monitoring
process, even if Scanning mode is used.
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.
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)
Please refer to the appendix paragraph “14.2 Scanning recommendations” for details
regarding the recommended scanning durations.
Note: when the list is modified, EdgeProbe Advanced restart the Scanning monitoring.
Note: when the list is modified, EdgeProbe Advanced restart the Scanning monitoring.
To access the Output management, select the “Settings” tab of the Menu and then the
“Output” sub menu.
The “IP output” functionality enables the MPEG-2 TS stream (monitored from the RF or
ASI input) to be forwarded on the IP data port of the EdgeProbe Advanced. VLAN tagging
is supported.
The Output tab provides the “Output Management” panel for enabling the IP output
mode and configure the IP address, port and if applicable the VLAN ID and priority.
6.1 Overview
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 .
Note: to quickly access to the details of alarms, click on the counters of the channel. This will
open the Alarm View for this channel.
To access the Alarm View panel, select the “Alarm View” menu in the main menu or click
on an alarm counter in the Network View.
Alarm View displays details of alarms for a specific channel. You can select the channel
using the “Channel Selection” . This list provides access to device specific alarms and
monitored channels.
The “Alarms” panel provide current state of all alarms for the selected channel.
Reset all counters of alarm condition for the selected channel. Please
note that this only reset counters, not current state of the alarm.
To access the Monitoring View panel, select the “Monitoring” menu in the main.
Channel view displays real-time values of RF measurements and the modulation of the
currently monitored channel.
SFN view displays real-time values of the SFN Drift measurement of the current
monitored channel.
Frequency view displays real-time values of the Frequency Drift measurement of the
current monitored channel.
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.
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.
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 system indicates the following
parameters:
• T2-Frame 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.
Please refer to the appendix paragraph “14.3 SFN synchronization measurement” for
details concerning the SFN synchronization mechanism and measurements.
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.
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.
- 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 Echoes panel. The echo alarm configuration made in this mon-
itoring view is associated to the alarm profile active for the current channel being
monitored.
The echoes alarms are configurable via the Settings Alarm Profiles panel Echoes
tab (see also paragraph 5.1.12 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).
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.
The T2MI 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.
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.
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.
GNSS 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.
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 ena-
bled; see “4.8 Setting the Memory Management” paragraph for configuration and
“6.3.8 Data Storage monitoring view” paragraph for log files retrieval.
For more information about firmware update availability, please contact ENENSYS
TESTSYSTEMS support team (support@enensystest.com).
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).
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 state).
“alarmAdvancedConfig” contains the OIDs which
enable the alarms’ thresholds configuration.
“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.
“testMonitoringLine” provides access to the
device’s monitoring configuration (“configuration”
file) and monitoring parameters (“statistics” file).
The device’s monitoring parameters are
structured in three categories:
- “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.
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. Your
equipment will be shipped back to you along with a repair report.
This paragraph presents a few detailed uses cases for the ETR 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 pe-
riod in order to trigger the alarm start
• OvertLast (T): the duration an alarm remains active after the error stop has
been detected.
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 9 Alarm lifecycle during scanning: alarm duration < channel scanning time
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.
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.
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.
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.
Minimum values recommended for the scanning time depending on the bitrate and the
measured parameters:
Alarm
RF & Multiplex ETR Base ETR Advanced (QoS)
Bitrate
TNT 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, Ser-
viceMissing).
• 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.
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.
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 mega-frame N – STS mega-frame N (from MIPN-1)]
• SFN Drift: variation of the SFN Delay.
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 algorithm:
• At startup of the SFN Drift process, gets the reception date T0 (from a real-time
clock) of T2-Frame N and permanently store it. This value represents the reference
• 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.
• T2-Frame 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.
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 differences are calculated (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 (∆Τ) ]
and display the results over an appropriate period, e. g. 10 minutes, and calculate
Service_Availability_Error_Ratio as the percentage of time for which the parameter
exceeds a pre-defined threshold.
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 differences are calculated (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 (∆Τ)]
and display the results over an appropriate period, e. g. 10 minutes, and calculate
Service_Degradation_Error_Ratio as the percentage of time for which the parameter
exceeds a pre-defined threshold.