Tool touch-off in QTDragon
Also, the dialog that comes up when you press the Touch-Plate button displays in white on off-white and can barely be read.
Any help would be appreciated. I will keep digging.
Thank You
John
Please Log in or Create an account to join the conversation.
Please Log in or Create an account to join the conversation.
As for the dialog, add the following to your stylesheet.
QDialog {
background-color: gray;
}
QDialog QPushButton {
width: 100px;
height: 40px;
}
Please Log in or Create an account to join the conversation.
I noticed something else. I have my machine units set to inch and at the end of the probe action using the Touch-Plate button on the Tool screen it switches to Metric.
In 2.8 the macros for probing are in nc_files/probe/basicprobe/macros
[RS274NGC]
SUBROUTINE_PATH = ../../../../nc_files/probe/basic_probe/macros
looking at the macro for touch_plate.ngc:
o<touch_plate> sub
#<max_probe> = #<_ini[TOOLSENSOR]maxprobe>
#<search_vel> = #<_ini[TOOLSENSOR]search_vel>
#<probe_vel> = #<_ini[TOOLSENSOR]probe_vel>
#<touch_height> = #<_ini[TOOLSENSOR]touch>
(print, max_probe is #<max_probe>)
(print, search vel is #<search_vel>)
(print, probe vel is #<probe_vel>)
(print, touch height is #<touch_height>)
G21 (use metric units)
G49 (cancel tool offset)
G10 L20 P0 Z0 (clear current offsets)
G91 (switch to incremental mode)
; this section commented out for sim
;G38.2 Z[-#<max_probe>] F#<search_vel> (probe down)
;G1 Z1.0 (go up 1 mm)
;G4 P0.5 (pause 0.5 sec.)
;G38.2 Z-2 F#<probe_vel> (probe down slower)
; this section used for sim, comment out otherwise
G1 Z-10 F#<search_vel>
G10 L20 P0 Z#<touch_height> (store offset in offset table)
G90 (absolute distance mode)
G53 G0 Z0 (move Z up to 0)
o<touch_plate> endsub
M2
It sets metric for it's process.
I'm sure there is away to record the current units before and restore them after.
Chris
Please Log in or Create an account to join the conversation.
QtDragon was never intended to be used with an ATC but I could certainly look into it. It would only affect the tool table when using a tool setter, not a touchplate.
As for the dialog, add the following to your stylesheet.
Adjust the color or any other parameters you like to suit whatever stylesheet you're using.QDialog { background-color: gray; } QDialog QPushButton { width: 100px; height: 40px; }
I will still be the "MTC" but I did want to try preset tools. The dialog looks a lot like I remember a couple of the other dialogs looking until Chris made a change. I knew the colors were controlled by style sheets but have never messed with them. I'll give it a try.
Thanks
Please Log in or Create an account to join the conversation.
I noticed something else. I have my machine units set to inch and at the end of the probe action using the Touch-Plate button on the Tool screen it switches to Metric.
In 2.8 the macros for probing are in nc_files/probe/basicprobe/macros[RS274NGC] SUBROUTINE_PATH = ../../../../nc_files/probe/basic_probe/macros
looking at the macro for touch_plate.ngc:
o<touch_plate> sub #<max_probe> = #<_ini[TOOLSENSOR]maxprobe> #<search_vel> = #<_ini[TOOLSENSOR]search_vel> #<probe_vel> = #<_ini[TOOLSENSOR]probe_vel> #<touch_height> = #<_ini[TOOLSENSOR]touch> (print, max_probe is #<max_probe>) (print, search vel is #<search_vel>) (print, probe vel is #<probe_vel>) (print, touch height is #<touch_height>) G21 (use metric units) G49 (cancel tool offset) G10 L20 P0 Z0 (clear current offsets) G91 (switch to incremental mode) ; this section commented out for sim ;G38.2 Z[-#<max_probe>] F#<search_vel> (probe down) ;G1 Z1.0 (go up 1 mm) ;G4 P0.5 (pause 0.5 sec.) ;G38.2 Z-2 F#<probe_vel> (probe down slower) ; this section used for sim, comment out otherwise G1 Z-10 F#<search_vel> G10 L20 P0 Z#<touch_height> (store offset in offset table) G90 (absolute distance mode) G53 G0 Z0 (move Z up to 0) o<touch_plate> endsub M2
It sets metric for it's process.
I'm sure there is away to record the current units before and restore them after.
Chris
I did get probing working quite well with my 3D probe. I did see the macros you pointed me to. I'll have a look at this and tweak for my purposes. Just as much a learning experience as getting it to do what I want.
Thanks
And Merry Christmas to all.
Please Log in or Create an account to join the conversation.
Please Log in or Create an account to join the conversation.
I did some digging and found that QTDragon doesn't use the macros for the probing that happens on the Offsets and Tool screens. It is done in the Python code in qtdragon_handler.py file. I'm going to attempt to make a change so that any values that are shown, entered on the screen or in the .ini file are treated at units in the specified by LINEAR_UNITS in the .ini file. Having some values in MM and others in Inches is confusing. If successful I'll have to learn how to contribute changes."In 2.8 the macros for probing are in nc_files/probe/basicprobe/macros"
The macros are used for the probing done on the Probe screen. This is a great learning exercise.
Please Log in or Create an account to join the conversation.
I have recently been working on versa probing code a bit.
I don't think I included the tool probe stuff as it requires remap code.
keep us posted!
Please Log in or Create an account to join the conversation.
- seebaer1976
- Offline
- Junior Member
- Posts: 33
- Thank you received: 1
I did some digging and found that QTDragon doesn't use the macros for the probing that happens on the Offsets and Tool screens. It is done in the Python code in qtdragon_handler.py file. I'm going to attempt to make a change so that any values that are shown, entered on the screen or in the .ini file are treated at units in the specified by LINEAR_UNITS in the .ini file. Having some values in MM and others in Inches is confusing. If successful I'll have to learn how to contribute changes."In 2.8 the macros for probing are in nc_files/probe/basicprobe/macros"
The macros are used for the probing done on the Probe screen. This is a great learning exercise.
Hi,
have the same problem that I don't get my manual tool change macro to work properly.
the marco calculates and the qtdragon_handler.py calculates again and this gives me a value that is twice as large.
Unfortunately I can't get any further because I can't program python.
qtdragon - new tool length after a manual tool change
best regards
Please Log in or Create an account to join the conversation.