Eutelsat 36E: reception and sharing setup 2026

The Eutelsat 36E satellite: reception setup is a topic relevant for many owners of Enigma2 receivers. If you are having trouble receiving channels, this guide will help you understand the settings and diagnostics. In this material, I will try to explain how to properly set up reception from this satellite, what parameters to use, and how to solve common problems.

Eutelsat 36E (36°E): what kind of satellite is this and what can be received on it

Eutelsat 36E is a satellite constellation operating at the position 36°E. This satellite offers various channels, including FTA and encrypted ones. The frequencies used in the Ku-band range from 10.7 to 12.75 GHz. For reliable reception, it is recommended to use a dish with a diameter of 60 to 90 cm depending on the region and latitude.

Position 36°E and combined Eutelsat 36B/36C

At position 36°E, the Eutelsat 36B and Eutelsat 36C satellites are located, providing a wide range of TV channels for various countries, including Russia and the CIS countries. These satellites work closely together, allowing for a stable signal.

Ku band and used polarization

Channels on Eutelsat 36E are transmitted in the Ku band using both vertical and horizontal polarization. This allows for optimized reception in different conditions.

What equipment is needed: LNB, receiver on Enigma2, dish diameter

To set up reception, you will need a universal LNB with a stability of 9750/10600 MHz and a receiver on Enigma2. The dish should be at least 60 cm in diameter to ensure a quality signal, especially in regions with low signal levels.

Aiming the dish and transponder parameters

Aiming the dish is a critically important step. First, you need to catch a strong FTA transponder to optimize the signal. I usually start with a transponder at a frequency of 11597 MHz, SR 27500, FEC 3/4, vertical polarization. It is important to monitor the signal level (Signal) and quality (SNR/AGC) in the receiver menu.

Azimuth angles and installation locations, LNB polarization

Make sure the dish is installed at the correct angle. For 36°E, the azimuth angle is about 40° in most regions of Russia. The LNB polarization also needs to be adjusted according to the location, which can significantly affect the signal quality.

Searching for a reference open transponder for aiming

For aiming, it is best to use an open transponder, as it does not require a subscription. This simplifies the setup process and allows you to accurately aim the dish before configuring encrypted channels.

Target SNR, AGC, and BER values

For stable reception, it is necessary to have a margin on SNR. The target SNR level should be above 8 dB, and AGC should be within 60-80%. BER should be below 1E-6 for reliable reception.

Manual addition of a transponder in Enigma2

If your receiver does not detect the transponder, add it manually in the settings menu. Specify the frequency, symbol rate, FEC, and polarization. For example, for a DVB-S2 8PSK transponder, add the following parameters:

• Frequency: 11597 MHz
• Symbol rate: 27500
• FEC: 3/4
• Polarization: V
• Modulation: DVB-S2/8PSK

Setting up reception of encrypted channels via CCcam

Now let's move on to the setupCCcam. The configuration file is usually located at /var/etc/CCcam.cfg. In it, you will specify the connection parameters to the server.

Where the config is located: /var/etc/CCcam.cfg

The file /var/etc/CCcam.cfg contains the settings for connecting to the server. Open it with a text editor such as vi or nano.

Syntax of the C-line for connecting to the server

The format of the C-line looks as follows:C: hostname port username password no { 0:0:0 }. Here you specify the server address, port, username, and password.

Parameters: hostname, port, username, password, additional flags

Each field has its own value.hostname is the address of your sharing server.port is the port, usually 12000.username andpassword are your credentials for access. Additional flags may disable the local map.

Restart the daemon and check the status via the web interface :16001

To restart CCcam, use the commands:killall -9 CCcam to terminate the process and then start it again. You can check the status via the web interface athttp://ваш_IP:16001, where you will see the connection status and ECM time.

Alternative: configuring OScam for 36°E

If CCcam does not suit you, you can use OScam. The OScam configuration files are usually located at /etc/tuxbox/config/oscam/ or /var/keys/.

Files oscam.conf, oscam.server, oscam.user

OScam uses three files for configuration:oscam.conf,oscam.server andoscam.user. Each of them is responsible for different aspects of the configuration.

Connection via CCcam-reader protocol (cccam) inside oscam.server

In the fileoscam.server create a section[reader] with parametersprotocol=cccam,device=host,port,user/password,group. This will allow you to connect to the CCcam server.

Web interface OScam (httpport) and reading the log /tmp/.oscam

Enable the web interface in the section[webif] parameterhttpport. Logs can be viewed in the file/tmp/.oscam, which allows for detailed analysis of OScam's operation.

Comparison of CCcam vs OScam: stability, logging, flexibility

CCcam is easier to set up, but OScam offers better logging and DCW control capabilities. If you need more flexibility and diagnostic options, OScam will be the better choice.

Diagnosis and troubleshooting of typical reception problems on 36E

Now let's look at how to diagnose reception issues. The first problem is the absence of a signal. Check the F-connectors, LNB power, and the 22 kHz band switch.

No signal: check the cable, LNB, and frequency range

The absence of a signal may be related to cable damage, incorrect LNB setup, or an incorrect frequency range. Ensure that the antenna is properly oriented and all connections are secure.

Channels do not open: ECM errors and CAID/Provider ID group

If the channels are encrypted but do not open, check the CAID and Provider ID in the log. Make sure that ECM is sent and DCW is returned. You can use log viewing commands for this.

Picture freezing (FREEZE) and high ECM time

If you experience FREEZE, it may be related to high ECM time exceeding 1000 ms. Causes may include weak SNR on the transponder or network issues.

Conflict between local card and network reader

Sometimes the local card and network reader may conflict. In this case, check which source the signal is coming from — the slow local one or the more stable network one.

How to choose a sharing server/provider: criteria without names

Choosing a sharing server is an important step. Pay attention to low and stable ECM time. The geographical proximity of the server is also important to minimize latency.

Stability of uptime and low ECM time

Ensure that the server operates stably and that ECM time does not exceed 300-500 ms. This will help avoid picture freezing issues.

Support for necessary CAID specifically for 36°E

Check if the necessary CAID and packages for 36°E are supported. This can be done by examining the logs for the required IDs.

Number of hops and locality of servers

Try to choose servers with hops=1 to ensure direct access to the cards. This reduces latency and increases stability.

Trial period and transparency of technical conditions

Look for providers that offer trial access to check service quality before purchasing. Transparency of conditions also plays an important role.