107 replies to this topic

[littlesat]

I have no idea what is going on here... I can only observe that VU's procs are giving false information. The procs also indicate you only can do an FR switch from K to L and not from L to K. I also do not see why ATV does work-a-round this as they have really wierd spaghetti code arround this topic. Can you check if ATV also have the same procs stupid things? If they do not have it we need to look at the BSP (VU need to change it).

When you have a 2nd fbc tuner can you try it in the middle slot as only for the last tuner slots the procs seems to be good.

 

As I do not have your tuner in the middle for me it is impossible to troubleshoot and debug/work-a-round it. I just limited to let you try something which delays investigation and solution.

[nemosince1996]

Give me some time and I try what you need. I can use fbc tuners from my old box to place them to second slot. I will flash OpenATV and I will provide you with data from frontends.
You are right it takes time because I cannot play with it all day and I am not an expert which could search solutions himself. You do not need to appologize. Your position is clear you depend on what I give you.

[littlesat]

I'm afraid with your patience you'll become an expert.

But I suppose for the rest it is working... except for the DVB-S2 tuner in the last slot...?

Edited by littlesat, 13 August 2019 - 10:44.

[nemosince1996]

Yes, the rest except dvb-s2 works. Small problem appeared with dvb-t2 mtsif but I did not want to mix it with existing one. I will come to it later.

Back to dvb-s2: it did not change anything in bad behaviour and functionality of dvb-s2 when I inserted fbc tuners to slot 2. Everything stays as it was.

Now I will focus on OpenATV.

Attached Files

•  frontend_2x_fbc.txt   6.12KB   6 downloads

[nemosince1996]

I have problems with configuration of fbc tuners in OpenATV. They do not have my unicable2 multiswitch in configuration. I only configured dvb-s2 and it works ok (I mean PIP). If you tell me name of configuration file in OpenPLI can I use it in OpenATV?

Attached Files

•  frontend_2x_fbc_ATV.txt   537bytes   2 downloads

[littlesat]

Nope they are not complatible... openatv’s unicable.xml is a bit more complicated and not consequenf. With openpli at least you can also set the parameters manually

[littlesat]

Mmm the procs look the same....

[nemosince1996]

My Inverto unicable multiswitches use each two wideband lnb's which are addressed position1 and 2. There is no device with such a possibility in ATV. From this point of view OpenPLI is much more higher league.

 

Do you mean that there is nothing significant which could help to solve it?

[littlesat]

better to post it on the atv forum or use openpli
That you can see a transponder on tuner L indicates something is working and that was why I was thinking about adapt diseqc timing and/or somewhere a stupid setting that disturbs is... and not the software... eg 22KHz burst 14/18 Volt on/off???

Edited by littlesat, 14 August 2019 - 06:33.

[arn354]

You should provide the product name.

If you compare your inverto product specification with any other existing configuration in unicable.xml you could also use a different product - as long parameters are identical, the manufacturer and naming is not relevant.

for example a inverto unicable/Jess matrix with 4 positions: https://github.com/o...icable.xml#L273

 

In addition you can also completely manually configure your unicable/jess matrix according to the specifications of your user manual of that unicable/jess matrix.

Edited by arn354, 14 August 2019 - 07:51.

[nemosince1996]

I was not successful to force tuner L running correctly even if I changed all possible parameters. Nothing has change for better and it does not work with some settings at all what was expected.

 

@arn354 - It is really for discussion on OpenATV forum but one remark. There are different parameters for IDLU-UWT110-CUO10-32P which I have in unicable.xml existing in  image and in github. It is important for me that it does not work.

[littlesat]

Also with satellite equipment system plugin?

[nemosince1996]

I have not used it so far. I installed it and played with setting of parameters without any efect. If you have some idea what to change and how, I will do it. I have already prolonged timing by 500 ms separately or more items together.
Today I can try it but I won't be at home next three consequent days.

[littlesat]

At least it is a very wierd issue...

 

It would also be helpfull go get some log data via putty/console...

 

init 4

ENIGMA_DEBUG_LVL=4 enigma2

 

So I can see what's happening when you try to tune tuner L

Edited by littlesat, 15 August 2019 - 09:38.

[littlesat]

Another thing... do you have LCD4linux installed? If so please remove it and retry...

[nemosince1996]

1) first file - K running on screen and L running in PIP, the same polarization

2) second file - L running on screen and K running in PIP, the same polarization

3) third file - K running on screen and L not running in PIP (black field), opposite polarization

4) fourth file - L not running (black screen) and K running in PIP, opposite polarization

 

 

 

Attached Files

•  K_on_active_screen-L_on_running_PIP.log   709.5KB   4 downloads
•  L_on_active_screen-K_on_running_PIP.log   709.14KB   1 downloads
•  K_on_active_screen-L_not_running_PIP.log   709.01KB   1 downloads
•  L_black_screen-K_on_running_PIP.log   689.86KB   2 downloads

[littlesat]

As far I can see uner 11 = L is never used, I only see in use tuner 10 = K

 

In the L_black_skreen- K in running PIP I discovered the following in the tuner initialization.

 

[eDVBFrontend10] opening frontend

[eDVBFrontend10] opening frontend

[eDVBFrontend] opening /dev/dvb/adapter0/frontend10 failed: Device or resource busy

[eDVBFrontend11] opening frontend

[eDVBFrontend11] opening frontend

[eDVBFrontend] opening /dev/dvb/adapter0/frontend11 failed: Device or resource busy

 

It could be that E2 was stopped here somehow improperly and the drivers keep the tuners busy. But it might be this log is invalid as both tuners were unusable during this enigma2 session.

 

As far I can see tuner 11 = L was never used. I can only speculate E2 thinks there are no 'satellites' available on that connection, so it will not be use it except when it can loopthrough 10 = K. So I hope the undelaying issue is a configuration issue. Can you please send me your nim configuration for verification?

 

cat /etc/enigma2/settings | grep Nims

Edited by littlesat, 15 August 2019 - 13:43.

[WanWizard]

English !

[nemosince1996]

You have not specified conditions for "cat". It is running K on screen and L in PIP.

Attached Files

•  Nims.txt   7.71KB   8 downloads

[littlesat]

I see differences in the config that are somehow contra-indicated, different diseqc mode, commited switch and uncommited switch different and tonemode=OFF enz... order not concequent etc...

 

Red the differences highlighted and yellow can be ignored due to the config is on advanced... (that are simple parameters that are kept).

 

As far I can see tuner 11 = L cannot switch the uncommitted switch..... and tuner 10 = K switches an uncommited switch with 3 LNBs on 1,2,3 where one LNB has two satpositions.

 

 Capture.PNG   77.77KB   4 downloads

Edited by littlesat, 15 August 2019 - 14:09.