Project

General

Profile

Forums » General »

Unable to scan or tune on a FBC tuner within VU Plus Uno 4K SE

Added by Peter Bašista over 4 years ago

Hi,

I am trying to use Tvheadend 4.3-1857~g221c29b40 on a VU Plus Uno 4K SE receiver. I have compiled it using this Openembedded recipe.

I am facing an issue where Tvheadend is unable to scan any transponder despite the fact that dvbv5-scan utility can do it successfully. I am attaching logs from scan attempts via both dvbv5-scan and Tvheadend.

Scanning via Tvheadend fails due to a "no data" TIMEOUT.

The DVB adapter itself is supposed to contain a FBC tuner. It has two physical inputs and presents itself as a single DVB adapter with 8 frontends. Is it possible that such a configuration requires some special setup which Tvheadend normally does not do, but dvbv5-scan does?

dvbv5-scan.log (24.9 KB) dvbv5-scan.log Log from scanning via dvbv5-scan
tvheadend.log (3.78 KB) tvheadend.log Log from scanning via Tvheadend

Replies (1)

RE: Unable to scan or tune on a FBC tuner within VU Plus Uno 4K SE - Added by Peter Bašista over 4 years ago

I have tried to use minisatip in combination with Tvheadend on the same machine. I have configured Tvheadend to only use the tuners exposed by minisatip. The result was that scanning and EPG grabbing worked. But continuity errors appeared regularly even when watching unscrambled channels.

However, when I enabled the "RTP/AVP/TCP transport supported" option within the "Advanced settings" group of the minisatip adapter's parameters in Tvheadend, the continuity errors have disappeared and I was able to watch the channels normally. I do not know what this particular setting does and why it influences the occurrence of continuity errors. I have also mentioned it in a discussion about minisatip issue related to FBC tuners.

Afther I had the channels scanned, I have tried to switch back to using Tvheadend directly. The streaming somewhat worked, but with regularly occurring continuity errors. Scanning and EPG grabbing did not work. This behavior resembles an issue that was reportedly fixed within minisatip a while ago.

    (1-1/1)