Array index runs from 0 to size-1. So for int myArray[16] the indexing is 0 to 15! not 1 to 16.

So the for loop should look like

for (1=0;i<16;i++){
}

There is no bounds checking in c/c++ so you will not be given any warning if you try to read/write outside the bounds to the array.

Writing out side the array will over write other data with random results

Mark

Servos should not normally be powered from the arduino it's self (but you can get away with it for one micro servo and a small load). So yes you need a second power supply and of course a common ground.

Mark

But first use auto format to make it readable!. I for 1 will never download large files. Why not create a small sketch to show the problem you are having. Post the errors you are getting.

Mark

Well, the problem is not the "bounce".

How do you know this. Are you going to post you're latest code? Where is your circuit diagram?

Mark

You DO need a motor shield. Try using a servo instead!

Mark

"iswaked" should be declared volatile. All var's changed in an interrupt routine should be declared as volatile. But that's not your problem.

I think you button/switch is bouncing look at de-bouncing in the playground.

Mark

You can't do it. Names are gone by the time the code has been built.

Mark

Just don't see why!

Mark

What use would a prototype be at that point in the code?. I can't see a possible use and therefore would expect and error message.

Mark

What do you mean by 3 digits?

Mark

Even so it makes no sense at that point in the code!

@op DO NOT DELETE THIS THREAD

Mark

@mods, paulS, etc but why did the ops code build at all. You can't dec functions within functions and we where not within a class!

Mark

Use the lib or SoftwareSerial but not both!

Mark

While servicing and interrupt all other interrupts are disabled. If the routine takes to long this will cause problems. Some of the things which may have trouble due over long interrupt routines include serial, the servo lib, pwm.

Serial and delay can not be used in interrupt routines.

In general interrupt routines should be kept as short as possible. You cannot run other parts of a program in an interrupt routine instead you should set a flag in the interrupt routine and then check the state of the flag in loop().

Any var modified by an interrupt routine must be declared as volatile.

Mark

read up on using serial.

1. Most 99.9999% of the time x will be -1 the result of reading when there is no data.

2. If you type 1 in the serial monitor serial.read() will return 48(the vaule used to represent the char '1') and then 13(cr) and then 10 (LF) read up on ascii

Mark