Posts by abu baniaz

Gjstroom has released PLI 3.0 images for the Sim2 800SE

guide contained in download package

You use this at your own risk. I am not responsible for any damage that is caused. Best to make a backup of your image first. I have however done this about four times to make sure that it is fine. I used it on GJStroom's 26th Sept 2013 build of PLI on a DM800HD.    




Programs used: 7zip, Putty and Filezilla.




IPK's have been named differently so they install in that order.  Transfer the ipks to the /tmp/ directory and install using the following command:




opkg install -force-overwrite /tmp/*.ipk 




List of ipks:
01_gst-rtmp-support_2.4-r0_mipsel.ipk
02_python-json_2.6.7-ml8.3_mipsel.ipk
03_libpython2.6-1.0_2.6.7-ml8.3_mipsel.ipk
04_python-simplejson_2.0.7-ml0_mipsel.ipk
05_enigma2-plugin-extensions-et-livestream_1.0-r0_mipsel.ipk
**Packages with original names attached in folder called "ignore these".




Transfer the "usr" folder to the root of the internal memory, they will fall in the right place. Apologies if unneeded files are contained. Overwrite any existing files. Reboot your receiver.




Hopefully OnDemand will work. As you are aware, 4OD does not work. There is an option to hide sections of the plugin when you press menu.




Output from putty session included for reference.

Most of these files are those provided by Chhertz. Credit to him.

I encountered same error. Re-copied the files over as per instructions and worked fine. Instructions/files could do with a tweak or two but works fine.

Have autobouquetsreader and autobouquets_e2.sh been given 755 properties?

Can you confirm you are using the sh4 architecture file?

If I remember correctly, on openATV images you place file in /usr/keys/ instead of /etc/

Attached is AutoBouquets 28.2 E1. It is unlike the E2 version, it overwrites existing bouquets and the numbering is not like the official receivers. It is unfinished but functional. If using the frontend trial, it will run silently in the background and perform a restart after it completes.

All the work is by Lraizer and some contribution by PaphosAl. The only things I have done is edit the autoscan file. Many thanks to both of them. The few edits I have made have been asterixed below.

By Lraizer @UKCVS
Some contribution by PaphosAl.




Here is AutoBouquets E1 28.2E plugin that works on OpenPli dm500s image
(Should also work on other pcc stb based images, but not tested on any)(*Tested on TM 500 Super with use of frontend trial)




The coding is not finished and some options in the menu don't work yet. 
It is still only a "BETA TESTING version, use at own risk of losing your bouquets. 
Best to backup any existing bouquets before you transfer this package. 
*It replaces existing bouquets.
*Not official numbering







1)
install all files to their relevant folders
(You only need the /var/lib/libstdc++.so.6 if the plugin does not work without it)(*TM500 Super required it)







2)
chmod 755 all files in /var/bin/ with telnet command:
chmod 755 /var/bin/*




3)
reboot box




4)
zap to any active 28.2E service so that you are currently viewing a working channel




5)
press yellow button for AutoBouquets E1 28.2E PPanel GUI, setup your options, not all options are working yet.




6)
press download bouquets and select your local area, go put the kettle on...
as scanning will take just under 2 minutess, so can be done during the ad breaks while making a cup of tea




PS:
autobouqets e1 also generates an up to date channels.uk file in /var/etc/ for use with weekepglog plugin




*7)
FrontEnd Missing
If the panel does not show up. eg on a TM 500 Super, then extract "AB E1 plugin frontend trial" and send files to correct locations and repeat steps 2 and 3 above. If using the frontend trial, the default location for generated bouquets is London. To change this, edit the file called "autoscan" located in /var/bin using a Linux compatible editor. All you have to do is add a # on one line and delete it from another.

You have tried a virgin image from another forum and also this one. This to me sounds as hardware issue. PSU is first suspect

PAphosAL and Lraizer recommend that when flashing, use DreamUp. Flash erase first then flash image. Also use the network cable. not just null modem.

Have you tried a different PSU to confirm it is not faulty?

7zip will extract ipk files.

neecarl
BLUE > BLUE > YELLOW >RED

Just to be on the safe side and avoid errors, could someone upload the config files and I'll upload a backup with them included..

Have you tried a reflash?

Just tested it, oscam and CCcam started fine and with oscam first. I used the same configs and emulator binaries as you had in your backup image. I did not touch miniops.

ladder 49, if the buttons presses do not resolve your issue, best to start oscam using telnet to find any errors that pop up.
ps
............ will show what is running
/var/bin/emu/oscam
.............will start oscam for you and show any errors

thatfellow, have you seen this image?
UkCvs.net Forums

Considering I started that thread, I am surprised that it has not got carried over to 14.7. These things happen. Hints and tips readme file has the following

Some users wish to run oscam AND CCcam together, but need oscam to always load first, in order that it grabs priority over CCcam for the CardReader. Your wish is our command! 
LraiZer has tweaked Mohoush's original softcam nenu code logic so that this cam start order should now (in theory) be obeyed. Feedback awaited please...

I will check and pester PaphosAl to fix it properly (if applicable). He has already fixed the mgcamd coming out of standby issue. May take some time as he is concentrating on souping up the getepg code.

Oscam starting before other cams was incorporated into 14.7 as far as I am aware.

Best way to check what is running is to execute the ps command using telnet.

There is no startup script. Press Blue > Menu > Red to enter the softcam menu. You can enable the softcams from there. Oscam will always start before CCcam.

Is lxml available for 0E 1.6?

What image are you running and what satellite configuration have you got?

A bug has been found in VIX image and fix will be included in image soon. If you want to do it now, the following as per Rob Van der Does. W

Quote

I think we found the bug.
You can try for yourself using the attached file (unzip to /usr/lib/enigma2/python/Components ).
Restart Enigma2 and remove the file after the restart.

The motor's LNB can be on any port on the switch, just make sure that the diseqc commands match. Also using LNB 1 (can be any) in the config for all motorised satellites means fewer button pushes when configuring.