Troubleshooting tips for anyone using the EUMETCast system.

Before installing your EUMETCast Client Software and EKU, we recommend that you read the relevant tips below and also the read me files contained on the accompanying CD ROM.

PLEASE NOTE: EUMETSAT is providing User Service Helpdesk support for EUMETCast in general and specifically for the integration of the Tellicast and EKU software. The additional components contained in the EUMETCast package, such as DVB drivers, DVB software and tools, are provided on best effort to facilitate the installation. We may not be able to assist you with system-specific problems if you are not using recommended devices and because of the large variety of hardware, operating systems and application software available. If a manufacturer has installed your reception station, please seek assistance from them first if your equipment fails.

Please refer to the installation guides and this troubleshooting guide first before contacting the Helpdesk.

Reception station components recommended by us

A) General

If you have an issue please follow these steps first:

  • A1) set in recv.ini file:
    • log_level=verbose
  • A2) continue reception for a few hours. then send us following files
    • recv.ini
    • recv-channels.ini
    • recv.log
    • recv.log.1
  • A3) send us a screenshot
    • of task manager ("processes" and "performance" tab)
    • open the Tellicast shell (double-click the T icon)
    • select License
    • send us a screenshot of this page
  • A4) answer following questions
    • what is the source of the EUMETCast reception station installation? (e.g. VCS, UKW-Technik, EUMETSAT CD & version, ...)
    • antenna size & DVB band used (C or KU band)
    • version of the Tellicast software? (latest version is 2.4.0a)
    • Operating system & version? (W2K PRO, XP PRO, ME, Linux RH 9 kernel ..., etc)
    • eToken (EKU) runtime environment (check installed programs in the control panel), please provide a screenshot of installed programs
    • used DVB card, version of the DVB card software? (e.g. Skystar2 software V4.2.8)
    • when did the problems start? (from the beginning, at installation, when EKU was installed, etc.)
    • what are the symptoms? (e.g. reception works fine, stops after 30min, EKU light off, EKU properties not visible)
  • A5) Installation Problems

    Please use the installation guides provided on the EUMETCast CD.

    for windows:


    for Linux:


    If you encounter a problem, then please refer to the point in the guide where the problem occurs, and send screenshots if possible.

B) Windows™ problems

B1) EKU or username/password problems on Windows: "missing key" or "Failed to decode key" or no reception at all


  • The DVB reception software is correctly configured and the Tellicast shell "Active Channels" page shows the Announcement channel in active state with Received Bytes incrementing.
  • No data or only a limited set of data is received

Check the following conditions:

B1.1) No data received and no messages written to the Tellicast Shell "Log File" page


The username might be wrong or data channels inhibited in the DVB or network setup

To check the username, use a generic user, open the recv.ini file of the reception software (located in the Tellicast installation directory) and replace the lines "user_name..." and "user_key..." with the following lines:
(use exactly this syntax)
You don't need to reinstall the Tellicast software to change the username/userkey
Now check if files can be received. There should be files every 15 min.
This username only allows reception of six-hourly MSG image data.

If this is successful, go to B13 or confirm the username/password with our User Service Helpdesk.

If unsuccessful, try other sections in the troubleshooting guide.

B1.2) Receiving only a sub-set of data


- Tellicast shell "Active Channels" shows only unencrypted Channels, e.g. SAF channels as active
- Getting the unencrypted SAF data e.g.:


- This is a sign that either the password is not correct in the recv.ini or that the EKU is not working for some reason (e.g. software not installed correctly or EKU broken).
- It is known that the usage of "Windows Remote Desktop" will stop the communication to the EKU. Using it will show "missing key" symptoms and cause loss of reception. If you want to remotely connect to the PC, we recommend to use the freely available VNC software which provides the same functionality. This can be downloaded from
Check if the correct password was entered, see B13 for details. If the problem is stil present, continue with the next step.

B1.3) Check the EKU (key) functionality

- remove the key from the PC
- (re-)install the run time environment Rte_3_51.msi (or later), follow the instructions on the CD
(RTE_3_51 or later is located on the EUMETSAT CD under Windows\EKU_software)
- plug in the key, a red light on the key should come on
- open menu/Settings/Control Panel/administrative tools/services (can also be located one directory higher), check if "Smart Card service" is running (the name can be slightly different).
- if it is not running, start the service and repeat this step (B1.3)
- make sure that this service is set to "Automatic" in order to start at boot time

- open menu/Programs/etoken Properties, you should be able to see the key name and some properties (see also error B12)
- if you see the following, the key is broken and must be replaced
Name <this is completely blank>
Type PRO (Card OS/M4)
FW Version (0x8514)
User Not present
Administrator Not present

- please send us a screenshot of this window to verify the status

Check communication with Tellicast software
- disconnect the antenna cable from the DVB receiver card or box
Note: to distinguish a wrong password from EKU problems, Tellicast must be running without active Announcement channel

- start the Tellicast reception software
- open the Tellicast shell (double click the T icon)
- select License
under "Client Identification" you should see the selected username and 4 host_key.. parameters, check if you see the following

host_key_4: ****-****-****-****

if not, the Tellicast software cannot see the key
- send us a screenshot of this page

If all prior checks were successful and the host_key_4 is blank ("-"), the EKU must be replaced. Please send us the following files together with the problem description:

Don't forget to plug in the antenna cable again after the troubleshooting.

B2) Problems after the transponder change (change of frequency)

  • check signal quality, has it dropped significantly?
  • If after the switch over data acquisition does not restart, please check that your service channel PIDs are still correctly set.

B3) Can't display throughput on Tellicast Client "Overview page"

  • check signal quality, has it dropped significantly?
  • If after the switch over data acquisition does not restart, please check that your service channel PIDs are still correctly set.

Although EUMETCast does work perfectly on XP (Home or Pro), a lot of members cannot display the throughput graph in the Tellicast client overview.

Some testing was performed and a missing Java module in IE explorer was discovered. It seems that Microsoft had a dispute with Sun on the Java virtual machine and does not include it in XP or later products anymore. (see

The solution is: (tested on XP Pro)

  • Search the Microsoft Java virtual Machine build 3805 on the web and install this full version. (look for file like "msjavx86.exe"). Because of the lawsuits with Sun, you won't find it on Microsoft's support site.
  • Once installed you do need to upgrade to build 3810 because of severe security risks in the old build.
  • Either find file "msjavwu.exe" on the web and install this or perform a "Windows™ Update"

Please note that installing this build 3810 will only update an existing JVM, and will abort with an unknown error if JVM was not installed before. As alternative you could download and install the Sun Java Virtual Machine (not tested).

B4) Missing channel(s) on Skystar 2 cards under Windows™

Right-click on the antenna icon and select "EUMETCast". There is also a T-Systems entry, but with different PIDs. This is probably an oversight from Technisat when they defined the database.

If the EUMETSAT provided Skystar driver (V4.3.0) is installed, all PIDs are already preselected.

B5) Cannot install/upgrade or uninstall Tellicast Software


The message "unable to locate the installation log file 'C:\program
Files\Technisat DVB\Uninst.isu' installation will not continue." or similar appears. The software cannot be installed. This can happen if the systems crashes during an upgrade or if the registry is corrupted.

  • Open the registry editor and search for "BusinessTV-IP".
  • Delete the keys


HKEY_LOCAL_MACHINE\SOFTWARE\Wise Solutions\Wise Installation System\Repair\C:/Program Files/T-Systems/BusinessTV-IP/INSTALL.LOG

B6) Skystar2 cards: "Interference" with ARAB NET on Windows

The antenna icon is green but no connection to announcement and data channels in Tellicast software. ARAB NET may be displayed as the Network. Please upgrade to Skystar driver and software version 4.3.0. CD is available from EUMETSAT.

B7) Reception only when connected to the internet (Windows systems)

This is caused by a firewall setting that allows incoming traffic only when connected to the internet. Enable the DVB network interface as trusted device in the firewall configuration.

B8) No reception and "wrong interface address" after installation of a new DVB card/box


No reception after installation of a new DVB card or USB box. Following messages in recv.log: "... wrong interface address ..."


The hardware entries for previously installed hardware stay in the windows registry, regardless of whether the device is physically present or not. Since the DVB device is a network interface, it occupies a given IP address. An IP address cannot be assigned to more than one network interface.


Open Control Panel - System - Hardware - Device Manager

  • Under "View", select "hidden devices"
  • Uninstall all DVB network interfaces
  • Reinstall the DVB card or USB box
  • Check/set the IP address of the DVB network interface (Control Panel - Network Connections)
  • Right-click the DVB device, then select Properties - Internet protocol(TCP/IP) - Properties
  • Set the IP address. It must match the address in recv.ini (normally
  • Subnet mask must be
  • Other parameters (DNS, gateway) need not be set

Alternative solution: If you cannot uninstall the hidden device, just use a different IP address:

  • Set the IP address of the DVB network interface (Control Panel - Network Connections)
  • Right-click the DVB device, then select Properties - Internet protocol(TCP/IP) - Properties.
  • Set the IP address, e.g.
  • Subnet mask must be
  • Other parameters (DNS, gateway) need not to be set.
  • Open the Tellicast client configuration file recv.ini
  • Set the same IP address: interface_address=

B9) No files received or many T icons in taskbar


Signal level and DVB reception looks ok.
No files are received.
Following messages in recv.log: "ERR:2005-06-02 06:50:24.771:Cannot create file ..."


Either the disk is full, or a file system is used that limits the number of directory entries (FAT, FAT32)


Install a disk maintenance program.
Use NTFS on Windows system.

B10) Problems opening Tellicast shell

After right-click or double left-click on the "T" icon Microsoft Internet Explorer may prompt you to "Work Offline" or "Try Again." See following article from the Microsoft knowledge base: Microsoft Support

B11) Skystar2 cards: "Interference" with CYFRA on Windows


The antenna icon is green but no connection to announcement and data channels in Tellicast software. CYFRA may be displayed as the Network.


Due to tolerances in manufacturing the DVB card locks to the next transponder.


Shift the downlink frequency up in steps of 5 MHz until the card locks to the correct transponder. See document EUM TD 15 (Annex A) provided with the installation CD on how to perform this change.

B12) Error in eToken Properties


When you try to run the eToken Properties application after installing the eToken drivers, a "Failed to load etoken.dll" or "Cannot initialize eToken.dll" errror may occur.


This is usually caused by a Service error.


To check the Service:

  • Click Start, Settings, Control Panel, Administrative Tools, then Services.
  • Locate the Smart card service.
  • Verify that the Service is Started. Ideally, the startup type should be set to Automatic.
  • Locate eToken Notification Service.
  • Verify that the Service is Started.

After verifying that both services are set to Started, check to see if the eToken Properties application still shows an error with the etoken.dll. If it does, there may be a permissions error. If either service fails to start or the problem persists, contact your IT Help Desk or Computer Support person for assistance

B13) Problems with entering a new username/password


The reception stops or does not work at all after entering new username/password


The username/password was incorrectly entered


At first installation the username/password given by EUMETCast in connection with the EKU has to be entered when installing the Tellicast software. During installation a window will open and ask for the information. In this case the parameters user_name= and user_key_crypt= will be added to the file recv.ini.

If Tellicast is already installed, then open the file recv.ini and enter the following two lines:
user_name=... (replace "..." with the username given by EUMETSAT)
user_key=... (replace "..." with the password given by EUMETSAT)

Remove the old "user_name=..." and "user_key_crypt=..." entries.

Never attempt to change the password in the etoken properties, this might damage the EKU!

B14) Tellicast problems under Windows 98 and/or ME


One or more of the following symtoms are observed on Windows 98 or Windows ME systems:
- The installation fails or returns an error message.
- Startup of the Tellicast client fails with the following error message
The TC-RECV.EXE file is linked to missing export
- Startup of the Tellicast results in red icon and double-click on the icon shows "Attention, No License" message


The Tellicast client 2.4.4b is not compatible with some elements of Windows 98 and Windows ME


Tellicast client 2.4.4a will solve the problem, it is available from our User Service Helpdesk.

B15) Tellicast no reception while all DVB reception parameters seem ok


- The T icon in the tray is always yellow.
- The DVB reception parameters appear to be correct, i.e. signal lock ok, PIDs correct, icon green.


The transfer of multicast packets from the DVB interface to the Tellicast client is inhibited, either by the firewall, or by an incorrect internet setting, e.g. proxy server entry, or an incorrect data service is selected when using the Skystar2 card.


- Switch off the firewall, if enabled.
- Check the proxy server setting under Control Panel - Internet Properties - Connection - LAN Settings:
If there is a proxy server entered, delete it, even if not enabled:
Check "Use a proxy server ..."
Delete any proxy server entry
Un-check "Use a proxy server ..."
- Skystar2 cards: Right-click on the antenna icon and select "EUMETCast::<name>", where <name> is the satellite used for reception. The EUMETCast entries will only appear if the Skystar driver and reception software from the EUMETSAT CD is installed.

B16) Cannot delete received files if using tmp_directory


- Files received on a reception station cannot be deleted from another station when using a network share
- This seems to happen more frequently (or only) if a tmp_directory is configured in either recv.ini or recv-channels.ini


This is related to a Microsoft Windows OS problem.


- see
- on XP, install SP2 or later on both, the receiving and sending PC

B17) Frequent Windows crashes or hangups


- The systems hangs, freezes and may have to be powered off/on to get it working again
- Uninterrupted operation is only possible for short periods (minutes to several hours)


Operating system drivers or application are not compatible with Tellicast. Some applications or services put too much load on the system in connection with Tellicast.


Please apply one of the following steps at a time, then check if the problem still exists.

1. Disable unnecessary Microsoft services/applications e.g. turn Off Indexing for the EUMETCast data directories or disks

Open My Computer ( press the Windows & E keys)
- right-click on each drive and choose Properties
- under the General tab, un-check the box that says Allow the Indexing Service to
index this disk for fast file searching
- a window will pop up, make sure the box is checked that says Apply change to
(drive letter):\, subfolders and files and click OK. Windows will apply the changes,
click OK. reboot.

2. Drivers, e.g. the graphics driver, can install additional control applets which should be disabled.
Stop following processes from running (check one process at a time and see if the problem still exists):


To disable permanently:
- Click | Start | Run | and type msconfig on the text box and click the OK button to start MSCONFIG
- Click the startup tab
- Uncheck the check boxes of the programs you want to not run

3. Dual core CPUs:
Install latest Java version.
Disable hyperthreading mode in the BIOS.

4. Install OS/applications and EUMETCast received files received on separate physical disks.

5. Disk should all be NTFS.

B18) DVB card hangup under Windows


Occasionally, when the DVB stream is interrupted due to an uplink problem, the DVB reception card or box stops receiving data and does not resume automatically.


Skystar2 cards under Windows and Linux and Pent@Value cards under Linux are sensitive to interruptions of the DVB stream. Some configuration information is lost. This might be a driver and/or a hardware problem. The cards have to be reinitialised to get it working again.


Several methods can be used which are all described in the following link The solution described here works for all DVB cards and boxes starting automatically after login.

Windows logoff-logon method (works reliably on XP/2000):

1. Prepare an account with administrator privileges, under which DVB reception is running.
Create a password for this account.
Install the DVB reception software to automatically start after logon.
Install TelliCast (NOT as a service, it will start from the startup folder).

2. Restart the PC to test if reception automatically starts after manual login.

3. Use Tweak UI (can be downloaded from Microsoft for each Windows version) to enable autologon:
Open Tweak UI - Logon - Autologon, then select username and password - Apply.
Tweak UI 2.10 for Windows XP
Tweak UI 1.33

Use version 1.33 for Windows 2000, (to install, unpack files, then right-click tweakui.inf - Install)

4. Reboot system to test if reception automatically starts after automatic login.

5. Configure automatic logon after logoff

Write the following three lines into a file named autologon.reg:

Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon]

Run autologon_XP_2000.reg (double-click)

6. Create a file "restart.bat" in the TelliCast working directory and put the following single command into the file, depending on the Windows version:

if the system is Windows XP: logoff
if the system is 2000: logoff /n /f

Test the command and batch file before proceeding to the next step.

Note: on Windows 2000 systems you might have to install logoff.exe from the Windows 2000 or NT resource kit

7. Add the following two lines under [watchdog] in recv.ini and restart TelliCast:


Note: While working interactively on the reception station with restart enabled, the automatic logoff — if triggered — will close all applications immediately and interrupt the interactive work. Therefore, please disable the automatic restart (step 8) if you want to work in the running account, or log in to a different account using the "fast user switching" capability on Windows XP. User sessions running in parallel will not be logged out.

8. To disable the automatic restart, edit recv.ini the following way and restart TelliCast:


9. To disable autologon, undo step 3:
Open Tweak UI - Logon - remove Autologon check mark - Apply

10. The ForceAutoLogon setting will only be active if autologon is enabled. To disable this setting in the registry, repeat step 5 but use "ForceAutoLogon"="0"

B19) Vista Problems — Tellicast cannot connect to DVB interface


TelliCast fails to work, being either stuck in the yellow T-icon state or, if the network cable is connected after the system was working, the icon alternates between the "pink" and "red" states.


This is related to the default multicast entries in the TCP/IP routing table. On previous Windows operating systems, the entry into the TCP/IP routing table was added automatically.


