So, you are saying that we should not allow anyone to learn anything that could _possibly_ have a sinister application?
So, you are saying that we should not allow anyone to learn anything that could _possibly_ have a sinister application?
"I think fish is nice, but then I think that rain is wet, so who am I to judge?" - Douglas Adams
Hi Kamikaze,
The application is what you do with the thing ... Even simulating fighting ( stupid video games ... or ... ) could lead 'light minded" guys to do it for real in the real life.
Hunting is just supposed to bring you food ... not adrenaline peaks.
Quite everything in this world could have a sinister application.
we just should not help if knowing the final use leads to violence ...
but how to always know ???
Alain
************************************************** ***********************
Why insist on using 32 Bits when you're not even able to deal with the first 8 ones ??? ehhhhhh ...
************************************************** ***********************
IF there is the word "Problem" in your question ...
certainly the answer is " RTFM " or " RTFDataSheet " !!!
*****************************************
This is exactly my point ^^^.
I'm saying that we shouldn't withhold helping someone learn something just because it could possibly be used for a sinister application, because that would apply to almost everything.
I agree that we should not help if we _know_ that the final use is for violence, but certainly in this case, there is no reason for us to assume that that is true.
I guess I just assume the best in people unless I see evidence to the contrary. I definitely believe in innocent until proven guilty.
"I think fish is nice, but then I think that rain is wet, so who am I to judge?" - Douglas Adams
Hay there again, well after reading through the thread and at first feeling like i was accused of 911 myself :O and then reading peoples reactions it seems to of gone a bit far.
If i was said crazy crazy bomb bomb man i dont think i would bother with all this coding jargon. Maplins and RS and similar people (radio shack for you americans among us) proberly sell things that would be alot more reliable.
I'm an electronics apprentice and im trying to improve my background knowledge and find some intresting projects along the way. With any luck this will also be used towards my BTEC HNC at the end of next year.
Anyway back on topic and away from my dating agency advert^.
I'm going to give some of the proposed codes on here a try today and shall report back on findingsalthough i have neverused the timer commands on pics ive always used loops adding 1 to b1 and checking values etc.
Yes, unless you need really accurate timer, then the "add 1 to b1 and check value" sort of thing would be good enough for almost any project. I personally have only had timer experience with Mel's olympic timer and modified it somewhat to count either up or down, depending on another pin's level. I still haven't really nutted out the timer function or the interrupt bizzo, 'cos I figure I can simply use the modified Mel's timer for whatever I want. I don't think I really need to know EXACTLY why/how a PIC does what it does, I just need to know that it WILL do what it does. I have picked the timer and interrupt sections out of the original and simply use them when I need to. See?, plagerism is alive and well!!
Peter Moritz.
Up the bush, Western Plains,
New South Wales,
Australia.
Okay well after trying to get my head around this coding for several hours im going to have to ask for some help!
I ended up using the very very well written but advanced coding in the oylimpic timer. First of all i set up the programe running normally and checked that all options and modes etc were working fully.
I then started looking into making the programe count down instead of up so i set a value in the LCD display in the minutes and seconds incase it needed. (I dont know if there is a registry file which this info also needs to be placed into?)
I then looked at the coding and found the commands to change the seconds to 60 and minutes etc and change them to what i believe to be right:
' Timer Interrupt Handler
' =======================
TickCount:
Gosub SetTimer ' Set the Timer for next 10mS Interrupt
If RunningFlag=1 then ' If timing actually enabled... then...
Hundredths=Hundredths-1
' Increment 10mS Seconds Counter
If Hundredths<0 then
Hundredths=99
Seconds=Seconds-1
' Increment the Seconds
If Seconds<0 then
Seconds=59
Minutes=Minutes-1
' Increment the Minutes
If Minutes<0 then
Minutes=59
Hours=Hours-1
' Increment the Hours
If Hours>99 then
' Handle any Overflow
Hours=0
OverFlowError=1
Now im stuck. When i boot the programe up i get the time showing which ive set. I then start the timer and the tenth of seconds count down like i want them too! However it doesnt role over into the seconds.
Any help appreciated!
Write a chunk of code that does this...Now im stuck. When i boot the programe up i get the time showing which ive set. I then start the timer and the tenth of seconds count down like i want them too! However it doesnt role over into the seconds
Take a byte variable, assign a value of ZERO to it, subtract one from that value and display it. For example:
What's the result?Code:temp var byte temp = 0 temp = temp - 1 lcdout $fe , 1 , DEC temp
Is it what you expect?
Bookmarks