Skip to main content
DKing.1
DKing.1
Associate II
November 14, 2021
Solved

See details

  • November 14, 2021
  • 1 reply
  • 1225 views

Hi,

Some feedback for ST on the latest motor control MCSDK_v5.Y.3: Within files mcptl.h and aspep.c, bad practice to name an enumerated constant 'free', as of course conflicts with stdlib.h free function. We include stdlib.h for a few standard functions, though not free. Anyway, the duplicate name use causes a compilation error, that was not present with MCSDK_v5.4.5. Our workaround: Within the two mentioned files, rename free to free_ (one place in mcptl.h, three places in aspep.c)

Also, while writing, ST, do you have some documentation about the ASPEP protocol? A quick google yielded none, though I see someone else requested, two months back. Presently, we are using the published information about the 5.4.5 Motor Control Protocol, to communicate with a device other than the workbench. To use 5.Y.3, we would need to changeover our device comms to use ASPEP. I'll take a guess at what that stands for. Is it Advanced Serial Private Embedded Protocol?

Mods, if moving parts of a thread to a more appropriate section of the forum, could you include a source to dest link, and vice-versa, so that the thread is still useful?

Thank you,

David

This topic has been closed for replies.
Best answer by cedric H

Hello David,

Thanks for your feedback. Indeed the usage of 'free' is a bad practice and it is already fixed in our master branch. The coming 5.Y.4 will not contain this constant anymore.

The ASPEP protocol documentation is not yet available mainly because it is not frozen yet. The release 5.Y is an intermediate step towards the 6.0, and we will guarantee the backward compatibility from the 6.0 only.

To answer your question, ASPEP stands for Asymmetric Serial Packet Exchange Protocol. It will be published when the 6.0 will be out.

Regards

Cedric

1 reply

cedric H
cedric HAnswer
Technical Moderator
November 15, 2021

Hello David,

Thanks for your feedback. Indeed the usage of 'free' is a bad practice and it is already fixed in our master branch. The coming 5.Y.4 will not contain this constant anymore.

The ASPEP protocol documentation is not yet available mainly because it is not frozen yet. The release 5.Y is an intermediate step towards the 6.0, and we will guarantee the backward compatibility from the 6.0 only.

To answer your question, ASPEP stands for Asymmetric Serial Packet Exchange Protocol. It will be published when the 6.0 will be out.

Regards

Cedric

Terms & ConditionsAccessibility statement