MPLAB X: Target device was not found (could not detect target voltage VDD)

[BoboHan]

I'm in the process of making a DC-motor . However, I'm getting an error, the problem is that my PICKIT3 will not connect to the microcontroller. What am I doing wrong?

I'm using PIC16F15325 controller and using MPLAB X IDE v5.45. I'm using PICKIT3 for programming/debugging.

What I think has gone wrong; could it be because pin 5 on PICKIT3-PGC is connected to VDD on the PIC?

Here's the output:

*****************************************************

Connecting to MPLAB PICkit 3...

Currently loaded firmware on PICkit 3
Firmware Suite Version.....01.56.07
Firmware type..............Enhanced Midrange

Target device was not found (could not detect target voltage VDD). You must connect to a target device to use PICkit 3.

Here are my circuits and schematics:

What do I have to do, any suggestions?

 

[hexreader]

You have connected PK3 in reverse...

https://components101.com/misc/pickit3-programmer-debugger-pinout-connections-datasheet

 

[Pommie]

As mentioned, you've connected it wrong. Plus, you need to power the circuit to get it to work. The PK3 will not power your circuit.

Mike.

 

[BoboHan]

You have connected PK3 in reverse...

https://components101.com/misc/pickit3-programmer-debugger-pinout-connections-datasheet

So actually on the last picture I have attached, so the last (left) has no connection? So basically, the one to left, has to be free (not used)?

As mentioned, you've connected it wrong. Plus, you need to power the circuit to get it to work. The PK3 will not power your circuit.

Mike.

What am I doing wrong, I'm now using this power supply.
I've followed several tutorials on how to connect PICKIT3 to PIC, but that's what I got from them, what pins are wrong?

Here's my updated schematic, I am in the proces of making an 'smart project', where I'll control two DC Motors and a buzzer connected to the PIC microcontroller from a android phone wireless, through bluetooth.

Is it completely wrong done?

 

[Dr_Doggy]

the arrow on pickit is mclr, vdd is beside it

 

[BoboHan]

the arrow on pickit is mclr, vdd is beside it

Yeah, I found that out. Thanks for helping.

I got the 'programming/debugging complete' output, but however after trying to run the project a few times all of sudden it stopped working, and I am now getting:

Loading completed
Connecting to programmer...
The programmer could not be started: null

Any idea, why I am getting that. And I haven't changed anything.

 

[BoboHan]

As mentioned, you've connected it wrong. Plus, you need to power the circuit to get it to work. The PK3 will not power your circuit.

Mike.

I actually got it to work, but after a while (10-20 minutes) it stopped working. Could it because the battery is done?
(I know the power supply is off now, just turned it off)

the arrow on pickit is mclr, vdd is beside it

Yeah, I found that out. Thanks for helping.
View attachment 131237

I got the 'programming/debugging complete' output, but however after trying to run the project a few times all of sudden it stopped working, and I am now getting:

Loading completed
Connecting to programmer...
The programmer could not be started: null

Any idea, why I am getting that. And I haven't changed anything (posted an image above of the power supply with battery).

 

[BoboHan]

I am getting 'Failed to program device... Target Vdd not detected. Please ensure the target device is connected' - So that means, that the battery is done?

 

[Pommie]

Exit everything, unplug the PK3 and try again. MPLABX is disgustingly buggy and Microchip should be VERY ashamed of it.

Mike.

 

[KeepItSimpleStupid]

MPLABX is disgustingly buggy and Microchip should be VERY ashamed of it.

I've heard the same thing about Reneses software.

 

[granddad]

How long are the wires from PK3 to mcu ? They need to be as short as possible..

 

[granddad]

MPLABX is disgustingly buggy and Microchip should be VERY ashamed of it.

Have to agree, But it has improved slowly , and the linux version (with www switched off ) works fine for me (mostly) .