42 replies to this topic

[Persian Prince]

is it a clone of http://satellites-xml.eu ? (maybe nulled version)

Not at all. The only thing it has in common with the other site is the presentation uses 4 tabs, but tabs is just a common web feature where big forms are concerned. The code is written 100% by me, and not copied from anywhere as anyone viewing the source html, css, and javascript will see. The quick select has a lot more control than the other site, C-band and Ku-band are selectable individually and a user can just enter their co-ordinates and download a horizon to horizon satellites.xml for their location.

it's awesome

can you provide a direct link of satelllites.xml with all data so we can add it to our plugins ? i mean without any custom settings and with all data

[jeanclaude]

is it not possible to put this satellites.xml in the download list, like a settings list viz Henksat. But ONLY the satellites.xml module, NOT the services/bouquets. This way we can get an up-to-date satellite.xml without loosing our personal channel lists.

[Henksat]

In our OpenPli images we have an up to date satellites.xml. Our grabber continously update the file.
The settings in our donwloads, e.g. the Henksatsettings, contains no satellites.xml, so the xml in the image will be used and can not be overwritten.

[Huevos]

In our OpenPli images we have an up to date satellites.xml. Our grabber continously update the file.

You're missing the point. This will produce a satellites.xml that only contains active transponders. This does away with all the time wasted scanning inactive frequencies. On some satellites that can speed up a scan by a factor of 10:1.

[Erik Slagter]

Yes, it was discussed before. The satellites.xml in our feed really has to be changed to it does not contain feeds. Scanning feeds (that often are not active) takes ages because the tuner can't get a lock. I think it shouldn't be too hard to adapt the script for that, but somebody has to do it

[MiLo]

If you want to use a "personal" satellites.xml, just place it in /etc/enigma2/ instead. The "central" one will be ignored in that case, so updates won't touch your file. And it'll go into your settings backup as well.

[Rob van der Does]

If you want to use a "personal" satellites.xml, just place it in /etc/enigma2/ instead. The "central" one will be ignored in that case, so updates won't touch your file. And it'll go into your settings backup as well.

Correct, but this is about a way to enhance the system-file, not the user-file.

[MartiniB]

it's awesome

+1 +1 +1

small suggestions and comments
1. didnt able download with IE, with FF no problem
2. some option to able convert Circular polarities to L->H and R->V
(who have Torroidal dish maibe can be interested on oposite conversion L->V and R->H)
3. some option to able skip African transponders on 36E http://www.lyngsat.c...6A-36B.html
4. "custom+ section" - load positions from selected xml on hdd
5. skip transponders which are present in some user own made blacklist.xml (register with not receiveable in his area)

[Huevos]

it's awesome

+1 +1 +1

small suggestions and comments
1. didnt able download with IE, with FF no problem
2. some option to able convert Circular polarities to L->H and R->V
(who have Torroidal dish maibe can be interested on oposite conversion L->V and R->H)
3. some option to able skip African transponders on 36E http://www.lyngsat.c...6A-36B.html
4. "custom+ section" - load positions from selected xml on hdd
5. skip transponders which are present in some user own made blacklist.xml (register with not receiveable in his area)

1, Do people still use IE? Anyway I checked IE9 and IE8 and both work fine. IE9 asks "open or save?" but it does work.
2, What for? (On a torroidal dish linear polarisation is not affected, only circular needs reversing).
3, That really is a minefield that would require a human being in the loop. This is 100% automated.
4, I'm not sure what you mean.
5, That would be a lot easier to do on the receiver. There is an option on the blindscan plugin of the VIX image that does a similar thing. It skips any transponders in satellites.xml (uses satellites.xml as the blacklist) so you only find channels on unknown transponders, which is great for feed hunting.

Edited by Huevos, 8 June 2012 - 21:17.

[MartiniB]

@Huevos
1. this isnt first time when i have to notice im not normal
_ i have installed IE, FF and GC, but somewhy IE always prefered
_ but most important problem currently is gone

