Welcome to GOFASTMOTORSPORTS.com ... ... ... Green Flag - Green Flag - Go Go Go ... ... Brought to you by Ricks Satellite - Where the Big Dish Rules!

Ricks Satellite Wildfeed and Backhaul Forum
Register Latest Topics
 
 
 


Reply
  Author   Comment   Page 1 of 2      1   2   Next
newsy

Registered:
Posts: 61
Reply with quote  #1 
Hi,

I'm wondering if there is any way to trace down locking errors on that driver modules.
There are two muxes on Hispasat 30°W on 11491 V (CLM) and 11496 H (TVA) that use physical layer scrambling (PLS). When entering the right PLS code I can lock both on windows using crazyscan.
However on linux using the tbsdtv tree or crazycats linux_media tree I can lock CLM but TVA fails with the same HW. I tried both TBS 5980 (stv090x driver) and TBS 6903 (stv0910 driver) and the behavior between is exactly the same.
The muxes use similar parameters, 8psk, fec 8/9 only difference is the symbolrate and CLM has pilots off while TVA has pilots on.

So how can I trace / debug the locking procedure?

__________________
85cm motorized dish 31.5°E - 15.0°W
newsy

Registered:
Posts: 61
Reply with quote  #2 
it seems Status is changing between 01 (FE_HAS_SIGNAL) and 03 (FE_HAS_CARRIER)
__________________
85cm motorized dish 31.5°E - 15.0°W
pendragon

Registered:
Posts: 1,001
Reply with quote  #3 
From your description, the demods are locking the carriers, but not the internal signal timing (SR). I'm very familiar with those symptoms using STV090* demods, but a little less so with the STV0910s. Particular signals can be quite hard to lock and yet others with similar parameters are easy. What troubles me in your case, though, is two different demods lock fine on Windows, but neither on Linux. That suggests the problem might be more systemic than what I experienced, and possibly easier to fix. Maybe the PLS codes you input are getting corrupted in the Linux DVB infrastructure, but that's purely wild speculation because I never do that. However if the problem is embedded in the driver locking process, you could have a real headache on your hands.

I can't speak for the Windows drivers vs. Linux, because I only use the latter. But 7+ years ago I spent a lot of time characterizing the limitations and root causes with the Linux STV090* drivers, and found much of what is there is at best suboptimal and at worst plain wrong. Part of the problem is there are hundreds of hardware registers that have to be tweaked to make the hardware work. Most don't affect locking, but there are enough that are very touchy and coupled to each other. The release Linux drivers are pretty much straight copies of the reference STM STV090* drivers, and I don't think STM ever spent much time on them. To solve my locking problems, I largely rewrote the stv0900 driver for my personal use, although I released a simplified version for general consumption not that long ago. That driver now has very few locking issues, and locks signals noticeably faster. The release drivers haven't changed significantly since 2009, and none of their problems have been fixed.

As for Linux drivers with the STV0910 demods, that hardware is better implemented than the STV090* hardware, meaning the default register settings generally work well. I partially rewrote the stv0910 Linux driver, but for the most part I didn't find it to be the same catastrophes as the stv090* drivers. Perhaps if I invested more time I would find more problems. 
Mounir

Registered:
Posts: 108
Reply with quote  #4 
apparently it seems to be a problem of sensitivity ..on Atlantic Bird 5W i can get the Lock on all italian mutistreams except the french one ( 12648 V PLS Gold : 121212. and 11509 H PLS Gold : 50416.) ...
if someone can confirm this issue ?

i use skystar 2 xpress HD and updatelee driver with pendragon patch .

__________________
Special Thanks to Mr Rick Caylor
newsy

Registered:
Posts: 61
Reply with quote  #5 
@Mounir: Perhaps you are not setting the stream_id correctly for gold mode. What did you set for the french channels?

