Posts by s3n0

Hi.

Yes, of course FTA channels do not need to be decoded at all and therefore they bypass Oscam. You can easily pull the decoder card out of the device and the FTA channels will continue to work. It doesn't matter if Oscam is there or not. This is because decoding is not necessary for FTA channels.

CAID 0000 is obviously some nonsense. But I don't really know why there is a CAID value of 0000 :).

/// EDIT :

It would help if you show your Oscam configuration files. I guess you have something wrong there. Remember to mask your passwords, IP addresses, or friends' user accounts.

So then in that case, we only need to see the report from the softcam-feed installation, from Linux-Shell (from the terminal). That what is actually going on there :).

Quote from stefen

sorry is there a soft cam compatible with OpenAtv 7.1? i installed the softcam-feed-universal_4.6-r0_all

but it is not in the plugin menu. Or if there is a compatible Cccam 2.3.2. Or are there problems with python 3?

Why do you use test versions of OpenATV 7.0 and 7.1, which are intended ONLY for developers (programmers) and for experienced users ? Experienced users can install any softcam even manually.

If the softcam-feed doesn't work in test (alpha / beta) versions, it's normal, because it's a test version of OpenATV and not the official stable version. If you want a stable latest version, then use OpenATV 6.4. There this softcam-feed extension works.

I already wrote you how to start the Python3 interpreter :).

I don't want to be stupid with you, but if you don't have IT skills, it will be difficult for you.

First, learn to work with IT in general. Then learn the basics of working with a Linux system. Then learn the principles of Enigma2 algorithms. Finally, learn how Python works and what this Python is.

If you have to ask me how to run Python interpreter, it's very bad and you shouldn't do it at all. You skipped the rough foundations of programming knowledge. It's a big mistake. You will find it very difficult until you have knowledge of the basics of Linux systems, the Python language and the Enigma2 GUI in set-top boxes.

The moderators could (please for it) also separate the last few comments and create a new topic, as this is off-topic. This does not apply to SoftCAM-feed installation, but it is a topic about how to work with Python3 in Enigma2.

Quote from stefen

Quote from giopet

Quote from stefen

thanks guys, I already had 6.4 before but the problem is that I would need python 3, 6.4 mounts version 2 of python. is it possible to install version 3 on OpenAtv 6.4? mine is a Vu + SoloSe, so is there openatv 7.0 RC1 image for my Vu +?

Yes it is ,yon can test it,but I don´t now how it work´s on your receiver.Here on all my receiver ATV 7.0(Beta) and 7.1(Alpha) work´s.

openATV Nightly Downloads (mynonpublic.com)

does it work on my Vu SoloSe version 1? that picture is for Vu SoloSe v2 4k thanks

Vu+ Solo SE and Vu+ Solo SE V2 are the same models. There is a small difference only - i.e. double size of the flash memory and also there is added a new DUAL-DVB-tuner support. The Vu+ Solo SE V2 4K does not exist.

This is wrong:

opkg install python 3

I wrote this:

opkg install python3

After installing Python3, you must of course run the Python3 interpreter as the python3 command. The default is still the Python2 in your Enigma2/OpenATV6.4 distribution - i.e. python2 or python (as command).

As I wrote before... use the Linux Shell... for example: opkg update; opkg install python3

In OpenATV Enigma2 distribution is used the opkg - as the Linux package manager.

Quote from stefen

thanks guys, I already had 6.4 before but the problem is that I would need python 3, 6.4 mounts version 2 of python. is it possible to install version 3 on OpenAtv 6.4? mine is a Vu + SoloSe, so is there openatv 7.0 RC1 image for my Vu +?

opkg update
opkg install python3

Of course this is possible, but you probably need Python3 as tree inside the Enigma2 core. Not as a stand-alone Python3 interpreter. So installing Python3 will probably not be enough for you.

Enigma2 OpenATV 6.4 is being developed in Python2 ... and not in Python3. But you can install the Python3 interpreter... as I mentioned above.

If you need an Enigma2 distribution, that is being developed in Python3, then use the OpenATV 7.0 (as test version / non-stable yet). But if you need Python3 for your own experiments only, i.e. outside of the Enigma2 source code structure, then it will work.

Quote from stefen

sorry, i have a problem with softcam on OpenAtv 6.5. when I install the plugin, there are only Oscam inside and there is no ccam 2.3.2, while the same softcam-feed-universal_4.6-r0_all installed on OpenAtv 6.4 about 6 months ago I find all the cccam, what's wrong?

If you want, you can use the manual Cccam installation procedure (using a binary file, without the IPK installation package).

You can use the simple instructions directly in my "init.d" script (located at the beginning of the file):

e2scripts/softcam at master · s3n0/e2scripts

