Date
1 - 20 of 20
BER and bad frame rate issues with the new uplink and the SR1
|
Perhaps this may be of help to someone...
Following a suggestion from Gordon Smith (EUMETSAT) I changed the MODCOD setting on my two separate BAS and HVS-1 Ayecka receivers from BAS-only and HVS1-only respectively to BAS+HVS1 on both. This resulted in the BER rate report on both dropping to zero: https://www.satsignal.eu/mrtg/performance_eumetcast-europe_ber.php This also appears to have dropped the bad frame rate to zero: https://www.satsignal.eu/mrtg/sr1-bad-frames.html https://www.satsignal.eu/mrtg/sr1b-bad-frames.html Of course, it now leaves my BAS reception being cut whenever the HVS-1 level is too low, sigh. Of course, this was not previously required. What we are getting now, is not what we had before.... Cheers, David -- SatSignal Software - Quality software for you Web: https://www.satsignal.eu Email: david-taylor@... Twitter: @gm8arv |
|
|
|
Hugo
Thanks David, I'm going to try that. I have a BAS only station at the moment and have a lot of 'missing keys' and no delivery of files ...
It is certainly not what we had before ... Grts, Hugo |
|
|
|
Douglas Deans
On 17/12/2022 06:56, David J Taylor GM8ARV 🏴 🇪🇺 via groups.io wrote:
Perhaps this may be of help to someone...========================================================================================= I have a SR1 only on basic and yesterday for about 5 hours had no issues This morning on the same set up I am losing about 10,000 packets every 5 minutes. The whole thing is just a mess. Regards, Douglas. |
|
|
|
On 17/12/2022 08:57, Douglas Deans via groups.io wrote:
I have a SR1 only on basic and yesterday for about 5 hours had no issuesMy BAS+HVS1 fix was intended just to reduce the erroneous BER reports. It did that. I've now zeroed those out in the MRTG graphs. However it seems to have also stopped bad frames as well: http://web-server/blueyonder/mrtg/sr1-bad-frames.html My TelliCast losses are now essentially zero, so it may be worth a try on your SR1. I do think this needs further resolution by EUMETSAT/Telespazio as many folk reply on the Basic Service and having to open to HVS-1 as well effectively reduces the signal by several dB. 73, David GM8ARV -- SatSignal Software - Quality software for you Web: https://www.satsignal.eu Email: david-taylor@... Twitter: @gm8arv |
|
|
|
On 17/12/2022 08:36, Hugo wrote:
Thanks David, I'm going to try that. I have a BAS only station at the moment and have a lot of 'missing keys' and no delivery of files ...Do give it a try, Hugo, and report back. I hope it can't make things any worse, and it is reversible. At one point yesterday restarting the TelliCast client software was suggested, although this didn't work well for me. It may be another thing to try. Cheers, David -- SatSignal Software - Quality software for you Web: https://www.satsignal.eu Email: david-taylor@... Twitter: @gm8arv |
|
|
|
Ernst Lobsiger
Hi,
in 2014 EUMETSAT told us that we could still use our smaller dishes for BAS due to the benefits of VCM. Then we found out that HVS-1 with low link margins was tearing down BAS as well. MODCOD filters came as an SR1 firmware update and we had now expensive DVB-S2 VCM routers for the job we have done before with cheap SkyStar cards. Most of us bought bigger antennas and finally even GNU/Linux had MODCOD filters built in the TBS open source drivers. Now they suggest us to go without MODCODS to at least suppress BER and bad frames reports? I have currently five TBS-6909X cards. I have not payed for them but worked hard with TBS and CrazyCat to get them to where they have been for the last years. With the kind of signal we still get on HVS-2 C10 (H) these cards are capable to receive BAS with MODCODS set, HVS-1, HVS-2 and coming HVS-3 all at the same time. I have used 3 demodulators of these cards for years and will not switch off BAS MODCODS again but expect EUMETSAT and TeleSpazio to fix this transport stream issue. I have angrily setup a BAS only receiver with a 15 Euro SkyStar2 eXpress from eBAY.de yesterday. Regards, Ernst  |
|
|
|
Graham Woolf
Hi Ernst
I hope so too - I dont want to have yet another PC Its only the Basic service thats broken - I am still getting HVS1and 2 through normally Kind Regards Graham |
|
|
|
On 17/12/2022 11:09, Graham Woolf wrote:
Hi ErnstGraham, Perhaps no need for another PC, just a second-hand TBS5925 and a USB input to the PC? That box also has an RF feed at least for the same frequency band and polarisation which you can use for e.g. spectrum analysis with a cheap RTL-SDR.COM dongle. David -- SatSignal Software - Quality software for you Web: https://www.satsignal.eu Email: david-taylor@... Twitter: @gm8arv |
|
|
|
Christian Peters
Hi all,
toggle quoted message
Show quoted text
I have similar problems here. Running two linux systems: - 2x TBS5925 (BAS+HVS-1 on C4)+(HVS-2 on C10) problems on BAS, HVS-1 (no TPG-1 and TPG-2 any more on HVS-1 since the provider switch - both systems!): Failed to open data channel `E1H-TPG-1',
address 224.223.223.3:7013: No data received from sender Failed to open data channel `E1H-TPG-2',
address 224.223.223.3:7015: No data received from sender HVS-2 on C10 error free and perfect!  - TBS 6909x (BAS demod 1 C4, HVS-1 demod 2 on C4, HVS-2 demod 3 on C3) same problems as with TBS-5925 but much better on BAS as Ernst and Graham, even BAS, HVS-1 and HVS-2 with errors  Nothing changed in the setup, all raised with the provider switch at 15-12-2022, 10:15 local time Germany. Regards, Christian
|
|
|
|
Ernst Lobsiger
On Sat, Dec 17, 2022 at 03:09 AM, Graham Woolf wrote:
I am still getting HVS1and 2 through normallyGraham, NO, nothing behaves as usual. The Telespazio managed HVS-1 and HVS-2 quality is much worse too. Yesterday afternoon I have set back receiver Luna to a single cable solution using HVS-2 on C10 (H) again. This transponder Uplink is still managed by the old provider until the end of 2022 according to EUMETSAT. Kallisto uses HVS-2 on C3 (V). Here is the result so far. @David the fact that different SR1 receivers report or don't report BER and bad frames issues could -- appart from MODCOD setting --- point to different versions of firmware. I doubt that most SR1 users have always updated to the latest available SR1 firmware. Some might even not have the MODCOD extensions. Cheers, Ernst |
|
|
|
On 17/12/2022 11:48, Ernst Lobsiger via groups.io wrote:
@David the fact that different SR1 receivers report or don't report BER and bad frames issues could -- appart from MODCOD setting --- point to different versions of firmware. I doubt that most SR1 users have always updated to the latest available SR1 firmware. Some might even not have the MODCOD extensions.Yes, that's a good point. I haven't done any updates for a while, but I think I was up-to-date with the recommended firmware at the time we were doing e.g. HVS-1 and possible HVS-2. My three SR1s report as follows: SR1 #1 - BAS SR1c SW: 1.05b264 V HW: 2.05 FW: 2.02b022 V BL: 1.01b14 SR1 #2 - HVS-1 SR1c SW: 1.05b264 V HW: 2.00 FW: 2.02b022 V BL: 1.01b14 SR1 #3 - HVS-2 SR1c SW: 1.05b264 V HW: 2.10 FW: 2.02b022 O BL: 1.01b14 So the hardware version is the only difference. Of course, these were all working perfectly (i.e. zero errors) until the change. This is the version recommended in the current EUMETSAT document: ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ SR1c Serial No. 111700 30AAC Run Time: 46:11:04 Software Version 1.05b264 Hardware Version 2.00 Firmware Version 2.02b022 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ No, I don't know what, if any, difference there is between the "O" and the "V" firmware. Software 264 is the latest version on the EUMETSAT site, so it seems they are unlikely to be running anything later: https://sftp.eumetsat.int/public/folder/uscvknvooksycdgpmimjnq/User-Materials/EUMETCast_Support/EUMETCast_Licence_cd/Windows/DVB_devices/SR1/SR1_updates/ Cheers, David -- SatSignal Software - Quality software for you Web: https://www.satsignal.eu Email: david-taylor@... Twitter: @gm8arv |
|
|
|
geojohnt@aol.com
David,
Regarding the SR1 and the points you and Ernst make, here are my reading:
SR1c. S/W V1.05b264 V. FPGA V2.02b022 V. H/W V2.10 S/N 111538 30AAC.
I cleared the SR1's BFCO and BPC - if they were not at 0, which I think they were anyway - last evening and at 14:30 today I had 0 BFCO and 0 BPC.
My BER is 0.00e-7.
SNR 13.8 dB Power -18 dBm.
I reported on BS and HVS-1 MPBFEC and FECRP last evening.
This count has gone up a little but all (again - unusually for me) have been recovered.
BS 59 59
HVS-1 93 93
I run a single BS/HVS-1 PC system with 3 x MDM, 1x Himawari, 2 x GOES, 2X Metop Manager, 1 x MSG Animator, AVHRR Manager. And SR1 Controller (1.01b491) 192.168.10.99
I don't run RAMDISK.
And you know Norton is 'in the system' somewhere.
I note your comments on 'Windows security' is sufficient.
Regards,
John
-----Original Message-----
From: David J Taylor GM8ARV 🏴 🇪🇺 via groups.io <david-taylor@...> To: MSG-1@groups.io Sent: Sat, 17 Dec 2022 14:24 Subject: Re: [MSG-1] BER and bad frame rate issues with the new uplink and the SR1 On 17/12/2022 11:48, Ernst Lobsiger via groups.io wrote:
> @David the fact that different SR1 receivers report or don't report BER and bad > frames issues could -- appart from MODCOD setting --- point to different > versions of firmware. I doubt that most SR1 users have always updated to the > latest available SR1 firmware. Some might even not have the MODCOD extensions. Yes, that's a good point. I haven't done any updates for a while, but I think I was up-to-date with the recommended firmware at the time we were doing e.g. HVS-1 and possible HVS-2. My three SR1s report as follows: SR1 #1 - BAS SR1c SW: 1.05b264 V HW: 2.05 FW: 2.02b022 V BL: 1.01b14 SR1 #2 - HVS-1 SR1c SW: 1.05b264 V HW: 2.00 FW: 2.02b022 V BL: 1.01b14 SR1 #3 - HVS-2 SR1c SW: 1.05b264 V HW: 2.10 FW: 2.02b022 O BL: 1.01b14 So the hardware version is the only difference. Of course, these were all working perfectly (i.e. zero errors) until the change. This is the version recommended in the current EUMETSAT document: ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ SR1c Serial No. 111700 30AAC Run Time: 46:11:04 Software Version 1.05b264 Hardware Version 2.00 Firmware Version 2.02b022 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ No, I don't know what, if any, difference there is between the "O" and the "V" firmware. Software 264 is the latest version on the EUMETSAT site, so it seems they are unlikely to be running anything later: https://sftp.eumetsat.int/public/folder/uscvknvooksycdgpmimjnq/User-Materials/EUMETCast_Support/EUMETCast_Licence_cd/Windows/DVB_devices/SR1/SR1_updates/ Cheers, David -- SatSignal Software - Quality software for you Web: https://www.satsignal.eu Email: david-taylor@... Twitter: @gm8arv |
|
|
|
I think I must be pretty luck to not have any problems with my setup. I am on Mizen Head in SW Ireland, so not a good signal at the best of times. I am just receiving the Basic Service on an Ayecka SR1 as below:
SW Ver 1.05b264 V HW Ver 2.10 FW Ver 2.02b022 V BL Ver 1.01b14 My receiving system us running on Ubuntu 18.04.6 LTS on a QEMU Virtual Server and then another QEMU Virtual server on the same Dell Box using SatPy to create the images I need. Yes I did get a few dropped/recovered packets last night because of heavy rain, but really once the first few hours of the changeover occurred everything is much the same as before. Sorry if this upsets folk with problems, but I just thought I would let the group know all is well here as far as I can see. Seasons Greetings all round Francis |
|
|
|
Hugo
David,
I changed the filter to 0x41000, but my dish is only 80~90 cm diameter and this results in an SNR of only 8.5db ... Also I noticed that my Software version of the SR1 is 1.05b255 . I need a bigger dish ... Grts, Hugo |
|
|
|
On 18/12/2022 14:53, Hugo wrote:
David,Changing the MODCOD should not affect the SNR. Not sure where you are located, Hugo, but Arne van Belle gets an SNR of over 12 dB with a "90cm" dish: https://home.hccnet.nl/a.van.belle/MRTG/dvbdataex-snr-p1-tbs6983-tunera.html He's located at 's-Gravendeel in the Netherlands. I feel you should be doing better so, if you can, do check dish pointing and LNB skew adjustments. I don't recall what software 1.05b264 did for us - possibly just SNMP MIBs - but it /might/ be worth upgrading. Cheers, David -- SatSignal Software - Quality software for you Web: https://www.satsignal.eu Email: david-taylor@... Twitter: @gm8arv |
|
|
|
Luis Martín Pomares
Hello, I don't receive any package since last Thursday. My configuration is the following. What is wrong?    On Sun, Dec 18, 2022 at 7:48 PM David J Taylor GM8ARV 🏴 🇪🇺 via groups.io <david-taylor=blueyonder.co.uk@groups.io> wrote: On 18/12/2022 14:53, Hugo wrote: |
|
|
|
Ernst Lobsiger
Luis,
there is a problem with the new Uplink that will probably last for the next weeks. Try to set MODCOD "All" (or whatever it does show for no MODCOD filter). But don't expect your results to be as good as before last Thursday ... Ernst |
|
|
|
Luis Martín Pomares
thnk you Ernst. It worked with the CCM option in MODCOD On Mon, Dec 19, 2022 at 3:40 PM Ernst Lobsiger via groups.io <ernst.lobsiger=belponline.ch@groups.io> wrote: Luis, |
|
|
|
Hugo
On Sat, Dec 17, 2022 at 06:24 AM, David J Taylor GM8ARV 🏴 🇪🇺 wrote:
David, just read in the Ayecka SR1 manual (page 5): e) X' - there is no version in flash f) O' - there is one version in flash g) V' - there is two versions in flash grts, Hugo |
|
|
|
On 19/12/2022 13:00, Hugo wrote:
David,Thanks< Hugo. So the "V" verasion mush have has an upgrade! Cheers, David -- SatSignal Software - Quality software for you Web: https://www.satsignal.eu Email: david-taylor@... Twitter: @gm8arv |
|
|
