Microcontroller Compete Course

Page 2
Welcome to the course!

The course contains a series of programming exercises, (part 1) supported by background
information for reference, (parts 2 to 6).
Part 1 - Programming Exercises - p.4

Part 2 - Using E-Blocks - p.29
Part 3 - Introduction to Flowcode 7 - p.37
Part 4 - Flowcode 7 - Your first program - p.48
Part 5 - Flowcode 7 - Worked Examples - p.55
Part 6 - Introduction to Microcontrollers - p.84
Part 7 - Course Rationale - p.106
Your route through it:

Broadly speaking, there are two types of student:
The experienced programmer:

probably begins with the ‘Programming Exercises’, (part 1), referring back to the information in
the other sections, as and when needed.
After all, programmers only read the manual when they get stuck!
Nevertheless, before starting an exercise, you should familiarise yourself with the reference
section(s) so that you know where to look for help should you get stuck!
The less confident user:

concentrates first on the reference material and the worked examples and then attempts the
exercises.
Copyright © 2016 Matrix Technology Solutions Limited www.matrixtsl.com

Page 3
Before you start:

‘Flowcode 7’ works with a range of microcontrollers, including PIC, Arduino and ARM. For
simplicity, this course focuses on PIC microcontrollers. It also includes information for the Arduino
user.
‘Flowcode 7’ itself is microcontroller neutral - it presents virtually the same user interface
regardless of the microcontroller used. The differences are in the hardware and the way the
program is downloaded and tested.
For PIC users, most of the exercises use the E-blocks EB006 v9 Multiprogrammer and the EB083
Combo board. These are shown in the following images.
Arduino users need an Arduino Uno and E-blocks Arduino Uno Shield (EB093), shown below, as
well as the Combo board.
For more information:

On the Matrix website, www.matrixtsl.com, in the ‘Products’ menu:
click on ‘Flowcode’ - open the ‘Support Resources’ menu and access:
 ‘Flowcode 7’ - Getting Started Guide;
 ‘Flowcode 7’ Wiki;
 a range of ‘Flowcode 7’ examples.
click on ‘E-blocks’ - access the ‘E-blocks User Guide’;
open the ‘Boards’ menu and click on any E-blocks board to locate its
datasheet, under the ‘Resources’ tab.
search for ‘Arduino’ - access the ‘Flowcode Arduino Beginners Guide’ under ‘Resources’.
search for ‘HPACT (the Actuator training panel)
- under the ‘Resources’ tab, access the ‘Actuators panel worksheets’.

Page 4
Part 1
Programming Exercises

Page 5
Part 1 Contents
The hardware: ............................................................................................................................................. 7
Hardware jumper settings: ......................................................................................................................... 7
Flowcode 7 and download settings: ........................................................................................................... 7
Exercise 1 - Creating Outputs ..................................................................................................................... 8
Exercise 2 - Using Delays............................................................................................................................. 9
Exercise 3 - Using Connection Points ........................................................................................................ 10
Exercise 4 - Performing Calculations ........................................................................................................ 11
Exercise 5 - Using Loops............................................................................................................................ 12
Exercise 6 - Inputting Data ........................................................................................................................ 14
Exercise 7 - Making Decisions ................................................................................................................... 15
Exercise 8 - Programming LCDs ................................................................................................................ 17
Exercise 9 - Using the Keypad ................................................................................................................... 19
Exercise 10 - Analogue Inputs and the EEPROM ...................................................................................... 21
Exercise 11 - Using Software Macros ........................................................................................................ 23
Exercise 12 - Using External Interrupts ..................................................................................................... 24
Exercise 13 - Using Timer Interrupts......................................................................................................... 26
Additional Challenges: .............................................................................................................................. 28

Page 6
Programming Exercises for you to try:

The aim of the exercises is to develop experience in using ‘Flowcode 7’ and, in the process, develop
understanding of the programming terminology and techniques it embraces.
At all stages, further experimentation is always to be encouraged. “What happens if…” is the best
way to learn!
Experienced programmers may wish to start the course here and use the reference material as and
when needed.
Most exercises assume that the programmer is using a PIC microcontroller though they are equally
applicable to other microcontrollers. The next page describes the hardware and settings used in
these exercises. Occasionally, they may differ from this standard, in which case the details are con-
tained in the instructions for the exercise.
For some exercises, it is sufficient to test programs by simulating them on ‘Flowcode 7’.
Others should be downloaded to a microcontroller and tested on hardware.
The instructions make the recommended option clear.
The section ends with some challenges. These are fairly open-ended and contain only a brief speci-
fication.
Part 2 contains information about using E-Blocks to create and test control systems.

Page 7
The hardware:
Most exercises use the EB006 Multiprogrammer and EB083 Combo board, shown below.
(They can be supplied together as HP4832 - E-Blocks Development Board.)
The tables list the hardware and software settings used to test most programs.
Any changes to these are indicated in the instructions for the exercise.
Hardware jumper settings:
EB006
Jumper settings
version 9
PIC device 16F1937
Target voltage 5V J15
Voltage source PSU J11
Programming Source USB J12,13,14: USB
Oscillator Selector OSC J18,19
Port A E-block E-blocks Combo board
Port B E-block EB083
Port C E-block
Port D E-block
Port E E-block
Flowcode 7 and download settings:

Menu Name Setting
Build > Project Options... > Choose a Target Family - PIC 16F1937
Clock speed (Hz) 19 660 800
Build > Project Options... > General Options
Simulation speed Normal
Oscillator HS Oscillator
Build > Project Options... > Configure
Watchdog Timer Enable bit Disabled

Exercise 1 Page 8
Creating Outputs
This exercise configures ‘Flowcode 7’ to output specific digital signals to the LED array.
Objectives:
 to send different 8-bit codes to port B of the microcontroller;
 to change the logic level of a one single pin of port B;
 to configure an output icon;
 to use binary code;
 to manipulate logic output levels;
 to use LEDs to display an output;
 to compile a program to a microcontroller.
Relevant course content:
 Part 6 - ‘Introduction to microcontrollers’;
 Part 2 - ‘Using E-blocks’;
 Adding digital outputs - “Light the LED”;
 Flowcode Wiki - ‘Using masks’;
Instructions
Program 1:
 create ‘Flowcode 7’ flowcharts that:
 add a single output icon, configured to light all port B LEDs and run the simulation;
 then alter the parameters to light only the odd-numbered LEDs and run the simulation;
 do the same but for only the even-numbered LEDs;
 finally do the same but for only the high ‘nibble’ bits (4 to 7) of port B.
 modify this program by:
 repeating these four steps using hexadecimal rather than decimal numbering;
 lighting only the LED on bit 7, by sending an 8-bit value to the port;
 lighting only the LED on bit 7, using the 'single bit' output method;
 lighting only the LED on bit 7, using the 'masking' output method.
Program 2:
 write a program that uses at least twenty outputs icons to write different values to port B, one
after the other:
 use all four methods in this exercise - hexadecimal, decimal, single bit and masking;
 simulate the program and review the results;
 save the program and download it to the microcontroller;
 restart the program a number of times by pressing the Reset button on the multipro-
grammer board.

Exercise 2 Page 9
Using Delays
Introduction:
In this exercise, you learn how delays are used to slow down program execution. Microcontrollers
work extremely quickly - a PIC can execute about 5,000,000 assembly instructions, every second.
A human can detect and understand only around three stable images per second.
To allow a high-speed microcontroller to communicate with ‘slow’ humans, we sometimes need to
slow it down by adding Delay instructions.
Objectives:
 to add a delay to slow down execution of a program;
 to change the delay interval;
 to configure a delay icon;
 to control the speed of a microcontroller;
 to use an oscilloscope to time events .
 Flowcode Wiki - ‘Loop icon properties’;
Instructions
Program 1:
 open the program created in the last exercise (Exercise 1, Program 2):
 add Delay icons and configure them so that the output states can be viewed comfortably
even at ‘HS oscillator’ speed;
 save the program and download it to the microcontroller;
 test the program on the E-blocks boards;
 modify the length of the delays caused by the Delay icons:
 start with a delay of 1s;
 progressively reduce the delay until it is too fast for your eyes to detect the differ-
ent outputs states;
 download the program to the microcontroller every time and test it on E-blocks.
 use an oscilloscope to measure the delays you set up in ‘Flowcode 7’;
 make a detailed drawing of the oscilloscope image, complete with voltage and tim-
ing information and the delay time used in the ‘Flowcode 7’ program.
Hint:
Do not test this in simulation mode - simulation timing is not always accurate because it runs under a
Windows operating system and not in ‘real time’;

Exercise 3 Page 10
Using Connection Points
Introduction:
A Connection Point, or ‘goto’ instruction, is often used to create an infinite loop - to repeat a set of instruc-
tions over and over again. (A better way to do this is to use a ‘Loop’ instruction.) The advantage of a Con-
nection Point is that it can be used jump out of a loop to a certain location in the program.
The idea of pulse-width modulation (PWM) is introduced as a means of controlling LED brightness.
Objectives:
 to use Connection Points to introduce unconditional branching in a program;
 to introduce PWM as a means of controlling the brightness of LEDs.
 to create an infinite loop;
 Flowcode Wiki - ‘Connection point icon properties’;
Instructions
Program 1:
 create a flowchart that uses Delay, Output and Connection Point icons to light the even and odd LEDs of
port B, alternately on and off, with a 300ms interval between, in an infinite loop;
 test the program at first ‘step-by-step’ and then continuously in the ‘Flowcode 7’ simulator.;
 use Delay, Output and Connection Point icons to flash the high nibble and low nibble LEDs of port B al-
ternately on and off, with a 300ms interval between, in an infinite loop;
 download the program to the microcontroller and test it.
 use Delay and Output icons to flash all the LEDs of port B on and off with a 500ms interval in between,
in an infinite loop;
Hint:
Make the delays in these program very short and make the on and off times asymmetrical,
(e.g. on for 8ms and off for 12ms).
You have just designed a software PWM generator. (Search for ‘PWM’ on the internet for more infor-
mation.) When you run it, the intensity of the LEDs is lower. They flash on and off too fast for our eyes to
observe. Instead, we see the intensity change.
 modify program 1 by changing the ‘on’ and ‘off’ times in such a way that the total (‘on’ + ‘off’) time is
unchanged, e.g. on for 12ms and off for 8ms;
 download the program to the microcontroller and test it - what is the difference?
Program 2:
 write a program that:
 lights LEDs on the four most-significant bits, (MSB,) of port B and keeps them on;
 dims the intensity of the LEDs on the four least-significant bits, (LSB,) of port B, compared to the
four MSB LEDs, using PWM;
 use an oscilloscope to examine the signal controlling one of the four LSB LEDs;
 make a detailed drawing of the oscilloscope image, complete with voltage and timing information and
the on and off times used in the ‘Flowcode 7’ program.

Exercise 4 Page 11
Performing Calculations
Introduction:
Modern microcontrollers, like the PIC, are able to do simple mathematical tasks with 8-bit num-
bers at very high speed. As the calculations get more complex or the numbers rise above an 8-bit
value, then the execution time lengthens dramatically. ‘Flowcode 7’ allows complex calculations
using up to 16-bit numbers and takes care of all the complexities. However, these may slow down
execution of the program.
Objectives:
 to create and use a variable;
 to configure a calculation icon to perform arithmetic and logic calculations.
 to create and manipulate variables;
 to perform calculations;
 to use LEDs with current limiting resistors;
 Variables - ‘Example 1. Adding digital inputs - Where's the fire?’
 Flowcode Wiki - ‘Creating variables’;
 Digital inputs -‘Example 1. Adding digital inputs - Where's the fire?’;
 Flowcode Wiki - ‘Calculation icon properties’;
Instructions
Program 1:
 create a flowchart that:
 uses a variable called ‘counter’ containing an initial value of ‘1’;
 displays the value stored in the variable ‘counter’ on LEDs.
 simulate the program to test that it works.
 modify Program 1 by:
 adding a Calculation icon to double the value stored in the variable ‘counter’;
 displaying this new value on LEDs.
 using an infinite loop to repeat these steps continuously with a 300ms delay between
them. What do you see? (This is called a ‘running light’.)
 replacing the 'multiply by 2' with 'counter = counter + 1'.
What do you see now? (You just programmed a binary counter.)
Program 2:
 modify Program 1 to display the result of the following calculations on the LEDs of port B:
 45 + 52;
 45 AND 52;
 45 OR 52;
 NOT 45;
 (1+3)*(6/2);
 VAR2 = VAR1 * 3 (where variable ‘VAR1’ stores the number 18).
On paper, check if the results are correct.

Exercise 5 Page 12
Using Loops
Introduction:
Repeating a set of instructions, for an exact number of times, while or until a condition is met is
one of the most powerful programming operations.
The programs are now getting more interesting but also more complex. Use the slow simulation or
'Step Over' function in the ‘Flowcode 7’ simulator to debug programs from now on.
Objectives:
 to create and use a ‘running light’ program, using the ‘multiply-by-two’ method;
 to create and use a ‘running light’ program, using the ‘shift-right’ method;
 to create and populate an array;
 to create a conditional loop;
 Flowcode Wiki - ‘Loop icon properties’;
 LCD - ‘Exercise 8 - Programming LCDs’
 Flowcode Wiki - ‘Creating variables’;
Instructions
Program 1:
 write a program to make an 8-bit binary counter, using a Loop icon, to count from 0 to 255,
then reset and repeat the count;
 display the counter value on the LEDs of port B.
 modify Program 1 to make the counter count up from 0 to 255 and then count back down to
‘0’:
 using two loops inside an infinite loop so that the process repeats indefinitely;
 displaying the counter value on the LEDs of port B.
 download the program to the microcontroller and test it at full speed.
Program 2:
Remember KITT From Knight Rider or the Cylon robots from Battlestar Galactica?.
 write a program to make a simple ‘running light’ that runs from port B, bit 0 to port B bit 7 and
then back to port B bit 0, repeatedly:
 using the ‘multiply-by-two’ method;
 displaying the output on the LEDs of port B.

Exercise 5 Page 13
Using Loops
Program 3:
 make a simple ‘running light’ that runs from port B, bit 0 to port B bit 7 and then back to port B
bit 0, repeatedly:
 using the ‘shift right’ method;
 displaying the output on the LEDs of port B.
 modify program 3 to create a 16-bit running light, using the LEDs at both port A and B.
 use only loops - no decisions!
 save this program, download it to the microcontroller and test it.
Program 4:
 create a flowchart that:
 contains an array of four variables, called ‘Matrix[x]’ which stores the following values:
 Matrix[0] =129;
 Matrix[1] =66;
 Matrix[2] =36;
 Matrix[3] =24;
 uses two ‘do-while’ loops to create an infinite sequence:
 Matrix[0]-Matrix[1]-Matrix[2]-Matrix[3]-Matrix[2]-Matrix[1]-Matrix[0]-Matrix[1]-
..... ;
 refers to the four variables as ‘Matrix[x]’ where ‘x’ is a separate variable, known as the
index of the array;
 displays the output on the LEDs of port B.

Exercise 6 Page 14
Inputting Data
Introduction:
Adding digital inputs to a microcontroller circuit is quite easy but is a big step forward. This allows
external signals to influence how the program reacts.
Objectives:
 to input data from switches;
 to use loops to create LED sequences;
 to configure an input icon;
Instructions
Program 1:
 write a program to show the status of the switches connected to port A, on the LEDs connected
to port B i.e. when a switch is pressed, the corresponding LED on port B lights;
 modify the program so that:
 the corresponding LED on port B stays lit for 2s;
 during this time, no new inputs should be read;
 modify the program again so that:
 when switch ‘0’ is pressed, ‘LB1’ lights;
 when switch ‘1’ is pressed, ‘LB2’ lights, and so on;
 when switch ‘7’ is pressed, nothing happens;
Program 2:
 write a program to create a counter that:
 contains two loops;
 counts up when switch ‘0’ is pressed;
 counts down when switch ‘1’ is pressed;
 displays the count on the LEDs of port B;
Program 3:
 write a ‘running light’ program that:
 contains two loops;
 causes the LEDs to ‘run’ left when switch ‘0’ is pressed;
 causes the LEDs to ‘run’ right when switch ‘1’ is pressed;
 displays the count on the LEDs of port B;

Exercise 7 Page 15
Making Decisions
Introduction:
Earlier programs included simple decision-making, using loops and connection points. Now we look
in detail at the Decision icon, widely known as the ‘if…then…else’ structure, probably the most
widely used command line in any program.
Objectives:
 to configure Decision icons and hence add conditional branching to a program;
 to control the frequency at which LEDs flash;
 to use LEDs to display output logic levels;
 to use temporary memory;
 Flowcode Wiki - ‘Decision icon properties’;
Instructions
Program 1:
 write a program that uses switches to produce a reversed sequence on the LEDs:
and so on…
Program 2:
 write a program that creates an 8-bit counter, counting from ‘0’ to ‘255’ and then back to ‘0’
repeatedly:
 using Decision icons instead of Loop icons.
 using two switches connected to port B, bits 0 and 1;
 counting up when switch ‘0’ is pressed;
 counting down when switch ‘1’ is pressed;
 displays the current count on the LEDs connected to port A;
Program 3:
 write a program that counts from ‘0’ to a value stored in a variable called ‘count’ when switch
‘0’ is pressed and then waits until switch ‘1’ is pressed before counting down to ‘0’:
 using two switches connected to port B, bits 0 and 1;
 displaying the current value of the count on the LEDs on port A;
Program 4:
 write a program that makes all eight LEDs on port B flash on and off at a frequency of 1Hz, i.e.
taking one second for an ‘on-and-off’ cycle. In addition:
 the LEDs flash faster if switch ‘0’ is pressed;
 they flash more slowly if switch ‘1’ is pressed;

Exercise 7 Page 16
Making Decisions
Program 5:
 write a program that makes all eight LEDs on port B light when switch ‘0’ is pressed the first
time and go off when it is pressed again;
Program 6:
 A car has two interior lights, one in the front of the car, the second in the rear. These will be
simulated using LEDs.
 Five switches control them:
 switches ‘0’ to ‘3’ represent door switches that indicate if a door is open or not;
 switch’4’ indicates that the boot (trunk) is open or not.
Assuming that the switches are closed when the doors are open - easier to simulate with ‘push-
to-make’ switches, write a program that:
 lights both LEDs when any door opens;
 lights only the ‘rear’ LED when the boot is opened;
Program 7:
 write a program to control the car’s external lights, using switches on the steering wheel:
 switch ‘0’ controls the left direction-indicator (represented by ‘LB0’), which flashes on for
250ms and then off for 250ms repeatedly until switch ‘0’ is released;
 switch ‘1’ controls the right direction-indicator (‘LB1’) in the same way;
 switch ‘2’ controls the brake lights (‘LB2’ and ‘LB3’), which light up as long as the switch is
pressed;
 switch ‘3’ controls the head lights (‘LB4’ and ‘LB5’), which light when the switch is pressed
and stay on until it is pressed again;
 switch ‘4’ controls the fog lights (‘LB6’ and ‘LB7’), in the same way;
