Jump to content


Photo

VU+ duo 4k se - service unavailable! check tuner configuration! & No auto discovery of Eutelsat 5.0W

Started by madiv, 15 May 2021 18:14

  • Please log in to reply
85 replies to this topic

Re: VU+ duo 4k se - service unavailable! check tuner configuration! & No auto discovery of Eutelsat 5.0W #61 Dimitrij

  • PLi® Core member
  • 10,327 posts

+350
Excellent

Posted 23 May 2021 - 08:28

 

 

For some reason my second FBC tuner is now seen as two ( I and J-Q ) instead of one ( I-P ).

Please answer

 

cat /proc/bus/nim_sockets


GigaBlue UHD Quad 4K /Lunix3-4K/Duo 4K

Re: VU+ duo 4k se - service unavailable! check tuner configuration! & No auto discovery of Eutelsat 5.0W #62 Huevos

  • PLi® Contributor
  • 4,661 posts

+163
Excellent

Posted 23 May 2021 - 11:42

 

 

 

For some reason my second FBC tuner is now seen as two ( I and J-Q ) instead of one ( I-P ).

Please answer

 

cat /proc/bus/nim_sockets

 

For me, Vu+ Ultimo 4K, it works fine.

root@vuultimo4k:~# cat /proc/bus/nim_sockets
NIM Socket 0:
        Type: DVB-S2
        Name: Vuplus DVB-S NIM(45208 FBC)
        Frontend_Device: 0
NIM Socket 1:
        Type: DVB-S2
        Name: Vuplus DVB-S NIM(45208 FBC)
        Frontend_Device: 1
NIM Socket 2:
        Type: DVB-S2
        Name: Vuplus DVB-S NIM(45208 FBC)
        Frontend_Device: 2
NIM Socket 3:
        Type: DVB-S2
        Name: Vuplus DVB-S NIM(45208 FBC)
        Frontend_Device: 3
NIM Socket 4:
        Type: DVB-S2
        Name: Vuplus DVB-S NIM(45208 FBC)
        Frontend_Device: 4
NIM Socket 5:
        Type: DVB-S2
        Name: Vuplus DVB-S NIM(45208 FBC)
        Frontend_Device: 5
NIM Socket 6:
        Type: DVB-S2
        Name: Vuplus DVB-S NIM(45208 FBC)
        Frontend_Device: 6
NIM Socket 7:
        Type: DVB-S2
        Name: Vuplus DVB-S NIM(45208 FBC)
        Frontend_Device: 7
NIM Socket 8:
        Type: DVB-S2X
        Name: Vuplus DVB-S NIM(45308X FBC)
        Frontend_Device: 8
NIM Socket 9:
        Type: DVB-S2X
        Name: Vuplus DVB-S NIM(45308X FBC)
        Frontend_Device: 9
NIM Socket 10:
        Type: DVB-S2X
        Name: Vuplus DVB-S NIM(45308X FBC)
        Frontend_Device: 10
NIM Socket 11:
        Type: DVB-S2X
        Name: Vuplus DVB-S NIM(45308X FBC)
        Frontend_Device: 11
NIM Socket 12:
        Type: DVB-S2X
        Name: Vuplus DVB-S NIM(45308X FBC)
        Frontend_Device: 12
NIM Socket 13:
        Type: DVB-S2X
        Name: Vuplus DVB-S NIM(45308X FBC)
        Frontend_Device: 13
NIM Socket 14:
        Type: DVB-S2X
        Name: Vuplus DVB-S NIM(45308X FBC)
        Frontend_Device: 14
NIM Socket 15:
        Type: DVB-S2X
        Name: Vuplus DVB-S NIM(45308X FBC)
        Frontend_Device: 15
NIM Socket 16:
        Type: DVB-T2
        Name: Vuplus DVB-T NIM(TT3L10)
        Mode 0: DVB-C
        Mode 1: DVB-T2
        Frontend_Device: 16
        I2C_Device: 3
NIM Socket 17:
        Type: DVB-T2
        Name: Vuplus DVB-T NIM(TT3L10)
        Mode 0: DVB-C
        Mode 1: DVB-T2
        Frontend_Device: 17
        I2C_Device: 3