- To solve this problem, you need to tell Vista that the addresses handled by the DVB software must always be reached through the address which you set up in DVB card installation (normally In the Start menu, All Programs, Accessories menu, you will find an item named Command Prompt. Right-click on this item, and select Run as administrator. Enter the following command:
route -p -4 ADD mask

- then restart the PC

NOTE: if the DVB interface is on another IP address, use that address instead of

B20) Vista Problems


Changing recv.ini does not seem to have any effect, cannot find


Windows Vista no longer allows programs to write in the C:\Program Files\ directory.


The default (Microsoft) solution is to virutalise the Program Files directory for each user. This means that while the .exe files stay in C:\Program Files\, anything which is written goes into a virtual store called:

C:\Users\<name>\AppData\Local\VirtualStore\Program Files\.....

and this is done transparently for the user. However, it can mean that there are two copies of the files, and, hence, causes confusion.

Check in "C:\Users\<name>\AppData\Local\VirtualStore\Program Files\T-Systems\BusinessTV-IP" and see if the "real" files in here. Hopefully the log files and data files will be here.

Note: You need to have "display hidden files and folders" selected.

B21) eToken PKIMonitor frequently asking for password


After installation of EKU software (PKIClient) version 4.5 or later from time to time Etoken pops up a window requiring the password.


The PKIMonitor is running, however this feature is not used by the EUMETCast software


Disable the PKIMonitor with msconfig
- start - run, enter "msconfig", ok
- select the Startup tab
- disable "PKIMonitor", ok
- reboot the station
- after reboot a window will come up showing that something was changed,
check "Don't show..." and accept, close the open window and reboot again


Note: see also related entry (D15)

B22) Increased file losses after migration to EUTELSAT 9A with Skystar-2 DVB cards


Increased file losses after the EUTELSAT 9A upgrade package was applied on a Skystar-2 card


- the upgrade enables all EUMETCast PIDs on the DVB card
- driver and software version 4.3.0 cannot cope with the complete data rate and drops packets


Option 1: upgrade the DVB driver and software to version 4.4.1 (part of the EUMETCast CD)
- get the latest CD from EUMETSAT (CD 5_4)
- open the device manager(control panel - system - hardware - device manager)
- select the DVB card under "Network Adapters" and upgrade the driver, point to the 4.4.1 directory on the CD
- uninstall the DVB software
- install version 4.4.1 from the EUMETCast CD, follow the provided instructions

Option 2: remove unwanted PIDs in setup4pc

B23) Tellicast no reception while all DVB reception parameters seem ok, unable to control Windows firewall


- the T icon in the tray is always yellow.
- the DVB reception parameters appear to be correct, i.e. signal lock ok, PIDs correct, icon green.
- the Windows firewall cannot be switched on or off, the Windows firewall service cannot be started


- the winsock settings are corrupted, possibly due to an incorrect installation of software.
- this inhibits the firewall services and control.


Step 1: follow the instructions in To reset the winsock settings.
Step 2: if Step 1 didn't solve the problem, repair the WMI repository. See then repeat Step 1.
Step 3: open Control Panel - Administrative Tools - Services. Start the service "Windows Firewall/Internet Connection Sharing (ICS)"

The firewall can now be controlled again and can be configured to allow Tellicast reception. See B24.

B24) Configure Windows Firewall to allow Tellicast reception


If the firewall is switched on, it stops multicast traffic from the DVB interface to Tellicast.


- open Control Panel - Network Connections
- right-click on the name of the DVB interface ("Local Area Connection .."), select Properties
- click the "Advanced" Tab and select "Settings" in the Windows Firewall section
- A "Windows Firewall" window opens, click the "Advanced" tab
- un-check the DVB network interface ("Local Area Connection ..") under Network Connection Settings
- accept changes and close open windows, reception should immediately start

B25) Wrong satellite after startup on Skystar2 cards


After a restart of the PC the Skystar card connects to the wrong satellite


The initial locking transponder is not correct, either not saved or not set.


- right-click the antenna icon, select the correct satellite and service
- make sure Tellicast is receiving data
- double-click the green antenna icon, select the correct satellite (currently used satellite)
- click the "Data services" button
- under "Transponder" select the correct satellite/transponder
- click "Edit"
- check "Initial locking transponder"
- accept all settings with "OK", "OK" "Close"
- restart the PC to check if the right transponder is selected at startup

B26) How to use Skystar II cards on Windows 7

Support is provided in EUMETCast package V 5_8 or later.

B27) Losses due to excessive scheduled tasks/services running under Windows


Messages in the recv.log containing the string "Missed parts of file" at specific times (typically around 01:00 and on Sunday mornings)


Windows (7 and 8) has many scheduled tasks and services that can "hog resources" and so lead to data losses at certain times of the day/week.


The exact settings are left up to the user as it depends on the level of losses they are happy with and also on what level of security they wish to have. The following are recommendations only for dedicated EUMETCast reception machines, not connected to the internet.

The following scheduled tasks should be disabled (Control Panel-->System and Security --> Scheduled Tasks):

1 Microsoft\Windows\Active Directory Rights Management Services Client\AD RMS Rights Policy Template Management (Automated)
2 Microsoft\Windows\AppID\PolicyConverter
3 Microsoft\Windows\AppID\VerifiedPublisherCertStoreCheck
4 Microsoft\Windows\Application Experience\AitAgent
5 Microsoft\Windows\Application Experience\ProgramDataUpdater
6 Microsoft\Windows\CertificateServicesClient\UserTask-Roam
7 Microsoft\Windows\Customer Experience Improvement Program\Consolidator
8 Microsoft\Windows\Customer Experience Improvement Program\KernelCeipTask
9 Microsoft\Windows\Customer Experience Improvement Program\UsbCeip
10 Microsoft\Windows\Defrag\ScheduledDefrag
11 Microsoft\Windows\Diagnosis\Scheduled
12 Microsoft\Windows\DiskDiagnostic\Microsoft-Windows-DiskDiagnosticDataCollector
13 Microsoft\Windows\DiskDiagnostic\Microsoft-Windows-DiskDiagnosticResolver
14 Microsoft\Windows\Maintenance\WinSAT
15 Microsoft\Windows\Media Center\PeriodicScanRetry
16 Microsoft\Windows\Media Center\RecordingRestart
17 Microsoft\Windows\Offline Files\Background Synchronization
18 Microsoft\Windows\Offline Files\Logon Synchronization
19 Microsoft\Windows\PerfTrack\BackgroundConfigSurveyor
20 Microsoft\Windows\Power Efficiency Diagnostics\AnalyzeSystem
21 Microsoft\Windows\RAC\RacTask
22 Microsoft\Windows\Registry\RegIdleBackup
23 Microsoft\Windows\Shell\WindowsParentalControls
24 Microsoft\Windows\Shell\WindowsParentalControlsMigration
25 Microsoft\Windows\SideShow\AutoWake
26 Microsoft\Windows\SideShow\SessionAgent
27 Microsoft\Windows\SideShow\SystemDataProviders
28 Microsoft\Windows\SoftwareProtectionPlatform\SvcRestartTask
29 Microsoft\Windows\SystemRestore\SR
30 Microsoft\Windows\Time Synchronization\SynchronizeTime
31 Microsoft\Windows\User Profile Service\HiveUploadTask
32 Microsoft\Windows\WindowsBackup\ConfigNotification
33 Microsoft\Windows\WindowsColorSystem\Calibration Loader

The following services may be disabled (Start Menu, type "services.msc" into the search line, then hit enter):

1 Windows Update (NOTE: this should still be run manually from time to time)
2 Windows Defender
3 Windows search indexing
4 Themes
5 SSDP Discovery
6 Desktop Windows session manager
7 Offline files
8 Print spooler (Unless you wish to print from the PC)
9 Program compatible assistant

Other performance gains:

1 Uncheck the indexing check box on the drive(s) data are written to (Right-click drive --> Properties)
2 Write Cache Policy - Enabled on Data Drive(s) - Unsafe in system without a UPS

B28) Reception stops when connecting to internet on Vista/Windows 7 with some DSL modems


Tellicast reception stops when connecting via a DSL modem to the internet. This was observed with modems from Alice and Arcor ISPs, when PPPoE was used as connection method.


The problem was occurs only with Vista and Windows 7.


A software fix is not known. Replacement of the modem and avoiding PPPoE can solve the problem.

B29) Skystar DVB cards - the tool b2status does not run


The b2status.exe command line tool is part of the Skystar software and SDK on the EUMETSAT CD. When started, the error message "side by side configuration error" is displayed and b2status stops.


The MS Visual C++ 2005 Redistributable Package is missing.


Install the package from the Technotrend driver subdirectory "3rdParty\MFC8.0Runtime\vcredist_x86.exe".

B30) No Ku-band EUMETCast data - Good signal but Yellow "T" with correct transponder settings


No data received, the "T" is yellow. Signal strength is good.
On Skystar cards the Network displayed on setup4pc 'Sky'.


