Difference between revisions of "Main Page"

From Dynomotion

Jump to: navigation, search
(Wiring Diagrams)
(TK)
Line 1: Line 1:
 
=='''Dynomotion wiki'''==
 
=='''Dynomotion wiki'''==
Find and share information on Dynomotion Systems.  Please feel free to contribute and correct information yourself.  Joining is not required to View or Search for information.  You will need to Register and confirm your email account before having permission to edit or add pages.  By default WYSIWYG editing is enabled.  Standard MediaWiki editing may also be used or set as the default in your User Preferences.
+
Find and share information on Dynomotion Systems.  Please feel free to contribute and correct information yourself.  Joining is not required to View or Search for information.  You will need to Register and confirm your email account before having permission to edit or add pages.  By default WYSIWYG editing is enabled.  Standard MediaWiki editing may also be used or set as the default in your User Preferences.
  
''Warning: Use at your own risk.  Information is for example purposes only and may contain errors.  It is up to the User to verify the information is correct and safe to use. In no cases will any contributor or Dynomotion be liable for incorrect information.''
+
''Warning: Use at your own risk.  Information is for example purposes only and may contain errors.  It is up to the User to verify the information is correct and safe to use. In no cases will any contributor or Dynomotion be liable for incorrect information.''
  
 
Thanks for Contributing!
 
Thanks for Contributing!
Line 13: Line 13:
 
Kanalog [[Kanalog Hardware Info|Hardware Info]]
 
Kanalog [[Kanalog Hardware Info|Hardware Info]]
  
==<br />Software Test Releases==
+
==<br/>Software Test Releases==
 
