Logging with FunMagic |
|
| Logging Data with a Funcard. One of the great features of FunMagic, is the possibility to use the funcard as a simple logger. But....... I haven't been able to get my card to log any data. Whether this is a problem of the configuration I am running here, or if it's due to the data that I use to log, I don't know. It seems though that I am only one of few people that have a problem getting any log results. So I need to find out why my log is failing. In the mean time I have used Adrians external eeprom for this manual. Luckily his log was filled:) For the sake of this tutorial, I assume that you have enabled the FunMagic log function. If that's not the case, then click here for more info on the "Special Functions". Open your COM-port and connect to your card in Phoenix mode. If you don't know how, click here for more info on communicating with your card in Phoenix mode. Click on"Fred's" icon to read the external eeprom from your card via the Phoenix interface. In the pop up screen click "Start". If, at the end of the read process, you notice the word "LOG" appearing on the "Number of bytes read" line, then there is a log available on the card. If you only see a certain number of bytes read, then your log is empty. Press "Exit" and then press "Logs Tool" jsut below the menu bar.
On a 'normal' funcard-2 with the 64K external Eeprom, there is room for approx. 180 EMMs. That resembles about 5 - 10 min. of logging, depending on what you are looking at, i.e. which channel, PPV or not, etc. Your log s cleared b.t.w. upon every reset of your receiver or card. So extracting and re-inserting your card empties the log. OK then, you'll notice a log screen with all logged data in it. I will explain all functions (icons) from left to right. But first the main screen itself: When you click a INStruction in the log, you will notice an explanation of that specific INStruction at the bottom of the window. In the small window area at the bottom right, you can browse all the Nano's that where used in the specific selected INStruction. Underneath that area there are 2 lines containing some global information: - a general description of the INStruction type - the status of the INStruction
The "Export" icon: If you like, you can save the logged data in a file. Just click the "Export" icon. In the popup window you can enter some additional comments. Now click "Export" and a file will be created. Important: If you want to creat a library of log files, you will need to rename the log files first. FunMagic will allways save the log file under the name "Phoenix.txt". The file is created in the same folder where your FunMagic.exe is stored b.t.w.
The "Erase" icon: Clicking this icon will not immediately remove the logged data from your card. Only upon saving the changes you made, will the new data be written to the card. So if you wipe the log, you need to write those changes to the card before they will take effect.
The "INStructions" icon: When you select a specific line from the log and then click the "INStruction" icon, specific information about that INS will be shown in a popup window. In this example down here, you can see that this line contained a message from the card. So this must have been an answer, requested by the CAM. The INS involved was 3A, with parameters P1 & P2 (both 00) and the answer containing 10 bytes. For an explanation of the exact meaning of this INS and all of its associated Nano's, please read the Seca pages in the Coding section. There are 2 important INStructions that have received special attention in FunMagic: - "C1 40 xx 80 5x" - "C1 40 xx 81 4E" Those of you having any experience in WallBanger (or any other logger software) will recognize this. What pupose does "C1 40 xx 80 5x" serve: Let's assume you have logged a "C1 40 01 80 54" EMM. You can then decode that INStruction further by clicking "Decode ins C1 40 xx 80 5x". By the way, EMM "C1 40 01 80 54" is used to change the Package Bit Map (PBM) of your card. What pupose does "C1 40 xx 81 4E" serve: If you have logged a "C1 40 01 81 4E" EMM. You can then decode that INStruction further by clicking "Decode ins C1 40 xx 81 4E". The EMM "C1 40 01 81 4E" is used to distribute information to cards covered by a valid subscription. Decoding this INStruction will show you which Operational Keys and which Customer Word Pointers (CWP) are active. But it will allso show you when the current subscription will end.
The "Search" icon: This one speaks for itself I assume. You can search for specific INStructions.
The "Filter" icon: This feature allows you to filter your log list, thus showing only a selection of INStructions. So if for instance you would like to see INS 3A only, click "Cancel all filters" and then check "Select instruction 3A". Then click "Apply filter" and your list will show lines contaning INS 3A only.
The "Reload Log" icon: If you have made changes to the log, you can reload the log from your card, provided you have not yet written the changes to your card. So as long as the changes are made in memory only, you can return to the original list.
The "Send to Phoenix" icon: This procedure is identical to the procedure explained here: Manipulate your card through a Phoenix Interface. Click this icon and a popup window will open, allowing you to communicate with your card directly.
If you have not yet established contact with the Phoenix interface, please do so now: - Click "Open Port" - Click "Reset" You can select any number of INStructions from the small window area at the top left "Instructions captured". These INStructions can now be executed again manually to see what effect they have on your card. This is really educational stuff:) Pick your selection of INStructions and click "Send instruction". Notice the INStructions being executed. The small window area in the left middle of the screen will show the INStructions as they are sent to the card. On the right side of the screen, the complete communication is shown in more detail. So both questions and answers are shown on the right.
The "Events" icon: This function is meant to log PPV events in order to buy them later. As you can see, my log did not contain any PPV events, so I cannot show the exact working of this function. But if you have captured any PPV events in your log, you canm then buy them.
This is how the PPV events screen looks. Sorry that I cannot tell/show you more about it now. As soon as I have a sample log containing PPV events, I will complete this description.
The "PPUA" icon: Same story here, sorry. As you can see, the log that I had didn't contain any PPUA related INStructions. So I cannot tell you more about it until I have had a chance to test it myself.
| |