QtDragon GUI

QtDragon is resizable from a resolution of 1280x768 to 1680x1200. It will work in window mode on any monitor with higher resolution but not on monitors with lower resolution.

QtDragon_hd is a similar design as QtDragon but modified to utilize the extra space of modern larger monitors. There are some small differences in layout and utility.

QtDragon_hd has a resolution of 1920x1056 and is not resizeable. It will work in window mode on any monitor with higher resolution but not on monitors with lower resolution.

In the section [DISPLAY] change the DISPLAY = assignment to read:

You can add -v, -d, -i, or -q for (respectably) verbose, debug, info or quiet output to the terminal.

To keep track of preferences, QtDragon looks for a preference text file. Add the following entry under the [DISPLAY] heading.
It can use ~ for home directory or WORKINGFOLDER or CONFIGFOLDER to represent QtVCP’s idea of those directories:
This example will save the file in the config folder of the launch screen. (Other options are possible see the QtVCP’s screenoption widget docs.)

You can specify where to save history/logs.
These file names can be user selected.
In the section [DISPLAY] add:

These set qtdragon’s override controls (1.0 = 100 percent):

Spindle control settings (in rpm and watts):

Set selectable jogging increments.
These increments can be user changed.

Set jog speed controls (in units per second)

Optional popup custom message dialogs, controlled by HAL pins.
MESSAGE_TYPE can be okdialog or yesnodialog. See qtvcp/library/messages for more information.
This example shows how to make a dialog that requires the user to select ok to acknowledge and hide.
These dialogs could be used for such things as low lube oil warnings, etc.

Multimessages use an s32 HAL pin to pop multiple defined messages.

You can optionally embed QtVCP Virtual Control Panels into the QtDragon or QtDragon_hd screen.
These panels can be either user built or builtin QtVCP Panels.
See QtVCP/VCP panels for other available builtin panels.

The EMBED_TAB_NAME entry will used as the title for the new tab.(must be unique)
Tab EMBED_TAB_LOCATION options include: tabWidget_utilities, tabWidget_setup and stackedWidget_mainTab.
Tab EMBED_TAB_COMMAND specifies what embed-able program to run, including any of its command line options.

If using the tabWidget_utilities or tabWidget_setup locations, an extra tab will appear with the panel.
If using stackedWidget_mainTab, a button labelled User will appear.
Pressing this button will cycle through displaying all available panels (specified for this location) on the main tab area.

If using NGCGUI, remap or custom M codes routines, LinuxCNC needs to know where to look for the files.
This sample is typical of what is needed for NgcGui, Basic Probe. and Versa Probe remap code.
These paths will need to be adjusted to point to the actual files on your system. RS274NZGC Section Details

QtVCP’s NGCGUI program also need to know where to open for subroutine selection and pre-selection.
NGCGUI_SUBFILE_PATH must point to an actual path on your system and also a path described in SUBROUTINE_PATHS.

Magic comments can be used to control the G-code preview.

On very large programs the preview can take a long time to load. You can control what is shown and what is hidden the the graphics screen by adding the appropriate comments from this list into your G-code:

You can control what programs are displayed in the filemanager window with program extensions.
Create a line with the . endings you wish to use separated by commas, then a space and the description.
You can add multiple lines for different selections in the combo box.

QtDragon has the ability to send loaded files through a filter program. This filter can do any desired task: Something as simple as making sure the file ends with M2, or something as complicated as generating G-code from an image. See Filter Programs for more information.

The [FILTER] section of the INI file controls how filters work. First, for each type of file, write a PROGRAM_EXTENSION line. Then, specify the program to execute for each type of file. This program is given the name of the input file as its first argument, and must write rs274ngc code to standard output. This output is what will be displayed in the text area, previewed in the display area, and executed by LinuxCNC when Run.

The following lines add support for the image-to-gcode converter included with LinuxCNC and running Python based filter programs:

QtDragon has INI entries for two optional probing tab screens available. Comment/uncomment which ever you prefer.