Although you have changed all your settings correctly, you have not yet moved your antenna to the new position 9° E for Eurobird 9a


Repoint the antenna. See to find the new pointing angle appropriate for your geographical location.
Maximise the signal level, quality and SNR by fine adjustment of the pointing
azimuth and elevation, and by adjusting the skew angle of the LNB


If the dish design supports several LNBs, a second LNB can be installed to receive both satellites with one antenna. The second LNB must be mounted several cm (typically 6cm) to the East of the Hotbird LNB

B31) Increased losses on Windows XP


Files missing and following messages in recv.log:
WRN:2012-03-27 09:35:35.539:Failed to open data channel `EPS-2', address Coordinator lost
MSG:2012-03-27 09:35:35.539:Disconnect from data channel `EPS-2', address completed (channel lost)
VRB:2012-03-27 09:35:35.539:Reconnecting to data channel `EPS-2', address (channel lost)
MSG:2012-03-27 09:35:36.586:Reconnected to data channel `EPS-2', address (channel was lost)


Windows XP supports inly a limited number of simultaneous multicast channels. This problem happens only if many services are received on the same PC.


Limit the number of multicast channels to 32, see (D6).
Upgrade to Windows 7 or the related server version.
See also Annex A at the bottom of this document.

B32) Increased losses with Technisat Skystar PCI cards and certain motherboards


Files missing and many of following message types in recv.log:MSG:2012-07-09 06:24:25.229:Channel "TSL Announcement Channel": Lost message 16494333 (message lost)MSG:2012-07-09 06:24:25.229:Channel "TSL Announcement Channel": Lost message 16494336 (message lost)MSG:2012-07-09 06:24:25.229:Channel "TSL Announcement Channel": Lost message 16494337 (message lost)MSG:2012-07-09 06:24:25.229:Channel "TSL Announcement Channel": Lost message 16494338 (message lost)MSG:2012-07-09 06:24:25.666:Channel "TSL Announcement Channel": Lost message 16494342 (message lost)


The Skystar 2 and/or Skystar S2 PCI cards have compatibility problems with certain motherboards.The following chipsets and stations are known to have this issue: Intel 6/C200 Series chipset, Dell Optiplex 990, Dell Precision T1600


There is no technical solution known for these combinations, use a different DVB card or external box.

B33) Some data channels cannot be received although the configuration seems to be correct


