1. Introduction

QtDragon and QtDragon_hd are built with the QtVCP framework. It is the creative vision of forum personality Persei8. Much of it is based on the excellent work of others in the LinuxCNC community. LinuxCNC’s version is adapted from Persei8’s Github versions. It is primarily meant for 3/4 axes machines such as mills or routers. It works well with a touchscreen and/or mouse. QtDragon supports multiple ways to touch off tools and probing work pieces. You can use LinuxCNC’s external offsets capability to automatically raise the spindle during a pause. If you the VersaProbe option and remap code you can add auto tool length probing at tool changes.

QtDragon and QtVcp are relatively new programs added into LinuxCNC.
Bugs and oddities are possible. Please test carefully when using a dangerous machine. Please forward reports to the forum or maillist.

1.1. QtDragon

QtDragon Router
Figure 1. QtDragon - 3 or 4 Axes Sample (1440x860) in silver theme

QtDragon has a resolution of 1440x900 and is not resizable.
It will work in window mode on any monitor with higher resolution but not on monitors with lower resolution.

1.2. QtDragon_hd

Figure 2. QtDragon_hd - 3 or 4 Axis Sample for larger monitors (1920x1056) in dark theme

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 realizable.
It will work in window mode on any monitor with higher resolution but not on monitors with lower resolution.

2. Getting Started

If your configuration is not currently set up to use QtDragon, you can change it by editing the INI file [DISPLAY] section. For an exhaustive list of options, see the display section of INI file documentation.

2.1. Display

In the section [DISPLAY] change the DISPLAY line to read:

  • qtdragon for a small version

  • qtdradon_hd for the large version.

You can add -c- or -v for debug output to the terminal.

DISPLAY = qtvcp qtdragon

2.2. Preferences

To keep track of preferences, QtDragon looks for a preference text file. add the following entry under the [DISPLAY] heading. This will save the file in the config folder of the launch screen. (other options are possible see the QtVCP’s screenoption widget docs.)


2.3. Logging

You can specify where to save history/logs. In the section [DISPLAY] add:

MDI_HISTORY_FILE = mdi_history.dat
MACHINE_LOG_PATH = machine_log.dat
LOG_FILE = qtdragon.log

2.4. Override controls

set override controls (1.0 = 100 percent):


2.5. Spindle controls

Spindle control settings (in rpm and watts):


2.6. Jogging increments

Set selectable jogging increments

INCREMENTS = Continuous, .001 mm, .01 mm, .1 mm, 1 mm, 1.0 inch, 0.1 inch, 0.01 inch
ANGULAR_INCREMENTS = 1, 5, 10, 30, 45, 90, 180, 360

2.7. Jog speed

Set jog speed controls (in units per minute)


2.8. User message dialog system

Popup Message dialogs, controlled by HAL pins. MESSAGE_TYPE can be okdialog or yesnodialog.

MESSAGE_BOLDTEXT = This is the short text
MESSAGE_TEXT = This is the longer text of the both type test. It can be longer than the status bar text
MESSAGE_TYPE = okdialog

2.9. Embed Custom VCP Panels

You can embed QtVCP Virtual Control Panels into the QtDragon or QtDragon_hd screen.
These panels can be either user built or builtin QtVCP Panels.
The TAB_NAME entry will used as the title for the new tab.
Tab TAB_LOCATION options include: tabWidget_utilities and tabWidget_setup.

This sample adds a builtin panel; a graphical animated machine using the vismach library.

EMBED_TAB_NAME = Vismach demo
EMBED_TAB_COMMAND = qtvcp vismach_mill_xyz
EMBED_TAB_LOCATION = tabWidget_utilities

2.10. Preview Control

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 gcode:


2.11. Program Extensions/Filters

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.

PROGRAM_EXTENSION = .ngc,.nc,.tap G-Code File (*.ngc,*.nc,*.tap)

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.

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:

PROGRAM_EXTENSION = .png,.gif,.jpg Greyscale Depth Image
PROGRAM_EXTENSION = .py Python Script
png = image-to-gcode
gif = image-to-gcode
jpg = image-to-gcode
py = python