@pendragon: thanks for your answer. It seems you are right, there might be some mis-/unconfigured hw registers. There's also some other strange behavior here with PLS encrypted channels.
I use my modified version of szap-s2 to allow bigger stream_id values as it contains the pls and also the pls mode. On first tune I get lock, when I stop and restart szap-s2 I get no lock. I first have to tune another non PLS mux and then locking will work again. This workaraound however won't work on TVA of course.
But it seems stv090x and stv0910 are not that different as the problem with TA occours on both of them.

Then there's one really stupid question. Which pendragon patch? I thought these changes are already merged right?

__________________
85cm motorized dish 31.5°E - 15.0°W
newsy

Registered:
Posts: 61
Reply with quote  #6 
@Mounir: I set the following stream_ids for the french muxes.
On 12648 I've got 98139137, 98139138 and 98139139 and on 11509 I've got 80015361, 80015364 and 80015366

__________________
85cm motorized dish 31.5°E - 15.0°W
pendragon

Registered:
Posts: 1,001
Reply with quote  #7 
newsy - My 'rewrite' of the stv0900 driver was mostly done in the 2009-2010 timeframe, but I didn't release it at that time. When people had issues with high rate muxes using the stock Linux drivers sometime afterwards, I posted a snippet from my driver on these forums. Others turned it into a patch and what was referred to at the time as the 'pendragon patch', but it was only a miniscule subset of what I had changed. 

Since then I made improvements and partially rewrote a personal version of the stv0910 driver. I also sat on those changes, because I am running a highly modified kernel with many changes unrelated to DVB, although my drivers take advantage of those features. Thus if I had released my DVB code, it would have been nearly useless without my corresponding kernel mods. 

At the beginning of 2016 I upgraded my kernel, but in order to provide the community with my DVB mods, I first did a baseline merge of my DVB code with a nearly virgin kernel. That meant for a moment in time my drivers were cleaned of my modified kernel dependencies. I posted the results in a thread here, with a few small subsequent updates:

https://rickcaylor.websitetoolbox.com/post/dragon-flames-not-tails-nor-tales-7890469

There was very little interest in that code, although majortom did insert it into a respository he created. Then a few weeks ago midwestmac started a short thread on his efforts:

https://rickcaylor.websitetoolbox.com/post/v4lpendragon-8493821

Over the past year I made a number of important fixes and improvements to my now 'polluted' DVB drivers, but as no one seems particularly interested, I haven't bothered to back these out into a virgin kernel baseline. In terms of your locking issues, I know I made no changes to the stv0900 driver that should have any effect, but it's possible my subsequent stv0910 effort could have affected something in this regard.

You commented on your modified szap-s2 code, and that it only works on the first lock attempt, and after that you have to lock a non PLS mux before it will work again. That sounds like a repeatable problem that I would suggest first debugging at the driver level, because it could even lead to your fundamental problem.
Mounir

Registered:
Posts: 108
Reply with quote  #8 
Quote:
Originally Posted by newsy
@Mounir: I set the following stream_ids for the french muxes.
On 12648 I've got 98139137, 98139138 and 98139139 and on 11509 I've got 80015361, 80015364 and 80015366

thank u newsy 4 reply
i use the enigma2pc of crazycat and i set exactly the pls code mentionned from sites of kingofsat.net ..i will try your streamids and report the result .
regards
mounir
PS: pendragon patch that i use is "high bit rate support" ..

@newsy
can u post please the correct command for szap or scan-s2 with stream_id ?
thank U

PS: on enigma2 it is not possible to insert this .

__________________
Special Thanks to Mr Rick Caylor
newsy

Registered:
Posts: 61
Reply with quote  #9 
@pendragon:
Thanks for you link. I will check those modifications in the next days. I already found out why tuning of pls channels only worked once on each Stop call I need to set default PLS Code 1, then retuning with the same PLS code will work. However for TVA this workaraound did not work.

@Mounir: this is the modified version of szap-s2 https://bitbucket.org/CrazyCat/szap-s2 there was no change done by me. I mixed it up, I just modified dvbstream, as the pid-filter for Pid 0 did not work.

