Superb quality and spec AB-Com PULSe 4K SE only £99! FREE UK DELIVERY! 4K UHD, Enigma 2, Multiboot 4 images & more!...
Superb quality and spec AB-Com PULSe 4K Rev II Twin Satellite tuner only £149! FREE UK DELIVERY! 4K UHD, Enigma 2, SATA HDD facility, Multiboot 4 images & more!...

[VU+ Ultimo] CI conax module + valid card not working

kvarnstj

New member
Joined
Jul 2, 2012
Messages
49
Reaction score
0
Points
0
Age
45
Hi!

I have a CI Conax module (SCM Microsystems Conax), with a valid card in it, provided by my cable TV provider.
I can't get the channels working at all with OpenVIX Zeus (have not tried older). I flashed my Ultimo with BlackHole image, and channels worked out of the box. Also my TV can manage to get the module to work, but not OpenVIX
I get this message after while
No data on transponder. Timeout reading PAT.
In the CI Assignment menu I see it registered as Conax 4.00e. When pressing edit for it, the UI crashes.
Can anybody help me with this?

.jokv
 
My Vu+Ultimo gives a CAM-message something like "not a valid receiver". I suppose a proper CAM+valid card is somehow paired with the accepted receivers chip. My TV-set Samsung works and is listed by the distributor. They exclude Vu+ with purpose. Can anyone comfirm this?
 
Hi!

A CI+ module needs to be paired, but I am talking about a regular CAM Conax module, which don't need pairing of any kind. As said, the module works on Blackhole image out-of-the-box, but not with OpenVIX. Actually I have used this same module with Vix 2 images, and it worked fine. However the card was from another service provider at that time.
Could someone from VIX team comment on the support of CAM modules in VIX Zeus, are they supported at all?
 
CAM support is solely dependant on the drivers; so if it works in BH it should also work in ViX.
However: AFAIK nobody in our team has suck a module, so actually testing isn't possible.
 
This means that should be used exclusively for Softcam! :D
 
Hi!

Yesterday, I tried with a new CAM module, a CI+ module, with card and module linked together by the service provider. No luck this time either. Today I will try the same with BH image, and check if it works.
It really seems to me that OpenVIX image is missing the ability for channel decryption with CAM module (really a shame).
 
I understand that it might be dependant on drivers, and you cannot impact those. But maybe the problem is with how the drivers are used? I don't get it, how can it work on BH but not on OpenVIX, if the drivers are the same? If the driver it self wouldn't work, then this should not work on BH either, right?
 
Right.

But there's one complicating factor: VU is using ancient versions of Open Embedded and E2, and they are apparently not interested in updating their libraries and packages (it's roughly comparable to sticking to use Windows XP, while the world has moved on). And as most hardware developers and we as well do move forwards, it is possible that the VU drivers don't support all functions they should support. And VU support stops at the moment something is working in their ancient environment.
 
I don't even have or use this module, I was just simply curious why it work with BH and not ViX.

Not too sure what the commemt about a clone has to do with it, yes I do have a clone solo2 but I also have an original Duo.

Sent from my GT-I9505 using Tapatalk
 
Did some more testing. I have one Conax CI module and one CI+ module under test, same card.
As said, CI module works with BH and Vu+ own image, but not with Vix. However this very same module has worked a few years ago with some Vix 2.x image. So Vix has taken a step backwards what comes to decrypting channels. This is a shame since I find Vix the only good and userfriendly image out there, e.g. the EPG is useless in other images. I would not like to swap to another image.
What comes to the CI+ module, I don't know if that is supported by VU+ receivers at all? Can someone comment on that?
Did not get it to work on any other image either. The pairing of module and card is done by the
Service provider, and should be ok. Need to double check that. However, now it seems that CAMs are not supported by Vix at all ( apart from softcam), which really is a shame. I find this a very fundamental feature to have in a receiver, in terms of legal channel decryption. You have explained that there is nothing you can do about it, but I still can't exept the fact that it would be undoable. If it works in all other images I have tried. Please try to make it work, I can send any log you need.
 
CI+ modules will never work in any open source device; after all the whole point of CI+ is limiting users in hardware.
Having said that: many providers start with no limitations implied on CI+ when they introduce those modules. The idea of that is not to deter people from day 1 they use the module; later on they can and will enforce limitations.

For the rest: as I repeatedly tried to explain: CAM-support is entirely realised by the drivers, not by any other part of an image. So there is nothing we can do about that.
And as the use of any CAM will only limit users freedom, I don't consider CAM-support to be a real issue for any open box at all. We are happy to enjoy the freedom that SoftCams give us, and their support is clearly fine.
 
I don't consider CAM-support to be a real issue for any open box at all. We are happy to enjoy the freedom that SoftCams give us, and their support is clearly fine.
Any encrypted channel you pay for legally, you will get on a card that will need a CAM module. Don't understand why the lack of this support is not considered to be a problem. Tell me how I can legally watch the channels I have paid for with only softcam support?
You keep saying
as I repeatedly tried to explain: CAM-support is entirely realised by the drivers, not by any other part of an image. So there is nothing we can do about that.
I keep saying, you don't need to touch the drivers as they work ok in all other images except VIX. There is nothing wrong with the drivers. It must be up to the image to use the drivers correctly, in order to get the channels visible . When I try to show the details of the CI module from the CAM menu, it just keep showing "waiting for CI". I also get the box to crash when choosing edit.
action -> OkCancelActions ok
[CI_Wizzard] FOUND 2 CI Slots
KEY: 352 OK
KEY: 108 DOWN
KEY: 108 DOWN
KEY: 352 OK
action -> SetupActions ok
[CI_Wizzard] selected CI Slot : 1
[CI_Wizzard_Config] Configuring CI Slots : 1
[2816L]
[CI_Wizzard_Config_CI1] read following CAIds from CI: [('0xb00', '2816', 1)]
[CI_Config_CI1] error parsing xml...
Screen <class 'Plugins.SystemPlugins.CommonInterfaceAssignment.plugin.CIconfigMenu'>((1,), {}): <type 'exceptions.AttributeError'>
Traceback (most recent call last):
File "/usr/lib/enigma2/python/mytest.py", line 245, in create
return screen(self, *arguments, **kwargs)
File "/usr/lib/enigma2/python/Plugins/SystemPlugins/CommonInterfaceAssignment/plugin.py", line 159, in __init__
File "/usr/lib/enigma2/python/Plugins/SystemPlugins/CommonInterfaceAssignment/plugin.py", line 303, in loadXML
AttributeError: 'CIconfigMenu' object has no attribute 'read_services'
Traceback (most recent call last):
File "/usr/lib/enigma2/python/Components/ActionMap.py", line 48, in action
File "/usr/lib/enigma2/python/Plugins/SystemPlugins/CommonInterfaceAssignment/plugin.py", line 83, in greenPressed
File "/usr/lib/enigma2/python/mytest.py", line 330, in open
dlg.isTmp = True
AttributeError: 'NoneType' object has no attribute 'isTmp'
(PyObject_CallObject(<bound method ActionMap.action of <Components.ActionMap.ActionMap instance at 0x1eb4f80>>,('SetupActions', 'ok')) failed)
]]>
 
Sorry, but I can't explain it an clearer then I did already.

Sorry mate but its not that clear.
If he states it works with Black hole and the original Vu+ image and the old version of Vix then it cant be the drivers has to be something to do with the Zeus image
 

OpenViX Feeds Status

Back
Top