26 replies to this topic

[labomber]

Hallo Leute,

 

ich habe eine Frage zur Unicable Konfiguration.

 

Zum Setup:

 

Vu Ultimo 4K mit 2x FBC und 1x Legacy . Gigablue Ultra SRC LNB.

 

Astra ist angeschlossen am Tuner I 

 

Tuner I 

userband 1

nicht verbunden 

 

Tuner J 

userband 2

verbunden mit I

 

Tuner K

userband 3

verbunden mit J

 

Tuner L

userband 4

verbunden K

 

Beim Tuner M wollte ich nun user band 5 und verbunden mit L einstellen jedoch geht dieser nur zu verbinden mit A B I oder J.

 

Was mache ich hier falsch? Bitte um Hilfe & Danke!

 

[Abu Baniaz]

You associate/connect to the tuner that has the signal wire.

[labomber]

The signal cable is connect @ Tuner I. The others are configured like this manual https://wiki.vuplus-...ne_Satposition 

 

I can´t connect all Tuners to Tuner I you need to connect J to I, K to L and M to L but this works only until Tuner L. It´s not possible to connect M to L because when I´m trying to do this there are only ABIJ is available.

[Abu Baniaz]

The daisy chaining (connecting to previous tuner, on every tuner) in that wiki page was because of driver issues which have now been fixed. Please ignore that wiki page and use the PLI wiki page.

A,B,I and J are the only tuners that can have a physical connection, this is why they are the only options you have.

Also, you can only connect/associate within the same FBC unit/card/module. So, A-H can only connect to A or B. I-P can only connect to I or J.

Edited by Abu Baniaz, 11 September 2021 - 18:03.

[labomber]

Great it works! Many thx for this.  I will just use from now the PLI wiki page 

[anudanan]

Ja, beim PLI ist das anders, bin ich anfänglich auch dran reingefallen, weil ich das beim vti immer so gelesen hatte. Beim openPLI wird jeder Tuner ohne Anschluss mit dem Tuner verbunden, an dem das Kabel angeschlossen ist. Das ist aus meiner Sicht auch viel logischer als das Verbinden mit dem vorherigen Tuner, wie es beim VTI empfohlen wird und da wohl auch so sein muss.

 

Mir ist allerdings vor der Umstellung auf unicable mit 2 legacy Kabeln an Tuner A und B aufgefallen, dass die automatische Verschaltung der nachgelagerten Tuner (C-H) auch immer mit dem vorherigen passiert und nicht nur mit den Tunern A oder B, an denen die Kabel hängen. Ob das der Treiber so macht oder ob das openpli das macht, kann ich nicht sagen.

 

Für unicable ist das jedenfalls beim openpli die falsche Weg

Edited by anudanan, 13 September 2021 - 18:05.

[littlesat]

Wass vti da macht is nicht richtig…. Das passiert auch nicht…. Man muss Oder mit a Oder b verbinden… (Oder I j). Bei openpli kann Mann Rass configurieren und functioniert richtig… hardware massig zit es klein cascade… c d e f g h werden verbonden mitt a Oder b….  D mit c und dann b usw ist unzinn…

Edited by littlesat, 14 September 2021 - 07:45.

[labomber]

Ich habe nun ein weitere Frage, betrifft auch Unicable daher schreibe ich hier weiter.

 

Setup:

 

4 x Wide Band LNB Inverto

2 x Unicable Multischalter IDLU-UST110-CU010-32P

1 x combiner 2 x Netzteile

 

Multischalter 1 AB Multischalter 2 CD

 

Das ganze geht mit einem Kabel an einen Vu Uno 4K SE

 

Satpositionen

 

A = 19

B = 13

C = 16

D =0.8 

 

Konfiguration:

 

Tuner A:

 

erweitert >

19 Astra >

LNB 1 > 

Auto

SCR Unicable

SCR Unicable Matrix Switch

Inverto

IDLU-UST110-CU010-32P

Userband 1

DiseqC deactivated

Legaqcy deactivated

 

erweitert >

13 Hotbird >

LNB 2 > 

Auto

SCR Unicable

SCR Unicable Matrix Switch

Inverto

IDLU-UST110-CU010-32P

Userband 1

DiseqC deactivated

Legaqcy deactivated

 

erweitert >

0.8 Thor >

LNB 3 > 

Auto

SCR Unicable

SCR Unicable Matrix Switch

Inverto

IDLU-UST110-CU010-32P

Userband 1

DiseqC deactivated

Legaqcy deactivated

 

erweitert >

16 Astra >

LNB 4 > 

Auto

SCR Unicable

SCR Unicable Matrix Switch

Inverto

IDLU-UST110-CU010-32P

Userband 1

DiseqC deactivated

Legaqcy deactivated

 

 

Mit diesen Einstellungen habe ich nur auf Astra einen Signal und komme nicht weiter. 

 

 

Viele Grüße

[labomber]

Solved!

[Frenske]

Solved!

Könntest du mal kurz erklären wie dies gelöst ist damit andere Mitglieder davon lernen können. Danke im voraus.

[labomber]

Falsche Modell vom Multischalter ausgewählt, somit auch falsche Userbänder  .  

[anudanan]

