Date   

Re: Realtime co-lin outage map for your location.

geojohnt@...
 

David,

Thanks for your thoughts.

Right, my dish is supposed to be a 1 m dish.
It's maximum dimensions are 107 cm tall and 96.5 cm wide.
The reflective surface slightly less of course.

Which means the beamwidth is wider in the horizontal plane - slightly than the vertical?

The LNB is adjusted for max 'best focus' - SN - which is right up one end on the LNB throat 
in the LNB holder.
The skew and dish alignment - 'best SN alignment.'

Today was my 'day before max outage.'
It looked from the Satellite-calculation map that today was/or around, your max outage day.

Iv'e had some thoughts, is WXtrack and satellite-calculations predicting for a prime focus dish 
or an offset dish?
And, are they both predicting for total degradation in SN or just the 3 dB level?

Satellite-calculation displays -1 dB to  -6 dB contours in the outage cone.
I watched the progress of the contours across my location and they pretty well matched my SN variation.
And, I think I'm right in saying that their 'outage time predictions' which were about the same as WXtrack 
were for the 3 dB level degradation looking at the passing cone levels.

My 'drop from and rise to original signal level' (13.2 dB to 13.2 dB) was around 18 minutes.
And about 17 yesterday. 
My peak outage SN was 7.0 dB.

Ah, just noticed on WXtrack - Solar Outage, First nulls beamwidth 3.73 degrees. ???
My drop in SN starts around the time the sun is 2 degrees from 10A and ends around the sun being 2 degrees past.

WXtrack and satellite-calculation almost agree on prediction times (today -0.28 degrees Closest):
Begin 11:21 Peak 11:28:11 End 11:34 - a period of 13 minutes.
My total outage period was 18 minutes.


I tried reducing the dish size a bit in WXtrack which changed the beamwidth but didn't alter the Begin 
Peak, End, times much.

So, the question seems to be, are the predictions based on the 3 dB outage level and not the total outage?

Regards,
John.

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

 
 John,

If the outage is lasting longer than the prediction then perhaps the figures
you are entering into the calculation are not appropriate?  Dish size - for
example - where a dish bought as "1m" may have an active area somewhat less,
particularly if the 1m is actually the maximum axis of the ellipse rather
than the "average" dimension of the two axes.  There's also an efficiency
figure - your dish flatness and illumination by the LNB won't be 100%.
Again, what you mean by "co-lin begins" - is it the precise angular
separation, or a certain number of dB?  The dB figure will depend on the
exact shape of your dish's response, not to mention any diffraction from
nearby trees!

Just some thoughts....

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

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

-----Original Message-----
From: David J Taylor via Groups.Io <david-taylor@...>
To: MSG-1 <MSG-1@groups.io>
Sent: Fri, 28 Feb 2020 7:39
Subject: Re: [MSG-1] Realtime co-lin outage map for your location.

David,

Yes of course, and I have always used this WXtrack function.

But, even with a 1 m dish I find that the co-lin begins before the 'begin' 
in the list noted and lasts
longer than the end prediction.
Especially if I recall correctly, around the max Closest.

I subtract 4 then 4 minutes from the predicted Peak - and likewise add 4 
minutes plus 4 minutes to
the Peak - giving me 4 degree beamwidth.
My drop in CN being longer (starting earlier and ending later) than the 
prediction.

I had a tweak of my dish yesterday after co-lin just to check the dish was - 
as far as possible - 'aligned.'
It appeared so.

It seems at times that tweaking can be counter productive?

Regards,
John
=============================================


Gibertini OP150S Satellite Dish

diogenes1@...
 

Hello All,
I currently have this 1.5m dish mounted on a post in my garden (this is not a dish that you could mount on a house wall). After much trial & error over the last couple of years I have come to the conclusion that the dish would need to be mounted higher in order to clear the surrounding hills. For practical reasons I do not want to attempt this. Therefore I am offering it free* to any member who is willing to disassemble it and transport it to their location. You can see the dish in question at this website;
http://www.gibertini.it/index.php/en/antennas-uk/op-150-s 
Please take note of the dimensions of the dish for transport purposes.
* In return I would ask this person to take down two small dishes from the side of my bungalow, I have ladders for this purpose.
Regards, Peter, near Alston in Cumbria.


Re: Big jump of SNR T1 at 07:05 UTC

George Sz
 

It looked like this later on.


Re: Big jump of SNR T1 at 07:05 UTC

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

Hi All

This is about the biggest jump in SNR I'v seen so far ...
Almost +1.5dB here. Also visible on David's page.

Best regards
Ernst ====================================

unfortunately, that was only a recovery from an earlier drop! TP1 only, TP2 possibly had a slight drop. Snow at Vienna/Aflenz, I guess:

