Hallo, working on branch gmoccapy_JA_based_on_master I stepped over the following problem. To follow my comments, just get the mentioned branch and use
/sim/gmoccapy/gmoccapy_JA/gantry_mm.ini * get out of estop, * switch on the machine * home all axis OK, now we are in world coordinates (XYZ), that is OK, as "on_hal_status_all_homed" in gmoccapy.py switch automatically to world mode. Please change to MDI, ok we are still in world coordinates (you can see the mode as the dro will be displayed in gremlin if you are in Joint mode) Change back to Manual, why we are now again in JOINT coordinates??? The button in gmoccapy does nothing else than setting manual mode with the command self.command.mode(linuxcnc.MODE_MANUAL) but hal_glib.py (this is the "hal_status widget" from glade) does receive a change of motion mode, as self.stat.motion_mode has a changed value. AXIS does not do that, as it does not use hal_glib.py . But I do not understand, why the motion mode change back to JOINT automatically if we get back to manual mode. That signal should not be emitted. By the way we receive 3 modes: Mode = 1 = Joint ; Mode = 2 = MDI ; Mode = 3 = World; IMHO that is also strange. Could you please help to avoid the mode change on going back to Manual. Norbert ------------------------------------------------------------------------------ What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic patterns at an interface-level. Reveals which users, apps, and protocols are consuming the most bandwidth. Provides multi-vendor support for NetFlow, J-Flow, sFlow and other flows. Make informed decisions using capacity planning reports.http://sdm.link/zohodev2dev _______________________________________________ Emc-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-developers
