Arduino Fundamentals: Part I: Quiz

rough, but finally got it

void setup() { }  /is only for assingments like i=0, or things that are run once ie. bitSet(TCCR1B, CS12);  // 256 prescaler  NEVER LOOPS!! unless you are Initalizing an arry buy I might just put the array in a .pde file and include it.

Since you're still posting this opinion after a year, I thought I'd offer a counter-opinion.

1. setup() is just a C++ function.  You can put any code you want inside it.  The statements inside of setup ARE "executable code", so your earlier emphasis ("NEVER put executable code in setup!" is just wrong.  Your examples all contain "executable code."  (loop() is just a C++ function too.  I interpret the current form of the question as checking whether the quiz-ee understands that they're just functions, not "magic names that do something special."
2. A statement like "Serial.println("Arduino sketch that does neat things!");" inside setup() is entirely appropriate.  And guess what?  It loops (down inside of Print, but still... looping is looping.)
3. It is a STANDARD RECOMMENDATION, when porting C code to Arduino, to "rename main() to setup() and leave loop() empty."  setup() behaves essentially similar to main() in a normal C program, except it happens after the core code sets up the chip for the Arduino environment.
4. For the example from the quiz "blink an LED 10 times" (or any "do X for a limited time" scenario), you wind up with three choices:   A) Put a loop in setup().  B) put loop inside of loop() and then have it stop.   C) torture and obfuscate code in loop to let it do the LED thing 10 (perhaps 20) times and then have it stop touching the LED.   All of these have advantages and disadvantages, at least stylistically.  None of them are going to fit well within the "best style for Arduino sketches" because the example is NOT a good example of a typical Arduino application...

void setup() {
  pinMode(13, OUTPUT);
  for (int i=0; i < 20; i++) { // 20 toggles == 10 flashes.  Check for fenceposts!
    digitalWrite(13, !digitalRead(13));
    delay(500);
  }
}
void loop() {}

void setup() {
  pinMode(13, OUTPUT);
}
void loop() {
  for (int i=0; i < 20; i++) {  // 20 toggles == 10 flashes.  Check for fenceposts!
    digitalWrite(13, !digitalRead(13));
    delay(500);
  }
  while (1) ;   // stop
}

void setup() {
 pinMode(13, OUTPUT);
}
int i = 0;   // global counter
void loop() {
 if (i < 20) {  // 20 toggles == 10 flashes.  Check for fenceposts!
    digitalWrite(13, !digitalRead(13));
    delay(500);
    i++;
  }
  // after 10 flashes, loop will do nothing.
}

(I should add that I dislike the third example, IF all you need to do is "flash the LED 10x."  However, it is the path that you'd need to go toward if you wanted to "flash the LED 10 times WHILE ALSO DOING SOMETHING ELSE.")

Question 24 (connect an LED on pin 13) - correct answer actually depends on the details of how the LED is connected.

It looks to me like question 3 has two correct answers.

Question 7  (delay(10000)) is poorly worded, IMO.  The "result" is a delay, not just "some number of seconds" (what happens to the new seconds?  Do they get added to the time till the heat death of the universe?  Or maybe to the lifetime of the programmer?)

I sort of felt that there were a bunch of questions here that tested things that an Arduino user doesn't really need to know.  (instruction pipeline!?)  I've always been a bit hesitant to take the "certification" test, even thought I'm theoretically an experienced C and AVR programmer (I did get 100% on THIS), since I was worried that it would veer away from general engineering into things that were closer to what Arduino users actually do (that I haven't done.)  Like "Multiple I2C sensors can be connected to the same i2C bus as a long as...", or "The following interfaces are commonly used to connect an LCD display to an Arduino..."

Also... very AVR-centric.  I guess that matches usage statistics, but...

Nice quiz to boost our knowledge.5 stars rating

I suspect, long before your gold sticker there was parental pride.

javagoza   Thanks!

~~Cris

For the banded lines:

1. Select the code to highlight
2. Then use de Insert button [>>] menu / Syntax Highlighting / c++

javagoza Enrique, this may sound dumb, but how do you get this stupid editor to give you the banded lines????

and you are quite right about the second form but I did not include it as I did not think they would get it.

in C there is no square primitive ie number² The easy way is with a define.

#define SQUARE(x)  ((x)*(x))

another good candidate is Pi

#define pi 3.14159265359

~~Cris

colporteur lol, mom and dad are going to be proud of me.

Thanks for the sticker and for your personal and detailed road tests.

Thanks for taking the time to prepare such a detailed write-up. It answered my question and then some. Like in school I felt you deserved a sticker for your efforts.