On Sat, Mar 19, 2016 at 12:08 PM, Nicklas Karlsson < nicklas.karlsso...@gmail.com> wrote:
> On Sat, 19 Mar 2016 13:50:22 -0400 > Gene Heskett <ghesk...@wdtv.com> wrote: > > > I am thinking about split in two with real time threads on micro > controller and the computer for the user interface. It would also be a > flexible solution then it come to choice of user interface but require > extra hardware. > If I were designing this in the current century (the 21st) I'd divide the functions roughly in to three (not two) and place them as follows 1) "Hard" real time functions, on a small micro processor not running any OS. Maybe something like an ARM I'd like size the uP so that it could handle four axis and use multiple uP if more axis were needed 2) The user interface _managment_ and higher level non-real time functions on a generic "Posix" platform (written in a portable high level language) This could be a PC, Mac, Linux/86, LinuxARM) 3) Rendering of the GUI, that is driving the actual screen and mouse/keyboard. This would be web-abased and like targeted to a mobile device like a cheep $100 Android but of course could run on the same machine as #2 above. Another words just as you said except I'd drive the screen with some kind of network protocol (like HTML or whatever) that would be wireless if the user prefers that. One of the more modern architectures I like is ROS (Robot Operating System) and it can do something like LinuxCNC like for example drive a pick and place machine or an robot that welds auto bodies on a factory floor. ROS is to comp-lex for most CNC machines but it's architecture is good. It uses a very large number of processes that communicate via message passing (publisher/subscribber model) and each processor can run on a separate computer if you like. Some real-time, some not. This allows me to do things like swap in a simulated sensor for the real on without a even a restart just be redirecting message routing. And of course message logging (and later playback) is a great debugging tool. One need not go as far as ROS but I'd decouple into three parts (1) RT stuff, (2) the "guts", and (3) the physical display and user input device -- Chris Albertson Redondo Beach, California ------------------------------------------------------------------------------ Transform Data into Opportunity. Accelerate data analysis in your applications with Intel Data Analytics Acceleration Library. Click to learn more. http://pubads.g.doubleclick.net/gampad/clk?id=278785231&iu=/4140 _______________________________________________ Emc-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users
