Posts by s3n0

  • Automated oscam script Updated 100%

    Quote from sagher

    Will you please create a automated script for pc linux vps x64 and x32? it is really a hard job to upgrade oscam almost every week.

    Why difficult to update? Create your own Shell script and schedule it to run via CRON. In your Shell script, be the first to stop Oscam service. Then you update Oscam using SVN tools. And in the third step, you restart Oscam (usually using some startup script in the "/etc/init.d" folder). Everything is easier on a Linux PC than with set top boxes. That is, provided that you have at least a basic knowledge of writing Shell-scripts.


    Quote from odem2014

    is this script need to be updated ?

    What update do you mean ? Do you think it is always necessary to update Oscam ? Or is it necessary to update the functionality of the script ?


    All:


    Who would want to ... it probably doesn't belong here (the script is dedicated to another author), but for use in Enigma2 set top boxes, I also created an update script for Oscam. My script uses the source of the Oscam binaries from the SpaceRat team and is intended for the OpenATV image. I haven't tried functionality on other Enigms, but some functions for detecting the Enigma kernel version (OE Alliance Group version) may not work correctly in OpenPLi, for example. However, the script could theoretically work in OpenPLi as well. If anyone is interested, just adjust the parameters at the top of the script as needed and then schedule the script to run via the CRON controller. Upload a script e.g. to the "/etc/init.d" folder or to "/usr/script" folder, assign it execute permissions ("chmod a+x file_path"), and then add an entry to CRON to run this Oscam-update from my shell-script. However, I do not know exactly what all the modules in the Oscam binary from SpaceRat feed-server - i.e. what libraries / modules are included in the Oscam compilation... for example: cache-ex support, support for Phoenix readers, support for USB readers in general, and other modules in the binary. Of course the basic modules are compiled in Oscam as they should be. But some additional modules may be missing (for example, support for reader protocols such as smargo or mp35).


    https://github.com/s3n0/e2scri…am-new-version-updater.sh

    (Information on the use of the script is also given in the file itself, right at the beginning.)

  • delay while change channel

    You could view or post to the discussion LOG from Oscam. What's going on there. It may be possible to find out from Oscam LOG. Passwords should not have any passwords and you can rename or replace IP addresses / host names with # characters, if there are any.

  • how to connect satellite receiver card to oscam server

    Hi.


    Unfortunately, this is a more complicated explanation ... your provider or decoder card must support "sharing" as first. If it also supports sharing, it may have a protection algorithm present, such as SurfLock - blocking the card for a certain period of time (or permanently - depending on the firmware in the decoder card), when trying multiple accesses to decode the ECM - simultaneously for multiple satellite channels.


    Some decoder cards are also paired with the original device and you need to find out this pairing key for Oscam if you want to insert the card into the universal reader. Finding a pairing key is also a very complicated process (some people can do it for money). But even if you get a pairing key, you're still not sure if the card will work as "shared" for decoding multiple satellite channels at once.

  • Need help with log

    Don't have a decoder card inserted the other way around? Show us your oscam configuration files (if you have any passwords and IP addresses, rewrite them with the # character, for example).


    How to converting C-Line Cccam to Oscam: How to setup Oscam.server on H 7 C box


    I don't see any "proxy" (remote card reader) in the LOG records, so why do you want to convert the C-Line connection ? Only the failure to create sci0 and sci1 (lower and upper universal physical reader in the set top box) is noticed in the LOG. There can be several reasons for this.

  • oscam stopping after 20 mins

    What does your OscamWebif LiveLog show (after disconnection) ? What type of disconnection do you see there ? Copy it here to the post, to the CODE TAGs. If there are any usernames, IP addresses, passwords, then rewrite them with the "?" character.

  • READER DEVICE ERROR ubuntu 18/Oscam..

    How about trying another "mouse" protocol:

    Code
    protocol       = mouse
