Dvb-t detaile scan

[dax]

Hi at all, is it possible to do a detailed scan on dvb-t channel? I mean, when i do a scan the tuner save the parameter like

474000 mhz auto auto auto auto
I would a string like this

CH 21 8k 64qam 2/3 1/4
Is it possible by modify a terrestrial.xml file (removing auto mode and add every combination for each frequency)? And for the channel number instead of frequency?
Thanks

[dax]

I' ve modified the terrestrial.xml file but doesn't work, no channel found

<transponder centre_frequency="474000000" bandwidth="0" constellation="0" code_rate_hp="0" guard_interval="0" transmission_mode="0"/> <!--ch21 -->
<transponder centre_frequency="474000000" bandwidth="0" constellation="1" code_rate_hp="0" guard_interval="0" transmission_mode="0"/> <!--ch21 -->
<transponder centre_frequency="474000000" bandwidth="0" constellation="2" code_rate_hp="0" guard_interval="0" transmission_mode="0"/> <!--ch21 -->
<transponder centre_frequency="474000000" bandwidth="0" constellation="0" code_rate_hp="1" guard_interval="0" transmission_mode="0"/> <!--ch21 -->
<transponder centre_frequency="474000000" bandwidth="0" constellation="1" code_rate_hp="1" guard_interval="0" transmission_mode="0"/> <!--ch21 -->
<transponder centre_frequency="474000000" bandwidth="0" constellation="2" code_rate_hp="1" guard_interval="0" transmission_mode="0"/> <!--ch21 -->
<transponder centre_frequency="474000000" bandwidth="0" constellation="0" code_rate_hp="2" guard_interval="0" transmission_mode="0"/> <!--ch21 -->
<transponder centre_frequency="474000000" bandwidth="0" constellation="1" code_rate_hp="2" guard_interval="0" transmission_mode="0"/> <!--ch21 -->
<transponder centre_frequency="474000000" bandwidth="0" constellation="2" code_rate_hp="2" guard_interval="0" transmission_mode="0"/> <!--ch21 -->
<transponder centre_frequency="474000000" bandwidth="0" constellation="0" code_rate_hp="3" guard_interval="0" transmission_mode="0"/> <!--ch21 -->
<transponder centre_frequency="474000000" bandwidth="0" constellation="1" code_rate_hp="3" guard_interval="0" transmission_mode="0"/> <!--ch21 -->
<transponder centre_frequency="474000000" bandwidth="0" constellation="2" code_rate_hp="3" guard_interval="0" transmission_mode="0"/> <!--ch21 -->
<transponder centre_frequency="474000000" bandwidth="0" constellation="0" code_rate_hp="4" guard_interval="0" transmission_mode="0"/> <!--ch21 -->
<transponder centre_frequency="474000000" bandwidth="0" constellation="1" code_rate_hp="4" guard_interval="0" transmission_mode="0"/> <!--ch21 -->
<transponder centre_frequency="474000000" bandwidth="0" constellation="2" code_rate_hp="4" guard_interval="0" transmission_mode="0"/> <!--ch21 -->
<transponder centre_frequency="474000000" bandwidth="0" constellation="0" code_rate_hp="0" guard_interval="1" transmission_mode="0"/> <!--ch21 -->
<transponder centre_frequency="474000000" bandwidth="0" constellation="1" code_rate_hp="0" guard_interval="1" transmission_mode="0"/> <!--ch21 -->
<transponder centre_frequency="474000000" bandwidth="0" constellation="2" code_rate_hp="0" guard_interval="1" transmission_mode="0"/> <!--ch21 -->
<transponder centre_frequency="474000000" bandwidth="0" constellation="0" code_rate_hp="1" guard_interval="1" transmission_mode="0"/> <!--ch21 -->
<transponder centre_frequency="474000000" bandwidth="0" constellation="1" code_rate_hp="1" guard_interval="1" transmission_mode="0"/> <!--ch21 -->
<transponder centre_frequency="474000000" bandwidth="0" constellation="2" code_rate_hp="1" guard_interval="1" transmission_mode="0"/> <!--ch21 -->
<transponder centre_frequency="474000000" bandwidth="0" constellation="0" code_rate_hp="2" guard_interval="1" transmission_mode="0"/> <!--ch21 -->
<transponder centre_frequency="474000000" bandwidth="0" constellation="1" code_rate_hp="2" guard_interval="1" transmission_mode="0"/> <!--ch21 -->
<transponder centre_frequency="474000000" bandwidth="0" constellation="2" code_rate_hp="2" guard_interval="1" transmission_mode="0"/> <!--ch21 -->
<transponder centre_frequency="474000000" bandwidth="0" constellation="0" code_rate_hp="3" guard_interval="1" transmission_mode="0"/> <!--ch21 -->
<transponder centre_frequency="474000000" bandwidth="0" constellation="1" code_rate_hp="3" guard_interval="1" transmission_mode="0"/> <!--ch21 -->
<transponder centre_frequency="474000000" bandwidth="0" constellation="2" code_rate_hp="3" guard_interval="1" transmission_mode="0"/> <!--ch21 -->
<transponder centre_frequency="474000000" bandwidth="0" constellation="0" code_rate_hp="4" guard_interval="1" transmission_mode="0"/> <!--ch21 -->
<transponder centre_frequency="474000000" bandwidth="0" constellation="1" code_rate_hp="4" guard_interval="1" transmission_mode="0"/> <!--ch21 -->
<transponder centre_frequency="474000000" bandwidth="0" constellation="2" code_rate_hp="4" guard_interval="1" transmission_mode="0"/> <!--ch21 -->
<transponder centre_frequency="474000000" bandwidth="0" constellation="0" code_rate_hp="0" guard_interval="2" transmission_mode="0"/> <!--ch21 -->
<transponder centre_frequency="474000000" bandwidth="0" constellation="1" code_rate_hp="0" guard_interval="2" transmission_mode="0"/> <!--ch21 -->
<transponder centre_frequency="474000000" bandwidth="0" constellation="2" code_rate_hp="0" guard_interval="2" transmission_mode="0"/> <!--ch21 -->
<transponder centre_frequency="474000000" bandwidth="0" constellation="0" code_rate_hp="1" guard_interval="2" transmission_mode="0"/> <!--ch21 -->
<transponder centre_frequency="474000000" bandwidth="0" constellation="1" code_rate_hp="1" guard_interval="2" transmission_mode="0"/> <!--ch21 -->
<transponder centre_frequency="474000000" bandwidth="0" constellation="2" code_rate_hp="1" guard_interval="2" transmission_mode="0"/> <!--ch21 -->
<transponder centre_frequency="474000000" bandwidth="0" constellation="0" code_rate_hp="2" guard_interval="2" transmission_mode="0"/> <!--ch21 -->
<transponder centre_frequency="474000000" bandwidth="0" constellation="1" code_rate_hp="2" guard_interval="2" transmission_mode="0"/> <!--ch21 -->
<transponder centre_frequency="474000000" bandwidth="0" constellation="2" code_rate_hp="2" guard_interval="2" transmission_mode="0"/> <!--ch21 -->
<transponder centre_frequency="474000000" bandwidth="0" constellation="0" code_rate_hp="3" guard_interval="2" transmission_mode="0"/> <!--ch21 -->
<transponder centre_frequency="474000000" bandwidth="0" constellation="1" code_rate_hp="3" guard_interval="2" transmission_mode="0"/> <!--ch21 -->
<transponder centre_frequency="474000000" bandwidth="0" constellation="2" code_rate_hp="3" guard_interval="2" transmission_mode="0"/> <!--ch21 -->
<transponder centre_frequency="474000000" bandwidth="0" constellation="0" code_rate_hp="4" guard_interval="2" transmission_mode="0"/> <!--ch21 -->
<transponder centre_frequency="474000000" bandwidth="0" constellation="1" code_rate_hp="4" guard_interval="2" transmission_mode="0"/> <!--ch21 -->
<transponder centre_frequency="474000000" bandwidth="0" constellation="2" code_rate_hp="4" guard_interval="2" transmission_mode="0"/> <!--ch21 -->
<transponder centre_frequency="474000000" bandwidth="0" constellation="0" code_rate_hp="0" guard_interval="3" transmission_mode="0"/> <!--ch21 -->
<transponder centre_frequency="474000000" bandwidth="0" constellation="1" code_rate_hp="0" guard_interval="3" transmission_mode="0"/> <!--ch21 -->
<transponder centre_frequency="474000000" bandwidth="0" constellation="2" code_rate_hp="0" guard_interval="3" transmission_mode="0"/> <!--ch21 -->
<transponder centre_frequency="474000000" bandwidth="0" constellation="0" code_rate_hp="1" guard_interval="3" transmission_mode="0"/> <!--ch21 -->
<transponder centre_frequency="474000000" bandwidth="0" constellation="1" code_rate_hp="1" guard_interval="3" transmission_mode="0"/> <!--ch21 -->
<transponder centre_frequency="474000000" bandwidth="0" constellation="2" code_rate_hp="1" guard_interval="3" transmission_mode="0"/> <!--ch21 -->
<transponder centre_frequency="474000000" bandwidth="0" constellation="0" code_rate_hp="2" guard_interval="3" transmission_mode="0"/> <!--ch21 -->
<transponder centre_frequency="474000000" bandwidth="0" constellation="1" code_rate_hp="2" guard_interval="3" transmission_mode="0"/> <!--ch21 -->
<transponder centre_frequency="474000000" bandwidth="0" constellation="2" code_rate_hp="2" guard_interval="3" transmission_mode="0"/> <!--ch21 -->
<transponder centre_frequency="474000000" bandwidth="0" constellation="0" code_rate_hp="3" guard_interval="3" transmission_mode="0"/> <!--ch21 -->
<transponder centre_frequency="474000000" bandwidth="0" constellation="1" code_rate_hp="3" guard_interval="3" transmission_mode="0"/> <!--ch21 -->
<transponder centre_frequency="474000000" bandwidth="0" constellation="2" code_rate_hp="3" guard_interval="3" transmission_mode="0"/> <!--ch21 -->
<transponder centre_frequency="474000000" bandwidth="0" constellation="0" code_rate_hp="4" guard_interval="3" transmission_mode="0"/> <!--ch21 -->
<transponder centre_frequency="474000000" bandwidth="0" constellation="1" code_rate_hp="4" guard_interval="3" transmission_mode="0"/> <!--ch21 -->
<transponder centre_frequency="474000000" bandwidth="0" constellation="2" code_rate_hp="4" guard_interval="3" transmission_mode="0"/> <!--ch21 -->
<transponder centre_frequency="474000000" bandwidth="0" constellation="0" code_rate_hp="0" guard_interval="3" transmission_mode="0"/> <!--ch21 -->
<transponder centre_frequency="474000000" bandwidth="0" constellation="1" code_rate_hp="0" guard_interval="3" transmission_mode="0"/> <!--ch21 -->
<transponder centre_frequency="474000000" bandwidth="0" constellation="2" code_rate_hp="0" guard_interval="3" transmission_mode="0"/> <!--ch21 -->
<transponder centre_frequency="474000000" bandwidth="0" constellation="0" code_rate_hp="1" guard_interval="3" transmission_mode="0"/> <!--ch21 -->
<transponder centre_frequency="474000000" bandwidth="0" constellation="1" code_rate_hp="1" guard_interval="3" transmission_mode="0"/> <!--ch21 -->
<transponder centre_frequency="474000000" bandwidth="0" constellation="2" code_rate_hp="1" guard_interval="3" transmission_mode="0"/> <!--ch21 -->
<transponder centre_frequency="474000000" bandwidth="0" constellation="0" code_rate_hp="2" guard_interval="3" transmission_mode="0"/> <!--ch21 -->
<transponder centre_frequency="474000000" bandwidth="0" constellation="1" code_rate_hp="2" guard_interval="3" transmission_mode="0"/> <!--ch21 -->
<transponder centre_frequency="474000000" bandwidth="0" constellation="2" code_rate_hp="2" guard_interval="3" transmission_mode="0"/> <!--ch21 -->
<transponder centre_frequency="474000000" bandwidth="0" constellation="0" code_rate_hp="3" guard_interval="3" transmission_mode="0"/> <!--ch21 -->
<transponder centre_frequency="474000000" bandwidth="0" constellation="1" code_rate_hp="3" guard_interval="3" transmission_mode="0"/> <!--ch21 -->
<transponder centre_frequency="474000000" bandwidth="0" constellation="2" code_rate_hp="3" guard_interval="3" transmission_mode="0"/> <!--ch21 -->
<transponder centre_frequency="474000000" bandwidth="0" constellation="0" code_rate_hp="4" guard_interval="3" transmission_mode="0"/> <!--ch21 -->
<transponder centre_frequency="474000000" bandwidth="0" constellation="1" code_rate_hp="4" guard_interval="3" transmission_mode="0"/> <!--ch21 -->
<transponder centre_frequency="474000000" bandwidth="0" constellation="2" code_rate_hp="4" guard_interval="3" transmission_mode="0"/> <!--ch21 -->
Why?

