Sample files as requested:

https://www.satsignal.eu/wxsat/cast-client-channels-bas.ini.txt
https://www.satsignal.eu/wxsat/cast-client-channels-hvs-1.ini.txt

I've added the .TXT extension so that you can download them without any
malware warnings.  You could right-click, properties, unblock before use
and, of course, these are simply sample working files taken from my own
systems, and would need editing to suit your own data needs and directory
structure.

Please see the examples I just linked to.

I tried a greater bugger size (16 MB) for the HVS-1/2 instances, but I don't
think it made a lot of difference to be honest.  Better ways to reduce data
loss!

The version supplied by EUMETSAT is a good template.

Cheers,
David

John,

It sounds as though you are making some progress - that's good.

Yes, 2.14.5 is current.  I cheated an just copied the minimum files as I
didn't want to go through all the reconfiguration again, and was uncertain
whether the install.exe offered an "update the minimum" option.  The minimum
files are the tc-cast-client.exe and licence.ini.

It looks like I did leave out the tmp_directory, but that does restrict you
to having all the data coming into one partition.  I configure the tmp in
the cast-client.ini.  For the Basic Service I use a RAMdisk:

[parameters]
tmp_directory=Z:\EUMETCast\tmp

and for the HVS-1 (where I take the minimum data, a directory on the
receiving drive (i.e. partition letter):

[parameters]
tmp_directory=L:\Tools\EUMETCast\tmp_2

I used a RAMdisk on BAS as I was upgrading from an earlier installation, and
a separate physical HD on the HVS-1 system sort of a a test.  With ONLY the
HVS-1 data on that HD (a cheap 1 TB drive), there appears to be no need for
a RAMdisk.  Your configuration will vary!

I would strongly advise against the "default" directory, you can fill HDs
very easily that way, and create an unnecessary workload for TelliCast and
the HDs.  Define all the channels you want, and comment out the default.  I
think you're already doing that.

It doesn't matter where the executable and the configuration files live.

Leave the buffer at the EUMETSAT suggested 8 MB value.  As before, start
with the minimum to prove things work, and then build up the other channels.

I'm running four MSG Data Managers on one PC (IODC, RSS, Himawari,
0-degree), and three on another PC (IODC, RSS, 0-degree/Himawari).  On the
third system it's still like the old days - the MDM IODC/RSS/0-degree) as
that PC is BAS-only.

I'm running three Metop Managers on the systems with HVS-1 access, two on
the BAS system, with the Metop-B instance as the NOAA-19 handler, as the
Metop-A data is moving to HVS-1 soon.

Many ways to skin this cat!

David,

Looks like I will need two copies of 'GDM ' since the data folder names are different - hence Tellicast received flies location path.

Or, could

Regards,

John.

John,

With the large number of services now offering Sentinel derived data - some
free of charge - I'm not that convinced that it's worth collecting.  I
wonder what others think?

The zero degree MSG Data Manager can handle Himawari data as well, but needs
a little fiddling to get both into the single Manager, which can read both
"Data Channel 4" and "EUMETSAT_Data_Channel_4".  Use one for the BAS/Chan.4
data and the other for HVS-1/Himawari data.  But using four is simpler.  3 x
Metop, 2 x ABI.  FOr a few more weeks there's also GOES-15 in EUMETSAT's

format.

GOES-15 information is here:

  https://www.eumetsat.int/website/home/News/DAT_4167864.html

It's a temporary service, and I have a free program to handle the data.

Some of the sounding files will be handled by the Metop Managers, I recall.

Yes, the GOES-15 is purely a transition arrangement, which is coming to an
end - perhaps before the second half of the year.  In any case, there are
some issues with processing the data in real-time (the location information
is sent /after/ the data, not before!).

Each Metop satellite offers data named like:

  W_XX-EUMETSAT-Darmstadt,SOUNDING+SATELLITE,METOPA+AVHRR
  W_XX-EUMETSAT-Darmstadt,SOUNDING+SATELLITE,METOPB+AVHRR
  W_XX-EUMETSAT-Darmstadt,SOUNDING+SATELLITE,METOPC+AVHRR

These are air motion vectors, and the Metop Manager will handle them if the
Process AVHRR polar winds box is checked, so if you're getting that data you
need a third Metop Manager for Metop-C.  That's on EPS-10 as it's from the
AVHRR instrument.

The highest resolution Sentinel data is from Sentinel-2, and that's not on
EUMETCast.  The Sentinel-3 data (which is) is 300m resolution.  I don't know
whether anyone is still taking Sentinel data on a regular basis as it's
readily available in image form from the Internet, and various folk have
written quite complex processing scripts to make the most of the data.  Folk
here have written scripts to keep data for a particular area of interest
up-to-date.

Interestingly, the data flow from the next generation of satellites is
reported to be ten times what we have at the moment.  How many transponders
on which satellites will that take!