Log on to rate and give feedback    1 2 3 4 5 Log on to rate
0
Concept Concept 6/3/2022
Products: RP-C
Functionalities: Hardware
Product version: 2022

RP-C BACnet MS/TP Support

The RP-C controllers can be reconfigured to communicate with automation servers based on the BACnet MS/TP protocol, instead of the BACnet/IP protocol.

For the RP-C controller models RP-C-12A-F-24V, RP-C-12B-F-24V, RP-C-12C-F-24V, and RP-C-16A-F-230V, the following description applies only for hardware version 10 and later of the controller. For more information, see Differences Between RP-C Hardware Versions .

The support for connecting RP-C controllers to a BACnet MS/TP (RS-485) network for communication with an automation server (AS-P or AS-B) enables retrofitting of MNB and b3 BACnet devices on the network while reusing parts of the existing cabling and equipment. For more information, see RS-485 Communications .The support for both BACnet IP and BACnet MS/TP protocols also facilitates a transition from a BACnet MS/TP (RS-485) network to an IP based network. The controller can be configured to use either protocol.

Note:
  • “MNB BACnet devices” refers to Schneider Electric (TAC I/A Series) MicroNet BACnet (MNB) zone controllers.

  • “b3 BACnet devices” refers to Schneider Electric (Andover Continuum) b3 BACnet zone controllers.

An RJ45 to screw terminal block adapter and a separate connection cable is required to connect the RP-C controllers to the BACnet MS/TP (RS-485) network. For more information, see RS-485 Adapters .

The RS-485 adapters are available in two models:

  • Isolated RS-485 Adapter (SXWISORS48510001)

  • Non-isolated RS-485 Adapter (SXWNISORS48510001)

The RS-485 adapters can be ordered from Schneider Electric using the above part numbers.

The isolated adapter is designed to be used when connecting RP-C controllers to a BACnet MS/TP (RS-485) network with MNB devices.

The non-isolated adapter is designed to be used when connecting RP-C controllers to a BACnet MS/TP (RS-485) network with b3 BACnet devices.

The cable is not included and needs to be purchased separately.

To connect the adapter, it is recommended to use a Cat 5 (or higher) unshielded, straight-through wired cable with eight conductors (four twisted pairs) and RJ45 connectors. The recommended maximum cable length is 0.3 m (12 inches). The wire size (cross-sectional area) should be 22 to 26 AWG (0.34 to 0.14 mm²). When RP-C controllers are installed in a space that handles conditioned air or return air, the BACnet MS/TP (RS-485) network cables and IP network cables frequently must be plenum-rated to meet applicable building codes.

For more information, see Wiring .

Notice

LOSS OF COMMUNICATION

  • Ensure that the length of the cable for connection of the RS-485 adapter to the controller does not exceed 0.3 m (12 inches).

  • Use a Cat 5 or higher unshielded twisted pair cable with eight conductors (four twisted pairs), a cross-sectional area of 22 to 26 AWG (0.34 to 0.14 mm 2 ), and a rating that meets the requirements of the target environment.

Failure to follow these instructions can result in loss of communication.

You need to configure which RS-485 (RJ45) port on the RP-C controller to use for connection to the automation server BACnet MS/TP (RS-485) network. You can configure to use either the RS-485 Com A or Com B port, with the following restrictions:

  • RS-485 Com B can either be used for connection of an isolated adapter or a non-isolated adapter

  • RS-485 Com A can only be used for connection of a non-isolated adapter

For more information, see RP-C Communication Ports .

For more information, see Allocating Flexible Ports .

Location of the RS-485 Com A and Com B ports on the RP-C controllers

Location of the RS-485 Com A and Com B ports on the RP-C controllers

Automation Server BACnet MS/TP (RS-485) Network with MNB BACnet devices

In retrofit projects with MNB devices, the RP-C controllers can be mixed with MNB devices on the BACnet MS/TP (RS-485) network.

A mix of up to 50 devices per RS-485 Com port can be connected to an automation server.

The isolated RS-485 adapter is used for connection of the RP-C controller.

The isolated RS-485 adapter must be connected to the RS-485 Com B port on the RP-C controller.

Notice

BACNET MS/TP NETWORK OUTAGE OR PERFORMANCE DEGRADATION

For a BACnet MS/TP network with MNB BACnet devices, ensure you use an isolated RS-485 adapter (SXWISORS48510001) connected to the RP-C controller's Com B port.

Failure to follow these instructions can result in BACnet MS/TP network outage or performance degradation.

Examples of automation server BACnet MS/TP (RS-485) networks mixing RP-C controllers with MNB BACnet devices

Examples of automation server BACnet MS/TP (RS-485) networks mixing RP-C controllers with MNB BACnet devices

Automation Server BACnet MS/TP (RS-485) Network with b3 BACnet devices

In retrofit projects with b3 BACnet devices, the RP-C controllers can be mixed with b3 BACnet devices on the BACnet MS/TP (RS-485) network.

A mix of up to 50 devices per RS-485 Com port can be connected to an automation server.

The non-isolated RS-485 adapter is used for connection of the RP-C controller.

The non-isolated RS-485 adapter can be connected to either the RS-485 Com A or Com B port on the RP-C controller.

Examples of automation server BACnet MS/TP (RS-485) networks mixing RP-C controllers with b3 BACnet devices

Examples of automation server BACnet MS/TP (RS-485) networks mixing RP-C controllers with b3 BACnet devices

Community Content

Product version

Language