The daisy chaining (connecting to previous tuner, on every tuner) in that wiki page was because of driver issues which have now been fixed. Please ignore that wiki page and use the PLI wiki page. A,B,I and J are the only tuners that can have a physical connection, this is why they are the only options you have. Also, you can only connect/associate within the same FBC unit/card/module. So, A-H can only connect to A or B. I-P can only connect to I or J.

Which driver issue of the FBC driver from VU do you mean?  Since my switch from legacy to unicablesome month ago on my uno4kse I´ve seen sometimes a little interrupt on some channels when a new timer starts and requests a new tuner. I´ve made the configuration with all tuners C-H are connected to tuner A (like PLI WIKI).

Because the config in vti uses a chain I´ve made a quickhack to NimManager.py a week ago to enable the possibility to make a tuner chain with B to A, C to B, D to C ... H to G (like vti WIKI) and now it works without problems .

I use openpli 7.3. Is inside openpli 7.3 a VU FCB driver which only works without problems, if the tuners are in a chain instead of connecting B-H to A?

It seems so. But for me the tuner chain works great.

Edited by anudanan, 15 November 2021 - 07:08.

[WanWizard]

I have a legacy setup on my FBC tuners in the Duo 4K, and since quite recently I also see this, even when nothing specific happens.

 

Last night several times in an hour, watching a programme while recording F1.

[anudanan]

you mean you have picture interrupts with a legacy setup on a DUO4k? 

I haven´t seen that with my legacy setup over many month ago during recording movies. Do you have than only on your DUO4k?

Edited by anudanan, 15 November 2021 - 13:17.

[WanWizard]

Yes. but only recently, like in the last few weeks or so. I'm running the latest develop on my boxes.

 

I have nothing else connected at the moment, due to a house move.

[Abu Baniaz]

 

The daisy chaining (connecting to previous tuner, on every tuner) in that wiki page was because of driver issues which have now been fixed. Please ignore that wiki page and use the PLI wiki page. A,B,I and J are the only tuners that can have a physical connection, this is why they are the only options you have. Also, you can only connect/associate within the same FBC unit/card/module. So, A-H can only connect to A or B. I-P can only connect to I or J.

Which driver issue of the FBC driver from VU do you mean?  Since my switch from legacy to unicablesome month ago on my uno4kse I´ve seen sometimes a little interrupt on some channels when a new timer starts and requests a new tuner. I´ve made the configuration with all tuners C-H are connected to tuner A (like PLI WIKI).

Because the config in vti uses a chain I´ve made a quickhack to NimManager.py a week ago to enable the possibility to make a tuner chain with B to A, C to B, D to C ... H to G (like vti WIKI) and now it works without problems .

I use openpli 7.3. Is inside openpli 7.3 a VU FCB driver which only works without problems, if the tuners are in a chain instead of connecting B-H to A?

It seems so. But for me the tuner chain works great.

 

The issue was about 5 years ago, which is no longer applicable. If you wan't to us your change workaround, suit yourself. I don't know what you gain by daisy chaining teh unicabe setup. Personally, I think if teher is an issue with thePLI implementation, a clear description of problem should be given so it can be looked at and resolved. 

 

Let me ask you a question, if you had a unicable device for 19.2 in socket/physical tuner A, i.e top one. You also had another unicable device pointing to 28.2 socket/physical tuner B, i.e bottom one. How would you assign 4 tuners for 19.2 and 4 for 28.2 in the VTI/daisy chaining implementation?

[Abu Baniaz]

@wanwizard, not many people use universal LNBs with FBC tuners. There is a user on another forum who is doing so, he has had issues. I was meant to test his setup, but I took my dishes down. He is very unclear and never tests things straight away owing to constantly recording radio/news. There might be an issue with universal LNBs and Vu FBC tuners if your problem has started since you started using universal lnbs/setup

[WanWizard]

My setup hasn't changed since I got the Duo 4K and it replaced my ET10000.

 

I have two FBC cards, which I use in Legacy mode, 3 of the inputs connected to an Inverto Triple Quad (19.2/23.5/28/2), 1 input connected directly to 28.2 via the building distribution system.

 

This has always worked fine, I have only noticed the last week (or so?) that the channel I'm watching sometimes freezes for a second, or started juddering, like there is some latency issue. Haven't seen it tonight btw...

 

If testing is needed, I will have this only for a week or so, by december I'll have moved to a Unicable II setup.

[anudanan]

Let me ask you a question, if you had a unicable device for 19.2 in socket/physical tuner A, i.e top one. You also had another unicable device pointing to 28.2 socket/physical tuner B, i.e bottom one. How would you assign 4 tuners for 19.2 and 4 for 28.2 in the VTI/daisy chaining implementation?

 

 

 

 

Then vti use twei daiy´sy chain. For example. Connecte Tuner C to A, D to C, E to D and F to B, G to F, G to H.  The main difference to the PLI config is, every tuner has only one tuner, which is connect to it and not more than one as it is in pli konfig. Maybe there ist a bug inside the vu driver for a bugfree support of more than one tuner is connected to A or B because vti only uses chains.

Edited by anudanan, 16 November 2021 - 06:45.

[Dimitrij]

 

Maybe there ist a bug inside the vu driver for a bugfree support of more than one tuner is connected to A or B because vti only uses chains.

I don't think the error was in the drivers.

Perhaps the error was in Enigma2 and it is hoped that it has been fixed.

Unicable/FBC loop through add checking the availability of multiple t…