#hazzy | Logs for 2018-07-15

Back
[01:50:50] * lcvette[m]2 uploaded an image: IMG-20180715-0002.png (48KB) < https://matrix.org >
[01:53:55] <TurBoss> hey thats great!
[01:54:24] * lcvette[m]2 uploaded an image: IMG-20180715-0003.png (48KB) < https://matrix.org >
[01:54:28] <hazzy-lab> very nice!
[01:54:49] <lcvette[m]2> Trying to get the feel for everything still
[01:55:01] <lcvette[m]2> Slot of tricks on YouTube
[01:55:04] <lcvette[m]2> Alot
[01:55:23] <TurBoss> a wild alot apeared
[01:55:39] <hazzy-lab> lol
[01:56:10] <lcvette[m]2> Swype
[01:56:17] <lcvette[m]2> I'm working on my tablet
[01:56:23] * TurBoss uploaded an image: ALOT.png (672KB) < https://matrix.org >
[01:56:26] <TurBoss> :P
[01:56:29] <lcvette[m]2> Lol
[01:56:38] <hazzy-lab> haha
[01:56:41] <TurBoss> hihihihi
[02:21:31] * lcvette[m]2 uploaded an image: IMG-20180715-0004.png (17KB) < https://matrix.org >
[02:21:45] <lcvette[m]2> Is this an icon?
[09:29:30] -!- Roguish has joined #hazzy
[09:35:10] -!- Roguish_ has joined #hazzy
[09:36:20] -!- Roguish__ has joined #hazzy
[09:37:02] -!- Roguish has quit [Ping timeout: 276 seconds]
[09:37:06] Roguish__ is now known as Roguish
[09:39:10] -!- Roguish_ has quit [Read error: Connection reset by peer]
[09:43:54] -!- Roguish has quit [Remote host closed the connection]
[09:53:35] -!- Roguish has joined #hazzy
[11:57:37] -!- Roguish_shop has joined #hazzy
[11:58:14] <Roguish_shop> machining like a mad man today
[11:59:05] <hazzy-lab> Great! What kinda parts are you making?
[12:46:16] <lcvette[m]2> Nice
[12:47:06] <lcvette[m]2> Whatcha making?
[13:13:19] <Roguish_shop> https://imgur.com
[13:15:45] <hazzy-lab> Nice! Looks like a liner bearing/guide?
[13:24:51] <Roguish_shop> manifold for quench water for an induction hardener.
[13:25:15] <hazzy-lab> Sweet!
[13:28:01] <lcvette[m]2> Nice!
[13:30:30] <Roguish_shop> https://imgur.com
[13:31:01] <Roguish_shop> the linear track is the yellow in the center. it is driven through after the vee edges are heated.
[13:31:37] <Roguish_shop> water comes in the top and bottom big red holes, and sprays the track from all sides.
[13:34:29] <hazzy-lab> Very noice! Is the v-rail induction tempered too, after going thru the water quench?
[13:40:12] <Roguish_shop> no, just left hard, about 55 Rc
[13:40:21] <Roguish_shop> cleaned, polished.
[13:41:12] <Roguish_shop> https://www.modernlinear.com
[13:48:01] * lcvette[m]2 uploaded an image: IMG-20180715-0006.png (135KB) < https://matrix.org >
[13:48:28] <hazzy-lab> nice!
[13:49:15] <hazzy-lab> I think I like the top and left ones best
[13:49:49] <lcvette[m]2> That's awesome rougish!
[13:49:50] <lcvette[m]2> That's awesome rougish!
[13:50:22] <lcvette[m]2> Simple
[13:50:26] <lcvette[m]2> I like those too
[13:50:29] <hazzy-lab> I had never heard of modern linear, that have some nice stuff!
[13:51:09] <Roguish_shop> oh yeah. it's good quality stuff. i do all the engineering and design, and machine design
[13:51:38] <hazzy-lab> That is awesome!
[13:54:32] <hazzy-lab> Added to my list of suppliers :)
[14:19:35] <lcvette[m]2> Hazzy, do you have access to a pp2.0 screen set you can get screen shots from all the different screens?
[14:20:11] <lcvette[m]2> I can get the tool graphics laid out for it
[14:20:27] <hazzy-lab> No, but I could set it up, but it's a pain to do, lol
[14:20:34] <lcvette[m]2> And any of the other goodies you refer to
[14:20:43] <lcvette[m]2> Graphics*
[14:21:17] <lcvette[m]2> I downloaded inkscape
[14:21:35] <hazzy-lab> Great
[14:21:46] <lcvette[m]2> That way I can start banging any of that out in my spare time
[14:22:28] <lcvette[m]2> Stock piling the folder, you just tell me where to upload it to
[14:24:43] <lcvette[m]2> Ah, I wonder if we know anyone running pp2.0 who could take screen captures
[14:24:46] <lcvette[m]2> Dave your time
[14:24:53] <lcvette[m]2> Save*
[14:28:05] <hazzy-lab> I guess i should see what all the hype over PP2.0 is about, but its not very interesting to me, haha
[14:28:40] <hazzy-lab> I pushed the Sub Caller UI so you can start playing with it if you want: https://gitlab.com
[14:29:17] <lcvette[m]2> Ok
[14:29:48] <hazzy-lab> I included an sample subroutine, which might be a decent starting point for probing routines
[14:30:16] <lcvette[m]2> Perfect
[14:31:00] <lcvette[m]2> I like to break up my learning
[14:31:26] <lcvette[m]2> Or I'll get frustrated
[14:31:28] <lcvette[m]2> Lol
[14:31:37] <hazzy-lab> Yes!
[14:32:10] <lcvette[m]2> Hit a wall switch gears come back and I usually resolve it
[14:33:19] <lcvette[m]2> Besides, both take go towards Completion of the same overall goal
[14:33:25] <lcvette[m]2> Tasks
[14:33:27] -HaikuBot[m]:#hazzy- Besides, both take go
[14:33:28] -HaikuBot[m]:#hazzy- towards Completion of the
[14:33:29] -HaikuBot[m]:#hazzy- same overall goal
[14:33:41] <lcvette[m]2> So both motivate the other
[14:33:42] <hazzy-lab> LOL
[14:33:53] <lcvette[m]2> Lol
[14:33:54] <hazzy-lab> Yeah, that's right
[16:01:13] <lcvette[m]2> #<feed_ruff> = #1 (feed rate from UI main screen DRO)
[16:01:14] <lcvette[m]2> #<feed_fine> = [#<feed_ruff> / 20]
[16:01:17] <TurBoss> ello
[16:01:31] <lcvette[m]2> Hello
[16:01:54] <lcvette[m]2> So I have notepad++ on my tablet now
[16:02:04] <lcvette[m]2> I'm amazed what you can get on a tablet
[16:02:35] <lcvette[m]2> This is PP probe routine
[16:03:04] <lcvette[m]2> They are pulling from gui box current feedrate setting I'm guessing
[16:04:18] <lcvette[m]2> And then fine feed is 1/20th fun screen feed rate
[16:08:22] * hazzy1[m] uploaded an image: VectorImage_2018-07-15_033923.jpg (12032KB) < https://matrix.org >
[16:08:23] <hazzy1[m]> Cutting brick
[16:09:16] <hazzy1[m]> Yes, that looks like what they are doing
[16:10:27] <lcvette[m]2> Fun times... Keep it wet
[16:10:35] <lcvette[m]2> Don't breath the dust
[16:11:03] <hazzy1[m]> Another way to do it would be to make a probe Hal comp, and read values for pins
[16:12:48] <hazzy1[m]> Haha, I use the "hold your breath" dust mask, works about as well as the "look away" welding giggles 😂
[16:14:21] <lcvette[m]2> Soon as you use the word pins, it sounds scary
[16:14:41] <lcvette[m]2> I start visualizing my mesa cards
[16:14:53] <lcvette[m]2> And everything goes to pot
[16:20:50] <TurBoss> hazzy
[16:21:02] <TurBoss> I can launch teh designer
[16:21:08] <TurBoss> and loads the widgets
[16:21:13] <hazzy-lab> Hurray!
[16:21:22] <TurBoss> buuuut...
[16:21:27] <TurBoss> make doesn't work
[16:21:27] <TurBoss> :(
[16:21:42] <TurBoss> i make works widgets doesn't load
[16:21:49] <TurBoss> 😁
[16:21:56] <hazzy-lab> Comment out the line that imports the _rc.py file
[16:21:57] <hazzy-lab> xD
[16:22:07] <TurBoss> ok
[16:22:16] <hazzy-lab> easy solution!
[16:22:36] <hazzy-lab> The icons won't work, but there arn't any right now anyway
[16:22:56] -HaikuBot[m]:#hazzy- The icons won't
[16:22:56] -HaikuBot[m]:#hazzy- work, but there arn't any
[16:22:57] -HaikuBot[m]:#hazzy- right now anyway
[16:23:06] <hazzy-lab> Every time!
[16:23:08] <hazzy-lab> LOL
[16:23:14] <TurBoss> sorry , what _rc.py?
[16:23:40] <hazzy-lab> in main.py near the bottom there should be a import, let me check
[16:23:50] <TurBoss> ok checking
[16:24:08] <hazzy-lab> Comment out: recources = import_module(module_name + '_rc')
[16:24:08] <hazzy-lab>
[16:24:20] <hazzy-lab> line 95
[16:24:44] <hazzy-lab> How did I send an empty line??
[16:26:22] <TurBoss> http://dpaste.com
[16:26:28] <TurBoss> commented 95
[16:27:16] <hazzy-lab> Is that when you run make?
[16:27:24] <TurBoss> yes
[16:27:35] <TurBoss> python-sip is installed
[16:27:38] <hazzy-lab> With that line commented you don't need to make
[16:27:57] <hazzy-lab> It would start with out needing the _rc file
[16:28:01] <TurBoss> ah ok
[16:28:04] <hazzy-lab> should*
[16:29:00] <TurBoss> ok
[16:36:39] <hazzy-lab> lcvette: With a probe HAL comp we could do things like this in the subroutines:
[16:36:40] <hazzy-lab> G38.2 Z F#<_hal[probe.probe-velocity]>
[16:36:40] <hazzy-lab> and it would read the feed value from HAL pin
[16:37:19] <hazzy-lab> Might be worth looking into, I have never tried it before
[16:37:42] * hazzy-lab goes to cut the grass
[16:37:57] <lcvette[m]2> But what a halpin
[16:40:49] <hazzy-lab> Ah, they are things of beauty, they are like voodoo doll pins stuck into the RT linux kernel that give access to values used in the real time parts if LCNC
[16:41:16] <lcvette[m]2> That doesn't help me
[16:41:39] <hazzy-lab> sigh
[16:41:39] <hazzy-lab> :D
[16:41:49] <hazzy-lab> They are basicaly THE thing that makes linuxcnc so powerful and customizable
[16:42:16] <lcvette[m]2> Where is ahal pin?
[16:42:32] <lcvette[m]2> Ok
[16:42:56] <lcvette[m]2> Hmm, less Grand view, more specific location
[16:43:21] <lcvette[m]2> Where is a Hal pin found?
[16:43:44] <hazzy-lab> Think about it as a software equivalent to a physical pin on a circuit board
[16:45:12] <lcvette[m]2> Ok
[16:45:34] <lcvette[m]2> How does that help me?
[16:46:16] <lcvette[m]2> How do I interpreted a physical pin to be a numerical value of data
[16:46:24] <lcvette[m]2> That is used changeable on a screen
[16:47:08] <lcvette[m]2> This is where I can't make it click
[16:47:22] <lcvette[m]2> I comprehend a file that can save values I specified numeric positions
[16:47:27] <lcvette[m]2> That makes sense
[16:47:48] <lcvette[m]2> I understand a box with an address that can be called
[16:48:07] <hazzy-lab> Just like a physical pin has a voltage, a HAL pin has a value, and that value can be set from with in the GUI, like a potentiometer can set the value of a physical pin
[16:48:45] <hazzy-lab> (you can also connect a physical potentiometer to a HAL pin thru IO)
[16:50:53] <lcvette[m]2> Ok
[16:51:43] <hazzy-lab> In Gmoccapy if you go to the settings page, in the lower right corner there is a button called "halshow". That will list all of the HAL pins and if you click on one you can see its value, that might give you a better understanding of how they can be/are used
[16:54:25] <lcvette[m]2> I understand pins on the I/O, just wasn't aware box values feel it that category
[16:54:47] <lcvette[m]2> Fell
[16:55:40] <hazzy-lab> Yes, that is the beauty of HAL, it can be used for almost anything
[16:56:48] <lcvette[m]2> Do these need to be on the Hal?
[16:56:59] <lcvette[m]2> Would it be advantageous?
[16:58:20] <hazzy-lab> No they don't have to be, but it might be advantageous.
[16:58:20] <hazzy-lab> maybe a combination of HAL and passing parameters to the subroutines would be best
[16:59:14] <lcvette[m]2> Those are questions I want to better understand
[17:00:57] <lcvette[m]2> For stability, ease of future changes, upgrades, transition to other guy's, use in various Hal/in configs etc
[17:03:01] <hazzy-lab> Yes, there are always trade offs, and unfortunately I don't know enough about it to know what they are
[17:04:02] <hazzy-lab> Ok, I really should go cut the grass :)
[17:04:03] <hazzy-lab> bbl
[17:04:05] <lcvette[m]2> Now I have some good direction for researching
[17:04:23] <lcvette[m]2> Ok
[17:04:25] <lcvette[m]2> Thanks hazzy
[17:32:23] -!- RSSBot[turbosssp has joined #hazzy
[17:41:03] <hazzy1[m]> What is this RSS bot?
[17:41:15] <TurBoss> gitlab spam!
[17:41:33] <TurBoss> I know you wanted them
[17:42:00] <hazzy1[m]> Lol, I do!
[17:42:21] -RSSBot[turbosssp:#hazzy- Hazzy activity posted a new article: TurBoss pushed to project branch CameraWidget at Hazzy / QtPyVCP ( https://gitlab.com )
[17:42:28] <lcvette[m]2> we have a new bot?
[17:42:51] * hazzy1[m] uploaded an image: VectorImage_2018-07-15_054226.jpg (814KB) < https://matrix.org >
[17:43:03] <lcvette[m]2> lawnbot
[17:43:13] <TurBoss> you should roomba it
[17:43:14] <lcvette[m]2> lol
[17:43:17] <hazzy1[m]> I broke it, xD
[17:43:22] <TurBoss> :O
[17:44:22] <TurBoss> Lcvette: yes a new bot ! it will spam our activity with the code :P
[17:44:32] <lcvette[m]2> nice
[17:44:39] <TurBoss> so we don't get bored
[17:46:01] <lcvette[m]2> sounds awesome
[17:46:49] <hazzy1[m]> I guess I forgot to snug up the nuts last time I worked on it and they vibrated off, shoot
[17:47:17] <lcvette[m]2> Let it grow
[17:47:27] <TurBoss> https://hackaday.com
[17:47:33] <lcvette[m]2> Tall grass is the new in thing
[17:47:35] <TurBoss> stmbl on hack aday
[18:12:35] -RSSBot[turbosssp:#hazzy- Hazzy activity posted a new article: TurBoss pushed to project branch CameraWidget at Hazzy / QtPyVCP ( https://gitlab.com )
[18:33:46] <hazzy1[m]> A new article xD
[19:01:49] <lcvette[m]2> So popuplar
[19:27:55] <hazzy-lab> TurBoss: You got the camera working in designer!!!
[19:28:23] <TurBoss> yes
[19:28:37] <TurBoss> but not in linuxcnc
[19:28:51] <hazzy-lab> hmm
[19:29:45] <hazzy-lab> Thats odd, how can it work one place and not the other?
[19:29:50] <hazzy-lab> very strange
[19:31:29] <TurBoss> it doesn't show
[19:31:42] <TurBoss> but I think that the problem is the path to camera.ui
[19:31:56] <hazzy-lab> I fixed the path, still does not work
[19:31:57] <hazzy-lab> :9
[19:32:00] <hazzy-lab> :(
[19:33:21] <hazzy-lab> It does make the UI slow to load, so it is doing something ..
[19:33:36] <TurBoss> yes
[19:33:52] <hazzy-lab> afk to climb stone mountain
[19:34:02] <TurBoss> latter
[20:21:50] <TurBoss> Lcvette: have you moved to 2.8 master?
[21:58:42] <hazzy-lab> TurBoss: I think the reason the camera does not show is that it is a subclass of QMainWIndow instead of QWidget, so there is a MainWindow inside of another MainWIndow
[21:59:17] <TurBoss> i suspected but didnt know qwidget
[21:59:32] <TurBoss> trying
[21:59:50] <hazzy-lab> I still can't get it to work though :(
[22:00:09] <hazzy-lab> TypeError: ('Wrong base class of toplevel widget', (<class 'QtPyVCP.widgets.display_widgets.camera.camera.Camera'>, 'QMainWindow'))
[22:00:09] <hazzy-lab> (main.py:48)
[22:00:32] <lcvette[m]2> No :/
[22:00:56] <lcvette[m]2> Was a lazy ass today
[22:01:32] <hazzy-lab> We all were, it was Sunday :D
[22:02:02] <hazzy-lab> Is your wifes friend still visiting?
[22:04:29] <lcvette[m]2> No, took her to the airport at 6
[22:04:58] <lcvette[m]2> Had dinner after and been vegging since
[22:11:35] <TurBoss> hazzy-lab could be where its the widget placed in the GUI?
[22:12:59] <lcvette[m]2> Still wrapping with installing 2.8 turboss?
[22:13:11] <lcvette[m]2> Wrestling*
[22:13:24] <TurBoss> ?¿
[22:13:26] <hazzy-lab> Oh, could be! Will check
[22:13:46] <hazzy-lab> Lcvette: No, this is with the interface now
[22:13:52] <TurBoss> what does that mean?
[22:13:52] <TurBoss> :)
[22:13:59] <TurBoss> ty
[22:14:12] <lcvette[m]2> Ah ok
[22:14:38] <lcvette[m]2> The camera interface
[22:14:38] <lcvette[m]2> Ok
[22:14:45] <lcvette[m]2> I see now
[22:14:53] <TurBoss> yes :)
[22:15:08] <TurBoss> it doesnt show
[22:15:18] <TurBoss> itself
[22:15:33] <hazzy-lab> maybe it needs a .show()?
[22:15:39] <hazzy-lab> I will try
[22:21:49] <hazzy-lab> Got it working!!!
[22:21:53] <hazzy-lab> I will push
[22:22:32] -!- Roguish has quit [Quit: ChatZilla 0.9.92-rdmsoft [XULRunner 35.0.1/20150122214805]]
[22:24:02] <hazzy-lab> Spam??
[22:24:24] <hazzy-lab> Lazy spam bot
[22:26:47] <hazzy-lab> Changing to a QWidget broke the layout
[22:26:57] <hazzy-lab> But that should be easy to fix
[22:28:52] -RSSBot[turbosssp:#hazzy- Hazzy activity posted a new article: Kurt Jacobson pushed to project branch CameraWidget at Hazzy / QtPyVCP ( https://gitlab.com )
[22:29:04] <hazzy-lab> Hmm the menu will not work either, since a QWidget does not have a menubar :(
[22:29:30] <hazzy-lab> gtg, bbl
[22:31:28] -!- hazzy1 has joined #hazzy
[22:31:28] -!- mode/#hazzy [+o hazzy1] by ChanServ
[22:31:33] <hazzy-dev> aha! I have an idea!!!
[22:31:44] <TurBoss> menu is temporal
[22:32:04] <TurBoss> also the status bar
[22:32:08] <hazzy-dev> Ok, but it could append to the main windows menu!
[22:32:22] <hazzy-dev> because it is passed the parent
[22:32:37] <hazzy-dev> but I have do go :D
[22:32:42] <TurBoss> bye
[23:43:18] * hazzy-lab is back
[23:43:50] <lcvette[m]2> what's the idea
[23:55:32] <TurBoss> hazzy-lab got anything ?
[23:57:35] <hazzy-lab> no, not yet