Advanced Search

I would say this, I would live with the stock ui for a bit, I think like most find the led's seem important initially, but in most cases once the machine is setup which can be done with halshow mainly, you will never visit the page they are on almost never. if you hit a limit, you get a pop up message, if you need an led for verification on a switch on item that isn't obvious I would say go for it, otherwise you are pretty much just creating a setup aid that halshow can handle much easier with a lot less work. just my two cents from developing and using PB for the last 7 years.

live with it and you will find the things that you need and the things that you can live without.

as for the how to, the qtpyvcp docs cover these things like widget rules etc. most mainstream settings and status items are baked in, anything custom you would have to sort on your own.

www.qtpyvcp.com/tutorials/widget_rules.html

Now i think of it, you're probably right. Maybe this is the case. What does imply for my setup / what should i look up so that i don't mess up the connection.

[EDIT]

I think i then have to connect it to GND and input right? (This is more safe, so i can test it first in this setup). I have this simple probe:

www.makerstore.com.au/wp-content/uploads...OOL-TP-V1-6a-NWM.png

Thanks. I was overthinking it.

For part of this I want to connect LEDs to hal pins. I have IO pins and based on their status high/low to enable the led. Much like Hal Show. I assume this is what HalLedIndicator is for? How do I "connect" the led to a pin? Rules? How are the hal pins named?

Examples of some pin I want to connect:
lcec.link-up
lcec.0.Z.din.1
lcec.0.Z.limit-neg