16F627 PIC Problem with K8048

Hello,

I’ve had a pre-constructed K8048 lying around for a while now, and I finally got the time to mess around with it.
Unfortunately, I’ve immediately run into trouble, trying to transfer the example program to the pic.
Whenever I do anything in PicProg2009, it says, “The settings don’t match the Pic in the programmer.”
Whenever I hit write it immediately fails. As you may already know the first 2 bytes of the program read 280A.
When I read the program from my PIC the result is 280# where # is random, followed by 3FFF, which I assume is the highest possible value. Is my PIC broken? Or is there another possibility?

For completeness, here is my PicProg setup:

Thanks for reading
Gazok

Hi,

Looking at the screen shot it looks like you have the software setup for the K8076
I think you need to go under functions hardware and change it to the K8048

Hi, thanks for your response.

What makes you think that? At the top, it says K8048. Here’s a screenshot of my Hardware Config panel:

I was looking at the picture of the K8076 in the upper right corner.

I thought when the K8048 was selected it would be blank.
I guess it just dims.
Sorry about that.

No problem.

I just read that if the PIC has enough power, with SW5 set to standby, LD1 should be on, which it isn’t. I’m using a 12V AC/DC adaptor at 500mA - I guess this isn’t sufficient?

If your using a 12 volt power supply it needs to be unregulated.
The kit requires 15 volts to work properly

Okay, I’ve got a 15V 500mA AC/DC adaptor, and a new 16F627, and I still have the same problem.
I’ve also noticed that a lot of people have trouble with USB-Serial connectors. I would have thought it wouldn’t work at all, had that been the problem, but I’m not sure.
Any ideas?

Never use an USB-serial converter for these kinds of applications. Problems almost guaranteed…

Real serial ports are hard to find these days.

Even things like ExpressCard serial adapters are often USB ports with on-board USB->Serial converter.

They apparently still are there on even the cheapest motherboards, but their headers aren’t used.

Explains a lot. My motherboard doesn’t have a serial port, but Windows reports a COM port anyway. I do have an old PC with a serial port somewhere, I can’t remember if it works or not, I might need to change some hardware first. I’ll dig it out and see if that works with the PIC at some point.

And it probably has the actual hardware for it, just that there is no DB9 on the connector shield for it.

Check your motherboard documentation. It may have a 10-pin header for COM1. You might then need something like this:

frontx.com/cpx102_2.html

Just make sure the pinout is correct.

I just recently finished assembling my K8048 programmer and ran into similar issues. At first the board was not recognized by the PicProg2009 program. Then I realized the hardware setting defaulted to the K8076 board so I changed it. Next I had some issues recognizing my 16F627 that came with the programmer. Then I realized the selection I made in the pull-down for the controller type had changed. As a result I was targeting the wrong chip and didn’t notice it at first. I believe this happened when I tried to scroll in another window with the mouse wheel but was actually still in the PicProg2009 program with the PicType pull-down highlighted. o I fixed that a well. Still no luck. I found all kinds of references to serial port cabling references, voltage problems, etc. All to no avail. I checked several voltage on the board which were correct and verified I didn’t, somehow, solder in my LD1-6 backwards accidentally. All good. Having a bit a software background, the thought occurred to me that I hadn’t closed the PicProg2009 program after changing the hardware configuration. Knowing that sometimes programs only initialize everything properly on start-up I gave this a shot. I closed the program, re-opened it to make sure the settings were still the same and tried to download the program again. Even though I tried this several times earlier and the download appeared to work, this time it actually did! I switched to RUN mode and sure enough, the LEDs started cycling as I expected based on the demo1.asm program I was attempting to download. Wow, what a waste of time. Very frustrating. Now maybe I can get to some learning…
Hopefully this helps someone else struggling with a similar problem.

Oddly, when I tried to test the second demo, I got a message when I start the PicProg2009 program that the pic in the programmer does not match and asks if I wish to continue or not. The settings are still the same as when this worked with the first demo so I indicated yes and loaded the new demo.hex file. I was able to download the program and it worked as designed so I’m not exactly sure what this was complaining about. The only thing I was wondering i that the chip I got with the programmer is a PIC16F627-04/P. I’m not sure if reports some kind of an ID differently that the programmer software thinks it doesn’t match even though it’s the closest match in the list of types. Anyone know if that makes sense? Seems to work either way which is good for now.

Hi Folks; Thank you for letting me join this board.
I purchased my K8048 some time ago and have been using it without problems. It is an excellent product for the money. Here is list of my current configuration. I hope it helps some of the individuals with troubles:
Computer: ASUS ITX mainboard; AMD E-450 CPU:1G65; 8GB RAM; 64B-windows-7 Ultimate
PORT: Prolific USB to Serial Adapter configured as COM4;
Power to programmer: 15VDC 1AMP DC. ** I believe this to be critical **

Working Software:

  1. PICPGM programmer version 1.6.5.0 picpgm.picprojects.net
  2. ProgPIC2 Revision 2.3.1 Velleman software
  3. PICprog2009 Version 3.0.05 www.RE-applications.be

Sometimes it is tricky and I have to force the PIC device name into the software as autodetect does not work. After this it is fine.
My worst difficulty is reading the PIC device name on the chip itself.

Good luck and a happy 2013.