Re: TBS IP replacement
Ernst Lobsiger
On Tue, Dec 1, 2020 at 06:58 AM, Giftmacher wrote:
Great, thank you, I'll give it a try.Giftmacher, if you havn't found BDADataEx yet, look here: https://groups.io/g/MSG-1/message/29750 Ernst
|
|
Re: TBS IP replacement
Giftmacher
Great, thank you, I'll give it a try.
|
|
Re: TBS IP replacement
Ernst Lobsiger
Giftmacher
More or less everybody under Windows uses CrazyCat's BdaDataEx. I'm under GNU/Linux. No idea where you get the latest version. Search this list. Ernst
|
|
TBS IP replacement
Giftmacher
Hi all, is there any better IP tool than TBS IP? Both versions I tried crashes to desktop after few hours of use.
|
|
Re: TBS6903X and TBS6909X ready for EUMETCast under GNU/Linux
Ernst Lobsiger
Dear All
I am pleased to report 30 days performance figures of my GNU/Linux receiver Kallisto. It's a Fujitsu Celsius Xeon with a TBS-6909X receiving all 3 services using a RAM disk. We had a rather dry November and Kallisto has not lost a single packet. I cannot remember to have had such figures ever since we changed from DVB-S to DVB-S2 in 2014. Cheers, Ernst P.S. Please compare: http://www.satsignal.eu/mrtg/performance_eumetcast-europe_losses.php?period=month
|
|
Re: Help in the beginning
Ernst Lobsiger
On Sun, Nov 29, 2020 at 04:12 AM, Giftmacher wrote:
Today I'm using only BAS, but again missing parts errors appeared. I started to suspect the coaxialGiftmacher It's not enough to use only BAS by starting just a BAS client. You have to set a MODCOD filter to prevent HVS-1 from even reaching your PC. Missing keys are often due to an EKU problem. Put the receiver and EKU in USB2 sockets. Maybe try different USB2 sockets (rear and front). Regards Ernst
|
|
Re: Help in the beginning
On 29/11/2020 12:12, Giftmacher via groups.io wrote:
Today I'm using only BAS, but again missing parts errors appeared. I started to suspect the coaxialThe LNB contains a down-converter from the 11 GHz signal to a 1.5 GHz (approx) signal, so cable intended for "satellite TV" will be fine. David -- SatSignal Software - Quality software for you Web: https://www.satsignal.eu Email: david-taylor@blueyonder.co.uk Twitter: @gm8arv
|
|
Re: FY-3D.
Graham Woolf
Hi Ernst
Thanks for the help - Ill try that Regards Graham
|
|
Re: FY-3D.
Ernst Lobsiger
On Sun, Nov 29, 2020 at 08:52 AM, Graham Woolf wrote:
Thanks for that - its these things that trip me up and knowing how to fix themGraham Maybe a somewhat more advanced Python code like try: layers, height, width = new_scn[composite].shape except: height, width = new_scn[composite].shape would cover both multi channel composites and single channel "composites". That's something to be tested for the HOWTO 2.0 somewhere in the future ... Cheers, Ernst
|
|
Re: FY-3D.
Ernst Lobsiger
On Sun, Nov 29, 2020 at 08:52 AM, Graham Woolf wrote:
Thanks for that - its these things that trip me up and knowing how to fix themGraham Maybe a code like try: layers, height, width = new_scn[composite].shape except: height, width = new_scn[composite].shape
|
|
Re: FY-3D.
Graham Woolf
Hi Ernst
Thanks for that - its these things that trip me up and knowing how to fix them I wouldn't have got the str bit either but I think I have a working script Douglas Thanks - it would be great to see your script too Regards Graham
|
|
Re: FY-3D.
Ernst Lobsiger
Graham
If you use one of my latest scripts with automatic annotation and logos on the left side of the image you might run into an additional problem with 1 channel only. There is a script line "layers, height, width = new_scn[composite].shape" (credits Christian Peters) where I only use the "height" to automagically scale the annotation and logos. In case of a single channel there is no "layers" and this must read "height, width = new_scn[composite].shape". But Python will tell you anyway ... Good luck Ernst
|
|
Re: FY-3D.
Douglas Deans
On 29/11/2020 12:47, Graham Woolf wrote:
Hi Ernst============================================================================= Graham I have a script that gives me this image. I will post it direct later when I get time but you will have to adjust for your own directories/files etc. Regards, Douglas.
|
|
Re: FY-3D.
Ernst Lobsiger
On Sun, Nov 29, 2020 at 04:47 AM, Graham Woolf wrote:
Hi ErnstGraham Metop uses the 'avhrr_l1b_eps' reader. Under ..satpy/etc/readers/avhrr_l1b_eps.yaml you see the datasets (channels) you can expect. You can either try by name or by center wavelength. composite = '4' or composite = 10.8 should work. The later will fail when assembling the final image file name (because it's not of type string). In this case change the file naming to ...+str(composite)+ .... Here are two examples from Metop-B. It's from yesterday, There is no UK data from today yet. Best regards Ernst
|
|
Re: FY-3D.
Graham Woolf
Hi Ernst
I need a bit of help please if you wouldnt mind I have looked through all the reader and composite files and the satpy documentation but I cant find out what I want to do I want to process just a single METOP channel whether it be visual or infra-red in its raw format so no composites I have tried this composite = '4' to process channel 4 data but it doesnt seem to work What do I need to do do to get a single channel Regards Graham
|
|
Re: Help in the beginning
Giftmacher
Today I'm using only BAS, but again missing parts errors appeared. I started to suspect the coaxial
cable, which is Televes T100, which seems to be intended for 2-3 GHz.
|
|
Re: Help in the beginning
On 29/11/2020 11:13, Giftmacher via groups.io wrote:
Ok, since I have no other coaxial cable, I have tried the RAMdisk according to this articleYour first step should be to disable the HVS-1, and get the BAS working properly first. Any errors in the HVS can affect the BAS. The RAMdisk we now tend to use in a different way. David -- SatSignal Software - Quality software for you Web: https://www.satsignal.eu Email: david-taylor@blueyonder.co.uk Twitter: @gm8arv
|
|
Re: Help in the beginning
On 29/11/2020 11:13, Giftmacher via groups.io wrote:
Ok, since I have no other coaxial cable, I have tried the RAMdisk according to this articleWeak signal or other errors. Could be a wobbly dish. David -- SatSignal Software - Quality software for you Web: https://www.satsignal.eu Email: david-taylor@blueyonder.co.uk Twitter: @gm8arv
|
|
Re: Help in the beginning
Giftmacher
Ok, since I have no other coaxial cable, I have tried the RAMdisk according to this article
https://www.satsignal.eu/wxsat/atovs/RAMdisk.pdf Now I see messages like this: ERR:2020-11-29 11:10:40.806:Could not join channel "EPS-10": Missing key 58020.
|
|
Re: Help in the beginning
On 29/11/2020 09:02, Giftmacher via groups.io wrote:
Maybe the repeater USB cable isn't best idea. Most of the pictures are incomplete.I think it more likely to be one of the PC issues I mentioned, but try a longer RF lead as a test. The RF gain is in the LNB, so longer cables can be tolerated. David -- SatSignal Software - Quality software for you Web: https://www.satsignal.eu Email: david-taylor@blueyonder.co.uk Twitter: @gm8arv
|
|