I have the following problem, which I have not yet been able to solve with existing posts from the forum.
I am using an AcoposMulti (single) on which a real axis runs. Now I would like to create an additional virtual axis that receives an encoder value from an external encoder. The encoder is connected to plug-in module 2 (SS2) of the Acopos. (8BAC0123.000-1) Unfortunately, I am unable to obtain a position value. I have already tried different ParIDs, but without success.
with mapp Motion you can configure an “External encoder axis”, see screenshot.
The axis object can then be used with function blocks, e.g. as master axis for couplings.
Encoder errors are reported via this axis object (not via the real axis of channel 2).
If the issue is solved, can you tell us the final solution so we can close the topic? For new questions, it is always good to create a new discussion (use a link to refer to this topic) so we do not mix discussions
Unfortunately, I don’t have a clean solution. More of a workaround…
Instead of the virtual axis, I create a real one and then get the position. The problem with the virtual axis is that although I have my encoder value in ParID 91 (ENCOD1_S_ACT), I can’t get it into the MpAxisBasic structure and can’t reference it.
Neither with ParID 230 (PCTRL_S_ACT_PARID) and ParID 722 (VCTRL_S_ACT_PARID), nor in any other way. Maybe someone has an idea?
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.
