85 replies to this topic

[Dimitrij]

"NIM(45308 FBC)"

 

I think I get it, it's not VU+.

This is Gigablue "DVB-S2 NIM(45308 FBC)"

 

https://github.com/O...ntend.cpp#L1155

 

and

 

1)Qviart Lunix 4K

-"DVB-S NIM(45208X FBC)"

+"DVB-S NIM(45208 FBC)"

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

[Abu Baniaz]

@Dimitrij, would you know if the issue ccs has encountered with multiple Terrestrial tuner cards on an Ultimo 4K is a driver issue or Enigma2 issue? He has to disable one of the tuners for system to work. He is using combination of the legacy cards and MTSIF cards. 

Edited by Abu Baniaz, 17 May 2021 - 12:11.

[madiv]

@twol
Thanks for your comments on this bug, appreciated.
> I am not a OpenPli user
One more reason to say thank you for your help on OpenPLi forum :-)

@Dimitrij
Thank you for your active work in trying to fix this.

@members taking care of OpenPLi web site
Could you consider putting a note in Duo 4k se Download section
  https://openpli.org/...plus/Duo 4K SE/
like
  if DVB-T2 card is in 'Tuner A' slot & DVB-S2 card in 'Tuner B'. Sat channels will not work. We are working to fix that.

Because, in my case, I spent much time installing several times 8.0, then other versions of OpenPLi, then trying some workaround, until I eventually gave up & reported the issue in this forum. It is not necessary that others experience such long journey that ends up in 'does not work'.

[Dimitrij]

@Dimitrij, would you know if the issue ccs has encountered with multiple Terrestrial tuner cards on an Ultimo 4K is a driver issue or Enigma2 issue? He has to disable one of the tuners for system to work. He is using combination of the legacy cards and MTSIF cards. 

The problem was simple.

The code in the NimManager.py did not take into account that the first slot was not a FBC tuner, but dual DVB-T/C .

Therefore, the root tuners were calculated out incorrectly.

This applies to Duo4k/Duo4k se receivers and has already been fixed.

 

Regarding Ultimo 4K, I don't have it to check all the combinations.

Slot1 --> dual MTSIF DVB-T/C

Slot2 --> dual MTSIF DVB-T/C

Slot3 --> legacy DVB-T/C

Such a combination?

 

 

 

P.S. By the way, this receiver is my dream, with the combination 2XFBC DVB-S2 .

Edited by Dimitrij, 17 May 2021 - 13:57.

[ccs]

 

@Dimitrij, would you know if the issue ccs has encountered with multiple Terrestrial tuner cards on an Ultimo 4K is a driver issue or Enigma2 issue? He has to disable one of the tuners for system to work. He is using combination of the legacy cards and MTSIF cards. 

 

 

Regarding Ultimo 4K, I don't have it to check all the combinations.

Slot1 --> dual MTSIF DVB-T/C

Slot2 --> dual MTSIF DVB-T/C

Slot3 --> legacy DVB-T/C

Such a combination?

 

 

This is my setup on the Ultimo4K.

 

BCM3466's in slot 1 and slot 2, TT3L10 in slot 3. Terrestrial T2 only.

 

If Slot 2 is empty, all 4 T2 tuners work, when I add the BCM3466 in slot 2, the box hangs on reboot, even when tuners C and D have been disabled.

 

Rebooting eventually comes back with tuner B and tuner F now both set as cable. 

 

Disabling tuner F gives me 5 working tuners.....

Attached Files

•  works.jpg   82.08KB   0 downloads

[Huevos]

 

@Dimitrij, would you know if the issue ccs has encountered with multiple Terrestrial tuner cards on an Ultimo 4K is a driver issue or Enigma2 issue? He has to disable one of the tuners for system to work. He is using combination of the legacy cards and MTSIF cards. 

Regarding Ultimo 4K, I don't have it to check all the combinations.

Slot1 --> dual MTSIF DVB-T/C

Slot2 --> dual MTSIF DVB-T/C

Slot3 --> legacy DVB-T/C

Such a combination?

 

 

 

P.S. By the way, this receiver is my dream, with the combination 2XFBC DVB-S2 .

 

Slot 3 can be used for any legacy tuner. So DVB-S2 single, DVB-S2 twin or legacy terrestrial or cable tuners.

[Dimitrij]

 

Disabling tuner F gives me 5 working tuners.....

Looks like a problem with the drivers.

But five tuners are not bad either .

[ccs]

 

 

Disabling tuner F gives me 5 working tuners.....

Looks like a problem with the drivers.

But five tuners are not bad either .

 

All six worked before the driver update of 2019-04-24, when the BCM3466 was only a dual T2 tuner with no Cable support.

 

