#hazzy Logs
May 28 2020
#hazzy Calendar
12:00 AM * TurBoss sent a long message: < https://matrix.org/_matrix/media/r0/download/matrix.org/aHFcRUudQXJaDkSGpnCcwInJ >
12:01 AM Joco[m]: Eeek. MATH!!!
12:01 AM Lcvette1: im plotting to see if it is correct
12:06 AM TurBoss: 0.35 * cos(87)
12:06 AM TurBoss: isnt this correct?
12:08 AM Lcvette1: think we may have something wrong
12:08 AM Lcvette1: /o\
12:08 AM TurBoss: why?
12:11 AM Lcvette1: lcvette is struggling
12:12 AM Lcvette1: lol
12:12 AM TurBoss: :O
12:12 AM Lcvette1: trying to sort out what we need
12:12 AM * TurBoss sent a long message: < https://matrix.org/_matrix/media/r0/download/matrix.org/mLoJxWQrwrxgsXeQEEumTUbw >
12:12 AM TurBoss: 1 is ok?
12:13 AM * TurBoss sent a long message: < https://matrix.org/_matrix/media/r0/download/matrix.org/dqxTvwhBNeGxrllqizXFlVNq >
12:13 AM Lcvette1: neither is calculating correctly
12:13 AM TurBoss: ok
12:13 AM Lcvette1: im plotting it and not getting the correct positions
12:24 AM Lcvette1: lcvette can't figure it
12:25 AM Lcvette1: its like math is broken
12:30 AM Lcvette1: im an idiot
12:34 AM Lcvette1: i was plotting using .35 as the diameter of the circle so the radius was not .35 it was half
12:34 AM Lcvette1: but im still not getting the correct plot points
12:40 AM * Lcvette1 uploaded an image: image.png (111KB) < https://matrix.org/_matrix/media/r0/download/matrix.org/ggAjIsqTlmKZxQyQuhNKXNlj >
12:40 AM Lcvette1: this calculator is working but it doesn't show the formula
12:40 AM Lcvette1: \o/
12:59 AM Joco[m]: do you need to know the formula?
12:59 AM Lcvette1: yes
12:59 AM Joco[m]: or have you worked that out now?
12:59 AM Lcvette1: need the formula
12:59 AM Lcvette1: what i thought should work is not
12:59 AM Joco[m]: ok - basic trig then
01:00 AM Joco[m]: in theory - lol famous last wrods
01:00 AM Joco[m]: what are the known elements?
01:00 AM Joco[m]: side a?
01:01 AM Lcvette1: no
01:01 AM Joco[m]: b?
01:01 AM Lcvette1: hypot, and angle
01:01 AM Joco[m]: c and A?
01:01 AM Lcvette1: all 3 angles
01:01 AM Lcvette1: since right triangle
01:01 AM Lcvette1: 87,3,90
01:01 AM Lcvette1: hypot is .35
01:02 AM Joco[m]: solving for?
01:03 AM Lcvette1: the remianing 2 sides
01:05 AM TurBoss: yo
01:05 AM Lcvette1: yo
01:05 AM TurBoss: got something?
01:05 AM Lcvette1: found a calculator that gives the correct answer but it does not show the formula and im not having much luck finding a working formula
01:06 AM TurBoss: oh
01:06 AM Joco[m]: just working it out. Got the correct trig formulas
01:06 AM TurBoss: cool!
01:07 AM Joco[m]: All you need is A and c
01:07 AM Lcvette1: that all we got
01:07 AM TurBoss: ok afk 5 min
01:07 AM Lcvette1: k
01:08 AM Joco[m]: proofed a
01:10 AM Joco[m]: proofed b
01:11 AM Joco[m]: so, using the same letters per the image/calc you posted ....
01:11 AM Joco[m]: a = c * sin(A)
01:11 AM Joco[m]: b = c * cos(A)
01:13 AM * Joco[m] uploaded an image: image.png (22KB) < https://matrix.org/_matrix/media/r0/download/matrix.org/FuXAJGVdQZwsNfNWojUPjbOx >
01:13 AM Lcvette1: thats isn't giving me the corect answer
01:14 AM TurBoss: so what is A c?
01:14 AM Lcvette1: try it with A=87
01:14 AM Lcvette1: c=.35
01:14 AM Lcvette1: and tell me what you get for a and b
01:14 AM * Joco[m] uploaded an image: image.png (7KB) < https://matrix.org/_matrix/media/r0/download/matrix.org/mbDyMnBZgbuvVzeRFnXoeVhM >
01:15 AM Joco[m]: a = 0.34952
01:15 AM Joco[m]: b = 0.018317
01:15 AM Lcvette1: right answers but im notn getting that when i calculate it
01:15 AM Lcvette1: neither is the python formula
01:15 AM Joco[m]: let my try in python. I did this on calculator
01:16 AM Joco[m]: remember python is probably doing stuff in radians
01:16 AM Lcvette1: .35*cos(87)=
01:16 AM * TurBoss uploaded an image: Captura de pantalla de 2020-05-28 08-06-58.png (305KB) < https://matrix.org/_matrix/media/r0/download/jauriarts.org/rBsSGyqBamcqSbkqpIVVWFfY >
01:17 AM Joco[m]: if you are getting the wronfg answer I can pretty much guarantee it will becasue the python trig is looking for radians not degrees
01:17 AM TurBoss: so its not 87
01:17 AM TurBoss: rad(87)
01:17 AM Joco[m]: just looked up the docs
01:17 AM * TurBoss uploaded an image: Captura de pantalla de 2020-05-28 08-08-39.png (39KB) < https://matrix.org/_matrix/media/r0/download/jauriarts.org/IqjtubTgJFuhwQMaPGhcYpVO >
01:17 AM Joco[m]: you need to convert degrees to radians
01:18 AM Joco[m]: yup
01:19 AM * TurBoss uploaded an image: Captura de pantalla de 2020-05-28 08-10-01.png (66KB) < https://matrix.org/_matrix/media/r0/download/jauriarts.org/AZUdgUMCvakbHkaJFVAMyaRU >
01:19 AM TurBoss: Lcvette: !!^!!^!!
01:19 AM Joco[m]: lol
01:19 AM Lcvette1: \o/
01:19 AM Lcvette1: damn radians
01:19 AM Joco[m]: yup - catches people all the time
01:19 AM TurBoss: its correct?
01:19 AM Lcvette1: yes
01:20 AM TurBoss: \o/
01:20 AM Lcvette1: but,
01:20 AM TurBoss: 🥳
01:20 AM * Joco[m] bows
01:20 AM Lcvette1: now we need to solve the issue of the 0-360
01:20 AM TurBoss: thanks!
01:20 AM Lcvette1: thanks joco!
01:20 AM Lcvette1: while you are on a role!
01:20 AM Joco[m]: O.o
01:20 AM Lcvette1: any thoughts on that?
01:21 AM Lcvette1: our goal
01:21 AM Joco[m]: think you might need to explain the problem. not been watching this today
01:21 AM Joco[m]: been in meeting hell
01:21 AM Lcvette1: is to plot a triangle
01:21 AM Lcvette1: based on the front angle and back angle of the tool
01:22 AM Lcvette1: we are using a given radius or hypot of .35"
01:22 AM Lcvette1: in linuxcnc, the font and back angles are measured as in this image:
01:24 AM * Lcvette1 uploaded an image: image.png (54KB) < https://matrix.org/_matrix/media/r0/download/matrix.org/kBgNFvCMuwqZiChTSVhbiTtI >
01:25 AM Lcvette1: zero is on the right side
01:25 AM Lcvette1: and counts clockwise to 360 back at the right side
01:26 AM Lcvette1: so we need to be able to translate angles from 0-360 with a leg leaving the origin of .35"
01:26 AM Lcvette1: inot coordinates on a cartesian plane
01:27 AM Joco[m]: so the tool positions are fixed for the point but the front and back angle will change based on the specificis the insert/tool used?
01:27 AM Lcvette1: in order to have vtk draw the triangles according to the tool data
01:27 AM Lcvette1: correct
01:27 AM Lcvette1: depoending on the entered back angles
01:27 AM Lcvette1: front angles etc
01:27 AM TurBoss: reading I and J columns from the tooltable
01:28 AM * Lcvette1 uploaded an image: Screenshot_2020-05-28_00-22-40.png (45KB) < https://matrix.org/_matrix/media/r0/download/matrix.org/ROFjqoeSSzlxTVaONoTedTWi >
01:28 AM Joco[m]: ok. So they are just variables that define the angle at the nose
01:28 AM Lcvette1: FNT ANGLE and BACK ANG
01:28 AM Joco[m]: but that angle may not be symatrical about
01:28 AM Joco[m]: about the nose axis
01:28 AM Lcvette1: and the orientation of the tool
01:28 AM Lcvette1: we are making it symettrical
01:28 AM * TurBoss uploaded an image: image.png (13KB) < https://matrix.org/_matrix/media/r0/download/jauriarts.org/HIHAyKRKifEZjolehcfAtbqW >
01:28 AM TurBoss: Lcvette: ^^
01:29 AM Lcvette1: lets not confuse the issue turboss
01:29 AM TurBoss: ok
01:29 AM TurBoss: ok
01:29 AM Lcvette1: stick to the tsask at hand
01:30 AM Joco[m]: from that tool position doesn't linuxcnc assume that the tool nose is 0,0 for that purpose of the triangle?
01:30 AM Lcvette1: we are not dealing with anyhting bu the angles
01:30 AM Lcvette1: from a 0,0 point
01:31 AM Lcvette1: forget what turboss just posted
01:31 AM Joco[m]: lol - ok
01:31 AM Lcvette1: i think once this is sorted it would be the ground work for anything further anyways
01:31 AM Lcvette1: so one step at a time
01:32 AM Lcvette1: So the formula we just proofed works great if it were the upper right quadrant always
01:33 AM TurBoss: we need Q
01:33 AM TurBoss: 1-9
01:34 AM TurBoss: ```
01:34 AM TurBoss: tool_orientation_table = [135, 45, 315, 225, 180, 90, 0, 270]
01:34 AM Lcvette1: I don't know yet if that will be useful
01:34 AM TurBoss: thats how i set quads
01:34 AM * Joco[m] uploaded an image: ima_73075fb.jpeg (133KB) < https://matrix.org/_matrix/media/r0/download/matrix.org/hFEuTTcLlAJuNaIDvzMsxNXH >
01:35 AM Joco[m]: the tool orientation is moot from the point of view of the triangle used to represent front/back angles around that position. Yes?
01:36 AM Lcvette1: Bit we need to calculate the coordinates based off absolute angles
01:36 AM Lcvette1: That's my thought
01:36 AM Joco[m]: I understand. I'm just making sure I understand the base logic of the problem. Before going to the geometry constraints of the tools we have
01:36 AM Lcvette1: We need to translate the absolute angles into correct quadra t angles for the formula
01:37 AM Lcvette1: Ie, cannot enter 265 into the sohcahtoa formula
01:38 AM Joco[m]: you mean how the front and back angles get adjusted with reference to the tool positions angle?
01:38 AM Lcvette1: Bit we need it to translate into the correct x+/- z+/- coords
01:39 AM Joco[m]: I know. I'm pulling the piece of string to make sure I am not missing anything. Remember you guys have been discussing this for a while. I haven't.
01:39 AM Lcvette1: the front and back angle define the tool orientation
01:39 AM Joco[m]: hang on.
01:39 AM Lcvette1: ie a front angle of 265 with a back angle of 185 puts the tool orientation in the upper left quad
01:40 AM Joco[m]: ahhh
01:40 AM Joco[m]: see that is why I am pulling the string
01:40 AM Lcvette1: yup
01:40 AM Joco[m]: so the Q value in the linuxnc is not used
01:40 AM Lcvette1: im with you just trying to detemrine the best way to communicate it
01:40 AM Lcvette1: lol
01:40 AM Joco[m]: i.e. it does not form the basis off which the tool angles are defined?
01:41 AM Lcvette1: reqord that question
01:41 AM Lcvette1: * reword that question
01:41 AM Joco[m]: ok ....
01:41 AM Lcvette1: lol
01:41 AM Lcvette1: sorry
01:41 AM Lcvette1: :D
01:41 AM Joco[m]: if Q = 5
01:42 AM Joco[m]: then linuxcnc knows that is 180
01:42 AM Lcvette1: yes and no
01:42 AM Lcvette1: linux uses the Q# to determine the tool nose rsadius calcs
01:42 AM Joco[m]: so I would have expected the Front and Back angles in the tool table to be +/- off that
01:42 AM Lcvette1: not the actual to shape
01:43 AM Joco[m]: but you are saying they are not delta adjustments but absolutes
01:43 AM Lcvette1: they aren't
01:43 AM * Lcvette1 uploaded an image: image.png (52KB) < https://matrix.org/_matrix/media/r0/download/matrix.org/EFLGghfnRaHnCSdVBOThXJlQ >
01:43 AM Joco[m]: i.e. 190 and 170
01:43 AM Lcvette1: notice position 7 shows a front angle of 330
01:43 AM Joco[m]: ok. still just math. All good
01:43 AM Lcvette1: back angle of 30
01:44 AM Lcvette1: if you go around the tools you will see the front and back angle sweep 0-360 clockwise from the z axis line on the right
01:44 AM Joco[m]: so what result does VTK need to work?
01:44 AM Lcvette1: coordinates
01:44 AM Joco[m]: angle wise?
01:44 AM Lcvette1: lol
01:45 AM Lcvette1: it doesn't know angles
01:45 AM Lcvette1: cartesian coords
01:45 AM Joco[m]: so all we need to solve is a way to get the lengths of sides so a coord can be calculated?
01:45 AM Lcvette1: which is why we were using the formula to detemrin the legs of a and b which translate into coords
01:45 AM Joco[m]: k
01:46 AM Lcvette1: but they need to be x+/- z+/-
01:46 AM Lcvette1: to define correct orientation of the tool image drawn
01:47 AM Joco[m]: is the centre of your image above the 0,0 point?
01:47 AM Lcvette1: the constsant point for all tools will be 0,0
01:47 AM Lcvette1: the origin of the cartesian plane
01:48 AM Joco[m]: well put it a different way. is 0,0 the tip of each tool
01:48 AM Lcvette1: yes
01:48 AM Joco[m]: ok ... need to think
01:48 AM Lcvette1: ok i need to sleep, almost 3am here and i have work in 4 hours
01:48 AM Lcvette1: /o\
01:48 AM Joco[m]: sleep - if i have a pattern will post here
01:49 AM Lcvette1: ok
01:49 AM Lcvette1: have fun!
01:49 AM Lcvette1: :d
01:49 AM Lcvette1: \o/
01:49 AM Lcvette1: night turboss!
01:49 AM Joco[m]: I've done this before in game tool dev
01:49 AM Lcvette1: night joco!
01:49 AM TurBoss: nigt
01:49 AM Joco[m]: just need to brush off old brain
01:49 AM Joco[m]: nite
01:49 AM Lcvette1: i know the feeling
01:49 AM Lcvette1: that radians thing was killin me
01:49 AM Lcvette1: thought i was loosing my mind
01:49 AM Joco[m]: lol
01:50 AM Lcvette1: i knew that formula should work but was kickin out wrong answers
01:54 AM Lcvette1: phuck me
01:54 AM Lcvette1: 0.35 * sin(87) gives the correct coords
01:55 AM Lcvette1: * 0.35 * sin(265) gives the correct coords
01:55 AM * Lcvette1 uploaded an image: image.png (50KB) < https://matrix.org/_matrix/media/r0/download/matrix.org/MFXwDYTasxDkiDhsGmssAVSU >
01:57 AM Lcvette1: but its inverted on X
01:57 AM Lcvette1: 0.35 x sin265 = -.3487
01:57 AM Lcvette1: * 0.35 x sin265 = -0.3487
01:58 AM Joco[m]: yeah - I think you might have been making it harder than it is
01:58 AM Joco[m]: but you need sleep
01:58 AM Joco[m]: let me muck about with this.
01:58 AM Joco[m]: only 6:50pm here
01:58 AM Lcvette1: 0.35 x cos265 = -0.0305
01:59 AM Lcvette1: so the cos is correct here but the sin is inverted
02:01 AM Lcvette1: maybe a combination of Q to define the +/_ symbols and the formula combined kicking out an absolute value would work
02:01 AM Lcvette1: * maybe a combination of Q to define the +/- symbols and the formula combined kicking out an absolute value would work
02:02 AM Lcvette1: turboss, could you do that?
02:02 AM Lcvette1: in python?
02:03 AM Lcvette1: with an if statement
02:03 AM TurBoss: yes
02:03 AM Lcvette1: if Q=# then the result of the formula would have + or _ to the cartesian coord
02:03 AM TurBoss: yes
02:04 AM Lcvette1: great then i think we have the solution
02:04 AM TurBoss: cool!
02:04 AM Lcvette1: or couls use the angles too
02:06 AM * Lcvette1 sent a long message: < https://matrix.org/_matrix/media/r0/download/matrix.org/ZwYfzfmjSkLVJAZresazMprP >
02:07 AM Lcvette1: night be better to use an angles rule
02:08 AM Lcvette1: \o/
02:56 AM Joco[m]: hmmm. I think I am missing something here.
02:56 AM Joco[m]: or we are
02:57 AM Joco[m]: if we look at position #4 on the tool positino graphic
02:58 AM Joco[m]: and we treat the red cross intersection as a 0,0 for relative reference.
02:58 AM Joco[m]: i.e the tip of the tool
03:01 AM * Joco[m] uploaded an image: ima_555a02f.jpeg (11KB) < https://matrix.org/_matrix/media/r0/download/matrix.org/zJLSDskgVkvrjlkutKUifOas >
03:02 AM Joco[m]: if I an looking to calculate the point I have circled. I presume we need to calculate the two black lines from the red cross centre?
03:03 AM Joco[m]: So that you get the correct x/z offsets from that nominal 0,0
03:03 AM Joco[m]: at the centre of the red cross
03:15 AM TurBoss: what i have
03:15 AM * TurBoss uploaded an image: image.png (33KB) < https://matrix.org/_matrix/media/r0/download/jauriarts.org/hBAYjotpxNmPrcUwKIWopbiI >
03:17 AM Joco[m]: ok to calc the back two corners of that triangle you need to have an angle and the length of the edge.
03:17 AM TurBoss: yes
03:18 AM Joco[m]: so we have angles (front/back) and the edge? from tool table
03:18 AM TurBoss: what do you mean by the edje?
03:19 AM Joco[m]: the long sides of your triangle
03:20 AM Joco[m]: unless that is a static size you are just using for how you represent a pretend tool on VTK
03:21 AM Joco[m]: in not very familiar with the tooltable content from a lathe angle
03:21 AM TurBoss: yes lenght is static
03:22 AM Joco[m]: rgr - cool
03:22 AM Joco[m]: so ....
03:23 AM Joco[m]: if you need to get the position of the point of the back left/bottom corner of your red triangle do you need to have the offset values based off the axes of my black lines?
03:24 AM Joco[m]: i.e. left n units and up n units
03:24 AM TurBoss: I think Lcvette wants to just set the angle
03:24 AM TurBoss: not offset
03:25 AM Joco[m]: he can set the angle from tool table but under the hood you have to do those calcs to get the x/z offsets - don't you?
03:25 AM TurBoss: yes
03:25 AM TurBoss: i missunderstood
03:26 AM Joco[m]: cool - I'm not going mad. So that means for this example what you are doing is something like .....
03:26 AM Joco[m]: using Q = tool position angle, B = back angle and F = front angle
03:28 AM Joco[m]: angle for trig calc = (Q -45) - B
03:32 AM Joco[m]: and I think same for other point, just - F
03:32 AM Joco[m]: instead of -B
03:33 AM Joco[m]: think will map out on s/s makes easier to see all the variations as you move around the cirrcle
04:10 AM Joco[m]: been looking at it and while you might be able to get clever and have a small number of calcs I think the simplest way to do it is to just have an if statement for each tool positiion and then get the calc for the x/z offsets exactly right for that location. Will also be easier to debug as well.
04:14 AM Joco[m]: a little more code maybe but way more obvious as to what is happening. Just a thought.
04:17 AM * TurBoss sent a long message: < https://matrix.org/_matrix/media/r0/download/matrix.org/WLfVAqKylzgGmGkWlJbayZjM >
04:17 AM TurBoss: tool.diameter is tool.orientation
04:17 AM * TurBoss sent a long message: < https://matrix.org/_matrix/media/r0/download/matrix.org/AXYDNYtOcANvJoFarvdJitNH >
04:19 AM Joco[m]: yup that could work
04:26 AM Joco[m]: just need to set a 1 multiplier in those if statments. and maybe make p1_x and p1_z absolute
04:44 AM JT-Cave-: morning
05:10 AM TurBoss: morning
05:11 AM Joco[m]: morning JT
05:22 AM JT-Cave: another rainy day here... should get the exhaust finished lol can't work on chicken stuff
07:36 AM Lcvette1: Morning
07:58 AM JT-Shop: morning
08:03 AM Lcvette1: turboss you did it!
08:03 AM Lcvette1: \o/
08:03 AM Lcvette1: hurray!
08:03 AM TurBoss: no
08:03 AM Lcvette1: oh
08:04 AM Lcvette1: no worky
08:04 AM TurBoss: not yet
08:04 AM Lcvette1: ah
08:04 AM Lcvette1: :D
08:04 AM Lcvette1: you sleeping?
08:04 AM Lcvette1: youn were up late
08:05 AM TurBoss: had a little nap
08:05 AM Lcvette1: nice, same
08:05 AM Lcvette1: lcvbette wants another nap
08:05 AM Lcvette1: lol
08:05 AM TurBoss: I was talking to my friend about the maths involed
08:05 AM TurBoss: he is math profesor now
08:05 AM TurBoss: lol
08:06 AM Lcvette1: nice
08:06 AM TurBoss: I didn't remember
08:06 AM Lcvette1: did he have any thoughts?
08:07 AM TurBoss: he will take a look when posible
08:09 AM Lcvette1: great!
09:30 AM * JT[m] uploaded an image: VectorImage_2020-05-28_092010.jpg (3076KB) < https://matrix.org/_matrix/media/r0/download/matrix.org/paEccHoxbyFczpjbLHsWdtrd >
09:30 AM JT[m]: Just need to line everything up and torque everything down
09:30 AM Lcvette1: nice JT!
11:31 AM JT-Shop: Lcvette1, turns out the only Magnaflow part on the whole exhaust was the tips lol
11:31 AM Lcvette1: yeah that seems to be about right from the look of the welds on that system
11:31 AM Lcvette1: magnaflow is pretty shiny and high quality loking usually
11:32 AM * JT[m] uploaded an image: VectorImage_2020-05-28_112254.jpg (5862KB) < https://matrix.org/_matrix/media/r0/download/matrix.org/LPFycOvdeZGqBrlQtETSvCdF >
01:32 PM Lcvette1: ]yeah thats not magnaflow quality
01:32 PM Lcvette1: lol
01:32 PM TurBoss: Lcvette: I have something to test for lathe tool
01:32 PM TurBoss: \o/
01:32 PM Lcvette1: thats some Jeb quality from the dirty muffler shop down the road
01:32 PM Lcvette1: you have a test for me?
01:32 PM Lcvette1: \o/
01:32 PM Lcvette1: Huirray!
01:32 PM TurBoss: pushing
01:33 PM Not-944e: [02qtpyvcp] 07TurBoss pushed 031 commit to 03VTK_Lather [+0/-0/±1] 13https://git.io/JfoVa
01:33 PM Not-944e: [02qtpyvcp] 07TurBoss 0366fa110 - take I and J to draw the tool
01:34 PM Not-944e: [02probe_basic] 07Lcvette pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/JfoVV
01:34 PM Not-944e: [02probe_basic] 07Lcvette 0311d7627 - lathe tool table updates
01:35 PM Not-944e: [02probe_basic] 07KurtJacobson pushed 031 commit to 03gh-pages [+88/-0/±0] 13https://git.io/JfoVP
01:35 PM Not-944e: [02probe_basic] 07traviscibot 03837215f - Deploy kcjengr/probe_basic to github.com/kcjengr/probe_basic.git:gh-pages
01:36 PM Lcvette1: almost
01:36 PM Lcvette1: its changing
01:36 PM Lcvette1: but the legs are different lengths
01:36 PM Lcvette1: turboss ^^^
01:36 PM TurBoss: 😕
01:37 PM Lcvette1: oh wait
01:37 PM Lcvette1: it is the right shape, but wrong position
01:37 PM TurBoss: oh
01:37 PM TurBoss: ????
01:38 PM * Lcvette1 uploaded an image: Screenshot_2020-05-28_14-29-13.png (7KB) < https://matrix.org/_matrix/media/r0/download/matrix.org/bFSrPyiArxTATMZCXKVVObNT >
01:39 PM TurBoss: do you have tool offsets?
01:40 PM TurBoss: can be confusing
01:40 PM Lcvette1: this tool should be flipped on the z axis
01:41 PM Lcvette1: i removed all offsets now
01:41 PM Lcvette1: work and tool
01:42 PM Lcvette1: tool is still showing away from machine coords o,o
01:42 PM Lcvette1: sek im going to restart to see if it fixes
01:42 PM TurBoss: cool
01:42 PM TurBoss: ok
01:50 PM Lcvette1: i think maybe something is broken in the offsets table
01:50 PM Lcvette1: keep changing to -.1000 for all work fofsets
01:50 PM Lcvette1: any thoughts?
01:52 PM TurBoss: seems that offsets change and save tooltable not ok
01:54 PM Lcvette1: yeah think offsets table and or tool table is broken
01:54 PM Lcvette1: :(
01:56 PM TurBoss: on save they are not refreshed
01:56 PM TurBoss: needs a restart
02:00 PM Lcvette1: signals and slots?
02:01 PM JT-Shop: that's way better a nice rumble but not too loud you can't hear the radio... now to put the sway bar back on and get it back down to the ground
02:02 PM Lcvette1: nice JT-Shop
02:04 PM Lcvette1: TurBoss: i aded suignals and slots
02:04 PM Lcvette1: it clears, but it isn't saving and returns the previous values on reload
02:04 PM TurBoss: on save its not changing
02:05 PM Lcvette1: oh wait
02:05 PM Lcvette1: i needed to have power button and estop ready
02:06 PM Lcvette1: ok offsets is working now
02:06 PM Lcvette1: tool orientation is wrong still
02:06 PM Lcvette1: can you show me the rules?
02:07 PM Lcvette1: if statements for the tool leg points
02:07 PM TurBoss: no one talks about the fight club
02:07 PM TurBoss: wich rules?
02:07 PM TurBoss: :P
02:07 PM Lcvette1: you are not a unique and special snowflake
02:07 PM Lcvette1: :D
02:07 PM TurBoss: :-)
02:07 PM TurBoss: wich rules?
02:07 PM Lcvette1: the vtk draw tool rule
02:07 PM Lcvette1: for quadrants
02:08 PM TurBoss: there isn't
02:08 PM TurBoss: it just applyes the front and back angle
02:08 PM Lcvette1: yes but you have if statements right?
02:08 PM TurBoss: tool tip remains 0.0 + offset
02:08 PM TurBoss: unused
02:08 PM Lcvette1: for angle and x +/- z +/-
02:08 PM Lcvette1: ?
02:09 PM Lcvette1: if you just use the sin cos with the front and back angles and use those results they will be wrong
02:09 PM Lcvette1: maybe thats what is happening here
02:10 PM * Lcvette1 sent a long message: < https://matrix.org/_matrix/media/r0/download/matrix.org/PGHbglxBpUDiXRDNnXGkDuJm >
02:10 PM TurBoss: I found update_tool needs lathe specific stuff
02:10 PM * TurBoss sent a long message: < https://matrix.org/_matrix/media/r0/download/matrix.org/mYOcnvjwxqUtfzmsAabUfUug >
02:11 PM Lcvette1: you need to change the result signs on the answers
02:11 PM TurBoss: ok
02:12 PM Lcvette1: like in the one above you had
02:12 PM Lcvette1: 0-90, 91-180, 181-270, 270-360
02:12 PM Lcvette1: or it will not draw in the correct quadrant
02:18 PM TurBoss: ok
02:18 PM * TurBoss sent a long message: < https://matrix.org/_matrix/media/r0/download/matrix.org/FsmDhjAngIaFVsJuOstyWnZR >
02:20 PM Lcvette1: coorect
02:21 PM Lcvette1: it is drawing them perfect except the quadrant they should be in
02:30 PM TurBoss: ok got it
02:30 PM Not-944e: [02qtpyvcp] 07TurBoss pushed 031 commit to 03VTK_Lather [+0/-0/±1] 13https://git.io/JforN
02:30 PM Not-944e: [02qtpyvcp] 07TurBoss 03b6ac42c - apply quadrant modifiers
02:30 PM TurBoss: Lcvette: can you test again?
02:30 PM TurBoss: this one is the good one
02:30 PM Lcvette1: yes
02:32 PM TurBoss: position 1 7 5 show correctly here
02:32 PM Not-944e: [02qtpyvcp] 07TurBoss pushed 031 commit to 03VTK_Lather [+0/-0/±1] 13https://git.io/Jfooe
02:32 PM Not-944e: [02qtpyvcp] 07TurBoss 034e30b44 - bypass tranform
02:33 PM * Lcvette1 uploaded an image: Screenshot_2020-05-28_15-24-10.png (7KB) < https://matrix.org/_matrix/media/r0/download/matrix.org/xISuJbycfezZPxWfzSepFaTC >
02:33 PM Lcvette1: /o\
02:34 PM TurBoss: :O
02:34 PM Lcvette1: lol
02:35 PM TurBoss: is the tooltable data correct?
02:35 PM Joco[m]: Morning
02:35 PM TurBoss: morning Mr Joco
02:35 PM Lcvette1: yes according to linuxcnc docs
02:36 PM Joco[m]: TurBoss: in those if statements where are your -1 and 1 asignmemts for the movement direction later?
02:36 PM Lcvette1: o/
02:36 PM Lcvette1: morning joco!
02:36 PM Joco[m]: Morning Lcvette
02:37 PM * TurBoss uploaded an image: Captura de pantalla de 2020-05-28 21-28-01.png (25KB) < https://matrix.org/_matrix/media/r0/download/jauriarts.org/fmxdYNOmInyMLHkmurHoWLlc >
02:37 PM TurBoss: this tools are shown correctly for me
02:37 PM Joco[m]: Just asking question as at the moment per that code that if block seems to do nothing.
02:38 PM Lcvette1: your tool table is wrong
02:38 PM * TurBoss sent a long message: < https://matrix.org/_matrix/media/r0/download/matrix.org/rMlxSNpKrRHudhUHAuKuNcqp >
02:38 PM TurBoss: why?
02:39 PM TurBoss: whats wrong?
02:39 PM Joco[m]: That looks better. One i saw above still had pass in it
02:39 PM TurBoss: noticed a bug in the code I pasted
02:40 PM TurBoss: ```
02:40 PM TurBoss: points.InsertNextPoint((offset[2], 0.0, offset[0]))
02:40 PM * Lcvette1 uploaded an image: Screenshot_2020-05-28_15-31-06.png (45KB) < https://matrix.org/_matrix/media/r0/download/matrix.org/qIFApyHwIKKUpUvXxAaHdViF >
02:40 PM TurBoss: is 0 the 2
02:41 PM Joco[m]: As a suggestions do the x-pol multiplications before the insert and print. So can see real values being used from your print statements
02:41 PM TurBoss: * is 0 then 2
02:41 PM TurBoss: ok
02:43 PM Lcvette1: turboss you need the updated tool table i sent above
02:43 PM Lcvette1: its in latest PB
02:43 PM Not-944e: [02qtpyvcp] 07TurBoss pushed 031 commit to 03VTK_Lather [+0/-0/±1] 13https://git.io/JfooY
02:43 PM Not-944e: [02qtpyvcp] 07TurBoss 03b7eb4c7 - do math before
02:44 PM TurBoss: ok
02:46 PM Lcvette1: but it broke
02:46 PM Lcvette1: /o\
02:46 PM * Lcvette1 uploaded an image: Screenshot_2020-05-28_15-37-11.png (23KB) < https://matrix.org/_matrix/media/r0/download/matrix.org/ZJwlSayuehGoQTgaSHTYNJQB >
02:47 PM Lcvette1: TurBoss: ^^^
02:47 PM Lcvette1: :o
02:47 PM TurBoss: yes
02:47 PM TurBoss: just pressed w/s
02:47 PM * Lcvette1 sent a long message: < https://matrix.org/_matrix/media/r0/download/matrix.org/wiLAoycwJURqgmAXFbwcXDwk >
02:47 PM Lcvette1: ambigous shortcut overload
02:47 PM Lcvette1: :D
02:47 PM Lcvette1: \o/
02:47 PM Lcvette1: lol
02:48 PM TurBoss: somethin ok?
02:48 PM TurBoss: need to smoke
02:50 PM Lcvette1: me too
02:50 PM Lcvette1: turboss it is working fantastic
02:50 PM Lcvette1: but we have one thing to solve
02:50 PM Lcvette1: and i don't know a good way to solve it
02:50 PM Lcvette1: grooving tools
02:51 PM Lcvette1: they have usually a 90* front and back angle
02:51 PM TurBoss: does Joco smoke
02:51 PM Lcvette1: so it essentially disappears
02:51 PM TurBoss: 90 90 is a flat line
02:51 PM TurBoss: should be 110 90 80
02:51 PM Joco[m]: Nope. Dad was a big pipe smoker. He quite when we were kids and drummed anti smoking into us.
02:52 PM TurBoss: cool
02:52 PM TurBoss: don't smoke
02:52 PM TurBoss: 🚬
02:54 PM * hazzy-m only smokes cigars and pipes occasionally
02:54 PM TurBoss: if nuzelar magic isnt gona kill you smoke is fine
02:55 PM TurBoss: like yin yanf
02:55 PM TurBoss: * like yin yang
02:55 PM TurBoss: equilibrium
02:55 PM TurBoss: Lcvette: makes any sense to you 110 FA 80 BA?
02:56 PM TurBoss: in Q64
02:58 PM TurBoss: sorry Q6
03:02 PM Lcvette1: yo
03:02 PM Lcvette1: sorry had to get the mail
03:02 PM TurBoss: np
03:02 PM Lcvette1: can't change the front and back angle
03:03 PM Lcvette1: its important to linuxcnc kinematics
03:03 PM Lcvette1: has to be correct
03:03 PM Lcvette1: and other tools for position 6 are triangles
03:04 PM TurBoss: @lcvette if you place 2 lines in same angle the will not show
03:04 PM TurBoss: that or Im missing something else
03:05 PM Lcvette1: can we make a rule?
03:05 PM Lcvette1: if front angle and back angle are 90, 90 then draw a rectangle?
03:05 PM TurBoss: how
03:05 PM TurBoss: how should look
03:06 PM * Lcvette1 uploaded an image: VectorImage_2020-05-28_035744.jpg (73KB) < https://matrix.org/_matrix/media/r0/download/matrix.org/qxcOSspxmbrlVjvkdEizanPM >
03:09 PM TurBoss: ok this is very broke
03:10 PM Lcvette1: whats broke?
03:12 PM Joco[m]: <Lcvette1 "if front angle and back angle ar"> Should be able to. Just more if logic.
03:12 PM Lcvette1: im not sure how linuxcnc handle grooving tools
03:12 PM Joco[m]: Make TurBoss work lol
03:14 PM Joco[m]: If anyone has any framework level requirements let me know. More comfortable in that space 😎
03:15 PM TurBoss: 🚆
03:16 PM TurBoss: is VTK plotter a framerowk level?
03:16 PM TurBoss: :P
03:16 PM * TurBoss takes some ralaxing minutes 30 aprox or maybe more
03:19 PM Lcvette1: ok
03:20 PM Lcvette1: i think maybe if 90, 90 then make rectangle, one side will be at the control crosshars the other will be an arbitray distance away
03:20 PM Lcvette1: too bad we can't have a width input for the tool
03:20 PM Lcvette1: they generally come in standard 1mm, 1.5mm 2mm, 2,5mm, 3mm etc
03:20 PM Lcvette1: width of cut
03:22 PM Joco[m]: Weeee thread mills out for delivery with courier. I get to learn that process this weekend
03:25 PM Lcvette1: its easy peasy
03:25 PM Lcvette1: lcvette threadmills ALL THE TIME!!!!
03:25 PM Lcvette1: lol
03:25 PM Lcvette1: trick is figuring out what fit you like
03:25 PM Lcvette1: and adjkusting the recipe
03:26 PM Lcvette1: I am happy to give some help if needed!
03:26 PM Lcvette1: ok lcvette goes back to the shop
03:26 PM Lcvette1: turboss what is working is fantastic!!
03:26 PM JT-Shop: Lcvette1, thanks again for the link on that mid pipe that saved my ass
03:27 PM Lcvette1: no worries!!
03:27 PM Lcvette1: alot less work then what you were getting ready to try and do
03:27 PM Lcvette1: lol
03:27 PM Lcvette1: bolt on for the win
03:27 PM Lcvette1: \o/
03:27 PM Joco[m]: Lcvette: that would be awesome!
03:28 PM Joco[m]: Lcvette: just remember im a metric lad.
03:28 PM Joco[m]: 😱😋😂
03:30 PM Joco[m]: <TurBoss "is VTK plotter a framerowk level"> Errr. I think that is your baby. Been way too long since i had to think in matrix math for graphics stuff.
03:30 PM Lcvette1: same same
03:30 PM Lcvette1: thread diameter - drill diameter = pitch diameter offset
03:30 PM Lcvette1: then just add a few hundreths?
03:31 PM Lcvette1: whats equivelant to saying add a few thousandths in metrid
03:31 PM Lcvette1: * whats equivelant to saying add a few thousandths in metric
03:31 PM TurBoss: 🛫
03:31 PM Joco[m]: Hundreds i would say
03:32 PM Lcvette1: i usually add 0.004" to the pitch diameter offset on a new thread
03:32 PM Lcvette1: it generally is a smidge tight still so I bump it up 0.001" and rerun until i get the fit then i save that recipe for that thread
03:32 PM Joco[m]: A thou is 2.5 hundreds
03:32 PM Lcvette1: so add 10 hundreds
03:33 PM Lcvette1: or does that become one tenth mm?
03:33 PM Lcvette1: 0.10mm = 0.003937"
03:33 PM Lcvette1: so yeah
03:34 PM Lcvette1: start by adding 0.10mm to the calculated pitch diameter offset
03:34 PM Joco[m]: A tenth
03:34 PM Lcvette1: whats the drill size for m6x1.0 tap?
03:34 PM Lcvette1: 5mm?
03:34 PM Lcvette1: 5.2mm
03:34 PM Lcvette1: ?
03:35 PM Joco[m]: 5
03:35 PM Lcvette1: ok so your pitch diameter offset would be:
03:35 PM Lcvette1: 6-5+0.1= 1.1mm pitch diameter offset
03:35 PM Lcvette1: add that number in fusion for M6
03:36 PM Joco[m]: Rgr
03:36 PM Lcvette1: very important to use the correct /same size drill as is used in the calculations
03:36 PM JT-Shop: yea once the old crap was out it was easy
03:36 PM Joco[m]: Going to get some scrap to run test holes
03:36 PM Lcvette1: you'll do one and if youn use that formula it will be damn near where it should be
03:37 PM Lcvette1: then you can go nuts
03:37 PM Joco[m]: <Lcvette1 "very important to use the correc"> I can imagine. Else things can break
03:37 PM Lcvette1: other thing is just make sure the drilled hole is deeper than the required thread and that you go in and set the thread depth in fusion
03:37 PM Lcvette1: so if your threadmill can do 13mm depth threads, drill the hole 14mm
03:38 PM Lcvette1: 14.5mm
03:38 PM Joco[m]: Will be doing through holes to start with
03:38 PM Lcvette1: give it enough clesrance so that it won't touch the bnoittom
03:38 PM Joco[m]: Rgr
03:38 PM Lcvette1: ok then just make sure not to go deeper than the threadmill allows
03:39 PM Lcvette1: you will have to set the top of the hole as the top and offset from the top for the bottom
03:39 PM Lcvette1: best practice so you never miscalulate a distance from the bottom and break the thread mill
03:39 PM Joco[m]: Yup. And i will not be able to reach all the way. But that is fine. Dont want the screws to be able to mare the mill table.
03:40 PM Joco[m]: Re fixture plate.
03:40 PM Joco[m]: Good call. Will remember that.
03:41 PM Lcvette1: its fun threadmilling and the threads come out so nice and pretty and shiny
03:41 PM Lcvette1: lol
03:41 PM Joco[m]: Im quite excited for this. I have a LOT of holes to thread. Doing by hand was not going to be fun.
03:42 PM Lcvette1: if you make threaded dowel pins on the lathe and threadmill on the mill for receiver threads you can make the threads a bit snug and the pins will align with precision
03:43 PM Lcvette1: i do that alot for ficture plates on different part runs
03:43 PM Joco[m]: Now that is an interesting idea.
03:44 PM Joco[m]: So no slip fit pin holes? All holes threaded?
03:44 PM Lcvette1: yeah its nice having that flexibility
03:44 PM Lcvette1: don't need reemed holes
03:44 PM Lcvette1: and can move the threaded dowels anywhere on your table theres threads
03:44 PM Lcvette1: easy to expand the fixturing patterns
03:45 PM Joco[m]: I have a bunch of dowel pins. I can clock then on lathe and thread
03:45 PM Lcvette1: can also make big pucks with threads on the back for flipping parts
03:45 PM Lcvette1: ie part with a round pocket
03:45 PM Lcvette1: make a 2" puck with an M8 threaded boss to screw into the fixture table
03:45 PM Lcvette1: lots of awesome fun things with thread mills
03:46 PM Joco[m]: Yeah. Might need to revise my hole design a bit.
03:46 PM Lcvette1: can do dual sizes too
03:47 PM Lcvette1: M6 stepped to M8 or M10
03:47 PM Lcvette1: threadmill is very precise on where the threads start
03:47 PM Lcvette1: unlike taps
03:47 PM Lcvette1: or do M8 threads with a 6mm pin hole below it
03:47 PM Lcvette1: dual use
03:48 PM Joco[m]: That stepped hole could be very handy
03:48 PM Lcvette1: yeah
03:48 PM Lcvette1: just ned you plate to be thick enough to do it
03:51 PM * Joco[m] uploaded an image: ima_40cf949.jpeg (106KB) < https://matrix.org/_matrix/media/r0/download/matrix.org/KYQUCUDxCNBuVRZEdHCiONxh >
03:51 PM Lcvette1: How thick?
03:52 PM Joco[m]: Im trying to balance the types of work i do. Lots of small parts so lots of m6 holes
03:52 PM Joco[m]: 15mm steel
03:54 PM Joco[m]: But also a slection of 10mm dowel pin holes and m10 holes for clamping kit.
03:55 PM Joco[m]: There are also some specific holes for vice mounting
03:56 PM Joco[m]: Its about 400mm long and 196 wide
03:58 PM * Joco[m] uploaded an image: ima_c155023.jpeg (219KB) < https://matrix.org/_matrix/media/r0/download/matrix.org/GyqMOJZghLyQxpVWgjfceEmt >
03:59 PM Joco[m]: The blank with mounting holes ready to go on cnc
04:42 PM * Joco[m] has threadmills in his hot little hands :-)
04:43 PM Not-944e: [02qtpyvcp] 07TurBoss pushed 032 commits to 03VTK_Lather [+0/-0/±2] 13https://git.io/JfoP8
04:43 PM Not-944e: [02qtpyvcp] 07TurBoss 037c3dee6 - fix lathe tool offsets
04:44 PM Not-944e: [02qtpyvcp] 07TurBoss 03c3037a3 - fix tool offsets for mill also
04:45 PM TurBoss: now on save tooltable ploter reloads too
04:45 PM TurBoss: no need to restart
04:48 PM Joco[m]: you are on a roll
05:07 PM TurBoss: aparently we don't need Q in the equation
05:09 PM Joco[m]: we don't?
05:10 PM * TurBoss uploaded a video: lathe tool angle.webm (20KB) < https://matrix.org/_matrix/media/r0/download/jauriarts.org/ePKgwTDlfCPVJJCFnDJZlxrq >
05:10 PM TurBoss: tool changes from 1 - 9
05:11 PM TurBoss: <Lcvette1 "image.png"> taking this as reference
05:11 PM * TurBoss uploaded an image: Captura de pantalla de 2020-05-29 00-02-47.png (58KB) < https://matrix.org/_matrix/media/r0/download/jauriarts.org/QwnnzddHpScxbNdxtuCJEzjE >
05:12 PM TurBoss: and this tooltable
05:12 PM Joco[m]: from a VTK angle thought we needed to consider Q to get the correct offsets for rendering on the display?
05:14 PM Joco[m]: or is your no Q thing relating to something else?
05:15 PM TurBoss: twhe tooltip was a circle yes
05:15 PM TurBoss: was nedded
05:15 PM TurBoss: * when tooltip was a circle yes
05:15 PM TurBoss: * was needed
05:18 PM TurBoss: with inserting the front and back angle based on the picture
05:19 PM TurBoss: there is no need for Q
05:20 PM TurBoss: <TurBoss "image.png"> we had this the black circle
05:20 PM TurBoss: <TurBoss "image.png"> but now this
05:23 PM * TurBoss sent a long message: < https://matrix.org/_matrix/media/r0/download/matrix.org/dsPbmrqsJtRydKIwIqNqBkVl >
06:04 PM Lcvette1: you did it turboss?
06:05 PM TurBoss: with the given tool table it acts correctly
06:05 PM TurBoss: offsets are take on save now
06:06 PM Lcvette1: its broken again
06:06 PM Lcvette1: was working before
06:07 PM Lcvette1: wrong quadrant
06:07 PM TurBoss: ok
06:09 PM * Lcvette1 uploaded an image: Screenshot_2020-05-28_18-58-21.png (1KB) < https://matrix.org/_matrix/media/r0/download/matrix.org/eojApKerSQoolRXEwTvIZkbf >
06:09 PM Lcvette1: this should be in quadrant 2
06:10 PM TurBoss: there are logs now
06:12 PM TurBoss: its upside
06:18 PM * TurBoss uploaded an image: Captura de pantalla de 2020-05-29 01-08-51.png (107KB) < https://matrix.org/_matrix/media/r0/download/jauriarts.org/FelbJPcNzzBNyrLqwMhFgYhe >
06:30 PM Lcvette1: fixed?
06:30 PM Lcvette1: you are changing the fonrt and back angles
06:30 PM Lcvette1: lol
06:30 PM Lcvette1: those tools have specific front and back angles built into the tool holder and insert
06:30 PM Lcvette1: :D
06:30 PM Lcvette1: lol
06:30 PM TurBoss: lol
06:31 PM TurBoss: well
06:31 PM TurBoss: it works
06:31 PM Lcvette1: hurray!
06:31 PM TurBoss: have you tried?
06:31 PM Lcvette1: not since the broken one
06:32 PM Lcvette1: did you push?
06:33 PM TurBoss: maybe is the positive negative begin wrong?
06:33 PM Lcvette1: it works beforree this push
06:34 PM Lcvette1: but this last push you did its broken again
06:34 PM TurBoss: hmm
06:36 PM hazzy-m: hello
06:36 PM * hazzy-m is finally on dev
06:36 PM Lcvette1: \o/
06:36 PM Lcvette1: hurray!!
06:36 PM Lcvette1: lathe desperately needs the dro entries for setting radius and diameter
06:37 PM Lcvette1: no worky without
06:37 PM Lcvette1: well maybe mdi entry but
06:37 PM Lcvette1: mew
06:37 PM Lcvette1: :D
06:37 PM Lcvette1: have a fun trip?
06:41 PM hazzy-m: yes, it was pretty good. Moving my grandparents to assisted living, so a little sad, but very good otherwise
06:41 PM hazzy-m: Ok, I'm gonna try to catch up
06:41 PM hazzy-m: Jcoc's PRs are first priority
06:45 PM TurBoss: great1
08:16 PM hazzy-m: Joco: are you around?
08:25 PM Joco[m]: back
08:25 PM Joco[m]: been out
08:25 PM Joco[m]: taken the day off so was enjoying the fact I don't need to be house bound anymore
08:26 PM Not-944e: [02qtpyvcp] 07KurtJacobson synchronize pull request 03#35: Editor enhance2 - 13https://git.io/JfatA
08:26 PM hazzy-m: Joco: nice!
08:26 PM Joco[m]: yeah. 5 days in a row with zero new cases and no one in hospital
08:27 PM Joco[m]: so people are starting to relax a bit more even though the government is still banging on about being careful and social distancing
08:27 PM Not-944e: [02qtpyvcp] 07KurtJacobson synchronize pull request 03#35: Editor enhance2 - 13https://git.io/JfatA
08:27 PM hazzy-m: that's excellent
08:28 PM Joco[m]: NZ went hard early and it seems to be paying off
08:28 PM Joco[m]: plus as a country people played the game
08:28 PM Joco[m]: we have very very few people being ass holes
08:29 PM Joco[m]: probably the closest I will come to experiencing a near war footing in my lifetime
08:29 PM Joco[m]: as far as curfew like measures
08:32 PM Not-944e: [02qtpyvcp] 07KurtJacobson synchronize pull request 03#35: Editor enhance2 - 13https://git.io/JfatA
08:32 PM hazzy-m: Hopefully!
08:32 PM Joco[m]: well yeah - very much hopefully
08:32 PM hazzy-m: Ok, trying to get this PR cleaned up so I can follow it lol
08:33 PM Joco[m]: I can remember desert storm. Was traveling in the USA when that went down. VERY interesting times
08:33 PM Joco[m]: follow it? it's easy. :-p
08:35 PM Joco[m]: but happy to talk through anything while I'm at home. Need to go out again in a while. Wife has given me a shoping list
08:37 PM hazzy-m: Joco: what is this import for?
08:37 PM hazzy-m: https://github.com/kcjengr/qtpyvcp/blob/e0c5a911a47660db2769fe3645a0dde223a42e82/qtpyvcp/widgets/input_widgets/gcode_editor.py#L44
08:39 PM Joco[m]: in all honesty I did not put it in. It might have been auto added by eclipse-pydev when I inadvertantly had an auto import checkbox on.
08:39 PM Joco[m]: kill it.
08:39 PM Joco[m]: if its new
08:41 PM hazzy-m: ok
08:41 PM Joco[m]: I assume it is new from original file?
08:41 PM hazzy-m: yes, if you look at he file diff you added it
08:42 PM Joco[m]: then kill it
08:42 PM Joco[m]: cose I did not type that in
08:42 PM Joco[m]: that will have come from eclispe trying to be too bloody clever
08:43 PM hazzy-m: I spent about a half hour trying to figure that out
08:43 PM Joco[m]: I'm using liclipse now, but will check for rogue imports in the future.
08:43 PM hazzy-m: since the value returned by lines() is the entire file contents, which might be quite large
08:44 PM Joco[m]: hazzy: really sorry. Wasn't trying to cause probs
08:44 PM hazzy-m: no problem! Just was confusing lol
08:46 PM Joco[m]: <hazzy-m "since the value returned by line"> i thought self.lines() was the count for the total lines in the editor?
08:46 PM Joco[m]: Or were were refering to something else?
08:49 PM hazzy-m: It is, but that import was bringing in the lines() method from this package, which was causing all sorts of problems: https://www.logilab.org/project/logilab-common
08:50 PM Joco[m]: Oh. Never encountered issues when testing. Hmm. But with it killed off it should be fine?
08:52 PM Joco[m]: getting correct checkout on my side so can check shit
08:55 PM Joco[m]: ok - removed that line and loaded a 4k line file just fine
08:55 PM hazzy-m: excellent
08:56 PM Joco[m]: removed lines in edit mode to 999 lines and the line number gutter auto adjusts as expected
08:58 PM Joco[m]: lol - really do like liclipse. It is my go to editor. pycharm is nice but in community addition is a bit limited for working with linuxcnc
09:02 PM Lcvette1: Hurray!
09:03 PM Lcvette1: You guys got the pull request fixed?
09:03 PM Not-944e: [02qtpyvcp] 07joco-nz synchronize pull request 03#35: Editor enhance2 - 13https://git.io/JfatA
09:05 PM Joco[m]: Lcvette: I think hazzy is still in review mode. Just fixed a rogue import thanks to eclipse trying to be too dang helpful.
09:06 PM Lcvette1: Ah
09:07 PM Joco[m]: I can't see any other issues but then will leave to the master to pick through things. Its probably one of the bigger pulls I have done given its hacking up gcode viewer/editor.
09:08 PM Joco[m]: Lcvette: I think you are going to like the new highlight styling I merged in from Don's work off linuxcnc forum from Dec '19
09:09 PM Lcvette1: Nice! I remember the image you posted
09:09 PM Joco[m]: plus the ability to set the gcode editors font fro designer
09:09 PM Lcvette1: Nice! Can't wait!
09:09 PM Joco[m]: I also fixed an issue in the framework that stopped more than one font from being loaded via yaml
09:11 PM Joco[m]: which is finda nice if you want to be able to have different fonts for different purposes and not rely on them being istalled on the distro
09:11 PM Joco[m]: example from a yaml file ...
09:11 PM * Joco[m] sent a long message: < https://matrix.org/_matrix/media/r0/download/matrix.org/WkPwRppfTcwekBXtobZiHtCj >
09:22 PM hazzy-m: Joco: thanks for the import delete
09:22 PM Joco[m]: hazzy: as an FYI, I have some plans for editor-enhance3.
09:23 PM hazzy-m: yes, thinking about how we can prevent breaking changes when doing even more upgrades ...
09:23 PM Joco[m]: will look to further clean up and want to get the color definitions for the sytnax highlighting out into a config file. Probably the yaml config
09:24 PM hazzy-m: since colors are style specific I'm thinking QSS is the best place
09:24 PM Joco[m]: not sure how that would be done. the whole qt style mechanic is a bit black art for me at the moment.
09:26 PM Joco[m]: plus how it will/would play with the QT lexar engine is a big question mark.
09:28 PM * hazzy-m sent a long message: < https://matrix.org/_matrix/media/r0/download/matrix.org/VRapkRHVoILSPjrGOYyKmbbR >
09:28 PM Joco[m]: i.e. i looks like each time a style was changed you would need to build a new lexer object and apply to the editor. Doable I suspect. Will need to extend how colors are held and used by the lexer object. maybe if they are properies that are dynamically set ...
09:28 PM * hazzy-m sent a long message: < https://matrix.org/_matrix/media/r0/download/matrix.org/aAxCJqhLsNubudIBBrQhVryj >
09:29 PM Joco[m]: Well ... can try and learn it and translate to python
09:30 PM Joco[m]: well if I can get that behaving it would be a good. win. ok - thats the target for v3. Off to get food. Will be on phone.
10:25 PM Joco[m]: back
11:01 PM Lcvette1: turboss are you with dev?
11:01 PM Not-944e: [02probe_basic] 07Lcvette pushed 031 commit to 03master [+0/-0/±6] 13https://git.io/Jfo5N
11:01 PM Not-944e: [02probe_basic] 07Lcvette 0343583a4 - fixed some subroutines specific to lathe and signals and slots
11:03 PM Not-944e: [02probe_basic] 07KurtJacobson pushed 031 commit to 03gh-pages [+88/-0/±0] 13https://git.io/Jfo5p
11:03 PM Not-944e: [02probe_basic] 07traviscibot 03a1edc10 - Deploy kcjengr/probe_basic to github.com/kcjengr/probe_basic.git:gh-pages
11:57 PM Joco[m]: Lcvette: hi. with threadmilling of say an M6 thread into mild steel. what kind of step over would you be doing? If you are going to cut out 1.1 as the offset, that is 0.55 on the radius, so presume step over size is going to impact how many passes needed to complete the thread. What I am not sure is what is a reasonable but safe stepover. something in the 0.1 to 0.3 range?
11:57 PM Joco[m]: All numbers are in mm
11:57 PM Lcvette1: single point thread mill?
11:59 PM Lcvette1: Joco: ^^^