XLogic3: Delayed Off

Owned by Wolfgang Granzer
Dec 05, 2018

This example shall implement the following functionality: if a rising edge of a Boolean input is detected, the output shall be set to true. After a defined delay, the output shall be set to false again. If the output is currently set to true and another rising edge at the input is detected, the time delay for setting the output to false shall be reset. The following figure shows the functionality mentioned above.

Delayed off

To use this tutorial, please do the following steps in advance:

  • Install the NETx BMS Server. The setup can be found here at our website.
  • Create a new BMS server workspace and integrate some data points that you use for this example.

Creating the command

Within the BMS Studio, start the XLogic Editor using the corresponding icon in the toolbar. Then select the entry "New Command ..." from the menu "File". A new dialog opens that is used to define the name of the command as well as its inputs, outputs, and parameters.

 

 

Within this dialog, set the name to "Delayed Off" and define the following input:

  • Input: this is the item ID that specifies the input that shall be monitored.

Then, define the following output:

  • Output: this is the item ID that specifies the output where the result shall be written.

Finally, define the following parameter:

  • Delay: this parameter of type "NUMBER" specifies the delay in seconds.

 

The dialog with all correct values is shown in the figure above.

Command flow

As next the command flow has to be defined. The proposed command shall be split into two different parts -- one part that processes the input and one part that process the output. To achieve this, insert two "CMD BLOCK"s and set the comment of the first one to "Process input" and the comment of the second one to "Process output". Figure \ref{fig:delayed_off_flow} shows the final command flow.



"Process input"

As next the "Process input" block shall be implemented. By doing a double click on the corresponding block, the work sheet of the "CMD BLOCK" opens. Within this work sheet, define the command flow that is shown in the following figure.

 

The command flow of the "Process input" block consists of the following blocks:

  • "Edge detection": this block of type "CMD BLOCK" performs the detection of the rising edge of the input.
  • "Is edge detected?": after having performed the edge detection, it has to be verified whether a edge currently exists or not.
  • "Set counter": if an edge was detected, the time delay is reset to the initial value (i.e. to the specified delay).
  • "Is output false?": this condition verifies whether the output is current set to "false".
  • "Write true to output": if the output is currently "false", it is set to "true".

In the following, the above mentioned blocks are explained in more detail.

"Edge detection"

The command flow of the "Edge detection" block is shown in the following figure.

 

It consists of the following blocks:

"Is edge detected?"

This condition verifies whether a positive edge is detected at the input. The condition is shown in here.

"Set edge'"

Here, the variable "edge" is set which indicates that an edge has been detected. The implementation is shown in the following figure.

"Reset edge"

This block is used to reset the variable "edge". The implementation is shown in the following figure.

 

"Set last value edge"

Here, the current value of the input is stored in the variable "last input" which is used in the next command execution to perform the edge detection. The implementation is shown in the following figure.

 

"Is edge detected?"

This condition verifies whether an edge has been detected in the previous "CMD BLOCK". Using an "EQUAL" block, the current value of the variable "edge" (retrieved by the "VARIABLE VALUE" block in combination with a "VARIABLE NAME" block) is compared to the constant "TRUE" (provided by a "BOOL" block). The implementation of the "Is edge detected" condition is shown in the following figure.

 

"Set counter"

This block resets the counter to the value that is specified by the "Delay" parameter. The implementation of the "Set counter" block is shown in the following figure.

 

"Is output false?"

After having reset the counter, the output shall be set to true if it is not already true. To achieve this, the output has to verified. Figure \ref{fig:delayed_off_is_output_false} shows the implementation of the required condition.

 

"Write true to output"

The following figure shows how the output is set to true. Note that a "WRITE OUTPUT ITEM" block also forwards the value to the bus if a physical data point is behind the server item.

"Process output"

After having finished the "Process input" block, the "Process output" block has to be implemented. By doing a double click on the corresponding block, the work sheet of the "CMD BLOCK" opens. Within this work sheet, define the command flow that is shown in the following figure.

 

The command flow of the "Process output" block consists of the following blocks:

  • "Is counter 0?": this condition verifies whether the current counter value is zero.
  • "Is output true?": if the counter is zero, the output shall be reset to false again. However, this shall only be done if the output is currently set to true. The required test is done within this block.
  • "Write false to output": Within this "CMD" block, the output is set to false.
  • "Decrement counter": if the counter is not yet zero, it is decremented by one within this block.

In the following, the above mentioned blocks are explained in more detail.

"Is counter 0?'

Using a "LESS OR EQUAL" block, the current counter value which is stored within the variable "counter" is compared with zero. To get the value of the variable, a "VARIABLE VALUE" block is used. Since the variable may be uninitialized after server startup, zero is specified as default value. The implementation of this condition is shown in the following figure.

 

"Is output true?'

If the current counter value is zero, the delay interval is elapsed and the output shall be reset to false again. However, to avoid that multiple "false" telegrams are sent to the bus, the output shall only be set to false if the output is currently true. The implementation of the required test is shown in the following figure.

 

"Write false to output'

The following figure shows how the output is set to false. To forward the value also to the bus if the output is a physical data point, a "WRITE OUTPUT ITEM" is used. If the value shall only be set internally and not forwarded to the bus, a "SET OUTPUT VALUE" block has to be used instead.

 

"Decrement counter'

If the current counter value is not zero, the delay interval has not been elapsed and thus the counter value has to be decremented by one. The following figure shows the implementation of this functionality. Decrementing the value is done using a "SUB" block. The incoming "Input 1" connector is connected to outgoing "VALUE" connector of the "VARIABLE VALUE" block that provides the current counter value. The "Input 2" connector is connected to the "NUMBER" block that provides the constant value 1. The result of the subtraction is stored in the "counter" variable again using a "SET VARIABLE" block.

 

Saving the command and using the command within the NETx BMS Server

To provide the command to the NETx BMS Server, it has to be compiled. This can be done by clicking the "Save" icon within the toolbar which saves and compiles the current command. In addition, it is possible to change several options of a command. To open the "Options" dialog, the entry "Options ..." within the menu "File" has to be selected. Within this dialog, basic information about the command can be specified. The flag "Add to Catalog" defines whether the command shall be visible within the catalog of the XLogic Editor. If activated, the command can be reused in other commands. If the option "Auto-Compile" is set, the command is automatically compiled whenever the project is saved.

 

After having compiled the command successfully, close the XLogic editor and go back to the NETx BMS Studio. Afterwards, the new command has to be loaded before it can be used. This can be done by restarting the NETx BMS Server or by loading the command manually by selecting the entry "Load logic module" within the "Tools" menu of the NETx BMS Studio. Then, open the "XCommand event definitions" via the menu "Extensions". Add a new definition and enter a name for the command within the first column. The next column can be left empty since all variables shall only be used locally. Within the third column, select "ON_TIMER_AND_INPUT". This indicates that the command shall be invoked whenever one of the inputs changes and/or after a predefined timer interval has elapsed. To specify the timer interval, enter "1" in the "Options" column. This indicated that the command shall be executed every second in addition to a change of value of an input. Then, press the "..." button within the "XCommand" column. A dialog appears where the command can be selected and configured. Select the "Delayed Off" command from the drop down list. Afterwards, specify the different inputs, outputs, and parameters. A possible configuration is shown in the following figure.

After having saved the "XCommand event definition", restart the NETx BMS Server and test the command.