I'm sorry for bugging you guys, just shortly after sending to the list I figured it out. But did stare a day into it before w/o reckognizing... My branch for a "pocket based" non random toolchanger is working fine. Tools are ordered but the changer works only based on the pockets associated to the tool. So tool can now be any number, as long as the pocket is valid for the changer, it works.
Question to the dev process - is there any written rule when/how a branch can be part of the linuxcnc github repo? Regards, Daniel PS: The adaptations base on the ones from Rene and are merged on the latest 2.8 branch. You can find them here: https://github.com/mydani/linuxcnc/tree/2.8-pocket-fix Am Mi., 18. Dez. 2019 um 07:29 Uhr schrieb mydani <[email protected]>: > Hello folks, > > I am currently playing with the recent 2.8 and merged my branch for a tool > changer support into the C-part of linuxcnc. > In axis all is proper, then I started to use gmoccapy and I faced a > strange situation there. > In my change.ngc macro, I show the interesting values by these lines: > > (debug, current tool: #<_current_tool>) > (debug, current pocket: #<_current_pocket>) > (debug, selected tool: #<_selected_tool>) > (debug, selected pocket: #<_selected_pocket>) > > In my tooltable I am just using 2 tools to show the behavior. Tool 1 has > pocket 101, tool 2 has pocket 2. > > Scenario 1) change from t1 to t2 => all works as expected, the values > shown in gmoccapy are exactly what I can see in the debuggers (both C and > python). > > Scenario 2) change from t2 to t1 => the pocket value for tool 1 is shown > as -1, while it imho should be 101. In the debuggers I can see in the > epilog, that the value of the variable is in fact 101 at that time. > However I notized gmoccapy shows the debug messages after (!) the epilog > function was run through. So I wonder whether a race condition could occure > there. But then I wonder also why with smaller pocket values the issue is > not observed. > > Pictures of scenario 1&2 can be found here: > Scen1: > https://i.ibb.co/2sDFLd2/01-Change-T1-T2-Prolog.png > https://i.ibb.co/8YqRfhD/02-Change-T1-T2-Epilog.png > https://i.ibb.co/zZVzv4d/03-Change-T1-T2-Gmoccapy-Debug-Msg.png > > Scen2: > https://i.ibb.co/jLTx0Qg/04-Change-T2-T1-Prolog.png > https://i.ibb.co/0Mbv5DG/05-Change-T2-T1-Epilog.png > https://i.ibb.co/ZHS4nRV/06-Change-T2-T1-Gmoccapy-Debug-Msg.png > > > Looking forward on any hint which helps me understand this. > > > > > Thanks and regards > Daniel > > PS: excuse me if I am not supposed to sent screenshots along, will do > otherwise / store otherwhere if told so. > _______________________________________________ Emc-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-developers
