myCNC Online Documentation

User Tools

Site Tools

Trace:
mycnc:mycnc_screen_configuration

Differences

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

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
Next revisionBoth sides next revision
mycnc:mycnc_screen_configuration [2019/10/25 12:55] – ivanmycnc:mycnc_screen_configuration [2019/12/19 12:37] – ivan
Line 5: Line 5:
 ==== MyCNC GUI elements ==== ==== MyCNC GUI elements ====
  
-=== Label ===+++++Label|
  
 Labels are static text elements which are displayed as a text box (typically simple text headings/titles/etc). An example of such a label can be seen in the User Settings window of the 1366M4 profile, in the Oil Change tab: Labels are static text elements which are displayed as a text box (typically simple text headings/titles/etc). An example of such a label can be seen in the User Settings window of the 1366M4 profile, in the Oil Change tab:
Line 31: Line 31:
   * **message** can be written in the required languages (which must be specified). The program will automatically display the correct message for each selected program language.    * **message** can be written in the required languages (which must be specified). The program will automatically display the correct message for each selected program language. 
  
- +++++ 
-=== Display ===+++++ Display|
  
 **Display** allows to show dynamic info (such as a changing value), and often works in conjunction with a Label (a label will create some title, and the dynamic changing value will be placed on the screen next to the Label as a Display). An example of a Display is the Trip Counter from the User Settings window in the 1336M4 profile: **Display** allows to show dynamic info (such as a changing value), and often works in conjunction with a Label (a label will create some title, and the dynamic changing value will be placed on the screen next to the Label as a Display). An example of a Display is the Trip Counter from the User Settings window in the 1336M4 profile:
Line 57: Line 57:
   * **format** specifies how the values are presented. The first number specifies the overall digits that the value will display, while the second number specifies the amount of digits after the dot. F stands for float, while d stands for integer. For example, in this case, %6.3f specifies a float number with six total digits maximum and which allows the number to display up to the third decimal place (degree of accuracy).    * **format** specifies how the values are presented. The first number specifies the overall digits that the value will display, while the second number specifies the amount of digits after the dot. F stands for float, while d stands for integer. For example, in this case, %6.3f specifies a float number with six total digits maximum and which allows the number to display up to the third decimal place (degree of accuracy). 
   * **deviation** can be specified to indicate the minimum absolute value change that would require the program to display a new value. For example, deviation of 0.01 means that the value needs to change by at lease 0.01 (absolute value) for the new numeric value to be displayed. This allows to eliminate visual changes/jumps in numbers due to small changes which can be disregarded.    * **deviation** can be specified to indicate the minimum absolute value change that would require the program to display a new value. For example, deviation of 0.01 means that the value needs to change by at lease 0.01 (absolute value) for the new numeric value to be displayed. This allows to eliminate visual changes/jumps in numbers due to small changes which can be disregarded. 
 +++++
  
-=== BDisplay ===+++++ BDisplay|
  
 The BDisplay element allows to display a dynamic value, like a typical Display, which can also be clicked. When clicked, a popup element will be brought up on the screen that will allow the user to enter a new value. For example, the program coordinates displayed on the main screen of the software are BDisplay elements which bring up a popup when clicked, allowing to change their values: The BDisplay element allows to display a dynamic value, like a typical Display, which can also be clicked. When clicked, a popup element will be brought up on the screen that will allow the user to enter a new value. For example, the program coordinates displayed on the main screen of the software are BDisplay elements which bring up a popup when clicked, allowing to change their values:
