LM query TBS


fvalk@...
 

David,

 

I have a query concerning link margin reporting on a new TBS6908 card.

- I include separate .inc files into the mrtg.cfg for lm, snr etc.

- my TBS6808 has currently three wired connections to three different LNB outputs

- they provide separate data streams for basic, HVS1 and HVS2

- in order to define in the link-margin.inc which receiver is being polled we use:

Target[IDname-bdadataex-lm]: `signalex.exe snr n` - value

Where n stands for the device number of the receiver on the TBS and -value for what is being subtracted from the SNR for the stream.

 

In my case device 1 = basic, device 2 = HVS1 and device 3 = HVS2.

On the basic I subtract 5.9 dB and reporting is OK

On the HVS1 I subtract 9.3 dB and reporting is OK

On HVS2 I also subtract 9.3, but no results are coming back and 0.0dB is reported.

I have also tried `signalex.exe snr` and `signalex.exe snr 0` for the third (HVS2) device, but to no avail.

 

Is there maybe a limit to the device numbers known to signalex.exe that you know of? Or am I maybe overlooking the usual obvious thing?

Your thoughts are appreciated.

 

Cheers,

Ferdinand


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

On 14/01/2023 12:55, fvalk@... wrote:
David,
I have a query concerning link margin reporting on a new TBS6908 card.
- I include separate .inc files into the mrtg.cfg for lm, snr etc.
- my TBS6808 has currently three wired connections to three different LNB outputs
- they provide separate data streams for basic, HVS1 and HVS2
- in order to define in the link-margin.inc which receiver is being polled we use:
Target[IDname-bdadataex-lm]: `signalex.exe snr n` - value
Where n stands for the device number of the receiver on the TBS and -value for what is being subtracted from the SNR for the stream.
In my case device 1 = basic, device 2 = HVS1 and device 3 = HVS2.
On the basic I subtract 5.9 dB and reporting is OK
On the HVS1 I subtract 9.3 dB and reporting is OK
On HVS2 I also subtract 9.3, but no results are coming back and 0.0dB is reported.
I have also tried `signalex.exe snr` and `signalex.exe snr 0` for the third (HVS2) device, but to no avail.
Is there maybe a limit to the device numbers known to signalex.exe that you know of? Or am I maybe overlooking the usual obvious thing?
Your thoughts are appreciated.
Cheers,
Ferdinand
I don't know!

You've already tried:

signalex.exe snr

signalex.exe snr 1

signalex.exe snr 2

signalex.exe snr 3

and see whether values are retuned for all three tuners (and a failure for the fourth?). Other than that, it seems like there might be a limit on device numbers that CrazyCat has set or simply been unable to test not having a four-tuner device.

Perhaps someone else can help?

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


fvalk@...
 

-----Original Message-----
From: MSG-1@groups.io On Behalf Of David J Taylor
GM8ARV ?????????????? ???? via groups.io
Sent: Saturday, 14 January, 2023 14:53
To: MSG-1@groups.io
Subject: Re: [MSG-1] LM query TBS

On 14/01/2023 12:55, fvalk@... wrote:
David,

I have a query concerning link margin reporting on a new TBS6908 card.

- I include separate .inc files into the mrtg.cfg for lm, snr etc.

- my TBS6808 has currently three wired connections to three different
LNB outputs

- they provide separate data streams for basic, HVS1 and HVS2

- in order to define in the link-margin.inc which receiver is being polled we
use:

Target[IDname-bdadataex-lm]: `signalex.exe snr n` - value

Where n stands for the device number of the receiver on the TBS and
-value for what is being subtracted from the SNR for the stream.

In my case device 1 = basic, device 2 = HVS1 and device 3 = HVS2.

On the basic I subtract 5.9 dB and reporting is OK

On the HVS1 I subtract 9.3 dB and reporting is OK

On HVS2 I also subtract 9.3, but no results are coming back and 0.0dB is
reported.

I have also tried `signalex.exe snr` and `signalex.exe snr 0` for the
third
(HVS2) device, but to no avail.

Is there maybe a limit to the device numbers known to signalex.exe
that you know of? Or am I maybe overlooking the usual obvious thing?

Your thoughts are appreciated.

Cheers,

Ferdinand
I don't know!

You've already tried:

signalex.exe snr

signalex.exe snr 1

signalex.exe snr 2

signalex.exe snr 3

and see whether values are retuned for all three tuners (and a failure for the
fourth?). Other than that, it seems like there might be a limit on device
numbers that CrazyCat has set or simply been unable to test not having a
four-tuner device.

Perhaps someone else can help?

