On 07/18/2016 11:19 AM, Niemand Sonst wrote: > OK, I think I found the problem, but I will need help to solve this issue! > I do not know C++, sorry: > > Please take a look at emc/task/emctask.cc > around line 223 > > switching to EMC_TASK_MODE_MANUAL sets the trajectory mode to > EMC_TRAJ_MODE_FREE > > IMHO that should not be this way, if we come back from MDI or AUTO, > being in EMC_TRAJ_MODE_COORD > So there should be > > if emcTrajMode == EMC_TRAJ_MODE_COORD: > return > else: > emcTrajSetMode(EMC_TRAJ_MODE_FREE) > > Can anyone fix that bug?
In the days before we merged the joints/axes branch, Task's "Manual" mode was associated with Motion's "Free" mode, because that's where jogging worked the best (at least for id-kins machines). The JA branch fixed jogging (for all kins) in Motion's "Teleop" mode, so that's what Task's "Manual" mode should be associated with now. Note that Motion's "Coord" mode is for running G-code programs and MDI, not for jogging. So i agree with Norbert's suggestion, except Task should ask for Teleop instead of Coord. I'm not sure what all the consequences of making that change will be, but i think we should accept them, and fix any breakage that results. -- Sebastian Kuzminsky ------------------------------------------------------------------------------ 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