Adding Cable has had undesired side effects.

[Huevos]

Is there a PR?

[WanWizard]

The Xarius Galaxy 4K also has an FBC tuner, but I assume it's the same as the Lunix 4K.

[Dimitrij]

 

All six worked before the driver update of 2019-04-24, when the BCM3466 was only a dual T2 tuner with no Cable support.

 

Adding Cable has had undesired side effects.

last driver

 

Update drivers for 4k models (20190425.p0)

 - Support MIS in 45308X DVB-S2X tuner(uno4k, uno4kse, ultimo4k, duo4k)
 - Fixed DVB-CI init.
 - Fixed demux(incorrect pid)
 - Fixed vtuner(zero4k)
 - Support DVB-C in Dual MTSIF DVB-T2 tuner(uno4k, uno4kse, ultimo4k, duo4k)
 ** limitation : TS is broken when both tuenres are in use. (When one tuner is configured as DVB-C and the other one is configured as DVB-T2)

prev last

 

Update drivers for uno4k,uno4kse,ultimo4k (20190104.p0)

 - Support FBC DVB-C V2 tuner

[ccs]

 

 

Update drivers for 4k models (20190425.p0)

 ** limitation : TS is broken when both tuenres are in use. (When one tuner is configured as DVB-C and the other one is configured as DVB-T2)

 

That's the bit I've never understood, I'm not trying to mix DVB-C and DVB-T2, but it gets configured that way when rebooting.

Edited by ccs, 17 May 2021 - 16:38.

[Dimitrij]

The Xarius Galaxy 4K also has an FBC tuner, but I assume it's the same as the Lunix 4K.

Thanks

https://github.com/o...a9a61f494fc4707

 

I always could not understand what kind of receiver it was dags7252-200 .

Bingo!

dags7252-200 -->Xarius Galaxy 4K

dags7252-300 -->Lunix 4K

 

 

DVB-S NIM(45208 FBC)

For this log https://forums.openp...dpost&p=1095514

Edited by Dimitrij, 17 May 2021 - 16:52.

[Dimitrij]

 

That's the bit I've never understood, I'm not trying to mix DVB-C and DVB-T2, but it gets configured that way when rebooting.

Maybe you should install the previous drivers ?

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

[ccs]

 

 

That's the bit I've never understood, I'm not trying to mix DVB-C and DVB-T2, but it gets configured that way when rebooting.

Maybe you should install the previous drivers ?

 

That's a bit beyond me, I'm afraid.

 

This is what I've got from the last time I tried....

 

root@vuultimo4k:/media/hdd# ls -l old_working_drivers
drwxr-xr-x    5 root     root          4096 May 17 17:00 3.14.28-1.12
-rw-r--r--    1 root     root          4376 May 17 17:00 bcm3466
drwxr-xr-x    3 root     root          4096 May 17 17:00 bcm_3466bs_cls_class
drwxr-xr-x    3 root     root          4096 May 17 17:00 bcm_3466bs_cls_virtual
drwxr-xr-x    3 root     root          4096 May 17 17:00 drivers
drwxr-xr-x    2 root     root          4096 May 17 17:00 extra
drwxr-xr-x    6 root     root          4096 May 17 17:00 kernel
root@vuultimo4k:/media/hdd#

[Dimitrij]

drivers change here /lib/modules/kernel version/extra/

The first init 4

Second ps

and killall working drivers

 

But this is only in theory.

[ccs]

drivers change here /lib/modules/kernel version/extra/

The first init 4

Second ps

and killall working drivers

 

But this is only in theory.

Thanks for looking, it's much appreciated, I'll give it a go!

 

"and killall working drivers" - you'll have to give me a clue on that one. 

Edited by ccs, 17 May 2021 - 18:43.

[Dimitrij]

This requires discussion.

[NimManager] improvize definition FBC tuners

 

I thought for a long time, but I could not find another way.

Just for information:

Duo4k

Slot1 --> dual MTSIF DVB-T not FBC

/proc/stb/frontend/0/fbc_id -->FOUND!!!

/proc/stb/frontend/1/fbc_id -->FOUND!!!

 

Slot2 --> FBC DVB-SX

/proc/stb/frontend/2/fbc_id -->found

&

/proc/stb/frontend/9/fbc_id-->found

 

 

Test fbc.zip

Only develop image.

 

[WanWizard]

It this related to this topic?

 

 1_0_16_5282_C96_3_EB0000_0_0_0_20210522204839.jpg   118.93KB   1 downloads

 

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

[Pr2]

Autodiscovery on 5W is already fixed in develop so will be fixed in 8.1