Timing problem

Hello,
I found a problem with load gmoccapy. I made a gladevcp panel with leds. I connect to this leds some other pins in postgui.hal. With axis ui no problem. But with gmoccap ui is send message : custom_postgui.hal :13: Pin 'leds.hal_led1' does not exist.
This error message not all time. Sometimes gmoccapy is started and the hal leds working well.

I think the custom_postgui.hal loaded before the gmoccapy started.

Sorry for my english.

korbendallas78 wrote: I made a gladevcp panel with leds. I connect to this leds some other pins in postgui.hal. With axis ui no problem. But with gmoccap ui is send message : custom_postgui.hal :13: Pin 'leds.hal_led1' does not exist.

Are you loading the GladeVCP with a "-W" switch?

This is likely to be more a GladeVCP timing issue that Gmoccapy.

loadusr flags are given here:
www.linuxcnc.org/docs/html/man/man1/halcmd.1.html

EMBED_TAB_COMMAND = loadusr -W gladevcp -x {XID} leds.glade

korbendallas78 wrote: EMBED_TAB_COMMAND = loadusr -W gladevcp -x {XID} leds.glade

The manual ( www.linuxcnc.org/docs/html/gui/gladevcp.html ) suggests -Wn gladevcp, ie

This waits for a component "gladevcp" and has a -c option that I am not sure of the meaning of, but I think forces a component name, which is possibly useful if it is waiting (-Wn) for a specific component to be ready.

This is a guess, though. No guarantees expressed or implied

I tried. Same problem

@korbendallas78

I also noticed that behavior some times, I recomend the followingf, as till now it works under all circumstances perferct.
Move all the relevant hal connections from postgui.hal to hal file named leds.hal. That hal file should be in your config dir.

And load your panel like this one:

That command loads the panel and after loading it it connects the hal pin mentioned in the named hal file.
If you need, you can add your own python handler by adding -u led.py
For an example you may look at sim/gmoccapy/gmoccapy-plasma/gmoccapy-plasma.ini

Norbert