Errors during Execution - Versionsgeschichte

Cg: Weiterleitung nach Common Errors erstellt

2022-02-23T00:56:35Z

Weiterleitung nach Common Errors erstellt

Cg: /* A Chain of Looped-Over Steps */

2021-11-26T14:24:24Z

A Chain of Looped-Over Steps

← Nächstältere Version		Version vom 26. November 2021, 14:24 Uhr
Zeile 120:		Zeile 120:

	Fix:		Fix:
	* put all steps which are in the chain into a separate compound action. The editor's right-button-menu has a special function for that ("''Extract and Replace by New Compound Action''" under the the "''Refactor''" menu item).		* put all steps which are in the chain into a separate compound action.<br>The editor's right-button-menu has a special function for that ("''Extract and Replace by New Compound Action''" under the the "''Refactor''" menu item).

	=== Action does not Finish in a Producer-Consumer Setup ===		=== Action does not Finish in a Producer-Consumer Setup ===

Cg: /* Self Retrigger does not Work */

2021-11-26T14:23:56Z

Self Retrigger does not Work

@@ Zeile 109: / Zeile 109: @@
 Fix:
 * Either make the output pin buffered, or use the step's trigger-output pin for retrigger (which is by definition buffered and only send out a value AFTER the step has finished).
 === Action does not Finish in a Producer-Consumer Setup ===

Cg: /* Self Retrigger does not Work */

2021-11-26T09:49:10Z

Self Retrigger does not Work

← Nächstältere Version		Version vom 26. November 2021, 09:49 Uhr
Zeile 107:		Zeile 107:
	Therefore, connecting an unbuffered data output to the step's own trigger input will not work as expected.		Therefore, connecting an unbuffered data output to the step's own trigger input will not work as expected.

	Fix:~~<br>~~		Fix:
	~~You~~ ~~should either~~ make the output pin buffered, or use the ~~steps~~ trigger-output pin (which is by definition only ~~sending~~ out a value ~~after~~ the step has finished).		* Either make the output pin buffered, or use the step's trigger-output pin for retrigger (which is by definition buffered and only send out a value AFTER the step has finished).

	=== Action does not Finish in a Producer-Consumer Setup ===		=== Action does not Finish in a Producer-Consumer Setup ===

Cg: /* Step in Loop is not Executed at All */

2021-11-26T09:47:55Z

Step in Loop is not Executed at All

← Nächstältere Version		Version vom 26. November 2021, 09:47 Uhr
Zeile 93:		Zeile 93:
	Fix:		Fix:
	* To provide this initial trigger, add any dummy step, which generates an output and feed that as additional input to the loop-top's enableIn pin. Any output and especially a trigger-output will do.		* To provide this initial trigger, add any dummy step, which generates an output and feed that as additional input to the loop-top's enableIn pin. Any output and especially a trigger-output will do.
			:

	The standard library provides such a block named "Start", which is actually a No-Operation block, and its sole purpose is to provide such an initial trigger condition. Make sure that the Start step is itself triggered, usually by setting its autostart execution flag.		:The standard library provides such a block named "Start", which is actually a No-Operation block, and its sole purpose is to provide such an initial trigger condition. Make sure that the Start step is itself triggered, usually by setting its autostart execution flag.

	=== Self Retrigger does not Work ===		=== Self Retrigger does not Work ===

Cg: /* Step in Loop is not Executed at All */

2021-11-26T09:47:27Z

Step in Loop is not Executed at All

← Nächstältere Version		Version vom 26. November 2021, 09:47 Uhr
Zeile 91:		Zeile 91:
	<br>If you have instructed a loop which is connected via enableOut-enableIn control pins, the loop will not start, as no initial trigger ever appears.		<br>If you have instructed a loop which is connected via enableOut-enableIn control pins, the loop will not start, as no initial trigger ever appears.

			Fix:
	To provide this initial trigger, add any dummy step, which generates an output and feed that as additional input to the loop-top's enableIn pin. Any output and especially a trigger-output will do.		* To provide this initial trigger, add any dummy step, which generates an output and feed that as additional input to the loop-top's enableIn pin. Any output and especially a trigger-output will do.

	The standard library provides such a block named "Start", which is actually a No-Operation block, and its sole purpose is to provide such an initial trigger condition. Make sure that the Start step is itself triggered, usually by setting its autostart execution flag.		The standard library provides such a block named "Start", which is actually a No-Operation block, and its sole purpose is to provide such an initial trigger condition. Make sure that the Start step is itself triggered, usually by setting its autostart execution flag.

