mappMotion alternative to "MC_BR_InitReceiveNetworkEnc"?

Hello everyone,

what is the mappMotion alternative to the ACP10 library function block “MC_BR_InitReceiveNetworkEnc”? Do I have to declare an extra axis (Encoder axis) just to read the position value of a network encoder? Or am i missing something here?

Thanks in advance.

Dominik

I should add I am using a ACOPOS micro (80VD100PD.C000-01) and a DC1073 Module to read the encoder values. The goal is to transfer the values to the position controller.

Any ACP10 and mappMotion expert who can help here?

This sounds like the solution intended for it: B&R Online Help

Please feel free to let me know, if not

yup not too much info in the Help (at least on the migration table):

Unfortunately the help does not really help much and isn’t very specific. At the moment i dont have an idea how to implement this in mappMotion.

Hello,

The “ACP10 to MappMotion” Migration tells us that it was intended to solve this via
Configuration. For the External Encoder Axis this was already made possible like we can see in the Screenshot. For some other possibilities it was not yet made possible via configuration.

In Generall the function behind the PLCopen Functionblock is there.
But it must be made by Hand, some of us had made it back in days of ncAction. :wink:

In General it is based on Virtual Encoder Mode 30. And Network Communication.
This Article in AS-Help descripes a lot of variants.
AS-Help: Virtual Encoder

I would also assume that after enabling MC_BR_InitReceiveNetworkEnc on an old machine with ACP10 you can check Network Command Trace and check most of the ParIDs written to enable the communication.


Enabling the External encoder to use the Cofiguration and then use ACOPOS cross communitcation could also be a way of solving this. But i am not sure which way is the “better way”.


Sorry that i do not currently have a out of the hand solution.

Greetings
Michael Bertsch

Hi MIchael, thanks for the response. To be honest, I’m really surprised that there isn’t a clean mappMotion solution for this use case yet and that you have to configure everything yourself at the ParID level. Is this not a common use case more customers need?

Hello all,

In this type of situation, you can use Pure Virtual Axis’s General purpose axis interface as an external encoder without needing any additional hardware to configure an encoder as an axis. By doing this, you can use this axis either as a master axis for a cam automat or as a standard axis for position and velocity reading like you did in ACP10. Actually, in all the cases where I used the function in ACP10, I configured the encoder this way when using MappMotion.

PureVirtualAxis

Hello,

to be honest i don’t know how much use Cases we have out there for this. But if i would invest Money for a expensive Servo, i would try to get a Drive Control where i have the right Interface to connect it, to get all the build in LoopControl Performance from short delays. I would try to avoid the Fieldbus at all cost, even if it is possible to do. I know its not easy with all that different Encoder options out there…

There is a ACOPOSmicro with SIN/COS like your DC1073 ; So i think you will use the Encoder as TwoEncoder Control… ?

I am not sure if this will lead to something, as you probably move a existing Machine from ACP10 to MappMotion and would not like to change electronics, to stay compatible…

The most often use case i think is the additional Master Encoder which can be solved via the External Encoder. Here we have also the support for configuring Network Encoders.


If you have trouble to set this up, please contact local Support so they can help you in getting this LoopControl back to run. I know that the ParID stuff can be complicated.

Greetings
Michael

Hi Michael,

thanks for the effort. I will contact the local support to find a solution that fits our needs.

Best regards
Dominik