Test your Knowledge of Arduino Fundamentals: Part I: Quiz

So how does one create a quiz like this, anyway?

knob? what kind of I/O device is it?
Great quiz!

couple of those questions skunked me :-)

tough one

Thanks!

Csak megvan56%.De ez itt mi:

Jaj nem egészen teljesítetted az évfolyamot.

Something like this make us dig deeper into concepts which we never know even when we do projects on arduino, so its a great idea to keep these kind of quiz to gain knowledge.

WestfW Bill this is a never-ending story! I know that setup is a function in C++ but I still disagree.

let say you want to initialize an array[] = {{........ll.}, {.....}...............} is fine.

when I set my IO pins to names  I do it with #defines as it makes life easier and this is in its own file. that is included before the setup().

saying this you could make your assignments with a loop ie..   for ( int i = 22;  i < 40;  i++ ) {

if ( i > 30 ) { set pinMode (i, OUTPUT); }

else {

set pinMode (i, INPUT); }

now about loop(), main(0, init() personly I set up my code like blocks one sits on the other. so this is what I do:

//each function  has  a assoceated .h file and some times 2 as some may be public, and some private.

#include main.h // this has a lot of things the main() needs

#include inti.h // most of stuff that the init needs

int main ( argc, argv) {

    init() // this is atken to setup

    setup() { the Radio Sub Stystem in my Sim, init and setup are very diferant animials. }  

   do {

} while(  sometihg is true);

~~Cris

BTW Modularize your code. easier to read.

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.")