I thought the word for VRCON, CMCON etc. is fuses. Good to know better.
So what I want to know: Which numbers are to be used for VRCON and CMCON for the effect wanted?
|
I thought the word for VRCON, CMCON etc. is fuses. Good to know better.
So what I want to know: Which numbers are to be used for VRCON and CMCON for the effect wanted?
|
Generally speaking - the 'FUSES', specifically CONFIG fuses are set a programming time by the programmer.Originally Posted by Ted's
Anything else that can be set at run time (including ram used for variables) are called registers.
Hate to say it, but it's all in the datasheet for your PIC.So what I want to know: Which numbers are to be used for VRCON and CMCON for the effect wanted?
|
I know, skimask. But I would not ask if I could filter out the useful information myself. If you do not want to tell me, fine.
Can you help me out here aswell, g-hoot?
|
It's not that I don't want to tell you (like it's some sort of state secret or something). I mean, look at the project. You obviously have a clue as to what you're doing and how to get there from here. It's just that I would've led you to the right piece of information sooner or later, then you could've figured it out for yourself....that whole 'give a fish, teach to fish' thing...
|
Ted's,
I think I understand this less than you, so don't put too much faith in mu help. I still don't understand what a comparator does?... The idea of checking for high or low is what I like best (cause it's simple), but I guess there can be some issues with in bouncing like skimask mentioned. Maybe you could use a weak pull-up resistor to keep the pin high to prevent the bouncing problem. Or, you could simply cut and paste the RCTime code I posted and be done. ;-) I agree with skimask that all the info is in the data sheet, but I still have a hard time understanding what the data sheet says! They sure aren't written for people that are using PBP! That's why I posted my exact RCTIME code for you. I know to most here, that it is day one basics, but for us new guys, it's like learning a new language, and a little spoon feeding is nice and helps in understanding what's going on. :-)
Gary
|
I agree, the manual is not written for people using basic. And on the right site in the pdf manual the pictures of comparator configurations don't show the configuration I need.
|
The PIC datasheet and the PBP manual are 2 different worlds, connected by a common purpose...True. It's not like a car owners manual vs. an engine overhaul manual. Agreed. But...PICs ain't cars and cars ain't PICs. And you can't reconfigure a car to haul satellites into orbit.
As far as the comparator goes...if the right configuration isn't in the datasheet, it probably can't be configured the way you want to be....
Which is what again? Maybe we can come up with a workaround for ya...
|
With my wire and duct tape, and your BFH, we can do anything! HA
I understand your analogy about the car owners manual vs. an engine overhaul manual, and you are right....but, Look at the attched pic for an exaple of what I'm talking about though. When I wanted to use EEPROM, that is the example in the datasheet for my chip. I guess that's assembly language? It don't look anything like that in my program. It almost makes sense in PBP. :-) Would be nice if they offered examples in the common languages. I like stuff like "Read, Write, If, Then" that makes sense. I mean no disrespect. I'm just whining cause I'm a rooky an don't really understand what's under the hood! ;-)
Gary
Members who have read this thread : 0You do not have permission to view the list of names.
Posting Permissions
Bookmarks