Cheers,
David
=============================
Yes, maybe CrazyCat can enlighten us. Whichever setting I use, only a max of two receivers are reporting out of (my) max 4. One can envision the situation that with more transponders coming online in the future, an octo receiver might be opportune!

Cheers,
Ferdinand


Ernst Lobsiger
 

On Sat, Jan 14, 2023 at 07:47 AM, <fvalk@...> wrote:
One can envision the situation that with more transponders coming online in the future, an octo receiver might be opportune!
Ferdinand,

with the TBS6909X I use the following setup. Given that BAS+HVS-1, HVS-2 and future HVS-3 are all in the LOW band I can feed the card in mode=0 with two cables only: One cable at plug LNB0 and one cable at plug LNB2. This way I can use demod0 for BAS with MODCODs filtered, demod1 for HVS-1, demod2 for HVS-2 and demod3 for future HVS-3. There is still room to experiment in LOW band with demods 4 - 7 e.g. for sun outage measurements using an extra strong but moderate bandwidth transponder. I have demonstrated years ago that this card can easily cope with four full fledged EUMETCast transponders. That said with one Inverto black ultra QUAD LNB, four cables but no additional components like splitters or multi switches I can setup two such EUMETCast receivers. Unfortunately AFAIK this only works under GNU/Linux and CrazyCat lives (used to live?) in Charkiv. The good news is that EUMETSAT has finally bought a TBS6909X and I'm currently giving them a hand to set it up.

Cheers,
Ernst


Graham Woolf
 

Hi Ernst

I currently have my two cables plugged into LNB0/1
It appears to be working OK so should I leave them or move one to LNB2

If I do that do I need to change any files

Kind Regards

Graham


Ernst Lobsiger
 

Graham,

TBH my second receiver still works that way for comparison. This is called (direct) mode=1. It means you have demod0 + demod1 behind plug LNB0, demod2 + demod3 behind plug LNB1, etc., etc.. This way we will not be able to add HVS-3 with two cables unless stopping running BAS with MODCODs. The only possibility will be BAS+HVS-1 at demod0, HVS-3 at demod1 (H) and HVS-2 at demod2 (V). If you move the second cable to plug LNB2 you have to set (multi switch) mode=0 in /etc/modprobe.d/stid135.conf and reboot.

Regards,
Ernst


Graham Woolf
 

Hi Ernst

Thanks - in that case I think I will leave as is until HVS3 actually arrives

Kind Regards

Graham


fvalk@...
 

Ernst,

 

I was away last night and missed your note.

That is an interesting, economic and very versatile setup you use and certainly future proof. My setup here is (for operational purposes) more gluttonous than that. I have eight cables coming in from an octo lnb and the TBS6908 gets one cable connected per receiver. Basic, HVS1 and HVS2 each use a dedicated receiver and the fourth is meant for HVS3. Each data stream is being handled with its own hard disk to limit interference and to prevent excessive disk access times. The other LNB cables are in use for non-operational activities and backup receivers (SR-1 and TBS6903).

 

Still, I can now run the full operation via only two PCs: one receiving and handling all data and the other doing all customer jobs. Two other PCs are off-line as backup in case of need. Next to this I have my main machine running all else.

 

Cheers,

Ferdinand

 

From: MSG-1@groups.io On Behalf Of Ernst Lobsiger via groups.io
Sent: Saturday, 14 January, 2023 16:57
To: MSG-1@groups.io
Subject: Re: [MSG-1] LM query TBS

 

On Sat, Jan 14, 2023 at 07:47 AM, <fvalk@...> wrote:

One can envision the situation that with more transponders coming online in the future, an octo receiver might be opportune!

Ferdinand,

with the TBS6909X I use the following setup. Given that BAS+HVS-1, HVS-2 and future HVS-3 are all in the LOW band I can feed the card in mode=0 with two cables only: One cable at plug LNB0 and one cable at plug LNB2. This way I can use demod0 for BAS with MODCODs filtered, demod1 for HVS-1, demod2 for HVS-2 and demod3 for future HVS-3. There is still room to experiment in LOW band with demods 4 - 7 e.g. for sun outage measurements using an extra strong but moderate bandwidth transponder. I have demonstrated years ago that this card can easily cope with four full fledged EUMETCast transponders. That said with one Inverto black ultra QUAD LNB, four cables but no additional components like splitters or multi switches I can setup two such EUMETCast receivers. Unfortunately AFAIK this only works under GNU/Linux and CrazyCat lives (used to live?) in Charkiv. The good news is that EUMETSAT has finally bought a TBS6909X and I'm currently giving them a hand to set it up.

Cheers,
Ernst