CAS Interface Studio 3.3
1. Introduction and what you should know before you start
2. Programming UCAS type CAM
3. Programming @SKY type CAM
4. Other options of this programmer & Software
5. What problems are you going to encounter
Before you put any CAM into your CAS Interface, you should know a thing or 2 about your equipment. Handling your programmer and/or CAM wrong, can result in damaging it. So let's start by explaining just a little bit about the CAS Interface and what it is supposed to be used for.
I don't know why, but there is hardly any information to be found on the www about what UCAS or @SKY stand for. So I can only hope that I used the right sources for my research and got the correct info. As I stated on several occasions, all over this website: "I am not a hardware specialist!!!". So if anyone finds anything on these pages that is incorrect, please let me know and please do not email me for help with your CAM.
OK then, let's share some of the knowledge I have gathered ;)
The CAS Interface 2 is a programmer, designed to program certain types of (re)programmable Conditional Access System modules. It can handle both external CAS modules and internal systems. You should be aware though that it cannot handle every type of CAM or receiver.
The CAS Interface is capable of programming the following types of CAMs:
@SKY or ATSKY CAMs: These CAMs are also called MultiCAM and they are based on Neotions ATSKY platform.
Samples of @SKY type CAMs are the Joker CAM, the SkyCrypt CAM, the IceCrypt CAM, the Zeta CAM etc. etc. Down here you see the interior of such an @SKY type of CAM.
First a picture of the component side:
And next, a picture of the contact side:
Now this is the side that is very important in these CAMs because here are the pins located that are needed when (re)programming this CAM with the CAS Interface 2.
Notice the 6 copper contacts on the right side of the picture.
For these CAMs you do need the Jcard. Now look in the picture below how the Jcard should be inserted in the CAM in order to let the Jcard pins make proper contact with the 3 CAM contact pads.
In case you wonder, this is a view from the bottom side of the CAM and no, the Jcard isn't that transparent. I have added the transparency to this picture for purpose of this explanation.
In a regular setup with a closed CAM, it should look like this when you have the Jcard properly inserted (see below).
But before you start forcing the Jcard into your CAM, please read the page about Programming the @SKY CAM, because there is an illustrated description on how to insert the Jcard properly.
UCAS CAMs: Universal Conditional Access System, also called Universal CAM. These CAMs are based on SIDSA platform technology.
Samples of UCAS type CAMs are the Magic Module and the Matrix Reloaded. And you should NOT use the Jcard for programming this type of CAM. In case you don't know, the Jcard is the little printed circuit board that is supplied with your CAS Interface 2.
Down here you see a sample of the interior of a Matrix CAM (component side).
This down here is the interior of a Magic Module (component side).
As you can see, it is build exactly identical to the Matrix CAM, which is no wonder as it also is SIDSA based like the Matrix. The only obvious difference is the print on the components. So now you will understand why they can be loaded with the same firmware and turned into identical CAMs.
The UCAS type CAMs are simply plugged into the programmer like you see on the picture below. That's it!!!
You can also use the CAS Interface 2 to (re)program the following receivers:
Dreambox, Nextwave 2500 and Xtreme: I did not test this functionality myself, simply because I don't have a Nextwave or an Extreme, and the Dreambox that I have is to dear to me to risk damaging it :)
Furthermore, there is an extension board available for the CAS Interface 2 which allows you to program smartcards with it. I don't have the extension board, so I could not test that functionality myself.
So what did I test? Well, I tested both CAM programming procedures.
But before I get to the interesting stuff, just a quick note up front.
When you start the program, the software first checks to see if a valid (read original) CAS Interface is connected. Down here you can see what your program window should look like while it is checking the connected programmer.
Then, if everything is OK and the software has beeped a few times, you will see a few pictures appear in your program window and also the serial number of your CAS Interface will appear in the lower left corner of the window (see below).
Now you are ready to continue.
Just pick your choice from the menu at the top of the page.