Date   

Re: RSS

Douglas Deans
 

On 10/08/2018 17:05, Ian Deans via Groups.Io wrote:
I see from the Weekly Operations Schedule that there is to be an extension of the RSS processing area from the 29/8/2018.
Unfortunately the URL they give for details and sample files does not appear to exist !!
Regards
Ian.
=============================================================================

There is an error in the address. I went into News Items on the Eumetsat site and found the correct address :-

https://www.eumetsat.int/website/home/News/DAT_4019034.html?lang=EN&pState=1

Regards,
Douglas.


Re: RSS

Thorsten Miglus
 

Hi Ian,

this link works for me:
https://www.eumetsat.int/website/home/News/DAT_4019034.html

Cheers,
Thorsten


On Fri, Aug 10, 2018 at 06:05 PM, Ian Deans wrote:
I see from the Weekly Operations Schedule that there is to be an extension of the RSS processing area from the 29/8/2018.

Unfortunately the URL they give for details and sample files does not appear to exist !!

Regards
Ian.


RSS

Ian Deans
 

I see from the Weekly Operations Schedule that there is to be an extension of the RSS processing area from the 29/8/2018.

Unfortunately the URL they give for details and sample files does not appear to exist !!

Regards
Ian.


Re: Tellicast client version 2.14.4 for Linux

David J Taylor GM8ARV 🏴󠁧󠁢󠁳󠁣󠁴󠁿 🇪🇺
 

Hi All,

As promised I did some "beta testing" of TC client 2.14.4.
David mentionned that documentation of the new parameters
under Windows is missing. Here some answers to his questions.

