Summary:
Currently the focus of troubleshooting errors in programming languages is via highlighting syntax errors (linting) in the software or IDE. However, as Artists and Designers there are wide conceptual reasons for using code resulting in the pushing of creative and programmable boundaries. As Functional Errors also include conceptual misunderstandings of what outputs will result from certain programming methods, it is important to explore how this can be fedback to users.
When considering physical computing, students may find a visual or kinetic output that differs from what they expect from their code. As their code is technically correct it will not feedback any compiler or runtime errors. Therefore, this shield explores an alternate pedagogical method of providing legible, immediate feedback regarding what the microcontroller is actually executing.
An example would be an LED that is intended to blink ON and OFF. The code compiles without error but the user has not considered the timing of the commands being executed. Therefore, the LED is executing the task but at a speed our eyes cannot interpret. This may *look like* a flickering or static light. Without the conceptual understanding of timing it may be difficult for a user to debug this error.
The aim of this Arduino Uno shield is to listen to input and output activity on the Uno pins and provide visual colour coded feedback based on the behaviour executed.
The shield consists of a second 'listener' microcontroller and a ring of LEDs.
Pin Guide :
The inputs and outputs from your Arduino can be interpreted as follows:
- Digital pin is HIGH a light will be green
- Digital pin is LOW a light will be red
- PWM pin is pulsing a light will be blue at the intensity and timing of that value
As such the example given above would be illustrated as a very fast flickering green LED, or static red LED signifying the message is being executed far faster than our eyes can interpret.
Should a user be accidentally sending a message out of a different pin to which a component is plugged into then this should also be evident via the number LED that is on or off in the ring.
See the pin guide card for indicators as to which LED corresponds to which pin. A few oporational things to note are:
- The shield requires its own battery power source and does not run off the main Arduino board (Uno/Leonardo).
- There is a black dot to indicate pin 2 and it goes up in LED number to the right (clockwise)
- Pin 3 is inactive as this drives the ring of LEDs.
- Pins 0 and 1 on the Uno are not visually represented on the Feedback Shield due to their common use in Serial communication.
