qtdragon - new tool length after a manual tool change

hottabich wrote: Mdi Touchy allows you to use controlled macros. You can adjust the macro for your tasks.

I don't know Mdi Touchy, is there a wiki or something about it?

seebaer1976 wrote:

hottabich wrote: Mdi Touchy allows you to use controlled macros. You can adjust the macro for your tasks.

I don't know Mdi Touchy, is there a wiki or something about it?

Look at the link for QtVcp widgets. Or just try it out in QtDragon!

seebaer1976 wrote: 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:

Attachment not found

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

Hi seebaer1976

Im trying to implement this code for a toolsetter. I can get the Axes to move to toolchange position in the cycle. But after that what do I need to do to acknowledge that I have changed the tool and it can continue on to the Sensor to measure the tool. Thanks.

Hi,
normally a popup should open, which you confirm when you have changed the tool.

cmorley wrote: This is qtvcp's other probe screen.

Attachment not found

Hi,
How can I switch the probe screen from Basic Probe to Versa Probe?

would like to try Versa Probe, maybe I can do it with it.

best regards
seebaer1976

Try it.

Is this still a work in progress?

Using the latest version that is bundled with the BuildBot 2.9pre version (I update daily) there now is a pop-up screen but no movement to toolsensor or even toolheight measurement.

What am I doing wrong? I expected the behaviour to be like gmoccapy's toolmeasurement, the remapping of M6.

Unless you added remap code to your configuration, then it will not probe at tool change.

I had done some work on a (hopefully) standard remap code to cover most requirements, but have not finished it.

but what ever code that was used with gmocccapy should be able to be adapted to qtdragon.

I'm using qtdragon,
just implemented the files from Peter, talla83, video #29
and I can confirm that it works perfectly. Almost all setup was done with pncconf, then I added Peter's extensions.
During the first test the Z movement stopped with an error msg at the tool probe. This was fixed
by debouncing the tool probe.
When M6T1 is in the gcode, it moves to the tool change position, I change the tool and click the confirmation dialog. Then it moves over the tool sensor and slowly touches it. Then it moves z up to a secure position and continues.
 

Hello Harry. Would you like to share your settings? Here's another option, can anyone try it: wiki.printnc.info/en/controllers/linuxcnc/tool-setter-no-probe