Date   

R: [MSG-1] Signal strength recovery

Stefano Mina
 

Good evening. Also here in Italy, on TP1 the found snr is: 0.2-0.3 db of the
0.4 db missing initially

Greetings

Stefano Mina

-----Messaggio originale-----
Da: MSG-1@groups.io <MSG-1@groups.io> Per conto di David J Taylor via
Groups.Io
Inviato: martedì 9 ottobre 2018 14:53
A: MSG-1@groups.io
Oggetto: Re: [MSG-1] Signal strength recovery

From: Ian Deans via Groups.Io

No sign of an improvement here in Angus, although to be fair my drop was
only about 0.2/0.3 SNR. Will of course continue to monitor, as we need every
drop of signal we can get up here !!

Regards
Ian.
==========================

Thanks for the report, Ian. I hope that EUMETSAT will be monitoring the
group messages.

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


Re: Eumetcast on Debian 9 - was "TBS 6903 extra power cable"

nigel
 

Thanks Ernst,
I've now installed Samba on the receiving computer (Vento) and have tried to map a drive, on the Windows7 (Inwin) processing machine, to the folder on Vento where the received files are.
BUT, as the received folder and files on Vento, belong to root (reception is being run by root at the moment), Windows objects to giving access to them !
So, a basic question, if I may :- does Eumetcast reception have to be done by root or is there a way (short of regularly running a script to chown of all the received files) to have the files belong to a regular user ? I'm just wondering if there is an option, somewhere, to change the ownership of the received files, as they are received ?

Regards
Nigel

On 09/10/2018 15:03, Ernst Lobsiger wrote:

Nigel,

For the connection you need a Network File System:

For Linux to Linux I use NFS where the receiver has
the server and the processor PC attaches as client.

For GNU/Linux to Windows you will want to use CIFS
(SMB) where the receiver has the server (SAMBA) and
the processor PC connects to the receiver as client.
Nothing extra must be installed on the Windows side.

Best regards
Ernst

 



Re: Eumetcast on Debian 9 - was "TBS 6903 extra power cable"

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

Many thanks David - spot on !

Using port 8100 works a treat. I'm still trying to understand (and
remember!) what all the various files do

Thanks very much

Nigel
===================================

Excellent!

My Web site is often just my notebook. I sometimes Google a question, only to find my own Web site pointed to with the answer! I've put some simple commands up there - like finding a file, checking disk space, etc. etc. I do feel confident about adding SNMP, SAMBA to a system and customising NTP. For remote monitoring I still run MRTG on the Windows PCs, and get the data from the Linux systems over SNMP calls.

The thing I like least about Linux is the lack of compatibility between different versions, and the hell which upgrades can introduce - "Oh, you just recompile a, b, c ...." and find that they all use different versions of the tools or packages. At least with Windows my software which started on 32-bit XP still runs without issues on the latest Win-10, 32- or 64-bit. Backwards compatibility is a very welcome feature of Windows.

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


Re: Signal strength recovery

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

From: Ian Deans via Groups.Io

No sign of an improvement here in Angus, although to be fair my drop was
only about 0.2/0.3 SNR. Will of course continue to monitor, as we need
every drop of signal we can get up here !!

Regards
Ian.
==========================

Thanks for the report, Ian. I hope that EUMETSAT will be monitoring the group messages.

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


Re: BS/TP 1 H/V co-channel?

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

All,

Well, those who might have a spectrum analyser.

Flysat is still showing 11.263 Ghz V Tricolor (IPTV) Packages on 10 E (22-06-17), alongside EUMETCast on 11.263 Ghz H.

I was adjusting my skew yesterday after noon and feel pretty sure that the V channel is not fired up.
Can anyone confirm this please?

Thanks,
John Tellick.
=========================================

John,

I monitor this on a twice-daily basis using a TBS5925 and CrazyCat's excellent CrazyScan software. To the best on my knowledge, the cross-polarised signal on 11263 MHz has been on since 2018-08-31. This is independent of any modulation (data or TV) on that channel. It's there right now.

I've been playing with a few other DVB tools so I might be able to check what ID the V signal is sending if that's important, but I'm not very familiar with those tools so it might take a while!

Attached, this morning's plot.

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


