107 replies to this topic

[WanWizard]

OE-A drivers are latest from vendor...... 

 

 

We have the same VU+ drivers as OE-A, they haven't been updated in a while.

[malahini]

I have exactly the same problem as nemosince1996! The problem requires a solution.

Thank you, guys! Now my old tuners are displayed and working correctly too!

[nemosince1996]

After two weeks of exploatation I have found a problem in PIP with  tuners (K and L in my case) but now I cannot surely distinguish whether it is hardware or drivers. PIP runs OK when I use two channels from the same satellite and with the same polarization. I can swap them without problem. If I have different polarization (V and H) on one satellite or two channels from different satellites I cannot see both channels. One is always black.
When I switch K-tuner off L-tuner does not run correctly. It is on and it tries to give a picture but it never reaches stable picture. It behaves as if it has very bad signal on the edge of switching off-

 

@malahini - could you try behavior of PIP in your box? I do not have possibility to borrow another DVB-S2 (AVL6222) now to compare results.

[nemosince1996]

I remembered OpenATV. I flashed it and PIP is OK in it. Definitelly it is not faulty hardware.

[littlesat]

Vu f#cked up the procs.. the procs for ijklmnop are all saying I’m the second fbc tuner. so it can be the software do not see the loopthrough from k to l.... I’m getting tired of it. So tuner L cannot tune anything?
Sounds for now it can only be solved by a quick and dirty work a round.... (when no fbc and tuner letter is J or L, so tuner 9 or 11,’then enable loop through as it has to be loop through tuners) crasy!!!!!

Better vu solved the ‘static’ procs....
It also looks like the last tuner has a kind of reverted loop through...

But another question do you have one or two cables connected?’ if so then the loopthrough is not relevant. ... another question you have two dvb-s tuner types inserted. So more tuners are involved here????

Edited by littlesat, 11 August 2019 - 21:35.

[nemosince1996]

Recent configuration:

1st slot dvb-s2x           tuners A,C,D,E,F from unicable2 multiswitch satellites 23,5°E and 19,2°E

                                     tuners B,G,H from unicable2 multiswitch satellites 13,0°E and 0,8°W

2nd slot dvb-t2-mtsif   tuners I,J

3rd slot dvb-s2            tuners K,L two cables from diseq switches satellites 9,0°E, 4,8°E, 4,0°W and 5,0°W

 

Yes, standalone tuner L itself cannot tune anything.

[littlesat]

And tuner k is working and L is dead?
It should be with normal zapping the first tuner it selects...so I still do not fully understand your situation.

[nemosince1996]

Tuner K is always working. To proof that tuner L is really "dead" what seemed to me I scanned all four satellites first with tuner K on and then with tuner K disabled. I received very strange result. Tuner L tuned only one transponder (12224 MHz V 3/4 27500 4,8E) from all four satellites in both cases.

[nemosince1996]

I swapped cables between tuners K and L. Tuner L did not tune anything in this case after restart of box. ... I can try last thing. I mean to swap all tuners between my VU+ Ultimo 4K boxes. But if it is in drivers I cannot expect any positive result.

[littlesat]

When it can tune one transponder on L... then it is most likely not related to a software issue... But it stays weird... Does it switch properly through the DiseqC switches?

 

Tuner L tuned only one transponder (12224 MHz V 3/4 27500 4,8E) from all four satellites in both cases.

Edited by littlesat, 12 August 2019 - 12:47.

[nemosince1996]

Diseqc switches worked correctly several years with Solo2 even when I sent unicable signal  through them. Yesterday I tried and check thoroughly OpenATV without any error in PIP. ... When I observed these problems I installed Solo2 back to be sure that there is not fault in diseqc switches. Bear in mind #69 where I wrote that I swapped cables and it means that signal from diseqc switches goes to opposite tuners. Result is let say the same except this strange transponder. Nothing tuned.

[littlesat]

Solo2 hack only works for tuner a and b... and is intended for the loop through.... do you have issues with loop through.... sounds like it is doing L to K? Then it sounds like we cannot get rid of an if VU hack then.... then I’m afraid it is game over..... in addition it is also difficult to troubleshoot as I do not have your config. OpenAtv’s Nimmanager is a mass and not really helpfull. Still wierd it does tune that one tuner on L...

Can you try to ‘change’ the rf_switch procs in /proc/stb/frontend for the specific tuner via telnet... ?

What happens when you remove the middle tuner? And it becomes I and J?

Does it give tuned fail or nothing... do you see a percentage or dB value

At this moment I have no clue what vu madness might cause what you now experience... I already made some tricky work a round regards this.... in cpp code I also cannot find any clue. For the rest the code is also approx the same

Edited by littlesat, 12 August 2019 - 17:48.

[nemosince1996]

I removed dvb-t2. Dvb-s2 moved to I and J but behavior is the same as it is for K and L. More over letters K,L stayed shaded.

 

Failed tuner shows zero signal. I use HDGlass skin and I can see both percentage and dB scale.

 

I am ready to try everything if you will send me commands which I should apply through telnet.

[littlesat]

With cable the rf switch does not care... are you sure tuner L is still fully functional?
Can you try with just two lnbs without a switch just to verify if the diseqc commands are getting through... maybe you just need to adapt some timing?

Edited by littlesat, 12 August 2019 - 21:45.

[nemosince1996]

What does it mean fully functional? It only runs 100% in PIP on one satellite on channels with the same polarization.

[littlesat]

Then it does always a loop through from k to l ? And never go straight to the input of l.... sounds now I need help from a cpp coder and also wierd it switches backwards... that was also why I say look for a proc... echo 0 or 1 >/proc/stb/frontend/x/rf_switch
Use cat to see the current value first and then try to switch it to the different one (could also be enable/disable instead of 0 or 1.

Edited by littlesat, 12 August 2019 - 22:14.

[nemosince1996]

I changed value of rf_switch to internal (choices external or internal) and then I tried to set  fbc_connect to 1 without any result. If you look to file you see difference for dvb-s2x (frontends 0-7), dvb-t2 (frontends 8,9) and dvb-s2 (frontends 10,11) in fbc_set_id.

Attached Files

•  frontend.txt   4.41KB   4 downloads

[littlesat]

I see the value you have to wire into the rf_switch is internal and external and not 0 or 1. Sorry about that.

 

I also think it is still strange you can get that one transponder.... could it be something on the diseqc switching is not going well so we're looking at the wrong point?

Edited by littlesat, 13 August 2019 - 08:22.

[nemosince1996]

You are focussed on diseqc. I have only one possibility at this time. I will connect cables from diseqc's to dvb-s2x, configure tuners and try it but I am not persuaded that this will tell us more. I expect that this will run correctly.

[nemosince1996]

As I expected PIP runs in all combinations of all four satellites and both polarizations perfectly. You have three times proof (Solo2, OpenATV and dvb-s2x now) that even if there is some strange signal from one transponder diseqc must be ok. I do not have any idea what to do next.