On Mon, Jul 15, 2013, at 02:49 PM, David Bagby wrote: > Hi, > This thread caused me to clean up some notes I'd jotted down during > Wichita related to this topic. > In this thread I think that different people are talking about different > aspects of a topic that I think of as "implications of multiple > programmatic motion sources". > > Alas I think about this stuff better with pictures... (unfortunately, > it's a little hard to share text and pics via a text only email list > that does not allow attachments). > So pardon me, but the best I can think of to do is to upload a pdf doc > with pics and ask that you grab it to look at. > www.CalypsoVentures.com/privatedl/LCNC/LCNC_control_mode_distinctions.pdf Lots of good stuff in that document. I agree that drawing things out often really helps both clarifying it in my own mind and communicating it to others. Thanks!
In the interest of making the drawings a bit more accurate, a minor nit-pick. In the third drawing, MDI is shown sending canonical commands to motion thru a different path than the interpreter. MDI actually uses the interpreter. I think a more accurate drawing would have two boxes labeled "file (AUTO mode)" and "keyboard (MDI mode)", above the interpreter, and both of those boxes would feed into a single interpreter, which would then feed canonical commands to motion. The distinction matters because the interpreter has some internal state, which affects the way a g-code is interpreted. Code from a file can change they canonical commands that are generated by MDI code, and vice-versa. That can't happen if the system were built per the original drawing. I'm not commenting on the merits of any current or proposed approach, just trying to make sure we correctly understand the existing implementation. > The pics helped me structure how different aspects of this thread > interrelate. > > Michael: I'd also like to know if I have translated reasonably what you > tried to describe via email text. > Kent: thanks for my new vocabulary word of the day: Gedanken - I had to > look that one up - only to find that is what I was doing with the > notes... ;-) > > Comments are welcome. > > Dave > > P.S. I'm also happy to provide the base doc for the pdf if anyone > prefers to comment by editing it directly to create red lines (MS office > sources). > > On 7/14/2013 2:00 PM, Chris Morley wrote: > > This has been bugging me awhile. > > Why does linuxcnc force three modes? > > I understand it's a hold over from industrial machines. > > > > > > > ------------------------------------------------------------------------------ > See everything from the browser to the database with AppDynamics > Get end-to-end visibility with application monitoring from AppDynamics > Isolate bottlenecks and diagnose root cause in seconds. > Start your free trial of AppDynamics Pro today! > http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk > _______________________________________________ > Emc-developers mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/emc-developers -- John Kasunich [email protected] ------------------------------------------------------------------------------ See everything from the browser to the database with AppDynamics Get end-to-end visibility with application monitoring from AppDynamics Isolate bottlenecks and diagnose root cause in seconds. Start your free trial of AppDynamics Pro today! http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk _______________________________________________ Emc-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-developers
