<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>https://www.flowcode.co.uk/wiki/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=ReeceL</id>
	<title>Flowcode Help - User contributions [en]</title>
	<link rel="self" type="application/atom+xml" href="https://www.flowcode.co.uk/wiki/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=ReeceL"/>
	<link rel="alternate" type="text/html" href="https://www.flowcode.co.uk/wiki/index.php?title=Special:Contributions/ReeceL"/>
	<updated>2026-04-03T22:32:56Z</updated>
	<subtitle>User contributions</subtitle>
	<generator>MediaWiki 1.34.1</generator>
	<entry>
		<id>https://www.flowcode.co.uk/wiki/index.php?title=File:Gen_Properties_Tabs.png&amp;diff=14497</id>
		<title>File:Gen Properties Tabs.png</title>
		<link rel="alternate" type="text/html" href="https://www.flowcode.co.uk/wiki/index.php?title=File:Gen_Properties_Tabs.png&amp;diff=14497"/>
		<updated>2014-02-03T15:45:40Z</updated>

		<summary type="html">&lt;p&gt;ReeceL: Properties Panel - Property and Position tabs&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Properties Panel - Property and Position tabs&lt;/div&gt;</summary>
		<author><name>ReeceL</name></author>
		
	</entry>
	<entry>
		<id>https://www.flowcode.co.uk/wiki/index.php?title=File:Gen_Global_Options_Application.png&amp;diff=14493</id>
		<title>File:Gen Global Options Application.png</title>
		<link rel="alternate" type="text/html" href="https://www.flowcode.co.uk/wiki/index.php?title=File:Gen_Global_Options_Application.png&amp;diff=14493"/>
		<updated>2014-02-03T15:08:52Z</updated>

		<summary type="html">&lt;p&gt;ReeceL: ReeceL uploaded a new version of &amp;amp;quot;File:Gen Global Options Application.png&amp;amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Global Options - Default Application Tab&lt;/div&gt;</summary>
		<author><name>ReeceL</name></author>
		
	</entry>
	<entry>
		<id>https://www.flowcode.co.uk/wiki/index.php?title=File:Gen_Global_Options_Application.png&amp;diff=14492</id>
		<title>File:Gen Global Options Application.png</title>
		<link rel="alternate" type="text/html" href="https://www.flowcode.co.uk/wiki/index.php?title=File:Gen_Global_Options_Application.png&amp;diff=14492"/>
		<updated>2014-02-03T15:08:51Z</updated>

		<summary type="html">&lt;p&gt;ReeceL: ReeceL uploaded a new version of &amp;amp;quot;File:Gen Global Options Application.png&amp;amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Global Options - Default Application Tab&lt;/div&gt;</summary>
		<author><name>ReeceL</name></author>
		
	</entry>
	<entry>
		<id>https://www.flowcode.co.uk/wiki/index.php?title=File:Gen_Global_Options_Editor.png&amp;diff=14487</id>
		<title>File:Gen Global Options Editor.png</title>
		<link rel="alternate" type="text/html" href="https://www.flowcode.co.uk/wiki/index.php?title=File:Gen_Global_Options_Editor.png&amp;diff=14487"/>
		<updated>2014-02-03T14:35:08Z</updated>

		<summary type="html">&lt;p&gt;ReeceL: Global Options - Editor tab&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Global Options - Editor tab&lt;/div&gt;</summary>
		<author><name>ReeceL</name></author>
		
	</entry>
	<entry>
		<id>https://www.flowcode.co.uk/wiki/index.php?title=File:Gen_Global_Options_Locations.png&amp;diff=14486</id>
		<title>File:Gen Global Options Locations.png</title>
		<link rel="alternate" type="text/html" href="https://www.flowcode.co.uk/wiki/index.php?title=File:Gen_Global_Options_Locations.png&amp;diff=14486"/>
		<updated>2014-02-03T14:34:44Z</updated>

		<summary type="html">&lt;p&gt;ReeceL: ReeceL uploaded a new version of &amp;amp;quot;File:Gen Global Options Locations.png&amp;amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Global Options - Locations Tab&lt;/div&gt;</summary>
		<author><name>ReeceL</name></author>
		
	</entry>
	<entry>
		<id>https://www.flowcode.co.uk/wiki/index.php?title=File:Gen_Global_Options_Application.png&amp;diff=14485</id>
		<title>File:Gen Global Options Application.png</title>
		<link rel="alternate" type="text/html" href="https://www.flowcode.co.uk/wiki/index.php?title=File:Gen_Global_Options_Application.png&amp;diff=14485"/>
		<updated>2014-02-03T14:34:20Z</updated>

		<summary type="html">&lt;p&gt;ReeceL: ReeceL uploaded a new version of &amp;amp;quot;File:Gen Global Options Application.png&amp;amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Global Options - Default Application Tab&lt;/div&gt;</summary>
		<author><name>ReeceL</name></author>
		
	</entry>
	<entry>
		<id>https://www.flowcode.co.uk/wiki/index.php?title=Main_Page&amp;diff=14404</id>
		<title>Main Page</title>
		<link rel="alternate" type="text/html" href="https://www.flowcode.co.uk/wiki/index.php?title=Main_Page&amp;diff=14404"/>
		<updated>2014-01-24T14:04:07Z</updated>

		<summary type="html">&lt;p&gt;ReeceL: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{| cellpadding=&amp;quot;4&amp;quot; style=&amp;quot;border: 1px solid darkgray; float:right; width:300px&amp;quot;&lt;br /&gt;
|+ '''Flowcode 6'''&lt;br /&gt;
|-&lt;br /&gt;
| colspan=&amp;quot;2&amp;quot;|[[File:FC6_Icon.png|center]]&lt;br /&gt;
|-&lt;br /&gt;
| colspan=&amp;quot;2&amp;quot;|[[File:FC6_Box_Cover.jpg|center]]&lt;br /&gt;
|-&lt;br /&gt;
|width=&amp;quot;40%&amp;quot;|'''Developer'''&lt;br /&gt;
|[http://matrixmultimedia.com Matrix Multimedia]&lt;br /&gt;
|-&lt;br /&gt;
|'''Initial release'''&lt;br /&gt;
|3rd September 2013&lt;br /&gt;
|-&lt;br /&gt;
|'''Development status'''&lt;br /&gt;
|Active&lt;br /&gt;
|-&lt;br /&gt;
|'''Written in'''&lt;br /&gt;
|C++&lt;br /&gt;
|-&lt;br /&gt;
|'''Operating system'''&lt;br /&gt;
|[http://en.wikipedia.org/wiki/Windows_XP Windows XP]&lt;br /&gt;
&lt;br /&gt;
[http://en.wikipedia.org/wiki/Windows_Vista Windows Vista]&lt;br /&gt;
&lt;br /&gt;
[http://en.wikipedia.org/wiki/Windows_7 Windows 7]&lt;br /&gt;
&lt;br /&gt;
[http://en.wikipedia.org/wiki/Windows_8 Windows 8]&lt;br /&gt;
|-&lt;br /&gt;
|'''Platform'''&lt;br /&gt;
| [http://en.wikipedia.org/wiki/IA-32 IA-32] and [http://en.wikipedia.org/wiki/X86-64 x86-64]&lt;br /&gt;
|-&lt;br /&gt;
|'''Available in'''&lt;br /&gt;
|Over 20 languages&lt;br /&gt;
|-&lt;br /&gt;
|'''Type'''&lt;br /&gt;
|Advanced graphical programming software&lt;br /&gt;
|-&lt;br /&gt;
|'''License'''&lt;br /&gt;
|[http://en.wikipedia.org/wiki/Proprietary_software Proprietary]&lt;br /&gt;
|-&lt;br /&gt;
|'''Website'''&lt;br /&gt;
|[http://www.matrixmultimedia.com www.matrixmultimedia.com]&lt;br /&gt;
|-&lt;br /&gt;
|'''Blog site'''&lt;br /&gt;
|[http://www.matrixmultimedia.com/blog www.matrixmultimedia.com/blog]&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
Welcome to the Matrix Multimedia wiki, here you can find out and learn all you need to know about Flowcode 6 (and more!), from easy to follow exercises such as creating and saving a flowchart to technical API functions.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
From this page you can navigate the wiki and follow the base learning structure which has been set in place for your benefit, you can also search for articles to find out specific functions or components for useful information to help you get the most out of Flowcode 6.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
There are links to our '''[http://www.youtube.com/playlist?list=PLQDWBb7bxuCgg6aJgPJcfXBMzZdLILceQ official Youtube videos]''' throughout the wiki to help you learn about Flowcode, these videos are a few minutes (1 minute - 4 minutes) long and show you how to use features and functionality in Flowcode, these resources are very useful and can help you further understand Flowcode.&lt;br /&gt;
&lt;br /&gt;
These videos can also be found on the [http://www.matrixmultimedia.com/flowcode_help/help_videos.php Flowcode Help Videos] page at the [http://www.matrixmultimedia.com Matrix Multimedia website].&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
For more information about Flowcode as well as news, announcements and events including our general activity at Matrix see our blog site [http://www.matrixmultimedia.com/blog www.matrixmultimedia.com/blog], which is updated regularly and consists of various articles from different staff, from information and events in the new building to new additions to the team as well as new projects and applications.&lt;br /&gt;
&amp;lt;br /&amp;gt;__NOTOC__&amp;lt;br /&amp;gt;&lt;br /&gt;
==Flowcode Help==&lt;br /&gt;
&lt;br /&gt;
===[[Migrating to V6]]===&lt;br /&gt;
A mix of important information for migrating/upgrading from version 5 to version 6 of Flowcode including practical changes such as the positioning of components on the panels, technical changes such as the software &amp;amp; hardware channel selection changes and other information e.g. a table listing the status of component migration to Flowcode 6.&lt;br /&gt;
&lt;br /&gt;
===[[Flowcode Help Overview|Flowcode Basics]]===&lt;br /&gt;
Learn how to use Flowcode 6 and participate in practical exercises to improve your skills and knowledge of Flowcode. This explains the basics of Flowcode and how to use it effectively and efficiently. All users should at least skim through this section to learn about new features and methods integrated into Flowcode 6. New users are advised to start here to learn Flowcode from the base up.&lt;br /&gt;
&lt;br /&gt;
===[[Components|Component Help]]===&lt;br /&gt;
List of components which provide detailed information about individual components as well as examples of them in use, the information provided includes component and simulation macro references as well as property references and component functionality.&lt;br /&gt;
&lt;br /&gt;
===[[Event Reference|Simulation Events]]===&lt;br /&gt;
Structured overview of Events providing technical information for individual functions, each article contains information of the parameters and return value, a detailed description and an example of the Event.&lt;br /&gt;
&lt;br /&gt;
===[[API Overview|Simulation API]]===&lt;br /&gt;
''See also [[API Reference]]''&lt;br /&gt;
&lt;br /&gt;
Structured overview of Simulation API explaining individual functions and technical information, the [[API Reference|API reference]] page also provides a similar purpose although in a more open and expanded list to show each individual function under its class.&lt;br /&gt;
&lt;br /&gt;
===[[Exercises]]===&lt;br /&gt;
List of all exercises including the exercises used in [[Flowcode Help Overview|Flowcode Basics]] section as well as additional exercises to further improve your skills, the exercises are set in a practical and informative structure. Advanced users can start here and use these exercises to familiarize themselves with the new interface, features and functionality.&lt;br /&gt;
&lt;br /&gt;
===[[Feature List|Features]]===&lt;br /&gt;
This section lists the articles about features in Flowcode 6 which are structured into the [[Flowcode Help Overview|Flowcode Basics]] section so you can easily find information on specific features and learn how to use them effectively and efficiently. This section helps accompany other content to provide extra information to help you use the features correctly and understand them enough to use them to their full potential.&lt;br /&gt;
&lt;br /&gt;
===[[Concepts]]===&lt;br /&gt;
Complex methods, techniques and functionality used in Flowcode explained in a robust and practical manner, with reference to conventions used outside of Flowcode as well as information linking to functionality directly integrated within Flowcode.&lt;br /&gt;
&lt;br /&gt;
===[[Frequently Asked Questions]]===&lt;br /&gt;
Frequently asked questions (FAQ) regarding Flowcode 6, including changes from version 5, new features and altered functionality. Commonly asked questions feature general information regarding component properties, local, constant and global variables and exporting macros.&lt;/div&gt;</summary>
		<author><name>ReeceL</name></author>
		
	</entry>
	<entry>
		<id>https://www.flowcode.co.uk/wiki/index.php?title=Main_Page&amp;diff=14403</id>
		<title>Main Page</title>
		<link rel="alternate" type="text/html" href="https://www.flowcode.co.uk/wiki/index.php?title=Main_Page&amp;diff=14403"/>
		<updated>2014-01-24T14:03:33Z</updated>

		<summary type="html">&lt;p&gt;ReeceL: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{| cellpadding=&amp;quot;4&amp;quot; style=&amp;quot;border: 1px solid darkgray; float:right; width:300px&amp;quot;&lt;br /&gt;
|+ '''Flowcode 6'''&lt;br /&gt;
|-&lt;br /&gt;
| colspan=&amp;quot;2&amp;quot;|[[File:FC6_Icon.png|center]]&lt;br /&gt;
|-&lt;br /&gt;
| colspan=&amp;quot;2&amp;quot;|[[File:FC6_Box_Cover.jpg|center]]&lt;br /&gt;
|-&lt;br /&gt;
|width=&amp;quot;40%&amp;quot;|'''Developer'''&lt;br /&gt;
|[http://matrixmultimedia.com Matrix Multimedia]&lt;br /&gt;
|-&lt;br /&gt;
|'''Initial release'''&lt;br /&gt;
|3rd September 2013&lt;br /&gt;
|-&lt;br /&gt;
|'''Development status'''&lt;br /&gt;
|Active&lt;br /&gt;
|-&lt;br /&gt;
|'''Written in'''&lt;br /&gt;
|C++&lt;br /&gt;
|-&lt;br /&gt;
|'''Operating system'''&lt;br /&gt;
|[http://en.wikipedia.org/wiki/Windows_XP Windows XP]&lt;br /&gt;
&lt;br /&gt;
[http://en.wikipedia.org/wiki/Windows_Vista Windows Vista]&lt;br /&gt;
&lt;br /&gt;
[http://en.wikipedia.org/wiki/Windows_7 Windows 7]&lt;br /&gt;
&lt;br /&gt;
[http://en.wikipedia.org/wiki/Windows_8 Windows 8]&lt;br /&gt;
|-&lt;br /&gt;
|'''Platform'''&lt;br /&gt;
| [http://en.wikipedia.org/wiki/IA-32 IA-32] and [http://en.wikipedia.org/wiki/X86-64 x86-64]&lt;br /&gt;
|-&lt;br /&gt;
|'''Available in'''&lt;br /&gt;
|Over 20 languages&lt;br /&gt;
|-&lt;br /&gt;
|'''Type'''&lt;br /&gt;
|Advanced graphical programming software&lt;br /&gt;
|-&lt;br /&gt;
|'''License'''&lt;br /&gt;
|[http://en.wikipedia.org/wiki/Proprietary_software Proprietary]&lt;br /&gt;
|-&lt;br /&gt;
|'''Predecessor'''&lt;br /&gt;
|Flowcode 5&lt;br /&gt;
|-&lt;br /&gt;
|'''Website'''&lt;br /&gt;
|[http://www.matrixmultimedia.com www.matrixmultimedia.com]&lt;br /&gt;
|-&lt;br /&gt;
|'''Blog site'''&lt;br /&gt;
|[http://www.matrixmultimedia.com/blog www.matrixmultimedia.com/blog]&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
Welcome to the Matrix Multimedia wiki, here you can find out and learn all you need to know about Flowcode 6 (and more!), from easy to follow exercises such as creating and saving a flowchart to technical API functions.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
From this page you can navigate the wiki and follow the base learning structure which has been set in place for your benefit, you can also search for articles to find out specific functions or components for useful information to help you get the most out of Flowcode 6.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
There are links to our '''[http://www.youtube.com/playlist?list=PLQDWBb7bxuCgg6aJgPJcfXBMzZdLILceQ official Youtube videos]''' throughout the wiki to help you learn about Flowcode, these videos are a few minutes (1 minute - 4 minutes) long and show you how to use features and functionality in Flowcode, these resources are very useful and can help you further understand Flowcode.&lt;br /&gt;
&lt;br /&gt;
These videos can also be found on the [http://www.matrixmultimedia.com/flowcode_help/help_videos.php Flowcode Help Videos] page at the [http://www.matrixmultimedia.com Matrix Multimedia website].&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
For more information about Flowcode as well as news, announcements and events including our general activity at Matrix see our blog site [http://www.matrixmultimedia.com/blog www.matrixmultimedia.com/blog], which is updated regularly and consists of various articles from different staff, from information and events in the new building to new additions to the team as well as new projects and applications.&lt;br /&gt;
&amp;lt;br /&amp;gt;__NOTOC__&amp;lt;br /&amp;gt;&lt;br /&gt;
==Flowcode Help==&lt;br /&gt;
&lt;br /&gt;
===[[Migrating to V6]]===&lt;br /&gt;
A mix of important information for migrating/upgrading from version 5 to version 6 of Flowcode including practical changes such as the positioning of components on the panels, technical changes such as the software &amp;amp; hardware channel selection changes and other information e.g. a table listing the status of component migration to Flowcode 6.&lt;br /&gt;
&lt;br /&gt;
===[[Flowcode Help Overview|Flowcode Basics]]===&lt;br /&gt;
Learn how to use Flowcode 6 and participate in practical exercises to improve your skills and knowledge of Flowcode. This explains the basics of Flowcode and how to use it effectively and efficiently. All users should at least skim through this section to learn about new features and methods integrated into Flowcode 6. New users are advised to start here to learn Flowcode from the base up.&lt;br /&gt;
&lt;br /&gt;
===[[Components|Component Help]]===&lt;br /&gt;
List of components which provide detailed information about individual components as well as examples of them in use, the information provided includes component and simulation macro references as well as property references and component functionality.&lt;br /&gt;
&lt;br /&gt;
===[[Event Reference|Simulation Events]]===&lt;br /&gt;
Structured overview of Events providing technical information for individual functions, each article contains information of the parameters and return value, a detailed description and an example of the Event.&lt;br /&gt;
&lt;br /&gt;
===[[API Overview|Simulation API]]===&lt;br /&gt;
''See also [[API Reference]]''&lt;br /&gt;
&lt;br /&gt;
Structured overview of Simulation API explaining individual functions and technical information, the [[API Reference|API reference]] page also provides a similar purpose although in a more open and expanded list to show each individual function under its class.&lt;br /&gt;
&lt;br /&gt;
===[[Exercises]]===&lt;br /&gt;
List of all exercises including the exercises used in [[Flowcode Help Overview|Flowcode Basics]] section as well as additional exercises to further improve your skills, the exercises are set in a practical and informative structure. Advanced users can start here and use these exercises to familiarize themselves with the new interface, features and functionality.&lt;br /&gt;
&lt;br /&gt;
===[[Feature List|Features]]===&lt;br /&gt;
This section lists the articles about features in Flowcode 6 which are structured into the [[Flowcode Help Overview|Flowcode Basics]] section so you can easily find information on specific features and learn how to use them effectively and efficiently. This section helps accompany other content to provide extra information to help you use the features correctly and understand them enough to use them to their full potential.&lt;br /&gt;
&lt;br /&gt;
===[[Concepts]]===&lt;br /&gt;
Complex methods, techniques and functionality used in Flowcode explained in a robust and practical manner, with reference to conventions used outside of Flowcode as well as information linking to functionality directly integrated within Flowcode.&lt;br /&gt;
&lt;br /&gt;
===[[Frequently Asked Questions]]===&lt;br /&gt;
Frequently asked questions (FAQ) regarding Flowcode 6, including changes from version 5, new features and altered functionality. Commonly asked questions feature general information regarding component properties, local, constant and global variables and exporting macros.&lt;/div&gt;</summary>
		<author><name>ReeceL</name></author>
		
	</entry>
	<entry>
		<id>https://www.flowcode.co.uk/wiki/index.php?title=Activating_Flowcode&amp;diff=13144</id>
		<title>Activating Flowcode</title>
		<link rel="alternate" type="text/html" href="https://www.flowcode.co.uk/wiki/index.php?title=Activating_Flowcode&amp;diff=13144"/>
		<updated>2014-01-02T14:40:50Z</updated>

		<summary type="html">&lt;p&gt;ReeceL: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;sidebar&amp;gt;Sidebar: Introduction&amp;lt;/sidebar&amp;gt;&lt;br /&gt;
[[File:Gen_Activate_Flowcode_01.png|right]]&lt;br /&gt;
[[File:Gen_Manual_Activation_01.png|right|282x256px]]&lt;br /&gt;
To allow Flowcode to compile and access locked components it requires a valid license, you can activate Flowcode offline by using a license file, username and key.&lt;br /&gt;
&lt;br /&gt;
The Flowcode registration application is a tool that runs when performing the CD key or activation process.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The registration application is executed when you click the 'Activate' button or by pressing the '''Enter''' key button on the Flowcode activation screen which is accessed by clicking 'Activate' from the 'Help' menu in Flowcode (Help &amp;gt; Activate...).&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The icon to the top left of the 'Activate Flowcode' window indicates the current status of Flowcode.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Red - Free/Demo Mode - No active license.&lt;br /&gt;
&lt;br /&gt;
Amber  - Trial Mode - Trial license activated (30 day trial).&lt;br /&gt;
&lt;br /&gt;
Green - Activated - Valid license activated.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
You can activate Flowcode offline by using the 'Manual Activation' window which can be accessed by clicking the 'Manual activation...' button from the 'Activate Flowcode' window previously mentioned.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Manual activation can be done with a Flowcode username, a license .key file and a key including the =====Start key===== and =====End key===== tags before and after the key.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Please note that newer operating systems will require that you run the registration application as an administrator to allow it to correctly perform the activation process on your computer.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Flowcode Reminder Screen==&lt;br /&gt;
When running Flowcode with a trail license you will be notified when your license is about to run out, from this window you can see how many days are left until your license runs out. &lt;br /&gt;
&lt;br /&gt;
You can also enter a new key to activate license which you have already purchased, you can also click the 'Buy Now!' button to buy a license to then activate Flowcode or you can just click 'OK' and continue using Flowcode with a trial license.&lt;br /&gt;
&lt;br /&gt;
[[File:Gen_Flowcode_Temporary_Key_Expiration_Warning.png|center]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Enter Key''' - Opens the 'Activate Flowcode' window previously mentioned to activate your purchased license.&lt;br /&gt;
&lt;br /&gt;
'''OK''' - Dismisses the warning and carrys on using the trail/demo mode of Flowcode.&lt;br /&gt;
&lt;br /&gt;
'''Buy Now!''' - Opens the [http://www.matrixmultimedia.co.uk/flowcode.php Flowcode page] on the [http://www.matrixmultimedia.com Matrix Multimedia website] in order to buy a license.&lt;/div&gt;</summary>
		<author><name>ReeceL</name></author>
		
	</entry>
	<entry>
		<id>https://www.flowcode.co.uk/wiki/index.php?title=Key_Mappings&amp;diff=13080</id>
		<title>Key Mappings</title>
		<link rel="alternate" type="text/html" href="https://www.flowcode.co.uk/wiki/index.php?title=Key_Mappings&amp;diff=13080"/>
		<updated>2013-11-27T11:12:22Z</updated>

		<summary type="html">&lt;p&gt;ReeceL: Redirected page to Editing Key Mappings&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;#REDIRECT [[Editing Key Mappings]]&lt;/div&gt;</summary>
		<author><name>ReeceL</name></author>
		
	</entry>
	<entry>
		<id>https://www.flowcode.co.uk/wiki/index.php?title=Editing_Key_Mappings&amp;diff=12263</id>
		<title>Editing Key Mappings</title>
		<link rel="alternate" type="text/html" href="https://www.flowcode.co.uk/wiki/index.php?title=Editing_Key_Mappings&amp;diff=12263"/>
		<updated>2013-11-08T09:10:07Z</updated>

		<summary type="html">&lt;p&gt;ReeceL: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;sidebar&amp;gt;Sidebar: What Is a Component?&amp;lt;/sidebar&amp;gt;&lt;br /&gt;
[[File:Gen_Edit_Menu_Key_Mappings.png|right]]&lt;br /&gt;
Key mappings allow you to use the keyboard keys 0 to 9 to control components attached to the microcontroller. For example if you have a bank of 8 push switches connected to the microcontroller, you could map the keys 1 to 8 to mimic the pushing and releasing of these switches when the flowchart is simulated.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
To set up or change key mappings, select the Key Mappings option from the Edit menu (Edit &amp;gt; Key Mappings...). For each numeric key, you can select a component and for each component, you can select the individual element that you wish to control with that key. For example if you wish to use the '0' key to control the 5th switch in a component named 'Switches1' then select 'Switches1' in the Component list for Key 0 and then select 5 in the Element list for Key 0.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[File:Gen_Component_Key_Mappings_01.png|left]]&lt;br /&gt;
&lt;br /&gt;
''Work in progress - needs re-writing.&lt;br /&gt;
&lt;br /&gt;
'''Key'''&lt;br /&gt;
&lt;br /&gt;
The key on the number keypad that you wish to map.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Component'''&lt;br /&gt;
&lt;br /&gt;
The attached component that you wish to map the key to.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Element'''&lt;br /&gt;
&lt;br /&gt;
The individual element (Switch etc.) that you wish to bind the key to.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Elements are numbered sequentially in the same order as on the component.&lt;br /&gt;
&lt;br /&gt;
Components with scrollbars use elements 1 and 2 to increase/decrease the scrollbar value.&lt;br /&gt;
&lt;br /&gt;
Using Key mapping with elements that toggle will toggle the element on/off.&lt;br /&gt;
&lt;br /&gt;
Using key mapping with press to make elements will send the element into its high, active, state when the key is pressed. &lt;br /&gt;
&lt;br /&gt;
Releasing the key will return the element to its low, inactive state.&lt;br /&gt;
&lt;br /&gt;
Using key mapping with scrollbars will increase/decrease the scrollbar value.''&lt;/div&gt;</summary>
		<author><name>ReeceL</name></author>
		
	</entry>
	<entry>
		<id>https://www.flowcode.co.uk/wiki/index.php?title=Editing_Key_Mappings&amp;diff=12262</id>
		<title>Editing Key Mappings</title>
		<link rel="alternate" type="text/html" href="https://www.flowcode.co.uk/wiki/index.php?title=Editing_Key_Mappings&amp;diff=12262"/>
		<updated>2013-11-08T09:08:48Z</updated>

		<summary type="html">&lt;p&gt;ReeceL: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;sidebar&amp;gt;Sidebar: What Is a Component?&amp;lt;/sidebar&amp;gt;&lt;br /&gt;
[[File:Gen_Edit_Menu_Key_Mappings.png|right]]&lt;br /&gt;
Key mappings allow you to use the keyboard keys 0 to 9 to control components attached to the microcontroller. For example if you have a bank of 8 push switches connected to the microcontroller, you could map the keys 1 to 8 to mimic the pushing and releasing of these switches when the flowchart is simulated.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
To set up or change key mappings, select the Key Mappings option from the Edit menu (Edit &amp;gt; Key Mappings...). For each numeric key, you can select a component and for each component, you can select the individual element that you wish to control with that key. For example if you wish to use the '0' key to control the 5th switch in a component named 'Switches1' then select 'Switches1' in the Component list for Key 0 and then select 5 in the Element list for Key 0.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[File:Gen_Component_Key_Mappings_01.png|left]]&lt;br /&gt;
&lt;br /&gt;
'''Key'''&lt;br /&gt;
&lt;br /&gt;
The key on the number keypad that you wish to map.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Component'''&lt;br /&gt;
&lt;br /&gt;
The attached component that you wish to map the key to.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Element'''&lt;br /&gt;
&lt;br /&gt;
The individual element (Switch etc.) that you wish to bind the key to.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Elements are numbered sequentially in the same order as on the component.&lt;br /&gt;
&lt;br /&gt;
Components with scrollbars use elements 1 and 2 to increase/decrease the scrollbar value.&lt;br /&gt;
&lt;br /&gt;
Using Key mapping with elements that toggle will toggle the element on/off.&lt;br /&gt;
&lt;br /&gt;
Using key mapping with press to make elements will send the element into its high, active, state when the key is pressed. &lt;br /&gt;
&lt;br /&gt;
Releasing the key will return the element to its low, inactive state.&lt;br /&gt;
&lt;br /&gt;
Using key mapping with scrollbars will increase/decrease the scrollbar value.&lt;/div&gt;</summary>
		<author><name>ReeceL</name></author>
		
	</entry>
	<entry>
		<id>https://www.flowcode.co.uk/wiki/index.php?title=Editing_Key_Mappings&amp;diff=12261</id>
		<title>Editing Key Mappings</title>
		<link rel="alternate" type="text/html" href="https://www.flowcode.co.uk/wiki/index.php?title=Editing_Key_Mappings&amp;diff=12261"/>
		<updated>2013-11-08T09:08:40Z</updated>

		<summary type="html">&lt;p&gt;ReeceL: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;sidebar&amp;gt;Sidebar: What Is a Component?&amp;lt;/sidebar&amp;gt;&lt;br /&gt;
[[File:Gen_Edit_Menu_Key_Mappings.png|right]]&lt;br /&gt;
Key mappings allow you to use the keyboard keys 0 to 9 to control components attached to the microcontroller. For example if you have a bank of 8 push switches connected to the microcontroller, you could map the keys 1 to 8 to mimic the pushing and releasing of these switches when the flowchart is simulated.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
To set up or change key mappings, select the Key Mappings option from the Edit menu (Edit &amp;gt; Key Mappings...). For each numeric key, you can select a component and for each component, you can select the individual element that you wish to control with that key. For example if you wish to use the '0' key to control the 5th switch in a component named 'Switches1' then select 'Switches1' in the Component list for Key 0 and then select 5 in the Element list for Key 0.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[File:Gen_Component_Key_Mappings_01.png|left]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Key'''&lt;br /&gt;
&lt;br /&gt;
The key on the number keypad that you wish to map.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Component'''&lt;br /&gt;
&lt;br /&gt;
The attached component that you wish to map the key to.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Element'''&lt;br /&gt;
&lt;br /&gt;
The individual element (Switch etc.) that you wish to bind the key to.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Elements are numbered sequentially in the same order as on the component.&lt;br /&gt;
&lt;br /&gt;
Components with scrollbars use elements 1 and 2 to increase/decrease the scrollbar value.&lt;br /&gt;
&lt;br /&gt;
Using Key mapping with elements that toggle will toggle the element on/off.&lt;br /&gt;
&lt;br /&gt;
Using key mapping with press to make elements will send the element into its high, active, state when the key is pressed. &lt;br /&gt;
&lt;br /&gt;
Releasing the key will return the element to its low, inactive state.&lt;br /&gt;
&lt;br /&gt;
Using key mapping with scrollbars will increase/decrease the scrollbar value.&lt;/div&gt;</summary>
		<author><name>ReeceL</name></author>
		
	</entry>
	<entry>
		<id>https://www.flowcode.co.uk/wiki/index.php?title=Editing_Key_Mappings&amp;diff=12260</id>
		<title>Editing Key Mappings</title>
		<link rel="alternate" type="text/html" href="https://www.flowcode.co.uk/wiki/index.php?title=Editing_Key_Mappings&amp;diff=12260"/>
		<updated>2013-11-08T09:08:28Z</updated>

		<summary type="html">&lt;p&gt;ReeceL: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;sidebar&amp;gt;Sidebar: What Is a Component?&amp;lt;/sidebar&amp;gt;&lt;br /&gt;
[[File:Gen_Edit_Menu_Key_Mappings.png|right]]&lt;br /&gt;
Key mappings allow you to use the keyboard keys 0 to 9 to control components attached to the microcontroller. For example if you have a bank of 8 push switches connected to the microcontroller, you could map the keys 1 to 8 to mimic the pushing and releasing of these switches when the flowchart is simulated.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
To set up or change key mappings, select the Key Mappings option from the Edit menu (Edit &amp;gt; Key Mappings...). For each numeric key, you can select a component and for each component, you can select the individual element that you wish to control with that key. For example if you wish to use the '0' key to control the 5th switch in a component named 'Switches1' then select 'Switches1' in the Component list for Key 0 and then select 5 in the Element list for Key 0.&lt;br /&gt;
&lt;br /&gt;
[[File:Gen_Component_Key_Mappings_01.png|left]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Key'''&lt;br /&gt;
&lt;br /&gt;
The key on the number keypad that you wish to map.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Component'''&lt;br /&gt;
&lt;br /&gt;
The attached component that you wish to map the key to.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Element'''&lt;br /&gt;
&lt;br /&gt;
The individual element (Switch etc.) that you wish to bind the key to.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Elements are numbered sequentially in the same order as on the component.&lt;br /&gt;
&lt;br /&gt;
Components with scrollbars use elements 1 and 2 to increase/decrease the scrollbar value.&lt;br /&gt;
&lt;br /&gt;
Using Key mapping with elements that toggle will toggle the element on/off.&lt;br /&gt;
&lt;br /&gt;
Using key mapping with press to make elements will send the element into its high, active, state when the key is pressed. &lt;br /&gt;
&lt;br /&gt;
Releasing the key will return the element to its low, inactive state.&lt;br /&gt;
&lt;br /&gt;
Using key mapping with scrollbars will increase/decrease the scrollbar value.&lt;/div&gt;</summary>
		<author><name>ReeceL</name></author>
		
	</entry>
	<entry>
		<id>https://www.flowcode.co.uk/wiki/index.php?title=File:Gen_Component_Key_Mappings_01.png&amp;diff=12259</id>
		<title>File:Gen Component Key Mappings 01.png</title>
		<link rel="alternate" type="text/html" href="https://www.flowcode.co.uk/wiki/index.php?title=File:Gen_Component_Key_Mappings_01.png&amp;diff=12259"/>
		<updated>2013-11-08T09:08:01Z</updated>

		<summary type="html">&lt;p&gt;ReeceL: Example - Editing Key Mappings - Component Key Mappings window.&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Example - Editing Key Mappings - Component Key Mappings window.&lt;/div&gt;</summary>
		<author><name>ReeceL</name></author>
		
	</entry>
	<entry>
		<id>https://www.flowcode.co.uk/wiki/index.php?title=Flowcode_Help:Community_portal&amp;diff=12236</id>
		<title>Flowcode Help:Community portal</title>
		<link rel="alternate" type="text/html" href="https://www.flowcode.co.uk/wiki/index.php?title=Flowcode_Help:Community_portal&amp;diff=12236"/>
		<updated>2013-11-06T14:15:04Z</updated>

		<summary type="html">&lt;p&gt;ReeceL: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;There is an introduction course based around the Flowcode software and getting started with Microcontrollers.&lt;br /&gt;
&lt;br /&gt;
[http://www.matrixmultimedia.com/courses/itm/index.php Introduction to Microcontroller Programming]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
There is a very active Flowcode community on the Matrix forums which can be used to ask questions, share knowledge and collaborate on projects.&lt;br /&gt;
&lt;br /&gt;
[http://www.matrixmultimedia.com/mmforums/ Matrix User Forums]&lt;br /&gt;
&lt;br /&gt;
To sign up for the forums please visit the following link.&lt;br /&gt;
&lt;br /&gt;
[http://www.matrixmultimedia.com/mmforums/ucp.php?mode=register Matrix User Forums Registration Page]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
There is also a Blog which is written and maintained by the Matrix staff responsible for the creation and the upkeep of the Flowcode software.&lt;br /&gt;
&lt;br /&gt;
[http://matrixmultimedia.com/blog/ Matrix Blog]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Finally there is a repository of information, test files, examples, videos and articles available as part of our Learning Centre.&lt;br /&gt;
&lt;br /&gt;
[http://www.matrixmultimedia.com/lc_index.php Learning Centre]&lt;/div&gt;</summary>
		<author><name>ReeceL</name></author>
		
	</entry>
	<entry>
		<id>https://www.flowcode.co.uk/wiki/index.php?title=Sidebar:_Advanced_Features&amp;diff=12235</id>
		<title>Sidebar: Advanced Features</title>
		<link rel="alternate" type="text/html" href="https://www.flowcode.co.uk/wiki/index.php?title=Sidebar:_Advanced_Features&amp;diff=12235"/>
		<updated>2013-11-06T14:04:26Z</updated>

		<summary type="html">&lt;p&gt;ReeceL: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;* navigation&lt;br /&gt;
** mainpage|mainpage-description&lt;br /&gt;
** portal-url|portal&lt;br /&gt;
** Migrating_to_V6|Migrating to v6&lt;br /&gt;
** Flowcode_Help_Overview|Flowcode Basics&lt;br /&gt;
** Components|Component Help&lt;br /&gt;
** Event_Reference|Simulation Events&lt;br /&gt;
** API_Overview|Simulation API&lt;br /&gt;
** Exercises|Exercises&lt;br /&gt;
** Feature_List|Features&lt;br /&gt;
** Concepts|Concepts&lt;br /&gt;
** Frequently_Asked_Questions|FAQs&lt;br /&gt;
*SEARCH&lt;br /&gt;
*Advanced Features&lt;br /&gt;
**Advanced Features | Advanced Features&lt;br /&gt;
**Debugging Hardware and Software | Debugging Hardware and Software&lt;br /&gt;
**In Circuit Debugging | In Circuit Debugging&lt;br /&gt;
**Panel Managers | Panel Managers&lt;br /&gt;
**Using the Data Injector | Using the Data Injector&lt;br /&gt;
**Using the Data Scope | Using the Data Scope&lt;br /&gt;
**Assigning Code to an Existing Component | Assigning Code to an Existing Component&lt;br /&gt;
**Exercise - Create an LED Component | Creating a Component From Scratch&lt;br /&gt;
**CAL Components | CAL Components&lt;br /&gt;
**CAL - ADC | CAL - ADC&lt;br /&gt;
**CAL - CAN | CAL - CAN&lt;br /&gt;
**CAL - CAPTOUCH | CAL - CAPTOUCH&lt;br /&gt;
**CAL - EEPROM | CAL - EEPROM&lt;br /&gt;
**CAL - I2C | CAL - I2C&lt;br /&gt;
**CAL - SPI | CAL - SPI&lt;br /&gt;
**CAL - UART | CAL - UART&lt;br /&gt;
**Internal Oscillator | Internal Oscillator&lt;br /&gt;
**Phase Locked Loop (PLL) | Phase Locked Loop (PLL)&lt;br /&gt;
*TOOLBOX&lt;br /&gt;
*LANGUAGES&lt;br /&gt;
&lt;br /&gt;
[[Category:Sidebar]]&lt;/div&gt;</summary>
		<author><name>ReeceL</name></author>
		
	</entry>
	<entry>
		<id>https://www.flowcode.co.uk/wiki/index.php?title=Sidebar:_Advanced_Features&amp;diff=12234</id>
		<title>Sidebar: Advanced Features</title>
		<link rel="alternate" type="text/html" href="https://www.flowcode.co.uk/wiki/index.php?title=Sidebar:_Advanced_Features&amp;diff=12234"/>
		<updated>2013-11-06T14:03:46Z</updated>

		<summary type="html">&lt;p&gt;ReeceL: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;* navigation&lt;br /&gt;
** mainpage|mainpage-description&lt;br /&gt;
** portal-url|portal&lt;br /&gt;
** Migrating_to_V6|Migrating to v6&lt;br /&gt;
** Flowcode_Help_Overview|Flowcode Basics&lt;br /&gt;
** Components|Component Help&lt;br /&gt;
** Event_Reference|Simulation Events&lt;br /&gt;
** API_Overview|Simulation API&lt;br /&gt;
** Exercises|Exercises&lt;br /&gt;
** Feature_List|Features&lt;br /&gt;
** Concepts|Concepts&lt;br /&gt;
** Frequently_Asked_Questions|FAQs&lt;br /&gt;
*SEARCH&lt;br /&gt;
*Advanced Features&lt;br /&gt;
**Advanced Features | Advanced Features&lt;br /&gt;
**Debugging Hardware and Software | Debugging Hardware and Software&lt;br /&gt;
**In Circuit Debugging | In Circuit Debugging&lt;br /&gt;
**Panel Managers | Panel Managers&lt;br /&gt;
**Using the Data Injector | Using the Data Injector&lt;br /&gt;
**Using the Data Scope | Using the Data Scope&lt;br /&gt;
**Assigning Code to an Existing Component | Assigning Code to an Existing Component&lt;br /&gt;
**Exercise - Creating an LED Component | Creating a Component From Scratch&lt;br /&gt;
**CAL Components | CAL Components&lt;br /&gt;
**CAL - ADC | CAL - ADC&lt;br /&gt;
**CAL - CAN | CAL - CAN&lt;br /&gt;
**CAL - CAPTOUCH | CAL - CAPTOUCH&lt;br /&gt;
**CAL - EEPROM | CAL - EEPROM&lt;br /&gt;
**CAL - I2C | CAL - I2C&lt;br /&gt;
**CAL - SPI | CAL - SPI&lt;br /&gt;
**CAL - UART | CAL - UART&lt;br /&gt;
**Internal Oscillator | Internal Oscillator&lt;br /&gt;
**Phase Locked Loop (PLL) | Phase Locked Loop (PLL)&lt;br /&gt;
*TOOLBOX&lt;br /&gt;
*LANGUAGES&lt;br /&gt;
&lt;br /&gt;
[[Category:Sidebar]]&lt;/div&gt;</summary>
		<author><name>ReeceL</name></author>
		
	</entry>
	<entry>
		<id>https://www.flowcode.co.uk/wiki/index.php?title=Phase_Locked_Loop_(PLL)&amp;diff=12233</id>
		<title>Phase Locked Loop (PLL)</title>
		<link rel="alternate" type="text/html" href="https://www.flowcode.co.uk/wiki/index.php?title=Phase_Locked_Loop_(PLL)&amp;diff=12233"/>
		<updated>2013-11-06T14:03:10Z</updated>

		<summary type="html">&lt;p&gt;ReeceL: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;sidebar&amp;gt;Sidebar: Advanced Features&amp;lt;/sidebar&amp;gt;&lt;br /&gt;
A lot of the devices have an inbuilt PLL or phase locked loop which can be used to provide a variable frequency from a fixed source oscillator such as a crystal.&lt;br /&gt;
&lt;br /&gt;
A common use for the PLL is to take the input crystal frequency and multiply this up to give a much higher clock frequency on board the device.&lt;br /&gt;
&lt;br /&gt;
Some devices can even use their PLL with the internal oscillator allowing for maximum flexibility with minimal external parts.&lt;br /&gt;
&lt;br /&gt;
The device datasheet should detail if a PLL is available to the device.&lt;br /&gt;
&lt;br /&gt;
Some devices are very easy to configure and expose all the settings for the PLL via the configuration options. An example of this is the PIC18F2455 family which features a PLL to provide the functionality of boosting the input clock speed to 48MHz which is compatible with full speed USB communications. Here we have specified a 4MHz input clock speed and configured the oscillator to use the PLL multiplied version of the HS oscillator.&lt;br /&gt;
&lt;br /&gt;
[[File:PLLConf1.jpg]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Some devices are not this simple and require a section of C code at the start of the program. These devices normally have to startup in a low speed mode and then switch to the high speed mode to allow the PLL to be configured correctly. The upside to these types of device is you can normally re-configure the PLL at any time to reduce power consumption etc.&lt;br /&gt;
&lt;br /&gt;
Here is a piece of example C code used to enable the PLL on-board a PIC18F24J50 device.&lt;br /&gt;
&lt;br /&gt;
[[File:PLLConf2.jpg]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Here is an example of a much more complicated PLL where there is a large calculation using several parameters that determines the overall output frequency as seen on the dsPIC33FJ128GP802. &lt;br /&gt;
&lt;br /&gt;
This takes the input clock speed of 12MHz and multiplies it up to 80MHz to provide the maximum clock frequency for the device which equates to 40MIPs.&lt;br /&gt;
&lt;br /&gt;
[[File:PLLConf3.jpg]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Here is the PLL calculation plus information shown in the dsPIC33FJ128GP802 device datasheet.&lt;br /&gt;
&lt;br /&gt;
[[File:PLLConf4.jpg]]&lt;/div&gt;</summary>
		<author><name>ReeceL</name></author>
		
	</entry>
	<entry>
		<id>https://www.flowcode.co.uk/wiki/index.php?title=Internal_Oscillator&amp;diff=12232</id>
		<title>Internal Oscillator</title>
		<link rel="alternate" type="text/html" href="https://www.flowcode.co.uk/wiki/index.php?title=Internal_Oscillator&amp;diff=12232"/>
		<updated>2013-11-06T14:02:56Z</updated>

		<summary type="html">&lt;p&gt;ReeceL: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;sidebar&amp;gt;Sidebar: Advanced Features&amp;lt;/sidebar&amp;gt;&lt;br /&gt;
A lot of the devices have an inbuilt oscillator which can be used to reduce the number of devices required to drive the microcontroller.&lt;br /&gt;
&lt;br /&gt;
The device datasheet should detail the type of oscillator available to the device.&lt;br /&gt;
&lt;br /&gt;
Here we have the datasheet for the PIC16F88 device listing the options available for the internal oscillator.&lt;br /&gt;
&lt;br /&gt;
[[File:16F88OscCon.jpg]] &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Using a C code icon at the very top of the Main macro we can specify which speed the microcontroller should start-up with.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
To access a register using PIC use the register name in all lower case. e.g. &amp;quot;osccon&amp;quot; &lt;br /&gt;
&lt;br /&gt;
For the PIC16 and AVR use the register name in all upper case. e.g. &amp;quot;OSCCON&amp;quot; &lt;br /&gt;
&lt;br /&gt;
Remember to end the line of C code with a semicolon to mark the end of the instruction.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Here is an example to configure the internal oscillator to 8MHz on the PIC16F88.&lt;br /&gt;
&lt;br /&gt;
[[File:16F88IntOsc1.jpg]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Here is an example to configure the internal oscillator to 1MHz on the PIC16F88.&lt;br /&gt;
&lt;br /&gt;
[[File:16F88IntOsc2.jpg]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Be sure to set the clock speed in the project options to the same speed to allow your delays and any communications baud rates to be correct.&lt;br /&gt;
&lt;br /&gt;
[[File:16F88IntOscProj.jpg]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The configuration settings will also need to be edited from the default HS type oscillator to the IntOsc setting.&lt;br /&gt;
&lt;br /&gt;
[[File:16F88IntOscConf.jpg]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
A [[One second LED flasher]] test can be very useful to confirm if your device is actually running at the intended speed.&lt;/div&gt;</summary>
		<author><name>ReeceL</name></author>
		
	</entry>
	<entry>
		<id>https://www.flowcode.co.uk/wiki/index.php?title=Assigning_Code_to_an_Existing_Component&amp;diff=12231</id>
		<title>Assigning Code to an Existing Component</title>
		<link rel="alternate" type="text/html" href="https://www.flowcode.co.uk/wiki/index.php?title=Assigning_Code_to_an_Existing_Component&amp;diff=12231"/>
		<updated>2013-11-06T14:02:39Z</updated>

		<summary type="html">&lt;p&gt;ReeceL: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;sidebar&amp;gt;Sidebar: Advanced Features&amp;lt;/sidebar&amp;gt;&lt;br /&gt;
Here is a brief video detailing how to wrap up your custom macros into a component that can be re-used in many projects. This should also prove useful to anyone wanting to understand the basics of creating a component in Flowcode.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div align=&amp;quot;center&amp;quot;&amp;gt;&lt;br /&gt;
{{#ev:youtube|xhvrwILJA38|640}}&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;/div&gt;</summary>
		<author><name>ReeceL</name></author>
		
	</entry>
	<entry>
		<id>https://www.flowcode.co.uk/wiki/index.php?title=Using_the_Data_Recorder&amp;diff=12230</id>
		<title>Using the Data Recorder</title>
		<link rel="alternate" type="text/html" href="https://www.flowcode.co.uk/wiki/index.php?title=Using_the_Data_Recorder&amp;diff=12230"/>
		<updated>2013-11-06T14:02:08Z</updated>

		<summary type="html">&lt;p&gt;ReeceL: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;sidebar&amp;gt;Sidebar: Advanced Features&amp;lt;/sidebar&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
__TOC__&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Scope Introduction===&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The '''Data Scope''' allows the user to see the results and values from raw data and components such as dials and measures. This data is displayed during simulation and allows you to monitor the state of the various signals plotted to the various scope channels. &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The Data Scope can read and display data from various different ports simultaneously during simulation and can be adjusted to view the data at various speeds which allowed for increased accuracy or a larger amount of data to be displayed at any time.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The Scope is very useful for analyzing data as it can accurately display information to identify patterns in the data as well as the speed data is being displayed at. Components such as the DSP range will automatically create their own scope channels allowing for very simple yet powerful means of monitoring and debugging the system.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The Scope window is also used with the ICT (In Circuit Test) which is due to be released early 2014 along with the EB006 version 9 hardware.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[File:Gen_Data_Scope_Example_01.png]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Creating a scope group===&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
To create a new scope group you first need to create a global handle type variable to store the reference to the scope group. This is basically a unique number which used to refer to that specific group of the scope window. To do this open the [[Project_Explorer|Project Explorer]] window and select the Globals tab. Next right click the Variables portion of the tree view and select Add New from the menu. In the Create a new variable dialogue that pops up give the variable a meaningful name such as ScopeGroupHandle, then switch the variable type to Object Handle and click OK. You should then get a Object handle variable appearing in the [[Project_Explorer|Project Explorer]] window.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[File:Scope1.jpg]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Next we need to assign the handle variable with a value by calling the Simulation API. To do this we add a [[Simulation_Macro_Icon_Properties|simulation macro] icon to the Main flowchart and double click the item on the flowchart to edit the icon's properties. Inside the icon property window we first need to ensure that the Functions tab is selected and then scroll down to the Scope section before clicking the + icon to see all the API calls related to the Scope functionality.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[File:Scope2.jpg]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The [[API_Scope.AddGroup|AddGroup]] function call creates a new named group of streams on the Scope window. The return value the function call requires a handle type variable, luckily we have already created this above.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[File:Scope3A.jpg]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The [[API_Scope.AddStream|AddStream]] function call adds a new named stream to the group on the Scope window. The return value the function call requires a handle type variable so we will have to create a new global object handle type variable to store this. This handle must be unique for a single stream so a new object handle variable must exist for every stream on the scope.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[File:Scope3B.jpg]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
When we run the simulation the new group will be created on the scope window ready for data to be streamed in. &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[File:Scope3.jpg]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
By moving the API call from the Main macro to say the [[Event_Components.Initialise|simulation initialise event]] macro we can create a component which will automatically add our new scope group and stream when the component is added to a program. This is the way that components such as the DSP based components add their data to the console window.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[File:Scope4.jpg]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Note that a group with no valid stream handles will not show up on the Scope window just to try and avoid potential unnecessary clutter. &lt;br /&gt;
&lt;br /&gt;
Assigning the handle variable with the value of 0 using a [[Calculation_Icon_Properties|Calculation icon]] or calling the [[API_System.DeleteHandle|System -&amp;gt; DeleteHandle]] API call will effectively remove the group or stream from the scope window.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Adding a digital pin or port to a stream===&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
A digital pin or port can be assigned to a stream object handle by using the [[API_Scope.AddPort|AddPort]] function call. The function requires the stream object handle, the port index where PORTA is 0, PORTB is 1 etc. The BitMask parameter is a binary AND mask which selects which bits of the port will be available on the scope stream. The PackMask parameter will move all the active bits together if necessary. The merge parameter allows you to add multiple ports or pins to a single stream.&lt;br /&gt;
&lt;br /&gt;
To monitor a single pin with a LED connected to port pin A0 we can simply call the [[API_Scope.AddPort|AddPort]] function like this.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[File:Scope5.jpg]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Here is a simple program to toggle the LED with the signal being replicated on the scope trace.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[File:Scope6.jpg]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
To monitor a full port with a LED Array connected to PortB we can simply call the [[API_Scope.AddPort|AddPort]] function like this.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[File:Scope7.jpg]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
We then need to scale the scope channel to get the value in the range of 0-1 by calling the [[API_Scope.AddOp|AddOp]] function like this.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[File:Scope8.jpg]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Here is a simple program to generate a digital counter on the port with the signal being replicated on the scope trace. The [[API_System.ShowHandle|ShowHandle]] function allows the Scope window to appear automatically without the user having to manually open the Scope window.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[File:Scope14.jpg]]&lt;br /&gt;
&lt;br /&gt;
===Adding an analogue pin to a stream===&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
An analogue pin can be assigned to a stream object handle by using the [[API_Scope.AddAnalog|AddAnalog]] function call. The function requires the stream object handle, the analogue channel index where AN0 is 0, AN1 is 1 etc. The subtract parameter allows you to add or subtract multiple analogue signals on a single stream.&lt;br /&gt;
&lt;br /&gt;
To monitor a single analogue pin with a potentiometer connected to pin AN0 we can simply call the [[API_Scope.AddAnalog|AddAnalog]] function like this.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[File:Scope9.jpg]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Here is a simple program to track the value of an analogue input signal based on the position of the potentiometer.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[File:Scope10.jpg]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Adding an custom value to a stream===&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
A custom value can be assigned to a stream object handle by using the [[API_Scope.AddCustom|AddCustom]] function call. The function requires the stream object handle, the custom channel index 0-31 for each stream handle. The subtract parameter allows you to add or subtract multiple signals on a single stream.&lt;br /&gt;
&lt;br /&gt;
To create a single custom stream we can simply call the [[API_Scope.AddCustom|AddCustom]] function like this. &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[File:Scope11.jpg]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The data for a custom channel cannot come from a digital or analogue channel automatically so instead we have to manually pass the data to the custom channel.  This is done by using the [[API_Scope.SetCustom|SetCustom]] function call. The value passed should be a floating point real number in the range between 0 and 1 so to convert a byte variable we have to divide by the value 255.0.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[File:Scope13.jpg]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Here is a simple program to track the values of two analogue input signals and then calculate and plot the average between the two readings.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[File:Scope12.jpg]]&lt;/div&gt;</summary>
		<author><name>ReeceL</name></author>
		
	</entry>
	<entry>
		<id>https://www.flowcode.co.uk/wiki/index.php?title=Sidebar:_Advanced_Features&amp;diff=12229</id>
		<title>Sidebar: Advanced Features</title>
		<link rel="alternate" type="text/html" href="https://www.flowcode.co.uk/wiki/index.php?title=Sidebar:_Advanced_Features&amp;diff=12229"/>
		<updated>2013-11-06T14:01:26Z</updated>

		<summary type="html">&lt;p&gt;ReeceL: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;* navigation&lt;br /&gt;
** mainpage|mainpage-description&lt;br /&gt;
** portal-url|portal&lt;br /&gt;
** Migrating_to_V6|Migrating to v6&lt;br /&gt;
** Flowcode_Help_Overview|Flowcode Basics&lt;br /&gt;
** Components|Component Help&lt;br /&gt;
** Event_Reference|Simulation Events&lt;br /&gt;
** API_Overview|Simulation API&lt;br /&gt;
** Exercises|Exercises&lt;br /&gt;
** Feature_List|Features&lt;br /&gt;
** Concepts|Concepts&lt;br /&gt;
** Frequently_Asked_Questions|FAQs&lt;br /&gt;
*SEARCH&lt;br /&gt;
*Advanced Features&lt;br /&gt;
**Advanced Features | Advanced Features&lt;br /&gt;
**Debugging Hardware and Software | Debugging Hardware and Software&lt;br /&gt;
**In Circuit Debugging | In Circuit Debugging&lt;br /&gt;
**Panel Managers | Panel Managers&lt;br /&gt;
**Using the Data Injector | Using the Data Injector&lt;br /&gt;
**Using the Data Scope | Using the Data Scope&lt;br /&gt;
**Assigning Code to an Existing Component | Assigning Code to an Existing Component&lt;br /&gt;
**Creating a Component From Scratch | Creating a Component From Scratch&lt;br /&gt;
**CAL Components | CAL Components&lt;br /&gt;
**CAL - ADC | CAL - ADC&lt;br /&gt;
**CAL - CAN | CAL - CAN&lt;br /&gt;
**CAL - CAPTOUCH | CAL - CAPTOUCH&lt;br /&gt;
**CAL - EEPROM | CAL - EEPROM&lt;br /&gt;
**CAL - I2C | CAL - I2C&lt;br /&gt;
**CAL - SPI | CAL - SPI&lt;br /&gt;
**CAL - UART | CAL - UART&lt;br /&gt;
**Internal Oscillator | Internal Oscillator&lt;br /&gt;
**Phase Locked Loop (PLL) | Phase Locked Loop (PLL)&lt;br /&gt;
*TOOLBOX&lt;br /&gt;
*LANGUAGES&lt;br /&gt;
&lt;br /&gt;
[[Category:Sidebar]]&lt;/div&gt;</summary>
		<author><name>ReeceL</name></author>
		
	</entry>
	<entry>
		<id>https://www.flowcode.co.uk/wiki/index.php?title=Assigning_Code_to_an_Existing_Component&amp;diff=12228</id>
		<title>Assigning Code to an Existing Component</title>
		<link rel="alternate" type="text/html" href="https://www.flowcode.co.uk/wiki/index.php?title=Assigning_Code_to_an_Existing_Component&amp;diff=12228"/>
		<updated>2013-11-06T14:00:07Z</updated>

		<summary type="html">&lt;p&gt;ReeceL: ReeceL moved page Assigning code to an existing component to Assigning Code to an Existing Component without leaving a redirect&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Here is a brief video detailing how to wrap up your custom macros into a component that can be re-used in many projects. This should also prove useful to anyone wanting to understand the basics of creating a component in Flowcode.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div align=&amp;quot;center&amp;quot;&amp;gt;&lt;br /&gt;
{{#ev:youtube|xhvrwILJA38|640}}&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;/div&gt;</summary>
		<author><name>ReeceL</name></author>
		
	</entry>
	<entry>
		<id>https://www.flowcode.co.uk/wiki/index.php?title=Exercise_-_Exporting_the_LED_Component&amp;diff=12226</id>
		<title>Exercise - Exporting the LED Component</title>
		<link rel="alternate" type="text/html" href="https://www.flowcode.co.uk/wiki/index.php?title=Exercise_-_Exporting_the_LED_Component&amp;diff=12226"/>
		<updated>2013-11-06T13:59:01Z</updated>

		<summary type="html">&lt;p&gt;ReeceL: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;sidebar&amp;gt;Sidebar: Component Exercises&amp;lt;/sidebar&amp;gt;&lt;br /&gt;
Now that we have created an LED in the previous [[Exercise - Create an LED Component]] article we can now export the component for use elsewhere.&lt;br /&gt;
&lt;br /&gt;
__NOTOC__&lt;br /&gt;
==Preliminaries==&lt;br /&gt;
[[File:gen_exerciseLEDexport_compmansetup_01.png|280px|right]]&lt;br /&gt;
* Create a LED component as shown in the [[Exercise - Create an LED Component]].&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Declaring the interface==&lt;br /&gt;
&lt;br /&gt;
Before you export a component, you need to 'declare the interface'. The interface is the collection of macros and files publically available to the user. Declaring the interface means deciding which of the component routines to make available to the user, and to decide whether these are suitable for simulation or for download.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
* Move the mouse cursor over the [[System Panel]], and right-click.&lt;br /&gt;
&lt;br /&gt;
* Select the option 'Export component'. The 'Component Management' dialogue box opens. This replicates the settings, [[Settings Manager]], [[Interface Manager]] and [[Resource Manager]] available on the [[Properties Panel]].&lt;br /&gt;
[[File:gen_exerciseLEDexport_componentman01.png|280px|right]]&lt;br /&gt;
* Configure this for the LED component as follow:&lt;br /&gt;
:* Click on the 'Setup' tab.&lt;br /&gt;
::* Assign the component to a category, by clicking on the down-arrow next to the label 'Category'. In this case, the component will go into the 'Outputs' toolbox.&lt;br /&gt;
::* Click on the check-box next to the 'Use an image of the panel' label.&lt;br /&gt;
:* Click on the 'Interface' tab. &lt;br /&gt;
::* Set the 'LEDoff' and 'LEDon' macros as 'Component' macros, by selecting each in turn, and clicking on 'Component macro' in the 'Type of macro' drop-down menu. &lt;br /&gt;
::* Set the 'PinChange' macro as a 'Hidden' macro, in the same way.&lt;br /&gt;
:* In this case, there is no need to use the 'Resources' tab, as there are no additional files to save with the component.&lt;br /&gt;
&lt;br /&gt;
* Click on 'OK'.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Saving the component==&lt;br /&gt;
* You may be asked if you want to save the current flowchart. Do so if you wish.&lt;br /&gt;
&lt;br /&gt;
* The 'Save As' dialogue box opens. This will automatically point to a destination Flowcode will search for components. Select a suitable name for the component. &lt;br /&gt;
&lt;br /&gt;
* Click 'Save'. The component file is saved with a '*.fcpx' extension.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==What next?==&lt;br /&gt;
Now you need to [[Exercise - Importing the LED Component|import the component]] into a new flowchart for testing.&lt;/div&gt;</summary>
		<author><name>ReeceL</name></author>
		
	</entry>
	<entry>
		<id>https://www.flowcode.co.uk/wiki/index.php?title=Exercise_-_Create_an_LED_Component&amp;diff=12225</id>
		<title>Exercise - Create an LED Component</title>
		<link rel="alternate" type="text/html" href="https://www.flowcode.co.uk/wiki/index.php?title=Exercise_-_Create_an_LED_Component&amp;diff=12225"/>
		<updated>2013-11-06T13:57:57Z</updated>

		<summary type="html">&lt;p&gt;ReeceL: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;sidebar&amp;gt;Sidebar: Component Exercises&amp;lt;/sidebar&amp;gt;&lt;br /&gt;
[[File:gen_exerciseLEDcreate_oneLEDprops.png|200px|right]]&lt;br /&gt;
&lt;br /&gt;
==Creating a graphic==&lt;br /&gt;
* [[Creating Flowcharts|Create a new Flowcode flowchart]].&lt;br /&gt;
&lt;br /&gt;
* Make sure that the [[System Panel]] and [[Properties Panel]] are visible. &lt;br /&gt;
&lt;br /&gt;
* If they are not, then select them in the [[View]] menu.&lt;br /&gt;
&lt;br /&gt;
* Click on the hemisphere shape in the Shapes menu and drag one onto the Systems Panel.&lt;br /&gt;
&lt;br /&gt;
: [[File:Gen_Panel_Shapes_Toolbar_01.png|center|border]]&lt;br /&gt;
&lt;br /&gt;
* The blue dotted square around it shows that this object is currently selected.&lt;br /&gt;
&lt;br /&gt;
* Change the name of the component to 'oneLED'. &lt;br /&gt;
: To do this:&lt;br /&gt;
::* Find the 'handle' of the component at the top of the Panel Properties. &lt;br /&gt;
::* Click on the name 'shape' (the default name).&lt;br /&gt;
::* Change it to 'oneLED'.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Adding properties==&lt;br /&gt;
Next, add two properties to the LED. The first allocates a color. The second sets up a connection from the LED to the microcontroller.&lt;br /&gt;
&lt;br /&gt;
First add a default color to the component, using a new property called 'color'. &lt;br /&gt;
: To do this:&lt;br /&gt;
::* De-select the hemisphere by clicking anywhere outside it in the Systems Panel.&lt;br /&gt;
::* Hover over the icon to the right of the 'Properties' label.&lt;br /&gt;
::* Click on the down-arrow that appears.&lt;br /&gt;
::* Click on 'Add new'.&lt;br /&gt;
::* In the 'Cosmetic name' box type &amp;quot;LEDcolor&amp;quot;.&lt;br /&gt;
::* Select 'Color picker' for the 'Property type'.&lt;br /&gt;
::* Type &amp;quot;color&amp;quot; for the 'Property variable' name.&lt;br /&gt;
&lt;br /&gt;
In the same way, then add another new property to specify the default connection. Give it a Cosmetic name &amp;quot;Connection&amp;quot;, with Property type 'Single digital pin' and a Property variable name &amp;quot;pin&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
Finally, configure these properties. &lt;br /&gt;
: To do this:&lt;br /&gt;
::* Click on the color shown for the 'color' property.[[File:Gen_ExerciseLEDcreate_LEDcomppropsdetail_01.jpg|200px|right]]&lt;br /&gt;
::* Select a color from the color chart that appears.&lt;br /&gt;
::* Click on the word 'Unconnected', alongside the 'pin' property.&lt;br /&gt;
::* Select an appropriate pin, such as RA0, from the chip pin layout.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Reacting when the pin changes state==&lt;br /&gt;
[[File:Gen_Exercise_LEDcreate_Proj_explorer.png|200px|right]]&lt;br /&gt;
&lt;br /&gt;
This involves two macros. One, called [[Event Connection.PinChange|PinChange]], recognizes when the pin changes logic level. The second, called Property, then causes a property of the LED, in this case the color, to change. &amp;lt;br /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
First, create a 'PinChange' macro.&lt;br /&gt;
&lt;br /&gt;
* Open the [[Using the Project Explorer|Project Explorer]] from the [[View]] menu.&lt;br /&gt;
&lt;br /&gt;
* Double-click on the item 'Connection -&amp;gt; PinChange'. The 'Add event' dialogue box opens.&lt;br /&gt;
&lt;br /&gt;
* Hover over the icon to the left of the 'Macro' label. A drop-down arrow appears.&lt;br /&gt;
&lt;br /&gt;
* Click on the arrow and select the option 'Add new'. The 'Edit Macro Details' dialogue box opens.&lt;br /&gt;
&lt;br /&gt;
* Change the name of the macro to 'PinChange'.&lt;br /&gt;
&lt;br /&gt;
* Click on 'OK'.&lt;br /&gt;
&amp;lt;br /&amp;gt;&lt;br /&gt;
Next, set up the 'PinChange' macro.&lt;br /&gt;
&lt;br /&gt;
* Select 'Show as Flowchart' from the 'Macro' menu, and choose the 'PinChange' macro.&lt;br /&gt;
&lt;br /&gt;
Add the following details:&lt;br /&gt;
&lt;br /&gt;
* Add a Decision icon to the PinChange, rename it &amp;quot;Pin state&amp;quot;, and set the condition as 'If pin = 1'.&lt;br /&gt;
&lt;br /&gt;
* Drag a SIM command into the 'No' branch. Configure it as follows:&lt;br /&gt;
&lt;br /&gt;
::* Rename it &amp;quot;Switch off&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
::* Click on the 'Functions' label.&lt;br /&gt;
&lt;br /&gt;
::* Expand the 'Component' and then the 'Property' sections.&lt;br /&gt;
&lt;br /&gt;
::* Click on the SetValue command, and complete it by adding &amp;quot;oneLED&amp;quot; as the Handle, &amp;quot;color&amp;quot; (including the quotes) as the Property and 0 (zero) as the Value. Then click on 'OK'.&lt;br /&gt;
&lt;br /&gt;
* Click on the Panel command and copy and paste it into the 'Yes' branch.&lt;br /&gt;
&lt;br /&gt;
* Change the configuration as follows:&lt;br /&gt;
&lt;br /&gt;
::* Rename it &amp;quot;Switch on&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
::* Change the Value to &amp;quot;color&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
* Then click on 'OK'.&lt;br /&gt;
&amp;lt;br /&amp;gt;&lt;br /&gt;
The flowchart now resembles this. [[File:Gen exerciseLEDcreate pinchangeprog01.png|500px|centre]]&lt;br /&gt;
&lt;br /&gt;
==Updating the LED==&lt;br /&gt;
&lt;br /&gt;
When the state of the LED pin changes, you want the color of the LED to change too. This is done through the 'Component / Property' macro. This will re-use the code already created in the PinChange macro.&lt;br /&gt;
&lt;br /&gt;
* Open the [[Project Explorer]] as before.&lt;br /&gt;
&lt;br /&gt;
* Click on the 'Functions' label.&lt;br /&gt;
&lt;br /&gt;
* Expand the 'Component' section.&lt;br /&gt;
&lt;br /&gt;
* Double-click on the 'Property' command to open the 'Add event' dialogue box.&lt;br /&gt;
&lt;br /&gt;
* Click on the PinChange macro (to re-use it,) and then click on 'OK'.&lt;br /&gt;
&amp;lt;br / &amp;gt;&lt;br /&gt;
==Adding an interface==&lt;br /&gt;
[[File:Gen exerciseLEDcreate macropropsLEDoff 01.png|300px|right]]&lt;br /&gt;
&lt;br /&gt;
A component is not much use if no one can interact with it. What is needed is to create two macros, LEDon and LEDoff, which set and reset the state of the pin. This will become the ''public interface'' of the component.&lt;br /&gt;
&amp;lt;br /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
* Click on Macro in the top toolbar, and select the New option (Macro &amp;gt; New...). This opens the [[Creating a New Macro|Create a New Macro]] dialogue box.&lt;br /&gt;
&lt;br /&gt;
* Name the new macro &amp;quot;LEDoff&amp;quot;, and click on 'OK'. A new tab is created on the Flowchart workspace.&lt;br /&gt;
: Set it up as follows:&lt;br /&gt;
::* Drag a [[Calculation Icon Properties|Calculation]] icon into the macro.&lt;br /&gt;
&lt;br /&gt;
::* Double-click on it and re-name it &amp;quot;Reset pin&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
::* In the calculation area, type &amp;quot;pin=0&amp;quot;, and click 'OK'&lt;br /&gt;
&lt;br /&gt;
* Create the second macro in the same way. This one is called LEDon. It contains a calculation icon, called &amp;quot;Set pin&amp;quot; and the calculation &amp;quot;pin=1&amp;quot;.&lt;br /&gt;
&amp;lt;br /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==What next?==&lt;br /&gt;
The next stage in the process is to [[Exercise - Exporting the LED Component|export the component]].&lt;/div&gt;</summary>
		<author><name>ReeceL</name></author>
		
	</entry>
	<entry>
		<id>https://www.flowcode.co.uk/wiki/index.php?title=Exercise_-_Create_an_LED_Component&amp;diff=12224</id>
		<title>Exercise - Create an LED Component</title>
		<link rel="alternate" type="text/html" href="https://www.flowcode.co.uk/wiki/index.php?title=Exercise_-_Create_an_LED_Component&amp;diff=12224"/>
		<updated>2013-11-06T13:57:46Z</updated>

		<summary type="html">&lt;p&gt;ReeceL: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;sidebar&amp;gt;Sidebar: Component Exercises&amp;lt;/sidebar&amp;gt;&lt;br /&gt;
[[File:gen_exerciseLEDcreate_oneLEDprops.png|200px|right]]&lt;br /&gt;
&lt;br /&gt;
==Creating a graphic==&lt;br /&gt;
* [[Creating Flowcharts|Create a new Flowcode flowchart]].&lt;br /&gt;
&lt;br /&gt;
* Make sure that the [[System Panel]] and [[Properties Panel]] are visible. &lt;br /&gt;
&lt;br /&gt;
* If they are not, then select them in the [[View]] menu.&lt;br /&gt;
&lt;br /&gt;
* Click on the hemisphere shape in the Shapes menu and drag one onto the Systems Panel.&lt;br /&gt;
&lt;br /&gt;
: [[File:Gen_Panel_Shapes_Toolbar_01.png|center|border]]&lt;br /&gt;
&lt;br /&gt;
* The blue dotted square around it shows that this object is currently selected.&lt;br /&gt;
&lt;br /&gt;
* Change the name of the component to 'oneLED'. &lt;br /&gt;
: To do this:&lt;br /&gt;
::* Find the 'handle' of the component at the top of the Panel Properties. &lt;br /&gt;
::* Click on the name 'shape' (the default name).&lt;br /&gt;
::* Change it to 'oneLED'.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Adding properties==&lt;br /&gt;
Next, add two properties to the LED. The first allocates a color. The second sets up a connection from the LED to the microcontroller.&lt;br /&gt;
&lt;br /&gt;
First add a default color to the component, using a new property called 'color'. &lt;br /&gt;
: To do this:&lt;br /&gt;
::* De-select the hemisphere by clicking anywhere outside it in the Systems Panel.&lt;br /&gt;
::* Hover over the icon to the right of the 'Properties' label.&lt;br /&gt;
::* Click on the down-arrow that appears.&lt;br /&gt;
::* Click on 'Add new'.&lt;br /&gt;
::* In the 'Cosmetic name' box type &amp;quot;LEDcolor&amp;quot;.&lt;br /&gt;
::* Select 'Color picker' for the 'Property type'.&lt;br /&gt;
::* Type &amp;quot;color&amp;quot; for the 'Property variable' name.&lt;br /&gt;
&lt;br /&gt;
In the same way, then add another new property to specify the default connection. Give it a Cosmetic name &amp;quot;Connection&amp;quot;, with Property type 'Single digital pin' and a Property variable name &amp;quot;pin&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
Finally, configure these properties. &lt;br /&gt;
: To do this:&lt;br /&gt;
::* Click on the color shown for the 'color' property.[[File:Gen_ExerciseLEDcreate_LEDcomppropsdetail_01.jpg|200px|right]]&lt;br /&gt;
::* Select a color from the color chart that appears.&lt;br /&gt;
::* Click on the word 'Unconnected', alongside the 'pin' property.&lt;br /&gt;
::* Select an appropriate pin, such as RA0, from the chip pin layout.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Reacting when the pin changes state==&lt;br /&gt;
[[File:Gen_Exercise_LEDcreate_Proj_explorer.png|200px|right]]&lt;br /&gt;
&lt;br /&gt;
This involves two macros. One, called [[Event Connection.PinChange|PinChange]], recognizes when the pin changes logic level. The second, called Property, then causes a property of the LED, in this case the color, to change. &amp;lt;br /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
First, create a 'PinChange' macro.&lt;br /&gt;
&lt;br /&gt;
* Open the [[Using the Project Explorer|Project Explorer]] from the [[View]] menu.&lt;br /&gt;
&lt;br /&gt;
* Double-click on the item 'Connection -&amp;gt; PinChange'. The 'Add event' dialogue box opens.&lt;br /&gt;
&lt;br /&gt;
* Hover over the icon to the left of the 'Macro' label. A drop-down arrow appears.&lt;br /&gt;
&lt;br /&gt;
* Click on the arrow and select the option 'Add new'. The 'Edit Macro Details' dialogue box opens.&lt;br /&gt;
&lt;br /&gt;
* Change the name of the macro to 'PinChange'.&lt;br /&gt;
&lt;br /&gt;
* Click on 'OK'.&lt;br /&gt;
&amp;lt;br /&amp;gt;&lt;br /&gt;
Next, set up the 'PinChange' macro.&lt;br /&gt;
&lt;br /&gt;
* Select 'Show as Flowchart' from the 'Macro' menu, and choose the 'PinChange' macro.&lt;br /&gt;
&lt;br /&gt;
Add the following details:&lt;br /&gt;
&lt;br /&gt;
* Add a Decision icon to the PinChange, rename it &amp;quot;Pin state&amp;quot;, and set the condition as 'If pin = 1'.&lt;br /&gt;
&lt;br /&gt;
* Drag a SIM command into the 'No' branch. Configure it as follows:&lt;br /&gt;
&lt;br /&gt;
::* Rename it &amp;quot;Switch off&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
::* Click on the 'Functions' label.&lt;br /&gt;
&lt;br /&gt;
::* Expand the 'Component' and then the 'Property' sections.&lt;br /&gt;
&lt;br /&gt;
::* Click on the SetValue command, and complete it by adding &amp;quot;oneLED&amp;quot; as the Handle, &amp;quot;color&amp;quot; (including the quotes) as the Property and 0 (zero) as the Value. Then click on 'OK'.&lt;br /&gt;
&lt;br /&gt;
* Click on the Panel command and copy and paste it into the 'Yes' branch.&lt;br /&gt;
&lt;br /&gt;
* Change the configuration as follows:&lt;br /&gt;
&lt;br /&gt;
::* Rename it &amp;quot;Switch on&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
::* Change the Value to &amp;quot;color&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
* Then click on 'OK'.&lt;br /&gt;
&amp;lt;br /&amp;gt;&lt;br /&gt;
The flowchart now resembles this. [[File:Gen exerciseLEDcreate pinchangeprog01.png|500px|centre]]&lt;br /&gt;
&lt;br /&gt;
==Updating the LED==&lt;br /&gt;
&lt;br /&gt;
When the state of the LED pin changes, you want the color of the LED to change too. This is done through the 'Component / Property' macro. This will re-use the code already created in the PinChange macro.&lt;br /&gt;
&lt;br /&gt;
* Open the [[Project Explorer]] as before.&lt;br /&gt;
&lt;br /&gt;
* Click on the 'Functions' label.&lt;br /&gt;
&lt;br /&gt;
* Expand the 'Component' section.&lt;br /&gt;
&lt;br /&gt;
* Double-click on the 'Property' command to open the 'Add event' dialogue box.&lt;br /&gt;
&lt;br /&gt;
* Click on the PinChange macro (to re-use it,) and then click on 'OK'.&lt;br /&gt;
&amp;lt;br / &amp;gt;&lt;br /&gt;
==Adding an interface==&lt;br /&gt;
[[File:Gen exerciseLEDcreate macropropsLEDoff 01.png|300px|right]]&lt;br /&gt;
&lt;br /&gt;
A component is not much use if no one can interact with it. What is needed is to create two macros, LEDon and LEDoff, which set and reset the state of the pin. This will become the ''public interface'' of the component.&lt;br /&gt;
&amp;lt;br /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
* Click on Macro in the top toolbar, and select the New option (Macro &amp;gt; New...). This opens the [[Creating a New Macro|Create a New Macro]] dialogue box.&lt;br /&gt;
&lt;br /&gt;
* Name the new macro &amp;quot;LEDoff&amp;quot;, and click on 'OK'. A new tab is created on the Flowchart workspace.&lt;br /&gt;
: Set it up as follows:&lt;br /&gt;
::* Drag a [[Calculation Icon Properties|Calculation]] icon into the macro.&lt;br /&gt;
&lt;br /&gt;
::* Double-click on it and re-name it &amp;quot;Reset pin&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
::* In the calculation area, type &amp;quot;pin=0&amp;quot;, and click 'OK'&lt;br /&gt;
&lt;br /&gt;
* Create the second macro in the same way. This one is called LEDon. It contains a calculation icon, called &amp;quot;Set pin&amp;quot; and the calculation &amp;quot;pin=1&amp;quot;.&lt;br /&gt;
&amp;lt;br /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==What next?==&lt;br /&gt;
The next stage in the process is to [[Exercise - Exporting the LED Component|export the component]].&lt;/div&gt;</summary>
		<author><name>ReeceL</name></author>
		
	</entry>
	<entry>
		<id>https://www.flowcode.co.uk/wiki/index.php?title=Sidebar:_What_Is_a_Component%3F&amp;diff=12223</id>
		<title>Sidebar: What Is a Component?</title>
		<link rel="alternate" type="text/html" href="https://www.flowcode.co.uk/wiki/index.php?title=Sidebar:_What_Is_a_Component%3F&amp;diff=12223"/>
		<updated>2013-11-06T13:51:56Z</updated>

		<summary type="html">&lt;p&gt;ReeceL: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;* navigation&lt;br /&gt;
** mainpage|mainpage-description&lt;br /&gt;
** portal-url|portal&lt;br /&gt;
** Migrating_to_V6|Migrating to v6&lt;br /&gt;
** Flowcode_Help_Overview|Flowcode Basics&lt;br /&gt;
** Components|Component Help&lt;br /&gt;
** Event_Reference|Simulation Events&lt;br /&gt;
** API_Overview|Simulation API&lt;br /&gt;
** Exercises|Exercises&lt;br /&gt;
** Feature_List|Features&lt;br /&gt;
** Concepts|Concepts&lt;br /&gt;
** Frequently_Asked_Questions|FAQs&lt;br /&gt;
*SEARCH&lt;br /&gt;
*What Is a Component?&lt;br /&gt;
**What Is a Component? | What Is a Component?&lt;br /&gt;
**Exercise - Using Analogue Input Devices | Using Analogue Input Devices&lt;br /&gt;
**Analog Window | Analog Window&lt;br /&gt;
**Editing Key Mappings | Editing Key Mappings&lt;br /&gt;
**What Is a Switch? | What Is a Switch?&lt;br /&gt;
**What Is an LED? | What Is an LED?&lt;br /&gt;
**What Is an LCD? | What Is an LCD?	&lt;br /&gt;
**What Is a 7 Segment Display? | What Is a 7 Segment Display?&lt;br /&gt;
**What Is a Keypad? | What Is a Keypad?	&lt;br /&gt;
*TOOLBOX&lt;br /&gt;
*LANGUAGES&lt;br /&gt;
&lt;br /&gt;
[[Category:Sidebar]]&lt;/div&gt;</summary>
		<author><name>ReeceL</name></author>
		
	</entry>
	<entry>
		<id>https://www.flowcode.co.uk/wiki/index.php?title=Phase_Locked_Loop&amp;diff=12221</id>
		<title>Phase Locked Loop</title>
		<link rel="alternate" type="text/html" href="https://www.flowcode.co.uk/wiki/index.php?title=Phase_Locked_Loop&amp;diff=12221"/>
		<updated>2013-11-06T13:47:38Z</updated>

		<summary type="html">&lt;p&gt;ReeceL: Redirected page to Phase Locked Loop (PLL)&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;#REDIRECT [[Phase Locked Loop (PLL)]]&lt;/div&gt;</summary>
		<author><name>ReeceL</name></author>
		
	</entry>
	<entry>
		<id>https://www.flowcode.co.uk/wiki/index.php?title=Main_Page&amp;diff=11958</id>
		<title>Main Page</title>
		<link rel="alternate" type="text/html" href="https://www.flowcode.co.uk/wiki/index.php?title=Main_Page&amp;diff=11958"/>
		<updated>2013-10-22T10:12:06Z</updated>

		<summary type="html">&lt;p&gt;ReeceL: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{| cellpadding=&amp;quot;4&amp;quot; style=&amp;quot;border: 1px solid darkgray; float:right; width:30%&amp;quot;&lt;br /&gt;
|+ '''Flowcode 6'''&lt;br /&gt;
|-&lt;br /&gt;
| colspan=&amp;quot;2&amp;quot;|[[File:FC6_Icon.png|center]]&lt;br /&gt;
|-&lt;br /&gt;
| colspan=&amp;quot;2&amp;quot;|[[File:FC6_Box_Cover.jpg|center]]&lt;br /&gt;
|-&lt;br /&gt;
|width=&amp;quot;40%&amp;quot;|'''Developer'''&lt;br /&gt;
|[http://matrixmultimedia.com Matrix Multimedia]&lt;br /&gt;
|-&lt;br /&gt;
|'''Initial release'''&lt;br /&gt;
|3rd September 2013&lt;br /&gt;
|-&lt;br /&gt;
|'''Development status'''&lt;br /&gt;
|Active&lt;br /&gt;
|-&lt;br /&gt;
|'''Written in'''&lt;br /&gt;
|C++&lt;br /&gt;
|-&lt;br /&gt;
|'''Operating system'''&lt;br /&gt;
|[http://en.wikipedia.org/wiki/Windows_XP Windows XP]&lt;br /&gt;
&lt;br /&gt;
[http://en.wikipedia.org/wiki/Windows_Vista Windows Vista]&lt;br /&gt;
&lt;br /&gt;
[http://en.wikipedia.org/wiki/Windows_7 Windows 7]&lt;br /&gt;
&lt;br /&gt;
[http://en.wikipedia.org/wiki/Windows_8 Windows 8]&lt;br /&gt;
|-&lt;br /&gt;
|'''Platform'''&lt;br /&gt;
| [http://en.wikipedia.org/wiki/IA-32 IA-32] and [http://en.wikipedia.org/wiki/X86-64 x86-64]&lt;br /&gt;
|-&lt;br /&gt;
|'''Available in'''&lt;br /&gt;
|Over 20 languages&lt;br /&gt;
|-&lt;br /&gt;
|'''Type'''&lt;br /&gt;
|Advanced graphical programming software&lt;br /&gt;
|-&lt;br /&gt;
|'''License'''&lt;br /&gt;
|[http://en.wikipedia.org/wiki/Proprietary_software Proprietary]&lt;br /&gt;
|-&lt;br /&gt;
|'''Predecessor'''&lt;br /&gt;
|Flowcode 5&lt;br /&gt;
|-&lt;br /&gt;
|'''Website'''&lt;br /&gt;
|[http://www.matrixmultimedia.com www.matrixmultimedia.com]&lt;br /&gt;
|-&lt;br /&gt;
|'''Blog site'''&lt;br /&gt;
|[http://www.matrixmultimedia.com/blog www.matrixmultimedia.com/blog]&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
Welcome to the Matrix Multimedia wiki, here you can find out and learn all you need to know about Flowcode 6 (and more!), from easy to follow exercises such as creating and saving a flowchart to technical API functions.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
From this page you can navigate the wiki and follow the base learning structure which has been set in place for your benefit, you can also search for articles to find out specific functions or components for useful information to help you get the most out of Flowcode 6.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
There are links to our '''[http://www.youtube.com/playlist?list=PLQDWBb7bxuCgg6aJgPJcfXBMzZdLILceQ official Youtube videos]''' throughout the wiki to help you learn about Flowcode, these videos are a few minutes (1 minute - 4 minutes) long and show you how to use features and functionality in Flowcode, these resources are very useful and can help you further understand Flowcode.&lt;br /&gt;
&lt;br /&gt;
These videos can also be found on the [http://www.matrixmultimedia.com/flowcode_help/help_videos.php Flowcode Help Videos] page at the [http://www.matrixmultimedia.com Matrix Multimedia website].&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
For more information about Flowcode as well as news, announcements and events including our general activity at Matrix see our blog site [http://www.matrixmultimedia.com/blog www.matrixmultimedia.com/blog], which is updated regularly and consists of various articles from different staff, from information and events in the new building to new additions to the team as well as new projects and applications.&lt;br /&gt;
&amp;lt;br /&amp;gt;__NOTOC__&amp;lt;br /&amp;gt;&lt;br /&gt;
==Flowcode Help==&lt;br /&gt;
&lt;br /&gt;
===[[Flowcode Help Overview|Flowcode Help]]===&lt;br /&gt;
Learn how to use Flowcode 6 and participate in practical exercises to improve your skills and knowledge of Flowcode. This explains the basics of Flowcode and how to use it effectively and efficiently. All users should at least skim through this section to learn about new features and methods integrated into Flowcode 6. New users are advised to start here to learn Flowcode from the base up.&lt;br /&gt;
&lt;br /&gt;
===[[Exercises]]===&lt;br /&gt;
List of all exercises including the exercises used in [[Flowcode Help Overview|Flowcode Help]] section as well as additional exercises to further improve your skills, the exercises are set in a practical and informative structure. Advanced users can start here and use these exercises to familiarize themselves with the new interface, features and functionality.&lt;br /&gt;
&lt;br /&gt;
===[[Feature List]]===&lt;br /&gt;
This section lists the articles about features in Flowcode 6 which are structured into the [[Flowcode Help Overview|Flowcode Help]] section so you can easily find information on specific features and learn how to use them effectively and efficiently. This section helps accompany other content to provide extra information to help you use the features correctly and understand them enough to use them to their full potential.&lt;br /&gt;
&lt;br /&gt;
===[[Concepts]]===&lt;br /&gt;
Complex methods, techniques and functionality used in Flowcode explained in a robust and practical manner, with reference to conventions used outside of Flowcode as well as information linking to functionality directly integrated within Flowcode. &lt;br /&gt;
&lt;br /&gt;
'''''Note: the Concepts section contains complicated articles intended for advanced users and complex component creation.'''''&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Technical Help==&lt;br /&gt;
&lt;br /&gt;
===[[Migrating to V6]]===&lt;br /&gt;
A mix of important information for migrating/upgrading from version 5 to version 6 of Flowcode including practical changes such as the positioning of components on the panels, technical changes such as the software &amp;amp; hardware channel selection changes and other information e.g. a table listing the status of component migration to Flowcode 6.&lt;br /&gt;
&lt;br /&gt;
===[[Components]]===&lt;br /&gt;
List of components which provide detailed information about individual components as well as examples of them in use, the information provided includes component and simulation macro references as well as property references and component functionality.&lt;br /&gt;
&lt;br /&gt;
===[[Event Reference]]===&lt;br /&gt;
Structured overview of Events providing technical information for individual functions, each article contains information of the parameters and return value, a detailed description and an example of the Event.&lt;br /&gt;
&lt;br /&gt;
===[[API Overview]]===&lt;br /&gt;
''See also [[API Reference]]''&lt;br /&gt;
&lt;br /&gt;
Structured overview of Simulation API explaining individual functions and technical information, the [[API Reference|API reference]] page also provides a similar purpose although in a more open and expanded list to show each individual function under its class.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===[[Frequently Asked Questions]]===&lt;br /&gt;
Frequently asked questions (FAQ) regarding Flowcode 6, including changes from version 5, new features and altered functionality. Commonly asked questions feature general information regarding component properties, local, constant and global variables and exporting macros.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Consult the [//meta.wikimedia.org/wiki/Help:Contents User's Guide] for information on using the wiki software.&lt;br /&gt;
&lt;br /&gt;
* [//www.mediawiki.org/wiki/Manual:Configuration_settings Configuration settings list]&lt;br /&gt;
* [//www.mediawiki.org/wiki/Manual:FAQ MediaWiki FAQ]&lt;br /&gt;
* [https://lists.wikimedia.org/mailman/listinfo/mediawiki-announce MediaWiki release mailing list]&lt;/div&gt;</summary>
		<author><name>ReeceL</name></author>
		
	</entry>
	<entry>
		<id>https://www.flowcode.co.uk/wiki/index.php?title=Main_Page&amp;diff=11957</id>
		<title>Main Page</title>
		<link rel="alternate" type="text/html" href="https://www.flowcode.co.uk/wiki/index.php?title=Main_Page&amp;diff=11957"/>
		<updated>2013-10-22T09:08:16Z</updated>

		<summary type="html">&lt;p&gt;ReeceL: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{| cellpadding=&amp;quot;4&amp;quot; style=&amp;quot;border: 1px solid darkgray; float:right; width:30%&amp;quot;&lt;br /&gt;
|+ '''Flowcode 6'''&lt;br /&gt;
|-&lt;br /&gt;
| colspan=&amp;quot;2&amp;quot;|[[File:FC6_Icon.png|center]]&lt;br /&gt;
|-&lt;br /&gt;
| colspan=&amp;quot;2&amp;quot;|[[File:FC6_Box_Cover.jpg|center]]&lt;br /&gt;
|-&lt;br /&gt;
|width=&amp;quot;40%&amp;quot;|'''Developer'''&lt;br /&gt;
|[http://matrixmultimedia.com Matrix Multimedia]&lt;br /&gt;
|-&lt;br /&gt;
|'''Initial release'''&lt;br /&gt;
|3rd September 2013&lt;br /&gt;
|-&lt;br /&gt;
|'''Development status'''&lt;br /&gt;
|Active&lt;br /&gt;
|-&lt;br /&gt;
|'''Written in'''&lt;br /&gt;
|C++&lt;br /&gt;
|-&lt;br /&gt;
|'''Operating system'''&lt;br /&gt;
|[http://en.wikipedia.org/wiki/Windows_XP Windows XP]&lt;br /&gt;
&lt;br /&gt;
[http://en.wikipedia.org/wiki/Windows_Vista Windows Vista]&lt;br /&gt;
&lt;br /&gt;
[http://en.wikipedia.org/wiki/Windows_7 Windows 7]&lt;br /&gt;
&lt;br /&gt;
[http://en.wikipedia.org/wiki/Windows_8 Windows 8]&lt;br /&gt;
|-&lt;br /&gt;
|'''Platform'''&lt;br /&gt;
| [http://en.wikipedia.org/wiki/IA-32 IA-32] and [http://en.wikipedia.org/wiki/X86-64 x86-64]&lt;br /&gt;
|-&lt;br /&gt;
|'''Available in'''&lt;br /&gt;
|Over 20 languages&lt;br /&gt;
|-&lt;br /&gt;
|'''Type'''&lt;br /&gt;
|Advanced graphical programming software&lt;br /&gt;
|-&lt;br /&gt;
|'''License'''&lt;br /&gt;
|[http://en.wikipedia.org/wiki/Proprietary_software Proprietary]&lt;br /&gt;
|-&lt;br /&gt;
|'''Predecessor'''&lt;br /&gt;
|Flowcode 5&lt;br /&gt;
|-&lt;br /&gt;
|'''Website'''&lt;br /&gt;
|[http://www.matrixmultimedia.com www.matrixmultimedia.com]&lt;br /&gt;
|-&lt;br /&gt;
|'''Blog site'''&lt;br /&gt;
|[http://www.flowcode.co.uk www.flowcode.co.uk]&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
Welcome to the Matrix Multimedia wiki, here you can find out and learn all you need to know about Flowcode 6 (and more!), from easy to follow exercises such as creating and saving a flowchart to technical API functions.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
From this page you can navigate the wiki and follow the base learning structure which has been set in place for your benefit, you can also search for articles to find out specific functions or components for useful information to help you get the most out of Flowcode 6.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
There are links to our '''[http://www.youtube.com/playlist?list=PLQDWBb7bxuCgg6aJgPJcfXBMzZdLILceQ official Youtube videos]''' throughout the wiki to help you learn about Flowcode, these videos are a few minutes (1 minute - 4 minutes) long and show you how to use features and functionality in Flowcode, these resources are very useful and can help you further understand Flowcode.&lt;br /&gt;
&lt;br /&gt;
These videos can also be found on the [http://www.matrixmultimedia.com/flowcode_help/help_videos.php Flowcode Help Videos] page at the [http://www.matrixmultimedia.com Matrix Multimedia website].&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
For more information about Flowcode as well as news, announcements and events including our general activity at Matrix see our blog site [http://flowcode.co.uk www.flowcode.co.uk], which is updated regularly and consists of various articles from different staff, from information and events in the new building to new additions to the team as well as new projects and applications.&lt;br /&gt;
&amp;lt;br /&amp;gt;__NOTOC__&amp;lt;br /&amp;gt;&lt;br /&gt;
==Flowcode Help==&lt;br /&gt;
&lt;br /&gt;
===[[Flowcode Help Overview|Flowcode Help]]===&lt;br /&gt;
Learn how to use Flowcode 6 and participate in practical exercises to improve your skills and knowledge of Flowcode. This explains the basics of Flowcode and how to use it effectively and efficiently. All users should at least skim through this section to learn about new features and methods integrated into Flowcode 6. New users are advised to start here to learn Flowcode from the base up.&lt;br /&gt;
&lt;br /&gt;
===[[Exercises]]===&lt;br /&gt;
List of all exercises including the exercises used in [[Flowcode Help Overview|Flowcode Help]] section as well as additional exercises to further improve your skills, the exercises are set in a practical and informative structure. Advanced users can start here and use these exercises to familiarize themselves with the new interface, features and functionality.&lt;br /&gt;
&lt;br /&gt;
===[[Feature List]]===&lt;br /&gt;
This section lists the articles about features in Flowcode 6 which are structured into the [[Flowcode Help Overview|Flowcode Help]] section so you can easily find information on specific features and learn how to use them effectively and efficiently. This section helps accompany other content to provide extra information to help you use the features correctly and understand them enough to use them to their full potential.&lt;br /&gt;
&lt;br /&gt;
===[[Concepts]]===&lt;br /&gt;
Complex methods, techniques and functionality used in Flowcode explained in a robust and practical manner, with reference to conventions used outside of Flowcode as well as information linking to functionality directly integrated within Flowcode. &lt;br /&gt;
&lt;br /&gt;
'''''Note: the Concepts section contains complicated articles intended for advanced users and complex component creation.'''''&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Technical Help==&lt;br /&gt;
&lt;br /&gt;
===[[Migrating to V6]]===&lt;br /&gt;
A mix of important information for migrating/upgrading from version 5 to version 6 of Flowcode including practical changes such as the positioning of components on the panels, technical changes such as the software &amp;amp; hardware channel selection changes and other information e.g. a table listing the status of component migration to Flowcode 6.&lt;br /&gt;
&lt;br /&gt;
===[[Components]]===&lt;br /&gt;
List of components which provide detailed information about individual components as well as examples of them in use, the information provided includes component and simulation macro references as well as property references and component functionality.&lt;br /&gt;
&lt;br /&gt;
===[[Event Reference]]===&lt;br /&gt;
Structured overview of Events providing technical information for individual functions, each article contains information of the parameters and return value, a detailed description and an example of the Event.&lt;br /&gt;
&lt;br /&gt;
===[[API Overview]]===&lt;br /&gt;
''See also [[API Reference]]''&lt;br /&gt;
&lt;br /&gt;
Structured overview of Simulation API explaining individual functions and technical information, the [[API Reference|API reference]] page also provides a similar purpose although in a more open and expanded list to show each individual function under its class.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===[[Frequently Asked Questions]]===&lt;br /&gt;
Frequently asked questions (FAQ) regarding Flowcode 6, including changes from version 5, new features and altered functionality. Commonly asked questions feature general information regarding component properties, local, constant and global variables and exporting macros.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Consult the [//meta.wikimedia.org/wiki/Help:Contents User's Guide] for information on using the wiki software.&lt;br /&gt;
&lt;br /&gt;
* [//www.mediawiki.org/wiki/Manual:Configuration_settings Configuration settings list]&lt;br /&gt;
* [//www.mediawiki.org/wiki/Manual:FAQ MediaWiki FAQ]&lt;br /&gt;
* [https://lists.wikimedia.org/mailman/listinfo/mediawiki-announce MediaWiki release mailing list]&lt;/div&gt;</summary>
		<author><name>ReeceL</name></author>
		
	</entry>
	<entry>
		<id>https://www.flowcode.co.uk/wiki/index.php?title=Compiler_Settings&amp;diff=11956</id>
		<title>Compiler Settings</title>
		<link rel="alternate" type="text/html" href="https://www.flowcode.co.uk/wiki/index.php?title=Compiler_Settings&amp;diff=11956"/>
		<updated>2013-10-21T16:00:24Z</updated>

		<summary type="html">&lt;p&gt;ReeceL: Redirected page to Managing Compiler Options&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;#REDIRECT [[Managing Compiler Options]]&lt;/div&gt;</summary>
		<author><name>ReeceL</name></author>
		
	</entry>
	<entry>
		<id>https://www.flowcode.co.uk/wiki/index.php?title=Compiler_Settings&amp;diff=11955</id>
		<title>Compiler Settings</title>
		<link rel="alternate" type="text/html" href="https://www.flowcode.co.uk/wiki/index.php?title=Compiler_Settings&amp;diff=11955"/>
		<updated>2013-10-21T16:00:15Z</updated>

		<summary type="html">&lt;p&gt;ReeceL: Created page with &amp;quot;REDIRECT Managing Compiler Options&amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;REDIRECT [[Managing Compiler Options]]&lt;/div&gt;</summary>
		<author><name>ReeceL</name></author>
		
	</entry>
	<entry>
		<id>https://www.flowcode.co.uk/wiki/index.php?title=Compiler_Options&amp;diff=11954</id>
		<title>Compiler Options</title>
		<link rel="alternate" type="text/html" href="https://www.flowcode.co.uk/wiki/index.php?title=Compiler_Options&amp;diff=11954"/>
		<updated>2013-10-21T16:00:00Z</updated>

		<summary type="html">&lt;p&gt;ReeceL: Redirected page to Managing Compiler Options&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;#REDIRECT [[Managing Compiler Options]]&lt;/div&gt;</summary>
		<author><name>ReeceL</name></author>
		
	</entry>
	<entry>
		<id>https://www.flowcode.co.uk/wiki/index.php?title=Compiler_Options&amp;diff=11953</id>
		<title>Compiler Options</title>
		<link rel="alternate" type="text/html" href="https://www.flowcode.co.uk/wiki/index.php?title=Compiler_Options&amp;diff=11953"/>
		<updated>2013-10-21T15:59:45Z</updated>

		<summary type="html">&lt;p&gt;ReeceL: Redirected page to Managing Compiler Settings&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;#REDIRECT [[Managing Compiler Settings]]&lt;/div&gt;</summary>
		<author><name>ReeceL</name></author>
		
	</entry>
	<entry>
		<id>https://www.flowcode.co.uk/wiki/index.php?title=Using_the_Data_Injector&amp;diff=11952</id>
		<title>Using the Data Injector</title>
		<link rel="alternate" type="text/html" href="https://www.flowcode.co.uk/wiki/index.php?title=Using_the_Data_Injector&amp;diff=11952"/>
		<updated>2013-10-08T15:59:20Z</updated>

		<summary type="html">&lt;p&gt;ReeceL: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;sidebar&amp;gt;Sidebar: Advanced Features&amp;lt;/sidebar&amp;gt;&lt;br /&gt;
Some of the more common communications based components have an inbuilt option to use a data injector component to allow the external portion of the communications bus to be simulated. The data injectors are designed to replicate the functionality of a specific external interface without adding anything to the downloadable code sent to the embedded device. This allows you to fully test out your program in simulation before downloading your code to the black box which is the embedded device.&lt;br /&gt;
&lt;br /&gt;
[[File:Injector.png|center]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The current data injectors packaged with Flowcode include.&lt;br /&gt;
:*[[Component: ID cc936c18 5d20 42c4 b940 d3c7ea7ca802|Injector Base]] - An empty injector used to create placeholders in communications components which can then be replaced with an actual injector once the component is exported.&lt;br /&gt;
:*[[Component: ID 5a237757 52e5 414b b6e4 79c7b784c3ba|AT Injector]] - A simple AT command based injector which will wait for a carriage return and then echo back any data it received along with an OK response.&lt;br /&gt;
:*[[Component: ID 299cb595 3e6f 4022 a728 b9df1434262c|CAN Injector]] - A means of decoding CAN ID's by referring to an external CSV file containing data in the format ID,DecodeString\n.&lt;br /&gt;
:*[[Component: ID 8d670813-9a40-4891-accc-c1bf864b8217|DS1307 Injector]] - A simple I2C device compromising of a real time clock based on the PC system time and a section of user memory which can be accessed.&lt;br /&gt;
:*[[Component: ID c6d16a4d a800 4636 98c5 70f7bde65654|GPS Injector]] - A means of dynamically adding NMEA type GPS message data into a component.&lt;br /&gt;
:*[[Component: ID 2ed54982 ef92 4509 a67c 7b3a72f91279|Human Interface Injector]] - A means of allowing direct data input and data queuing from a keyboard, similar to the v5 RS232/I2C component functionality.&lt;br /&gt;
:*[[Component: ID b81ab4d7 be8f 4ddd b5dc 937bda03dc82|Vnet Injector]] - A means of passing communications to other Flowcode nodes or other devices using TCP-IP style network messages.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The Vnet injector can be used to pass data between several instances of Flowcode running on a single machine or across a network.&lt;br /&gt;
&lt;br /&gt;
[[File:InjectorVnet.png|center]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Custom injectors can be created to allow almost any external device to be simulated and tested.&lt;br /&gt;
&lt;br /&gt;
More details of how to do this are available from the user forums: [http://www.matrixmultimedia.com/mmforums/viewtopic.php?f=58&amp;amp;t=12727 Creating Custom Injectors].&lt;/div&gt;</summary>
		<author><name>ReeceL</name></author>
		
	</entry>
	<entry>
		<id>https://www.flowcode.co.uk/wiki/index.php?title=Compiling_a_Flowchart_to_a_Chip&amp;diff=11930</id>
		<title>Compiling a Flowchart to a Chip</title>
		<link rel="alternate" type="text/html" href="https://www.flowcode.co.uk/wiki/index.php?title=Compiling_a_Flowchart_to_a_Chip&amp;diff=11930"/>
		<updated>2013-09-24T08:03:30Z</updated>

		<summary type="html">&lt;p&gt;ReeceL: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;sidebar&amp;gt;Sidebar: Adding Finishing Touches&amp;lt;/sidebar&amp;gt;&lt;br /&gt;
Chips can only execute code that is in hexadecimal (hex.) format. Flowcode needs to process your flowcharts (for example TEST.FCF) into a format that a chip can execute Flowcode takes a number of steps:&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
1) Compile Flowchart into C code&lt;br /&gt;
&lt;br /&gt;
2) Compile C code into Assembler &lt;br /&gt;
&lt;br /&gt;
3) Assemble the Assembler into Hex&lt;br /&gt;
&lt;br /&gt;
4) Send the Hex code to the chip&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Whilst this seems a bit long-winded it has the advantage that it allows you to embed third party C code or Assembly code into your programs without actually getting too bogged down in creating the code - or understanding it.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The various options available allow users to halt the process at various stages so that they can view the resulting code, or check for errors at that code level.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Before compiling your flowchart into a program that can be sent to a chip you will need to ensure you have followed the instructions in the section entitled [[Selecting a Target Chip]].&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Compile to C==&lt;br /&gt;
&lt;br /&gt;
Compiles the Flowchart to C code.&lt;br /&gt;
&lt;br /&gt;
The resulting C file is saved in the program directory, with a .c extension, and can be viewed or used by external programs.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Select the 'Compile to C' option from the 'Build' menu (Build &amp;gt; Compile to C...).&lt;br /&gt;
&lt;br /&gt;
Flowcharts must be saved before they can be transferred and Flowcode will prompt you if this is the case.&lt;br /&gt;
&lt;br /&gt;
You can also use the 'Compile to C' [[File:Btn_Compile_C.png|border]] icon on the toolbar.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Compile to Hex==&lt;br /&gt;
&lt;br /&gt;
Compiles the Flowchart to C code and then compiles the C code to Assembly and Machine code.&lt;br /&gt;
&lt;br /&gt;
The resulting ASM file is saved in the program directory, with a .asm or .s extension, and can be viewed or used by external programs.&lt;br /&gt;
&lt;br /&gt;
The resulting machine code file is also saved in the program directory with a .hex, .s19 or .bin extension.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Select the 'Compile to HEX' option from the 'Build' menu (Build &amp;gt; Compile to HEX...). &lt;br /&gt;
&lt;br /&gt;
Flowcharts must be saved before they can be transferred and Flowcode will prompt you if this is the case.&lt;br /&gt;
&lt;br /&gt;
You can also use the 'Compile to HEX' [[File:Btn_Compile_Hex.png|border]] icon on the toolbar.&lt;br /&gt;
&lt;br /&gt;
If the program has already been compiled and the flowchart has not been edited then you can force a re-compilation by holding down the left shift button while clicking the 'Compile to HEX' icon on the toolbar.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Compiling to Chip==&lt;br /&gt;
&lt;br /&gt;
Unlike the previous two methods Compile to chip actually programs the chip after compiling the machine code file.&lt;br /&gt;
&lt;br /&gt;
Compile to chip compiles the Flowchart to C code, then ASM code, then assembles the ASM to Machine code and launches the Programmer application to download the program into the chip.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Select the 'Compile to Chip' option from the 'Build' menu (Build &amp;gt; Compile to Chip...) to transfer the flowchart to the target microcontroller. &lt;br /&gt;
&lt;br /&gt;
Flowcharts must be saved before they can be transferred and Flowcode will prompt you if this is the case.&lt;br /&gt;
&lt;br /&gt;
You can also use the 'Compile to Chip' [[File:Btn_Compile_Chip.png|border]] icon on the toolbar.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Please check your Configuration information before downloading, or if you are having problems: Many perceived errors are as a result of the incorrect set up.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
====Compiler errors====&lt;br /&gt;
&lt;br /&gt;
If the compiler detects any errors during compilation, these errors will be displayed within the [[Using the Icon Lists Pane|Icon Lists]] panel.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
If the program has already been successfully compiled and the flowchart has not been edited then clicking the 'Compile to Chip' [[File:Btn_Compile_Chip.png|border]] icon on the toolbar will skip the compilation stage and go directly to programming the device allowing multiple devices to be programmed.&lt;br /&gt;
&lt;br /&gt;
You can force a re-compilation by holding down the left '''Shift''' button while clicking the 'Compile to Chip' [[File:Btn_Compile_Chip.png|border]] icon on the toolbar.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
====Compiling with non standard applications====&lt;br /&gt;
&lt;br /&gt;
Flowcode is optimized for use with the Boost C or HiTech compiler (PIC) and GCC compilers (PIC16, AVR, ARM). The C code generated may not be appropriate for other compilers.&lt;/div&gt;</summary>
		<author><name>ReeceL</name></author>
		
	</entry>
	<entry>
		<id>https://www.flowcode.co.uk/wiki/index.php?title=Using_the_Data_Recorder&amp;diff=11929</id>
		<title>Using the Data Recorder</title>
		<link rel="alternate" type="text/html" href="https://www.flowcode.co.uk/wiki/index.php?title=Using_the_Data_Recorder&amp;diff=11929"/>
		<updated>2013-09-23T15:11:04Z</updated>

		<summary type="html">&lt;p&gt;ReeceL: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;sidebar&amp;gt;Sidebar: What Is a Component?&amp;lt;/sidebar&amp;gt;&lt;br /&gt;
The '''Data Scope''' allows the user to see the results and values from raw data and components such as dials and measures, this data is displayed during simulation and allows you to monitor the state of a dial for example or even record and display data such as audio output and input, analog and digital measurements and even capacitive sensing.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The Data Scope can read and display data from various different ports simultaneously during simulation and can be adjusted to view the data at various speeds which allowed for increased accuracy or a larger amount of data to be displayed at any time.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The Scope is very useful for analyzing data as it can accurately display information to identify patterns in the data as well as the speed data is being displayed at.&lt;br /&gt;
&lt;br /&gt;
[[File:Gen_Data_Scope_Example_01.png|center]]&lt;/div&gt;</summary>
		<author><name>ReeceL</name></author>
		
	</entry>
	<entry>
		<id>https://www.flowcode.co.uk/wiki/index.php?title=Using_the_Data_Recorder&amp;diff=11928</id>
		<title>Using the Data Recorder</title>
		<link rel="alternate" type="text/html" href="https://www.flowcode.co.uk/wiki/index.php?title=Using_the_Data_Recorder&amp;diff=11928"/>
		<updated>2013-09-23T15:07:47Z</updated>

		<summary type="html">&lt;p&gt;ReeceL: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;sidebar&amp;gt;Sidebar: What Is a Component?&amp;lt;/sidebar&amp;gt;&lt;br /&gt;
The '''Data Scope''' allows the user to see the results and values from raw data and components such as dials and measures, this data is displayed during simulation and allows you to monitor the state of a dial for example or even record and display data such as audio output and input, analog and digital measurements and even capacitive sensing.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The Data Scope can read and display data from various different ports simultaneously during simulation and can be adjusted to view the data at various speeds which allowed for increased accuracy or a larger amount of data to be displayed at any time.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The Scope is very useful for analyzing data as it can accurately display information to identify patterns in the data as well as the speed data is being transferred, read and written.&lt;br /&gt;
&lt;br /&gt;
[[File:Gen_Data_Scope_Example_01.png|center]]&lt;/div&gt;</summary>
		<author><name>ReeceL</name></author>
		
	</entry>
	<entry>
		<id>https://www.flowcode.co.uk/wiki/index.php?title=Using_the_Data_Recorder&amp;diff=11927</id>
		<title>Using the Data Recorder</title>
		<link rel="alternate" type="text/html" href="https://www.flowcode.co.uk/wiki/index.php?title=Using_the_Data_Recorder&amp;diff=11927"/>
		<updated>2013-09-23T15:06:11Z</updated>

		<summary type="html">&lt;p&gt;ReeceL: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;sidebar&amp;gt;Sidebar: What Is a Component?&amp;lt;/sidebar&amp;gt;&lt;br /&gt;
The '''Data Scope''' allows the user to see the results and values from raw data and components such as dials and measures, this data is displayed during simulation and allows you to monitor the state of a dial for example or even record and display data such as audio output and input, analog and digital measurements and even capacitive sensing.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The Data Scope can read and display data from various different ports simultaneously during simulation and can be adjusted to view the data at various speeds which allowed for increased accuracy or a larger amount of data to be displayed at any time.&lt;br /&gt;
&lt;br /&gt;
The Scope is very useful for analyzing data as it can accurately display information to decipher patterns in the data and the speed data is being transferred, read and written.&lt;br /&gt;
&lt;br /&gt;
[[File:Gen_Data_Scope_Example_01.png|center]]&lt;/div&gt;</summary>
		<author><name>ReeceL</name></author>
		
	</entry>
	<entry>
		<id>https://www.flowcode.co.uk/wiki/index.php?title=Simulation_Macro_Icon_Properties&amp;diff=11926</id>
		<title>Simulation Macro Icon Properties</title>
		<link rel="alternate" type="text/html" href="https://www.flowcode.co.uk/wiki/index.php?title=Simulation_Macro_Icon_Properties&amp;diff=11926"/>
		<updated>2013-09-23T14:59:43Z</updated>

		<summary type="html">&lt;p&gt;ReeceL: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;sidebar&amp;gt;Sidebar: Icon Properties&amp;lt;/sidebar&amp;gt;&lt;br /&gt;
{| style=&amp;quot;margin:auto; text-align:center;&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
|[[File:Btn_Simulation_Macro.gif|border]]&lt;br /&gt;
| width=&amp;quot;50px&amp;quot; |&amp;amp;rarr; &lt;br /&gt;
|[[File:Gen_Simulation_Macro_Flowchart_Icon_01.png]] &lt;br /&gt;
|width=&amp;quot;50px&amp;quot; |&amp;amp;rarr; &lt;br /&gt;
|[[File:Gen_Simulation_Macro_Icon_Properties_01.png]]&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
Macros are split into Macros and Component/Simulation macros.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Component macros are pre-defined macros supplied with the components. For example LCD macros are used to display numbers and characters on the LCD display.&lt;br /&gt;
&lt;br /&gt;
Component macros are only available for use with that particular component. &lt;br /&gt;
&lt;br /&gt;
Component macros have hatched outer bands on the icon.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Simulation macros can call simulation-only Component Macros, which provide a similar purpose, although they can only be used in simulation and cannot be run on hardware.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Creating a New Macro|Macros]] are those designed and created by the user.&lt;br /&gt;
&lt;br /&gt;
Macros can be [[Exporting a Macro|exported]] and [[Importing a Macro|imported]] allowing users to build up macro libraries of common or important tasks.&lt;br /&gt;
&lt;br /&gt;
On Macros the outer bands are clear and not hatched.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
As well as calling simulation-only [[Component Macro Icon Properties|Component macros]], Simulation Macros can also call [[API Overview|Simulation Functions]] which provide enhanced software simulation although do not download code or compile to hardware.&lt;br /&gt;
&lt;br /&gt;
These simulation functions are used to produce advanced systems on software to accurately replicate and simulate existing systems and even demonstrate new concepts by creating simulation-only programs to test the capabilities of potential systems.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Adding a simulation macro'''&lt;br /&gt;
&lt;br /&gt;
Select the component and then [[Selecting Component Macros|select the Simulation Macro icon.]]&lt;br /&gt;
&lt;br /&gt;
Select the component name from the list of attached components to expand the list group to reveal the available component macros to choose from.&lt;br /&gt;
&lt;br /&gt;
Select the macro and add in any parameters required, and select a return value if required.&lt;br /&gt;
&lt;br /&gt;
OR&lt;br /&gt;
&lt;br /&gt;
Select the Simulation Macro icon and click the 'Functions' section.&lt;br /&gt;
&lt;br /&gt;
Select filter through the categories and search through the list of all available functions.&lt;br /&gt;
&lt;br /&gt;
Select the macro and fill in the parameters required and select a return value if required.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Parameters'''&lt;br /&gt;
&lt;br /&gt;
If the device macro requires any parameters then these can be entered in this field. They can be numeric values or existing variables. Clicking on the down arrow [[File:Btn_Arrow.png]] brings up the variables dialog window allowing you to select an existing variable or to [[Creating Variables|create a new one]].&lt;br /&gt;
&lt;br /&gt;
The parameter details will list the parameter type. Parameters must be of the required type to be accepted.&lt;br /&gt;
&lt;br /&gt;
Note that a full set of parameters must be provided.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Return value'''&lt;br /&gt;
&lt;br /&gt;
If the device macro returns a value then you can assign that value to an existing variable for use later in the flowchart. If the function returns a value but you do not wish to retrieve it then leave this field empty.&lt;br /&gt;
&lt;br /&gt;
The [[Variable Types|variable type]] of the return value will be listed. A variable of the specified type must be used to accept the return value.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
====Video instructions====&lt;br /&gt;
&lt;br /&gt;
Watch the [http://www.youtube.com/watch?v=LSz0p0NqMBw&amp;amp;list=PLQDWBb7bxuCgg6aJgPJcfXBMzZdLILceQ Download and Simulation code] video for a demonstration, example and explanation of downloadable and simulation only code and the difference between the two.&lt;br /&gt;
&lt;br /&gt;
See the [http://www.youtube.com/watch?v=B_tOeSTeAbw&amp;amp;list=PLQDWBb7bxuCgg6aJgPJcfXBMzZdLILceQ Simulation Icon] video for information on the simulation functions available, the video highlights how they are organised and presented and how they can be used.&lt;br /&gt;
&lt;br /&gt;
{| style=&amp;quot;margin:auto;&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
|{{#ev:youtube|LSz0p0NqMBw}}&lt;br /&gt;
| width=&amp;quot;100px&amp;quot; |&lt;br /&gt;
|{{#ev:youtube|B_tOeSTeAbw}}&lt;br /&gt;
|}&lt;/div&gt;</summary>
		<author><name>ReeceL</name></author>
		
	</entry>
	<entry>
		<id>https://www.flowcode.co.uk/wiki/index.php?title=Simulation_Macro_Icon_Properties&amp;diff=11925</id>
		<title>Simulation Macro Icon Properties</title>
		<link rel="alternate" type="text/html" href="https://www.flowcode.co.uk/wiki/index.php?title=Simulation_Macro_Icon_Properties&amp;diff=11925"/>
		<updated>2013-09-23T14:48:33Z</updated>

		<summary type="html">&lt;p&gt;ReeceL: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;sidebar&amp;gt;Sidebar: Icon Properties&amp;lt;/sidebar&amp;gt;&lt;br /&gt;
{| style=&amp;quot;margin:auto; text-align:center;&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
|[[File:Btn_Simulation_Macro.gif|border]]&lt;br /&gt;
| width=&amp;quot;50px&amp;quot; |&amp;amp;rarr; &lt;br /&gt;
|[[File:Gen_Simulation_Macro_Flowchart_Icon_01.png]] &lt;br /&gt;
|width=&amp;quot;50px&amp;quot; |&amp;amp;rarr; &lt;br /&gt;
|[[File:Gen_Simulation_Macro_Icon_Properties_01.png]]&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
Macros are split into Macros and Component/Simulation macros.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Component macros are pre-defined macros supplied with the components. For example LCD macros are used to display numbers and characters on the LCD display.&lt;br /&gt;
&lt;br /&gt;
Component macros are only available for use with that particular component. &lt;br /&gt;
&lt;br /&gt;
Component macros have hatched outer bands on the icon.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Simulation macros are simulation-only Component macros - they provide a similar purpose, although they can only be used in simulation and cannot be run on hardware.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Creating a New Macro|Macros]] are those designed and created by the user.&lt;br /&gt;
&lt;br /&gt;
Macros can be [[Exporting a Macro|exported]] and [[Importing a Macro|imported]] allowing users to build up macro libraries of common or important tasks.&lt;br /&gt;
&lt;br /&gt;
On Macros the outer bands are clear and not hatched.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
As well as calling simulation-only [[Component Macro Icon Properties|Component macros]], Simulation Macros can also call [[API Overview|Simulation Functions]] which provide enhanced software simulation although do not download code or compile to hardware.&lt;br /&gt;
&lt;br /&gt;
These simulation functions are used to produce advanced systems on software to accurately replicate and simulate existing systems and even demonstrate new concepts by creating simulation-only programs to test the capabilities of potential systems.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Adding a simulation macro'''&lt;br /&gt;
&lt;br /&gt;
Select the component and then [[Selecting Component Macros|select the Simulation Macro icon.]]&lt;br /&gt;
&lt;br /&gt;
Select the component name from the list of attached components to expand the list group to reveal the available component macros to choose from.&lt;br /&gt;
&lt;br /&gt;
Select the macro and add in any parameters required, and select a return value if required.&lt;br /&gt;
&lt;br /&gt;
OR&lt;br /&gt;
&lt;br /&gt;
Select the Simulation Macro icon and click the 'Functions' section.&lt;br /&gt;
&lt;br /&gt;
Select filter through the categories and search through the list of all available functions.&lt;br /&gt;
&lt;br /&gt;
Select the macro and fill in the parameters required and select a return value if required.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Parameters'''&lt;br /&gt;
&lt;br /&gt;
If the device macro requires any parameters then these can be entered in this field. They can be numeric values or existing variables. Clicking on the down arrow [[File:Btn_Arrow.png]] brings up the variables dialog window allowing you to select an existing variable or to [[Creating Variables|create a new one]].&lt;br /&gt;
&lt;br /&gt;
The parameter details will list the parameter type. Parameters must be of the required type to be accepted.&lt;br /&gt;
&lt;br /&gt;
Note that a full set of parameters must be provided.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Return value'''&lt;br /&gt;
&lt;br /&gt;
If the device macro returns a value then you can assign that value to an existing variable for use later in the flowchart. If the function returns a value but you do not wish to retrieve it then leave this field empty.&lt;br /&gt;
&lt;br /&gt;
The [[Variable Types|variable type]] of the return value will be listed. A variable of the specified type must be used to accept the return value.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
====Video instructions====&lt;br /&gt;
&lt;br /&gt;
Watch the [http://www.youtube.com/watch?v=LSz0p0NqMBw&amp;amp;list=PLQDWBb7bxuCgg6aJgPJcfXBMzZdLILceQ Download and Simulation code] video for a demonstration, example and explanation of downloadable and simulation only code and the difference between the two.&lt;br /&gt;
&lt;br /&gt;
See the [http://www.youtube.com/watch?v=B_tOeSTeAbw&amp;amp;list=PLQDWBb7bxuCgg6aJgPJcfXBMzZdLILceQ Simulation Icon] video for information on the simulation functions available, the video highlights how they are organised and presented and how they can be used.&lt;br /&gt;
&lt;br /&gt;
{| style=&amp;quot;margin:auto;&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
|{{#ev:youtube|LSz0p0NqMBw}}&lt;br /&gt;
| width=&amp;quot;100px&amp;quot; |&lt;br /&gt;
|{{#ev:youtube|B_tOeSTeAbw}}&lt;br /&gt;
|}&lt;/div&gt;</summary>
		<author><name>ReeceL</name></author>
		
	</entry>
	<entry>
		<id>https://www.flowcode.co.uk/wiki/index.php?title=Simulation_Macro_Icon_Properties&amp;diff=11924</id>
		<title>Simulation Macro Icon Properties</title>
		<link rel="alternate" type="text/html" href="https://www.flowcode.co.uk/wiki/index.php?title=Simulation_Macro_Icon_Properties&amp;diff=11924"/>
		<updated>2013-09-23T14:48:20Z</updated>

		<summary type="html">&lt;p&gt;ReeceL: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;sidebar&amp;gt;Sidebar: Icon Properties&amp;lt;/sidebar&amp;gt;&lt;br /&gt;
{| style=&amp;quot;margin:auto; text-align:center;&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
|[[File:Btn_Simulation_Macro.gif|border]]&lt;br /&gt;
| width=&amp;quot;50px&amp;quot; |&amp;amp;rarr; &lt;br /&gt;
|[[File:Gen_Simulation_Macro_Flowchart_Icon_01.png]] &lt;br /&gt;
|width=&amp;quot;50px&amp;quot; |&amp;amp;rarr; &lt;br /&gt;
|[[File:Gen_Simulation_Macro_Icon_Properties_01.png]]&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
Macros are split into Macros and Component/Simulation macros.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Component macros are pre-defined macros supplied with the components. For example LCD macros are used to display numbers and characters on the LCD display.&lt;br /&gt;
&lt;br /&gt;
Component macros are only available for use with that particular component. &lt;br /&gt;
&lt;br /&gt;
Component macros have hatched outer bands on the icon.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Simulation macros are simulation-only Component macros - they provide a similar purpose, although they can only be used in simulation and cannot be run on hardware.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Creating a New Macro|Macros]] are those designed and created by the user.&lt;br /&gt;
&lt;br /&gt;
Macros can be [[Exporting a Macro|exported]] and [[Importing a Macro|imported]] allowing users to build up macro libraries of common or important tasks.&lt;br /&gt;
&lt;br /&gt;
On Macros the outer bands are clear and not hatched.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
As well as calling simulation-only [[Component Macro Icon Properties|Component macros]], Simulation Macros can also call [[API Overview|Simulation Functions]] which provide enhanced software simulation although do not download code or compile to hardware. These simulation functions are used to produce advanced systems on software to accurately replicate and simulate existing systems and even demonstrate new concepts by creating simulation-only programs to test the capabilities of potential systems.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Adding a simulation macro'''&lt;br /&gt;
&lt;br /&gt;
Select the component and then [[Selecting Component Macros|select the Simulation Macro icon.]]&lt;br /&gt;
&lt;br /&gt;
Select the component name from the list of attached components to expand the list group to reveal the available component macros to choose from.&lt;br /&gt;
&lt;br /&gt;
Select the macro and add in any parameters required, and select a return value if required.&lt;br /&gt;
&lt;br /&gt;
OR&lt;br /&gt;
&lt;br /&gt;
Select the Simulation Macro icon and click the 'Functions' section.&lt;br /&gt;
&lt;br /&gt;
Select filter through the categories and search through the list of all available functions.&lt;br /&gt;
&lt;br /&gt;
Select the macro and fill in the parameters required and select a return value if required.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Parameters'''&lt;br /&gt;
&lt;br /&gt;
If the device macro requires any parameters then these can be entered in this field. They can be numeric values or existing variables. Clicking on the down arrow [[File:Btn_Arrow.png]] brings up the variables dialog window allowing you to select an existing variable or to [[Creating Variables|create a new one]].&lt;br /&gt;
&lt;br /&gt;
The parameter details will list the parameter type. Parameters must be of the required type to be accepted.&lt;br /&gt;
&lt;br /&gt;
Note that a full set of parameters must be provided.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Return value'''&lt;br /&gt;
&lt;br /&gt;
If the device macro returns a value then you can assign that value to an existing variable for use later in the flowchart. If the function returns a value but you do not wish to retrieve it then leave this field empty.&lt;br /&gt;
&lt;br /&gt;
The [[Variable Types|variable type]] of the return value will be listed. A variable of the specified type must be used to accept the return value.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
====Video instructions====&lt;br /&gt;
&lt;br /&gt;
Watch the [http://www.youtube.com/watch?v=LSz0p0NqMBw&amp;amp;list=PLQDWBb7bxuCgg6aJgPJcfXBMzZdLILceQ Download and Simulation code] video for a demonstration, example and explanation of downloadable and simulation only code and the difference between the two.&lt;br /&gt;
&lt;br /&gt;
See the [http://www.youtube.com/watch?v=B_tOeSTeAbw&amp;amp;list=PLQDWBb7bxuCgg6aJgPJcfXBMzZdLILceQ Simulation Icon] video for information on the simulation functions available, the video highlights how they are organised and presented and how they can be used.&lt;br /&gt;
&lt;br /&gt;
{| style=&amp;quot;margin:auto;&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
|{{#ev:youtube|LSz0p0NqMBw}}&lt;br /&gt;
| width=&amp;quot;100px&amp;quot; |&lt;br /&gt;
|{{#ev:youtube|B_tOeSTeAbw}}&lt;br /&gt;
|}&lt;/div&gt;</summary>
		<author><name>ReeceL</name></author>
		
	</entry>
	<entry>
		<id>https://www.flowcode.co.uk/wiki/index.php?title=Component_Debugger&amp;diff=11923</id>
		<title>Component Debugger</title>
		<link rel="alternate" type="text/html" href="https://www.flowcode.co.uk/wiki/index.php?title=Component_Debugger&amp;diff=11923"/>
		<updated>2013-09-23T14:31:26Z</updated>

		<summary type="html">&lt;p&gt;ReeceL: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;sidebar&amp;gt;Sidebar: Overview of Simulation&amp;lt;/sidebar&amp;gt;&lt;br /&gt;
The '''Component Debugger''' is used for tracking, monitoring and developing components, it displays [[API Overview|API functions]] such as timers, events, macro calls such as [[Component Macro Icon Properties|Component Macros]] and [[Simulation Macro Icon Properties|Simulation Macros]] and much more. It can easily track button presses, switch triggers, as well as component properties and the function process.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The Component Debugger is invaluable for testing and developing components as it allows you to accurately keep track of the process of the component and allows you to enhance the functionality of the component in development with the helpful information to troubleshoot problems and errors as well as the ability to evaluate the component by watching and monitoring the process and functions of the component.&lt;br /&gt;
&lt;br /&gt;
[[File:Gen_Component_Debugger_01.png|center]]&lt;br /&gt;
&lt;br /&gt;
The Component Debugger also offers various useful options to extend the information you can gather to test a component. Information such as a detailed component tree shown in the [[Properties Panel]] as well as mouse position, object position and the ability to show hidden objects on the Dashboard Panel and System Panel can be used to identify any graphical, simulation and functionality issues to find areas to improve upon with the help of this additional information.&lt;br /&gt;
&lt;br /&gt;
The position of components and objects are very useful to see in simulation, it allows you to accurately test accurate movement and animation as well as collision detection and input devices such as switches, buttons and dials etc.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
There are simulation functions available to print text onto the 'Component Debugger' to diagnose and identify errors by allowing a trace to be printed during events, this ensures that the program is running correctly and that the flowchart logic is sound.&lt;br /&gt;
&lt;br /&gt;
See the [[API Debug]] section for further technical information, including an example of the functions in use, you can download the Flowcode file by clicking on the file name on the following link:&lt;br /&gt;
:[[File:SIMAPI_Debug_Print.fcfx]]&lt;/div&gt;</summary>
		<author><name>ReeceL</name></author>
		
	</entry>
	<entry>
		<id>https://www.flowcode.co.uk/wiki/index.php?title=Analogue_Window&amp;diff=11919</id>
		<title>Analogue Window</title>
		<link rel="alternate" type="text/html" href="https://www.flowcode.co.uk/wiki/index.php?title=Analogue_Window&amp;diff=11919"/>
		<updated>2013-09-23T13:48:26Z</updated>

		<summary type="html">&lt;p&gt;ReeceL: Redirected page to Analog Window&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;#REDIRECT [[Analog Window]]&lt;/div&gt;</summary>
		<author><name>ReeceL</name></author>
		
	</entry>
	<entry>
		<id>https://www.flowcode.co.uk/wiki/index.php?title=Auto_Documentation&amp;diff=11918</id>
		<title>Auto Documentation</title>
		<link rel="alternate" type="text/html" href="https://www.flowcode.co.uk/wiki/index.php?title=Auto_Documentation&amp;diff=11918"/>
		<updated>2013-09-23T13:28:08Z</updated>

		<summary type="html">&lt;p&gt;ReeceL: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;sidebar&amp;gt;Sidebar: Adding Finishing Touches&amp;lt;/sidebar&amp;gt;&lt;br /&gt;
[[File:Gen_Project_Report_Export_Wizard_01.png|right]]&lt;br /&gt;
Auto-generated documentation consists of technical information taken directly from within Flowcode, for example auto-generated documentation consists of information regarding [[API Overview|API Functions]], [[Component]] macros, properties and functions as well as information regarding [[Editing Variables|Variables]].&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
You can 'Create a Project Report' of your own Flowcode file to auto-generate documentation of your project in different styles, from an overall report to flowchart images and even flowchart source code, the report covers the contents of your Flowcode file, from chip and compiler settings to macros and variables.&lt;br /&gt;
&lt;br /&gt;
This information is taken directly from Flowcode and exported into a HTML document, where all the information will be formatted and organised to include tables and images etc.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
In regards to the auto-documentation for the wiki, there are then fields and areas left to complete such as detailed descriptions and an examples and further information regarding a function, component or property etc.&lt;br /&gt;
&lt;br /&gt;
By default these fields contain red text saying &amp;quot;''&amp;lt;span style=&amp;quot;color:red;&amp;quot;&amp;gt;No additional information&amp;lt;/span&amp;gt;''&amp;quot;, or &amp;quot;''&amp;lt;span style=&amp;quot;color:red;&amp;quot;&amp;gt;No additional examples&amp;lt;/span&amp;gt;''&amp;quot;. These fields are then filled out on the wiki to provide further information about the specified area.&lt;br /&gt;
&lt;br /&gt;
This documentation provides technical information regarding Flowcode, examples of this on the wiki are as follows:&lt;br /&gt;
*[[Variable Types]]&lt;br /&gt;
*[[Components]]&lt;br /&gt;
*[[Event Reference]]&lt;br /&gt;
*[[API Reference]]&lt;/div&gt;</summary>
		<author><name>ReeceL</name></author>
		
	</entry>
	<entry>
		<id>https://www.flowcode.co.uk/wiki/index.php?title=Auto_Documentation&amp;diff=11917</id>
		<title>Auto Documentation</title>
		<link rel="alternate" type="text/html" href="https://www.flowcode.co.uk/wiki/index.php?title=Auto_Documentation&amp;diff=11917"/>
		<updated>2013-09-23T13:26:59Z</updated>

		<summary type="html">&lt;p&gt;ReeceL: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;sidebar&amp;gt;Sidebar: Adding Finishing Touches&amp;lt;/sidebar&amp;gt;&lt;br /&gt;
[[File:Gen_Project_Report_Export_Wizard_01.png|right]]&lt;br /&gt;
Auto-generated documentation consists of technical information taken directly from within Flowcode, for example auto-generated documentation consists of information regarding [[API Overview|API Functions]], [[Component]] macros, properties and functions as well as information regarding [[Editing Variables|Variables]].&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
You can 'Create a Project Report' of your own Flowcode file to auto-generate documentation of your project in different styles, from an overall report to flowchart images and even flowchart source code, the report covers the contents of your Flowcode file, from chip and compiler settings to macros and variables.&lt;br /&gt;
&lt;br /&gt;
This information is taken directly from Flowcode and exported into a HTML document, where all the information will be formatted and organised to include tables and images etc.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
In regards to the auto-documentation for the wiki, there are then fields and areas left to complete such as detailed descriptions and an examples and further information regarding a function, component or property etc.&lt;br /&gt;
&lt;br /&gt;
By default these fields contain red text saying &amp;quot;''&amp;lt;span style=&amp;quot;color:red;&amp;quot;&amp;gt;No additional information&amp;lt;/span&amp;gt;''&amp;quot;, or &amp;quot;''&amp;lt;span style=&amp;quot;color:red;&amp;quot;&amp;gt;No additional examples&amp;lt;/span&amp;gt;''&amp;quot;. These fields are then filled out on the wiki to provide further information about the specified area.&lt;br /&gt;
&lt;br /&gt;
This documentation provides technical information about Flowcode, examples of such content on this wiki are as follows:&lt;br /&gt;
*[[Variable Types]]&lt;br /&gt;
*[[Components]]&lt;br /&gt;
*[[Event Reference]]&lt;br /&gt;
*[[API Reference]]&lt;/div&gt;</summary>
		<author><name>ReeceL</name></author>
		
	</entry>
	<entry>
		<id>https://www.flowcode.co.uk/wiki/index.php?title=Auto_Documentation&amp;diff=11916</id>
		<title>Auto Documentation</title>
		<link rel="alternate" type="text/html" href="https://www.flowcode.co.uk/wiki/index.php?title=Auto_Documentation&amp;diff=11916"/>
		<updated>2013-09-23T13:26:41Z</updated>

		<summary type="html">&lt;p&gt;ReeceL: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;sidebar&amp;gt;Sidebar: Adding Finishing Touches&amp;lt;/sidebar&amp;gt;&lt;br /&gt;
[[File:Gen_Project_Report_Export_Wizard_01.png|right]]&lt;br /&gt;
Auto-generated documentation consists of technical information taken directly from within Flowcode, for example auto-generated documentation consists of information regarding [[API Overview|API Functions]], [[Component]] macros, properties and functions as well as information regarding [[Editing Variables|Variables]].&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
You can 'Create a Project Report' of your own Flowcode file to auto-generate documentation of your project in different styles, from an overall report to flowchart images and even flowchart source code, the report covers the contents of your Flowcode file, from chip and compiler settings to macros and variables.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
This information is taken directly from Flowcode and exported into a HTML document, where all the information will be formatted and organised to include tables and images etc.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
In regards to the auto-documentation for the wiki, there are then fields and areas left to complete such as detailed descriptions and an examples and further information regarding a function, component or property etc.&lt;br /&gt;
&lt;br /&gt;
By default these fields contain red text saying &amp;quot;''&amp;lt;span style=&amp;quot;color:red;&amp;quot;&amp;gt;No additional information&amp;lt;/span&amp;gt;''&amp;quot;, or &amp;quot;''&amp;lt;span style=&amp;quot;color:red;&amp;quot;&amp;gt;No additional examples&amp;lt;/span&amp;gt;''&amp;quot;. These fields are then filled out on the wiki to provide further information about the specified area.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
This documentation provides technical information about Flowcode, examples of such content on this wiki are as follows:&lt;br /&gt;
*[[Variable Types]]&lt;br /&gt;
*[[Components]]&lt;br /&gt;
*[[Event Reference]]&lt;br /&gt;
*[[API Reference]]&lt;/div&gt;</summary>
		<author><name>ReeceL</name></author>
		
	</entry>
	<entry>
		<id>https://www.flowcode.co.uk/wiki/index.php?title=File:Gen_Project_Report_Export_Wizard_01.png&amp;diff=11915</id>
		<title>File:Gen Project Report Export Wizard 01.png</title>
		<link rel="alternate" type="text/html" href="https://www.flowcode.co.uk/wiki/index.php?title=File:Gen_Project_Report_Export_Wizard_01.png&amp;diff=11915"/>
		<updated>2013-09-23T13:15:37Z</updated>

		<summary type="html">&lt;p&gt;ReeceL: File &amp;gt; Create Project Report... = Export wizard&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;File &amp;gt; Create Project Report... = Export wizard&lt;/div&gt;</summary>
		<author><name>ReeceL</name></author>
		
	</entry>
	<entry>
		<id>https://www.flowcode.co.uk/wiki/index.php?title=Analog_Window&amp;diff=11910</id>
		<title>Analog Window</title>
		<link rel="alternate" type="text/html" href="https://www.flowcode.co.uk/wiki/index.php?title=Analog_Window&amp;diff=11910"/>
		<updated>2013-09-23T12:35:32Z</updated>

		<summary type="html">&lt;p&gt;ReeceL: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;sidebar&amp;gt;Sidebar: What Is a Component?&amp;lt;/sidebar&amp;gt;&lt;br /&gt;
[[File:Gen_Analog_Window_01.png|right|332x290px]]&lt;br /&gt;
The '''Analog Window''' displays and monitors analog values on each channel, allowing you to see the results/values of each channel both as a text values and dynamic bars to display the output values of analog devices.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
To open the 'Analog Window' select 'Analog Inputs' from the 'View' menu (View &amp;gt; Analog Inputs').&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The Analog Window dynamically displays values of analog inputs and can display the data from a range of different channels simultaneously during simulation. Analog data is displayed in this window by using bars to convey the data value as well as text to accurately read the results the text can be changed to display the data as several different values/units.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
You can change the 'View values as:' option at the top of the window by selecting an option from the drop-down box, by doing so you can change the text to display the data value of the analog channels as:&lt;br /&gt;
*Raw&lt;br /&gt;
*Byte&lt;br /&gt;
*Percent&lt;br /&gt;
*Unit&lt;br /&gt;
&lt;br /&gt;
{| style=&amp;quot;margin:auto; text-align:center;&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
|[[File:Gen_Analog_Window_Raw_01.png]]&lt;br /&gt;
| width=&amp;quot;100px&amp;quot; |&lt;br /&gt;
|[[File:Gen_Analog_Window_Percent_01.png]]&lt;br /&gt;
|}&lt;/div&gt;</summary>
		<author><name>ReeceL</name></author>
		
	</entry>
</feed>