It would appear that the new Basic Service Channels reorganisation due to start today at 10.00 UTC ( except for MSG and EARS - 22/3/2022 ) has not happened.

Regards
Ian.

Hi

No files on renamed BAS channels here either. Latest files shortly before 10:00 UTC.

Regards,
Ernst

On 01/03/2022 13:54, Ernst Lobsiger via groups.io wrote:

Hi
No files on renamed BAS channels here either. Latest files shortly before 10:00 UTC.
Regards,
Ernst

======================================================================

Ernst,

Thank you for your confirmation.

I have sent a mail to OPS asking if it has been postponed and if so likely new date. Depending on reply I may have to re-install my old Tellique to get back Metop, NOAA etc.

Regards
Ian.

Ian,

these are the error messages I get in the WEB interface of my GNU/Linux BASIC SERVICE only receiver. Have I done something wrong? Do others have similar problems?
...

ERR:2022-03-01 14:11:56.058:Cannot rename file "/srv/tmpdir_bas/621e299500c375a5.tmp" to "/opt/E1B-GEO-1/H-000-MSG1__-MSG1_IODC___-HRV______-000019___-202203011400-C_" (Invalid cross-device link)
ERR:2022-03-01 14:12:15.744:Cannot rename file "/srv/tmpdir_bas/621e29b300c3762a.tmp" to "/opt/E1B-GEO-1/H-000-MSG1__-MSG1_IODC___-HRV______-000020___-202203011400-C_" (Invalid cross-device link)
ERR:2022-03-01 14:12:19.004:Cannot rename file "/srv/tmpdir_bas/621e287400c37104.tmp" to "/opt/E1B-TPL-1/thin_MOD021KM.A2022060.1305.061.2022060135908.NRT.hdf" (Invalid cross-device link)
ERR:2022-03-01 14:12:20.790:Cannot rename file "/srv/tmpdir_bas/621e287400c37105.tmp" to "/opt/E1B-TPL-1/thin_MOD021KM.A2022060.1310.061.2022060135908.NRT.hdf" (Invalid cross-device link)
ERR:2022-03-01 14:12:23.047:Cannot rename file "/srv/tmpdir_bas/621e287400c37106.tmp" to "/opt/E1B-TPL-1/thin_MOD021KM.A2022060.1315.061.2022060135908.NRT.hdf" (Invalid cross-device link)
ERR:2022-03-01 14:12:30.742:Cannot rename file "/srv/tmpdir_bas/621e29c700c37699.tmp" to "/opt/E1B-GEO-1/H-000-MSG1__-MSG1_IODC___-VIS006___-000007___-202203011400-C_" (Invalid cross-device link)
ERR:2022-03-01 14:12:34.182:Cannot rename file "/srv/tmpdir_bas/621e29c700c3769a.tmp" to "/opt/E1B-GEO-1/H-000-MSG1__-MSG1_IODC___-VIS008___-000007___-202203011400-C_" (Invalid cross-device link)
ERR:2022-03-01 14:12:37.886:Cannot rename file "/srv/tmpdir_bas/621e29c700c3769b.tmp" to "/opt/E1B-GEO-1/H-000-MSG1__-MSG1_IODC___-IR_016___-000007___-202203011400-C_" (Invalid cross-device link)
ERR:2022-03-01 14:12:41.209:Cannot rename file "/srv/tmpdir_bas/621e29c700c3769c.tmp" to "/opt/E1B-GEO-1/H-000-MSG1__-MSG1_IODC___-IR_039___-000007___-202203011400-C_" (Invalid cross-device link)
ERR:2022-03-01 14:12:45.004:Cannot rename file "/srv/tmpdir_bas/621e29c700c3769d.tmp" to "/opt/E1B-GEO-1/H-000-MSG1__-MSG1_IODC___-WV_062___-000007___-202203011400-C_" (Invalid cross-device link)
ERR:2022-03-01 14:12:48.592:Cannot rename file "/srv/tmpdir_bas/621e29c700c3769e.tmp" to "/opt/E1B-GEO-1/H-000-MSG1__-MSG1_IODC___-WV_073___-000007___-202203011400-C_" (Invalid cross-device link)

