C Code Simulation - Revision history

MartinW: /* Example */

2023-10-05T10:23:45Z

Example

MartinW at 10:21, 5 October 2023

2023-10-05T10:21:29Z

DavidA at 07:55, 2 July 2019

2019-07-02T07:55:42Z

BenR at 10:37, 1 August 2018

2018-08-01T10:37:12Z

DanielM at 13:57, 31 May 2018

2018-05-31T13:57:43Z

DanielM at 13:55, 31 May 2018

2018-05-31T13:55:37Z

DanielM at 13:53, 31 May 2018

2018-05-31T13:53:45Z

DanielM: /* Interacting with Flowcode variables in C code */

2018-05-31T13:51:24Z

Interacting with Flowcode variables in C code

DanielM: /* Calling Flowcode functions and your own Macros */

2018-05-31T13:42:42Z

Calling Flowcode functions and your own Macros

DanielM at 13:41, 31 May 2018

2018-05-31T13:41:51Z

← Older revision		Revision as of 10:23, 5 October 2023
Line 202:		Line 202:

	The C Simulation feature is similar to the [[C_Code_to_Flowchart_Conversion\|C Code to Flowchart Conversion]] feature that converts C code into Flowchart icons.		The C Simulation feature is similar to the [[C_Code_to_Flowchart_Conversion\|C Code to Flowchart Conversion]] feature that converts C code into Flowchart icons.
		+
		+	To view all the c code ,ither hover over the C code box as shown above, or double click on it.

← Older revision		Revision as of 10:21, 5 October 2023
Line 1:		Line 1:
−	~~Unlike previous versions,~~ Flowcode 8 can simulate C code inside C Code icons. Note, in order to use this feature you will need to have purchased the ~~C Simulation feature pack~~.	+	Flowcode can simulate C code inside C Code icons. Note, in order to use this feature you will need to have purchased the Professional or Academic license.

−	This feature can be great for debugging custom C code within your project, prior to compilation to a microcontroller. It is also invaluable as a teaching tool, and allows you to teach students the effects of certain C language statements on variables. When simulating C code, you can step through individual statements within a block in the same way that you step through multiple icons in your Flowchart.	+	This feature can be great for debugging custom C code within your project, prior to compilation to a microcontroller. It is also invaluable as a teaching tool and allows you to teach students the effects of certain C language statements on variables. When simulating C code, you can step through individual statements within a block in the same way that you step through multiple icons in your Flowchart.

← Older revision		Revision as of 07:55, 2 July 2019
Line 1:		Line 1:
−	~~<sidebar>Sidebar: Flowcode Help Overview:Flowcharts</sidebar>~~
	Unlike previous versions, Flowcode 8 can simulate C code inside C Code icons. Note, in order to use this feature you will need to have purchased the C Simulation feature pack.		Unlike previous versions, Flowcode 8 can simulate C code inside C Code icons. Note, in order to use this feature you will need to have purchased the C Simulation feature pack.

← Older revision		Revision as of 10:37, 1 August 2018
Line 1:		Line 1:
		+	<sidebar>Sidebar: Flowcode Help Overview:Flowcharts</sidebar>
	Unlike previous versions, Flowcode 8 can simulate C code inside C Code icons. Note, in order to use this feature you will need to have purchased the C Simulation feature pack.		Unlike previous versions, Flowcode 8 can simulate C code inside C Code icons. Note, in order to use this feature you will need to have purchased the C Simulation feature pack.

← Older revision		Revision as of 13:57, 31 May 2018
Line 77:		Line 77:


−	However, the behaviour of these variable types cannot be guaranteed to be the same between various compiler families. Therefore, we recommend that you use the Flowcode types from the above table in order to keep your code as portable ~~as possible between different microcontrollers~~.	+	However, the behaviour of these variable types cannot be guaranteed to be the same between various compiler families. Therefore, if you plan on compiling your code to a microcontroller, we recommend that you use the Flowcode types from the above table in order to keep your code as portable. On the other hand, the native C data types can be useful for educational purposes.

@@ Line 82: / Line 82: @@
 ===Accessing variables created in Flowcode's UI===
-You can easily modify and read the values of variables that you have created in the user-interface (for example, using the Project Explorer). Variables are referred to using purely upper-case, and with a special prefix depending on whether they are global or local variables.
+You can easily modify and read the values of variables that you have created in the user-interface (for example, using the Project Explorer). Variables are referred to using purely uppercase, and with a special prefix depending on whether they are global or local variables.
 {| class="wikitable"

@@ Line 2: / Line 2: @@
 This feature can be great for debugging custom C code within your project, prior to compilation to a microcontroller. It is also invaluable as a teaching tool, and allows you to teach students the effects of certain C language statements on variables. When simulating C code, you can step through individual statements within a block in the same way that you step through multiple icons in your Flowchart.
@@ Line 98: / Line 99: @@
 |}
 ==Calling Flowcode functions and your own Macros==