__________________
85cm motorized dish 31.5°E - 15.0°W
Richard

Registered:
Posts: 36
Reply with quote  #10 
Quote:
Originally Posted by pendragon


......

There was very little interest in that code, although majortom did insert it into a respository he created. Then a few weeks ago midwestmac started a short thread on his efforts:

https://rickcaylor.websitetoolbox.com/post/v4lpendragon-8493821

Over the past year I made a number of important fixes and improvements to my now 'polluted' DVB drivers, but as no one seems particularly interested, I haven't bothered to back these out into a virgin kernel baseline.

.......



@Pendragon

An appreciation, very much, for the efforts you have gone to in this regard.

I am currently in the process of working through your "spectrum scanning" additions in an attempt to a) understand how you are getting your narrow resolution data and b) adapt it to the STV0910 driver, as I no longer have an STV0900 card.

This is not likely to happen any time soon, as although I have a strong analogue RF and IT background, DSP and programming are relatively new fields.

I am very much enjoying the learning process and have spent many hours so far, so please don't feel that your contributions are in vain - far from it as far as I'm concerned.

Regards,

Richard
newsy

Registered:
Posts: 61
Reply with quote  #11 
Was the v4l-pendragon tree deleted? Link is not working any more.
__________________
85cm motorized dish 31.5°E - 15.0°W
Richard

Registered:
Posts: 36
Reply with quote  #12 
Quote:
Originally Posted by newsy
Was the v4l-pendragon tree deleted? Link is not working any more.


Looks as though Bill has removed it.

The latest pendragon driver release that the repo was based on, is here:

https://rickcaylor.websitetoolbox.com/post/show_single_post?pid=1291604720&postcount=11&forum=106995

Regards,

Richard
majortom

Avatar / Picture

Registered:
Posts: 4,778
Reply with quote  #13 
do you guys need that repo? It's still there, just set to private...
If someone signs up for their own bitbucket account, and wants to maintain it,
ie pendragon, et al... let me know and I will pass it over to you for maintenance.
Then you can collaborate and do whatever you want with it.

__________________
Perfect 10 7.5' mesh Chapparal C/Ku Co-Rotor feed, Norsat 8115 CBAND, Norsat 4106A Ku Thomson Saginaw Actuator, Vbox positioner,
Home Brew Polarotor683 Servo circuit. Openbox S9, Prof7500, v4l-updatelee linux drivers installed.
Richard

Registered:
Posts: 36
Reply with quote  #14 
I have a copy thanks Bill and it won't be anytime soon that I have anything worthwhile to contribute to it, unfortunately.
midwestmac

Registered:
Posts: 2,218
Reply with quote  #15 
Quote:
Originally Posted by majortom
do you guys need that repo? It's still there, just set to private...
If someone signs up for their own bitbucket account, and wants to maintain it,
ie pendragon, et al... let me know and I will pass it over to you for maintenance.
Then you can collaborate and do whatever you want with it.


Thanks I started a bitbucket account what now? Do you need to make it public again for me to get it?


__________________
Azbox Ultra, Pansat 2500, Prof7301,Tbs 6925,5980, Genpix 8psk card, Dektec 2137c, Hauppauge 950q
Previous Topic | Next Topic
Print
Reply

Quick Navigation:

Fellow Members, your posts are welcome here! Do not worry about posting everything perfect. Different receivers and LNB's will give you different Frequencies and Symbol Rates. Some set top boxes, PCI cards and USB receivers, Do Not Require all of the same information that others may need. It is not Required to post everything that others may need to tune in a feed. It is just most important to share the find. We can always adjust the Frequency and Symbol Rates and try the various Modulations and FEC's on our own receivers until we get a lock and then give a polite reply with what works for your receiver, as that information might help others as well. We all appreciate the efforts and energy of the Posters!

Thank You for Visiting GOFASTMOTORSPORTS.com - Keep Your Eyes on the Sky and the Track!