I found not much new except for the EUMETSAT distributed
channel ini files do not work as expected under GNU/Linux.
"receive_buffer_size=8000000" seems to be a no go :-(.

Attached my findings so far ...

Cheers,
Ernst
==========================================

Ernst,

Many thanks for that.

As all the other parameters are specified in bytes, I expect that the buffer size is as well. The pedants would be arguing between MB and MiB!

There was a note in the current TD15 that the default buffer size - if not specified - was 4000000. That note also suggests it's since 2.14.4 (meaning 2.14.4 and later, or post 2.1.14, perhaps a subtly different meaning in the German?).

https://www.eumetsat.int/website/wcm/idc/idcplg?IdcService=GET_FILE&dDocName=PDF_TD15_EUMETCAST&RevisionSelectionMethod=LatestReleased&Rendition=Web

I found that the 2.14.4 program worked as expected both without a buffer size begin specified (i.e. just replacing the .exe and the licence.ini file in Windows systems), and with the buffer as 8000000 as in the EUMETCast example channels file.

I'm also using a RAMdisk for temp and received files on some systems, a RAMdisk for temp on others, and no RAMdisk at all on other systems (one HVS-1 and one HVS-2). I'm trying to see whether there are any differences although the measurements are made more difficult here partially because of the slight skew error, and partially because of the low signal here (with the weather conditions making things worse).

It's too early to tell whether there's any difference. Whilst I agree that having the temp.data RAMdisk helps, it's still possible that that using a bigger buffer in the TelliCast would reduce the number of calls to the OS for disk I/O operations, so there might be a benefit.

But most of my problems with HVS-2 are lost TelliCast packets, so if they're not coming in over the network there's not much you can do about that, unless in the exceptional case of the network interface (or virtual network in the TBS PCIe case) not having enough buffering. As we're using gigabit interfaces and network cards on the Ayecka SR1 that's capable of speeds some 12 times in excess of what's needed. Interestingly, the SR1 can occasionally produce zero packet loss on the PC without a RAMdisk at all, while the TBS/temp/files/RAMdisk system always has missed & recovered packets.

Fun, this TelliCast, isn't it!

Cheers,
David
--
SatSignal Software - Quality software written to your requirements
Web: http://www.satsignal.eu
Email: david-taylor@...
Twitter: @gm8arv


Re: Tellicast client version 2.14.4 for Linux

Ernst Lobsiger
 

Hi All,

As promised I did some "beta testing" of TC client 2.14.4.
David mentionned that documentation of the new parameters
under Windows is missing. Here some answers to his questions.

I found not much new except for the EUMETSAT distributed
channel ini files do not work as expected under GNU/Linux.
"receive_buffer_size=8000000" seems to be a no go :-(.

Attached my findings so far ...

Cheers,
Ernst


GOES 17 ABI problem update.

Douglas Deans
 

Another interesting update from NOAA re the GOES 17 ABI IR issue.
Looks as if it will go into GOES W service by the end of the year as even with its limitations it is still far better than GOES 15.
Please see :-

https://www.nesdis.noaa.gov/content/noaa-shares-first-infrared-imagery-goes-17-satellite

Regards,
Douglas.


Planned Termination of NOAA's U.S. DOMSAT Meteosat Second Generation (MSG) Broadcast Service

David J Taylor GM8ARV 🏴󠁧󠁢󠁳󠁣󠁴󠁿 🇪🇺
 

For some USA users. Looks like Internet access will be available instead.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
*Topic: *Planned Termination of NOAA's U.S. DOMSAT Meteosat Second Generation (MSG) Broadcast Service

*Date/Time Issued:* August 7, 2018 1430 UTC

*Product(s) or Data Impacted:* EUMETSAT's Prime Satellite (0 degree) Meteosat-11 MSG HRIT Data

*Date/Time of Initial Impact:* Tentatively mid-November 2018

*Date/Time of Expected End: *Indefinitely

*Details/Specifics of Change:* In coordination with EUMETSAT, NOAA/NESDIS plans to terminate its U.S. DOMSAT direct broadcast of MSG 0 degree Prime satellite data (currently Meteosat-11) in the mid-November 2018 time frame. This service termination is due in large part to obsolete equipment, limited distribution capacity and other factors such as the availability of robust data delivery systems.

In parallel with the U.S. DOMSAT service, NOAA/NESDIS has Meteosat-11 HRIT data available for its authorized users from its Product Distribution and Access (PDA) system (24x7 support) and from STAR FTP services (best effort support). In preparation for the loss of the U.S. DOMSAT MSG broadcast service, 24x7 operational users can access the MSG data from the NESDIS PDA or for non-operational users, from NESDIS STAR.

Please contact "nesdis.data.access@... <mailto:nesdis.data.access@...>" for additional information to acquire MSG 0 degree Prime satellite data (currently Meteosat-11) from the NESDIS PDA or from the NESDIS STAR server. Following further coordination with EUMETSAT, in the early fall 2018 time frame, NESDIS will provide the specific November 2018 date of U.S. DOMSAT MSG service termination.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Cheers,
David
--
SatSignal Software - Quality software written to your requirements
Web: http://www.satsignal.eu
Email: david-taylor@...
Twitter: @gm8arv


Re: Tellicast client version 2.14.4 for Linux

David J Taylor GM8ARV 🏴󠁧󠁢󠁳󠁣󠁴󠁿 🇪🇺
 

Hi David,

This is indeed quite an elaborate setup !
I don't monitor as such, but sometimes I leave my system running for a few days on end, and I never saw any segments loss in normal weather.
We have here in Belgium a good signal and my parabolic antenne is 1.25 m in diameter
I think that you don't need a powerful pc for Eumetcast , because the performance of the tellicast client software is very good. What's more important is the speed of the hard disks.

Cheers,
Hugo
===============================

Hugo,

The setup has just grown over the years, as I have been involved in EUMETCast almost before it started (it was used for Meteosat-6 and -7 data).

I envy your good signal!

Much of the effort in the early days (2003) was devoted to getting TelliCast to work as well as possible on the PCs which were affordable at that time. Memory was expensive, and affordable HDs were slow. Different motherboards and different network adapters performed better or worse, and sometimes you needed to find the "best" combination.

More recently the challenge has moved to receiving some 400 GB of data per day. I'd agree that for reception alone processing power is not so important, but having multiple cores helps (hyperthreading didn't work as well with earlier versions of the software). For processing both CPU power and memory is needed, particularly for the highest resolution data. Memory is also important for buffering HDs. Selection of data by PID and channel filtering is very important too.

You might like to automate missed and recovered packet reporting using one of Ernst's scripts - when you have a spare 5 minutes!

Cheers,
David
--
SatSignal Software - Quality software written to your requirements
Web: http://www.satsignal.eu
Email: david-taylor@...
Twitter: @gm8arv


Re: Tellicast client version 2.14.4 for Linux

Hugo
 

Hi David,

This is indeed quite an elaborate setup !
I don't monitor as such, but sometimes I leave my system running for a few days on end, and I never saw any segments loss in normal weather.
We have here in Belgium a good signal and my parabolic antenne is 1.25 m in diameter.
I think that you don't need a powerful pc for Eumetcast , because the performance of the tellicast client software is very good. What's more important is the speed of the hard disks.

Cheers,

Hugo


Re: Austria weather....

David J Taylor GM8ARV 🏴󠁧󠁢󠁳󠁣󠁴󠁿 🇪🇺
 

Looks like storms over Aflenz causing signal level drops. Possibly a switch to the Vienna uplink instead.

Cheers,
David
===========================================

Robert Moore asked m to post this, as he is having access issues....

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Staying with my son in South Tyrol - magnificent thunder storms, almost an hour and a half of continuous lightning last night. David's lightning detector picked up over 700 strikes within 40km (that's David Moore).
Will be posting pictures to TORRO website and a film on the web - will notify Group of the latter.
BTW South Tyrol is in Italy - used to be in Austria - but thereby hangs a complicated story!

