Probe Basic - HAL pins not being created

Now that I've got the user tabs, ATB buttons, and user DRO showing up, the next snag is creating hal pins.

I added some hal LED indicators to my custom DRO panel, but they aren't being created when LCNC/PB is started.  At least they don't appear in halshow.

Dragged & dropped a HalLedIndicator in the panel
edited the object name
edited the pinBaseName

Just trying to get an on-screen indicator of an "is-homed" status.

I remember running in to this issue a few years ago - that time I was missing the lines in custom_config.yml:

I added the above under data_plugins: but still no joy.

Do I need to add this:
To the dros_user.py file somewhere?
 

After a bit more digging, I'm guessing the "# create a new component..." stuff is for creating a new component and not for just linking qtpyvcp hal widgets to hal.

Reviewing the terminal output during PB startup, it looks like 'exported hal' is working, or at least not throwing a warning:

 

Not sure what this warning is:

 

Attached the full terminal output during startup, halshow showing no pin being created, as well as a screenshot of the hal led indicator I'm trying to connect.

 

Still can't get halpins to show up, but I used the widget rules to cook up a workaround...

DRO is now sorted.  Red = unhomed, black = homed

Personal preference is not to have anything that can zero out my DRO with one click.  And since I've got a physical 'home-all' button and no need for a 'go-to-zero' function, those could leave the chat, too.

 

I can keep going for now, but I'd still like to figure out the missing hal pins if anyone's got an idea.

did you add the halpins to the postgui hal file?  you can use the blue led on the touch probe graphic as an example for wiring it up.

I did not add the pins to post-gui.hal.  I was under the impression that qtpyvcp created the halpins outside of the user-config HAL process.

I see pins like qtpyvcp.probe-in and qtpyvcp.timerhours.in in the demo post-gui hal file but there is no loadrt or addf statements present.

I hadn't bothered trying to connect the new qtpyvcp pins until I could see them in halshow.  All the 'standard' probe basic or qtpyvcp pins are present in halshow... just not the new ones I'm trying to create.

the user tabs get loaded after so they may need to be loaded through post gui hal so they get initialized during startup otherwise they may be created after the initial ui loads but before the child ui is loaded. but just guessing as i have not tried what you are doing before with halpins,. if you have them listed in the main hal file i would move them to the post gui and retest.

I don't have any of the qtpyvcp pins listed in any of my hal files - but they're still loading.

I get that connections to any of the qtpyvcp hal pins needs to be done in post-gui.hal.

Would you mind trying to create a qtpyvcp hal pin like I'm attempting and see if you can make it work?

I don't want to start fiddling with the main probe_basic.ui file, but you or one of the other devs might have some test configs to see if you all can figure out if this is just me or a bug.

ok i just tested and i see the test button i created in halshow, i can set and clr it to enable and disable it, it is under Pins/qtpyvcp/hal_test_button. sooo it is working here, not sure what you might be doing differently?

here it is working.. i did not change anything at all just dropped the halbutton widget in the usertab and gave it a pinbase name saved then started probe basic and everything was there!

Awesome, thanks!

Can you try a HalLedLight and see if it shows up too?  That'd confirm I'm off the rails somewhere.