root@vuultimo4k:~#

 


Re: VU+ duo 4k se - service unavailable! check tuner configuration! & No auto discovery of Eutelsat 5.0W #63 Dimitrij

  • PLi® Core member
  • 10,327 posts

+350
Excellent

Posted 23 May 2021 - 12:18

Done

[NimManager] fix fbc count


GigaBlue UHD Quad 4K /Lunix3-4K/Duo 4K

Re: VU+ duo 4k se - service unavailable! check tuner configuration! & No auto discovery of Eutelsat 5.0W #64 WanWizard

  • PLi® Core member
  • 70,523 posts

+1,810
Excellent

Posted 23 May 2021 - 14:14

Just seen the question, and maybe to late, but for completeness:

root@vuduo4k:~# cat /proc/bus/nim_sockets 
NIM Socket 0:
	Type: DVB-S2X
	Name: Vuplus DVB-S NIM(45308X FBC)
	Frontend_Device: 0
NIM Socket 1:
	Type: DVB-S2X
	Name: Vuplus DVB-S NIM(45308X FBC)
	Frontend_Device: 1
NIM Socket 2:
	Type: DVB-S2X
	Name: Vuplus DVB-S NIM(45308X FBC)
	Frontend_Device: 2
NIM Socket 3:
	Type: DVB-S2X
	Name: Vuplus DVB-S NIM(45308X FBC)
	Frontend_Device: 3
NIM Socket 4:
	Type: DVB-S2X
	Name: Vuplus DVB-S NIM(45308X FBC)
	Frontend_Device: 4
NIM Socket 5:
	Type: DVB-S2X
	Name: Vuplus DVB-S NIM(45308X FBC)
	Frontend_Device: 5
NIM Socket 6:
	Type: DVB-S2X
	Name: Vuplus DVB-S NIM(45308X FBC)
	Frontend_Device: 6
NIM Socket 7:
	Type: DVB-S2X
	Name: Vuplus DVB-S NIM(45308X FBC)
	Frontend_Device: 7
NIM Socket 8:
	Type: DVB-S2X
	Name: Vuplus DVB-S NIM(45308X FBC)
	Frontend_Device: 8
NIM Socket 9:
	Type: DVB-S2X
	Name: Vuplus DVB-S NIM(45308X FBC)
	Frontend_Device: 9
NIM Socket 10:
	Type: DVB-S2X
	Name: Vuplus DVB-S NIM(45308X FBC)
	Frontend_Device: 10
NIM Socket 11:
	Type: DVB-S2X
	Name: Vuplus DVB-S NIM(45308X FBC)
	Frontend_Device: 11
NIM Socket 12:
	Type: DVB-S2X
	Name: Vuplus DVB-S NIM(45308X FBC)
	Frontend_Device: 12
NIM Socket 13:
	Type: DVB-S2X
	Name: Vuplus DVB-S NIM(45308X FBC)
	Frontend_Device: 13
NIM Socket 14:
	Type: DVB-S2X
	Name: Vuplus DVB-S NIM(45308X FBC)
	Frontend_Device: 14
NIM Socket 15:
	Type: DVB-S2X
	Name: Vuplus DVB-S NIM(45308X FBC)
	Frontend_Device: 15

 


Currently in use: VU+ Duo 4K (2xFBC S2), VU+ Solo 4K (1xFBC S2), uClan Usytm 4K Ultimate (S2+T2), Octagon SF8008 (S2+T2), Zgemma H9.2H (S2+T2)

Due to my bad health, I will not be very active at times and may be slow to respond. I will not read the forum or PM on a regular basis.

Many answers to your question can be found in our new and improved wiki.

Re: VU+ duo 4k se - service unavailable! check tuner configuration! & No auto discovery of Eutelsat 5.0W #65 Dimitrij

  • PLi® Core member
  • 10,327 posts

+350
Excellent

Posted 23 May 2021 - 16:51

I was able to simulate your situation by creating a text file nim_sockets with similar tuner data.

