Product manual

TAC Xenta Server – Gateway, Technical Manual B Protocols
Schneider Electric Buildings AB, June 2011 177 (184)
04-00124-06-en
B.8.3 C-Bus Application Pseudo-Devices
One or more application pseudo-devices are added to the C-Bus inter-
face node in the network pane of XBuilder, as shown for the dimmer
application of the Workshop example network in the following screen-
shot.
Device Template
Device templates having a [CBus] filename prefix are used to create
C-Bus application pseudo-devices in XBuilder. Subsequently, each
device node is used to define the application it represents on the C-Bus
network.
Device Properties
• Application# – Allows the required application number to be
entered. The entered number should correspond to that of an appli-
cation on the C-Bus network. Each pseudo-device defines a set of
Group Variables associated with the application number.
In most cases only one application will exist on a C-Bus system
(numbered hex 38 as shown in the table above). However, on larger
systems additional application entries will be required.
Device Status Signal
For each device the Clipsal C-Bus interface driver generates a commu-
nication status signal.
• ComsFail – Flags if communications with the C-Bus application
have failed. Normally caused by an incorrect Application# having
been entered.
• online – Flags ONLINE during normal device communications,
and will change to OFFLINE if communications with the C-Bus
application have failed. An OFFLINE condition normally indi-
Note
• Two or more applications can have the same number. This allows
splitting a large set of Group Variables into smaller sub-applica-
tions, each represented by a separate node in XBuilder.