2.12. Probe/Touchplate/Laser Settings

QtDragon has custom INI entries for required setup.

TOUCH = 29.7

X = 106.9
Y = -16.85

QtDragon has two optional probing tab screens:

#USE_PROBE = versaprobe
USE_PROBE = basicprobe

2.13. Macro Buttons

QtDragon has up to ten convenient macro buttons. 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. These could also call OWord routines if desired. This example shows how to move Z axis up first. The commands are separated by the ; The label is set after the comma. The symbols \n adds a line break.

# for macro buttons
MDI_COMMAND = G0 Z25;X0 Y0;Z0, Goto\nUser\nZero
MDI_COMMAND = G53 G0 Z0;G53 G0 X0 Y0,Goto\nMachn\nZero

2.14. Builtin Sample Configurations

The sample configurations sim/qtvcp_screens/qtdragon/qtdragon_xyza.ini is already configured to use QtDragon as its front-end.
There are several others, to demonstrate different machine configurations.

3. Key Bindings

QtDragon is not intended to primarily use a keyboard for machine control. It lacks many keyboatd short cuts that for instance AXIS has - but you can use a mouse. There are several key presses that will control the machine for convenience.

F1 - Estop on/off
F2 - Machine on/off
F12 - Style Editor
Home - Home All Joint of the Machine
Escape - Abort Movement
Pause -Pause Machine Movement

4. Buttons

Buttons that are checkable will change their text colour when checked.
This is controlled by the stue theme

5. Virtual Keyboard

QtDragon includes a virtual keyboard for use with touchscreens.
To enable the keyboard, check the Use Virtual Keyboard checkbox in the Settings page.
Clicking on any input field, such as probe parameters or tool table entries, will show the keyboard.
It can also be shown by clicking the KEYBD button on the top of the screen,
unless the machine is in AUTO mode. To hide the keyboard, do one of the following:

  • click the MAIN page button

  • click the KEYBD button

  • go into AUTO mode

It should be noted that keyboard jogging is disabled when using the virtual keyboard.

6. HAL Pins

These pins are specific to the QtDragon screen, There are of course are many more HAL pins that must be connected for LinuxCNC to function.

If you need a manual tool change prompt, add these lines in your postgui file.

net tool-change      hal_manualtoolchange.change   <=  iocontrol.0.tool-change
net tool-changed     hal_manualtoolchange.changed  <=  iocontrol.0.tool-changed
net tool-prep-number hal_manualtoolchange.number   <=  iocontrol.0.tool-prep-number

This input pin should be connected to indicate probe state:


These pins are inputs related to spindle VFD indicating: The volt and amp pins are used to calculate spindle power. (You must also set the MAX_SPINDLE_POWER in the INI)


This bit pin is an output to the spindle control to pause it: You would connect it to spindle.0.inhibit.


This bit output pin can be connected to turn on a laser:


This float output pin indicates the camera rotation in degrees:


These bit/s32 pins are related to external offsets if they are used:


These float output pins reflect the current slider jograte (in machine units):


These float output pins reflect the current slider override rates:


These pins are available when setting the Versa Probe INI option. They can be used for auto-tool-length-probe at tool change - with added remap code.


7. HAL files

The HAL files supplied are for simulation only. A real machine needs its own custom HAL files. The QtDragon screen works with 3 or 4 axes with one joint per axis or 3 or 4 axes in a gantry configuration. (2 joints on 1 axis)

8. Manual Tool Changes

If your machine requires manual tool changes, QtDragon can pop a message box to direct you. You must connect the proper HAL pin in the postgui HAL file. For example:

net tool-change      hal_manualtoolchange.change   <=  iocontrol.0.tool-change
net tool-changed     hal_manualtoolchange.changed  <=  iocontrol.0.tool-changed
net tool-prep-number hal_manualtoolchange.number   <=  iocontrol.0.tool-prep-number

9. Spindle

The screen is intended to interface to a VFD, but will still work without it. There are a number of VFD drivers included in the LinuxCNC distribution. It is up to the end user to supply the appropriate driver and HAL file connections according to his own machine setup.

