TBS 6925 PCi Card with hardware blind scan in DVB-S2 and DVB-S

[Vipersan]

Hi friends
Finally got a fairly complete set of transponder .ini files together for 30 East to 58 West.
_most_ of receiveable channels/transponders covered ...though some are time of day dependent.
_some_ of the satellites carry few Tv channels ...but data channels are included
An example of which is NSS5 @20 West ..
..no Tv channels at my location ...only data channels.

One interesting thing I wanted to mention ..
I thought NSS10 @ 37.5 West was a very quiet spot in the sky ...
How wrong I was ...
Yes there are a couple of TV channels Silverbird & Metro ....but there are also at least 15 data transponders active at this point in the arc..

just goes to show how wrong you can be ...
rgds
VS

 

[Huevos]

got a fairly complete set of transponder .ini files together for 30 East to 58 West.

Now you've just got Ku-band left to do.

 

[Vipersan]

Now you've just got Ku-band left to do.

Yeah ...you might well larrrf Huevos ..
I fully intend to do just that ...but not until they fix the diseqc (1.1/usals/22khz band switching) & dvbviewer app compatibility issues ..
Just too long winded to keep climbing in the loft to isolate the various dishes.
Doh!
rgds
VS

 

[strs65]

When I clicked on the frequency TSReader started, and indeed I had to set manually parameters.I was surprised that even TSReader can be activated by EBS!!!I'm pretty sure it can automatically activate tsreader directly from transponder elected as you can start it from CrazyScan.

After some trials, I think this is not possible with the current TBS6925 source file for TSReader. It just doesn't support command line parameters as some other source files do (see screenshots). So every time I was trying to pass some parameters (frequency, sr, polarization, etc) to TSReader with the TBS 6925 I was getting always the same error message (third screenshot). TSReader was not recognizing correctly the card as a satellite DVB-S/S2 card and obviously was mistaken it as a DVB-T or DVB-C card!

 

[satesco]

After some trials, I think this is not possible with the current TBS6925 source file for TSReader. It just doesn't support command line parameters as some other source files do (see screenshots). So every time I was trying to pass some parameters (frequency, sr, polarization, etc) to TSReader with the TBS 6925 I was getting always the same error message (third screenshot). TSReader was not recognizing correctly the card as a satellite DVB-S/S2 card and obviously was mistaken it as a DVB-T or DVB-C card!

I tried this method myself without success.Cjcr, author of EBS, said that TSReader can be activated only with professional versions and command line is the following:Code-{0} {2} {1} {18} 0 and and Uncheck send in kHz.

ps-@strs65,what kind of dvbs2 card you have?;because Cjcr said that with Prof7301 EBS don't work with TSReader{own BDA}.

 

[Vipersan]

Hi friends ..
Spent most of Sunday scanning the Western arc in Ku after hooking the TD110/Black Ultra up to the TBS card directly ..

When I do the Eastern arc it will be 2E to 28E using the same combo ..but 30East to 66East The TD88/Black Ultra combo takes over
I appreciate that Transponder ini files already exist ...but This was to prove to me definatively just what a dish around 1 mtre can actually see in the NW UK ..
Hope Someone other than just me finds it useful ..
..as Data transponders are included as usual..
rgds
VS

 

[strs65]

I tried this method myself without success.Cjcr, author of EBS, said that TSReader can be activated only with professional versions and command line is the following:Code-{0} {2} {1} {18} 0 and and Uncheck send in kHz.

Yes, I also tried some other schemes, this one included. None worked, I always had the same error. I also tried to launch TSReader directly from a command prompt window using the command line parameters as they are listed in the TSReader site. As soon as I put a source command line parameter I get the same error. It is obvious to me that the current "TSReader_BDASource_TBS6925.dll" source file does not support at this stage command lines.

ps-@strs65,what kind of dvbs2 card you have?;because Cjcr said that with Prof7301 EBS don't work with TSReader{own BDA}.

The 6925, I think it is obvious. I also have a Technotrend TT S2-1600 in the pc, but it doesn't work directly with TSReader (only with tcp/ip streaming from CrazyScan).

 

[Llew]

A useful set of .ini's there VS. Will do a check of them with my setup in due course.

 

[Vipersan]

Hi Friends ..
Completion of whats viewable for me on the TD110
Now starting on the rest of the Eastern arc ..which requires moving to the TD88

So ...part Eastern arc zipped transponder .ini files 2.0 East to 28.2 East attached
rgds
VS

 

[Vipersan]

