Hello,
if your Axis-Slot is free and not used with a Motor i think the solution is ok and would not make a performance difference in comparison to the virtual one.
The only improvment with the External Encoder Setting is to free up the Axis for a real Motor and still having the External Encoder usable.
There is an advantage of the real axis, it is better in simulation. Because the Positions of the External Encoder are not Simulated in ARsim. So it might be an advantage to use the real Axis if it is free.
If you need to use both Motor and External Encoder in parallel i would recommend that you get in contact of local support. Becuase i currently don’t see why you should not get the Values into mpAxisBasic (considering that ARsim does not simulate Positions, only on Real Hardware you would see something). The External Encoder Object can directly be linked to mpAxisBasic.
One Additional Hint: You once refered to MC_BR_InitEndlessPosAcpEnc which is a Functionblock from ACP10. Please be aware that MappMotion and ACP10 can not be mixed up. While using the Automation Studio Help it is easy to accidentaly come over a Function which belongs to the different Feature-Set.
Greetings
Michael Bertsch