#hazzy | Logs for 2020-06-15

Back
[00:23:14] -!- c-log has quit [Ping timeout: 240 seconds]
[00:27:10] -!- c-log has joined #hazzy
[00:31:42] -!- c-log has quit [Ping timeout: 258 seconds]
[00:35:08] -!- c-log has joined #hazzy
[02:31:38] -!- jmarsac has joined #hazzy
[02:33:14] -!- jmarsac_ has joined #hazzy
[02:34:43] -!- c-log has quit [Ping timeout: 246 seconds]
[02:37:17] -!- jmarsac has quit [Ping timeout: 272 seconds]
[02:37:26] -!- c-log has joined #hazzy
[02:48:34] -!- Becksvill has joined #hazzy
[02:59:34] <Becksvill> hey guys. I have just installed qtpyvcp on my linux cnc linux mint installation on my laptop. and I open up a config in probe basic successfully by renaming the display to probe_basic.
[03:00:31] <Becksvill> I am just trying to get a understanding of how everything works now. does anyone have a list of places that helped with the learning process? I am a little lost at the moment
[03:01:08] <Becksvill> forgot to say that I did the development install
[03:02:46] <Becksvill> I have 3 but 4-5 ton cnc machines that I want to get up and running soon with probe basic on the cnc mills and once it is ready the new probebasic lathe gui. so I want to learn this. and it really interests me.
[03:35:01] -!- c-log has quit [Ping timeout: 264 seconds]
[03:36:26] <Joco[m]1> So you want to learn probe basic specifically?
[03:37:17] <Becksvill> yep
[03:37:57] <Becksvill> I have all the rest of the linuxcnc stuff sussed I think.
[03:38:17] <Becksvill> and i am quite comfortable with hal cmd and classic ladder now
[03:38:41] <Joco[m]1> hmmm. Not sure there is any documentation as such on probe basic
[03:38:56] <Becksvill> yes i wondered
[03:39:54] <Becksvill> how did you learn? the rest of linux is similar lol. you just charge in and eventually learn it
[03:40:31] <Becksvill> through many late nights and lots of work and a bit of banging my head against the wall
[03:41:47] <Becksvill> just to confirm. I understand general linuxcnc stuff i think. it is the qtpyvcp stuff I need to learn
[03:42:17] <Joco[m]1> So on probe basic I think you just play with it in sim
[03:42:39] <Joco[m]1> Lcvette: is mr probe basic guru
[03:43:33] <Joco[m]1> If you want to learn the framework then it’s looking at the documentation site where you did the dev install. Looking at examples and ask questions.
[03:44:02] -!- c-log has joined #hazzy
[03:56:55] <Becksvill> sweet
[03:57:50] <Joco[m]1> the framework has a pretty good tutorial that will get you going
[03:58:35] <Becksvill> were would I find that. beginner here with qtpyvcp remember
[03:59:06] <Joco[m]1> http://www.qtpyvcp.com
[04:02:01] <Becksvill> checking it out now thanks
[04:05:32] <Joco[m]1> no worries. I'm pretty new myself but it doesn't take long to get into things if you are prepared to put the time in. If you get into some of the python coding I would suggets getting liclipse as an editor. Its free and supports debugging which is a must.
[04:05:50] <Joco[m]1> http://www.liclipse.com
[04:06:07] <Joco[m]1> way easier and much more responsive in my view than pycharm.
[04:06:31] <Joco[m]1> pycharm is very good but the community edition is a bit nerfed
[04:10:33] -!- Becksvill has quit [Remote host closed the connection]
[04:17:59] -!- Becksvill has joined #hazzy
[04:18:57] <Becksvill> well I got the first part working
[04:19:44] <Becksvill> can't find the examples on the config picker now
[04:43:49] -!- Becksvill has quit [Ping timeout: 245 seconds]
[05:19:39] -!- Becksvill has joined #hazzy
[05:24:11] <Joco[m]1> sorry been in the garage
[05:25:50] <Becksvill> all good
[05:26:25] <Joco[m]1> you might need to copy the qtpyvcp examples to the linuxcnc folder
[05:26:43] <Becksvill> of course!
[05:26:46] <Becksvill> I will try that now
[05:27:08] <Joco[m]1> do you have this directory per instructions:
[05:27:08] <Joco[m]1> This will install QtPyVCP along with the examples, and will add QtPyVCP specific sim configs to ~/linuxcnc/configs/sim.qtpyvcp.
[05:29:28] <Joco[m]1> got my manual touchoff UI working more fully now
[05:29:56] <Becksvill> nice
[05:30:03] * Joco[m]1 uploaded an image: image.png (42KB) < https://matrix.org >
[05:30:24] <Becksvill> hey thats sweet
[05:30:31] <Joco[m]1> basic edge finder style touch off
[05:30:41] <Becksvill> nice
[05:30:58] <Becksvill> I will buy a probe soon but for now only have a edge finder
[05:30:58] <Joco[m]1> sometimes doing it by hand is just easier than getting all auto proby
[05:31:09] <Becksvill> yes probably lol
[05:31:12] <Joco[m]1> this is for an edge finder
[05:31:28] <Becksvill> how did you upload a photo here?
[05:31:51] <Joco[m]1> copy and past into the web client
[05:32:02] <Joco[m]1> or use the attach file
[05:32:13] <Joco[m]1> "Upload File" it's called
[05:32:34] <Joco[m]1> assuming you are using thr Riot.im web client
[05:32:40] <Becksvill> still looking for that
[05:32:53] <Becksvill> i am using the kiwi irc web irc client
[05:32:54] <Joco[m]1> https://riot.im
[05:33:17] <Joco[m]1> I just do it through thw browser
[05:33:40] <Joco[m]1> https://about.riot.im
[05:33:49] <Joco[m]1> has all the clients
[05:36:37] <Joco[m]1> Becksvill: sorry got distracted. Do you have this directoy?
[05:36:37] <Joco[m]1> ```
[05:36:37] <Joco[m]1> ~/linuxcnc/configs/sim.qtpyvcp
[05:37:36] <Becksvill> no
[05:37:57] <Joco[m]1> there's a problem then
[05:39:03] <Joco[m]1> in the folder where you have the qtpyvcp dev files there is a folder call 'linuxcnc'
[05:39:05] <Becksvill> I have the sim here I think I copied and pasted it into the chat /home/andrew/qtpyvcp/linuxcnc/configs/sim.qtpyvcp
[05:39:12] <Joco[m]1> that needs to be copied to ~/
[05:39:40] <Joco[m]1> so you want to do this ....
[05:40:14] <Joco[m]1> cp -r ~/qtpyvcp/linuxcnc ~/
[05:40:43] <Becksvill> think I have done it just testing now
[05:41:03] <Becksvill> yep got it! yeha
[05:41:18] <Joco[m]1> win
[05:41:30] <Becksvill> I had almost copied to the right place.
[05:41:57] <Becksvill> I copied it to the linuxcnc folder. I needed to go one deeper to the config folder
[05:42:03] <Becksvill> once I did that everything works
[05:42:04] <Becksvill> thanks
[05:42:59] <Becksvill> now to carry on with the tutorials
[05:43:13] <Becksvill> I am liking this so far
[05:43:24] <Becksvill> but can see if is going to take some serious time lol.
[05:43:26] <Joco[m]1> there are some good examples out there which are not as complicated as probe_basic
[05:43:56] <Joco[m]1> but there is no doubt probe_basic is the flagship gui for the framework
[05:44:38] <Becksvill> sweet
[05:45:55] <Becksvill> actually one problem I have is editing classic ladder with probe basic. as probe basic automatically goes full screen It hides the classic ladder plc
[05:46:18] <Becksvill> I use the classic ladder plc lots for my e stop circuit and also the random position toolchanger
[05:46:27] <Becksvill> it makes more sense to me that using gcodes
[05:47:35] <Joco[m]1> really? I'm the other way around. Way more comfortable in stuff that looks like code
[05:48:05] <Becksvill> yes ladder logic is easier for me. I had someone on the forum help me out at first.
[05:48:11] <Joco[m]1> probe_basic is designed for 1080p screens. It is intended to full the whole thing.
[05:48:46] <Becksvill> the plc is much better for safety stuff in my opinion
[05:48:51] <Joco[m]1> you can change things to not always be on top. From memory
[05:49:12] <Becksvill> yes that is what I want to do. I want to force the plc to stay on top of probe basic
[05:49:15] <Becksvill> just for testing
[05:49:31] <Becksvill> and also hal meter and the rest of them the tools.
[05:49:34] <Joco[m]1> you can do that in linux
[05:49:42] <Becksvill> they all hide and i can't get them back
[05:49:44] <Joco[m]1> yup - all possible
[05:50:01] <Becksvill> I have heard of using some command line tools to do this
[05:50:09] <Joco[m]1> there is even an add on tool that will auto do it as the windows appeart
[05:50:17] <Joco[m]1> I do it on my debian box for certain things
[05:50:25] <Becksvill> that would be nice
[05:50:30] <Becksvill> do you know what it is called
[05:50:48] <Joco[m]1> hand on ....
[05:54:14] <Becksvill> Wmctl is one name I think
[05:54:36] <Becksvill> and another is xdtool
[05:54:58] <Joco[m]1> yeah - trying to find what I used
[05:55:14] <Becksvill> not that I have any idea how they work. but everything is like that lol. I am a machinist learning programming and electronics lol
[05:55:22] <Becksvill> yes no hurry
[06:00:27] <Joco[m]1> used this: http://www.nongnu.org
[06:00:43] <Joco[m]1> got the gui for it
[06:01:32] <Joco[m]1> or I might have used the original verson as it did have a gui and it just seemed to work
[06:03:50] <Joco[m]1> https://help.ubuntu.com
[06:11:28] <hazzy-m1> Becksvill: hot F11 to exit full screen mode
[06:11:29] <hazzy-m1> Hit
[06:11:53] <Becksvill> yes!
[06:12:45] <Becksvill> that is funny haha. the solution was so easy:)
[06:13:02] <Becksvill> f11 works perfectly thanks hazzy
[06:13:38] <Joco[m]1> there might also be an F button for always on top as well
[06:13:52] <Joco[m]1> ?
[06:14:57] <Becksvill> yes that would be good to know
[06:14:59] <hazzy-m1> no, but we can add one, might be useful
[06:15:50] <JT-Cave> morning
[06:15:54] <Becksvill> well for now I am happy as. its funny lol. I went back to axis as I had to get something done and needed classic ladder. and couldn't work out how to get it working
[06:16:18] <Becksvill> morning john
[06:18:01] <Joco[m]1> https://www.maketecheasier.com
[06:19:19] <Joco[m]1> hazzy: for the tools from the menu - like halshow having them started with always-on-top might be a good idea.
[06:21:03] <Joco[m]1> hazzy: been thinking about the mdi history. I might have some enhancements to make to it
[06:25:35] <Joco[m]1> I'm thinking about slots to raise/lower a selected entry in the history. Also the ability to copy the selected rows into the gcode editor. I was wanting these functions over the weekend.
[06:25:59] -!- Jedi93 has joined #hazzy
[06:27:01] -!- Jedi93 has quit [Remote host closed the connection]
[06:27:41] <Joco[m]1> maybe also a setting in designer that allows a vcp developer to increase the heart beat rate to make things a little more responsive.
[06:44:21] <hazzy-m1> yes, that's a good idea
[06:45:42] <Joco[m]1> will have a tinker then
[07:21:39] -!- jmarsac_ has quit [Ping timeout: 272 seconds]
[07:34:15] -!- Becksvill has quit [Ping timeout: 245 seconds]
[07:44:18] -!- becksvill has joined #hazzy
[08:34:59] -!- jmarsac_ has joined #hazzy
[08:43:24] -!- becksvill has quit [Ping timeout: 245 seconds]
[09:45:58] -!- fjodor[m] has joined #hazzy
[09:47:37] <Not-944e> [02qtpyvcp] 07KurtJacobson pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/Jf7a4
[09:47:39] <Not-944e> [02qtpyvcp] 07KurtJacobson 0369b43ae - BUG: Settings - Pass on errors encountered when initing setting value
[09:47:55] <Lcvette> morning
[09:48:00] <Lcvette> hazzy on your flight yety
[09:49:28] <Not-944e> [02qtpyvcp] 07KurtJacobson pushed 031 commit to 03gh-pages [+489/-0/±0] 13https://git.io/Jf7ar
[09:49:30] <Not-944e> [02qtpyvcp] 07traviscibot 03c0d8386 - Deploy kcjengr/qtpyvcp to github.com/kcjengr/qtpyvcp.git:gh-pages
[09:55:49] -!- c-log has quit [Ping timeout: 265 seconds]
[09:59:55] -!- c-log has joined #hazzy
[10:01:44] <hazzy-m1> Lcvette: yes, working on the plane!
[10:01:56] <Lcvette> /o\
[10:02:38] <Lcvette> don't get yelled at by the stewardess
[10:02:42] <Lcvette> :D
[10:02:47] <Lcvette> unless she is hot
[10:02:52] <Lcvette> :D
[10:02:52] <Lcvette> \o/
[10:06:00] <hazzy-m1> hahahaha
[10:06:29] <hazzy-m1> I'm not wearing a mask either :o
[10:13:41] <Lcvette> /o\
[10:16:18] <hazzy-m1> I love Delta, it's kinda like Chick-fil-A, they always find someway to exceed my expectations
[10:16:41] <Lcvette> nice
[10:17:37] * Lcvette sent a long message: < https://matrix.org >
[10:17:55] <Lcvette> hazzy i started getting this when opening designer
[10:19:29] <hazzy-m1> Check the most recent push
[10:19:40] <hazzy-m1> Should be fixed
[10:20:15] <Lcvette> \o/
[10:20:22] <Lcvette> hurray
[10:20:26] <Lcvette> gone!
[10:21:36] <hazzy-m1> Sweet!
[10:22:03] <Lcvette> updating probe basic mill stacked widget dro's
[10:22:04] <Lcvette> :D
[10:22:06] <Lcvette> \o/
[10:26:48] <Lcvette> the drowidget dro editor is gone now
[10:27:04] <Lcvette> still shows for drolabel
[10:27:09] <Lcvette> hazzy^
[10:43:06] <Lcvette> ok all dro's have been updated in probe basic
[10:44:09] <Lcvette> the drowidget is editable in properties sidebar but the window the tohers use is nto available, not sure if that is right or not ?
[10:44:32] <Lcvette> * the drowidget is editable in properties sidebar but the window the others use is not available, not sure if that is right or not ?
[10:44:50] <Lcvette> color change rule does not apply from stylesheet
[10:45:14] <Lcvette> for unhomed, homing, homed
[10:58:30] <Lcvette> hazzy: i think i did a merge in probe basic
[10:58:46] <Not-944e> [02probe_basic] 07Lcvette pushed 032 commits to 03master [+0/-0/±6] 13https://git.io/Jf7K8
[10:58:48] <Not-944e> [02probe_basic] 07Lcvette 03cb258b2 - update probe basic DRO's to new DROWidget and labels
[10:58:49] <Not-944e> [02probe_basic] 07Lcvette 03fb171e4 - Merge remote-tracking branch 'origin/master'
[11:00:11] <Not-944e> [02probe_basic] 07KurtJacobson pushed 031 commit to 03gh-pages [+88/-0/±0] 13https://git.io/Jf7Ko
[11:00:12] <Not-944e> [02probe_basic] 07traviscibot 036549b53 - Deploy kcjengr/probe_basic to github.com/kcjengr/probe_basic.git:gh-pages
[11:19:38] -!- paul[m]1 has joined #hazzy
[11:19:57] <hazzy-m1> Lcvette: Heading to a customer, I'll try to check tonight
[11:19:59] <hazzy-m1> Sorry
[11:20:27] <hazzy-m1> I'll add the style class stuff to the DROs
[11:33:37] -!- emilvv has joined #hazzy
[11:34:33] -!- emilvv has quit [Remote host closed the connection]
[11:40:51] <hazzy-m1> Then you won't have to use rules
[11:50:56] <Lcvette> no worries, i was just reporting back from testing
[11:51:04] <Lcvette> was super easy to get swapped over and setup
[12:35:25] <Lcvette> turboss are you here?
[13:25:54] -!- jmarsac__ has joined #hazzy
[13:29:37] -!- jmarsac_ has quit [Ping timeout: 272 seconds]
[13:36:33] <TurBoss> Lcvette: yo
[13:51:09] -!- jmarsac__ has quit [Ping timeout: 272 seconds]
[13:56:50] <Lcvette> TurBoss: \o/
[13:56:57] <TurBoss> hello!
[13:56:58] <Lcvette> hola turboss!
[13:57:01] <Lcvette> :d
[13:57:04] <Lcvette> * :D
[13:57:12] <Lcvette> hazzy pushed the new dro's
[13:57:15] <TurBoss> que hay?
[13:57:20] <TurBoss> oh
[13:57:25] <TurBoss> cool!
[13:57:26] <Lcvette> i installed in probe basic mill and lathe
[13:57:48] <TurBoss> so vtk is missing?
[13:57:51] <Lcvette> is it time to merge the vtklathe to master?
[13:57:53] <Lcvette> yes
[13:58:03] <Lcvette> i think if we merge can test together
[13:58:18] <TurBoss> if 90 90 tools only go in Q1 o Q2 yes
[13:58:21] <TurBoss> ok
[13:58:24] <TurBoss> sure will merge
[13:59:07] <Lcvette> they can also go in Q3 and Q4
[13:59:15] <Lcvette> turboss
[13:59:28] <TurBoss> ok
[13:59:29] <Lcvette> 90 90 can be in Q1,2,3,4
[13:59:34] <TurBoss> gona fix tha
[13:59:35] <TurBoss> t
[13:59:53] <Lcvette> ok
[14:00:04] <Lcvette> should be same just inverted
[14:06:38] <TurBoss> Lcvette: my dev is offline
[14:06:47] <Lcvette> /o\
[14:06:49] <TurBoss> I need you to verify the commit
[14:06:55] <Lcvette> can i do?
[14:07:00] <Lcvette> ok how to do?
[14:07:07] <Not-944e> [02qtpyvcp] 07TurBoss pushed 031 commit to 03VTK_Lather [+0/-0/±1] 13https://git.io/Jf7Sp
[14:07:08] <Not-944e> [02qtpyvcp] 07TurBoss 03bbb7d1f - add Q3 and Q4
[14:07:34] <TurBoss> just Q3 and Q4
[14:07:40] * Lcvette uploaded an image: Screenshot_2020-06-15_14-07-26.png (90KB) < https://matrix.org >
[14:07:40] <TurBoss> if the are oriented fine
[14:07:41] <TurBoss> I drew the box
[14:07:47] <Lcvette> ok testing
[14:08:06] <TurBoss> need m,erge?
[14:08:10] <TurBoss> I can push to my fork
[14:11:42] <Lcvette> hurray, looks corretg!
[14:11:54] <Lcvette> * hurray, looks correct!
[14:12:08] <TurBoss> great!
[14:12:17] <TurBoss> I'll merge push
[14:12:18] <Lcvette> you better catch up your fork
[14:12:24] <Lcvette> catch up your master
[14:12:29] <TurBoss> ok
[14:12:39] <Not-944e> [02qtpyvcp] 07TurBoss created branch 03VTK_Lather 13https://git.io/Jf79Y
[14:12:41] <Lcvette> in qtpyvcp
[14:12:53] <Lcvette> in probe basic too
[14:13:01] <TurBoss> done
[14:13:02] <TurBoss> I merged to mine
[14:13:12] <TurBoss> push to kcjeng?
[14:14:00] <Lcvette> sek im testing
[14:15:15] <Not-944e> [02probe_basic] 07Lcvette pushed 031 commit to 03master [+0/-0/±3] 13https://git.io/Jf79C
[14:15:17] <Not-944e> [02probe_basic] 07Lcvette 034c6936d - fixed xz_view signal slot back
[14:16:40] <Not-944e> [02probe_basic] 07KurtJacobson pushed 031 commit to 03gh-pages [+88/-0/±0] 13https://git.io/Jf794
[14:16:41] <Not-944e> [02probe_basic] 07traviscibot 03b53c5cb - Deploy kcjengr/probe_basic to github.com/kcjengr/probe_basic.git:gh-pages
[14:17:14] * Lcvette sent a long message: < https://matrix.org >
[14:17:24] <Lcvette> getting an error now when trying to do a tool change
[14:20:45] <TurBoss> I'll setup dev in desk in some way
[14:21:04] <Lcvette> im tyring to find the culprit
[14:21:15] <Lcvette> think it may be there was now tool change position setup0
[14:21:24] <Lcvette> i may need to add a default value to the subroutine
[14:24:21] <Lcvette> ok all is working
[14:24:29] <Lcvette> it was missing the tool change position
[14:24:35] <Lcvette> \o/
[14:24:39] <Lcvette> think it is good to merge!
[14:24:40] <Lcvette> :D
[14:24:41] <Lcvette> hurray!
[14:25:16] <TurBoss> great
[14:25:21] <TurBoss> managed to boot
[14:25:22] <TurBoss> :D
[14:25:29] <Lcvette> hurray!!
[14:25:30] <Lcvette> \o/
[14:25:39] <Not-944e> [02qtpyvcp] 07TurBoss pushed 0338 commits to 03master [+0/-0/±42] 13https://git.io/Jf79Q
[14:25:41] <Not-944e> [02qtpyvcp] 07TurBoss 031e1232a - Merge branch 'VTK_Lather'
[14:27:07] <Not-944e> [02qtpyvcp] 07KurtJacobson pushed 031 commit to 03gh-pages [+489/-0/±0] 13https://git.io/Jf795
[14:27:09] <Not-944e> [02qtpyvcp] 07traviscibot 03c219131 - Deploy kcjengr/qtpyvcp to github.com/kcjengr/qtpyvcp.git:gh-pages
[14:30:19] <Lcvette> TurBoss: you need to catch up your probe basic
[14:30:45] <TurBoss> done
[14:30:58] <Lcvette> \o/ hurray
[14:31:04] <Lcvette> lcvette is testing the newest merge now
[14:33:38] <Lcvette> it is glorious!
[14:34:33] <TurBoss> great!
[14:34:41] <TurBoss> take a pic :P
[14:35:09] <Lcvette> what is the difference between click and toggle?
[14:37:28] <TurBoss> toggle holds the button down
[14:37:33] <TurBoss> button toggle
[14:40:20] <Lcvette> do you know of a way to have a vcplineedit run an mdi command when return is pressed?
[14:40:33] <Lcvette> without connecting to a button?
[14:41:18] <Lcvette> i just happened to test something and saw it didn't work
[14:42:31] <TurBoss> not sure
[14:44:11] * Lcvette posted a file: change_tool_offset.mkv (2493KB) < https://matrix.org >
[14:44:46] <Lcvette> i made video of the vtk awesomeness!!
[14:44:46] <Lcvette> :D
[14:44:46] <Lcvette> \o/
[14:46:38] <Lcvette> TurBoss: ^^^ video 4 u!
[14:46:38] <Lcvette> :D
[14:48:48] <TurBoss> lets seee
[14:51:24] <TurBoss> perfect
[14:52:54] <Lcvette> \o/
[14:55:41] <Lcvette> TurBoss: for the tool offsets, i don't understand how it works in gmoccapy
[14:55:51] <Lcvette> i tried using the x touch button and z touch button but it is confusing
[14:55:58] <Lcvette> no graphical representation
[15:03:59] -!- logs has quit [Ping timeout: 272 seconds]
[15:05:10] -!- logs has joined #hazzy
[15:05:10] -!- mode/#hazzy [+o logs] by ChanServ
[15:07:19] <Lcvette> is the motion for the tool touch stuff available to use?
[15:07:21] <Lcvette> i can start working on it
[15:08:19] <TurBoss> ah the qml thing?
[15:08:40] <Lcvette> yes!
[15:08:42] <Lcvette> \o/
[15:11:40] <TurBoss> in designer should show a white box but i think it works
[15:12:10] <Lcvette> i don't follow
[15:12:29] <TurBoss> its abailable on designer
[15:13:29] * Lcvette uploaded an image: Screenshot_2020-06-15_15-13-08.png (185KB) < https://matrix.org >
[15:15:31] <Lcvette> whats it called in designer?
[15:15:36] <Lcvette> dynatc same as mill?
[15:21:28] <TurBoss> no
[15:21:41] <TurBoss> its... under probebasic widgets
[15:23:08] <Lcvette> TurBoss: /o\ i dunno what you are saying
[15:23:44] <Lcvette> how do i use the probe basic widgets ?
[15:24:10] <Lcvette> we need it to be in designer?
[15:24:17] <Lcvette> or how to activate it?
[15:28:54] * Lcvette uploaded an image: Screenshot_2020-06-15_15-28-41.png (46KB) < https://matrix.org >
[15:29:12] <Lcvette> TurBoss: i see it here but how to I make it work in the ui?
[15:29:18] <Lcvette> turn it on or set it up?
[16:05:05] <Lcvette> man I really need soem lathe help
[16:10:37] <Joco[m]1> do we have a new dependency now for VTK?
[16:10:37] <Joco[m]1> ```
[16:10:37] <Joco[m]1> ImportError: No module named more_itertools
[16:11:44] * Joco[m]1 sent a long message: < https://matrix.org >
[16:12:27] <Lcvette> Joco: whats that?
[16:12:36] <Lcvette> what are you opening?
[16:12:56] <Lcvette> we just merged vtk for lathe stuff
[16:13:03] <Lcvette> but i did not get that error
[16:13:19] <Lcvette> with probe basic
[16:13:21] <Lcvette> mill or lathe
[16:13:32] <Joco[m]1> Just opening my GUI. Have just checked out latest version of framework.
[16:14:09] <Lcvette> may be something to do with your tool table?
[16:14:20] <Lcvette> turboss any clues ^^^
[16:14:22] <Lcvette> ?
[16:17:45] <Joco[m]1> All I did was change my framework checkout. No install update.
[16:33:55] <TurBoss> yes i forgot a new depepndency Joco
[16:34:20] <TurBoss> pipinstall it
[16:36:43] <Joco[m]1> Ok. After work.
[16:51:20] <Lcvette> TurBoss: did you see my questions?
[16:51:31] <Lcvette> how to get the lathe touch thing working?
[16:54:22] <TurBoss> is a widget in the qdesigner should be under probebasic widgets in desgner
[16:55:59] <Lcvette> i9 don't see probebasicwidgets in designer
[16:57:39] * Lcvette posted a file: Screenshot_2020-06-15_16-56-46.png (30KB) < https://matrix.org >
[16:57:42] * Lcvette uploaded an image: Screenshot_2020-06-15_16-56-27.png (47KB) < https://matrix.org >
[16:58:54] * Lcvette uploaded an image: Screenshot_2020-06-15_16-56-46.png (30KB) < https://matrix.org >
[17:10:04] <Joco[m]1> Maybe you need to do another pop install of latest framework checkout?
[17:10:22] <Joco[m]1> * Maybe you need to do another pip install of latest framework checkout?
[17:17:55] <TurBoss> backl
[17:23:16] * TurBoss uploaded an image: Captura de pantalla de 2020-06-15 23-23-01.png (68KB) < https://matrix.org >
[17:23:22] <TurBoss> is there
[17:23:23] <TurBoss> did nothing
[17:31:40] <Lcvette> i do not see that in my qtdesigner
[17:32:17] <Lcvette> how did you get it?
[17:32:19] <Lcvette> ^^^
[17:33:41] <Lcvette> TurBoss: lcvette doesn't have that option in designer
[17:33:48] <Lcvette> /o\
[17:34:19] <Lcvette> how come you have it and i do not?
[17:34:27] <Lcvette> is it on a another branmch?
[17:35:59] * Lcvette uploaded an image: Screenshot_2020-06-15_17-35-33.png (35KB) < https://matrix.org >
[17:36:13] <Lcvette> i see dynatc but not Probe Basic Widgets
[17:38:04] <TurBoss> 5 min
[17:39:00] <Lcvette> ok
[17:45:36] <TurBoss> back again :D
[17:45:44] <Lcvette> \o/
[17:45:54] <Lcvette> hurray turboiss is here!
[17:45:56] <Lcvette> * hurray turboss is here!
[17:46:06] <TurBoss> Lcvette: navigate to de probebasic directory and issue pip install -e .
[17:46:11] <TurBoss> \o/
[17:47:14] * Lcvette sent a long message: < https://matrix.org >
[17:48:02] <TurBoss> dot
[17:48:02] <TurBoss> add the .
[17:48:07] <TurBoss> -e space dot
[17:51:28] <Lcvette> ok done
[17:51:38] <Lcvette> now how to launch?
[17:52:09] <TurBoss> designer
[17:52:21] <TurBoss> editvcp probe_basic_lathe
[17:52:33] <Lcvette> hurray!!!
[17:52:37] <TurBoss> it shows?
[17:52:40] <Lcvette> now my designer lathe launcher works too!!
[17:52:41] <Lcvette> :D
[17:52:44] <Lcvette> you did it!!
[17:52:50] <Lcvette> \o/
[17:53:00] <Lcvette> o/ \o
[17:53:01] <TurBoss> but do the widget show?
[17:53:12] <TurBoss> \o/
[17:53:28] <Lcvette> yes!
[17:53:30] <Lcvette> do i delete the existing images?
[17:53:36] <Lcvette> in the designer
[17:53:37] <TurBoss> ok now we can work on it
[17:53:50] -!- jmarsac has joined #hazzy
[17:53:51] <TurBoss> yes no?
[17:53:58] <Lcvette> yes!!
[17:54:04] <Lcvette> \im in it now
[17:54:13] <Lcvette> trying to figure how to insert the new lathe tool touch widget
[17:54:22] <TurBoss> is just a draft how will it be managed?=
[17:54:27] <Lcvette> do i remove what is currently there?
[17:54:45] <TurBoss> is like the atc
[17:54:51] <TurBoss> yes
[17:54:52] <TurBoss> it will show a whte box
[17:55:10] -!- CaptHindsight has joined #hazzy
[17:55:56] <Lcvette> designer crasdhes when i try and drag and drop
[17:56:03] <TurBoss> ops
[17:56:46] <Lcvette> /o\
[17:56:55] <Lcvette> tried 3 times and keeps closing down
[17:57:58] <TurBoss> Lcvette:
[17:58:20] <TurBoss> cd qtpyvcp and pip install --upgrade -e .
[17:58:27] <TurBoss> same for probe_basic again
[18:00:14] -!- jmarsac has quit [Ping timeout: 240 seconds]
[18:00:31] <Lcvette> 5 minutes
[18:00:40] <TurBoss> sure
[18:05:56] -!- jmarsac has joined #hazzy
[18:10:45] <Lcvette> back
[18:11:13] <TurBoss> ok
[18:12:00] <TurBoss> it crashes?
[18:12:05] -!- jmarsac has quit [Ping timeout: 272 seconds]
[18:12:24] * Lcvette sent a long message: < https://matrix.org >
[18:12:28] <Lcvette> just ran this
[18:12:37] <Lcvette> did it correctly?
[18:12:37] <TurBoss> ok
[18:12:59] <TurBoss> yes
[18:13:00] <Lcvette> hurray
[18:13:02] <Lcvette> no crash!
[18:13:12] <TurBoss> still crash?
[18:13:19] <TurBoss> great
[18:13:38] <Lcvette> how do i size it?
[18:14:29] <TurBoss> is static
[18:14:47] <TurBoss> 600x1024
[18:15:00] <Lcvette> ok it is working in probe basic
[18:15:05] <TurBoss> easy to change in the qml file
[18:15:08] <Lcvette> but the sizing has some issues
[18:15:40] -!- jmarsac has joined #hazzy
[18:17:50] <Lcvette> but it is a good step now to see things moving!
[18:17:50] <Lcvette> :D
[18:17:59] <Lcvette> so how to adjust now?
[18:18:10] <Lcvette> and the white lines are missing i think
[18:19:27] <TurBoss> white lines?=
[18:20:28] <Lcvette> There was some dimension lines
[18:20:29] <Lcvette> With arrows
[18:20:54] <Lcvette> To help show the measurement you were obtaining
[18:20:55] <TurBoss> ah
[18:21:14] <TurBoss> not implemented yet
[18:21:37] <Lcvette> Ah
[18:30:30] <Lcvette> https://www.youtube.com
[18:30:38] <Lcvette> this guy explains everything pretty well
[18:35:29] <Lcvette> https://www.youtube.com
[18:35:37] <Lcvette> this is another good one
[18:36:47] -!- jmarsac has quit [Read error: Connection reset by peer]
[18:36:57] <TurBoss> ok
[18:37:30] <Lcvette> im watching trying to figure out what we need
[18:37:35] <Lcvette> but its elusive
[18:38:40] <TurBoss> :)
[18:39:35] -!- Becksvill has joined #hazzy
[18:42:51] <Lcvette> lcvette gets so confused on lathe tool offsets
[18:43:45] <Becksvill> what are you getting confused on lcvette?
[18:44:22] <Lcvette> how to set everything up in the ui
[18:45:02] <Lcvette> setting up one tool is not hard
[18:45:22] <Lcvette> doing it manually taking a cut in z and x and setting z to 0 and x to the newly turned diameter
[18:45:32] <Lcvette> but its the subsequent tooling that stumps me
[18:45:48] <Lcvette> is one of the tools a master tool? if so how is that specified?
[18:46:07] <Becksvill> ah I might be able to help there.
[18:46:22] <Becksvill> normally on cnc lathes there are a couple of ways to do it.
[18:46:29] <Lcvette> i just want to be able to offer a very simple method for setting up the lathe tool offsets for repeatable holders
[18:46:44] <Becksvill> yes
[18:46:51] <Lcvette> thats what i have been seeing
[18:47:32] <Becksvill> I think linuxcnc axis is not too bad with their zero tool offset
[18:49:19] <Lcvette> i just looked at it and it was not intuitive to me
[18:49:33] <Becksvill> anyway. on the fagor and semiens control that I have used usually we just specify one tool that is the master tool. this may be a OD finishing tool or something.
[18:49:33] <Lcvette> I want probe basic lathe to be pretty much look at it and understand it
[18:49:53] <Lcvette> ok
[18:50:13] <Lcvette> how do you specify it as a master tool?
[18:50:37] <Lcvette> btw this is very similar to what I am used to in Machstdmill
[18:50:43] <Lcvette> mstertool mode
[18:51:09] <Becksvill> remember on a lathe it is only the z offset that changes really. the x axis is fixed to the centre of the spindle. and that never changes.
[18:51:36] <Lcvette> yes, if the machine has home switches
[18:51:50] <Lcvette> but i have to figure not all machines running this will have home switches
[18:52:18] <Lcvette> so x will be floating at startup until defined
[18:52:28] <Lcvette> need to be able to use in that fashion as well
[18:52:33] <Becksvill> so to set up the x axis offset correctly you just take a cut and then measure it. and then put the measured value into the tool size
[18:53:35] <Becksvill> just trying to keep up with questions here... usually we just call the master tool tool 1. or tool 20 or something.
[18:54:03] <Becksvill> calling it tool 20 only works if the lathe has a quick change toolpost rather than a turret
[18:54:22] <Becksvill> so calling it tool 1 is probably the best thing to do
[18:55:27] <Becksvill> I think all machines should have home switches! they cost like 5usd and are so much better but I see what you mean not everyone will have them. in that case. Tool 1 should be the master tool. so that has no tool offset applied
[18:56:01] <Becksvill> all the other tools are referenced off that tool. via the tool offset tables
[18:56:05] <Becksvill> just like on a cnc mill
[18:56:35] <Lcvette> yup
[18:56:43] <Lcvette> but how do i implement that in the ui
[18:57:12] <Lcvette> thats what im wrestling with, the subsequent tools muyst be measured against the master tool
[18:57:39] <Lcvette> so to simplify it, I feel as the the mastertool should have an actual place to call it the master tool
[18:57:39] <Lcvette> a box
[18:57:40] <Becksvill> a easy way to set things up initially if x is floating would be to take a light cut on the dia with tool 1 and then measure what size it is. then update the x value in the dro with that value.
[18:57:51] <Becksvill> ok I see what you mean
[18:58:31] <Lcvette> and maybe a box that you enter in the actual measured skim pass diameter so you have a number to use in calculating the other tool's offets in x and z
[18:59:20] <Becksvill> yes maybe
[18:59:28] <Lcvette> trying to make it so you only have to enter in the master tools skim pass diameter then bring the other tools down fora touch off and the calcs are auto
[18:59:59] * TurBoss uploaded an image: Captura de pantalla de 2020-06-16 00-59-38.png (115KB) < https://matrix.org >
[19:00:12] <Becksvill> I will take a detailed video next time I get a chance to show how the industrial guys do it
[19:00:33] <Lcvette> I am gonna throw somethign together real quick in the ui and I will post it up to get your feedback on, i have something forming after sounding it out with you
[19:00:46] <Becksvill> sweet
[19:01:02] <Lcvette> TurBoss: hurray!!!!!
[19:01:05] <Becksvill> I wish I could actually help with the coding lol! but still learning things
[19:01:31] <TurBoss> qml is like javascript very easy
[19:01:32] <Lcvette> I did all the graphics like 2 years ago.. we are just now getting around to implement it all
[19:01:48] <Lcvette> turboss does all the sweet sweet motion
[19:01:48] <TurBoss> just start by doin little hacks here and there
[19:02:18] <TurBoss> where do I put the tools for referencing
[19:02:19] <TurBoss> on the line?
[19:02:36] <Becksvill> turboss. my 12 year old brother is actually really good at java script lol
[19:02:43] <Joco[m]1> Guys - with this tool measuring are you not mixing setup of the lathe for working on a part versus actual setup of the tools that are repeatable?
[19:02:43] <Becksvill> might have to learn from him
[19:03:17] <Lcvette> Joco: setting it up for single tool use is very simple
[19:03:23] <Lcvette> just type into the dro's
[19:03:30] <Lcvette> and you are ready to cut
[19:04:02] <Lcvette> this si for setting up alibrary of repeatable holders or tools that are repeatable in a turret
[19:04:08] <TurBoss> https://github.com
[19:04:09] <TurBoss> :P
[19:04:14] <Joco[m]1> Maybe I’m missing what you are getting at. The light cut model on a master tool that everything else references from should be very simple.
[19:04:26] <Lcvette> * this is for setting up a library of repeatable holders or tools that are repeatable in a turret
[19:04:44] <Joco[m]1> That of course assumes that all the other tools have already been setup referenced from that master tool
[19:04:45] <Joco[m]1> Yes?
[19:04:47] <Lcvette> yes in its mechanical form it is very simple
[19:05:01] <Lcvette> but in the ui it becomes much more complex
[19:05:15] <Lcvette> this si how to setup and reference all of the other tools
[19:05:30] <Lcvette> without having to do it manually with a calulator
[19:05:59] <Lcvette> i feel it should be very simple and easy and the calcs done for you with the simple push of a button
[19:06:11] <Joco[m]1> Of so. Isn’t that just a matter of using a DI type tool with the master set at zero and then measure the deltas for all other tools from that point?
[19:06:19] <Lcvette> ie store the master tool measurements in a line edit
[19:06:44] <Lcvette> riught but work the process out in your head
[19:06:53] <Lcvette> it gets cumbersome
[19:07:08] <Joco[m]1> It’s only done once?
[19:07:08] <Lcvette> having to remember to not the master tools measurmeent
[19:07:17] <Joco[m]1> Or infrequently
[19:07:17] <Lcvette> then using it to measure new emasurmeents against
[19:07:41] <Joco[m]1> Trapping the master tool measurement should be simple.
[19:07:44] <Lcvette> once is enough if you are doing 20-30 tools
[19:07:57] <Lcvette> hence why i want it simplified
[19:08:45] <Becksvill> guys just a thought. If some has a tool turret or toolpost on a cnc lathe and has gone to all the trouble to set up a probe basic. maybe we should just assume they have installed home switches
[19:08:51] <Lcvette> i also want to do it this way because i would like to e able to use a touch probe on the lathe as well and maybe some form of auto tool measurement that goes in the spindle
[19:08:52] <Lcvette> have some ideas
[19:08:59] <Lcvette> hence the "Probe Basic" way
[19:09:04] <Joco[m]1> I’m just thinking through how I would do it in a lathe DRO tool library and automating the parts that I would normally do by hand.
[19:09:05] <Lcvette> lol
[19:09:37] <Lcvette> i attempted to understand in gmoccapy what was going on and failed at every turn
[19:09:43] <Lcvette> what i expected to happen did not
[19:09:44] <Becksvill> my cnc has a touch probe arm.. would be good to get that running eventually
[19:09:50] <Lcvette> not very intuitive
[19:10:24] <Becksvill> well I will await what you come up with lcvette(y) (y)
[19:10:32] <Lcvette> I would love to put a probe routine in that found true center
[19:10:50] <Lcvette> and use it as the master tool
[19:11:16] <Joco[m]1> You still need to reference in the spindle that is running true?
[19:11:26] <Lcvette> so then you could probve the work piece and all is ready to go
[19:12:10] <Lcvette> probe it while the spindle is turning
[19:12:14] <Becksvill> lcvett. I think that might be overkill compared to someone just running home switches because x value never changes relative to the physical machine eg hard stops
[19:12:29] <Joco[m]1> Yup
[19:12:34] <Becksvill> also a lot of the time parts are not even round
[19:12:45] <Lcvette> i don't trust home switches
[19:12:49] <Joco[m]1> If you have a probe and home switches you need to be slapped. Hard.
[19:12:50] <Lcvette> not for positioning
[19:13:00] <Becksvill> eg machining a part in a 4jaw chuck that is square
[19:13:16] <Lcvette> i have tried mechanicals, proximities and none have had repeatability I would base all my tools off of
[19:14:21] <Lcvette> my big machine i put some high end proximity switches and even it never homes perfect everytime
[19:14:39] <Lcvette> it moves around a few tenths
[19:15:00] <Lcvette> using the index pulse from an axis servo encoder would help
[19:15:08] <Lcvette> but not everyone will be running servos
[19:15:10] -!- c-log has quit [Ping timeout: 260 seconds]
[19:15:18] <Joco[m]1> Encoder or scales with indexes. :-p
[19:15:32] <Joco[m]1> Preferably the later
[19:15:37] <Becksvill> normally on cnc lathes you set up all your tool offsets and they don't change. after that point say you turned the machine on and wanted to set things up. you could choose tool 1 or any tool really and take a cut measuring what it is actually is cutting. then compare that to the value in the dro. if they are different just update the dro x axis
[19:15:37] <Becksvill> value
[19:16:05] <Lcvette> but i know exactly what you guys are saying
[19:16:40] <Lcvette> Becksvill: yup
[19:16:49] <Lcvette> i agree with you there
[19:16:49] -!- c-log has joined #hazzy
[19:16:55] <Becksvill> the tool offsets will still stay the same. and if you can't trust your home switches then just take a cut with any tool. for the sake of simplicity you could use the master tool eg tool 1. but it really doesnt matter
[19:17:04] <Lcvette> thats how i have been running my lathe recently
[19:17:27] <Becksvill> measure what it is actually cutting and then put that into the controller
[19:17:31] <Lcvette> i think I will set it up for master tool mode
[19:17:42] <Lcvette> seems like the simplest way to do things
[19:18:58] * TurBoss uploaded an image: Captura de pantalla de 2020-06-16 01-18-34.png (103KB) < https://matrix.org >
[19:18:59] * TurBoss uploaded an image: Captura de pantalla de 2020-06-16 01-16-17.png (104KB) < https://matrix.org >
[19:19:11] <Lcvette> hurray!!!
[19:19:19] <Lcvette> you aligned the tools!!
[19:19:20] <Lcvette> thats great turboss!!
[19:19:39] <Becksvill> one thing that linuxcnc is really lacking currently is a way to easily adjust the tool offsets easily. eg if tool 2 had a worn insert and started cutting slightly over size and you wanted to change it currently there is only the one offset that you can change. what it needs is a place where you can just type in -.01mm or whatever and it
[19:19:40] <Becksvill> calculates it for you
[19:19:59] <Becksvill> I think other controllers call them wear offsets. they are so important
[19:20:16] <Lcvette> yeah it looks like path pilot has that
[19:20:21] <Lcvette> not sure how they nimplemented it
[19:21:21] <Joco[m]1> <Becksvill "measure what it is actually cutt"> Essentially what I do on my manual lathe
[19:23:34] <Joco[m]1> On my mill I use dynamic TLO but that does not play well with offsets from the tool table.
[19:27:17] <Joco[m]1> Maybe pathpilot uses g43.2 ?
[19:28:31] <Becksvill> lcvette. here is what tormach does. this is the other way I was talking about. I like it. https://www.youtube.com
[19:29:17] <Becksvill> you have to remember also often you will have a part in the lathe that is long and needs a tailstock. so probing both sides of the part in that case would cause a crash
[19:29:25] <Lcvette> watching now
[19:30:49] <Joco[m]1> All this cnc lathe talk has me wondering. Do I have room in my garage .... but I sooo wanted a surface grinder.
[19:31:20] <TurBoss> they are nice
[19:33:30] <Joco[m]1> Was going to use my bonus to buy one. Manual version, new. But then covid landed.
[19:34:05] <Joco[m]1> finding “smallish” second hand ones in NZ are like hens teeth.
[19:34:28] <Joco[m]1> Becksvill: unless you have visibility of such stuff ?
[19:34:57] <TurBoss> at job i they habe a danobat big one
[19:35:02] <TurBoss> more then 2 x 1.5 m
[19:35:17] <Becksvill> joco here in new zealand surface grinders are about 2k second hand for a decent one
[19:35:19] <Joco[m]1> Yeah. Me looking at more baby sized in comparison.
[19:35:21] <Becksvill> I have one up here
[19:35:31] <Becksvill> mine weighs about 1 ton
[19:35:32] <Joco[m]1> Where you find them?
[19:35:40] <Becksvill> trade me is fine
[19:35:54] <Becksvill> no one wants them in industry unless they are cnc now
[19:35:56] <Joco[m]1> That is where I struggle, finding the siding things.
[19:36:16] <Becksvill> what is your budget?
[19:36:34] <Joco[m]1> have standing search on trademe but only stuff that has come up is just too big
[19:36:42] * Lcvette uploaded an image: Screenshot_2020-06-15_19-36-30.png (30KB) < https://matrix.org >
[19:36:57] <Becksvill> also because of the shutdowns so many companies are going out of business that they are cheaper than ever right now
[19:37:01] <Lcvette> so if you enter in the master tool number in that box
[19:37:20] <Joco[m]1> https://www.machineryhouse.co.nz
[19:37:26] <Becksvill> joco If I see something I will let you know.
[19:37:26] <Lcvette> then measure a skim cut in both x and z and enter the diameter for X in the x box and set z to 0.000
[19:37:32] <Joco[m]1> Had been looking at one of these.
[19:37:34] <Lcvette> that would give the baseline for all te other tools
[19:37:57] <Becksvill> lcvette yes that sounds right
[19:38:02] <Lcvette> then i would make a rule for the touch x and touch z buttons that pulled the data from the master tool boxes to make the offsets with just the touch of a button
[19:38:15] <Joco[m]1> <Becksvill "joco If I see something I will l"> That would be AWESOME
[19:38:46] <Joco[m]1> Just don’t tell the wife. ;-)
[19:38:55] <Lcvette> it would record the difference in x and z to the tool offsets table
[19:39:06] <Lcvette> does that seem like the right way?
[19:39:41] -!- CaptHindsight has quit [Remote host closed the connection]
[19:40:04] -!- CaptHindsight has joined #hazzy
[19:40:04] -!- CaptHindsight has quit [Changing host]
[19:40:04] -!- CaptHindsight has joined #hazzy
[19:40:49] * TurBoss uploaded an image: image.png (208KB) < https://matrix.org >
[19:41:08] <Becksvill> lol turboss
[19:41:20] <TurBoss> we have this one
[19:41:28] <TurBoss> rtc1200
[19:43:05] <Becksvill> lcvette. not sure how it would work in the background. but you want to be able to just replace your current x and z axis value with the new measured value. I think tormach has it nailed.
[19:43:35] <Becksvill> we could just copy them for a lot of stuff. making changes as required if you want something different
[19:43:43] <Lcvette> this method makes it so it will auto pull that data from the dro
[19:43:57] <Lcvette> and compare to the single time entered master tool x and z
[19:44:11] <Lcvette> so say you skim cut x to 1.4000"
[19:44:27] <Lcvette> you enter 1.4000 in teh X box and it is recorded
[19:44:41] <Lcvette> then skim z and set z box to 0.000
[19:45:17] <Lcvette> then load the next tool and touch off on the skimmed x diameter and hit the touch x button, it takes the current dro reading and takes the difference of the stored master tool
[19:45:32] <Lcvette> this is doing the same thing but you don't have to enter anything, just hit s button
[19:45:40] <Joco[m]1> TurBoss: oooo. There is half the garage gone.
[19:45:43] <Lcvette> * this is doing the same thing but you don't have to enter anything, just hit abutton
[19:46:16] <Becksvill> lcvette. in that case your way sounds perfect
[19:46:37] <Lcvette> yeah no fiddling with reading and entering dro's incorrectly on accident'
[19:46:45] <Lcvette> fool proofing is the way i like to do it
[19:46:57] <Lcvette> but i guess i see an issue
[19:47:12] <Lcvette> if you are using the paper touch method this will not add in that paper thickness
[19:47:20] <Becksvill> yes.
[19:47:22] <Lcvette> i cold use another box to add that amount
[19:47:36] <Lcvette> what would it be called?
[19:47:37] -!- roper has joined #hazzy
[19:48:18] <Becksvill> I think the way tormach does it is ok. and you might be complicating it possibly.
[19:48:50] <Lcvette> their way is not bad
[19:49:26] <Lcvette> but 9 out of 10 times you will use the same touch off medium im guessing so that thickness entered could be hard saved and only change if manually re-entered
[19:49:40] <Lcvette> would still take the math out of the hands of the user
[19:50:04] <Lcvette> and keep it to a one button touch for all the subsequent tool offset measurements
[19:50:09] -!- MrHindsight has joined #hazzy
[19:50:09] -!- MrHindsight has quit [Changing host]
[19:50:09] -!- MrHindsight has joined #hazzy
[19:50:21] <Joco[m]1> Would you use a feeler gauge? That would be consistent.
[19:50:29] <Becksvill> you only actually need to face the z axis with the master tool. the x axis doesn't matter. assuming your machine is set up with home switches or you do what they did and set up with the master tool block you can take a cut at any size and measure it and put that into the tool offset for that tool
[19:50:30] <Lcvette> i know i tear off a post it for my measurements
[19:51:14] -!- CaptHindsight has quit [Ping timeout: 240 seconds]
[19:51:43] <Becksvill> and all the relative tool offsets will remain regardless so you will normally only have to set up tools very rarely.
[19:52:03] <Becksvill> I think I used to do it every couple of months just to check them
[19:52:07] <Lcvette> or if you change your master tool
[19:52:17] <Joco[m]1> Is a small variation in thickness really material? Given you have not real reference until facing or having done a diam cut.
[19:52:43] <Lcvette> thats the thing with master tool method
[19:52:56] <Becksvill> apart from that they just stay the same. and you can adjust the wear offsets to suit when machining the job
[19:52:59] <Lcvette> you can't really take a cut after the mnater has made its skim pass or you loose your reference
[19:53:35] <Lcvette> im surious about the other method not using the master tool
[19:53:40] <Lcvette> is there one?
[19:53:52] <Lcvette> all i have seen is the master tool method porttrated
[19:53:57] <Lcvette> * all i have seen is the master tool method portrayed
[19:55:10] <Becksvill> lcvette. I will make some thing up now to show the method I use with a normal turning tool eg tool 1
[19:55:25] -!- roper has parted #hazzy
[19:58:11] <Lcvette> Becksvill: great!!
[19:58:49] <Lcvette> TurBoss: are you still working on the qml stuff?
[20:02:00] <TurBoss> did some little
[20:04:20] <Lcvette> pushy?
[20:04:23] <Lcvette> /:D
[20:04:32] <Lcvette> * push?
[20:04:39] <Lcvette> * :D
[20:06:09] <TurBoss> sure
[20:12:36] <Not-944e> [02probe_basic] 07TurBoss pushed 032 commits to 03master [+0/-0/±2] 13https://git.io/Jf7jQ
[20:12:37] <Not-944e> [02probe_basic] 07TurBoss 032c34f80 - show reference lines
[20:12:39] <Not-944e> [02probe_basic] 07TurBoss 03ab97b1d - set destintation points
[20:12:45] <TurBoss> done
[20:13:16] <Lcvette> \o/
[20:13:19] <Lcvette> hurray!
[20:13:50] <Not-944e> [02probe_basic] 07Lcvette pushed 032 commits to 03master [+0/-0/±4] 13https://git.io/Jf7jd
[20:13:52] <Not-944e> [02probe_basic] 07Lcvette 03c175278 - play with tool offset mode
[20:13:53] <Not-944e> [02probe_basic] 07Lcvette 033da9dae - Merge remote-tracking branch 'origin/master'
[20:14:20] <Not-944e> [02probe_basic] 07KurtJacobson pushed 031 commit to 03gh-pages [+88/-0/±0] 13https://git.io/Jf7jb
[20:14:22] <Not-944e> [02probe_basic] 07traviscibot 03cf05c0d - Deploy kcjengr/probe_basic to github.com/kcjengr/probe_basic.git:gh-pages
[20:15:07] <Not-944e> [02probe_basic] 07KurtJacobson pushed 031 commit to 03gh-pages [+88/-0/±0] 13https://git.io/Jf7jA
[20:15:09] <Not-944e> [02probe_basic] 07traviscibot 031fa2d26 - Deploy kcjengr/probe_basic to github.com/kcjengr/probe_basic.git:gh-pages
[20:15:38] <Lcvette> TurBoss: need to do some tweaks i think
[20:16:07] <TurBoss> sure
[20:16:14] <TurBoss> find the qml file
[20:16:27] <Lcvette> maybe the box sizes need adjusting on the tool images
[20:16:28] <TurBoss> :P
[20:16:44] <TurBoss> how? what?
[20:17:15] <Lcvette> the tools should land on the dimension lines in specific positions
[20:17:22] <Lcvette> so they make sense
[20:17:30] <TurBoss> ah
[20:17:31] <TurBoss> each one?
[20:17:37] <Lcvette> yes
[20:17:38] <TurBoss> ya i imagined
[20:17:58] <Lcvette> is it set up so its easy to change int he qml?
[20:17:59] <TurBoss> yup I'l try to fin the way to set the tools origin
[20:17:59] <Lcvette> i can tinker on it
[20:18:11] <Lcvette> ok great!
[20:18:30] <Lcvette> qtcreator?
[20:19:32] <Lcvette> turboss qt quick designer?
[20:19:45] <Becksvill> Method for touching up tools in a cnc lathe 1. choose a tool that will be the master tool. This can be any number but the easiest way is to be tool 1 2. take a facing cut with this tool so set a z axis reference point for everything 3. set all the other tools to this freshly cut face 4. that is all the z axis offsets done. 5. On
[20:19:46] <Becksvill> the industrial controllers I use there is a recall button that allows me to touch up on the freshly cut face with the next tool and push recall which loads the z offset value for that tool automatically.Because the x axis spindle centre point is fixed on a cnc lathe instead of moving like on a cnc mill the x axis offsets can all be set but just
[20:19:46] <Becksvill> taking a cut and measuring the size and then entering that value into the tool dia for that tool.I think I need to find some more videos to explain this lol and this is not that clear
[20:19:56] * Lcvette uploaded an image: Screenshot_2020-06-15_20-19-45.png (16KB) < https://matrix.org >
[20:20:45] <Becksvill> this is not that clear lcvette sorry. I need to find some more videos to link here
[20:20:59] <TurBoss> Lcvette: open the qml file with qtcreator
[20:21:41] <Lcvette> Becksvill: ok
[20:21:58] <Lcvette> yeah i think it is missing some information on how ti uses that recall and the new skim cut
[20:22:29] <Lcvette> im guessing it takes it from a number somewhere but is it from the master tool's skim cut diameter or is it from machine coords x zero?
[20:22:42] <Lcvette> TurBoss: im trying this is the options it gives
[20:23:12] <TurBoss> QMLJS
[20:25:23] <Becksvill> lcvette this is how fagor does it. and works quite well. the first part is blurry so but there is a clear close up a 2:25
[20:25:24] <Becksvill> https://www.youtube.com
[20:25:45] <Joco[m]1> Becksvill: on a repeating tool holder for the lathe isn’t the Z offset for a tool also stored? Relative the master tool?
[20:26:38] <Becksvill> yes definitely. but you never know where in machine space the first z axis cut is. unlike the x axis where the zero point is fixed
[20:26:59] <Becksvill> but it sounds like I just confused people lol sorry guys
[20:28:18] <Lcvette> Becksvill: thanks, i will give it a watch
[20:34:39] <Becksvill> lcvette actually don't watch that fagor video. I found a NYC video what is so much better he is showing how to set up tools in tormach pathpilot
[20:34:45] <Becksvill> https://www.youtube.com
[20:36:12] <Joco[m]1> <Becksvill "yes definitely. but you never k"> Cool. Yes until first facing cut you are in referenced in Z
[20:36:35] <Joco[m]1> * > <@freenode_Becksvill:matrix.org> yes definitely. but you never know where in machine space the first z axis cut is. unlike the x axis where the zero point is fixed
[20:36:35] <Joco[m]1> Cool. Yes until first facing cut you are unreferenced in referenced in Z
[20:38:52] <Becksvill> just a quick note on the NYC video guys. the reason he had to re measure that first cut in the video several times is he was slowly feeding backwards off the job after taking a skim cut. which altered his size. if he moved off the job in the z axis much faster he wouldn't have changed the size.
[20:39:15] <Becksvill> and of course a more rigid setup and machine would have had less spring in it
[20:42:31] -!- MrHindsight has quit [Ping timeout: 246 seconds]
[20:46:11] <Becksvill> a couple of other things about john saunders NYC cnc video. I never bother with paper. I just take a skim cut with the master tool. in x and z and then touch up to that spinning bare metal surface with the next tool I want to touch up.
[20:46:44] <Becksvill> If I really cared about the size I might take another cut on the x axis dia and measure that just to be sure.
[20:47:05] <Becksvill> any thing closer than that can be fine tuned with the wear offsets
[20:48:46] <Becksvill> on a lathe things are changing all the time. eg longer parts get tool deflection. and cut taper because of that. and longer boring bars also get tool deflection. often significant amounts. like 0.20mm so I get set things up and then take a cut and measure what I actually get, then adjust the wear offsets to suit
[20:49:16] <Becksvill> it is quite a bit different to a cnc mill.
[20:51:53] <Joco[m]1> Yeah. A lot of what you are saying translates into what I essentially do in my head on the manual lathe.
[20:56:33] <Becksvill> yes it is all pretty much the same. what happened with some of the other guys in the machine shop is they were used to setting up with slant bed lathes and we had a teach lathe. they couldn't just hack some things that didn't matter and everything had to be perfect. so they took ages to make anything
[20:57:44] <Becksvill> they guys that taught me could program a part in like 2mins and then be cutting. I learnt there way and even for one off parts it was often easier to just use the cnc. the programming was so fast. and you didn't have to think about what size the machine was cutting
[20:58:47] <Becksvill> for bearing fits and stuff on one off parts often we would run the finishing pass .2 mm over size measure that with a micrometer and then dial in the tool wear offset to get the right size on the final pass.
[20:59:38] <Joco[m]1> heh. Just like on manual
[21:00:13] <Joco[m]1> and make last two cuts even so as to get balanced deflection.
[21:00:33] <Becksvill> if you did a production run we could just trust the cnc to hold size. but it is amazing how much parts deflect when machining. in practice we adjust the wear offset or the program all the time. for example if the part was deflecting causing taper you would just change the program to cut a taper the other way to end up with a straight part.
[21:00:43] <Becksvill> and yes just make the last two cuts even
[21:00:56] <Becksvill> we did three cuts if there was no room for error
[21:01:02] <Becksvill> just in case
[21:01:42] <Joco[m]1> I like that taper trick. Can’t do that manual
[21:03:50] <Becksvill> well actually you can. just measure how much taper you are getting over the part that needs to be parallel. measure it every 15 mm or so along the length and write on the part how much taper you get. then just tap the handwheel on the dia as you machine along to take out the taper as you go. we do it all the time. very usefull for removing
[21:03:50] <Becksvill> that annoying 0.02 mm taper on parts and easy as
[21:04:06] * Joco[m]1 uploaded an image: ima_6836d5d.jpeg (325KB) < https://matrix.org >
[21:04:14] <Joco[m]1> speaking of manual ....
[21:04:21] <Becksvill> haha
[21:04:30] <Becksvill> thats a baby
[21:04:36] <Becksvill> hey joco
[21:05:05] <Joco[m]1> Alba 1A - my restoration project
[21:05:25] <Joco[m]1> just right size for garage sized workshop.
[21:05:32] <Joco[m]1> And a bit of old school fun.
[21:05:46] <Becksvill> my email is andrew@carbidecutters.co.nz maybe if you contact me there if I ever see machines going cheap I will let you know. I bought my surface grinder for about 500 nzd lol so they do come up cheap
[21:06:07] <Becksvill> my surface grinds fine
[21:06:19] <Joco[m]1> oh dear lord. Would give my eye teeth for one at the price.
[21:07:36] <Becksvill> seriously they come up all the time. what blows the price up is when they are small and every hobbiest wants them. once they are three phase they are so much cheaper
[21:11:24] <Joco[m]1> I’m prepared to retro fit VFD to three phase of need be. Still cheaper over all.
[21:11:42] <Joco[m]1> Did that on my Dah Leh mill
[21:12:12] <Becksvill> yes they are cheap as
[21:12:44] <Joco[m]1> * Did that on my Dah Lih mill
[21:12:52] <Becksvill> anyway with that I better go and move some machines around in my shed ready for the new cnc mill
[21:13:11] <Joco[m]1> later
[21:13:40] -!- Becksvill has quit [Remote host closed the connection]
[21:44:44] -!- Becksvill has joined #hazzy
[23:59:28] -!- Becksvill has quit [Remote host closed the connection]