270 replies to this topic

[mirakels]

could be. we will probably know tomorrow...

Edited by mirakels, 26 February 2012 - 21:00.

[zackmuc]

Still no solution .. does anybody know to to solve it?

[dAF2000]

Still no solution .. does anybody know to to solve it?

[modbreak=Modbreak]
Please do not ask the same question in three different threads. This thread is about motorized installations, not about the manual scan problem.
[/modbreak]

[rhinoceros]

Hello rhinoceros,
Built-in recalculate works fine, but is installed near the dish below the roof an is hard to reach. I always neet two persons to re-synchronise, both with handys, one to control the vbox, the other to check signal-strength.
Regards, goedi

@goedi
If I post here a test version with (re-)calculate, would you be willing to test it and post your results here?

[halflife]

after fresh install positioner setup works, but after I memorised few positions, GS when press ok on plugin. I was try to deinstall and install plugin again, but nothing helps.
et9000, latest pli

Attached Files

•  enigma2_crash_1330452929.log   16.87KB   8 downloads

[Dimitrij]

et9000
tuner A - 1.2(rotor)
tuner B - 1.1('advanced')

Сurrent transponder:36*E,12380V,tuner B
Positioner Setup ->SNR 0%,Frequency 0 and etc is also 0 ->Tune and Focus ->Tune(red button) ->exit

crash:

action ->  OkCancelActions ok
okbuttonClick
opening frontend 0
tuning to transponder with data (0, 0, 0, 0, 2, 0, 0, 1, 0, 2)
(0)tune
found no useable satellite configuration for DVB-S freq 0H QPSK on orbital position (0)
warning, skin is missing element polarisation in <class 'Plugins.SystemPlugins.PositionerSetup.plugin.PositionerSetup'>
warning, skin is missing element status_bar in <class 'Plugins.SystemPlugins.PositionerSetup.plugin.PositionerSetup'>
action ->  ColorActions red
[SKIN] Parsing embedded skin <embedded-in-'TunerScreen'>
[Skin] SKIN ERROR in screen '<embedded-in-'TunerScreen'>' widget 'widget': {infinity-hd-full-info/skin.xml}: component with name 'introduction' was not found in skin of screen '<embedded-in-'TunerScreen'>'!. Please contact the skin's author!
action ->  SetupActions cancel
Traceback (most recent call last):
  File "/usr/lib/enigma2/python/mytest.py", line 194, in processDelay
	callback(*retval)
  File "/usr/lib/enigma2/python/Plugins/SystemPlugins/PositionerSetup/plugin.py", line 527, in tune
	rotorposition = int(self.advancedsats[orb_pos].rotorposition.value)
KeyError: 0

Edited by Dima73, 28 February 2012 - 20:56.

[rhinoceros]

@Dima73,
Can you, please test exactly the same scenario with the old plugin file just to confirm that this is indeed an issue that has been existing prior to the upgrade.

[rhinoceros]

after fresh install positioner setup works, but after I memorised few positions, GS when press ok on plugin. I was try to deinstall and install plugin again, but nothing helps.
et9000, latest pli

Can you please post your settings file (/etc/enigma2/settings).

[Dimitrij]

@Dima73,
Can you, please test exactly the same scenario with the old plugin file just to confirm that this is indeed an issue that has been existing prior to the upgrade.

Checked.
In the old version everything is fine.

[Dimitrij]

The problem in line 1198:
def keyCancel(self):
self.close(None)

The simplest solution:
def keyCancel(self):
self.keyGo()

Although it is not correct.

[rhinoceros]

Indeed this is not correct. What I understand is that you are using tuner B, diseqc 1.1, advanced. The error is here: "found no useable satellite configuration ...". You should not even be allowed to get so far as to be able to open the Tune screen. That is what I meant by pre-existing issue. Question: with the old plugin, can you open the Positioner setup screen and press the Tune button? If yes, that is where the error is, since there should be no satellite available on tuner B for the positioner screen. You can use Satfinder for tuner B, but not the positioner plugin.

[Dimitrij]

Question: with the old plugin, can you open the Positioner setup screen and press the Tune button?

Yes, I wrote above.
In the old version, I can the press Tune button and press exit.
Without the crash.

[Dimitrij]

Anyone I have made, the plug must not cause a crash.
What the user did not.
For me this is the main condition.

Edited by Dima73, 29 February 2012 - 06:30.

[littlesat]

[Skin] SKIN ERROR in screen '<embedded-in-'TunerScreen'>' widget 'widget': {infinity-hd-full-info/skin.xml}: component with name 'introduction' was not found in skin of screen '<embedded-in-'TunerScreen'>'!. Please contact the skin's author!
action -> SetupActions cancel

Isn't this not skin related... the new screens are not alligned with this skin.... And chicken and egg story.....

A work-a-round could be to define a custom screen so foreign skins do not steal the screen by an old style but now crashy screen.... We can add the new screenname in the plugin itself... or in skin_default.xml... so a foreign skin cannot steal it anymore,

Another solution is alter all those third party skins .... this is somehow not done....

Edited by littlesat, 29 February 2012 - 08:17.

[rhinoceros]

I agree there should not be a crash. But the problem is also not in the skin or the screen definition. There is allways a plaster way to solve this, i.e. we circumvent the problem, but then the real problem is not solved.

Before the positioner setup is started, there is a check whether there are nim's connected to a rotor. If not, there is a messagebox telling the user and the positioner setup is not even started. Apparently, this check is OK. There are sats on a rotor, but for only tuner A. But on tuning from tuner B there is no switch to tuner A, therefore, the tuning is inconsistent. A fix for this crash should not be in the code of the positioner plugin. I will see if I can dig a little further.

[rhinoceros]

@Dima73:
You can try this patch. In exactly the same case the tuning would still not be correct, but it will prevent the crash. Why the tuning (sometimes) does not work is not so easy to find out.

There is a diff included, so if the test is successful the diff might be applied to the repo.

Attached Files

•  PositionerSetup.zip   11.02KB   26 downloads

[Dimitrij]

Ok.
In the evening check.

[rhinoceros]

No reply from halflife yet but I suspect incomplete user configuration. I can use (meaningless) defaults just to prevent a crash in any case.

The patch attached here is cumulative. It includes the patch just here above.

Attached Files

•  PositionerSetup.zip   11.22KB   33 downloads

[adri]

Since the new positioner patches have been applied by Mirakels, the dish icon shown during a move of the rotor does not blink/flash anymore.
The old code used to flash the dish image once per second.

[Dimitrij]

Since the new positioner patches have been applied by Mirakels, the dish icon shown during a move of the rotor does not blink/flash anymore.
The old code used to flash the dish image once per second.

But there is information about how to move.
What is more important?