NimManager.py

        try:
            #nimfile = open("/proc/bus/nim_sockets")
            nimfile = open("/etc/nim_sockets")
        except IOError:
            return


Edited by Dimitrij, 23 May 2021 - 16:55.

GigaBlue UHD Quad 4K /Lunix3-4K/Duo 4K

Re: VU+ duo 4k se - service unavailable! check tuner configuration! & No auto discovery of Eutelsat 5.0W #66 WanWizard

  • PLi® Core member
  • 70,523 posts

+1,810
Excellent

Posted 23 May 2021 - 19:28

Thanks, it is fixed now.


Currently in use: VU+ Duo 4K (2xFBC S2), VU+ Solo 4K (1xFBC S2), uClan Usytm 4K Ultimate (S2+T2), Octagon SF8008 (S2+T2), Zgemma H9.2H (S2+T2)

Due to my bad health, I will not be very active at times and may be slow to respond. I will not read the forum or PM on a regular basis.

Many answers to your question can be found in our new and improved wiki.

Re: VU+ duo 4k se - service unavailable! check tuner configuration! & No auto discovery of Eutelsat 5.0W #67 madiv

  • Senior Member
  • 29 posts

0
Neutral

Posted 24 May 2021 - 09:30

To confirm on duo 4k se, I installed latest Nightly build:
  openpli-develop-vuduo4kse-20210524_usb
Then (got additional) updated packages on 24/05.

[ Sat: 'service unavailable! check tuner configuration!'   (problem 1-) ]
Solved, I can tune Sat channels.
FYI see attached picture of tuners (note that previous I-J are now called C-D = more logical)

[ Auto DiseqC does not discover Eutelsat 5.0W   (problem 2-) ]
Auto DiseqC finds Eutelsat 5.0W (as previous nightly build also did)

=> all issues got solved in Nightly build.
Thanks,

Attached Files


Re: VU+ duo 4k se - service unavailable! check tuner configuration! & No auto discovery of Eutelsat 5.0W #68 Huevos

  • PLi® Contributor
  • 4,661 posts

+163
Excellent

Posted 24 May 2021 - 13:39

Something very weird.

 

Vu Ultimo 4K

 

Attached File  tuners.jpg   32.81KB   0 downloads

 

Settings file looks like this:

config.Nims.0.terrestrial=All regions, United Kingdom, (Europe DVB-T/T2)
config.Nims.1.terrestrial=All regions, United Kingdom, (Europe DVB-T/T2)
config.Nims.2.terrestrial=All regions, United Kingdom, (Europe DVB-T/T2)
config.Nims.3.terrestrial=All regions, United Kingdom, (Europe DVB-T/T2)
config.Nims.4.multiType=1
config.Nims.4.terrestrial=All regions, United Kingdom, (Europe DVB-T/T2)
config.Nims.5.multiType=nothing

root@vuultimo4k:~# cat /proc/bus/nim_sockets
NIM Socket 0:
        Type: DVB-T2
        Name: Vuplus DVB-T NIM(BCM3466)
        Mode 0: DVB-T2
        Mode 1: DVB-C
        Frontend_Device: 0
        I2C_Device: 2
NIM Socket 1:
        Type: DVB-T2
        Name: Vuplus DVB-T NIM(BCM3466)
        Mode 0: DVB-T2
        Mode 1: DVB-C
        Frontend_Device: 1
        I2C_Device: 2
NIM Socket 2:
        Type: DVB-T2
        Name: Vuplus DVB-T NIM(BCM3466)
        Mode 0: DVB-T2
        Mode 1: DVB-C
        Frontend_Device: 2
        I2C_Device: 4
NIM Socket 3:
        Type: DVB-T2
        Name: Vuplus DVB-T NIM(BCM3466)
        Mode 0: DVB-T2
        Mode 1: DVB-C
        Frontend_Device: 3
        I2C_Device: 4
NIM Socket 4:
        Type: DVB-T2
        Name: Vuplus DVB-T NIM(TT3L10)
        Mode 0: DVB-C
        Mode 1: DVB-T2
        Frontend_Device: 4
        I2C_Device: 3
