CGP Electronics TP-42 Dokumentacja

MS/TP Communications Bus Technical BulletinCode No. LIT-12011034Software Release 7.0Issued March 13, 2015Refer to the QuickLIT website for the most up

Table 2: BACnet Router AttributesUser Action or RecommendedSettingDescriptionBACnet Router Attribute NameSpecify the network number assigned forBACnet

Table 2: BACnet Router AttributesUser Action or RecommendedSettingDescriptionBACnet Router Attribute Namedefault=0The MS/TP MAC address of the BACnetR

Figure 4: Setting Network Address or Network NumberSupervisory Engine Configuration for Adding Remote Field BusYou define the Remote Field Bus at a Me

Trunk NumberOn a supervisory engine, trunk numbers 1 and 2 are reserved for the local field bus integration. Trunk numbers 3to 20 are reserved for Rem

Figure 5: Wiring BACnet RouterRemote Field Bus RestrictionsCompared to the local MS/TP field bus, the Remote Field Bus has several operational restric

Field Controller Main Code ReleaseFor Remote Field Bus compatibility, the Main Code for the field controllers you connect to remotely must be atMetasy

The Clear Statistics command is redirected to the FEC Family BACnet Device used for collecting MS/TP trunkstatistics. If the device used for collectin

Figure 6: EOL Terminations on an MS/TP BusBaud Rates on the MS/TP BusAn MS/TP bus can be configured to communicate at one of four different baud rates

If you anticipate critical peer-to-peer communication and therefore do not want field controllers to wait for the bussupervisor to establish the baud

The device address set on the ADDRESS DIP switch block applies to the device connection on the bus where thedevice is not the bus supervisor. For exam

Surge Protectors...44Appendix: Maxi

Table 4: Valid MS/TP Bus Address Values and Address Ranges for MS/TP Bus DevicesDevicesClassAddress Value/ AddressRangeFC Bus: NAE or NCESA Bus: FAC,

Important: On FAC, FEC, VMA16, and IOM Series controllers only, the 128 DIP switch on the controller’s deviceaddress DIP switch block is a mode switch

Table 5: Local FC Bus RulesRules/LimitsCategoryNAE55 Series models can support up to two local FC buses.Note: When a second FC bus is added to the NAE

