1.627 Sencore-MRD3187-DVBS2

This page describes the device driver and the device window for one DVB-S2 receiver unit in a Sencore MRD3187 device. The Sencore MRD3187 may contain up to two receiver / decoder boards, this driver controls one DVB-S2 receiver board in the MRD. To control two boards in one unit, set up two sat-nms devices with the same IP address, but different 'rds' configuration settings.

Device window pages

The following table shows which device window pages are available with this individual device type. Tool-bar functions not mentioned here are described at the general description of device windows .

• --- Contains the main receiver settings and status display.
• --- Contains the conditional access parameters. See also the remark about RAS and BISS keys below.
• --- Contains the parameters concerning the video, video test output and embedded audio assignment.
• --- Contains the parameters concerning the audio outputs and the selection of the audio signals from the MPEG stream.
• --- The faults page.
• --- The device info page.
• --- The maintenance page. The configuration parameters described below are set at this page.

Configuration parameters

At the maintenance page of the device window there are a couple of configuration parameters which must be set to make the software talk to the MRD3187.

• parameter --- description

• address --- The SNMP address specification for the device. The full address specification consists of the following fields:aaa.bbb.ccc.ddd:pppp read-community write-community

  • aaa.bbb.ccc.ddd --- The IP address of the device in 'dotted quad' notation. This field is mandatory.
  • pppp --- The IP port number where the device accepts SNMP requests. The port number may be omitted, the driver uses the standard port 161 in this case.
  • read-community --- The SNMP read community name. This must match the read community expected by the device.
  • write-community --- The SNMP write community name. This must match the write community expected by the device. The write community name may be omitted, the driver uses the read community name for both, read and write in this case. If both community names are missing, the driver uses 'public' as a default for read and write community.

• rds --- Addresses the RDS DVB-S2 receiver in the MRD unit (1/2). To control both IRDs in one unit, set up two sat-nms devices which use the same IP address, nut one configured to rds=1, the to rds=2.

• loFreqHigh --- The LO frequency for the high frequency band. The software sets the appropriate LO frequency every time before it changes the receive frequency.

• loFreqLow --- The LO frequency for the low frequency band. The software sets the appropriate LO frequency every time before it changes the receive frequency.

• bandEdge --- The frequency where the software switches the LO frequencies.

• ebnoMin --- This value is used to compute in the driver a link margin from the Eb/No reading provided by the device. The displayed margin value is (Eb/No - ebnoMin).

• readBackDelay --- Delays the read back of a parameter actually set for at least the given delay time. This shall ensure that the device has processed the new parameter before it is read back. You should leave this parameter at it's default setting.

• deviceComment --- An optional text entered here appears as an addition to the tooltip which is shown while the mouse is placed over a device icon in the GUI. The "\n" character sequence is translated into a newline character, splitting the text into multiple lines.

Remarks

The Sencore MRD3187 provides no means to translate frequency settings with a LO frequency. Hence, the frequency translation has been entirely implemented in the driver: At the sat-nms GUI the receive frequency is set as "true RX frequency", the Sencore WebGUI shows the L-band receive frequency.

As the LO frequency selection is not coupled to a switch or LNB supply setting, the sat-nms device driver does not know which LO frequency to use at system startup. For this reason the sat-nms GUI shows the actual L-band receive frequency after system start, as long as not receive frequency has been set by the operator.

Variables defined by this device driver