Flowcode Help - User contributions [en]

Sidebar: Panel Exercises

2013-09-01T14:00:59Z

JohnVerrill:

*Flowcode Wiki
**Main Page|Main page
**portal-url|portal
**randompage-url|randompage
**helppage|helppage
*SEARCH
*Panel Exercises
**Exercises | Exercises
**Exercise - System Panel - Adding Objects | Adding Objects to the System Panel
**Exercise - System Panel - Controlling Shapes | Controlling Shapes on the System Panel
**Exercise - Dashboard Panel - Adding Objects | Adding Objects to the Dashboard Panel
**Exercise - Dashboard and System Panel - Controlling Multiple Objects | Controlling Multiple Objects
**Exercise - System Panel - Controlling Collisions | Controlling Collisions on the System Panel
*TOOLBOX
*LANGUAGES

[[Category:Sidebar]]

Exercise - Importing and Testing the Traffic Cone

2013-09-01T14:00:00Z

JohnVerrill:

<sidebar>Sidebar: Component Exercises</sidebar>
[[File:gen_exercisetestconeimport_macroprops_01.png|300px|right]]
* [[Creating Flowcharts|Create a new flowchart]].

* The following assumes that you have built, and exported a traffic cone component, as described in [[Exercise - Building a Complex Component|Building a Complex Component - a traffic cone]] and [[Exercise - Exporting the Traffic Cone Component|exporting the traffic cone]].

* Open the 'Misc' toolbox, and locate the exported 'traffic cone' component.

* Use the down-arrow next to it to add it to the [[System Panel]].

* Create a flowchart to test the imported component:

:* Add a component macro to the flowchart, and double-click on it.

:* Click on the 'Simulation' tab, and then on the 'flash' macro that appears in the macro list.

:* Then click on 'OK'.

* Your flowchart should now resemble the one shown below:
[[File:gen_exercisetestconeimport_flowchart_01.png|200px|center]]

* Simulate the flowchart, (see [[Exercise - Simulating a Program]]), to test whether the import has worked.

==Link==
To download the Flowcode program for this exercise, click on the following link [[File:xxx|xxx]]

Exercise - Building a Complex Component

2013-09-01T13:59:28Z

JohnVerrill:

<sidebar>Sidebar: Component Exercises</sidebar>
This exercise shows how to create a traffic cone with a double flashing lamp, using the 'newLED' component.
The settings and dimensions given are found by trial-and-error, or by using the cursor and cursor position settings shown at the bottom of the [[System Panel]].

==Setting up the LED component==
* [[Creating Flowcharts|Open a new Flowcode flowchart]].

* Ensure that the [[System Panel]] is visible. If not use the [[View]] menu.

* The following assumes that you have built, and exported a LED component, as described in [[Exercise - Create an LED Component]] and [[Exercise - Exporting the LED Component]].
[[File:gen_exerciseBuildComplexComp_complex1.png|180px|right]]
* Open the 'Outputs' toolbox, where you stored the exported 'newLED' component.

* Locate the 'newLED' component, and use the down-arrow next to it to add it to the [[System Panel]].

* Click on the LED to select it. Change the 'color' property to orange (e.g. 0x0080FF).

* Using the Panel Properties, with the LED still selected, set its 'Position' to X=0, Y=0, Z=10, and its 'Scale' to 'Wi...'=1, 'He...'=1, 'De...'=0.25.
: The component should resemble the picture opposite, (depending on the 'camera' zoom.)

==Adding the second LED==
[[File:gen_exerciseBuildComplexComp_complex2_01.png|180px|right]]
* Click on the head of the vertical arrow, (green), to rotate the camera to give an 'edge-on' view.

* The LED should still be selected. If not, click on it. Right-click and select the 'Copy' option. Then right-click and select the 'Paste' option.
: A second identical LED appears.

* Set its 'Position' co-ordinates to X=0, Y=0, Z=-10, and the 'Rotation' settings to X=0, Y=180, Z=0.
: The System panel should now resemble the one shown opposite:

==Mounting the LEDs==
[[File:gen_exerciseBuildComplexComp_complex3_01.png|180px|right]]
* Drag and drop a cube onto the System Panel.

* Select it, and set its 'Position' co-ordinates to X=0, Y=0, Z=0, and 'Scale' to 'Wi...'=32, 'He...'=12, 'De...'=32.

* Change its 'color' property to mid-grey (e.g. 0x5A5A5A).

: The System Panel looks like the one opposite:

==Building the traffic cone==
* Drag across all three shapes and group them by clicking on the 'Group' icon.[[File:Gen_Panel_Object_Group_01.png|border]]
* Notice that the 'Component Handle' and 'Type' have changed to 'Group'. Rename the 'Handle' as "flasher".

* Click on the head of the vertical arrow, (blue), to rotate the camera back to the 'head-on' view.

* Drag and drop a cone onto System Panel.

* Select it, and set its 'Position' co-ordinates to X=0, Y=-12, Z=0, 'Scale' to 'Wi...'=45, 'He...'=45, 'De...'=120 and 'Rotation' to X=-90, Y=0, Z=0.

* Change its 'color' to red (e.g. 0x0000C0).

* View it from different 'camera' directions by clicking on the heads of the red, green and blue arrows. It should resemble the picture shown below:

<gallery widths=180px perrow=3 caption="Three views">
File:gen_exerciseBuildComplexComp_complex4_01.png
File:gen_exerciseBuildComplexComp_complex5_01.png
File:gen_exerciseBuildComplexComp_complex6_01.png
</gallery>

* Revert to the original (left-hand side) view.

* Drag and drop a cylinder onto the System Panel.

* Give it the following settings:
:: 'Position' - X=0, Y=-75, Z=0;
:: 'Scale' -'Wi...'=60, 'He...'=60, 'De...'=10;
:: 'Rotation' - X=-90, Y=0, Z=0.

* Change its 'color' to dark red (e.g. 0x000080).

==The completed traffic cone==
* Drag across all three shapes and group them by clicking on the 'Group' icon.

::::: The System Panel now looks like this:[[File:gen_exerciseBuilbComplexComp_complex7_01.png|middle|180px]]

==Adding an interface==
The next task is to make the cone do something - flash on and off.

* Click on 'Macro' and then 'New' to create a new macro.
* In the 'Create a New Macro dialogue box, name the new macro "flash" and click on 'OK'.
* On the 'flash' macro workspace:
:* add an infinite loop, and inside the loop:
::* drag and drop a 'Simulation macro' icon;
:::* double click on it. Rename it "Switch on". Click on the 'Simulation' tab, and on one of the 'LEDon' labels and click on 'OK'.
::* drag and drop a 'Delay' icon.
:::* double click on it. Change its name to "One second delay". Change the units to 'seconds' and click on 'OK'.
::* drag and drop a second 'Simulation macro' icon;
:::* double click on it. Rename it "Switch off". Click on the 'Simulation' tab, and on one of the 'LEDoff' labels and click on 'OK'.
::* drag and drop a second 'Delay' icon, and configure it exactly as before.

 
The 'flash' flowchart now resembles the one shown below:

[[File:Gen exercisetest LEDimport testflowchart.png|200px|center]][[File:gen_exerciseBuildComplexComp_flashmacro_01.png|250px|right]]
 
 
 
* In the 'Main' part of the flowchart, drag and drop a 'Macro' icon.
:* Double click on it and then click on the 'flash' label.
* Test the component by simulating the program.
:* See the [[Exercise - Simulating a Program]]
 

==What next?==
* The traffic cone component can now be exported in the usual way. (See [[Exercise - Exporting the Traffic Cone Component|Exporting the Traffic Cone]].)

==Link==
To download the Flowcode program for this exercise, click on the following link [[File:xxx|xxx]]

Exercise - Dashboard and System Panel - Controlling Multiple Objects

2013-09-01T13:58:08Z

JohnVerrill:

<sidebar>Sidebar: Panel Exercises</sidebar>
This exercise shows how to add two more LEDs to the car's instrument panel, each controlled separately by switches on the [[Dashboard Panel]]. These will warn the driver that the sidelights are switched on, and that a seatbelt is not fastened.

__TOC__

==Open the 'Headlight warning' flowchart==

* [[Opening an Existing Flowchart|Open the flowchart]] 'Headlight warning' which you created in [[Exercise - Dashboard Panel - Adding Objects]].
: This uses one switch, labeled 'main', operating an orange LED on the instrument panel.

==Add the LEDs==

* Add two more 'Single LEDs to the [[System Panel]].
: Do this either from the 'Outputs' toolbox, as you did for the first LED, or by 'copying and pasting' that LED. [[File:gen_exercisemulticontrol_finalinstpan_01.png|300px|right]]

* In either case,
: give one coordinates 'X'= -60, 'Y'=-55, 'Z'=-1.75, and color it green;
: give the other coordinates 'X'= 60, 'Y'=-55, 'Z'=-1.75, and color it blue.

: All three LEDs should have the same size ('Wi...' =32, 'He...'=32, 'De...'=10).

: The System Panel now resembles the one shown opposite.

==Connect the LEDs==
The original LED is connected to PORT A, bit 1.
* Click on the each of the added LEDs in turn, and use the Panel Properties to connect:
:: the left-hand LED (green) to PORT A, bit 0,
:: the right-hand (blue) LED to PORT A, bit 2.

==Add the switches==
[[File:gen_exercisemulticontrol_multidash_01.png|300px|right]]
* Add two more 'Toggle Metal Panel' switches to the Dashboard Panel.
: As above, you can do this either from the 'Inputs' panel or by 'copying and pasting' the first switch.
: In either case, give one coordinates 'X'= 30, 'Y'=5, 'Z'=-2, and the other coordinates 'X'= 60, 'Y'=5, 'Z'=-2.

: All three switches should have the same size ('Wi...' =2, 'He...'=2, 'De...'=1).

* Create two further labels, either by dragging them onto the Dashboard panel, using the 'T' icon, or by copying and pasting the 'side' label.
: In either case, rename one "side", and give it coordinates 'X'=30, 'Y'=-15, 'Z'=0.5.
: Rename the other "belt" and give it coordinates 'X'=60, 'Y'=-15, 'Z'=0.5.
: All three labels should be the same size, ('Wi...' =10, 'He...'=10, 'De...'=2).

: The Dashboard Panel now resembles the one shown opposite.

==Connect the switches==
The original 'main' switch is attached to PORT B, bit 0.
* Connect the switch above the 'side' label to PORT B, bit 1, and the one above the 'belt' label to PORTB,2.

==Binary arithmetic==
Before creating the Flowcode program, here is a little background in binary arithmetic. The switches don't have to be read as separate items. Instead, they can be used to control the first three bits of a binary number applied to PORT B. The table shows the input binary number resulting from different combinations of switch presses:

{| class="wikitable" style="text-align: center; margin:auto; color: black;" width="40%"
! belt bit 2 !! main bit 1!! side bit 0!! binary no.!! decimal no.
|-
|0||0||0||000||0
|-
|0||0||1||001||1
|-
|0||1||0||010||2
|-
|0||1||1||011||3
|-
|1||0||0||100||4
|-
|1||0||1||101||5
|-
|1||1||0||110||6
|-
|1||1||1||111||7
|}

The way this works:
: The 'belt' switch is worth '4' in decimal, because it controls the third binary digit, and so is worth 22 (=4).
: The 'main' switch is worth '2' in decimal, because it controls the second binary digit, and so is worth 21 (=2).
: The 'side' switch is worth '1' in decimal, because it controls the first binary digit, and so is worth 20 (=1).

When more than one switch is pressed, the number generated, (whether in binary or decimal,)is equal to the sum of these values.
So, when the 'belt' switch and the 'side' switch are both pressed, the number produced is '5'.

The Flowcode program senses this number using the 'Switch' icon.

==Creating the Flowcode flowchart==
* Modify the 'Headlight warning' program as follows:
:* Double-click on the 'Input' icon to open the dialogue box.
::* Change the 'Input from:' setting from 'Single Bit:' to 'Entire Port:'.
::* Click on 'OK'.
: (The program now reads all devices connected to PORT B, and so inputs the number generated by the three switches.)
[[File:gen_exercisemulticontrol_switchcaseconfig_01.png|300px|right]]
:* Click on the 'Decision' icon, to select it, and then delete it (by pressing on the 'Delete' key, for example.)
:* Drag and drop a 'Switch' icon to replace it.

::* Double-click on it to open the dialogue box, and then:
:::* Rename it "Input".
:::* Insert the variable name "input" in the box following the label 'Switch:'.
:::* There are eight possible combinations of switches, giving input numbers up to 111 (7 in decimal), so click to add ticks to the boxes from 1 to 7.
:::: The dialogue box resembles the one shown opposite.
:::* Click on 'OK'.
:* In the default branch, add an 'Output' icon, and double-click on it to configure it to output value 0 to the entire PORT A. Rename it "Switch off".
:* In the '=1' branch, add an 'Output' icon, and double-click on it to configure it to output value 1 to the entire PORT A. Rename it "Switch on".
:: This branch is activated when the 'side'light switch, alone, is pressed. The green warning light will come on as a result.
:* In the '=2' branch, add an 'Output' icon, and configure it to output value 2 to the entire PORT A. Rename it "Switch on".
:: This branch is activated when the 'main' switch, alone, is pressed. The orange warning light will come on.
:* In the '=3' branch, add an 'Output' icon, and configure it to output value 3 to the entire PORT A. Again, rename it "Switch on".
:: This branch is activated when both the 'side'light and 'main' switches are pressed. Both the green and orange warning lights will come.
:* In the '=4' branch, add an 'Output' icon, and configure it to output value 4 to the entire PORT A. Rename it "Switch on".
:* Follow this with a 'Delay' icon, configured to give a delay of one second.
:* Then add a second 'Output' icon, configured to output value 0 to the entire PORT A, to switch the warning light off.
:* Then add a second 'Delay' icon, also configured to give a delay of one second.
:: This branch is activated when the 'belt' switch, alone, is pressed (because the seat belt is not in use.) The blue warning light flashes on an off repeatedly.
:* In the '=5' branch, add an 'Output' icon, and configure it to output value 5 to the entire PORT A. Rename it "Switch on".
:* Follow this with a 'Delay' icon, configured to give a delay of one second.
:* Then add a second 'Output' icon, configured to output value 1 to the entire PORT A.
:* Then add a second 'Delay' icon, also configured to give a delay of one second.
:: This branch is activated when the 'side' and 'belt' switches are both activated. The program keeps the green warning light on, but makes the blue warning light flash on an off.
:* In the '=6' branch, add an 'Output' icon, and configure it to output value 6 to the entire PORT A. Rename it "Switch on".
:* Follow this with a 'Delay' icon, configured to give a delay of one second.
:* Then add a second 'Output' icon, configured to output value 2 to the entire PORT A.
:* Then add a second 'Delay' icon, also configured to give a delay of one second.
:: This branch is activated when the 'main' and 'belt' switches are both activated. The program keeps the orange warning light on, but makes the blue warning light flash on an off.
:* In the '=7' branch, add an 'Output' icon, and configure it to output value 7 to the entire PORT A. Rename it "Switch on".
:* Follow this with a 'Delay' icon, configured to give a delay of one second.
:* Then add a second 'Output' icon, configured to output value 3 to the entire PORT A.
:* Then add a second 'Delay' icon, also configured to give a delay of one second.
:: This branch is activated when all three switches are activated. The program keeps the green and orange warning lights on, but makes the blue warning light flash on an off.
The flowchart looks like the one below:
[[File:gen_exercisemulticontrol_multiprog1_01.png|1200px|center]]
* Simulate the program to check that it responds correctly when different combinations of the switches are pressed.

: '''Congratulations! You have completed the construction of the car instrument panel.'''

==Link==
To download the Flowcode program for this exercise, click on the following link [[File:xxx|xxx]]

Exercise - System Panel - Controlling Shapes

2013-09-01T13:57:20Z

JohnVerrill:

<sidebar>Sidebar: Panel Exercises</sidebar>
The following assumes that you have added a single LED to the [[System Panel]], as described in [[Exercise - System Panel - Adding Objects]].

The aim of this exercise is to mount the LED on the car's instrument panel, and to control the viewpoint of the resulting component.

__TOC__

==Open the LED flowchart==
[[File:gen_exerciseSystemPanel_controlviewpoint_moveicon_01.png|300px|right]]
* Open the flowchart "System_Panel_Add_LED" which you created in [[Exercise - System Panel - Adding Objects]].
* Check that the Panel Properties is displaying sizes as 'World size'.
* Move the LED into the top right-hand corner by clicking on the 'Move with the mouse' icon.

==Add the instrument panel==
* Click and drag a cylinder from the vertical toolbar onto the [[System Panel]].
[[File:gen_exerciseSystemPanelcontrolviewpoint_addcylinder_01.png|150px|right]]
* Click on it to select it. You will see five properties listed on the [[Properties Panel]],
: 'Shape', 'Color', 'Outline', 'Thickness' and 'Image'.
* The default 'Color' property is red (0x0000C0). Click on its value, and change the color to black (0x000000).

==Change the shape of the instrument panel==
[[File:gen_exerciseSystemPanelcontrolviewpoint_scaleicon_01.png|300px|right]]
* Click on the 'Scale with mouse' icon on the top, horizontal toolbar.
: Now, when you select the cylinder, eight drag handles appear around the edges.
: These allow you to reshape the cylinder by dragging on the appropriate handle.

* Drag on one of the horizontal handles until the width of the cylinder is 120mm.

* Drag on one of the vertical handles until the height is 60mm.

* On the Properties Panel, set the depth (De...) to 3mm.
[[File:gen_exerciseSystemPanelshapecontrol_instpanel_01.png|200px|right]]
* Centre the cylinder by setting its position coordinates to 'X'=0, 'Y'=0, 'Z'=0, on the Properties Panel.

* To make it look more realistic, locate the 'ADC dial' in the 'Inputs' toolbox. (This device can be used as an input device, but here it is being used as a decoration.)
* Click on the down-arrow to the left of the label, and select the 'Add to system panel' option.
* Click on the dial on the System Panel to select it and give it the following properties:
: 'Coordinates': X=0, Y=25, Z=5;
: 'World size': 'Wi...'=35, 'He...'=35, 'De...'=5;

* Now add two more dials in the same way.
* Give one 'Coordinates': X=-100, Y=0, Z=5, and 'World size': 'Wi...'=15, 'He...'=15, 'De...'=5.
* Give the other one 'Coordinates': X=100, Y=0, Z=5, and 'World size': 'Wi...'=15, 'He...'=15, 'De...'=5.

: The [[System Panel]] looks like the one opposite.

==Add the LED to the instrument panel==
* Now, move the LED back into position by selecting it and setting its position coordinates to 'X'=0, 'Y'=-60, 'Z'=0.
: Doing it in this order ensures that the LED appears on top of the instrument panel.

* Drag over both objects, and group them by clicking on the 'Group' icon. [[File:Gen_Panel_Object_Group_01.png|border]]

* At this point, save the flowchart as "System_Panel_Add_MountedLED".

==Change the viewpoint==
* Flowcode allows you to view these objects from different directions by changing the 'camera position' (viewpoint.)

: The first method uses the red, green and blue arrows at the top left hand corner of the System Panel.
:: First, click on the arrowhead of the green arrow.
:: This gives you a view of the objects from the 'green' direction.
:: Now do the same with the head of the red arrow, to see them from the 'red' direction.
:: Finally, clicking on the head of the blue arrow takes you back to the original view.

* There are three 'camera' controls that give finer control.
[[File:Gen Panel Object Move 01.png|left|border]]
: The first is the 'pan' control that allows you to move the viewpoint to one side.
:: To see this, click on the 'pan' control. Hold down the '''Ctrl''' key, and click the mouse anywhere on the System Panel.
:: As you move the cursor up and down or from side to side, the viewpoint moves accordingly.
:: Notice that the coordinates of the objects do not change. The objects stay in the same place, but they are viewed from a different place.

: The second and third are 'camera rotation' controls.
[[File:Gen Panel Camera Orbit 01.png|left|border]]
[[File:Gen Panel Camera Rotate 01.png|left|border]]
:: Click on the first of these. Hold down the '''Ctrl''' key, and click the mouse anywhere on the System Panel.
:: As you move the cursor, the objects seem to rotate, though, if you look at the 'Rotation' settings on the Properties Panel, you see that these settings do not change. Again, it is the viewpoint that is changing.
:: Then, try the same with the other control.

==Multiple views==
* A powerful feature of Flowcode 6 is the ability to view the components from a number of different directions simultaneously.

* To see this:
[[File:Gen Panel General Options 01.png|left|border]]
: Click on the 'General options' icon.
: In 'Number of views:', click on the down-arrow and select "3".
: By clicking on the appropriate arrowheads, set up each view as shown below.
: (Depending on the size and shape of the Systems Panel, the three views may be arranged vertically, instead of horizontally.
: Drag one edge of the Systems Panel sideways to see this effect. )
[[File:gen_exerciseSystemPanelshapecontrol_threeview1_01.png|500px|center]]

* You can adjust the viewpoint individually for each view, by operating the 'camera position' controls.
: An example of doing so is given below - notice the positions of the red, green and blue arrows in each:
[[File:gen_exerciseSystemPanelshapecontrol_threeview2_01.png|500px|center]]

* Alternatively, you can make changes to the objects themselves, in which case all three views are affected at once.
: In the next image, the instrument panel has been rotated:
[[File:gen_exerciseSystemPanelshapecontrol_threeview3_01.png|500px|center]]
: You can see what is happening by viewing the [[Properties Panel]]. Changes to the objects themselves result in changes to properties such as 'Coordinates' and 'World size'.
: Camera movement and rotation change the viewpoint, but do nothing to the properties of the objects themselves.

==What next==
The next stage is to control the LED using a switch mounted on Flowcode's Dashboard Panel. This is covered in the exercise [[Exercise - Dashboard Panel - Adding Objects|Adding Objects to the Dashboard Panel]]

==Video instructions==

