*2 Faster programming is possible if you have firmware 1.4 or newer.

*3 Only possible with third party software

*4 Only possible with firmware 4.1 or newer

*5 Only possible with firmware 4.2 or newer

*6 Only possible with firmware 0.1 or newer

1. The card you read from and the card you will copy to, must be of the same type (same chip's and memory sizes).

2. The card you read from must not be protected in any way to be able to copy all memory areas.

3. The card must be supported by Multiprog Utility.

And here is how to:

• Manually select the type of card in Multiprog Utility you will be reading/writing to, for example goldcard.
• Insert the card you which to read from and press "Read"
• When done, insert the card you want to copy the information to and press "Program"
• Done!

When the software searches for the programmer it will normally come on with a steady light for about 1 second, but if it's:

Flashing Quickly: The internal 5V regulator fails to generate proper 5Volt power for the programmer, please check your battery and replace with a new 9V alkaline battery. It could also be caused by a faulty DC-adapter or a DC-adapter with wrong voltage.

Nothing is happening at all: This can be caused by:

• No or bad power supply connected to the programmer, please check the polarity of the DC-output of your DC-adapter, and make sure that it supplies 9 Volt regulated DC output with minus in the centre of the DC-plug. If you are unsure about your power supply, we strongly recommend to try your programmer with an 9 Volt Alkaline battery.
• The com-port you are using for your programmer is not available in Windows or being used by another software
• You are using an USB-modem and are using a software called RVS-COM 1.63 to create virtual comports for the modem. This software is currently not compatible with our Windows software.
• Something is wrong with the cable between the programmer and your computer

Generally, there is no need to configure your serial ports for use with our programmer it should configure itself and it will determine which of your comport your programmer is connected to by itself, but in case of trouble and for advanced testing of the programmer, there is a software called Easycom which can be used for advanced troubleshooting. The software can be downloaded by pressing here.

Install the software in your computer and set the properties in the software to the comport you are using and baud rate of 9600, 8 data bits, 1 stop bit, and no flow control. From the communication menu, you can set the DTR signal, if you enable it the led on the programmer should go on with a steady light. If it's blinking, try to disable the DTR and then turn it back on again. If the programmers LED is still blinking try to send a command to the programmer (Please note that all commands are case sensitive, a full list of commands can be found here), write:

*c

and press transmit, *c should appear on the DTE-1 line and also on DCE-2, followed by 4 more characters, the last of those 4 characters is an acknowledge character, the 3 characters is the error bits, if there is no error all should be set to zero, but if there is an error the led is blinking and one or more of these bits should be set, you can examine the binary result of each of the 3 bytes by clicking on them with your mouse. By looking at the command list you can determine what error the programmer reported. The LED should not be blinking after this command because the error register in the programmer is also cleared, but if it's continue blinking it's a sign that the error is re-appearing, for example it could be a low battery causing the error condition.

If you didn't get anything on the DCE-2 line it could be caused by:

1. Wrong serial port selected
2. Faulty cable or the programmer is not connected to your computer
3. Dead battery or bad power supply connected to the programmer.
4. Serial port is faulty on your computer.
5. You forgot to set the DTR signal active, the LED must be on, otherwise the programmer is not active.
6. The programmer is faulty.

If you get the *c in response but nothing else on the DCE-2 line it could be caused by:

1. Wrong serial port selected, you can get this result if you are sending the command to a modem.
2. Wrong baud rate and/or databits, stop bits, parity selected, the programmer will not recognize data received and will not respond to it, the LED can also start blinking since the programmer can detect a serial communication error.
3. The micro controller of the programmer is not responding, the programmer is faulty.

If the LED on the programmer doesn't go on when you set the DTR signal active it could be caused by:

1. Wrong serial port selected
2. No or bad powersupply connected, if unsure about the power supply, always try a fresh 9V battery.
3. Programmer is not properly connected to your computer
4. The selected serial port is faulty
5. The selected serial port is being used by another software, Easycom should report an error when opening the comport in this case.
6. The programmer is faulty.

If the coil is damaged, the autodetect function will not detect and program pic-cards since the coil is used to generate the 13V programming voltage required for programming and detection of these chips. However the programmer can still program eeproms and atmel chips, and work as a smartmouse/phoenix interface even though the coil is damaged.

On newer programmers the coils is from a different manufacturer.

A 9 Volt regulated DC power supply should be used, with a 2.1mm DC plug with minus in the centre, capable of supplying 150mA or more.

What does "regulated" mean? It means that the the output voltage should always be the same even when no load or full load is connected to the power supply. If you have a digital voltmeter you can check this yourself if you are not sure about your power supply. Just measure the output voltage from the power supply when it's not connected to the programmer, the instrument should now read 9V.

What happens if I use a 9V non regulated power supply? When unloaded, these power supplies can easily give 17V or more which could damage the programmer and your cards.

Can I supply the programmer from 12V from my computer? In most cases you can, but measure your 12V from your computer with a digital Multi meter and make sure it doesn't exceed 14 V. And be very careful not to reverse polarity.

Most cards have 2 chips these days, one cpu and one external eeprom. All cpu's from Atmel and Microchip that we support on our programmer has the possibility to protect all or some data inside the cpu. Thus making it difficult to read the content of the chip. However the external eeprom has no protection of any kind. In order to protect the data on this chip it has to be encrypted or to put any data that you wish to be protected in the cpu instead.

If you encrypt the data on the eeprom, a decrypt routine has to be put in the cpu and the encryption key for it should be placed in the protected memory of the cpu.

If the cpu has been code protected the chip cannot be read, but it can be reprogrammed if you erase it first. However the MP6, MP7beta and DosProg software automatically erases the chip when you re-program the chip, so you don't even need to erase it first.

Phoenix and Smartmouse are two types of interfaces which is used to communicate with smartcards.

The only difference between phoenix and smartmouse is the polarity of the reset signal, and most softwares for it will run on both types.

There are many phoenix and smartmouse interfaces available on the market and it's a very basic construction:

• All data sent on the comport is sent to the card and back to the computer (loop back)

• Any data sent by the card is directly send to the computer.

• The cards reset signal is operated by the RTS signal on the comport.

• A 3.58MHz oscillator is supplied by the interface to the card.

The Multiprogrammer 3.5 emulates this behaviour when you send a command to the programmer, this command can be sent by the MPSET software but you can also use MP6, MP7beta, Multiprog V1.10 or Elvis Control Centre. Once the programmer has entered phoenix or smartmouse emulation mode it will not return to it's normal state until you have removed the power or used the "Power OFF" function in Multiprog V1.10.

We recommend using Multiprog 1.10 to set the programmer to phoenix/smartmouse mode especially if you are running Win 2000 or XP.

Once the programmer has entered phoenix/smartmouse mode the LED should be lit with a steady light and it will only blink when data being sent back and forth to the card. To determine if the programmer really entered phoenix/smartmouse mode you can perform this simple test:

• Remove the serialcable of the programmer, if the LED still is on, the programmer has successfully entered phoenix/smartmouse mode.

A very important fact to know about the phoenix/smartmouse mode is that it can only be used for smartcards that are not empty, since there must be some sort of software on the smartcard that receives the data send by the computer. This is one of the reason why you cannot program empty cards with it. Another reason is that the phoenix/smartmouse interface is not capable of delivering any programming voltage which is required for programming Goldcards for example.

But you can still use it with Goldcards once you have programmed a loader into the pic-chip that is capable of receiving commands from software's like WinPhoenix for example.

Another important thing is that all software supplied by AD-Teknik doesn't make use of the phoenix/smartmouse interface. Once the programmer has entered phoenix/smartmouse mode then AD-Teknik's software will not be able to detect the programmer until it has been reset.

If you are using a battery don't forget to exit the phoenix/smartmouse mode when you are done, if you don't, the programmer will empty your battery in a few hours time.

There is also phoenix/smartmouse interfaces operating at other speeds than 3.58MHz, for example 6MHz but the Multiprogrammer 3.5 will only use 3.58MHz, this is normally no problem because all cards can be run with 3.58MHz and most phoenix/smartmouse software can adjust the baudrate on the comport to suit with the 3.58MHz oscillator.

There is an 6 pin ICSP (In-Circuit serial programming) connector located just behind the D-sub on the programmer, the pins are used as follows starting with pin 1 (squared).

1. MCLR

2. +5V, Only to be used for the chip itself, don't use it if your application supplies power the pic-chip.

3. GND

4. Data

5. Clock

6. Oscillator, don't connect for normal ICSP operation.

Normally you don't have to verify your card since the programmer will verify your card while programming it. Anyway here is how to do it with MP6:

• First of all, make sure the mode is set to "normal" in the file menu of MP6.

• Create two new goldcard projects, by selecting "new project" and choose goldcard (1PIC+EEPROM D7C3) two times.

• Highlight the first line of the first project and press open to read 2 files to the first project (hold down the CTRL-key to select the second file)

• highlight the first line of the second project and press read to read the entire goldcard.

• Now open the tree-structure under the PIC16F84 and 24C16 chips for both projects and locate the "memory maps" PROGRAM and DATA, highlight the memory you want to see and press "view".

Tip: You can open several windows at the same time, and put them beside each other to easily compare the 1'st project PROGRAM memory with the 2'nd  project PROGRAM memory.

If the window for the PROGRAM memory only displays 3FFF then it means that the chip was empty, or the chip couldn't be read due to the chip was codeprotected. (the MP6 software always reports if the chip was protected when reading it).

The same procedure can be used for all chips that the MP6 software supports, just make sure to open the right type of project for your chip.

In order to upgrade the programmer it must be sent back to AD-Teknik.

The cost of the upgrade depends on what microcontroller your programmer is equipped with:

• If it's an PIC16C622A it needs to be replaced with an PIC16F628, price 10 GBP or 15 Euro.

• If it's an PIC16F628 then we will just re-flash your chip, price 3.50 GBP or 5 Euro.

Prices includes return carriage within Europe.

The latest firmware version is:

• Multiprogrammer 3.4, Firmware version 0.13 (this version only uses PIC16C622A)

• Multiprogrammer 3.5, Firmware version 1.10

Here is how to do it:

Send your programmer in an envelope together with the correct sum in cash and please don't forget to include your return address.

Our address:

AD-Teknik AB
Karl Gustavsgatan 7
SE-411 25 Göteborg
SWEDEN

You can get a discount on our Multiprogrammer3.6 USB if you send us your old programmer. Here is how it works:

Send us your old programmer and we will send you a new Multiprogrammer3.6 USB for 495 SEK plus shipping.

Our adress:
AD-Teknik AB
Karl Gustavsgatan 7
SE-411 25 Göteborg
Sweden

This driver which can be downloaded from our website has been prepared so that the Plug-and-Play function which causes this problem are disabled.

If you download the driver from another website you'll have to do this manually:

After that you have installed the driver, open the "Device Manager" from the "Start"-button and choose "run..." type DEVMGMT.MSC and press OK.
Double-click "USB Serial Port" which is found under Ports(COM&LPT).
Under the tab Port Setting press Advanced
Mark Disable PNP and press OK.
Done.

Note!
-If you have WindowsXP or Windows2000 you can't choose to disable PNP.
-If you have an old version of the driver, see question 13 how to install a new driver

When opening the the file it will extract itself in either C:\R9032148 or C:\P8002104 depending on which file you have downloaded.

To install a new driver

To uninstall/erase an old driver:

• Disconnect the programmer/phoenix-reader from the USB-port
• Open the Controlpanel and choose "Add/remove program". Find "FTDI USB Serial Converter Drivers" and follow the instructions
  on the screen to remove this.

When installing a driver it will choose the first available number that in some cases can be for example COM 5. This is not supported in some softwares.
Here's how to rename a COM-port:

Note! The non-certified driver R9032148 must be installed.

Open the "Device Manager" from the "Start"-button and choose "run...", type devmgmt.msc and press OK.

Find a COM-port which you're not using for the virtual comport. 

"Right-click" on this COM-port and choose deactivate

"Right-click" again and choose uninstall

Then choose properties for the virtual COM-port(USB Serial Port) under ports, choose advanced. Then choose the COM-port-number that you just erased.

Close the "Device manager" and open it again. Now shall the virtual comport have got the new name.

Then press under action in the menu "search for hardware changes" and the previously erased COM-port is found again.

Then use for example 'echo' to send digits inside the " to the programmer. In this case the programmer will be set to
phoenix 3.58 MHz:
echo -n "*}" > /dev/ttyS6