User Tools

Site Tools

한국어

comfilehmi:hmieditor_susik:index

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
comfilehmi:hmieditor_susik:index [2023/04/15 03:15]
COMFILE Technology [Internal Memory]
comfilehmi:hmieditor_susik:index [2024/02/01 13:27] (current)
COMFILE Technology
Line 4: Line 4:
  
 In the ComfileHMI, a //Internal variable// refers to a named location in the ComfileHMI hardware'​s memory. In the ComfileHMI, a //Internal variable// refers to a named location in the ComfileHMI hardware'​s memory.
 +
 +{{ :​comfilehmi:​hmieditor_susik:​hmiandplc2.png?​nolink |}}
  
 If a Internal variable is used without first being declared, it will be implicitly declared and available for use immediately. If a Internal variable is used without first being declared, it will be implicitly declared and available for use immediately.
Line 15: Line 17:
     * //Motor Status// is invalid because it contains a space     * //Motor Status// is invalid because it contains a space
  
-A list of variables in use can be obtained from the ComfileHMI Editor's main menu: //​Project//​->//​View Addresses and Variables in Use//.+A list of variables in use can be obtained from Comfile Studio's main menu: //​Project//​->//​View Addresses and Variables in Use//.
 ==== String Variables ==== ==== String Variables ====
  
-String variables were added in a subsequent version of the ComfileHMI Editor software.  They are declared and used with ''​$''​ prefix. ​ For example <​html><​code>​$a=&​quot;​hello&​quot;</​code></​html>​.+String variables were added in a subsequent version of Comfile Studio.  They are declared and used with ''​$''​ prefix. ​ For example <​html><​code>​$a=&​quot;​hello&​quot;</​code></​html>​.
  
 ===== Internal Memory ===== ===== Internal Memory =====
comfilehmi/hmieditor_susik/index.1681496159.txt.gz · Last modified: 2023/04/15 03:15 by COMFILE Technology