Another question, i measured the alternating votlage(AC) it was about 19v
and also measured DC voltage at the output of bridge recitifer and it was about 23.7v, i think these these values are consulted depending on the law: Vdc=Veff*root(2), but i'm not sure....what's your opinion ?!
As a general rule, it's good design practice to just ground them all, as everyone simply assumes that everyone else grounds them all. This way, anyone who is going to modify your design won't have to waste time figuring out why some pins are not grounded, and just in case the parallel port on the host side fails to ground all the pins.
Another question, i measured the alternating votlage(AC) it was about 19v
and also measured DC voltage at the output of bridge recitifer and it was about 23.7v, i think these these values are consulted depending on the law: Vdc=Veff*root(2), but i'm not sure....what's your opinion ?!
AC voltages are normally given in rms values.
AC-DC conversion involves full-wave rectification, followed by a low-pass filter. Vac*root(2) gives you the peak value of sinusoidal AC. Depending on the quality of your low pass filter, the resulting DC voltage should be slightly lower than the peak sinusoidal voltage.
if you tried looking at www.beyondlogic.org, it says that pins 18 to 25 are ground (standard parallel port with 25 pins).
i checked my parallel port with multimeter, it seems that 18 to 25 ground pins are already connected. i agree with checkmate that its a good practice to have a robust grounding connection.
Link pins18-25 with a thin wire at the DB25 socket of the programmer(I'm assuming you're building a programmer). Very easy to do and avoids all problem with different cables. Cheap cable has only one core for ground connection and which pin it connects to is anyone's guess although good cable manufacturer would certainly links all the above pins but who knows.
The red led and green led next to each other in programmer p16pro40 didn't light that is they didn't work and other red led did work...
I haven't placed my pic in the circuit yet , might be that the reason or likely there's another reason?!
Something like you've got it set to the wrong parallel port!, you can check using the hardware toggle buttons in WinPicProg and a simple meter to check the voltages.
Something like you've got it set to the wrong parallel port!, you can check using the hardware toggle buttons in WinPicProg and a simple meter to check the voltages.
I tried the buttons located in hardware options but i really don't know what's happening , i didn't know what is the function of each button, so i became a little confused!!
Something like you've got it set to the wrong parallel port!, you can check using the hardware toggle buttons in WinPicProg and a simple meter to check the voltages.
I tried the buttons located in hardware options but i really don't know what's happening , i didn't know what is the function of each button, so i became a little confused!!
All a parallel port PIC programmer does is 'wiggle' the output lines UP and DOWN, the hardware toggle buttons let you do this manually, so you can test the results with a voltmeter.
WinPicProg automatically detects the programmer on the port, so for a start, is it being detected? - the power to the programmer must be turned on for this to work.
Assuming it is, toggling Vdd should turn the Vdd LED ON and OFF, likewise toggling Vpp should switch the Vpp LED.
Measure the voltages at the following test points A-H, without the parallel cable connected, no PIC in socket and just DC power to the circuit. Black lead of meter connects to 0V.