"KeyError" suddenly appears after moving a limitswitch

ok, so then in your other config in the ini, add G54 to the start line and it should resolve for the time being. I will investigate the scenario here with it removed from the startup and see if i can reproduce, if so i will look at hardcoding a default work offset for startup to avoid the error in future releases. great job identifying the difference!

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