Posts by s3n0

    Hi.


    I either need to own a physical set-top-box with the same Enigma you use at home (dm800se with NewEnigma2), or I need to see a real debug-log (not crash-log) from your Enigma, i.e. what exactly happens in it when you press the RCU buttons. Otherwise I can't help you. This is a specific problem, because on many cores of the new Enigma (OE2.5+), everything works fine.


    Blue button (updating your picons) - will not work because it is very complicated to do. There is some problem with running a single thread in conjunction with Enigma timers. It works everywhere, but not in your case (even if I use the new method for new cores of new Enigies). I would have to rework the whole algorithm again. Or at least debug this mistake as I mentioned above (ie if I owned dm800se with NewEnigma2 and if I played with it for a few days at home).


    Picon folder - do not press the OK button! The OK button should not work at all. Only in the case of the "user defined folder" selection and only for some Enigma distributions, the directory browser will also open automatically (not every Config-module in each Enigma, this unfortunately has a functional one).


    Update method + Picon folder after pressing the left / right arrow on the RCU - these things are a mystery for me. I would need a debug-log (not a crash-log).


    You don't have to write what works again and again! You create such incredible chaos. The discussion is then very difficult to read. Please always write only what does not work exactly. But as I said, it won't work without a real debug-log.


    I don't know NewEnigma2 very well. I don't know how to create a debug-log to a file ... maybe like this ?

    journalctl -f -u enigma2 >> /tmp/journal.log

    ... or :

    journalctl -f >> /tmp/journal.log

    ... or :

    journalctl -f -o verbose >> /tmp/journal.log (more detailed ?)


    This debug-log may also contain private data (login, password, IP address). It is better to send me the created "journal" to a private message or to Skype.

    espaun206 :


    Why everyone has to use foreign procedures that are also misspelled. The wget command downloads files so that it often fails to determine the name of the file to be downloaded, and then the destination on the disk is named exactly as the name of the URL address. Therefore, it is necessary to use the -O /path/file argument to avoid this problem. If you are downloading from a github server, many versions of wget have a problem with SSL, so try using the --no-check-certificate argument in wget.


    Of course, directory change command does not work: from -bash: cd: oscam-svn: No such file or directory Try searching your system for the downloaded "oscam-emu.patch" file: sudo find / -type f -name "oscam-emu.patch". Or find the directory only: sudo find / -type d -name "oscam-svn". Then use the change directory command (cd) again. So, change the current directory to the found "oscam-svn" directory.


    Assuming my directory estimate was correct... - probably the correct command and directory will be:

    cd /usr/src/oscam-svn

    ...instead of:

    cd oscam-svn

    Also the wget command is wrong ... it should be correct as follows:

    wget -O /usr/src/oscam-svn/oscam-emu.patch --no-check-certificate "https://github.com/oscam-emu/oscam-emu/raw/master/oscam-emu.patch"


    However, I don't know for sure, because I don't use any softcam in Raspberry Pi. The default user directory can be different ! Such as /home/pi


    Perhaps it would be better to use "git" instead:

    https://github.com/oscam-emu/o…d/wiki/Building-OSCam-Emu

    Dvbapi is an interface that creates a virtual user in your Oscam. It is the so-called loopback user. Oscam refers to himself in requests for ECMs. This means you can connect to yourself - as if with a softcam client, you connect to your own softcam server. Oscam joins himself with the helping of this virtual user.


    However, if you mean "oscam.dvbapi" file, it is different. This file is used to prioritize CAID, PROVID, and SID.


    Emulator module is part of OscamEmu. There is also an Oscam without an Emu module. The emulator serves as a virtual reader with a virtual card. So you don't need a local physical card reader or a remote card reader at all. All you need is the necessary keys - in the SoftCam.key file.

    Maybe only FTA channels are working ? :) I'm not sure if it's possible to share Conax cards that require pairing with the device. Does your Conax card require pairing with your set-top box ? Although ... you actually only connect the softcam client to the softcam server. Not directly the softcam client to the decoding card.

    Decoding cards with "entitlements" like your card do work on a different principle. Although the subscription package expires every month, at least one EMM impulse must be given to the card at this time interval (1 month) for refreshing the "entitlements". If it does not, the card will be blocked - the card becomes inactive. Then you have to send the so-called "activation EMM" to your card from the satellite provider. These EMMs in turn activate the card - they start it to receive all the necessary EMMs and ECMs again. So for the card algorithm to respond to ECM requests, the card must also be activated / registered. So it is not enough to have cards in the table, a valid end date for prepaid packages (entitlements) only. And maybe this is your problem. That means the right EMMs won't get on your card - probably because of incorrect Oscam settings (blocking of all unknown EMMs maybe ?).

    If it is true that every time you switch the tuner to TVP1, everything starts to work for your card, there is one easy solution: write a shell script that switches your tuner to TVP1 for 5 minutes every night, and then after this time, the script stops the tuner again. It's easy - you can use Enigma2 Open-Webif to switch channels.


    If the provider instructs you to switch the channel to a specific one, this is normal. The Provider simply does not want to overwhelm all its networks / transponders on the satellite with EMM packets, so it will use a simpler alternative for this purpose. The EMM commands for your card are sent primarily via one stream - via a specific satellite channel. For example, it will send this data continuously for an hour, every minute, and Oscam will send it to your card.


    It seems strange to me because Conax should have valid "entitlements" for a very long time. So it is enough to refresh the decode card only occasionally. This means that there is no need to overload satellite streaming with unnecessary EMM packets. Therefore, in my opinion the provider could send EMM to all clients and through all available stations, not just TVP1.


    How do your "entitilements" work ? For how long are they valid ? For a month ? For a year ? Maybe shorter / longer time period ?

    You can try to enable ECM lenghts as the following config ("oscam.server" file, under your "reader"):

    Code
    caid = 0B01
    auprovid = 0B01
    ecmwhitelist = 6C,76,88

    ( http://www.streamboard.tv/oscam/wiki/ECMLengthList )


    And file "oscam.dvbapi":

    Code
    P: 0B01
    I: 0

    But that probably won't help either.


    Why only via TVP1 channel ? I do not understand. Do you mean that, the provider sends EMMs only via the TVP1 station for your satellite card ? Ask the provider which EMMs exactly are sending ... because you cannot then block unknown-EMMs maybe ? Why are you blocking them ? Do they have to block ? :-) In my opinion, this blocking of unknown EMMs should not be there. I don't know for sure.


    What does an Oscam log file look like when your mentioned problem occurs? Will an EMM arrive or should it arrive, but no EMM will arrive?


    Back up your Oscam configuration and try this one which I found:

    [How-To] Oscam or Oscam & CCcam For TNK Smart HD+ (NC+) Caid 0B01


    Unfortunately I do not have an NC+ provider card, CAID 0B01, with Conax encoding. :scratch_one-s_head:

    Hello.


    Which DVB provider is related to your problem ?


    When it stops working, do you also follow the oscam-log ? Set EMM logging via "emmcache=..." in the "oscam.server" file.

    49eae6ebc7800767e.png


    Maybe the oscam-log will show the EMM that arrived when your Conax card coding stopped working.

    Have you got an file that can be installed through ipk installer? I’ve never telnet into box so not sure how to go about that. Thanks for the help.

    Download and connect to your set-top box using the PUTTY application, whether via Telnet or SSH connection. The login name should be "root" by default and the password, if you have not changed it, is empty - just press "ENTER". However, be careful - in the new OpenATV 6.4, it is necessary to select and set a password ! Otherwise, you will not connect via FTP, SSH, etc. . Without a password, you can only connect using the Telnet protocol. So when you connect via Telnet using the PUTTY app, I recommend setting a new password using the "passwd" command. You can find the IP address or DNS name of your set-top box in the web-interface of your WiFi router or in the Info-MENU in the Enigma-GUI (in the set-top box). The specific IP address in OpenATV should be traceable somewhere through:

    Blue Button -> Network -> Network Settings

    wget -O - -q http://updates.mynonpublic.com/oea/feed | bash



    in putty or telnet paste command and enter. wait few seconds and try download

    The complete procedure is as follows:

    Code
    wget -qO- http://updates.mynonpublic.com/oea/feed | bash     # add the new one feed/plugin source (with Softcams packages)
    opkg update                # update list of available packages
    init 4; sleep 5; init 3    # fast Enigma2-GUI restart

    Now, as the next step ... go to Plugin-MENU in the Enigma GUI and install some Softcam.


    Or also you can to use the following commands (instead of Plugin-MENU in Enigma-GUI):

    Code
    opkg list | grep oscam
    opkg install <some_package_name>

    Hello.


    Maybe you are asking for some Softcam feed in some Enigma distribution. Well, if no update is needed, even on the feed server will not appear a new version even a month. Only after testing the version, it will be uploaded to the Enigma feed server.


    If you always want to be up-to-date, you have to use binaries. However, they may not always be 100% reliable. For example, a programmer who added a new thing may forget some facts and Oscam may stop working properly. Two days later, for example, another programmer will notice the problem and report the bug to fix it, and then will released the another/corrected version. This 11576 version is a relatively new version compared to the current version 11578. If you still want the latest version, try to download and update the binary file in the "/usr/bin" folder for your set-top box (by CPU architecture) yourself. However, in my opinion this is not necessary.


    //// EDIT :


    I forgot to mention that in this forum many people use OscamEmu and not Oscam (without Emu). Therefore, the discussion thread for OscamEmu is more supported. There you will also find newer binaries than in the Oscam thread. But if you want, here is Oscam build compiled by juli13:

    Again, please note that the LINUX system must maintain the correct file and directory names. This is the so-called case sensitivity. The file name should be correct as SoftCam.key as described in the configuration instructions on the above OscamEmu website. Not softcam.key, not Softcam.key, etc. ... use just the correct filename: SoftCam.key


    ////////// EDIT :


    Hmm, or the correct name is just the SoftCam.Key ? :-D

    I dont know... sorry... it is a mish-match...

    Source: https://github.com/oscam-emu/o…dule-emulator-osemu.h#L10


    I don't use OscamEmu, so I don't know how exactly the name of this file is defined.

    Maybe the case is ignored when searching for the correct file name.

    Or do I use the file name "oscam.key"?

    Sorry, but if you were wondering if the server could detect your illegal connection multiple times with multiple set-top boxes at the same time, it really depends only on the skill of the softcam-server administrators.


    It depends on which method of detecting the illegal connection (re-share) the server uses - for example: Cccam NodeID, different IP address, higher number of ECM requests in the last 10 seconds, number of connections under one account, number of HOPs, etc. .


    Although most of these methods can be fooled, what cannot be avoided is the number of ECM queries from the server at a certain time interval. If the server detects that at the same time from your IP address is required 3x ECM, always for a different channel, of course, the server can evaluate as an unwanted connection from multiple set-top boxes at once.

    Please create a new thread or request some moderators to move a post to another thread. This thread is not about Oscam-Emu support, but is used to discuss about Softcam-feeds.

    See the URL link I mentioned above for Oscam-Emu ( https://github.com/oscam-emu/oscam-patched/wiki ). The configuration of these Emulators is also described there. I don't use Oscam-Emu at all, so I can't advise you very well. In the forum thread about Oscam-Emu threads will certainly give you some advice. I think in "oscam.server" should be correct: device = emulator.