#hazzy | Logs for 2019-04-25

Back
[00:16:13] -!- jthornton has quit [Read error: Connection reset by peer]
[00:16:33] -!- JT-Shop2 has quit [Read error: Connection reset by peer]
[00:16:38] -!- JT-Shop has quit [Read error: Connection reset by peer]
[00:16:55] -!- jthornton has joined #hazzy
[00:17:00] -!- JT-Shop2 has joined #hazzy
[00:18:50] -!- JT-Shop has joined #hazzy
[01:16:12] <Lcvette> \o/
[01:16:26] <Lcvette> lcvette figured out how to make the probed position buttons!
[01:17:10] <Lcvette> but im not sure how to make the probed width and probed diameter labels work
[01:17:17] <Lcvette> i meant the probed position labels
[01:17:19] <Lcvette> lol
[01:18:29] <Lcvette> but should the probed position reflect the actual machine position when the probe tripped or should there be an expression added to account for the probe tip and trigger distance
[04:11:18] <Lcvette> https://youtu.be
[04:18:21] <Lcvette> 22 out of 26 probing routines written! whoo hoo! 4 left to do tomorrow and friday! and probing is ~done?
[04:18:22] <Lcvette> :D
[04:18:23] <Lcvette> \o/
[04:18:40] <Lcvette> night!
[04:18:47] <Lcvette> morning to you early risers
[04:18:51] <Lcvette> :D
[05:47:54] <JT[m]1> morning
[06:02:48] <hazzy-m> morning
[06:37:55] <jthornton> niebubf
[06:37:59] <jthornton> morning
[06:46:41] <hazzy-m> TurBoss I like the utility widgets!
[06:48:20] * hazzy-m desktop riot is broken, won't refresh
[06:51:05] * JT[m]1 sent a long message: < https://matrix.org >
[06:51:20] <JT[m]1> hmm I get this now when trying to run editvcp
[06:56:43] * JT[m]1 sent a long message: < https://matrix.org >
[07:03:13] -!- pcw_home has quit [Remote host closed the connection]
[07:12:50] -!- JT-Shop2 has quit [Read error: Connection reset by peer]
[07:12:50] -!- JT-Shop has quit [Read error: Connection reset by peer]
[07:12:50] -!- jthornton has quit [Read error: Connection reset by peer]
[07:21:36] -!- JT-Shop2 has joined #hazzy
[07:23:01] -!- JT-Shop has joined #hazzy
[07:25:05] -!- jthornton has joined #hazzy
[07:40:31] -!- jthornton has quit [Read error: Connection reset by peer]
[07:40:37] -!- JT-Shop has quit [Read error: Connection reset by peer]
[07:40:37] -!- JT-Shop2 has quit [Read error: Connection reset by peer]
[07:58:08] -!- JT-Shop has joined #hazzy
[07:58:11] -!- JT-Shop2 has joined #hazzy
[07:58:11] -!- jthornton has joined #hazzy
[09:03:35] * JT[m]1 sent a long message: < https://matrix.org >
[09:10:01] -!- Roguish has joined #hazzy
[09:54:46] * JT[m]1 uploaded a video: RTV6-1.mp4 (542KB) < https://matrix.org >
[09:55:39] <JT[m]1> drilling then rigid tapping
[10:33:40] <roguish[m]> JT: what's CHNC ?
[10:34:04] <JT-Shop2> Hardinge chucker lathe
[10:37:29] <roguish[m]> ah, ok.
[10:43:34] <Not-e6c6> [02qtpyvcp] 07marfis89 commented on issue 03#10: vcpchooser fails to load if no vcp is specified in command line arguments - 13https://git.io/fjs0J
[11:39:43] <JT[m]1> roguish: I've not seen a board of directors in a long long time
[11:53:37] <Lcvette> morning
[12:15:19] <JT-Shop2> morning
[12:47:14] <Lcvette> JT do you have any secrets to probe routines?
[12:47:33] <Lcvette> JT-Shop2: someof these are getting a bit long
[12:47:46] <Lcvette> not sure if that is the norm
[12:47:53] * JT[m]1 uploaded an image: VectorImage_2019-04-25_114744.jpg (39KB) < https://matrix.org >
[12:47:58] <Lcvette> they are a bit more involved with some extra things
[12:48:05] <Lcvette> awwwwwwww
[12:48:13] <Lcvette> kittay!!
[12:48:34] <Lcvette> with a rain shelter
[12:50:12] <Lcvette> https://paste.ubuntu.com
[12:53:03] <JT[m]1> there are only 5 probe routines that are needed X+ X- Y+ Y- and Z-
[12:53:25] <JT[m]1> so if you call them as a sub to your more complicated probe routine you never have to write it twice
[12:54:21] <Lcvette> as in a remap?
[12:54:21] <Lcvette> like in a remap
[12:54:22] <Lcvette> oh
[12:54:47] <JT[m]1> like a subroutine
[12:55:20] <JT[m]1> you to the prep move then call the subroutine to do the actual probe move
[12:55:39] <Lcvette> ah
[12:55:48] <Lcvette> with o<word>
[12:56:07] <Lcvette> ?
[12:56:54] <JT[m]1> aye
[12:58:29] <Lcvette> lcvette feels as though he has learned something the hard way
[13:00:24] -!- jthornton has quit [Read error: Connection reset by peer]
[13:00:25] -!- JT-Shop2 has quit [Read error: Connection reset by peer]
[13:00:25] -!- JT-Shop has quit [Read error: Connection reset by peer]
[13:00:51] -!- jthornton has joined #hazzy
[13:01:04] -!- JT-Shop2 has joined #hazzy
[13:01:31] -!- JT-Shop has joined #hazzy
[13:13:50] * JT[m]1 uploaded an image: VectorImage_2019-04-25_121325.jpg (138KB) < https://matrix.org >
[13:16:34] <Lcvette> looking good!
[16:21:53] -!- JT-Shop has quit [Read error: Connection reset by peer]
[16:21:53] -!- JT-Shop2 has quit [Read error: Connection reset by peer]
[16:24:46] -!- jthornton has quit [Ping timeout: 276 seconds]
[16:37:18] -!- JT-Shop has joined #hazzy
[16:37:39] -!- JT-Shop2 has joined #hazzy
[16:37:46] -!- jthornton has joined #hazzy
[16:54:01] <Lcvette> JT: im struggling with the new method of using the o word call, not sure if im doing it right or not, the docs show the same as what i am doing but im not getting the result of the sub
[16:54:26] <Lcvette> I am putting:
[16:54:52] <Lcvette> o<probe_z_minus> call
[16:55:16] <Lcvette> where the z minus sub should occur but it just skips it
[16:55:21] <Lcvette> the formatting appears the same as the docs
[16:56:41] <Lcvette> o<myfile> call
[16:57:03] <Lcvette> pulling my hair out on this now
[16:58:34] <Lcvette> i went through and made the x, y, z-, x-, y- subs to work with this as it seems much better but im losing now..lol
[16:58:43] <Lcvette> any help is appreciated!
[17:01:16] <Lcvette> https://paste.ubuntu.com
[17:01:39] <Lcvette> that is the o<probe_z_minus> sub
[17:01:43] <JT[m]1> what is the name of that file?
[17:02:00] <Lcvette> probe_z_minus.ngc
[17:02:15] <JT[m]1> and it's executable?
[17:02:24] <Lcvette> yeah
[17:02:42] <Lcvette> it works perfect on its own in probe basic
[17:02:42] <JT[m]1> and you restarted linuxcnc after creating it?
[17:03:05] <Lcvette> yes
[17:07:07] <JT[m]1> I get cannot probe with zero feed rate error
[17:08:18] <JT[m]1> wrap the call with msg comments then run
[17:08:57] <Lcvette> you ar eprobably getting error on that ebcaus eyou don't have the linked boxes with the feed inputs
[17:08:59] <Lcvette> for slow/fast
[17:09:13] <Lcvette> those are in probe basic
[17:09:18] <JT[m]1> right
[17:09:37] <Lcvette> ok I will wrap
[17:09:38] <Lcvette> try see what it says
[17:10:41] <JT[m]1> when setting up something complex like your probing routines sometimes it's best to just have a stub of a subroutine with a msg and a short pause then after all that works you add the content
[17:13:50] <Lcvette> its the probe tool error
[17:14:05] <Lcvette> thats a wierd one
[17:14:21] <Lcvette> it is passing in the main sub but fsiling in the inner sub?
[17:14:26] <Lcvette> failing
[17:24:16] <Lcvette> ok i see the problem
[17:24:37] <Lcvette> the sub inside the sub is not being passed the data from the boxes in probe basic
[17:24:39] <Lcvette> thats a problem
[17:24:41] <Lcvette> im not sure how to resolve
[17:29:34] <JT[m]1> can you make a simple example for me of what is failing?
[17:50:30] <Lcvette> JT: in probe basic there are entry boxes for probing parameters such as fast feed rate, slow feedrate, probe tool, step off width, etc... thos all are passed to the subroutine when it is called and those parameters are then used in the subroutine for various functions and calculations
[17:51:29] <Lcvette> they work great except apparantly they do not get passed to a subroutine called within a subroutine
[17:52:36] <Lcvette> so the main subroutine is called and all is good but then when the o<sub> is called it is not receiving those parameters and is aborting because of that
[17:52:53] <Lcvette> so i need to find a way to overcome that issue
[17:53:47] <JT[m]1> how are the parameters passed to the subroutine?
[17:54:14] <Lcvette> with some hazzy magic
[17:54:57] <JT[m]1> I'm from Missouri show me
[17:55:52] <Lcvette> im looking to see if there is something now that i can show you
[17:56:29] <Lcvette> im not sure where its hidden
[17:56:45] <Lcvette> i just know that the box must be named the same thing as what is in the subrtoutine
[17:59:43] <Lcvette> there is nothing special about the QlineEdit
[18:00:00] <Lcvette> they don't appear to be part of a widget
[18:00:10] <Lcvette> so im stumped
[18:00:42] <Lcvette> he added a note that says uses NCGUI style arg spec
[18:04:20] <JT[m]1> #number is the parameter passed to the subroutine, which one is failing?
[18:05:08] <Lcvette> all in the o<> called sub
[18:05:17] <Lcvette> i can remove them one at a time and the next in line is the objector
[18:05:38] <Lcvette> the main sub is getting them fine
[18:05:52] <Lcvette> it attempts to roll on without the sub-sub
[18:08:14] <JT[m]1> o<110> if [#5400 NE #<probe_tool_number>]
[18:08:15] <JT[m]1> this one fails?
[18:08:53] <Lcvette> yes unless i remove it
[18:08:53] <JT[m]1> you have a main probe file that's calling the subroutine but your not passing the values?
[18:09:09] <Lcvette> then the next item containing a probe basic passed parameter fails
[18:09:51] <Lcvette> the inner subroutine is not getting the values correct
[18:09:58] <Lcvette> the main subroutine is
[18:10:55] <Lcvette> ie "probe_front_left_top_corner,ngc" starts, it receives all the parameters from probe basic fine
[18:11:03] <Lcvette> inside that sub is the first base sub
[18:11:04] <Lcvette> o<probe_z_minus> call
[18:11:31] <Lcvette> ithat sube also requires some of the probe basic parameters to function correctly
[18:11:49] <Lcvette> but it receives none of them
[18:14:50] <JT[m]1> ah so your using a sub call button that passes parameters but when you call a sub from the original one you must pass the parameters to it
[18:15:08] <Lcvette> correct
[18:15:45] <Lcvette> sorry i didn't do a great job explaining that
[18:16:45] * JT[m]1 sent a long message: < https://matrix.org >
[18:18:01] * JT[m]1 sent a long message: < https://matrix.org >
[18:18:46] <Lcvette> yup i saw the second one and it is in the same file as the path specifies
[18:19:32] <Lcvette> the top section, hazzy defines the PB parameters starting with #1 thru #14
[18:19:50] <Lcvette> i didn't understand that portion when i was reading it
[18:20:04] <Lcvette> still don't
[18:20:39] <JT[m]1> ok, you are dealing with two different things, a sub call button and an o call
[18:20:40] <Lcvette> but I am guessing it means it can't use them?
[18:21:43] <JT[m]1> I don't think the sub call button passes things to subroutines that are part of the main subroutine if that makes sense
[18:21:59] <Lcvette> yes it does
[18:22:13] <Lcvette> make sense
[18:22:14] <Lcvette> i mean
[18:22:31] <JT[m]1> so to call p-zminus you need to also pass those parameters that it needs
[18:23:50] <Lcvette> right
[18:23:50] <JT[m]1> so it's o<something> call [1] [2] [3] etc and in the subroutine the #1 #2 #3 are the passed values
[18:24:13] <Lcvette> ahhhhhhh
[18:25:21] * Lcvette sent a long message: < https://matrix.org >
[18:25:27] <Lcvette> so this is an example of the main sub
[18:25:33] <JT[m]1> so in a subroutine don't use ngcgui type of variables just use #1 etc. you can name them by doing #<myname> = #1
[18:26:35] <Lcvette> the interior sub would be o<probe_z_minus> call [#1] [#2] [#5][#7] etc
[18:28:06] <JT[m]1> yea that would work as the sub call button is just passing the args by reading the file and making a list
[18:28:12] <Lcvette> that creates abnother dilema
[18:28:17] <JT[m]1> so you have all the info
[18:28:44] <Lcvette> that means the base subs are no longer useable by sub call buttons
[18:28:58] <Lcvette> ?
[18:29:05] <JT[m]1> why is that?
[18:29:23] <Lcvette> oh nevermind i understyand
[18:29:36] <Lcvette> change the words to numbers in the sub body
[18:30:02] <JT[m]1> just use the numbers that are assoiated with the name
[18:30:33] <Lcvette> yup
[18:30:33] <JT[m]1> ah yea or just change them back like the main one does
[18:30:36] <Lcvette> ok
[18:30:40] <Lcvette> think i have it now
[18:31:29] <Lcvette> wait
[18:31:29] <JT[m]1> just remember if you pass #2 #3 #1 they arrive as #1 #2 #3
[18:31:37] <Lcvette> no its backwards then still
[18:31:39] <Lcvette> lol
[18:31:53] <JT[m]1> what's it?
[18:32:11] <Lcvette> well does it matter?
[18:32:24] <Lcvette> sek for an example
[18:32:25] <JT[m]1> what is it?
[18:32:39] <Lcvette> #<max_z_distance> = #2
[18:32:54] <Lcvette> G38.2 Z-[#<max_z_distance>]
[18:32:55] <JT[m]1> they both contain the same value
[18:33:22] <Lcvette> G38.2 Z-[#<#2>]
[18:33:46] <JT[m]1> no, G38.2 Z-[#2]
[18:34:01] <JT[m]1> <> are for named variables
[18:34:12] <Lcvette> ah
[18:34:15] <Lcvette> k
[18:34:28] <Lcvette> that number 2
[18:34:31] <Lcvette> will be receiving the value from the main sub
[18:34:50] <Lcvette> i don't have to redefine it again in the minor sub do i?
[18:35:17] <JT[m]1> no, you just have to send it in order
[18:36:38] <Lcvette> no gaps?
[18:36:45] <Lcvette> 1 2 5
[18:36:47] <Lcvette> ?
[18:36:51] <Lcvette> or gaps ok?
[18:37:01] <JT[m]1> gaps?
[18:37:32] <Lcvette> you say send them in order
[18:37:48] <JT[m]1> in the called file the sent values arrive in order starting with 1
[18:38:51] <JT[m]1> so if you do o<mysub> call [#3] [#5] [#2]
[18:38:51] <JT[m]1> mysub will have #1 #2 and #3 as left to right in the call
[18:39:29] <Lcvette> oh
[18:39:43] <Lcvette> it will renumber the parameters?
[18:40:02] <Lcvette> ok
[18:40:08] <JT[m]1> your not sending the parameter, your sending the value of that parameter
[18:40:13] <Lcvette> so i need to send all of them in order
[18:41:00] <JT[m]1> it would help if all the probe subroutines had the same order of passed values
[18:41:26] <Lcvette> right, so pass them all regardless of whats needed or not
[18:41:39] <Lcvette> 1-14
[18:42:01] * Lcvette sent a long message: < https://matrix.org >
[18:42:35] * Lcvette sent a long message: < https://matrix.org >
[18:42:52] <Lcvette> thats the list of all parameters
[18:43:12] * JT[m]1 sent a long message: < https://matrix.org >
[18:43:21] <Lcvette> so if i pass them all 1 2 3 4 5 6 7 8 9 10 11 12 13 14
[18:44:26] <JT[m]1> you can pass them all and use the named parameters but delete the (=xxx)
[18:45:22] <Lcvette> im unclear what im going to receive in the sub sub
[18:45:23] <Lcvette> you say values
[18:45:34] <Lcvette> as in the actual value?
[18:45:48] <Lcvette> so if #1 is 99, ithe sub sub will receive 99
[18:46:00] <JT[m]1> yes
[18:46:03] <Lcvette> ok
[18:46:06] <Lcvette> no im with you
[18:47:06] <Lcvette> so i do have to redefine it in the o<sub>
[18:48:12] <JT[m]1> what is an it?
[18:48:28] <Lcvette> the value
[18:48:43] <Lcvette> it will be used in multiple places
[18:49:03] <Lcvette> so receivign #1 as 99 i need to define it
[18:49:29] <Lcvette> at the top of the existing sub will be that list
[18:49:41] <Lcvette> because it is an existing used sub already
[18:49:42] <JT[m]1> not making any sense
[18:50:00] <Lcvette> probe_z_minus is its own sub also
[18:50:09] <Lcvette> with its own subcallbutton
[18:50:59] <Lcvette> im trying to figuire how not to destroy its functionality while incorporating it being used as a sub-sub
[18:51:57] <Lcvette> or i guess maybe i need to just make different subs
[18:52:13] <JT[m]1> you would need to say make a pzminus that is the sub sub and make a probe z minus as the sub call button subroutine
[18:52:29] <Lcvette> yup think you are right
[18:52:38] <JT[m]1> so any time you need to probe z you call pzminus
[18:52:49] <JT[m]1> and pass all 14 parameter values to it
[18:56:02] * JT[m]1 sent a long message: < https://matrix.org >
[18:56:15] <Lcvette> how do the parameters come through on the sub side?
[18:56:50] <Lcvette> you may have just answerd me above sek while i examine
[18:59:08] * JT[m]1 sent a long message: < https://matrix.org >
[18:59:24] <JT[m]1> should have pastebin that lol
[18:59:43] <Lcvette> its ok
[19:01:42] <Lcvette> from the main sub, value from PB is 2.000: #<x_hint> = #11
[19:02:10] <Lcvette> passed to sub-sub as: #<x_hint> = #11
[19:02:12] <Lcvette> ?
[19:02:30] <Lcvette> or #<x_hint> = 2.000
[19:03:29] <Lcvette> the actual characters
[19:04:10] <JT[m]1> #<x_hint> = #11 means #<x_hint> is assigned the value of the eleventh passed value
[19:04:25] <Lcvette> ok
[19:04:38] <JT[m]1> so both #<x_hint> and #11 have the value of 2.000000
[19:04:40] <Lcvette> so tghat where i was confused
[19:04:51] <Lcvette> correct
[19:05:02] <Lcvette> i follow that from the regular sub writing
[19:05:04] <JT[m]1> understandable it can be cornfusing
[19:05:35] <Lcvette> i was interpereting you literally when you were saying it passed the value
[19:05:54] <Lcvette> was trying to determine how to prepare to receive the value
[19:06:00] <Lcvette> lol
[19:06:04] <Lcvette> couldn't solve it mentaly
[19:06:17] <JT[m]1> it does only pass the value not the number or anything else
[19:06:19] <Lcvette> empty + sign...
[19:06:20] <Lcvette> lol
[19:06:29] <JT[m]1> look at my second example
[19:06:55] <Lcvette> but the value is represented by #1
[19:07:08] <roguish[m]> JT: how's _v6 coming along?
[19:08:11] <JT[m]1> very well, I'm using it all the time, need to get some single point thread mills and some machinable butter to test that out lol
[19:08:48] <JT[m]1> in the sub sub #1 receives the first value passed and is that value
[19:09:21] <roguish[m]> well, i don't need any thread milling at the present. but something that just is easy to do setups with and run.
[19:09:56] <roguish[m]> the basics....
[19:10:01] <JT[m]1> yea, I hear that I'm in the same canoe I just want it to work easy and fast
[19:10:34] <JT[m]1> that's why I have a G0X0Y0 button next to home all
[19:10:45] <JT[m]1> and tool setting is working very nice now
[19:11:08] <JT[m]1> actually everything is working for me now
[19:22:59] <JT[m]1> roguish: did you see my answer about the emc board of directors?
[19:23:18] <JT[m]1> Subroutines can change the value of parameters above #30 and those changes will be visible to the calling code. Subroutines
[19:23:19] <JT[m]1> may also change the value of global named parameters.
[19:23:32] <JT[m]1> the above is also good to know about subroutines
[19:25:11] <Lcvette> cool!
[19:25:17] <Lcvette> im trying to get this one working
[19:25:25] <Lcvette> but dinner bell just rang
[19:25:30] <Lcvette> maybe some food will help
[19:25:30] <JT[m]1> you will
[19:25:31] <Lcvette> lol
[19:25:59] <JT[m]1> make the framework work then add the content
[19:28:18] <roguish[m]> hadn't seen your answer. just looked.
[19:28:54] <roguish[m]> JT: ok, so to install _v6, do a git clone, and then a pip install?
[19:29:18] <roguish[m]> then git pull, and pip install again to update?
[19:30:12] <JT[m]1> if you do git clone then pip install -e . to update you just need to to a git pull
[19:30:41] <roguish[m]> ok, will try that.
[19:30:55] <JT[m]1> git clone https://github.com
[19:31:17] <JT[m]1> then cd to mill touch v6 and do the pip install -e .
[19:31:23] <roguish[m]> i'm having a horrible problem. lcnc just stops, sort of randomly. like the 'power on' button gets pushed.
[19:31:49] <JT[m]1> that is odd
[19:32:07] <roguish[m]> absolutely no idea why. if I run from a cmd line, it doesn't even show an error.
[19:33:08] <roguish[m]> way odd. stumped.
[19:34:12] <JT[m]1> so it's not an error condition possibly a hardware issue or loose wire
[19:35:10] <roguish[m]> I've changed out cables and boards. gone through all the physical wiring
[19:35:47] <roguish[m]> no base_thread. only a servo_thread.
[19:36:25] <roguish[m]> seems like it could be a realtime error, but no error message.....
[19:38:13] <roguish[m]> it's really inconvenient when milling..... just stops in the middle of an operation.
[19:38:20] <JT[m]1> https://github.com
[19:38:40] <JT[m]1> I can imagine that is frustrating
[19:38:41] <roguish[m]> ah, thantk.
[19:39:02] <JT[m]1> is the power button off when it stops?
[19:39:43] <roguish[m]> yeah. the axis icon changes. to off.
[19:39:58] <roguish[m]> guess I should watch a few more signals and pins.
[19:40:23] <JT[m]1> do you have an external power button
[19:41:32] <roguish[m]> yes. it's linked to the axis screen with an 'and' but I have totally rewired it. i'll look at it again......
[19:41:58] <roguish[m]> better, easier, just comment out the hal commands.
[19:44:59] <JT[m]1> I updated the readme with terse install and usage instruction
[19:49:41] <Not-e6c6> [02qtpyvcp] 07RENATOK opened issue 03#11: ImportError: No module named QtQuickWidgets - 13https://git.io/fjswB
[19:57:53] <JT[m]1> hmm I need to add the depends stuff
[20:09:30] <JT[m]1> done with chow already Chris?
[20:09:44] <Lcvette> yeah
[20:09:51] <Lcvette> trying to get this working
[20:09:58] <Lcvette> it is but something isn't quite right
[20:10:16] <JT[m]1> may the force be with you
[20:12:54] <Lcvette> getting invalid params in linear commands
[20:13:55] * Lcvette sent a long message: < https://matrix.org >
[20:14:21] <Lcvette> i see the params listed here and they are listed in the correct order
[20:14:30] <Lcvette> i have the receiving list identical
[20:14:35] <Lcvette> but the params don't seem to be lining up
[20:14:53] <JT[m]1> use debug prints to check
[20:15:29] <JT[m]1> remember the order you pass the parameter values in
[20:15:35] <Lcvette> dunno debugs\
[20:15:55] <Lcvette> i copied the list
[20:16:10] <Lcvette> pasted in the other receiving sub
[20:16:10] <JT[m]1> (debug, this is variable #<something>)
[20:16:11] <Lcvette> att he top
[20:16:19] <Lcvette> ah
[20:17:09] <JT[m]1> did you delete the (=somevalue)
[20:17:46] <Lcvette> yeah from the receiving sub
[20:17:49] <Lcvette> not the sending sub
[20:18:02] <Lcvette> as its a default value in the event a box is left blank
[20:18:07] <JT[m]1> that is correct then
[20:18:46] <JT[m]1> it should receive the value
[20:19:05] <JT[m]1> use debug to verify
[20:21:03] <Lcvette> just added debug
[20:21:05] <Lcvette> about to run
[20:21:28] * JT[m]1 runs and hides
[20:23:18] * Lcvette sent a long message: < https://matrix.org >
[20:24:59] <Lcvette> https://paste.ubuntu.com
[20:24:59] <Lcvette> thats the current sub-sub
[20:26:12] <JT[m]1> #<feed> = #<_feed>
[20:27:04] <JT[m]1> that is an error because #<_feed> is not defined anywhere
[20:27:57] <Lcvette> is that not a global parameter?
[20:28:26] <Lcvette> from whats set on the machine?
[20:28:28] <JT[m]1> if it has been set yea
[20:29:07] <JT[m]1> ah no, you have to set it in g code
[20:30:20] <Lcvette> k
[20:30:27] <Lcvette> i don't think my routines even use that feedrate
[20:30:53] <Lcvette> just sfr ffr and G0
[20:30:57] <Lcvette> i will remove it
[20:31:36] * Lcvette sent a long message: < https://matrix.org >
[20:31:57] <Lcvette> that is with the debug set to #1 #2 etc
[20:32:07] <Lcvette> doesn't look like its passing parameters
[20:32:55] <JT[m]1> what is the call line
[20:33:36] * Lcvette sent a long message: < https://matrix.org >
[20:33:44] <JT[m]1> me thinks you're missing the #
[20:33:56] <Lcvette> ah
[20:33:56] <JT[m]1> yup
[20:34:34] <JT[m]1> your passing values not the parameter values
[20:35:34] <JT[m]1> o<pzminus> call [#1] [#2] [#3] [#4] [#5] [#6] [#7] [#8] [#9] [#10] [#11] [#12] [#13] [#14]
[20:37:15] <Lcvette> adjusted and testing
[20:38:36] <Lcvette> \o/
[20:38:37] <Lcvette> Hurrray! :D
[20:38:38] <Lcvette> victory
[20:38:56] <JT[m]1> I knew you would win
[20:39:12] <Lcvette> lol
[20:39:40] <Lcvette> if you pushed hard enough you'd get me through the door
[20:39:50] <JT[m]1> yup
[20:40:02] <Lcvette> and we are certain it won't work with the (=xxx)
[20:40:10] <Lcvette> ?
[20:40:14] <JT[m]1> I'm the pusher from Sargent York
[20:40:44] <JT[m]1> that will be an error in a sub of a sub
[20:41:00] <Lcvette> cause other then that missing, everything else is untouched
[20:41:01] <Lcvette> ok
[20:41:04] <Lcvette> so close
[20:41:05] <Lcvette> but thats ok
[20:42:20] <JT[m]1> have you seen Sargeant York
[20:42:54] <Lcvette> no
[20:42:55] <Lcvette> ,pvie?
[20:42:58] <Lcvette> movie
[20:43:12] <JT[m]1> yes it's a must see movie
[20:44:21] <Lcvette> i will put it on my list
[20:44:22] <JT[m]1> right hand off by one lol
[20:44:47] <JT[m]1> and The Sand Pebbles
[20:47:08] <Lcvette> i looked but diidnt see anything about passing information from a subroutine to the gui
[20:47:48] <Lcvette> i used your docs to setup the probed position status labels and they are working
[20:47:58] <Lcvette> ]but i would like to report a diameter and x and y width probed
[20:48:42] <Lcvette> i saw some things on print but it looked like that was for reporting to the temrinal
[20:51:25] <JT[m]1> well msg can report to notifications
[20:51:27] <JT[m]1> I think
[20:53:35] <Lcvette> would like to rteport to a label
[20:54:21] <Lcvette> whats notifications?
[20:55:16] <Lcvette> like the little pop up thing?
[20:56:01] <JT[m]1> no it can display error, warning, info etc messaages
[20:56:41] <JT[m]1> the pop up crap is desktop notifications
[20:57:41] <Lcvette> ah
[20:58:24] * JT[m]1 wanders upstairs
[20:58:38] <Lcvette> Thanks JT for the help!!!!
[20:58:50] <Lcvette> I now have days worth of revisions to sort through
[20:58:51] <Lcvette> lol
[22:15:02] <Lcvette> JT: https://paste.ubuntu.com
[22:15:04] <Lcvette> \o/
[22:15:43] <Lcvette> turboss appears!
[22:15:44] <Lcvette> \o/
[22:17:02] <TurBoss> \ø(
[22:17:42] <Lcvette> :o
[22:18:25] <TurBoss> \ø/
[22:18:35] <TurBoss> sup¿
[22:18:57] <Lcvette> turboss has a busted head
[22:19:23] <TurBoss> :P
[22:19:41] <Lcvette> lcvette is out of his usually cloud juice
[22:19:56] <Lcvette> puffing some old carmel cheesecake juice
[22:21:07] <Lcvette> lcvette started over on the probe subs
[22:21:13] <TurBoss> why?
[22:21:28] <Lcvette> make them better
[22:21:33] <TurBoss> cool
[22:21:39] <Lcvette> they were too long
[22:21:47] <Lcvette> one was almost 600 lines
[22:22:25] <Lcvette> now they are easier to make
[22:22:27] <Lcvette> use subcall inside subcall
[22:22:31] <Lcvette> less chance of mistakes
[22:22:43] <TurBoss> nic3
[22:25:46] <Lcvette> do you know how to send information from a subroutine to a label?
[22:26:26] <Lcvette> i would like to report the probed width for x and y and siameter to a label or status label
[22:30:38] <TurBoss> dunbo
[22:37:55] <TurBoss> Lcvette: https://www.youtube.com
[22:38:05] <TurBoss> origin isn't show until you change view
[22:39:21] <Lcvette> i know
[22:39:22] <Lcvette> :(