https://twitter.com/gm8arv/status/1233264268658794496/photo/1

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


Big jump of SNR T1 at 07:05 UTC

Ernst Lobsiger
 

Hi All

This is about the biggest jump in SNR I'v seen so far ...
Almost +1.5dB here. Also visible on David's page.

Best regards
Ernst


Re: Realtime co-lin outage map for your location.

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

David,

Yes of course, and I have always used this WXtrack function.

But, even with a 1 m dish I find that the co-lin begins before the 'begin' in the list noted and lasts
longer than the end prediction.
Especially if I recall correctly, around the max Closest.

I subtract 4 then 4 minutes from the predicted Peak - and likewise add 4 minutes plus 4 minutes to
the Peak - giving me 4 degree beamwidth.
My drop in CN being longer (starting earlier and ending later) than the prediction.

I had a tweak of my dish yesterday after co-lin just to check the dish was - as far as possible - 'aligned.'
It appeared so.

It seems at times that tweaking can be counter productive?

Regards,
John
=============================================

John,

If the outage is lasting longer than the prediction then perhaps the figures you are entering into the calculation are not appropriate? Dish size - for example - where a dish bought as "1m" may have an active area somewhat less, particularly if the 1m is actually the maximum axis of the ellipse rather than the "average" dimension of the two axes. There's also an efficiency figure - your dish flatness and illumination by the LNB won't be 100%. Again, what you mean by "co-lin begins" - is it the precise angular separation, or a certain number of dB? The dB figure will depend on the exact shape of your dish's response, not to mention any diffraction from nearby trees!

Just some thoughts....

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


Re: Realtime co-lin outage map for your location.

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

David,

Yes of course, and I have always used this WXtrack function.

But, even with a 1 m dish I find that the co-lin begins before the 'begin' in the list noted and lasts
longer than the end prediction.
Especially if I recall correctly, around the max Closest.

I subtract 4 then 4 minutes from the predicted Peak - and likewise add 4 minutes plus 4 minutes to
the Peak - giving me 4 degree beamwidth.
My drop in CN being longer (starting earlier and ending later) than the prediction.

I had a tweak of my dish yesterday after co-lin just to check the dish was - as far as possible - 'aligned.'
It appeared so.

It seems at times that tweaking can be counter productive?

Regards,
John
==============================

Yes, John, I find it useful to compare the solar outage to the prediction as an estimate of the errors in azimuth and elevation I likely have. I wrote my Solar Outage SNR program to automatically plot the data for later analysis.

https://www.satsignal.eu/software/beta.htm

Attached is one I made earlier....

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


Re: Realtime co-lin outage map for your location.

geojohnt@...
 

David,

Yes of course, and I have always used this WXtrack function.

But, even with a 1 m dish I find that the co-lin begins before the 'begin' in the list noted and lasts 
longer than the end prediction.
Especially if I recall correctly, around the max Closest.

I subtract 4 then 4 minutes from the predicted Peak - and likewise add 4 minutes plus 4 minutes to 
the Peak - giving me 4 degree beamwidth.
My drop in CN being longer (starting earlier and ending later) than the prediction.

I had a tweak of my dish yesterday after co-lin just to check the dish was - as far as possible - 'aligned.'
It appeared so.

It seems at times that tweaking can be counter productive?  

Regards,
John

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

-----Original Message-----
From: David J Taylor via Groups.Io <david-taylor@...>
To: msg-1 <msg-1@groups.io>
Sent: Wed, 26 Feb 2020 14:08
Subject: Re: [MSG-1] Realtime co-lin outage map for your location.

Nice one, John!

For those with registered WXtrack, you can get the results in a tabular
format.

  https://www.satsignal.eu/software/wxtrack.htm

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





Re: Realtime co-lin outage map for your location.

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

Nice one, John!

For those with registered WXtrack, you can get the results in a tabular format.

https://www.satsignal.eu/software/wxtrack.htm

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


Realtime co-lin outage map for your location.

geojohnt@...
 

All,

My spring outage period has started and I've found this realtime map of the 'outage area.'
It updates on a timescale that you select and shows the outage area crossing 'your' location.
In our case parts of Europe.

www.satellite-calculations.com

https://www.satellite-calculations.com/Satellite/sunoutagestatusconfigurator.php

Quite interesting?

Regards,
John Tellick.





Re: dish and signal level on a TBS 6903 for 10e and iptool

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

hi all just lined my 90cm dish up with my sat meter to 10 e and got the optimum signal(meter shows video of one of the channels on 10e so i know its the right sat),when i connect it to my pci card it is showing full signal but no quality,when i unplug the aerial it shows roughly half signal disconnected ive got a 20 m run of cable.Two questions is the dish big enough here in yorkshire and is it normal to show half strength when the aerial is unplugged ,any advice appreciated,cheers
==========================

