Billy Boy wrote:

Aside: I have not been able to find any documentation that really explains how ESTOP is expected to work?  I'm unclear on if I should work with estop_latch or not?  The estop_latch documentation is also pretty thin and does not appear to include any examples for either simple or complex configurations?
 

Yes, you should use estop-latch if you have an external estop button (or a safety relay but that's another story). Its pretty well described in the man page and there was a hal tutorial about it on the forum.

works fine!  how are you creating things?  are you opening using editvcp probe_basic and then opening the user ui?

No, I edited the user ui directly.  Sounds like that may be my problem.  I'll have another go at it and report back.

I'm on trixie, did a pull just a week or so ago so I should be up to date.

 

maybe try bringing over the latest user files, there have been some changes and some may no longer be up to date with the porting we did.  the testing i was using used the latest develop branch for the trixie debian 13 probe basic for reference, i do not have a bookworm machine at the momenht while im working on another project so cannot test there if that is what you are on. if so i would recommend updating to the trixie version
 

works fine!  how are you creating things?  are you opening using editvcp probe_basic and then opening the user ui?

 

 

Awesome, thanks!

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

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!

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?

That is a cool trick! Glad to know about Show Hal Configuration. Thanks.

I am using the Axis GUI.

When I watch the ESTOP-ext variable (is variable the correct term here?) I see that it changes state when I toggle the hardware ESTOP. Hal Show Configuration shows yellow when the hardware ESTOP is not active and red when the hardware ESTOP is active. That seems right to me.

When I watch ESTOP-out, it just stays red the whole time regardless of what I do in hardware or software. This seems wrong to me, but it is also consistent with the problem I am having.

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.

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.

just loaded up a new computer today and copied and pasted the config and it just works.  conversational stuff all works fine.  which shows there are not library's that are needed.  its all internal to the config files

the file auto loads also with axis load remote file feature.  so i am not getting the bug that tuxcnc got earlier.  however i am using axis gui so other gui's might have issues.  can't be bothered currently supporting the other gui's but i might if more people post here and are using the software.  but no stress.