I can confirm the same on another 3 axis machine with trivial kinematics. After stopping or pause/stopping a program motion continues some straight line at programmed feedrate to some point and stops. The distance is big. This occurs every time, when paused in an arc motion and stopped after that. Two tools already broken..
I found this as an already fixed "surprise move bug" in master: https://github.com/LinuxCNC/linuxcnc/commit/404be0fd8f6b6396f31943755db4b4754687d79b Then I installed master branch and get another errors - not being able to run any program with an error: emc/task/emctask.cc 397: interp_error: exception during generator call: TypeError: 'NoneType' object is not callable exception during generator call: TypeError: 'NoneType' object is not callable What would you recommend me to do? Info from v. 2.7.8 config: In G-code: G64 P0.05 Q0.001 I use M6 tool change remap with subroutines. Two important lines in main INI file: [RS274NGC] ... REMAP=M6 modalgroup=6 prolog=change_prolog ngc=toolchange epilog=change_epilog ON_ABORT_COMMAND=O <on_abort> call ... [TRAJ] AXES = 3 COORDINATES = X Y Z LINEAR_UNITS = mm ANGULAR_UNITS = degree CYCLE_TIME = 0.010 DEFAULT_LINEAR_VELOCITY = 50 MAX_LINEAR_VELOCITY = 700 NO_FORCE_HOMING = 0 ARC_BLEND_ENABLE = 1 ARC_BLEND_FALLBACK_ENABLE = 0 ARC_BLEND_OPTIMIZATION_DEPTH = 100 ARC_BLEND_GAP_CYCLES = 4 ARC_BLEND_RAMP_FREQ = 100 LinuxCNC/AXIS version 2.7.8 3.4-9-rtai-686-pae #1 SMP PREEMPT Debian 3.4.55-4linuxcnc i686 GNU/Linux Debug messages: Issuing EMC_TRAJ_LINEAR_MOVE -- ( +220,+120, +0,105.936000,174.984000,-401.414000,0.000000,0.000000,0.000000,0.000000,0.000000,0.000000, +2,13.333333,342.188909,1231.880073, +0, -1,) Motion id 24 took 0.082464 seconds. Outgoing motion id is 1108. Issuing EMC_TRAJ_LINEAR_MOVE -- ( +220,+120, +0,105.047000,175.443000,-401.414000,0.000000,0.000000,0.000000,0.000000,0.000000,0.000000, +2,13.333333,375.140935,1350.507367, +0, -1,) Issuing EMC_TASK_PLAN_PAUSE -- ( +510,+12, +31,) Issuing EMC_TASK_ABORT -- ( +503,+12, +32,) emc/task/emctask.cc 389: interp_error: bad number format (conversion failed) parsing '' bad number format (conversion failed) parsing '' Motion id 25 took 3.132175 seconds. Motion id 0 took 0.000002 seconds. Outgoing motion id is 2114. Issuing EMC_TASK_PLAN_SYNCH -- ( +516,+12, +0,) Outgoing motion id is 2115. Issuing EMC_TRAJ_LINEAR_MOVE -- ( +220,+120, +0,169.066000,226.898000,-401.414000,0.000000,0.000000,0.000000,0.000000,0.000000,0.000000, +2,13.333333,342.896322,1234.426761, +0, -1,) Issuing EMC_TASK_SET_MODE -- ( +504,+16, +33, +1,) Motion id 2115 took 5.132525 seconds. Motion id 0 took 0.000002 seconds. Issuing EMC_TASK_PLAN_SYNCH -- ( +516,+12, +0,) can't do that (EMC_TRAJ_SET_TELEOP_ENABLE) in auto mode with the interpreter idle 06/25/2016 08:35 PM, Tomaz T. rašė: > > > > I'm a bit confused what could cause unexpected move after pressing stop or > pause->stop. > Here is print screen what happened: https://cdn.pbrd.co/images/1X2RCHL7.jpg > Recently I implemented manualtoolchange but the only thing I was modifying > were subroutines ... not sure if there could be source of this issue? ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, SlashDot.org! http://sdm.link/slashdot _______________________________________________ Emc-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-users
