#hazzy Logs
May 29 2020
#hazzy Calendar
12:00 AM Joco[m]: yeah single row of teeth and 4 teeth around the edge
12:00 AM Lcvette1: I would do 2
12:01 AM Lcvette1: First at 60% of the pitch radius part
12:01 AM Lcvette1: Then a spring 3rd pass finish
12:02 AM Lcvette1: 60% 40% spring
12:02 AM Lcvette1: Second cut had higher toll pressure as its deeper
12:02 AM Joco[m]: so set step over at 0.33 and passes at 2 with a repeat pass (aka spring pass)
12:02 AM Lcvette1: Yup
12:02 AM Joco[m]: cool
12:03 AM Lcvette1: 0.0005" per tooth
12:03 AM Lcvette1: What's max rpm?
12:03 AM Lcvette1: Currently
12:03 AM Joco[m]: any advice on feeds? My max rpm for any length of time is going to be in the 1800 to 2000 band
12:03 AM Joco[m]: else I get heat issues on the motor
12:08 AM Lcvette1: I like mine to not wobble
12:09 AM Lcvette1: But thread smoothly by hand entirely in
12:09 AM Lcvette1: If that slow you could go 0.001" ipt
12:09 AM Lcvette1: .025 mmpt
12:09 AM Joco[m]: k - about 0.025mm
12:09 AM Joco[m]: snap
12:09 AM Lcvette1: Yup
12:09 AM Lcvette1: Single row is very light cutting
12:09 AM Joco[m]: ok
12:09 AM Lcvette1: If the shooting pass seems like it cutting, then bump it down in feed
12:09 AM Lcvette1: It should just be picking up works of remaining material here and there
12:09 AM Lcvette1: Run one hole, test thread fitment, if it's too tight, bump pitch diameter offset up .025mm and run the same hole again recheck thread fit
12:09 AM Lcvette1: * If the spring pass seems like it cutting, then bump it down in feed
12:09 AM Lcvette1: * If the spring pass seems like its cutting alot, then bump it down in feed for next run
12:10 AM Lcvette1: Joco ^^^
12:10 AM Lcvette1: Also i like to chamfer thread milled holes ahead of thread milling
12:11 AM Joco[m]: ok - thanks. I will be setting up a bit of 12mm mild steel and drilling a bunch of holes to do exactly what you just described
12:11 AM Lcvette1: For a 6mm hole i would go with a 6.5mm chamfer width
12:11 AM Joco[m]: a row of m6 a row of m8 and a row of m8
12:11 AM Joco[m]: m10
12:11 AM Lcvette1: Just need one hole
12:12 AM Lcvette1: Per size
12:12 AM Joco[m]: start "small" and just bump up until fit is on the money?
12:12 AM Lcvette1: Toy cam adjust the call and rerun the same hole
12:13 AM Lcvette1: * Adjust the cam and rerun the same hole
12:13 AM Joco[m]: ok - makes sense.
12:13 AM Joco[m]: so only need 3 holes.
12:13 AM Lcvette1: Start with 1.1mm pdo
12:14 AM Lcvette1: Go up .025mm I'd fit is top right
12:14 AM Lcvette1: But do the same hole
12:14 AM Joco[m]: yup - gotcha
12:14 AM Lcvette1: No need for doing different holes
12:14 AM Lcvette1: Except for different sizes
12:14 AM Joco[m]: yup - eaxctly
12:14 AM Joco[m]: 3 holes covering m6, m8 and m10
12:15 AM Lcvette1: * Go up .025mm If fit is too tight
12:15 AM Lcvette1: Yup
12:15 AM Joco[m]: I want to dail all those receipes in for fit before going at the fixture plate
12:15 AM Lcvette1: Each tool will have something it likes different than the others
12:15 AM Lcvette1: The flat portion or Crest of the tool requires that little extra
12:17 AM Joco[m]: yup - been reading up on that.
12:17 AM Joco[m]: Watched nycnc video on it as well
12:17 AM Joco[m]: k - off to supermarkte
12:17 AM Joco[m]: my job to sort dinner
12:18 AM Lcvette1: Enjoy
01:13 AM Joco[m]: WIN. 7 days straight and no new cases and only 1 active case on record in the country
01:36 AM Mufdvr0978[m]: A lot of the Oz states are starting to clear as well, I am in Tassie, No new for 13 days, hopefully the 10 active get better soon.
01:42 AM Joco[m]: Nice.
01:49 AM Joco[m]: hazzy: hi - anything more you need from me on the two pull requests?
02:28 AM Joco[m]: Lcvette: rechecked the m6 threadmill. It had 4 teeth so if I run at 2000rpm I can get 200mm/min
02:29 AM Joco[m]: Fees rate at 0.025 loading per tooth
02:58 AM Mufdvr0978[m]: @joco Hi, I am trying to understand git, with regards to https://github.com/kcjengr/qtpyvcp/pull/37 am I correct in thinking this has not been committed yet?
02:58 AM Joco[m]: Correct. Hazzy is still working through reviews.
03:01 AM Mufdvr0978[m]: thanks
03:01 AM Mufdvr0978[m]: just making sure I hadn't missed it.
03:02 AM Joco[m]: When the pulls close then they should have been accepted into master.
03:42 AM Joco[m]: Lcvette: for when you return. When modeling holes for thread-milling in Fusion do you model smooth holes that are the exact size of the drill to be be used? I had been threaded holes using the hole functions. But was not getting the radius values in the gcode we had calculated. But when I changed to clean holes of the correct drill size things started to look correct in gcode.
03:43 AM Joco[m]: * Lcvette: for when you return. When modeling holes for thread-milling in Fusion do you model smooth holes that are the exact size of the drill to be be used? I had been modelling threaded holes using the hole functions. But was not getting the radius values in the gcode we had calculated. But when I changed to clean holes of the correct drill size things started to look correct in gcode.
07:42 AM hazzy-m: Morning
07:45 AM JT-Cave: morning
09:37 AM Lcvette1: Joco: yes size the modeled holes for the tap drill
09:37 AM Lcvette1: m6 would be 5mm
12:43 PM TurBoss: Hello
01:12 PM TurBoss: Lcvette: hello o/
01:36 PM TurBoss: I think i found
01:36 PM TurBoss: its upside down
01:40 PM * TurBoss uploaded a video: lathe tool a.webm (409KB) < https://matrix.org/_matrix/media/r0/download/jauriarts.org/DvUrEcqSWGYhXOPxbVMjEown >
02:39 PM TurBoss: https://www.youtube.com/watch?v=7o_V_1AIaXE
03:40 PM JT-Shop: yippie I got that job to automate the 100 year old spoke lathes
03:40 PM TurBoss: great!
03:43 PM Joco[m]: congrats
04:00 PM Joco[m]: question for the QT pythoners: has anyone worked out if you can EXTEND the standard properties supported by QSS? I am trying to see if there is a way to expose the syntax highlighting/coloring options of gcode editor/viewer (qsci) into QSS. I have yet to find any example (in C++ or other) of extendiing QSS.
04:06 PM Joco[m]: To use QSS I need to be able to extend what ever is parsing the QSS file to understand what to do when it encounters new properties like ....
04:07 PM * Joco[m] sent a long message: < https://matrix.org/_matrix/media/r0/download/matrix.org/hZmqiqrnLCfVkHcybCqvtUKb >
04:07 PM Joco[m]: etc etc etc
04:07 PM TurBoss: https://github.com/TurBoss/JauriaCNC/blob/master/tnc/style.qss#L3
04:09 PM TurBoss: you can set properties from qss
04:10 PM Joco[m]: ok - understand those properties which are standard in qsci but what about if I am adding whole new things through a custom lexer for gcode? That is what I am trying to solve.
04:12 PM TurBoss: create a property for them in the widget
04:13 PM Joco[m]: are widget properties accessable/set via QSS?
04:15 PM Joco[m]: I can totally see how to do things if I put the setting of these values into yaml or ini type files. But doing via QSS is a black box for me
04:15 PM TurBoss: i can't try now but some are
04:17 PM Joco[m]: I can not find any example of where someone has a NEW properties (i.e. none standard QT) on a widget that QSS is referencing
04:24 PM Joco[m]: WIN - think I might have found that pattern to use. Which aligns with what you linked to in that qss file TurBoss:
04:24 PM TurBoss: hurray!
04:25 PM Joco[m]: https://stackoverflow.com/questions/36125907/adding-new-stylesheet-parameters-for-custom-qt-widgets
04:25 PM Joco[m]: now the question will be what is a QProperty in python speak where we do not have typed vars
04:29 PM Joco[m]: https://www.riverbankcomputing.com/static/Docs/PyQt5/qt_properties.html
04:29 PM Joco[m]: could be the answer
04:31 PM Joco[m]: oooh ... gonna try this. dang hope it works. Would be so cool to understand how to do tihs stuff.
05:38 PM Joco[m]: WIN. I know know how to hook in custom QSS properties :-D
05:40 PM Joco[m]: I think today I should be able to get a gcode viewer/editor that can have pretty much all the coloring and maybe even the fonts and the number column sizing adjustable from QSS
06:14 PM Lcvette1: Joco: did you thread mill?
06:14 PM Lcvette1: o/
06:14 PM Lcvette1: hello turboss!
06:14 PM Lcvette1: \o/
06:14 PM TurBoss: o/
06:14 PM Lcvette1: :D
06:14 PM Joco[m]: not yet. having breakfast then heading out to the garage
06:14 PM Lcvette1: nice
06:14 PM Lcvette1: ive been busy all day
06:14 PM TurBoss: bf20 for 1100€ is worht no cnc
06:14 PM Joco[m]: good progress on whatever you were working on?
06:15 PM * Lcvette1 uploaded an image: 1590776711497.JPEG (78KB) < https://matrix.org/_matrix/media/r0/download/matrix.org/NyOHJiwmnFgoBQptoGSArKSK >
06:15 PM * Lcvette1 uploaded an image: 1590776722362.JPEG (102KB) < https://matrix.org/_matrix/media/r0/download/matrix.org/vUmokWWITvfMagmhKyWNonrR >
06:15 PM * Lcvette1 uploaded an image: 1590792957221.JPEG (164KB) < https://matrix.org/_matrix/media/r0/download/matrix.org/hikQDEiZFAhvOYOpmflSNtpt >
06:16 PM TurBoss: wow
06:16 PM Lcvette1: TurBoss: you are getting a bf20?
06:16 PM TurBoss: no
06:16 PM TurBoss: just found
06:16 PM Lcvette1: found a bf20?
06:16 PM TurBoss: for 1100€
06:16 PM Lcvette1: not bad
06:16 PM TurBoss: is worth?
06:16 PM Lcvette1: how much in usd?
06:16 PM Joco[m]: sounds new
06:17 PM Joco[m]: price wise
06:17 PM TurBoss: is not cnc
06:17 PM Lcvette1: what is that in usd turboss?
06:17 PM TurBoss: ah
06:17 PM Lcvette1: 1100 = USD
06:17 PM Lcvette1: ?
06:17 PM Lcvette1: a grizzly brand new is 1650.00
06:17 PM TurBoss: 1.221,67
06:18 PM Lcvette1: thats not bad at all
06:18 PM Joco[m]: that's 1900NZD. I paid less than that for my BF20 new
06:18 PM Lcvette1: cheaper then what we can get here in the states
06:18 PM TurBoss: bf 16 800€
06:18 PM TurBoss: 888,48
06:18 PM Lcvette1: i paid $895 new for my G0704 in 2010
06:18 PM Lcvette1: but prices went way up
06:18 PM Lcvette1: BF16 no
06:18 PM TurBoss: ok
06:18 PM Lcvette1: BF20 not too bad
06:19 PM Lcvette1: you gonna get a bf20 turboss?
06:19 PM Lcvette1: :D
06:19 PM TurBoss: not sure
06:19 PM Lcvette1: i would recommend a larger machine
06:19 PM Joco[m]: https://www.machineryhouse.co.nz/M650 <-- got that at one of the sales for $1800
06:19 PM Joco[m]: and they have these sales at least 2 times a year
06:20 PM Joco[m]: thats $1800 including tax
06:20 PM Lcvette1: TurBoss: whats your budget?
06:20 PM TurBoss: none
06:20 PM Joco[m]: so 1100 euro is a new price
06:20 PM Lcvette1: lol
06:20 PM Joco[m]: none - ROFL
06:21 PM TurBoss: ☹︎
06:21 PM Joco[m]: sounds like my budget at the moment
06:22 PM Joco[m]: hmmm som very screwy behaviour going on in gcode editor
06:43 PM Joco[m]: fighting with stupid call order issues.
06:44 PM TurBoss: doesn't work?
06:50 PM Joco[m]: No calls to some methods are happening before the object is fully initialised which is causing issues.
06:51 PM Joco[m]: Is I am getting attempts to reference properties or objects that are not yet in place.
06:51 PM TurBoss: :/
06:53 PM Joco[m]: I am also moving a bunch of functions that are really core or base editor functions back into parent class. So just shit moving around making it complicated. Thank goodness for being able to set break points to check what is happening. Will solve it. Just need to work through the issues.
07:43 PM hazzy-m: Joco: where is your new editor work?
08:05 PM Joco[m]: as what I am doing right now? As of this morning?
08:07 PM Joco[m]: * hazzy: as what I am doing right now? As of this morning?
08:07 PM hazzy-m: yes
08:08 PM Joco[m]: local machine
08:08 PM hazzy-m: k
08:08 PM Joco[m]: at the moment I am getting myself tied into knots trying to keep local branches synched and controlled
08:09 PM Joco[m]: made more a problem cose I am trying to use new capabilities
08:10 PM Joco[m]: I think I am going to yank the editor pull. I want to rehack it to support QSS
08:11 PM Joco[m]: now that I know how to do that
08:11 PM hazzy-m: or you could add commits ...
08:11 PM Joco[m]: ok - lets do it that way. So hold off anymore on that pull. Getting the hal pin one done would be helpful.
08:11 PM hazzy-m: yesh, just need `qproperty-backgroundColor: green;`
08:11 PM Joco[m]: A user is interested in that
08:12 PM Joco[m]: I have found that all @Property can be reference in QSS via qproperty-xxxxx
08:13 PM Joco[m]: but you need getter and setters
08:13 PM * hazzy-m sent a long message: < https://matrix.org/_matrix/media/r0/download/matrix.org/swrrDkKPSbWUuWoQinIoQuFZ >
08:13 PM hazzy-m: It would be good to used typed properties as well, like this
08:13 PM hazzy-m: same for QFont etc.
08:14 PM Joco[m]: yup. for the simple stuff it is easy. It gets a little complex to get control over the actual coloring of the gcode syntax
08:15 PM hazzy-m: get as far as you can, and I'll run with it from there
08:15 PM Joco[m]: I am currently dealing with some very screwy call timing. I am getting calls to setters when not all of the object has finished initalising
08:16 PM hazzy-m: there are some funky things I noticed when reviewing last night
08:18 PM hazzy-m: https://github.com/kcjengr/qtpyvcp/blob/e0c5a911a47660db2769fe3645a0dde223a42e82/qtpyvcp/widgets/input_widgets/gcode_editor.py#L431
08:18 PM hazzy-m: setting a property like that in init can cause unexpected behavior
08:19 PM hazzy-m: instead of setting the property to initialize it, initialize the protected variable that stores the property value
08:20 PM Joco[m]: is that because the property has a setter?
08:20 PM Joco[m]: it might be why I am seeing some screwy shit
08:20 PM Joco[m]: I think something is happening cose python is trying to be "clever".
08:21 PM Joco[m]: I hate "clever" languages. lol
08:21 PM hazzy-m: no, it's because the self._backgroundcolor was never initialized, with will cause errors
08:21 PM Joco[m]: oh - yeah - changing all that at the moment
08:22 PM hazzy-m: its not because of python doing something unexpected
08:22 PM Joco[m]: there is still something screwy going on,. I'm getting a setter called before the inits are finishing
08:23 PM Joco[m]: shrug just need to follow it through
08:23 PM hazzy-m: that should not be hapening, I think the setting is being called in the init by accident
08:23 PM Joco[m]: end of the day will have a better setup and will have styling driven by QSS
08:23 PM hazzy-m: yes, its gonna be sweet!
08:24 PM Joco[m]: <hazzy-m "that should not be hapening, I t"> possibly. Hence why need some quiet time to slowly go through it
08:24 PM hazzy-m: Ok, I'll let you fiddle with it :)
08:24 PM hazzy-m: the PR is an excellent start!!
08:25 PM hazzy-m: at least 90% of the way there
08:25 PM Joco[m]: thought I had it right. poop. Ah well. Still learning lots
08:26 PM Not-944e: [02qtpyvcp] 07KurtJacobson pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/JfKwR
08:27 PM Not-944e: [02qtpyvcp] 07KurtJacobson 035ba5bd0 - BUG: MDIHistory Widget - hasattr expects str
08:28 PM Not-944e: [02qtpyvcp] 07KurtJacobson pushed 031 commit to 03gh-pages [+489/-0/±0] 13https://git.io/JfKwu
08:28 PM Not-944e: [02qtpyvcp] 07traviscibot 03bb554a8 - Deploy kcjengr/qtpyvcp to github.com/kcjengr/qtpyvcp.git:gh-pages
08:39 PM Lcvette1: hazzy: are you gonna be on the dro entry widgets?
08:40 PM Lcvette1: 🤣
08:40 PM TurBoss: Lcvette: what does that need?
08:41 PM hazzy-m: Lcvette: I'm on it now!
08:41 PM hazzy-m: almost done
08:41 PM TurBoss: hurrat!
08:41 PM Lcvette1: \o/
08:41 PM TurBoss: * hurray!
08:41 PM Lcvette1: Hurray!
08:41 PM TurBoss: Glorious victory awaits
08:41 PM Lcvette1: Hello turboss
08:41 PM TurBoss: hello
08:42 PM TurBoss: can we take somethin from the lathe tool stuff?
08:42 PM Lcvette1: \o/
08:42 PM Lcvette1: Whatcha thinking?
08:42 PM TurBoss: couldbe upside down?
08:42 PM Lcvette1: It's upside down still?
08:43 PM Lcvette1: You had it working right
08:43 PM TurBoss: :/
08:43 PM TurBoss: yes but messed
08:43 PM TurBoss: need some final tweaks
08:43 PM TurBoss: need your jelp
08:43 PM Lcvette1: Ok
08:44 PM Lcvette1: Now can i help.
08:44 PM Lcvette1: :D
08:44 PM TurBoss: great
08:46 PM * TurBoss uploaded an image: Captura de pantalla de 2020-05-29 20-02-14.png (60KB) < https://matrix.org/_matrix/media/r0/download/jauriarts.org/ailSoJJtNbaxzQCqxPKASnak >
08:47 PM Lcvette1: Whatcha need?
08:47 PM TurBoss: having 0 offsets to not mess much
08:48 PM TurBoss: so whats the error with on the latest
08:49 PM Lcvette1: Upside down
08:49 PM TurBoss: i dont know where should each tool draw
08:49 PM TurBoss: ok
08:49 PM TurBoss: I can do 2 things
08:49 PM Lcvette1: Wrong quadrant
08:49 PM TurBoss: mirror the images upside down
08:49 PM TurBoss: or look for the positive negative
08:49 PM Lcvette1: What about the rule
08:50 PM TurBoss: for the 90 90?
08:50 PM Lcvette1: No bo
08:50 PM Lcvette1: * No no
08:50 PM Lcvette1: For the correct drawing
08:50 PM TurBoss: should be wrong
08:50 PM TurBoss: there is one
08:51 PM Lcvette1: 0-90 91-180 etc
08:51 PM * TurBoss sent a long message: < https://matrix.org/_matrix/media/r0/download/matrix.org/HVwDVhNnRoXqGEGJpkrKZmwR >
08:51 PM TurBoss: fixed 1
08:51 PM * TurBoss sent a long message: < https://matrix.org/_matrix/media/r0/download/matrix.org/EeNEEselOzYrlNgdSTGglxgX >
08:51 PM Lcvette1: That's correct
08:52 PM Lcvette1: Does or draw correctly now with that rule in place. It should
08:52 PM TurBoss: id draws upside down
08:53 PM Not-944e: [02qtpyvcp] 07TurBoss pushed 031 commit to 03VTK_Lather [+0/-0/±1] 13https://git.io/JfKrl
08:53 PM Not-944e: [02qtpyvcp] 07TurBoss 03aab22c7 - fix ranges
08:53 PM TurBoss: pushing
08:53 PM TurBoss: can you test this please?
08:54 PM Lcvette1: yup
08:57 PM * Lcvette1 uploaded an image: Screenshot_2020-05-29_21-48-05.png (29KB) < https://matrix.org/_matrix/media/r0/download/matrix.org/aCogyJsbpcsDjFdWaRougufq >
08:57 PM TurBoss: :/
08:58 PM Lcvette1: tool 1, 2, 4 showed correctly but tool 3 did not
08:58 PM TurBoss: what angles do have
08:58 PM TurBoss: * what angles does have
08:58 PM Lcvette1: sek need to double check it
09:05 PM Lcvette1: something is broken on offsets
09:05 PM Lcvette1: can't make zero
09:05 PM Lcvette1: the tool angle was wrong
09:05 PM Lcvette1: i fixed
09:06 PM Lcvette1: but it is not showing corretly because of the offset i think
09:06 PM TurBoss: ok can you restart pb?
09:06 PM TurBoss: i think I know what the offsets issue is
09:06 PM TurBoss: but not the fix right now
09:08 PM Lcvette1: ok
09:08 PM Lcvette1: yes i restarted
09:08 PM Lcvette1: the tool display for tool 3 is still wrong
09:08 PM Lcvette1: it has a different fron and back angle than tool 4 but shows the same
09:08 PM Lcvette1: has a front angle of 95 back angle of 175
09:09 PM Lcvette1: so should be negative negative
09:09 PM Lcvette1: x and z both negative in the quadrant but its not drawing that way
09:09 PM * TurBoss sent a long message: < https://matrix.org/_matrix/media/r0/download/matrix.org/ilvRjeiYzgVJlGoFnWigmvgO >
09:10 PM Lcvette1: maybe the operrand error thing is the issue?
09:10 PM Lcvette1: not doing the multiplication?
09:10 PM TurBoss: i just multiply
09:11 PM Lcvette1: becaue it errors out"
09:11 PM TurBoss: 1 -1
09:11 PM * Lcvette1 uploaded an image: Screenshot_2020-05-29_21-48-05.png (29KB) < https://matrix.org/_matrix/media/r0/download/matrix.org/kMOjTKagOSjGkbNknSIEsOcl >
09:11 PM * TurBoss sent a long message: < https://matrix.org/_matrix/media/r0/download/matrix.org/SvjXOynTDvrZGdyDekkXbHYS >
09:11 PM Lcvette1: oh
09:11 PM TurBoss: for some reason its doesnt fit on any if instance
09:12 PM Lcvette1: but i think the cos and sin functions give - or + results depending ont he angle
09:12 PM TurBoss: yup
09:12 PM TurBoss: maybe they are wrong
09:12 PM TurBoss: cos
09:12 PM TurBoss: sin
09:12 PM Lcvette1: so maybe we need to make them absolute then use the multiplier so it is ALWAYS multiplying agains a positive number
09:13 PM Lcvette1: can you make the answer absolute?
09:13 PM Lcvette1: from the cos sin result before multiplying by 1 or -1
09:13 PM Lcvette1: i think that will fix
09:13 PM Lcvette1: turboss^^
09:14 PM * TurBoss sent a long message: < https://matrix.org/_matrix/media/r0/download/matrix.org/iYRJqxsQRhoRDOCmAZVcDPXC >
09:14 PM TurBoss: ok
09:15 PM Lcvette1: C * cos(A) = (answer must be absolute)
09:15 PM Lcvette1: before multiplying * x_pol
09:15 PM * TurBoss sent a long message: < https://matrix.org/_matrix/media/r0/download/matrix.org/SUDqVNdoHahlqUGiRyFlvfem >
09:15 PM Lcvette1: otherwise if the angle creates a negative answer we and making a positive by multiplying by -1
09:15 PM Lcvette1: yes!!!
09:16 PM Lcvette1: i think that is going to work perfect
09:16 PM TurBoss: testing
09:16 PM Lcvette1: :o
09:18 PM TurBoss: now tool 5 fails
09:18 PM TurBoss: I'll push
09:18 PM Not-944e: [02qtpyvcp] 07TurBoss pushed 031 commit to 03VTK_Lather [+0/-0/±1] 13https://git.io/JfKr5
09:18 PM Not-944e: [02qtpyvcp] 07TurBoss 03c37219c - make absolutes
09:19 PM Lcvette1: testing
09:20 PM Lcvette1: too many parethesis
09:20 PM Lcvette1: no no
09:20 PM Lcvette1: i see
09:21 PM Lcvette1: does x_pol need to be in parenthesis on its own?
09:21 PM TurBoss: no
09:21 PM TurBoss: it the order
09:21 PM TurBoss: parentesis first
09:21 PM TurBoss: then multiplication
09:22 PM Lcvette1: p1_x = (abs(C * sin(A))) * (x_pol)
09:22 PM TurBoss: x_pol may become None if angle not betwen 0-360
09:23 PM Lcvette1: i tinkn it is becoming this
09:23 PM TurBoss: maybe the 91
09:23 PM Lcvette1: p1_x = (abs(C * sin(A))) * -1
09:23 PM TurBoss: the range
09:23 PM Lcvette1: maybe the * -
09:23 PM Lcvette1: cannot be next to each other without parenthesis\
09:23 PM TurBoss: ok
09:24 PM Lcvette1: :o
09:24 PM TurBoss: same error
09:24 PM Lcvette1: you did for all of them?
09:24 PM * TurBoss uploaded an image: Captura de pantalla de 2020-05-30 04-15-39.png (16KB) < https://matrix.org/_matrix/media/r0/download/jauriarts.org/bWvWnGvglcReENEgVUmdpRSx >
09:25 PM TurBoss: tried
09:25 PM * Lcvette1 sent a long message: < https://matrix.org/_matrix/media/r0/download/matrix.org/vNNgBJIndgqBQMyvAUnTopXw >
09:25 PM TurBoss: remember x - is up
09:25 PM TurBoss: x+ down
09:27 PM * Lcvette1 sent a long message: < https://matrix.org/_matrix/media/r0/download/matrix.org/KdeTPMQPHjMQDrNLEQAbhPsw >
09:27 PM Lcvette1: one was missing a parenthesis
09:27 PM Lcvette1: TurBoss: TurBoss ^^^^
09:27 PM Lcvette1: copy that and see if it works
09:28 PM * TurBoss sent a long message: < https://matrix.org/_matrix/media/r0/download/matrix.org/XWpAxHyDptwynmOYrEtxhIPU >
09:29 PM Lcvette1: yes?
09:29 PM TurBoss: it doesn't throw the error but doesn't draw
09:30 PM Lcvette1: 0 90 180 270 360
09:30 PM Lcvette1: they become 0
09:30 PM Lcvette1: i think
09:30 PM TurBoss: the rule currently looks for degrees
09:31 PM TurBoss: could it look for Q
09:31 PM TurBoss: ?
09:31 PM Lcvette1: cos(90) =0
09:31 PM * TurBoss sent a long message: < https://matrix.org/_matrix/media/r0/download/matrix.org/QWlwKBifveBZfYgHODwNzwWl >
09:31 PM TurBoss: can I do this way=?
09:32 PM Lcvette1: yes
09:32 PM Lcvette1: no
09:32 PM TurBoss: the what should the the big if else look
09:32 PM Lcvette1: i don't know
09:32 PM TurBoss: tool.orientation is Q
09:32 PM Lcvette1: i don't know if that will be easier
09:33 PM TurBoss: if Q then
09:33 PM Lcvette1: its the same thing
09:33 PM TurBoss: les code
09:33 PM Lcvette1: you are still going to be multiplying by 1 or 0
09:33 PM Lcvette1: * you are still going to be multiplying by 1 or -1
09:33 PM TurBoss: ok
09:33 PM Lcvette1: i think our issue is that 0 90 180 270 360 give wierd results for sin and cos
09:34 PM TurBoss: ok
09:34 PM TurBoss: I'll try one thing
09:34 PM Lcvette1: maybe need to do
09:34 PM TurBoss: add some logs
09:35 PM Lcvette1: 1-89 91-179 181-269 271-359
09:35 PM Lcvette1: then do a different rule for 0, 90, 180, 270
09:35 PM Lcvette1: smolke break
09:36 PM TurBoss: ok
09:38 PM * TurBoss sent a long message: < https://matrix.org/_matrix/media/r0/download/matrix.org/ejTLrBHaEiyGFobzkiwTqhCD >
09:38 PM TurBoss: this tool doesn't show
09:38 PM TurBoss: tool 5
09:38 PM Not-944e: [02qtpyvcp] 07TurBoss pushed 031 commit to 03VTK_Lather [+0/-0/±1] 13https://git.io/JfKoI
09:38 PM Not-944e: [02qtpyvcp] 07TurBoss 03cd453d1 - add logs
09:42 PM Lcvette1: TurBoss: the raw answer for 62.5 are both positive
09:42 PM TurBoss: not negative like the logs?
09:42 PM Lcvette1: no
09:43 PM Lcvette1: sin62.5 * .35 = 0.31045379161
09:43 PM * TurBoss sent a long message: < https://matrix.org/_matrix/media/r0/download/matrix.org/pnwwfsuHPOVanxepqQxrsuFc >
09:44 PM TurBoss: range are wrong?
09:45 PM Lcvette1: cos62.5 * .35 = 0.16161201463
09:45 PM Lcvette1: sin62.5 * .35 = 0.31045379161
09:45 PM TurBoss: [qtpyvcp.widgets.display_widgets.vtk_backplot.vtk_backplot][DEBUG] BackAngle 62.5 Point P2 X = -0.310453791612 P2 Z = -0.161612014632 (vtk_backplot.py:1459)
09:46 PM Lcvette1: so its getting multiplied both x and z by -1
09:46 PM Lcvette1: but only x should be negative
09:47 PM Lcvette1: z should be positive
09:48 PM TurBoss: the log results are after the multiplication
09:48 PM * Lcvette1 sent a long message: < https://matrix.org/_matrix/media/r0/download/matrix.org/JvbWUHRtoAaDmiOIOXttsbaA >
09:48 PM Lcvette1: did you do this?
09:49 PM TurBoss: yes
09:49 PM Lcvette1: does it accept decimals?
09:49 PM Lcvette1: 62.5
09:50 PM TurBoss: yes
09:51 PM TurBoss: I'm idiot
09:51 PM Lcvette1: so we need to understand why we ar egetting 2 negative results when it should be a negative and a positive
09:51 PM Lcvette1: 62.5 should be x_pol = -1
09:51 PM Lcvette1: z_pol = 1
09:52 PM Lcvette1: so something may be broken somewhere in the equation?
09:52 PM TurBoss: so it only has o change the sign in some cases?
09:53 PM Lcvette1: it should change everything to absolute so we can control the signs correctly
09:55 PM TurBoss: did this way
09:55 PM * TurBoss sent a long message: < https://matrix.org/_matrix/media/r0/download/matrix.org/dzPYaHHXoNbjSfOHqoxRKNGH >
09:55 PM * TurBoss sent a long message: < https://matrix.org/_matrix/media/r0/download/matrix.org/MFIrpocuRfEgRjZIPvmAIsgJ >
09:55 PM Lcvette1: works?
09:55 PM TurBoss: its te same
09:55 PM TurBoss: but operation in 2 lines
09:58 PM TurBoss: i noticed that I had a mirror on Z axis
09:58 PM TurBoss: disabled
09:58 PM TurBoss: that was messing with the mat
09:58 PM TurBoss: 👿
09:58 PM * Lcvette1 sent a long message: < https://matrix.org/_matrix/media/r0/download/matrix.org/WUlGGvimfHduFrgcInktfMVn >
09:58 PM TurBoss: ok
09:58 PM Lcvette1: fixed?
09:58 PM TurBoss: I'll skip thoose
09:59 PM TurBoss: I think I figured
10:00 PM TurBoss: I'm conparing the Q fixed angle value
10:00 PM TurBoss: not the fron back angle
10:00 PM TurBoss: thats
10:00 PM TurBoss: I'll change and report
10:02 PM * Lcvette1 sent a long message: < https://matrix.org/_matrix/media/r0/download/matrix.org/kwUJlAOFHfcAtCpemQJCyKil >
10:03 PM * Lcvette1 sent a long message: < https://matrix.org/_matrix/media/r0/download/matrix.org/uVcgmXOPUlzVBskYFwXFoGuR >
10:03 PM * Lcvette1 sent a long message: < https://matrix.org/_matrix/media/r0/download/matrix.org/AtIrKzfxXfGmSMUlJytyPCpA >
10:05 PM * TurBoss sent a long message: < https://matrix.org/_matrix/media/r0/download/matrix.org/njHDHrLmmkEuuxxKUkoAQCZp >
10:05 PM TurBoss: so if tool front angle is 90=?
10:06 PM Lcvette1: z is 0
10:06 PM TurBoss: ok
10:06 PM TurBoss: how 0
10:06 PM TurBoss: positive or negative
10:06 PM Lcvette1: all the way 0
10:06 PM Lcvette1: lol
10:06 PM Lcvette1: 0 is neither positive or negative
10:07 PM Lcvette1: its the vertical line on the cross hair
10:07 PM TurBoss: ok
10:07 PM TurBoss: so it doesn' change sign
10:07 PM Lcvette1: | z sero
10:07 PM Lcvette1: __ x zero
10:07 PM Lcvette1: right on the line
10:08 PM TurBoss: ok
10:10 PM Lcvette1: if front angle is 0, the z would be zero
10:11 PM * Lcvette1 sent a long message: < https://matrix.org/_matrix/media/r0/download/matrix.org/DYHDHgmmnjAddnoDMIVlJjtq >
10:11 PM Lcvette1: same for back angle
10:12 PM TurBoss: if fron angle is 0 what for X ?
10:12 PM Lcvette1: .35
10:13 PM Joco[m]: Lcvette: what would this line do: G43 Z15. H1
10:13 PM Lcvette1: whenever one is zero the other will always be 0.35
10:13 PM Joco[m]: I didn't think G43 allows an axis value
10:13 PM Lcvette1: G43 is tool offset H1 is tool 1
10:14 PM Joco[m]: yeah know that. But why is the Z15. on that line?
10:14 PM Lcvette1: Z15. is an axis position
10:14 PM Joco[m]: so its mixing axis poition an tool offset on the same line?
10:14 PM Lcvette1: it would be a move to Z15 with tool offset for tool 1 active
10:15 PM Lcvette1: in the cirrent work offset
10:15 PM Joco[m]: isn't g43 modal?
10:15 PM Lcvette1: with the current feed value ie g1, g0
10:15 PM Joco[m]: i.e on until turned off?
10:15 PM Lcvette1: it is likely the first move since changing the tool
10:16 PM Lcvette1: what the preceeding code
10:16 PM Lcvette1: lets see the whole picture
10:16 PM * Joco[m] sent a long message: < https://matrix.org/_matrix/media/r0/download/matrix.org/kDJWkbABLbccrPPmjzpqyaIV >
10:16 PM Lcvette1: yeah so it is the first move after a tool change
10:17 PM Joco[m]: k
10:17 PM * Lcvette1 sent a long message: < https://matrix.org/_matrix/media/r0/download/matrix.org/OLnhgrWovJpwDYrPpZBtKBrH >
10:17 PM Lcvette1: same in all my code
10:17 PM Joco[m]: I think it's f'ing up my G43.1
10:17 PM Lcvette1: what G43.1?
10:17 PM Joco[m]: Dynamic TLO
10:17 PM Lcvette1: for what?
10:18 PM Joco[m]: after manual tool change and tool length measure
10:18 PM Lcvette1: not sure i follow your use of G43.1
10:19 PM Joco[m]: its special to my machines setp and that I auto measure tools after changing. rmember no fixed/measured tool holding
10:20 PM Joco[m]: will do a manual check but I'm pretty sure that is what is borking stuff
10:20 PM Lcvette1: but why use a G43.1?
10:20 PM Lcvette1: just do auto tool measdure and it will update the current tools length
10:20 PM Lcvette1: and set it active
10:21 PM Lcvette1: * just do auto tool measure and it will update the current tools length
10:21 PM Not-944e: [02qtpyvcp] 07KurtJacobson pushed 031 commit to 03DROWidgets [+5/-0/±2] 13https://git.io/JfKop
10:21 PM Not-944e: [02qtpyvcp] 07KurtJacobson 03c82db44 - add new DROLabel and DROLineEdit widgets
10:21 PM Joco[m]: how?
10:21 PM Not-944e: [02qtpyvcp] 07KurtJacobson created branch 03DROWidgets - 13https://git.io/fhCou
10:21 PM Joco[m]: what is "auto tool measure"?
10:22 PM travis-ci: kcjengr/qtpyvcp#1541 (DROWidgets - c82db44 : Kurt Jacobson): The build passed.
10:22 PM travis-ci: Diff view : https://github.com/kcjengr/qtpyvcp/commit/c82db4452542
10:22 PM travis-ci: Build details : https://travis-ci.org/kcjengr/qtpyvcp/builds/692795672
10:23 PM hazzy-m: Joco: you can set the tool table offset from gcode
10:23 PM hazzy-m: that might be better than using a G43
10:23 PM hazzy-m: * that might be better than using a G43.1
10:24 PM Joco[m]: ok - so the macro does the measurement and instead of doing G43.1 it actually writes the measurement to tool table?
10:24 PM Lcvette1: #5063 is a probed z coordinate
10:24 PM Lcvette1: yes
10:24 PM Joco[m]: ok - will look into thta.
10:24 PM Lcvette1: probe basic has a tool touch off routine
10:24 PM Joco[m]: especially if it saves me having to hack the post processor
10:25 PM Joco[m]: what I have measures everything ok
10:25 PM Lcvette1: tool_touch_off.ngc in the subroutines folder
10:25 PM Joco[m]: it's just coming unstuck due to the fusion gcode doing these g43's
10:25 PM Lcvette1: but it measures everything in rlation to the spindle gaige line
10:26 PM Joco[m]: i have no reliable way to measure the "spindle guage line"
10:27 PM Lcvette1: i know
10:27 PM Joco[m]: I can reliably measure with reference to a starting tool that has been manually touched off
10:27 PM Lcvette1: you should be touching off on top of the part i assume?
10:27 PM Lcvette1: with a fixed height touch plate?
10:28 PM Joco[m]: gauge pin
10:28 PM Lcvette1: ?
10:28 PM Lcvette1: are you doing this automatically?
10:28 PM Lcvette1: ie with a wired probe plate?
10:28 PM Joco[m]: no - touch on first tool is old school.
10:28 PM Lcvette1: im lost
10:29 PM Lcvette1: you have no touch plate?
10:29 PM Lcvette1: rolling a gauge pin under the tool
10:30 PM Joco[m]: guage pin of know size. Tool broough down to say 8mm from stock top. then slowly raised until guage pin just rolls under it. Then ofset set at guauge pin diam
10:30 PM Joco[m]: nominally 10mm
10:30 PM Lcvette1: so yes
10:30 PM Joco[m]: at htat point z=10mm
10:31 PM Lcvette1: so you just need to set the tables offset to 10mm
10:32 PM Lcvette1: G10 L1 P #5400 Z [#<new_tool_length_offset>]
10:32 PM Joco[m]: and everything else is relative to that?
10:32 PM Joco[m]: that is how G43.1 works
10:33 PM Lcvette1: this sets the current tool number #5400 parameter to Z8
10:34 PM Lcvette1: just make an mdi button and a box to type in your gauge pin height
10:34 PM Lcvette1: or put it in the button code
10:34 PM Lcvette1: G10 L1 P#5400 Z8
10:34 PM Lcvette1: if you use the same pin everytime that will always set the offset to 8mm
10:35 PM Lcvette1: should change the dro also
10:36 PM Joco[m]: ok - have a manual touch off section for all that. Just doesn't save anything to tool table.
10:36 PM Joco[m]: it just sets g54
10:38 PM Joco[m]: Lcvette: thanks. Know what to look into now so will work it through.
10:39 PM Lcvette1: if your offsets change everytime, then this is really all you need though right?
10:40 PM Lcvette1: if you want to set the tool table it would be:
10:40 PM Joco[m]: yup - saving to tool table or using g43.1 all does the same thing. It just comes down to what will play nice with what fusion generates
10:43 PM Lcvette1: http://linuxcnc.org/docs/2.8/html/gcode/g-code.html#gcode:g10-l1
10:43 PM Lcvette1: G10 L1 P#5400 Z8
10:43 PM Lcvette1: this should be setting the tool table
10:43 PM Lcvette1: if the tool is in the tool table
10:43 PM Lcvette1: and loaded in the spindle
10:44 PM Lcvette1: joco ^^^
10:45 PM Lcvette1: i just tested and it changes the tool table
10:45 PM Lcvette1: so this would work with fusion
10:46 PM Lcvette1: as fusion is calling G43 H(tool#) from the tool table
10:46 PM Lcvette1: but the tool must be loaded in the spindle in the ui
10:47 PM Joco[m]: going to do some tests. Assume the tool length is all relative to the current perceived Z0 for g43?
10:47 PM Joco[m]: nah - ignore that. I'll just go and check stuff and learn
10:48 PM * Lcvette1 posted a file: change_tool_offset.mkv (1544KB) < https://matrix.org/_matrix/media/r0/download/matrix.org/XttgVXRTYjSsbumPBmxYlYNr >
10:49 PM Lcvette1: joco ^^^
10:49 PM Lcvette1: everything is relative to the work offset of the part
10:49 PM Lcvette1: how are you setting the work offset?
10:50 PM Joco[m]: G10L20P0Z#<manualZoffset>
10:50 PM Joco[m]: on an mdi button
10:50 PM Lcvette1: yes but physically
10:51 PM Joco[m]: z as dezsrcibed before. x/y using a wobbly style edge finder
10:53 PM Lcvette1: i think maybe just having a zero offset in the tool table and setting the current tool to the zero work height may be a safer solution
10:53 PM Joco[m]: which is essentially what I have I think
10:54 PM Joco[m]: at the moment.
10:54 PM Lcvette1: but if you plan on using G43.1 you will need to go into the post processor i belive to rework it
10:54 PM Lcvette1: you need some repeatable holders
10:54 PM Lcvette1: lol
10:55 PM Lcvette1: makes life sooo much easier
10:55 PM Lcvette1: and a touch probe
10:55 PM Joco[m]: guess I'm hacking the post process.
10:55 PM Joco[m]: cose those are months away
10:55 PM Lcvette1: i don't think you need G43.1
10:55 PM Lcvette1: i would write a small macro
10:57 PM Lcvette1: there are alot of issues you will face with setting tools manually thought especially if using the work piece top
10:58 PM Lcvette1: ie once the surface is gone, you will lose your refeence siurface
10:58 PM Lcvette1: you could overcome this by creating lots of different setups in fusion for each height i suppose
10:59 PM Lcvette1: but man thats alot to keep track of
10:59 PM Joco[m]: I tend to use the fixed vice jaw as a reference top.
11:00 PM Lcvette1: but that means you have to know the distance from the work to the vise jaw everytime
11:00 PM Joco[m]: It's not ideal but workable.
11:00 PM Lcvette1: so two measurements
11:00 PM Lcvette1: get some chinese TTS holders
11:01 PM Not-944e: [02qtpyvcp] 07TurBoss pushed 031 commit to 03VTK_Lather [+0/-0/±1] 13https://git.io/JfKKD
11:01 PM Not-944e: [02qtpyvcp] 07TurBoss 03500ce6a - take the front / back angle
11:01 PM Lcvette1: get them direct, i have tons of them usually get a bunch for $9/pc
11:02 PM Lcvette1: they will make your life soooo much easier
11:02 PM Lcvette1: and make machining much funner and less tedious
11:02 PM Lcvette1: set all your tools up and measure them store the offsets
11:02 PM Lcvette1: then literally probe the location you setup in fusion and hit cycle start
11:03 PM Lcvette1: turboss needs testing?
11:03 PM TurBoss: no.. is unfinished
11:03 PM TurBoss: duno how to apply the values when 0 90 etc
11:04 PM Lcvette1: if else rules
11:04 PM TurBoss: they are there
11:04 PM TurBoss: i added
11:04 PM Lcvette1: what file
11:05 PM TurBoss: qtpyvcp/widgets/display_widgets/vtk_backplot/vtk_backplot.py
11:06 PM TurBoss: line 1430
11:06 PM Lcvette1: you nhave pass
11:06 PM TurBoss: replace pass with the correct code lol
11:06 PM TurBoss: :P
11:07 PM * Lcvette1 sent a long message: < https://matrix.org/_matrix/media/r0/download/matrix.org/GpOZczihvmMFjBWlhckYHFsu >
11:08 PM Lcvette1: if you make the multiplier a 0 for the correct one it should work
11:10 PM * TurBoss sent a long message: < https://matrix.org/_matrix/media/r0/download/matrix.org/wyTUSqwWoGVPQtroYtpLJlXW >
11:10 PM TurBoss: what I should do with the z polatiry
11:11 PM Lcvette1: 0 = positive
11:11 PM Lcvette1: 90 = negative
11:11 PM Lcvette1: 180 = negative
11:12 PM Lcvette1: 270 = positive
11:12 PM Lcvette1: turboss^^^
11:12 PM TurBoss: what for 360?
11:12 PM TurBoss: nothing?
11:12 PM Lcvette1: positive
11:12 PM Lcvette1: its same as 0
11:12 PM Lcvette1: lol
11:13 PM TurBoss: ```python
11:13 PM TurBoss: v
11:13 PM * TurBoss sent a long message: < https://matrix.org/_matrix/media/r0/download/matrix.org/lCbyrQTXPkXryxSmXvJOBrLW >
11:13 PM TurBoss: please chech this
11:13 PM TurBoss: * please chec kthis
11:13 PM Lcvette1: yes i think so
11:13 PM TurBoss: * please check this
11:14 PM TurBoss: ok now for back angle
11:14 PM Lcvette1: same
11:14 PM TurBoss: its the same?
11:14 PM Lcvette1: yes
11:15 PM Lcvette1: so if you make a tool with front angle 90 and back angle 0, it should draw a perfectly aligned triangle to x zn z in the bottom right quadrant
11:17 PM Lcvette1: * so if you make a tool with front angle 90 and back angle 0, it should draw a perfectly aligned triangle to x and z in the bottom right quadrant
11:17 PM Lcvette1: works?
11:24 PM TurBoss: it doesn't compare decimals in the if else statement
11:25 PM Lcvette1: compare?
11:25 PM TurBoss: how many decimal points are allowed
11:25 PM TurBoss: 62.5 is not in range (60 - 70)
11:25 PM Lcvette1: how many are required?
11:25 PM TurBoss: range fgoes 1 by one
11:25 PM TurBoss: 3?
11:25 PM TurBoss: in the angle
11:26 PM Lcvette1: can you make range from 60.000 - 70.000
11:26 PM Lcvette1: ?
11:26 PM TurBoss: yes
11:26 PM Lcvette1: ok
11:26 PM TurBoss: thats 3 decimal
11:26 PM Lcvette1: hurray!
11:26 PM Lcvette1: i asked about the decimals earlier
11:26 PM Lcvette1: lol
11:26 PM Lcvette1: :D
11:27 PM TurBoss: yes
11:27 PM TurBoss: i know
11:27 PM Lcvette1: i use dpanda fu
11:27 PM Lcvette1: * i use panda fu
11:27 PM TurBoss: ```python
11:27 PM TurBoss: elif tool.frontangle in seq(1, 89, 0.001):
11:28 PM Lcvette1: :o
11:28 PM Lcvette1: thats how you tell it to count by .001 increments?
11:29 PM TurBoss: ```python
11:29 PM TurBoss: elif tool.frontangle in seq(0.001, 89.999, 0.001):
11:29 PM TurBoss: should look like this
11:29 PM TurBoss: ok
11:52 PM Lcvette1: works?
11:56 PM TurBoss: nope yet...
11:57 PM Lcvette1: whats broken in it?
11:58 PM Lcvette1: maybe i can help
11:58 PM Lcvette1: :D
11:59 PM TurBoss: Im searching if a float in in the range