Quote Originally Posted by John S View Post
<snip>
I bought a K-Flop a while ago as having been told it can do lathe which it can IF you are able to program in C++

So it stands on the shelf with the rest of the very expensive components that promise the earth but never deliver.
Some very valid points regarding support.
One of the things I like about Dynomotion, is Tom (main man behind the company) is very responsive to any questions. Any bugs discovered are dealt with quickly. Only last week a bug was found in their new screen editor, and the fix was released today, which was actually pretty slow for them, but he had already posted a work around within a few hours, so a full fix wasn't urgent.
It's not unknown for him to release patches within a day to fix proven bugs.
.
Yes, they can be daunting to setup, but if you post up on the Yahoo group, or the cnczone forum, you'll get help. I've seen people with no programming background have their systems up and running within a couple days, which isn't bad by the time you factor in time for replies, and for the people to gather/post/test things.
.
For basic systems, the hardest part is the main configuration file (configures the KFlop with what axis outputs/inputs are needed), but there are sample files included, and for the axis configuration information, the KMotion configuration program can generate the required code for you to copy and paste in.
It's only when you want to start doing custom things that the C coding really kicks in, but there are plenty sample files included.
.
For a basic lathe, running Mach3, all you need is the main config file, with just the axis information for the two axis. Everything else can be handled in Mach 3. For KMotionCNC, with the new screen editor, simple things like flipping outputs with a button, can now be handled without having to write any C code.
However KFlops also suffer with the Mach3 slow pull out problem when threading. The problem is although Mach3 switches back from mm/rev to mm/min mode, it uses the mm/rev value as the mm/min value, so for a 2mm pitch thread, you get 2mm/min pull out, instead of the set federate.
KMotionCNC on the other hand doesn't. Provided you write the G-code correctly, it'll group together all the required synchronised moves, so you can pull out however you want.
Somebody posted an example not that long ago which involved a taper lead in to a parallel thread to a 45deg pullout.
The only requirement is you need a quadrature output encoder on the spindle. Single/multi-slot sensors won't work.
.
However, if you want to clear some shelf space, I'd buy the KFlop, as it can be handy having an extra one for testing.