Tvheadend

... and before anyone asks: yes I pressed save for the configs ;-)

I'm having exactly the same problem with almost the same configuration and there are a few other tickets regarding this topic that have been opened in the past without closure.

I'm really crossing my fingers that the devs will have an eye on this issue somewhere soon. I'm still sticking to the seife's branch even if I'm having some stability issues and tuning problems, but I'd like to get my hands on some of the new features that have been implemented since then.

Kind regards,

Tim

I'm not alone, that's fine :)
I tried also seife's build, but I could not compile it under Ubuntu 14.04 so that I have to use github build ...

I dont want to use outdated Ubuntu 13 just to have it working in some way.

I found also tickets that the devs do not have an unicable system for their own, that makes the development further more a long time task... But hope dies last :)

No, you are not the only one!

The unicable configuration itself doesn't seem to be the problem as it works once it is set up. the problem that we are experiencing is caused by the fact, that tvh doesn't save these settings properly and we have to start over after a reboot or service restart. i think this could be checked even without the necessity of an available unicable installation because the frequencies for each unicable tuner are gone after every restart and this needs to be fixed.

but i guess i'm not the only one willing to test new versions to check if a fix was successful or not.

Yes, I would test this fix too... immediately! :)

Are you also from germany Tim? Let us stay in contact concerning unicable setup.

Could you try recent version v3.9-1121 or above ? This http://bit.ly/1tBS60c commit should fix it..

sadly, the current commit (HTS Tvheadend version 3.9.1133~g4bf8754) doesn't work for me as a fix for my unicable issues.

I don't know if I'm doing something wrong, but after switching to 'unicable' in adapter settings 'sat-config' plus an additional 'save' and then finally editing the basic settings (ID, Freq, Network, no Pin) at 'unicable switch' (network has been set up already) plus a final 'save' nothing happens.
Neither mux discovery, nor network. after restarting tvh the basic settings 'ID' and 'Freq' are set again to '0' so i guess it wasn't stored correctly in first place and no muxes could have been discovered anyway.

maybe kai can reproduce my issues too.

checking dmesg tells me too, that the frequencies are not stored correctly, because the network/mux discovery is causing this messages

[ 594.425963] ngene 0000:01:00.0: DVB: adapter 1 frontend 0 frequency 0 out of range (950000..2150000)
[ 594.483080] ngene 0000:01:00.0: DVB: adapter 0 frontend 0 frequency 0 out of range (950000..2150000)
[ 854.543462] ngene 0000:01:00.0: DVB: adapter 1 frontend 0 frequency 0 out of range (950000..2150000)
[ 854.600601] ngene 0000:01:00.0: DVB: adapter 0 frontend 0 frequency 0 out of range (950000..2150000)
[ 950.475159] ngene 0000:01:00.0: DVB: adapter 1 frontend 0 frequency 0 out of range (950000..2150000)
[ 950.532193] ngene 0000:01:00.0: DVB: adapter 0 frontend 0 frequency 0 out of range (950000..2150000)

plus the tvh debug output

linuxdvb: STV090x Multistandard : DVB-S #0 - failed to tune [e=Invalid argument]

sadly it is as Tim said, still not working.

