Skip to topic
    ← Back to course topics

    Electronic systems and programmable components — Eduqas GCSE Design and Technology

    Electronic systems and programmable components explained

    This topic covers the integration of electronic systems and programmable components into products, focusing on the systems approach (input, process, output), feedback mechanisms, and the use of programmable microcontrollers to enhance functionality.

    What to demonstrate

    1. Understanding of the systems approach: input, process, output.
    2. Ability to use graphical conventions: circuit diagrams, block diagrams, and flowcharts.
    3. Knowledge of input sensors (LDR, thermistor) and output devices (buzzer, LED).
    Show all 6 objectives
    1. Understanding the role of feedback in control systems.
    2. Knowledge of programmable microcontrollers (e.g., PIC) and their benefits/limitations.
    3. Understanding of sub-routines and macros in control systems.

    Electronic systems and programmable components exam tips

    Topic Overview

    Electronic systems and programmable components form a core part of the WJEC GCSE Design and Technology curriculum, bridging the gap between traditional electronics and modern computing. This topic explores how systems are built from inputs, processes, and outputs, and how microcontrollers (like the Arduino or PIC) can be programmed to control devices. Understanding this allows you to create smart products that respond to their environment, such as automatic lighting, alarm systems, or wearable tech.

    In the modern world, programmable components are everywhere—from washing machines to drones. By learning how to design and program these systems, you gain skills that are highly valued in engineering and product design. This topic also develops logical thinking and problem-solving, as you must break down a problem into a sequence of instructions. It connects closely with other areas of the specification, such as materials and manufacturing, because the electronic system must be integrated into a physical product.

    For your GCSE, you will need to understand block diagrams, flowcharts, and simple programming constructs (sequence, selection, iteration). You'll also learn about sensors (e.g., LDR, thermistor) and actuators (e.g., motor, buzzer), and how to choose appropriate components. The exam may ask you to analyse a given system, suggest improvements, or write a simple program. Mastering this topic can help you achieve higher marks in the 'design and make' task, where you can incorporate smart features into your prototype.

    Key Concepts
    • →Input-Process-Output (IPO) model: All electronic systems follow this structure. Inputs are sensors (e.g., light-dependent resistor), process is the microcontroller or logic circuit, and outputs are actuators (e.g., LED, motor).
    • →Microcontrollers: Programmable chips that can read inputs, make decisions, and control outputs. Common examples include Arduino, PIC, and BBC micro:bit. They are programmed using languages like C++ or block-based coding.
    • →Flowcharts and pseudocode: Used to plan the program logic. Key symbols: oval (start/end), parallelogram (input/output), rectangle (process), diamond (decision).
    • →Sensors and actuators: Sensors convert physical quantities (light, temperature, pressure) into electrical signals. Actuators convert electrical signals into physical actions (movement, sound, light).
    • →Programming constructs: Sequence (steps in order), selection (if-else statements), and iteration (loops like while or for). These allow the system to respond to different conditions.
    Marking Points
    • Understanding of the systems approach: input, process, output.
    • Ability to use graphical conventions: circuit diagrams, block diagrams, and flowcharts.
    • Knowledge of input sensors (LDR, thermistor) and output devices (buzzer, LED).
    • Understanding the role of feedback in control systems.
    • Knowledge of programmable microcontrollers (e.g., PIC) and their benefits/limitations.
    • Understanding of sub-routines and macros in control systems.
    Examiner Tips
    • 💡Practice drawing block diagrams for common everyday products.
    • 💡Ensure you can clearly distinguish between analogue and digital sensors.
    • 💡Be prepared to explain how a system would respond to a change in input (e.g., light level or temperature).
    • 💡Use correct terminology for electronic components and control devices.
    • 💡Always draw a clear block diagram for any system you design. Label inputs, process, and outputs. This shows the examiner you understand the system structure and can earn you easy marks.
    • 💡When writing a program or flowchart, use meaningful variable names (e.g., 'temperature' not 'x') and add comments. This demonstrates good practice and makes your code easier to mark.
    • 💡In the exam, if asked to 'evaluate' a system, consider reliability, cost, ease of programming, and suitability for the user. Don't just describe it—give a balanced judgement.
    Common Mistakes
    • Confusing the roles of input, process, and output components.
    • Failing to correctly identify or draw appropriate circuit/block diagrams.
    • Misunderstanding the purpose of feedback within a control system.
    • Inability to explain the benefits of using programmable microcontrollers over fixed logic circuits.
    • Misconception: 'A microcontroller is the same as a microprocessor.' Correction: A microcontroller includes a processor, memory, and input/output peripherals on a single chip, making it a complete system. A microprocessor only contains the CPU and requires external components.
    • Misconception: 'All sensors output a digital signal.' Correction: Many sensors (e.g., thermistor, LDR) output an analogue voltage that must be converted to digital using an ADC (analogue-to-digital converter) inside the microcontroller.
    • Misconception: 'If the program works in simulation, it will work in real life.' Correction: Real-world factors like power supply stability, component tolerances, and noise can cause issues. Always test the physical circuit.
    Frequently Asked Questions
    What is the difference between an Arduino and a Raspberry Pi?
    An Arduino is a microcontroller board designed for simple, real-time control tasks like reading sensors and turning on LEDs. It runs one program at a time and is ideal for electronic projects. A Raspberry Pi is a single-board computer that runs a full operating system (like Linux) and can multitask, handle complex calculations, and connect to the internet. For GCSE projects, an Arduino is usually simpler and more suitable for basic programmable systems.
    How do I choose the right sensor for my project?
    First, identify what physical quantity you need to measure (e.g., light, temperature, distance). Then consider the sensor's range, accuracy, output type (analogue or digital), and cost. For example, an LDR is cheap and good for detecting light levels, but a photodiode is more accurate. Also check if the sensor works with your microcontroller's voltage (usually 5V or 3.3V). Finally, think about the environment—if it's outdoors, you may need a waterproof sensor.
    What is a flowchart and why do I need it?
    A flowchart is a visual diagram that shows the steps and decisions in a program. It uses standard symbols: ovals for start/end, parallelograms for input/output, rectangles for processes, and diamonds for decisions. You need it to plan your program logic before coding, which helps avoid errors and makes it easier to explain your design to others. In exams, you may be asked to draw or interpret a flowchart.
    How do I program a microcontroller?
    You write code on a computer using an IDE (Integrated Development Environment) like the Arduino IDE. The code is written in a language similar to C++. You then connect the microcontroller to your computer via USB and upload the program. The microcontroller stores the program in its memory and runs it when powered. Common commands include pinMode(), digitalWrite(), analogRead(), and delay().
    What is a 'pull-up resistor' and when do I need one?
    A pull-up resistor is a resistor connected between a signal pin and a positive voltage (e.g., 5V) to ensure the pin reads a high logic level when no input is present. It is often used with switches or open-collector outputs to prevent the pin from 'floating' (unpredictable state). For example, when using a push button, a pull-up resistor keeps the input high until the button is pressed, which pulls it low. Many microcontrollers have internal pull-up resistors that can be enabled in software.
    Can I use a microcontroller without knowing how to code?
    Yes, you can use block-based programming environments like Scratch for micro:bit or Ardublock for Arduino. These allow you to drag and drop blocks to create programs. However, for the GCSE exam, you will need to understand basic coding concepts (sequence, selection, iteration) and be able to read simple code. Learning to code gives you more control and flexibility in your projects.