Quote from Alienato

I've never had problems with this string and it has always downnloaded me the right and last version of the softcam feed that i usually install on a clean image...

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

Yes, the guy tried to add a base URL (with empty source), using the GUI MENU in OpenATV - as a new feed package source. But that won't work. Only if a specific URL was added with components that exactly specify the OE version (if needed some version) and also that exactly specify the chipset / architecture.

the real mojo

You probably just used the wrong URL (via the GUI MENU - in OpenATV).

Adding a simple URL (http://updates.mynonpublic.com/oea/feed) probably won't be enough... I mean adding such a shortened URL and nothing more.

I don't know for sure... but I think that there is another folder to be added to the URL - according to the OE version (enigma2 core in OpenATV) and according to the chipset/architecture of the set-top box.

Anyway... the online shell-script performs more steps in its algorithm. It automatically detects the required enigma2 core version and also detects the chipset/architecture. Based on this information, the shell-script then creates and adds the appropriate feed source to the OPKG manager in your set-top box.

Hi the real mojo .

As giopet wrote... please explain what exactly this statement of yours means, because I don't understand:

Quote

Software update gets stuck on this link

You could also add a screenshot of the error you see. Or... at least a copy from the terminal... for example, in PUTTY (opened terminal window): mark the text with the mouse, then when the text is marked, go to the web browser, to the discussion, and use the CTRL+V keyboard shortcut to insert the text. Then... mark the inserted text in the discussion forum and enclose it in CODE TAGs.

Take a look and try to run the online shell-script for installing new softcam feed, using the debug / verbose argument:

Post

RE: OpenATV SoftCam Feed Discussion Thread

Hi.

In my opinion it is best to use the original online installer - intended for OpenATV. What is IPK good for ? That is useless.

Here is the online installer (shell script), which is also included in the IPKs:
wget -qO- --no-check-certificate "http://updates.mynonpublic.com/oea/feed" | bash

Or using it, with debugging to a temporary file (for diagnosing possible problems and errors during installation):
wget -qO- --no-check-certificate "http://updates.mynonpublic.com/oea/feed" | bash -xv >…

s3n0

Oct 21st 2022

Hi.

Exactly so. Just separate them with an empty line for better clarity. It is simple.

You have just to create 8 these readers in the "oscam.server" file. OSCam alone, then selects automatically from the available readers, depending on which one has which CAID provider and available services. OSCam should handle it himself.

However, it will help if you know the CAID for individual readers and add a line to specify the CAID everywhere ( https://wiki.streamboard.tv/wi…/Config/oscam.server#caid ). But it is not necessary.

Also, don't forget to create an internal dvbapi user for local access if you use this OSCam of yours as a softcam-client and at the same time as a softcam+server for your own set-top box.

It looks like someone tried to connect from several IP addresses. Either it is a dynamic IP address or it tries to attack from several hosts on the internet.

You can find out the DNS name of each IP address, for example like this command: nslookup 192.168.1.1 . If they are always the same DNS name... then you can to block this DNS name.

For now, try to create at least a regular account called anonymous in "oscam.user" and set a very strong password of at least 15-20 characters, also with various special characters (underscore, dash, wrapper, ... ) + with some numbers + with a different letter size.

If the same IPs are always repeated, then disable them on the firewalls of the router or Linux set top box or, as written above, it can also be disabled in Oscam by IP.

---------------------------------------

The "anonymous" account also shows up with various Oscam errors. Unfortunately, I don't remember exactly which errors. In the case of bugs such as poorly set cascading or reshare. When more than one account is connected at the same time and you have only allowed 1 account (in "oscam.user" file)... the attempt may be reported as a disconnected "anonymous" account. But I really don't know exactly... when this "anonymous" appears with which Oscam bugs.

---------------------------------------

In Linux (in a set-top box) you can also disable groups of IP addresses... you can already find it in Google... but be careful... for example:

Block range of IP Addresses

I am getting bombarded with attempted hacks from China all with similar IPs. How would I block the IP range with something like 116.10.191.* etc. I am…

serverfault.com

You can try the older version from OpenPLi-7, which is a bit different. Strange because CCcam is closed code. I don't know where the OpenPLi team got this version of CCcam from. The difference is in the letter "a" in the version. The older version of CCcam softcam from OpenPLi-7 does not contain this letter "a". See Attachment.

If it doesn't work well, feel free to try OSCam as well - I mean as a softcam client, instead of CCcam. OSCam is reliable in most cases, but with a few exceptions, it causes communication problems (paradoxically, between the same versions of OSCam !). Maybe it will work fine in your case.

However, you have uClan Ustym 4K: Hisilicon Hi3798MV200 chipset / ARM Cortex A53 processor. So... I don't know. It depends on which version of Enigma2 you are using. The Cortex A53 processor is a bit more complex. It can run in ARM-7 backward compatibility mode as AArch32 mode. However, it can also run in full AArch64 / ARM-8 mode. I assume that OpenPLi-8 runs in the old compatible mode. Try to find out, for example, with the command in the linux terminal:

uname -a

...or try the info from the listing:

cat /proc/cpuinfo

Quote from real73

Thanks! now need CCcam 3.2.0---

You probably wanted to write 2.3.0 and not 3.2.0.

First, find out what chipset / CPU architecture you have in the set-top box :-).

Then download the appropriate CCcam 2.3.0 accordingly.

I think that even here on this forum, there should be binaries or installation packages. Binary is probably better + solve auto-start + add one configuration file ("/etc/CCcam.cfg").

CCcams in attachments come from OpenPLi-8 feed. They are all IPK installation packages.

Unfortunately for the ARM architecture you will not find v2.3.0 but only v2.3.2. I have not verified how v2.3.2 works, but I believe that it works well. Version 2.3.0 exists probably only for the MIPS architecture.

Hi.

Try the CCcam 2.3.0 softcam version... or... as a colleague wrote earlier... try CCcam, which is available on the OpenPLi feed. The OpenPLi team also has softcams on its feed servers (directly).

On the other hand, it is also a fact that CCcam does not have an open source code ! The code is "secret". Unfortunately, it is not published on any Github or other portals. It is hard-compiled, so no CCcam should differ much from another build (OpenPLi vs OpenATV vs others) - they should all be identical. But it is possible that someone made CCcam 2.3.2 with some dependencies a long time ago. And these binaries for CCcam 2.3.2 are distributed differently among users. Well... and OpenPLi maybe uses the "appropriate" file that will work correctly in their own OpenPLi.

If nothing helps, try the softcam version CCcam 2.3.0. This version, for me personally, always worked everywhere. All the others, I don't know why, older and newer, always have some minor problems over time.

Hi.

BTW, even though this topic is old... I have to mention here that cak7 has already been added to the official OSCam build. So, if a specific DVB provider does not use any specialties regarding cak7, then the official OSCam build should also work.

Quote

Changeset 11735

Timestamp:

03/04/24 18:27:02

Author:

bust3d

Message:

added Streamrelay libdvbcsa - thanks to lpm11 <lpm11@lpm11>, fegol, icb, loka, kitte888, youtube18, WXbet and many more

added cak7 patch - thanks to ohmza, TV-Gamer and others

Display More

SOURCE: https://trac.streamboard.tv/oscam/changeset/11735

Hi.

I usually use a softcam client for everything, only CCcam v2.3.0. For softcam server purposes, I prefer to use OSCam - always the current version.

However, everything also depends on which DVB encoding system you use (which CAID)... which softcam communication protocol... how the specific decoding card behaves, etc. etc. etc. .

I use the two listed softcams for the IRDETO system. They proved to be the best for me.

If I tried to use other versions of CCcam as clients, communication stopped working within a few hours or days. A restart of the softcam server was necessary. I thought it was a softcams compatibility error. So, I tested it as a softcam client, also using OSCam. However, it did not help. I also tried different versions of CCcam as softcam clients, but that didn't help either. Only what I mentioned above proved true. So I've been using this "set" for a long time and it works without problems.

/// EDIT :

If you need to use only one softcam exclusively, as a client, e.g. for remote connection, I recommend OSCam despite everything. If you do not plan to combine different softcams and if you will only use one softcam (in one own set-top box), then you should rather use this OSCam. It is a multi-protocol softcam and has a very nice Web-GUI and also a lot of setting options.

Hi. The administrator of the softcam server will be able to advise you with this problem. Only he knows what is happening on the server... he sees the debug... he knows the coding systems used... he knows the configuration of the server... and he can check where the problem is. You have to contact him and not random people who unfortunately don't know anything about the softcam server you are connecting to. Also, the correct configuration of the softacm client for you is best advised only by the softcam server administrator.

Hi.

I don't have and don't use dpkg manager, so I can't advise you with dpkg installation manager.

The problem arises when unpacking the DEB installation package in your used Enigma2 - Peter Pan distribution. I don't know where the problem might be, because the DEB-package with the plugin works almost everywhere.

Copy it to the "/tmp" folder and try the following in Linux Shell. Try to get debug information...

dpkg -D2 -i /tmp/enigma2-plugin-extensions-chocholousek-picons_5.0.231225_all.deb

...or just unpack the package...

cd /tmp
dpkg --unpack /tmp/enigma2-plugin-extensions-chocholousek-picons_5.0.231225_all.deb

It could easily be some kind of Enigma2 error. I don't know exactly (I don't remember) how the debug is obtained from these systems. I think it is done via "journalctl":