After restart of tvheadend, tvheadend displays following lines (here just some of them)
2014-08-03 12:18:06.912 [ INFO] mpegts: 11992H in ASTRA 19.2E 1 - tuning on STV090x Multistandard : DVB-S #0
2014-08-03 12:18:08.374 [ ERROR] linuxdvb: STV090x Multistandard : DVB-S #0 - failed to tune [e=Das Argument ist ungültig]
2014-08-03 12:18:08.374 [WARNING] mpegts: 11992H in ASTRA 19.2E 1 - failed to start on STV090x Multistandard : DVB-S #0, try another
2014-08-03 12:18:08.375 [ INFO] mpegts: 11479V in ASTRA 19.2E 1 - tuning on STV090x Multistandard : DVB-S #0
2014-08-03 12:18:12.972 [ ERROR] linuxdvb: STV090x Multistandard : DVB-S #0 - failed to tune [e=Das Argument ist ungültig]
2014-08-03 12:18:12.972 [WARNING] mpegts: 11479V in ASTRA 19.2E 1 - failed to start on STV090x Multistandard : DVB-S #0, try another
2014-08-03 12:18:12.972 [ INFO] mpegts: 10758V in ASTRA 19.2E 1 - tuning on STV090x Multistandard : DVB-S #0
2014-08-03 12:18:14.178 [ ERROR] linuxdvb: STV090x Multistandard : DVB-S #0 - failed to tune [e=Das Argument ist ungültig]
2014-08-03 12:18:14.178 [WARNING] mpegts: 10758V in ASTRA 19.2E 1 - failed to start on STV090x Multistandard : DVB-S #0, try another
2014-08-03 12:18:14.179 [ INFO] mpegts: 12692H in ASTRA 19.2E 1 - tuning on STV090x Multistandard : DVB-S #0
2014-08-03 12:18:15.356 [ ERROR] linuxdvb: STV090x Multistandard : DVB-S #0 - failed to tune [e=Das Argument ist ungültig]
2014-08-03 12:18:15.356 [WARNING] mpegts: 12692H in ASTRA 19.2E 1 - failed to start on STV090x Multistandard : DVB-S #0, try another
2014-08-03 12:18:15.356 [ INFO] mpegts: 11523H in ASTRA 19.2E 1 - tuning on STV090x Multistandard : DVB-S #0
2014-08-03 12:18:17.768 [ ERROR] linuxdvb: STV090x Multistandard : DVB-S #0 - failed to tune [e=Das Argument ist ungültig]
2014-08-03 12:18:17.768 [WARNING] mpegts: 11523H in ASTRA 19.2E 1 - failed to start on STV090x Multistandard : DVB-S #0, try another
2014-08-03 12:18:17.768 [ INFO] mpegts: 11332H in ASTRA 19.2E 1 - tuning on STV090x Multistandard : DVB-S #0
2014-08-03 12:18:18.978 [ ERROR] linuxdvb: STV090x Multistandard : DVB-S #0 - failed to tune [e=Das Argument ist ungültig]
2014-08-03 12:18:18.979 [WARNING] mpegts: 11332H in ASTRA 19.2E 1 - failed to start on STV090x Multistandard : DVB-S #0, try another
2014-08-03 12:18:18.979 [ INFO] mpegts: 12662H in ASTRA 19.2E 1 - tuning on STV090x Multistandard : DVB-S #0
2014-08-03 12:18:19.711 [ ERROR] linuxdvb: STV090x Multistandard : DVB-S #0 - failed to tune [e=Das Argument ist ungültig]

This is the first sign that the config I made wasn't saved correctly. Now I took a look into the web interface and yes... old configuration lost.

If you need further input from us - just ask.

Many thanks + Best
Kai

Hey Christian,

Before applying the patch I updated the whole tvheadend source to the current github version.

I don't understand the difference between these patches. They aren't different if I am correct? The contents do not look different in any way.
I applied the 1st patch by calling "patch -p0 < patchfile" within the tvheadend directory, where I downloaded the patch.

But still nothing changes for me. the configuration is not saved or cannot be parsed (don't know exactly what is broken). After restart of tvheadend, the network dropdown list is now even empty for my adapter.
Many thanks again for your help Christian in this case.

Best Kai

Sorry for my mistake, after a 2nd restart of tvh, the network list is now available.
But the original Problem still exists.

Ticket can be closed - my fault... had a bad day and forgot to trigger ./make ;o)
many thanks christian, good job - this patch may get pushed to github.

Please do push it to github, once it's been accepted into master I can mark this as fixed! :)

Thanks for testing - I've submitted a pull request:

https://github.com/tvheadend/tvheadend/pull/457

Christian Brunner wrote:

Thanks for testing - I've submitted a pull request:

https://github.com/tvheadend/tvheadend/pull/457

There is still something wrong with this patch (or tvheadend in general)... In advanced setup mode unicable gets selected even though it has not been touched, only switch. Also I could still not tune unicable in through a switch nor turn a motor in a unicable setup. Works on an enigma2 box.

DVB-S/S2 USB TVHEADEND PC -- diseqc switch --- AA -> LNB1 | |- AB --- |
DC POWER SWITCH -> USALS ROTOR -> UNICABLE LNB |
ENIGMA2 BOX1-- DC POWER SWITCH - ENIGMA2 BOX2

My ASSCI setup got messed up.... I have a setup that uses unicable lnb to some extent. In tvheadend I use unicable freq 1210
DVB-S/S2 USB TVHEADEND PC --> to an two port diseqc switch --- port AA > LNB1
DVB-S/S2 USB TVHEADEND PC -> to an two port diseqc switch --- port AB > DC POWER SWITCH1 2X1 DC IN1> USALS ROTOR > UNICABLE LNB
DC POWER SWITCH1 2X1 DC IN2 --> DC POWER SWITCH2 2X1 DC IN1 - ENIGMA2 BOX1 unicable 1680
DC POWER SWITCH1 2X1 DC IN2 ---> DC POWER SWITCH2 2X1 DC IN2 - ENIGMA2 BOX2 unicable 1420

The motor can be turned by one of the unicable setups at a time. However it does not work in tvheadend.

Note: The sequence for the sat config in tvh is:

1) switch (if rotor present)
2) rotor (if present)
3) switch
4) unicable
5) LNB

If you have any other issues, please, create another report with detailed diseqc trace...