:: Links to examples of projects that explain KMotionCNC customizations
::: Troy (tmday7) created some helpful documents listed on the Yahoo Group Files Section [https://groups.yahoo.com/neo/groups/DynoMotion/files/KmotionCNC%20Screen%20Customizing/ here].
===[[KMotionCNC Screen Editor]]===
'''Table of contents:''' # Introduction# Control styles# Control attributes# Main Window attributes# Bitmap types and Alpha and locations # '''Introduction<br /> <br /> ''' Video: [https://www.youtube.com/watch?v=l6d_AYTptVQ https://www.youtube.com/watch?v== ===l6d_AYTptVQ] '''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<br /><br />
===PC Example Applications===
<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>
===<span class="mw-headline">Axis Resolution - counts/inch (or counts/mm)</span>===
<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.