device         = /dev/ttyUSB0

    Well, if it already works for you, then OK.


    However, always make sure that each time you work with the configuration, your Oscam has already been compiled, including the appropriate modules:


    b73480.png

  • READER DEVICE ERROR ubuntu 18/Oscam..

    So what ? Did the "smargo" protocol and the use of the USB interface help ?


    Specify exactly which external reader you own (photo or URL).


    The "mp35" protocol, as far as I know, is used for external readers with a programmer. Not for ordinary external readers. So with the "mp35" protocol, it's useless to try.

  • Oscam script on Enigma2

    Hi.


    First, you should state which Enigma you use (OpenPLi, OpenATV, OpenHDF, etc.) and also which Oscam-launcher (when booting) you use (which also depends on the Oscam installation package, but also on the Enigma used).


    Linux set-top boxes / Linux op. systems usually have the CRON scheduler already pre-installed and you can check it also via the Shell:

    opkg list-installed | grep -i "cron"


    If CRON is not pre-installed already, it can be installed manually (via the Shell / command-line terminal):

    1. opkg update && opkg list | grep -i cron - to view available installation packages of the CRON
    2. opkg install enigma2-crontab-package-name to install the appropriate package
    3. reboot - reboot the set-top box


    Next, just edit the scheduler configuration file, which should be located here: /etc/crontabs/cron/root.

    Add a new line... intended for the type of Oscam trigger via shell-script, which should be present in the folder /etc/init.d:

    Code
    00 03 * * *        /bin/bash /etc/init.d/softcam restart

    - every day at 03:00, will executed the command for Bash shell, what runs the "softcam" script - with "restart" argument

    - if the script filename is different as "softcam", then change it by your needs... for example "softcam.oscam", "SoftCAM.sh", "Oscam_launcher.sh", etc.


    And restart the CRON service, or whole system / set-top box again.

  • Phoenix Smartmouse card reader error

    The correct device designation is in the Oscam configuration, which is detected by Oscam itself from OS. This can be viewed in OscamWebif -> Readers -> USB Scan. There should be a USB reader visible and this device name (code) should be used, according to the numbers that will be there BUS number : Device number.


    It's probably stupid, but try this:

    (this probably only works on a full-fledged linux, which can also properly handle the serial interface with the converter to the USB interface)

    Code
    protocol     = smartreader
device       = Serial:AL016X0S

    https://wiki.streamboard.tv/wiki/OSCam/en/examples/Reader

    https://wiki.streamboard.tv/wi…are_supported#Card_Reader


    BTW, if there is a switch on the card reader and you are trying to switch the correct mode, you have to do it when the reader is disconnected from the set-top-box. It would also be advisable to restart your Oscam (or the entire op.system) after reconnecting the card reader. You can always check the card reader after its reconnection, via dmesg, for example as: dmesg | grep -i "usb"

  • Phoenix Smartmouse card reader error

    Hi.


    What does Oscam LOG look like ? What does the initialization of the reader look like step by step ?


    Is the 4.8 MHz scaling crystal OK ? Why 4.8 MHz ? Is this frequency appropriate for your card ? If not, change the crystal (with the reader off) and then turn it on again and test.


    What encoding do you use ? I mean the provider, the CAID, the decoder card, ... and similar information.


    /// EDIT :


    I don't know Conax cards very well, but the Conax frequency should be about 5 MHz and not 4.8 MHz. Conax encryption may also require a pairing RSA key - to the oscam.server configuration file for your reader section. Write which Conax card it is (CAID code and name of the DVB provider).


    In addition to what master G wrote, also check the support for CONAX (it should be: YES). You can also find the supported functions via Oscam Webif: http://IP-address:8888 and then go to Files -> oscam.version, ... and scroll down the web-page (check Conax support and Phoenix support at your Oscam).

  • Oscam entitlements not updating

    NoGod1992:


    What provider / CAID / card encoding you use ?


    Why do you answer a 3-year question and not write a new question ? Does this apply to the same CAID and provider for the CZ / SK country as in the last comment of this TOPIC ? Is your problem related to CAID 0D97 how gersey wrote, or is it CAID 0B00 (encoding Conax) as newbone wrote ?