#hazzy | Logs for 2018-07-16
Back
[00:00:52] <Lcvette[m]> hazzy, float type for the hal pin used?
[00:01:23] <hazzy-lab> Yes
[00:01:48] <hazzy-lab> You are learning, fast!
[00:02:27] <Lcvette[m]> im only learning down a specific path
[00:02:34] <Lcvette[m]> so the requirement is specific
[00:02:36] <Lcvette[m]> lol
[00:30:48] <Lcvette[m]> am i understanding correctly that in order to create pins they need to be compiled and written into the crc files?
[00:30:55] <Lcvette[m]> src
[00:32:03] <Lcvette[m]> or wait, did i read straight through pins and into components
[00:37:44] <hazzy-lab> Yes, HAL pins can only be created by a HAL component (which can be written in C or Python)
[00:38:13] <hazzy-lab> The connections between HAL pins is defined by the hal file
[00:38:31] <hazzy-lab> Which is part of each machine config
[00:39:59] <hazzy-lab> But HAL components don't have to be part of the src code, they can be written and compiled outside of the main build using a tool called halcompile
[00:40:15] <lcvette[m]2> ok
[00:40:28] <lcvette[m]2> that's what I was reading
[00:40:28] <hazzy-lab> If a HAL comp it written in Python it does not have to be compiled at all
[00:40:46] <lcvette[m]2> interesting
[00:41:02] <lcvette[m]2> it just needs a path to the source directory
[00:41:12] <hazzy-lab> correct
[00:42:12] <hazzy-lab> it seems complicated, but it is much simpler than it sounds!
[00:42:35] <lcvette[m]2> ok, so now I better u dwrstand where the names of things come from
[00:42:40] <lcvette[m]2> I am starting to understand the eb and flow
[00:42:56] <lcvette[m]2> the detailed technical syntax
[00:43:09] <lcvette[m]2> that is not going to come easy
[00:43:35] <hazzy-lab> excellent!
[00:44:48] <lcvette[m]2> I have a feeling it's like math, and without actual understanding of the symbology and how it functions I deretnading how, why and where it's used will be difficult
[00:45:05] <lcvette[m]2> understanding*
[00:46:58] <hazzy-lab> Yes, it is very much like that, even to the point that you can use it even if you could not explain the underlying concepts perfectaly or be able to "derive" it
[00:47:32] -!- hazzy-lab has quit [Quit: hazzy-lab]
[00:48:12] -!- aircooled has joined #hazzy
[00:48:17] <lcvette[m]2> I'm referring to the syntax
[00:48:34] <lcvette[m]2> writing new stuff from scratch
[00:48:50] <lcvette[m]2> I fear it is going g to be problematic
[00:49:48] <lcvette[m]2> all the [ ]<_ >( )._
[00:50:02] <lcvette[m]2> #
[00:51:04] <lcvette[m]2> I just read the online docs and it did a poor job explaining the syntax
[00:55:18] <aircooled> that can be confusion at first, but once you understand what it is for it makes sense
[00:55:31] aircooled is now known as hazzy-lab
[00:56:04] <hazzy-lab> Sorry, that was me
[00:56:26] <lcvette[m]2> lol
[00:56:53] <lcvette[m]2> I figured, I was excited to get to the part where it explained that
[00:57:03] <lcvette[m]2> it never came
[00:57:41] <lcvette[m]2> or if it explained it, it did so poorly enough as to make it impossible to know that's what it was attempting
[00:57:54] <hazzy-lab> think of it like punctuation, or mathematical operators
[00:58:07] <lcvette[m]2> I assumed
[00:58:48] <hazzy-lab> If you give me an example of some syntax I will try to explain it
[00:59:59] <lcvette[m]2> G38.2 Z F#<_hal[probe.probe-velocity]>
[01:00:00] <lcvette[m]2> let's use your example from yesterday
[01:00:16] <lcvette[m]2> I understand up to the #
[01:00:26] <hazzy-lab> Perfect!
[01:01:45] <hazzy-lab> Ok, the "#<" indicates the beginning of a named parameters name, and the closing ">" indicates where the name ends
[01:02:32] <lcvette[m]2> ok
[01:02:49] <hazzy-lab> "_hal" just specifies were the value should be taken from, there is also "_ini" for reading INI parameters
[01:03:44] <lcvette[m]2> ok..making sense
[01:04:37] <hazzy-lab> The square brackets [] are basically equivalent to () in a mathematical expression, they are used to group operations and and to pass values to a function
[01:05:54] <hazzy-lab> so when we say "_hal[probe.probe-velocity]", the brackets after the _hal enclose the name of the HAL pin we are interested in
[01:06:13] <lcvette[m]2> ok
[01:06:55] <hazzy-lab> if we did not use the brackets, then it would make it impossible to have anything after the pin name, because _hal would not no where the information it was being passed stopped
[01:08:09] <lcvette[m]2> and probe.probe-velocity is a pin we will compile for a box using python
[01:08:12] <lcvette[m]2> ?
[01:08:25] <lcvette[m]2> or some other method in the gui
[01:08:32] <hazzy-lab> The dot between the "probe" and "probe-velocity" specifies that we are interested in the "probe" component, and specifically in the value of the it's pin named "probe-velocity"
[01:08:47] <hazzy-lab> Yes, that is correct
[01:08:56] <lcvette[m]2> ok
[01:09:08] <lcvette[m]2> so probe will have sub pins
[01:09:14] <hazzy-lab> yes
[01:09:53] <hazzy-lab> or, to be precise, the probe component will have pins :)
[01:10:05] <lcvette[m]2> probe-velocity, probe-extra_z_depth
[01:10:15] <lcvette[m]2> etc
[01:10:18] <hazzy-lab> exactly
[01:10:25] <lcvette[m]2> aha
[01:10:35] <hazzy-lab> starting to make sense?
[01:10:43] <lcvette[m]2> I saw that type listing in the halshow
[01:10:50] <lcvette[m]2> yes!
[01:10:50] <hazzy-lab> yes!
[01:11:01] <lcvette[m]2> like a folder
[01:11:16] <lcvette[m]2> kinda
[01:11:19] <hazzy-lab> yes, that is a good analogy
[01:11:56] <lcvette[m]2> but with - instead of /
[01:12:03] <lcvette[m]2> ok I'm getting it
[01:12:03] <hazzy-lab> the dot defines the hierarchy, just like a / does in path names
[01:12:23] <lcvette[m]2> gotcha
[01:12:24] <hazzy-lab> You are!
[01:12:40] <hazzy-lab> you are getting it faster than I can type :D
[01:12:51] <lcvette[m]2> lol
[01:13:13] <lcvette[m]2> I think I'm good for now.. gonna let that marinate for the night
[01:13:13] <hazzy-lab> (which is not saying much, lol)
[01:13:44] <hazzy-lab> sounds good, best to not get saturated
[01:13:54] <lcvette[m]2> I don't know how hard it is to compile the actual pins
[01:14:05] <hazzy-lab> easy peasy
[01:14:12] <lcvette[m]2> bit I can see now writing the code with Hal would be pretty simple
[01:14:44] <hazzy-lab> it is, it is kinda like legos for engineers :D
[01:14:59] <lcvette[m]2> so, was just thinking
[01:15:01] <hazzy-lab> You can start small and slowly build up what you need
[01:15:38] <lcvette[m]2> probe-probe_extra_z_depth
[01:15:44] -HaikuBot[m]:#hazzy- bit I can see now
[01:15:45] -HaikuBot[m]:#hazzy- writing the code with Hal would
[01:15:46] -HaikuBot[m]:#hazzy- be pretty simple
[01:15:49] <lcvette[m]2> lol
[01:15:51] <hazzy-lab> LOL
[01:16:01] <hazzy-lab> slow bot xD
[01:16:22] <lcvette[m]2> to use that box
[01:16:27] <lcvette[m]2> if you think back MSM
[01:16:55] <hazzy-lab> yes, that is right
[01:17:08] <hazzy-lab> actually: probe.probe_extra_z_depth
[01:17:08] <lcvette[m]2> it is going to require some equations, those would be written in the subroutine ngc file correct
[01:17:20] <lcvette[m]2> yes, sorry
[01:17:22] <hazzy-lab> yes
[01:17:56] <hazzy-lab> you can even do trig in the ngc files
[01:18:26] <hazzy-lab> #<x_distance> = SIN[45]
[01:18:30] <hazzy-lab> type of thing=
[01:18:38] <lcvette[m]2> nice!
[01:18:49] <hazzy-lab> its awesome!
[01:18:55] <lcvette[m]2> I can see this being fun
[01:19:12] <hazzy-lab> I think you will get into it
[01:19:30] <hazzy-lab> But, I warn you, it can be addictive
[01:19:36] <lcvette[m]2> I will try and write a little something tomorrow
[01:20:00] <hazzy-lab> great
[01:20:08] <lcvette[m]2> and send it to your for inspection
[01:20:23] <lcvette[m]2> i'm sure I'm going to have some additional questions
[01:20:49] <lcvette[m]2> but I'll try and sort what i can on my own
[01:20:50] <hazzy-lab> I am going to go to a friends shop and melt some metal and do some fab work, but I should be around in the morning in the evening
[01:21:09] <hazzy-lab> and in the*
[01:21:24] <hazzy-lab> that was a paradox they way I first wrote it :D
[01:21:28] <lcvette[m]2> and reserve your help for the ones that the docs fail yo get me through
[01:21:49] <lcvette[m]2> hahaha
[01:21:55] <lcvette[m]2> sounds awesome
[01:22:10] <lcvette[m]2> I have tons to toll on to around here
[01:22:13] <hazzy-lab> sounds good,. I think you will catch on quickly though
[01:22:39] <lcvette[m]2> I appreciate it!!
[01:23:01] <lcvette[m]2> ok, I'm hitting the sack with my victory!! thanks man!!
[01:23:16] <hazzy-lab> You are very welcome!
[01:23:23] <hazzy-lab> sleep tight!
[01:24:35] <lcvette[m]2> night!
[01:56:30] -!- hazzy-dev has quit [Remote host closed the connection]
[01:56:47] -!- hazzy-dev has joined #hazzy
[11:00:37] * hazzy1[m] uploaded an image: Screenshot_2018-07-16_11-00-03.png (100KB) < https://matrix.org >
[11:01:17] -!- Roguish_shop has quit [Ping timeout: 276 seconds]
[11:03:23] <hazzy-lab> ... man that is ugly
[11:03:40] <hazzy-lab> but it works :)
[11:09:54] <lcvette[m]2> look at you go!!
[11:10:36] <lcvette[m]2> is that the camera
[11:11:10] <hazzy-lab> lol
[11:11:12] <hazzy-lab> yes
[11:31:36] <lcvette[m]2> outstanding
[11:31:47] <lcvette[m]2> sorry, my tool holder order arrived
[11:32:09] <lcvette[m]2> was unpacking and inspecting
[11:32:10] <hazzy-lab> oh ho!!
[11:32:18] * hazzy-lab is jealous
[11:32:36] <hazzy-lab> feel like Christmas?
[11:32:52] <hazzy-lab> What type of holders?
[11:33:16] * lcvette[m]2 uploaded an image: VectorImage_2018-07-16_113233.jpg (161KB) < https://matrix.org >
[11:33:24] <lcvette[m]2> feels like; have the rest of what I needed
[11:33:27] <lcvette[m]2> BT30
[11:33:40] <lcvette[m]2> er20/16/11
[11:33:48] <hazzy-lab> I like the extended ones!
[11:34:29] <lcvette[m]2> these are 100mm
[11:35:14] <lcvette[m]2> I didn't get any of these in the first order and discovered that was a mistake for smaller endmills and drills
[11:36:04] <lcvette[m]2> I bought a tool height setter too, and I'm looking at it and discovering it's a complete piece of shit
[11:36:30] <lcvette[m]2> it's useless without a second hand dial
[11:36:55] -RSSBot[turbosssp:#hazzy- Hazzy activity posted a new article: Kurt Jacobson pushed to project branch CameraWidget at Hazzy / QtPyVCP ( https://gitlab.com )
[11:37:18] <hazzy-lab> I guess it is supposed to only ever make on rev? Seems odd to not have the second hand
[11:38:45] <lcvette[m]2> yeah, maybe, bit if that's the case it's way off on calibration and the two screws don't do anything bit hold the bezel in place
[11:39:07] <lcvette[m]2> typical low quality chinese
[11:39:19] <lcvette[m]2> oh well
[11:39:21] <lcvette[m]2> shiny paperweight
[11:39:21] <hazzy-lab> yeah, that is not good
[11:39:40] <hazzy-lab> lol, at leastit looks fawncy enough
[11:40:14] <lcvette[m]2> lol
[11:40:22] <lcvette[m]2> it goes 1.5 turns
[12:23:51] * hazzy1[m] uploaded an image: brender_tabs.png (88KB) < https://matrix.org >
[12:24:05] <hazzy1[m]> ugly brender tabs
[12:32:20] -RSSBot[turbosssp:#hazzy- Hazzy activity posted a new article: Kurt Jacobson pushed to project branch master at Hazzy / QtPyVCP ( https://gitlab.com )
[12:35:27] <lcvette[m]2> that's awesome man
[12:36:16] <lcvette[m]2> pathpilot clone
[12:36:18] <lcvette[m]2> ?
[12:36:31] <lcvette[m]2> in the shop at the moment still
[12:55:17] -!- hazzy-dev has quit [Quit: hazzy-dev]
[13:46:39] -!- Roguish has joined #hazzy
[16:45:06] * lcvette[m]2 uploaded an image: VectorImage_2018-07-16_044435.jpg (457KB) < https://matrix.org >
[16:48:01] * lcvette[m]2 uploaded an image: VectorImage_2018-07-16_044725.jpg (457KB) < https://matrix.org >
[16:56:16] * lcvette[m]2 uploaded a video: VID_20180716_165024203.mp4 (63997KB) < https://matrix.org >
[17:05:43] <lcvette[m]2> Busy tool day, not much else accomplished unfortunaely, the tool height setter was a wasted time suck I was not expecting (although I suppose I should have counted on it)
[17:07:59] <lcvette[m]2> Ended up taking it apart, the DTI was hacked, they just cut the shaft off a normal DTI pointed it up and let the underside of the tool touch platter push it down. There was zero adjustment for it. Pretty lame
[17:09:22] <lcvette[m]2> The shaft off the DTI was threaded, so i filled it down further, added a screw that I then carefully filed to height giving just under one revolution
[17:11:11] <lcvette[m]2> Went through 3 screws trying to get it in the vertical position before giving up where you see it in the video. Trying to get a few thou by hand filing is tedious when each attempt requires a full break down of everything to remove the DTI
[18:14:42] <Lcvette[m]> ANybody here?
[18:39:21] <hazzy1[m]> Nope 😂
[18:39:42] <Lcvette[m]> so lonely
[18:40:04] * hazzy1[m] uploaded an image: VectorImage_2018-07-16_063952.jpg (190KB) < https://matrix.org >
[18:40:29] <hazzy1[m]> Melting wheel weights ...
[18:40:31] <Lcvette[m]> manly stuff right there
[18:52:09] <Lcvette[m]> so I started looking over the probe routines for linuxcnc
[18:52:56] <Lcvette[m]> from what i can see there are 5 probing .ngc file
[18:54:02] <Lcvette[m]> xplus, xminus, yminus, yplus, down
[18:55:12] <Lcvette[m]> so now i am curious how he was using these subroutines to generate broader probing routines
[21:27:31] <hazzy-lab> hey Lcvette[m]
[21:27:44] <hazzy-lab> Were did you fine the probe .ngc files?
[21:28:14] <lcvette[m]2> In the macros folder
[21:28:21] <hazzy-lab> Ah, thanks
[21:28:24] <hazzy-lab> checking
[21:28:59] <lcvette[m]2> They are naked as listed above
[21:29:01] <lcvette[m]2> Named
[21:29:07] <hazzy-lab> lol
[21:29:14] <lcvette[m]2> xplus, xminus, yminus, yplus, down
[21:29:19] <lcvette[m]2> Lol
[21:30:44] <hazzy-lab> I don't see those anywhere, could they have been included with the config you used?
[21:31:44] <lcvette[m]2> Yeah, they were copied in from the probing
[21:31:49] <lcvette[m]2> Se
[21:31:50] <lcvette[m]2> Sek
[21:31:55] <hazzy-lab> ok
[21:32:54] <hazzy-lab> All the probing is done using one of the G38 flavors: http://linuxcnc.org
[21:32:56] * lcvette[m]2 posted a file: VMC2 old working.zip (256KB) < https://matrix.org >
[21:33:03] <lcvette[m]2> There in there
[21:33:19] * lcvette[m]2 sent a long message: < https://matrix.org >
[21:33:24] <hazzy-lab> The sub is what does the calculates etc
[21:33:31] <hazzy-lab> Thanks!
[21:33:41] <lcvette[m]2> That's the code for the down.ngc
[21:34:39] <hazzy-lab> aha, that are useing HAL
[21:34:56] <hazzy-lab> sorry, gtg, back in a bit
[21:35:08] <lcvette[m]2> It seems there are the individual probe moves for all directions
[21:35:15] <lcvette[m]2> But no compound moves
[21:35:21] <lcvette[m]2> Combined
[21:35:24] <lcvette[m]2> K
[22:20:13] <TurBoss> Hello!
[22:20:25] <TurBoss> hurray some progress
[22:21:20] <TurBoss> > <@kcjengr:matrix.org> sent an image.
[22:21:21] <TurBoss> Thank You!!
[22:29:21] <TurBoss> you guys working on probe screen
[22:30:26] <lcvette[m]2> Yo
[22:30:36] <lcvette[m]2> Yes, working on probing
[22:35:39] <TurBoss> great
[22:36:22] <lcvette[m]2> Yeah, hopefully
[23:07:09] -RSSBot[turbosssp:#hazzy- Hazzy activity posted a new article: TurBoss pushed to project branch CameraWidget at Hazzy / QtPyVCP ( https://gitlab.com )
[23:07:10] -RSSBot[turbosssp:#hazzy- Hazzy activity posted a new article: TurBoss pushed to project branch CameraWidget at Hazzy / QtPyVCP ( https://gitlab.com )
[23:08:25] * hazzy-lab is back
[23:08:59] <hazzy-lab> TurBoss: You got the _rc files to compile? Hurray!
[23:09:13] <TurBoss> yes
[23:09:14] <TurBoss> :D
[23:09:27] <TurBoss> I removed pyqt5 by hand and reinstalled from apt
[23:10:19] <TurBoss> now I can back to work on Camera thing
[23:10:56] <TurBoss> how did you make it work?
[23:12:10] -RSSBot[turbosssp:#hazzy- Hazzy activity posted a new article: TurBoss pushed to project branch CameraWidget at Hazzy / QtPyVCP ( https://gitlab.com )
[23:13:13] <TurBoss> I had an Idea
[23:13:19] <TurBoss> xD
[23:13:49] <hazzy-lab> excellent!
[23:13:50] <hazzy-lab> All I did was make it a QWidget instead of a QMainWindow
[23:13:57] <TurBoss> "make" could also copy the sim directory to the linuxcnc/config dir
[23:14:16] <TurBoss> and replace the Display var
[23:14:20] <TurBoss> what do you think?
[23:14:35] <hazzy-lab> Oh, that is a great idea!
[23:14:55] <hazzy-lab> And add the the main.py to bin!
[23:15:10] <hazzy-lab> Maybe it should have an install for that? make install
[23:15:27] <hazzy-lab> make install-sim
[23:15:33] <TurBoss> so no need to change the DISPLAY var
[23:15:33] <TurBoss> great
[23:15:34] <TurBoss> bin
[23:15:43] <hazzy-lab> I like it!
[23:15:48] <TurBoss> debian or ubunt has a ~/bin
[23:15:52] <TurBoss> not sure
[23:16:05] <hazzy-lab> i think to, then no need for sudo
[23:16:21] <TurBoss> or .local
[23:16:24] <TurBoss> let me check
[23:16:46] <hazzy-lab> .local/bin
[23:16:58] <TurBoss> yes!
[23:17:04] <TurBoss> checking if works
[23:17:08] <hazzy-lab> sweet!
[23:17:50] * hazzy-lab is reading about makefiles
[23:18:23] <hazzy-lab> Hey, it could also install the libpyqt.so file!
[23:18:38] <TurBoss> .local/bin has to be added to PATH :(
[23:18:59] <TurBoss> I don't needed
[23:19:14] <hazzy-lab> hmm
[23:19:16] <TurBoss> I didn't use it
[23:19:29] <TurBoss> and everything seems to work...
[23:19:33] <TurBoss> 😛
[23:19:40] <hazzy-lab> That is fantastic!
[23:19:44] <lcvette[m]2> You guys are smart
[23:20:18] <TurBoss> nah
[23:20:23] <hazzy-lab> naw, we just fix it till is't broke, and then some and it works
[23:20:46] <hazzy-lab> :D
[23:20:53] <lcvette[m]2> Lol
[23:21:38] <TurBoss> kurt you know what?
[23:21:49] <TurBoss> I'm mantaining a ¢# code
[23:21:50] <TurBoss> 😛
[23:22:04] <hazzy-lab> No, really! lol
[23:22:10] <TurBoss> booooo
[23:22:27] <hazzy-lab> I did some c#, but don't like it
[23:22:33] <TurBoss> c# sucks
[23:22:34] <TurBoss> its a windows tool to hack Final fantasy 6
[23:22:35] <TurBoss> *7
[23:22:57] <hazzy-lab> Oh, I think you showed that to me
[23:23:32] <TurBoss> it wraps the binary and interceps the system calls and manipulate it
[23:23:55] <TurBoss> I don't know how it works I just fix bugs
[23:24:00] <TurBoss> :P
[23:28:18] <TurBoss> did you managed to work with the python daemon for the log thing?
[23:28:18] <TurBoss> logs
[23:45:32] <hazzy-lab> That is pretty neat, but it sounds complicated ..
[23:45:32] <hazzy-lab> Does the game ever change so it breaks the wrapper, or is it pretty stable?
[23:46:25] <hazzy-lab> No, never played with the python daemon, haven't even checked it the logs are still working, but I guess they are, lol
[23:54:33] <hazzy-lab> TurBoss: We could also make it a pip package, then it would be on the path ...
[23:55:05] <hazzy-lab> and could be installed with pip
[23:59:41] <hazzy-lab> Uh oh, new Brenda post ..