"KeyError" suddenly appears after moving a limitswitch

Hi!
I am 99% sure that I do have G54 in my startup code, but I will double check tomorrow.

Thx!

Update: Confirmed - G54 was in the startup code line. 

Update / Wednesday 5:52PM: 
finally found the root cause for this behavior.
Its line 25 in my pendant.hal

# --- ESTOP-EXT ---
net pendant-estop     <=  hm2_7i76e.0.7i76.0.0.input-29

when I comment it out, everything is fine. 

Now I just have to understand whats going on with this signal.

Regards
Sebastian

###############################

OK, I am one step closer.. I created a "virgin" configuration.. that worked fine and didnt show this error. Than I started copying my old config file by file into the new folder to narrow down when this error would be introduced.

And - believe it or not - it happens as soon as I include my pendant.hal file.

Here is a screencast. Its 100% reproducable.


As soon as "G54" is highlighted in the top left corner, everything is fine. When its "off", I always get this popup...

Does this make any sense to you?
this is my config.
github.com/SebastianMusser/LinuxCNC

I wonder if it's because it's being loaded before the GUI is loaded

Good question.
I also wonder is this really is a PB issue or maybe a general LinuxCNC topic. What do you think?

It looks like maybe a comflict in pb, the ui tries loading which should set an active work coordinate system. This is how the button synchronization and exclusivity functions.

It may be your pendant code. This is the first error of that nature ive had reported in 8 years and there are thousands of pendant users out there.

I would try moving any items that need to synchronize with the gui into the postgui halfile and see if functionality still works and the error goes away.

Success!
I moved that line to my posthui.hal and now everything works. 

# --- ESTOP-EXT ---
net pendant-estop     <= hm2_7i76e.0.7i76.0.0.input-29

Thx for the support. 

Awesome. Glad it's working!