"KeyError" suddenly appears after moving a limitswitch

So you are saying that the latest stable version is not known to work? It worked great for me...

Shouldnt I try to update the my stable branch first?

the latest stable version DOES work, but it is not working for you currently. what i am saying is i have no idea why you are getting that error and i cannot reproduce it here, so without knowing where or why that error is happening for you specifically and not here or being complained about elsewhere, the next logical step would be to update and make sure its not something wrong with your install or a change made that you may not remember making or be aware had effect that was made without your knowledge.

Before i spend any time troubleshooting with such little data on the problem, it would be prudent to know for certain that it's in probe basic/qtpyvcp and not an issue elsewhere.

I would also test the probe basic sim to see if the issue is there as well, if it is then it is probably an internal error issue and not a configuration issue. from there we can figure next steps. but identifying where the issue stems from is in my opinion the first step, so i would test in the sim and see if you can reproduce the error there. if not, then its a configuration change, maybe a stray typo from your editing? if you can reproduce in the sim, then i would say the next step is removing and reinstalling the stable branch and testing or testing, or testing the develop version. the develop version has file changes for the work coordinate system table and the dro's which may be a resolution. it also has a fix for running on linuxcnc version 2.10. i'm not sure what version you are running on, but if it is 2.10 it NEEDS the develop version.

Alright, understood.
Today I spent some time with my cnc. I setup a new machine in LinuxCNC, and now I have two setups.. one is "good", and the other one shows this issue. 
What I found out - when I startup the "bad" machine and open the "probing" tab, none of the work offsets at the top is selected.
When I start the "good" machine, G54 always is preselected.

No idea if this makes sense or helps, but it fits to the error message imho...

 

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