journalctl --since "1 hour ago"        # the contents of the system log will be displayed from the current time, 1 hour backwards

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

I noticed that you are using an old version of the plugin. That is not good ! Download and install the latest plugin package (https://github.com/s3n0/e2plug…usekPicons/released_build). The old one (5.0.221007), if it is installed, let it be uninstalled.

Quote from mouadhada

Hi, why picons are not longer updated on the plugin ?

Hi. Picons continue to be updated. Approximately every 15 days ...... when there is enough free time. If you open the website https://picon.cz/ , the dates of the last updates are displayed in the right part of the website.

I don't see problems in assigning SNP <-> SRP, but in creating a suitable filename for a specific channel, because even if the definition for creating a file name is clear, it may not always be exact (it may not always be the same). There are many similar channel names which, when converted to a file name, will be the same.

Also, using lameDB is not easy, because there is a big mess (inconsistencies) in the content of these files. I have already tried to use lameDB more than once, but some important information is wrong there. LameDB ver.5 is a bit more polished, but something was missing there too. I don't remember what exactly. It is not possible to create a good mapping of SRC (ServiceReferenceCode) to file names, according to DVB channel names. For example, some people use reception from 3 channels at the same time, where there are often 2-3 identical names of the resulting file (after shortening the channel name) for always a different picon. I don't remember exactly, but during various experiments with lameDB file, I always ended up running into an unsolvable problem. That's why I use lameDB files really minimally. For example, some channel names officially present in lameDB are found more than once only because there is an SD version and also an HD version (according to the channel resolution). The first situation is often that the channel names are the same, but the HD and SD channel icons are different. Second, as far as I know, the formula for shortening channel names also includes deleting the final letters "HD" placed separately (after an empty space). Simply put, a lot of problems arise when creating these "abbreviated" channel names.

Hi.

I don't know what exactly you mean.

You have to specify - what doesn't work, what you want to achieve, ... and also how the ChocholousekPicons plugin is related to this, etc. .

It makes the process a bit more complicated if I were to add it to a plugin. There would have to be some kind of conversion table. Someone must then constantly take care of this table and maintain it ( chocholousek - picon designer). And then these symbolic lines... I don't know, um, if it won't cause problems, for example. in some Enigma2 SKINs or in some drivers for the front LCD display... or something similar.

By now, you should be able to find at least one SNP pikon color design that chocholousek (picon designer) put in there. They are background / color picons: "SNPtransaprent". They are probably only available in "220x132" resolution (I don't know exactly, because I don't follow the available picon designs... this is always handled by chocholousek himself).

Quote from BanjoXo71

Just want to update that i reflashed OpenBH 5.3, this time round i used the very latest picon ipk from github and all is installed and fully updated now. Its weird because i had other plugins that was the same such as ipchecker but with the new install that also worked to. Something must have happened [not sure what] but it fixed itself.

Thanks for a great add on :)