iwolsey,

Welcome to the group!

90 cm should be enough for the Basic Service, but I'm unsure about the HVS-1 and HVS-2. Here's a guide to what some others are using:

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

I've seen signal strength readings with no connection before, so I wouldn't worry about that.

The signal from the wide-beam EUEMTCast transponders is much weaker than that from narrow-beam "Satellite TV" such as Astra, so it's important to maximise it by very careful adjustment of azimuth, elevation, skew (rotate the LNB) and focus (move the LNB nearer to or further from the dish, often very limited).

Ask again here if you need further help.

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


posting

ian
 

hi just a quick question,when i post a new topic is there a delay before it is posted thanks

[Members' first posts are moderated.  David, owner]


dish and signal level on a TBS 6903 for 10e and iptool

ian
 

hi all just lined my 90cm dish up with my sat meter to 10 e and got the optimum signal(meter shows video of one of the channels on 10e so i know its the right sat),when i connect it to my pci card it is showing full signal but no quality,when i unplug the aerial it shows roughly half signal disconnected ive got a 20 m run of cable.Two questions is the dish big enough here in yorkshire and is it normal to show half strength when the aerial is unplugged ,any advice appreciated,cheers


Re: experiences and lessons learned with a fresh Eumetcast install for WIndows and Linux

Ernst Lobsiger
 

Markus,

Your NAS GNU/Linux receiver seems to work perfectly now. I attach what my 11 years
old Fujitsu/Siemens CoreDuo receiver io did when I tested the TBS-6925 two days ago.

I also attach the patched driver with updated installation instructions once more.
If anybody is encouraged by this thread to give GNU/Linux a try there is a second
hand TBS-5925 for sale on www.eBay.de currently. A couple of people use it 24/7.

Let's close that thread now. I want to go back building my third Beowulf Cluster.
If your curiosity for PyTroll/SatPy shows results MSG-1 already started a thread.


Best regards,
Ernst


Re: experiences and lessons learned with a fresh Eumetcast install for WIndows and Linux

Markus Kempf
 

# service tellicast-client status|grep Memory:
Memory: 2.3G
# grep VmPeak /proc/4679/status
VmPeak: 185332 kB

the peak allocated virtual memory value increases, the allocated memory for the service fluctuates between 2 and 5 GB.

Received Packets on Data Channel: 31654570
Missed Packets before FEC: 3
FEC Recovered Packets: 3
Received Bytes on Data Channel: 36929653635

I see no reason not to upgrade to the 5.4 kernel. It's the new LTS kernel in the 5 series.

Markus


Re: experiences and lessons learned with a fresh Eumetcast install for WIndows and Linux

Markus Kempf
 

Ernst,
I can observe an increase in memory usage. Right now the service allocates 5.1GB of memory:
root@openmediavault:~# service tellicast-client status|grep Memory:
Memory: 5.1G
the main running tc
root@openmediavault:~# pmap 4679
4679: /usr/local/bin/tc-cast-client -c /etc/cast-client_bas.ini
0000000000400000 2760K r-x-- tc-cast-client
00000000007b1000 3036K rw--- tc-cast-client
0000000000aa8000 492K rw--- [ anon ]
0000000001a3f000 83204K rw--- [ anon ]
00007f661828e000 664K rw--- [ anon ]
00007f6618334000 12K r---- libnss_files-2.28.so
00007f6618337000 28K r-x-- libnss_files-2.28.so
00007f661833e000 8K r---- libnss_files-2.28.so
00007f6618340000 4K ----- libnss_files-2.28.so
00007f6618341000 4K r---- libnss_files-2.28.so
00007f6618342000 4K rw--- libnss_files-2.28.so
00007f6618343000 36K rw--- [ anon ]
00007f661834c000 136K r---- libc-2.28.so
00007f661836e000 1312K r-x-- libc-2.28.so
00007f66184b6000 304K r---- libc-2.28.so
00007f6618502000 4K ----- libc-2.28.so
00007f6618503000 16K r---- libc-2.28.so
00007f6618507000 8K rw--- libc-2.28.so
00007f6618509000 16K rw--- [ anon ]
00007f661850d000 52K r---- libm-2.28.so
00007f661851a000 636K r-x-- libm-2.28.so
00007f66185b9000 852K r---- libm-2.28.so
00007f661868e000 4K r---- libm-2.28.so
00007f661868f000 4K rw--- libm-2.28.so
00007f6618690000 4K r---- libdl-2.28.so
00007f6618691000 4K r-x-- libdl-2.28.so
00007f6618692000 4K r---- libdl-2.28.so
00007f6618693000 4K r---- libdl-2.28.so
00007f6618694000 4K rw--- libdl-2.28.so
00007f6618695000 8K rw--- [ anon ]
00007f6618699000 72K rw--- [ anon ]
00007f66186ab000 4K r---- ld-2.28.so
00007f66186ac000 120K r-x-- ld-2.28.so
00007f66186ca000 32K r---- ld-2.28.so
00007f66186d2000 4K r---- ld-2.28.so
00007f66186d3000 4K rw--- ld-2.28.so
00007f66186d4000 4K rw--- [ anon ]
00007fff5f5bb000 232K rw--- [ stack ]
00007fff5f5fc000 12K r---- [ anon ]
00007fff5f5ff000 4K r-x-- [ anon ]
total 94112K
root@openmediavault:~# grep VmPeak /proc/4679/status
VmPeak: 94168 kB

It slowly creeps up, will check again in a few hours after maybe some garbage colection has taken place.

Markus


Re: experiences and lessons learned with a fresh Eumetcast install for WIndows and Linux

Ernst Lobsiger
 

Markus,

Here I have to change the driver stv090x.c in ./media as described. The point probably is
that this only works if the the patched driver copy is newer than the replaced one. This
is because make relies on time stamps. So if you downloaded the media tree from TBS again
your files could have been newer than my patched copy. Just checked this here again:

My downloaded TBS tree dates from Feb 12 10:47
This tree has been compiled and installed before (including my patches too)

I make sure in ./media_build I have again the stv090x.c from Feb 12 10:47
My patched stv090x.c driver copied to ./media dates from Feb 14 19:26
I go to ./media_build and do a make that compiles just one module stv090x.o
Now in my ./media_build I have a patched todays copy of stv090x.c Feb 16 13:45

Every thing works as discribed in the README_FIRST.txt if the patched driver is newer
than the files in the TBS tree. I guess you downloaded the GIT tree again and it was
newer than my patched driver? You can open the patched source with mc and save it again
to get the newest file on the planet. Maybe I should explain that in my README_FIRST.txt.

Nice to hear your GNU/Linux receiver is now up and running fine. I have a problem here
with my Debian 10 and latest 64bit tellicast client. Some 10 minutes after I start tellicast
there is a very small but slowly increasing use of swap space. Is there a memory leak?
How does your NAS with a far newer kernel handle that? What does top (memory) show?


Best regards,
Ernst

P.S. SatPy/Pytroll is powerful and extreme fun. But this is not an overnight thing either ...


Re: experiences and lessons learned with a fresh Eumetcast install for WIndows and Linux

Markus Kempf
 

Ernst,

total success. For unknown reasons, my CN dropped to 10,0 - 10,2 since about 4 UTC and I had the errors again. Compiled and copied your versions, rebooted, run setmc and everything is perfect again.
One remark, copying the file stv090x.c to the ./media/... folder did not work, I had to copy it to ./media_build/v4l and ./media_build/linux/drivers/... to get it compiled and installed.

Btw. I have changed my BIOS settings back to SpeedStep enabled and C1,C6 and C5e enabled. The linux cpu governor runs in powersave mode. No packet losses even with all modcods if the CN is high enough (~>10,5).

Eumetcastview also runs on the NAS now and happily creates pictures. Out of curiosity, I will try SatPy/Pytroll now.

Markus


Re: experiences and lessons learned with a fresh Eumetcast install for WIndows and Linux

Ernst Lobsiger
 

Markus,

Let's take the shortcut. Here is the Igor M. Liplianin, CrazyCat enhanzed szap-s2 version you better use.

All you have to do is add in channel.conf behind   :hS1   more stuff: It should then read    :hS1P1O20
P1 sets the STREAM_ID = 1   and O20 gives you ROLLOFF = 20   (AFAIK EUMETSAT talks about 5)

Good luck
Ernst


Re: msg data manager defect ??

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

Hello,
May I just add that I use Windows 10 home, 64bits.
When trying to re-install the MSG D.M. I receive the message:
error 126, WaveletDLL.dll.
I must have lost this WaveletDLL somehow and I guess that this is the origin of my MSG data manager not functioning any longer.
Could you assist me please by telling me where I can find this DLL in order to put it into
the MSG file ?
Thanks in advance.
Regards,
Roland
================================

Roland,

That DLL is only included in the full install, so close all instances of the MSG Data Manager, install the full release (not the beta), and then install any beta updates you wish to run.

I echo Ian's remarks that if something worked yesterday but not today, as there have been no changes in the software or the data, it must be something you did on your computer. I can't help you with that!

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