See the [http://www.youtube.com/watch?v=5-IzDJ2NDcc&list=PLQDWBb7bxuCgg6aJgPJcfXBMzZdLILceQ Aligning Objects on the Panel 1] video to learn the basics of aligning objects on the panel, this video covers the all available options of the 'Snap to' function including Snap to '''''Grid''''', '''''Objects''''' and '''''Table top'''''.

The next video, [http://www.youtube.com/watch?v=okbJ9pJrEeA&list=PLQDWBb7bxuCgg6aJgPJcfXBMzZdLILceQ Aligning Objects on the Panel 2], expands onto manipulating objects by moving, rotating and scaling / re-sizing objects to align them on the panel, this video makes use of the [[Project Explorer]] in order to manipulate the objects precisely.

Finally, the [http://www.youtube.com/watch?v=0b0jtQzBS9Q&list=PLQDWBb7bxuCgg6aJgPJcfXBMzZdLILceQ Alignig Objects on the Panel 3] video details additional options to effectively align objects on the panel, this includes various options from the context menu when you right-click a selected object.

{| style="margin:auto; text-align:center;"
|-
|{{#ev:youtube|5-IzDJ2NDcc}}
| width="100px" |
|{{#ev:youtube|okbJ9pJrEeA}}
|-
| colspan="3" | 
|-
| colspan="3" |{{#ev:youtube|0b0jtQzBS9Q}}
|}

==Link==
To download the Flowcode program for this exercise, click on the following link [[File:xxx|xxx]]

Exercise - Using Interrupts

2013-09-01T13:55:56Z

JohnVerrill:

<sidebar>Sidebar: What Is an Interrupt?</sidebar>
Interrupts are a way of grabbing the microcontroller's attention immediately.

They are very widely used, both in microcontrollers and microprocessors. For example, the keyboard and mouse in your computer probably use interrupts to talk to the CPU.

They can also be used to save energy. In many battery-powered applications, the microcontroller is 'put to sleep' when inactive, and so requires little energy. An interrupt is used to 'awaken' the controller, and bring it back into operation, when needed.

This exercise shows how to use an interrupt to sense when a switch is closed, (an external interrupt).

__TOC__

==Polling vs interrupt==

The microcontroller is often connected to a large number of peripheral input devices - switches, sensors, memory, timers etc.
There are two broad ways in which one of these devices can be serviced by the microcontroller:
* polling - each device is 'asked' in turn if it has data to transfer to the controller;
* interrupts - allow the device to interrupt the task being carried out by the controller.

The exercise aims to show the difference between polling and using interrupts.

==The system==

This exercise sets up a system with LEDs controlled by two switches:
::* Switch 1 is polled by the program, at regular intervals. 
::* Switch 2 initiates an interrupt.

The polled switch, switch 1, is checked at regular (and predictable) intervals - every six seconds in this example.
Switch 2 is connected so that as soon as it operates, the processor stops what it is doing and jumps to the Interrupt Service Routine (ISR). In the process, the return address is stored, so that at the end of the ISR, the processor can return to where it left the main program. In Flowcode, the ISR takes the form of a macro, configured like any other.

==The flowchart==

The flowchart sequence:
:* Check if switch 1 is pressed.
:: If it isn't, make the red LED flash slowly.
:: If it is, make the yellow LED flash slowly.
:* Go back to the beginning and repeat the process.
:* Whenever switch 2 is pressed, immediately make both LEDs flash quickly ten times and then go back to the main program.

==The main program==

* [[Creating Flowcharts|Start a new Flowcode flowchart]], using the default microcontroller.

* Make sure that the [[System Panel]] is visible. If necessary, click on [[View]] and then select 'System Panel' a check-box will appear next to the option when enabled.

* Drag and drop a [[Loop Icon Properties|Loop icon]] between the BEGIN and END icons.

* Inside the loop, drag and drop an [[Input Icon Properties|Input icon]] from the [[Tools and Views#1) Icons Toolbar|Icons toolbar]].

* Drag and drop a [[Decision Icon Properties|Decision icon]] after the 'Input' icon.

Next, add icons to control what happens when switch is not pressed, (and so the program follows the 'No' branch):

* Drag and drop an [[Output Icon Properties|Output icon]] in the 'No' branch.
: This icon is going to turn the red LED on.

* Drag and drop a [[Delay Icon Properties|Delay icon]] after the 'Output' icon.
: This will keep the LED on for three seconds.

* Follow it with another [[Output Icon Properties|Output icon]].
: This icon is going to turn the LED off.

* Add a second [[Delay Icon Properties|Delay icon]] next.
: This will keep the LED off for three seconds.

The program then loops back and checks the state of the switch again.

Next, add icons to control what happens when switch is pressed, and so the program follows the 'Yes' branch:

* Drag and drop an [[Output Icon Properties|Output icon]] in the 'Yes' branch.

* Drag and drop a [[Delay Icon Properties|Delay icon]] after the 'Output' icon.

* Follow it with another [[Output Icon Properties|Output icon]].

* Add a second [[Delay Icon Properties|Delay icon]] next.

The program then loops back, as before, and checks the state of the switch again.

==Add switch 1 and the LEDs ==

* Locate the 'Inputs' toolbox, and click on the down arrow next to the switch labelled 'Toggle Metal PCB'.
: Click on the 'Add to system panel' option.
: Configure its properties so that it is connected to Port B, bit 1.

* Locate the 'Outputs' toolbox, and click on the down arrow next to the 'LED array' label.
: Click on the 'Add to system panel' option.
* Click on one, and configure its properties as follows
:: set the 'Count' property to "2", to give two LEDs in the array;
:: set the colour of LED0 to red, and that of LED1 to yellow.
:: LED0 will light when Port A is sent value '1', and LED1 will light when Port A is sent value '3';
:: check that the 'Connections' property shows that it is connected to Port A.

Double click on each icon in the flowchart and configure it as shown in the following images:

<gallery caption="Configuring the icons" perrow="6">
File:Exercise_UsingInt_redLEDon.jpg|Turn the red LED on
File:Exercise_UsingInt_3sdelay.jpg|Three seconds delay
File:Exercise_UsingInt_LEDoff.jpg|Turn the LEDs off
File:Exercise_UsingInt_yellLEDon.jpg|Turn on the yellow LED
File:Exercise_UsingInt_sw1_prop.jpg|Configure switch 1
File:Exercise_UsingInt_decision.jpg|Configure the decision icon
</gallery>

To see a larger version, double click on the image.

Simulate the flowchart to make sure that the LEDs behave as expected.

==Add switch 2==
[[File:Exercise_UsingInt_int_prop.jpg|200px|right]]

* Add a second 'Toggle Metal PCB' switch to the system panel.
: Configure its properties so that it is connected to Port B, bit 0 - the hardware interrupt bit.
* Drag and drop an interrupt icon [[File:Btn_Interrupt.gif|border]] between 'BEGIN'and the upper loop icon, (although it will work anywhere in the flowchart.)
: Double click on the icon, and configure it as shown opposite.
* The next task is to create the ISR. Click on the 'Create New Macro...' button.
[[File:Exercise UsingInt Int flashfastmacro.jpg|200px|right]]

* The 'Create a New Macro' dialogue box opens.
: Give the macro the name "flash_fast".
: Click on OK.

* In the 'Properties:Interrupt' dialogue box, click on the 'OK & Edit Macro' button.
: Create the flowchart shown opposite for the macro.
: Sending value '3' (=00011 in binary,) to Port A switches on both LEDs.

==The main flowchart==

Your flowchart should now be set up to resemble the image below:

[[File:Exercise_UsingInt_main.jpg|350px|center]]

==Test the system==

Earlier, you tested the effect of switch 1 on the LEDs. Now you can test the effect of switch 2 as well.
* Run the simulation, and confirm the action of switch 1 on the LEDs.
* While Flowcode is simulating a three second delay, toggle switch 2 on and off.
: The three second simulationshould stop, mid-delay, and both LEDs should flash quickly, ten times, as specified in the ISR.
: After this, the microcontroller resumes the main program from where it left off, the three second delay.
* Repeat the tests until you are happy with the way the system operates.

==Link==
To download the Flowcode program for this exercise, click on the following link [[File:xxx|xxx]]

Exercise - Inserting Code Into Flowcode

2013-09-01T13:55:23Z

JohnVerrill:

<sidebar>Sidebar: What Is a Macro?</sidebar>
C code is a high-level programming language widely used in industry. 
It has spawned a number of other programming languages, such as C#, C++, Java and Python.

Flowcode programs are first compiled into C before being crunched down eventually into hex code.

There are two mechanisms for adding your own C code to a Flowcode flowchart:
[[File:Exercise_InsCode_C_suppcode.jpg|right|350px]]
* using the 'C Code' icon [[File:Btn C Code.gif|border]] ;
* using the 'Use supplementary code' facility within 'Project Options', shown opposite:

__TOC__

==Why would you want to?==

* Flowcode programs are compiled to 'C', but produce many lines of code.
: They do so because they must be able to cope with any function or structure that the designer wishes to use.
: Experienced C programmers may wish to use code more efficiently, and so insert a few lines of code to replace many lines which Flowcode would generate. (This usually applies to the 'Adding supplementary code' option.)

* Experienced programmers can insert a short section of C code in order to reduce the length, or complexity, of the Flowcode program.

* Students learning to program in C can test short sections of code by inserting them into a Flowcode program. This avoids having to write the full program in C.

==Adding supplementary code==

This feature is used when you have blocks of code containing routines, definitions, lookup tables, etc.
[[File:Gen_Supplementary_Code_01.png|right|frameless]]

'''Definitions and function declarations:'''

This is the first section. It allows users to initialise the program, by adding structures such as 'defines', 'includes', and other function declarations. This section must be placed at the beginning of the C file so that the code is 'visible' to all parts of the program.

'''Function implementations:'''

This second section allows for the addition of the main function code.

Structured thus, the code is accessible to any Flowcode macro, and vice-versa.

==Warning==

Be sure that the added C code is correct! 

Flowcode does not simulate C Code, so programs that make use of supplementary code may not simulate correctly.
Where Flowcode fails to compile, it may be that the supplementary code contains errors.

==Using the 'Code' icon==
[[File:Exercise_InsCode_C_Flowchart.png|right|294x261px]]

* [[Opening Flowcode|Open Flowcode]].

* On the Startup screen, click on 'New project' to [[Creating Flowcharts|create a new flowchart]].

* Add the icons shown in the flowchart:
::* a loop icon, configured as an infinite loop;
::* a calculation icon:
:::* use it to create two byte variables, 'var1' and 'add',
:::* set them to the following values:
::::: var1 = 2, add = 3;
::* a Code icon [[File:Btn C Code.gif|border]]- details given below;
::* a delay icon configured to give a two second delay.

==The C Code==

Configure the Code icon by typing in the following code, exactly as written here:

<pre class="brush:[cpp]" style="float:left;">
trisb = 0; //Set all of Port B to output
portb = FCV_VAR1; //Output the value of var1 to port B
trisa = 1; //Convert port A bit 0 to input
if (test_bit(porta,0)) //Check to see if A0 is high
{
portb = FCV_VAR1 + FCV_ADD; //If so, portb = 2 + 3 = 5 (0101 in binary)
}
else
{
portb = FCV_VAR1; //Otherwise portb = 2
}
</pre>

The 'Code' icon properties box resembles that shown opposite.

[[File:Exercise_InsCode_C_Code_Properties.png|center]]

The software recognizes instructions and comments, and colour-codes them accordingly.

'''Some notes on this code:'''

* The ports on the PIC chip are bi-directional - they can act as either input or output.
* Their behaviour is controlled by the contents of two more registers - TRISA (for Port A) and TRISB (for Port B.)
:* A value of '0' in the control register makes the corresponding bit of the port into an output bit.
:* A value of '1' in the control register makes the corresponding bit of the port into an input bit.
* Commands are finished by adding a semicolon (;).
* The characters '//' are used to indicate comments - there to aid understanding of the program. These are ignored by the compiler.
* Where variables are defined in the Flowcode program, the prefix 'FCV_' must be added to the name of the variable, which is written in upper case lettering.
* The 'if-else' construction examines a possible condition - "Is Port A bit 0 high?"
:* If true, the values of the two variables are added together and sent to Port B.
:* If false, only the value of 'var1' is sent to Port B.

* All of this could have been done using 'pure' Flowcode, but it would have required around five more icons in the flowchart.

==Testing==

As pointed out earlier, Flowcode will not simulate added C code, and so there is no value in simulating this program. 
Instead, compile it to the PIC chip which you specified as the target.

Add the following E-Blocks units to the EB-008 Multiprogrammer holding the PIC chip:
:: a switch unit to Port A,
:: a LED unit to Port B.
Press the reset switch on the Multiprogrammer.

Test the program by noticing the output displayed on the LEDs when switch 0 on the switch unit is pressed.
* When pressed, LEDs D2 and D0 should light, indicating an output 0101 (i.e. the number 5,)
* When not pressed, LED D1 should light, indicating an output 0010, (i.e. the number 2.)

==Link==
To download the Flowcode program for this exercise, click on the following link [[File:xxx|xxx]]

Exercise - Using Macros

2013-09-01T13:54:57Z

JohnVerrill:

<sidebar>Sidebar: What Is a Macro?</sidebar>
Macros are sections of code that are repeated a number of times within a program. 
It is more efficient to use a macro than to create the code repeatedly every time it is needed. 
For more information about macros, see [[What Is a Macro?]].

This exercise shows how to use macros with a menu to create a simple LED flasher. The LED can be made to flash at different frequencies by pressing different switches.

The first section looks at creating the core program, with the menu. The second section shows how to create the macro.

__TOC__

==Linking frequency and delay==
[[File:Exercise_Using_Macros_LED_Flash.png|200px|right]]
The flowchart controlling the LED flashes is shown opposite. 
The table that follows shows the link between length of delay in each 'Delay' icon, and the frequency of flashing.
The LED is switched on for one delay period, and then off for one delay period.

{| class="wikitable" style="text-align:center;"

! colspan="2" | LED frequency and delay
|-
| Delay in milliseconds || Frequency
|-
| 1000 ||0.5
|-
| 500 ||1

|-
| 250 ||2

|-
| 125 ||4
|}

==Create the variables==
The program will use two variables, 'selection', to store the state of the switches used to select frequency, and 'delay', used to determine the frequency at which the LED flashes.
:* In the 'Edit' menu, on the main toolbar, click on 'Variables...' to open the [[Variable Manager]] dialogue box.
::* Hover just to the left of the 'Variables' label, and click on the down arrow that appears.
::* Select 'Add new' and the 'Create a New Variable' dialogue box opens.
::* Name the first new variable "selection".
::* Leave the variable type as 'Byte'.
::* Click on 'OK'.
::* Now do the same thing again to add the second variable "delay".

==Create the macro==
[[File:Exercise_Using_Macros_Set_Frequency_Properties.png|250px|right]]
* Open the 'Macro' menu on the main toolbar, and click on the 'New...' option.
: The 'Create a New Macro' dialogue box opens.
:* Name the new macro "Set_Frequency".
:: (Notice the underscore!
:: Macro names must appear to be a single word. To use more than one word, join them together with underscore characters.)
:* Hover to the left of the 'Parameters' label, and click on the down arrow that appears.
:* Click on 'Add new' and then write in the name "delay" as the variable name in the dialogue box that opens.
:* Leave the 'Description:' box empty, and accept the default variable type, 'Byte'.
:* Click on 'OK'.
: The dialogue box for this macro is shown opposite.

: Notice that this creates a new tab, called 'Set_Frequency' on the Flowcode work area.
[[File:Exercise_Using_Macros_Macro_Loop.png|250px|right]]
:* Click on this tab so that you can create the details of the macro.
::* Drag and drop a 'Loop' icon between 'BEGIN' and 'END'.
::* Double click on it to open its dialogue box.
::* Change the 'Display name:' to "Loop ten times".
::* Click on 'OK'.
::* Tick the 'Loop count:' box and insert the number "10".
[[File:Exercise_Using_Macros_Output_Properties.png|250px|right]]
: The dialogue box for the 'Loop' is shown opposite.

::: Inside the loop:
::* Drag and drop and 'Output' icon, and double click on it.
:::* Change the 'Display name:' to "Switch on".
:::* Configure it to output value "1" to bit 0 of Port A.
:::* Click on 'OK'.
[[File:Exercise_Using_Macros_Macro_Delay.png|250px|right]]
: This dialogue box for the 'Output' icon is shown opposite.

::* Follow this icon with a 'Delay' icon, and double click on it.
:::* Leave the 'Display name:' as 'Delay', and the timing units as 'milliseconds'.
:::* In the 'Delay value or variable:' box, type the name of the variable "delay".
:::* Click on 'OK'.
: The dialogue box for this 'Delay' is shown opposite.

::* Next, place a second 'Output' icon.
::: The easiest way to do this is to 'copy and paste' the first one, then select the copy and drag it into position.
::* Double click on it and rename it "Switch off".
:::* Configure it to output value "0" to bit 0 of Port A.
:::* Click on 'OK'.

::* Follow that with a second 'Delay' icon, configured in exactly the same way as the first.
::: (Again, 'copy and paste' followed by dragging the resulting icon is the easiest way to do this.)
: The structure of the macro should resemble that shown below.
[[File:Exercise_Using_Macros_Flowchart_Progress.png|250px|center]]

==The main sequence==
This part of the program uses three switches to select the frequency for the LED. 
The flowchart sequence will be:
::::* Read the state of the switches.
::::* Use this state to determine the correct branch to take.
::::* Set up the appropriate time delay for the chosen frequency.
::::* Run the macro with that delay setting.
::::* Loop back and check the switches again.

==Set up the 'main' flowchart==
* Open Flowcode, and set up the new flowchart as described in [[Exercise - Creating a Flowchart|Creating a Flowchart]].

* Click and drag an infinite loop, [[File:Btn Loop.gif|border]] between the 'BEGIN' and 'END' icons.
: Inside the loop:
[[File:Exercise_Using_Macros_Input_Properties.png|250px|right]]
:* Click and drag an 'Input' icon [[File:Btn Input.gif|border]].
::* Double click on it to open the dialogue box.
::* Rename it "Read the switches" and set it up to input from the entire Port B.
::* In the 'Variable:' box, type "selection"
::: The three switches will be connected to bits 0, 1 and 2 of Port B.
::: The state of these switches will be stored in the variable 'selection'.
::* Click on 'OK'.
:: The input dialogue box for the 'Input' icon is shown opposite.

[[File:Exercise_Using_Macros_Switch_Properties.png|250px|right]]
:* Click and drag a 'Switch-case' icon, [[File:Btn Switch.gif|border]] after the 'Input' icon.
::* Double click on it to open the dialogue box.
::* Leave the 'Display name:' as 'Switch'.
::* In the 'Switch:' box, type the name of the variable that will trigger the branching, "selection".
::* Tick the first three 'Case:' boxes, and change the content of the third one from '3' to '4'.
::* Click on 'OK'.
:: The 'Switch-case' dialogue box is shown opposite.

:* Inside each of the three branches ('=1', '=2' and '=3'), click and drag a macro icon, [[File:Btn Macro.gif|border]] and a calculation icon, [[File:Btn Calculation.gif|border]].
::* In the '=1' branch, double click on the 'Calculation' icon, and rename it "One hertz delay".
::* In the 'Calculations:' box, type "delay = 500".
::* In the '=2' branch, double click on the 'Calculation' icon, and rename it "Two hertz delay".
::* In the 'Calculations:' box, type "delay = 250".
::* In the '=4' branch, double click on the 'Calculation' icon, and rename it "Four hertz delay".
::* In the 'Calculations:' box, type "delay = 125".

The three 'Calculation' dialogue boxes are shown below.
<Gallery widths=120px>
File:Exercise_Using_Macros_Delay_Properties_01.png
File:Exercise_Using_Macros_Delay_Properties_02.png
File:Exercise_Using_Macros_Delay_Properties_04.png
</gallery>
[[File:Exercise_Using_Macros_Flash_Macro.png|250px|right]]
:* Double click on each of the macro icons, in turn, and:
::* change the 'Display name:' to "Flash macro";
::* click on the 'Set_Frequency' label that appears (alone) in the list of possible macros;
::* type "delay" in the 'Parameters:' 'Expression' box.
:* Then click on 'OK'.
:: The resulting dialogue box is shown opposite.

===Main sequence flowchart===
The final flowchart for the main sequence should resemble the one shown below.
[[File:Exercise_Using_Macros_Main_Flowchart.png|850px|center]]

==Add the electronics==

===Add the switches===
* Locate the 'Push Round Panel' switch in the 'Inputs' toolbox in the [[Tools and Views#1) Icons Toolbar|Icons toolbar]].
:* Hover over the image to the left of the switch label, and click on the down-arrow that appears.
:* Click on the 'Add to system panel' option to select it.
:: An image of the push-button switch appears on the System Panel.
:* Click on the image of the switch on the System panel to select it.
:* Use the 'Edit' menu on the main toolbar to copy and paste two more instances of this push-button switch.
:* Click on one to select it, and use the Panel Properties to give it coordinates 'X'=-25, 'Y'=10, 'Z'=0.
:* In the same way, give the second coordinates of 'X'=0, 'Y'=10, 'Z'=0, and the third coordinates of 'X'=25, 'Y'=10, 'Z'=0.
:* Click on the first again, and then click on the 'Connections' property on the Panel Properties.
:* Use the microcontroller pinout that appears to connect the switch to Port B, bit 0.
:* Similarly, connect the other two switches to Port B, bit 1 and Port B, bit 2.

===Add the LED===
* Locate the 'Single LED' in the 'Outputs' toolbox in the [[Tools and Views#1) Icons Toolbar|Icons toolbar]].
:* Hover over the image to the left of the 'Single LED' label, and click on the down-arrow that appears.
:* Click on the 'Add to system panel' option to select it.
:* Select the LED on the System panel and drag it to a suitable position below the switches.
:* Look at the Panel Properties, the 'Connection' property shows that, by default, it is connected to Port A, bit 0.
:: Leave it like this.

===The System Panel===
The System Panel should now resemble the one shown below.
[[File:Exercise_Using_Macros_System_Panel.png|250px|center]]

==The alternative==
The final flowchart is much more compact because it uses a macro. The flowchart that follows does the same job, without using a macro:
[[File:Exercise_Using_Macros_Complete_Flowchart.png|1200px|center]]

==Link==
To download the Flowcode program for this exercise, click on the following link [[File:xxx|xxx]]

Exercise - Using Simulation Macros

2013-09-01T13:54:28Z

JohnVerrill:

<sidebar>Sidebar: What Is a Macro?</sidebar>
Simulation macros are a form of Component macros. Their purpose is to make simulation more realistic by adding physical components to the electronic devices.

When the Flowcode program is compiled and downloaded to a microcontroller, they are ignored - hence the name Simulation macros.

Even a cursory glance at the dialogue box used to configure them shows that they are very powerful devices, with a huge range of possible effects.

This exercise uses three of them to illustrate the use of a PIR (Passive Infra-Red sensor) to operate an intruder sensor.

__TOC__

==The scenario==

The scene depicts the front of a house.
[[File:Exercise SimIcon pan.png|center|350px]]

A PIR sensor is mounted on the wall of the house, above the path leading across the garden.

The data sheet for the PIR shows that it is sensitive to a range of 10 metres, within a cone of angle 100 degrees.

Its detection area is represented in the image by the pale blue cone.

When an intruder enters the detection cone, a warning lamp lights up in the house.

This exercise allows us to investigate factors such as the height of the sensor on the brick wall and the angle of the detection zone, so that these can be optimised for a typical intruder height.

==The System Panel==

On the System Panel, viewed from above (the default position,)create:
* '''a brick wall''', represented by adding a red cuboid and changing it to a rectangle, 15mm wide, 120mm high and 120mm deep,
:: located at coordinates x = 0, y = 0, z = 60,
:: with rotation settings X = 0, Y = 0, Z = 0;

* '''a path''', represented by a grey rectangle, 240mm wide, 100mm high and 0mm deep,
:: located at coordinatesx = 125mm, y = 0mm, z = 0mm,
:: with rotation settings of X = 0, Y = 0, Z = 0;

* '''a cone''', couloured light blue, representing the sensing region of the PIR, with width = 70mm, height = 250mm, depth 95mm,
:: located at coordinates x = 45mm, y = 0mm, z = 80mm,
:: with rotation settings of X = 0, Y = -55, Z = 0.

* Drag the mouse cursor over these three elements and group them together.

This produces 'group 1'.
:: Give this group:
::: dimensions - width = 265mm, height = 250mm, depth = 135mm;
::: coordinates - x = 128, y = 0, z = 68;
::: rotation - X = 0, Y = 0, Z = 0.

Also on the System Panel, create an intruder, by:
* adding four spheres, and configuring the properties as follows:
:: sphere 1 ('''the head'''):
::: colour pink;
::: dimensions - width = 12mm, height = 13mm, depth = 15mm;
::: coordinates - x = -2.2, y = 0.7, z = 22;
::: rotation - X = 90, Y = 0, Z = 0.

:: sphere 2 ('''the body'''):
::: colour blue;
::: dimensions - width = 14mm, height = 26mm, depth = 24mm;
::: coordinates - x = -2.2, y = 0.5, z = 4;
::: rotation - X = 90, Y = 0, Z = -180.

:: sphere 3 ('''the legs'''):
::: colour dark green;
::: dimensions - width = 9mm, height = 23mm, depth = 15mm;
::: coordinates - x = -2.2, y = 1, z = -16;
::: rotation - X = 90, Y = 0, Z = -180.

:: sphere 4 ('''the feet'''):
::: colour black;
::: dimensions - width = 6mm, height = 15mm, depth = 25mm;
::: coordinates - x = -6, y = 0, z = -25;
::: rotation - X = 90, Y = 90, Z = 0.

* Drag the mouse cursor over the four spheres and group them together.

This produces 'group 2'.
:: Give it:
::: dimensions - width = 18mm, height = 32mm, depth = 60mm;
::: coordinates - x = 165, y = 0, z = 28;
::: rotation - X = 0, Y = 0, Z = 0.

The System Panel should resemble the image shown above. (The image has been rotated to show all components. The table-top is coloured green.)

Click on the 'Collisions' icon, [[File:Gen Panel Object Collision Move Around.png|35px]] and select the 'Move through' option, which allows the intruder to enter the detection cone.

==The Dashboard Panel==
[[File:Exercise SimIcon dash.png|right|200px]]
* Open the 'Outputs' toolbox, and locate the 'LED 5mm Panel' device.
* Click on the down arrow next to it and choose the 'Add to dashboard panel' option.
* Zoom in to the Dashboard Panel to make the LED large enough to see.
* Click on the LED and configure its properties as follows:
::* choose a suitable colour, such as red;
::* connect it to Port A, bit 0.

==The Flowcode program==
'''The plan:'''
* Set the initial position of the intruder, using the 'MoveTo' simulation macro.

* Move the intruder towards the detection cone using the 'MoveAlong' simulation macro.
:: This '''changes''' the x coordinate of the intruder '''by an amount specified by the variable 'xpos''''.

* When the intruder enters the detection zone, the simulation macro 'CollisionTest' returns a value of '1' in the variable 'hit'.
:: At this point, we can stop any more movement so that we can look at the x coordinate of the intruder.
:: To do so, we change the value of 'xpos' to zero.

* Otherwise, the simulation repeats.

'''Implementation:'''

* [[Opening Flowcode|Open Flowcode]].

* On the Startup screen, click on 'New project' to [[Creating Flowcharts|create a new flowchart]].

* Add the icons shown in the flowchart:
:* a loop icon, configured as an infinite loop, and within it:
::* a Simulation macro icon[[File:Btn Simulation Macro.gif|border]];
::* a second loop;
::* a Calculation icon.

:* Within the second loop, add:
::* two more Simulation macro icons;
::* a decision icon with:
:::* a 'Yes' loop containing an output icon, followed by a delay icon and then a calculation icon;
:::* a 'No' loop containing an output icon, followed by a delay icon;

[[File:Exercise_SimIcon_Simmove.png|right|250px]]

* Configure the icons, by double clicking on each in turn, as follows:
::* the top Simulation macro:
:::* name it "Set initial position";
:::* click on the 'Panel' tab, and then on the 'Position' folder;
:::* click on the 'MoveTo' macro and:
::::* choose 'group2'(the intruder)as the Handle;
::::* set the X value to "200";
::::* set the Y value to "0";
::::* set the Z value to "28";
::::* click on OK.

::* the second loop:
:::* set it to 'Loop while:' "hit = 0";
:::* 'Test the loop at the:' 'End'
:::* Click on OK.

[[File:Exercise_SimIcon_Moveint.png|right|350px]]

::* the second Simulation macro:
:::* name it "Move the intruder";
:::* click on the 'Panel' tab, and then on the 'Position' folder;
:::* click on the 'MoveAlong' macro and:
::::* choose 'group2'(the intruder)as the Handle;
::::* choose 'shape1'( the brick wall) as the Axis;
::::* click on the down arrow on the end of the 'X' row, and create a floating point variable called "xpos", with an initial value 5.0, to use as the X variable;
::::* click on OK.

[[File:Exercise SimIcon Simcheck.png|right|250px]]

::* the third Simulation macro:
:::* name it "Check detection";
:::* click on the 'Panel' tab, and then on the 'Collision' folder;
:::* click on the 'TestSingle' macro and:
::::* choose 'shape2'(the detection cone) for 'Pos' and 'shape5' (the intruder's head,) for 'Test';
:::* use the down arrow at the end of the 'Return Value' box to create a boolean variable caled "hit" to use as the 'Return Value'.
::::* click on OK.

::* the decision icon:
:::* name it "Intruder detected?";
:::* insert the condition "hit = 1";
:::* click on OK.

:::* In the 'Yes' loop:
::::* name the Output icon "Switch on lamp";
::::* send value '1' to Port A single bit 0;
::::* click on OK.

::::* name the Delay icon "Wait 100ms";
::::* configure it to give a delay of 100ms;
::::* click on OK.

::::* name the Calculation icon "Stop movement";
::::* in the 'Calculations:' box, insert "xpos = 0" to reduce the distance incremented each time to zero;
::::* click on OK.

:::* In the 'No' loop:
::::* name the Output icon "Switch off lamp";
::::* send value '0' to Port A single bit 0;
::::* click on OK.

::::* name the Delay icon "Wait 100ms";
::::* configure it to give a delay of 100ms;
::::* click on OK.

::* the final Calculation icon:
::::* name it "Reset variables";
::::* in the 'Calculations:' box, insert "hit = 0" and "xpos = 5.0";
::::* click on OK.

The Flowcode flowchart resembles the one shown below:

[[File:Exercise SimIcon Simflow.png|center|500px]]
==Testing==

* Run the simulation.
: The intruder should move towards the house, until he enters the detection zone.

: At this point, the warning lamp turns on and he stops for three seconds.

: Then the simulation repeats.

* Stop the simulation when the lamp is lit, and click on the image of the intruder. You can now read the x coordinate from the Panel properties box.

* Change the height of the PIR sensor on the wall, or the angle of the detection cone, and see what happens to this coordinate.

==DON'T DOWNLOAD IT!!==
The important point is that the two Simulation macros do not compile to code that can be downloaded to a microcontroller. They affect only the simulation of the program.

==Link==
To download the Flowcode program for this exercise, click on the following link [[File:xxx|xxx]]

Exercise - Using Component Macros

2013-09-01T13:53:49Z

JohnVerrill:

<sidebar>Sidebar: What Is a Macro?</sidebar>
Component macros are sections of code that have been written to support the components included with Flowcode 6. 
They take all the effort out of using these components.

This exercise uses them to control a particularly complicated, but very common device, the Liquid Crystal Display (LCD). 
In this case, it uses a LCD to display elapsed time in a timer.

The first section looks at using [[Component Macro Icon Properties|Component Macros]] to create the core timing sequence. The second section looks at using it to turn on a lamp for ten seconds once a switch is pressed.

__TOC__

==The core timing sequence==
At the core of the program is a section that sets up the LCD to display the time. 
The flowchart sequence for displaying the elapsed time will be:
::::* Initialize the LCD using the 'Start' macro.
::::* Set the cursor position in the LCD, using the 'Cursor' macro.
::::* Display the text "Elapsed time", using the 'PrintString' macro.
::::* Set the time to zero.
::::* Change the cursor position, using the 'Cursor' macro.
::::* Display the time.
::::* Wait for one second.
::::* Increment the time.
::::* Display the new time.
::::* Loop back and repeat the process from the one second delay.

===Set up the flowchart===
* Open Flowcode, and set up the new flowchart as described in [[Exercise - Creating a Flowchart|Creating a Flowchart]].

===Create the core sequence===
===Add the LCD===
* Locate the 'LCD' inside the 'Outputs' toolbox in the [[Tools and Views#1) Icons Toolbar|Icons toolbar]].
:* Hover over the image to the left of the 'LCD' label, and click on the down-arrow that appears.
:* Click on the 'Add to system panel' option to select it.
:* Zoom in until the LCD image is big enough to read. (See [[Exercise - Controlling the Camera]] for information on how to zoom in on the [[System Panel]].)

===Initialise the LCD===
* Click and drag an infinite loop between the 'BEGIN' and 'END' icons.
* Inside the loop:
:* Click and drag a 'Component macro' icon.[[File:Btn_Component_Macro.gif|border]]
::* Double click on it to open the dialogue box, so that you can configure it.
::: The program 'knows' which components you have added to the System or Dashboard panel, and modifies the list of available commands accordingly.
::: Under 'Components', the LCD will be listed, and underneath it the list of commands.
::* Scroll down to the bottom of the list and click on the 'Start' command.
::* Rename the 'Display name' as "Start the LCD".
::* Click on 'OK'.
::* The dialogue box is shown below.

===Set up the display===
The first task is to define where the text will be displayed. 
This involves another LCD 'Component Macro' called 'Cursor'.
This defines the LCD 'cell' where the text display starts. The LCD has a grid of 32 cells, arranged in 2 rows of 16. 
The upper row is given the value y=0, and the lower y=1. The sixteen horizontal cells are given values from x=0 to x=15.
:* Click and drag a second 'Component macro' icon just below the first.
::* Double click on it to open the dialogue box.
::* Scroll down to the 'Cursor' command.
::* Rename the 'Display name' as "Move the cursor".
::* In the 'Parameters' section, set the value of 'x' to 2, and 'y' to 0.
::* Click on 'OK'.

The next 'Component Macro' specifies the text to be printed, starting at this location.
:* Click and drag a third 'Component macro' icon just below the first.
::* Double click on it to open the dialogue box.
::* Scroll down to the 'PrintString' command and click on it.
::* Rename the 'Display name' as "Elapsed time".
::* In the 'Expression' box, type "Elapsed time" (making sure you include the quotation marks "".)
::* Click on 'OK'.
::* The dialogue box is shown below.

[[File:Exercise_Using_Component_Macros_Variable_Properties.png|250px|right]]
===Display elapsed time===
:* In the 'Edit' menu, on the main toolbar, click on 'Variables...' to open the [[Variable Manager]] dialogue box.
::* Hover just to the left of the 'Variables' label, and click on the down arrow that appears.
::* Select 'Add new' and the 'Create a New Variable' dialogue box opens.
::* Name the new variable "time", and give it an initial value of zero.
::* Leave the variable type as 'Byte'.
::* Click on 'OK'.
::* The dialogue box is shown below.

: The next Component Macro repositions the cursor, so that the elapsed time is shown below the "Elapsed time" label. 
: The y value is changed to y=1, and the x value to x=8.
:* Click and drag a fourth 'Component Macro' to follow the third one.
::* Double click on it to open the dialogue box.
::* Scroll down to the 'Cursor' command.
::* Rename the 'Display name' as "Move the cursor".
::* In the 'Parameters' section, set the value of 'x' to 8, and 'y' to 1.
::* Click on 'OK'.

:* Click and drag a fifth 'Component macro' icon just below the fourth.
::* Double click on it to open the dialogue box.
::* Scroll down to the 'PrintNumber' command and click on it.
::* Rename the 'Display name' as "Display elapsed time".
::* In the 'Expression' box, type the variable name "time".
::* Click on 'OK'.
::* The fifth 'Component Macro' dialogue box is shown below.
<gallery widths=200px heights=200px perrow=5 caption="Component Macro Properties">
File:Exercise_Using_Component_Macros_Icon_Properties_01.png
File:Exercise_Using_Component_Macros_Icon_Properties_04.png
File:Exercise_Using_Component_Macros_Icon_Properties_02.png
File:Exercise_Using_Component_Macros_Icon_Properties_05.png
File:Exercise_Using_Component_Macros_Icon_Properties_03.png
</gallery>

===Finishing touches===
:* Click and drag a 'Delay' icon to follow the fifth 'Component Macro'.
::* Double click on it to open the dialogue box.
::* Rename it "Wait one second."
::* Configure it to give a delay of one second.
::: For help with 'Delay' icons, see [[Icon Properties]]
::* Click on 'OK'.

:* Click and drag a 'Calculation' icon to follow the 'Delay'.
::* Double click on it to open the dialogue box.
::* Rename it "Add one second."
::* In the 'Calculations:' section, type "time=time+1".
::: The effect of this is to increase the number stored in the 'time' variable by one, (also called incrementing the 'time' variable.)
::: For help with 'Calculation' icons, see [[Icon Properties]]
::* Click on 'OK'.

===Test the Core===
: The diagram below shows the flowchart at this stage.
[[File:Exercise_Using_Component_Macros_Flowchart_01.png|350px|center]]
: At this point, the flowchart should be saved as 'Timer', and can be simulated to test it.

==Extend the program==
The full program is designed to:
:::: wait until a switch is pressed momentarily;
:::: light a lamp ;
:::: time a ten second period;
:::: then switch it off.

To do this, the sequence is now modified, as follows:
:* Is the switch pressed?
::* If not, branch back and test the switch again.
::* If it has:
:::* light the lamp;
:::* run through the timing core ten times,
:::* switch off the lamp.

===Add the switch===
* Locate the 'Push Round Panel' switch in the 'Inputs' toolbox in the [[Tools and Views#1) Icons Toolbar|Icons toolbar]].
:* Hover over the image to the left of the switch label, and click on the down-arrow that appears.
:* Click on the 'Add to system panel' option to select it.
:* Click on the image of the switch on the System panel to select it and drag it to a suitable position.
:* On the Panel Properties, click on the 'Unconnected' label, next to 'Connection'.
:: A pinout of the microcontroller appears.
:* Click on the rectangle that represents the pin RA1/AN1, to connect the switch to Port A, bit 1 of the microcontroller.

===Add the LED===
* Locate the 'Single LED' in the 'Outputs' toolbox in the [[Tools and Views#1) Icons Toolbar|Icons toolbar]].
:* Hover over the image to the left of the 'Single LED' label, and click on the down-arrow that appears.
:* Click on the 'Add to system panel' option to select it.
:* Select the LED on the System panel and drag it to a suitable position.
:* Look at the Panel Properties, the 'Connection' property shows that, by default, it is connected to Port A, bit 0.
:: Leave it like this.

===Modify the flowchart===
* Immediately after the 'Begin' icon, drag and drop a 'Connection Point (Declare Connection Point)' icon.[[File:Btn Connection Point.gif|border]]
* Next, add an 'Input' icon, and double click on it to open the dialogue box.
* Change the 'Display name:' to "Read the switch".
* Create a new variable, called 'switch'. One way to do this is to click on the down arrow at the end of the 'Variable:' box.
:* Then click on the down arrow next to the 'Variables' label, and select 'Add new'.
:* The 'Create a New Variable' dialogue box opens. Type in "switch" as the name of the new variable. Leave the variable type as 'Byte'.
:* Click on 'OK'.
* In the 'Variable' box, type the name of the new variable "switch".
* In the 'Port:' box, select 'PORT A'. Configure the rest of the dialogue box to 'Input from:' 'Single Bit:' 1.
:* Click on 'OK'.
* Next, drag and drop a 'Decision' box, and double click on it to open the dialogue box.
:* Rename it "Switch pressed?".
:* In the condition 'If' box, type "switch=1"
:* Click on 'OK'.
* In the 'No' branch, drag and drop a 'Connection Point (Jump to Connection Point)' icon.[[File:Btn Goto Connection Point.gif|border]]
* In the 'Yes' branch, drag and drop an 'Output' icon.
:* Double click on it to open the dialogue box.
:* Change the 'Display name:' to "Switch on the lamp".
:* In the 'Variable or value:' box, type "1".
:* Configure the rest of the box to output this to 'PORT A' 'Single Bit:' 0.
:* Click on 'OK'.
* Click and drag the 'Loop' icon to follow this in the 'Yes' branch.
:* Double click on the 'Loop' icon to configure it.
:* Leave the 'Display name:' as 'Loop', and the 'Loop while:' box checked.
:* In the other box, type the condition "time<10".
:* Click on 'OK'.
* After the end of the loop, drag and drop a second 'Output' icon.
:* Double click on it, rename it "Switch off the lamp" and configure it to output value 0 to Port A, bit 0.
:* Click on 'OK'.

The dialogue boxes for all these additions are shown below.
<gallery widths=200px heights=200px perrow=5 caption="Added Component Macro Properties">
File:Exercise_Using_Component_Macros_Input_Properties_01.png
File:Exercise_Using_Component_Macros_Decision_Properties_01.png
File:Exercise_Using_Component_Macros_Output_Properties_01.png
File:Exercise_Using_Component_Macros_Loop_Properties_01.png
File:Exercise_Using_Component_Macros_Output_Properties_02.png
</gallery>

The final flowchart resembles the one below.
[[File:Exercise_Using_Component_Macros_Flowchart_02.png|350px|center]]

==Final testing==
* [[Saving a Flowchart|Save the flowchart]].
* [[Starting Flowchart Simulation|Run the simulation]] to test that it works.

==Link==
To download the Flowcode program for this exercise, click on the following link [[File:xxx|xxx]]

Exercise - Expanding a Program

2013-09-01T13:53:19Z

JohnVerrill:

<sidebar>Sidebar: Taking Flowcode Further</sidebar>
This exercise assumes you have created, tested and documented the program described in the exercise [[Exercise - Documenting a Flowchart|Documenting a Flowchart]].

Because you have documented the flowchart properly, you can easily and accurately change the program as you know exactly how the program functions and what process it goes through.

You do not have to massively alter your program to make it more effective, sometimes a little change can make a big difference, simply adding and configuring one component can change the program to be much more effective and suitable for use elsewhere.

__TOC__

==Load the Flowcode flowchart==
* [[Opening an Existing Flowchart|Open the flowchart]] called 'Lamp1.fcf' which you created earlier and documented in the exercise [[Exercise - Documenting a Flowchart|Documenting a Flowchart]].

==Enhancing a program==
Now that you have a fully functioning program which is properly documented both by display names of icons and detailed comments, you can manipulate this program integrate it into another system, or expand the program further and turn it into your own expanded system, and even turn it into a full application.

We are going to expand our program to function as a set of traffic lights, to do this we are going to add 2 more LEDs and add to our 'Decision' icon which responds to when the switch is on to activate the traffic lights accordingly.

==Add the LEDs==
[[File:Exercise_Expanding_a_Program_Components.png|right]]
First of all, we are going to set up the System Panel and add two more LED components to expand the program.
* Add two LED components by using either of the following methods:
:* Either copy and paste the current component on the System Panel to duplicate the component.
:* Or add two more components by using the [[Tools and Views#2) Components Toolbar|Components Toolbar]].

Now position the LEDs accordingly on the System Panel.
* Move the LEDs to be aligned in a row on the Y axis.
* Ensure the original green LED component is at the bottom and that it is still connected to '$PORTB.0'.

Next change the colour and connection properties of the two new LEDs.
* Change the middle LED properties.
:* Connect the LED to Port B Pin 1 by changing the 'Connection' property to '$PORTB.1'.
:* Change the 'Color' property to yellow (00FFFF) using the colour selection window.

* Change the top LED properties
:* Connect the LED to Port B Pin 2 by changing the 'Connection' property to '$PORTB.2'.
:* Change the 'Color' property to red (000FF) using the colour selection window.

==Expand the program==
Now that the components are set up correctly, its time to configure the flowchart and expand the program.
Firstly we need to set up the default state of the traffic lights to display only the red light when the switch is not pressed.
[[File:Exercise_Expanding_a_Program_Final_Flowchart.png|right]]
* Add an 'Input' icon to the 'No' section of the 'Decision' icon.
:* Change the 'Display name:' to "Red on".
:* Input the the value "1" into the 'Variable or value:' box.
:* Set the 'Port:' connection to 'PORTB'.
:* In the 'Output to:' section select 'Single Bit:' and change the pin to '2'.
:* Click 'OK' to confirm the changes to the icon.

We are now going to set up the activation sequence of the traffic lights by configuring and expanding the 'Yes' section of the 'Decision' icon.

* Add 4 'Input' icons above the existing icons, then add a 'Delay' icon in-between the 4 'Input' icons.
:* We will configure these icons top to bottom as follows:

* Change the 'Display name:' of the first 'Input' icon to "Red on".
:* This icon is the same as the previous one we set up in the 'No' section of the 'Decision icon'.
:* Send the value '1' to Port B, Pin 2.

* For the second 'Input' icon change the name to "Yellow on".
:* Similarly send the value '1' to Port B but this time send it to bit (pin) 1

* Next is the 'Delay' icon.
:* Change the name to "For 1 second".
:* Input the value "1" into the 'Delay value or variable:' box.
:* Change the unit to 'seconds'.

* Switch the first two (red and yellow) lights off to allow the last (green) light to show on its own which we programmed before.
:* Alter the 'Input' icon after the 'Delay' icon.
::* Change the 'Display name:' to "Red off".
::* Send the value "0" to Port B, Pin 1 - this switches off the red light.
:* Configure the next 'Input' icon, the last of the new icons we added.
::* Name it "Yellow off".
::* Send the value "0" to Port B, Pin 2 - this switches off the yellow light.

Next, the green light displays for 10 seconds before switching off, this is due to the icons we configured and programmed in the earlier exercises.
* Update the display names of the existing icons as follows:
:* Replace the "Switch on" display name with "Green on".
:* Replace the "Switch off" display name with "Green off".

* Under these icons add an 'Input' icon, followed by a 'Delay' icon and finally add the last 'Input' icon.
:* Configure the first 'Input' icon.
::* Change the 'Display name:' to "Yellow on".
::* In the 'Variable or value:' box type "1".
::* Change the 'Port:' to 'PORTB'.
::* In the 'Output to:' section select 'Single Bit:' and change the value to '1'.

:* Now configure the 'Delay' icon.
::* Change the 'Display name:' to "For 2 seconds".
::* Type "2" into the 'Delay value or variable:'.
::* Change the unit to 'seconds'

:* Finally configure the last 'Input' icon.
::* Change the 'Display name:' to "Yellow off".
::* In the 'Variable or value:' type "0".
::* Change the 'Port:' to 'PORTB'
::* In the 'Output to:' section select 'Single Bit:' and change it to '1'.

==Final testing==
* [[Saving a Flowchart|Save the flowchart]].
* [[Starting Flowchart Simulation|Run the simulation]] to test that it works.
* If you are going to further expand a program, or release it for public use, be sure to [[Exercise - Documenting a Flowchart|document the flowchart]] accordingly to explain the process and describe what affect it has on the components.

==What Next?==
Now you have effectively developed and expanded a program you can move on to other exercises and learn different areas, methods and techniques.

The next exercise available will show you how create an effective program using [[Component Macro Icon Properties|Component Macros]] and how to expand the program using Component Macros to increase efficiency. (See [[Exercise - Using Component Macros]])

==Link==
To download the Flowcode program for this exercise, click on the following link [[File:xxx|xxx]]

Exercise - Expanding a Program

2013-09-01T13:52:49Z

JohnVerrill:

<sidebar>Sidebar: Taking Flowcode Further</sidebar>
This exercise assumes you have created, tested and documented the program described in the exercise [[Exercise - Documenting a Flowchart|Documenting a Flowchart]].

Because you have documented the flowchart properly, you can easily and accurately change the program as you know exactly how the program functions and what process it goes through.

You do not have to massively alter your program to make it more effective, sometimes a little change can make a big difference, simply adding and configuring one component can change the program to be much more effective and suitable for use elsewhere.

__TOC__

==Load the Flowcode flowchart==
* [[Opening an Existing Flowchart|Open the flowchart]] called 'Lamp1.fcf' which you created earlier and documented in the exercise [[Exercise - Documenting a Flowchart|Documenting a Flowchart]].

==Enhancing a program==
Now that you have a fully functioning program which is properly documented both by display names of icons and detailed comments, you can manipulate this program integrate it into another system, or expand the program further and turn it into your own expanded system, and even turn it into a full application.

We are going to expand our program to function as a set of traffic lights, to do this we are going to add 2 more LEDs and add to our 'Decision' icon which responds to when the switch is on to activate the traffic lights accordingly.

==Add the LEDs==
[[File:Exercise_Expanding_a_Program_Components.png|right]]
First of all, we are going to set up the System Panel and add two more LED components to expand the program.
* Add two LED components by using either of the following methods:
:* Either copy and paste the current component on the System Panel to duplicate the component.
:* Or add two more components by using the [[Tools and Views#2) Components Toolbar|Components Toolbar]].

Now position the LEDs accordingly on the System Panel.
* Move the LEDs to be aligned in a row on the Y axis.
* Ensure the original green LED component is at the bottom and that it is still connected to '$PORTB.0'.

Next change the colour and connection properties of the two new LEDs.
* Change the middle LED properties.
:* Connect the LED to Port B Pin 1 by changing the 'Connection' property to '$PORTB.1'.
:* Change the 'Color' property to yellow (00FFFF) using the colour selection window.

* Change the top LED properties
:* Connect the LED to Port B Pin 2 by changing the 'Connection' property to '$PORTB.2'.
:* Change the 'Color' property to red (000FF) using the colour selection window.

==Expand the program==
Now that the components are set up correctly, its time to configure the flowchart and expand the program.
Firstly we need to set up the default state of the traffic lights to display only the red light when the switch is not pressed.
[[File:Exercise_Expanding_a_Program_Final_Flowchart.png|right]]
* Add an 'Input' icon to the 'No' section of the 'Decision' icon.
:* Change the 'Display name:' to "Red on".
:* Input the the value "1" into the 'Variable or value:' box.
:* Set the 'Port:' connection to 'PORTB'.
:* In the 'Output to:' section select 'Single Bit:' and change the pin to '2'.
:* Click 'OK' to confirm the changes to the icon.

We are now going to set up the activation sequence of the traffic lights by configuring and expanding the 'Yes' section of the 'Decision' icon.

* Add 4 'Input' icons above the existing icons, then add a 'Delay' icon in-between the 4 'Input' icons.
:* We will configure these icons top to bottom as follows:

* Change the 'Display name:' of the first 'Input' icon to "Red on".
:* This icon is the same as the previous one we set up in the 'No' section of the 'Decision icon'.
:* Send the value '1' to Port B, Pin 2.

* For the second 'Input' icon change the name to "Yellow on".
:* Similarly send the value '1' to Port B but this time send it to bit (pin) 1

* Next is the 'Delay' icon.
:* Change the name to "For 1 second".
:* Input the value "1" into the 'Delay value or variable:' box.
:* Change the unit to 'seconds'.

* Switch the first two (red and yellow) lights off to allow the last (green) light to show on its own which we programmed before.
:* Alter the 'Input' icon after the 'Delay' icon.
::* Change the 'Display name:' to "Red off".
::* Send the value "0" to Port B, Pin 1 - this switches off the red light.
:* Configure the next 'Input' icon, the last of the new icons we added.
::* Name it "Yellow off".
::* Send the value "0" to Port B, Pin 2 - this switches off the yellow light.

Next, the green light displays for 10 seconds before switching off, this is due to the icons we configured and programmed in the earlier exercises.
* Update the display names of the existing icons as follows:
:* Replace the "Switch on" display name with "Green on".
:* Replace the "Switch off" display name with "Green off".

* Under these icons add an 'Input' icon, followed by a 'Delay' icon and finally add the last 'Input' icon.
:* Configure the first 'Input' icon.
::* Change the 'Display name:' to "Yellow on".
::* In the 'Variable or value:' box type "1".
::* Change the 'Port:' to 'PORTB'.
::* In the 'Output to:' section select 'Single Bit:' and change the value to '1'.

:* Now configure the 'Delay' icon.
::* Change the 'Display name:' to "For 2 seconds".
::* Type "2" into the 'Delay value or variable:'.
::* Change the unit to 'seconds'

:* Finally configure the last 'Input' icon.
::* Change the 'Display name:' to "Yellow off".
::* In the 'Variable or value:' type "0".
::* Change the 'Port:' to 'PORTB'
::* In the 'Output to:' section select 'Single Bit:' and change it to '1'.

==Final testing==
* [[Saving a Flowchart|Save the flowchart]].
* [[Starting Flowchart Simulation|Run the simulation]] to test that it works.
* If you are going to further expand a program, or release it for public use, be sure to [[Exercise - Documenting a Flowchart|document the flowchart]] accordingly to explain the process and describe what affect it has on the components.

==What Next?==
Now you have effectively developed and expanded a program you can move on to other exercises and learn different areas, methods and techniques.

==Link==
To download the Flowcode program for this exercise, click on the following link [[File:xxx|xxx]]

The next exercise available will show you how create an effective program using [[Component Macro Icon Properties|Component Macros]] and how to expand the program using Component Macros to increase efficiency. (See [[Exercise - Using Component Macros]])

Exercise - Documenting a Flowchart

2013-09-01T13:52:09Z

JohnVerrill:

<sidebar>Sidebar: Adding Finishing Touches</sidebar>
This exercise assumes that you have created and tested the program described in exercise [[Exercise - Transferring a Program to the Microcontroller|Transferring a Program to the Microcontroller]].

Documenting the flowchart is essential in some projects, although we have properly labelled the icons, a few comment icons helps to further explain the program and the process in further detail to aid expansion and helps others understand the system.

__TOC__

==Load the Flowcode flowchart==
* [[Opening an Existing Flowchart|Open the flowchart]] called 'Lamp1.fcf' which you tested further in the exercise [[Exercise - Transferring a Program to the Microcontroller|Transferring a Program to the Microcontroller]].

==Benefits of documentation==

Documenting your flowchart is very useful - it allows other users to understand your flowchart and allows them to learn and even add to your flowchart to help produce the final program and increase efficiency throughout the system.

Adding comments to document your flowchart is extremely easy and very useful, using comments allows you to clarify the process, purpose and function of your program and allows others to understand it so they can see what is going on and learn from it and even help to develop the program, even by suggestion a more efficient method or directly editing a icon to function more effectively.

==Adding comments==
[[File:Exercise_Documenting_a_Flowchart_Final_Flowchart.png|right]]
* Drag a [[Comment Icon Properties|Comment icon]] onto the flowchart above the 'Loop' icon.
* Double click the 'Comment' icon to open up the [[Comment Icon Properties]] dialogue box.

:* Explain the purpose of the loop and how it is the base of the process.

:: The loop is the base of the program as it allows the program to continually check if the switch has been pressed by repeating the process of detecting the state of the switch.

* Add a comment above the 'Input' icon.

* Open the icon properties by double clicking on the 'Comment' icon.

:* Describe the use of the 'Input' icon and how it reads the state of the switch.

:: The 'Input' icon uses a variable to read and store the state of the switch, this allows the information contained in the variable to be used to see if the switch is being pressed or not.

* Comment and document the 'Decision' icon.

:* Describe how the 'Decision' icon detects the state of the switch and decides the next step to take.

:: The 'Decision' icon will read the information in the variable to see if the switch has been pressed, it then decides which process path to follow next, if it is not being pressed it will go straight through to the loop and continually check if the switch is being pressed or not. If the switch is being pressed the following icons activate the LED and turns it off after 10 seconds.

* Comment and document the 'Output' icon.

:* Describe the function of the 'Output' icon.

:: Once the 'Decision' icon detects that the switch is being pressed, the 'Output' icon turns on / lights up the LED and indicates that the switch has been pressed.

* Comment and document the 'Delay' icon.

:* Describe the function and purpose of the icon.

:: This delays the program and stops it from continuing with another process, this allows the LED to stay lit up due to the previous command, this delay lasts 10 seconds until the program is then continued.

* Comment and document the second 'Output' icon.

:* Explain the function of this icon and the process afterwards.

:: After the 10 second delay, this icon will turn the LED off and then continue the process of the program, which in turn, will loop to check if the button is being pressed again, this is the completes the circuit and will continue to loop and repeat the process, until stopped.

==Save the Flowchart==
* Save the flowchart using the same name. The simplest way to do this is to click on the 'Save' icon. [[File:Btn Save.png|border]]
: For more information, see [[Saving a Flowchart]].

==What Next?==
Now that the flowchart is complete, and documented correctly, you can further expand and develop the flowchart in the next exercise [[Exercise - Expanding a Program|Expanding a Program]].

==Link==
To download the Flowcode program for this exercise, click on the following link [[File:xxx|xxx]]

Exercise - Transferring a Program to the Microcontroller

2013-09-01T13:51:36Z

JohnVerrill:

<sidebar>Sidebar: Adding Finishing Touches</sidebar>
This exercise looks at transferring to the microcontroller, the flowchart 'Lamp1.fcf' which you tested and simulated in the exercise [[Exercise - Simulating a Program|Simulating a Program]]. 
This involves:
* Compiling the program (translating it into a form which the microcontroller can use).
* Moving it to the connected microcontroller.
* Storing it in the microcontroller's memory.
For more details about this part of the process, see [[Adding Finishing Touches]].

__NOTOC__

==Load the Flowcode Flowchart==

* [[Opening an Existing Flowchart|Open the flowchart]] called 'Lamp1.fcf' which you tested in the exercise [[Exercise - Simulating a Program|Simulating a Program]].

==Compile the program==
* Click on the 'Compile to chip' icon. [[File:Btn_Compile_Chip.png|border]]
: The 'Compiler Messages' box appears and shows the progress of the process.
: First of all, the program is converted into 'C' language.
: This is then translated into another language called 'Assembler'.
: Finally, the resulting code is transferred to the microcontroller.
: The good news is that all of this happens automatically, without the need for any intervention from you!

==What Next?==
Now you have tested that the program performs on hardware correctly, develop your flowchart further by documenting it for clear interpretation by others and for future expansion purposes as described in the exercise [[Exercise - Documenting a Flowchart]]

==Link==
To download the Flowcode program for this exercise, click on the following link [[File:xxx|xxx]]

Exercise - Simulating a Program

2013-09-01T13:51:13Z

JohnVerrill:

<sidebar>Sidebar: Overview of Simulation</sidebar>
This exercise looks at testing the flowchart 'Lamp1.fcf' which you developed in the exercise [[Exercise - Adding Devices to a Program|Adding Devices to a Program]]. 
The first part of this process is to simulate the flowchart. This tests the program only, and not the hardware.
It is done within the Flowcode program itself, and does not require that any hardware is present.
For more details about simulation, see [[Overview of Simulation]].

__TOC__

==Load the Flowcode Flowchart==

* [[Opening an Existing Flowchart|Open the flowchart]] you created earlier called 'Lamp1.fcf' which you expanded upon in the exercise [[Exercise - Adding Devices to a Program|Adding Devices to a Program]].

==Run the simulation==
* Click on the 'Run' icon, (or hit the F5 function key). [[File:Btn_Run.png|border]]
: The [[Simulation Debugger|Simulation debugger]] window may open - ignore it for now!
* Nothing happens until you switch the lamp on. To do this, click momentarily on the push switch.
: The lamp comes on and the 'Simulation Delay' window opens, as Flowcode simulates the ten second delay.
: At the end of this, the lamp goes off.
* You can repeat the process as many times as you like. When you are ready, click on the 'Stop simulation' icon, (or press the Shift and F5 keys). [[File:Btn_Stop.png|border]]

==Step through the simulation==
: When things don't go according to plan, it is useful to simulate the program step-by-step, (meaning icon-by-icon.)
: To do this:
:* Click on the 'Step Into' icon, (or press the F8 key). [[File:Btn_Step_Into.png|border]]
:: A red box appears around the first icon in the flowchart.
:: When you click on the icon again, the program executes that icon, and the red box moves onto the next icon.
:: In this way, you can check whether or not the expected actions happen.
* At any point, click on the 'Stop simulation' icon to end the simulation.
: For more information, see [[Simulating Icons Step by Step]].

==What Next?==
Once you have shown that the flowchart does what you want it to, the next step is to transfer the program to the microcontroller, and test that it runs the hardware as you want it to. That is covered in the exercise [[Exercise - Transferring a Program to the Microcontroller|Transferring a Program to the Microcontroller]].

==Link==
To download the Flowcode program for this exercise, click on the following link [[File:xxx|xxx]]

Exercise - Adding Devices to a Program

2013-09-01T13:50:47Z

JohnVerrill:

<sidebar>Sidebar: Controlling Electronic Devices With Flowcode</sidebar>
This exercise assumes that you have already built the Flowcode flowchart described in the exercise [[Exercise - Configuring Icons and Variables|Configuring Icons and Variables]]. 
To complete the program, you need to add the two electronic components, the switch and the lamp.

__TOC__

==Load the Flowcode Flowchart==

* Open the flowchart, called 'Lamp1.fcf' which you created in the exercise [[Exercise - Configuring Icons and Variables|Configuring Icons and Variables]].
:(For help with this, see the article [[Opening an Existing Flowchart]])
: The System Panel and Panel Properties should be visible. If not, use the [[View]] menu to select them.

==Add the Switch==
[[File:Exercise Adding Devices to a Program Switch Properties.png|300px|right]]
* Click on the 'Inputs' toolbox, and locate the 'Push Round Panel' [[File:Component Icon 5c1da48f ce54 4622 bdd9 fc812e373696.png]] switch.
* Hover over the image, and click on the down arrow that appears.
* Select the 'Add to system panel' option.

* Click on the switch on the [[System Panel]] to select it. Its properties appear in the Panel Properties.
: Notice that the name ('Handle') of the component selected appears at the top of the Panel Properties.
: In this case, it shows the name of the switch as 'sw_push_rnd_pnl'!

* Find the 'Connections' properties on the Panel Properties, the box to the right of it.
: A pinout of the microcontroller appears.
:* Ensure that it is connected to Port A bit 0 by using the drop down menus or clicking on the rectangle representing the pin for Port A bit 0 (called RA0/AN0 on the graphic.)
:: This connects the switch to Port A bit 0 of the microcontroller, matching the settings you used when you created the flowchart.
:: This setting is shown opposite.

:* No other properties need changing, though '[[Object Scale|Scale]]' allows you to change the size (and shape) of the switch if you wish.

==Add the Lamp==
[[File:Exercise Adding Devices to a Program LED Properties.png|300px|right]]
* Click on the 'Outputs' toolbox, and locate the 'Single LED', which we will use as a lamp.
* Hover over the image, and click on the down arrow that appears.
* Select the 'Add to system panel' option.
* The LED appears in the middle of the System Panel, probably right on top of the switch.
: It should already be selected, but if not click on it.
: If so, drag it to a suitable position off to one side.

* With the LED selected, look at the Panel Properties.
: Notice that the 'Handle' has changed to 'led'.
: The 'Connection' property may not be connected to the correctly, as the flowchart expects it to be connected to Port B, bit 0.
:* Click on the box next to the 'Connection' property and, as before, a pinout of the chip appears.
:* Click on the rectangle representing the pin for bit 0 of Port B, shown as RB0/INT or use the drop down menus to connect the component.
:: The Panel Properties now show that the LED is connected to Port B, bit 0.

:* Once again, no other properties need changing, though 'Scale' and 'Color' settings can be altered to change the size and color of the LED.

==Save the Flowchart==
* Save the flowchart using the same name. The simplest way to do this is to click on the 'Save' icon. [[File:Btn Save.png|border]]
: For more information, see [[Saving a Flowchart]].

==What Next?==
Now that the flowchart is complete, we are ready to test it in simulation, as described in the next exercise [[Exercise - Simulating a Program|Simulating a Program]].

==Link==
To download the Flowcode program for this exercise, click on the following link [[File:xxx|xxx]]

Exercise - Configuring Icons and Variables

2013-09-01T13:50:20Z

JohnVerrill:

<sidebar>Sidebar: Controlling Electronic Devices With Flowcode</sidebar>
This exercise assumes that you have already built the Flowcode flowchart described in the exercise [[Exercise - Creating a Flowchart|Creating a Flowchart]]. 
To set up and program the flowchart you must configure the icons and variables to create an effective and functioning process. 
This will prepare the program to interact with components connected to the specific ports.

__TOC__

==Load the Flowcode flowchart==
* Open the flowchart, called 'Lamp1.fcf' which you created in the exercise [[Exercise - Creating a Flowchart|Creating a Flowchart]].
:(For help with this, see the article [[Opening an Existing Flowchart]])
: The System Panel and Panel Properties should be visible. If not, use the [[View]] menu to select them.

==Program the sequence==

Now that the flowchart icons are correctly set up, we need to program them to carry out the following process:
:Check if the switch is pressed.
::If it isn't, go back to the beginning.
::If it is:
:::Switch on the lamp;
:::Wait for 10 seconds;
:::Switch off the lamp;
:::Go back to the beginning.

It takes such a short time for the microcontroller to carry this out, that we don't need to worry whether the switch latches on or not.

==Program the input==
:* Double click on the [[Input Icon Properties|Input icon]].
:: This opens the 'Properties: Input' dialogue box, allowing you to configure the way the program treats information from the switch.
:: This information will be contained in a variable called 'switch'.

::* Click on the down arrow at the right-hand end of the 'Variable:' box to open the variables dialogue box.
::* Hover to the left of the 'Variables' label and click on the down arrow that appears.
::* Click on the 'Add new' option to open the 'Create a New Variable' dialogue box.

::* [[Creating Variables|Create a new variable]] named "switch" with initial value "0" and description "Copies the state of the switch"
::* Leave the 'Variable type:' as 'Byte'.
::: (For more information about variables, see [[Creating Variables]] and [[Variable Types]].
::: (The resulting dialogue box is shown opposite.)
[[File:Exercise_Configuring_Icons_and_Variables_Input_Properties.png|250px|right]]

:* Finish configuring the input properties as follows:
::* Change the 'Display name:' to "Read the switch".
::* In the 'Variable:' box, type the name of the variable you created "switch".
::* Leave the 'Port:' as PORT A.
::* Select to 'Input from:' 'Single Bit' and choose bit 0.
::: (The resulting dialogue box is shown opposite.)

[[File:Exercise_Configuring_Icons_and_Variables_New_Variable.png|250px|right]]

: Set up like this, the program monitors the state of the switch, which will be connected to bit 0 of Port A of the microcontroller.
: When the program looks at the input switch if it is pressed, the variable 'switch' contains logic 1. If unpressed, it contains logic 0.

==Check the Switch==
:* Double click on the [[Decision Icon Properties|Decision icon]] to open the configuration dialogue box, and then: [[File:Exercise_Configuring_Icons_and_Variables_Decision_Properties.png|250px|right]]
::* Rename it "Switch pressed?".
::* In the 'If:' box, type "switch=1".
::* Leave the 'Swap Yes and No' box unchecked.
::* Click on 'OK'.

: This will cause the program to perform what is known as a conditional branch.
: The subsequent course of the program depends on the outcome of the condition specified in the 'Decision' icon.
: In this case, it depends on whether or not the variable 'switch' = 1.
: If it is, the program follows the 'Yes' route. If not, it follows the 'No' route.

==Control the Lamp==
: The 'No' branch is easy to set up. All we want is that the program returns to the beginning (taken care of by the 'Loop' icon.)
: No further configuration is needed.
[[File:Exercise_Configuring_Icons_and_Variables_Output_Properties_01.png|250px|right]]

:* Double click the [[Output Icon Properties|Output icon]] to open the configuration dialogue box, and then:
::* Change the 'Display name:' to "Switch on".
::* In the 'Variable or value:' box, type value "1".
::* Change the 'Port:' to PORT B.
::* Select to 'Output to: 'Single Bit' and choose bit 0.
::* Click on 'OK'.
::: (The resulting dialogue box is shown opposite.)

: The effect of this icon is to send a logic 1 signal (high voltage) to the lamp, connected to Port B, bit 0 of the microcontroller.
: This turns on the lamp.

: Now, we tackle the requirement that it stays on for ten seconds and then goes off.
[[File:Exercise_Configuring_Icons_and_Variables_Delay_Properties.png|250px|right]]
* Drag and drop a [[Delay Icon Properties|Delay icon]] after the 'Output' icon.
:* Double click on it to open the configuration dialogue box, and then:
::* Change the 'Display name:' to "For 10 seconds".
::* Change the 'Delay value:' to '10'.
::* Change the unit to 'seconds'.
::* Click on 'OK'.
::: (The resulting dialogue box is shown opposite.)
[[File:Exercise_Configuring_Icons_and_Variables_Output_Properties_02.png|250px|right]]

: Finally, we need to turn off the lamp, after the ten second delay.
* Double click on the second 'Output' icon to allow you to configure it.
:* Rename it "Switch off", and configure it to deliver value "0" to single bit 0 of Port B.
:: (The resulting dialogue box is shown opposite.)

You should now [[Saving a Flowchart|save the flowchart]] as "Lamp1.fcf", and [[Closing Flowcode|close Flowcode]].

==What next==
The next step is to add the switch and lamp to the flowchart. This is covered in the exercise [[Exercise - Adding Devices to a Program|Adding Devices to a Program]].

==Link==
To download the Flowcode program for this exercise, click on the following link [[File:xxx|xxx]]

Exercise - Creating a Flowchart

2013-09-01T13:49:48Z

JohnVerrill:

<sidebar>Sidebar: What Is a Flowcode Flowchart?</sidebar>
The task is to produce a Flowcode flowchart which will set the base of a program that will, when configured and programmed correctly, light a lamp for ten seconds when a switch is pressed. Note that we will not be configuring the flowchart icons to function in this exercise, we are just setting up the base to be expanded upon. 
Although it may not be realistic to use a microcontroller in such a straight-forward application, it illustrates the technique of producing a Flowcode program. 
The program itself may form part of a bigger program.

__TOC__

==Formulate the sequence==
The flowchart sequence will be:
: Check if the switch is pressed.
:: If it isn't, go back to the beginning.
:: If it is:
::: Switch on the lamp;
::: Wait for 10 seconds;
::: Switch off the lamp;
::: Go back to the beginning.

It takes such a short time for the microcontroller to carry this out, that we don't need to worry whether the switch latches on or not.

==Set up the flowchart==
[[File:Gen_Startup_Selection.png||250px|right]]
* [[Opening Flowcode|Open Flowcode]].
* On the Startup screen, click on 'New project'.

[[File:Gen_Project_Options_Target_SIM.png|right|250px]]
: The [[Project Options]] dialogue box opens.
: (Click on the link for a full explanation of all the options available.)

* Accept the default settings by clicking on 'OK'.
: An empty flowchart window opens, which may contain other items such as a [[System Panel]], [[Dashboard Panel]], [[Properties Panel]] etc.
: These can be revealed or hidden using the [[View]] menu.

* Set up the flowchart window so that you can see the System Panel and the Properties Panel.
: The flowchart window should resemble the one shown below (depending on the configuration.)

[[File:Exercise_Creating_a_Flowchart_Flowcode_Layout.png|500px|center]]

: The System Panel and Properties Panel can be moved by clicking and dragging the title bar at the top of each panel.

==Prepare the input==
: More information about the icons used in this flowchart can be found in [[Icon Properties]].
* Drag and drop a [[Loop Icon Properties|Loop icon]] between the BEGIN and END icons.
: The 'Loop' icon will make the microcontroller repeatedly run through the program, (though the icon can be configured to limit the number of times this happens.)

* Inside the loop, drag and drop an [[Input Icon Properties|Input icon]] from the [[Tools and Views#1) Icons Toolbar|Icons toolbar]].
:* This will be configured later and contain a variable value which will be used to read the state of the switch - to detect if the switch is being pressed..

==Prepare the switch==
* Drag and drop a [[Decision Icon Properties|Decision icon]] after the 'Input' icon.
: This icon will be used to make the program perform what is known as a conditional branch when the following icons are configured.

[[File:Exercise_Creating_a_Flowchart_Icons_Layout.png|right]]

: When the icons are configured and programmed, these icons will be able to continually check if the switch is being pressed or not.
: In the next step we will be adding icons which will allow us to control what happens if the switch is pressed. Note that the program will not function until the icons are configured and programmed.

: Once programmed - when the switch is pressed it will perform an the action or process and continue to check if it is being pressed again.
: If the switch is not pressed it will follow the 'No' branch and keep looping to continue to check if the switch has been pressed.

==Set up the lamp==
: Next we concentrate on the 'Yes' branch of the 'Decision' icon.
* Drag and drop an [[Output Icon Properties|Output icon]] in the 'Yes' branch.
: When programmed, this icon is going to function as a trigger to turn the lamp on.

: Next we want the lamp to stay on for ten seconds and then turn off.
* Drag and drop a [[Delay Icon Properties|Delay icon]] after the 'Output' icon.
:* This is the icon which will allow us to delay the circuit for a specified period of time.
:* The delay will last for 10 seconds, in this time the circuit will not be able to carry out any other function until the delay is complete.

:* Drag and drop a second 'Output' icon after the 'Delay' icon.
: Finally this will be used to turn the lamp off after the ten second delay.

Your flowchart should now be set up to resemble the image to the right. Note that none of the icons are configured yet, so the program will not simulate or function, please see the next exercise to configure the icons so that the program will simulate accordingly.

You should now [[Saving a Flowchart|save the flowchart]] as "Lamp1.fcf", and [[Closing Flowcode|close Flowcode]].

==What next==
The flowchart is now ready to be configured and programmed in order to operate electronic devices (components). The configuration of the flowchart is covered in the exercise [[Exercise - Configuring Icons and Variables|Configuring Icons and Variables]].

==Link==
To download the Flowcode program for this exercise, click on the following link [[File:xxx|xxx]]

Exercise - Using Analogue Input Devices

2013-08-30T13:59:09Z

JohnVerrill:

<sidebar>Sidebar: Advanced Features</sidebar>
The aim of this exercise is to demonstrate the use of analogue input devices within a Flowcode flowchart.

Digital inputs are simpler to deal with, as they have a finite range of possible values. 
For example, a two bit digital input can have one of only four possible values - 00, 01, 10 or 11. 
Flowcode uses an 'Input' icon [[File:Btn Input.gif|border]] to deal with digital inputs.

An analogue input, on the other hand can have any of an infinite number of possible values. 
As a result, it is more difficult to handle in Flowcode.
[[File:Exercise_Using_Analogue_Input_Devices_System_Panel.png|300px|right]]
A component macro [[File:Btn Component Macro.gif|border]] is used to input data from an analogue sensor. 
The data is then stored in a variable.

Component macros are sections of code that have been written to support the components included with Flowcode 6. 
They take all the effort out of using these components.

In this exercise, a warning lamp lights when the signal from an ADC dial device rises too far.

__TOC__

==The flowchart sequence==
The flowchart will:
::::* Read the value set on the input device, the ADC dial.
::::* Compare this with a set value, and:
::::: if greater than the set value, turn on a lamp;
::::: if less, then make sure that the lamp is off.
::::* Loop back to the beginning, and repeat the process.

[[File:Exercise_Using_Analogue_Input_Devices_Variable_Manager.png|300px|right]]
==Create the 'input' variable==
:* In the 'Edit' menu, on the main toolbar, click on 'Variables...' to open the [[Variable Manager]] dialogue box.
::* Hover just to the left of the 'Variables' label, and click on the down arrow that appears.
::* Select 'Add new' and the 'Create a New Variable' dialogue box opens.
::* Name the new variable "input".
::* Leave the variable type as 'Byte'.
::* Click on 'OK'.
::* The dialogue box is shown opposite.

==Create the flowchart==
* Click and drag an infinite loop, [[File:Btn Loop.gif|border]] between the 'BEGIN' and 'END' icons.

[[File:Exercise_Using_Analogue_Input_Devices_Component_Macro_Properties.png|300px|right]]
* Inside the loop:
:* Click and drag a 'Component macro' icon.[[File:Btn_Component_Macro.gif|border]]
::* Double click on it to open the dialogue box, so that you can configure it.
::: The program 'knows' which components you have added to the System or Dashboard panel, and modifies the list of available commands accordingly.
::: Under 'Components', the ADC dial will be listed, and underneath it the list of commands.
::* Scroll down the list and click on the 'GetByte' command.
::: This reads the output of the analogue input device - the ADC dial in this case, and stores it in the byte variable called 'input'.
::* Rename the 'Display name' as "Read the input".
::* Click on 'OK'.
::* Again, the dialogue box is shown opposite.

* Next, drag and drop a 'Decision' box, [[File:Btn Decision.gif|border]] and double click on it to open the dialogue box.
[[File:Exercise_Using_Analogue_Input_Devices_Decision_Properties.png|300px|right]]
:* Rename it "Compare it !"
:* In the condition 'If' box, type "input>128".
:: The '128' is totally arbitrary in this program. A byte variable can store any value from 0 to 255, so 128 is roughly half way.
:: In this case, the program decides whether the value stored in the variable 'input' is greater or smaller than 128, and reacts differently depending on that decision.
:* Click on 'OK'.
::* Again, the resulting dialogue box is shown opposite.

[[File:Exercise_Using_Analogue_Input_Devices_Output_Properties_01.png|300px|right]]
* In the 'Yes' branch, drag and drop an 'Output' icon, [[File:Btn Output.gif|border]].
:* Double click on it to open the dialogue box.
:* Change the 'Display name:' to "Switch on the lamp".
:* In the 'Variable or value:' box, type "1".
:* Configure the rest of the box to output this to 'PORT A' 'Single Bit:' 0.
:* Click on 'OK'.

[[File:Exercise_Using_Analogue_Input_Devices_Output_Properties_02.png|300px|right]]
* In the 'No' branch, drag and drop a second 'Output' icon.
:* Double click on it to open the dialogue box.
:* Change the 'Display name:' to "Switch off the lamp".
:* In the 'Variable or value:' box, type "0".
:* Configure the rest of the box to output this to 'PORT A' 'Single Bit:' 0.
:* Click on 'OK'.
::* Again, the dialogue boxes for the 'Output' icons are shown opposite.

The flowchart should now resemble the one shown below.
[[File:Exercise_Using_Analogue_Input_Devices_Flowchart.png|300px|center]]

==Add the LED==
* Locate the 'Single LED' in the 'Outputs' toolbox in the [[Tools and Views#1) Icons Toolbar|Icons toolbar]].
:* Hover over the image to the left of the 'Single LED' label, and click on the down-arrow that appears.
:* Click on the 'Add to system panel' option to select it.
:* Select the LED on the System panel and drag it to a suitable position.
:* Look at the Panel Properties, the 'Connection' property shows that, by default, it is connected to Port A, bit 0.
:: Leave it like this.

==Add the ADC dial==
The ADC dial represents a number of input devices.
* Locate the 'ADC dial' in the 'Inputs' toolbox in the [[Tools and Views#1) Icons Toolbar|Icons toolbar]].
:* Hover over the image to the left of the label, and click on the down-arrow that appears.
:* Click on the 'Add to system panel' option to select it.
:* Select the ADC dial on the System panel and drag it to a suitable position.
:* Look at the Panel Properties, and locate the 'Connection' property. Just below it, the 'Channel' property shows that, by default, it is connected to 'AN0' - the first bit of the microcontroller capable of accepting an analogue input. Click on 'AN0' to open a pinout of the microcontroller.
::* Click on the rectangle representing input 'AN1' to change the connection to this channel.
:: Leave it like this.

The System Panel should resemble the image shown at the top of the page.

==Final testing==
* Save the flowchart as 'Analogue,fcf'.
* Click on the simulation button [[File:Btn Run.png|border]].
* Use the mouse to turn the pointer on the ADC dial, and notice what happens when you pass the half-way mark.
* Click on the 'Stop simulation' button, [[File:Btn Stop.png|border]] when you are happy with the program's behavior.

==Link==
To download the Flowcode program for this exercise, click on this link [[File:Exercise AnInputs Analogue input1.fcf|Analogue Input 1]]

Exercise - Using Analogue Input Devices

2013-08-30T13:55:14Z

JohnVerrill:

<sidebar>Sidebar: What Is a Component?</sidebar>
The aim of this exercise is to demonstrate the use of analogue input devices within a Flowcode flowchart.

Digital inputs are simpler to deal with, as they have a finite range of possible values. 
For example, a two bit digital input can have one of only four possible values - 00, 01, 10 or 11. 
Flowcode uses an 'Input' icon [[File:Btn Input.gif|border]] to deal with digital inputs.

An analogue input, on the other hand can have any of an infinite number of possible values. 
As a result, it is more difficult to handle in Flowcode.
[[File:Exercise_Using_Analogue_Input_Devices_System_Panel.png|300px|right]]
A component macro [[File:Btn Component Macro.gif|border]] is used to input data from an analogue sensor. 
The data is then stored in a variable.

Component macros are sections of code that have been written to support the components included with Flowcode 6. 
They take all the effort out of using these components.

In this exercise, a warning lamp lights when the signal from an ADC dial device rises too far.

__TOC__

==The flowchart sequence==
The flowchart will:
::::* Read the value set on the input device, the ADC dial.
::::* Compare this with a set value, and:
::::: if greater than the set value, turn on a lamp;
::::: if less, then make sure that the lamp is off.
::::* Loop back to the beginning, and repeat the process.

[[File:Exercise_Using_Analogue_Input_Devices_Variable_Manager.png|300px|right]]
==Create the 'input' variable==
:* In the 'Edit' menu, on the main toolbar, click on 'Variables...' to open the [[Variable Manager]] dialogue box.
::* Hover just to the left of the 'Variables' label, and click on the down arrow that appears.
::* Select 'Add new' and the 'Create a New Variable' dialogue box opens.
::* Name the new variable "input".
::* Leave the variable type as 'Byte'.
::* Click on 'OK'.
::* The dialogue box is shown opposite.

==Create the flowchart==
* Click and drag an infinite loop, [[File:Btn Loop.gif|border]] between the 'BEGIN' and 'END' icons.

[[File:Exercise_Using_Analogue_Input_Devices_Component_Macro_Properties.png|300px|right]]
* Inside the loop:
:* Click and drag a 'Component macro' icon.[[File:Btn_Component_Macro.gif|border]]
::* Double click on it to open the dialogue box, so that you can configure it.
::: The program 'knows' which components you have added to the System or Dashboard panel, and modifies the list of available commands accordingly.
::: Under 'Components', the ADC dial will be listed, and underneath it the list of commands.
::* Scroll down the list and click on the 'GetByte' command.
::: This reads the output of the analogue input device - the ADC dial in this case, and stores it in the byte variable called 'input'.
::* Rename the 'Display name' as "Read the input".
::* Click on 'OK'.
::* Again, the dialogue box is shown opposite.

* Next, drag and drop a 'Decision' box, [[File:Btn Decision.gif|border]] and double click on it to open the dialogue box.
[[File:Exercise_Using_Analogue_Input_Devices_Decision_Properties.png|300px|right]]
:* Rename it "Compare it !"
:* In the condition 'If' box, type "input>128".
:: The '128' is totally arbitrary in this program. A byte variable can store any value from 0 to 255, so 128 is roughly half way.
:: In this case, the program decides whether the value stored in the variable 'input' is greater or smaller than 128, and reacts differently depending on that decision.
:* Click on 'OK'.
::* Again, the resulting dialogue box is shown opposite.

[[File:Exercise_Using_Analogue_Input_Devices_Output_Properties_01.png|300px|right]]
* In the 'Yes' branch, drag and drop an 'Output' icon, [[File:Btn Output.gif|border]].
:* Double click on it to open the dialogue box.
:* Change the 'Display name:' to "Switch on the lamp".
:* In the 'Variable or value:' box, type "1".
:* Configure the rest of the box to output this to 'PORT A' 'Single Bit:' 0.
:* Click on 'OK'.

[[File:Exercise_Using_Analogue_Input_Devices_Output_Properties_02.png|300px|right]]
* In the 'No' branch, drag and drop a second 'Output' icon.
:* Double click on it to open the dialogue box.
:* Change the 'Display name:' to "Switch off the lamp".
:* In the 'Variable or value:' box, type "0".
:* Configure the rest of the box to output this to 'PORT A' 'Single Bit:' 0.
:* Click on 'OK'.
::* Again, the dialogue boxes for the 'Output' icons are shown opposite.

The flowchart should now resemble the one shown below.
[[File:Exercise_Using_Analogue_Input_Devices_Flowchart.png|300px|center]]

==Add the LED==
* Locate the 'Single LED' in the 'Outputs' toolbox in the [[Tools and Views#1) Icons Toolbar|Icons toolbar]].
:* Hover over the image to the left of the 'Single LED' label, and click on the down-arrow that appears.
:* Click on the 'Add to system panel' option to select it.
:* Select the LED on the System panel and drag it to a suitable position.
:* Look at the Panel Properties, the 'Connection' property shows that, by default, it is connected to Port A, bit 0.
:: Leave it like this.

==Add the ADC dial==
The ADC dial represents a number of input devices.
* Locate the 'ADC dial' in the 'Inputs' toolbox in the [[Tools and Views#1) Icons Toolbar|Icons toolbar]].
:* Hover over the image to the left of the label, and click on the down-arrow that appears.
:* Click on the 'Add to system panel' option to select it.
:* Select the ADC dial on the System panel and drag it to a suitable position.
:* Look at the Panel Properties, and locate the 'Connection' property. Just below it, the 'Channel' property shows that, by default, it is connected to 'AN0' - the first bit of the microcontroller capable of accepting an analogue input. Click on 'AN0' to open a pinout of the microcontroller.
::* Click on the rectangle representing input 'AN1' to change the connection to this channel.
:: Leave it like this.

The System Panel should resemble the image shown at the top of the page.

==Final testing==
* Save the flowchart as 'Analogue,fcf'.
* Click on the simulation button [[File:Btn Run.png|border]].
* Use the mouse to turn the pointer on the ADC dial, and notice what happens when you pass the half-way mark.
* Click on the 'Stop simulation' button, [[File:Btn Stop.png|border]] when you are happy with the program's behavior.

==Link==
To download the Flowcode program for this exercise, click on this link [[File:Exercise_AnInput_

Exercise - Using Simulation Macros

2013-08-30T13:30:58Z

JohnVerrill:

Exercise - Using Simulation Macros

2013-08-30T13:30:00Z

JohnVerrill:

<sidebar>Sidebar: What Is a Macro?</sidebar>
Simulation macros are a form of Component macros. Their purpose is to make simulation more realistic by adding physical components to the electronic devices.

When the Flowcode program is compiled and downloaded to a microcontroller, they are ignored - hence the name Simulation macros.

Even a cursory glance at the dialogue box used to configure them shows that they are very powerful devices, with a huge range of possible effects.

This exercise uses three of them to illustrate the use of a PIR (Passive Infra-Red sensor) to operate an intruder sensor.

__TOC__

==The scenario==

The scene depicts the front of a house.
[[File:Exercise SimIcon pan.png|center|350px]]

A PIR sensor is mounted on the wall of the house, above the path leading across the garden.

The data sheet for the PIR shows that it is sensitive to a range of 10 metres, within a cone of angle 100 degrees.

Its detection area is represented in the image by the pale blue cone.

When an intruder enters the detection cone, a warning lamp lights up in the house.

This exercise allows us to investigate factors such as the height of the sensor on the brick wall and the angle of the detection zone, so that these can be optimised for a typical intruder height.

==The System Panel==

On the System Panel, viewed from above (the default position,)create:
* '''a brick wall''', represented by adding a red cuboid and changing it to a rectangle, 15mm wide, 120mm high and 120mm deep,
:: located at coordinates x = 0, y = 0, z = 60,
:: with rotation settings X = 0, Y = 0, Z = 0;

* '''a path''', represented by a grey rectangle, 240mm wide, 100mm high and 0mm deep,
:: located at coordinatesx = 125mm, y = 0mm, z = 0mm,
:: with rotation settings of X = 0, Y = 0, Z = 0;

* '''a cone''', couloured light blue, representing the sensing region of the PIR, with width = 70mm, height = 250mm, depth 95mm,
:: located at coordinates x = 45mm, y = 0mm, z = 80mm,
:: with rotation settings of X = 0, Y = -55, Z = 0.

* Drag the mouse cursor over these three elements and group them together.

This produces 'group 1'.
:: Give this group:
::: dimensions - width = 265mm, height = 250mm, depth = 135mm;
::: coordinates - x = 128, y = 0, z = 68;
::: rotation - X = 0, Y = 0, Z = 0.

Also on the System Panel, create an intruder, by:
* adding four spheres, and configuring the properties as follows:
:: sphere 1 ('''the head'''):
::: colour pink;
::: dimensions - width = 12mm, height = 13mm, depth = 15mm;
::: coordinates - x = -2.2, y = 0.7, z = 22;
::: rotation - X = 90, Y = 0, Z = 0.

:: sphere 2 ('''the body'''):
::: colour blue;
::: dimensions - width = 14mm, height = 26mm, depth = 24mm;
::: coordinates - x = -2.2, y = 0.5, z = 4;
::: rotation - X = 90, Y = 0, Z = -180.

:: sphere 3 ('''the legs'''):
::: colour dark green;
::: dimensions - width = 9mm, height = 23mm, depth = 15mm;
::: coordinates - x = -2.2, y = 1, z = -16;
::: rotation - X = 90, Y = 0, Z = -180.

:: sphere 4 ('''the feet'''):
::: colour black;
::: dimensions - width = 6mm, height = 15mm, depth = 25mm;
::: coordinates - x = -6, y = 0, z = -25;
::: rotation - X = 90, Y = 90, Z = 0.

* Drag the mouse cursor over the four spheres and group them together.

This produces 'group 2'.
:: Give it:
::: dimensions - width = 18mm, height = 32mm, depth = 60mm;
::: coordinates - x = 165, y = 0, z = 28;
::: rotation - X = 0, Y = 0, Z = 0.

The System Panel should resemble the image shown above. (The image has been rotated to show all components. The table-top is coloured green.)

Click on the 'Collisions' icon, [[File:Gen Panel Object Collision Move Around.png|35px]] and select the 'Move through' option, which allows the intruder to enter the detection cone.

==The Dashboard Panel==
[[File:Exercise SimIcon dash.png|right|200px]]
* Open the 'Outputs' toolbox, and locate the 'LED 5mm Panel' device.
* Click on the down arrow next to it and choose the 'Add to dashboard panel' option.
* Zoom in to the Dashboard Panel to make the LED large enough to see.
* Click on the LED and configure its properties as follows:
::* choose a suitable colour, such as red;
::* connect it to Port A, bit 0.

==The Flowcode program==
'''The plan:'''
* Set the initial position of the intruder, using the 'MoveTo' simulation macro.

* Move the intruder towards the detection cone using the 'MoveAlong' simulation macro.
:: This '''changes''' the x coordinate of the intruder '''by an amount specified by the variable 'xpos''''.

* When the intruder enters the detection zone, the simulation macro 'CollisionTest' returns a value of '1' in the variable 'hit'.
:: At this point, we stop any more movement so that we can look at the x coordinate of the intruder.
:: To do so, we change the value of 'xpos' to zero.

'''Implementation:'''

* [[Opening Flowcode|Open Flowcode]].

* On the Startup screen, click on 'New project' to [[Creating Flowcharts|create a new flowchart]].

* Add the icons shown in the flowchart:
:* a loop icon, configured as an infinite loop, and within it:
::* a Simulation macro icon[[File:Btn Simulation Macro.gif|border]];
::* a second loop;
::* a Calculation icon.

:* Within the second loop, add:
::* two more Simulation macro icons;
::* a decision icon with:
:::* a 'Yes' loop containing an output icon, followed by a delay icon and then a calculation icon;
:::* a 'No' loop containing an output icon, followed by a delay icon;

[[File:Exercise_SimIcon_Simmove.png|right|250px]]

* Configure the icons, by double clicking on each in turn, as follows:
::* the top Simulation macro:
:::* name it "Set initial position";
:::* click on the 'Panel' tab, and then on the 'Position' folder;
:::* click on the 'MoveTo' macro and:
::::* choose 'group2'(the intruder)as the Handle;
::::* set the X value to "200";
::::* set the Y value to "0";
::::* set the Z value to "28";
::::* click on OK.

::* the second loop:
:::* set it to 'Loop while:' "hit = 0";
:::* 'Test the loop at the:' 'End'
:::* Click on OK.

[[File:Exercise_SimIcon_Moveint.png|right|350px]]

::* the second Simulation macro:
:::* name it "Move the intruder";
:::* click on the 'Panel' tab, and then on the 'Position' folder;
:::* click on the 'MoveAlong' macro and:
::::* choose 'group2'(the intruder)as the Handle;
::::* choose 'shape1'( the brick wall) as the Axis;
::::* click on the down arrow on the end of the 'X' row, and create a floating point variable called "xpos", with an initial value 5.0, to use as the X variable;
::::* click on OK.

[[File:Exercise SimIcon Simcheck.png|right|250px]]

::* the third Simulation macro:
:::* name it "Check detection";
:::* click on the 'Panel' tab, and then on the 'Collision' folder;
:::* click on the 'TestSingle' macro and:
::::* choose 'shape2'(the detection cone) for 'Pos' and 'shape5' (the intruder's head,) for 'Test';
:::* use the down arrow at the end of the 'Return Value' box to create a boolean variable caled "hit" to use as the 'Return Value'.
::::* click on OK.

::* the decision icon:
:::* name it "Intruder detected?";
:::* insert the condition "hit = 1";
:::* click on OK.

:::* In the 'Yes' loop:
::::* name the Output icon "Switch on lamp";
::::* send value '1' to Port A single bit 0;
::::* click on OK.

::::* name the Delay icon "Wait 100ms";
::::* configure it to give a delay of 100ms;
::::* click on OK.

::::* name the Calculation icon "Stop movement";
::::* in the 'Calculations:' box, insert "xpos = 0" to reduce the distance incremented each time to zero;
::::* click on OK.

:::* In the 'No' loop:
::::* name the Output icon "Switch off lamp";
::::* send value '0' to Port A single bit 0;
::::* click on OK.

::::* name the Delay icon "Wait 100ms";
::::* configure it to give a delay of 100ms;
::::* click on OK.

::* the final Calculation icon:
::::* name it "Reset variables";
::::* in the 'Calculations:' box, insert "hit = 0" and "xpos = 5.0";
::::* click on OK.

The Flowcode flowchart resembles the one shown below:

[[File:Exercise SimIcon Simflow.png|center|500px]]
==Testing==

* Run the simulation.
: The intruder should move towards the house, until he enters the detection zone.

: At this point, the warning lamp turns on and he stops for three seconds.

: Then the simulation repeats.

* Stop the simulation when the lamp is lit, and click on the image of the intruder. You can now read the x coordinate from the Panel properties box.

* Change the height of the PIR sensor on the wall, or the angle of the detection cone, and see what happens to this coordinate.

==DON'T DOWNLOAD IT!!==
The important point is that the two Simulation macros do not compile to code that can be downloaded to a microcontroller. They affect only the simulation of the program.

File:Exercise SimIcon Moveint.png

2013-08-30T13:17:02Z

JohnVerrill:

Exercise - Using Simulation Macros

2013-08-30T13:15:22Z

JohnVerrill:

<sidebar>Sidebar: What Is a Macro?</sidebar>
Simulation macros are a form of Component macros. Their purpose is to make simulation more realistic by adding physical components to the electronic devices.

When the Flowcode program is compiled and downloaded to a microcontroller, they are ignored - hence the name Simulation macros.

Even a cursory glance at the dialogue box used to configure them shows that they are very powerful devices, with a huge range of possible effects.

This exercise uses three of them to illustrate the use of a PIR (Passive Infra-Red sensor) to operate an intruder sensor.

__TOC__

==The scenario==

The scene depicts the front of a house.
[[File:Exercise SimIcon pan.png|center|350px]]

A PIR sensor is mounted on the wall of the house, above the path leading across the garden.

The data sheet for the PIR shows that it is sensitive to a range of 10 metres, within a cone of angle 100 degrees.

Its detection area is represented in the image by the pale blue cone.

When an intruder enters the detection cone, a warning lamp lights up in the house.

This exercise allows us to investigate factors such as the height of the sensor on the brick wall and the angle of the detection zone, so that these can be optimised for a typical intruder height.

==The System Panel==

On the System Panel, viewed from above (the default position,)create:
* '''a brick wall''', represented by adding a red cuboid and changing it to a rectangle, 15mm wide, 120mm high and 120mm deep,
:: located at coordinates x = 0, y = 0, z = 60,
:: with rotation settings X = 0, Y = 0, Z = 0;

* '''a path''', represented by a grey rectangle, 240mm wide, 100mm high and 0mm deep,
:: located at coordinatesx = 125mm, y = 0mm, z = 0mm,
:: with rotation settings of X = 0, Y = 0, Z = 0;

* '''a cone''', couloured light blue, representing the sensing region of the PIR, with width = 70mm, height = 250mm, depth 95mm,
:: located at coordinates x = 45mm, y = 0mm, z = 80mm,
:: with rotation settings of X = 0, Y = -55, Z = 0.

* Drag the mouse cursor over these three elements and group them together.

This produces 'group 1'.
:: Give this group:
::: dimensions - width = 265mm, height = 250mm, depth = 135mm;
::: coordinates - x = 128, y = 0, z = 68;
::: rotation - X = 0, Y = 0, Z = 0.

Also on the System Panel, create an intruder, by:
* adding four spheres, and configuring the properties as follows:
:: sphere 1 ('''the head'''):
::: colour pink;
::: dimensions - width = 12mm, height = 13mm, depth = 15mm;
::: coordinates - x = -2.2, y = 0.7, z = 22;
::: rotation - X = 90, Y = 0, Z = 0.

:: sphere 2 ('''the body'''):
::: colour blue;
::: dimensions - width = 14mm, height = 26mm, depth = 24mm;
::: coordinates - x = -2.2, y = 0.5, z = 4;
::: rotation - X = 90, Y = 0, Z = -180.

:: sphere 3 ('''the legs'''):
::: colour dark green;
::: dimensions - width = 9mm, height = 23mm, depth = 15mm;
::: coordinates - x = -2.2, y = 1, z = -16;
::: rotation - X = 90, Y = 0, Z = -180.

:: sphere 4 ('''the feet'''):
::: colour black;
::: dimensions - width = 6mm, height = 15mm, depth = 25mm;
::: coordinates - x = -6, y = 0, z = -25;
::: rotation - X = 90, Y = 90, Z = 0.

* Drag the mouse cursor over the four spheres and group them together.

This produces 'group 2'.
:: Give it:
::: dimensions - width = 18mm, height = 32mm, depth = 60mm;
::: coordinates - x = 165, y = 0, z = 28;
::: rotation - X = 0, Y = 0, Z = 0.

The System Panel should resemble the image shown above. (The image has been rotated to show all components. The table-top is coloured green.)

Click on the 'Collisions' icon, [[File:Gen Panel Object Collision Move Around.png|35px]] and select the 'Move through' option, which allows the intruder to enter the detection cone.

==The Dashboard Panel==
[[File:Exercise SimIcon dash.png|right|200px]]
* Open the 'Outputs' toolbox, and locate the 'LED 5mm Panel' device.
* Click on the down arrow next to it and choose the 'Add to dashboard panel' option.
* Zoom in to the Dashboard Panel to make the LED large enough to see.
* Click on the LED and configure its properties as follows:
::* choose a suitable colour, such as red;
::* connect it to Port A, bit 0.

==The Flowcode program==
'''The plan:'''
* Set the initial position of the intruder, using the 'MoveTo' simulation macro.

* Move the intruder towards the detection cone using the 'MoveAlong' simulation macro.
:: This '''changes''' the x coordinate of the intruder '''by an amount specified by the variable 'xpos''''.

* When the intruder enters the detection zone, the simulation macro 'CollisionTest' returns a value of '1' in the variable 'hit'.
:: At this point, we stop any more movement so that we can look at the x coordinate of the intruder.
:: To do so, we change the value of 'xpos' to zero.

'''Implementation:'''

* [[Opening Flowcode|Open Flowcode]].

* On the Startup screen, click on 'New project' to [[Creating Flowcharts|create a new flowchart]].

* Add the icons shown in the flowchart:
:* a loop icon, configured as an infinite loop, and within it:
::* a Simulation macro icon[[File:Btn Simulation Macro.gif|border]];
::* a second loop.
:* Within the second loop, add:
::* two more Simulation macro icons;
::* a decision icon with:
:::* a 'Yes' loop containing an output icon, followed by a delay icon and then a calculation icon;
:::* a 'No' loop containing an output icon, followed by a delay icon;

[[File:Exercise_SimIcon_Simmove.png|right|250px]]

* Configure the icons, by double clicking on each in turn, as follows:
::* the top Simulation macro:
:::* name it "Set initial position";
:::* click on the 'Panel' tab, and then on the 'Position' folder;
:::* click on the 'MoveTo' macro and:
::::* choose 'group2'(the intruder)as the Handle;
::::* set the X value to "200";
::::* set the Y value to "0";
::::* set the Z value to "28";
::::* click on OK.

::* the second Simulation macro:
:::* name it "Move the intruder";
:::* click on the 'Panel' tab, and then on the 'Position' folder;
:::* click on the 'MoveAlong' macro and:
::::* choose 'group2'(the intruder)as the Handle;
::::* choose 'shape1'( the brick wall) as the Axis;
::::* click on the down arrow on the end of the 'X' row, and create a floating point variable called "xpos", with an initial value 5.0, to use as the X variable;
::::* click on OK.

[[File:Exercise SimIcon Simcheck.png|right|250px]]

::* the third Simulation macro:
:::* name it "Check detection";
:::* click on the 'Panel' tab, and then on the 'Collision' folder;
:::* click on the 'TestSingle' macro and:
::::* choose 'shape2'(the detection cone) for 'Pos' and 'shape5' (the intruder's head,) for 'Test';
:::* use the down arrow at the end of the 'Return Value' box to create a boolean variable caled "hit" to use as the 'Return Value'.
::::* click on OK.

::* the decision icon:
:::* name it "Intruder detected?";
:::* insert the condition "hit = 1";
:::* click on OK.

:::* In the 'Yes' loop:
::::* name the Output icon "Switch on lamp";
::::* send value '1' to Port A single bit 0;
::::* click on OK.

::::* name the Delay icon "Wait 100ms";
::::* configure it to give a delay of 100ms;
::::* click on OK.

::::* name the Calculation icon "Stop movement";
::::* in the 'Calculations:' box, insert "xpos = 0" to reduce the distance incremented each time to zero;
::::* click on OK.

:::* In the 'No' loop:
::::* name the Output icon "Switch off lamp";
::::* send value '0' to Port A single bit 0;
::::* click on OK.

::::* name the Delay icon "Wait 100ms";
::::* configure it to give a delay of 100ms;
::::* click on OK.

The Flowcode flowchart resembles the one shown below:

[[File:Exercise SimIcon Simflow.png|center|500px]]
==Testing==

* Run the simulation.
: The intruder should move towards the house, until he enters the detection zone.

: At this point, the warning lamp turns on and he stops.

* Stop the simulation, and click on the image of the intruder. You can now read the x coordinate from the Panel properties box.

* Change the height of the PIR sensor on the wall, or the angle of the detection cone, and see what happens to this coordinate.

==DON'T DOWNLOAD IT!!==
The important point is that the two Simulation macros do not compile to code that can be downloaded to a microcontroller. They affect only the simulation of the program.

File:Exercise SimIcon Simmoveint.png

2013-08-30T13:14:15Z

JohnVerrill:

Exercise - Using Simulation Macros

2013-08-30T13:11:26Z

JohnVerrill:

<sidebar>Sidebar: What Is a Macro?</sidebar>
Simulation macros are a form of Component macros. Their purpose is to make simulation more realistic by adding physical components to the electronic devices.

When the Flowcode program is compiled and downloaded to a microcontroller, they are ignored - hence the name Simulation macros.

Even a cursory glance at the dialogue box used to configure them shows that they are very powerful devices, with a huge range of possible effects.

This exercise uses three of them to illustrate the use of a PIR (Passive Infra-Red sensor) to operate an intruder sensor.

__TOC__

==The scenario==

The scene depicts the front of a house.
[[File:Exercise SimIcon pan.png|center|350px]]

A PIR sensor is mounted on the wall of the house, above the path leading across the garden.

The data sheet for the PIR shows that it is sensitive to a range of 10 metres, within a cone of angle 100 degrees.

Its detection area is represented in the image by the pale blue cone.

When an intruder enters the detection cone, a warning lamp lights up in the house.

This exercise allows us to investigate factors such as the height of the sensor on the brick wall and the angle of the detection zone, so that these can be optimised for a typical intruder height.

==The System Panel==

On the System Panel, viewed from above (the default position,)create:
* '''a brick wall''', represented by adding a red cuboid and changing it to a rectangle, 15mm wide, 120mm high and 120mm deep,
:: located at coordinates x = 0, y = 0, z = 60,
:: with rotation settings X = 0, Y = 0, Z = 0;

* '''a path''', represented by a grey rectangle, 240mm wide, 100mm high and 0mm deep,
:: located at coordinatesx = 125mm, y = 0mm, z = 0mm,
:: with rotation settings of X = 0, Y = 0, Z = 0;

* '''a cone''', couloured light blue, representing the sensing region of the PIR, with width = 70mm, height = 250mm, depth 95mm,
:: located at coordinates x = 45mm, y = 0mm, z = 80mm,
:: with rotation settings of X = 0, Y = -55, Z = 0.

* Drag the mouse cursor over these three elements and group them together.

This produces 'group 1'.
:: Give this group:
::: dimensions - width = 265mm, height = 250mm, depth = 135mm;
::: coordinates - x = 128, y = 0, z = 68;
::: rotation - X = 0, Y = 0, Z = 0.

Also on the System Panel, create an intruder, by:
* adding four spheres, and configuring the properties as follows:
:: sphere 1 ('''the head'''):
::: colour pink;
::: dimensions - width = 12mm, height = 13mm, depth = 15mm;
::: coordinates - x = -2.2, y = 0.7, z = 22;
::: rotation - X = 90, Y = 0, Z = 0.

:: sphere 2 ('''the body'''):
::: colour blue;
::: dimensions - width = 14mm, height = 26mm, depth = 24mm;
::: coordinates - x = -2.2, y = 0.5, z = 4;
::: rotation - X = 90, Y = 0, Z = -180.

:: sphere 3 ('''the legs'''):
::: colour dark green;
::: dimensions - width = 9mm, height = 23mm, depth = 15mm;
::: coordinates - x = -2.2, y = 1, z = -16;
::: rotation - X = 90, Y = 0, Z = -180.

:: sphere 4 ('''the feet'''):
::: colour black;
::: dimensions - width = 6mm, height = 15mm, depth = 25mm;
::: coordinates - x = -6, y = 0, z = -25;
::: rotation - X = 90, Y = 90, Z = 0.

* Drag the mouse cursor over the four spheres and group them together.

This produces 'group 2'.
:: Give it:
::: dimensions - width = 18mm, height = 32mm, depth = 60mm;
::: coordinates - x = 165, y = 0, z = 28;
::: rotation - X = 0, Y = 0, Z = 0.

The System Panel should resemble the image shown above. (The image has been rotated to show all components. The table-top is coloured green.)

Click on the 'Collisions' icon, [[File:Gen Panel Object Collision Move Around.png|35px]] and select the 'Move through' option, which allows the intruder to enter the detection cone.

==The Dashboard Panel==
[[File:Exercise SimIcon dash.png|right|200px]]
* Open the 'Outputs' toolbox, and locate the 'LED 5mm Panel' device.
* Click on the down arrow next to it and choose the 'Add to dashboard panel' option.
* Zoom in to the Dashboard Panel to make the LED large enough to see.
* Click on the LED and configure its properties as follows:
::* choose a suitable colour, such as red;
::* connect it to Port A, bit 0.

==The Flowcode program==
'''The plan:'''
* Set the initial position of the intruder, using the 'MoveTo' simulation macro.

* Move the intruder towards the detection cone using the 'MoveAlong' simulation macro.
:: This '''changes''' the x coordinate of the intruder '''by an amount specified by the variable 'xpos''''.

* When the intruder enters the detection zone, the simulation macro 'CollisionTest' returns a value of '1' in the variable 'hit'.
:: At this point, we stop any more movement so that we can look at the x coordinate of the intruder.
:: To do so, we change the value of 'xpos' to zero.

'''Implementation:'''

* [[Opening Flowcode|Open Flowcode]].

* On the Startup screen, click on 'New project' to [[Creating Flowcharts|create a new flowchart]].

* Add the icons shown in the flowchart:
:* a loop icon, configured as an infinite loop, and within it:
::* a Simulation macro icon[[File:Btn Simulation Macro.gif|border]];
::* a second loop.
:* Within the second loop, add:
::* two more Simulation macro icons;
::* a decision icon with:
:::* a 'Yes' loop containing an output icon, followed by a delay icon and then a calculation icon;
:::* a 'No' loop containing an output icon, followed by a delay icon;

[[File:Exercise_SimIcon_Simmove.png|right|250px]]

* Configure the icons, by double clicking on each in turn, as follows:
::* the top Simulation macro:
:::* name it "Set initial position";
:::* click on the 'Panel' tab, and then on the 'Position' folder;
:::* click on the 'MoveTo' macro and:
::::* choose 'group2'(the intruder)as the Handle;
::::* set the X value to "200";
::::* set the Y value to "0";
::::* set the Z value to "28";
::::* click on OK.

[[File:Exercise SimIcon Simmoveint.png|right|400px]]

::* the second Simulation macro:
:::* name it "Move the intruder";
:::* click on the 'Panel' tab, and then on the 'Position' folder;
:::* click on the 'MoveAlong' macro and:
::::* choose 'group2'(the intruder)as the Handle;
::::* choose 'shape1'( the brick wall) as the Axis;
::::* click on the down arrow on the end of the 'X' row, and create a floating point variable called "xpos", with an initial value 5.0, to use as the X variable;
::::* click on OK.

[[File:Exercise SimIcon Simcheck.png|right|250px]]

::* the third Simulation macro:
:::* name it "Check detection";
:::* click on the 'Panel' tab, and then on the 'Collision' folder;
:::* click on the 'TestSingle' macro and:
::::* choose 'shape2'(the detection cone) for 'Pos' and 'shape5' (the intruder's head,) for 'Test';
:::* use the down arrow at the end of the 'Return Value' box to create a boolean variable caled "hit" to use as the 'Return Value'.
::::* click on OK.

::* the decision icon:
:::* name it "Intruder detected?";
:::* insert the condition "hit = 1";
:::* click on OK.

:::* In the 'Yes' loop:
::::* name the Output icon "Switch on lamp";
::::* send value '1' to Port A single bit 0;
::::* click on OK.

::::* name the Delay icon "Wait 100ms";
::::* configure it to give a delay of 100ms;
::::* click on OK.

::::* name the Calculation icon "Stop movement";
::::* in the 'Calculations:' box, insert "xpos = 0" to reduce the distance incremented each time to zero;
::::* click on OK.

:::* In the 'No' loop:
::::* name the Output icon "Switch off lamp";
::::* send value '0' to Port A single bit 0;
::::* click on OK.

::::* name the Delay icon "Wait 100ms";
::::* configure it to give a delay of 100ms;
::::* click on OK.

The Flowcode flowchart resembles the one shown below:

[[File:Exercise SimIcon Simflow.png|center|500px]]
==Testing==

* Run the simulation.
: The intruder should move towards the house, until he enters the detection zone.

: At this point, the warning lamp turns on and he stops.

* Stop the simulation, and click on the image of the intruder. You can now read the x coordinate from the Panel properties box.

* Change the height of the PIR sensor on the wall, or the angle of the detection cone, and see what happens to this coordinate.

==DON'T DOWNLOAD IT!!==
The important point is that the two Simulation macros do not compile to code that can be downloaded to a microcontroller. They affect only the simulation of the program.

File:Exercise SimIcon Simcheck.png

2013-08-30T13:05:48Z

JohnVerrill:

Exercise - Using Simulation Macros

2013-08-30T13:01:30Z

JohnVerrill:

<sidebar>Sidebar: What Is a Macro?</sidebar>
Simulation macros are a form of Component macros. Their purpose is to make simulation more realistic by adding physical components to the electronic devices.

When the Flowcode program is compiled and downloaded to a microcontroller, they are ignored - hence the name Simulation macros.

Even a cursory glance at the dialogue box used to configure them shows that they are very powerful devices, with a huge range of possible effects.

This exercise uses three of them to illustrate the use of a PIR (Passive Infra-Red sensor) to operate an intruder sensor.

__TOC__

==The scenario==

The scene depicts the front of a house.
[[File:Exercise SimIcon pan.png|center|350px]]

A PIR sensor is mounted on the wall of the house, above the path leading across the garden.

The data sheet for the PIR shows that it is sensitive to a range of 10 metres, within a cone of angle 100 degrees.

Its detection area is represented in the image by the pale blue cone.

When an intruder enters the detection cone, a warning lamp lights up in the house.

This exercise allows us to investigate factors such as the height of the sensor on the brick wall and the angle of the detection zone, so that these can be optimised for a typical intruder height.

==The System Panel==

On the System Panel, viewed from above (the default position,)create:
* '''a brick wall''', represented by adding a red cuboid and changing it to a rectangle, 15mm wide, 120mm high and 120mm deep,
:: located at coordinates x = 0, y = 0, z = 60,
:: with rotation settings X = 0, Y = 0, Z = 0;

* '''a path''', represented by a grey rectangle, 240mm wide, 100mm high and 0mm deep,
:: located at coordinatesx = 125mm, y = 0mm, z = 0mm,
:: with rotation settings of X = 0, Y = 0, Z = 0;

* '''a cone''', couloured light blue, representing the sensing region of the PIR, with width = 70mm, height = 250mm, depth 95mm,
:: located at coordinates x = 45mm, y = 0mm, z = 80mm,
:: with rotation settings of X = 0, Y = -55, Z = 0.

* Drag the mouse cursor over these three elements and group them together.

This produces 'group 1'.
:: Give this group:
::: dimensions - width = 265mm, height = 250mm, depth = 135mm;
::: coordinates - x = 128, y = 0, z = 68;
::: rotation - X = 0, Y = 0, Z = 0.

Also on the System Panel, create an intruder, by:
* adding four spheres, and configuring the properties as follows:
:: sphere 1 ('''the head'''):
::: colour pink;
::: dimensions - width = 12mm, height = 13mm, depth = 15mm;
::: coordinates - x = -2.2, y = 0.7, z = 22;
::: rotation - X = 90, Y = 0, Z = 0.

:: sphere 2 ('''the body'''):
::: colour blue;
::: dimensions - width = 14mm, height = 26mm, depth = 24mm;
::: coordinates - x = -2.2, y = 0.5, z = 4;
::: rotation - X = 90, Y = 0, Z = -180.

:: sphere 3 ('''the legs'''):
::: colour dark green;
::: dimensions - width = 9mm, height = 23mm, depth = 15mm;
::: coordinates - x = -2.2, y = 1, z = -16;
::: rotation - X = 90, Y = 0, Z = -180.

:: sphere 4 ('''the feet'''):
::: colour black;
::: dimensions - width = 6mm, height = 15mm, depth = 25mm;
::: coordinates - x = -6, y = 0, z = -25;
::: rotation - X = 90, Y = 90, Z = 0.

* Drag the mouse cursor over the four spheres and group them together.

This produces 'group 2'.
:: Give it:
::: dimensions - width = 18mm, height = 32mm, depth = 60mm;
::: coordinates - x = 165, y = 0, z = 28;
::: rotation - X = 0, Y = 0, Z = 0.

The System Panel should resemble the image shown above. (The image has been rotated to show all components. The table-top is coloured green.)

Click on the 'Collisions' icon, [[File:Gen Panel Object Collision Move Around.png|35px]] and select the 'Move through' option, which allows the intruder to enter the detection cone.

==The Dashboard Panel==
[[File:Exercise SimIcon dash.png|right|200px]]
* Open the 'Outputs' toolbox, and locate the 'LED 5mm Panel' device.
* Click on the down arrow next to it and choose the 'Add to dashboard panel' option.
* Zoom in to the Dashboard Panel to make the LED large enough to see.
* Click on the LED and configure its properties as follows:
::* choose a suitable colour, such as red;
::* connect it to Port A, bit 0.

==The Flowcode program==
'''The plan:'''
* Set the initial position of the intruder, using the 'MoveTo' simulation macro.

* Move the intruder towards the detection cone using the 'MoveAlong' simulation macro.
:: This '''changes''' the x coordinate of the intruder '''by an amount specified by the variable 'xpos''''.

* When the intruder enters the detection zone, the simulation macro 'CollisionTest' returns a value of '1' in the variable 'hit'.
:: At this point, we stop any more movement so that we can look at the x coordinate of the intruder.
:: To do so, we change the value of 'xpos' to zero.

'''Implementation:'''

* [[Opening Flowcode|Open Flowcode]].

* On the Startup screen, click on 'New project' to [[Creating Flowcharts|create a new flowchart]].

* Add the icons shown in the flowchart:
:* a loop icon, configured as an infinite loop, and within it:
::* a Simulation macro icon[[File:Btn Simulation Macro.gif|border]];
::* a second loop.
:* Within the second loop, add:
::* two more Simulation macro icons;
::* a decision icon with:
:::* a 'Yes' loop containing an output icon, followed by a delay icon and then a calculation icon;
:::* a 'No' loop containing an output icon, followed by a delay icon;

[[File:Exercise_SimIcon_Simmove.png|right|250px]]

* Configure the icons, by double clicking on each in turn, as follows:
::* the top Simulation macro:
:::* name it "Set initial position";
:::* click on the 'Panel' tab, and then on the 'Position' folder;
:::* click on the 'MoveTo' macro and:
::::* choose 'group2'(the intruder)as the Handle;
::::* set the X value to "200";
::::* set the Y value to "0";
::::* set the Z value to "28";
::::* click on OK.

[[File:Exercise SimIcon Sim move.png|right|400px]]

::* the second Simulation macro:
:::* name it "Move the intruder";
:::* click on the 'Panel' tab, and then on the 'Position' folder;
:::* click on the 'MoveAlong' macro and:
::::* choose 'group2'(the intruder)as the Handle;
::::* choose 'shape1'( the brick wall) as the Axis;
::::* click on the down arrow on the end of the 'X' row, and create a floating point variable called "xpos", with an initial value 5.0, to use as the X variable;
::::* click on OK.

[[File:Exercise SimIcon Sim test.png|right|250px]]

::* the third Simulation macro:
:::* name it "Check detection";
:::* click on the 'Panel' tab, and then on the 'Collision' folder;
:::* click on the 'TestSingle' macro and:
::::* choose 'shape2'(the detection cone) for 'Pos' and 'shape5' (the intruder's head,) for 'Test';
:::* use the down arrow at the end of the 'Return Value' box to create a boolean variable caled "hit" to use as the 'Return Value'.
::::* click on OK.

::* the decision icon:
:::* name it "Intruder detected?";
:::* insert the condition "hit = 1";
:::* click on OK.

:::* In the 'Yes' loop:
::::* name the Output icon "Switch on lamp";
::::* send value '1' to Port A single bit 0;
::::* click on OK.

::::* name the Delay icon "Wait 100ms";
::::* configure it to give a delay of 100ms;
::::* click on OK.

::::* name the Calculation icon "Stop movement";
::::* in the 'Calculations:' box, insert "xpos = 0" to reduce the distance incremented each time to zero;
::::* click on OK.

:::* In the 'No' loop:
::::* name the Output icon "Switch off lamp";
::::* send value '0' to Port A single bit 0;
::::* click on OK.

::::* name the Delay icon "Wait 100ms";
::::* configure it to give a delay of 100ms;
::::* click on OK.

The Flowcode flowchart resembles the one shown below:

[[File:Exercise SimIcon Simflow.png|center|500px]]
==Testing==

* Run the simulation.
: The intruder should move towards the house, until he enters the detection zone.

: At this point, the warning lamp turns on and he stops.

* Stop the simulation, and click on the image of the intruder. You can now read the x coordinate from the Panel properties box.

* Change the height of the PIR sensor on the wall, or the angle of the detection cone, and see what happens to this coordinate.

==DON'T DOWNLOAD IT!!==
The important point is that the two Simulation macros do not compile to code that can be downloaded to a microcontroller. They affect only the simulation of the program.

File:Exercise SimIcon Simmove.png

2013-08-30T12:41:57Z

JohnVerrill:

Exercise - Using Simulation Macros

2013-08-30T12:32:18Z

JohnVerrill:

<sidebar>Sidebar: What Is a Macro?</sidebar>
Simulation macros are a form of Component macros. Their purpose is to make simulation more realistic by adding physical components to the electronic devices.

When the Flowcode program is compiled and downloaded to a microcontroller, they are ignored - hence the name Simulation macros.

Even a cursory glance at the dialogue box used to configure them shows that they are very powerful devices, with a huge range of possible effects.

This exercise uses three of them to illustrate the use of a PIR (Passive Infra-Red sensor) to operate an intruder sensor.

__TOC__

==The scenario==

The scene depicts the front of a house.
[[File:Exercise SimIcon pan.png|center|350px]]

A PIR sensor is mounted on the wall of the house, above the path leading across the garden.

The data sheet for the PIR shows that it is sensitive to a range of 10 metres, within a cone of angle 100 degrees.

Its detection area is represented in the image by the pale blue cone.

When an intruder enters the detection cone, a warning lamp lights up in the house.

This exercise allows us to investigate factors such as the height of the sensor on the brick wall and the angle of the detection zone, so that these can be optimised for a typical intruder height.

==The System Panel==

On the System Panel, viewed from above (the default position,)create:
* '''a brick wall''', represented by adding a red cuboid and changing it to a rectangle, 15mm wide, 120mm high and 120mm deep,
:: located at coordinates x = 0, y = 0, z = 60,
:: with rotation settings X = 0, Y = 0, Z = 0;

* '''a path''', represented by a grey rectangle, 240mm wide, 100mm high and 0mm deep,
:: located at coordinatesx = 125mm, y = 0mm, z = 0mm,
:: with rotation settings of X = 0, Y = 0, Z = 0;

* '''a cone''', couloured light blue, representing the sensing region of the PIR, with width = 70mm, height = 250mm, depth 95mm,
:: located at coordinates x = 45mm, y = 0mm, z = 80mm,
:: with rotation settings of X = 0, Y = -55, Z = 0.

* Drag the mouse cursor over these three elements and group them together.

This produces 'group 1'.
:: Give this group:
::: dimensions - width = 265mm, height = 250mm, depth = 135mm;
::: coordinates - x = 128, y = 0, z = 68;
::: rotation - X = 0, Y = 0, Z = 0.

Also on the System Panel, create an intruder, by:
* adding four spheres, and configuring the properties as follows:
:: sphere 1 ('''the head'''):
::: colour pink;
::: dimensions - width = 12mm, height = 13mm, depth = 15mm;
::: coordinates - x = -2.2, y = 0.7, z = 22;
::: rotation - X = 90, Y = 0, Z = 0.

:: sphere 2 ('''the body'''):
::: colour blue;
::: dimensions - width = 14mm, height = 26mm, depth = 24mm;
::: coordinates - x = -2.2, y = 0.5, z = 4;
::: rotation - X = 90, Y = 0, Z = -180.

:: sphere 3 ('''the legs'''):
::: colour dark green;
::: dimensions - width = 9mm, height = 23mm, depth = 15mm;
::: coordinates - x = -2.2, y = 1, z = -16;
::: rotation - X = 90, Y = 0, Z = -180.

:: sphere 4 ('''the feet'''):
::: colour black;
::: dimensions - width = 6mm, height = 15mm, depth = 25mm;
::: coordinates - x = -6, y = 0, z = -25;
::: rotation - X = 90, Y = 90, Z = 0.

* Drag the mouse cursor over the four spheres and group them together.

This produces 'group 2'.
:: Give it:
::: dimensions - width = 18mm, height = 32mm, depth = 60mm;
::: coordinates - x = 165, y = 0, z = 28;
::: rotation - X = 0, Y = 0, Z = 0.

The System Panel should resemble the image shown above. (The image has been rotated to show all components. The table-top is coloured green.)

Click on the 'Collisions' icon, [[File:Gen Panel Object Collision Move Around.png|35px]] and select the 'Move through' option, which allows the intruder to enter the detection cone.

==The Dashboard Panel==
[[File:Exercise SimIcon dash.png|right|200px]]
* Open the 'Outputs' toolbox, and locate the 'LED 5mm Panel' device.
* Click on the down arrow next to it and choose the 'Add to dashboard panel' option.
* Zoom in to the Dashboard Panel to make the LED large enough to see.
* Click on the LED and configure its properties as follows:
::* choose a suitable colour, such as red;
::* connect it to Port A, bit 0.

==The Flowcode program==

'''The plan:'''
* Set the initial position of the intruder, using the 'MoveTo' simulation macro.

* Move the intruder towards the detection cone using the 'MoveAlong' simulation macro.
:: This '''changes''' the x coordinate of the intruder '''by an amount specified by the variable 'xpos''''.

* When the intruder enters the detection zone, the simulation macro 'CollisionTest' returns a value of '1' in the variable 'hit'.
:: At this point, we stop any more movement so that we can look at the x coordinate of the intruder.
:: To do so, we change the value of 'xpos' to zero.

'''Implementation:'''

* [[Opening Flowcode|Open Flowcode]].

* On the Startup screen, click on 'New project' to [[Creating Flowcharts|create a new flowchart]].

* Add the icons shown in the flowchart:
:* a loop icon, configured as an infinite loop, and within it:
::* a Simulation macro icon;
::* a second loop.
:* Within the second loop, add:
::* two Simulation macro icons [[File:Btn Simulation Macro.gif|border]];
::* a decision icon with:
:::* a 'Yes' loop containing an output icon, followed by a delay icon and then a calculation icon;
:::* a 'No' loop containing an output icon, followed by a delay icon;
[[File:Exercise SimIcon Sim move.png|right|450px]]

* Configure the icons, by double clicking on each in turn, as follows:
::* the top Simulation macro:
:::* name it "Set initial position";
:::* click on the 'Panel' tab, and then on the 'Position' folder;
:::* click on the 'MoveTo' macro and:
::::* choose 'group2'(the intruder)as the Handle;
::::* set the X value to "200";
::::* set the Y value to "0";
::::* set the Z value to "28";
::::* click on OK.

::* the second Simulation macro:
:::* name it "Move the intruder";
:::* click on the 'Panel' tab, and then on the 'Position' folder;
:::* click on the 'MoveAlong' macro and:
::::* choose 'group2'(the intruder)as the Handle;
::::* choose 'shape1'( the brick wall) as the Axis;
::::* click on the down arrow on the end of the 'X' row, and create a floating point variable called "xpos", with an initial value 5.0, to use as the X variable;
::::* click on OK.

::* the third Simulation macro:
:::* name it "Check detection";
:::* click on the 'Panel' tab, and then on the 'Collision' folder;
[[File:Exercise SimIcon Sim test.png|right|300px]]
:::* click on the 'TestSingle' macro and:
::::* choose 'shape2'(the detection cone) for 'Pos' and 'shape5' (the intruder's head,) for 'Test';
:::* use the down arrow at the end of the 'Return Value' box to create a boolean variable caled "hit" to use as the 'Return Value'.
::::* click on OK.

::* the decision icon:
:::* name it "Intruder detected?";
:::* insert the condition "hit = 1";
:::* click on OK.

:::* In the 'Yes' loop:
::::* name the Output icon "Switch on lamp";
::::* send value '1' to Port A single bit 0;
::::* click on OK.

::::* name the Delay icon "Wait 100ms";
::::* configure it to give a delay of 100ms;
::::* click on OK.

::::* name the Calculation icon "Stop movement";
::::* in the 'Calculations:' box, insert "xpos = 0" to reduce the distance incremented each time to zero;
::::* click on OK.

:::* In the 'No' loop:
::::* name the Output icon "Switch off lamp";
::::* send value '0' to Port A single bit 0;
::::* click on OK.

::::* name the Delay icon "Wait 100ms";
::::* configure it to give a delay of 100ms;
::::* click on OK.

The Flowcode flowchart resembles the one shown below:

[[File:Exercise SimIcon Simflow.png|center|500px]]
==Testing==

* Run the simulation.
: The intruder should move towards the house, until he enters the detection zone.

: At this point, the warning lamp turns on and he stops.

* Stop the simulation, and click on the image of the intruder. You can now read the x coordinate from the Panel properties box.

* Change the height of the PIR sensor on the wall, or the angle of the detection cone, and see what happens to this coordinate.

==DON'T DOWNLOAD IT!!==
The important point is that the two Simulation macros do not compile to code that can be downloaded to a microcontroller. They affect only the simulation of the program.

Exercise - Using Simulation Macros

2013-08-30T12:24:40Z

JohnVerrill:

<sidebar>Sidebar: What Is a Macro?</sidebar>
Simulation macros are a form of Component macros. Their purpose is to make simulation more realistic by adding physical components to the electronic devices.

When the Flowcode program is compiled and downloaded to a microcontroller, they are ignored - hence the name Simulation macros.

Even a cursory glance at the dialogue box used to configure them shows that they are very powerful devices, with a huge range of possible effects.

This exercise uses three of them to illustrate the use of a PIR (Passive Infra-Red sensor) to operate an intruder sensor.

__TOC__

==The scenario==

The scene depicts the front of a house.
[[File:Exercise SimIcon pan.png|center|350px]]

A PIR sensor is mounted on the wall of the house, above the path leading across the garden.

The data sheet for the PIR shows that it is sensitive to a range of 10 metres, within a cone of angle 100 degrees.

Its detection area is represented in the image by the pale blue cone.

When an intruder enters the detection cone, a warning lamp lights up in the house.

This exercise allows us to investigate factors such as the height of the sensor on the brick wall and the angle of the detection zone, so that these can be optimised for a typical intruder height.

==The System Panel==

On the System Panel, viewed from above (the default position,)create:
* '''a brick wall''', represented by adding a red cuboid and changing it to a rectangle, 15mm wide, 120mm high and 120mm deep,
:: located at coordinates x = 0, y = 0, z = 60,
:: with rotation settings X = 0, Y = 0, Z = 0;

* '''a path''', represented by a grey rectangle, 240mm wide, 100mm high and 0mm deep,
:: located at coordinatesx = 125mm, y = 0mm, z = 0mm,
:: with rotation settings of X = 0, Y = 0, Z = 0;

* '''a cone''', couloured light blue, representing the sensing region of the PIR, with width = 70mm, height = 250mm, depth 95mm,
:: located at coordinates x = 45mm, y = 0mm, z = 80mm,
:: with rotation settings of X = 0, Y = -55, Z = 0.

* Drag the mouse cursor over these three elements and group them together.

This produces 'group 1'.
:: Give this group:
::: dimensions - width = 265mm, height = 250mm, depth = 135mm;
::: coordinates - x = 128, y = 0, z = 68;
::: rotation - X = 0, Y = 0, Z = 0.

Also on the System Panel, create an intruder, by:
* adding four spheres, and configuring the properties as follows:
:: sphere 1 ('''the head'''):
::: colour pink;
::: dimensions - width = 12mm, height = 13mm, depth = 15mm;
::: coordinates - x = -2.2, y = 0.7, z = 22;
::: rotation - X = 90, Y = 0, Z = 0.

:: sphere 2 ('''the body'''):
::: colour blue;
::: dimensions - width = 14mm, height = 26mm, depth = 24mm;
::: coordinates - x = -2.2, y = 0.5, z = 4;
::: rotation - X = 90, Y = 0, Z = -180.

:: sphere 3 ('''the legs'''):
::: colour dark green;
::: dimensions - width = 9mm, height = 23mm, depth = 15mm;
::: coordinates - x = -2.2, y = 1, z = -16;
::: rotation - X = 90, Y = 0, Z = -180.

:: sphere 4 ('''the feet'''):
::: colour black;
::: dimensions - width = 6mm, height = 15mm, depth = 25mm;
::: coordinates - x = -6, y = 0, z = -25;
::: rotation - X = 90, Y = 90, Z = 0.

* Drag the mouse cursor over the four spheres and group them together.

This produces 'group 2'.
:: Give it:
::: dimensions - width = 18mm, height = 32mm, depth = 60mm;
::: coordinates - x = 165, y = 0, z = 28;
::: rotation - X = 0, Y = 0, Z = 0.

The System Panel should resemble the image shown above. (The image has been rotated to show all components. The table-top is coloured green.)

Click on the 'Collisions' icon, [[File:Gen Panel Object Collision Move Around.png|35px]] and select the 'Move through' option, which allows the intruder to enter the detection cone.

==The Dashboard Panel==
[[File:Exercise SimIcon dash.png|right|200px]]
* Open the 'Outputs' toolbox, and locate the 'LED 5mm Panel' device.
* Click on the down arrow next to it and choose the 'Add to dashboard panel' option.
* Zoom in to the Dashboard Panel to make the LED large enough to see.
* Click on the LED and configure its properties as follows:
::* choose a suitable colour, such as red;
::* connect it to Port A, bit 0.

==The Flowcode program==

'''The plan:'''
* Set the initial position of the intruder, using the 'MoveTo' simulation macro.

* Move the intruder towards the detection cone using the 'MoveAlong' simulation macro.
:: This '''changes''' the x coordinate of the intruder '''by an amount specified by the variable 'xpos''''.

* When the intruder enters the detection zone, the simulation macro 'CollisionTest' returns a value of '1' in the variable 'hit'.
:: At this point, we stop any more movement so that we can look at the x coordinate of the intruder.
:: To do so, we change the value of 'xpos' to zero.

'''Implementation:'''

* [[Opening Flowcode|Open Flowcode]].

* On the Startup screen, click on 'New project' to [[Creating Flowcharts|create a new flowchart]].

* Add the icons shown in the flowchart:
:* a loop icon, configured as an infinite loop, and within it:
::* two Simulation macro icons [[File:Btn Simulation Macro.gif|border]];
::* a decision icon with:
:::* a 'Yes' loop containing an output icon, followed by a delay icon and then a calculation icon;
:::* a 'No' loop containing an output icon, followed by a delay icon;
[[File:Exercise SimIcon Sim move.png|right|450px]]

* Configure the icons, by double clicking on each in turn, as follows:
::* the top Simulation macro:
:::* name it "Move the intruder";
:::* click on the 'Panel' tab, and then on the 'Position' folder;
:::* click on the 'MoveAlong' macro and:
::::* choose 'group2'(the intruder)as the Handle;
::::* choose 'shape1'( the brick wall) as the Axis;
::::* click on the down arrow on the end of the 'X' row, and create a floating point variable called "xpos", with an initial value 5.0, to use as the X variable;
::::* click on OK.

::* the second Simulation macro:
:::* name it "Check detection";
:::* click on the 'Panel' tab, and then on the 'Collision' folder;
[[File:Exercise SimIcon Sim test.png|right|300px]]
:::* click on the 'TestSingle' macro and:
::::* choose 'shape2'(the detection cone) for 'Pos' and 'shape5' (the intruder's head,) for 'Test';
:::* use the down arrow at the end of the 'Return Value' box to create a boolean variable caled "hit" to use as the 'Return Value'.
::::* click on OK.

::* the decision icon:
:::* name it "Intruder detected?";
:::* insert the condition "hit = 1";
:::* click on OK.

:::* In the 'Yes' loop:
::::* name the Output icon "Switch on lamp";
::::* send value '1' to Port A single bit 0;
::::* click on OK.

::::* name the Delay icon "Wait 100ms";
::::* configure it to give a delay of 100ms;
::::* click on OK.

::::* name the Calculation icon "Stop movement";
::::* in the 'Calculations:' box, insert "xpos = 0" to reduce the distance incremented each time to zero;
::::* click on OK.

:::* In the 'No' loop:
::::* name the Output icon "Switch off lamp";
::::* send value '0' to Port A single bit 0;
::::* click on OK.

::::* name the Delay icon "Wait 100ms";
::::* configure it to give a delay of 100ms;
::::* click on OK.

The Flowcode flowchart resembles the one shown below:

[[File:Exercise SimIcon Simflow.png|center|500px]]
==Testing==

* Run the simulation.
: The intruder should move towards the house, until he enters the detection zone.

: At this point, the warning lamp turns on and he stops.

* Stop the simulation, and click on the image of the intruder. You can now read the x coordinate from the Panel properties box.

* Change the height of the PIR sensor on the wall, or the angle of the detection cone, and see what happens to this coordinate.

==DON'T DOWNLOAD IT!!==
The important point is that the two Simulation macros do not compile to code that can be downloaded to a microcontroller. They affect only the simulation of the program.

Exercise - Using Simulation Macros

2013-08-30T12:21:30Z

JohnVerrill:

<sidebar>Sidebar: What Is a Macro?</sidebar>
Simulation macros are a form of Component macros. Their purpose is to make simulation more realistic by adding physical components to the electronic devices.

When the Flowcode program is compiled and downloaded to a microcontroller, they are ignored - hence the name Simulation macros.

Even a cursory glance at the dialogue box used to configure them shows that they are very powerful devices, with a huge range of possible effects.

This exercise uses three of them to illustrate the use of a PIR (Passive Infra-Red sensor) to operate an intruder sensor.

__TOC__

==The scenario==

The scene depicts the front of a house.
[[File:Exercise SimIcon pan.png|center|350px]]

A PIR sensor is mounted on the wall of the house, above the path leading across the garden.

The data sheet for the PIR shows that it is sensitive to a range of 10 metres, within a cone of angle 100 degrees.

Its detection area is represented in the image by the pale blue cone.

When an intruder enters the detection cone, a warning lamp lights up in the house.

This exercise allows us to investigate factors such as the height of the sensor on the brick wall and the angle of the detection zone, so that these can be optimised for a typical intruder height.

==The System Panel==

On the System Panel, viewed from above (the default position,)create:
* '''a brick wall''', represented by adding a red cuboid and changing it to a rectangle, 15mm wide, 120mm high and 120mm deep,
:: located at coordinates x = 0, y = 0, z = 60,
:: with rotation settings X = 0, Y = 0, Z = 0;

* '''a path''', represented by a grey rectangle, 240mm wide, 100mm high and 0mm deep,
:: located at coordinatesx = 125mm, y = 0mm, z = 0mm,
:: with rotation settings of X = 0, Y = 0, Z = 0;

* '''a cone''', couloured light blue, representing the sensing region of the PIR, with width = 70mm, height = 250mm, depth 95mm,
:: located at coordinates x = 45mm, y = 0mm, z = 80mm,
:: with rotation settings of X = 0, Y = -55, Z = 0.

* Drag the mouse cursor over these three elements and group them together.

This produces 'group 1'.
:: Give this group:
::: dimensions - width = 265mm, height = 250mm, depth = 135mm;
::: coordinates - x = 128, y = 0, z = 68;
::: rotation - X = 0, Y = 0, Z = 0.

Also on the System Panel, create an intruder, by:
* adding four spheres, and configuring the properties as follows:
:: sphere 1 ('''the head'''):
::: colour pink;
::: dimensions - width = 12mm, height = 13mm, depth = 15mm;
::: coordinates - x = -2.2, y = 0.7, z = 22;
::: rotation - X = 90, Y = 0, Z = 0.

:: sphere 2 ('''the body'''):
::: colour blue;
::: dimensions - width = 14mm, height = 26mm, depth = 24mm;
::: coordinates - x = -2.2, y = 0.5, z = 4;
::: rotation - X = 90, Y = 0, Z = -180.

:: sphere 3 ('''the legs'''):
::: colour dark green;
::: dimensions - width = 9mm, height = 23mm, depth = 15mm;
::: coordinates - x = -2.2, y = 1, z = -16;
::: rotation - X = 90, Y = 0, Z = -180.

:: sphere 4 ('''the feet'''):
::: colour black;
::: dimensions - width = 6mm, height = 15mm, depth = 25mm;
::: coordinates - x = -6, y = 0, z = -25;
::: rotation - X = 90, Y = 90, Z = 0.

* Drag the mouse cursor over the four spheres and group them together.

This produces 'group 2'.
:: Give it:
::: dimensions - width = 18mm, height = 32mm, depth = 60mm;
::: coordinates - x = 165, y = 0, z = 28;
::: rotation - X = 0, Y = 0, Z = 0.

The System Panel should resemble the image shown above. (The image has been rotated to show all components. The table-top is coloured green.)

Click on the 'Collisions' icon, [[File:Gen Panel Object Collision Move Around.png|35px]] and select the 'Move through' option, which allows the intruder to enter the detection cone.

==The Dashboard Panel==
[[File:Exercise SimIcon dash.png|right|200px]]
* Open the 'Outputs' toolbox, and locate the 'LED 5mm Panel' device.
* Click on the down arrow next to it and choose the 'Add to dashboard panel' option.
* Zoom in to the Dashboard Panel to make the LED large enough to see.
* Click on the LED and configure its properties as follows:
::* choose a suitable colour, such as red;
::* connect it to Port A, bit 0.

==The Flowcode program==

The plan:

: Set the initial position of the intruder, using the 'MoveTo' simulation macro
: Move the intruder towards the detection cone using the 'MoveAlong' simulation macro.
:: This '''changes''' the x coordinate of the intruder '''by an amount specified by the variable 'xpos''''.

: When the intruder enters the detection zone, the simulation macro 'CollisionTest' returns a value of '1' in the variable 'hit'.
:: At this point, we stop any more movement so that we can look at the x coordinate of the intruder.
:: To do so, we change the value of 'xpos' to zero.

* [[Opening Flowcode|Open Flowcode]].

* On the Startup screen, click on 'New project' to [[Creating Flowcharts|create a new flowchart]].

* Add the icons shown in the flowchart:
:* a loop icon, configured as an infinite loop, and within it:
::* two Simulation macro icons [[File:Btn Simulation Macro.gif|border]];
::* a decision icon with:
:::* a 'Yes' loop containing an output icon, followed by a delay icon and then a calculation icon;
:::* a 'No' loop containing an output icon, followed by a delay icon;
[[File:Exercise SimIcon Sim move.png|right|450px]]

* Configure the icons, by double clicking on each in turn, as follows:
::* the top Simulation macro:
:::* name it "Move the intruder";
:::* click on the 'Panel' tab, and then on the 'Position' folder;
:::* click on the 'MoveAlong' macro and:
::::* choose 'group2'(the intruder)as the Handle;
::::* choose 'shape1'( the brick wall) as the Axis;
::::* click on the down arrow on the end of the 'X' row, and create a floating point variable called "xpos", with an initial value 5.0, to use as the X variable;
::::* click on OK.

::* the second Simulation macro:
:::* name it "Check detection";
:::* click on the 'Panel' tab, and then on the 'Collision' folder;
[[File:Exercise SimIcon Sim test.png|right|300px]]
:::* click on the 'TestSingle' macro and:
::::* choose 'shape2'(the detection cone) for 'Pos' and 'shape5' (the intruder's head,) for 'Test';
:::* use the down arrow at the end of the 'Return Value' box to create a boolean variable caled "hit" to use as the 'Return Value'.
::::* click on OK.

::* the decision icon:
:::* name it "Intruder detected?";
:::* insert the condition "hit = 1";
:::* click on OK.

:::* In the 'Yes' loop:
::::* name the Output icon "Switch on lamp";
::::* send value '1' to Port A single bit 0;
::::* click on OK.

::::* name the Delay icon "Wait 100ms";
::::* configure it to give a delay of 100ms;
::::* click on OK.

::::* name the Calculation icon "Stop movement";
::::* in the 'Calculations:' box, insert "xpos = 0" to reduce the distance incremented each time to zero;
::::* click on OK.

:::* In the 'No' loop:
::::* name the Output icon "Switch off lamp";
::::* send value '0' to Port A single bit 0;
::::* click on OK.

::::* name the Delay icon "Wait 100ms";
::::* configure it to give a delay of 100ms;
::::* click on OK.

The Flowcode flowchart resembles the one shown below:

[[File:Exercise SimIcon Simflow.png|center|500px]]
==Testing==

* Run the simulation.
: The intruder should move towards the house, until he enters the detection zone.

: At this point, the warning lamp turns on and he stops.

* Stop the simulation, and click on the image of the intruder. You can now read the x coordinate from the Panel properties box.

* Change the height of the PIR sensor on the wall, or the angle of the detection cone, and see what happens to this coordinate.

==DON'T DOWNLOAD IT!!==
The important point is that the two Simulation macros do not compile to code that can be downloaded to a microcontroller. They affect only the simulation of the program.

Exercise - Using Simulation Macros

2013-08-30T12:17:33Z

JohnVerrill:

<sidebar>Sidebar: What Is a Macro?</sidebar>
Simulation macros are a form of Component macros. Their purpose is to make simulation more realistic by adding physical components to the electronic devices.

When the Flowcode program is compiled and downloaded to a microcontroller, they are ignored - hence the name Simulation macros.

Even a cursory glance at the dialogue box used to configure them shows that they are very powerful devices, with a huge range of possible effects.

This exercise uses two of them to illustrate the use of a PIR (Passive Infra-Red sensor) to operate an intruder sensor.

__TOC__

==The scenario==

The scene depicts the front of a house.
[[File:Exercise SimIcon pan.png|center|350px]]

A PIR sensor is mounted on the wall of the house, above the path leading across the garden.

The data sheet for the PIR shows that it is sensitive to a range of 10 metres, within a cone of angle 100 degrees.

Its detection area is represented in the image by the pale blue cone.

When an intruder enters the detection cone, a warning lamp lights up in the house.

This exercise allows us to investigate factors such as the height of the sensor on the brick wall and the angle of the detection zone, so that these can be optimised for a typical intruder height.

==The System Panel==

On the System Panel, viewed from above (the default position,)create:
* '''a brick wall''', represented by adding a red cuboid and changing it to a rectangle, 15mm wide, 120mm high and 120mm deep,
:: located at coordinates x = 0, y = 0, z = 60,
:: with rotation settings X = 0, Y = 0, Z = 0;

* '''a path''', represented by a grey rectangle, 240mm wide, 100mm high and 0mm deep,
:: located at coordinatesx = 125mm, y = 0mm, z = 0mm,
:: with rotation settings of X = 0, Y = 0, Z = 0;

* '''a cone''', couloured light blue, representing the sensing region of the PIR, with width = 70mm, height = 250mm, depth 95mm,
:: located at coordinates x = 45mm, y = 0mm, z = 80mm,
:: with rotation settings of X = 0, Y = -55, Z = 0.

* Drag the mouse cursor over these three elements and group them together.

This produces 'group 1'.
:: Give this group:
::: dimensions - width = 265mm, height = 250mm, depth = 135mm;
::: coordinates - x = 128, y = 0, z = 68;
::: rotation - X = 0, Y = 0, Z = 0.

Also on the System Panel, create an intruder, by:
* adding four spheres, and configuring the properties as follows:
:: sphere 1 ('''the head'''):
::: colour pink;
::: dimensions - width = 12mm, height = 13mm, depth = 15mm;
::: coordinates - x = -2.2, y = 0.7, z = 22;
::: rotation - X = 90, Y = 0, Z = 0.

:: sphere 2 ('''the body'''):
::: colour blue;
::: dimensions - width = 14mm, height = 26mm, depth = 24mm;
::: coordinates - x = -2.2, y = 0.5, z = 4;
::: rotation - X = 90, Y = 0, Z = -180.

:: sphere 3 ('''the legs'''):
::: colour dark green;
::: dimensions - width = 9mm, height = 23mm, depth = 15mm;
::: coordinates - x = -2.2, y = 1, z = -16;
::: rotation - X = 90, Y = 0, Z = -180.

:: sphere 4 ('''the feet'''):
::: colour black;
::: dimensions - width = 6mm, height = 15mm, depth = 25mm;
::: coordinates - x = -6, y = 0, z = -25;
::: rotation - X = 90, Y = 90, Z = 0.

* Drag the mouse cursor over the four spheres and group them together.

This produces 'group 2'.
:: Give it:
::: dimensions - width = 18mm, height = 32mm, depth = 60mm;
::: coordinates - x = 165, y = 0, z = 28;
::: rotation - X = 0, Y = 0, Z = 0.

The System Panel should resemble the image shown above. (The image has been rotated to show all components. The table-top is coloured green.)

Click on the 'Collisions' icon, [[File:Gen Panel Object Collision Move Around.png|35px]] and select the 'Move through' option, which allows the intruder to enter the detection cone.

==The Dashboard Panel==
[[File:Exercise SimIcon dash.png|right|200px]]
* Open the 'Outputs' toolbox, and locate the 'LED 5mm Panel' device.
* Click on the down arrow next to it and choose the 'Add to dashboard panel' option.
* Zoom in to the Dashboard Panel to make the LED large enough to see.
* Click on the LED and configure its properties as follows:
::* choose a suitable colour, such as red;
::* connect it to Port A, bit 0.

==The Flowcode program==

The plan is to move the intruder towards the detection cone using the 'MoveAlong' macro. This '''changes''' the x coordinate of the intruder '''by an amount specified by the variable 'xpos''''.

When the intruder enters the detection zone, the macro 'CollisionTest' returns a value of '1' in the variable 'hit'.

At that point, we want to stop any more movement so that we can look at the x coordinate of the intruder. To do this, we change the value of 'xpos' to zero.

* [[Opening Flowcode|Open Flowcode]].

* On the Startup screen, click on 'New project' to [[Creating Flowcharts|create a new flowchart]].

* Add the icons shown in the flowchart:
:* a loop icon, configured as an infinite loop, and within it:
::* two Simulation macro icons [[File:Btn Simulation Macro.gif|border]];
::* a decision icon with:
:::* a 'Yes' loop containing an output icon, followed by a delay icon and then a calculation icon;
:::* a 'No' loop containing an output icon, followed by a delay icon;
[[File:Exercise SimIcon Sim move.png|right|450px]]

* Configure the icons, by double clicking on each in turn, as follows:
::* the top Simulation macro:
:::* name it "Move the intruder";
:::* click on the 'Panel' tab, and then on the 'Position' folder;
:::* click on the 'MoveAlong' macro and:
::::* choose 'group2'(the intruder)as the Handle;
::::* choose 'shape1'( the brick wall) as the Axis;
::::* click on the down arrow on the end of the 'X' row, and create a floating point variable called "xpos", with an initial value 5.0, to use as the X variable;
::::* click on OK.

::* the second Simulation macro:
:::* name it "Check detection";
:::* click on the 'Panel' tab, and then on the 'Collision' folder;
[[File:Exercise SimIcon Sim test.png|right|300px]]
:::* click on the 'TestSingle' macro and:
::::* choose 'shape2'(the detection cone) for 'Pos' and 'shape5' (the intruder's head,) for 'Test';
:::* use the down arrow at the end of the 'Return Value' box to create a boolean variable caled "hit" to use as the 'Return Value'.
::::* click on OK.

::* the decision icon:
:::* name it "Intruder detected?";
:::* insert the condition "hit = 1";
:::* click on OK.

:::* In the 'Yes' loop:
::::* name the Output icon "Switch on lamp";
::::* send value '1' to Port A single bit 0;
::::* click on OK.

::::* name the Delay icon "Wait 100ms";
::::* configure it to give a delay of 100ms;
::::* click on OK.

::::* name the Calculation icon "Stop movement";
::::* in the 'Calculations:' box, insert "xpos = 0" to reduce the distance incremented each time to zero;
::::* click on OK.

:::* In the 'No' loop:
::::* name the Output icon "Switch off lamp";
::::* send value '0' to Port A single bit 0;
::::* click on OK.

::::* name the Delay icon "Wait 100ms";
::::* configure it to give a delay of 100ms;
::::* click on OK.

The Flowcode flowchart resembles the one shown below:

[[File:Exercise SimIcon Simflow.png|center|500px]]
==Testing==

* Run the simulation.
: The intruder should move towards the house, until he enters the detection zone.

: At this point, the warning lamp turns on and he stops.

* Stop the simulation, and click on the image of the intruder. You can now read the x coordinate from the Panel properties box.

* Change the height of the PIR sensor on the wall, or the angle of the detection cone, and see what happens to this coordinate.

==DON'T DOWNLOAD IT!!==
The important point is that the two Simulation macros do not compile to code that can be downloaded to a microcontroller. They affect only the simulation of the program.

Exercise - Using Simulation Macros

2013-08-30T12:15:19Z

JohnVerrill:

<sidebar>Sidebar: What Is a Macro?</sidebar>
Simulation macros are a form of Component macros. Their purpose is to make simulation more realistic by adding physical components to the electronic devices.

When the Flowcode program is compiled and downloaded to a microcontroller, they are ignored - hence the name Simulation macros.

Even a cursory glance at the dialogue box used to configure them shows that they are very powerful devices, with a huge range of possible effects.

This exercise uses two of them to illustrate the use of a PIR (Passive Infra-Red sensor) to operate an intruder sensor.

__TOC__

==The scenario==

The scene depicts the front of a house.
[[File:Exercise SimIcon pan.png|center|350px]]

A PIR sensor is mounted on the wall of the house, above the path leading across the garden.

The data sheet for the PIR shows that it is sensitive to a range of 10 metres, within a cone of angle 100 degrees.

Its detection area is represented in the image by the pale blue cone.

When an intruder enters the detection cone, a warning lamp lights up in the house.

This exercise allows us to investigate factors such as the height of the sensor on the brick wall and the angle of the detection zone, so that these can be optimised for a typical intruder height.

==The System Panel==

On the System Panel, viewed from above (the default position,)create:
* '''a brick wall''', represented by adding a red cuboid and changing it to a rectangle, 15mm wide, 120mm high and 120mm deep,
:: located at coordinates x = 0, y = 0, z = 60,
:: with rotation settings X = 0, Y = 0, Z = 0;

* '''a path''', represented by a grey rectangle, 240mm wide, 100mm high and 0mm deep,
:: located at coordinatesx = 125mm, y = 0mm, z = 0mm,
:: with rotation settings of X = 0, Y = 0, Z = 0;

* '''a cone''', couloured light blue, representing the sensing region of the PIR, with width = 70mm, height = 250mm, depth 95mm,
:: located at coordinates x = 45mm, y = 0mm, z = 80mm,
:: with rotation settings of X = 0, Y = -55, Z = 0.

* Drag the mouse cursor over these three elements and group them together.

This produces 'group 1'.
:: Give this group:
::: dimensions - width = 265mm, height = 250mm, depth = 135mm;
::: coordinates - x = 128, y = 0, z = 68;
::: rotation - X = 0, Y = 0, Z = 0.

Also on the System Panel, create an intruder, by:
* adding four spheres, and configuring the properties as follows:
:: sphere 1 ('''the head'''):
::: colour pink;
::: dimensions - width = 12mm, height = 13mm, depth = 15mm;
::: coordinates - x = -2.2, y = 0.7, z = 22;
::: rotation - X = 90, Y = 0, Z = 0.

:: sphere 2 ('''the body'''):
::: colour blue;
::: dimensions - width = 14mm, height = 26mm, depth = 24mm;
::: coordinates - x = -2.2, y = 0.5, z = 4;
::: rotation - X = 90, Y = 0, Z = -180.

:: sphere 3 ('''the legs'''):
::: colour dark green;
::: dimensions - width = 9mm, height = 23mm, depth = 15mm;
::: coordinates - x = -2.2, y = 1, z = -16;
::: rotation - X = 90, Y = 0, Z = -180.

:: sphere 4 ('''the feet'''):
::: colour black;
::: dimensions - width = 6mm, height = 15mm, depth = 25mm;
::: coordinates - x = -6, y = 0, z = -25;
::: rotation - X = 90, Y = 90, Z = 0.

* Drag the mouse cursor over the four spheres and group them together.

This produces 'group 2'.
:: Give it:
::: dimensions - width = 18mm, height = 32mm, depth = 60mm;
::: coordinates - x = 165, y = 0, z = 28;
::: rotation - X = 0, Y = 0, Z = 0.

The System Panel should resemble the image shown above. (The image has been rotated to show all components. The table-top is coloured green.)

Click on the 'Collisions' icon, [[File:Gen Panel Object Collision Move Around.png|35px]] and select the 'Move through' option, which allows the intruder to enter the detection cone.

==The Dashboard Panel==
[[File:Exercise SimIcon dash.png|right|200px]]
* Open the 'Outputs' toolbox, and locate the 'LED 5mm Panel' device.
* Click on the down arrow next to it and choose the 'Add to dashboard panel' option.
* Zoom in to the Dashboard Panel to make the LED large enough to see.
* Click on the LED and configure its properties as follows:
::* choose a suitable colour, such as red;
::* connect it to Port A, bit 0.

==The Flowcode program==

The plan is to move the intruder towards the detection cone using the 'MoveAlong' macro. This '''changes''' the x coordinate of the intruder '''by an amount specified by the variable 'xpos''''.

When the intruder enters the detection zone, the macro 'CollisionTest' returns a value of '1' in the variable 'hit'.

At that point, we want to stop any more movement so that we can look at the x coordinate of the intruder. To do this, we change the value of 'xpos' to zero.

* [[Opening Flowcode|Open Flowcode]].

* On the Startup screen, click on 'New project' to [[Creating Flowcharts|create a new flowchart]].

* Add the icons shown in the flowchart:
:* a loop icon, configured as an infinite loop, and within it:
::* two Simulation macro icons [[File:Btn Simulation Macro.gif|border]];
::* a decision icon with:
:::* a 'Yes' loop containing an output icon, followed by a delay icon and then a calculation icon;
:::* a 'No' loop containing an output icon, followed by a delay icon;
[[File:Exercise SimIcon Sim move.png|right|450px]]

* Configure the icons, by double clicking on each in turn, as follows:
::* the top Simulation macro:
:::* name it "Move the intruder";
:::* click on the 'Panel' tab, and then on the 'Position' folder;
:::* click on the 'MoveAlong' macro and:
::::* choose 'group2'(the intruder)as the Handle;
::::* choose 'shape1'( the brick wall) as the Axis;
::::* click on the down arrow on the end of the 'X' row, and create a floating point variable called "xpos", with an initial value 5.0, to use as the X variable;
::::* click on OK.

::* the second Simulation macro:
:::* name it "Check detection";
:::* click on the 'Panel' tab, and then on the 'Collision' folder;
[[File:Exercise SimIcon Sim test.png|right|300px]]
:::* click on the 'TestSingle' macro and:
::::* choose 'shape2'(the detection cone) for 'Pos' and 'shape5' (the intruder's head,) for 'Test';
:::* use the down arrow at the end of the 'Return Value' box to create a boolean variable caled "hit" to use as the 'Return Value'.
::::* click on OK.

::* the decision icon:
:::* name it "Intruder detected?";
:::* insert the condition "hit = 1";
:::* click on OK.

:::* In the 'Yes' loop:
::::* name the Output icon "Switch on lamp";
::::* send value '1' to Port A single bit 0;
::::* click on OK.

::::* name the Delay icon "Wait 100ms";
::::* configure it to give a delay of 100ms;
::::* click on OK.

::::* name the Calculation icon "Stop movement";
::::* in the 'Calculations:' box, insert "xpos = 0" to reduce the distance incremented each time to zero;
::::* click on OK.

:::* In the 'No' loop:
::::* name the Output icon "Switch off lamp";
::::* send value '0' to Port A single bit 0;
::::* click on OK.

::::* name the Delay icon "Wait 100ms";
::::* configure it to give a delay of 100ms;
::::* click on OK.

The Flowcode flowchart resembles the one shown below:

==Testing==

* Run the simulation.
: The intruder should move towards the house, until he enters the detection zone.

: At this point, the warning lamp turns on and he stops.

* Stop the simulation, and click on the image of the intruder. You can now read the x coordinate from the Panel properties box.

* Change the height of the PIR sensor on the wall, or the angle of the detection cone, and see what happens to this coordinate.

==DON'T DOWNLOAD IT!!==
The important point is that the two Simulation macros do not compile to code that can be downloaded to a microcontroller. They affect only the simulation of the program.

File:Exercise SimIcon Simflow.png

2013-08-30T12:13:05Z

JohnVerrill:

Exercise - Using Simulation Macros

2013-08-30T11:04:12Z

JohnVerrill:

<sidebar>Sidebar: What Is a Macro?</sidebar>
Simulation macros are a form of Component macros. Their purpose is to make simulation more realistic by adding physical components to the electronic devices.

When the Flowcode program is compiled and downloaded to a microcontroller, they are ignored - hence the name Simulation macros.

Even a cursory glance at the dialogue box used to configure them shows that they are very powerful devices, with a huge range of possible effects.

This exercise uses two of them to illustrate the use of a PIR (Passive Infra-Red sensor) to operate an intruder sensor.

__TOC__

==The scenario==

The scene depicts the front of a house.
[[File:Exercise SimIcon pan.png|center|350px]]

A PIR sensor is mounted on the wall of the house, above the path leading across the garden.

The data sheet for the PIR shows that it is sensitive to a range of 10 metres, within a cone of angle 100 degrees.

Its detection area is represented in the image by the pale blue cone.

When an intruder enters the detection cone, a warning lamp lights up in the house.

This exercise allows us to investigate factors such as the height of the sensor on the brick wall and the angle of the detection zone, so that these can be optimised for a typical intruder height.

==The System Panel==

On the System Panel, viewed from above (the default position,)create:
* '''a brick wall''', represented by adding a red cuboid and changing it to a rectangle, 15mm wide, 120mm high and 120mm deep,
:: located at coordinates x = 0, y = 0, z = 60,
:: with rotation settings X = 0, Y = 0, Z = 0;

* '''a path''', represented by a grey rectangle, 240mm wide, 100mm high and 0mm deep,
:: located at coordinatesx = 125mm, y = 0mm, z = 0mm,
:: with rotation settings of X = 0, Y = 0, Z = 0;

* '''a cone''', couloured light blue, representing the sensing region of the PIR, with width = 70mm, height = 250mm, depth 95mm,
:: located at coordinates x = 45mm, y = 0mm, z = 80mm,
:: with rotation settings of X = 0, Y = -55, Z = 0.

* Drag the mouse cursor over these three elements and group them together.

This produces 'group 1'.
:: Give this group:
::: dimensions - width = 265mm, height = 250mm, depth = 135mm;
::: coordinates - x = 128, y = 0, z = 68;
::: rotation - X = 0, Y = 0, Z = 0.

Also on the System Panel, create an intruder, by:
* adding four spheres, and configuring the properties as follows:
:: sphere 1 ('''the head'''):
::: colour pink;
::: dimensions - width = 12mm, height = 13mm, depth = 15mm;
::: coordinates - x = -2.2, y = 0.7, z = 22;
::: rotation - X = 90, Y = 0, Z = 0.

:: sphere 2 ('''the body'''):
::: colour blue;
::: dimensions - width = 14mm, height = 26mm, depth = 24mm;
::: coordinates - x = -2.2, y = 0.5, z = 4;
::: rotation - X = 90, Y = 0, Z = -180.

:: sphere 3 ('''the legs'''):
::: colour dark green;
::: dimensions - width = 9mm, height = 23mm, depth = 15mm;
::: coordinates - x = -2.2, y = 1, z = -16;
::: rotation - X = 90, Y = 0, Z = -180.

:: sphere 4 ('''the feet'''):
::: colour black;
::: dimensions - width = 6mm, height = 15mm, depth = 25mm;
::: coordinates - x = -6, y = 0, z = -25;
::: rotation - X = 90, Y = 90, Z = 0.

* Drag the mouse cursor over the four spheres and group them together.

This produces 'group 2'.
:: Give it:
::: dimensions - width = 18mm, height = 32mm, depth = 60mm;
::: coordinates - x = 165, y = 0, z = 28;
::: rotation - X = 0, Y = 0, Z = 0.

The System Panel should resemble the image shown above. (The image has been rotated to show all components. The table-top is coloured green.)

Click on the 'Collisions' icon, [[File:Gen Panel Object Collision Move Around.png|35px]] and select the 'Move through' option, which allows the intruder to enter the detection cone.

==The Dashboard Panel==
[[File:Exercise SimIcon dash.png|right|200px]]
* Open the 'Outputs' toolbox, and locate the 'LED 5mm Panel' device.
* Click on the down arrow next to it and choose the 'Add to dashboard panel' option.
* Zoom in to the Dashboard Panel to make the LED large enough to see.
* Click on the LED and configure its properties as follows:
::* choose a suitable colour, such as red;
::* connect it to Port A, bit 0.

==The Flowcode program==

The plan is to move the intruder towards the detection cone using the 'MoveAlong' macro. This '''changes''' the x coordinate of the intruder '''by an amount specified by the variable 'xpos''''.

When the intruder enters the detection zone, the macro 'CollisionTest' returns a value of '1' in the variable 'hit'.

At that point, we want to stop any more movement so that we can look at the x coordinate of the intruder. To do this, we change the value of 'xpos' to zero.

* [[Opening Flowcode|Open Flowcode]].

* On the Startup screen, click on 'New project' to [[Creating Flowcharts|create a new flowchart]].

* Add the icons shown in the flowchart:
:* a loop icon, configured as an infinite loop, and within it:
::* two Simulation macro icons [[File:Btn Simulation Macro.gif|border]];
::* a decision icon with:
:::* a 'Yes' loop containing an output icon, followed by a delay icon and then a calculation icon;
:::* a 'No' loop containing an output icon, followed by a delay icon;
[[File:Exercise SimIcon Sim move.png|right|450px]]

* Configure the icons, by double clicking on each in turn, as follows:
::* the top Simulation macro:
:::* name it "Move the intruder";
:::* click on the 'Panel' tab, and then on the 'Position' folder;
:::* click on the 'MoveAlong' macro and:
::::* choose 'group2'(the intruder)as the Handle;
::::* choose 'shape1'( the brick wall) as the Axis;
::::* click on the down arrow on the end of the 'X' row, and create a floating point variable called "xpos", with an initial value 5.0, to use as the X variable;
::::* click on OK.

::* the second Simulation macro:
:::* name it "Check detection";
:::* click on the 'Panel' tab, and then on the 'Collision' folder;
[[File:Exercise SimIcon Sim test.png|right|300px]]
:::* click on the 'TestSingle' macro and:
::::* choose 'shape2'(the detection cone) for 'Pos' and 'shape5' (the intruder's head,) for 'Test';
:::* use the down arrow at the end of the 'Return Value' box to create a boolean variable caled "hit" to use as the 'Return Value'.
::::* click on OK.

::* the decision icon:
:::* name it "Intruder detected?";
:::* insert the condition "hit = 1";
:::* click on OK.

:::* In the 'Yes' loop:
::::* name the Output icon "Switch on lamp";
::::* send value '1' to Port A single bit 0;
::::* click on OK.

::::* name the Delay icon "Wait 100ms";
::::* configure it to give a delay of 100ms;
::::* click on OK.

::::* name the Calculation icon "Stop movement";
::::* in the 'Calculations:' box, insert "xpos = 0" to reduce the distance incremented each time to zero;
::::* click on OK.

:::* In the 'No' loop:
::::* name the Output icon "Switch off lamp";
::::* send value '0' to Port A single bit 0;
::::* click on OK.

::::* name the Delay icon "Wait 100ms";
::::* configure it to give a delay of 100ms;
::::* click on OK.

The Flowcode flowchart resembles the one shown below:

[[File:Exercise SimIcon Simflow.png|center|500px]]

==Testing==

* Run the simulation.
: The intruder should move towards the house, until he enters the detection zone.

: At this point, the warning lamp turns on and he stops.

* Stop the simulation, and click on the image of the intruder. You can now read the x coordinate from the Panel properties box.

* Change the height of the PIR sensor on the wall, or the angle of the detection cone, and see what happens to this coordinate.

==DON'T DOWNLOAD IT!!==
The important point is that the two Simulation macros do not compile to code that can be downloaded to a microcontroller. They affect only the simulation of the program.

Exercise - Using Simulation Macros

2013-08-30T08:58:27Z

JohnVerrill:

<sidebar>Sidebar: What Is a Macro?</sidebar>
Simulation macros are a form of Component macros. Their purpose is to make simulation more realistic by adding physical components to the electronic devices.

When the Flowcode program is compiled and downloaded to a microcontroller, they are ignored - hence the name Simulation macros.

Even a cursory glance at the dialogue box used to configure them shows that they are very powerful devices, with a huge range of possible effects.

This exercise uses two of them to illustrate the use of a PIR (Passive Infra-Red sensor) to operate an intruder sensor.

__TOC__

==The scenario==

The scene depicts the front of a house.
[[File:Exercise SimIcon pan.png|center|350px]]

A PIR sensor is mounted on the wall of the house, above the path leading across the garden.

The data sheet for the PIR shows that it is sensitive to a range of 10 metres, within a cone of angle 100 degrees.

Its detection area is represented in the image by the pale blue cone.

When an intruder enters the detection cone, a warning lamp lights up in the house.

This exercise allows us to investigate factors such as the height of the sensor on the brick wall and the angle of the detection zone, so that these can be optimised for a typical intruder height.

==The System Panel==

On the System Panel, viewed from above (the default position,)create:
* '''a brick wall''', represented by adding a red cuboid and changing it to a rectangle, 15mm wide, 120mm high and 120mm deep,
:: located at coordinates x = 0, y = 0, z = 60,
:: with rotation settings X = 0, Y = 0, Z = 0;

* '''a path''', represented by a grey rectangle, 240mm wide, 100mm high and 0mm deep,
:: located at coordinatesx = 125mm, y = 0mm, z = 0mm,
:: with rotation settings of X = 0, Y = 0, Z = 0;

* '''a cone''', couloured light blue, representing the sensing region of the PIR, with width = 70mm, height = 250mm, depth 95mm,
:: located at coordinates x = 45mm, y = 0mm, z = 80mm,
:: with rotation settings of X = 0, Y = -55, Z = 0.

* Drag the mouse cursor over these three elements and group them together.

This produces 'group 1'.
:: Give this group:
::: dimensions - width = 265mm, height = 250mm, depth = 135mm;
::: coordinates - x = 128, y = 0, z = 68;
::: rotation - X = 0, Y = 0, Z = 0.

Also on the System Panel, create an intruder, by:
* adding four spheres, and configuring the properties as follows:
:: sphere 1 ('''the head'''):
::: colour pink;
::: dimensions - width = 12mm, height = 13mm, depth = 15mm;
::: coordinates - x = -2.2, y = 0.7, z = 22;
::: rotation - X = 90, Y = 0, Z = 0.

:: sphere 2 ('''the body'''):
::: colour blue;
::: dimensions - width = 14mm, height = 26mm, depth = 24mm;
::: coordinates - x = -2.2, y = 0.5, z = 4;
::: rotation - X = 90, Y = 0, Z = -180.

:: sphere 3 ('''the legs'''):
::: colour dark green;
::: dimensions - width = 9mm, height = 23mm, depth = 15mm;
::: coordinates - x = -2.2, y = 1, z = -16;
::: rotation - X = 90, Y = 0, Z = -180.

:: sphere 4 ('''the feet'''):
::: colour black;
::: dimensions - width = 6mm, height = 15mm, depth = 25mm;
::: coordinates - x = -6, y = 0, z = -25;
::: rotation - X = 90, Y = 90, Z = 0.

* Drag the mouse cursor over the four spheres and group them together.

This produces 'group 2'.
:: Give it:
::: dimensions - width = 18mm, height = 32mm, depth = 60mm;
::: coordinates - x = 165, y = 0, z = 28;
::: rotation - X = 0, Y = 0, Z = 0.

The System Panel should resemble the image shown above. (The image has been rotated to show all components. The table-top is coloured green.)

Click on the 'Collisions' icon, [[File:Gen Panel Object Collision Move Around.png|35px]] and select the 'Move through' option, which allows the intruder to enter the detection cone.

==The Dashboard Panel==
[[File:Exercise SimIcon dash.png|right|200px]]
* Open the 'Outputs' toolbox, and locate the 'LED 5mm Panel' device.
* Click on the down arrow next to it and choose the 'Add to dashboard panel' option.
* Zoom in to the Dashboard Panel to make the LED large enough to see.
* Click on the LED and configure its properties as follows:
::* choose a suitable colour, such as red;
::* connect it to Port A, bit 0.

==The Flowcode program==

The plan is to move the intruder towards the detection cone using the 'MoveAlong' macro. This '''changes''' the x coordinate of the intruder '''by an amount specified by the variable 'xpos''''.

When the intruder enters the detection zone, the macro 'CollisionTest' returns a value of '1' in the variable 'hit'.

At that point, we want to stop any more movement so that we can look at the x coordinate of the intruder. To do this, we change the value of 'xpos' to zero.

* [[Opening Flowcode|Open Flowcode]].

* On the Startup screen, click on 'New project' to [[Creating Flowcharts|create a new flowchart]].

* Add the icons shown in the flowchart:
:* a loop icon, configured as an infinite loop, and within it:
::* two Simulation macro icons [[File:Btn Simulation Macro.gif|border]];
::* a decision icon with:
:::* a 'Yes' loop containing an output icon, followed by a delay icon and then a calculation icon;
:::* a 'No' loop containing an output icon, followed by a delay icon;
[[File:Exercise SimIcon Sim move.png|right|450px]]

* Configure the icons, by double clicking on each in turn, as follows:
::* the top Simulation macro:
:::* name it "Move the intruder";
:::* click on the 'Panel' tab, and then on the 'Position' folder;
:::* click on the 'MoveAlong' macro and:
::::* choose 'group2'(the intruder)as the Handle;
::::* choose 'shape1'( the brick wall) as the Axis;
::::* click on the down arrow on the end of the 'X' row, and create a floating point variable called "xpos", with an initial value 5.0, to use as the X variable;
::::* click on OK.

::* the second Simulation macro:
:::* name it "Check detection";
:::* click on the 'Panel' tab, and then on the 'Collision' folder;
[[File:Exercise SimIcon Sim test.png|right|300px]]
:::* click on the 'TestSingle' macro and:
::::* choose 'shape2'(the detection cone) for 'Pos' and 'shape5' (the intruder's head,) for 'Test';
:::* use the down arrow at the end of the 'Return Value' box to create a boolean variable caled "hit" to use as the 'Return Value'.
::::* click on OK.

::* the decision icon:
:::* name it "Intruder detected?";
:::* insert the condition "hit = 1";
:::* click on OK.

:::* In the 'Yes' loop:
::::* name the Output icon "Switch on lamp";
::::* send value '1' to Port A single bit 0;
::::* click on OK.

::::* name the Delay icon "Wait 100ms";
::::* configure it to give a delay of 100ms;
::::* click on OK.

::::* name the Calculation icon "Stop movement";
::::* in the 'Calculations:' box, insert "xpos = 0" to reduce the distance incremented each time to zero;
::::* click on OK.

:::* In the 'No' loop:
::::* name the Output icon "Switch off lamp";
::::* send value '0' to Port A single bit 0;
::::* click on OK.

::::* name the Delay icon "Wait 100ms";
::::* configure it to give a delay of 100ms;
::::* click on OK.

The Flowcode flowchart resembles the one shown below:

[[File:Exercise SimIcon Simprog.png|center|500px]]

==Testing==

* Run the simulation.
: The intruder should move towards the house, until he enters the detection zone.

: At this point, the warning lamp turns on and he stops.

* Stop the simulation, and click on the image of the intruder. You can now read the x coordinate from the Panel properties box.

* Change the height of the PIR sensor on the wall, or the angle of the detection cone, and see what happens to this coordinate.

==DON'T DOWNLOAD IT!!==
The important point is that the two Simulation macros do not compile to code that can be downloaded to a microcontroller. They affect only the simulation of the program.

Exercise - Using Simulation Macros

2013-08-26T16:35:24Z

JohnVerrill:

Simulation macros are a form of Component macros. Their purpose is to make simulation more realistic by adding physical components to the electronic devices.

When the Flowcode program is compiled and downloaded to a microcontroller, they are ignored - hence the name Simulation macros.

Even a cursory glance at the dialogue box used to configure them shows that they are very powerful devices, with a huge range of possible effects.

This exercise uses two of them to illustrate the use of a PIR (Passive Infra-Red sensor) to operate an intruder sensor.

__TOC__

==The scenario==

The scene depicts the front of a house.
[[File:Exercise SimIcon pan.png|center|350px]]

A PIR sensor is mounted on the wall of the house, above the path leading across the garden.

The data sheet for the PIR shows that it is sensitive to a range of 10 metres, within a cone of angle 100 degrees.

Its detection area is represented in the image by the pale blue cone.

When an intruder enters the detection cone, a warning lamp lights up in the house.

This exercise allows us to investigate factors such as the height of the sensor on the brick wall and the angle of the detection zone, so that these can be optimised for a typical intruder height.

==The System Panel==

On the System Panel, viewed from above (the default position,)create:
* '''a brick wall''', represented by adding a red cuboid and changing it to a rectangle, 15mm wide, 120mm high and 120mm deep,
:: located at coordinates x = 0, y = 0, z = 60,
:: with rotation settings X = 0, Y = 0, Z = 0;

* '''a path''', represented by a grey rectangle, 240mm wide, 100mm high and 0mm deep,
:: located at coordinatesx = 125mm, y = 0mm, z = 0mm,
:: with rotation settings of X = 0, Y = 0, Z = 0;

* '''a cone''', couloured light blue, representing the sensing region of the PIR, with width = 70mm, height = 250mm, depth 95mm,
:: located at coordinates x = 45mm, y = 0mm, z = 80mm,
:: with rotation settings of X = 0, Y = -55, Z = 0.

* Drag the mouse cursor over these three elements and group them together.

This produces 'group 1'.
:: Give this group:
::: dimensions - width = 265mm, height = 250mm, depth = 135mm;
::: coordinates - x = 128, y = 0, z = 68;
::: rotation - X = 0, Y = 0, Z = 0.

Also on the System Panel, create an intruder, by:
* adding four spheres, and configuring the properties as follows:
:: sphere 1 ('''the head'''):
::: colour pink;
::: dimensions - width = 12mm, height = 13mm, depth = 15mm;
::: coordinates - x = -2.2, y = 0.7, z = 22;
::: rotation - X = 90, Y = 0, Z = 0.

:: sphere 2 ('''the body'''):
::: colour blue;
::: dimensions - width = 14mm, height = 26mm, depth = 24mm;
::: coordinates - x = -2.2, y = 0.5, z = 4;
::: rotation - X = 90, Y = 0, Z = -180.

:: sphere 3 ('''the legs'''):
::: colour dark green;
::: dimensions - width = 9mm, height = 23mm, depth = 15mm;
::: coordinates - x = -2.2, y = 1, z = -16;
::: rotation - X = 90, Y = 0, Z = -180.

:: sphere 4 ('''the feet'''):
::: colour black;
::: dimensions - width = 6mm, height = 15mm, depth = 25mm;
::: coordinates - x = -6, y = 0, z = -25;
::: rotation - X = 90, Y = 90, Z = 0.

* Drag the mouse cursor over the four spheres and group them together.

This produces 'group 2'.
:: Give it:
::: dimensions - width = 18mm, height = 32mm, depth = 60mm;
::: coordinates - x = 165, y = 0, z = 28;
::: rotation - X = 0, Y = 0, Z = 0.

The System Panel should resemble the image shown above. (The image has been rotated to show all components. The table-top is coloured green.)

Click on the 'Collisions' icon, [[File:Gen Panel Object Collision Move Around.png|35px]] and select the 'Move through' option, which allows the intruder to enter the detection cone.

==The Dashboard Panel==
[[File:Exercise SimIcon dash.png|right|200px]]
* Open the 'Outputs' toolbox, and locate the 'LED 5mm Panel' device.
* Click on the down arrow next to it and choose the 'Add to dashboard panel' option.
* Zoom in to the Dashboard Panel to make the LED large enough to see.
* Click on the LED and configure its properties as follows:
::* choose a suitable colour, such as red;
::* connect it to Port A, bit 0.

==The Flowcode program==

The plan is to move the intruder towards the detection cone using the 'MoveAlong' macro. This '''changes''' the x coordinate of the intruder '''by an amount specified by the variable 'xpos''''.

When the intruder enters the detection zone, the macro 'CollisionTest' returns a value of '1' in the variable 'hit'.

At that point, we want to stop any more movement so that we can look at the x coordinate of the intruder. To do this, we change the value of 'xpos' to zero.

* [[Opening Flowcode|Open Flowcode]].

* On the Startup screen, click on 'New project' to [[Creating Flowcharts|create a new flowchart]].

* Add the icons shown in the flowchart:
:* a loop icon, configured as an infinite loop, and within it:
::* two Simulation macro icons [[File:Btn Simulation Macro.gif|35px]];
::* a decision icon with:
:::* a 'Yes' loop containing an output icon, followed by a delay icon and then a calculation icon;
:::* a 'No' loop containing an output icon, followed by a delay icon;
[[File:Exercise SimIcon Sim move.png|right|450px]]

* Configure the icons, by double clicking on each in turn, as follows:
::* the top Simulation macro:
:::* name it "Move the intruder";
:::* click on the 'Panel' tab, and then on the 'Position' folder;
:::* click on the 'MoveAlong' macro and:
::::* choose 'group2'(the intruder)as the Handle;
::::* choose 'shape1'( the brick wall) as the Axis;
::::* click on the down arrow on the end of the 'X' row, and create a floating point variable called "xpos", with an initial value 5.0, to use as the X variable;
::::* click on OK.

::* the second Simulation macro:
:::* name it "Check detection";
:::* click on the 'Panel' tab, and then on the 'Collision' folder;
[[File:Exercise SimIcon Sim test.png|right|300px]]
:::* click on the 'TestSingle' macro and:
::::* choose 'shape2'(the detection cone) for 'Pos' and 'shape5' (the intruder's head,) for 'Test';
:::* use the down arrow at the end of the 'Return Value' box to create a boolean variable caled "hit" to use as the 'Return Value'.
::::* click on OK.

::* the decision icon:
:::* name it "Intruder detected?";
:::* insert the condition "hit = 1";
:::* click on OK.

:::* In the 'Yes' loop:
::::* name the Output icon "Switch on lamp";
::::* send value '1' to Port A single bit 0;
::::* click on OK.

::::* name the Delay icon "Wait 100ms";
::::* configure it to give a delay of 100ms;
::::* click on OK.

::::* name the Calculation icon "Stop movement";
::::* in the 'Calculations:' box, insert "xpos = 0" to reduce the distance incremented each time to zero;
::::* click on OK.

:::* In the 'No' loop:
::::* name the Output icon "Switch off lamp";
::::* send value '0' to Port A single bit 0;
::::* click on OK.

::::* name the Delay icon "Wait 100ms";
::::* configure it to give a delay of 100ms;
::::* click on OK.

The Flowcode flowchart resembles the one shown below:

[[File:Exercise SimIcon Simprog.png|center|500px]]

==Testing==

* Run the simulation.
: The intruder should move towards the house, until he enters the detection zone.

: At this point, the warning lamp turns on and he stops.

* Stop the simulation, and click on the image of the intruder. You can now read the x coordinate from the Panel properties box.

* Change the height of the PIR sensor on the wall, or the angle of the detection cone, and see what happens to this coordinate.

==Downloading the program==

* Click on the 'Compile to chip' icon, to download the program to the microcontroller.

* Run the program on the hardware. Nothing happens.
: The software is waiting for the value of the variable 'hit' to change to logic 1. However, there is no hardware attached to make this happen.
: There are two remedies:
::* Add a PIR sensor to the hardware, and connect it to Port A, bit 0.
::* Use a switch, connected to Port A, bit 0 to mimic the action of the PIR sensor.

: The important point is that the two Simulation macros did not compile to any code that was downloaded to the microcontroller. They affected only the simulation of the program.

Exercise - Using Simulation Macros

2013-08-26T16:34:56Z

JohnVerrill:

Simulation macros are a form of Component macros. Their purpose is to make simulation more realistic by adding physical components to the electronic devices.

When the Flowcode program is compiled and downloaded to a microcontroller, they are ignored - hence the name Simulation macros.

Even a cursory glance at the dialogue box used to configure them shows that they are very powerful devices, with a huge range of possible effects.

This exercise uses two of them to illustrate the use of a PIR (Passive Infra-Red sensor) to operate an intruder sensor.

__TOC__

==The scenario==

The scene depicts the front of a house.
[[File:Exercise SimIcon pan.png|center|350px]]

A PIR sensor is mounted on the wall of the house, above the path leading across the garden.

The data sheet for the PIR shows that it is sensitive to a range of 10 metres, within a cone of angle 100 degrees.

Its detection area is represented in the image by the pale blue cone.

When an intruder enters the detection cone, a warning lamp lights up in the house.

This exercise allows us to investigate factors such as the height of the sensor on the brick wall and the angle of the detection zone, so that these can be optimised for a typical intruder height.

==The System Panel==

On the System Panel, viewed from above (the default position,)create:
* '''a brick wall''', represented by adding a red cuboid and changing it to a rectangle, 15mm wide, 120mm high and 120mm deep,
:: located at coordinates x = 0, y = 0, z = 60,
:: with rotation settings X = 0, Y = 0, Z = 0;

* '''a path''', represented by a grey rectangle, 240mm wide, 100mm high and 0mm deep,
:: located at coordinatesx = 125mm, y = 0mm, z = 0mm,
:: with rotation settings of X = 0, Y = 0, Z = 0;

* '''a cone''', couloured light blue, representing the sensing region of the PIR, with width = 70mm, height = 250mm, depth 95mm,
:: located at coordinates x = 45mm, y = 0mm, z = 80mm,
:: with rotation settings of X = 0, Y = -55, Z = 0.

* Drag the mouse cursor over these three elements and group them together.

This produces 'group 1'.
:: Give this group:
::: dimensions - width = 265mm, height = 250mm, depth = 135mm;
::: coordinates - x = 128, y = 0, z = 68;
::: rotation - X = 0, Y = 0, Z = 0.

Also on the System Panel, create an intruder, by:
* adding four spheres, and configuruing the properties as follows:
:: sphere 1 ('''the head'''):
::: colour pink;
::: dimensions - width = 12mm, height = 13mm, depth = 15mm;
::: coordinates - x = -2.2, y = 0.7, z = 22;
::: rotation - X = 90, Y = 0, Z = 0.

:: sphere 2 ('''the body'''):
::: colour blue;
::: dimensions - width = 14mm, height = 26mm, depth = 24mm;
::: coordinates - x = -2.2, y = 0.5, z = 4;
::: rotation - X = 90, Y = 0, Z = -180.

:: sphere 3 ('''the legs'''):
::: colour dark green;
::: dimensions - width = 9mm, height = 23mm, depth = 15mm;
::: coordinates - x = -2.2, y = 1, z = -16;
::: rotation - X = 90, Y = 0, Z = -180.

:: sphere 4 ('''the feet'''):
::: colour black;
::: dimensions - width = 6mm, height = 15mm, depth = 25mm;
::: coordinates - x = -6, y = 0, z = -25;
::: rotation - X = 90, Y = 90, Z = 0.

* Drag the mouse cursor over the four spheres and group them together.

This produces 'group 2'.
:: Give it:
::: dimensions - width = 18mm, height = 32mm, depth = 60mm;
::: coordinates - x = 165, y = 0, z = 28;
::: rotation - X = 0, Y = 0, Z = 0.

The System Panel should resemble the image shown above. (The image has been rotated to show all components. The table-top is coloured green.)

Click on the 'Collisions' icon, [[File:Gen Panel Object Collision Move Around.png|35px]] and select the 'Move through' option, which allows the intruder to enter the detection cone.

==The Dashboard Panel==
[[File:Exercise SimIcon dash.png|right|200px]]
* Open the 'Outputs' toolbox, and locate the 'LED 5mm Panel' device.
* Click on the down arrow next to it and choose the 'Add to dashboard panel' option.
* Zoom in to the Dashboard Panel to make the LED large enough to see.
* Click on the LED and configure its properties as follows:
::* choose a suitable colour, such as red;
::* connect it to Port A, bit 0.

==The Flowcode program==

The plan is to move the intruder towards the detection cone using the 'MoveAlong' macro. This '''changes''' the x coordinate of the intruder '''by an amount specified by the variable 'xpos''''.

When the intruder enters the detection zone, the macro 'CollisionTest' returns a value of '1' in the variable 'hit'.

At that point, we want to stop any more movement so that we can look at the x coordinate of the intruder. To do this, we change the value of 'xpos' to zero.

* [[Opening Flowcode|Open Flowcode]].

* On the Startup screen, click on 'New project' to [[Creating Flowcharts|create a new flowchart]].

* Add the icons shown in the flowchart:
:* a loop icon, configured as an infinite loop, and within it:
::* two Simulation macro icons [[File:Btn Simulation Macro.gif|35px]];
::* a decision icon with:
:::* a 'Yes' loop containing an output icon, followed by a delay icon and then a calculation icon;
:::* a 'No' loop containing an output icon, followed by a delay icon;
[[File:Exercise SimIcon Sim move.png|right|450px]]

* Configure the icons, by double clicking on each in turn, as follows:
::* the top Simulation macro:
:::* name it "Move the intruder";
:::* click on the 'Panel' tab, and then on the 'Position' folder;
:::* click on the 'MoveAlong' macro and:
::::* choose 'group2'(the intruder)as the Handle;
::::* choose 'shape1'( the brick wall) as the Axis;
::::* click on the down arrow on the end of the 'X' row, and create a floating point variable called "xpos", with an initial value 5.0, to use as the X variable;
::::* click on OK.

::* the second Simulation macro:
:::* name it "Check detection";
:::* click on the 'Panel' tab, and then on the 'Collision' folder;
[[File:Exercise SimIcon Sim test.png|right|300px]]
:::* click on the 'TestSingle' macro and:
::::* choose 'shape2'(the detection cone) for 'Pos' and 'shape5' (the intruder's head,) for 'Test';
:::* use the down arrow at the end of the 'Return Value' box to create a boolean variable caled "hit" to use as the 'Return Value'.
::::* click on OK.

::* the decision icon:
:::* name it "Intruder detected?";
:::* insert the condition "hit = 1";
:::* click on OK.

:::* In the 'Yes' loop:
::::* name the Output icon "Switch on lamp";
::::* send value '1' to Port A single bit 0;
::::* click on OK.

::::* name the Delay icon "Wait 100ms";
::::* configure it to give a delay of 100ms;
::::* click on OK.

::::* name the Calculation icon "Stop movement";
::::* in the 'Calculations:' box, insert "xpos = 0" to reduce the distance incremented each time to zero;
::::* click on OK.

:::* In the 'No' loop:
::::* name the Output icon "Switch off lamp";
::::* send value '0' to Port A single bit 0;
::::* click on OK.

::::* name the Delay icon "Wait 100ms";
::::* configure it to give a delay of 100ms;
::::* click on OK.

The Flowcode flowchart resembles the one shown below:

[[File:Exercise SimIcon Simprog.png|center|500px]]

==Testing==

* Run the simulation.
: The intruder should move towards the house, until he enters the detection zone.

: At this point, the warning lamp turns on and he stops.

* Stop the simulation, and click on the image of the intruder. You can now read the x coordinate from the Panel properties box.

* Change the height of the PIR sensor on the wall, or the angle of the detection cone, and see what happens to this coordinate.

==Downloading the program==

* Click on the 'Compile to chip' icon, to download the program to the microcontroller.

* Run the program on the hardware. Nothing happens.
: The software is waiting for the value of the variable 'hit' to change to logic 1. However, there is no hardware attached to make this happen.
: There are two remedies:
::* Add a PIR sensor to the hardware, and connect it to Port A, bit 0.
::* Use a switch, connected to Port A, bit 0 to mimic the action of the PIR sensor.

: The important point is that the two Simulation macros did not compile to any code that was downloaded to the microcontroller. They affected only the simulation of the program.

Exercise - Using Simulation Macros

2013-08-26T15:38:31Z

JohnVerrill:

Simulation macros are a form of Component macros. Their purpose is to make simulation more realistic by adding physical components to the electronic devices.

When the Flowcode program is compiled and downloaded to a microcontroller, they are ignored - hence the name Simulation macros.

Even a cursory glance at the dialogue box used to configure them shows that they are very powerful devices, with a huge range of possible effects.

This exercise uses two of them to illustrate the use of a PIR (Passive Infra-Red sensor) to operate an intruder sensor.

__TOC__

==The scenario==

The scene depicts the front of a house.
[[File:Exercise SimIcon pan.png|center|350px]]

A PIR sensor is mounted on the wall of the house, above the path leading across the garden.

The data sheet for the PIR shows that it is sensitive to a range of 10 metres, within a cone of angle 100 degrees.

Its detection area is represented in the image by the pale blue cone.

When an intruder enters the detection cone, a warning lamp lights up in the house.

This exercise allows us to investigate factors such as the height of the sensor on the brick wall and the angle of the detection zone, so that these can be optimised for a typical intruder height.

==The System Panel==

On the System Panel, viewed from above (the default position,)create:
* '''a brick wall''', represented by adding a red cuboid and changing it to a rectangle, 15mm wide, 120mm high and 120mm deep,
:: located at coordinates x = 0, y = 0, z = 60,
:: with rotation settings X = 0, Y = 0, Z = 0;

* '''a path''', represented by a grey rectangle, 240mm wide, 100mm high and 0mm deep,
:: located at coordinatesx = 125mm, y = 0mm, z = 0mm,
:: with rotation settings of X = 0, Y = 0, Z = 0;

* '''a cone''', couloured light blue, representing the sensing region of the PIR, with width = 70mm, height = 250mm, depth 95mm,
:: located at coordinates x = 45mm, y = 0mm, z = 80mm,
:: with rotation settings of X = 0, Y = -55, Z = 0.

* Drag the mouse cursor over these three elements and group them together.

This produces 'group 1'.
:: Give this group:
::: dimensions - width = 265mm, height = 250mm, depth = 135mm;
::: coordinates - x = 128, y = 0, z = 68;
::: rotation - X = 0, Y = 0, Z = 0.

Also on the System Panel, create an intruder, by:
* adding four spheres, and configuruing the properties as follows:
:: sphere 1 ('''the head'''):
::: colour pink;
::: dimensions - width = 12mm, height = 13mm, depth = 15mm;
::: coordinates - x = -2.2, y = 0.7, z = 22;
::: rotation - X = 90, Y = 0, Z = 0.

:: sphere 2 ('''the body'''):
::: colour blue;
::: dimensions - width = 14mm, height = 26mm, depth = 24mm;
::: coordinates - x = -2.2, y = 0.5, z = 4;
::: rotation - X = 90, Y = 0, Z = -180.

:: sphere 3 ('''the legs'''):
::: colour dark green;
::: dimensions - width = 9mm, height = 23mm, depth = 15mm;
::: coordinates - x = -2.2, y = 1, z = -16;
::: rotation - X = 90, Y = 0, Z = -180.

:: sphere 4 ('''the feet'''):
::: colour black;
::: dimensions - width = 6mm, height = 15mm, depth = 25mm;
::: coordinates - x = -6, y = 0, z = -25;
::: rotation - X = 90, Y = 90, Z = 0.

* Drag the mouse cursor over the four spheres and group them together.

This produces 'group 2'.
:: Give it:
::: dimensions - width = 18mm, height = 32mm, depth = 60mm;
::: coordinates - x = 165, y = 0, z = 28;
::: rotation - X = 0, Y = 0, Z = 0.

The System Panel should resemble the image shown above. (The image has been rotated to show all components. The table-top is coloured green.)

Click on the 'Collisions' icon, [[File:Gen Panel Object Collision Move Around.png|35px]] and select the 'Move through' option, which allows the intruder to enter the detection cone.

==The Dashboard Panel==
[[File:Exercise SimIcon dash.png|right|200px]]
* Open the 'Outputs' toolbox, and locate the 'LED 5mm Panel' device.
* Click on the down arrow next to it and choose the 'Add to dashboard panel' option.
* Zoom in to the Dashboard Panel to make the LED large enough to see.
* Click on the LED and configure its properties as follows:
::* choose a suitable colour, such as red;
::* connect it to Port A, bit 0.

==The Flowcode program==

The plan is to move the intruder towards the detection cone using the 'MoveAlong' macro. This '''changes''' the x coordinate of the intruder '''by an amount specified by the variable 'xpos''''.

When the intruder enters the detection zone, the macro 'CollisionTest' returns a value of '1' in the variable 'hit'.

At that point, we want to stop any more movement so that we can look at the x coordinate of the intruder. To do this, we change the value of 'xpos' to zero.

* [[Opening Flowcode|Open Flowcode]].

* On the Startup screen, click on 'New project' to [[Creating Flowcharts|create a new flowchart]].

* Add the icons shown in the flowchart:
:* a loop icon, configured as an infinite loop, and within it:
::* two Simulation macro icons [[File:Btn Simulation Macro.gif|35px]];
::* a decision icon with:
:::* a 'Yes' loop containing an output icon, followed by a delay icon and then a calculation icon;
:::* a 'No' loop containing an output icon, followed by a delay icon;
[[File:Exercise SimIcon Sim move.png|right|450px]]

* Configure the icons, by double clicking on each in turn, as follows:
::* the top Simulation macro:
:::* name it "Move the intruder";
:::* click on the 'Panel' tab, and then on the 'Position' folder;
:::* click on the 'MoveAlong' macro and:
::::* choose 'group2'(the intruder)as the Handle;
::::* choose 'shape1'( the brick wall) as the Axis;
::::* click on the down arrow on the end of the 'X' row, and create a floating point variable called "xpos", with an initial value 5.0, to use as the X variable;
::::* click on OK.

::* the second Simulation macro:
:::* name it "Check detection";
:::* click on the 'Panel' tab, and then on the 'Collision' folder;
[[File:Exercise SimIcon Sim test.png|right|300px]]
:::* click on the 'TestSingle' macro and:
::::* choose 'shape2'(the detection cone) for 'Pos' and 'shape5' (the intruder's head,) for 'Test';
:::* use the down arrow at the end of the 'Return Value' box to create a boolean variable caled "hit" to use as the 'Return Value'.
::::* click on OK.

::* the decision icon:
:::* name it "Intruder detected?";
:::* insert the condition "hit = 1";
:::* click on OK.

:::* In the 'Yes' loop:
::::* name the Output icon "Switch on lamp";
::::* send value '1' to Port A single bit 0;
::::* click on OK.

::::* name the Delay icon "Wait 100ms";
::::* configure it to give a delay of 100ms;
::::* click on OK.

::::* name the Calculation icon "Stop movement";
::::* in the 'Calculations:' box, insert "xpos = 0" to reduce the distance incremented each time to zero;
::::* click on OK.

:::* In the 'No' loop:
::::* name the Output icon "Switch off lamp";
::::* send value '0' to Port A single bit 0;
::::* click on OK.

::::* name the Delay icon "Wait 100ms";
::::* configure it to give a delay of 100ms;
::::* click on OK.

The Flowcode flowchart resembles the one shown below:

[[File:Exercise SimIcon Sim prog.png|center|350px]]

==Testing==

* Run the simulation.
: The intruder should move towards the house, until he enters the detection zone.

: At this point, the warning lamp turns on and he stops.

* Stop the simulation, and click on the image of the intruder. You can now read the x coordinate from the Panel properties box.

* Change the height of the PIR sensor on the wall, or the angle of the detection cone, and see what happens to this coordinate.

==Downloading the program==

* Click on the 'Compile to chip' icon, to download the program to the microcontroller.

* Run the program on the hardware. Nothing happens.
: The software is waiting for the value of the variable 'hit' to change to logic 1. However, there is no hardware attached to make this happen.
: There are two remedies:
::* Add a PIR sensor to the hardware, and connect it to Port A, bit 0.
::* Use a switch, connected to Port A, bit 0 to mimic the action of the PIR sensor.

: The important point is that the two Simulation macros did not compile to any code that was downloaded to the microcontroller. They affected only the simulation of the program.

Exercise - Using Simulation Macros

2013-08-26T15:23:07Z

JohnVerrill:

Simulation macros are a form of Component macros. Their purpose is to make simulation more realistic by adding physical components to the electronic devices.

When the Flowcode program is compiled and downloaded to a microcontroller, they are ignored - hence the name Simulation macros.

Even a cursory glance at the dialogue box used to configure them shows that they are very powerful devices, with a huge range of possible effects.

This exercise uses two of them to illustrate the use of a PIR (Passive Infra-Red sensor) to operate an intruder sensor.

__TOC__

==The scenario==

The scene depicts the front of a house.
[[File:Exercise SimIcon pan.png|center|350px]]

A PIR sensor is mounted on the wall of the house, above the path leading across the garden.

The data sheet for the PIR shows that it is sensitive to a range of 10 metres, within a cone of angle 100 degrees.

Its detection area is represented in the image by the pale blue cone.

When an intruder enters the detection cone, a warning lamp lights up in the house.

This exercise allows us to investigate factors such as the height of the sensor on the brick wall and the angle of the detection zone, so that these can be optimised for a typical intruder height.

==The System Panel==

On the System Panel, viewed from above (the default position,)create:
* '''a brick wall''', represented by adding a red cuboid and changing it to a rectangle, 15mm wide, 120mm high and 120mm deep,
:: located at coordinates x = 0, y = 0, z = 60,
:: with rotation settings X = 0, Y = 0, Z = 0;

* '''a path''', represented by a grey rectangle, 240mm wide, 100mm high and 0mm deep,
:: located at coordinatesx = 125mm, y = 0mm, z = 0mm,
:: with rotation settings of X = 0, Y = 0, Z = 0;

* '''a cone''', couloured light blue, representing the sensing region of the PIR, with width = 70mm, height = 250mm, depth 95mm,
:: located at coordinates x = 45mm, y = 0mm, z = 80mm,
:: with rotation settings of X = 0, Y = -55, Z = 0.

* Drag the mouse cursor over these three elements and group them together.

This produces 'group 1'.
:: Give this group:
::: dimensions - width = 265mm, height = 250mm, depth = 135mm;
::: coordinates - x = 128, y = 0, z = 68;
::: rotation - X = 0, Y = 0, Z = 0.

Also on the System Panel, create an intruder, by:
* adding four spheres, and configuruing the properties as follows:
:: sphere 1 ('''the head'''):
::: colour pink;
::: dimensions - width = 12mm, height = 13mm, depth = 15mm;
::: coordinates - x = -2.2, y = 0.7, z = 22;
::: rotation - X = 90, Y = 0, Z = 0.

:: sphere 2 ('''the body'''):
::: colour blue;
::: dimensions - width = 14mm, height = 26mm, depth = 24mm;
::: coordinates - x = -2.2, y = 0.5, z = 4;
::: rotation - X = 90, Y = 0, Z = -180.

:: sphere 3 ('''the legs'''):
::: colour dark green;
::: dimensions - width = 9mm, height = 23mm, depth = 15mm;
::: coordinates - x = -2.2, y = 1, z = -16;
::: rotation - X = 90, Y = 0, Z = -180.

:: sphere 4 ('''the feet'''):
::: colour black;
::: dimensions - width = 6mm, height = 15mm, depth = 25mm;
::: coordinates - x = -6, y = 0, z = -25;
::: rotation - X = 90, Y = 90, Z = 0.

* Drag the mouse cursor over the four spheres and group them together.

This produces 'group 2'.
:: Give it:
::: dimensions - width = 18mm, height = 32mm, depth = 60mm;
::: coordinates - x = 165, y = 0, z = 28;
::: rotation - X = 0, Y = 0, Z = 0.

The System Panel should resemble the image shown above. (The image has been rotated to show all components. The table-top is coloured green.)

Click on the 'Collisions' icon, [[File:Gen Panel Object Collision Move Around.png|35px]] and select the 'Move through' option, which allows the intruder to enter the detection cone.

==The Dashboard Panel==
[[File:Exercise SimIcon dash.png|right|200px]]
* Open the 'Outputs' toolbox, and locate the 'LED 5mm Panel' device.
* Click on the down arrow next to it and choose the 'Add to dashboard panel' option.
* Zoom in to the Dashboard Panel to make the LED large enough to see.
* Click on the LED and configure its properties as follows:
::* choose a suitable colour, such as red;
::* connect it to Port A, bit 0.

==The Flowcode program==

The plan is to move the intruder towards the detection cone using the 'MoveAlong' macro. This '''changes''' the x coordinate of the intruder '''by an amount specified by the variable 'xpos''''.

When the intruder enters the detection zone, the macro 'CollisionTest' returns a value of '1' in the variable 'hit'.

At that point, we want to stop any more movement so that we can look at the x coordinate of the intruder. To do this, we change the value of 'xpos' to zero.

* [[Opening Flowcode|Open Flowcode]].

* On the Startup screen, click on 'New project' to [[Creating Flowcharts|create a new flowchart]].

* Add the icons shown in the flowchart:
:* a loop icon, configured as an infinite loop, and within it:
::* two Simulation macro icons [[File:Btn Simulation Macro.gif|35px]];
[[File:Exercise SimIcon Sim move.png|right|450px]]
::* a decision icon with:
:::* a 'Yes' loop containing an output icon, followed by a delay icon and then a calculation icon;
:::* a 'No' loop containing an output icon, followed by a delay icon;

* Configure the icons, by double clicking on each in turn, as follows:
::* the top Simulation macro:
:::* name it "Move the intruder";
:::* click on the 'Panel' tab, and then on the 'Position' folder;
:::* click on the 'MoveAlong' macro and:
::::* choose 'group2'(the intruder)as the Handle;
::::* choose 'shape1'( the brick wall) as the Axis;
::::* click on the down arrow on the end of the 'X' row, and create a floating point variable called "xpos", with an initial value 5.0, to use as the X variable;
::::* click on OK.
[[File:Exercise SimIcon Sim test.png|right|300px]]

::* the second Simulation macro:
:::* name it "Check detection";
:::* click on the 'Panel' tab, and then on the 'Collision' folder;
:::* click on the 'TestSingle' macro and:
::::* choose 'shape2'(the detection cone) for 'Pos' and 'shape5' (the intruder's head,) for 'Test';
:::* use the down arrow at the end of the 'Return Value' box to create a boolean variable caled "hit" to use as the 'Return Value'.
::::* click on OK.

::* the decision icon:
:::* name it "Intruder detected?";
:::* insert the condition "hit = 1";
:::* click on OK.

::* In the 'Yes' loop:
:::* name the Output icon "Switch on lamp";
:::* send value '1' to Port A single bit 0;
:::* click on OK.

:::* name the Delay icon "Wait 100ms";
:::* configure it to give a delay of 100ms;
:::* click on OK.

:::* name the Calculation icon "Stop movement";
:::* in the 'Calculations:' box, insert "xpos = 0" to reduce the distance incremented each time to zero;
:::* click on OK.

::* In the 'No' loop:
:::* name the Output icon "Switch off lamp";
:::* send value '0' to Port A single bit 0;
:::* click on OK.

:::* name the Delay icon "Wait 100ms";
:::* configure it to give a delay of 100ms;
:::* click on OK.

[[File:Exercise SimIcon Sim prog.png|right|350px]]

* Flowcode

* Experienced

* Students

==Adding supplementary code==

This feature

'''Definitions and function declarations:'''

This is

'''Function implementations:'''

Exercise - Using Simulation Macros

2013-08-26T15:19:17Z

JohnVerrill:

Simulation macros are a form of Component macros. Their purpose is to make simulation more realistic by adding physical components to the electronic devices.

When the Flowcode program is compiled and downloaded to a microcontroller, they are ignored - hence the name Simulation macros.

Even a cursory glance at the dialogue box used to configure them shows that they are very powerful devices, with a huge range of possible effects.

This exercise uses two of them to illustrate the use of a PIR (Passive Infra-Red sensor) to operate an intruder sensor.

__TOC__

==The scenario==

The scene depicts the front of a house.
[[File:Exercise SimIcon pan.png|center|350px]]

A PIR sensor is mounted on the wall of the house, above the path leading across the garden.

The data sheet for the PIR shows that it is sensitive to a range of 10 metres, within a cone of angle 100 degrees.

Its detection area is represented in the image by the pale blue cone.

When an intruder enters the detection cone, a warning lamp lights up in the house.

This exercise allows us to investigate factors such as the height of the sensor on the brick wall and the angle of the detection zone, so that these can be optimised for a typical intruder height.

==The System Panel==

On the System Panel, viewed from above (the default position,)create:
* '''a brick wall''', represented by adding a red cuboid and changing it to a rectangle, 15mm wide, 120mm high and 120mm deep,
:: located at coordinates x = 0, y = 0, z = 60,
:: with rotation settings X = 0, Y = 0, Z = 0;

* '''a path''', represented by a grey rectangle, 240mm wide, 100mm high and 0mm deep,
:: located at coordinatesx = 125mm, y = 0mm, z = 0mm,
:: with rotation settings of X = 0, Y = 0, Z = 0;

* '''a cone''', couloured light blue, representing the sensing region of the PIR, with width = 70mm, height = 250mm, depth 95mm,
:: located at coordinates x = 45mm, y = 0mm, z = 80mm,
:: with rotation settings of X = 0, Y = -55, Z = 0.

* Drag the mouse cursor over these three elements and group them together.

This produces 'group 1'.
:: Give this group:
::: dimensions - width = 265mm, height = 250mm, depth = 135mm;
::: coordinates - x = 128, y = 0, z = 68;
::: rotation - X = 0, Y = 0, Z = 0.

Also on the System Panel, create an intruder, by:
* adding four spheres, and configuruing the properties as follows:
:: sphere 1 ('''the head'''):
::: colour pink;
::: dimensions - width = 12mm, height = 13mm, depth = 15mm;
::: coordinates - x = -2.2, y = 0.7, z = 22;
::: rotation - X = 90, Y = 0, Z = 0.

:: sphere 2 ('''the body'''):
::: colour blue;
::: dimensions - width = 14mm, height = 26mm, depth = 24mm;
::: coordinates - x = -2.2, y = 0.5, z = 4;
::: rotation - X = 90, Y = 0, Z = -180.

:: sphere 3 ('''the legs'''):
::: colour dark green;
::: dimensions - width = 9mm, height = 23mm, depth = 15mm;
::: coordinates - x = -2.2, y = 1, z = -16;
::: rotation - X = 90, Y = 0, Z = -180.

:: sphere 4 ('''the feet'''):
::: colour black;
::: dimensions - width = 6mm, height = 15mm, depth = 25mm;
::: coordinates - x = -6, y = 0, z = -25;
::: rotation - X = 90, Y = 90, Z = 0.

* Drag the mouse cursor over the four spheres and group them together.

This produces 'group 2'.
:: Give it:
::: dimensions - width = 18mm, height = 32mm, depth = 60mm;
::: coordinates - x = 165, y = 0, z = 28;
::: rotation - X = 0, Y = 0, Z = 0.

The System Panel should resemble the image shown above. (The image has been rotated to show all components. The table-top is coloured green.)

Click on the 'Collisions' icon, [[File:Gen Panel Object Collision Move Around.png|35px]] and select the 'Move through' option, which allows the intruder to enter the detection cone.

==The Dashboard Panel==
[[File:Exercise SimIcon dash.png|right|200px]]
* Open the 'Outputs' toolbox, and locate the 'LED 5mm Panel' device.
* Click on the down arrow next to it and choose the 'Add to dashboard panel' option.
* Zoom in to the Dashboard Panel to make the LED large enough to see.
* Click on the LED and configure its properties as follows:
::* choose a suitable colour, such as red;
::* connect it to Port A, bit 0.

==The Flowcode program==

The plan is to move the intruder towards the detection cone using the 'MoveAlong' macro. This '''changes''' the x coordinate of the intruder by an amount specified by the variable 'xpos'. When the intruder enters the detection zone, the macro 'CollisionTest' returns a value of '1' in the variable 'hit'. At that point, we want to stop any more movement so that we can look at the x coordinate of the intruder. To do this, we change the value of 'xpos' to zero.

* [[Opening Flowcode|Open Flowcode]].

* On the Startup screen, click on 'New project' to [[Creating Flowcharts|create a new flowchart]].

* Add the icons shown in the flowchart:
:* a loop icon, configured as an infinite loop, and within it:
::* two Simulation macro icons [[File:Btn Simulation Macro.gif|35px]];
[[File:Exercise SimIcon Sim move.png|right|450px]]
::* a decision icon with:
:::* a 'Yes' loop containing an output icon, followed by a delay icon and then a calculation icon;
:::* a 'No' loop containing an output icon, followed by a delay icon;

* Configure the icons, by double clicking on each in turn, as follows:
::* the top Simulation macro:
:::* name it "Move the intruder";
:::* click on the 'Panel' tab, and then on the 'Position' folder;
:::* click on the 'MoveAlong' macro and:
::::* choose 'group2'(the intruder)as the Handle;
::::* choose 'shape1'( the brick wall) as the Axis;
::::* click on the down arrow on the end of the 'X' row, and create a floating point variable called "xpos", with an initial value 5.0, to use as the X variable;
::::* click on OK.
[[File:Exercise SimIcon Sim test.png|right|300px]]

::* the second Simulation macro:
:::* name it "Check detection";
:::* click on the 'Panel' tab, and then on the 'Collision' folder;
:::* click on the 'TestSingle' macro and:
::::* choose 'shape2'(the detection cone) for 'Pos' and 'shape5' (the intruder's head,) for 'Test';
:::* use the down arrow at the end of the 'Return Value' box to create a boolean variable caled "hit" to use as the 'Return Value'.
::::* click on OK.

::* the decision icon:
:::* name it "Intruder detected?";
:::* insert the condition "hit = 1";
:::* click on OK.

::* In the 'Yes' loop:
:::* name the Output icon "Switch on lamp";
:::* send value '1' to Port A single bit 0;
:::* click on OK.

:::* name the Delay icon "Wait 100ms";
:::* configure it to give a delay of 100ms;
:::* click on OK.

:::* name the Calculation icon "Stop movement";
:::* in the 'Calculations:' box, insert "xpos = 0" to reduce the distance incremented each time to zero;
:::* click on OK.

::* In the 'No' loop:
:::* name the Output icon "Switch off lamp";
:::* send value '0' to Port A single bit 0;
:::* click on OK.

:::* name the Delay icon "Wait 100ms";
:::* configure it to give a delay of 100ms;
:::* click on OK.

[[File:Exercise SimIcon Sim prog.png|right|350px]]

* Flowcode

* Experienced

* Students

==Adding supplementary code==

This feature

'''Definitions and function declarations:'''

This is

'''Function implementations:'''

Exercise - Using Simulation Macros

2013-08-26T15:16:00Z

JohnVerrill:

Simulation macros are a form of Component macros. Their purpose is to make simulation more realistic by adding physical components to the electronic devices.

When the Flowcode program is compiled and downloaded to a microcontroller, they are ignored - hence the name Simulation macros.

Even a cursory glance at the dialogue box used to configure them shows that they are very powerful devices, with a huge range of possible effects.

This exercise uses two of them to illustrate the use of a PIR (Passive Infra-Red sensor) to operate an intruder sensor.

__TOC__

==The scenario==

The scene depicts the front of a house.
[[File:Exercise SimIcon pan.png|center|350px]]

A PIR sensor is mounted on the wall of the house, above the path leading across the garden.

The data sheet for the PIR shows that it is sensitive to a range of 10 metres, within a cone of angle 100 degrees.

Its detection area is represented in the image by the pale blue cone.

When an intruder enters the detection cone, a warning lamp lights up in the house.

==The System Panel==

On the System Panel, viewed from above (the default position,)create:
* '''a brick wall''', represented by adding a red cuboid and changing it to a rectangle, 15mm wide, 120mm high and 120mm deep,
:: located at coordinates x = 0, y = 0, z = 60,
:: with rotation settings X = 0, Y = 0, Z = 0;

* '''a path''', represented by a grey rectangle, 240mm wide, 100mm high and 0mm deep,
:: located at coordinatesx = 125mm, y = 0mm, z = 0mm,
:: with rotation settings of X = 0, Y = 0, Z = 0;

* '''a cone''', couloured light blue, representing the sensing region of the PIR, with width = 70mm, height = 250mm, depth 95mm,
:: located at coordinates x = 45mm, y = 0mm, z = 80mm,
:: with rotation settings of X = 0, Y = -55, Z = 0.

* Drag the mouse cursor over these three elements and group them together.

This produces 'group 1'.
:: Give this group:
::: dimensions - width = 265mm, height = 250mm, depth = 135mm;
::: coordinates - x = 128, y = 0, z = 68;
::: rotation - X = 0, Y = 0, Z = 0.

Also on the System Panel, create an intruder, by:
* adding four spheres, and configuruing the properties as follows:
:: sphere 1 ('''the head'''):
::: colour pink;
::: dimensions - width = 12mm, height = 13mm, depth = 15mm;
::: coordinates - x = -2.2, y = 0.7, z = 22;
::: rotation - X = 90, Y = 0, Z = 0.

:: sphere 2 ('''the body'''):
::: colour blue;
::: dimensions - width = 14mm, height = 26mm, depth = 24mm;
::: coordinates - x = -2.2, y = 0.5, z = 4;
::: rotation - X = 90, Y = 0, Z = -180.

:: sphere 3 ('''the legs'''):
::: colour dark green;
::: dimensions - width = 9mm, height = 23mm, depth = 15mm;
::: coordinates - x = -2.2, y = 1, z = -16;
::: rotation - X = 90, Y = 0, Z = -180.

:: sphere 4 ('''the feet'''):
::: colour black;
::: dimensions - width = 6mm, height = 15mm, depth = 25mm;
::: coordinates - x = -6, y = 0, z = -25;
::: rotation - X = 90, Y = 90, Z = 0.

* Drag the mouse cursor over the four spheres and group them together.

This produces 'group 2'.
:: Give it:
::: dimensions - width = 18mm, height = 32mm, depth = 60mm;
::: coordinates - x = 165, y = 0, z = 28;
::: rotation - X = 0, Y = 0, Z = 0.

The System Panel should resemble the image shown above. (The image has been rotated to show all components. The table-top is coloured green.)

Click on the 'Collisions' icon, [[File:Gen Panel Object Collision Move Around.png|35px]] and select the 'Move through' option, which allows the intruder to enter the detection cone.

==The Dashboard Panel==
[[File:Exercise SimIcon dash.png|right|200px]]
* Open the 'Outputs' toolbox, and locate the 'LED 5mm Panel' device.
* Click on the down arrow next to it and choose the 'Add to dashboard panel' option.
* Zoom in to the Dashboard Panel to make the LED large enough to see.
* Click on the LED and configure its properties as follows:
::* choose a suitable colour, such as red;
::* connect it to Port A, bit 0.

==The Flowcode program==

The plan is to move the intruder towards the detection cone using the 'MoveAlong' macro. This '''changes''' the x coordinate of the intruder by an amount specified by the variable 'xpos'. When the intruder enters the detection zone, the macro 'CollisionTest' returns a value of '1' in the variable 'hit'. At that point, we want to stop any more movement so that we can look at the x coordinate of the intruder.

* [[Opening Flowcode|Open Flowcode]].

* On the Startup screen, click on 'New project' to [[Creating Flowcharts|create a new flowchart]].

* Add the icons shown in the flowchart:
:* a loop icon, configured as an infinite loop, and within it:
::* two Simulation macro icons [[File:Btn Simulation Macro.gif|35px]];
[[File:Exercise SimIcon Sim move.png|right|450px]]
::* a decision icon with:
:::* a 'Yes' loop containing an output icon, followed by a delay icon and then a calculation icon;
:::* a 'No' loop containing an output icon, followed by a delay icon;

* Configure the icons, by double clicking on each in turn, as follows:
::* the top Simulation macro:
:::* name it "Move the intruder";
:::* click on the 'Panel' tab, and then on the 'Position' folder;
:::* click on the 'MoveAlong' macro and:
::::* choose 'group2'(the intruder)as the Handle;
::::* choose 'shape1'( the brick wall) as the Axis;
::::* click on the down arrow on the end of the 'X' row, and create a floating point variable called "xpos", with an initial value 5.0, to use as the X variable;
::::* click on OK.
[[File:Exercise SimIcon Sim test.png|right|300px]]

::* the second Simulation macro:
:::* name it "Check detection";
:::* click on the 'Panel' tab, and then on the 'Collision' folder;
:::* click on the 'TestSingle' macro and:
::::* choose 'shape2'(the detection cone) for 'Pos' and 'shape5' (the intruder's head,) for 'Test';
:::* use the down arrow at the end of the 'Return Value' box to create a boolean variable caled "hit" to use as the 'Return Value'.
::::* click on OK.

::* the decision icon:
:::* name it "Intruder detected?";
:::* insert the condition "hit = 1";
:::* click on OK.

::* In the 'Yes' loop:
:::* name the Output icon "Switch on lamp";
:::* send value '1' to Port A single bit 0;
:::* click on OK.

:::* name the Delay icon "Wait 100ms";
:::* configure it to give a delay of 100ms;
:::* click on OK.

:::* name the Calculation icon "Stop movement";
:::* in the 'Calculations:' box, insert "xpos = 0" to reduce the distance incremented each time to zero;
:::* click on OK.

::* In the 'No' loop:
:::* name the Output icon "Switch off lamp";
:::* send value '0' to Port A single bit 0;
:::* click on OK.

:::* name the Delay icon "Wait 100ms";
:::* configure it to give a delay of 100ms;
:::* click on OK.

[[File:Exercise SimIcon Sim prog.png|right|350px]]

* Flowcode

* Experienced

* Students

==Adding supplementary code==

This feature

'''Definitions and function declarations:'''

This is

'''Function implementations:'''

Exercise - Using Simulation Macros

2013-08-26T15:11:33Z

JohnVerrill:

Simulation macros are a form of Component macros. Their purpose is to make simulation more realistic by adding physical components to the electronic devices.

When the Flowcode program is compiled and downloaded to a microcontroller, they are ignored - hence the name Simulation macros.

Even a cursory glance at the dialogue box used to configure them shows that they are very powerful devices, with a huge range of possible effects.

This exercise uses two of them to illustrate the use of a PIR (Passive Infra-Red sensor) to operate an intruder sensor.

__TOC__

==The scenario==

The scene depicts the front of a house.
[[File:Exercise SimIcon pan.png|center|350px]]

A PIR sensor is mounted on the wall of the house, above the path leading across the garden.

The data sheet for the PIR shows that it is sensitive to a range of 10 metres, within a cone of angle 100 degrees.

Its detection area is represented in the image by the pale blue cone.

When an intruder enters the detection cone, a warning lamp lights up in the house.

==The System Panel==

On the System Panel, viewed from above (the default position,)create:
* '''a brick wall''', represented by adding a red cuboid and changing it to a rectangle, 15mm wide, 120mm high and 120mm deep,
:: located at coordinates x = 0, y = 0, z = 60,
:: with rotation settings X = 0, Y = 0, Z = 0;

* '''a path''', represented by a grey rectangle, 240mm wide, 100mm high and 0mm deep,
:: located at coordinatesx = 125mm, y = 0mm, z = 0mm,
:: with rotation settings of X = 0, Y = 0, Z = 0;

* '''a cone''', couloured light blue, representing the sensing region of the PIR, with width = 70mm, height = 250mm, depth 95mm,
:: located at coordinates x = 45mm, y = 0mm, z = 80mm,
:: with rotation settings of X = 0, Y = -55, Z = 0.

* Drag the mouse cursor over these three elements and group them together.

This produces 'group 1'.
:: Give this group:
::: dimensions - width = 265mm, height = 250mm, depth = 135mm;
::: coordinates - x = 128, y = 0, z = 68;
::: rotation - X = 0, Y = 0, Z = 0.

Also on the System Panel, create an intruder, by:
* adding four spheres, and configuruing the properties as follows:
:: sphere 1 ('''the head'''):
::: colour pink;
::: dimensions - width = 12mm, height = 13mm, depth = 15mm;
::: coordinates - x = -2.2, y = 0.7, z = 22;
::: rotation - X = 90, Y = 0, Z = 0.

:: sphere 2 ('''the body'''):
::: colour blue;
::: dimensions - width = 14mm, height = 26mm, depth = 24mm;
::: coordinates - x = -2.2, y = 0.5, z = 4;
::: rotation - X = 90, Y = 0, Z = -180.

:: sphere 3 ('''the legs'''):
::: colour dark green;
::: dimensions - width = 9mm, height = 23mm, depth = 15mm;
::: coordinates - x = -2.2, y = 1, z = -16;
::: rotation - X = 90, Y = 0, Z = -180.

:: sphere 4 ('''the feet'''):
::: colour black;
::: dimensions - width = 6mm, height = 15mm, depth = 25mm;
::: coordinates - x = -6, y = 0, z = -25;
::: rotation - X = 90, Y = 90, Z = 0.

* Drag the mouse cursor over the four spheres and group them together.

This produces 'group 2'.
:: Give it:
::: dimensions - width = 18mm, height = 32mm, depth = 60mm;
::: coordinates - x = 165, y = 0, z = 28;
::: rotation - X = 0, Y = 0, Z = 0.

The System Panel should resemble the image shown above. (The image has been rotated to show all components. The table-top is coloured green.)

Click on the 'Collisions' icon, [[File:Gen Panel Object Collision Move Around.png|35px]] and select the 'Move through' option, which allows the intruder to enter the detection cone.

==The Dashboard Panel==
[[File:Exercise SimIcon dash.png|right|200px]]
* Open the 'Outputs' toolbox, and locate the 'LED 5mm Panel' device.
* Click on the down arrow next to it and choose the 'Add to dashboard panel' option.
* Zoom in to the Dashboard Panel to make the LED large enough to see.
* Click on the LED and configure its properties as follows:
::* choose a suitable colour, such as red;
::* connect it to Port A, bit 0.

==The Flowcode program==

* [[Opening Flowcode|Open Flowcode]].

* On the Startup screen, click on 'New project' to [[Creating Flowcharts|create a new flowchart]].

* Add the icons shown in the flowchart:
:* a loop icon, configured as an infinite loop, and within it:
::* two Simulation macro icons [[File:Btn Simulation Macro.gif|35px]];
[[File:Exercise SimIcon Sim move.png|right|450px]]
::* a decision icon with:
:::* a 'Yes' loop containing an output icon, followed by a delay icon and then a calculation icon;
:::* a 'No' loop containing an output icon, followed by a delay icon;

* Configure the icons, by double clicking on each in turn, as follows:
::* the top Simulation macro:
:::* name it "Move the intruder";
:::* click on the 'Panel' tab, and then on the 'Position' folder;
:::* click on the 'MoveAlong' macro and:
::::* choose 'group2'(the intruder)as the Handle;
::::* choose 'shape1'( the brick wall) as the Axis;
::::* click on the down arrow on the end of the 'X' row, and create a floating point variable called "xpos", with an initial value 5.0, to use as the X variable;
::::* click on OK.
[[File:Exercise SimIcon Sim test.png|right|300px]]

::* the second Simulation macro:
:::* name it "Check detection";
:::* click on the 'Panel' tab, and then on the 'Collision' folder;
:::* click on the 'TestSingle' macro and:
::::* choose 'shape2'(the detection cone) for 'Pos' and 'shape5' (the intruder's head,) for 'Test';
:::* use the down arrow at the end of the 'Return Value' box to create a boolean variable caled "hit" to use as the 'Return Value'.
::::* click on OK.

::* the decision icon:
:::* name it "Intruder detected?";
:::* insert the condition "hit = 1";
:::* click on OK.

::* In the 'Yes' loop:
:::* name the Output icon "Switch on lamp";
:::* send value '1' to Port A single bit 0;
:::* click on OK.

:::* name the Delay icon "Wait 100ms";
:::* configure it to give a delay of 100ms;
:::* click on OK.

:::* name the Calculation icon "Stop movement";
:::* in the 'Calculations:' box, insert "xpos = 0" to reduce the distance incremented each time to zero;
:::* click on OK.

::* In the 'No' loop:
:::* name the Output icon "Switch off lamp";
:::* send value '0' to Port A single bit 0;
:::* click on OK.

:::* name the Delay icon "Wait 100ms";
:::* configure it to give a delay of 100ms;
:::* click on OK.

[[File:Exercise SimIcon Sim prog.png|right|350px]]

* Flowcode

* Experienced

* Students

==Adding supplementary code==

This feature

'''Definitions and function declarations:'''

This is

'''Function implementations:'''

Exercise - Using Simulation Macros

2013-08-26T15:03:53Z

JohnVerrill:

Simulation macros are a form of Component macros. Their purpose is to make simulation more realistic by adding physical components to the electronic devices.

When the Flowcode program is compiled and downloaded to a microcontroller, they are ignored - hence the name Simulation macros.

Even a cursory glance at the dialogue box used to configure them shows that they are very powerful devices, with a huge range of possible effects.

This exercise uses two of them to illustrate the use of a PIR (Passive Infra-Red sensor) to operate an intruder sensor.

__TOC__

==The scenario==

The scene depicts the front of a house.
[[File:Exercise SimIcon pan.png|center|350px]]

A PIR sensor is mounted on the wall of the house, above the path leading across the garden.

The data sheet for the PIR shows that it is sensitive to a range of 10 metres, within a cone of angle 100 degrees.

Its detection area is represented in the image by the pale blue cone.

When an intruder enters the detection cone, a warning lamp lights up in the house.

==The System Panel==

On the System Panel, viewed from above (the default position,)create:
* '''a brick wall''', represented by adding a red cuboid and changing it to a rectangle, 15mm wide, 120mm high and 120mm deep,
:: located at coordinates x = 0, y = 0, z = 60,
:: with rotation settings X = 0, Y = 0, Z = 0;

* '''a path''', represented by a grey rectangle, 240mm wide, 100mm high and 0mm deep,
:: located at coordinatesx = 125mm, y = 0mm, z = 0mm,
:: with rotation settings of X = 0, Y = 0, Z = 0;

* '''a cone''', couloured light blue, representing the sensing region of the PIR, with width = 70mm, height = 250mm, depth 95mm,
:: located at coordinates x = 45mm, y = 0mm, z = 80mm,
:: with rotation settings of X = 0, Y = -55, Z = 0.

* Drag the mouse cursor over these three elements and group them together.

This produces 'group 1'.
:: Give this group:
::: dimensions - width = 265mm, height = 250mm, depth = 135mm;
::: coordinates - x = 128, y = 0, z = 68;
::: rotation - X = 0, Y = 0, Z = 0.

Also on the System Panel, create an intruder, by:
* adding four spheres, and configuruing the properties as follows:
:: sphere 1 ('''the head'''):
::: colour pink;
::: dimensions - width = 12mm, height = 13mm, depth = 15mm;
::: coordinates - x = -2.2, y = 0.7, z = 22;
::: rotation - X = 90, Y = 0, Z = 0.

:: sphere 2 ('''the body'''):
::: colour blue;
::: dimensions - width = 14mm, height = 26mm, depth = 24mm;
::: coordinates - x = -2.2, y = 0.5, z = 4;
::: rotation - X = 90, Y = 0, Z = -180.

:: sphere 3 ('''the legs'''):
::: colour dark green;
::: dimensions - width = 9mm, height = 23mm, depth = 15mm;
::: coordinates - x = -2.2, y = 1, z = -16;
::: rotation - X = 90, Y = 0, Z = -180.

:: sphere 4 ('''the feet'''):
::: colour black;
::: dimensions - width = 6mm, height = 15mm, depth = 25mm;
::: coordinates - x = -6, y = 0, z = -25;
::: rotation - X = 90, Y = 90, Z = 0.

* Drag the mouse cursor over the four spheres and group them together.

This produces 'group 2'.
:: Give it:
::: dimensions - width = 18mm, height = 32mm, depth = 60mm;
::: coordinates - x = 165, y = 0, z = 28;
::: rotation - X = 0, Y = 0, Z = 0.

The System Panel should resemble the image shown above. (The image has been rotated to show all components. The table-top is coloured green.)

Click on the 'Collisions' icon, [[File:Gen Panel Object Collision Move Around.png|35px]] and select the 'Move through' option, which allows the intruder to enter the detection cone.

==The Dashboard Panel==
[[File:Exercise SimIcon dash.png|right|200px]]
* Open the 'Outputs' toolbox, and locate the 'LED 5mm Panel' device.
* Click on the down arrow next to it and choose the 'Add to dashboard panel' option.
* Zoom in to the Dashboard Panel to make the LED large enough to see.
* Click on the LED and configure its properties as follows:
::* choose a suitable colour, such as red;
::* connect it to Port A, bit 0.

==The Flowcode program==

* [[Opening Flowcode|Open Flowcode]].

* On the Startup screen, click on 'New project' to [[Creating Flowcharts|create a new flowchart]].

* Add the icons shown in the flowchart:
:* a loop icon, configured as an infinite loop, and within it:
::* two Simulation macro icons [[File:Btn Simulation Macro.gif|35px]];
[[File:Exercise SimIcon Sim move.png|right|450px]]
::* a decision icon with:
:::* a 'Yes' loop containing an output icon, followed by a delay icon and then a calculation icon;
:::* a 'No' loop containing an output icon, followed by a delay icon;

* Configure the icons, by double clicking on each in turn, as follows:
::* the top Simulation macro:
:::* name it "Move the intruder";
:::* click on the 'Panel' tab, and then on the 'Position' folder;
:::* click on the 'MoveAlong' macro and:
::::* choose 'group2'(the intruder)as the Handle;
::::* choose 'shape1'( the brick wall) as the Axis;
::::* click on the down arrow on the end of the 'X' row, and create a floating point variable called "xpos", with an initial value 5.0, to use as the X variable;
::::* click on OK.

[[File:Exercise SimIcon Sim test.png|right|300px]]

::* the second Simulation macro:
:::* name it "Check detection";
:::* click on the 'Panel' tab, and then on the 'Collision' folder;
:::* click on the 'TestSingle' macro and:
::::* choose 'shape2'(the detection cone) for 'Pos' and 'shape5' (the intruder's head,) for 'Test';
:::* use the down arrow at the end of the 'Return Value' box to create a boolean variable caled "hit" to use as the 'Return Value'.
::::* click on OK.

::* the decision icon:
:::* name it "Intruder detected?";
:::* insert the condition "hit = 1";
:::* click on OK.

[[File:Exercise SimIcon Sim prog.png|right|350px]]

* Flowcode

* Experienced

* Students

==Adding supplementary code==

This feature

'''Definitions and function declarations:'''

This is

'''Function implementations:'''

Exercise - Using Simulation Macros

2013-08-26T14:59:46Z

JohnVerrill:

Simulation macros are a form of Component macros. Their purpose is to make simulation more realistic by adding physical components to the electronic devices.

When the Flowcode program is compiled and downloaded to a microcontroller, they are ignored - hence the name Simulation macros.

Even a cursory glance at the dialogue box used to configure them shows that they are very powerful devices, with a huge range of possible effects.

This exercise uses two of them to illustrate the use of a PIR (Passive Infra-Red sensor) to operate an intruder sensor.

__TOC__

==The scenario==

The scene depicts the front of a house.
[[File:Exercise SimIcon pan.png|center|350px]]

A PIR sensor is mounted on the wall of the house, above the path leading across the garden.

The data sheet for the PIR shows that it is sensitive to a range of 10 metres, within a cone of angle 100 degrees.

Its detection area is represented in the image by the pale blue cone.

When an intruder enters the detection cone, a warning lamp lights up in the house.

==The System Panel==

On the System Panel, viewed from above (the default position,)create:
* '''a brick wall''', represented by adding a red cuboid and changing it to a rectangle, 15mm wide, 120mm high and 120mm deep,
:: located at coordinates x = 0, y = 0, z = 60,
:: with rotation settings X = 0, Y = 0, Z = 0;

* '''a path''', represented by a grey rectangle, 240mm wide, 100mm high and 0mm deep,
:: located at coordinatesx = 125mm, y = 0mm, z = 0mm,
:: with rotation settings of X = 0, Y = 0, Z = 0;

* '''a cone''', couloured light blue, representing the sensing region of the PIR, with width = 70mm, height = 250mm, depth 95mm,
:: located at coordinates x = 45mm, y = 0mm, z = 80mm,
:: with rotation settings of X = 0, Y = -55, Z = 0.

* Drag the mouse cursor over these three elements and group them together.

This produces 'group 1'.
:: Give this group:
::: dimensions - width = 265mm, height = 250mm, depth = 135mm;
::: coordinates - x = 128, y = 0, z = 68;
::: rotation - X = 0, Y = 0, Z = 0.

Also on the System Panel, create an intruder, by:
* adding four spheres, and configuruing the properties as follows:
:: sphere 1 ('''the head'''):
::: colour pink;
::: dimensions - width = 12mm, height = 13mm, depth = 15mm;
::: coordinates - x = -2.2, y = 0.7, z = 22;
::: rotation - X = 90, Y = 0, Z = 0.

:: sphere 2 ('''the body'''):
::: colour blue;
::: dimensions - width = 14mm, height = 26mm, depth = 24mm;
::: coordinates - x = -2.2, y = 0.5, z = 4;
::: rotation - X = 90, Y = 0, Z = -180.

:: sphere 3 ('''the legs'''):
::: colour dark green;
::: dimensions - width = 9mm, height = 23mm, depth = 15mm;
::: coordinates - x = -2.2, y = 1, z = -16;
::: rotation - X = 90, Y = 0, Z = -180.

:: sphere 4 ('''the feet'''):
::: colour black;
::: dimensions - width = 6mm, height = 15mm, depth = 25mm;
::: coordinates - x = -6, y = 0, z = -25;
::: rotation - X = 90, Y = 90, Z = 0.

* Drag the mouse cursor over the four spheres and group them together.

This produces 'group 2'.
:: Give it:
::: dimensions - width = 18mm, height = 32mm, depth = 60mm;
::: coordinates - x = 165, y = 0, z = 28;
::: rotation - X = 0, Y = 0, Z = 0.

The System Panel should resemble the image shown above. (The image has been rotated to show all components. The table-top is coloured green.)

Click on the 'Collisions' icon, [[File:Gen Panel Object Collision Move Around.png|35px]] and select the 'Move through' option, which allows the intruder to enter the detection cone.

==The Dashboard Panel==
[[File:Exercise SimIcon dash.png|right|200px]]
* Open the 'Outputs' toolbox, and locate the 'LED 5mm Panel' device.
* Click on the down arrow next to it and choose the 'Add to dashboard panel' option.
* Zoom in to the Dashboard Panel to make the LED large enough to see.
* Click on the LED and configure its properties as follows:
::* choose a suitable colour, such as red;
::* connect it to Port A, bit 0.

==The Flowcode program==

* [[Opening Flowcode|Open Flowcode]].

* On the Startup screen, click on 'New project' to [[Creating Flowcharts|create a new flowchart]].

* Add the icons shown in the flowchart:
:* a loop icon, configured as an infinite loop, and within it:
::* two Simulation macro icons [[File:Btn Simulation Macro.gif|35px]];
[[File:Exercise SimIcon Sim move.png|right|450px]]
::* a decision icon with:
:::* a 'Yes' loop containing an output icon, followed by a delay icon and then a calculation icon;
:::* a 'No' loop containing an output icon, followed by a delay icon and then a calculation icon;

* Configure the icons, by double clicking on each in turn, as follows:
::* the top Simulation macro:
:::* click on the 'Panel' tab, and then on the 'Position' folder;
:::* click on the 'MoveAlong' macro and:
::::* choose 'group2'(the intruder)as the Handle;
::::* choose 'shape1'( the brick wall) as the Axis;
::::* click on the down arrow on the end of the 'X' row, and create a floating point variable called "xpos", with an initial value 5.0, to use as the X variable;
::::* click on OK.

[[File:Exercise SimIcon Sim test.png|right|300px]]

::* the second Simulation macro:
:::* click on the 'Panel' tab, and then on the 'Collision' folder;
:::* click on the 'TestSingle' macro and:
::::* choose 'shape2'(the detection cone) for 'Pos' and 'shape5' (the intruder's head,) for 'Test';
:::* use the down arrow at the end of the 'Return Value' box to create a boolean variable caled "hit" to use as the 'Return Value'.
::::* click on OK.

::* the decision icon:

[[File:Exercise SimIcon Sim prog.png|right|350px]]

* Flowcode

* Experienced

* Students

==Adding supplementary code==

This feature

'''Definitions and function declarations:'''

This is

'''Function implementations:'''

Exercise - Using Simulation Macros

2013-08-26T14:58:54Z

JohnVerrill:

Simulation macros are a form of Component macros. Their purpose is to make simulation more realistic by adding physical components to the electronic devices.

When the Flowcode program is compiled and downloaded to a microcontroller, they are ignored - hence the name Simulation macros.

Even a cursory glance at the dialogue box used to configure them shows that they are very powerful devices, with a huge range of possible effects.

This exercise uses two of them to illustrate the use of a PIR (Passive Infra-Red sensor) to operate an intruder sensor.

__TOC__

==The scenario==

The scene depicts the front of a house.
[[File:Exercise SimIcon pan.png|center|350px]]

A PIR sensor is mounted on the wall of the house, above the path leading across the garden.

The data sheet for the PIR shows that it is sensitive to a range of 10 metres, within a cone of angle 100 degrees.

Its detection area is represented in the image by the pale blue cone.

When an intruder enters the detection cone, a warning lamp lights up in the house.

==The System Panel==

On the System Panel, viewed from above (the default position,)create:
* '''a brick wall''', represented by adding a red cuboid and changing it to a rectangle, 15mm wide, 120mm high and 120mm deep,
:: located at coordinates x = 0, y = 0, z = 60,
:: with rotation settings X = 0, Y = 0, Z = 0;

* '''a path''', represented by a grey rectangle, 240mm wide, 100mm high and 0mm deep,
:: located at coordinatesx = 125mm, y = 0mm, z = 0mm,
:: with rotation settings of X = 0, Y = 0, Z = 0;

* '''a cone''', couloured light blue, representing the sensing region of the PIR, with width = 70mm, height = 250mm, depth 95mm,
:: located at coordinates x = 45mm, y = 0mm, z = 80mm,
:: with rotation settings of X = 0, Y = -55, Z = 0.

* Drag the mouse cursor over these three elements and group them together.

This produces 'group 1'.
:: Give this group:
::: dimensions - width = 265mm, height = 250mm, depth = 135mm;
::: coordinates - x = 128, y = 0, z = 68;
::: rotation - X = 0, Y = 0, Z = 0.

Also on the System Panel, create an intruder, by:
* adding four spheres, and configuruing the properties as follows:
:: sphere 1 ('''the head'''):
::: colour pink;
::: dimensions - width = 12mm, height = 13mm, depth = 15mm;
::: coordinates - x = -2.2, y = 0.7, z = 22;
::: rotation - X = 90, Y = 0, Z = 0.

:: sphere 2 ('''the body'''):
::: colour blue;
::: dimensions - width = 14mm, height = 26mm, depth = 24mm;
::: coordinates - x = -2.2, y = 0.5, z = 4;
::: rotation - X = 90, Y = 0, Z = -180.

:: sphere 3 ('''the legs'''):
::: colour dark green;
::: dimensions - width = 9mm, height = 23mm, depth = 15mm;
::: coordinates - x = -2.2, y = 1, z = -16;
::: rotation - X = 90, Y = 0, Z = -180.

:: sphere 4 ('''the feet'''):
::: colour black;
::: dimensions - width = 6mm, height = 15mm, depth = 25mm;
::: coordinates - x = -6, y = 0, z = -25;
::: rotation - X = 90, Y = 90, Z = 0.

* Drag the mouse cursor over the four spheres and group them together.

This produces 'group 2'.
:: Give it:
::: dimensions - width = 18mm, height = 32mm, depth = 60mm;
::: coordinates - x = 165, y = 0, z = 28;
::: rotation - X = 0, Y = 0, Z = 0.

The System Panel should resemble the image shown above. (The image has been rotated to show all components. The table-top is coloured green.)

Click on the 'Collisions' icon, [[File:Gen Panel Object Collision Move Around.png|35px]] and select the 'Move through' option, which allows the intruder to enter the detection cone.

==The Dashboard Panel==
[[File:Exercise SimIcon dash.png|right|200px]]
* Open the 'Outputs' toolbox, and locate the 'LED 5mm Panel' device.
* Click on the down arrow next to it and choose the 'Add to dashboard panel' option.
* Zoom in to the Dashboard Panel to make the LED large enough to see.
* Click on the LED and configure its properties as follows:
::* choose a suitable colour, such as yellow;
::* connect it to Port A, bit 0.

==The Flowcode program==

* [[Opening Flowcode|Open Flowcode]].

* On the Startup screen, click on 'New project' to [[Creating Flowcharts|create a new flowchart]].

* Add the icons shown in the flowchart:
:* a loop icon, configured as an infinite loop, and within it:
::* two Simulation macro icons [[File:Btn Simulation Macro.gif|35px]];
[[File:Exercise SimIcon Sim move.png|right|450px]]
::* a decision icon with:
:::* a 'Yes' loop containing an output icon, followed by a delay icon and then a calculation icon;
:::* a 'No' loop containing an output icon, followed by a delay icon and then a calculation icon;

* Configure the icons, by double clicking on each in turn, as follows:
::* the top Simulation macro:
:::* click on the 'Panel' tab, and then on the 'Position' folder;
:::* click on the 'MoveAlong' macro and:
::::* choose 'group2'(the intruder)as the Handle;
::::* choose 'shape1'( the brick wall) as the Axis;
::::* click on the down arrow on the end of the 'X' row, and create a floating point variable called "xpos", with an initial value 5.0, to use as the X variable;
::::* click on OK.

[[File:Exercise SimIcon Sim test.png|right|300px]]

::* the second Simulation macro:
:::* click on the 'Panel' tab, and then on the 'Collision' folder;
:::* click on the 'TestSingle' macro and:
::::* choose 'shape2'(the detection cone) for 'Pos' and 'shape5' (the intruder's head,) for 'Test';
:::* use the down arrow at the end of the 'Return Value' box to create a boolean variable caled "hit" to use as the 'Return Value'.
::::* click on OK.

::* the decision icon:

[[File:Exercise SimIcon Sim prog.png|right|350px]]

* Flowcode

* Experienced

* Students

==Adding supplementary code==

This feature

'''Definitions and function declarations:'''

This is

'''Function implementations:'''

Exercise - Using Simulation Macros

2013-08-26T14:55:07Z

JohnVerrill:

Exercise - Using Simulation Macros

2013-08-26T14:53:09Z

JohnVerrill:

Exercise - Using Simulation Macros

2013-08-25T14:32:41Z

JohnVerrill: