#hazzy | Logs for 2018-12-06

Back
[00:00:51] <Lcvette> still got a ton of errors after running that line you ntold me too
[00:01:37] * Lcvette sent a long message: < https://matrix.org >
[00:06:49] <hazzy-m> `AttributeError: 'linuxcnc.stat' object has no attribute 'joint'`
[00:07:14] <hazzy-m> that means it is trying to use LinuxCNC 2.7 instead of 2.8~pre
[00:07:42] <hazzy-m> oh!
[00:08:12] <hazzy-m> you have to run `. /home/chris/dev/linuxcnc-master/scripts/rip-environment` in the same terminal right before you run `./launch_designer.sh`
[00:08:16] <Lcvette> run that in terminal?
[00:08:30] <hazzy-m> yes
[00:08:52] <hazzy-m> both commands in the ~dev/qtpyvcp-master terminal
[00:09:30] <Lcvette> hurray!
[00:09:33] <Lcvette> everytime?
[00:10:03] <hazzy-m> only the first time you use a new terminal
[00:10:13] <Lcvette> ok
[00:10:26] <hazzy-m> you only need to run the ` . /home/chris/dev/linuxcnc-master/scripts/rip-environment` once
[00:11:06] <Lcvette> hey, i can see my pictures
[00:11:19] <Lcvette> you fixed it
[00:13:24] <hazzy-m> hurray!
[00:13:32] <Lcvette> hurray!
[00:13:33] <hazzy-m> the pictures show in designer now?
[00:13:39] <Lcvette> yes
[00:13:44] <Lcvette> sad face
[00:13:45] <hazzy-m> fantabulous!
[00:14:38] <Lcvette> lol
[00:14:47] <Lcvette> think i know why zero for x and y doesn't work
[00:15:26] <Lcvette> G10 L2 P{ch[0]} X0.0
[00:15:52] <Lcvette> G10 L20 P{ch[0]} Z0.0
[00:16:00] <Lcvette> supposed to all be L20?
[00:18:39] <hazzy-m> not sure
[00:18:43] <hazzy-m> I was guessing
[00:18:44] <hazzy-m> lol
[00:19:09] <Lcvette> z works
[00:19:18] <Lcvette> x and y have L2 instead of L20
[00:38:37] <Lcvette> hazzy youn here?
[00:38:44] <Lcvette> trying to work this out
[00:38:57] <Lcvette> have the linux docs open
[00:39:45] <Lcvette> but im not sure what your doing with P{ch[0]}
[00:40:02] <Lcvette> is that directing it to the currently selected work coordinate system?
[00:40:31] <Lcvette> if so how is that information being pulled in?
[00:42:20] <hazzy-m> aha!
[00:42:26] <Lcvette> normall it would be G10 L2 P1 Z0.0
[00:42:32] <hazzy-m> right
[00:42:34] <Lcvette> that would be for G54
[00:42:53] <hazzy-m> so the {ch[0]} is replaces with the current WCS
[00:43:10] <Lcvette> how is it defined?
[00:43:22] <Lcvette> that must be where the disconnect is because the code is correct
[00:43:23] <hazzy-m> the ch[0] is defined in thw widget rules editor
[00:43:42] <hazzy-m> double click on whe zero button and it will come up
[00:44:16] <hazzy-m> should look like this
[00:44:18] <Lcvette> its up
[00:44:19] * hazzy-m uploaded an image: image.png (65KB) < https://matrix.org >
[00:44:47] <Lcvette> it needs to be represented by 1
[00:45:04] <Lcvette> how do we do that?
[00:45:35] <hazzy-m> so the ch[0] get replaced with the value of linuxcnc.status.g5x_index
[00:45:40] <hazzy-m> ??
[00:46:02] <Lcvette> if you are going to make it into the linux gcode it needs to be a 1
[00:46:04] <Lcvette> ?
[00:46:06] <Lcvette> yes?
[00:46:14] <Lcvette> to complete the line of code
[00:46:20] <hazzy-m> for G54 yes
[00:46:49] <Lcvette> and for each of the others they would be the correct correspoindingn expressions 2 g55, 3 g56
[00:46:55] <Lcvette> etc
[00:47:04] <Lcvette> is there a way to make that happen?
[00:47:11] <hazzy-m> that already happens
[00:47:42] <Lcvette> oh
[00:47:56] <Lcvette> so its broken somewhere else?
[00:49:07] <hazzy-m> if you run LCNC in a terminal it will log the actual MDI command when you push the button
[00:49:20] <hazzy-m> when G54 is active it is G10 L2 P1 X0.0
[00:49:26] <hazzy-m> which should be correct
[00:49:33] <Lcvette> yes
[00:49:37] <Lcvette> ok
[00:49:44] <Lcvette> so it just isn't working
[00:49:46] <hazzy-m> for g58 is gives G10 L2 P5 X0.0
[00:49:50] <hazzy-m> which also seems right
[00:50:11] <hazzy-m> so I think the button is doing the right think
[00:50:23] <hazzy-m> But the numbers seems funky ..
[00:50:29] <hazzy-m> the numbers in the DROs
[00:51:01] <Lcvette> are they pulling from the correct dro places?
[00:51:24] <hazzy-m> I think so, but that is the most likly problem
[00:51:28] <hazzy-m> checking
[00:53:02] <hazzy-m> what is the WC Current pos supposed to be?
[00:53:18] <hazzy-m> the current tool pos relative to the active WCS?
[00:53:40] <hazzy-m> ot the WCS offset from machine zero?
[00:54:01] <Lcvette> hmmm
[00:54:11] <Lcvette> brainer teaser
[00:54:21] <hazzy-m> no, that the WCS offset
[00:54:23] <hazzy-m> sorry
[00:54:25] <Lcvette> let me make sure i pulled those from MSM correctly
[00:54:28] <Lcvette> ;lol
[00:54:41] * hazzy-m is confused
[00:54:43] <hazzy-m> lol
[00:56:04] * Lcvette uploaded an image: workoffsets_probe_bosses.PNG (646KB) < https://matrix.org >
[00:56:15] <Lcvette> lol
[00:56:22] <Lcvette> he is using it as an equation
[00:56:40] <Lcvette> the offset is the diference
[00:56:58] <Lcvette> the current position is the realtime position in work coordinates
[00:57:29] <hazzy-m> ah
[00:58:02] <Lcvette> so there would need to be some math in that wc offset dro
[00:58:18] <hazzy-m> there is a lot of math, lol
[00:58:23] <hazzy-m> I already done it
[00:58:24] <hazzy-m> :D
[00:58:24] <Lcvette> or if the offset value is stored
[00:58:36] <Lcvette> hurrray
[00:59:01] * hazzy-m uploaded an image: image.png (78KB) < https://matrix.org >
[00:59:24] <Lcvette> hazzy is a mathlete
[00:59:30] <Lcvette> hahahaha
[00:59:32] <hazzy-m> also rotation in XY to acount for
[00:59:40] <hazzy-m> which I don't think mach has
[00:59:51] <Lcvette> yeah becuz...mach3 is meh
[00:59:53] <Lcvette> lol
[01:00:09] <Lcvette> and it doesn't have tuple
[01:00:23] <Lcvette> which is a fun word
[01:00:24] <hazzy-m> lol
[01:00:30] <hazzy-m> it is!
[01:00:41] <hazzy-m> I love tuples
[01:00:45] <hazzy-m> so much better then list
[01:00:48] <hazzy-m> haha
[01:00:50] <Lcvette> i do too
[01:01:01] <Lcvette> don't know it but i love it!
[01:01:08] <Lcvette> must be good stuff!
[01:01:35] <hazzy-m> tuple is a list that is not mutable i.e. cant be changed
[01:01:52] <hazzy-m> uses less memory and is faster
[01:02:08] * Lcvette sent a long message: < https://matrix.org >
[01:02:19] <hazzy-m> you found it!
[01:02:23] <Lcvette> totally shows the right code!
[01:02:42] <Lcvette> had to dig deep in my limited bag of terminal fu
[01:03:00] <hazzy-m> the bag is getting fuller
[01:03:03] <hazzy-m> lol
[01:03:13] <Lcvette> then realized it just is fancy words for look at the terminal
[01:03:25] <hazzy-m> commands seem all right
[01:03:41] <Lcvette> hazzy hould use lcvette speak
[01:03:47] <Lcvette> yeah
[01:03:53] <Lcvette> sooo.. then
[01:04:04] <hazzy-m> I heally hould
[01:04:30] <Lcvette> that would look like this.. look in the black window behind the gui scvrteen
[01:04:41] <Lcvette> lol
[01:04:45] <hazzy-m> haha
[01:04:59] <Lcvette> pl
[01:05:05] <Lcvette> so commands are good]
[01:05:06] <hazzy-m> I didn't know you run LCNC in a terminal
[01:05:13] <hazzy-m> I'm impressed!
[01:05:15] <Lcvette> i don't
[01:05:17] <Lcvette> it pops up
[01:05:28] <Lcvette> don't be impressed
[01:05:35] <hazzy-m> Oh, I remember, I set that up for you
[01:05:41] <Lcvette> you programmed it like that i thought for me cuz of my handicaps
[01:05:47] <hazzy-m> since I knew you wouldn't
[01:05:48] <Lcvette> lol
[01:05:48] <hazzy-m> hahaha
[01:05:48] <Lcvette> exaclty
[01:06:14] <Lcvette> you have good forethought
[01:06:50] <hazzy-m> sometimes, not often
[01:07:34] <Lcvette> the real kicker is why it activates when the G10 L20 Px z 0.0 command is given
[01:09:06] <hazzy-m> oh, the DRO values seems screwed up
[01:09:16] <hazzy-m> even the main dros
[01:09:26] <Lcvette> yeah
[01:09:36] <Lcvette> something wonly is happening there
[01:09:56] <Lcvette> i don't see why L20 is used in the docs
[01:11:05] * Lcvette uploaded an image: image.png (33KB) < https://matrix.org >
[01:11:26] <Lcvette> this is showing L2 used for all axis for offset changes
[01:11:26] <Lcvette> no L20
[01:11:35] <Lcvette> maybe a typo?
[01:13:00] <hazzy-m> "G10 L20 is similar to G10 L2 except that instead of setting the offset/entry to the given value, it is set to a calculated value that makes the current coordinates become the given value."
[01:13:30] <hazzy-m> "G10 L2 offsets the origin of the axes in the coordinate system specified to the value of the axis word. The offset is from the machine origin established during homing. The offset value will replace any current offsets in effect for the coordinate system specified. Axis words not used will not be changed."
[01:13:37] <hazzy-m> So I think we want L2
[01:13:50] <Lcvette> i just changed z to L2
[01:13:58] <Lcvette> it was L20 the others were L2
[01:14:06] <Lcvette> maybe that was the issue?
[01:14:30] <hazzy-m> Oh, my bad!
[01:14:38] <hazzy-m> I guess I did't change them all
[01:14:48] <hazzy-m> part of the issure at least
[01:14:55] <hazzy-m> the DROs are still wrong
[01:16:10] <Lcvette> yeah that didn't change much
[01:16:17] * hazzy-m uploaded an image: image.png (262KB) < https://matrix.org >
[01:16:32] <Lcvette> well except now z changes to 0.000 also when i hit the zero button
[01:16:42] <Lcvette> but why is it changing all of them?
[01:16:50] <hazzy-m> so at least the offsets zeror
[01:16:54] <Lcvette> and x and y don't do didly
[01:16:58] <Lcvette> that is sooo wierd
[01:16:59] <hazzy-m> so it is now only a DRO problemo
[01:18:12] <hazzy-m> they do do didly-squat, if the offsets arn't ) zeror to start with
[01:18:34] <hazzy-m> how did zoro get into this?
[01:19:00] <Lcvette> if i move off the origin as if i were going to a part corner, then try and zero x and y, they don't zero
[01:19:27] <Lcvette> lol
[01:19:31] <Lcvette> zeror
[01:19:36] <Lcvette> :D
[01:22:37] <hazzy-m> once I changed from L20 to L2 they seem to work correctly, the DROs don't though
[01:22:43] <Lcvette> i would ask if maybe it is interpereting the dro's differently for reading and writing, but that wouldn't make sense
[01:23:04] <Lcvette> what do you mean they work correctly?
[01:23:06] <hazzy-m> the DROs arn't read at all yet ..
[01:23:26] <hazzy-m> the ofsets are cleared when hitting the zeror button
[01:23:33] <Lcvette> machine coordinates shouldn't ever change
[01:23:50] <hazzy-m> right, the machine coord DROs are broken
[01:23:51] <Lcvette> except at initial homing
[01:23:59] <hazzy-m> I think everything else it OK
[01:24:03] <Lcvette> maybe that is why everything else is broken?
[01:24:13] <hazzy-m> I think so
[01:24:17] <hazzy-m> I hope so
[01:24:24] <Lcvette> everything is based of machine coords
[01:24:47] <Lcvette> and everything times zero is 0
[01:24:48] <Lcvette> lol
[01:25:06] <Lcvette> even though its all addition and subtraction
[01:25:07] <Lcvette> lol
[01:25:21] <hazzy-m> lol
[01:26:02] <Lcvette> that would also be why the arrows on the main window are not where the cone is
[01:26:13] <Lcvette> but are at the origin
[01:26:39] <Lcvette> the doohicky
[01:26:51] <Lcvette> red and green and blue
[01:33:55] <hazzy-m> fixed
[01:33:57] <hazzy-m> push in a few
[01:34:08] <Lcvette> what?
[01:34:10] <Lcvette> seriously?
[01:34:13] <Lcvette> you did it?
[01:34:16] <Lcvette> HURRAY!!!!
[01:34:30] <Lcvette> thats MAJOOOOOOOOORRRRRR!!!!!
[01:36:34] * hazzy-m uploaded an image: image.png (44KB) < https://matrix.org >
[01:36:51] <Lcvette> you are the effin man!
[01:37:12] <Lcvette> that is a thing of beauty my friend!
[01:37:29] <Not> [02QtPyVCP] 07Kurt Jacobson pushed 031 commit to 03master [+0/-0/±1] 13https://gitlab.com/Hazzy/qtpyvcp/compare/5b85297d8178bd631c8a8913bd6a33c35ebb7dcd...c1ae7ea1a07407d607fcbeb0b6e8f11276b1b06b
[01:37:30] <Not> [02QtPyVCP] 07Kurt Jacobson 03c1ae7ea - VCP: fix offsets in ProbeBasic
[01:37:42] <hazzy-m> Hurray!!
[01:37:49] <Lcvette> HURRAYY!!!!
[01:38:03] <hazzy-m> now I can sleep in peace 😃
[01:38:22] <Lcvette> i now see that the tool offset dro's for x, y, a, b are not needed in the offsets page
[01:38:36] <Lcvette> just got the push!
[01:38:41] <Lcvette> sleep in peace my man!
[01:38:46] <Lcvette> that was a major win in my book
[01:39:11] <hazzy-m> not for a plain jain mill, but what if you have a seirial number engraver (dremil tool) clamped to the side of your mill head?
[01:39:23] <hazzy-m> might want the x and y tool offsets then ...
[01:39:45] <Lcvette> ah yeah
[01:39:51] <Lcvette> right angle milling
[01:39:57] <Lcvette> good point
[01:40:00] <hazzy-m> you didn't even think about that with Mach3
[01:40:02] <hazzy-m> hahaha
[01:40:22] <Lcvette> wait
[01:40:28] <Lcvette> one more ask then sleep
[01:40:34] <Lcvette> mdi screen!
[01:40:38] <Lcvette> light gray
[01:40:46] <Lcvette> lol
[01:40:52] <Lcvette> or in the monring
[01:40:56] <Lcvette> lol
[01:41:00] <hazzy-m> do you have the color codes?
[01:41:12] <Lcvette> no
[01:41:15] <Lcvette> :(
[01:41:23] <hazzy-m> ok
[01:41:24] <Lcvette> they get erased everytime i reset
[01:41:26] <hazzy-m> sek
[01:41:36] <Lcvette> its the basic light gray from the color swatch
[01:41:46] <Lcvette> in sad face designer
[01:42:00] <Lcvette> you have to use the #DHDHD or something like that
[01:43:24] * hazzy-m uploaded an image: image.png (70KB) < https://matrix.org >
[01:43:27] <hazzy-m> we can refine them latter
[01:43:33] <Lcvette> great
[01:43:41] <Lcvette> my offsets don't zero at all now
[01:44:46] * hazzy-m uploaded an image: Peek 2018-12-06 01-44.gif (49KB) < https://matrix.org >
[01:45:10] <Lcvette> :(
[01:45:17] <Lcvette> mine don't do that
[01:45:41] <hazzy-m> are you sure the machine is hommed etc?
[01:45:46] <Lcvette> yeah
[01:45:50] <Lcvette> first thing i do
[01:45:53] <hazzy-m> hmmm
[01:46:05] <Lcvette> sek
[01:46:34] <Not> [02QtPyVCP] 07Kurt Jacobson pushed 031 commit to 03master [+0/-0/±1] 13https://gitlab.com/Hazzy/qtpyvcp/compare/c1ae7ea1a07407d607fcbeb0b6e8f11276b1b06b...9ee7148b80ed71e2a011a6cfd86b6473d0eb0a07
[01:46:36] <Not> [02QtPyVCP] 07Kurt Jacobson 039ee7148 - VCP: fix gcode editor colors in ProbeBasic
[01:47:24] * Lcvette sent a long message: < https://matrix.org >
[01:48:04] <hazzy-m> were than any offsets in effect to zero?
[01:48:33] <Lcvette> it was at zero after home
[01:48:38] <Lcvette> no offset in effect
[01:48:53] <Lcvette> i moved and set g55 and tried to zero and nada
[01:48:59] <Lcvette> nothing happens
[01:49:49] * Lcvette sent a long message: < https://matrix.org >
[01:49:56] <Lcvette> homed
[01:51:07] * Lcvette sent a long message: < https://matrix.org >
[01:51:14] <Lcvette> homed
[01:52:05] <Not> [02QtPyVCP] 07Kurt Jacobson pushed 031 commit to 03master [+0/-0/±1] 13https://gitlab.com/Hazzy/qtpyvcp/compare/9ee7148b80ed71e2a011a6cfd86b6473d0eb0a07...cf20f03fa7f0dfb7f7b272a18fb52daa5aa77b35
[01:52:06] <Not> [02QtPyVCP] 07Kurt Jacobson 03cf20f03 - MDIButton: kill debug prints and catch and log exception
[01:53:13] <hazzy-m> Jog around a bit, that issue `G10 L20 P1 X0 Y0 Z0` and then try zeroing
[01:53:24] <hazzy-m> then*
[01:54:16] <Lcvette> zeros after the mdi line
[01:54:54] * Lcvette sent a long message: < https://matrix.org >
[01:55:18] <Lcvette> first zero attempts nothing last ones after your mdi line success
[01:55:50] <hazzy-m> I think that is because there were no offsets active untill you set them with G10 L20
[01:56:07] <Lcvette> so my offset buttons are not working?
[01:56:22] <hazzy-m> the zero buttons?
[01:56:36] <Lcvette> they show in the status on the right of the screen as changing
[01:56:42] <Lcvette> the ofset buttons
[01:56:44] <Lcvette> G54
[01:56:48] <Lcvette> G55
[01:56:52] <hazzy-m> oh yes
[01:57:33] * Lcvette uploaded an image: image.png (29KB) < https://matrix.org >
[01:57:34] <Lcvette> it was active
[01:57:36] <hazzy-m> those are working, but that is just the WCS number, each WCS has it's own set of offsets
[01:58:11] <Lcvette> ?
[01:58:16] <hazzy-m> and you need to set those offsets with G10 L20 before you can have anything to clear
[01:58:42] <Lcvette> not sure i understand
[01:59:59] <Lcvette> get some sleep
[02:00:09] <Lcvette> we can discuss it on fresh minds
[02:00:11] <Lcvette> lol
[02:00:15] <Lcvette> you killed it tonight!
[02:00:28] <hazzy-m> you have multible WCS (G54, G55 ...), and each one of those WCS has it own set of WCO (work coord offsets)
[02:00:33] <Lcvette> even go to zero works now
[02:00:42] <hazzy-m> hurray!
[02:00:51] <hazzy-m> yeah, I better sleep
[02:01:03] <hazzy-m> night man!
[02:01:11] <Lcvette> night bud!
[02:31:55] <Lcvette> figured it out! we are supposed to use the L20 in the zero button formula. it works perfectly when you do. it reets everything automatically as expected and all you have to do is simply press the G5x button up top. they are stored so if you return to a previously stored offset it returns the correct offset and position for the current position. Hurray!
[02:40:32] <Lcvette> im so flippin excited right now!! lol
[02:40:45] <Lcvette> ive worn the type face of the z button
[03:56:20] -!- JT-Shop2 has quit [Ping timeout: 250 seconds]
[03:57:12] -!- JT-Shop has quit [Ping timeout: 250 seconds]
[05:52:40] -!- JT-Shop2 has joined #hazzy
[05:53:31] -!- JT-Shop has joined #hazzy
[09:05:33] <Lcvette> Morning
[09:20:10] <Lcvette> So I think the old noodle was working offerings last night hazzy
[09:20:19] <Lcvette> Overtime
[09:39:47] <Lcvette> I copied over the dro's from work coord current position on offsets page to the main dro box under work so it works there too now!
[09:39:53] <Lcvette> Hurray!
[09:44:06] <Lcvette> Turboss
[09:44:11] <TurBoss> yo
[09:44:14] <TurBoss> morning
[09:44:25] <Lcvette> Morning!
[09:44:49] <TurBoss> whats up?
[09:45:08] <hazzy-m> Morning
[09:45:19] <Lcvette> Hazzy and I figured out the dro and offsets issues last night
[09:45:26] <Lcvette> Is fixed
[09:45:34] <TurBoss> oh greatt
[09:45:35] <Lcvette> Morning Suleman
[09:45:41] <Lcvette> Superman
[09:45:47] <Lcvette> Lol
[09:47:01] <Lcvette> I have no internet
[09:47:29] <Lcvette> Wood is on her way to exchange our modem router
[09:47:33] <Lcvette> M on tablet
[09:47:45] <Lcvette> And Linux computer
[09:48:53] <Lcvette> But if you change the zero button code to G10 L20 P
[09:49:02] <Lcvette> Every thing works properly
[09:49:31] <TurBoss> ohhhh
[09:50:10] <Lcvette> And copy the dro's from work current position in offsets page to the main dro work
[09:52:39] <Lcvette> Dtg still needs to be setup I think
[09:53:07] <Lcvette> But it's starting to work correctly is so exciting
[09:53:15] <TurBoss> fantastic
[09:55:00] <JT-Shop> morning
[09:55:42] <Lcvette> Morning JT
[09:55:49] <TurBoss> hey
[10:03:36] <Lcvette> I think we need to copy the machine coordinates dro from ffsets page to main also
[10:04:02] <Lcvette> The main offsets dro is acting funny but offsets page one is perfect
[10:07:20] <Lcvette> Yes that fixes the odd behavior
[10:28:32] * hazzy-m is back
[10:28:34] <hazzy-m> Hurray!!!
[10:28:46] <Lcvette> Hurray
[10:28:49] <hazzy-m> wait, you said L20 works right?
[10:28:51] <Lcvette> I broke it
[10:28:56] <Lcvette> Yes
[10:29:04] <Lcvette> L20 was the answer
[10:29:53] <Lcvette> But you have to fix the other drowsiness the main window
[10:29:54] <hazzy-m> LOLOLOL, I think I misunderstood what the zero button was supposed to do, I though it was supposed to zeror the offset, but it was suposed to zeror out the current machine position!
[10:30:11] <Lcvette> I just copied the new ones down
[10:30:16] * hazzy-m cant spell zero
[10:30:29] <Lcvette> Yes correct
[10:30:47] <hazzy-m> Excellent!
[10:30:54] <hazzy-m> so in that case L20 is correct
[10:30:57] <Lcvette> But that should effectively be kicking the old offset out and creating a new one
[10:31:01] <Lcvette> Which it does
[10:31:15] <hazzy-m> Right
[10:31:18] <hazzy-m> great
[10:31:40] <Lcvette> The number that pops up in the other dro wc offset
[10:31:46] <Lcvette> ;)
[10:31:49] <Lcvette> You did it
[10:32:09] <Lcvette> But I broke the yellow and red dro
[10:32:37] <Lcvette> I redid the style s sheet and I didn't know how to make it change though
[10:32:48] <Lcvette> :(
[10:33:04] <Lcvette> But now it all works flawlessly
[10:33:59] <Lcvette> This offsets page is for like manual work position setting
[10:34:09] <Lcvette> If you were using a haimer etc
[10:35:02] <hazzy-m> perfect!
[10:35:21] <Lcvette> The probe page has the g5x buttons similarly so you would hit the g5x offset you wanted the probed position to record in
[10:35:35] <hazzy-m> I guess I'll wait for you to push your changes to avoid conflicts here
[10:35:47] <Lcvette> Is all coming together beautifully
[10:35:56] <Lcvette> Wife just walked in with new modem
[10:36:01] <Lcvette> Shekels I install
[10:36:06] <Lcvette> Sek
[11:06:32] <Lcvette> do i have to push them?
[11:06:45] <Lcvette> or just copm,mit them
[11:08:19] <hazzy-m> commit them and then push
[11:09:05] * Lcvette uploaded an image: image.png (221KB) < https://matrix.org >
[11:09:16] <Lcvette> ?
[11:09:39] <hazzy-m> for push should be fine
[11:09:44] <hazzy-m> force*
[11:10:18] <Lcvette> you sure?
[11:10:27] <hazzy-m> yes
[11:10:34] <hazzy-m> you can do any harm
[11:10:38] <hazzy-m> can't*
[11:10:40] <Lcvette> failed
[11:10:56] <Lcvette> declined
[11:11:05] <Lcvette> says Hazzy kicked me out of the club
[11:11:11] <Lcvette> i got the hook
[11:12:02] <hazzy-m> maybe kitkraken is not logged into gitlab?
[11:12:06] <hazzy-m> what is the error?
[11:12:24] <Lcvette> it dissapearewd
[11:13:21] * Lcvette uploaded an image: image.png (225KB) < https://matrix.org >
[11:13:46] <Lcvette> dammit i tried to capture the message
[11:14:14] <hazzy-m> everything looks right
[11:14:18] <Lcvette> refs/heads/masters pre-received hook declined
[11:14:35] <hazzy-m> what? that is strange
[11:15:05] <hazzy-m> hohoho, you cant force push!
[11:15:19] <hazzy-m> not to that level yet :D
[11:15:22] <hazzy-m> hmm
[11:15:35] * Lcvette uploaded an image: IMG_20181206_111502427_HDR.jpg (25KB) < https://matrix.org >
[11:16:00] <Lcvette> padwan status
[11:16:12] <Lcvette> lol
[11:16:18] <hazzy-m> try doing a pull and see what happens
[11:16:25] <Lcvette> padwan panda status
[11:16:54] <Lcvette> merge conflicts that need to be resolved
[11:17:40] <hazzy-m> cancel
[11:18:09] <Lcvette> aborted
[11:18:18] <hazzy-m> git lab makes some things harder than it should be, sigh
[11:23:12] <hazzy-m> ok
[11:23:45] <hazzy-m> log into gitlab in the web browser
[11:23:58] <hazzy-m> go do your QtPyVCP repository
[11:24:08] <hazzy-m> to
[11:25:06] <hazzy-m> on the left hand side click settings > repository
[11:25:18] <hazzy-m> find the Protected Branches secction and click the expand button
[11:25:49] * hazzy-m uploaded an image: image.png (68KB) < https://matrix.org >
[11:26:05] <hazzy-m> click unprotect and you should be good
[11:31:49] <Lcvette> now push again?
[11:32:11] <hazzy-m> yes
[11:32:23] <hazzy-m> it should let you force push now
[11:35:18] <Lcvette> atill pushing
[11:35:23] <Lcvette> still
[11:36:42] <Lcvette> did it go through on your end?
[11:36:48] <hazzy-m> hurray!
[11:36:58] <hazzy-m> it worked!!!!!
[11:37:03] <Lcvette> nice!
[11:37:09] <Lcvette> i fu'd it
[11:37:10] <Lcvette> waaaaa
[11:38:00] <hazzy-m> a solution to that would have been to put you changes in a feature branch ...
[11:39:50] <hazzy-m> perfect, works great!
[11:40:02] <Lcvette> but the dro colors don't work anymore
[11:40:02] <Lcvette> :(
[11:40:08] <Lcvette> i busted them
[11:40:16] <hazzy-m> fixing those now
[11:40:20] <Lcvette> nice
[11:59:26] <Lcvette> ok, Lcvette must get some orders ready for pickup, back in a couople hours!
[12:28:28] <Not> [02QtPyVCP] 07Kurt Jacobson pushed 034 commits to 03master [+0/-0/±4] 13https://gitlab.com/Hazzy/qtpyvcp/compare/cf20f03fa7f0dfb7f7b272a18fb52daa5aa77b35...5b640878246e8b5427b794ea5e3bde0e9c54266e
[12:28:30] <Not> [02QtPyVCP] 07Lcvette 036f9b41e - fixed dros in main window copied hazzy's dros to main window dros so they work correctly
[12:28:31] <Not> [02QtPyVCP] 07Kurt Jacobson 03287422d - Merge remote-tracking branch 'Lcvette/master'
[12:28:33] <Not> [02QtPyVCP] 07Kurt Jacobson 0384efc04 - status for all spindles and joints
[12:28:34] <Not> [02QtPyVCP] 07Kurt Jacobson 035b64087 - VCP: fix ProbeBasic DRO homing indicators
[15:47:23] <Lcvette> hu8rray!!!!
[15:47:28] <Lcvette> you did it Hazzy!\
[15:47:35] <Lcvette> Hazzy rocks!
[15:48:28] * hazzy-m feels like an old man
[15:48:32] <hazzy-m> don't only old men rock?
[15:48:37] <hazzy-m> lol
[15:48:44] <Lcvette> hahaha
[15:48:54] <Lcvette> real men rock
[15:48:58] <Lcvette> of all ages
[15:49:08] <hazzy-m> haha
[15:49:25] <hazzy-m> making lost of progress on other things
[15:49:32] <Lcvette> where is jeff?
[15:49:44] <Lcvette> his step jog stuff is busted
[15:49:44] <hazzy-m> like custom dialogs
[15:49:57] <Lcvette> yeah?
[15:50:00] <hazzy-m> for Turbos's work offsets dialog
[15:50:08] <Lcvette> what
[15:50:24] <hazzy-m> don't know, he hasn't been around for a while
[15:50:35] <hazzy-m> he's been playing in his shop
[15:50:40] <Lcvette> yeah
[15:50:45] <Lcvette> im gonna instagram him
[15:50:45] <hazzy-m> working on that G0602 probably :D
[15:50:55] <hazzy-m> G0704*
[15:51:03] <Lcvette> or do you need to fix his stuff?
[15:51:09] <Lcvette> special
[15:51:17] <Lcvette> with your new fu
[15:51:28] <hazzy-m> yes, I broke a lot of his stuff
[15:51:38] <Lcvette> oih
[15:51:48] <hazzy-m> should be easy to fix but I don't wan't him to see I broke it
[15:51:49] <hazzy-m> lol
[15:52:18] <Lcvette> ok
[15:52:37] <Lcvette> leave turboss crap til later
[15:53:33] <Lcvette> he is splitting resources
[15:54:29] <Lcvette> build one then build many
[15:55:02] <hazzy-m> no, this will benefit you too!
[15:55:09] <hazzy-m> a lot
[15:55:16] <Lcvette> what is it
[16:06:22] <hazzy-m> global configurations
[16:06:56] <hazzy-m> it will make it possible for designer to automagicaly set everything up
[16:07:13] <hazzy-m> so you don't have to use ./launch_designer.sh anymore
[16:07:42] <hazzy-m> and will make using the QSS style sheets in designer much easier
[16:09:22] <Lcvette> Ugh I twr et out again
[16:09:26] <Lcvette> Internet
[16:09:44] <hazzy-m> you must have AT&T
[16:09:47] <Lcvette> Cable guy is here to try and fix
[16:09:57] <Lcvette> Spectrum time warner
[16:10:04] <Lcvette> When it works it's good
[16:10:23] <Lcvette> Last few days it's been horrible dropping in and out
[16:10:50] <hazzy-m> they don't have enough lines on our street to support everyone, so sombody is always without
[16:11:20] <hazzy-m> we droped one of the buessness lines which helped a bit
[16:11:20] <hazzy-m> lol
[16:11:45] <Lcvette> So now that the dros and eveythi g work with offsets etc, it's pretty close to being able to use o. The machine it would seem no?
[16:11:48] <Lcvette> Haha
[16:12:49] <hazzy-m> yeah, I think it should be useable at this point
[16:13:10] <hazzy-m> I fixed the jogging so that should work properly now too
[16:13:14] <Lcvette> Just need jog step
[16:13:23] <Lcvette> Hahaha
[16:13:31] <hazzy-m> right
[16:13:32] <hazzy-m> ok
[16:13:37] <hazzy-m> I'll get on it
[16:14:13] <Lcvette> Lolol
[16:14:19] <Lcvette> Hazzy is ahead of the game
[16:14:37] <Not> [02QtPyVCP] 07Kurt Jacobson created branch 03YMLConfig
[16:15:13] <Lcvette> Lcvette waits for a blip in the Internet for kraken to load
[16:18:50] * Lcvette sent a long message: < https://matrix.org >
[16:19:10] <Lcvette> error on last update when trying to load
[16:19:40] <hazzy-m> run
[16:19:45] <hazzy-m> `pip install ruamel.yaml`
[16:20:12] <hazzy-m> you are really staying on the cuttin edge :)
[16:21:14] <Lcvette> Which window
[16:21:20] <Lcvette> Terminalwindow
[16:21:26] <hazzy-m> anywhere
[16:21:29] <Lcvette> Any?
[16:21:34] <hazzy-m> yes
[16:22:13] * Lcvette sent a long message: < https://matrix.org >
[16:24:05] <hazzy-m> great
[16:24:09] <hazzy-m> now it should work
[16:24:21] <Lcvette> yup
[16:24:34] <Lcvette> any reason the steps are not stepping accurately?
[16:25:10] <hazzy-m> not that I know of
[16:25:16] <hazzy-m> more bugs?
[16:30:36] <Lcvette> I set it to step and moved away from zero like 3" and then back the result is worse with each step and on the way back to zero it stops at 0.0880" away from 0.000
[16:31:28] <hazzy-m> you are talking about setp jog mode or program step?
[16:31:49] <Lcvette> Mach3 would occasionally be off by a tenth or so but not by this much
[16:32:06] <Lcvette> Step jog
[16:32:40] <Lcvette> Program mode it's dead nuts
[16:33:25] <hazzy-m> I see
[16:33:33] <hazzy-m> another bug
[16:34:21] <hazzy-m> what is happening is when you click the button before the lase move has finished it aborts what was left of the previous move
[16:34:39] <hazzy-m> thanks ofr noticing that
[16:35:06] <Lcvette> Lol
[16:35:10] <Lcvette> Sorry
[16:35:20] <Lcvette> Big bug or little bug
[16:36:43] <hazzy-m> if you don't let go of the button untill the jog is done it works right
[16:36:49] <hazzy-m> should be easy to fix
[16:37:22] <Lcvette> Hey you are right
[16:38:33] <Lcvette> Also, when you select the jog button it doesn't disable the step mode
[16:38:46] <Lcvette> So if you go I to step mode you get stuck there
[16:38:55] <hazzy-m> lots of stuff in there is broke :(
[16:44:51] * Lcvette uploaded an image: image.png (52KB) < https://matrix.org >
[16:45:05] <Lcvette> something in here maybe?
[16:45:32] <Lcvette> i remember he had me go in here and do things
[16:45:33] <hazzy-m> could be
[16:45:35] <Lcvette> but i forget what
[16:45:41] <hazzy-m> I need to look into it
[17:05:36] <Lcvette> what is bool
[17:05:53] <hazzy-m> True/False
[17:06:05] <hazzy-m> 1/0
[17:32:36] <TurBoss> what I did
[17:33:55] <hazzy-m> hey!
[17:34:22] <TurBoss> Hello
[17:35:03] <TurBoss> new blender beta released
[17:35:08] <TurBoss> 2.80 beta
[17:35:56] <TurBoss> https://www.blender.org
[17:38:41] <hazzy-m> nice!
[17:39:02] <hazzy-m> new Qt LTS released too
[17:40:36] <TurBoss> great
[17:54:04] <Lcvette> internet fixed and moved closer to computers
[17:54:08] <Lcvette> see if that works
[18:00:47] <Lcvette> i think for the step and jog buttons the highlight for inactive is a wasted thing
[18:01:05] <Lcvette> it should just be click jog or step for which you want
[18:05:50] <Lcvette> ok i masnaged to do that
[18:06:16] <Lcvette> that works much better now
[18:06:24] <Lcvette> but now it is still getting stuck in step
[18:06:34] <Lcvette> even though it should be disabling
[18:14:59] <Lcvette> i think it is probably inside the deeper code
[18:15:16] <Lcvette> and not in the signals and slots commands perhaps
[18:15:35] <Lcvette> ive tried about every combination and not much is working
[18:16:32] <Lcvette> it is also odd that if you select step and do not select a step increment, that it remains in jog mode
[18:17:15] <Lcvette> i think it would be better suited to be consistently in a step increment even at startup as default so when step is pressed it is actually in step
[18:17:29] <Lcvette> and then the user can change the step increment
[18:20:27] <Lcvette> this makes much more sense to me... thoughts?
[18:27:56] <hazzy-m> I think that when put in setp mode a default step size should be set
[18:28:08] <hazzy-m> right, I agree
[18:29:12] <Lcvette> do i need to ask jeff
[18:29:46] <Lcvette> I'm not sure if thats a Jeff thing now or a Hazzy thing
[18:29:47] <Lcvette> lol
[18:30:13] <hazzy-m> it is probably a hazzy thing, jeff had it working, I broke it
[18:30:13] <hazzy-m> lol
[18:30:37] <Lcvette> i don't remember it ever being preset to a default step increment
[18:37:01] * Lcvette uploaded an image: image.png (206KB) < https://matrix.org >
[18:37:11] <Lcvette> i don't know this fu at all
[18:37:38] <hazzy-m> jeff wrote that
[18:37:55] <Lcvette> thats just sillyness
[18:38:01] <hazzy-m> its pretty easy once you learn it
[18:38:22] <hazzy-m> I'm just kidding you!
[18:38:22] <Lcvette> yeah
[18:38:23] <hazzy-m> LOL
[18:38:39] <Lcvette> i'll put that right up there next to ancient sandscript
[18:38:51] <hazzy-m> That is a byte compiled python code
[18:39:16] <hazzy-m> it is what python actualy runs
[18:39:35] <hazzy-m> you oppened the .pyc file instead of the .py file
[18:39:45] <hazzy-m> pyc => python compiled
[18:39:55] <Lcvette> ah
[18:40:15] <Lcvette> can't find the py file
[18:40:41] <hazzy-m> hmm
[18:40:44] <hazzy-m> checking
[18:41:11] <Lcvette> everything in my folders are pyc files
[18:41:20] <hazzy-m> it should be in input_widgets/jog_incruments.py
[18:41:22] <Lcvette> you locked lcvette out didn't you
[18:41:37] <hazzy-m> what?
[18:41:38] <hazzy-m> lol
[18:41:43] * Lcvette uploaded an image: image.png (104KB) < https://matrix.org >
[18:41:54] <hazzy-m> ahahahahahaa
[18:42:02] <Lcvette> yeah
[18:42:06] <hazzy-m> the folder names changed
[18:42:06] <Lcvette> no fu for you
[18:42:20] <hazzy-m> delete the QtPyVCP folder, everything it now in the qtpyvcp folder
[18:42:44] <hazzy-m> I try to keep you on your toes
[18:43:27] * Lcvette uploaded an image: image.png (133KB) < https://matrix.org >
[18:43:31] <Lcvette> more better
[18:45:05] * Lcvette uploaded an image: image.png (208KB) < https://matrix.org >
[18:45:21] <Lcvette> maybe this is the code portion that sets the increment?
[18:45:55] <hazzy-m> looks like it
[18:51:17] <Lcvette> i cant make sense of it
[18:53:00] <Lcvette> would i maybe just change one of the buttons to checked in the designer?
[18:53:11] <Lcvette> si its natural state nwould be a checked state?
[18:53:17] <Lcvette> hazzy?
[18:53:39] <hazzy-m> that may work
[18:53:48] <hazzy-m> certainly worth a try
[18:53:53] <hazzy-m> I need to look at the code
[18:54:12] <Lcvette> trying to channel my inner panda
[18:54:22] <Lcvette> WWHD
[18:54:40] <hazzy-m> lol
[18:54:53] <Lcvette> ah crap
[18:54:57] <Lcvette> they aren't buttons
[18:55:02] <Lcvette> its a widget as a unit
[18:55:07] <Lcvette> can't select buttons
[18:55:21] <hazzy-m> oh, I forgot
[18:55:36] <hazzy-m> ok, don't worry about it, I'll look
[18:55:41] <hazzy-m> eventualy
[18:55:45] <hazzy-m> 😃
[18:55:48] <Lcvette> but im playuing
[18:55:58] <Lcvette> and pestering you
[18:55:59] <hazzy-m> and learning!
[18:56:03] <Lcvette> lol
[18:56:26] <hazzy-m> no no. you are the least of my pestering worries
[18:56:38] <hazzy-m> you can't even compeat
[18:56:38] <hazzy-m> lol
[18:56:38] <Lcvette> there are like only a few small things to get dialed in and this could be put into use
[18:57:53] <Lcvette> then we turboss and I could finish the ATC and I could test some probe routines live
[18:57:59] <Lcvette> it would be glorious
[18:58:11] <Lcvette> champaign would rain from the heavens
[18:58:21] <hazzy-m> lol
[18:58:28] <Lcvette> we will youtube it and the mach3 forums would vacate
[18:58:31] <hazzy-m> yes! we are getting VERY close!
[18:58:47] <Lcvette> the linuxcnc servers would implode with new memberships
[18:59:00] <Lcvette> PCW would have a stroke from mesa sales
[18:59:21] <Lcvette> Hazzy would have a statue erected in his honor
[19:00:12] <Lcvette> and the world of CNC would never be the same
[19:17:26] <TurBoss> Lol
[19:18:03] <hazzy-m> LOL
[19:35:56] <Lcvette> true statements
[19:36:35] <Lcvette> it may be embelished..
[19:37:10] <Lcvette> but i would mail you champaign, and a lego man mounted on a pedestal with your name engraved on it at least
[19:37:13] <Lcvette> :D
[19:38:01] <Lcvette> there may be some truth to the mach3 crowd coming over to the linuxcnc side with an updated sweet sweet gui
[19:38:19] <Lcvette> that didn't have the stigma of requiring code fu to use like PP
[19:40:43] <hazzy-m> yea, I do think that the lack if good UIs so far has realy limited LCNC
[19:42:12] <Lcvette> my buddy who just downloaded linuxcnc to tour it and poke around was all excited because i had sent him the screen shots and told him how powerful linuxcnc was
[19:42:52] <Lcvette> he then sent me an email and said geez Chris, your screens are a spoiler.. everything i saw in linuxcnc after seeing them was a compolete let down
[19:43:38] <hazzy-m> not for long
[19:43:40] <hazzy-m> :D
[19:43:52] * Lcvette uploaded an image: image.png (30KB) < https://matrix.org >
[19:44:11] <Lcvette> hahaha
[19:45:19] <hazzy-m> haha!!!
[19:45:24] <hazzy-m> its true
[19:45:33] <hazzy-m> don't let jepler see that ...
[19:45:38] <hazzy-m> :D
[19:45:56] <Lcvette> Jepler made what was needed
[19:46:03] <Lcvette> a universal controller
[19:46:43] <hazzy-m> yes, he is extremely good at that stuff
[19:47:26] <Lcvette> but it just was very generic
[19:47:44] <Lcvette> and very cumbersome to modify
[19:47:44] <hazzy-m> and done a long time ago
[19:47:49] <Lcvette> unless you were another jepler
[19:48:13] <Lcvette> i removed them
[19:48:17] <Lcvette> xD
[19:48:47] <Lcvette> thatsb what i hated most about linuxcnc
[19:49:43] <Lcvette> the new stuff you are doing is better
[19:49:58] <Lcvette> but its still not for the end user type
[19:50:33] <Lcvette> but then you have to balance flexibility and ease of use
[19:51:20] <hazzy-m> it is a difficult compromise
[19:51:34] <Lcvette> same with anything
[19:51:53] <Lcvette> when i was buillding houses it was the same way
[19:52:32] <Lcvette> track building you cuold offer only so many floor plans and options before it began to get over complicated and the costs would shoot up
[19:52:51] <Lcvette> so you limit options to a smal pool for buyers
[19:53:03] <Lcvette> in doing so you shape the community basically
[19:53:24] <Lcvette> and you can build out a 500 home community in a year
[19:53:42] <Lcvette> try that in a golfcourse community with custom homes and its a 15 year project
[19:54:12] <Lcvette> homes take a year+ to complete
[19:54:18] <Lcvette> rather than 8 weeks