Setting started modification Probe Basic

I am new to LinuxCNC and  ProbeBasic, but not to Linux or Python.

I want to modify the "Status" tab to be similar to what  anfänger did in the thread forum.linuxcnc.org/qtpyvcp/39734-show-your-screens#177730 (see below).   I also want to change so the "Main" tab is the default on start-up

Is there a getting-started guide or notes?  I reviewed the ProbeBasic docs kcjengr.github.io/probe_basic.
Thanks!!!

the best way to do this is to use the provided usertab, this way your edits remain with your config folder and do not get overwritten during updates (which a couple big ones are getting ready to drop). what you definitely do not want to do is edit the main probe basic because then you become the developer for any and all future updates which is not ideal for an end user.

to edit a user tab, open a terminal, type in:
editvcp

a dialog will pop up, in the dialog, find your machine config directory, typically it will be
/home/(your_pc_name)/linuxcnc/configs/(whatever_you_named_your_machine)/user_tabs/template_main/template_main.ui

in the file type drop down at the bottom of the dialog, make sure the type is set to VCP UI Files (*.ui)

this will show you the file :

template_main.ui

select it and click the open button.

Here you can add and edit it as you desire. when done, click save.

check your ini file and make sure that user tabs path is active under the display section:

[DISPLAY]
USER_TABS_PATH = user_tabs/

this activates the user tab and loads on probe basic start up.

enjoy!

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

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

BTW, great job on PB!

I don't disagree that in the long term, this might not be needed. But as all the EtherCAT drivers and IO are in a cabinet, it makes it much easier to troubleshoot, and as I finish the setup and fine-tune. The messages that are passed up to LinucCNC are almost useless.

Also, for future readers.

I am using the HAL widget (www.qtpyvcp.com/widgets/hal/index.html#hal-widgets), HalLedIndicator. The state of these are managed via the postgui.hal. The pin that qtpyvcp presents in the hal is named by the property pinBaseName (translated from the object name by default)

qtpyvcp.led-lcec-link-up = pinBaseName

yup, from memory the probe led is a good example, forgot about that one