10. Auto Raise Z Axis on Spindle Pause

QtDragon can be set up to automatically raise and lower the Z axis when the spindle is paused. When a program is paused, then you press the Spindle Pause button to stop the spindle and raise it in Z. Press the button again to start spindle and lower it, then unpause program. The amount to raise and lower is set in the Settings tab under the heading Z Ext Offset. This requires additions to the INI and the qtdragon_post_gui file.

In the INI, under the AXIS_Z heading.


In the qtdragon_postgui.hal file add:

# Set up Z axis external offsets
net eoffset_clear    qtdragon.eoffset-clear => axis.z.eoffset-clear
net eoffset_count    qtdragon.eoffset-count => axis.z.eoffset-counts
net eoffset          qtdragon.eoffset-value <= axis.z.eoffset

# uncomment for dragon_hd
#net limited          qtdragon.led-limits-tripped <= motion.eoffset-limited

setp axis.z.eoffset-enable 1
setp axis.z.eoffset-scale 1.0

11. Z level compensation

QtDragon_hd can be set up to probe and compensate for Z level height changes by utilizing the external program G-code Ripper.

This is only available in the QtDragon_hd version.

Z level compensation is a bed levelling/distortion correction function typically used in 3D printing or engraving. It uses a HAL user space component which utilizes the external offsets feature of LinuxCNC. The component has a HAL pin that specifies an interpolation type, which must be one of cubic, linear or nearest (0,1,2 respectively). If none is specified or if an invalid number is specified, the default is assumed to be cubic.

When Z LEVEL COMP is enabled, the compensation component reads a probe data file, which must be called probe_points.txt. The file can be modified or updated at any time while compensation is disabled. When next enabled, the file will be reread and the compensation map is recalculated. This file is expected to be in the configuration directory.

The probe data file is generated by a probing program which itself is generated by an external python program called gcode_ripper, which can be launched from the file manager tab using the G-code Ripper button.

11.1. Using G-code Ripper for Z level Compensation

QtDragon G-code Ripper
Figure 3. QtDragon_hd showing G-code Ripper
G-code Ripper offers many functions that we will not go in to here. This is only available in the QtDragon_hd version.
  • In Qtdragon_hd switch to the file tab and press the load G-code Ripper button.

  • set origin to match the origin of the gcode file to be probed

  • under G-Code Operations, check Auto Probe

  • File -> Open G-Code File (The file you will run after compensation)

  • if necessary, make adjustments and press Recalculate

  • press Save G-Code File - Probe Only

  • save the generated file to the nc_files folder

  • exit gcode_ripper

  • Without changing the offsets, run this program. Make sure the probe tool is installed. When complete, there will be a file in the config directory called probe_points.txt

  • In Qtdragon_hd press the Enable Z Comp button to enable compensation. Look at the status line for indication of success or failure. Active compensation will be displayed beside the label: Z Level Comp While jogging that display should change based on the compensation component.

If you use auto raise Z to lift the spindle on pause, you must combine the two with a HAL component and feed that to LinuxCNC’s motion component.

sample postgui HAL file for combined spindle raise and Z Level compensation

# load components

# load a summing component for adding spindle lift and Z compensation
loadrt scaled_s32_sums
addf scaled-s32-sums.0 servo-thread

loadusr -Wn z_level_compensation z_level_compensation
# method parameter must be one of nearest(2), linear(1), cubic (0)
setp z_level_compensation.method 1
setp z_level_compensation.fade-height 0.0

# connect signals to LinuxCNC's motion component

net eoffset-clear    axis.z.eoffset-clear
net eoffset-counts   axis.z.eoffset-counts
setp axis.z.eoffset-scale .001
net eoffset-total          axis.z.eoffset
setp axis.z.eoffset-enable True

# external offsets for spindle pause function
net eoffset-spindle-count   <= qtdragon.eoffset-spindle-count