[http://dynomotion.com/Software/KMotion4.33q.exe V4.33q]
 
[http://dynomotion.com/Software/KMotion4.33q.exe V4.33q]
  
==<br />PC Example Applications==
+
==<br/>PC Example Applications==
A number of PC Applications using the KMotion Libraries are available in the Software download.  Visual Studio should be used to modify/compile the applications.  Currently the projects are compatible with VS 2008 Standard but later Versions can upgrade the projects and can be used including the free Microsoft Version of VS 2013 Community.  In some cases MFC capability needs to be added as a separate download.
+
A number of PC Applications using the KMotion Libraries are available in the Software download.&nbsp; Visual Studio should be used to modify/compile the applications.&nbsp; Currently the projects are compatible with VS 2008 Standard but later Versions can upgrade the projects and can be used including the free Microsoft Version of VS 2013 Community.&nbsp; In some cases MFC capability needs to be added as a separate download.
  
 
The Install Root directory contains a VS Solution BuildAllLibs.sln to build the KMotion Libraries.
 
The Install Root directory contains a VS Solution BuildAllLibs.sln to build the KMotion Libraries.
  
The VS Solution <install dir>\PC VC Examples\BuildExamples.sln will build most all of the Examples 
+
The VS Solution \PC VC Examples\BuildExamples.sln will build most all of the Examples&nbsp;
  
  
MFC C++ Examples - <install dir>\PC VC Examples
+
MFC C++ Examples - \PC VC Examples
  
 
* KMotionCNC - CNC Application for controlling Mill/Router/Lathe etc
 
* KMotionCNC - CNC Application for controlling Mill/Router/Lathe etc
* Download Waveform - simple example to download some data to the gather buffer
+
* Download Waveform -&nbsp;simple example to download some data to the gather buffer
 
* SimpleCoffload - simple example to compile/download a C Program to KFLOP
 
* SimpleCoffload - simple example to compile/download a C Program to KFLOP
* SimpleConsole - simple example to send [http://www.dynomotion.com/Help/CmdsCategory.htm Console Script commands] to KFLOP
+
* SimpleConsole - simple example to send&nbsp;[http://www.dynomotion.com/Help/CmdsCategory.htm Console Script commands] to KFLOP
 
* SimpleCoordMotion - simple example of creating coordinated motion paths in KFLOP
 
* SimpleCoordMotion - simple example of creating coordinated motion paths in KFLOP
 
* SimpleGCode - simple example to execute a GCode File
 
* SimpleGCode - simple example to execute a GCode File
  
  
C# Examples - <install dir>\PC VC Examples
+
C# Examples - \PC VC Examples
  
 
* KFlopWebNC - HTML CNC based App interfacing to KMotion Libraries
 
* KFlopWebNC - HTML CNC based App interfacing to KMotion Libraries
Line 43: Line 43:
  
  
Visual Basic Examples <install dir>\PC VB Examples
+
Visual Basic Examples \PC VB Examples
  
* DynoMotion VB.net - Demonstrates Coordinated motion, GCode Execution, Status, etc...  
+
* DynoMotion VB.net - Demonstrates Coordinated motion, GCode Execution, Status, etc...
 
* Jogger - Simple VB6 App to Jog Axes
 
* Jogger - Simple VB6 App to Jog Axes
* Jogger.NET - simple VB .NET App to Jog Axes  
+
* Jogger.NET - simple VB .NET App to Jog Axes
  
  
 
+
=Wiring Diagrams=
====
+
C Programs provide a powerful and flexible capability to perform almost any sequence of operations within KFLOP.&nbsp;&nbsp; In most cases after you have tested and tuned all your hardware using the KMotion.exe setup program all the settings and initialization steps required for your system can be placed into an Initialization C Program so that your system can be fully initialized simply by executing the Initialization program. &nbsp; Using a C Program offers full flexibility to initialize your system however and in whatever order you wish.&nbsp; In most common cases an existing example can be used with simple modification of values specific to your system.&nbsp; The KMotion.exe Setup program has some&nbsp;[http://www.dynomotion.com/Help/ConfigurationScreen/ConfigurationScreen.htm#Utilities automatic capability] to translate the Axes Screen Values that were determined by you during configuration and testing into C Code.
C Programs provide a powerful and flexible capability to perform almost any sequence of operations within KFLOP.   In most cases after you have tested and tuned all your hardware using the KMotion.exe setup program all the settings and initialization steps required for your system can be placed into an Initialization C Program so that your system can be fully initialized simply by executing the Initialization program.   Using a C Program offers full flexibility to initialize your system however and in whatever order you wish.  In most common cases an existing example can be used with simple modification of values specific to your system.  The KMotion.exe Setup program has some [http://www.dynomotion.com/Help/ConfigurationScreen/ConfigurationScreen.htm#Utilities automatic capability] to translate the Axes Screen Values that were determined by you during configuration and testing into C Code.
+
  
  
 
The Initialization C Program will normally perform operations of the following type:
 
The Initialization C Program will normally perform operations of the following type:
  
* Enable/define any Option boards present (ie.    KStepPresent=TRUE;      // enable KSTEP input multiplexing)
+
* Enable/define any Option boards present (ie.&nbsp;&nbsp;&nbsp; KStepPresent=TRUE;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; // enable KSTEP input multiplexing)
* The setting of Axes parameters (ie.    ch0->Accel=200000; )
+
* The setting of Axes parameters (ie.&nbsp;&nbsp;&nbsp; ch0-&gt;Accel=200000; )
 
* Enable Axes (ie.EnableAxisDest(0,0); )
 
* Enable Axes (ie.EnableAxisDest(0,0); )
* Define the Coordinated Motion Axes (ie.    DefineCoordSystem(0,1,2,-1);  // define axes for XYZ
+
* Define the Coordinated Motion Axes (ie.&nbsp;&nbsp;&nbsp; DefineCoordSystem(0,1,2,-1);&nbsp; // define axes for XYZ
 
* Forever Loop to service any continuous requirements such as MPG, External Buttons, EStop, etc
 
* Forever Loop to service any continuous requirements such as MPG, External Buttons, EStop, etc
  
  
 +
====Simplest C Program====
 +
It is important to understand that any KFLOP C Program consists of a minimum number of parts as shown below.&nbsp;
  
====Simplest C Program====
+
The first part is an #include statement which includes a definition file that defines all the functionality available in KFLOP.&nbsp; The KMotionDef.h file is included with every installation to define all the functions, variables, structures, and defines available in that Version.&nbsp; It is located in the DSP_KFLOP subdirectory of the installation.&nbsp; Open it with the KMotion.exe C Programs Screen to see what's available.
It is important to understand that any KFLOP C Program consists of a minimum number of parts as shown below. 
+
  
The first part is an #include statement which includes a definition file that defines all the functionality available in KFLOP.  The KMotionDef.h file is included with every installation to define all the functions, variables, structures, and defines available in that Version.  It is located in the DSP_KFLOP subdirectory of the installation.  Open it with the KMotion.exe C Programs Screen to see what's available.
+
The next part is the "main" function. This is where execution of the program will actually begin.&nbsp;
  
The next part is the "main" function. This is where execution of the program will actually begin. 
+
The last part is the code that is to be executed and belongs to the main function.&nbsp; Curly brackets { } define the beginning and end of the function.&nbsp; This example contains only one print statement to be executed. Note how the code within the curly brackets is indented (using a tab or spaces) to show that it belongs to the main function block.&nbsp; This indentation is not required but helps readers see the program structure.&nbsp; Instructions must end with a semicolon ';'. &nbsp; Double forward slashes allow comments to be added at the end of an instruction. &nbsp;
  
The last part is the code that is to be executed and belongs to the main function.  Curly brackets { } define the beginning and end of the function.  This example contains only one print statement to be executed. Note how the code within the curly brackets is indented (using a tab or spaces) to show that it belongs to the main function block.  This indentation is not required but helps readers see the program structure.  Instructions must end with a semicolon ';'.   Double forward slashes allow comments to be added at the end of an instruction.  
 
  
  
#include "KMotionDef.h"<br />main()<br />{<br />    printf("Hello World!\n");  // send message to console<br />}
+
# include "KMotionDef.h"<br/>main()<br/>{<br/>&nbsp;&nbsp; &nbsp;printf("Hello World!\n");&nbsp; // send message to console<br/>}
  
  
==<br />Wiring Diagrams==
+
==<br/>Wiring Diagrams==
 
[[Media:Kanalog_Connections.pdf|Basic Kanalog DAC and Encoder Connections 3 Axis]]
 
[[Media:Kanalog_Connections.pdf|Basic Kanalog DAC and Encoder Connections 3 Axis]]
  

Revision as of 22:33, 11 October 2015

Dynomotion wiki

Find and share information on Dynomotion Systems.  Please feel free to contribute and correct information yourself.  Joining is not required to View or Search for information.  You will need to Register and confirm your email account before having permission to edit or add pages.  By default WYSIWYG editing is enabled.  Standard MediaWiki editing may also be used or set as the default in your User Preferences.

Warning: Use at your own risk.  Information is for example purposes only and may contain errors.  It is up to the User to verify the information is correct and safe to use. In no cases will any contributor or Dynomotion be liable for incorrect information.

Thanks for Contributing!

Official Dynomotion Site

Board Info

SnapAmp Hardware Info

Kanalog Hardware Info


Software Test Releases

V4.33q


PC Example Applications

A number of PC Applications using the KMotion Libraries are available in the Software download.  Visual Studio should be used to modify/compile the applications.  Currently the projects are compatible with VS 2008 Standard but later Versions can upgrade the projects and can be used including the free Microsoft Version of VS 2013 Community.  In some cases MFC capability needs to be added as a separate download.

The Install Root directory contains a VS Solution BuildAllLibs.sln to build the KMotion Libraries.

The VS Solution \PC VC Examples\BuildExamples.sln will build most all of the Examples 


MFC C++ Examples - \PC VC Examples

  • KMotionCNC - CNC Application for controlling Mill/Router/Lathe etc
  • Download Waveform - simple example to download some data to the gather buffer
  • SimpleCoffload - simple example to compile/download a C Program to KFLOP
  • SimpleConsole - simple example to send Console Script commands to KFLOP
  • SimpleCoordMotion - simple example of creating coordinated motion paths in KFLOP
  • SimpleGCode - simple example to execute a GCode File


C# Examples - \PC VC Examples

  • KFlopWebNC - HTML CNC based App interfacing to KMotion Libraries
  • KMotion_dotNet Console - Windows Console App using .NET Library Interface
  • MeasureFiducials - Video Alignment Application to measure fiducial alignment marks and map coordinte space
  • SimpleFormsCS - Simple Windows C# Forms App includes USB speed test
  • TeachMotion - App for use with Lathe Spinners to teach Spinning motion and create GCode


Visual Basic Examples \PC VB Examples

  • DynoMotion VB.net - Demonstrates Coordinated motion, GCode Execution, Status, etc...
  • Jogger - Simple VB6 App to Jog Axes
  • Jogger.NET - simple VB .NET App to Jog Axes


Wiring Diagrams

C Programs provide a powerful and flexible capability to perform almost any sequence of operations within KFLOP.   In most cases after you have tested and tuned all your hardware using the KMotion.exe setup program all the settings and initialization steps required for your system can be placed into an Initialization C Program so that your system can be fully initialized simply by executing the Initialization program.   Using a C Program offers full flexibility to initialize your system however and in whatever order you wish.  In most common cases an existing example can be used with simple modification of values specific to your system.  The KMotion.exe Setup program has some automatic capability to translate the Axes Screen Values that were determined by you during configuration and testing into C Code.


The Initialization C Program will normally perform operations of the following type:

  • Enable/define any Option boards present (ie.    KStepPresent=TRUE;      // enable KSTEP input multiplexing)
  • The setting of Axes parameters (ie.    ch0->Accel=200000; )
  • Enable Axes (ie.EnableAxisDest(0,0); )
  • Define the Coordinated Motion Axes (ie.    DefineCoordSystem(0,1,2,-1);  // define axes for XYZ
  • Forever Loop to service any continuous requirements such as MPG, External Buttons, EStop, etc


Simplest C Program

It is important to understand that any KFLOP C Program consists of a minimum number of parts as shown below. 

The first part is an #include statement which includes a definition file that defines all the functionality available in KFLOP.  The KMotionDef.h file is included with every installation to define all the functions, variables, structures, and defines available in that Version.  It is located in the DSP_KFLOP subdirectory of the installation.  Open it with the KMotion.exe C Programs Screen to see what's available.

The next part is the "main" function. This is where execution of the program will actually begin. 

The last part is the code that is to be executed and belongs to the main function.  Curly brackets { } define the beginning and end of the function.  This example contains only one print statement to be executed. Note how the code within the curly brackets is indented (using a tab or spaces) to show that it belongs to the main function block.  This indentation is not required but helps readers see the program structure.  Instructions must end with a semicolon ';'.   Double forward slashes allow comments to be added at the end of an instruction.  


  1. include "KMotionDef.h"
    main()
    {
        printf("Hello World!\n");  // send message to console
    }



Wiring Diagrams

Basic Kanalog DAC and Encoder Connections 3 Axis

Basic Kanalog DAC and Encoder Connections 3 Axis #2

KFLOP+SnapAmp DC Brush Motors with MPG

KFLOP JP5 Open Collector Step/Dir Connections to Power Step PSD5042-2P Drives