#hazzy Logs
Jun 12 2020
#hazzy Calendar
01:56 AM Joco[m]1: well that is a step in the right dorection. Able to get a skeleton plugin registered and the initalise method is triggered
01:56 AM Joco[m]1: * well that is a step in the right direction. Able to get a skeleton plugin registered and the initalise method is triggered
02:20 AM Joco[m]1: well that was easy
03:19 AM Not-944e: [02qtpyvcp] 07joco-nz opened pull request 03#39: Plugin to export specifc HAL pins and associated linuxcnc action. - 13https://git.io/JfHqy
03:22 AM Not-944e: [02qtpyvcp] 07joco-nz edited pull request 03#39: Plugin to export specifc HAL pins and associated linuxcnc action. - 13https://git.io/JfHqy
03:28 AM Joco[m]1: hazzy: did the HAL stuff via a plugin. Nice and contained and for an initial release very simple. I think there is potential to get more clever later. But I don't see a lot of value in delaying some simple to do and useful things while waiting for a "grand design".
04:59 AM JT-Cave: morning
05:00 AM Joco[m]1: hi JT
06:01 AM hazzy-m1: Joco: fantastic!
06:07 AM Not-944e: [02qtpyvcp] 07KurtJacobson closed pull request 03#39: Plugin to export specifc HAL pins and associated linuxcnc action. - 13https://git.io/JfHqy
06:07 AM Not-944e: [02qtpyvcp] 07KurtJacobson pushed 032 commits to 03master [+2/-0/±2] 13https://git.io/JfHGK
06:07 AM Not-944e: [02qtpyvcp] 07James 03d349d9f - Plugin to export specifc HAL pins and associated linuxcnc action.
06:07 AM Not-944e: [02qtpyvcp] 07KurtJacobson 03cc5733e - Merge pull request #39 from joco-nz/exported-hal-plugin
06:07 AM Not-944e: [02qtpyvcp] 07KurtJacobson commented on pull request 03#39: Plugin to export specifc HAL pins and associated linuxcnc action. - 13https://git.io/JfHGi
06:08 AM Not-944e: [02qtpyvcp] 07KurtJacobson pushed 031 commit to 03gh-pages [+489/-0/±0] 13https://git.io/JfHG1
06:08 AM Not-944e: [02qtpyvcp] 07traviscibot 03e281c84 - Deploy kcjengr/qtpyvcp to github.com/kcjengr/qtpyvcp.git:gh-pages
06:13 AM Not-944e: [02probe_basic] 07joco-nz commented on issue 03#13: feed rate override reset - 13https://git.io/JfHGQ
06:23 AM Not-944e: [02probe_basic] 07lmclaren7000 commented on issue 03#13: feed rate override reset - 13https://git.io/JfHZI
10:24 AM Lcvette: is there a seperate post for linuxcnc turning in fusion360?
10:24 AM Lcvette: im trying to run the first part in full cnc and i am not having any luck getting it to post
10:31 AM Lcvette: figured it out
10:32 AM Lcvette: needed a new post
12:34 PM hazzy-m1: Sweet
12:35 PM * Lcvette uploaded an image: ADAD7419-6A8B-4512-A77A-3598BBE38E07.jpg (469KB) < https://matrix.org/_matrix/media/r0/download/matrix.org/voHiSYYCsXIyRsgHMAGmUjiK >
12:36 PM Lcvette: first customer just installed the power upgrade kit
01:06 PM Lcvette: turboss are you here?
01:07 PM * Lcvette sent a long message: < https://matrix.org/_matrix/media/r0/download/matrix.org/qzCHhGhMRwSUQCpVAbeGiSeY >
01:07 PM Lcvette: getting this error when trying to load the lathe gui
01:10 PM Lcvette: looks like i am missing the xz view slot in designer
01:11 PM Lcvette: loads if i set it to z view or another listed slot
01:12 PM Lcvette: not sure how to resolve
01:12 PM Lcvette: halp!
01:12 PM Lcvette: /o\]
01:12 PM Lcvette: * /o\
03:05 PM Joco[m]1: Setviewxz - is that supposed to be a perspective view? I dont recall that one.
04:16 PM Lcvette: no flat lathge view
04:16 PM Lcvette: * no flat lathe view
04:16 PM Lcvette: * no, flat lathe view
04:16 PM Lcvette: in the correct orientation
04:18 PM Joco[m]1: Oh. Is that like Z1 and Z2?
04:19 PM Joco[m]1: Oops - lathe specific?
04:26 PM Lcvette: no there used to be a slot for that specific view
04:26 PM Lcvette: may have been lost in the merge
04:26 PM Lcvette: ?
04:27 PM Lcvette: or maybe when turboss was doing the tool vtk stuff it got lost
04:27 PM Lcvette: i dunno
04:27 PM Lcvette: but it is sorely needed since lathe starts up in 3d mode
04:27 PM Lcvette: can never quite get the view flat without it
04:38 PM Joco[m]1: You could hard set the starting view from within the VCP main python file
04:41 PM Joco[m]1: I do that for panning on my UI
04:41 PM Lcvette: i dunno python stuff
04:41 PM Joco[m]1: I can do that for you
04:41 PM Lcvette: /o\
04:41 PM Lcvette: i think lathe should only be xz view
04:41 PM Lcvette: no rotation
04:42 PM Lcvette: but i don't think turboss knows how to turn rotation off in vtk without messing things up
04:42 PM Joco[m]1: I turn it off
04:42 PM Joco[m]1: Panning mode
04:42 PM Joco[m]1: Set panning mode in code and no button to change it
04:43 PM Lcvette: ah intersting
04:43 PM Joco[m]1: I hard set panning mode active on my UI.
04:43 PM Lcvette: can you set the xz view so it matches what a lathe should look like?
04:43 PM Joco[m]1: I have a button to toggle it on and off but starting state is on
04:44 PM Joco[m]1: If there is a slot on VTK for a view we can hard set that view in the starting python code of the VCP
04:46 PM Lcvette: ok
04:46 PM Lcvette: I am about to run a lathe pully real quick...I hope
04:46 PM Lcvette: ttryiung to squeeze it in before dinner
04:48 PM Joco[m]1: I’m just reading he VTK code
04:53 PM Joco[m]1: Lcvette: had a look at code back in March and not seeing a setviewxz slot
04:56 PM Joco[m]1: It might be there is a missing view for lathes
06:41 PM Lcvette: hazzy: im beggin please make those dro's work
06:41 PM Lcvette: im floundering in gmoccapy trying to get things working in lathe it is horrid
06:53 PM Joco[m]1: Donuts. The ultimate bribe.
06:54 PM Joco[m]1: I’m sitting down at a little hole in a wall cafe getting coffee and Baileys cream donuts
07:03 PM hazzy-m1: Joco: nice
07:04 PM hazzy-m1: Lcvette: We can merge, but they don't have radius mode yet
07:04 PM hazzy-m1: or dia mode ...
07:04 PM Lcvette: i only use diameter mode
07:04 PM Lcvette: \o/
07:04 PM hazzy-m1: which ever it is
07:04 PM Lcvette: oh you mean only has radius mode
07:05 PM Lcvette: not diameter mode?
07:05 PM Lcvette: /o\
07:06 PM hazzy-m1: yeah
07:06 PM hazzy-m1: should be an easy fix
07:06 PM hazzy-m1: so it needs to just multiply the value by 2 for the Y axis?
07:09 PM Lcvette: X axis?
07:09 PM Lcvette: I dunno
07:11 PM Lcvette: hazzy: lathe uses x and z
07:15 PM Joco[m]1: hazzy: x = cross slide, z = axis out from lathe spindle
07:58 PM * hazzy-m1 should have known that
07:58 PM hazzy-m1: thanks Joco!
08:16 PM Joco[m]1: Lcvette: the load meter on PB. What does that hook up to? Is there a HAL pin exposed for it?
08:18 PM hazzy-m1: it currently is not a HAL load meter
08:18 PM hazzy-m1: so no way to use it
08:19 PM Joco[m]1: Ok. So where does it get its load data from?
08:19 PM hazzy-m1: we need to finish the HAL load meter, got hung of on the paint event
08:19 PM Joco[m]1: Ah snap
08:19 PM hazzy-m1: it works in vertical orientation, but not in horizontal and inverted
08:21 PM hazzy-m1: Joco: https://github.com/kcjengr/qtpyvcp/tree/layout_aware_bar_indicator
08:21 PM Joco[m]1: oh. How odd. Is that something worth me getting into ? No promises. But if no one else looking at it. ...
08:21 PM hazzy-m1: Yes, that would be awesome!
08:21 PM hazzy-m1: its just a little simple math
08:22 PM Joco[m]1: I’m interested as the servo I’m looking to use as a spindle motor can report load data. Amps and torque
08:22 PM hazzy-m1: sweet!
08:23 PM Joco[m]1: It’s only 1 HP but I have found a number of users that seem to have success. Worse case I use it for something else and accept I need something in the 3hp range and accept the $ associated with that.
08:24 PM Joco[m]1: Anyway - back on topic. I’ll start to snoop at that widget.
08:29 PM Joco[m]1: hazzy: is it this widget: https://github.com/kcjengr/qtpyvcp/blob/layout_aware_bar_indicator/qtpyvcp/widgets/hal_widgets/hal_bar_indicator.py
08:31 PM Joco[m]1: Just snooping on phone as in car with the boss (aka The Wife)
08:35 PM hazzy-m1: Yes, that's the HALBarIndicator, and its based off of this bar indicator:
08:35 PM hazzy-m1: https://github.com/kcjengr/qtpyvcp/blob/layout_aware_bar_indicator/qtpyvcp/widgets/base_widgets/bar_indicator.py
08:36 PM Not-944e: [02qtpyvcp] 07KurtJacobson pushed 0353 commits to 03ed-enhance-color-bug [+1/-0/±69] 13https://git.io/JfHSa
08:36 PM Not-944e: [02qtpyvcp] 07joco-nz 03aca011c - Merge pull request #2 from kcjengr/master
08:36 PM Not-944e: [02qtpyvcp] 07James 037f2e73f - MDIHistory widgit based on QListWidget:
08:36 PM Not-944e: [02qtpyvcp] 07James 038bbdd1b - Rough pass functionality done and looking to be finctional. Ready for tests and code refinement.
08:36 PM Not-944e: [02qtpyvcp] ... and 50 more commits.
08:36 PM Not-944e: [02qtpyvcp] 07KurtJacobson created branch 03ed-enhance-color-bug - 13https://git.io/fhCou
08:36 PM hazzy-m1: oops
08:36 PM hazzy-m1: what did I do
08:36 PM hazzy-m1: haha
08:37 PM Joco[m]1: O.o
08:37 PM travis-ci: kcjengr/qtpyvcp#1593 (ed-enhance-color-bug - 55291d1 : Kurt Jacobson): The build passed.
08:37 PM travis-ci: Diff view : https://github.com/kcjengr/qtpyvcp/compare/aca011caa99b^...55291d197b95
08:37 PM travis-ci: Build details : https://travis-ci.org/kcjengr/qtpyvcp/builds/697856319
08:38 PM hazzy-m1: I guess I can't push the the PR...
08:38 PM hazzy-m1: strange
08:38 PM hazzy-m1: * I guess I can't push to the PR...
08:38 PM Joco[m]1: Beats me. It’s all git magic.
08:39 PM hazzy-m1: It will all end up in the same place eventually, but not what I intended to do
08:39 PM Joco[m]1: svn I understand. Git feels like there is a large does of black magic in the mix.
08:40 PM Joco[m]1: dose dang nabbit. Bloody auto correct
08:43 PM Lcvette: Hazzy you pushed. \o/
09:17 PM Lcvette: Hazzy how do i implement?
09:26 PM hazzy-m1: Lcvette: DRO?
09:27 PM Lcvette: Yeah
09:27 PM Lcvette: Does it just work or do i need to change or the dros for a new widget?
09:28 PM Lcvette: hazzy: ^^^
09:31 PM hazzy-m1: you need to change to a new widget
09:31 PM hazzy-m1: but I have not merged to master yet
09:32 PM hazzy-m1: I decided to create a new widget so it would not break existing VCPs that used the old style DROs
09:32 PM hazzy-m1: but the old one will be depreciated
09:32 PM Lcvette: Ah
09:33 PM Lcvette: What's depreciated
09:33 PM hazzy-m1: * but the old one will be deprecated
09:33 PM Lcvette: In these terms
09:33 PM Lcvette: I know it's meaning with values in cars etc
09:34 PM hazzy-m1: marked as obsolete, and something that will be removed down the road
09:34 PM Lcvette: Deprecated
09:34 PM Lcvette: Ah
09:34 PM hazzy-m1: auto correct got me, I fixed it
09:34 PM Lcvette: 🤣
09:35 PM hazzy-m1: damn auto correct lol
09:35 PM Lcvette: Lol
09:35 PM hazzy-m1: but I'd be in even worse trouble without it haha
09:35 PM Lcvette: /o\
09:37 PM * hazzy-m1 uploaded an image: ima_baaa0df.jpeg (86KB) < https://matrix.org/_matrix/media/r0/download/matrix.org/jVDslkgnRJJOaSnwyfysTMBG >
09:37 PM hazzy-m1: somebody said that was me, and they are not wrong
09:37 PM Lcvette: Lol
09:37 PM Lcvette: Walfus
09:38 PM Lcvette: I'm gonna demand some walfus for breakfast from my wife
09:39 PM Lcvette: If no one hears from me in a few days report me buried in the back yard
09:40 PM hazzy-m1: hahahaha
09:40 PM Lcvette: :D
10:28 PM Joco[m]1: yup - if I demand anything from the boss its is ALWAYS outside of kicking distance
11:17 PM Joco[m]1: hazzy: you might need to explain again what the issue with that HAL bar indicator is. Cose I'm just running it in dummy UI at the moment. It's horizontal, I'm setting the pin values via halshow and things seem to be working fine.
11:22 PM Joco[m]1: ah - think I found it. When I put it into vertical mode the color gradient goes to pot
11:27 PM Joco[m]1: and the issue is in the base widget