Line 83: Line 84:
   * **action** allows to perform some sort of action or command after the confirmation checkmark in the popup window is pressed (after the new value is entered). This value is stored as %v and will be used to change the program coordinates to the necessary value in the selected axis. This is extremely useful for changing the values which would require an action to do so (e.g. some kind of machine movement). If no actions are required (i.e., if all that is required is a value/variable change which does not lead to direct machine actions immediately), KDisplay can also be used.   * **action** allows to perform some sort of action or command after the confirmation checkmark in the popup window is pressed (after the new value is entered). This value is stored as %v and will be used to change the program coordinates to the necessary value in the selected axis. This is extremely useful for changing the values which would require an action to do so (e.g. some kind of machine movement). If no actions are required (i.e., if all that is required is a value/variable change which does not lead to direct machine actions immediately), KDisplay can also be used.
   * **name** specifies the global variable or the item that the element will be receiving its value from to display. In this case, it is receiving a value from the work-pos-axis-0 item. A comprehensive [[mycnc:item_list|Common Item list]] and [[mycnc:global_variables|Global Variables list]] can be used for reference in choosing a name for a BDisplay element.    * **name** specifies the global variable or the item that the element will be receiving its value from to display. In this case, it is receiving a value from the work-pos-axis-0 item. A comprehensive [[mycnc:item_list|Common Item list]] and [[mycnc:global_variables|Global Variables list]] can be used for reference in choosing a name for a BDisplay element. 
 +++++
  
-=== RadioDisplay ===+++++RadioDisplay|
  
 RadioDisplay allows to display some value from a list. For example, the display of the coordinate system in the Diagnostics window of the 1366M4 profile is done by using a RadioDisplay element. This allows the user to select some coordinate system (which is not labeled G54/G55/etc within the software, but rather 1, 2, 3, etc), and then display the selected choice as some sort of a user-facing text string (thus, for example, displaying a software "2", which would not be useful to the user without an external reference sheet, as "G55"). This is useful to "translate" machine settings or error codes into a text string that the user can easily read: RadioDisplay allows to display some value from a list. For example, the display of the coordinate system in the Diagnostics window of the 1366M4 profile is done by using a RadioDisplay element. This allows the user to select some coordinate system (which is not labeled G54/G55/etc within the software, but rather 1, 2, 3, etc), and then display the selected choice as some sort of a user-facing text string (thus, for example, displaying a software "2", which would not be useful to the user without an external reference sheet, as "G55"). This is useful to "translate" machine settings or error codes into a text string that the user can easily read:
Line 139: Line 141:
   * **action** is set to "cnc-gvariable-toggle-8225". Here, when the RadioDisplay element is clicked, the action is triggered and the global variable is toggled between 0 and 1.   * **action** is set to "cnc-gvariable-toggle-8225". Here, when the RadioDisplay element is clicked, the action is triggered and the global variable is toggled between 0 and 1.
   * **format** is set to "Rectangle;Area". This corresponds to the 0/1 toggle for the global variable, when the RadioDisplay is clicked, the visual display element also switches - however, it is important to note that it is the **action** and not the **format** which determines what actually happens to the program when the click occurs.     * **format** is set to "Rectangle;Area". This corresponds to the 0/1 toggle for the global variable, when the RadioDisplay is clicked, the visual display element also switches - however, it is important to note that it is the **action** and not the **format** which determines what actually happens to the program when the click occurs.  
 +++++
  
-=== Radio2Display ===+++++ Radio2Display |
  
 Radio2Display allows for a more granular display configuration than the simpler RadioDisplay. Similar to RadioDisplay, Radio2Display transforms some system values into a user-facing string from a list of options which are specified beforehand. For example, the step size values for the jog buttons on the main screen of the 1366M4 profile use Radio2Display elements: Radio2Display allows for a more granular display configuration than the simpler RadioDisplay. Similar to RadioDisplay, Radio2Display transforms some system values into a user-facing string from a list of options which are specified beforehand. For example, the step size values for the jog buttons on the main screen of the 1366M4 profile use Radio2Display elements:
Line 171: Line 174:
 The example in RadioDisplay code can also be used to assign actions to Radio2Display if type="radio2-display". The example in RadioDisplay code can also be used to assign actions to Radio2Display if type="radio2-display".
  
-=== KDisplay ===+++++ 
 + 
 +++++ KDisplay |
  
 KDisplay is similar to BDisplay, as it allows to display some dynamic changing variable/number and to register when it is clicked on the software screen (after which the user can enter a new value). It is different from BDisplay in that it is geared towards keyboard/mouse combos (rather than touchscreen setups) and does not bring up a full popup screen, and because it does not allow for actions to be executed after the new value has been inputted. As such, it is typically used on simple value changes which do not cause direct machine actions immediately after.  KDisplay is similar to BDisplay, as it allows to display some dynamic changing variable/number and to register when it is clicked on the software screen (after which the user can enter a new value). It is different from BDisplay in that it is geared towards keyboard/mouse combos (rather than touchscreen setups) and does not bring up a full popup screen, and because it does not allow for actions to be executed after the new value has been inputted. As such, it is typically used on simple value changes which do not cause direct machine actions immediately after. 
