I had the same annoying problems with an 18F4520. Sometimes yes, sometimes not, then again a non-working program !! Luckily I still have my old wisp. Connected and everything works flawlessly, just like before . If something didn't work for me in the past, I was sure it was my fault. !!! Wouldn't Wouter be able to expand his wisp so that it can also handle the newer things? Otherwise I think I'll just use pics that the wisp supports. There's plenty of fun to do with that.
Op zaterdag 12 november 2022 om 07:06:16 UTC+1 schreef vasile: > Rob, prior to throwing it away, plug it in a stanium foil for a while to > short all pins together. > Old PIC12F675 had this problem with address 0 and this was in a surprising > way the cure. > > Of course, only if you did not supply it at 220V, see the top right > corner... > http://www.voti.nl/wloader/index_1.html > another one of my daughter's old drawings...:) > > > On Fri, Nov 11, 2022 at 9:53 PM Rob CJ <[email protected]> wrote: > >> Hi Evan, >> >> Downloaded, installed it and it work for my PIC16F18857 (also programmed >> a PIC 12F675 and works OK). >> >> I still get the error on the PIC16F18857 that it is not able to program >> address 0x0000 (verification error) but I think the PIC died so not related >> to the PICKit3 software. I will try with a fresh version. >> >> Thanks for the quick service. >> >> Kind regards, >> >> Rob >> >> ------------------------------ >> *Van:* '[email protected]' via jallib <[email protected]> >> *Verzonden:* vrijdag 11 november 2022 19:10 >> *Aan:* jallib <[email protected]> >> *Onderwerp:* Re: [jallib] Re: PICKIT 3 problems >> >> Just sent the order go through the process. >> >> If you have issues, then, we can set about resolving for you and the >> greater community. The new release has the new 16F180xx and 16F171xx >> chipfamily - we are waiting on the 16F181xx to arrive before we can add >> (as we have to test them!). Also, adding more PIC32Mxs at the moment. >> Always busy. >> >> On Friday, 11 November 2022 at 17:59:56 UTC [email protected] wrote: >> >> Hi Evan, >> >> I noticed indeed issues with PICkitminus that it sometimes recognizes >> another PIC than the one that is installed. >> >> So in order to get rid of this - and other issues I encountered - I just >> ordered your PICKitPlus software for my PICKit3 🙂. >> >> Kind regards, >> >> Rob >> >> ------------------------------ >> *Van:* '[email protected]' via jallib <[email protected]> >> *Verzonden:* vrijdag 11 november 2022 07:51 >> *Aan:* jallib <[email protected]> >> *Onderwerp:* [jallib] Re: PICKIT 3 problems >> >> As the real developer of PICKitPlus and the database that was plagiarized >> by PK- I am the right person to help. >> >> When our database was copied the developer decided to change the order >> that the chip families are searched. I wrote a detailed analysis for him >> and he ignored. So, using PK- can apply the incorrect voltage your PCB >> during startup. >> >> Which chip or chips have this issue? This will help me isolate the issue. >> >> Evan >> >> On Friday, 11 November 2022 at 06:43:29 UTC hans wrote: >> >> Hello all, >> >> I regularly have problems with the pickit-3.(MPlab X IPE v 5.45) . >> >> Because it happens less often when I first start up my PC, connect the >> pickit to the PIC and put voltage on it and only then connect the USB >> cable, this is my base. >> >> Despite this, I get often messages that the voltage is insufficient, >> the PIC is not the right type or a wrong feedback occurs during >> programming. This can almost always be solved by restarting MPlab, or by >> first performing a read or an erase. >> >> Lately I've been working with 3.3V. Now I had a program under 3.3V and >> that didn't work at all after programming without errors. After I erased >> the PIC separately below 5 V, the program works again. >> >> I have two clones. One suddenly doesn't work at all under 3.3 V, but with >> the Pickit_minus (with modified firmware) on 5V. >> >> Can anyone tell me where to look for the cause of all this? >> >> regards >> >> Hans >> >> -- >> You received this message because you are subscribed to the Google Groups >> "jallib" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/jallib/e74098b6-6d7d-45a6-ba6c-087cc51faadcn%40googlegroups.com >> >> <https://groups.google.com/d/msgid/jallib/e74098b6-6d7d-45a6-ba6c-087cc51faadcn%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> >> -- >> You received this message because you are subscribed to the Google Groups >> "jallib" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/jallib/64b27e61-12c7-451c-85e4-5c743cb3b417n%40googlegroups.com >> >> <https://groups.google.com/d/msgid/jallib/64b27e61-12c7-451c-85e4-5c743cb3b417n%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> >> -- >> You received this message because you are subscribed to the Google Groups >> "jallib" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> > To view this discussion on the web visit >> https://groups.google.com/d/msgid/jallib/GVXP195MB16375063A36BD0B02383E0C0E6009%40GVXP195MB1637.EURP195.PROD.OUTLOOK.COM >> >> <https://groups.google.com/d/msgid/jallib/GVXP195MB16375063A36BD0B02383E0C0E6009%40GVXP195MB1637.EURP195.PROD.OUTLOOK.COM?utm_medium=email&utm_source=footer> >> . >> > -- You received this message because you are subscribed to the Google Groups "jallib" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jallib/2cbd8c03-6b6b-4203-9ff4-32d82cb8d2f9n%40googlegroups.com.
