270 replies to this topic

[Robinson]

Would I sound dumb if I said I do not have such option in the "Satellite" line?

When I flick through available options I only get dozens of satellites (from satellites.xml, I suspect) and the 4 "All satellites (USALS)" options. Nothing of the sort of "Selecting satellites (USALS)" unless this option is hiding somewhere between satellite positions.

Does anyone know what is wrong in my case?

I can run an online update if necessary but from what I understand this option has been in the image for quite a while, so a 3-month's old image should definitely include it.

 

Attached Files

•  2.jpg   22.01KB   21 downloads

[Huevos]

I can run an online update if necessary but from what I understand this option has been in the image for quite a while, so a 3-month's old image should definitely include it.

You need to do an update.

Edited by Huevos, 11 August 2014 - 17:42.

[theparasol]

Does anyone happen to know what voltage is used to let the motor position the dish?

My motor can use 13V and 18V as input and turnspeed is fastest with 18V (as stated in user manual)

AFAIK on horizontal polarized channels the motor is driven by 18V, but on vertical polarized channels the motor is driven by 13V.

 

Can the motor be driven on 18V all the time and if dish is settled on right position swap the voltage to the correct one?

[littlesat]

Not when THE tune in means sat found

[Huevos]

Can the motor be driven on 18V all the time and if dish is settled on right position swap the voltage to the correct one?

Yes always select a horizontally polarized channel first when changing satellite.

 

But, TBH, the amount of time saved is minuscule. Say changing from 19E to 23E you're only talking less than 1 second difference. If you really want to save time and zap quickly you should look at setting up a fixed LNB at all your main positions. That way you don't have to wait for a motor at all.

[Rob van der Does]

LNB is one physical LNB. So if you have a motorized dish with one LNB just set up every satellite as LNB 1.

Not necessarily; you can also use it as a 'virtual' LNB.
I have one dish with a pole that is slightly off-perpendicular. Now I use 'LNB1' for my Easterly satellites and 'LNB2' for the Westerly. It is the same physical LNB and the same coax; both settings are the same with only a slightly different position (one is half a degree more to the east).

[Huevos]

LNB is one physical LNB. So if you have a motorized dish with one LNB just set up every satellite as LNB 1.

Not necessarily; you can also use it as a 'virtual' LNB.
I have one dish with a pole that is slightly off-perpendicular. Now I use 'LNB1' for my Easterly satellites and 'LNB2' for the Westerly. It is the same physical LNB and the same coax; both settings are the same with only a slightly different position (one is half a degree more to the east).

The problem with E2 is there is no motor object. If there were you wouldn't need to do that. What you would do is one LNB number maps to one physical LNB. And then set up motor 1, motor 2, etc. and assign the desired motor to each individual satellite. That way LNB routing and motor config would become independent. Not having a motor object also causes other problems like stored positions are held in the LNB object when they should be held in the motor object. Rhinoceros, said he was going to sort this out at some point, but no news so far.

Edited by Huevos, 12 August 2014 - 12:00.

[Robinson]

Is it possisble to find out (in ET9000 menu or using FTP client) if software east/west limits are set or not?

[Huevos]

Is it possisble to find out (in ET9000 menu or using FTP client) if software east/west limits are set or not?

No, not possible. Software limits are saved in the motor (or V-box) not the STB. This is so the software limits persist even if the STB is changed.

[Robinson]

Thanks, I did not know that. It is smart not to store them in STB but it's a pity there is no command that could read that back from the rotor.

[Huevos]

Why would you want to read the limits, and in what form? Hardware/software limits are to protect the motor, not the STB, which is why they are stored on the motor.

[Robinson]

The situation at the moment is that I cannot loop through all the satellites in my satellites.xml file and I'm wondering why.

Could it be that the limits are set? But I guess I should be able to loop through them - the motor would just not move.

That is why I wanted to check my softare limits.

Over the last few months, I fiddled with some individual offsets for some satellites. Perhaps I screwed something up in there:

config.Nims.1.diseqcMode=toneburst_a_b
config.Nims.1.configMode=satposdepends
config.Nims.1.powerMeasurement=false
config.Nims.0.turningspeedH=2.7
config.Nims.0.powerMeasurement=false
config.Nims.0.tuningstepsize=0.112
config.Nims.0.configMode=advanced
config.Nims.0.longitude=20.783
config.Nims.0.diseqcMode=positioner
config.Nims.0.latitude=49.683
config.Nims.0.advanced.sats=3605
config.Nims.0.advanced.lnb.1.turningspeedH=2.7
config.Nims.0.advanced.lnb.1.diseqcMode=1_2
config.Nims.0.advanced.lnb.1.powerMeasurement=false
config.Nims.0.advanced.lnb.1.latitude=49.683
config.Nims.0.advanced.lnb.1.tuningstepsize=0.112
config.Nims.0.advanced.lnb.1.longitude=20.783
config.Nims.0.advanced.lnb.1.turningspeedV=2.4
config.Nims.0.advanced.lnb.69.turningspeedH=2.7
config.Nims.0.advanced.lnb.69.powerMeasurement=false
config.Nims.0.advanced.lnb.69.latitude=49.683
config.Nims.0.advanced.lnb.69.tuningstepsize=0.112
config.Nims.0.advanced.lnb.69.longitude=20.783
config.Nims.0.advanced.lnb.69.turningspeedV=2.4
config.Nims.0.advanced.sat.3324.usals=false
config.Nims.0.advanced.sat.3324.lnb=1
config.Nims.0.advanced.sat.3325.lnb=1
config.Nims.0.advanced.sat.3325.usals=false
config.Nims.0.advanced.sat.3300.rotorposition=2
config.Nims.0.advanced.sat.3300.usals=false
config.Nims.0.advanced.sat.3300.lnb=1
config.Nims.0.advanced.sat.3605.userSatellitesList=[31, 32, 48, 70, 72, 90, 92, 100, 101, 130, 160, 162, 170, 171, 192, 194, 201, 216, 235, 255, 260, 282, 305, 306, 315, 330, 360, 380, 381, 390, 420, 450, 460, 461, 475, 491, 502, 503, 505, 506, 525, 530, 550, 559, 570, 571, 600, 601, 620, 621, 642, 643, 660, 661, 685, 686, 705, 722, 740, 741, 750, 751, 765, 766, 785, 786, 3254, 3255, 3284, 3285, 3354, 3355, 3379, 3380, 3399, 3400, 3419, 3420, 3450, 3459, 3475, 3489, 3490, 3520, 3530, 3549, 3550, 3560, 3591, 3592]
config.Nims.0.advanced.sat.3605.lnb=69
config.Nims.0.turningspeedV=2.4

In what form? Preferably something like this?

E limit - 75 deg

W limit - 30 deg

or:

E limit - 90 E

W limit - not set

 

An alternative could also be the following information in the PositionerSetup menu:

Latest limits set by this STB:

[Rob van der Does]

Than simply delete the limits ('limits off' in positioner setup). Than you're sure no limits are set.

[Robinson]

Yes, sure.

But for me it would be nice to know if the limits have been set or not so if there is someone here who could add one of the alternatives suggested in my previous message it would be very good.

[janejak]

are isn it simple better?

this is my settings:

config.Nims.1.configMode=satposdepends
config.Nims.0.turningspeedH=2.5
config.Nims.0.rotorPositions=60
config.Nims.0.powerMeasurement=false
config.Nims.0.diseqcA=3592
config.Nims.0.diseqcB=48
config.Nims.0.longitude=18.758
config.Nims.0.diseqcMode=positioner
config.Nims.0.latitude=69.381
config.Nims.0.turningspeedV=1.9

[Huevos]

To me it sounds like satellites.xml is knackered, or doesn't correspond with your tuner config.

Anyway nothing to do with software limits because the STB doesn't know anything aboutthese.

[Robinson]

To me it sounds like satellites.xml is knackered, or doesn't correspond with your tuner config.

 

Probably not. I replaced both my satellites.xml files with a one of yours (?) (satellites.org) and I can still see only those satellites between 78.5E and 34.5W although I selected a wider range.

When in signal measurement screen i can circulate between them like that:

3E -> ..... -> 78.5E -> 34.5W -> 31W -> 24.5W -> ..... -> 0.8W -> 30W -> 27.5W -> 3E (and the loop is closed)

Please note the strange sequence in which 30W and 27.5W appear. These are the 2 satellites I selected a rotor offset using advanced tuner settings.

Still no trace of 45W and 90E although they are present in satellites.xml.

I am now quite convinced that something was messed up when I fiddled with my rotor offsets for 30W and 27.5W.

I think the culprit is here in this part of my etc/enigma2/settings file (I quoted a longer part of this file above):

config.Nims.0.advanced.sat.3605.userSatellitesList=[31, 32, 48, 70, 72, 90, 92, 100, 101, 130, 160, 162, 170, 171, 192, 194, 201, 216, 235, 255, 260, 282, 305, 306, 315, 330, 360, 380, 381, 390, 420, 450, 460, 461, 475, 491, 502, 503, 505, 506, 525, 530, 550, 559, 570, 571, 600, 601, 620, 621, 642, 643, 660, 661, 685, 686, 705, 722, 740, 741, 750, 751, 765, 766, 785, 786, 3254, 3255, 3284, 3285, 3354, 3355, 3379, 3380, 3399, 3400, 3419, 3420, 3450, 3459, 3475, 3489, 3490, 3520, 3530, 3549, 3550, 3560, 3591, 3592]
config.Nims.0.advanced.sat.3605.lnb=69: 