Line 195: Line 200:
   * **name** displays the global variable that will be used in this field (in this example, it's global variable #7525 for the gantry alignment procedure)   * **name** displays the global variable that will be used in this field (in this example, it's global variable #7525 for the gantry alignment procedure)
   * **deviation** specifies the minimum value by which the parameter (global variable used in this case) should change for the change to be visually represented on the screen. This cutoff allows to disregard some small changes.    * **deviation** specifies the minimum value by which the parameter (global variable used in this case) should change for the change to be visually represented on the screen. This cutoff allows to disregard some small changes. 
 +++++
  
-=== KSpinBox ===+++++ KSpinBox |
  
 KSpinBox shows a certain value with an arrow on either side, allowing the user to change the value upon pressing (or pressing and holding) the arrow buttons. The PWM outputs section of the Diagnostics window is done using KSpinBoxes: KSpinBox shows a certain value with an arrow on either side, allowing the user to change the value upon pressing (or pressing and holding) the arrow buttons. The PWM outputs section of the Diagnostics window is done using KSpinBoxes:
Line 224: Line 230:
   * **number** specifies the particular hardware port that the on-screen element will be monitoring. Here, it is the number of the PWM output, as specified in the address. It is counted from 0, not from 1, so PWM output 1's number is 0, PWM Output 2 is number 1, etc.   * **number** specifies the particular hardware port that the on-screen element will be monitoring. Here, it is the number of the PWM output, as specified in the address. It is counted from 0, not from 1, so PWM output 1's number is 0, PWM Output 2 is number 1, etc.
   * **type** is set to "kspinbox"   * **type** is set to "kspinbox"
 +++++
  
-=== KSpinBox2 ===+++++ KSpinBox2 |
  
 KSpinBox2 allows the user to add an element similar to a regular KSpinBox, displaying a value between two arrows, which also allows the user to click on the current value and change it using a popup screen in addition to changing the value by pressing the respective arrows. This element is used, for example, on the main screen of myCNC software's 1366M4 profile to change overspeed, jog overspeed, and spindle speed. Below is an example of such a screen element when the value in the jog overspeed box has been clicked, bringing up a popup screen: KSpinBox2 allows the user to add an element similar to a regular KSpinBox, displaying a value between two arrows, which also allows the user to click on the current value and change it using a popup screen in addition to changing the value by pressing the respective arrows. This element is used, for example, on the main screen of myCNC software's 1366M4 profile to change overspeed, jog overspeed, and spindle speed. Below is an example of such a screen element when the value in the jog overspeed box has been clicked, bringing up a popup screen:
Line 257: Line 264:
   * **orientation** can be set to be horizontal or vertical   * **orientation** can be set to be horizontal or vertical
   * the message can be listed in different languages, the system will automatically display the correct message depending on the user language settings for myCNC   * the message can be listed in different languages, the system will automatically display the correct message depending on the user language settings for myCNC
 +++++
  
-=== LED Display ===+++++ LED Display |
  
 LED Display allows the user to display an LED element on the screen. This light can be on or off, and each LED element can have a different colour set for its ON configuration. This is useful to show the state of system items which have a binary state (on or off), such as input ports which can be viewed from the Diagnostics page: LED Display allows the user to display an LED element on the screen. This light can be on or off, and each LED element can have a different colour set for its ON configuration. This is useful to show the state of system items which have a binary state (on or off), such as input ports which can be viewed from the Diagnostics page:
Line 281: Line 289:
   * **number** specifies the particular hardware port in the specified hardware section (inputs in this example) that will be monitored. Here, the state of port 0 will be monitored.    * **number** specifies the particular hardware port in the specified hardware section (inputs in this example) that will be monitored. Here, the state of port 0 will be monitored. 
   * **type** is set to "led"   * **type** is set to "led"
 +++++
  
-=== SVG Display ===+++++ SVG Display |
  
 SVG Display allows to display a set of images that will be changing depending on the user input (cycling through the available images). This allows for more granular control than an LED Display element which can only show two states of a system. SVG Display allows to display a set of images that will be changing depending on the user input (cycling through the available images). This allows for more granular control than an LED Display element which can only show two states of a system.
Line 303: Line 312:
   * **K** is the coefficient by which the value will be multiplied by before it is used by the element   * **K** is the coefficient by which the value will be multiplied by before it is used by the element
   * **min** and **max** values specify the bounds for the values which are used. Anything lower than the min value is assumed to be equal to min (displays the first image on the list), everything higher than the max value is assumed to be equal to max (displays the last image on the list).    * **min** and **max** values specify the bounds for the values which are used. Anything lower than the min value is assumed to be equal to min (displays the first image on the list), everything higher than the max value is assumed to be equal to max (displays the last image on the list). 
 +++++
  
-=== Myitems Widget ===+++++ Myitems Widget |
  
 The Myitems widget allows the user to create a section or a window within the main myCNC screen which can later be filled with buttons/display elements/etc. The Myitems widget will serve as a container which can easily be moved on the screen, opened and closed without having to write additional code for the buttons which are inside the widget if simple changes to the widget size/location are required. Most window elements are done using a myitems widget, for example, the oil change section of the window in the User Settings:  The Myitems widget allows the user to create a section or a window within the main myCNC screen which can later be filled with buttons/display elements/etc. The Myitems widget will serve as a container which can easily be moved on the screen, opened and closed without having to write additional code for the buttons which are inside the widget if simple changes to the widget size/location are required. Most window elements are done using a myitems widget, for example, the oil change section of the window in the User Settings: 
Line 336: Line 346:
   * **basewidth** and **baseheight** are specified to serve as reference width and height during the window resizing process. The system will look at the basewidth/baseheight, and compare that with the actual current width and height of the on-screen widget element. This will allow to position other elements (which are inside the widget) correctly, according to the difference between the default (base) and the actual width and height of the program window.    * **basewidth** and **baseheight** are specified to serve as reference width and height during the window resizing process. The system will look at the basewidth/baseheight, and compare that with the actual current width and height of the on-screen widget element. This will allow to position other elements (which are inside the widget) correctly, according to the difference between the default (base) and the actual width and height of the program window. 
  
-=== Button ===+++++ 
 + 
 +++++Button|
  
 A PushButton screen item can be used on myCNC screen to serve as as a button which will trigger some command when pressed. For example, the refresh button can be seen on the main screen of the myCNC software: A PushButton screen item can be used on myCNC screen to serve as as a button which will trigger some command when pressed. For example, the refresh button can be seen on the main screen of the myCNC software:
Line 364: Line 376:
     * **both** - there are separate actions (";" semicolon separated) for **pressed** and **released** events     * **both** - there are separate actions (";" semicolon separated) for **pressed** and **released** events
   * **skinbase** - besides the Image file for each button there is a common **skin** SVG file for all the buttons. For selected buttons skin file can be redefined with **skinbase** attribute which specifies the border/mask which the button will be used with. This SVG file will be used as a bottom layer for the button image.   * **skinbase** - besides the Image file for each button there is a common **skin** SVG file for all the buttons. For selected buttons skin file can be redefined with **skinbase** attribute which specifies the border/mask which the button will be used with. This SVG file will be used as a bottom layer for the button image.
 +++++
  
-=== XButton ===+++++ XButton |
  
 XButton is a Push button (similar to a typical button described above) with a built-in light indicator. The light is typically used to show the current state of some CNC controller input, output pin, or CNC global variable register value. Effectively, this combines the Button and LED Display elements, for example, in the M03 button in the 1366M4 profile. XButton is a Push button (similar to a typical button described above) with a built-in light indicator. The light is typically used to show the current state of some CNC controller input, output pin, or CNC global variable register value. Effectively, this combines the Button and LED Display elements, for example, in the M03 button in the 1366M4 profile.
Line 405: Line 418:
       * "outputs" - the light is "attached" to an output pin       * "outputs" - the light is "attached" to an output pin
       * "number" - defines the pin number than the light is attached to. A number can be assigned directly, for example \\ number="0" for pin #0 \\ number="15" for ipn #15 \\ or through pin definition file used in Hardware PLC - "pins.h". In this case sign "#" and the pin name defined in "pins.h" should be instead of pin number. For example \\ **number="#OUTPUT_SPINDLE"** \\ and "pins.h should contain this name definition, for example <code C>#define OUTPUT_SPINDLE 7</code>       * "number" - defines the pin number than the light is attached to. A number can be assigned directly, for example \\ number="0" for pin #0 \\ number="15" for ipn #15 \\ or through pin definition file used in Hardware PLC - "pins.h". In this case sign "#" and the pin name defined in "pins.h" should be instead of pin number. For example \\ **number="#OUTPUT_SPINDLE"** \\ and "pins.h should contain this name definition, for example <code C>#define OUTPUT_SPINDLE 7</code>
 +++++
  
-=== GLView ===+++++ GLView |
  
 GLView allows to display a 3D visualization window which will show a visualization of the imported program (such as the window on the main screen of myCNC software's 1366M4 profile).  GLView allows to display a 3D visualization window which will show a visualization of the imported program (such as the window on the main screen of myCNC software's 1366M4 profile). 
Line 429: Line 443:
   * **ColorT0, T1, etc** describe the visualization colours for different tools in the G-code   * **ColorT0, T1, etc** describe the visualization colours for different tools in the G-code
   * **HColorT0, T1, etc** describes the highlight colour for the selected tool   * **HColorT0, T1, etc** describes the highlight colour for the selected tool
 +++++
  
-=== NCView ===+++++ NCView |
  
 {{:mycnc:screen-config-018-2d.png}} {{:mycnc:screen-config-018-2d.png}}
Line 453: Line 468:
   * **HColor** signifies the highlight colour for each tool (colour of the tool visualization when selected - yellow in this case)   * **HColor** signifies the highlight colour for each tool (colour of the tool visualization when selected - yellow in this case)
  
-=== X-log and Logview ===+++++ X-log and Logview |
  
 Logview is the log window tab at the bottom of the main screen of myCNC software (within the x-log widget). It contains information on program start and end times, error messages, etc.  Logview is the log window tab at the bottom of the main screen of myCNC software (within the x-log widget). It contains information on program start and end times, error messages, etc. 
Line 485: Line 500:
   * **where** points out that the status bar is inserted into the x-log widget, same as the Logview element.   * **where** points out that the status bar is inserted into the x-log widget, same as the Logview element.
   * **name** and **type** are set to "statusbar"   * **name** and **type** are set to "statusbar"
- +++++ 
-=== NCList ===+++++ NCList |
  
 The NCList widget is used to display the G-code commands window to the user, as can be seen in the G-code tab on the main screen of the 1366M4 profile, as well as the nesting, rotation and Run From Here buttons:  The NCList widget is used to display the G-code commands window to the user, as can be seen in the G-code tab on the main screen of the 1366M4 profile, as well as the nesting, rotation and Run From Here buttons: 
Line 503: Line 518:
   * **type="frame"** allows to draw a frame border around the NCList window.    * **type="frame"** allows to draw a frame border around the NCList window. 
   * **hide-list** serves as an option to hide the x-log and x-mill windows when the NCList window is active (as they are all situated in the same area). The **exclusive** flag signifies that only the NCList widget will be up on the screen if it is selected, thus allowing to not interfere with x-log and x-mill windows (the same setting is present in both other respective windows).   * **hide-list** serves as an option to hide the x-log and x-mill windows when the NCList window is active (as they are all situated in the same area). The **exclusive** flag signifies that only the NCList widget will be up on the screen if it is selected, thus allowing to not interfere with x-log and x-mill windows (the same setting is present in both other respective windows).
 +++++
  
-=== CentringView ===+++++CentringView|
  
 CentringView consists of the probe tools which allow to center the machine tool with regards to some obstacles. The window is brought up by clicking the Probe Sensor Window button: CentringView consists of the probe tools which allow to center the machine tool with regards to some obstacles. The window is brought up by clicking the Probe Sensor Window button:
Line 524: Line 540:
   * **action** specifies the command which will be perform when the button is pressed (in this case, the button toggles the visibility of the x-centring widget (found in the x-centring.xml file)   * **action** specifies the command which will be perform when the button is pressed (in this case, the button toggles the visibility of the x-centring widget (found in the x-centring.xml file)
   * type is set to "button"   * type is set to "button"
 +++++
  
-=== Rotation2View ===+++++Rotation2View|
  
 Rotation2View is the window which allows to rotate the program part by some degree. It is brought up by clicking the Rotate button in the G-code tab on the main screen of myCNC software: Rotation2View is the window which allows to rotate the program part by some degree. It is brought up by clicking the Rotate button in the G-code tab on the main screen of myCNC software:
Line 531: Line 548:
 {{:mycnc:screen-config-026-rotate-button.png}} {{:mycnc:screen-config-026-rotate-button.png}}
  
-The following window is brought up when clicking the button: +The following window is brought up when clicking the button (window functions described [[mycnc:mycnc_rotate_widget|here]]): 
  
 {{:mycnc:screen-config-025-rotation2view.png}} {{:mycnc:screen-config-025-rotation2view.png}}
Line 546: Line 563:
   * **action** specifies that pressing this button will toggle the x-rotate window visibility   * **action** specifies that pressing this button will toggle the x-rotate window visibility
   * **type** is set to "button"   * **type** is set to "button"
 +++++
  
 ==== MyCNC Actions ==== ==== MyCNC Actions ====
Line 551: Line 569:
 All button-like screen components (button, xbutton, bdisplay, kspinbox2) run a **Handler** procedure when pressed or released event is activated by a mouse click or a touch screen tap. The Handler is defined in the "action" attribute of an XML configuration item.  All button-like screen components (button, xbutton, bdisplay, kspinbox2) run a **Handler** procedure when pressed or released event is activated by a mouse click or a touch screen tap. The Handler is defined in the "action" attribute of an XML configuration item. 
  
-List of actions is presented below:+++++ List of actions: |
  
 ^ Action Name ^ Description ^ ^ Action Name ^ Description ^
Line 565: Line 583:
 | toggle-item: | This is a general toggle action command for any item (item name is specified after the colon). Item list can be found [[mycnc:item_list|here]]. | | toggle-item: | This is a general toggle action command for any item (item name is specified after the colon). Item list can be found [[mycnc:item_list|here]]. |
 | laser-marker- | Special purpose action reserved for laser marker machines. This action perform a test run in anticipation of the actual cutting process. | | laser-marker- | Special purpose action reserved for laser marker machines. This action perform a test run in anticipation of the actual cutting process. |
 +++++ 
  
-===Items===+++++Items|
  
 Items are a subset of actions, and are written in the following form - item:item-name (such as //item:motion-rapid-speed-xy//). Items are different from actions in that items effectively describe a value that can be changed by some input (similar to Global Variables which store a value). In this way, there can exist both an action with some name, and an item with that same name, which are separate from one another (one will describe an action that will be taken, and the other will describe a value that will be changed by that action).  Items are a subset of actions, and are written in the following form - item:item-name (such as //item:motion-rapid-speed-xy//). Items are different from actions in that items effectively describe a value that can be changed by some input (similar to Global Variables which store a value). In this way, there can exist both an action with some name, and an item with that same name, which are separate from one another (one will describe an action that will be taken, and the other will describe a value that will be changed by that action). 
Line 575: Line 594:
  
 A list of commonly used items can be found in the [[mycnc:item_list|Item List]].  A list of commonly used items can be found in the [[mycnc:item_list|Item List]]. 
 +++++
  
-=== Player actions ===+++++ Player actions|
  
 ^ Action Name ^ Description ^ ^ Action Name ^ Description ^
Line 603: Line 623:
 | mdi-open | Opens the Manual Data Input window | | mdi-open | Opens the Manual Data Input window |
  
 +++++
  
-=== Jog actions ===+++++ Jog actions |
  
 ^ Action Name ^ Description ^ ^ Action Name ^ Description ^
 | jog-0-plus, jog-1-plus, \\ jog-2-plus, jog-3-plus, \\ jog-4-plus, jog-5-plus, \\ jog-6-plus, jog-7-plus \\ jog-8-plus | Positive direction jog in the in  the X, Y, Z, A, B, C, U, V, W axes | | jog-0-plus, jog-1-plus, \\ jog-2-plus, jog-3-plus, \\ jog-4-plus, jog-5-plus, \\ jog-6-plus, jog-7-plus \\ jog-8-plus | Positive direction jog in the in  the X, Y, Z, A, B, C, U, V, W axes |
 | jog-0-minus, jog-1-minus, \\ jog-2-minus, jog-3-minus, \\ jog-4-minus, jog-5-minus, \\ jog-6-minus, jog-7-minus, \\ jog-8-minus   | Negative direction jog in the X,Y,Z,A,B,C,U,V,W axes | | jog-0-minus, jog-1-minus, \\ jog-2-minus, jog-3-minus, \\ jog-4-minus, jog-5-minus, \\ jog-6-minus, jog-7-minus, \\ jog-8-minus   | Negative direction jog in the X,Y,Z,A,B,C,U,V,W axes |
-| jog-0-plus-1-plus | Simultaneous two-axes Jog, X+ Y+ | +| jog-0-plus-1-plus | Two-axes Jog, X+ Y+ | 
-| jog-0-plus-1-minus | Simultaneous two-axes Jog, X+ Y- | +| jog-0-plus-1-minus | Two-axes Jog, X+ Y- | 
-| jog-0-minus-1-plus | Simultaneous two-axes Jog, X- Y+ | +| jog-0-minus-1-plus | Two-axes Jog, X- Y+ | 
-| jog-0-minus-1-minus | Simultaneous two-axes Jog, X- Y- |+| jog-0-minus-1-minus | Two-axes Jog, X- Y- |
 | jog-overspeed-inc \\ jog-overspeed-dec | Increment/Decrement Jog Overspeed value (%) - the default jog speed is set to be 100%. | | jog-overspeed-inc \\ jog-overspeed-dec | Increment/Decrement Jog Overspeed value (%) - the default jog speed is set to be 100%. |
 | jog-overspeed-set:  | Set given Jog Overspeed value (%). The bounds for overspeed can be set in Settings > Config > Motion | | jog-overspeed-set:  | Set given Jog Overspeed value (%). The bounds for overspeed can be set in Settings > Config > Motion |
 +++++
  
- +++++ Motion Settings Actions |
-=== Motion Settings Actions===+
  
 ^ Action Name ^ Description ^ ^ Action Name ^ Description ^
Line 632: Line 653:
 | spindle-overspeed-inc \\ spindle-overspeed-dec \\ spindle-overspeed | Increase/decrease/set Spindle Speed (S) | | spindle-overspeed-inc \\ spindle-overspeed-dec \\ spindle-overspeed | Increase/decrease/set Spindle Speed (S) |
  
-=== Built-in Editor Actions ===+++++ 
 + 
 +++++ Built-in Editor Actions |
  
 ^ Action Name ^ Description ^ ^ Action Name ^ Description ^
Line 650: Line 673:
 | editor-save-as | Save File As | | editor-save-as | Save File As |
 | editor-save | Save the editor file | | editor-save | Save the editor file |
 +++++
  
-=== File Manipulation Actions ===+++++ File Manipulation Actions |
  
 ^ Action Name ^ Description ^ ^ Action Name ^ Description ^
Line 662: Line 686:
 | image-import | Import an image into myCNC | | image-import | Import an image into myCNC |
  
 +++++
  
-=== Visualization Actions ===+++++ Visualization Actions |
  
 ^ Action Name ^ Description ^ ^ Action Name ^ Description ^
Line 675: Line 700:
 | 3dview-custom: | 3D Visualization: show Custom view, defined by Alpha, Beta, and Gamma angles for the rotation matrix  | | 3dview-custom: | 3D Visualization: show Custom view, defined by Alpha, Beta, and Gamma angles for the rotation matrix  |
  
 +++++
  
-=== Widget Manipulations Actions ===+++++ Widget Manipulations Actions |
 These actions allow to display widgets on the screen which are then used to change certain machine values/navigate to different menus/etc. They are displayed either as popup windows on the main screen, or full windows which require navigation to return back to the main screen. These actions allow to display widgets on the screen which are then used to change certain machine values/navigate to different menus/etc. They are displayed either as popup windows on the main screen, or full windows which require navigation to return back to the main screen.
  
Line 702: Line 728:
 | mywidget: | Older version of the syntax for mywidget commands (still functional, but no longer developed further). The name of the widget would be set after the colon, and then, after a doubleslash, the show/hide/toggle command would be inserted. This has been largely replaced by the mywidget-toggle, mywidget-show and mywidget-hide syntax. | | mywidget: | Older version of the syntax for mywidget commands (still functional, but no longer developed further). The name of the widget would be set after the colon, and then, after a doubleslash, the show/hide/toggle command would be inserted. This has been largely replaced by the mywidget-toggle, mywidget-show and mywidget-hide syntax. |
  
 +++++
  
- +++++ Application Actions |
-=== Application Actions ===+
  
 ^ Action Name ^ Description ^ ^ Action Name ^ Description ^
Line 710: Line 736:
 | cnc-config-save | Save myCNC configuration files to disk | | cnc-config-save | Save myCNC configuration files to disk |
  
 +++++
  
-=== Hardware Manipulation actions ===+++++ Hardware Manipulation actions |
  
 ^ Action Name ^ Description ^ ^ Action Name ^ Description ^
Line 742: Line 769:
 | toggle-button-mist | Toggles the mist state on/off | | toggle-button-mist | Toggles the mist state on/off |
 | <del>toggle-button-cv-mode</del> | Obsolete. Used for constant velocity mode toggle. | | <del>toggle-button-cv-mode</del> | Obsolete. Used for constant velocity mode toggle. |
 +++++
  
-=== PLC Actions ===+++++ PLC Actions |
  
  
Line 757: Line 785:
 | cnc-gvariable-toggle | Toggles a global variable (writes 0 or 1 into the global variable, depending on the previous value) | | cnc-gvariable-toggle | Toggles a global variable (writes 0 or 1 into the global variable, depending on the previous value) |
 | cnc-gvariable-clear | Clears the value of a global variable | | cnc-gvariable-clear | Clears the value of a global variable |
 +++++
  
-=== Job Actions ===+++++ Job Actions |
  
 ^ Action Name ^ Description ^ ^ Action Name ^ Description ^
Line 775: Line 804:
 | mode-show-workarea | Shows a box around the program visualization which will denote the work area (useful to see the minimum material dimensions necessary to fit the entire program file in) | | mode-show-workarea | Shows a box around the program visualization which will denote the work area (useful to see the minimum material dimensions necessary to fit the entire program file in) |
  
 +++++
  
-=== OS/System Actions ===+++++ OS/System Actions |
  
 ^ Action Name ^ Description ^ ^ Action Name ^ Description ^
Line 784: Line 814:
 | application-minimize | Minimize MyCNC Application | | application-minimize | Minimize MyCNC Application |
  
 +++++
  
-=== CNC Variables manupulation Actions ===+++++ CNC Variables manupulation Actions |
  
 ^ Action Name ^ Description ^ ^ Action Name ^ Description ^
Line 803: Line 834:
 | myitem-value-inc, myitem-value-dec | Increement/Decrement XML item value by name | | myitem-value-inc, myitem-value-dec | Increement/Decrement XML item value by name |
  
-=== HMI  Actions ===+++++ 
 + 
 +++++ HMI  Actions |
  
 ^ Action Name ^ Description ^ ^ Action Name ^ Description ^
Line 820: Line 853:
 | run-from-here | **Run From Here** command - start job from the selected line | | run-from-here | **Run From Here** command - start job from the selected line |
  
 +++++
  
 ==== MyCNC screen configuration examples ==== ==== MyCNC screen configuration examples ====
 The examples for the screen configuration can be found here: [[mycnc:mycnc_screen_configuration:screen_configuration_examples|Screen configuration examples]] The examples for the screen configuration can be found here: [[mycnc:mycnc_screen_configuration:screen_configuration_examples|Screen configuration examples]]
  
mycnc/mycnc_screen_configuration.txt · Last modified: 2023/07/25 11:26 by ivan
Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki