{"id":3998,"date":"2019-02-12T16:10:18","date_gmt":"2019-02-12T16:10:18","guid":{"rendered":"https:\/\/cyflexdoc.wpengine.com\/usage-help-manual\/19-variables-and-computations\/svar\/"},"modified":"2026-05-20T12:59:29","modified_gmt":"2026-05-20T17:59:29","slug":"svar","status":"publish","type":"page","link":"https:\/\/cyflex.com\/index.php\/usage-help-manual\/2-variables-and-computations\/svar\/","title":{"rendered":"svar"},"content":{"rendered":"

Purpose:<\/h3>\n
\n
\n

Set the value of a variable or list of variables.<\/p>\n

Only REAL, REAL_ARRAY, INTEGER, INTEGER_ARRAY, LOGICAL, LOGICAL_ARRAY, STRING, and STRING_ARRAY variable types are supported. COMPOSITION, PROPERTY, STATISTICAL and EMISSION types cannot be set with this command.<\/p>\n

Note that there are many optional ways to express the value, such as a constant, variable label, or computed expression. Special consideration is given to certain cases of REAL variables:<\/p>\n

    \n
  1. Changing the value of the “Cell_meter” hour meter value is not allowed.<\/li>\n
  2. Changing the value of the \u201cPAM_point\u201d variable is not allowed. Use the “setPAMpoint” command to do this.<\/li>\n
  3. If you set the value of a counter (CI) channel or a Gantner counter channel from a 2143 module, a message is sent to the transfer layer task so that this new value can be ‘synchronized’ to the current raw data value from the input channel.<\/li>\n<\/ol>\n

    In version CyFlex.6.2 and newer releases, dimensional consistency checking has been added.<\/p>\n<\/dd>\n<\/dl>\n

    Enter:<\/h3>\n
    \n
    \n
    \n\n\n\n<\/colgroup>\n\n\n\n\n\n\n\n\n
    svar<\/strong><\/td>\n<variable_label> <value><\/td>\n<\/tr>\n
    svar<\/strong><\/td>\n<label1> <value1> label2 value2 label3 value3 \u2026<\/td>\n<\/tr>\n
    \u00a0<\/td>\n(etc.\u00a0list of variable_label,value pairs)<\/td>\n<\/tr>\n
    svar<\/strong><\/td>\n[-f <format>] <variable_label> <value><\/td>\n<\/tr>\n
    svar<\/strong><\/td>\n<filename><\/td>\n<\/tr>\n
    svar<\/strong><\/td>\n<\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 stdin_file \u00a0 \u00a0 \u00a0<\/td>\n<\/tr>\n
    svar<\/strong><\/td>\n[–updated_by <\/path\/to\/script>] <variable_label> <value><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<\/dd>\n<\/dl>\n

    Where:<\/h3>\n
    \n
    \n
    \n\n\n\n<\/colgroup>\n\n\n\n\n\n\n\n
    \n

    filename<\/p>\n<\/td>\n

    		\n

    Specify a text file containing an indefinite number of lines, each containing a label, value pair of entries. All the options for ‘value’ described below are supported in the file entries. This form, where the argument is NOT a redirected stdin, may contain #comment lines, blank lines, etc., similar to a normal CyFlex spec file.<\/p>\n<\/td>\n<\/tr>\n

    \n

    stdin_file<\/p>\n<\/td>\n

    		\n

    Specify a text file containing an indefinite number of lines, each containing a label, value pair of entries. All the options for ‘value’ described below are supported in the file entries. When the input file is stdin_file, #comment lines and blank lines are not ignored and will produce an error.<\/p>\n<\/td>\n<\/tr>\n

    \n

    variable_label<\/p>\n<\/td>\n

    		\n

    Specify the label of the variable to be modified. A CSAR variable label may also be specified.<\/p>\n<\/td>\n<\/tr>\n

    \n

    -f <format><\/p>\n<\/td>\n

    		\n

    Enter a format specifier. The format string must be valid for the type of variable that is being set. Only int and real type general use variables are supported.\u00a0<\/p>\n

    The format matching should be: %[flags][width][.precision][length]specifier<\/p>\n

    The ‘%’ and specifier are required.<\/p>\n

    Flags: 0, #, +, –<\/p>\n

    Width: number only, NOT *<\/p>\n

    Precision: number only, NOT .*<\/p>\n

    Length:
    \nfloating point: L
    \nintegers: h, l, j, z, t<\/p>\n

    Specifiers:
    \nfloating point: e, E, f, F, g, G, a, A
    \nintegers: d, i, u, o, x, X<\/p>\n

    Example:\u00a0
    \nsvar<\/strong> -f %10.4f myReal 12.345<\/p>\n<\/td>\n<\/tr>\n

    \n

    –updated_by <\/path\/to\/script><\/p>\n<\/td>\n

    		\n

    This argument is intended to allow the application to override the variables field for the last process to update the variable. This can make it easier if a shell script is used to call svar on variables when troubleshooting.
    \nSpecify a string, which will often be a path to a script. The path needs to be 23 characters or less. If longer than 23 characters, only the first 23 characters of the script name will be used.\u00a0<\/p>\n<\/td>\n<\/tr>\n

    \n

    value<\/p>\n<\/td>\n

    		\n

    The value to which variable is set.<\/p>\n

    For REAL or REAL_ARRAY variables, the value may be expressed in 4 different ways.<\/p>\n

      \n
    1. As a number where the units are assumed to be the same units as the target variable.\n

      Example: svar<\/strong> engine_hrs 13.5<\/p>\n

      The above command sets the hour meter to 13.5 hours<\/p>\n<\/li>\n

    2. As a number with concatenated units. The value will be converted to the units of the target variable.\n

      Example: svar<\/strong> engine_hrs 1[sec]<\/p>\n

      Assuming that engine_hrs variable has units of [hr], the result will be .0064[hr]<\/p>\n<\/li>\n

    3. As a variable label\n

      Example: svar<\/strong> engine_hrs test_hrs<\/p>\n

      The value of the test_hrs variable will be copied to the engine_hrs variable with appropriate units conversion<\/p>\n<\/li>\n

    4. As a computed expression<\/li>\n<\/ol>\n

      svar<\/strong> engine_hrs “test_hrs + 1[min]”<\/p>\n

      The quoted expression will be evaluated and the result will be placed in the engine_hrs variable with appropriate units conversion.<\/p>\n

      For INTEGER variables, the value may be entered as a decimal or hex number. Both below commands have the same result.
      \nsvar\u00a0<\/strong> count 16
      \nsvar<\/b> count 0x10<\/span><\/p>\n

      For LOGICAL variables, the value may be entered in any of the following forms:<\/span><\/p>\n

      TRUE, ON\u00a0 (not case sensitive)
      \nFALSE, OFF (not case sensitive)
      \nstate_description<\/p>\n

      svar\u00a0<\/strong>water_value\u00a0 On
      \nsvar\u00a0<\/strong> water_value\u00a0 false
      \nsvar<\/strong>\u00a0 water_value\u00a0 Open<\/p>\n

      In the last case, the string “Open” is assumed to match the “true_desc” field used when the variable was created.\u00a0 See the example output from the “gvar” command below.\u00a0 The true and false descriptions can also be obtained from the ‘dumpit’ command.<\/span><\/p>\n

      gvar water_valve
      \nwater_valve is OFF which is ‘Closed’ with status = NO, mem.index=33<\/p>\n

      ‘Closed’ is the “false_desc”<\/p>\n

       <\/p>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<\/dd>\n<\/dl>\n

      Example:<\/h3>\n

      See above descriptions for Enter<\/strong> and Where<\/strong>.<\/p>\n

      Notes:<\/h3>\n
      \n
      \n

      The svar command sets the value of the specified variable in the units of the specified variable.<\/p>\n

      Some variables have their values continuously updated by another CyFlex process, which can overwrite any value set with this command. Analog inputs are an example of variables in this category. The ‘gvar’ command will show the name of the last process which modified the variable value.<\/p>\n<\/dd>\n<\/dl>\n

      See Also:<\/h3>\n
      \n
      \n

      gvar<\/a>, rvar<\/a>, sovr<\/a>, dumpit,<\/a> override_mon<\/a>, override_status<\/a>, Array Variables<\/a><\/p>\n<\/dd>\n<\/dl>\n","protected":false},"excerpt":{"rendered":"

      Purpose: Set the value of a variable or list of variables. Only REAL, REAL_ARRAY, INTEGER, INTEGER_ARRAY, LOGICAL, LOGICAL_ARRAY, STRING, and STRING_ARRAY variable types are supported. COMPOSITION, PROPERTY, STATISTICAL and EMISSION types cannot be set with this command. Note that there are many optional ways to express the value, such as a constant, variable label, or […]<\/p>\n","protected":false},"author":47,"featured_media":0,"parent":1966,"menu_order":0,"comment_status":"closed","ping_status":"closed","template":"","meta":{"footnotes":""},"class_list":["post-3998","page","type-page","status-publish","hentry"],"post_mailing_queue_ids":[],"_links":{"self":[{"href":"https:\/\/cyflex.com\/index.php\/wp-json\/wp\/v2\/pages\/3998","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/cyflex.com\/index.php\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/cyflex.com\/index.php\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/cyflex.com\/index.php\/wp-json\/wp\/v2\/users\/47"}],"replies":[{"embeddable":true,"href":"https:\/\/cyflex.com\/index.php\/wp-json\/wp\/v2\/comments?post=3998"}],"version-history":[{"count":1,"href":"https:\/\/cyflex.com\/index.php\/wp-json\/wp\/v2\/pages\/3998\/revisions"}],"predecessor-version":[{"id":15340,"href":"https:\/\/cyflex.com\/index.php\/wp-json\/wp\/v2\/pages\/3998\/revisions\/15340"}],"up":[{"embeddable":true,"href":"https:\/\/cyflex.com\/index.php\/wp-json\/wp\/v2\/pages\/1966"}],"wp:attachment":[{"href":"https:\/\/cyflex.com\/index.php\/wp-json\/wp\/v2\/media?parent=3998"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}