2.10 Gmoccapy - remap M61 disable show MDI window #3120
Comments
|
Modification INI file: needed file: |
|
I can reproduce this. |
|
Or you must change tool by M6 and it works again. |
|
The odd thing is that even if I remove these lines from the ini I still get the bug: |
|
Just did some investigating:
So I would conclude that this is not related to your remap. |
|
Hi, I would like to tell you more about this issues. |
|
I know and I am with you as I was the one who actually could replicate some of the issues you have been reporting. |
|
Sorry for the confusion. |
|
Here is the debug output (with my comments added): |
|
Source of problem is "tool_change = True". I THINK. "tool_change = True" is for hidden blinkink modes during tooling change after homing. I dont know, why is activated after M61. |
|
I agree. There is a comment in gmoccpy.py: That may explain why it is set during a tool change so maybe the question is why it is still on when we click on the MDI button later. The only place I can find where that happens is in 'on_hal_status_interp_idle' (which is clearly not called as we do not see the debug message 'IDLE'): |
|
I went back to version 2.9 on my system and noticed that the severe form of the bug sometimes also occurs but most of the time I observe the less severe form where the MDI button functionality can be recovered by clickin on the MANUAL button and then on the MDI button again. in this case the behavior is like this: Note the If it misses the interp_state being idle then we get the severe form if it catches the idle state we get the less severe form. [EDIT] |
|
I notice that if we artificially prolong the M61 command by inserting a G4 into your 'settool_g43' remap we can actually make the bug go away: Of course that does not fix it when the remap is not used. |
|
I forgot remove it. BUT it cant be source of problem. Gmoccapy must akcept everything in remap. g4 p10 for example. |
|
I'm saying that if I insert 'g4 p.1' the issue goes away. |
|
I understand now. |
|
Here is the difference in the debug output Without 'g4 p.1' -> Bug: MDI button unresponsive: This it with 'g4 p.1' -> MDI button works fine |
|
Now I get this slightly different output with 'g4 p.1' -> MDI button works fine |
|
If I understand this correctly then 'on_hal_status_interp_idle' is called from 'GStat' which would be outside of the GUIs control (but I really know too little about 'GStat'): So I get the impression that some GCode execution (like 'M61 Q') may simply have become too fast for the event to reach the python handlers in the GUI. maybe @c-morley would be able to give a more educated opinion. |
|
Since I have a system where this issue can easily be reproduced I'll try to find out if the GStat Python Module is actually sending the message about the change in inter-idle. |
|
Actually looking at the GStat documentation I may not even have to look much further as it seems that the LinuxCNC status is checked in 0.1s intervalls: So if we have Gcode that takes less then 100ms to execute the chances are that GStat does not register a change and it would make sense that adding G4 P.1 would make the issue go away. |
|
As a first idea.
It might make sense to look for other 'self.command.mdi()' calls that could potentially suffer from this bug. |
zz912
changed the title
I added to LCNC remap for M61 and I found out, that after using, Gmoccapy MDI window is disabled.
For more information and test configuration look here: #3113
The text was updated successfully, but these errors were encountered: