Posts by s3n0

Do not contain at feed server ? Um, it is possible because the DM800 HD device has a very little flash memory. So even the feed server or OpenPLi-7.2 image for this device will not include ServiceApp. Powerful hardware is also required, which unfortunately the old DM800 HD is not. ServiceApp uses ffmpeg and ExtEplayer3, which require some better hardware. Rather, this will be why they were not included in the OpenPLi 7.2 feed for your DM800HD.

You need to use an flash expander that extends the flash memory to the USB stick. This is not reliable, but at least the plug-in folder should be transferable to a USB stick. There is a symbolic-link, referring to the USB stick empty directory. Of course, the USB stick must contain the Linux file-system (ext2, ext3 or ext4).

If you would like to play with it, here you have current download links:

(WARNING ! URL-links will only work until the next update is released - i.e. just a few days.)

[1] http://downloads.openpli.org/f…g_3.4.2-r0.2_mips32el.ipk

[2] http://downloads.openpli.org/f…52666ca-r0.2_mips32el.ipk

[3] http://downloads.openpli.org/f…02956ea-r0.5_vusolose.ipk

Install these packages in the same sequence.

Again, note that you should use a flash expander and do not guarantee proper functionality, as the DM800 HD hardware is weak and old (300MHz mipsel CPU).

/////// EDIT :

Unfortunately, I found out that ServiceApp installation package also contains a binary file. It will probably not work on another chipset (a different decoder found in your set top box). This binary file will probably be bound not only to the processor type I thought (mipsel) but will also be bound to the chipset type (decoder type).

He asked how to download from the Internet, right ?

:-P

He did not ask how to install it.

- via Shell / command-line:

opkg update
opkg list | grep serviceapp
cd /tmp
opkg download <package_name>      # i.e. found package name from the list (above):  enigma2-plugin-systemplugins-serviceapp
ls /tmp/*.ipk

2.0.200221

Added Turkish language.

Quote from maybin

I have issues with making cccam operation on my sf8008. The image installed is OPENVIX. Assist me with the tutorial on how to cfg cccam on my box.

First you have to write exactly what you want to know. What exactly you have a problem with. Can't connect to the softcam server? Do you want to create your softcam server? What is displayed in the CccamWebif LOG records (Web-GUI that you open through any web browser).

Quote from kokoko

Per favore qualcuno che ha ; extra url per OpenATV 6.3

Non riesco installare emulatore perché manca la cartella di extra.

If you don't know English, use Google Translator (https://translate.google.com).

You can also use the Italian class discussion, with fewer users active: Italian

I didn't quite understand your question. Where is the problem ? Can't find the right directory for Cccam configuration files ? Usually there is default folder as "/etc/keys/CCcam.cfg", but can be changed for some Cccam installations - e.g. "/etc/CCcam.cfg" or "/var/etc/CCcam.cfg". You can also find the right path to configuration files in the Web-GUI, which you can open in any web browser (http://IP_address_of_your_set-top-box:16001).

Check out the latest version of Oscam 11572, for mipsel architecture.

Mipsel is also in your old DM800 HD -> https://en.wikipedia.org/wiki/Dreambox#Table

However, I don't know if it will run on the old OpenPLi 2.1 and the old Linux kernel.

First try the IPK package for the new OpenPLi 7.2, for mipsel architecture. If it doesn't help, just try download a individual binary file (for mipsel architecture), upload it to the /usr/bin folder, then assign the attributes chmod a+x /usr/bin/oscam and then try to run the binary as /usr/bin/oscam --help. If the oscam binary file works... also add there some "init.d" startup script. Procedure for init.d script can be found here: Tutorial : How to install softcam (OSCam/CCCam) manually, if you hate ipk packages

OK, so if you have "entitlements" already registered, then OK. Then you don't have to change the "audisabled" conf. item. I don't know your provider or your card encoding.

Sorry :-)

Unfortunately, I do not know the TNT provider, so I can not even in this case quite accurately advise.

However, AU stands for Auto Update. This is to allow EMM packets to pass through to your decode card. EMMs are management packets. For example, the EMM sets up prepaid packages that your decode card has subscribed to (according to its serial number) and also refreshes the subscription timeout period (entities). So if you turn off the EMM / AU, then your card will be dead. Rather, AU disabled is not to send the EMM unnecessarily to a softcam server remote somewhere on the Internet when the EMM has already been taken care of by the owner of the softcam server.

Here you can read more about it (I mentioned it above):

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

AU disabled ? Why ?

Why exactly do you want to buy Vu+ device ? There are many good and cheap Linux set top boxes that include 2x DVB-S2 tuner + 2x UNI reader + 1x CIplus interface for sure too (for CAM modul).

But it doesn't matter. Try it also on a USB card reader. If you do not have functional so-called "entitlements", then AU (Auto Update) is set incorrectly and therefore no EMMs for your decode card are passing.

As I wrote, it is easier to run the card in an internal UNI reader built into the set top box. Fewer problems arise in configuring EMM packets / AU refreshments than with external USB readers.

First start one and then the other. Do not try both cards at the same time.

Oscam configuration, have you lost from the previous set top box ?

Sorry, but this is stupid if it doesn't work. It must work if you replace the set top box and use the same Oscam configuration.

Do you have backed up the original Oscam configuration from the old and dead Vu + set top box? If so, use it and it must work! It doesn't matter which device.

Usually, the built-in internal readers in the set top box are more reliable than external USB readers. These external USB readers are quite difficult to configure (as you can see yourself). An internal reader to set up is easier and faster. Even so-called entities are less problematic in the case of a built-in internal reader - the AU (AutoUpdate) settings or the throughput of the EMMs to the decoder card with the help of a "dvbapi" user is easier to set up. Of course, only if the type of card encoding is supported by UNI-readers, since there are also paired decoder cards that require a CAM CAM paired with the card, and then do not work software (in a UNI-reader, via Softcam).

Sorry. I cannot advise you on the entitlements (prepaid packages from the provider). This is directly dependent on the encoding type or encoding system used by your provider on the decoding card. Each provider needs different Oscam configuration settings - sending EMM packets to the decoder card must be properly configured and also enabled. Some coding systems cannot decode the ECM unless the algorithm is awakened by an EMM packet.

Unfortunately I am not an expert on DVB technology or an expert in card coding, so I cannot advise you on this. For example, my provider uses the IRDETO card coding system, and every time a decryption card is reset (restarted), the entititlements are lost. Control EMM packets for card refreshment are therefore required. About 10-20 seconds after the softcam restarts (the decryption card restarts), EMMs are received from a satellite stream and sent to the card. Only then the ECM packet decoding (channel decoding) will start to work once the card has already actively paid packages (entititlements).

Try the following config:

[reader]
label               = my_smargo_1
protocol            = mouse
device              = /dev/ttyUSB0
mhz                 = 600
cardmhz             = 600

Your USB card reader is identified as the USB device 0403:6001 ( https://usb-ids.gowdy.us/read/UD/0403/6001 ), i.e. bus 001 and device 009, so, you can to try also the following config:

[reader]
label               = my_smargo_2
protocol            = smartreader
device              = 001:009
aeskey              = 0102030405060708090a0b0c0d0e0f10
mhz                 = 600
cardmhz             = 600

You can't invent or copy your own devices. You must use one that is identified or assigned on your system under your firmware. It should be detectable by: "Oscam Webif" -> "Readers" -> "Scan USB". It's actually the same as the Shell command lsusb.

There you will find a suitable name to write to oscam.server under "device =".

You can also try disconnecting and reconnecting your external USB card reader and then use this command in Shell:

dmesg | grep -E "serial|Serial|USB"

...to identify the correct name for your device.

Which card reader is yours? Model, brand, type, photo ... ?

You don't need to know any super knowledge. Just download the attached file "plugin.py", upload it using FTP connection to the above folder. Then restart the set top box to compress the code to the Python interpreter code (to a .pyo file). After restarting, delete this "plugin.py" source code file (also via FTP connection). Deleting this .py file is required to update your Enigma. If the .pyo file from the BackupSuite plugin were updated at the same time with the Enigma, it would be overwritten with the compressed source code of the .py file after restarting the set top box - again and again. So updating the BackupSuite plugin would be useless in this case.

Uhm, your Smargo reader also doesn't work in "smartreader" mode ?

http://www.streamboard.tv/wiki…der#Smargo_Smartreader.2B

Oscam compilation contains a smartreader module:

cardreader_smartreader: yes

I've tested the above python code modification (plugin.py - BackupSuite) in OpenATV and it works. The plugin does not report any errors. It was launched in OpenATV exactly as it was in OpenPLi.

Hi.

How do you use (start and stop) Oscam ?

Do you use "/etc/init.d/softcam" script ? Or did you install your Oscam with a .deb package and then start / stop via the GUI MENU (that is, through the Python code - under Enigma2 - for example under Softcam Panel) ?

Maybe Merlin has the same problem as with the newer OpenATV:

The Softcam startup method in OpenATV is performed by immediate stopping and then immediate starting - without a wait loop. The init.d script is called with the "stop" argument and immediately without waiting again with the "start" argument. However, some "init.d" softcam scripts have a problem with this.

Simply put - the script code fails to make the required stop / start Oscam in time. As a result of the unfinished first softcam "init.d" running script with the "start" argument, a copy of the script and this second script are called immediately, the first script still being executed and the second just running. The first run of the script with the "stop" argument will stop after the second init.d script with the "start" argument has been run and the first script will stop Softcam again. This is a complicated problem with some "init.d" Oscam scripts.

So first, I recommend trying to run your Oscam manually - in Shell / command-line. If Oscam starts up, test if OscamWebif is active and working. If it works, the problem is probably with the Oscam launch. It depends on which method of starting the process (daemon) is used for your Oscam.

Or you could also show LOG about the reader error (you can find it in OscamWebif> LiveLog after restarting Oscam and thus initializing the cards).

This is a question for the developers of a particular CCCam or the OpenATV developers (but it is forbidden to discuss Softcam in the OpenATV forum). The error will probably be in incompatible libraries or differently functioning libraries. In OpenATV 6.4, you may want to use new Linux libraries and modules. It is necessary to find out which dependencies on libraries are in case of CCCam. Then check whether these libraries have been updated to newer in OpenATV 6.4.