Unfortunately, The same behaviour still exist with SoftMotion V4.19.0.0 too.
(default ramp type is quadratic instead trapezoid for new created axis object)
For your information.
thanks for your feedback. This change was intentional, as the quadratic ramp type has many advantages over the trapez ramptype. Sorry to hear it causes problems in your situation. Can you please shortly explain the nature of the problems?
Best regards,
Georg
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I fully agree that the quadratic ramp type may have certain technical advantages.
However, the main problem is backward compatibility and consistency across projects.
In many automation projects, application developers rely on the fact that creating a new axis object will behave exactly the same way as in previous versions. With SoftMotion V4.18.0.0 and later, if an application developer adds an axis and overlooks the changed default, the motion function blocks behave differently than expected.
In particular, since the Jerk value in SM3_Basic function blocks is ineffective in trapezoid ramp type, users are accustomed to leaving this parameter empty in their projects. In many existing projects, this variable has not even been assigned. When the default is changed to quadratic, the Jerk parameter suddenly becomes relevant, which can cause errors or unexpected behaviour in the field.
From a user perspective, a default setting should always be the “safe” and “expected” option, while alternative options (like quadratic) can be selected manually if desired.
Keeping the default as trapezoid ensures compatibility with existing projects and prevents unexpected issues, while still allowing users to benefit from quadratic ramps if they explicitly choose so.
For these reasons, I kindly ask you to reconsider making trapezoid the default again. This would significantly reduce the risk of unexpected behaviour in future projects while still preserving the advantages of the quadratic ramp type for those who actively select it.
Of course, the final decision is entirely at your discretion.
Best Regards,
imdatatas
Last edit: imdatatas 2025-09-26
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Dear @gseidel, @tk096,
I noticed that with SoftMotion V4.18.0.0, if a new axis is added to the project, the ramp type selection defaults to "Quadratic".
In all previous versions, the velocity ramp type selection was "Trapezoidal".
This causes some unexpected issues in projects with SoftMotion version V4.18.0.0 for newly created or newly added axes to existing projects.
Is it possible to reconsider this situation in the next update and set the velocity ramp type to "Trapezoid" by default again?
Best Regards,
Imdat
Last edit: imdatatas 2025-07-22
Unfortunately, The same behaviour still exist with SoftMotion V4.19.0.0 too.
(default ramp type is quadratic instead trapezoid for new created axis object)
For your information.
Hi imdatatas,
thanks for your feedback. This change was intentional, as the quadratic ramp type has many advantages over the trapez ramptype. Sorry to hear it causes problems in your situation. Can you please shortly explain the nature of the problems?
Best regards,
Georg
Dear @gseidel,
Thank you for your clarification.
I fully agree that the quadratic ramp type may have certain technical advantages.
However, the main problem is backward compatibility and consistency across projects.
In many automation projects, application developers rely on the fact that creating a new axis object will behave exactly the same way as in previous versions. With SoftMotion V4.18.0.0 and later, if an application developer adds an axis and overlooks the changed default, the motion function blocks behave differently than expected.
In particular, since the Jerk value in SM3_Basic function blocks is ineffective in trapezoid ramp type, users are accustomed to leaving this parameter empty in their projects. In many existing projects, this variable has not even been assigned. When the default is changed to quadratic, the Jerk parameter suddenly becomes relevant, which can cause errors or unexpected behaviour in the field.
From a user perspective, a default setting should always be the “safe” and “expected” option, while alternative options (like quadratic) can be selected manually if desired.
Keeping the default as trapezoid ensures compatibility with existing projects and prevents unexpected issues, while still allowing users to benefit from quadratic ramps if they explicitly choose so.
For these reasons, I kindly ask you to reconsider making trapezoid the default again. This would significantly reduce the risk of unexpected behaviour in future projects while still preserving the advantages of the quadratic ramp type for those who actively select it.
Of course, the final decision is entirely at your discretion.
Best Regards,
imdatatas
Last edit: imdatatas 2025-09-26
Hi imdatatas,
thanks for your detailed and thoughtful feedback. We will discuss the topic in our team.
Best regards,
Georg