#hazzy | Logs for 2020-06-13

Back
[00:07:56] <Joco[m]1> hazzy: you might need to explain again what the issue with that HAL bar indicator is. Cose I'm just running it in dummy UI at the moment. It's horizontal, I'm setting the pin values via halshow and things seem to be working fine.
[00:13:01] <Joco[m]1> ah - think I found it. When I put it into vertical mode the color gradient goes to pot
[00:18:44] <Joco[m]1> and the issue is in the base widget
[01:07:18] <Joco[m]1> hazzy: this what you were looking for?
[01:07:25] * Joco[m]1 uploaded an image: image.png (26KB) < https://matrix.org >
[01:07:52] <Joco[m]1> those are the halbar widgets after tweaking the base bar widget code.
[02:10:07] <lmclaren[m]1> Thanks for the plugin Joco, it works perfectly once I worked out that I had to net it in the postgui
[02:10:42] <Joco[m]1> cool - great news
[02:17:57] <Joco[m]1> If there are other functions that are not easy to get at from HAL but which you can see being done in the GUI let me know. It might be easy to extend the plugin for more pins
[02:18:40] <lmclaren[m]1> thank you
[02:43:35] -!- c-log has quit [Ping timeout: 258 seconds]
[05:19:12] <Joco[m]1> hazzy: possible another step in the right direction:
[05:19:15] * Joco[m]1 uploaded an image: image.png (29KB) < https://matrix.org >
[06:04:31] <JT-Cave> morning
[06:23:08] <TurBoss> hello
[06:23:16] <Joco[m]1> hi
[07:33:15] -!- JT-Cave has quit [Remote host closed the connection]
[07:33:34] -!- JT-Cave has joined #hazzy
[08:09:49] <hazzy-m1> Joco: look like you got it! Fantastic
[11:17:55] -!- slata[m] has joined #hazzy
[11:22:23] <hazzy-m1> slata: hello
[11:24:37] -!- harindugamlath has joined #hazzy
[11:25:18] -!- harindugamlath has quit [Remote host closed the connection]
[11:30:23] -!- harindu has joined #hazzy
[11:33:25] <harindu> Hi, I was directed here from linuxcnc forum and I'm having some questions on probe basic. I just got my okuma howa mill converted. I was a mach 3 user before and have very minimal experience with linux.
[11:33:47] <harindu> First issue I cannot update with the maintenance tool
[11:34:42] <harindu> second one is that my tool table is missing tool wear offsets. am I missing something here.
[11:35:32] <harindu> Can anyone help me to setup probe basic correctly. This what I'm facing.
[11:35:44] <harindu> https://forum.linuxcnc.org
[11:37:52] <hazzy-m1> harindu: LinuxCNC doesn't have wear offsets in addition to cutter dia
[11:38:25] <hazzy-m1> I've been thinking of ways we can add that on the GUI side
[11:39:19] <harindu> wow. that's a bit of a surprise.
[11:39:25] -!- cerna has joined #hazzy
[11:39:25] <cerna> Isn't wear offset dynamic property?
[11:41:21] <harindu> did you look in to the forum post link. My tool table is missing some offsets which I thought were wear offsets.
[11:43:10] <harindu> https://forum.linuxcnc.org
[11:44:33] <JT-Cave> I thought we had wear offsets we == LinuxCNC
[11:46:16] <JT-Cave> http://linuxcnc.org
[11:50:50] <harindu> Can Anyone explain what are those x,y offsets in the above image
[11:52:31] <hazzy-m1> harindu: they offset the control point. Really would only use those if you had multiple spindles
[11:53:09] <harindu> That cleared everything. Thanks.
[11:53:12] <hazzy-m1> For example a secondary height speed engraving spindle
[11:54:04] <harindu> One question though, When I try to run the maintenance tool I get an repository error
[11:54:21] <harindu> https://forum.linuxcnc.org
[11:54:41] <hazzy-m1> JT-Cave: in some controls you have a tool wear value that is subtracted from the diameter
[11:55:02] <TurBoss> <harindu "One question though, When I try "> thats my fault
[11:55:03] <JT-Cave> ah
[11:55:04] <TurBoss> not updates yet
[11:56:48] <harindu> I'm having mix feeling on not having wear offsets in the control. In some specific operations that is incredibly useful
[12:00:15] <harindu> Thanks guys. So i'm not missing anything right. I was confused with repository error.
[12:04:54] <TurBoss> I'll try to get it working soon
[12:10:31] <Not-944e> [02qtpyvcp] 07TurBoss pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/JfQkv
[12:10:33] <Not-944e> [02qtpyvcp] 07TurBoss 033b6aa9f - (installer) set date automatically
[12:11:07] <Lcvette> morning
[12:11:55] <harindu> If you need a machine to test I can surely help. I converted an Old Okuma Howa Ram type CNC mill and now trying to play around with it. (a Big green machine). With delta servos and drive that can take a secondary linear encoder to give a fully closed loop within the drive.
[12:12:02] <Not-944e> [02qtpyvcp] 07KurtJacobson pushed 031 commit to 03gh-pages [+489/-0/±0] 13https://git.io/JfQkT
[12:12:03] <Not-944e> [02qtpyvcp] 07traviscibot 0326930bd - Deploy kcjengr/qtpyvcp to github.com/kcjengr/qtpyvcp.git:gh-pages
[12:12:47] <TurBoss> amazing
[12:13:02] <TurBoss> morning
[12:13:13] <hazzy-m1> harindu: I agree the lack of wear offsets is a slight inconvenience. What I generally do is program the part with with the path offset by tool dia, and then use the diameter offset for wear
[12:13:41] <hazzy-m1> harindu: nice machine!!
[12:15:26] <harindu> Thanks. That's one way doing that. Thanks it had a approximately 4.2kw servo on the Z axis.
[12:18:52] <TurBoss> hazzy: hi, did you found any issue with having the installer as submodule?
[12:19:02] <TurBoss> its needed for the buildbot
[12:19:16] <TurBoss> also the build bot can do other thing too
[12:19:19] <TurBoss> if nedded
[12:19:39] -!- harindu has quit [Ping timeout: 245 seconds]
[12:22:13] -!- harindu has joined #hazzy
[12:22:58] <TurBoss> Lcvette: we have to finish the 3d plotter for the lathe
[12:23:12] <Lcvette> /o\
[12:23:14] <Lcvette> its broken
[12:23:22] <Lcvette> error on start up
[12:23:33] <TurBoss> what branch
[12:23:35] <Lcvette> missing the xz_view slot in designer
[12:23:40] <Lcvette> master
[12:23:46] <Lcvette> think we merged lathe to master
[12:23:58] <TurBoss> nono
[12:24:04] <TurBoss> as far i know
[12:24:13] <TurBoss> we merged the max tool
[12:24:23] <TurBoss> for tooltable
[12:24:45] * Lcvette uploaded an image: Screenshot_2020-06-13_12-24-35.png (32KB) < https://matrix.org >
[12:24:56] <Lcvette> this looks like lathevcp was merged to master no?
[12:25:14] <Lcvette> turboss ^^^
[12:25:14] <TurBoss> yes
[12:25:42] <TurBoss> thats probebasic
[12:25:52] <TurBoss> we need to merge it on qtpyvcp too
[12:25:55] <TurBoss> but is unfinished
[12:26:04] <Lcvette> ah
[12:26:18] <Not-944e> [02qtpyvcp] 07TurBoss deleted branch 03max_tooltable_rows - 13https://git.io/fhCou
[12:26:19] <Not-944e> [02qtpyvcp] 07TurBoss deleted branch 03max_tooltable_rows
[12:27:04] <TurBoss> I'll try to get the installer for pb working then the vtk
[12:27:33] <Lcvette> \o/
[12:27:34] <Lcvette> ok
[12:27:36] <Lcvette> hurray!
[12:27:43] <Lcvette> then we need hazzy's dro's and i think its ready to test on machine!
[12:27:45] <Lcvette> \o/
[12:27:57] <Lcvette> and can say goodbye to gmoccapy
[12:28:02] <Lcvette> its soo bad
[12:28:02] <TurBoss> great
[12:28:05] <TurBoss> \ø/
[12:28:47] <TurBoss> Lcvette: with the new installer config there is no option to build it locally (with qtcreator)
[12:29:02] <TurBoss> only auto
[12:29:16] <Lcvette> does it need to be built locally?
[12:29:23] <Lcvette> isn't auto better?
[12:29:40] <TurBoss> no
[12:29:42] <TurBoss> they get build and uploaded
[12:30:02] <Lcvette> thats a good thing right?
[12:30:13] <TurBoss> yea
[12:30:49] <TurBoss> each commit builds a dev installer wich may prompt updates for dev aka master
[12:31:24] <TurBoss> tagged commits will get a release installer wich only will prompt releases as update
[12:31:43] <TurBoss> stable and develop versions
[12:36:21] harindu is now known as hr_ram
[12:41:27] -!- hr_ram has quit [Remote host closed the connection]
[12:43:57] -!- hr_ram has joined #hazzy
[12:46:09] -!- jmarsac has joined #hazzy
[12:59:45] -!- hr_ram has quit [Remote host closed the connection]
[13:10:12] <Not-944e> [02probe_basic] 07TurBoss pushed 031 commit to 03installer [+0/-0/±1] 13https://git.io/JfQI4
[13:10:14] <Not-944e> [02probe_basic] 07TurBoss 0367b40a6 - package templates
[13:26:51] <Not-944e> [02probe_basic] 07TurBoss pushed 032 commits to 03installer [+0/-0/±2] 13https://git.io/JfQI9
[13:26:52] <Not-944e> [02probe_basic] 07TurBoss 037dea885 - qtpyvcp as requirement
[13:26:54] <Not-944e> [02probe_basic] 07TurBoss 0382fb3e6 - use qtpyvcp pipy packages
[13:35:53] <Not-944e> [02probe_basic] 07TurBoss pushed 031 commit to 03installer [+0/-0/±1] 13https://git.io/JfQLt
[13:35:55] <Not-944e> [02probe_basic] 07TurBoss 03decb1ce - (installer) remove old files from config
[13:40:27] <Not-944e> [02probe_basic] 07TurBoss pushed 031 commit to 03installer [+0/-0/±1] 13https://git.io/JfQLZ
[13:40:28] <Not-944e> [02probe_basic] 07TurBoss 0320ef159 - fix dependencies
[13:43:42] <hazzy-m1> TurBoss: Awesome!!!
[13:47:15] <Not-944e> [02probe_basic] 07TurBoss pushed 031 commit to 03installer [+0/-0/±1] 13https://git.io/JfQLR
[13:47:16] <Not-944e> [02probe_basic] 07TurBoss 036011cb7 - install probebasic from the packagae
[13:47:27] <TurBoss> incomming
[13:47:29] <TurBoss> spam
[13:55:46] <Not-944e> [02probe_basic] 07TurBoss pushed 031 commit to 03installer [+0/-0/±1] 13https://git.io/JfQLi
[13:55:48] <Not-944e> [02probe_basic] 07TurBoss 03727e4f9 - fix wheel path
[13:59:15] <TurBoss> hurray!
[13:59:41] <TurBoss> Lcvette: you arround?
[13:59:43] <TurBoss> I'm gona merge the installer branch of PB
[13:59:59] <TurBoss> it includes a submodule
[14:00:53] <Lcvette> You did it?
[14:01:18] <Lcvette> \o/
[14:01:30] <TurBoss> yes only left the subroutines and the config examples
[14:01:31] <TurBoss> \o/
[14:02:22] <Lcvette> Hurray
[14:02:45] <Lcvette> That's awesome!
[14:02:56] <TurBoss> we need to rename the probebasic coonfig directory
[14:03:09] <TurBoss> on put it inside one named linuxcnc
[14:03:10] <Lcvette> Ok
[14:03:16] <TurBoss> * or put it inside one named linuxcnc
[14:03:47] <TurBoss> to follow common configuration style
[14:03:58] <TurBoss> @hazzy started once to do it on a branch
[14:04:21] <TurBoss> we can se there how to do
[14:08:30] <TurBoss> https://github.com
[14:10:23] <TurBoss> tha files there should be old
[14:10:44] <TurBoss> we need to make the same file structure in the format of that branch
[14:11:26] <TurBoss> linuxcnc/configs/sim.probe_basic
[14:11:27] <TurBoss> nc_files/probe_basic
[14:12:03] <TurBoss> * we can see there how to do
[14:26:06] <TurBoss> ok the installer works, some error with versions but fine (not useable yet lol)
[14:26:34] <TurBoss> Lcvette: do you have time to look at the vtk for lathe stuff?
[15:17:31] -!- jmarsac has quit [Ping timeout: 272 seconds]
[15:34:11] <Lcvette> TurBoss: yo
[15:34:18] <Lcvette> im here
[15:34:27] <Lcvette> sorry had to get cleaned up
[15:34:42] <TurBoss> okay
[15:35:21] <Lcvette> so remember the slot for xz view?
[15:35:24] <Lcvette> it dissapeared
[15:35:33] <Lcvette> not im getting an error when i try and open lathe
[15:35:57] <TurBoss> it doesn't is on vtk_lather branch
[15:36:05] <TurBoss> wich is not on master yet
[15:36:34] <Lcvette> oh oh oh... i seee lathe branch on qtpyvcp
[15:36:35] <Lcvette> /o\
[15:36:39] <Lcvette> lcvette misunderstood
[15:36:50] <Lcvette> ok just checked out and it works
[15:36:50] <Lcvette> \o/
[15:37:14] <TurBoss> okay
[15:37:29] <TurBoss> great
[15:37:37] <TurBoss> only the last tweaks left
[15:37:39] <TurBoss> for 90 90 tools
[15:39:37] <Lcvette> I think for the 90 90 thing
[15:39:39] <Lcvette> we just make a rectangle
[15:39:46] <Lcvette> and make the width 2mm
[15:40:00] <Lcvette> pretty styandard size for a parting/grooving too
[15:40:08] <TurBoss> ok
[15:40:52] <Lcvette> if it is position 2 it offsets to the right, if position 1 it offsets to the left
[15:54:10] <TurBoss> Lcvette: don't use diamter as width?
[15:54:19] <Lcvette> no
[15:54:31] <Lcvette> diameter is for the corner radius
[15:54:42] <Lcvette> would be way too small
[15:54:50] <TurBoss> a fixed value?
[15:54:51] <Lcvette> 1/128"
[15:55:00] <Lcvette> yes 2mm
[16:02:26] <Not-944e> [02qtpyvcp] 07TurBoss pushed 031 commit to 03VTK_Lather [+0/-0/±1] 13https://git.io/JfQYR
[16:02:27] <Not-944e> [02qtpyvcp] 07TurBoss 03de82f77 - draw 90 90 tools
[16:02:34] <TurBoss> done
[16:02:42] <TurBoss> test and merge?
[16:03:01] <Lcvette> pulling to test
[16:03:11] * TurBoss uploaded an image: Captura de pantalla de 2020-06-13 22-02-52.png (2KB) < https://matrix.org >
[16:03:45] <Not-944e> [02qtpyvcp] 07Lcvette created branch 03VTK_Lather 13https://git.io/JfQY0
[16:03:51] * TurBoss posted a file: Captura de pantalla de 2020-06-13 22-03-10.png (2KB) < https://matrix.org >
[16:05:14] <Lcvette> i just pulled but im not getting the rectangle with the 90 90 tool
[16:05:37] <TurBoss> is 1 or 2?
[16:05:41] <Lcvette> ?
[16:05:42] <TurBoss> in orientation ?
[16:06:12] <TurBoss> <Lcvette "if it is position 2 it offsets t"> this ^^
[16:06:41] <Lcvette> lol /o\
[16:06:46] <Lcvette> was on position 6
[16:06:57] <Lcvette> /o\
[16:06:58] <Lcvette> fixed and is working
[16:07:01] <Lcvette> that is 2mm?
[16:07:10] <Lcvette> looks wide
[16:07:14] <Lcvette> and really long
[16:08:26] <TurBoss> smaller
[16:08:27] <TurBoss> ok
[16:09:36] <TurBoss> how much ?
[16:09:37] <TurBoss> half?
[16:11:00] * TurBoss uploaded an image: Captura de pantalla de 2020-06-13 22-10-45.png (6KB) < https://matrix.org >
[16:11:24] <Lcvette> How long are the arrows?
[16:11:30] <Lcvette> Proportional?
[16:12:05] <TurBoss> 10 if mm 2 if inchs
[16:12:29] <Lcvette> Arrows are 10mm?
[16:12:51] <TurBoss> or 2 inch
[16:13:32] <TurBoss> depend on unit system
[16:13:33] <Lcvette> 2 inch is too long
[16:13:43] <TurBoss> the active one
[16:13:58] <TurBoss> fo the arrows?
[16:14:07] <TurBoss> or the tool?
[16:14:29] <TurBoss> Lcvette: sorry arrows are 1 inc
[16:14:45] <TurBoss> ```python
[16:14:45] <TurBoss> http://repository.qtpyvcp.com
[16:14:56] <Lcvette> I'm saying make the groove tool display length the same as the arrow length
[16:15:19] <TurBoss> now is one inch both
[16:15:24] <TurBoss> its ok?
[16:15:30] <Lcvette> 1inch is big
[16:15:46] <TurBoss> ok both smaller?
[16:15:53] <Lcvette> Yes
[16:15:58] <Lcvette> Sek I'll show you
[16:16:06] <TurBoss> ok
[16:17:10] * Lcvette uploaded an image: VectorImage_2020-06-13_041700.jpg (95KB) < https://matrix.org >
[16:18:35] <Lcvette> TurBoss: ^^^
[16:20:04] <Not-944e> [02qtpyvcp] 07TurBoss pushed 031 commit to 03VTK_Lather [+0/-0/±1] 13https://git.io/JfQOL
[16:20:06] <Not-944e> [02qtpyvcp] 07TurBoss 032f5cb39 - tool and axis size
[16:20:11] <Lcvette> That is mm
[16:20:15] <TurBoss> up
[16:22:39] <Not-944e> [02qtpyvcp] 07Lcvette created branch 03VTK_Lather 13https://git.io/JfQOs
[16:23:38] <Lcvette> still looks way too long
[16:23:50] <Lcvette> that is only 10mm length and 2mm width?
[16:28:01] <TurBoss> they are 0.5 units for now
[16:29:01] <Lcvette> Lost me
[16:29:39] <TurBoss> vtk units atr tricky
[16:29:42] <TurBoss> :P
[16:30:49] <Lcvette> Not the same for x and y?
[16:31:01] <Lcvette> How you do 2mm?
[16:32:22] <TurBoss> with the data comming from tooltable or path
[16:32:24] <TurBoss> not by hand
[16:39:03] <Lcvette> By hand how are you doing?
[16:41:21] <TurBoss> sorry I'm afk
[16:44:19] <Lcvette> no worries
[16:56:26] -!- jmarsac has joined #hazzy
[16:56:37] <Lcvette> TurBoss: are you gona for the day or just a little bit?
[16:57:10] <TurBoss> we can continue other day or latter
[16:57:14] <TurBoss> sorry
[16:57:16] <TurBoss> :/
[16:57:18] <Lcvette> ok
[16:57:26] <Lcvette> what file was it in?
[16:57:36] <Lcvette> i can try tinkering
[16:57:54] <TurBoss> thanks
[16:57:55] <TurBoss> will countinue
[16:58:06] <Lcvette> i see
[16:58:14] <Lcvette> vtkbackplot.poy
[16:59:37] <TurBoss> yes
[16:59:44] <TurBoss> !
[16:59:46] <TurBoss> search for Tool:
[16:59:53] <TurBoss> thes it starts
[17:04:23] <Lcvette> oh i see
[17:04:34] <Lcvette> its about the same length at the triangle tool now
[17:04:36] <Lcvette> that looks fine!
[17:22:08] <Not-944e> [02qtpyvcp] 07joco-nz opened pull request 03#40: BUG: Corrected shading for vertical orirentation. - 13https://git.io/JfQsC
[17:22:17] -!- jmarsac has quit [Ping timeout: 272 seconds]
[17:23:43] <hazzy-m1> sweet!
[17:23:49] <Joco[m]1> hazzy: my corrections to the bar widget in this pull. Hopefully is enough to be able to push this and the hal version into mainstream.
[17:26:11] <Joco[m]1> <hazzy-m1 "sweet!"> give it a bit of a kick to make sure I've not been a dumb-ass. It seems to work from what I can see. was also testing the HAL version in the UI and using halshow to set the pins and drive changes. Those were the pics I posted earlier.
[17:30:56] <hazzy-m1> I just tested in designer, and by twiddling the HAL pins, works perfect!
[17:31:13] <hazzy-m1> merge coming uo
[17:31:24] <Joco[m]1> sweet
[17:31:48] <Not-944e> [02qtpyvcp] 07KurtJacobson closed pull request 03#40: BUG: Corrected shading for vertical orirentation. - 13https://git.io/JfQsC
[17:31:49] <Not-944e> [02qtpyvcp] 07KurtJacobson pushed 032 commits to 03layout_aware_bar_indicator [+0/-0/±2] 13https://git.io/JfQsN
[17:31:51] <Not-944e> [02qtpyvcp] 07James 03a1962c4 - BUG: Corrected shading for vertical orirentation. Corrected logic to deal with border display based on orientation. Removed trying to rotate text in vertical display. Removes need to traying to deal with width issues and working out correct bar width to display text as it widens as percentage climbs to 100%.
[17:31:52] <Not-944e> [02qtpyvcp] 07KurtJacobson 0376495ef - Merge pull request #40 from joco-nz/layout_aware_bar_indicator
[17:33:08] <Joco[m]1> well that was a useful little bit of focus. 🙂
[17:34:27] <hazzy-m1> yes, very!
[17:34:32] <hazzy-m1> Thank you
[17:36:16] -!- jmarsac has joined #hazzy
[17:52:45] <Joco[m]1> right - sunny but cool day. Time to get my A into G.
[18:30:16] -!- jmarsac has quit [Read error: Connection reset by peer]
[22:42:26] <Not-944e> [02qtpyvcp] 07KurtJacobson pushed 0322 commits to 03master [+7/-1/±28] 13https://git.io/JfQuM
[22:42:27] <Not-944e> [02qtpyvcp] 07KurtJacobson 03d975900 - remove debug prints and add ToDo
[22:42:29] <Not-944e> [02qtpyvcp] 07KurtJacobson 03ff86d02 - Merge branch 'layout_aware_bar_indicator'
[22:42:30] <Not-944e> [02qtpyvcp] 07KurtJacobson 03e3f32f6 - add range setter methods
[22:42:32] <Not-944e> [02qtpyvcp] ... and 19 more commits.
[22:43:40] <Not-944e> [02qtpyvcp] 07KurtJacobson deleted branch 03layout_aware_bar_indicator - 13https://git.io/fhCou
[22:43:41] <Not-944e> [02qtpyvcp] 07KurtJacobson deleted branch 03layout_aware_bar_indicator
[22:43:55] <Not-944e> [02qtpyvcp] 07KurtJacobson pushed 031 commit to 03gh-pages [+489/-0/±0] 13https://git.io/JfQu9
[22:43:57] <Not-944e> [02qtpyvcp] 07traviscibot 0341bedac - Deploy kcjengr/qtpyvcp to github.com/kcjengr/qtpyvcp.git:gh-pages
[22:44:23] <hazzy-m1> Joco: all done with the HAL bar indicator, really appreciate it
[22:44:50] <hazzy-m1> you can delete joco-nz:layout_aware_bar_indicator if you like, it has been merged to master
[22:45:41] <Joco[m]1> Rgr. Cheers.
[22:45:58] <hazzy-m1> Lcvette: you will now get this warning when running ProbeBasic:
[22:45:58] <hazzy-m1> ```
[22:45:58] <hazzy-m1> [qtpyvcp.lib.decorators][WARNING] Deprecation Warning: The widget "qtpyvcp.widgets.display_widgets.load_meter.LoadMeter" has been deprecated and will be removed in the future. Reason: new base class implementation. Replaced by: BarIndicator. (decorators.py:25)
[22:46:25] * hazzy-m1 sent a long message: < https://matrix.org >
[22:46:33] <Lcvette> What's that?
[22:46:59] <hazzy-m1> You will need to replace the old spindle LoadMeter with the new HALBarIndicator
[22:47:15] <Lcvette> Ok
[22:47:24] <Lcvette> Works now?
[22:47:38] <hazzy-m1> yes, Joco fixed it!!
[22:47:54] <Lcvette> Hurray!
[22:48:01] <Lcvette> \o/
[22:49:59] <hazzy-m1> Lcvette: I'll do it for you
[22:50:10] <hazzy-m1> will be easier that way lol
[22:50:15] <Lcvette> I can do our unless it python stuff
[22:50:24] <Lcvette> Ok
[22:50:36] <Lcvette> /o\
[22:50:54] <hazzy-m1> requires a little code fu
[22:51:22] <Lcvette> Ok... you do it!
[22:51:28] <Lcvette> Lol
[22:57:37] <hazzy-m1> Lcvette: why do you have the max value set to 150?
[22:57:43] <hazzy-m1> should it not be 100 for percent?
[22:57:57] <hazzy-m1> you should it be able to go over 100%
[22:57:59] <hazzy-m1> ?
[22:59:26] <Not-944e> [02probe_basic] 07KurtJacobson pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/JfQzc
[22:59:27] <Not-944e> [02probe_basic] 07KurtJacobson 03ccc333d - use new HALBarIndicator for spindle load
[23:00:07] <hazzy-m1> I'll let you format it however you like , I just replaced it with the new widget and left everything like before
[23:00:49] <Not-944e> [02probe_basic] 07KurtJacobson pushed 031 commit to 03gh-pages [+88/-0/±0] 13https://git.io/JfQzR
[23:00:50] <Not-944e> [02probe_basic] 07traviscibot 0332672ba - Deploy kcjengr/probe_basic to github.com/kcjengr/probe_basic.git:gh-pages
[23:00:52] <Not-944e> [02qtpyvcp] 07KurtJacobson pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/JfQz0
[23:00:53] <Not-944e> [02qtpyvcp] 07KurtJacobson 038c5a02a - missed rename
[23:02:19] <Not-944e> [02qtpyvcp] 07KurtJacobson pushed 031 commit to 03gh-pages [+489/-0/±0] 13https://git.io/JfQzz
[23:02:21] <Not-944e> [02qtpyvcp] 07traviscibot 03cec7b59 - Deploy kcjengr/qtpyvcp to github.com/kcjengr/qtpyvcp.git:gh-pages
[23:03:59] <Not-944e> [02qtpyvcp] 07KurtJacobson pushed 031 commit to 03DROWidgets [+5/-0/±3] 13https://git.io/JfQzr
[23:04:00] <Not-944e> [02qtpyvcp] 07KurtJacobson 03f9e9bf4 - add new DROLabel and DROLineEdit widgets
[23:05:16] <Lcvette> You cam go over 100%
[23:05:33] <Lcvette> But not for long
[23:05:36] <Lcvette> * You can go over 100%
[23:06:27] <Lcvette> Most spindle drives have a short period for higher acceptable spindle loads
[23:09:27] <Lcvette> Hazzy^^^
[23:09:55] <Lcvette> While your winning sp much hows the dros? :o
[23:10:10] <Lcvette> * While your winning so much hows the dros? :o
[23:10:22] <hazzy-m1> Ok, that's what I though
[23:10:58] <Joco[m]1> oh this is cool.. Got a LinuxMint dev VM on my windows box working. So I get to use my 32" widescreen :-)
[23:11:14] <Lcvette> Hurray
[23:11:25] <hazzy-m1> So you will need to change the format from percentage to value, since other wise the text will only show the percentage of the bar filled, rathe then the actual value
[23:11:34] <Joco[m]1> using Designer with a BIG screen is much nicer
[23:11:36] <hazzy-m1> Joco: sweet!
[23:11:58] <Joco[m]1> yeah - 32" of curved widescren goodnes
[23:12:08] <Lcvette> You added the new dro label and line edits?
[23:12:23] <hazzy-m1> Lcvette: not yet
[23:12:32] <hazzy-m1> they still need a little work, but almost done
[23:12:33] <Lcvette> Oh
[23:12:38] <hazzy-m1> just need to add Dia mode
[23:12:39] <Lcvette> Ok
[23:12:53] <hazzy-m1> but that's for another day
[23:13:10] * hazzy-m1 is up way past his bed time lol
[23:13:17] <hazzy-m1> night
[23:13:20] <Lcvette> It's Saturday!
[23:13:28] <Lcvette> No bedtimes on Saturdays
[23:13:34] <Lcvette> Lol
[23:14:00] <hazzy-m1> if you have to fly out for work the next day there is lol
[23:17:36] <hazzy-m1> Lcvette: did I tell you we have a new demo machine coming in next week? Its a monster, even bigger than the one CaptHindsight saw at fabtech. 24' x 24' x 12' tall and 56,000lbs, it will just barely fit in the show room. Should be fun, so now that rona is mostly over got to round people up to buy it haha
[23:18:24] <Lcvette> Lol
[23:18:32] <Lcvette> That's a big machine
[23:18:43] <Lcvette> But it will fit in my shop
[23:19:06] <Lcvette> Will only tackle up about 1/3
[23:19:15] <hazzy-m1> Hahahaha
[23:19:15] <Lcvette> * Will only take up about 1/3
[23:19:25] <Lcvette> I will demo it if you need
[23:19:27] <hazzy-m1> Might punch the slab
[23:20:02] <Lcvette> I put 8" rebar reinforced floors in
[23:20:19] <Lcvette> Process kit still not enough
[23:20:19] <hazzy-m1> I got 1.25" steel plates cut to distribute the load since we only have an 8" slab
[23:20:49] <Lcvette> * Still not enough
[23:20:53] <Joco[m]1> hazzy: Can i feed an MDICommand button some maths to eval?
[23:21:24] <Joco[m]1> or can that just be using the gcode maths functions on the gcode line?
[23:21:32] <hazzy-m1> Joco: I'm afraid not, but would have to refresh on the code
[23:21:46] <hazzy-m1> Gcode maths will work
[23:22:05] <Lcvette> Even with 8" floors, when my machine is turned up on rapids i can feel it in the concrete
[23:22:25] <Joco[m]1> ok - should be able to work.
[23:23:10] <Lcvette> Sub call button would work joco
[23:23:35] <Joco[m]1> yup - that is my backup
[23:24:11] <Joco[m]1> either path should get me where I want. Cheers.
[23:24:17] <hazzy-m1> Last thing I have to do before the machine arrives is run a new 100A 480v power drop for it
[23:24:39] <Joco[m]1> ahh 3phase. The dream.
[23:24:42] <Lcvette> Lcvette doesn't have 480v
[23:24:56] <Lcvette> I have 230v 3ph
[23:25:02] <Joco[m]1> lol - in NZ phase == 480V
[23:25:17] <Joco[m]1> * lol - in NZ 3 phase == 480V
[23:25:18] <hazzy-m1> That's better than single phase!
[23:25:31] <Lcvette> Lcvette actually had 250v 3phase
[23:26:02] <Lcvette> Have high voltage here for some reason
[23:26:44] <hazzy-m1> I almost bought a house that had a separate shop with 240v 3ph, I liked that more than the house lol
[23:26:44] <Lcvette> hazzy: so is the radius mode pushed?
[23:26:59] <Lcvette> Yes
[23:27:00] <hazzy-m1> Not to master yet
[23:27:20] <Lcvette> 3ph from the power company is expensive to have run in residential
[23:29:34] <hazzy-m1> Yes, it actually came from a separate set of lines on the back of the lot, which was nice. Most neighborhoods don't have 3ph, but it backed up to a elementary school
[23:29:35] <Joco[m]1> one day I will get a 5Hp 480V motor and build a 3ph rotaery converter
[23:29:58] <Joco[m]1> actually maybe 8Hp
[23:30:27] <Joco[m]1> ah well .... dreams
[23:31:02] <hazzy-m1> That would be sweet. I just run everything of of VFDs , but that's not idea depending on the equipment
[23:31:44] <Joco[m]1> I use VFD as well. got ones that take single phase and spit out 380V 3ph
[23:37:12] <Lcvette> Mine is 25hp
[23:37:46] * hazzy-m1 uploaded an image: ima_fc284e1.jpeg (211KB) < https://matrix.org >
[23:38:24] <Lcvette> 25hp phase converter showed up today.. another item needed scratched off the list!! Now to get all the wiring, breakers, and miscellaneous crap needed..hahaha... Never ending project!! #cncporn #cncmilling #cnc #cncspindle #cncmachining #g0704cnc #grizzlyg0704 #benchtopmachinist #benchtopcnc #instamachinist #instamachining #diycnc
[23:38:24] <Lcvette> https://www.instagram.com
[23:38:48] <hazzy-m1> I picked up this 5hp vfd the other day, forgot to check if it could take single phase input, it can't lol
[23:39:30] <Lcvette> From memory most Vehicles can run on single phase power but you have to derate the motor that you use with them
[23:39:30] <hazzy-m1> Lcvette: that's a big motor!
[23:39:45] <Lcvette> * From memory most Vfds can run on single phase power but you have to derate the motor that you use with them
[23:40:19] <Lcvette> For the big machine
[23:40:21] <Lcvette> Lol
[23:41:18] <Lcvette> So for example you could use a 3 horsepower motor with that 5 horsepower of vfd on single phase even though it says it's a three phase input
[23:42:30] <Lcvette> Hazzy^^^
[23:42:30] <Joco[m]1> yup - that's what I have done and what the manfacturer says you have to do. Double the VFD power = 2 * motor power
[23:42:54] <Joco[m]1> 1kW motor == 2 kW VFD
[23:42:57] <Lcvette> Pretty common practice
[23:43:28] <Joco[m]1> right ... more cnc machinglearning.
[23:43:40] * Joco[m]1 off to make steel chips
[23:56:20] <Lcvette> Lcvette needs a replacement doldering iron
[23:56:33] <Lcvette> * Lcvette needs a replacement soldering iron