The line "config.Nims.0.advanced.sat.3605.userSatellitesList=" is missing some satellites.

Don't know why.

 

[Robinson]

If you have a rotor, is there a limit to how many individual rotor positions can be set as "offsets" from the regular USALS function?

Maybe I'm doing something wrong but I only managed to do 2 in order to improve the signal on the few satellites that have an issue with USALS.

This is the part of my current settings file responsible for tuner configuration:

config.Nims.1.diseqcMode=toneburst_a_b
config.Nims.1.configMode=satposdepends
config.Nims.1.powerMeasurement=false
config.Nims.0.turningspeedH=2.7
config.Nims.0.powerMeasurement=false
config.Nims.0.tuningstepsize=0.112
config.Nims.0.configMode=advanced
config.Nims.0.longitude=20.383
config.Nims.0.diseqcMode=positioner
config.Nims.0.latitude=49.683
config.Nims.0.advanced.sats=3605
config.Nims.0.advanced.lnb.1.turningspeedH=2.7
config.Nims.0.advanced.lnb.1.diseqcMode=1_2
config.Nims.0.advanced.lnb.1.powerMeasurement=false
config.Nims.0.advanced.lnb.1.latitude=49.683
config.Nims.0.advanced.lnb.1.tuningstepsize=0.112
config.Nims.0.advanced.lnb.1.longitude=20.783
config.Nims.0.advanced.lnb.1.turningspeedV=2.4
config.Nims.0.advanced.lnb.69.turningspeedH=2.7
config.Nims.0.advanced.lnb.69.powerMeasurement=false
config.Nims.0.advanced.lnb.69.latitude=49.683
config.Nims.0.advanced.lnb.69.tuningstepsize=0.112
config.Nims.0.advanced.lnb.69.longitude=20.383
config.Nims.0.advanced.lnb.69.turningspeedV=2.4
config.Nims.0.advanced.sat.3325.lnb=1
config.Nims.0.advanced.sat.3325.usals=false
config.Nims.0.advanced.sat.3300.rotorposition=2
config.Nims.0.advanced.sat.3300.usals=false
config.Nims.0.advanced.sat.3300.lnb=1
config.Nims.0.advanced.sat.3605.userSatellitesList=[30, 48, 70, 90, 100, 130, 160, 170, 192, 216, 235, 255, 260, 282, 305, 315, 330, 360, 380, 390, 420, 450, 460, 475, 505, 525, 530, 550, 560, 570, 600, 620, 642, 660, 685, 705, 740, 750, 765, 785, 830, 851, 865, 875, 880, 3255, 3285, 3325, 3355, 3380, 3400, 3420, 3450, 3475, 3490, 3520, 3530, 3550, 3560, 3592]
config.Nims.0.advanced.sat.3605.lnb=69
config.Nims.0.turningspeedV=2.4

I managed to successfully offset 27.5W and hopefully 30W.

I think this is the part of settings file which is responsible for that although I'm not sure why there is only one entry of "config.Nims.0.advanced.sat.3300.rotorposition=":

config.Nims.0.advanced.sat.3325.lnb=1
config.Nims.0.advanced.sat.3325.usals=false
config.Nims.0.advanced.sat.3300.rotorposition=2
config.Nims.0.advanced.sat.3300.usals=false
config.Nims.0.advanced.sat.3300.lnb=1

Also, out of curiosity, can anyone please explain the difference between 1 and 69 in the 2 lines below?

config.Nims.0.advanced.lnb.1.turningspeedV=2.4
config.Nims.0.advanced.lnb.69.turningspeedH=2.7

[Huevos]

1-64 are standard LNBs. 69 is part of all-sats.

 

64 = 16 uncommitted x 4 committed.

 

And as there is no motor object you will need to set up a new LNB for each set fake of USALS co-ordinates

Edited by Huevos, 27 April 2015 - 19:13.

[rhinoceros]

Indeed I had it on my list of to-do's to look into a more flexible setup for motors. Can someone collect examples of what would be needed. More LNB's on 1 rotor ? More rotors ? If possible with a schematic of the cabling, since it is important to know how the flow of commands has to be. E.g., if a rotor diseqc command has to go on a different cable than the LNB selected then we need to store more topology details. In other words it would become more complex.

 

What would be the most important flexibility to have?