136 replies to this topic

[gerard0610]

@ Littlesat: Thanks.

I will try this tomorrow morning after the nightly build.

[littlesat]

you can also try to download the NimManager.py from our sources and but it on your box on /usr/lib/enigma2/python/Components... and then restart enigma2.

[gerard0610]

you can also try to download the NimManager.py from our sources and but it on your box on /usr/lib/enigma2/python/Components... and then restart enigma2.

Strange,

You mention (and I have donloaded) ‘NimManager.py’ and in my satellite receiver I see only the file ‘NimManager.pyo’ in /usr/lib/enigma2/python/Components.

What to do?

[Dimitrij]

http://sourceforge.n...s/NimManager.py

[betacentauri]

The .py file is the source code. The box compiles it automatically and generates the .pyo file. So only put the .py file in the same directory as the .pyo file and restart e2. Then the .pyo will be generated (it overwrites the original). After the restart you should delete the py file again.

Edited by betacentauri, 20 April 2014 - 17:56.

[gerard0610]

The .py file is the source code. The box compiles it automatically and generates the .pyo file. So only put the .py file in the same directory as the .pyo file and restart e2. Then the .pyo will be generated (it overwrites the original). After the restart you should delete the py file again.

bedankt.

[gerard0610]

you can also try to download the NimManager.py from our sources and but it on your box on /usr/lib/enigma2/python/Components... and then restart enigma2.

I preform this action with success with the help from ‘betacentauri’

 

The green screen is gone however the rotor is not working (no moving).  ('All satellites' on 'LNB 65' with the same adjustments  as I have used in the past)

[littlesat]

I do not have a rotor... so for me it is difficult to debug

 

The only thing I can do is go back to 32 LNBs in short term when I do not have help from someone who is using a rotor.

Edited by littlesat, 20 April 2014 - 19:28.

[littlesat]

I just found an additional mistake... This will be committed soon.

Edited by littlesat, 20 April 2014 - 19:33.

[Huevos]

As far I can see LNB 33, 34, 35 and 36 is used for unicable...

I do not have unicable... so I cannot check if I break this.....

No, not Unicable. It is used for "All satellites 1/2/3/4".

 

By the way can't just modify nimmanager.py, but also Screens/Satconfig.py.

[Rob van der Does]

I do not have a rotor... so for me it is difficult to debug

This is a common mistake: when you tell E2 a motor has been connected, the system actually believes you and performs everything as if an actual motor is there.

[littlesat]

If it was so simple Satkiekerd, than you better do it instead of me...

 

I just tried to get all those 64 LNBs and experienced all struggles... just because my configuration is not able to test it...

 tried as far I could...

 

At least the 64 sats patch came from openPli... and debugged with help from our forum visitors...

 

No, not Unicable. It is used for "All satellites 1/2/3/4".

I already discovered... but tel what I need te change in satconfig??? Please point me to what to modify (when really required)...

Edited by littlesat, 20 April 2014 - 21:57.

[Rob van der Does]

..... I have set ‘All satellite 1’set as in figure “DiSEqC adjustments All satellites 1.jpg”. ....

A bit off-topic, but seeing you use the 'all satellites 1': what are 'all satellites 2/3/4' for?

[gerard0610]

..... I have set ‘All satellite 1’set as in figure “DiSEqC adjustments All satellites 1.jpg”. ....

A bit off-topic, but seeing you use the 'all satellites 1': what are 'all satellites 2/3/4' for?

see message no 19: http://openpli.org/f...rs/#entry418258

[gerard0610]

This morning Update my VU+Duo and ….

Yes,Yes,Yes, It function now correct

I have now select:
All satellites 1, LNB 65 and USALS (Yes). See picture.
and I have so programmed 'all satellites' and my rotor is moving to the selected satellite position

 

Because I have also a tuner 32 LNB’s but no 33 or more LNB’s I cannot check this options ‘LNB 33’ untill ‘LNB 64’. This need to be tested by someone else (Huevos?).

LNB’s 1 untill 32 are working correct.

 

@Littlesat: Thank you very much.

Attached Files

•  DiSEqC adjustments All satellites LNB65 1.JPG   28.85KB   29 downloads

[littlesat]

Thanks for the feedback...

[Rob van der Does]

..... I have set ‘All satellite 1’set as in figure “DiSEqC adjustments All satellites 1.jpg”. ....

A bit off-topic, but seeing you use the 'all satellites 1': what are 'all satellites 2/3/4' for?

see message no 19: http://openpli.org/f...rs/#entry418258

That is what I was referring to. And hence my question what 'all satellites 2/3/4' can be used for.

[gerard0610]

@Satkiekerd.

 

Sorry, I didn't read your question not clear enough.

But I have also no answer to this question.

[Rob van der Does]

OK, to prevent further off-topic posts, I asked the question in http://openpli.org/f...ig/#entry418519

[Dimitrij]

littlesat

Can be so?

advanced mode -->LNB > 32

--- a/Satconfig.py
+++ b/Satconfig.py
@@ -328,7 +328,7 @@
 				self.list.append(getConfigListEntry(_("Increased voltage"), currLnb.increased_voltage))
 				self.list.append(getConfigListEntry(_("Tone mode"), Sat.tonemode))
 
-			if lnbnum < 33:
+			if lnbnum < 65:
 				self.advancedDiseqcMode = getConfigListEntry(_("DiSEqC mode"), currLnb.diseqcMode)
 				self.list.append(self.advancedDiseqcMode)
 			if currLnb.diseqcMode.value != "none":