some helpful scripts (Python or Shell) for Enigma2 - e2scripts/softcam at master · s3n0/e2scripts

github.com

Or... also, for example... you can use the following procedure:

Article

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

OMG ... don't use IPK packages. Don't be lazy to learn something. Use the manual installation method to install SoftCams like OSCam or CCcam.

s3n0

May 1st 2019

And what about older versions of Cccam ? They don't work either ?

/// EDIT :

Try the Cccam version from the OpenPLi feed (I am attaching a binary from the IPK package to the attachment)... although it is designed for Cortex A15, so I don't know if this version will be able to work in compatibility mode. However, it includes support for the VFPv4 processor instruction set (as well as your new chipset).

Alternatively, try some pretty old versions of Cccam softcam for old ARM v7 processors. Of course, if you can find something old, like that, on the internet. Unfortunately, there is closed source code, so it's really a problem.

Hi.

That Oscam LOG should have been copied with the help of a mouse (mark whole text with mouse cursor ... and copied with the CTRL + C keyboard shortcut) and then pasted (keyboard shortcut CTRL + V) into the CODE TAG or QUOTE TAG here in discussion.

According to the LOG (screenshot) you can see that you have the wrong CAID. Don't set any if you don't know which one to set. Oscam will then try to use all detected CAIDs on your card.

So simply delete caid = 0100. You will also probably need to set up and enable AutoUpdate (AU), which is the ability to send EMM control packets (commands) to your card. These EMM packets are currently writing and setting "entitlements" on your decoding card.

Oscam to use the so-called dvbapi interface, for sending EMMs to an internal reader. To enable the AU function, you need the correct settings in the "oscam.user" and "oscam.conf" files. If you want, I am attaching the basic universal configuration for internal readers - for Oscam, even with the AU function enabled.

I also don't understand what kind of build this Oscam_Simple_by_ATARI it is. Is that special ? Why do you need this special version ? If it is a private, specially modified version, then unfortunately on this discussion forum, support is only allowed for mainstream Oscam build versions. Not for modified third party versions.

I probably won't make it with this... I don't want to look for it on the internet... I don't know your firmware... sorry.

This is another question from you - configuring the CRON service. This, in turn, is a long story.

First of all, CRON can be used in various Linux systems in various ways, even with a slightly different version. Somewhere it's "crond", somewhere "crontab" and somewhere it's just "cron". Of course, after each editing of the CRON configuration file, you must restart the CRON service. I don't know what CRON your Linux system is using, so I don't know where and how to edit the files and I also don't know how to restart CRON in your case. It's different everywhere.

The surest way is to configure via the CRON service tool and then restart the entire set-top box:

crontab -e

After saving the changes, just restart the system:

reboot

Depending on your Enigma2 distribution, a Nano or Vi text editor may be used. The default text editor can be changed (if installed), but I don't know exactly where.

Unfortunately, Vi is an ancient and only easy-to-use editor via the console / terminal (keyboard keys). Unfortunately, this Vi editor does not have very comprehensive support for using cursor keys, backspace, text highlighting, etc. as in modern text editors. It is possible, but complicated. I think Nano is a more human editor.

Or try to google yourself how to properly restart and configure your CRON, on your Linux system (in your Enigma2 distribution). In some Enigma2 distributions, it is possible to install and configure CRON even directly through the GUI (via SKIN) with the help of RCU.

You'd better add what I wrote above to the CRON service :).

If there is an compatibility issue with Oscam vs Linux, then after the update it may have occurred. Then it is necessary to use another binary file. You probably don't know much about it, but there are a lot of oscam binary file dependencies on system libraries. Sometimes a small change is made in Linux and the binary file stops working correctly.

Of course, Oscam compatibility with Linux doesn't have to be a problem. It can be in something else.

For example, a provider will change the way its own encoding system works... and then problems need to be addressed. This happens quite often when providers always change something. Certified set-top boxes are not affected, but Linux set-top boxes are, because they are designed to be universal (universal in general, not just a card reader in Linux set-top boxes called "universal").

These problems are solved by making up a new discussion thread with the name of your provider and its CAID + of your used Enigma2 distribution ... with asking for advice.

If you look at the system logs, I mean debugging the system or even the Enigma2 process ... then you may find an error ... propably :). Oscam can be shot down for other reasons and not just for the possible causes mentioned above. You should look for the cause. Don't try to auto-restart Oscam when it falls.

You have to be able to adjust the command-line as yourself.

For example, as I stated in post number #23: RE: Oscam telnet command for stopping

Maybe it will work for you. Since you can't do it otherwise and since it doesn't work correctly, using it with a CRON scheduler could be a good and easy solution for you. However, in some Enigma2 distributions, CRON must be installed from the feed server because it is not preinstalled by default.