Robert
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Cheers,
David
--
SatSignal Software - Quality software written to your requirements
Web: http://www.satsignal.eu
Email: david-taylor@...
Twitter: @gm8arv


Re: Tellicast client version 2.14.4 for Linux

David J Taylor GM8ARV 🏴󠁧󠁢󠁳󠁣󠁴󠁿 🇪🇺
 

Hi David,

If you use 'minimal' hardware ( Pentium, 486 ) than Linux is the only solution. You can't run Windows 10 on a 486 PC ...
I have only one receiving PC ( a Pentium from several years ago ) were I run BS, HVS-1 and HVS-2 without any problems.
Why do you use four PC's to receive Eumetcast ? Redundency ?

Kind regards,
Hugo
========================================

For testing, Hugo, with multiple receivers, TelliCast versions, and configurations (e.g. no RAMdisk, with RAMdisk for temp, with RAMdisk for temp & received). It's actually five PCs, as shown here:

https://www.satsignal.eu/mrtg/performance_eumetcast-dvb-s2.php#config

I have a spare LNB feed I can use for checking the cross-polarised signal.

Good news that you are able to use an older PC for EUMETCast. Do you monitor and record packet loss?

BTW: I've just updated some clients to TelliCast 2.14.4 and others to add the receive_buffer parameter. I'd be interested to know what value is optimum.

Cheers,
David
--
SatSignal Software - Quality software written to your requirements
Web: http://www.satsignal.eu
Email: david-taylor@...
Twitter: @gm8arv


Re: Tellicast client version 2.14.4 for Linux

Hugo
 

Hi David,

If you use 'minimal' hardware ( Pentium, 486 ) than Linux is the only solution. You can't run Windows 10 on a 486 PC ...
I have only one receiving PC ( a Pentium from several years ago ) were I run BS, HVS-1 and HVS-2 without any problems.
Why do you use four PC's to receive Eumetcast  ? Redundency ?

Kind regards,

Hugo


Re: Tellicast client version 2.14.4 for Linux

David J Taylor GM8ARV 🏴󠁧󠁢󠁳󠁣󠁴󠁿 🇪🇺
 

Ernst,
[]
It was the first time I installed TC on Windows and the installation was going very smoothly ... Of course running TC on Windows in 'production' is not an option ....
[]
Kind regards,
Hugo
==============================

Running seven instances of TelliCast on Windows-10 in "production" on four PCs isn't an issue. Three BS, two HVS-1 and two HVS-2. The lack of a good signal is much more of a problem here!

Cheers,
David
--
SatSignal Software - Quality software written to your requirements
Web: http://www.satsignal.eu
Email: david-taylor@...
Twitter: @gm8arv


Re: Tellicast client version 2.14.4 for Linux

Hugo
 

Ernst,

Our mails crossed.
In my first attempts to install the TC client I used the installation script, but it didn't work. I saw the errors in the startup of my system ( dmesg ) and then I remembered your HOWTO and changed the 20-etoken file.
I should have going over all the possible errors in the Troubleshooting guide a bit sooner ...
Anyway, it is always an adventure installing TC on Linux.

Hugo


Re: Tellicast client version 2.14.4 for Linux

Hugo
 

Ernst,

Apparently a lot more effort is going in the development and maintenance of the Windows version of Tellicast than for the Linux version.
It was the first time I installed TC on Windows and the installation was going very smoothly ... Of course running TC on Windows in 'production' is not an option ....
I didn't use the tellicast installation script this time, ( i did everything manual) just to be sure nothing was going wrong.

