Class BusConfig
Version 1.0
Modified 08-MAR-2026 11:05:32.00
 The Bus object configures a Qcom bus that nodes in the project will
 communicate on.

 Qcom is the communication protocoll for ProviewR nodes and proview
 processes. Nodes that will communicate over Qcom has to use the same
 Qcom bus. Communication between nodes in different busses is not possible.

 A Qcom bus is specified with a busnumber in the interval 0-999.

 The BusConfig object should be configured in the directory volume as a top
 object. Below this, each node of the system, that belong to this Qcom bus,
 should be configured with a NodeConfig object.

 It is common to configure at least two different Qcom busses in a system, one
 for the production nodes and one for simulation nodes.

See also



RtBody attributes pwr_sClass_BusConfig
String80 Description   Description of the bus.
UInt32 BusNumber   Specification of a Qcom bus.
A number in the intervall 1-999.

Qcom is the communication protocoll used by the nethandler and
message handler to communicate between ProviewR nodes. The Qcom network
is divided into busses, where two nodes has to be on the same bus to be
able to communicate.

Normally you divide the network into one production bus and one simulation
bus, thus preventing the simulation nodes to interfere with the production
nodes. In large networks it is also possible to divide the production nodes
into several busses.
YesNoEnum QComAutoConnectDisable   Disable the QCom auto connect. The nodes in the project
will not automatically create QCom links between each other.
These links can be configured individually for each node with
FriendNode objects.


Attributes detail


Description Attribute
Class Attribute
Type String80
Flags
Body RtBody
Description of the bus.

BusNumber Attribute
Class Attribute
Type UInt32
Flags
Body RtBody
Specification of a Qcom bus.
A number in the intervall 1-999.

Qcom is the communication protocoll used by the nethandler and
message handler to communicate between ProviewR nodes. The Qcom network
is divided into busses, where two nodes has to be on the same bus to be
able to communicate.

Normally you divide the network into one production bus and one simulation
bus, thus preventing the simulation nodes to interfere with the production
nodes. In large networks it is also possible to divide the production nodes
into several busses.

QComAutoConnectDisable Attribute
Class Attribute
Type YesNoEnum
Flags
Body RtBody
 Disable the QCom auto connect. The nodes in the project
 will not automatically create QCom links between each other.
 These links can be configured individually for each node with
 FriendNode objects.