Jump to content


Photo

Wrong frequency in extra-infobar

H7S

  • Please log in to reply
24 replies to this topic

Re: Wrong frequency in extra-infobar #21 Huevos

  • PLi® Contributor
  • 2,347 posts

+116
Excellent

Posted 28 January 2018 - 00:05

So we can safely assume drivers for these brands (Zgemma and Mut@nt) may well be developed by the same people.

By the way, it is not only the frequency which is incorrect but also SR=0 and FEC=auto.

No, you can't assume that. More likely is the manufacturer of the tuner chip has supplied both with the same (dodgy?) code.



Re: Wrong frequency in extra-infobar #22 Robinson

  • Senior Member
  • 2,500 posts

+30
Good

Posted 28 January 2018 - 00:12

Huevos, do you experience the wrong frequency/SR/FEC on your HD51?

Do you still use this box? What tuner do you have? S2 or S2X?


ET9000, OpenPLi 4.0, 13E, 19E

HD51, OpenPLi 6.2, 75E - 30W


Re: Wrong frequency in extra-infobar #23 Rob van der Does

  • Senior Member
  • 7,731 posts

+184
Excellent

Posted 28 January 2018 - 05:56

By the way, as the author of this thread pointed out:
"The correct frequency can be spotted for a second while zapping."  It just immediately turns into 9750 or 10600 in the second infobar.

Possibly because the lamedb values are used until lock?
PLi has the option to show just the database values or the tuner feed back. 
 

So we can safely assume drivers for these brands (Zgemma and Mut@nt) may well be developed by the same people.

Possibly; don't forget that Zgemma has a proven track record of counterfeit cloning boxes.

Re: Wrong frequency in extra-infobar #24 Huevos

  • PLi® Contributor
  • 2,347 posts

+116
Excellent

Posted 28 January 2018 - 06:19

Huevos, do you experience the wrong frequency/SR/FEC on your HD51?

Do you still use this box? What tuner do you have? S2 or S2X?

I have never owned an HD51.



Re: Wrong frequency in extra-infobar #25 Robinson

  • Senior Member
  • 2,500 posts

+30
Good

Posted 28 January 2018 - 14:23

 

By the way, as the author of this thread pointed out:
"The correct frequency can be spotted for a second while zapping."  It just immediately turns into 9750 or 10600 in the second infobar.

Possibly because the lamedb values are used until lock?
PLi has the option to show just the database values or the tuner feed back. 
 

 

Makes sense.

Although, if someone can read the code for displaying the values in the second infobar, could you please check if they are indeed taken from lamedb before lock? If so, then that must be driver fault.

Otherwise, it might suggest that something overrrides these values.


ET9000, OpenPLi 4.0, 13E, 19E

HD51, OpenPLi 6.2, 75E - 30W






Also tagged with one or more of these keywords: H7S

1 user(s) are reading this topic

0 members, 1 guests, 0 anonymous users