#hazzy | Logs for 2018-07-17
Back
[00:00:14] <hazzy-lab> What the heck is the "plugin" setting a slider?? xD
[00:00:27] <hazzy-lab> Why*
[00:04:13] <hazzy-lab> hahah, the emojis come thru in the logs: http://irc-logs.kcjengr.com
[00:09:41] <lcvette[m]2> Yeah.. Saw it.. Replied
[00:09:52] <lcvette[m]2> She's lost her marbles
[00:10:28] <hazzy-lab> Nice reply!!!!
[00:10:38] <lcvette[m]2> She wants a Fischer Price control
[00:10:46] <TurBoss> what pip?
[00:10:48] <hazzy-lab> lol, so true
[00:10:57] <hazzy-lab> pip
[00:11:01] <hazzy-lab> pip 2
[00:11:05] <lcvette[m]2> Pip
[00:11:10] <TurBoss> pip
[00:11:10] <hazzy-lab> is that what you meant?
[00:11:14] <TurBoss> :D
[00:11:15] <hazzy-lab> pip
[00:11:15] <lcvette[m]2> Lol
[00:11:22] <TurBoss> peep
[00:11:43] <hazzy-lab> i'm dieing :D
[00:11:50] <TurBoss> you where talking about makefile
[00:11:51] <TurBoss> not pip
[00:11:59] -!- Roguish has quit [Quit: ChatZilla 0.9.92-rdmsoft [XULRunner 35.0.1/20150122214805]]
[00:12:56] <hazzy-lab> your right, but it I make it a pip package setup.py could do the same things the makefiles does now
[00:13:04] <TurBoss> oh ok
[00:13:05] <hazzy-lab> I think
[00:14:35] * TurBoss was playing some urbanterror
[00:15:04] * hazzy-lab looks up urbanterror
[00:15:07] <hazzy-lab> :)
[00:15:12] <TurBoss> ok so python setup.py will install qtpyvcp/hazzy/brender
[00:15:29] <hazzy-lab> urbanterror looks fun!
[00:15:34] <TurBoss> it is
[00:15:42] <TurBoss> is like counterstrike 1.4
[00:15:46] <TurBoss> before source
[00:16:03] <TurBoss> sadly enemyterritory is ded
[00:16:23] <hazzy-lab> Yes, that is the idea, if there were multiple interfaced (PP clone, Brender ..) they could all be separate pip packages
[00:16:37] <hazzy-lab> maybe
[00:18:11] <TurBoss> afk
[00:18:12] <TurBoss> a bit
[00:18:20] <hazzy-lab> ok
[00:22:32] <hazzy-lab> Lcvette[m]: Thanks for the config folder! Looking at the probe routines
[00:22:41] -HaikuBot[m]:#hazzy- Lcvette[m]: Thanks for the
[00:22:42] -HaikuBot[m]:#hazzy- config folder! Looking at
[00:22:43] -HaikuBot[m]:#hazzy- the probe routines
[00:23:16] <lcvette[m]2> No worries
[00:24:07] <lcvette[m]2> I'm just working on a rougher outline of a probe routine
[00:24:12] -HaikuBot[m]:#hazzy- I'm just working
[00:24:13] -HaikuBot[m]:#hazzy- on a rougher outline of
[00:24:13] -HaikuBot[m]:#hazzy- a probe routine
[00:24:34] <hazzy-lab> lol, we're on a roll!
[00:24:44] <lcvette[m]2> Lol
[00:25:07] <lcvette[m]2> Just wording out things
[00:25:11] <hazzy-lab> Great!
[00:25:48] <lcvette[m]2> I may need more boxes
[00:26:12] <hazzy-lab> Ok, let me know I can add them
[00:26:27] <lcvette[m]2> 😂
[00:26:32] <hazzy-lab> Should I duplicate the boxes in MSM?
[00:26:35] <hazzy-lab> for now?
[00:26:49] <lcvette[m]2> Yes
[00:26:55] <hazzy-lab> ok!
[00:27:02] <lcvette[m]2> I think that's the best thing
[00:27:38] <hazzy-lab> So do I, I don't know why I did not do that to start with
[00:27:40] <lcvette[m]2> If we want the same one touch routines
[00:28:56] <TurBoss> a setup.py would be great but not published to pip
[00:28:57] <TurBoss> as this is very specific software
[00:28:59] <TurBoss> it requires linuxcnc
[00:30:22] <hazzy-lab> it could install LCNC as a dependency xD
[00:30:40] <hazzy-lab> your right, no need to have it on pip
[00:31:04] <TurBoss> lol
[00:31:04] <TurBoss> on windows
[00:31:10] <hazzy-lab> HAHA
[00:31:34] <hazzy-lab> Yeah, bad idea ..
[00:32:03] <TurBoss> we need linuxcnc with python3
[00:32:11] <TurBoss> so I can go back to yocto thing
[00:32:23] <hazzy-lab> yesm we really do
[00:32:33] <hazzy-lab> I was looking at it yesterday, no luck
[00:32:54] <TurBoss> :(
[00:33:46] <hazzy-lab> tried this: https://github.com
[00:35:02] <TurBoss> will try
[00:51:06] * hazzy1[m] uploaded an image: Screenshot_2018-07-17_00-50-21.png (20KB) < https://matrix.org >
[00:51:18] <hazzy1[m]> Lcvette: Better?
[00:51:58] <TurBoss> wow
[00:56:50] <lcvette[m]2> Outstanding!
[00:57:31] <lcvette[m]2> Now I'm getting chills
[00:57:51] <lcvette[m]2> I'm going to dedicate all day tomorrow to this
[00:58:37] <lcvette[m]2> Not sure how far I'll get but I hope to at least get some foundation learned and something written
[00:58:46] <hazzy-lab> That would be fantastic!
[00:59:07] <hazzy-lab> I'll see if I can get this actually working ..
[01:45:16] <hazzy-lab> Lcvette[m]: Finished the probe parameters settings box
[01:45:45] <lcvette[m]2> Seriously?
[01:45:52] <lcvette[m]2> That was fast
[01:46:03] <hazzy-lab> Yes, it is pretty basic
[01:46:23] <lcvette[m]2> Nice
[01:47:01] <lcvette[m]2> Same names as next to the bosses with underscores
[01:47:27] <lcvette[m]2> extra_probe_depth
[01:47:30] <hazzy-lab> yes! How did you know?
[01:47:38] <hazzy-lab> lol, mind reader !
[01:47:42] <lcvette[m]2> Catching on
[01:47:45] <lcvette[m]2> Lol
[01:48:16] <lcvette[m]2> Yoda
[01:48:19] <TurBoss> hey
[01:48:26] <TurBoss> I need help
[01:48:27] <TurBoss> https://github.com
[01:48:41] <TurBoss> I managed to get ./configure to pass
[01:48:48] <TurBoss> with python 3
[01:48:55] <hazzy-lab> HURRAY!!!!
[01:49:09] <lcvette[m]2> Nice
[01:49:13] <TurBoss> did a pullrequest on jepler branch
[01:49:28] * hazzy-lab is reading
[01:49:35] <TurBoss> I know nothing about autotools
[01:50:57] <hazzy-lab> That looks good!
[01:50:59] <TurBoss> it fails on halcompile tests but thats another story
[01:51:24] <hazzy-lab> does it build at all?
[01:51:33] <TurBoss> no
[01:51:35] <hazzy-lab> ok
[01:51:50] <TurBoss> a bit more close
[01:51:57] <hazzy-lab> yes indeed!
[01:52:02] <hazzy-lab> thank you!
[01:53:12] <TurBoss> make does this http://dpaste.com
[01:53:47] <hazzy-lab> hehe
[01:53:54] <hazzy-lab> that should be easy to fix
[01:54:31] <hazzy-lab> py3 catches more errors than py2, which is good
[01:54:59] <hazzy-lab> (Jepler does not like Py3 xD)
[01:57:55] -RSSBot[turbosssp:#hazzy- Hazzy activity posted a new article: Kurt Jacobson pushed new project branch MSMProbe at Hazzy / SubCaller ( https://gitlab.com )
[02:01:52] <hazzy-lab> TurBoss: I get this: http://dpaste.com
[02:02:16] <hazzy-lab> I ran: ./configure --with-python=python3 --with-boost-python=boost_python-py35
[02:02:35] <hazzy-lab> Why does it ask for gtk2?
[02:02:43] <TurBoss> mew
[02:03:14] <lcvette[m]2> Hazzy, may not want to call it that
[02:03:14] <TurBoss> py 3.4?
[02:04:00] <hazzy-lab> Lcvette[m]: Worried about copyrights?
[02:04:09] <hazzy-lab> ah will try 3.4
[02:04:46] <hazzy-lab> same
[02:04:47] <hazzy-lab> :(
[02:04:58] <TurBoss> 😞
[02:05:25] <lcvette[m]2> He can't copy right what you made, but the name he can
[02:05:26] <hazzy-lab> gtk2 is already installed, hmm
[02:05:41] <TurBoss> did you run autoconf.sh?
[02:05:47] <hazzy-lab> Ok, I will change it!
[02:05:54] <TurBoss> before ./configure?
[02:05:56] <hazzy-lab> Oh, no I did not!
[02:05:57] <lcvette[m]2> And he's pretty socket for software license stuff
[02:06:03] <lcvette[m]2> Stickler
[02:06:15] <lcvette[m]2> Good call
[02:06:20] <TurBoss> what is the problem?
[02:06:47] <TurBoss> what name?
[02:07:05] <lcvette[m]2> MSM
[02:07:15] <lcvette[m]2> Machstdmill
[02:07:22] <TurBoss> ah
[02:08:18] <TurBoss> tehn just call it TurBoProbe
[02:08:18] <lcvette[m]2> His code is hidden and would look nothing like what is used in linuxcnc
[02:08:19] <TurBoss> :P
[02:08:20] <TurBoss> TurBoPobre 3000
[02:08:54] <hazzy-lab> Yes!!!
[02:09:01] <hazzy-lab> Still does not work :(
[02:09:11] <lcvette[m]2> And I'm going to change a few things
[02:09:23] <TurBoss> yes what?
[02:09:24] <TurBoss> :P
[02:09:31] <TurBoss> then
[02:09:32] <hazzy-lab> TurBoPobre 3000 :D
[02:09:57] <TurBoss> pobre means poor in spanish
[02:10:06] <hazzy-lab> I know xD
[02:10:11] <TurBoss> hehehe
[02:10:23] <lcvette[m]2> Lol
[02:10:40] <TurBoss> hazzy-lab:
[02:11:11] <TurBoss> hmmm
[02:11:12] <TurBoss> did you picked my linuxcnc branch right?
[02:11:30] <hazzy-lab> I think so, lol
[02:11:51] <TurBoss> ok
[02:12:33] * hazzy-lab is stupid
[02:12:46] <TurBoss> yes?
[02:12:47] <hazzy-lab> I used jeffs branch xD
[02:12:54] <TurBoss> no
[02:13:47] <lcvette[m]2> I dunno what to call the probe
[02:13:52] <lcvette[m]2> Have to ponder it
[02:14:06] <lcvette[m]2> Throw it out in the wild
[02:14:06] <hazzy-lab> too many branches, lol
[02:14:34] <TurBoss> add my fork as remote
[02:14:54] <TurBoss> and checkot configure-python3
[02:14:54] <hazzy-lab> You branch works!
[02:14:59] <TurBoss> hurra!
[02:15:15] <TurBoss> El Chapas aproves
[02:15:34] <hazzy-lab> I had both your's and Jeffs are remotes, I searched on the branch name and picked the wrong one
[02:15:43] <TurBoss> is my cat
[02:15:44] <hazzy-lab> haha
[02:15:47] <lcvette[m]2> Python 3?
[02:16:02] <TurBoss> so it configures?
[02:16:08] <lcvette[m]2> It works?
[02:16:26] <TurBoss> make should fail
[02:17:54] <hazzy-lab> It does: http://dpaste.com
[02:18:27] <hazzy-lab> print does not have ()
[02:18:38] <hazzy-lab> that is farther than you got?
[02:18:47] <lcvette[m]2> You guys are trying to make linuxcnc and python 3 work together?
[02:18:48] <TurBoss> so I don't have to close the Pull Request
[02:19:02] <TurBoss> yes if we can
[02:19:21] <hazzy-lab> Py2 is almost at its end of life
[02:19:35] <hazzy-lab> https://pythonclock.org
[02:19:42] <TurBoss> hehehe
[02:19:49] <lcvette[m]2> Gotcha
[02:19:54] <TurBoss> bad news python father leaves
[02:20:01] <hazzy-lab> less than a year and a half left :0
[02:20:25] <hazzy-lab> Oh no, really? Guido leaves?
[02:20:39] <TurBoss> aka Guido
[02:21:05] <TurBoss> sadly yes
[02:21:11] <hazzy-lab> That is very sad
[02:21:13] <TurBoss> sek I'll search his email
[02:21:28] <hazzy-lab> thanks
[02:22:02] <TurBoss> https://mail.python.org
[02:23:02] <lcvette[m]2> What about Ruby for the probe screen
[02:24:41] <hazzy-lab> Ruby is too magical for a machine controller
[02:24:43] <hazzy-lab> :D
[02:25:30] <hazzy-lab> he sounds a little frustrated and tired in that email :(
[02:25:55] <TurBoss> yes...
[02:26:00] <lcvette[m]2> But what if we use some anime porn and Ruby stylus tips as nipples
[02:26:05] <lcvette[m]2> Lol
[02:26:09] <hazzy-lab> LOL
[02:26:16] <TurBoss> buttons could be tits
[02:26:41] <lcvette[m]2> Hahaha
[02:26:50] <TurBoss> but all censored
[02:26:51] <hazzy-lab> xD
[02:26:55] <TurBoss> please
[02:27:02] <lcvette[m]2> Glad you guys have a sense of humor
[02:28:04] <hazzy-lab> what's life without humor ;)
[02:28:25] * hazzy-lab is getting tired ..
[02:28:52] <lcvette[m]2> Yup.. I'm delerious tired
[02:29:24] <TurBoss> time to go bed
[02:29:27] <TurBoss> n8 guys
[02:29:40] <hazzy-lab> TurBoss: It is morning in spain yet?
[02:29:48] <hazzy-lab> probably, lol
[02:29:53] <hazzy-lab> gn8
[02:30:21] <TurBoss> as usual
[02:30:36] <hazzy-lab> haha
[02:30:41] <TurBoss> 8:30
[02:30:44] <TurBoss> am
[02:30:57] <TurBoss> I should change my habits...
[02:30:58] <hazzy-lab> You won't be late to work xD
[02:31:18] <TurBoss> ...
[02:31:23] <hazzy-lab> It's only 2:30 am here
[03:10:06] <hazzy-lab> Hurray! I converted halcompil.py and elbpcom.py to py3
[03:10:29] <hazzy-lab> not it has errors with the C++ python bindings in emc/task/taskclass.cc
[03:10:34] <hazzy-lab> time for bed ..
[08:59:31] <TurBoss> https://github.com
[09:44:25] <hazzy1> I told you, Jepler does not like Py3 xD
[09:45:05] <hazzy1> I talked with him about it for a while once, he hates it, lol
[09:47:03] <hazzy1> I hope they merge https://github.com
[10:22:23] <Lcvette[m]> yeah!
[10:22:31] <Lcvette[m]> merge dammit
[10:22:51] <hazzy-lab> hehe
[10:22:56] <hazzy-lab> Get some sleep?
[10:23:20] <hazzy-lab> I had trouble waking up :]
[10:23:27] <Lcvette[m]> linuxcnc i went off on a reading tangent last night
[10:23:54] <Lcvette[m]> i just woke up
[10:23:56] <Lcvette[m]> lol
[10:24:04] <hazzy-lab> good!
[10:25:05] <Lcvette[m]> coffee not working yet
[10:25:08] <Lcvette[m]> lol
[10:25:40] <hazzy-lab> I ran out of coffee already, I will need to make some more :D
[10:45:36] -!- Roguish has joined #hazzy
[11:22:27] <TurBoss> yep
[11:22:39] <TurBoss> i just rememberer that rene-dev is also working on the same
[11:22:56] <hazzy-lab> Yes, I don't think he got as far though
[11:23:17] <TurBoss> i should unify all
[11:23:24] <TurBoss> remembered
[11:24:07] <TurBoss> but went good
[11:25:42] <hazzy-lab> very good
[11:26:21] <hazzy-lab> now we need to fix the c++ py bindings ...
[11:26:31] <hazzy-lab> I am lost on that :)
[11:31:08] <lcvette[m]2> Hazzy... Was late last night, I missed the x hint, y hint, diameter boxes. 😮
[11:33:14] <lcvette[m]2> No rush, im going to be laying out the formats and that in itself is going to take some itme
[11:39:03] <hazzy-lab> I missed them too, must have been late :)
[12:08:11] <Lcvette[m]> lol
[12:18:06] <hazzy-lab> I am trying to add probe results section as well, don't quite one how to do that though ..
[12:18:18] <hazzy-lab> know how*
[12:20:15] <Lcvette[m]> iimagine they would be a normal dro
[12:20:40] <Lcvette[m]> that read zero unless written to by the subroutines
[12:21:42] <hazzy-lab> Not quite, because it should show the values in parameters 5061 to 5069, I think
[12:21:51] <Lcvette[m]> numbers should be static non moving
[12:22:43] <Lcvette[m]> right but those number are static
[12:22:52] <Lcvette[m]> meaning not they change but only when rewritten
[12:22:57] <Lcvette[m]> not a flowing
[12:23:01] <Lcvette[m]> pulse source
[12:23:07] <hazzy-lab> ha, yes, i see what you mean!
[12:23:37] <Lcvette[m]> you understand but you also are thinking that doesn't mean jacksquat..lol
[12:23:46] <hazzy-lab> Yes, they should only be changed on a sucsesfull probe
[12:23:52] <hazzy-lab> lol
[12:23:57] <Lcvette[m]> hahahhaa
[12:25:26] <Lcvette[m]> ok, so do you know how to link the var file 5061-5069 entries to dro boxes?
[12:25:55] <Lcvette[m]> and then do they require a trigger to update? or are they kept constantly update based on a refresh in the system?
[12:26:16] <Lcvette[m]> im curious as i don't understand how things work
[12:27:01] <hazzy-lab> That is what I am mulling over, how to get those values ...
[12:27:47] <Lcvette[m]> in MSM the values remain the same until a new probe event has completed and the data is calculated
[12:27:48] <Lcvette[m]> ah ok
[12:28:00] <Lcvette[m]> you are on the linking process
[12:28:10] <Lcvette[m]> if thats what you call it
[12:28:11] <Lcvette[m]> this is a good thing
[12:28:23] <hazzy-lab> yes
[12:28:32] <Lcvette[m]> this will be required for alot of other things
[12:28:46] <Lcvette[m]> ATC :)
[12:30:03] <hazzy-lab> Sweet! The python python interface already includes signals for probe events!
[12:30:13] <hazzy-lab> (I don't remember doing that, lol)
[12:30:58] <Lcvette[m]> ATC Pocket numbers are assigned to var file 5xxx numbers and that is where it stores the current tool stored in that pocket
[12:30:58] <Lcvette[m]> oh sweet!
[12:31:43] <hazzy-lab> Ok, so I need to add the toll signals too
[12:31:57] <hazzy-lab> don't thing I did that yet, but who knows :D
[12:32:29] <Lcvette[m]> yes we should add a toll signal so every time someone uses the probe we get a click charge amount sent to our paypal accounts
[12:32:30] <Lcvette[m]> i like it
[12:32:44] <Lcvette[m]> lol
[12:33:09] <hazzy-lab> hahahaha
[12:33:56] <Lcvette[m]> "please deposit additional tokens to complete probing routine"
[12:34:01] <Lcvette[m]> lol
[12:34:18] <hazzy-lab> xD
[12:34:26] <Lcvette[m]> seriously though thats awesome man
[12:34:28] <Lcvette[m]> great job
[12:36:34] <hazzy-lab> Only problem, I think the probe screen will have to start relying on QtPyVCP ...
[12:38:12] <Lcvette[m]> what does that mean for the goal of being a free standing integrate-able module?
[12:40:39] <hazzy-lab> It won't effect that, but it means I need to get busy working on QtPyVCP
[14:16:55] <hazzy-lab> Got the probed pos readouts working!!!!
[14:21:24] <Lcvette[m]> really?
[14:21:31] <Lcvette[m]> thats awesome!!
[14:21:36] * hazzy1[m] uploaded an image: Screenshot_2018-07-17_14-21-14.png (36KB) < https://matrix.org >
[14:21:49] <hazzy1[m]> Those are actual probe results1
[14:22:16] <Lcvette[m]> you probed?
[14:22:33] <hazzy1[m]> I guess I should change "GroupBox" to results :D
[14:23:20] <hazzy1[m]> Yes, not a real probe, but I twiddled the probe input pin so LCNC though it probed for real
[14:23:44] <Lcvette[m]> hahahaha thats fantastic!!!
[14:24:09] <Lcvette[m]> this guy really did some work creatingt he probe routines
[14:24:37] <Lcvette[m]> i started writing them out trying to do it in my head and that was a no go
[14:24:39] <Lcvette[m]> alot of variables to consider
[14:24:58] <hazzy-lab> Yes, they can get complicated!
[14:25:04] <Lcvette[m]> had to make a chart to keep track of everything that needs to be tracked and used
[14:25:12] <hazzy-lab> great!
[14:25:24] <Lcvette[m]> working on that now
[14:25:26] <Lcvette[m]> slowly but surely
[14:25:30] <Lcvette[m]> finding out what i don't know stages
[14:25:59] <hazzy-lab> I wort a basic probe z routine, I will include that when I sent the probe screen GUI
[14:26:08] <hazzy-lab> wrote* lol
[14:26:27] <Lcvette[m]> awesome!
[15:22:01] <TurBoss> hello
[15:22:08] <hazzy-lab> hey
[15:22:22] <TurBoss> sup?
[15:22:32] <hazzy-lab> working on probing
[15:22:57] <hazzy-lab> we need a way to get return values from a sub
[15:23:01] <TurBoss> I have to work on the camera thing
[15:23:17] <hazzy-lab> yes!
[15:23:36] <hazzy-lab> But not very important, still a long way to go :)
[15:23:41] <TurBoss> what kind of data?
[15:23:43] <TurBoss> anything?
[15:23:53] <hazzy-lab> Just parameters
[15:23:57] <hazzy-lab> numbers
[15:24:32] <TurBoss> if you set a hal_pin to 0 on startup and increase it on the sub?
[15:24:33] <TurBoss> ugly
[15:25:07] <hazzy-lab> You can't set hal pins from gcode, only read :(
[15:25:33] <TurBoss> ught
[15:25:47] <hazzy-lab> Looking at this: https://github.com
[15:25:55] <hazzy-lab> But what is self??
[15:26:04] * hazzy-lab is confused
[15:26:16] <TurBoss> a custom MCODE?
[15:26:45] <hazzy-lab> no, just the way they get the parameter value: self.params["speed"] = c.s_number
[15:26:48] <TurBoss> no the self
[15:27:23] <hazzy-lab> Maybe could use in non remap code, but I don't know what self is, lol
[15:27:36] <hazzy-lab> I am got to make a remap and print self :D
[15:27:55] <TurBoss> oh
[15:28:20] <Lcvette[m]> which portion Hazzy?
[15:28:53] <hazzy-lab> you mean of the file?
[15:29:53] <hazzy-lab> just looking at how they read the parameters, but I think that can only be done in a remap
[15:30:27] <Lcvette[m]> what are you trying to get?
[15:31:57] <hazzy-lab> You know the "Probed Width" and "Probed Dia" DROs in MSM? Those values have to come from the subroutine, but I don't know how to get them
[15:32:16] <Lcvette[m]> which parameter?or any of them you mean?
[15:32:40] <hazzy-lab> Ideally it would be nice to be able to get any parameter
[15:33:33] <Lcvette[m]> from?
[15:33:35] <Lcvette[m]> NGC?
[15:33:48] <Lcvette[m]> confused where youre trying to pull from
[15:33:58] <hazzy-lab> from the interpretor
[15:34:12] <hazzy-lab> which is reading the NGC files
[15:34:34] <Lcvette[m]> from my reading i thought those were output using a print command?
[15:34:58] <hazzy-lab> heh, there is an idea!
[15:35:15] <hazzy-lab> It would be a kludge, but it may work!
[15:36:40] <TurBoss> http://linuxcnc.org
[15:37:07] <hazzy-lab> but those are only the probed positions
[15:37:12] <TurBoss> http://linuxcnc.org
[15:38:00] <TurBoss> what do you need?
[15:38:25] <hazzy-lab> maybe we could pipe stderr
[15:38:35] <hazzy-lab> sek, I will explain
[15:38:58] <TurBoss> sound hacky
[15:39:10] <hazzy-lab> it would be :(
[15:39:28] <TurBoss> :)
[15:39:28] <Lcvette[m]> http://linuxcnc.org
[15:40:16] <Lcvette[m]> section 15.. logging maybe?
[15:40:45] <Lcvette[m]> then slightly past that is print and special handling of printed output
[15:41:15] <Lcvette[m]> i don't understand most of it but rememberd seeing it
[15:41:15] -HaikuBot[m]:#hazzy- then slightly past that
[15:41:16] -HaikuBot[m]:#hazzy- is print and special handling
[15:41:17] -HaikuBot[m]:#hazzy- of printed output
[15:41:24] <TurBoss> https://www.forum.linuxcnc.org
[15:41:28] <TurBoss> seems tha you are here
[15:41:35] <Lcvette[m]> ah yeah bot action baby
[15:42:08] <TurBoss> ✌
[15:42:18] <hazzy-lab> TurBoss: Yes! I was trying to find that again, thanks
[15:44:54] <TurBoss> https://github.com
[15:44:58] <TurBoss> what about this?
[15:45:40] <hazzy-lab> but what is self? lol
[15:47:33] <TurBoss> hmmmm
[15:47:35] <TurBoss> another direction
[15:47:37] <TurBoss> mentioned here
[15:47:38] <TurBoss> It already exists, in your config directory is a file called emc.var or linuxcnc.var
[15:47:56] <TurBoss> https://forum.linuxcnc.org
[15:48:10] <hazzy-lab> yes, but that files does not have the current values
[15:48:48] <TurBoss> ok
[15:48:50] <TurBoss> and this ? It already exists, in your config directory is a file called emc.var or linuxcnc.var
[15:48:51] <TurBoss> oop
[15:48:51] <TurBoss> s
[15:48:52] <TurBoss> http://www.linuxcnc.org
[15:49:02] * Lcvette[m] sent a long message: < https://matrix.org >
[15:50:00] <Lcvette[m]> the interpreter instance
[15:50:07] <hazzy-lab> Lcvette[m]: Perfect!
[15:50:15] <hazzy-lab> Thank you!!
[15:50:36] <hazzy-lab> So, now, how to get the interpretor instance ...
[15:50:52] <Lcvette[m]> no idea what i gave you
[15:50:53] <Lcvette[m]> but it appeared to be what you asked for
[15:51:06] <hazzy-lab> yes, that was very helpfull
[15:51:43] <hazzy-lab> were did you find that?
[15:51:46] <Lcvette[m]> http://linuxcnc.org
[15:51:49] <Lcvette[m]> where it came from
[15:51:52] <hazzy-lab> thanks
[15:52:25] <Lcvette[m]> monkey typed it in google
[15:52:33] <Lcvette[m]> lol
[15:52:40] * TurBoss sent a long message: < https://matrix.org >
[15:52:53] <hazzy-lab> your google foo is better than mine :D
[15:53:09] <TurBoss> get_T_number is the function that uses the self
[15:55:19] <Lcvette[m]> blind squirrel and all
[16:12:41] * TurBoss uploaded an image: Captura de pantalla de 2018-07-17 22-12-07.png (318KB) < https://matrix.org >
[16:12:53] * TurBoss uploaded an image: Captura de pantalla de 2018-07-17 22-12-18.png (217KB) < https://matrix.org >
[16:15:25] <Lcvette[m]> nice!
[16:15:37] <TurBoss> thx
[16:21:56] -RSSBot[turbosssp:#hazzy- Hazzy activity posted a new article: TurBoss pushed to project branch CameraWidget at Hazzy / QtPyVCP ( https://gitlab.com )
[16:28:26] <hazzy-lab> LOL, I like the image of an image of an image of a ....
[16:31:06] <TurBoss> its magic
[16:32:11] * TurBoss is watching some alien/god fake documentary
[16:48:54] <Lcvette[m]> hazzy-lab: is it possible to have a pop up window with a graphic in linuxcnc?
[16:49:05] <Lcvette[m]> like a helper diagram?
[16:49:18] <hazzy-lab> Sure!
[16:50:25] <Lcvette[m]> interesting
[17:09:59] * Lcvette[m] uploaded an image: step_off_width.png (143KB) < https://matrix.org >
[17:10:19] <hazzy-lab> Very nice!
[17:10:32] <Lcvette[m]> so little helper graphics that could pop up for the boxes
[17:10:35] <hazzy-lab> Now I need to make a popup window to show it in
[17:11:07] <Lcvette[m]> actually don't use that, i can make it more condensed
[17:11:18] <hazzy-lab> ok
[17:12:58] * Lcvette[m] uploaded an image: step_off_width.png (122KB) < https://matrix.org >
[17:13:18] <hazzy-lab> much better!
[17:15:13] <Lcvette[m]> its still huge
[17:15:16] <Lcvette[m]> lol
[17:15:21] <Lcvette[m]> can you shrink it?
[17:15:41] <hazzy-lab> Yes, its better to have it too big than too small!
[17:15:42] <Lcvette[m]> or do i need to?
[17:15:44] <Lcvette[m]> im a dummy
[17:15:53] <Lcvette[m]> but can figure it out if you need a certain size or something
[17:15:54] -HaikuBot[m]:#hazzy- but can figure it
[17:15:55] -HaikuBot[m]:#hazzy- out if you need a certain
[17:15:55] -HaikuBot[m]:#hazzy- size or something
[17:16:02] <hazzy-lab> LOL
[17:16:20] <Lcvette[m]> ok
[17:16:33] <Lcvette[m]> hahaha
[17:16:41] <hazzy-lab> I think I might shrink them at load time, then they would still look good on a high res screen
[17:17:00] <Lcvette[m]> sweet
[17:17:05] <Lcvette[m]> ok i will keep them this size
[17:17:26] <Lcvette[m]> these are part of my builder manual to help me make the routines
[17:17:30] -HaikuBot[m]:#hazzy- these are part of my
[17:17:31] -HaikuBot[m]:#hazzy- builder manual to help
[17:17:32] -HaikuBot[m]:#hazzy- me make the routines
[17:18:15] <Lcvette[m]> i tried doing a single graphic but it was a mess so i settled on individual graphics and then thought hey this might be beneficial if they can be used for reference on the probe screens also
[17:18:49] <hazzy-lab> Perfect!
[17:19:26] <Lcvette[m]> and here is what im going to do ive decided
[17:20:46] <Lcvette[m]> instead of me trying to do this by myself, I am going to finish the helper graphics, then do the probe graphics in 2D/3D to help me visualise what is going to be happening, then put it all together in a doc
[17:21:25] <Lcvette[m]> then post it up and see if we can get some more takers to help on it
[17:21:33] <Lcvette[m]> think it will help go faster
[17:22:33] <hazzy-lab> That is a very good idea, and it will be much easier to explain what you are trying to do
[17:22:48] <hazzy-lab> when we ask for help :D
[17:23:03] <Lcvette[m]> otherwise i fear it may take a year for me to get it done working when i can on it
[17:23:13] <Lcvette[m]> yup thats what i was thinking too
[17:23:24] <Lcvette[m]> a good solid visual road map
[17:23:45] <Lcvette[m]> with a solid foundation and start done
[17:23:52] <Lcvette[m]> i think that will entice people
[17:24:09] <Lcvette[m]> to join the fray
[18:19:18] * Lcvette[m] uploaded an image: max_z_distance.png (217KB) < https://matrix.org >
[18:20:17] <hazzy-lab> looks great
[18:21:13] <Lcvette[m]> does it make sense to you?
[18:21:37] <Lcvette[m]> trying to keep it from turning into a full manual
[18:21:51] <Lcvette[m]> but not so short its nonsensical
[18:21:55] <Lcvette[m]> lol
[18:23:10] <hazzy-lab> I think that is a good compromise, a newbie should be able to understand it, but not too terse or long winded
[18:23:50] <Lcvette[m]> ok good
[18:43:22] * Lcvette[m] uploaded an image: max_x_y_distance.png (133KB) < https://matrix.org >
[18:50:46] * Lcvette[m] uploaded an image: max_x_y_distance.png (112KB) < https://matrix.org >
[19:51:03] * Lcvette[m] uploaded an image: x_y_clearance.png (135KB) < https://matrix.org >
[20:00:13] * Lcvette[m] uploaded an image: x_y_clearance.png (173KB) < https://matrix.org >
[20:04:45] * Lcvette[m] posted a file: Probing Reference Documentation.docx (561KB) < https://matrix.org >
[20:04:57] <Lcvette[m]> wife time for a few hours now
[20:05:45] <Lcvette[m]> will finish up the probe diagrams later tonight hopefully and cross those off the list then switch gears and start the probe button graphics tomorrow
[20:06:00] <Lcvette[m]> i'll need your feedback
[20:06:06] <Lcvette[m]> see what you guys like
[20:06:15] <hazzy1[m]> Looking great!
[20:06:15] <Lcvette[m]> thinking simple though
[21:26:38] <lcvette[m]2> Did you find any resolution to your quandary
[21:31:13] <hazzy-lab> No, but I don't think it will be a hold up for now, but it would be nice to be able to get return values from the subroutins
[21:32:07] <lcvette[m]2> Is there anyone you want me to ask?
[21:33:28] <hazzy-lab> I asked on the dev list and JT tried to help, but did not know enough about the interpretor
[21:33:46] <lcvette[m]2> Gotcha
[21:34:05] <lcvette[m]2> Chris Morley? Is he a portion guy?
[21:34:11] <lcvette[m]2> Python
[21:34:30] <hazzy-lab> I see a lot of forum posts asking how to do it, so I am pretty sure it is not possible at the moment, but it would be very valuable feature, so I may try to add it
[21:35:04] <lcvette[m]2> Ah... It's undiscovered territory
[21:35:12] <lcvette[m]2> You're so boss
[21:35:13] <lcvette[m]2> Lol
[21:35:14] <hazzy-lab> He may now, I need to reply to an email he sent, I will ask!
[21:35:23] <hazzy-lab> haha
[21:35:41] -HaikuBot[m]:#hazzy- He may now, I need
[21:35:42] -HaikuBot[m]:#hazzy- to reply to an email
[21:35:42] -HaikuBot[m]:#hazzy- he sent, I will ask!
[21:35:44] <hazzy-lab> LOL
[21:36:18] <lcvette[m]2> Lol
[21:36:30] <hazzy-lab> The probe GUI is coming alone well, I think we may not need to use a HAL component!
[21:36:59] <lcvette[m]2> Yeah?
[21:37:38] <hazzy-lab> I made it so it will work on 2.7 so you can try it without having to update
[21:37:46] <hazzy-lab> to 2.8
[21:37:50] <lcvette[m]2> Do it more like tormach did it?
[21:38:19] <lcvette[m]2> Nice
[21:38:46] <hazzy-lab> yes, I think it is simpler, which is usualy better
[21:39:22] <lcvette[m]2> So withoutthehal component, how does it work?
[21:39:29] <hazzy-lab> LOL, I crashed my spell checker again, they can't handle my volume of misspellings xD
[21:39:34] <lcvette[m]2> Without the Hal*
[21:40:14] <lcvette[m]2> Lol
[21:40:25] <hazzy-lab> At the top of each sub file you but a special comment like this:
[21:40:25] <hazzy-lab> (#ARGS [{x_hint}] [{y_hint}] [{diameter_hint}])
[21:41:18] <hazzy-lab> The name in the curly brackets corrisponds to the name of one of the input boxes
[21:41:40] <lcvette[m]2> Ok
[21:41:40] <hazzy-lab> When the sub is called it passes the values from those input boxes to the sub
[21:42:14] <lcvette[m]2> Ah ok
[21:42:41] <hazzy-lab> The advantage is that the subs can be used stand alone, even without the probe screen, so hopefully it will encourage people to develope new rutines
[21:43:01] <lcvette[m]2> Yes I like that
[21:43:24] <hazzy-lab> I am working on a way to specify default values values
[21:44:16] <lcvette[m]2> Specify?
[21:44:38] <lcvette[m]2> Such as? If empty=default
[21:44:58] <hazzy-lab> exactly
[21:45:24] <lcvette[m]2> Or if 0= skip
[21:45:29] <hazzy-lab> so it can be like the renishaw screen, which has optional args
[21:45:38] <lcvette[m]2> Ignore etc
[21:45:45] -HaikuBot[m]:#hazzy- so it can be like
[21:45:46] -HaikuBot[m]:#hazzy- the renishaw screen, which has
[21:45:47] -HaikuBot[m]:#hazzy- optional args
[21:45:48] <hazzy-lab> yes, that too
[21:45:49] <lcvette[m]2> Lol
[21:45:53] <hazzy-lab> xD
[21:45:56] <lcvette[m]2> Nice
[21:47:23] <lcvette[m]2> So with this method, what would a typical line using a box pull look like?
[21:48:09] <hazzy-lab> here is a messy sub example: http://dpaste.com
[21:48:15] <hazzy-lab> I have to run, bbl
[21:48:19] <lcvette[m]2> O
[22:11:25] <lcvette[m]2> That looks way easier to understand and use
[22:11:27] <lcvette[m]2> Thank you!!
[22:31:09] <hazzy-lab> I hope it is!
[23:01:46] <lcvette[m]2> Sure looks that way, basically put everything right at the top of the subroutine you'll need to plug in
[23:02:53] <lcvette[m]2> Will also need to pull in the probe tool DIAM measurement from the tool table
[23:04:07] <lcvette[m]2> And the z length
[23:04:10] <hazzy-lab> That might be able to be done in the sub itself ...
[23:04:18] <lcvette[m]2> Nice
[23:06:32] <hazzy-lab> yes, tool diameter it variable #5410, perfect!
[23:06:40] <lcvette[m]2> Tool diameter sets the probe depth below stock surface
[23:07:06] <lcvette[m]2> Extra depth adds to that parameter
[23:08:04] <hazzy-lab> I am having trouble visualizing that
[23:09:58] <lcvette[m]2> .125" ball diamond probe tip = probe finds top of stock doing z probe, the steps off and goes below stock zero point -0.125" to begin probing in x and y direction
[23:10:08] <lcvette[m]2> Diameter*
[23:10:18] <lcvette[m]2> Substitute for diamond
[23:10:39] <hazzy-lab> oh, now I see! Thank you!
[23:10:52] <lcvette[m]2> 😋
[23:11:27] <lcvette[m]2> Extra probe depth is added to the probe tip diameter value
[23:11:28] <hazzy-lab> So the extra depth it how much farther below the probed surface the center of the ball goes to probe the sides!
[23:11:33] <hazzy-lab> got it!
[23:12:23] <hazzy-lab> Would it be the probe tip radius, or diameter?
[23:12:33] <lcvette[m]2> Radius
[23:12:34] * hazzy-lab is too tired to think very well lol
[23:12:35] <lcvette[m]2> Sorry
[23:12:48] <hazzy-lab> ok
[23:13:03] <lcvette[m]2> But extra is full value
[23:13:43] <lcvette[m]2> Wait
[23:13:55] <lcvette[m]2> In Z it's not radius
[23:14:11] <hazzy-lab> hmm
[23:14:20] <lcvette[m]2> It's bottom of the probe
[23:14:27] <lcvette[m]2> Same as an endmill
[23:14:58] <hazzy-lab> buts its bottom of probe to center of ball, which would be radios, right?
[23:15:12] <lcvette[m]2> No
[23:15:27] <hazzy-lab> ok
[23:15:29] <lcvette[m]2> That's side to side for spindle centerline
[23:15:43] <lcvette[m]2> Depth is absolute
[23:15:50] <lcvette[m]2> Bottom is bottom
[23:16:19] <hazzy-lab> ok
[23:16:26] * hazzy-lab makes a sketch
[23:16:30] <lcvette[m]2> Gets yricky
[23:16:37] <hazzy-lab> yes indeed!
[23:17:50] <lcvette[m]2> Think of it as an endmill and you won't go wrong
[23:20:18] <hazzy-lab> I guess i was thinking that for the equator of the ball to touch the edge of the part the probe would have to go down the radius of the ball, and then extra depth is additional to that
[23:21:36] <lcvette[m]2> That's why we pull the diameter
[23:21:38] <lcvette[m]2> And use it
[23:21:41] <lcvette[m]2> And lower a full diameter
[23:22:15] -!- Roguish has quit [Quit: ChatZilla 0.9.92-rdmsoft [XULRunner 35.0.1/20150122214805]]
[23:22:16] <lcvette[m]2> It would be a full ball deep for default probe depth
[23:22:40] <lcvette[m]2> Extra would be full ball + extra
[23:22:56] <lcvette[m]2> Designed for changers and what not
[23:23:02] <lcvette[m]2> Chamfers*
[23:24:15] <lcvette[m]2> I had it right initially when I said diameter
[23:24:31] <lcvette[m]2> And got confused when you asked about radius
[23:24:36] <hazzy-lab> Ok that makes perfect sense, default to touching one radius below the surface to aviod burs and chamfers
[23:24:40] <lcvette[m]2> Correct answer is diameter
[23:25:02] <hazzy-lab> I am very good at confuzing people (especialy myself :D)
[23:25:09] <lcvette[m]2> Lol
[23:25:40] <lcvette[m]2> I was confused because I was using a center line earlier to locate the probe graphic
[23:25:51] <lcvette[m]2> And had that in my mind
[23:25:59] <hazzy-lab> haha
[23:26:38] <lcvette[m]2> But the centerline was set at .0625" below stock surface for a .125" ball
[23:28:52] <lcvette[m]2> Question
[23:29:14] <lcvette[m]2> G0 Z[#<latch_distance>]
[23:29:15] <lcvette[m]2> F[#<probe_slow_fr>]
[23:29:16] <lcvette[m]2> G38.3 Z-[#<latch_distance> * 2]
[23:29:37] <lcvette[m]2> What's the *2?
[23:33:06] <lcvette[m]2> I see you have latch distance set at .1000, so I read that line as:
[23:33:06] <lcvette[m]2> G38.3 Z-0.200
[23:33:10] -HaikuBot[m]:#hazzy- I see you have latch
[23:33:11] -HaikuBot[m]:#hazzy- distance set at .1000, so I read
[23:33:12] -HaikuBot[m]:#hazzy- that line as: G38.3 Z-0.200
[23:33:14] <lcvette[m]2> Lol
[23:33:29] <hazzy-lab> Ah, after the first probe I go up "latch_distance", so if it only went down "latch_distance" the end of the probe move would be right at the surface of the part
[23:33:46] <lcvette[m]2> Ok
[23:33:51] <hazzy-lab> so I had it go down an additional latch_distance so it would not run out of room
[23:34:10] <lcvette[m]2> So it's over travel command to ensure contact
[23:34:12] <hazzy-lab> I don't know what is standard practice
[23:34:14] <hazzy-lab> yes
[23:34:22] <lcvette[m]2> Gotcha
[23:34:29] <hazzy-lab> I guess it could just as well be a fixed number
[23:34:33] <lcvette[m]2> Just wanted to follow your logic
[23:35:28] <hazzy-lab> That might be hard, since most of the time I can't follow it lol
[23:36:11] <lcvette[m]2> Is latch_distance a part of the probe routine itself
[23:36:43] <hazzy-lab> well, just there, saw you called it something else in your drawings
[23:36:56] <hazzy-lab> I assume it should have an entry box
[23:37:04] <lcvette[m]2> Right, that's why I was asking
[23:37:14] <lcvette[m]2> Just trying to see if I was reinventing the wheel
[23:37:36] <lcvette[m]2> We can call it whatever
[23:39:34] <hazzy-lab> What did you call it? I can't find the picture
[23:39:52] <lcvette[m]2> Clearance
[23:40:01] <hazzy-lab> Ah, thats right!
[23:40:17] <lcvette[m]2> X/Y Clearance and Z Clearance
[23:41:14] <lcvette[m]2> That's an odd name
[23:41:19] <hazzy-lab> That is also the distance it backs off before the probe moves up
[23:41:26] -HaikuBot[m]:#hazzy- That is also the
[23:41:27] -HaikuBot[m]:#hazzy- distance it backs off before
[23:41:28] -HaikuBot[m]:#hazzy- the probe moves up
[23:41:31] <hazzy-lab> LOL
[23:41:52] <hazzy-lab> No, clearance is a good name!
[23:41:56] <lcvette[m]2> I always thought it would be better named Backstep
[23:42:51] <hazzy-lab> That is more descriptive
[23:43:53] <lcvette[m]2> Although it also represents the probe clearance travel plane while traversing the top or sides of the stock in between probing moves
[23:44:22] <lcvette[m]2> Maybe clearance back-step
[23:44:30] <lcvette[m]2> Lol
[23:44:58] <hazzy-lab> how about "clearance back-step latch distance"?
[23:44:59] <lcvette[m]2> Long name
[23:45:00] <hazzy-lab> lol
[23:45:05] <lcvette[m]2> Lol
[23:45:57] <lcvette[m]2> Ok leave it as is
[23:46:02] <lcvette[m]2> Lol
[23:46:09] <hazzy-lab> We could make it a German word: clearancebacksteplatchdistance
[23:46:25] <hazzy-lab> more technical that way :D
[23:47:03] <lcvette[m]2> I think we should finish it and then let icks type it all up
[23:47:21] <hazzy-lab> AHAHAHAHAHAHA
[23:47:39] <lcvette[m]2> He has awesome germlish spelling
[23:47:39] <lcvette[m]2> Hahahaha
[23:49:19] <hazzy-lab> clearance is what MSM uses, so that is probably the right term
[23:49:33] <lcvette[m]2> Yeah
[23:49:37] <hazzy-lab> LOL, that means I already have input boxes for it! lol
[23:49:53] <hazzy-lab> I should maybe look at what I make
[23:49:58] <lcvette[m]2> Hahaha
[23:50:23] <lcvette[m]2> You do
[23:50:27] <lcvette[m]2> 😁
[23:53:08] <lcvette[m]2> The way tormach has the work coordinate offset settings setup, do you understand what they are doing?
[23:53:59] <hazzy-lab> I have not payed any attention to it, are you looking in the subs?
[23:54:31] <lcvette[m]2> Is it rolling? Ie, whatever offset your in it sets the probed position to the next available work offset?
[23:54:50] <lcvette[m]2> I can, want me to paste
[23:55:06] <hazzy-lab> sure! Thank you
[23:55:31] <hazzy-lab> That sounds interesting
[23:55:47] * lcvette[m]2 sent a long message: < https://matrix.org >
[23:58:24] * lcvette[m]2 sent a long message: < https://matrix.org >
[23:58:33] <lcvette[m]2> That's weird
[23:58:49] <lcvette[m]2> Added a bunch of stuff