#flex-dev Logs

Nov 04 2025

#flex-dev Calendar

04:19 AM Tom_L: morning
04:21 AM JT-Chicken: morning
04:25 AM Tom_L: 55F - 73F gonna be a nice day
04:26 AM JT-Chicken: 41f atm
08:37 AM JT-Cave: ok to build
09:41 AM lcnc-relay: <AllAboutJake@> can you access any pin in the hal? Tried this and it didn't work. I understand that it prepends "flexgui." to the pin, so I just added a "net homedx flexgui.joint.0.homed <= joint.0.homed" to my postgui hal, and it works, but wasn't sure if there's a btter way
09:41 AM lcnc-relay: <AllAboutJake@> https://jauriarts.org/_heisenbridge/media/jauriarts.org/ctjUmEgjTnULrRqkpvpZmqku/diH5WaRirrc/image.png
09:42 AM JT-Shop: yes you have access to any hal pin with flex
09:43 AM JT-Shop: is flexgui.joint.0.homed a hal label or something?
09:44 AM lcnc-relay: <AllAboutJake@> well "joint.0.homed" is what I was trying to expose, but I had to create an entry in the postgui hal file to map that to "flexgui.joint.0.hal"
09:44 AM lcnc-relay: <AllAboutJake@> * "flexgui.joint.0.homed"
09:49 AM JT-Shop: I don't follow what you mean by expose joint.0.homed
09:49 AM JT-Shop: that pin is there if you have a joint 0
09:54 AM lcnc-relay: <AllAboutJake@> I was setting up a led in the UI to show "joint.0.homed" from the hal as above. it didn't work. Then I read in the docs:
09:54 AM lcnc-relay: "A QLabel can be used to monitor HAL pins. HAL connections must be made in the post gui HAL file. The pin_name used will create a HAL pin prefixed with flexhal. A pin_name of my-reader would be in HAL flexhal.my-reader."
09:54 AM lcnc-relay: So I added this to my postgui:
09:54 AM lcnc-relay: "net homed-x flexhal.joint.0.homed <= joint.0.homed"
09:54 AM lcnc-relay: Then it works as expective.
09:55 AM lcnc-relay: <AllAboutJake@> So I wanted to confirm that only "flexhal.*" prefixed pins in the post gui HAL file can be exposed to the GUI and you are required to map them in this way.
09:55 AM JT-Shop: ah ok
09:57 AM JT-Shop: yes only flexhal pins part of the gui
09:57 AM JT-Shop: are part of
10:09 AM lcnc-relay: <AllAboutJake@> cool. can you do a LED button for homing such that the button shows a green led if homed, and red if not, and if you click the button it triggers the homing operation for that joint?
10:11 AM lcnc-relay: <AllAboutJake@> seems like you can't just add dynamic properties to a "home_pb_0" button
10:12 AM JT-Shop: I'd have to check on that
10:14 AM JT-Shop: yup that is not available yet but it's a good idea to have led home buttons
10:16 AM lcnc-relay: <AllAboutJake@> got it. yeah. I think so. I wanted to replace the "homed" indicators near the DRO with buttons that both let you home a specific axis, as well as show the the state of being homed with an LED
10:17 AM lcnc-relay: <AllAboutJake@> also I was going to add MDI buttons near the DRO axis that execute "G10 L20 P0 X0" etc to let you zero out an axis.
12:10 PM Tom_L: JT-Shop, good to go for a build?
12:10 PM Tom_L: leds seem to becoming more popular now
12:13 PM lcnc-relay: <roguish> fyi.....I like leds in the gui
12:13 PM lcnc-relay: <roguish> give visible status
12:13 PM Tom_L: after all it is getting closer to christmas... the light season
12:16 PM Tom_L: should get my touch screen today sometime then i can start testing touch guis
12:16 PM Tom_L: need to work on the metric config first
12:17 PM Tom_L: all the metric probe routines have been tested and pushed, just the ops are left
12:38 PM Tom_L: PR #382
12:43 PM JT-Cave: https://pasteboard.co/gPHXVWlY0dAp.png
12:43 PM JT-Cave: https://pasteboard.co/pry2gUY4ukUI.png
12:45 PM Tom_L: nice
12:48 PM JT-Cave: https://gnipsel.com/linuxcnc/flexgui/controls.html#led-buttons
12:55 PM Tom_L: is this led just for those buttons?
12:55 PM Tom_L: and
12:55 PM Tom_L: do i need to change my current example dynamic properties for this?
12:59 PM JT-Shop: the control led buttons only need one dynamic property to function
12:59 PM JT-Shop: not sure what you're asking
01:00 PM Tom_L: yeah gimme a sec then i can focus
01:01 PM JT-Shop: damn jap beetles are back
01:03 PM Tom_dev: what i was asking is with the current led buttons: estop, pwr and probe enable, has this changed any: http://tom-itx.no-ip.biz:443/~webpage/cnc/JT-SHOP/flexgui/estop_led.png
01:03 PM Tom_dev: well, those are the only ones i'm using anyway currently
01:04 PM Tom_dev: it seems like with just the led_indicator property they use defaults you have already set
01:04 PM JT-Shop: nothing to change there
01:05 PM Tom_L: ok great
01:05 PM JT-Shop: all I added was the home all button to that group of led controls
01:05 PM Tom_L: ahh ok
01:05 PM Tom_L: i may eventually add the led to it also
01:06 PM Tom_L: got a couple other fires to extinguish first
01:06 PM JT-Shop: nap time here
01:06 PM Tom_L: agree
04:14 PM * Tom_L waits for rdtsc to pop in
05:02 PM Tom_L: rdtsc, how did you handle doubletap on the waveshare?
05:03 PM Tom_L: other than that i think it will do what i need done
05:30 PM lcnc-relay: <AllAboutJake@> JT-Cave: Is it possible to do individual home_pb_(0-n) as well? Wanted to use these to replace the homing indicators in the DRO, making them both indicators and buttons to trigger individual joint homing
05:32 PM JT-Shop: yup I can do that in the morning
05:35 PM lcnc-relay: <AllAboutJake@> Cool. I’m just getting into figuring out how this all works. But starting to get the idea
05:51 PM rdtsc-w: Tom, think there was no solution for double-tap at that time, may have changed recently
06:03 PM Tom_L: so you can't really do a touch only with this
06:18 PM Tom_L: seems if you put a launcher on the bar it works ok
06:19 PM Tom_L: increase the pixel size a bit on the bar
06:55 PM Tom_L: JT-Cave, can you save the location of the number keypad popup
06:55 PM Tom_L: as well as the other keyboard helps
06:56 PM Tom_L: rdtsc, it's interesting to note that double tap works in the flexgui but not in debian12 itself