One of the problems I hit when investigating different tuners was that the different display features appear to use different data, and/or display the available data incorrectly. Using the logic I proposed for DVB-T frequency finder both Si2168 & Si2169 provide sensibly varying values. The Si2169 responds sensibly to the "signalQuality = self.frontend.readFrontendData(iFrontendInformation.snrValue)", but the Si2168 does not and so the "signalQuality = self.frontend.readFrontendData(iFrontendInformation.signalQualitydB) is invoked and gives values that appear to be in milliBels - i.e. 30 dB is reported as 3000.
The following SNRdB results from the webif "web/signal?AGC=" command may be of interest (the main figures are averages across 20 samples, and those in brackets are the lowest figures in those samples) :
Code:
<----------------- Signal SNR ----------------->
Name Status Tuner A Tuner B Tuner C Tuner D
Si2169 Si2169 Si2169 Si2168
1 PSB1 In Use 340 (334) 301 (301) 340 (340) 31 (31)
2 PSB2 In Use 348 (347) 341 (340) 340 (334) 32 (31)
3 PSB3 In Use 354 (353) 348 (347) 347 (308) 31 (31)
4 COM4 In Use 360 (353) 358 (353) 360 (360) 33 (32)
5 COM5 In Use 360 (360) 343 (340) 341 (340) 33 (33)
6 COM6 In Use 355 (353) 284 (275) 301 (301) 28 (27)
Note that the "HD" mux is being shown apparently correctly, unlike Signal finder where I have seen the same problem as reported by ccs.
It would also appear that the Si2169 reports are in centiBels, as they seem to be a factor of 10 larger than for the Si2168. However as DVB-T frequency finder is only interested in relative levels, that would not affect the results.
EMJB