To assist new users in setting up their EUMETCast station we have established a set of troubleshooting notes. A copy of these notes is included with the EUMETCast Client Software. Before installing your EUMETCast Client Software and EKU, we recommend that you read the relevant read me files contained on the CD ROM supplied by EUMETSAT.
If a manufacturer has installed your reception station, we recommend that you contact them first in the event of a failure of your equipment.
Please note that EUMETSAT can only provide Helpdesk support for those reception station components recommended by us. If you are using different components, we would be very interested in learning about your experiences. However, we may not be able to assist you with system-specific problems.
EUMETCast troubleshooting Notes
(A) General, provide following information
- (A1) set in recv.ini file:
- (A2) continue reception for a few hours. then send us following files
- recv.ini
- recv-channels.ini
- recv.log
- (A3) send us a screen shot
- of task manager ("processes" and "performance" tab)
- open the Tellicast shell (double click the T icon)
- select License
- send us a screen shot 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)
(B) Windows™ problems:
(B1) EKU or username/password problems on Windows: "missing key" or "Failed to decode key" or no reception at all
Symptoms:
- 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
Problem:
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:
user_name=eumetcastuser
user_key=9Ecast3004us
(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 MPEF files every 15 min.
This user name allows only reception of 6 hourly MSG image data.
If this is successful, goto B13 or confirm the username/password with the EUMETSAT helpdesk.
If unsuccessful, try other sections in the troubleshooting guide.
(B1.2) Receiving only a sub-set of data
Symptoms:
- Tellicast shell "Active Channels" shows only unencrypted Channels, e.g. SAF channels as active
- Getting the unencrypted SAF data e.g.:
ascat_yyyymmdd_hhnnss_metopa_06330_...
S-O3M_GOME_OE-NO2_L2_yyyymmddhhnnss_...
S-OSI_-KNMI-OS100_DS08007_...
S-LSA_-HDF5_LSASAF_MSG_...
Problem:
- 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 ![[External link]](/groups/jsp/documents/fragmentassets/icon_link_external_coloured.gif)
www.realvnc.com
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 4.2.5.4 (0x8514)
User Not present
Administrator Not present
- please send us a screen shot 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 screen shot 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:
recv.ini
recv-channels.ini
recv.log
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 www.mvps.org/marksxp/WindowsXP/java.php
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
Symptom:
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
example:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\BusinessTV-IP
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
Symptom:
No reception after installation of a new DVB card or USB box.
Following messages in recv.log: "... wrong interface address ..."
Problem:
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.
Solution:
-
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 192.168.238.238)
-
Subnet mask must be 255.255.255.0
-
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. 192.168.238.239.
-
Subnet mask must be 255.255.255.0
-
Other parameters (DNS, gateway) need not to be set.
-
Open the Tellicast client configuration file recv.ini
-
Set the same IP address: interface_address=192.168.238.239
(B9) No files received or many T icons in taskbar
Symptoms:
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 ..."
Problem:
Either the disk is full, or a file system is used that limits the number of directory entries (FAT, FAT32)
Solution:
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:
http://support.microsoft.com/?id=290766
(B11) Skystar2 cards: "Interference" with CYFRA on Windows
Symptoms:
The antenna icon is green but no connection to announcement and data channels in Tellicast software.
CYFRA may be displayed as the Network.
Problem:
Due to tolerances in manufacturing the DVB card locks to the next transponder.
Solution:
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
Symptoms:
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.
Problem:
This is usually caused by a Service error.
Solution:
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
SYMPTOMS:
The reception stops or does not work at all after entering new username/password
PROBLEM:
The username/password was incorrectly entered
SOLUTION:
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.
Do never attempt to change the password in the etoken properties, this might damage the EKU!
(B14) Tellicast problems under Windows 98 and/or ME
SYMPTOMS:
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
IPHLPAPI.DLL:FlushlpNetTable
- Startup of the Tellicast results in red icon and double-click on the icon shows "Attention, No License" message
PROBLEM:
The Tellicast client 2.4.4b is not compatible with some elements of Windows 98 and Windows ME
SOLUTION:
Tellicast client 2.4.4a will solve the problem, it is available from the EUMETSAT helpdesk.
(B15) Tellicast no reception while all DVB reception parameters seem ok
SYMPTOMS:
- 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.
PROBLEM:
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.
SOLUTION:
- 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
SYMPTOMS:
- 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
PROBLEM:
This is related to a Microsoft Windows OS problem.
SOLUTION:
- see
http://support.microsoft.com/kb/826722
- on XP, install SP2 or later on both, the receiving and sending PC
(B17) Frequent Windows crashes or hangups
SYMPTOMS:
- 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)
PROBLEM:
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.
SOLUTION:
Please apply one of the following steps at a time, then check it 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):
ATKKBService.exe
nTuneService.exe
PDVDServ.exe
RTHDCPL.exe
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
SYMPTOMS:
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.
PROBLEM:
- 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 reinitialized to getit working again.
SOLUTION:
Several methods can be used which are all described in the following link
http://www.david-taylor.myby.co.uk/software/msg_dm_pc.htm#AutomaticRestart. 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.
Downloads:
Tweak UI 2.10 for Windows XP at http://www.microsoft.com/windowsxp/downloads/powertoys/xppowertoys.mspx
Tweak UI 1.33 at http://www.microsoft.com/windowsxp/downloads/powertoys/xppowertoys.mspx
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]
"ForceAutoLogon"="1"
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, depeding 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:
[watchdog]
error_script=restart.bat
error_script_cause_announcement=60
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 login 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:
[watchdog]
#error_script=restart.bat
#error_script_cause_announcement=60
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
SYMPTOMS:
- 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.
PROBLEM:
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.
SOLUTION:
- 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 192.168.238.238). 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 224.0.0.0 mask 240.0.0.0 192.168.238.238
- then restart the PC
NOTE: if the DVB interface is on another IP address, use that address instead of 192.168.238.238
(B20) Vista Problems -
SYMPTOMS:
- Changing recv.ini does not seem to have any effect, cannot find
PROBLEM:
Windows Vista no longer allows programs to write in the C:\Program Files\ directory.
SOLUTION:
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
SYMPTOMS:
- after installation of EKU software (PKIClient) version 4.5 or later
from time to time Etoken pops up a window requiring the password
PROBLEM:
- the PKIMonitor is running, however this feature is not used by the EUMETCast software
SOLUTION:
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
(B22) Increased file losses after migration to Eurobird-9 with Skystar-2 DVB cards
SYMPTOMS:
- increased file losses after the Eurobird-9 upgrade package was applied on a Skystar-2 card
PROBLEM:
- 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
SOLUTION:
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
SYMPTOMS:
- 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
PROBLEM:
- the winsock settings are corrupted, possibly due to an incorrect installation of software.
- this inhibits the firewall services and control.
SOLUTION:
Step 1: follow the instructions in
http://support.microsoft.com/kb/914230#LetMeFixItMyselfAlways
to reset the winsock settings.
Step 2: if Step 1 didn't solve the problem, repair the WMI repository.
See
http://windowsxp.mvps.org/repairwmi.htm 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
PROBLEM:
- if the firewall is switched on, it stops multicast traffic from the DVB interface to Tellicast.
SOLUTION:
- 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
SYMPTOMS
- after a restart of the PC the Skystar card connects to the wrong satellite
PROBLEM:
-
the initial locking transponder is not correct, either not saved or not set.
SOLUTION:
- 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
SYMPTOMS:
N/A
PROBLEM:
- Windows is releasing a new version - Windows 7
SOLUTION:
- This solution has been tested on Windows 7 beta.
- Install the card in the PC
- Start the PC
- Download the latest driver package from the Technisat web site (we have tested soft_4.5.1_dvb_pv_tv_stars_6816.zip)
- Unzip the package and run the "start.exe" program to install the drivers/software
- Reboot the PC
- Install PKIClient 4.5 from the EUMETSAT CD following the instructions in the Readme(s)
- Insert the EKU
- Install the Tellicast software (2.4.4a) from the EUMETSAT CD following the instructions in the Readme(s)
- Follow the instructions for updating the Skystar II Cards database for the EB9 switch from the EUMETSAT CD e.g. Licence_cd_v5_5_11-02-2009\Windows\DVB-software\Windows_Migration_to_Eurobird-9\Readme.txt
(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)
SYMPTOMS:
* 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:
- Install pcsc-lite
rpm -i pcsc-lite-1.1.1-1-redhat.i386.rpm
- 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
- 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.
- 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)
- 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
Try:
- look at /etc/ld.so.conf (vi /etc/ld.so.conf)
- check for entries /usr/local/lib and /usr/lib
if they don't appear add them at the end, save file and then type
(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
- start etokend, pscsd, tellicast (in that order)
- 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 screen shot of this page
- send us following files
/var/log/dmesg
/var/log/messages
/etc/reader.conf
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.
Solution: 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.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)
- Ubuntu 8.04 (later versions see below):
- Edit the mountdevsusbfs.sh script e.g.:
# vi /etc/init.d/mountdevsubfs.sh
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/mountdevsubfs.sh 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 (H1) 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) goto (C3)
SYMPTOMS:
* 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.
PROBLEM:
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
...
PATH=/sbin:/bin:/usr/local/sbin:/usr/bin:/usr/sbin
LD_LIBRARY_PATH=/usr/lib:/usr/local/lib
export LD_ASSUME_KERNEL=2.4.1
SYSLOGD_OPTIONS="-d syslog"
...
- 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
/var/log/messages
/etc/init.d/pcscd
/etc/init.d/etokend
- after the test, disable the line in /etc/init.d/pcscd by preceeding it with a "#"
#SYSLOGD_OPTIONS="-d syslog"
SOLUTION:
- 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 the EUMETSAT 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.
(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"
hotbird6:10853.44:h:0:27500::::
atlanticbird3:3732:h:0:11963::::
nss806:3803:h:0:27500::::
- 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 http://sourceforge.net/projects/dvbtools/
- 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
Frequency=3803.000000
;Frequency=3731.757000
Symbol rate=28.93000
;Polar=VER
Polar=HOR
;Band=KU
Band=C
(C7) DVB Card hangup under Linux
SYMPTOMS:
After an interruption of the DVB downlink ( e.g. weather related) the
Pent@Value
DBV card might stop receiving data.
PROBLEM:
This is probably a driver problem, since it does not occur in the Windows version.
SOLUTION:
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/tellicast-error.sh with the following content:
/etc/init.d/pentaval restart
2. make the file executable
chmod +x /etc/tellicast-error.sh
3. modify the [watchdog] section in the Tellicast configuration file recv.ini
[watchdog]
error_script=/etc/tellicast-error.sh
error_script_cause_announcement=30
Note: this procedure may be adapted to the users needs for other DVB cards.
(C8) Firewall configuration tables (iptables)
SYMPTOMS:
No reception by Tellicast while all DVB reception parameters seem ok
PROBLEM:
The Linux firewalls (which are often installed by default - especially in newer builds) do not allow the
flow of DVB data.
SOLUTION:
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.
[ DVB CARD / 2.4 KERNEL ]
iptables -I INPUT -i pentaval0 -p udp -s 192.168.1.1 -j ACCEPT
[ DVB CARD / 2.4 KERNEL / SMCROUTE ]
iptables -I FORWARD -i pentaval0 -o dummy0 -p udp -s 192.168.1.1 -j ACCEPT
iptables -I INPUT -i dummy0 -p udp -s 192.168.1.1 -j ACCEPT
[ DVB CARD / 2.6 KERNEL / SMCROUTE ]
iptables -I FORWARD -i dvb0+ -o dummy0 -p udp -s 192.168.1.1 -j ACCEPT
iptables -I INPUT -i dummy0 -p udp -s 192.168.1.1 -j ACCEPT
[ DVB ROUTER ]
iptables -I INPUT -i eth1 -p udp -s 192.168.1.1 -j ACCEPT
[ DVB ROUTER / SMCROUTE ]
iptables -I FORWARD -i eth1 -o dummy0 -p udp -s 192.168.1.1 -j ACCEPT
iptables -I INPUT -i dummy0 -p udp -s 192.168.1.1 -j ACCEPT
[ DVB ROUTER WEB INTERFACE ]
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 192.168.1.1 -j ACCEPT
-I INPUT -i dummy0 -p udp -s 192.168.1.1 -j ACCEPT
(C9) EKU / USB Problems with new Linux distributions
SYMPTOMS:
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.
PROBLEM:
- Newer Linux versions have changed the devicenames/udev rules for usb devices.
SOLUTION:
- 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 with Ubuntu 9.10 distributions
SYMPTOMS:
Seen on:
- Ubuntu 9.10
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'
FAILED
PROBLEM:
The dummy module is not included by default in the /etc/modules for Ubuntu 9.10 version.
SOLUTION:
In a terminal window, type:
$ sudo su -
# echo dummy >> /etc/modules
then reboot the station.
(C11) Missing symbolic link for etoken libraries
Note: If the light on EKU is off (no red light) goto (C3)
SYMPTOMS:
Seen on:
- Ubuntu Server 8.04.1
- Ubuntu 9.04
- Debian 5.0 (Lenny), Kernel 2.6.26
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/aksifdh.so to /usr/local/lib/aksifdh.so.1.3-15.84
SOLUTION:
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/aksifdh.so.1.3-15.84 /usr/local/lib/aksifdh.so
(there should also be a copy in /usr/local/etoken/aksrte-3-15.84p3/aksifdh.so.1.3-15.84)
Then run ldconfig to be on the safe side
# ldconfig
then reboot the station.
(D) Common problems
(D1) Frequent loss of files
SYMPTOMS:
* 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 224.223.222.223:4711 completed (channel lost)
VRB:2005-04-08 09:10:36.703:Reconnecting to announcement channel `TSL Announcement Channel', address 224.223.222.223:4711 (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'
PROBLEM:
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
SOLUTION:
1. Check reception system, replace faulty or low quality hardware (LNB, cables, DVB cards), increase antenna size
2. Install a ramdisk (> 60 MB) and set following parameters in the recv.ini file (leave other parameters unchanged)
[locations]
file_database_directory=<directory name on ramdisk>
log_file=>>recv.log
# enables buffered write mode to log file
[logging]
log_level=normal
# verbose mode is intended for debugging
[parameters]
file_database_size=62914560
# this restricts the file database to 60 MB, the default value is 250 MB.
# make the ramdisk 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
SYMPTOMS:
The DVB reception software indicates one or more of the following:
- no signal or signal on noise level
- no carrier lock
- no data lock
PROBLEM:
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
SOLUTION:
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
SYMPTOMS:
* 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 224.223.222.21:2511 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 224.223.222.23:2611 completed (channel closed)
PROBLEM:
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.
SOLUTION:
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
SYMPTOMS:
intermittent reception problems in C-band
PROBLEM:
Radar interference can cause reception problems in C-Band.
SOLUTION:
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:
http://www.microwavefilter.com/tvrointerference.htm
The type is
13961
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
PROBLEM:
The data is temporarily not needed or there are performance problems receiving to many channels.
SOLUTION:
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]
target_directory=received
tmp_directory=received/tmp
[EUMETSAT Data Channel 2]
target_directory=received
tmp_directory=received/tmp
[EUMETSAT Data Channel 3]
target_directory=received
tmp_directory=received/tmp
#
# The commented channels will not be received
#
#[EUMETSAT Data Channel 5]
#target_directory=received
#tmp_directory=received/tmp
#
#[EUMETSAT Data Channel 6]
#target_directory=received
#tmp_directory=received/tmp
[SAF-Europe]
target_directory=received
tmp_directory=received/tmp
(D7) "Address already in use" messages in Tellicast logs
SYMPTOMS:
* 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!
PROBLEM:
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.
SOLUTION:
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
SYMPTOMS:
* in recv.log
messages like :
ERR:2006-05-30 13:49:41.250:Failed to open data channel `EUMETSAT Data Channel 1', address 224.223.222.1:4811 (wrong interface address 192.168.238.238?)
MSG:2006-05-30 13:49:41.250:Disconnect from data channel `EUMETSAT Data Channel 1', address 224.223.222.1:4811 completed (channel closed)
MSG:2006-05-30 13:49:45.000:Disconnect from data channel `EUMETSAT Data Channel 1', address 224.223.222.1:4811 completed (channel closed)
PROBLEM:
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 ramdisk with sufficient size for the subscribed services (e.g. 60 MB MSG1 only, 500 MB all including EPS)
- specify the ramdisk location (e.g. if G:\ is the ramdisk under Windows)
[locations]
file_database_directory=G:\
- specify the maximum size in recv.ini (should be less than the physical size)
[parameters]
file_database_size=62914560
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]
target_directory=/data/received
tmp_directory=/data/received/tmp
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
[locations]
log_file=>>recv.log
[logging]
#log_level=none
#log_level=quiet
log_level=normal
#log_level=verbose
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.
[parameters]
#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
Symptoms:
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 stronly 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"
SYMPTOMS:
* 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).
PROBLEM:
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.
SOLUTION:
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 ramdisk size for the file database
This section gives some help to determine the best ramdisk 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 ramdisk 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 ramdisk.
8. Add 30% to this value from step 7. Configure the ramdisk 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)
SYMPTOMS:
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.
PROBLEM:
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
SOLUTION:
Install a ram disk and put the file database on the ramdisk, details see D9 and D12.
(D14) Frequent loss of files at high data rates with certain DVB cards
SYMPTOMS:
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.
PROBLEM:
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
SOLUTION:
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
SYMPTOMS:
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).
PROBLEM:
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.
SOLUTION:
- 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'
(D16) Frequent loss of lock on Eurobird 9 when several DVB devices are connected via RF signal splitters
SYMPTOMS:
The DVB reception is interrupted in regular intervals when a splitter is used to feed several stations from one antenna.
PROBLEM:
The EUMETCast transponder on Eurobird is on the high band. A 22 KHz signal is sent from the DVB card/box to switch
the LNB into high band. If multiple DVB devices are connected via a signal splitter, the 22 KHz signals from several
devices might cancel out if phase and amplitudes are unfavourable.
This effect is most pronounced on a two station system.
SOLUTION:
- disable the 22 KHz signal or the DVB card on one station
This solution leaves only cold redundancy - if the DVB card providing the 22 KHz signal fails, reception is lost on both stations.
- insert an attenuator in the signal path of on station only, i.e. between the splitter and the DVB card
(inserting one additional splitter has been successfully tested and will be sufficient in most cases)
This solution maintains hot redundancy - the system will continue receiving even if one station fails.
(D17) No Ku-band EUMETCast data - Good signal but Yellow "T" with correct transponder settings
SYMPTOMS:
No data received, the "T" is yellow. Signal strength is good.
On Skystar cards the Network displayed on setup4pc 'Sky'.
PROBLEM:
Although you have changed all your settings correctly, you have not yet
moved your antenna to the new position 9° E for Eurobird 9a
SOLUTION:
Repoint the antenna. See http://www.satsig.net/maps/lat-long-finder.htm
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
ALTERNATIVE SOLUTION:
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
![[Internal link]](/groups/jsp/documents/fragmentassets/icon_link_coloured.gif){kind=icon}
EO Portal![[Internal link]](/groups/jsp/documents/fragmentassets/icon_link_coloured_down.gif){kind=icon}
EUMETCast
Print 