#hazzy Logs
Feb 13 2020
#hazzy Calendar
02:25 AM MrHindsight is now known as CaptHindsight
07:48 AM TurBoss: hello!
08:13 AM Lcvette: o/
08:13 AM Lcvette: morning
08:13 AM Lcvette: turboss, i am learning python
08:13 AM Lcvette: \o/
08:14 AM TurBoss: \o/
08:14 AM TurBoss: i saw!
08:15 AM Lcvette: but im not sure if what i learning is good because its pyton 3.6
08:15 AM Lcvette: the titorial
08:15 AM Lcvette: * the tutorial
08:17 AM TurBoss: its the same
08:17 AM TurBoss: only little changes
08:17 AM TurBoss: python 2.7 id ded
08:17 AM TurBoss: but youl be able to do that on 2.7
08:18 AM Lcvette: ok
08:24 AM Lcvette: your avatar changed!
08:25 AM Lcvette: \o/
08:25 AM Lcvette: its glowing blue now
08:29 AM TurBoss: :)
08:30 AM TurBoss: HD pixel
08:31 AM Lcvette: :D
01:53 PM Lcvette: im stuck on a macro for the programmable coolant nozzle
01:54 PM * Lcvette sent a long message: < https://matrix.org/_matrix/media/r0/download/matrix.org/NjjMxGHFkpFIRyDxUErNZkuV >
01:54 PM Lcvette: i amnot sure if i am getting the tool length offset value in time for a calculation
01:55 PM Lcvette: i can't find a parameter for getting a named tools length offset in the docs
01:55 PM Lcvette: anyone know?
01:57 PM Lcvette: i tried using H<#selected_tool> = #<toole_length_offset>
01:57 PM Lcvette: but it yelled at me for bad chanracter '='
01:57 PM Lcvette: * but it yelled at me for bad character '='
01:58 PM Lcvette: any ideas or thoughts, its my last hurdle to have this programmable coolant macros working i think
01:58 PM Lcvette: tubross or hazzy
01:58 PM Lcvette: ?
01:58 PM Lcvette: * turboss or hazzy
03:01 PM TurBoss: Lcvette: hey
03:01 PM Lcvette: o/
03:01 PM Lcvette: turboss is here!
03:01 PM Lcvette: hurray!
03:02 PM * TurBoss sent a long message: < https://matrix.org/_matrix/media/r0/download/matrix.org/KMdXbUvJepteTTXqzzxlLmRW >
03:03 PM * TurBoss sent a long message: < https://matrix.org/_matrix/media/r0/download/matrix.org/RmZCuMDBdBaypNdSvitftblD >
03:03 PM TurBoss: edited^^
03:03 PM TurBoss: something like that?
03:04 PM TurBoss: its missing <> symbols
03:04 PM Lcvette: the problem is getting the temp variable
03:04 PM Lcvette: it is the tool length offset number
03:05 PM TurBoss: its the same :o
03:05 PM TurBoss: im idiot
03:05 PM TurBoss: :D
03:05 PM TurBoss: do one operation each line
03:05 PM Lcvette: lol
03:06 PM Lcvette: i don't think the variable is being brought in
03:06 PM Lcvette: #<pc_tool_length> = #1
03:06 PM Lcvette: i don't think the box that is pulling from is yet populated
03:07 PM Lcvette: i need to find a way to be able to bring the tool length offset in
03:07 PM Lcvette: for a given tool
03:07 PM Lcvette: i tried it a few ways
03:07 PM Lcvette: including trying to grab it in the m6 subroutine
03:07 PM Lcvette: and bring it over
03:07 PM Lcvette: but i think that variable does not write until the macros is concluded
03:09 PM TurBoss: oh
03:09 PM Lcvette: turboss, i looked through the docs but did not see a variable either named or numbered that was the actual tool length offset number
03:09 PM Lcvette: unless i was not formatting it correctly
03:10 PM TurBoss: cant you print the values of #1 #2 #3?
03:11 PM Lcvette: how do you man?
03:12 PM Lcvette: print i where?
03:12 PM TurBoss: in console
03:12 PM TurBoss: from gcode
03:12 PM TurBoss: (print , 1 #1 )
03:13 PM * Lcvette sent a long message: < https://matrix.org/_matrix/media/r0/download/matrix.org/cgxvBhInarLWAzQKiKkQNPCX >
03:13 PM Lcvette: ?
03:14 PM TurBoss: does that work?
03:14 PM * Lcvette sent a long message: < https://matrix.org/_matrix/media/r0/download/matrix.org/eYfNEGKKFOvYDMNcQvyplUvC >
03:14 PM TurBoss: you said its not receiving the data in #3?
03:14 PM Lcvette: is it formatted correctly?
03:14 PM Lcvette: in #1
03:15 PM Lcvette: it receives it after the macro is completed but that messes up the angle calculation because its is not included in the calc when run
03:16 PM TurBoss: (debug,#1)
03:16 PM TurBoss: :/
03:22 PM * Lcvette uploaded an image: Screenshot_2020-02-13_16-15-09.png (114KB) < https://matrix.org/_matrix/media/r0/download/matrix.org/FCddiIxuxFozBPZrUkADnXIE >
03:24 PM Lcvette: the print is printing wrong numbers
03:25 PM TurBoss: brb
03:32 PM MrHindsight is now known as CaptHindsight
03:33 PM TurBoss: back
03:33 PM * Lcvette uploaded an image: Screenshot_2020-02-13_16-26-15.png (85KB) < https://matrix.org/_matrix/media/r0/download/matrix.org/YFuVmyPjMahxlOjlWdOfKFlW >
03:34 PM Lcvette: so it is bringing in the variable from the settings page, but the tool length offset like i suspected comes in as 0.000 because it is not yet populated
03:35 PM Lcvette: if i change tools, then it brings in the previous tools tool length offset and uses it in the calculation
03:36 PM * Lcvette uploaded an image: Screenshot_2020-02-13_16-28-31.png (3KB) < https://matrix.org/_matrix/media/r0/download/matrix.org/QounhBDFCwlGqIaXjSJbOqFd >
03:36 PM Lcvette: the calculation works but needs the tool length variable from the selected tool's length offset
03:40 PM Lcvette: so the issue is how to get the tool length offset of a given tool
03:40 PM Lcvette: can it be pulled from the tool table?
03:43 PM TurBoss: how?
03:43 PM Lcvette: I'm asking
03:48 PM Lcvette: or can it be pulled from the tool table file?
03:51 PM TurBoss: Lcvette: https://github.com/LinuxCNC/linuxcnc/blob/master/nc_files/tool-length-probe.ngc
03:51 PM TurBoss: what is #5063
03:51 PM Lcvette: 5061-5069 - Coordinates of a G38 probe result (X, Y, Z, A, B, C, U, V & W). Coordinates are in the coordinate system in which the G38 took place. Volatile.
03:52 PM TurBoss: oh ok
04:34 PM Lcvette: this is infuriating
04:34 PM Lcvette: :(
04:36 PM Lcvette: TurBoss: im also having trouble outputting a value tpo a status label
04:36 PM Lcvette: * TurBoss: im also having trouble outputting a value to a status label
04:36 PM TurBoss: how
04:37 PM Lcvette: sek im pushing
04:37 PM Lcvette: using debug
04:37 PM TurBoss: I'm not on dev
04:38 PM Not-c468: [02probe_basic] 07Lcvette pushed 031 commit to 03programmable_coolant [+2/-0/±9] 13https://git.io/JvWh6
04:38 PM Not-c468: [02probe_basic] 07Lcvette 03b4e747b - programmable coolant settings and subroutines start
04:38 PM Not-c468: [02probe_basic] 07Lcvette created branch 03programmable_coolant - 13https://git.io/JeDwL
04:38 PM * Lcvette sent a long message: < https://matrix.org/_matrix/media/r0/download/matrix.org/utgAERXcZERuRUwfDiORpqRS >
04:39 PM travis-ci: kcjengr/probe_basic#284 (programmable_coolant - b4e747b : Chris): The build passed.
04:39 PM travis-ci: Diff view : https://github.com/kcjengr/probe_basic/commit/b4e747b699a9
04:39 PM travis-ci: Build details : https://travis-ci.org/kcjengr/probe_basic/builds/650186170
04:39 PM TurBoss: brb dev
04:39 PM * Lcvette uploaded an image: Screenshot_2020-02-13_17-32-38.png (39KB) < https://matrix.org/_matrix/media/r0/download/matrix.org/YSUjjAoHxQxWqbTxSRgqmNdT >
04:40 PM Lcvette: seems like its setup correctly?
04:47 PM TurBoss: back on dev
04:47 PM Lcvette: hurray!
04:47 PM Lcvette: \o/
04:49 PM Lcvette: im testing on just regular probe basic
04:49 PM Lcvette: not atc
04:49 PM Lcvette: easier and faster
04:49 PM Lcvette: and is setup for 5 axis already
04:50 PM TurBoss: how do I
04:50 PM Lcvette: just open probe basic ti will be on the settings page already whe it opens
04:50 PM Lcvette: home the sim
04:50 PM Lcvette: then change a tool
04:51 PM Lcvette: watch the b axis dro
04:51 PM Lcvette: it will go to 24.xxx on first tool change
04:51 PM Lcvette: vecause there is no tool length offset being calculated in
04:51 PM Lcvette: if you change the tool to the same tool again then it calculates properly
04:52 PM Lcvette: the label not being populated corrextly is cakculated nozzle angle
04:56 PM * Lcvette uploaded an image: Screenshot_2020-02-13_17-48-57.png (47KB) < https://matrix.org/_matrix/media/r0/download/matrix.org/CLcYfzvycLverZupxdzohwZt >
04:56 PM Lcvette: :o
05:00 PM TurBoss: thats the end
05:01 PM Lcvette: i told it to print a variable
05:02 PM Lcvette: whoops, missed a> on the end
05:06 PM * Lcvette uploaded an image: Screenshot_2020-02-13_17-57-54.png (95KB) < https://matrix.org/_matrix/media/r0/download/matrix.org/KwbfFgSPnwzZmOtTlIclIHLf >
05:10 PM TurBoss: Lcvette: wich file is responsible?
05:10 PM Lcvette: there are two
05:11 PM * Lcvette uploaded an image: Screenshot_2020-02-13_18-03-46.png (141KB) < https://matrix.org/_matrix/media/r0/download/matrix.org/szLAMcVDswxORlBHPvOnKAqQ >
05:11 PM Lcvette: M6_tool_call_main_panel.ngc is the main call for the m6 g43 button on the lower main panel
05:11 PM Lcvette: and program_coolant.ngc
05:12 PM Lcvette: is the secondary sub called from within the first sub
05:13 PM TurBoss: in config/probe_basic/subroutines/m6_tool_call_main_panel.ngc
05:13 PM TurBoss: from where does #1000 come?
05:13 PM Lcvette: its arbitrary
05:13 PM Lcvette: its assigned a value in that line
05:14 PM Lcvette: i used to have it in the program_coolant.ngc
05:15 PM Lcvette: but i though i would try it in the main sub to see if the debug thing wouldn't work from the subcall inside the sub
05:15 PM Lcvette: can copy it back over to the program_coolant sub
05:16 PM Lcvette: but i had no luck there either
05:16 PM * Lcvette sent a long message: < https://matrix.org/_matrix/media/r0/download/matrix.org/ivdByUGNFcIqWaWPuSziLXMO >
05:16 PM Lcvette: this is how i had it before
05:22 PM Lcvette: is it making sense to you?
05:23 PM Lcvette: have any questions?
05:24 PM TurBoss: doesn't matter how much i break it still works
05:24 PM Lcvette: ?
05:24 PM TurBoss: I made 100 modifications
05:24 PM Lcvette: works there?
05:24 PM TurBoss: nothing changed
05:25 PM Lcvette: are you in the main panel and using the main panel?
05:25 PM Lcvette: for the tool changes
05:25 PM TurBoss: the bottom one?
05:25 PM TurBoss: yes
05:25 PM Lcvette: yes
05:25 PM Lcvette: if using the m6 main panel tool entry and m6 buttons you must use the associated sub routine
05:26 PM Lcvette: m6_tool_call_main_panel.ngc
05:26 PM Lcvette: and use bottom fixed panel tool entry and m6 buttons
05:26 PM TurBoss: so #1000 holds the returned value?
05:27 PM Lcvette: i dunno this is how you instructed me to set it up before
05:27 PM Lcvette: i just copied from the probing ones
05:27 PM * Lcvette sent a long message: < https://matrix.org/_matrix/media/r0/download/matrix.org/rLBmbobdmDitDDHFQpFTkUIo >
05:28 PM Lcvette: turboss
05:28 PM Lcvette: ^^^
05:28 PM Lcvette: this is from the working probe ones
05:28 PM TurBoss: :o
05:30 PM TurBoss: you have the order swaped
05:30 PM Lcvette: /o\
05:30 PM TurBoss: ```
05:30 PM TurBoss: #<coolant_abs_angle> = #1000
05:30 PM Lcvette: i uust saw it
05:30 PM Lcvette: changing
05:31 PM Lcvette: \o/
05:31 PM Lcvette: works
05:31 PM Lcvette: hurray!!!
05:31 PM * Lcvette uploaded an image: Screenshot_2020-02-13_18-24-16.png (23KB) < https://matrix.org/_matrix/media/r0/download/matrix.org/bRObnsmVDAJmWQkKBMNCgDvE >
05:31 PM Lcvette: so now how about the last thing with the tool offset?
05:32 PM TurBoss: \o/
05:32 PM Lcvette: \o/
05:32 PM Lcvette: but the tool offset thing is still broken
05:32 PM Lcvette: load pb and home and change tool
05:32 PM TurBoss: wait still celebrating
05:32 PM Lcvette: first tool change will always be 24.087
05:32 PM TurBoss: ok
05:33 PM Lcvette: hit the m6 buttons again
05:33 PM Lcvette: leave same tool
05:33 PM Lcvette: it then gives the correct angle
05:33 PM Lcvette: because the tool length offset is not reflected in the pc_tool_length status label when the calulation is run
05:34 PM Lcvette: i moved it as far down the m6 macro as i could
05:34 PM Lcvette: but it won't register in time for the program_coolant.ngc to have the right data in the calulation
05:34 PM Lcvette: make sense?
05:35 PM TurBoss: yes
05:35 PM TurBoss: wich file
05:36 PM Lcvette: It originates I. The m6 main panel file
05:36 PM Lcvette: And is passed to the ptogram_voolant.ngc file
05:37 PM Lcvette: Program_coolant.ngc*
05:37 PM Lcvette: It's passed in the [#5] variable
05:40 PM Lcvette: "{:.4f}".format(ch[0]) if ch[1] == 'in' else "{:.4f}".format(ch[0])
05:41 PM * Lcvette uploaded an image: Screenshot_2020-02-13_18-33-54.png (31KB) < https://matrix.org/_matrix/media/r0/download/matrix.org/NWwdlgqngdTFjEtGwgmQaLcM >
05:41 PM Lcvette: this is the label rule that populates the status label i am pulling the data from
05:42 PM Lcvette: but this isn't updated until the m6 macros completes
05:42 PM Lcvette: so how to get the tool length offset out of the table file or write the macros such that the m6 macro can complete before passing the data to the program_coolant.ngc macro
05:43 PM Lcvette: turboss ^^
05:43 PM TurBoss: 🤔
05:43 PM Lcvette: see the dilema?
05:44 PM Lcvette: 6 hours i have been trying to solve
05:44 PM Lcvette: /o\
05:45 PM Lcvette: i can pull in the selected too
05:45 PM Lcvette: * i can pull in the selected tool
05:45 PM Lcvette: but not its tool length offset
05:48 PM * Lcvette sent a long message: < https://matrix.org/_matrix/media/r0/download/matrix.org/RuhUobznbmpdxuvhSJgMtPcW >
05:48 PM Lcvette: turboss ^^^
05:49 PM Lcvette: http://linuxcnc.org/docs/2.8/html/config/python-interface.html
05:49 PM Lcvette: maybe this?
05:52 PM Lcvette: tooltable:selected_tool?zoffset
05:52 PM Lcvette: ?
05:52 PM Lcvette: we can get selected tool from the macro
05:52 PM Lcvette: but can python work in amacro?
05:53 PM Lcvette: i dunno
05:53 PM Lcvette: my python fu is beginner
05:54 PM Lcvette: just barely past hello world
05:54 PM Lcvette: :(
05:54 PM Lcvette: /o\
05:54 PM Lcvette: lol
05:54 PM TurBoss: config/probe_basic/subroutines/m6_tool_call_main_panel.ngc
05:54 PM TurBoss: there
05:54 PM TurBoss: where does 5 come from?
05:55 PM TurBoss: #5
05:55 PM Lcvette: the status label
05:55 PM Lcvette: the status label is called pc_tool_length
05:56 PM * Lcvette uploaded an image: Screenshot_2020-02-13_18-49-00.png (45KB) < https://matrix.org/_matrix/media/r0/download/matrix.org/LquCtaszurginoLQOITVLVuy >
05:56 PM Lcvette: it has the rule setup in it i posted above
05:56 PM Lcvette: turboss ^^^
05:56 PM Lcvette: but that label is not updated when it pulls the data
05:57 PM Lcvette: hence the issue
05:57 PM Lcvette: it pulls the data in fine its just from the previous tool length offset
05:57 PM Lcvette: so its bad data
05:58 PM Lcvette: thats why on startup it always pulls a 0
05:58 PM Lcvette: and why if you hit the m6 button again then the data it pulls had been updated on the previous m6 button press
05:59 PM TurBoss: so you ar using a statuslabel as holder for the data?
06:00 PM Lcvette: it is the only way i could think to get the tool offset
06:00 PM Lcvette: but it does not update in time for it to be useful
06:01 PM Lcvette: all i need is to be able to pull in the selected tools z offset
06:01 PM Lcvette: to use it in the angle calculation
06:04 PM * Lcvette posted a file: programmable_coolant_issue.mkv (6223KB) < https://matrix.org/_matrix/media/r0/download/matrix.org/RcXHcfkvfdSFYgRsvwmAYWbH >
06:05 PM Lcvette: turboss ^^^ made an explanation video maybe its clearer
06:05 PM TurBoss: i think I had an idea
06:05 PM Lcvette: :o
06:05 PM Lcvette: \o/
06:06 PM TurBoss: but is gone
06:06 PM Lcvette: /o\
06:06 PM TurBoss: use a component to write to hal
06:06 PM TurBoss: but component doesnt know
06:06 PM TurBoss: the tlo
06:07 PM Lcvette: i never anticipated this being an issue
06:07 PM Lcvette: lol
06:07 PM Lcvette: thought it would be a fairly simple macro to write
06:08 PM Lcvette: the tool table, are the fields accecible?
06:08 PM Lcvette: * the tool table, are the fields accessible?
06:08 PM Lcvette: hazzy o/
06:08 PM hazzy-m: Yo!
06:08 PM Lcvette: fearless leader is here
06:09 PM Lcvette: have a stumper for you
06:09 PM hazzy-m: Long time no chat lol
06:09 PM hazzy-m: Yeah?
06:09 PM Lcvette: yeah
06:09 PM hazzy-m: Nubby
06:09 PM Lcvette: how can i pull a tool length offset
06:09 PM hazzy-m: That kind of stump?
06:09 PM Lcvette: nub power
06:09 PM TurBoss: \o/
06:09 PM Lcvette: \o/
06:09 PM TurBoss: hi!
06:09 PM hazzy-m: TurBoss: hey!
06:10 PM Lcvette: scroll up an d watch the video
06:10 PM * hazzy-m still lives
06:10 PM Lcvette: it shows ther issue
06:13 PM hazzy-m: how far up?
06:13 PM hazzy-m: today?
06:13 PM hazzy-m: found it lol
06:13 PM Lcvette: 8 poists of mine
06:14 PM * Lcvette posted a file: programmable_coolant_issue.mkv (6223KB) < https://matrix.org/_matrix/media/r0/download/matrix.org/GtybEYiRQwHWBUDELuOsgFBY >
06:17 PM hazzy-m: ok, I see what the problem is, I think
06:17 PM Not-c468: [02probe_basic] 07Lcvette pushed 031 commit to 03programmable_coolant [+0/-0/±4] 13https://git.io/Jvlvv
06:17 PM Lcvette: i just pushed
06:17 PM Not-c468: [02probe_basic] 07Lcvette 0392b500f - fixed one issue but the tool offset issue remains
06:17 PM hazzy-m: what triggers the calculation of the new nozzle angle?
06:18 PM Lcvette: its a calll within another sub
06:18 PM Lcvette: the m6 g43 buttons and or the m6 remap toolchange.ngc will call it
06:18 PM Lcvette: they all call subroutine themselves and inside is the program_coolant.ngc sub
06:18 PM hazzy-m: ok
06:19 PM * Lcvette sent a long message: < https://matrix.org/_matrix/media/r0/download/matrix.org/UNcARloPlxHrBXlvHBJkHFXA >
06:19 PM Lcvette: this is the button call sub
06:19 PM * Lcvette sent a long message: < https://matrix.org/_matrix/media/r0/download/matrix.org/ocXlKkTjodLtSOwYClLpBTDH >
06:19 PM hazzy-m: I think the problem is that at the time the sub is called the tool has not been compleatly loaded so the TLO is wrong
06:19 PM Lcvette: this is the coolant calculation sub
06:19 PM Lcvette: correct
06:20 PM Lcvette: how can i get the tool offset prior to it populating the status label im pulling it from?
06:20 PM Lcvette: or how can i organize the macro such that it completes and updates the status label and then runs the program_coolant.ngc all from one button press
06:21 PM hazzy-m: your pulling the tool length from a label?
06:21 PM * Lcvette uploaded an image: Screenshot_2020-02-13_18-33-54.png (31KB) < https://matrix.org/_matrix/media/r0/download/matrix.org/VWqCvNOJGAbnUUcDiIFmWhQG >
06:21 PM Lcvette: yes with this rule in it
06:22 PM Lcvette: i don't know any other way to get at it
06:23 PM Lcvette: Can it be pulled from the tool table file?
06:24 PM hazzy-m: how about using #5401?
06:24 PM hazzy-m: I mean #5403
06:24 PM Lcvette: What's that?
06:25 PM hazzy-m: shouldn't that be the current tool length offset?
06:25 PM Lcvette: But it's happening during a tool change
06:25 PM Lcvette: That the issue at hand
06:28 PM * hazzy-m thinks that the angle of the nozzle shouldn't be controlled by gcode, but directly thru HAL, then your can use a slider to change the position while in the middle of a program
06:29 PM Lcvette: the issue is it is now pulling the current tool length offset but it is behind because the current tool is still the previous tool
06:29 PM hazzy-m: and won't the nozzle hit the ATC if it moves into position during the tool change?
06:29 PM Lcvette: no clue how to do that in hal
06:29 PM Lcvette: no
06:30 PM Lcvette: nozzle is on the other side of the head
06:30 PM hazzy-m: ok
06:30 PM Lcvette: i want this to be automatic
06:30 PM Lcvette: not on a slider
06:30 PM hazzy-m: yeah
06:30 PM hazzy-m: but you could have a slider to tweak its position
06:31 PM Lcvette: otherwise i could reach in and adjust by hand and that sucks
06:31 PM hazzy-m: you could still do that the way you are doing it though with external offsets
06:31 PM TurBoss: :/
06:31 PM Lcvette: can it run an axis while in auto mode?
06:31 PM hazzy-m: yes
06:31 PM Lcvette: i didn't think that wa spossible
06:31 PM hazzy-m: that is they I LOVE external offsets lol
06:32 PM hazzy-m: but I'm getting detracted
06:32 PM Lcvette: how can it be done?
06:32 PM Lcvette: im open for whatever works
06:32 PM Lcvette: this was just the way i figured i could do it
06:32 PM Lcvette: because i know macros more than hal
06:32 PM Lcvette: lol
06:32 PM Lcvette: but doesn't mean its a good way
06:33 PM Lcvette: lol
06:33 PM TurBoss: what a m66 and a hal comp waiting to toolchange begind finished
06:33 PM TurBoss: * what about m66 and a hal comp waiting to toolchange begind finished
06:33 PM Lcvette: i think the issue there would be that it won't finish until the subroutine is completed and this is happening inside that subroutine
06:33 PM hazzy-m: yes, or have it all in python and fired bu the tool in spindle signal ...
06:34 PM Lcvette: is there a way for a subroutine completing to call a second subroutine
06:35 PM TurBoss: idea!
06:35 PM Lcvette: \o/
06:35 PM TurBoss: there is allready a spindle pin
06:36 PM TurBoss: doesn't exist
06:37 PM * Lcvette uploaded a video: videoa28d805a-57cc-4407-947a-5c4b3915f6e0video.mp4 (1520KB) < https://matrix.org/_matrix/media/r0/download/matrix.org/dmOcaFcaXHZDYeguioItuOyb >
06:37 PM TurBoss: beebep
06:37 PM TurBoss: lol
06:38 PM Lcvette: lol
06:40 PM Lcvette: did we lose hazzy?
06:41 PM Lcvette: can we populate lots of labels with the tool table offsets?
06:41 PM Lcvette: would be hacky but that would work
06:43 PM Lcvette: maybe not
06:43 PM Lcvette: can't think of how to do it
06:43 PM Lcvette: :(
06:59 PM TurBoss: I think i did it
06:59 PM TurBoss: need halp
06:59 PM Lcvette: You did it?
07:00 PM Lcvette: What do you need?
07:01 PM TurBoss: this is temporal
07:01 PM TurBoss: add this to core hal
07:01 PM TurBoss: ```
07:01 PM TurBoss: net tlo motion.analog-in-30 <= halui.tool.length_offset.z
07:01 PM TurBoss: then
07:01 PM * TurBoss sent a long message: < https://matrix.org/_matrix/media/r0/download/matrix.org/XhlUkigsFkhCjEhQAgAouwud >
07:02 PM TurBoss: motion pin 30 is temporal
07:02 PM Lcvette: what line in hal t pu that line?
07:02 PM TurBoss: bot
07:02 PM TurBoss: last one
07:03 PM TurBoss: config/probe_basic/hallib/core_sim_5.hal
07:07 PM Lcvette: still broken
07:07 PM TurBoss: but does it print the right offset?
07:07 PM TurBoss: or the previous one?
07:08 PM Lcvette: no
07:08 PM Lcvette: previous
07:11 PM * Lcvette sent a long message: < https://matrix.org/_matrix/media/r0/download/matrix.org/sFNytedcnMaXNfKEWrrPFAwM >
07:12 PM * TurBoss uploaded an image: image.png (27KB) < https://matrix.org/_matrix/media/r0/download/matrix.org/QPHbTOebeoZXbmGJGfWOpmPv >
07:13 PM Lcvette: not tool would make it 90
07:13 PM Lcvette: :o
07:13 PM Lcvette: that pointing straight down
07:13 PM Lcvette: thats a calculation error
07:13 PM Lcvette: you need to put numbers in the other boxes
07:13 PM Lcvette: set first box to 1
07:14 PM Lcvette: set second box to 10
07:14 PM Lcvette: set 3rd box to 5
07:14 PM Lcvette: thay are used in calculations
07:14 PM Lcvette: must be non zero
07:15 PM * TurBoss uploaded an image: image.png (27KB) < https://matrix.org/_matrix/media/r0/download/matrix.org/buXBenDQFbGDjweXhZaVLURr >
07:15 PM TurBoss: Lcvette: ^
07:16 PM Lcvette: yes, but that box always updates at the end of the macro
07:16 PM Lcvette: im not getting those values
07:16 PM Lcvette: maybe im missing one of your changes?
07:16 PM * TurBoss uploaded an image: image.png (76KB) < https://matrix.org/_matrix/media/r0/download/matrix.org/aYsDvnEERakBZTlmDkyPegqY >
07:16 PM TurBoss: ops
07:16 PM TurBoss: yes
07:16 PM Lcvette: lol
07:17 PM * TurBoss sent a long message: < https://matrix.org/_matrix/media/r0/download/matrix.org/XxViYKzFqaEaetHJQdPPbRlT >
07:17 PM TurBoss: line 25
07:18 PM * TurBoss uploaded an image: tenor.gif (1233KB) < https://matrix.org/_matrix/media/r0/download/matrix.org/xpmIiulFvGgQWunToduFKjqY >
07:18 PM Lcvette: wargames
07:19 PM TurBoss: did work?
07:19 PM Lcvette: \o/
07:20 PM TurBoss: \o/!!???
07:20 PM Lcvette: \o/
07:20 PM Lcvette: hurray!
07:20 PM Lcvette: hows it work?
07:21 PM TurBoss: it whaits to tlo to be changed with m66
07:21 PM TurBoss: * it waits to tlo to be changed with m66
07:24 PM Lcvette: just updating the other m6 button subs
07:24 PM Lcvette: going to test all ofthem too
07:24 PM Lcvette: :D'
07:24 PM TurBoss: hurray!
07:24 PM TurBoss: pew pew
07:25 PM Lcvette: pew pew pew
07:25 PM Lcvette: where do i put that hal line in my machine hal file?
07:25 PM TurBoss: do you have motion pins?
07:25 PM * Lcvette sent a long message: < https://matrix.org/_matrix/media/r0/download/matrix.org/wwcTRoNxZeyWZVWZXvFITLOd >
07:26 PM TurBoss: at bottom
07:26 PM TurBoss: last line
07:26 PM TurBoss: choose a non collide pin number
07:26 PM TurBoss: 30 was an example
07:28 PM Lcvette: like mesa pins?
07:28 PM Lcvette: i did find and 30
07:28 PM Lcvette: it found none
07:31 PM TurBoss: any pin analog motion pin not used
07:32 PM TurBoss: and initialized
07:32 PM Lcvette: i will leave it at 30
07:32 PM TurBoss: oki
07:32 PM Lcvette: does that mean i have to change aio to 30?
07:32 PM TurBoss: yes
07:33 PM TurBoss: super cigar
07:33 PM Lcvette: can you check my hal; and tell me the number i can use?
07:33 PM Lcvette: yes smoke time
07:33 PM TurBoss: duno...
07:33 PM TurBoss: the last unused +1
07:36 PM Lcvette: Now I need to put it in tookchange.ngc
07:39 PM * Lcvette sent a long message: < https://matrix.org/_matrix/media/r0/download/matrix.org/oGXpHPALCgZfxVEpbZGHgkHP >
07:42 PM * Lcvette sent a long message: < https://matrix.org/_matrix/media/r0/download/matrix.org/hBBgpwqOQgffDNMoqdswlvHC >
07:42 PM Lcvette: look right?
07:42 PM TurBoss: phew
07:43 PM TurBoss: too long
07:43 PM Lcvette: copy and paste in text editor thats what i do
07:43 PM Lcvette: all i did was add these at the top
07:43 PM * Lcvette sent a long message: < https://matrix.org/_matrix/media/r0/download/matrix.org/mnhnDrdkYNoevRIfgUFbOvZu >
07:44 PM Lcvette: and this at the bottom
07:44 PM * Lcvette sent a long message: < https://matrix.org/_matrix/media/r0/download/matrix.org/BbYpvoIYviugZgloiNfORIQj >
07:44 PM TurBoss: what #13?
07:45 PM Lcvette: it activates the programmable coolant call
07:45 PM Lcvette: if 1 it runs the program_coolant.ngc macro
07:45 PM Lcvette: is 0 it skips it
07:45 PM TurBoss: but from where it comes?
07:45 PM Lcvette: set in the gui
07:45 PM TurBoss: ahhh
07:46 PM * Lcvette uploaded an image: Screenshot_2020-02-13_20-38-56.png (21KB) < https://matrix.org/_matrix/media/r0/download/matrix.org/ngZyvUjdHLOldrVlfuNWMQMC >
07:46 PM TurBoss: hmmm
07:47 PM Lcvette: i need to test in atc sim but it is not 5 axis
07:47 PM Lcvette: :o
08:11 PM Lcvette: lcvette is struggling to get the simulator to work with 5 axis
08:12 PM TurBoss: :)
08:15 PM TurBoss: hazzy: https://github.com/KDAB/GammaRay
08:16 PM Not-c468: [02probe_basic] 07Lcvette pushed 031 commit to 03programmable_coolant [+4/-0/±10] 13https://git.io/JvlJd
08:16 PM Not-c468: [02probe_basic] 07Lcvette 03857d13e - fix programmable coolant and try test on sim
08:20 PM Lcvette: can't test on atc sim bad character b because axis not setup
08:20 PM Lcvette: :(
08:20 PM Lcvette: meh
08:20 PM Lcvette: i guess i will test on the machine
08:21 PM Lcvette: not sure where to put the hal line in the atc sim hal
08:21 PM Lcvette: there are so many of them
08:21 PM Lcvette: lol
08:21 PM Lcvette: i think maybe vmc.hal
08:41 PM Lcvette: What's that link turboss
08:41 PM TurBoss: a debugger for Qt
08:43 PM Lcvette: Gammaray
08:43 PM Lcvette: It's good?
08:43 PM TurBoss: duno
08:43 PM Lcvette: We need it?
08:43 PM Lcvette: Ah
08:43 PM TurBoss: it will show properties signals and such on live
08:43 PM Lcvette: Oh cool
08:44 PM Lcvette: Like signals and slots etc?
08:44 PM TurBoss: maybe yes
08:44 PM Lcvette: Very cool
08:44 PM TurBoss: tryin to run
08:44 PM TurBoss: but no space left
08:44 PM Lcvette: Can see them happening
08:44 PM Lcvette: :o
08:44 PM TurBoss: I wiped al the pron but still nospace
08:45 PM Lcvette: Turboss ran out of hard drive?
08:45 PM TurBoss: dev is 60GB
08:45 PM TurBoss: lol
08:45 PM Lcvette: Turboss needs a 5tb ssd