I have experienced exactly the same problem than you jm.
The first thing I did was to change the PIC : I've replaced the original 16F627 by a 16F84A one.
The problem remained. Exactly : "no device ID received" whit the 16F627 and
"write error..." with the 16F84A.
I've then reinstalled the soft PROGPIC2.EXE, without success.
I've also replaced the non-regulated 12 Vdc supply, no more success.
I've then measured, with a Tektronix TDS 210 scope, the non-regulated voltage produced by both supplies : it appeared to be near well regulated (!) at +/- 17V3...I thought the problem was not there.
Please note that my PC offers two serial ports, my scope was connected on COM1, and the VM111/K8048 on COM2.
I've swapped the VM111 with the scope : it now works well with the 16F627 but the problem persists with with the 16F84A...but maybe that the 16F84A is out of order?
Of course my scope still works well on COM2.
Don't ask me why the fact of use COM1 instead of COM2 SEEMS to solve the problem (of course I knew that the COM's can be selected with PROGPIC2...)
I think that peoples, like you and me, experiencing this kind of problem, have not to look on the hardware side (bad programmer, bad PIC, bad cable,...) but on the software side.
I think the first thing to do is to uninstall ALL the devices addressing a serial
port (except the VM111), even if you think that they do not address the COM# where your pic programmer is connected, connect the pic programmer on COM1, and then retry...but I'm absolutely not an expert.
Hope this will help. |