Restarting TelliCast did not help ...

Regards,
Ernst

On Tue, Mar 1, 2022 at 06:26 AM, Ernst Lobsiger wrote:

Have I done something wrong?

OK,

E1B-GEO-1

E1B-GEO-1

301

500

224.223.222.27

2   000

IODC   High Rate SEVIRI

The problem seems to be the change from OLD PID 301 to NEW PID 500. This means under GNU/Linux I have to change the file /etc/eumetcast-channels.cfg.

Obviously EUMETSAT still distributes the old setup file /etc/eumetcast-channels.cfg from April 11 2021


Regards,
Ernst

P.S. Not sure this means anything on the Windows side ...

On Tue, Mar 1, 2022 at 06:40 AM, Ernst Lobsiger wrote:

E1B-GEO-1   E1B-GEO-1    301   500   224.223.222.27   2000     IODC   High Rate SEVIRI

Things are getting worse: Above is what the EUMETSAT WEB page says. IODC changes from PID 301 to PID 500.
But when I check in my /etc/eumetcast-channels.cfg from April 11 2021 it has been 500 ever since. WEB is wrong!

There are a couple of other lines where PIDs 300 and 301 has to be replaced by 100 and 500 though ...
This is rather a lot of manual work and will show whether the above is the only typo on the WEB page.

Ernst

I have just had a reply from Eumetsat, who have confirmed that the Basic Service Channels reorganisation has been implemented as planned and they want to check my BAS channel configuration file.

Regards
Ian.

Hi Ernst and Ian

I am still getting data , however I did things slightly differently

I manually edited my bas file and kept the old and new channels and pointed the new channels to the old directory if it was necessary

I am still getting data and no error messages

Regards

Graham

On 01/03/2022 14:31, g-woolf@... via groups.io wrote:

Hi Ernst and Ian

I am still getting data , however I did things slightly differently

I manually edited my bas file and kept the old and new channels and pointed the
new channels to the old directory if it was necessary

I am still getting data and no error messages

Regards

Graham

That's just what the EUMETSAT upgrade script did.

Having said that it didn't like my BAS channels file being in a different
location. I left both old and new data streams pointing to the original
received channels.

Cheers,
David
--
SatSignal Software - Quality software for you
Web: https://www.satsignal.eu
Email: david-taylor@...
Twitter: @gm8arv

I have to report that suddenly at about 15.50 UTC data started coming in on the new channels on my channels_bas.ini without any changes being made by myself.

I can only conclude that something was done at the Eumetsat end.
I have now reported this to Eumetsat.

Regards
Ian.

On Tue, Mar 1, 2022 at 08:38 AM, g-woolf@... wrote:

Hi Ernst and Ian

I am still getting data , however I did things slightly differently

I manually edited my bas file and kept the old and new channels and pointed the new channels to the old directory if it was necessary

I am still getting data and no error messages

Graham,

my problem was that I copied a reworked cast-client-channels_bas.ini from a receiver with RAM-disk to a receiver without.
The problem of  /etc/eumetcast-channels.cfg  remains as there are still entries of PID 300 and PID 301. On the other hand
the EUMETSAT reorganisation WEB page has typos and there seems to be some not listed multicast addresses used.

I will contact OPS that EUMETSAT provides an updated  /etc/eumetcast-channels.cfg  file for users with GNU/Linux receivers.
I have now all 4 receivers running and use the new BASIC channel names also as names for the respective target directories.
This of course means that I also had to change the variable segdir and the caption in a bunch of my PyTROLL/Satpy scripts.
All working now.

Regards,
Ernst

On 01/03/2022 14:31, g-woolf@... via groups.io wrote:

Hi Ernst and Ian
I am still getting data , however I did things slightly differently
I manually edited my bas file and kept the old and new channels and pointed the new channels to the old directory if it was necessary
I am still getting data and no error messages
Regards
Graham

=================================================================================

I did the same with a simple manual change and then kept both until the appropriate time.
However Ian was right in that the change to the new channel names did not occur until late afternoon. All worked well.
Note however that NOAA-20 data is considered as EARS although not in the old EARS channel and so NPP-2 is still in operation and not EIB-RDS-2 until 22nd March presumably.

