#hazzy Logs
Oct 11 2019
#hazzy Calendar
01:37 AM cnccustoms[m]: Morning
01:37 AM cnccustoms[m]: I'm hoping someone can help me...
01:37 AM cnccustoms[m]: I've probably got a very old version of linuxcnc
01:37 AM cnccustoms[m]: Trying to update
01:38 AM cnccustoms[m]: But sudo apt update
01:38 AM cnccustoms[m]: Say apt command not found
01:38 AM cnccustoms[m]: What should I do?
01:38 AM cnccustoms[m]: Sudo apt-get update
01:39 AM cnccustoms[m]: Completed with many errors
02:15 AM cnccustoms[m]: Nevermimd.... I'm an idiot. I'm already on 2.7.14
02:21 AM Lcvette: Sudo apt-get update
02:21 AM Lcvette: If your on old version of Debian
02:22 AM Lcvette: cnccustoms: what are you updating?
02:23 AM cnccustoms[m]: Nermind
02:23 AM Lcvette: K
02:23 AM cnccustoms[m]: Lol
02:25 AM Lcvette: cd probe_basic
02:25 AM Lcvette: Got pull
02:25 AM Lcvette: git pull
02:25 AM Lcvette: cd qtpyvcp
02:25 AM Lcvette: git pull
02:26 AM Lcvette: cnccustoms: when you get a chance you need to update those by entering in main terminal
02:26 AM Lcvette: Has new offsets table
05:30 AM Tom_L: he needs debian 9 to do that
05:30 AM Tom_L: if he's on an old system it may be too slow
05:30 AM Tom_L: morning.
05:33 AM jthornton: morning
05:33 AM hazzy-m: morning
08:53 AM roguish[m]: good morning from a quite left coast.....
08:55 AM * JT-Shop2 makes a thermoforming thingy
09:22 AM Lcvette: morning
09:22 AM Lcvette: im trying to resolve the probing issue thaty it does not trip the machine to stop during non probing moves
09:22 AM Lcvette: seems the issue is not uncommon
09:23 AM Lcvette: was wondering if any of you knew of a solution?
09:42 AM jthornton: can you rephrase that? I don't understand what your saying
09:43 AM Lcvette: sorry..
09:46 AM Lcvette: when in a traversing move, for instance over the top of a part, if the user enters a stock width too short and the probe begins a downward positioning move before clearing the edge of the part, and the probe contacts the part top.. it does not stop..ie a crash
09:46 AM Lcvette: jthornton: ^^
09:47 AM Lcvette: i would think that any move with a probe tool loaded should stop when the probe is triggered as a safety
09:47 AM Lcvette: but this is not the case.
09:49 AM Lcvette: it seems the only time a probing trigger is recognized is during a probing G38.n move
09:52 AM Lcvette: there should be some way to have traversing or positioning moves have a safety stop and error message kicked out if the probe is triggered during a non G38.n in a probe routine
09:53 AM JT-Shop2: my machines have always stopped iirc when the probe is tripped but I may be wrong
09:53 AM JT-Shop2: linuxcnc would not know you have a probe loaded during a traverse or feed move
09:54 AM Lcvette: It was brought to my attention by Wanda who is testing and I was able to confirm on my machine
09:54 AM Lcvette: It does not stop
09:54 AM JT-Shop2: I'll go look while the glue dries on this part
09:54 AM Lcvette: Thank you
09:55 AM Lcvette: Is there a way to tell it?
09:55 AM Lcvette: In a routine
09:58 AM JT-Shop: tripping the probe during a homing routine stops the machine
10:00 AM JT-Shop: and it stops during a rapid move
10:01 AM JT-Shop: and it stops during a feed move is the probe is tripped
10:02 AM JT-Shop: how did you confirm that is does not stop if the probe is tripped? I can't reproduce that
10:05 AM cnccustoms[m]: What I have found is that it does not stop movement if a move other thst probe move is commanded while the probe is tripped.
10:05 AM cnccustoms[m]: It doesn't allow a probe move to happen though
10:05 AM JT-Shop: every move I tried including running a program stops the machine the moment the probe is tripped
10:06 AM cnccustoms[m]: Also... If the probe changes state during the rapid or jog or other move, Linux send out a signal. To either stop or just send an error message
10:06 AM Lcvette: JT-Shop: JT-Shop during the probing routines it didn't stop when triggered fitting a non probing move
10:06 AM cnccustoms[m]: Yeah... It's when the probe changes state that something happens
10:07 AM cnccustoms[m]: Mine doesn't stop during other moves either... Which is fine by me since the probe I'm using is in tripped. Mode when the probe is off
10:08 AM cnccustoms[m]: I'm not sure if it is supposed to stop motion... I always hear the Haas guys talk about a protected move and a non protected move
10:09 AM cnccustoms[m]: How is the state changed in Linux from non protected to protected?
10:10 AM cnccustoms[m]: There must be a setting since we are getting different results
10:10 AM JT-Shop: Lcvette: not sure how you managed that but it stops the machine for every type of move I tried and I can't reproduce what you got
10:10 AM Lcvette: In auto mode?
10:11 AM Lcvette: It is during a routine
10:11 AM Lcvette: Maybe it's because your tripping in mdi or manual mode so the jogging protection works?
10:11 AM Lcvette: JT-Shop: ^^^
10:12 AM JT-Shop: I tried mdi, program, and homing
10:12 AM JT-Shop: not tried manual jogging
10:12 AM JT-Shop: trips in manual jog as well
10:12 AM JT-Shop: everything I tried trips with an error and the machine stops
10:13 AM Lcvette: maybe your probe is setup differently?
10:13 AM Lcvette: i dunno maybe yuou have the secret method to avoid the crash?
10:13 AM JT-Shop: it's just setup normally AFIK
10:14 AM Lcvette: https://paste.ubuntu.com/p/4wsjtZ7gkJ/
10:15 AM Lcvette: line 65 or 81 would be the move it fails to stop once triggered
10:15 AM Lcvette: maybe i did something wrong in the way i wrote the move?
10:15 AM Lcvette: but it works otherwise?
10:16 AM Lcvette: well thats odd
10:16 AM JT-Shop: looks normal to me
10:17 AM Lcvette: have three people saying it doesn't stop after testing and 1 saying that it stops any time its triggered
10:17 AM Lcvette: what a mess
10:17 AM cnccustoms[m]: Could be the way the probe is linked in the hal
10:18 AM cnccustoms[m]: I can't see now but I think it's linked to motion and something else...
10:18 AM cnccustoms[m]: Maybe the way it is linked affects how a trip is hamdled
10:18 AM JT-Shop: the probe should just be connected to the probe input
10:19 AM JT-Shop: anything else in the way could mask the input
10:19 AM Lcvette: https://paste.ubuntu.com/p/dKBb4NFTqQ/
10:19 AM cnccustoms[m]: Yeah... But the probe input is linked in the Hal to motion
10:19 AM Lcvette: there is my hal file, line 84 is my probe
10:20 AM Lcvette: ```net estop-ext <= hm2_7i92.0.7i76.0.3.input-21
10:20 AM Lcvette: # --- PROBE-IN ---
10:20 AM Lcvette: net probe-in <= hm2_7i92.0.7i77.0.0.input-15-not
10:20 AM cnccustoms[m]: Look down at 478
10:20 AM cnccustoms[m]: Mine is similar to yours
10:21 AM Lcvette: ```net coolant-flood <= iocontrol.0.coolant-flood
10:21 AM Lcvette: # ---probe signal---
10:21 AM Lcvette: net probe-in => mot
10:21 AM cnccustoms[m]: JT-Shop: yours may be different
10:21 AM Lcvette: ```net coolant-flood <= iocontrol.0.coolant-flood
10:21 AM Lcvette: # ---probe signal---
10:21 AM Lcvette: net probe-in => motion.probe-input
10:22 AM Lcvette: i have bnoth of those in my hal
10:22 AM cnccustoms[m]: Yup needs to be that way
10:22 AM JT-Shop: net probe-in motion.probe-input <= hm2_5i25.0.7i77.0.0.input-13-not
10:22 AM cnccustoms[m]: Link single to probe... Link probe to motion in Linux... Well that's the way I understand it
10:23 AM cnccustoms[m]: May be way off
10:23 AM JT-Shop: that's my probe line
10:23 AM Lcvette: what version were you testing JT-Shop
10:23 AM Lcvette: maybe its a version thing
10:23 AM JT-Shop: 2.8 or master dunno
10:23 AM Lcvette: my issue was on 2.9
10:23 AM Lcvette: ok
10:23 AM cnccustoms[m]: Look firther down in your Hal... The motion. Probe-input must be linked to motion or something somewhere... Do a search
10:25 AM JT-Shop: I'm running 2.8
10:25 AM * Lcvette sent a long message: < https://matrix.org/_matrix/media/r0/download/matrix.org/EUmEFAJfgQQBUrIlpiyFxQWq >
10:26 AM Lcvette: i saw on the forum there are others experiencing the same and this was pointed too
10:26 AM cnccustoms[m]: But what does it mean?
10:26 AM cnccustoms[m]: Lol
10:27 AM Lcvette: i don't know
10:27 AM Lcvette: maybe motion.motion−type OUT S32 can be used to tell linuxcnc when the move is a traversing move with probe?
10:27 AM Lcvette: or maybe that it is probing ?
10:28 AM Lcvette: dunno hal well enough to know
10:28 AM Lcvette: maybe JT-Shop can shed some light on it
10:29 AM Lcvette: https://forum.linuxcnc.org/10-advanced-configuration/29775-figuring-out-what-kind-of-move-is-being-executed
10:29 AM Lcvette: jt replied in there too
10:29 AM Lcvette: lol
10:29 AM Lcvette: he is everywhere
10:29 AM Lcvette: linuxcnc ninja
10:31 AM jthornton: the probe input should only be connected to one pin motion.probe-input
10:33 AM Lcvette: That's all mine is connected
10:33 AM Lcvette: Oh wait
10:34 AM * Lcvette sent a long message: < https://matrix.org/_matrix/media/r0/download/matrix.org/zsuoVUErQJsgONWtTKeFlNNY >
10:35 AM Lcvette: So I need to combine like youra
10:38 AM jthornton: no, that works as well but it is harder to read for humans, I prefer to have it all on one line but hal does not care it connects all the pins to the signqal
10:39 AM JT[m]: I'm running 2.9 over here on this pc and can test when I get home from town with a sim
10:39 AM Lcvette: ok
10:39 AM Lcvette: thanks JT
10:40 AM Lcvette: it would never be an issue for me because i know the parameters and how to use but this could cause some problems for those starting as has been shown
10:40 AM jthornton: indeed
10:44 AM Lcvette: im changing my probe to match your jt and will test
10:44 AM Lcvette: ```net estop-ext <= hm2_7i92.0.7i76.0.3.input-21
10:44 AM Lcvette: # --- PROBE-IN ---
10:44 AM Lcvette: net probe-in motion.probe-input <= hm2_7i92.0.7i77.0.0.input-15-not
10:45 AM cnccustoms[m]: Now a question... My probe issues a tripped signal when off... But I want to use a tool setter as well. How would I do that. Since the tool setter would be on always but should be tripped of course when the tool touches it?
10:45 AM cnccustoms[m]: How that made sense?
10:46 AM jthornton: you could do that in hal and a selector to select which input to use
10:46 AM Lcvette: not very
10:47 AM cnccustoms[m]: Sounds way above my pay grade
10:54 AM hazzy-m: If you used a subroutine for the tool deter you could set a digital output to tell some HAL logic what probe you were trying to use
10:55 AM cnccustoms[m]: OK cool
10:56 AM cnccustoms[m]: Do I connect both pins to motion?
10:56 AM cnccustoms[m]: So say probe on pin 17 and setter on pin 19.... And bother to motion?
10:56 AM cnccustoms[m]: How to do Hal logic though?
10:57 AM cnccustoms[m]: I'm stupid 😁
10:57 AM Lcvette: cnccustoms: post on the linuxcnc irc, there is a larger pool there
10:58 AM Lcvette: i am sure people already have it done with examples
10:58 AM cnccustoms[m]: 👍
10:58 AM Lcvette: may be easier to learn by seeing
10:58 AM Lcvette: at least i find it is
11:03 AM * Lcvette sent a long message: < https://matrix.org/_matrix/media/r0/download/matrix.org/vTovQWEemweuztAvcOhvofcB >
11:04 AM Lcvette: would that work?
11:04 AM Lcvette: touch probe on 15 and tool setter on 14?
11:04 AM Lcvette: cnccustoms: hazzy
11:05 AM Lcvette: for touch probe and tool setter?
11:20 AM Lcvette: thats confusing
11:20 AM Lcvette: or cornfusing as JT would say
11:20 AM Lcvette: lol
11:21 AM Lcvette: do they not have another input for toolsetterdifferent than probe?
11:21 AM Lcvette: sure would simplify things
11:25 AM Lcvette: cnccustoms:
11:25 AM * Lcvette sent a long message: < https://matrix.org/_matrix/media/r0/download/matrix.org/JlSGeShUzYXfKwdyNSksxzZO >
11:25 AM Lcvette: https://forum.linuxcnc.org/38-general-linuxcnc-questions/35861-tool-length-sensor-and-touch-probe-with-mesa7i76e?start=0
11:28 AM Lcvette: that what you were looking for?
11:35 AM cnccustoms[m]: going to have a read
11:39 AM Lcvette: looks like you would need to change the length-in from not to regular
11:39 AM * Lcvette sent a long message: < https://matrix.org/_matrix/media/r0/download/matrix.org/BKiRLswWFKnWveRZsLISJRdP >
11:40 AM cnccustoms[m]: problem with the above is that the signal is taken from either probe or setter. Will not work for our wireless probe since when the probe is off, thesignal is tripped. So I would not be able to give a probe instruction to linuxcnc for the setter. What is needed is to ignore the probe signal when I want o do a toollength probe on the setter
11:42 AM Lcvette: yeah dunno then
11:42 AM Lcvette: maybe post in that thread
11:42 AM Lcvette: or call for andy on the linuxcnc board
11:42 AM Lcvette: maybe he can show you how to alter whats there
11:43 AM Lcvette: to do what you need
11:44 AM Lcvette: is that above not using two different inputs?
11:44 AM Lcvette: 04 and 05
11:44 AM Lcvette: so wouldn't it know which the signal is coming from?
11:44 AM Lcvette: \o/
11:45 AM Lcvette: turboss is here!
11:45 AM TurBoss: hello
11:45 AM Lcvette: hello
11:45 AM Lcvette: \o/
11:45 AM Lcvette: how is turboss today?
11:45 AM TurBoss: nice
11:45 AM TurBoss: fine
11:45 AM TurBoss: i mean
11:45 AM Lcvette: carrillos?
11:45 AM Lcvette: :D
11:45 AM TurBoss: xD
11:57 AM Lcvette: turboss, i am trying to figure out why probe does not stop machine when making a non probing move
11:57 AM Lcvette: the issue that wandoo brought to my attentions
11:57 AM Lcvette: stop machine when triggered
11:58 AM Lcvette: ie cause a crash
11:58 AM TurBoss: hmmmmmmmmmmmmmmmmmmmmmm
12:00 PM TurBoss: so it moved but doest stop if not touch?
12:00 PM Lcvette: yes when making a non g38.n move
12:00 PM JT[m]: 2.9 does just like 2.8 and 2.7 motion stops if the probe is tripped during a non probe move
12:01 PM Lcvette: JT: then im lost because it is not stopping in probe basic
12:01 PM TurBoss: he uses metric?
12:01 PM JT[m]: but the third time I just tried and it keeps going so something is broken in 2.9
12:01 PM Lcvette: yeah but it is happening in both inch and metric
12:01 PM Lcvette: \o/
12:01 PM Lcvette: im not crazy
12:02 PM JT[m]: and axis locked up
12:02 PM Lcvette: :o
12:02 PM JT[m]: there is no reason to 2.9 AFAIK unless you like suprises
12:03 PM Lcvette: i tried in 2.8 with same result
12:03 PM Lcvette: put in my old HDD from the other day of testing
12:03 PM Lcvette: that install installs 2.8 not 2.9
12:03 PM TurBoss: > there is no reason to 2.9 AFAIK unless you like suprises
12:03 PM TurBoss: very true
12:04 PM TurBoss: hmmm
12:04 PM Lcvette: but i will test again
12:04 PM Lcvette: to verify
12:04 PM * JT[m] uploaded an image: Screenshot at 2019-10-11 11-57-53.png (115KB) < https://matrix.org/_matrix/media/r0/download/matrix.org/JCHihApJloZriAOoUpKnZDyd >
12:04 PM JT[m]: now it works as expeced
12:04 PM JT[m]: that first one is a keyboard jog
12:06 PM Lcvette: https://github.com/LinuxCNC/linuxcnc/issues/368
12:06 PM Lcvette: i had found this last night
12:06 PM Lcvette: but it was rom 2017
12:09 PM JT[m]: Lcvette: it does not stop when running a program, that may be a feature in 2.9
12:09 PM Lcvette: guessing an ngc routine is a program
12:09 PM Lcvette: ?
12:09 PM Lcvette: so currently no solution
12:10 PM Lcvette: :o
12:10 PM JT[m]: yes use 2.8
12:11 PM Lcvette: 2.8 stops during sa program?
12:12 PM jthornton: that's what I have on the mill but let me double check
12:13 PM Lcvette: K
12:19 PM Lcvette: turboss can you help with the cycle timer?
12:21 PM TurBoss: sure
12:21 PM Lcvette: tom_l found some stuff but i read it and wasn't sure how to implement
12:23 PM Lcvette: https://doc.qt.io/qt-5/designer-widget-mode.html#
12:23 PM Lcvette: http://linuxcnc.org/docs/2.8/html/man/man9/time.9.html
12:24 PM JT-Shop: Lcvette: 2.8 does not stop when running a program
12:24 PM Lcvette: thats what my experience was too
12:24 PM Lcvette: so no current solution
12:24 PM Lcvette: probe_basic requires 2.8 or 2.9 but neither stop while running a program
12:26 PM Lcvette: thats a problem
12:26 PM Lcvette: and appears its been a problem for a while
12:26 PM Lcvette: so probably no solution soon to come
12:26 PM Lcvette: wonder if there is a work around
12:27 PM Lcvette: can i use G38.n moves for positioning where it won't error out if no probe trigger is received before end of positioning move?
12:28 PM JT-Shop: G38.3 - probe toward workpiece, stop on contact
12:28 PM JT-Shop: G38.2 - probe toward workpiece, stop on contact, signal error if failure
12:28 PM JT-Shop: yes
12:28 PM Lcvette: ok so change the G1 moves to G38.3
12:29 PM Lcvette: and the rapid moves i guess too
12:30 PM Lcvette: going to test now
12:31 PM TurBoss: \o/
12:31 PM * TurBoss will take a look at cycle_time in a moment
12:32 PM Lcvette: \o/
12:32 PM Lcvette: hurray!
12:32 PM Lcvette: lcvette will try and get probing safe
12:32 PM Lcvette: but wil;l be here with you
12:36 PM TurBoss: don't worry I have to finish som other stuff first
12:52 PM Lcvette: Ok
12:57 PM JT-Shop: 2.7 works the same way while running a program a probe input does not stop the program
12:57 PM JT-Shop: I guess it's been that way forever
12:59 PM Lcvette: Hmmm.. that needs a solution considering probe routines are programs
01:02 PM Lcvette: But I supposeif g38.3 works in my edited routine testing I can just change all non probing moves to g38.3
01:03 PM hazzy-m: Weve had this discussion in devel many times, and the consensus is probe trip while jogging should stop, but not while running a program
01:04 PM Lcvette: I would think while probing at all program or not it should stop
01:04 PM Lcvette: Crash prevention
01:04 PM Lcvette: What's the benefit to not having it stop?
01:05 PM Lcvette: Besides failing to safeguard what could potentially be a very 3xpensive probe
01:06 PM Lcvette: Crash a $100-150 probe it stings, but someone using a high end probe... Man that would be a big hurt
01:06 PM Lcvette: So why was the concensus to not stop it in a program during a non g38.n move with an error?
01:07 PM Lcvette: What purpose?
01:20 PM hazzy-m: The reasoning is that most people who have high end probes have an ATC, and probes tend to trip each time the ATC indexes. Probes also tend to trip erroneously during G0 moves, which if it resulted in an estop each time you tried to rapid would make probing only possible at low speeds
01:25 PM Not-5e4d: [02qtpyvcp] 07TurBoss created branch 03timmer_plugin - 13https://git.io/fhCou
01:25 PM Not-5e4d: [02qtpyvcp] 07TurBoss created branch 03timmer_plugin 13https://git.io/Jela6
01:25 PM Not-5e4d: [02qtpyvcp] 07TurBoss pushed 031 commit to 033D_PLOT [+0/-0/±1] 13https://git.io/Jelai
01:25 PM Not-5e4d: [02qtpyvcp] 07TurBoss 0372c0ae3 - initial data to zero
01:27 PM travis-ci: kcjengr/qtpyvcp#1119 (timmer_plugin - 6873758 : TurBoss): The build passed.
01:27 PM travis-ci: Diff view : https://github.com/kcjengr/qtpyvcp/compare/timmer_plugin
01:27 PM travis-ci: Build details : https://travis-ci.org/kcjengr/qtpyvcp/builds/596725431
01:31 PM Lcvette: TurBoss: you did it?
01:31 PM Lcvette: \o/
01:31 PM TurBoss: no
01:31 PM TurBoss: fail push
01:31 PM Lcvette: hazzy: good point
01:31 PM TurBoss: empty branch
01:31 PM Lcvette: the solution it seems is to use a g38.3 as i just tested and it stops the machine when tripped
01:34 PM Lcvette: TurBoss: ah
01:34 PM TurBoss: i found a clock plugin
01:34 PM Lcvette: \o/
01:42 PM hazzy-m: Tormach solved the problem by adding another Goode to set wether probe trip would cause an error
01:43 PM Lcvette: guessing that was the g38.6
01:43 PM Lcvette: it appears i can use g38.3 in the same manner
01:44 PM Lcvette: and i guess we need to add a box for traverse speed so i can change the G0 rapid traverse moves to g38.3 with a feed speed
01:45 PM Lcvette: its a solution, but gonna make a mess of the parameters page
01:45 PM Lcvette: meh
01:50 PM jthornton: could you remap a g code to do that?
01:51 PM jthornton: G0.1 maybe a rapid to position with probe in spindle
01:58 PM Lcvette: i don't know
01:59 PM Lcvette: jthornton: i only know what i do in ngc
01:59 PM Lcvette: lol
01:59 PM Lcvette: that would be great
02:09 PM Lcvette: lcvette goes to harbor freight
02:09 PM Lcvette: anyone need anything?
02:09 PM Lcvette: :D
02:10 PM Lcvette: lcvette is buying a little 36" sheetmetal brake cause he's tired of bending crap with a hammer and vise
02:10 PM Lcvette: back in a bit
02:11 PM Lcvette: he may even try and modify it to be a box and pan brake
02:11 PM Lcvette: :o
02:18 PM JT-Shop: which brake?
02:20 PM Lcvette: the red one
02:20 PM JT-Shop: can't see it from here lol
02:20 PM Lcvette: https://www.harborfreight.com/36-in-metal-brake-with-stand-62518.html
02:21 PM Lcvette: have a 25% coupon!
02:21 PM JT-Shop: what thickness are you bending?
02:21 PM Lcvette: $192.15 after tax and coupon
02:22 PM Lcvette: nothing thicker then 11 gauge aluminum
02:22 PM Lcvette: .059 maybe in mild steel
02:22 PM * Lcvette sent a long message: < https://matrix.org/_matrix/media/r0/download/matrix.org/ZMJoMOnVJRpZYXpziEWxlUUu >
02:23 PM JT-Shop: read the specs in the manual
02:25 PM JT-Shop: https://www.grizzly.com/products/Grizzly-48-Pan-Box-Brake-12-Gauge/G0542
02:25 PM * Lcvette sent a long message: < https://matrix.org/_matrix/media/r0/download/matrix.org/IyHMWcuPtyFysJaUVoGtXPLG >
02:25 PM JT-Shop: I have that one and it takes two guys to bend 11gauge with it lol
02:25 PM Lcvette: aluminum?
02:25 PM JT-Shop: mild steel
02:25 PM Lcvette: big difference there
02:25 PM Lcvette: lol
02:26 PM Lcvette: aluminum is soft
02:26 PM JT-Shop: that one you listed doesn't even do 11 gauge
02:26 PM Lcvette: it will
02:26 PM Lcvette: my buiddy has one and i run to his place from time to time to bend things that would not fit in the vise
02:26 PM Lcvette: but its a pain because he is only around in the evenings
02:27 PM Lcvette: i would love a big boy like that one you listed but i just can't afford a purchase like that right now
02:28 PM Lcvette: we just had new roads put in and the assessment is outrageous and now they want to help the community in front of ours get the main entrance road updated to DOT spoecs so the state can take it over and thats another expense we were not expecting all in all about $6k
02:28 PM Lcvette: could have been a nice brake and shear
02:28 PM Lcvette: and a vacation
03:55 PM Tom_L: man what a day.
04:01 PM JT-Shop: hows that
05:20 PM Tom_L: just busy
05:39 PM Lcvette: got the bender home and assembled but got called to the dinner table before i could adjsut and test
05:40 PM Tom_L: you see jt's bender?
05:41 PM Lcvette: thats monster bender
05:41 PM Tom_L: everything he does is supersized
05:42 PM Lcvette: lol
05:52 PM Tom_L: when he runs out of room he just adds on a new wing
05:54 PM Not-5e4d: [02qtpyvcp] 07TurBoss pushed 031 commit to 033D_PLOT [+0/-0/±1] 13https://git.io/JelK8
05:54 PM Not-5e4d: [02qtpyvcp] 07TurBoss 03a5641ed - draw axes on the active offset
05:55 PM TurBoss: fixed some issues on the vtk 3d plot but stil bugged when using offsets
05:56 PM Tom_L: TurBoss can the linuxcnc comps be accessed thru qtpyvcp?
05:56 PM Tom_L: or just the hal pins?
05:56 PM Lcvette: \o/
05:57 PM TurBoss: not sure Tom_L
06:47 PM jthornton: if the component creates a pin yes
06:54 PM TurBoss: so vtk works fine
06:54 PM TurBoss: until you restart with a offset in place
07:01 PM TurBoss: its wierd because the origin is drawn correctly
07:17 PM * Lcvette posted a file: VectorVideo_2019-10-11_081056.mp4 (3KB) < https://matrix.org/_matrix/media/r0/download/matrix.org/SpwLuTACoNNwdTHuoktgnHNt >
07:17 PM * Lcvette uploaded an image: VectorImage_2019-10-11_081129.jpg (133KB) < https://matrix.org/_matrix/media/r0/download/matrix.org/uTZPtZWXoXThmEgyWwOZpCph >
07:18 PM Lcvette: Good little brake for the money, got an extra 10% off because the crate was smashed and it was the last one left
07:18 PM Lcvette: $166 out the door
07:19 PM jthornton: can't beat that
07:19 PM Lcvette: \o\/o/
07:19 PM Lcvette: See a few places that will need beefing up for full length b2nds but easy enough to fix
07:20 PM jthornton: maybe some longer handles dunno but they look a bit on the short side
07:21 PM Lcvette: Yup
07:21 PM Lcvette: Needs a longer handle set
07:22 PM jthornton: I'm stuffed, we went to the new Chinese place and they had so much to try I ate too much
07:23 PM Lcvette: No worries you'll be hungry again in an hour
07:23 PM Lcvette: So it is with Chinese food
07:23 PM Lcvette: Lol
07:23 PM jthornton: I'll be asleep in an hour
07:23 PM roguish[m]: jthornton: do you ship out on Saturday?
07:24 PM roguish[m]: to Calli
07:25 PM jthornton: world wide and yes usually ship Saturdays
07:25 PM Lcvette: jthornton: to g some water to bed
07:25 PM jthornton: whatchaneeding
07:25 PM Lcvette: You'll wake thirsty in the middle of the night
07:25 PM roguish[m]: jthornton: 6i24-16
07:25 PM jthornton: I'm drinking vino...
07:25 PM jthornton: got one
07:25 PM roguish[m]: yur site says in stock.
07:26 PM jthornton: yep I keep one in stock
07:28 PM jthornton: and I always deliver to the po before the pick up deadline so it hits the distribution center the same day
07:28 PM jthornton: saves a day in transit
07:30 PM Lcvette: jthornton: is there an Fword that can be used in an ngc file for rapid speed
07:31 PM jthornton: no
07:32 PM jthornton: rapid is move at maximum rate, feed is move at the speed set by Fn
07:32 PM Lcvette: yeah
07:33 PM Lcvette: trying to find a way to move at the machines rapid while using G38.3
07:33 PM jthornton: F
07:33 PM Lcvette: just F?
07:33 PM jthornton: plus the speed you want to move
07:34 PM Lcvette: i don't know what everyones machine rapid will be
07:34 PM jthornton: they would have to set it and that's a good idea to have them set how fast they want to move during the probing operation
07:34 PM Lcvette: gonna look now to see if i can pull max_velocity out of parameter maybe
07:34 PM TurBoss: F is cool
07:34 PM TurBoss: \o/
07:34 PM jthornton: they may want to go F1 the first time just so they have time to stop
07:35 PM Lcvette: \o/
07:35 PM Lcvette: for traverse moves rapid is pretty std
07:35 PM jthornton: I would give them the choice to set the speed they want to do the routine at
07:35 PM Lcvette: with G38.3 it will stop if probe trips
07:35 PM Lcvette: they have control over touch speed first and second if they choose
07:36 PM jthornton: yea but a newbee first time they might want to go real slow for all the moves
07:36 PM Lcvette: no room for another box
07:36 PM Lcvette: that page is the worst for space
07:37 PM Lcvette: if they really wanna control it they can turn down the max velocity on the machine
07:37 PM Lcvette: the slider
07:37 PM Lcvette: it has a rapid slider
07:37 PM Lcvette: i tested and it adheres to the slider even in the ngc file
07:38 PM jthornton: but the rapid slider won't change the feed speed
07:38 PM TurBoss: also G0 sometimes does round corners
07:38 PM TurBoss: or not
07:38 PM TurBoss: ...
07:38 PM jthornton: aye and big round sometimes if acceleration is low
07:38 PM Lcvette: they have control over the feed speed
07:38 PM Lcvette: they have the max velocity slider
07:39 PM Lcvette: they have noth in probe basic
07:39 PM Lcvette: both*
07:40 PM Lcvette: i can add that to the probe help pages in the gui
07:40 PM Lcvette: i just want an easy way to resolve changing the G0 to a G38.3 move without adding a box which won't fit
07:44 PM Tom_L: need a 4k monitor?
07:45 PM * Lcvette uploaded an image: Screenshot_2019-10-11_20-38-56.png (51KB) < https://matrix.org/_matrix/media/r0/download/matrix.org/bepVloTEApymxYdmCJKzJEtK >
07:45 PM Lcvette: no pace left
07:57 PM Lcvette: i have an idea.. i will pull the number from the max velocity slider label
07:57 PM Lcvette: that way they have control over it, it will be a feedword and can use G38.3
07:57 PM Lcvette: \o/
08:21 PM Lcvette: works!
08:21 PM Lcvette: hurray!!
08:21 PM Lcvette: what a great solution!
08:22 PM TurBoss: hurray!
08:23 PM Lcvette: im very pleased with that option, now all moves during the probing routine will stop if the probe is triggered
08:23 PM Lcvette: now I have to go through and edit 38 probe routines
08:23 PM Lcvette: :o
08:24 PM TurBoss: Lcvette: can you help me figure the vtk issue?
08:24 PM TurBoss: oh ok
08:24 PM TurBoss: latter
08:24 PM Lcvette: sure whats up
08:24 PM Lcvette: i can edit the probe routines whenever
08:24 PM TurBoss: okay
08:24 PM Lcvette: but while you are available i prefer to spend my time helping you
08:25 PM TurBoss: it you reset offsets to zero
08:25 PM TurBoss: and restart
08:25 PM TurBoss: then set some offsets it worsk fine
08:25 PM Tom_L: vtk?
08:25 PM TurBoss: the 3d plot
08:25 PM Lcvette: checkout 3D_PLOT
08:25 PM Lcvette: latest?
08:26 PM TurBoss: ok I'll push
08:26 PM TurBoss: in a sek
08:26 PM * Lcvette uploaded an image: Screenshot_2019-10-11_21-20-08.png (24KB) < https://matrix.org/_matrix/media/r0/download/matrix.org/xGykNOxCpMITVnpMhRLysWrT >
08:26 PM Lcvette: kjc one?
08:26 PM Lcvette: oh ok
08:26 PM Lcvette: will wait for the go ahead from you
08:26 PM TurBoss: not pushed yet
08:28 PM Not-5e4d: [02qtpyvcp] 07TurBoss pushed 031 commit to 033D_PLOT [+0/-0/±1] 13https://git.io/Jeliz
08:28 PM Not-5e4d: [02qtpyvcp] 07TurBoss 03f618075 - Status at top
08:29 PM TurBoss: Lcvette: done
08:29 PM Lcvette: ok
08:32 PM Lcvette: pulled
08:32 PM TurBoss: okay
08:32 PM Lcvette: now what?
08:32 PM TurBoss: set g54 to zero
08:32 PM TurBoss: then close
08:33 PM Lcvette: ok
08:33 PM Lcvette: now
08:33 PM Lcvette: ?
08:34 PM Lcvette: next
08:34 PM Lcvette: all looks normal
08:34 PM Lcvette: TurBoss: ?
08:34 PM TurBoss: ok
08:35 PM TurBoss: now open a file
08:35 PM TurBoss: wich you know the origin
08:35 PM Lcvette: ok
08:35 PM Lcvette: looks correct
08:36 PM TurBoss: not set some offset
08:36 PM TurBoss: in g54
08:36 PM TurBoss: now
08:36 PM TurBoss: **
08:36 PM TurBoss: * now set some offset
08:37 PM TurBoss: ran the sim
08:37 PM TurBoss: the program
08:37 PM TurBoss: and see if there is no "error offset"
08:37 PM Lcvette: no
08:37 PM TurBoss: ok
08:37 PM TurBoss: so now there is a offset
08:37 PM Lcvette: the tool stayed at the machine coordinates zero
08:38 PM Lcvette: but when i hit cycle start it moved correctly to the part
08:38 PM TurBoss: ok
08:38 PM TurBoss: now close and open again
08:38 PM * Lcvette uploaded an image: Screenshot_2019-10-11_21-32-20.png (90KB) < https://matrix.org/_matrix/media/r0/download/matrix.org/alBWWCeGsjUhBEXlJYeOfoIV >
08:39 PM TurBoss: then open a file
08:39 PM TurBoss: and run
08:39 PM TurBoss: it should be wrong
08:40 PM Lcvette: still good
08:40 PM TurBoss: ?
08:40 PM TurBoss: yes?
08:40 PM TurBoss: try to run and see
08:40 PM * Lcvette uploaded an image: Screenshot_2019-10-11_21-34-28.png (109KB) < https://matrix.org/_matrix/media/r0/download/matrix.org/PiYDqhNCsQeWjwnIawrEgXZB >
08:40 PM TurBoss: 😐️
08:41 PM Lcvette: is correct, same as the first time
08:41 PM TurBoss: can I have the file?
08:41 PM TurBoss: :P
08:42 PM Lcvette: ek
08:43 PM * Lcvette posted a file: bezel_fast.ngc (673KB) < https://matrix.org/_matrix/media/r0/download/matrix.org/aFKQdBXOsqBYRyYnSZDiWsnq >
08:44 PM Lcvette: turboss^^^
08:44 PM * TurBoss uploaded an image: image.png (33KB) < https://matrix.org/_matrix/media/r0/download/matrix.org/YTMkpkxzzpQzinLsePgNqQrg >
08:44 PM Lcvette: check the calibration offset page in probing
08:45 PM Lcvette: for some reason and i have no clue where it comes from but when i start up the system there is a 2.0000 in there
08:45 PM Lcvette: could that be it?
08:45 PM TurBoss: checking
08:46 PM TurBoss: where?
08:46 PM Lcvette: its not there now
08:46 PM Lcvette: lol
08:46 PM Lcvette: donno where it went or where it comes from
08:46 PM Lcvette: im running 3dchips now and all is fine there too
08:47 PM Tom_L: check your back pocket
08:47 PM TurBoss: 😁
08:48 PM Lcvette: Tom_L: is so quippy
08:48 PM Lcvette: lol
08:48 PM Tom_L: gotta keep it real
08:48 PM Lcvette: you get the timer working yet?
08:48 PM Lcvette: turboss mine is acting fine here
08:49 PM Tom_L: got in a good nap
08:49 PM Lcvette: but i know it acts up as i saw it earlier today
08:49 PM Lcvette: can't make it do it now
08:49 PM TurBoss: did you restart
08:49 PM Lcvette: Tom_L: did the code come to you in a dream by chance?
08:49 PM Lcvette: lol
08:49 PM Lcvette: turboss.. yes retsrated
08:49 PM Tom_L: i have a plan but no execution
08:49 PM Lcvette: used the previously set g54 offset
08:50 PM TurBoss: cool
08:50 PM Tom_L: if i knew python it would be one
08:50 PM Tom_L: done*
08:50 PM Lcvette: is that correct?
08:50 PM TurBoss: can't figure why mine if wrong
08:50 PM TurBoss: * can't figure why mine is wrong
08:50 PM TurBoss: Tom_L: try to write some widget
08:51 PM TurBoss: with my docs == 0
08:51 PM TurBoss: :(
08:54 PM * TurBoss uploaded an image: image.png (204KB) < https://matrix.org/_matrix/media/r0/download/matrix.org/awDEUTbIllGjKBcqyhduFZjR >
08:54 PM Tom_L: that's fugly
08:55 PM TurBoss: ☹️
08:58 PM Lcvette: dunno
08:58 PM Lcvette: im running xyzab sim
08:58 PM Lcvette: how about you turboss?
08:59 PM Lcvette: ive tried to screw it up multiple times now but it won't break
08:59 PM Tom_L: :O
08:59 PM TurBoss: i just have to set an offset then restart
08:59 PM TurBoss: and load file
08:59 PM TurBoss: tried meny
09:00 PM Lcvette: set how?
09:00 PM TurBoss: from the dro Zero buttons
09:00 PM Lcvette: in the table or with zero
09:00 PM Lcvette: ah ok
09:00 PM Lcvette: lemme try that way
09:01 PM TurBoss: okay!
09:02 PM Lcvette: npe still good
09:02 PM Lcvette: wonder if you have axisshift offsets set somewherre?
09:02 PM TurBoss: duno...
09:02 PM Lcvette: tried clear all offsets in the table?
09:02 PM TurBoss: yes
09:02 PM Lcvette: save and relaod
09:03 PM Lcvette: thenh shut down start up and try
09:03 PM Lcvette: run G91.1
09:04 PM TurBoss: ok
09:08 PM Lcvette: nubby has arrived o/
09:08 PM TurBoss: he ran
09:08 PM Lcvette: lol
09:08 PM Lcvette: hazzy
09:08 PM Lcvette: why you run away?
09:09 PM TurBoss: 😛
09:09 PM Lcvette: its the full development install
09:09 PM Lcvette: yes
09:11 PM Lcvette: TurBoss: you hav it working
09:11 PM TurBoss: no
09:11 PM TurBoss: it wrong...
09:11 PM TurBoss: * its wrong...
09:12 PM * hazzy-m was reading devel
09:13 PM Lcvette: lcvette found a great solution for probing and turboss has somethign brok but its not acting the same on my machine
09:13 PM TurBoss: #freenode_#linuxcnc-devel:matrix.org
09:13 PM * hazzy-m forgot to order folding beam tools for one of the FABTECH machines, and they have a 15week lead time
09:13 PM hazzy-m: oppsie
09:13 PM TurBoss: oops
09:13 PM Lcvette: :o
09:13 PM Lcvette: hazzy is fored!
09:13 PM Lcvette: fired!
09:13 PM Lcvette: * hazzy is fired!
09:14 PM hazzy-m: I would fire my self if I did something like that lol
09:14 PM TurBoss: still in place?
09:14 PM TurBoss: xD
09:14 PM hazzy-m: been trying to find a customer I can borrow tools from
09:14 PM hazzy-m: TurBoss: VTK is broken?
09:15 PM TurBoss: on mine deskt
09:15 PM hazzy-m: hmm
09:15 PM Lcvette: https://www.google.com/url?sa=i&source=images&cd=&ved=2ahUKEwiP4e_p0ZXlAhXpYN8KHbJoDCgQjRx6BAgBEAQ&url=https%3A%2F%2Ftenor.com%2Fview%2Fyoure-fired-bugs-life-disney-gif-7727001&psig=AOvVaw2TBjQ6l5S4_kKYHv1c4fPZ&ust=1570932514569818
09:15 PM TurBoss: 3D_PLOT
09:16 PM hazzy-m: what branch?
09:16 PM * hazzy-m uploaded an image: image.png (121KB) < https://matrix.org/_matrix/media/r0/download/matrix.org/tgIZfpreSpzPpviTJFDJzWOo >
09:16 PM Lcvette: https://www.youtube.com/watch?v=xwEuCxOT2O0
09:16 PM Lcvette: \o/
09:16 PM TurBoss: whe I restart with a offset in g54 it draws the path in the wrong place put the origin is drawn correctly
09:16 PM TurBoss: * whe I restart with a offset in g54 it draws the path in the wrong place but the origin is drawn correctly
09:16 PM TurBoss: xyz
09:17 PM Lcvette: TurBoss: try xyzab
09:17 PM TurBoss: the branch has some other fixes
09:17 PM TurBoss: like no file handle
09:17 PM TurBoss: probe_basic/config/xyzab/xyzab.ini
09:18 PM Lcvette: \o/
09:18 PM hazzy-m: Lcvette: lol
09:18 PM hazzy-m: strange
09:18 PM Lcvette: turboss is not cauight up in probe basic
09:19 PM Lcvette: maybe try that?
09:19 PM Lcvette: \o/
09:19 PM Lcvette: i did it?
09:19 PM TurBoss: you !
09:20 PM TurBoss: 😈
09:20 PM TurBoss: tried
09:20 PM Lcvette: turboss is fixed?
09:20 PM TurBoss: yes
09:20 PM TurBoss: !
09:20 PM Lcvette: \o/
09:20 PM Lcvette: im the genius
09:20 PM TurBoss: its wrong? hazzy
09:21 PM hazzy-m: TurBoss: are you polling status in vtk now?
09:21 PM TurBoss: i was getting crazy changed all
09:21 PM TurBoss: but in a branch
09:21 PM TurBoss: lol
09:21 PM * hazzy-m sent a long message: < https://matrix.org/_matrix/media/r0/download/matrix.org/vJywhWBpjpydOuRzpGHhuMgr >
09:21 PM TurBoss: ah xd
09:22 PM hazzy-m: I need to read what you did, but looks like good ideas
09:22 PM Lcvette: Turboss is a victim of leaving the nest
09:22 PM Lcvette: :o
09:22 PM TurBoss: the poll can out
09:22 PM TurBoss: 🤐
09:22 PM Lcvette: Hazzy fixes the timer?
09:23 PM Lcvette: What broke now?
09:23 PM TurBoss: just nuked
09:23 PM TurBoss: g5x_offset
09:23 PM Lcvette: :o
09:23 PM hazzy-m: TurBoss: what were you polling for?
09:23 PM hazzy-m: ah!
09:24 PM TurBoss: ok there is no need
09:24 PM Lcvette: Lcvette solved
09:24 PM TurBoss: good cathc
09:24 PM Lcvette: \o/
09:24 PM TurBoss: * good catch
09:24 PM TurBoss: \o/
09:24 PM TurBoss: also
09:24 PM Lcvette: Now the timer?
09:25 PM TurBoss: the timer
09:25 PM TurBoss: lol
09:25 PM TurBoss: ok
09:25 PM Lcvette: \o\/o/
09:25 PM TurBoss: give me a ek
09:25 PM Lcvette: Hazzy the persistent boxes?
09:25 PM Lcvette: Lcvette fixes the probe safeguards
09:25 PM Not-5e4d: [02qtpyvcp] 07TurBoss pushed 031 commit to 033D_PLOT [+0/-0/±1] 13https://git.io/Jelih
09:25 PM Not-5e4d: [02qtpyvcp] 07TurBoss 03f1afe71 - remove useless
09:26 PM Lcvette: Then probe basic works!
09:26 PM Lcvette: Then it's disco time
09:26 PM hazzy-m: Hurray!
09:26 PM hazzy-m: so close!
09:27 PM Lcvette: Nooooooool not close again
09:27 PM hazzy-m: hahaha
09:27 PM Not-5e4d: [02qtpyvcp] 07TurBoss pushed 031 commit to 033D_PLOT [+0/-0/±1] 13https://git.io/JelPf
09:27 PM Not-5e4d: [02qtpyvcp] 07TurBoss 034f83cff - fix load in designer
09:28 PM TurBoss: up for merge
09:36 PM hazzy-m: Sweet!
09:36 PM Tom_L: who would be in charge of making a timer widget?
09:36 PM Tom_L: i thought of using Qtimer but don't know pythong
09:37 PM Tom_L: basically it needs a start trigger that comes from halui.program.is-idle
09:37 PM Tom_L: and a stop trigger
09:37 PM Tom_L: when it reverses state
09:37 PM TurBoss: me
09:37 PM TurBoss: I need to know from where the inputs an d the outpus
09:37 PM TurBoss: * I need to know from where the inputs an d the outpust
09:38 PM TurBoss: * I need to know from where the inputs an d the outputs
09:38 PM hazzy-m: The TurBoWidget master
09:38 PM TurBoss: @hazzy can I send signals to plugins?
09:38 PM TurBoss: with rules?
09:38 PM TurBoss: or somthing
09:38 PM TurBoss: :P
09:38 PM Tom_L: well alot would need to be python since Qtimer isn't a widget on the list
09:38 PM Tom_L: or add it to the widget list somehow?
09:38 PM Tom_L: then expose the hal pin
09:38 PM Tom_L: which i can't find but you said was interp
09:38 PM TurBoss: but what should display?
09:39 PM TurBoss: in the UI
09:39 PM TurBoss: nothing'0
09:39 PM TurBoss: * nothing??
09:39 PM Tom_L: elapsed overall run time and individual tool time
09:39 PM TurBoss: cool
09:39 PM Tom_L: one sec
09:39 PM Tom_L: http://tom-itx.no-ip.biz:81/~webpage/cnc/screenshot.png
09:39 PM Tom_L: "Cycle Times"
09:40 PM Tom_L: that's what Lcvette wants in the box between estop on his probe_basic
09:40 PM TurBoss: okay
09:40 PM Lcvette: \o/
09:42 PM Tom_L: or
09:42 PM Tom_L: tap into a linuxcnc user comp time.comp to do the same thing
09:42 PM Tom_L: that's what i'm currently using for time
09:43 PM Tom_L: qtimer is in mS so might need a little math
09:43 PM Tom_L: it does have an elapsed time function already though
09:44 PM TurBoss: can't status labels do that?
09:44 PM Tom_L: one feature that was added recently to the time.comp was a pause to be used during idle events in the program sequence like tool changes etc
09:44 PM Tom_L: no idea you're the master guru
09:44 PM TurBoss: hmmm
09:44 PM Tom_L: if i had a clue i would try but i don't
09:47 PM Tom_L: TurBoss, you can see the available pins and signals here: http://linuxcnc.org/docs/2.8/html/man/man9/time.9.html
09:47 PM Tom_L: would be handy to have them for probe_basic or the "time" widget
09:48 PM Tom_L: the code for it would also be in master of linuxcnc if it would help any
10:01 PM Tom_dev: https://github.com/LinuxCNC/linuxcnc/blob/master/src/hal/components/time.comp
10:02 PM Tom_L: are those pins visible to qtpyvcp?
10:03 PM Tom_L: if so, that timer should work, just need the display end coded in qtpyvcp
10:04 PM Tom_L: which the link also shows pyvcp code for
10:29 PM Tom_L[m]: put everybody to sleep?
10:30 PM Lcvette: jammin on updating the probe routines for the safe moves everywhere
10:30 PM Lcvette: turbos is probably coding
10:31 PM Lcvette: hopefully hazzy is jammin on persistent boxes
10:38 PM * TurBoss uploaded an image: image.png (4KB) < https://matrix.org/_matrix/media/r0/download/matrix.org/oDTLfIZvQzUdDHYOOkrWPpLJ >
10:39 PM TurBoss: Tom_L: you can use hal_labels
10:39 PM Lcvette: you did it?
10:39 PM Lcvette: \o/
10:39 PM Lcvette: can i format?
10:39 PM TurBoss: not yet
10:39 PM Lcvette: ok
10:40 PM TurBoss: very easy
10:40 PM TurBoss: you add hallabels
10:40 PM TurBoss: one for secs other mins and hours
10:41 PM Lcvette: ok
10:41 PM TurBoss: and 2 regular labels for the ":"
10:42 PM Lcvette: ok
10:42 PM Lcvette: im with ya
10:42 PM Lcvette: and put it all in a qwidget box to keep them together
10:42 PM TurBoss: yup
10:44 PM Tom_L: i wish i had a better understanding of this
10:44 PM Tom_L: can you post what you did?
10:44 PM TurBoss: yes
10:45 PM TurBoss: in designer there are hal labels
10:45 PM Tom_L: are you using the time.comp?
10:45 PM TurBoss: in the hal section
10:45 PM TurBoss: yes
10:45 PM Tom_L: where do i find those
10:45 PM TurBoss: in the designer
10:45 PM TurBoss: in the widget column
10:45 PM TurBoss: there is a hal section
10:45 PM Tom_L: if i don't have that, how do i get it?
10:45 PM Tom_L: i think i'm missing some
10:46 PM TurBoss: new install?
10:46 PM TurBoss: dev install?=
10:46 PM Tom_L: possibly yes
10:46 PM Tom_L: i thought i had the dev installed
10:46 PM Tom_L: used you know who's directions :)
10:46 PM TurBoss: yo need to run a scripp
10:47 PM Tom_L: ok terminal is up
10:47 PM TurBoss: pyqt5designer/Qt5.7.1-64bit/install.sh
10:47 PM TurBoss: in qtpyvcp
10:47 PM Tom_L: one sec
10:47 PM TurBoss: cd qtpycvp
10:47 PM TurBoss: cd pyqt5designer/Qt5.7.1-64bit/
10:48 PM Tom_dev: ok
10:48 PM TurBoss: sudo ./install.sh
10:48 PM * Lcvette uploaded an image: Screenshot_2019-10-11_23-41-45.png (97KB) < https://matrix.org/_matrix/media/r0/download/matrix.org/gzpQSgZanclofdauHBeQoOLe >
10:48 PM TurBoss: this will enable the widgets on designer
10:48 PM Lcvette: here they are do you not have those?
10:48 PM Tom_dev: lemme check
10:48 PM Lcvette: all the way at the bottom
10:48 PM Lcvette: scroll down the green ones should appear
10:48 PM Lcvette: they do on my test pc and i followed the instructions myself
10:49 PM Tom_L: so which hal widget did you use?
10:49 PM TurBoss: hal label
10:49 PM Tom_L: ahh
10:49 PM TurBoss: add 3
10:49 PM TurBoss: and 2 regular labels
10:49 PM Tom_L: inside his little window?
10:50 PM TurBoss: if mini yes
10:50 PM Lcvette: welcome to designer formatting 101
10:50 PM Tom_L: no i'm in probe_basic
10:50 PM TurBoss: ok
10:50 PM TurBoss: place a horizontal layout somewere
10:50 PM TurBoss: then the labels inside
10:50 PM Lcvette: you are best off using the setting page and start with a qwidget box
10:50 PM TurBoss: or that
10:50 PM Lcvette: format it for horizontal
10:50 PM Lcvette: layout
10:51 PM Lcvette: in the property editor
10:51 PM Lcvette: or right click in it
10:51 PM Lcvette: then add your labels one at a time droping them in the box
10:51 PM Lcvette: then add your text or the :
10:51 PM Lcvette: in the two normal labels
10:51 PM Tom_L: looking for qwidget
10:51 PM * TurBoss uploaded an image: image.png (11KB) < https://matrix.org/_matrix/media/r0/download/matrix.org/FhbUcppUwHNgUBgioTxcZFPv >
10:51 PM Lcvette: and add in the hallabels
10:52 PM TurBoss: and set a easy name for each one
10:52 PM TurBoss: like cycle_hours cycle_mins
10:52 PM TurBoss: etc..
10:52 PM TurBoss: very important
10:52 PM Tom_L[m]: right
10:52 PM Tom_L[m]: that's what i did in axis
10:52 PM * TurBoss uploaded an image: image.png (4KB) < https://matrix.org/_matrix/media/r0/download/matrix.org/IssDDnZFtBtOojikymCRSmtG >
10:53 PM * Tom_L is not keeping up
10:53 PM TurBoss: ok
10:53 PM TurBoss: what you have
10:53 PM Tom_L: nothing yet
10:54 PM Tom_L: looking for qwidget
10:54 PM * TurBoss uploaded an image: image.png (5KB) < https://matrix.org/_matrix/media/r0/download/matrix.org/ABccXlCabImGXTjEbzlUafVP >
10:54 PM TurBoss: horizontal layout
10:54 PM Tom_L: just a widget from the container section?
10:54 PM TurBoss: at top
10:54 PM Tom_L: k, horizontal drug into settings page
10:54 PM TurBoss: ok
10:55 PM TurBoss: the inside place the hal labels
10:55 PM TurBoss: then*
10:55 PM Tom_L: do i want a vertical inside it as well?
10:55 PM TurBoss: many as you need
10:56 PM TurBoss: horizontal is fine
10:56 PM Tom_L: ok i did 3, hr min sec
10:56 PM TurBoss: okay
10:57 PM Tom_L: and named them
10:57 PM TurBoss: you can also place regular labels for the dots
10:57 PM TurBoss: then in each hal label properties
10:57 PM Tom_L: where are those?
10:57 PM TurBoss: label
10:57 PM TurBoss: there is a search at top
10:59 PM Tom_L: ok got 2 and named them
10:59 PM TurBoss: ok
10:59 PM TurBoss: sou you have 3 hal and 2 regular
10:59 PM TurBoss: ok
10:59 PM Tom_L: yup
10:59 PM Tom_L: no particular order yet
10:59 PM TurBoss: then go to the hours label
11:00 PM Tom_L: k
11:00 PM TurBoss: at bottom
11:00 PM Lcvette: lcvette update every probing routine!
11:00 PM TurBoss: \o/
11:00 PM Tom_L: under signal slots?
11:00 PM TurBoss: no
11:00 PM Lcvette: \o/
11:01 PM Lcvette: lcvette goes for a cigar
11:01 PM Lcvette: will be on mobile then coming back to see the timer update!
11:01 PM * TurBoss uploaded an image: image.png (83KB) < https://matrix.org/_matrix/media/r0/download/matrix.org/vcryxAnDOksesZCuRZPxybrx >
11:02 PM TurBoss: is a window
11:02 PM TurBoss: from designer
11:02 PM Tom_L: ok changed to u32
11:02 PM TurBoss: and the texFormat too
11:02 PM TurBoss: same with others
11:02 PM Tom_L: k
11:03 PM TurBoss: once
11:03 PM TurBoss: inyour ini
11:03 PM Tom_L: done
11:03 PM TurBoss: in hal section you add
11:03 PM TurBoss: POSTGUI_HALFILE = time.hal
11:03 PM TurBoss: or whatever you like
11:03 PM Tom_L: where do i find it for probe_basic?
11:03 PM TurBoss: name
11:04 PM TurBoss: the one you want to run
11:04 PM Tom_L: i dunno where you keep them
11:04 PM TurBoss: probe_basic/confis/xyzab.ini
11:04 PM TurBoss: i think
11:04 PM Tom_L: ok
11:04 PM Tom_L: looking
11:05 PM Tom_L: what section should that go in?
11:05 PM TurBoss: [HAL]
11:06 PM Tom_L: not halui?
11:06 PM Tom_L: ok done
11:06 PM TurBoss: the create a file
11:06 PM Tom_L: i'd ahve to look at mine to see where i put mine
11:06 PM TurBoss: time.hal
11:06 PM Tom_L: in what dir?
11:06 PM * TurBoss sent a long message: < https://matrix.org/_matrix/media/r0/download/matrix.org/sGmSyWsmkKGrlMuKJRVWUZvz >
11:06 PM TurBoss: in the same is the ini
11:07 PM TurBoss: timeminutes hous here are the status labels
11:07 PM TurBoss: hal label names
11:07 PM Lcvette: what are you guys working in branchwise?
11:07 PM Tom_L: ok done
11:08 PM TurBoss: ok the fire pb
11:08 PM TurBoss: with that ini
11:08 PM Tom_L: i need : in the other 2 labels
11:08 PM Tom_L: where's that at?
11:08 PM TurBoss: linuxcnc probebasic/configs/xyzab.ini
11:08 PM TurBoss: save the designer and all stuff
11:09 PM TurBoss: the cycle time
11:09 PM TurBoss: Tom_L: any luck?
11:09 PM Tom_L: ok just a sec
11:10 PM Lcvette: TurBoss: what branch?
11:10 PM TurBoss: none
11:10 PM TurBoss: master
11:10 PM TurBoss: is fine
11:11 PM TurBoss: i should write more words in one line
11:11 PM Tom_L: mmm trouble finding the file
11:12 PM TurBoss: where did you clone probe_basic
11:12 PM TurBoss: ?
11:13 PM Tom_L: it's not a damn simlink is it?
11:13 PM TurBoss: no
11:13 PM TurBoss: in home
11:13 PM TurBoss: probe_basic
11:13 PM * Tom_L[m] uploaded an image: image.png (121KB) < https://matrix.org/_matrix/media/r0/download/matrix.org/MdjktdnHSRQOtdvQclUrUMrw >
11:13 PM TurBoss: ye
11:14 PM * Tom_L[m] uploaded an image: image.png (41KB) < https://matrix.org/_matrix/media/r0/download/matrix.org/VgZdqvNRbVEuefIOnztsENtS >
11:14 PM TurBoss: in terminal run linuxcnc /home/tomm/probe_basic/config/xyzab/xyzab.ini
11:14 PM Tom_L: nevermind
11:15 PM TurBoss: works?
11:15 PM * Tom_L[m] uploaded an image: image.png (66KB) < https://matrix.org/_matrix/media/r0/download/matrix.org/vYXPcXEdIIkSCdySONOpUPNb >
11:15 PM TurBoss: in time.hal
11:16 PM TurBoss: you have to replace timesecondes with the name you gived to the label
11:16 PM TurBoss: and same for others
11:16 PM Tom_L: well duh
11:16 PM TurBoss: just 3
11:17 PM Tom_L: what did i name them?
11:17 PM Tom_L: :)
11:17 PM TurBoss: in designer
11:17 PM Tom_L: i know
11:17 PM TurBoss: name it timeseconds
11:17 PM Tom_L: stupid mistake
11:17 PM TurBoss: i forgot to mention lol
11:18 PM Tom_L: and i new it too
11:19 PM Tom_L: still crashed
11:19 PM TurBoss: same error?
11:19 PM Tom_dev: Pin 'qtpyvcp.timeseconds.in' does not exist
11:20 PM Tom_L: probably same for the other 2
11:20 PM TurBoss: if you disable the postgui line in the ini and run probebasic it shows the labels you created?
11:20 PM TurBoss: just put comment it #
11:20 PM Tom_L: yes
11:20 PM TurBoss: do the name match¿
11:21 PM * Tom_L[m] uploaded an image: image.png (185KB) < https://matrix.org/_matrix/media/r0/download/matrix.org/tTaYluPAofaWAmHLUHrBaQDX >
11:21 PM Tom_L: upper left
11:21 PM TurBoss: works?
11:21 PM Tom_L: if i comment out the postgui line yes
11:21 PM TurBoss: ok
11:22 PM TurBoss: have you double cheked the names of the labes in designer ? :)
11:22 PM TurBoss: seconds or secconds?
11:22 PM Tom_L: i renamed the net
11:22 PM TurBoss: ok
11:22 PM Tom_L: i think i need to rename the qtpyvcp.xxxx
11:22 PM Tom_L: right?
11:22 PM TurBoss: yes
11:22 PM TurBoss: xxx.in
11:22 PM TurBoss: qtpyvcp.hallabelname.in
11:23 PM TurBoss: if still fails
11:24 PM TurBoss: duno
11:24 PM TurBoss: it does?
11:24 PM TurBoss: in tools hal meter
11:25 PM TurBoss: check for the qtpyvcp pins in there
11:27 PM Tom_dev: Pin 'qtpyvcp.cycle_sec.in' does not exist
11:27 PM Tom_L: i named the widget cycle_sec
11:27 PM Tom_L: do i need to add the .in to it?
11:28 PM TurBoss: no
11:28 PM TurBoss: only on the hal
11:28 PM Tom_L: that's what i thought
11:28 PM TurBoss: hal file
11:28 PM Tom_L: i don't get it
11:28 PM TurBoss: hmmmmmmm
11:28 PM Tom_L: just a sec
11:29 PM * Tom_L[m] uploaded an image: image.png (22KB) < https://matrix.org/_matrix/media/r0/download/matrix.org/QHvTPwlmqOQAQMVqqufnLVOZ >
11:30 PM * Tom_L[m] uploaded an image: image.png (16KB) < https://matrix.org/_matrix/media/r0/download/matrix.org/gxlWOBNvYeXsZlWUeQkQiWIS >
11:30 PM TurBoss: i think that _ is not valid
11:30 PM Tom_L: it is in hal :)
11:30 PM TurBoss: ok
11:30 PM Tom_L: lemme change it anyway
11:30 PM TurBoss: in probebasic there is the hal meter
11:31 PM Tom_L: it won't let me add the '-'
11:31 PM * Lcvette uploaded an image: Screenshot_2019-10-12_00-25-19.png (24KB) < https://matrix.org/_matrix/media/r0/download/matrix.org/jDLJAcgqvmpPaCDWMECxwVQZ >
11:32 PM TurBoss: works Lcvette ??
11:32 PM Lcvette: all i did is the formatting of the labels
11:32 PM Lcvette: 3 hallabels and two qlabels
11:32 PM TurBoss: looks fine
11:32 PM Lcvette: and the stylesheet
11:33 PM TurBoss: tom is having issues...
11:33 PM TurBoss: duno why
11:34 PM Lcvette: now what to do?
11:35 PM TurBoss: did you set the u32 thing?
11:35 PM Lcvette: have pictures of the three property editor settings?
11:35 PM TurBoss: yes
11:35 PM TurBoss: gibve them names
11:35 PM * Tom_L[m] uploaded an image: image.png (184KB) < https://matrix.org/_matrix/media/r0/download/matrix.org/UosOowDfcZvdfszqqfsAsJue >
11:35 PM Lcvette: hours, minutes, seconds
11:35 PM Lcvette: ?
11:36 PM Tom_L: Lcvette how did you get that in the box?
11:36 PM * TurBoss uploaded an image: image.png (30KB) < https://matrix.org/_matrix/media/r0/download/matrix.org/vmSHCRxABjumgoNZQRmqMCxS >
11:36 PM Tom_L: mine is working
11:36 PM TurBoss: hurray!
11:36 PM Tom_L: how to get the timer to start now?
11:36 PM TurBoss: duno
11:36 PM TurBoss: :D
11:36 PM TurBoss: cycle start
11:37 PM TurBoss: it runs auto
11:37 PM Tom_L: nothing
11:38 PM Tom_L: estop, power, home, cycle start
11:38 PM TurBoss: did you load a file?
11:39 PM Lcvette: TurBoss: ok now what
11:40 PM TurBoss: in the ini
11:40 PM Lcvette: yup
11:40 PM TurBoss: you may need a POSTGUI_HALFILE
11:40 PM Lcvette: :o
11:40 PM TurBoss: time.hal
11:41 PM Lcvette: upload here?
11:41 PM * TurBoss sent a long message: < https://matrix.org/_matrix/media/r0/download/matrix.org/gLhUWCVjXiwrUpQfzSdNVcjs >
11:41 PM TurBoss: rename the timehours to your labels to match
11:43 PM Tom_L: cycle start doesn't start
11:43 PM * Lcvette sent a long message: < https://matrix.org/_matrix/media/r0/download/matrix.org/oEHQMBevhgJHIcJKnMqkaMmi >
11:43 PM TurBoss: check notifications
11:43 PM Tom_L: where?
11:43 PM TurBoss: in status
11:43 PM TurBoss: maybe the file is out of limits
11:43 PM Tom_L: something about home switches
11:43 PM TurBoss: the path
11:44 PM TurBoss: start over
11:44 PM TurBoss: home is buged
11:44 PM TurBoss: can't be home twice but is a sim bug
11:44 PM Lcvette: what else turboss?
11:44 PM TurBoss: nothing more
11:44 PM TurBoss: just run a program
11:44 PM Tom_L: ok it's working
11:45 PM Tom_L: yay!
11:45 PM TurBoss: hurray!
11:45 PM TurBoss: but I don't know how to get the overall
11:45 PM TurBoss: 😐️
11:45 PM * Tom_L[m] uploaded an image: image.png (199KB) < https://matrix.org/_matrix/media/r0/download/matrix.org/veFiwPHZkTtzdLutelFdVSQu >
11:46 PM Tom_L: start the timer without the pin for the overall
11:46 PM TurBoss: !giphy victory
11:46 PM * Giphy[m] uploaded an image: football-night-fantasy-lnlAifQdenMxW (455KB) < https://matrix.org/_matrix/media/r0/download/matrix.org/MPQTdkkHaOYaBGlBjNzrMGIQ >
11:46 PM TurBoss: then same process
11:46 PM Lcvette: no worky
11:46 PM Tom_L[m]: http://tom-itx.no-ip.biz:81/~webpage/cnc/configs/NEW_MILL_2.8/postgui.hal
11:47 PM Tom_L: timer.0 is one, timer.1 is the other
11:47 PM Tom_L: 2 instances
11:47 PM TurBoss: i see
11:47 PM * Lcvette sent a long message: < https://matrix.org/_matrix/media/r0/download/matrix.org/zAhDLSqNEYAdmGRtjrZfmUua >
11:47 PM TurBoss: The specified POSTGUI_HALFILE does not exist
11:47 PM TurBoss: your file is somewhere
11:48 PM Lcvette: im dumb figured it out testing again
11:48 PM TurBoss: 🙂
11:48 PM Tom_L: TurBoss, can i drag all that into the box by the estop?
11:49 PM Lcvette: now it does exist but linuxcnc won't start
11:49 PM * Lcvette sent a long message: < https://matrix.org/_matrix/media/r0/download/matrix.org/pCsZxOomQCBwMNWmoIDAmINs >
11:49 PM TurBoss: Tom_L: it could
11:50 PM TurBoss: is time there?
11:50 PM * Lcvette uploaded an image: Screenshot_2019-10-12_00-44-24.png (67KB) < https://matrix.org/_matrix/media/r0/download/matrix.org/KTEpHdSvbzxJLZTcwoFZTuFc >
11:50 PM TurBoss: okay
11:50 PM TurBoss: no more errors?
11:50 PM TurBoss: can you run from terminal'
11:51 PM Tom_L: Lcvette, how did you get them inside the timer box?
11:51 PM * Lcvette sent a long message: < https://matrix.org/_matrix/media/r0/download/matrix.org/cpBfuwVomkmSGDyWqVkRKRaq >
11:51 PM Lcvette: ?
11:51 PM TurBoss: remove _
11:51 PM Lcvette: sek lemme get mine working and i will tell you
11:51 PM Lcvette: remove_ where?
11:52 PM Lcvette: POSTGUI_HAL
11:52 PM TurBoss: in label names and time.hal
11:52 PM Lcvette: POSTGUIHAL
11:52 PM TurBoss: no
11:52 PM TurBoss: dont' put "_" in label names and time.hal file
11:53 PM TurBoss: designer desn't allow to put "-"
11:54 PM Lcvette: \o/
11:55 PM * Lcvette uploaded an image: Screenshot_2019-10-12_00-48-48.png (36KB) < https://matrix.org/_matrix/media/r0/download/matrix.org/ZtypdpkunJmajDupsgERUKRs >
11:55 PM Tom_L: now explain how you got the number in there
11:57 PM Lcvette: got what number where?
11:57 PM Lcvette: just like i told you
11:57 PM Tom_L: tell me again
11:57 PM Lcvette: qwidget box
11:57 PM Lcvette: then add your hallabels to it
11:58 PM Lcvette: right click select layout horizontally
11:58 PM Tom_L: i can't drag them into it
11:58 PM Lcvette: you need to do it in setting page
11:58 PM Lcvette: where there is no previous formatting
11:58 PM Tom_L: center horizontal?
11:58 PM Lcvette: you will format it in the settings page then drag the whole qwidget box
11:59 PM Lcvette: layout
11:59 PM Lcvette: do you have a qwidget box in the setting page
11:59 PM Tom_L: i do now