Hello,
Dear All,
Kindly can some one help against my IRDETO FREE-XTV card?
Because my this card not working in T-REX Cam. What I Have
to do to get it work in T-REX Cam? Thanks
Hello,
Dear All,
Kindly can some one help against my IRDETO FREE-XTV card?
Because my this card not working in T-REX Cam. What I Have
to do to get it work in T-REX Cam? Thanks
Do you know if your Card is still good? Or if the Card in question really is for Irdeto? Couse the T-Rex should be able to read Irdeto Cards just fine. But, I'm wondering if your card is either out of date, or in fact for Neotion Crypt...
Revisitng this I think your problem could be that the Predator Software could be to blame. Having had a simular problem, with Kable Deutschland.
The problem is likely that the Predator can't claer the CAID for Free-X Irdeto. Sadly I don't know it off hand either. You might be able to find it if you check your Predator (Dragon / T-Rex), Settings Smartcard (Smartcard is IRDETO/BETA ..... .... Crypt ID: 1702), If that CAID is not in your CAM or if your STB can not clear more then a handfull of CAIDs at one time. Then the Channel(s), will likeily remain dark.
Thankfully you can use the DragonCrypt Software, to edit out which CAIDs you want to have loaded. So if you set the CAID for FreeX as one of the first CAIDs to be loaded on the Predator. Your problem should then go away...
I have a free xtv viaccess card and it does not really work properly with the latest predator version. I have to switch on and off my receiver every time to decrypt the channel. With earlier versions of predator, didn't have that problem.
Get the lattest DragonCrypt (see Dragon Files Thread), load the current v3.43 File in it then File -> CAIDs to open the CAID Editor. Click on the Table Button, and Load the predator340.cds File. Lastly click the Load Button, to load the current Predator Table List.
You should then see at the bottom a string of CAIDs, like this:
0100 0500 1702 0B00 4A70 0604 0D03 1801 1762 1800 0606 0D01 0D00 0961 0D05 0D04 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 etc., etc...
If you have origianl Files you might have seen in the README that on average any given STB can handle at best 16 CAIDs. Allthough you could in theroy add more CAIDs it could cause system instablilty. Given this it's thought that only the more important (i.e. popular), CAIDs are used and others such as 1722 (CAID for KDH), were not. At least somehow in mycase I can not recall ever forking with that end of the CAM before.
But there you have it...