Both perform similar probing routines, though Versa probe optionally handles auto tool measurement.

When using qtdragon’s probing routines, it is important to detect a user abort request.
By default, LinuxCNC does not report an abort in a useful way for the probe routines.
You need to add a ngc file to print out an error that can be detected. Remap Abort Details

This example code will send a message on abort. The probe routines can detect this sample.
According to the setting above, it would need to be saved as on_abort.ngc within LinuxCNC’s [RS274NGC] SUBROUTINE_PATHS and [DISPLAY] PROGRAM_PREFIX search paths.

You should set default M/G code for start up. These will be overridden by running a NGC file.
These are only sample codes, integrator should choose appropriate codes.

QtDragon has up to ten convenience buttons for calling macro actions.
These are under the heading [MDI_COMMAND_LIST] as MDI_COMMAND_MACRO0 = to MDI_COMMAND_MACRO9 =
These could also call OWord routines if desired.
In the sample configurations they are labelled for moving between current user system origin (zero point) and Machine system origin.
User origin is the first MDI command in the INI list, machine origin is the second.
This example shows how to move Z axis up first. Commands separated by the ; are run one after another.
The button label text can be set with any text after a comma, the \n symbol adds a line break.

These optional HAL files will be called after QtDragon has loaded everything else.
You can add multiple line for multiple file. Each one will be called in the order they appear.
Calling HAL files after QtDragon is already loaded assures that QtDragon’s HAL pins are available.

These optional HAL commands will be run after QtDragon has loaded everything else.
You can add multiple line. Each one will be called in the order they appear.
Any HAL command can be used.

The sample configurations sim/qtdragon/ or sim/qtdragon_hd are already configured to use QtDragon as the screen. There are several examples that demonstrate various machine configurations.

Versa probe is used to semi-automatically probe work pieces to find edges, centers and angles.
It can also be sued to auto probe tool length at tool changes with added remap code.

You must carefully set the Probing Parameters:

There are three toggle buttons:

Basic probe is used to semi-automatically probe work pieces to find edges, centers and angles. The combo box allows selecting the basic type of probing buttons shown:

You must carefully set the Probing Parameters:

There are also hint parameters depending on selected probing type:

After setting the parameters and hints:

The probing routine will start immediately.

QtDragon can be setup to do integrated auto tool measurement using the Versa Probe widget and remap code.

This feature assumes the use of two probes in concert:

These techniques are useful for machines that do not have repeatable tool holders and do not have automatic tool changing devices. (For machines with repeatable tool holders, see the section on measuring tool length. For machines with automatic tool changing devices, consult work done under the LinuxCNC repository at configs/sim/axis/remap/rack-toolchange.)

Чтобы использовать эту функцию, вам нужно будет сделать некоторые дополнительные настройки, и вы можете захотеть использовать предлагаемые контакты HAL для получения значений в вашей собственной процедуре переназначения ngc. Эти настройки рассматриваются далее в разделе.

First, this document covers how to use this technique. Second, this document covers how to set up for this technique at the beginning of a production run.

A detailed workflow walkthrough follows this overview.

Setup steps include:

Tool Measurement in QtDragon is organized into the following steps which will be explained in more detail in the following section:

With the first given tool change the tool will be measured and the offset will be set automatically to fit the block height. The advantage of this way is, that you do not need a reference tool.

The sequence of events (using the default files in the default setting):

The [TOOL_CHANGE] Z position should be high enough so the tool will not hit the tool probe when moving to the [VERSA_TOOLSETTER] X and Y position. MAXPROBE distance needs to be high enough for the tool to touch the probe.

This program probes 2 user specified locations in the Z axis and calculates the difference in heights.

Versaprobe offers 5 output pins for tool measurement purpose. The pins are used to be read from a remap G-code subroutine, so the code can react to different values.

Modify your INI file to include the following:

Make sure to connect the tool probe input in your HAL file: If connected properly, you should be able to toggle the probe LED in QtDragon if you press the probe stylus.

