Tellicast on Linux and HVS-2


Christian Peters
 

Just for info, 

I did a power off for 5min and restarted everything, now the card works flawless (proposed by Ernst-thank you very much!). 
Just for info if you have problems with retuning the 6909X. A reboot doesn’t cure it.

Regards,

Christian 

Am 23.11.2022 um 12:48 schrieb Christian Peters via groups.io <hctpeters@...>:

Ernst,

strange,
/etc/modprobe.d/stid135.conf
has set:
options stid135 mode=1 rfsource=0 ts_nosync=1
..?

systool -vm stid135 shows:

Module = "stid135"
  Attributes:
    coresize            = "323584"
    initsize            = "0"
    initstate           = "live"
    refcnt              = "8"
    taint               = "OE"
    uevent              = <store method only>

  Parameters:
    mc_auto             = "0"
    mode                = "1"
    rfsource            = "0"
    ts_nosync           = "1"

Two cables connected (Port 1+2)

Regards,

Christian

Am 23.11.22 um 10:32 schrieb Ernst Lobsiger via groups.io:
On Tue, Nov 22, 2022 at 11:00 PM, Christian Peters wrote:

Hm….no! The new transponder setting (h/v) is not working here. :-(
BAS and HVS-2 is good, HVS-1 is not working correct, see screenshot.


Christian,

your HVS-1 looks like a new compiled driver with missing ts_nosync=1.

Everything works fine here with HVS-2 vertical having a +4dB
signal and also some +0.8dB increase in HVS-2 SNR seen.

Ernst










Christian Peters
 

Ernst,

strange,
/etc/modprobe.d/stid135.conf
has set:
options stid135 mode=1 rfsource=0 ts_nosync=1
..?

systool -vm stid135 shows:

Module = "stid135"
  Attributes:
    coresize            = "323584"
    initsize            = "0"
    initstate           = "live"
    refcnt              = "8"
    taint               = "OE"
    uevent              = <store method only>

  Parameters:
    mc_auto             = "0"
    mode                = "1"
    rfsource            = "0"
    ts_nosync           = "1"

Two cables connected (Port 1+2)

Regards,

Christian

Am 23.11.22 um 10:32 schrieb Ernst Lobsiger via groups.io:

On Tue, Nov 22, 2022 at 11:00 PM, Christian Peters wrote:

Hm….no! The new transponder setting (h/v) is not working here. :-(
BAS and HVS-2 is good, HVS-1 is not working correct, see screenshot.

Christian,

your HVS-1 looks like a new compiled driver with missing ts_nosync=1.

Everything works fine here with HVS-2 vertical having a +4dB
signal and also some +0.8dB increase in HVS-2 SNR seen.

Ernst





Ernst Lobsiger
 

On Wed, Nov 23, 2022 at 01:32 AM, Ernst Lobsiger wrote:
Everything works fine here with HVS-2 vertical having a +4dB
signal and also some +0.8dB increase in HVS-2 SNR seen.
... and here is my first image received with HVS-2 V polarization.

Cheers,
Ernst


Ernst Lobsiger
 

On Tue, Nov 22, 2022 at 11:00 PM, Christian Peters wrote:
Hm….no! The new transponder setting (h/v) is not working here. :-( 
BAS and HVS-2 is good, HVS-1 is not working correct, see screenshot.
 
Christian,

your HVS-1 looks like a new compiled driver with missing ts_nosync=1.

Everything works fine here with HVS-2 vertical having a +4dB
signal and also some +0.8dB increase in HVS-2 SNR seen.

Ernst


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

On 23/11/2022 07:00, Christian Peters via groups.io wrote:
Hm….no! The new transponder setting (h/v) is not working here. :-(
BAS and HVS-2 is good, HVS-1 is not working correct, see screenshot.
Regards,
Christian
Christian,

The new transponder is only used for HVS-2, not HVS-1.

As far as I know there has been no change to HVS-1, and even more unlikely late into the evening. No-one else shows a similar change:

https://www.satsignal.eu/mrtg/performance_eumetcast-europe_losses.php
https://www.satsignal.eu/mrtg/performance_eumetcast-europe_rx_io.php

If this is TBS hardware, check that the drivers haven't changed which tuner is being used for HVS-1/BAS.

Watch out for any new cross-polarisation leakage from transponder C3 into C4.

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


Christian Peters
 

Hm….no! The new transponder setting (h/v) is not working here. :-( 
BAS and HVS-2 is good, HVS-1 is not working correct, see screenshot.

Regards,

Christian



Am 22.11.2022 um 21:46 schrieb Christian Peters via groups.io <hctpeters@...>:

Charlie,

now in the evening it looks good here, too. 
(Linux, 2 cables, TBS6909X).

Christian 


Am 22.11.2022 um 21:22 schrieb Charlie <charlie.johnson119@...>:

Tested again this evening (20:20Z) and appears to be functioning correctly now with just the parameter changed in /etc/channels.conf for TP freq and pol.

Charlie



Christian Peters
 

Charlie,

now in the evening it looks good here, too. 
(Linux, 2 cables, TBS6909X).

Christian 


Am 22.11.2022 um 21:22 schrieb Charlie <charlie.johnson119@...>:

Tested again this evening (20:20Z) and appears to be functioning correctly now with just the parameter changed in /etc/channels.conf for TP freq and pol.

Charlie


Charlie
 

Tested again this evening (20:20Z) and appears to be functioning correctly now with just the parameter changed in /etc/channels.conf for TP freq and pol.

Charlie


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

On 18/11/2022 22:10, Charlie wrote:
Still borked here checking just now (2200Z).
Charlie
Oh, sorry to hear that, Charlie.

I wasn't able to find out (yet) what changed, if anything. I say "If anything" because when I was first testing the signal was very marginal - you may have read about the intense rain in eastern Scotland yesterday.

My guess is that the chap I spoke with won't be back until Monday, but do keep sending your reports - and that applies to anyone seeing issues with the new HVS-2/11263/V service.

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


Charlie
 

Still borked here checking just now (2200Z).

Charlie


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

Folks,

I've been in touch with EUMETSAT about this issue and forwarded Charlie's information (most helpful, thanks). I was able to check again at 16:20 UTC today and HVS-2/11263/V now appears to be perfect. Perhaps anyone with the issue could check?

Thanks for your reports.

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


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

On 16/11/2022 16:16, Charlie wrote:
Hi all,
I feel like I've missed something painfully obvious but I've dug through the config files and scripts and can't seem to find what I'm missing.
When I've tested HVS-2 on 11263 V or the HB13 service I've only been able to get the announcement channel on Tellicast - the data channels fail to connect! This is from changing the frequency in /etc/channels.conf.
Changing it back is all okay on 11388 H.
Has anyone else run into this wall and if so, (how) did you manage to fix it?
Charlie

Charles,

I'm seeing something similar with a TBS6903 card and BDADataEx on Windows. I /should/ only need to change frequency and polarisation, but thwn I do that TelliCast doesn't connect correctly. I suggest you report your findings to EUMETSAT as I intend to do.

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


Christian Peters
 

Charlie,

Ernst teaches me something: „RTFM“, but it’s still hard to learn his lesson! :-D 
So maybe they are still testing and we should wait with creating an issue and reporting it to OPS…
I too had strange effects and and a disturbed BAS with the 6909x….
Switched HVS-2 transponder back for now….

"The migration will include a parallel downlink period where the old and new transponders will be used from 24 November to 23 December.“


Regards,

Christian 

Am 16.11.2022 um 20:32 schrieb Charlie <charlie.johnson119@...>:

At least I'm not the only one...!

I've contacted EUMETSAT Ops on this one to see what they say as I'm stumped.

I can get scan-s2 to scan the transponder with dvb-eumetcast running on 11263 V, but not on 11263 H or 11388 H with dvb-eumetcast running *or* stopped. Latter times out as I guess the frontend is taken up already! It's like there is something buried in dvb-eumetcast expecting a different PMT PID or similar. The actual programme PIDs seem to be the same (610 and 611 available there on the HVS-2 PMT) Looks like 11263 V is already on the new teleport going by the following:

PAT
service_id = 0x0
service_id = 0x1
pmt_pid = 0x20
service_id = 0x320
pmt_pid = 0x1F40
>>> parse_section, section number 0 out of 0...!
SDT (actual TS)
0x04B1 0x0001: pmt_pid 0x0020 Telespazio -- HVS-2 (running)
0x04B1 0x0320: pmt_pid 0x1F40 MyIntProvider -- SERVICE IP/MAC NOTIFICATION (running)
>>> parse_section, section number 0 out of 0...!
PMT 0x1F40 for service 0x0320
 OTHER     : PID 0x1F41 TYPE 0x0D
 OTHER     : PID 0x0366 TYPE 0x80
>>> parse_section, section number 0 out of 0...!
PMT 0x0020 for service 0x0001
 OTHER     : PID 0x0262 TYPE 0x0D
 OTHER     : PID 0x0263 TYPE 0x0D
dumping lists (2 services)
Done.

Be nice to compare this against the existing transponders but I can't scan it. Might have to spin up a live boot for a clean system to check...

 

Charlie

 


Charlie
 

At least I'm not the only one...!

I've contacted EUMETSAT Ops on this one to see what they say as I'm stumped.

I can get scan-s2 to scan the transponder with dvb-eumetcast running on 11263 V, but not on 11263 H or 11388 H with dvb-eumetcast running *or* stopped. Latter times out as I guess the frontend is taken up already! It's like there is something buried in dvb-eumetcast expecting a different PMT PID or similar. The actual programme PIDs seem to be the same (610 and 611 available there on the HVS-2 PMT) Looks like 11263 V is already on the new teleport going by the following:

PAT
service_id = 0x0
service_id = 0x1
pmt_pid = 0x20
service_id = 0x320
pmt_pid = 0x1F40
>>> parse_section, section number 0 out of 0...!
SDT (actual TS)
0x04B1 0x0001: pmt_pid 0x0020 Telespazio -- HVS-2 (running)
0x04B1 0x0320: pmt_pid 0x1F40 MyIntProvider -- SERVICE IP/MAC NOTIFICATION (running)
>>> parse_section, section number 0 out of 0...!
PMT 0x1F40 for service 0x0320
 OTHER     : PID 0x1F41 TYPE 0x0D
 OTHER     : PID 0x0366 TYPE 0x80
>>> parse_section, section number 0 out of 0...!
PMT 0x0020 for service 0x0001
 OTHER     : PID 0x0262 TYPE 0x0D
 OTHER     : PID 0x0263 TYPE 0x0D
dumping lists (2 services)
Done.

Be nice to compare this against the existing transponders but I can't scan it. Might have to spin up a live boot for a clean system to check...

 

Charlie

 


Ernst Lobsiger
 

Charlie,

Christian Peters has told me similar stories ..

Ernst


Charlie
 

Hi all,

I feel like I've missed something painfully obvious but I've dug through the config files and scripts and can't seem to find what I'm missing.

When I've tested HVS-2 on 11263 V or the HB13 service I've only been able to get the announcement channel on Tellicast - the data channels fail to connect! This is from changing the frequency in /etc/channels.conf.

Changing it back is all okay on 11388 H.

 

Has anyone else run into this wall and if so, (how) did you manage to fix it?

 

Charlie