Scribd Logo
Upload

Welcome to Scribd!

  • 70 views

    SINUMERIK Integrate Run MyScreens - 1

    Uploaded by

    Suresh Ramachandran
    The document provides recommendations for writing efficient and high-performing code for SINUMERIK Integrate Run MyScreens programs. It advises using system variables over complex names, only updating screen properties when values change, combining multiple read/write functions, avoiding fast drive parameter reads, and separating repeated code into subroutines to reduce load. Monitoring CPU load can reveal performance impacts of code changes.

    Copyright:

    © All Rights Reserved
    Download as PDF, TXT or read online from Scribd

    SINUMERIK Integrate Run MyScreens - 1

    Uploaded by

    Suresh Ramachandran
    70 views2 pages
    The document provides recommendations for writing efficient and high-performing code for SINUMERIK Integrate Run MyScreens programs. It advises using system variables over complex names, only updating screen properties when values change, combining multiple read/write functions, avoiding fast drive parameter reads, and separating repeated code into subroutines to reduce load. Monitoring CPU load can reveal performance impacts of code changes.

    Original Title

    SINUMERIK Integrate Run MyScreens_1

    Copyright

    © © All Rights Reserved

    Available Formats

    PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    The document provides recommendations for writing efficient and high-performing code for SINUMERIK Integrate Run MyScreens programs. It advises using system variables over complex names, only updating screen properties when values change, combining multiple read/write functions, avoiding fast drive parameter reads, and separating repeated code into subroutines to reduce load. Monitoring CPU load can reveal performance impacts of code changes.

    Copyright:

    © All Rights Reserved
    Download as PDF, TXT or read online from Scribd
    Download as pdf or txt
    70 views2 pages

    SINUMERIK Integrate Run MyScreens - 1

    Uploaded by

    Suresh Ramachandran
    The document provides recommendations for writing efficient and high-performing code for SINUMERIK Integrate Run MyScreens programs. It advises using system variables over complex names, only updating screen properties when values change, combining multiple read/write functions, avoiding fast drive parameter reads, and separating repeated code into subroutines to reduce load. Monitoring CPU load can reveal performance impacts of code changes.

    Copyright:

    © All Rights Reserved
    Download as PDF, TXT or read online from Scribd
    Download as pdf or txt
    You are on page 1of 2

    12/17/21, 4:39 PM SINUMERIK Integrate Run MyScreens

    I​f possible, use the OPI version for system variables ($ variables).
    ​Reason:
    ​Avoids complex name resolution.
    ​Example:
    ​Instead of
    "$R[10]", it is better to use "/Channel/Parameter/R[u1,10]".

    ​ voids cyclic (similar) setting, e.g. of the screen and variable HLP property. Compare the value to be
    A
    set with the current value first, and only set it when it is different.
    ​Reason:
    ​Avoid a
    time-consuming search of the resolution-dependent help screens.
    ​Example:

    DEF MyVar=(R3///,"X1",,"mm"/WR1//"$AA_IM[0]")
    CHANGE(MyVar)
    IF MyVar.VAL < 100
    HLP="mypic1.png"
    ELSE
    HLP="mypic2.png"
    ENDIF
    END_CHANGE

    Recommendation:
    CHANGE(MyVar)
    IF MyVar.VAL < 100
    IF HLP <> "mypic1.png"
      HLP="mypic1.png"
    ENDIF
    ELSE
    IF HLP <> "smypic2.png"
    HLP="mypic2.png"
    ENDIF
    ENDIF
    END_CHANGE

    ​ eplace several RNP() functions in succession with one MRNP() function.


    R
    ​Replace several RDOP() functions in succession with one MRDOP() function.
    ​Reason:
    ​Reduces the communication load and increases the performance.

    ​ o not read drive parameters faster than in a 1 second cycle, slower is better.
    D
    ​Reason: The communication with the drives can otherwise be extremely disturbed or even cause
    failures.

    ​ void successive arithmetic operations with system or user variable-connected dialog variables.
    A
    Use, for example, register (REG[x]) or (invisible) help variables for this.

    https://cache.industry.siemens.com/dl/dl-media/123/109803123/att_1083101/v1/828D_Run_MyScreens_progr_man_0721_en-US/en-US/index.html# 1/2
    12/17/21, 4:39 PM SINUMERIK Integrate Run MyScreens
    ​ eason: Each assignment of a value results in a write operation in the connected system or user
    R
    variable.

    ​ imilar code used in different blocks should be combined in a SUB block for reasons of
    S
    transparency, serviceability and performance (when displaying the screen). It can then be called at
    the appropriate positions with the CALL() function.

    ​ y monitoring the CPU load in the dialog line (setting in slguiconfig.xml), it is possible to investigate
    B
    the effects of changes in the screen on the performance.

    https://cache.industry.siemens.com/dl/dl-media/123/109803123/att_1083101/v1/828D_Run_MyScreens_progr_man_0721_en-US/en-US/index.html# 2/2

    You might also like