> >>ahh thx for the note,,
let me re-model the conflict so we can get a better view and to get sure i'm knowing what i am talking about..
in pic we must keep a 5 volt on reset"mclr" in all times...so that's clash's with the idea of the output pin...right.
Yes that’s right I normally do this via a 10k resister, although I have in the past omitted the resister and directly clamped from MCLR/VPP to VDD, - if not using reset control or/as well as ICSP (In Circuit Serial Programming requirements is 20k resister or a diode in series with a 10k resister between MCLR/VPP and VDD), though Microchip don’t advise this procedure on there microcontrollers.
that's what i was afraid from..and that's why u shouldn't build a project with an unknown lang ...if i had any knowledge with c i would choose "1"for sure...i would simply change the code "which i think not that big of a deal" so i could use another pin for f....or i would choose "2" simply larger pic will solve the problem..
both choices will spare me the twisted number's..
as for my situation not knowing c...i have no choice but taking "3" building the project on test board and at the same time getting a small idea on c so i can solve the problem and changing the pic to a larger 1.
violin as i said it's a project i should do for a doctor whom won't take a bascom avr project..and the deadline getting closer so i am in a kind of a pickle..
Thank u for your concern,,,keep in touch..soon i will post the pic's of the test board version on the forum if nothing gone wrong ...like the problem i had with the pizo-mic that was damaged from the source and have to replace it tomorrow.
For me if I were to take on this particular project, I would start off with option (2). This is because I am so used to porting/translating codes over from one device to another although mostly in assembly language so far and I know that the only change in the program is the device selected and its configuration bit changes, which is unlike option (1) changes required. It will also give me extra free pins for expansion options.
For any beginner, not saying that it includes yourself as I don’t know your level of experience/skills, - I would say option (3) would be the best route to take. This way you can follow the projects guide step by step to a working model and at the moment I don’t feel that are any other issues relating to it.
Option (1) would be for those who are familiar with C-language that can easily make the transition from one pin to another within the program and who will not be looking for expansion at any time with the project.
ps:...u didn't answered me about the book...so i guess u are not interested and u have another source for learning c...
I don’t have any other source into C-language skills other than stuff that I find on the internet so I am very interested in this particular book and any other source that may aid my progress into my knowledge of C-language. I appreciate that very much. Thanks. At the time my interest was only to concentrate on the project issue and didn’t feel to make diversion to my own personal interests.
I'll say goodnight to you now being the time as it is here. A little bit of music practice for me now before I get ready for sleep. - Via headphones of course.