NIM Socket 5:
        Type: DVB-C
        Name: Vuplus DVB-C NIM(TT3L10)
        Mode 0: DVB-C
        Mode 1: DVB-T2
        Frontend_Device: 5
        I2C_Device: 3

Tuner F is not configured.

 

Now we try to configure Tuner F.

config.Nims.0.terrestrial=All regions, United Kingdom, (Europe DVB-T/T2)
config.Nims.1.terrestrial=All regions, United Kingdom, (Europe DVB-T/T2)
config.Nims.2.terrestrial=All regions, United Kingdom, (Europe DVB-T/T2)
config.Nims.3.terrestrial=All regions, United Kingdom, (Europe DVB-T/T2)
config.Nims.4.multiType=1
config.Nims.4.terrestrial=All regions, United Kingdom, (Europe DVB-T/T2)
config.Nims.5.multiType=1
config.Nims.5.terrestrial=All regions, United Kingdom, (Europe DVB-T/T2

Restart enigma...

 

Now the box has an endless spinner and "cat /proc/bus/nim_sockets" looks like this:

root@vuultimo4k:~# cat /proc/bus/nim_sockets
NIM Socket 0:
        Type: DVB-T2
        Name: Vuplus DVB-T NIM(BCM3466)
        Mode 0: DVB-T2
        Mode 1: DVB-C
        Frontend_Device: 0
        I2C_Device: 2
root@vuultimo4k:~#

What is causing that?


Edited by Huevos, 24 May 2021 - 13:47.

Re: VU+ duo 4k se - service unavailable! check tuner configuration! & No auto discovery of Eutelsat 5.0W #69 Dimitrij

  • PLi® Core member
  • 10,327 posts

+350
Excellent

Posted 24 May 2021 - 16:24

 

What is causing that?

My fixes didn't touch /proc/bus/nim_sockets

Maybe same problem https://forums.openp...dpost&p=1349963

 

Restart enigma...

Maybe restart box


Edited by Dimitrij, 24 May 2021 - 16:25.

GigaBlue UHD Quad 4K /Lunix3-4K/Duo 4K

Re: VU+ duo 4k se - service unavailable! check tuner configuration! & No auto discovery of Eutelsat 5.0W #70 Dimitrij

  • PLi® Core member
  • 10,327 posts

+350
Excellent

Posted 24 May 2021 - 16:29

 

NimManager.py

        try:
            #nimfile = open("/proc/bus/nim_sockets")
            nimfile = open("/etc/nim_sockets")
        except IOError:
            return

I wonder if you do it like this

/etc/nim_sockets

NIM Socket 0:
        Type: DVB-T2
        Name: Vuplus DVB-T NIM(BCM3466)
        Mode 0: DVB-T2
        Mode 1: DVB-C
        Frontend_Device: 0
        I2C_Device: 2
NIM Socket 1:
        Type: DVB-T2
        Name: Vuplus DVB-T NIM(BCM3466)
        Mode 0: DVB-T2
        Mode 1: DVB-C
        Frontend_Device: 1
        I2C_Device: 2
NIM Socket 2:
        Type: DVB-T2
        Name: Vuplus DVB-T NIM(BCM3466)
        Mode 0: DVB-T2
        Mode 1: DVB-C
        Frontend_Device: 2
        I2C_Device: 4
NIM Socket 3:
        Type: DVB-T2
        Name: Vuplus DVB-T NIM(BCM3466)
        Mode 0: DVB-T2
        Mode 1: DVB-C
        Frontend_Device: 3
        I2C_Device: 4
NIM Socket 4:
        Type: DVB-T2
        Name: Vuplus DVB-T NIM(TT3L10)
        Mode 0: DVB-C
        Mode 1: DVB-T2
        Frontend_Device: 4
        I2C_Device: 3
NIM Socket 5:
        Type: DVB-C
        Name: Vuplus DVB-C NIM(TT3L10)
        Mode 0: DVB-C
        Mode 1: DVB-T2
        Frontend_Device: 5
        I2C_Device: 3

 


Edited by Dimitrij, 24 May 2021 - 17:20.

GigaBlue UHD Quad 4K /Lunix3-4K/Duo 4K

Re: VU+ duo 4k se - service unavailable! check tuner configuration! & No auto discovery of Eutelsat 5.0W #71 Dimitrij

  • PLi® Core member
  • 10,327 posts

+350
Excellent

Posted 25 May 2021 - 05:38

Huevos

 

  nimfile = open("/etc/nim_sockets")

Have you tried this option?


GigaBlue UHD Quad 4K /Lunix3-4K/Duo 4K

Re: VU+ duo 4k se - service unavailable! check tuner configuration! & No auto discovery of Eutelsat 5.0W #72 twol

  • Senior Member
  • 448 posts

+15
Neutral

Posted 25 May 2021 - 07:24

@Dimitrij what is "nimfile = open("/etc/nim_sockets")" supposed to do?
File is not on my gbue4K image only "/proc/bus/nim_sockets"


Gigablue Quad 4K & UE 4K, Vu+Uno4KSE, DM900
.........FBC Tuners:
------------------> GT-SAT unicable lnb to 1.5M dish(28.2E)
------------------> Gigablue unicable lnb to 80 cm dish(19.2E)

Octagon sf8008, AX HD61, Edision Osmio 4K+, Zgemma H9Combo using Legacy ports on multiswitches
Zgemma H9twin & Zgemma H9 C/S mode into Giga4K
 

Re: VU+ duo 4k se - service unavailable! check tuner configuration! & No auto discovery of Eutelsat 5.0W #73 Dimitrij

  • PLi® Core member
  • 10,327 posts

+350
Excellent

Posted 25 May 2021 - 07:28

@Dimitrij what is "nimfile = open("/etc/nim_sockets")" supposed to do?
File is not on my gbue4K image only "/proc/bus/nim_sockets"

https://forums.openp...dpost&p=1351703

Create a test file /etc/nim_sockets to simulate the original /proc/bus/nim_sockets".

This is for developers only.


GigaBlue UHD Quad 4K /Lunix3-4K/Duo 4K

Re: VU+ duo 4k se - service unavailable! check tuner configuration! & No auto discovery of Eutelsat 5.0W #74 Pr2

  • PLi® Contributor
  • 6,181 posts

+261
Excellent

Posted 31 July 2021 - 09:29

 

 

BTW, if there are FBC DVB-C and FBC DVB-S in the same Vu receiver, the DVB-C tuner must go in the first slot.

 

Not true I have a Duo 4K and a Soloi4K with just the opposite and it is working fine.

 

Of course it does not apply to the Solo4K, that machine does not accept slot in FBC tuners. And you certainly can't put an FBC cable tuner in it.

 

I still have the email from Vu plus (12/2016) explaining that if FBC DVB-C is used it must go in the first slot. Duo4k came out 2 years later so possibly is different, but I am talking about FBC tuners, not the legacy TT3L10 that is not compatible with the FBC socket.

 

 

Mea culpa,  in the Duo 4K the Vuplus DVB-C NIM(BCM3148) is working in slot 2 but then you cannot fully use the FBC tuner, only 2 tuners are available (I and J)  the box indeed tries to use the K tuner but screen remains black. :-(

 

So I have switched my tuner and set the DVB-C into slot 1 and then I can use tuner ABCDE...

 

So indeed VU+ only fully support one and only one FBC tuner in its box and it must be in slot 1, a FBC tuner in slot 2 just behave like a dual tuner (at least in Solo4K and Duo4K).


NO SUPPORT by PM, it is a forum make your question public so everybody can benefit from the question/answer.
If you think that my answer helps you, you can press the up arrow in bottom right of the answer.

Wanna help with OpenPLi Translation? Please read our Wiki Information for translators

Sat: Hotbird 13.0E, Astra 19.2E, Eutelsat5A 5.0W
VU+ Solo 4K: 2*DVB-S2 + 2*DVB-C/T/T2 (used in DVB-C) & Duo 4K: 2*DVB-S2X + DVB-C (FBC)

AB-Com: PULSe 4K 1*DVB-S2X (+ DVB-C/T/T2)
Edision OS Mio 4K: 1*DVB-S2X + 1*DVB-C/T/T2
 

Re: VU+ duo 4k se - service unavailable! check tuner configuration! & No auto discovery of Eutelsat 5.0W #75 Dimitrij

  • PLi® Core member
  • 10,327 posts

+350
Excellent

Posted 31 July 2021 - 09:42

 

Mea culpa,  in the Duo 4K the Vuplus DVB-C NIM(BCM3148) is working in slot 2 but then you cannot fully use the FBC tuner, only 2 tuners are available (I and J)  the box indeed tries to use the K tuner but screen remains black. :-(

Please answer when use two fbc tuner dvb-c/dvb-s

cat /proc/bus/nim_sockets

Edited by Dimitrij, 31 July 2021 - 09:43.

GigaBlue UHD Quad 4K /Lunix3-4K/Duo 4K

Re: VU+ duo 4k se - service unavailable! check tuner configuration! & No auto discovery of Eutelsat 5.0W #76 Pr2

  • PLi® Contributor
  • 6,181 posts

+261
Excellent

Posted 31 July 2021 - 11:21

Here it is DVB-C is back into slot 2.

 

root@vuduo4k:~# cat /proc/bus/nim_sockets 
NIM Socket 0:
        Type: DVB-S2X
        Name: Vuplus DVB-S NIM(45308X FBC)
        Frontend_Device: 0
NIM Socket 1:
        Type: DVB-S2X
        Name: Vuplus DVB-S NIM(45308X FBC)
        Frontend_Device: 1
NIM Socket 2:
        Type: DVB-S2X
        Name: Vuplus DVB-S NIM(45308X FBC)
        Frontend_Device: 2
NIM Socket 3:
        Type: DVB-S2X
        Name: Vuplus DVB-S NIM(45308X FBC)
        Frontend_Device: 3
NIM Socket 4:
        Type: DVB-S2X
        Name: Vuplus DVB-S NIM(45308X FBC)
        Frontend_Device: 4
NIM Socket 5:
        Type: DVB-S2X
        Name: Vuplus DVB-S NIM(45308X FBC)
        Frontend_Device: 5
NIM Socket 6:
        Type: DVB-S2X
        Name: Vuplus DVB-S NIM(45308X FBC)
        Frontend_Device: 6
NIM Socket 7:
        Type: DVB-S2X
        Name: Vuplus DVB-S NIM(45308X FBC)
        Frontend_Device: 7
NIM Socket 8:
        Type: DVB-C
        Name: Vuplus DVB-C NIM(BCM3148)
        Frontend_Device: 8
        I2C_Device: 4
NIM Socket 9:
        Type: DVB-C
        Name: Vuplus DVB-C NIM(BCM3148)
        Frontend_Device: 9
        I2C_Device: 4
NIM Socket 10:
        Type: DVB-C
        Name: Vuplus DVB-C NIM(BCM3148)
        Frontend_Device: 10
        I2C_Device: 4
NIM Socket 11:
        Type: DVB-C
        Name: Vuplus DVB-C NIM(BCM3148)
        Frontend_Device: 11
        I2C_Device: 4
NIM Socket 12:
        Type: DVB-C
        Name: Vuplus DVB-C NIM(BCM3148)
        Frontend_Device: 12
        I2C_Device: 4
NIM Socket 13:
        Type: DVB-C
        Name: Vuplus DVB-C NIM(BCM3148)
        Frontend_Device: 13
        I2C_Device: 4
NIM Socket 14:
        Type: DVB-C
        Name: Vuplus DVB-C NIM(BCM3148)
        Frontend_Device: 14
        I2C_Device: 4
NIM Socket 15:
        Type: DVB-C
        Name: Vuplus DVB-C NIM(BCM3148)
        Frontend_Device: 15
        I2C_Device: 4

NO SUPPORT by PM, it is a forum make your question public so everybody can benefit from the question/answer.
If you think that my answer helps you, you can press the up arrow in bottom right of the answer.

Wanna help with OpenPLi Translation? Please read our Wiki Information for translators

Sat: Hotbird 13.0E, Astra 19.2E, Eutelsat5A 5.0W
VU+ Solo 4K: 2*DVB-S2 + 2*DVB-C/T/T2 (used in DVB-C) & Duo 4K: 2*DVB-S2X + DVB-C (FBC)

AB-Com: PULSe 4K 1*DVB-S2X (+ DVB-C/T/T2)
Edision OS Mio 4K: 1*DVB-S2X + 1*DVB-C/T/T2
 

Re: VU+ duo 4k se - service unavailable! check tuner configuration! & No auto discovery of Eutelsat 5.0W #77 Dimitrij

  • PLi® Core member
  • 10,327 posts

+350
Excellent

Posted 31 July 2021 - 11:34

 

Here it is DVB-C is back into slot 2.

Only NIM Socket 8(I)/NIM Socket 9(J) work?

If so, then this is some kind of hardware limitation.


Edited by Dimitrij, 31 July 2021 - 11:38.

GigaBlue UHD Quad 4K /Lunix3-4K/Duo 4K

Re: VU+ duo 4k se - service unavailable! check tuner configuration! & No auto discovery of Eutelsat 5.0W #78 WanWizard

  • PLi® Core member
  • 70,523 posts

+1,810
Excellent

Posted 31 July 2021 - 13:22

So indeed VU+ only fully support one and only one FBC tuner in its box and it must be in slot 1, a FBC tuner in slot 2 just behave like a dual tuner (at least in Solo4K and Duo4K).

 

Perhaps you mean something else than you write, but I have two FBC tuners in my Duo 4K, and both work fine.
 

Maybe the hardware limitation is limited to the DVB-C FBC tuner?


Currently in use: VU+ Duo 4K (2xFBC S2), VU+ Solo 4K (1xFBC S2), uClan Usytm 4K Ultimate (S2+T2), Octagon SF8008 (S2+T2), Zgemma H9.2H (S2+T2)

Due to my bad health, I will not be very active at times and may be slow to respond. I will not read the forum or PM on a regular basis.

Many answers to your question can be found in our new and improved wiki.

Re: VU+ duo 4k se - service unavailable! check tuner configuration! & No auto discovery of Eutelsat 5.0W #79 Pr2

  • PLi® Contributor
  • 6,181 posts

+261
Excellent

Posted 31 July 2021 - 15:14

Did you try to use more than 2 tuners on your second FBC tuner?
The tuner is working but when I went to K I have no image (DVB-C) so yes my second FBC tuner works but only on 2 tuners and not more.

NO SUPPORT by PM, it is a forum make your question public so everybody can benefit from the question/answer.
If you think that my answer helps you, you can press the up arrow in bottom right of the answer.

Wanna help with OpenPLi Translation? Please read our Wiki Information for translators

Sat: Hotbird 13.0E, Astra 19.2E, Eutelsat5A 5.0W
VU+ Solo 4K: 2*DVB-S2 + 2*DVB-C/T/T2 (used in DVB-C) & Duo 4K: 2*DVB-S2X + DVB-C (FBC)

AB-Com: PULSe 4K 1*DVB-S2X (+ DVB-C/T/T2)
Edision OS Mio 4K: 1*DVB-S2X + 1*DVB-C/T/T2
 

Re: VU+ duo 4k se - service unavailable! check tuner configuration! & No auto discovery of Eutelsat 5.0W #80 WanWizard

  • PLi® Core member
  • 70,523 posts

+1,810
Excellent

Posted 31 July 2021 - 15:25

Yup, all the time, as I use them in DiSeqC mode at the moment. But I have two DVB-S FBC tuners, and afaik the issue is related to DVB-C only.


Currently in use: VU+ Duo 4K (2xFBC S2), VU+ Solo 4K (1xFBC S2), uClan Usytm 4K Ultimate (S2+T2), Octagon SF8008 (S2+T2), Zgemma H9.2H (S2+T2)

Due to my bad health, I will not be very active at times and may be slow to respond. I will not read the forum or PM on a regular basis.

Many answers to your question can be found in our new and improved wiki.

Back to [EN] Enduser support

5 user(s) are reading this topic

0 members, 5 guests, 0 anonymous users

  1. Forums
  2. → PLi® Support
  3. → [EN] Enduser support