Huevos

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.

Nothing wrong with keeping a catalogue of your finds but I don't think satellites.xml is the correct place to do it. The thing is a feed might be up for 5 minutes and never seen again. If you keep scanning a satellite that is busy for feeds you might end up with satellites in your satellites.xml with hundreds of transponders listed when there are just a handful of permanent ones on the satellite. When it comes to doing a service scan that scan will take much longer than necessary as the receiver trawls through the oversize list of non-existant transponders. There are other issues to like the receiver would need to be restarted after every scan for the changes to be meaningful... and you could no longer uses satellites.xml as a source of transponders to ignore.

@Huevos

ver1 suited to et9h00?

I haven't used it personally on an ET9x00, but it has been tested by the Vix team on those receivers and is reported to work fine.

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.

I'm not sure about the license. You'd need to check with Andyblac. He wrote the code for the Vix image. I just modified it a bit and submitted it back to the Vix team for them to use as they please.

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.