If execution of MDI command is active don't interpret subsequent
commands but store them in mdi_execute_queue. On errors flush it.
Now commands sequences like G38.2 Z-2 F10 && G0 Z[#5063+1] works.
Signed-off-by: Pavel Shramov
---
src/emc/task/emctaskmain.cc | 28 +++-
1
You've complained about some subsequent commands not wokring fine in MDI mode
so I've created simple and maybe dirty patch on top of previous patch set.
It introduces another (alongside with interp_list) command queue which is filled
with EMC_TASK_PLAN_EXECUTE messages that may not be interpreted.
> Date: Fri, 24 Sep 2010 08:31:36 -0500
> From: Jeff Epler
> Subject: Re: [Emc-developers] Error running userspace python HAL
>component in Axis
>
> You probably need to use the 'loadusr -Wn name command...' form of
> loadusr. For instance, if you run the command "python
> /path/to/passth
Bugs item #3077238, was opened at 2010-09-28 15:01
Message generated for change (Tracker Item Submitted) made by wschnitker
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=106744&aid=3077238&group_id=6744
Please note that this message will contain a full copy of the