Hint: Don’t attempt to write this program all at once - divide it into subsections and solve each sep-
arately before putting them all together.
To make it easier, use the labelling feature of ‘Flowcode 7’ to label switches and LEDs.
Program 8:
Six sheep are allowed to wander between two paddocks. Be-
tween the two paddocks, there are two sensors.
Two are needed because sometimes a sheep triggers one sen-
sor and then turns back.
 write a program that counts and displays the number of
sheep in each paddock:
 the results are shown in binary form on the LEDs of
port B;
 the four LSB LEDs show the number in the left-hand paddock;
 the four MSB LEDs show the number in the right-hand paddock;
 when switch ‘0’ is pressed, it represents a sheep triggering Sensor 1;
 when switch ‘1’ is pressed, it represents a sheep triggering Sensor 2;
(A sheep is longer than the gap between the sensors!)

Exercise 8 Page 17
Programming LCDs
Introduction:
Using LEDs to display outputs limits them to numbers only and in binary code at that!
The LCD is a much better way to display data, both letters and numbers, for ‘non binary’ humans.
Objectives:
 to create, populate and manipulate string variables;
 to control the display of text and numbers on a LCD;
 to use a LCD as an output device for the microcontroller;
 to configure a Component macro for the LCD;
 Flowcode Wiki - ‘String manipulation functions’;
Instructions
Program 1:
 write a program that displays the text “Hello World” in the centre of the bottom line of the
2x16 LCD display.
Program 2:
 write a program, using either Loops or Decisions, that:
 counts up while switch ‘0’ is pressed;
 counts down while switch ‘1’ is pressed;
 shows the current count in binary on LEDs attached to port B;
 shows the count in decimal on the LCD.
Program 3:
 write a program to show the status of the switches attached to port A, so that every time a
switch or switches is/are pressed, the corresponding LED(s) of port B light(s) and the decimal
equivalent is displayed on the LCD.
Program 4:
 write a program to show the status of the switches attached to port A on the LED(s) of port B
and on the top line of the LCD and then:
 multiply this binary number by 100;