2. i prefere keep in serviceslist only H and V then that list can be easyer exported to older dreams which dont know about L and R
_ on regular dish L has been stored as H and R as V
_ on Torroidal L as V and R as H, (yes i know the best place make inversion is enigma2, but does DMM listenig to theyr customers)
_ after each autoscan i always make patching of lamedb, by execute script /usr/script/lamedb_set_inversion.sh

#!/bin/sh
# MartiniB
#
fLAMEDB="/etc/enigma2/lamedb"
sedLIST="$fLAMEDB".sed
#sedLIST="/tmp/lamedb.sed"
[ -e "$fLAMEDB".tmp ] && rm -f "$fLAMEDB".tmp
[ -e "$sedLIST" ] && sed -f "$sedLIST" "$fLAMEDB">"$fLAMEDB".tmp|| echo sedList "$sedLIST" not found
if [ -s "$fLAMEDB".tmp ]; then
mv "$fLAMEDB".tmp "$fLAMEDB"
wget -O /dev/null -q [url="http://127.0.0.1/web/servicelistreload?mode=1"]http://127.0.0.1/web/servicelistreload?mode=1[/url]
else
echo ErRoR - Zero len "$fLAMEDB".tmp
fi

/etc/enigma2/lamedb.sed

s#:48:2:0#:48:0:0#
s#11554000:27500000:0:3:70:2:0#11554000:27500000:0:3:70:1:0#
s#:70:2:0#:70:0:0#
s#11919000:27500000:1:3:90:2:0#11919000:27500000:1:3:90:1:0#
s#:90:2:0#:90:0:0#
s#:100:2:0#:100:0:0#
s#11727000:27500000:1:3:130:2:0#11727000:27500000:1:3:130:1:0#
s#:130:2:0#:130:0:0#
s#12714000:5632000:1:3:158:2:0#12714000:5632000:1:3:158:1:0#
s#:158:2:0#:158:0:0#
s#:160:2:0#:160:0:0#
s#:192:2:0#:192:0:0#
s#:235:2:0#:235:0:0#
s#:282:2:0#:282:0:0#
s#:360:2:0#:360:0:0#
s#:390:2:0#:390:0:0#
s#000:2:0:360:#000:0:0:360:#
s#000:2:1:360:#000:0:1:360:#
s#000:2:2:360:#000:0:2:360:#
s#000:2:3:360:#000:0:3:360:#
s#000:2:4:360:#000:0:4:360:#
s#000:2:5:360:#000:0:5:360:#
s#000:2:6:360:#000:0:6:360:#
s#000:3:0:360:#000:1:0:360:#
s#000:3:1:360:#000:1:1:360:#
s#000:3:2:360:#000:1:2:360:#
s#000:3:3:360:#000:1:3:360:#
s#000:3:4:360:#000:1:4:360:#
s#000:3:5:360:#000:1:5:360:#
s#000:3:6:360:#000:1:6:360:#
s#:400:2:0#:400:0:0#
s#:420:2:0#:420:0:0#
s#10974000:8150000:0:3:530:2:0#10974000:8150000:0:3:530:1:0#
s#:530:2:0#:530:0:0#
s#11512000:2617000:1:3:600:2:0#11512000:2617000:1:3:600:1:0#
s#:600:2:0#:600:0:0#
s#:750:2:0#:750:0:0#
s#:-300:2:0#:-300:0:0#
s#:-245:2:0#:-245:0:0#
s#:-220:2:0#:-220:0:0#
s#:-180:2:0#:-180:0:0#
s#:-150:2:0#:-150:0:0#
s#12661000:2170000:1:3:-125:2:0#12661000:2170000:1:3:-125:1:0#
s#:-125:2:0#:-125:0:0#
s#:-80:2:0#:-80:0:0#
s#:-50:2:0#:-50:0:0#
s#:-40:2:0#:-40:0:0#
s#:-8:2:0#:-8:0:0#
s#:011a0000:07f6:0002:130:0#:011a0000:07f6:0002:1:0#
s#^STREAM-#BBC\ Stream\ #

3. if list comes from www.lyngsat.com then excluding can be done by search keywords(africa; south east; etc) in column `Beam`

4. something like select your previous .xml on hdd and by present `position="???"` in it set checkboxes in custom area

5. im talking about oposite way - skip some transponders which i know as not receiveable
_ like Astra 1N on 28E i cant receive with too small(1.8m) dish
_ meibe another way is extend option "3." with option `Exclude by Sattelite Title`

[Huevos]

@MartiniB,

2, Looks like you're already sorted with that. My problem is I have a T90 and other dishes sharing the the same transponder blocks so editing the satellites.xml to correct on the T90 would break it on my other dishes. But fortunately I don't have any circular polarised LNBs on the T90.

3, 4, & 5, That would just make the whole thing messy and complicated. If you are going to exclude by name that would mean over 300 satellites on the form, and exclude by beam would be far worse. Also my intention was to create a satellites.xml based on what is available at each slot, and not based on the user's equipment. For individual needs I would say just create a blacklist and just run an automated process to edit the satellites.xml so it corresponds with your blacklist.

[Erik Slagter]

Apparently Lyngsat has a mind of it's own at times (think of the recent "movement" of 23.5 to 23.3 for instance). I don't think we can do much about that.

On the other hand, the much requested feature of leaving out feeds (and test cards as well, I decided...) from the satellites.xml has been implemented now, so scanning of a whole satellite is much much faster now!

[Huevos]

Apparently Lyngsat has a mind of it's own at times (think of the recent "movement" of 23.5 to 23.3 for instance). I don't think we can do much about that.

The reason you have that trouble is your code is completely dynamic. But 23.5E is not dynamic, it is a fixed position so you can hard code it as such. If it later becomes listed as 23.3E your code should be able to cope with that. And it's not just 23.5E this has affected. In the last few weeks this happened on 50W, 4.8E and 21.6E, and a little while back on 15.8E. All you need is your major positions hard coded and when you find a satellite within a couple of decimal places of those it skews the position to reflect the hard coded one.

I don't know how your grabber works, but mine downloads the data, filters it, corrects any errors it can, and then puts it in the database. From there on it can be used to create any custom satellites.xml file configuration. The only limitation is imagination. Then as a final quality control test it runs last week's complete satellites.xml and this week's complete satellites.xml through a difference checker and emails me the result so I can check nothing weird has slipped through my filtering.

[Erik Slagter]

We thought about these "fuzzy" satellite positions. The problem is: where to draw the line. 0.2 degrees, 0.5 degrees, more? Sometimes real positions (according to Lyngsat) are very close to each other. We now use a static mapping from e.g. 23.3 to 23.5 so the transponders on 23.5 simply show up as such on your box. I think that's good enough.

[Huevos]

We thought about these "fuzzy" satellite positions. The problem is: where to draw the line. 0.2 degrees, 0.5 degrees, more?

I set my fuzzy logic to orb_pos +/-2, and that is applied to all the major positions. If something was further out I'd just send them an email and it would be corrected.

[Erik Slagter]

How about, for instance, 23.3E and 21.6E then?

[jozy]

satloader.net is a website of ismail demir (ihad) which performs approx the same.
i always use that satellite.xml since the scans are much faster, especially on satellites with different spots such as turksat or astra 2

[Huevos]

How about, for instance, 23.3E and 21.6E then?

23.5E = orb_pos 235. Tolerance is +/-2. So anything between 233 and 237 counts as 235. Same for all positions that are listed in my fixed slots array.

Result is here:
http://satellites-xml.org

[Erik Slagter]

Oh you mean 0.2, I thought 2.0. That will probably work at the moment, until Lyngsat changes it's mind again and moves a position 0.3 degrees from it's official position. The question how much slack you can/must use before you run into other problems.

[Huevos]

The question how much slack you can/must use before you run into other problems.

Erik, I went for 0.2º and it hasn't caused problems so far. 0.3º is the minimum distance (under ITU rules) for competing operators so I thought 0.2º was good.

I think the most important thing, whatever system you use, is to have some sort of quality control mechanism in place whenever you are using external, unsanitised data.