[Huevos]

Post the region line.

[dax]

Here

<terrestrial name="Europe, Middle East, Africa: DVB-T Frequencies" flags="5">
Missed some arguments?

[Joe_90]

Why are you doing this? Putting all tuner permutations in, I mean.
Auto will generally work and the tuner will find the appropriate settings. I's possibly only in the case of DVB-T vs DVB-T2 where you might need to specify that you want a T2 scan.
As regards your xml changes, is your local transmitter on UHF Ch 21 (474MHz)? If you scan all of the UHF band you should pick up the relevant transmitters.

[Huevos]

Why are you doing this? Putting all tuner permutations in, I mean. Looks like some sort of strange software blind scan. :confused:

[dax]

Why are you doing this? Putting all tuner permutations in, I mean.
Auto will generally work and the tuner will find the appropriate settings. I's possibly only in the case of DVB-T vs DVB-T2 where you might need to specify that you want a T2 scan.
As regards your xml changes, is your local transmitter on UHF Ch 21 (474MHz)? If you scan all of the UHF band you should pick up the relevant transmitters.
No, no, i'll explain: i'm looking for this feature because broadcast is my job, so when i go to dvb-t channel list i would see the detailed channel parameter (add from this (https://github.com/OpenViX/enigma2/commit/d9ae1010b3ea83dcb1bd9f759c2777a6e2e1446b) commit) instead of 'DVB-T 421.000 MHz auto auto auto auto'. I would like to see a string

DVB-T CH21 8MHz 8k QAM64 2/3 1/4
If i do a normal scan this is not possible so i have thinked up about the terrestrial.xml but doesn't work.
In my example above i put only channel 21 but my terrestrial.xml contains all channels 21-60 (with each possible combination) and i can also add combinations for dvb-t2.
I hope I made myself clear:)

[Joe_90]

Ok - so your issue is with the new transponder/multiplex information which is displayed at the bottom of the channel list?

If your job is in broadcasting then you could set your multiplex details exactly in the xml as you are trying to do, but I think the display information would be the parameter settings rather than the actual transmitter characteristics. If you are in the UK the multiplex info is available from ukfree.tv. UHF reception conditions would mean that you would be only able to receive from a limited number of transmitters, so you should be able to input those details, rather than every UHF channel from 21 - 60, which would be a waste unless you are into moving your receiver around the country!

As I don't know whether you are receiving from Freeview in the UK or located elsewhere I can't comment on your specific case, but here are my details on my box. I'm using the Ireland section of the terrestrial.xml file which I have supplied to the team. This contains the correct tuner settings for all transmitters in the Saorview DVB-T system and does not use the "auto" settings.

[dax]

Ok - so your issue is with the new transponder/multiplex information which is displayed at the bottom of the channel list?
Yes, you're right! Moreover i think that 'auto auto auto' is useless:)

If your job is in broadcasting then you could set your multiplex details exactly in the xml as you are trying to do, but I think the display information would be the parameter settings rather than the actual transmitter characteristics. If you are in the UK the multiplex info is available from ukfree.tv. UHF reception conditions would mean that you would be only able to receive from a limited number of transmitters, so you should be able to input those details, rather than every UHF channel from 21 - 60, which would be a waste unless you are into moving your receiver around the country!
Yes, i can set the multiplexer details but only for my region (and not the whole) because in Italy we have some differents regional provider with different configuration. If i write a file it doesn't work on other regions but now begin to my region:). And also i have not to moving my receiver around the country.
The only method to display the detailed info that i've found is a manual scan for each channel by inserting the exactly parameters. Very annoying.
Tomorrow i try to write a terrestrial.xml like you said, because my previous file show a wrong parameters. Don't ask me why, i don' t known!

As I don't know whether you are receiving from Freeview in the UK or located elsewhere I can't comment on your specific case, but here are my details on my box. I'm using the Ireland section of the terrestrial.xml file which I have supplied to the team. This contains the correct tuner settings for all transmitters in the Saorview DVB-T system and does not use the "auto" settings.
I would the diplay info like your, i replaced fec lp in favor of trasmission mode:)
You use