One possibility to avoid all the different flavors of Linux is that Eumetsat roles his own Linux distribution with TC already installed. Something like this : https://devuan.org/os/partners/devuan-distros .
Ernst, I see some opportunities here for you ....:)

One of the advantages of open source is of course that Linux would have a 64 bit TC client version years ago, and that there would be a constant development on the software.
Now, TC for Linux it is just an afterthought in a Windows world.

Kind regards,

Hugo





Re: Tellicast client version 2.14.4 for Linux

Ernst Lobsiger
 

Hugo,

I compared my aksrte installation deb with the
latest v. p6 downloaded from EUMETSAT ftp site.
They are identical and the link you had to force
is actually generated though as a "link chain":

aksifdh.so-> aksifdh.so.1-> aksifdh.so.1.3-15.84

So the only problem EUMETSAT can be blamed for is
the content of /etc/udev/rules.d/20-etoken.rules:

ACTION=="add",    SUBSYSTEM=="usb_device", SYSFS{idVendor}=="0529", SYSFS{idProduct}=="0514", RUN="/etc/hotplug/usb/etoken" 
ACTION=="remove", SUBSYSTEM=="usb_device", SYSFS{idVendor}=="0529", SYSFS{idProduct}=="0514", RUN="/etc/hotplug/usb/etoken" 
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" 

Since Debian 7 I always had to change that to:

ACTION=="add",    SUBSYSTEM=="usb", ATTR{idVendor}=="0529", ATTR{idProduct}=="0514", RUN="/etc/hotplug/usb/etoken"
ACTION=="remove", SUBSYSTEM=="usb", ATTR{idVendor}=="0529", ATTR{idProduct}=="0514", RUN="/etc/hotplug/usb/etoken"

That's why I asked August 2nd: "Have you edited the
etoken rules?" (explained in attached STRETCH64.txt).

Maybe you should send a ticket to OPS and ask
them to change the rules or at least to clarify
the C9 problem in the trouble shooting guide.

Cheers,
Ernst


Re: Tellicast client version 2.14.4 for Linux

Ernst Lobsiger
 

Hugo,

Nice to hear you got it working. I just hope the Devuan people
have the strength to maintain this distro. Most distros have systemd
now which is something like "microsofting" the UNIX desktop. IMHO
this is unacceptable for a CLI based EUMETCast receiver. Why should
I want a monster that tries to do everything from time keeping, network
management to binary log files? My future TC receivers are all Devuan.

The missing link is something I told EUMETSAT many years ago.
This was then described as C11 in the trouble shooting guide.

The really bad thing: In the installation files I use C11 was fixed
by EUMETSAT. That's what I remarked in my HOWTO. It seems
the very latest version from the ftp site has this problem again :-(.

The udev rule lines have changed several times. There is a C9
entry in the trouble shooting guide that should be updated too.
I think I figured out the latest working version some times back.

Cheers,
Ernst



Re: Tellicast client version 2.14.4 for Linux

Hugo
 

Ernst,

I found the reason why it didn't work... :}
One of the reasons was indeed the entry in /etc/udev/rules.d//20-etoken like you explained in your STRETCH.TXT.
But also I had to create the following symbolic link :
ln -sf /usr/local/lib/aksifdh.so.1.3-15.84 /usr/local/lib/aksifdh.so
In my previous (working) installations I never had to do that.

There isn't anything in the logging file where you can see that the etokend service was not working.
The errors for the entries in /etc/udev/rules.d//20-etoken are displayed at startup.
This time I took notes for the future !

Well, the whole experience was very educational , but sometimes frustrating !

I now have a working Eumetcast receiving station running on Devuan ASCII (amd64) ... hopefully for a few years...


And Ernst, thanks again for the help !

Kind regards,

Hugo



Austria weather....

David J Taylor GM8ARV 🏴󠁧󠁢󠁳󠁣󠁴󠁿 🇪🇺
 

Looks like storms over Aflenz causing signal level drops. Possibly a switch to the Vienna uplink instead.

Cheers,
David
--
SatSignal Software - Quality software written to your requirements
Web: http://www.satsignal.eu
Email: david-taylor@...
Twitter: @gm8arv


Re: Tellicast client version 2.14.4 for Linux

Hugo
 

Hi Ernst,

Yes I used the p6 version freshly downloaded from the Eumetsat ftp site ....
Tomorrow I will do a new install of Devuan 2.0 and do it all over again.
It must work ...


grts,

Hugo