Hi.

Good... nice if it works.

Probably there was some error with the update - the previous beta / alpha test version became the official released version... but in the case of Enigma2 test-versions, I already saw that the directories for the plugins were in different paths than usual.

Also, the error could happen when you use a multiboot and it uses symbolic links to directories with plugins (and when these symbolic links or paths are lost for some reason).

Hard to say really since you didn't create a debug file ;-).

Quote from Melgas

Hello, chocholousek

I have been searching picons without success (HISPASAT 30W):

Sport TV + and 1, 2, 3, 4, 5, 6 and NBA Sport TV.

Picon transparent SAT 220X132 HISPASAT (30W).

Picon transparent Cable 220X132 ZON + MEO (Portugal).

Thank you very much.

Display More

Hi.

You're on the wrong thread... to support specific picons, you have to use the picon thread and not the enigma2 plugin thread :).

Post

RE: Picons by Chocholoušek

DTT ITALIA + SAT 9°E

CANALE 232 ( STUDIO + HbbTv )

1_0_1_FA9_107_217C_EEEE0000_0_0_0 - 1_0_1_FA9_107_217C_5A0000_0_0_0

Azzurra

Jan 16th 2024

There are many ways to debug the Enigma2.

In every Enigma2 distribution, you can find it elsewhere in the GUI MENU.