display the result on the bottom line of the LCD, with “[x 100 = ]” displayed in front of it;
Program 5:
 write a program that displays the text “[R15=560 ” in the centre of the bottom line of the LCD
display, using the ‘PrintASCII’ command to print the ‘ ’ sign:

Exercise 8 Page 18
Programming LCDs
Program 6:
 write a program that scrolls the lines of text given below, one line at a time:
 initially, the text is centred on the bottom line of the display for 2s;
 then it moves up to be centred on the top line for 2s, to be replaced on the bottom line by the
next line of text, and so on;
 Text:
 “There are only”;
 ”10 kinds”;
 ”of people !”;
 “Those who”;
 “understand”;
 “BINARY”;
 “and those who”;
 “DON’T….”.
 enclose the program in an infinite loop;
Program 7:
 uses the string manipulation icon to load a string variable called ‘MyStrA[20]’ with the text
“Hello”;
 displays this string variableon the LCD using the ‘PrintString’ command with the parameter
‘MyStrA’ (without the ‘[]’].
Program 8:
 loads a string variable called ‘MyStrA[20]’ with the text “Hello”;
 loads a second string variable called ‘MyStrB[20]’ with the text “Matrix”;
 displays “Hello Matrix” on the LCD using simple string manipulation.
 modify program 8 so that, using the same string variables with the same content, the LCD displays the
message “HELLO MATRIX” using simple string manipulation.
Program 9:
 displays “ello MATRIX=13” on the LCD using a range of string manipulations.
Hint: Find out how to display string length using string manipulation. The number changes automatically
when the length of the string changes.
Program 10:
 displays the message “xirtaM olleH” on the LCD.
Program 11:
 modify the sheep counter program from the last exercise to display the numbers of sheep in the two
paddocks on the LCD. (You decide the format of the display!)

Exercise 9 Page 19
Using the Keypad
Introduction:
A numeric keypad is used in many electronic devices, your mobile ‘phone, for example, where it is
used both as a numeric keypad and as a way to type text instead of numbers.
An issue- there are twelve buttons on the keypad, yet the keypad is connected to the microcontrol-
ler by only eight lines! This problem is solved by using multiplexing.
Objectives:
 to input text and numbers from a keypad and display messages on the LCD;
 to use ASCII code to transmit this data;
 to use multiplexed inputs;
 to configure a Component macro for the keypad;
Instructions
Program 1:
 write a program to:
 display, on the LCD, the number that is pressed on the keypad;
 display it for as long as the button on the keypad is pressed;
 display only one number at a time;
 re-write this program without using the Keypad Component macro:
 extend this program to:
 display, one after another on the top row of the LCD, numbers that are pressed on the
keypad;
 use the character ‘*’ for a space;
 clear the display when ‘#’ is pressed;
 display a maximum of fifteen characters;
 display a warning on the bottom row of the LCD when this maximum is exceeded;

Exercise 9 Page 20
Using the Keypad
Program 2:
 add together two numbers, less than ‘9999’, entered via the keypad;
 display the two numbers, the ‘+’ and ‘=’ and the resulting sum on the top row of the LCD;
 display a warning on the bottom row when ‘9999’ limit is exceeded;
Program 3:
 write a program for a simple guessing game, where:
 a player needs to guess a number between ‘0’ and ‘9’;
 the secret number is pre-programmed into the microcontroller;
 the LCD displays, on the top row, the latest guess entered via the keypad;
 the LCD displays a message, on the bottom row, indicating whether the guess is too high
or too low;
 extend this program so that:
 the secret number is in the range ‘0’ to ‘255’;
 extend the program again so that:
 the secret number is in the range ‘0’ to ‘9999’;
Program 4:
 write a program to use the keypad, as on a mobile phone, to input text to the microcontroller:
 using ASCII code to transmit the data;
 using the character ‘*’ for a space;
 clearing the display when ‘#’ is pressed;
 displaying a message on the bottom row when the text has more than ten characters;

Exercise 10 Page 21
Analogue Inputs and the EEPROM
Introduction:
The 16F1937 PIC Microcontroller accepts fourteen separate analogue inputs. Newer devices have
even more. An analogue signal on one of these inputs can be translated into a 10-bit digital binary
number. We can choose to use only the eight most-significant-bits of this 10-bit number or to use
the full 10-bit number. Be aware that working with 10-bit numbers in an 8-bit microcontroller like
the PIC, needs careful program writing!
Objectives:
 to create data loggers, using 8-bit and 10-bit data from the ADC;
 to configure an analogue input;
 to enter data via switches;
 to enter information from light and temperature sensors;
 to configure and use the EEPROM;
 to scroll through EEPROM data;
 to display text and numerical data on the LCD;
 to use the E-blocks prototype board.
Instructions
Program 1:
 display, on the LCD, an 8-bit number equivalent to the analogue input voltage from the
light sensor on the Sensor board;
 save the program, download it to the microcontroller and test it. (Connect a voltmeter to meas-
ure the analogue input voltage.)
Program 2:
 modify program 1 to:
 display data from the ‘pot’ on the Sensor board;
 save the program, download it to the microcontroller and test it,as before.
 modify this program to:
 convert the ADC 8-bit output into a voltage reading between 0 and 5V, making it as accu-
rate as the 8-bit mode allows;
 save the program, download it to the microcontroller and test it, using a voltmeter to measure
the analogue input voltage, once more.

Exercise 10 Page 22
Analogue Inputs and the EEPROM
Program 3:
 modify program 2 to:
 display, on the LCD, a 10-bit number equivalent to the analogue input voltage from the
‘pot’ on the Sensor board;
 then modify this program to:
 convert the ADC 10-bit output into a voltage reading between 0 and 5V, making it as ac-
curate as the 10-bit mode allows;
Program 4:
 write a program to monitor the lighting in a room over a 24 hour period:
 using the analogue signal from the light sensor on the Sensor board;
 storing light measurements on the EEPROM;
 sampling at the highest rate possible, given that the PIC has 256 bytes of EEPROM
memory on board
 and displaying each sample with its sample number, on the LCD;
 by scrolling forwards through the samples by pressing switch ‘0’, or scrolling backwards
by pressing switch ‘1’;
 save the program, download it to the microcontroller and test it.
Hint: Increase sampling rate so that you don’t have to spend 24 hours in testing.
Program 5:
 connect the Prototype board to port E and modify program 4 to develop a 10-bit accurate
temperature display unit that:
 monitors room temperature every 20 minutes over a 24 hour period;
 resembles the logger developed for room lighting, except that this one stores 10-bit data
in an 8-bit wide EEPROM;
 keeps a LED flashing to indicate that the system is still logging;
 lights all LEDs after 24 hours to indicate that logging is completed;
 allows you to scroll through the results using switches ‘0’ and ‘1’ as before;
 displays the temperature and its EEPROM address on the LCD.
 save the program, download it to the microcontroller and test it.

Exercise 11 Page 23
Using Software Macros
Introduction:
In code-based programming languages, like ‘C’ and ‘BASIC’, a software macro would be called a
‘subroutine’ or ‘function’ or ‘procedure’. As programs get bigger, they use certain combinations of
instructions over and over again. These programs become harder to understand and read. Rou-
tines that are re-used can be put into a software macro, which can be called whenever it is needed
in the main program. Making use of these software macros ‘lightens up’ the main program and
makes it much easier to read.
Objectives:
 to use software macros to simplify the structure of a program;
 to create software macros;
 to use closed loop control;
 to use PWM to control the brightness of LEDs.
 Software macros - Exercise 11 - Using Software Macros
 Flowcode Wiki - ‘Software macro icon properties;
Instructions
Program 1:
 write a program that selects and runs one of three different programs by using two switches:
 switch ‘0’ selects one of three programs (which you developed earlier);
 ‘X’: an 8-bit binary up-counter, displayed on the LEDs.
 ‘Y’: an 8-bit binary down-counter, displayed on the LEDs.
 ‘Z’: an 8-bit bidirectional ‘running light’, displayed on the LEDs.
 the LCD displays a text message identifying the selected program;
 switch ‘1’ activates the chosen program when pressed.
 the three programs are placed in software macros.
 download this program to the microcontroller and test it.
 modify program 1 so that:
 if switch ‘0’ is pressed while one of the three software is running, execution stops imme-
diately and focus returns to the main loop and waits for a new selection.
 modify program 1 again so that:
 if switch ‘0’ is pressed while one of the three software is running, execution stops and
returns to the main loop, as before, but it stores the value displayed on the LEDs;
 when the next selection is made, that macro starts the LEDs from where the previous one
left off, making the transition between them smoother.

Exercise 12 Page 24
Using External Interrupts
Introduction:
In earlier exercises, the microcontroller did not necessarily react to inputs straight away because it
was busy doing something else. The external interrupt features of the PIC solve this problem. On a
16F1937, the external interrupts are on pin ‘RB0’ - a single pin interrupt and on port B as an
‘interrupt on change (IOC)’. If these interrupts are initialized correctly, then a change on port B can
cause the program to stop execution immediately and switch to executing the appropriate inter-
rupt macro. We then have what is called a ‘real time’ execution.
Objectives:
 to create and use ‘single-pin’ interrupts;
 to create and use ‘interrupt-on-change’ (IOC) interrupts;
 to use real time operation of a microcontroller;
 ‘Flowcode 7’ Wiki.
Instructions
Program 1:
 write a program to time how many seconds have passed since the program was reset and :
 display the result on the LCD;
 uses a variable called ‘count’ whose value is displayed on the LEDs.
Don’t use any kind of interrupt.
Hint:
Use a 1s delay.
A rising edge on pin ‘RB0’ should call a macro that adds one to ‘count’.
 re-design this program using an interrupt (single-pin) on RB0.
 now re-design it using both kinds of external interrupt so that:
 triggering the single-pin interrupt increments ‘count’ (count = count + 1);
 triggering the IOC interrupt decrements ‘count’ (count = count - 1).

Exercise 12 Page 25
Using External Interrupts
Program 2:
 write a program to make an electronic dice that :
 counts from 1 to 12;
 display the result on the LCD;
 starts ‘rolling’ when switch ‘0’ is pressed;
 stops ‘rolling’ when switch ‘0’ is pressed again.
Hint:
The LCD should display numbers from 1 to 12, one after the other, over and over again rapidly, at
20 ms intervals - much to fast to see with a human eye.
 modify this program so that:
 the dice keeps ‘rolling’ as long as switch ‘0’ is held down;
 stops ‘rolling’ when the switch is released;
 at that point displays the number on the LCD.
Program 3:
 write a program to make a reaction timer that :
 lights all LEDs initially;
 keeps them lit for around 6s;
 switches them off and starts a timer;
 stops the timer when the player presses switch ‘0’;
 then displays the resulting ‘reaction time’ on the LCD.
(Use a variable that is incremented every 10ms.)
 modify program 3 to limit the time allowed to the size of the used variable and:
 displays a message is displayed on the LCD when this size is exceeded;
 includes a trap to prevent cheating by simply holding down switch ‘0’ continuously.

Exercise 13 Page 26
Using Timer Interrupts
Introduction:
The other type of interrupt function in ‘Flowcode 7’ is the timer interrupt. These allow you to per-
form software tasks at precisely predetermined time intervals - a really useful feature when devel-
oping time critical applications and clocks.
Objectives:
 to create and use timer interrupts;
 to use the prescaler to create accurate time intervals;
 to trigger the timer using the crystal or an external event;
 Flowcode Wiki - ‘What is a 7-segment display?’;
Timer arithmetic:
The 16F1937 has several timers, but we look at only two: ‘TMR0’ (Timer 0) and ‘TMR1’ (Timer 0).
 TMR0 can be triggered by the crystal or by a transition on the ‘T0CKI’ pin ‘RA4’.
 The internal clock has a frequency of ‘crystal clock frequency’/4, i.e. 19,660,800/4 =
4,915,200Hz.
 The TMR0 prescaler can be set from 1:2 to 1:256. For this exercise, set it to 1:256, so that every
256 clock pulses cause the TMR0 to increase by 1. This happens at a frequency of
4.915.200/256 = 19.200Hz.
 Every time this 8-bit timer ‘overflows’ (reaches 256), it generates an interrupt. This happens
with a frequency of 19.200/256 = 75Hz, so that the main program is stopped 75 times per sec-
ond and so the timer interrupt macro is executed 75 times per second.
 Instead of using the crystal, this timer can also be ‘clocked’ by an external event, as when
measuring motor speed etc.
 TMR1 can be triggered by the crystal oscillator or by a transition on the ‘T1CKI’ pin ‘RC0’.
 Its operation is similar to that of TMR0, except that it uses different prescaler values.
 TMR2 also exist but this in not discussed in this course.

Exercise 13 Page 27
Using Timer Interrupts
Instructions
Program 1:
 write a program to produce a precise ‘seconds’ timer that :
 displays the result on the LCD;
 starts when the microcontroller is reset.
(Use a 1s delay. Don’t use a timer interrupt.)
 download this program to the microcontroller and test it using your watch.
 rewrite the program using a timer interrupt.
 download this program to the microcontroller and test it as before.
Program 2:
 write a program to create a basketball timer that :
 starts when switch ‘0’ is pressed;
 displays the time elapsed on the LCD;
 makes the LEDs flash on and off when 30s has elapsed, (the time allowed for the team
with the ball to make a goal attempt.)
(Use a ‘single-bit’ interrupt on pin ‘RB0’ to start the timing.)
Program 3:
 rewrite the reaction-timer program (Exercise 12, program 3) to use a timer interrupt.
 download this program to the microcontroller and test it as before.
Program 4:
 write a program to produce a precise clock that displays the time elapsed since the last reset, in
hours, minutes and seconds on the LCD.
 modify this program so that:
 switch ‘0’ stops the clock when pressed the first time;
 switches ‘1’, ‘2’ and ‘3’ can be used to change the displayed time to the actual time;
 switch ‘0’ restarts the clock when pressed a second time;
Program 5:
 write a program to produce a timer that counts down from 01:00:00 to 00:00:00 in seconds and
then lights all the LEDs.

Additional Challenges Page 28
1. Develop a dimmer for all the LEDs that reacts to measured light intensity.
 The light sensor monitors the light intensity in a room. When this intensity drops, a control circuit
sends more power to the lights in that room and vice versa when the intensity increases.
 Use the LEDs to simulate the dimmed lights. This is done by programming a software PWM output
to all LEDs on port B. When the PWM ‘on’ time increases, the LEDs get brighter, etc.
 Put this program in a timer interrupt macro.
 The main loop monitors the analogue input from the light sensor on the sensor board, on port C.
When the light sensor detects less light, the LEDs need to shine brighter. The opposite should hap-
pen with the LEDs when the light level, measured by the light sensor, intensifies.
 The period of the PWM signal stays a constant 20ms at all times, set using a timer interrupt.
 Download this program to the microcontroller and test it. If you have a 2 channel oscilloscope,
measure the analogue input of the light sensor on one and the PWM output to one of the LEDs on
the other.
 Using a similar approach, develop a temperature controller for an incubator. The EB090 Sensor
Motherboard can be used with either the EBM003 Thermistor sensor module or the EBM004 Digi-
tal temperature sensor module. Use the LEDs to simulate the action of a heater.
2. Three judges vote on variety acts in a ‘X-factor’-like game show. When two or more judges vote ‘Yes’,
the act progresses to the next round.
 Design a program to combine the judges’ votes into a ‘pass/fail’ verdict.
 Create two LED light sequences, one to indicate ‘pass’ and the other ‘fail’.
3. Design an automatic watering system for a sealed terrarium (glass plant container). Use the EBM016
Humidity sensor module to sense when the terrarium needs watering.
 The output device is a motor-driven pump that runs for a set period of time once triggered. There
should be a ‘rest’ period after watering before the system can operate again.
4. Create a combination lock, using the EB014 Keypad board to input a four-digit ‘PIN’.
 Add a feature that ‘locks out’ a user after three unsuccessful attempts.
 Modify it to prevent further access to the system for a period of time such as ten seconds.
 Use the LCD display to show the numbers selected on the keypad and the number of attempts
made.
5. Develop a proximity switch for a security light using the EBM019 Ultrasonic distance sensor module. The
system should switch on four lights (12V lamps) when a person approaches within one metre of the sen-
sor and so makes use of the EB038 Relay module
6. Use the EBM020 Infrared sensor module to time the swing of a pendulum without impeding it.
7. Design a system to drive the DC motor (and sensor) on the Actuators training panel at a steady speed.
 Add a feature to modify this set speed.
8. Design a system to drive the stepper motor on the Actuators training panel so that it rotates, in 15 0
steps, through one complete circle and then reverses back to its initial position in the same manner.

Page 29
Part 2
Using E-Blocks

Page 30
Part 2 Contents
How E-blocks connect to each other ....................................................................................................... 31

Using a backplane .................................................................................................................................... 31
Using E-blocks on the bench .................................................................................................................... 32
Protecting E-blocks circuitry .................................................................................................................... 32
Using covers ............................................................................................................................................. 32
Adding power to E-blocks ........................................................................................................................ 33
Understanding the patch system ............................................................................................................. 34
Sharing a port ........................................................................................................................................... 35
Using ZIF Sockets ...................................................................................................................................... 35
E-blocks documentation and numbering ................................................................................................ 35
Notes for Arduino users: .......................................................................................................................... 36

Page 31
How E-blocks connect to each other

E-blocks are built on a bus-based concept. Each E-block D-type connector uses nine pins, allowing
transfer of eight bits of data and ‘ground’.
In the E-blocks system, some E-blocks are ‘upstream’ and some are ‘downstream’. ‘Upstream’
devices have ‘intelligence’, are usually programmable and control the flow of information to
‘downstream’ devices. In the E-blocks system, ‘upstream’ devices connect using 9-way D-type
sockets, whereas ‘downstream’ devices connect using 9-way D-type plugs.
The diagrams show how the pins are numbered on the plugs and sockets. On
both plugs and sockets, bit 0 is delivered on pin 1, bit 7 on pin 8 and pin 9 is
designated 0V.
Where two ‘upstream’ devices need to be connected together a gender changer
or ‘Insulation Displacement Connector’ (IDC) cable with two IDC sockets on can
be used.
Using a backplane
E-blocks can be mounted onto a metal backplane to form a
completely rugged system. To facilitate this, each E-block is
fitted with four 3mm holes spaced at 20mm intervals. M3
bolts with spacers are used to mount the E-blocks onto a
backplane, which has 4mm holes on a regular 20mm grid.
The mounting holes on the backplane, the holes on the
E-blocks and the spacing of each D-type plug and socket on
the E-blocks are arranged so that E-blocks can be connected
together and still be mounted on the backplane.
If you modify your E-blocks system regularly or want others to be able to do this, we suggest that
you use steel or Nylon M3 bolts on all E-blocks. They will then ‘sit’ on the metal backplane without
being bolted to it. (If you intend to move the system around, then one or two nuts on the back will
ensure your E-blocks stay in place.)
The diagram shows 12mm bolts with self locking nuts - these keep the bolts secured onto the
circuit board and allow you to position the boards on the backplane as you wish.
For best results, attach the self locking bolts and nuts and then slacken off the nuts by a quarter
turn to allow a little movement in the PCB mounting holes. This makes it easier to take the board
off the backplane.

Page 32
Using E-blocks on the bench

You do not need a backplane to use E-blocks - you can simply connect them together on the bench.
In each E-blocks package you will find a four small rubber feet to
facilitate this. These provide a degree of protection for the E-blocks
boards and help prevent short-circuits from tinned copper wire and
other metal objects on the bench.
The disadvantage is that your E-blocks system is less portable as the
connectors will be under more stress as the system is moved about.
Protecting E-blocks circuitry
Where possible, leaded components have been used for devices on E-blocks boards that are
susceptible to electrical damage. This makes the task of replacing them simple should they be
damaged.
Some ‘upstream’ boards (such as the ARM processor boards and the FPGA board) make use of
surface mounted technology components which are not easy to replace. In these cases, small
daughter boards have been used instead. Where damage occurs, new daughter boards can be
ordered to replace them.
To protect ‘upstream’ components, all ‘downstream’ E-blocks boards include protective resistors.
Should errors occur when declaring the nature of port pins, e.g. an input declared as an output, no
damage will be caused.
However there are circumstances where it is possible to cause damage:
 care is needed when using screw terminal connectors and patch/prototype boards;
 where possible, use protective resistors for the lines you need to connect when connecting two
‘upstream’ boards together with a gender changer or IDC cable;
 make sure you are earthed before handling E-blocks circuit boards to minimise the risk of static
damage. If you have not got an antistatic wrist band, then touch a radiator or other earthed
metal object.
Before making any changes to the E-blocks system, turn off the power supply.
Using covers
In some circumstances, it is desirable to limit access to parts of the E-blocks boards. Perhaps you
do not want users to change board settings or perhaps there is a risk of vandalism or theft.
To deliver this enhanced protection, clear acrylic covers are available for all E-blocks - the diagram
shows one in use with a Multiprogrammer.

Page 33
These covers are mounted onto E-blocks

with 25mm M3 bolts and 10mm spacers,
using the grid of holes for mounting the E-
blocks to the backplane.
The cross section view shows how this is
done:
The tight-fitting clear acrylic covers add

considerable strength to each E-block as
well as making them more tamper proof.
A different technique is used for the switch
board where, because the switches are
relatively short, the spacers are replaced
with M3 lock nuts before the cover is put into place. This can be seen in the diagram opposite:
Adding power to E-blocks
Power connections are routed between E-blocks using simple screw terminals. This facilitates the
interoperation of E-blocks with different voltage levels (notably 3.3V and 5V) and power sources.
Most ‘upstream’ E-blocks have 5V outputs provided by a voltage regulator. These boards are
powered by applying a higher voltage via a power jack (usually positive outer) or using screw
terminal blocks.
As 0V is connected to all boards through the
9-way D-type connectors, it is only the
positive power supply line that needs a wire
link.
To improve the layout, power wires can be
looped under E-blocks and backplane to
connect ‘downstream’ E-blocks.
The photograph shows the red power wires
linking E-blocks together. They route 14V
from the Multiprogrammer to the Proto
board.
Be careful when doing this as using the wrong voltage can damage the PIC device on the
ultiprogrammer board!

Page 34
Understanding the patch system

Most 'downstream' E-blocks include a patch system that gives you flexibility in the connections
that are made between ‘upstream’ and ‘downstream’ E-blocks. The default connections are
optimized for ease of connection between PIC ‘upstream’ and E-Blocks ‘downstream’ boards.
Other microcontrollers may require different connections, facilitated by the patch system.
The patch system has two parts:
 jumper links that select between default connections and the patch system,
 the patch connectors themselves.
The photographs show an EB090 sensors motherboard with and without sensors attached to it.
The next two diagrams show how to use

the patch system on this board.
In the upper diagram, jumpers J12 and J13
are set to the ‘default’ position. This
routes signals from the light sensor and
‘pot’ to pins 1 and 2 of the D-type plug,
respectively.
However, when using a different

microcontroller, you might want the signal
from the ‘pot’ to appear on pin 5 of the D-
type plug. To achieve this, move jumpers
J12 and J13 to the 'patch' position and add
a wire from the ‘pot’ socket on ‘J11’ to pin
5 on J8, as shown in the lower diagram.

Page 35
Sharing a port
Sometimes, you need to split a port into several sections, or share signals on a port between
‘downstream’ E-blocks. To do this, use a splitter cable. This allows you to connect one ‘upstream’
port to two ‘downstream’ ports using IDC (Insulation Displacement Connector) connectors and
ribbon cable.
For example, suppose that you are developing a system that uses two external analogue sensors.
The Sensor board has only one external analogue sensor port. Use a splitter cable and two Sensor
boards, giving the result shown (note; board(s) shown below are the discontinued EB003):
The analogue sensor input on the upper board uses the default connection, bit 3. On the lower
board the jumpers are moved to the ‘patch’ position and a small wire is used to connect the
second analogue sensor to bit 2. The result allows you to connect one analogue sensor to bit 3 and
the other to bit 2 on the ‘upstream’ board.
Using ZIF Sockets
It is possible to use Zero Insertion Force (ZIF) sockets with the E-Blocks PIC
Multiprogrammer and other programmers in the E-blocks range. These sockets are
useful where the chips will be removed from the programmer many times.
ZIF sockets are available from many vendors and can be inserted into the DIL
sockets on the ‘upstream’ boards. Where E-blocks boards have other components
close to the DIL socket, add further DIL sockets to gain enough height to allow the
ZIF socket to be inserted safely.
Matrix sells a PIC microcontroller programmer complete with ZIF sockets.
E-blocks documentation and numbering

The E-blocks range is under constant development. Understanding E-blocks product codes allows
you to locate the correct information for your boards.
A typical part number for an E-block is: 'EBAAA-BB-C'.
Here:
 'AAA' refers to the type of board;
 ‘BB’ refers to an item related to that board;
 'C' refers to the version number of that board.
Example 1: the part number 'EB006-00-6':
'006' is the code for the Multiprogrammer;
'00' is the code for the built and tested board;
'6' is version 6.
Example 2: the part number 'EB003-30-1':
'003' is the code for the Sensor board;
‘30’ is the code for the technical datasheet;
'1' is version 1.

Page 36
Notes for Arduino users:

Connect the EB083 and EB093 together as shown in the
diagram.
In addition, connect an Arduino Uno to the EB093 E-blocks
board and provide a USB connection between the Arduino
and a computer running Flowcode 7.
On opening Flowcode 7, you are presented with the

‘Welcome’ screen, part of which is shown opposite.
From here, click on ‘Open Template’.
From the Load Template screen, select

‘UnoR3 & Combo’.
Click on ‘Load’ to open the template.
The template opens with the

standard Flowcode 7 environment
with the EB083 Development Board
on the System Panel.
The basic flowchart can now be
developed into a program that uses
components on the EB083 board.
Note: Despite having two full 8-bit hardware port connections between the EB083 Development
board and the EB093 Shield, the Arduino Uno can only provide 6 general purpose I/O connections
on port A, (A0-A5). Therefore, LEDs ‘LA6’ and ‘LA7’ and switches ‘SA6’ and ‘SA7’ cannot be used
with the Arduino Uno.
In order to program the Arduino Uno board directly from within Flowcode 7, you must ensure that
the appropriate drivers are installed. These are provided with the Flowcode 7 download, but are
not automatically installed.

Page 37
Part 3
Introduction to
Flowcode 7

Page 38
Part 3 Contents
Introduction to ‘Flowcode 7’ ................................................................................................................. 39

What is ‘Flowcode 7’ ............................................................................................................................. 39
‘Flowcode 7’ overview ........................................................................................................................... 39
The toolbars and panels: ....................................................................................................................... 40
Icons toolbar: ......................................................................................................................................... 40
Components toolbar: ............................................................................................................................ 40
Menu and simulation toolbar: ............................................................................................................... 40
Dashboard & System Panels: ................................................................................................................. 41
Properties pane ..................................................................................................................................... 41
Project explorer ..................................................................................................................................... 41
Icon list ................................................................................................................................................... 41
Chip window .......................................................................................................................................... 42
Docking and undocking the toolbars and panes ................................................................................... 42
Flowchart window ................................................................................................................................. 43
Simulation Debugger window ............................................................................................................... 43
Controlling windows, toolbars and panes ............................................................................................. 43
Starting a new Flowchart ....................................................................................................................... 44
Opening an existing Flowchart .............................................................................................................. 44
Saving a Flowchart ................................................................................................................................. 44
Saving Flowchart Images ....................................................................................................................... 44
Printing Flowcharts ................................................................................................................................ 45
The View menu ...................................................................................................................................... 45
Global Options ....................................................................................................................................... 45
Flowchart Tab ........................................................................................................................................ 45
Scheme Tab ........................................................................................................................................... 46
Annotation Tab ...................................................................................................................................... 46
Application Tab ...................................................................................................................................... 46
Editor Tab .............................................................................................................................................. 46
Locations Tab ......................................................................................................................................... 47
Scope Tab .............................................................................................................................................. 47

Page 39
Introduction to ‘Flowcode 7’
This section allows those who are new to ‘Flowcode 7’ to understand how it can be used to devel-
op programs. It allows you to create programs step-by-step to learn about how ‘Flowcode 7’
works.
We advise that you work through every section to familiarise you with all of the options and fea-
tures of ‘Flowcode 7’ and introduce you to a range of programming techniques. As you work
through each part, please also refer to the ‘Flowcode 7’ help file. The main ‘Flowcode 7’ icons are
introduced in turn.
Specifically in this section you will learn:
 how to use each ‘Flowcode 7’ icon (except the C code icon);
 how the fundamental Components in ‘Flowcode 7’ work - the LED, LCD, ADC, switch, 7-segment
display, 7-segment quad display, keypad and EEPROM components.
What is ‘Flowcode 7’
‘Flowcode 7’ allows you to create microcontroller applications by dragging and dropping icons on
to a flowchart to create programs. These can control external devices attached to the microcon-
troller such as LED's, LCD displays etc.
Once the flowchart has been designed, its behaviour can be simulated in ‘Flowcode 7’ before the
flowchart is compiled, assembled and transferred to a microcontroller.
The process:
1. Create a new flowchart, specifying the microcontroller that you wish to target.
2. Drag and drop icons from the toolbar onto the flowchart and configure them to create the pro-
gram.
3. Add external devices by clicking on the buttons in the components toolbar.
4. Edit their properties, including how they are connected to the microcontroller, and configure
any macros they use.
5. Run the simulation to check that the program behaves as expected.
6. Transfer the program to the microcontroller by compiling the flowchart to C, then to assembler
code and finally to object code.
‘Flowcode 7’ overview
The ‘Flowcode 7’ environment consists of:
 a main work area in which the flowchart windows are displayed;
 a number of toolbars that allow icons and components to be added to the flowchart;
 the System and Dashboard panels that display the attached components and provide basic
drawing capabilities;
 the Project Explorer panel that shows project variables, macros and component macros;
 the Icon List panel that shows bookmarks, breakpoints and search results;
 windows that:
 allow the status of the microcontroller to be viewed;
 display variables and macro calls when the flowchart is being simulated.

Page 40
A typical screen - an automotive project:
The toolbars and panels:

Icons toolbar:
'Drag-and-drop' icons from this toolbar onto the
main flowchart window to create the flowchart application.
Normally positioned on the left hand side of the screen, it can be undocked.
Components toolbar:
Connect external components to the microcontroller or use basic panel drawing commands. Com-
ponents are grouped in different categories that appear as drop down menus. Click on a compo-
nent and it will be added to the microcontroller and appear on the panel. The pin connections and
properties of the component can then be edited. Normally positioned on the top left hand side of
the screen next to the Icons toolbar this toolbar, it can be undocked.
Menu and simulation toolbar:

 Open and save files.
 Undo and redo actions.
 Print out your flowchart.
 Control the simulation and download functions.
These functions are also available on the standard Windows menu at the top of the screen:

Page 41
Dashboard & System Panels:

 The components that you connect to the microcontroller will be displayed on one of these panels where
you can interact with them when running a simulation.
 They also provide basic drawing features like lines, shapes, and images, which can be used to build ad-
vanced professional-looking panels.
The Dashboard Panel is primarily for 2D
use although it does offers a fixed 3D view.
It is generally used as an interface showing
the controls for interactive components.
The System Panel is the main 3D panel,

offering many more features and options:
 full camera control;
 editable background environments with default
'Sky Dome'and 'World Dome' views;
 the option to use an image as the background;
 'Shadow mode', offering both 'Tabletop' and 'Object' shadow options.
More details on these panels are found in the 'Flowcode 7 - Getting Started Guide’.
Properties panel
All items on the panel, including the panel itself, have associated properties
that are displayed in the Properties pane when the item is selected.
Some are read-only while others can be manipulated.
Some, like size and position, change as you interact with the item.
Others allow access to more advanced features of the selected item.
The Properties pane typically docks to the right hand side of the screen but
looks like this when undocked:
Project explorer
The buttons along the top of this panel allow you to select ‘Ports’, ‘Globals’,
‘Macros’ and ‘Components’.
 'Ports' - variable names assigned to the microcontroller ports.
 'Globals' - any constants and variables that have been defined for use in the cur-
rent project.
 'Macros' - user-created macros in the current program and allows the userto drag
them into the current flowchart.
 'Components' - similar except that it also lists components that are present in the
panel.
Icon list
All bookmarks, breakpoints and disabled icons are listed, together with search and error results.

Page 42
Chip window
The pinout for the currently selected microcontroller chip is displayed.
When the flowchart is being simulated, the state of each microcontroller I/O
pin is shown as red or blue, for ‘high’ or ‘low’ outputs respectively.
Docking and undocking the toolbars and panes

Toolbars and panes can be undocked from their default positions and either be left free floating, or
docked to the top, bottom or the sides of the ‘Flowcode 7’ window.
Here is an (extreme) example, showing floating toolbars:
To undock a docked toolbar, simply click and hold on the toolbar 'grab bars' (the speckled area at
the top or side of the toolbar) and drag the toolbar to its new position.
To dock it again, double-click on the ‘grab bar’.

Page 43
Flowchart window
The icons that make up the flowchart are displayed in this main
space.
In addition, the flowcharts of any macros involved in the program
are shown under their own separate tab.
The Main flowchart tab is always visible and the macro tabs can
be shown or hidden as needed.
A red star alongside an icon indicates that the flowchart has not
been saved in its current form.
Simulation
When simulating a program on ‘Flowcode 7’ a red rectangle
around an icon indicates the icon to be executed next.
Debugger window
When simulating a flowchart, the current values of any
variables used in the program appear in this window.
These are updated after a command is simulated
(unless the simulation is running at full speed - 'As fast
as possible').
If you press the pause button during simulation, you
can click on a variable in this window to change its value, (allowing you to test the program under
known conditions).
The window also shows the current macro being simulated under the 'Macro Calls' section, useful
when one macro calls another during the simulation process.

Page 44
Starting a new flowchart

 Create a new flowchart by selecting File > New or click the 'New' button on the 'Main
toolbar'.
 Select the microcontroller that you wish to target from the list presented.
 ‘Flowcode 7’ then displays that microcontroller in the 'Chip' view (View > Chip) and creates an
empty flowchart for you to start adding your icons to.
Opening an existing flowchart
 There are a number of ways of opening an existing ‘Flowcode 7’ flowchart:
 Select the Open option from the File menu (File > Open) or click the 'Open' button on the
'Main toolbar'. This will allow you to browse for the file you want.
or
 Select the file from the list of most recently used files in the File menu.
or
 Double-click on a ‘Flowcode 7’ (.fcf) file in Windows Explorer to launch ‘Flowcode 7’ and open
the file.
Saving a Flowchart
To save a flowchart, select either the ‘Save’ or ‘Save As’ options from the File menu (File > Save /
Save As...).
Flowcharts must be saved before they can be compiled to C or transferred to a microcontroller.
Saving Flowchart Images
To save an image of the currently active flowchart, select 'Save current Flowchart...' from the 'Save
Image' sub-menu in the 'File' menu (File > Save Image > Save current Flowchart...).
This function saves an image of the program to any file in the format chosen from the list:
 Bitmap (*.bmp);
 JPEG (*.jpg;*.jpeg);
 GIF (*.gif);
 PNG (*.png).
Note that the current zoom rate is used to determine the resolution of the image saved. If you
need high quality images for printing then increase the zoom rate.
From the 'Save Image' menu, you also have the option to save the current image of either the
'Dashboard Panel' or the 'System Panel' (File > Save Image > Save Dashboard image... / Save Sys-
tem image...).
These images can be saved to any file format chosen from the list:
 Model (*.mesh)
 Bitmap (*.bmp)
 JPEG (*.jpg;*.jpeg)
 GIF (*.gif)
 PNG (*.png)Model (*.mesh)

Page 45
Printing Flowcharts
Use the Print Preview command to display the flowchart as it would appear when printed.
When you use this command, the main window will be replaced with a Print Preview window in
which one or two pages will be displayed in their printed format.
The print preview toolbar offers you options to:
 view either one or two pages at a time;
 move back and forth through the document;
 zoom in and out of pages;
 initiate a print job.
Alternatively, the print job can be initiated without preview by selecting 'Print' from the 'File' menu
(File > Print) or clicking the ‘Print’ icon on the 'Main toolbar'.
The View menu
This dictates which panels and toolbars appear on the workspace, a useful feature when trying to
simplify its appearance.
It also has a ‘Zoom’ menu, which allows you to display more icons in the workspace window than
when using the default zoom setting. The current zoom setting is displayed on the ‘Zoom’ sub-
menu, and on the right hand side of the status bar, at the bottom of the ‘Flowcode 7’ window.
The size of each icon is dictated by the zoom level - for larger icons, zoom in - for smaller icons,
zoom out! Use the Print Preview function to optimise the appearance of your flowchart on the pa-
per.
The ‘Zoom’ menu can also be accessed by right-clicking on the flowchart workspace.
Function key shortcuts:
 Increase Zoom (F3) - increases zoom size by 5%;
 Decrease zoom (F2) - decreases zoom size by 5%;
 Default zoom (F4) - set zoom to 75%;
 Zoom to fit - Zooms to fit the whole flowchart into the current window;
 Zoom to fit width - Zooms to fit the width of the flowchart into the width of the window.
The ‘View’ menu also includes a ‘Style’ menu, offering a dark or a light overall appearance to the
‘Flowcode 7’ application and a ‘Global Options’ area, offering a series of powerful tools to config-
ure the flowchart.
Global Options
To see the effect of changing these settings, click the 'Preview' button at the bottom of the win-
dow.
Flowchart Tab
This tab contains the settings for changing font style
and size and features of the icons.

Page 46
Scheme Tab
This tab contains the settings for changing the ap-
pearance of the flowchart, including icon colours
and graphics, background colours and patterns etc.
Annotation Tab
All the settings on this tab relate to manipulating the
annotations on the flowchart, including icon text
and descriptions as well as annotation and tooltip
styles.
It also the ability to add icon comments in C code.
Application Tab
These settings affect the look and ‘feel’ of the over-
all program.
The skin presets and tab options change the general
look of ‘Flowcode 7’. It also offers the ability to print
in colour and to change web access settings.
The ‘Override language’ option allows the user to
override the default ‘Flowcode 7’ language settings
and to display ‘Flowcode 7’ in a specified language.
To do this, select the language from those available
on the drop down list and restart ‘Flowcode 7’.
It will do so in the selected language, provided the relevant language pack has been installed.
Editor Tab
‘Auto-edit new icons’ opens the Properties pane
when a new icon is added to the flowchart.
Use the ‘Add icons comments to C code’ option to
include their associated comments when icons are
compiled to C code.
The ‘Allow errors in flowcharts’ option allows you to
edit icon properties without triggering error messag-
es.
The ‘Allow unconnected ports and pins’ option al-
lows you to change component connections to ‘unconnected’ without triggering an error message
(though these will still occur during simulation and compilation.)

Page 47
Locations Tab
This allows you to choose the target directory that
‘Flowcode 7’ compiles to by default. It also allows
you to specify directories that ‘Flowcode 7’ should
search when looking for components and dictionar-
ies.
Scope Tab
The Data Scope allows the user to see the results
and values from raw data and from components
themselves. This data is displayed during simulation
and allows the user to monitor signals selected on
the various scope channels.
It can read and display data from a number of differ-
ent ports simultaneously. Adjusting the ‘timebase’
allows the user to view a small amount of data at
increased accuracy or larger amounts of data.

Page 48
Part 4
Flowcode 7
Your first program

Page 49
Part 4 Contents
Adding digital outputs - Light the LED: .................................................................................................. 50

The hardware: ........................................................................................................................................ 50
The flowchart: ........................................................................................................................................ 50
Adding LEDs ........................................................................................................................................... 51
Review the progress! ............................................................................................................................. 51
Congratulations! .................................................................................................................................... 51
High Speed Simulation ........................................................................................................................... 51
Slowing it Down ..................................................................................................................................... 51
Stepping Through Your Program: .......................................................................................................... 52
Changing the output: ............................................................................................................................. 52
Binary Numbers ..................................................................................................................................... 52
Converting Numbers .............................................................................................................................. 53
Outputting Numbers .............................................................................................................................. 53
And a short test! .................................................................................................................................... 53
Working in Hex ....................................................................................................................................... 54
Hex in ‘Flowcode 7’ ................................................................................................................................ 54

Page 50
Adding digital outputs - Light the LED:

Create a program that lights an LED attached to port B of the microcontroller
Put another way, this program introduces the topic of how to control a digital output.
Don't worry - this program will not radically change your life!
The hardware:
This diagram shows you how to set up the E-blocks hardware. It was shown earlier at the beginning
of the 'Programming Exercises' section, along with appropriate hardware settings.
The flowchart:
 Start a new project by selecting 'File' and then clicking 'New'
in the menu which appears (File > New). You are asked to
choose a target microcontroller from the list that appears.
Double-click on '16F1937'.
 Next, you see a flowchart, blank except for 'BEGIN' and 'END' icons. All flowcharts have
these icons by default. Move the cursor over the 'Output' icon, , in the Icon toolbar. Click
and drag it over to the work area. While dragging it, the normal cursor changes into a small
icon.
 Move it in between the 'BEGIN' and 'END' icons. As you do so, an arrow appears showing you
where the Output icon will be placed. Release the mouse button to drop the icon in between
the 'BEGIN' and 'END' boxes.
 Move the cursor over the Output icon. Now, either double-click with the left mouse button or
click with the right mouse button and choose 'Properties'
from the menu that appears.
 You now see a dialogue box like the one opposite
Move the cursor over the ‘0’ in the ‘Variable or value’ box
and click once. This will highlight the '0' value. Change this
value to '1'. This is the value that will be sent to the se-
lected output.

Page 51
 Move the cursor over the arrow in the ‘Port’ win-

dow.
Click on 'PORTB' in the menu that appears. The dialogue
box now looks like the one opposite.
 Click on the 'OK' button to close the box.
So far, you have created a program that outputs the number

'1' to port B of the microcontroller.
The next step is to connect a virtual component to that port to test whether the program works.
Adding LEDs
 Click the 'Outputs' button in the Components toolbar and select the 'LED
Array' component.
It looks like this:
 Click or drag it to add it to the System Panel.
 Click once on the component in the panel to select it. Its 'Properties' pane
will open and display its properties.
 In the 'Simulation' section, change the 'Count'
property to '8' by typing in the box next to the name.
 Now, go to the 'Connections' section and change the 'Port' to 'PORTB'. Do-
ing this means that port B controls the LED array
 Change the colour of the LED's to red, using the 'Colors' property.
(Make sure that the 'Same’ property is set to 'Yes' to change the whole LED
array. )
Review the progress!
So far, you have:
 inserted an Output icon in the flowchart;
 set it up to deliver a value of 1 to port B;
 connected eight red LED's to the eight bits of port B.
Congratulations!
You have completed the first part of the program - to control digital (i.e. on / off) outputs.
Now test it by running a simulation of this program.
High Speed Simulation
Click on the 'Run' icon, on the main toolbar.
The result - the first LED lights and then there is a message saying that the simulation is completed.
If you blinked, you missed it!
What happened? The program outputted the number 1 and displayed it on the LED's, by lighting
the first and leaving the others off. But it happened extremely quickly!
Slowing it Down
When you pressed the 'Run' button, the program was over in a flash!
It's the good news and the bad - microcontrollers work really fast.
In later programs you learn how to slow them down to a speed that humans can cope with, using
delays or loops. For now we slow down the simulation!

Page 52
Stepping Through Your Program:

‘Flowcode 7’ allows you to step through the program icon by icon, using the 'Step
Into' button on the menu toolbar.
Click on it to see ‘Flowcode 7’ simulate the program step by step.
Now, you can see the effect of each icon.
On the flowchart, the red rectangle shows the icon that will be simulated the next
time you click on 'Step into'.
Changing the output:
 Right-click on the Output icon, and choose 'Properties' (or double-click the Output icon,) to
open the Properties dialogue box again.
 Click once on the 'Variable or value' box and change the number from 1 to 2.
 Click on 'OK' to close the box.
 Run the simulation by clicking on the Run icon:
 Notice that the LED array behaves differently.
 Repeat this, using different numbers in the 'Variable or value' box.
 What number makes all the LED's light?
Binary Numbers
Digital electronic devices can't cope with decimal numbers (0, 1, 2, ..9 etc.). Instead, they use the
binary system, which uses only two numbers 0 and 1. The number 1 could be represented by a
high voltage signal, while number 0 could be a low voltage.
The table opposite shows how the two number systems compare:
Decimal Same in binary
The decimal system uses ten numbers, 0, 1, 2, 3, 4, 5, 6, 7, 8 and 9. 0 0

On reaching the last of these, ‘9’, we start again with '0', but add an- 1 1
other number in front. For example, after '8' and '9' comes '10', and 2 10
after '18' and '19' comes '20' and so on. When we reach '99', both of
3 11
these go back to '0''s but with a '1' in front, to make '100'.
4 100
5 101
6 110
7 111
8 1000
9 1001
10 1010
In binary, the same thing happens, but a lot more often, because it Decimal Same in binary
uses only '0''s and '1''s. Counting up starts with '0', then '1', then back 1 1
to '0' with a '1' in front, making '10' (not ten - it's two!) Next comes
'11' (three) and start again with two '0's but with a '1' in front, to give 2 10
'100' (four) and so on. 4 100
8 1000

Page 53
Converting Numbers
Notice that each time the binary '1' moves one place Binary value
to the left, it doubles in value of the number in deci- 16 Decimal value
8 4 2 1
mal, as the table opposite shows.
1 1
We can use this idea to convert between number
systems. 1 0 2
In any binary number, the bit at the left-hand end, 1 0 0 4
the 'Most Significant Bit', (MSB), has the highest val- 1 0 0 0 8
ue. The one at the right-hand end, the 'Least Signifi- so
cant Bit', (LSB), is worth least . 1 1 1 7
1 0 0 1 9
Outputting Numbers 1 0 1 0 0 20
Finally, back to the question of outputting numbers! 1 1 1 1 1 31
Modify your program to output the numbers given
in the table, setting the LED colour to match, and check that the LED array behaves as shown!
Number sent to output LED array

31
32
130
255
And a short test!

Complete the table by:
 shading in the LEDs that light, for the first three rows;
 working out what number produces the LED patterns shown in the last three rows.
Number sent to output LED array

51
204
195
____
____
____

Page 54
Working in Hex
An experienced programmer might wonder if Decimal Binary Hex
‘Flowcode 7’ supports hexadecimal numbers. 0 00000000 0
The answer is ‘yes’.
1 00000001 1
Hexadecimal, 'hex' for short, is a more conven- 2 00000010 2

ient form than binary (for humans) for repre- 3 00000011 3
senting numbers. 4 00000100 4
 A binary digit is either 0 or 1. 5 00000101 5
 A decimal digit varies between 0 and 10.
6 00000110 6
 A hex digit has sixteen possible states.
7 00000111 7
Clearly sixteen states is a problem, as we have 8 00001000 8
only the digits from 0 to 9. To get round this, we
9 00001001 9
use the letters A to F to provide the additional six
digits required. 10 00001010 A
11 00001011 B
The table shows equivalent numbers in decimal,
12 00001100 C
binary and hex. Notice that we have shown the
binary number with eight digits. This is a handy 13 00001101 D
convention as computers - and our PIC chips - 14 00001110 E
store information in groups of eight bits. 15 00001111 F
A single memory cell inside a PIC device can store a number ranging from 0000 0000 and 1111
1111. In decimal this range is 0 to 255. The equivalent in hex is 0 to FF.
Hex in ‘Flowcode 7’
You can enter a hex number into ‘Flowcode 7’ by preceding it with '0x' in any of the dialogue box-
es.
For example:
This is equivalent to placing the binary number 1111 0000 onto port B.
In other words it places a logic 1 (around 5V) onto the most-significant four output pins, and a logic
0 (0 volts) onto the least-significant four pins.

Page 55
Part 5
Flowcode 7
Worked Examples

Page 56
Part 5 Contents
PIC or Arduino? ...................................................................................................................................... 57

Example 1. Adding digital inputs - Where's the fire? ............................................................................ 57
Setting up the flowchart ........................................................................................................................ 57
Creating the variables ............................................................................................................................ 58
More on variables .................................................................................................................................. 59
'Flowcode 7' variables: .......................................................................................................................... 59
Other variable issues: ............................................................................................................................ 59
Why worry?: .......................................................................................................................................... 59
Setting up the outputs ........................................................................................................................... 60
Adding the switches .............................................................................................................................. 60
Simulating the program ......................................................................................................................... 60
Example 2. Using loops - Counting sheep (badly) ................................................................................. 61
Setting up the calculation ...................................................................................................................... 62
Configuring loop properties ................................................................................................................... 62
When to test? ........................................................................................................................................ 62
Loop for a set number of times ............................................................................................................. 62
Setting up the input ............................................................................................................................... 63
Setting up the output ............................................................................................................................ 63
Adding the LED array ............................................................................................................................. 63
Adding the switch .................................................................................................................................. 64
Simulating the program ......................................................................................................................... 64
The solution: Adding a Delay ................................................................................................................. 65
Example 3. The LCD display - Posting messages ................................................................................... 66
LCD displays ........................................................................................................................................... 66
Adding the LCD component ................................................................................................................... 66
Writing messages ................................................................................................................................... 67
Other LCD functions .............................................................................................................................. 67
Using PrintNumber - an example: ......................................................................................................... 68
Example 4. A stopwatch ........................................................................................................................ 69
Example 5. Using binary numbers - A binary calculator! ...................................................................... 70
Setting up the inputs ............................................................................................................................. 71
Setting up the calculation ...................................................................................................................... 72
Setting up the output ............................................................................................................................ 72
Adding a LED array ................................................................................................................................. 72
Adding the switches .............................................................................................................................. 72
Slow simulation ..................................................................................................................................... 73
Example 6. Binary logic in control! ........................................................................................................ 74
A. Controlling the microwave oven: ...................................................................................................... 74
B. Controlling interior light in a car: ...................................................................................................... 76
Example 7. The SPI board - Making music! ........................................................................................... 78
Hardware setup ...................................................................................................................................... 78
Page 57
PIC or Arduino?
All of these examples can be tried out using either a PIC or an Arduino microcontroller. Arduino
users should familiarise themselves with the hardware information at the end of Part 2 of the
course.
Example 1. Adding digital inputs - Where's the fire?

The scenario!
A large building has a number of heat sensors in its fire alarm system. When there is a fire, the fire
brigade needs to know where the fire is. In other words, they need to know which heat sensor has
triggered the alarm.
The system is controlled by a PIC device. There are five heat sensors, connected as inputs to port A.
Port B is set up as the output port and connected to a set of five LEDs. If a heat sensor detects a
fire, the corresponding LED lights up.
Setting up the flowchart

 Launch ‘Flowcode 7’.
 Start a new flowchart by either:
 clicking on the new document icon, , on the main toolbar at the top left of the
screen;
 clicking on 'File' and then on 'New' on the menu that appears (File > New);
 pressing 'Ctrl+N' on your keyboard.
 Ignore the 'Project Options' 'Choose a Target' dialogue box for the moment.
 Click and drag an input icon, , and drop it in between the 'BEGIN' and 'END' boxes.
 Click and drag an output icon, , and drop it just below the input
icon.
 Your flowchart should look like the one below:

Page 58
Creating the variables

 Right-click on the input icon, and select 'Properties' from
the menu. The Input Properties dialogue box appears,
shown opposite. This allows us to add a 'variable'.
But what is a variable?
A variable is a place where we can store information, in
particular, information that changes as our program runs.
In this case, it is the number of the heat sensor that triggers
the alarm. It might be sensor 1 that goes off, or sensor 5…. .
We are going to use a variable called "SENSOR" (without
quotation marks) to store the information on which sensor has been triggered.
 Click on the arrow, , next to the
'Variable:' box.
You will see the next dialogue box:
 Now hover over the word 'Variables' and the arrow appears.
Click on it and select 'Add new'.
Another dialogue box, shown opposite, appears, offering
a large choice of variable types. For now, accept the default
type of 'Byte', a variable which can store numbers from '0' to
'255'.
Type the name "SENSOR" (without quotation marks) as the
name of the new variable and click on the ‘OK’ button. It now
appears in the list of variables that the flowchart can use.
 Double-click on the name of the variable to use it, or alterna-
tively click and drag the name into the variable box.
You now see the input 'Properties' box again. Notice that you
need to tell the system which port you are going to use to input
the data the system needs. It is set to port A at the moment, and we are going to leave it that
way.
In this case, the system needs to monitor the heat sensors and so each sensor will be connected
to a different bit of port A. Click on ‘OK’ to close the Input Properties box.

Page 59
More on variables
In the previous section you added a variable to the program using
the variable dialogue box:
Computer signals consist of streams of binary '0's and '1's on each
wire. A group of eight wires can carry eight 'bits', (binary digits,)
simultaneously. This grouping of eight bits, known as a 'byte' is
used for much of the internal wiring inside microcontrollers and
for the registers that hold and process data.
It is also used within memory subsystems. The contents of a
memory register having eight bits can vary from '0' to '255'.
A variable inside ‘Flowcode 7’ can be configured to use just one
memory register or more than one.
'Flowcode 7' variables:

‘Flowcode 7’ offers eight different types of variables:
 a 'Bool' (Boolean) variable can either be '1' or '0' (true or false);
 a single register, known as a 'Byte' variable, can store numbers from '0' to '255';
 a double register, known as an 'Int' variable, can store numbers from '-32768' to '+32767';
 a double register can also be unsigned, when it is known as a 'UInt' variable, which can store
numbers from '0' to '65535';
 a quad register, known as a 'Long' variable, can store numbers from '-2147483648' to
'2147483647';
 a quad register can also be unsigned, when it is known as a 'ULong' variable, which can store
numbers from '0' to '4294967295'.
The advice - Use a ‘Byte’ variable for simple counters and for variables that will not go above the
value '255'. It is the most economical in terms of memory space and also the fastest. Mathematical
processes involving two bytes (often referred to as '16 bit arithmetic') take longer to execute. A
multiple register, known as a 'String' variable, can consist of a number of ‘Byte’ variables - the de-
fault in ‘Flowcode 7’ is 20.
Other variable issues:
Floating point numbers, (that contain a decimal point somewhere in them,) can also be used, alt-
hough they represent a much wider range of values than an integer. They suffer a loss of accuracy
over large ranges.
Finally an 'object handle' is used to reference a more complicated piece of data (such as a file,
component or a block of text) whose internal format is not known.
Why worry?:
The number of registers inside a microcontroller is limited, and in larger applications the number
and types of variables must be managed carefully to ensure that there are enough.
On downloading a program, the variables in ‘Flowcode 7’ are implemented in the Random Access
Memory (RAM) part of the PIC device. In the 16F1937 there are 512 Bytes of memory. This means
you can have 512 ‘Byte’ variables, 265 ‘Int’ variables or 25 ‘Strings’ each consisting of twenty
‘Bytes’ or characters.

Page 60
Setting up the outputs

 Next, right-click on the Output icon, and select 'Properties' or just double-click on it. The Out-
put Properties box appears.
 Click on the arrow, , next to the 'Variable:' box. You will see the 'SENSOR' variable listed.
 Double-click on the word 'SENSOR' or click and drag it to the 'Variable:' box.
 The Output Properties box now shows that the system is set to output whatever data is stored
in the 'SENSOR' variable. Change the port used to port B, by clicking on the arrow, in the
port window, and then clicking on 'PORTB' in the menu that opens.
 Click on ‘OK’ to close the Output Properties box.
 The flowchart should now look like this:
Notice the arrows in the icon annotations. They show that infor-
mation will flow from port A into the flowchart, via ‘SENSOR’, (Input
icon) and from the flowchart, via ‘SENSOR’, out to port B (Output
icon).
 Now click on the Outputs button and select the ‘LED Array’ icon,
'Click-and-drag' it onto the System Panel.
 Change the 'Count' property under the 'Simulation' section to
the value '5' by clicking on the box next to the 'Count' property and
using the keyboard to input the value.
 Click next to 'Port' under the 'Connections' section to open an inter-
active view of the chip, showing the compatible pins.
 Click on the drop-down menu and select the 'PORT B' option. You have now connected the
LEDs to the pins on port B.
Adding the switches
You are going to use five switches to simulate the five heat sensors. The switch that is ‘on’ (closed)
is the heat sensor that has triggered the fire alarm.
 Click on the 'Inputs' button and select the ‘Switch Array’ Drag it into a suitable spot on the
System Panel.
 Click on the box next to the 'Count' property and change the value to '5'. Check that the com-
ponent is connected to 'PORTA'.
Simulating the program
 Click once on the 'Step Into', , button. The 'Simulation Debugger' window appears but ig-
nore it for now.
 Move the cursor over one of the switches and click, to simulate detecting a fire. The switch
graphic toggles to the closed position. Click the ‘Step Into’ button a few more times to simulate
the complete program.
The program is finished, and working!
You have just detected a fire, which turned on a heat sensor.
The LED array tells you, or the fire brigade, which sensor detected the fire.

Page 61
Example 2. Using loops - Counting sheep (badly)

Counting sheep, badly at first, but without falling asleep!
The plan is straightforward - when a sheep passes through the gate, it
breaks a light beam. This sends a pulse to a counting system, which then
adds one to the total stored in the system.
We display this total on the LED array. (The 7-segment display would be a
better output device - that's a later exercise!)
The plan seems straightforward - but there will be problems!
(Note that ‘Flowcode 7’ has a 'Beam Breaker' component, based on the 'Collision Detector'. Alt-
hough this would do a far better job, for now we detect the light beam interruption using more
basic methods.)

 Launch ‘Flowcode 7’ and start a new flowchart.
 Create the flowchart shown opposite. It contains a 'Loop' icon and a 'Calculation' icon which
you have not used before.

We are going to create two variables, one called 'SHEEP' and the other called 'TOTAL'.
 The 'SHEEP' variable will show whether a sheep is present or not.
 The variable 'TOTAL' will store the total number of sheep recorded so far.
 Click 'View' on the menu bar, and ensure that 'Project Explorer' is
checked (View > Project Explorer).
 Click on the 'Globals' button at the top of the Project Explorer pan-
el:
 Hover over 'Variable:' in the project explorer panel and click
on
 Click 'Add new'. You now see the 'Create a New Varia-
ble' dialogue box. Type in the name "SHEEP" and then click on
‘OK’. You can leave the variable type as 'Byte' as there will not be
that many sheep!
 Create a variable named "TOTAL" in the same way.

Page 62
Setting up the calculation

 Double-click on the 'Calculation' icon to open
the 'Properties' dialogue box.
 Change the 'Display name' to "New total".
 Create the calculation by typing the following
in the 'Calculations' window:
TOTAL = TOTAL + SHEEP
 We will simulate breaking the light beam us-
ing a push switch marked 'SW0' on port A bit
0.
 The 'Input' properties are set up to store whatever number appears on port A in the variable
called 'SHEEP'. Initially, that number is '0'. When the switch is pressed, the number on port A
and stored in the variable 'SHEEP' is '1'. (With only one switch, the biggest number we can cre-
ate on port A is 1.)
When the 'Calculation' icon is executed, the number stored in the variable 'SHEEP' is added to
the 'TOTAL' variable. Hence, when a sheep breaks the light beam, 'TOTAL' is increased by 1.
With no sheep present, 'TOTAL' remains unchanged.
 Click on the ‘OK’ button, to close the dialogue box.
Configuring loop properties

 Double-click on the 'Loop' icon to open its 'Properties' dialogue box.
This shows the options for controlling the
loop.
Next to the 'Loop while:' statement is the
loop control text box, where you write the
loop condition - the program continues loop-
ing until this condition is met.
Examples of loop conditions:
 count = 10 (Loop runs as long as
the variable 'count' = 10)
 count > 4 (Loop runs as long as the 'count' is greater than 4)
 count = preset (Loop runs as long as the 'count' is the same as the variable ‘preset’)
In all of these, looping continues as long as the condition in the 'Loop while' text box is 'true'.
In programming 'true' has a special meaning. It is assigned a numerical value of ‘1’ so that a test
can determine if something is ‘true’. Similarly 'false' is assigned the numerical value '0'.
The default condition in the 'Loop while:' text box is '1' - this condition is always 'true' and so
with this value, the loop will run forever. Programs usually contain a ‘loop forever’ structure. If
they do not, the program will end suddenly and the computer will just sit there doing nothing.
When to test?
You can configure the properties to test the loop condition either at the start of the loop or at the
end. Understanding this option is important. It can affect the number of times that the program
will loop.
Loop for a set number of times
Sometimes, you just want to run a loop for a set number of iterations. To do this, check the 'Loop
count:' box and enter the number of loops you want in the associated text box.

Page 63
Setting up the input

 Right-click on the 'Input' icon, and select 'Properties' from
the menu, to see the following dialogue box:
 Change the display name. Double-click on 'Input' in the
'Display name:' box and type "Check the sensor".
 Click on the next to the 'Variable:' box to open the
'Variable Manager'.
 Double-click on the word 'SHEEP' to insert it into the
'Variable:' box.
 By default, the input is port A, which is what we want.
Click on ‘OK’ to close the dialogue box.
Setting up the output

 Double-click on the 'Output' icon to open the output 'Properties' dialogue box.
 Click on the next to the 'Variable:' box.
 Double- click on the word 'TOTAL' to insert it into the 'Variable:' box.
 In the output' Properties' box, change the port used to 'PORTB'.
 Click on 'OK' to close the dialogue box.
The flowchart should now look like this:
Adding the LED array

 Click once on the 'Outputs' box and select the 'LED Array' icon Place it on the System Panel
by moving the cursor over it and then ‘clicking-and-dragging’ it into position.
 Change the value of the 'Count' property to '8' to set the number of LEDs in the array.
 Click the 'Connections' property in the 'Properties' pane. Select 'PORTB' from the drop-down
menu to connect the LEDs to the pins on port B.
 You can change the colour of the LED array in the 'Colors' section.
When the 'Same Color' property is set to 'Yes', you change the colour of the whole LED array to
your selected colour.
When the 'Same Color' property is set to 'No', you can set the colour of each LED individually.

Page 64
Adding the switch

A single push switch will represent the light beam sensor.
 Click once on the 'Inputs' box and select 'Push Round Panel' icon, . Add or drag it onto the
System Panel.
 On the 'Properties' pane 'Connections' section, check that the 'Connection' property for the
switch is '$PORTA.0' i.e. the switch is connected to port A bit 0.
 Click and drag the 'Text' icon from the System Panel toolbar and place it next to the switch.
 Click on the 'Text' property in the 'Properties' pane and replace the default text with "Light
beam interruption".
 To adjust the size of the text, click on the ‘Position’ tab and change the values of ‘Width’ and
‘Height’ under the ‘World size’ section. Move the text to a suitable position next to the switch.
You should now have a project that looks something like this:
Simulating the program

 Now run the simulation by clicking on the Run button
 The 'Simulation debugger' window appears - close it as it is not needed.
 Move the cursor over the switch and give the briefest mouse click you can.
What happens depends on how quickly you click, and how fast the PC works!
We want only the 'B0' LED to light, to show a total of 1 sheep. The program runs at high speed,
however, and so keeps cycling through the 'Input' and 'Calculation' steps. As a result, before you
have time to release the push switch, the total has incremented (increased by one) several times.
This problem is explored in the next section.

Page 65
The solution: Adding a Delay

The problem - the program runs too fast!
Before we have time to release the switch, the program has run through several times, adding one
to the total each time.
We need to slow it down by adding a delay.
 Move the cursor over the 'Delay' icon.
 Drag it onto the main work area and drop it between the Calculation and the Output icons.
The flowchart should now looks like this:
 Double-click on the 'Delay' icon to open the 'Properties'

dialogue box.
 Change the value in the 'Delay value or variable:' box to '200' and then click on the ‘OK’ button.
This causes a 200 millisecond (0.2 second) delay when the 'Delay' icon is activated. In other
words, the system just sits there and does nothing for 0.2 seconds.
 Now run the simulation again. Providing you don't keep it pressed for too long, you should find
that the LED array shows an increase of 1 each time you press the switch.
 The program now works satisfactorily, providing the sheep rush through the light beam in less
than 0.2 seconds. The delay could be increased to allow for slower sheep!
One of the problems with this program is that it shows the total number of sheep in binary format.
That is interesting, but not that useful.
In the next section, you learn that an LCD display can show the total in decimal format.

Page 66
Example 3. The LCD display - Posting messages

Programs using the LCD display need to use the crystal oscillator. If necessary, in ‘Flowcode 7’, se-
lect 'Build' from the main menu, then 'Project Options...' and finally the 'Configure' tab. Select the
crystal oscillator from the list of options (Build > Project Options... > Configure).
LCD displays
‘Flowcode 7’ comes with a number of components that add commonly used subsystems to
‘Flowcode 7’, such as the LCD display, 7-segment display, and analogue inputs devices.
Here, we look at the LCD display, the basic text display subsystem on a
range of electronics devices, from calculators to mobile phones. It can
display text or numbers on one or more rows of the display.
In most programming languages, the LCD is one of the last things you
learn, as it is quite a complicated device to program. However, ‘Flowcode
7’ takes care of the complexities, making the LCD simple to use. The LCD display referred to here is
the one used on the E-Blocks Combo board and on the LCD display - a two row, sixteen character
display.
Adding the LCD component

Before you can use the LCD, you need to add a LCD component to a ‘Flowcode 7’ panel.
To do so, click on the 'Outputs' box, select a LCD component
from the menu and add it to the System Panel. A LCD display
mimic will now appear on the panel.
At the top of the 'Properties' pane, the ‘Component’ section identifies the component you have
just selected. By default, the LCD is added to port B. You could change this, but we will keep it on
port B.
We have now added a LCD display to the program. Is it ready to use? How do we use it?
The LCD display requires five connections. It displays letters
and numbers conveyed as serial data on this five wire bus.
The techniques involved go beyond this tutorial. Fortunately,
‘Flowcode 7’ has some embedded routines that take care of
the complexities.
Drag a 'Component Macro' icon, , onto the flowchart and
open up the corresponding macro dialogue box by double-
clicking on it.
Now scroll through the 'LCD' section in ‘Components’ and se-
lect the macro called 'Start'. This initiates the LCD, clearsthe
display and gets it ready for action. We examine more LCD
macros in the next couple of sections, but for now scroll
through the available macros and take a quick look at each.

Page 67
Writing messages
To display text on the LCD, simply type it in!
 Add another 'Component Macro' to the flowchart and
open the macro dialogue box.
 Select the LCD macro called 'PrintString'. This requires a
single parameter (item of data), 'Text', - the text to be
printed.
 Type the text into the parameter box surrounded by quota-
tion marks, e.g. "Hello World"
 Run the program and the text will be sent to the LCD display.
Other LCD functions

There are a number of other useful functions in the LCD macro list:
'Clear'
Clears the display and resets the cursor position, (where the display prints next,) to '0,0' i.e. top
left.
'Cursor'
Moves the cursor to the specified location. The two parameters, ‘X’ and ‘Y’ select the horizontal
and vertical positions of the cell respectively. ‘0,0’ is the top left cell, ‘0,1’ the first cell on the sec-
ond line, ‘3,2’ the fourth cell on the third line … .
'PrintNumber'
Works like 'PrintString' but prints a number instead of a string.
It can be used with variables, or with actual numbers.

Page 68
Using PrintNumber - an example:

 add a Component Macro icon to a flowchart;
 select 'Cursor' and add 0,1 to the parameters;
 add another 'Component Macro' icon;
 select 'PrintNumber' with the parameter value as '123';
 add a third Component Macro;
 select 'PrintString' and add "Hello World" (with quotation marks) as the parameter;
 click 'Run' to simulate the program.
You should see a result similar to the one shown below:
'PrintASCII' and 'Command'

are more advanced features that you will learn about later. For now ignore them!

Page 69
Example 4. A stopwatch
 Expand your program by dragging a Loop icon below the 'PrintString' Component Macro.
 Change the text in the 'PrintString' Component Macro to "Hundredths:" (with quotation
marks).
 Drag a 'Calculation' icon into the loop.
 Create a variable called 'Count' as an 'Int' type.
 Double-click on the 'Calculation' icon. In the 'Calculations:' text box type "Count = Count + 1".
This will add 1 to the value of variable count every time the icon is executed.
 Next drag another 'Component Macro' into the Loop.
 Double-click the 'Component Macro' and find 'Cursor' under the 'LCD' macros.
 Enter “0,1” as parameters to position the cursor on the first character of the second line.
 Next, drag another 'Component Macro' onto the workspace.
 Select 'PrintNumber' and enter 'Count' as the parameter.
 Now, drag a 'Delay' icon into the flowchart and set the delay to 10ms (which equals one hun-
dredth of a second).
 Refine the program by clicking on each icon and entering comments on the icon does. It may
seem to be a lot of effort, but it saves time later as your program will be easier to follow.
 Run the program. You have now made a counter that will count (approximately) the time
elapsed in hundredths of seconds.

Page 70
Example 5. Using binary numbers - A binary calculator!

In this section you build a binary adder - a system that makes the microcontroller add two num-
bers.
The simplest way to input a binary number is
to use a set of switches attached to the input
port.
To input two numbers, we need two sets of
switches and two input ports.
To see the result of the calculation, we will use
a LED array, connected to the output port.
We need a microcontroller with three ports!

 Launch ‘Flowcode’ and start a new flowchart.
 This time we take notice of this dialogue box:
We need a microcontroller with at least three ports.
Pull the slide bar down to find the 16F1937 PIC.
 Click on it to select it and then click on ‘OK’.
 Click-and-drag a Loop' icon between the 'BEGIN' and 'END' box-
es.
 Click-and-drag an 'Input' icon and drop it between the ends of
the loop.
 Click and drag a second 'Input' icon and drop it in between the
ends of the loop.
 Click and drag an Output icon and drop it just below the 'Input'
boxes.
 Click and drag a Calculation icon, , and place it in between
the second Input icon and the Output icon.
 Your flowchart should now look like this:

Page 71

 Click 'View' on the menu bar and ensure that 'Project Explorer' is
checked (View > Project Explorer).
 Click on the 'Globals' button at the top of the Project Explorer panel.
We are going to create three variables, called ‘input1’, ‘input2’ and
‘sum’. The first two store the numbers fed in from the switches. The
variable 'sum' stores the result of adding them together.
 Hover over 'Variables' in the 'Project Explorer' panel then click on the
that appears.
 Click 'Add new' and the 'Create a New Variable' dialogue box appears.
Type in the name "input1", and click on the ‘OK’ button - leave the varia-
ble type as 'Byte'.
 Create variables, ‘input2’ and ‘sum’ in the same way.
Setting up the inputs

 Right-click on the top 'Input' icon, and select ‘Properties’. The
‘Properties: Input’ dialogue box appears.
 Double-click on the word ‘Input’ in the 'Display name:' box to
highlight it.
 Type "Input the first number" to replace it. This will appear
alongside the 'Input' icon in the flowchart.
(Adding labels like this helps users to understand what is hap-
pening.)
 Click on the next to the variable box to open
the 'Variable Manager'.
This lists the three variables that you just created.
 Double-click on 'input1' to use this variable in the
input box.
 Back in the 'Input Properties' dialogue box, click on
the down arrow at the end of the port window
and select 'PORTB' to replace ‘PORTA’.
 Click on ‘OK’ to close the dialogue box.
 Double-click on the second 'Input' icon, (a quicker
way to open the 'Properties' box.)
 Configure this input to:
 display the label ‘Input the second number’;
 use the variable 'input2';
 use 'PORTC'.
 Then close the dialogue box by clicking the ‘OK’ button .

Page 72
Setting up the calculation

 Double-click on the Calculation icon to open
the Properties dialogue box.
 Change the 'Display name:' to ‘Add the two
numbers together’.
 In the 'Calculations:' box insert:
sum = input1 + input2
(Either type this in directly, or drag in varia-
bles from the right window and then insert
the '=' and '+' signs in the right place!)
 Then click on the ‘OK’ button, to close the dialogue box.
Setting up the output

 Double-click on the 'Output' icon, to open the output
'Properties' dialogue box.
 Click on the next to the 'Variable:' box.
 Double- click on 'sum' to insert it in the box.
 Back at the output 'Properties' dialogue box:
 change the port used to 'PORTD'.
 click on ‘OK’ to close the dialogue box.
 The flowchart should now look like this:
Adding a LED array

 Click on the ‘Outputs’ tab and select 'LED Array'
Place it in the middle of the System Panel by moving the
cursor over the component and then clicking-and-
dragging it into position (or right-clicking it and selecting
'Center all objects').
 Click next to the 'Count' property under the 'Simulation'
section on the Properties pane and change the number of
LEDs to seven.
 Click next to the 'Port' property and select 'PORTD' from
the drop-down menu to connect the LEDs to the pins on
port D.
 Change the colour of the LED array to red (0000FF), by changing the 'LED 0' property while the
'Same Color' property is set to 'Yes'.
Adding the switches

Two sets of switches are used, one for each binary number. The output port has only eight bits.
The biggest number it can output is 1111 1111, (= 255 in decimal). We are going to limit ourselves
to inputting seven bit numbers meaning that the biggest number we can input is 111 1111, (= 127
in decimal). If we used bigger numbers, we would overflow the capacity of the output.
 Click on the 'Inputs' tab, select 'Switch Array' and drag it onto the System Panel above the
LED array.
 Open the 'Properties' pane for the switch array. Connect it to port B, using the next to the
'Port' property to open the drop down menu.
 Add a second 'Switch Array' to the System Panel in the same way. Position it under the 'LED Ar-
ray' and connect it to 'PORTC'.

Page 73
Slow simulation
As described earlier, ‘Flowcode 7’ allows you to progress through the flowchart one step/icon at a
time, to see the effect of each on the variables and on the output.
 There are three ways to simulate the program step-by-step:
 Click on 'Run' on the Main toolbar and on the 'Step Into' button (Run > Step Into).
 Press the F8 function key on the keyboard.
 Click on the 'Step Into' button on the main toolbar in the simulation section.
Do one of these!
 Several things happen:
 a red rectangle appears around the 'BEGIN' icon, showing that this is the current step;
 the 'Simulation debugger' window appears - containing 'Variables' and 'Macro Calls';
 the 'Variables' section lists the three variables that you defined for this program, and
shows their current values - all zero at the moment.
Ignore the 'Macro Calls' section for the moment.
 Now set up two numbers on the switch components.
 Move the cursor over the switch box connected to port B.
 Click on switches B0, B1, and B3, to activate them.
 The switches now look like this:

 You have set up the binary number 000 1011 (= eleven in decimal.)
 (Switch 'B6' gives the most significant bit and 'B0' the least significant bit).
 Set up the number 000 1111 (fifteen) on the switches connected to port C.
 Now ‘Step Into’ to the next icon in the program by, for example, pressing F8 once more.
 The red rectangle moves on to the next icon, the 'Loop' icon, but little else happens.
 Press F8 once again. The red rectangle moves on to the first Input icon.
 Press F8 again and the 'Variables' box shows that the 'input1' variable now contains eleven -
the result of the 'Input' instruction just carried out.
 Press F8 again and the 'Variables' section shows that 'input2' now contains fifteen.
 Press F8 again and the calculation is carried out. The 'sum' variable stores the result.
 Press F8 again. The value stored in 'sum' is transferred to the LEDarray.
It looks like:
Reading from the most significant bit ('D7') to the least significant bit ('D0'), the LED array shows
the number 0001 1010. In decimal, this is the number 26. No surprises there then!
 Repeat the same procedure using different numbers and step through the program to check
what the sum of the numbers is.
The program is finished, and working.

As usual, you could now let ‘Flowcode 7’ translate it into machine code, and burn it into a micro-
controller.

Page 74
Example 6. Binary logic in control!

Electronic systems can make decisions!
Very often, these are of the form "If this AND this is true, then..." or "If this OR this is true, then...".
They rely on specific combinations of circumstances in order to take some particular action.
They are examples of using binary logic. The answer to the “If…” question is either “Yes” / “No”, or
“True” / “False”, i.e. one of two possibilities - a binary situation! This answer could be expressed as
a logic 0 or a logic 1 and electronically by a high voltage or a low voltage.
There is a class of digital electronic components, called logic gates, that perform exactly these deci-
sions. The inputs and output are logic 0 or logic 1.
We can program ‘Flowcode 7’ to make exactly the same decisions. Here are two examples:
A. Controlling the microwave oven:
For reasons of safety, a microwave oven has a door sensor to
make sure that the microwave generator will not operate if the
door is open. Put another way, the generator operates if the door
is closed AND one of the heating control switches is pressed.
We can build this condition into a ‘Flowcode 7’ program.

 Launch ‘Flowcode’ with a new flowchart.
 Create the flowchart shown opposite.
It uses:
 a loop icon,
 two input icons,
 three output icons,
 two decision icons,
 two calculation icons
 and a delay icon.
 Create four variables:
 ‘door’ - to store the state of the door
switch;
 ‘control’ - to store the state of the on/
off control switch;
 ‘output’ - to control whether the micro-
wave switches on or not;
 ‘count’ - to monitor how many times the
1s delay has occurred. Give it an initial
value of ten, so that the microwave ov-
en will operate for nine seconds.
 Use the default configuration for the loop
icon..
 Configure one input icon to store the state of
the door switch (on port A bit 0,) in the varia-
ble ‘door’.

Page 75
 Configure the other input icon to store the state of the control switch (on port A bit 1,) in the
variable ‘control’.
 The upper calculation icon checks to see whether the door AND the control switch have been
pressed.
Configure it using the equation: output = control & door.
The ‘&’ signifies the AND operation. The result of this operation, (‘0’ or ‘1’) is stored in the
variable ‘output’.
 The upper decision icon checks the value stored in ‘output’. (“If output?” is shorthand for “If
output=1?”)
Configure this decision icon.
 When the result of the calculation is ‘0’, the program follows the ‘No’ route from the decision
icon and the left-hand output icon is executed. This sends a logic ‘0’ to the LED, ensuring that it
(and the microwave generator) is switched off. When the result of the calculation is ‘1’, the
program follows the ‘Yes’ route. The ‘Turn on’ output icon sends a logic ‘1’ to the LED turning it
on.
Configure both of these output icons.
 The lower calculation icon reduces the number stored in the variable ‘count’ by one.
Configure it using the equation: count = count - 1.
 The initial value of ‘count’ is ten. Provided the number stored in ‘count’ has not reached zero,
the program follows the ‘No’ route. Eventually, after looping enough times, the number stored
does reduce to zero. The program then follows the ‘Yes’ route and executes the ‘Turn off’
output icon, which is configured in the same way as the other ‘Turn off’ icon, to switch off the
microwave generator.
 Add a switch array to the System Panel. Configure it to have only two switches, one connected
to port A, bit 0 and the other to port A, bit 1.
 Add a LED connected to port B, bit 0 to represent the microwave generator.
 Add labels to the System Panel to identify the components, as shown in the diagram. Position
them using the ‘World coordinates’ under the ‘Position’ tab of the label properties.
 Now simulate the program step-by-step, using the F8 function key repeatedly.
 Check what happens for different combinations of switch states and interpret this in terms of
the behaviour of the microwave oven. What happens, for example, if the door is opened while
the microwave generator is operating?

Page 76
B. Controlling interior light in a car:

The interior ‘courtesy’ (or ‘dome’ light) can be controlled by anoth-
er Boolean logic equation.
For simplicity, consider a two-door car with the following behav-
iour:
The interior light turns on when one door (A) OR the other (B) is
opened and stays on until the ignition switch (C) is turned on.
In Boolean-speak, we say that the light is on if (A OR B) AND NOT C
is true.
Once again, we can build this condition into a ‘Flowcode 7’ program.
 Launch ‘Flowcode’ and start a new
flowchart.
 Create the flowchart shown opposite, us-
ing:
 a loop icon,
 three input icons,
 two output icons,
 a decision icon,
 and a calculation icon.
 Create four variables:
 ‘door_A’ - to store the state of the
switch on door A;
 ‘door_B’ - to store the state of the
switch on door B;
 'ig_switch' - to store the state of the
ignition switch;
 ‘output’ - to control whether the
dome light switches on or not;
 Use the default configuration for the loop
icon..
 Configure one input icon to store the state
of the switch on door A (on port A bit 0,) in
the variable ‘door_A’.
 Configure one input icon to store the state of the switch on door B (on port A bit 1,) in the vari-
able ‘door_B’.
 Configure the other input icon to store the state of the ignition switch (on port A bit 2,) in the
variable ‘ig_switch’.
 The calculation icon checks to see whether either door has been opened AND the ignition
switch is NOT on.
Configure it using the equation: output = (door_A ||door_B) & !ig_switch.
The ‘||’ signifies the OR operation and '!' the NOT operation. The result of the calculation is
stored in the variable ‘output’.

Page 77
 The decision icon checks the value stored in ‘output’.

 Configure this decision icon.
 When the result of the calculation is ‘0’, the program follows the ‘No’ route from the decision
icon and the 'Turn Off' output icon is executed, ensuring that the light is switched off.
 When the result of the calculation is ‘1’, the program follows the ‘Yes’ route. The
‘Turn on’ output icon sends a logic ‘1’ to the LED turning it on.
 Configure both of these output icons.
 Add a switch array to the System Panel. Configure it to have three switches, one connected to
port A, bit 0, one to portA, bit 1 and the other to port A, bit 2.
 Add a LED connected to port B, bit 0 to represent the interior light in the car.
 Add labels to the System Panel to identify the components and position them as shown in the
diagram.
 Now simulate the program step-by-step, using the F8 function key repeatedly.
 Check what happens for different combinations of open doors and ignition switch states. Inter-
pret the behaviour in terms of the behaviour of the interior light. What happens, for example, if
the door is opened and then closed shortly after? Is this behaviour correct?

Page 78
Example 7. The SPI board - Making music!

Digital audio is everywhere - in CDs, Blu-Ray discs, DAB radio, music
streaming…
 It has a number of advantages over analogue audio:
 It can be stored like any other data in electronic memory.
 It can be distributed over computer networks and the internet.
 It can be regenerated to remove noise.
SPI (Serial Peripheral Interface) is a common protocol used to send data
between microcontrollers and peripherals such as LCDs, sensors and SD
cards. In our case, it is used to transfer data between the microcontroller
and the memory and DAC on the SPI board.
The SPI protocol uses a master-slave configuration with a single master (the microcontroller.)
Communication is full duplex (two-way simultaneously).
SPI can involve the following four signals:
 SCLK : Serial Clock (clock signal generated by the master).
 MOSI : Master Output, Slave Input (data output from the master).
 MISO : Master Input, Slave Output (data output from the slave device).
 S̅S̅ : Slave Select (active low,) (output from master in order to specify the target slave device.)
These are transmitted down separate clock, data and control lines.
Stored as digital data, the music is converted to analogue form by the DAC (digital-to-analogue con-
verter) built on the SPI board. It is then amplified and outputted from the headphone socket or
screw terminals (J10).
Hardware setup:
The EB006 Multiprogrammer and EB083 Combo board are connected as usual, using ports A and B.
On the EB083 board, ensure that:
 port A (pin 0 and 1) mode selectors are set to Analogue.
The EB013 SPI board is connected to port C. A positive power supply connection is needed between
the ‘+V’ screw terminal on the SPI board and the same on the EB006 board.
On the EB013 board, ensure that:
 jumper J2 is in the right hand side - ‘AMP’ position;
 jumper J4 selects ‘A’;
 jumper J5 selects 1’.
The pot ‘RV1’ on the SPI board is a hard-wired hardware volume control, independent of the soft-
ware volume control created in the program.
Plug headphones into the ‘Headphones’ socket.
Connect the EB006 Multiprogrammer to a 12V power supply.
Use a USB cable to link it to the computer.

Page 79

 Launch ‘Flowcode’ with a new flowchart.
 Select the PIC16F1937 microcontroller as the target device.
 Create two variables:
 ‘tone’ - to store a value representing the tone of the note generated;
 ‘volume’ - to store a value representing the loudness of the note generated.
As the images below show, ‘tone’ is created as a ‘UInt’ variable with an initial value of 128
and ‘volume’ as a ‘Byte’ variable with an initial value of 127.
 On the Dashboard panel, add:

 the ‘SPI Master (EB013)’ component, from the ‘Comms’ box;
 two ‘Potentiometer (Colour)’ components from the ‘Inputs’ box.
Position them as shown opposite:
The upper ‘pot’ represents the volume control (‘AN1 POT’ on the EB083 Combo board).
The lower one represents the tone control (‘AN0 LDR’ on the EB083 Combo board.)
Click on each, in turn, and select ‘Properties’.
Configure them as shown in the following diagrams:

Page 80
 Add icons to create the flowchart shown below.

Page 81
The steps in the program are:
1. Initialise the SPI:
2. Read the tone control setting:
3. Read the volume control setting:
4. Limit the size of ‘volume’ to a maximum of 127:

(Shifting the binary number stored in ‘volume’ by one
place to the right amounts to dividing it by two.
The biggest value it could have as a ‘byte’ variable is 255.
Moved one place right, this is 127.)
5. Set up a continuous loop, using the default configuration .

6. Check the tone control setting:
7. Delay for a time determined by ‘tone’:

(The heights of the audio wave are sent regularly with a delay
in between that is set by the ‘tone’ variable. The bigger this
value, the longer the time interval between the peak and
trough values of the wave and so the lower the tone.)
8. Send the audio wave peak value:

(This is set as ‘128 + volume’. ‘Volume’ is limited to a
maximum of 127 giving the peak a maximum of 255.)

Page 82
9. Check the volume control setting:
10. Delay for a time determined by ‘tone’ again.

11. Limit the new size of ‘volume’ to a maximum of 127 again.
12. Send the audio wave trough value:
(This is set as ‘128 - volume’. ‘Volume’ is limited to a
maximum of 127 giving the trough a minimum of 1.)
The program loops back to send further peak and trough values, re-creating the audio wave.
 The program is now complete.
Save it and then click on the ‘Compile to Chip’ icon to transfer it to the microcontroller.
 When the transfer is complete, press the ‘Reset’ button on the EB006 Multiprogrammer.
You should hear an audio tone coming through the headphones.
 Turn the ‘pot’ ‘AN1 POT’ on the Combo board and notice the effect. This controls the loudness
of the tone through the software, unlike the ‘pot’ ‘RV1’ on the SPI board which controls volume
through the hardware - because of the circuit configuration.
 Shade the LDR on the Combo board. The tone of the audio signal should change.
 On the ‘Flowcode 7’ screen, click on ‘Data Recorder’ in the ‘View’ menu. You see the following:

Page 83
 On the ‘DEBUG’ menu, click on ‘Ghost’ and then on ‘Enable’.

You should find that ‘Monitor (ICT)’ is enabled.
‘Ghost’ monitors the logic levels on the selected microcontroller pins while the program is
running and displays them on the ‘Data recorder’ display.
 Click on the ‘Run’ icon to simulate the program. You will see the data being transmitted from
the microcontroller to the SPI DAC. The diagram opposite shows typical output.

Page 84
Part 6
Introduction to
Microcontrollers

Page 85
Part 6 Contents
What is a microcontroller? .................................................................................................................... 86

Microcontrollers .................................................................................................................................... 86
The Digital World ................................................................................................................................... 87
The Analogue World .............................................................................................................................. 87
Analogue Data ....................................................................................................................................... 88
Digital Data ............................................................................................................................................ 88
Analogue to Digital Conversion ............................................................................................................. 89
Inputting data into a PIC microcontroller ............................................................................................. 90
Outputting data ..................................................................................................................................... 90
Current Limits ........................................................................................................................................ 91
Storing Data ........................................................................................................................................... 91
Types of Memory .................................................................................................................................. 92
Read Only Memory (ROM) .................................................................................................................... 92
Random Access Memory (RAM) ........................................................................................................... 92
PIC Memory ........................................................................................................................................... 93
Programming ......................................................................................................................................... 93
What is a Program? ............................................................................................................................... 93
The ‘Flowcode 7’ Process ...................................................................................................................... 94
Running the Program ............................................................................................................................ 94
Different types of PIC ............................................................................................................................ 95
PIC16F1937 Architecture ...................................................................................................................... 95
PORT A ................................................................................................................................................... 96
PORT B ................................................................................................................................................... 96
PORT C ................................................................................................................................................... 96
PORT D ................................................................................................................................................... 97
PORT E ................................................................................................................................................... 97
Other subsystems in the 16F1937 PIC .................................................................................................. 97
Memory: ................................................................................................................................................ 97
ALU: ....................................................................................................................................................... 98
Timer 1 (TMR1): ..................................................................................................................................... 98
Timer 0 (TMR0): ..................................................................................................................................... 98
RBO External Interrupt: ......................................................................................................................... 99
PORT B External Interrupt: .................................................................................................................... 99
A/D: ........................................................................................................................................................ 99
Busses: ................................................................................................................................................... 99
Introduction to ‘clocks’ ........................................................................................................................ 100
Clock Settings ....................................................................................................................................... 100
Introduction to E-blocks ...................................................................................................................... 102
E-blocks Projects ................................................................................................................................. 103
Course hardware ................................................................................................................................. 104
EB006 Multiprogrammer ..................................................................................................................... 104
EB083 Combo Board ............................................................................................................................ 105

Page 86
What is a microcontroller?
As its name suggests, microcontrollers are tiny devices used to control other electronic devices.
They are found in a huge range of products:
 automotive - engines, anti-lock brakes, climate control systems… ;
 domestic electronics - TVs, VCR's, digital cameras, mobile phones, printers, microwave ovens,
dishwashers, washing machines... .
So what are these wonderful devices?
A microcontroller is a digital integrated circuit, consisting of:
 central processing unit
 memory
 input ports
 output ports
Microcontrollers
At their heart (or is it brain?) there is a Central Processing Unit (CPU). This processes the digital
signals, does calculations and logic operations, creates time delays, sets up sequences of signals
etc.
How does it know what to do? It is following a program of instructions, stored in part of the
memory, called the 'program memory', inside the PIC.
From time to time, the CPU needs to store data, and then later retrieve it. It uses a different area
of memory, called the 'data memory' to do this.
The clock synchronises the activities of the CPU. It sends a stream of voltage pulses into the CPU
that controls when data is moved around the system and when the instructions in the program
are carried out. The faster the clock, the quicker the microcontroller runs through the program.
Typically, the clock will run at a frequency of 20MHz (twenty million voltage pulses every second.)
To talk to the outside world, the microcontroller has 'ports' that input or output data in the form
of binary numbers. Each port has a number of connections - often referred to as 'bits'. An 8-bit
port handles an 8-bit (or one byte) number.
Information from sensors is fed into the system through the input port(s). The microcontroller
processes this data and uses it to control devices that are connected to the output port(s). The
ports themselves are complex electronic circuits - not simply a bunch of terminals to hang compo-
nents on.
Page 87
The name PIC, (Peripheral Interface Controller), refers to a group of

microcontrollers, produced by Arizona Microchip.
When we use a PIC microcontroller, we have to specify how we want
the ports to behave. The ports are bi-directional, meaning that they
can act as either input ports or output ports. When we write a pro-
gram for the PIC, we start by configuring the ports, telling them wheth-
er they are to behave as input ports or output ports.
The input port can receive data (information) in one of two forms, as an analogue signal, or as a
digital signal. It is important that we understand clearly the difference between these.
The Digital World
Much of our everyday information is described in numerical format.
For example:
 "It is 2 o'clock."
 "The temperature outside is 21 degrees C."
 "The car was travelling at 48 kilometres per hour."
It is easy to understand data in this form.
For example, the table shows how the speed of a car changes over a period of time.
Time in seconds Speed in kilometres per hour

0 0
10 15
20 21
30 25
40 22
50 20
60 16
However, you might wonder what happened at time 35 seconds.

Was the car moving faster or slower than 25 km/h at that moment?
The Analogue World
Now the information is given in the form of an analogy! In other words, we use
something that behaves in a similar way.
For example:
1. The hour glass egg timer:
The greater the time elapsed, the deeper the sand in the bottom of the egg
timer.
2. The mercury-in-glass thermometer
The hotter it gets, the further the mercury moves up the tube.
3. The car speedometer
The higher the speed, the further the pointer moves around the dial.
The problem with analogue data is that you have to do some work to extract it.
For the speedometer, and thermometer, you have to work out where the pointer sits on the scale.
On the other hand, it is easy to judge how the temperature of a body or speed of a car is changing -
watch how quickly the mercury is moving along the tube or how fast the pointer moves round the
dial.

Page 88
Analogue Data
Many electronic sensors provide signals in analogue form. For example, a
microphone provides an electrical 'copy' of a sound wave.
Another - the temperature sensor!
Here is the circuit diagram for one type of temperature sensor.
The output voltage increases when the temperature increases.
It is an analogue signal because the voltage copies the behaviour
of the temperature.
An electrical analogue signal can have any voltage value,
limited only by the power supply used.
In this case, the output of the temperature sensor could,
in theory, go as high as 5V, or as low as 0V.
Over a period of time, the output voltage could change as
shown in the diagram. This is an analogue signal.
Digital Data
A digital signal carries its information in the form of a number. Electronic systems usually employ
the binary number system, which uses only the numbers ‘0’ and ‘1’, coded as voltages. We could
decide on the following code: '0' = 0V, '1' = 5V, for example.
Digital signals, then, have only two possible voltage values, usually the
power supply voltage, or as close to it as the system can get, and 0V.
How can we enter these numbers into an electronic system?
One (very slow) way would be to use a switch (an example of a digital
sensor.) The circuit diagram shows such a digital sensor.
 When the switch is open (not pressed,) the output is 'pulled down' to
0V by the resistor.
This output could represent the binary number '0'.
 With the switch closed (pressed,) the output is connected to the positive supply, 5V in this case.
This could represent the binary number '1'.
(Note - if the positions of the switch and resistor were reversed, pressing the switch would put a
logic 0 signal on the pin etc.)
The following diagram shows a more complex digital signal.
The nine bit binary number represented by the signal is given under the waveform.

Page 89
Analogue to Digital Conversion

Much of our 'real world' data is analogue, but computers (including microcontrollers) can only pro-
cess digital data. Fortunately the microcontrollers often contain a subsystem that can convert in-
formation from analogue format to digital format. This is called an Analogue-to-Digital Converter -
usually shortened to 'ADC' or 'A/D'.
The ADC inside the PIC chip divides the range of possible analogue voltages into equal steps.
The lowest step is given the number ‘0’, and the highest step is given the highest number that the
A/D converter can handle.
This highest number is determined by the resolution of the ADC, which, in turn, depends on num-
ber of 'bits' the internal circuitry of the ADC can handle. The resolution of PIC ADCs is 8, 10 or 12
bit.
For example, if the biggest analogue voltage is 5V, and the PIC has an 8-bit ADC:
 the highest 8-bit number is 1111 1111 (= 255 in decimal);
 the first step is 0000 0000 (= 0 in decimal) ;
 meaning that there are 256 voltage levels;
 so stepping from one level to the next involves a voltage jump of 5V/256, or about 20mV.
When this PIC processes an analogue signal, it first divides it by 20mV, to find out how many steps
the signal includes. This gives the digital equivalent of the analogue signal.
The next graph illustrates this process.
In our example, the converter outputs '0000 0000' for any analogue signal up to 20mV, outputs
'0000 0001' for analogue signals between 20 and 40mV, and so on. The analogue signal shown in
the graph produces an output of '0000 0011'.

Page 90
Inputting data into a PIC microcontroller

The PIC microcontroller is a digital device, but data can be entered in both analogue and digital
forms. Programmers choose whether pins on the PIC are used as analogue inputs, digital inputs or
digital outputs. This flexibility leads to complex labelling.
The diagram shows the pinout for a PIC
16F1937 chip. It has five ports, known as A,
B, C, D and E. The pins on port A are la-
belled RA0 to RA7; pins on port B are la-
belled RB0 to RB7 etc. Ports A, B, C and D
have eight pins but port E has only four.
For example, up to eight digital sensors can
be connected to port A of the 16F1937.
Pin 2 is marked as 'RA0/AN0', meaning
that it can be used as bit 0 of port A
(Register A bit 0) or as ANalogue input 0.
The function of each input / output pin is
determined by setting the contents of in-
ternal registers, called 'data-direction' reg-
isters inside the PIC device.
Pins RA6 and RA7 are also labelled as
‘OSC1’ and ‘OSC2’. They can be connected
to an external oscillator circuit or be used for digital input /output.
Analogue sensors must be attached to the pins labelled with an 'ANx' (ANalogue) label. These,
found on ports A, B and E, can handle analogue signals between V DD (5V) and VSS (Gnd).
Most pins have alternative functions. For example pin 25 is labelled as 'RC6/TX/CK', meaning that it
can be Register C bit 6, or the transmit (TX) pin of the internal serial interface, or the ClocK pin of
the internal serial interface.
Fortunately ‘Flowcode 7’ takes care of the internal settings that dictate pin functionality for you.
Outputting data
The PIC microcontroller is a digital device - we have said that several times already! It outputs a
digital signal. In most cases, we use this to turn something on and off - '0' = 'off' and '1' = '0n', for
example.
Suppose that we set up port B as the output port, (or let ‘Flowcode 7’ do it for us). There are eight
pins on port B, so we can switch eight devices on and off. It is important to plan how we connect
these devices, as otherwise they might work the opposite way round!

Page 91
The diagram shows eight LEDs connected to port B of

a PIC16F84 microcontroller:
 The four red LEDs are connected between the posi-
tive supply rail and the port B pins
For these LEDs, PIC is 'sinking' current.
 The four green LEDs are connected between the
pins and the 0V rail.
For these, PIC is 'sourcing' current.
Each red LED lights up when its pin is at a low voltage,
outputting '0' in other words.
Each green LED lights when its pin is at a high voltage, outputting a '1'.
(There are limits as to how much current the ports can control. Typically, one output pin can man-
age up to 25mA. This is enough to drive LEDs and buzzers directly, but higher-powered devices will
need additional circuitry to interface with the PIC - dealt with later. However, the maximum cur-
rent for the whole port is around 100mA, so not all pins can output 25mA at the same time.)
Current Limits
Maximum current sunk/sourced by any I/O pin 25mA
Maximum current sunk by all ports 200mA
Maximum current sourced by all ports 140mA
Maximum current out of VSS (Gnd) pin 95mA
Maximum current into VDD (5V) pin 70mA
As you have seen, ‘Flowcode 7’ has a simulation mode that allows you to attach LEDs to show the
status of the pins on the microcontroller when they are used as outputs. The LED simulation func-
tion inside ‘Flowcode 7’ assumes that current is sourced from the PIC device - like the green LEDs
in the diagram above.
At some stage, you will need to use the PIC pin specifications in order to use them as digital inputs,
analogue inputs, or as digital outputs. In particular, there are limitations on the output capabilities
of the device. Exceeding these limits, even for a short time, may cause permanent damage to the
PIC.
Fortunately the E-block boards used on this course all have current limiting resistors which protect
the PIC device. When using the prototype or patch boards, however, there is no such protection
and care must be taken not to damage your device.
Storing Data
Electronic sub-systems that store data are known as Address
'memory'. They can store only digital data. Data stored
In decimal In binary
One item of data is stored in one location in the memory. This 0 000 11101001
data could be the correct combination to disarm a burglar
1 001 00100101
alarm, or the target temperature of a car engine block.
2 010 10000101
Each memory location has a unique address, a number used
to identify the particular location. This means that we can 3 011 11001101
draw up a map of the memory, showing what data is held in 4 100 01110100
each location. 5 101 00011011
The decimal version of the address is included to make the 6 110 11110011
table easier to read. 7 111 10000101

Page 92
Electronic systems understand only binary numbers. This very small memory has eight locations.
(Notice that numbering normally starts at ‘0’!) It needs a 3-bit binary number to create unique ad-
dresses for each location. It allows us to store items of data that are eight bits long, (one
'byte' (1B).
Our example memory could be called a 8 x 1B memory. Memory systems used in computers are
much larger. Data is often stored as 32 bit numbers, allowing the use of much larger numbers.
There are many more locations, too. A typical computer memory now has millions of memory loca-
tions!
Types of Memory
There are several types of electronic memory, each with a slightly different job to do.
We can divide them into two main groups, ROM and RAM,:
Read Only Memory (ROM)
These devices are normally only read (i.e. the contents are accessed but not changed ‘written’,)
during the running of a program.
 The contents are not volatile. (The data remains stored even when the power supply is
switched off.)
 They are often used to store the basic programs, known as 'operating systems', needed by com-
puters.
 The group includes:
 PROM (Programmable Read Only Memory),
 EPROM (Erasable Programmable Read Only Memory),
 EEPROM (Electrically Erasable Programmable Read Only Memory)
A PROM is a one-shot device, which arrives blank, ready to receive data. Data can then be 'burned'
into it, but only once. After that it behaves like a ROM chip that can be read many times but not
altered.
With an EPROM, shining ultraviolet light through a window in the top of the chip erases the con-
tents. New data can then be 'burned' into the memory. Some older PIC devices operate in this way.
The EEPROM devices work in a similar way to an EPROM, except that the contents are erased by
sending in a special sequence of electrical signals to selected pins. 'Flash' memory is a form of
EEPROM, widely used as the storage medium in digital cameras, (the memory stick) and in home
video games consoles.
Random Access Memory (RAM)
 RAM allows both read and write operations during the running of a program.
 The contents are volatile and disappear as soon as the power supply is removed.
(The exception is NVRAM, Non-Volatile RAM, where the memory device may include a battery
to retain the contents, or may include an EEPROM chip as part of the memory to store the con-
tents during power loss.)
 They are often used for the temporary storage of data or application programs.

Page 93
PIC Memory
PIC chips have three separate areas of memory:
 program memory (Flash);
 user variable memory (RAM);
 EEPROM.
The names give strong hints as to the purpose of the
areas!
For the eighteen pin PIC16F84 the graphic illustrates
the organisation of the memory:
Program memory is used to store the program!
In most PICs, such as the 16F1937, this uses 'Flash'
technology, meaning that it can be programmed and
cleared many times. Older PIC's use PROM for the
program memory so that many of these can be pro-
grammed only once.
Data memory is used to store data!
Part of this uses RAM and part uses EEPROM.
The EEPROM allows us to preserve important data
even if the power supply to the system is switched
off.
For example, suppose that the PIC is part of a temperature controller that keeps an incubator at a
set temperature. It might make sense to store the target temperature value in EEPROM so that we
do not have to enter it into the system every time we switch the incubator on.
The 16F84 illustrated is a relatively small device. In the 16F1937 there are 8192 words of program
memory (each word has 13-bits), 512 bytes of user RAM and 256 bytes of EEPROM.
Programming
What is a Program?
Microcontrollers are programmable devices. They do exactly what they are told to do by the pro-
gram, and nothing else! A program is a list of instructions, along with any data needed to carry
them out.
Unfortunately, microcontrollers do not understand english. The only thing they understand is num-
bers. There's a problem! We don't speak in numbers, and they don't understand english!
There are two solutions, and both need some form of translator:
 Write the program in english, or something close to it, and then have the result translated into
numbers.
 We can think through the program design in English and then translate it ourselves into a lan-
guage that is similar to numbers, known as 'assembler'. From there, it is a swift and simple step
to convert into the numerical code that the microcontroller understands.
These two extremes are known as programming in a high-level language (something close to eng-
lish) or in a low-level language (assembler).
The first is usually quicker and easier for the programmer, but takes longer to run the program, be-
cause of the need to translate it for the microcontroller.
The second is much slower for the programmer, but ends up running very quickly on the microcon-
troller.
If you think that this sounds very complicated, you are right. It is!

Page 94
Fortunately, ‘Flowcode 7’ works using flowcharts - the easiest, and highest level, of programming
and then takes care of all translation needed.
The ‘Flowcode 7’ Process
'‘Flowcode 7’' offers an easy way to program PIC chips, as you will see. Once the flowchart is de-
signed on-screen, one press of a button causes the software to translate it into numerical code!
‘Flowcode 7’ passes the program through a number of processes before it gets sent into the mi-
crocontroller. The flowchart is processed:
 first into C code,
 then into Assembler,
 and finally into hexadecimal numbers or 'Hex', which the microcontroller 'understands'.
The Hex code is then sent into the microcontroller, using a subsidiary program called 'Mloader'.
When you select Build > Project Options... Configure from the ‘Flowcode 7’ menu, the program
'Mloader' runs. It controls a number of options and configurations by setting the value of registers
inside the device when you download a program.
The Hex code is 'burned' into the microcontroller program memory. Since Flash memory is used to
form the program memory, the program is not lost when the microcontroller is removed from the
programmer. This allows you to use it in a circuit. Equally, use of Flash memory means that you can
reuse the microcontroller and overwrite the program memory with a new program.
Running the Program
As soon as the microcontroller is powered up and is supplied with clock pulses, it will start to run
whatever program is stored in program memory (Flash).
When you press the reset button on the microcontroller programming board, the program restarts
from the beginning.

Page 95
During programming the microcontroller stops while the program is being loaded. When that is
completed, it then restarts and runs the downloaded program.
Different types of PIC
There are a large number of PIC devices available, from the humble 16F84 to larger more complex
PIC's such as the 40 pin 16F1937. Different PIC's have different number of ports, or I/O pins, ana-
logue inputs, larger memory, or advanced serial communications capabilities such as RS232 or SPI
bus.
Deciding on which device to use for a project can be a task in itself. For this course we use a
16F1937 device, a 40 pin PIC that has many internal subsystems (like an A/D converter, and a serial
port).
PIC16F1937 Architecture
As this course uses the 16F1937 PIC, it is important that you un-
derstand a little more about what it does and how to use it. This
section details the pins that are available on the 16F1937 and
the connectors they use on the Multiprogrammer. (The section
on 'Using E-blocks' looks at how these connections are made).
At this point in a traditional programming course, you would be
introduced in some detail to the various internal circuit blocks of
the PIC device. You would need this information to write code
for the PIC in C or assembly code. No need - ‘Flowcode 7’ takes
care of these details!
However, you do need to understand the input and output con-
nections of the PIC, the memory available and the role of the
other subsystems in the PIC.
Ports - The 16F1937 PIC has five ports, labelled ‘A’ to ‘E’,
connected to the rest of the PIC internals by an 8-bit bus system.

Page 96
PORT A
 All eight pins of port A are usable as inputs or
outputs:
 RA0-RA7 can be used as digital inputs;
 RA0-RA7 can be used as digital outputs;
 RA6-RA7 can be used for an external oscil-
lator and so may not be available as I/O;
 AN0-AN4 can be used as analogue inputs
(giving five analogue inputs on port A).
PORT B
 All eight pins of port B are usable as inputs or outputs:
 RB0-RB7 can be used as digital inputs;
 RB0-RB7 can be used as digital outputs;
 an external interrupt pin is possible on RB0;
 an external IOC (Interrupt On Change) is possible on any
of RB0-RB7;
 AN8-AN13 can be used as analogue inputs (giving six ana-
logue inputs on port B).
PORT C
 All eight pins of port C are usable as inputs or out-
puts:
 RC0-RC7 can be used as digital inputs;
 RC0-RC7 can be used as digital outputs;
 PWM (Pulse Width Modulation) is possible
on RC1 and RC2;
 Port C also contains a USART (Universal Syn-
chronous - Asynchronous Receiver Trans-
mitter) and a MSSP (Master Synchronous Se-
rial Port) for serial communication.

Page 97
PORT D
 All eight pins of port D are usable as inputs
or outputs:
 RD0-RD7 can be used as digital in-
puts;
 RD0-RD7 can be used as digital out-
puts.
PORT E
 There are only four pins on port E:
 RE0-RE3 can be used as digital inputs;
 RE0-RE2 can be used as digital outputs;
 RE3 can only be an input; (When used
as the MCLR pin (i.e. reset) it may not
be available as an input.)
 AN5-AN7 can be used as analogue in-
puts (giving three analogue inputs on
port E).
Other subsystems in the 16F1937 PIC
Memory:
 Flash
 Flash memory is used to store the pro-
gram you write.
 This program is 'compiled' by the com-
puter to binary code and then downloaded into the Flash memory of the PIC.
 You can read from, and write to it and it is retained, even after a power cut.
 The Flash memory contained in the 16F1937 can store up to 8192 program commands.
 RAM
 Data from inputs, outputs, analogue inputs, calculations etc. is typically stored in
‘variables’ (values in the program that alter as it runs). RAM is where these are stored.
 This memory is erased every time the power gets cut or a reset occurs.
 It also contains system 'registers' which control and report the status of the device.
 The RAM memory in the 16F1937 can store up to 512 bytes of data.
 EEPROM
 EEPROM is where data can be permanently stored
 This memory is of the PROM-type - preserved every time the power cuts or a reset oc-
curs.
 The EEPROM of the 16F1937 can store up to 256 bytes of data.

Page 98
ALU:
 The ALU (Arithmetic Logic Unit) is at the heart of the PIC’s data processing.
 All data passes through this unit.
 The program in the Flash memory tells the ALU what to do.
 The ALU can send data to, and fetch data from all the separate blocks and ports in the PIC using
the 8-bit wide data-bus.
 The ALU needs four external oscillator clock pulses to execute one whole instruction.
 How the ALU works is very complicated. Fortunately ‘Flowcode 7’ programmers do not need to
know how it works.
Timer 1 (TMR1):
 This timer interrupt is used to provide the PIC with exact timing information.
 It is ‘clocked’ either by the system clock or by an external clock on pin RC0.
 Either clock can be divided by 1, 2, 4 or 8 by configuring the Prescaler of TMR1 in ‘Flowcode 7’.
The resulting output triggers TMR1 and increments the TMR1 register.
 TMR1 is a 16-bit register, which ‘overflows’ when it reaches ‘65536’.
 At the instant it overflows, it generates an interrupt and the TMR1 register is reset to ‘0’.
 This TMR1 Interrupt stops the main program immediately and makes it jump to the TMR1 mac-
ro.
 After this finishes, the main program continues from where it left off just before the interrupt.
For example:
External clock oscillator frequency (crystal oscillator) 19 660 800 Hz
System Clock (four clock pulses per instruction) 4 915 200 Hz
Set prescaler to ‘8’ (divides by 8) 614 400 Hz
Overflow frequency when TMR1 = ‘65536’ 9.375 Hz
Result: TMR1 interrupts the main program and execute the TMR1 macro 9.375 times per second.
Timer 0 (TMR0):
 This timer interrupt also provides the PIC with exact timing information.
 It is ‘clocked’ either by the system clock or by an external clock on pin RA4.
 This system clock runs exactly four times slower than the external oscillator clock.
 Either clock can be divided by 1, 2, 4 or 8, 16, 32, 64, 128, or 256 by configuring the Prescaler of
TMR0 in ‘Flowcode 7’. The result triggers TMR0 and increment the TMR0 register.
 This TMR0 register is an 8-bit register, which overflows when it reaches 256.
 At the instant it overflows, it generates an interrupt and the TMR0 register is reset to 0.
 A TMR0 Interrupt stops the main program immediately and makes it jump to the TMR0 macro.
 After this finishes, the main program continues from where it left off just before the interrupt.
For example:
External clock oscillator frequency (crystal oscillator) 19 660 800 Hz

System Clock (4 clock pulses per instruction) 4 915 200 Hz
Set prescaler to 256 (divides by 256) 19 200 Hz
Overflow when TMR0 = 256 75 Hz
Result: TMR0 interrupts the main program and execute the TMR0 macro 75 times per second.

Page 99
RBO External Interrupt:

 A logic level change on pin RB0 can be configured to generate an interrupt.
 It can be configured in ‘Flowcode 7’ to react to a rising or to a falling edge on RB0.
 If set to react to a rising edge, when one occurs:
 it immediately stops the main program;
 the RB0 related macro is executed;
 then the main program continues from where it left off just before the interrupt.
This happens every time a rising edge is detected at pin RB0.
PORT B External Interrupt:
 A logic level change on any combination of pins on port B can generate an interrupt.
 This can be configured to occur on a rising or a falling edge, or both.
 When one of these interrupts occurs:
 it immediately stops the main program;
 the port B related macro is executed;
 then the main program continues from where it left off just before the interrupt.
This happens every time a level change is detected on one of the pins selected on port B.
A/D:
 The 16F1937 PIC has fourteen pins that have an extra A/D function.
 It has only one 10-bit A/D converter.
 This implies that these fourteen analogue inputs can't all be read at the same time.
 A built-in analogue switch, configured in ‘Flowcode 7’, selects which inputs are sampled.
 After the 'sample' instruction, the analogue switch points to the correct input and this is
converted into a 10-bit binary value.
 In ‘Flowcode 7’, you can opt to use only the eight most-significant bits (MSB's) of this 10-bit
value, by using the 'GetByte' instruction, or to use the full ten bits by using the 'GetInt'
instruction. The ten bits will fill up the ten least-significant bits (LSB's) of the selected 16-bit
integer variable.
 After this, the program can select to read another analogue input.
Busses:
 A PIC microcontroller uses Harvard architecture.
 This means that there are separate busses for instructions and for data.
 The data bus is 8-bits wide and connects every block and port together.
 The instruction bus is 14-bits wide and transports instructions, which are 14-bits long, from the
program memory to the ALU.

Page 100
Introduction to ‘clocks’
Every microcontroller needs a clock signal to operate. Internally, the clock signal controls the speed
of operation and synchronises the operation of the various internal hardware blocks.
In general, microcontrollers can be ‘clocked’ in several ways, using:
 an external crystal oscillator;
 ‘RC’ mode, where the clock frequency depends on an external resistor and capacitor;
 an internal oscillator.
The ‘RC’ mode exists partly historical and partly for reasons of economics. It was introduced as a
low cost alternative to a crystal oscillator. It is fine for applications that are not timing critical, but is
not available on the E-blocks Multiprogrammer used in this course.
The Multiprogrammer uses an external crystal oscillator, with a frequency of 19.660800MHz.
Why such a precise number?
The reason is that this frequency can be reduced, by a sequence of binary counters, to a standard
Baud rate to facilitate communication between systems, using protocols such as RS232.
In this case the fundamental clock frequency divided by 2 to the power of 10 is 19200Hz, an
internationally recognised standard serial communication Baud rate.
Mathematically:
19660800 / 210 = 19200
Clock Settings
When ‘Flowcode 7’ downloads a program to the microcontroller, it changes internal clock settings
and circuitry to mirror the external clock circuit on the Multiprogrammer board, as specified by the
programmer.
This is done by selecting ‘Build > Project Options...’ from the ‘Flowcode 7’ menu, giving this screen:

Page 101
If the target microcontroller is not 'PIC16F1937' then click on the 'Choose a Target' tab.
Click on the ‘Configure’ tab.

This screen allows you to choose between a variety of oscillator configurations.
Select ‘OK’.
Experienced users may wish to change some of the advanced settings on the chip. All this is done
from the screen shown above.

Page 102
Introduction to E-blocks
E-blocks are small circuit boards that can be snapped together to form an electronic system.
There are two kinds of E-blocks:
 Upstream boards
'Upstream' is a computing term indicating a board that controls the flow of information in a
system. They are usually programmed in some way.
Any device which contains 'intelligence' and can dictate the direction of flow of information on
the bus can be thought of as an 'upstream' device.
Examples include microcontroller boards, and Programmable Logic Device boards.
 Downstream boards
‘Downstream’ boards are controlled by an ‘upstream’ board, but information can flow into or
out of them.
Examples include LED boards, RS232 boards etc.

Page 103
E-blocks Projects
‘Upstream’ and ‘downstream’ boards can be snapped together
to form complete electronic systems, like this fully working
mobile phone.
E-blocks are compatible with a wide range of sensors and
accessories, enabling you to build a wide variety of systems.
Here are some other examples:

 an ElectroCardioGram (ECG) system to show heart rate waveforms on a PC.
It consists of:
 a PIC Multiprogrammer,
 a sensor board fitted with an ECG sensor,
 an LCD display,
 a keypad,
 an RS232 board (to facilitate communication
with the PC).
 This is an electronic bug using mobile phone

technology.
A small patch board contains a microphone and
amplifier feeding into a Sony GSM module with SIM
card.
The PIC Multiprogrammer detects an incoming call
and then channels local sound to the incoming
caller who can then hear what is going on in the
room.
The keypad and LCD allow various configurations,
with ‘dial-out’ at pre-determined times.

Page 104
Course hardware
The two main boards for this course are the EB006 Multiprogrammer and the EB083 Combo board,
described below.
EB006 Multiprogrammer
 The board has five ports, labelled ‘A’ to ‘E ‘.
 Ports ‘B’, ‘C’ and ‘D’ offer full 8-bit functionality.
 Port ‘A’ has 6-bit functionality, (8-bit if the internal oscillator is
selected).
 Port ‘E’ has 3-bit functionality.
 It can be powered from an external power supply, delivering
7.5V to 9V or from a USB supply.
 As pointed out elsewhere, no 5V connection is provided in
the D-type connector. This must be provided by an additional
connection to ‘downstream’ boards, using the screw
terminals on the Multiprogrammer board. The ground
connection is provided through pin 9 of the D-type connector.
IMPORTANT - DO NOT connect the 14V screw terminal to a 5V ‘downstream’ screw terminal.
 If the Reset switch is pressed, the program stored in the PIC microcontroller will restart.
 There is a 1:1 mapping between pins on the D-type connector and those on the ports, (e.g. Pin1
is connected to PB0, Pin 2 to PB1 etc.)
 The board is USB programmable via a programming chip. This takes care of communication
between ‘Flowcode 7’’ and the PIC microcontroller.
 The PIC microcontroller executes one instruction for every four clock pulses it receives.
 (Note - a single instruction is NOT the same as a single ‘Flowcode 7’ symbol, which is compiled
into C and then into Assembly and probably results in a number of instructions.)
 This course uses a 19,660,800Hz crystal. The advantages of this frequency include:
 standard Baud rate (19200) is obtainable by dividing it by 1024;
 it can be further divided by 256 to give 75 Hz.
 Jumpers allow the user to select a number of options:
 external power supply or USB power supply;
 where the PIC uses an internal oscillator, all eight bits of port A can be used for I/O
operation;
 use of an professional ICD2 (In-Circuit Debugger) tool from Microchip.

Page 105
EB083 Combo Board

The board combines together on one compact board the
functionality found on a number of individual E-blocks boards:
 EB004 LED board (x2);
 EB005 LCD board;
 EB007 Switch board (x2);
 EB008 Quad 7-segment Display board.
 For this course, the D-type connectors attach to female
connectors on ports A and B of the Multiprogrammer.
 The board provides a set of eight switches and eight LEDs for
port A and the same for port B.
 With J14 links in the ‘Digital’ position, port A is routed to its
push switches (SA0 to SA7), to LEDs (LA0 to LA7) and to the quad 7-segment display.
 With J14 links in the ‘Analogue’ position, port A is switched to the analogue sensor section of
the board, so that pin RA0 is connected to the on-board light sensor and pin RA1 is connected
to the potentiometer to give a variable output voltage, (simulating the action of an analogue
sensing subsystem).
 (With these links in this position, the on-board switches and LEDs LA0 and LA1 will not
operate.)
 Port B I/O pins are routed to its push switches (SB0 to SB7), to the LEDs (LB0 to LB7), to the
quad 7-segment displays and to the LCD display.
 The quad 7-segment display is turned on by switch S3. It is connected to both port A and B.
 Port B is used to control the LED segments and the decimal point).
 Port A, bits 0 to 3, select which display is activated.
 The LCD is a 16 character x 2 lines module, turned on by switch S5. Normally a complex device
to program, ‘Flowcode 7’ takes care of the complexities, unseen by the user.

Page 106
Part 7
Course Rationale

Page 107
Part 7 Contents
About this Course ................................................................................................................................... 108

Aim: ........................................................................................................................................................ 108
What you will need: ............................................................................................................................... 108
Course Conventions ........................................................................................................................... 109
Learning Objectives ................................................................................................................................ 110
Mapping to BTEC Level 3 National Extended Diploma in Engineering - Unit 6 ..................................... 112

Page 108
About this Course

Aim:
The aim of this course is to introduce you to the concepts of developing electronic systems using
microcontrollers.
In doing so, it offers substantial coverage of Unit 6 of the BTEC Level 3 National Extended Diploma
in Engineering . The precise mapping of the course to this unit is given in later pages.
On completing this course you will have learned:
 what a microcontroller is;
 how to construct circuits and systems based on microcontrollers;
 how to program microcontrollers.
What you will need:
To complete this course you will need the following equipment:
 ‘Flowcode 7’ software
 E-blocks including:
 EB006 Multiprogrammer
 EB083 Combo board
 EB013 SPI board
 EB014 Keypad board
 EB016 Prototype board
 EB038 Relay board
 EB090 Sensor Motherboard
 EBM003 Thermistor sensor module
 EBM004 Digital temperature sensor module
 EBM016 Humidity sensor module
 EBM019 Ultrasonic distance sensor module
 EBM020 Infrared sensor module
 HPACT Actuator training panel
 EB634 IDC cable
 HP2666 Power supply
Time: It will take you around 60 hours to undertake all of the worksheets on this course.

Page 109
Course Conventions
The following abbreviations are used in the course:
Abbreviation Meaning
ADC Analogue to Digital Converter
ALU Arithmetic Logic Unit
ASCII American Standard Code for Information Interchange
CPU Central Processing Unit
EEPROM Electrically Erasable Programmable Read Only Memory
EPROM Erasable Programmable Read Only Memory
GND ground
Hex hexadecimal
IDC Insulation Displacement Connector
I/O Input / Output
ISP In-System Programming
JPEG Joint Picture Expert Group (standard for images)
LCD Liquid Crystal Display
LED Light Emitting Diode
LVP Low Voltage Programming
LDR Light Dependent Resistor
LSB Least Significant Bit
MSB Most Significant Bit
NVRAM Non-Volatile Random Access Memory
PIC Peripheral Interface Controller
PROM Programmable Read Only Memory
PSU Power Supply Unit
RAM Random Access Memory
RV1 Resistor-Variable 1
SPI Serial Programmable Interface
XTAL crystal
ZIF Zero Insertion Force
+V positive supply voltage
The following conventions are used:

 Matrix products are capitalised on the first word.
For example: Multiprogrammer, Prototype board, ‘Flowcode 7’.
 ‘Flowcode 7’ menu instructions are presented as:
File > Open
 Abbreviations are spelled out in full the first time they are mentioned:
EPROM (Electrically Programmable Read Only Memory)
 Single quotes are used when a string from a dialogue box is mentioned in the text:
Change the value in the 'Delay value or variable' text box.
 European circuit symbols are used throughout the course.

Page 110
Learning Objectives
After completing this course, you will be able to:
 to send different 8-bit codes to port B of the microcontroller;
 to change the logic level of a one single pin of port B;
 to configure an output icon;
 to use binary code;
 to use LED’s to display an output;
 to compile a program to the PIC.
 to add a delay to slow down execution of a program;
 to change the delay interval;
 to configure a delay icon;
 to control the speed of a microcontroller;
 to use an oscilloscope to time events .
 to use Connection Points to introduce unconditional branching in a program;
 to introduce PWM as a means of controlling the brightness of LEDs.
 to create an infinite loop;
 to create and use a variable;
 to configure a calculation icon to perform arithmetic and logic calculations.
 to create and manipulate variables;
 to perform calculations;
 to use LEDs with current limiting resistors;
 to create and use a ‘running light’ program, using the ‘multiply-by-two’ method;
 to create and use a ‘running light’ program, using the ‘shift-right’ method;
 to create and populate an array;
 to create a conditional loop;
 to input data from switches;
 to use loops to create LED sequences;
 to configure an input icon;
 to configure Decision icons and hence add conditional branching to a program;
 to control the frequency at which LEDs flash;
 to use LEDs to display output logic levels;
 to use temporary memory;
 to create, populate and manipulate string variables;
 to control the display of text and numbers on a LCD;
 to use a LCD as an output device for the PIC;
 to configure a Component macro for the LCD;
 to input text and numbers from a keypad and display messages on the LCD;
 to use ASCII code to transmit this data;
 to use multiplexed inputs;

Page 111
 to configure a Component macro for the keypad;

 to create data loggers, using 8-bit and 10-bit data from the ADC;
 to configure an analogue input;
 to enter data via switches;
 to enter information from light and temperature sensors;
 to configure and use the EEPROM;
 to scroll through EEPROM data;
 to display text and numerical data on the LCD;
 to use the E-blocks prototype board.
 to use software macros to simplify the structure of a program;
 to create software macros;
 to use closed loop control;
 to use PWM to control the brightness of LEDs.
 to create and use ‘single-pin’ interrupts;
 to create and use ‘interrupt-on-change’ (IOC) interrupts;
 to use real time operation of a PIC;
 to create and use timer interrupts;
 to use the prescaler to create accurate time intervals;
 to trigger the timer using the crystal or an external event;

Mapping to BTEC Level 3 National Extended Diploma in Engineering - Unit 6 Page 112
A Investigate typical microcontroller system hardware Covered?
A1 Control hardware
I/O capabilities – number, type (analogue/digital), ports 
hardware specification – bus width, processor speed 
memory – RAM, ROM 
hardware features - interrupts, PWM 
- stack 
required peripherals 
cost and accessibility 
ease of use 
software and programming language 
operating voltages and power requirements 
A2 Input devices
User input:
digital – switches and buttons 
analogue – control potentiometer 
Temperature
thermistor 
temperature sensors 
environmental sensor – temperature and humidity 
Light
light-dependent resistor (LDR) 
IR – phototransistor, photodiode or IR receiver 
Movement/orientation
tilt switch 
Presence
micro-switch 
ultrasonic 
Input interfacing requirements
signal conditioning 
analogue-to-digital (ADC) conversion 
modular sensor boards 
PWM 
serial communications 
Inter-Integrated Circuit (I2C) 
A3 Output devices
Optoelectronic
light-emitting diode (LED) – indicator and IR 
7-segment display 
liquid crystal display (LCD) 
Electromechanical
relay 
direct current motor 
servo 
Audio
buzzer or siren 
speaker or piezo transducer 
Output interfacing requirements
power requirements and drivers 
transistor output stage 
relay 
PWM 
serial communications 
I2C device interfacing 
A4 Selecting hardware devices and system design
A5 Assembling and operating a microcontroller system

Page 113
B Programming Techniques and Coding
B1 Programming techniques
Use of a programming development environment
software operation 
connecting to microcontroller hardware 
creating and managing program files 
syntax/error checking 
simulation 
compiling, downloading and live testing 
monitoring/debugging 
safe use of computer and display 
Coding practices:
device set-up and program initiation
introductory comments 
chip set-up 
pin modes 
Libraries 
Declarations 
efficient/effective code authoring 
code syntax 
in-line commenting 
code organisation and structure 
B2 Coding constructs
Input/output
digital – bit and port level read/write 
analogue read/write, resolution, calibration 
tone and sound generation 
pulse and PWM 
communication, including serial and I2C 
Program flow and control:
calling libraries 
subroutines and functions 
control structure sequence iteration 
– if, else, switch, case, for, do, while, until and end
delays and timing 
Interrupts 
Logic and arithmetic
variables – data types (Boolean, 
character, byte, integer, word, float, long, double, string)
arrays 
comparative operators: 
=, not =, <, >, < or =, > or =.
Boolean operators – AND, OR, NOT 
logic using input condition 
– digital and analogue
arithmetic operations 
B3 Structured program design

pseudo code 
flowchart 
decision table 
B3 Number systems
bits, bytes 
parallel and serial 
binary to decimal conversion 
Page 114
C System development cycle Project
C1 Development processes Project

Stages of the development process.
C2 Documentation Project
A portfolio of evidence produced
throughout the development process.
Key
Symbol Meaning
 Content covered by the course
 Content partly covered by the course
 Content not covered by the course
Project Content addressed through project work

Page 115
Version control
Version Author Date Changes
1.0 JV 28/10/2016 Document creation

Matrix Technology Solutions Ltd.
33 Gibbet Street
Halifax
HX1 5BA
t: +44 (0) 1422 252380

e: sales@matrixtsl.com
www.matrixtsl.com
CP4375

Microcontroller Compete Course

Uploaded by

Copyright:

Available Formats

Microcontroller Compete Course

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Microcontroller Compete Course

Uploaded by

Copyright:

Available Formats

What are the main sections covered in the course?

What are the main sections covered in the course?

What hardware is required for the exercises?

What hardware is required for the exercises?

Page 2

Welcome to the course!

Part 1 - Programming Exercises - p.4

Your route through it:

The experienced programmer:

The less confident user:

Copyright © 2016 Matrix Technology Solutions Limited www.matrixtsl.com

Before you start:

For more information:

Copyright © 2016 Matrix Technology Solutions Limited www.matrixtsl.com

Copyright © 2016 Matrix Technology Solutions Limited www.matrixtsl.com

Copyright © 2016 Matrix Technology Solutions Limited www.matrixtsl.com

Programming Exercises for you to try:

Copyright © 2016 Matrix Technology Solutions Limited www.matrixtsl.com

Hardware jumper settings:

Flowcode 7 and download settings:

Copyright © 2016 Matrix Technology Solutions Limited www.matrixtsl.com

Copyright © 2016 Matrix Technology Solutions Limited www.matrixtsl.com

Copyright © 2016 Matrix Technology Solutions Limited www.matrixtsl.com

Using Connection Points

Copyright © 2016 Matrix Technology Solutions Limited www.matrixtsl.com

Copyright © 2016 Matrix Technology Solutions Limited www.matrixtsl.com

Copyright © 2016 Matrix Technology Solutions Limited www.matrixtsl.com

Copyright © 2016 Matrix Technology Solutions Limited www.matrixtsl.com

Copyright © 2016 Matrix Technology Solutions Limited www.matrixtsl.com

Copyright © 2016 Matrix Technology Solutions Limited www.matrixtsl.com

Copyright © 2016 Matrix Technology Solutions Limited www.matrixtsl.com

Copyright © 2016 Matrix Technology Solutions Limited www.matrixtsl.com

Copyright © 2016 Matrix Technology Solutions Limited www.matrixtsl.com

Using the Keypad

Copyright © 2016 Matrix Technology Solutions Limited www.matrixtsl.com

Using the Keypad

Copyright © 2016 Matrix Technology Solutions Limited www.matrixtsl.com

Analogue Inputs and the EEPROM

Copyright © 2016 Matrix Technology Solutions Limited www.matrixtsl.com

Analogue Inputs and the EEPROM

Copyright © 2016 Matrix Technology Solutions Limited www.matrixtsl.com

Using Software Macros

Copyright © 2016 Matrix Technology Solutions Limited www.matrixtsl.com

Using External Interrupts

Copyright © 2016 Matrix Technology Solutions Limited www.matrixtsl.com

Using External Interrupts

Copyright © 2016 Matrix Technology Solutions Limited www.matrixtsl.com

Using Timer Interrupts

Copyright © 2016 Matrix Technology Solutions Limited www.matrixtsl.com

Using Timer Interrupts

Copyright © 2016 Matrix Technology Solutions Limited www.matrixtsl.com

Copyright © 2016 Matrix Technology Solutions Limited www.matrixtsl.com

Copyright © 2016 Matrix Technology Solutions Limited www.matrixtsl.com

How E-blocks connect to each other ....................................................................................................... 31

Copyright © 2016 Matrix Technology Solutions Limited www.matrixtsl.com

How E-blocks connect to each other

Copyright © 2016 Matrix Technology Solutions Limited www.matrixtsl.com

Using E-blocks on the bench

Copyright © 2016 Matrix Technology Solutions Limited www.matrixtsl.com

These covers are mounted onto E-blocks