gseidel

Hi imdatatas, thanks for your detailed and thoughtful feedback. We will discuss the topic in our team. Best regards, Georg

Hi imdatatas, sorry to hear this issue caused so much overhead for you. Frankly, I'd expect a project created with an older version to compile without errors after opening > it with the latest Codesys version and updating all libraries. Yes, that is a reasonable expectation. I tried a few times but could not reproduce the problem. In case you run into the problem again, we can investigate the issue if you send a project archive. Best regards, Georg

Hi liai, I tried it with a fresh CODESYS SP21 Patch 2 installation and SoftMotion 4.18, but cannot reproduce the compile errors. Could you please upload a project archive that has the errors? Then I can have a deeper look. https://dl.codesys.com/s/q4KcbKCcZndg6oR Best regards, Georg

Hi blitz, the G1 sentences N50, N70, and N110, which have length 0, lead to a stop of interpolation between the arcs. If you remove these lines, SMC_SmoothPath works (I tried it). Bst regards, Georg

Hi SLUCodesys, dwErrorId is a drive specific error number. The drive documentation should be consulted to interpret it. (Note that you should use MC_ReadAxisError to read this error, see https://content.helpme-codesys.com/en/libs/SM3_Basic/Current/SM3_Basic/POUs/Diagnostics/MC_ReadAxisError.html. Accessing the internal variable will result in outdated values if the acis error is not mapped by PDO and is not recommended in general.) uiDriveInterfaceError holds errors of the SoftMotion driver for the...

Hi liai, is it possible, that SM3_Basic is missing in the library manager? (It should be inserted automatically when adding a Cam table, along with the other motion libs.) You can add it manually and see if that solves the compile errors. Best regards, Georg

We updated our help on the queue sizes, see this new page for our recommendations: https://content.helpme-codesys.com/en/CODESYS%20SoftMotion/_sm_preprocessing_queuesize.html

Hi manuknecht, the axis group currently always writes the axis set torque values. If no dynamic model has been configured for the axis group, then the set torques are written to 0. The solution for your use case is to call SMC_GroupUpdate [0] before you call SMC_SetTorque on the axes. This way, the axis group will write 0 to the set torques in the call to SMC_GroupUpdate(), and SMC_SetTorque then will write the desired set torque. Best regards, Georg [0] https://content.helpme-codesys.com/en/lib...