Brendon, ( and anyone else confused about my ramblings here )
 
 
Summary-

• I develop software for a machine tool company.
• Machine Manager is a machine tool/automation  framework developed in .net
• KMotion_dotNet is a c# wrapper for the Dynomotion devices that can be used from any CLR compliant language(c#, vb.net, managed c++, IronPython, IronRuby, IronJS, etc...)
• I just want to share this framework and GUI so that:

1. others can have a lower point of entry into this field(simplified programming)
2. we have yet another alternative to Mach as well as KmotionCNC
3. the .net wrappers could also be used in conjuntion with Mach/KmotionCNC for custom behaviors
4. I will hopefully get feature requests, feedback and bug reporting so that it becomes better and better

 
 
If you have time for a read, continue on:
 
 
________________Back Ground______________________________________________________________
 
   I am a software engineer for an American machine tool manufacturer that specializes in the woodworking and plastic markets.
 
See here for the machines:
 
(((The software shots are in the order of 8-10 yrs old, much updating has happened since the videos were made)))
 
http://www.accu-systems.com/machines.php
 
 
  I stumbled upon the Kflop while resarching some cost effective motion controllers for a line of entry level machines we are developing.  It is an amazing package of hardware+software and I was drooling from the moment I read the specs.
 
  We are currently using Galil products for our 'economy machines', but I would like to move over to the Kflop and maybe use it for some larger systems as well.  To make this happen, I need to devise a "hardened" enclosure/IO interface(opto-isolated 24v), and I also plan to use it on my personal machine to show the 'higher ups' what it can do.
 
 
 
When I came to Accu-Systems every machine had it's own software, and worse variations had their own software as well(the previous developers would copy/paste/frankenstein the code together any time a new machine order came in). 
 
  So the first thing I did was to make a uniform framework for wich nearly any machine can be configured and built.  Base level things like points of IO, Axes and axis groups are programmed in c#, while behavior can be controlled via a scripting language(things like a tool-change routine is an excellent candidate for scripting as it may vary slightly from machine to machine).  Add to that framework a flexible GUI layer that can be configured to control any type of machine(CNC or custom process).
________________________________________________________________________________________
 
 
 

________________What am I doing on this forum?_______________________________________________
 
 The CNCTW project is slated to be the next version of the MachineManager framework, which is really the third iteration as I learned much when writing the first two.
There are also some proprietary technologies I have developed for Accu that I cannot use in an open-source project so that is another reason for the third version.
To get the excellent DynoMotion hardware working in the framework, I had to write a c++ to c# wrapper, which now looks like it will be added to the Kmotion software package.  This will be great for all DynoMotion customers as it should ensure it is always available and maintained to the current version(of which I am happy to continue doing).
 
So with the CNCTW project, you should be able to command a CNC machining center, a robotics work cell or a cutom automation process.
__________________________________________________________________________________________
 
 
There is still a bit of work to be done on the framework, but it should be ready as a CNC controller within the next week or two.(it already has much of the basic functionality, just needs some additional features and polishing)
 
 
Let me know if there is anything required clarification.
-Brad Murry