qtdragon - new tool length after a manual tool change

Hi all,

how can the new tool length after a manual tool change be measured while the job is still in progress, using the touch tool on the workpiece?

While the job is running, the buttons for man, mdi, offsets and tool ... are locked.

When changing the tool and trying to move on, the job continues with the tool length of the first tool without measuring the new one first.

either you preset all your tools or need to add the capability to measure tools at tool change.
There has been various methods - I think gmoccapy could do this.
Have you used a different screen or is this your first taste of linuxcnc?

If there is a somewhat standard way to do it - we can incorporate the controls in qtvcp.

cmorley wrote:

either you preset all your tools or need to add the capability to measure tools at tool change.
There has been various methods - I think gmoccapy could do this.
Have you used a different screen or is this your first taste of linuxcnc?

If there is a somewhat standard way to do it - we can incorporate the controls in qtvcp.

Hi everyone

first of all thanks for the great work you do here, qtdragon looks awesome.

i am looking for exactly this possibility in qtdragon. since I have a spindle with er16 and therefore have no fixed tool lengths.

have been using axis with probe_screen_v2 for 1.5 years. and it worked properly there.


maunuel tool change process at axis with probe_screen_v2:

- Measure the workpiece with the touch probe
- load job
- start job
- spindle moves to the tool change position and requests the first tool
- tool clamped and confirmed
- spindle drives to the tool sensor and measures the first tool
- first milling begins
- first milling finished
- spindle moves to the tool change position and requests the second tool
- tool clamped and confirmed
- spindle moves to the tool sensor and measures the second tool
- second milling begins
- etc. until the job is finished


maunuel tool change process at qtdragon:

- measure the workpiece with the touch probe
- load job
- start job
- spindle moves to the tool change position and requests the first tool
- tool clamped and confirmed
- first milling starts without measuring the new tool, which means that z lies at the height of the touch probe and not on that of the new tool
- first milling finished
- spindle moves to the tool change position and requests the second tool
- tool clamped and confirmed
- second milling begins without measuring the new tool, which means that z lies at the height of the touch probe and not on that of the new tool
- etc. until the job is finished

unfortunately have experience of programming, but can it be that it has something to do with remap m6?
it would be very helpful if it could be integrated like probe_screen_v2.

best regards

qtvcp does have a robe screen that was based from versa_probe - I think I used version2. I have not really tested it with hardware.
It could be incorporated in QtDragon as a custom screen.

but if the probing was automatic then there must be more to it then just the probe program - yes my bet would be remapped tool changes.

Chris

This is qtvcp's other probe screen.

I got in touch with peter dam ... from talla83.de. last year he wrote a script for dynamic tool measurement.
asked him if you can install it in qtdragon.
he has agreed and approved to use it.

here is a video on youtube:

and here the script:


Maybe it will help you.
it can perhaps be so integrated that it can be activated or deactivated under settings for those who do not need it.

markus

So now that we know it's a remapped tool change that adds probing - It's not a qtdragon issue it's a configuration option.

If it's common enough I suppose I could add an example config - the problem being that the complicated sample configs often don't work if you move them because file path references (of macros for instance) are not very flexible to change

Chris

Hi,

Would it be a lot of work to incorporate your own macro, what does this measure after the tool change?
maybe you can integrate it so that you can activate or deactivate it when you don't need it.

Those macros included in qtvcp are primarily to probe work pieces for a mill.
Remapping tool changes is a different configuration process - not related to screen files.
So there is nothing to incorporate into qtvcp, you must remap toolchanges with INI changes and python remap files.

I don't think there are any samples in the official docs - probably would be a good project to include.