So, what are people using for CHEAP ICSP programmers these days?

[TrueMetalGeek]

Hey all. I've been using a Kit149 programmer for years running Microburn software. One of them died and I'm still on my second one but it's getting worn and sometimes acts up.
Anyway I have ordered a few Pickit3 knock offs from Amazon which would work for a while then something happens to them. I don't know if the knock offs are very sensitive to being connected to my circuit at the same time but my old Kit149 usually just has a hickup and then works again after it resets but the PicKit 3 just dies.

Anyway I ordered a kit150 off of ebay. Cheap.
Man. It is using that horrible prolific usb to serial chip that Windows 10/11 hates. And even after I get a driver to work and see it at all, microburn doesn't connect to it. So that was junk.

So I thought before I searched and took a chance on something else maybe I'd ask you guys what is a good cheap programmer tool.

I see that Microchip uses pikit4 or something like that, but that thing isn't cheap and if it is sensitive and will fry easy like the pickit3's then I don't want that. But of course the pickit3 issues could be because they are knock offs.

Anyway. When I did get the pickit3 to work initially I did get it to work with Microcode studio with some setup info I found on the forums.
It just didn't last more than a few uses the few times I bought one. :-(

[Ioannis]

I use Pikprog+ by Elnec for many years (this model is not in production now and is based on parallel port!), Pickit 2 and Pickit3 (original by Microchip) and ICD3.

I can say that never had any issue, except a static discharge that killed a pin on the Elnec programmer and this was fixed in no time by the manufacturer.

Also recently used a clone of Pickit 2 with success.

For stand alone software I use this https://pickitplus.co.uk/Typesetter/index.php/Software which is more than GREAT! Evan Venn that made the stand alone IDE for Pickit2 and 3, is very helpful and solves any problems asap. He also sells his design Pickit 2 clone kits if it is enough for your needs.

So, I guess looking around costs more money at the end. Buy a good and trusted programmer that will save you time, frustration and money.

Ioannis

[mpgmike]

The price leader for quality would have to be the Snap Programmer from Microchip, $34.09 (USD). It cannot power the target, but other than that, it does everything the PICkit4 does. Oh, it requires LVP (Low Voltage Programming) CONFIG.

https://www.microchip.com/en-us/deve...-tool/PG164100

[tumbleweed]

I've used all the Microchip ones, and even a few pickit3 clones and never had an issue with any of them.
If you keep blowing up PK3's then it could be your setup/configuration (not using MCLR, setting RB6/RB7 as outputs, etc).

If you've been using the kit149/150 then you must be using some OLD chips, stuff from the 1990's/early 2000.
If that's the case you'll want to get a programmer that can do HV programming, which some of the pickit3 clones can't do and neither does the SNAP.

The SNAP and pickit4 will require you to install MPLABX to get the drivers, so that's a negative, plus you're pretty much limited to command-line operation with them (no programming app except for MPLABX)

From what you've described you've been using, I'd second a vote for the Pickitplus software with a decent pickit3 clone, although that might be getting harder and harder to come by these days.

[tumbleweed]

I like to support the folks at pickitplus, but if you're really strapped for cash there's a similar free version called pickitminus at http://kair.us/projects/pickitminus/
It's not as up to date as pickitplus, but for free it's hard to complain.

[TrueMetalGeek]

The PICKIT 3 was nice when it worked as it worked with the MPLAB and Microcode Studio when I added the command lines I found on the forums.
So I have been using 16F690's most exclusively. Data, Clock and VPP are all on port A. VPP is on an input only port and I most often used the port a0 and a1 as inputs where data and clock are but ya know, I wouldn't doubt that I left those to default outputs when I start a new project. So you think it could be as simple as the a0/a1 (data/clock) being latched down that fries the programmer?

I do most often power the PIC buy my circuit and so now that I think about it, after the first program when it starts it will have A0 and A1 as outputs (if I don't change it right away in my first program) and held low if I don't first set them as inputs or isolate them.
I also use the MCLR pin as an input rather than as MCLR. Would that be an issue? I wouldn't think so unless there is something I don't know with that.

I'd try another PICKIT 3 if there was a reason for the failures that I could remedy it in the future.
I also see that PICKIT 2 clones are closer to $20.

Oh yeah. I see that Adruino stuff is coming down in price but I am so used to PIC and I like building minimalistic boards to do various things with the small cheap $2 PIC's and I'd have to learn the C language better when i am used to PIC BASIC (was used to that since the Tandy 8000/VIC20 days)

I've used all the Microchip ones, and even a few pickit3 clones and never had an issue with any of them.
If you keep blowing up PK3's then it could be your setup/configuration (not using MCLR, setting RB6/RB7 as outputs, etc).

If you've been using the kit149/150 then you must be using some OLD chips, stuff from the 1990's/early 2000.
If that's the case you'll want to get a programmer that can do HV programming, which some of the pickit3 clones can't do and neither does the SNAP.

The SNAP and pickit4 will require you to install MPLABX to get the drivers, so that's a negative, plus you're pretty much limited to command-line operation with them (no programming app except for MPLABX)

From what you've described you've been using, I'd second a vote for the Pickitplus software with a decent pickit3 clone, although that might be getting harder and harder to come by these days.

[tumbleweed]

I do most often power the PIC buy my circuit and so now that I think about it, after the first program when it starts it will have A0 and A1 as outputs (if I don't change it right away in my first program) and held low if I don't first set them as inputs or isolate them.
I also use the MCLR pin as an input rather than as MCLR. Would that be an issue? I wouldn't think so unless there is something I don't know with that.

If you don't let the pickit control VDD then there are configurations that, once programmed, can prevent the PK from being able to put the part back into programming mode.
It would have to use the VDD-first method, and that method of entry is valid only if INTOSC and internal MCLR are not selected.

Also, make sure that there is nothing on the MCLR/VPP pin that would prevent the programmer from raising it to 12V.