Thema: Common Interface port problem

Hello,

Since the release of the new Vu + Duo 4KSE, there is a big problem with the common interface. After a mains start, there is no problem, then, after some usage time, especially when viewing a unencrypted channel for several hours, the module no longer decrypts the channel. Access to the menu of the common interface clearly shows the module present (but sometimes no longer sees it), but we can no longer access the module itself (there is a "wait for ci" message). Even the "Reset" or "Initialize" functions no longer work. You must reboot the decoder.
In fact, I think the decoder deactivates the module and as long as we do not do a restart, it does not reset the module.
I don't know if there is a problem with the VU + driver, but I have done tests with Open VTi and there is no problem. It is therefore a defect at the OpenATV level.
I tried with a Cam Viaccess Neotion 6320 series module but also with a Cam ViaccessNeotion FRANSAT CI + 1.3 module.
Also tested with Cam Nagravison Tivùsat module

Thanks for checking this problem out.

Hello,

Still no resolution since the last update 20210219.
The Cam module (CI) works but after a while there is no more CI access. This happens after viewing an unencrypted channel for several hours or after viewing recorded video, the module becomes inoperative.
When you want to access the module via the menu, you can clearly see the Cam module (as in the photos of the first post) but when accessing the Cam module, there is the message "wait for ci" and it stays like that, without no access to the Cam module. In addition, there is no possibility to reset it from the "Common interface" menu. The only way is to remove the module and put it back in place to reset it. This gives the impression that the module is going into standby mode but there is no way to reactivate it.
This problem does not occur with the VTi image. There is therefore a processing problem on the common interface. I even tried assigning a string to the module, but to no avail.

If a developer wants more information, you can contact me privately.
The problem was found with different Cam module (Viaccess or Nagravision)

Thank you

Nachricht in Englisch

Hello,
I had already opened a post on this subject (Common Interface port problem #) which was closed by Papi2000 @ by misunderstanding.
This is not illegal but a problem on the common interface slot (slot 1 or slot2) of the Vu + Duo 4K SE
The port does not remain stable and deactivates the CI module which remains readable in the menu of the common interface but without any accessibility.
I'm not talking about a CI PLUS module, but a CI Viaccess module. But I also tested with the same problem on a Nagravison module (not CI +). So it has nothing to do with the CI+ standard, just the CI classic dialogue.

The problem is as follows: after viewing an unencrypted channel for several hours or after viewing a recorded video, the module becomes inoperative as if it were on standby (the problem is totally random).
The problem is as follows: when you want to access the module through the menu, you can clearly see the CI module but when accessing the CI module, there is the message "wait for ci" and it stays like that, without no access to the module. In addition, it is not possible to reset it from the "Common interface" menu. The only way is to remove the module and put it back in place to reset it. It really gives the impression that the module is going into sleep mode but there is no way to wake it up.
This problem does not occur from the release of the Vu + Duo 4K SE but with Open ATV because I have tested with the VTi image and everything works fine. There is therefore a problem of processing ATV on the common interface. I even tried to assign a string to the module, but to no avail.
Could this be a Vu + driver problem? But if so, why the problem does not occur with Open VTi ...
Please find a solution.

Schau mal da,
Common Interface port problem

Nachricht in Englisch

Hello,
Yes, I had already opened a post on this topic.
Your link goes to the post I had already created!
I had displayed the screen (photos) with the problem encountered.
The message was closed thinking I was hacking!
There is currently no solution ...