Hmmm ....
Spent many wasted hours trying to figure out why EBS/TBS couldn't scan the HD mux on Hellas 2 @39East ..
I know damned well I can receive this ok ..but with occasional freezes and fluctuations in the past ..
I _think_ I finally have it figured out ..
After manually inputting the transponder and forcing a channel scan I moved on to Turksat @42 East ..
I performed the usual EBS TBS scan ...but it omitted the Dsmart mux containing TayTV ..
This I also know I can get ...but again I had to force a manual scan ...

See if you can spot why ??
I think I have finally worked this out ..

rgds
VS



11012 V
tp 2 Dolce TV DVB-S2
MPEG-4/HD
Videoguard 30000-3/4
8PSK
-----------------------------

11012 V
tp 9 D-Smart DVB-S
Videoguard 30000-5/6

D-Smart promo 1401 1101 1201 Tu

TAY TV 1439 1139 1239 Tu

Sports TV 1441 1141 1241 Tu

 

[Vipersan]

...No takers ?
If not...I'll give what I believe to be the explanation for this oddity..after I've made myself a mug of tea..
If anyone wants to hear it that is
;)
rgds
VS

 

[strs65]

Wait, I'm scanning (no problem so far).

Ok, everything just fine!



If those two satellites were closer (1 degree apart) I would suspect some kind of interference between them, but now?

 

[Vipersan]

Ok ..here goes ..
Since I'm using a smaller dish ..the TD88 ....this effectively makes beam width wider ...
The dish is therefore more prone to co channel reception ..
I also believe that since both signals travel roughly the same distance ....and both birds effectively are received at an oblique angle relative to my location ..the beams are effectively elongated ...effectively making the illumination footprint oval ..
This again makes a small dish likely to get fragments of co channel regardless of which sat I'm directly pointing at ..
Thus the dish picks up both sats at the same time ...
Ordinarily this wouldn't be a problem if I was the intended target ...or If I used a bigger dish with a narrower beamwidth ..
But ...I'm not..
To make the situation worse ..
both transponders are using the same frequency and SR ...
The difference being one is S the other S2 ...and the FECs are different ...but very similar ..
I believe that the process of blind scanning ..which steps through all variants of fec ..is causing the received dual signal (one dominant ..the other not) ..to confuse the TBS tuner ..
This of course doesn't happen when all variables are specified during a forced scan ...and thus the tuner can't get confused ...
Result ..the transponders scan perfectly ....just not if blind-scanned ..
Anyone think this is plausible ?
rgds
VS

 

[Vipersan]

Wait, I'm scanning (no problem so far).

Ok, everything just fine!

View attachment 37016

If those two satellites were closer (1 degree apart) I would suspect some kind of interference between them, but now?

You have it Strs ...but I believe the location and size of the dish are the missing factors ..
but essentially ..you are correct..
rgds
VS

 

[strs65]

Yes, could be. Smaller dish (wider reception angle) lower signals from both. I have already seen this scenario, but mainly with Amos and Atlantic Bird 3 (1 degree apart).

 

[Vipersan]

Yes, could be. Smaller dish (wider reception angle) lower signals from both. I have already seen this scenario, but mainly with Amos and Atlantic Bird 3 (1 degree apart).

Agreed Strs ..
If the sats in question were higher on the arc ...they would have to be closer together for this effect to be observed ..
but lower to the horizon ..I suspect they can produce this effect at 3 degrees apart ..
I have noticed this elongating illumination effect ..when I was persuing 66East ...
I observed that I could move the TD88 a long way East and West (relatively speaking) without losing the signal completely..
Food for thought..
;)
rgds
VS

 

[strs65]

Yeap, tasty food!

 

[Lazarus]

Yes, could be. Smaller dish (wider reception angle) lower signals from both. I have already seen this scenario, but mainly with Amos and Atlantic Bird 3 (1 degree apart).

No such possibility in UK as Amos is marginal and AB3 stonking!

But I get where you are coming from.

 

[Vipersan]

Yeap, tasty food!

Tasty indeed m8 ...but not as tasty as a Gyros ...
mmm ...
That takes me back ..
The only fast food I ever really enjoyed.
rgds

 

[Huevos]

I believe the location and size of the dish are the missing factors

VS, I don't really see where you are coming from. 17º isn't exactly low elevation and anyway 3º is 3º whatever the elevation. Also, on an 80cm dish 3º off target results in a signal around 20dB down. That means the signal coming from the central satellite is 100x stronger than that coming from the offset satellite. With a 5/6 FEC signal you need <8dB SNR for correctable reception leaving 12dB in reserve. That means for this effect to happen one signal needs to be at least 12dB stronger than the other... but that would mean you would have a 32dB margin in the other direction, i.e. almost 2000:1 SNR. I can see a strong signal on an adjacent satellite wiping out a weak one on the central satellite but it would not be possible for that to happen in both directions, at least not at 3º separation.