# Z level compensation
net xpos-cmd                z_level_compensation.x-pos      <= axis.x.pos-cmd
net ypos-cmd                z_level_compensation.y-pos      <= axis.y.pos-cmd
net zpos-cmd                z_level_compensation.z-pos      <= axis.z.pos-cmd
net z_compensation_on       z_level_compensation.enable-in  <= qtdragon.comp-on
net eoffset-zlevel-count    z_level_compensation.counts     => qtdragon.eoffset-zlevel-count

# set up scaled sum component
net eoffset-spindle-count   scaled-s32-sums.0.in0
net eoffset-zlevel-count    scaled-s32-sums.0.in1       qtdragon.eoffset-value
setp scaled-s32-sums.0.scale0 1000
net eoffset-counts          scaled-s32-sums.0.out-s

12. Probing

The probe screen has been through basic testing but there could still be some minor bugs. When running probing routines, use extreme caution until you are familiar with how everything works. Probe routines run without blocking the main GUI. This gives the operator the opportunity to watch the DROs and stop the routine at any time.

Probing is very unforgiving to mistakes; be sure to check settings before using.
QtDragon Probe
Figure 4. QtDragon - Probe Sample

QtDragon has 2 possible methods for setting Z0. The first is a touchplate, where a metal plate of known thickness is placed on top of the workpiece and then the tool is lowered until it touches the plate, triggering the probe signal. Z0 is set to probe height - plate thickness.

The second method uses a tool setter in a fixed position and a known height above the table where the probe signal will be triggered. In order to set Z0 to the top of the workpiece, it has to know how far above the table the probe trigger point is (tool setter height) and how far above the table the top of the workpiece is. This operation has to be done every time the tool is changed as the tool length is not saved.

For touching off with a touch probe, whether you use the touchplate operation with thickness set to 0 or use a probing routine, the height from table to top of workpiece parameter is not taken into account and can be ignored. It is only for the tool setter.

13. Touch plate

QtDragon Touch Plate
Figure 5. QtDragon - Touch Plate

You can use a conductive touch plate or equivalent to auto touch off (zero the user coordinate) for the Z position of a tool. There must be a tool loaded prior to probing. In the tool tab or settings tab, set the touch plate height, search and probe velocity and Max probing distance.

When using a conductive plate the search and probe velocity should be the same and slow. If using a tool setter that has spring loaded travel then you can set search velocity faster. LinuxCNC ramps speed down at the maximum acceleration rate, so there can be travel after the probe trip if the speed is set to high.

Place the plate on top of the surface you wish to zero Z on. Connect the probe input wire to the tool (if using a conductive plate) There is a LED to confirm the probe connection is reliable prior to probing. Move the tool manually within the max probe distance. Press the Touch Plate button. The machine will probe down twice and the current user offset (G5X) will be zeroed at the bottom of the plate by calculation from the touchplate height setting.

14. Auto Tool Measurement

QtDragon can be setup to do integrated auto tool measurement using the Versa Probe widget. To use this feature, you will need to do some additional settings and you may want to use the offered HAL pin to get values in your own ngc remap procedure.

Before starting the first test, do not forget to enter the probe height and probe velocities on the versa probe settings page.

Tool Measurement in QtDragon is done with the following steps:

  • touch of you workpiece in X and Y

  • measure the height of your block from the base where your tool switch is located, to the upper face of the block (including chuck etc.)

  • In the Versa probe tab, enter the measured value for block height

  • Make sure the use tool measurement button in the Vesa probe tab is enabled

  • Go to auto mode and start your program

When fist setting up auto tool measurement, please use caution until you confirm tool change and probe locations - it’s easy to break a tool/probe. Abort will be honoured while the probe is in motion.
Figure 6. Auto tool measurement

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.

Your program must contain a tool change at the beginning. The tool will be measured, even it has been used before, so there is no danger if the block height has changed. There are several videos on you tube that demonstrate the technique using Gmoccapy. The Gmoccapy screen pioneered the technique.

14.1. Work Piece Height Probing

QtDragon_hd height probing
Figure 7. QtDragon_hd - Work piece Height probing

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

This is only available in the QtDragon_hd version.

Enable Probe Position Set Buttons

  • when checked, the SET buttons are enabled

  • this allows the user to automatically fill in the X, Y and Z parameters with the current position as displayed on the DROs.

