Posts by s3n0

    Surflock - this means that it is impossible to decode multiple channels simultaneously in one decoding card. I don't know where that dirty text comes from (YOUR CARD IS FUCKED UP WITH SURFLOCK), but if it's true that you have an active Surflock on your card, you can't share it anymore (watch more than one channel at a time from this one decoding card).

    Surflock is included in some decoder card firmware and can be activated remotely by controling / management packets (EMMs).


    It is also possible that Surflock was activated automatically in the built-in firmware when trying to decode very many channels (different streams or the same channel multiple times in a very short interval) simultaneously.


    You can still try another version of Oscam - just to be safe. Ideally, if you download Oscam from a source other than the one you are currently using. However, this probably won't help you anymore.

    2.0.191111

    - further code tuning for OE2.5 users - for ".deb" packages (thanks to chocholousek )

    - finally fixed the problem with incorrect saving / loading of satellite selection settings


    Upgrading to this version of the plugin may cause a problem with the type of configuration variable ("dictionary" type) stored by the old plugin in the "/etc/enigma2/settings" file. You may need to reset your old plugin configuration. This can be done via the Shell / command-line:

    -for OE2.0:

    init 4; sleep 5; sed -i '/config\.plugins\.chocholousekpicons/d' /etc/enigma2/settings ; init 3

    -for OE2.5:

    systemctl stop enigma2; sleep 5; sed -i '/config\.plugins\.chocholousekpicons/d' /etc/enigma2/settings ; systemctl start enigma2

    2.0.191109
    - solved problem with loading of saved satellites ... after restarting set-top box, it was not possible to load saved configuration of satellites (thanks to saragusa )

    - resolved issue of picon update method for TV + RADIO (thanks to chocholousek )


    2.0.191110

    - solved a problem with slow internet connection ... extended longer timeout (thanks to saragusa )


    (still in testing, but fairly functional version)

    I need to see the DebugLOG file. :derpthink:


    The NOOP error is shown when the picon update process does not start at all for an unknown reason. The process is performed in a separate thread, and I will only see a specific error in DebugLOG.

    Hello saragusa !


    Please try updating the plugin to the latest version 2.0.191108 via the configuration plugin MENU (yellow button on RCU). You will have to reset the selection of the required satellites (the type of satellite selection has changed).


    If the problem persists, can you describe it in detail ? Will you see any specific error while updating the picon ?


    Are you sure you have enough free disk space ?


    If a crash occurs in Enigma/OpenATV, a crash-log file should be created in the "/home/root" folder after the crash. Is there some crash-log file ? Can you send it to me as a private message or to a discussion forum ?


    Alternatively, you can turn on DebugLOG in OpenATV, GUI-MENU, and then restart the set-top box. After the error, you will find the debug-log file in the "/home/root/logs" folder and there should be more details about the error.


    Thanks.

    Hello.


    It depends mainly on which platform receives your stream. VLC or Enigma have no problem. In the case of KODI / XBMC or other decoders, there may be a problem with the correct configuration. However, Enigma always handles everything :). In Enigma, everything can be solved - it's just a matter of your free time, how much time you have left.


    If you have Enigma set-top-boxes everywhere and if you have at least one box on the original DVB source, then you can share the entire file "epg.dat" in Enigma. It’s enough to update it every three days, for example. However, the use of "epg.dat" may differ on some Enigmas. Not every Enigma is set to automatically and periodically save the "epg.dat" file to internal disk (it is usually held only in RAM memory and is saved only when the Enigma is stopped). Also, not every Enigme file is stored in "/etc/enigma/epg.dat" as on OpenATV, but on OpenPLi, for example, the file is stored in "/media/hdd/epg.dat".

    quinquelhas :


    If you only use Linux set-top boxes everywhere, you can do a primitive bash script to copy EPG data from the primary set-top box. Also install the EPG-Refresh plugin on the primary set-top box and set to automatically refresh EPG data every night when no one is watching TV.


    This actually creates a new "epg.dat" file with fresh information. Depending on the type of Enigma, it is necessary to set automatic saving of "epg.dat" file from memory to disk. This means that not only during shutting down the Enigma, but also preventively saving "epg.dat" to disk. Unfortunately, each Enigma does this quite differently.


    Finally, a script that uploads a full "epg.dat" to the server is sufficient. With the rest of the Enigma you download this file from the server and then restart the Enigma and switch it back to standby mode (most Enigma distributions always start in active mode after restart).


    You can also find some EPG scripts on my github profile (even a simple plugin to download an EPG file), but you may need to customize them because Shell scripts are optimized for running in OpenATV: https://github.com/s3n0


    In order to include EPG data in the stream, I don't know anymore. Obviously you have to enable this somewhere in the Enigma configuration. For example, under the OpenATV Enigma, it is possible to enable EIT and AIT to be included in HTTP streams in the EPG settings. But EPG data should already be included.


    For IPTV streaming, however, it is ideal to use a Linux PC machine with Tvheadend installed as well as a PCIe card - as a satellite tuner. Set-top boxes are not good for streaming IPTV. Maximum if you have two tuners in a set-top box and one of them will be used by an external client. However, this is more about using a secondary tuner by the client rather than IPTV streaming.

    Thanks for that information mate, as well could you please refer me to an oscam tutorial setup?

    Files I need to configure and other stuff related to that please?

    Thanks once more for support.

    All you need is basically just a binary file, but compiled for your particular chipset (mipsel, arm, sh4). Softcam can be run on Linux, through the system, you don't need Enigma at all. Enigma or graphical interface is only necessary in some cases to monitor Softcam via this graphical interface (via Enigma) - for users, but this is not necessary as Softcams can also be monitored via the web-interface.


    So ... simply put, the dependency on Enigma is not so important unless you need to monitor Softcam's functionality through the Enigma graphical interface (using the buttons on the RCU).


    If you can install and run softcam in a Linux-only way, Enigma is not at all, and you only need to know the type of chipset architecture on your device. You then download the appropriate softcam for your chipset from the Internet and upload it to the appropriate folder (usually in the "/usr/bin" folder), and then configure a Softcam launcher (usually in the "/etc/init.d" folder). Manual procedure (beware - often without the possibility of watching Softcam also from the graphical interface via RCU on the TV screen):

    Tutorial : How to install softcam (OSCam/CCCam) manually, if you hate ipk packages


    As for the configuration, unfortunately you have to know it. At least basic knowledge of SoftCAM (such as Oscam) configuration is required! Configuration files that are shipped by default do not work in 90% of decoding cases. You usually have to set many things so that the decoder card works correctly.


    If you are missing a configuration file, you can create it directly through the Softcam Webif interface (http://box_IP_address:8888 or port :83). Just change the random item in the Config->Global menu, i.e. for the "oscam.conf" file and have the changed configuration saved. The file "oscam.conf" contains only global settings. The most important files are "oscam.server" and "oscam.user".


    Oscam configuration files are described here:

    http://www.streamboard.tv/wiki/OSCam/en

    Unfortunately, the user icons for the channel list name do not address this plugin. So far, only channel icons (picons) are available in this plug-in.


    I am planning to add picons conversion for OscamWebif ... but I don't have enough free time :). I have to solve (test in several Enigma distributions) dependence with another Python module for image processing (PIL / Pillow module).

    Depending on the version of Enigma used, there may be some minor problems. As for the set-top-box type, I was mainly interested in the architecture of the chipset (CPU). There may be several Cccam compilations / versions for a particular chipset. I don't use Cccam because it's waste time. My last experience was that the newer Cccam 1.45 in my friend's box didn't work at all (the configuration remained the same), so I went back to the original and old version 1.35.


    If your problem is related to a problem like SKY DE (common problem) then try these Cccam:

    https://community.helpsite.com…m-version-for-sky-germany


    You haven't even given a LOG so I can at least have an idea of a possible error in your case. I can't help you, sorry, because you didn't write the necessary information (you probably know why, too).

    Dude... what about your set-top-box, PLi version, CAID or satellite provider or country ?


    If you use a randomly paid pirate server, I am unfortunately unable to advise you.

    Yes, using subversion and apt-get:

    OSCAM on Debian 9: possible?


    If Oscam is already installed via svn, it will probably be enough to update it (download sources and compile).


    On the Internet you will find a procedure for installing Oscam for each Linux distribution (usually the installation procedure is the same everywhere). It is best to compile your own and always the latest Oscam directly from the Streamboard server. SVN is also used for this purpose:

    http://www.streamboard.tv/oscam/wiki/BuildingOscam

    First, you should write down your level of knowledge of IT and satellite technology :) and whether you know at least the basics of Linux. Otherwise there is no point in sending you a complete tutorial with explanations (above in my post). You really need to know the basics (what is a flash drive, what is a shell, what is a binary file, and so on).


    I wrote everything to you. The questions you ask are therefore incorrect. Most Enigma2 distributions require a binary in the "/usr/bin" folder. Then you have to set the execution rights. As I wrote before (there is a link to this forum, a short article for manual installation).


    However, everything is explained in the post above - the link above! Write less! Read more and search more!


    You can find out the chipset architecture, for example, by uname -m command, but I write it again for the second time.

    Hello. I do not know which Enigma you are using, but in the Plugin-MENU, each Enigma2 should also include a Set Password plugin (system-plugins). So try to find this plugin in Enigma2 Plugin-MENU and install it. Use it to clear the password.


    Or try the official plugin from the OpenPLi-7 feed server:

    (copy it with a PC to a USB stick, then insert the USB stick into the receiver and install it via the GUI MENU in Enigma)

    enigma2-plugin-systemplugins-setpasswd_6.3+git6799+bf513b0-r0.ipk


    Normally, the password can be changed in the Shell (terminal) with the command: passwd

    Hi @EML . Thanks for the report. If possible, please try the following commands in the terminal:

    Code
    ping -c 1 -w 1 www.google.com
    echo $?
    
    ping -c 1 -w 1 www.google.com > /dev/null 2>&1
    echo $?
    
    ping --help

    Nowhere else will be the problem. I use this primitive method to detect the internet - through system, without using a Python socket module, so the error must be in the problem ping "command". Thanks.


    EDIT:


    SatDreamGr uses the same command to test connectivity, but without the -w 1 argument. It is quite possible that the ping command in the SatDreamGr firmware does not know this argument (it only knows -c 1).

    https://github.com/satdreamgr/…gr/Hardware/plugin.py#L87

    I do not recommend using the "nodeid = " configuration parameter. Many users from the discussion forum copy and use it everywhere in all their configs. Then collision situations arise (users copy it everywhere). Use a nodeid only if instructed by the administrator of the softcam server (who will give you this node).