earth_america
user_standard Connexion
action_search_stroke
earth_america
Log on to rate and give feedback 1 2 3 4 5 Log on to rate
0
Concept

Concept


Produits : RP-C
Fonctionnalités : Matériel
Version produit : 2023, 2024, 7.0
04/11/2024

RP-C BACnet MS/TP Support

arrow1_rotationRP-C Controllers Supporting both BACnet/IP and MS/TP arrow1_rotationRP-C Controllers Only Supporting BACnet MS/TP

The RP-C controllers support BACnet MS/TP communication. The BACnet MS/TP configuration differs between the RP-C models. The BACnet/IP enabled RP-C controllers can be reconfigured to communicate with automation servers based on the BACnet MS/TP protocol, instead of the BACnet/IP protocol. An adapter is required for converting the controller RS-485 Com port with RJ45 interface to screw terminals. There are also RP-C models designed for connection to a BACnet MS/TP (RS-485) network and these models can only communicate via MS/TP.

Regarding the differences in the BACnet protocol support, the RP-C controller models can be divided into the following two categories:

  • RP-C controllers supporting both BACnet/IP and MS/TP

  • RP-C controllers only supporting BACnet MS/TP

RP-C Controllers Supporting both BACnet/IP and MS/TP

This category of BACnet/IP enabled RP-C controllers needs to be reconfigured to communicate using BACnet MS/TP, instead BACnet/IP. The category consists of the RP-C models with “-F” in the product name:

  • RP-C-12A-F-24V, RP-C-12B-F-24V, RP-C-12C-F-24V, RP-C-16A-F-230V, RP-C-16B-F-24V, and RP-C-16B-F-230V, and RP-C-16C-F-230V

Déclaration

Even if the RP-C-16C-F-230V model supports BACnet MS/TP communications, this BACnet/IP enabled RP-C controller is not intended to be reconfigured for connection to a BACnet MS/TP (RS-485) network and it does not support connection to a network comprised of devices with an isolated RS-485 interface, such as the MNB BACnet zone controllers.

Déclaration

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 BACnet MS/TP support only applies to hardware version 10 and later of the controller. Pour plus d'informations, voir Differences Between RP-C Hardware Versions .

Pour plus d'informations, voir RP-C Models .

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. Pour plus d'informations, voir 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.

Déclaration

  • “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. Pour plus d'informations, voir 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.

Déclaration

The isolated adapter is not supported by the RP-C-16C-F-230V model.

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.

Pour plus d'informations, voir Wiring .

Déclaration

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

Pour plus d'informations, voir Communication Ports on RP-C Models with “-F” in the Product Name .

Pour plus d'informations, voir Allocating Flexible Ports .

As part of the commissioning process for the device, you also need to configure the baud rate for the automation server BACnet MS/TP (RS-485) bus. Pour plus d'informations, voir MS/TP Communications Baud Rate .

 
action_zoom_plus_stroke Location of the RS-485 Com A and Com B ports on the RP-C controllers with “-F” in the product name
Figure : Location of the RS-485 Com A and Com B ports on the RP-C controllers with “-F” in the product name
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.

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.

Déclaration

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 controller's Com B port.

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

 
action_zoom_plus_stroke Examples of automation server BACnet MS/TP (RS-485) networks mixing RP-C controllers (models with “-F” in the product name) with MNB BACnet devices
Figure : Examples of automation server BACnet MS/TP (RS-485) networks mixing RP-C controllers (models with “-F” in the product name) 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.

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.

 
action_zoom_plus_stroke Examples of automation server BACnet MS/TP (RS-485) networks mixing RP-C controllers (models with “-F” in the product name) with b3 BACnet devices
Figure : Examples of automation server BACnet MS/TP (RS-485) networks mixing RP-C controllers (models with “-F” in the product name) with b3 BACnet devices

RP-C Controllers Only Supporting BACnet MS/TP

This category of RP-C controllers only supports connection to an BACnet MS/TP (RS-485) network. The category consists of the RP-C models with “-M” in the product name:

  • RP-C-12A-M-24V, RP-C-12B-M-24V, and RP-C-16A-M-24V

Pour plus d'informations, voir RP-C Models .

The RP-C controllers have an RS-485 port with a 3-pole removable screw terminal block that is used for connection to the BACnet MS/TP (RS-485) network and MS/TP communication with the automation server (AS-P or AS-B). Connecting to an IP network is not supported as these RP-C models do not have Ethernet ports. Pour plus d'informations, voir Communication Ports on RP-C Models with “-M” in the Product Name .

You need to configure a unique MS/TP address for the device during installation using the address DIP switches on the device. Pour plus d'informations, voir MS/TP DIP Switches .

As part of the commissioning process for the device, you also need to configure the baud rate for the automation server BACnet MS/TP (RS-485) bus. Pour plus d'informations, voir MS/TP Communications Baud Rate .

 
action_zoom_plus_stroke Location of the RS-485 screw terminal block on the RP-C controllers with “-M” in the product name
Figure : Location of the RS-485 screw terminal block on the RP-C controllers with “-M” in the product name
Automation Server BACnet MS/TP (RS-485) Network with b3 BACnet devices

The RP-C controllers can be mixed with b3 BACnet devices on the BACnet MS/TP (RS-485) network. Pour plus d'informations, voir RS-485 Communications .

Déclaration

The RP-C controller models with “-M” in the product name are not isolated and connection of the controllers to a network comprised of isolated RS-485 interfaces is not recommended. The RS-485 application guidelines provide additional details. Pour plus d'informations, voir RS-485 Communications .

 
action_zoom_plus_stroke Examples of automation server BACnet MS/TP (RS-485) networks mixing RP-C controllers (models with “-M” in the product name) with b3 BACnet devices
Figure : Examples of automation server BACnet MS/TP (RS-485) networks mixing RP-C controllers (models with “-M” in the product name) with b3 BACnet devices

Voir aussi

  • Hardware Overview
  • RP-C Controllers
  • RP-C Models
  • RS-485 Adapters
  • RS-485 Communications
  • Wiring
  • Communication Ports on RP-C Models with “-F” in the Product Name
  • Communication Ports on RP-C-16C-F-230V
  • Communication Ports on RP-C Models with “-M” in the Product Name
  • Differences Between RP-C Hardware Versions
  • Allocating Flexible Ports
  • MS/TP Communications Baud Rate
  • Configuring MS/TP Network Settings
  • MS/TP DIP Switches
  • Configuring the MS/TP Address