Table 5: Local FC Bus RulesRules/LimitsCategory22 AWG Stranded, 3-Wire Twisted, Shielded CableRecommended Cable2The EOL switch must be set to On (or a

Table 6: FC Bus SpecificationsSpecificationCategoryMeets EN61000-4-4 and EN6100-4-5 requirements for heavy industrialapplications.Protected against mi

EOL Termination on the Local FC BusThe FC bus requires EOL termination at the end of each bus segment. Figure 10 shows four examples of EOLtermination

EOL Terminator ModuleThe MS-BACEOL-0 RS485 EOL Terminator provides EOL termination on FC bus segments when the deviceconnected at the end of a bus seg

SA Bus Rules and SpecificationsThe SA bus connects IOMs, VSDs, and NS-Series network sensors to field controllers. Figure 11 shows three SAbus example

SA Bus Device LimitsThe SA Bus is limited to 10 devices total to ensure good communication on the bus and is limited to four NS sensorsbecause only fo

EOL Termination on the SA BusOn an SA bus, the minimum requirement is that EOL termination must be enabled on at least one device. Since anSA bus supe

Document IntroductionThe BACnet® protocol Master-Slave/Token-Passing (MS/TP) communications bus is a local network that connectssupervisory controller

SA Buses with Multiple Network SensorsAn SA bus supports up to four network sensors. Figure 12 shows an example of two SA buses, each with fournetwork

Remote Field Bus Rules and SpecificationsTable 10 provides rules for the Remote Field Bus (RFB). In addition to these rules:• Configure the BACnet Rou

Table 10: Remote Field Bus RulesRules/LimitsCategoryWhen all of the devices connected on the Remote Field Bus are Metasys FACs, FECs,VMA16s, or IOMs,

EOL Termination on the Remote Field BusThe Remote Field Bus requires EOL termination at the end of each bus segment. Figure 13 shows four examplesof E

EOL Terminator Module for Remote Field BusAn EOL terminator is required in all Metasys MS/TP applications wherever a terminating device on a Remote Fi

Table 11: Cable for FC Buses and SA Buses in Order of PreferencePlenum ApplicationsNon-Plenum ApplicationsBus and Cable TypeO.D.Part NumberO.D.Part Nu

Table 12: FC Bus Wire Gauge and FC Bus Baud Rate1,524 (5,000)(A)1,524 (5,000)(Best)1,524 (5,000)(A)1,524 (5,000)(A)Maximum Cable Length perBus Segment

Figure 14: FC Bus and SA Bus Terminal Block Wiring DetailsGrounding the Bus Cable ShieldInductive interference and Radio Frequency (RF) interference c

Note: The majority of properly grounded MS/TP applications do not require soft ground connections, but you shouldassess the potential interference tha

Figure 16: 6-Pin Modular Jack Pinout DetailsCommissioning Devices on the MS/TP BusCommission the devices on the local and remote MS/TP buses using the

Table 1: Related DocumentationSee DocumentFor Information OnVMA1610 and VMA1620 Variable Air Volume ControllersInstallation Instructions (Part No. 24-

Appendix: FC Bus Auxiliary DevicesRepeatersRepeaters are optional components on the FC Bus that increase the maximum allowable length and device count

Figure 17: Configuring the RepeaterFiber-Optic ModemsYou can install the 2110 fiber-optic modems in any location on the FC bus. Just as only two repea

Fiber Modem between Two SegmentsIf you need to place the 2110 modem between two segments of MS/TP bus, wire a stub length of 6 inches or feweras shown

Figure 20: Female Modem Cable Connector: EOL Set to InModem Set EOL to OutTo set the modem with the end-of-line selection set to Out, wire the 9-pin c

Surge ProtectorsSurge protection is strongly recommended if the MS/TP bus is wired between buildings. The protection is providedby a voltage surge sup

Table 16: Surge Protector SpecificationsSpecificationCategory80 Joules per conductor (10/1000 us)Maximum Energy Dissipation12 VDCMaximum Operating Vol

The surge protector consists of two sections: the terminal block and the main assembly. These sections separateto make the unit easier to install and

Appendix: Maximizing and Troubleshooting the MS/TP BusMaximizing TipsObserve the following guidelines to maximize the performance of an MS/TP bus.Desc

Figure 25: MS/TP Object Diagnostic TabBus Health IndexThe Bus Health Index is a snapshot of the immediate number of errors on the bus. This index prov

Bus Performance IndexThe Bus Performance Index provides a snapshot of the performance of the network by taking the weighted movingaverage of the ratio

MS/TP Bus OverviewThe MS/TP bus is based on BACnet® standard protocol SSPC-135, Clause 9.The BACnet MS/TP protocol is a peer-to-peer, multiple master

Table 18: Statistics AttributesError Condition IndicatedAttributeThe node is trying to send or receive too much at this time.Buffer OverflowsNetwork d

Table 19: Bus Device Configuration ListPossible Values/Exception ValuesDescriptionLabelAny name or numberDisplays the name of the field device. The na

Table 19: Bus Device Configuration ListPossible Values/Exception ValuesDescriptionLabelBoot indicates that the device is starting andis not completely

Check for duplicate addresses in the following ways, depending on the severity of the situation:• If bus performance is degraded, check the address sw

Table 20: Common ProblemsPossible CausesSymptom• Device is failing to respond to the NAE's request.• Power or other failure occurred at the devic

• Check for and correct unstable sensors.• Reduce the number of devices on the bus, if possible.• If running at less than 38.4k baud, increase the bau

Figure 27: MSTP Master Summary Showing Baud RatesCounting the COVsYou can check the COV report rates on the main device object Diagnostics tab of each

The device remains offline until you repeat this procedure and send the Enable command.Changing the Baud Rate of an Entire BusThe following procedure

In some cases, there are statistical counters that count when recovery actions have been taken. The followingsections define four resources monitored

Protocol Engine Output Pending QueueThe BACnet® Protocol Engine has an output pending queue used to hold messages when slower communicationslinks, suc

FC BusAn FC bus connects a Metasys® system NAE or NCE to FACs, FECs, VMA16s, IOMs, and TEC26xx Seriesthermostats. Third-party BACnet MS/TP devices can

Remote Field BusThe Remote Field Bus uses a BACnet Router to connect remote BACnet MS/TP devices such as FECs and VMA16sto the Metasys network. These

The Remote Field Bus is defined at a Metasys NxE supervisory engine or Open Data Server (ODS) Workstation(Figure 3) through field bus integration, sim

• Remote buildings where an MS/TP bus is not already available, but an Ethernet BACnet/IP network is (forexample, university or hospital campuses)• Si