/// EDIT :

However, Oscam freezing is a problem of the binary file itself and should NOT be solved by restarting, but by identifying the cause and eliminating it.

For example, this may be a Linux compatibility issue if the Oscam binary is not designed and compiled specifically for your firmware. Then you should try another binary file, also designed for your firmware (you can find the Oscam binary according to the chipset specification - arm / mipsel / aarch64 / sh4).

If so, then back up your current oscam binary file - for example, by renaming the file "oscam_11704" to "oscam_11704_bckup". As next step, you upload a new oscam binary there and rename it to "oscam_11704". Then assign the executable attributes of this new file (as I mentioned above).

OS 2.5 only means that you are using newer firmware in a set-top box that uses more advanced Linux and the newer Enigma2 core. It doesn't mean anything more. Everything (every Oscam) must always work there, and of course, if all compatibility is maintained (system libraries + Linux kernel).

Maybe you should try another Oscam... but if you use a pirate Oscam... then tribute pitch. There is probably a problem when it freezes or falls in your Oscam.

The above procedure with CRON, in conjunction with the manual installation of Oscam, must work on every each Linux system. The problem, as I wrote, can only be in your Oscam (compatibility issues). But you already own a oscam binary file, so there should be no problem.

Or you can keep the file name as it is... and leave the IPK package or updater on your system. Simply install (if not yet installed) the CRON service on your system. Then use what I sent you - i.e. see the link to my next post on using CRON, for restarting Oscam. There, of course, you have to edit the file name and possibly the directory to the one you use (oscam_XXXXX). There are several ways to auto-restart Oscam if the service is no longer running.

/// EDIT :

Especially for you... one example... for CRON (user config):

* * * * *        if ! pidof oscam_11704 > /dev/null; then systemctl restart oscam_11704; fi

The CRON service uses the pidof command every minute, to test whether the Oscam service is running. If it is not running, it will be restarted, using the systemctl.

Hi.

What do you want to accomplish with your Oscam ? I still don't understand you exactly. You wrote before that you wanted to "test" and "restart" the Oscam service. If you mean testing, just freezing or falling Oscam, this can be solved in many ways.

This is addressed very often here. Just browse this discussion forum. Of course, it also depends on what exactly you want to test. If Oscam falls, it's easy. But if you want to test, for example, the loss of the Entitlements in Oscam, and then restarting Oscam, then it's more complicated.

Personally, I recommend removing the IPK package with Softcam completely. Then you install (just copy) the oscam binary file to the appropriate folder in your set-top box. I recommend renaming this stupid filename "oscam_XXXXX" to a simple "oscam" and continue to use only this simple filename. You then assign the execution right, i.e. the attributes of the file, for example via the Shell:

chmod a+x /usr/bin/oscam

or by setting the file attributes via FTP client to the value:

755

Finally, you will use the CRON scheduler on your linux system (in the set-top box). If the CRON is not installed, install it. Here are examples of testing the running Oscam process + auto-restarting, via the CRON: RE: Oscam restart script

Try adding this as well (under the "Service" configuration section):

[Service]
Restart=always
RestartSec=5
StartLimitInterval=0

Although I'm not sure if this will be recognized by your Lilnux, used in your set-top box. I hope so.

You should not have created this new file there. It probably already exists there. Or have you already looked for him and not found him? You should have used one that already exists there (of course only if you find it there).

You're wrong again. You attacked me as the first.

It was your "hate" speech, basically something like: "I won't read your 5 sentences because it's a very long read for me".

Put these cheeky and hateful expressions behind your hat.

As you continue to insist on the hate, I welcome you in the ignore list.

Quote from teak-won-do

I can read, sorry I'm not interested in your long statements

Long statements ? Really ? You mean these 5 sentences ? :)

You are probably not a programmer or an IT technician :). I'm right ? :) If the 5 sentences are very complicated for you, then you should not focus on IT at all.

Quote from teak-won-do

i already wrote in #post4 you find all oscam in OpenATV Softcamfeed

Quote from teak-won-do

i think Mutant 51 is arm receiver

He doesn't need to know this information.

When installing the softcam feed for OpenATV, the installation script automatically selects the appropriate chipset architecture and installs the new feed source that currently belongs to the specific chipset.

The installation script also determines the correct version of the Enigma2 core (based on the OE Alliance) and installs the feed-source that belongs to the installed Enigma2 core (in a specific OpenATV).

The interviewer asked something else in his post number #5. He asked about some ".rar" file there, which of course is nonsense. It's completely off topic. Therefore, I replied that no ".rar" was needed and I wrote a usage procedure (of course, after successfully installing a new feed source in the Enigma2 OpenATV).