4.0.210427
Fixed a minor bug in the list of picons loaded from local disk:
- the list of file names on the local disk was created incorrectly, including SRN file names
- the plugin only works with SRC file names, so deleting "unnecessary" SRN file names is undesirable
- the plugin from this version or later will completely ignore files named as SRN
- thx to manuel06
Hi.
You mean to add a new reader ? And what about other configuration items, of which there are several ?! Didn't you get it wrong with de/activating a specific reader ?
It would be better to edit the "oscam.server" file via the shell, by adding or removing the whole cfg-passage for the reader and then restarting Oscam.
Hi.
You are asking incorrectly. Oscam is also a client (you connect to an external or your own card reader) and also acts as a server (ECM sharing).
"oscam.server" = here you set up a connection to your internal reader (dvbapi internal oscam-user) or to some external reader (Oscam as a client)
"oscam.conf" = here you set running Oscam server services (for ECM sharing) on a various protocols (cccam, newcamd, cs357x, ...)
"oscam.user" = in this file you will set the internal oscam-user dvbapi or here you will add user accounts that will apply to the created Oscam servers (for cccam, newcamd, etc. that you have set in "oscam.conf")
Note:
If you want to connect with your Oscam to yourself, that is, connection to itself, to the internal card reader, then it is also necessary to use the dvbapi module - so it is necessary to configure a local dvbapi user - in the files "oscam.user" and "oscam.conf".
More info about Oscam configuration files can be found here:
Hello.
They are all standard Oscam (open source code), extended by some type of module.
For example, the "Emu" module added to Oscam serves as an emulator of the reader and the decoder card in this reader (several types of encryption / satellite providers), for example based on some available encryption keys. The source code of the Emu module extension is available on github - freely available:
There you will also find a description of the different types of configurations for which this Emu module is intended:
https://github.com/oscam-emu/o…i/OSCam-Emu-configuration
Unfortunately, I don't know the other two modes "supcam" and "revcam" :). They are apparently unknown and unpopular. I don't know what the other two modes are for.
Hi.
What exactly doesn't work ?
Where is any output from the console ?
How exactly does the error of image flashing manifest itself ?
Why didn't you rather ask this on the OpenATV discussion forum ?
:)
What is the rescue loader: http://wiki.blue-panel.com/index.php/Rescue_Loader_(en)
How to boot in rescue mode:
How to flash using the Web-GUI:
It would be appropriate to create new binaries there. Backward compatibility with old versions of the system libraries (for example libcrypto, libssl, libusb, ...) usually doesn't work. However, in some specific cases, as I have already written, depending on the chipset in the set-top box (i.e. hardware dependent) and also depending on the Enigma distribution itself, even if the binary works, small problems may arise.
For example, specifically under mipsel processors, on the Linux kernel version 3.13 - the CCcam 2.3.2 softcam can freeze through new system libraries, while the CCcam 2.3.0 softcam works fine also in the new system libraries.
Linux systems are really great, but they require a lot of expert users and developers, unfortunately. Linux is not like Windows ... where you see 5 icons that you can click on and then the default task is performed (figuratively speaking). Linux is a universal solution ... but universal solutions also require people's hyper-intelligence :). And that's the stumbling block :).
So if you bought a new set-top box, it is quite possible that it is a coincidence that you hit the right version of the chipset, the appropriate distribution of Enigma, good softcam, DVB system coding of your provider, where everything is compatible and functional together.
///// EDIT :
Unfortunately, Oscam is similar in its versatility. Although it works always and everywhere, there are minor discrepancies, in various chipsets, libraries, DVB systems, etc..
Let me come up with a small example for understanding:
For the CONAX DVB-encoding system, OSCam will use a decoding algorithm via the libcrypto system library. However, the libcrypto system library in version 1.0.2 does some algorithms a little differently than in version 1.0.0. Oscam therefore needs a patch to be able to process the output, in an algorithm from the libcrypto 1.0.2 library, as it did in version 1.0.0.
(This is just a fictional example. Don't take it seriously. It's just for better understanding !)
Unfortunately, no developer will do this patch in the near future because no softcam developer uses CONAX decoding. We could still associate the problem only with the case where OSCam is used only as a client, not as a server. This complex problem will not be solved until many years later, when finally some softcam developer encounters this problem at home and fixes it. Unfortunately, this is the fate of the universal OSCam.
Hi.
I don't know what the "7325" number OR the "se" string represents ... or where it gets it from. Maybe it's some chipset shortcut, obtained from the system and used as a subdirectory name ?
I can't see and can't find the "burn.bat" or "burn.sh" script anywhere. Or is it just your own script to use the "flash" command ?
BTW, the ".bat" extension is probably your typo ? It belongs under Windows systems as a Batch script. The ".sh" extension is used for Linux shell scripts. Or without an file extension, but then Shebang / Sha-bang must be in the first line at the beginning of the file.
That won't help us, but thanks. It works as a plugin, written in Python code, for Enigma. However, during the backup, shell scripts are used, which are usually run only after Enigma is stopped. Basically, the firmware backup is performed by the appropriate selected shell script (according to the type of set-top box and its flash memory).
I would rather be interested in how this problem was solved. :)
I don't know where the cause of the problems was... but maybe the script was called in the wrong shell interpreter. After updating to the PLi plugin, the correct interpreter is already used. Maybe... :). I dont know.
After all, OpenPLi includes its own Backup Suite plugin. I don't know if it's even built into the OpenPLi image directly. If not, install it from the OpenPLi feed:
opkg update
opkg list | grep -i 'backupsuite'
# ....
# .... here you will see available packages, filtered to the text 'backupsuite' ....
# ....
opkg install <package_name> # note: do not use the IPK file name, but the package nameOr try moving the line #!/bin/sh to the beginning of the script and then try running the backup again... but I don't know if this will help:
sed -i '/\#\!\/bin\/sh/d' /usr/bin/backupsuite.sh
sed -i '1i \#\!\/bin\/sh' /usr/bin/backupsuite.shHi,
But where is the problematic ".sh" script? Please insert it as an attachment to the discussion (zip if it is not possible to send the .sh file extension).
Which backup suite do you use? Each device and each Enigma2 needs slightly different procedures. For example, you may be trying to use BasckupSuite where a Bash shell still did not exist, but only a redirection by a symbolic system link from Bash -> to Sh / Ash or other mini-shells. Bash is used almost everywhere in the new Enigma2 distributions. But this was not the case in older versions. So if you use the old Enigma, it is possible that there is a missing Bash shell. For example, Ash is used instead of Bash. Then, when a programmer writes a shell script for Bash (that is, does not use POSIX compatibility for all shells), logically, these problems arise. The most famous and hated so-called "bashism" in shell scripts are quotes and square brackets :).
So depending on which BackupSuite you are using, for example:
OpenPLi - https://github.com/persianpros/BackupSuite-PLi
OpenVisionE2 - https://github.com/OpenVisionE2/BackupSuite
...and depending on which device, these problems can be different. You should report this BUG to the author of the source code (on Github), depending on which BackupSuite you are using.
Hi.
First you need to install OscamEmu (or replace the binary file if you know how to do it), which already has the "Emu" module built into it. You can find this, for example, in "OscamWebif > Files > oscam.version" or in Shell: /usr/bin/oscam --build-info.
So you can't have a classic Oscam, but you have to have an OscamEmu.
For Raspberry-Pi you can try the following guide:
https://github.com/oscam-emu/o…d/wiki/Building-OSCam-Emu
Or the discussion thread:
Display MoreDisplay MoreSend ipk file via FTP (via DCC or FileZilla) to tmp> / var / temp
after over telnet:
opkg install /tmp/*.ipk
reboot
Ok big thank but feed has the last oscam 11689 ?
Thank
Hispa
Yes, the softcam-feed for OpenATV image usually has the latest version of Oscam.
Try studying an older topic, specially designed for SKY DE:
(also browse a few pages from the back, towards newer pages)
Maybe you'll find your problem somewhere. Unfortunately, I don't have time :). And I don't know the SKY DE configuration for Oscam well.
Hi,
you have a lot of errors there, for example:
oscam.server CLIENT.txt
- the "services" configuration item is not used to enter a specific ServiceID, but the name of the entire field, which you fill in the "oscam.services" file
- in addition, you used CAID values there, not a SID values.... maybe you were wrong and instead of "caid = 0500,..." you wrote "services = 0500,..."
- more info, here: https://wiki.streamboard.tv/wi…fig/oscam.server#services
oscam.user CLIENT.txt
- the "keepalive" item in the case of a dvbapi user should not be, because firstly, this item is already active by default (keepalive = 1) and secondly it is used mainly for newcamd connections, not for connections between internal algorithms of the same Oscam
- info, here: https://wiki.streamboard.tv/wi…nfig/oscam.user#keepalive
I recommend not using the LB scale (lb_mode, lb_save, etc.) until everything is working as it should.
What does LOG (for example, LiveLOG in OscamWebif) show as a reason for server "freezing" ?
Hi.
Yes it's true. The problem can be caused by the processing of softcam-protocols, which is unfortunately non-standard in the case of Oscam - it is not original, so it does not affect the original softcams, according to the authors. In Oscam open code, someone is constantly fixing bugs. Often people who have no idea about coding systems. Also, each DVB provider can use slightly different methods in their own firmware, on their own decoder card. Then nothing works as it should.
If that doesn't help (using the cccam softcam-protocol), try using the communication softcam protocol, which is less well known but reliable - cs378x or cs357x (https://wiki.streamboard.tv/wi…fig/oscam.server#protocol).
I have a similar problem in CCCAM protocol communication. I have to use CCcam as a softcam-client, not OSCam as a softcam-client. I am using the CCcam 2.3.0 softcam-client for the mipsel chipset, which only works in an OpenATV image, without any problems. Other versions of CCcam softcam freeze, crash, do not work properly, etc. . This is IRDETO encoding card.
Oscam is probably only suitable as a server, not as a client.
The longer I use Oscam, the more I hate it. I've been using Oscam for about 4 years ... testing ... changing versions ... setting up a large number of different configurations on different types of DVB systems. But I still like Oscam softcam less and less.
So if your set-top box contains a mips(32)el chipset, then try to use Cccam-2.3.0 softcam as a client. Maybe it will help.
I really don't know why your Oscam will destroy the ECM format (readability).
Maybe you just misconfigured some items in the Oscam configuration related to ECM. Some settings may require, for example, an "ecmwhitelist" configuration item (but I don't know which one).
I don't know your DVB encoding, so I can't advise you anymore.
Hi.
Did you not test the Cccam protocol instead of Newcamd protocol (server+client) ? Just to test if it helps.
ddinc :
Both the "oscam.config" and "oscam.user" files do not match the local (internal) user name.
Or there is probably no dvbapi user at all in the "oscam.user" file ? Dream2 user supposed to be an external client and therefore not a dvbapi local user ?
In this case, also add the dvbapi user to the "oscam.user" file:
[account]
user = dvbapi
pwd =
au = 1
group = 1
[account]
user = Dream2
pwd = xxxxxxxxxx
group = 1You also didn't know which device your configuration files came from. Are all the configuration files from you coming from the Oscam softcam client ? Or are these files belonging to softcam-server Oscam ?
You could also create a debug-log in OpenPLi and attach it here (via the Shell: init 4; sleep 5; ENIGMA_DEBUG_LVL=4 enigma2 > /tmp/e2.log 2>&1). I wonder what will appear if you switch to an IPTV channel. Switch to the IPTV channel, then wait for 10 seconds and then send the generated "/tmp/e2.log" file in a private message (your personal data will probably be there, so don't post it publicly in discussions).
I don't know if this will help, but try adding a DESCRIPTION line as well as a slash at the end of the URL:
#SERVICE 5002:0:1:029A:00C3:0:0:0:0:0:http%3a//xxxxxxxxxxx%3a23361/live/vvvvvvvv/uuuuuuu/195.ts/:Sport AD Sports1
#DESCRIPTION Sport AD Sports1Try also the service No. 5001 - i.e. Gstplayer, instead of service 5002 (i.e. ExtEplayer3).
However, the solution to the problem might be known on the OpenPLi discussion forum (https://forums.openpli.org/), where there are users and moderators who have been using OpenPLi for a long time and know it very well. Check also the search option on the OpenPLi forum (match the word "ServiceApp").
By the way, it's probably just a typo, but you meant service number 4097 instead of 4007. Right ?
Show what your userbouquet file looks like for IPTV - just one example / line of IPTV will suffice. Is the service number written in the userbouquet file, correct ?
