Browse FAQs

Bus number allocation in project imported into Unity Pro.

Published date: 27 November 2018

A Proworx 32 project, for example, has an IO map configured with an NOM, two NOEs and an RIO module.
PLC (DIO 1) = Slot 2
NOM (DIO 2) = Slot 4
NOE(1) = Slot 5
NOE(2) = Slot 10
CRP = Slot 16

Once the project is imported into Unity Pro, the Configuration as below in the the Unity Project Browser.

Local Bus = Bus 1
DIO Bus = Bus 2
RIO Bus = Bus 5

Here is how these numbers are assigned and why there are only 3 Buses.
The numbers are assigned in sequence for network interfaces.
The only buses that are shown in the configuration are Local, DIO configured for Peer Cop, and RIO.

Bus 1 is assigned to the CPU in slot 2,
Bus 2 is assigned to the NOM in slot 4 because it is configured for Peer Cop,
Bus 5 is assigned to the CRP RI/O head located in slot 16.

Bus 3 and 4 that are not seen because they are allocated to the NOE's in slots 5 and 10.


Legacy KB System (APS) Data: RESL212951 V1.0, Originally authored by DaSo on 11/06/2013, Last Edited by DaSo on 11/06/2013
Related ranges: Unity Pro - SoCollaborative software

Was this helpful?

What can we do to improve the information ?

Can't find what you are looking for?

Reach out to our customer care team to receive information on technical support, assistance for complaints and more.