"Satellite config" drop-down menu missing from the "Basic settings" parameters group for one of DVB-S frontends

Hi,

My tuner (Si21662 on Octagon SF4008 set-top box) has two DVB-S frontends. In Tvheadend, I seem to only be able to use the "Satellite config" menu item in the "Basic settings" parameters group of the Configuration->DVB Inputs->TV adapters tab on one of the frontends. The other frontend does not have this option.

I am not sure why this happens and I am also not sure how to properly configure Tvheadend, so that it can utilize more than one DVB-S frontend simultaneously.

Both frontends are connected to the same dual output LNB. One frontend is connected via USALS rotor, the other is connected directly. I would like to achieve the state where frontend 0 is used to rotate the dish and fetch the first transponder, while frontend 1 is used to fetch one extra transponder from the same satellite when frontend 0 is occupied.

The current state is that frontend 0 works fine, including turning the dish using USALS. But it is only able to tune in one transponder at a time, obviously. The second frontend is enabled, but Tvheadend does not seem to be using it. When I would like to watch a channel from a different transponder (on the same satellite), Tvheadend logs a message saying "No input source available" and then "No free adapter". Maybe it has something to do with the missing "Satellite config" drop-down menu, but I am not sure how to resolve it.

Can someone help by explaining how to configure Tvheadend, so that it could utilize both frontends?

Thank you.

tvheadend-frontend0.png (142 KB) tvheadend-frontend0.png	frontend 0 (/dev/dvb/adapter0/frontend0)
tvheadend-frontend1.png (133 KB) tvheadend-frontend1.png	frontend 1 (/dev/dvb/adapter0/frontend1)

Replies (4)

RE: "Satellite config" drop-down menu missing from the "Basic settings" parameters group for one of DVB-S frontends - Added by saen acro over 6 years ago

There is only one adapter on image
Is second one is released?

I use Octagon SF1028p with in past come with wrong tvh config with hide second tunner
http://www.hdmedia-universe.com/board/showthread.php?9205-Audioniek-git-Tvheadend (post 94)

RE: "Satellite config" drop-down menu missing from the "Basic settings" parameters group for one of DVB-S frontends - Added by Peter Bašista over 6 years ago

Hi,

thanks for the reply, but in my case there is only one adapter, which has multiple frontends. As I have explained before, all the frontends are visible to Tvheadend, but it was unable to utilize the second DVB-S one.

I have tried to resolve the situation by manually updating the adapters configuration file at ~/.hts/tvheadend/input/linuxdvb/adapters/__some__hash__. I have probably done it incorrectly, because after Tvheadend was restarted, my adapter settings were reset. The content of the configuration file has also been rewritten to the default values.

So, I have tried to manually update the configuration from the web UI again and this time I was able to use the "Satellite config" drop-down menu for both frontends. It seems like the issue was caused by some weird internal state of Tvheadend, which prevented the second frontend from being configurable. After the adapter configuration has been reset, it started to behave normally.

tvheadend-frontend1-after-config-reset.png (146 KB) tvheadend-frontend1-after-config-reset.png

frontend 1 (/dev/dvb/adapter0/frontend1)

RE: "Satellite config" drop-down menu missing from the "Basic settings" parameters group for one of DVB-S frontends - Added by saen acro over 6 years ago

Editing config files is pointless after restart they are regenerated

ls /dev/dvb

what is result?
What image you use

RE: "Satellite config" drop-down menu missing from the "Basic settings" parameters group for one of DVB-S frontends - Added by Peter Bašista over 6 years ago

saen acro wrote:

Editing config files is pointless after restart they are regenerated

That is not true. You can edit anything you like and as long as you keep the valid format of the data, including the hash-based references, your changes will be preserved.

The DVB devices are irrelevant for my particular issue. The problem was with a weird state of Tvheadend, not with the underlying DVB stack.

As I have stated before, after the configuration files have been regenerated, the issue has disappeared. Not sure why.

(1-4/4)

Project

General

Profile

Tvheadend