Improved version of blind scan for ET9x00...
rhinoceros 14 feb 2012
This is an update to the blindscan plugin for ET9x00 only!
First, a thanks is in order to the PLi team for using open source. Remember that work like this is possible only because we have access to that. With closed-source, developments like these would be very difficult to do if not impossible.
Second, the original version is by ET (www.et-view.com). Thanks to ET for this blind scan plugin. Here is an update since the plugin is not very robust, especially in a motorised installation.
Third, this is software, therefore there are bugs. Please have patience and tell me about them.
Installation:
If you want to restore your present system, make a backup of this file since it will be overwritten:
/usr/lib/enigma2/python/Screens/ ScanSetup.pyo
Install the attached package and restart e****2. Done.
This package is only for testing purposes only.
Changes:[list]
[*]The blind scan frequently does not run to completion and suffers from other robustness issues, such as tuner hang after scan completion. The robustness is significantly improved.
[*]Both bands and polarisations can now be selected individually or together for the same run. No need to run the blind scan several times each for one band or polarisation.
[*]Frequency and symbol rate values are rounded to multiples of 1000.
[/list]
Comments:
The blind scan is Ku band only.
The binary executable is by ET and seems to work fine. It is fairly fast but occasionally misses transponders. Perhaps better results can be achieved by limiting the symbol rate range in the scan. Select one rate or a small range only. I have not tested this myself, though.
There is a focusing stage in the beginning. This is necessary to achieve better robustness and in order not to loose transponders in the start of the scan. Please be patient.
Once a blind scan has started you cannot interrupt it. You will need to wait until completion, which might take up to 5 minutes or so if both bands and polarisations are selected. As soon as the transponder scan is complete and the service scan starts you can press the ‘back’ or ‘esc’ button if you don’t want to continue. Nothing will be saved in that way.
Rounding of frequency and symbol rates means that some 5 significant digits are available for each. More digits are technically insignificant and do not occur in technical publications.
First, a thanks is in order to the PLi team for using open source. Remember that work like this is possible only because we have access to that. With closed-source, developments like these would be very difficult to do if not impossible.
Second, the original version is by ET (www.et-view.com). Thanks to ET for this blind scan plugin. Here is an update since the plugin is not very robust, especially in a motorised installation.
Third, this is software, therefore there are bugs. Please have patience and tell me about them.
Installation:
If you want to restore your present system, make a backup of this file since it will be overwritten:
/usr/lib/enigma2/python/Screens/ ScanSetup.pyo
Install the attached package and restart e****2. Done.
This package is only for testing purposes only.
Changes:[list]
[*]The blind scan frequently does not run to completion and suffers from other robustness issues, such as tuner hang after scan completion. The robustness is significantly improved.
[*]Both bands and polarisations can now be selected individually or together for the same run. No need to run the blind scan several times each for one band or polarisation.
[*]Frequency and symbol rate values are rounded to multiples of 1000.
[/list]
Comments:
The blind scan is Ku band only.
The binary executable is by ET and seems to work fine. It is fairly fast but occasionally misses transponders. Perhaps better results can be achieved by limiting the symbol rate range in the scan. Select one rate or a small range only. I have not tested this myself, though.
There is a focusing stage in the beginning. This is necessary to achieve better robustness and in order not to loose transponders in the start of the scan. Please be patient.
Once a blind scan has started you cannot interrupt it. You will need to wait until completion, which might take up to 5 minutes or so if both bands and polarisations are selected. As soon as the transponder scan is complete and the service scan starts you can press the ‘back’ or ‘esc’ button if you don’t want to continue. Nothing will be saved in that way.
Rounding of frequency and symbol rates means that some 5 significant digits are available for each. More digits are technically insignificant and do not occur in technical publications.
Bijgevoegde Bestanden
littlesat 15 feb 2012
I just put it on our download server... After the next builds it will be available.
littlesat 15 feb 2012
It might be more convenient when you put such source code to github or so....
ajeeb 15 feb 2012
The blindscan never worked for even this update
in tuner2 I tried several times
ET9x00
in tuner2 I tried several times
ET9x00
rhinoceros 15 feb 2012
I am not sure I understand your statement. What is tuner2, is it the second tuner called tuner B in the skin?. If that is the case, does the blind scan work on tuner A ? We know tuner B has issues in all present day ET9X00 boxes. Can you expand a little further on your situation, please, what does not work, how do you use it, etc. Thanks for your feedback.The blindscan never worked for even this update
in tuner2 I tried several times
rhinoceros 15 feb 2012
Oeps, this would largely exceed my small skill set ...It might be more convenient when you put such source code to github or so....
ajeeb 15 feb 2012
Yes you right tunerB not works !!
in tunerA works tested with low,vertical !!
I will try to swap them to test
BR
in tunerA works tested with low,vertical !!
I will try to swap them to test
BR
ajeeb 15 feb 2012
I did swap no problem to scan Nilesat7w
But always show me nothing to scan with amos4w and lnb is ok but recently some freq. changed so I want to search but did not work with this sat !!!
I test using default settings universal LNB
Vertical,low,30000-35000 this my range and those channels are HD !!!
But always show me nothing to scan with amos4w and lnb is ok but recently some freq. changed so I want to search but did not work with this sat !!!
I test using default settings universal LNB
Vertical,low,30000-35000 this my range and those channels are HD !!!
Gennar1 15 feb 2012
I test using default settings universal LNB
Vertical,low,30000-35000 this my range and those channels are HD !!!
Tuner B will not work with symbol rates >= 30000. This is a known hardware issue of ET9x00 decoders (fixed only in a very recent revision).
zeeteefje 15 feb 2012
Tuner B will not work with the original xtrend code.
From ET-Support on 5-18-2011:
--------
The python code is made at the moment only for Tuner A.
So you have to wait when a programmer makes it work for both tuners.
So far we see it's not a driver issue.
---------
Source: http://www.et-suppor...needs-more-work
From ET-Support on 5-18-2011:
--------
The python code is made at the moment only for Tuner A.
So you have to wait when a programmer makes it work for both tuners.
So far we see it's not a driver issue.
---------
Source: http://www.et-suppor...needs-more-work
ajeeb 15 feb 2012
Yes I read about this so am testing with tuner A !!
Can't get any result .
Can't get any result .
ajeeb 15 feb 2012
Well, now it's works need shutdown box !!! Sometimes tuners become crazy and I find new freq. thanks to your MOD
Huevos 15 feb 2012
Hi rhinoceros,
I recently edited the blindscan.py file of the VIX image. Now the user doesn't need to know anything about bands and IF frequencies. Just enter the frequencies in kingofsat/lyngsat format (5 figure MHz frequencies) and the code works out the rest (i.e. what bands to scan, etc). No need for multiple runs anymore. Still testing at the moment but it seems to work fine in Vu+ Ultimo, Vu+ Uno, ET9x00.
Works in C-band and Ku.
Frequencies and symbol rates are entered in MHz (symbol rates between 1-45MHz). 2 figure user input for symbol rates and 5 figure for frequencies.
Also there are various filters. Before the service scan is done found transponders are compared with known transponders (satellite.xml). If the found transponders are known transponders the values of the known transponders will be used for the service scan, not the values from the blind scan. This avoids duplicate channels. Another option is omit known transponders from the service scan. This is great for feed hunting as it only finds new transponders. Also there is an option to ignore transponders on neighbouring satellites (up to 3º in 1º steps). This means if the blindscan locks onto a powerful transponder on an adjacent satellite that will not be included in the service scan.
You can see it in action on youtube:
_http://www.youtube.com/watch?v=Jl7JRACnVvs
If you are interested in having a look at the source I could post it.
P.S. I'd be interested in seeing your positioner.py code if you would be kind enough to post a link to it.
I recently edited the blindscan.py file of the VIX image. Now the user doesn't need to know anything about bands and IF frequencies. Just enter the frequencies in kingofsat/lyngsat format (5 figure MHz frequencies) and the code works out the rest (i.e. what bands to scan, etc). No need for multiple runs anymore. Still testing at the moment but it seems to work fine in Vu+ Ultimo, Vu+ Uno, ET9x00.
Works in C-band and Ku.
Frequencies and symbol rates are entered in MHz (symbol rates between 1-45MHz). 2 figure user input for symbol rates and 5 figure for frequencies.
Also there are various filters. Before the service scan is done found transponders are compared with known transponders (satellite.xml). If the found transponders are known transponders the values of the known transponders will be used for the service scan, not the values from the blind scan. This avoids duplicate channels. Another option is omit known transponders from the service scan. This is great for feed hunting as it only finds new transponders. Also there is an option to ignore transponders on neighbouring satellites (up to 3º in 1º steps). This means if the blindscan locks onto a powerful transponder on an adjacent satellite that will not be included in the service scan.
You can see it in action on youtube:
_http://www.youtube.com/watch?v=Jl7JRACnVvs
If you are interested in having a look at the source I could post it.
P.S. I'd be interested in seeing your positioner.py code if you would be kind enough to post a link to it.
Bijgevoegde Bestanden
littlesat 15 feb 2012
@Huevos,
Then please post your sources here. You say it is working on VU and ET this single code?
Then please post your sources here. You say it is working on VU and ET this single code?
Frogman 16 feb 2012
Today i get an error updating my blindscan:
... Upgrading enigma2-plugin-systemplugins-blindscan on root from 2011-04-15 to 2012-02-14... Downloading http://downloads.pli-images.org/feeds/openpli-2.1/et9x00/3rd-party/enigma2-plugin-system plugins-blindscan_2012-02-14_mipsel.ipk. .. Collected errors: * satisfy_dependencies_for: Cannot satisfy the following dependencies for enigma2-plugin-systemplugins-blindscan: * unknown *
Pedro_Newbie 16 feb 2012
That's exactly what is noted behind Depends in the control file: unknown
Maybe this one is better:
Maybe this one is better:
Bijgevoegde Bestanden
malakudi 16 feb 2012
Frequencies and symbol rates are entered in MHz (symbol rates between 1-45MHz). 2 figure user input for symbol rates and 5 figure for frequencies.
Actually, Symbol Rate is in baud (Bd), or symbols/sec, or in your context, Megabaud (MBaud or MBd) or Megasymbols/sec
Is your code GPL? Seems very interesting and usefull blindscan additions. Another good addition would be to update satellites.xml with new transponders found, marked with a flag as feed transponders or not.
Frogman 16 feb 2012
No, sorry - doesn't work.That's exactly what is noted behind Depends in the control file: unknown
Maybe this one is better: