239 replies to this topic

[Neo64]

WTE I've explained the issue two times and you keep draggin in stuff that is totally irrelevant and avoiding the real issue. I suggest you read either one of my previous again and try to understand what they say.

I think that problem and all posts will cut how much you will add one more option in configuration of USALS like all other Teams.

Thanks

[WTE]

WTE I've explained the issue two times and you keep draggin in stuff that is totally irrelevant and avoiding the real issue. I suggest you read either one of my previous again and try to understand what they say.

 

Please check the follow situation as it's probably an enigma2 bug.

You have in the User Interface the follow option: Infobar frontend data source. This has option "Settings" and "Tuner"

 

So what should happen in my opinion is that with "Settings" the information comes from Enigma2 and with "Tuner" the information comes in this case from the Silabs.

What really happen is that in "Tuner" and "Settings" the values from Enigma2 is used and not from the Tuner.

[Erik Slagter]

"Settings" is information from lamedb (so refers that what's in the satellites.xml file or whatever the user entered / scanned himself).

"Tuner" is from driver. That used to be the default.

 

What really happen is that in "Tuner" and "Settings" the values from Enigma2 is used and not from the Tuner.

Fair enough, but why does that only happen on hd51 tuners then?

 

My solo4k says for NPO 1 HD:

    * settings: 12187

    * live: 12186

 

So apparently it can work...

Edited by Erik Slagter, 31 March 2018 - 11:55.

[MCelliotG]

There is no enigma2 bug, simply drivers bug! It also affects all tuners that come natively with Mutant, both Si2166D and the CDX2837 DVB-T2 tuner. This does not report real values either!

To check 100% the bug, you can simply connect any USB tuner on HD51. With these using third party drivers, you see that Live Tuner values work correctly. If it was an Enigma2 bug we would have problem with these too! Clearly not!

Check it for yourselves!

 

The real thing here, and the source of all disagreement is to report issues to Asia and expect any driver update. Anything more is pointless wording!

 

There are even more issues, but I will not even go there. Let's have the most important ones fixed first! Will we?

[WTE]

Fair enough, but why does that only happen on hd51 tuners then?
 

 

My solo4k says for NPO 1 HD:

    * settings: 12187

    * live: 12186

 

So apparently it can work...

 

Right I never disagree about it.

 

Enigma2 is fine, my mistake the setting doesn't work on the fly and you need to change channel to show the effects.

So I still had "Settings" values when it was standing on "Tuner"

Edited by WTE, 31 March 2018 - 12:29.

[Abu Baniaz]

Works on the fly with my non-Mutant receiver.

[MCelliotG]

For what is worth WTE and I had a talk, and it was a good one! Am I right mr WTE?

I really pray all will be good from now on! Every problem has a solution after all!

[Neo64]

 

And where is the solution to this problem, with date of 26.03 or 6.1 neither 4.0 work correctly with Motor.
We are doing a meaningless chat, the other Teams add a line in Configuation 1.2 / USALS / and point ball. In OpenPLI also works after changing that line in etc/eniga2/setting  and follows the annoying mesage "Fail tuner" when you move the antenna, it does not even come out on the images of others after date 23.03 .

That  I offer to try all Betas of this Team, pass PM to a Mod, I just do not understand why it is that delay.
Thank you

Edited by Neo64, 31 March 2018 - 17:51.

[Huevos]

 

 

And where is the solution to this problem, with date of 26.03 or 6.1 neither 4.0 work correctly with Motor.
We are doing a meaningless chat, the other Teams add a line in Configuation 1.2 / USALS / and point ball. In OpenPLI also works after changing that line in etc/eniga2/setting  and follows the annoying mesage "Fail tuner" when you move the antenna, it does not even come out on the images of others after date 23.03 .

That  I offer to try all Betas of this Team, pass PM to a Mod, I just do not understand why it is that delay.
Thank you

 

Solution is in the develop branch. If you are in a big hurry either build PLi develop, or use an image that already contains the commit.

[WanWizard]

Is that commit also present in the rc branch? If not, can you post the commit hash, so I can cherry pick?

[Neo64]

^{Forgive so much annoyance Teachers.}

^Thanks

[Neo64]

Nuevo rc 6.2  work PERFECT - Mutant HD51  !

Thanks

[twol]

I wonder if this driver update will improve anything??

 

[gfeatures] update drivers all models

silabs: update firmware and dvb-fe frontend info

hd530c: fix high cpu load for subtitle and radio
all: improve edid info

Edited by twol, 25 April 2018 - 12:29.

[WTE]

Some people have the drivers for some weeks in test and no report is made.

So I assume everything is now fine

 

 

[kalehrl]

What is the default entry in release 6.2 regarding 'powerMeasurement'?
 

[MCelliotG]

Some people have the drivers for some weeks in test and no report is made.

So I assume everything is now fine

 

 

I made a little report on another thread, so I guess it should be useful to report here after a month of testing (and it was a hectic month)!

 

First of all the fixes were for the better. Overall the situation was improved

 

HOWEVER....

- SNR display increments.

The improvement is obvious, we no longer have the calculated down values and the huge increments, but now the behaviour of Silabs SNR indication is very peculiar. Instead of the default 0.25 we have smaller increments of multipliants of 0.16!

This means the signal is now counted with smaller increments, which normally would make the readings more precise, however the 0.16 span occurs very rarely. Instead we see increments of 0.32, 0.48 and more often 0.64.

I must say this is not so severe, since the signal in general is around the same values as before. The question is why since the default of Silabs demods is 0.25 by factory we see now different increments? Has the R270T tuner anything to do with that?

 

- The lower initial SNR has not been fixed. So when we tune to a new transponder instead of the correct signal for the first second we see a smaller signal that rises to the expected value after. This affect both Silabs and the DVB-T2 tuner, so I guess it's more of a different issue than simply the drivers. Not so severe either, we can live with this as well.

 

- The real time values HAS NOT BEEN FIXED. What has happened is that now the real time values duplicate and report the lamedb values. This is totally wrong. The real time values should display the correct tuned values regardless of what we input.

For instance if the correct frequency is 11823 H DVB-S2 8PSK 3/4 and we input 11823 H DVB-S2 QPSK 1/2, Silabs will also tune the frequency but the real time values should show the first correct values and not what the user or the satellite xml inputs.

I will give more examples later.

At least we don't see the 10600/9750 values anymore, but the change was cosmetic to cover up the problem and not a real solution. The DVB-T2 tuner has not been fixed either.

 

More issues will be reported later also!

Edited by MCelliotG, 13 May 2018 - 14:34.

[Huevos]

It is a pity the commit to fix this tuner breaks scanning on all boxes. It's been reported, but right now it doesn't look like anyone cares.

[pieterg]

It is a pity the commit to fix this tuner breaks scanning on all boxes. It's been reported, but right now it doesn't look like anyone cares.

are you talking about this https://github.com/O...c96ca95eadf3ac9 commit?
That's not related to this tuner as far as I know.

[Huevos]

Yes, that commit fixed this tuner taking forever to get lock after a motor event.

[pieterg]

ok, in that case this tuner probably generates the FE_TIMEDOUT event, which is now properly handled by e2.