Further to my earlier mail re my SR1 performance, I decided after closing down to try my TBS 5925 with both basic and HVS-1 ( so Modecode "all" used ). I tried it with BDADataEx and the TBS IP tool and in both cases constant losses and unusable.

I will try later with one service ( so "all" not used ) but to be honest that is not the set up I would want.

Regards
Ian.

I am using a TBS 5925 Ian. Modcode ALL is unusable for me, errors like mad and drops lock every minute so no reception worth talking about. If I change the modcode to 8PSK3/5 in BDADataEx I can receive BAS ok with a few errors, most of which are recovered, but no HVS1. Change the modcode to 16APSK2/3 and I get HVS1 but no BAS. So it's either\or but not both.

Philip

On 18/12/2022 11:33, Philip Morris via groups.io wrote:

I am using a TBS 5925 Ian. Modcode ALL is unusable for me, errors like mad and drops lock every minute so no reception worth talking about. If I change the modcode to 8PSK3/5 in BDADataEx I can receive BAS ok with a few errors, most of which are recovered, but no HVS1. Change the modcode to 16APSK2/3 and I get HVS1 but no BAS. So it's either\or but not both.
Philip

===================================================================================

Yes I am the same as well Philip. I am running a TBS 5925 for HVS-1 (16APSK 2/3) with some losses but all recovered and all data fine. Switching to all MODCODS is a disaster and unusable.

However my real puzzle on my other computer is the Basic service on a SR1. Yesterday from about 15.00 to 22.00 (when I closed down) I was completely lossless 00.

This morning back to thousands every 10 minutes or so. This has been going on since the uplink change. I have not changed anything so clearly someone else is <smile>. Signal good and steady over those periods, although about 0.5dB SNR down on pre change levels.
Why those good periods then bad periods does puzzle me.

Regards,
Douglas.

On 18/12/2022 11:59, Douglas Deans via groups.io wrote:

This morning back to thousands every 10 minutes or so. This has been
going on since the uplink change. I have not changed anything so clearly
someone else is <smile>. Signal good and steady over those periods,
although about 0.5dB SNR down on pre change levels.
Why those good periods then bad periods does puzzle me.
Regards,
Douglas.

Douglas,

I have heard of instance in the past when parameters changes haven't "stuck". Possibly due to not following the 0, 0, 0 chain after the change until the top menu was reached. I wasn't overly convinced about that, but it may be worth a check to enure that the parameters actually are as you want.

Besides playing with the MODCOD, I was also advised to remove all but 100 and 500 (IIRC) from the PID filter, but I guess you've already done that.

Just as random thought do you see any difference between warm reset and cold reset, and are you closing an restarting the TelliCast client each time?

I'm hoping that Ernst's report on the transport stream may help EUMETSAT to direct Telespazio to the issues causing problems.

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

On 18/12/2022 14:15, David J Taylor GM8ARV 🏴 🇪🇺 via groups.io wrote:

On 18/12/2022 11:59, Douglas Deans via groups.io wrote:

This morning back to thousands every 10 minutes or so. This has been
going on since the uplink change. I have not changed anything so clearly
someone else is <smile>. Signal good and steady over those periods,
although about 0.5dB SNR down on pre change levels.
Why those good periods then bad periods does puzzle me.

Regards,
Douglas.

Douglas,
I have heard of instance in the past when parameters changes haven't "stuck". Possibly due to not following the 0, 0, 0 chain after the change until the top menu was reached.  I wasn't overly convinced about that, but it may be worth a check to enure that the parameters actually are as you want.
Besides playing with the MODCOD, I was also advised to remove all but 100 and 500 (IIRC) from the PID filter, but I guess you've already done that.
Just as random thought do you see any difference between warm reset and cold reset, and are you closing an restarting the TelliCast client each time?
I'm hoping that Ernst's report on the transport stream may help EUMETSAT to direct Telespazio to the issues causing problems.
Cheers,
David

===========================================================================================

Thanks for your observations David.
I have done all the suggested things except a cold start as I am not sure what that actually does. Of course you must do a warm restart after a MODCOD change or it doesn't hold.
The change from 'bad' to 'good' just happens and has nothing to do with any interventions from me. I am often not even at the computer when it happens. It has to be some sort of change in the data stream.

Still I am sure things will get fixed or clarified as there are many expert brains (I do not include myself in this) pursuing it.

Thanks David,
Douglas.

On 18/12/2022 14:26, Douglas Deans via groups.io wrote:

Thanks for your observations David.
I have done all the suggested things except a cold start as I am not
sure what that actually does. Of course you must do a warm restart after
a MODCOD change or it doesn't hold.
The change from 'bad' to 'good' just happens and has nothing to do with
any interventions from me. I am often not even at the computer when it
happens. It has to be some sort of change in the data stream.
Still I am sure things will get fixed or clarified as there are many
expert brains (I do not include myself in this) pursuing it.
Thanks David,
Douglas.

Douglas,

According to the EUMETSAT setup guide:

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
(a) Warm Reset-Restarts the controller without reloading the FPGA or resetting the internal
switch
(b) Cold Reset-Restarts the controller, reloads the FPGA and restarts the internal switch.
(c) Restore to factory-Resets the SR1 to the values set in production, deleting all configurations
performed later.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

I'm just wondering whether the change you see could possibly be triggered by SNR drops below the threshold? What values do you have set?

The more reports the better!

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

On Sun, Dec 18, 2022 at 07:39 AM, David J Taylor GM8ARV 🏴󠁧󠁢󠁳󠁣󠁴󠁿 🇪🇺 wrote:

I'm just wondering whether the change you see could possibly be triggered by SNR drops below the threshold? What values do you have set?

David and Douglas,

the TBS-6909X V2 without modcods set works ("kind of") for BAS and HVS-1. As soon as you set modcods on BAS this service gets unusable.
So it might be an idea to check the start of periods of unusable SR1 reception with slight SNR changes that might trigger modcod filter changes.

Cheers,
Ernst

===================================================================================

Yes I am the same as well Philip. I am running a TBS 5925 for HVS-1

(16APSK 2/3) with some losses but all recovered and all data fine. Switching to all MODCODS is a disaster and unusable.

However my real puzzle on my other computer is the Basic service on a

SR1. Yesterday from about 15.00 to 22.00 (when I closed down) I was completely lossless 00.

This morning back to thousands every 10 minutes or so. This has been

going on since the uplink change. I have not changed anything so clearly someone else is <smile>. Signal good and steady over those periods, although about 0.5dB SNR down on pre change levels.

Why those good periods then bad periods does puzzle me.

Regards,
Douglas.

===============================================================================

I am seeing exactly the same with the TBS 5925.

Yesterday ran the 5925 basic service only on 8PSK for 14 hours with 0/0 missed and recovered packets, but today I do exactly the same and so far have over 4500 missed packets and just over 4000 recovered.

What a mess !!

Regards
Ian.