This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
comfilehmi:multiaction:index [2023/04/07 05:20] COMFILE Technology [Run Action Group] |
comfilehmi:multiaction:index [2024/02/13 17:28] (current) COMFILE Technology [Send to Remote PC(s)] |
||
---|---|---|---|
Line 8: | Line 8: | ||
{{ :comfilehmi:multiaction:multiaction.png?nolink |}} | {{ :comfilehmi:multiaction:multiaction.png?nolink |}} | ||
- | |||
---- | ---- | ||
Line 14: | Line 13: | ||
===== Write Directly ===== | ===== Write Directly ===== | ||
- | Literal values or variables can be written to a memory location in an attached device ((A PLC or MCU connected to the ComfileHMI hardware)). | + | Literal values or variables can be written to a memory location in an attached external device ((A PLC or MCU connected to the ComfileHMI hardware)) or internal variable / internal memory. |
{{ :comfilehmi:multiaction:multiaction1.png?nolink |}} | {{ :comfilehmi:multiaction:multiaction1.png?nolink |}} | ||
Line 46: | Line 45: | ||
{{ :comfilehmi:multiaction:screen_capture.png |}} | {{ :comfilehmi:multiaction:screen_capture.png |}} | ||
- | ==== Send to Remote PC(s) ==== | + | ==== Destination: Remote PC ==== |
- | Check this option to have the log data send to any Supervisory Remote Control clients that may be connected to the panel PC. | + | Select this option to have the log data send to any Supervisory Remote Control clients that may be connected to the panel PC. |
{{ :comfilehmi:multiaction:sendtoremote.png?nolink |}} | {{ :comfilehmi:multiaction:sendtoremote.png?nolink |}} | ||
+ | |||
+ | ==== Destination: Communication Channel ==== | ||
+ | |||
+ | Select this option to have the log data transmitted out a serial port. The serial port must be configured for the //USER > SERIAL TX// protocol in the //Project Properties//. | ||
+ | |||
+ | {{ :comfilehmi:multiaction:sendtoserial.png?nolink |}} | ||
---- | ---- | ||
Line 77: | Line 82: | ||
First, an action group must be registered and given a unique name. In the illustration below the variable //ABC// will be initialized with the value 0. | First, an action group must be registered and given a unique name. In the illustration below the variable //ABC// will be initialized with the value 0. | ||
- | {{ :comfilehmi:multiaction:actiongroup.gif?nolink |}} | + | {{ :comfilehmi:multiaction:makeactiongroup.mp4?900x542 |}} |
Then the event can be used in a multi-action list. | Then the event can be used in a multi-action list. | ||
Line 119: | Line 124: | ||
---- | ---- | ||
- | ===== Display a Keypad ===== | + | ===== Open Dynamic Keypad ===== |
The //Keypad// action will display a keypad so an operator to enter numeric input. | The //Keypad// action will display a keypad so an operator to enter numeric input. | ||
Line 125: | Line 130: | ||
{{ :comfilehmi:multiaction:keypadpopup.png?nolink |}} | {{ :comfilehmi:multiaction:keypadpopup.png?nolink |}} | ||
- | {{ :comfilehmi:multiaction:keypad.mp4?850x453 |}} | ||
- | ===== Multi-action Conditional Activation ====== | ||
- | An action can be activated dynamically by specifying a conditional expression. | + | ---- |
- | {{ :comfilehmi:multiaction:actioncondition.png?nolink |}} | + | ===== Internal String Variable Control ===== |
- | So, this action is only executed if the condition is satisfied. | + | This software provides various tools to edit Internal string variable. |
- | {{ :comfilehmi:multiaction:actioncondition2.png?nolink |}} | + | {{ :comfilehmi:multiaction:stringcontrol.png?nolink |}} |
+ | ---- | ||
===== HTTP Request ===== | ===== HTTP Request ===== | ||
Line 154: | Line 158: | ||
{{ :comfilehmi:multiaction:multiaction7_1.png?nolink |}} | {{ :comfilehmi:multiaction:multiaction7_1.png?nolink |}} | ||
+ | |||
+ | ===== Special Feature : Alarm History Viewer ===== | ||
+ | |||
+ | Various tools are provided to edit alarm-history-viewer. | ||
+ | |||
+ | {{ :comfilehmi:multiaction:alramcontrol.png?nolink |}} | ||
+ | |||
+ | ---- | ||
+ | |||
+ | ====== Multi-action Conditional Activation ======= | ||
+ | |||
+ | An action can be activated dynamically by specifying a conditional expression. | ||
+ | |||
+ | {{ :comfilehmi:multiaction:actioncondition.png?nolink |}} | ||
+ | |||
+ | So, this action is only executed if the condition is satisfied. | ||
+ | |||
+ | {{ :comfilehmi:multiaction:actioncondition2.png?nolink |}} | ||
[[comfilehmi:index#widgets| Back to ComfileHMI]] | [[comfilehmi:index#widgets| Back to ComfileHMI]] | ||