#hazzy Logs

Oct 10 2019

12:25 AM Lcvette: :o
12:31 AM Guido[m]: Thanks for getting back to me. The part that is most appealing to me is the atc stuff. What I have seen thus far, it seems to be able to handle pocket# and tool# correctly, which, from what I understand, is not necessarily the case in other environments. Or has this been fixed elsewhere? Furthermore, probe_basic seems to have thought about providing an interface to interact with an atc. I will need a rack style atc, but it is
12:31 AM Guido[m]: a place to start:).
02:52 AM * Lcvette uploaded an image: boost_concepts_logo.png (353KB) < https://matrix.org/_matrix/media/r0/download/matrix.org/IQuLOfkBAnBudjAbZVNMtoBa >
02:52 AM TurBoss: turboost
02:52 AM Lcvette: lol
02:52 AM TurBoss: morning
02:53 AM Lcvette: bed time almsot
02:53 AM TurBoss: night!
02:53 AM Lcvette: hazzy had me turn off my travis
02:53 AM Lcvette: hopefully that fixed
02:54 AM TurBoss: hurray!
02:54 AM Lcvette: \o/ huray!
03:12 AM * Lcvette uploaded an image: qtpyvcp2.png (622KB) < https://matrix.org/_matrix/media/r0/download/matrix.org/ITVitIiokXRSNhVwAUrUpeaq >
03:17 AM * Lcvette uploaded an image: qtpyvcp_icon.png (7KB) < https://matrix.org/_matrix/media/r0/download/matrix.org/WLVohLcwSpMWtbHKVjVmzbSk >
03:21 AM * Lcvette uploaded an image: Screenshot_2019-10-10_04-15-00.png (109KB) < https://matrix.org/_matrix/media/r0/download/matrix.org/PgUxTucIVJwGlRPmEdoAMdre >
03:21 AM TurBoss: \o/
03:23 AM Lcvette: \o/
03:23 AM Lcvette: hurray
03:23 AM Lcvette: lcvette setup the icons and desktop on new computer
03:24 AM TurBoss: so....
03:24 AM TurBoss: the build system is ok
03:24 AM TurBoss: we only got confused bythe other one
03:24 AM Lcvette: guess so
03:25 AM Lcvette: but i turned it off for lcvette/probe_basic
03:25 AM TurBoss: ok !
03:25 AM Lcvette: \o/
03:28 AM * Lcvette uploaded an image: qtpyvcp_icon v5.png (387KB) < https://matrix.org/_matrix/media/r0/download/matrix.org/JRStgrKaiPbqCIGBORpMNhKK >
03:33 AM * Lcvette uploaded an image: qtpyvcp_icon v5.png (18KB) < https://matrix.org/_matrix/media/r0/download/matrix.org/ZlMywWLVpjBPorESRcCqiINR >
03:36 AM * Lcvette uploaded an image: Screenshot_2019-10-10_04-30-50.png (86KB) < https://matrix.org/_matrix/media/r0/download/matrix.org/hFxLQjslIdWIvzBXEwlIDtkJ >
03:41 AM Lcvette: TurBoss: can you merge the latest and do a release?
03:42 AM Lcvette: i removed the old test offset i made from the gui that was on the settings tab
03:42 AM Lcvette: i also updated the atc sim to call probe_basic in the index_inch and index_metric ini files
03:43 AM Lcvette: now it calls the correct ui rather then the old dead qtpyvcp probebasic
03:44 AM TurBoss: cool ill do
03:44 AM Lcvette: \o/ thanks!
03:44 AM Lcvette: lcvette goes to bed
03:44 AM Lcvette: hes keeping turboss hours
03:44 AM Lcvette: lol
03:44 AM TurBoss: night
03:45 AM Lcvette: time for dreams of ibiza
03:45 AM Lcvette: \o/
05:23 AM jthornton: morning
06:28 AM hazzy-m: morning
06:39 AM Wandoo1980|Sebas: Good morning 😁
07:00 AM cnccustoms[m]: Afternoon
07:25 AM * hazzy-m goes to a customer to trian the techs that are suposed to be training the customer lol
07:49 AM TurBoss: hi
09:17 AM * TurBoss uploaded an image: image.png (321KB) < https://matrix.org/_matrix/media/r0/download/matrix.org/jpwHIXkrTVUAvzJrNMDJHJha >
09:18 AM TurBoss: chaotic neutral
09:24 AM Lcvette: hahahahaha
09:24 AM Lcvette: broken TP holder?
09:29 AM * Lcvette uploaded an image: image.png (39KB) < https://matrix.org/_matrix/media/r0/download/matrix.org/wGahTicKSmNmoHYSlNEoJclb >
09:29 AM Lcvette: holyroller bible thumper lawful good
09:45 AM Lcvette: TurBoss: getting a bug eror i think
09:45 AM * Lcvette sent a long message: < https://matrix.org/_matrix/media/r0/download/matrix.org/nMhBqWIdfOfrSvOsowFvCQhk >
09:45 AM TurBoss: when opening some file?
09:45 AM * Lcvette uploaded an image: Screenshot_2019-10-10_10-39-49.png (33KB) < https://matrix.org/_matrix/media/r0/download/matrix.org/QecSIuHoXchrGHvibNRnGxWh >
09:46 AM Lcvette: no, while probing
09:46 AM Lcvette: in sim
09:46 AM TurBoss: there is no open filewhile probing?
09:47 AM Lcvette: no
09:47 AM TurBoss: so you loaded a file then probed?¿
09:47 AM Lcvette: oh need a program file loaded?
09:47 AM Lcvette: thought we fixed that?
09:47 AM TurBoss: any way is a bug
10:02 AM TurBoss: ok is fixed
10:02 AM TurBoss: if there is no file open don't try to load it
10:02 AM Lcvette: \o/
10:02 AM Lcvette: your at dev?
10:02 AM Lcvette: :o
10:02 AM TurBoss: yup
10:03 AM TurBoss: just noticed that R is not cleared or saved or plot didn't noticed
10:03 AM Lcvette: ?
10:04 AM Lcvette: that was fixed no?
10:04 AM TurBoss: is cleared and saved
10:04 AM TurBoss: but the plot doesn't notice
10:05 AM Lcvette: oh
10:05 AM Lcvette: it was when i was using it
10:05 AM TurBoss: hmmmm
10:05 AM Lcvette: i was doing edge angle probes then clearing and the origin would return to normal
10:05 AM Lcvette: sek i'll test
10:05 AM Lcvette: maybe something got bothed in the merge?
10:06 AM TurBoss: posible
10:13 AM Lcvette: clears the rotation and the origin follows suit
10:14 AM TurBoss: so it works?
10:14 AM TurBoss: ?
10:14 AM Lcvette: no
10:14 AM TurBoss: ☹️
10:15 AM Lcvette: it looked like it worked, but then i changed to another offset and did not show its rotation
10:15 AM Lcvette: but if i change to another offset then back to the one with rotation it changes
10:15 AM Lcvette: so its a refresh issue again
10:16 AM Lcvette: maybe need to tie in any button pushes to refresh of the backplot
10:16 AM Lcvette: ?
10:17 AM Lcvette: is that even possible?
10:17 AM TurBoss: if I set the rotation by hand on the offset table it works
10:17 AM TurBoss: but the probed rotation doesn't
10:18 AM Lcvette: make two offsets with rotation
10:18 AM Lcvette: go to one and clear it
10:18 AM Lcvette: it should work
10:18 AM TurBoss: ```
10:18 AM TurBoss: [qtpyvcp.actions.machine_actions][INFO] Issuing MDI command: o<probe_corner_x_plus_edge_angle> call [99.0] [1.0] [1.0] [0.1] [0.1] [0.5] [0.0] [0.0] [10.0] [0.0] [1.0] [1.0] [1.0] [1.0] [0.0] [0.0] (machine_actions.py:184)
10:18 AM Lcvette: but then click on the other offset with rotation
10:18 AM Lcvette: it does not show the rotation in the backplot
10:18 AM Lcvette: but then if you click on another and back it shows it]
10:18 AM Lcvette: so its some kind of refresh issue
10:19 AM TurBoss: oh I'll test
10:20 AM Lcvette: no now it seems to work
10:20 AM Lcvette: coffee is still sinking in
10:20 AM Lcvette: maybe im imagining it
10:21 AM Lcvette: one thing we are definitely going to need though is a pan button for touch screen
10:21 AM Lcvette: for the back plot
10:23 AM roguish[m]: oh joy. multiple windows updates. ...... just getting it done so I can do some work.
10:24 AM Lcvette: set them to run at night
10:24 AM roguish[m]: here goes another booot
11:02 AM * TurBoss goes away
11:03 AM Not-5e4d: [02qtpyvcp] 07TurBoss created branch 033D_PLOT - 13https://git.io/fhCou
11:03 AM Not-5e4d: [02qtpyvcp] 07TurBoss pushed 033 commits to 033D_PLOT [+0/-0/±3] 13https://github.com/kcjengr/qtpyvcp/compare/a57d79bd805e^...55c20ae24a22
11:03 AM Not-5e4d: [02qtpyvcp] 07TurBoss 03a57d79b - remove no file loaded warnings
11:03 AM Not-5e4d: [02qtpyvcp] 07TurBoss 031fdcec3 - 3d plot initial values to machine data
11:03 AM Not-5e4d: [02qtpyvcp] 07TurBoss 0355c20ae - status stat
11:04 AM Lcvette: turboss did it?
11:04 AM Lcvette: \o/
11:05 AM travis-ci: kcjengr/qtpyvcp#1118 (3D_PLOT - 55c20ae : TurBoss): The build passed.
11:05 AM travis-ci: Diff view : https://github.com/kcjengr/qtpyvcp/compare/a57d79bd805e^...55c20ae24a22
11:05 AM travis-ci: Build details : https://travis-ci.org/kcjengr/qtpyvcp/builds/596185877
11:06 AM TurBoss: may need tests
11:06 AM Lcvette: testing now
11:07 AM Lcvette: what should i be looking for?
11:18 AM Lcvette: TurBoss: something is broken
11:20 AM * Lcvette uploaded an image: Screenshot_2019-10-10_12-13-18.png (347KB) < https://matrix.org/_matrix/media/r0/download/matrix.org/aVzkNuZZBSReuNJphFaiSiqa >
11:20 AM Lcvette: :0
11:32 AM roguish[m]: ghosts ....
12:03 PM Tom_L: mmm
12:04 PM Lcvette: thats from the new backplot fix branch not the main
12:04 PM Lcvette: \o/ tom and rougish are here!
12:04 PM Tom_L: seems it should stay there a while
12:04 PM Lcvette: few lines of code and it will be right as rain
12:05 PM Lcvette: the tubonater is the backplot guru
12:13 PM Tom_L: have you tested persistence?
12:17 PM Lcvette: no, think its still work in progress
12:35 PM Lcvette: Hazzy im trying to get the cycle timer working, i changed the label to a status label and made the following rule for it, but i think i have something wrong
12:35 PM Lcvette: can't get it to work
12:35 PM * Lcvette uploaded an image: Screenshot_2019-10-10_13-28-46.png (28KB) < https://matrix.org/_matrix/media/r0/download/matrix.org/QMKfisqywdxhkGjxSUDOsRzo >
12:37 PM Lcvette: or turboss
12:37 PM Lcvette: ?
12:37 PM * TurBoss just arraived
12:38 PM Lcvette: \o/
12:41 PM Lcvette: TurBoss: any ideas?
12:41 PM TurBoss: testing new fix
12:41 PM Lcvette: k
12:43 PM Tom_L: is it safe to git pull?
12:44 PM Lcvette: it?
12:44 PM Lcvette: what?
12:45 PM Tom_L: qtpyvcp and probe_basic
12:45 PM Lcvette: yes
12:46 PM Lcvette: turboss how to merge probe basic?
12:47 PM TurBoss: no need
12:47 PM Lcvette: it will pull from lcvette master?
12:47 PM TurBoss: just set upstream to origin
12:47 PM TurBoss: and push
12:48 PM Lcvette: \o/
12:48 PM Tom_L: ok let's see if i totally pooched this pc
12:48 PM Lcvette: if i create a tag now with it be ok?
12:48 PM TurBoss: no need
12:49 PM TurBoss: not yet
12:49 PM Lcvette: oh no need because its gitpull?
12:49 PM TurBoss: yes
12:49 PM Lcvette: pulls latest master?
12:49 PM Lcvette: ok
12:49 PM TurBoss: yes
12:50 PM Tom_L: master should never be broke :D
12:51 PM Tom_L: that's what branches are for
12:51 PM * Lcvette uploaded an image: Screenshot_2019-10-10_13-45-38.png (76KB) < https://matrix.org/_matrix/media/r0/download/matrix.org/iekKRqwFhrkatFWwgUSvBTFd >
12:51 PM Lcvette: :(
12:51 PM Lcvette: error
12:53 PM travis-ci: kcjengr/probe_basic#111 (master - 4d75d72 : Chris): The build has errored.
12:53 PM travis-ci: Diff view : https://github.com/kcjengr/probe_basic/compare/4d75d7267c68...4d75d7267c68
12:53 PM travis-ci: Build details : https://travis-ci.org/kcjengr/probe_basic/builds/596231057
12:54 PM Lcvette: im tired of this crap
12:54 PM Lcvette: thought this was fixed
12:54 PM Lcvette: :(
12:54 PM TurBoss: ok there is a offset in path
12:55 PM Lcvette: problematic because he want to set 4 from the offset not machine coordinates
12:57 PM Lcvette: turboss whats that mean?
12:58 PM TurBoss: that the path and the tool path are not the same
12:58 PM TurBoss: like you post in the screenshot
12:58 PM Lcvette: where is the problem from?
12:58 PM TurBoss: offsets
12:58 PM TurBoss: :P
12:58 PM TurBoss: vtk
12:59 PM Lcvette: ah
12:59 PM Lcvette: Tom_L: was your gitpull succesful?
01:00 PM Tom_L: didn't do it yet
01:00 PM Tom_L: busy
01:00 PM Lcvette: i think i know my issue
01:00 PM Lcvette: i changed some files in my install that i don't have gitkraken on
01:00 PM Lcvette: and i think it has created a conflict
01:01 PM Lcvette: and git kraken won't install on my new machine for some reason
01:01 PM Tom_L: you need to stop that!
01:01 PM Tom_L: if you want to stay in sync
01:05 PM Tom_L: TurBoss do you know how to remove a bootloader? does that require a re'install?
01:06 PM Tom_L: trying to get grub back
01:06 PM TurBoss: grub-install /dev/sda
01:06 PM Tom_L: lilo is currently it
01:06 PM Tom_L: how do i get lilo off?
01:06 PM TurBoss: no idea
01:07 PM Tom_L: how do i list the dev?
01:07 PM TurBoss: lsblk
01:08 PM Tom_L: thanks
01:08 PM Tom_L: list block devices?
01:08 PM Tom_L: better unplug the other ssd's first
01:09 PM Tom_L: just to be safe
01:10 PM TurBoss: sure
01:10 PM * TurBoss goes afk
01:11 PM Lcvette: got git kraken up and running on new computer
01:11 PM Lcvette: rset changes
01:11 PM Lcvette: did gitpull, worked great!
01:11 PM Lcvette: \o/
01:11 PM Lcvette: fu's it
01:13 PM Lcvette: hazzy o/
01:14 PM hazzy-m: Yo
01:14 PM * Lcvette uploaded an image: Screenshot_2019-10-10_13-28-46.png (28KB) < https://matrix.org/_matrix/media/r0/download/matrix.org/ztNqprFReUpkSqVMlepYdohm >
01:14 PM TurBoss: hello!
01:14 PM Lcvette: \o/
01:14 PM Lcvette: trying to make the timer work
01:14 PM Lcvette: used a statuslabel and made this rule but i think its needing somethign else
01:15 PM Lcvette: do i need to connect signals and slots from cycle start button to time label?
01:16 PM Lcvette: or do i not have the correct expression?
01:17 PM Tom_L: sounds right
01:19 PM Tom_L: http://tom-itx.no-ip.biz:81/~webpage/cnc/configs/NEW_MILL_2.8/postgui.hal
01:19 PM Tom_L: that's how i did it in axis
01:20 PM Tom_L: do you already have a time function?
01:20 PM Lcvette: dunno
01:21 PM Tom_L: i ran 2 timers
01:21 PM Tom_L: one was the current tool and the other was the overall
01:21 PM Lcvette: good idea
01:21 PM Lcvette: but how to setup in the gui?
01:21 PM Tom_L: since tool changes didn't stop the overall
01:22 PM Tom_L: i wanted to see both
01:22 PM Tom_L: it will be a hal function
01:23 PM Tom_L: so how do you access hal in your gui?
01:23 PM Lcvette: i like it
01:23 PM Lcvette: with that rules box
01:23 PM Lcvette: status:cycle_timer
01:23 PM Lcvette: then make the correct epression
01:23 PM Lcvette: but ocvette doesn't know anything about the xpressions
01:24 PM Lcvette: so if it hasn't been done before i am not able to make a custom expression
01:24 PM Tom_L: you need to start it
01:24 PM Lcvette: in designer
01:26 PM Lcvette: g0
01:27 PM Lcvette: z-4
01:27 PM Lcvette: g0
01:30 PM Lcvette: Tom_L: pull the latest probe bsic
01:30 PM Lcvette: and in designer double click on the timer status label between the estop and power button
01:30 PM Lcvette: it will bring up a rules box
01:30 PM Lcvette: that is how you do things in the gui
01:31 PM Lcvette: for co9nnecting will existin hal things
01:31 PM travis-ci: kcjengr/probe_basic#112 (master - 159efad : Chris): The build passed.
01:31 PM travis-ci: Diff view : https://github.com/kcjengr/probe_basic/compare/4d75d7267c68...159efaddd12d
01:31 PM travis-ci: Build details : https://travis-ci.org/kcjengr/probe_basic/builds/596245451
01:32 PM Tom_L: one sec
01:36 PM Wandoo1980|Sebas: https://youtu.be/lnwfesVo1Ts
01:36 PM Wandoo1980|Sebas: Works great with one little issue 🤔
01:39 PM Tom_L: ok do what now?
01:40 PM Lcvette: do probe_basic git pull
01:40 PM Tom_L: i did and i don't see it
01:40 PM Lcvette: for latest probe_basic pdate
01:40 PM Lcvette: has the timer work in it
01:40 PM Tom_L: it's up to date
01:41 PM Lcvette: i just updated it when i last typed to you earlier
01:41 PM Lcvette: have you updated since?
01:41 PM Wandoo1980|Sebas: if driving to the right is not far enough and the Z moves to the vise, the Z-axis does not stop
01:41 PM Lcvette: like 4 minutes ago?
01:41 PM Tom_L: like 2 sec ago
01:41 PM Tom_L: on the top menu bar?
01:42 PM Lcvette: no, below between the estop and power byutton
01:42 PM Tom_L: take a pic of it
01:42 PM Tom_L: oh ok
01:42 PM * Lcvette uploaded an image: Screenshot_2019-10-10_14-36-42.png (21KB) < https://matrix.org/_matrix/media/r0/download/matrix.org/wLlGvVdVhHrGBrawcstyIqxK >
01:43 PM Lcvette: Wandoo1980 | Sebastian | End-CNC: whats the issue?
01:43 PM Wandoo1980|Sebas: if driving to the right is not far enough and the Z moves to the vise, the Z-axis does not stop
01:44 PM Wandoo1980|Sebas: Like in the video but not far enough
01:44 PM Lcvette: what are your probing parameter settings?
01:44 PM Lcvette: can you post a picture of them
01:46 PM Wandoo1980|Sebas: 100mm at first but it's 110mm wide
01:46 PM * Lcvette uploaded an image: Screenshot_2019-10-10_14-39-49.png (88KB) < https://matrix.org/_matrix/media/r0/download/matrix.org/LgoPSGgepUoCkyHXicQLJFii >
01:46 PM Lcvette: these settings
01:46 PM Wandoo1980|Sebas: I did that for a test
01:46 PM Lcvette: this is in inches
01:46 PM Lcvette: if you are metric it will be WAY to small
01:47 PM Lcvette: step off width would only be .5mm
01:47 PM Lcvette: make them equivalent to the numbers shown but in mm
01:47 PM Lcvette: so 0.5000 would be 13mm
01:47 PM Wandoo1980|Sebas: It works fine in mm ;) i am not on the machine
01:47 PM Lcvette: so change to 13
01:47 PM Wandoo1980|Sebas: Yes, that works fine
01:48 PM Lcvette: the step off width determines how far past the hint width the probe travels before going down
01:49 PM Wandoo1980|Sebas: Damn, I have to learn English better 😅
01:49 PM Lcvette: so if hint width is 100mm then the actual probe width would become 126mm
01:49 PM Lcvette: look at the probe help
01:49 PM Lcvette: it has pictures that may better fill the language barrier gap
01:49 PM Wandoo1980|Sebas: Yes, but that is not the problem, that works fine
01:50 PM Wandoo1980|Sebas: Also the parameter
01:50 PM Lcvette: you said it doesn't go wide wnough
01:50 PM Wandoo1980|Sebas: But if you have a 100mm or 4" vise
01:50 PM Lcvette: then you put in 100mm in the hint
01:51 PM Lcvette: the step off width takes care of the extra travel before going down and back in to probe the side
01:51 PM Wandoo1980|Sebas: And measure it like in the video
01:52 PM * Lcvette uploaded an image: Screenshot_2019-10-10_14-46-22.png (97KB) < https://matrix.org/_matrix/media/r0/download/matrix.org/uieZAmiPMUbAjXkQAbyGNOiC >
01:53 PM * Wandoo1980|Sebas uploaded an image: IMG_20191009_184503.jpg (3147KB) < https://matrix.org/_matrix/media/r0/download/jauriarts.org/YVtwbIjqKZovOkIxjQqmGlmd >
01:53 PM Wandoo1980|Sebas: In this screen
01:53 PM Tom_L: Lcvette, https://doc.qt.io/qtforpython/overviews/timers.html?highlight=timer
01:54 PM Lcvette: you have wrong probing parameter settings
01:54 PM Tom_L: https://doc.qt.io/qtforpython/PySide2/QtCore/QTimer.html?highlight=timer
01:55 PM Wandoo1980|Sebas: exactly, that was intentional 😅
01:56 PM Wandoo1980|Sebas: I have tested it to see if the Z axis stops when the X axis does not travel far enough
01:57 PM * Lcvette uploaded an image: Screenshot_2019-10-10_14-50-29.png (53KB) < https://matrix.org/_matrix/media/r0/download/matrix.org/oUQSNebWNmTtbgiLgRoQyfOl >
01:57 PM Lcvette: i would imagine this would be where you wanted to start your probing parameters in metric
01:57 PM Lcvette: have you tried?
01:58 PM Tom_L: Lcvette, you need to define start() and stop() events for the timer
01:58 PM Lcvette: Wandoo1980 | Sebastian | End-CNC: ^^^
01:58 PM Tom_L: you need to start the timer
01:59 PM Wandoo1980|Sebas: I did this for the dumbest user 😂
01:59 PM Lcvette: ?
01:59 PM Lcvette: im having trouble understanding what the issue is
01:59 PM Lcvette: sorry if im not getting it
02:00 PM Wandoo1980|Sebas: to see if the axle stops when something is not working properly
02:00 PM Wandoo1980|Sebas: No problem, my english is not the best 😅
02:01 PM Lcvette: (step off width) + (x or y hint) + (step off width) = total probe width travel during the routine
02:01 PM Lcvette: probing parameter step off width is 15 +100mm vice + step Off width parameter 15 equals 130mm total width
02:02 PM Lcvette: Wandoo1980 | Sebastian | End-CNC: ^^
02:02 PM Lcvette: any more helpful?
02:03 PM Wandoo1980|Sebas: the screen works great! I only test scenarios to see what happens when a human makes a mistake 😁
02:04 PM Lcvette: video the error maybe
02:05 PM Lcvette: once the persistent boxes are working, the values you enter in the probe parameter settings will remain
02:05 PM Wandoo1980|Sebas: Unfortunately, I am currently not at the machine
02:06 PM Lcvette: they will stay what you entered even agfter restart
02:06 PM Lcvette: hazzy is working on that
02:06 PM Lcvette: i will take some footage maybe to show the parameter input effect onthe probing routine
02:07 PM Lcvette: i need two cameras one for the screen and one for the machine
02:07 PM Wandoo1980|Sebas: but if you make too narrow a width for the vise in your bill, the axis moves down too early
02:07 PM Lcvette: and to learn how to video edit
02:07 PM Lcvette: lol
02:07 PM Lcvette: the width for the vice should be the exact vise width or close
02:08 PM Lcvette: you have the tep off width parameter that add the additiional probe travel
02:08 PM Lcvette: but you must set it correctly
02:08 PM Wandoo1980|Sebas: Yes, that's it 🙂
02:08 PM Lcvette: yours is set to inch numbers
02:08 PM Lcvette: you need to change to equivalent metric numbers
02:09 PM Wandoo1980|Sebas: and I have tested what happens if I enter wrong parameters
02:09 PM Lcvette: what is your oparameter settings for step off width?
02:10 PM Lcvette: in your picture it shows .375
02:10 PM Lcvette: which is 3/8"
02:10 PM Wandoo1980|Sebas: to see if the machine stops when the probe is triggered when a wrong axis is running
02:10 PM Lcvette: but if metric is only 0.375mm
02:10 PM Wandoo1980|Sebas: Yes, that was only for a post
02:10 PM Lcvette: very small
02:11 PM Wandoo1980|Sebas: just to show the screen in which I intentionally entered a wrong value
02:11 PM Lcvette: so ttoal width during probing operation would be 100.75mm
02:11 PM Lcvette: would be too narrow
02:11 PM Lcvette: would do as you say and hit z because its not big enough
02:11 PM Wandoo1980|Sebas: exactly
02:11 PM Lcvette: if 15mm
02:11 PM Lcvette: the it becomes 130mm\plenty of room
02:11 PM Wandoo1980|Sebas: yes
02:11 PM Lcvette: ok
02:12 PM Lcvette: do you know the probe help to define the parameters?
02:12 PM Wandoo1980|Sebas: but if you type 70mm
02:12 PM Lcvette: then it should stop before because you over travel the max xy distance
02:12 PM Wandoo1980|Sebas: the x axis does not travel far enough
02:13 PM Lcvette: why would you put 70mm for a 100mm piece?
02:13 PM Wandoo1980|Sebas: and the axle moves on the vise and the probe triggers when the z is still running
02:14 PM Wandoo1980|Sebas: to test what happens then
02:14 PM Lcvette: you have to have the values pretty close or you need to widen the paremeters
02:14 PM Wandoo1980|Sebas: to see if the axis then stops
02:14 PM Lcvette: mak max xy dist bigger and step off width bigger
02:14 PM Lcvette: does it not stop?
02:14 PM Wandoo1980|Sebas: Yes, i know ^^
02:14 PM Lcvette: it should stop whenever the probe is triggered?
02:15 PM Lcvette: if not that is a bug that needs fixing
02:15 PM Wandoo1980|Sebas: no
02:15 PM Wandoo1980|Sebas: it goes down ^^
02:15 PM Lcvette: :o
02:15 PM Lcvette: that is a problem
02:15 PM Wandoo1980|Sebas: that was what i meant 🙂
02:15 PM Lcvette: z does not stop when triggering because of too short a travel in x?
02:16 PM Lcvette: hmmmm
02:16 PM Lcvette: need to find a solution for that
02:16 PM Wandoo1980|Sebas: exactly
02:17 PM Lcvette: thought hazzy told me that anytime the probe too is in a trigger should stop movement
02:17 PM Wandoo1980|Sebas: I only showed the picture, so that you can see in which picture I am
02:17 PM Wandoo1980|Sebas: 😅
02:18 PM Wandoo1980|Sebas: That's exactly what I would have expected, but to test whether it really is, I have given wrong values
02:18 PM Lcvette: going to try an replicate in sim
02:18 PM Wandoo1980|Sebas: With very slow motion
02:19 PM Lcvette: sim doesn't matter
02:19 PM Lcvette: no hardware involved
02:19 PM * Wandoo1980|Sebas uploaded an image: unknown.png (230KB) < https://matrix.org/_matrix/media/r0/download/jauriarts.org/QlgYsFKwcKfTNeKzGXzfiEuK >
02:19 PM * Lcvette uploaded an image: Screenshot_2019-10-10_15-13-42.png (12KB) < https://matrix.org/_matrix/media/r0/download/matrix.org/NvvOwbUGyhYpUzcHvIatolVT >
02:20 PM Wandoo1980|Sebas: Here I entered the wrong width
02:20 PM Lcvette: touch is probe trigger for simulating
02:22 PM Wandoo1980|Sebas: I deliberately provoked this to find any mistakes. If you enter everything correctly, it works wonderfully, as in the video
02:22 PM Lcvette: thank you
02:22 PM Lcvette: good bug report!
02:22 PM Lcvette: took a little to understand but we got there and now will fix
02:23 PM Wandoo1980|Sebas: i have to apologize for my english, i am working on it 😅
02:24 PM Lcvette: you speak far better English then I speak German
02:24 PM Lcvette: lol
02:24 PM Lcvette: no apologies necessary
02:25 PM Wandoo1980|Sebas: thanks a lot 🙂
02:25 PM Lcvette: for a quick solution, you can change your max z distance to a small number
02:26 PM Lcvette: it should stop it i think*
02:26 PM Lcvette: testing that now
02:26 PM Wandoo1980|Sebas: ok 🙂
02:26 PM Wandoo1980|Sebas: In the next few days I will test a few other scenarios to see if I can find anything else.
02:29 PM Lcvette: thanks!
02:29 PM Lcvette: \o/
02:29 PM Lcvette: wandoo the brave tester!
02:32 PM Wandoo1980|Sebas: 😅
02:42 PM Lcvette: Tom_L (@freenode_Tom_L:matrix.org): but I don't know how to make it an expression in the rules editor in the gui
02:59 PM TurBoss: vtk 3d plot is bugged
02:59 PM TurBoss: there is a small offset in the drawn path and the followed one
03:32 PM Tom_L: TurBoss, how do you tie widgets to hal events?
03:32 PM Tom_L: halui./program.is-idle
03:32 PM Tom_L: halui.program.is-idle
03:33 PM Tom_L: Lcvette, i tie my timer start to that thru a not gate
03:33 PM Tom_L: so when it goes off idle the timer starts
03:34 PM Tom_L: net prog-running not.0.in <= halui.program.is-idle
03:34 PM Tom_L: the not.0.out goes to the timer start
03:35 PM Tom_L: net cycle-timer time.1.start <= not.0.out
03:49 PM Tom_L: mmm where did my sims go?
03:51 PM TurBoss: not on desktop
03:51 PM TurBoss: but the atc widget does
03:51 PM Tom_L: i wanted to edit mini but i can't find it now
04:00 PM TurBoss: editvcp mini
04:00 PM Tom_L: i found it
04:00 PM Tom_L: is there a qt timer widget?
04:02 PM Lcvette: but how to you turn that into an expression in the rules editor?
04:04 PM TurBoss: i dont know rules
04:04 PM Lcvette: :o
04:04 PM Lcvette: turboss knows everything
04:04 PM TurBoss: lol
04:04 PM Tom_L: TurBoss, how do you get this in designer as a widget?
04:04 PM Tom_L: https://doc.qt.io/qtforpython/PySide2/QtCore/QTimer.html?highlight=qtimer
04:06 PM Lcvette: cycle timer is already in the rules
04:06 PM Tom_L: where?
04:06 PM Lcvette: status:cycle_time
04:06 PM Lcvette: double click the box i told you too
04:06 PM Lcvette: then select cycle_timer
04:07 PM Lcvette: it shows i made a channel for cycle_time its a float
04:07 PM Lcvette: then in the expression line at the bottom is where you do the cool things to it to make it work
04:08 PM Lcvette: Tom_L: https://qtpyvcp.kcjengr.com/tutorials/widget_rules.html
04:11 PM Lcvette: Tom_L: i bet you could figure thie rules out based on your previous cycle time setup
04:11 PM Lcvette: jt also knows rules
04:11 PM Tom_L: you need access to the hal pins
04:11 PM Tom_L: don't know how to do that
04:12 PM Lcvette: what function do you need?
04:12 PM Tom_L: i pasted it above
04:12 PM Lcvette: hazzy tied in most of the major stuff in linuxcnc to the rules editor
04:15 PM Lcvette: status, settings, position
04:16 PM Lcvette: more
04:16 PM Lcvette: if you would take a look
04:16 PM Lcvette: add a channel then type the letter s a list pops up
04:30 PM Tom_L: not finding the signal i need
04:30 PM Tom_L: sry
04:31 PM Tom_L: closest is status:paused and that's not it
04:41 PM Tom_L: looked in the signal editor too
04:47 PM TurBoss: what you trying to achieve?
04:47 PM TurBoss: https://doc.qt.io/qt-5/qtimer.html+
04:48 PM TurBoss: https://doc.qt.io/qt-5/qtimer.html
04:59 PM Lcvette: rthe timer
04:59 PM TurBoss: to trigger something?
05:00 PM Lcvette: the timer for run time
05:00 PM Lcvette: cycle_time
05:00 PM Lcvette: it never worked
05:00 PM TurBoss: exist
05:00 PM Lcvette: was always just a decorative label
05:00 PM TurBoss: ?
05:00 PM Lcvette: yes there is a status:cycle_time
05:01 PM Lcvette: in the rules editor
05:01 PM Lcvette: but lcvette doesn't know how or what to do with the rules
05:01 PM TurBoss: taking a look
05:01 PM Lcvette: \o/
05:11 PM Tom_L: i was looking for a pin halui.program.is-idle to connect the start timer to
05:14 PM jthornton: you want an idle timer?
05:14 PM Tom_L: program run time
05:14 PM Tom_L: i invert the idle to show the program is running
05:15 PM Tom_L: http://tom-itx.no-ip.biz:81/~webpage/cnc/configs/NEW_MILL_2.8/new_mill.hal
05:15 PM Tom_L: net prog-running not.0.in <= halui.program.is-idle
05:15 PM Tom_L: http://tom-itx.no-ip.biz:81/~webpage/cnc/configs/NEW_MILL_2.8/postgui.hal
05:15 PM Tom_L: net cycle-timer time.1.start <= not.0.out
05:16 PM Lcvette: cycle timer
05:16 PM Tom_L: i just don't know how to convert that to qtpyvcp speak
05:16 PM Lcvette: maybe a timer for each tool like tom-l made
05:17 PM Tom_L: same timer, it just starts over
05:17 PM Tom_L: http://tom-itx.no-ip.biz:81/~webpage/cnc/screenshot.png
05:17 PM Tom_L: "Cycle Times"
05:18 PM Tom_L: also, i though somebody modded it to not count tool changes but i might be mistaken
05:18 PM jthornton: they added a pause feature
05:19 PM jthornton: there is a halui program is idle pin
05:19 PM Tom_L: i'm using it
05:20 PM Tom_L: net prog-running not.0.in <= halui.program.is-idle
05:20 PM Tom_L: and invert it to start when it is not idle
05:21 PM Tom_L: i tried to find that somewhere in the developer windows but wasn't able to
05:22 PM TurBoss: ```
05:22 PM TurBoss: cycle_time
05:22 PM TurBoss: (returns float) - thread period
05:22 PM TurBoss: is tgo
05:23 PM TurBoss: * is this the whole program time?
05:23 PM * hazzy-m is home early!
05:23 PM Lcvette: dnuno
05:23 PM Lcvette: o/
05:23 PM TurBoss: \o
05:23 PM hazzy-m: o/
05:23 PM Tom_L: one of mine is and one just counts the current tool time
05:23 PM Lcvette: o\
05:23 PM Tom_L: ask hazzy-m. he knows
05:23 PM Lcvette: hey ho hey ho hey ho
05:24 PM hazzy-m: what do I know? :D
05:24 PM Lcvette: everything
05:24 PM Lcvette: you are the wizard of oz
05:24 PM hazzy-m: lol
05:24 PM Lcvette: the great and powerful
05:24 PM Tom_L: JT-Shop, it's gettin cold here
05:25 PM jthornton: we are getting that tomorrow night down to 36f
05:26 PM hazzy-m: oh, we need a cycle time and part count plugin
05:26 PM Tom_L: 48�F currently
05:26 PM hazzy-m: Tom_L: send some of it down here!
05:26 PM Tom_L: and dropping
05:28 PM hazzy-m: we just installed a machine for a customer in St. Louis and he keeps complaing about the tempertures falling, getting depressed, grumpy and hard to work with lol
05:31 PM Tom_L: tried to find that signal in the rules editor but didn't see it
05:31 PM Tom_L: "status:program-is-idle" or such
05:32 PM hazzy-m: status:interp_idel should do
05:32 PM Tom_L: to tell when the program is actually cutting
05:33 PM Tom_L: i see status:interp_state
05:33 PM Tom_L: but no status:interp_idle
05:34 PM Lcvette: yeah
05:34 PM Lcvette: \o/
05:34 PM Lcvette: hazzy knows it!
05:34 PM hazzy-m: Tom_L: sorry
05:34 PM * hazzy-m is getting rusty
05:35 PM hazzy-m: use `status:interp_state.text == "idle"`
05:35 PM hazzy-m: I think that is the correct syntax
05:35 PM Tom_L: in the expression?
05:35 PM hazzy-m: yes
05:36 PM Tom_L: "idle" goes in quotes?
05:36 PM Tom_L: that must be defined T F somewhere else
05:36 PM Tom_L: true/false 1/0 whatever
05:37 PM Tom_L: expression not valid
05:37 PM Lcvette: We need an expression doc
05:37 PM Tom_L: type is int in the channel type
05:41 PM jthornton: hazzy-m, flew the camera drone a few times today, flies nice
05:42 PM Tom_L: tie it to google maps to plot your journey
05:42 PM Tom_L: i suppose it logs it's coordinates if it has a 'return home' feature
05:45 PM jthornton: yea if it has a good enough GPS lock when you lift off that is home and it has a Return To Home button... but the lowest it will RTH is 20 meters!
05:45 PM jthornton: if it's within 20 meters of home it just lands without moving to home
05:46 PM jthornton: that's 65' for us
07:23 PM * Lcvette sent a long message: < https://matrix.org/_matrix/media/r0/download/matrix.org/TfzojCwwyjPnLAKaoyVNtwZb >
07:23 PM Lcvette: lcvetyte typed out the list
07:24 PM Lcvette: * lcvette typed out the list
07:25 PM Tom_L: nothing else to do?
07:26 PM Lcvette: we need docs
07:26 PM Lcvette: on this
07:26 PM Tom_L: true
07:26 PM Lcvette: i don't know how to use the rules
07:26 PM Lcvette: and would like to know
07:27 PM Lcvette: need a list of possible expression variables to use
07:27 PM Lcvette: so i can begine to put some form of combination use together that is understandable
07:27 PM Lcvette: hazzy o9nce asked me to look at this and aked if it seemed easy
07:27 PM Lcvette: to me it is not
07:28 PM Tom_L: it would be nice to know the 'rules' for expressions
07:28 PM Tom_L: what is valid and not valid
07:28 PM Lcvette: agreed
07:28 PM Lcvette: i think that will make it easier for people to undersdtand
07:29 PM Lcvette: as well as how and when to use certain expressions
07:29 PM hazzy-m: JT wrote some pretty good tutorials on using the rules
07:29 PM Lcvette: lol
07:29 PM Lcvette: not even close
07:29 PM Lcvette: they are good if you know expressiosn
07:30 PM Tom_L: hazzy-m i was looking for them and can't seem to find em
07:30 PM Lcvette: other then that they are a brief overview
07:30 PM Tom_L: the possibilities are beyond the scope of any turorial
07:31 PM Tom_L: but a few good examples would go a long ways
07:31 PM hazzy-m: they use standard python expressions, so its easy if you know python, but not everyone does!
07:32 PM hazzy-m: yes, we do need better examples
07:32 PM hazzy-m: or more examples
07:32 PM Tom_dev: https://qtpyvcp.kcjengr.com/install/index.html
07:32 PM Tom_dev: where are jt's turorials?
07:32 PM Lcvette: https://qtpyvcp.kcjengr.com/components/index.html
07:32 PM hazzy-m: https://qtpyvcp.kcjengr.com/tutorials/widget_rules.html
07:33 PM Tom_dev: that didn't seem all that helpful to me
07:33 PM Tom_dev: it shows the 'where to go' but not the 'what to do'
07:34 PM Lcvette: yeah like hazzy said its easy if you know pythos
07:34 PM Lcvette: * yeah like hazzy said its easy if you know python
07:34 PM Lcvette: seems to be the handicap i have everywhere outside of the design work is not knowing pythos
07:35 PM Lcvette: but in order to make the gui builder more universally easy to use, most will not know python and should have access to ways to do things that doesn't require it
07:35 PM Lcvette: or docs that make whats hard to understand easier for us dumb dumbs
07:38 PM Lcvette: i don't m,ind helping with docs
07:39 PM Lcvette: unfortunately when it comes to the code stuff.. its the blind leading the blind so to speak
07:52 PM Lcvette: i think im gonna sign up for a class somewhere for python
07:53 PM Lcvette: i tried the online classes and if i do hello world one more time ....
07:53 PM Lcvette: i get to the bottom and it showed me what to do but not how it does it which im the type person who needs to know that to understand what is going on
07:54 PM Lcvette: i need like a breakdown of one of our py files
07:54 PM Lcvette: explaining what everything is doing
07:54 PM Lcvette: then i woukld understand better
07:57 PM hazzy-m: yea, i understand that
07:57 PM hazzy-m: the rules are even a bit cnfusing for me since its been a little while since I wrote them
07:59 PM Lcvette: lol
07:59 PM Lcvette: i remember when you wrote them you were so excited
07:59 PM Lcvette: and you shoved them to me and said wha do ya think
07:59 PM Lcvette: hahahaha
08:00 PM Lcvette: i remember thinking omg... i have no clue what hes got goin on here
08:00 PM Lcvette: unfortunately nothing has chasnged since then..lol
08:01 PM Lcvette: but for the ones that have a good example i can soemtimes tinker with it and find whats going on but thats not very frequently
08:02 PM Lcvette: so anyhow, i figured i would start putting together a list of definitions at least of what all the options do and an example for how to use it
08:02 PM Lcvette: or maybe multiple options on how to use it if that be the case
08:03 PM Lcvette: then maybe at least if you don't know it one of the examples is bound tobe close enough to make sense and be able to adjust to suit
08:17 PM hazzy-m: jthorntondid a great job documenting the data channels: https://qtpyvcp.kcjengr.com/plugins/status.html#qtpyvcp.plugins.status.Status.interp_state
08:17 PM hazzy-m: for example that is what Tom was looking for
08:18 PM Tom_L: if you know where to look :)
08:18 PM Tom_L: i was going back thru his tutorial again
08:18 PM hazzy-m: so it should have been `status:interp_state?string == "Idle"`
08:19 PM hazzy-m: we needs some docs for the docs :D
08:19 PM Tom_L: what would it be if you wanted to test for the opposite state?
08:19 PM hazzy-m: `status:interp_state?string != "Idle"`
08:19 PM hazzy-m: `!=` means not equal
08:19 PM Tom_L: yes just like C
08:19 PM Tom_L: but idle goes in quotes?
08:20 PM hazzy-m: yes, most of the syntax is very close to C, if not identical
08:20 PM hazzy-m: the "Idle" is in quotes because it is a string
08:20 PM Tom_L: it's been a while...
08:20 PM Tom_L: yes
08:20 PM Tom_L: i wonder if those are case sensitive
08:20 PM hazzy-m: you could also use `status:interp_state == 1` which give the same result
08:21 PM Tom_L: i did that
08:21 PM Tom_L: i think i got an error but i can't remember
08:21 PM hazzy-m: the rules editer should give you some hints as what to do
08:21 PM Tom_L: since it's a string
08:22 PM hazzy-m: what were you trying to use the rule to do?
08:22 PM Tom_L: i wouldn't have figured interp to be program.is-xxx though
08:22 PM TurBoss: o/
08:22 PM Tom_L: i want to know when the gcode program is running for a cycle timeer
08:23 PM hazzy-m: `status:interp_state == 1` will result in a booling True or False value, so you can only use it for boolian rules, e.g. enabling puttons, setting LEDs on or off etc.
08:23 PM Tom_L: so i need something to trigger the timer.start and stop
08:23 PM hazzy-m: ah, that makes sence
08:24 PM hazzy-m: probably best to write a plugin that watches the apropriate status items and keeps track of the time
08:24 PM Tom_L: i'm doing that in axis currently
08:24 PM * Tom_L assigns that task to hazzy-m
08:25 PM * hazzy-m adds the task to the gowing list :)
08:26 PM Lcvette: hazzy: > [jthornton](https://matrix.to/#/@freenode_jthornton:matrix.org)did a great job documenting the data channels: https://qtpyvcp.kcjengr.com/plugins/status.html#qtpyvcp.plugins.status.Status.interp_state
08:26 PM Tom_L: Lcvette was trying to struggle thru it too
08:26 PM Lcvette: yes he did!
08:26 PM TurBoss: I think that the offsetstable pluging shoudl be renamed to params plugin...
08:27 PM Tom_L: i don't
08:27 PM TurBoss: does params handle more data?
08:27 PM Tom_L: they are work offsets
08:27 PM Tom_L: the .var file contains other things beside just offsets
08:28 PM Tom_L: but i think that is the bulk of it
08:28 PM hazzy-m: Tom_L: it includes all sorts of other persisten interp data
08:28 PM Tom_L: question.
08:28 PM TurBoss: the glo thing still updated?
08:28 PM Lcvette: but i think throwing a wider blanket over it will be more confusing to the end user
08:29 PM Tom_L: so when i start a new project and save the .ui and make the .py from it, where is the vcp file?
08:29 PM Lcvette: better to wrap each instance with its own name
08:29 PM Tom_L: err pyc
08:29 PM Tom_L: whatever it's called
08:30 PM Lcvette: although the plugin will be there regardless and the end user i guess won't know its being used
08:30 PM Lcvette: is that true?
08:30 PM hazzy-m: TurBoss: I agree that the offsettable plugin should be renames to params plugin, the ofsets table widget will still keep the same name so won;t be confusing
08:30 PM Lcvette: ie there will still be an offsets table it just uses the parameter plugin?
08:30 PM TurBoss: ok!
08:30 PM TurBoss: yes that
08:30 PM Lcvette: ok
08:30 PM Lcvette: then that makes sense
08:31 PM Lcvette: as long as what the end user deals with is still broken out more compartmentally i think that would be fine
08:31 PM hazzy-m: Tom_L: the pyc file is a Py cached file, it is a bite compiled python that is loaded the next time the file is run to save time interpreting it again
08:31 PM * TurBoss has to firgure the vtk bugs
08:31 PM hazzy-m: it is automagicaly generated
08:31 PM Tom_L: after running linuxcnc?
08:32 PM hazzy-m: after launching the VCP for the fisrt time
08:32 PM Tom_L: yeah you'd think i already knew that... my bot does that
08:32 PM hazzy-m: :)
08:33 PM Tom_L: i just couldn't figure out why it wasn't on the editvcp picker
08:33 PM * hazzy-m heads to catch a few Zzzz's
08:33 PM TurBoss: night man
08:33 PM Lcvette: night hazzy
08:33 PM hazzy-m: Thanks for your help TurBoss!
08:34 PM Lcvette: zTom_l did you figure out the timer?
08:34 PM hazzy-m: Lcvette: night!
08:34 PM TurBoss: Tom_L: if you just run editvcp
08:34 PM Lcvette: o/
08:34 PM TurBoss: you may be able to navigate to where your vcp is stored
08:34 PM Tom_L: Lcvette, no there needs to be a way to access it's start() and stop() functions
08:34 PM Tom_L: and i haven't figured that out
08:35 PM Tom_L: https://doc.qt.io/qtforpython/PySide2/QtCore/QTimer.html?highlight=qtimer
08:35 PM Lcvette: wonder if we could use code from the gcode
08:36 PM Tom_L: not what i would do
08:36 PM Lcvette: ie cycle start triggers with signasls and slots and then m6 or m30 stops it
08:36 PM Lcvette: ah ok
08:36 PM Tom_L: interp is your signal
08:37 PM Tom_L: plug it into the timer start() stop() and you'll have it
08:41 PM Lcvette: https://qtpyvcp.kcjengr.com/plugins/notifications.html
08:41 PM Lcvette: what about this?
08:41 PM TurBoss: notifications are begin reworked
08:42 PM TurBoss: thoose are the popups
08:44 PM TurBoss: iirc
08:44 PM Lcvette: ok
08:47 PM Tom_L: it needs to be a widget
08:48 PM TurBoss: delphi used to have floating widgets with elemets like that
08:48 PM Lcvette: status:interp_state
08:48 PM Lcvette: ?
08:48 PM Tom_L: 'status:interp_state != "idle"'
08:48 PM * TurBoss uploaded an image: image.png (153KB) < https://matrix.org/_matrix/media/r0/download/matrix.org/WahAMNNoteNVLlciVfgOdGaa >
08:48 PM Tom_L: Qtimer:start()
08:49 PM * Lcvette uploaded an image: Screenshot_2019-10-10_21-42-53.png (29KB) < https://matrix.org/_matrix/media/r0/download/matrix.org/FYcmFRfVaHWbJhTLywpPAScb >
08:50 PM Lcvette: 'status:interp_state != "idle"'Qtimer:start() str(ch[0])
08:52 PM Lcvette: ?
08:57 PM * Lcvette uploaded an image: Screenshot_2019-10-10_21-51-13.png (41KB) < https://matrix.org/_matrix/media/r0/download/matrix.org/XrDSDcKuPpJIGspUmDVHKUXv >
08:57 PM Lcvette: eh timer is not critical i guess
08:58 PM Tom_L: heh
08:58 PM Lcvette: will just use fusion output estimate and wall clock
08:58 PM Lcvette: lol
08:58 PM Lcvette: i don't see it
08:58 PM Tom_L: it's doable
08:59 PM Lcvette: i dunno how to put things together in the expression box to make it work
08:59 PM Lcvette: i tested several variations and nada
08:59 PM Tom_L: i think it needs more than that
08:59 PM Tom_L: i think it needs some .py code to make it work
09:00 PM Lcvette: what is interp_state
09:01 PM Lcvette: is that readong the gcode file of the program?
09:01 PM Tom_L: state of the rs274 interpreter
09:02 PM Lcvette: so what state of the interp_state would stop the timer?
09:03 PM Tom_L: idle
09:03 PM Lcvette: idle starts and stops it?
09:03 PM Tom_L: uh huh
09:04 PM Tom_L: but you need access to the start stop functions of qtimer
09:04 PM Lcvette: what is cycle time
09:04 PM Lcvette: status:cycle_time
09:04 PM Tom_L: nothing i know of
09:05 PM Lcvette: https://qtpyvcp.kcjengr.com/plugins/notifications.html
09:07 PM Lcvette: Tom_L: ^^^
09:07 PM Tom_L: you asked about that already
09:07 PM Lcvette: this seems to touch on that notion of it needing python
09:08 PM Lcvette: http://linuxcnc.org/docs/html/config/python-interface.html
09:08 PM Tom_L: <TurBoss> thoose are the popups
09:08 PM Tom_L: <TurBoss> iirc
09:08 PM Lcvette: sorry address did something wierd when i double clicked
09:10 PM Tom_L: http://linuxcnc.org/docs/2.8/html/man/man9/time.9.html
09:10 PM Tom_L: you want something like that to happen
09:12 PM Tom_L: recent versions have added a pause feature to it
09:12 PM Lcvette: so do it in hal instead of code?
09:12 PM Tom_L: it's a time.comp
09:12 PM Tom_L: a user comp
09:13 PM Tom_L: i don't know if you have hooks to read the time function in qtpyvcp or not
09:14 PM Tom_L: if not, the QTimer would do a similar thing
09:14 PM Tom_L: with a little code
09:14 PM Tom_L: i don't know python.
09:14 PM Tom_L: i barely know anything about qtpyvcp
09:15 PM Lcvette: Me too from a linuxcnc link perspective
09:16 PM Tom_L: not enough time in a day for me to learn it either
09:28 PM * Lcvette uploaded an image: _20191010_222227.JPG (6KB) < https://matrix.org/_matrix/media/r0/download/matrix.org/XeKPdaxMZmRyvBVJohJWNfCW >
09:28 PM Lcvette: Lol, not what I thought it meant
09:29 PM Lcvette: Tom_L (@freenode_Tom_L:matrix.org): ∆∆∆
10:44 PM Tom_L: hah
10:44 PM Lcvette: /o\
10:44 PM Tom_L: so we need code to make a timer for what you want
10:45 PM Lcvette: yup looks that way
10:45 PM Tom_L: it could be possible to hook into the hal component. i don't know... that's something TurBoss or hazzy-m could answer
10:45 PM Tom_L: and if not, Qtimer would be the backbone of the 'widget'
10:46 PM Lcvette: yeah its beyond my knowledge scop once it requires coding
10:47 PM Tom_L: https://doc.qt.io/qt-5/qtime.html
10:47 PM Tom_L: or possibly that
10:47 PM Tom_L: but that one is for C++
10:47 PM Lcvette: i search for pyqt
10:47 PM Lcvette: seems to give more relevant answers
10:48 PM Lcvette: but i usualy do that when helping the turboss or hazzy find solutions to issues
10:48 PM Lcvette: thats my extent of code input
10:48 PM Lcvette: lol
10:49 PM Tom_L: https://doc.qt.io/qtforpython/PySide2/QtCore/QTime.html?highlight=qtime
10:49 PM Tom_L: there's the python counterpart
10:51 PM Tom_L: https://www.programcreek.com/python/example/99593/PyQt5.QtCore.QTime
10:52 PM Lcvette: do you understand python?
10:52 PM Tom_L: somewhat
10:52 PM Tom_L: i doubt i could write any
10:52 PM Lcvette: me either
10:52 PM Lcvette: lol
10:52 PM Lcvette: so we will await the python heros
10:52 PM Tom_L: but you learn by example
10:53 PM Tom_L: you can. i'm gonna see what i can find
10:53 PM Tom_L: i probably won't get far
10:53 PM Lcvette: im game to help
10:53 PM Lcvette: just not sure what we need or how to tie it in to hal
10:56 PM Tom_L: https://het.as.utexas.edu/HET/Software/html/qtime.html
10:56 PM Tom_L: Member Function Documentation
10:56 PM Tom_L: for various return values
10:57 PM Tom_L: int QTime::elapsed () const
11:00 PM Tom_L: so on start you take a snapshot of time then add to that each function call to get elapsed time
11:00 PM Lcvette: ok
11:01 PM Tom_L: it would be nice if the function had a pause feature for things like tool changes etc
11:01 PM Lcvette: i ws just looking in designer to see what we had available already made up
11:01 PM Tom_L: nothing
11:02 PM Lcvette: there is a HalLabel
11:02 PM Tom_L: not that i could find
11:04 PM Lcvette: when you did yours on axis, you just triggered it with hal pins?
11:04 PM Lcvette: forgive me i know as little about hal as i do python
11:05 PM Tom_L: yes
11:05 PM Tom_L: i used halui.program.is-idle to tell the timer when to start
11:06 PM Tom_L: i inverted the signal so that it would indicate when it was not paused
11:06 PM Tom_L: the description under time shows it
11:07 PM * Lcvette sent a long message: < https://matrix.org/_matrix/media/r0/download/matrix.org/RFDGTcCfsnnjlYhNJtzNkZbn >
11:07 PM Lcvette: this section only?
11:07 PM Lcvette: right?
11:07 PM Tom_L: yeah the rest is in the main ini
11:08 PM Tom_L: where the pin hooks to the not.0 gate
11:08 PM Tom_L: http://linuxcnc.org/docs/2.8/html/man/man9/time.9.html
11:09 PM Tom_L: jt explains the whole thing there
11:10 PM Lcvette: so can the HalLabel use it?
11:10 PM Tom_L: https://doc.qt.io/qt-5/designer-widget-mode.html#
11:10 PM Lcvette: in conjunction with a rule for the format
11:10 PM Tom_L: it displays it
11:10 PM Tom_L: i don't know
11:11 PM Lcvette: the HalLabel uses u32, float, s32, or bit
11:12 PM Lcvette: i see those in JT's paper you just sent but i don't know anything much about them
11:12 PM Lcvette: just throwing ideas out
11:13 PM Tom_L: that goes in the postgui file in lcnc
11:14 PM * Lcvette sent a long message: < https://matrix.org/_matrix/media/r0/download/matrix.org/mhhKBGCVOGPGmbCKztjxcnre >
11:14 PM Lcvette: this all can be done in the property editor
11:14 PM Lcvette: there is a text format entry that can be coded to time format, and it uses the stylesheet for
11:15 PM Lcvette: font, size, color etc
11:15 PM Lcvette: and thent he label could be triggered by the hal code stuff?
11:15 PM Lcvette: like i said i dunno how it all works but im trying
11:16 PM Tom_L: bedtime
11:16 PM Tom_L: gnite
11:16 PM Lcvette: night
11:17 PM Tom_L: https://doc.qt.io/qt-5/designer-widget-mode.html#
11:17 PM Tom_L: you can make your own widget