New project help rapidfire on 12f683

[thm ov3rkill]

hey joe what mode should i use the turn the rapidfire off i can make it go to sleep. the most it can sleep for is 19 hours but i hihgly doubt anyone will play for that long also im a bit confused on that code


what will i write to cheak for the button switch cause if i put it as main it will jsut restart thansk joe

[skimask]

hey joe what mode should i use the turn the rapidfire off i can make it go to sleep. the most it can sleep for is 19 hours but i hihgly doubt anyone will play for that long also im a bit confused on that code

what will i write to cheak for the button switch cause if i put it as main it will jsut restart thansk joe

First off, why not trying to type a bit slower or something, maybe add something like punctuation. Makes it just that much easier for the rest of us to read.
Second...You might want to try and write out exactly what you want your 'buttons' to do, flowchart the whole thing.
I'm reading through this and your other threads over at Microchip, and your ideas are half-structured at best. You seem to be hoping that somebody will just come up with the magic code for you and it'll all be done.
Joe's code, a couple of posts above, is a good base for you to add onto. I think the end result that you desire is just as easy as what Joe has written up. Why not just try a few things here and there? Then, when things don't work as expected, post the code YOU wrote and the rest of us can help YOU figure out what YOU did wrong, rather than the other way around. As has been said here before, this isn't a 'drive-thru get your code' forum, although a few would be more than happy to write the code for you, I don't know of any.
After that, you might want to hit the books a little bit and do some reading on the SLEEP command for putting your PIC into SLEEP mode.

[thm ov3rkill]

First off, why not trying to type a bit slower or something, maybe add something like punctuation. Makes it just that much easier for the rest of us to read.
Second...You might want to try and write out exactly what you want your 'buttons' to do, flowchart the whole thing.
I'm reading through this and your other threads over at Microchip, and your ideas are half-structured at best. You seem to be hoping that somebody will just come up with the magic code for you and it'll all be done.
Joe's code, a couple of posts above, is a good base for you to add onto. I think the end result that you desire is just as easy as what Joe has written up. Why not just try a few things here and there? Then, when things don't work as expected, post the code YOU wrote and the rest of us can help YOU figure out what YOU did wrong, rather than the other way around. As has been said here before, this isn't a 'drive-thru get your code' forum, although a few would be more than happy to write the code for you, I don't know of any.
After that, you might want to hit the books a little bit and do some reading on the SLEEP command for putting your PIC into SLEEP mode.

hey ski mask thanks.. Ill keep that in mind I been reading 2 books already so yup.. Ill try to get this code to work one question was if the same pin can read the low coming from the trigger and rapidfire on the same pin..

[Archangel]

I thought you were trying to duplicate the the other guys chip, with separate mode and trigger inputs. And in your subroutines you can tell it to do what you want including sleep, then you have to figure out how to reawaken it with . . . an interrupt ? It is why I said at the beginning, buy the other guy's chip and then work on your own too, he put a lot of effort into that including storing the on/off status in eprom. If you are as new as you appear, you are looking @ 2 years to success, a little less if you are young. That said, none of are getting any younger, so post the code you PMed me and let's have at it!

[Darrel Taylor]

First off, why not trying to type a bit slower or something, maybe add something like punctuation. Makes it just that much easier for the rest of us to read.
Second...You might want to try and write out exactly what you want your 'buttons' to do, flowchart the whole thing.
I'm reading through this and your other threads over at Microchip, and your ideas are half-structured at best. You seem to be hoping that somebody will just come up with the magic code for you and it'll all be done.

What's it going to take skimask?

People come here for help, and the purpose of this forum is to try to provide that.
Ridicule and belittling, are NOT part of the program.

If you have no help to offer, then you have no reason to post.
<br>

[skimask]

What's it going to take skimask?

People come here for help, and the purpose of this forum is to try to provide that.
Ridicule and belittling, are NOT part of the program.

If you have no help to offer, then you have no reason to post.
<br>

I think I've got a pretty good template for him to work from, complete and everything, never thought it was worth anything since I've seen the same type of thing all over the internet.
BUT, I'VE ALREADY BUILT A COUPLE OF THEM FOR A FRIEND AS A BIRTHDAY PRESENT ABOUT A YEAR AGO! NOT QUITE THE SAME, SINGLE-SHOT, 5 SHOT, CONTINUOUS, OFF, AND...NOT ONLY THAT, BUT EVENTUALLY, ONCE I SAW THAT THE GUY WAS ACTUALLY WORKING TOWARDS LEARNING HOW PBP WORKS, I WOULD HAVE UPLOADED THE WHOLE SHEBANG, THE WHOLE LOT, SCHEMATICs FOR THE NEW AND THE OLD CONTROLLER, PBP SOURCE CODE FOR THE 12F683, HEX FILEs, AND MAYBE, JUST MAYBE, SINCE IT'S THE HOLIDAY SEASON AND ALL, I MIGHT HAVE SENT THE GUY A FINISHED, PROGRAMMED PIC AND A FEW PICTURES OF THE FINISHED PRODUCT.

But, you know what...(and sorry there 'thm ov3rkill', but you've got DT to thank for this), skip it. Not gonna do it.

Go ban yourself for awhile! Better yet...Put it to another vote like you did last year.

But I will give the original poster a suggestion on the one question...

Ill try to get this code to work one question was if the same pin can read the low coming from the trigger and rapidfire on the same pin..

With some creative hardware, you might be able to get away with it. You could leave the pin floating, use one switch to pull it low thru a high value resistor, use the other switch to pull it high thru another high value resistor. There's an app note around somewhere that describes how to do that sort of thing.
Another option is to plug the switches into an A/D input and use a couple of resistors as a voltage divider. One switch pulls the input down to, say 1v, the other switch pulls the input down to 2v, both switches 3v, or something to that effect.
But since you've got unused pins, easier just to read two pins with one switch each, than read two switches on one pin.

[Darrel Taylor]

No vote required.

Thank you!

[Darrel Taylor]

Sorry bout that!

Maybe now, Joe can't get something accomplished here.

I'll help if I can too.
Might want to start a new thread though.
<br>

[Archangel]

Maybe now, Joe <font color=red>can't </font color>get something accomplished here.

Freudian slip, or are you telling me something here ?