# How many ACOPOS receive channels (MA1 - MA5) does MC\_BR\_InitReceiveNetworkEnc need? **URL:** \ **Category:** Mechatronics & Motion\ **Tags:** acopos, acp10\ **Created:** [May 4, 2026, 7:44am UTC](https://community.br-automation.com/t/how-many-acopos-receive-channels-ma1-ma5-does-mc-br-initreceivenetworkenc-need/11128 "2026-05-04T07:44:48Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![dominik.lehnberg](https://avatars.discourse-cdn.com/v4/letter/d/FF8800/32.png) [@dominik.lehnberg](https://community.br-automation.com/u/dominik.lehnberg)\ **Post date:** [May 4, 2026, 7:44am UTC](https://community.br-automation.com/t/how-many-acopos-receive-channels-ma1-ma5-does-mc-br-initreceivenetworkenc-need/11128/1 "2026-05-04T07:44:48Z")
Hi there, can someone tell me how many ACOPOS Receive Channels (MA1 - MA5) on the drive the function block “MC\_BR\_InitReceiveNetworkEnc” uses with different configurations: ![image](https://europe1.discourse-cdn.com/brcommunity/original/2X/b/b70281d970c9390813084995da998e540825c8de.png) The B&R help is not 100% clear. Only the mode “mcINC\_REF” is documented and uses all 5 channels. Does this mean, there is no channel left for axis coupling via Gear/CamIn ? Or am I missing something? ![image](https://europe1.discourse-cdn.com/brcommunity/original/2X/3/3d9a8945937877030c6cc8d3c932d6873c72a15b.png) Thanks in advance 🙂 Dominik ---
**Author:** ![Martin.Schrott](https://avatars.discourse-cdn.com/v4/letter/m/FF8800/32.png) [@Martin.Schrott](https://community.br-automation.com/u/Martin.Schrott)\ **Post date:** [May 4, 2026, 10:30am UTC](https://community.br-automation.com/t/how-many-acopos-receive-channels-ma1-ma5-does-mc-br-initreceivenetworkenc-need/11128/2 "2026-05-04T10:30:59Z")
Hi Dominik, MC\_BR\_InitReceiveNetworkEnc uses one ACOPOS receive channel per data point. The possible data points are listed in this table in the Help: ![image](https://europe1.discourse-cdn.com/brcommunity/original/2X/d/def11f3ee18322012e96519f59c8d110bf93d14b.png) The example for “mcINC\_REF\_” in the Help uses 4 receive channels: NetEncoderInfoRef.Type := mcINC\_REF; DeviceString := ‘IF3.ST6.IF1.ST2’; Position := ‘Position’; PositionTime := ‘PosTime’; ReferencePosition := ‘Reference’; ReferenceCount := ‘RefCycle’; NetEncoderInfoRef.AdrDeviceString := ADR(DeviceString); **NetEncoderInfoRef.AdrPosition := ADR(Position); NetEncoderInfoRef.AdrPositionTime := ADR(PositionTime); NetEncoderInfoRef.AdrReferencePosition := ADR(ReferencePosition); NetEncoderInfoRef.AdrReferenceCount := ADR(ReferenceCount);** ---
**Author:** ![dominik.lehnberg](https://avatars.discourse-cdn.com/v4/letter/d/FF8800/32.png) [@dominik.lehnberg](https://community.br-automation.com/u/dominik.lehnberg)\ **Post date:** [May 4, 2026, 11:45am UTC](https://community.br-automation.com/t/how-many-acopos-receive-channels-ma1-ma5-does-mc-br-initreceivenetworkenc-need/11128/3 "2026-05-04T11:45:07Z")
Hi Martin, thanks for your reply. I am still missing a table where each mode is listed with the number of channels needed? How many channels does the simple “mcINC” mode use for example? Only 1 (Position Value)? Best regards Dominik ---
**Author:** ![valerio.manenti](https://dub1.discourse-cdn.com/brcommunity/user_avatar/community.br-automation.com/valerio.manenti/32/11712_2.png) [@valerio.manenti](https://community.br-automation.com/u/valerio.manenti)\ **Post date:** [May 4, 2026, 12:18pm UTC](https://community.br-automation.com/t/how-many-acopos-receive-channels-ma1-ma5-does-mc-br-initreceivenetworkenc-need/11128/4 "2026-05-04T12:18:39Z")
Hi @dominik.lehnberg , regarding the screenshot for “Additional information”, due mistakes we did in the past now R&D has added that note because they want to clarify, one more time, you can configure max 5 cyclic read channels. When you use MpAxisBasic (Legacy version for my example) you see some of them are using for updating Torque/LagError/MotorTemperature info: ![image](https://europe1.discourse-cdn.com/brcommunity/original/2X/2/2a391afeb18d0b6de7729a7f2ce514e8c195371d.png) ![image](https://europe1.discourse-cdn.com/brcommunity/original/2X/f/f20ed64d625e18b5dd370ad476ccd6626aad5664.png) Ciao Valerio ---
**Author:** ![Martin.Schrott](https://avatars.discourse-cdn.com/v4/letter/m/FF8800/32.png) [@Martin.Schrott](https://community.br-automation.com/u/Martin.Schrott)\ **Post date:** [May 4, 2026, 1:40pm UTC](https://community.br-automation.com/t/how-many-acopos-receive-channels-ma1-ma5-does-mc-br-initreceivenetworkenc-need/11128/5 "2026-05-04T13:40:26Z")
The table above tells us that for “mcINC” “AdrPosition” is required and “AdrPositionTime” and “AdrEncoderStatus” are optional. If only “AdrPosition” is used, 1 receive channel is used. If all 3 data points are used, then 3 receive channels are used, 1 for each data point. I recommend to use at least one of the 2 data points “AdrPositionTime” or “AdrEncoderStatus” to detect problems with the encoder values. ---
**Author:** ![dominik.lehnberg](https://avatars.discourse-cdn.com/v4/letter/d/FF8800/32.png) [@dominik.lehnberg](https://community.br-automation.com/u/dominik.lehnberg)\ **Post date:** [May 6, 2026, 8:02am UTC](https://community.br-automation.com/t/how-many-acopos-receive-channels-ma1-ma5-does-mc-br-initreceivenetworkenc-need/11128/6 "2026-05-06T08:02:59Z")
Thanks for the clarification 🙂