65 replies to this topic

[Rob van der Does]

It's a shame Eutelsat doesn't follow then.

Well, I hope they don't. Those 'strange' polarizations limit the use of a motorised setup.
As it is now I have the Astra's on a fixed dish, so whatever the skew is, I can adjust to it. All other satellites are on my motor, so it is a prerequisite that those transponders behave 'normal'.

[Huevos]

Well, I hope they don't. Those 'strange' polarizations limit the use of a motorised setup.

Not just motorised either. Any setup where the same LNB is used for 2 satellites. So for example a 13E/19E monoblock will be skewed wrong on 19E... and even worse a 19E/23E monoblock will be skewed wrong on both satellites.

[Robinson]

So it would be useful to have a remotely-controlled LNB skew from the comfort of our house, especially for the Astra satellites, but possibly ohne or two other satellites also use that "distorted" skew.

I wonder if such solutions exist.

[Rob van der Does]

So it would be useful to have a remotely-controlled LNB skew from the comfort of our house, especially for the Astra satellites, but possibly ohne or two other satellites also use that "distorted" skew.
I wonder if such solutions exist.

That does exist: look for mobile solutions (so meant for on a motorhome/caravan). The skew is then controlled either automated (seems not useful for those special satellites) or manual via a button.

Edited by SatKiekerd, 27 December 2013 - 17:29.

[Huevos]

Easiest solution is a fixed dish... or a second motorised dish skewed for Astra satellites... but if you are in the intended reception area these satellites are so strong this skew adjustment is irrelevant so just set the motorised dish up with neutral skew.

Edited by Huevos, 27 December 2013 - 17:31.

[Huevos]

That does exist: look for mobile solutions (so meant for on a motorhome/caravan). The skew is then controlled either automated (seems not useful for those special satellites) or manual via a button.

Not cheap though. Oyster 85cm dish with auto-skew comes in at just under 3000€.

[Robinson]

You can make your own satellites.xml and put it in /etc/enigma2 and then that one will be used and it won't get overwritten by updates.

I understand the one in /etc/tuxbox/ will continue to be updated during online updates but it just won't be used as long as there is one in /etc/enigma2/ ?

[Erik Slagter]

Yes exactly.

[Robinson]

I understand the one in /etc/tuxbox/ will continue to be updated during online updates?

 

Can somebody please attach here the latest satellites.xml file from /etc/tuxbox/ folder as used by OpenPli?

Thank you.

[Bag58]

@Robinson

Attached the file from yesterdays build.

Attached Files

•  satellites.zip   27.24KB   13 downloads

[Robinson]

Thank you very much.

[Robinson]

Let me understand one thing because I notice satellite positions are split into different entries (0.1 offset) between Ku and C band.

What is the purpose? I'm sure there is one but I would appreciate if someone could explain.

[WanWizard]

I think positions need to be unique in the file.

 

The position is just a value, it doesn't have any special meaning within the file itself (but it does outside it, for example for EPG or PICON entries that need a link to the service ref).

[Robinson]

Let me give you a couple of examples.

 

There is a fleet of satellites at 19.2E.

The entries in satellites.xml show:

<sat name="19.2E Astra 1KR/1L/1M/1N Ka Band" flags="1" position="194">
<sat name="19.2E Astra 1KR/1L/1M/1N Ku Band" flags="1" position="192">

 

or at 5W:

 

<sat name="5.0W Eutelsat 5 West A C Band" flags="1" position="-51">
<sat name="5.0W Eutelsat 5 West A Ku Band" flags="1" position="-50">

 

Why are they split into 2 different entries in the file?

[Bag58]

For scanning purposes I think it is a good thing that the various bands are split over two or even three satellites this way. So if you select one of the satellites for scanning, either only C-band, Ku-band or Ka-band is scanned. For each of these bands you need a specific type of LNB, which means that scanning a combination of bands would not bring anything, and only be slower.

[Robinson]

scanning a combination of bands would not bring anything, and only be slower.

 

If it is slower, then that makes sense indeed.

Unless someone never scans a complete satellite, then s/he had better combine the bands into one in order not to have to skip through so many satellites when choosing a satellite to scan in service search menu.

[Bag58]

As far as I know you can only link one LNB to a satellite. And since an LNB can only handle one of the bands, you still need different satellites for each band you want to be able to receive.

 

Please ignore this post.

Edited by Bag58, 22 July 2015 - 15:21.

[Bag58]

As far as I know you can only link one LNB to a satellite, and an LNB can only handle one band. So you would still need separate satellites for each of the bands you want to be able to receive.

 

If I'm wrong at this, anyone who knows better, please correct me.

 

Sorry for the double posting, but something went wrong.....

Edited by Bag58, 22 July 2015 - 15:20.

[Rob van der Does]

scanning a combination of bands would not bring anything, and only be slower.

 
If it is slower, then that makes sense indeed.
Unless someone never scans a complete satellite, then s/he had better combine the bands into one in order not to have to skip through so many satellites when choosing a satellite to scan in service search menu.

Or use a dedicated xml like you can get on http://satellites-xml.org/ ; no need to include bands one doesn't have at all.

[Robinson]

Or use a dedicated xml like you can get on http://satellites-xml.org/ ; no need to include bands one doesn't have at all.

 

Exactly. I assume 99% of normal users never use Ka or S band and only a handful of Europeans use C band.