If you are experiencing problems with the programmer please look through these items.
Programmer Not Responding
This can have many causes.
Reset Polarity
Try changing the reset polarity option.
Check the one that is NOT checked and try resetting again.
Components and Connections
DO NOT TOUCH THE BOARD CONNECTIONS. SOME COMPONENTS MAY BE DAMAGED OR DEGRADED BY STATIC ELECTRICITY DISCHARGES.
Please go over your construction work and check all parts orientation and placement. Also check for shorted tracks and solder bridges.
On Kit 149-A, diode D3, has a via next to the component hole on the anode side. Make sure this component is placed correctly.
Make sure all polarised components like electrolytic capacitors and chips are inserted correctly.
Make sure the crystal(s) are 6MHz in all kits.
Look closely at the FTDI chip connections and make sure they have been presoldered properly at the factory.
Power Supply
K149-A, K149-B and K150 need at least 16VDC to operate properly. 18VDC is preferred. The supply must be able to provide at least 200mA at these voltages.
The power connector for these kits has a centre positive connection.
K128 is powered from the USB port.
Verify that the red PWR indicator LED is on after powering up the kit. K128 will flash red/green before settling to red.
Using a voltmeter…
On K149 kits, check that 5VDC is appearing on the test pads.
On K150 you can only measure the voltage on the PICMICRO© pins 14(+ve) and 5(-ve). You should read 5V.
Please select 16F877 chip. With no chip in the programming socket. Connect a volt meter +ve to socket pin 1 (top left corner), and -ve to test GND on PCB.
Click [READ] and don't cancel when error messages appear.
Verify that 12-13VDC appears while reading.
Connect a volt meter +ve to socket pin 35 (right side, 6th from top), and -ve to test GND on PCB. Click [READ] and don't cancel when error messages appear.
Verify that approx 5VDC appears while reading.
If not, you need to check the PCB for problems.
The power supply jack is 5.5mm OD, 2.5mm ID DC type.
Inadvertent short circuits in the programmer socket may cause the programming voltage control transistors to be damaged.
Serial connection
Check your serial cable. It should not be a NULL modem type. It needs to be a straight through type. Eg. Pin 1 to Pin 1, Pin 2 to Pin 2 etc.
Make sure the COM port is selected properly and open and the serial cable is connected to the selected COM port.
Make sure the COM port is active in MicroPro.
If you are using the USB connection, make sure the cable is connected correctly and the FTDI drivers are installed properly. Visit their web site to download them.
http://www.ftdichip.com/FTWinDriver.htm
Do not use the new enhanced drivers.
Any problems related to the USB driver should be directed to the FDTI web site.
http://www.ftdichip.com/
If [COM x] is showing in the MicroPro status area then the COM port is not active. (Serial or USB)
On K149-A and K149-B make sure the COM switch is set to [USB] if you are using USB and [Serial] if you are using the COM port.
Make sure the cables are connected and apply power.
If you have a terminal program, run it and set it to 19200 baud, 8 bit, No Parity and 1 Stop Bit. (19200, 8, N, 1)
Send HEX values, 0x50 then 0x16.
The firmware will respond and send the ASCII protocol number back.
It will have the ASCII format 'P' 'P' '0' '0' '?' where '?' is the protocol number.
If this does not occur, then you need to verify your connections and circuitry around the ICL232 chip, or the FTDI USB chip.
If you did manage to read the protocol number then run MicroPro and verify that it is the same as the version you are using. If not, check the KitsRus web sit for the latest upgrade. You may need another PICmicro® programmer to perform the upgrade.
http://www.kitsrus.com
USB mode may be slightly slower than Serial mode because the USB driver must convert the data from Serial -> USB -> Serial.
Programmer Verify
To verify the programmer, connect it to the PC and apply power. Run MicroPro and you should see Board Connected appear. The software may auto connect if a different programmer is selected.
If the programmer appears to work, but only programs 1 or 2 locations and then reports a connection error, then it is likely that the firmware is not matched to MicroPro. Check the protocol number in Help -> About.
Reading and all 0000’s appear
This may mean that the Code Protect Fuse is set on the chip you are trying to read from, or the chip has not been inserted into the programmer socket properly. The chip may also be damaged. Check the PCB as described above.
K128 was not designed for ICSP programming, although some have tried and it does work. The high voltage programming supply for K128 is very HI-Impedance and may not work.
HEX File Won’t Load
Some chips require HEX files to be of a certain type.
12 and 14 bit PICmicro® chips can have HEX file types of INHX8M or INHX32, but PICmicro® chips in the 18F family require INHX32 only.
See your compiler for details.
“F” series chips program, but “C” series won’t
Check that your programmer power supply is supplying at least 18VDC at 200mA.
You cannot ERASE a “C” series chip unless it is a JW type and you have a UV eraser.
Is the “C” series blank before programming.
“C” Series PICmicro® chips cannot be programmed by the K128 programmer. It will only program FLASH type “F” series chips.
What is the LOW ICSP Programmer Connection?
This is an open collector output and may be used to pull the LVP or OCS1 pins low while programming. It may also be used for some other function on the target board.
Check your source code
If all else fails, maybe your code does not work. Please check your source code. It may be the solution to the problem. Maybe your FUSE settings are incorrect.
Chip ID’s
Some PICmicro® chips do not have a chip ID. The 16F84 is an example. You may receive an error message stating this.
My chip gets warm in the programming socket
This should NOT happen. Please check your hardware for problems. Make sure there are no stray voltages present in the programming socket when the board is idle. Check that your chip is inserted correctly.
There is a PCB modification for Kits 149A 149B and 150. Please see the file called “resmod.pdf” in your installation directory.