FunMagic |
|
| Allmost done, only the Blacklist needs finishing!!! OK then, there we go with this fantastic product: FunMagic. If this is your first time working with Funmagic, I suggest that you read the entire page. Just follow the example, to get acquainted with all the goodies of this product. You may address different parts of this page directly though. Just click the links down here. 1. Importing data from other applications. 2. In- & Output formats supported by FunMagic. 3. Known issues you should be aware of. 4. Some special logging functions. 5. The Blacklist or Intelligent Bytes. 6. Programming the card with a Fun programmer. 7. Programming the External Eeprom with a Phoenix Interface. 8. Manipulate your card through a Phoenix Interface. 9. Use the Fun card as a simple logger. Importing data from MKFind into FunMagic: So make sure you have your MKF log prepared for this one. Start the program and you should see a screen like the one down here. Click on "Edit External Eeprom", just below the menu bar.
Now your screen should look like this down here. Click on the "2 masks" icon in order to start importing data from another application.
In- & Output formats supported by FunMagic You'll notice the "Import Data" screen popping up. The "Import Data" screen allows you to determine a number of different input file formats. Take your pick, depending on what you've used previously i.e. an original subscription card or a cloned one. In this example, I assume you have an original subscription card and have prepared a MKF log from its data. Next you have a choice from 2 different output formats, i.e. FoM or Secom. You'll find a zip file called "sandra-d7.zip" in the FunMagic folder in the download archive. The zip file contains empty files only. Just create your own external eeprom file in FoM 1.x format, using your MKF log and you have a fully functional funcard. OK then, on we go. Click on "01 ---> MKFind_4x" and click the "Open" button on the source line. From the File Select screen, pick your MKF log file.
Select your output file the same way: Tick the desired output file format (in this example I use FoM 1.x). Then click the "Open" button on the target line and type a name for the external eeprom file you want to create. In this example I chose "My_MKF_Ext_eep.hex". Next, when the Source- and Destination files have been named, click the "Import" button in the lower left corner of the "Import Data" screen. FunMagic will now read your MKF log file and if no errors are encountered, it will pop up a screen telling you so. Just click OK to continue.
Known issues you should be aware of The MKF log issue: There is a possibility that your data will not be imported correctly. This is due to the fact that the MKF log isn't allways saved in the same way. It just depends on the amount of data, stored in the MKF log really. So allways check the data after import. Not only the Seca provider, but all channel providers as well. The Seca startup record: Then there is a small compatibility problem between MKF and FM that will cause your card to fail if you don't correct it. The Seca startup record in your MKF log contains 10 bytes only. FunMagic expects 11 bytes though. That's why, after importing your MKF log, you will probably have a Seca startup record identical to the one from your MKF log, but with an extra byte (containing FF) added at the end. You need to edit this by hand. Just copy & paste bytes 1 thru 10 to make them bytes 2 thru 11. Then edit the first byte and make it 01. So when you're done, your Seca startup record should look like this: 01 xx xx xx xx xx xx xx xx xx xx instead of this: xx xx xx xx xx xx xx xx xx xx FF. Have a look at these 2 screenshots down here.
OK then, let's go on. Your screen should look similar to the one up here. Check if all data was imported correctly (UA, PBM, RC etc.). Check if the "UA" and the "Serial N." fileds match. Check all of your channel providers as well.
Now click the "wizzard" icon, to enter the "Special Menu".
Some special logging functions FunMagic supports the use of Masks, to filter out specific INStructions. 3 diggerent MAKS can be specified: A, B & C. Some samples: Mask A: C1 40 01 81 49 - Will only let the cw update pass Mask B: C1 0E 00 00 08 - Will only let the serial number pass Mask C: C1 16 00 00 07 - Will only let the supported number of providers pass Below, you see the "Special Menu". You are advised to change some of the default values: - Tick the option "Auto Log" to turn on the cards internal log function - Remove the check mark from the "AutoPPV" option - Set Masks B & C to all 00, unless you want to filter out a specific INStruction If you are using a PCB type funcard, then it will probably contain a few LEDs. The function for those LEDs can be determined as follows: - Don't use the LEDs - Show which key is in use - Show what provider is active After having set all special functions as you require, click "Update" to store the changes. Next click "Exit" to leave the "Special Menu".
All modifications you have just made, need to be written to the card of course. These special functions are stored in the external Eeprom. To save the changes to a file first, click on the anchor icon.
Select the External Eeprom file in which you want to store the changes and press "Save".
The Blacklist or Intelligent Bytes. This is the last piece of the software I have not yet finished. But I am working on it, so check back later. | |