Reorganisation of EUMETCast Satellite data flows

For a better usage and share of the EUMETCast bandwidth between all Copernicus missions, Sentinel-3 data and future Copernicus data will be gathered on one same transponder, TP2. In order to achieve this, a re-organisation of the data flows on EUMETCast-Satellite is necessary and will take place, as follows:

• Sentinel-3A data will be transferred to TP2, which will be used to disseminate Sentinel-3B and Sentinel-5P data.
• Third-party data which are currently on TP2 — GOES-16 data and NOAA-20 global data — will be transferred to TP1.

To support users in their preparation for these changes, periods of parallel disseminations on both TP1 and TP2 are planned:

User actions

A) DVB reception changes

If your system already supports 2 transponders, go to section B).

1. Users who want to receive data from both transponders need two DVB receivers.
   A minimum hardware upgrade to support 2 transponders is shown in the following figure. A passive splitter is inserted in the antenna cable and splits the incoming IF signal (0.9 – 2.1 GHz) into multiple output ports to which the DVB receivers can be directly connected. They usually allow DC pass-through from the receivers in order to feed power to the LNB.

   

2. Users currently receiving Sentinel-3A data only (i.e. receiving only the High Volume Service on TP1 and not the Basic Service) can simply reconfigure the existing receiver for the second transponder to receive all of the Sentinel-3 products. It is however recommended to add a second receiver to be able to receive products from both transponders.
3. Please follow the DVB receiver setup guides in the Devices section on the Reception Station Set-up page to configure the receivers for transponder 1 and/or transponder 2.
4. Linux users that have installed the dvb-eumetcast package using the EUMETSAT provided tar/rpm/deb packages can update to the latest version supporting all EUMETCast services on all transponders using multiple DVB cards or a DVB card with multiple inputs. A new dvb-eumetcast package is available for download from our ftp site: ftp://ftp.eumetsat.int/pub/OPS/out/user/EUMETCast_Support/EUMETCast_Licence_cd/Linux/DVB_devices/Common_Apps/

B) Tellicast client changes — Preparations for parallel phase I

Sentinel-3A products will be disseminated on TP2 using the following channels:

To receive the Sentinel-3A data stream on TP2, the following needs to be done:

• Tellicast client configuration change: for the users that already receive HVS-2, add to cast-client-channels_hvs-2.ini the following:

  [channel]
  name=E2H-S3A-01
  target_directory=data/eumetcast/hvs-2/E2H-S3A-01
  tmp_directory=data/tmp/hvs-2

  [channel]
  name=E2H-S3A-02
  target_directory=data/eumetcast/hvs-2/E2H-S3A-02
  tmp_directory=data/tmp/hvs-2

  [channel]
  name=E2H-S3A-03
  target_directory=data/eumetcast/hvs-2/E2H-S3A-03
  tmp_directory=data/tmp/hvs-2

  [channel]
  name=E2H-S3A-04
  target_directory=data/eumetcast/hvs-2/E2H-S3A-04
  tmp_directory=data/tmp/hvs-2

  [channel]
  name=E2H-S3A-05
  target_directory=data/eumetcast/hvs-2/E2H-S3A-05
  tmp_directory=data/tmp/hvs-2

  [channel]
  name=E2H-S3A-06
  target_directory=data/eumetcast/hvs-2/E2H-S3A-06
  tmp_directory=data/tmp/hvs-2

  [channel]
  name=E2H-S3A-07
  target_directory=data/eumetcast/hvs-2/E2H-S3A-07
  tmp_directory=data/tmp/hvs-2

  [channel]
  name=E2H-S3A-08
  target_directory=data/eumetcast/hvs-2/E2H-S3A-08
  tmp_directory=data/tmp/hvs-2

• Or, alternatively, add (or use the existing) generic entry:

  [channel]
  name=*
  target_directory=data/eumetcast/hvs-2/default
  tmp_directory=data/tmp/hvs-2

Please note: you can use your own directories, but the location of tmp and target directory must be in the same file system.

C) Tellicast client changes — Preparations for parallel phase II

Third party data which are currently on TP2 — GOES-16 and NOAA-20 global data — will be disseminated on TP1 using the following channels:

To receive the “Third Party Data” (NOAA-20, GOES-16) stream on TP1, the following needs to be done:

• Tellicast client configuration change: for the users that already receive HVS-1, add to cast-client-channels_hvs-1.ini the following:

  [channel]
  name=E1H-TPL-1
  target_directory=data/eumetcast/hvs-1/ E1H-TPL-1
  tmp_directory=data/tmp/hvs-1

  [channel]
  name=E1H-TPG-1
  target_directory=data/eumetcast/hvs-1/ E1H-TPG-1
  tmp_directory=data/tmp/hvs-1

  [channel]
  name=E1H-TPG-2
  target_directory=data/eumetcast/hvs-1/ E1H-TPG-2
  tmp_directory=data/tmp/hvs-1

• Or, alternatively, add (or use the existing) generic entry:

  [channel]
  name=*
  target_directory=data/eumetcast/hvs-1/default
  tmp_directory=data/tmp/hvs-1

Please note: you can use your own directories, but the location of tmp and target directory must be in the same file system

D) The new Tellicast package on ftp site

In order to facilitate the migration, a new Tellicast package containing the new channels is available from our ftp site:

Linux: ftp://ftp.eumetsat.int/pub/OPS/out/user/EUMETCast_Support/EUMETCast_Licence_cd/Linux/Tellicast/
Windows: ftp://ftp.eumetsat.int/pub/OPS/out/user/EUMETCast_Support/EUMETCast_Licence_cd/Windows/Tellicast/

Note: It is not mandatory to have Tellicast Client V2.14.4 to receive the data, the required configuration changes work also with V2.12 or later. If you have an older version, please contact our User Service Helpdesk.

More details about TP1, TP2, Channels and PIDs can be found on the Channels & PIDS page.

For further information, contact our User Service Helpdesk.