239 replies to this topic

[twol]

Do you mean the old drivers would not work with S2X tuners? If so, you are probably right.
Or do you mean that the issue concerns S2X tuners only? If so, this is probably not the case.

No the old drivers probably will not support the s2x which came out later.
The lock issue is apparently on both tuner types.

[WanWizard]

Are OpenPLi images available for HD51, dated October/November 2016?

 

Not with us, we only keep 6 months of images in backup, due to storage limitations.

[MCelliotG]

One major issue is that Enigma2 does not get the real time values from the tuners, and this happens also with the DVB-T2 tuner (CXD2837).

 hd51dvbt2.jpg   94.85KB   5 downloads

 

This is what the DVB-T2 tuner reports

 hd51tunervalues.jpg   138.9KB   7 downloads

As you can see everything is set to auto even when this info is set to be read from the tuner

 

In direct comparison, here's what shows on OSmini's Panasonic DVB-T2 tuner

 osminitunervalues.jpg   126.23KB   6 downloads

 

Now, OK two different tuners, two different drivers, but how much of a coincidence is it for both HD51 tuners to have faulty drivers? As far as I know Zgemma has the same issue, and can someone with a SF4008 report if the issue is there too?

I remember the initial images of OSmini had this problem as well, but was fixed.

[twol]

I haven‘t heard of any lock issues with the SF4008.... and I am sure Huevos would have said if there is an issue.

[MCelliotG]

I don't refer to the lock issue, that's totally different. I talk specifically about the real time tuner values report. It does not work on HD51's internal tuners. Does Octagon report correctly?

[MCelliotG]

I connected a usb tuner and it reports correctly btw. So is it only a driver issue?

Edited by MCelliotG, 23 February 2018 - 17:26.

[Robinson]

As regards those "real-time" values, are you absolutely sure they are not simply copied from lamedb even though the setting is supposed to use tuner values?

Can you verify it?

[MCelliotG]

Absolutely sure. I deliberately perform many manual scans with modified parameters (i.e. wrong fec as silabs ignores that) and while settings value displays the wrong parameter (the lamedb entry), the tuner value will always return the tuned ones if the drivers or whatever elsee is supposed to supports it. Mutant has no support for their internal tuners as it seems.

[Robinson]

OK, thanks.

Just a question regarding reporting of tuner values,

If you tune to an offset frequency, for example 10710 instead of 10719, does the tuner report correctly the strongest signal or does it stay at 10710?

[MCelliotG]

In OSmini (correct values report) it goes back to a center frequency (you see the tuner trying to update) but I don't know in what margin. If I tune +/- 5 it goes to the correct frequency, haven't tried a bigger gap. The SR, FEC etc are updated as they should. In HD51 you get the classic 10600 or 9750 whatever you enter. If the settings value is on you see the frequency you input!

Big, big tuner problems and I don't know how to report them to anyone that can fix them.

Edited by MCelliotG, 24 February 2018 - 00:33.

[Erik Slagter]

If you tell it like this, it seems like actually a driver bug in some drivers?

[MCelliotG]

But it is exactly that. Big problems in drivers. Just comparing how the very same tuner behaves in Dreamboxes, it's like a whole different tuner. Neither the values are rounded, the tuner reports all parameters correctly (except DVBS2X is returned as regular DVBS2 naturally) and not to mention native blindscan.
I don't know what the manufacturer does. All open images have these issues with Silabs. It's a pity cause it's an excellent tuner, perhaps the best ever to be in an Enigma2 receiver but support for it is very bad.

[Erik Slagter]

Did you also check the VU+ Zero4k (which also comes with a Si2166 tuner)?

[athoik]

The frequency is not updated.

It should be 11836 but remains 11832.

Attached Files

•  1_0_1_6DCA_44D_1_C00000_0_0_0_settings.jpg   74.66KB   8 downloads
•  1_0_1_6DCA_44D_1_C00000_0_0_0_live.jpg   82.1KB   7 downloads

[MCelliotG]

Did you also check the VU+ Zero4k (which also comes with a Si2166 tuner)?

I don't own a zero 4k but as far as I've seen they have modified some stuff for their obsession with not supporting snr in db so that the tuners show only percentages. So I can't tell if the real time report works there at least!

Edited by MCelliotG, 25 February 2018 - 14:07.

[Neo64]

After the emergence of the new 2X tuner, all the images of Open Pli and all the other people who write about this decoder have a glitch that is definitely irritating when working with a motorized antenna.

When switching a channel from one satellite to another and moving the antenna, the signal appears after 20-30 seconds and after another 5-6 second picture.

 

With the image of Oren Pli of 10.12.2016, Mutant 51HD works perfectly with the tuner AVL, with All new images from 05.2017 to today the decoder has the commented problem, which for motorized users is more than annoying, the same problem with Open PLI  has the new ZGemma H7S. If Mutant have a Support Forum, please put a link to it to burn their tires, because the bug should come from their official images.

 

Thanks

Edited by Neo64, 28 February 2018 - 07:54.

[Robinson]

We can therefore assume that the "rotor lock" bug was introduced when they updated their drivers in order to support S2X tuners.

This bug concerns both Mutant HD51, AX HD51 as well as Zgemma H7S models.

I guess they all use the same S2/S2X tuners and so the same tuner drivers.

So who is to blame? Mutant? AX? Zgemma? Silicon Labs?

[Rob van der Does]

Zgemma has always been a clone manufacturer, so my guess is Mutant.

[Neo64]

We can therefore assume that the "rotor lock" bug was introduced when they updated their drivers in order to support S2X tuners.

This bug concerns both Mutant HD51, AX HD51 as well as Zgemma H7S models.

I guess they all use the same S2/S2X tuners and so the same tuner drivers.

So who is to blame? Mutant? AX? Zgemma? Silicon Labs?

Guilt, of course only the manufacturer has it .

If the main drivers are the base of the Teams, they are going to be at fault. I've been in this puddle for a long time and always a manufacturer brings out a product in the market that needs to be sold and hands raised, bored of giving a touch of a thing, annoying and still bothering

[WanWizard]

Zgemma has always been a clone manufacturer, so my guess is Mutant.

 

Maybe in the early days, but none of the boxes supported by OpenPLi are clones! On the contrary, currently with the h9 they are ahead of all competition, with the new HiSil chipset.