107 replies to this topic

[nemosince1996]

I use VU+ Ultimo 4K from time it appeared on a market with configutation 2x DVB-S2 (45208 FBC) and DVB-T2 (TT3L10). Everything is running as it should with some smaller problems during time.
Now I have bought another VU+ Ultimo 4K with DVB-S2x (45308X FBC), DVB-T2 MTSIF (BCM3466) and DVB-S2 (AVL6222).

I found two problems after flashing OpenPLI 7.1:

1) DVB-T2 MTSIF was recognized and running but after each restart of box both tuners were disabled. I had to enable them all the time. I flashed OpenPLI 7.0 and problem disappeared even if I upgraded back to 7.1. The only one thing which remains is black screen after 2-3 seconds after switching to dvb-t2 channel for several seconds. Later the picture is stable.

2) More serious problem is with DVB-S2 (AVL6222) for universal LNB's in position 3 (old socket type). Tuners are recognized as FBC tuners and they cannot be set correctly. There must be wrong data in tuner configuration.

Can somebody check configuration files, eventually to place here where and what to change DVB-S2 (AVL6222) tuners would run? Thanks in advance.

 

 

Attached Files

•  IMG_tuners_K_L.jpg   69.7KB   16 downloads

[littlesat]

How can you put a normal dual tuner in the middle slot... post the file /proc/bus/nim_sockets here... (from both boxes)
VU is currently doing a wierd thing... with latest drivers it creates too many directories in /proc/stb/frontend which confuses the nimmanager... it also creates dirs there for tuners that do not exist!

Edited by littlesat, 24 July 2019 - 13:48.

[littlesat]

And but the dvb-s2x tuner in the second slot...

[nemosince1996]

I do not how you find that I put tuners wrong. It is not possible physically because of different type of sockets.

 

Slot 1 (tuner A on the back side of box): DVB-S2x (45308X FBC)       - FBC connector, tuners A-H, standard position when you buy this box

Slot 2 (tuner B on the back side of box): DVB-T2 MTSIF (BCM3466)  - FBC connector, tuners I,J

Slot 3 (tuner C on the back side of box): DVB-S2 (AVL6222)               - old type long black socket, tuners K,L

 

Is it clear now? I need help, what to change to be able configure DVB-S2 (AVL6222) correctly and to use it. I am not an expert. Mybe OpenPLI team could issue it in next update but I would prefer to solve it quicker.

 

There are empty nim_sockets files in both boxes.

[littlesat]

The file nim_sockets must be there... without your box will not recognize any tuner.
The tuner with fbc connector which is in fact a double tuner is new to me and I can understand why the last tuner might be confused (sounds for fbc tuner I need to add an extra
check for if previous tuner or the mod 8 tuner is an fbc tuner and then also when you mix them the fbc must always be in first slot)

Edited by littlesat, 24 July 2019 - 14:30.

[Dimitrij]

In telnet(putty):

cat  /proc/bus/nim_sockets

[littlesat]

When you go from openpli 7.0 to 7.1 you indeed need to reconfigure each multi or combined tuner as the configs are changed for these... the duo tuner in fbc slot is a which leads to the 3rd tuner recognized as fbc is a different issue (and needs adaption in code)

Edited by littlesat, 24 July 2019 - 14:34.

[littlesat]

Then issue with fbc recognition is 100% sure a driver ‘issue’ as fbc_id in the /proc/stb/fronting dir must be there... I can work-a-round it by checking for this file in the first root tuner.
But still it is a stupid thing and I’m not sure if other code might be confused due to this.

[littlesat]

I also need the output from
ls /proc/stb/frontend/7

[nemosince1996]

Asked files

Attached Files

•  frontend_7.txt   223bytes   16 downloads
•  nim_sockets.txt   8.69KB   29 downloads

[littlesat]

Van welke box zijn die... want hier zie ik totaal die nieuwe tuner niet in.... dit moet gewoon goed gaan. Dit is denk ik van je eerste box.... in nim_sockets zit wel wat vreemds maar dat komt denk ik meer door her copy en pasten. Dit zijn twee fbc dvb-s2 tuners en een c/t multy duo tuner.
In de frontend dir zit op 7 een fbc_id file... je eerste box moet nu goed en perfect zijn!!!! Dat is denk ik meer de Instellingen die handmadig aangepast moest worden.

Edited by littlesat, 24 July 2019 - 16:13.

[nemosince1996]

Now for new box, previous files were for old one

Attached Files

•  frontend_7_new_box.txt   223bytes   6 downloads
•  nim_sockets_new_box.txt   1.51KB   15 downloads

[littlesat]

kan je
ls /proc/stb/frontend/8
En dan ook 9, 10, 11 ook geven. Ik hoop dat dan in 8 geen fbc_id staat. Allleen dan is er omheen te werken...
Sorry met 7 had ik me vertelt... dat was de 8e van de 1e fbc tuner.
Ook ff gefixt hebben daar ik pas morgen avond of vrijdag een oplossing kan maken

Edited by littlesat, 24 July 2019 - 16:25.

[WanWizard]

English !

[nemosince1996]

Sorry, littlesat, I do not know dutch. We are on EN section. Anyway I use Google translator.

Attached Files

•  frontend_8_new_box.txt   252bytes   5 downloads
•  frontend_9_new_box.txt   303bytes   4 downloads
•  frontend_10_new_box.txt   253bytes   3 downloads
•  frontend_11_new_box.txt   304bytes   5 downloads

[littlesat]

I cannot solve it... vu need to solve this! Driver issue. They put 18 frontend procs and the first 16!has fbc_id

Edited by littlesat, 24 July 2019 - 16:37.

[nemosince1996]

Does it mean really that there is no choice how to change it? Only VU team can? But strange is that when I tried OpenATV image it is ok in it and dvb-s2 tuner is correctly recognized and I was able to setup what I needed. I expect that drivers are the same for both images. But I need OpenPLI because you have the best configuration and control of FBC DVB-S2(x) tuners. Thank you for your effort. I can use this box so far the same way as Solo2 which I replaced and to wait for repair.

[WanWizard]

Yes, I've checked, we have the same drivers as OpenATV.

[littlesat]

Were the frontend dirs from the first or second box? When it was from the first box we still might have a solution.
Openatv is willing to create dirty work-a-rounds in their image to fix things instread or trying to arrange it the right way with vu.
Can you give a ‘cat’ of the fbc_id file? Maybe the content is different...

Edited by littlesat, 24 July 2019 - 19:42.

[littlesat]

Regarding the second box openatv has the same
Checks to verify for fbc tuner as we have https://github.com/o...s/NimManager.py so when they have the same drivers and the procs are coming from the drivers they should have the same issue... please ensure the last data was from the second box!
When something in the bsp layer creates these procs it might to be solved in the bsps

Edited by littlesat, 24 July 2019 - 19:46.