Re: Eumetcast on Debian 9 - was "TBS 6903 extra power cable"

Ernst Lobsiger
 

Nigel,

For the connection you need a Network File System:

For Linux to Linux I use NFS where the receiver has
the server and the processor PC attaches as client.

For GNU/Linux to Windows you will want to use CIFS
(SMB) where the receiver has the server (SAMBA) and
the processor PC connects to the receiver as client.
Nothing extra must be installed on the Windows side.

Best regards
Ernst

 


Re: Eumetcast on Debian 9 - was "TBS 6903 extra power cable"

nigel
 

Thanks Ernst,
That was my problem - my /etc/cast-client_bas.ini has :-

[shell]
login=none
port=8100
graphic_port=8105
refresh=3

and using "http://localhost:8100"   now works well. I should have looked into that file more carefully!

Thanks for the other suggestions - I'll get to them very soon.

My next priority is to get the Windows 7 machine ("Inwin"), with David's programmes on, fetching the files from the Debian 9 reception machine ("Vento") and deleting them when processed. I guess that will be a matter of firewalls and permissions - all good stuff!

Regards
Nigel


On 09/10/2018 13:46, Ernst Lobsiger wrote:

Nigel,

Congratulations! And wellcome in the club of the lonely rangers
that use GNU/Linux for EUMETCast reception. As for your minor
problem: David already has given the answer. EUMETSAT has changed
the ports years back, though I still use 2517, 3517 and 4517
for my three clients. Receiving BAS + HVS-1 is childs play now:

Just go to /etc/tellicast-client.cfg and edit it for 2 instances.

And here comes the next trick that makes the 6903 driver shine.
If you want a single cable system that takes T1 + T2 it's easy
again. Edit a file /etc/modprobe.d/stv6120.conf with content:

options stv6120 rfsource=1

The meaning that you might want to write into the file as comment:

#  Parameter rfsource is loaded when booting (cannot be changed in /sys/module/...)
#  0  = you can attach two cables LNB0->adaper0 and LNB1->adapter1 (DEFAULT)
#  1  = connect the cable to LNB0 where you can use adapter0 + adapter1
#  2  = connect the cable to LNB1 where you can use adapter0 + adapter1

Of course 1 and 2 is only possible if T1 and T2 is in the same band and polarisation.
But this is the case for EUMETCast transponders T1 and T2.

Cheers,
Ernst



Re: Eumetcast on Debian 9 - was "TBS 6903 extra power cable"

Ernst Lobsiger
 

Nigel,

