#linuxcnc Logs

Feb 07 2024

01:28 AM Deejay: moin
03:42 AM -!- #linuxcnc mode set to +v by ChanServ
06:21 AM JT-Cave: what did it do?
06:22 AM Tom_L: gotta leave early today... sry
06:23 AM Tom_L: didn't really get a chance to see, reinsstalled os 3x and it's not on the menu
06:23 AM Tom_L: later
07:26 AM JT-Cave: https://www.youtube.com/watch?v=iwpj446tLZg
08:06 AM * JT-Cave starts his chicken day
08:40 AM -!- #linuxcnc mode set to +v by ChanServ
01:30 PM Tom_L: JT-Shop, are those buttons just the style sheet or did you start another gui?
01:30 PM JT-Shop: which buttons?
01:30 PM Tom_L: in the video
01:30 PM JT-Shop: that's the touch option
01:30 PM JT-Shop: INPUT=TOUCH
01:31 PM Tom_L: are you running this on your bp?
01:31 PM JT-Shop: yup
01:31 PM Tom_L: i gotta figure out what's goin on with the install now
01:31 PM JT-Shop: adding a MDI button is pretty easy :)
01:31 PM Tom_L: looked like it
01:31 PM JT-Shop: it will be the same for a HAL button
01:32 PM Tom_L: maybe mine is redundant then
01:32 PM JT-Shop: a guy on the forum is looking at jet :)
01:33 PM JT-Shop: he asked about hal and that's what made me look into it
01:33 PM Tom_L: want me to push it or not?
01:33 PM JT-Shop: let me see where I'm at first
01:33 PM JT-Shop: I think I pushed all my changes
01:34 PM Tom_L: i still don't have qt designer working but i tested the coolant buttons
01:34 PM JT-Shop: cool
01:34 PM JT-Shop: what's up with designer?
01:35 PM Tom_L: no clue
01:35 PM Tom_L: i gotta find the ssd first
01:35 PM Tom_L: it _might_ be across the street
01:37 PM Tom_L: i used the lcnc 12 iso but didn't like the desktop so i got a web install cd and redid that
01:37 PM JT-Shop: did toss it out the window?
01:37 PM Tom_L: turns out the ssd is ok, it was a cable i think
01:37 PM Tom_L: i wanted to
01:38 PM Tom_L: so now i got mate back and installed a few things but designer isn't on the menu
01:38 PM -!- #linuxcnc mode set to +v by ChanServ
01:39 PM Tom_L: if i run dpkg-buildpackage will that install it if it's not there?
01:40 PM Tom_dev: are you using pyqt5 or 6?
01:43 PM JT-Shop: I'm running pyqt6 for the gui but qt5 designer, I couldn't get qt6 designer in debian
01:44 PM Tom_dev: maybe that's my problem
01:45 PM Tom_dev: so i need python3, python3-pyqt5 or 6? and the pyqtx-dev-tools?
01:45 PM JT-Shop: https://gnipsel.com/linuxcnc/flex/designer.html
01:45 PM Tom_dev: anything else?
01:45 PM JT-Shop: if you install jet it pulls in everything but dev tools
01:46 PM JT-Shop: actually it Depends: python3 (>=3.6), python3-pyqt6, pyqt6-dev-tools
01:46 PM JT-Shop: hmm
01:46 PM lcnc-relay: <schoch_> https://youtube.com/shorts/nmgSmUaQEDE?feature=share
01:46 PM Tom_dev: this is 3.11.2
01:47 PM JT-Shop: but qt6 dev tools does not have designer
01:47 PM Tom_dev: no wonder then
01:47 PM Tom_dev: i had been using 5
01:47 PM JT-Shop: qttools5-dev-tools had designer
01:48 PM JT-Shop: pyqt6-dev-tools has the uic tool
01:48 PM JT-Shop: which is required to run the gui
01:49 PM Tom_dev: whats uic?
01:50 PM Tom_dev: it says i have the pyqt5-dev-tools installed
01:51 PM Tom_dev: but it doesn't appear that they are
01:51 PM JT-Shop: pyqt5-dev-tools is not where designer is
01:52 PM JT-Shop: https://gnipsel.com/linuxcnc/flex/designer.html
01:52 PM Tom_dev: ok
01:53 PM JT-Shop: nice most of the images in the docs are missing...
01:53 PM Tom_dev: saw that
01:55 PM JT-Shop: it's like wtf happened to them lol
01:55 PM Tom_dev: i'd just clicked save and the drive crapped out on me
01:56 PM Tom_dev: there now designer is on the menu
01:57 PM Tom_dev: clipper1
01:58 PM Tom_dev: ok gonna stuff this in the dev pc and see what happens
02:00 PM Tom_L: i saw some 250gb drives for like $30 and was gonna get a few but they're sold out
02:02 PM Tom_L: oh, JT-Shop what was that grub editor you mentioned?
02:04 PM JT-Shop: Grub Customizer is a graphical interface to configure GRUB2
02:04 PM Tom_L: hmm there's something going on with that MB. it won't boot the ssd
02:04 PM JT-Shop: grub-customizer
02:04 PM Tom_L: thanks
02:04 PM -!- #linuxcnc mode set to +v by ChanServ
02:05 PM * JT-Shop goes to the other shop to try and get a bit of work done
02:05 PM Tom_dev: should i push this or wait?
02:06 PM Tom_dev: or just keep it local
02:16 PM JT-Cave: everything is up to date here
02:19 PM Tom_dev: ok, but now i'm messin with that button mdi think :)
02:19 PM Tom_dev: thing
02:21 PM JT-Cave: lol ok
02:24 PM Tom_dev: i tried an M9 as the mdi command and it didn't turn off the coolant
02:32 PM Tom_L: JT-Cave, http://tom-itx.no-ip.biz:81/~webpage/cnc/JT-SHOP/JET/jet_mdi_command.png
02:32 PM lcnc-relay: <darrick255#0> Hey, im having issues running vectric vcarve through wine on my rtai bookworm based Linux CNC install (seems to work fine with a regular kernel)
02:32 PM lcnc-relay: <darrick255#0>
02:32 PM lcnc-relay: <darrick255#0> Is there any resources on getting this configured properly. I have had poor luck google this
02:33 PM lcnc-relay: <darrick255#0> * Hey, im having issues running vectric vcarve through wine on my rtai bookworm based Linux CNC install (seems to work fine with a regular kernel)
02:33 PM lcnc-relay: <darrick255#0>
02:33 PM lcnc-relay: <darrick255#0> Is there any resources on getting this configured properly. I have had poor luck finding help through web searching.
02:46 PM JT-Shop: m9 works for me
02:46 PM Tom_dev: i must be doing something wrong
02:46 PM Tom_dev: i'm gonna push the coolat stuff shortly
02:46 PM Tom_dev: coolant
02:46 PM JT-Shop: looks right
02:46 PM lcnc-relay: <unterhausen> I never thought of the kernel being an issue with wine. You could try a vanilla kernel. There is no reason why you couldn't have both on the same computers
02:47 PM JT-Shop: I'll have to look at it in the morning
02:47 PM lcnc-relay: <unterhausen> Admittedly, I could never get wine to work for the programs I wanted to use.
02:54 PM Tom_dev: ok #6 in jet is there
02:56 PM JT-Shop: ok
02:56 PM JT-Shop: did you sort out m9?
02:57 PM Tom_dev: no, i need a break
02:57 PM JT-Shop: ok
03:04 PM Tom_L: i think one of my sata ports is bad
03:08 PM Tom_L: guess i'll try the next port a while and see
03:12 PM Tom_L: i'll test mdi after bit
03:15 PM JT-Cave: crap the dro is not updating anymore in real time...
03:17 PM Tom_L: dro?
03:17 PM Tom_L: oh, the axis?
03:23 PM Tom_L: ssd seems ok on that port so far
05:05 PM lcnc-relay: <mikemader#0> I currently have LinuxCNC 2.8.4 installed on Debian 10. Do I need to do a clean install of Debian 12 to upgrade to LinuxCNC 2.9.2, or can I upgrade the OS then upgrade LinuxCNC?
05:09 PM Roguish_desk: a clean install is best. not really that difficult. you can upgrade the OS, but it can get messy
05:10 PM Roguish_desk: https://gnipsel.com/linuxcnc/index.html
05:11 PM Tom_L: it would be easier to install the linuxcnc debian2 iso
05:11 PM Tom_L: http://linuxcnc.org/downloads/
05:12 PM lcnc-relay: <mikemader#0> Thank you
05:13 PM Tom_L: do the graphic install
05:13 PM Tom_L: it has several options to choose from
05:32 PM JT-Shop: well reload seems to be working as expected...
05:33 PM Tom_L: what was wrong with the dro?
05:34 PM JT-Shop: it doesn't update during a mdi
05:34 PM JT-Shop: until the mdi is done
05:34 PM Tom_L: oh
05:34 PM Tom_L: did it break or did it ever update then?
05:35 PM JT-Shop: I had it working this morning...
05:35 PM -!- #linuxcnc mode set to +v by ChanServ
05:36 PM Tom_L: i left the tab in the wrong spot again too :)
05:37 PM JT-Shop: yup and you forgot to set the layout but I fixed all that
05:37 PM solarwind: So getting a nut off a bolt deep down in a hard to reach spot is a solved problem - just use an extension bar on your ratchet
05:37 PM JT-Shop: going to rename the project to flexgui
05:37 PM solarwind: now how do we get the nut back on?
05:38 PM Tom_L: glue it to a stick
05:38 PM JT-Shop: you need a phd to know that
05:38 PM solarwind: the socket doesn't hold the nut
05:38 PM JT-Shop: or common sense
05:38 PM JT-Shop: sure it does
05:38 PM solarwind: tiny magnet?
05:38 PM Tom_L: double back tape on a stick
05:38 PM JT-Shop: bit of paper
05:38 PM Tom_L: bit of common sense
05:38 PM JT-Shop: yup
05:39 PM Tom_L: do it upside down and it won't fall into the hole
05:39 PM solarwind: it's all fun and games until you drop a 5mm nut
05:39 PM JT-Shop: use a bit of paper to wedge the nut in the socke
05:39 PM Tom_L: i've done that too
05:39 PM Tom_L: just not enough where you lose the socket too
05:39 PM JT-Shop: t
05:40 PM solarwind: Can I patent that nut-wedgin' paper?
05:41 PM JT-Shop: sure democrats will allow that but then they will ban it...
05:41 PM solarwind: Is it killing that many trees?
05:41 PM JT-Shop: they don't care
05:45 PM XXCoder: I highly doubt that jr
05:45 PM XXCoder: jt
05:45 PM Tom_L: i still can't figure out why the button doesn't work
05:46 PM JT-Shop: jr left the building
05:46 PM JT-Shop: which button?
05:47 PM Tom_L: the m9 thing
05:47 PM Tom_L: i even wrote down the steps (i think)
05:48 PM Tom_L: i may have seen a hint
05:49 PM * JT-Shop goes to tuck the chickens in
05:50 PM Tom_L: nope
06:12 PM JT-Cave: crap I don't know what's screwed up the dro update now...
06:14 PM Tom_L: i just realized i don't need the mdi_command in there since i'm using the emc function calls
06:14 PM -!- #linuxcnc mode set to +v by ChanServ
06:15 PM Tom_dev: parent.command.flood(emc.FLOOD_OFF)
06:15 PM Tom_dev: instead of
06:15 PM Tom_dev: parent.command.mdi(mdi_command)
06:17 PM Tom_dev: but i want to read the value of emc.stat.flood but all i get back is: Flood: <member 'flood' of 'linuxcnc.stat' objects>
06:17 PM Tom_L: how do i read the value at instead?
06:17 PM Tom_dev: print(f'Flood: {emc.stat.flood}')
06:18 PM JT-Cave: flood
06:18 PM JT-Cave: (returns integer) - Flood status, either FLOOD_OFF or FLOOD_ON.
06:18 PM JT-Cave: emc.flood not stat
06:18 PM Tom_dev: i was just getting ready to say that
06:18 PM Tom_dev: oh
06:18 PM JT-Cave: stat returns the status
06:19 PM Tom_dev: but that's listed under linuxcnc.stat attributes
06:19 PM JT-Cave: emc.flood is the constant
06:19 PM Tom_dev: so damn picky!
06:19 PM JT-Cave: lol
06:19 PM JT-Cave: hmm
06:20 PM JT-Cave: emc.stat.flood will return like 0 or 1
06:20 PM Tom_dev: i'm gonna remove that mdi_command = f'M8' etc
06:20 PM Tom_dev: right that's what i expected
06:20 PM JT-Cave: to get the name you need to use emc.FLOOD_OFF
06:20 PM Tom_dev: next, how do you reset the state of the button push
06:21 PM JT-Cave: when the mdi command finishes the button resets
06:21 PM Tom_dev: ie if flood is on but it was because of an MDI command not the button, the button should be updated to reflect the actual state
06:21 PM Tom_dev: not if it's set from another source
06:21 PM JT-Cave: ah you have to do that in status.py
06:22 PM JT-Cave: https://github.com/jethornton/jet/blob/0.2.0/jet/src/libjet/status.py
06:23 PM Tom_dev: print(f'Flood: {emc.flood}')
06:23 PM Tom_dev: ^^^^^^^^^
06:23 PM Tom_dev: AttributeError: module 'linuxcnc' has no attribute 'flood'
06:23 PM JT-Cave: right
06:23 PM JT-Cave: flood
06:23 PM JT-Cave: (returns integer) - Flood status, either FLOOD_OFF or FLOOD_ON.
06:24 PM Tom_dev: is that int or bool?
06:24 PM Tom_dev: int
06:25 PM Tom_dev: so it should return a number 0 or 1
06:25 PM JT-Cave: some number yea
06:25 PM Tom_dev: what's wrong with my syntax then?
06:25 PM Tom_dev: rint(f'Flood: {emc.flood}')
06:25 PM Tom_dev: p
06:26 PM JT-Cave: flood
06:26 PM JT-Cave: (returns integer) - Flood status, either FLOOD_OFF or FLOOD_ON.
06:26 PM JT-Cave: no constant flood
06:26 PM JT-Cave: flood
06:26 PM JT-Cave: <JT-Cave> (returns integer) - Flood status, either FLOOD_OFF or FLOOD_ON.
06:27 PM JT-Cave: emc.stat.flood returns either FLOOD_OFF or FLOOD_ON
06:27 PM Tom_dev: i defined those constants at the top though
06:27 PM JT-Cave: so the constants are either FLOOD_OFF or FLOOD_ON
06:27 PM JT-Cave: those are defined by emc
06:28 PM Tom_dev: but constants are replaced by their value at compile time
06:28 PM Tom_dev: in my experience
06:28 PM JT-Cave: https://github.com/jethornton/jet/blob/0.2.0/jet/src/libjet/startup.py#L120
06:29 PM JT-Cave: python is not compiled
06:29 PM Tom_dev: what's the pyc file then?
06:29 PM Tom_dev: not here but i've seen those
06:30 PM JT-Cave: it's a how do I describe it a machine code file but not compiled like c
06:30 PM JT-Cave: see you in the am
06:30 PM Tom_dev: interpreted not compiled
06:30 PM Tom_dev: later
06:31 PM Tom_dev: dbase was interpreted
06:31 PM Tom_dev: clipper was compiled
06:31 PM Tom_dev: and produced an executable
06:31 PM Tom_dev: ok
07:25 PM {HD}_ is now known as {HD}________
09:08 PM solarwind: https://www.youtube.com/watch?v=CglNRNrMFGM Title: dweeb who likes to replicate chemistry experiments and call himself a chemist discovers that you need a mold to compress stuff in a hydraulic press
09:09 PM solarwind: also, plain hardwood of that thickness can stop a 0.22 LR round
09:10 PM solarwind: Alternate titles: dweeb pays $5,000 CAD for a cheap heated hydraulic press
09:32 PM CaptHindsight: cringe worthy
09:32 PM XXCoder: dropped his channels a while ago
09:35 PM -!- #linuxcnc mode set to +v by ChanServ
10:39 PM lcnc-relay: <big_kevin420> i need to use that more, dweeb
11:31 PM -!- #linuxcnc mode set to +vv by tantalum.libera.chat
11:31 PM -!- #linuxcnc mode set to +v by tantalum.libera.chat
11:33 PM -!- #linuxcnc mode set to +v by ChanServ
11:37 PM fdarling: I would like to home my toolchanger as part of the homing process (ideally almost as if it were another axis), does anyone have any suggestions? Otherwise I have to hack in that it homes the first time it is used, which wastes time...
11:38 PM fdarling: (or it automatically homes after the machine is homed, so it will always happen after)