This looks sooooo familiar.
There is project building. Planning and physically building a project. Writing the code and testing. When it does something unexpected (that would include not working). There is “troubleshooting”.
Troubleshooting is an art. There are efficient ways and there are inefficient ways to accomplish the same end. The problem seems to be that some people just want the answer, not the procedure. They seem to think that someone can see their circuit, and mystically, clairvoyantly, pass their long-distant hand over the program or circuit and KNOW what their mistake is.
Real problems arise when the person ASKING for HELP thinks the helper is just asking silly questions and asking them to do silly things. All that the person ASKING for help wants is an ANSWER. So they end up DEMANDING that the foolish, silly, questions STOP, and GIVE ME THE ANSWER that I need.
So we are “stuck” with the “basic” truthful ANSWER , “I Don’t Know”.
See also
Originally Posted by
Eng4444
i did the same connections shown in the shematic , downloaded the same program (that is displayed here) inside PIC16F628A, gave 5VDc and checked the connections again. But i didn't see anything on LCD.......
...SO now, you will keep on saying that i have to read datasheets??
or you will try to help me in an effective way?
Friday i will present it in front of jury and MONDAY..... i'll graduate :-) and since then, i'll pass a whooooooole month in the Carribean!
...so i will just sleep......
Please guys, take it into consideration and check that schematic and program... tomorrow i'll be well awake so i'll concentrate on your replies and try to accomplish what you told me to do..
But please, please , please........ stop talking about datasheets...
-Adam- (this was mis-posted (by me) should have gone in answer to: http://www.picbasic.co.uk/forum/show...2&postcount=25
Last edited by Pic_User; - 20th October 2008 at 16:09.
Ohm it's not just a good idea... it's the LAW !
Bookmarks