Posts by abu baniaz

  • Picons: Service Named Picons

    You can have all three types in one folder. The priority of searches by Enigma2 is:

    Exact SRP

    Modified SRP (e.g namespace/dvb type changes)

    Utf8SNP

    SNP



    With ocrams picons packs, you cannot change between picon packs, you have to uninstall one before installing another. For argument's sake, if you installed an SRP version and wanted to install an SNP one. You installed 220x132 220 x132 but wanted to use 220x132 190x102. You installed dark on light and then wanted to install light on transparent. Any of these type of changes will result in a clash. You have to uninstall the first one before installing the next.


    For Ocram's packs, I decided against adding utf8snp links in the SNP.index files. People get confused by the fact that logo names and picon names are different. We would then have ask is that the SNP name or utf8snp name? Moreover, there are a lot of dead links. The utf8snp packs contain more working links than SNP ones anyway.


    If you are using another SNP picon pack or ones from kiddac's plugin, you could rename them. But why would you when both naming types work.


    If you install the "missing picons" plugin, it creates CSV files with symlinks to SRP which you could apply. But they will only work for current names and valid references. Better to just rename them when they change. This is why I find that other picon thread to be inefficient.

  • tuner setting

    Draw a picture/sketch/diagram if you want to avoid people assuming things. Also post screenshots of what you have currently set for each tuner.


    If the lever mount dish does not use USALS, you have to use advanced, Diseqc 1.2 and for each orbital position, tell it what position you have set your dish.


    The FBC tuners are set exactly like a non-FBC tuner if you are not using Unicable LNB. Start off with the fixed dish, then the USALS motor.

  • tuner setting

    I am understanding that you have 2 tuner cards, i.e 4 connection points. 16 tuners in total.


    I don't know which dish is in which tuner, so apply to the tuners you have used. I would have hooked up fixed dish to Tuner A. I would not have hooked up anything to Tuner B. Motorised dishes hooked up to Tuner I and also Tuner J.


    For fixed dish.

    Simple, single, whatever the orbital position that dish is pointing to.


    For the tuners with motorised dishes ( I am assuming the dishes have been aligned to use USALS)

    Simple, positioned, add your co-ordinates.


    The connection/tuner with no signal wire, set as FBC Automatic (This means internal loop-through when required. Nothing to do with Automatic).

  • tuner setting

    To be correct, tuner configuration must match the hardware.


    Your description of dishes/cabling is not clear enough for a proper response barring the motorised dish. And receiver does not come with cables, those are from your dishes/lnbs. Can you please draw a sketch/diagram.


    Unless you have unicable LNB/switch, tuner configuration is exactly the same as a non-fbc tuner.

  • replacing Duo with Duo2

    The file called "settings" that holds the configuration settings is held in RAM. If you do not stop Enigma2 before transferring it or editing, you will run into trouble.


    Transferring configuration settings has nothing to do with channel editors. My advice is to ignore the posts about Dreamset, Dreamboxedit, e-chanenlizer for the purpose of transferring your satellite motor configuration. It is irrelevant and unhelpful to your specific issue. The advice about channel editors is useful for copying/editing/transferring bouquets/channels.

  • replacing Duo with Duo2

    Please try the advice in post 2.


    In enigma2, there are different contexts of "settings". One interpretation is channel lists/bouquets. I suspect that this is what the other responses refer to. They will do bouquets/channels, but they will not save your configurations. With all due respect, their responses will not fulfill your requirements. The file called "settings" which holds the values you need is not touched by channel editors. You can test the suggestions if you want.


    Or issue this command using Putty which will create a file for you with only the tuner values.

    cat /etc/enigma2/settings | grep config.Nims > /tmp/mytunerconfig.txt

  • replacing Duo with Duo2

    The details will be in the file called "settings" located in /etc/enigma2. It's the lines with "NIM" If you stop enigma2 on the new receiver by issuing the following command using Putty/Terminal, "init 4", you can transfer the file to it. Restart with "init 3"

  • Picons: Service Named Picons

    UTF-8 Service Name Picons:


    Support for UTF8SNP was added to OpenPLI on 1st April 2024 in this commit:https://github.com/OpenViX/eni…57765a766dad42d67d13b502a

    Support for UTF8SNP was added to OpenPLI on 1st April 2024 in this commit: https://github.com/O...2f53d1b522ac3a4
    Support for UTF8SNP was added to ATV on 11th December 2024 in this commit: https://github.com/openatv/enigma2/comm ... f0862711ac



    UTF-8 is a character encoding system, created in 1993, that can represent more that one million characters. UTF-8 has become the de facto standard and today almost all webpages worldwide use this encoding. You can read more about it on Wikipedia ( https://en.wikipedia.org/wiki/UTF-8 ). Also, UTF-8 is the default encoding in Python 3 (which all images have now migrated to) and the characters are fully compatible with the Linux file system. So now the channel "Диема ХД" can have a picon with the filename “диема хд.png”. This type of picons are already in the feeds (packages marked utf8snp).


    Some of the picon packs on the image's plugin server are built from https://github.com/picons/picons so any problems with the packages should be reported there. The support for SNP on that project will be removed at some stage, so please start using the utf8snp sets and report issues before SNP sets are stopped.


    You must uninstall the other versions of picons (SRP or SNP) before installing the utf8snp version.

  • Picons: Service Named Picons

    Just to add, Service Named Picons (SNP) have been in all mainstream images since 2014. Surprisingly, people still want to use Service Reference Picons (SRP) and keep changing the names whenever there is a transponder change


    SNP code was introduced to OpenPLI on 8th November 2014 in this commit: https://github.com/OpenPLi/eni…ba36c3205af179b93fad86e38

    SNP code was introduced to OpenATV on 5th November 2014 in this commit: https://github.com/openatv/eni…8701f55aa4b382e525031966e


    To recap:

    Instead of using the service reference for the picon filename, the channel name is used instead, but at that time these were conceived it was decided to only allow lowercase ASCII letter and number characters. i.e. a-z and 0-9. All other characters, spaces, symbols, etc. were sent to the dustbin. This approach allowed for frequency and identifier changes and still continued to work, and was human readable.


    The limitation/problem with Service Name Picons is that the algorithm only allows a-z and 0-9 and no other characters. This is ok for channels that use the western alphabet without accents or special chars but not for Arabic ( اسم قناتي ) or Bulgarian ( Диема ХД ) or even western European ( Áèíöúñ ).

  • Plz Picon Sky iCAM package

    You cannot install two picon packages simultaneously.


    Until you get a better answer, download the hardlink snp or ut8snp version. Extract it (twice) and transfer every picon you need individually.


    Streamrelay bouquets are just a bouquet with modified service references. By using the name version of picons, you dont need to worry about service reference difference between normal channels and those with stream relay. Nor subsequent transponder changes.

  • FBC unicable on motorized dish issues on OE images

    So if one receiver sends the dish and LNB to 19.2 and other sends it to 13e, what does the motor do and how would you wire it? Or if you are recording on 13e and another timer kicks in on 19.2e, what does the receiver do?


    Until you or anyone can provide data from the LNB manufacturer that you can motorise a unicable LNB, it will not be coded.


    Good luck in your quest.