Project

General

Profile

Problem with version 4.1 : No Initial Scan

Added by Werner Karl over 9 years ago

Hello,

I own a TBS 6985 with 4 dvb-s2 tuners. I must use it with a unicable setup because there is only one cable to the tvheadend server. I tried version 3.4 with a universal lnb setup. This works fine, but I can only usee one channel. Now I tried to find a version with unicable support and found versions 3.9 and 4.1. But, with theses versions, there is no initial scan when I setup the dvb input.

Am I doing something wrong or do others confirm that these versions lack initial scan?

Is there a version that supports unicable and does an initial scan?


Replies (8)

RE: Problem with version 4.1 : No Initial Scan - Added by Werner Karl over 9 years ago

Thank you very much, this is pretty much what I was looking for. However, this is also pretty much how I tried it. But - the initial scan did not start. Maybe result of the bleeding edge nightly build.

Also, I was tired of switching between stable, unstable, beta, utopic etc. apt-get remove --purge , apt-get install etc. turning in circles.

I decided to compile tvheadend myself from git. I use linux for far more than a decade now, so configure/make/make install are well-known. git OTOH is not so familiar. But I'll dig into it. And maybe come back with new questions.

RE: Problem with version 4.1 : No Initial Scan - Added by Gary Brown over 9 years ago

can you show me screenshots of the network screen on your setup.

RE: Problem with version 4.1 : No Initial Scan - Added by Werner Karl over 9 years ago

Unstable version over repo was 4.1.5, git compiled versions were 4.1.12 and 4.1.18 (yesterday). None of them did the initial scan. Scan status shows 'Active' then 'Idle', Result then shows 'Fail'. The hardware and driver setup has not been changed since it worked (including initial scan) on stable Version 3.4 and even on beta Version (3.5?).

Have been very busy last days on my work. Will upload screenshots of network screen etc. shortly, hopefully tonight.

RE: Problem with version 4.1 : No Initial Scan - Added by Werner Karl over 9 years ago

Finally I had time to make the screenshots. Please find them attached.

BTW.: In the Edit Networks dialog, I can select "19.2E:Astra" in the "Pre-defined Muxes" and save, but when I re-open the dialog, the entry reads "Select Pre-defined Muxes" again. OTOH, the "Muxes" page shows the correct entry.

On the "Muxes" page, the "Scan status" reads "IDLE". When I select "Force scan" under "Networks", the "Scan status" goes to "ACTIVE", then after some seconds to "IDLE" and "Scan Result" is "FAIL". The log reads:

2015-05-23 14:50:53.035 mpegts: 12551.5V in Astra - tuning on TurboSight TBS 6985 DVBS/S2 frontend : DVB-S #0
2015-05-23 14:50:53.334 subscription: 0003: "scan" subscribing to mux "12551.5V", weight: 6, adapter: "TurboSight TBS 6985 DVBS/S2 frontend : DVB-S #0", network: "Astra", service: "Raw PID Subscription" 
2015-05-23 14:51:03.000 mpegts: 12551.5V in Astra - scan no data, failed
2015-05-23 14:51:03.000 subscription: 0003: "scan" unsubscribing

RE: Problem with version 4.1 : No Initial Scan - Added by Gary Brown over 9 years ago

ahh Astra 19.2. Then mux on record is no longer used. add the following to a mux manually and

"frequency": 11953500,
"symbol_rate": 27500000,
"fec": "3/4",
"polarisation": "Horizontal",
"modulation": "QPSK",
"delivery_system": "SYS_DVBS",

Also the advanced settings in the adaptor turn off the "tune before diseqc" and "full diseqc" as these are not relevant to your setup.

RE: Problem with version 4.1 : No Initial Scan - Added by Werner Karl over 9 years ago

Ohhhhh, great. That seems to work, great! Thank you for this hint. It finds some services on this particular transponder. Do I have to enter all transponders manually? Why did version 3.4 find all muxes and services on its own?

RE: Problem with version 4.1 : No Initial Scan - Added by Werner Karl over 9 years ago

OK, I have entered the data of a different transponder and deleted the old one. Now the initial scan seems to recognize all transponders, muxes and services. At least, it is scanning right at this moment.

I think, this thread can be considered closed for now.

    (1-8/8)