Dear Osmanmom
Much of this Motion Control system I understand. Just like I understand how a Tesla Coil works from looking at a schematic of a Tesla Coil. Problem is, you can't build a Tesla Coil, just from looking at a schematic. The schematic isn't enough information for "construction".
Yet, If given a diagram of how all the components of a home entertainment system go together, showing the DVD player, and the Television, connected to the amplifier, DVR and speakers .. the average person probably could get it working ... just from the diagram.
So now I have a HMI, a Siemens PLC (both interconnect with ethernet/profibus). I have two types of driver/controllers for the LinMot linear motor. They are both PID drivers.
One, is Profibus connectable, and the other is intended to receive digital I/O. Both are capable of storing the "curves" that I would want the actuator to run. The PLC need only to tell the driver which curve, and when to run it.
I also have a "dumb" driver/controller from LinMot .. It does not generate stored curves... it is only intended to follow a signal on an analog input .. which is provided by a Motion Controller. The Motion Controller creates the curves "on the fly" .. they're just sine waves after all …
The Motion Controller also uses the feedback from the actuator for tuning.
Knowing how these components of linear motion control go together, isn't enough information to make them function together.
I presently have a working LinMot system functioning quite well ..under the control of a PC, using LinMot's configuration software "TALK-6"
The PLC is not connected yet. In theory, the PC is emulating the PLC to do this "configuration" of the Driver. At least the I/O's can manually be entered by the PC... and the Driver/actuator responds with the desired curve. All this works Great!
LinMot has generated several publications which aid in the programing of their Driver/Controllers. They speak of "Control words", Status Words", "Warning words".. Parameters, Variables .. There are long tables of commands, which might be entered in the Driver's Motion Command Tables.
All of this is presented as though the reader already knows what the information is.. and more importantly, how it is used... The DETAILS, as it were, are not provided … there are no "explanations", or examples.. or tutorials to get one started on simple motion control without the PLC. Or perhaps a Motion Controller.
I'm kinda left with the sinking feeling that the next step for me, is writing code.. I never expected that. I expected something more user friendly. I just didn't know.
to be continued ... Regards, Michael