Dear Tom,

In the past I've used a KFlop to interface with a VB-program. Basically I got everyting to run. However, back then I already thought that the documentation was not too clear and very fragmented. It really took me quite a long time to get a sufficient amount of information together from all the links on the support page. Mainly with the use of the VB-examples and only with addtional info of a CNC-forum, I got things up and running. 

The main problem with the current information base is, that the links are sort of "pointers" on how you can find out things on your own. However, every link just half (or less) of the story. Links are either very dry descriptions of pins and connection, or they are "quick start" descriptions. Nowhere can I find a step by step descriptions of walkthroughs or detailed information on how to best connect the hardware and configure the software for a specific application. 

Anyway, I currently want to interface some linear AC servo motors and figured a Snapamp together with the second KFlop could probably do the job. Again, I found out how very limited the documentation (especially on the Snapamp) really is. There is just 3 links in the help function that are together contain nothing remotely near to a manual. I looks as if every item sort of stops half way. Say I would want to interface the Snapamp with a ac-servo and resolver. In the examples (not in the Snapamp section), I can find a resolver example, however, the example does not show a Snapamp but with a card called "KMotion". This is not a product mentioned in the product list. So, can I just use the same pins?? Unclear to me. 

Same problem with the software: "channels" for example. This is what the Dynomotion Wiki says about it: "Dynomotion loves the term Channels.  It is used everywhere and causes much confusion." That is because some channels are actually "axes" and others are actually "devices". So why not name them that way in the GUI and save everybody the confusion?

Basically my question is: why not save everybody (including yourself) a lot of time and frustration and write some good documentation to go with every card? I think the hardware deserves it. I also think that the user base of you cards could dramatically increase if concise and complete documentation became available. The way it is set up right now is really not professional at all.

Best regards, Jeroen