Back to top

Hello,

I am having trouble with mapping telegram 400 of an AKD drive over profinet. 

Mapping of all "one word" parameters is fine, I am using examples from here - https://www.kollmorgen.com/en-us/developer-network/sample-projects-siemens-s7-1200-s7-1500-plcs-and-akd-profinet-drive/ but lets say I want to map fe. HOME.ACC - 2192 - DWord.. I tried many variants by changing example program, but I just cant get it to work. 

New features include TCP/IP Function Blocks, BBH FSoE Master + SafePLC with KAS-IDE and AKD2G w/ SMM, KAS IDE-WorkBench Improvements, new File Management functions, DriveParamStrRead, Multi-select PDO objects, new axis parameter to read PLCopen user units, and more!

I am commanding the AKD drive in velocity mode.  I would like to obtain an S-curve velocity profile.  The way the drive is controlled now is to command 0rpm and then 80 rpm to go that speed.  The standard motion creates some problems in control including overshoot.

I know how to compute the path by setting a Jerk value and laying out the acceleration and velocity profile.  My question is what could be a way to entice the drive to perform this.   It is being controlled via the Modbus commands over ethernet. I have two ideas:

WorkBench (version ≥ 2.2.2.4811) has some accessible parameters to tweak the way data are exchanged with the drive. Keywords sent to the drive and answers returned will be grouped together to build bigger packets of data. This is particularly helpful on networks with high latency. It is also useful for slowing down the polling interval to avoid overloading the communication channel on slower networks.

These parameters are accessible in the WorkBench configuration file, which is usually placed in the install directory:

Implementation of STO Inputs

There are two types of STO input in common use today:

  1. DC-DC Type: isolated STO input based on using a DC-DC converter to power the date driver circuitry. 
  2. O-C Type: opto-isolated input of a drive that acts upon the gate driver circuit.

Here is a simplified drawing of an O-C Type input:

image

This application note demonstrates configuration and addressing for Modbus TCP communications using a Trio Motion Controller to AKD1G.

The application notes is an example only and the implementation and verification of proper operation of the application and system is the programmer's responsibility

This application note demonstrates configuration and addressing for Modbus TCP communications a Automation Drive HMI using their C-More Programming Software.

The application notes is an example only and the implementation and verification of proper operation of the application and system is the programmer's responsibility

This application note demonstrates configuration and addressing for Modbus TCP communications a Red Lion HMI using their Crimson 3.0 software.

The application notes is an example only and the implementation and verification of proper operation of the application and system is the programmer's responsibility.

 

Basic functionality was tested with hardware or learned over a Web meeting.

100% compatibility is not guaranteed.

Hello there!

How can i configure echo on the AKD servoamlifier?
On s300/s700 the PROMPT parameter helps me with it, but i can't find same parameter on AKD.
Can you help me with it, please?

This patameter important for me, because i track answer to sent command using echo.
Now AKD is giving only the prompt (-->) symbol for inputting data.
I can’t track which of the sent commands the answer is coming at the moment.

How do you track which of the sent commands the answer is coming at the moment?

Thank you!

Pages