Regards,
Douglas.

On Tue, Mar 1, 2022 at 02:03 PM, Douglas Deans wrote:

Note however that NOAA-20 data is considered as EARS although not in the old EARS channel and so NPP-2 is still in operation and not EIB-RDS-2 until 22nd March presumably.

Yes, and one hour ago E1B-GEO-1 (IODC, high rate SEVIRI) was still disseminated on 224.223.222.23 PID 301 and not on 224.223.222.27 PID 500 as noted on EUMETSATs WEB page.

Ernst

Hi all,

ongoing problems on BAS here. I have a cast-client-channels_bas.ini with NEW channel naming ONLY.
I do still get DVB traffic on Basic Service PID 300 and PID 301 which EUMETSAT said will be emptied.

I receive no files on E1B-GEO-3 (MSG4 0° seviri) and E1B-GEO-5 (MSG3 9.5° RSS).
When I do not setup PID 301 I have also problems with E1B-GEO-1 (MSG1 41.5° IODC).

WRN:2022-03-02 09:53:51.871:Failed to open data channel `E1B-GEO-1', address 224.223.222.23:6015: No data received from sender

but as I pointed out yesterday this multicast address is not on the EUMETCast BAS reorganisation WEB page. It should be 224.223.222.27 PID 500.

Is there someone that has a setup with the NEW channel names ONLY, that can confirm files on E1B-GEO-3, E1B-GEO-5, E1B-GEO-1 on PID 500?
Any feedbacks from OPS?

Best regards,
Ernst

On 02/03/2022 10:16, Ernst Lobsiger via groups.io wrote:

Hi all,
ongoing problems on BAS here. I have a cast-client-channels_bas.ini with NEW channel naming ONLY.
I do still get DVB traffic on Basic Service PID 300 and PID 301 which EUMETSAT said will be emptied.
I receive no files on E1B-GEO-3 (MSG4 0° seviri) and E1B-GEO-5 (MSG3 9.5° RSS).
When I do not setup PID 301 I have also problems with E1B-GEO-1 (MSG1 41.5° IODC).
WRN:2022-03-02 09:53:51.871:Failed to open data channel `E1B-GEO-1', address 224.223.222.23:6015: No data received from sender
but as I pointed out yesterday this multicast address is not on the EUMETCast BAS reorganisation WEB page. It should be 224.223.222.27 PID 500.
Is there someone that has a setup with the NEW channel names ONLY, that can confirm files on E1B-GEO-3, E1B-GEO-5, E1B-GEO-1 on PID 500?
Any feedbacks from OPS?
Best regards,
Ernst

==========================================================================================

Ernst perhaps I am misunderstanding your issue but MSG services (and EARS) on the new Channels will not commence until 22nd March.
I am not receiving any of the above channels and continuing to use the old channels. The PID issue is not relevant to Windows users.
In addition just to confuse us RSS is off until Thursday.

Regards,
Douglas.

Hi Ernst

Here is my eumetcast-channels .cfg

Do I need to change anything

Out of interest what are you using all 4 receivers for - are you still using a single cable operation

I know I will need to use two cables after the transponder changes later this year

On Wed, Mar 2, 2022 at 02:40 AM, Douglas Deans wrote:

Ernst perhaps I am misunderstanding your issue but MSG services (and EARS) on the new Channels will not commence until 22nd March.

Douglas,

thanks for that. My not perfect English seems to be the problem. I took "MSG mission data" for some files I'm not interested in.

From the EUMETSAT WEB page : "All datasets will be moved to the new channels, except EARS and MSG mission data."

All falls into place now. I kept NPP-2 (EARS) as channel name for NOAA20 and only changed the target to E1B-RDS-2 though.

Thanks again,
Ernst

On Wed, Mar 2, 2022 at 02:46 AM, g-woolf@... wrote:

Hi Ernst

Here is my eumetcast-channels .cfg

Do I need to change anything

Graham,

some time after March 22. EUMETSAT should provide a new version of  eumetcast-channels.cfg  with PID 300 and PID 301 eliminated.
As Douglas just explained to me that all MSG data channels will not migrate until March 22.,  so don't change anything in your *.cfg now.

Regards,
Ernst