Unicable / Satellite Channel Router / DIN EN 50494

[twoof7@…]

The Patch is providing the Unicable (DIN EN 50494) support for MythTV.

It is based on a kernel patch (​http://www.mythtvtalk.com/unicable-scr-din-en-50494-a-14103/), which will not be integrated into the kernel. In addition I am using some bug fixing from a VDR patch (​http://www.vdr-portal.de/index.php?page=Thread&threadid=89731).

The .patch file will extend the DiSEqCDevLNB class (only), to implement the functional parts of the Unicable support.

The necessary configuration of userband ID, userband frequency, satellite position and PIN can be done within the mythtv-setup's "LNB Configuration" with LNB Preset "Custom" and LNB Type "Unicable / SCR". One open issue is the LNBSCRUserBandSetting inheriting from class SpinBoxSetting?, which can not be disabled by its setEnabled(false).

I know that the user interface for configuration is not yet perfect. But I first like to get your feedback whether the functional parts of this patch are acceptable, or whether it is better to add e.g. a new class DiSEqCDevSCR inheriting directly from class DiSEqCDevDevice (like DiSEqCDevSwitch, DiSEqCDevRotor and DiSEqCDevLNB).

The .sql file will add some columns to database "mythconverg" table "diseqc_tree" to store the configuration parameters.

The patch was tested with a Inverto IDLB-QUDL41-UNI2L-1PP (​http://www.inverto.tv/products/product.php?section=1&id=160&cat=6).

[twoof7@…]

Minor bugfixing.

[twoof7@…]

I found a small error causing the unicable implementation to send the DiSEqC command twice. Because the parameter "repeats" of the function call "m_tree.SendCommand?(...)" (file "diseqc.cpp", line 2394) was set to "1" instead of "0". Please see corrected patch "0002-libmythtv-Unicable-SCR-DIN-EN-50494.patch".

[twoof7@…]

Rewritten Unicable support incl. UI for configuration

[twoof7@…]

Rewritten Unicable support incl. GUI for configuration (new sql)

[twoof7@…]

The rewritten Unicable support "0003-libmythtv-Unicable-SCR-DIN-EN-50494.patch" is also providing a UI dialog to configure necessary parameters (userband ID, userband frequency, PIN code). The satellite position (column "scr_position") was removed from table "diseqc_tree" (see new .sql file). It will be stored as setting within table "diseqc_config". The patch is now functional complete.

Configuration within "mythtv-setup":

1. configure "Capture cards" => "New capture card"

=> select card type "DVB DTV capture card (v3.x)" => press "DiSEqC (Switch, LNB, and Rotor Configuration"

=> press enter and select "Unicable" within dialog "Select Type of Device"

=> configure "Userband", "Frequency" and "PIN code" => select "Finish"

=> select "(Unconnected)"

=> select "LNB" within dialog "Select Type of Device"

=> use preset "Universal (Europe)" => press "Finish"

=> press key "ESC"

=> press "Finish"

=> press key "ESC"

=> press key "ESC"

2. configure "Video source" ...
3. configure "Input connections" => select respective "[DVB: /dev/dvb/adapterX/frontendX] New Input"

=> configure "Position" (A/B) => press "Next>" ...

Regards, twoofseven

[cvb@…]

I would be very interested in this patch. Are there plans to include it into the next mythtv version?

[twoof7@…]

I haven't got any feedback from other developers so far. Therefore I don't know whether this patch will be included into the next mythtv version.

[sphery]

Oops, misfiled. Stuart A, is this something you might be able to handle?

[stefano-rossi@…]

How can I apply this patch to my Mythbuntu? I have an unicable dish and a Technisat usb hd...

Thanks Stefano Italy

[twoof7@…]

You need to manually build MythTV as described at http://www.mythtv.org/docs/mythtv-HOWTO.html#toc5.2 . Before invoking ./configure you need to patch the source code:

$ patch -p1 < 0003-libmythtv-Unicable-SCR-DIN-EN-50494.patch

After installing MythTV it is necessary to manually add additional columns to table "diseqc_tree" within MythTV database "mythconverg". Therefore I prepared the following SQL statement (see file "mythconverg_diseqc_tree_SCR.2.sql"), which should be executed within the MySQL browser of your choice:

ALTER TABLE `mythconverg`.`diseqc_tree` ADD COLUMN `scr_userband` INTEGER UNSIGNED NOT NULL DEFAULT 0 AFTER `address`,
 ADD COLUMN `scr_frequency` INTEGER UNSIGNED NOT NULL DEFAULT 1400 AFTER `scr_userband`,
 ADD COLUMN `scr_pin` INTEGER  NOT NULL DEFAULT '-1' AFTER `scr_frequency`;

Please see comment 2 for configuration within mythtv-setup.

twoofseven

[dekarl@…]

Stefano, for Mythbuntu with a patch see "Patching and building from source" at ​http://www.mythbuntu.org/wiki/recipes

[stefano-rossi@…]

Replying to dekarl@…:

Stefano, for Mythbuntu with a patch see "Patching and building from source" at ​http://www.mythbuntu.org/wiki/recipes

Thanks, but "get-build-deps" had been removed from "ubuntu-dev-tools" so I can't get dependencies...

Stefano

[Shinck@…]

Adapted patch for unicable support with configuration for use with 0.25/fixes

[Shinck@…]

I've adapted the patch to work with 0.25/fixes builds. The logging from 0.24 to 0.25 was altered and uses now the LOG procedure instead of VERBOSE.

It would be great if this could be included in the next version because I think other user also suffers from unicable support.

Unicable installations are extremely helpful, if you use a backend with multiple tuner cards (or twin-tuners) because of the need of only one cable from the existing installation to the backend server (no altering of existing installation, only switch the LNB to a Unicable one)

Regards, Sascha

[warpme@…]

Hi, It's great that mythtv can support Unicable. I patched current 0.25-fixes, compile and start to test Unicable on my system. Unfortunately this patch causes BE segfault when system has any DVB card declared as non-unicable (when all DVB tuners are declared as unicable) - no segfaults. As I have DVB-T & DVB-S tuners and want to use unifiable - current verssion of patch is impossible to use. Backtrace from segfault attached.

[warpme@…]

be segfault trace with mixed unable & non-unicable cards

[warpme@…]

be segfault full trace with mixed unable & non-unicable cards

[Shinck@…]

Hi warpme,

I've also mixed tunercards, one dvb-t and two dvb-s/s2 and the dvb-s-cards are on Unicable configuration - no segfaults at all. But I looked over your segfault traces and figured out that there is a erroneous frequency-calculation if at least one DVB-S Tuner is on normal LNB-configuration.

So with some hacking of the database I could also reproduce the segfault on my system and providing a fix for stability.

I've attached it. Please check if this also fixes the segfault-issue on your system.

Regards, Sascha

[Shinck@…]

Fix against sefault if one or more DVB-S tuner cards are on LNB-configuration and don't use Unicable

[warpme@…]

Sascha, thx for fix. (infact I was suspecting that issue is in checking: when tuning freq. should be scr and when original. Previous patch does it for any LNB while it should be done only for LNB associated with SCR). I'm attaching slightly modified patch. Changes are: 1\ UserBandID higher than 7 now is not exiting tuning but prints info that ID is out of standard range. It is required for Unicable converters which are not meeting standard (i.e. mine Inverto IDLP-40UNIQD+S has following mapping: 1210->ID=3; 1420->ID=1; 1680->ID=8; 2040-ID=10). 2\For SCR tuners, tuning info has logging category "general" as it helps to routinely monitor SCR operation without spamming BE log with massive "channel" logging entries; 3\I extend some mythtv-setup screens help. It might hint users about most popular UserBand? frequencies; 4\ID spin box has 0-8 boundaries as some systems have 1-8 numbering instead of 0-7.

Thx again for You contribution to Unicable. It is wonderful technology and I still hope someday it will find official place in mythtv...

[warpme@…]

v6 of patch with cosmetic changes

[dekarl@…]

Can you confirm that the numbering 1-8 vs. 0-7 is not simply different labels for the same values?

Googling around I read that the scr id has 3 bits which allows 8 distinct values. Either zero based 0-7 (called scr id) which can also be used one based as 1-8 (called channel number) (taken from this unicable faq ​http://www.hifi-forum.de/viewthread-97-13287.html ) Either way its very strange to see an id 10.

According to the patch m_scr_userband has valid values 0-7, too.

unsigned char data[3];
data[0] = t >> 8 | m_scr_userband << 5;

The guide for Inverto IDLB-QUDL41-UNI2L-1PP (what the OP tested with) the also hints at it (noticed that channel 1 maps to scr 0 and so on)

Output IF Channel 1 (SCR0) 1210 MHz

with the current patch the id gets truncated to 3 bits and you get id 0 when you enter 8 and 2 when you enter 10.

Your id -> frequency map should look like this

1680 MHz, ID=8;  really id 0
1420 MHz, ID=1;  really id 1
2040 MHz, ID=10; really id 2
1210 MHz, ID=3;  really id 3

that matches what is documented at ​http://www.doebis.de/sites/lnbs/lnbs_datenpdfs/inverto_idlp_40uniqd.pdf

[warpme@…]

Right. It's Friday and I had some time to look on thing more closely. You are right. I went to wrong conclusions probably because in test system I have 2 new things: new tuners (new 2xDVBS Satix tuner) & SCR. Probably real issues with tuner I qualified as wrong SCR ID with this tuner. Today I launch test system again and do some tests. Log:

2012-07-13 18:01:36.525019 I  SCR: Tuning to 11393000kHz, LoBand, V using UB=10, FREQ=2040MHz, POS=A
2012-07-13 18:01:36.525019 I  DiSEqCDevTree: Changing LNB voltage to 18V
2012-07-13 18:01:36.626783 I  DiSEqCDevTree: Sending DiSEqC Command: e0 10 5a 42 3b

2012-07-13 18:06:44.877051 I  SCR: Tuning to 11393000kHz, LoBand, V using UB=2, FREQ=2040MHz, POS=A
2012-07-13 18:06:44.877102 I  DiSEqCDevTree: Changing LNB voltage to 18V
2012-07-13 18:06:44.978281 I  DiSEqCDevTree: Sending DiSEqC Command: e0 10 5a 42 3b 

2012-07-13 18:03:46.945920 I  SCR: Tuning to 11393000kHz, LoBand, V using UB=8, FREQ=1680MHz, POS=A
2012-07-13 18:03:46.945928 I  DiSEqCDevTree: Changing LNB voltage to 18V
2012-07-13 18:03:47.046916 I  DiSEqCDevTree: Sending DiSEqC Command: e0 10 5a  1 e1

2012-07-13 18:15:19.481170 I  SCR: Tuning to 11393000kHz, LoBand, V using UB=0, FREQ=1680MHz, POS=A
2012-07-13 18:15:19.481180 I  DiSEqCDevTree: Changing LNB voltage to 18V
2012-07-13 18:15:19.582110 I  DiSEqCDevTree: Sending DiSEqC Command: e0 10 5a  1 e1

DIsec commands are the same for ID 2 & 10. Not strange looking on code. Sorry for confusion ! For consistency I uploading v7 patch with cosmetic corrections in setup screen hints. -br

[warpme@…]

v7 with minor corrections in setup screen hints

[warpme@…]

FYI: As in Unicable Diseqc commands are directly impacting demodulator PLL lock, for some (less tolerant) demodulators ticket #10997 seems to be needed. With #10997 I have Unicable in mythtv with production quality. (I'm using it 4 weeks, +600 recordings, and had 5 or so wrong mplex tunes. I think Unicable support is stable enough to integrate it into mythtv main code.

[warpme@…]

This patch makes sure reset disecq bus only once if SCR system is used. Originally disecq.cpp does disecq microcontroler reset (e0 00 00) for every phy card. So there is situation where card1 does reset diseq, set LNB_SCR_VCO1, next, card2 does reset diseq, set LNB_SCR_VCO2, etc. As disecq microcontroller at LNB is shared, there is potential issue as next disecq microcontroller reset impacts previous LNB_SCR_VCOx setting. Issue can manifest when i.e LiveTV last channel is the same like starting channel in DB and #10997 is applied. In such case user can experience issues with first launch of LiveTV after BE start on all tuners except last one. Attached patch makes sure disecq microcontroler reset (e0 00 00) is sent only once for SCR disecq busses. For non-SCR disecq busses, disecq microcontroler reset behavior is unchanged.

[warpme@…]

reset disecq only once for SCR busses

[warpme@…]

This patch resolves issue with some SCR converters which have wrong/missing implementation of Disecq command repeat (i.e. OP Inverto IDLB-QUDL41-UNI2L-1PP). My system has 0.7-0.8% error Disecq bus rate. With attached patch and setting resend=1 (repeat=11) I haven't yet SCR Disecq error for so far 1300 tunings.

[warpme@…]

Add Disecq command resend

[dekarl@…]

Some questions after looking at 0037-mythtv-0.26-resend_disecq_cmds.patch​

What happens if the setting is exactly 10?

Why can you repeat 9 times but only resend 5 times?

Wouldn't it be easier to understand with separate settings for separate concerns? e.g. repeat_count and repeat_mode/_kind instead of the <10 or >10 kludge

[warpme@…]

dekarl, Pls see replay on [hxxp://www.gossamer-threads.com/lists/mythtv/dev/529920#529920]

[warpme@…]

Per requests I prepared single consolidated patch against current 0.26-fixes. I includes:

-0007-libmythtv-Unicable-SCR-DIN-EN-50494.patch,

-0029-mythtv-0.26-reset_diseqc_bus_only_once_v4.patch​,

-0037-mythtv-0.26-resend_disecq_cmds.patch,

-patch from #10997

-some cosmetic changes in logging helping to monitor Unicable operation.

BTW: Pls remember: enabling Unicable requires this patch + change in DB (You have to apply mythconverg_diseqc_tree_SCR.sql from this ticket).

[warpme@…]

Single consolidated patch for Unicable in 0.26-fixes

[warpme@…]

I had temp. problem with Internet connection, so by mistake I uploaded twice. (mythtv-0.26-unicable_all_patches_consolidated.patch​ and mythtv-0.26-unicable_all_patches_consolidated.2.patch). Both are identical. I don't know how can I delete already uploaded file in trac...

[Karl Egly]

Find a PPA for fixes/0.26 on Ubuntu 12.04 LTS including the consolidated patch at ​https://launchpad.net/~dekarl/+archive/mythtv-unicable.

Please note that you need to manually add (and remove later!) the schema changes from mythconverg_diseqc_tree_SCR.2.sql​. Also note that enabling this PPA and the Mythbuntu nightly will likely give you a newer version but without the patch.

[t.kistler@…]

Hi all,

Here is my feedback: I am running mytht-0.26-fixes with a Turbosight TBS6991 receiver and a Technisat Technirouter Mini. The mythtv-0.26-unicable_all_patches_consolidated.2.patch gives me a signal strength of about 50% (normally above 75) and no lock. I tried with repeats 0,1,5,10,11 and 15. If I apply only 0007-libmythtv-Unicable-SCR-DIN-EN-50494.patch, then I do get a Lock and reception (Channel scanning under Unicable does not work for me).

Thank you for your efforts. Regards, Toni

[warpme@…]

@t.kistler: may You do me favour and try incrementally add list of patches in order from comment #22?. Pls start with 0007, then add 0029, etc - do it pls until You stop getting lock. For speedup tuning process I implemented one cosmetic change in Unicable protocol and I want to be sure it isn't causing Yours problems....

[t.kistler@…]

Replying to warpme@…:

@t.kistler: may You do me favour and try incrementally add list of patches in order from comment #22?. Pls start with 0007, then add 0029, etc - do it pls until You stop getting lock. For speedup tuning process I implemented one cosmetic change in Unicable protocol and I want to be sure it isn't causing Yours problems....

@warpme: Installed patches 0007,0029,0037 and 0028-mythtv-0.25-dont_send_diseq_if_tuning_to_the_same_transponder.patch. System has still lock and I can even scan channels in mythtv-setup

[warpme@…]

@t.kistler: thx for your time spent on this ticket & sorry for hassle. 0007,0028,0028,0037 are attempt to support unicable without enhancements for tuning speed-up which are running OK on my Uni-LNB but small violation seems to be problem for some very strict implementations of disecq protocol.

@dkarl: pls find consolidated mythtv-0.26-unicable_all_patches_consolidated.3.patch which is 0007,0028,0028,0037 in single shot. Sorry for additional work with creating new ppa...

[warpme@…]

0007,0028,00028,0037 in single patch

[Karl Egly]

the PPA at ​https://launchpad.net/~dekarl/+archive/mythtv-unicable has been updated (no worries, the update takes little manual effort once its first setup, its mostly waiting)

[k_straussberger@…]

I ported the patch to 0.27

[k_straussberger@…]

The 0.27 patch in running since 4 weeks with Digital Devices CineS2 6.5 in a 4-head configuraton with a DouFlex? S2 and Inverto IDLB-QUDL42-UNI2L-1PP (settings can be taken from: ​http://www.inverto.tv/products/product.php?section=1&id=160&cat=6)

[haarman@…]

The PPA still contains the old version. If it can be done easily can you update the PPA to saucy?

[Karl Egly]

The PPA has been extended to Saucy and an update for Precise is now in the build queue, too.

[sonderfeld@…]

Dear all, I applied the 0.27 patch to the 0.27 mythtv version. I was able to configure the unicable settings as described above. I use the Digital Devices CineS2 5.5 and the Inverto Unicable LNB. Unfortunatly mythbackend is not able to tune correctly. The error message looks like this: DVBChan[11](/dev/dvb/adapter1/frontend0): Opening DVB frontend device failed. eno: Device or resource busy (16)

The operation with the legacy LNB connection works properly. What might be my problem with the unicable option?

[k_straussberger@…]

Hi, the configuration depends highly on your type of LNB. Which one do you have?

Also the version of the Linux driver package is relevant. Did you download and compile from ​http://linuxtv.org/hg/~endriss/media_build_experimental/?

Just make sure no other dvb processes are active and require the resource!

Happy new year

[sonderfeld@…]

Thanks for your reply and also happy new year to you guys. I am using the LNB Dur-Line UK 102. I made sure that I connected to the unicable port.

I am currently using the 3.2.0-57-generic #87-Ubuntu SMP Tue Nov 12 21:35:10 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux

version of Linux. Not sure if the driver you mentioned is loaded.

I thought that the recent ubuntu versions carry already sufficient drivers for the Dur-Line LNB. But if not, I am willing to replace it by a development version. How can I check which kind of driver is installed in my current set-up? The link you provided creates some confusion on my side which kind of file I should use for a manual build and make procedure? Can someone assist here? Thanks in advance for any kind of help since I would very much appreciate to use the unicable port instead of the old legacy one!

[k_straussberger@…]

Your current version can be found in "modinfo ddbridge" (I see 0.9.9 with srcversion 4E5D0F16E9FC52D35C8FFFB)

Well I'm not sure about the Ubuntu/Linux? driver versions but anyhow the newer the better. There is a pretty good instruction how to install the drivers under ​http://www.vdr-portal.de/board18-vdr-hardware/board102-dvb-karten/113367-aktuelle-treiber-f%C3%BCr-octopus-ddbridge-cines2-ngene-ddbridge-duoflex-s2-duoflex-ct-cinect-sowie-tt-s2-6400-teil-2/ (well it's in German, but the commands are not NLS sensitive).

The next thing that is really troublesome is the setup for the LNB: Matching Userband-Frequency mappings can be found in the users manual of your LNB (or somewhere online: ​http://www.xmediasat.com/shop/artikel/XM27418.php in the picture).

Another thing I figured out right now, is the topic of firmware, which you may need (details can also be found on the German driver page above)

[haarman@…]

You can check if scanning and your hardware is working by using w_scan ​http://wirbel.htpc-forum.de/w_scan/index2.html ​http://wirbel.htpc-forum.de/w_scan/w_scan-20140102.tar.bz2

for Sat 28.2 east, Channel-ID 0, User Frequency 1400 MHz on Satellite Position A: w_scan -fs -s S28E2 -u 0:1400:A

[sonderfeld@…]

Dear all, thanks for the hints. Unfortunately, when I tried to update to the latest Digital Devices driver as outlined under the link above the final "make" procedure aborts with the following error message:

make[2]: Leaving directory `/usr/src/linux-headers-3.2.0-57-generic' ./scripts/rmmod.pl check Can't locate Proc/ProcessTable?.pm in @INC (@INC contains: /etc/perl /usr/local/lib/perl/5.14.2 /usr/local/share/perl/5.14.2 /usr/lib/perl5 /usr/share/perl5 /usr/lib/perl/5.14 /usr/share/perl/5.14 /usr/local/lib/site_perl .) at ./scripts/rmmod.pl line 4. BEGIN failed--compilation aborted at ./scripts/rmmod.pl line 4. make[1]: * [default] Error 2 make[1]: Leaving directory `/home/smartbox/mythtv/media_build_experimental/v4l' make: * [all] Error 2

I am not sure if I can do anything about this error message or if this needs a fix in the driver installation files. Maybe there is an update on the market that I should use. Maybe I contact Digital Devices directly on it.

I will also try to play around with the w_scan (at least the LNB is definitly working with the legacy port) but I am not sure if I will find the right paramters to test unicable with w_scan.

Regarding the Userband Frequency, I already had compared it for the Dur-Line UK 102 with the above mentioned table. Looks like the same settings unless there is something important regarding the sequence of the different frequencies.

If I make any progress, I will post my findings in this forum.

[haarman@…]

try:

sudo apt-get install libproc-processtable-perl

[haarman@…]

Replying to sonderfeld@…:

I will also try to play around with the w_scan (at least the LNB is definitly working with the legacy port) but I am not sure if I will find the right paramters to test unicable with w_scan.

As said I my previous reply:

for Sat 28.2 east, Channel-ID 0, User Frequency 1400 MHz on Satellite Position A: w_scan -fs -s S28E2 -u 0:1400:A

I suppose the 0 is the userband, 1400 the frequency and the A the satellite position ;-). The only other parameter is the satellite you want to scan (in this case S28E2). If you need to specify the adapter use -a N

[Kenni Lund [kenni a kelu dot dk]]

Guys, please continue this discussion on the mythtv-users mailing list. This is a bug tracker, not a support forum.

[haarman@…]

I added the ppa and applied the sql changes and was still able to watch satellite over the legacy ports (so standard diseqc behaviour). Then I switched to unicable and that now also works like a charm.

using: Dual satellite cascadable Unicable switch with 8 User bands IDLP-USS2OO-CUO1O-8PP ​http://www.inverto.tv/products/product.php?section=49&id=161&cat=83

[Karl Dietz <dekarl@…>]

In feabd4ed12fd10a7e2482a52df0eb0165b540be8/mythtv:

Add new columns for Unicable related configuration data

Refs #9726

[warpme@…]

Adding ref to #12092 as it can further increase Unicable stability.

[Karl Dietz <dekarl@…>]

In 111a7559fec5f81d7561f46cc10800f47d331b7b/mythtv:

Add support for Unicable / Satellite Channel Router / DIN EN 50494

Our loyal user base has kept this feature patch alive since fixes/0.24
and its been reported as being (rock) solid by multiple users which
also performed regression tests against plain-old-DVB-S setups.

Patch by Matthias Benesch
With additions by Shinck and warpme
updated by k_straussberger

Fixes #9726
Fixes #10997

[tilman.wagner@…]

In Myth-Backend-Setup the section "Capture Cards" appears to only allow to connect to either a switch or probably a unicable LNB, not a unicable switch. I have two universal LNB connected to a multiswitch. When receive the signal from a single multiswitch output MythTV works fine.

However, when physically adding a unicable multiswitch (Spaun SUS 21 F) by connecting it to two outputs of the same primary multiswitch then within "DiSEqC (Switch-, LNB-, and Rotor-Configuration)" I can select Unicable, then the multiswitch in front of it with two sources, each of which I select as Universal LNB:

Unicable

Switch

LNB

LNB

But when trying to save this it resets the DiSEqC Configuration to Unconnected.

I have installed this unicable patch in MythTV 0.27 under Ubuntu 14.04 (trusty).

[haarman@…]

Replying to tilman.wagner@…:

However, when physically adding a unicable multiswitch (Spaun SUS 21 F) by connecting it to two outputs of the same primary multiswitch then within "DiSEqC (Switch-, LNB-, and Rotor-Configuration)" I can select Unicable, then the multiswitch in front of it with two sources, each of which I select as Universal LNB:

Unicable

Switch

LNB

LNB

Try:

Unicable

LNB

instead. I then can select the 2 (A/B) switch positions when selecting the actual inputs. I use 0.28 though.

[tilman.wagner@…]

Thank you for your suggestion, I checked it again:

When I select Unicable I can then only define one userband (1:1076), there is no place to enter the second userband (2:1178), I can then only define a single LNB for userband 1 underneath Unicable. However the information is not being saved when doing the regular closing of these windows with ESC and CR and sets it back to Unconnected (same as with the Switch).

Since you indicated that MythTV 0.28 may do this correctly I will do a test installation of 0.28, try it there and get back.

[tilman.wagner@…]

Created a test installation of 0.28 by installing 0.27 with the unicable patch enabled and then changing the repository version to 0.28 in the MythTV Control Center. That did not go smoothly and there were errors, the system now does not recognize the tuner cards any more...

Could you suggest a way to create a working MythTV 0.28 test installation with unicable patch included?

[tilman.wagner@…]

The problem I am seeing may be specific to my installation, because it has components from 3 different manufacturers:

Using the very same physical hardware I installed tvheadend on mythbuntu to see if that can correctly address the Spaun SUS 21 F unicable multiswitch. I did not work either, however it does do something different: While with MythTV the switch indicates "orange" (=remote supply voltage > 15 V) with tvheadend it indicates "green" (=remote supply voltage > 15 V) and sometimes "flashing green" (=valid DiSEqC command). In either case it does not find any transponders or channels though.

So the error could be basically anywhere in the communication between the Kathrein LNBs, the Spaun multiswitch, the Spaun unicable switch, or the Technisat Skystar USB HDs DVB-S2 cards. And maybe the MythTV unicable setup cannot be saved just because MythTV checks if the source is valid.

Therefore I am returning the Spaun Unicable components and will now try a different unicable solution with a Onecable Stacker/Destacker? in the DiSEqC enabled version (Manufacturer: Global Invacom). These two boxes completely encapsulate the Unicable path and I should be able to just use standard MythTV without the Unicable patch at the two outputs I will get in my appartment.

[haarman@…]

Hi. I have an inverto idlp-uss200-cu010-8pp unicable multiswitch with two quattro lnb's directly connected to it. I just use the mythbuntu ppa: ​http://ppa.launchpad.net/mythbuntu/0.28/ubuntu (since the patch is included in master)