From Dynomotion

Jump to: navigation, search

Main Page

3,808 bytes added, 17 October
/* ModBus */
==Dynomotion Software Topics==
===Installation Topics===
* Announcement of our Latest Test Release (V4.35a35b) on the [ 742 Dynomotion Forum]
* [ Latest Stable 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: 12/21/2018: [ KMotion.exe V4.35a], See the release notes for this test version here: [ V4.35a release notes (pdf)]
* Previous Test Release: 09/28/2017: [ KMotion.exe V4.34j], See the release notes for this test version here: [ V4.34j release notes (pdf)]
* Previous Test Release: 05/07/2017: [ KMotion.exe V4.34i], See the release notes for this test version here: [ V4.34i release notes (pdf)]
: '''General Information'''
: Compiling KMotionCNC
:: The KMotionCNC's Visual Studio Project Solution (\PC VC Programs\KMotionCNC\KMotionCNC.sln) is currently written for Visual Studio 2008 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 listed on the Yahoo Group Files Section (PDF format):: :* [ How to edit KMotionCNC faces]:* [ Adding external buttons]:* [https:/ here/ Adding more user buttons]:* [ Adding Jog Percent Cell to Main Dialog Face] 
====<span style="text-decoration: underline;">KMotionCNC Screen Editor</span>====
Introduces the capability of using Screen Script files to modify the look and function of KMotionCNC.<br />[[KMotionCNC Screen Editor|More information.]]
===PC Example Applications===
A number of PC Applications using the KMotion Libraries are available in the Software download.&nbsp; Visual Studio should be used to modify/compile the applications.&nbsp;
Currently the projects are compatible with VS 2008 Standard but later Versions can upgrade the projects and can be used including the free Microsoft Version of VS 2013 Community.&nbsp; In some cases MFC capability needs to be added as a separate download.
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 [ free utility].:
[ Sending ModBus msgs from KmotionCNC to a RS485 port]
==Dynomotion Hardware Topics==
===General Hardware Information===
KFLOP ====[[KFLOP Hardware Info|KFLOP specific Hardware Info]]==== KStep ====[[KStep Hardware Info|KStep specific Hardware Info]]==== Kanalog ====[[Kanalog Hardware Info|Kanalog specific Hardware Info]]==== SnapAmp ====[[SnapAmp Info|SnapAmp specific Hardware Info]]==== Konnect ====[[Konnect Hardware Info|Konnect specific Hardware Info]] ====
===Wiring Diagrams===
[[|]] STEP and IGS models - Thanks to Chris
===Wiring Topics===
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.
[ Jogging Pendant]
[[Filehttps:MPG4_from_cnc4pc//www.jpg|none|link=|83x169px] Connecting Keling MPG2 Pendant]
[ CNCZone Thread] on obtaining smooth filtered motion.
====Interfacing NPN Devices to KFLOP IO====
====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
JP4 and JP6 have +5V available on Pin1 and GND on Pins 8 and 9 that might be used to power 5V encoders.
==<span id="Axes_Servo_Tuning_and_Trajectory_Planner" class="mw-headline">Axes Servo Tuning and Trajectory Planner</span>==
===Tuning Master/Slave Configurations===
Master/Slave [ 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 [ 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 [ 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.