Cg: /* Self Retrigger does not Work */

2021-11-26T09:46:25Z

Self Retrigger does not Work

← Nächstältere Version		Version vom 26. November 2021, 09:46 Uhr
Zeile 105:		Zeile 105:

	Therefore, connecting an unbuffered data output to the step's own trigger input will not work as expected.		Therefore, connecting an unbuffered data output to the step's own trigger input will not work as expected.

			Fix:<br>
	You should either make the output pin buffered, or use the steps trigger-output pin (which is by definition only sending out a value after the step has finished).		You should either make the output pin buffered, or use the steps trigger-output pin (which is by definition only sending out a value after the step has finished).

Cg: /* Strange Behavior in Loops */

2021-11-26T09:43:22Z

Strange Behavior in Loops

← Nächstältere Version		Version vom 26. November 2021, 09:43 Uhr
Zeile 74:		Zeile 74:
	== Strange Behavior in Loops ==		== Strange Behavior in Loops ==

			See also "[[Common Errors/en\|Common Errors]]".

	=== Step in a Loop is not Executed or Executed only Once ===		=== Step in a Loop is not Executed or Executed only Once ===

Cg: /* Self Retrigger seems not to work */

2021-11-26T09:41:53Z

Self Retrigger seems not to work

← Nächstältere Version		Version vom 26. November 2021, 09:41 Uhr
Zeile 94:		Zeile 94:
	The standard library provides such a block named "Start", which is actually a No-Operation block, and its sole purpose is to provide such an initial trigger condition. Make sure that the Start step is itself triggered, usually by setting its autostart execution flag.		The standard library provides such a block named "Start", which is actually a No-Operation block, and its sole purpose is to provide such an initial trigger condition. Make sure that the Start step is itself triggered, usually by setting its autostart execution flag.

	=== Self Retrigger ~~seems~~ not ~~to work~~ ===		=== Self Retrigger does not Work ===
	A self trigger setup is done by connecting a step's output (either a data output or a trigger output) back to its own trigger input.		A self trigger setup is done by connecting a step's output (either a data output or a trigger output) back to its own trigger input.

Cg: /* Step in Loop is not Executed at All */

2021-11-26T09:41:15Z

Step in Loop is not Executed at All

← Nächstältere Version		Version vom 26. November 2021, 09:41 Uhr
Zeile 93:		Zeile 93:

	The standard library provides such a block named "Start", which is actually a No-Operation block, and its sole purpose is to provide such an initial trigger condition. Make sure that the Start step is itself triggered, usually by setting its autostart execution flag.		The standard library provides such a block named "Start", which is actually a No-Operation block, and its sole purpose is to provide such an initial trigger condition. Make sure that the Start step is itself triggered, usually by setting its autostart execution flag.

			=== Self Retrigger seems not to work ===
			A self trigger setup is done by connecting a step's output (either a data output or a trigger output) back to its own trigger input.

			The idea is to fire the step again, once finished. A typical situation where this is useful is with the "[ Wait for Variable to Change ]" action, which is often used in GUI-action (and there usually waiting for some user interaction).

			Be reminded, that there are two kinds of output pin behavior: buffered and unbuffered.
			Buffered means, that the value is written AFTER the step has finished successful, whereas unbuffered outputs are written immediately.
			If you have an unbuffered output connected to the steps own trigger input, the trigger will not be effective (because the step is already running, and the trigger is ignored then).

			Therefore, connecting an unbuffered data output to the step's own trigger input will not work as expected.
			You should either make the output pin buffered, or use the steps trigger-output pin (which is by definition only sending out a value after the step has finished).

	=== Action does not Finish in a Producer-Consumer Setup ===		=== Action does not Finish in a Producer-Consumer Setup ===