Dynomotion - User contributions [en]

Main Page

2025-12-20T20:30:49Z

TK: /* 3D Board Models added SnapAmp Step files */

=='''Dynomotion wiki'''''' '''==
Welcome to our wiki where you can find and share knowledge on Dynomotion's systems. To begin adding information to this wiki, simply create an account, verify your email, and start editing (click pencil icon). To make editing pages easier for everyone, we have installed a [https://help.bluespice.com/index.php/VisualEditor visual editor] by default. This visual editor allows you to edit a wiki page much like you would a standard word processing document.  For the seasoned wiki editors, standard [https://www.mediawiki.org/wiki/Help:Editing MediaWiki editing] may also be used.<nowiki> </nowiki>

''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 is safe to use. In no case will any contributor or Dynomotion be liable for incorrect information. Dynomotion reserves the right to modify or delete any contributions. ''

 Thanks for Contributing!

[http://dynomotion.com Official Dynomotion Site]

==Editing and Creating Wiki Pages==
Unintuitively, you first create a link to the page you want to make before you can make the page. To make a new page: while editing, right-click where you want your link to be, insert a link with a descriptive title and link text, save the page, click on the link you created, then click on "Empty Page" to begin editing your new page.

Here are a few other quick tips:

* You can insert links or images by Right-Clicking with the mouse on the line where you want the link or image to appear.
* For Spell Correction you can use Ctrl-Right-Click.
* To insert a YouTube Video use an EmbedVideo command such as <nowiki> {{#ev:youtube|xxxxx}}
</nowiki>with xxxxx changed to the Video ID.
* Choose a descriptive page name and link text when creating a new page: e.g. Not "My Machine", but rather "Brand X Three Axis Milling Machine Retrofit"
* Create pages in an organized manner: Describe what the page is about, create clear sections that flow

For more information:

[[Help:New Page Creation|How to create a new wiki page]]

[[Help:Editing Pages|How to Edit and insert Media into your wiki pages]]

==Dynomotion Software Topics==
===Installation Topics===
* Announcement of our Latest Release (5.4.1) on the [https://www.dynomotion.com/forum/viewtopic.php?f=4&t=1884 Dynomotion Forum]
* [https://dynomotion.com/Software/Download.html Latest Release] Note: For Windows 7 64bit signed Drivers to work, all Windows Updates should be performed.
* [[Upgrading from previous KMotion Versions]]

Archive of Test Releases:

* Previous Test Release: 06/03/2025: [https://dynomotion.com/Software/KMotion5.4.0.exe KMotion.exe 5.4.0], See the release notes for this test version here: [https://dynomotion.com/Software/KMotion%20Released%20Version%205.4.0%20Changes.pdf 5.4.0 release notes (pdf)]

* Previous Test Release: 04/08/2025: [https://dynomotion.com/Software/KMotion5.3.8.exe KMotion.exe 5.3.8], See the release notes for this test version here: [https://dynomotion.com/Software/KMotion%20Released%20Version%205.3.8%20Changes.pdf 5.3.8 release notes (pdf)]

* Previous Test Release: 01/14/2025: [https://dynomotion.com/Software/KMotion5.3.7.exe KMotion.exe 5.3.7], See the release notes for this test version here: [https://dynomotion.com/Software/KMotion%20Released%20Version%205.3.7%20Changes.pdf 5.3.7 release notes (pdf)]

* Previous Test Release: 09/30/2024: [https://dynomotion.com/Software/KMotion5.3.6.exe KMotion.exe 5.3.6], See the release notes for this test version here: [https://dynomotion.com/Software/KMotion%20Released%20Version%205.3.6%20Changes.pdf 5.3.6 release notes (pdf)]

* Previous Test Release: 09/16/2024: [https://dynomotion.com/Software/KMotion5.3.5.exe KMotion.exe 5.3.5], See the release notes for this test version here: [https://dynomotion.com/Software/KMotion%20Released%20Version%205.3.5%20Changes.pdf 5.3.5 release notes (pdf)]

* Previous Test Release: 08/13/2024: [https://dynomotion.com/Software/KMotion5.3.4.exe KMotion.exe 5.3.4], See the release notes for this test version here: [https://dynomotion.com/Software/KMotion%20Released%20Version%205.3.4%20Changes.pdf 5.3.4 release notes (pdf)]

* Previous Test Release: 04/04/2024: [https://dynomotion.com/Software/KMotion5.3.3.exe KMotion.exe 5.3.3], See the release notes for this test version here: [https://dynomotion.com/Software/KMotion%20Released%20Version%205.3.3%20Changes.pdf 5.3.3 release notes (pdf)]

* Previous Test Release: 02/01/2024: [https://dynomotion.com/Software/KMotion5.3.2.exe KMotion.exe 5.3.2], See the release notes for this test version here: [https://dynomotion.com/Software/KMotion%20Released%20Version%205.3.2%20Changes.pdf 5.3.2 release notes (pdf)]

* Previous Test Release: 11/20/2023: [https://dynomotion.com/Software/KMotion5.3.1.exe KMotion.exe 5.3.1], See the release notes for this test version here: [https://dynomotion.com/Software/KMotion%20Released%20Version%205.3.1%20Changes.pdf 5.3.1 release notes (pdf)]
* Previous Test Release: 09/19/2023: [https://dynomotion.com/Software/KMotion5.3.0.exe KMotion.exe 5.3.0], See the release notes for this test version here: [https://dynomotion.com/Software/KMotion%20Released%20Version%205.3.0%20Changes.pdf 5.3.0 release notes (pdf)]
* Previous Test Release: 06/30/2023: [https://dynomotion.com/Software/KMotion5.1.0.exe KMotion.exe 5.1.0], See the release notes for this test version here: [https://dynomotion.com/Software/KMotion%20Released%20Version%205.1.0%20Changes.pdf 5.1.0 release notes (pdf)]
* Previous Test Release: 05/01/2023: [https://dynomotion.com/Software/KMotion5.0.7.exe KMotion.exe 5.0.7], See the release notes for this test version here: [https://dynomotion.com/Software/KMotion%20Released%20Version%205.0.7%20Changes.pdf 5.0.7 release notes (pdf)]
* Previous Test Release: 09/21/2022: [https://dynomotion.com/Software/KMotion435h.exe KMotion.exe V4.35h], See the release notes for this test version here: [https://dynomotion.com/Software/KMotion%20Released%20Version%204.35h%20Changes.pdf V4.35h release notes (pdf)]
* Previous Version 4.35g was not released, but see the change notes for this version here: [https://dynomotion.com/Software/KMotion%20Released%20Version%204.35g%20Changes.pdf V4.35g change notes (pdf)]
* Previous Test Release: 12/28/2020: [https://dynomotion.com/Software/KMotion435f.exe KMotion.exe V4.35f], See the release notes for this test version here: [https://dynomotion.com/Software/KMotion%20Released%20Version%204.35f%20Changes.pdf V4.35f release notes (pdf)]
* Previous Test Release: 11/18/2019: [https://dynomotion.com/Software/KMotion435e.exe KMotion.exe V4.35e], See the release notes for this test version here: [https://dynomotion.com/Software/KMotion%20Released%20Version%204.35e%20Changes.pdf V4.35e release notes (pdf)]
* Previous Test Release: 09/10/2019: [https://dynomotion.com/Software/KMotion435d.exe KMotion.exe V4.35d], See the release notes for this test version here: [https://dynomotion.com/Software/KMotion%20Released%20Version%204.35d%20Changes.pdf V4.35d release notes (pdf)]
* Previous Test Release: 01/28/2019: [https://dynomotion.com/Software/KMotion435b.exe KMotion.exe V4.35b], See the release notes for this test version here: [https://dynomotion.com/Software/KMotion%20Released%20Version%204.35b%20Changes.pdf V4.35b release notes (pdf)]
* Previous Test Release: 12/21/2018: [https://dynomotion.com/Software/KMotion435a.exe KMotion.exe V4.35a], See the release notes for this test version here: [https://dynomotion.com/Software/KMotion%20Released%20Version%204.35a%20Changes.pdf V4.35a release notes (pdf)]
* Previous Test Release: 09/28/2017: [https://dynomotion.com/Software/KMotion434j.exe KMotion.exe V4.34j], See the release notes for this test version here: [https://dynomotion.com/Software/KMotion%20Released%20Version%204.34j%20Changes.pdf V4.34j release notes (pdf)]
* Previous Test Release: 05/07/2017: [https://dynomotion.com/Software/KMotion434i.exe KMotion.exe V4.34i], See the release notes for this test version here: [https://dynomotion.com/Software/KMotion%20Released%20Version%204.34i%20Changes.pdf V4.34i release notes (pdf)]
* Previous Test Release: 12/14/2016: [https://dynomotion.com/Software/KMotion434h.exe KMotion.exe V4.34h], See the release notes for this test version here: [https://dynomotion.com/Software/KMotion%20Released%20Version%204.34h%20Changes.pdf V4.34h release notes (pdf)]
* Previous Test Release: 12/13/2016: [https://dynomotion.com/Software/KMotion434g.exe KMotion.exe V4.34g], See the release notes for this test version here: [https://dynomotion.com/Software/KMotion%20Released%20Version%204.34g%20Changes.pdf V4.34g release notes (pdf)]
* Previous Test Release: 12/05/2016: [https://dynomotion.com/Software/KMotion434f.exe KMotion.exe V4.34f], See the release notes for this test version here: [https://dynomotion.com/Software/KMotion%20Released%20Version%204.34f%20Changes.pdf V4.34f release notes (pdf)]
* Previous Test Release: 11/07/2016: [https://dynomotion.com/Software/KMotion434e.exe KMotion.exe V4.34e], See the release notes for this test version here: [https://dynomotion.com/Software/KMotion%20Released%20Version%204.34e%20Changes.pdf V4.34e release notes (pdf)]
* Previous Test Release: 10/32/2016: [https://dynomotion.com/Software/KMotion434d.exe KMotion.exe V4.34d], See the release notes for this test version here: [https://dynomotion.com/Software/KMotion%20Released%20Version%204.34d%20Changes.pdf V4.34d release notes (pdf)]
* Previous Test Release: 10/23/2016: [https://dynomotion.com/Software/KMotion434c.exe KMotion.exe V4.34c], See the release notes for this test version here: [https://dynomotion.com/Software/KMotion%20Released%20Version%204.34c%20Changes.pdf V4.34c release notes (pdf)]
* Previous Test Release: 10/03/2016: [https://dynomotion.com/Software/KMotion434b.exe KMotion.exe V4.34b], See the release notes for this test version here: [https://dynomotion.com/Software/KMotion%20Released%20Version%204.34b%20Changes.pdf V4.34b release notes (pdf)]
* Previous Test Release: 03/09/2016: [https://dynomotion.com/Software/KMotion434a.exe KMotion.exe V4.34a], See the release notes for this test version here: [https://dynomotion.com/Software/KMotion%20Released%20Version%204.34a%20Changes.pdf V4.34a release notes (pdf)]
* [https://dynomotion.com/Help/KFLOPQuickStart/KFLOPQuickStart.htm How to install KMotion.exe and KMotionCNC]
* [[How to install KMotion.exe and KMotion in Windows 10|Preparing Windows 10 for driver installation]] (no longer required)
* [[Special Case for Windows 8.1 Industry Embedded Enterprise]]
* [[Updating KFLOP Firmware|How to update KFLOP Firmware]] - whenever a new version of software is installed, the firmware within KFLOP must be updated to match the new version

===KMotion.exe Executive Software Topics===
KMotion.exe is the main program that is used to configure settings in KFLOP, initialize axes, and to write C programs to configure and setup KFLOP to control your system. In this program you can plot step response, test movement, view Bode plots, monitor I/O, set filter parameters, and generally set the pertinent parameters.

* [http://www.dynomotion.com/Help/index.htm General software information] from the manuals
* Insert pages for other KMotion.exe-related topics here

===Configuration Topics===
====Channels, Channels, Channels what are they?====
[[Channels Channels Channels|Read Article Here]]

====How to Setup Backlash Compensation====
[[Backlash Compensation|Read Article Here]]

====PWM Output Mode====
[[PWM Output Mode|Read Article Here]]

===KMotionCNC Software Topics===
KMotionCNC is Dynomotion's CNC program used as a graphical user interface to your KFLOP-enabled machine tool. KMotionCNC has all of the basic functionality you need to run a machine of up to 6 axes, in addition to spindle control.

* Insert pages for other KMotionCNC-related general topics here

====Using KMotionCNC====
* Homing discussion - page to be created
* Insert other KMotionCNC use pages here

[[Internal/concave Path Tool Radius Compensation Example G41/G42]]

[[Known KMotionCNC CAD/CAM Post Processors]]

[[Invoking C Programs with Execute Only for previously Downloaded Programs]]

[[Rigid Tapping G84 Setup and Use]]

[[Tool Length/Offsets G43Hn G49]]

====Customize KMotionCNC====
KMotionCNC is written as a Windows C++ MFC (Microsoft Foundation Classes) program developed in Visual Studio. Source code is provided and may be customized using Visual Studio. MFC Support is a requirement.

: '''General Information'''
: Compiling KMotionCNC
:: The KMotionCNC's Visual Studio Project Solution (\PC VC Programs\KMotionCNC\KMotionCNC.sln) is currently written for Visual Studio 2015 Standard. This version can be used for the simplest compatibility. Projects can be upgraded to newer version of VS with minimal effort. Including Microsoft's Free Visual Studio 2013 Community. [[PC Example Applications|More info on PC Example Applications.]]
:: Note Test Versions 4.34a and later have project solutions targeted for Visual Studio 2015 Community which is free for most Users.
: '''KMotionCNC Customization Examples and Applications'''
:: Links to examples of projects that explain KMotionCNC customizations. Troy (tmday7) created some helpful documents (PDF format):
:
:* [https://www.dynomotion.com/forum/archive/attachments/How%20to%20Edit%20KMotionCNC%20Faces.pdf How to edit KMotionCNC faces]
:* [https://www.dynomotion.com/forum/archive/attachments/Adding%20External%20Buttons.pdf Adding external buttons]
:* [https://www.dynomotion.com/forum/archive/attachments/Adding%20More%20User%20Buttons.pdf Adding more user buttons]
:* [https://www.dynomotion.com/forum/archive/attachments/Adding%20Jog%20Percent%20Cell%20to%20Main%20Dialog%20Face.pdf Adding Jog Percent Cell to Main Dialog Face]
====KMotionCNC Screen Editor====
Introduces the capability of using Screen Script files to modify the look and function of KMotionCNC. [[KMotionCNC Screen Editor|More information.]]

====KMotionCNC Geometric Correction====
Information regarding the powerful [https://dynomotion.com/Help/KMotionCNC/GeoCorrection.htm Geometric Correction capability] which allows calibration and distortion correction of the XY CAD space to Machine/Actuator Space as well as flatness in Z. Simple 4 point correction tables can apply XY Scale, Rotation, skew, offset, tilt. Larger tables can apply more non-linear corrections.

Note the Geometric Correction is built into the KMotion Libraries and can be utilized by Custom Programs as well as with KMotionCNC [[Geometric Correction|More information and Examples.]]

====KMotionCNC Linear Table Correction (Screw Mapping)====
Individual Axes can be corrected in a 1 dimensional manner referred to as Linear Table Corrections. For more information See [[Linear Table Correction|here]].

===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. 

'''Note All the projects should work out-of-the-box with Visual Studio 2022.'''

[[PC Example Applications|More information.]]

===KMotion Libraries - GCode Interpreter - Trajectory Planner - Coordinated Motion - .NET===
The KMotion Libraries are a series of DLLs (Dynamic Link Libraries) that reside on the PC that contain the common core motion control, I/O, and communication functionality for KFLOP. These libraries permit PC Applications to be built using high level control without being concerned with the underlying details of Interpreting GCode, Trajectory Planning, Coordinated Motion, Motion Buffering, USB Communication, etc.

[[KMotion Libraries - GCode Interpreter - Trajectory Planner - Coordinated Motion - .NET|More information]].

===Kinematics===
The KMotion Libraries contain a Kinematics Layer where Users can add their own non-linear Kinematics

[[Kinematics|More information]].

===KFLOP C Programs===
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.

[[KFLOP C Programs|More Information]]

===ModBus===
Modbus can be connected to the PC or directly to KFLOP. A PC connection will not be deterministically real-time but may work for basic speed control and on/off. Here is a related Thread for interfacing KMotionCNC to Modbus using a [http://www.modbusdriver.com/modpoll.html free utility]:

[https://www.dynomotion.com/forum/archive/sending%20ModBus%20msgs%20from%20KmotionCNC%20to%20a%20RS485%20port.html Sending ModBus msgs from KmotionCNC to a RS485 port]

To connect Modbus directly to KFLOP's [http://www.dynomotion.com/Help/RS232/RS232.htm UART] see the C Examples in \C Programs\RS232\ModBus\

===Linux Support===
KMotion Motion Libraries are fully supported under Microsoft Windows. Some Users have ported the KMotion Libraries to Linux. Dynomotion will offer support where possible but can't offer full support under Linux. Special Thanks to [https://github.com/parhansson/KMotionX Par Hansson] for the initial Linux Port.

See [[Linux|here]] for more info.

==Dynomotion Hardware Topics==
===General Hardware Information===
====[[KFLOP Hardware Info|KFLOP specific Hardware Info]]====
====[[KStep Hardware Info|KStep specific Hardware Info]]====
====[[Kanalog Hardware Info|Kanalog specific Hardware Info]]====
====[[SnapAmp Info|SnapAmp specific Hardware Info]]====
====[[Konnect Hardware Info|Konnect specific Hardware Info]]====
===Wiring Diagrams===
[[Media:Kanalog_Connections.pdf|Basic Kanalog DAC and Encoder Connections 3 Axis]]

[[Media:KanalogSchematic3Axis.pdf|Basic Kanalog DAC and Encoder Connections 3 Axis #2]]

[[Media:dyn4 kanalog KE1524 V1.1.png|Basic Kanalog DAC and DMM DYN4 Drive 1 Axis]]

[[Media:Kflop-Kanalog_wiring_11-19-2018.pdf|Kanalog with Geckos G210 updated 11-19-2018]] (Thanks to Joseph Mirocha)

[[Media:Kanalog_to_Tree_Journeyman_325_by_Rick_B.pdf|Kanalog to Tree Journeyman 325.pdf]] (Thanks to Rick_B)

[[Media:KFlopSnapBrushMPG.pdf|KFLOP+SnapAmp DC Brush Motors with MPG]]

[[Media:Stepper_Wiring_Diagram_Step-Dir_on_JP5.pdf|KFLOP JP5 Open Collector Step/Dir Connections to Power Step PSD5042-2P Drives ]]

[[Media:Matrika_V1_wiring_diagram_Rev1.pdf|KFLOP+KStep with VFD and NPN Limit Switches for Matrika Rev1]]

[[Media:KonnectTouchPlate.png|Touch Plate Wiring to Konnect]]

[https://easyeda.com/350banshee/BreakoutBoard-93bdd16e3c3d48b98ae66c34f2436c40 User Created KFLOP JP7 Breakout/OptoIsolation Board] Schematic, Gerbers, PCBs Publicly available (thanks 350banshee)

[https://www.dynomotion.com/wiki/index.php?action=ajax&title=-&rs=SecureFileStore::getFile&f=/b/bb/RotarySwitchToKanalog.png Rotary Switch Connected to Kanalog Opto Inputs]

===3D Board Models===
[[Media:kflop-kstep-3d-models-1.snapshot.3.zip.txt|kflop-kstep-3d-models-1.snapshot.3.zip.txt]] STEP file format - Thanks to Curtis

[[File:kflop_kstep_render.JPG|none|link=|329x329px]]

[[Media:KFLOP3D_Step_IGS_Chris.zip.txt|KFLOP3D_Step_IGS_Chris.zip.txt]] STEP and IGS models - Thanks to Chris

[[File:KFLOP_3D.png|none|link=|413x296px]]

[[Media:KONNECT_BOARD_MODEL.zip.txt|KONNECT_BOARD_MODEL.zip.txt]] STEP model - Thanks to Jeff Redington

(Component locations may be off one way or another by .5mm)

[[File:Konnect_Board.png|none|link=|339x292px]]

Konnect Basic Step file showing hole locations

[[Media:KonnectHoles.stp.txt|KonnectHoles.stp.txt]]

[[File:KonnectHoles.png|none|link=|352x323px]]

Kanalog Step Model with Mechanical hole and Pin locations

[[Media:Kanalog.stp.txt|Kanalog.stp.txt]]

[[File:KanalogFromStep.png|none|link=|304x279px]]

Kanalog Step Model with Mechanical hole and Connectors (Thanks to

Roberto Gotti of Powertech)''' '''

[[Media:KANALOG_BOARD.stp.txt|KANALOG_BOARD.stp.txt]]

[[File:KanalogWithConnectors.png|none|link=|311x286px]]

SnapAmp 3D Step Model - Thanks to Isaac

[[Media:SnapAmp.stp.txt|SnapAmp.stp.txt]]

[[File:SnapAmp_Step.png|none|link=]]

[[Media:KFlop_2SnapAmp.stp.txt|2 Snap Amps added to Curtis's KFLOP STEP model - Thanks to Isaac]]

[[Media:KFlop_2SnapAmp.stp.txt|KFlop_2SnapAmp.stp.txt]]

[[File:KFLOP_2SnapAmp_Step.png|none|link=]]

===Board Terminal DXF/DWG files===
[[Media:KFLOP_Terminals.dxf|KFLOP_Terminals.dxf]] [[Media:KFLOP_Terminals.dwg|KFLOP_Terminals.dwg]]

[[Media:Kanalog_Terminals.dxf|Kanalog_Terminals.dxf]] [[Media:Kanalog_Terminals.dwg|Kanalog_Terminals.dwg]]

[[Media:Konnect_Terminals.dxf|Konnect_Terminals.dxf]] [[Media:Konnect_Terminals.dwg|Konnect_Terminals.dwg]]

[[Media:KStep_Terminals.dxf|KStep_Terminals.dxf]] [[Media:KStep_Terminals.dwg|KStep_Terminals.dwg]]

===Wiring Topics===
Place links to pages on wiring inputs and

outputs specific to your experiences and projects. Be descriptive with page titles and links.

====KFLOP IDC Connectors and Cables====
Cables that connect between Dynomotion boards are normally included when purchasing the boards together. They are also very common and easy to make. Use '''16-conductor or 26-conductor ribbon cable''' (0.05 inch pitch 26 AWG preferrably or 28AWG) and IDC sockets. [[File:RibbonCable.png|none|link=]]16 conductor ribbon cable 3M part number 3801/16 100 https://www.digikey.com/product-detail/en/3m/3801-16-100/3M156105-100-ND/1107501 26 conductor ribbon cable 3M part number C3801/26 100 https://www.digikey.com/product-detail/en/3m/C3801-26-100/C3801-26-100-ND/1107648 Winford also sells ribbon cable (although only the thinner 28 AWG): http://www.winford.com/products/rib.php Note you can usually tear off wires to reduce the number of conductors. For example from 26 down to 16. Tear off the conductors away from the red stripe that marks pin 1. The '''crimp tools''' are common: https://www.amazon.com/Accessories-Crimp-Ribbon-Cable-Connectors/dp/B007R2JEM4/ [[File:RibbonCrimp.png|none|link=]] '''IDC Sockets 16-pin '''(pin pitch 0.1 inch) https://www.digikey.com/product-detail/en/assmann-wsw-components/AWP-16-7240-T/HHKC16H-ND/5031953 Assman Part number AWP 16-7240-T[[File:16pinIDC.png|none|link=]]
https://www.digikey.com/product-detail/en/assmann-wsw-components/AWP-26-7240-T/HHKC26H-ND/5011313
[[File:26pinIDC.png|none|link=]]

====KFLOP KStep JR1 Molex Power Connectors====
KFLOP and KStep JR1 are standard Disk Drive Power Connectors. Possibly one of the most common connectors. Originally used on PC ATX Power Supplies. Sometimes referred to as Molex Connectors. They have 4 pins with 0.2 inch pitch with 0.083~0.084 inch socket pins. The mating cable will have female socket pins as shown here:

[[File:Molex_female_connector.jpg|none|link=|251x168px]]

Molex Series 8981 P# [https://www.digikey.com/short/zjp329 0015244048] using Molex Series 8980 Crimp Pins P# [https://www.digikey.com/short/zjp3ff 0002081201]

Also AMP Series MATE-N-LOK P# [https://www.digikey.com/short/zjpq3n 1-480424-0] using AMP Series MATE-N-LOK Crimp Pins P# [https://www.digikey.com/short/zjpqqw 60619-1] or P# [https://www.digikey.com/en/products/detail/molex/0194200002/2404783 194200002]

Molex Crimp Tool P# [https://www.digikey.com/en/products/detail/molex/0640160035/665311 0640160035]

====MPG Wiring and Interface====
MPGs (Manual Pulse Generators) should be connected directly to KFLOP for guaranteed real-time response (not USB based or connected to the PC). MPGs are handled by a C Program that monitors the MPG and creates motion based on the MPG Encoder changes and switch selections for axis, speed, and so forth. See the MPG C Program Examples. Here is a Discussion with other links.

[https://www.dynomotion.com/forum/archive/Jogging%20Pendant.html Jogging Pendant]

[https://www.dynomotion.com/forum/archive/Connecting%20Keling%20MPG2%20pendant.html Connecting Keling MPG2 Pendant]

[https://www.cnczone.com/forums/dynomotion-kflop-kanalog/349740-applying-acceleration-mpg-target-possible.html#post2119732 CNCZone Thread] on obtaining smooth filtered motion.

[[File:MPG4_from_cnc4pc.jpg|none|link=|83x169px]]

====Interfacing NPN Devices to KFLOP IO====
NPN devices (open collector)operate as a switch to GND and can be interfaced to KFLOP using a pull up resistor as shown below. When the transistor switches to 0V the KFLOP IO Pin is driven low. The transistor will need to sink ~3ma. When the transistor is off (open circuit) the resistor pulls the IO Pin to 3.3V. Note even though some KFLOP IO Pins can tolerate 5V pulling them above 3.8V should be avoided when possible so the 3.3V supply is used. This technique will only work with KFLOP IO Pins that do not have pull down resistors (JP7 and JP5). In some cases a 0.1uF Ceramic capacitor connected close to KFLOP might be added in parallel with the resistor to filter noise. Cable shielding connected to KFLOP GND on the KFLOP end only is recommended. Note that in noisy environments this technique may couple noise into KFLOP so opto isolation should be used instead.

[[File:NPN_Interface_to_KFLOP.png|none|link=|544x544px]]

====Multiplexing Encoder Inputs to KFLOP JP4 and JP6====
If KFLOP JP7 and JP5 are used for other purposes the encoder inputs can be multiplexed to KFLOP JP4 and JP6. There is an option to multiplex encoders 0-3 from JP7 to JP4 and another option to multiplex encoders 4-7 from JP5 to JP6. See the MuxEncoders.c for an example.

Note the JP4 and JP6 IO are 3.3V inputs and shouldn't be driven hard (more than 10ma) above 3.8V. This is not usually an issue as most encoders or RS422 drivers don't do this. The inputs also have 150 ohm termination.

The following line of code might be added to your Initialization C Program. It needs to be executed once to multiplex the encoders after any power cycle. Encoders 0-3 will then be input on JP4 and 4-7 will be on JP6. Both JP4 and Jp6 have 10 IO bits. The 4 encoders will appear on the first 8 IO bits. 2 bits for each encoder's A B channels in order. So for example Encoder #0 will appear on JP4 IO16 (Pin5) and IO17 (Pin6)

<pre class="brush:c">
// Mux encoder inputs from KFLOP JP7 & JP5 to JP4 and JP6
FPGAW(ENC_NOISE_FILTER_ADD) = ENC_0_3_JP4 + ENC_4_7_JP6 + ENC_NOISE_FILTER_DEFAULT_VAL; </pre>

JP4 and JP6 have +5V available on Pin1 and GND on Pins 8 and 9 that might be used to power 5V encoders.

==Axes Servo Tuning and Trajectory Planner==
===Basic Servo Tuning Overview===
Once an axis is configured and proved capable of holding a position it is ready to be tuned and optimized. Most often a small value of P Gain only is used to show the servo is functional and can hold position. The Servo may be very weak and inaccurate but will be functional.

Every system is different and the tuning parameters are interactive in a manner that usually doesn't allow parameters to be determined one at a time. Rather after one parameter is changed it may be necessary to revisit the other parameters.

In general higher gains will reduce errors and improve accuracy, but tend to make the system more unstable. So the general idea is to increase gains to reduce errors as much as possible but still have a stable system.

Often during tuning the system may go unstable. In fact, it is normally intentionally driven to instability to find its limits for a certain parameter. This can result in a violent oscillation or worse so one should be prepared to quickly disable the Servo. If an appropriate [http://dynomotion.com/Help/ConfigurationScreen/ConfigurationScreen.htm#Max_Following_Error Max Following Error] is used the axis can be automatically disabled before the oscillation becomes too violent, yet not disable when performing a normal test.

KMotion.exe allows you to change any axis parameter on the Step/Response, Config, or Filters Screens then simply push "Move" to see the effect of the change. Note that as performance improves the errors will become small and difficult to see on the Position Plot without Zooming in (Left click drag) so changing the plot type to plot the error is useful.

The overall process normally goes something like this:

# Select a Test [http://dynomotion.com/Help/StepScreen/StepScreen.htm#Measurement Move Size] and [http://dynomotion.com/Help/StepScreen/StepScreen.htm#Motion_Profile Motion Profile]. [http://www.dynomotion.com/wiki/index.php?title=Main_Page#Velocity.2C_Acceleration.2C_and_Jerk See Also]
# Select [http://dynomotion.com/Help/StepScreen/StepScreen.htm#max_limits Max Limits] to allow for the Test. [http://www.dynomotion.com/wiki/index.php?title=Main_Page#Max_Limits_-_Error See Also]
# Determine maximum level of [http://dynomotion.com/Help/StepScreen/StepScreen.htm#PID P Gain]
# Determine maximum level of [http://dynomotion.com/Help/StepScreen/StepScreen.htm#PID D Gain] (with Low Pass Filtering) See Also [http://www.dynomotion.com/wiki/index.php?title=Main_Page#Torque_Servos_vs_Velocity_Servos here] and [http://www.dynomotion.com/wiki/index.php?title=Main_Page#Lead_Compensator_vs_Derivative_Gain here].
# Determine new maximum level of P Gain now that D Gain increased stability
# Add I Gain to improve accuracy and remove steady state errors. [http://www.dynomotion.com/wiki/index.php?title=Main_Page#I_Gain.2FMax_Limit_Integrator See Also]
# Add [http://dynomotion.com/Help/StepScreen/StepScreen.htm#Feed_Forward Feed Forward] to reduce errors

===Torque Servos vs Velocity Servos===
+/-10V Analog Amplifiers usually come in one of two varieties: '''Torque''' or '''Velocity'''. Torque mode amplifiers consider the input command as a Torque Command and work to generate the commanded Motor Torque. Velocity mode amplifiers consider the input command as a Velocity Command and work to generate the commanded Velocity. Its important to understand what type of Amplifiers you have.

'''Velocity Mode Amplifiers''' need some form of feedback going to the Amplifier in order for the drive to know the current velocity. This might be a digital encoder or an analog tachometer.

Its easy to tell if you have a Velocity Mode Amplifier by looking at a plot of a move on the Step Response Screen. The Output (green plot with right scale) will be proportion to the motor velocity. When moving at constant speed the output will be relatively constant. See in the plot below the output (green) remains at a relatively constant ~1100 DAC counts while the position (red) ramps at a constant slope of the 90000 count/sec rate:

[[File:VelocityAmp.png|none|link=]]

Velocity mode amplifiers can be relatively easy to tune using only P (Proportional) Gain. Additional Gains and filters can be used for best performance but using only P Gain will often result in reasonable performance and a stable system (unlike Torque Mode Amplifiers).

As an example consider controlling the speed of a car using only Proportional Gain as it approaches a target (Stop sign). Consider a P Gain of 0.1 where at 1000ft from the stop sign we command 1000 x 0.1 = 100MPH. Then at 100ft we command 10MPH. Then at 10ft we command 1MPH. This results in a nice, smooth, exponential approach, without overshoot.

Contrast this with controlling the acceleration (torque) of a car using only Proportional Gain as it approaches a target (Stop sign). At large distance we apply maximum acceleration. Although as we approach the stop sign we reduce acceleration, we continue to accelerate and speed continues to increase until we pass the stop sign. Torque mode servos are inherently unstable. P only gain only works at all if there is some friction (the car is dragging a sled which slows us down with less torque).

'''Acceleration Mode Servos''' may or may not have any feedback. If they have feedback it is usually used only to commutate a brushless motor. In the plots the Output (green) will have large magnitude when the Position (red) is accelerating, where the plot has curvature (changing slope).

Acceleration mode Servos are unlikely to work well or at all with only P Gain. Some form of damping or lead compensation will usually be required to get a stable system. D (derivative) Gain (or a lead compensator) should be included with the P Gain to help stabilize the system. D Gain can be increased to make the system more stable up to a point. After some point the additional D Gain will make the system more unstable. and should be reduced.

When using D Gain (or lead compensation) the quantization noise (steps) in the encoder position can cause spikes in the output. For example a D Gain of 100 will cause a spike of 100 counts in the output whenever the input changes suddenly by 1 count. If the spikes are very high amplitude and short duration, the Amplifier may not handle them in the expected manner. A low pass filter can be used to widen and reduce their amplitude allowing the amplifier to handle them more effectively. Typically a 2nd order low pass filter of 500Hz Q=1.4 is used. The last filter is normally used so it is applied to any Feed Forward. Such as:

[[File:LowPass400Q1p4.png|none|link=|680x439px]]

===Velocity, Acceleration, and Jerk===
<div id="yui_3_16_0_1_1445622719616_3315" class="yiv2818182665class" style="color: #000000; font-size: 13.3333px; font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif; background-color: transparent; font-style: normal;">The Velocity, Acceleration, and Jerk in the Step Response Screen (KFLOP parameter settings) and the Acceleration and Velocity in the KMotionCNC | Tool Setup | Trajectory Planner | Axis Parameters are both used for different things. The two sets of parameters are independent. </div>
<div id="yui_3_16_0_1_1445622719616_3313" class="yiv2818182665class" style="color: #000000; font-size: 13.3333px; font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif; background-color: transparent; font-style: normal;"> </div>
<div class="yiv2818182665class" style="color: #000000; font-size: 13.3333px; font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif; background-color: transparent; font-style: normal;">The KFLOP parameters are used for 3rd order motions. These include things like: Jogging, Homing, and GCode Rapids (G0). The units in KFLOP are in counts or steps. The KMotionCNC parameters are used for 2nd order (infinite Jerk) coordinated motion paths. These are GCode G1,G2,G3 continuous paths. The units are in Inches (or in some cases degrees). Note there is an Option in KMotionCNC "Rapids as Feeds" where these parameters will also be used for Rapids. But this option should only be used for highly non-linear Kinematic Systems which can not take advantage of faster/smoother 3rd order point to point straight line Rapids. </div>
<div class="yiv2818182665class" style="color: #000000; font-size: 13.3333px; font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif; background-color: transparent; font-style: normal;"></div>
<div class="yiv2818182665class" style="color: #000000; font-size: 13.3333px; font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif; background-color: transparent; font-style: normal;">Tests to find and verify optimal settings for both types of moves should be made using the Step Response Screen. Optimal settings are usually determined by experimentation. Although it might be possible to calculate the settings based on motor torque gains, back-emf, amplifier voltage/current, mass, moments of inertia, friction, encoder resolution, leadscrew pitch, required following accuracy, etc... It is often too complicated and with too many unknowns to be practical. So experimental moves can be tested at ever increasing Velocities, Accelerations, and Jerks until the system is unable to follow the trajectory without having too much error or shock to the system. After absolute limits of the system are determined then the settings should be backed off by some amount to provide operating margins (ie 20%). </div>
<div class="yiv2818182665class" style="color: #000000; font-size: 13.3333px; font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif; background-color: transparent; font-style: normal;">It is usually best to first determine max possible velocity using a relatively low acceleration. Maximum power is usually required at the point of the trajectory where velocity is high and still accelerating. Supply Voltage limitations tend to limit velocity. Current limitations tend to limit acceleration. </div>
<div class="yiv2818182665class" style="color: #000000; font-size: 13.3333px; font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif; background-color: transparent; font-style: normal;"></div>
<div class="yiv2818182665class" style="color: #000000; font-size: 13.3333px; font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif; background-color: transparent; font-style: normal;">[[File:MaxVelAccelPower.png|none|link=|485x361px]] The Step Response Screen always performs 3rd order motion but 2nd order motion can be simulated by temporarily setting the Jerk to a huge value (1000X the acceleration value). In general reducing the Jerk value will result in longer times to perform motions, but often the improved smoothness will permit higher maximum accelerations and velocities to be used resulting in overall shorter motion times. An analogy might be how you might stop more quickly in a car, without skidding or spilling your coffee, by applying the brakes harder in a more gradual manner rather than slamming on the brakes. Make sure when testing the size of move is long enough for full acceleration and velocity are achieved. A common mistake is to have Acceleration or Velocity Settings set to too high for your system but when testing a short move there is no indication of a problem. The plot mode of Velocity Output vs Time can be helpful to verify full Velocity is being achieved. </div>
<div class="yiv2818182665class" style="color: #000000; font-size: 13.3333px; font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif; background-color: transparent; font-style: normal;"></div>
<div class="yiv2818182665class" style="color: #000000; font-size: 13.3333px; font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif; background-color: transparent; font-style: normal;">The idea is that a motor axis has torque and speed limitations and you should determine and understand what they both are for your system. Available motor torque drops off with higher speed. At some speed the motor will not even be able to generate any torque at all. Motor torque is required to accelerate the axis. We need to make sure that no combination of velocity and acceleration will ever cause the axis to fault/stall/fail. So there is often a complex set of speeds and accelerations that will work ok that form an envelope of workable speed and acceleration. So one nice thing to know is top speed possible. It is like taking your car out on a long straight highway and gradually accelerating to find the max speed is 100MPH. You will then know that ever attempting a speed over 100MPH will always fail. Also speed should probably be limited to something like 80MPH to allow for margin and to allow reasonable acceleration up to that speed. The reason for performing the top speed test at low acceleration is to avoid a failure because of not being able to accelerate at the specified rate. So we want to set the acceleration to a low value so it will not be a limiting factor when determining top speed. However if we set the acceleration so low with a short trip distance we will never go very fast and the speed test will be meaningless. This should be avoided. Change the Plot type to Velocity, Output, vs Time to clearly see if this is the case. You may want to turn off Measured Velocity if it obscures viewing the Commanded Velocity For example to accelerate to 700,000 counts/sec at an acceleration rate of 700,000 counts/sec^2 would take 1 second. And then to slow back down would take 1 more second. So at least 2 seconds of motion would be required to get to full speed. A 100,000 count move (2 inches for a system with 50,000 counts/inch) takes much less time than that. Furthermore with a relatively low Jerk setting (1e6). This means the acceleration will be applied gradually over 0.7 seconds. This means an even much longer time and distance would be required to achieve top speed. Here is the method to follow to find 2nd/3rd order motion profile limits: (note every system is different and will vary based on resolution, motor size/type, mass, etc...)

'''1 - Find Max Velocity at low Acceleration and infinite Jerk'''

Choose a Velocity to test (ie V=100000 counts/sec) Set a moderately low Acceleration Time of 1 second (A = V/1sec = 100000 counts/sec^2) Set very high Jerk so Acceleration is applied almost instantaneously in 0.001 sec (J = A/0.001sec = 1e8 counst/sec^3) Test a very long move 20 inches if possible (for resolution 50000 counts/inch, 1,000,000 counts) Plot Velocity, Output, vs time to see if V is actually obtained If the motion was successful repeat all above with higher V, if not try lower V Once Max V is found reduce by some margin (ie 20-50%) Note you may decide on lower speed for other reasons (safety, vibration, noise, wobble, shock, etc....) '''2 - Find Max Acceleration for your system for the chosen Velocity'''

Using the V found above increase A (keeping Jerk high in the same manner) until the system fails/faults/excessive shock, etc... Once Max A is found reduce by some margin (ie 20-50%) These V and A Values are now known good values for your system and can be used for 2nd order motions such as KMotionCNC Trajectory Planner or Mach3 Motor tuning. Note units will need to be converted (counts to inches or mm, time from seconds to minutes depending on the App)

'''3 - Find optimal 3rd order Jerk limited motions.'''

The previous result from Step #1 and #2 used nearly infinite Jerk where Acceleration forces were applied nearly instantaneously. By reducing Jerk smoother motion should be possible. Set Jerk so it is applied over 20ms (ie for A=200000 J = A/0.020 = 1e7 Test to see if motions are smoother. With closed loop systems the Position Error Plot can be used to see if the motion has less error and is smoother. Open loop system will require you to hear the difference. Increase/decrease Jerk to find the optimal value. Note reducing Jerk a lot will of course make the system very smooth, but will also be much slower using less acceleration and velocity which is undesirable. So the highest Jerk possible should be found that still provides some smoothness. Reducing Jerk only will always make the system slower with less performance (but hopefully significantly smoother). It is usually then possible to increase Acceleration and Velocity somewhat to achieve even higher performance than what was possible with infinite Jerk while being as smooth or smoother.

'''4 - Reduce Max Following Error Limit to small value'''

</div>
<div class="yiv2818182665class" style="color: #000000; font-size: 13.3333px; font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif; background-color: transparent; font-style: normal;">Now that the system is properly tuned and reasonable Acceleration, Velocity, and Jerk are set the motor Position should always follow the commanded Destinations accurately with only small errors. By Plotting Position Errors under various conditions (Distances) you can get an idea of the worst case following errors under normal conditions. The Max Following Error Parameter should be set to a value slightly larger than the worst case following error (ie 20~50% larger). In this case if anything abnormal occurs: ie. The axis hits an obstacle, commanded at too high of a speed, servo goes unstable, hardware/electronics failure, a Following Error will be immediately detected and the axes disabled.</div>
<div class="yiv2818182665class" style="color: #000000; font-size: 13.3333px; font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif; background-color: transparent; font-style: normal;"></div>
===Axis Resolution - counts/inch (or counts/mm)===
<div class="yiv2818182665class" style="color: #000000; font-size: 13.3333px; font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif; background-color: transparent; font-style: normal;"></div>
<div class="yiv2818182665class" style="color: #000000; font-size: 13.3333px; font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif; background-color: transparent; font-style: normal;">Its important to understand the resolution of your Axis which is the number of fundamental raw motor/driver encoder counts or motor steps per standard unit of distance (inch or mm). Although tuning in KMotion.exe Step Response Screen and motions within KFLOP typically use units of raw counts or steps it is important to know how these translate to real-world distances, speeds, etc... Later, applications such as KMotionCNC or Mach3 will need this information to scale motions properly. </div>
<div class="yiv2818182665class" style="color: #000000; font-size: 13.3333px; font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif; background-color: transparent; font-style: normal;"></div>
<div class="yiv2818182665class" style="color: #000000; font-size: 13.3333px; font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif; background-color: transparent; font-style: normal;">There are usually a number of factors that combine together to determine the Axis Resolution. These might include:</div>
* counts or steps per motor revolution
* any gearing or belts and pulleys involved between motor and drive mechanisms
* lead screw pitch, rack and pinion tooth pitch, drive belt radius, etc.

For example consider a Stepper Drive with:

3200 steps per motor rev

2:1 gear reduction from motor to lead screw

0.2 inch lead screw pitch

Axis Resolution = 3200 step/motor rev x (2 motor rev/ screw rev) / (0.2 inch / screw rev) = 32000 steps/inch

To determine whether your assumptions and calculations are correct perform a test. Command as large of a move as convenient and measure the actual distance moved with a ruler. For example in the axis described above you might command a move of 320000 steps. This should result in a motion of:

320000 steps / (32000 steps/inch) = 10 inches.

For KMotionCNC set the Axis Resolution in the [http://dynomotion.com/Help/KMotionCNC/ToolSetupScreenTP.htm#Axis_Motion_Parameters Tool Setup | Trajectory Planner Screen | Axis Parameters | cnts/inch]. Note units must be in units of inches. If your resolution is in mm units multiply by 25.4.

For Mach3 enter the Axis Resolution in the Configuration | Motor Tuning Screen. Make sure the setup units (not GCode units) match the mode of your values.

===Servo Dither/Hunting - (oscillation around zero error)===
<div class="yiv2818182665class" style="color: #000000; font-size: 13.3333px; font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif; background-color: transparent; font-style: normal;"></div>
<div class="yiv2818182665class" style="color: #000000; font-size: 13.3333px; font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif; background-color: transparent; font-style: normal;">Servos have high accuracy because they are always actively trying to make corrections and drive the error to zero. Unfortunately this can sometimes cause annoying dither or position hunting around zero when not moving. This is a very complex non-linear effect dependent on the dynamics of the mechanics. Because of the highly non-linear quantization effects of single "steps" in the encoder position, stiction, backlash, etc. it follows different rules and is harder to analyze than normal servo tuning/stability in the larger magnitude more linear regime. For example attempting to apply "Damping" is unlikely to work. Lowering gains will usually help at the expense of performance. However in many cases more than acceptable performance can be achieved with lower gains so one should consider if the higher gains are really needed. KFLOP has a Deadband Gain and Range feature that can basically be used to tell the servo to not attempt to correct small errors (treat the errors as zero), or to try to correct them less aggressively (with a Gain less than 1.0). See [http://dynomotion.com/Help/StepScreen/StepScreen.htm#Dead_Band here for more information] Unfortunately adding Deadband doesn't always help the servo "sit still" and may actually increase the size of the dither depending on the dynamics.
 Note that when the servo is commanded to a non integer position ie 999999.7 encoder counts without deadband the servo will always be making corrections. The best the servo can do is dither between encoder positions 999999.0 and 1000000.0. With an error of either -0.7 or +0.3. A servo with Integrator gain will guarantee the average is 999999.7 If dither is still a major problem a C Program might be used to monitor things and change settings under certain conditions to reduce dither. See the example AntiServoDither__ALL.c which monitors for small errors for a period of time and if so reduces or turns off Integrator gain. 

</div>
===Noisy GCode - Trajectory Planner Smoothing===
<div class="yiv2818182665class" style="color: #000000; font-size: 13.3333px; font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif; background-color: transparent; font-style: normal;">An analysis of Quantization Noise in GCode and Trajectory Planner Settings to generate smooth motion. [[File:GCode_Noisy_Path.png|none|link=|432x432px]]</div>
<div class="yiv2818182665class" style="color: #000000; font-size: 13.3333px; font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif; background-color: transparent; font-style: normal;">[[Trajectory Planner Smoothing Noisy GCode|See Analysis and Solution]]</div>
<div class="yiv2818182665class" style="color: #000000; font-size: 13.3333px; font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif; background-color: transparent; font-style: normal;"></div>
===Arc "faceting" - Trajectory Planner - Collinear Tolerance===
<div class="yiv2818182665class" style="color: #000000; font-size: 13.3333px; font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif; background-color: transparent; font-style: normal;"></div>
<div class="yiv2818182665class" style="color: #000000; font-size: 13.3333px; font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif; background-color: transparent; font-style: normal;">[[File:ArcsTrajectoryZoomXTol.0005.png|none|link=|526x460px]]</div>
<div class="yiv2818182665class" style="color: #000000; font-size: 13.3333px; font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif; background-color: transparent; font-style: normal;"></div>
<div class="yiv2818182665class" style="color: #000000; font-size: 13.3333px; font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif; background-color: transparent; font-style: normal;">[[ArcFacetingColinearTol|See Analysis and Solution]]</div>
<div class="yiv2818182665class" style="color: #000000; font-size: 13.3333px; font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif; background-color: transparent; font-style: normal;"></div>
===I Gain/Max Limit Integrator===
I (Integrator) Gain can be used to eliminate persistent errors. In fact any Integrator Gain at all guarantees the average error over infinite time is zero. Without I Gain a system might have a small error that does not create enough output to overcome stiction to make a correction. In such a case the error could persist forever. Not so with any Integrator Gain. Any error will be integrated and ramp the output higher and higher until eventually there will be a correction. That assumes the Integrator or Output doesn't saturate or reach their programmed limits. The rate the output ramps (or sums) is dependent on the size of the error and the I Gain value. The Error x I Gain is summed every servo sample (90us). This is why I Gain values are often small numbers (0.0001 - 0.01 typical range). There is no guarantee that the position doesn't over shoot the target Destination. In fact it is likely as as any error (area) under the trajectory will always be balanced by an equal area over the trajectory. Too high of I Gain will make the system unstable.

Another case where I Gain is useful is when moving at high speed with a Velocity Amplifier. To move at high speed a significant amount of output is required. Without I Gain a significant amount of error could be required to provide this Output (ie Error x P Gain = Output). With I Gain the Integrator will eventually ramp up to provide any Output necessary to move at the desired speed driving the error to zero.

Integrators have an issue often referred to as "Integrator Wind Up". This issue usually doesn't arise under normal conditions. However if something is preventing the servo from making a correction such as forcing the position away from the target for a sustained amount of time, or disabling the amplifier, the Integrator will integrate to a huge unlimited value. When the force is removed or amplifier re-enabled, the Integrator will likely cause a violent motion and overshoot. Max Limit Integrator can help to minimize this issue by limiting the amount the Integrator can ramp up to. So the Max Limit Integrator Value should be set at the minimum value that can still allow the Integrator to function in normal circumstances.

Typically there are two cases that should be considered when determining the Max Limit Integrator.

# The amount of output expected to be required to overcome any stiction, friction, or other forces (cutting, gravity, etc...). This is often not a large value and can be estimated or can be observed from the Step Response Screen (green plot right side scale is the output) when making a move.
# The amount of output required to provide the output needed to move at speed. It is important to note that D Gain provides a damping or drag effect on the Output. So the Integrator must be able to ramp up to a sufficient level to overcome the damping or drag effect and still provide enough output to move at the commanded speed. For example:

Assume:

# Commanded speed of 500,000 counts/sec
# D Gain of 35
# Output required to move at speed is 1800 DAC Counts
# Servo Sample Time of 90us

Damping effect = Speed x D Gain x Sample Time = 500000 x 35 x 90e-6 = 1575 counts

Required Integrator Value = 1800 + 1575 = 3375

So to provide some margin an Max Limit Integrator Value of 3500 might be used.

===Max Limits - Error===
Max limits error can be helpful to have your system respond less violently in the abnormal event where an excessively large error occurs. Normally with a properly tuned system following errors should be small. Setting a Max limits error can cause the servo to treat errors beyond a specified limit as if they were only the size of the limit and therefore respond less so than they would otherwise. The max limits error is normally set to a value so it is not limiting under normal circumstances.

The Plot below shows a situation where a small max limits error combined with a low P gain severely limits the Output. In the plot below a large move (10000 counts) at a high speed (40000 counts/sec) is commanded. Only P Gain (0.2) is used to provide the Output (green). The max error limit of 200 combined with the low gain (0.2) limits the output to only 40 DAC counts. Even as the true error increases to many thousands of counts, the servo is told to ignore the amount over 200. So the output can never exceed 40 DAC counts. The 40 DAC count limit means that the Axis is therefor not capable of providing the output necessary to keep up with the commanded motion. The axis does the best it can with the limited output, and only does a fraction of the desired motion.

[[File:Move10000.png|none|link=|665x431px]]

After increasing the max limits error the Output (green - right scale) now goes to a much higher value (900), and the Position (red) follows the Command (blue) to a much better degree.

[[File:Move10000_nolimit.png|none|link=|667x430px]]

Increasing the P Gain to 1.6 also applies more Output sooner and the Position follows the command still better.

[[File:Move1000_p1.6.png|none|link=|667x432px]]

===Lead Compensator vs Derivative Gain===
Derivative (D) Gain is often used to help stabilize a system.  It helps to think in the Frequency Domain to help understand how the two forms of compensation help.  Please read below and [http://dynomotion.com/Help/BodeScreen/BodeScreen.htm this] for more information on the Frequency Domain.  Both Compensation methods add positive phase to help stabilize the system.  Unfortunately both methods increase gain at higher frequencies possibly causing the system to go unstable at higher frequency.  A Lead Compensator provides the benefit of positive phase but without as much gain increase at higher frequencies.  This figure shows a simplified Gain Plot comparison:

[[File:DGainvsLead.png|none|link=|593x593px]]

Here is a Bode Plot of a P=0.5 D=20 Compensator. Note the KMotion.exe Bode Plot Screen has the capability of plotting the Frequency Domain Response of the PID+Filters Compensation. Assume we desire positive phase to be added at 40Hz. Notice the positive phase of 40 degrees at 40Hz which is good. However the Gain increase in the 1KHz region of about 21db which is bad.

[[File:P.5D20Annotate.png|none|link=|621x460px]]

Here is a Bode Plot of a P=0.5 N1=N2=25Hz D1=D2=70Hz Compensator. Assume we desire positive phase to be added at 40Hz. We choose N1 N2 and D1 D2 to surround the frequency where the positive phase is desired. Moving them further apart will increase the amount of positive phase but also increase the added Gain. Notice the positive phase of 60 degrees at 40Hz which is good. However the Gain increase in the 1KHz region of about 12db which is bad. However both are improvements over the D Gain compensator.

[[File:PoleZeroFilter.png|none|link=|210x319px]]

[[File:P.5D0N25D70Annotate.png|none|link=|644x478px]]

===Tuning Master/Slave Configurations===
Master/Slave [http://dynomotion.com/Help/ConfigurationScreen/ConfigurationScreen.htm#Master/Slave_Settings Configurations] allow two (or more) motors to drive the same axis. Slaves are configured to follow a Master Axis. For example two lead screws on both sides of a gantry.

Tuning slaved axes is kind of a catch 22. In order to tune one axis the other axis must be tuned well enough to follow and vice versa. If possible, disconnect any mechanical linkage between the Master and Slave and test them separately without Slaving the Axes together to verify each axis Servos (can hold a position), moves at least somewhat properly, and moves in the same direction (assuming a positive [http://dynomotion.com/Help/ConfigurationScreen/ConfigurationScreen.htm#Master/Slave_Settings Slave Gain] will be used).

It is usually possible to incrementally tune each axis, at first moving slowly, then later at higher speeds, accelerations, and gains. Only the Master Axis can be tested with the [http://dynomotion.com/Help/StepScreen/StepScreen.htm Step Response Screen]. This is because the Slave will follow any movement of the Master, but the Master will not follow movement of the Slave. So if the Master Axis is moved all is well as both axes will move together, but if you try to move the Slave axis the two axes will fight. The Master fighting to stay where it is, and the Slave fighting to move.

To test/tune the Slave axis temporarily reverse the Master/Slave roles to make it the Master and then test it as the Master.

Note: only the Master Axis should be included into the Coordinated Motion System.

===Bode Plots===
A Bode Plot is a powerful tool for characterizing and providing insight into a dynamic system. It can help determine closed loop stability, bandwidth/performance, resonant frequencies, and more. It is entirely based on the system being linear. Linear in the sense that if the amplitude of some input signal is changed then the output signal will change proportionally as well. Unfortunately most systems are not entirely linear. Stiction, backlash, encoder quantization, amplifier saturation, and other effects are non-linear. For example driving a system with a signal too small to overcome stiction will result in no output at all whereas a larger signal will result in some output. This is clearly non-linear behavior. It would be nice to use a technique that handles non-linear systems but basically none are known. A Bode Plot is made injecting a stimulus to the system and observing how the system responds. For the reasons of non-linearity it is very important to perform a Bode Plot measurement using a representative level of stimulus similar to what the system will actually have during normal operation. If the Stimulus is not adjusted properly the result is likely to be completely invalid. Additionally the system should be reasonably tuned and stable so that it is responding in a reasonable way to the stimulus. If the system is unstable or very poorly tuned the result is likely to be completely invalid. You might think of it somewhat like shaking a box to determine what is in it. You should shake it with enough intensity and at frequencies to get some reaction, but not so high of intensity to break or distort the object inside. To create a Bode Plot use the KMotion.exe Bode Plot Screen. First select Plot: Time domain - Command, Position, Output vs Time and adjust the Amplitude and cutoff Freq until there is small but significant Position (red) changes (ie 50 encoder counts), at a frequency low enough that the Position at least somewhat attempts to follow the Command (blue), and where the Output (green) is not near saturation for the Drive being used. After the Stimulus/Noise Injection settings are set switch to Plot: Open Loop - Magnitude and Phase vs Frequency. Set the number of Samples to average (ie 20) and perform a Measurement.  [http://dynomotion.com/Help/BodeScreen/BodeScreen.htm See here for more information].

===Links to other Information on Tuning and Bode Plots===
[http://ctms.engin.umich.edu/CTMS/index.php?example=Introduction&section=ControlFrequency umich.edu Introduction section Control Frequency]

[http://www.motiontech.com.au/assets/pdf/Kollmorgen%20Use%20Control%20Theory%20to%20Improve%20Servo%20Performance%20230712.pdf Kollmorgen Use Control Theory to Improve Servo Performance 230712.pdf]

==Problems and Resolutions==
====General====
:* [[Noise - Typical Problems and Resolutions|Dealing with noise on inputs]]. If you experience issues with inputs misreading, the issue may be noise. This page provides examples on what might be causing noise issues and examples of how to possibly deal with noise.
:* Other
===Software-Specific Problems and Resolutions===
:* Place links to pages explaining resolutions to problems that are largely software-related here
[[KFLOP User C Programs Compiling/Launching Slowly because of Windows Defender]]

===Hardware-Specific Problems and Resolutions===
:* Place links to pages explaining resolutions to problems that are largely hardware-related
====[[Step/Dir Drives lose 2 Steps for each pair of Direction Reversals]]====
==Applications and Projects==
:* Place links to pages that explain how you accomplished your particular project. Write clear explanations that provide background on what you did and how you did it.
====[[Tool Changer - router linear 4 Tools - C Program]]====
[[File:LINEAT+ATC.jpg|none|link=|246x178px]]More linear milling tools: https://www.ichome.com/

====[[Part Zero & Tool Height Touch Plate|Part Zero & Tool Height Touch Plate]]====
====[[Driving Hobby Servos]]====
[[File:HobbyServo.png|left|link=]]

HiTec Type

==Electrical Discharge Machining==
[https://en.wikipedia.org/wiki/Electrical_discharge_machining EDM (wikipedia)] is a method of cutting materials with high precision and detail. Dynomotion Motion Controllers work well for EDM because of the ability for feedrate to be dynamically controlled including reversal along cutting path.

[[Information on BAXEDM Arc Generators used with KFLOP]]

Applied Science video that shows how to build an BAXEDM drilling machine using KFLOP and describes how it works:

{{#ev:youtube|https://youtu.be/rpHYBz7ToII|||||start=980}}

==How to convert a milling machine to a 3D printer in 3 easy steps==
[[File:CNCto3DPrinter.png|none|link=]]

More information [[How to convert a milling machine to a 3D printer in 3 easy steps|here]].

==International and other Languages==
[[Russian]]

[[Spanish]]

File:KFlop 2SnapAmp.stp.txt

2025-12-20T20:21:32Z

TK: 3D Step file of KFLOP + 2 SnapAmps

3D Step file of KFLOP + 2 SnapAmps

File:SnapAmp.stp.txt

2025-12-20T20:17:22Z

TK: 3D Step File of SnapAmp (by Isaac)

3D Step File of SnapAmp (by Isaac)

File:KFLOP 2SnapAmp Step.png

2025-12-20T20:10:22Z

TK:

2024-09-05T00:12:43Z

TK: /* Kinematics GimbalCB and guide contributed by kizilkaya */

==Advantages of Kinematics and Rotation Tool Center Point (RTCP)==
RTCP takes into consideration the Kinematics of the machine to allow angular changes to the tool while keeping the tool center point at the same location relative to the machine table. Note this is true regardless of whether the Tool angle changes or the Table angle changes. The diagram below shows an example where the Tool angle is changed.

[[File:RTCP_On_Off.png|none|link=|670x350px]]

To perform RTCP an XYZ adjustment is applied to correct for XYZ shifts that occur with ABC angular changes.

For Gimbal Head type systems the Tool Tip location relative to the head pivot points must be known to compute the appropriate adjustments. This means that changes of Tool Lengths and Tool Offsets will affect the required adjustments.

For Trunnion Table table type systems the Tool Tip location relative to the Table pivot points must be known to compute the appropriate adjustments. This means that changes to GCode Offsets (Fixture/work or Global) will shift all the Tool Tip locations relative to the Table and will affect the required adjustments.

The data flow diagram below shows the difference between having a CAD system perform the Kinematics vs having the Controller perform the Kinematics. Having the Controller perform the Kinematics allows the same GCode to be used even though Tool Lengths, Work Offsets, or even Machine Geometries have been changed.

[[File:RTCP_Data_Flow.png|none|link=|770x550px]]

An additional advantage to having Kinematics performed in the Controller is that the Kinematics/RTCP is performed continuously throughout angular motions and not only on GCode Coordinates/Blocks/Lines. So for example in the case where only the B Axis is desired to rotate:

G0 B0 (start at angle 0)

G1 B90 (rotate B 90 degrees).

With RTCP in the Controller, only one line of GCode is required to rotate B 90degrees and throughout the motion the tool tip will remain in the same place. With RTCP in CAD, many lines of GCode would be required that include all the intermediate XYZ positions to keep the tool tip in the same place.

==Overview==
Kinematics are part of the Coordinated Motion Library which is used by the GCode Interpreter. It provides a transformation from the desired CAD positions to the System's required Actuator positions to move there.

To add new Kinematics a new C++ Kinematics Class will be required to be added to the GCodeInterpreter Project. See [http://www.dynomotion.com/wiki/index.php?title=PC_Example_Applications here] for information on modifying and building the KMotion Libraries and PC Examples.

Normally only equations for inverse kinematics (determines Actuator positions from given CAD position) are required to be defined. The CKinematics class will automatically solve forward kinematics numerically.

A text file (Kinematics.txt) in the in the <>\KMotion\Data directory contains a string that is used by the CCoordMotion class to determine what Kinematics Class is to be used. If the text file doesn't exist standard, orthogonal, linear Kinematics are used.

After adding your new kinematics class a test for your new class should be added to CoordMotion.cpp into the code shown below. Also the appropriate string should be placed into the Kinematics.txt file. Additional parameters might be included in this file to be read by your Kinematics Class to make it more general.

<pre class="brush:c"> FILE *f = fopen((CString)MainPath + "\\Data\\Kinematics.txt","rt");

if (f)
{
char s[81];
fgets(s, 80, f);
// one exists, check if it is calling for Geppetto otherwise assume it is the 3Rod

if (strstr(s, "5AxisTableAC") != NULL)
Kinematics = new CKinematics5AxisTableAC;
else if (strstr(s, "5AxisTableBC") != NULL)
Kinematics = new CKinematics5AxisTableBC;
else if (strstr(s, "5AxisGimbalAB") != NULL)
Kinematics = new CKinematics5AxisGimbalAB;
else if (strstr(s, "5AxisGimbalCB") != NULL)
Kinematics = new CKinematics5AxisGimbalCB;
else if (strstr(s, "GeppettoExtruder") != NULL)
Kinematics = new CKinematicsGeppettoExtrude;
else if (strstr(s, "Geppetto") != NULL)
Kinematics = new CKinematicsGeppetto;
else
Kinematics = new CKinematics3Rod;

fclose(f);
}</pre>

Note: In order for your new class to be defined its header file should be added into the standard header include file StdAfx.h in the GCodeInterpreter Directory as are the other Kinematic class headers as shown below:

<pre class="brush:c">#include "Kinematics.h"
#include "Kinematics3Rod.h"
#include "KinematicsGeppetto.h"
#include "KinematicsGeppettoExtrude.h"
#include "Kinematics5AxisGimbalAB.h"
#include "Kinematics5AxisGimbalCB.h"
#include "Kinematics5AxisTableAC.h"
#include "Kinematics5AxisTableBC.h"</pre>

==Kinematics3Rod==
The first non-linear Kinematics that was added to the KMotion Libraries was the simple Kinematics3Rod class shown below. Given the XYZ CAD position it computes the necessary lengths of 3 "rod" type linear actuators to place the end effector at the desired CAD location. Also below is a old video of it in operation.

<pre class="brush:c"> // Kinematics3Rod.cpp: implementation of the CKinematics3Rod class.
//
//////////////////////////////////////////////////////////////////////

#include "stdafx.h"
#include "Kinematics3Rod.h"

#define sqr(x) ((x)*(x))

//////////////////////////////////////////////////////////////////////
// Construction/Destruction
//////////////////////////////////////////////////////////////////////

CKinematics3Rod::CKinematics3Rod()
{
Act0Center.x = 12;
Act0Center.y = 0;
Act0Center.z = 0;

Act1Center.x = 0;
Act1Center.y = 12;
Act1Center.z = 0;

Act2Center.x = 11;
Act2Center.y = 3;
Act2Center.z = 12;

// when actuator position is zero this is how long the rod is

Act0Off = sqrt(sqr(Act0Center.x) + sqr(Act0Center.y) + sqr(Act0Center.z));
Act1Off = sqrt(sqr(Act1Center.x) + sqr(Act1Center.y) + sqr(Act1Center.z));
Act2Off = sqrt(sqr(Act2Center.x) + sqr(Act2Center.y) + sqr(Act2Center.z));

m_MotionParams.MaxLinearLength = 0.25; // limit the segment lengs for nonlinear systems
m_MotionParams.MaxRapidFRO = 1.0; // limit the increase in Rapid HW FRO
m_MotionParams.UseOnlyLinearSegments=true;
}

CKinematics3Rod::~CKinematics3Rod()
{

}

int CKinematics3Rod::TransformCADtoActuators(double x, double y, double z, double a, double b, double c, double *Acts, bool NoGeo)
{
// find lengths of each actuator

GeoCorrect(x,y,z,&x,&y,&z);

double r0 = sqrt(sqr(x-Act0Center.x) + sqr(y-Act0Center.y) + sqr(z-Act0Center.z)) - Act0Off;
double r1 = sqrt(sqr(x-Act1Center.x) + sqr(y-Act1Center.y) + sqr(z-Act1Center.z)) - Act1Off;
double r2 = sqrt(sqr(x-Act2Center.x) + sqr(y-Act2Center.y) + sqr(z-Act2Center.z)) - Act2Off;

Acts[0] = r0*m_MotionParams.CountsPerInchX;
Acts[1] = r1*m_MotionParams.CountsPerInchY;
Acts[2] = r2*m_MotionParams.CountsPerInchZ;

Acts[3] = a*m_MotionParams.CountsPerInchA;
Acts[4] = b*m_MotionParams.CountsPerInchB;
Acts[5] = c*m_MotionParams.CountsPerInchC;

return 0;
}

// perform Inversion to go the other way

int CKinematics3Rod::TransformActuatorstoCAD(double *Acts, double *xr, double *yr, double *zr, double *ar, double *br, double *cr, bool NoGeo)
{
return InvertTransformCADtoActuators(Acts, xr, yr, zr, ar, br, cr);
}

</pre>
{{#ev:youtube|MV42zmiT_4I}}

==A more complex 6 axis Kinematics (CKinematicsGeppetto)==
{{#ev:youtube|MSONYPXe3bE}}
Formulas to calculate Actuator Positions from XYZABC CAD Position uses Rotate3 function to rotate a point through 3 angles.

<pre class="brush:c">int CKinematicsGeppettoExtrude::TransformCADtoActuators(double x, double y, double z, double a, double b, double c, double *Acts, bool NoGeo)
{
double x_0,y_0,z_0,x_1,y_1,z_1,x_2,y_2,z_2,x_3,y_3,z_3,x_4,y_4,z_4,x_5,y_5,z_5, TCP_Rotated_x,TCP_Rotated_y,TCP_Rotated_z;
// find lengths of each actuator

// Determine where the TCP rotated point would be relative to origin when oriented at the desired angles.
Rotate3(0, 0, 0, m_MotionParams.TCP_X, m_MotionParams.TCP_Y, m_MotionParams.TCP_Z, a, b, c, &TCP_Rotated_x, &TCP_Rotated_y, &TCP_Rotated_z);

// Translate from TCP to end effector origin
x += TCP_Rotated_x - m_MotionParams.TCP_X;
y += TCP_Rotated_y - m_MotionParams.TCP_Y;
z += TCP_Rotated_z - m_MotionParams.TCP_Z;

if (!NoGeo) GeoCorrect(x,y,z,a,b,c,&x,&y, &z, &a, &b, &c);

// Find where connection points should be
Rotate3(x,y,z,x+X0,y+Y0,z+Z0,a,b,c,&x_0,&y_0,&z_0);
Rotate3(x,y,z,x+X1,y+Y1,z+Z1,a,b,c,&x_1,&y_1,&z_1);
Rotate3(x,y,z,x+X2,y+Y2,z+Z2,a,b,c,&x_2,&y_2,&z_2);
Rotate3(x,y,z,x+X3,y+Y3,z+Z3,a,b,c,&x_3,&y_3,&z_3);
Rotate3(x,y,z,x+X4,y+Y4,z+Z4,a,b,c,&x_4,&y_4,&z_4);
Rotate3(x,y,z,x+X5,y+Y5,z+Z5,a,b,c,&x_5,&y_5,&z_5);

double r0 = sqrt(sqr(x_0 - Act0Center.x) + sqr(y_0 - Act0Center.y) + sqr(z_0 - Act0Center.z)) - Act0Off;
double r1 = sqrt(sqr(x_1 - Act1Center.x) + sqr(y_1 - Act1Center.y) + sqr(z_1 - Act1Center.z)) - Act1Off;
double r2 = sqrt(sqr(x_2 - Act2Center.x) + sqr(y_2 - Act2Center.y) + sqr(z_2 - Act2Center.z)) - Act2Off;
double r3 = sqrt(sqr(x_3 - Act3Center.x) + sqr(y_3 - Act3Center.y) + sqr(z_3 - Act3Center.z)) - Act3Off;
double r4 = sqrt(sqr(x_4 - Act4Center.x) + sqr(y_4 - Act4Center.y) + sqr(z_4 - Act4Center.z)) - Act4Off;
double r5 = sqrt(sqr(x_5 - Act5Center.x) + sqr(y_5 - Act5Center.y) + sqr(z_5 - Act5Center.z)) - Act5Off;

Acts[0] = r0*m_MotionParams.CountsPerInchX;
Acts[1] = r1*m_MotionParams.CountsPerInchY;
Acts[2] = r2*m_MotionParams.CountsPerInchZ;
Acts[3] = r3*m_MotionParams.CountsPerInchA;
Acts[4] = r4*m_MotionParams.CountsPerInchB;
Acts[5] = r5*m_MotionParams.CountsPerInchC;

return 0;
}</pre>

==Alex's system with a Table A axis and Gimbal B axis (Kinematics5AxisTableAGimbalB.cpp)==
[[File:TableAGimbalBCAD.png|none|link=]]

{{#ev:youtube|PuIdtZKdYfA}}
Here is the math. First the definitions:

[[File:TableAGimbalBDefs.png|none|link=]]

Origin Definition

[[File:TableAGimbalBOrigin.png|none|link=]]

The Solution

[[File:TableAGimbalBSolution.png|none|link=]]

The formula in C++ code:

<pre class="brush:c">// Kienematics for Table with A Axis and Tool Gimble head with B Axis
//
// A axis always rotates about X axis
// B axis always rotates about Y axis

int CKinematics5AxisTableAGimbalB::TransformCADtoActuators(double x, double y, double z, double a, double b, double c, double *Acts, bool NoGeo)
{
double Xt, Yt, Zt, Xa, Ya, Za, ToolXR, ToolZR, ChuckXR, ChuckZR, Dummy;

if (m_MotionParams.TCP_Active)
{
//Find CAD Tool Tip Location from coordinate passed in (Xt, Yt, Zt)
Xt = x - m_MotionParams.TCP_X; // remove tool offset
Yt = y - m_MotionParams.TCP_Y;
Zt = z - m_MotionParams.TCP_Z;

//Perform A rotation to obtain (Xa, Ya, Za)
Rotate3(0, 0, 0, Xt, Yt, Zt, a, 0, 0, &Xa, &Ya, &Za);

//Determine ChuckXR ChuckZR by rotating PivotChuckLength by Angle B
Rotate3(0, 0, 0, 0, 0, PivotToChuckLength, 0, -b, 0, &ChuckXR, &Dummy, &ChuckZR);

//Determine Rotated Tool offset ToolXR ToolZR by rotating ToolX ToolZ by Angle B
Rotate3(0, 0, 0, m_MotionParams.TCP_X, m_MotionParams.TCP_Y, m_MotionParams.TCP_Z, 0, -b, 0, &ToolXR, &Dummy, &ToolZR);

x = Xa + ToolXR + ChuckXR;
y = Ya;
z = Za + ToolZR + ChuckZR - PivotToChuckLength;
}

if (!NoGeo) GeoCorrect(x,y,z,&x,&y, &z);

Acts[0] = x*m_MotionParams.CountsPerInchX;
Acts[1] = y*m_MotionParams.CountsPerInchY;
Acts[2] = z*m_MotionParams.CountsPerInchZ;
Acts[3] = a*m_MotionParams.CountsPerInchA;
Acts[4] = b*m_MotionParams.CountsPerInchB;
Acts[5] = c*m_MotionParams.CountsPerInchC;

return 0;
}
</pre>

==Scara Robot Kinematics by Demondor==
See Forum Thread with code [https://www.dynomotion.com/forum/viewtopic.php?f=10&t=922 here].

Geometry below

[[File:ScaraGeometry.png|none|link=]]

Class name CKinematicsScara

==2 Axis Spray Robot by Scott Little==
Simulation

{{#ev:youtube|veQftMBxbzU}}
{{#ev:youtube|eon96CIPQkY}}

Forum Thread [https://dynomotion.com/forum/viewtopic.php?f=16&t=1182 here].

Class Name CKinematics2AxisRobot

3 Axis Cable Delta Robot by Александр Украинец==

{{#ev:youtube|1LG6tnt08wE}}

Class Name CKinematics3axisDeltaRobot

Project Details

[https://docs.google.com/document/d/1FLZXM_LQojO0Z4cQUFxOFcynNfsAr4oe34-rbIXFz8E/edit?usp=sharing Shared Project Files]

==5 Axis Gimbal CB by Forum User kizilkaya==

{{#ev:youtube|US-MbuuB5U8}}

Class Name CKinematicsGimbalCB

Here is an RTCP Guide submitted by kizilkaya

There is a lot of complicated information about RTCP and it took me a long time to collect all this and deliver the machine to my customer, but I finally succeeded. RTCP works without any problems. I have prepared a detailed guide for those who do not want to experience difficulties like me. I would be happy if you share it. STEP 1 ) Adjust all axis settings very precisely, especially the angled axes. STEP 2 ) Kinematics.txt from Data.rar copy to C:\KMotion5.3.4\GCodeInterpreter STEP 3 ) Select Kinematic from Kinematics.txt according to your machine configuration. (e.g. Kinematics5AxisGimbalCB). STEP 4 )B and C axis positions must be set to "0 (zero)" as shown in the picture, otherwise the angled axes will tilt in different directions when RTCP is active. STEP 5 ) Open the C:\KMotion5.3.4\GCodeInterpreter\GCodeInterpreter.vcxproj file with Visual Studio and set the pivot as seen in the pivot.png image, then compile the project and create the GCodeInterpreter element. Now you can use rctp actively with "G43.4 Hx (x tool number)" and turn off rtcp with "G49". Example ; Please first pull the x, y and z axes (taking the pivot length into consideration) to a safe area and edit the g code according to the C and B axis limits. G43.4 H1 G1 F3000 B0 C0 B90 B-90 C-180 C180 B0 C0 M30

[[File:pivot.png|none|link=|958x393px]]

[[File:Cosmeq.jpeg|none|link=|768x432px]]

Download Project [[Media:5AxisGimbalCBFiles.zip|Files]]

File:Cosmeq.jpeg

2024-09-05T00:01:31Z

TK: TK uploaded a new version of "File:Cosmeq.jpeg"

File:pivot.png

2024-09-04T23:59:20Z

TK: TK uploaded a new version of "File:pivot.png"

File:pivot.png

2024-09-04T23:55:11Z

TK: TK uploaded a new version of "File:pivot.png"

File:Cosmeq.jpeg

2024-09-04T23:51:56Z

TK:

File:pivot.png

2024-09-04T23:51:25Z

TK:

File:5AxisGimbalCBFiles.zip

2024-09-04T23:46:38Z

TK:

Main Page

2024-06-24T00:26:18Z

TK: Linear Table Corrections

=='''Dynomotion wiki'''''' '''==
Welcome to our wiki where you can find and share knowledge on Dynomotion's systems. To begin adding information to this wiki, simply create an account, verify your email, and start editing (click pencil icon). To make editing pages easier for everyone, we have installed a [https://help.bluespice.com/index.php/VisualEditor visual editor] by default. This visual editor allows you to edit a wiki page much like you would a standard word processing document.  For the seasoned wiki editors, standard [https://www.mediawiki.org/wiki/Help:Editing MediaWiki editing] may also be used.<nowiki> </nowiki>

''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 is safe to use. In no case will any contributor or Dynomotion be liable for incorrect information. Dynomotion reserves the right to modify or delete any contributions. ''

 Thanks for Contributing!

[http://dynomotion.com Official Dynomotion Site]

==Editing and Creating Wiki Pages==
Unintuitively, you first create a link to the page you want to make before you can make the page. To make a new page: while editing, right-click where you want your link to be, insert a link with a descriptive title and link text, save the page, click on the link you created, then click on "Empty Page" to begin editing your new page.

Here are a few other quick tips:

* You can insert links or images by Right-Clicking with the mouse on the line where you want the link or image to appear.
* For Spell Correction you can use Ctrl-Right-Click.
* To insert a YouTube Video use an EmbedVideo command such as <nowiki> {{#ev:youtube|xxxxx}}
</nowiki>with xxxxx changed to the Video ID.
* Choose a descriptive page name and link text when creating a new page: e.g. Not "My Machine", but rather "Brand X Three Axis Milling Machine Retrofit"
* Create pages in an organized manner: Describe what the page is about, create clear sections that flow

For more information:

[[Help:New Page Creation|How to create a new wiki page]]

[[Help:Editing Pages|How to Edit and insert Media into your wiki pages]]

==Dynomotion Software Topics==
===Installation Topics===
* Announcement of our Latest Release (5.3.3) on the [https://www.dynomotion.com/forum/viewtopic.php?f=4&t=1752 Dynomotion Forum]
* [https://dynomotion.com/Software/Download.html Latest Release] Note: For Windows 7 64bit signed Drivers to work, all Windows Updates should be performed.
* [[Upgrading from previous KMotion Versions]]

Archive of Test Releases:

* Previous Test Release: 02/01/2024: [https://dynomotion.com/Software/KMotion5.3.2.exe KMotion.exe 5.3.2], See the release notes for this test version here: [https://dynomotion.com/Software/KMotion%20Released%20Version%205.3.2%20Changes.pdf 5.3.2 release notes (pdf)]
* Previous Test Release: 11/20/2023: [https://dynomotion.com/Software/KMotion5.3.1.exe KMotion.exe 5.3.1], See the release notes for this test version here: [https://dynomotion.com/Software/KMotion%20Released%20Version%205.3.1%20Changes.pdf 5.3.1 release notes (pdf)]
* Previous Test Release: 09/19/2023: [https://dynomotion.com/Software/KMotion5.3.0.exe KMotion.exe 5.3.0], See the release notes for this test version here: [https://dynomotion.com/Software/KMotion%20Released%20Version%205.3.0%20Changes.pdf 5.3.0 release notes (pdf)]
* Previous Test Release: 06/30/2023: [https://dynomotion.com/Software/KMotion5.1.0.exe KMotion.exe 5.1.0], See the release notes for this test version here: [https://dynomotion.com/Software/KMotion%20Released%20Version%205.1.0%20Changes.pdf 5.1.0 release notes (pdf)]
* Previous Test Release: 05/01/2023: [https://dynomotion.com/Software/KMotion5.0.7.exe KMotion.exe 5.0.7], See the release notes for this test version here: [https://dynomotion.com/Software/KMotion%20Released%20Version%205.0.7%20Changes.pdf 5.0.7 release notes (pdf)]
* Previous Test Release: 09/21/2022: [https://dynomotion.com/Software/KMotion435h.exe KMotion.exe V4.35h], See the release notes for this test version here: [https://dynomotion.com/Software/KMotion%20Released%20Version%204.35h%20Changes.pdf V4.35h release notes (pdf)]
* Previous Version 4.35g was not released, but see the change notes for this version here: [https://dynomotion.com/Software/KMotion%20Released%20Version%204.35g%20Changes.pdf V4.35g change notes (pdf)]
* Previous Test Release: 12/28/2020: [https://dynomotion.com/Software/KMotion435f.exe KMotion.exe V4.35f], See the release notes for this test version here: [https://dynomotion.com/Software/KMotion%20Released%20Version%204.35f%20Changes.pdf V4.35f release notes (pdf)]
* Previous Test Release: 11/18/2019: [https://dynomotion.com/Software/KMotion435e.exe KMotion.exe V4.35e], See the release notes for this test version here: [https://dynomotion.com/Software/KMotion%20Released%20Version%204.35e%20Changes.pdf V4.35e release notes (pdf)]
* Previous Test Release: 09/10/2019: [https://dynomotion.com/Software/KMotion435d.exe KMotion.exe V4.35d], See the release notes for this test version here: [https://dynomotion.com/Software/KMotion%20Released%20Version%204.35d%20Changes.pdf V4.35d release notes (pdf)]
* Previous Test Release: 01/28/2019: [https://dynomotion.com/Software/KMotion435b.exe KMotion.exe V4.35b], See the release notes for this test version here: [https://dynomotion.com/Software/KMotion%20Released%20Version%204.35b%20Changes.pdf V4.35b release notes (pdf)]
* Previous Test Release: 12/21/2018: [https://dynomotion.com/Software/KMotion435a.exe KMotion.exe V4.35a], See the release notes for this test version here: [https://dynomotion.com/Software/KMotion%20Released%20Version%204.35a%20Changes.pdf V4.35a release notes (pdf)]
* Previous Test Release: 09/28/2017: [https://dynomotion.com/Software/KMotion434j.exe KMotion.exe V4.34j], See the release notes for this test version here: [https://dynomotion.com/Software/KMotion%20Released%20Version%204.34j%20Changes.pdf V4.34j release notes (pdf)]
* Previous Test Release: 05/07/2017: [https://dynomotion.com/Software/KMotion434i.exe KMotion.exe V4.34i], See the release notes for this test version here: [https://dynomotion.com/Software/KMotion%20Released%20Version%204.34i%20Changes.pdf V4.34i release notes (pdf)]
* Previous Test Release: 12/14/2016: [https://dynomotion.com/Software/KMotion434h.exe KMotion.exe V4.34h], See the release notes for this test version here: [https://dynomotion.com/Software/KMotion%20Released%20Version%204.34h%20Changes.pdf V4.34h release notes (pdf)]
* Previous Test Release: 12/13/2016: [https://dynomotion.com/Software/KMotion434g.exe KMotion.exe V4.34g], See the release notes for this test version here: [https://dynomotion.com/Software/KMotion%20Released%20Version%204.34g%20Changes.pdf V4.34g release notes (pdf)]
* Previous Test Release: 12/05/2016: [https://dynomotion.com/Software/KMotion434f.exe KMotion.exe V4.34f], See the release notes for this test version here: [https://dynomotion.com/Software/KMotion%20Released%20Version%204.34f%20Changes.pdf V4.34f release notes (pdf)]
* Previous Test Release: 11/07/2016: [https://dynomotion.com/Software/KMotion434e.exe KMotion.exe V4.34e], See the release notes for this test version here: [https://dynomotion.com/Software/KMotion%20Released%20Version%204.34e%20Changes.pdf V4.34e release notes (pdf)]
* Previous Test Release: 10/32/2016: [https://dynomotion.com/Software/KMotion434d.exe KMotion.exe V4.34d], See the release notes for this test version here: [https://dynomotion.com/Software/KMotion%20Released%20Version%204.34d%20Changes.pdf V4.34d release notes (pdf)]
* Previous Test Release: 10/23/2016: [https://dynomotion.com/Software/KMotion434c.exe KMotion.exe V4.34c], See the release notes for this test version here: [https://dynomotion.com/Software/KMotion%20Released%20Version%204.34c%20Changes.pdf V4.34c release notes (pdf)]
* Previous Test Release: 10/03/2016: [https://dynomotion.com/Software/KMotion434b.exe KMotion.exe V4.34b], See the release notes for this test version here: [https://dynomotion.com/Software/KMotion%20Released%20Version%204.34b%20Changes.pdf V4.34b release notes (pdf)]
* Previous Test Release: 03/09/2016: [https://dynomotion.com/Software/KMotion434a.exe KMotion.exe V4.34a], See the release notes for this test version here: [https://dynomotion.com/Software/KMotion%20Released%20Version%204.34a%20Changes.pdf V4.34a release notes (pdf)]
* [https://dynomotion.com/Help/KFLOPQuickStart/KFLOPQuickStart.htm How to install KMotion.exe and KMotionCNC]
* [[How to install KMotion.exe and KMotion in Windows 10|Preparing Windows 10 for driver installation]] (no longer required)
* [[Special Case for Windows 8.1 Industry Embedded Enterprise]]
* [[Updating KFLOP Firmware|How to update KFLOP Firmware]] - whenever a new version of software is installed, the firmware within KFLOP must be updated to match the new version

===KMotion.exe Executive Software Topics===
KMotion.exe is the main program that is used to configure settings in KFLOP, initialize axes, and to write C programs to configure and setup KFLOP to control your system. In this program you can plot step response, test movement, view Bode plots, monitor I/O, set filter parameters, and generally set the pertinent parameters.

* [http://www.dynomotion.com/Help/index.htm General software information] from the manuals
* Insert pages for other KMotion.exe-related topics here

===Configuration Topics===
====Channels, Channels, Channels what are they?====
[[Channels Channels Channels|Read Article Here]]

====How to Setup Backlash Compensation====
[[Backlash Compensation|Read Article Here]]

====PWM Output Mode====
[[PWM Output Mode|Read Article Here]]

===KMotionCNC Software Topics===
KMotionCNC is Dynomotion's CNC program used as a graphical user interface to your KFLOP-enabled machine tool. KMotionCNC has all of the basic functionality you need to run a machine of up to 6 axes, in addition to spindle control.

* Insert pages for other KMotionCNC-related general topics here

====Using KMotionCNC====
* Homing discussion - page to be created
* Insert other KMotionCNC use pages here

[[Internal/concave Path Tool Radius Compensation Example G41/G42]]

[[Known KMotionCNC CAD/CAM Post Processors]]

[[Invoking C Programs with Execute Only for previously Downloaded Programs]]

[[Rigid Tapping G84 Setup and Use]]

[[Tool Length/Offsets G43Hn G49]]

====Customize KMotionCNC====
KMotionCNC is written as a Windows C++ MFC (Microsoft Foundation Classes) program developed in Visual Studio. Source code is provided and may be customized using Visual Studio. MFC Support is a requirement.

: '''General Information'''
: Compiling KMotionCNC
:: The KMotionCNC's Visual Studio Project Solution (\PC VC Programs\KMotionCNC\KMotionCNC.sln) is currently written for Visual Studio 2015 Standard. This version can be used for the simplest compatibility. Projects can be upgraded to newer version of VS with minimal effort. Including Microsoft's Free Visual Studio 2013 Community. [[PC Example Applications|More info on PC Example Applications.]]
:: Note Test Versions 4.34a and later have project solutions targeted for Visual Studio 2015 Community which is free for most Users.
: '''KMotionCNC Customization Examples and Applications'''
:: Links to examples of projects that explain KMotionCNC customizations. Troy (tmday7) created some helpful documents (PDF format):
:
:* [https://www.dynomotion.com/forum/archive/attachments/How%20to%20Edit%20KMotionCNC%20Faces.pdf How to edit KMotionCNC faces]
:* [https://www.dynomotion.com/forum/archive/attachments/Adding%20External%20Buttons.pdf Adding external buttons]
:* [https://www.dynomotion.com/forum/archive/attachments/Adding%20More%20User%20Buttons.pdf Adding more user buttons]
:* [https://www.dynomotion.com/forum/archive/attachments/Adding%20Jog%20Percent%20Cell%20to%20Main%20Dialog%20Face.pdf Adding Jog Percent Cell to Main Dialog Face]

====KMotionCNC Screen Editor====
Introduces the capability of using Screen Script files to modify the look and function of KMotionCNC. [[KMotionCNC Screen Editor|More information.]]

====KMotionCNC Geometric Correction====
Information regarding the powerful [https://dynomotion.com/Help/KMotionCNC/GeoCorrection.htm Geometric Correction capability] which allows calibration and distortion correction of the XY CAD space to Machine/Actuator Space as well as flatness in Z. Simple 4 point correction tables can apply XY Scale, Rotation, skew, offset, tilt. Larger tables can apply more non-linear corrections.

Note the Geometric Correction is built into the KMotion Libraries and can be utilized by Custom Programs as well as with KMotionCNC [[Geometric Correction|More information and Examples.]]

====KMotionCNC Linear Table Correction (Screw Mapping)====
Individual Axes can be corrected in a 1 dimensional manner referred to as Linear Table Corrections. For more information See [[Linear Table Correction|here]].

===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. 

'''Note All the projects in KMotion Versions 4.34a and later have now been updated and should work out-of-the-box with VS2015.'''

[[PC Example Applications|More information.]]

===KMotion Libraries - GCode Interpreter - Trajectory Planner - Coordinated Motion - .NET===
The KMotion Libraries are a series of DLLs (Dynamic Link Libraries) that reside on the PC that contain the common core motion control, I/O, and communication functionality for KFLOP. These libraries permit PC Applications to be built using high level control without being concerned with the underlying details of Interpreting GCode, Trajectory Planning, Coordinated Motion, Motion Buffering, USB Communication, etc.

[[KMotion Libraries - GCode Interpreter - Trajectory Planner - Coordinated Motion - .NET|More information]].

===Kinematics===
The KMotion Libraries contain a Kinematics Layer where Users can add their own non-linear Kinematics

[[Kinematics|More information]].

===KFLOP C Programs===
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.

[[KFLOP C Programs|More Information]]

===ModBus===
Modbus can be connected to the PC or directly to KFLOP. A PC connection will not be deterministically real-time but may work for basic speed control and on/off. Here is a related Thread for interfacing KMotionCNC to Modbus using a [http://www.modbusdriver.com/modpoll.html free utility]:

[https://www.dynomotion.com/forum/archive/sending%20ModBus%20msgs%20from%20KmotionCNC%20to%20a%20RS485%20port.html Sending ModBus msgs from KmotionCNC to a RS485 port]

To connect Modbus directly to KFLOP's [http://www.dynomotion.com/Help/RS232/RS232.htm UART] see the C Examples in \C Programs\RS232\ModBus\

===Linux Support===
KMotion Motion Libraries are fully supported under Microsoft Windows. Some Users have ported the KMotion Libraries to Linux. Dynomotion will offer support where possible but can't offer full support under Linux. Special Thanks to [https://github.com/parhansson/KMotionX Par Hansson] for the initial Linux Port.

See [[Linux|here]] for more info.

==Dynomotion Hardware Topics==
===General Hardware Information===
====[[KFLOP Hardware Info|KFLOP specific Hardware Info]]====
====[[KStep Hardware Info|KStep specific Hardware Info]]====
====[[Kanalog Hardware Info|Kanalog specific Hardware Info]]====
====[[SnapAmp Info|SnapAmp specific Hardware Info]]====
====[[Konnect Hardware Info|Konnect specific Hardware Info]]====

===Wiring Diagrams===
[[Media:Kanalog_Connections.pdf|Basic Kanalog DAC and Encoder Connections 3 Axis]]

[[Media:KanalogSchematic3Axis.pdf|Basic Kanalog DAC and Encoder Connections 3 Axis #2]]

[[Media:dyn4 kanalog KE1524 V1.1.png|Basic Kanalog DAC and DMM DYN4 Drive 1 Axis]]

[[Media:Kflop-Kanalog_wiring_11-19-2018.pdf|Kanalog with Geckos G210 updated 11-19-2018]] (Thanks to Joseph Mirocha)

[[Media:Kanalog_to_Tree_Journeyman_325_by_Rick_B.pdf|Kanalog to Tree Journeyman 325.pdf]] (Thanks to Rick_B)

[[Media:KFlopSnapBrushMPG.pdf|KFLOP+SnapAmp DC Brush Motors with MPG]]

[[Media:Stepper_Wiring_Diagram_Step-Dir_on_JP5.pdf|KFLOP JP5 Open Collector Step/Dir Connections to Power Step PSD5042-2P Drives ]]

[[Media:Matrika_V1_wiring_diagram_Rev1.pdf|KFLOP+KStep with VFD and NPN Limit Switches for Matrika Rev1]]

[[Media:KonnectTouchPlate.png|Touch Plate Wiring to Konnect]]

[https://easyeda.com/350banshee/BreakoutBoard-93bdd16e3c3d48b98ae66c34f2436c40 User Created KFLOP JP7 Breakout/OptoIsolation Board] Schematic, Gerbers, PCBs Publicly available (thanks 350banshee)

[https://www.dynomotion.com/wiki/index.php?action=ajax&title=-&rs=SecureFileStore::getFile&f=/b/bb/RotarySwitchToKanalog.png Rotary Switch Connected to Kanalog Opto Inputs]

===3D Board Models===
[[Media:kflop-kstep-3d-models-1.snapshot.3.zip.txt|kflop-kstep-3d-models-1.snapshot.3.zip.txt]] STEP file format - Thanks to Curtis

[[File:kflop_kstep_render.JPG|none|link=|329x329px]]

[[Media:KFLOP3D_Step_IGS_Chris.zip.txt|KFLOP3D_Step_IGS_Chris.zip.txt]] STEP and IGS models - Thanks to Chris

[[File:KFLOP_3D.png|none|link=|413x296px]]

[[Media:KONNECT_BOARD_MODEL.zip.txt|KONNECT_BOARD_MODEL.zip.txt]] STEP model - Thanks to Jeff Redington

(Component locations may be off one way or another by .5mm)

[[File:Konnect_Board.png|none|link=|339x292px]]

Konnect Basic Step file showing hole locations

[[Media:KonnectHoles.stp.txt|KonnectHoles.stp.txt]]

[[File:KonnectHoles.png|none|link=|352x323px]]

Kanalog Step Model with Mechanical hole and Pin locations

[[Media:Kanalog.stp.txt|Kanalog.stp.txt]]

[[File:KanalogFromStep.png|none|link=|304x279px]]

Kanalog Step Model with Mechanical hole and Connectors (Thanks to

Roberto Gotti of Powertech)''' '''

[[Media:KANALOG_BOARD.stp.txt|KANALOG_BOARD.stp.txt]]

[[File:KanalogWithConnectors.png|none|link=|311x286px]]

===Board Terminal DXF/DWG files===
[[Media:KFLOP_Terminals.dxf|KFLOP_Terminals.dxf]] [[Media:KFLOP_Terminals.dwg|KFLOP_Terminals.dwg]]

[[Media:Kanalog_Terminals.dxf|Kanalog_Terminals.dxf]] [[Media:Kanalog_Terminals.dwg|Kanalog_Terminals.dwg]]

[[Media:Konnect_Terminals.dxf|Konnect_Terminals.dxf]] [[Media:Konnect_Terminals.dwg|Konnect_Terminals.dwg]]

[[Media:KStep_Terminals.dxf|KStep_Terminals.dxf]] [[Media:KStep_Terminals.dwg|KStep_Terminals.dwg]]

===Wiring Topics===
Place links to pages on wiring inputs and

outputs specific to your experiences and projects. Be descriptive with page titles and links.

====KFLOP IDC Connectors and Cables====
Cables that connect between Dynomotion boards are normally included when purchasing the boards together. They are also very common and easy to make. Use '''16-conductor or 26-conductor ribbon cable''' (0.05 inch pitch 26 AWG preferrably or 28AWG) and IDC sockets. [[File:RibbonCable.png|none|link=]]
16 conductor ribbon cable 3M part number 3801/16 100 https://www.digikey.com/product-detail/en/3m/3801-16-100/3M156105-100-ND/1107501 26 conductor ribbon cable 3M part number C3801/26 100 https://www.digikey.com/product-detail/en/3m/C3801-26-100/C3801-26-100-ND/1107648 Winford also sells ribbon cable (although only the thinner 28 AWG): http://www.winford.com/products/rib.php Note you can usually tear off wires to reduce the number of conductors. For example from 26 down to 16. Tear off the conductors away from the red stripe that marks pin 1. The '''crimp tools''' are common: https://www.amazon.com/Accessories-Crimp-Ribbon-Cable-Connectors/dp/B007R2JEM4/ [[File:RibbonCrimp.png|none|link=]] '''IDC Sockets 16-pin '''(pin pitch 0.1 inch) https://www.digikey.com/product-detail/en/assmann-wsw-components/AWP-16-7240-T/HHKC16H-ND/5031953 Assman Part number AWP 16-7240-T
[[File:16pinIDC.png|none|link=]]
https://www.digikey.com/product-detail/en/assmann-wsw-components/AWP-26-7240-T/HHKC26H-ND/5011313
[[File:26pinIDC.png|none|link=]]

====KFLOP KStep JR1 Molex Power Connectors====
KFLOP and KStep JR1 are standard Disk Drive Power Connectors. Possibly one of the most common connectors. Originally used on PC ATX Power Supplies. Sometimes referred to as Molex Connectors. They have 4 pins with 0.2 inch pitch with 0.083~0.084 inch socket pins. The mating cable will have female socket pins as shown here:

[[File:Molex_female_connector.jpg|none|link=|251x168px]]

Molex Series 8981 P# [https://www.digikey.com/short/zjp329 0015244048] using Molex Series 8980 Crimp Pins P# [https://www.digikey.com/short/zjp3ff 0002081201]

Also AMP Series MATE-N-LOK P# [https://www.digikey.com/short/zjpq3n 1-480424-0] using AMP Series MATE-N-LOK Crimp Pins P# [https://www.digikey.com/short/zjpqqw 60619-1] or P# [https://www.digikey.com/en/products/detail/molex/0194200002/2404783 194200002]

Molex Crimp Tool P# [https://www.digikey.com/en/products/detail/molex/0640160035/665311 0640160035]

====MPG Wiring and Interface====
MPGs (Manual Pulse Generators) should be connected directly to KFLOP for guaranteed real-time response (not USB based or connected to the PC). MPGs are handled by a C Program that monitors the MPG and creates motion based on the MPG Encoder changes and switch selections for axis, speed, and so forth. See the MPG C Program Examples. Here is a Discussion with other links.

[https://www.dynomotion.com/forum/archive/Jogging%20Pendant.html Jogging Pendant]

[https://www.dynomotion.com/forum/archive/Connecting%20Keling%20MPG2%20pendant.html Connecting Keling MPG2 Pendant]

[https://www.cnczone.com/forums/dynomotion-kflop-kanalog/349740-applying-acceleration-mpg-target-possible.html#post2119732 CNCZone Thread] on obtaining smooth filtered motion.

[[File:MPG4_from_cnc4pc.jpg|none|link=|83x169px]]

====Interfacing NPN Devices to KFLOP IO====
NPN devices (open collector)operate as a switch to GND and can be interfaced to KFLOP using a pull up resistor as shown below. When the transistor switches to 0V the KFLOP IO Pin is driven low. The transistor will need to sink ~3ma. When the transistor is off (open circuit) the resistor pulls the IO Pin to 3.3V. Note even though some KFLOP IO Pins can tolerate 5V pulling them above 3.8V should be avoided when possible so the 3.3V supply is used. This technique will only work with KFLOP IO Pins that do not have pull down resistors (JP7 and JP5). In some cases a 0.1uF Ceramic capacitor connected close to KFLOP might be added in parallel with the resistor to filter noise. Cable shielding connected to KFLOP GND on the KFLOP end only is recommended. Note that in noisy environments this technique may couple noise into KFLOP so opto isolation should be used instead.

[[File:NPN_Interface_to_KFLOP.png|none|link=|544x544px]]

====Multiplexing Encoder Inputs to KFLOP JP4 and JP6====
If KFLOP JP7 and JP5 are used for other purposes the encoder inputs can be multiplexed to KFLOP JP4 and JP6. There is an option to multiplex encoders 0-3 from JP7 to JP4 and another option to multiplex encoders 4-7 from JP5 to JP6. See the MuxEncoders.c for an example.

Note the JP4 and JP6 IO are 3.3V inputs and shouldn't be driven hard (more than 10ma) above 3.8V. This is not usually an issue as most encoders or RS422 drivers don't do this. The inputs also have 150 ohm termination.

The following line of code might be added to your Initialization C Program. It needs to be executed once to multiplex the encoders after any power cycle. Encoders 0-3 will then be input on JP4 and 4-7 will be on JP6. Both JP4 and Jp6 have 10 IO bits. The 4 encoders will appear on the first 8 IO bits. 2 bits for each encoder's A B channels in order. So for example Encoder #0 will appear on JP4 IO16 (Pin5) and IO17 (Pin6)

<pre class="brush:c">
// Mux encoder inputs from KFLOP JP7 & JP5 to JP4 and JP6
FPGAW(ENC_NOISE_FILTER_ADD) = ENC_0_3_JP4 + ENC_4_7_JP6 + ENC_NOISE_FILTER_DEFAULT_VAL; </pre>

JP4 and JP6 have +5V available on Pin1 and GND on Pins 8 and 9 that might be used to power 5V encoders.

==Axes Servo Tuning and Trajectory Planner==
===Basic Servo Tuning Overview===
Once an axis is configured and proved capable of holding a position it is ready to be tuned and optimized. Most often a small value of P Gain only is used to show the servo is functional and can hold position. The Servo may be very weak and inaccurate but will be functional.

Every system is different and the tuning parameters are interactive in a manner that usually doesn't allow parameters to be determined one at a time. Rather after one parameter is changed it may be necessary to revisit the other parameters.

In general higher gains will reduce errors and improve accuracy, but tend to make the system more unstable. So the general idea is to increase gains to reduce errors as much as possible but still have a stable system.

Often during tuning the system may go unstable. In fact, it is normally intentionally driven to instability to find its limits for a certain parameter. This can result in a violent oscillation or worse so one should be prepared to quickly disable the Servo. If an appropriate [http://dynomotion.com/Help/ConfigurationScreen/ConfigurationScreen.htm#Max_Following_Error Max Following Error] is used the axis can be automatically disabled before the oscillation becomes too violent, yet not disable when performing a normal test.

KMotion.exe allows you to change any axis parameter on the Step/Response, Config, or Filters Screens then simply push "Move" to see the effect of the change. Note that as performance improves the errors will become small and difficult to see on the Position Plot without Zooming in (Left click drag) so changing the plot type to plot the error is useful.

The overall process normally goes something like this:

# Select a Test [http://dynomotion.com/Help/StepScreen/StepScreen.htm#Measurement Move Size] and [http://dynomotion.com/Help/StepScreen/StepScreen.htm#Motion_Profile Motion Profile]. [http://www.dynomotion.com/wiki/index.php?title=Main_Page#Velocity.2C_Acceleration.2C_and_Jerk See Also]
# Select [http://dynomotion.com/Help/StepScreen/StepScreen.htm#max_limits Max Limits] to allow for the Test. [http://www.dynomotion.com/wiki/index.php?title=Main_Page#Max_Limits_-_Error See Also]
# Determine maximum level of [http://dynomotion.com/Help/StepScreen/StepScreen.htm#PID P Gain]
# Determine maximum level of [http://dynomotion.com/Help/StepScreen/StepScreen.htm#PID D Gain] (with Low Pass Filtering) See Also [http://www.dynomotion.com/wiki/index.php?title=Main_Page#Torque_Servos_vs_Velocity_Servos here] and [http://www.dynomotion.com/wiki/index.php?title=Main_Page#Lead_Compensator_vs_Derivative_Gain here].
# Determine new maximum level of P Gain now that D Gain increased stability
# Add I Gain to improve accuracy and remove steady state errors. [http://www.dynomotion.com/wiki/index.php?title=Main_Page#I_Gain.2FMax_Limit_Integrator See Also]
# Add [http://dynomotion.com/Help/StepScreen/StepScreen.htm#Feed_Forward Feed Forward] to reduce errors

===Torque Servos vs Velocity Servos===
+/-10V Analog Amplifiers usually come in one of two varieties: '''Torque''' or '''Velocity'''. Torque mode amplifiers consider the input command as a Torque Command and work to generate the commanded Motor Torque. Velocity mode amplifiers consider the input command as a Velocity Command and work to generate the commanded Velocity. Its important to understand what type of Amplifiers you have.

'''Velocity Mode Amplifiers''' need some form of feedback going to the Amplifier in order for the drive to know the current velocity. This might be a digital encoder or an analog tachometer.

Its easy to tell if you have a Velocity Mode Amplifier by looking at a plot of a move on the Step Response Screen. The Output (green plot with right scale) will be proportion to the motor velocity. When moving at constant speed the output will be relatively constant. See in the plot below the output (green) remains at a relatively constant ~1100 DAC counts while the position (red) ramps at a constant slope of the 90000 count/sec rate:

[[File:VelocityAmp.png|none|link=]]

Velocity mode amplifiers can be relatively easy to tune using only P (Proportional) Gain. Additional Gains and filters can be used for best performance but using only P Gain will often result in reasonable performance and a stable system (unlike Torque Mode Amplifiers).

As an example consider controlling the speed of a car using only Proportional Gain as it approaches a target (Stop sign). Consider a P Gain of 0.1 where at 1000ft from the stop sign we command 1000 x 0.1 = 100MPH. Then at 100ft we command 10MPH. Then at 10ft we command 1MPH. This results in a nice, smooth, exponential approach, without overshoot.

Contrast this with controlling the acceleration (torque) of a car using only Proportional Gain as it approaches a target (Stop sign). At large distance we apply maximum acceleration. Although as we approach the stop sign we reduce acceleration, we continue to accelerate and speed continues to increase until we pass the stop sign. Torque mode servos are inherently unstable. P only gain only works at all if there is some friction (the car is dragging a sled which slows us down with less torque).

'''Acceleration Mode Servos''' may or may not have any feedback. If they have feedback it is usually used only to commutate a brushless motor. In the plots the Output (green) will have large magnitude when the Position (red) is accelerating, where the plot has curvature (changing slope).

Acceleration mode Servos are unlikely to work well or at all with only P Gain. Some form of damping or lead compensation will usually be required to get a stable system. D (derivative) Gain (or a lead compensator) should be included with the P Gain to help stabilize the system. D Gain can be increased to make the system more stable up to a point. After some point the additional D Gain will make the system more unstable. and should be reduced.

When using D Gain (or lead compensation) the quantization noise (steps) in the encoder position can cause spikes in the output. For example a D Gain of 100 will cause a spike of 100 counts in the output whenever the input changes suddenly by 1 count. If the spikes are very high amplitude and short duration, the Amplifier may not handle them in the expected manner. A low pass filter can be used to widen and reduce their amplitude allowing the amplifier to handle them more effectively. Typically a 2nd order low pass filter of 500Hz Q=1.4 is used. The last filter is normally used so it is applied to any Feed Forward. Such as:

[[File:LowPass400Q1p4.png|none|link=|680x439px]]

===Velocity, Acceleration, and Jerk===
<div id="yui_3_16_0_1_1445622719616_3315" class="yiv2818182665class" style="color: #000000; font-size: 13.3333px; font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif; background-color: transparent; font-style: normal;">The Velocity, Acceleration, and Jerk in the Step Response Screen (KFLOP parameter settings) and the Acceleration and Velocity in the KMotionCNC | Tool Setup | Trajectory Planner | Axis Parameters are both used for different things. The two sets of parameters are independent. </div>
<div id="yui_3_16_0_1_1445622719616_3313" class="yiv2818182665class" style="color: #000000; font-size: 13.3333px; font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif; background-color: transparent; font-style: normal;"> </div>
<div class="yiv2818182665class" style="color: #000000; font-size: 13.3333px; font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif; background-color: transparent; font-style: normal;">The KFLOP parameters are used for 3rd order motions. These include things like: Jogging, Homing, and GCode Rapids (G0). The units in KFLOP are in counts or steps. The KMotionCNC parameters are used for 2nd order (infinite Jerk) coordinated motion paths. These are GCode G1,G2,G3 continuous paths. The units are in Inches (or in some cases degrees). Note there is an Option in KMotionCNC "Rapids as Feeds" where these parameters will also be used for Rapids. But this option should only be used for highly non-linear Kinematic Systems which can not take advantage of faster/smoother 3rd order point to point straight line Rapids. </div>
<div class="yiv2818182665class" style="color: #000000; font-size: 13.3333px; font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif; background-color: transparent; font-style: normal;"></div>
<div class="yiv2818182665class" style="color: #000000; font-size: 13.3333px; font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif; background-color: transparent; font-style: normal;">Tests to find and verify optimal settings for both types of moves should be made using the Step Response Screen. Optimal settings are usually determined by experimentation. Although it might be possible to calculate the settings based on motor torque gains, back-emf, amplifier voltage/current, mass, moments of inertia, friction, encoder resolution, leadscrew pitch, required following accuracy, etc... It is often too complicated and with too many unknowns to be practical. So experimental moves can be tested at ever increasing Velocities, Accelerations, and Jerks until the system is unable to follow the trajectory without having too much error or shock to the system. After absolute limits of the system are determined then the settings should be backed off by some amount to provide operating margins (ie 20%). </div>
<div class="yiv2818182665class" style="color: #000000; font-size: 13.3333px; font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif; background-color: transparent; font-style: normal;">It is usually best to first determine max possible velocity using a relatively low acceleration. Maximum power is usually required at the point of the trajectory where velocity is high and still accelerating. Supply Voltage limitations tend to limit velocity. Current limitations tend to limit acceleration. </div>
<div class="yiv2818182665class" style="color: #000000; font-size: 13.3333px; font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif; background-color: transparent; font-style: normal;"></div>
<div class="yiv2818182665class" style="color: #000000; font-size: 13.3333px; font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif; background-color: transparent; font-style: normal;">[[File:MaxVelAccelPower.png|none|link=|485x361px]] The Step Response Screen always performs 3rd order motion but 2nd order motion can be simulated by temporarily setting the Jerk to a huge value (1000X the acceleration value). In general reducing the Jerk value will result in longer times to perform motions, but often the improved smoothness will permit higher maximum accelerations and velocities to be used resulting in overall shorter motion times. An analogy might be how you might stop more quickly in a car, without skidding or spilling your coffee, by applying the brakes harder in a more gradual manner rather than slamming on the brakes. Make sure when testing the size of move is long enough for full acceleration and velocity are achieved. A common mistake is to have Acceleration or Velocity Settings set to too high for your system but when testing a short move there is no indication of a problem. The plot mode of Velocity Output vs Time can be helpful to verify full Velocity is being achieved. </div>
<div class="yiv2818182665class" style="color: #000000; font-size: 13.3333px; font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif; background-color: transparent; font-style: normal;"></div>
<div class="yiv2818182665class" style="color: #000000; font-size: 13.3333px; font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif; background-color: transparent; font-style: normal;">The idea is that a motor axis has torque and speed limitations and you should determine and understand what they both are for your system. Available motor torque drops off with higher speed. At some speed the motor will not even be able to generate any torque at all. Motor torque is required to accelerate the axis. We need to make sure that no combination of velocity and acceleration will ever cause the axis to fault/stall/fail. So there is often a complex set of speeds and accelerations that will work ok that form an envelope of workable speed and acceleration. So one nice thing to know is top speed possible. It is like taking your car out on a long straight highway and gradually accelerating to find the max speed is 100MPH. You will then know that ever attempting a speed over 100MPH will always fail. Also speed should probably be limited to something like 80MPH to allow for margin and to allow reasonable acceleration up to that speed. The reason for performing the top speed test at low acceleration is to avoid a failure because of not being able to accelerate at the specified rate. So we want to set the acceleration to a low value so it will not be a limiting factor when determining top speed. However if we set the acceleration so low with a short trip distance we will never go very fast and the speed test will be meaningless. This should be avoided. Change the Plot type to Velocity, Output, vs Time to clearly see if this is the case. You may want to turn off Measured Velocity if it obscures viewing the Commanded Velocity For example to accelerate to 700,000 counts/sec at an acceleration rate of 700,000 counts/sec^2 would take 1 second. And then to slow back down would take 1 more second. So at least 2 seconds of motion would be required to get to full speed. A 100,000 count move (2 inches for a system with 50,000 counts/inch) takes much less time than that. Furthermore with a relatively low Jerk setting (1e6). This means the acceleration will be applied gradually over 0.7 seconds. This means an even much longer time and distance would be required to achieve top speed. Here is the method to follow to find 2nd/3rd order motion profile limits: (note every system is different and will vary based on resolution, motor size/type, mass, etc...)

'''1 - Find Max Velocity at low Acceleration and infinite Jerk'''

Choose a Velocity to test (ie V=100000 counts/sec) Set a moderately low Acceleration Time of 1 second (A = V/1sec = 100000 counts/sec^2) Set very high Jerk so Acceleration is applied almost instantaneously in 0.001 sec (J = A/0.001sec = 1e8 counst/sec^3) Test a very long move 20 inches if possible (for resolution 50000 counts/inch, 1,000,000 counts) Plot Velocity, Output, vs time to see if V is actually obtained If the motion was successful repeat all above with higher V, if not try lower V Once Max V is found reduce by some margin (ie 20-50%) Note you may decide on lower speed for other reasons (safety, vibration, noise, wobble, shock, etc....) '''2 - Find Max Acceleration for your system for the chosen Velocity'''

Using the V found above increase A (keeping Jerk high in the same manner) until the system fails/faults/excessive shock, etc... Once Max A is found reduce by some margin (ie 20-50%) These V and A Values are now known good values for your system and can be used for 2nd order motions such as KMotionCNC Trajectory Planner or Mach3 Motor tuning. Note units will need to be converted (counts to inches or mm, time from seconds to minutes depending on the App)

'''3 - Find optimal 3rd order Jerk limited motions.'''

The previous result from Step #1 and #2 used nearly infinite Jerk where Acceleration forces were applied nearly instantaneously. By reducing Jerk smoother motion should be possible. Set Jerk so it is applied over 20ms (ie for A=200000 J = A/0.020 = 1e7 Test to see if motions are smoother. With closed loop systems the Position Error Plot can be used to see if the motion has less error and is smoother. Open loop system will require you to hear the difference. Increase/decrease Jerk to find the optimal value. Note reducing Jerk a lot will of course make the system very smooth, but will also be much slower using less acceleration and velocity which is undesirable. So the highest Jerk possible should be found that still provides some smoothness. Reducing Jerk only will always make the system slower with less performance (but hopefully significantly smoother). It is usually then possible to increase Acceleration and Velocity somewhat to achieve even higher performance than what was possible with infinite Jerk while being as smooth or smoother.

'''4 - Reduce Max Following Error Limit to small value'''

</div>
<div class="yiv2818182665class" style="color: #000000; font-size: 13.3333px; font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif; background-color: transparent; font-style: normal;">Now that the system is properly tuned and reasonable Acceleration, Velocity, and Jerk are set the motor Position should always follow the commanded Destinations accurately with only small errors. By Plotting Position Errors under various conditions (Distances) you can get an idea of the worst case following errors under normal conditions. The Max Following Error Parameter should be set to a value slightly larger than the worst case following error (ie 20~50% larger). In this case if anything abnormal occurs: ie. The axis hits an obstacle, commanded at too high of a speed, servo goes unstable, hardware/electronics failure, a Following Error will be immediately detected and the axes disabled.</div>
<div class="yiv2818182665class" style="color: #000000; font-size: 13.3333px; font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif; background-color: transparent; font-style: normal;"></div>
===Axis Resolution - counts/inch (or counts/mm)===
<div class="yiv2818182665class" style="color: #000000; font-size: 13.3333px; font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif; background-color: transparent; font-style: normal;"></div>
<div class="yiv2818182665class" style="color: #000000; font-size: 13.3333px; font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif; background-color: transparent; font-style: normal;">Its important to understand the resolution of your Axis which is the number of fundamental raw motor/driver encoder counts or motor steps per standard unit of distance (inch or mm). Although tuning in KMotion.exe Step Response Screen and motions within KFLOP typically use units of raw counts or steps it is important to know how these translate to real-world distances, speeds, etc... Later, applications such as KMotionCNC or Mach3 will need this information to scale motions properly. </div>
<div class="yiv2818182665class" style="color: #000000; font-size: 13.3333px; font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif; background-color: transparent; font-style: normal;"></div>
<div class="yiv2818182665class" style="color: #000000; font-size: 13.3333px; font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif; background-color: transparent; font-style: normal;">There are usually a number of factors that combine together to determine the Axis Resolution. These might include:</div>
* counts or steps per motor revolution
* any gearing or belts and pulleys involved between motor and drive mechanisms
* lead screw pitch, rack and pinion tooth pitch, drive belt radius, etc.

For example consider a Stepper Drive with:

3200 steps per motor rev

2:1 gear reduction from motor to lead screw

0.2 inch lead screw pitch

Axis Resolution = 3200 step/motor rev x (2 motor rev/ screw rev) / (0.2 inch / screw rev) = 32000 steps/inch

To determine whether your assumptions and calculations are correct perform a test. Command as large of a move as convenient and measure the actual distance moved with a ruler. For example in the axis described above you might command a move of 320000 steps. This should result in a motion of:

320000 steps / (32000 steps/inch) = 10 inches.

For KMotionCNC set the Axis Resolution in the [http://dynomotion.com/Help/KMotionCNC/ToolSetupScreenTP.htm#Axis_Motion_Parameters Tool Setup | Trajectory Planner Screen | Axis Parameters | cnts/inch]. Note units must be in units of inches. If your resolution is in mm units multiply by 25.4.

For Mach3 enter the Axis Resolution in the Configuration | Motor Tuning Screen. Make sure the setup units (not GCode units) match the mode of your values.

===Servo Dither/Hunting - (oscillation around zero error)===
<div class="yiv2818182665class" style="color: #000000; font-size: 13.3333px; font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif; background-color: transparent; font-style: normal;"></div>
<div class="yiv2818182665class" style="color: #000000; font-size: 13.3333px; font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif; background-color: transparent; font-style: normal;">Servos have high accuracy because they are always actively trying to make corrections and drive the error to zero. Unfortunately this can sometimes cause annoying dither or position hunting around zero when not moving. This is a very complex non-linear effect dependent on the dynamics of the mechanics. Because of the highly non-linear quantization effects of single "steps" in the encoder position, stiction, backlash, etc. it follows different rules and is harder to analyze than normal servo tuning/stability in the larger magnitude more linear regime. For example attempting to apply "Damping" is unlikely to work. Lowering gains will usually help at the expense of performance. However in many cases more than acceptable performance can be achieved with lower gains so one should consider if the higher gains are really needed. KFLOP has a Deadband Gain and Range feature that can basically be used to tell the servo to not attempt to correct small errors (treat the errors as zero), or to try to correct them less aggressively (with a Gain less than 1.0). See [http://dynomotion.com/Help/StepScreen/StepScreen.htm#Dead_Band here for more information] Unfortunately adding Deadband doesn't always help the servo "sit still" and may actually increase the size of the dither depending on the dynamics.
 Note that when the servo is commanded to a non integer position ie 999999.7 encoder counts without deadband the servo will always be making corrections. The best the servo can do is dither between encoder positions 999999.0 and 1000000.0. With an error of either -0.7 or +0.3. A servo with Integrator gain will guarantee the average is 999999.7 If dither is still a major problem a C Program might be used to monitor things and change settings under certain conditions to reduce dither. See the example AntiServoDither__ALL.c which monitors for small errors for a period of time and if so reduces or turns off Integrator gain. 

</div>
===Noisy GCode - Trajectory Planner Smoothing===
<div class="yiv2818182665class" style="color: #000000; font-size: 13.3333px; font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif; background-color: transparent; font-style: normal;">An analysis of Quantization Noise in GCode and Trajectory Planner Settings to generate smooth motion. [[File:GCode_Noisy_Path.png|none|link=|432x432px]]</div>
<div class="yiv2818182665class" style="color: #000000; font-size: 13.3333px; font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif; background-color: transparent; font-style: normal;">[[Trajectory Planner Smoothing Noisy GCode|See Analysis and Solution]]</div>
<div class="yiv2818182665class" style="color: #000000; font-size: 13.3333px; font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif; background-color: transparent; font-style: normal;"></div>
===Arc "faceting" - Trajectory Planner - Collinear Tolerance===
<div class="yiv2818182665class" style="color: #000000; font-size: 13.3333px; font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif; background-color: transparent; font-style: normal;"></div>
<div class="yiv2818182665class" style="color: #000000; font-size: 13.3333px; font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif; background-color: transparent; font-style: normal;">[[File:ArcsTrajectoryZoomXTol.0005.png|none|link=|526x460px]]</div>
<div class="yiv2818182665class" style="color: #000000; font-size: 13.3333px; font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif; background-color: transparent; font-style: normal;"></div>
<div class="yiv2818182665class" style="color: #000000; font-size: 13.3333px; font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif; background-color: transparent; font-style: normal;">[[ArcFacetingColinearTol|See Analysis and Solution]]</div>
<div class="yiv2818182665class" style="color: #000000; font-size: 13.3333px; font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif; background-color: transparent; font-style: normal;"></div>
===I Gain/Max Limit Integrator===
I (Integrator) Gain can be used to eliminate persistent errors. In fact any Integrator Gain at all guarantees the average error over infinite time is zero. Without I Gain a system might have a small error that does not create enough output to overcome stiction to make a correction. In such a case the error could persist forever. Not so with any Integrator Gain. Any error will be integrated and ramp the output higher and higher until eventually there will be a correction. That assumes the Integrator or Output doesn't saturate or reach their programmed limits. The rate the output ramps (or sums) is dependent on the size of the error and the I Gain value. The Error x I Gain is summed every servo sample (90us). This is why I Gain values are often small numbers (0.0001 - 0.01 typical range). There is no guarantee that the position doesn't over shoot the target Destination. In fact it is likely as as any error (area) under the trajectory will always be balanced by an equal area over the trajectory. Too high of I Gain will make the system unstable.

Another case where I Gain is useful is when moving at high speed with a Velocity Amplifier. To move at high speed a significant amount of output is required. Without I Gain a significant amount of error could be required to provide this Output (ie Error x P Gain = Output). With I Gain the Integrator will eventually ramp up to provide any Output necessary to move at the desired speed driving the error to zero.

Integrators have an issue often referred to as "Integrator Wind Up". This issue usually doesn't arise under normal conditions. However if something is preventing the servo from making a correction such as forcing the position away from the target for a sustained amount of time, or disabling the amplifier, the Integrator will integrate to a huge unlimited value. When the force is removed or amplifier re-enabled, the Integrator will likely cause a violent motion and overshoot. Max Limit Integrator can help to minimize this issue by limiting the amount the Integrator can ramp up to. So the Max Limit Integrator Value should be set at the minimum value that can still allow the Integrator to function in normal circumstances.

Typically there are two cases that should be considered when determining the Max Limit Integrator.

# The amount of output expected to be required to overcome any stiction, friction, or other forces (cutting, gravity, etc...). This is often not a large value and can be estimated or can be observed from the Step Response Screen (green plot right side scale is the output) when making a move.
# The amount of output required to provide the output needed to move at speed. It is important to note that D Gain provides a damping or drag effect on the Output. So the Integrator must be able to ramp up to a sufficient level to overcome the damping or drag effect and still provide enough output to move at the commanded speed. For example:

Assume:

# Commanded speed of 500,000 counts/sec
# D Gain of 35
# Output required to move at speed is 1800 DAC Counts
# Servo Sample Time of 90us

Damping effect = Speed x D Gain x Sample Time = 500000 x 35 x 90e-6 = 1575 counts

Required Integrator Value = 1800 + 1575 = 3375

So to provide some margin an Max Limit Integrator Value of 3500 might be used.

===Max Limits - Error===
Max limits error can be helpful to have your system respond less violently in the abnormal event where an excessively large error occurs. Normally with a properly tuned system following errors should be small. Setting a Max limits error can cause the servo to treat errors beyond a specified limit as if they were only the size of the limit and therefore respond less so than they would otherwise. The max limits error is normally set to a value so it is not limiting under normal circumstances.

The Plot below shows a situation where a small max limits error combined with a low P gain severely limits the Output. In the plot below a large move (10000 counts) at a high speed (40000 counts/sec) is commanded. Only P Gain (0.2) is used to provide the Output (green). The max error limit of 200 combined with the low gain (0.2) limits the output to only 40 DAC counts. Even as the true error increases to many thousands of counts, the servo is told to ignore the amount over 200. So the output can never exceed 40 DAC counts. The 40 DAC count limit means that the Axis is therefor not capable of providing the output necessary to keep up with the commanded motion. The axis does the best it can with the limited output, and only does a fraction of the desired motion.

[[File:Move10000.png|none|link=|665x431px]]

After increasing the max limits error the Output (green - right scale) now goes to a much higher value (900), and the Position (red) follows the Command (blue) to a much better degree.

[[File:Move10000_nolimit.png|none|link=|667x430px]]

Increasing the P Gain to 1.6 also applies more Output sooner and the Position follows the command still better.

[[File:Move1000_p1.6.png|none|link=|667x432px]]

===Lead Compensator vs Derivative Gain===
Derivative (D) Gain is often used to help stabilize a system.  It helps to think in the Frequency Domain to help understand how the two forms of compensation help.  Please read below and [http://dynomotion.com/Help/BodeScreen/BodeScreen.htm this] for more information on the Frequency Domain.  Both Compensation methods add positive phase to help stabilize the system.  Unfortunately both methods increase gain at higher frequencies possibly causing the system to go unstable at higher frequency.  A Lead Compensator provides the benefit of positive phase but without as much gain increase at higher frequencies.  This figure shows a simplified Gain Plot comparison:

[[File:DGainvsLead.png|none|link=|593x593px]]

Here is a Bode Plot of a P=0.5 D=20 Compensator. Note the KMotion.exe Bode Plot Screen has the capability of plotting the Frequency Domain Response of the PID+Filters Compensation. Assume we desire positive phase to be added at 40Hz. Notice the positive phase of 40 degrees at 40Hz which is good. However the Gain increase in the 1KHz region of about 21db which is bad.

[[File:P.5D20Annotate.png|none|link=|621x460px]]

Here is a Bode Plot of a P=0.5 N1=N2=25Hz D1=D2=70Hz Compensator. Assume we desire positive phase to be added at 40Hz. We choose N1 N2 and D1 D2 to surround the frequency where the positive phase is desired. Moving them further apart will increase the amount of positive phase but also increase the added Gain. Notice the positive phase of 60 degrees at 40Hz which is good. However the Gain increase in the 1KHz region of about 12db which is bad. However both are improvements over the D Gain compensator.

[[File:PoleZeroFilter.png|none|link=|210x319px]]

[[File:P.5D0N25D70Annotate.png|none|link=|644x478px]]

===Tuning Master/Slave Configurations===
Master/Slave [http://dynomotion.com/Help/ConfigurationScreen/ConfigurationScreen.htm#Master/Slave_Settings Configurations] allow two (or more) motors to drive the same axis. Slaves are configured to follow a Master Axis. For example two lead screws on both sides of a gantry.

Tuning slaved axes is kind of a catch 22. In order to tune one axis the other axis must be tuned well enough to follow and vice versa. If possible, disconnect any mechanical linkage between the Master and Slave and test them separately without Slaving the Axes together to verify each axis Servos (can hold a position), moves at least somewhat properly, and moves in the same direction (assuming a positive [http://dynomotion.com/Help/ConfigurationScreen/ConfigurationScreen.htm#Master/Slave_Settings Slave Gain] will be used).

It is usually possible to incrementally tune each axis, at first moving slowly, then later at higher speeds, accelerations, and gains. Only the Master Axis can be tested with the [http://dynomotion.com/Help/StepScreen/StepScreen.htm Step Response Screen]. This is because the Slave will follow any movement of the Master, but the Master will not follow movement of the Slave. So if the Master Axis is moved all is well as both axes will move together, but if you try to move the Slave axis the two axes will fight. The Master fighting to stay where it is, and the Slave fighting to move.

To test/tune the Slave axis temporarily reverse the Master/Slave roles to make it the Master and then test it as the Master.

Note: only the Master Axis should be included into the Coordinated Motion System.

===Bode Plots===
A Bode Plot is a powerful tool for characterizing and providing insight into a dynamic system. It can help determine closed loop stability, bandwidth/performance, resonant frequencies, and more. It is entirely based on the system being linear. Linear in the sense that if the amplitude of some input signal is changed then the output signal will change proportionally as well. Unfortunately most systems are not entirely linear. Stiction, backlash, encoder quantization, amplifier saturation, and other effects are non-linear. For example driving a system with a signal too small to overcome stiction will result in no output at all whereas a larger signal will result in some output. This is clearly non-linear behavior. It would be nice to use a technique that handles non-linear systems but basically none are known. A Bode Plot is made injecting a stimulus to the system and observing how the system responds. For the reasons of non-linearity it is very important to perform a Bode Plot measurement using a representative level of stimulus similar to what the system will actually have during normal operation. If the Stimulus is not adjusted properly the result is likely to be completely invalid. Additionally the system should be reasonably tuned and stable so that it is responding in a reasonable way to the stimulus. If the system is unstable or very poorly tuned the result is likely to be completely invalid. You might think of it somewhat like shaking a box to determine what is in it. You should shake it with enough intensity and at frequencies to get some reaction, but not so high of intensity to break or distort the object inside. To create a Bode Plot use the KMotion.exe Bode Plot Screen. First select Plot: Time domain - Command, Position, Output vs Time and adjust the Amplitude and cutoff Freq until there is small but significant Position (red) changes (ie 50 encoder counts), at a frequency low enough that the Position at least somewhat attempts to follow the Command (blue), and where the Output (green) is not near saturation for the Drive being used. After the Stimulus/Noise Injection settings are set switch to Plot: Open Loop - Magnitude and Phase vs Frequency. Set the number of Samples to average (ie 20) and perform a Measurement.  [http://dynomotion.com/Help/BodeScreen/BodeScreen.htm See here for more information].

===Links to other Information on Tuning and Bode Plots===
[http://ctms.engin.umich.edu/CTMS/index.php?example=Introduction&section=ControlFrequency umich.edu Introduction section Control Frequency]

[http://www.motiontech.com.au/assets/pdf/Kollmorgen%20Use%20Control%20Theory%20to%20Improve%20Servo%20Performance%20230712.pdf Kollmorgen Use Control Theory to Improve Servo Performance 230712.pdf]

==Problems and Resolutions==
====General====
:* [[Noise - Typical Problems and Resolutions|Dealing with noise on inputs]]. If you experience issues with inputs misreading, the issue may be noise. This page provides examples on what might be causing noise issues and examples of how to possibly deal with noise.
:* Other
===Software-Specific Problems and Resolutions===
:* Place links to pages explaining resolutions to problems that are largely software-related here
[[KFLOP User C Programs Compiling/Launching Slowly because of Windows Defender]]

===Hardware-Specific Problems and Resolutions===
:* Place links to pages explaining resolutions to problems that are largely hardware-related
====[[Step/Dir Drives lose 2 Steps for each pair of Direction Reversals]]====

==Applications and Projects==
:* Place links to pages that explain how you accomplished your particular project. Write clear explanations that provide background on what you did and how you did it.
====[[Tool Changer - router linear 4 Tools - C Program]]====
[[File:LINEAT+ATC.jpg|none|link=|246x178px]]
More linear milling tools: https://www.ichome.com/

====[[Part Zero & Tool Height Touch Plate|Part Zero & Tool Height Touch Plate]]====
====[[Driving Hobby Servos]]====
[[File:HobbyServo.png|left|link=]]

HiTec Type

==Electrical Discharge Machining==
[https://en.wikipedia.org/wiki/Electrical_discharge_machining EDM (wikipedia)] is a method of cutting materials with high precision and detail. Dynomotion Motion Controllers work well for EDM because of the ability for feedrate to be dynamically controlled including reversal along cutting path.

[[Information on BAXEDM Arc Generators used with KFLOP]]

Applied Science video that shows how to build an BAXEDM drilling machine using KFLOP and describes how it works:

{{#ev:youtube|https://youtu.be/rpHYBz7ToII|||||start=980}}

==How to convert a milling machine to a 3D printer in 3 easy steps==
[[File:CNCto3DPrinter.png|none|link=]]

More information [[How to convert a milling machine to a 3D printer in 3 easy steps|here]].

==International and other Languages==
[[Russian]]

[[Spanish]]

Linear Table Correction

2024-06-24T00:19:08Z

TK: /* Linear Table Correction */

==Linear Table Correction==
Besides the [https://dynomotion.com/Help/KMotionCNC/GeoCorrection.htm 2.5D Geometric Correction capability] 1D Linear Table corrections can be applied to each axis independently. Lead Screw mapping fits into this category where there a nonlinear distortion of the commanded axis position to the true position of the axis.

Each or both 2.5D Geo Correction and 1D Linear correction can be applied. If both are applied then the 2.5D Geo Correction is applied first and then the Actuator positions have 1D Linear corrections applied. Between Points a linear interpolation is used.

Below is shown an example plot of a correction table for an angular A axis. The table values contain the commanded positions required to position at the theoretical positions. For example in the plot below to move to angle 0 the axis actually needs to be commanded to 10 degrees. To move to 90 degrees the axis would need to be commanded to 95 degrees. Note these values are exaggerated over what they would typically be for a real system for demonstration purposes. The example is created using a cosine function where the correction is 0 at -80 and +180 degrees and 10 degrees at 0 degrees.

The actual table contains a list of necessary commanded position but the plot below shows the difference between the commanded positions and the theoretical positions to plot errors and to make the errors more visible.

[[File:CosineCorrection_Excel_Plot.png|none|link=]]

Below is a fragment of the text file for a Linear Correction Table. The first 3 lines define the table range.

Line 1 contains the number of commanded positions. Note that for N ranges N+1 points must be specified. The example defined 180 2 degree ranges so 181 points are required.

Line 2 defines the size of each range. In this case 2 degrees.

Line 3 defines the offset or starting point for the table. In this example it is assumed the useful machine range is from -180 to +180 degrees. So the Table offset is -180. The A axis theoretically goes from -infinity to +infinity so it must be specified what range the table should be applied. If the machine coordinates operated from 0 to 360 degrees then the offset would be 0.

Line 4 through N+3 defines the actual axis commanded values preceded by the point number. The points may be specified in any order as long as all point numbers are specified.

[[File:MapFile.png|none|link=]]

The Tool Setup | Tool/Setup Files | Geo File specifies the root of which files are to be used. The file name itself specified the name of the 2.5D Geo Correction file. The Linear Table corrections files are derived from this name by appending: '_X', '_Y', '_Z ', '_A', '_B' or '_C' before any suffix. So assuming a Geo Correction name of C:\Temp\MapFile.txt the Linear Table Names would be

C:\Temp\MapFile_X.txt

C:\Temp\MapFile_Y.txt

C:\Temp\MapFile_Z.txt

C:\Temp\MapFile_A.txt

C:\Temp\MapFile_B.txt

C:\Temp\MapFile_C.txt

 The Software will automatically search for these files and apply corrections for the found files. The 2.5D Geo Correction file may or may not be present. But at least one file must be present and valid. [[File:GeoFile.png|none|link=]]

With the above Linear Correction in effect and the GCode A Axis commanded to 0 degrees note that the actual commanded axis position is 1000 counts. This corresponds to a 10 degree offset because the trajectory Planner settings are specified to be 100 count/degree

[[File:A0_Correction10.png|none|link=]]

Here the GCode A Axis commanded to -90 degrees note that the actual commanded axis position is -8500 counts (-85 degrees). This corresponds to a +5 degree offset

[[File:A-90_Correction5.png|none|link=]]

Here the GCode A Axis commanded to -180 degrees note that the actual commanded axis position is -18000 counts (-90 degrees). This corresponds to no offset

[[File:A-180_Correction0.png|none|link=]]

Below is an example KFLOP/Kogna C Program that was used to create the MapFile_A.txt file

<pre class="brush:c">#include "KMotionDef.h"

// Create Simple Linear Correction file for A axis

int main(void)
{
int i;
double angle, error;

// Calibrate Table for A -180 to +180 degrees at 2 degree increments
FILE *f=fopen("C:\\Temp\\MapFile_A.txt","wt");
fprintf(f,"181\n"); // 181 points specify 180 regions
fprintf(f,"2.0\n"); // 2 degree Spacing
fprintf(f,"-180\n"); // Offset - Table begins at -180

// use dummy correction of cosine function with no error
// at -180 and +180 but 10 degrees at center (0 degrees)

for (i=0; i<181; i++)
{
angle = -180.0 + i * 2.0;
error = (cos(angle * PI/180.0)+1)/2.0 * 10.0;
fprintf(f,"%d,%.11f\n", i, angle+error);
}

fclose(f);
}
</pre>

This is the Excel Spreadsheet used to create the Error Plot from the Linear Table file.

[[:Media:PlotLinearCorrectionTable.xlsx|PlotLinearCorrectionTable.xlsx]]

Linear Table Correction

2024-06-23T23:43:09Z

2024-05-09T23:07:09Z

TK: /* KFLOP KStep JR1 Molex Power Connectors additional P#*/

=='''Dynomotion wiki'''''' '''==
Welcome to our wiki where you can find and share knowledge on Dynomotion's systems. To begin adding information to this wiki, simply create an account, verify your email, and start editing (click pencil icon). To make editing pages easier for everyone, we have installed a [https://help.bluespice.com/index.php/VisualEditor visual editor] by default. This visual editor allows you to edit a wiki page much like you would a standard word processing document.  For the seasoned wiki editors, standard [https://www.mediawiki.org/wiki/Help:Editing MediaWiki editing] may also be used.<nowiki> </nowiki>

''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 is safe to use. In no case will any contributor or Dynomotion be liable for incorrect information. Dynomotion reserves the right to modify or delete any contributions. ''

 Thanks for Contributing!

[http://dynomotion.com Official Dynomotion Site]

==Editing and Creating Wiki Pages==
Unintuitively, you first create a link to the page you want to make before you can make the page. To make a new page: while editing, right-click where you want your link to be, insert a link with a descriptive title and link text, save the page, click on the link you created, then click on "Empty Page" to begin editing your new page.

Here are a few other quick tips:

* You can insert links or images by Right-Clicking with the mouse on the line where you want the link or image to appear.
* For Spell Correction you can use Ctrl-Right-Click.
* To insert a YouTube Video use an EmbedVideo command such as <nowiki> {{#ev:youtube|xxxxx}}
</nowiki>with xxxxx changed to the Video ID.
* Choose a descriptive page name and link text when creating a new page: e.g. Not "My Machine", but rather "Brand X Three Axis Milling Machine Retrofit"
* Create pages in an organized manner: Describe what the page is about, create clear sections that flow

For more information:

[[Help:New Page Creation|How to create a new wiki page]]

[[Help:Editing Pages|How to Edit and insert Media into your wiki pages]]

==Dynomotion Software Topics==
===Installation Topics===
* Announcement of our Latest Release (5.3.3) on the [https://www.dynomotion.com/forum/viewtopic.php?f=4&t=1752 Dynomotion Forum]
* [https://dynomotion.com/Software/Download.html Latest Release] Note: For Windows 7 64bit signed Drivers to work, all Windows Updates should be performed.
* [[Upgrading from previous KMotion Versions]]

Archive of Test Releases:

* Previous Test Release: 02/01/2024: [https://dynomotion.com/Software/KMotion5.3.2.exe KMotion.exe 5.3.2], See the release notes for this test version here: [https://dynomotion.com/Software/KMotion%20Released%20Version%205.3.2%20Changes.pdf 5.3.2 release notes (pdf)]
* Previous Test Release: 11/20/2023: [https://dynomotion.com/Software/KMotion5.3.1.exe KMotion.exe 5.3.1], See the release notes for this test version here: [https://dynomotion.com/Software/KMotion%20Released%20Version%205.3.1%20Changes.pdf 5.3.1 release notes (pdf)]
* Previous Test Release: 09/19/2023: [https://dynomotion.com/Software/KMotion5.3.0.exe KMotion.exe 5.3.0], See the release notes for this test version here: [https://dynomotion.com/Software/KMotion%20Released%20Version%205.3.0%20Changes.pdf 5.3.0 release notes (pdf)]
* Previous Test Release: 06/30/2023: [https://dynomotion.com/Software/KMotion5.1.0.exe KMotion.exe 5.1.0], See the release notes for this test version here: [https://dynomotion.com/Software/KMotion%20Released%20Version%205.1.0%20Changes.pdf 5.1.0 release notes (pdf)]
* Previous Test Release: 05/01/2023: [https://dynomotion.com/Software/KMotion5.0.7.exe KMotion.exe 5.0.7], See the release notes for this test version here: [https://dynomotion.com/Software/KMotion%20Released%20Version%205.0.7%20Changes.pdf 5.0.7 release notes (pdf)]
* Previous Test Release: 09/21/2022: [https://dynomotion.com/Software/KMotion435h.exe KMotion.exe V4.35h], See the release notes for this test version here: [https://dynomotion.com/Software/KMotion%20Released%20Version%204.35h%20Changes.pdf V4.35h release notes (pdf)]
* Previous Version 4.35g was not released, but see the change notes for this version here: [https://dynomotion.com/Software/KMotion%20Released%20Version%204.35g%20Changes.pdf V4.35g change notes (pdf)]
* Previous Test Release: 12/28/2020: [https://dynomotion.com/Software/KMotion435f.exe KMotion.exe V4.35f], See the release notes for this test version here: [https://dynomotion.com/Software/KMotion%20Released%20Version%204.35f%20Changes.pdf V4.35f release notes (pdf)]
* Previous Test Release: 11/18/2019: [https://dynomotion.com/Software/KMotion435e.exe KMotion.exe V4.35e], See the release notes for this test version here: [https://dynomotion.com/Software/KMotion%20Released%20Version%204.35e%20Changes.pdf V4.35e release notes (pdf)]
* Previous Test Release: 09/10/2019: [https://dynomotion.com/Software/KMotion435d.exe KMotion.exe V4.35d], See the release notes for this test version here: [https://dynomotion.com/Software/KMotion%20Released%20Version%204.35d%20Changes.pdf V4.35d release notes (pdf)]
* Previous Test Release: 01/28/2019: [https://dynomotion.com/Software/KMotion435b.exe KMotion.exe V4.35b], See the release notes for this test version here: [https://dynomotion.com/Software/KMotion%20Released%20Version%204.35b%20Changes.pdf V4.35b release notes (pdf)]
* Previous Test Release: 12/21/2018: [https://dynomotion.com/Software/KMotion435a.exe KMotion.exe V4.35a], See the release notes for this test version here: [https://dynomotion.com/Software/KMotion%20Released%20Version%204.35a%20Changes.pdf V4.35a release notes (pdf)]
* Previous Test Release: 09/28/2017: [https://dynomotion.com/Software/KMotion434j.exe KMotion.exe V4.34j], See the release notes for this test version here: [https://dynomotion.com/Software/KMotion%20Released%20Version%204.34j%20Changes.pdf V4.34j release notes (pdf)]
* Previous Test Release: 05/07/2017: [https://dynomotion.com/Software/KMotion434i.exe KMotion.exe V4.34i], See the release notes for this test version here: [https://dynomotion.com/Software/KMotion%20Released%20Version%204.34i%20Changes.pdf V4.34i release notes (pdf)]
* Previous Test Release: 12/14/2016: [https://dynomotion.com/Software/KMotion434h.exe KMotion.exe V4.34h], See the release notes for this test version here: [https://dynomotion.com/Software/KMotion%20Released%20Version%204.34h%20Changes.pdf V4.34h release notes (pdf)]
* Previous Test Release: 12/13/2016: [https://dynomotion.com/Software/KMotion434g.exe KMotion.exe V4.34g], See the release notes for this test version here: [https://dynomotion.com/Software/KMotion%20Released%20Version%204.34g%20Changes.pdf V4.34g release notes (pdf)]
* Previous Test Release: 12/05/2016: [https://dynomotion.com/Software/KMotion434f.exe KMotion.exe V4.34f], See the release notes for this test version here: [https://dynomotion.com/Software/KMotion%20Released%20Version%204.34f%20Changes.pdf V4.34f release notes (pdf)]
* Previous Test Release: 11/07/2016: [https://dynomotion.com/Software/KMotion434e.exe KMotion.exe V4.34e], See the release notes for this test version here: [https://dynomotion.com/Software/KMotion%20Released%20Version%204.34e%20Changes.pdf V4.34e release notes (pdf)]
* Previous Test Release: 10/32/2016: [https://dynomotion.com/Software/KMotion434d.exe KMotion.exe V4.34d], See the release notes for this test version here: [https://dynomotion.com/Software/KMotion%20Released%20Version%204.34d%20Changes.pdf V4.34d release notes (pdf)]
* Previous Test Release: 10/23/2016: [https://dynomotion.com/Software/KMotion434c.exe KMotion.exe V4.34c], See the release notes for this test version here: [https://dynomotion.com/Software/KMotion%20Released%20Version%204.34c%20Changes.pdf V4.34c release notes (pdf)]
* Previous Test Release: 10/03/2016: [https://dynomotion.com/Software/KMotion434b.exe KMotion.exe V4.34b], See the release notes for this test version here: [https://dynomotion.com/Software/KMotion%20Released%20Version%204.34b%20Changes.pdf V4.34b release notes (pdf)]
* Previous Test Release: 03/09/2016: [https://dynomotion.com/Software/KMotion434a.exe KMotion.exe V4.34a], See the release notes for this test version here: [https://dynomotion.com/Software/KMotion%20Released%20Version%204.34a%20Changes.pdf V4.34a release notes (pdf)]
* [https://dynomotion.com/Help/KFLOPQuickStart/KFLOPQuickStart.htm How to install KMotion.exe and KMotionCNC]
* [[How to install KMotion.exe and KMotion in Windows 10|Preparing Windows 10 for driver installation]] (no longer required)
* [[Special Case for Windows 8.1 Industry Embedded Enterprise]]
* [[Updating KFLOP Firmware|How to update KFLOP Firmware]] - whenever a new version of software is installed, the firmware within KFLOP must be updated to match the new version

===KMotion.exe Executive Software Topics===
KMotion.exe is the main program that is used to configure settings in KFLOP, initialize axes, and to write C programs to configure and setup KFLOP to control your system. In this program you can plot step response, test movement, view Bode plots, monitor I/O, set filter parameters, and generally set the pertinent parameters.

* [http://www.dynomotion.com/Help/index.htm General software information] from the manuals
* Insert pages for other KMotion.exe-related topics here

===Configuration Topics===
====Channels, Channels, Channels what are they?====
[[Channels Channels Channels|Read Article Here]]

====How to Setup Backlash Compensation====
[[Backlash Compensation|Read Article Here]]

====PWM Output Mode====
[[PWM Output Mode|Read Article Here]]

===KMotionCNC Software Topics===
KMotionCNC is Dynomotion's CNC program used as a graphical user interface to your KFLOP-enabled machine tool. KMotionCNC has all of the basic functionality you need to run a machine of up to 6 axes, in addition to spindle control.

* Insert pages for other KMotionCNC-related general topics here

====Using KMotionCNC====
* Homing discussion - page to be created
* Insert other KMotionCNC use pages here

[[Internal/concave Path Tool Radius Compensation Example G41/G42]]

[[Known KMotionCNC CAD/CAM Post Processors]]

[[Invoking C Programs with Execute Only for previously Downloaded Programs]]

[[Rigid Tapping G84 Setup and Use]]

[[Tool Length/Offsets G43Hn G49]]

====Customize KMotionCNC====
KMotionCNC is written as a Windows C++ MFC (Microsoft Foundation Classes) program developed in Visual Studio. Source code is provided and may be customized using Visual Studio. MFC Support is a requirement.

: '''General Information'''
: Compiling KMotionCNC
:: The KMotionCNC's Visual Studio Project Solution (\PC VC Programs\KMotionCNC\KMotionCNC.sln) is currently written for Visual Studio 2015 Standard. This version can be used for the simplest compatibility. Projects can be upgraded to newer version of VS with minimal effort. Including Microsoft's Free Visual Studio 2013 Community. [[PC Example Applications|More info on PC Example Applications.]]
:: Note Test Versions 4.34a and later have project solutions targeted for Visual Studio 2015 Community which is free for most Users.
: '''KMotionCNC Customization Examples and Applications'''
:: Links to examples of projects that explain KMotionCNC customizations. Troy (tmday7) created some helpful documents (PDF format):
:
:* [https://www.dynomotion.com/forum/archive/attachments/How%20to%20Edit%20KMotionCNC%20Faces.pdf How to edit KMotionCNC faces]
:* [https://www.dynomotion.com/forum/archive/attachments/Adding%20External%20Buttons.pdf Adding external buttons]
:* [https://www.dynomotion.com/forum/archive/attachments/Adding%20More%20User%20Buttons.pdf Adding more user buttons]
:* [https://www.dynomotion.com/forum/archive/attachments/Adding%20Jog%20Percent%20Cell%20to%20Main%20Dialog%20Face.pdf Adding Jog Percent Cell to Main Dialog Face]

====KMotionCNC Screen Editor====
Introduces the capability of using Screen Script files to modify the look and function of KMotionCNC. [[KMotionCNC Screen Editor|More information.]]

====KMotionCNC Geometric Correction====
Information regarding the powerful [https://dynomotion.com/Help/KMotionCNC/GeoCorrection.htm Geometric Correction capability] which allows calibration and distortion correction of the XY CAD space to Machine/Actuator Space as well as flatness in Z. Simple 4 point correction tables can apply XY Scale, Rotation, skew, offset, tilt. Larger tables can apply more non-linear corrections.

Note the Geometric Correction is built into the KMotion Libraries and can be utilized by Custom Programs as well as with KMotionCNC [[Geometric Correction|More information and Examples.]]

===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. 

'''Note All the projects in KMotion Versions 4.34a and later have now been updated and should work out-of-the-box with VS2015.'''

[[PC Example Applications|More information.]]

===KMotion Libraries - GCode Interpreter - Trajectory Planner - Coordinated Motion - .NET===
The KMotion Libraries are a series of DLLs (Dynamic Link Libraries) that reside on the PC that contain the common core motion control, I/O, and communication functionality for KFLOP. These libraries permit PC Applications to be built using high level control without being concerned with the underlying details of Interpreting GCode, Trajectory Planning, Coordinated Motion, Motion Buffering, USB Communication, etc.

[[KMotion Libraries - GCode Interpreter - Trajectory Planner - Coordinated Motion - .NET|More information]].

===Kinematics===
The KMotion Libraries contain a Kinematics Layer where Users can add their own non-linear Kinematics

[[Kinematics|More information]].

===KFLOP C Programs===
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.

[[KFLOP C Programs|More Information]]

===ModBus===
Modbus can be connected to the PC or directly to KFLOP. A PC connection will not be deterministically real-time but may work for basic speed control and on/off. Here is a related Thread for interfacing KMotionCNC to Modbus using a [http://www.modbusdriver.com/modpoll.html free utility]:

[https://www.dynomotion.com/forum/archive/sending%20ModBus%20msgs%20from%20KmotionCNC%20to%20a%20RS485%20port.html Sending ModBus msgs from KmotionCNC to a RS485 port]

To connect Modbus directly to KFLOP's [http://www.dynomotion.com/Help/RS232/RS232.htm UART] see the C Examples in \C Programs\RS232\ModBus\

===Linux Support===
KMotion Motion Libraries are fully supported under Microsoft Windows. Some Users have ported the KMotion Libraries to Linux. Dynomotion will offer support where possible but can't offer full support under Linux. Special Thanks to [https://github.com/parhansson/KMotionX Par Hansson] for the initial Linux Port.

See [[Linux|here]] for more info.

==Dynomotion Hardware Topics==
===General Hardware Information===
====[[KFLOP Hardware Info|KFLOP specific Hardware Info]]====
====[[KStep Hardware Info|KStep specific Hardware Info]]====
====[[Kanalog Hardware Info|Kanalog specific Hardware Info]]====
====[[SnapAmp Info|SnapAmp specific Hardware Info]]====
====[[Konnect Hardware Info|Konnect specific Hardware Info]]====

===Wiring Diagrams===
[[Media:Kanalog_Connections.pdf|Basic Kanalog DAC and Encoder Connections 3 Axis]]

[[Media:KanalogSchematic3Axis.pdf|Basic Kanalog DAC and Encoder Connections 3 Axis #2]]

[[Media:dyn4 kanalog KE1524 V1.1.png|Basic Kanalog DAC and DMM DYN4 Drive 1 Axis]]

[[Media:Kflop-Kanalog_wiring_11-19-2018.pdf|Kanalog with Geckos G210 updated 11-19-2018]] (Thanks to Joseph Mirocha)

[[Media:Kanalog_to_Tree_Journeyman_325_by_Rick_B.pdf|Kanalog to Tree Journeyman 325.pdf]] (Thanks to Rick_B)

[[Media:KFlopSnapBrushMPG.pdf|KFLOP+SnapAmp DC Brush Motors with MPG]]

[[Media:Stepper_Wiring_Diagram_Step-Dir_on_JP5.pdf|KFLOP JP5 Open Collector Step/Dir Connections to Power Step PSD5042-2P Drives ]]

[[Media:Matrika_V1_wiring_diagram_Rev1.pdf|KFLOP+KStep with VFD and NPN Limit Switches for Matrika Rev1]]

[[Media:KonnectTouchPlate.png|Touch Plate Wiring to Konnect]]

[https://easyeda.com/350banshee/BreakoutBoard-93bdd16e3c3d48b98ae66c34f2436c40 User Created KFLOP JP7 Breakout/OptoIsolation Board] Schematic, Gerbers, PCBs Publicly available (thanks 350banshee)

[https://www.dynomotion.com/wiki/index.php?action=ajax&title=-&rs=SecureFileStore::getFile&f=/b/bb/RotarySwitchToKanalog.png Rotary Switch Connected to Kanalog Opto Inputs]

===3D Board Models===
[[Media:kflop-kstep-3d-models-1.snapshot.3.zip.txt|kflop-kstep-3d-models-1.snapshot.3.zip.txt]] STEP file format - Thanks to Curtis

[[File:kflop_kstep_render.JPG|none|link=|329x329px]]

[[Media:KFLOP3D_Step_IGS_Chris.zip.txt|KFLOP3D_Step_IGS_Chris.zip.txt]] STEP and IGS models - Thanks to Chris

[[File:KFLOP_3D.png|none|link=|413x296px]]

[[Media:KONNECT_BOARD_MODEL.zip.txt|KONNECT_BOARD_MODEL.zip.txt]] STEP model - Thanks to Jeff Redington

(Component locations may be off one way or another by .5mm)

[[File:Konnect_Board.png|none|link=|339x292px]]

Konnect Basic Step file showing hole locations

[[Media:KonnectHoles.stp.txt|KonnectHoles.stp.txt]]

[[File:KonnectHoles.png|none|link=|352x323px]]

Kanalog Step Model with Mechanical hole and Pin locations

[[Media:Kanalog.stp.txt|Kanalog.stp.txt]]

[[File:KanalogFromStep.png|none|link=|304x279px]]

Kanalog Step Model with Mechanical hole and Connectors (Thanks to

Roberto Gotti of Powertech)''' '''

[[Media:KANALOG_BOARD.stp.txt|KANALOG_BOARD.stp.txt]]

[[File:KanalogWithConnectors.png|none|link=|311x286px]]

===Board Terminal DXF/DWG files===
[[Media:KFLOP_Terminals.dxf|KFLOP_Terminals.dxf]] [[Media:KFLOP_Terminals.dwg|KFLOP_Terminals.dwg]]

[[Media:Kanalog_Terminals.dxf|Kanalog_Terminals.dxf]] [[Media:Kanalog_Terminals.dwg|Kanalog_Terminals.dwg]]

[[Media:Konnect_Terminals.dxf|Konnect_Terminals.dxf]] [[Media:Konnect_Terminals.dwg|Konnect_Terminals.dwg]]

[[Media:KStep_Terminals.dxf|KStep_Terminals.dxf]] [[Media:KStep_Terminals.dwg|KStep_Terminals.dwg]]

===Wiring Topics===
Place links to pages on wiring inputs and

outputs specific to your experiences and projects. Be descriptive with page titles and links.

====KFLOP IDC Connectors and Cables====
Cables that connect between Dynomotion boards are normally included when purchasing the boards together. They are also very common and easy to make. Use '''16-conductor or 26-conductor ribbon cable''' (0.05 inch pitch 26 AWG preferrably or 28AWG) and IDC sockets. [[File:RibbonCable.png|none|link=]]
16 conductor ribbon cable 3M part number 3801/16 100 https://www.digikey.com/product-detail/en/3m/3801-16-100/3M156105-100-ND/1107501 26 conductor ribbon cable 3M part number C3801/26 100 https://www.digikey.com/product-detail/en/3m/C3801-26-100/C3801-26-100-ND/1107648 Winford also sells ribbon cable (although only the thinner 28 AWG): http://www.winford.com/products/rib.php Note you can usually tear off wires to reduce the number of conductors. For example from 26 down to 16. Tear off the conductors away from the red stripe that marks pin 1. The '''crimp tools''' are common: https://www.amazon.com/Accessories-Crimp-Ribbon-Cable-Connectors/dp/B007R2JEM4/ [[File:RibbonCrimp.png|none|link=]] '''IDC Sockets 16-pin '''(pin pitch 0.1 inch) https://www.digikey.com/product-detail/en/assmann-wsw-components/AWP-16-7240-T/HHKC16H-ND/5031953 Assman Part number AWP 16-7240-T
[[File:16pinIDC.png|none|link=]]
https://www.digikey.com/product-detail/en/assmann-wsw-components/AWP-26-7240-T/HHKC26H-ND/5011313
[[File:26pinIDC.png|none|link=]]

====KFLOP KStep JR1 Molex Power Connectors====
KFLOP and KStep JR1 are standard Disk Drive Power Connectors. Possibly one of the most common connectors. Originally used on PC ATX Power Supplies. Sometimes referred to as Molex Connectors. They have 4 pins with 0.2 inch pitch with 0.083~0.084 inch socket pins. The mating cable will have female socket pins as shown here:

[[File:Molex_female_connector.jpg|none|link=|251x168px]]

Molex Series 8981 P# [https://www.digikey.com/short/zjp329 0015244048] using Molex Series 8980 Crimp Pins P# [https://www.digikey.com/short/zjp3ff 0002081201]

Also AMP Series MATE-N-LOK P# [https://www.digikey.com/short/zjpq3n 1-480424-0] using AMP Series MATE-N-LOK Crimp Pins P# [https://www.digikey.com/short/zjpqqw 60619-1] or P# [https://www.digikey.com/en/products/detail/molex/0194200002/2404783 194200002]

Molex Crimp Tool P# [https://www.digikey.com/en/products/detail/molex/0640160035/665311 0640160035]

====MPG Wiring and Interface====
MPGs (Manual Pulse Generators) should be connected directly to KFLOP for guaranteed real-time response (not USB based or connected to the PC). MPGs are handled by a C Program that monitors the MPG and creates motion based on the MPG Encoder changes and switch selections for axis, speed, and so forth. See the MPG C Program Examples. Here is a Discussion with other links.

[https://www.dynomotion.com/forum/archive/Jogging%20Pendant.html Jogging Pendant]

[https://www.dynomotion.com/forum/archive/Connecting%20Keling%20MPG2%20pendant.html Connecting Keling MPG2 Pendant]

[https://www.cnczone.com/forums/dynomotion-kflop-kanalog/349740-applying-acceleration-mpg-target-possible.html#post2119732 CNCZone Thread] on obtaining smooth filtered motion.

[[File:MPG4_from_cnc4pc.jpg|none|link=|83x169px]]

====Interfacing NPN Devices to KFLOP IO====
NPN devices (open collector)operate as a switch to GND and can be interfaced to KFLOP using a pull up resistor as shown below. When the transistor switches to 0V the KFLOP IO Pin is driven low. The transistor will need to sink ~3ma. When the transistor is off (open circuit) the resistor pulls the IO Pin to 3.3V. Note even though some KFLOP IO Pins can tolerate 5V pulling them above 3.8V should be avoided when possible so the 3.3V supply is used. This technique will only work with KFLOP IO Pins that do not have pull down resistors (JP7 and JP5). In some cases a 0.1uF Ceramic capacitor connected close to KFLOP might be added in parallel with the resistor to filter noise. Cable shielding connected to KFLOP GND on the KFLOP end only is recommended. Note that in noisy environments this technique may couple noise into KFLOP so opto isolation should be used instead.

[[File:NPN_Interface_to_KFLOP.png|none|link=|544x544px]]

====Multiplexing Encoder Inputs to KFLOP JP4 and JP6====
If KFLOP JP7 and JP5 are used for other purposes the encoder inputs can be multiplexed to KFLOP JP4 and JP6. There is an option to multiplex encoders 0-3 from JP7 to JP4 and another option to multiplex encoders 4-7 from JP5 to JP6. See the MuxEncoders.c for an example.

Note the JP4 and JP6 IO are 3.3V inputs and shouldn't be driven hard (more than 10ma) above 3.8V. This is not usually an issue as most encoders or RS422 drivers don't do this. The inputs also have 150 ohm termination.

The following line of code might be added to your Initialization C Program. It needs to be executed once to multiplex the encoders after any power cycle. Encoders 0-3 will then be input on JP4 and 4-7 will be on JP6. Both JP4 and Jp6 have 10 IO bits. The 4 encoders will appear on the first 8 IO bits. 2 bits for each encoder's A B channels in order. So for example Encoder #0 will appear on JP4 IO16 (Pin5) and IO17 (Pin6)

<pre class="brush:c">
// Mux encoder inputs from KFLOP JP7 & JP5 to JP4 and JP6
FPGAW(ENC_NOISE_FILTER_ADD) = ENC_0_3_JP4 + ENC_4_7_JP6 + ENC_NOISE_FILTER_DEFAULT_VAL; </pre>

JP4 and JP6 have +5V available on Pin1 and GND on Pins 8 and 9 that might be used to power 5V encoders.

==Axes Servo Tuning and Trajectory Planner==
===Basic Servo Tuning Overview===
Once an axis is configured and proved capable of holding a position it is ready to be tuned and optimized. Most often a small value of P Gain only is used to show the servo is functional and can hold position. The Servo may be very weak and inaccurate but will be functional.

Every system is different and the tuning parameters are interactive in a manner that usually doesn't allow parameters to be determined one at a time. Rather after one parameter is changed it may be necessary to revisit the other parameters.

In general higher gains will reduce errors and improve accuracy, but tend to make the system more unstable. So the general idea is to increase gains to reduce errors as much as possible but still have a stable system.

Often during tuning the system may go unstable. In fact, it is normally intentionally driven to instability to find its limits for a certain parameter. This can result in a violent oscillation or worse so one should be prepared to quickly disable the Servo. If an appropriate [http://dynomotion.com/Help/ConfigurationScreen/ConfigurationScreen.htm#Max_Following_Error Max Following Error] is used the axis can be automatically disabled before the oscillation becomes too violent, yet not disable when performing a normal test.

KMotion.exe allows you to change any axis parameter on the Step/Response, Config, or Filters Screens then simply push "Move" to see the effect of the change. Note that as performance improves the errors will become small and difficult to see on the Position Plot without Zooming in (Left click drag) so changing the plot type to plot the error is useful.

The overall process normally goes something like this:

# Select a Test [http://dynomotion.com/Help/StepScreen/StepScreen.htm#Measurement Move Size] and [http://dynomotion.com/Help/StepScreen/StepScreen.htm#Motion_Profile Motion Profile]. [http://www.dynomotion.com/wiki/index.php?title=Main_Page#Velocity.2C_Acceleration.2C_and_Jerk See Also]
# Select [http://dynomotion.com/Help/StepScreen/StepScreen.htm#max_limits Max Limits] to allow for the Test. [http://www.dynomotion.com/wiki/index.php?title=Main_Page#Max_Limits_-_Error See Also]
# Determine maximum level of [http://dynomotion.com/Help/StepScreen/StepScreen.htm#PID P Gain]
# Determine maximum level of [http://dynomotion.com/Help/StepScreen/StepScreen.htm#PID D Gain] (with Low Pass Filtering) See Also [http://www.dynomotion.com/wiki/index.php?title=Main_Page#Torque_Servos_vs_Velocity_Servos here] and [http://www.dynomotion.com/wiki/index.php?title=Main_Page#Lead_Compensator_vs_Derivative_Gain here].
# Determine new maximum level of P Gain now that D Gain increased stability
# Add I Gain to improve accuracy and remove steady state errors. [http://www.dynomotion.com/wiki/index.php?title=Main_Page#I_Gain.2FMax_Limit_Integrator See Also]
# Add [http://dynomotion.com/Help/StepScreen/StepScreen.htm#Feed_Forward Feed Forward] to reduce errors

===Torque Servos vs Velocity Servos===
+/-10V Analog Amplifiers usually come in one of two varieties: '''Torque''' or '''Velocity'''. Torque mode amplifiers consider the input command as a Torque Command and work to generate the commanded Motor Torque. Velocity mode amplifiers consider the input command as a Velocity Command and work to generate the commanded Velocity. Its important to understand what type of Amplifiers you have.

'''Velocity Mode Amplifiers''' need some form of feedback going to the Amplifier in order for the drive to know the current velocity. This might be a digital encoder or an analog tachometer.

Its easy to tell if you have a Velocity Mode Amplifier by looking at a plot of a move on the Step Response Screen. The Output (green plot with right scale) will be proportion to the motor velocity. When moving at constant speed the output will be relatively constant. See in the plot below the output (green) remains at a relatively constant ~1100 DAC counts while the position (red) ramps at a constant slope of the 90000 count/sec rate:

[[File:VelocityAmp.png|none|link=]]

Velocity mode amplifiers can be relatively easy to tune using only P (Proportional) Gain. Additional Gains and filters can be used for best performance but using only P Gain will often result in reasonable performance and a stable system (unlike Torque Mode Amplifiers).

As an example consider controlling the speed of a car using only Proportional Gain as it approaches a target (Stop sign). Consider a P Gain of 0.1 where at 1000ft from the stop sign we command 1000 x 0.1 = 100MPH. Then at 100ft we command 10MPH. Then at 10ft we command 1MPH. This results in a nice, smooth, exponential approach, without overshoot.

Contrast this with controlling the acceleration (torque) of a car using only Proportional Gain as it approaches a target (Stop sign). At large distance we apply maximum acceleration. Although as we approach the stop sign we reduce acceleration, we continue to accelerate and speed continues to increase until we pass the stop sign. Torque mode servos are inherently unstable. P only gain only works at all if there is some friction (the car is dragging a sled which slows us down with less torque).

'''Acceleration Mode Servos''' may or may not have any feedback. If they have feedback it is usually used only to commutate a brushless motor. In the plots the Output (green) will have large magnitude when the Position (red) is accelerating, where the plot has curvature (changing slope).

Acceleration mode Servos are unlikely to work well or at all with only P Gain. Some form of damping or lead compensation will usually be required to get a stable system. D (derivative) Gain (or a lead compensator) should be included with the P Gain to help stabilize the system. D Gain can be increased to make the system more stable up to a point. After some point the additional D Gain will make the system more unstable. and should be reduced.

When using D Gain (or lead compensation) the quantization noise (steps) in the encoder position can cause spikes in the output. For example a D Gain of 100 will cause a spike of 100 counts in the output whenever the input changes suddenly by 1 count. If the spikes are very high amplitude and short duration, the Amplifier may not handle them in the expected manner. A low pass filter can be used to widen and reduce their amplitude allowing the amplifier to handle them more effectively. Typically a 2nd order low pass filter of 500Hz Q=1.4 is used. The last filter is normally used so it is applied to any Feed Forward. Such as:

[[File:LowPass400Q1p4.png|none|link=|680x439px]]

===Velocity, Acceleration, and Jerk===
<div id="yui_3_16_0_1_1445622719616_3315" class="yiv2818182665class" style="color: #000000; font-size: 13.3333px; font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif; background-color: transparent; font-style: normal;">The Velocity, Acceleration, and Jerk in the Step Response Screen (KFLOP parameter settings) and the Acceleration and Velocity in the KMotionCNC | Tool Setup | Trajectory Planner | Axis Parameters are both used for different things. The two sets of parameters are independent. </div>
<div id="yui_3_16_0_1_1445622719616_3313" class="yiv2818182665class" style="color: #000000; font-size: 13.3333px; font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif; background-color: transparent; font-style: normal;"> </div>
<div class="yiv2818182665class" style="color: #000000; font-size: 13.3333px; font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif; background-color: transparent; font-style: normal;">The KFLOP parameters are used for 3rd order motions. These include things like: Jogging, Homing, and GCode Rapids (G0). The units in KFLOP are in counts or steps. The KMotionCNC parameters are used for 2nd order (infinite Jerk) coordinated motion paths. These are GCode G1,G2,G3 continuous paths. The units are in Inches (or in some cases degrees). Note there is an Option in KMotionCNC "Rapids as Feeds" where these parameters will also be used for Rapids. But this option should only be used for highly non-linear Kinematic Systems which can not take advantage of faster/smoother 3rd order point to point straight line Rapids. </div>
<div class="yiv2818182665class" style="color: #000000; font-size: 13.3333px; font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif; background-color: transparent; font-style: normal;"></div>
<div class="yiv2818182665class" style="color: #000000; font-size: 13.3333px; font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif; background-color: transparent; font-style: normal;">Tests to find and verify optimal settings for both types of moves should be made using the Step Response Screen. Optimal settings are usually determined by experimentation. Although it might be possible to calculate the settings based on motor torque gains, back-emf, amplifier voltage/current, mass, moments of inertia, friction, encoder resolution, leadscrew pitch, required following accuracy, etc... It is often too complicated and with too many unknowns to be practical. So experimental moves can be tested at ever increasing Velocities, Accelerations, and Jerks until the system is unable to follow the trajectory without having too much error or shock to the system. After absolute limits of the system are determined then the settings should be backed off by some amount to provide operating margins (ie 20%). </div>
<div class="yiv2818182665class" style="color: #000000; font-size: 13.3333px; font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif; background-color: transparent; font-style: normal;">It is usually best to first determine max possible velocity using a relatively low acceleration. Maximum power is usually required at the point of the trajectory where velocity is high and still accelerating. Supply Voltage limitations tend to limit velocity. Current limitations tend to limit acceleration. </div>
<div class="yiv2818182665class" style="color: #000000; font-size: 13.3333px; font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif; background-color: transparent; font-style: normal;"></div>
<div class="yiv2818182665class" style="color: #000000; font-size: 13.3333px; font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif; background-color: transparent; font-style: normal;">[[File:MaxVelAccelPower.png|none|link=|485x361px]] The Step Response Screen always performs 3rd order motion but 2nd order motion can be simulated by temporarily setting the Jerk to a huge value (1000X the acceleration value). In general reducing the Jerk value will result in longer times to perform motions, but often the improved smoothness will permit higher maximum accelerations and velocities to be used resulting in overall shorter motion times. An analogy might be how you might stop more quickly in a car, without skidding or spilling your coffee, by applying the brakes harder in a more gradual manner rather than slamming on the brakes. Make sure when testing the size of move is long enough for full acceleration and velocity are achieved. A common mistake is to have Acceleration or Velocity Settings set to too high for your system but when testing a short move there is no indication of a problem. The plot mode of Velocity Output vs Time can be helpful to verify full Velocity is being achieved. </div>
<div class="yiv2818182665class" style="color: #000000; font-size: 13.3333px; font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif; background-color: transparent; font-style: normal;"></div>
<div class="yiv2818182665class" style="color: #000000; font-size: 13.3333px; font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif; background-color: transparent; font-style: normal;">The idea is that a motor axis has torque and speed limitations and you should determine and understand what they both are for your system. Available motor torque drops off with higher speed. At some speed the motor will not even be able to generate any torque at all. Motor torque is required to accelerate the axis. We need to make sure that no combination of velocity and acceleration will ever cause the axis to fault/stall/fail. So there is often a complex set of speeds and accelerations that will work ok that form an envelope of workable speed and acceleration. So one nice thing to know is top speed possible. It is like taking your car out on a long straight highway and gradually accelerating to find the max speed is 100MPH. You will then know that ever attempting a speed over 100MPH will always fail. Also speed should probably be limited to something like 80MPH to allow for margin and to allow reasonable acceleration up to that speed. The reason for performing the top speed test at low acceleration is to avoid a failure because of not being able to accelerate at the specified rate. So we want to set the acceleration to a low value so it will not be a limiting factor when determining top speed. However if we set the acceleration so low with a short trip distance we will never go very fast and the speed test will be meaningless. This should be avoided. Change the Plot type to Velocity, Output, vs Time to clearly see if this is the case. You may want to turn off Measured Velocity if it obscures viewing the Commanded Velocity For example to accelerate to 700,000 counts/sec at an acceleration rate of 700,000 counts/sec^2 would take 1 second. And then to slow back down would take 1 more second. So at least 2 seconds of motion would be required to get to full speed. A 100,000 count move (2 inches for a system with 50,000 counts/inch) takes much less time than that. Furthermore with a relatively low Jerk setting (1e6). This means the acceleration will be applied gradually over 0.7 seconds. This means an even much longer time and distance would be required to achieve top speed. Here is the method to follow to find 2nd/3rd order motion profile limits: (note every system is different and will vary based on resolution, motor size/type, mass, etc...)

'''1 - Find Max Velocity at low Acceleration and infinite Jerk'''

Choose a Velocity to test (ie V=100000 counts/sec) Set a moderately low Acceleration Time of 1 second (A = V/1sec = 100000 counts/sec^2) Set very high Jerk so Acceleration is applied almost instantaneously in 0.001 sec (J = A/0.001sec = 1e8 counst/sec^3) Test a very long move 20 inches if possible (for resolution 50000 counts/inch, 1,000,000 counts) Plot Velocity, Output, vs time to see if V is actually obtained If the motion was successful repeat all above with higher V, if not try lower V Once Max V is found reduce by some margin (ie 20-50%) Note you may decide on lower speed for other reasons (safety, vibration, noise, wobble, shock, etc....) '''2 - Find Max Acceleration for your system for the chosen Velocity'''

Using the V found above increase A (keeping Jerk high in the same manner) until the system fails/faults/excessive shock, etc... Once Max A is found reduce by some margin (ie 20-50%) These V and A Values are now known good values for your system and can be used for 2nd order motions such as KMotionCNC Trajectory Planner or Mach3 Motor tuning. Note units will need to be converted (counts to inches or mm, time from seconds to minutes depending on the App)

'''3 - Find optimal 3rd order Jerk limited motions.'''

The previous result from Step #1 and #2 used nearly infinite Jerk where Acceleration forces were applied nearly instantaneously. By reducing Jerk smoother motion should be possible. Set Jerk so it is applied over 20ms (ie for A=200000 J = A/0.020 = 1e7 Test to see if motions are smoother. With closed loop systems the Position Error Plot can be used to see if the motion has less error and is smoother. Open loop system will require you to hear the difference. Increase/decrease Jerk to find the optimal value. Note reducing Jerk a lot will of course make the system very smooth, but will also be much slower using less acceleration and velocity which is undesirable. So the highest Jerk possible should be found that still provides some smoothness. Reducing Jerk only will always make the system slower with less performance (but hopefully significantly smoother). It is usually then possible to increase Acceleration and Velocity somewhat to achieve even higher performance than what was possible with infinite Jerk while being as smooth or smoother.

'''4 - Reduce Max Following Error Limit to small value'''

</div>
<div class="yiv2818182665class" style="color: #000000; font-size: 13.3333px; font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif; background-color: transparent; font-style: normal;">Now that the system is properly tuned and reasonable Acceleration, Velocity, and Jerk are set the motor Position should always follow the commanded Destinations accurately with only small errors. By Plotting Position Errors under various conditions (Distances) you can get an idea of the worst case following errors under normal conditions. The Max Following Error Parameter should be set to a value slightly larger than the worst case following error (ie 20~50% larger). In this case if anything abnormal occurs: ie. The axis hits an obstacle, commanded at too high of a speed, servo goes unstable, hardware/electronics failure, a Following Error will be immediately detected and the axes disabled.</div>
<div class="yiv2818182665class" style="color: #000000; font-size: 13.3333px; font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif; background-color: transparent; font-style: normal;"></div>
===Axis Resolution - counts/inch (or counts/mm)===
<div class="yiv2818182665class" style="color: #000000; font-size: 13.3333px; font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif; background-color: transparent; font-style: normal;"></div>
<div class="yiv2818182665class" style="color: #000000; font-size: 13.3333px; font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif; background-color: transparent; font-style: normal;">Its important to understand the resolution of your Axis which is the number of fundamental raw motor/driver encoder counts or motor steps per standard unit of distance (inch or mm). Although tuning in KMotion.exe Step Response Screen and motions within KFLOP typically use units of raw counts or steps it is important to know how these translate to real-world distances, speeds, etc... Later, applications such as KMotionCNC or Mach3 will need this information to scale motions properly. </div>
<div class="yiv2818182665class" style="color: #000000; font-size: 13.3333px; font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif; background-color: transparent; font-style: normal;"></div>
<div class="yiv2818182665class" style="color: #000000; font-size: 13.3333px; font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif; background-color: transparent; font-style: normal;">There are usually a number of factors that combine together to determine the Axis Resolution. These might include:</div>
* counts or steps per motor revolution
* any gearing or belts and pulleys involved between motor and drive mechanisms
* lead screw pitch, rack and pinion tooth pitch, drive belt radius, etc.

For example consider a Stepper Drive with:

3200 steps per motor rev

2:1 gear reduction from motor to lead screw

0.2 inch lead screw pitch

Axis Resolution = 3200 step/motor rev x (2 motor rev/ screw rev) / (0.2 inch / screw rev) = 32000 steps/inch

To determine whether your assumptions and calculations are correct perform a test. Command as large of a move as convenient and measure the actual distance moved with a ruler. For example in the axis described above you might command a move of 320000 steps. This should result in a motion of:

320000 steps / (32000 steps/inch) = 10 inches.

For KMotionCNC set the Axis Resolution in the [http://dynomotion.com/Help/KMotionCNC/ToolSetupScreenTP.htm#Axis_Motion_Parameters Tool Setup | Trajectory Planner Screen | Axis Parameters | cnts/inch]. Note units must be in units of inches. If your resolution is in mm units multiply by 25.4.

For Mach3 enter the Axis Resolution in the Configuration | Motor Tuning Screen. Make sure the setup units (not GCode units) match the mode of your values.

===Servo Dither/Hunting - (oscillation around zero error)===
<div class="yiv2818182665class" style="color: #000000; font-size: 13.3333px; font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif; background-color: transparent; font-style: normal;"></div>
<div class="yiv2818182665class" style="color: #000000; font-size: 13.3333px; font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif; background-color: transparent; font-style: normal;">Servos have high accuracy because they are always actively trying to make corrections and drive the error to zero. Unfortunately this can sometimes cause annoying dither or position hunting around zero when not moving. This is a very complex non-linear effect dependent on the dynamics of the mechanics. Because of the highly non-linear quantization effects of single "steps" in the encoder position, stiction, backlash, etc. it follows different rules and is harder to analyze than normal servo tuning/stability in the larger magnitude more linear regime. For example attempting to apply "Damping" is unlikely to work. Lowering gains will usually help at the expense of performance. However in many cases more than acceptable performance can be achieved with lower gains so one should consider if the higher gains are really needed. KFLOP has a Deadband Gain and Range feature that can basically be used to tell the servo to not attempt to correct small errors (treat the errors as zero), or to try to correct them less aggressively (with a Gain less than 1.0). See [http://dynomotion.com/Help/StepScreen/StepScreen.htm#Dead_Band here for more information] Unfortunately adding Deadband doesn't always help the servo "sit still" and may actually increase the size of the dither depending on the dynamics.
 Note that when the servo is commanded to a non integer position ie 999999.7 encoder counts without deadband the servo will always be making corrections. The best the servo can do is dither between encoder positions 999999.0 and 1000000.0. With an error of either -0.7 or +0.3. A servo with Integrator gain will guarantee the average is 999999.7 If dither is still a major problem a C Program might be used to monitor things and change settings under certain conditions to reduce dither. See the example AntiServoDither__ALL.c which monitors for small errors for a period of time and if so reduces or turns off Integrator gain. 

</div>
===Noisy GCode - Trajectory Planner Smoothing===
<div class="yiv2818182665class" style="color: #000000; font-size: 13.3333px; font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif; background-color: transparent; font-style: normal;">An analysis of Quantization Noise in GCode and Trajectory Planner Settings to generate smooth motion. [[File:GCode_Noisy_Path.png|none|link=|432x432px]]</div>
<div class="yiv2818182665class" style="color: #000000; font-size: 13.3333px; font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif; background-color: transparent; font-style: normal;">[[Trajectory Planner Smoothing Noisy GCode|See Analysis and Solution]]</div>
<div class="yiv2818182665class" style="color: #000000; font-size: 13.3333px; font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif; background-color: transparent; font-style: normal;"></div>
===Arc "faceting" - Trajectory Planner - Collinear Tolerance===
<div class="yiv2818182665class" style="color: #000000; font-size: 13.3333px; font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif; background-color: transparent; font-style: normal;"></div>
<div class="yiv2818182665class" style="color: #000000; font-size: 13.3333px; font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif; background-color: transparent; font-style: normal;">[[File:ArcsTrajectoryZoomXTol.0005.png|none|link=|526x460px]]</div>
<div class="yiv2818182665class" style="color: #000000; font-size: 13.3333px; font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif; background-color: transparent; font-style: normal;"></div>
<div class="yiv2818182665class" style="color: #000000; font-size: 13.3333px; font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif; background-color: transparent; font-style: normal;">[[ArcFacetingColinearTol|See Analysis and Solution]]</div>
<div class="yiv2818182665class" style="color: #000000; font-size: 13.3333px; font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif; background-color: transparent; font-style: normal;"></div>
===I Gain/Max Limit Integrator===
I (Integrator) Gain can be used to eliminate persistent errors. In fact any Integrator Gain at all guarantees the average error over infinite time is zero. Without I Gain a system might have a small error that does not create enough output to overcome stiction to make a correction. In such a case the error could persist forever. Not so with any Integrator Gain. Any error will be integrated and ramp the output higher and higher until eventually there will be a correction. That assumes the Integrator or Output doesn't saturate or reach their programmed limits. The rate the output ramps (or sums) is dependent on the size of the error and the I Gain value. The Error x I Gain is summed every servo sample (90us). This is why I Gain values are often small numbers (0.0001 - 0.01 typical range). There is no guarantee that the position doesn't over shoot the target Destination. In fact it is likely as as any error (area) under the trajectory will always be balanced by an equal area over the trajectory. Too high of I Gain will make the system unstable.

Another case where I Gain is useful is when moving at high speed with a Velocity Amplifier. To move at high speed a significant amount of output is required. Without I Gain a significant amount of error could be required to provide this Output (ie Error x P Gain = Output). With I Gain the Integrator will eventually ramp up to provide any Output necessary to move at the desired speed driving the error to zero.

Integrators have an issue often referred to as "Integrator Wind Up". This issue usually doesn't arise under normal conditions. However if something is preventing the servo from making a correction such as forcing the position away from the target for a sustained amount of time, or disabling the amplifier, the Integrator will integrate to a huge unlimited value. When the force is removed or amplifier re-enabled, the Integrator will likely cause a violent motion and overshoot. Max Limit Integrator can help to minimize this issue by limiting the amount the Integrator can ramp up to. So the Max Limit Integrator Value should be set at the minimum value that can still allow the Integrator to function in normal circumstances.

Typically there are two cases that should be considered when determining the Max Limit Integrator.

# The amount of output expected to be required to overcome any stiction, friction, or other forces (cutting, gravity, etc...). This is often not a large value and can be estimated or can be observed from the Step Response Screen (green plot right side scale is the output) when making a move.
# The amount of output required to provide the output needed to move at speed. It is important to note that D Gain provides a damping or drag effect on the Output. So the Integrator must be able to ramp up to a sufficient level to overcome the damping or drag effect and still provide enough output to move at the commanded speed. For example:

Assume:

# Commanded speed of 500,000 counts/sec
# D Gain of 35
# Output required to move at speed is 1800 DAC Counts
# Servo Sample Time of 90us

Damping effect = Speed x D Gain x Sample Time = 500000 x 35 x 90e-6 = 1575 counts

Required Integrator Value = 1800 + 1575 = 3375

So to provide some margin an Max Limit Integrator Value of 3500 might be used.

===Max Limits - Error===
Max limits error can be helpful to have your system respond less violently in the abnormal event where an excessively large error occurs. Normally with a properly tuned system following errors should be small. Setting a Max limits error can cause the servo to treat errors beyond a specified limit as if they were only the size of the limit and therefore respond less so than they would otherwise. The max limits error is normally set to a value so it is not limiting under normal circumstances.

The Plot below shows a situation where a small max limits error combined with a low P gain severely limits the Output. In the plot below a large move (10000 counts) at a high speed (40000 counts/sec) is commanded. Only P Gain (0.2) is used to provide the Output (green). The max error limit of 200 combined with the low gain (0.2) limits the output to only 40 DAC counts. Even as the true error increases to many thousands of counts, the servo is told to ignore the amount over 200. So the output can never exceed 40 DAC counts. The 40 DAC count limit means that the Axis is therefor not capable of providing the output necessary to keep up with the commanded motion. The axis does the best it can with the limited output, and only does a fraction of the desired motion.

[[File:Move10000.png|none|link=|665x431px]]

After increasing the max limits error the Output (green - right scale) now goes to a much higher value (900), and the Position (red) follows the Command (blue) to a much better degree.

[[File:Move10000_nolimit.png|none|link=|667x430px]]

Increasing the P Gain to 1.6 also applies more Output sooner and the Position follows the command still better.

[[File:Move1000_p1.6.png|none|link=|667x432px]]

===Lead Compensator vs Derivative Gain===
Derivative (D) Gain is often used to help stabilize a system.  It helps to think in the Frequency Domain to help understand how the two forms of compensation help.  Please read below and [http://dynomotion.com/Help/BodeScreen/BodeScreen.htm this] for more information on the Frequency Domain.  Both Compensation methods add positive phase to help stabilize the system.  Unfortunately both methods increase gain at higher frequencies possibly causing the system to go unstable at higher frequency.  A Lead Compensator provides the benefit of positive phase but without as much gain increase at higher frequencies.  This figure shows a simplified Gain Plot comparison:

[[File:DGainvsLead.png|none|link=|593x593px]]

Here is a Bode Plot of a P=0.5 D=20 Compensator. Note the KMotion.exe Bode Plot Screen has the capability of plotting the Frequency Domain Response of the PID+Filters Compensation. Assume we desire positive phase to be added at 40Hz. Notice the positive phase of 40 degrees at 40Hz which is good. However the Gain increase in the 1KHz region of about 21db which is bad.

[[File:P.5D20Annotate.png|none|link=|621x460px]]

Here is a Bode Plot of a P=0.5 N1=N2=25Hz D1=D2=70Hz Compensator. Assume we desire positive phase to be added at 40Hz. We choose N1 N2 and D1 D2 to surround the frequency where the positive phase is desired. Moving them further apart will increase the amount of positive phase but also increase the added Gain. Notice the positive phase of 60 degrees at 40Hz which is good. However the Gain increase in the 1KHz region of about 12db which is bad. However both are improvements over the D Gain compensator.

[[File:PoleZeroFilter.png|none|link=|210x319px]]

[[File:P.5D0N25D70Annotate.png|none|link=|644x478px]]

===Tuning Master/Slave Configurations===
Master/Slave [http://dynomotion.com/Help/ConfigurationScreen/ConfigurationScreen.htm#Master/Slave_Settings Configurations] allow two (or more) motors to drive the same axis. Slaves are configured to follow a Master Axis. For example two lead screws on both sides of a gantry.

Tuning slaved axes is kind of a catch 22. In order to tune one axis the other axis must be tuned well enough to follow and vice versa. If possible, disconnect any mechanical linkage between the Master and Slave and test them separately without Slaving the Axes together to verify each axis Servos (can hold a position), moves at least somewhat properly, and moves in the same direction (assuming a positive [http://dynomotion.com/Help/ConfigurationScreen/ConfigurationScreen.htm#Master/Slave_Settings Slave Gain] will be used).

It is usually possible to incrementally tune each axis, at first moving slowly, then later at higher speeds, accelerations, and gains. Only the Master Axis can be tested with the [http://dynomotion.com/Help/StepScreen/StepScreen.htm Step Response Screen]. This is because the Slave will follow any movement of the Master, but the Master will not follow movement of the Slave. So if the Master Axis is moved all is well as both axes will move together, but if you try to move the Slave axis the two axes will fight. The Master fighting to stay where it is, and the Slave fighting to move.

To test/tune the Slave axis temporarily reverse the Master/Slave roles to make it the Master and then test it as the Master.

Note: only the Master Axis should be included into the Coordinated Motion System.

===Bode Plots===
A Bode Plot is a powerful tool for characterizing and providing insight into a dynamic system. It can help determine closed loop stability, bandwidth/performance, resonant frequencies, and more. It is entirely based on the system being linear. Linear in the sense that if the amplitude of some input signal is changed then the output signal will change proportionally as well. Unfortunately most systems are not entirely linear. Stiction, backlash, encoder quantization, amplifier saturation, and other effects are non-linear. For example driving a system with a signal too small to overcome stiction will result in no output at all whereas a larger signal will result in some output. This is clearly non-linear behavior. It would be nice to use a technique that handles non-linear systems but basically none are known. A Bode Plot is made injecting a stimulus to the system and observing how the system responds. For the reasons of non-linearity it is very important to perform a Bode Plot measurement using a representative level of stimulus similar to what the system will actually have during normal operation. If the Stimulus is not adjusted properly the result is likely to be completely invalid. Additionally the system should be reasonably tuned and stable so that it is responding in a reasonable way to the stimulus. If the system is unstable or very poorly tuned the result is likely to be completely invalid. You might think of it somewhat like shaking a box to determine what is in it. You should shake it with enough intensity and at frequencies to get some reaction, but not so high of intensity to break or distort the object inside. To create a Bode Plot use the KMotion.exe Bode Plot Screen. First select Plot: Time domain - Command, Position, Output vs Time and adjust the Amplitude and cutoff Freq until there is small but significant Position (red) changes (ie 50 encoder counts), at a frequency low enough that the Position at least somewhat attempts to follow the Command (blue), and where the Output (green) is not near saturation for the Drive being used. After the Stimulus/Noise Injection settings are set switch to Plot: Open Loop - Magnitude and Phase vs Frequency. Set the number of Samples to average (ie 20) and perform a Measurement.  [http://dynomotion.com/Help/BodeScreen/BodeScreen.htm See here for more information].

===Links to other Information on Tuning and Bode Plots===
[http://ctms.engin.umich.edu/CTMS/index.php?example=Introduction&section=ControlFrequency umich.edu Introduction section Control Frequency]

[http://www.motiontech.com.au/assets/pdf/Kollmorgen%20Use%20Control%20Theory%20to%20Improve%20Servo%20Performance%20230712.pdf Kollmorgen Use Control Theory to Improve Servo Performance 230712.pdf]

==Problems and Resolutions==
====General====
:* [[Noise - Typical Problems and Resolutions|Dealing with noise on inputs]]. If you experience issues with inputs misreading, the issue may be noise. This page provides examples on what might be causing noise issues and examples of how to possibly deal with noise.
:* Other
===Software-Specific Problems and Resolutions===
:* Place links to pages explaining resolutions to problems that are largely software-related here
[[KFLOP User C Programs Compiling/Launching Slowly because of Windows Defender]]

===Hardware-Specific Problems and Resolutions===
:* Place links to pages explaining resolutions to problems that are largely hardware-related
====[[Step/Dir Drives lose 2 Steps for each pair of Direction Reversals]]====

==Applications and Projects==
:* Place links to pages that explain how you accomplished your particular project. Write clear explanations that provide background on what you did and how you did it.
====[[Tool Changer - router linear 4 Tools - C Program]]====
[[File:LINEAT+ATC.jpg|none|link=|246x178px]]
More linear milling tools: https://www.ichome.com/

====[[Part Zero & Tool Height Touch Plate|Part Zero & Tool Height Touch Plate]]====
====[[Driving Hobby Servos]]====
[[File:HobbyServo.png|left|link=]]

HiTec Type

==Electrical Discharge Machining==
[https://en.wikipedia.org/wiki/Electrical_discharge_machining EDM (wikipedia)] is a method of cutting materials with high precision and detail. Dynomotion Motion Controllers work well for EDM because of the ability for feedrate to be dynamically controlled including reversal along cutting path.

[[Information on BAXEDM Arc Generators used with KFLOP]]

Applied Science video that shows how to build an BAXEDM drilling machine using KFLOP and describes how it works:

{{#ev:youtube|https://youtu.be/rpHYBz7ToII|||||start=980}}

==How to convert a milling machine to a 3D printer in 3 easy steps==
[[File:CNCto3DPrinter.png|none|link=]]

More information [[How to convert a milling machine to a 3D printer in 3 easy steps|here]].

==International and other Languages==
[[Russian]]

[[Spanish]]

Main Page

2024-04-04T23:57:53Z

TK: /* Installation Topics */

=='''Dynomotion wiki'''''' '''==
Welcome to our wiki where you can find and share knowledge on Dynomotion's systems. To begin adding information to this wiki, simply create an account, verify your email, and start editing (click pencil icon). To make editing pages easier for everyone, we have installed a [https://help.bluespice.com/index.php/VisualEditor visual editor] by default. This visual editor allows you to edit a wiki page much like you would a standard word processing document.  For the seasoned wiki editors, standard [https://www.mediawiki.org/wiki/Help:Editing MediaWiki editing] may also be used.<nowiki> </nowiki>

''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 is safe to use. In no case will any contributor or Dynomotion be liable for incorrect information. Dynomotion reserves the right to modify or delete any contributions. ''

 Thanks for Contributing!

[http://dynomotion.com Official Dynomotion Site]

==Editing and Creating Wiki Pages==
Unintuitively, you first create a link to the page you want to make before you can make the page. To make a new page: while editing, right-click where you want your link to be, insert a link with a descriptive title and link text, save the page, click on the link you created, then click on "Empty Page" to begin editing your new page.

Here are a few other quick tips:

* You can insert links or images by Right-Clicking with the mouse on the line where you want the link or image to appear.
* For Spell Correction you can use Ctrl-Right-Click.
* To insert a YouTube Video use an EmbedVideo command such as <nowiki> {{#ev:youtube|xxxxx}}
</nowiki>with xxxxx changed to the Video ID.
* Choose a descriptive page name and link text when creating a new page: e.g. Not "My Machine", but rather "Brand X Three Axis Milling Machine Retrofit"
* Create pages in an organized manner: Describe what the page is about, create clear sections that flow

For more information:

[[Help:New Page Creation|How to create a new wiki page]]

[[Help:Editing Pages|How to Edit and insert Media into your wiki pages]]

==Dynomotion Software Topics==
===Installation Topics===
* Announcement of our Latest Release (5.3.3) on the [https://www.dynomotion.com/forum/viewtopic.php?f=4&t=1752 Dynomotion Forum]
* [https://dynomotion.com/Software/Download.html Latest Release] Note: For Windows 7 64bit signed Drivers to work, all Windows Updates should be performed.
* [[Upgrading from previous KMotion Versions]]

Archive of Test Releases:

* Previous Test Release: 02/01/2024: [https://dynomotion.com/Software/KMotion5.3.2.exe KMotion.exe 5.3.2], See the release notes for this test version here: [https://dynomotion.com/Software/KMotion%20Released%20Version%205.3.2%20Changes.pdf 5.3.2 release notes (pdf)]
* Previous Test Release: 11/20/2023: [https://dynomotion.com/Software/KMotion5.3.1.exe KMotion.exe 5.3.1], See the release notes for this test version here: [https://dynomotion.com/Software/KMotion%20Released%20Version%205.3.1%20Changes.pdf 5.3.1 release notes (pdf)]
* Previous Test Release: 09/19/2023: [https://dynomotion.com/Software/KMotion5.3.0.exe KMotion.exe 5.3.0], See the release notes for this test version here: [https://dynomotion.com/Software/KMotion%20Released%20Version%205.3.0%20Changes.pdf 5.3.0 release notes (pdf)]
* Previous Test Release: 06/30/2023: [https://dynomotion.com/Software/KMotion5.1.0.exe KMotion.exe 5.1.0], See the release notes for this test version here: [https://dynomotion.com/Software/KMotion%20Released%20Version%205.1.0%20Changes.pdf 5.1.0 release notes (pdf)]
* Previous Test Release: 05/01/2023: [https://dynomotion.com/Software/KMotion5.0.7.exe KMotion.exe 5.0.7], See the release notes for this test version here: [https://dynomotion.com/Software/KMotion%20Released%20Version%205.0.7%20Changes.pdf 5.0.7 release notes (pdf)]
* Previous Test Release: 09/21/2022: [https://dynomotion.com/Software/KMotion435h.exe KMotion.exe V4.35h], See the release notes for this test version here: [https://dynomotion.com/Software/KMotion%20Released%20Version%204.35h%20Changes.pdf V4.35h release notes (pdf)]
* Previous Version 4.35g was not released, but see the change notes for this version here: [https://dynomotion.com/Software/KMotion%20Released%20Version%204.35g%20Changes.pdf V4.35g change notes (pdf)]
* Previous Test Release: 12/28/2020: [https://dynomotion.com/Software/KMotion435f.exe KMotion.exe V4.35f], See the release notes for this test version here: [https://dynomotion.com/Software/KMotion%20Released%20Version%204.35f%20Changes.pdf V4.35f release notes (pdf)]
* Previous Test Release: 11/18/2019: [https://dynomotion.com/Software/KMotion435e.exe KMotion.exe V4.35e], See the release notes for this test version here: [https://dynomotion.com/Software/KMotion%20Released%20Version%204.35e%20Changes.pdf V4.35e release notes (pdf)]
* Previous Test Release: 09/10/2019: [https://dynomotion.com/Software/KMotion435d.exe KMotion.exe V4.35d], See the release notes for this test version here: [https://dynomotion.com/Software/KMotion%20Released%20Version%204.35d%20Changes.pdf V4.35d release notes (pdf)]
* Previous Test Release: 01/28/2019: [https://dynomotion.com/Software/KMotion435b.exe KMotion.exe V4.35b], See the release notes for this test version here: [https://dynomotion.com/Software/KMotion%20Released%20Version%204.35b%20Changes.pdf V4.35b release notes (pdf)]
* Previous Test Release: 12/21/2018: [https://dynomotion.com/Software/KMotion435a.exe KMotion.exe V4.35a], See the release notes for this test version here: [https://dynomotion.com/Software/KMotion%20Released%20Version%204.35a%20Changes.pdf V4.35a release notes (pdf)]
* Previous Test Release: 09/28/2017: [https://dynomotion.com/Software/KMotion434j.exe KMotion.exe V4.34j], See the release notes for this test version here: [https://dynomotion.com/Software/KMotion%20Released%20Version%204.34j%20Changes.pdf V4.34j release notes (pdf)]
* Previous Test Release: 05/07/2017: [https://dynomotion.com/Software/KMotion434i.exe KMotion.exe V4.34i], See the release notes for this test version here: [https://dynomotion.com/Software/KMotion%20Released%20Version%204.34i%20Changes.pdf V4.34i release notes (pdf)]
* Previous Test Release: 12/14/2016: [https://dynomotion.com/Software/KMotion434h.exe KMotion.exe V4.34h], See the release notes for this test version here: [https://dynomotion.com/Software/KMotion%20Released%20Version%204.34h%20Changes.pdf V4.34h release notes (pdf)]
* Previous Test Release: 12/13/2016: [https://dynomotion.com/Software/KMotion434g.exe KMotion.exe V4.34g], See the release notes for this test version here: [https://dynomotion.com/Software/KMotion%20Released%20Version%204.34g%20Changes.pdf V4.34g release notes (pdf)]
* Previous Test Release: 12/05/2016: [https://dynomotion.com/Software/KMotion434f.exe KMotion.exe V4.34f], See the release notes for this test version here: [https://dynomotion.com/Software/KMotion%20Released%20Version%204.34f%20Changes.pdf V4.34f release notes (pdf)]
* Previous Test Release: 11/07/2016: [https://dynomotion.com/Software/KMotion434e.exe KMotion.exe V4.34e], See the release notes for this test version here: [https://dynomotion.com/Software/KMotion%20Released%20Version%204.34e%20Changes.pdf V4.34e release notes (pdf)]
* Previous Test Release: 10/32/2016: [https://dynomotion.com/Software/KMotion434d.exe KMotion.exe V4.34d], See the release notes for this test version here: [https://dynomotion.com/Software/KMotion%20Released%20Version%204.34d%20Changes.pdf V4.34d release notes (pdf)]
* Previous Test Release: 10/23/2016: [https://dynomotion.com/Software/KMotion434c.exe KMotion.exe V4.34c], See the release notes for this test version here: [https://dynomotion.com/Software/KMotion%20Released%20Version%204.34c%20Changes.pdf V4.34c release notes (pdf)]
* Previous Test Release: 10/03/2016: [https://dynomotion.com/Software/KMotion434b.exe KMotion.exe V4.34b], See the release notes for this test version here: [https://dynomotion.com/Software/KMotion%20Released%20Version%204.34b%20Changes.pdf V4.34b release notes (pdf)]
* Previous Test Release: 03/09/2016: [https://dynomotion.com/Software/KMotion434a.exe KMotion.exe V4.34a], See the release notes for this test version here: [https://dynomotion.com/Software/KMotion%20Released%20Version%204.34a%20Changes.pdf V4.34a release notes (pdf)]
* [https://dynomotion.com/Help/KFLOPQuickStart/KFLOPQuickStart.htm How to install KMotion.exe and KMotionCNC]
* [[How to install KMotion.exe and KMotion in Windows 10|Preparing Windows 10 for driver installation]] (no longer required)
* [[Special Case for Windows 8.1 Industry Embedded Enterprise]]
* [[Updating KFLOP Firmware|How to update KFLOP Firmware]] - whenever a new version of software is installed, the firmware within KFLOP must be updated to match the new version

===KMotion.exe Executive Software Topics===
KMotion.exe is the main program that is used to configure settings in KFLOP, initialize axes, and to write C programs to configure and setup KFLOP to control your system. In this program you can plot step response, test movement, view Bode plots, monitor I/O, set filter parameters, and generally set the pertinent parameters.

* [http://www.dynomotion.com/Help/index.htm General software information] from the manuals
* Insert pages for other KMotion.exe-related topics here

===Configuration Topics===
====Channels, Channels, Channels what are they?====
[[Channels Channels Channels|Read Article Here]]

====How to Setup Backlash Compensation====
[[Backlash Compensation|Read Article Here]]

====PWM Output Mode====
[[PWM Output Mode|Read Article Here]]

===KMotionCNC Software Topics===
KMotionCNC is Dynomotion's CNC program used as a graphical user interface to your KFLOP-enabled machine tool. KMotionCNC has all of the basic functionality you need to run a machine of up to 6 axes, in addition to spindle control.

* Insert pages for other KMotionCNC-related general topics here

====Using KMotionCNC====
* Homing discussion - page to be created
* Insert other KMotionCNC use pages here

[[Internal/concave Path Tool Radius Compensation Example G41/G42]]

[[Known KMotionCNC CAD/CAM Post Processors]]

[[Invoking C Programs with Execute Only for previously Downloaded Programs]]

[[Rigid Tapping G84 Setup and Use]]

[[Tool Length/Offsets G43Hn G49]]

====Customize KMotionCNC====
KMotionCNC is written as a Windows C++ MFC (Microsoft Foundation Classes) program developed in Visual Studio. Source code is provided and may be customized using Visual Studio. MFC Support is a requirement.

: '''General Information'''
: Compiling KMotionCNC
:: The KMotionCNC's Visual Studio Project Solution (\PC VC Programs\KMotionCNC\KMotionCNC.sln) is currently written for Visual Studio 2015 Standard. This version can be used for the simplest compatibility. Projects can be upgraded to newer version of VS with minimal effort. Including Microsoft's Free Visual Studio 2013 Community. [[PC Example Applications|More info on PC Example Applications.]]
:: Note Test Versions 4.34a and later have project solutions targeted for Visual Studio 2015 Community which is free for most Users.
: '''KMotionCNC Customization Examples and Applications'''
:: Links to examples of projects that explain KMotionCNC customizations. Troy (tmday7) created some helpful documents (PDF format):
:
:* [https://www.dynomotion.com/forum/archive/attachments/How%20to%20Edit%20KMotionCNC%20Faces.pdf How to edit KMotionCNC faces]
:* [https://www.dynomotion.com/forum/archive/attachments/Adding%20External%20Buttons.pdf Adding external buttons]
:* [https://www.dynomotion.com/forum/archive/attachments/Adding%20More%20User%20Buttons.pdf Adding more user buttons]
:* [https://www.dynomotion.com/forum/archive/attachments/Adding%20Jog%20Percent%20Cell%20to%20Main%20Dialog%20Face.pdf Adding Jog Percent Cell to Main Dialog Face]

====KMotionCNC Screen Editor====
Introduces the capability of using Screen Script files to modify the look and function of KMotionCNC. [[KMotionCNC Screen Editor|More information.]]

====KMotionCNC Geometric Correction====
Information regarding the powerful [https://dynomotion.com/Help/KMotionCNC/GeoCorrection.htm Geometric Correction capability] which allows calibration and distortion correction of the XY CAD space to Machine/Actuator Space as well as flatness in Z. Simple 4 point correction tables can apply XY Scale, Rotation, skew, offset, tilt. Larger tables can apply more non-linear corrections.

Note the Geometric Correction is built into the KMotion Libraries and can be utilized by Custom Programs as well as with KMotionCNC [[Geometric Correction|More information and Examples.]]

===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. 

'''Note All the projects in KMotion Versions 4.34a and later have now been updated and should work out-of-the-box with VS2015.'''

[[PC Example Applications|More information.]]

===KMotion Libraries - GCode Interpreter - Trajectory Planner - Coordinated Motion - .NET===
The KMotion Libraries are a series of DLLs (Dynamic Link Libraries) that reside on the PC that contain the common core motion control, I/O, and communication functionality for KFLOP. These libraries permit PC Applications to be built using high level control without being concerned with the underlying details of Interpreting GCode, Trajectory Planning, Coordinated Motion, Motion Buffering, USB Communication, etc.

[[KMotion Libraries - GCode Interpreter - Trajectory Planner - Coordinated Motion - .NET|More information]].

===Kinematics===
The KMotion Libraries contain a Kinematics Layer where Users can add their own non-linear Kinematics

[[Kinematics|More information]].

===KFLOP C Programs===
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.

[[KFLOP C Programs|More Information]]

===ModBus===
Modbus can be connected to the PC or directly to KFLOP. A PC connection will not be deterministically real-time but may work for basic speed control and on/off. Here is a related Thread for interfacing KMotionCNC to Modbus using a [http://www.modbusdriver.com/modpoll.html free utility]:

[https://www.dynomotion.com/forum/archive/sending%20ModBus%20msgs%20from%20KmotionCNC%20to%20a%20RS485%20port.html Sending ModBus msgs from KmotionCNC to a RS485 port]

To connect Modbus directly to KFLOP's [http://www.dynomotion.com/Help/RS232/RS232.htm UART] see the C Examples in \C Programs\RS232\ModBus\

===Linux Support===
KMotion Motion Libraries are fully supported under Microsoft Windows. Some Users have ported the KMotion Libraries to Linux. Dynomotion will offer support where possible but can't offer full support under Linux. Special Thanks to [https://github.com/parhansson/KMotionX Par Hansson] for the initial Linux Port.

See [[Linux|here]] for more info.

==Dynomotion Hardware Topics==
===General Hardware Information===
====[[KFLOP Hardware Info|KFLOP specific Hardware Info]]====
====[[KStep Hardware Info|KStep specific Hardware Info]]====
====[[Kanalog Hardware Info|Kanalog specific Hardware Info]]====
====[[SnapAmp Info|SnapAmp specific Hardware Info]]====
====[[Konnect Hardware Info|Konnect specific Hardware Info]]====

===Wiring Diagrams===
[[Media:Kanalog_Connections.pdf|Basic Kanalog DAC and Encoder Connections 3 Axis]]

[[Media:KanalogSchematic3Axis.pdf|Basic Kanalog DAC and Encoder Connections 3 Axis #2]]

[[Media:dyn4 kanalog KE1524 V1.1.png|Basic Kanalog DAC and DMM DYN4 Drive 1 Axis]]

[[Media:Kflop-Kanalog_wiring_11-19-2018.pdf|Kanalog with Geckos G210 updated 11-19-2018]] (Thanks to Joseph Mirocha)

[[Media:Kanalog_to_Tree_Journeyman_325_by_Rick_B.pdf|Kanalog to Tree Journeyman 325.pdf]] (Thanks to Rick_B)

[[Media:KFlopSnapBrushMPG.pdf|KFLOP+SnapAmp DC Brush Motors with MPG]]

[[Media:Stepper_Wiring_Diagram_Step-Dir_on_JP5.pdf|KFLOP JP5 Open Collector Step/Dir Connections to Power Step PSD5042-2P Drives ]]

[[Media:Matrika_V1_wiring_diagram_Rev1.pdf|KFLOP+KStep with VFD and NPN Limit Switches for Matrika Rev1]]

[[Media:KonnectTouchPlate.png|Touch Plate Wiring to Konnect]]

[https://easyeda.com/350banshee/BreakoutBoard-93bdd16e3c3d48b98ae66c34f2436c40 User Created KFLOP JP7 Breakout/OptoIsolation Board] Schematic, Gerbers, PCBs Publicly available (thanks 350banshee)

[https://www.dynomotion.com/wiki/index.php?action=ajax&title=-&rs=SecureFileStore::getFile&f=/b/bb/RotarySwitchToKanalog.png Rotary Switch Connected to Kanalog Opto Inputs]

===3D Board Models===
[[Media:kflop-kstep-3d-models-1.snapshot.3.zip.txt|kflop-kstep-3d-models-1.snapshot.3.zip.txt]] STEP file format - Thanks to Curtis

[[File:kflop_kstep_render.JPG|none|link=|329x329px]]

[[Media:KFLOP3D_Step_IGS_Chris.zip.txt|KFLOP3D_Step_IGS_Chris.zip.txt]] STEP and IGS models - Thanks to Chris

[[File:KFLOP_3D.png|none|link=|413x296px]]

[[Media:KONNECT_BOARD_MODEL.zip.txt|KONNECT_BOARD_MODEL.zip.txt]] STEP model - Thanks to Jeff Redington

(Component locations may be off one way or another by .5mm)

[[File:Konnect_Board.png|none|link=|339x292px]]

Konnect Basic Step file showing hole locations

[[Media:KonnectHoles.stp.txt|KonnectHoles.stp.txt]]

[[File:KonnectHoles.png|none|link=|352x323px]]

Kanalog Step Model with Mechanical hole and Pin locations

[[Media:Kanalog.stp.txt|Kanalog.stp.txt]]

[[File:KanalogFromStep.png|none|link=|304x279px]]

Kanalog Step Model with Mechanical hole and Connectors (Thanks to

Roberto Gotti of Powertech)''' '''

[[Media:KANALOG_BOARD.stp.txt|KANALOG_BOARD.stp.txt]]

[[File:KanalogWithConnectors.png|none|link=|311x286px]]

===Board Terminal DXF/DWG files===
[[Media:KFLOP_Terminals.dxf|KFLOP_Terminals.dxf]] [[Media:KFLOP_Terminals.dwg|KFLOP_Terminals.dwg]]

[[Media:Kanalog_Terminals.dxf|Kanalog_Terminals.dxf]] [[Media:Kanalog_Terminals.dwg|Kanalog_Terminals.dwg]]

[[Media:Konnect_Terminals.dxf|Konnect_Terminals.dxf]] [[Media:Konnect_Terminals.dwg|Konnect_Terminals.dwg]]

[[Media:KStep_Terminals.dxf|KStep_Terminals.dxf]] [[Media:KStep_Terminals.dwg|KStep_Terminals.dwg]]

===Wiring Topics===
Place links to pages on wiring inputs and

outputs specific to your experiences and projects. Be descriptive with page titles and links.

====KFLOP IDC Connectors and Cables====
Cables that connect between Dynomotion boards are normally included when purchasing the boards together. They are also very common and easy to make. Use '''16-conductor or 26-conductor ribbon cable''' (0.05 inch pitch 26 AWG preferrably or 28AWG) and IDC sockets. [[File:RibbonCable.png|none|link=]]
16 conductor ribbon cable 3M part number 3801/16 100 https://www.digikey.com/product-detail/en/3m/3801-16-100/3M156105-100-ND/1107501 26 conductor ribbon cable 3M part number C3801/26 100 https://www.digikey.com/product-detail/en/3m/C3801-26-100/C3801-26-100-ND/1107648 Winford also sells ribbon cable (although only the thinner 28 AWG): http://www.winford.com/products/rib.php Note you can usually tear off wires to reduce the number of conductors. For example from 26 down to 16. Tear off the conductors away from the red stripe that marks pin 1. The '''crimp tools''' are common: https://www.amazon.com/Accessories-Crimp-Ribbon-Cable-Connectors/dp/B007R2JEM4/ [[File:RibbonCrimp.png|none|link=]] '''IDC Sockets 16-pin '''(pin pitch 0.1 inch) https://www.digikey.com/product-detail/en/assmann-wsw-components/AWP-16-7240-T/HHKC16H-ND/5031953 Assman Part number AWP 16-7240-T
[[File:16pinIDC.png|none|link=]]
https://www.digikey.com/product-detail/en/assmann-wsw-components/AWP-26-7240-T/HHKC26H-ND/5011313
[[File:26pinIDC.png|none|link=]]

====KFLOP KStep JR1 Molex Power Connectors====
KFLOP and KStep JR1 are standard Disk Drive Power Connectors. Possibly one of the most common connectors. Originally used on PC ATX Power Supplies. Sometimes referred to as Molex Connectors. They have 4 pins with 0.2 inch pitch with 0.083~0.084 inch socket pins. The mating cable will have female socket pins as shown here:

[[File:Molex_female_connector.jpg|none|link=|251x168px]]

Molex Series 8981 P# [https://www.digikey.com/short/zjp329 0015244048] using Molex Series 8980 Crimp Pins P# [https://www.digikey.com/short/zjp3ff 0002081201]

Also AMP Series MATE-N-LOK P# [https://www.digikey.com/short/zjpq3n 1-480424-0] using AMP Series MATE-N-LOK Crimp Pins P# [https://www.digikey.com/short/zjpqqw 60619-1]

====MPG Wiring and Interface====
MPGs (Manual Pulse Generators) should be connected directly to KFLOP for guaranteed real-time response (not USB based or connected to the PC). MPGs are handled by a C Program that monitors the MPG and creates motion based on the MPG Encoder changes and switch selections for axis, speed, and so forth. See the MPG C Program Examples. Here is a Discussion with other links.

[https://www.dynomotion.com/forum/archive/Jogging%20Pendant.html Jogging Pendant]

[https://www.dynomotion.com/forum/archive/Connecting%20Keling%20MPG2%20pendant.html Connecting Keling MPG2 Pendant]

[https://www.cnczone.com/forums/dynomotion-kflop-kanalog/349740-applying-acceleration-mpg-target-possible.html#post2119732 CNCZone Thread] on obtaining smooth filtered motion.

[[File:MPG4_from_cnc4pc.jpg|none|link=|83x169px]]

====Interfacing NPN Devices to KFLOP IO====
NPN devices (open collector)operate as a switch to GND and can be interfaced to KFLOP using a pull up resistor as shown below. When the transistor switches to 0V the KFLOP IO Pin is driven low. The transistor will need to sink ~3ma. When the transistor is off (open circuit) the resistor pulls the IO Pin to 3.3V. Note even though some KFLOP IO Pins can tolerate 5V pulling them above 3.8V should be avoided when possible so the 3.3V supply is used. This technique will only work with KFLOP IO Pins that do not have pull down resistors (JP7 and JP5). In some cases a 0.1uF Ceramic capacitor connected close to KFLOP might be added in parallel with the resistor to filter noise. Cable shielding connected to KFLOP GND on the KFLOP end only is recommended. Note that in noisy environments this technique may couple noise into KFLOP so opto isolation should be used instead.

[[File:NPN_Interface_to_KFLOP.png|none|link=|544x544px]]

====Multiplexing Encoder Inputs to KFLOP JP4 and JP6====
If KFLOP JP7 and JP5 are used for other purposes the encoder inputs can be multiplexed to KFLOP JP4 and JP6. There is an option to multiplex encoders 0-3 from JP7 to JP4 and another option to multiplex encoders 4-7 from JP5 to JP6. See the MuxEncoders.c for an example.

Note the JP4 and JP6 IO are 3.3V inputs and shouldn't be driven hard (more than 10ma) above 3.8V. This is not usually an issue as most encoders or RS422 drivers don't do this. The inputs also have 150 ohm termination.

The following line of code might be added to your Initialization C Program. It needs to be executed once to multiplex the encoders after any power cycle. Encoders 0-3 will then be input on JP4 and 4-7 will be on JP6. Both JP4 and Jp6 have 10 IO bits. The 4 encoders will appear on the first 8 IO bits. 2 bits for each encoder's A B channels in order. So for example Encoder #0 will appear on JP4 IO16 (Pin5) and IO17 (Pin6)

<pre class="brush:c">
// Mux encoder inputs from KFLOP JP7 & JP5 to JP4 and JP6
FPGAW(ENC_NOISE_FILTER_ADD) = ENC_0_3_JP4 + ENC_4_7_JP6 + ENC_NOISE_FILTER_DEFAULT_VAL; </pre>

JP4 and JP6 have +5V available on Pin1 and GND on Pins 8 and 9 that might be used to power 5V encoders.

==Axes Servo Tuning and Trajectory Planner==
===Basic Servo Tuning Overview===
Once an axis is configured and proved capable of holding a position it is ready to be tuned and optimized. Most often a small value of P Gain only is used to show the servo is functional and can hold position. The Servo may be very weak and inaccurate but will be functional.

Every system is different and the tuning parameters are interactive in a manner that usually doesn't allow parameters to be determined one at a time. Rather after one parameter is changed it may be necessary to revisit the other parameters.

In general higher gains will reduce errors and improve accuracy, but tend to make the system more unstable. So the general idea is to increase gains to reduce errors as much as possible but still have a stable system.

Often during tuning the system may go unstable. In fact, it is normally intentionally driven to instability to find its limits for a certain parameter. This can result in a violent oscillation or worse so one should be prepared to quickly disable the Servo. If an appropriate [http://dynomotion.com/Help/ConfigurationScreen/ConfigurationScreen.htm#Max_Following_Error Max Following Error] is used the axis can be automatically disabled before the oscillation becomes too violent, yet not disable when performing a normal test.

KMotion.exe allows you to change any axis parameter on the Step/Response, Config, or Filters Screens then simply push "Move" to see the effect of the change. Note that as performance improves the errors will become small and difficult to see on the Position Plot without Zooming in (Left click drag) so changing the plot type to plot the error is useful.

The overall process normally goes something like this:

# Select a Test [http://dynomotion.com/Help/StepScreen/StepScreen.htm#Measurement Move Size] and [http://dynomotion.com/Help/StepScreen/StepScreen.htm#Motion_Profile Motion Profile]. [http://www.dynomotion.com/wiki/index.php?title=Main_Page#Velocity.2C_Acceleration.2C_and_Jerk See Also]
# Select [http://dynomotion.com/Help/StepScreen/StepScreen.htm#max_limits Max Limits] to allow for the Test. [http://www.dynomotion.com/wiki/index.php?title=Main_Page#Max_Limits_-_Error See Also]
# Determine maximum level of [http://dynomotion.com/Help/StepScreen/StepScreen.htm#PID P Gain]
# Determine maximum level of [http://dynomotion.com/Help/StepScreen/StepScreen.htm#PID D Gain] (with Low Pass Filtering) See Also [http://www.dynomotion.com/wiki/index.php?title=Main_Page#Torque_Servos_vs_Velocity_Servos here] and [http://www.dynomotion.com/wiki/index.php?title=Main_Page#Lead_Compensator_vs_Derivative_Gain here].
# Determine new maximum level of P Gain now that D Gain increased stability
# Add I Gain to improve accuracy and remove steady state errors. [http://www.dynomotion.com/wiki/index.php?title=Main_Page#I_Gain.2FMax_Limit_Integrator See Also]
# Add [http://dynomotion.com/Help/StepScreen/StepScreen.htm#Feed_Forward Feed Forward] to reduce errors

===Torque Servos vs Velocity Servos===
+/-10V Analog Amplifiers usually come in one of two varieties: '''Torque''' or '''Velocity'''. Torque mode amplifiers consider the input command as a Torque Command and work to generate the commanded Motor Torque. Velocity mode amplifiers consider the input command as a Velocity Command and work to generate the commanded Velocity. Its important to understand what type of Amplifiers you have.

'''Velocity Mode Amplifiers''' need some form of feedback going to the Amplifier in order for the drive to know the current velocity. This might be a digital encoder or an analog tachometer.

Its easy to tell if you have a Velocity Mode Amplifier by looking at a plot of a move on the Step Response Screen. The Output (green plot with right scale) will be proportion to the motor velocity. When moving at constant speed the output will be relatively constant. See in the plot below the output (green) remains at a relatively constant ~1100 DAC counts while the position (red) ramps at a constant slope of the 90000 count/sec rate:

[[File:VelocityAmp.png|none|link=]]

Velocity mode amplifiers can be relatively easy to tune using only P (Proportional) Gain. Additional Gains and filters can be used for best performance but using only P Gain will often result in reasonable performance and a stable system (unlike Torque Mode Amplifiers).

As an example consider controlling the speed of a car using only Proportional Gain as it approaches a target (Stop sign). Consider a P Gain of 0.1 where at 1000ft from the stop sign we command 1000 x 0.1 = 100MPH. Then at 100ft we command 10MPH. Then at 10ft we command 1MPH. This results in a nice, smooth, exponential approach, without overshoot.

Contrast this with controlling the acceleration (torque) of a car using only Proportional Gain as it approaches a target (Stop sign). At large distance we apply maximum acceleration. Although as we approach the stop sign we reduce acceleration, we continue to accelerate and speed continues to increase until we pass the stop sign. Torque mode servos are inherently unstable. P only gain only works at all if there is some friction (the car is dragging a sled which slows us down with less torque).

'''Acceleration Mode Servos''' may or may not have any feedback. If they have feedback it is usually used only to commutate a brushless motor. In the plots the Output (green) will have large magnitude when the Position (red) is accelerating, where the plot has curvature (changing slope).

Acceleration mode Servos are unlikely to work well or at all with only P Gain. Some form of damping or lead compensation will usually be required to get a stable system. D (derivative) Gain (or a lead compensator) should be included with the P Gain to help stabilize the system. D Gain can be increased to make the system more stable up to a point. After some point the additional D Gain will make the system more unstable. and should be reduced.

When using D Gain (or lead compensation) the quantization noise (steps) in the encoder position can cause spikes in the output. For example a D Gain of 100 will cause a spike of 100 counts in the output whenever the input changes suddenly by 1 count. If the spikes are very high amplitude and short duration, the Amplifier may not handle them in the expected manner. A low pass filter can be used to widen and reduce their amplitude allowing the amplifier to handle them more effectively. Typically a 2nd order low pass filter of 500Hz Q=1.4 is used. The last filter is normally used so it is applied to any Feed Forward. Such as:

[[File:LowPass400Q1p4.png|none|link=|680x439px]]

===Velocity, Acceleration, and Jerk===
<div id="yui_3_16_0_1_1445622719616_3315" class="yiv2818182665class" style="color: #000000; font-size: 13.3333px; font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif; background-color: transparent; font-style: normal;">The Velocity, Acceleration, and Jerk in the Step Response Screen (KFLOP parameter settings) and the Acceleration and Velocity in the KMotionCNC | Tool Setup | Trajectory Planner | Axis Parameters are both used for different things. The two sets of parameters are independent. </div>
<div id="yui_3_16_0_1_1445622719616_3313" class="yiv2818182665class" style="color: #000000; font-size: 13.3333px; font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif; background-color: transparent; font-style: normal;"> </div>
<div class="yiv2818182665class" style="color: #000000; font-size: 13.3333px; font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif; background-color: transparent; font-style: normal;">The KFLOP parameters are used for 3rd order motions. These include things like: Jogging, Homing, and GCode Rapids (G0). The units in KFLOP are in counts or steps. The KMotionCNC parameters are used for 2nd order (infinite Jerk) coordinated motion paths. These are GCode G1,G2,G3 continuous paths. The units are in Inches (or in some cases degrees). Note there is an Option in KMotionCNC "Rapids as Feeds" where these parameters will also be used for Rapids. But this option should only be used for highly non-linear Kinematic Systems which can not take advantage of faster/smoother 3rd order point to point straight line Rapids. </div>
<div class="yiv2818182665class" style="color: #000000; font-size: 13.3333px; font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif; background-color: transparent; font-style: normal;"></div>
<div class="yiv2818182665class" style="color: #000000; font-size: 13.3333px; font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif; background-color: transparent; font-style: normal;">Tests to find and verify optimal settings for both types of moves should be made using the Step Response Screen. Optimal settings are usually determined by experimentation. Although it might be possible to calculate the settings based on motor torque gains, back-emf, amplifier voltage/current, mass, moments of inertia, friction, encoder resolution, leadscrew pitch, required following accuracy, etc... It is often too complicated and with too many unknowns to be practical. So experimental moves can be tested at ever increasing Velocities, Accelerations, and Jerks until the system is unable to follow the trajectory without having too much error or shock to the system. After absolute limits of the system are determined then the settings should be backed off by some amount to provide operating margins (ie 20%). </div>
<div class="yiv2818182665class" style="color: #000000; font-size: 13.3333px; font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif; background-color: transparent; font-style: normal;">It is usually best to first determine max possible velocity using a relatively low acceleration. Maximum power is usually required at the point of the trajectory where velocity is high and still accelerating. Supply Voltage limitations tend to limit velocity. Current limitations tend to limit acceleration. </div>
<div class="yiv2818182665class" style="color: #000000; font-size: 13.3333px; font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif; background-color: transparent; font-style: normal;"></div>
<div class="yiv2818182665class" style="color: #000000; font-size: 13.3333px; font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif; background-color: transparent; font-style: normal;">[[File:MaxVelAccelPower.png|none|link=|485x361px]] The Step Response Screen always performs 3rd order motion but 2nd order motion can be simulated by temporarily setting the Jerk to a huge value (1000X the acceleration value). In general reducing the Jerk value will result in longer times to perform motions, but often the improved smoothness will permit higher maximum accelerations and velocities to be used resulting in overall shorter motion times. An analogy might be how you might stop more quickly in a car, without skidding or spilling your coffee, by applying the brakes harder in a more gradual manner rather than slamming on the brakes. Make sure when testing the size of move is long enough for full acceleration and velocity are achieved. A common mistake is to have Acceleration or Velocity Settings set to too high for your system but when testing a short move there is no indication of a problem. The plot mode of Velocity Output vs Time can be helpful to verify full Velocity is being achieved. </div>
<div class="yiv2818182665class" style="color: #000000; font-size: 13.3333px; font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif; background-color: transparent; font-style: normal;"></div>
<div class="yiv2818182665class" style="color: #000000; font-size: 13.3333px; font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif; background-color: transparent; font-style: normal;">The idea is that a motor axis has torque and speed limitations and you should determine and understand what they both are for your system. Available motor torque drops off with higher speed. At some speed the motor will not even be able to generate any torque at all. Motor torque is required to accelerate the axis. We need to make sure that no combination of velocity and acceleration will ever cause the axis to fault/stall/fail. So there is often a complex set of speeds and accelerations that will work ok that form an envelope of workable speed and acceleration. So one nice thing to know is top speed possible. It is like taking your car out on a long straight highway and gradually accelerating to find the max speed is 100MPH. You will then know that ever attempting a speed over 100MPH will always fail. Also speed should probably be limited to something like 80MPH to allow for margin and to allow reasonable acceleration up to that speed. The reason for performing the top speed test at low acceleration is to avoid a failure because of not being able to accelerate at the specified rate. So we want to set the acceleration to a low value so it will not be a limiting factor when determining top speed. However if we set the acceleration so low with a short trip distance we will never go very fast and the speed test will be meaningless. This should be avoided. Change the Plot type to Velocity, Output, vs Time to clearly see if this is the case. You may want to turn off Measured Velocity if it obscures viewing the Commanded Velocity For example to accelerate to 700,000 counts/sec at an acceleration rate of 700,000 counts/sec^2 would take 1 second. And then to slow back down would take 1 more second. So at least 2 seconds of motion would be required to get to full speed. A 100,000 count move (2 inches for a system with 50,000 counts/inch) takes much less time than that. Furthermore with a relatively low Jerk setting (1e6). This means the acceleration will be applied gradually over 0.7 seconds. This means an even much longer time and distance would be required to achieve top speed. Here is the method to follow to find 2nd/3rd order motion profile limits: (note every system is different and will vary based on resolution, motor size/type, mass, etc...)

'''1 - Find Max Velocity at low Acceleration and infinite Jerk'''

Choose a Velocity to test (ie V=100000 counts/sec) Set a moderately low Acceleration Time of 1 second (A = V/1sec = 100000 counts/sec^2) Set very high Jerk so Acceleration is applied almost instantaneously in 0.001 sec (J = A/0.001sec = 1e8 counst/sec^3) Test a very long move 20 inches if possible (for resolution 50000 counts/inch, 1,000,000 counts) Plot Velocity, Output, vs time to see if V is actually obtained If the motion was successful repeat all above with higher V, if not try lower V Once Max V is found reduce by some margin (ie 20-50%) Note you may decide on lower speed for other reasons (safety, vibration, noise, wobble, shock, etc....) '''2 - Find Max Acceleration for your system for the chosen Velocity'''

Using the V found above increase A (keeping Jerk high in the same manner) until the system fails/faults/excessive shock, etc... Once Max A is found reduce by some margin (ie 20-50%) These V and A Values are now known good values for your system and can be used for 2nd order motions such as KMotionCNC Trajectory Planner or Mach3 Motor tuning. Note units will need to be converted (counts to inches or mm, time from seconds to minutes depending on the App)

'''3 - Find optimal 3rd order Jerk limited motions.'''

The previous result from Step #1 and #2 used nearly infinite Jerk where Acceleration forces were applied nearly instantaneously. By reducing Jerk smoother motion should be possible. Set Jerk so it is applied over 20ms (ie for A=200000 J = A/0.020 = 1e7 Test to see if motions are smoother. With closed loop systems the Position Error Plot can be used to see if the motion has less error and is smoother. Open loop system will require you to hear the difference. Increase/decrease Jerk to find the optimal value. Note reducing Jerk a lot will of course make the system very smooth, but will also be much slower using less acceleration and velocity which is undesirable. So the highest Jerk possible should be found that still provides some smoothness. Reducing Jerk only will always make the system slower with less performance (but hopefully significantly smoother). It is usually then possible to increase Acceleration and Velocity somewhat to achieve even higher performance than what was possible with infinite Jerk while being as smooth or smoother.

'''4 - Reduce Max Following Error Limit to small value'''

</div>
<div class="yiv2818182665class" style="color: #000000; font-size: 13.3333px; font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif; background-color: transparent; font-style: normal;">Now that the system is properly tuned and reasonable Acceleration, Velocity, and Jerk are set the motor Position should always follow the commanded Destinations accurately with only small errors. By Plotting Position Errors under various conditions (Distances) you can get an idea of the worst case following errors under normal conditions. The Max Following Error Parameter should be set to a value slightly larger than the worst case following error (ie 20~50% larger). In this case if anything abnormal occurs: ie. The axis hits an obstacle, commanded at too high of a speed, servo goes unstable, hardware/electronics failure, a Following Error will be immediately detected and the axes disabled.</div>
<div class="yiv2818182665class" style="color: #000000; font-size: 13.3333px; font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif; background-color: transparent; font-style: normal;"></div>
===Axis Resolution - counts/inch (or counts/mm)===
<div class="yiv2818182665class" style="color: #000000; font-size: 13.3333px; font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif; background-color: transparent; font-style: normal;"></div>
<div class="yiv2818182665class" style="color: #000000; font-size: 13.3333px; font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif; background-color: transparent; font-style: normal;">Its important to understand the resolution of your Axis which is the number of fundamental raw motor/driver encoder counts or motor steps per standard unit of distance (inch or mm). Although tuning in KMotion.exe Step Response Screen and motions within KFLOP typically use units of raw counts or steps it is important to know how these translate to real-world distances, speeds, etc... Later, applications such as KMotionCNC or Mach3 will need this information to scale motions properly. </div>
<div class="yiv2818182665class" style="color: #000000; font-size: 13.3333px; font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif; background-color: transparent; font-style: normal;"></div>
<div class="yiv2818182665class" style="color: #000000; font-size: 13.3333px; font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif; background-color: transparent; font-style: normal;">There are usually a number of factors that combine together to determine the Axis Resolution. These might include:</div>
* counts or steps per motor revolution
* any gearing or belts and pulleys involved between motor and drive mechanisms
* lead screw pitch, rack and pinion tooth pitch, drive belt radius, etc.

For example consider a Stepper Drive with:

3200 steps per motor rev

2:1 gear reduction from motor to lead screw

0.2 inch lead screw pitch

Axis Resolution = 3200 step/motor rev x (2 motor rev/ screw rev) / (0.2 inch / screw rev) = 32000 steps/inch

To determine whether your assumptions and calculations are correct perform a test. Command as large of a move as convenient and measure the actual distance moved with a ruler. For example in the axis described above you might command a move of 320000 steps. This should result in a motion of:

320000 steps / (32000 steps/inch) = 10 inches.

For KMotionCNC set the Axis Resolution in the [http://dynomotion.com/Help/KMotionCNC/ToolSetupScreenTP.htm#Axis_Motion_Parameters Tool Setup | Trajectory Planner Screen | Axis Parameters | cnts/inch]. Note units must be in units of inches. If your resolution is in mm units multiply by 25.4.

For Mach3 enter the Axis Resolution in the Configuration | Motor Tuning Screen. Make sure the setup units (not GCode units) match the mode of your values.

===Servo Dither/Hunting - (oscillation around zero error)===
<div class="yiv2818182665class" style="color: #000000; font-size: 13.3333px; font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif; background-color: transparent; font-style: normal;"></div>
<div class="yiv2818182665class" style="color: #000000; font-size: 13.3333px; font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif; background-color: transparent; font-style: normal;">Servos have high accuracy because they are always actively trying to make corrections and drive the error to zero. Unfortunately this can sometimes cause annoying dither or position hunting around zero when not moving. This is a very complex non-linear effect dependent on the dynamics of the mechanics. Because of the highly non-linear quantization effects of single "steps" in the encoder position, stiction, backlash, etc. it follows different rules and is harder to analyze than normal servo tuning/stability in the larger magnitude more linear regime. For example attempting to apply "Damping" is unlikely to work. Lowering gains will usually help at the expense of performance. However in many cases more than acceptable performance can be achieved with lower gains so one should consider if the higher gains are really needed. KFLOP has a Deadband Gain and Range feature that can basically be used to tell the servo to not attempt to correct small errors (treat the errors as zero), or to try to correct them less aggressively (with a Gain less than 1.0). See [http://dynomotion.com/Help/StepScreen/StepScreen.htm#Dead_Band here for more information] Unfortunately adding Deadband doesn't always help the servo "sit still" and may actually increase the size of the dither depending on the dynamics.
 Note that when the servo is commanded to a non integer position ie 999999.7 encoder counts without deadband the servo will always be making corrections. The best the servo can do is dither between encoder positions 999999.0 and 1000000.0. With an error of either -0.7 or +0.3. A servo with Integrator gain will guarantee the average is 999999.7 If dither is still a major problem a C Program might be used to monitor things and change settings under certain conditions to reduce dither. See the example AntiServoDither__ALL.c which monitors for small errors for a period of time and if so reduces or turns off Integrator gain. 

</div>
===Noisy GCode - Trajectory Planner Smoothing===
<div class="yiv2818182665class" style="color: #000000; font-size: 13.3333px; font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif; background-color: transparent; font-style: normal;">An analysis of Quantization Noise in GCode and Trajectory Planner Settings to generate smooth motion. [[File:GCode_Noisy_Path.png|none|link=|432x432px]]</div>
<div class="yiv2818182665class" style="color: #000000; font-size: 13.3333px; font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif; background-color: transparent; font-style: normal;">[[Trajectory Planner Smoothing Noisy GCode|See Analysis and Solution]]</div>
<div class="yiv2818182665class" style="color: #000000; font-size: 13.3333px; font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif; background-color: transparent; font-style: normal;"></div>
===Arc "faceting" - Trajectory Planner - Collinear Tolerance===
<div class="yiv2818182665class" style="color: #000000; font-size: 13.3333px; font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif; background-color: transparent; font-style: normal;"></div>
<div class="yiv2818182665class" style="color: #000000; font-size: 13.3333px; font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif; background-color: transparent; font-style: normal;">[[File:ArcsTrajectoryZoomXTol.0005.png|none|link=|526x460px]]</div>
<div class="yiv2818182665class" style="color: #000000; font-size: 13.3333px; font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif; background-color: transparent; font-style: normal;"></div>
<div class="yiv2818182665class" style="color: #000000; font-size: 13.3333px; font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif; background-color: transparent; font-style: normal;">[[ArcFacetingColinearTol|See Analysis and Solution]]</div>
<div class="yiv2818182665class" style="color: #000000; font-size: 13.3333px; font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif; background-color: transparent; font-style: normal;"></div>
===I Gain/Max Limit Integrator===
I (Integrator) Gain can be used to eliminate persistent errors. In fact any Integrator Gain at all guarantees the average error over infinite time is zero. Without I Gain a system might have a small error that does not create enough output to overcome stiction to make a correction. In such a case the error could persist forever. Not so with any Integrator Gain. Any error will be integrated and ramp the output higher and higher until eventually there will be a correction. That assumes the Integrator or Output doesn't saturate or reach their programmed limits. The rate the output ramps (or sums) is dependent on the size of the error and the I Gain value. The Error x I Gain is summed every servo sample (90us). This is why I Gain values are often small numbers (0.0001 - 0.01 typical range). There is no guarantee that the position doesn't over shoot the target Destination. In fact it is likely as as any error (area) under the trajectory will always be balanced by an equal area over the trajectory. Too high of I Gain will make the system unstable.

Another case where I Gain is useful is when moving at high speed with a Velocity Amplifier. To move at high speed a significant amount of output is required. Without I Gain a significant amount of error could be required to provide this Output (ie Error x P Gain = Output). With I Gain the Integrator will eventually ramp up to provide any Output necessary to move at the desired speed driving the error to zero.

Integrators have an issue often referred to as "Integrator Wind Up". This issue usually doesn't arise under normal conditions. However if something is preventing the servo from making a correction such as forcing the position away from the target for a sustained amount of time, or disabling the amplifier, the Integrator will integrate to a huge unlimited value. When the force is removed or amplifier re-enabled, the Integrator will likely cause a violent motion and overshoot. Max Limit Integrator can help to minimize this issue by limiting the amount the Integrator can ramp up to. So the Max Limit Integrator Value should be set at the minimum value that can still allow the Integrator to function in normal circumstances.

Typically there are two cases that should be considered when determining the Max Limit Integrator.

# The amount of output expected to be required to overcome any stiction, friction, or other forces (cutting, gravity, etc...). This is often not a large value and can be estimated or can be observed from the Step Response Screen (green plot right side scale is the output) when making a move.
# The amount of output required to provide the output needed to move at speed. It is important to note that D Gain provides a damping or drag effect on the Output. So the Integrator must be able to ramp up to a sufficient level to overcome the damping or drag effect and still provide enough output to move at the commanded speed. For example:

Assume:

# Commanded speed of 500,000 counts/sec
# D Gain of 35
# Output required to move at speed is 1800 DAC Counts
# Servo Sample Time of 90us

Damping effect = Speed x D Gain x Sample Time = 500000 x 35 x 90e-6 = 1575 counts

Required Integrator Value = 1800 + 1575 = 3375

So to provide some margin an Max Limit Integrator Value of 3500 might be used.

===Max Limits - Error===
Max limits error can be helpful to have your system respond less violently in the abnormal event where an excessively large error occurs. Normally with a properly tuned system following errors should be small. Setting a Max limits error can cause the servo to treat errors beyond a specified limit as if they were only the size of the limit and therefore respond less so than they would otherwise. The max limits error is normally set to a value so it is not limiting under normal circumstances.

The Plot below shows a situation where a small max limits error combined with a low P gain severely limits the Output. In the plot below a large move (10000 counts) at a high speed (40000 counts/sec) is commanded. Only P Gain (0.2) is used to provide the Output (green). The max error limit of 200 combined with the low gain (0.2) limits the output to only 40 DAC counts. Even as the true error increases to many thousands of counts, the servo is told to ignore the amount over 200. So the output can never exceed 40 DAC counts. The 40 DAC count limit means that the Axis is therefor not capable of providing the output necessary to keep up with the commanded motion. The axis does the best it can with the limited output, and only does a fraction of the desired motion.

[[File:Move10000.png|none|link=|665x431px]]

After increasing the max limits error the Output (green - right scale) now goes to a much higher value (900), and the Position (red) follows the Command (blue) to a much better degree.

[[File:Move10000_nolimit.png|none|link=|667x430px]]

Increasing the P Gain to 1.6 also applies more Output sooner and the Position follows the command still better.

[[File:Move1000_p1.6.png|none|link=|667x432px]]

===Lead Compensator vs Derivative Gain===
Derivative (D) Gain is often used to help stabilize a system.  It helps to think in the Frequency Domain to help understand how the two forms of compensation help.  Please read below and [http://dynomotion.com/Help/BodeScreen/BodeScreen.htm this] for more information on the Frequency Domain.  Both Compensation methods add positive phase to help stabilize the system.  Unfortunately both methods increase gain at higher frequencies possibly causing the system to go unstable at higher frequency.  A Lead Compensator provides the benefit of positive phase but without as much gain increase at higher frequencies.  This figure shows a simplified Gain Plot comparison:

[[File:DGainvsLead.png|none|link=|593x593px]]

Here is a Bode Plot of a P=0.5 D=20 Compensator. Note the KMotion.exe Bode Plot Screen has the capability of plotting the Frequency Domain Response of the PID+Filters Compensation. Assume we desire positive phase to be added at 40Hz. Notice the positive phase of 40 degrees at 40Hz which is good. However the Gain increase in the 1KHz region of about 21db which is bad.

[[File:P.5D20Annotate.png|none|link=|621x460px]]

Here is a Bode Plot of a P=0.5 N1=N2=25Hz D1=D2=70Hz Compensator. Assume we desire positive phase to be added at 40Hz. We choose N1 N2 and D1 D2 to surround the frequency where the positive phase is desired. Moving them further apart will increase the amount of positive phase but also increase the added Gain. Notice the positive phase of 60 degrees at 40Hz which is good. However the Gain increase in the 1KHz region of about 12db which is bad. However both are improvements over the D Gain compensator.

[[File:PoleZeroFilter.png|none|link=|210x319px]]

[[File:P.5D0N25D70Annotate.png|none|link=|644x478px]]

===Tuning Master/Slave Configurations===
Master/Slave [http://dynomotion.com/Help/ConfigurationScreen/ConfigurationScreen.htm#Master/Slave_Settings Configurations] allow two (or more) motors to drive the same axis. Slaves are configured to follow a Master Axis. For example two lead screws on both sides of a gantry.

Tuning slaved axes is kind of a catch 22. In order to tune one axis the other axis must be tuned well enough to follow and vice versa. If possible, disconnect any mechanical linkage between the Master and Slave and test them separately without Slaving the Axes together to verify each axis Servos (can hold a position), moves at least somewhat properly, and moves in the same direction (assuming a positive [http://dynomotion.com/Help/ConfigurationScreen/ConfigurationScreen.htm#Master/Slave_Settings Slave Gain] will be used).

It is usually possible to incrementally tune each axis, at first moving slowly, then later at higher speeds, accelerations, and gains. Only the Master Axis can be tested with the [http://dynomotion.com/Help/StepScreen/StepScreen.htm Step Response Screen]. This is because the Slave will follow any movement of the Master, but the Master will not follow movement of the Slave. So if the Master Axis is moved all is well as both axes will move together, but if you try to move the Slave axis the two axes will fight. The Master fighting to stay where it is, and the Slave fighting to move.

To test/tune the Slave axis temporarily reverse the Master/Slave roles to make it the Master and then test it as the Master.

Note: only the Master Axis should be included into the Coordinated Motion System.

===Bode Plots===
A Bode Plot is a powerful tool for characterizing and providing insight into a dynamic system. It can help determine closed loop stability, bandwidth/performance, resonant frequencies, and more. It is entirely based on the system being linear. Linear in the sense that if the amplitude of some input signal is changed then the output signal will change proportionally as well. Unfortunately most systems are not entirely linear. Stiction, backlash, encoder quantization, amplifier saturation, and other effects are non-linear. For example driving a system with a signal too small to overcome stiction will result in no output at all whereas a larger signal will result in some output. This is clearly non-linear behavior. It would be nice to use a technique that handles non-linear systems but basically none are known. A Bode Plot is made injecting a stimulus to the system and observing how the system responds. For the reasons of non-linearity it is very important to perform a Bode Plot measurement using a representative level of stimulus similar to what the system will actually have during normal operation. If the Stimulus is not adjusted properly the result is likely to be completely invalid. Additionally the system should be reasonably tuned and stable so that it is responding in a reasonable way to the stimulus. If the system is unstable or very poorly tuned the result is likely to be completely invalid. You might think of it somewhat like shaking a box to determine what is in it. You should shake it with enough intensity and at frequencies to get some reaction, but not so high of intensity to break or distort the object inside. To create a Bode Plot use the KMotion.exe Bode Plot Screen. First select Plot: Time domain - Command, Position, Output vs Time and adjust the Amplitude and cutoff Freq until there is small but significant Position (red) changes (ie 50 encoder counts), at a frequency low enough that the Position at least somewhat attempts to follow the Command (blue), and where the Output (green) is not near saturation for the Drive being used. After the Stimulus/Noise Injection settings are set switch to Plot: Open Loop - Magnitude and Phase vs Frequency. Set the number of Samples to average (ie 20) and perform a Measurement.  [http://dynomotion.com/Help/BodeScreen/BodeScreen.htm See here for more information].

===Links to other Information on Tuning and Bode Plots===
[http://ctms.engin.umich.edu/CTMS/index.php?example=Introduction&section=ControlFrequency umich.edu Introduction section Control Frequency]

[http://www.motiontech.com.au/assets/pdf/Kollmorgen%20Use%20Control%20Theory%20to%20Improve%20Servo%20Performance%20230712.pdf Kollmorgen Use Control Theory to Improve Servo Performance 230712.pdf]

==Problems and Resolutions==
====General====
:* [[Noise - Typical Problems and Resolutions|Dealing with noise on inputs]]. If you experience issues with inputs misreading, the issue may be noise. This page provides examples on what might be causing noise issues and examples of how to possibly deal with noise.
:* Other
===Software-Specific Problems and Resolutions===
:* Place links to pages explaining resolutions to problems that are largely software-related here
[[KFLOP User C Programs Compiling/Launching Slowly because of Windows Defender]]

===Hardware-Specific Problems and Resolutions===
:* Place links to pages explaining resolutions to problems that are largely hardware-related
====[[Step/Dir Drives lose 2 Steps for each pair of Direction Reversals]]====

==Applications and Projects==
:* Place links to pages that explain how you accomplished your particular project. Write clear explanations that provide background on what you did and how you did it.
====[[Tool Changer - router linear 4 Tools - C Program]]====
[[File:LINEAT+ATC.jpg|none|link=|246x178px]]
More linear milling tools: https://www.ichome.com/

====[[Part Zero & Tool Height Touch Plate|Part Zero & Tool Height Touch Plate]]====
====[[Driving Hobby Servos]]====
[[File:HobbyServo.png|left|link=]]

HiTec Type

==Electrical Discharge Machining==
[https://en.wikipedia.org/wiki/Electrical_discharge_machining EDM (wikipedia)] is a method of cutting materials with high precision and detail. Dynomotion Motion Controllers work well for EDM because of the ability for feedrate to be dynamically controlled including reversal along cutting path.

[[Information on BAXEDM Arc Generators used with KFLOP]]

Applied Science video that shows how to build an BAXEDM drilling machine using KFLOP and describes how it works:

{{#ev:youtube|https://youtu.be/rpHYBz7ToII|||||start=980}}

==How to convert a milling machine to a 3D printer in 3 easy steps==
[[File:CNCto3DPrinter.png|none|link=]]

More information [[How to convert a milling machine to a 3D printer in 3 easy steps|here]].

==International and other Languages==
[[Russian]]

[[Spanish]]

Known KMotionCNC CAD/CAM Post Processors

2024-03-25T16:46:41Z

TK: /* Dolphin CAD/CAM */

==Mechsoft==
<div class="yiv354472887MsoNormal">http://mecsoft.com/freemill/</div>
<div class="yiv354472887MsoNormal"></div>
<div class="yiv354472887MsoNormal">Hi Tom,</div>
<div class="yiv354472887MsoNormal"> </div>
<div class="yiv354472887MsoNormal"> After much digging, I did find a post processor file in the Freemill site and it seems to work! </div>
<div class="yiv354472887MsoNormal" style="text-indent: .5in;"> </div>
<div class="yiv354472887MsoNormal" style="text-indent: .5in;">Just an FYI:</div>
<div class="yiv354472887MsoNormal" style="text-indent: .5in;">The (freemill) instructions installing it were not accurate so if you run into this in the future the processor is downloaded at :</div>
<div class="yiv354472887MsoNormal" style="text-indent: .5in;">[http://mecsoft.com/PostProcessors/MILL/kmotion.spm http://mecsoft.com/PostProcessors/MILL/kmotion.spm]</div>
<div class="yiv354472887MsoNormal" style="text-indent: .5in;"> </div>
<div class="yiv354472887MsoNormal" style="text-indent: .5in;">And then the file is installed into</div>
<div class="yiv354472887MsoNormal" style="text-indent: .5in;">C:\ProgramData\MecSoft Corporation\VisualCAM 2014\Posts\MILL</div>
<div class="yiv354472887MsoNormal"> </div>
<div class="yiv354472887MsoNormal">Thanks for your rapid reply!</div>
<div class="yiv354472887MsoNormal"> </div>
<div class="yiv354472887MsoNormal">Troy</div>
<div class="yiv354472887MsoNormal"></div>
==AutoDesk Fusion 360==
<div class="yiv354472887MsoNormal"></div>
See this post

https://forums.autodesk.com/t5/fusion-360-computer-aided/tool-parameters/td-p/5711808

Also this post

http://www.cnczone.com/forums/dynomotion-kflop-kanalog/343726-posprocessor-fusion360-kflop.html#post2086576

'''Alexander (Александр Украинец)''' contributed two Posts. One for Mill and one for Lathe (the .txt extension should be removed)

[[Media:Fusion_360_KFLOP_Mill.cps.txt|Fusion_360_KFLOP_Mill.cps.txt]]

[[Media:Fusion360_KFLOP_Turning.cps.txt|Fusion360_KFLOP_Turning.cps.txt]]

[[Media:Fusion360_KFLOP_Turning_Rev2.cps.txt|Fusion360_KFLOP_Turning_Rev2.cps.txt]] (Added thread cutting G32)

'''mirocha''' posted this file on [https://www.cnczone.com/forums/dynomotion-kflop-kanalog/394550-fusion-360-post-processor-post2345608.html#post2345608 cnczone]

[https://www.dynomotion.com/wiki/index.php?action=ajax&title=-&rs=SecureFileStore::getFile&f=/7/73/KmotionCNC_fusion_post_processor.pdf KMotionCNC Fusion Post Processor]

Post Processor for Fusion 360, I built a DIY 3 axia router, built to mill aluminum, 40 mm anti backlash ball screws, 3 hp spindle, stout machine. My programing computer hard drive crashed, new hard drive and reloaded Fusion 360 took hours to find the post processor file I was using and has worked for a few years with no problems. Below is the post processor for fusion 360 that I use. In my case I zero the XYZ to the piece, I do not have a tool changer, when I create the g code in Fusion 360 I create the g code for each tool separately, run the program, manually change the tool and run the next program for the next tool. This has worked great for me.

If your a DIY and need a post processor for fusion 360 this one works for Kflop/Kmotion, What I did was made a copy of one of the fusion 360 stock .cps files that are in fusion 360, open the KmotionCNC.pdf in notepad copy what is in the pdf over the stock .cps file and renamed it KmotionCNC

==BobCAD==
See Forum Thread [https://www.dynomotion.com/forum/viewtopic.php?f=10&t=1230 here].

==Dolphin CAD/CAM==
See Forum Thread [https://www.dynomotion.com/forum/viewtopic.php?f=10&t=1743#p7413 here].

Known KMotionCNC CAD/CAM Post Processors

2024-03-25T16:42:07Z

TK: /* Dolphin CAD/CAM */

KMotionCNC Screen Editor

2024-03-21T16:27:11Z

TK: Using Resizeable/Floating GViewer Control with Custom Screen

''' '''

=====Introduction=====

Video: [https://www.youtube.com/watch?v=uQWDttzKuDA https://www.youtube.com/watch?v=uQWDttzKuDA]
'''Features include:'''

* Show/Hide Controls
* Change Size and Position of Controls
* Change Label/Button Text
* International Character Support
* Change Font/Text Size
* Bitmap Buttons and Labels
* JPG, BMP, PNG Bitmaps
* Toggle Bitmap Labels (LEDs)
* Customizable Keyboard Hotkeys
* Customizable Button Tool Tips
* Programmable DRO (Digital Read Output) Labels
* Custom User Entry Controls

The 6-axes default screen is changed to a 5-axes screen by deleting the z-axis. We start by installing KMotion 4.34b or later. Note that if you don’t already have Dot Net version 4.62 or Visual Studio 2015 libraries installed, you will be prompted to load those. Create desktop icons for KMotion, KMotionCNC and KMotionCNC Screen Editor. Run KMotion and observe the default 3-axes resizable screen.

[[File:3axes-resizable-screen.png|none|link=|504x286px]]

Close the G Viewer window and change the dialog face to Default Custom Screen with no screen script specified. (Tool Setup):

[[File:Default-custom-screen.png|none|link=]]

Now run the KMotionCNC Screen Editor. It automatically syncs to KMotionCNC’s controls and they are graphically displayed.

This graphical representation allows you to select which controls you want to modify.

Notice we can select a control and immediately hide or show it over at KMotionCNC. The controls can be moved or resized. There is also unlimited undo/redo. Multiple controls can be selected by dragging the mouse over the graphical display. Click SHIFT to add more controls, or CTRL to remove from the selection.

'''Examples: '''

* Select multiple controls for hiding and moving.
* Change main dialog screen dimensions.
* Change label text. Push SET key and KMotion CNC screen updates the text.
* Increase the size of the controls.

The screen editor features international text support. Note that only certain fonts are capable of displaying international text. In our example, we selected Arial.

Labels can show or toggle bitmaps based on an IO bit. As an example, we first we select bitmap 1, then bitmap 2. Increase the size of the label, so the bitmap shows properly. Then assign an IO bit number that will control the bitmap displayed. Notice the bitmap turns green, because the bit is currently on. Open KMotion and look at the state of IO bit #46 and see that it is on. Toggling the bit affects the bitmap on the screen:

[[File:Toggle-IO-bit.png|none|link=]]

Users can configure push buttons for text, font, size, color, and tool tip. Select two sample labels and change them to type: button. Select both buttons and modify their fonts as well as their size. Four colors are available for text and background, each in normal and depressed button state. You can then change the name of each button individually, one to say “On” and the other“Off”. You can assign tool tips to each of the buttons, so when the operator hovers over the buttons, they will be prompted with a tool tip notification.

Buttons can be assigned to perform actions. Select a script that can either be a screen script or an action. We select an action type to set bit 46 to 1. Notice that this is the script that indicated that. For the other button, we select an action which sets bit 46 to 0. Now pushing the buttons will perform these actions. Save your new screen as a screen script file. Screen script is under the KMotionCNC directory and the sub-directory“Screens”. Configure KMotionCNC to use this new screen at every new startup.Notice that tool setup screen can be accessed by right-mouse clicking on the KMotionCNC title (in “Tools/Setup files”). Select the screen you just created.

Some more advanced features include input fields, C program actions, label DROs. Load the addition example in the screen editor. Example contains two user input controls and one DRO label control. The input edit controls are associated with KFLOP persist variables 160 and 161. The DRO label is associated with KFLOP persist variable 162. The Add button is configured for screen script action to run a C program in KFLOP. The C program is contained in the file “Add.c”. Test it by entering two values and pushing the Add button. Now open KMotion and look at the simple C code that is behind the function. (Open the file “Add.c”).

=====Momentary and Toggle button types in KMotion CNC Screen Editor=====
[https://www.youtube.com/watch?v=eE2mSUXxN2M https://www.youtube.com/watch?v=eE2mSUXxN2M]

Start KMotion CNC Screen Editor, and click on the “Main” tab, then on “Read Script” and choose the file named MomentaryToggle.scr

You will see two buttons, a Momentary button assigned to bit46 and a Toggle button assigned to bit 47. You will also see two labels to display the status of bits 46 and 47 as LED bitmaps. We also have KMotion displaying the status of bits 46 and 47.

[[File:Momentary-button-2.png|none|link=]]

Clicking the Momentary button activates the bit; releasing it,deactivates it. Clicking the Toggle button once sets the bit; clicking it again releases it.

=====Instantaneous Feed Rate Display=====
[https://youtu.be/w-bKvqXCd0Q https://youtu.be/w-bKvqXCd0Q]

Normally the feed rate indication in KMotionCNC shows ''average'' feed rate over 100ms, assuming straight line motion. Here we use a C program to calculate a more instantaneous rate and display it on the KMotionCNC screen using the KMotionCNC screen editor. Here the C program samples two positions and times, computes the delta position and the delta time, formats it to a string and displays it onto DRO label 162 in KMotionCNC and it performs this action roughly every one ½ seconds. Here is the screen script for the screen shown on the left, we’ve added a type DRO label in the screen editor, edited colors and it is connected to persist variable 162. This job consist of a rapid helix bore at a rate of about 6 revolutions per second. It shows the instant feed rate being more correct.

There is a newer example which also displays the feed rate as a vertical bar graph. See:

ShowInstantFeedRate3AxisBar.scr and related C Program ShowInstantVelocityDROBar.c

=====Split/Full/Hidden GViewer Display on Main Dialog Face=====
[https://youtu.be/VkBhYpyGpNU https://youtu.be/VkBhYpyGpNU]

=====Using Resizeable/Floating GViewer Control with Custom Screen=====
Normally with a Custom Screen the GViewer Plotting is sent to the GViewer Control on the Main Dialog Face and the floating/re-sizable GViewer window is not used. It is normally closed and the GViwer Button to open it is hidden. However if it is desired to use the floating/re-sizable GViewer window rather than the Control on the Main Screen (which is hidden), this can be accomplished by setting the Var parameter for the Main Screen GViewer Control (IDC_viewctrl) to 0. Non-zero values will direct the Plotting to the GViewer Control on the Main Dialog Face.

=====Main Screen Style=====
KMotionCNC Screen Editor supports changing main screen style. See the Main Dialog Screen Option under the Main Tab. Boolean Screen Script Options: "Caption:" "MaxBox:" "MinBox:" "ResizeFrame:" "Maximize:"

=====Maximized Captionless KMotionCNC Screens=====
[https://youtu.be/R44F0_upIoA https://youtu.be/R44F0_upIoA]

New option in KMotionCNC Screen Editor V4.34e allows screens to be maximized to full screen and with or without Window Frame/Title. New options in Screen Editor: turn minimum box on or off, maximum box on or off, resizing frame on or off. Caption on top can be present or absent.

Available viewing options (three buttons on the top-right hand side of the screen: “Split”: Split screen mode, “View”: G Code Viewer or “Code”: G Code.

=====Control styles=====
''' '''Available style options: [[File:Style-options.png|none|link=]]

* '''Label''' Can be text or bitmap. The background is determined by the main dialog background.
* '''Button''' Buttons can have all 4 options (foreground and background colors in on- and off-state) or they can also be bitmaps. Labels can load actions/scripts when the main screen is loaded.
* '''MotionButton''' Motion buttons are strictly for jog button use only.
* '''ToggleButton''' See description above and [https://www.youtube.com/watch?v=eE2mSUXxN2M video].
* '''DROLabel '''('''D'''igital '''R'''ead '''O'''ut) runs a program in KFLOP, e.g. reads two edit cells in the “Add” example and passes back the result. X, Y, and Z are other examples of DRO labels.
* '''VertBar''' Plots a vertical graph from 0 to 100% and is read by KFLOP like DRO labels. See also the [https://youtu.be/w-bKvqXCd0Q Instant Feed Rate Display video].
* '''Radio''' button
* '''Momentary''' '''button''' See description above and video: [https://www.youtube.com/watch?v=eE2mSUXxN2M https://www.youtube.com/watch?v=eE2mSUXxN2M]
* '''DualButton''' See description above and video: [https://www.youtube.com/watch?v=8dAEeGnLaRg https://www.youtube.com/watch?v=8dAEeGnLaRg]
* '''Checkbox '''
* '''DualLabel '''F for feed rate and S for spindle are example of dual labels. They display the state (one or another). They are fixed and cannot be edited.

=====Control attributes=====
'''[[File:Control-attributes.png|none|link=]]'''

* '''Select ID''' Defines the name of the control on the screen.
* '''Type''' Defines the type of control, e.g.: CONTROL, PUSHBUTTON, COMBOBOX.
* '''Font''' Set the font type, size and normal, bold, or italic.
* '''BitmapFile1, BitMapFile2 '''Select a bitmap image (.bmp, .gif or .png) for your buttons. BitMapFile1 will show the selected file when the button is in normal state, BitMapFile2 when the button pressed.
* '''Colors''' Select two colors for on- and off-state (text).
* '''Highlight''' Select two colors for on- and off-state (background).
* '''Tool Tip''' Compose text to describe the button action. This text will be visible when the user hovers over the button.
* '''HotKey''' Assigns a keyboard key to perform an action. This field is by default set to “-1”. For example, select a control like “mm” and type “CTRL M” or select “in” and type “CTRL I” and click “Set”. The “x” button next to the field will restore the value back to “-1”.
* '''Var '''Numeric variable attribute. Assigning a number toggles the corresponding bit in KFLOP (from 0 to 2047).
* '''X, Y '''Changes the horizontal and vertical position of the control.
* '''Width, Height''' Changes the size of the control.
* '''Script''' Using this field, the user has three options: 

a) Selecting a screen script file from the library:

[[File:Script-Option-1.png|none|link=]]

b) Selecting an Action: [[File:Script-Option-2.png|none|link=]]

c) Selecting a Windows Message: [[File:Script-Option-3.png|none|link=]]

* '''Show/Hide''' Select a control and immediately show or hide it.

* '''Move/Resize''' Move the position of the control or change its size.
* '''Undo/Redo '''An unlimited number of undoes and redoes is available.
* '''Copy/Paste '''The user can edit all three screens (Split, View, and Code) by clicking “Copy” after making an edit such as moving a button, then loading the next screen, clicking outside the editable area and selecting “Paste”.
* '''General '''When selecting multiple controls, white fields are shown when all settings are the same, and grey fields when the values are different. In the example below note that we have selected the radio buttons labeled 1 through 7. While they all share the same font type, size, width and horizontal (x) position etc., “text” and “y-position” are grayed-out, since the radio buttons’ text labels and their vertical position are unique to each field. To override this, just click into the grayed-out field(s) and start editing. [[File:General.png|none|link=]]

=====Main Window attributes=====
* '''Main Dialog Screen '''Defines the look and feel as well as the size of your KMotionCNC screen. You can choose a background color, or select a bitmap file as your background. Choose the size of the window, or whether the window should be resizable or fixed and so on. 
* '''Script File''' Select a screen script file from the library or set an action. A screen script file defines the look of a page. You can assign an action to a button to load a screen script file. [[File:Style-file.png|none|link=]]

=====Bitmap types, Alpha, and locations=====
 The following bitmap types are supported: .bmp, .gif, and.png. Out of these, only the png file type supports alpha channels, i.e. background transparency. Images are stored in the following “Resources” location: \KMotion434i\PC VC Examples\KMotionCNC\res

=====Motion Buttons (for Jogging)=====
Special Buttons for Jogging exist with Style MotionButton. Although these buttons can be customized with regard to Bitmap images, size, positions, Font, ToolTips, Show/Hide, and Hotkeys they have fixed functionality for the 6 GCode Axes XYZABC. They support momentary Hotkey and combined mouse operation with the ability to have multiple Hotkeys pushed simultaneously and dynamically change speed using the SHIFT key. Additional MotionButtons can not be currently added.

[[File:MotionButtons.png|none|link=]]

The Jog Buttons are grouped into 6 buttons per axis. 3 of the 6 buttons are used for moving one direction and 3 for the other direction. The 3 buttons correspond to Stepping a fixed distance, Jogging slow, and Jogging Fast. The Resource IDs corresponding to each axis are:

'''X + = IDC_RightStep, IDC_Right, IDC_Right2'''

'''X - = IDC_LeftStep, IDC_Left, IDC_Left2'''

''' '''

'''Y + = IDC_UpStep, IDC_Up, IDC_Up2'''

'''Y - = IDC_DownStep, IDC_Down, IDC_Down2'''

''' '''

'''Z + = IDC_ZplusStep, IDC_Zplus, IDC_Zplus2'''

'''Z - = IDC_ZminusStep, IDC_Zminus, IDC_Zminus2'''

''' '''

'''A + = IDC_AplusStep, IDC_Aplus, IDC_Aplus2'''

'''A - = IDC_AminusStep, IDC_Aminus, IDC_Aminus2'''

'''B + = IDC_BplusStep, IDC_Bplus, IDC_Bplus2'''

'''B - = IDC_BminusStep, IDC_Bminus, IDC_Bminus2'''

'''C + = IDC_CplusStep, IDC_Cplus, IDC_Cplus2'''

'''C - = IDC_CminusStep, IDC_Cminus, IDC_Cminus2'''

'''Note the HotKeys for all 3 Motion Buttons for each axis/direction must be set to the same value.''' This is because the same HotKey combined with CTRL and SHIFT alter the behavior to Step and Fast respectively. If not all 3 buttons are desired for the screen the others may be hidden but should be all defined to the same HotKey for the HotKey functionality to work correctly. Furthermore no other buttons should be defined with the same HotKeys. The Screen Editor has a special feature to test for Duplicate HotKey assignments called "check dup hotkey"

There is also one associated IDC_StopStep button which will stop any Step Movement currently in progress.

=====Performing an action Immediately within Screen Script=====
Normally when processing a Screen Script, the "Script" Parameter defines for a Push Button Control what should happen when the Push Button is pushed. However when a "Script" Parameter is specified for a static Label the Action will occur immediately after the Screen Script is processed.

For example: when loading a screen intended for Simulation we might want to have the Simulation mode automatically selected on. So the Script for the IDC_SimulateStatic Label might be set to check the simulate checkbox with:

WinMsg:DlgName;IDC_Simulate;BM_SETCHECK;BST_CHECKED

=====Scaling an Entire Screen or Portion of a Screen=====
A new Screen Editor feature has been added to stretch/shrink a number of selected screen controls by a specified percentage. The height and width of the controls can be stretched as with their XY positions. The horizontal and vertical directions can be Stretched/Shrunk independently. Scaling the Vertical direction will also scale any Font point settings. The Width and Height of the entire dialog will also be scaled accordingly.

To Scale a Screen:

# Select the controls to be scaled - usually all controls (drag a box to select multiple controls)
# Select mode: Screen Scale
# Select the desired Size Change as a percentage 1-100% (ie 60% corresponds to a stretch/shrink factor of 1.6)
# Push Increase/Decrease Width button
# Push Increase/Decrease Height button

Note: it is best to scale in one step vs multiple steps as control widths and font sizes are integers and may have rounding after each step.

Note: any bitmap images will be unchanged and remain the same size. They can be manually scaled with a graphics app if necessary.

If not in the current Version a Version with scaling added can be downloaded here (place in \KMotion\Release Directory):

[http://dynomotion.com/Software/Patch/ScreenEditorWithScaling_V434j/KMotionCNCScreenEditor.exe KMotionCNC Screen Editor with Scaling]

Screen Editor with Screen Scale of 60% and all controls selected:

[[File:ScreenScale.png|none|link=|710x627px]]

Example Original Screen:

[[File:ScreenScale100.png|none|link=|639x471px]]

Example Scaled up 60%

[[File:ScreenScale160.png|none|link=|879x641px]]

Main Page

2024-03-02T00:44:36Z

TK: Board Terminal DXF/DWG files

=='''Dynomotion wiki'''''' '''==
Welcome to our wiki where you can find and share knowledge on Dynomotion's systems. To begin adding information to this wiki, simply create an account, verify your email, and start editing (click pencil icon). To make editing pages easier for everyone, we have installed a [https://help.bluespice.com/index.php/VisualEditor visual editor] by default. This visual editor allows you to edit a wiki page much like you would a standard word processing document.  For the seasoned wiki editors, standard [https://www.mediawiki.org/wiki/Help:Editing MediaWiki editing] may also be used.<nowiki> </nowiki>

''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 is safe to use. In no case will any contributor or Dynomotion be liable for incorrect information. Dynomotion reserves the right to modify or delete any contributions. ''

 Thanks for Contributing!

[http://dynomotion.com Official Dynomotion Site]

==Editing and Creating Wiki Pages==
Unintuitively, you first create a link to the page you want to make before you can make the page. To make a new page: while editing, right-click where you want your link to be, insert a link with a descriptive title and link text, save the page, click on the link you created, then click on "Empty Page" to begin editing your new page.

Here are a few other quick tips:

* You can insert links or images by Right-Clicking with the mouse on the line where you want the link or image to appear.
* For Spell Correction you can use Ctrl-Right-Click.
* To insert a YouTube Video use an EmbedVideo command such as <nowiki> {{#ev:youtube|xxxxx}}
</nowiki>with xxxxx changed to the Video ID.
* Choose a descriptive page name and link text when creating a new page: e.g. Not "My Machine", but rather "Brand X Three Axis Milling Machine Retrofit"
* Create pages in an organized manner: Describe what the page is about, create clear sections that flow

For more information:

[[Help:New Page Creation|How to create a new wiki page]]

[[Help:Editing Pages|How to Edit and insert Media into your wiki pages]]

==Dynomotion Software Topics==
===Installation Topics===
* Announcement of our Latest Release (5.3.2) on the [https://www.dynomotion.com/forum/viewtopic.php?f=4&t=1725 Dynomotion Forum]
* [https://dynomotion.com/Software/Download.html Latest Release] Note: For Windows 7 64bit signed Drivers to work, all Windows Updates should be performed.
* [[Upgrading from previous KMotion Versions]]

Archive of Test Releases:

* Previous Test Release: 11/20/2023: [https://dynomotion.com/Software/KMotion5.3.1.exe KMotion.exe 5.3.1], See the release notes for this test version here: [https://dynomotion.com/Software/KMotion%20Released%20Version%205.3.1%20Changes.pdf 5.3.1 release notes (pdf)]* Previous Test Release: 09/19/2023: [https://dynomotion.com/Software/KMotion5.3.0.exe KMotion.exe 5.3.0], See the release notes for this test version here: [https://dynomotion.com/Software/KMotion%20Released%20Version%205.3.0%20Changes.pdf 5.3.0 release notes (pdf)]
* Previous Test Release: 06/30/2023: [https://dynomotion.com/Software/KMotion5.1.0.exe KMotion.exe 5.1.0], See the release notes for this test version here: [https://dynomotion.com/Software/KMotion%20Released%20Version%205.1.0%20Changes.pdf 5.1.0 release notes (pdf)]
* Previous Test Release: 05/01/2023: [https://dynomotion.com/Software/KMotion5.0.7.exe KMotion.exe 5.0.7], See the release notes for this test version here: [https://dynomotion.com/Software/KMotion%20Released%20Version%205.0.7%20Changes.pdf 5.0.7 release notes (pdf)]
* Previous Test Release: 09/21/2022: [https://dynomotion.com/Software/KMotion435h.exe KMotion.exe V4.35h], See the release notes for this test version here: [https://dynomotion.com/Software/KMotion%20Released%20Version%204.35h%20Changes.pdf V4.35h release notes (pdf)]
* Previous Version 4.35g was not released, but see the change notes for this version here: [https://dynomotion.com/Software/KMotion%20Released%20Version%204.35g%20Changes.pdf V4.35g change notes (pdf)]
* Previous Test Release: 12/28/2020: [https://dynomotion.com/Software/KMotion435f.exe KMotion.exe V4.35f], See the release notes for this test version here: [https://dynomotion.com/Software/KMotion%20Released%20Version%204.35f%20Changes.pdf V4.35f release notes (pdf)]
* Previous Test Release: 11/18/2019: [https://dynomotion.com/Software/KMotion435e.exe KMotion.exe V4.35e], See the release notes for this test version here: [https://dynomotion.com/Software/KMotion%20Released%20Version%204.35e%20Changes.pdf V4.35e release notes (pdf)]
* Previous Test Release: 09/10/2019: [https://dynomotion.com/Software/KMotion435d.exe KMotion.exe V4.35d], See the release notes for this test version here: [https://dynomotion.com/Software/KMotion%20Released%20Version%204.35d%20Changes.pdf V4.35d release notes (pdf)]
* Previous Test Release: 01/28/2019: [https://dynomotion.com/Software/KMotion435b.exe KMotion.exe V4.35b], See the release notes for this test version here: [https://dynomotion.com/Software/KMotion%20Released%20Version%204.35b%20Changes.pdf V4.35b release notes (pdf)]
* Previous Test Release: 12/21/2018: [https://dynomotion.com/Software/KMotion435a.exe KMotion.exe V4.35a], See the release notes for this test version here: [https://dynomotion.com/Software/KMotion%20Released%20Version%204.35a%20Changes.pdf V4.35a release notes (pdf)]
* Previous Test Release: 09/28/2017: [https://dynomotion.com/Software/KMotion434j.exe KMotion.exe V4.34j], See the release notes for this test version here: [https://dynomotion.com/Software/KMotion%20Released%20Version%204.34j%20Changes.pdf V4.34j release notes (pdf)]
* Previous Test Release: 05/07/2017: [https://dynomotion.com/Software/KMotion434i.exe KMotion.exe V4.34i], See the release notes for this test version here: [https://dynomotion.com/Software/KMotion%20Released%20Version%204.34i%20Changes.pdf V4.34i release notes (pdf)]
* Previous Test Release: 12/14/2016: [https://dynomotion.com/Software/KMotion434h.exe KMotion.exe V4.34h], See the release notes for this test version here: [https://dynomotion.com/Software/KMotion%20Released%20Version%204.34h%20Changes.pdf V4.34h release notes (pdf)]
* Previous Test Release: 12/13/2016: [https://dynomotion.com/Software/KMotion434g.exe KMotion.exe V4.34g], See the release notes for this test version here: [https://dynomotion.com/Software/KMotion%20Released%20Version%204.34g%20Changes.pdf V4.34g release notes (pdf)]
* Previous Test Release: 12/05/2016: [https://dynomotion.com/Software/KMotion434f.exe KMotion.exe V4.34f], See the release notes for this test version here: [https://dynomotion.com/Software/KMotion%20Released%20Version%204.34f%20Changes.pdf V4.34f release notes (pdf)]
* Previous Test Release: 11/07/2016: [https://dynomotion.com/Software/KMotion434e.exe KMotion.exe V4.34e], See the release notes for this test version here: [https://dynomotion.com/Software/KMotion%20Released%20Version%204.34e%20Changes.pdf V4.34e release notes (pdf)]
* Previous Test Release: 10/32/2016: [https://dynomotion.com/Software/KMotion434d.exe KMotion.exe V4.34d], See the release notes for this test version here: [https://dynomotion.com/Software/KMotion%20Released%20Version%204.34d%20Changes.pdf V4.34d release notes (pdf)]
* Previous Test Release: 10/23/2016: [https://dynomotion.com/Software/KMotion434c.exe KMotion.exe V4.34c], See the release notes for this test version here: [https://dynomotion.com/Software/KMotion%20Released%20Version%204.34c%20Changes.pdf V4.34c release notes (pdf)]
* Previous Test Release: 10/03/2016: [https://dynomotion.com/Software/KMotion434b.exe KMotion.exe V4.34b], See the release notes for this test version here: [https://dynomotion.com/Software/KMotion%20Released%20Version%204.34b%20Changes.pdf V4.34b release notes (pdf)]
* Previous Test Release: 03/09/2016: [https://dynomotion.com/Software/KMotion434a.exe KMotion.exe V4.34a], See the release notes for this test version here: [https://dynomotion.com/Software/KMotion%20Released%20Version%204.34a%20Changes.pdf V4.34a release notes (pdf)]
* [https://dynomotion.com/Help/KFLOPQuickStart/KFLOPQuickStart.htm How to install KMotion.exe and KMotionCNC]
* [[How to install KMotion.exe and KMotion in Windows 10|Preparing Windows 10 for driver installation]] (no longer required)
* [[Special Case for Windows 8.1 Industry Embedded Enterprise]]
* [[Updating KFLOP Firmware|How to update KFLOP Firmware]] - whenever a new version of software is installed, the firmware within KFLOP must be updated to match the new version

===KMotion.exe Executive Software Topics===
KMotion.exe is the main program that is used to configure settings in KFLOP, initialize axes, and to write C programs to configure and setup KFLOP to control your system. In this program you can plot step response, test movement, view Bode plots, monitor I/O, set filter parameters, and generally set the pertinent parameters.

* [http://www.dynomotion.com/Help/index.htm General software information] from the manuals
* Insert pages for other KMotion.exe-related topics here

===Configuration Topics===
====Channels, Channels, Channels what are they?====
[[Channels Channels Channels|Read Article Here]]

====How to Setup Backlash Compensation====
[[Backlash Compensation|Read Article Here]]

====PWM Output Mode====
[[PWM Output Mode|Read Article Here]]

===KMotionCNC Software Topics===
KMotionCNC is Dynomotion's CNC program used as a graphical user interface to your KFLOP-enabled machine tool. KMotionCNC has all of the basic functionality you need to run a machine of up to 6 axes, in addition to spindle control.

* Insert pages for other KMotionCNC-related general topics here

====Using KMotionCNC====
* Homing discussion - page to be created
* Insert other KMotionCNC use pages here

[[Internal/concave Path Tool Radius Compensation Example G41/G42]]

[[Known KMotionCNC CAD/CAM Post Processors]]

[[Invoking C Programs with Execute Only for previously Downloaded Programs]]

[[Rigid Tapping G84 Setup and Use]]

[[Tool Length/Offsets G43Hn G49]]

====Customize KMotionCNC====
KMotionCNC is written as a Windows C++ MFC (Microsoft Foundation Classes) program developed in Visual Studio. Source code is provided and may be customized using Visual Studio. MFC Support is a requirement.

: '''General Information'''
: Compiling KMotionCNC
:: The KMotionCNC's Visual Studio Project Solution (\PC VC Programs\KMotionCNC\KMotionCNC.sln) is currently written for Visual Studio 2015 Standard. This version can be used for the simplest compatibility. Projects can be upgraded to newer version of VS with minimal effort. Including Microsoft's Free Visual Studio 2013 Community. [[PC Example Applications|More info on PC Example Applications.]]
:: Note Test Versions 4.34a and later have project solutions targeted for Visual Studio 2015 Community which is free for most Users.
: '''KMotionCNC Customization Examples and Applications'''
:: Links to examples of projects that explain KMotionCNC customizations. Troy (tmday7) created some helpful documents (PDF format):
:
:* [https://www.dynomotion.com/forum/archive/attachments/How%20to%20Edit%20KMotionCNC%20Faces.pdf How to edit KMotionCNC faces]
:* [https://www.dynomotion.com/forum/archive/attachments/Adding%20External%20Buttons.pdf Adding external buttons]
:* [https://www.dynomotion.com/forum/archive/attachments/Adding%20More%20User%20Buttons.pdf Adding more user buttons]
:* [https://www.dynomotion.com/forum/archive/attachments/Adding%20Jog%20Percent%20Cell%20to%20Main%20Dialog%20Face.pdf Adding Jog Percent Cell to Main Dialog Face]

====KMotionCNC Screen Editor====
Introduces the capability of using Screen Script files to modify the look and function of KMotionCNC. [[KMotionCNC Screen Editor|More information.]]

====KMotionCNC Geometric Correction====
Information regarding the powerful [https://dynomotion.com/Help/KMotionCNC/GeoCorrection.htm Geometric Correction capability] which allows calibration and distortion correction of the XY CAD space to Machine/Actuator Space as well as flatness in Z. Simple 4 point correction tables can apply XY Scale, Rotation, skew, offset, tilt. Larger tables can apply more non-linear corrections.

Note the Geometric Correction is built into the KMotion Libraries and can be utilized by Custom Programs as well as with KMotionCNC [[Geometric Correction|More information and Examples.]]

===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. 

'''Note All the projects in KMotion Versions 4.34a and later have now been updated and should work out-of-the-box with VS2015.'''

[[PC Example Applications|More information.]]

===KMotion Libraries - GCode Interpreter - Trajectory Planner - Coordinated Motion - .NET===
The KMotion Libraries are a series of DLLs (Dynamic Link Libraries) that reside on the PC that contain the common core motion control, I/O, and communication functionality for KFLOP. These libraries permit PC Applications to be built using high level control without being concerned with the underlying details of Interpreting GCode, Trajectory Planning, Coordinated Motion, Motion Buffering, USB Communication, etc.

[[KMotion Libraries - GCode Interpreter - Trajectory Planner - Coordinated Motion - .NET|More information]].

===Kinematics===
The KMotion Libraries contain a Kinematics Layer where Users can add their own non-linear Kinematics

[[Kinematics|More information]].

===KFLOP C Programs===
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.

[[KFLOP C Programs|More Information]]

===ModBus===
Modbus can be connected to the PC or directly to KFLOP. A PC connection will not be deterministically real-time but may work for basic speed control and on/off. Here is a related Thread for interfacing KMotionCNC to Modbus using a [http://www.modbusdriver.com/modpoll.html free utility]:

[https://www.dynomotion.com/forum/archive/sending%20ModBus%20msgs%20from%20KmotionCNC%20to%20a%20RS485%20port.html Sending ModBus msgs from KmotionCNC to a RS485 port]

To connect Modbus directly to KFLOP's [http://www.dynomotion.com/Help/RS232/RS232.htm UART] see the C Examples in \C Programs\RS232\ModBus\

===Linux Support===
KMotion Motion Libraries are fully supported under Microsoft Windows. Some Users have ported the KMotion Libraries to Linux. Dynomotion will offer support where possible but can't offer full support under Linux. Special Thanks to [https://github.com/parhansson/KMotionX Par Hansson] for the initial Linux Port.

See [[Linux|here]] for more info.

==Dynomotion Hardware Topics==
===General Hardware Information===
====[[KFLOP Hardware Info|KFLOP specific Hardware Info]]====
====[[KStep Hardware Info|KStep specific Hardware Info]]====
====[[Kanalog Hardware Info|Kanalog specific Hardware Info]]====
====[[SnapAmp Info|SnapAmp specific Hardware Info]]====
====[[Konnect Hardware Info|Konnect specific Hardware Info]]====

===Wiring Diagrams===
[[Media:Kanalog_Connections.pdf|Basic Kanalog DAC and Encoder Connections 3 Axis]]

[[Media:KanalogSchematic3Axis.pdf|Basic Kanalog DAC and Encoder Connections 3 Axis #2]]

[[Media:dyn4 kanalog KE1524 V1.1.png|Basic Kanalog DAC and DMM DYN4 Drive 1 Axis]]

[[Media:Kflop-Kanalog_wiring_11-19-2018.pdf|Kanalog with Geckos G210 updated 11-19-2018]] (Thanks to Joseph Mirocha)

[[Media:Kanalog_to_Tree_Journeyman_325_by_Rick_B.pdf|Kanalog to Tree Journeyman 325.pdf]] (Thanks to Rick_B)

[[Media:KFlopSnapBrushMPG.pdf|KFLOP+SnapAmp DC Brush Motors with MPG]]

[[Media:Stepper_Wiring_Diagram_Step-Dir_on_JP5.pdf|KFLOP JP5 Open Collector Step/Dir Connections to Power Step PSD5042-2P Drives ]]

[[Media:Matrika_V1_wiring_diagram_Rev1.pdf|KFLOP+KStep with VFD and NPN Limit Switches for Matrika Rev1]]

[[Media:KonnectTouchPlate.png|Touch Plate Wiring to Konnect]]

[https://easyeda.com/350banshee/BreakoutBoard-93bdd16e3c3d48b98ae66c34f2436c40 User Created KFLOP JP7 Breakout/OptoIsolation Board] Schematic, Gerbers, PCBs Publicly available (thanks 350banshee)

[https://www.dynomotion.com/wiki/index.php?action=ajax&title=-&rs=SecureFileStore::getFile&f=/b/bb/RotarySwitchToKanalog.png Rotary Switch Connected to Kanalog Opto Inputs]

===3D Board Models===
[[Media:kflop-kstep-3d-models-1.snapshot.3.zip.txt|kflop-kstep-3d-models-1.snapshot.3.zip.txt]] STEP file format - Thanks to Curtis

[[File:kflop_kstep_render.JPG|none|link=|329x329px]]

[[Media:KFLOP3D_Step_IGS_Chris.zip.txt|KFLOP3D_Step_IGS_Chris.zip.txt]] STEP and IGS models - Thanks to Chris

[[File:KFLOP_3D.png|none|link=|413x296px]]

[[Media:KONNECT_BOARD_MODEL.zip.txt|KONNECT_BOARD_MODEL.zip.txt]] STEP model - Thanks to Jeff Redington

(Component locations may be off one way or another by .5mm)

[[File:Konnect_Board.png|none|link=|339x292px]]

Konnect Basic Step file showing hole locations

[[Media:KonnectHoles.stp.txt|KonnectHoles.stp.txt]]

[[File:KonnectHoles.png|none|link=|352x323px]]

Kanalog Step Model with Mechanical hole and Pin locations

[[Media:Kanalog.stp.txt|Kanalog.stp.txt]]

[[File:KanalogFromStep.png|none|link=|304x279px]]

Kanalog Step Model with Mechanical hole and Connectors (Thanks to

Roberto Gotti of Powertech)''' '''

[[Media:KANALOG_BOARD.stp.txt|KANALOG_BOARD.stp.txt]]

[[File:KanalogWithConnectors.png|none|link=|311x286px]]

===Board Terminal DXF/DWG files===
[[Media:KFLOP_Terminals.dxf|KFLOP_Terminals.dxf]] [[Media:KFLOP_Terminals.dwg|KFLOP_Terminals.dwg]]

[[Media:Kanalog_Terminals.dxf|Kanalog_Terminals.dxf]] [[Media:Kanalog_Terminals.dwg|Kanalog_Terminals.dwg]]

[[Media:Konnect_Terminals.dxf|Konnect_Terminals.dxf]] [[Media:Konnect_Terminals.dwg|Konnect_Terminals.dwg]]

[[Media:KStep_Terminals.dxf|KStep_Terminals.dxf]] [[Media:KStep_Terminals.dwg|KStep_Terminals.dwg]]

===Wiring Topics===
Place links to pages on wiring inputs and

outputs specific to your experiences and projects. Be descriptive with page titles and links.

====KFLOP IDC Connectors and Cables====
Cables that connect between Dynomotion boards are normally included when purchasing the boards together. They are also very common and easy to make. Use '''16-conductor or 26-conductor ribbon cable''' (0.05 inch pitch 26 AWG preferrably or 28AWG) and IDC sockets. [[File:RibbonCable.png|none|link=]]
16 conductor ribbon cable 3M part number 3801/16 100 https://www.digikey.com/product-detail/en/3m/3801-16-100/3M156105-100-ND/1107501 26 conductor ribbon cable 3M part number C3801/26 100 https://www.digikey.com/product-detail/en/3m/C3801-26-100/C3801-26-100-ND/1107648 Winford also sells ribbon cable (although only the thinner 28 AWG): http://www.winford.com/products/rib.php Note you can usually tear off wires to reduce the number of conductors. For example from 26 down to 16. Tear off the conductors away from the red stripe that marks pin 1. The '''crimp tools''' are common: https://www.amazon.com/Accessories-Crimp-Ribbon-Cable-Connectors/dp/B007R2JEM4/ [[File:RibbonCrimp.png|none|link=]] '''IDC Sockets 16-pin '''(pin pitch 0.1 inch) https://www.digikey.com/product-detail/en/assmann-wsw-components/AWP-16-7240-T/HHKC16H-ND/5031953 Assman Part number AWP 16-7240-T
[[File:16pinIDC.png|none|link=]]
https://www.digikey.com/product-detail/en/assmann-wsw-components/AWP-26-7240-T/HHKC26H-ND/5011313
[[File:26pinIDC.png|none|link=]]

====KFLOP KStep JR1 Molex Power Connectors====
KFLOP and KStep JR1 are standard Disk Drive Power Connectors. Possibly one of the most common connectors. Originally used on PC ATX Power Supplies. Sometimes referred to as Molex Connectors. They have 4 pins with 0.2 inch pitch with 0.083~0.084 inch socket pins. The mating cable will have female socket pins as shown here:

[[File:Molex_female_connector.jpg|none|link=|251x168px]]

Molex Series 8981 P# [https://www.digikey.com/short/zjp329 0015244048] using Molex Series 8980 Crimp Pins P# [https://www.digikey.com/short/zjp3ff 0002081201]

Also AMP Series MATE-N-LOK P# [https://www.digikey.com/short/zjpq3n 1-480424-0] using AMP Series MATE-N-LOK Crimp Pins P# [https://www.digikey.com/short/zjpqqw 60619-1]

====MPG Wiring and Interface====
MPGs (Manual Pulse Generators) should be connected directly to KFLOP for guaranteed real-time response (not USB based or connected to the PC). MPGs are handled by a C Program that monitors the MPG and creates motion based on the MPG Encoder changes and switch selections for axis, speed, and so forth. See the MPG C Program Examples. Here is a Discussion with other links.

[https://www.dynomotion.com/forum/archive/Jogging%20Pendant.html Jogging Pendant]

[https://www.dynomotion.com/forum/archive/Connecting%20Keling%20MPG2%20pendant.html Connecting Keling MPG2 Pendant]

[https://www.cnczone.com/forums/dynomotion-kflop-kanalog/349740-applying-acceleration-mpg-target-possible.html#post2119732 CNCZone Thread] on obtaining smooth filtered motion.

[[File:MPG4_from_cnc4pc.jpg|none|link=|83x169px]]

====Interfacing NPN Devices to KFLOP IO====
NPN devices (open collector)operate as a switch to GND and can be interfaced to KFLOP using a pull up resistor as shown below. When the transistor switches to 0V the KFLOP IO Pin is driven low. The transistor will need to sink ~3ma. When the transistor is off (open circuit) the resistor pulls the IO Pin to 3.3V. Note even though some KFLOP IO Pins can tolerate 5V pulling them above 3.8V should be avoided when possible so the 3.3V supply is used. This technique will only work with KFLOP IO Pins that do not have pull down resistors (JP7 and JP5). In some cases a 0.1uF Ceramic capacitor connected close to KFLOP might be added in parallel with the resistor to filter noise. Cable shielding connected to KFLOP GND on the KFLOP end only is recommended. Note that in noisy environments this technique may couple noise into KFLOP so opto isolation should be used instead.

[[File:NPN_Interface_to_KFLOP.png|none|link=|544x544px]]

====Multiplexing Encoder Inputs to KFLOP JP4 and JP6====
If KFLOP JP7 and JP5 are used for other purposes the encoder inputs can be multiplexed to KFLOP JP4 and JP6. There is an option to multiplex encoders 0-3 from JP7 to JP4 and another option to multiplex encoders 4-7 from JP5 to JP6. See the MuxEncoders.c for an example.

Note the JP4 and JP6 IO are 3.3V inputs and shouldn't be driven hard (more than 10ma) above 3.8V. This is not usually an issue as most encoders or RS422 drivers don't do this. The inputs also have 150 ohm termination.

The following line of code might be added to your Initialization C Program. It needs to be executed once to multiplex the encoders after any power cycle. Encoders 0-3 will then be input on JP4 and 4-7 will be on JP6. Both JP4 and Jp6 have 10 IO bits. The 4 encoders will appear on the first 8 IO bits. 2 bits for each encoder's A B channels in order. So for example Encoder #0 will appear on JP4 IO16 (Pin5) and IO17 (Pin6)

<pre class="brush:c">
// Mux encoder inputs from KFLOP JP7 & JP5 to JP4 and JP6
FPGAW(ENC_NOISE_FILTER_ADD) = ENC_0_3_JP4 + ENC_4_7_JP6 + ENC_NOISE_FILTER_DEFAULT_VAL; </pre>

JP4 and JP6 have +5V available on Pin1 and GND on Pins 8 and 9 that might be used to power 5V encoders.

==Axes Servo Tuning and Trajectory Planner==
===Basic Servo Tuning Overview===
Once an axis is configured and proved capable of holding a position it is ready to be tuned and optimized. Most often a small value of P Gain only is used to show the servo is functional and can hold position. The Servo may be very weak and inaccurate but will be functional.

Every system is different and the tuning parameters are interactive in a manner that usually doesn't allow parameters to be determined one at a time. Rather after one parameter is changed it may be necessary to revisit the other parameters.

In general higher gains will reduce errors and improve accuracy, but tend to make the system more unstable. So the general idea is to increase gains to reduce errors as much as possible but still have a stable system.

Often during tuning the system may go unstable. In fact, it is normally intentionally driven to instability to find its limits for a certain parameter. This can result in a violent oscillation or worse so one should be prepared to quickly disable the Servo. If an appropriate [http://dynomotion.com/Help/ConfigurationScreen/ConfigurationScreen.htm#Max_Following_Error Max Following Error] is used the axis can be automatically disabled before the oscillation becomes too violent, yet not disable when performing a normal test.

KMotion.exe allows you to change any axis parameter on the Step/Response, Config, or Filters Screens then simply push "Move" to see the effect of the change. Note that as performance improves the errors will become small and difficult to see on the Position Plot without Zooming in (Left click drag) so changing the plot type to plot the error is useful.

The overall process normally goes something like this:

# Select a Test [http://dynomotion.com/Help/StepScreen/StepScreen.htm#Measurement Move Size] and [http://dynomotion.com/Help/StepScreen/StepScreen.htm#Motion_Profile Motion Profile]. [http://www.dynomotion.com/wiki/index.php?title=Main_Page#Velocity.2C_Acceleration.2C_and_Jerk See Also]
# Select [http://dynomotion.com/Help/StepScreen/StepScreen.htm#max_limits Max Limits] to allow for the Test. [http://www.dynomotion.com/wiki/index.php?title=Main_Page#Max_Limits_-_Error See Also]
# Determine maximum level of [http://dynomotion.com/Help/StepScreen/StepScreen.htm#PID P Gain]
# Determine maximum level of [http://dynomotion.com/Help/StepScreen/StepScreen.htm#PID D Gain] (with Low Pass Filtering) See Also [http://www.dynomotion.com/wiki/index.php?title=Main_Page#Torque_Servos_vs_Velocity_Servos here] and [http://www.dynomotion.com/wiki/index.php?title=Main_Page#Lead_Compensator_vs_Derivative_Gain here].
# Determine new maximum level of P Gain now that D Gain increased stability
# Add I Gain to improve accuracy and remove steady state errors. [http://www.dynomotion.com/wiki/index.php?title=Main_Page#I_Gain.2FMax_Limit_Integrator See Also]
# Add [http://dynomotion.com/Help/StepScreen/StepScreen.htm#Feed_Forward Feed Forward] to reduce errors

===Torque Servos vs Velocity Servos===
+/-10V Analog Amplifiers usually come in one of two varieties: '''Torque''' or '''Velocity'''. Torque mode amplifiers consider the input command as a Torque Command and work to generate the commanded Motor Torque. Velocity mode amplifiers consider the input command as a Velocity Command and work to generate the commanded Velocity. Its important to understand what type of Amplifiers you have.

'''Velocity Mode Amplifiers''' need some form of feedback going to the Amplifier in order for the drive to know the current velocity. This might be a digital encoder or an analog tachometer.

Its easy to tell if you have a Velocity Mode Amplifier by looking at a plot of a move on the Step Response Screen. The Output (green plot with right scale) will be proportion to the motor velocity. When moving at constant speed the output will be relatively constant. See in the plot below the output (green) remains at a relatively constant ~1100 DAC counts while the position (red) ramps at a constant slope of the 90000 count/sec rate:

[[File:VelocityAmp.png|none|link=]]

Velocity mode amplifiers can be relatively easy to tune using only P (Proportional) Gain. Additional Gains and filters can be used for best performance but using only P Gain will often result in reasonable performance and a stable system (unlike Torque Mode Amplifiers).

As an example consider controlling the speed of a car using only Proportional Gain as it approaches a target (Stop sign). Consider a P Gain of 0.1 where at 1000ft from the stop sign we command 1000 x 0.1 = 100MPH. Then at 100ft we command 10MPH. Then at 10ft we command 1MPH. This results in a nice, smooth, exponential approach, without overshoot.

Contrast this with controlling the acceleration (torque) of a car using only Proportional Gain as it approaches a target (Stop sign). At large distance we apply maximum acceleration. Although as we approach the stop sign we reduce acceleration, we continue to accelerate and speed continues to increase until we pass the stop sign. Torque mode servos are inherently unstable. P only gain only works at all if there is some friction (the car is dragging a sled which slows us down with less torque).

'''Acceleration Mode Servos''' may or may not have any feedback. If they have feedback it is usually used only to commutate a brushless motor. In the plots the Output (green) will have large magnitude when the Position (red) is accelerating, where the plot has curvature (changing slope).

Acceleration mode Servos are unlikely to work well or at all with only P Gain. Some form of damping or lead compensation will usually be required to get a stable system. D (derivative) Gain (or a lead compensator) should be included with the P Gain to help stabilize the system. D Gain can be increased to make the system more stable up to a point. After some point the additional D Gain will make the system more unstable. and should be reduced.

When using D Gain (or lead compensation) the quantization noise (steps) in the encoder position can cause spikes in the output. For example a D Gain of 100 will cause a spike of 100 counts in the output whenever the input changes suddenly by 1 count. If the spikes are very high amplitude and short duration, the Amplifier may not handle them in the expected manner. A low pass filter can be used to widen and reduce their amplitude allowing the amplifier to handle them more effectively. Typically a 2nd order low pass filter of 500Hz Q=1.4 is used. The last filter is normally used so it is applied to any Feed Forward. Such as:

[[File:LowPass400Q1p4.png|none|link=|680x439px]]

===Velocity, Acceleration, and Jerk===
<div id="yui_3_16_0_1_1445622719616_3315" class="yiv2818182665class" style="color: #000000; font-size: 13.3333px; font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif; background-color: transparent; font-style: normal;">The Velocity, Acceleration, and Jerk in the Step Response Screen (KFLOP parameter settings) and the Acceleration and Velocity in the KMotionCNC | Tool Setup | Trajectory Planner | Axis Parameters are both used for different things. The two sets of parameters are independent. </div>
<div id="yui_3_16_0_1_1445622719616_3313" class="yiv2818182665class" style="color: #000000; font-size: 13.3333px; font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif; background-color: transparent; font-style: normal;"> </div>
<div class="yiv2818182665class" style="color: #000000; font-size: 13.3333px; font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif; background-color: transparent; font-style: normal;">The KFLOP parameters are used for 3rd order motions. These include things like: Jogging, Homing, and GCode Rapids (G0). The units in KFLOP are in counts or steps. The KMotionCNC parameters are used for 2nd order (infinite Jerk) coordinated motion paths. These are GCode G1,G2,G3 continuous paths. The units are in Inches (or in some cases degrees). Note there is an Option in KMotionCNC "Rapids as Feeds" where these parameters will also be used for Rapids. But this option should only be used for highly non-linear Kinematic Systems which can not take advantage of faster/smoother 3rd order point to point straight line Rapids. </div>
<div class="yiv2818182665class" style="color: #000000; font-size: 13.3333px; font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif; background-color: transparent; font-style: normal;"></div>
<div class="yiv2818182665class" style="color: #000000; font-size: 13.3333px; font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif; background-color: transparent; font-style: normal;">Tests to find and verify optimal settings for both types of moves should be made using the Step Response Screen. Optimal settings are usually determined by experimentation. Although it might be possible to calculate the settings based on motor torque gains, back-emf, amplifier voltage/current, mass, moments of inertia, friction, encoder resolution, leadscrew pitch, required following accuracy, etc... It is often too complicated and with too many unknowns to be practical. So experimental moves can be tested at ever increasing Velocities, Accelerations, and Jerks until the system is unable to follow the trajectory without having too much error or shock to the system. After absolute limits of the system are determined then the settings should be backed off by some amount to provide operating margins (ie 20%). </div>
<div class="yiv2818182665class" style="color: #000000; font-size: 13.3333px; font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif; background-color: transparent; font-style: normal;">It is usually best to first determine max possible velocity using a relatively low acceleration. Maximum power is usually required at the point of the trajectory where velocity is high and still accelerating. Supply Voltage limitations tend to limit velocity. Current limitations tend to limit acceleration. </div>
<div class="yiv2818182665class" style="color: #000000; font-size: 13.3333px; font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif; background-color: transparent; font-style: normal;"></div>
<div class="yiv2818182665class" style="color: #000000; font-size: 13.3333px; font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif; background-color: transparent; font-style: normal;">[[File:MaxVelAccelPower.png|none|link=|485x361px]] The Step Response Screen always performs 3rd order motion but 2nd order motion can be simulated by temporarily setting the Jerk to a huge value (1000X the acceleration value). In general reducing the Jerk value will result in longer times to perform motions, but often the improved smoothness will permit higher maximum accelerations and velocities to be used resulting in overall shorter motion times. An analogy might be how you might stop more quickly in a car, without skidding or spilling your coffee, by applying the brakes harder in a more gradual manner rather than slamming on the brakes. Make sure when testing the size of move is long enough for full acceleration and velocity are achieved. A common mistake is to have Acceleration or Velocity Settings set to too high for your system but when testing a short move there is no indication of a problem. The plot mode of Velocity Output vs Time can be helpful to verify full Velocity is being achieved. </div>
<div class="yiv2818182665class" style="color: #000000; font-size: 13.3333px; font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif; background-color: transparent; font-style: normal;"></div>
<div class="yiv2818182665class" style="color: #000000; font-size: 13.3333px; font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif; background-color: transparent; font-style: normal;">The idea is that a motor axis has torque and speed limitations and you should determine and understand what they both are for your system. Available motor torque drops off with higher speed. At some speed the motor will not even be able to generate any torque at all. Motor torque is required to accelerate the axis. We need to make sure that no combination of velocity and acceleration will ever cause the axis to fault/stall/fail. So there is often a complex set of speeds and accelerations that will work ok that form an envelope of workable speed and acceleration. So one nice thing to know is top speed possible. It is like taking your car out on a long straight highway and gradually accelerating to find the max speed is 100MPH. You will then know that ever attempting a speed over 100MPH will always fail. Also speed should probably be limited to something like 80MPH to allow for margin and to allow reasonable acceleration up to that speed. The reason for performing the top speed test at low acceleration is to avoid a failure because of not being able to accelerate at the specified rate. So we want to set the acceleration to a low value so it will not be a limiting factor when determining top speed. However if we set the acceleration so low with a short trip distance we will never go very fast and the speed test will be meaningless. This should be avoided. Change the Plot type to Velocity, Output, vs Time to clearly see if this is the case. You may want to turn off Measured Velocity if it obscures viewing the Commanded Velocity For example to accelerate to 700,000 counts/sec at an acceleration rate of 700,000 counts/sec^2 would take 1 second. And then to slow back down would take 1 more second. So at least 2 seconds of motion would be required to get to full speed. A 100,000 count move (2 inches for a system with 50,000 counts/inch) takes much less time than that. Furthermore with a relatively low Jerk setting (1e6). This means the acceleration will be applied gradually over 0.7 seconds. This means an even much longer time and distance would be required to achieve top speed. Here is the method to follow to find 2nd/3rd order motion profile limits: (note every system is different and will vary based on resolution, motor size/type, mass, etc...)

'''1 - Find Max Velocity at low Acceleration and infinite Jerk'''

Choose a Velocity to test (ie V=100000 counts/sec) Set a moderately low Acceleration Time of 1 second (A = V/1sec = 100000 counts/sec^2) Set very high Jerk so Acceleration is applied almost instantaneously in 0.001 sec (J = A/0.001sec = 1e8 counst/sec^3) Test a very long move 20 inches if possible (for resolution 50000 counts/inch, 1,000,000 counts) Plot Velocity, Output, vs time to see if V is actually obtained If the motion was successful repeat all above with higher V, if not try lower V Once Max V is found reduce by some margin (ie 20-50%) Note you may decide on lower speed for other reasons (safety, vibration, noise, wobble, shock, etc....) '''2 - Find Max Acceleration for your system for the chosen Velocity'''

Using the V found above increase A (keeping Jerk high in the same manner) until the system fails/faults/excessive shock, etc... Once Max A is found reduce by some margin (ie 20-50%) These V and A Values are now known good values for your system and can be used for 2nd order motions such as KMotionCNC Trajectory Planner or Mach3 Motor tuning. Note units will need to be converted (counts to inches or mm, time from seconds to minutes depending on the App)

'''3 - Find optimal 3rd order Jerk limited motions.'''

The previous result from Step #1 and #2 used nearly infinite Jerk where Acceleration forces were applied nearly instantaneously. By reducing Jerk smoother motion should be possible. Set Jerk so it is applied over 20ms (ie for A=200000 J = A/0.020 = 1e7 Test to see if motions are smoother. With closed loop systems the Position Error Plot can be used to see if the motion has less error and is smoother. Open loop system will require you to hear the difference. Increase/decrease Jerk to find the optimal value. Note reducing Jerk a lot will of course make the system very smooth, but will also be much slower using less acceleration and velocity which is undesirable. So the highest Jerk possible should be found that still provides some smoothness. Reducing Jerk only will always make the system slower with less performance (but hopefully significantly smoother). It is usually then possible to increase Acceleration and Velocity somewhat to achieve even higher performance than what was possible with infinite Jerk while being as smooth or smoother.

'''4 - Reduce Max Following Error Limit to small value'''

</div>
<div class="yiv2818182665class" style="color: #000000; font-size: 13.3333px; font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif; background-color: transparent; font-style: normal;">Now that the system is properly tuned and reasonable Acceleration, Velocity, and Jerk are set the motor Position should always follow the commanded Destinations accurately with only small errors. By Plotting Position Errors under various conditions (Distances) you can get an idea of the worst case following errors under normal conditions. The Max Following Error Parameter should be set to a value slightly larger than the worst case following error (ie 20~50% larger). In this case if anything abnormal occurs: ie. The axis hits an obstacle, commanded at too high of a speed, servo goes unstable, hardware/electronics failure, a Following Error will be immediately detected and the axes disabled.</div>
<div class="yiv2818182665class" style="color: #000000; font-size: 13.3333px; font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif; background-color: transparent; font-style: normal;"></div>
===Axis Resolution - counts/inch (or counts/mm)===
<div class="yiv2818182665class" style="color: #000000; font-size: 13.3333px; font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif; background-color: transparent; font-style: normal;"></div>
<div class="yiv2818182665class" style="color: #000000; font-size: 13.3333px; font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif; background-color: transparent; font-style: normal;">Its important to understand the resolution of your Axis which is the number of fundamental raw motor/driver encoder counts or motor steps per standard unit of distance (inch or mm). Although tuning in KMotion.exe Step Response Screen and motions within KFLOP typically use units of raw counts or steps it is important to know how these translate to real-world distances, speeds, etc... Later, applications such as KMotionCNC or Mach3 will need this information to scale motions properly. </div>
<div class="yiv2818182665class" style="color: #000000; font-size: 13.3333px; font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif; background-color: transparent; font-style: normal;"></div>
<div class="yiv2818182665class" style="color: #000000; font-size: 13.3333px; font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif; background-color: transparent; font-style: normal;">There are usually a number of factors that combine together to determine the Axis Resolution. These might include:</div>
* counts or steps per motor revolution
* any gearing or belts and pulleys involved between motor and drive mechanisms
* lead screw pitch, rack and pinion tooth pitch, drive belt radius, etc.

For example consider a Stepper Drive with:

3200 steps per motor rev

2:1 gear reduction from motor to lead screw

0.2 inch lead screw pitch

Axis Resolution = 3200 step/motor rev x (2 motor rev/ screw rev) / (0.2 inch / screw rev) = 32000 steps/inch

To determine whether your assumptions and calculations are correct perform a test. Command as large of a move as convenient and measure the actual distance moved with a ruler. For example in the axis described above you might command a move of 320000 steps. This should result in a motion of:

320000 steps / (32000 steps/inch) = 10 inches.

For KMotionCNC set the Axis Resolution in the [http://dynomotion.com/Help/KMotionCNC/ToolSetupScreenTP.htm#Axis_Motion_Parameters Tool Setup | Trajectory Planner Screen | Axis Parameters | cnts/inch]. Note units must be in units of inches. If your resolution is in mm units multiply by 25.4.

For Mach3 enter the Axis Resolution in the Configuration | Motor Tuning Screen. Make sure the setup units (not GCode units) match the mode of your values.

===Servo Dither/Hunting - (oscillation around zero error)===
<div class="yiv2818182665class" style="color: #000000; font-size: 13.3333px; font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif; background-color: transparent; font-style: normal;"></div>
<div class="yiv2818182665class" style="color: #000000; font-size: 13.3333px; font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif; background-color: transparent; font-style: normal;">Servos have high accuracy because they are always actively trying to make corrections and drive the error to zero. Unfortunately this can sometimes cause annoying dither or position hunting around zero when not moving. This is a very complex non-linear effect dependent on the dynamics of the mechanics. Because of the highly non-linear quantization effects of single "steps" in the encoder position, stiction, backlash, etc. it follows different rules and is harder to analyze than normal servo tuning/stability in the larger magnitude more linear regime. For example attempting to apply "Damping" is unlikely to work. Lowering gains will usually help at the expense of performance. However in many cases more than acceptable performance can be achieved with lower gains so one should consider if the higher gains are really needed. KFLOP has a Deadband Gain and Range feature that can basically be used to tell the servo to not attempt to correct small errors (treat the errors as zero), or to try to correct them less aggressively (with a Gain less than 1.0). See [http://dynomotion.com/Help/StepScreen/StepScreen.htm#Dead_Band here for more information] Unfortunately adding Deadband doesn't always help the servo "sit still" and may actually increase the size of the dither depending on the dynamics.
 Note that when the servo is commanded to a non integer position ie 999999.7 encoder counts without deadband the servo will always be making corrections. The best the servo can do is dither between encoder positions 999999.0 and 1000000.0. With an error of either -0.7 or +0.3. A servo with Integrator gain will guarantee the average is 999999.7 If dither is still a major problem a C Program might be used to monitor things and change settings under certain conditions to reduce dither. See the example AntiServoDither__ALL.c which monitors for small errors for a period of time and if so reduces or turns off Integrator gain. 

</div>
===Noisy GCode - Trajectory Planner Smoothing===
<div class="yiv2818182665class" style="color: #000000; font-size: 13.3333px; font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif; background-color: transparent; font-style: normal;">An analysis of Quantization Noise in GCode and Trajectory Planner Settings to generate smooth motion. [[File:GCode_Noisy_Path.png|none|link=|432x432px]]</div>
<div class="yiv2818182665class" style="color: #000000; font-size: 13.3333px; font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif; background-color: transparent; font-style: normal;">[[Trajectory Planner Smoothing Noisy GCode|See Analysis and Solution]]</div>
<div class="yiv2818182665class" style="color: #000000; font-size: 13.3333px; font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif; background-color: transparent; font-style: normal;"></div>
===Arc "faceting" - Trajectory Planner - Collinear Tolerance===
<div class="yiv2818182665class" style="color: #000000; font-size: 13.3333px; font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif; background-color: transparent; font-style: normal;"></div>
<div class="yiv2818182665class" style="color: #000000; font-size: 13.3333px; font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif; background-color: transparent; font-style: normal;">[[File:ArcsTrajectoryZoomXTol.0005.png|none|link=|526x460px]]</div>
<div class="yiv2818182665class" style="color: #000000; font-size: 13.3333px; font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif; background-color: transparent; font-style: normal;"></div>
<div class="yiv2818182665class" style="color: #000000; font-size: 13.3333px; font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif; background-color: transparent; font-style: normal;">[[ArcFacetingColinearTol|See Analysis and Solution]]</div>
<div class="yiv2818182665class" style="color: #000000; font-size: 13.3333px; font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif; background-color: transparent; font-style: normal;"></div>
===I Gain/Max Limit Integrator===
I (Integrator) Gain can be used to eliminate persistent errors. In fact any Integrator Gain at all guarantees the average error over infinite time is zero. Without I Gain a system might have a small error that does not create enough output to overcome stiction to make a correction. In such a case the error could persist forever. Not so with any Integrator Gain. Any error will be integrated and ramp the output higher and higher until eventually there will be a correction. That assumes the Integrator or Output doesn't saturate or reach their programmed limits. The rate the output ramps (or sums) is dependent on the size of the error and the I Gain value. The Error x I Gain is summed every servo sample (90us). This is why I Gain values are often small numbers (0.0001 - 0.01 typical range). There is no guarantee that the position doesn't over shoot the target Destination. In fact it is likely as as any error (area) under the trajectory will always be balanced by an equal area over the trajectory. Too high of I Gain will make the system unstable.

Another case where I Gain is useful is when moving at high speed with a Velocity Amplifier. To move at high speed a significant amount of output is required. Without I Gain a significant amount of error could be required to provide this Output (ie Error x P Gain = Output). With I Gain the Integrator will eventually ramp up to provide any Output necessary to move at the desired speed driving the error to zero.

Integrators have an issue often referred to as "Integrator Wind Up". This issue usually doesn't arise under normal conditions. However if something is preventing the servo from making a correction such as forcing the position away from the target for a sustained amount of time, or disabling the amplifier, the Integrator will integrate to a huge unlimited value. When the force is removed or amplifier re-enabled, the Integrator will likely cause a violent motion and overshoot. Max Limit Integrator can help to minimize this issue by limiting the amount the Integrator can ramp up to. So the Max Limit Integrator Value should be set at the minimum value that can still allow the Integrator to function in normal circumstances.

Typically there are two cases that should be considered when determining the Max Limit Integrator.

# The amount of output expected to be required to overcome any stiction, friction, or other forces (cutting, gravity, etc...). This is often not a large value and can be estimated or can be observed from the Step Response Screen (green plot right side scale is the output) when making a move.
# The amount of output required to provide the output needed to move at speed. It is important to note that D Gain provides a damping or drag effect on the Output. So the Integrator must be able to ramp up to a sufficient level to overcome the damping or drag effect and still provide enough output to move at the commanded speed. For example:

Assume:

# Commanded speed of 500,000 counts/sec
# D Gain of 35
# Output required to move at speed is 1800 DAC Counts
# Servo Sample Time of 90us

Damping effect = Speed x D Gain x Sample Time = 500000 x 35 x 90e-6 = 1575 counts

Required Integrator Value = 1800 + 1575 = 3375

So to provide some margin an Max Limit Integrator Value of 3500 might be used.

===Max Limits - Error===
Max limits error can be helpful to have your system respond less violently in the abnormal event where an excessively large error occurs. Normally with a properly tuned system following errors should be small. Setting a Max limits error can cause the servo to treat errors beyond a specified limit as if they were only the size of the limit and therefore respond less so than they would otherwise. The max limits error is normally set to a value so it is not limiting under normal circumstances.

The Plot below shows a situation where a small max limits error combined with a low P gain severely limits the Output. In the plot below a large move (10000 counts) at a high speed (40000 counts/sec) is commanded. Only P Gain (0.2) is used to provide the Output (green). The max error limit of 200 combined with the low gain (0.2) limits the output to only 40 DAC counts. Even as the true error increases to many thousands of counts, the servo is told to ignore the amount over 200. So the output can never exceed 40 DAC counts. The 40 DAC count limit means that the Axis is therefor not capable of providing the output necessary to keep up with the commanded motion. The axis does the best it can with the limited output, and only does a fraction of the desired motion.

[[File:Move10000.png|none|link=|665x431px]]

After increasing the max limits error the Output (green - right scale) now goes to a much higher value (900), and the Position (red) follows the Command (blue) to a much better degree.

[[File:Move10000_nolimit.png|none|link=|667x430px]]

Increasing the P Gain to 1.6 also applies more Output sooner and the Position follows the command still better.

[[File:Move1000_p1.6.png|none|link=|667x432px]]

===Lead Compensator vs Derivative Gain===
Derivative (D) Gain is often used to help stabilize a system.  It helps to think in the Frequency Domain to help understand how the two forms of compensation help.  Please read below and [http://dynomotion.com/Help/BodeScreen/BodeScreen.htm this] for more information on the Frequency Domain.  Both Compensation methods add positive phase to help stabilize the system.  Unfortunately both methods increase gain at higher frequencies possibly causing the system to go unstable at higher frequency.  A Lead Compensator provides the benefit of positive phase but without as much gain increase at higher frequencies.  This figure shows a simplified Gain Plot comparison:

[[File:DGainvsLead.png|none|link=|593x593px]]

Here is a Bode Plot of a P=0.5 D=20 Compensator. Note the KMotion.exe Bode Plot Screen has the capability of plotting the Frequency Domain Response of the PID+Filters Compensation. Assume we desire positive phase to be added at 40Hz. Notice the positive phase of 40 degrees at 40Hz which is good. However the Gain increase in the 1KHz region of about 21db which is bad.

[[File:P.5D20Annotate.png|none|link=|621x460px]]

Here is a Bode Plot of a P=0.5 N1=N2=25Hz D1=D2=70Hz Compensator. Assume we desire positive phase to be added at 40Hz. We choose N1 N2 and D1 D2 to surround the frequency where the positive phase is desired. Moving them further apart will increase the amount of positive phase but also increase the added Gain. Notice the positive phase of 60 degrees at 40Hz which is good. However the Gain increase in the 1KHz region of about 12db which is bad. However both are improvements over the D Gain compensator.

[[File:PoleZeroFilter.png|none|link=|210x319px]]

[[File:P.5D0N25D70Annotate.png|none|link=|644x478px]]

===Tuning Master/Slave Configurations===
Master/Slave [http://dynomotion.com/Help/ConfigurationScreen/ConfigurationScreen.htm#Master/Slave_Settings Configurations] allow two (or more) motors to drive the same axis. Slaves are configured to follow a Master Axis. For example two lead screws on both sides of a gantry.

Tuning slaved axes is kind of a catch 22. In order to tune one axis the other axis must be tuned well enough to follow and vice versa. If possible, disconnect any mechanical linkage between the Master and Slave and test them separately without Slaving the Axes together to verify each axis Servos (can hold a position), moves at least somewhat properly, and moves in the same direction (assuming a positive [http://dynomotion.com/Help/ConfigurationScreen/ConfigurationScreen.htm#Master/Slave_Settings Slave Gain] will be used).

It is usually possible to incrementally tune each axis, at first moving slowly, then later at higher speeds, accelerations, and gains. Only the Master Axis can be tested with the [http://dynomotion.com/Help/StepScreen/StepScreen.htm Step Response Screen]. This is because the Slave will follow any movement of the Master, but the Master will not follow movement of the Slave. So if the Master Axis is moved all is well as both axes will move together, but if you try to move the Slave axis the two axes will fight. The Master fighting to stay where it is, and the Slave fighting to move.

To test/tune the Slave axis temporarily reverse the Master/Slave roles to make it the Master and then test it as the Master.

Note: only the Master Axis should be included into the Coordinated Motion System.

===Bode Plots===
A Bode Plot is a powerful tool for characterizing and providing insight into a dynamic system. It can help determine closed loop stability, bandwidth/performance, resonant frequencies, and more. It is entirely based on the system being linear. Linear in the sense that if the amplitude of some input signal is changed then the output signal will change proportionally as well. Unfortunately most systems are not entirely linear. Stiction, backlash, encoder quantization, amplifier saturation, and other effects are non-linear. For example driving a system with a signal too small to overcome stiction will result in no output at all whereas a larger signal will result in some output. This is clearly non-linear behavior. It would be nice to use a technique that handles non-linear systems but basically none are known. A Bode Plot is made injecting a stimulus to the system and observing how the system responds. For the reasons of non-linearity it is very important to perform a Bode Plot measurement using a representative level of stimulus similar to what the system will actually have during normal operation. If the Stimulus is not adjusted properly the result is likely to be completely invalid. Additionally the system should be reasonably tuned and stable so that it is responding in a reasonable way to the stimulus. If the system is unstable or very poorly tuned the result is likely to be completely invalid. You might think of it somewhat like shaking a box to determine what is in it. You should shake it with enough intensity and at frequencies to get some reaction, but not so high of intensity to break or distort the object inside. To create a Bode Plot use the KMotion.exe Bode Plot Screen. First select Plot: Time domain - Command, Position, Output vs Time and adjust the Amplitude and cutoff Freq until there is small but significant Position (red) changes (ie 50 encoder counts), at a frequency low enough that the Position at least somewhat attempts to follow the Command (blue), and where the Output (green) is not near saturation for the Drive being used. After the Stimulus/Noise Injection settings are set switch to Plot: Open Loop - Magnitude and Phase vs Frequency. Set the number of Samples to average (ie 20) and perform a Measurement.  [http://dynomotion.com/Help/BodeScreen/BodeScreen.htm See here for more information].

===Links to other Information on Tuning and Bode Plots===
[http://ctms.engin.umich.edu/CTMS/index.php?example=Introduction&section=ControlFrequency umich.edu Introduction section Control Frequency]

[http://www.motiontech.com.au/assets/pdf/Kollmorgen%20Use%20Control%20Theory%20to%20Improve%20Servo%20Performance%20230712.pdf Kollmorgen Use Control Theory to Improve Servo Performance 230712.pdf]

==Problems and Resolutions==
====General====
:* [[Noise - Typical Problems and Resolutions|Dealing with noise on inputs]]. If you experience issues with inputs misreading, the issue may be noise. This page provides examples on what might be causing noise issues and examples of how to possibly deal with noise.
:* Other
===Software-Specific Problems and Resolutions===
:* Place links to pages explaining resolutions to problems that are largely software-related here
[[KFLOP User C Programs Compiling/Launching Slowly because of Windows Defender]]

===Hardware-Specific Problems and Resolutions===
:* Place links to pages explaining resolutions to problems that are largely hardware-related
====[[Step/Dir Drives lose 2 Steps for each pair of Direction Reversals]]====

==Applications and Projects==
:* Place links to pages that explain how you accomplished your particular project. Write clear explanations that provide background on what you did and how you did it.
====[[Tool Changer - router linear 4 Tools - C Program]]====
[[File:LINEAT+ATC.jpg|none|link=|246x178px]]
More linear milling tools: https://www.ichome.com/

====[[Part Zero & Tool Height Touch Plate|Part Zero & Tool Height Touch Plate]]====
====[[Driving Hobby Servos]]====
[[File:HobbyServo.png|left|link=]]

HiTec Type

==Electrical Discharge Machining==
[https://en.wikipedia.org/wiki/Electrical_discharge_machining EDM (wikipedia)] is a method of cutting materials with high precision and detail. Dynomotion Motion Controllers work well for EDM because of the ability for feedrate to be dynamically controlled including reversal along cutting path.

[[Information on BAXEDM Arc Generators used with KFLOP]]

Applied Science video that shows how to build an BAXEDM drilling machine using KFLOP and describes how it works:

{{#ev:youtube|https://youtu.be/rpHYBz7ToII|||||start=980}}

==How to convert a milling machine to a 3D printer in 3 easy steps==
[[File:CNCto3DPrinter.png|none|link=]]

More information [[How to convert a milling machine to a 3D printer in 3 easy steps|here]].

==International and other Languages==
[[Russian]]

[[Spanish]]

File:KStep Terminals.dwg

2024-03-02T00:43:39Z

TK:

File:KStep Terminals.dxf

2024-03-02T00:43:16Z

TK:

File:Konnect Terminals.dwg

2024-03-02T00:42:37Z

TK:

File:Konnect Terminals.dxf

2024-03-02T00:42:05Z

TK:

File:Kanalog Terminals.dwg

2024-03-02T00:41:24Z

TK: