In some situations related to calling motion commands, the mappMotion information “ACPDRV_ACTION’3’: Interface busy” can be reported several times inside the logger.
Beginning with mappMotion 6.7.0 following documentation is available for that status number:
I would like to add here, that this information gets inserted when internally in FBs implementation a new command tries to transfer data to the drive while the previous command is still active. This is similar to calling a ncAction in an ACP10 environment and getting status ncACTIVE. In this case the new command tries to send the command in the next cycle again.
Root causes in cases I dealt with have been motion commands which get called simultaneously (in the case above e.g. MC_SetOverride and MC_Power).
By making sure that such motion commands are not called simultaneously, but rather step by step once the earlier FB call is not busy anymore, this information can be avoided in the logger / NCT.
Best regards
Philipp
