Documentation and pin mapping in Arduino - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to define the LED pin number.

Arduino

const int ledPin = [1];

Drag options to blanks, or click blank then click option'

AHIGH

BdigitalWrite

CINPUT

D13

Attempts:

3 left

💡 Hint

Common Mistakes

Using a function name instead of a pin number.

Using a constant like HIGH or INPUT instead of a pin number.

The LED is connected to pin 13, so we assign 13 to ledPin.

2fill in blank

medium

Complete the code to set the LED pin as an output in the setup function.

Arduino

void setup() {
  pinMode([1], OUTPUT);
}

Drag options to blanks, or click blank then click option'

AledPin

BINPUT

CdigitalWrite

DHIGH

Attempts:

3 left

💡 Hint

Common Mistakes

Using a constant like INPUT instead of the pin variable.

Using a function name instead of a pin number.

We use ledPin to refer to the pin number and set it as OUTPUT.

3fill in blank

hard

Fix the error in the code to turn the LED on.

Arduino

void loop() {
  digitalWrite([1], HIGH);
}

Drag options to blanks, or click blank then click option'

AledPin

BINPUT

CLOW

DpinMode

Attempts:

3 left

💡 Hint

Common Mistakes

Using INPUT or pinMode instead of the pin variable.

Using LOW instead of HIGH to turn the LED on.

We must use ledPin to specify which pin to set HIGH.

4fill in blank

hard

Fill both blanks to create a comment documenting the LED pin number.

Arduino

// [1] is connected to pin [2]

Drag options to blanks, or click blank then click option'

ALED

Bbutton

C13

D7

Attempts:

3 left

💡 Hint

Common Mistakes

Confusing the LED with the button.

Using the wrong pin number in the comment.

This comment explains that the LED is connected to pin 13.

5fill in blank

hard

Fill all three blanks to create a dictionary mapping pin names to pin numbers.

Arduino

const int pins[] = { [1], [2], [3] };

Drag options to blanks, or click blank then click option'

AledPin

BbuttonPin

C13

D7

Attempts:

3 left

💡 Hint

Common Mistakes

Using variable names instead of pin numbers.

Repeating the wrong pin numbers.

The array holds pin numbers 13, 7, and 13 for LED and button pins.

Practice

1. What is the main purpose of pin mapping in Arduino projects?

easy

A. To reduce the power consumption of the board

B. To increase the speed of the Arduino board

C. To give pins clear and meaningful names in the code

D. To change the physical location of pins on the board

Solution

1. Step 1: Understand what pin mapping means

   Pin mapping means assigning clear names to pins in your code to make it easier to understand.

2. Step 2: Identify the main purpose

   The main purpose is to make the code readable and easier to maintain by using meaningful names.

3. Final Answer:

   To give pins clear and meaningful names in the code -> Option C

4. Quick Check:

   Pin mapping = Clear pin names [OK]

Hint: Pin mapping means naming pins clearly in code [OK]

Common Mistakes:

• Thinking pin mapping changes hardware
• Confusing pin mapping with power settings
• Assuming pin mapping speeds up the board

2. Which of the following is the correct way to define a pin mapping in Arduino code?

easy

A. int ledPin = 13;

B. pinMode(13) = ledPin;

C. digitalWrite(ledPin, 13);

D. define ledPin 13;

Solution

1. Step 1: Review Arduino syntax for pin mapping

   Pin mapping is done by assigning a pin number to a variable, usually with int.

2. Step 2: Check each option

   int ledPin = 13; correctly assigns pin 13 to variable ledPin. Others have wrong syntax or order.

3. Final Answer:

   int ledPin = 13; -> Option A

4. Quick Check:

   Pin mapping syntax = int variable = pin number [OK]

Hint: Use 'int variable = pinNumber;' to map pins [OK]

Common Mistakes:

• Using pinMode incorrectly for mapping
• Trying to assign pinMode as a variable
• Using 'define' without # for constants

3. What will be the output on the serial monitor after running this Arduino code?

int sensorPin = A0;
void setup() {
  Serial.begin(9600);
}
void loop() {
  int value = analogRead(sensorPin);
  Serial.println(value);
  delay(1000);
}

medium

A. The text 'sensorPin' printed every second

B. A number between 0 and 1023 printed every second

C. An error because A0 cannot be used in analogRead

D. Nothing prints because Serial.begin is missing

Solution

1. Step 1: Understand the code behavior

   The code reads analog input from pin A0 and prints the value to the serial monitor every second.

2. Step 2: Analyze the output

   analogRead returns a value from 0 to 1023 based on voltage. Serial.println prints this number.

3. Final Answer:

   A number between 0 and 1023 printed every second -> Option B

4. Quick Check:

   analogRead(A0) = 0-1023 values [OK]

Hint: analogRead returns 0-1023 values from analog pins [OK]

Common Mistakes:

• Thinking analogRead returns pin name
• Assuming A0 is invalid for analogRead
• Forgetting Serial.begin disables output

4. Identify the error in this Arduino code snippet related to pin mapping and fix it:

const int ledPin;
void setup() {
  ledPin = 13;
  pinMode(ledPin, OUTPUT);
}

medium

A. ledPin must be declared as a variable, not const

B. pinMode should be called before assigning ledPin

C. No error, code is correct

D. ledPin should be assigned when declared, not in setup()

Solution

1. Step 1: Understand const variable rules in Arduino

   Constants must be assigned a value when declared and cannot be assigned later.

2. Step 2: Identify the error in code

   Code declares const int ledPin; without value, then assigns in setup(), which is invalid.

3. Final Answer:

   ledPin should be assigned when declared, not in setup() -> Option D

4. Quick Check:

   const variables need immediate assignment [OK]

Hint: Assign const variables when declaring them [OK]

Common Mistakes:

• Assigning const variables later in code
• Thinking pinMode order matters here
• Ignoring const keyword rules

5. You want to document your Arduino project with multiple sensors and LEDs. Which approach best improves code readability and maintenance?

hard

A. Use descriptive pin mapping variables and add comments explaining each connection

B. Use raw pin numbers directly in code without comments

C. Write all code in one function without separating setup and loop

D. Avoid comments to keep code clean and short

Solution

1. Step 1: Understand importance of documentation and pin mapping

   Descriptive variable names and comments help others and yourself understand the project connections.

2. Step 2: Evaluate each option

   Use descriptive pin mapping variables and add comments explaining each connection uses clear names and comments, which is best practice. Others reduce clarity and maintainability.

3. Final Answer:

   Use descriptive pin mapping variables and add comments explaining each connection -> Option A

4. Quick Check:

   Good documentation = clear names + comments [OK]

Hint: Name pins clearly and comment connections [OK]

Common Mistakes:

• Using raw pin numbers without explanation
• Skipping comments thinking code is self-explanatory
• Mixing all code in one function