Advanced Search

just an fyi why are you destroying the format and look of the ui.. your better than that!

there is no 3 states only on off because you only have on and off hal output and this can only use a single hal reader

and i am adding a flashing property to button widgets because thats a good idea..

 

That's really slick!

Any thoughts on the three-state label I mentioned?

PAUSED state is blinking.

ok yeah this is what you want to do it is much cleaner with no code changes to hack it up, this is existing hal code and the button itself is none functional in the ui essentially becomes a label, you cannot click it or select it or do anything bu observe it physically.

you then just add your net in postgui.hal file and your off to the races!

here is the stylesheet used:

doesn't have to be, you can give it no focus, im tinklering with it now just about have it and it is pretty easy with no code changes and making more of them would be way faster and not require code changes for each instance

Lcvette wrote:

Ok I see now, did you try just using a halbutton? If you just wanted color change I think that would work and be simple. Have to check, but I believe they are bidirectional.
 

No, it didn't occur to me to use a button as an indicator.  And I didn't want an on-screen button or control widget.

Ok I see now, did you try just using a halbutton? If you just wanted color change I think that would work and be simple. Have to check, but I believe they are bidirectional.

As I said earlier, the LED was just a first attempt.  When that didn't work out, I realized a label that acted like an LED could do double-duty and save screen space.

Just so we're on the same page, here are two screenshots of what I've got after Claude created new .py and .qss files



The red one is actually blinking, but you get the idea.

I'm not completely sure about the architecture, but it looks like that python file creates two hal pins per Qlabel instance.  And links the label to a .qss setting via the standard Qt Qlabel's dynamic settings.  Screenshot of the dynamic properties:



The rest of the indicators follow the same process.  Two hal pins are created per label, I link one of the pins in post-gui, set the dynamic properties to a color, and they all work.

I've attached the files in case you're interested in what's backstage.  And I think the status_tab.py was also modified - and is what I'm not supposed to touch (auto-updated when probe_basic.ui is open).

The above is what I was trying to do with HalLabel widget rules, but couldn't.

I agree with Tommy. Pointless adding additional failure points!

I would try and arrange the drives horizontallly as there is a risk the top drives overheat with the heat from the ones below. I have had this happen but at a lot more than 24 volts (which I think is too low, velocity and acceleration are king with plasma and you are limiting yours by the low voltage)

for reference here are the already linuxcnc exposed status items:

linuxcnc.org/docs/html/config/python-interface.html

you want the label now and not the led? the led you simply set the pin base name and then point to it in hal in the post gui hal file and when the net is active it will light up the led.

halLabels are for numerical values, not strings. there is not a really clean method to access the hal io layer digitally with strings. this is just a linuxcnc shortcoming, they expose certain things through python and they are determined through the linuxcnc repo and not qtpyvcp/probe basic. so if you need a status or setting that is in that python channel its easy if its a customized halpin not so much unless its something very basic like toggling a switch for an led or outputting an actual numerical value since that coding is present in the linuxcnc codebase.

you can get around this a few ways, the first being to make a hallabel that would display a value and make your other changable label display certain text based on that hallabel's current value: for example,

1 = air pressure LOW
2 = air pressure OK

its a bit hacky so you will need to determine if the hackiness is ok to achieve your goal, or maybe just use the led.

I can look at giving the user a default state color style for the halledindicator which could give you the ability to make it green default and red active.

Because I don't know how to make a hallabel change how it is displayed based on pin state without using the widget rules.

And I don't know how to make a non-hal Qlabel change based on a hal input state.

In the example  - thank you for that - you showed a screen button that changed display based on clicked (or not).  And an LED that changed from off to blinking when the button was clicked (the connection feature).  But the example wasn't tied to a hal pin - at least I didn't see that it was.

So how do I get a label - hal or not - to change state based on a hal pin state change?

Ok so you just need it active when the pin flips? What the issue then I'm confused

My reply was that i use parallel port on several machines (over 10 for sure) with RTAI kernel, and use RT-Preempt on new-ish PC's for parallel port and Mesa boards.
In total, easily over 50 machines.
-
I do have a PCI board that i have to spend some time with, got it from a friend so i have no clue where he got it, and another set of boards that was driving a 5 axis machine, from initial tests i did back then all are recognized by older kernels, but will probably need drivers and i am not in the mood of writing those.