Files from certain channels missing and many of following message types in recv.log:
WRN:2015-05-11 14:31:06.174:Failed to open data channel `EPS-Africa', address Coordinator lost

This can happen with internat DVB cards or external DVB routers or USB devices.



The Windows operating system does not correctly subscribe to the data channel on the EUMETCast network interface. The reason is unknown.


The following solution will resolve the problem in most cases.

Set the interface address to "" in the Tellicast configuration file recv.ini and restart Tellicast.


C) Linux problems

C1) EKU problems on Linux: "Found missing or wrong user key part"

If light on EKU is off (not red) go to (C3)


* host_key_4: (empty) instead of host_key_4: *****-*******-***** at the html client.

* continuous messages like :

ERR:2005-01-26 11:31:50.886:Cannot join channel "EUMETSAT Data Channel 2": Missing key 20864.
ERR:2005-01-26 11:31:50.886:Cannot join channel "EUMETSAT Data Channel 2": Failed to decode key 20864.
ERR:2005-01-26 11:31:51.145:Found missing or wrong user key part for decrypting announce data key. Etokend and pcscd running fine, eku lighted in red and everything seems perfect.

C1.1) Missing " Aladdin eToken virtual reader" information in /etc/reader.conf

Note: This problem is fixed with EUMETSAT CD "Licence_cd_v4_1_19-08-2005" (and later versions). A patch kit from the previous version can be requested from the user service and will soon be available for download on the EUMETSAT website.

  • When installing the etoken package, you will execute "petoken install ...". The petoken script also updates the /etc/reader.conf file, but this may fail.. The cause of the problem is that the perl "rename" (in-built) function does not work across file systems. If "/tmp" is not on the same partition as the / file system the perl installation script (petoken) trying to move files from /tmp to /etc will fail.
Please use this updated EKU installation procedure:
  1. Install pcsc-lite
    rpm -i pcsc-lite-1.1.1-1-redhat.i386.rpm
  2. Install etoken
    mkdir /usr/local/etoken
    tar -zxf aksrte-3-15.84.Linux.i386.tgz -C /usr/local/etoken
    cd /usr/local/etoken/aksrte-3-15.84/
    ./petoken install 2
    /etc/init.d/etokend stop
  3. Check /etc/reader.conf
    Check if this file contains a block starting with "# Aladdin eToken virtual reader" If not, the petoken script didn't update /etc/reader.conf.
  4. In this case the updated reader.conf file was created in /tmp, the name consisting of just numbers.
    It starts with:
    # Configuration file for IFD Handler 2.0 drivers
    it should contain a block starting with:
    # Aladdin eToken virtual reader #0
    Copy this file over /etc/reader.conf (overwrite the file)
  5. Overwrite the service files with files from CD, located in /EKU_software
    cp etokend /etc/init.d/etokend
    cp pcscd /etc/init.d/pcscd

C1.2) Missing shared library information

Missing shared library information


  • look at /etc/ (vi /etc/
  • check for entries /usr/local/lib and /usr/lib

if they don't appear add them at the end, save file and then type:
  • "ldconfig"

(This allows the system to look for the libraries in these folders.)
If they appear:
  • please do "ldconfig" anyway to check.

Reboot the system to finish.


C1.3) If 1) and 2) are successful, check communication with Tellicast software

  • open the Tellicast shell (open browser and select "http://localhost:2517")
  • select License
under "Client Identification" you should see the selected username and 4 host_key.. parameters, check if you see the following:
  • host_key_4: ****-****-****-****
if not, the Tellicast software cannot see the key
  • send us a screenshot of this page
  • send us following files
    list of processes (ps aux > ps.log)

C2) EKU problems on Linux: pcscd service fails to start

Note: This problem is fixed with EUMETSAT CD "Licence_cd_v4_1_19-08-2005" (and later versions). A patch kit from the previous version can be requested from the user service and is available for download on the EUMETSAT website.
When the pcscd service is started, pcscd creates a /tmp/pcsc directory entry. If pcscd was incorrecty stopped, e.g. after a crash or power cycle while running, the entry remains in /tmp. Any attempt to start pcscd again will then fail because it thinks it is already running.


Remove /tmp/pcsc and start the service again.

C3) LINUX: EKU light off

C3.1) USB system is not configured

C3.1.1) 2.4 kernels

- check if /proc/bus/usb is present
- if not, add follwing entry in /etc/mtab

usbdevfs /proc/bus/usb usbdevfs rw 0 0

- check if usb-uhci module is loaded (lsmod)
- if not "modprobe usb-uhci" and add to /etc/modules.con (2.4 kernels)
- alias usb-controller1 usb-uhci

- then "cat /proc/bus/usb/devices" should contain following line
P: Vendor=0529 ProdID=0514 Rev= 1.00

C3.1.2) 2.6 Kernels

If you get messages in the /var/log/syslog or /var/log/messages (depending on build) such as:

Jun 4 11:53:04 eumct06 etokend: unable to open /proc/bus/usb/devices file

Non Ubuntu:

Add the following entry to the /etc/fstab file:

# vi /etc/fstab

usbfs /proc/bus/usb usbfs defaults 0 0

Then mount the filesystem:

# mount -a

(or "mount -t usbfs usbfs /proc/bus/usb" from the command line)

Fedora Core 16:
Editing the /etc/fstab not appear to work after a reboot so the command line needs to be run each time the PC is re-booted so it is a good idea to add the lines above, so that they are executed before the etokend is started e.g. add the mount line to the start

subroutine of the /etc/init.d/etokend script (and an umount to the stop subroutine).

Ubuntu 8.04 (later versions see below):

Edit the script e.g.:

# vi /etc/init.d/

Find the following section, and uncomment the last 4 lines:

# Magic to make /proc/bus/usb work
#mkdir -p /dev/bus/usb/.usbfs
#domount usbfs "" /dev/bus/usb/.usbfs -obusmode=0700,devmode=0600,listmode=0644
#ln -s .usbfs/devices /dev/bus/usb/devices

#mount --rbind /dev/bus/usb /proc/bus/usb

The run the script as root (or reboot the machine):

# /etc/init.d/ start

Ubuntu 10.04 (domount no longer available):
# mount --bind /dev/bus /proc/bus

# ln -s /sys/kernel/debug/usb/devices /proc/bus/usb/devices

Then restart the etoken daemon, pcscd daemon and tellicast software.

Note: this needs to be redone each time the PC is re-booted so it is a good idea to add the lines above so that they are executed before the etokend is started, e.g. add the lines to the start subroutine of the /etc/init.d/etokend script.

(C3.2) If (C3.1) is ok and the light is still off, the EKU is damaged and must be replaced

C4) EKU problems after successful installation: "Failed to decode key"

If the light on EKU is off (not red) go to (C3)


* host_key_4: *****-*******-***** at
the html client (at least after restart).

* continous messages like :

ERR:2005-01-26 11:31:50.886:Cannot join channel "EUMETSAT Data Channel 2":
Failed to decode key 20864.
ERR:2005-04-06 15:03:51.505:Critical dongle error (eToken transaction timed out). Restarting child.

Etokend and pcscd running fine, eku lighted in red and everything seems perfect.


The communication to the EKU is harmed. It the EKU doesn't respond within 10s, the "Critical dongle error" is triggered. This can be caused by a badly functioning EKU, or by incorrectly running EKU drivers.

Please perform one of the two options for the following check:

Option 1: Command line option
Run pcscd in debug mode:
# /etc/init.d/tellicast-client stop
# /etc/init.d/pcscd stop

Run pcscd in the forground and inspect messages:
# pcscd -f -d stdout
[or run it with strace ]
#strace pcscd -f -d stdout
start tellicast
#/etc/init.d/tellicast-client start

Option 2: Boot option

- add the line SYSLOGD_OPTIONS="-d syslog" to /etc/init.d/pcscd

extract of /etc/init.d/pcscd
export LD_ASSUME_KERNEL=2.4.1

- restart the reception station
this will add debugging information in /var/log/messages

- log the data until the EKU problem reappears, then send us the following files

- after the test, disable the line in /etc/init.d/pcscd by preceeding it with a "#"
#SYSLOGD_OPTIONS="-d syslog"


- Check to see if there are error messages in the console output (option 1) or in /var/log/messages (option 2) about libraries not found, if so and if host_key_4 is is empty "_" instead of "****_****_****_****" goto C11
- The log will contain message pairs like "... SCardBeginTransaction ..." / " ... SCardEndTransaction ..."
An increased time delay of several seconds between "SCardBeginTransaction" and "SCardEndTransaction" indicates a communication problem. In this case the EKU might have to be be replaced.
- If this problem only occurs occasionally, a monitoring tool can be installed that automatically restarts the involved services. The tool is available from our User Service Helpdesk as a tar archive (monitor-eku.tar).
The tool will be integrated into a future release of the EUMETCast package.

C5) Using DVB cards under 2.6 kernels

Support for Linux 2.6 kernels is provided in versions 5.2 of the EUMETCast package and higher. Note: Only Kernels 2.6.32 and above support DVB-S2 (DVB API V5)

C6) Configuring Linux stations for C-band (2.4 kernel)

- The EUMETSAT CD currently contains only settings for reception of 2.4 kernel Linux stations in Ku-band.

- Use following lines in the startup scripts for C-band reception:

Note: for 2.6 kernels: if you use the standard install instructions for 2.6 kernels from the EUMETSAT CD, you can select the satellite/transponder by editing the /etc/dvb-eumetcast.cfg — see readme files in 2.6 directory

- if using szap:
- set up file "channels.conf"


- run command line:
# uncomment next line for DVB KU band Europe
#/usr/bin/szap -c /etc/channels.conf -n 1 > /dev/null &
# uncomment next line for DVB C band Africa
/usr/bin/szap -l C-BAND -c /etc/channels.conf -n 2 > /dev/null &
# uncomment next line for DVB C band South America
#/usr/bin/szap -l C-BAND -c /etc/channels.conf -n 3 > /dev/null &

- if using dvbtune:
- use the latest version of dvbtune (later than 2003) on 2.6 kernels, install RPM or compile source from
- dvbtune is supporting only KU-band, for C-band you have to use modified frequencies (to take into account the LOF of the LNB)
- set up following lines in the start up script

# use next line to select PID 100 on C-band Africa, select other PIDs using repeated lines
dvbtune -c 0 -f 11168243 -p H -s 11963 -n 100 >/dev/null 2>&1
# use next line to select PID 1921 on C-band South America, select other PIDs using repeated lines
#dvbtune -c 0 -f 11097000 -p H -s 27500 -n 1921 >/dev/null 2>&1

- if using pentamedia cards:
- set following line in pentaval.conf
Symbol rate=28.93000

C7) DVB Card hangup under Linux


After an interruption of the DVB downlink ( e.g. weather related) the Pent@Value DBV card might stop receiving data.


This is probably a driver problem, since it does not occur in the Windows version.


A restart of the pentaval driver will fix the problem.
The tellicast cient v2.4.3 and higher will support automatic detection of an interruption.
Do the following steps to configure this function:

1. create a restart script /etc/ with the following content:

/etc/init.d/pentaval restart

2. make the file executable

chmod +x /etc/

3. modify the [watchdog] section in the Tellicast configuration file recv.ini

Note: this procedure may be adapted to the users needs for other DVB cards.

C8) Firewall configuration tables (iptables)


No reception by Tellicast while all DVB reception parameters seem ok


The Linux firewalls (which are often installed by default - especially in newer builds) do not allow the flow of DVB data.


The exact implementation depends on the specific firewall used. The examples below show how to use the command line to add rules using iptables. Again, most Linux builds have a GUI interface to configure the firewall and to allow default start up settings to be loaded. This varies from build to build but an experienced Linux user should be able to use the examples below to configure their own firewall.
Note: The user needs to change the DVB interface device name (i.e. pentaval0, dvb0, eth1) as appropriate.

iptables -I INPUT -i pentaval0 -p udp -s -j ACCEPT

iptables -I FORWARD -i pentaval0 -o dummy0 -p udp -s -j ACCEPT
iptables -I INPUT -i dummy0 -p udp -s -j ACCEPT

iptables -I FORWARD -i dvb0+ -o dummy0 -p udp -s -j ACCEPT
iptables -I INPUT -i dummy0 -p udp -s -j ACCEPT

iptables -I INPUT -i eth1 -p udp -s -j ACCEPT

iptables -I FORWARD -i eth1 -o dummy0 -p udp -s -j ACCEPT
iptables -I INPUT -i dummy0 -p udp -s -j ACCEPT

iptables -I OUTPUT -o eth1 -p tcp -m tcp --dport 80 -m state --state NEW,ESTABLISHED -j ACCEPT
iptables -I INPUT -i eth1 -p tcp -m tcp --sport 80 -m state --state ESTABLISHED -j ACCEPT

e.g. under FC8 (2.6 kernel) create a file with the following lines and then using the GUI add it to the "custom rules"
part of the firewall (ip4 -> filter):
-I FORWARD -i dvb0+ -o dummy0 -p udp -s -j ACCEPT
-I INPUT -i dummy0 -p udp -s -j ACCEPT

C9) EKU / USB Problems with new Linux distributions


Seen on:
- Fedora Core 9 and above
- Ubuntu 8.10

Etoken not working

* continuous messages like:

ERR:2005-01-26 11:31:50.886:Cannot join channel "EUMETSAT Data Channel 2": Missing key 20864.
ERR:2005-01-26 11:31:50.886:Cannot join channel "EUMETSAT Data Channel 2": Failed to decode key 20864.
ERR:2005-01-26 11:31:51.145:Found missing or wrong user key part for decrypting announce data key.


Newer Linux versions have changed the devicenames/udev rules for usb devices.


- edit /etc/udev/rules.d/20-etoken.rules and add the following 2 lines:
ACTION=="add", SUBSYSTEM=="usb", SYSFS{idVendor}=="0529", SYSFS{idProduct}=="0514", RUN="/etc/hotplug/usb/etoken"
ACTION=="remove", SUBSYSTEM=="usb", SYSFS{idVendor}=="0529", SYSFS{idProduct}=="0514", RUN="/etc/hotplug/usb/etoken"

C10) Problems with the dummy0 interface


Seen on:
- Ubuntu 9.10
- CentOS 6.2/RHEL6

No reception by Tellicast while all DVB reception parameters seem OK.

Also if run manually, e.g:

$ sudo /etc/init.d/dvb-eumetcast start
[sudo] password:
Starting dvb-eumetcast: Failed to configure the multicast interface 'dummy0'


The dummy module is not included by default in the /etc/modules for Ubuntu 9.10 version.


In a terminal window, type:

[for Ubuntu]

$ sudo su -
# echo dummy >> /etc/modules

[For CentOS]

# echo 'modprobe dummy' >> /etc/rc.modules # chmod +x /etc/rc.modules

then reboot the station.

C11) Missing symbolic link for etoken libraries

Note: If the light on EKU is off (no red light) go to (C3)


Seen on:
Ubuntu Server 8.04.1
Ubuntu 9.04
Debian 5.0 (Lenny), Kernel 2.6.26
Fedora Core 16 (Kernel 3.4.9)

EKU is lit (red light)
host key 4 is empty - Tellicast client license page shows host_key_4: " " instead of "****_****_****_****"
Continous messages like:
ERR:2010-01-26 11:31:50.886:Cannot join channel "EUMETSAT Data Channel 2": Failed to decode key 20864.
There is no softlink in /usr/local/lib/ to /usr/local/lib/


In order for the etoken software to work on some builds it is necessary to manually create the following symbolic link.

As the root user in a terminal window, type:

# ln -sf /usr/local/lib/ /usr/local/lib/

(there should also be a copy in /usr/local/etoken/aksrte-3-15.84p3/

Then run ldconfig to be on the safe side

# ldconfig

then reboot the station.

C12) Reverse Path Filter (rp_filter)


Seen on:
Kubuntu 10.04 LTS

Tellicast cannot connect to any channels
Multicast packets coming into the DVB0_x (RX Bytes) interfaces but not being passed to the dummy0 (TX Bytes) interface.


The /etc/init.d/dvb-eumetcast script disables the anti-spoofing for each dvb-device plus dummy0. But in some builds it is also necessary to disable it in the "all" interface (/proc/sys/net/ipv4/conf/all).

Before starting dvb-eumetcast, type:

# echo 0 > /proc/sys/net/ipv4/conf/all/rp_filter

This needs to be done every restart so ideally should be added the /etc/init.d/dvb-eumetcast script, e.g. in the configure_multicast_interface() sub-routine:

# check if kernel anti-spoofing for the multicast interface is configured...
if [ -e /proc/sys/net/ipv4/conf/all/rp_filter ]; then
# kernel anti-spoofing for the multicast interface is configured, check if it is enabled...
if [ "`cat /proc/sys/net/ipv4/conf/all/rp_filter`" = "1" ]; then
# kernel anti-spoofing for the multicast interface is enabled, disable it...
echo 0 > /proc/sys/net/ipv4/conf/all/rp_filter

C13) CentOS default kernels — dvb support not included


Seen on:
CentOS 4 and 5

/dev/dvb does not exist.

# lsmod | grep dvb

returns no results.

dvb-eumetcast fails to start:
# /etc/init.d/dvb-eumetcast start
Starting dvb-eumetcast: Failed to add the DVB interface 'dvb0_0 for the service PID '100'


The CentOS kernel does not include support for DVB by default. You need to install the CentOSPlus kernel.

Please follow the instructions here to install the CentOSPlus kernel:

C14) Skystar 2 - firmware version 2.8A and 2.8B (older firmware is ok)


Error messages when starting /etc/init.d/dvb-eumetcast such as:
Starting dvb-eumetcast:
Failed to add the DVB interface 'dvb0_0 for the service PID '100'

And when running szap manually:

# szap -c /etc/channels.conf -n 1
reading channels from file '/etc/channels.conf'
zapping to 1 'eurobird9':
sat 0, frequency = 11976 MHz H, symbolrate 27500000, vpid = 0x0000, apid = 0x0000 using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0'
opening frontend failed: No such device


These specifc firmware versions (2.8A and 2.8B) were not supported in some older builds (kernels/dvb-utils versions).
They are supported in the latest builds. Please update to the latest kernel and dvb-utils (or dvb-apps) package.

If this is not possible, please see the instructions here:

C15) RAMDisk not being created or only 16 MB in size.


Seen on later Fedora Core builds, fix tested on FC16 (3.4.9 Kernel)

When the "RAM_DISK_DEVICE=/dev/ram0" option is enabled in the /etc/tellicast-client.cfg file, stopping and restarting

the tellicast-client service does not create a RAMDisk or it creates one that is 16 MB in size.


The RAMDisk module is no longer called "rd" and its size no longer seems to be controlled via the kernel command line

option "ramdisk_size=500000".

Increase the RAMDisk size (the example here is to 500MB):

# mv /etc/modprobe.d/dvb-eumetcast /etc/modprobe.d/dvb-eumetcast.conf
# vi /etc/modprobe.d/dvb-eumetcast.conf
[add the line]

options brd rd_nr=1 rd_size=500000 max_part=0

# modprobe -r brd

# modprobe brd

Update the tellicast-client script to use "brd" instead of "rd":

# vi /etc/init.d/tellicast-client

[change "rd" to "brd" in the following lines]

# check the RAM disk device...
if [ "$RAM_DISK_DEVICE" != "" ]; then
# the RAM disk device has been specified, check if it exists...
if [ ! -e $RAM_DISK_DEVICE ]; then
# the RAM disk device does not exist, check if the brd kernel module is loaded...
if [ "`lsmod | grep '^brd '`" = "" ]; then
# the brd kernel module is not loaded, load it...
modprobe brd > /dev/null 2>&1

# systemctl --system daemon-reload

Then restart the tellicast-client service or reboot the machine.


On some modern distributions brd is broken and does not accept parameters. Then use the tmpfs ramdisk.
Check if /dev/shm exists, execute df, then a line like the following should be returned

tmpfs                  1811664         0   1811664   0% /dev/shm

stop tellicast-client

disable the following line (insert "#" as first character) in /etc/tellicast-client.cfg

update the following line in /etc/recv.ini to

start tellicast-client

C16) DMA Buffer full


Seen on:
Fedora Core 6 - kernel with the dvb cards running the SAA7146 PCI interface chipset from Philips (TechnoTrend, Hauppauge).

Occasional losses by Tellicast but signal strength/quality are fine.

Messages in /var/log/messages such as:
Jan 9 09:03:01 eumcr04 kernel: saa7146 (0) vpeirq: used 1 times >80% of buffer


Add the following line to the /etc/modprobe.conf file:
options budget_core bufsize=1410

and reboot the machine.

C17) Installation logs on various Linux Distributions

Installation logs from test installations on lab PCs at EUMETSAT are provided here for reference:

Please note these logs are for guidance only and may need to be varied depending on your specific hardware.

D) Common problems

D1) Frequent loss of files


* in recv.log continous messages like:

MSG:2005-04-08 08:53:18.308:Channel "EUMETSAT Data Channel 2": Lost message 1400 (unknown error)
MSG:2005-04-08 08:53:19.916:Missed parts of file `H-000-MSG1__-MSG1________-WV_073___-000004___-200504080845-C_' id 42564639004f9d42 from channel `EUMETSAT Data Channel 2'
MSG:2005-04-08 09:10:36.703:Disconnect from announcement channel `TSL Announcement Channel', address completed (channel lost)
VRB:2005-04-08 09:10:36.703:Reconnecting to announcement channel `TSL Announcement Channel', address (channel lost)
MSG:2005-04-08 09:10:49.418:Missed parts of file `L-000-MSG1__-GOES9_______-10_7_140E-000004___-200504080900-C_' id 42564a23004fa21a from channel `EUMETSAT Data Channel 3'
MSG:2005-04-08 09:10:49.418:Missed file `L-000-MSG1__-GOES9_______-10_7_140E-000005___-200504080900-C_' id 42564a23004fa21b from channel `EUMETSAT Data Channel 3'