Of course, it can also be done through a terminal connection (PuTTY application, using Telnet or SSH protocol).

In OpenATV you can find it in:

GUI MENU > Settings > System > Debug

And there... turn on the debug log and reboot the set-top box.

Then trigger an error, and after the error occurs, a record is also created in the debugging file. Next, connect via an FTP connection and copy the debug file (folder /home/roots/logs) to the PC from the set-top box. Next, insert this file into the discussion or into my private message (due to possible personal data in the debugging file... even though... they probably won't be there anymore).

When you get the debug file, turn off debugging in OpenATV again. That's because it might slow down the Enigma2 a bit.

You have to contact the creators of OpenBH, let them fix the BUG. Unfortunately, I don't know OpenBH and I don't use it. I only know and use OpenATV and OpenPLi.

As I have already written to you twice, you must provide me with a debug file. Otherwise, I won't find out where the problem is in the case of your OpenBH.

OpenATV 7.4 is still not the official version! You can only get to it by manually changing the version number in the URL ! Change "/current/" in the URL address to the value "/7.4/" and you will see these T E S T versions ! This is a secret procedure and normally inaccessible to inexperienced users. These test-versions are intended (again repeating ! and I won't be anymore !) for developers, testers and experienced IT users !!!

The official URL for downloading the current released OpenATV edition is here:

https://www.opena.tv/downloads/

...or...

https://images.mynonpublic.com/openatv/current/

I can't help you without the debug file. Sorry. :-/

I would have to install the OpenATV that you own - I don't know which one, but I assume that the official OpenATV 7.4 has already been released (it is no longer just a development version). Then next I have to start debugging on this installed image.

But I guess that the error will be somewhere in upgrading the OpenATV 7.4 develop version to the new (full) released 7.4 version.

If I remember correctly, the developer versions use different directories for plugins. After you update to the official version, these old directories will remain there. And maybe that's the problem. That the upgraded official OpenATV can no longer find the plugin in the right directory. And now I'm just guessing the cause of the possible problem. I don't know if that's true. Maybe reinstalling the plugin or checking that there is a proper "plugin.py" file (i.e. module) and path to it would help:

# INSTALL - the latest released version of the plugin:

# (Warning ! The plugin configuration will be deleted !)

wget -qO- --no-check-certificate "https://github.com/s3n0/e2plugins/blob/master/ChocholousekPicons/online-setup?raw=true" | bash -s install

# or:

curl -LJs "https://github.com/s3n0/e2plugins/blob/master/ChocholousekPicons/online-setup?raw=true" | bash -s install

Also, the need for the ".py" / ".pyo" / ".pyc" files present may be different for the development version and for the official released version. The develop version should contain all of the listed ones (I'm not sure, but it probably does).

/////////EDIT:

So I'm adding info !

The official version of OpenATV 7.4 has not yet been released. ONLY version 7.3 is still available for download - as stable / released version. OpenATV 7.4 version is intended for testers and not for novices and amateurs ! As of today, version OpenATV 7.4 has still not been officially released.

If you are using version OpenATV 7.3, then you probably did something wrong, because in my case (Chocholousek Picons 5.0.231225), with my OpenATV 7.3 (up to date) everything works OK.

I repeat again that I need a debug file from you. Otherwise I won't find the error. The error should be / will be recorded in more detail in the debug file.

However, I still think that you are using the 7.4 version intended for developers / testers ... and there is a small problem in it.