You are on page 1of 9

RQ_ECHO_CLIENT SETUP: This guide is show how to setup the rq_echo_client application to be used with echo equipment.

This setup is only for windows platform (I might do one for linux later on). Although you can use AVR or Maxmel board for this purpose, but this guide will only cover AVR. Information in this guide is written for educational purpose that you may use to learn. Please use at your own risk. Required Equipment: 1. AVR or Maxmel board. 2. Echo IRD with married cam image (could be public numbers). 3. Computer to run the echo_client application. The way it works is that you run the client application on the computer and connect the AVR / Maxmel board to the serial port of computer. AVR board emulates the ATR for the respective ROM 24X or ROM10X and echo client application does the rest of the work. There are 2 main steps to this process: 1. AVR Programming 2. Echo Client Application. So lets start! AVR Programming 1. You need to have AVR board with AT90S8515 chip (This is the one I have used).

2. You can find the AVR flashes here and you can program with AVR programmer called Jeepers. Download the appropriate AVR flash file depending upon the provider you want to use (ROM240 for bell / ROM 241 for dish) Unzip both zip files into same folder. Connect the AVR board to parallel port of your computer. Start Jeepers and you should see screen below:

Press Full Monty and you should see Programming AT90S8515 in the bottom bar. After the programming, a pop up will show once programming is complete. 3. Now you need to create a serial to AVR board cable. The cable diagram is below:

You could use Zener Diode from 4 to 6.2 volts. They will all work. You also need to install a 10uf 25 Volt (capacitor needs to be at least 25 volts). If you dont install the capacitor, you will probably get a SCNIC (Smart Card Not Installed Correctly). The capacitor needs to be installed on the 8515 chip at pin 9 (+ side) to pin 20 (- side).

This is a picture of the cable I created. Instead of using the DB25 adaptor, I soldered the cable directly to the AVR board, there are only 3 wires.

Echo Client Configuration Now you have AVR board ready! Lets get echo client application up and running. AVR board will pass the ATR for ROM 24X (from the AVR flashes) and communicate between the IRD and echo client application. For this to work, you need to an echo IRD (301, 510, 522, 625, VIP receivers, etc) with married cam image. The cam image is used to provide the client ird with cam information (CAM serial, IRD serial) as well as guide information. The cam image needs to be in the same folder as the echo client application. Save the ROM102 or ROM 103 image, depending upon the IRD you using, in the folder and rename to something like rom102.bn102 or rom103.bn103. You could actually name it anything you want as long as the name matches with configuration file. Now one thing you need to make sure that tiers on the image are not expired. There are many apps you could use for this purpose. If you need help find such app, pm me. Client IRD guide will depend upon CAM Image tiers, if something is not in CAM tiers, it will appear as Green or Red. But even CAM image has all the tiers dish offers, you will only be able to watch what is in the subscription, others channels will remain black. Shared card will only be able to provide control words for channels that are in the subscription. Once you unzip the echo client zip file, there will be 7 files in there. As I mentioned above, this guide is only for Windows platform, so you only need 2 files (rq-echo-client.exe and rq-echoclient.conf). You can leave other files in the folder, they wont affect anything. Now remember

you do need to have CAM image in this folder but you need one that is married to your IRD, the one in folder is using public number I believe. So here is details for the rq-echo-client.conf, I am only going to mention the setting s that need to be changed. Leave all others as they are, dont delete them. Leave them to default values as they came from zip file. All the setting that say NOTE:Ignored in the WIN32 version, you can leave them as they are. [General] serial_port= COMX <- X is the COM port # of the serial port the AVR board is connected to. byte_write_delay=0 <- Dont need to touch this unless you are having communication issues. background_execution=1 <- Leave as it is debug_level=2 <- Leave as it unless want more or less details in the app window. log_to_console=1 <- Leave as is. Change if you dont want to see communication in the window. log_to_file=0 <- Change this to 1 if you want to turn on the log. logfile_name=x:/xyx/xyx.log <- This is path where you want the log to be saved.

nagra_generation=0 <- Leave @ 0 for Nagra 2 or change to 1 for Nagra 3 Cam. Note: You can add 2 url to different servers where one is running N3 card and other is running N2 card hoping you will get all the channels. Raton has advised me that echo IRD are incapable of switching between N2 and N3 packets. You can either use N3 or N2. nagra_cam_image=./xxx.bn10x.bn102 <- This is the name of CAM image that is married to your client IRD. Make sure this matches with actual Cam image in the folder. nagra_tier_source=0 <- Change this to 1 if you want to use custom tiers. nagra_tier_0= <- This is where you specify custom tiers. Up to 64 tiers can be added by updating nagra_tier_1= <- index. nagra_autoupdate_expired_dataitems=30 <- Leave as is. # URL of card-server to use, formats are as follows:

card_server_url=newcamd://dummy:dummy@127.0.0.1:10000/0102030405060708091011121314/EMM card_server_url_1=newcamd://dummy1:dummy1@127.0.0.1:10000/0102030405060708091011121314 card_server_url_2=newcamd://dummy2:dummy2@127.0.0.1:10000/0102030405060708091011121314