<terrestrial name="Republic of Ireland, all regions(ie) (Europe DVB-T/T2)" flags="5">
section from this (https://github.com/oe-alliance/oe-alliance-tuxbox-common/blob/1d7b78655d98903bcacea4249f35286b9add02d6/src/terrestrial.xml) file?

[Joe_90]

<terrestrial name="Republic of Ireland, all regions(ie) (Europe DVB-T/T2)" flags="5">
section from this (https://github.com/oe-alliance/oe-alliance-tuxbox-common/blob/1d7b78655d98903bcacea4249f35286b9add02d6/src/terrestrial.xml) file?

Correct - that's the section I use (I created it for the team). It's got the exact parameters for the terrestrial network in my country, but no use to you.

I really can't help with the configuration for Italy, but as you are in broadcasting as you say, then you should be able to find out the correct parameters for the transmitters which you can receive at your location. There is no point really in putting in all parameter settings as I think the tuning will fail if you put in wrong ones. You need to do a bit of local research to find the transmitter parameters that are correct for your local region.

[dax]

Correct - that's the section I use (I created it for the team). It's got the exact parameters for the terrestrial network in my country, but no use to you.
Yes, i known!

I really can't help with the configuration for Italy, but as you are in broadcasting as you say, then you should be able to find out the correct parameters for the transmitters which you can receive at your location. There is no point really in putting in all parameter settings as I think the tuning will fail if you put in wrong ones. You need to do a bit of local research to find the transmitter parameters that are correct for your local region.
I've done a terrestrial with accurate parameters of my region aided by my field strenght meter and it works well.

@Huevos

Looks like some sort of strange software blind scan. :confused:
This is a good idea, in my opinion better than a terrestrial with different states. A terrestrial that include all frequencies and parameter combinations. Sure take more time for a scan process but it is like a blindscan. I don't known why, but with the terrestrial file that i had posted in 2 post doesn' t work.
Could you help me to display the channel number instead of frequency?
The other things i ask to you is:
-as the attached images with the infobar the parameters show for the tuner are not the same of the bottom of channel list, could you fixed?
infobar--> system, frequency(wrong), bandwidth, const, fec_lp, fec_hp
channel list--> system, frequency(right), trasmission mode, const, fec_hp, guard interval
In my opinion the more interesting parameters are: system, channel, bandwidth, trasmission mode, const, fec_hp, guard interval:thumbsup:
-if i navigate through menu>info>channel the frequeny show is wrong (like the infobar) for example 569 instead of 560 and channel is missing
I known, i'm a cosmetics fan:D
If i try to do a manual scan or use satfinder enigma crash (only after a scan, not with a freshly image), see crashlog. Apollo 062
Thanks a lot

[Joe_90]

As regards the frequency display, I assume it is due to the way the tuners work in different boxes. In your case you have a display of 570Mhz in one place and 569MHz in another. In my case I have a display of 754MHz in one place and 753MHz in another. When I look in the log I see the tuner displaying 753999997. I presume when it's converted to integer display the frequency is rounded down. The tuners are not very precise in any case and will tend to auto-tune over a range of several hundred kilohertz in any case.
Peterj and Huevos are probably best placed to determine if the info you are looking for could be displayed in the order you wish. I find the current info useful as it helps me to distinguish between the same channel which are carried on satellite and terrestrial.

[dax]

As regards the frequency display, I assume it is due to the way the tuners work in different boxes. In your case you have a display of 570Mhz in one place and 569MHz in another. In my case I have a display of 754MHz in one place and 753MHz in another. When I look in the log I see the tuner displaying 753999997. I presume when it's converted to integer display the frequency is rounded down. The tuners are not very precise in any case and will tend to auto-tune over a range of several hundred kilohertz in any case.
We (all) have the same problem related to wrong frequency. I agree with you, tuner couldn't be precise but i think is possible to do the trick like jpuigs do here (https://github.com/OpenViX/enigma2/commit/d9ae1010b3ea83dcb1bd9f759c2777a6e2e1446b) for show the right frequency at the bottom of channel list.
Shame on me if i'm wrong, I'm not skilled about coding.

Peterj and Huevos are probably best placed to determine if the info you are looking for could be displayed in the order you wish. I find the current info useful as it helps me to distinguish between the same channel which are carried on satellite and terrestrial.
I hope that they can help. And yes, also for me the current info is very useful i' m here to advise what doesn't work properly:)
I repeat, it's only my personal opinion

[dax]

No input from Huevos and/or Peterj?:D