Last edited by Huevos; 26-09-18 at 11:53.
If you can't receive those muxes there is no need for custom transponders.
Which .xml file?
This because what you have done is a pre-scan. That negates the need for a custom transponder.
ABM only requires a tuner to be enabled.
Thanks, I guess there are lots of these gems hiding somewhere (I've never looked for them, mind.)
The command finds data for all mux's eg -Signal finder only finds data for SD mux's, nothing comes up on the HD mux's.Code:<e2frontendstatus> <e2snrdb>373.55 dB</e2snrdb> <e2snr>100 %</e2snr> <e2ber>0</e2ber> <e2acg>0 %</e2acg> </e2frontendstatus>
What I guess is happening is the values in terrestrial.xml don't correspond with your mast. In Signalfinder if you switch to user defined transponder and then to T2 it should show signal.
Last edited by Huevos; 26-09-18 at 13:19.
ccs (26-09-18)
If you are performing this manually as part of a test and have left Menu-> tuner config -> manual scan -> Sytem =DVB-T then you will only pick up SD MUxs when you slowly select each transmitter channel. If you change that setting to Auto or DVB-T2 you should pick up both SD and HD MUXs with a test manual scan.
Xtrend ET10K, 2 x satellite tuners 28.2 (Sky FTA), 2 x hybrid (UK Freeview), Zgemma H9S (satellite)
abu baniaz (30-05-19)
My suspicion is that it is frontend.cpp that is the problem, rather than the drivers, and it has a lot of tuner-specific code, but nothing for the Si2168/9. Who is likely to sort out what is wrong and fix it, and what sort of timescale is that going to take?
While I appreciate your position but:
- In the short term you will continue to waste time responding to users with problems that my code avoids (e.g. incorrect terrestrial_finder.xml files being reported).
- It does seem likely that new tuners will appear and suffer from the same problems, so you are in danger of creating work in the long term for yourself as problems keep arising.
It does seem to be pity to deny people with Si2168/9 tuners a working feature for what a suspect will be a significant time for the sake of a few lines of code that you could remove once the source of the problem has been fixed. N.B. I suspect the TerrestrialScan plug-in suffers from the same problems, so that is not a useful alternative as an interim measure for people with Si2168/9 tuners.
If you really are adamant not to include my fixes to get better data, I suggest the user advice along the lines of my warning message when data is missing, and a log of the tuner type in use, would be useful additions.
EMJB
Xtrend Xt10000 with 3 Freeview tuners