#hazzy | Logs for 2020-06-11
Back
[00:59:00] -!- c-log has quit [Ping timeout: 256 seconds]
[01:02:27] -!- c-log has joined #hazzy
[01:32:56] -!- jmarsac has joined #hazzy
[02:15:35] -!- KimK has quit [Ping timeout: 272 seconds]
[02:29:05] -!- KimK has joined #hazzy
[04:00:49] -!- c-log has quit [Ping timeout: 264 seconds]
[04:04:30] -!- c-log has joined #hazzy
[06:05:59] -!- jmarsac has quit [Read error: Connection reset by peer]
[06:07:54] -!- jmarsac_ has joined #hazzy
[07:45:13] -!- c-log has quit [Ping timeout: 264 seconds]
[07:49:39] -!- c-log has joined #hazzy
[08:00:42] <Lcvette> morning
[08:02:48] <JT-Cave> morning
[08:46:57] -!- jmarsac has joined #hazzy
[08:50:47] -!- jmarsac_ has quit [Ping timeout: 272 seconds]
[08:53:44] <TurBoss> hello
[09:01:31] -!- JT-Shop_ has quit [Quit: Leaving]
[09:01:48] -!- JT-Shop has joined #hazzy
[10:18:06] <Not-944e> [02qtpyvcp] 07hadcom opened issue 03#38: AttributeError: 'Status' object has no attribute 'backplot_gcode_error' - 13https://git.io/Jf9Rd
[12:12:32] -!- c-log has quit [Ping timeout: 256 seconds]
[12:47:03] -!- c-log has joined #hazzy
[12:51:51] -!- c-log has quit [Remote host closed the connection]
[12:52:11] -!- c-log has joined #hazzy
[13:24:49] -!- c-log has quit [Ping timeout: 264 seconds]
[13:32:27] -!- c-log has joined #hazzy
[15:10:35] -!- michyamrane has joined #hazzy
[15:27:55] -!- michyamrane has quit [Ping timeout: 246 seconds]
[16:46:43] -!- ute[m] has joined #hazzy
[16:48:22] -!- jmarsac_ has joined #hazzy
[16:50:51] -!- jmarsac has quit [Ping timeout: 272 seconds]
[17:11:45] <Lcvette> o/
[17:18:32] <Lcvette> JT are you running linuxcnc on your lathe?
[17:36:53] * JT[m] uploaded an image: VectorImage_2020-06-11_043553.jpg (8195KB) < https://matrix.org >
[17:36:53] <JT[m]> Lcvette yes
[17:38:24] <JT[m]> Assuming you're talking about the CHNC and not the Samson lol
[17:39:16] <Joco[m]1> FRIDAY!!
[17:45:08] <Lcvette> JT: do you use a master tool method for tool offsets?
[17:45:27] <Lcvette> im new to lathes and trying to sort out what i need to do to setup my tools
[17:50:51] <JT[m]> I have an 8 station turret
[17:52:49] <JT[m]> I set the XZ offset when I put a tool in the holder, no repeatability when changing tools
[17:53:36] <JT[m]> Tool 1 I use to set Z for the material
[17:54:46] <JT[m]> I set Z tool offset on the face of the spindle
[18:32:14] -!- jmarsac_ has quit [Read error: Connection reset by peer]
[20:31:47] <lmclaren[m]1> Hi, I am new to this but am I correct in thinking that https://github.com has not been merged into trunk yet?
[20:37:33] <hazzy-m1> lmclaren: correct
[20:38:46] <hazzy-m1> lmclaren: were you the one that needed the HAL pins?
[20:38:48] <lmclaren[m]1> @haz
[20:38:55] <lmclaren[m]1> yes
[20:39:29] <lmclaren[m]1> Does it need to wait for a feature rollup before it will be merged?
[20:39:59] <lmclaren[m]1> not pushing, I understand that people are doing this on their own free time
[20:41:45] <hazzy-m1> I'm not real comfortable with that being in the main application code. The exposed HAL pins should at lease be defined in a separate module, and preferably in a plugin so they can be added or modified on a per VCP basis if needed
[20:43:13] <hazzy-m1> lmclaren: have you created your own VCP, or using one of the standard ones like ProbeBasic?
[20:43:44] <lmclaren[m]1> I am using probebasic
[21:06:59] <hazzy-m1> ok
[21:07:03] * hazzy-m1 uploaded an image: image.png (37KB) < https://matrix.org >
[21:07:25] <hazzy-m1> syntax highlighting is working again!
[21:12:18] <Joco[m]1> <hazzy-m1 "I'm not real comfortable with th"> If the Hal pins were VCP specific I agree. But are these ones not just exposing fundamental capability’s within the LinuxCNC python binding?
[21:13:40] <Joco[m]1> Or do you really just want anything Hal related in a separate module, period?
[21:22:55] <hazzy-m1> The HAL pins you have added are exposing the QtPyVCP actions as HAL pins, which is good, but I don't think that belongs in application.py, since it makes the entirety of QtPyVCP dependent on the LinuxCNC specific actions, which might not always be available in that way (for instance a remote interface, or QtPyVCP used for something other than a LinuxCNC interface)
[21:24:15] <hazzy-m1> I think those HAL pins should probably be exposed in the same location that the actions are defined, or in a plugin
[21:29:27] <Joco[m]1> will have a look at how to expose with actions. Not sure when will get to it. Now that NZ is about back to normal not go anywhere near the spare time.
[21:30:12] <Not-944e> [02qtpyvcp] 07joco-nz commented on pull request 03#37: Expose override reset pins - cheerypick - 13https://git.io/Jf95h
[21:30:13] <Not-944e> [02qtpyvcp] 07joco-nz closed pull request 03#37: Expose override reset pins - cheerypick - 13https://git.io/Jfwmw
[21:32:56] <hazzy-m1> I'm not sure when the actions module gets imported first, if it gets imported before the hal comp is created it might be a pain
[21:33:25] <hazzy-m1> really need to move actions to a plugin so we have control of the order everything is loaded in
[21:35:04] <hazzy-m1> I was temped to merge what you did since it works, and reconsider later, but am suffering from paralyses by analysis
[21:39:16] <Joco[m]1> lol
[21:39:38] <Joco[m]1> decision made. pulled the pull ;-)
[21:40:08] <Joco[m]1> off to find some lunhc