#hazzy | Logs for 2018-12-12
Back
[00:19:58] -!- JT-Shop2 has quit [Read error: Connection reset by peer]
[01:32:36] <Not-97e5> [02QtPyVCP] 07Kurt Jacobson pushed 036 commits to 03YAMLMenus [+0/-0/±12] 13https://gitlab.com/Hazzy/qtpyvcp/compare/395f48dfec39af953b896cf7419e07ef65abdd21...894ad934337f24c17ae9b654a0ec14500ff5f71e
[01:32:38] <Not-97e5> [02QtPyVCP] 07Kurt Jacobson 033bfd8bd - menu actions and more clean up
[01:32:39] <Not-97e5> [02QtPyVCP] 07Kurt Jacobson 037064827 - fake ok and bindOk for program.load action
[01:32:41] <Not-97e5> [02QtPyVCP] 07Kurt Jacobson 037efce57 - clean up YAML config files
[01:32:42] <Not-97e5> [02QtPyVCP] ... and 3 more commits.
[01:33:10] <hazzy-m> gn8
[02:18:45] -!- JT-Shop2 has joined #hazzy
[04:26:59] <hazzy-m> we just had an earthquake, did any of y'all notice it too?
[04:28:31] <hazzy-m> It was shaking pretty good, certainly the biggest I have experienced
[09:57:13] -!- logs has joined #hazzy
[09:57:13] -!- mode/#hazzy [+o logs] by ChanServ
[09:57:46] <Lcvette> No
[09:57:50] <Lcvette> I slept through it
[09:57:53] <Lcvette> Lol
[09:59:32] <hazzy-m> I would probably have to except I have all kinds of junk on my desk that rattles
[09:59:33] <hazzy-m> lol
[10:00:38] -!- logs has joined #hazzy
[10:00:39] -!- mode/#hazzy [+o logs] by ChanServ
[10:19:28] <Lcvette> hazzy
[10:20:13] <Lcvette> is there a keyboard shortcut for capturing screenshots of the enture screen?
[10:20:21] <Lcvette> for when you are in fullscreen mode?
[10:20:36] <Lcvette> i tried prntscrn but doesn't seem to work like in windows
[10:20:49] <hazzy-m> hmm, not that I know of, should be easy to add
[10:20:49] <hazzy-m> sek
[10:28:54] <hazzy-m> Applications Menu > Settings > Keyboard
[10:29:30] <hazzy-m> in the keyboard window select the Application Shortcuts tab
[10:30:00] <Lcvette> k
[10:30:01] <hazzy-m> at the bottom click the Add button with the plus sign
[10:30:26] <hazzy-m> for the command paste in `xfce4-screenshooter -f`
[10:30:38] <hazzy-m> and click Ok
[10:31:26] <hazzy-m> on the command shortcut window press the Print Screen button
[10:31:27] <Lcvette> ok
[10:31:32] <hazzy-m> and that should be it
[10:32:02] <Lcvette> nice3!
[10:46:18] -!- Roguish_ has joined #hazzy
[10:49:56] -!- Roguish has quit [Ping timeout: 268 seconds]
[10:49:57] Roguish_ is now known as Roguish
[10:51:59] * Lcvette uploaded an image: image.png (224KB) < https://matrix.org >
[10:58:33] * Lcvette uploaded an image: image.png (250KB) < https://matrix.org >
[11:02:38] * Lcvette uploaded an image: image.png (386KB) < https://matrix.org >
[11:03:43] * Lcvette uploaded an image: image.png (270KB) < https://matrix.org >
[11:05:39] * Lcvette uploaded an image: image.png (264KB) < https://matrix.org >
[11:07:18] * Lcvette uploaded an image: image.png (428KB) < https://matrix.org >
[11:08:31] * Lcvette uploaded an image: image.png (419KB) < https://matrix.org >
[11:09:11] * Lcvette uploaded an image: image.png (368KB) < https://matrix.org >
[11:10:05] * Lcvette uploaded an image: image.png (367KB) < https://matrix.org >
[11:10:52] * Lcvette uploaded an image: image.png (328KB) < https://matrix.org >
[11:11:40] * Lcvette uploaded an image: image.png (308KB) < https://matrix.org >
[11:12:37] * Lcvette uploaded an image: image.png (361KB) < https://matrix.org >
[11:13:35] * Lcvette uploaded an image: image.png (392KB) < https://matrix.org >
[11:16:18] <hazzy-m> man that looks good fullscreen!
[11:16:55] <Lcvette> yeah it rreally does
[11:17:06] <Lcvette> looks phenominal on my 27" screen
[11:17:07] <Lcvette> lol
[11:17:12] <Lcvette> and my 24"
[11:17:22] <Lcvette> hoping it looks as good on my 22"
[11:17:39] <hazzy-m> haha, hope it fits :D
[11:17:41] <Lcvette> im sure it will, that 22" screen actually has the best picture of all of them
[11:18:00] <Lcvette> it eill, its 1920x1080
[11:27:28] <Lcvette> https://forum.linuxcnc.org
[11:27:31] <Lcvette> updated!
[11:57:27] <Lcvette> hazzy
[11:57:31] <Lcvette> do you know Norbert?
[11:58:27] <Lcvette> he goes by newbynobi on linuxcnc
[11:59:04] <Lcvette> he is interested in helping eith qtvcp
[11:59:21] <Lcvette> but i think that is different than your qtpyvcp?
[12:49:24] <Lcvette> hazzy
[12:49:31] <Lcvette> breaker breaker come in
[12:53:36] <Lcvette> is that G52 something I need to add to the Offsets page Zeroing table before G92?
[12:54:37] * Lcvette uploaded an image: image.png (159KB) < https://matrix.org >
[12:54:40] <Lcvette> here?
[12:55:04] <Lcvette> hazzy
[12:55:10] <Lcvette> beuller
[12:55:16] <Lcvette> beuller
[12:55:20] <Lcvette> beuller
[12:55:24] <Lcvette> beuller
[12:55:26] <Lcvette> hazzy
[12:55:28] <Lcvette> hazzy
[12:55:31] <Lcvette> hazzy
[12:55:33] <Lcvette> lol
[13:09:31] <hazzy-m> Lol, I'm out, back in a bit
[13:20:04] * Lcvette uploaded an image: image.png (270KB) < https://matrix.org >
[14:09:19] * Lcvette uploaded an image: image.png (270KB) < https://matrix.org >
[14:09:46] <Lcvette> final revision for this one!
[14:10:18] * hazzy-m is back
[14:10:36] <Lcvette> everything fits and should have enough room for digits in both inch and metric units up to 1000.000mm and 100.0000"
[14:10:58] <Lcvette> if you are over that may be trouble
[14:11:20] <hazzy-m> that's plenty of digits
[14:11:22] <jesseg> wow faaaaanceeeey
[14:11:33] <Lcvette> of course that means 999.9999"
[14:11:36] <hazzy-m> unless somebody has a huge machine
[14:11:45] <Lcvette> and 9999.999mm
[14:11:47] <hazzy-m> jesseg: Hello!
[14:11:51] <Lcvette> so thats pretty big
[14:11:57] <jesseg> howdy hazzy-m !! How's things going for you?
[14:11:57] <Lcvette> hello jesseg
[14:12:11] <jesseg> hey there Lcvette how're you doing?
[14:12:11] <hazzy-m> very good
[14:12:19] <Lcvette> excited!
[14:12:29] <hazzy-m> got much snow up there yet?
[14:12:45] <jesseg> hazzy-m, none yet, at least not below 3k feet.
[14:13:00] <jesseg> but up around 5k feet the mountain tops are getting dusted white for sure
[14:14:37] <hazzy-m> have you been camping yet in the hammocks you made?
[14:15:10] <jesseg> yeah! but months ago
[14:15:40] <jesseg> I had it a couple times up at my favorite 6k ft mountain lake
[14:16:05] <hazzy-m> great!
[14:16:49] <jesseg> https://www.google.com!4m5!3m4!1s0x548fd317333ad431:0x8fe4d2587aec6b76!8m2!3d47.8409226!4d-123.1894864!5m1!1e4
[14:17:58] <jesseg> and I've found a secondary use for it too. You can put it on like a straight jacket LOL. like for emergencies, you draw the string around your ankles and around your neck or over the top of your head and peak out the whole
[14:18:03] <hazzy-m> is that the same place the old mine is at?
[14:18:04] <jesseg> so you can keep warm standing up
[14:18:13] <jesseg> it's a few mountain ridges over from the old mine
[14:18:29] <hazzy-m> hahaha
[14:18:39] <jesseg> I wish I'd put sleeves on the sleeping bag because it would double as a grand emergency cloak
[14:19:05] <hazzy-m> yeah, actualy that is a great idea
[14:19:31] <hazzy-m> and if your lazy getting up in the morning you can stay in it
[14:19:33] <hazzy-m> lol
[14:19:38] <jesseg> LOL yup
[15:08:17] <Lcvette> pushed the revisions
[17:28:55] -!- pdadroid4[m]1 has joined #hazzy
[17:29:21] -!- grijalvap[m]1 has joined #hazzy
[17:29:29] -!- pdadroid4[m] has quit [Ping timeout: 250 seconds]
[17:29:29] -!- grijalvap[m] has quit [Ping timeout: 250 seconds]
[17:29:29] -!- jschi[m] has quit [Ping timeout: 250 seconds]
[17:29:35] -!- jschi[m]1 has joined #hazzy
[17:56:27] <Not-97e5> [02QtPyVCP] 07Kurt Jacobson pushed 031 commit to 03master [+0/-0/±1] 13https://gitlab.com/Hazzy/qtpyvcp/compare/a1f7c04744cf1963fc94bf6f6ba6454a10cb70a3...175008323231c1e2f0ad5370ac136a98ef37cb1a
[17:56:28] <Not-97e5> [02QtPyVCP] 07Lcvette 031750083 - added G52 to offsets page adjusted page items to accommodate g52 addition in offsets
[17:57:30] <Lcvette> hurray!
[17:57:41] <Lcvette> i have a thingy
[17:57:48] <Lcvette> with my name on it
[17:58:00] <Lcvette> hard core coder!
[17:58:02] <Lcvette> mad fu
[17:58:05] <Lcvette> waaaaa!
[17:58:05] <hazzy-m> hahaha
[17:58:45] <hazzy-m> keep that fu coming!!!
[17:59:16] <hazzy-m> bout to push something I think you're gonna like
[18:43:22] <Lcvette> im on pins and needles, where is it!
[18:43:38] <Lcvette> damn you and your teasing
[18:43:40] <Lcvette> lol
[18:44:00] <hazzy-m> it got delayed a bit
[18:44:01] <hazzy-m> lol
[18:44:04] <Lcvette> ive reloaded kraken like 20 times
[18:44:15] <hazzy-m> bugs ..
[18:44:20] <hazzy-m> LOL
[18:44:27] <Lcvette> damn bugs
[18:44:41] <Lcvette> you know i like things you say im gonna like
[18:45:10] <hazzy-m> just a hint, it is happy
[18:45:26] <Lcvette> you made my happyface launcher finally?
[18:45:33] <Lcvette> shut the front door
[18:45:39] <hazzy-m> yes!
[18:45:43] <Lcvette> hahaha
[18:45:47] <hazzy-m> it's pretty nice
[18:50:53] <Not-97e5> [02QtPyVCP] 07Kurt Jacobson pushed 032 commits to 03master [+2/-1/±4] 13https://gitlab.com/Hazzy/qtpyvcp/compare/175008323231c1e2f0ad5370ac136a98ef37cb1a...2c81060439970440b4e489dbbda5d66152ee9d7f
[18:50:55] <Not-97e5> [02QtPyVCP] 07Kurt Jacobson 03fe3c655 - fix some bugs in logger which prevented setting custom logger names
[18:50:57] <Not-97e5> [02QtPyVCP] 07Kurt Jacobson 032c81060 - add `editvcp`, a tool for selecting VCPs to edit and launching designer
[18:51:28] <Lcvette> you did it?
[18:51:42] <hazzy-m> yes, it should be up
[18:52:50] <hazzy-m> you'll have to reinstal
[18:53:00] <hazzy-m> so once you check it out run
[18:53:10] <Lcvette> checked out
[18:53:14] <hazzy-m> `pip install -e .`
[18:53:44] <hazzy-m> then you should be able to run `editvcp` from any terminal to launch designer
[18:53:54] * Lcvette sent a long message: < https://matrix.org >
[18:54:13] <hazzy-m> you need to be in the qtpyvcp-master dir
[18:55:19] <Lcvette> that worked
[18:55:22] <Lcvette> now
[18:56:18] * Lcvette sent a long message: < https://matrix.org >
[18:56:29] <hazzy-m> shoot
[18:56:48] <hazzy-m> try `sudo pip install -e .`
[18:59:46] * Lcvette uploaded an image: image.png (262KB) < https://matrix.org >
[18:59:51] <Lcvette> now it opens this
[19:00:02] <hazzy-m> perfect
[19:00:26] <hazzy-m> now browse to the probe basic dir and click the yml file
[19:04:07] <hazzy-m> if you run `editvcp -h` it will give you a list of options
[19:05:05] <hazzy-m> if you run `editvcp --yaml-file /path/to/brobebasic.yml` it will launch the designer with the probe basic file open and the qss file applied
[19:06:35] -!- Roguish_desk has joined #hazzy
[19:14:30] <Roguish_desk> hey, sorry for lurking.....
[19:14:47] <Roguish_desk> sudo pip install -e what????
[19:15:34] <Roguish_desk> like that autolauncher too.
[19:16:42] <Roguish_desk> noel@Hecton120:~/hazzy/qtpyvcp$ sudo pip install -e
[19:16:42] <Roguish_desk> Usage:
[19:16:42] <Roguish_desk> pip install [options] <requirement specifier> [package-index-options] ...
[19:16:42] <Roguish_desk> pip install [options] -r <requirements file> [package-index-options] ...
[19:16:42] <Roguish_desk> pip install [options] [-e] <vcs project url> ...
[19:16:44] <Roguish_desk> pip install [options] [-e] <local project path> ...
[19:16:46] <Roguish_desk> pip install [options] <archive url/path> ...
[19:16:48] <Roguish_desk> -e option requires an argument
[19:19:01] <Not-97e5> [02QtPyVCP] 07Kurt Jacobson pushed 031 commit to 03master [+0/-0/±1] 13https://gitlab.com/Hazzy/qtpyvcp/compare/2c81060439970440b4e489dbbda5d66152ee9d7f...cb629e9047dfc1355b32cafa9abf56be90443c5d
[19:19:02] <Not-97e5> [02QtPyVCP] 07Kurt Jacobson 03cb629e9 - enable selecting VCP to edit based on name
[19:19:23] <hazzy-m> Roguish_desk: Hey!
[19:19:53] <hazzy-m> `pip install -e /path/to/qtpyvcp-source`
[19:20:10] <Roguish_desk> just checking in, and see you're making a handy dandy little launcher thing. cooooool.
[19:20:20] <hazzy-m> if the current working dir is the vcp source dir you can just do `.`
[19:20:48] <hazzy-m> Lcvette: Now you can select a VCP to edit just from its name
[19:21:09] <hazzy-m> `editvcp probebasic`
[19:21:18] <hazzy-m> just pushed
[19:23:12] <Roguish_desk> SUCCESSSSSSSS.
[19:23:24] <hazzy-m> hurray!!
[19:35:33] <Roguish_desk> hazzy-m: i'm looking at brender.qss where can I find docs on all the format options? is this ok? http://doc.qt.io
[19:36:26] <hazzy-m> Yes, that is the best documentation, still not great
[19:36:58] <hazzy-m> I usualy find it more helpful to look at other QSS files to see what they did
[19:37:34] <hazzy-m> this is good: https://github.com
[19:38:15] <Roguish_desk> ok. i do the same. had to hack thru a simple macro for solidworks the other day. oh joy. it's vb
[19:38:48] * hazzy-m hates VB
[19:45:46] <Roguish_desk> hazzy-m: how do I get changes I make to show in brender when I run my test system using brender? I recall you mentioned I need a run-in-place install?
[19:48:43] <Lcvette> hazzy, sorry wife came with groceries and a long story about her day\
[19:48:53] <Lcvette> where were we'
[19:51:18] <Lcvette> daMMIT HAZZY ITS NOT WORKING
[19:51:21] <Lcvette> LOL
[19:53:07] * Lcvette sent a long message: < https://matrix.org >
[19:53:15] <Lcvette> had it open with errors
[20:08:16] <Lcvette> hazzy: yo
[20:15:32] <Roguish_desk> hazzy-m: if I delete the brender.pyc the modified 'resources' are sucked in and used.
[20:19:43] <hazzy-m> Roguish_desk: The modifications to the QSS file should be picked up without needing to do anything
[20:20:07] <hazzy-m> if you change the .qrc files you will need to recompile them
[20:20:51] <hazzy-m> you can use `qcompile /path/to/brender-dir` to recompile
[20:21:22] <hazzy-m> Lcvette: You did not set up the linuxcnc environment
[20:21:48] <hazzy-m> the ctrl + r ... command
[20:23:13] <Lcvette> ?
[20:24:10] <hazzy-m> `. /home/chris/dev/linuxcnc-master/scripts/rip-environment`
[20:25:13] <hazzy-m> maybe we should get you set up with a build bot LCNC install so you don't have to worry about that ...
[20:25:59] <Lcvette> ijm mconfused
[20:26:20] <Lcvette> i thought i nwas going to be able to open with the happyface icon?
[20:26:50] <hazzy-m> oh shoot
[20:27:03] <hazzy-m> the linuxcc version is a problem there
[20:27:05] <hazzy-m> hmmm
[20:27:18] <Lcvette> it opens now
[20:27:32] <Lcvette> but instead of the .sh its just a different command in temrinal
[20:27:36] <Lcvette> thats not hapopy face
[20:27:43] <Lcvette> that just different sadface
[20:27:45] <Lcvette> lol
[20:27:54] <Lcvette> deceiver!
[20:28:02] <Lcvette> haha
[20:28:03] <hazzy-m> did you try `qtpyvcp probebasic`?
[20:28:20] <Lcvette> ?
[20:28:25] <Lcvette> i got it working
[20:28:33] <hazzy-m> ok
[20:28:44] <Lcvette> editvcp probebasic
[20:29:06] <hazzy-m> if you install linuxcnc system wide it will work from the happy face launcher, I forgot that you are running a RIP
[20:29:27] <hazzy-m> sorry, that is what I meant
[20:29:39] * hazzy-m is a bit detracted
[20:29:45] <hazzy-m> destracted
[20:29:46] <hazzy-m> LOL
[20:30:07] <hazzy-m> distracted*
[20:30:12] <hazzy-m> xD
[20:30:39] * Lcvette sent a long message: < https://matrix.org >
[20:31:01] <hazzy-m> great!
[20:33:24] <Roguish_desk> I see if i do not delete the .pyc file, the changes are not picked up. if I do delete the .pyc they are.
[20:33:54] <hazzy-m> interesting
[20:34:10] <hazzy-m> it this in designer, or running it normaly?
[20:34:42] <Roguish_desk> running normally
[20:35:00] <hazzy-m> that is very strange
[20:35:07] <hazzy-m> what files are you editing?
[20:35:34] <Roguish_desk> brender.qss
[20:36:28] <Lcvette> what are you working on rougish?
[20:36:34] <hazzy-m> the qss files are not compiled, so I don't understand why that is happening
[20:36:48] <Roguish_desk> playing, experimenting... fing around
[20:36:54] <Lcvette> share!
[20:36:55] <hazzy-m> can you try `export PYTHONDONTWRITEBYTECODE=1` and see if that helps?
[20:36:57] <Roguish_desk> f'ing
[20:37:15] <hazzy-m> that will keep python from generating the .pyc files
[20:37:17] <Lcvette> -get install vokoscreen
[20:37:58] * Lcvette sent a long message: < https://matrix.org >
[20:38:38] <hazzy-m> what are you doing? LOL
[20:38:40] <hazzy-m> try
[20:38:54] <hazzy-m> sudo apt update && apt upgrade
[20:38:56] <Lcvette> trying to install a screen capture software so i can do a video demo of the ui so far for peeps
[20:39:24] <Lcvette> anything after that?
[20:39:44] <hazzy-m> then try reinstalling the vovothing
[20:39:56] <hazzy-m> I really simple screen recorder ...
[20:40:21] * Lcvette sent a long message: < https://matrix.org >
[20:40:42] <Lcvette> I am Groot
[20:40:44] <Lcvette> lol
[20:40:46] <Lcvette> ?
[20:40:50] <hazzy-m> sudo apt upgrade
[20:42:14] <Lcvette> wow thats alot of upgrading
[20:43:04] <hazzy-m> you should run `sudo apt update && sudo apt upgrade` on a regular basis
[20:43:43] <Lcvette> how am i supposed to know that?
[20:44:06] <hazzy-m> your not, but now you do :D
[20:45:21] <Lcvette> 50%
[20:45:46] <hazzy-m> 71% here, I decided to do it too
[20:45:57] <Lcvette> i'll have to find the windows update settings
[20:46:20] <Lcvette> automatic updates
[20:59:17] <Lcvette> ok updates
[20:59:20] <Lcvette> s
[20:59:22] <Lcvette> d
[21:00:29] * Lcvette sent a long message: < https://matrix.org >
[21:01:18] <hazzy-m> lol
[21:01:31] <hazzy-m> sudo apt install vokoscreen
[21:01:37] <Lcvette> the other one installed
[21:01:48] <hazzy-m> excellent
[21:38:22] <Lcvette> https://youtu.be
[21:38:28] <Lcvette> test video
[21:38:39] <Lcvette> just an unscripted test
[21:38:58] <Lcvette> unlisted
[21:39:01] <Lcvette> i have a cold so forgive my voice its pretty hoarse and weak
[21:39:09] <Lcvette> found some bugs maybe
[21:42:28] <Lcvette> hazzy, for the tool length dro, would that not be the same code as the diameter dro just pulling from a different location for the length offset?
[21:44:57] <Lcvette> and of coursein the public version i will credit you fine gents on all your hard work!
[21:45:18] <Lcvette> and it will be much better presented not so random..lol
[21:45:27] <Lcvette> will waiut for my voice to return
[21:45:39] <Lcvette> so i can talk about it with some higher passion!
[21:46:25] <hazzy-m> yes, should be the same code, but x_offset instead of diameter
[21:46:34] * hazzy-m watches
[21:53:15] <hazzy-m> that's good!
[21:53:29] <hazzy-m> wonder why goto zero is broke
[21:53:30] <hazzy-m> hmm
[21:53:32] <Lcvette> that screen recorder software is awesome
[21:53:38] <Lcvette> not sure
[21:53:43] <Lcvette> it works without a tool loaded
[21:53:48] <Lcvette> im playing with it now
[21:54:00] <hazzy-m> I'll hve to try to, audio was good
[21:55:23] <Lcvette> i have a decent microphone i bought for it
[21:55:24] <Lcvette> :D
[21:57:48] <Lcvette> g49
[21:57:57] <Lcvette> works if you undo the tool offset
[21:58:04] <Lcvette> may be a safety in linuxcnc?
[21:58:11] <hazzy-m> strange
[21:58:16] <hazzy-m> that does not seem right
[21:58:47] <hazzy-m> oh, maybe the tool is already at zero?
[21:59:01] <hazzy-m> what is Go To Zero supposed to do?
[21:59:03] <Lcvette> no
[21:59:07] <hazzy-m> I mean what zero
[21:59:16] <Lcvette> zero of the curtrent wcs
[21:59:23] <Lcvette> i think there is an issue maybe
[21:59:47] <Lcvette> trying to think it through in my head
[21:59:51] <Lcvette> with the tool length offset
[22:01:29] <Lcvette> i think maybe that is correct not being able to go to 0 with a tool offset in play
[22:02:04] <Lcvette> because if you were at machine 0 in z and added a tool which drops the z down and tried to go to zero it would go past max travel
[22:02:21] <Lcvette> so one of two things should happen
[22:02:31] <Lcvette> zero should be set with the tool in place
[22:02:49] <Lcvette> automatically and the offset adjusted
[22:03:32] <Lcvette> so that when the machine went to zero with a tool loaded, the tool would go to its zero position and the spindle would be at its zero position
[22:03:36] <Lcvette> make sense?
[22:03:53] <hazzy-m> yes, I guess that does
[22:04:03] <hazzy-m> but I had never noticed that behavior in the past
[22:04:08] <Lcvette> ie when i load a tool with a G43 offset i don't think the wc position should change, but rather the offet
[22:05:01] <Lcvette> so wc current position should reman 0.000 but the wc offset should have the G43 offset value added to it
[22:05:16] <Lcvette> so its relation to machine coordinates is adjusted for
[22:05:26] <Lcvette> think that is the correct method of handling the tool offsets
[22:06:36] <Lcvette> im pretty sure actually
[22:06:40] <Lcvette> that way gcode works for it
[22:06:58] <Lcvette> since tool offsets are always handled in the control system and not cam
[22:07:56] <Lcvette> does that track with you?
[22:08:39] <Lcvette> heading out to verify in mas
[22:08:45] <Lcvette> msm
[22:15:11] <Lcvette> Nope
[22:15:13] <Lcvette> I'm wrong
[22:18:51] <Lcvette> So
[22:19:02] <Lcvette> Not sure why it's not working
[22:19:39] <Lcvette> If I hit go to zero on msm it will goto zero with the tlo in the wc current position
[22:20:27] <Lcvette> Not a big deal usually because I use my probe and that just brings the tool to the same height as the probe tip which makes life easy on operations
[22:20:39] <Lcvette> Can't believe I forgot since I use that function often
[22:22:58] <Lcvette> Hazzy Amy other questions while I'm here with msm booted up?
[22:24:33] <Lcvette> OK heading in then It's cold... Lol
[22:55:40] <Lcvette> hhahaha.. have some pathpilot users talkin about jumping ship once the Probe Basic is released! thats how we know we made it big time
[22:55:43] <Lcvette> lol
[22:59:25] <hazzy-m> sorry, was out with the family
[22:59:35] <hazzy-m> LOL, that is great!
[23:13:17] <Roguish_desk> hazzy-m: hey, what is the LED button supposed to do? if I try to add a 'widget rule' the whole designer crashes out....
[23:13:40] <hazzy-m> That is a BUG!
[23:13:48] <hazzy-m> thanks for reporting
[23:15:21] <hazzy-m> the LED can be used to show various states, which are not necessarily dependant on the button state
[23:16:42] <hazzy-m> Have you been able to figure out the rules editor? I hear it is confusing ...
[23:16:56] <hazzy-m> Need to work on some socumentation for it
[23:17:08] <hazzy-m> documentation*
[23:18:05] <Roguish_desk> that's kinda what I'm doing. mostly trial and error, lots of errors.
[23:18:29] <Roguish_desk> what's the difference between an LED_button and an LED_widget ?
[23:19:04] <hazzy-m> The LED widget is just the LED, without the button
[23:19:49] <Roguish_desk> and what is the halLEDwidget
[23:19:51] <hazzy-m> the LED button is an actionbutton with the LED stuck in the corner, other then that they behave as seperate widgets
[23:20:34] <Roguish_desk> i like LED's to show statuses of things, like limit switches
[23:20:49] <hazzy-m> The HAL LED was intended to show BIT type hall pin states, but has been superseded by the more generic LED widget and rules editor
[23:21:21] <hazzy-m> Yes, that is exactly the type of thing i intended them for!
[23:22:16] <Roguish_desk> and in the 'widget box' of the designer, the LEDbutton and halLEDwidget show, but not the plain LED.
[23:22:43] <hazzy-m> hmm
[23:24:07] <hazzy-m> your right, I guess I never updated the plain LED
[23:24:11] <hazzy-m> thanks!
[23:24:37] <hazzy-m> keep them coming!
[23:26:02] <hazzy-m> I can reproduce the designer crash with the LEDButton
[23:26:07] <hazzy-m> fix coming up
[23:26:53] <Roguish_desk> check it out. power of copy and paste. https://imgur.com
[23:27:17] <Roguish_desk> and I modified the rules too, so they work
[23:27:35] <Roguish_desk> oh, the joint statuses
[23:27:43] <hazzy-m> Nice!!
[23:28:30] <Roguish_desk> the motors on my mill are woefully undersized, so I constantly monitor the ferror.
[23:34:24] <Roguish_desk> i just don't see how it's all tied together.
[23:35:14] <Roguish_desk> ex: for the ferror, the thing is a StatusLabel, with the RulesEditor of 'status:joint[1].ferror_current'
[23:35:56] <Roguish_desk> how and/or what ties the linuxcnc status info to the GUI?
[23:37:03] <hazzy-m> good question, I'll try to explain how it works
[23:38:05] <hazzy-m> the `status:` part of the channel entry in the rules editor specifies soemthing that I call a DataChannel
[23:39:01] <hazzy-m> you can alomost think of the channels being URLs specifying the DataChannel to get the data from
[23:40:04] <hazzy-m> the DataChannels themselves are defined by the files in the plugins directory
[23:40:40] <hazzy-m> one file for each DataSource and a DataSource probvides multiple DataCahnnels
[23:41:34] <hazzy-m> those do the actualy polling of the linuxcnc.status channel and provide the data to the channels
[23:41:35] <Roguish_desk> like status.py
[23:41:49] <hazzy-m> exactly
[23:42:44] <hazzy-m> so `status;` in the data channle URL is refering to data provided by the status.py pluggin
[23:46:01] <Roguish_desk> it looks like you have about 1/2 the data for each joint in the status.py joint status class
[23:47:06] <hazzy-m> it should have all the values that change, some of the configuration values I did not add
[23:47:45] <hazzy-m> if I missed something let me know and I'll add it
[23:48:18] <Roguish_desk> and I don't see an Axis Status Class. are you assuming joint=axis ?
[23:48:30] <Roguish_desk> and axis=joint
[23:49:11] <hazzy-m> yes, in 2.8 there are only a few axis status items, and they are not particualrly usefull
[23:49:30] <hazzy-m> I'd be glad to add them if you think they are of value
[23:49:31] <Roguish_desk> yeah, for a simple cartesian machine it's ok.
[23:49:55] <hazzy-m> http://linuxcnc.org
[23:50:40] <hazzy-m> that is all there is, and those are configuration values except from velocity, I should definatly add velocity
[23:50:45] <Roguish_desk> I get the '40' above by looking at joint.n in 'HAL Configuration' command.
[23:52:13] <hazzy-m> what 40? I think I might not be getting all your messages
[23:52:21] <Roguish_desk> OH, the selection is already selected.....
[23:54:27] <Roguish_desk> here: https://imgur.com
[23:54:58] <hazzy-m> ah, yes
[23:55:15] <hazzy-m> the only values provided by status.py are those provided by the linuxcnc.status channel, which does not have all of the HAL values
[23:55:42] <Roguish_desk> yeah, i see that now.
[23:55:57] <hazzy-m> I am woking on a hal_status.py plugin so you have accsess to all the HAL values as well as the status values
[23:56:17] <hazzy-m> it is almost done but have a few things to work out
[23:57:16] <hazzy-m> the syntax for the rules editor will be something like `hal:joint.0.home-state`
[23:57:30] <Roguish_desk> that looks ok.
[23:59:00] <Roguish_desk> hey, it's late for me here. long day in front of a Haas. tomorrow in front of Solidworks..... even later for you on the right coast.
[23:59:48] <Roguish_desk> thank you for the help. i'll see if i can do anything useful with it all. ttfn