QtDragonHD tool sensor help for a maker space

More
2 years 9 months ago #291383 by cmorley
Did you get a chance to test the code?

Please Log in to join the conversation.

More
2 years 9 months ago #291384 by warwickben
I’ll check it this week. Had family member in the hospital etc and haven’t been able to get to my maker space.

Please Log in to join the conversation.

More
2 years 9 months ago #291385 by cmorley
No worries just checking back - hope all is ok at home.

Please Log in to join the conversation.

More
2 years 7 months ago #296346 by Flocki
Hi,

I hope this is the correct place for some testing feedback.
Reading the documentation I would have expected, that in "Auto"-mode after changing the tool manually behaves as follows:
1) Rapid move in X and Y to position defined in the INI’s [VERSA_TOOLSETTER] X and Y
2)Rapid move down in Z to position defined in the INI’s [VERSA_TOOLSETTER] Z
3)Probe down in Z to maximum defined in the INI’s [VERSA_TOOLSETTER] MAXPROBE

However Step 2 is happening at search-velocity rather then rapid.

Besides that working perfectly for me so far :)

Please Log in to join the conversation.

More
2 years 7 months ago #296362 by cmorley
I think you are speaking of the auto probe tool tool change.
Yes looks like the program qt_auto_probe_tool.ngc uses search velocity.
relevant code:
Code:
G53 G0 X[#<_ini[VERSA_TOOLSETTER]X>] Y[#<_ini[VERSA_TOOLSETTER]Y>] F #<_hal[qtversaprobe.searchvel]> G53 G1 Z[#<_ini[VERSA_TOOLSETTER]Z>]

you could change it to:
Code:
G53 G0 X[#<_ini[VERSA_TOOLSETTER]X>] Y[#<_ini[VERSA_TOOLSETTER]Y>] G53 G0 Z[#<_ini[VERSA_TOOLSETTER]Z>]

Chris

Please Log in to join the conversation.

More
2 years 7 months ago #296385 by Flocki
Thanks for your help, that indeed fixed it.

I am completely new to LinuxCNC, so sorry if I am not asking the correct questions, since I don't fully understand yet, how all the parts interact.

Maybe you are also able to assist with another thing:
My toolsetter has an 8 mm diameter, but my facemill has 10mm diameter and needs to be measured at the tips. I have seen some python-code here on the forum, that is applying an x-offset for this use-case, but that seems not to be part of the "stock"-installation-auto-probe-tool-change?
Any advice on how to activate that would be appreciated.

Please Log in to join the conversation.

More
2 years 7 months ago #296426 by cmorley
Yes I have done some work on probing a tool and setting the tooltable. In that case diameter offsetting was added.

You could probably add this to auto probe ngc program.
Parameter 5410 should give yoy the tool diameter, as set from the tool table.
Then you would offset half that diameter.

Please Log in to join the conversation.

More
2 years 7 months ago #296488 by Flocki
Thanks, that was the hint needed.

I have replaced:
Code:
G53 G0 X[#<_ini[VERSA_TOOLSETTER]X>] Y[#<_ini[VERSA_TOOLSETTER]Y>] F #<_hal[qtversaprobe.searchvel]> G53 G0 Z[#<_ini[VERSA_TOOLSETTER]Z>]

With this:
Code:
O250 if [#5410 GT [#<_ini[VERSA_TOOLSETTER]DIAMETER>-1]]     #<toolprobe_x_offset> = [#5410/2] O250 else     #<toolprobe_x_offset> = 0 O250 endif G53 G0 X[#<_ini[VERSA_TOOLSETTER]X>+#<toolprobe_x_offset>] Y[#<_ini[VERSA_TOOLSETTER]Y>] F #<_hal[qtversaprobe.searchvel]> G53 G0 Z[#<_ini[VERSA_TOOLSETTER]Z>]

Please Log in to join the conversation.

More
1 year 1 month ago #335310 by Clark222
I've been using Linuxcnc for the past 5-6 years (I use to be Clark22 but I got locked out).   More accurately, I've been making baby steps towards getting my cnc to work properly before taking an extended break (build the machine and get it moving, stop for a long break, get the spindle working properly, take a break, get endstops working then take a break ......).  The last big step was getting the spring probe and edge probe to play nicely with each other and then to get the auto tool change and updated tool.table working.  I've don't tend to ask for help but rather keep plugging at it until I get it figured out.  The past month has been going around and around, but today I finally got it working.  I've seen you ask for people to test out the probe_routine.py and the versa_probe.ui and I wanted to let you know that I got it working today and I really like how it's doing.  I have a lot more testing on it to make sure it's actually working but after a month the tool.tbl finally updates.  For anyone else wanting to try these out there's on part that was causing a lot of confusion for me.  the python_probe.py goes in the /usr/lib/python3/dist-packages/qtvcp/widgets/probe_routines.py directory and the versa_probe.ui goes in the /usr/share/qtvcp/widgets_ui directory.  For some reason I had the versa_probe.us in the first directory (who knows how it ended up in there). I thought clarifying that might help somebody.

Please Log in to join the conversation.

Time to create page: 0.378 seconds
Powered by Kunena Forum