[Emc-users] mdi does not queue commands
Previous two attempts at posting this have silently failed. Not obvious if lists.sourceforge.net or something else is filtering me... Today I was reading the Axis 2.5 documentation: http://www.linuxcnc.org/docs/devel/html/gui/axis.html and noted for the first time Section 6, describing the program named mdi, which provides a manual data input function to a running LinuxCNC process. While testing this mdi program using simple G01 moves on a 3 axis stepper machine, using Axis V2.5.3 I see it does not queue commands, but subsequent tasks can interrupt previous incomplete ones. This is not how the MDI command function works in Axis, which queues tasks, so that each one completes. Is this interrupt behaviour a feature of the mdi program, or something with six legs? christopherpurc...@mac.com Tel: 902 464 9248 5 Mt Pleasant Ave Dartmouth, NS B3A 3T1 -- Managing the Performance of Cloud-Based Applications Take advantage of what the Cloud has to offer - Avoid Common Pitfalls. Read the Whitepaper. http://pubads.g.doubleclick.net/gampad/clk?id=121051231iu=/4140/ostg.clktrk ___ Emc-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users
Re: [Emc-users] mdi does not queue commands
On 02/06/2014 07:28 AM, Christopher Purcell wrote: Previous two attempts at posting this have silently failed. Not obvious if lists.sourceforge.net or something else is filtering me... Today I was reading the Axis 2.5 documentation: http://www.linuxcnc.org/docs/devel/html/gui/axis.html and noted for the first time Section 6, describing the program named mdi, which provides a manual data input function to a running LinuxCNC process. While testing this mdi program using simple G01 moves on a 3 axis stepper machine, using Axis V2.5.3 I see it does not queue commands, but subsequent tasks can interrupt previous incomplete ones. This is not how the MDI command function works in Axis, which queues tasks, so that each one completes. Is this interrupt behaviour a feature of the mdi program, or something with six legs? I think the mdi program is very rarely used. I think it was more a proof of concept than a serious implementation of a user interface, and i'm not surprised to hear it behaves in unexpected ways. The MDI tab in Axis is much more widely used, and should work much better. Could you use it instead? -- Sebastian Kuzminsky -- Managing the Performance of Cloud-Based Applications Take advantage of what the Cloud has to offer - Avoid Common Pitfalls. Read the Whitepaper. http://pubads.g.doubleclick.net/gampad/clk?id=121051231iu=/4140/ostg.clktrk ___ Emc-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users
Re: [Emc-users] mdi does not queue commands
2014-02-06 16:28 GMT+02:00 Christopher Purcell christopherpurc...@mac.com: While testing this mdi program using simple G01 moves on a 3 axis stepper machine, using Axis V2.5.3 I see it does not queue commands, but subsequent tasks can interrupt previous incomplete ones. This is not how the MDI command function works in Axis, which queues tasks, so that each one completes. What I see is that it does not work in Axis, but does work in ... Axis :)) Could you, please, describe in more detail, what exactly do you mean? Viesturs -- Managing the Performance of Cloud-Based Applications Take advantage of what the Cloud has to offer - Avoid Common Pitfalls. Read the Whitepaper. http://pubads.g.doubleclick.net/gampad/clk?id=121051231iu=/4140/ostg.clktrk ___ Emc-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users
