#linuxcnc Logs
May 04 2024
#linuxcnc Calendar
04:45 AM rigid: jpa-: fyi, I did some experiments with that 26k DPI optical mouse and it's precision is terrible. It drops steep after 1800 dpi. The material seems to matter a lot (best results with fine grit polishing sandpaper). Accuracy is amazing tho.
04:57 AM rigid: The homing race condition in linuxcnc also makes a testrun painfully long for averaging. I had to put sleep()s everywhere.
05:02 AM JT-Cave: morning
05:15 AM Tom_L: morning
05:16 AM Tom_L: was the loadrt flexhal the part that lets postgui see the pins?
05:17 AM Tom_L: the pins aren't visible there in mine
05:21 AM -!- #linuxcnc mode set to +v by ChanServ
05:22 AM Tom_dev: Note: Using POSIX realtime
05:22 AM Tom_dev: postgui_tom.hal:5: Pin 'flexhal.test_pin1' does not exist
05:23 AM travis_farmer: Morning
06:13 AM JT-Cave: today's puzzle connect to a hal pin...
06:15 AM Tom_L: JT-Cave, what was that file you were trying to load?
06:17 AM JT-Cave: puzzle solved... wow that was easy
06:17 AM JT-Cave: which file?
06:22 AM JT-Cave: loadrt flexhal was just a test while trying to finger out what needs to happen
06:52 AM rdtsc_away is now known as rdtsc
06:53 AM rdtsc: morning gents.
06:57 AM JT-Cave: Tom_L, https://gnipsel.com/linuxcnc/flexgui/hal.html
07:03 AM rdtsc: Looks like there are some libc updates available for Rpi bookworm this morning.
08:29 AM rdtsc is now known as rdtsc_away
08:33 AM lcnc-relay: <JT> Yo
09:04 AM JT-Cave: yo
09:09 AM Tom_L: what needs to happed for postgui to see the pins?
09:13 AM rdtsc_away is now known as rdtsc
09:13 AM Tom_L: JT-Cave, can you discard my last pr and i'll fix the ui name change and post it all at once
09:18 AM Tom_L: feed hold starts up pushed now. is that intentional?
09:18 AM Tom_L: and you push it and flex crashes
09:19 AM Tom_L: one sec..
09:28 AM Tom_L: reinstalled flexgui and it's ok now, it must not have installed right the first round
09:29 AM Tom_L: no.. with feed hold named: feed_hold_enable_pb flex crashes here
09:29 AM Tom_L: with the old name: feed_hold_pb it works
09:29 AM Tom_L: i sudo removed flexgui and installed 0.4.0 and that's what i get
09:32 AM Tom_L: yes, line 328 commands.py needs a look at
09:33 AM JT-Shop: opps
09:34 AM JT-Shop: Tom_L, if a post gui file is defined in the ini then flex will load it
09:34 AM Tom_L: ok
09:34 AM Tom_L: i'll test that after bit too
09:34 AM Tom_L: i have one ready
09:35 AM JT-Shop: let me fix the issue with feed hold before building
09:35 AM Tom_L: yeah, if i have any pending pr just discard them all and i'll send a fresh tom.ui etc
09:36 AM JT-Shop: ok
09:36 AM JT-Shop: no open pr's
09:36 AM Tom_L: i tried discarding here... it must have worked
09:37 AM Tom_L: all i need is to edit that one line?
09:37 AM JT-Shop: I'll fix the feed hold in a few
09:37 AM Tom_L: i'm just testing it here
09:38 AM JT-Shop: yup just fix the widget name
09:38 AM Tom_L: yeah that works but it still starts up depressed
09:39 AM Tom_L: i dunno what the default should be...
09:40 AM JT-Shop: https://gnipsel.com/linuxcnc/flexgui/controls.html
09:40 AM JT-Shop: that's because the default state of M53 is on
09:40 AM Tom_L: ok
09:40 AM JT-Shop: hmm I must not have uploaded the new doc page
09:41 AM Tom_L: yeah i ws looking and didn't see it there
09:43 AM -!- #linuxcnc mode set to +v by ChanServ
09:43 AM Tom_dev: Note: Using POSIX realtime
09:43 AM Tom_dev: postgui_tom.hal:5: Pin 'halui.mdi-command-00' does not exist
09:43 AM Tom_dev: umm... yes it does
09:44 AM Tom_dev: [HALUI]
09:44 AM Tom_dev: MDI_COMMAND = G10 L20 P1 X0
09:44 AM Tom_dev: MDI_COMMAND = G10 L20 P1 Y0
09:44 AM Tom_dev: MDI_COMMAND = G10 L20 P1 Z0
09:49 AM Tom_L: copied from my working mill config
09:50 AM JT-Cave: did you copy the part that loads halui?
09:50 AM Tom_L: i may not have a tom.hal
09:51 AM JT-Cave: HALUI = halui - adds the HAL user interface pins.
09:51 AM JT-Cave: in hal
09:51 AM Tom_L: in postgui?
09:52 AM JT-Cave: 2.7. [HAL] section
09:52 AM JT-Cave: http://linuxcnc.org/docs/stable/html/config/ini-config.html#sub:ini:sec:hal
09:53 AM Tom_L: yeah it works
09:54 AM Tom_L: x axis went to 0 with the button
09:54 AM JT-Cave: https://pasteboard.co/LqJ44kwbGom4.png
09:55 AM JT-Cave: did you see https://gnipsel.com/linuxcnc/flexgui/hal.html
09:56 AM Tom_L: i didn't scroll down but i see now :)
09:57 AM JT-Cave: if you get a change follow step by step and create a new pin and see if I missed anything
09:57 AM Tom_L: why is the property pin_0 and function hal-test-01? they don't have to be the same name?
09:58 AM Tom_L: i'll test that later i think i'm about to be interupted for a shopping trip
09:58 AM JT-Cave: property function must be hal_pin
09:58 AM Tom_L: right
09:59 AM JT-Cave: the pin_ property name is what flex looks for to make the pin
09:59 AM Tom_L: property name pin_0 and below that pin_0 has halpin as hal-test-01, HAL_BIT.....
09:59 AM Tom_L: they don't have to be the same name then?
09:59 AM JT-Cave: they?
09:59 AM Tom_L: just a sec
09:59 AM JT-Cave: k
10:02 AM Tom_L: http://tom-itx.no-ip.biz:81/~webpage/cnc/JT-SHOP/flexgui/hal_page.png
10:02 AM Tom_L: pin_0 has hal-test-01
10:02 AM Tom_L: they don't have to be the same name?
10:03 AM JT-Cave: no the property name must start with pin_ the pin name can be anything you want
10:03 AM Tom_L: pin_0 has hal-test-01 instead of hal-test-01 pin_0?
10:03 AM Tom_L: ok
10:03 AM JT-Cave: flex finds properties that start with pin_ and creates the pin using the information in the value
10:03 AM rdtsc is now known as rdtsc_away
10:03 AM Tom_L: so hal-test-01 is for the user
10:04 AM JT-Cave: the pin name will be flexhal.hal-test-01
10:04 AM Tom_L: it's important to know since it's tied to a nuclear missle!
10:04 AM JT-Cave: and it will be a bit type with a direction of out
10:05 AM JT-Cave: but you need to have both keys...
10:05 AM Tom_L: gotcha
10:05 AM Tom_L: first glance the page looks fine but i'll walk thru and create one later on
10:06 AM JT-Cave: scroll down and you can see the flexhal pins
10:06 AM Tom_L: i need to add a couple more for tom.ui anyway
10:06 AM Tom_L: right
10:07 AM Tom_L: i didn't look but did you mention the HALUI = HALUI line for posgui?
10:07 AM JT-Cave: the cat has a hematoma in her ear and is getting surgery today...
10:07 AM JT-Cave: nope, that's emc
10:07 AM Tom_L: ok
10:09 AM JT-Cave: I have a box turtle that walked into the hot wire and got electrocuted, now I have to wade through the weeds to move it away from the chicken yard
10:09 AM Tom_L: so you fixed the feed hold typo.. am i waiting for anything else?
10:09 AM JT-Cave: everything that I know of works, just waiting on you to break something :)
10:09 AM rdtsc_away is now known as rdtsc
10:10 AM * JT-Cave wanders out to the machine shop for a while
10:10 AM Tom_L: plotter :)
10:13 AM JT-Cave: oh yea there something wrong with mdi if you do a m code
10:21 AM Tom_L: i'm going to put my halshow preferences file in the examples so ppl can see all the buttons when they start hal
10:28 AM JT-Shop: ok, and I think I know why m codes that don't cause motion don't update the mdi list
10:28 AM Tom_L: JT-Cave, PR #18, new deb & updated tom.ui with example hal & posgui
10:28 AM JT-Shop: ok
10:28 AM Tom_L: and the halshow preference file
10:28 AM Tom_L: to show my pins
10:29 AM Tom_L: why on the mcode?
10:30 AM Tom_L: ok i'm off to the store
10:30 AM JT-Shop: ok
10:33 AM lcnc-relay: <roguish> good morning.... you guys are busy at it....
10:33 AM lcnc-relay: <roguish> do you get VLANs ???
10:34 AM Tom_L: roguish, check out the updated tom.ui
10:34 AM Tom_L: added postgui with hal buttons etc
10:35 AM Tom_L: later..
10:35 AM lcnc-relay: <roguish> will do. right now, I'm trying to setup a managed switch.
10:35 AM lcnc-relay: <roguish> yesterday I was trying to color some of your buttons....
10:35 AM Tom_L: it's in examples from jt
10:35 AM Tom_L: not on my server yet
10:35 AM lcnc-relay: <roguish> partial success.
10:36 AM Tom_L: i'd like to see that when you finish
10:36 AM Tom_L: gotta run
10:36 AM lcnc-relay: <roguish> Tom_L: will do...
11:46 AM rdtsc is now known as rdtsc_away
12:28 PM rdtsc_away is now known as rdtsc
12:38 PM rdtsc is now known as rdtsc_away
12:40 PM rdtsc_away is now known as rdtsc
01:21 PM XXCoder: nice machinist sat youtube day
01:25 PM JT-Shop: https://www.youtube.com/watch?v=6wHd7JHQqEI
01:33 PM solarwind: I spent more than a couple of weeks without using my lathe, now I forgot everything
01:33 PM solarwind: How do I face a 1cm thick disc, about 10cm in diameter with one known good face?
01:34 PM solarwind: I have a standard 4 jaw chuck
01:34 PM solarwind: but the inner step depth is taller than the disc's final thickness
01:42 PM CaptHindsight: shims
01:43 PM CaptHindsight: or a spacer with parallel faces
01:47 PM CaptHindsight: https://johnsmachines.com/tag/chuck-spider/
01:49 PM rdtsc is now known as rdtsc_away
01:51 PM * Tom_L goes for a nap
02:09 PM rdtsc_away is now known as rdtsc
02:11 PM Unterhaus__ is now known as Unterhausen
02:22 PM XXCoder: interesting sander. was linked in reprap https://youtu.be/AHUUXfB0qHY
02:26 PM Scopeuk: I loved the bit where he ran the cut away cycloidal
02:33 PM XXCoder: just got to that. cool indeed
02:40 PM Unterhausen: youtube thinks I want to see videos about gantry systems today
02:43 PM XXCoder: nice. his router have seperate holder for brush and vaccum system
02:50 PM XXCoder: I love his tols bar when he measures something
02:57 PM XXCoder: lol love the "magic" cnc poart
03:30 PM Tom_L: JT-Shop, not positive but touchoff seems broke now
03:31 PM Tom_L: maybe not..
03:32 PM Tom_L: something was odd there for a sec
03:58 PM Tom_L: JT-Shop, #19 updated my example files
04:13 PM JT-Shop: ok
04:16 PM XXCoder: added that channel to feeds. guy seems fun
04:22 PM Tom_L: starting to look like a gui builder
04:23 PM JT-Shop: :)
04:23 PM Tom_L: you know.. that Mcode thing used to work
04:23 PM Tom_L: mdi
04:23 PM Tom_L: saving to mdi history
04:23 PM JT-Shop: the only m codes that didn't work are m codes that don't change the interp state
04:23 PM JT-Shop: m53 and such
04:25 PM Tom_L: it makes sense you can mdi an M1
04:26 PM JT-Shop: the mdi commands executed but the history didn't update
04:27 PM Tom_L: your hal example build is ok
04:27 PM Tom_L: html
04:28 PM rdtsc is now known as rdtsc_away
04:28 PM JT-Shop: html?
04:29 PM Tom_L: at the bottom you could add connecting an mdi command to one
04:29 PM Tom_L: the hal html build page
04:29 PM JT-Shop: you could add one to the examples
04:29 PM Tom_L: i did
04:29 PM Tom_L: on mine
04:30 PM Tom_L: that's what i just pushed
04:30 PM JT-Shop: ok
04:35 PM Tom_L: what is echo_serial_number_lb for?
04:35 PM JT-Shop: I 'think' it's the nml serial number which is random
04:36 PM Tom_L: we're about to find out
04:36 PM Tom_L: doesn't seem to display anything
04:37 PM Tom_L: helps if you spell it right
04:37 PM Tom_L: returned a '4'
04:37 PM JT-Shop: echo_serial_number
04:37 PM JT-Shop: (returns integer) - The serial number of the last completed command sent by a UI to task. All commands carry a serial number. Once the command has been executed, its serial number is reflected in echo_serial_number.
04:38 PM JT-Shop: so my wag was wrong lol
04:38 PM Tom_L: load file is 6
04:38 PM Tom_L: :)
04:38 PM JT-Shop: see if it keeps changing
04:38 PM Tom_L: it does
04:39 PM JT-Shop: I wonder if it's useful to note a change of some sort
04:40 PM Tom_L: just keeps counting up
04:40 PM rdtsc_away is now known as rdtsc
04:40 PM JT-Shop: hmm
04:41 PM Tom_L: seems to increment by 2 or 3 depending what you do
04:41 PM Tom_L: opstop is only worth 1
04:42 PM Tom_L: really goes to town if you move a slider
04:42 PM JT-Shop: each increment is a command
04:43 PM Tom_L: i know
04:43 PM Tom_L: basically looks like a command counter
04:43 PM JT-Shop: I 'think' you can tell if a slider is in motion...
04:44 PM Tom_L: jog button is worth 1
04:45 PM Tom_L: ok well it works
04:45 PM Tom_L: add a start_line_lb to your webpage _lb
04:47 PM JT-Shop: hmm missed that I guess
04:47 PM Tom_L: wtf is delay_left_lb?
04:48 PM Tom_L: time remaining for the delay?
04:49 PM Tom_L: dwell?
04:49 PM Tom_L: let's find out...
04:51 PM JT-Cave: http://linuxcnc.org/docs/stable/html/config/python-interface.html#_linuxcnc_stat_attributes
04:51 PM JT-Cave: all the status labels are there
04:52 PM Tom_L: i'll try it anyway
04:53 PM Tom_L: works
04:53 PM Tom_L: it's a float and the .xxx is rather long
04:54 PM Tom_L: just like the docs suggest
04:58 PM JT-Shop: some float status items still need attention
04:58 PM Tom_L: limit decimals?
04:59 PM JT-Shop: yup
04:59 PM Tom_L: yeah well it _does_ work
04:59 PM Tom_L: hal was a big hurdle
05:00 PM JT-Shop: https://github.com/jethornton/flexgui/blob/master/flexgui/src/libflexgui/status.py#L273
05:00 PM JT-Shop: big thanks to that person on the forum that solved the magic part
05:00 PM Tom_L: yeah
05:00 PM Tom_L: he seems pretty sharp
05:00 PM JT-Shop: yup
05:01 PM Tom_L: i'm waiting for roguish to add some color to my ui :)
05:01 PM Tom_L: see what he comes up with
05:03 PM rdtsc is now known as rdtsc_away
05:03 PM Tom_L: mama robin built a nest on the end of my extension ladder under the patio
05:03 PM Tom_L: we've been watching them since she laid the eggs
05:03 PM Tom_L: they finally hopped from the nest today
05:04 PM JT-Shop: it's really cool if you can catch the young ones taking their first flight
05:04 PM Tom_L: kinda clumsy
05:04 PM JT-Shop: you would be too lol
05:04 PM Tom_L: probably worse
05:05 PM Tom_L: was gonna mow but that's gonna wait a bit now
05:26 PM Unterhausen: we rode our bikes on the Penn Creek rail trail yesterday, they were setting up the Sawdust festival
05:27 PM Unterhausen: there was a guy doing his chainsaw sculptures that he sells, talk about procrastinating
05:27 PM JT-Shop: pine creek rail trail?
05:31 PM rdtsc_away is now known as rdtsc
06:02 PM Unterhausen: yeah, pine creek
06:02 PM JT-Shop: cool
06:02 PM Unterhausen: Penn Creek has a nice road running next to it, but no rail trail
06:03 PM JT-Shop: we have an old railroad trail here in mo
06:05 PM Unterhausen: All the good trails near us are about an hours drive away
06:06 PM JT-Shop: wolf creek trail is about 10 minutes away and has 26 miles of trail
06:06 PM Unterhausen: People keep trying to make more, but neighbors have shot them down every time
06:07 PM Unterhausen: they think people from State College are going to ride their bikes out into the rural areas and steal their big screen tv's
06:07 PM JT-Shop: lol
06:07 PM Unterhausen: from doing jury duty, the direction of travel of criminals is definitely the other way around
06:09 PM JT-Shop: hmm looks like some rain is moving in
06:09 PM Unterhausen: criminals can't afford to live here
06:13 PM JT-Shop: ex bil was from pittsburg and his day was a beer bottle maker
06:13 PM JT-Shop: dad
06:19 PM * JT-Shop calls it a night
06:24 PM lcnc-relay: <turboss> yep its dow
06:24 PM lcnc-relay: <turboss> * down
06:25 PM lcnc-relay: <TurBoss> only one way bridge ... âšī¸
07:02 PM rdtsc is now known as rdtsc_away
07:28 PM lcnc-relay: <xxcodery> matrix <#> irc works. discord could send text but not get it, in order to stop it from sending to other 2 without ability to read replies, its blocked on discord side for now
07:29 PM lcnc-relay: <xxcodery> turboss is trying to figure out why
07:29 PM lcnc-relay: <TurBoss> /o/
07:29 PM lcnc-relay: <TurBoss> /o\
07:29 PM XXCoder: reply test
07:30 PM lcnc-relay: <TurBoss> hehe
07:30 PM lcnc-relay: <TurBoss> lol
07:30 PM lcnc-relay: <TurBoss> so i broke this room only
07:30 PM lcnc-relay: <TurBoss> lol
07:31 PM lcnc-relay: <xxcodery> https://tenor.com/view/homero-simpson-out-d-oh-gif-15451551
07:39 PM XXCoder: bridge have been repaired. yay!
07:39 PM XXCoder: amazing work by turboss
07:39 PM lcnc-relay: <TurBoss> thank you1
07:40 PM lcnc-relay: <xxcodery> đ
07:56 PM lcnc-relay: <TurBoss> has anyone experience in c++ and boost python plugin ? đ I'm having an issue when i run python remaped owords
07:56 PM lcnc-relay: i opened a github issue maybe some one can take a look, i tried dig on the c++ code but i'm a bit lost đ
07:56 PM lcnc-relay: https://github.com/LinuxCNC/linuxcnc/issues/2967
08:55 PM lcnc-relay: <satiowadahc#0> Ah the Gil problem. I haven't found a way around it
08:56 PM lcnc-relay: <satiowadahc#0> I have a script that basically issues a series of mdi commands, but it very much will lock the interpreter
08:56 PM lcnc-relay: <satiowadahc#0> The two solutions to GIL is either a separate python instance or multi threading.
08:58 PM lcnc-relay: <TurBoss> i tried wraping the "py_call" function wit "Py_BEGIN_ALLOW_THREADS" "end" but that crashed te milltask
08:58 PM lcnc-relay: <TurBoss> đ
10:03 PM lcnc-relay: <satiowadahc#0> What's your goal from python? Just being able to issue commands or logic to?
10:22 PM lcnc-relay: <turboss> i want to comunicate via oword with a api server from the gui so i can get info instead of passing them as parameters
10:32 PM lcnc-relay: <satiowadahc#0> Can I recommend a hal component then?
10:33 PM lcnc-relay: <satiowadahc#0> You can run a python hal component, and still monitor everything.
10:34 PM lcnc-relay: <satiowadahc#0> If you want it to run only a certain times connect it to motion digital inputs/outputs or analog if you want other values
10:34 PM lcnc-relay: <satiowadahc#0> You can monitor alot of internals via hal/status/command
10:36 PM lcnc-relay: <satiowadahc#0> It'll run in a separate python instance thus bypassing the global interpreter
10:38 PM lcnc-relay: <turboss> but i could not figure how to get ui element values or trigger some things from component, or a separeted processs
10:39 PM lcnc-relay: <satiowadahc#0> I'd use hal connections ? Which UI
10:39 PM lcnc-relay: <turboss> probe_basic
10:39 PM lcnc-relay: <turboss> motion pins
10:39 PM lcnc-relay: <turboss> i could run out of pins
10:39 PM lcnc-relay: <turboss> đ
10:39 PM lcnc-relay: <satiowadahc#0> It's only one constant to change to add more
10:40 PM lcnc-relay: <turboss> i can its up at github if you curious
10:40 PM lcnc-relay: <turboss> +show yoy,
10:40 PM lcnc-relay: <turboss> * you,
10:41 PM lcnc-relay: <satiowadahc#0> Sure. Waiting for a fire to die down before calling it quits for the night
10:42 PM lcnc-relay: <zincboy_ca_on> You can read and write gcode variables from python using a bit of code.
10:43 PM lcnc-relay: <zincboy_ca_on> Example:
10:43 PM lcnc-relay: <zincboy_ca_on> " def ngc274_memory_read(self, address):
10:43 PM lcnc-relay: if type(address) is int:
10:43 PM lcnc-relay: # is a fixed memory location read
10:43 PM lcnc-relay: if address < 31 or address > 5601:
10:43 PM lcnc-relay: raise ValueError("ngc274 memory read address must be between 31 and 5601")
10:43 PM lcnc-relay: s = "#" + str(address)
10:43 PM lcnc-relay: elif type(address) is str:
10:43 PM lcnc-relay: if address[0] != "_":
10:43 PM lcnc-relay: raise ValueError("ngc274 memory read must target a global variable")
10:43 PM lcnc-relay: # is a relative memory location read
10:43 PM lcnc-relay: s = "#<" + address + ">"
10:43 PM lcnc-relay: else:
10:43 PM lcnc-relay: raise ValueError("ngc274 memory read address must be of type str or int")
10:43 PM lcnc-relay: pin = str(self.inifile.find("PROBE_SCREEN", "NGC274_READ_PIN"))
10:43 PM lcnc-relay: self.gcode("M68 E" + pin + " Q[" + s + "]")
10:43 PM lcnc-relay: value = self.halcomp["hal_read_memory"]
10:43 PM lcnc-relay: return value"
10:44 PM lcnc-relay: <turboss> server: https://github.com/kcjengr/qtpyvcp/blob/rest_api/src/qtpyvcp/plugins/rest_api.py
10:44 PM lcnc-relay: client: https://github.com/kcjengr/probe_basic/blob/rest_api/configs/atc_sim/python/oword.py
10:46 PM lcnc-relay: <satiowadahc#0> Zincboy I'm missing where you actually read the var?
10:46 PM lcnc-relay: <satiowadahc#0> I'd recommend against direct access and use status for most vars
10:47 PM lcnc-relay: <zincboy_ca_on> "s" is the variable and it is used to set the value of the M68 command. You do need to connect the "pin" in HAL
10:48 PM lcnc-relay: <zincboy_ca_on> This is for the things that don't have status or are part of oword functions.
10:48 PM lcnc-relay: <satiowadahc#0> Turbos, looks like a simple task for a hal component.
10:48 PM lcnc-relay: <turboss> could access to the running instance of the UI elements?
10:49 PM lcnc-relay: <satiowadahc#0> Fair enough. Not many vars exist outside of status
10:50 PM lcnc-relay: <turboss> * UI?
10:50 PM lcnc-relay: <satiowadahc#0> Which elements in particular?
10:50 PM lcnc-relay: <turboss> example call some fucntions or get some field values
10:50 PM lcnc-relay: <zincboy_ca_on> There is not a good way I am aware of to trigger things in the GUI from the gcode interpreter. Pretty much everything I have seen requires the GUI to poll the status or internal functions.
10:50 PM lcnc-relay: <turboss> i can import the framework but thats a new instance and is empty
10:50 PM lcnc-relay: <turboss> yeah ...
10:51 PM lcnc-relay: <turboss> we just have the error status and command channels and debug
10:52 PM lcnc-relay: <zincboy_ca_on> Yes, but those also require polling. Reading internal variables lets you do pretty much the same thing with your oword code.
10:52 PM lcnc-relay: <turboss> so i was thinking... if i implement a rest api in the gui i could cominitate
10:52 PM lcnc-relay: <satiowadahc#0> Or have a gui make a hal component (:
10:52 PM lcnc-relay: <turboss> đŽ
10:52 PM lcnc-relay: <zincboy_ca_on> The GUI still has to poll it.
10:52 PM lcnc-relay: <satiowadahc#0> Polling > GIL
10:52 PM lcnc-relay: <turboss> okay! I'll try thank you!
10:53 PM lcnc-relay: <satiowadahc#0> Ui that freezes or UI that needs extra checking
10:57 PM lcnc-relay: <satiowadahc#0> I can play in the morning and make an exa.ple
10:58 PM lcnc-relay: <turboss> awesome thank !
10:58 PM lcnc-relay: <turboss> * thanks
11:02 PM lcnc-relay: <satiowadahc#0> Without modifying a ui python allows inheriting which may also be helpful
11:02 PM lcnc-relay: <turboss> đ¤
11:45 PM lcnc-relay: <TurBoss> ok found that there are component parameters, most than enoug đĨŗ i don't need the rest api thing hurray!