OpenPLi Wiki - User contributions [en]

Vu Multiboot

2024-10-02T09:12:30Z

Tech: /* Before you start */

=='''Intro'''==
With OpenPLi 9 we offer multiboot for all Vu+ '''4K''' receivers, so only the '''4K''' versions!!! So it's a Vu+ '''4K''' receiver specific feature that makes it possible to install multiple images on your Vu+ '''4K''' receiver. When you have activated this feature, you can install multiple images, how much images you can install, when it is supported, depends on the slots, let's say the partitions that become present. Below we will explain how to activate this feature.

=='''Initialize Vu+ 4K Multiboot'''==
By default Vu+ '''4K''' Multiboot is not active, you have to activate or Initialize Multiboot. If you want multiboot, you go to '''Main menu > Setup > Flash image'''. Your receiver needs connection to the internet (never connect your receiver directly to internet! Always behind a firewall/Router). So if you receiver supports it, below in the screen you will see the option Initialize Multiboot (see below)
[[File:VuMultiboot-001.jpg|centre|750px]] 

Now press the '''yellow button''' as pointed out in the picture above and the screen below will appear.
[[File:VuMultiboot-002.jpg|centre|750px]] 

Now you have tree choices,
*press Exit on your remote control and nothing is changed, so no multiboot,
*Press the '''Green button''' and you will Init Multiboot, as shown in the picture below, please wait until your receiver reboots.
[[File:VuMultiboot-003.jpg|centre|750px]]
*Press the '''Red button''' to completely remove the Multiboot option. when you do the screen below will appear.
[[File:VuMultiboot-004.jpg|centre|750px]] 
Pressed the Remove forever (as you can see above) you can still abort removing the Multiboot by selecting '''No''' with your remote control.
If you have pressed '''Yes''' and removed multiboot, please restart/reboot and after a restart the option "Initialize Multiboot" will be gone (see below).
[[File:VuMultiboot-005.jpg|centre|750px]]

===Remove forever===
----
Remove forever will of course only remove the multiboot feature from this particular image, so if you reconsider and want multiboot back, a flash will return the Multiboot feature. Remove forever will not be saved in your autobackup.

=='''Adding other OpenPLi versions or other images'''==
When you have multiboot you can install an image in every free slot (= partitions where you can install an image). In each slot you can install an OpenPLi version and there is the option to install OpenPLI with or without a backup. of course you can always install other images.

=='''AutoBackup'''==
When you flash a multi boot version from the menu a backup is created and restored by default. When this flash process starts there is a time window to cancel it, so by default a backup is created from the current image and will be restored right after the flash on the newly installed image. In most cases and certainly when there is no HDD present, a USB stick with enough space, has to be plugged into the receiver so create the backup. These backup files are relatively small. In many cases it is best to use a USB stick of about 1 Gb, albeit to store the downloaded image.

=='''How to select an installed multiboot image'''==
There are 2 ways to select the image to boot from. Using the remote control you simply press Menu and go into Standby/Restart menu. Press long on the power control button using your remote control a menu appears and as you can see in the picture below there is the "Multiboot image selector" option, once pressed it offers the images you have installed.

[[File:VuMultiboot-006.jpg|centre|750px]]

Now you can pick one and OpenPLi will boot into it. In the picture below only 1 is showed, as this is the one created after you initialized Multiboot. When you install more images these will also be displayed.
[[File:VuMultiboot-007.jpg|centre|750px]]

When there are more images installed there is also the possibility by pressing '''yellow button''' to remove an image. See picture below.

[[File:VuMultiboot-008.jpg|centre|750px]]

Once you remove an image, the '''yellow button''' changes to restore deleted images, in case you made a mistake. Even when you reboot you can restore deleted images, once you install a new one it the "old slot" it will be gone!

=='''Adding other images than OpenPLi'''==
If you want to add any other images, well other than OpenPLi, you can also flash them using the other images button, see pictures below. This will open the option to choose other brands.

[[File:VuMultiboot-009.jpg|centre|750px]]

[[File:VuMultiboot-010.jpg|centre|750px]]

=='''Forced loading recovery image'''==
The first image, the one in which you activated multi boot is called "the recovery image" is in slot 0. If you for some reason, you want to boot not from the menu using the multiboot image selector (see pictures above), then create an empty STARTUP_RECOVERY file at the root of you HHD/USB drive and hold de Power button for more than 12 seconds for reboot receiver.

=='''Multiboot images missing after an update?'''==
Under specific circumstances, it is possible to break the VU+ Kexec multiboot. This happens when the update contains a new kernel-image package, which gets installed in flash instead of in the current multiboot slot, if the image isn't built multiboot aware.
When this happens, the box will reboot into slot 0 (the original images flashed), the multiboot images will be gone, and Enigma will crash if you attempt to reinstall or reactivate multiboot.

However, not all is lost, and with a bit of commandline magic, you can restore the multiboot functionality without loss of data.

=== Before you start ===

It is recommended to make backups of your multiboot slots first, before you start restoring the multiboot kernel. This way, if the box won't boot after attempting the restore, you can always fall back to flashing the box via USB, install and activate multiboot again, and then restore your backups.

To make this backup, you need access to the commandline, so login using SSH or telnet. Then execute one of the following commands:
* <code>tar -cvzf /media/hdd/linuxrootfs1.tar.gz /linuxrootfs1</code> (for slot 1)
* <code>tar -cvzf /media/hdd/linuxrootfs2.tar.gz /linuxrootfs2</code> (for slot 2)
* <code>tar -cvzf /media/hdd/linuxrootfs3.tar.gz /linuxrootfs3</code> (for slot 3)
( if you don't want to use or don't have a local disk, change <code>/media/hdd</code> in these commands to your desired storage location. You need about 4GB of free space )

=== Reinstall the kexec multiboot kernel ===

Follow these steps, once you've booted slot 0, and logged in:
* execute the following command: ''opkg install vuplus-kexec --force-reinstall''
* for the '''VU+ Zero 4K''', execute the following command: <code>dd if=/usr/bin/kernel_auto.bin of=/dev/mmcblk0p4</code>
* for the '''VU+ Solo 4K''', execute the following command: <code>dd if=/usr/bin/kernel_auto.bin of=/dev/mmcblk0p1</code>
* for the '''VU+ Uno 4K''', execute the following command: <code>dd if=/usr/bin/kernel_auto.bin of=/dev/mmcblk0p1</code>
* for the '''VU+ Duo 4K''', execute the following command: <code>dd if=/usr/bin/kernel_auto.bin of=/dev/mmcblk0p6</code>
* for the '''VU+ Ultimo 4K''', execute the following command: <code>dd if=/usr/bin/kernel_auto.bin of=/dev/mmcblk0p1</code>
* for the '''VU+ Uno 4K SE''', execute the following command: <code>dd if=/usr/bin/kernel_auto.bin of=/dev/mmcblk0p1</code>
* for the '''VU+ Duo 4K SE''', execute the following command: <code>dd if=/usr/bin/kernel_auto.bin of=/dev/mmcblk0p6</code>
* execute the following command: <code>mv /usr/bin/STARTUP.cpio.gz /STARTUP.cpio.gz</code>
* <code>reboot</code>

=== Plan B ===

If the above doesn't give you a working box back, with all our multiboot slots exactly as they were, it is time for plan B.

If you followed the recommendation and made a backup first, that is. If you did, follow these steps:
* reflash the STB via USB, with the image you want to be used as slot 0. We advise to use OpenPLi, as it is one of the smallest available.
* after the image boots up, install and activate multiboot again. The box will restart after this.
* use telnet to connect (SSH won't work on newly flashed images without password), and restore your backups:
* <code>tar -xvzf /media/hdd/linuxrootfs1.tar.gz -C /</code> (for slot 1)
* <code>tar -xvzf /media/hdd/linuxrootfs2.tar.gz -C /</code> (for slot 2)
* <code>tar -xvzf /media/hdd/linuxrootfs3.tar.gz -C /</code> (for slot 3)
* <code>reboot</code>

The box should now restart the image in slot 0, and your multiboot slots should be available for selection again.

'''NB''': Be VERY careful when typing in these commands. A simple typo can spell disaster and may result in you having to start from scratch again, with the loss of your multiboot slots. It is advised to use copy/paste to make sure you don't make any mistakes while typing.

Vu Multiboot

2024-06-20T14:28:43Z

Tech: /* Restore kexec kernel for VU+ Duo 4K ONLY!! */

=='''Intro'''==
With OpenPLi 9 we offer multiboot for all Vu+ '''4K''' receivers, so only the '''4K''' versions!!! So it's a Vu+ '''4K''' receiver specific feature that makes it possible to install multiple images on your Vu+ '''4K''' receiver. When you have activated this feature, you can install multiple images, how much images you can install, when it is supported, depends on the slots, let's say the partitions that become present. Below we will explain how to activate this feature.

=='''Initialize Vu+ 4K Multiboot'''==
By default Vu+ '''4K''' Multiboot is not active, you have to activate or Initialize Multiboot. If you want multiboot, you go to '''Main menu > Setup > Flash image'''. Your receiver needs connection to the internet (never connect your receiver directly to internet! Always behind a firewall/Router). So if you receiver supports it, below in the screen you will see the option Initialize Multiboot (see below)
[[File:VuMultiboot-001.jpg|centre|750px]] 

Now press the '''yellow button''' as pointed out in the picture above and the screen below will appear.
[[File:VuMultiboot-002.jpg|centre|750px]] 

Now you have tree choices,
*press Exit on your remote control and nothing is changed, so no multiboot,
*Press the '''Green button''' and you will Init Multiboot, as shown in the picture below, please wait until your receiver reboots.
[[File:VuMultiboot-003.jpg|centre|750px]]
*Press the '''Red button''' to completely remove the Multiboot option. when you do the screen below will appear.
[[File:VuMultiboot-004.jpg|centre|750px]] 
Pressed the Remove forever (as you can see above) you can still abort removing the Multiboot by selecting '''No''' with your remote control.
If you have pressed '''Yes''' and removed multiboot, please restart/reboot and after a restart the option "Initialize Multiboot" will be gone (see below).
[[File:VuMultiboot-005.jpg|centre|750px]]

===Remove forever===
----
Remove forever will of course only remove the multiboot feature from this particular image, so if you reconsider and want multiboot back, a flash will return the Multiboot feature. Remove forever will not be saved in your autobackup.

=='''Adding other OpenPLi versions or other images'''==
When you have multiboot you can install an image in every free slot (= partitions where you can install an image). In each slot you can install an OpenPLi version and there is the option to install OpenPLI with or without a backup. of course you can always install other images.

=='''AutoBackup'''==
When you flash a multi boot version from the menu a backup is created and restored by default. When this flash process starts there is a time window to cancel it, so by default a backup is created from the current image and will be restored right after the flash on the newly installed image. In most cases and certainly when there is no HDD present, a USB stick with enough space, has to be plugged into the receiver so create the backup. These backup files are relatively small. In many cases it is best to use a USB stick of about 1 Gb, albeit to store the downloaded image.

=='''How to select an installed multiboot image'''==
There are 2 ways to select the image to boot from. Using the remote control you simply press Menu and go into Standby/Restart menu. Press long on the power control button using your remote control a menu appears and as you can see in the picture below there is the "Multiboot image selector" option, once pressed it offers the images you have installed.

[[File:VuMultiboot-006.jpg|centre|750px]]

Now you can pick one and OpenPLi will boot into it. In the picture below only 1 is showed, as this is the one created after you initialized Multiboot. When you install more images these will also be displayed.
[[File:VuMultiboot-007.jpg|centre|750px]]

When there are more images installed there is also the possibility by pressing '''yellow button''' to remove an image. See picture below.

[[File:VuMultiboot-008.jpg|centre|750px]]

Once you remove an image, the '''yellow button''' changes to restore deleted images, in case you made a mistake. Even when you reboot you can restore deleted images, once you install a new one it the "old slot" it will be gone!

=='''Adding other images than OpenPLi'''==
If you want to add any other images, well other than OpenPLi, you can also flash them using the other images button, see pictures below. This will open the option to choose other brands.

[[File:VuMultiboot-009.jpg|centre|750px]]

[[File:VuMultiboot-010.jpg|centre|750px]]

=='''Forced loading recovery image'''==
The first image, the one in which you activated multi boot is called "the recovery image" is in slot 0. If you for some reason, you want to boot not from the menu using the multiboot image selector (see pictures above), then create an empty STARTUP_RECOVERY file at the root of you HHD/USB drive and hold de Power button for more than 12 seconds for reboot receiver.

=='''Restore kexec kernel for VU+ Duo 4K ONLY!!'''==
Note: it is recommended to make backups first before you start restoring the slots by using plan A, in case the box won't boot you can always fall back to plan B.
 

Boot the STB in slot 0 

- log on the STB with ssh or telnet 

- execute the following command: opkg install vuplus-kexec --force-reinstall 

- execute the following command: dd if=/usr/bin/kernel_auto.bin of=/dev/mmcblk0p6 

- execute the following command: mv /usr/bin/STARTUP.cpio.gz /STARTUP.cpio.gz 

reboot 
If this procedure fails it is time for plan B: 
- backup the folders: linuxrootfs1, linuxrootfs2 and linuxrootfs3 with tar -czvf, on an external device 
example: tar -cvzf /media/hdd/linuxrootfs1.tar.gz /linuxrootfs1 (repeat this als for rootfs2 and 3) 
- reflash the STB via USB 
- install the multiboot option 
- restore the backup into the root of slot 0 
example: cd / 
tar -xzvf /media/hdd/linuxrootfs1.tar.gz (repeat this for rootfs2 and 3) 
 
After rebooting the STB the slots should be available again. 
 
Note: Again, it is recommended to make backups first before you start restoring the slots by using plan A, in case the box won't boot you can always fall back to plan B.

Vu Multiboot

2024-06-20T14:27:29Z

Tech:

=='''Intro'''==
With OpenPLi 9 we offer multiboot for all Vu+ '''4K''' receivers, so only the '''4K''' versions!!! So it's a Vu+ '''4K''' receiver specific feature that makes it possible to install multiple images on your Vu+ '''4K''' receiver. When you have activated this feature, you can install multiple images, how much images you can install, when it is supported, depends on the slots, let's say the partitions that become present. Below we will explain how to activate this feature.

=='''Initialize Vu+ 4K Multiboot'''==
By default Vu+ '''4K''' Multiboot is not active, you have to activate or Initialize Multiboot. If you want multiboot, you go to '''Main menu > Setup > Flash image'''. Your receiver needs connection to the internet (never connect your receiver directly to internet! Always behind a firewall/Router). So if you receiver supports it, below in the screen you will see the option Initialize Multiboot (see below)
[[File:VuMultiboot-001.jpg|centre|750px]] 

Now press the '''yellow button''' as pointed out in the picture above and the screen below will appear.
[[File:VuMultiboot-002.jpg|centre|750px]] 

Now you have tree choices,
*press Exit on your remote control and nothing is changed, so no multiboot,
*Press the '''Green button''' and you will Init Multiboot, as shown in the picture below, please wait until your receiver reboots.
[[File:VuMultiboot-003.jpg|centre|750px]]
*Press the '''Red button''' to completely remove the Multiboot option. when you do the screen below will appear.
[[File:VuMultiboot-004.jpg|centre|750px]] 
Pressed the Remove forever (as you can see above) you can still abort removing the Multiboot by selecting '''No''' with your remote control.
If you have pressed '''Yes''' and removed multiboot, please restart/reboot and after a restart the option "Initialize Multiboot" will be gone (see below).
[[File:VuMultiboot-005.jpg|centre|750px]]

===Remove forever===
----
Remove forever will of course only remove the multiboot feature from this particular image, so if you reconsider and want multiboot back, a flash will return the Multiboot feature. Remove forever will not be saved in your autobackup.

=='''Adding other OpenPLi versions or other images'''==
When you have multiboot you can install an image in every free slot (= partitions where you can install an image). In each slot you can install an OpenPLi version and there is the option to install OpenPLI with or without a backup. of course you can always install other images.

=='''AutoBackup'''==
When you flash a multi boot version from the menu a backup is created and restored by default. When this flash process starts there is a time window to cancel it, so by default a backup is created from the current image and will be restored right after the flash on the newly installed image. In most cases and certainly when there is no HDD present, a USB stick with enough space, has to be plugged into the receiver so create the backup. These backup files are relatively small. In many cases it is best to use a USB stick of about 1 Gb, albeit to store the downloaded image.

=='''How to select an installed multiboot image'''==
There are 2 ways to select the image to boot from. Using the remote control you simply press Menu and go into Standby/Restart menu. Press long on the power control button using your remote control a menu appears and as you can see in the picture below there is the "Multiboot image selector" option, once pressed it offers the images you have installed.

[[File:VuMultiboot-006.jpg|centre|750px]]

Now you can pick one and OpenPLi will boot into it. In the picture below only 1 is showed, as this is the one created after you initialized Multiboot. When you install more images these will also be displayed.
[[File:VuMultiboot-007.jpg|centre|750px]]

When there are more images installed there is also the possibility by pressing '''yellow button''' to remove an image. See picture below.

[[File:VuMultiboot-008.jpg|centre|750px]]

Once you remove an image, the '''yellow button''' changes to restore deleted images, in case you made a mistake. Even when you reboot you can restore deleted images, once you install a new one it the "old slot" it will be gone!

=='''Adding other images than OpenPLi'''==
If you want to add any other images, well other than OpenPLi, you can also flash them using the other images button, see pictures below. This will open the option to choose other brands.

[[File:VuMultiboot-009.jpg|centre|750px]]

[[File:VuMultiboot-010.jpg|centre|750px]]

=='''Forced loading recovery image'''==
The first image, the one in which you activated multi boot is called "the recovery image" is in slot 0. If you for some reason, you want to boot not from the menu using the multiboot image selector (see pictures above), then create an empty STARTUP_RECOVERY file at the root of you HHD/USB drive and hold de Power button for more than 12 seconds for reboot receiver.

=='''Restore kexec kernel for VU+ Duo 4K ONLY!!'''==
Note: it is recommended to make backups first before you start restoring the slots by using plan A, in case the box won't boot you can always fall back to plan B.
 

Boot the STB in slot 0 

- log on the STB with ssh or telnet 

- execute the following command: opkg install vuplus-kexec --force-reinstall 

- execute the following command: dd if=/usr/bin/kernel_auto.bin of=/dev/mmcblk0p6 

- execute the following command: mv /usr/bin/STARTUP.cpio.gz /STARTUP.cpio.gz 

reboot 
If this procedure fails it is time for plan B: 
- backup the folders: linuxrootfs1, linuxrootfs2 and linuxrootfs3 with tar -czvf, on an external device 
example: tar -cvzf /media/hdd/linuxrootfs1.tar.gz /linuxrootfs1 (repeat this als for rootfs2 and 3) 
- reflash the STB via USB 
- install the multiboot option 
- restore the backup into the root of slot 0 
example: cd / 
tar -xzvf /media/hdd/linuxrootfs1.tar.gz (repeat this for rootfs2 and 3) 
 
After rebooting the STB the slots should be available again. 
 
Note: it is recommended to make backups first before you start restoring the slots by using plan A, in case the box won't boot you can always fall back to plan B.

Vu Multiboot

2024-06-20T14:25:11Z

Tech:

=='''Intro'''==
With OpenPLi 9 we offer multiboot for all Vu+ '''4K''' receivers, so only the '''4K''' versions!!! So it's a Vu+ '''4K''' receiver specific feature that makes it possible to install multiple images on your Vu+ '''4K''' receiver. When you have activated this feature, you can install multiple images, how much images you can install, when it is supported, depends on the slots, let's say the partitions that become present. Below we will explain how to activate this feature.

=='''Initialize Vu+ 4K Multiboot'''==
By default Vu+ '''4K''' Multiboot is not active, you have to activate or Initialize Multiboot. If you want multiboot, you go to '''Main menu > Setup > Flash image'''. Your receiver needs connection to the internet (never connect your receiver directly to internet! Always behind a firewall/Router). So if you receiver supports it, below in the screen you will see the option Initialize Multiboot (see below)
[[File:VuMultiboot-001.jpg|centre|750px]] 

Now press the '''yellow button''' as pointed out in the picture above and the screen below will appear.
[[File:VuMultiboot-002.jpg|centre|750px]] 

Now you have tree choices,
*press Exit on your remote control and nothing is changed, so no multiboot,
*Press the '''Green button''' and you will Init Multiboot, as shown in the picture below, please wait until your receiver reboots.
[[File:VuMultiboot-003.jpg|centre|750px]]
*Press the '''Red button''' to completely remove the Multiboot option. when you do the screen below will appear.
[[File:VuMultiboot-004.jpg|centre|750px]] 
Pressed the Remove forever (as you can see above) you can still abort removing the Multiboot by selecting '''No''' with your remote control.
If you have pressed '''Yes''' and removed multiboot, please restart/reboot and after a restart the option "Initialize Multiboot" will be gone (see below).
[[File:VuMultiboot-005.jpg|centre|750px]]

===Remove forever===
----
Remove forever will of course only remove the multiboot feature from this particular image, so if you reconsider and want multiboot back, a flash will return the Multiboot feature. Remove forever will not be saved in your autobackup.

=='''Adding other OpenPLi versions or other images'''==
When you have multiboot you can install an image in every free slot (= partitions where you can install an image). In each slot you can install an OpenPLi version and there is the option to install OpenPLI with or without a backup. of course you can always install other images.

=='''AutoBackup'''==
When you flash a multi boot version from the menu a backup is created and restored by default. When this flash process starts there is a time window to cancel it, so by default a backup is created from the current image and will be restored right after the flash on the newly installed image. In most cases and certainly when there is no HDD present, a USB stick with enough space, has to be plugged into the receiver so create the backup. These backup files are relatively small. In many cases it is best to use a USB stick of about 1 Gb, albeit to store the downloaded image.

=='''How to select an installed multiboot image'''==
There are 2 ways to select the image to boot from. Using the remote control you simply press Menu and go into Standby/Restart menu. Press long on the power control button using your remote control a menu appears and as you can see in the picture below there is the "Multiboot image selector" option, once pressed it offers the images you have installed.

[[File:VuMultiboot-006.jpg|centre|750px]]

Now you can pick one and OpenPLi will boot into it. In the picture below only 1 is showed, as this is the one created after you initialized Multiboot. When you install more images these will also be displayed.
[[File:VuMultiboot-007.jpg|centre|750px]]

When there are more images installed there is also the possibility by pressing '''yellow button''' to remove an image. See picture below.

[[File:VuMultiboot-008.jpg|centre|750px]]

Once you remove an image, the '''yellow button''' changes to restore deleted images, in case you made a mistake. Even when you reboot you can restore deleted images, once you install a new one it the "old slot" it will be gone!

=='''Adding other images than OpenPLi'''==
If you want to add any other images, well other than OpenPLi, you can also flash them using the other images button, see pictures below. This will open the option to choose other brands.

[[File:VuMultiboot-009.jpg|centre|750px]]

[[File:VuMultiboot-010.jpg|centre|750px]]

=='''Forced loading recovery image'''==
The first image, the one in which you activated multi boot is called "the recovery image" is in slot 0. If you for some reason, you want to boot not from the menu using the multiboot image selector (see pictures above), then create an empty STARTUP_RECOVERY file at the root of you HHD/USB drive and hold de Power button for more than 12 seconds for reboot receiver.

=='''Restore kexec kernel for VU+ Duo 4K ONLY!!'''==

Boot the STB in slot 0
- log on the STB with ssh or telnet 

- execute the following command: opkg install vuplus-kexec --force-reinstall 

- execute the following command: dd if=/usr/bin/kernel_auto.bin of=/dev/mmcblk0p6 

- execute the following command: mv /usr/bin/STARTUP.cpio.gz /STARTUP.cpio.gz 

reboot 
If this procedure fails it is time for plan B: 
- backup the folders: linuxrootfs1, linuxrootfs2 and linuxrootfs3 with tar -czvf, on an external device 
example: tar -cvzf /media/hdd/linuxrootfs1.tar.gz /linuxrootfs1 (repeat this als for rootfs2 and 3) 
- reflash the STB via USB 
- install the multiboot option 
- restore the backup into the root of slot 0 
example: cd / 
tar -xzvf /media/hdd/linuxrootfs1.tar.gz (repeat this for rootfs2 and 3) 
 
After rebooting the STB the slots should be available again. 
 
Note: it is recommended to make backups first before you start restoring the slots by using plan A, in case the box won't boot you can always fall back to plan B.

Vu Multiboot

2024-06-20T14:23:36Z

Tech:

=='''Intro'''==
With OpenPLi 9 we offer multiboot for all Vu+ '''4K''' receivers, so only the '''4K''' versions!!! So it's a Vu+ '''4K''' receiver specific feature that makes it possible to install multiple images on your Vu+ '''4K''' receiver. When you have activated this feature, you can install multiple images, how much images you can install, when it is supported, depends on the slots, let's say the partitions that become present. Below we will explain how to activate this feature.

=='''Initialize Vu+ 4K Multiboot'''==
By default Vu+ '''4K''' Multiboot is not active, you have to activate or Initialize Multiboot. If you want multiboot, you go to '''Main menu > Setup > Flash image'''. Your receiver needs connection to the internet (never connect your receiver directly to internet! Always behind a firewall/Router). So if you receiver supports it, below in the screen you will see the option Initialize Multiboot (see below)
[[File:VuMultiboot-001.jpg|centre|750px]] 

Now press the '''yellow button''' as pointed out in the picture above and the screen below will appear.
[[File:VuMultiboot-002.jpg|centre|750px]] 

Now you have tree choices,
*press Exit on your remote control and nothing is changed, so no multiboot,
*Press the '''Green button''' and you will Init Multiboot, as shown in the picture below, please wait until your receiver reboots.
[[File:VuMultiboot-003.jpg|centre|750px]]
*Press the '''Red button''' to completely remove the Multiboot option. when you do the screen below will appear.
[[File:VuMultiboot-004.jpg|centre|750px]] 
Pressed the Remove forever (as you can see above) you can still abort removing the Multiboot by selecting '''No''' with your remote control.
If you have pressed '''Yes''' and removed multiboot, please restart/reboot and after a restart the option "Initialize Multiboot" will be gone (see below).
[[File:VuMultiboot-005.jpg|centre|750px]]

===Remove forever===
----
Remove forever will of course only remove the multiboot feature from this particular image, so if you reconsider and want multiboot back, a flash will return the Multiboot feature. Remove forever will not be saved in your autobackup.

=='''Adding other OpenPLi versions or other images'''==
When you have multiboot you can install an image in every free slot (= partitions where you can install an image). In each slot you can install an OpenPLi version and there is the option to install OpenPLI with or without a backup. of course you can always install other images.

=='''AutoBackup'''==
When you flash a multi boot version from the menu a backup is created and restored by default. When this flash process starts there is a time window to cancel it, so by default a backup is created from the current image and will be restored right after the flash on the newly installed image. In most cases and certainly when there is no HDD present, a USB stick with enough space, has to be plugged into the receiver so create the backup. These backup files are relatively small. In many cases it is best to use a USB stick of about 1 Gb, albeit to store the downloaded image.

=='''How to select an installed multiboot image'''==
There are 2 ways to select the image to boot from. Using the remote control you simply press Menu and go into Standby/Restart menu. Press long on the power control button using your remote control a menu appears and as you can see in the picture below there is the "Multiboot image selector" option, once pressed it offers the images you have installed.

[[File:VuMultiboot-006.jpg|centre|750px]]

Now you can pick one and OpenPLi will boot into it. In the picture below only 1 is showed, as this is the one created after you initialized Multiboot. When you install more images these will also be displayed.
[[File:VuMultiboot-007.jpg|centre|750px]]

When there are more images installed there is also the possibility by pressing '''yellow button''' to remove an image. See picture below.

[[File:VuMultiboot-008.jpg|centre|750px]]

Once you remove an image, the '''yellow button''' changes to restore deleted images, in case you made a mistake. Even when you reboot you can restore deleted images, once you install a new one it the "old slot" it will be gone!

=='''Adding other images than OpenPLi'''==
If you want to add any other images, well other than OpenPLi, you can also flash them using the other images button, see pictures below. This will open the option to choose other brands.

[[File:VuMultiboot-009.jpg|centre|750px]]

[[File:VuMultiboot-010.jpg|centre|750px]]

=='''Forced loading recovery image'''==
The first image, the one in which you activated multi boot is called "the recovery image" is in slot 0. If you for some reason, you want to boot not from the menu using the multiboot image selector (see pictures above), then create an empty STARTUP_RECOVERY file at the root of you HHD/USB drive and hold de Power button for more than 12 seconds for reboot receiver.

=='''Restore kexec kernel for VU+ Duo 4K ONLY!!'''==

Boot the STB in slot 0
- log on the STB with ssh or telnet 

- execute the following command: opkg install vuplus-kexec --force-reinstall 

- execute the following command: dd if=/usr/bin/kernel_auto.bin of=/dev/mmcblk0p6 

- execute the following command: mv /usr/bin/STARTUP.cpio.gz /STARTUP.cpio.gz 

reboot 
If this procedure fails it is time for plan B: 
- backup the folders: linuxrootfs1, linuxrootfs2 and linuxrootfs3 with tar -czvf, on an external device 
example: tar -cvzf /media/hdd/linuxrootfs1.tar.gz /linuxrootfs1 (repeat this als for rootfs2 and 3) 
- reflash the STB via USB 
- install the multiboot option 
- restore the backup into the root of slot 0 
example: cd / 
tar -xzvf /media/hdd/linuxrootfs1.tar.gz (repeat this for rootfs2 and 3) 
 
After rebooting the STB the slots should be available again. 
 
Note: it is recommended to make backups first before you start to restore the slots by using plan A, in case the box won't boot you can always fall back to plan B.

Vu Multiboot

2024-06-20T14:20:52Z

Tech:

=='''Intro'''==
With OpenPLi 9 we offer multiboot for all Vu+ '''4K''' receivers, so only the '''4K''' versions!!! So it's a Vu+ '''4K''' receiver specific feature that makes it possible to install multiple images on your Vu+ '''4K''' receiver. When you have activated this feature, you can install multiple images, how much images you can install, when it is supported, depends on the slots, let's say the partitions that become present. Below we will explain how to activate this feature.

=='''Initialize Vu+ 4K Multiboot'''==
By default Vu+ '''4K''' Multiboot is not active, you have to activate or Initialize Multiboot. If you want multiboot, you go to '''Main menu > Setup > Flash image'''. Your receiver needs connection to the internet (never connect your receiver directly to internet! Always behind a firewall/Router). So if you receiver supports it, below in the screen you will see the option Initialize Multiboot (see below)
[[File:VuMultiboot-001.jpg|centre|750px]] 

Now press the '''yellow button''' as pointed out in the picture above and the screen below will appear.
[[File:VuMultiboot-002.jpg|centre|750px]] 

Now you have tree choices,
*press Exit on your remote control and nothing is changed, so no multiboot,
*Press the '''Green button''' and you will Init Multiboot, as shown in the picture below, please wait until your receiver reboots.
[[File:VuMultiboot-003.jpg|centre|750px]]
*Press the '''Red button''' to completely remove the Multiboot option. when you do the screen below will appear.
[[File:VuMultiboot-004.jpg|centre|750px]] 
Pressed the Remove forever (as you can see above) you can still abort removing the Multiboot by selecting '''No''' with your remote control.
If you have pressed '''Yes''' and removed multiboot, please restart/reboot and after a restart the option "Initialize Multiboot" will be gone (see below).
[[File:VuMultiboot-005.jpg|centre|750px]]

===Remove forever===
----
Remove forever will of course only remove the multiboot feature from this particular image, so if you reconsider and want multiboot back, a flash will return the Multiboot feature. Remove forever will not be saved in your autobackup.

=='''Adding other OpenPLi versions or other images'''==
When you have multiboot you can install an image in every free slot (= partitions where you can install an image). In each slot you can install an OpenPLi version and there is the option to install OpenPLI with or without a backup. of course you can always install other images.

=='''AutoBackup'''==
When you flash a multi boot version from the menu a backup is created and restored by default. When this flash process starts there is a time window to cancel it, so by default a backup is created from the current image and will be restored right after the flash on the newly installed image. In most cases and certainly when there is no HDD present, a USB stick with enough space, has to be plugged into the receiver so create the backup. These backup files are relatively small. In many cases it is best to use a USB stick of about 1 Gb, albeit to store the downloaded image.

=='''How to select an installed multiboot image'''==
There are 2 ways to select the image to boot from. Using the remote control you simply press Menu and go into Standby/Restart menu. Press long on the power control button using your remote control a menu appears and as you can see in the picture below there is the "Multiboot image selector" option, once pressed it offers the images you have installed.

[[File:VuMultiboot-006.jpg|centre|750px]]

Now you can pick one and OpenPLi will boot into it. In the picture below only 1 is showed, as this is the one created after you initialized Multiboot. When you install more images these will also be displayed.
[[File:VuMultiboot-007.jpg|centre|750px]]

When there are more images installed there is also the possibility by pressing '''yellow button''' to remove an image. See picture below.

[[File:VuMultiboot-008.jpg|centre|750px]]

Once you remove an image, the '''yellow button''' changes to restore deleted images, in case you made a mistake. Even when you reboot you can restore deleted images, once you install a new one it the "old slot" it will be gone!

=='''Adding other images than OpenPLi'''==
If you want to add any other images, well other than OpenPLi, you can also flash them using the other images button, see pictures below. This will open the option to choose other brands.

[[File:VuMultiboot-009.jpg|centre|750px]]

[[File:VuMultiboot-010.jpg|centre|750px]]

=='''Forced loading recovery image'''==
The first image, the one in which you activated multi boot is called "the recovery image" is in slot 0. If you for some reason, you want to boot not from the menu using the multiboot image selector (see pictures above), then create an empty STARTUP_RECOVERY file at the root of you HHD/USB drive and hold de Power button for more than 12 seconds for reboot receiver.

=='''Restore kexec kernel for VU+ Duo 4K ONLY!!'''==

Boot the STB in slot 0
- log on the STB with ssh or telnet 

- execute the following command: opkg install vuplus-kexec --force-reinstall 

- execute the following command: dd if=/usr/bin/kernel_auto.bin of=/dev/mmcblk0p6 

- execute the following command: mv /usr/bin/STARTUP.cpio.gz /STARTUP.cpio.gz 

reboot 
If this procedure fails it is time for plan B: 
- backup the folders: linuxrootfs1, linuxrootfs2 and linuxrootfs3 with tar -czvf, on an external device 
example: tar -cvzf /media/hdd/linuxrootfs1.tar.gz /linuxrootfs1 (repeat this als for rootfs2 and 3) 
- reflash the STB via USB 
- install the multiboot option 
- restore the backup into the root of slot 0 
example: cd /; tar -xzvf /media/hdd/linuxrootfs1.tar.gz (repeat this for rootfs2 and 3) 
 
After rebooting the STB the slots should be available again. 
 
Note: it is recommended to make backups first before you start to restore the slots by using plan A, in case the box won't boot you can always fall back to plan B.

Vu Multiboot

2024-06-20T14:19:56Z

Tech:

=='''Intro'''==
With OpenPLi 9 we offer multiboot for all Vu+ '''4K''' receivers, so only the '''4K''' versions!!! So it's a Vu+ '''4K''' receiver specific feature that makes it possible to install multiple images on your Vu+ '''4K''' receiver. When you have activated this feature, you can install multiple images, how much images you can install, when it is supported, depends on the slots, let's say the partitions that become present. Below we will explain how to activate this feature.

=='''Initialize Vu+ 4K Multiboot'''==
By default Vu+ '''4K''' Multiboot is not active, you have to activate or Initialize Multiboot. If you want multiboot, you go to '''Main menu > Setup > Flash image'''. Your receiver needs connection to the internet (never connect your receiver directly to internet! Always behind a firewall/Router). So if you receiver supports it, below in the screen you will see the option Initialize Multiboot (see below)
[[File:VuMultiboot-001.jpg|centre|750px]] 

Now press the '''yellow button''' as pointed out in the picture above and the screen below will appear.
[[File:VuMultiboot-002.jpg|centre|750px]] 

Now you have tree choices,
*press Exit on your remote control and nothing is changed, so no multiboot,
*Press the '''Green button''' and you will Init Multiboot, as shown in the picture below, please wait until your receiver reboots.
[[File:VuMultiboot-003.jpg|centre|750px]]
*Press the '''Red button''' to completely remove the Multiboot option. when you do the screen below will appear.
[[File:VuMultiboot-004.jpg|centre|750px]] 
Pressed the Remove forever (as you can see above) you can still abort removing the Multiboot by selecting '''No''' with your remote control.
If you have pressed '''Yes''' and removed multiboot, please restart/reboot and after a restart the option "Initialize Multiboot" will be gone (see below).
[[File:VuMultiboot-005.jpg|centre|750px]]

===Remove forever===
----
Remove forever will of course only remove the multiboot feature from this particular image, so if you reconsider and want multiboot back, a flash will return the Multiboot feature. Remove forever will not be saved in your autobackup.

=='''Adding other OpenPLi versions or other images'''==
When you have multiboot you can install an image in every free slot (= partitions where you can install an image). In each slot you can install an OpenPLi version and there is the option to install OpenPLI with or without a backup. of course you can always install other images.

=='''AutoBackup'''==
When you flash a multi boot version from the menu a backup is created and restored by default. When this flash process starts there is a time window to cancel it, so by default a backup is created from the current image and will be restored right after the flash on the newly installed image. In most cases and certainly when there is no HDD present, a USB stick with enough space, has to be plugged into the receiver so create the backup. These backup files are relatively small. In many cases it is best to use a USB stick of about 1 Gb, albeit to store the downloaded image.

=='''How to select an installed multiboot image'''==
There are 2 ways to select the image to boot from. Using the remote control you simply press Menu and go into Standby/Restart menu. Press long on the power control button using your remote control a menu appears and as you can see in the picture below there is the "Multiboot image selector" option, once pressed it offers the images you have installed.

[[File:VuMultiboot-006.jpg|centre|750px]]

Now you can pick one and OpenPLi will boot into it. In the picture below only 1 is showed, as this is the one created after you initialized Multiboot. When you install more images these will also be displayed.
[[File:VuMultiboot-007.jpg|centre|750px]]

When there are more images installed there is also the possibility by pressing '''yellow button''' to remove an image. See picture below.

[[File:VuMultiboot-008.jpg|centre|750px]]

Once you remove an image, the '''yellow button''' changes to restore deleted images, in case you made a mistake. Even when you reboot you can restore deleted images, once you install a new one it the "old slot" it will be gone!

=='''Adding other images than OpenPLi'''==
If you want to add any other images, well other than OpenPLi, you can also flash them using the other images button, see pictures below. This will open the option to choose other brands.

[[File:VuMultiboot-009.jpg|centre|750px]]

[[File:VuMultiboot-010.jpg|centre|750px]]

=='''Forced loading recovery image'''==
The first image, the one in which you activated multi boot is called "the recovery image" is in slot 0. If you for some reason, you want to boot not from the menu using the multiboot image selector (see pictures above), then create an empty STARTUP_RECOVERY file at the root of you HHD/USB drive and hold de Power button for more than 12 seconds for reboot receiver.

=='''Restore kexec kernel for VU+ Duo 4K ONLY!!'''==

Boot the STB in slot 0
- log on the STB with ssh or telnet 

- execute the following command: opkg install vuplus-kexec --force-reinstall 

- execute the following command: dd if=/usr/bin/kernel_auto.bin of=/dev/mmcblk0p6 

- execute the following command: mv /usr/bin/STARTUP.cpio.gz /STARTUP.cpio.gz 

reboot 
If this procedure fails it is time for plan B: 
- backup the folders: linuxrootfs1, linuxrootfs2 and linuxrootfs3 with tar -czvf, on an external device 
example: tar -cvzf /media/hdd/linuxrootfs1.tar.gz /linuxrootfs1 (repeat this als for rootfs2 and 3) 
- reflash the STB via USB 
- install the multiboot option 
- restore the backup into the root of slot 0 
example: cd /; tar -xzvf /media/hdd/linuxrootfs1.tar.gz (repeat this for rootfs2 and 3) 
 
After rebooting the STB the slots should be available again. 
 
Note: it is recommended to make backups first before you start to restore the slots by using plan A, in case the box won't boot you can fall back to plan B.

Releasenotes-9.0

2023-10-24T09:14:35Z

Tech: /* New features or improved features: */

==New features or improved features:==
*'''This image is using the OE 'Hardknott branch' ([https://wiki.yoctoproject.org/wiki/ReleasesYocto project])'''
*Standby add delay 1.5 sec deep standby and CEC
*Add flash online support for sfx6008
*FlashImage add sanity check if plugin Autobackup is running
*PowerOffTimer add check mediafilesInUse before power off
*Added Opticum Unicable II LNB
*[rc_models] Add sfx6008 remote
*Restore network config before attempting an autoinstall
*Added skin extension to support connected widgets
*Added octagon3 remote controller for Octagon SX888
*Fixed sort for image list in Multiboot list
*[Network] completely rewrite the DNS name server code
*Remove NameserverSetup screen
*Multiboot - order by slots or by mode under blue button
*Allows to delete nameservers in AdapterSetup
*Multiboot - text for blue for order by slots or modes
*Multiboot - allow OpenPli images to participate in a Vu+ Multiboot
*Improve messages Media Scanner/ Hotplug
*Fixed timesync
*Introduce extended info also for iptv in ServiceInfo
*Uclan ustym 4k s2 ott x - initial addition
*Updated support FBC virtual tuners when using a motor
*Gtwebengine: fix hbbtv patch
*Ffmpeg update Version (Cosmetic) 4.4.1 -> 4.4.3
*Gstreamer update -> Version 1.20.5
*Add openresolv to the image to manage resolv.conf
*Umount nfs v4 mounts on shutdown
*Ffmpeg
**Add eac3 (muxer, demuxer, parser)
**Remove not usable h265
**Convert new style
*Openresolv update to version 3.13.1
*Auto install before Auto restore. This solves several issues:
**Packages with conf files will create -opkg files if they already exist when installed
**Packages with runtime dependencies will fail due to missing config
**Packages with enigma config dependencies will fail due to missin config
**Packages without proper conf files no longer have their restored files overwritten
*Added octagon3 remote controller for Octagon SX888
*Network update DNS setup and save
**Remove openresolv removing and code to work without it.Therefore don't write anything in the file /etc/resolv.conf. Use this file only to get DHCP nameservs.
*Multiboot - allow OpenPli images to participate in a Vu+ Multiboot
*Updated support FBC virtual tuners when using a motor. Tuner setting modes "Second cable of motorized LNB", "Additional cable of motorized LNB"
*Some improvements in SoftwareUpdate UpdatePlugin
**Improve imports.
**Move embedded skin to skin_default skin.xml.
**Slider shows the actual progress of the installed packages.
**Uses property for title, text and value.
**Remove instance variables sliderPackages and oktext.
**Print errors in log on exceptions.
*FlashImage: Add option to only download an image and not flash
*Update dB/snr value tuner M1502
*Vu 4K Multiboot: Multiboot can be enabled for Vu '''4K''' devices.
**More at https://forums.openpli.org/topic/94047-vu-4k-multiboot/page-30 and https://github.com/BlackHole/kexec-multiboot/blob/main/README.md
**A wiki page will be added a.s.a.p.

==New hardware support:==
*Octagon SFX6008 WL
*Rtl8818fu driver (sfx6008wl)
*Uclan ustym 4k s2 ott x
*Add another Inverto LNB IDLU-32L412-UNBRR-OPN, Unicable II Programmable 32UB dCSS LNB

==New or improved Plugins and Settings:==
*FileCommander back to e2openplugins repo
*Update enigma2-plugin-extensions-epgimport-rytec.bb.
**Added azman sources
**Replaced Spanish EPG with Koala EPG
*Update ZeroTier to v1.10.2
*Openwebif add sfx60x8
*Added Octagon SFX6018 to OpenWebif
*Add enigmalight recipe
*Add Gerbera to Feed
*Update Xstreamity
*Gerbera update 1.11
*Zerotier fix fetch failure
*Sabnzbd: Update to version 3.7.1
*Kodi update 19.5
*Openwebif added Octagon SX888 4K UHD
*Openwebif added uClan ustym4ktwin
*OpenVpn Update to version 2.6.2
*Kodi update 20
*Sabnzbd: Update to version 3.7.2
*Add serienrecorder
*Add the mtr diagnostic tool to the feed

==Look and feel changes:==
*Add an option to only restore network config
*TimerList add tuner number before tuner type name
*New radio background image

==Driver updates: ==
*Octagon
**Fix screenshot issue for Fhd skin
**Update drivers, fix recovery and multiboot files
*Vuplus Fixed Python3 issue in RemoteControlCode when pressing Green
*qviart fix cp preserve permission error
*octagon Change PAGE+/- to CH+/1 for rcu
*octagon fixed satip channel play issue
*vuplus [BluetoothSetup] updated for 4k models
*Zgemma h8: fix online update for bootmenu
*Octagon fix streaming issues
*Abcom make usb serial driver pl2303 a module
*Gfutures make usb serial driver pl2303 a module
*Maxytec make usb serial driver pl2303 a module
*Gfutures hisilicon: update recovery fastboot and bootargs to the last version
*Maxytec
**Add to nim info "Supports_Blind_Scan"**
**Add display for multiboxpro
**Update to latest fastboot and bootmenu
*Octagon [sfx6008wl] add the rtl8188fu driver to the image, used by the WL model
*Xtrend remove dependency from the old repo for binaries
*Uclan
**Add ustym4ks2ottx box model
**Add demod avl62x1 support
*Fix build with gcc 10+ host compiler (many bsp's)
*Vuplus
**Multiboot - init
** vuduo4k,duo4kse: reintroduce load of wifi driver in init script-needed while booting image from VU+ kexec MB. The script checks if the driver is already loaded and skip loading it, if necessary
*Gigablue Update gb-v3ddriver-gb7252.bb
*Uclan
**Replaced slash screen with the original uClan screen
**Remove the splash logo, we don't overwrite them
*Vuplus
**vuduo4k - vuplus-kexec - update timeout for searching STARTUP_RECOVERY to 4secs
**Vusolo4k: backport mmc patch from 3.14.28-1.10
*Gigablue Remove plugin bluetoothsetup-gb7252 from gb7252 image In the plugin is used the closed-source c library _gbbt, which is not compatible with python3, so the plugin does not work because it calls GSOD
*Gfutures added FTDI_SIO to the HD66SE defconfig
*Qviart
**dual update driver and libraries
**fixed AC3 downmix/passthrough issue : it didn't sound when user AC3 passthrough by HDMI
**added hot key function for new RCU
**fixed 1080p skin issue : it didn't show channel name properly when you move fast
**fixed TXT button issue : box halted when you press TXT button

==Other improvements:==
*Fix build with Ubuntu 23.04

Information for Developers

2023-02-19T13:38:48Z

Tech:

==''''I'm a developer, is there any technical info available from the PLi® team?'''==
Welcome and tell your developer friends about us

Yes and welcome aboard! If you have specific question, you can use our PLi® Third Party Development forum to ask it. You will find we are most accommodating.

This page is about software development using OpenEmbedded-core. If you're looking for the text that used to be on the this page, it's now called developer-information-old.

=='''Create your own build'''==
See also this forum post on setting up a development environment: [http://openpli.org/forums/topic/18806-openpli-quick-setup-ubuntudebian/http://openpli.org/forums/topic/18806-openpli-quick-setup-ubuntudebian/]

Basically, it boils down to this:

Run Linux. Most of us use the latest Ubuntu desktop release, I suggest you do the same, if you don't know what to pick.

Make sure the disk you use for the OE tree supports symbolic links, and you use at least git v1.8.0.

Install prerequisite packages, as described here: [http://www.openembedded.org/wiki/OEandYourDistrohttp://www.openembedded.org/wiki/OEandYourDistro]

For Ubuntu, that's:

sudo apt-get install sed wget cvs subversion git-core \
coreutils unzip texi2html texinfo docbook-utils \
gawk python-pysqlite2 diffstat help2man make gcc build-essential g++ \
desktop-file-utils chrpath default-jre gettext zip libssl-dev

You may need to create a symlink makeinfo->texi2any (in the bin folder) and a symlink makeinfo->/bin/texi2any in the hosttools folder.

For CentOS, that's:

sudo yum install gawk make wget tar bzip2 gzip python unzip perl patch \
diffutils diffstat git cpp gcc gcc-c++ glibc-devel texinfo chrpath socat \
openssl-devel zip python3 perl-Thread-Queue libstdc++-static \
glibc-devel.i686 libgcc.i686 libstdc++-devel.i686

Clone the openpli repository:
git clone https://github.com/OpenPLi/openpli-oe-core.git

or

git clone git@github.com:OpenPLi/openpli-oe-core.git

Setup the environment
cd openpli-oe-core

Select the branch to build from
git checkout develop

Install the required submodules
git submodule update --init --recursive

Build your first image
MACHINE=xxXXXX make image

To find the valid MACHINE=xxXXXX you can have a look at the .conf file in the meta-folder of the manufacturer MMMMM:
cd meta-MMMMM/conf/machine
ls

===Updating===
Before every build, update your cloned git repositories with
cd openpli-oe-core
make update

Note that by default, the develop branch of Enigma is used when you build an image, assuming that most "homebuild" users will want to build the latest development image.

If you want to build a release image, you need to specifcy the correct branch when building:
cd openpli-oe-core
git checkout release-7.2
git submodule update --init --recursive
ENIGMA2_BRANCH=release-7.2 MACHINE=xxXXXX make image

The resulting file will be into:

./openpli-oe-core/build/tmp/deploy/images/xxXXXX/
openpli-homebuild-xxXXXX_usb.zip

=== CentOS incompatibilities ===

Note that CentOS, even CentOS 7, comes with gcc 4, which is pretty old. It is advised to use DevToolsets to switch to 7 or 8:

sudo yum install centos-release-scl devtoolset-7 devtoolset-8

which gives you the option to use versions 6, 7 and 8 as well. You can enable a version using "scl enable devtoolset-8".

When you want to compile OpenPLi-8+ (i.e. an image based on Yocto Zeus or higher), you need at least tar v1.28, but CentOS comes with 1.26, and bitbake refuses to run.

You can address this issue by (as root):
cd /tmp
wget https://rpmfind.net/linux/mageia/distrib/6/x86_64/media/core/release/tar-1.28-3.1.mga5.x86_64.rpm
rpm2cpio tar-1.28-3.1.mga5.x86_64.rpm | cpio -idcmv
cp /tmp/usr/bin/tar /usr/bin

=='''Your own feed server'''==
Once you've built your own image, you'd want to keep it up to date. You can just let the box update itself from your build PC using the GUI as if running a full distro.
To do that, you first need to build the optional packages that go into the feed:
cd openpli-oe-core
MACHINE=xxXXXX make feed

Next, you need to install a webserver of some sort on the build PC, for example Apache2.

As an example, if you've installed apache on Ubuntu, it will share /var/www/html/ with the world. Create a feed subdirectory, and then add a symlink to the "ipk" folder of your build, for example:

sudo mkdir /var/www/html/feeds
sudo ln -s ${HOME}/work/openpli-oe-core/build/tmp/deploy/ipk/ /var/www/html/feeds/openpli-homebuild

To tell your box about this feed location, edit your local.conf or site.conf to contain the following lines:

FEED_NAME = "openpli-homebuild"
DISTRO_HOST = "mybuildpc.local"

After this, if you run a new image build, it will make the /etc/opkg/ files on the box point to your feed. After installing the built image on your box, you should be able to upgrade with opkg commands or the enigma2 GUI.

==='''No real webserver handy?'''===

If you don't have a real webserver, like Apache or Nginx, handy, there are some other options available to serve files via http.

Using PHP 5.4+:
cd /var/www/html/feeds
php -S 0.0.0.0:80

Using Python 2.x:
cd /var/www/html/feeds
python -m SimpleHTTPServer 80

Using Python 3.x:
cd /var/www/html/feeds
python3 -m http.server 80

Using Ruby:
cd /var/www/html/feeds
ruby -rwebrick -e'WEBrick::HTTPServer.new(:Port => 80, :DocumentRoot => Dir.pwd).start'

Using Ruby 1.9.2+:
cd /var/www/html/feeds
ruby -run -ehttpd . -p80

Using Perl:
cpan HTTP::Server::Brick # one-time install of perl dependency
cd /var/www/html/feeds
perl -MHTTP::Server::Brick -e '$s=HTTP::Server::Brick->new(port=>80); $s->mount("/"=>{path=>"."}); $s->start'

Using Busybox HTTPd:
cd /var/www/html/feeds
busybox httpd -f -p 80

NB: For ports below 1024, like the standard HTTP port 80 in the example above, you need root or administrator privileges.

=='''OpenPLi - Git commands'''==
Here is the link to some basic [[git-commands | '''git commands''']].

Softcam/OSCam

2021-06-12T08:29:36Z

Tech:

==What is OScam==
OScam is a softcam, software to be used to decrypt digital television channels on a settopbox (receiver), as an alternative for a conditional access module (CAM). OScam is, compared with other softcams (Cccam, mgcamd, etc.), open source. Hence, the name ''Open Source Conditional Access Module'' (OScam)). OScam is based on the not so well known softcam MpCS. The main features of OScam are next to its softcam capabilities, that it is able to function as a cardserver.

==OScam install==
OScam can be downloaded from the OpenPLi feeds (see also https://wiki.openpli.org/Plugin_Wiki:Information). 
Please note after installation you'll have to activate the softcam also in Menu -> Settings -> Softcam / CI -> Softcam settings.

==OScam config==
You can access OScam through the webinterface <nowiki>"http://ipaddressofyourbox:8081"</nowiki> or edit the files using your favorite remote access program (telnet-SSH-SCP-FTP-etc.) for this you could have a look at our Wiki page [[Tips_and_Tweaks|Tips and Tweaks]]

==Canaal Digitaal or TV Vlaanderen==
If you have a TV Vlaanderen or Canaal Digitaal card the OScam that we compile and is in the OpenPLi feed is already pre-configured for you. After installation (see above) you login the webinterface <nowiki>"http://ipaddressofyourbox:8081"</nowiki> with your favorite browser (Firefox, Chrome, Safari, etc.) and go to the tab '''Readers''' and enable the card by mouse clicking the '''on/off''' button for your card (see picture below) and that should be all.

[[File:OScam-001.png|frameless|Centre|1200px]]

===Manually access your config file===
You can find/place the OScam configuration file into:
/etc/tuxbox/config/oscam/

==OScam removing config files==
By default OpenPLi has the OScam package in the feed configured with a few common readers like for Canaal Digitaal (CD) and TV Vlaanderen (TVV) like in the picture above. When you don't see these, it is because every restore of a backup re-installs your previous readers. Removing your OScam using the plugin manager won't remove your configuration files, that's so made by design.

'''So what to do?'''
----
If you want to remove your current config files and have the OpenPLi configured OScam files and see the readers in the picture above? Well, you have to first remove the installed package using the menu, so go to the plugin manager and remove OScam. Second you have to manually remove a folder
/etc/tuxbox/config/oscam

There are a few ways to do this, manually using putty eg. telnet, or use a FTP program, like Filezilla. When these are not suited for you or your don't know how? Then try the solution below.

===In Windows===
*Be sure to have a OpenPLi [[Backup | Backup]]!
*Uninstall/remove OScam using the [[Plugin_Wiki | plugin manager]] and go to the softcam section.

#In Windows right click on Windows Start button
#Select Run or in Dutch Uitvoeren
#Enter the //the-ipaddress-of-your-box
##Example so like:
#: //192.168.100.10
#Choose the root folder
#Now go to
#: /etc/tuxbox/config
#Now you should see the oscam folder
#delete the folder oscam
#reboot/restart your receiver
#After a restart go to the plugin manager and install OScam
#After installation the readers created by OpenPLi should be there (like in the picture above)and select the one your need (see above)
#There is one thing to do!!
#Make a manual backup with [[Backup/AutoBackup | AutoBackup]] , so when you suddenly have to restore to replace the "old" config files in the last backup you made.

==Updates==
The OScam version will only be updated when there is a reason for it, so when you see you're not running the latest update, there is no reason for it. Of course you can always compile a new version yourself, see the developers site below.

==Internal cardshare==
In OpenPLi the softcam OScam is already set/configurated to do an internal cardshare between 2 boxes. By default OScam is configured to connect 2 boxes with "Mainreceiver" becoming the server and the “2nd_box” becoming the client (OSCam terminology calls this the reader).
As the developers of OpenPLi don’t know which box you want to be the Mainreceiver and which one becomes the 2nd_box, OScam is configured for both.
So you'll have to do 2 things on the one which becomes “2nd_box“ (OScam terminology calls this the reader).

===Preparations===
Both boxes have to be in the same network.
You have to know the IP address of the Mainreceiver.

===Mainreceiver===
----
This will be your server for the client “2nd_box”. On this one you don’t have to do anything, as there is already a user “2nd_box” which has access with the password “2nd_box”.

===2nd_box===
----
This box is the client and it will login on the Mainreceiver using a "reader", let’s say to read the data it needs. All you’ll have to do is to enter the IP address of the Mainreceiver and start the Reader.

Login into OScam on the box which will be the 2nd_box, by using your favorite browser, eg. Iceweasel-Firefox-Opera-Chrome-Internet Explorer or Microsoft Edge and enter <nowiki>http://ipadres_of_the_2nd_box:8081</nowiki> , so you can configure it properly.

#Go to the Readers TAB and click on the red pencil in the line of the Mainreceiver.
#A window will open , then you go to the line that says Device.
#On this line there is “ip_adress_mainreceiver,12005".
#Here you have to enter the IP address of the Mainreceiver instead of the text.
#Now go the bottom of the screen and click the save button.
#Now click on the Readers TAB on top of the screen.
#Then on the line Mainreceiver click on the On/Off button on the screen. By clicking it the button should go from grey to green.

It all should work like instant. Yet, to be on the safe side, you could restart the Mainreceiver and the 2nd_box.

==NL: Use with Ziggo Irdeto cards==
If you are using Ziggo Irdeto cards it will work after doing the following:
#Open in a editor the file \\ipofyourbox\root\etc\tuxbox\config\oscam\oscam.server (or add the keys in the reader section of the OScam webinterface using the pencil in the reader)
#Add the following rules in the section reader of the reader that contains the Ziggo card (or both): boxkey = please Google this generic key for Ziggo and rsakey = please Google this generic key for Ziggo
#Save the config and it should work
Note: Unfortunately this doesn't work with Ziggo Nagra cards as these cards are linked to the boxkey which is unique to the reciever you got from Ziggo. As long as you dont know this key the smartcard can't be used by OScam.

==OSCam Tuning (Mapping)==

'''Please, keep in mind use at own risk!'''

Edit all oscam.conf files with a simple text editor like kate/vim/notepad++, don't use wordpad or other windows badness

Restart the softcam after changing your config files by pressing '''Menu''' on remote control and navigate to: '''Setup > SoftCam/CI > Softcam setup... > Select softcam >''' (press left or right to select) '''oscam >''' press '''green button'''(ok).

'''Mapping'''

This mapping method will work for BE and NL seca cards.

Make sure you are using '''dvbapi request mode 1 (try all CAID simulataneously)'''

'''the dvbapi file is located in /etc/tuxbox/config/oscam/oscam.dvbapi'''

Add (or edit) two lines to the oscam.dvbapi file

M: 1817:00006A 0100:00006A
M: 1818:00006C 0100:00006C

'''oscam.server''' ratelimitecm and ratelimitseconds settings explained

This is setting crucial for performing home card sharing SECA cards of the M7 media group.
If this is setting is set wrong, the picture will result in frozen images, this is caused by bad decrypt keys (control words) from the smartcard also known as penalty mode.

Until now ratelimitecm have to be set to 4 (default setting if you use the oscam versions from the feeds), because you are not able to decode more than 4 channels continuously.

For ratelimitseconds it is known that values from 8 seconds and lower result in bad decode keys.
Further, it is also known that if ratelimitseconds is larger or equal to 11
seconds, you can zap you channels and keep a decoded tv image.
----

==There is a official website of the developers of OScam==
To go to official developers board http://www.streamboard.tv/wbb2/portal.php

To go to official OSCam wiki. http://www.streamboard.tv/wiki/index.php/OSCam/en

To see an overview of the last changes. https://trac.streamboard.tv/oscam/timeline

Softcam/OSCam

2021-06-12T08:28:23Z

Tech: /* OSCam Tuning (Mapping) */

==What is OScam==
OScam is a softcam, software to be used to decrypt digital television channels on a settopbox (receiver), as an alternative for a conditional access module (CAM). OScam is, compared with other softcams (Cccam, mgcamd, etc.), open source. Hence, the name ''Open Source Conditional Access Module'' (OScam)). OScam is based on the not so well known softcam MpCS. The main features of OScam are next to its softcam capabilities, that it is able to function as a cardserver.

==OScam install==
OScam can be downloaded from the OpenPLi feeds (see also https://wiki.openpli.org/Plugin_Wiki:Information). 
Please note after installation you'll have to activate the softcam also in Menu -> Settings -> Softcam / CI -> Softcam settings.

==OScam config==
You can access OScam through the webinterface <nowiki>"http://ipaddressofyourbox:8081"</nowiki> or edit the files using your favorite remote access program (telnet-SSH-SCP-FTP-etc.) for this you could have a look at our Wiki page [[Tips_and_Tweaks|Tips and Tweaks]]

==Canaal Digitaal or TV Vlaanderen==
If you have a TV Vlaanderen or Canaal Digitaal card the OScam that we compile and is in the OpenPLi feed is already pre-configured for you. After installation (see above) you login the webinterface <nowiki>"http://ipaddressofyourbox:8081"</nowiki> with your favorite browser (Firefox, Chrome, Safari, etc.) and go to the tab '''Readers''' and enable the card by mouse clicking the '''on/off''' button for your card (see picture below) and that should be all.

[[File:OScam-001.png|frameless|Centre|1200px]]

===Manually access your config file===
You can find/place the OScam configuration file into:
/etc/tuxbox/config/oscam/

==OScam removing config files==
By default OpenPLi has the OScam package in the feed configured with a few common readers like for Canaal Digitaal (CD) and TV Vlaanderen (TVV) like in the picture above. When you don't see these, it is because every restore of a backup re-installs your previous readers. Removing your OScam using the plugin manager won't remove your configuration files, that's so made by design.

'''So what to do?'''
----
If you want to remove your current config files and have the OpenPLi configured OScam files and see the readers in the picture above? Well, you have to first remove the installed package using the menu, so go to the plugin manager and remove OScam. Second you have to manually remove a folder
/etc/tuxbox/config/oscam

There are a few ways to do this, manually using putty eg. telnet, or use a FTP program, like Filezilla. When these are not suited for you or your don't know how? Then try the solution below.

===In Windows===
*Be sure to have a OpenPLi [[Backup | Backup]]!
*Uninstall/remove OScam using the [[Plugin_Wiki | plugin manager]] and go to the softcam section.

#In Windows right click on Windows Start button
#Select Run or in Dutch Uitvoeren
#Enter the //the-ipaddress-of-your-box
##Example so like:
#: //192.168.100.10
#Choose the root folder
#Now go to
#: /etc/tuxbox/config
#Now you should see the oscam folder
#delete the folder oscam
#reboot/restart your receiver
#After a restart go to the plugin manager and install OScam
#After installation the readers created by OpenPLi should be there (like in the picture above)and select the one your need (see above)
#There is one thing to do!!
#Make a manual backup with [[Backup/AutoBackup | AutoBackup]] , so when you suddenly have to restore to replace the "old" config files in the last backup you made.

==Updates==
The OScam version will only be updated when there is a reason for it, so when you see you're not running the latest update, there is no reason for it. Of course you can always compile a new version yourself, see the developers site below.

==Internal cardshare==
In OpenPLi the softcam OScam is already set/configurated to do an internal cardshare between 2 boxes. By default OScam is configured to connect 2 boxes with "Mainreceiver" becoming the server and the “2nd_box” becoming the client (OSCam terminology calls this the reader).
As the developers of OpenPLi don’t know which box you want to be the Mainreceiver and which one becomes the 2nd_box, OScam is configured for both.
So you'll have to do 2 things on the one which becomes “2nd_box“ (OScam terminology calls this the reader).

===Preparations===
Both boxes have to be in the same network.
You have to know the IP address of the Mainreceiver.

===Mainreceiver===
----
This will be your server for the client “2nd_box”. On this one you don’t have to do anything, as there is already a user “2nd_box” which has access with the password “2nd_box”.

===2nd_box===
----
This box is the client and it will login on the Mainreceiver using a "reader", let’s say to read the data it needs. All you’ll have to do is to enter the IP address of the Mainreceiver and start the Reader.

Login into OScam on the box which will be the 2nd_box, by using your favorite browser, eg. Iceweasel-Firefox-Opera-Chrome-Internet Explorer or Microsoft Edge and enter <nowiki>http://ipadres_of_the_2nd_box:8081</nowiki> , so you can configure it properly.

#Go to the Readers TAB and click on the red pencil in the line of the Mainreceiver.
#A window will open , then you go to the line that says Device.
#On this line there is “ip_adress_mainreceiver,12005".
#Here you have to enter the IP address of the Mainreceiver instead of the text.
#Now go the bottom of the screen and click the save button.
#Now click on the Readers TAB on top of the screen.
#Then on the line Mainreceiver click on the On/Off button on the screen. By clicking it the button should go from grey to green.

It all should work like instant. Yet, to be on the safe side, you could restart the Mainreceiver and the 2nd_box.

==NL: Use with Ziggo Irdeto cards==
If you are using Ziggo Irdeto cards it will work after doing the following:
#Open in a editor the file \\ipofyourbox\root\etc\tuxbox\config\oscam\oscam.server (or add the keys in the reader section of the OScam webinterface using the pencil in the reader)
#Add the following rules in the section reader of the reader that contains the Ziggo card (or both): boxkey = please Google this generic key for Ziggo and rsakey = please Google this generic key for Ziggo
#Save the config and it should work
Note: Unfortunately this doesn't work with Ziggo Nagra cards as these cards are linked to the boxkey which is unique to the reciever you got from Ziggo. As long as you dont know this key the smartcard can't be used by OScam.

==There is a official website of the developers of OScam==
To go to official developers board http://www.streamboard.tv/wbb2/portal.php

To go to official OSCam wiki. http://www.streamboard.tv/wiki/index.php/OSCam/en

To see an overview of the last changes. https://trac.streamboard.tv/oscam/timeline

==OSCam Tuning (Mapping)==

'''Please, keep in mind use at own risk!'''

Edit all oscam.conf files with a simple text editor like kate/vim/notepad++, don't use wordpad or other windows badness

Restart the softcam after changing your config files by pressing '''Menu''' on remote control and navigate to: '''Setup > SoftCam/CI > Softcam setup... > Select softcam >''' (press left or right to select) '''oscam >''' press '''green button'''(ok).

'''Mapping'''

This mapping method will work for BE and NL seca cards.

Make sure you are using '''dvbapi request mode 1 (try all CAID simulataneously)'''

'''the dvbapi file is located in /etc/tuxbox/config/oscam/oscam.dvbapi'''

Add (or edit) two lines to the oscam.dvbapi file

M: 1817:00006A 0100:00006A
M: 1818:00006C 0100:00006C

'''oscam.server''' ratelimitecm and ratelimitseconds settings explained

This is setting crucial for performing home card sharing SECA cards of the M7 media group.
If this is setting is set wrong, the picture will result in frozen images, this is caused by bad decrypt keys (control words) from the smartcard also known as penalty mode.

Until now ratelimitecm have to be set to 4 (default setting if you use the oscam versions from the feeds), because you are not able to decode more than 4 channels continuously.

For ratelimitseconds it is known that values from 8 seconds and lower result in bad decode keys.
Further, it is also known that if ratelimitseconds is larger or equal to 11
seconds, you can zap you channels and keep a decoded tv image.

----

Softcam/OSCam

2021-06-12T08:25:39Z

Tech: /* OSCam Tuning (Mapping) */

==What is OScam==
OScam is a softcam, software to be used to decrypt digital television channels on a settopbox (receiver), as an alternative for a conditional access module (CAM). OScam is, compared with other softcams (Cccam, mgcamd, etc.), open source. Hence, the name ''Open Source Conditional Access Module'' (OScam)). OScam is based on the not so well known softcam MpCS. The main features of OScam are next to its softcam capabilities, that it is able to function as a cardserver.

==OScam install==
OScam can be downloaded from the OpenPLi feeds (see also https://wiki.openpli.org/Plugin_Wiki:Information). 
Please note after installation you'll have to activate the softcam also in Menu -> Settings -> Softcam / CI -> Softcam settings.

==OScam config==
You can access OScam through the webinterface <nowiki>"http://ipaddressofyourbox:8081"</nowiki> or edit the files using your favorite remote access program (telnet-SSH-SCP-FTP-etc.) for this you could have a look at our Wiki page [[Tips_and_Tweaks|Tips and Tweaks]]

==Canaal Digitaal or TV Vlaanderen==
If you have a TV Vlaanderen or Canaal Digitaal card the OScam that we compile and is in the OpenPLi feed is already pre-configured for you. After installation (see above) you login the webinterface <nowiki>"http://ipaddressofyourbox:8081"</nowiki> with your favorite browser (Firefox, Chrome, Safari, etc.) and go to the tab '''Readers''' and enable the card by mouse clicking the '''on/off''' button for your card (see picture below) and that should be all.

[[File:OScam-001.png|frameless|Centre|1200px]]

===Manually access your config file===
You can find/place the OScam configuration file into:
/etc/tuxbox/config/oscam/

==OScam removing config files==
By default OpenPLi has the OScam package in the feed configured with a few common readers like for Canaal Digitaal (CD) and TV Vlaanderen (TVV) like in the picture above. When you don't see these, it is because every restore of a backup re-installs your previous readers. Removing your OScam using the plugin manager won't remove your configuration files, that's so made by design.

'''So what to do?'''
----
If you want to remove your current config files and have the OpenPLi configured OScam files and see the readers in the picture above? Well, you have to first remove the installed package using the menu, so go to the plugin manager and remove OScam. Second you have to manually remove a folder
/etc/tuxbox/config/oscam

There are a few ways to do this, manually using putty eg. telnet, or use a FTP program, like Filezilla. When these are not suited for you or your don't know how? Then try the solution below.

===In Windows===
*Be sure to have a OpenPLi [[Backup | Backup]]!
*Uninstall/remove OScam using the [[Plugin_Wiki | plugin manager]] and go to the softcam section.

#In Windows right click on Windows Start button
#Select Run or in Dutch Uitvoeren
#Enter the //the-ipaddress-of-your-box
##Example so like:
#: //192.168.100.10
#Choose the root folder
#Now go to
#: /etc/tuxbox/config
#Now you should see the oscam folder
#delete the folder oscam
#reboot/restart your receiver
#After a restart go to the plugin manager and install OScam
#After installation the readers created by OpenPLi should be there (like in the picture above)and select the one your need (see above)
#There is one thing to do!!
#Make a manual backup with [[Backup/AutoBackup | AutoBackup]] , so when you suddenly have to restore to replace the "old" config files in the last backup you made.

==Updates==
The OScam version will only be updated when there is a reason for it, so when you see you're not running the latest update, there is no reason for it. Of course you can always compile a new version yourself, see the developers site below.

==Internal cardshare==
In OpenPLi the softcam OScam is already set/configurated to do an internal cardshare between 2 boxes. By default OScam is configured to connect 2 boxes with "Mainreceiver" becoming the server and the “2nd_box” becoming the client (OSCam terminology calls this the reader).
As the developers of OpenPLi don’t know which box you want to be the Mainreceiver and which one becomes the 2nd_box, OScam is configured for both.
So you'll have to do 2 things on the one which becomes “2nd_box“ (OScam terminology calls this the reader).

===Preparations===
Both boxes have to be in the same network.
You have to know the IP address of the Mainreceiver.

===Mainreceiver===
----
This will be your server for the client “2nd_box”. On this one you don’t have to do anything, as there is already a user “2nd_box” which has access with the password “2nd_box”.

===2nd_box===
----
This box is the client and it will login on the Mainreceiver using a "reader", let’s say to read the data it needs. All you’ll have to do is to enter the IP address of the Mainreceiver and start the Reader.

Login into OScam on the box which will be the 2nd_box, by using your favorite browser, eg. Iceweasel-Firefox-Opera-Chrome-Internet Explorer or Microsoft Edge and enter <nowiki>http://ipadres_of_the_2nd_box:8081</nowiki> , so you can configure it properly.

#Go to the Readers TAB and click on the red pencil in the line of the Mainreceiver.
#A window will open , then you go to the line that says Device.
#On this line there is “ip_adress_mainreceiver,12005".
#Here you have to enter the IP address of the Mainreceiver instead of the text.
#Now go the bottom of the screen and click the save button.
#Now click on the Readers TAB on top of the screen.
#Then on the line Mainreceiver click on the On/Off button on the screen. By clicking it the button should go from grey to green.

It all should work like instant. Yet, to be on the safe side, you could restart the Mainreceiver and the 2nd_box.

==NL: Use with Ziggo Irdeto cards==
If you are using Ziggo Irdeto cards it will work after doing the following:
#Open in a editor the file \\ipofyourbox\root\etc\tuxbox\config\oscam\oscam.server (or add the keys in the reader section of the OScam webinterface using the pencil in the reader)
#Add the following rules in the section reader of the reader that contains the Ziggo card (or both): boxkey = please Google this generic key for Ziggo and rsakey = please Google this generic key for Ziggo
#Save the config and it should work
Note: Unfortunately this doesn't work with Ziggo Nagra cards as these cards are linked to the boxkey which is unique to the reciever you got from Ziggo. As long as you dont know this key the smartcard can't be used by OScam.

==There is a official website of the developers of OScam==
To go to official developers board http://www.streamboard.tv/wbb2/portal.php

To go to official OSCam wiki. http://www.streamboard.tv/wiki/index.php/OSCam/en

To see an overview of the last changes. https://trac.streamboard.tv/oscam/timeline

==OSCam Tuning (Mapping)==

'''Please, keep in mind use at own risk!'''

Edit all oscam.conf files with a simple text editor like kate/vim/notepad++, don't use wordpad or other windows badness

Restart the softcam after changing your config files by pressing '''Menu''' on remote control and navigate to: '''Setup > SoftCam/CI > Softcam setup... > Select softcam >''' (press left or right to select) '''oscam >''' press '''green button'''(ok).

'''Mapping'''

This mapping method will work for BE and NL seca cards.

Make sure you are using '''dvbapi request mode 1 (try all CAID simulataneously)'''

'''the dvbapi file is located in /etc/tuxbox/config/oscam/oscam.dvbapi'''

Add (or edit) two lines to the oscam.dvbapi file

M: 1817:00006A 0100:00006A
M: 1818:00006C 0100:00006C

'''oscam.server ratelimitecm and ratelimitseconds'''

This is setting crucial for performing home card sharing SECA cards of the M7 media group.
If this is setting is set wrong, the picture will result in frozen images, this is caused by bad decrypt keys (control words) from the smartcard also known as penalty mode.

Until now ratelimitecm have to be set to 4, because you are not able to decode more than 4 channels continuously.
For ratelimitseconds it is known that values from 8 seconds and lower result in bad decode keys. Further, it is also known that if ratelimitseconds is larger or equal to 11
seconds, you can zap you channels and keep a decoded tv image.

----

Softcam/OSCam

2021-06-12T08:25:19Z

Tech: /* OSCam Tuning (Mapping) */

==What is OScam==
OScam is a softcam, software to be used to decrypt digital television channels on a settopbox (receiver), as an alternative for a conditional access module (CAM). OScam is, compared with other softcams (Cccam, mgcamd, etc.), open source. Hence, the name ''Open Source Conditional Access Module'' (OScam)). OScam is based on the not so well known softcam MpCS. The main features of OScam are next to its softcam capabilities, that it is able to function as a cardserver.

==OScam install==
OScam can be downloaded from the OpenPLi feeds (see also https://wiki.openpli.org/Plugin_Wiki:Information). 
Please note after installation you'll have to activate the softcam also in Menu -> Settings -> Softcam / CI -> Softcam settings.

==OScam config==
You can access OScam through the webinterface <nowiki>"http://ipaddressofyourbox:8081"</nowiki> or edit the files using your favorite remote access program (telnet-SSH-SCP-FTP-etc.) for this you could have a look at our Wiki page [[Tips_and_Tweaks|Tips and Tweaks]]

==Canaal Digitaal or TV Vlaanderen==
If you have a TV Vlaanderen or Canaal Digitaal card the OScam that we compile and is in the OpenPLi feed is already pre-configured for you. After installation (see above) you login the webinterface <nowiki>"http://ipaddressofyourbox:8081"</nowiki> with your favorite browser (Firefox, Chrome, Safari, etc.) and go to the tab '''Readers''' and enable the card by mouse clicking the '''on/off''' button for your card (see picture below) and that should be all.

[[File:OScam-001.png|frameless|Centre|1200px]]

===Manually access your config file===
You can find/place the OScam configuration file into:
/etc/tuxbox/config/oscam/

==OScam removing config files==
By default OpenPLi has the OScam package in the feed configured with a few common readers like for Canaal Digitaal (CD) and TV Vlaanderen (TVV) like in the picture above. When you don't see these, it is because every restore of a backup re-installs your previous readers. Removing your OScam using the plugin manager won't remove your configuration files, that's so made by design.

'''So what to do?'''
----
If you want to remove your current config files and have the OpenPLi configured OScam files and see the readers in the picture above? Well, you have to first remove the installed package using the menu, so go to the plugin manager and remove OScam. Second you have to manually remove a folder
/etc/tuxbox/config/oscam

There are a few ways to do this, manually using putty eg. telnet, or use a FTP program, like Filezilla. When these are not suited for you or your don't know how? Then try the solution below.

===In Windows===
*Be sure to have a OpenPLi [[Backup | Backup]]!
*Uninstall/remove OScam using the [[Plugin_Wiki | plugin manager]] and go to the softcam section.

#In Windows right click on Windows Start button
#Select Run or in Dutch Uitvoeren
#Enter the //the-ipaddress-of-your-box
##Example so like:
#: //192.168.100.10
#Choose the root folder
#Now go to
#: /etc/tuxbox/config
#Now you should see the oscam folder
#delete the folder oscam
#reboot/restart your receiver
#After a restart go to the plugin manager and install OScam
#After installation the readers created by OpenPLi should be there (like in the picture above)and select the one your need (see above)
#There is one thing to do!!
#Make a manual backup with [[Backup/AutoBackup | AutoBackup]] , so when you suddenly have to restore to replace the "old" config files in the last backup you made.

==Updates==
The OScam version will only be updated when there is a reason for it, so when you see you're not running the latest update, there is no reason for it. Of course you can always compile a new version yourself, see the developers site below.

==Internal cardshare==
In OpenPLi the softcam OScam is already set/configurated to do an internal cardshare between 2 boxes. By default OScam is configured to connect 2 boxes with "Mainreceiver" becoming the server and the “2nd_box” becoming the client (OSCam terminology calls this the reader).
As the developers of OpenPLi don’t know which box you want to be the Mainreceiver and which one becomes the 2nd_box, OScam is configured for both.
So you'll have to do 2 things on the one which becomes “2nd_box“ (OScam terminology calls this the reader).

===Preparations===
Both boxes have to be in the same network.
You have to know the IP address of the Mainreceiver.

===Mainreceiver===
----
This will be your server for the client “2nd_box”. On this one you don’t have to do anything, as there is already a user “2nd_box” which has access with the password “2nd_box”.

===2nd_box===
----
This box is the client and it will login on the Mainreceiver using a "reader", let’s say to read the data it needs. All you’ll have to do is to enter the IP address of the Mainreceiver and start the Reader.

Login into OScam on the box which will be the 2nd_box, by using your favorite browser, eg. Iceweasel-Firefox-Opera-Chrome-Internet Explorer or Microsoft Edge and enter <nowiki>http://ipadres_of_the_2nd_box:8081</nowiki> , so you can configure it properly.

#Go to the Readers TAB and click on the red pencil in the line of the Mainreceiver.
#A window will open , then you go to the line that says Device.
#On this line there is “ip_adress_mainreceiver,12005".
#Here you have to enter the IP address of the Mainreceiver instead of the text.
#Now go the bottom of the screen and click the save button.
#Now click on the Readers TAB on top of the screen.
#Then on the line Mainreceiver click on the On/Off button on the screen. By clicking it the button should go from grey to green.

It all should work like instant. Yet, to be on the safe side, you could restart the Mainreceiver and the 2nd_box.

==NL: Use with Ziggo Irdeto cards==
If you are using Ziggo Irdeto cards it will work after doing the following:
#Open in a editor the file \\ipofyourbox\root\etc\tuxbox\config\oscam\oscam.server (or add the keys in the reader section of the OScam webinterface using the pencil in the reader)
#Add the following rules in the section reader of the reader that contains the Ziggo card (or both): boxkey = please Google this generic key for Ziggo and rsakey = please Google this generic key for Ziggo
#Save the config and it should work
Note: Unfortunately this doesn't work with Ziggo Nagra cards as these cards are linked to the boxkey which is unique to the reciever you got from Ziggo. As long as you dont know this key the smartcard can't be used by OScam.

==There is a official website of the developers of OScam==
To go to official developers board http://www.streamboard.tv/wbb2/portal.php

To go to official OSCam wiki. http://www.streamboard.tv/wiki/index.php/OSCam/en

To see an overview of the last changes. https://trac.streamboard.tv/oscam/timeline

==OSCam Tuning (Mapping)==

'''Please, keep in mind use at own risk!'''

Edit all oscam.conf files with a simple text editor like kate/vim/notepad++, don't use wordpad or other windows badness

Restart the softcam after changing your config files by pressing '''Menu''' on remote control and navigate to: '''Setup > SoftCam/CI > Softcam setup... > Select softcam >''' (press left or right to select) '''oscam >''' press '''green button'''(ok).

'''Mapping'''

This mapping method will work for BE and NL seca cards.

Make sure you are using '''dvbapi request mode 1 (try all CAID simulataneously)'''

'''the dvbapi file is located in /etc/tuxbox/config/oscam/oscam.dvbapi'''
Add (or edit) two lines to the oscam.dvbapi file

M: 1817:00006A 0100:00006A
M: 1818:00006C 0100:00006C

'''oscam.server ratelimitecm and ratelimitseconds'''

This is setting crucial for performing home card sharing SECA cards of the M7 media group.
If this is setting is set wrong, the picture will result in frozen images, this is caused by bad decrypt keys (control words) from the smartcard also known as penalty mode.

Until now ratelimitecm have to be set to 4, because you are not able to decode more than 4 channels continuously.
For ratelimitseconds it is known that values from 8 seconds and lower result in bad decode keys. Further, it is also known that if ratelimitseconds is larger or equal to 11
seconds, you can zap you channels and keep a decoded tv image.

----

Softcam/OSCam

2021-06-12T08:23:27Z

Tech: /* OSCam Tuning (Mapping) */

==What is OScam==
OScam is a softcam, software to be used to decrypt digital television channels on a settopbox (receiver), as an alternative for a conditional access module (CAM). OScam is, compared with other softcams (Cccam, mgcamd, etc.), open source. Hence, the name ''Open Source Conditional Access Module'' (OScam)). OScam is based on the not so well known softcam MpCS. The main features of OScam are next to its softcam capabilities, that it is able to function as a cardserver.

==OScam install==
OScam can be downloaded from the OpenPLi feeds (see also https://wiki.openpli.org/Plugin_Wiki:Information). 
Please note after installation you'll have to activate the softcam also in Menu -> Settings -> Softcam / CI -> Softcam settings.

==OScam config==
You can access OScam through the webinterface <nowiki>"http://ipaddressofyourbox:8081"</nowiki> or edit the files using your favorite remote access program (telnet-SSH-SCP-FTP-etc.) for this you could have a look at our Wiki page [[Tips_and_Tweaks|Tips and Tweaks]]

==Canaal Digitaal or TV Vlaanderen==
If you have a TV Vlaanderen or Canaal Digitaal card the OScam that we compile and is in the OpenPLi feed is already pre-configured for you. After installation (see above) you login the webinterface <nowiki>"http://ipaddressofyourbox:8081"</nowiki> with your favorite browser (Firefox, Chrome, Safari, etc.) and go to the tab '''Readers''' and enable the card by mouse clicking the '''on/off''' button for your card (see picture below) and that should be all.

[[File:OScam-001.png|frameless|Centre|1200px]]

===Manually access your config file===
You can find/place the OScam configuration file into:
/etc/tuxbox/config/oscam/

==OScam removing config files==
By default OpenPLi has the OScam package in the feed configured with a few common readers like for Canaal Digitaal (CD) and TV Vlaanderen (TVV) like in the picture above. When you don't see these, it is because every restore of a backup re-installs your previous readers. Removing your OScam using the plugin manager won't remove your configuration files, that's so made by design.

'''So what to do?'''
----
If you want to remove your current config files and have the OpenPLi configured OScam files and see the readers in the picture above? Well, you have to first remove the installed package using the menu, so go to the plugin manager and remove OScam. Second you have to manually remove a folder
/etc/tuxbox/config/oscam

There are a few ways to do this, manually using putty eg. telnet, or use a FTP program, like Filezilla. When these are not suited for you or your don't know how? Then try the solution below.

===In Windows===
*Be sure to have a OpenPLi [[Backup | Backup]]!
*Uninstall/remove OScam using the [[Plugin_Wiki | plugin manager]] and go to the softcam section.

#In Windows right click on Windows Start button
#Select Run or in Dutch Uitvoeren
#Enter the //the-ipaddress-of-your-box
##Example so like:
#: //192.168.100.10
#Choose the root folder
#Now go to
#: /etc/tuxbox/config
#Now you should see the oscam folder
#delete the folder oscam
#reboot/restart your receiver
#After a restart go to the plugin manager and install OScam
#After installation the readers created by OpenPLi should be there (like in the picture above)and select the one your need (see above)
#There is one thing to do!!
#Make a manual backup with [[Backup/AutoBackup | AutoBackup]] , so when you suddenly have to restore to replace the "old" config files in the last backup you made.

==Updates==
The OScam version will only be updated when there is a reason for it, so when you see you're not running the latest update, there is no reason for it. Of course you can always compile a new version yourself, see the developers site below.

==Internal cardshare==
In OpenPLi the softcam OScam is already set/configurated to do an internal cardshare between 2 boxes. By default OScam is configured to connect 2 boxes with "Mainreceiver" becoming the server and the “2nd_box” becoming the client (OSCam terminology calls this the reader).
As the developers of OpenPLi don’t know which box you want to be the Mainreceiver and which one becomes the 2nd_box, OScam is configured for both.
So you'll have to do 2 things on the one which becomes “2nd_box“ (OScam terminology calls this the reader).

===Preparations===
Both boxes have to be in the same network.
You have to know the IP address of the Mainreceiver.

===Mainreceiver===
----
This will be your server for the client “2nd_box”. On this one you don’t have to do anything, as there is already a user “2nd_box” which has access with the password “2nd_box”.

===2nd_box===
----
This box is the client and it will login on the Mainreceiver using a "reader", let’s say to read the data it needs. All you’ll have to do is to enter the IP address of the Mainreceiver and start the Reader.

Login into OScam on the box which will be the 2nd_box, by using your favorite browser, eg. Iceweasel-Firefox-Opera-Chrome-Internet Explorer or Microsoft Edge and enter <nowiki>http://ipadres_of_the_2nd_box:8081</nowiki> , so you can configure it properly.

#Go to the Readers TAB and click on the red pencil in the line of the Mainreceiver.
#A window will open , then you go to the line that says Device.
#On this line there is “ip_adress_mainreceiver,12005".
#Here you have to enter the IP address of the Mainreceiver instead of the text.
#Now go the bottom of the screen and click the save button.
#Now click on the Readers TAB on top of the screen.
#Then on the line Mainreceiver click on the On/Off button on the screen. By clicking it the button should go from grey to green.

It all should work like instant. Yet, to be on the safe side, you could restart the Mainreceiver and the 2nd_box.

==NL: Use with Ziggo Irdeto cards==
If you are using Ziggo Irdeto cards it will work after doing the following:
#Open in a editor the file \\ipofyourbox\root\etc\tuxbox\config\oscam\oscam.server (or add the keys in the reader section of the OScam webinterface using the pencil in the reader)
#Add the following rules in the section reader of the reader that contains the Ziggo card (or both): boxkey = please Google this generic key for Ziggo and rsakey = please Google this generic key for Ziggo
#Save the config and it should work
Note: Unfortunately this doesn't work with Ziggo Nagra cards as these cards are linked to the boxkey which is unique to the reciever you got from Ziggo. As long as you dont know this key the smartcard can't be used by OScam.

==There is a official website of the developers of OScam==
To go to official developers board http://www.streamboard.tv/wbb2/portal.php

To go to official OSCam wiki. http://www.streamboard.tv/wiki/index.php/OSCam/en

To see an overview of the last changes. https://trac.streamboard.tv/oscam/timeline

==OSCam Tuning (Mapping)==

'''Please, keep in mind use at own risk!'''

Edit all oscam.conf files with a simple text editor like kate/vim/notepad++, don't use wordpad or other windows badness

Restart the softcam after changing your config files by pressing '''Menu''' on remote control and navigate to: '''Setup > SoftCam/CI > Softcam setup... > Select softcam >''' (press left or right to select) '''oscam >''' press '''green button'''(ok).

'''Mapping'''

This mapping method will work for BE and NL seca cards.

Make sure you are using '''dvbapi request mode 1 (try all CAID simulataneously)'''

'''the dvbapi file is located in /etc/tuxbox/config/oscam/oscam.dvbapi'''

M: 1817:00006A 0100:00006A
M: 1818:00006C 0100:00006C

'''oscam.server ratelimitecm and ratelimitseconds'''

This is setting crucial for performing home card sharing SECA cards of the M7 media group.
If this is setting is set wrong, the picture will result in frozen images, this is caused by bad decrypt keys (control words) from the smartcard also known as penalty mode.

Until now ratelimitecm have to be set to 4, because you are not able to decode more than 4 channels continuously.
For ratelimitseconds it is known that values from 8 seconds and lower result in bad decode keys. Further, it is also known that if ratelimitseconds is larger or equal to 11
seconds, you can zap you channels and keep a decoded tv image.

----

Softcam/OSCam

2021-06-12T08:13:05Z

Tech: /* OSCam Tuning (MAPPING) */

==What is OScam==
OScam is a softcam, software to be used to decrypt digital television channels on a settopbox (receiver), as an alternative for a conditional access module (CAM). OScam is, compared with other softcams (Cccam, mgcamd, etc.), open source. Hence, the name ''Open Source Conditional Access Module'' (OScam)). OScam is based on the not so well known softcam MpCS. The main features of OScam are next to its softcam capabilities, that it is able to function as a cardserver.

==OScam install==
OScam can be downloaded from the OpenPLi feeds (see also https://wiki.openpli.org/Plugin_Wiki:Information). 
Please note after installation you'll have to activate the softcam also in Menu -> Settings -> Softcam / CI -> Softcam settings.

==OScam config==
You can access OScam through the webinterface <nowiki>"http://ipaddressofyourbox:8081"</nowiki> or edit the files using your favorite remote access program (telnet-SSH-SCP-FTP-etc.) for this you could have a look at our Wiki page [[Tips_and_Tweaks|Tips and Tweaks]]

==Canaal Digitaal or TV Vlaanderen==
If you have a TV Vlaanderen or Canaal Digitaal card the OScam that we compile and is in the OpenPLi feed is already pre-configured for you. After installation (see above) you login the webinterface <nowiki>"http://ipaddressofyourbox:8081"</nowiki> with your favorite browser (Firefox, Chrome, Safari, etc.) and go to the tab '''Readers''' and enable the card by mouse clicking the '''on/off''' button for your card (see picture below) and that should be all.

[[File:OScam-001.png|frameless|Centre|1200px]]

===Manually access your config file===
You can find/place the OScam configuration file into:
/etc/tuxbox/config/oscam/

==OScam removing config files==
By default OpenPLi has the OScam package in the feed configured with a few common readers like for Canaal Digitaal (CD) and TV Vlaanderen (TVV) like in the picture above. When you don't see these, it is because every restore of a backup re-installs your previous readers. Removing your OScam using the plugin manager won't remove your configuration files, that's so made by design.

'''So what to do?'''
----
If you want to remove your current config files and have the OpenPLi configured OScam files and see the readers in the picture above? Well, you have to first remove the installed package using the menu, so go to the plugin manager and remove OScam. Second you have to manually remove a folder
/etc/tuxbox/config/oscam

There are a few ways to do this, manually using putty eg. telnet, or use a FTP program, like Filezilla. When these are not suited for you or your don't know how? Then try the solution below.

===In Windows===
*Be sure to have a OpenPLi [[Backup | Backup]]!
*Uninstall/remove OScam using the [[Plugin_Wiki | plugin manager]] and go to the softcam section.

#In Windows right click on Windows Start button
#Select Run or in Dutch Uitvoeren
#Enter the //the-ipaddress-of-your-box
##Example so like:
#: //192.168.100.10
#Choose the root folder
#Now go to
#: /etc/tuxbox/config
#Now you should see the oscam folder
#delete the folder oscam
#reboot/restart your receiver
#After a restart go to the plugin manager and install OScam
#After installation the readers created by OpenPLi should be there (like in the picture above)and select the one your need (see above)
#There is one thing to do!!
#Make a manual backup with [[Backup/AutoBackup | AutoBackup]] , so when you suddenly have to restore to replace the "old" config files in the last backup you made.

==Updates==
The OScam version will only be updated when there is a reason for it, so when you see you're not running the latest update, there is no reason for it. Of course you can always compile a new version yourself, see the developers site below.

==Internal cardshare==
In OpenPLi the softcam OScam is already set/configurated to do an internal cardshare between 2 boxes. By default OScam is configured to connect 2 boxes with "Mainreceiver" becoming the server and the “2nd_box” becoming the client (OSCam terminology calls this the reader).
As the developers of OpenPLi don’t know which box you want to be the Mainreceiver and which one becomes the 2nd_box, OScam is configured for both.
So you'll have to do 2 things on the one which becomes “2nd_box“ (OScam terminology calls this the reader).

===Preparations===
Both boxes have to be in the same network.
You have to know the IP address of the Mainreceiver.

===Mainreceiver===
----
This will be your server for the client “2nd_box”. On this one you don’t have to do anything, as there is already a user “2nd_box” which has access with the password “2nd_box”.

===2nd_box===
----
This box is the client and it will login on the Mainreceiver using a "reader", let’s say to read the data it needs. All you’ll have to do is to enter the IP address of the Mainreceiver and start the Reader.

Login into OScam on the box which will be the 2nd_box, by using your favorite browser, eg. Iceweasel-Firefox-Opera-Chrome-Internet Explorer or Microsoft Edge and enter <nowiki>http://ipadres_of_the_2nd_box:8081</nowiki> , so you can configure it properly.

#Go to the Readers TAB and click on the red pencil in the line of the Mainreceiver.
#A window will open , then you go to the line that says Device.
#On this line there is “ip_adress_mainreceiver,12005".
#Here you have to enter the IP address of the Mainreceiver instead of the text.
#Now go the bottom of the screen and click the save button.
#Now click on the Readers TAB on top of the screen.
#Then on the line Mainreceiver click on the On/Off button on the screen. By clicking it the button should go from grey to green.

It all should work like instant. Yet, to be on the safe side, you could restart the Mainreceiver and the 2nd_box.

==NL: Use with Ziggo Irdeto cards==
If you are using Ziggo Irdeto cards it will work after doing the following:
#Open in a editor the file \\ipofyourbox\root\etc\tuxbox\config\oscam\oscam.server (or add the keys in the reader section of the OScam webinterface using the pencil in the reader)
#Add the following rules in the section reader of the reader that contains the Ziggo card (or both): boxkey = please Google this generic key for Ziggo and rsakey = please Google this generic key for Ziggo
#Save the config and it should work
Note: Unfortunately this doesn't work with Ziggo Nagra cards as these cards are linked to the boxkey which is unique to the reciever you got from Ziggo. As long as you dont know this key the smartcard can't be used by OScam.

==There is a official website of the developers of OScam==
To go to official developers board http://www.streamboard.tv/wbb2/portal.php

To go to official OSCam wiki. http://www.streamboard.tv/wiki/index.php/OSCam/en

To see an overview of the last changes. https://trac.streamboard.tv/oscam/timeline

==OSCam Tuning (Mapping)==

'''Please, keep in mind use at own risk!'''

Edit all oscam.conf files with a simple text editor like kate/vim/notepad++, don't use wordpad or other windows badness

Restart the softcam after changing your config files by pressing '''Menu''' on remote control and navigate to: '''Setup > SoftCam/CI > Softcam setup... > Select softcam >''' (press left or right to select) '''oscam >''' press '''green button'''(ok).

'''Mapping'''

This mapping method will work for BE and NL seca cards
Make sure you are using '''dvbapi request mode 1 (try all CAID simulataneously)'''

'''the dvbapi file is located in /etc/tuxbox/config/oscam/oscam.dvbapi'''

M: 1817:00006A 0100:00006A
M: 1818:00006C 0100:00006C

'''oscam.server ratelimitecm and ratelimitseconds'''

This is setting crucial for performing home card sharing SECA cards of the M7 media group.
If this is setting is set wrong, the picture will result in frozen images, this is caused by bad decrypt keys (control words) from the smartcard also known as penalty mode.

Until now ratelimitecm have to be set to 4, because you are not able to decode more than 4 channels continuously.
For ratelimitseconds it is known that values from 8 seconds and lower result in bad decode keys. Further, it is also known that if ratelimitseconds is larger or equal to 11
seconds, you can zap you channels and keep a decoded tv image.

----

Softcam/OSCam

2021-06-12T08:12:45Z

Tech: /* OSCam Tuning */

==What is OScam==
OScam is a softcam, software to be used to decrypt digital television channels on a settopbox (receiver), as an alternative for a conditional access module (CAM). OScam is, compared with other softcams (Cccam, mgcamd, etc.), open source. Hence, the name ''Open Source Conditional Access Module'' (OScam)). OScam is based on the not so well known softcam MpCS. The main features of OScam are next to its softcam capabilities, that it is able to function as a cardserver.

==OScam install==
OScam can be downloaded from the OpenPLi feeds (see also https://wiki.openpli.org/Plugin_Wiki:Information). 
Please note after installation you'll have to activate the softcam also in Menu -> Settings -> Softcam / CI -> Softcam settings.

==OScam config==
You can access OScam through the webinterface <nowiki>"http://ipaddressofyourbox:8081"</nowiki> or edit the files using your favorite remote access program (telnet-SSH-SCP-FTP-etc.) for this you could have a look at our Wiki page [[Tips_and_Tweaks|Tips and Tweaks]]

==Canaal Digitaal or TV Vlaanderen==
If you have a TV Vlaanderen or Canaal Digitaal card the OScam that we compile and is in the OpenPLi feed is already pre-configured for you. After installation (see above) you login the webinterface <nowiki>"http://ipaddressofyourbox:8081"</nowiki> with your favorite browser (Firefox, Chrome, Safari, etc.) and go to the tab '''Readers''' and enable the card by mouse clicking the '''on/off''' button for your card (see picture below) and that should be all.

[[File:OScam-001.png|frameless|Centre|1200px]]

===Manually access your config file===
You can find/place the OScam configuration file into:
/etc/tuxbox/config/oscam/

==OScam removing config files==
By default OpenPLi has the OScam package in the feed configured with a few common readers like for Canaal Digitaal (CD) and TV Vlaanderen (TVV) like in the picture above. When you don't see these, it is because every restore of a backup re-installs your previous readers. Removing your OScam using the plugin manager won't remove your configuration files, that's so made by design.

'''So what to do?'''
----
If you want to remove your current config files and have the OpenPLi configured OScam files and see the readers in the picture above? Well, you have to first remove the installed package using the menu, so go to the plugin manager and remove OScam. Second you have to manually remove a folder
/etc/tuxbox/config/oscam

There are a few ways to do this, manually using putty eg. telnet, or use a FTP program, like Filezilla. When these are not suited for you or your don't know how? Then try the solution below.

===In Windows===
*Be sure to have a OpenPLi [[Backup | Backup]]!
*Uninstall/remove OScam using the [[Plugin_Wiki | plugin manager]] and go to the softcam section.

#In Windows right click on Windows Start button
#Select Run or in Dutch Uitvoeren
#Enter the //the-ipaddress-of-your-box
##Example so like:
#: //192.168.100.10
#Choose the root folder
#Now go to
#: /etc/tuxbox/config
#Now you should see the oscam folder
#delete the folder oscam
#reboot/restart your receiver
#After a restart go to the plugin manager and install OScam
#After installation the readers created by OpenPLi should be there (like in the picture above)and select the one your need (see above)
#There is one thing to do!!
#Make a manual backup with [[Backup/AutoBackup | AutoBackup]] , so when you suddenly have to restore to replace the "old" config files in the last backup you made.

==Updates==
The OScam version will only be updated when there is a reason for it, so when you see you're not running the latest update, there is no reason for it. Of course you can always compile a new version yourself, see the developers site below.

==Internal cardshare==
In OpenPLi the softcam OScam is already set/configurated to do an internal cardshare between 2 boxes. By default OScam is configured to connect 2 boxes with "Mainreceiver" becoming the server and the “2nd_box” becoming the client (OSCam terminology calls this the reader).
As the developers of OpenPLi don’t know which box you want to be the Mainreceiver and which one becomes the 2nd_box, OScam is configured for both.
So you'll have to do 2 things on the one which becomes “2nd_box“ (OScam terminology calls this the reader).

===Preparations===
Both boxes have to be in the same network.
You have to know the IP address of the Mainreceiver.

===Mainreceiver===
----
This will be your server for the client “2nd_box”. On this one you don’t have to do anything, as there is already a user “2nd_box” which has access with the password “2nd_box”.

===2nd_box===
----
This box is the client and it will login on the Mainreceiver using a "reader", let’s say to read the data it needs. All you’ll have to do is to enter the IP address of the Mainreceiver and start the Reader.

Login into OScam on the box which will be the 2nd_box, by using your favorite browser, eg. Iceweasel-Firefox-Opera-Chrome-Internet Explorer or Microsoft Edge and enter <nowiki>http://ipadres_of_the_2nd_box:8081</nowiki> , so you can configure it properly.

#Go to the Readers TAB and click on the red pencil in the line of the Mainreceiver.
#A window will open , then you go to the line that says Device.
#On this line there is “ip_adress_mainreceiver,12005".
#Here you have to enter the IP address of the Mainreceiver instead of the text.
#Now go the bottom of the screen and click the save button.
#Now click on the Readers TAB on top of the screen.
#Then on the line Mainreceiver click on the On/Off button on the screen. By clicking it the button should go from grey to green.

It all should work like instant. Yet, to be on the safe side, you could restart the Mainreceiver and the 2nd_box.

==NL: Use with Ziggo Irdeto cards==
If you are using Ziggo Irdeto cards it will work after doing the following:
#Open in a editor the file \\ipofyourbox\root\etc\tuxbox\config\oscam\oscam.server (or add the keys in the reader section of the OScam webinterface using the pencil in the reader)
#Add the following rules in the section reader of the reader that contains the Ziggo card (or both): boxkey = please Google this generic key for Ziggo and rsakey = please Google this generic key for Ziggo
#Save the config and it should work
Note: Unfortunately this doesn't work with Ziggo Nagra cards as these cards are linked to the boxkey which is unique to the reciever you got from Ziggo. As long as you dont know this key the smartcard can't be used by OScam.

==There is a official website of the developers of OScam==
To go to official developers board http://www.streamboard.tv/wbb2/portal.php

To go to official OSCam wiki. http://www.streamboard.tv/wiki/index.php/OSCam/en

To see an overview of the last changes. https://trac.streamboard.tv/oscam/timeline

==OSCam Tuning (MAPPING)==

'''Please, keep in mind use at own risk!'''

Edit all oscam.conf files with a simple text editor like kate/vim/notepad++, don't use wordpad or other windows badness

Restart the softcam after changing your config files by pressing '''Menu''' on remote control and navigate to: '''Setup > SoftCam/CI > Softcam setup... > Select softcam >''' (press left or right to select) '''oscam >''' press '''green button'''(ok).

'''Mapping'''

This mapping method will work for BE and NL seca cards
Make sure you are using '''dvbapi request mode 1 (try all CAID simulataneously)'''

'''the dvbapi file is located in /etc/tuxbox/config/oscam/oscam.dvbapi'''

M: 1817:00006A 0100:00006A
M: 1818:00006C 0100:00006C

'''oscam.server ratelimitecm and ratelimitseconds'''

This is setting crucial for performing home card sharing SECA cards of the M7 media group.
If this is setting is set wrong, the picture will result in frozen images, this is caused by bad decrypt keys (control words) from the smartcard also known as penalty mode.

Until now ratelimitecm have to be set to 4, because you are not able to decode more than 4 channels continuously.
For ratelimitseconds it is known that values from 8 seconds and lower result in bad decode keys. Further, it is also known that if ratelimitseconds is larger or equal to 11
seconds, you can zap you channels and keep a decoded tv image.

----

Softcam/OSCam

2021-06-12T08:12:11Z

Tech:

==What is OScam==
OScam is a softcam, software to be used to decrypt digital television channels on a settopbox (receiver), as an alternative for a conditional access module (CAM). OScam is, compared with other softcams (Cccam, mgcamd, etc.), open source. Hence, the name ''Open Source Conditional Access Module'' (OScam)). OScam is based on the not so well known softcam MpCS. The main features of OScam are next to its softcam capabilities, that it is able to function as a cardserver.

==OScam install==
OScam can be downloaded from the OpenPLi feeds (see also https://wiki.openpli.org/Plugin_Wiki:Information). 
Please note after installation you'll have to activate the softcam also in Menu -> Settings -> Softcam / CI -> Softcam settings.

==OScam config==
You can access OScam through the webinterface <nowiki>"http://ipaddressofyourbox:8081"</nowiki> or edit the files using your favorite remote access program (telnet-SSH-SCP-FTP-etc.) for this you could have a look at our Wiki page [[Tips_and_Tweaks|Tips and Tweaks]]

==Canaal Digitaal or TV Vlaanderen==
If you have a TV Vlaanderen or Canaal Digitaal card the OScam that we compile and is in the OpenPLi feed is already pre-configured for you. After installation (see above) you login the webinterface <nowiki>"http://ipaddressofyourbox:8081"</nowiki> with your favorite browser (Firefox, Chrome, Safari, etc.) and go to the tab '''Readers''' and enable the card by mouse clicking the '''on/off''' button for your card (see picture below) and that should be all.

[[File:OScam-001.png|frameless|Centre|1200px]]

===Manually access your config file===
You can find/place the OScam configuration file into:
/etc/tuxbox/config/oscam/

==OScam removing config files==
By default OpenPLi has the OScam package in the feed configured with a few common readers like for Canaal Digitaal (CD) and TV Vlaanderen (TVV) like in the picture above. When you don't see these, it is because every restore of a backup re-installs your previous readers. Removing your OScam using the plugin manager won't remove your configuration files, that's so made by design.

'''So what to do?'''
----
If you want to remove your current config files and have the OpenPLi configured OScam files and see the readers in the picture above? Well, you have to first remove the installed package using the menu, so go to the plugin manager and remove OScam. Second you have to manually remove a folder
/etc/tuxbox/config/oscam

There are a few ways to do this, manually using putty eg. telnet, or use a FTP program, like Filezilla. When these are not suited for you or your don't know how? Then try the solution below.

===In Windows===
*Be sure to have a OpenPLi [[Backup | Backup]]!
*Uninstall/remove OScam using the [[Plugin_Wiki | plugin manager]] and go to the softcam section.

#In Windows right click on Windows Start button
#Select Run or in Dutch Uitvoeren
#Enter the //the-ipaddress-of-your-box
##Example so like:
#: //192.168.100.10
#Choose the root folder
#Now go to
#: /etc/tuxbox/config
#Now you should see the oscam folder
#delete the folder oscam
#reboot/restart your receiver
#After a restart go to the plugin manager and install OScam
#After installation the readers created by OpenPLi should be there (like in the picture above)and select the one your need (see above)
#There is one thing to do!!
#Make a manual backup with [[Backup/AutoBackup | AutoBackup]] , so when you suddenly have to restore to replace the "old" config files in the last backup you made.

==Updates==
The OScam version will only be updated when there is a reason for it, so when you see you're not running the latest update, there is no reason for it. Of course you can always compile a new version yourself, see the developers site below.

==Internal cardshare==
In OpenPLi the softcam OScam is already set/configurated to do an internal cardshare between 2 boxes. By default OScam is configured to connect 2 boxes with "Mainreceiver" becoming the server and the “2nd_box” becoming the client (OSCam terminology calls this the reader).
As the developers of OpenPLi don’t know which box you want to be the Mainreceiver and which one becomes the 2nd_box, OScam is configured for both.
So you'll have to do 2 things on the one which becomes “2nd_box“ (OScam terminology calls this the reader).

===Preparations===
Both boxes have to be in the same network.
You have to know the IP address of the Mainreceiver.

===Mainreceiver===
----
This will be your server for the client “2nd_box”. On this one you don’t have to do anything, as there is already a user “2nd_box” which has access with the password “2nd_box”.

===2nd_box===
----
This box is the client and it will login on the Mainreceiver using a "reader", let’s say to read the data it needs. All you’ll have to do is to enter the IP address of the Mainreceiver and start the Reader.

Login into OScam on the box which will be the 2nd_box, by using your favorite browser, eg. Iceweasel-Firefox-Opera-Chrome-Internet Explorer or Microsoft Edge and enter <nowiki>http://ipadres_of_the_2nd_box:8081</nowiki> , so you can configure it properly.

#Go to the Readers TAB and click on the red pencil in the line of the Mainreceiver.
#A window will open , then you go to the line that says Device.
#On this line there is “ip_adress_mainreceiver,12005".
#Here you have to enter the IP address of the Mainreceiver instead of the text.
#Now go the bottom of the screen and click the save button.
#Now click on the Readers TAB on top of the screen.
#Then on the line Mainreceiver click on the On/Off button on the screen. By clicking it the button should go from grey to green.

It all should work like instant. Yet, to be on the safe side, you could restart the Mainreceiver and the 2nd_box.

==NL: Use with Ziggo Irdeto cards==
If you are using Ziggo Irdeto cards it will work after doing the following:
#Open in a editor the file \\ipofyourbox\root\etc\tuxbox\config\oscam\oscam.server (or add the keys in the reader section of the OScam webinterface using the pencil in the reader)
#Add the following rules in the section reader of the reader that contains the Ziggo card (or both): boxkey = please Google this generic key for Ziggo and rsakey = please Google this generic key for Ziggo
#Save the config and it should work
Note: Unfortunately this doesn't work with Ziggo Nagra cards as these cards are linked to the boxkey which is unique to the reciever you got from Ziggo. As long as you dont know this key the smartcard can't be used by OScam.

==There is a official website of the developers of OScam==
To go to official developers board http://www.streamboard.tv/wbb2/portal.php

To go to official OSCam wiki. http://www.streamboard.tv/wiki/index.php/OSCam/en

To see an overview of the last changes. https://trac.streamboard.tv/oscam/timeline

==OSCam Tuning==

'''Please, keep in mind use at own risk!'''

Edit all oscam.conf files with a simple text editor like kate/vim/notepad++, don't use wordpad or other windows badness

Restart the softcam after changing your config files by pressing '''Menu''' on remote control and navigate to: '''Setup > SoftCam/CI > Softcam setup... > Select softcam >''' (press left or right to select) '''oscam >''' press '''green button'''(ok).

'''Mapping'''

This mapping method will work for BE and NL seca cards
Make sure you are using '''dvbapi request mode 1 (try all CAID simulataneously)'''

'''the dvbapi file is located in /etc/tuxbox/config/oscam/oscam.dvbapi'''

M: 1817:00006A 0100:00006A
M: 1818:00006C 0100:00006C

'''oscam.server ratelimitecm and ratelimitseconds'''

This is setting crucial for performing home card sharing SECA cards of the M7 media group.
If this is setting is set wrong, the picture will result in frozen images, this is caused by bad decrypt keys (control words) from the smartcard also known as penalty mode.

Until now ratelimitecm have to be set to 4, because you are not able to decode more than 4 channels continuously.
For ratelimitseconds it is known that values from 8 seconds and lower result in bad decode keys. Further, it is also known that if ratelimitseconds is larger or equal to 11
seconds, you can zap you channels and keep a decoded tv image.

----

Cable:Ziggo

2021-01-28T10:32:18Z

Tech:

'''Ziggo, former UPC area (before april 2015)''' 
If your contract/customer code does not start with a 1, then the following information is valid. Enter the following settings: 

Frequency / Symbolrate: According to Ziggo company: 164.000 / 6900 ; some people claim that they are in former UPC area but that they have to use 474.000 / 6875 ? 
Modulation: QAM64 (all area's) and in some area's QAM256 is also possible 
Network ID: 05555 for FTV and Scrambled channels 
Network ID: 04444 for FTV channels 

When for some reason scanning with network id 05555 or 06666 does not work correctly, you can try a different network ID, which is the same as described on the Ziggo website for some Philips TV's.

At the Ziggo website: https://www.ziggo.nl/klantenservice/televisie-radio/digitale-tv/Philips there is a notice that Philips TV sets from the year 2010 with the product type 6000 or higher, do not hold the network code 5555 for more than a few days. To workaround this problem Ziggo has kept the old network-ID's active. To continue watching channels, you must enter the following code:

{| class="wikitable"
|-
! Region !! Network-ID
|-
| Noord-Holland || 43136
|-
| Flevoland || 43138
|-
| Friesland || 43140
|-
| Gelderland || 43142
|-
| Brabant || 43144
|-
| Zuid-Holland || 43146
|-
|-
|}

----
'''Ziggo, (until april 2014 this was split into 3 different area's known as Ziggo West, Ziggo North and Ziggo South)''' 
If your contract/customer code start with a 1, then the following information is valid. Enter the following settings: 

Frequency: 474.000 
Symbolrate: 6875 
Modulation: QAM64 
Network ID: 05555 for FTV and Scrambled channels 
Network ID: 06666 for FTV and Scrambled channels 
Network ID: 04444 for FTV channels 

Instead of contract/customer code, you can also verify by your zipcode if you have to use these settings. All former Ziggo West/North/South customers are located in one of the following zipcode area's:

1119-1175
1181-1189
1218-1412
1426-1427
1432
1435-1873
1901-1902
1906
1911
1921-1935
1941-1949
1951
1961-1969
1971-2035
2041-2042
2051-2114
2116
2121-2158
2161-2163
2165
2171-2235
2241-2245
2251-2254
2261-2289
2311-2361
2371-2377
2381-2382
2391-2481
2491-2632
2661-2662
2711-2729
2731-2743
2751-2761
2771
2861-2872
2901-2954
3381
3411-3621
3625-3648
3701-3712
3721-3732
3734-3735
3737-3739
3741-3749
3751-3755
3761-3835
3901-3962
3971-3985
3991-4191
4201-4286
4611-4797
4811-4879
4881-4891
4901-4944
5011-5071
5074-5076
5084-5126
5131
5133-5146
5151-5154
5161-5176
5211-5349
5361-5364
5366-5375
5381-5398
5401-5469
5471-5482
5561-5583
5681-5685
5766-5815
5821-5846
5851-5944
5951-5954
5961-6039
6041-6077
6081-6099
6101-6112
6114-6471
6591-6599
7271-7439
7441-7591
7621-7635
7685
7687-7688
7691-7707
7711-7722
7731-7738
7741-7766
7771-7798
7811-7859
7861-7864
7871-7895
7901-7936
7938-7938
7941-7991
8011-8322
8325-8385
8388-8397
8401-8435
8448-9079
9241-9249
9301-9497
9501-9503
9511-9515
9521-9536
9541-9566
9571
9581-9591
9601-9628
9635-9636
9641-9648
9649-9651
9654-9659
9661-9699
9711-9893
9901-9909
9911-9924
9931-9949
9951-9999

When for some reason scanning with network id 05555 or 06666 does not work correctly, you can try a different network ID, which is the same as described on the Ziggo website for some Philips TV's.

At the Ziggo website: https://www.ziggo.nl/klantenservice/televisie-radio/digitale-tv/Philips there is a notice that Philips TV sets from the year 2010 with the product type 6000 or higher, do not hold the network code 5555 for more than a few days. To workaround this problem Ziggo has kept the old network-ID's active. To continue watching channels, you must enter the following code:

{| class="wikitable"
|-
! City !! Network-ID
|-
|-
| Alkmaar || 43192
|-
| Alphen a/d Rijn || 43185
|-
| Amersfoort || 43195
|-
| Breda || 43191
|-
| Capelle || 43194
|-
| Den Bosch || 43198
|-
| Den Haag || 43186
|-
| Driebergen || 43189
|-
| Emmen || 43208
|-
| Gorichem || 43190
|-
| Gorredijk || 43209
|-
| Groningen || 43206
|-
| Hengelo || 43211
|-
| Hilversum || 43196
|-
| Hoogeveen || 43205
|-
| Mill || 43197
|-
| Roermond || 43202
|-
| Roosendaal || 43199
|-
| Sassenheim || 43184
|-
| Schoonbron || 43203
|-
| Sneek || 43210
|-
| Tilburg || 43200
|-
| Utrecht || 43187
|-
| Veenendaal || 43188
|-
| Velsen || 43193
|-
| Venlo || 43201
|-
| Winschoten || 43207
|-
| Zwolle || 43204
|-
|}

'''Note: Netwerk ID by city: in case your city isn't mentioned try one nearby.''' 

----
Obviously, of course, the entire cabling must comply with the current standard set by Ziggo. In other words 'kabelkeur A+' certified (4g shielded) plugs, cables, splitters, plugs, amplifiers etc. The AOP (Subscriber Acquisition Point, in dutch: Abonnee Overname Punt) must also comply with this A+ standard, must be for digital signal only (only 2 outputs, one for modem and one DVB-C signal). If your AOP does not comply with this standard, it's likely that, after the new channel format, low and high frequency transmissions (channels) will not appear in the scan. Among others since the last change, the movie channels have been put in almost the entire ziggo region at very low frequencies.

A major mistake is that the cable has been connected to an outdated analogue wall socket or outdated digital/analogue wall socket. These old wall sockets, as well as the old cabling in the walls, often no longer meet the current "Kabelkeur A+" standard and therefore block some high and some low frequencies. The only correct way is the usage of an 'kabelkeur A+' certified cable connected directly from the decoder to AOP. The AOP should be a modern certificated Full-Digital AOP equipped with the cable mark and with 2(!) outputs only: 1 for the modem and 1 for the digital DBV-C signal. AOP's without this quality mark and/or with old certification label no longer meet(and may block low and high frequencies). Note: Digital/Analogue AOP's (which have 3 outputs) do not meet nowadays standard ! Only Full-Digital AOP's with 2 outputs should be used.

Since the merge between Ziggo and UPC on April 13th 2015, all different cards will work in in the entire new Ziggo area. So for example an irdeto card from formerly Casema (Ziggo West) can also be used in all other Ziggo Area's. Same applies to cards from former UPC, @Home and Multikabel.

Cable:Ziggo

2021-01-28T10:28:13Z

Tech:

'''Ziggo, former UPC area (before april 2015)''' 
If your contract/customer code does not start with a 1, then the following information is valid. Enter the following settings: 

Frequency / Symbolrate: According to Ziggo company: 164.000 / 6900 ; some people claim that they are in former UPC area but that they have to use 474.000 / 6875 or 474.000 / 6900? 
Modulation: QAM64 (all area's) and in some area's QAM256 is also possible 
Network ID: 05555 for FTV and Scrambled channels 
Network ID: 04444 for FTV channels 

When for some reason scanning with network id 05555 or 06666 does not work correctly, you can try a different network ID, which is the same as described on the Ziggo website for some Philips TV's.

At the Ziggo website: https://www.ziggo.nl/klantenservice/televisie-radio/digitale-tv/Philips there is a notice that Philips TV sets from the year 2010 with the product type 6000 or higher, do not hold the network code 5555 for more than a few days. To workaround this problem Ziggo has kept the old network-ID's active. To continue watching channels, you must enter the following code:

{| class="wikitable"
|-
! Region !! Network-ID
|-
| Noord-Holland || 43136
|-
| Flevoland || 43138
|-
| Friesland || 43140
|-
| Gelderland || 43142
|-
| Brabant || 43144
|-
| Zuid-Holland || 43146
|-
|-
|}

----
'''Ziggo, (until april 2014 this was split into 3 different area's known as Ziggo West, Ziggo North and Ziggo South)''' 
If your contract/customer code start with a 1, then the following information is valid. Enter the following settings: 

Frequency: 474.000 
Symbolrate: 6875 
Modulation: QAM64 
Network ID: 05555 for FTV and Scrambled channels 
Network ID: 06666 for FTV and Scrambled channels 
Network ID: 04444 for FTV channels 

Instead of contract/customer code, you can also verify by your zipcode if you have to use these settings. All former Ziggo West/North/South customers are located in one of the following zipcode area's:

1119-1175
1181-1189
1218-1412
1426-1427
1432
1435-1873
1901-1902
1906
1911
1921-1935
1941-1949
1951
1961-1969
1971-2035
2041-2042
2051-2114
2116
2121-2158
2161-2163
2165
2171-2235
2241-2245
2251-2254
2261-2289
2311-2361
2371-2377
2381-2382
2391-2481
2491-2632
2661-2662
2711-2729
2731-2743
2751-2761
2771
2861-2872
2901-2954
3381
3411-3621
3625-3648
3701-3712
3721-3732
3734-3735
3737-3739
3741-3749
3751-3755
3761-3835
3901-3962
3971-3985
3991-4191
4201-4286
4611-4797
4811-4879
4881-4891
4901-4944
5011-5071
5074-5076
5084-5126
5131
5133-5146
5151-5154
5161-5176
5211-5349
5361-5364
5366-5375
5381-5398
5401-5469
5471-5482
5561-5583
5681-5685
5766-5815
5821-5846
5851-5944
5951-5954
5961-6039
6041-6077
6081-6099
6101-6112
6114-6471
6591-6599
7271-7439
7441-7591
7621-7635
7685
7687-7688
7691-7707
7711-7722
7731-7738
7741-7766
7771-7798
7811-7859
7861-7864
7871-7895
7901-7936
7938-7938
7941-7991
8011-8322
8325-8385
8388-8397
8401-8435
8448-9079
9241-9249
9301-9497
9501-9503
9511-9515
9521-9536
9541-9566
9571
9581-9591
9601-9628
9635-9636
9641-9648
9649-9651
9654-9659
9661-9699
9711-9893
9901-9909
9911-9924
9931-9949
9951-9999

When for some reason scanning with network id 05555 or 06666 does not work correctly, you can try a different network ID, which is the same as described on the Ziggo website for some Philips TV's.

At the Ziggo website: https://www.ziggo.nl/klantenservice/televisie-radio/digitale-tv/Philips there is a notice that Philips TV sets from the year 2010 with the product type 6000 or higher, do not hold the network code 5555 for more than a few days. To workaround this problem Ziggo has kept the old network-ID's active. To continue watching channels, you must enter the following code:

{| class="wikitable"
|-
! City !! Network-ID
|-
|-
| Alkmaar || 43192
|-
| Alphen a/d Rijn || 43185
|-
| Amersfoort || 43195
|-
| Breda || 43191
|-
| Capelle || 43194
|-
| Den Bosch || 43198
|-
| Den Haag || 43186
|-
| Driebergen || 43189
|-
| Emmen || 43208
|-
| Gorichem || 43190
|-
| Gorredijk || 43209
|-
| Groningen || 43206
|-
| Hengelo || 43211
|-
| Hilversum || 43196
|-
| Hoogeveen || 43205
|-
| Mill || 43197
|-
| Roermond || 43202
|-
| Roosendaal || 43199
|-
| Sassenheim || 43184
|-
| Schoonbron || 43203
|-
| Sneek || 43210
|-
| Tilburg || 43200
|-
| Utrecht || 43187
|-
| Veenendaal || 43188
|-
| Velsen || 43193
|-
| Venlo || 43201
|-
| Winschoten || 43207
|-
| Zwolle || 43204
|-
|}

'''Note: Netwerk ID by city: in case your city isn't mentioned try one nearby.''' 

----
Obviously, of course, the entire cabling must comply with the current standard set by Ziggo. In other words 'kabelkeur A+' certified (4g shielded) plugs, cables, splitters, plugs, amplifiers etc. The AOP (Subscriber Acquisition Point, in dutch: Abonnee Overname Punt) must also comply with this A+ standard, must be for digital signal only (only 2 outputs, one for modem and one DVB-C signal). If your AOP does not comply with this standard, it's likely that, after the new channel format, low and high frequency transmissions (channels) will not appear in the scan. Among others since the last change, the movie channels have been put in almost the entire ziggo region at very low frequencies.

A major mistake is that the cable has been connected to an outdated analogue wall socket or outdated digital/analogue wall socket. These old wall sockets, as well as the old cabling in the walls, often no longer meet the current "Kabelkeur A+" standard and therefore block some high and some low frequencies. The only correct way is the usage of an 'kabelkeur A+' certified cable connected directly from the decoder to AOP. The AOP should be a modern certificated Full-Digital AOP equipped with the cable mark and with 2(!) outputs only: 1 for the modem and 1 for the digital DBV-C signal. AOP's without this quality mark and/or with old certification label no longer meet(and may block low and high frequencies). Note: Digital/Analogue AOP's (which have 3 outputs) do not meet nowadays standard ! Only Full-Digital AOP's with 2 outputs should be used.

Since the merge between Ziggo and UPC on April 13th 2015, all different cards will work in in the entire new Ziggo area. So for example an irdeto card from formerly Casema (Ziggo West) can also be used in all other Ziggo Area's. Same applies to cards from former UPC, @Home and Multikabel.

Cable:Ziggo

2020-12-29T08:18:19Z

Tech:

'''Ziggo, former UPC area (before april 2015)''' 
If your contract/customer code does not start with a 1, then the following information is valid. Enter the following settings: 

Frequency: 474.000, some networks still use 164.000 
Symbolrate: 6875, for the networks who use 164.00 the symbolrate is 6900 
Modulation: QAM64 (all area's) and in some area's QAM256 is also possible 
Network ID: 05555 for FTV and Scrambled channels 
Network ID: 04444 for FTV channels 

When for some reason scanning with network id 05555 or 06666 does not work correctly, you can try a different network ID, which is the same as described on the Ziggo website for some Philips TV's.

At the Ziggo website: https://www.ziggo.nl/klantenservice/televisie-radio/digitale-tv/Philips there is a notice that Philips TV sets from the year 2010 with the product type 6000 or higher, do not hold the network code 5555 for more than a few days. To workaround this problem Ziggo has kept the old network-ID's active. To continue watching channels, you must enter the following code:

{| class="wikitable"
|-
! Region !! Network-ID
|-
| Noord-Holland || 43136
|-
| Flevoland || 43138
|-
| Friesland || 43140
|-
| Gelderland || 43142
|-
| Brabant || 43144
|-
| Zuid-Holland || 43146
|-
|-
|}

----
'''Ziggo, (until april 2014 this was split into 3 different area's known as Ziggo West, Ziggo North and Ziggo South)''' 
If your contract/customer code start with a 1, then the following information is valid. Enter the following settings: 

Frequency: 474.000 
Symbolrate: 6875 
Modulation: QAM64 
Network ID: 05555 for FTV and Scrambled channels 
Network ID: 06666 for FTV and Scrambled channels 
Network ID: 04444 for FTV channels 

Instead of contract/customer code, you can also verify by your zipcode if you have to use these settings. All former Ziggo West/North/South customers are located in one of the following zipcode area's:

1119-1175
1181-1189
1218-1412
1426-1427
1432
1435-1873
1901-1902
1906
1911
1921-1935
1941-1949
1951
1961-1969
1971-2035
2041-2042
2051-2114
2116
2121-2158
2161-2163
2165
2171-2235
2241-2245
2251-2254
2261-2289
2311-2361
2371-2377
2381-2382
2391-2481
2491-2632
2661-2662
2711-2729
2731-2743
2751-2761
2771
2861-2872
2901-2954
3381
3411-3621
3625-3648
3701-3712
3721-3732
3734-3735
3737-3739
3741-3749
3751-3755
3761-3835
3901-3962
3971-3985
3991-4191
4201-4286
4611-4797
4811-4879
4881-4891
4901-4944
5011-5071
5074-5076
5084-5126
5131
5133-5146
5151-5154
5161-5176
5211-5349
5361-5364
5366-5375
5381-5398
5401-5469
5471-5482
5561-5583
5681-5685
5766-5815
5821-5846
5851-5944
5951-5954
5961-6039
6041-6077
6081-6099
6101-6112
6114-6471
6591-6599
7271-7439
7441-7591
7621-7635
7685
7687-7688
7691-7707
7711-7722
7731-7738
7741-7766
7771-7798
7811-7859
7861-7864
7871-7895
7901-7936
7938-7938
7941-7991
8011-8322
8325-8385
8388-8397
8401-8435
8448-9079
9241-9249
9301-9497
9501-9503
9511-9515
9521-9536
9541-9566
9571
9581-9591
9601-9628
9635-9636
9641-9648
9649-9651
9654-9659
9661-9699
9711-9893
9901-9909
9911-9924
9931-9949
9951-9999

When for some reason scanning with network id 05555 or 06666 does not work correctly, you can try a different network ID, which is the same as described on the Ziggo website for some Philips TV's.

At the Ziggo website: https://www.ziggo.nl/klantenservice/televisie-radio/digitale-tv/Philips there is a notice that Philips TV sets from the year 2010 with the product type 6000 or higher, do not hold the network code 5555 for more than a few days. To workaround this problem Ziggo has kept the old network-ID's active. To continue watching channels, you must enter the following code:

{| class="wikitable"
|-
! City !! Network-ID
|-
|-
| Alkmaar || 43192
|-
| Alphen a/d Rijn || 43185
|-
| Amersfoort || 43195
|-
| Breda || 43191
|-
| Capelle || 43194
|-
| Den Bosch || 43198
|-
| Den Haag || 43186
|-
| Driebergen || 43189
|-
| Emmen || 43208
|-
| Gorichem || 43190
|-
| Gorredijk || 43209
|-
| Groningen || 43206
|-
| Hengelo || 43211
|-
| Hilversum || 43196
|-
| Hoogeveen || 43205
|-
| Mill || 43197
|-
| Roermond || 43202
|-
| Roosendaal || 43199
|-
| Sassenheim || 43184
|-
| Schoonbron || 43203
|-
| Sneek || 43210
|-
| Tilburg || 43200
|-
| Utrecht || 43187
|-
| Veenendaal || 43188
|-
| Velsen || 43193
|-
| Venlo || 43201
|-
| Winschoten || 43207
|-
| Zwolle || 43204
|-
|}

'''Note: Netwerk ID by city: in case your city isn't mentioned try one nearby.''' 

----
Obviously, of course, the entire cabling must comply with the current standard set by Ziggo. In other words 'kabelkeur A+' certified (4g shielded) plugs, cables, splitters, plugs, amplifiers etc. The AOP (Subscriber Acquisition Point, in dutch: Abonnee Overname Punt) must also comply with this A+ standard. If this does not comply with this standard, it's likely that, after the new channel format, low and high frequency transmissions (channels) will not appear in the scan. Among others since the last change, the movie channels have been put in almost the entire ziggo region at very low frequencies.

A major mistake is that the cable has been connected to an outdated analogue wall socket. These old wall sockets, as well as the old cabling in the walls, often no longer meet the current "Kabelkeur A+" standard and therefore block the high and low frequencies. The only correct way is to connect is the usage of an 'kabelkeur A+' certified cable connected directly from the decoder to the AOP. The AOP should be a modern AOP equipped with the cable mark. AOP's without this quality mark often no longer meet (and may block low and high frequencies).

Since the merge between Ziggo and UPC on April 13th 2015, all different cards will work in in the entire new Ziggo area. So for example an irdeto card from formerly Casema (Ziggo West) can also be used in all other Ziggo Area's. Same applies to cards from former UPC, @Home and Multikabel.

Cable:Ziggo

2020-11-14T10:54:03Z

Tech:

'''Ziggo, former UPC area (before april 2015)''' 
If your contract/customer code does not start with a 1, then the following information is valid. Enter the following settings: 

Frequency: 474.000 (old 164) 
Symbolrate: 6875 (old 6900) 
Modulation: QAM64 (all area's) and in some area's QAM256 is also possible 
Network ID: 05555 for FTV and Scrambled channels 
Network ID: 04444 for FTV channels 

When for some reason scanning with network id 05555 or 06666 does not work correctly, you can try a different network ID, which is the same as described on the Ziggo website for some Philips TV's.

At the Ziggo website: https://www.ziggo.nl/klantenservice/televisie-radio/digitale-tv/Philips there is a notice that Philips TV sets from the year 2010 with the product type 6000 or higher, do not hold the network code 5555 for more than a few days. To workaround this problem Ziggo has kept the old network-ID's active. To continue watching channels, you must enter the following code:

{| class="wikitable"
|-
! Region !! Network-ID
|-
| Noord-Holland || 43136
|-
| Flevoland || 43138
|-
| Friesland || 43140
|-
| Gelderland || 43142
|-
| Brabant || 43144
|-
| Zuid-Holland || 43146
|-
|-
|}

----
'''Ziggo, (until april 2014 this was split into 3 different area's known as Ziggo West, Ziggo North and Ziggo South)''' 
If your contract/customer code start with a 1, then the following information is valid. Enter the following settings: 

Frequency: 474.000 
Symbolrate: 6875 
Modulation: QAM64 
Network ID: 05555 for FTV and Scrambled channels 
Network ID: 06666 for FTV and Scrambled channels 
Network ID: 04444 for FTV channels 

Instead of contract/customer code, you can also verify by your zipcode if you have to use these settings. All former Ziggo West/North/South customers are located in one of the following zipcode area's:

1119-1175
1181-1189
1218-1412
1426-1427
1432
1435-1873
1901-1902
1906
1911
1921-1935
1941-1949
1951
1961-1969
1971-2035
2041-2042
2051-2114
2116
2121-2158
2161-2163
2165
2171-2235
2241-2245
2251-2254
2261-2289
2311-2361
2371-2377
2381-2382
2391-2481
2491-2632
2661-2662
2711-2729
2731-2743
2751-2761
2771
2861-2872
2901-2954
3381
3411-3621
3625-3648
3701-3712
3721-3732
3734-3735
3737-3739
3741-3749
3751-3755
3761-3835
3901-3962
3971-3985
3991-4191
4201-4286
4611-4797
4811-4879
4881-4891
4901-4944
5011-5071
5074-5076
5084-5126
5131
5133-5146
5151-5154
5161-5176
5211-5349
5361-5364
5366-5375
5381-5398
5401-5469
5471-5482
5561-5583
5681-5685
5766-5815
5821-5846
5851-5944
5951-5954
5961-6039
6041-6077
6081-6099
6101-6112
6114-6471
6591-6599
7271-7439
7441-7591
7621-7635
7685
7687-7688
7691-7707
7711-7722
7731-7738
7741-7766
7771-7798
7811-7859
7861-7864
7871-7895
7901-7936
7938-7938
7941-7991
8011-8322
8325-8385
8388-8397
8401-8435
8448-9079
9241-9249
9301-9497
9501-9503
9511-9515
9521-9536
9541-9566
9571
9581-9591
9601-9628
9635-9636
9641-9648
9649-9651
9654-9659
9661-9699
9711-9893
9901-9909
9911-9924
9931-9949
9951-9999

When for some reason scanning with network id 05555 or 06666 does not work correctly, you can try a different network ID, which is the same as described on the Ziggo website for some Philips TV's.

At the Ziggo website: https://www.ziggo.nl/klantenservice/televisie-radio/digitale-tv/Philips there is a notice that Philips TV sets from the year 2010 with the product type 6000 or higher, do not hold the network code 5555 for more than a few days. To workaround this problem Ziggo has kept the old network-ID's active. To continue watching channels, you must enter the following code:

{| class="wikitable"
|-
! City !! Network-ID
|-
|-
| Alkmaar || 43192
|-
| Alphen a/d Rijn || 43185
|-
| Amersfoort || 43195
|-
| Breda || 43191
|-
| Capelle || 43194
|-
| Den Bosch || 43198
|-
| Den Haag || 43186
|-
| Driebergen || 43189
|-
| Emmen || 43208
|-
| Gorichem || 43190
|-
| Gorredijk || 43209
|-
| Groningen || 43206
|-
| Hengelo || 43211
|-
| Hilversum || 43196
|-
| Hoogeveen || 43205
|-
| Mill || 43197
|-
| Roermond || 43202
|-
| Roosendaal || 43199
|-
| Sassenheim || 43184
|-
| Schoonbron || 43203
|-
| Sneek || 43210
|-
| Tilburg || 43200
|-
| Utrecht || 43187
|-
| Veenendaal || 43188
|-
| Velsen || 43193
|-
| Venlo || 43201
|-
| Winschoten || 43207
|-
| Zwolle || 43204
|-
|}

'''Note: Netwerk ID by city: in case your city isn't mentioned try one nearby.''' 

----
Obviously, of course, the entire cabling must comply with the current standard set by Ziggo. In other words 'kabelkeur A+' certified (4g shielded) plugs, cables, splitters, plugs, amplifiers etc. The AOP (Subscriber Acquisition Point, in dutch: Abonnee Overname Punt) must also comply with this A+ standard. If this does not comply with this standard, it's likely that, after the new channel format, low and high frequency transmissions (channels) will not appear in the scan. Among others since the last change, the movie channels have been put in almost the entire ziggo region at very low frequencies.

A major mistake is that the cable has been connected to an outdated analogue wall socket. These old wall sockets, as well as the old cabling in the walls, often no longer meet the current "Kabelkeur A+" standard and therefore block the high and low frequencies. The only correct way is to connect is the usage of an 'kabelkeur A+' certified cable connected directly from the decoder to the AOP. The AOP should be a modern AOP equipped with the cable mark. AOP's without this quality mark often no longer meet (and may block low and high frequencies).

Since the merge between Ziggo and UPC on April 13th 2015, all different cards will work in in the entire new Ziggo area. So for example an irdeto card from formerly Casema (Ziggo West) can also be used in all other Ziggo Area's. Same applies to cards from former UPC, @Home and Multikabel.

Zgemma

2020-05-01T06:06:55Z

Tech:

[[File:RECEIVER-Zgemma-001.png|frameless|right]]

=='''How to flash Zgemma H1/2S/H2/S''' ==
Download a image from: https://openpli.org

#Format your USB stick with a FAT32 file system
#Unpack the ZIP file and place the content on a USB disk.
#Plug the USB stick to the back panel USB port.
#Power on,
#Press the Power Key on the front panel after you see “USB”on the display. Then the display shows “Flash”
#When done the box will boot up on its own.
#Remove usb stick once boot has completed.

=='''How to flash a Zgemma I55 IPTV device.''' ==
Download a image from: https://openpli.org/download/zgemma/I55/

#Format your USB stick with a FAT32 file system
#Unpack the ZIP file and place the content on a USB disk.
#Change the name of the file 'Noforce' to 'force' and disconnect the stick.
#Plug the USB stick to the USB port at the right side of the I55.
#Power on the box,
#The Red led on the front lights once. After about 2 min it light again.
#When done the box will boot up on its own.
#Remove usb stick once boot has completed.
#After you have configured the basic things like Language, video and lan you choose to download plugins.
#Basically the only plugin you need is RemoteStreamConvert to let the I55 do his job.

=='''How to flash Zgemma H7S/C/AC''' ==
Download an image from: https://openpli.org/download/zgemma/H7.S

# Use a USB stick with FAT32 format.
# Unpack the ZIP file to the USB stick.
# You should see a "zgemma" folder in the root of the USB stick.
# Power off your receiver.
# Plug the USB stick to one of the back panel USB ports. Recommended to remove all other USB connected devices.
# Power on
# Immediately after power on PRESS AND HOLD the front power button behind front flap.
# The display will show boot, USB, FLSH. Once FLSH is displayed you can release (stop pressing) the button.
# Wait, when "boot" is displayed you can remove the USB stick

=='''How to flash Zgemma H9.2H/S /H9S/T''' ==
Download an image from: https://openpli.org/download/zgemma/H9.2H

# Use a USB stick with FAT32 format.
# Unpack the ZIP file to the USB stick.
# You should see a "zgemma" folder in the root of the USB stick.
# Power off the receiver
# Plug the USB stick to one of the back panel USB ports. Recommended to remove all other USB connected devices.
# Power the receiver on whilst holding down the REAR RESET BUTTON
# Once the front Air Digital display logo start to flash White/Red, release the rear reset button and wait, your receiver is now being flashed.
# If successful the receiver will reboot it self after the flashing process has completed.
# Remove USB stick

Zgemma

2020-05-01T06:03:20Z

Tech: /* "'How to flash Zgemma H9.2H/H9S/H9.2S/H9.2H/H9T'" */

[[File:RECEIVER-Zgemma-001.png|frameless|right]]

=='''How to flash Zgemma H1/2S/H2/S''' ==
Download a image from: https://openpli.org

#Format your USB stick with a FAT32 file system
#Unpack the ZIP file and place the content on a USB disk.
#Plug the USB stick to the back panel USB port.
#Power on,
#Press the Power Key on the front panel after you see “USB”on the display. Then the display shows “Flash”
#When done the box will boot up on its own.
#Remove usb stick once boot has completed.

=='''How to flash a Zgemma I55 IPTV device.''' ==
Download a image from: https://openpli.org/download/zgemma/I55/

#Format your USB stick with a FAT32 file system
#Unpack the ZIP file and place the content on a USB disk.
#Change the name of the file 'Noforce' to 'force' and disconnect the stick.
#Plug the USB stick to the USB port at the right side of the I55.
#Power on the box,
#The Red led on the front lights once. After about 2 min it light again.
#When done the box will boot up on its own.
#Remove usb stick once boot has completed.
#After you have configured the basic things like Language, video and lan you choose to download plugins.
#Basically the only plugin you need is RemoteStreamConvert to let the I55 do his job.

=='''How to flash Zgemma H7S/C/AC''' ==
Download an image from: https://openpli.org/download/zgemma/H7.S

# Use a USB stick with FAT32 format.
# Unpack the ZIP file to the USB stick.
# You should see a "zgemma" folder in the root of the USB stick.
# Power off your receiver.
# Plug the USB stick to one of the back panel USB ports. Recommended to remove all other USB connected devices.
# Power on
# Immediately after power on PRESS AND HOLD the front power button behind front flap.
# The display will show boot, USB, FLSH. Once FLSH is displayed you can release (stop pressing) the button.
# Wait, when "boot" is displayed you can remove the USB stick

=="'How to flash Zgemma H9.2H/S /H9S/T'" ==
Download an image from: https://openpli.org/download/zgemma/H9.2H

# Use a USB stick with FAT32 format.
# Unpack the ZIP file to the USB stick.
# You should see a "zgemma" folder in the root of the USB stick.
# Power off the receiver
# Plug the USB stick to one of the back panel USB ports. Recommended to remove all other USB connected devices.
# Power the receiver on whilst holding down the REAR RESET BUTTON
# Once the front Air Digital display logo start to flash White/Red, release the rear reset button and wait, your receiver is now being flashed.
# If successful the receiver will reboot it self after the flashing process has completed.
# Remove USB stick

Zgemma

2020-05-01T06:01:26Z

Tech: /* "'How to flash Zgemma H9.2H'" */

[[File:RECEIVER-Zgemma-001.png|frameless|right]]

=='''How to flash Zgemma H1/2S/H2/S''' ==
Download a image from: https://openpli.org

#Format your USB stick with a FAT32 file system
#Unpack the ZIP file and place the content on a USB disk.
#Plug the USB stick to the back panel USB port.
#Power on,
#Press the Power Key on the front panel after you see “USB”on the display. Then the display shows “Flash”
#When done the box will boot up on its own.
#Remove usb stick once boot has completed.

=='''How to flash a Zgemma I55 IPTV device.''' ==
Download a image from: https://openpli.org/download/zgemma/I55/

#Format your USB stick with a FAT32 file system
#Unpack the ZIP file and place the content on a USB disk.
#Change the name of the file 'Noforce' to 'force' and disconnect the stick.
#Plug the USB stick to the USB port at the right side of the I55.
#Power on the box,
#The Red led on the front lights once. After about 2 min it light again.
#When done the box will boot up on its own.
#Remove usb stick once boot has completed.
#After you have configured the basic things like Language, video and lan you choose to download plugins.
#Basically the only plugin you need is RemoteStreamConvert to let the I55 do his job.

=='''How to flash Zgemma H7S/C/AC''' ==
Download an image from: https://openpli.org/download/zgemma/H7.S

# Use a USB stick with FAT32 format.
# Unpack the ZIP file to the USB stick.
# You should see a "zgemma" folder in the root of the USB stick.
# Power off your receiver.
# Plug the USB stick to one of the back panel USB ports. Recommended to remove all other USB connected devices.
# Power on
# Immediately after power on PRESS AND HOLD the front power button behind front flap.
# The display will show boot, USB, FLSH. Once FLSH is displayed you can release (stop pressing) the button.
# Wait, when "boot" is displayed you can remove the USB stick

=="'How to flash Zgemma H9.2H/H9S/H9.2S/H9.2H/H9T'" ==
Download an image from: https://openpli.org/download/zgemma/H9.2H

# Use a USB stick with FAT32 format.
# Unpack the ZIP file to the USB stick.
# You should see a "zgemma" folder in the root of the USB stick.
# Power off the receiver
# Plug the USB stick to one of the back panel USB ports. Recommended to remove all other USB connected devices.
# Power the receiver on whilst holding down the REAR RESET BUTTON
# Once the front Air Digital display logo start to flash White/Red, release the rear reset button and wait, your receiver is now being flashed.
# If successful the receiver will reboot it self after the flashing process has completed.
# Remove USB stick

Zgemma

2020-05-01T05:59:46Z

Tech: /* "'How to flash Zgemma H9.2H'" */

[[File:RECEIVER-Zgemma-001.png|frameless|right]]

=='''How to flash Zgemma H1/2S/H2/S''' ==
Download a image from: https://openpli.org

#Format your USB stick with a FAT32 file system
#Unpack the ZIP file and place the content on a USB disk.
#Plug the USB stick to the back panel USB port.
#Power on,
#Press the Power Key on the front panel after you see “USB”on the display. Then the display shows “Flash”
#When done the box will boot up on its own.
#Remove usb stick once boot has completed.

=='''How to flash a Zgemma I55 IPTV device.''' ==
Download a image from: https://openpli.org/download/zgemma/I55/

#Format your USB stick with a FAT32 file system
#Unpack the ZIP file and place the content on a USB disk.
#Change the name of the file 'Noforce' to 'force' and disconnect the stick.
#Plug the USB stick to the USB port at the right side of the I55.
#Power on the box,
#The Red led on the front lights once. After about 2 min it light again.
#When done the box will boot up on its own.
#Remove usb stick once boot has completed.
#After you have configured the basic things like Language, video and lan you choose to download plugins.
#Basically the only plugin you need is RemoteStreamConvert to let the I55 do his job.

=='''How to flash Zgemma H7S/C/AC''' ==
Download an image from: https://openpli.org/download/zgemma/H7.S

# Use a USB stick with FAT32 format.
# Unpack the ZIP file to the USB stick.
# You should see a "zgemma" folder in the root of the USB stick.
# Power off your receiver.
# Plug the USB stick to one of the back panel USB ports. Recommended to remove all other USB connected devices.
# Power on
# Immediately after power on PRESS AND HOLD the front power button behind front flap.
# The display will show boot, USB, FLSH. Once FLSH is displayed you can release (stop pressing) the button.
# Wait, when "boot" is displayed you can remove the USB stick

=="'How to flash Zgemma H9.2H'" ==
Download an image from: https://openpli.org/download/zgemma/H9.2H

# Use a USB stick with FAT32 format.
# Unpack the ZIP file to the USB stick.
# You should see a "zgemma" folder in the root of the USB stick.
# Power off the receiver
# Plug the USB stick to one of the back panel USB ports. Recommended to remove all other USB connected devices.
# Power the receiver on whilst holding down the REAR RESET BUTTON
# Once the front Air Digital display logo start to flash White/Red, release the rear reset button and wait, your receiver is now being flashed.
# If successful the receiver will reboot it self after the flashing process has completed.
# Remove USB stick

Zgemma

2020-05-01T05:58:26Z

Tech:

[[File:RECEIVER-Zgemma-001.png|frameless|right]]

=='''How to flash Zgemma H1/2S/H2/S''' ==
Download a image from: https://openpli.org

#Format your USB stick with a FAT32 file system
#Unpack the ZIP file and place the content on a USB disk.
#Plug the USB stick to the back panel USB port.
#Power on,
#Press the Power Key on the front panel after you see “USB”on the display. Then the display shows “Flash”
#When done the box will boot up on its own.
#Remove usb stick once boot has completed.

=='''How to flash a Zgemma I55 IPTV device.''' ==
Download a image from: https://openpli.org/download/zgemma/I55/

#Format your USB stick with a FAT32 file system
#Unpack the ZIP file and place the content on a USB disk.
#Change the name of the file 'Noforce' to 'force' and disconnect the stick.
#Plug the USB stick to the USB port at the right side of the I55.
#Power on the box,
#The Red led on the front lights once. After about 2 min it light again.
#When done the box will boot up on its own.
#Remove usb stick once boot has completed.
#After you have configured the basic things like Language, video and lan you choose to download plugins.
#Basically the only plugin you need is RemoteStreamConvert to let the I55 do his job.

=='''How to flash Zgemma H7S/C/AC''' ==
Download an image from: https://openpli.org/download/zgemma/H7.S

# Use a USB stick with FAT32 format.
# Unpack the ZIP file to the USB stick.
# You should see a "zgemma" folder in the root of the USB stick.
# Power off your receiver.
# Plug the USB stick to one of the back panel USB ports. Recommended to remove all other USB connected devices.
# Power on
# Immediately after power on PRESS AND HOLD the front power button behind front flap.
# The display will show boot, USB, FLSH. Once FLSH is displayed you can release (stop pressing) the button.
# Wait, when "boot" is displayed you can remove the USB stick

=="'How to flash Zgemma H9.2H'" ==
Download an image from: https://openpli.org/download/zgemma/h9.2h

# Use a USB stick with FAT32 format.
# Unpack the ZIP file to the USB stick.
# You should see a "zgemma" folder in the root of the USB stick.
# Power off the receiver
# Plug the USB stick to one of the back panel USB ports. Recommended to remove all other USB connected devices.
# Power the receiver on whilst holding down the REAR RESET BUTTON
# Once the front Air Digital display logo start to flash White/Red, release the rear reset button and wait, your receiver is now being flashed.
# If successful the receiver will reboot it self after the flashing process has completed.
# Remove USB stick

Releases

2020-03-30T07:35:44Z

Tech: /* OpenPLi 7.2 - Higher and better */

Attention!! 
Major releases (like 6 => 7) you must flash, preferably using the [[Installation#Flash_from_the_Menu_.28FlashImage_support.29|'''menu''']] and choosing the backup option, then everything is restored after the flash. When there is no Hard disk present use an USB stick.

Minor releases (like 7.0 => 7.1) are updates, so updating will suffice!

=='''OpenPLi 7.2''' - Higher and better==
[[File:OpenPLi 7.2.png|frameless|right]]
Release date 7 December 2019 
Hello '''{{CURRENTUSER}}''', 

We are pleased to announce the latest release of OpenPLi and it is now available for download at [https://openpli.org/downloadOpenPLi]. As of this version, new in the release notes are the details on driver updates per vendor. So come and follow the link below and have a look at the release notes of OpenPLi 7.2 to see the highlights of what has changed.

There was a release update on 2nd and one on 23 rd march of 2020, these have bugfixes and introduces new images for the Octagon SF8008 and Edision OS Mini 4K, further details are in the release notes link below 

[[Releasenotes-7.2|See the releasenotes]]

 

=='''OpenPLi 7.1''' - Better than 7==
[[File:OpenPLi 7.1.jpg|frameless|right]]
Release date 22 June 2019 
Adding support for the Vu Duo4K, the Gamma Curve and a few more, also more functionality added; like multiboot for certain receivers. So come and follow the link below and have look at the release notes of OpenPLi 7.1.

Note: Combined tuners must be reconfigured after an update or flash. This is due to improving tuner management, which is not fully backwards compatible. Tuners that can work 'combined' are therefore 'default' disabled here. 
[[Releasenotes-7.1|See the releasenotes]]

 

=='''OpenPLi 7.0''' - Many improvements==
[[File:OpenPLi 7.png|frameless|right]]
Release date 13 January 2019 
Support for the Gamma Curve (aka SDR/HDR/HLG), changes to Samba, Fallback tuner possibilities extended, support for many Wifi USB chipsets, bugfixes and introduction of new features.

With this release:
* OpenPLi 6.x has been declared end-of-support. It will no longer receive any bugfixes. Channel lists, transponder XML's and picons will be updated on a weekly basis, until it becomes end-of-life at the release of OpenPLi 8.
* OpenPLi 4 has been declared end-of-life. It will not be built anymore, and can no longer be downloaded for receivers for which an OpenPLi 6 exists. Receivers for which OpenPLi 4 was the last supported version are declared end-of-life on our download pages.
[[Releasenotes-7.0|See the releasenotes]]

 

=='''OpenPLi 6.2''' - Tweak and Tune.==
[[File:OpenPLi 6.2.png|frameless|right]]
Release date 14 April 2018 
New receiver support for Zgemma support for the H9, Axas E4HD 4K Ultra, Qviart Lunix / Lunix3 4K. New drivers for the Xtend ET8000 / ET1000 Bugfixes and introduction of new features.

'''Known Issues'''
* Mode 12 is not always possible due to hardware limitations of the SOC. Further investigation is needed.

[[Releasenotes-6.2|See the releasenotes]]
 

=='''OpenPLi 6.1''' - Improvement of a good image.==
[[File:OpenPLi 6.1.png|frameless|right]]
Release date 22 December 2017 
New receiver support for Amiko Viper Combo, Amiko Viper T2/C, VU+ Uno 4K SE, Zgemma H6, Edision OSnino. Bugfixes and introduction of new features.

'''Known Issues'''
* Due to problems with the overscan wizard, Xtrend ET8000 and ET10000 images can have display problems. We are still looking for a solution for this problem.
* On a Mutant HD51 with mode 12 active, you can not use Video 60p frequency. With mode 1 everything is fine.
* If you upgrade on the box, avahi-daemon might not want to restart (see fix in the releasenotes).

[[Releasenotes-6.1|See the releasenotes]]

 

=='''OpenPLi 6.0''' - The long awaited OpenPLi 6.0 heralds a new era of OpenPLi images.==
[[File:OpenPLi_6.0.png|frameless|right]]
Release date 24 June 2017 
As of this release, we no longer release automated nightly beta images, but use a develop -> release candidate -> release flow, with fully tested and stable images as a result.

'''Known Issues'''
* When you create a CIFS mapping to a device mounted under /media, you get an "out of space on device" error. We are still looking for a solution for this problem.
* The xmltvimport plugin no longer exists. This may give an error if you restore a backup of OpenPLi 4 on OpenPLi 6.0. To address this, install EPGimport from the plugin menu.

[[Releasenotes-6.0|See the releasenotes]]

Information for translators

2019-11-10T14:14:46Z

Tech: /* -r | --remote */

__TOC__

== Foreword ==
OpenPLi is always looking for help to have it translated properly in many languages.
But we kindly ask you to translate in your native language or in a language that you are really familiar with. OpenPLi is not looking for automated translation jobs.

== The easiest way to translate ==

# We recommend that you download and install PoEdit from this site (please consider to register it if you appreciate it): https://poedit.net/
# Once installed go into: Preferences - Advanced - '''suppress''' the wrap line option and '''do not select''' preserve original file format
# Download the language file you want to work on from: https://github.com/OpenPLi/enigma2/tree/develop/po (click on the file name, it will show you the file content, press the RAW button and save it locally on your disk).
# Open it up with PoEdit
# You can start translating the file
# Save it, you will get 2 files xx.po and xx.mo (where xx is your language code)
# Upload your updated xx.po file to the forum and we will put it back into github for you: https://forums.openpli.org/forum/55-en-enduser-support/ (we don't need to xx.mo file only the xx.po is important for us).

== FAQ ==
=== How can I test my translation on my OpenPLi? ===

In order to test you translation work on you receiver, you will need a FTP access to it. 
You can get a free FTP client from: https://filezilla-project.org/ (or any FTP client of your choice).
Advice: if you use FileZilla client go into Parameters - Transferts - FTP: file type : set it to Binary (this will avoid you many problems when using FTP).

# You have a local file that you have worked on called: xx.mo (where xx is your language code) rename it into: enigma2.mo
# Connect to your receiver and go to this path: /usr/share/enigma2/po
# There you will see a series of folders, one per language, enter the language that you are working on: /usr/share/enigma2/po/xx/LC_MESSAGES
# Rename the file already existing on your receiver enigma2.mo into enigma2.bak (this step is important if you want to be able to rollback your changes)
# Transfert your own enigma2.mo file
# Restart your receiver
# Enjoy your translation

=== My enigma2.mo gives trouble: how to rollback? ===

# If you have followed the previous step carefully, connect with FTP to you receiver go back into the folder, delete your enigma2.mo and rename the enigma2.bak into enigma2.mo 
# Restart you receiver.

=== There is a mistake in the original strings that I want to translate, how can I fix it? ===

If you find a mistake in the original strings / sentences that you need to translate it is useless to try to fix it in the po file. The correction must done in the source code. 
So please report the error on the OpenPLi forum and wait to have it fixed into the source code and the po files including the correction to be generated again. 
You can continue to translate in between, just skip the erroneous strings.

=== Do I need to translate every strings? ===

Some strings, perhaps, doesn't need to be translated, you can of course decide to skip those strings and leave them untranslated. From my side, I'd like to have the po file that I manage always translated at 100%. Why? Because I'd like to see immediately the strings that I still need to translate, otherwise you will read over and over the untranslated strings. But it's up to you to decide.

=== My plugin is not translated, can I add manually the missing strings in the OpenPLi po files to have it translated too? ===

No never add manually missing strings/sentences into OpenPLi file to translate, for exemple plugin, because the po files are generated on a regular basis and every strings/sentences that is included in a po file but not found in the OpenPLi source code will just deleted. So you will lose your work. 

Remark: I will explain later on how to properly translated plugins (stay tuned).

=== What are %s, %d, %f do I need to keep them? ===

%s, %d, %f, ... are respectively string, number, float number replacement strings, they are used in dynamically created string. So the same numbers of those special characters needs to be in your translation. You also need to keep them "attached" so %s cannot became % s in your translation. So be careful, especially if you trust suggested translation by PoEdit sometimes in the suggested translation those special important characters are changed.

=== What is \n? ===

\n is to force a carriage return so to preserve the layout of OpenPLi you need to respect them too. And there are some original strings that start with a \n this is normal, your translated string must also start with \n.

=== Do I need to respect spaces ===

Yes, some translation start or end with spaces, this is normal since they are part of a longer string so you need to preserve those starting and trailing spaces.

== PoEdit ==

# We recommend that you download and install PoEdit from this site (please consider to register it if you appreciate it): https://poedit.net/
# Once installed go into: Preferences - Advanced - '''suppress''' the wrap line option and '''do not select''' preserve original file format

=== Can I edit po file without using PoEdit? ===

po files are just plain text, so yes of course any linux compatible text editor can do the job but PoEdit is real help to avoid some common mistake that you can make when editing it with a text editor.

=== PoEdit report warning in my po file, is it normal? ===

Yes, PoEdit can report warning that are not mistakes, for exemple a capital letter set when it is not in the original string, this is not blocking. If you are happy with you translation, don't care about warnings. 
But if PoEdit report errors then you need to fix them, errors are important and will prevent you from saving the file. So you need to fix them all.

=== What are Fuzzy/To be reviewed lines in PoEdit? ===

The po files are generated based on the translatable strings that are in the source code, but the source code evolves and the strings are subject to change. 
So when the script detect that an already translated string is changed in the source code, it is marked as fuzzy/to be reviewed, this mean that the string must be reviewed by the translators. 
It can happen that the translation is still correct, so don't forgot to untick the fuzzy/to be reviewed flag in PoEdit because a fuzzy string is never displayed, only validated translation are.

During development process some well-known strings may evolve, so a translated string created for version X can turn into "fuzzy/to be reviewed" string in release X+1. So a translation file is really adapted for the version it is created for and it will need to reviewed with every OpenPLi version.

=== How to easily unwrap my file with PoEdit? ===
=== The po file that I proposed generates thousands of changed lines in github, is it normal? ===

Not really (except if you start a translation from scratch and work very hard).
po files can have 2 format: 
* the wrapped lines version where the editor wrap a big line into several smaller ones
* the unwrapped lines where the long line are remains untouched.

OpenPLi choose to include in there git the unwrapped version of the po file, so if you propose a wrapped po file this will generates thousands of changes.

But it is possible to easily unwrap your file with PoEdit:

# Please open PoEdit, go into Preferences - Advanced - '''do not enable the wrap line after xx chars option''' and also '''do not select the preserve original file format'''.
# Open up your po file and save it.
The new version will be an unwrapped version (size will be slightly smaller too).

== Multi OS translation script pre-requisites ==

=== On Mac OSX ===

Install PoEdit from: https://poedit.net/

Since this package is downloaded from the Internet once you try to install it, it will be locked by the system, you need to go into '''System Preferences''' - '''Security & Confidentiality''' and in the '''General''' tab at the bottom click on the button: '''Open anyway'''.

* Once installed launch PoEdit and go into: Preferences - Advanced - '''suppress''' the wrap line option and '''do not select''' preserve original file format

Then open up a terminal and type:

git --version

If git is not installed you should be prompted to install it.

Then go to this website to install Homebrew: https://brew.sh/ 
Follow the instructions from the site. Once installed (perhaps a reboot is needed)

You open up a terminal and type:

brew update
brew upgrade
brew install gawk gettext gnu-sed python

Now you will be able to clone the OpenPLi repository:

cd
git clone https://github.com/OpenPLi/enigma2.git
cd ./enigma2/po
./updateallpo-multiOS.sh

=== On Windows ===

Install PoEdit from: https://poedit.net/

* Once installed launch PoEdit and go into: Preferences - Advanced - '''suppress''' the wrap line option and '''do not select''' preserve original file format

Go to Python.org and install Python: https://www.python.org/

'''Important:''' during installation of Python you need to select the checkbox Add Python to PATH otherwise Python is not accessible in git-bash, at the end of Python install I also click to allow path longer than 256 characters.

Go to GitForWindows and install it: https://gitforwindows.org/ 
Remark: seems that git-gui doesn't start on Windows, you need to launch it in Windows 8 compatibility mode. (but we won't use it anyway).

Then start the '''git-bash''' and type:

cd
git clone https://github.com/OpenPLi/enigma2.git
cd ./enigma2/po
./updateallpo-multiOS.sh

Debug: if the script doesn't work please test that Python is accessible into git-bash. 
Start a git-bash command prompt and type: '''python -i''' then use '''exit()''' to leave Python.

If you didn't get into Python either:
* Python is not installed on your Windows
* Python is installed but the access path is not set into your Windows PATH variable (the easiest way to fix it is to reinstall Python and this time select Add Python into Path checkbox.)

=== On Ubuntu / Linux ===
sudo apt-get is Ubuntu command, it should also work on other distribution just adapt the package manager to it.

Install PoEdit from: https://poedit.net/

* Once installed launch PoEdit go into: Preferences - Advanced - '''suppress''' the wrap line option and '''do not select''' preserve original file format

Open up a terminal and type:

sudo apt-get update
sudo apt-get install python gettext gawk sed git

Now we will clone the OpenPLi repository:

cd
git clone https://github.com/OpenPLi/enigma2.git
cd ./enigma2/po
./updateallpo-multiOS.sh

== updateallpo-multiOS.sh ==
=== updateallpo-multiOS.sh parameters ===

This script is created to be multi Operating System compatible. Please refer to section above to properly install the pre-requisites according to your Operating System.

Actions performed by this script are:
* Syncing with the remote server and remote branch (by default remote server: origin and default branch: develop)
* Create a local branch named: MyTranslation to work on
* Generate the latest .pot file and update all the .po files (+ create the .mo files too)

Once the script is finished you will get the very latest .po files so you can always ensure to work on an up-to-date translation file.

Once you have finish translating you can post your translation on the OpenPLi forum:
https://forums.openpli.org/forum/55-en-enduser-support/

And we will push the translation for you in OpenPLi github.

The script has been tested on: 
* Windows 10
* Mac OSX
* Ubuntu 16.04 & 18.04
* Raspbian (on Raspberry PI)

BE CAREFUL: if you change your po file from within this folder and run the script again, all your changes will be discarded!

Script must be launched from the location where you find it, so please don't specify the a full or relative path to launch. So first change directory (cd) into the folder then launch the script.

=== updateallpo-multiOS.sh possible options are: ===

-r | --remote to specify the remote git to use, default[origin]
-b | --branch to specify the branch to translate, default[develop]
-p | --python to specify the python runtime name, default[python]
-n | --nodelete to keep the .pot files, useful to find where a message came from
-h | --help this text

==== -r | --remote ====

Default: origin 
For more advanced user that have there own git fork, if you define OpenPLi as upstream you can select toward which remote server you want to update the branch.

Example: 
./updateallpo-multiOS.sh -r upstream

==== -b|--branch ====

Default: develop 
Sometimes OpenPLi create a new branch (typically rc) before releasing a new image. So it is sometimes asked to propose translation towards this branch if you want to have it in the announced futur image.

Example: 
./updateallpo-multiOS.sh -b rc

==== -p|--python ====

Default: python 
You can specify the name of the python runtime to launch, some system that have both Python 2.x and Python 3.x have python for 2.x and python3 for 3.x 
So if you want to run the script towards a specific python version simply use: 
./updateallpo-multiOS.sh -p python3

==== -n|--nodelete ====

Default: false 
By default the generated .pot files are deleted, but it can be interesting if you want to know where a string came from to have a look into the enigma2-py.pot or enigma2-xml.pot file.
So if you want to keep them use the option -n 
./updateallpo-multiOS.sh -n

All options can be combined as needed.

=== Git command to push my changes ===
Please first read the following wiki page to create your github account and forked OpenPLi to your own git (origin), setup your own git as upstream and those are the pre-requisite for the following steps: 
* https://wiki.openpli.org/Git-commands

Assuming that you have your git fork and git clone from the OpenPLi git (not yours!), and you have run the script, enter your local git clone:
cd enigma2/po
git branch
git remote -v

Will show you that you are now in the branch MyTranslation this branch was automatically created by the script. 
Please check that origin is the OpenPLi repository and upstream is yours and not the opposite! 
Let say that you have worked on the fr.po and are happy with the changes, you need to add it properly to your local git and push it to your online git.

git push --set-upstream upstream MyTranslation
git add fr.po
git commit -m "fr.po translation for develop branch"
git push

Then you can go to your online github and create the Pull Request (see git-command wiki).

== Difference between updateallpo.sh and updateallpo-multiOS.sh ==

updateallpo.sh is acting exactly the same way as the normal build process does to update the po and generate the mo files, with the same constraint Python 2.x is the only supported version.
It also doesn't update your local git clone, you need then to handle the git command yourself. So it is used by advanced users that are familiar with command line and git command.

updateallpo-multiOS.sh is doing more than updateallpo.sh, it update the git clone for you so you always have the very latest po files to work on for translation.
Moreover, it is also compatible with Python 2.x and Python 3.x, it auto detects the python script to use and include more checks. It is design to be used by any user that want to help us with OpenPLi translation without the need to have a Linux style operating system.

== Plugins translation ==

Plugins are spread across multiple git or subversion (svn) repositories. 
Some plugins are grouped on the same repository, here are some urls:
* https://github.com/OpenPLi/enigma2-plugins
* https://github.com/E2OpenPlugins
Other plugins are on their creator repository. 
 
Look into the repository file for the po file (often located into plugin_name/src/locale folder) and start working on it. If the po file doesn't exist yet, then there is probably a .pot file available. Based on the .pot file, you can easily start a new translation for your language. 
Some plugins are closed-source, you need then to contact the author if you want to propose your translation services for this specific plugin.

=== How to add a new language file in https://github.com/OpenPLi/enigma2-plugins ===

Let's say that you want to add the fa.po file into the blindscan plugin. 
Steps are (in bash shell or into git-bash): 

cd
git clone https://github.com/OpenPLi/enigma2-plugins
cd enigma2-plugins
cd blindscan
cd po
touch fa.po
cd ../..
./updateallpo-multiOS.sh

'''BE CAREFULL:''' you always need to launch updateallpo-multiOS.sh from the folder you find it. So don't try to launch it with full or relative path, it won't work. In other words always launch it with: ./updateallpo-multiOS.sh. For Windows users the script must be launched into git-bash (it has the same pre-requisites as for the OpenPLi translation).

Explanation: 
* We git clone the sources
* We go into the plugin po folder
* We create an empty translation file
* We update all the po file, so the newly created one will also be generated

So now you can start translating the plugins that you want. 

You can upload your translation file to OpenPLi forum: https://forums.openpli.org/forum/55-en-enduser-support/ and it will be added for you into git.

'''Remark for advanced users:''' when you create a pull request to add a new language translation, please also include the Makefile.am since the new language is added to it too in the LANGS variable . This is done automatically by updateallpo-multiOS.sh

Information for translators

2019-11-10T14:14:27Z

Tech: /* -b|--branch */

__TOC__

== Foreword ==
OpenPLi is always looking for help to have it translated properly in many languages.
But we kindly ask you to translate in your native language or in a language that you are really familiar with. OpenPLi is not looking for automated translation jobs.

== The easiest way to translate ==

# We recommend that you download and install PoEdit from this site (please consider to register it if you appreciate it): https://poedit.net/
# Once installed go into: Preferences - Advanced - '''suppress''' the wrap line option and '''do not select''' preserve original file format
# Download the language file you want to work on from: https://github.com/OpenPLi/enigma2/tree/develop/po (click on the file name, it will show you the file content, press the RAW button and save it locally on your disk).
# Open it up with PoEdit
# You can start translating the file
# Save it, you will get 2 files xx.po and xx.mo (where xx is your language code)
# Upload your updated xx.po file to the forum and we will put it back into github for you: https://forums.openpli.org/forum/55-en-enduser-support/ (we don't need to xx.mo file only the xx.po is important for us).

== FAQ ==
=== How can I test my translation on my OpenPLi? ===

In order to test you translation work on you receiver, you will need a FTP access to it. 
You can get a free FTP client from: https://filezilla-project.org/ (or any FTP client of your choice).
Advice: if you use FileZilla client go into Parameters - Transferts - FTP: file type : set it to Binary (this will avoid you many problems when using FTP).

# You have a local file that you have worked on called: xx.mo (where xx is your language code) rename it into: enigma2.mo
# Connect to your receiver and go to this path: /usr/share/enigma2/po
# There you will see a series of folders, one per language, enter the language that you are working on: /usr/share/enigma2/po/xx/LC_MESSAGES
# Rename the file already existing on your receiver enigma2.mo into enigma2.bak (this step is important if you want to be able to rollback your changes)
# Transfert your own enigma2.mo file
# Restart your receiver
# Enjoy your translation

=== My enigma2.mo gives trouble: how to rollback? ===

# If you have followed the previous step carefully, connect with FTP to you receiver go back into the folder, delete your enigma2.mo and rename the enigma2.bak into enigma2.mo 
# Restart you receiver.

=== There is a mistake in the original strings that I want to translate, how can I fix it? ===

If you find a mistake in the original strings / sentences that you need to translate it is useless to try to fix it in the po file. The correction must done in the source code. 
So please report the error on the OpenPLi forum and wait to have it fixed into the source code and the po files including the correction to be generated again. 
You can continue to translate in between, just skip the erroneous strings.

=== Do I need to translate every strings? ===

Some strings, perhaps, doesn't need to be translated, you can of course decide to skip those strings and leave them untranslated. From my side, I'd like to have the po file that I manage always translated at 100%. Why? Because I'd like to see immediately the strings that I still need to translate, otherwise you will read over and over the untranslated strings. But it's up to you to decide.

=== My plugin is not translated, can I add manually the missing strings in the OpenPLi po files to have it translated too? ===

No never add manually missing strings/sentences into OpenPLi file to translate, for exemple plugin, because the po files are generated on a regular basis and every strings/sentences that is included in a po file but not found in the OpenPLi source code will just deleted. So you will lose your work. 

Remark: I will explain later on how to properly translated plugins (stay tuned).

=== What are %s, %d, %f do I need to keep them? ===

%s, %d, %f, ... are respectively string, number, float number replacement strings, they are used in dynamically created string. So the same numbers of those special characters needs to be in your translation. You also need to keep them "attached" so %s cannot became % s in your translation. So be careful, especially if you trust suggested translation by PoEdit sometimes in the suggested translation those special important characters are changed.

=== What is \n? ===

\n is to force a carriage return so to preserve the layout of OpenPLi you need to respect them too. And there are some original strings that start with a \n this is normal, your translated string must also start with \n.

=== Do I need to respect spaces ===

Yes, some translation start or end with spaces, this is normal since they are part of a longer string so you need to preserve those starting and trailing spaces.

== PoEdit ==

# We recommend that you download and install PoEdit from this site (please consider to register it if you appreciate it): https://poedit.net/
# Once installed go into: Preferences - Advanced - '''suppress''' the wrap line option and '''do not select''' preserve original file format

=== Can I edit po file without using PoEdit? ===

po files are just plain text, so yes of course any linux compatible text editor can do the job but PoEdit is real help to avoid some common mistake that you can make when editing it with a text editor.

=== PoEdit report warning in my po file, is it normal? ===

Yes, PoEdit can report warning that are not mistakes, for exemple a capital letter set when it is not in the original string, this is not blocking. If you are happy with you translation, don't care about warnings. 
But if PoEdit report errors then you need to fix them, errors are important and will prevent you from saving the file. So you need to fix them all.

=== What are Fuzzy/To be reviewed lines in PoEdit? ===

The po files are generated based on the translatable strings that are in the source code, but the source code evolves and the strings are subject to change. 
So when the script detect that an already translated string is changed in the source code, it is marked as fuzzy/to be reviewed, this mean that the string must be reviewed by the translators. 
It can happen that the translation is still correct, so don't forgot to untick the fuzzy/to be reviewed flag in PoEdit because a fuzzy string is never displayed, only validated translation are.

During development process some well-known strings may evolve, so a translated string created for version X can turn into "fuzzy/to be reviewed" string in release X+1. So a translation file is really adapted for the version it is created for and it will need to reviewed with every OpenPLi version.

=== How to easily unwrap my file with PoEdit? ===
=== The po file that I proposed generates thousands of changed lines in github, is it normal? ===

Not really (except if you start a translation from scratch and work very hard).
po files can have 2 format: 
* the wrapped lines version where the editor wrap a big line into several smaller ones
* the unwrapped lines where the long line are remains untouched.

OpenPLi choose to include in there git the unwrapped version of the po file, so if you propose a wrapped po file this will generates thousands of changes.

But it is possible to easily unwrap your file with PoEdit:

# Please open PoEdit, go into Preferences - Advanced - '''do not enable the wrap line after xx chars option''' and also '''do not select the preserve original file format'''.
# Open up your po file and save it.
The new version will be an unwrapped version (size will be slightly smaller too).

== Multi OS translation script pre-requisites ==

=== On Mac OSX ===

Install PoEdit from: https://poedit.net/

Since this package is downloaded from the Internet once you try to install it, it will be locked by the system, you need to go into '''System Preferences''' - '''Security & Confidentiality''' and in the '''General''' tab at the bottom click on the button: '''Open anyway'''.

* Once installed launch PoEdit and go into: Preferences - Advanced - '''suppress''' the wrap line option and '''do not select''' preserve original file format

Then open up a terminal and type:

git --version

If git is not installed you should be prompted to install it.

Then go to this website to install Homebrew: https://brew.sh/ 
Follow the instructions from the site. Once installed (perhaps a reboot is needed)

You open up a terminal and type:

brew update
brew upgrade
brew install gawk gettext gnu-sed python

Now you will be able to clone the OpenPLi repository:

cd
git clone https://github.com/OpenPLi/enigma2.git
cd ./enigma2/po
./updateallpo-multiOS.sh

=== On Windows ===

Install PoEdit from: https://poedit.net/

* Once installed launch PoEdit and go into: Preferences - Advanced - '''suppress''' the wrap line option and '''do not select''' preserve original file format

Go to Python.org and install Python: https://www.python.org/

'''Important:''' during installation of Python you need to select the checkbox Add Python to PATH otherwise Python is not accessible in git-bash, at the end of Python install I also click to allow path longer than 256 characters.

Go to GitForWindows and install it: https://gitforwindows.org/ 
Remark: seems that git-gui doesn't start on Windows, you need to launch it in Windows 8 compatibility mode. (but we won't use it anyway).

Then start the '''git-bash''' and type:

cd
git clone https://github.com/OpenPLi/enigma2.git
cd ./enigma2/po
./updateallpo-multiOS.sh

Debug: if the script doesn't work please test that Python is accessible into git-bash. 
Start a git-bash command prompt and type: '''python -i''' then use '''exit()''' to leave Python.

If you didn't get into Python either:
* Python is not installed on your Windows
* Python is installed but the access path is not set into your Windows PATH variable (the easiest way to fix it is to reinstall Python and this time select Add Python into Path checkbox.)

=== On Ubuntu / Linux ===
sudo apt-get is Ubuntu command, it should also work on other distribution just adapt the package manager to it.

Install PoEdit from: https://poedit.net/

* Once installed launch PoEdit go into: Preferences - Advanced - '''suppress''' the wrap line option and '''do not select''' preserve original file format

Open up a terminal and type:

sudo apt-get update
sudo apt-get install python gettext gawk sed git

Now we will clone the OpenPLi repository:

cd
git clone https://github.com/OpenPLi/enigma2.git
cd ./enigma2/po
./updateallpo-multiOS.sh

== updateallpo-multiOS.sh ==
=== updateallpo-multiOS.sh parameters ===

This script is created to be multi Operating System compatible. Please refer to section above to properly install the pre-requisites according to your Operating System.

Actions performed by this script are:
* Syncing with the remote server and remote branch (by default remote server: origin and default branch: develop)
* Create a local branch named: MyTranslation to work on
* Generate the latest .pot file and update all the .po files (+ create the .mo files too)

Once the script is finished you will get the very latest .po files so you can always ensure to work on an up-to-date translation file.

Once you have finish translating you can post your translation on the OpenPLi forum:
https://forums.openpli.org/forum/55-en-enduser-support/

And we will push the translation for you in OpenPLi github.

The script has been tested on: 
* Windows 10
* Mac OSX
* Ubuntu 16.04 & 18.04
* Raspbian (on Raspberry PI)

BE CAREFUL: if you change your po file from within this folder and run the script again, all your changes will be discarded!

Script must be launched from the location where you find it, so please don't specify the a full or relative path to launch. So first change directory (cd) into the folder then launch the script.

=== updateallpo-multiOS.sh possible options are: ===

-r | --remote to specify the remote git to use, default[origin]
-b | --branch to specify the branch to translate, default[develop]
-p | --python to specify the python runtime name, default[python]
-n | --nodelete to keep the .pot files, useful to find where a message came from
-h | --help this text

==== -r | --remote ====

Default: origin 
For more advanced user that have there own git fork, if you define OpenPLi as upstream you can select toward which remote server you want to update the branch.

Exemple: 
./updateallpo-multiOS.sh -r upstream

==== -b|--branch ====

Default: develop 
Sometimes OpenPLi create a new branch (typically rc) before releasing a new image. So it is sometimes asked to propose translation towards this branch if you want to have it in the announced futur image.

Example: 
./updateallpo-multiOS.sh -b rc

==== -p|--python ====

Default: python 
You can specify the name of the python runtime to launch, some system that have both Python 2.x and Python 3.x have python for 2.x and python3 for 3.x 
So if you want to run the script towards a specific python version simply use: 
./updateallpo-multiOS.sh -p python3

==== -n|--nodelete ====

Default: false 
By default the generated .pot files are deleted, but it can be interesting if you want to know where a string came from to have a look into the enigma2-py.pot or enigma2-xml.pot file.
So if you want to keep them use the option -n 
./updateallpo-multiOS.sh -n

All options can be combined as needed.

=== Git command to push my changes ===
Please first read the following wiki page to create your github account and forked OpenPLi to your own git (origin), setup your own git as upstream and those are the pre-requisite for the following steps: 
* https://wiki.openpli.org/Git-commands

Assuming that you have your git fork and git clone from the OpenPLi git (not yours!), and you have run the script, enter your local git clone:
cd enigma2/po
git branch
git remote -v

Will show you that you are now in the branch MyTranslation this branch was automatically created by the script. 
Please check that origin is the OpenPLi repository and upstream is yours and not the opposite! 
Let say that you have worked on the fr.po and are happy with the changes, you need to add it properly to your local git and push it to your online git.

git push --set-upstream upstream MyTranslation
git add fr.po
git commit -m "fr.po translation for develop branch"
git push

Then you can go to your online github and create the Pull Request (see git-command wiki).

== Difference between updateallpo.sh and updateallpo-multiOS.sh ==

updateallpo.sh is acting exactly the same way as the normal build process does to update the po and generate the mo files, with the same constraint Python 2.x is the only supported version.
It also doesn't update your local git clone, you need then to handle the git command yourself. So it is used by advanced users that are familiar with command line and git command.

updateallpo-multiOS.sh is doing more than updateallpo.sh, it update the git clone for you so you always have the very latest po files to work on for translation.
Moreover, it is also compatible with Python 2.x and Python 3.x, it auto detects the python script to use and include more checks. It is design to be used by any user that want to help us with OpenPLi translation without the need to have a Linux style operating system.

== Plugins translation ==

Plugins are spread across multiple git or subversion (svn) repositories. 
Some plugins are grouped on the same repository, here are some urls:
* https://github.com/OpenPLi/enigma2-plugins
* https://github.com/E2OpenPlugins
Other plugins are on their creator repository. 
 
Look into the repository file for the po file (often located into plugin_name/src/locale folder) and start working on it. If the po file doesn't exist yet, then there is probably a .pot file available. Based on the .pot file, you can easily start a new translation for your language. 
Some plugins are closed-source, you need then to contact the author if you want to propose your translation services for this specific plugin.

=== How to add a new language file in https://github.com/OpenPLi/enigma2-plugins ===

Let's say that you want to add the fa.po file into the blindscan plugin. 
Steps are (in bash shell or into git-bash): 

cd
git clone https://github.com/OpenPLi/enigma2-plugins
cd enigma2-plugins
cd blindscan
cd po
touch fa.po
cd ../..
./updateallpo-multiOS.sh

'''BE CAREFULL:''' you always need to launch updateallpo-multiOS.sh from the folder you find it. So don't try to launch it with full or relative path, it won't work. In other words always launch it with: ./updateallpo-multiOS.sh. For Windows users the script must be launched into git-bash (it has the same pre-requisites as for the OpenPLi translation).

Explanation: 
* We git clone the sources
* We go into the plugin po folder
* We create an empty translation file
* We update all the po file, so the newly created one will also be generated

So now you can start translating the plugins that you want. 

You can upload your translation file to OpenPLi forum: https://forums.openpli.org/forum/55-en-enduser-support/ and it will be added for you into git.

'''Remark for advanced users:''' when you create a pull request to add a new language translation, please also include the Makefile.am since the new language is added to it too in the LANGS variable . This is done automatically by updateallpo-multiOS.sh

Receivers:Maxytec

2019-07-22T14:51:18Z

Tech: Created page with "right =='''How to flash / place a new recovery image into the Maxytec Multibox''' == First download an image on http://open..."

[[File:RECEIVERS-Maxytec-001.jpg|frameless|right]]

=='''How to flash / place a new recovery image into the Maxytec Multibox''' ==

First download an image on http://openpli.org/download/maxytec/multibox/ and unpack the image on a FAT32 formatted USBstick. 
FLASHING THE IMAGE. 

# Shut down the power of the receiver by unplugging the 12 volt power at back of the receiver. Personally I prefer to unplug the primary (220 volt) power as there isn’t a power switch present. This appeared to be to expensive? 😮 
# Insert the USB stick containing the image files into the side USB 2.0 port on the receiver. (Do '''NOT''' use the USB 3.0 port at the back) 
# Power on the receiver by connecting the 220 volt power supply or put the 12 volt powerplug into the box. 
# Immediately push a paperclip in the small hole at the left side of the box (reset) and hold this for some seconds. The flashing of the recovery image starts. 
# Wait for the image to flash. In case your USB stick is equipped with a led you can follow this process as no other indication is present. 
# When the flashing process has completed the receiver will automatically reboot. 

After having flashed the box it starts to boot and you can continue with the [[Installation | setup or installation wizard]] of the settopbox.

How to Flash your receiver

2019-07-22T14:48:24Z

Tech:

* [https://openpli.org/downloadSettop Boxes that are supported]
Follow this link if you want to know if you can flash a receiver/Setop Box with OpenPLi.

* [[Receivers:Settopbox_Comparison| Settop Box Comparison]] 
Here is a table where Settop boxes are compared, right down to component level, nice when you want to buy one.

* [[Receivers:Power_comparison| Settop Box Power comparison]] 
 

'''How flash'''
----
Below in alphabetic order links on how to flash a certain brand Settop Box (btw if it's not there yet, please feel free to add it).

* '''[[Amiko| Amiko]]'''
* '''[[Axas| Axas]]'''
* '''[[Receivers:Dreambox| Dreambox]]'''
* '''[[Receivers:Edision| Edision]]'''
* '''[[Receivers:Formuler| Formuler]]'''
* '''[[Receivers:Gi| Gi]]'''
* '''[[Receivers:GigaBlue| GigaBlue]]'''
* '''[[Receivers:Golden_Interstar| Golden Interstar]]
* '''[[Receivers:Maxdigital| Maxdigital]]'''
* '''[[Receivers:Maxytec| Maxytec]]'''
* '''[[Receivers:Mircablebox| Miraclebox]]'''
* '''[[Receivers:Mut@nt| Mut@nt]]'''
* '''[[Qviart| Qviart]]'''
* '''[[Receivers:SAB| SAB]]'''
* '''[[Spycat| Spycat]]'''
* '''[[Vimastec| Vimastec]]'''
* '''[[Receivers:Vu| Vu+]]'''
* '''[[Xsarius| Xsarius]]'''
* '''[[Media:Leaflet-XsariusFusionHDSE.pdf|Fusion HD SE]]'''
* '''[[Wetek| Wetek]]'''
* '''[[Receivers:Xtrend| Xtrend]]'''
* '''[[Zgemma| Zgemma]]'''

Problems and Solutions

2019-01-13T10:10:25Z

Tech: /* Debugging Enigma */

=='''Crash logs'''==
Crash logs are generated during a system crash, also known as a GSOD (green screen of death). The log can give insight to the probable cause of the crash. If you want help with the content of the file, you can post it on our [https://forums.openpli.org forum]. The crash log file is named like in the example below:

enigma2_crash_3891289128.log

===The location of the crash log file when there is a HDD (Harddisk) present===
Normally the crash.log file is stored in the root of the HDD so in
/media/hdd

===The location of the crash.log file without any HDD (Harddisk) present===
Normally the crash log file is stored in the
/home/root

=='''Debugging Enigma'''==
If you want to debug and want to know what is happening in Enigma, you can start your receiver in debug mode with the following command:
root@<receiver>: init 4
root@<receiver>: ENIGMA_DEBUG_LVL=4 enigma2

To stop: Press CRTL-C. Enigma will halt. Then start enigma with:
root@<receiver>: init 3
Or reboot the receiver with:
root@<receiver>: reboot

'''Note:''' For '''debugging gstreamer''' with read actions stuff use: '''ENIGMA_DEBUG_LVL=4 GST_DEBUG=*soup*:6,*dvb*:6 enigma2''' 

===For easier reading (Less logging) use:===

ENIGMA_DEBUG_LVL=4 GST_DEBUG=*soup*:4,*dvb*:4 enigma2

===Writing debug log to a USB stick===
If for some reason your receiver reboots your debug log might be gone. Then plugin a USB stick in your receiver and use the command below, which writes the debug log to and USB stick
ENIGMA_DEBUG_LVL=4 enigma2 | tee /media/usb/enigma.log

=='''I cannot record with my receiver or recording with a Zapper (eg. Vu Zero / Vu Solo Se)'''==
By default some Vu+ boxes are a ''zapper'', meaning you can not record with it. If you want to record with it, you can install the "pau" plugin/extension. It is located in the
''extensions'' section of the [[Plugin_Wiki| plugin browser]].

=='''Mountmanager Problems'''==
Here are some solutions when you run into problems with mounting\sharing a medium (HDD) in your network.

===Older vs newer Kernel===
When your box uses a kernel 3.x ('''Menu-Information-About''') and you want to mount something that has a kernel 4.x your CIFS share might fail, even though you entered the data carefully, but there is a solution.

The solution is simple, you can try the following; If you make a mount with [[MountManager | Mountmanager]], change the "mount options" from "rw" to "rw, sec=ntlm", this will lower the security standard from ntlmv2 (default with kernel 4.x and up) to ntlm.

Now exit and re-mount or Reboot your box and if this was the cause, you can now access your share.

===Older vs newer SMB Protocol===
There is a similar issue regarding the version of the SMB protocol used.

There are several versions of the SMB protocol, v1, v2.0, v2.1 and v3. (see https://blogs.technet.microsoft.com/josebda/2013/10/02/windows-server-2012-r2-which-version-of-the-smb-protocol-smb-1-0-smb-2-0-smb-2-1-smb-3-0-or-smb-3-02-are-you-using/ for more in-depth information).

Recently, due to several security issues, an action has been ongoing to disable the unsafe SMBv1, not only in Windows, but also in NAS systems like Synology for example. Windows has the option to cycle through all available and allowed protocols when you want to connect to a share, so you as a user don't notice anything and don't know which protocol is used. But the Linux kernel driver doesn't. It connects using the version it has been programmed with, and if you as a user need a different version, you need to specify this in the mount options.

Up to kernel v4.13 (at the moment of writing all supported receivers), the default was SMBv1, after that, the default has been upgraded to SMBv3. So if your box has a kernel older than 4.13, and your "server" doesn't support SMBv1, you need to specify the version on the mount. Likewise, if your box runs 4.13 or higher, and your "server" doesn't support SMBv3, you also need to specify the version on the mount.

The solution is to change the SMB version used to mount, to do this in [[MountManager | Mountmanager]] change the "mount options" from "rw" to "rw, vers=3.0" (or whatever version you want to mount). You might have to try a few, if you don't know which one your server supports, but always start with the highest version.

This is a good overview on this subject: https://www.happyassassin.net/2017/11/03/linux-kernel-4-13-and-smb-protocol-version-fun/

The same is true for the authentication mechanism. This used to be NTLM, but in Kernel 3.8 the default has changed to NTLMv2, as Windows no longer supports NTLM (also because of security issues). But depending on the version and configuration of Windows (especially Windows Server), you might need to specify an alternative mechanism on the commandline too.

=='''Reset lost password'''==
In case you have lost your box password or someone else has been so 'funny' to create a password without having informed you, there are several ways to solve this issue.

I assume that you still have access via Explorer with \\boxname or \\ipaddressbox. If not, then the only 'solution' to get access again is to flash your box which is actually not a solution.

# Go to the map /etc where you find the file shadow.
# If you owe another Enigma2 box then go to the map \etc and copy there that file 'shadow'.
# Go to the box with the unknown password and paste the just copied file from the other box over your present version of shadow.

There is a second scenario to solve this.

# Go to the map /etc where you also find the file passwd.
# Select and edit the file passwd with right mouse button and select a proper editer. I use Notepad ++
# In this file the line: root: x: 0: 0: root: / root: / bin / sh or something as root: EIfidfjeSAEFKEOlasdf5ewr3rWEW: 0: 0: root: / root: / bin / sh is the actual PW. The Password field is x or the encrypted string EIfidfjeSAEFKEOlasdf5ewr3rWEW
# Delete the x or the string The line is now following: root :: 0: 0: root: / root: / bin / sh
# Save / overwrite this file and exit Notepad ++.

=='''Splash screen replacement'''==
The splashscreen is written in a limited reserved space of flash. We believe that the splash screen is not intended to be image specific, it should just show the manufacturer and/or box type information. The dimensions and type of splash file supported by the bootloader, differ per brand, and possibly even per box.
We advice to stay away from that, leave the splash screen to the bootloader, and the manufacturer.

If by some reason, let's say another image, has changed it, you can restore it to the one from the manufacturer. Do a search on the OpenPLi site using Google and type:

splash screen site:openpli.org

For the Vu+ jump to [[Problems_and_Solutions#Restore_Splash_screen_for_-_Factory_bootlogo | Restore Splash screen for Vu]]

=='''USB memory sticks working or not'''==
When you want to use an USB memory stick, lets say for flashing your box with OpenPLi, there is no way of telling your stick might work, it's trial and error! Because the USB detection system in the bootloader of your receiver is very simple, there are 2 things to consider:

#It has a short device detection time, which is as it should be, because a long device detection time could result in an annoying long booting procedure. This (short device detection) causes devices whose detection takes (too) long (usb3 devices, large sticks) not to be seen in time.
#It takes the first device that is found and if you've connected multiple devices, chances are that it's not the device you want to use.

Generally speaking, small old USB sticks with less than 1Gb have a bigger change to work.

=='''Video codecs and what if you can not play a movie on your receiver'''==
Video Codecs are not needed for your receiver. The difference between your PC/Lab top and your Receiver is that your PC/Lab top uses its processor to decode the video, while your receiver uses a specialized chip. For your PC/Lap top you can therefore add new codecs by installing software, with your receiver the codecs consist of electronic circuits in the chip and therefore codecs can't be added, so only the "codecs" in the chip can be played.

So if you have a movie that can't be played, you'll have to re-code it. For this you can use programs like [https://handbrake.fr/ Handbrake]. A good choice would be h264 or h265 as a video codec and mp2, mp3 or ac3 as an audio codec.

=='''Vu+ related'''==

==='''Cable Scan issue's?''' ===

There is bug with the VU+ drivers so that a scan can not be completed if tuner D is used.

This is the issue:
input3 and input2 have no input3_choices or input4_choices so the Enigma2 doesn't try to initialize them.

/proc/stb/tsmux/input1_choices:CI0 CI1 A B
/proc/stb/tsmux/input0_choices:CI0 CI1 A B
/proc/stb/tsmux/input3:A
/proc/stb/tsmux/input2:A
/proc/stb/tsmux/input1:B
/proc/stb/tsmux/input0:AA simple solution is to initialize them manually.

Temporary solution until reboot
echo -n C > /proc/stb/tsmux/input2
echo -n D > /proc/stb/tsmux/input3

Note: VU+ should add input2_choices and input3_choices nodes.

Temporary Solution, that still works after a reboot:
Install the IPK files that are posted at: https://forums.openpli.org/topic/49214-vuplus-duo2-dvb-t2-tuner-nim-tt3l10-stopped-working/page-3#entry701207
Reboot the receiver, and the scan problems are solved.

==='''Restore Splash screen for - Factory bootlogo'''===

The file that can be found at the forum (see below) will place the original factory bootlogo back on your receiver. The content of the file needs to be placed on a USB pen drive. The file contains splash screens for the models:

duo2, solo2, solo4k, solose, ultimo, ultimo4k, vuduo4k, uno, uno4k, uno4kse, zero and the zero4k.
You do not have to pick one of the bootlogo's.. Your receiver selects only the file that must be needed. .

So the following steps must be taken:
# place the content of the zip file on the USB pendrive
# reboot your receiver
# flash the 'image' (this wil take a few seconds)
# when the flash is completed, remove the USB pendrive
# restart your receiver

Source: https://forums.openpli.org/topic/48876-herstel-splash-screens-van-vu-modellen/page-3?p=975297

=='''Zgemma related'''==

==='''Restore Splash screen for Zgemma'''===

Source: https://forums.openpli.org/topic/41521-boot-screen/#entry549387

Problems and Solutions

2018-12-02T08:20:17Z

Tech: /* Restore Splash screen for - Factory bootlogo */

=='''Crash logs'''==
Crash logs are generated during a system crash, also known as a GSOD (green screen of death). The log can give insight to the probable cause of the crash. If you want help with the content of the file, you can post it on our [https://forums.openpli.org forum]. The crash log file is named like in the example below:

enigma2_crash_3891289128.log

===The location of the crash log file when there is a HDD (Harddisk) present===
Normally the crash.log file is stored in the root of the HDD so in
/media/hdd

===The location of the crash.log file without any HDD (Harddisk) present===
Normally the crash log file is stored in the
/home/root

=='''Debugging Enigma'''==
If you want to debug and want to know what is happening in Enigma, you can start your receiver in debug mode with the following command:
root@<receiver>: init 4
root@<receiver>: ENIGMA_DEBUG_LVL=4 /usr/bin/enigma2.sh

To stop: Press CRTL-C. Enigma will halt. Then start enigma with:
root@<receiver>: init 3
Or reboot the receiver with:
root@<receiver>: reboot

'''Note:''' For '''debugging gstreamer''' with read actions stuff use: '''ENIGMA_DEBUG_LVL=4 GST_DEBUG=*soup*:6,*dvb*:6 enigma2''' 

===For easier reading (Less logging) use:===

ENIGMA_DEBUG_LVL=4 GST_DEBUG=*soup*:4,*dvb*:4 enigma2

===Writing debug log to a USB stick===
If for some reason your receiver reboots your debug log might be gone. Then plugin a USB stick in your receiver and use the command below, which writes the debug log to and USB stick
ENIGMA_DEBUG_LVL=4 enigma2 | tee /media/usb/enigma.log

=='''I cannot record with my receiver or recording with a Zapper (eg. Vu Zero / Vu Solo Se)'''==
By default some Vu+ boxes are a ''zapper'', meaning you can not record with it. If you want to record with it, you can install the "pau" plugin/extension. It is located in the
''extensions'' section of the [[Plugin_Wiki| plugin browser]].

=='''Mountmanager Problems'''==
Here are some solutions when you run into problems with mounting\sharing a medium (HDD) in your network.

===Older vs newer Kernel===
When your box uses a kernel 3.x ('''Menu-Information-About''') and you want to mount something that has a kernel 4.x your CIFS share might fail, even though you entered the data carefully, but there is a solution.

The solution is simple, you can try the following; If you make a mount with [[MountManager | Mountmanager]], change the "mount options" from "rw" to "rw, sec=ntlm", this will lower the security standard from ntlmv2 (default with kernel 4.x and up) to ntlm.

Now exit and re-mount or Reboot your box and if this was the cause, you can now access your share.

===Older vs newer SMB Protocol===
There is a similar issue regarding the version of the SMB protocol used.

There are several versions of the SMB protocol, v1, v2.0, v2.1 and v3. (see https://blogs.technet.microsoft.com/josebda/2013/10/02/windows-server-2012-r2-which-version-of-the-smb-protocol-smb-1-0-smb-2-0-smb-2-1-smb-3-0-or-smb-3-02-are-you-using/ for more in-depth information).

Recently, due to several security issues, an action has been ongoing to disable the unsafe SMBv1, not only in Windows, but also in NAS systems like Synology for example. Windows has the option to cycle through all available and allowed protocols when you want to connect to a share, so you as a user don't notice anything and don't know which protocol is used. But the Linux kernel driver doesn't. It connects using the version it has been programmed with, and if you as a user need a different version, you need to specify this in the mount options.

Up to kernel v4.13 (at the moment of writing all supported receivers), the default was SMBv1, after that, the default has been upgraded to SMBv3. So if your box has a kernel older than 4.13, and your "server" doesn't support SMBv1, you need to specify the version on the mount. Likewise, if your box runs 4.13 or higher, and your "server" doesn't support SMBv3, you also need to specify the version on the mount.

The solution is to change the SMB version used to mount, to do this in [[MountManager | Mountmanager]] change the "mount options" from "rw" to "rw, vers=3.0" (or whatever version you want to mount). You might have to try a few, if you don't know which one your server supports, but always start with the highest version.

This is a good overview on this subject: https://www.happyassassin.net/2017/11/03/linux-kernel-4-13-and-smb-protocol-version-fun/

The same is true for the authentication mechanism. This used to be NTLM, but in Kernel 3.8 the default has changed to NTLMv2, as Windows no longer supports NTLM (also because of security issues). But depending on the version and configuration of Windows (especially Windows Server), you might need to specify an alternative mechanism on the commandline too.

=='''Reset lost password'''==
In case you have lost your box password or someone else has been so 'funny' to create a password without having informed you, there are several ways to solve this issue.

I assume that you still have access via Explorer with \\boxname or \\ipaddressbox. If not, then the only 'solution' to get access again is to flash your box which is actually not a solution.

# Go to the map /etc where you find the file shadow.
# If you owe another Enigma2 box then go to the map \etc and copy there that file 'shadow'.
# Go to the box with the unknown password and paste the just copied file from the other box over your present version of shadow.

There is a second scenario to solve this.

# Go to the map /etc where you also find the file passwd.
# Select and edit the file passwd with right mouse button and select a proper editer. I use Notepad ++
# In this file the line: root: x: 0: 0: root: / root: / bin / sh or something as root: EIfidfjeSAEFKEOlasdf5ewr3rWEW: 0: 0: root: / root: / bin / sh is the actual PW. The Password field is x or the encrypted string EIfidfjeSAEFKEOlasdf5ewr3rWEW
# Delete the x or the string The line is now following: root :: 0: 0: root: / root: / bin / sh
# Save / overwrite this file and exit Notepad ++.

=='''Splash screen replacement'''==
The splashscreen is written in a limited reserved space of flash. We believe that the splash screen is not intended to be image specific, it should just show the manufacturer and/or box type information. The dimensions and type of splash file supported by the bootloader, differ per brand, and possibly even per box.
We advice to stay away from that, leave the splash screen to the bootloader, and the manufacturer.

If by some reason, let's say another image, has changed it, you can restore it to the one from the manufacturer. Do a search on the OpenPLi site using Google and type:

splash screen site:openpli.org

For the Vu+ jump to [[Problems_and_Solutions#Restore_Splash_screen_for_-_Factory_bootlogo | Restore Splash screen for Vu]]

=='''USB memory sticks working or not'''==
When you want to use an USB memory stick, lets say for flashing your box with OpenPLi, there is no way of telling your stick might work, it's trial and error! Because the USB detection system in the bootloader of your receiver is very simple, there are 2 things to consider:

#It has a short device detection time, which is as it should be, because a long device detection time could result in an annoying long booting procedure. This (short device detection) causes devices whose detection takes (too) long (usb3 devices, large sticks) not to be seen in time.
#It takes the first device that is found and if you've connected multiple devices, chances are that it's not the device you want to use.

Generally speaking, small old USB sticks with less than 1Gb have a bigger change to work.

=='''Video codecs and what if you can not play a movie on your receiver'''==
Video Codecs are not needed for your receiver. The difference between your PC/Lab top and your Receiver is that your PC/Lab top uses its processor to decode the video, while your receiver uses a specialized chip. For your PC/Lap top you can therefore add new codecs by installing software, with your receiver the codecs consist of electronic circuits in the chip and therefore codecs can't be added, so only the "codecs" in the chip can be played.

So if you have a movie that can't be played, you'll have to re-code it. For this you can use programs like [https://handbrake.fr/ Handbrake]. A good choice would be h264 or h265 as a video codec and mp2, mp3 or ac3 as an audio codec.

=='''Vu+ related'''==

==='''Cable Scan issue's?''' ===

There is bug with the VU+ drivers so that a scan can not be completed if tuner D is used.

This is the issue:
input3 and input2 have no input3_choices or input4_choices so the Enigma2 doesn't try to initialize them.

/proc/stb/tsmux/input1_choices:CI0 CI1 A B
/proc/stb/tsmux/input0_choices:CI0 CI1 A B
/proc/stb/tsmux/input3:A
/proc/stb/tsmux/input2:A
/proc/stb/tsmux/input1:B
/proc/stb/tsmux/input0:AA simple solution is to initialize them manually.

Temporary solution until reboot
echo -n C > /proc/stb/tsmux/input2
echo -n D > /proc/stb/tsmux/input3

Note: VU+ should add input2_choices and input3_choices nodes.

Temporary Solution, that still works after a reboot:
Install the IPK files that are posted at: https://forums.openpli.org/topic/49214-vuplus-duo2-dvb-t2-tuner-nim-tt3l10-stopped-working/page-3#entry701207
Reboot the receiver, and the scan problems are solved.

==='''Restore Splash screen for - Factory bootlogo'''===

The file that can be found at the forum (see below) will place the original factory bootlogo back on your receiver. The content of the file needs to be placed on a USB pen drive. The file contains splash screens for the models:

duo2, solo2, solo4k, solose, ultimo, ultimo4k, vuduo4k, uno, uno4k, uno4kse, zero and the zero4k.
You do not have to pick one of the bootlogo's.. Your receiver selects only the file that must be needed. .

So the following steps must be taken:
# place the content of the zip file on the USB pendrive
# reboot your receiver
# flash the 'image' (this wil take a few seconds)
# when the flash is completed, remove the USB pendrive
# restart your receiver

Source: https://forums.openpli.org/topic/48876-herstel-splash-screens-van-vu-modellen/page-3?p=975297

=='''Zgemma related'''==

==='''Restore Splash screen for Zgemma'''===

Source: https://forums.openpli.org/topic/41521-boot-screen/#entry549387

Problems and Solutions

2018-12-01T14:50:44Z

Tech: /* Zgemma related */

=='''Crash logs'''==
Crash logs are generated during a system crash, also known as a GSOD (green screen of death). The log can give insight to the probable cause of the crash. If you want help with the content of the file, you can post it on our [https://forums.openpli.org forum]. The crash log file is named like in the example below:

enigma2_crash_3891289128.log

===The location of the crash log file when there is a HDD (Harddisk) present===
Normally the crash.log file is stored in the root of the HDD so in
/media/hdd

===The location of the crash.log file without any HDD (Harddisk) present===
Normally the crash log file is stored in the
/home/root

=='''Debugging Enigma'''==
If you want to debug and want to know what is happening in Enigma, you can start your receiver in debug mode with the following command:
root@<receiver>: init 4
root@<receiver>: ENIGMA_DEBUG_LVL=4 /usr/bin/enigma2.sh

To stop: Press CRTL-C. Enigma will halt. Then start enigma with:
root@<receiver>: init 3
Or reboot the receiver with:
root@<receiver>: reboot

'''Note:''' For '''debugging gstreamer''' with read actions stuff use: '''ENIGMA_DEBUG_LVL=4 GST_DEBUG=*soup*:6,*dvb*:6 enigma2''' 

===For easier reading (Less logging) use:===

ENIGMA_DEBUG_LVL=4 GST_DEBUG=*soup*:4,*dvb*:4 enigma2

===Writing debug log to a USB stick===
If for some reason your receiver reboots your debug log might be gone. Then plugin a USB stick in your receiver and use the command below, which writes the debug log to and USB stick
ENIGMA_DEBUG_LVL=4 enigma2 | tee /media/usb/enigma.log

=='''I cannot record with my receiver or recording with a Zapper (eg. Vu Zero / Vu Solo Se)'''==
By default some Vu+ boxes are a ''zapper'', meaning you can not record with it. If you want to record with it, you can install the "pau" plugin/extension. It is located in the
''extensions'' section of the [[Plugin_Wiki| plugin browser]].

=='''Mountmanager Problems'''==
Here are some solutions when you run into problems with mounting\sharing a medium (HDD) in your network.

===Older vs newer Kernel===
When your box uses a kernel 3.x ('''Menu-Information-About''') and you want to mount something that has a kernel 4.x your CIFS share might fail, even though you entered the data carefully, but there is a solution.

The solution is simple, you can try the following; If you make a mount with [[MountManager | Mountmanager]], change the "mount options" from "rw" to "rw, sec=ntlm", this will lower the security standard from ntlmv2 (default with kernel 4.x and up) to ntlm.

Now exit and re-mount or Reboot your box and if this was the cause, you can now access your share.

===Older vs newer SMB Protocol===
There is a similar issue regarding the version of the SMB protocol used.

There are several versions of the SMB protocol, v1, v2.0, v2.1 and v3. (see https://blogs.technet.microsoft.com/josebda/2013/10/02/windows-server-2012-r2-which-version-of-the-smb-protocol-smb-1-0-smb-2-0-smb-2-1-smb-3-0-or-smb-3-02-are-you-using/ for more in-depth information).

Recently, due to several security issues, an action has been ongoing to disable the unsafe SMBv1, not only in Windows, but also in NAS systems like Synology for example. Windows has the option to cycle through all available and allowed protocols when you want to connect to a share, so you as a user don't notice anything and don't know which protocol is used. But the Linux kernel driver doesn't. It connects using the version it has been programmed with, and if you as a user need a different version, you need to specify this in the mount options.

Up to kernel v4.13 (at the moment of writing all supported receivers), the default was SMBv1, after that, the default has been upgraded to SMBv3. So if your box has a kernel older than 4.13, and your "server" doesn't support SMBv1, you need to specify the version on the mount. Likewise, if your box runs 4.13 or higher, and your "server" doesn't support SMBv3, you also need to specify the version on the mount.

The solution is to change the SMB version used to mount, to do this in [[MountManager | Mountmanager]] change the "mount options" from "rw" to "rw, vers=3.0" (or whatever version you want to mount). You might have to try a few, if you don't know which one your server supports, but always start with the highest version.

This is a good overview on this subject: https://www.happyassassin.net/2017/11/03/linux-kernel-4-13-and-smb-protocol-version-fun/

The same is true for the authentication mechanism. This used to be NTLM, but in Kernel 3.8 the default has changed to NTLMv2, as Windows no longer supports NTLM (also because of security issues). But depending on the version and configuration of Windows (especially Windows Server), you might need to specify an alternative mechanism on the commandline too.

=='''Reset lost password'''==
In case you have lost your box password or someone else has been so 'funny' to create a password without having informed you, there are several ways to solve this issue.

I assume that you still have access via Explorer with \\boxname or \\ipaddressbox. If not, then the only 'solution' to get access again is to flash your box which is actually not a solution.

# Go to the map /etc where you find the file shadow.
# If you owe another Enigma2 box then go to the map \etc and copy there that file 'shadow'.
# Go to the box with the unknown password and paste the just copied file from the other box over your present version of shadow.

There is a second scenario to solve this.

# Go to the map /etc where you also find the file passwd.
# Select and edit the file passwd with right mouse button and select a proper editer. I use Notepad ++
# In this file the line: root: x: 0: 0: root: / root: / bin / sh or something as root: EIfidfjeSAEFKEOlasdf5ewr3rWEW: 0: 0: root: / root: / bin / sh is the actual PW. The Password field is x or the encrypted string EIfidfjeSAEFKEOlasdf5ewr3rWEW
# Delete the x or the string The line is now following: root :: 0: 0: root: / root: / bin / sh
# Save / overwrite this file and exit Notepad ++.

=='''Splash screen replacement'''==
The splashscreen is written in a limited reserved space of flash. We believe that the splash screen is not intended to be image specific, it should just show the manufacturer and/or box type information. The dimensions and type of splash file supported by the bootloader, differ per brand, and possibly even per box.
We advice to stay away from that, leave the splash screen to the bootloader, and the manufacturer.

If by some reason, let's say another image, has changed it, you can restore it to the one from the manufacturer. Do a search on the OpenPLi site using Google and type:

splash screen site:openpli.org

For the Vu+ jump to [[Problems_and_Solutions#Restore_Splash_screen_for_-_Factory_bootlogo | Restore Splash screen for Vu]]

=='''USB memory sticks working or not'''==
When you want to use an USB memory stick, lets say for flashing your box with OpenPLi, there is no way of telling your stick might work, it's trial and error! Because the USB detection system in the bootloader of your receiver is very simple, there are 2 things to consider:

#It has a short device detection time, which is as it should be, because a long device detection time could result in an annoying long booting procedure. This (short device detection) causes devices whose detection takes (too) long (usb3 devices, large sticks) not to be seen in time.
#It takes the first device that is found and if you've connected multiple devices, chances are that it's not the device you want to use.

Generally speaking, small old USB sticks with less than 1Gb have a bigger change to work.

=='''Video codecs and what if you can not play a movie on your receiver'''==
Video Codecs are not needed for your receiver. The difference between your PC/Lab top and your Receiver is that your PC/Lab top uses its processor to decode the video, while your receiver uses a specialized chip. For your PC/Lap top you can therefore add new codecs by installing software, with your receiver the codecs consist of electronic circuits in the chip and therefore codecs can't be added, so only the "codecs" in the chip can be played.

So if you have a movie that can't be played, you'll have to re-code it. For this you can use programs like [https://handbrake.fr/ Handbrake]. A good choice would be h264 or h265 as a video codec and mp2, mp3 or ac3 as an audio codec.

=='''Vu+ related'''==

==='''Cable Scan issue's?''' ===

There is bug with the VU+ drivers so that a scan can not be completed if tuner D is used.

This is the issue:
input3 and input2 have no input3_choices or input4_choices so the Enigma2 doesn't try to initialize them.

/proc/stb/tsmux/input1_choices:CI0 CI1 A B
/proc/stb/tsmux/input0_choices:CI0 CI1 A B
/proc/stb/tsmux/input3:A
/proc/stb/tsmux/input2:A
/proc/stb/tsmux/input1:B
/proc/stb/tsmux/input0:AA simple solution is to initialize them manually.

Temporary solution until reboot
echo -n C > /proc/stb/tsmux/input2
echo -n D > /proc/stb/tsmux/input3

Note: VU+ should add input2_choices and input3_choices nodes.

Temporary Solution, that still works after a reboot:
Install the IPK files that are posted at: https://forums.openpli.org/topic/49214-vuplus-duo2-dvb-t2-tuner-nim-tt3l10-stopped-working/page-3#entry701207
Reboot the receiver, and the scan problems are solved.

==='''Restore Splash screen for - Factory bootlogo'''===

The file that can be found at the forum (see below) will place the original factory bootlogo back on your receiver. The content of the file needs to be placed on a USB pen drive. The file contains splash screens for the models:

duo2, solo2, solo4k, solose, ultimo, ultimo4k, uno, uno4k, uno4kse, zero and the zero4k.
You do not have to pick one of the bootlogo's.. Your receiver selects only the file that must be needed. .

So the following steps must be taken:
# place the content of the zip file on the USB pendrive
# reboot your receiver
# flash the 'image' (this wil take a few seconds)
# when the flash is completed, remove the USB pendrive
# restart your receiver

Source: https://forums.openpli.org/topic/48876-herstel-splash-screens-van-vu-modellen/page-3#entry935371

=='''Zgemma related'''==

===''Restore Splash screen for Zgemma'''===

Source: https://forums.openpli.org/topic/41521-boot-screen/#entry549387

Problems and Solutions

2018-12-01T14:49:38Z

Tech:

=='''Crash logs'''==
Crash logs are generated during a system crash, also known as a GSOD (green screen of death). The log can give insight to the probable cause of the crash. If you want help with the content of the file, you can post it on our [https://forums.openpli.org forum]. The crash log file is named like in the example below:

enigma2_crash_3891289128.log

===The location of the crash log file when there is a HDD (Harddisk) present===
Normally the crash.log file is stored in the root of the HDD so in
/media/hdd

===The location of the crash.log file without any HDD (Harddisk) present===
Normally the crash log file is stored in the
/home/root

=='''Debugging Enigma'''==
If you want to debug and want to know what is happening in Enigma, you can start your receiver in debug mode with the following command:
root@<receiver>: init 4
root@<receiver>: ENIGMA_DEBUG_LVL=4 /usr/bin/enigma2.sh

To stop: Press CRTL-C. Enigma will halt. Then start enigma with:
root@<receiver>: init 3
Or reboot the receiver with:
root@<receiver>: reboot

'''Note:''' For '''debugging gstreamer''' with read actions stuff use: '''ENIGMA_DEBUG_LVL=4 GST_DEBUG=*soup*:6,*dvb*:6 enigma2''' 

===For easier reading (Less logging) use:===

ENIGMA_DEBUG_LVL=4 GST_DEBUG=*soup*:4,*dvb*:4 enigma2

===Writing debug log to a USB stick===
If for some reason your receiver reboots your debug log might be gone. Then plugin a USB stick in your receiver and use the command below, which writes the debug log to and USB stick
ENIGMA_DEBUG_LVL=4 enigma2 | tee /media/usb/enigma.log

=='''I cannot record with my receiver or recording with a Zapper (eg. Vu Zero / Vu Solo Se)'''==
By default some Vu+ boxes are a ''zapper'', meaning you can not record with it. If you want to record with it, you can install the "pau" plugin/extension. It is located in the
''extensions'' section of the [[Plugin_Wiki| plugin browser]].

=='''Mountmanager Problems'''==
Here are some solutions when you run into problems with mounting\sharing a medium (HDD) in your network.

===Older vs newer Kernel===
When your box uses a kernel 3.x ('''Menu-Information-About''') and you want to mount something that has a kernel 4.x your CIFS share might fail, even though you entered the data carefully, but there is a solution.

The solution is simple, you can try the following; If you make a mount with [[MountManager | Mountmanager]], change the "mount options" from "rw" to "rw, sec=ntlm", this will lower the security standard from ntlmv2 (default with kernel 4.x and up) to ntlm.

Now exit and re-mount or Reboot your box and if this was the cause, you can now access your share.

===Older vs newer SMB Protocol===
There is a similar issue regarding the version of the SMB protocol used.

There are several versions of the SMB protocol, v1, v2.0, v2.1 and v3. (see https://blogs.technet.microsoft.com/josebda/2013/10/02/windows-server-2012-r2-which-version-of-the-smb-protocol-smb-1-0-smb-2-0-smb-2-1-smb-3-0-or-smb-3-02-are-you-using/ for more in-depth information).

Recently, due to several security issues, an action has been ongoing to disable the unsafe SMBv1, not only in Windows, but also in NAS systems like Synology for example. Windows has the option to cycle through all available and allowed protocols when you want to connect to a share, so you as a user don't notice anything and don't know which protocol is used. But the Linux kernel driver doesn't. It connects using the version it has been programmed with, and if you as a user need a different version, you need to specify this in the mount options.

Up to kernel v4.13 (at the moment of writing all supported receivers), the default was SMBv1, after that, the default has been upgraded to SMBv3. So if your box has a kernel older than 4.13, and your "server" doesn't support SMBv1, you need to specify the version on the mount. Likewise, if your box runs 4.13 or higher, and your "server" doesn't support SMBv3, you also need to specify the version on the mount.

The solution is to change the SMB version used to mount, to do this in [[MountManager | Mountmanager]] change the "mount options" from "rw" to "rw, vers=3.0" (or whatever version you want to mount). You might have to try a few, if you don't know which one your server supports, but always start with the highest version.

This is a good overview on this subject: https://www.happyassassin.net/2017/11/03/linux-kernel-4-13-and-smb-protocol-version-fun/

The same is true for the authentication mechanism. This used to be NTLM, but in Kernel 3.8 the default has changed to NTLMv2, as Windows no longer supports NTLM (also because of security issues). But depending on the version and configuration of Windows (especially Windows Server), you might need to specify an alternative mechanism on the commandline too.

=='''Reset lost password'''==
In case you have lost your box password or someone else has been so 'funny' to create a password without having informed you, there are several ways to solve this issue.

I assume that you still have access via Explorer with \\boxname or \\ipaddressbox. If not, then the only 'solution' to get access again is to flash your box which is actually not a solution.

# Go to the map /etc where you find the file shadow.
# If you owe another Enigma2 box then go to the map \etc and copy there that file 'shadow'.
# Go to the box with the unknown password and paste the just copied file from the other box over your present version of shadow.

There is a second scenario to solve this.

# Go to the map /etc where you also find the file passwd.
# Select and edit the file passwd with right mouse button and select a proper editer. I use Notepad ++
# In this file the line: root: x: 0: 0: root: / root: / bin / sh or something as root: EIfidfjeSAEFKEOlasdf5ewr3rWEW: 0: 0: root: / root: / bin / sh is the actual PW. The Password field is x or the encrypted string EIfidfjeSAEFKEOlasdf5ewr3rWEW
# Delete the x or the string The line is now following: root :: 0: 0: root: / root: / bin / sh
# Save / overwrite this file and exit Notepad ++.

=='''Splash screen replacement'''==
The splashscreen is written in a limited reserved space of flash. We believe that the splash screen is not intended to be image specific, it should just show the manufacturer and/or box type information. The dimensions and type of splash file supported by the bootloader, differ per brand, and possibly even per box.
We advice to stay away from that, leave the splash screen to the bootloader, and the manufacturer.

If by some reason, let's say another image, has changed it, you can restore it to the one from the manufacturer. Do a search on the OpenPLi site using Google and type:

splash screen site:openpli.org

For the Vu+ jump to [[Problems_and_Solutions#Restore_Splash_screen_for_-_Factory_bootlogo | Restore Splash screen for Vu]]

=='''USB memory sticks working or not'''==
When you want to use an USB memory stick, lets say for flashing your box with OpenPLi, there is no way of telling your stick might work, it's trial and error! Because the USB detection system in the bootloader of your receiver is very simple, there are 2 things to consider:

#It has a short device detection time, which is as it should be, because a long device detection time could result in an annoying long booting procedure. This (short device detection) causes devices whose detection takes (too) long (usb3 devices, large sticks) not to be seen in time.
#It takes the first device that is found and if you've connected multiple devices, chances are that it's not the device you want to use.

Generally speaking, small old USB sticks with less than 1Gb have a bigger change to work.

=='''Video codecs and what if you can not play a movie on your receiver'''==
Video Codecs are not needed for your receiver. The difference between your PC/Lab top and your Receiver is that your PC/Lab top uses its processor to decode the video, while your receiver uses a specialized chip. For your PC/Lap top you can therefore add new codecs by installing software, with your receiver the codecs consist of electronic circuits in the chip and therefore codecs can't be added, so only the "codecs" in the chip can be played.

So if you have a movie that can't be played, you'll have to re-code it. For this you can use programs like [https://handbrake.fr/ Handbrake]. A good choice would be h264 or h265 as a video codec and mp2, mp3 or ac3 as an audio codec.

=='''Vu+ related'''==

==='''Cable Scan issue's?''' ===

There is bug with the VU+ drivers so that a scan can not be completed if tuner D is used.

This is the issue:
input3 and input2 have no input3_choices or input4_choices so the Enigma2 doesn't try to initialize them.

/proc/stb/tsmux/input1_choices:CI0 CI1 A B
/proc/stb/tsmux/input0_choices:CI0 CI1 A B
/proc/stb/tsmux/input3:A
/proc/stb/tsmux/input2:A
/proc/stb/tsmux/input1:B
/proc/stb/tsmux/input0:AA simple solution is to initialize them manually.

Temporary solution until reboot
echo -n C > /proc/stb/tsmux/input2
echo -n D > /proc/stb/tsmux/input3

Note: VU+ should add input2_choices and input3_choices nodes.

Temporary Solution, that still works after a reboot:
Install the IPK files that are posted at: https://forums.openpli.org/topic/49214-vuplus-duo2-dvb-t2-tuner-nim-tt3l10-stopped-working/page-3#entry701207
Reboot the receiver, and the scan problems are solved.

==='''Restore Splash screen for - Factory bootlogo'''===

The file that can be found at the forum (see below) will place the original factory bootlogo back on your receiver. The content of the file needs to be placed on a USB pen drive. The file contains splash screens for the models:

duo2, solo2, solo4k, solose, ultimo, ultimo4k, uno, uno4k, uno4kse, zero and the zero4k.
You do not have to pick one of the bootlogo's.. Your receiver selects only the file that must be needed. .

So the following steps must be taken:
# place the content of the zip file on the USB pendrive
# reboot your receiver
# flash the 'image' (this wil take a few seconds)
# when the flash is completed, remove the USB pendrive
# restart your receiver

Source: https://forums.openpli.org/topic/48876-herstel-splash-screens-van-vu-modellen/page-3#entry935371

=='''Zgemma related'''==

===''Restore Splash screen for Zgemma'''===

Source: https://forums.openpli.org/topic/41521-boot-screen/

Problems and Solutions

2018-12-01T14:47:24Z

Tech:

=='''Crash logs'''==
Crash logs are generated during a system crash, also known as a GSOD (green screen of death). The log can give insight to the probable cause of the crash. If you want help with the content of the file, you can post it on our [https://forums.openpli.org forum]. The crash log file is named like in the example below:

enigma2_crash_3891289128.log

===The location of the crash log file when there is a HDD (Harddisk) present===
Normally the crash.log file is stored in the root of the HDD so in
/media/hdd

===The location of the crash.log file without any HDD (Harddisk) present===
Normally the crash log file is stored in the
/home/root

=='''Debugging Enigma'''==
If you want to debug and want to know what is happening in Enigma, you can start your receiver in debug mode with the following command:
root@<receiver>: init 4
root@<receiver>: ENIGMA_DEBUG_LVL=4 /usr/bin/enigma2.sh

To stop: Press CRTL-C. Enigma will halt. Then start enigma with:
root@<receiver>: init 3
Or reboot the receiver with:
root@<receiver>: reboot

'''Note:''' For '''debugging gstreamer''' with read actions stuff use: '''ENIGMA_DEBUG_LVL=4 GST_DEBUG=*soup*:6,*dvb*:6 enigma2''' 

===For easier reading (Less logging) use:===

ENIGMA_DEBUG_LVL=4 GST_DEBUG=*soup*:4,*dvb*:4 enigma2

===Writing debug log to a USB stick===
If for some reason your receiver reboots your debug log might be gone. Then plugin a USB stick in your receiver and use the command below, which writes the debug log to and USB stick
ENIGMA_DEBUG_LVL=4 enigma2 | tee /media/usb/enigma.log

=='''I cannot record with my receiver or recording with a Zapper (eg. Vu Zero / Vu Solo Se)'''==
By default some Vu+ boxes are a ''zapper'', meaning you can not record with it. If you want to record with it, you can install the "pau" plugin/extension. It is located in the
''extensions'' section of the [[Plugin_Wiki| plugin browser]].

=='''Mountmanager Problems'''==
Here are some solutions when you run into problems with mounting\sharing a medium (HDD) in your network.

===Older vs newer Kernel===
When your box uses a kernel 3.x ('''Menu-Information-About''') and you want to mount something that has a kernel 4.x your CIFS share might fail, even though you entered the data carefully, but there is a solution.

The solution is simple, you can try the following; If you make a mount with [[MountManager | Mountmanager]], change the "mount options" from "rw" to "rw, sec=ntlm", this will lower the security standard from ntlmv2 (default with kernel 4.x and up) to ntlm.

Now exit and re-mount or Reboot your box and if this was the cause, you can now access your share.

===Older vs newer SMB Protocol===
There is a similar issue regarding the version of the SMB protocol used.

There are several versions of the SMB protocol, v1, v2.0, v2.1 and v3. (see https://blogs.technet.microsoft.com/josebda/2013/10/02/windows-server-2012-r2-which-version-of-the-smb-protocol-smb-1-0-smb-2-0-smb-2-1-smb-3-0-or-smb-3-02-are-you-using/ for more in-depth information).

Recently, due to several security issues, an action has been ongoing to disable the unsafe SMBv1, not only in Windows, but also in NAS systems like Synology for example. Windows has the option to cycle through all available and allowed protocols when you want to connect to a share, so you as a user don't notice anything and don't know which protocol is used. But the Linux kernel driver doesn't. It connects using the version it has been programmed with, and if you as a user need a different version, you need to specify this in the mount options.

Up to kernel v4.13 (at the moment of writing all supported receivers), the default was SMBv1, after that, the default has been upgraded to SMBv3. So if your box has a kernel older than 4.13, and your "server" doesn't support SMBv1, you need to specify the version on the mount. Likewise, if your box runs 4.13 or higher, and your "server" doesn't support SMBv3, you also need to specify the version on the mount.

The solution is to change the SMB version used to mount, to do this in [[MountManager | Mountmanager]] change the "mount options" from "rw" to "rw, vers=3.0" (or whatever version you want to mount). You might have to try a few, if you don't know which one your server supports, but always start with the highest version.

This is a good overview on this subject: https://www.happyassassin.net/2017/11/03/linux-kernel-4-13-and-smb-protocol-version-fun/

The same is true for the authentication mechanism. This used to be NTLM, but in Kernel 3.8 the default has changed to NTLMv2, as Windows no longer supports NTLM (also because of security issues). But depending on the version and configuration of Windows (especially Windows Server), you might need to specify an alternative mechanism on the commandline too.

=='''Reset lost password'''==
In case you have lost your box password or someone else has been so 'funny' to create a password without having informed you, there are several ways to solve this issue.

I assume that you still have access via Explorer with \\boxname or \\ipaddressbox. If not, then the only 'solution' to get access again is to flash your box which is actually not a solution.

# Go to the map /etc where you find the file shadow.
# If you owe another Enigma2 box then go to the map \etc and copy there that file 'shadow'.
# Go to the box with the unknown password and paste the just copied file from the other box over your present version of shadow.

There is a second scenario to solve this.

# Go to the map /etc where you also find the file passwd.
# Select and edit the file passwd with right mouse button and select a proper editer. I use Notepad ++
# In this file the line: root: x: 0: 0: root: / root: / bin / sh or something as root: EIfidfjeSAEFKEOlasdf5ewr3rWEW: 0: 0: root: / root: / bin / sh is the actual PW. The Password field is x or the encrypted string EIfidfjeSAEFKEOlasdf5ewr3rWEW
# Delete the x or the string The line is now following: root :: 0: 0: root: / root: / bin / sh
# Save / overwrite this file and exit Notepad ++.

=='''Splash screen replacement'''==
The splashscreen is written in a limited reserved space of flash. We believe that the splash screen is not intended to be image specific, it should just show the manufacturer and/or box type information. The dimensions and type of splash file supported by the bootloader, differ per brand, and possibly even per box.
We advice to stay away from that, leave the splash screen to the bootloader, and the manufacturer.

If by some reason, let's say another image, has changed it, you can restore it to the one from the manufacturer. Do a search on the OpenPLi site using Google and type:

splash screen site:openpli.org

For the Vu+ jump to [[Problems_and_Solutions#Restore_Splash_screen_for_-_Factory_bootlogo | Restore Splash screen for Vu]]

=='''USB memory sticks working or not'''==
When you want to use an USB memory stick, lets say for flashing your box with OpenPLi, there is no way of telling your stick might work, it's trial and error! Because the USB detection system in the bootloader of your receiver is very simple, there are 2 things to consider:

#It has a short device detection time, which is as it should be, because a long device detection time could result in an annoying long booting procedure. This (short device detection) causes devices whose detection takes (too) long (usb3 devices, large sticks) not to be seen in time.
#It takes the first device that is found and if you've connected multiple devices, chances are that it's not the device you want to use.

Generally speaking, small old USB sticks with less than 1Gb have a bigger change to work.

=='''Video codecs and what if you can not play a movie on your receiver'''==
Video Codecs are not needed for your receiver. The difference between your PC/Lab top and your Receiver is that your PC/Lab top uses its processor to decode the video, while your receiver uses a specialized chip. For your PC/Lap top you can therefore add new codecs by installing software, with your receiver the codecs consist of electronic circuits in the chip and therefore codecs can't be added, so only the "codecs" in the chip can be played.

So if you have a movie that can't be played, you'll have to re-code it. For this you can use programs like [https://handbrake.fr/ Handbrake]. A good choice would be h264 or h265 as a video codec and mp2, mp3 or ac3 as an audio codec.

===''Restore Splash screen for Zgemma'''===

Source: https://forums.openpli.org/topic/41521-boot-screen/

=='''Vu+ related'''==

==='''Cable Scan issue's?''' ===

There is bug with the VU+ drivers so that a scan can not be completed if tuner D is used.

This is the issue:
input3 and input2 have no input3_choices or input4_choices so the Enigma2 doesn't try to initialize them.

/proc/stb/tsmux/input1_choices:CI0 CI1 A B
/proc/stb/tsmux/input0_choices:CI0 CI1 A B
/proc/stb/tsmux/input3:A
/proc/stb/tsmux/input2:A
/proc/stb/tsmux/input1:B
/proc/stb/tsmux/input0:AA simple solution is to initialize them manually.

Temporary solution until reboot
echo -n C > /proc/stb/tsmux/input2
echo -n D > /proc/stb/tsmux/input3

Note: VU+ should add input2_choices and input3_choices nodes.

Temporary Solution, that still works after a reboot:
Install the IPK files that are posted at: https://forums.openpli.org/topic/49214-vuplus-duo2-dvb-t2-tuner-nim-tt3l10-stopped-working/page-3#entry701207
Reboot the receiver, and the scan problems are solved.

==='''Restore Splash screen for - Factory bootlogo'''===

The file that can be found at the forum (see below) will place the original factory bootlogo back on your receiver. The content of the file needs to be placed on a USB pen drive. The file contains splash screens for the models:

duo2, solo2, solo4k, solose, ultimo, ultimo4k, uno, uno4k, uno4kse, zero and the zero4k.
You do not have to pick one of the bootlogo's.. Your receiver selects only the file that must be needed. .

So the following steps must be taken:
# place the content of the zip file on the USB pendrive
# reboot your receiver
# flash the 'image' (this wil take a few seconds)
# when the flash is completed, remove the USB pendrive
# restart your receiver

Source: https://forums.openpli.org/topic/48876-herstel-splash-screens-van-vu-modellen/page-3#entry935371

Problems and Solutions

2018-12-01T14:45:19Z

Tech:

=='''Crash logs'''==
Crash logs are generated during a system crash, also known as a GSOD (green screen of death). The log can give insight to the probable cause of the crash. If you want help with the content of the file, you can post it on our [https://forums.openpli.org forum]. The crash log file is named like in the example below:

enigma2_crash_3891289128.log

===The location of the crash log file when there is a HDD (Harddisk) present===
Normally the crash.log file is stored in the root of the HDD so in
/media/hdd

===The location of the crash.log file without any HDD (Harddisk) present===
Normally the crash log file is stored in the
/home/root

=='''Debugging Enigma'''==
If you want to debug and want to know what is happening in Enigma, you can start your receiver in debug mode with the following command:
root@<receiver>: init 4
root@<receiver>: ENIGMA_DEBUG_LVL=4 /usr/bin/enigma2.sh

To stop: Press CRTL-C. Enigma will halt. Then start enigma with:
root@<receiver>: init 3
Or reboot the receiver with:
root@<receiver>: reboot

'''Note:''' For '''debugging gstreamer''' with read actions stuff use: '''ENIGMA_DEBUG_LVL=4 GST_DEBUG=*soup*:6,*dvb*:6 enigma2''' 

===For easier reading (Less logging) use:===

ENIGMA_DEBUG_LVL=4 GST_DEBUG=*soup*:4,*dvb*:4 enigma2

===Writing debug log to a USB stick===
If for some reason your receiver reboots your debug log might be gone. Then plugin a USB stick in your receiver and use the command below, which writes the debug log to and USB stick
ENIGMA_DEBUG_LVL=4 enigma2 | tee /media/usb/enigma.log

=='''I cannot record with my receiver or recording with a Zapper (eg. Vu Zero / Vu Solo Se)'''==
By default some Vu+ boxes are a ''zapper'', meaning you can not record with it. If you want to record with it, you can install the "pau" plugin/extension. It is located in the
''extensions'' section of the [[Plugin_Wiki| plugin browser]].

=='''Mountmanager Problems'''==
Here are some solutions when you run into problems with mounting\sharing a medium (HDD) in your network.

===Older vs newer Kernel===
When your box uses a kernel 3.x ('''Menu-Information-About''') and you want to mount something that has a kernel 4.x your CIFS share might fail, even though you entered the data carefully, but there is a solution.

The solution is simple, you can try the following; If you make a mount with [[MountManager | Mountmanager]], change the "mount options" from "rw" to "rw, sec=ntlm", this will lower the security standard from ntlmv2 (default with kernel 4.x and up) to ntlm.

Now exit and re-mount or Reboot your box and if this was the cause, you can now access your share.

===Older vs newer SMB Protocol===
There is a similar issue regarding the version of the SMB protocol used.

There are several versions of the SMB protocol, v1, v2.0, v2.1 and v3. (see https://blogs.technet.microsoft.com/josebda/2013/10/02/windows-server-2012-r2-which-version-of-the-smb-protocol-smb-1-0-smb-2-0-smb-2-1-smb-3-0-or-smb-3-02-are-you-using/ for more in-depth information).

Recently, due to several security issues, an action has been ongoing to disable the unsafe SMBv1, not only in Windows, but also in NAS systems like Synology for example. Windows has the option to cycle through all available and allowed protocols when you want to connect to a share, so you as a user don't notice anything and don't know which protocol is used. But the Linux kernel driver doesn't. It connects using the version it has been programmed with, and if you as a user need a different version, you need to specify this in the mount options.

Up to kernel v4.13 (at the moment of writing all supported receivers), the default was SMBv1, after that, the default has been upgraded to SMBv3. So if your box has a kernel older than 4.13, and your "server" doesn't support SMBv1, you need to specify the version on the mount. Likewise, if your box runs 4.13 or higher, and your "server" doesn't support SMBv3, you also need to specify the version on the mount.

The solution is to change the SMB version used to mount, to do this in [[MountManager | Mountmanager]] change the "mount options" from "rw" to "rw, vers=3.0" (or whatever version you want to mount). You might have to try a few, if you don't know which one your server supports, but always start with the highest version.

This is a good overview on this subject: https://www.happyassassin.net/2017/11/03/linux-kernel-4-13-and-smb-protocol-version-fun/

The same is true for the authentication mechanism. This used to be NTLM, but in Kernel 3.8 the default has changed to NTLMv2, as Windows no longer supports NTLM (also because of security issues). But depending on the version and configuration of Windows (especially Windows Server), you might need to specify an alternative mechanism on the commandline too.

=='''Reset lost password'''==
In case you have lost your box password or someone else has been so 'funny' to create a password without having informed you, there are several ways to solve this issue.

I assume that you still have access via Explorer with \\boxname or \\ipaddressbox. If not, then the only 'solution' to get access again is to flash your box which is actually not a solution.

# Go to the map /etc where you find the file shadow.
# If you owe another Enigma2 box then go to the map \etc and copy there that file 'shadow'.
# Go to the box with the unknown password and paste the just copied file from the other box over your present version of shadow.

There is a second scenario to solve this.

# Go to the map /etc where you also find the file passwd.
# Select and edit the file passwd with right mouse button and select a proper editer. I use Notepad ++
# In this file the line: root: x: 0: 0: root: / root: / bin / sh or something as root: EIfidfjeSAEFKEOlasdf5ewr3rWEW: 0: 0: root: / root: / bin / sh is the actual PW. The Password field is x or the encrypted string EIfidfjeSAEFKEOlasdf5ewr3rWEW
# Delete the x or the string The line is now following: root :: 0: 0: root: / root: / bin / sh
# Save / overwrite this file and exit Notepad ++.

=='''Splash screen replacement'''==
The splashscreen is written in a limited reserved space of flash. We believe that the splash screen is not intended to be image specific, it should just show the manufacturer and/or box type information. The dimensions and type of splash file supported by the bootloader, differ per brand, and possibly even per box.
We advice to stay away from that, leave the splash screen to the bootloader, and the manufacturer.

If by some reason, let's say another image, has changed it, you can restore it to the one from the manufacturer. Do a search on the OpenPLi site using Google and type:

splash screen site:openpli.org

For the Vu+ jump to [[Problems_and_Solutions#Restore_Splash_screen_for_-_Factory_bootlogo | Restore Splash screen for Vu]]

=='''USB memory sticks working or not'''==
When you want to use an USB memory stick, lets say for flashing your box with OpenPLi, there is no way of telling your stick might work, it's trial and error! Because the USB detection system in the bootloader of your receiver is very simple, there are 2 things to consider:

#It has a short device detection time, which is as it should be, because a long device detection time could result in an annoying long booting procedure. This (short device detection) causes devices whose detection takes (too) long (usb3 devices, large sticks) not to be seen in time.
#It takes the first device that is found and if you've connected multiple devices, chances are that it's not the device you want to use.

Generally speaking, small old USB sticks with less than 1Gb have a bigger change to work.

=='''Video codecs and what if you can not play a movie on your receiver'''==
Video Codecs are not needed for your receiver. The difference between your PC/Lab top and your Receiver is that your PC/Lab top uses its processor to decode the video, while your receiver uses a specialized chip. For your PC/Lap top you can therefore add new codecs by installing software, with your receiver the codecs consist of electronic circuits in the chip and therefore codecs can't be added, so only the "codecs" in the chip can be played.

So if you have a movie that can't be played, you'll have to re-code it. For this you can use programs like [https://handbrake.fr/ Handbrake]. A good choice would be h264 or h265 as a video codec and mp2, mp3 or ac3 as an audio codec.

=='''Vu+ related'''==

==='''Cable Scan issue's?''' ===

There is bug with the VU+ drivers so that a scan can not be completed if tuner D is used.

This is the issue:
input3 and input2 have no input3_choices or input4_choices so the Enigma2 doesn't try to initialize them.

/proc/stb/tsmux/input1_choices:CI0 CI1 A B
/proc/stb/tsmux/input0_choices:CI0 CI1 A B
/proc/stb/tsmux/input3:A
/proc/stb/tsmux/input2:A
/proc/stb/tsmux/input1:B
/proc/stb/tsmux/input0:AA simple solution is to initialize them manually.

Temporary solution until reboot
echo -n C > /proc/stb/tsmux/input2
echo -n D > /proc/stb/tsmux/input3

Note: VU+ should add input2_choices and input3_choices nodes.

Temporary Solution, that still works after a reboot:
Install the IPK files that are posted at: https://forums.openpli.org/topic/49214-vuplus-duo2-dvb-t2-tuner-nim-tt3l10-stopped-working/page-3#entry701207
Reboot the receiver, and the scan problems are solved.

==='''Restore Splash screen for - Factory bootlogo'''===

The file that can be found at the forum (see below) will place the original factory bootlogo back on your receiver. The content of the file needs to be placed on a USB pen drive. The file contains splash screens for the models:

duo2, solo2, solo4k, solose, ultimo, ultimo4k, uno, uno4k, uno4kse, zero and the zero4k.
You do not have to pick one of the bootlogo's.. Your receiver selects only the file that must be needed. .

So the following steps must be taken:
# place the content of the zip file on the USB pendrive
# reboot your receiver
# flash the 'image' (this wil take a few seconds)
# when the flash is completed, remove the USB pendrive
# restart your receiver

Source: https://forums.openpli.org/topic/48876-herstel-splash-screens-van-vu-modellen/page-3#entry935371

===Restore Splash screen for Zgemma===

Source: https://forums.openpli.org/topic/41521-boot-screen/

Problems and Solutions

2018-12-01T14:44:14Z

Tech: added zgemma splash instructions

=='''Crash logs'''==
Crash logs are generated during a system crash, also known as a GSOD (green screen of death). The log can give insight to the probable cause of the crash. If you want help with the content of the file, you can post it on our [https://forums.openpli.org forum]. The crash log file is named like in the example below:

enigma2_crash_3891289128.log

===The location of the crash log file when there is a HDD (Harddisk) present===
Normally the crash.log file is stored in the root of the HDD so in
/media/hdd

===The location of the crash.log file without any HDD (Harddisk) present===
Normally the crash log file is stored in the
/home/root

=='''Debugging Enigma'''==
If you want to debug and want to know what is happening in Enigma, you can start your receiver in debug mode with the following command:
root@<receiver>: init 4
root@<receiver>: ENIGMA_DEBUG_LVL=4 /usr/bin/enigma2.sh

To stop: Press CRTL-C. Enigma will halt. Then start enigma with:
root@<receiver>: init 3
Or reboot the receiver with:
root@<receiver>: reboot

'''Note:''' For '''debugging gstreamer''' with read actions stuff use: '''ENIGMA_DEBUG_LVL=4 GST_DEBUG=*soup*:6,*dvb*:6 enigma2''' 

===For easier reading (Less logging) use:===

ENIGMA_DEBUG_LVL=4 GST_DEBUG=*soup*:4,*dvb*:4 enigma2

===Writing debug log to a USB stick===
If for some reason your receiver reboots your debug log might be gone. Then plugin a USB stick in your receiver and use the command below, which writes the debug log to and USB stick
ENIGMA_DEBUG_LVL=4 enigma2 | tee /media/usb/enigma.log

=='''I cannot record with my receiver or recording with a Zapper (eg. Vu Zero / Vu Solo Se)'''==
By default some Vu+ boxes are a ''zapper'', meaning you can not record with it. If you want to record with it, you can install the "pau" plugin/extension. It is located in the
''extensions'' section of the [[Plugin_Wiki| plugin browser]].

=='''Mountmanager Problems'''==
Here are some solutions when you run into problems with mounting\sharing a medium (HDD) in your network.

===Older vs newer Kernel===
When your box uses a kernel 3.x ('''Menu-Information-About''') and you want to mount something that has a kernel 4.x your CIFS share might fail, even though you entered the data carefully, but there is a solution.

The solution is simple, you can try the following; If you make a mount with [[MountManager | Mountmanager]], change the "mount options" from "rw" to "rw, sec=ntlm", this will lower the security standard from ntlmv2 (default with kernel 4.x and up) to ntlm.

Now exit and re-mount or Reboot your box and if this was the cause, you can now access your share.

===Older vs newer SMB Protocol===
There is a similar issue regarding the version of the SMB protocol used.

There are several versions of the SMB protocol, v1, v2.0, v2.1 and v3. (see https://blogs.technet.microsoft.com/josebda/2013/10/02/windows-server-2012-r2-which-version-of-the-smb-protocol-smb-1-0-smb-2-0-smb-2-1-smb-3-0-or-smb-3-02-are-you-using/ for more in-depth information).

Recently, due to several security issues, an action has been ongoing to disable the unsafe SMBv1, not only in Windows, but also in NAS systems like Synology for example. Windows has the option to cycle through all available and allowed protocols when you want to connect to a share, so you as a user don't notice anything and don't know which protocol is used. But the Linux kernel driver doesn't. It connects using the version it has been programmed with, and if you as a user need a different version, you need to specify this in the mount options.

Up to kernel v4.13 (at the moment of writing all supported receivers), the default was SMBv1, after that, the default has been upgraded to SMBv3. So if your box has a kernel older than 4.13, and your "server" doesn't support SMBv1, you need to specify the version on the mount. Likewise, if your box runs 4.13 or higher, and your "server" doesn't support SMBv3, you also need to specify the version on the mount.

The solution is to change the SMB version used to mount, to do this in [[MountManager | Mountmanager]] change the "mount options" from "rw" to "rw, vers=3.0" (or whatever version you want to mount). You might have to try a few, if you don't know which one your server supports, but always start with the highest version.

This is a good overview on this subject: https://www.happyassassin.net/2017/11/03/linux-kernel-4-13-and-smb-protocol-version-fun/

The same is true for the authentication mechanism. This used to be NTLM, but in Kernel 3.8 the default has changed to NTLMv2, as Windows no longer supports NTLM (also because of security issues). But depending on the version and configuration of Windows (especially Windows Server), you might need to specify an alternative mechanism on the commandline too.

=='''Reset lost password'''==
In case you have lost your box password or someone else has been so 'funny' to create a password without having informed you, there are several ways to solve this issue.

I assume that you still have access via Explorer with \\boxname or \\ipaddressbox. If not, then the only 'solution' to get access again is to flash your box which is actually not a solution.

# Go to the map /etc where you find the file shadow.
# If you owe another Enigma2 box then go to the map \etc and copy there that file 'shadow'.
# Go to the box with the unknown password and paste the just copied file from the other box over your present version of shadow.

There is a second scenario to solve this.

# Go to the map /etc where you also find the file passwd.
# Select and edit the file passwd with right mouse button and select a proper editer. I use Notepad ++
# In this file the line: root: x: 0: 0: root: / root: / bin / sh or something as root: EIfidfjeSAEFKEOlasdf5ewr3rWEW: 0: 0: root: / root: / bin / sh is the actual PW. The Password field is x or the encrypted string EIfidfjeSAEFKEOlasdf5ewr3rWEW
# Delete the x or the string The line is now following: root :: 0: 0: root: / root: / bin / sh
# Save / overwrite this file and exit Notepad ++.

=='''Splash screen replacement'''==
The splashscreen is written in a limited reserved space of flash. We believe that the splash screen is not intended to be image specific, it should just show the manufacturer and/or box type information. The dimensions and type of splash file supported by the bootloader, differ per brand, and possibly even per box.
We advice to stay away from that, leave the splash screen to the bootloader, and the manufacturer.

If by some reason, let's say another image, has changed it, you can restore it to the one from the manufacturer. Do a search on the OpenPLi site using Google and type:

splash screen site:openpli.org

For the Vu+ jump to [[Problems_and_Solutions#Restore_Splash_screen_for_-_Factory_bootlogo | Restore Splash screen for Vu]]

=='''USB memory sticks working or not'''==
When you want to use an USB memory stick, lets say for flashing your box with OpenPLi, there is no way of telling your stick might work, it's trial and error! Because the USB detection system in the bootloader of your receiver is very simple, there are 2 things to consider:

#It has a short device detection time, which is as it should be, because a long device detection time could result in an annoying long booting procedure. This (short device detection) causes devices whose detection takes (too) long (usb3 devices, large sticks) not to be seen in time.
#It takes the first device that is found and if you've connected multiple devices, chances are that it's not the device you want to use.

Generally speaking, small old USB sticks with less than 1Gb have a bigger change to work.

=='''Video codecs and what if you can not play a movie on your receiver'''==
Video Codecs are not needed for your receiver. The difference between your PC/Lab top and your Receiver is that your PC/Lab top uses its processor to decode the video, while your receiver uses a specialized chip. For your PC/Lap top you can therefore add new codecs by installing software, with your receiver the codecs consist of electronic circuits in the chip and therefore codecs can't be added, so only the "codecs" in the chip can be played.

So if you have a movie that can't be played, you'll have to re-code it. For this you can use programs like [https://handbrake.fr/ Handbrake]. A good choice would be h264 or h265 as a video codec and mp2, mp3 or ac3 as an audio codec.

=='''Vu+ related'''==

==='''Cable Scan issue's?''' ===

There is bug with the VU+ drivers so that a scan can not be completed if tuner D is used.

This is the issue:
input3 and input2 have no input3_choices or input4_choices so the Enigma2 doesn't try to initialize them.

/proc/stb/tsmux/input1_choices:CI0 CI1 A B
/proc/stb/tsmux/input0_choices:CI0 CI1 A B
/proc/stb/tsmux/input3:A
/proc/stb/tsmux/input2:A
/proc/stb/tsmux/input1:B
/proc/stb/tsmux/input0:AA simple solution is to initialize them manually.

Temporary solution until reboot
echo -n C > /proc/stb/tsmux/input2
echo -n D > /proc/stb/tsmux/input3

Note: VU+ should add input2_choices and input3_choices nodes.

Temporary Solution, that still works after a reboot:
Install the IPK files that are posted at: https://forums.openpli.org/topic/49214-vuplus-duo2-dvb-t2-tuner-nim-tt3l10-stopped-working/page-3#entry701207
Reboot the receiver, and the scan problems are solved.

==='''Restore Splash screen for - Factory bootlogo'''===

The file that can be found at the forum (see below) will place the original factory bootlogo back on your receiver. The content of the file needs to be placed on a USB pen drive. The file contains splash screens for the models:

duo2, solo2, solo4k, solose, ultimo, ultimo4k, uno, uno4k, uno4kse, zero and the zero4k.
You do not have to pick one of the bootlogo's.. Your receiver selects only the file that must be needed. .

So the following steps must be taken:
# place the content of the zip file on the USB pendrive
# reboot your receiver
# flash the 'image' (this wil take a few seconds)
# when the flash is completed, remove the USB pendrive
# restart your receiver

Source: https://forums.openpli.org/topic/48876-herstel-splash-screens-van-vu-modellen/page-3#entry935371

==='''Restore Splash screen for Zgemma'''===

Source: https://forums.openpli.org/topic/41521-boot-screen/

Cable:Ziggo

2017-07-02T06:42:52Z

Tech:

'''Former UPC also known as Ziggo-East''' 
If your contract/customer code does not start with a 1, then the following information is valid. Enter the following settings: 

Frequency: 164.000 
Symbolrate: 6900 
Modulation: QAM64 or QAM256 - Note: This is changed since June 14th 
Network ID: 05555 for FTV and Scrambled channels 
Network ID: 04444 for FTV channels 

----
'''Ziggo before the merger also known as Ziggo-West''' 
If your contract/customer code start with a 1, then the following information is valid. Enter the following settings: 

Frequency: 474.000 
Symbolrate: 6875 
Modulation: QAM64 
Network ID: 05555 for FTV and Scrambled channels 
Network ID: 04444 for FTV channels 

----

At the Ziggo website: https://www.ziggo.nl/klantenservice/televisie-radio/digitale-tv/activeringscode-frequentie-netwerk-id-instellen/#netwerk-id-philips
there is a notice that Philips TV sets from the year 2010 with the product type 6000 or higher, do not hold the network code 5555 for more than a few days. To workaround this problem Ziggo has kept the old network-ID's active. To continue watching channels, you must enter the following code:

{| class="wikitable"
|-
! Region !! Network-ID
|-
| Noord-Holland || 43136
|-
| Flevoland || 43138
|-
| Friesland || 43140
|-
| Gelderland || 43142
|-
| Brabant || 43144
|-
| Zuid-Holland || 43146
|-
| ||
|-
| Alkmaar || 43192
|-
| Alphen a/d Rijn || 43185
|-
| Amersfoort || 43195
|-
| Breda || 43191
|-
| Capelle || 43194
|-
| Den Bosch || 43198
|-
| Den Haag || 43186
|-
| Driebergen || 43189
|-
| Emmen || 43208
|-
| Gorichem || 43190
|-
| Gorredijk || 43209
|-
| Groningen || 43206
|-
| Hengelo || 43211
|-
| Hilversum || 43196
|-
| Hoogeveen || 43205
|-
| Mill || 43197
|-
| Roermond || 43202
|-
| Roosendaal || 43199
|-
| Sassenheim || 43184
|-
| Schoonbron || 43203
|-
| Sneek || 43210
|-
| Tilburg || 43200
|-
| Utrecht || 43187
|-
| Veenendaal || 43188
|-
| Velsen || 43193
|-
| Venlo || 43201
|-
| Winschoten || 43207
|-
| Zwolle || 43204
|-
|}

'''Note: Netwerk ID by hometown: (in case your hometown isn't mentioned try a city near your hometown.)''' 

----
Obviously, of course, the entire cabling must comply with the current standard set by ziggo. In other words Cable tire A + (4g shielded) plugs, cables, splitters, plugs, amplifiers etc. The AOP (Subscriber Acquisition Point) must also comply with this. If this does not comply with this standard, it's likely that, after the new channel format, low and high frequency transmitters will not appear in the scan. Among others since the last change, the movie channels have been in almost the entire ziggo region at low frequencies.

A major mistake is that the cable connects to an outdated analogue wall socket. These old wall sockets, as well as the old cabling in the walls, often no longer meet the current "Kabelkeur A+" standard and therefore blocks the high and low frequencies. The only correct way is to connect the cable that is A + certified by cable directly to the AOP. The AOP should have a modern AOP equipped with the cable mark mark. AOPs without a quality mark often no longer meet.

History

2017-05-07T15:08:28Z

Tech: it is already 13 years ago :)

<big>The history of OpenPLi</big> 
 
'''The beginnings:''' 
About 13 years ago, the former chairman of the PLi association and the eponym of image, purchased a new satellite receiver which introduced a completely new concept: the Dreambox 7000. After a very succesful period with the Nokia 9500 satellite-receivers, this new box turned out to be a very succesful successor of the technique used by Nokia. After ‘playing’ a bit with the different firmware image available at that time, he felt that those images where not introducing something really ‘new’. He checked out images like Gemini, RuDream and other alternatives, but in his view none were it. Now what? 
 
'''Where to start:''' 
With regards to programming skills, there was no problem. He was fluent in multiple programming languages, but to familiarize himself with the internals of Enigma, that was quite an undertaking! Eventually, after numerous experiments and in cooperation with other well known names in the scene, a new image emerged. 
The next step was to come up with a name. Up until this point, nobody had thought about this. The first brain-farts were exactly that, nothing to be repeated. Eventually it turned out to be very simple. At his workplace, there were several people with the same first name. As login they used a three-letter code, and his was “PLi”. So the images were called after this code. To make it special, an attempt was undertaken to register this as a trademark. Unfortunately, it was already registered, other were there first. A check on the interwebs shows us that it looks a lot like “Practicing Law Institute”. So the registered mark was out of the question. Unfortunately the logo’s were already created, and PLi® was born. 
 
'''Brand awareness:''' 
To introduce his brainchild to the community it has to be distributed via the bulletinboards that were available on the internet at that time. Most of them were known mainly because of the creative or educational use of the Enigma receiver. Boards like the Dutch DuckFiles and Hutsefruts. These were well known boards, but the also Dutch board Sat4All started to grow in popularity. Soon, quite a few members of the community (and that includes me) became intrested in the Dreambox too, and wanted him to continue with his images. At times, the bootlogo was pretty odd, I can remember that at one point a view of his family members were immortalized on the bootlogo… This only increased the number of people that wanted to wor on the image too. Dream Multimedia became, in a large part due to the popularity of the DM7000 and later models like the DM500 and DM5620, a big success. A large part of that success undoubtedly because of the existence of alternative images, and the large developer population behind them. 
 
'''Note from Peter Lindeman (a.k.a. PLi®):''' 
“I actually started on what would be the first PLi image together with Ronaldd, after I got in touch with the Dreambox DM7000 via the Sat4All forum. After working on my own for a while, I got into contact with RadxNL, to try certain things. Together with him I went to a Sat4All user meeting in Breda,’ which must have been sometime 2004. At this meeting, I met Mirakels (also still active in the team), after which the first cooperation started. Not much later the well known “Hydra” team quit, after which a lot of former “Hydra” team members joined PLi. This is how it came about. What is very funny, and not known to a lot of people, is that I owned the first DM7020 in the Netherlands. I managed to get it via a contact abroad who shipped it to me. For reasons not known to me, certain people in the “Dutch scene” where “not amused”, not knowning how I managed to get hold of one. 

Let’s leave it at that. ;-)” 

'''The expansion:''' 
When at the end of 2005 the renowned and succesful “Hydra” team was dissolved due to circumstances, part of the team joined the PLi-team, which started the success that is PLi. Initially the image, like all others of that time, was closed source. Within the team there were daily builds, but these were not available to the public, and neither was the sourcecode. About twice a year major releases were announced, with names like Amber, Beryl, Citrine, Diamond, Emerald, Flubber, Helenite, Iolite and the latest in this series, Jade. The community was always looking out for these releases, since it meant the long wait for bugfixes and new features was over. For the team this was a joyous event too. Weeks before a release there always was a huge discussion about the new name. At release time, all members gathered in an MSN chatroom, and kept each other informed of all release activities as they happened. Once released everyone watched the download counters go up, and every time we were amazed how fast that went. After the release of Jade, we stopped with the “gemstone” series, but also stopped having formal releases. From that moment, the PLi team decided they would adhere to the open source license, and publish all source code, even if all other image builders did not (and could now use PLi code). The name of the image was changed to OpenPLi to reflect this occasion. Maybe interesting to report was that the way the new images were announced was quite revolutionary within the satellite scene. When introducing Iolite, the announcement was done in the form of a Youtube video. In that time, late 2006, PLi also started with their own internet forum, to provide active support to its users. This forum was known as http://pli-images.org, a domain name still owned by the team today. OpenPLi kept on growing, and in april 2008 the team decided a more formal structure was needed, with proper management to deal with the non-technical side of the team. Out of this the PLi Association was born, a not-for-profit association registered in the Netherlands. All former PLi team members became member of this new associated, and a board was selected to run it. Later, this was expanded with international developers and testers, to provide better support for the continuous growth of the userbase outside the Netherlands. 

'''The open-source concept:''' 
Somewhere at the end of 2008, is considered within the team whether “we” found that the sources of the image ‘should be’ public. In other words, should we really go on developing our firmware, but then in an actual “open way”? Eventually, after a test period, in which the potential of Git was tested, PLi announced that the open-source thought should be used in the right way and due to that thought, that the sources were public as from that moment. OpenPLi was a fact. Over the years, this had quite an impact. Incidentally, not only by the ‘open’ go from PLi, but also by the large increase based on Linux receivers, which were imported from Korea and China by the boatload, increased interest in this segment receivers and hence the number of ‘developers’ of firmware. A large part of them used at that time, and still are using the sources of our image.. 

'''Conclusion:''' 
Now, 10 years after purchasing the original Dreambox 7000 by the eponym of image, I feel we have to think for a moment about the open source concept. When we decided to go “Open” and publish all source, we hoped other teams would follow, and in the true open source spirit Enigma would be development by a large distributed group of developers, all contributing to a common cause, like “the linux of DVB”! We regret that this hasn’t materialized. There are several well known teams that use the OpenPLi source as the basis to develop there own product, and there are many more that just take the source and can’t even bother to change the brand name. We feel that there is still a long way to go, before people can move ego’s and craving for recognition aside and start working towards a common goal. It would put an end to continuously reinventing wheels, wasting development time, and slowing down progress. But, in the end for us the most important thing is simply to enjoy what we are doing, which has been the case in the 10 years that now lay behind us. 
 

On behalf of the PLi Association, 
Frenske, Chairman