This tab displays the graphical representation of the current program. The side buttons will control the display.

In qtdragon_hd there are also macro buttons available on the right side. Up to tens buttons can be defined in the INI.

You can use this tab to load or transfer programs. Editing of G-code programs can be selected from this tab. With qtdragon_hd, this is where you can load the G-code Ripper.

You can monitor/modify system offsets from this tab. There are convenience buttons for zeroing the rotation.G92 and current G5x user offset.

You can monitor/modify tool offsets from this tab. Adding and deleting tools from the tool file can also be done from this tab. When this tab is selected the individual home buttons in the DRO area will change to tool offset setting buttons. They will return to home buttons when you select another tab. Pressing this tool button will drop down a when menu of options:

A time-stamped log of important machine or system events will be shown here. Machine events would be more suited to an operator, where the system events may help in debugging problems.

Probing routines options are displayed on this tab. Depending on INI options, this could be VersaProbe or BasicProbe style. They are functionally similar. QtDragon_hd will also show a smaller graphics display window.

If the recognized webcam is connected, this tab will display the video image overlaid with a cross-hair, circle and degree readout. This can be adjusted to suit a part feature for such things as touchoff. The underlying library uses openCV Python module to connect to the webcam.
To adjust the X or Y size aspect ratio, or camera number, look in the preference file for:

These are in percent, usually the range will be 100 - 200 in one axis.
Negating these scales can be used to flip the image in X, Y or both axes.
The preference file can only be edited when QtDragon is not running.

This tab will display a list of LinuxCNC’s G-code. if you click on a line, a description of the code will be displayed.

It’s possible to load HTML or PDF file (.html / .pdf ending) with setup notes, and will be displayed in the setup tab.
If you load a G-code program and there is an HTML/PDF file of the same name, it will load automatically.
Some program, such as Fusion 360 and Aspire will create these files for you. You can also write your own HTML docs with the included SetUp Writer button.
There are three sub tabs:

There are navigation buttons for HTML page:

If you wish to include a custom default HTML page, name it default_setup.html and place it in your configuration folder.
Custom QtVCP panels can be displayed in this tab by setting the EMBED_TAB_LOCATION option to tabWidget_setup.

The settings tab is used to set running options, probing/touchplate/laser/camera offsets and load debugging external programs.

This tabs will display another stab election of G-code utility programs:

Custom QtVCP panels can be displayed here by setting the EMBED_TAB_LOCATION option to tabWidget_utilities

This tab will only be displayed if an embedded panel has been designated for the location stackedWidget_mainTab. If more then one embedded tab has been designated, then pressing the user tab will cycle through them.

Stylesheets can be leveraged to do a fair amount of customization, but you usually need to know a bit about the widget names. Pressing F12 will display a stylesheet editor dialog to load/test/save modification.
The View Sheet tab will allow you to select and apply what stylesheet QtDragon will use when it’s first loaded.
Press the button Copy to Edit Tab to copy the current stylesheet to the edit tab.
The Edit Sheet tab allows editing, applying and saving of changes od the displayed stylesheet.

Sometimes these lines will be present and you can change them, otherwise you will need to add them.

For instance, to change the DRO font (look for this entry and change the font name):

To change the DRO display font and display format:

Change the axis select button’s click menu items:

To change the text of the mist button to air (add these lines)

To change the Offsets display font and format:

To stop the blur effect with dialogs:

To change status highlight/selection colors:

Change the G-code text display colors/fonts:

To have the manual spindle buttons also incrementally increase/decrease speed:

All aspects of the GUI are fully customization through Qt Designer and/or Python code. This capability is included with the QtVCP development environment. The extensive use of QtVCP widgets keeps the amount of required Python code to a minimum, allowing relatively easy modifications. The LinuxCNC website has extensive documentation on the installation and use of QtVCP libraries. See QtVCP for more information about QtVCP in general.
QtDragon can also utilize QtVCP’s rc file to do minor python code modifications without using a custom handler file.

See Modifying Screens for more information about customization.