The problem might be caused be one of the following:
1. DVB reception problems, low margin for rain, noisy equipment, DVB signal interruptions
This problem is indicated by lost packets or high BER in the DVB card monitoring software
2. High load on the reception machine, especially disk I/O activities
3. Programs using high CPU load or disk I/O are running


1. Check reception system, replace faulty or low quality hardware (LNB, cables, DVB cards), increase antenna size
2. Install a RAM disk (> 60 MB) and set following parameters in the recv.ini file (leave other parameters unchanged)

file_database_directory=<directory name on RAM disk>
# enables buffered write mode to log file

# verbose mode is intended for debugging

# this restricts the file database to 60 MB, the default value is 250 MB.
# make the RAM disk larger than 60 MByte

All these changes reduce disk I/O activities and thus improve the performance even under heavy CPU load.
3. Switch off programs that cause interference like
- anti virus /anti spam software
- automatic windows update
- programs with heavy disk activities

D2) Need more information about Tellicast client and file formats.

While the tellicast client is running, open a web browser.
Enter URL http://localhost:2517/
Select "Help" in the menu displayed on the left side.

D3) No DVB reception or no signal


The DVB reception software indicates one or more of the following:
- no signal or signal on noise level
- no carrier lock
- no data lock


The problem might be caused be one or more of the following:
1. Antenna pointing incorrect
2. Wrong polarisation by incorrect mounting of the LNB (linear polarisation only)
3. Broken hardware, LNB or DVB card/box
4. High frequency offset of LNB
5. Cable and connector problems


1. Check antenna/LNB by using another DVB or digitab satellite TV receiver or testing equipment.
2. Visually check cables and connectors, check for shorts and throughput.
3. If the DVB software allows, scan the whole frequency range for transponders.
Check the results to see if the right satellite, polarisation and frequencies of the transponders are recognised.
Send results back to helpdesk.
4. Use an offset frequency (several MHz higher or lower) to correct for LNB oscillator offsets.
5. Replace faulty hardware.

D4) Missing channels


* in recv.log continous messages like:

MSG:2005-11-10 07:59:48.652:File transmission 4372fda0005e9d03 interrupted: filelist missing/incomplete
MSG:2005-11-10 07:59:50.808:File transmission 4372fdeb005e9d59 ended: filelist missing/incomplete
MSG:2005-11-10 07:59:50.949:File transmission 4372fdeb005e9d55 ended: filelist missing/incomplete
MSG:2005-11-10 07:59:50.964:Disconnect from data channel `EUMETSAT Data Channel 2', address completed (channel closed)
MSG:2005-11-10 08:00:01.511:File transmission 4372fda0005e9d03 ended: filelist missing/incomplete
MSG:2005-11-10 08:00:03.542:File transmission 4372fdd3005e9d3d interrupted: filelist missing/incomplete
MSG:2005-11-10 08:00:15.152:File transmission 4372fdc1005e9d2d ended: filelist missing/incomplete
MSG:2005-11-10 08:00:15.167:Disconnect from data channel `EUMETSAT Data Channel 3', address completed (channel closed)


The problem might be caused be one of the following:
1. Channel is not selected in recv-channels.ini.
If this is the case the "Disconnect from data channel..." message is not displayed.
2. PID not selected for related channel in DVB reception configuration.
3. A firewall setting or routing problem might prevent the routing of the multicast channel.
4. If all channels are missing, the card might be broken.


1. Edit recv-channels.ini, add a section for the missing channel, or add a wildcard, e.g.
[EUMETSAT Data Channel 3] or
[EUMETSAT Data Channel*] or
2. add PID for missing channel
3. enable routing or update firewall configuration.
4. Replace DVB card

D5) Interference in C-band and locking problems using bandpass filters


Intermittent reception problems in C-band


Radar interference can cause reception problems in C-Band.


Place a C-band bandpass filter between the feed and the LNB.
The following link shows a filter which is successfully being used for EUMETCast:

The type is
3.7 - 4.2 BPF
D/C 0301

Note: Occasionally, when powering up the DVB reception computer and a bandpass filter is installed, the LNB simply refuses to work.

If this is the case, please do the following:
1) Power up the DVB computer. Wait for the applications to start (reception does not work).
2) Disconnect the antenna cable from the receiving board, leave the cable disconnected for a couple of minutes
3) Reconnect the antenna cable to the board. Reception resumes almost immediately.

It is recommended to leave the system powered permanently to avoid this situation. Use an uninterruptible power supply in case of an unreliable power net.

D6) I want to remove channels from reception


The data is temporarily not needed or there are performance problems receiving too many channels.


Edit the file recv-channels.ini and specify each channel that should be received, remove the wildcard [*], e.g. add entries like this:
[EUMETSAT Data Channel 1]

[EUMETSAT Data Channel 2]

[EUMETSAT Data Channel 3]

# The commented channels will not be received
#[EUMETSAT Data Channel 5]
#[EUMETSAT Data Channel 6]


D7) "Address already in use" messages in Tellicast logs


* in recv.log
messages like:

ERR:2006-05-22 19:15:16.734:Cannot start HTTP server at port 2517 on all interfaces: (Address already in use)
ERR:2006-05-22 19:15:16.734:An error occurred while starting tc-recv.exe. Shutting down!


Tellicast is already running and a second attempt to start the client is made.
This could be caused by a second installation of Tellicast or by the user attempting to manually start the program.


1. Identify all installations of Tellicast. Remove (uninstall) the obsolete installations.
2. If necessary, uninstall all Tellicast installations and manually remove remaining files.
3. Reinstall Tellicast.

D8) Intermittend Config Error or red "T" Icon in versions 2.4.3/2.4.4


* in recv.log
messages like:

ERR:2006-05-30 13:49:41.250:Failed to open data channel `EUMETSAT Data Channel 1', address (wrong interface address
MSG:2006-05-30 13:49:41.250:Disconnect from data channel `EUMETSAT Data Channel 1', address completed (channel closed)
MSG:2006-05-30 13:49:45.000:Disconnect from data channel `EUMETSAT Data Channel 1', address completed (channel closed)


1. The PID for the related channel is not selected, or the channel is not available on the downlink.
2. A known bug in the uplink server software causes occasional occurrence of this error on the client side without any impact.
This problem will be fixed soon on the uplink side.

SOLUTION for problem 1

The error message is a standard feature of these client versions.
The messages can be avoided by using the recv-channels.ini file for positive channel selection.

1. Edit recv-channels.ini, add sections for the wanted channel(s), and remove wildcards and unwanted channels, e.g.
[EUMETSAT Data Channel 3] or
[EUMETSAT Data Channel*]
2. add PID for missing channel

D9) Location of file database, tmp files, received files, log files and other settings

To achieve the maximum performance of the client the following locations of the file outputs are recommended:

1. File database
The file database (0.fsy, 1.fsy, etc) is the temporary store for the received file fragments until a file is completely received.
Writing the fragments into the file database is a time critical operation and should not be interrupted.
We recommend to
- create a RAM disk with sufficient size for the subscribed services (e.g. 60 MB MSG1 only, 500 MB all including EPS)
- specify the RAM disk location (e.g. if G:\ is the RAM disk under Windows) [locations]

- specify the maximum size in recv.ini (should be less than the physical size) [parameters]

Should you not be able to use a RAM disk, please use the fastest disk on the system. If two disks are used, the location should be different from the target location of the files.

2. Temporary and target location for received files
Once a file is completely received in the file database, it will be written to disk. This takes time and the files should be written to a temporary name or location first. Once completely written the file will then be moved (renamed) to the final target location. IN order for the rename to work the temporary location must be on the same file system (disk, partition) as the target location.
- specify a temporary and target location in the recv-channels.ini file for every channel (or multiple using wildcards)

[EUMETSAT Data Channel 1]

3. Log files
Tellicast writes logging information into files called recv.log. This is useful for investigations and monitoring, however, it creates additional disk traffic. If logging is not required, you can turn it off by specifying "none".
If required you should at least use the buffered write mode using ">>" in front of the file name. The location can be anywhere on the system, but the file database location should be avoided.
- specify name, logging level and buffered mode for logging in recv.ini



4. Write to disk performance
The speed used for writing data from the file database to the final files can be adjusted by two parameters, the speed (in bit/s) and the rate in number of files per second.
The following values should be used as default for EUMETCast if all services are selected.

#file_delivery_counter=50 (is default)
file_delivery_speed=20000000 ( defaul 10 mbit/s)

D10) Problems after the upgrade on the EUMETCast uplink system on 30 May 2006


Reception before the switch was perfect or only few losses were observed.
After the switch on 30 May at 08:55 UTC the reception was severly degraded.
One or more of the following reasons might be responsible:

1. Old DVB card driver
Some Skystar2 cards running under driver version 4.2.2 (Windows) do not perform very well with the new system.
Please upgrade the DVB card driver and the reception software to V 4.3.0 (or higher).
V4.3.0 is included on the EUMETSAT CD and in the upgrade sent out recently over EUMETCast.
Follow the instructions to make sure that the low level drivers are also updated.

2. Old Tellicast Client software
Tellicast client version 2.3.1 will almost certainly create many losses.
Client version 2.4.0a might look perfect, but a username dependent error case might degrade the performance at any time in future.
We strongly recommend to upgrade to version 2.4.4b (Windows) or 2.4.3a (Linux).

3. More effective bandwidth control on the uplink side creates a slightly higher load on the reception stations. Please apply the recommendations listed in (D9) to optimise the configuration.

D11) Error message "Could not set the modification time"


* in recv.log
messages like:

ERR:2006-06-12 21:04:19.031:Could not set the modification time for file received\H-000-MSG1__-MSG1________-VIS008___-000002___-200606122100-C_ (Permission denied).


The Tellicast client version later than 2.4.3 sets the modification time of a received file to the original timestamp seen before uplink. The error message occurs if the file is accessed by other software before the operation is completed.


Use a temporary location (solution D9 2.) but make sure that the temporary location is in the same file system as the target location, e.g. by selecting a ./temp sub-directory under the target directrory.


D12) Setting the RAM disk size for the file database

This section gives some help to determine the best RAM disk size for the Tellicast file database.

1. Eliminate DVB reception losses
In order to continue with the next steps an error-free reception is needed for the test periods.
Use the statistics tools of the DVB card software to verify that the number of lost blocks is 0 or minimal.
Make the tests when the weather is fine.

2. Configure the largest size RAM disk you can make available on the system, e.g. 30%–50% of the physical ram.
Leave sufficient ram for the operating system and application, 256 MB is normally enough.

3. Stop all programs not necessary for DVB reception.

4. Configure all services you want to receive.

5. Install a task that regulary cleans up the disk, e.g. a batch job deleting the received files.

6. Run a reception test for at least 2 days. Repeat the test if reception losses were too high due to weather.

7. Analyse the Tellicast reception losses, search for "Missed files" or "Missed parts of file" messages in recv.log.
In case of frequent losses follow the related suggestions in this guide to correct the problem.
If no or only few losses occurred, note the size of the file database (.fsy files) in the RAM disk.

8. Add 30% to this value from step 7. Configure the RAM disk size to this new value (size= X bytes).
Set the file_database_size to a 1MB lower value (size= X - 1000 bytes).

D13) File database grows larger and larger

This fix applies only if a RAM disk is not used! See also (D1)


Frequent loss of files (see D1) and file 0.fsy quickly grows to large values or several files 0.fsy, 1.fsy, etc. are created.


Disk I/O performance is limiting the data throughput to/from disk, thereby interrupting the reception of raw data.
This can be tested by following procedure:
- stop Tellicast client (right-click T icon - exit)
- delete file database files 0.fsy, 1.fsy, etc. (normally located in the receiving/tmp sub-directory of Tellicast)
- start Tellicast client
- If file losses are initially gone (good reception for at least 1 hour), the solution will help


Install a RAM disk and put the file database on the RAM disk, for details see D9 and D12.

D14) Frequent loss of files at high data rates with certain DVB cards


When set to receive high data rate channels (e.g. EPS channels 5,10 & 11) in the recv.log messages like:

MSG:2007-10-09 09:21:15.435:Missed parts of file `IASI_xxx_00_M02_20071009073900Z_20071009074200Z_N_O_20071009091604Z' id 470b47d40004026d from channel `EPS-11'

This has been seen under Linux (Debian 3 and 4, Fedora Desktop 7) and Windows XP.


Certain Cards seem to have problems with data rates above about 10 Mbits/sec. Cards known to have these problem currently include:
Haupauge Nexus ver.2.1
TechnoTrend Premium S-2300


Currently the only solutions are to either reduce the data rate by removing the high rate channels from the recv-channels.ini or to buy another card.

D15) Firefox browser is requesting eToken password when visiting secure web pages


When EKU software 4.5 is installed on Windows (may also happen under linux with updated EKU drivers) and a secure web page is opened, a window pops up requesting the eToken password in order to write information to the eToken (EKU).



The EKU is also used as a device which can store passwords and CA information in connection with accessing secure web pages. Version 4.5 of the EKU software supports this operation, and the modules are automatically installed in the firefox browser.


- Use EKU for this purpose (not recommended because we have not tested the interoperability with this function)
- disable the eToken module in firefox
* Start Firefox
* (Linux) Go to Edit->Preferences->Advanced->Tab "Encryption"
* (Windows) Go to Tools->Options->Advanced->Tab "Encryption"
* Click on 'Security Devices'
* In the list "Security Modules and Devices", select the eToken ... device
* Click on 'Unload'

Note: see also related entry (B21)

D16) Java issue in Tellicast WEB interface graph display


After java update the TelliCast throughput graph from the HTML shell is not working anymore.


In January 2014 Java was updated to make it more secure, by making Java programs which were not "digitally signed" not run.
This stopped the TelliCast throughput graph from the HTML shell from working.


A future Tellicast software update will solve this problem. Until then use the workaround described by Dave Taylor:

D17) How to identify the satellite or transponder on DVB-S2 Ku band


DVB-S2 parameters are correct, there is signal, but no lock and no data.


Antenna may be pointed to the incorrect satellite and the another transponder is received.

How can I identify the correct transponder is selected?

The following transponders in the vicinity of E10A are locked with a green LED by the SR1 DVB-S2 receiver or may be indicated with a high signal level by other receivers:

16°E   11262 MHz   27.5 MSymbol/s   QPSK 2/3
13°E   11258 MHz   27.5 MSymbol/s   8PSK 3/4
10°E   11262 MHz   33.0 MSymbol/s   8PSK 3/5, 16APSK 2/3 (EUMETCast)
07°E   11262 MHz   30.0 MSymbol/s   8PSK 3/4

Any these transponders can be received at the EUMETCast downlink frequency of 11262.5 MHz, depending on the antenna pointing.


If the 16 °E or 13 °E position is identified, point the antenna slightly more West.

If the 07 °E position is identified, point the antenna slightly more East.

Move the antenna in very small steps and observe the reception status until the 10 °E position is reached.

Limitations of EUMETCast

With the addition of Metop-B and NPP data and the MSG-3 commissioning the total EUMETCast bandwidth will go up to 20.5 Mbps in September 2012. However, listed below are explanations about the current limitations of EUMETCast.

1. DVB device limitations

All DVB-S devices we have tested (except the USB-1.1 boxes) are capable to support this data rate easily. In general the DVB-S cards, USB-2 devices and DVB routers support the full transponder transport stream anyway. The EUMETCast data stream (i.e. the EUMETCast PIDs) is multiplexed into the overall transport stream and the DVB driver software filters the PIDs configured for reception.

Therefore, in general, all DVB devices supporting MPE encapsulation would, in principle, support EUMETCast. But in reality it is possible that there are driver or hardware conflicts with the chosen computer system for the built-in cards or USB boxes.

Lately all manufacturers switch to DVB-S2 devices and PCI-E interfaces. First tests have shown that these devices work with EUMETCast and show very good performance.

The DVB routers are protected against hardware and software problems because they deliver an IP multicast stream on a LAN interface. However, there may be other limitations (see below).

2. Limitations on Linux

With Linux operating systems (FC9 or other distributions using kernel 2.6) a modern state-of-the-art system does not show any limitation. By feeding the multicast via a LAN interface we could go up to a full transponder data rate (~30 Mbps) and the station could receive 100% of the files over multiple days.

A mandatory tool to achieve this performance is smcroute which is integrated into the EUMETCast CD.
This tool avoids the overhead and short delays which occur when multicast channels are opened or closed.

3. Limitations on Windows XP

Windows XP is limited by the number of multicast channels it can receive in parallel.
Test have shown that not more than 32 channels can be simultaneously open (joined).
This limit is reached already with the "EUMETSAT Data Channels" and EPS channels.
In this case following messages are seen in the recv.log:

WRN:2012-03-27 09:35:35.539:Failed to open data channel `EPS-2', address Coordinator lost
MSG:2012-03-27 09:35:35.539:Disconnect from data channel `EPS-2', address completed (channel lost)
VRB:2012-03-27 09:35:35.539:Reconnecting to data channel `EPS-2', address (channel lost)
MSG:2012-03-27 09:35:36.586:Reconnected to data channel `EPS-2', address (channel was lost)

The only solution is to restrict the number of channels in recv-channels.ini such that it stays below 32. Effectively an XP solution is only capable of receiving a sub-set of the EUMETCast services.

4. Limitations on Windows 7

Windows 7 does not show a hard limit on the number of simultaneously open multicast channels like XP. In principle an unlimited number of channels is supported. But depending on the hardware used there can be performance problems in joining/leaving multicast channels. This behaviour may depend on the network driver or on the DVB card driver which acts as a network device.

The result can then be similar to the above messages, i.e. a transmission is incomplete or missing. But the number of lost files per day is much lower than on XP systems.

The underlying problem is probably the multicast routing on a network level. On linux the static multicast routing (done with the smcroute tool) avoids this problem.

Some DVB card drivers handle this problem better than the network card driver, therefore, a DVB router might show problems whereas a built-in DVB card works perfectly.

Tests with the final hardware (PC and DVB card) are essential to characterise the performance.

5. Windows server operating system

We have not done specific tests with server versions. It is expected that the server versions behave similar to the related desktop versions.


The EUMETCast system with the current client is scalable up to a full transponder bandwidth using the recommended DVB-S (or S2) devices.
Under Linux no limitations are known.
Under Windows there is a limit of 32 simultaneous multicast channels. XP can still be used for receiving a sub-set of data (e.g. MSG only).

It is strongly recommended to upgrade to Windows 7 (or the related server version).

6. Virtualised IT environment  / Storage Area Network (SAN)

The TelliCast reception is real-time software that has to be able to process incoming data, access information and outgoing data at the speed of the incoming information. This makes it much different from unicast transfer protocols (ftp, etc) where lost data will be requested and retransmitted. The salient points for the TelliCast performance are the interfaces — networking for incoming data, file system for file fragments, data and logs, and EKU for decryption. Any bottlenecks in these interfaces will have an impact in performance.

For these reasons it is not recommended to use EUMETCast reception in a virtualised IT environment or using SAN solutions.

The Secretariat will investigate together with the software provider for an improved implementation for virtualised environments with the goal to have such updates integrated into a future release of Tellicast.