Any Solution for using MappIO with MappMotion

Ask Questions B&R Software & Runtime
1

Hello everyone,

I have a question regarding the combination of mappIO and mappMotion.

According to the documentation, using mappIO together with mappMotion is not supported. I’m wondering if there is still any way to use both in a meaningful setup, or if there are any known workarounds.

My specific use case is to move or remove stepper motor modules in the hardware slot configuration. With mappIO, this would normally be quite flexible, but in combination with mappMotion it seems to be restricted.

image
image412×340 15.9 KB

Has anyone here had experience with this or found a solution to handle such a scenario? Or is the only practical approach currently to avoid using mappIO in this case?

Thanks in advance!

Best regards

2

Hello,

according to the help it is supported to create mapp Motion hardware at runtime in combination with AsIOMMan library (Changing settings at runtime).

But I also wanted to use it with mappIO and it works for me. This is my case:

  1. Project configuration - In project I have template drives (one of each type which can be added at runtime) on nodes, which are excluded in mappIO configuration of Automation Runtime type (that means after MpIOImport they are removed from HW tree).
    {C43A2887-CB9C-46E6-9A20-FEFE40FF54D5}
    {C43A2887-CB9C-46E6-9A20-FEFE40FF54D5}521×224 6.62 KB
  2. ACOPOS P3 generation at runtime

    1. Creation using MC_BR_ProcessConfig function block

    2. Creation of configuration string for mapp IO

      {D9C078B1-B244-412C-8A89-1161ED263042}

    3. MpIoImport

This procedure works for me with ACOPOS P3, but I didnt test it with stepper modules, so you can try.