Feature #1752
closed
Feature #1738: SCR / Unicable / EN50494
Tvheadend missing EN50494 SCR (aka "Unicable") support
Added by Stefan Seyfried almost 12 years ago.
Updated over 11 years ago.
Description
Tvheadend cannot handle EN50494 SCR setups.
Since I have two dishes installed, one with a SCR LNB and the other with a SCR 2-input matrix, EN50494 support is a must have for me :)
I'm right now in the process of implementing this feature.
I pushed my code to https://github.com/seife/tvheadend
For the implementation, I added a third DiSEqC mode "unicable".
If this is selected, the parameters SCR# (channel, variable uni_scr), Unicable Frequency (the channel's frequency, uni_qrg) and PIN (for protected setups, uni_pin) are given to en50494_setup() which is called instead of diseqc_setup(). The value returned from this function is the Frequency the frontend needs to be set to.
It is debatable if EN50494 counts as a different DiSEqC mode, but it fits quite nicely into the implementation IMVHO.
The web UI bits can probably be done better, but I have almost zero knowledge about web stuff, so somebody else needs to do that :)
I've reworked the setup, now SCR#, Frequency and PIN are configured in the Adapter settings, only the port (which is not often needed anyway) is configured in the satconf screen.
The only thing that's left now is (IMHO) to dynamically show / hide the SCR# / Freq / PIN settings only if unicable is selected, but I don't have the knowledge to do that.
- Status changed from New to Rejected
- Parent task set to #1738
This is a duplicate or #1738.
Adam
Also available in: Atom
PDF