#hazzy Logs

May 08 2020

12:27 AM JamesW[m]: rodw-au: the gui building is pretty easy. I went from nothing to this in about 2 weeks: https://drive.google.com/open?id=1NKFGheYJj3H1ilZ2A08LEWO8kJnmZLyV
12:28 AM JamesW[m]: its at the stage that it is more than functional enough to use as my main gui on my mill. Now I confess I do not use things in a sophisticated manner. But its got most of the basics in plaxce.
12:29 AM JamesW[m]: Was wondering houw your plasma spaceship was going. :)
12:29 AM JamesW[m]: Oh - I ended up buying a new lathe as well. The little AL320 served me well but moved up to something a little bigger
12:31 AM JamesW[m]: I got an AL346V
12:31 AM JamesW[m]: love the variable speed drive.
12:31 AM JamesW[m]: like anything its all a compromise. But this one is working extremely well for me.
12:34 AM JamesW[m]: Are you looking for a customised/modern version of the gmoccapy plasma variant?
12:34 AM JamesW[m]: awesome!
12:35 AM JamesW[m]: you probably need one of the lads who really know the frameowrk and has a design lens.
12:36 AM JamesW[m]: using 7i76e?
12:36 AM JamesW[m]: or one of the smaller ethernet variants?
12:40 AM JamesW[m]: ok
12:40 AM JamesW[m]: well once the northern hemisphere lads wake up again you can start the conversation in ernest
12:40 AM JamesW[m]: I'm just an amatuer hack. :-D
12:44 AM JamesW[m]: from previous discussons people have said they are on their phone
12:44 AM JamesW[m]: so must be
12:53 AM JamesW[m]: later
02:30 AM JamesW[m]: hazzy: when you wake up would be good to know how I can submit updates to the geditor widget. Or at least get a code review and help/advice on making it meet standards. I now have the MDI hitsory/gcode view working. Got the notify on the status plug operating after looking over the code. So yeah .... some useful progress I think.
04:01 AM TurBoss: good morning
04:05 AM JamesW[m]: morning
04:05 AM JamesW[m]: TurBoss - how much do you know about the midientry_widget and how the code is supposed to work ?
04:06 AM JamesW[m]: trying to understand when the initialize(self) and terminate(self) procs fire
04:07 AM JamesW[m]: cose from what I can see/understand the history being built up does not write to disk until terminate fires
05:08 AM TurBoss: can't remember
05:08 AM TurBoss: I'll check the source
05:08 AM TurBoss: https://github.com/kcjengr/qtpyvcp/blob/master/qtpyvcp/widgets/input_widgets/mdientry_widget.py
05:09 AM TurBoss: it basically overrides a regular QLineEdit and add such features
05:09 AM TurBoss: ```
05:09 AM TurBoss: class MDIEntry(QLineEdit, CMDWidget):
05:09 AM TurBoss: here is the ihnerance
05:10 AM TurBoss: https://github.com/kcjengr/qtpyvcp/blob/43f4824401e61aa4ae9074fed291cf1f4df80197/qtpyvcp/actions/machine_actions.py#L173
05:10 AM TurBoss: it calls issue_mdi
05:11 AM JamesW[m]: so if I understand correctly if I want the gcodeeditor to be able to see the lastest MDI history then I need to either be writing the history to file after each submit or create a reference link between the two instances to the gcodeeditor can see the model list?
05:12 AM TurBoss: so you want to save mdi history to a file?
05:13 AM JamesW[m]: mdi history is saved to file on termination
05:14 AM JamesW[m]: however current history while the gui is running is held in memory in a mdientry widget instance
05:14 AM JamesW[m]: I'm ignoring the whole issue of multiple mdi entry widgets at the moment and the conflict that would create
05:14 AM JamesW[m]: SO ....
05:14 AM JamesW[m]: if you want to be able to reference that history you need a way to make it accesable to other widgets
05:15 AM JamesW[m]: either via file on disk or via some in memory list
05:16 AM JamesW[m]: on of the behaviours of the gcodeentry widget is supposed to be to be able to list the mdi history when the machine is in mdi mode
05:16 AM JamesW[m]: I have that working now as it loads the past history from the mdi_history file
05:17 AM JamesW[m]: BUT of course as soon as you start typing new commands via mdi I need a method to trap those and update the gcodeedit widget.
05:17 AM JamesW[m]: Therefore which is the more proper path .... via disk file or in memory list?
05:18 AM JamesW[m]: disk file is in place at the moment, but only updated on gui exit. In memory list linkage would be net new
05:18 AM TurBoss: for what i can see in the code each submit is stored in self.model.setStringList if not allready
05:18 AM JamesW[m]: but the in memory list does exist
05:18 AM JamesW[m]: yup - in memory list
05:19 AM JamesW[m]: but that is on the MDI widget objwct
05:19 AM JamesW[m]: it is not on a "global" list
05:20 AM TurBoss: we can add a signal that sends the submit command to the widget you need
05:20 AM JamesW[m]: the better model would be to have that moved to the INFO or STATUS singletons
05:20 AM TurBoss: or that
05:20 AM TurBoss: a new model
05:20 AM JamesW[m]: I like that latter as that means multiple mdi's be operate off the single list
05:21 AM JamesW[m]: and anything else wanting to reference it can get at it
05:21 AM JamesW[m]: but I confess it's been a long time since I have thought through these design considerations so might well be missing something important
05:22 AM TurBoss: so if i did understand you want to wtrite to the editor using the mdi prompt
05:22 AM TurBoss: ???
05:23 AM JamesW[m]: i essentially want what amounts to a self contained list of recently used (say last 20) MDI commands.
05:23 AM JamesW[m]: this should be referenced/updated by any MDI entryline widget that is used in a gui
05:23 AM TurBoss: ahhh a log for mdi?
05:24 AM JamesW[m]: it would also be available to be lists by the gcodeeditor when the mode is MDI
05:24 AM JamesW[m]: yeah - the log functions already exists from a history angle
05:24 AM JamesW[m]: the mdi history is save to disk on gui exit
05:24 AM JamesW[m]: but it feels a bit limited at the moment
05:25 AM TurBoss: so the history file is only saved on close
05:25 AM TurBoss: ok
05:25 AM JamesW[m]: the intention in the gcodeeditor (from reading the original code) is to have it dynamically flick between program display and mdi history display based on the machine mode (mdi, manual, auto)
05:26 AM JamesW[m]: I have the dynamic flicking working.
05:26 AM JamesW[m]: but the history side of things needs rework
05:26 AM TurBoss: https://github.com/kcjengr/qtpyvcp/blob/master/qtpyvcp/widgets/input_widgets/mdientry_widget.py#L75
05:26 AM TurBoss: this has to be triggered on each mdi
05:26 AM TurBoss: without checking if duped
05:27 AM JamesW[m]: and in this discussion with you I have pretty much convinced myself that the better way is to seperate it out into either the info or status data chanels
05:27 AM * TurBoss sent a long message: < https://matrix.org/_matrix/media/r0/download/matrix.org/fIFFmMvPadCOlFXiwqXQVpcB >
05:28 AM JamesW[m]: yeah understand all that
05:28 AM TurBoss: iojk
05:28 AM JamesW[m]: undertsand what it is doing
05:28 AM TurBoss: * ok
05:28 AM JamesW[m]: I just think where it is storing it in memory needs to be a common spot
05:28 AM JamesW[m]: not unique for each mdientry widget instance
05:28 AM TurBoss: now is one spot for each mdi entry
05:28 AM TurBoss: ok
05:28 AM TurBoss: gotcha
05:29 AM TurBoss: but i don't know how to achiev
05:29 AM TurBoss: * but i don't know how to achieve
05:29 AM JamesW[m]: I do.
05:29 AM TurBoss: cool
05:29 AM JamesW[m]: but is more "hacking" than was planned.
05:29 AM JamesW[m]: I probably need a design decision from hazzy
05:29 AM TurBoss: brb linuxcnc dev
05:29 AM TurBoss: yes thats good
05:29 AM TurBoss: idea
05:30 AM JamesW[m]: I'll hassle him tomorrow. :-p
05:30 AM JamesW[m]: hear that hazzy ?! Gonna hassle yah!!
05:30 AM JamesW[m]: ROFL
05:32 AM TurBoss: yo back
05:33 AM * TurBoss uploaded an image: Captura de pantalla de 2020-05-08 12-33-00.png (7KB) < https://matrix.org/_matrix/media/r0/download/jauriarts.org/vOYcoafxasnfrPecfwboeRuF >
05:34 AM JamesW[m]: gosh that's an old one.
05:35 AM TurBoss: :P
05:35 AM JamesW[m]: I'm starting to get some of my coding mojo back. :)
05:35 AM TurBoss: i worked next to the sun office in Valencia
05:35 AM TurBoss: once the was bought by oracle the just place a big sticker over the sun logo
05:36 AM JamesW[m]: ahhh - nice. Been to Valencia. Nice spot
05:36 AM TurBoss: :P
05:36 AM TurBoss: they drive like crazy
05:36 AM TurBoss: i hate it
05:36 AM * TurBoss is from Castellon
05:36 AM TurBoss: next to valencia
05:36 AM JamesW[m]: yup - Portugal was what gave me the real willies
05:37 AM JamesW[m]: Spain I was ok with
05:37 AM TurBoss: :)
05:38 AM JamesW[m]: Driving through the back streets in Toledo was like threading a needle
05:38 AM JamesW[m]: sheesh
05:38 AM JamesW[m]: stupid tight
05:38 AM TurBoss: XD
05:38 AM TurBoss: very old
05:39 AM JamesW[m]: yup
05:39 AM TurBoss: did yoi bought a sword?
05:39 AM TurBoss: * did you bought a sword?
05:39 AM JamesW[m]: they could just about shake hands out a window from one side of the street to the other
05:39 AM TurBoss: :)
05:39 AM JamesW[m]: nah - big tourist trap
05:39 AM TurBoss: my surname is Toledano!
05:40 AM JamesW[m]: interesting to look around though
05:40 AM TurBoss: wich means from toledo
05:40 AM TurBoss: ok back to the plugins stuff
05:40 AM JamesW[m]: it was MANY years ago. Pre kids. When wife and I were living in UK
05:41 AM JamesW[m]: rgr
05:41 AM JamesW[m]: I'm quietly tinkering on python as well
05:41 AM TurBoss: JamesW: how does you idea look?
05:41 AM TurBoss: for the history plugin
05:42 AM JamesW[m]: in esscene I want to have the mdi command history in a common location. So any number of mdi widget instance reference and update it.
05:43 AM JamesW[m]: Then have the ability ro have gcodeditor intance to reference that list and when in MDI mode show the history and have it update as mdi commands are entered. I ALSO wan to be able to select a line from that list and execute it
05:44 AM TurBoss: ok so we need a new plugin or hack a existing one
05:44 AM JamesW[m]: yup
05:44 AM JamesW[m]: it could easily hang of the Info one
05:44 AM JamesW[m]: off
05:45 AM TurBoss: infp¿
05:45 AM JamesW[m]: but Info might be intended to be static.
05:45 AM TurBoss: info?
05:45 AM JamesW[m]: utilities/info.py
05:45 AM TurBoss: checking
05:46 AM JamesW[m]: or add it to status.py plugin
05:46 AM JamesW[m]: since status is clearly about dynamic things
05:47 AM JamesW[m]: a whole new plugin seems OTT
05:47 AM TurBoss: ok
05:47 AM JamesW[m]: but that is what I think I need a design decision from hazzy on
05:47 AM TurBoss: yep
05:47 AM TurBoss: he has a better global view
05:48 AM JamesW[m]: yup
05:48 AM JamesW[m]: info has a getMDIHistoryFile
05:48 AM JamesW[m]: method
05:48 AM JamesW[m]: which was why I started thinking it could be a natural extension
05:52 AM TurBoss: maybe we should skip the mdi_widget and go to the issue_mdi
05:53 AM TurBoss: line 174 from machine_actions
05:55 AM JamesW[m]: I think if you moving the storage of the common list centrally then this makes sense as the place to update that lisrt
05:55 AM JamesW[m]: or does it .....
05:56 AM TurBoss: or
05:56 AM TurBoss: ...
05:56 AM TurBoss: play some robot games
05:56 AM TurBoss: :P
05:56 AM JamesW[m]: lol
05:56 AM TurBoss: lol
05:56 AM JamesW[m]: got a silly logic bug I need to solve then sleep time
06:08 AM hazzy-m: Morning
06:08 AM TurBoss: morning @hazzy
06:08 AM TurBoss: JamesW: was looking for advice
06:08 AM TurBoss: global mdi history
06:09 AM hazzy-m: I hear I'm gonna be hassled today, might go back to bed :D
06:09 AM JamesW[m]: lol
06:09 AM TurBoss: cool
06:09 AM TurBoss: I can do somethin if you tell me where
06:09 AM TurBoss: plugins?
06:10 AM hazzy-m: Status is a good place for now, it's also where the recent file list is kept
06:10 AM JamesW[m]: ok - so centralise mdi histtory into Status
06:11 AM hazzy-m: Correct, that's much better, than multiple objects can use the MDI history
06:12 AM JamesW[m]: yup - that's was the entire line of conversation with TurBoss
06:12 AM hazzy-m: Perfect, when I get to work I'll read the whole conversation, eating breakfast
06:12 AM JamesW[m]: no probs.
06:13 AM JamesW[m]: Friday sleep time for me.
06:13 AM JamesW[m]: getting gcodeeditor slowly knocked into a shape I like
06:14 AM JamesW[m]: not sure others will but it will do what I'm looking for :-p
06:23 AM TurBoss: okay thankyou !
06:34 AM JamesW[m]: right ... sleeps for real. Later.
09:06 AM Lcvette: morning
09:06 AM hazzy-m: rodw-au: Would diffidently be willing to help with developing a plasmac GUI. What is the time frame?
09:07 AM hazzy-m: Lcvette: morning
09:10 AM Not-944e: [02probe_basic] 07Lcvette created branch 03master 13https://git.io/JfcPA
09:10 AM Lcvette: hazzy: o/
09:11 AM Not-944e: [02probe_basic] 07KurtJacobson pushed 031 commit to 03gh-pages [+88/-0/±0] 13https://git.io/JfcXe
09:11 AM Not-944e: [02probe_basic] 07traviscibot 037fe6fd8 - Deploy kcjengr/probe_basic to github.com/kcjengr/probe_basic.git:gh-pages
09:12 AM hazzy-m: whatcha doing?
09:12 AM Lcvette: pulling out pb lathe to try and get it caught up
09:13 AM hazzy-m: sweet!
09:13 AM Lcvette: whatchu doin?
09:13 AM hazzy-m: I'm wondering if BP lathe should be in a separate repo, since it does not share any code or subs with the mill
09:14 AM hazzy-m: workin'
09:15 AM Lcvette: /o\
09:15 AM hazzy-m: trying to find the bug that won't let hustler make a new style mower deck, making a little progress
09:16 AM Lcvette: bug
09:16 AM Lcvette: mowerdeck?
09:17 AM TurBoss: Hello!
09:17 AM hazzy-m: yeah, the machine thinks the folding beam is going to it for floor on one of the bends, and it looks like it may. I think I'm gonna have to decrease the travel on one of the axes
09:17 AM Lcvette: o/
09:17 AM Lcvette: :D
09:17 AM Lcvette: turboss is hjere!
09:18 AM hazzy-m: * yeah, the machine thinks the folding beam is going to hit the floor on one of the bends, and it looks like it may. I think I'm gonna have to decrease the travel on one of the axes
09:18 AM Lcvette: * turboss is here!
09:18 AM hazzy-m: hey
09:18 AM TurBoss: hey
09:19 AM Lcvette: what tool data is needed in lathe
09:21 AM Lcvette: geez...lcvette can't remember anything about the lathe stuff
09:21 AM Lcvette: /o\
09:23 AM TurBoss: 😲
09:24 AM * Lcvette sent a long message: < https://matrix.org/_matrix/media/r0/download/matrix.org/SGHsCwCDLEbeHGBdacAaxrkZ >
09:25 AM Lcvette: any ideas?
09:25 AM Lcvette: can't even get lathe to load
09:26 AM Lcvette: oh it loaded but with lots of errors in the temrinal
09:28 AM Lcvette: TurBoss: did you make a vtk for lathe?
09:28 AM Lcvette: that has only x and z
09:28 AM Lcvette: 2D
09:29 AM TurBoss: it shows lathe programs yes but haven tested
09:29 AM Lcvette: wanna test?
09:29 AM TurBoss: no lath
09:29 AM TurBoss: sure!
09:29 AM Lcvette: in PB?
09:29 AM TurBoss: wait I'll reboot to dev
09:30 AM * Lcvette sent a long message: < https://matrix.org/_matrix/media/r0/download/matrix.org/hXfEBFxPzwSYFrpxcnJJWxXz >
09:30 AM Lcvette: this is the stack of errors in PB lathe when i boot up
09:30 AM Lcvette: hazzy: see anything easy to fix?
09:31 AM Lcvette: TurBoss: for lathe we probably need a way to swap the x axis orientation
09:31 AM Lcvette: for front tool post machines and back tool post machines so the plot is accurate
09:35 AM TurBoss: okay
09:35 AM TurBoss: I'm taking a look at thoose messages
09:37 AM Lcvette: \o/
09:38 AM Lcvette: we will get lathe working and it will be glorious!
09:38 AM TurBoss: hurray!
09:55 AM hazzy-m: sweet!
09:55 AM TurBoss: Lcvette: how do i run the lathevcp?
09:55 AM Lcvette: um
09:55 AM Lcvette: sek
09:55 AM Lcvette: i use a launcher
09:55 AM * TurBoss sent a long message: < https://matrix.org/_matrix/media/r0/download/matrix.org/JMRUKbNNYtPFZqkjqqnDGhTQ >
09:56 AM hazzy-m: Lcvette: I noticed you have some white on white text in PB, in menus and some comboboxes
09:56 AM Lcvette: ?
09:56 AM Lcvette: where?
09:56 AM * Lcvette uploaded an image: Screenshot_2020-05-08_10-55-26.png (40KB) < https://matrix.org/_matrix/media/r0/download/matrix.org/tnTVwljJHeTIpCFRkXursjTD >
09:56 AM Lcvette: turboss ^^^
09:56 AM Lcvette: this is how i launch it
09:57 AM Lcvette: hazzy: ?
09:57 AM TurBoss: i on't have a lathe config
09:57 AM Lcvette: where is white on white text?
09:57 AM Lcvette: should be in the dev folder no?
09:58 AM * Lcvette uploaded an image: Screenshot_2020-05-08_10-58-04.png (24KB) < https://matrix.org/_matrix/media/r0/download/matrix.org/VNawhccqVcDjQbPGkrWCIIWq >
09:58 AM Lcvette: TurBoss: ^^^
09:59 AM TurBoss: oh
09:59 AM TurBoss: on the lathe branch?
10:00 AM Lcvette: yes
10:00 AM TurBoss: named lathe_vcp?
10:00 AM Lcvette: but i think that should be there on all branches
10:00 AM Lcvette: yes
10:00 AM * Lcvette uploaded an image: Screenshot_2020-05-08_11-00-04.png (23KB) < https://matrix.org/_matrix/media/r0/download/matrix.org/exCMSJAOTwcDzfgWvqhaDqLQ >
10:00 AM Lcvette: thats what im on
10:01 AM TurBoss: okay!
10:09 AM TurBoss: ok getting that error
10:09 AM TurBoss: i'll try to fix
10:09 AM Lcvette: im connecting the vtk backplot buttons for zoom, clear etc that are relevant to lathe screen, i don't see pan
10:10 AM Lcvette: i thought you did the pan thing?
10:11 AM Lcvette: oh i bet i know, its because of how far behind lathe is to probe basic
10:12 AM TurBoss: the pan thin is on qtpyvcp
10:12 AM TurBoss: should be there
10:13 AM TurBoss: it requieres a bool signal
10:13 AM Not-944e: [02probe_basic] 07Lcvette pushed 031 commit to 03lathe_vcp [+2/-0/±1] 13https://git.io/JfcD2
10:13 AM Not-944e: [02probe_basic] 07Lcvette 0337afcb0 - added soem vtk button controls to PB Lathe
10:13 AM Lcvette: ah!
10:13 AM Lcvette: that must be it
10:13 AM Lcvette: ok looking
10:13 AM Lcvette: hazzy what white on white?
10:13 AM hazzy-m: text on background
10:13 AM hazzy-m: cant read
10:14 AM Lcvette: where?
10:15 AM Lcvette: hazzy^^^
10:17 AM TurBoss: Lcvette: thoose errors come from missiing settings
10:18 AM TurBoss: the settings yaml does't have some ui settings or the oposite
10:19 AM Lcvette: dunno
10:19 AM Lcvette: is it becauyse its behind?
10:19 AM Lcvette: * is it because its behind?
10:20 AM TurBoss: no
10:21 AM TurBoss: tool-change-position.x-tool-change-position
10:21 AM Lcvette: i don't understand what you mean by setting
10:21 AM TurBoss: not in the yaml
10:21 AM TurBoss: the persistent settings
10:22 AM Lcvette: lcvettes brain is trying to undrstand
10:22 AM Lcvette: its not in the ui or not in the yaml
10:22 AM TurBoss: spray som wd40
10:22 AM Lcvette: on the screen?
10:23 AM TurBoss: some probe settings
10:23 AM Lcvette: spray it on?
10:23 AM TurBoss: are not in the presisten yml
10:23 AM TurBoss: :P
10:23 AM TurBoss: 🧠
10:23 AM Lcvette: ok so probe screen boxes need to be defined in yaml
10:23 AM * TurBoss sent a long message: < https://matrix.org/_matrix/media/r0/download/matrix.org/QjQfswbgtntOLYpdnXAvwqFF >
10:23 AM Lcvette: can copy over from PB
10:24 AM TurBoss: thoose are the ones defined on the yaml
10:24 AM Lcvette: got it!
10:24 AM Lcvette: on it!
10:24 AM TurBoss: cool
10:24 AM Lcvette: \o/
10:24 AM Lcvette: we will be victorious
10:24 AM TurBoss: great
10:24 AM TurBoss: 🧟 eats 🧠
10:25 AM TurBoss: brb
10:27 AM * Lcvette sent a long message: < https://matrix.org/_matrix/media/r0/download/matrix.org/EYWWZGybNWTuWvaDirrOWYrA >
10:28 AM hazzy-m: you are missing a dialog definition in the YAML
10:28 AM hazzy-m: copy over from the regular YAML fil
10:28 AM hazzy-m: e
10:31 AM * Lcvette uploaded an image: Screenshot_2020-05-08_11-30-45.png (91KB) < https://matrix.org/_matrix/media/r0/download/matrix.org/NvhPLbObMuKCZANVyEvriwAT >
10:32 AM Lcvette: hazzy: ^^^
10:32 AM Lcvette: these are the only differences in the yaml files
10:32 AM Lcvette: i had already copied over the settings stuff
10:42 AM * Lcvette sent a long message: < https://matrix.org/_matrix/media/r0/download/matrix.org/toDYvnXyxHdIWIqolaHqBcYc >
10:42 AM Lcvette: getting better, loads now
10:42 AM Lcvette: these are the remaining errors
10:42 AM TurBoss: https://github.com/kcjengr/qtpyvcp/blob/master/qtpyvcp/yaml_lib/default_config.yml#L66
10:42 AM TurBoss: yo i sback
10:43 AM Not-944e: [02probe_basic] 07Lcvette pushed 031 commit to 03lathe_vcp [+2/-0/±2] 13https://git.io/JfcS7
10:43 AM Not-944e: [02probe_basic] 07Lcvette 0360da359 - updated some files for launch error
10:43 AM Lcvette: i just pushed the changes
10:43 AM Lcvette: still errors
10:43 AM TurBoss: cool
10:50 AM TurBoss: less than before
10:50 AM TurBoss: lol
10:50 AM Lcvette: much less and no pop up window when loading
10:50 AM Lcvette: looks like a few that are left are maybe outdated rules things
10:50 AM Lcvette: im not sure even where to look
10:50 AM * TurBoss uploaded an image: error.gif (2808KB) < https://matrix.org/_matrix/media/r0/download/jauriarts.org/mvJAsssxGjQmPjdFFhlYcMqz >
10:50 AM Lcvette: lol
10:50 AM TurBoss: :)
10:50 AM TurBoss: looks like a rule reqading axis position
10:50 AM TurBoss: could be?
10:52 AM roguish[m]: Lcvette: good morning. machining question?
10:53 AM TurBoss: position:axis?rel
10:53 AM TurBoss: status:spindle[0].speed
10:53 AM roguish[m]: I have some small 304 stainless parts to make. thin sheet, 14 g. .075 thick..
10:53 AM TurBoss: thoose fail
10:53 AM TurBoss: hey roguish
10:53 AM roguish[m]: carbide end mill. probably 1/4.
10:54 AM Lcvette: thats gonna be fun
10:54 AM roguish[m]: thinking about clamping the sheet between some thing aluminum sheets.
10:55 AM roguish[m]: I really don't want to destroy the end mill.
10:56 AM Lcvette: thats how i machine thin materials
10:56 AM Lcvette: sandwich it
10:56 AM Lcvette: roguish: how many
10:57 AM Lcvette: and size?
10:57 AM roguish[m]: well. I need 2 good parts.
10:57 AM roguish[m]: look like dog bones. about 1/2" wide, 3.5 long. 5/16 holes in each end.
10:58 AM Lcvette: more in the future?
10:58 AM roguish[m]: no.
10:58 AM Lcvette: then square up two pieces of aluminum about 3/8" thick
10:58 AM Lcvette: sandwich and rock on
10:59 AM Lcvette: if you do multiples, i would recommend pinning the two plates so they can repeat
10:59 AM roguish[m]: yeah, thats' sort of what i was thinking. drill the holes first, then use screws thgu the holes to hold it while I go all around the perimeter.
11:00 AM Lcvette: so the cut aluminum does not require recutting on subsequent parts
11:00 AM Lcvette: yeah
11:00 AM roguish[m]: thanks for the confirmation of ideas.....
11:00 AM Lcvette: i would use a center form on the platye to bolt on top of it
11:01 AM Lcvette: ie a piece that looks like the "dogbone
11:01 AM Lcvette: that bolts down on top of the sheet using the two 5/16 holes
11:01 AM Lcvette: so it doesn't pull the edge up or vibrate
11:01 AM Lcvette: should keep the tool healthy
11:01 AM Lcvette: if that sheet vibrates that endmill is trash
11:02 AM roguish[m]: think a HSS cutter would work?
11:03 AM Lcvette: probably if its sharp
11:03 AM Lcvette: you good with stainless feeds and speeds?
11:03 AM Lcvette: needs to be slow and aggressive
11:03 AM Lcvette: or it work hardens, especially thin material
11:05 AM roguish[m]: no, not good with sst. well familar with work hardening.
11:07 AM Lcvette: thin 304 work hardens fast because it has no where for the heat to go
11:07 AM Lcvette: so do not pussy foot with the feedrsate
11:23 AM * Lcvette uploaded an image: Screenshot_2020-05-08_12-22-18.png (32KB) < https://matrix.org/_matrix/media/r0/download/matrix.org/wZjazSygNWjVFONihshAktvi >
11:23 AM Lcvette: i fixed the spindle error
11:23 AM Lcvette: but this one im not sure what to do with it
11:23 AM Lcvette: hazzy thoughts?
11:23 AM Lcvette: this is for the DIAM box
11:24 AM Lcvette: under the axis dro's
11:24 AM Lcvette: im not sure what it does actually
11:24 AM Lcvette: off the top of my head
11:25 AM * Lcvette uploaded an image: Screenshot_2020-05-08_12-25-04.png (24KB) < https://matrix.org/_matrix/media/r0/download/matrix.org/ZJyIQXYCiqFKlqmONsPsFmmH >
11:26 AM Lcvette: maybe this is just an indicator?
11:26 AM Lcvette: so perhaps it tracks the X position relative to the centerline and calculates the diameter?
11:27 AM Lcvette: anyone know?
11:28 AM JT-Cave: lathe?
11:28 AM Lcvette: yeah
11:29 AM JT-Cave: http://linuxcnc.org/docs/2.8/html/gcode/g-code.html#gcode:g7
11:29 AM Lcvette: maybe its not needed?
11:30 AM Lcvette: not sure what that box was for
11:30 AM Lcvette: lcvette CRS
11:30 AM Lcvette: lol
11:30 AM Lcvette: i will remove it for now and add it back in if needed
11:31 AM Lcvette: i guess i probably need to make the X axis dro label change for radius or diam mode
11:33 AM * Lcvette sent a long message: < https://matrix.org/_matrix/media/r0/download/matrix.org/oLKXDHkwpXmyQDHQyOGYMDeQ >
11:33 AM Lcvette: down to just these errors now
11:33 AM * JT-Cave finishes up lunch
11:34 AM JT-Cave: Axis shows both diameter and radius for X but doesn't show which mode your in so that would be nice to know
11:34 AM Lcvette: ok i will add x diam and x radius
11:34 AM Lcvette: and have the inactive one gray out the numbers
11:35 AM Lcvette: thoughts?
11:35 AM Lcvette: still visible but not the bold black of the active
11:35 AM JT-Cave: that or a label with Diameter Mode or Radius Mode
11:35 AM JT-Cave: or both
11:35 AM Lcvette: have pushbuttons
11:35 AM Lcvette: mnake them exclusive
11:36 AM Lcvette: and make the inactive grayed out
11:36 AM Lcvette: seems like good redundancy
11:37 AM roguish[m]: Lcvette: in teh shop now.
11:38 AM Lcvette: lcvette heads to Goldsboro to pickup core pumps thyat are ready
11:38 AM Lcvette: back in 3 hours
11:39 AM Not-944e: [02probe_basic] 07Lcvette pushed 031 commit to 03lathe_vcp [+0/-0/±1] 13https://git.io/JfcQP
11:39 AM Not-944e: [02probe_basic] 07Lcvette 03ce9cf49 - fixed more errors, one left need halp finding it!
11:40 AM roguish[m]: JT-Cave: JT-Cave hey I used your 'face' gcode maker thing
12:14 PM Lcvette: TurBoss: how do i try the new lathe vtk?
12:14 PM Lcvette: i will try and put it in testing when i return!
12:14 PM Lcvette: :op
12:14 PM Lcvette: * :o
12:14 PM TurBoss: hmmm
12:15 PM TurBoss: duno
12:15 PM TurBoss: D
12:15 PM TurBoss: vtk should draw something
12:50 PM hazzy-m: it would be awesome to animate the turning in VTK
12:51 PM hazzy-m: its just a 2D revolution, so should be easy
01:16 PM roguish[m]: more bling
01:54 PM JT-Cave: roguish[m], awesome... did it work as expected?
02:44 PM JamesW[m]: Morning
02:44 PM JamesW[m]: lazy Saturday morning
03:03 PM JamesW[m]: I see some work being done on a lathe gui
03:56 PM JamesW[m]: anybody about to answer a quick python language question? not find clear definitions on the net. Guess I'm searching for the wrong terms
04:01 PM JamesW[m]: question: if I want a getter to return the reference to an object not a copy of it, what is the pattern to us?
04:48 PM hazzy-m: In Python most objects aren't mutable, so don't have a fixed reference
04:49 PM hazzy-m: Only lists and dict types are fixed
04:54 PM hazzy-m: that is, a new objects is created every time the value chanhes
04:56 PM JamesW[m]: ok - after some playing thiings seems to be acting as I want so I guess I have it right
04:57 PM JamesW[m]: lol - I did some reading and came away feeling nostalgic for the good old days of C.
04:58 PM JamesW[m]: sometimes I do miss the total and utter control I had when using C
05:08 PM Lcvette: hazzy: can you look at the last lathe error?
05:08 PM Lcvette: It's on the most recent branch of on lathe
05:12 PM JamesW[m]: hazzy: when you have time can you let me know how I would get my local gcodeeditor branch to you for review and when finally clean enough, merge?
05:21 PM hazzy-m: JamesW: yes, I'll be home an a couple hours
05:22 PM hazzy-m: Have you forked QtPyVCP?
05:23 PM hazzy-m: It would be easiest if you forked and put your changes in a branch, and push to your GitHub repo
05:23 PM JamesW[m]: nope - just working off a local clone
05:23 PM JamesW[m]: okay - can do that
05:24 PM hazzy-m: Or just send me the files, but a fork is easier to deal with
05:24 PM JamesW[m]: fork not a prob
05:26 PM JamesW[m]: I guess I just clone my fork to dev box and copy worked on files into it
05:40 PM roguish[m]: JT-Cave: yes. very handy
05:45 PM roguish[m]: JT-Cave: so there are several of those type gcode generators. is there any way to combine them into one screen? say open the general one in linuxcnc, then have tabs or something for the actual routines.
05:53 PM JamesW[m]: Is mobile. :-)
06:22 PM roguish[m]: Lcvette: Chris, you there?
06:24 PM * roguish[m] uploaded an image: 20200508_153453.jpg (5615KB) < https://matrix.org/_matrix/media/r0/download/matrix.org/jwQGgtjBjinGOzKPmBpVjPad >
06:24 PM roguish[m]: I hate F---ng stainless. only trashed 2 end mills...........making the dog bones.
06:30 PM Lcvette: roguish: yo
06:31 PM Lcvette: did you go aggressive on feed and low on rpm?
06:32 PM Lcvette: qalso that should be cut slotted
06:45 PM roguish[m]: not sure what the heck i did. I need to make another pair.
06:45 PM roguish[m]: what do you mean slotted? which part?
06:46 PM roguish[m]: oh, and it's 304L. hardened shit.
06:47 PM Lcvette: higher nickel content
06:47 PM roguish[m]: it's 93.6 outside right now. shop is about 85. i'm done for the day....
06:47 PM Lcvette: i mean don't take light passes, get through it and cut with the side of the endmill
06:48 PM roguish[m]: yeah, that's what i did.
06:48 PM Lcvette: what rp0m?
06:48 PM Lcvette: what feedrate
06:48 PM roguish[m]: 1200, 4
06:48 PM Lcvette: 4?
06:48 PM Lcvette: ipm?
06:48 PM Lcvette: thats why you trashed endmills
06:49 PM * hazzy-m uploaded an image: ima_095f77b.jpeg (236KB) < https://matrix.org/_matrix/media/r0/download/matrix.org/fKxSUwmoZWjIbMmBdttQqDLG >
06:49 PM roguish[m]: what would you use? my mill is limited to 3000 rpm. not faster.
06:49 PM hazzy-m: Freaking rectifier must have failed, I've replaced everything else in the cabinet
06:49 PM Lcvette: rpm is good
06:50 PM Lcvette: 4ipm is way too slow\
06:50 PM Lcvette: just rubbing the endmill
06:51 PM Lcvette: i would be taking like 0.002ipt minimum
06:51 PM Lcvette: safer would be 0.004
06:52 PM Lcvette: or about 19ipm
06:52 PM Lcvette: what size cutter?
06:52 PM roguish[m]: 1/4", 4 flute, carbide
06:52 PM Lcvette: yeah
06:52 PM Lcvette: that cutter will devour stainless at 19ipm and 1200rpm
06:53 PM Lcvette: all the heat will go into the chip
06:53 PM Lcvette: no work hardening
06:53 PM Lcvette: maybe 0.003" since the diameter of the tool is a bit smaller
06:54 PM Lcvette: but use that as your reference, never under 0.002" ipt
06:54 PM Lcvette: or the cutter and part are building up heat
06:59 PM JamesW[m]: Is that .002 ipt for any material or just SS?
07:00 PM roguish[m]: https://www.whitneytool.com/SpeedAndFeedCalculator.aspx
07:01 PM JamesW[m]: Cheers. I have a spreadsheet that helps with the calcs. Will use the reference points and convert to metric.
07:02 PM Lcvette: thats the minimum i would ever attempt to cut something
07:02 PM roguish[m]: Lcvette: ok. i'll up the ante, and go for it......
07:02 PM Lcvette: anything less and its doing more rubbing than cutting
07:02 PM Lcvette: start with 0.002"
07:02 PM Lcvette: work up
07:02 PM Lcvette: i think youll find you actually have a better ccolor chip, not burnt looking, more silver
07:03 PM Lcvette: JamesW: if you have the power go for all you can
07:03 PM Lcvette: on my little mill I cut 6061 with 0.004"
07:03 PM Lcvette: 5000rpm
07:03 PM roguish[m]: Lcvette: thanks again for the help and lesson.
07:03 PM Lcvette: 0.75" deep
07:04 PM Lcvette: 20% stepover
07:04 PM roguish[m]: anyway, it's 5, margarita time......
07:04 PM Lcvette: no worries, stainless is a tough nut to crack
07:04 PM Lcvette: party at roguishes house!
07:04 PM Lcvette: :D
07:04 PM Lcvette: \o/
07:05 PM Lcvette: roguish any coolant?
07:05 PM Lcvette: or airblast?
07:05 PM JamesW[m]: I tend to try for 0.05mm as a minimum.
07:05 PM Lcvette: airblast help with stainless
07:05 PM roguish[m]: oh, yeah, a heavy mist spray. lots of air.
07:05 PM Lcvette: thats damn close to 0,002"
07:06 PM Lcvette: ok good
07:06 PM Lcvette: then leter rip taterchip
07:06 PM JamesW[m]: I’m currently capped at 2800rpm so adjust feeds to get the right chip load
07:07 PM JamesW[m]: I hope post servo and spindle bearing upgrade I will be in the 4-5k band.
08:04 PM RacoonRider|MovT: hi all
08:05 PM RacoonRider|MovT: anyone atk?
08:07 PM JamesW[m]: Sort of. Dozing in recliner chair in the sun.
08:10 PM TurBoss: RacoonRider | MovT: hello whats ATK?
08:15 PM JamesW[m]: “At the keyboard”?
08:15 PM TurBoss: yes that what i think :D
08:29 PM RacoonRider|MovT: Yea at the keyboard
08:29 PM TurBoss: shoot
08:31 PM RacoonRider|MovT: i got my spindle ready and have a ration 2:1 or, if i change the pulley, 3:1 but my vfd and the motor running always at the same speed.
08:32 PM RacoonRider|MovT: now i search a way to handle that in the gcode. If i set a M3 S20000 the spindle runs only 10000. I have an encoder on the spindle.
08:33 PM RacoonRider|MovT: is there a way to do some "post math" with a M3 command?
08:34 PM TurBoss: i'm sorry I don't have a vfd on my little spindle never managed to configure thoose
08:34 PM RacoonRider|MovT: so if i set M3 S10000 the real command to the VFD should be M3 S20000 in case of the 2:1 ratio
08:35 PM TurBoss: how did you configured the spindle?
08:36 PM TurBoss: pncconf?
08:36 PM TurBoss: hal?
08:36 PM JamesW[m]: Assume you are controlling VFD with a 0/10v ?
08:36 PM RacoonRider|MovT: in the custom.hal its a Hitachi WJ200 2.2kw VFD
08:37 PM RacoonRider|MovT: the motor is a chinesium HF spindle with a pulley in the clamp
08:38 PM * RacoonRider|MovT uploaded an image: 72DE0A11-155A-4A92-B620-58D020012ADC_1_105_c.jpeg (180KB) < https://matrix.org/_matrix/media/r0/download/jauriarts.org/OGgvZcmuXDZOAhoKJuUKdrzs >
08:38 PM JamesW[m]: Do you have any feedback from spindle to LinuxCNC?
08:38 PM RacoonRider|MovT: yes the encoder on the left side
08:39 PM JamesW[m]: Ok. With encoder you could use the LinuxCNC spindle PID to control the speed.
08:39 PM JamesW[m]: That way it sorts out the gearing impact for you based on real speed feedback via the encoder
08:39 PM RacoonRider|MovT: yes but i control the VFD via Modbus
08:39 PM JamesW[m]: Oh
08:40 PM RacoonRider|MovT: you mean i need to control the VFD with the 10V input right?
08:40 PM JamesW[m]: So you set a frequency in modbus?
08:40 PM RacoonRider|MovT: yes
08:40 PM JamesW[m]: Same principle then.
08:41 PM RacoonRider|MovT: i use the WJ200 driver it comes with LinuxCNC
08:41 PM JamesW[m]: is it a continuous stream of speed commands?
08:41 PM RacoonRider|MovT: no
08:41 PM JamesW[m]: Poop
08:43 PM RacoonRider|MovT: i can change the input at the VFD to 10v but its not the real deal. If i can set a parameter like #SPINDLE_RATIO i can do the math in the driver itself
08:43 PM TurBoss: can you show the custom.hal?
08:43 PM TurBoss: or the relevan part
08:44 PM RacoonRider|MovT: sure
08:44 PM TurBoss: cool
08:44 PM RacoonRider|MovT: need a mom
08:44 PM TurBoss: ok
08:44 PM JamesW[m]: Does the modbus examples contemplate pid control?
08:45 PM TurBoss: http://linuxcnc.org/docs/devel/html/man/man9/wj200_vfd.9.html
08:45 PM TurBoss: this is the comp
08:47 PM * RacoonRider|MovT sent a long message: < https://matrix.org/_matrix/media/r0/download/matrix.org/UzsFTCNNMYybjZdvVzQMdKpt >
08:48 PM JamesW[m]: I recon you could hook up PID
08:48 PM TurBoss: ^
08:48 PM JamesW[m]: You have a frequency in pin. That can just be the output of the PID.
08:48 PM RacoonRider|MovT: that would be nice but how?
08:49 PM TurBoss: http://linuxcnc.org/docs/2.8/html/motion/pid-theory.html
08:49 PM TurBoss: :)
08:50 PM JamesW[m]: You would need to do the tuning work. But the result should be pid controls the speed and gear ratio is not relevant as it works out what frequency is needed to get the speed asked for.
08:50 PM JamesW[m]: Is what I have on my BF20. I’m controlling via voltage but it’s all the same from the PID angle. It just needs to know what scale it is working to.
08:51 PM RacoonRider|MovT: Yes the scale 1:1 is 3000-24000 rpm on the motor
08:52 PM RacoonRider|MovT: 2:1 is also 1500-12000
08:52 PM JamesW[m]: I have hi/low. 2800 or 1400
08:52 PM RacoonRider|MovT: i also have a 4:1 pulley for steel. Its 1000-6000 with lots of tourqe
08:53 PM JamesW[m]: Max. I dial up 800 one either ratio with M3 S800. Pid sorts it out from there.
08:54 PM RacoonRider|MovT: yea but i dont know how to fiddle that into the hal
08:54 PM TurBoss: http://linuxcnc.org/docs/devel/html/man/man9/pid.9.html this is the PID comp
08:56 PM TurBoss: RacoonRider | MovT: is the vel-cmd.-rps equal to the frequency?
08:56 PM TurBoss: spindle-vel-cmd-rps
08:57 PM * JamesW[m] posted a file: bf20.hal (15KB) < https://matrix.org/_matrix/media/r0/download/matrix.org/hbLNCAbaAJTAPUEXXLozQBKF >
08:58 PM RacoonRider|MovT: TurBoss yes
08:58 PM TurBoss: ok
08:59 PM RacoonRider|MovT: Its not the rpm
08:59 PM RacoonRider|MovT: if i set it to M3 S24000 vel-cmd-rps is 400
08:59 PM TurBoss: ah ok
08:59 PM * JamesW[m] sent a long message: < https://matrix.org/_matrix/media/r0/download/matrix.org/wEqUOufGWBIWVdgUwoXJiDBE >
08:59 PM TurBoss: !
09:01 PM JamesW[m]: net spindle-output => [HMOT](CARD0).7i76.0.0.spinout
09:02 PM JamesW[m]: in your setup you would send spindle-output to your modbus Hz-In pin
09:03 PM JamesW[m]: remember that these settings are what define and bound the pid:
09:03 PM * JamesW[m] sent a long message: < https://matrix.org/_matrix/media/r0/download/matrix.org/ttlwbfTwxMrEHAvDLmifgaeW >
09:05 PM RacoonRider|MovT: i guessed the feedback will be the hm2_7i76e.0.7i76.0.0.encoder.00.velocity
09:06 PM JamesW[m]: I guess you have two paths you could follow. 1. work on the PID angle or 2. do some hal work to essentially have a gear setting somewhere (GUI?) and have that tell HAL how to scale your 0-60Hz band (or whatever you are using) to get desired speeds.
09:07 PM RacoonRider|MovT: The band is 50-400Hz
09:08 PM JamesW[m]: I use a low pass filter to stop rpm jitter. It also scales the from rps to rpm
09:08 PM * JamesW[m] sent a long message: < https://matrix.org/_matrix/media/r0/download/matrix.org/SeeJVVRfhWsPllgbSFjFOIgA >
09:09 PM JamesW[m]: sorry - stupid formating and I don't now how to get it to quote code.
09:09 PM RacoonRider|MovT: no pro its ok
09:10 PM JamesW[m]: have a look in the hal file I posted
09:10 PM * TurBoss sent a long message: < https://matrix.org/_matrix/media/r0/download/matrix.org/ZZPyPZZMRdLxsSNrbLxIwMOz >
09:10 PM JamesW[m]: it has the full picture. Just remember mine is setup for a single ended encoder and voltage control
09:10 PM * JamesW[m] sent a long message: < https://matrix.org/_matrix/media/r0/download/matrix.org/DacYnXVoTHtrQrKDFsIPfjto >
09:11 PM TurBoss: ```
09:11 PM TurBoss: example
09:11 PM TurBoss: ```
09:11 PM TurBoss: tripe quote
09:11 PM JamesW[m]: just tried the three ' and still didnt do it
09:11 PM TurBoss: `
09:11 PM TurBoss: this one
09:11 PM TurBoss: the angled one
09:11 PM * JamesW[m] sent a long message: < https://matrix.org/_matrix/media/r0/download/matrix.org/WFBaoEFNumSutLkRbdjVOmpj >
09:12 PM JamesW[m]: ahhhh! thanks
09:13 PM JamesW[m]: I used the rpm-abs into the PID and the filtered on to use in the GUI
09:13 PM JamesW[m]: one==on
09:14 PM RacoonRider|MovT: yes i got it. the ini would be helpful for some things.
09:15 PM * JamesW[m] posted a file: bf20.ini (8KB) < https://matrix.org/_matrix/media/r0/download/matrix.org/gwjTgZYQGJjygoTQWXEXBcRg >
09:15 PM RacoonRider|MovT: encoder.scale ist the ppr fro the encoder right?
09:15 PM RacoonRider|MovT: thnx
09:15 PM RacoonRider|MovT: *edit:* ~~encoder.scale ist the ppr fro the encoder right?~~ -> encoder.scale is the ppr fro the encoder right?
09:16 PM JamesW[m]: think so. been a while. My "encoder" is a hall effect sensor that triggers 4 times per revolution.
09:16 PM JamesW[m]: hence the odd looking scale
09:17 PM JamesW[m]: and there is a quirk where single ended encoders come through with negative numbers hence the scale is negative to counter that
09:17 PM RacoonRider|MovT: yea my encoder i use has 4096 pulses per revolution 😭
09:17 PM RacoonRider|MovT: i can set it lower only with an expensive interface
09:19 PM RacoonRider|MovT: its a single ended encoder
09:19 PM RacoonRider|MovT: it have only 5 wires a+ b+ z+ gnd and vcc
09:19 PM JamesW[m]: my suggestion would be to setup with blank PID get the connections working then get cute adjusting the PID for control.
09:20 PM JamesW[m]: k
09:20 PM JamesW[m]: you hooking up to a 7i76e or equivalent?
09:21 PM RacoonRider|MovT: yes its a 7i76e
09:21 PM RacoonRider|MovT: thats the encoder https://www.ifm.com/ch/en/product/RV3100
09:21 PM RacoonRider|MovT: you can see it at the left side of the spindle housing
09:21 PM RacoonRider|MovT: you can see it at the left side of the spindle housing
09:21 PM JamesW[m]: yup
09:23 PM RacoonRider|MovT: yes i will try it with your files and will try to understand what i am doing there 🙂
09:24 PM JamesW[m]: like anything there are different ways to skin a cat. And this is just how I did it.
09:24 PM JamesW[m]: getting the PID wired up is not too hard. Getting it tuned to behave they way you want can be a bit more entertaining
09:25 PM RacoonRider|MovT: thanks a million for your help! i will try to skin it in the same way 🙂
09:25 PM TurBoss: poor cat lol
09:25 PM TurBoss: :P
09:25 PM RacoonRider|MovT: yes i can imagine
09:25 PM RacoonRider|MovT: 🙂
09:26 PM JamesW[m]: I have an axis setup I used to help with PID tuning. I'll go zip that up and post it here as well.
09:26 PM RacoonRider|MovT: if i tune it right the spnindle will hold the rpm under heavy workload right?
09:28 PM JamesW[m]: correct
09:28 PM JamesW[m]: it will self adjust to maintain set speed
09:28 PM RacoonRider|MovT: thats a nice benefit
09:29 PM JamesW[m]: like any PID it will seek a little bit. i.e. if you set 2000rpm it will seek between 1950 to 2050 or some range.
09:29 PM JamesW[m]: the better you get your tuning the more stable it will be.
09:30 PM RacoonRider|MovT: yea i will start today. Need to slitsaw my iso20 clamp and harden it than i assemble the spindle and start the work
09:30 PM JamesW[m]: but there needs to be a little instability to allow it to seek to a new position quickly.
09:31 PM RacoonRider|MovT: yes the hysteresis