23 replies to this topic

[jjg3000]

Hello,

 

I installed from scratch a VU+ DUO 2 with the 8.3 Jan 29th version, no extra plugins beside EpgImport from the image itself.

 

I descramble Astra 19.2 services with a legit Smardtv Pro CI Cam (no CI+, no softcam at all) and an official card that works perfectly with the VTI 15.x image on the same box and in several professionnal IRDs. The visible difference I see with the VTI image is that it has a delay parameter in the CI options but I still prefer the OpenPLI on all the other aspects

 

With the OpenPLI, after a boot/reboot , I can descramble services and zap on different channels without problem during a few minutes (around 5). During this initial period, I can also access the MMI menu of the cam in the Softcam/CI menu.  After around 5 minutes, the current channel is still descrambled correctly but if I try to zap on any channel even the ones that were OK just after the reboot, nothing is descrambled and I get a black screen without sound. I can still get the last descrambled channel. In this case, the MMI menu of the cam is no longer accessible (waiting forever...). 

 

In this state if I try to reset or Init the cam, nothing appends. Obviously the communication with the cam is down. In the "Setup, Softcam/CI, Common Interface, Slot 1" menu I Disabled and then re-enable the common interface, the current channel is immediately descrambled and zap on others is OK for a few minutes. Then a few minutes after back to a black screen if I try to zap ... 

 

To do some tests I installed the Common Interfecace assigment plugin and added the CAID, the provider and all the channels with the same results...

 

If someone has an idea of what to do

 

Thank you,

 

 

[Dimitrij]

 

If someone has an idea of what to do

This is a known issue with some VU+ receivers.

You can try another image(openATV/openBH).

[mimisiku]

It seems something to do with the CI watchdog timer. This fails and only restores when the CI port is restarted. Never been solved…. I only use actual smartcards now and never any issue.. Problem off-coyrse when your provider doesn’t issue smartcards…

[WanWizard]

I've always had issues with the M7 CI module in both the VU+ Duo 4K and the VU+ Solo 4K.

 

I now have defined the exact list (so not only the CAID) of channels decoded by the module in the CI assignment plugin, AND I have excluded those channels from being serviced by Oscam.

 

And in general it is very stable now, sometimes a restart of the module is needed after a restart of Enigma.

[jjg3000]

Thank you all for these answers

 

I'll try the other images or get back to VTI that work correctly on the CI side but loose the tuners from time to time...

 

I'll check the next versions of OpenPLI to see if the CI problem is fixed because everything else seems perfect...

[littlesat]

I'll try the other images or get back to VTI that work correctly on the CI side but loose the tuners from time to time...

 

Shame that this 'peace if sjit' is violating everything the software opensource licenses, so we cannot simply look at their fix and implement it in our code.... So we need to spend extra time to invent everything from the beginning (and once we do and our solution is better they simply grab it from github).

 

I know as soon the CI does not give picture you can de-activate it and re-activate it and then it works... but after a next reboot or restart from enigma2 you can do it again.

 

@mimisiku As we still need to re-invent what VTI actually already did... can you please tell a bit more about 'CI watchdog timer....'

Edited by littlesat, 13 February 2023 - 16:58.

[littlesat]

Regarding the 'CI assignment plugin' it would be much much better to find a way or good work-a-round that works over all of our supported boxes, to detect of a CI cannot decode a service -or- can decode a service... so we can get an automatic way to 'switch' between emu and CI.

Edited by littlesat, 13 February 2023 - 16:53.

[littlesat]

Since with have this option:

https://github.com/O...12bb42e89b67df0

 

We can add a kind of watchdog to disable/enable the CI shortly when we do not get a descrambled picture from the CI when it is expected. Or arrange that at a reboot/restart of E2 initially the CI is disabled and then shortly later on enabled....

[Pr2]

Give a try to this plugin:

 

https://forums.openp...p-for-ci/page-7

[Pr2]

And also this one available from the feed:

 

enigma2-plugin-systemplugins-commoninterfaceassignment

 

I just read that you already test it. Use slowzap for CI I think this will be the solution for you you can decide when reset the descrambling.

Edited by Pr2, 14 February 2023 - 11:36.

[littlesat]

Use slowzap for CI I think this will be the solution for you you can decide when reset the descrambling. -> It is a work-a-round....

[Pr2]

If you can please check your module in something else (like a TV) to ensure that it is working fine there, because one of my module is defective and restart by itself I was thinking of a STB problem until I test it in my TV and discovered that the module was the culprit and not the STB.

[jjg3000]

Thanks again for all your feed backs,

 

To reply to some of hem :

 

 - Slow Zap : Yes this is one thing I was looking for but how can I do that? Is this a setting somewhere, an extension? I will reinstall just to test it once I know how to

 - The module and the card are working perfectly in other STBs and also in the same VuDuo2 after a VTi image reinstall...

 

I still find sad to see that the basic / normal / legal way to descramble pay bouquets may not work correctly with OpenPLI when other image can do it on the exact same hardware... It just make the image unusable in my case.

 

Don't misunderstand me, I'm not complaining OpenPLI is a wonderful, free and constantly maintained image. So much better than VTi in many areas (overall stability, tuners management, speed, features...) that's the reason why I'll try the slow zap idea and maybe keep OpenPLI and in this case make a donation... I still hope to use OpenPLI in an upcoming VU Duo4k or similar Stb.

 

Thank you again to the community.

 

Ps. I'll keep on looking for solutions here and post if something does work for me.

[Dimitrij]

 

Ps. I'll keep on looking for solutions here and post if something does work for me.

 

This is a known issue with some VU+ receivers.

You can try another image(openATV/openBH).

 

No solution(forever).

[littlesat]

When I have issues since short I can disable the ci and re-enable it again and then it works again… when we can detect when something goes wrong this could be a work a round other images may also do something like this or have slow zap included. But the real solution is still that manufacturers most like should fix their drivers.

[Huevos]

 

 

Ps. I'll keep on looking for solutions here and post if something does work for me.

 

This is a known issue with some VU+ receivers.

You can try another image(openATV/openBH).

 

No solution(forever).

 

What does that mean? CI decoding works fine on OpenBH (on all Vu+ 4k hardware).

Edited by Huevos, 18 February 2023 - 20:19.

[Pr2]

CI is a quite complicated matter depends on the STB manufacture/driver and also the CAM itself the channel your are coming from and the channel you are going to.

 

When I played with CI I had issue switching from the DVB-C (Cam) to DVB-S2 (Cam) and I don't know why switching between ip stream and CI scrambled channel.  So slow zap was a nice solution/workaround for me that solves the issue that I had.

 

Some CAM are working really fine others are more sensitive (when not defective and reset by themselves  )

[neo]

What exactly does "slow zap" do that solves your problem? The name suggests timing issues?

[Pr2]

It reset the descrambler when you zap for exemple from DVB-C to DVB-S channel if you have trouble when doing this, it is a plugin written by Dimitrij:

 

https://forums.openp...p-for-ci/page-7

[neo]

He doesn't have a repo with that name, I would like to have a look at the source to see what is so special about it.