Since 2 days I'm owner of VU Ultiomo4k tuner. My previous one was VuDuo2 with VTI image on board so I had pretty good experience with VTI thus decided to go with VTI on the new Ultimo4k.
I spend more than one day trying to configure my Ultimo to work with two unicable converters. It is not possible from VTI menu ! VTI creates configuration which makes decored unusable ! I totally locked my device - not single tuner was useable!?
It is not possible to make it correctly - not possible to connect virtual tunners to the physical ones. For example I'd like to use tuners A, C, E, G for Hotbird 13E with Unicable II and B, D, F, H for Astra 19,2E with Inverto. VTI doesn't allow to connect tuner H to F, only G is accepted! Why?
There is total mess in 'settings' file (/etc/enigma2/setting)
I used this description: wiki.vuplus-support.org/index.…C3.BCr_zwei_Satpositionen.
It is totally wrong and not suitable for dual FBC!
The important points to start with configuration are:
G, E,C all together to A).
This is final configuration my Ultimo4k uses and doesn't change when enter the 'Setup' \ 'System Searching' \ 'Tuner configuration'.
Alles anzeigen
I entered with text editor similar text (not the same one) but once entered 'Setup' \ 'Service Searching' \ 'Tuner configuration' it has been re-ordered, also some lines become added like:
My Unicable II works with EN50494 (8 channels) or EN50607 (24 channels), I created configuration using just EN50607 but then VTI has added lines for EN50494. I thought, ok let's switch to EN50494 and replaced all EN50607 entries by EN50494. Upon next restart VTI add EN50607 entries. I don't understand why but as this not hurting my configuration I can live with.
Of course 'setting' file modification needs to be done very carefully. It needs telnet login, then 'init 4' to stop enigma, then edit your 'settings' then 'init 3' to start enigma again.
I don't know if my configuration is strange? Why VTI doesn't care for unicable owners even one year after Ultimo4k's presence on the market? Am I really the first one to face these troubles?
My lines could be useful for anybody else who will deal with it. I'd really appreciated if someone else wrote something Unicable and FBC about before I started doing my setup.
The issues created by VTI menu are:
As I tested just VTI I'm not sure whether described issue is valid for VTI or to Ultimo4k. I assume that it would be VTI responsible.
I spend more than one day trying to configure my Ultimo to work with two unicable converters. It is not possible from VTI menu ! VTI creates configuration which makes decored unusable ! I totally locked my device - not single tuner was useable!?
It is not possible to make it correctly - not possible to connect virtual tunners to the physical ones. For example I'd like to use tuners A, C, E, G for Hotbird 13E with Unicable II and B, D, F, H for Astra 19,2E with Inverto. VTI doesn't allow to connect tuner H to F, only G is accepted! Why?
There is total mess in 'settings' file (/etc/enigma2/setting)
I used this description: wiki.vuplus-support.org/index.…C3.BCr_zwei_Satpositionen.
It is totally wrong and not suitable for dual FBC!
The important points to start with configuration are:
- dual FBC card has got 8 tunners and 2 LNB inputs, ie. these 8 could be used (N1 + N2) = 8 (where N1 - number of tuners assigned to LNB1 and N2 - number of tuners assigned to LNB2).
- each tuner can be assigned to single LNB only, either connected directly to LNB or to another tuner (here wiki description is missleading as it suggest that each tuner could have configuration for LNB1 and LNB2 at the same time)
- tuner A connected to physical LNB (upper connector of the physical tuner A)
- tuner B connected to physical LNB (bottom connector of the physical tuner A)
- tuner C connected to tuner A
- tuner D connected to tuner B
- tuner E connected to tuner C
- tuner F connected to tuner D
- tuner G connected to tuner E
- tuner H connected to tuner F
This is final configuration my Ultimo4k uses and doesn't change when enter the 'Setup' \ 'System Searching' \ 'Tuner configuration'.
Quellcode
- config.Nims.1.configMode=advanced
- config.Nims.1.advanced.sats=192
- config.Nims.1.advanced.sat.192.lnb=2
- config.Nims.1.advanced.lnb.2.lof=unicable
- config.Nims.1.advanced.lnb.2.unicableMatrixManufacturer=Inverto
- config.Nims.1.advanced.lnb.2.unicableMatrix.Inverto.product=IDLP-UST1O1-CUO1O-4PP
- config.Nims.1.advanced.lnb.2.unicableMatrix.Inverto.vco.IDLP-UST1O1-CUO1O-4PP.0=1210
- config.Nims.0.configMode=advanced
- config.Nims.0.advanced.sats=130
- config.Nims.0.advanced.sat.130.lnb=1
- config.Nims.0.advanced.lnb.1.satcrvcouserEN50607.0=1210
- config.Nims.0.advanced.lnb.1.dictionuser=EN50494
- config.Nims.0.advanced.lnb.1.satcrvcouserEN50494.0=1210
- config.Nims.0.advanced.lnb.1.lof=unicable
- config.Nims.0.advanced.lnb.1.unicable=unicable_user
- config.Nims.3.configMode=advanced
- config.Nims.3.advanced.unicableconnectedTo=1
- config.Nims.3.advanced.unicableconnected=true
- config.Nims.3.advanced.sat.192.lnb=2
- config.Nims.3.advanced.sats=192
- config.Nims.3.advanced.lnb.2.lof=unicable
- config.Nims.3.advanced.lnb.2.unicableMatrixManufacturer=Inverto
- config.Nims.3.advanced.lnb.2.unicableMatrix.Inverto.product=IDLP-UST1O1-CUO1O-4PP
- config.Nims.3.advanced.lnb.2.unicableMatrix.Inverto.vco.IDLP-UST1O1-CUO1O-4PP.1=1420
- config.Nims.3.advanced.lnb.2.unicableMatrix.Inverto.scr.IDLP-UST1O1-CUO1O-4PP=2
- config.Nims.2.configMode=advanced
- config.Nims.2.advanced.unicableconnectedTo=0
- config.Nims.2.advanced.unicableconnected=true
- config.Nims.2.advanced.sat.130.lnb=1
- config.Nims.2.advanced.sats=130
- config.Nims.2.advanced.lnb.1.lof=unicable
- config.Nims.2.advanced.lnb.1.dictionuser=EN50494
- config.Nims.2.advanced.lnb.1.satcrvcouserEN50494.1=1420
- config.Nims.2.advanced.lnb.1.satcruserEN50494=2
- config.Nims.2.advanced.lnb.1.unicable=unicable_user
- config.Nims.2.advanced.lnb.1.satcrvcouserEN50607.1=1420
- config.Nims.5.configMode=advanced
- config.Nims.5.advanced.unicableconnectedTo=3
- config.Nims.5.advanced.unicableconnected=true
- config.Nims.5.advanced.sat.192.lnb=2
- config.Nims.5.advanced.sats=192
- config.Nims.5.advanced.lnb.2.lof=unicable
- config.Nims.5.advanced.lnb.2.unicableMatrixManufacturer=Inverto
- config.Nims.5.advanced.lnb.2.unicableMatrix.Inverto.product=IDLP-UST1O1-CUO1O-4PP
- config.Nims.5.advanced.lnb.2.unicableMatrix.Inverto.vco.IDLP-UST1O1-CUO1O-4PP.2=1680
- config.Nims.5.advanced.lnb.2.unicableMatrix.Inverto.scr.IDLP-UST1O1-CUO1O-4PP=3
- config.Nims.4.configMode=advanced
- config.Nims.4.advanced.unicableconnectedTo=2
- config.Nims.4.advanced.unicableconnected=true
- config.Nims.4.advanced.sat.130.lnb=1
- config.Nims.4.advanced.sats=130
- config.Nims.4.advanced.lnb.1.lof=unicable
- config.Nims.4.advanced.lnb.1.dictionuser=EN50494
- config.Nims.4.advanced.lnb.1.satcrvcouserEN50494.2=1680
- config.Nims.4.advanced.lnb.1.satcruserEN50494=3
- config.Nims.4.advanced.lnb.1.unicable=unicable_user
- config.Nims.4.advanced.lnb.1.satcrvcouserEN50607.2=1680
- config.Nims.7.configMode=advanced
- config.Nims.7.advanced.unicableconnectedTo=5
- config.Nims.7.advanced.unicableconnected=true
- config.Nims.7.advanced.sat.192.lnb=2
- config.Nims.7.advanced.lnb.2.lof=unicable
- config.Nims.7.advanced.lnb.2.unicableMatrixManufacturer=Inverto
- config.Nims.7.advanced.lnb.2.unicableMatrix.Inverto.product=IDLP-UST1O1-CUO1O-4PP
- config.Nims.7.advanced.lnb.2.unicableMatrix.Inverto.vco.IDLP-UST1O1-CUO1O-4PP.3=2040
- config.Nims.7.advanced.lnb.2.unicableMatrix.Inverto.scr.IDLP-UST1O1-CUO1O-4PP=4
- config.Nims.6.configMode=advanced
- config.Nims.6.advanced.unicableconnectedTo=4
- config.Nims.6.advanced.unicableconnected=true
- config.Nims.6.advanced.sat.130.lnb=1
- config.Nims.6.advanced.sats=130
- config.Nims.6.advanced.lnb.1.lof=unicable
- config.Nims.6.advanced.lnb.1.dictionuser=EN50494
- config.Nims.6.advanced.lnb.1.satcrvcouserEN50494.3=2040
- config.Nims.6.advanced.lnb.1.satcrvcouserEN50494.4=2040
- config.Nims.6.advanced.lnb.1.satcruserEN50494=4
- config.Nims.6.advanced.lnb.1.unicable=unicable_user
- config.Nims.6.advanced.lnb.1.satcrvcouserEN50607.3=2040
- config.Nims.6.advanced.lnb.1.satcrvcouserEN50607.4=2040
My Unicable II works with EN50494 (8 channels) or EN50607 (24 channels), I created configuration using just EN50607 but then VTI has added lines for EN50494. I thought, ok let's switch to EN50494 and replaced all EN50607 entries by EN50494. Upon next restart VTI add EN50607 entries. I don't understand why but as this not hurting my configuration I can live with.
Of course 'setting' file modification needs to be done very carefully. It needs telnet login, then 'init 4' to stop enigma, then edit your 'settings' then 'init 3' to start enigma again.
I don't know if my configuration is strange? Why VTI doesn't care for unicable owners even one year after Ultimo4k's presence on the market? Am I really the first one to face these troubles?
My lines could be useful for anybody else who will deal with it. I'd really appreciated if someone else wrote something Unicable and FBC about before I started doing my setup.
The issues created by VTI menu are:
- Each tuner can have several LNBs attached. This is root cause, most likely, lack of the operation when created configuration from menu. As act of desperation I removed configuration for tuners B .. H, only A left and there was still no signal from dish. When opened 'settings' I found config for LNB1 and LNB2. I found no way to remove LNB2 config from menu - this is why I decided to use 'setting' directly. After a while - I've got a signal.
- It is not possible to create connections between tuners. As mentioned previously I wanted G to E, E to C, C to A but VTI doesn't like this and replaced E by d or something else. Why? The rule is pretty simple - if tuner is not referred by any other tuner it should be accessible.
- There is some mess with SCR(n) and frequencies. It is possible to use channel SatCR0 for several times with different frequencies. Why? The rule is pretty simple - frequency goes together with channel, frequency is important so what is the point to lock tuner if SCR doesn't match the frequency?
As I tested just VTI I'm not sure whether described issue is valid for VTI or to Ultimo4k. I assume that it would be VTI responsible.