This is the url of rqcs server. You can add up 63 servers if you wanted as back up or accessing different subscription. The echo client will access the proper server for control words one after another stopping when the control words are returned. If there is no servers that are able to provide control words, this will run in loop until you change the channel to that one is available in the subscription. Lets dissect the url or server.
card_server_url=newcamd:// <- Dont need to change dummy:dummy <- this would the user name and password. These credentials need to in the server configuration under protocol_server_users otherwise you wont be able to log in. @127.0.0.1:10000 <- This is the address and the port of of rqcs server. The ip address and port is separated by : . You should update these with information from the rqcs server. 0102030405060708091011121314 <- this is the des key. This is used to encrypt and decrypt communication between server and client. Make sure this key matches the servers des key. /EMM <- This is used to pass EMM to card. It should only be used by the first user that is configured in the server configuration under protocol_server_users. If other users use this /EMM, it would be waste of bandwidth on client and server side since the server would reject it anyway. In my opinion, you should run a client locally to the server and pass /EMM on that client. So you dont need to have depend upon any other clients which may not be available.

Now that we covered all the configuration lines, it is time to start the echo client app. Connect the AVR boards cable to serial port of your computer where you going to run the echo client app. Dont insert the AVR board into IRD yet. So click on rq-echo-client.exe to start the app and you should see something like this:
****************** Starting log on Sun Mar 22 14:45:57 2009 ****************** Configuration settings: Debug level: 2 Initializing ------------------------------------------------------------------------------Loading CAM image: './Tiers/522.bn103', Done

Initializing Virtual CAM: Encryption system: Nagravision 3 Using custom tiers: <- I am custom tiers, if you are cam tiers, nothing will appear here. XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX YYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYY XYXYXYXXYXYXYXYXYXYXYXXYXYXYYXYXYXYXYXYXYXYXYXYXYXYXYXY CAM serial: XXXXXXXX <- Cam serial of the married Cam Image in the folder. IRD serial: XXXXXXXX <- Ird serial of the married Cam Image in the folder. System ID: 0100 [Dish Network] Box key: 0F951E94D5A02AB5 <- Box Key of the client IRD Processing DT06 key 0D: Done Calibrating Delay: Done [322] Connecting to card server (URL's truncated to 48 characters for display): Trying: newcamd://dummy:dummy@127.0.0.1 ... Connected Initializing IRD: Done

Client READY! -- Waiting for IRD requests...

If you see this in the echo client app window, it means that all the settings are correct. Now make sure all other IRD cable are connected (To TV, Input from Satellite). Now Insert the AVR board into card slot of your client IRD. After few seconds, you should see the Acquiring Satellite Signal window on your TV screen and echo client app windows should see bunch of numbers running (see below): IRD **** [Sun Mar 22 14:46:34 2009] | Cmd -- | ---- | Set field size to 80.
> 21 C1 01 80 61 < 12 E1 01 80 72 IRD **** [Sun Mar 22 14:46:34 2009] | Cmd C0 | ---- | CAM status request. > 21 00 08 A0 CA 00 00 02 C0 00 06 87 < 12 00 08 B0 04 00 03 00 00 90 00 3D IRD **** [Sun Mar 22 14:46:34 2009] | Cmd 22 | DT00 | DT Req. (IRD info). > 21 40 09 A0 CA 00 00 03 22 01 00 39 1B < 12 40 3B A2 37 2A FF 90 00 00 00 01 01 ED 16 16 16 04 28 F8 FE 00 00 00 00 A6 07 18 CB A8 BE 10 FE F8 28 04 31 34 31 36 47 41 50 44 4C 32 39 33 00 00 00 00 00 00 00 00 00 00 00 00 90 00 C2 IRD **** [Sun Mar 22 14:46:34 2009] | Cmd 22 | DT00 | DT Req. (end of chain). > 21 00 09 A0 CA 00 00 03 22 01 80 39 DB 12 00 3B A2 37 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 90 00 2C IRD **** [Sun Mar 22 14:46:34 2009] | Cmd 12 | ---- | CAM serial request. > 21 40 08 A0 CA 00 00 02 12 00 06 15 < 12 40 08 92 04 05 0A 4A 56 90 00 4F

While the IRD is Acquiring Satellite Signal, the app window will show that the client disconnected from server, dont worry it is normal. After the receiver has downloaded the guide, client will re-connect with server to request control words for the channel your IRD is on. When the Server send back the control words, you will see picture on screen and app window will show:
IRD **** [Sun Mar 22 23:39:15 2009] | Cmd 08 | ---- | Process ECM. ECM **** [Sun Mar 22 23:39:15 2009] Processing ECM... Control words received successfully.

If you dont get video on screen, you might tuning to a channel that is not in the subscription and you will see the Failed to received Control Words and client will try the next server url if one is defined in the rq-echo-client.conf (see below). It will keep trying until it gets to a server that can provide control words or you change to channel that is in the subscription.
IRD **** [Sun Mar 22 15:46:46 2009] | Cmd 08 | ---- | Process ECM. ECM **** [Sun Mar 22 15:46:46 2009] Processing ECM... Fail-over, trying: newcamd://dummy:dummy@127.0.0.1:10000/0102 ... Control words not received. Control words not received. Fail-over, trying: newcamd://dummy1:dummy1@127.0.0.1: 10000/01 ... Control words not received. Control words not received. Fail-over, trying: newcamd://dummy2:dummy2@127.0.0.1:10000/01 ... Control words not received.

Now, in order to connect to server over the internet, server sides router need to open ports to allow connection to server computer. The server computer also needs to define a rule in the firewall (if server computer has one; I think it should have one) to allow connection as well. If the firewall doesnt allow traffic to server, client wont connect. On the client side, you shouldnt need to do anything except maybe define exception in to your firewall if you have one. Hopefully by reading this guide, you are able to use the RQCS server and RQ-ECHO-CLIENT in conjunction. Information in this guide is written for educational purpose that you may use to learn. Please use at your own risk. Enjoy!

Fta_dude

You might also like