Autofill Workpiece Height on Main Screen

  • when checked, the calculated height is automatically transferred to the Workpice Height field in the main screen.

  • otherwise, the main screen is not affected

Workpiece Probe At

  • the X, Y and Z coordinates specify where the first probing routine should start, in current WCS

Machine Probe At

  • the X, Y and Z coordinates specify where the second probing routine should start, in current WCS

Z Safe Travel Height

  • the machine is raised to the Z safe travel height before jogging to the X and Y coordinates

  • the spindle then lowers to the specified Z coordinate

  • it should be selected so that the tool clears all obstructions while jogging

START button

  • the machine will jog to the first location and then probe down

  • the machine then jogs to the second location and probes down again

  • the difference in probed values is reported as Calculated Workpiece Height

  • the parameters for search velocity, probe velocity, maximum probe distance and return distance are read from the main GUI Settings page.

ABORT button

  • causes all jog and probe routines currently executing to stop

HELP button

  • displays this help file

Any 2 points within the machine operating volume can be specified. If the first point is higher than the second, the calculated height will be a positive number. If the first point is lower than the second, the calculated height will be a negative number. Units are irrelevant in this program. The probed values are not saved and only the difference is reported.
Setting incorrect values can lead to crashes into fixtures on the machine work surface. Initial testing with no tool and safe heights is recommended.

14.2. Tool Measurement Pins

Versaprobe offers 5 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.

  • qtversaprobe.toolmeasurement HAL_BIT enable or not tool measurement

  • qtversaprobe.blockheight HAL_FLOAT the measured value of the top face of the workpiece

  • qtversaprobe.probeheight HAL_FLOAT the probe switch height

  • qtversaprobe.searchvel HAL_FLOAT the velocity to search for the tool probe switch

  • qtversaprobe.probevel HAL_FLOAT the velocity to probe tool length

14.3. Tool Measurement INI File Modifications

Modify your INI File to include the following:

14.3.1. The PROBE section

QtDragon allows you to select one of two styles of touch probe routines. Versa probe works with a M6 remap to add auto tool probing.

USE_PROBE = versaprobe

14.3.2. The RS274NGC section


# adjust this paths to point to folders with stdglu.py and qt_auto_tool_probe.ngc
# or similarly coded custom remap files
SUBROUTINE_PATH = ~/linuxcnc/nc_files/remap-subroutines:~/linuxcnc/nc_files/remap_lib

# is the sub, with is called when a error during tool change happens, not needed on every machine configuration
ON_ABORT_COMMAND=O <on_abort> call

# The remap code for QtVCP's versaprobe's automatic tool probe of Z
REMAP=M6  modalgroup=6 prolog=change_prolog ngc=qt_auto_probe_tool epilog=change_epilog

14.3.3. The Tool Sensor Section

The position of the tool sensor and the start position of the probing movement, all values are absolute (G53) coordinates, except MAXPROBE, what must be given in relative movement. All values are in machine native units.

X = 10
Y = 10
Z = -20

14.3.4. The Change Position Section

This is not named TOOL_CHANGE_POSITION on purpose - canon uses that name and will interfere otherwise. The position to move the machine before giving the change tool command. All values are in absolute coordinates. All values are in machine native units.

X = 10
Y = 10
Z = -2

14.3.5. The Python Section

The Python section sets up what files LinuxCNC’s Python interpreter looks for. ie. toplevel.py file in the python folder in the configuration directory:

# The path to start a search for user modules
# The start point for all.
TOPLEVEL = python/toplevel.py

14.4. Needed Files

You must copy the following files to your config directory

First create a folder named python in your machine’s configuration folder.

If using a compiled RIP version of LinuxCNC:
From YOUR-LINUXCNC-DIRECTORY/configs/sim/QtDragon/python, copy toplevel.py and remap.py to your configuration’s new python folder.

if using an installed version of LinuxCNC:
from /usr/share/doc/linuxcnc/examples/sample-configs/sim/qtvcp_screens/qtdragon/python/ , copy toplevel.py and remap.py to your configuration’s new python folder.

