Back to top
Cause S-curve velocity ramp
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:
1. periodically enter a new velocity target, at specific intervals of time (setting the accleration limit above the highest that would exist in this profile)
2. Enter an acceleration limit of 0, then a step velocity command for the end target and then periodically enter a new acceleration limit.
or is there another way that this can be achieved?
Submitted by mark_uwp94 Sat, 06/06/2020 - 12:55
You didn't indicate what hardware model of AKD you have but the only S-Curve functionality built into the drive is using the Motion Profile Table in tandem with a motion task in the Motion Task table which requires an AKD-P drive in Service Position mode.
Velocity Mode requires the velocity command is given by the external controller or master.
Changing the velocity setpoint on the fly makes sense to me but keep in mind with Modbus TCP the X11 Service Port on the AKD is limited to a poll rate
down to 20msec. Anything faster will overrun the communications buffer. Therefore latency may affect your profile. A fieldbus option like EtherCAT or CANopen can achieve faster update rates.
Analog Velocity overcomes the communications latency but can add noise into the mix.
Submitted by toddevans01 Mon, 06/08/2020 - 07:07