On the VTi-forum they made a patch for the NimMager in PLi; that seems to be working fine.
Yes true, I can confirm that ...
Edited by Firex, 1 July 2013 - 13:07.
Posted 3 August 2013 - 16:13
I took a little time to investigate the loopthrough issue.
The "problem" in the drivers is that they report /proc/stb/frontend/X/rf_switch only on frontend 0. Nim manager expects to find it in /proc/stb/frontend/1/rf_switch when enabling loopthrough tuner A to tuner B.
If you manually do "echo -n internal > /proc/stb/frontend/0/rf_switch", it works fine.
The other VU+ receiver that has internal loop-through is VU+ Duo. On VU+ Duo, the rf_switch is located on frontend1, and internal loopthrough works ok for B. So it seems that for VU+, this setup is consistent and not a bug. It applies rf_switch on the tuner that can be setup as loopthrough. Which other boxes also have internal loopthrough? Xtrend do not have external loop.
Posted 3 August 2013 - 21:33
dm8kWhich other boxes also have internal loopthrough?
OK, so how does dm8k handles loop through? Which frontend has the rf_switch option? Can dm8k do loopthrough A->B and B->A?
VU's hack was "ugly" but I think we can improve the code to support all cases without ugly hack or box specific option.
Edited by malakudi, 3 August 2013 - 21:34.
Posted 11 August 2013 - 18:08
It's on /proc/stb/frontend/1. IMHO the most logical place, that's the tuner that is influenced, not tuner 0. So if VU+ would have use the same approach, it would have worked out of the box, apparently.
* Wavefrontier T90 with 28E/23E/19E/13E via SCR switches 2 x 2 x 6 user bands
I don't read PM -> if you have something to ask or to report, do it in the forum so others can benefit. I don't take freelance jobs.
Ik lees geen PM -> als je iets te vragen of te melden hebt, doe het op het forum, zodat anderen er ook wat aan hebben.
Posted 14 November 2013 - 05:40
If you manually do "echo -n internal > /proc/stb/frontend/0/rf_switch", it works fine.
The above solution works great, but the variable is lost after each box or enigma2 restart. I tried to add the function in /etc/init.d/ and link it in /etc/rc3.d/ but the box does NOT recognize it (cat /proc/stb/frontend/0/rf_switch returns "external"). It seems this must be ran after enigma2 is loaded but my skills are too limited to do this. Anyone can help? Thanks!
Posted 14 November 2013 - 15:34
OK I solved the problem of LOOPTHROUGH for the SOLO2. The trick is to make sure it runs AFTER enigma2 is loaded.
(a) connect your coax to LNB2
( setup receiver with TUNER B as the configured tuner, TUNER A as loopthrough to TUNER B
© make a script with enough sleep time to give enigma2 time to boot (loopthrough.sh here):
Don't forget to chmod u+x both files and add the "&" at the end of the call otherwise it will not run in parallel to the Enigma2 boot.
Posted 16 April 2015 - 09:11
thanks for info
but unfortunately, after i put nimmanager.py from link in thread you post (post nr. 26), after restart GUI i got only open pli start image, remote control doesn't work, i need to reflash image.
i don't understand german, so maybe i'm doing something wrong..
i don't understand part with opkg install enigma2-src. i tried this in telnet but i got some errors.
could you pls help, step by step in english please?
maybe nimmanager.py is wrong in attachment in post nr 26.
Posted 16 April 2015 - 09:45
i tried also this nimmanager.py:
http://sourceforge.n...s/NimManager.py
i deleted line that should be deleted but again after restart only open pli image at boot and remote doesn't work
i really don't understand what should i do..maybe delete nimmanager.pyo first? the one that's in the box as default?
i have open pli from 19.1.2015., maybe i neeed newer version (but this one seems more stable than newer versions i tried, regarding media player which i use very often).
Posted 16 April 2015 - 10:39
ok, i made opkg uppdate and now opkg install enigma2-src was ok.
i have nimmanager.py and nimmanager.pyo in box.
but now clock is wrong it's 11.33 and box shows 9.33, in menu-setup-timezone i can't change timezones, it says only UTC.
also, after deleting that sentence in nimmanager.py (if nim2 == (nim1 - 1), after restart again no booting and remote doesn't work...
i'm going mad..
Posted 16 April 2015 - 10:40
You have to change the actual "NimManager.py" (old "NimManager.py" from post doesn`t work anymore).
To get the actual file, you have to install the enigma2-src in Telnet with "opkg install enigma2-src". After that, there is also a file "NimManager.py" in direction "/usr/lib/python/components". This file you must Change ...
If there was an error, in telnet after "opkg install enigma2-src", are you sure you have no mistake or space when typing?
Unfortunately I am not at home and can not try it.
Posted 16 April 2015 - 10:44
in last post (maybe you didn't see it), i said i managed to install enigma2-src, but now clock is wrong and i can't make changes in menu-setup-timezones..
also, i changed nimmanager.py in the box, the one i got after installing enigma2-src, and again no booting after restart, remote control doesn't working.
Posted 16 April 2015 - 10:51
Edited by Firex, 16 April 2015 - 10:55.
0 members, 4 guests, 0 anonymous users