Alternately, you can make new files in your python folder that you made in your configuration folder, with a text editor.

One named remap.py saved with this text:

from stdglue import *

One named toplevel.py saved with this text:

import remap

Make a symbolic link or copy the following files into the python folder described above.

In ~/linuxcnc/nc_files/examples/remap_subroutine/ folder

In ~/linuxcnc/nc_files/examples/remap_lib/python_stdglue/ folder

These file names and location could be different depending on installed verses development (RIP) version of LinuxCNC. For instance –/linuxcnc/nc_files/macros is –/linuxcnc/nc_files/examples/macros in installed versions of LinuxCNC. You could use customized versions of the same files or name them differently. The entries in the [RS274NGC] section dictate to LinuxCNC what and where to look. The names and location quoted should be available in either system by default.

14.5. Needed HAL Connections

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.

net probe  motion.probe-input <= <your_input_pin>

15. Run from Line

A G-code program can be started at any line by clicking on the desired line in the G-code display while in AUTO mode. It is the operator’s responsibility to ensure the machine is in the desired operational mode. A dialog will be shown allowing the spindle direction and speed to be preset. The start line is indicated in the box labelled LINE, next to the CYCLE START button. The run from line feature can be disabled in the settings page.

LinuxCNC’s run-from-line is not very user friendly. E.g., it does not start the spindle or confirm the proper tool. Also, it does not handle subroutines well. If used it is best to start on a rapid move.

16. Laser buttons

The LASER ON/OFF button in intended to turn an output on or off which is connected to a small laser crosshair projector. When the crosshair is positioned over a desired reference point on the workpiece, the REF LASER button can be pushed which then sets the X and Y offsets to the values indicated by the LASER OFFSET fields in the Settings page and the INI file.

17. Tabs Description

Tabs allow the user to select the most appropriate info/control on the top three panels.
If the on screen keyboard is showing and the user wishes to hide it but keep the current tab,
they can do that by pressing the current show tab.

17.1. Main tab

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

  • User View: Select/restore a user set view of the current program

  • P,X,Y,Z: Set standard views

  • D: Toggle display of dimensions

  • +, -: Zoom controls

  • C: Clear graphics of tool movement lines

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

17.2. File Tab

You can use this tab to load or transfer programs.
Editing of G-code programs can be selected from this tab.

17.3. Offsets Tab

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

17.4. Tool Tab

You can monitor/modify tool offsets from this tab.
Adding and deleting tools from the tool file can also be done from this tab.

17.5. Status Tab

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.

17.6. Probe Tab

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.

17.7. Camview Tab

If the recognized webcam is connected, this tab will display the video image overlayed 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.

17.8. G-codes Tab

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.

17.9. Setup Tab

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

QtDragon Setup Tab
Figure 8. QtDragon - Setup Tab Sample

17.10. Settings Tab

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

17.11. Utilities Tab

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

  • Facing: allows quick face milling of a definable area at angles of 0,45 and 90 degrees

  • Hole Circle: allows quick setting of a program to drill a bolt circle of definable diameter and number of holes.

  • NGCGUI: is a QtVCP version of the popular G-code subroutine builder/selector.

18. Styles

Nearly all aspects of the GUI appearance are configurable via the QtDragon.qss stylesheet file. The file can be edited manually or through the stylesheet dialog widget in the GUI. To call up the dialog, press F12 on the main window. New styles can be applied temporarily and then saved to a new qss file, or overwrite the current qss file.

QtDragon styles
Figure 9. QtDragon - Two Style Examples

19. Customization

19.1. Stylesheets

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. For instance:

To change the DRO font (look for this entry and change the font name):

StatusLabel#status_rpm {
    border: 1px solid black;
    border-radius: 4px;
    font: 20pt "Noto Mono";

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

qproperty-true_state_string: "Air\\nOn";
qproperty-false_state_string: "Air\\nOff";

19.2. Qt Designer and Python code

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. QtVCP Overview for more information

QtDragon customized
Figure 10. QtDragon - Customized QtDragon