One thing I didn't mention: If you want BAS + HVS or even BAS + HVS-1 + HVS-2
you must also make minor changes to  K.-P.- Renner's  /etc/dvb-eumetcast.cfg.
This is for setting up additional multicast routes (see # ip mroute show) with
smcroute and also for tuning the second transponder if you take "the full monty".

When it comes to using David's software on Windows with a two PC system
where the receiver runs GNU/Linux you'll probably have to install SAMBA.
But for questions concerning this kind of setup Christian Peters is your man.

Cheers,
Ernst


Re: Eumetcast on Debian 9 - was "TBS 6903 extra power cable"

nigel
 

On 09/10/2018 13:02, David J Taylor via Groups.Io wrote:
Hi Ernst,
Many thanks for the links and info.
I've now got reception going and am receiving Basic Service with EUMETSAT Data Channels 2, 5 and 6 coming in well !!
Very satisfying !
However I have what I suspect is a simple problem that I can't find an answer to :-
I wanted to open the Tellicast shell, in a web browser (Chromium) on the receiving machine using "http://localhost:2517" but am getting the error :-
"localhost refused to connect"
I've checked /etc/hosts and it does have a line "127.0.0.1 localhost" in it.
I've also tried on a remote machine, prefixing the http command with the ip address of the Debian receiving machine, but am getting the same error.
When you have a moment, could you advise what I need to do, please?
Many thanks
Nigel
================================

Firewall?

Is 2517 still the correct default port with the new client?  My cast-client.ini has:

[shell]
login=none
port=8100
graphic_port=9100
refresh=2

David
Many thanks David - spot on !

Using port 8100 works a treat. I'm still trying to understand (and remember!) what all the various files do

Thanks very much

Nigel


Re: Signal strength recovery

Ian Deans
 

On 09/10/2018 11:06, David J Taylor via Groups.Io wrote:
Good to see a recovery in the last hour. Perhaps the accumulation of
alerts and graphs sent to Eumetsat were a help,
Cheers,
James
==================================
Thanks!  Looks good!
 https://www.satsignal.eu/mrtg/performance_eumetcast-europe_link_margin.php
Cheers,
David
=======================================================

No sign of an improvement here in Angus, although to be fair my drop was only about 0.2/0.3 SNR. Will of course continue to monitor, as we need every drop of signal we can get up here !!

Regards
Ian.


Re: Signal strength recovery

geojohnt@...
 

Douglas,

Not to rub salt into the wound, but it is the most wonderful warm day with 'gin clear skies' down here in London.
The sun is still quite hot - time for a bit of 'late' sunbathing with lunch.

Regards,
John

In a message dated 09/10/2018 11:47:55 GMT Standard Time, dsdeans@... writes:

Might be a while before I know if the changes have helped central Scotland !
My radar has looked like this for close to 3 days.
Dunblane is the red dot near the middle of the image.
It updates every 5 minutes just to depress me and zooms in to near
street level.


Re: Signal strength recovery

Douglas Deans
 

On 09/10/2018 10:59, James Brown wrote:
Good to see a recovery in the last hour. Perhaps the accumulation of alerts and graphs sent to Eumetsat were a help,
Cheers,
James
======================================================================

Might be a while before I know if the changes have helped central Scotland !
My radar has looked like this for close to 3 days.
Dunblane is the red dot near the middle of the image.
It updates every 5 minutes just to depress me and zooms in to near street level.

Regards,
Douglas.


Re: Signal strength recovery

Douglas Deans
 

On 09/10/2018 10:59, James Brown wrote:
Good to see a recovery in the last hour. Perhaps the accumulation of alerts and graphs sent to Eumetsat were a help,
Cheers,
James
==========================================================================

Might be a while before I know if the changes have helped central Scotland !
My radar has looked like this for close to 3 days.
Dunblane is the red dot near the middle of the image.
It updates every 5 minutes just to depress me and zooms in to near street level.

Regards,
Douglas.


Re: Eumetcast on Debian 9 - was "TBS 6903 extra power cable"

Ernst Lobsiger
 

Nigel,

Congratulations! And wellcome in the club of the lonely rangers
that use GNU/Linux for EUMETCast reception. As for your minor
problem: David already has given the answer. EUMETSAT has changed
the ports years back, though I still use 2517, 3517 and 4517
for my three clients. Receiving BAS + HVS-1 is childs play now:

Just go to /etc/tellicast-client.cfg and edit it for 2 instances.

And here comes the next trick that makes the 6903 driver shine.
If you want a single cable system that takes T1 + T2 it's easy
again. Edit a file /etc/modprobe.d/stv6120.conf with content:

options stv6120 rfsource=1

The meaning that you might want to write into the file as comment:

#  Parameter rfsource is loaded when booting (cannot be changed in /sys/module/...)
#  0  = you can attach two cables LNB0->adaper0 and LNB1->adapter1 (DEFAULT)
#  1  = connect the cable to LNB0 where you can use adapter0 + adapter1
#  2  = connect the cable to LNB1 where you can use adapter0 + adapter1

Of course 1 and 2 is only possible if T1 and T2 is in the same band and polarisation.
But this is the case for EUMETCast transponders T1 and T2.

Cheers,
Ernst


Re: Signal strength recovery

geojohnt@...
 

James,

YES!!!

Earlier this morning I sent Ops another plot recently sent to 'us' from Alan Gibbs which shows the drop very well.

Gosh, with a bit of luck I'll be back to my diurnal peak BS SNR of February 2018 of around 14.3/4 dB this evening - hopefully.

I was beginning to doubt my sanity whilst 'shoving the dish around' yesterday afternoon, unable to improve my SNR.

My outage season has just started and I'm photographing the fir trees shadow daily as I reach maximum co-linearity.

Regards,
John

++++++++++++++++++++

In a message dated 09/10/2018 11:06:28 GMT Standard Time, gm8arv@... writes:

Good to see a recovery in the last hour. Perhaps the accumulation of
alerts and graphs sent to Eumetsat were a help,
Cheers,
James
==================================

Thanks! Looks good!

https://www.satsignal.eu/mrtg/performance_eumetcast-europe_link_margin.php

Cheers,
David


BS/TP 1 H/V co-channel?

geojohnt@...
 

All,

Well, those who might have a spectrum analyser.

Flysat is still showing 11.263 Ghz V Tricolor (IPTV) Packages on 10 E (22-06-17), alongside EUMETCast on 11.263 Ghz H.

I was adjusting my skew yesterday after noon and feel pretty sure that the V channel is not fired up.
Can anyone confirm this please?

Thanks,
John Tellick.


Re: Signal strength recovery

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

Good to see a recovery in the last hour. Perhaps the accumulation of
alerts and graphs sent to Eumetsat were a help,
Cheers,
James
==================================

Thanks! Looks good!

https://www.satsignal.eu/mrtg/performance_eumetcast-europe_link_margin.php

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


Re: Eumetcast on Debian 9 - was "TBS 6903 extra power cable"

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

Hi Ernst,
Many thanks for the links and info.
I've now got reception going and am receiving Basic Service with EUMETSAT Data Channels 2, 5 and 6 coming in well !!
Very satisfying !
However I have what I suspect is a simple problem that I can't find an answer to :-
I wanted to open the Tellicast shell, in a web browser (Chromium) on the receiving machine using "http://localhost:2517" but am getting the error :-
"localhost refused to connect"
I've checked /etc/hosts and it does have a line "127.0.0.1 localhost" in it.
I've also tried on a remote machine, prefixing the http command with the ip address of the Debian receiving machine, but am getting the same error.
When you have a moment, could you advise what I need to do, please?
Many thanks
Nigel
================================

Firewall?

Is 2517 still the correct default port with the new client? My cast-client.ini has:

[shell]
login=none
port=8100
graphic_port=9100
refresh=2

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


Re: Signal strength recovery

James Brown
 

Good to see a recovery in the last hour. Perhaps the accumulation of alerts and graphs sent to Eumetsat were a help,
Cheers,
James


Re: Eumetcast on Debian 9 - was "TBS 6903 extra power cable"

nigel
 

Hi Ernst,
Many thanks for the links and info.
I've now got reception going and am receiving Basic Service with EUMETSAT Data Channels 2, 5 and 6 coming in well !!
Very satisfying !
However I have what I suspect is a simple problem that I can't find an answer to :-
I wanted to open the Tellicast shell, in a web browser (Chromium) on the receiving machine using "http://localhost:2517" but am getting the error :-
"localhost refused to connect"
I've checked /etc/hosts and it does have a line "127.0.0.1    localhost" in it.
I've also tried on a remote machine, prefixing the http command with the ip address of the Debian receiving machine, but am getting the same error.
When you have a moment, could you advise what I need to do, please?
Many thanks
Nigel


On 08/10/2018 20:02, Ernst Lobsiger wrote:

Nigel,

The latest TelliCast Client is 2.14.4-4 distributed
twice per day in Info-Channel-1. There seems to be
no *.deb package yet but there is a *.tgz. Not sure
you still have to ask OPS to be put on the list to
receive that. It's even sent to the generic eumetcast
user unencrypted (without a need for an EKU).

You should also find the latest CD version here:

ftp://ftp.eumetsat.int/pub/OPS/out/user/EUMETCast_Support/

Be aware that I use my own version of dvb-eumetcast that
does a multi transponder setup with 3 dummy interfaces.
I had that long before EUMETSAT (K.-P. Renner) came up
with their own multi transponder solution some month ago.
The EUMETSAT setup uses a single dummy0 interface where
all clients (up to 3 = BAS, HVS-1, HVS-2) attach. They
also come with a completly new configuration file
for dvb-eumetcast. I recommend to go with what you get
from EUMETSAT now. In any case 4GB RAM will be hardly
enough to setup a system that uses a RAM Disk for 3
clients. But that is fine tuning and comes later ...

You will also find a compiled version of szap-s2 distributed
by EUMETSAT. So forget what I wrote about a CrazyCat
Version and the soft links I make in my setup ...

Nice to hear that you are almost there. Keep going.

Cheers,
Ernst