@@ Line 177: / Line 179: @@
 |Sets the function sets the value of the pins of port w given by the mask x, to z, after left-shifting z by y positions
 |}
 ===User-defined macros===
@@ Line 187: / Line 190: @@
 Note that we do not have to make the "Func" part of the expression uppercase, unlike when referring to variables.
 ==Example==

@@ Line 34: / Line 34: @@
 ===Variable data types===
-When variables are created in the Project Explorer, you specify a given type (e.g. Byte). The actual types as they appear in C code can be understood using the following mapping:
+When variables are normally created in Flowcode, you specify a given type (e.g. Byte). The actual types as they appear in C code can be understood using the following mapping:
 {| class="wikitable"
@@ Line 79: / Line 79: @@
-===Accessing variables defined using the Project Explorer from C code===
+===Accessing variables created in Flowcode's UI===
 ==Calling Flowcode functions and your own Macros==

@@ Line 84: / Line 84: @@
 ==Calling Flowcode functions and your own Macros==
 Currently, there is a limited support for simulating Flowcode-generated function calls within your own C code.
@@ Line 160: / Line 162: @@
 |}
 Flowcode is also able to simulate the effects of calling your own user-defined macros. In C code, user-macros are referred to using the prefix "FCM_". For example, if we defined a user-macro called "Func", which returned a byte, and required an integer as a parameter, then we could write the following C code, which would successfully simulate.

@@ Line 89: / Line 89: @@
 Flowcode is able to simulate the effects of the following function calls:
-* '''FCI_DELAYBYTE_MS(x) where x is a byte and the function causes a delay of x milliseconds'''
+{| class="wikitable"
-* '''FCI_DELAYBYTE_US(x) where x is a byte and the function causes a delay of x microseconds'''
+|-
-* '''FCI_DELAYBYTE_S(x) where x is a byte and the function causes a delay of x seconds'''
+! scope="col"| Function call
-* '''FCI_DELAYINT_MS(x) where x is an int up to 2000 and the function causes a delay of x milliseconds'''
+! scope="col"| Parameter explanation
-* '''FCI_DELAYINT_US(x) where x is an int up to 2000 and the function causes a delay of x microseconds'''
+! scope="col"| Effect of function
-* '''FCI_DELAYINT_S(x)  where x is an int up to 2000 and the function causes a delay of x seconds'''
+|-
-* '''GET_PORT(x) where x is a port letter (A, B, C...) and the function returns the value of port x'''
+|FCI_DELAYBYTE_MS(x)
-* '''GET_PORT_PIN(x, y) where x is a port letter (A, B, C...), y is a pin index (0, 1, 2 etc.) and the function returns the value of pin y of port x'''
+|x is a byte
-* '''GET_PORT_MASK(x, y) where x is a port letter (A, B, C...), y is a mask value (e.g. 0xFF00) and the function returns the value of the pins of port x given by the mask y'''
+|Causes a delay of x milliseconds
-* '''GET_PORT_SHIFT(x, y) where x is a port letter (A, B, C...), y is a shift value (e.g. 3) and the function returns the value of port x after right-shifting it by y positions'''
+|-
-* '''GET_PORT_MASK_SHIFT(x, y, z) where x is a port letter (A, B, C...), y is a mask value (e.g. 0xFF00), z is a shift value (e.g. 3) and the function returns the value of the pins of port x given by the mask y, after right-shifting it by z positions'''
+|FCI_DELAYBYTE_US(x)
-* '''SET_PORT(x, y) where x is a port letter (A, B, C...), y is a numerical value and the function sets the value of port x to y'''
+|x is a byte
-* '''SET_PORT_PIN(x, y, z) where x is a port letter (A, B, C...), y is a pin index (0, 1, 2 etc.), z is a numerical value and the function sets the value of pin y of port x to z'''
+|Causes a delay of x microseconds
-* '''SET_PORT_MASK(x, y, z) where x is a port letter (A, B, C...), y is a mask value (e.g. 0xFF00), z is a numerical value and the function sets the value of the pins of port x given by the mask y, to z'''
+|-
-* '''SET_PORT_SHIFT(x, y, z) where x is a port letter (A, B, C...), y is a shift value (e.g. 3), z is a numerical value and the function sets the value of port x, to z, after left-shifting z by y positions'''
+|FCI_DELAYBYTE_S(x)
-* '''SET_PORT_MASK_SHIFT(w, x, y, z) where w is a port letter (A, B, C...), x is a mask value (e.g. 0xFF00), y is a shift value (e.g. 3), z is a numerical value and the function sets the value of the pins of port w given by the mask x, to z, after left-shifting z by y positions'''
+|x is a byte