MS/TP Communications Bus Technical Bulletin

1 MS/TP Communications Bus Technical BulletinCode No. LIT-12011034 Software Release January 2018 Refer to the QuickLIT website for the most up-to-date version of this of Bus Field Router Engine Configuration for Adding Remote Field Router Field Bus Field Bus Status and Statistics Field Bus Status Termination on the MS/TP Rates on the MS/TP Addressing on the MS/TP a Device Field Controllers for Wireless FC Bus Rules and Termination on Local FC Terminator Series Thermostats and Third-Party MS/TP Bus Rules and Bus Device Termination on SA Buses with Multiple Network Field Bus Rules and Termination on the Remote Field Terminator Module for Remote Field Bus Cable Terminal Blocks for Connecting FC and SA Bus the MS/TP

2 Bus Cable Modular Jack and Cables for SA Devices on the FC : FC Bus Auxiliary and Connecting the Fiber Modems to MS/TP Modem between Two Termination on Fiber Communications Bus Technical BulletinAppendix:Maximizingand Troubleshootingthe HealthFactorsof the Bus Baud Rate of Deviceon the Baud Rate of an :OptimizingSA Bus Bus Traffic BACnet protocolMS/TPcommunicationsbus is a local networkthat connectssupervisorycontrollersand fieldcontrollersto field documentdescribesthe specifications,devicelimits,and rulesof the MS/TPcommunicationsbus, as well ashow to wire and terminatedevices,and troubleshootdevicecommunicationon the MS/TPbus. The remoteMS/TPfield bus is also the additionof a BACnetIP to BACnetMS/TPRouter, the RemoteFieldBus allowsconnectionto remotefield controllersover documentis intendedfor the user who needsto knowthe rules,requirements,limits,specifications ,andconfigurationof the MS/TPbus to design,wire,or troubleshootan ChangesThe followinginformationis new or revised: UpdatedTable 3to showaddresses1 to 3 as reservedfor JCI use and 120-127as reservedfor multiplecoordinatorswhenusingapplication swith ZFR1810coordinators.

3 UpdatedTable 6to give moredetailon NS seriessensorlimits. UpdatedRelatedDocumentationtable. UpdatedAppendix:FC Bus AuxiliaryDevicesto highlightneedto use built-interminationwhena fiber opticmodemis at the end of a networksegment. UpdatedModel2110 modemthroughoutas Model2110 BAC,whichis the BACnetversionof the fiber opticmodem. Addednoteswhereappropriateaboutpossibili tyof orderinga DIN rail mountingversion,2110 BAC-DIN,ifavailable. Updatedand removedreferencesto TEC3000inTEC26xxSeriesThermostatsand Third-PartyMS/TPDevices. UpdatedRelatedDocumentationtableto includeIOM2723,IOM3723,and OverviewThe BACnet protocolMS/TPcommunicationsbus is a local networkthat connectssupervisorycontrollersand fieldcontrollersto field bus is basedon BACnet standardprotocolSSPC-135, BACnetMS/TPprotocolis a peer-to-peer, multiplemasterprotocolbasedon masterdevicescan receivethe token,and only the deviceholdingthe tokenis allowedto originatea messageon the bus.

4 The tokenis passedfrom masterdeviceto masterdeviceusinga tokenis passedin consecutiveorderstartingwith the the bus only communicateon the bus whenrespondingtoa data requestfrom a :Do not connectMS/TPdevicesand N2 devicesto the same wiringrulesfrom N2 communicationsbuses,and MS/TPdevicesand N2devicesare not compatibleon the MS/TPbus is usedfor two typesof buses:a FieldControllerbus (FC) and a SensorActuator(SA) bus (Figure1). The MS/TPbus can also be extendedremotelyover the IP networkwith the additionof a BACnetIP to FC bus, SA bus, and RemoteFieldBus are networksof has only one bussupervisor, dependingon whichcontrollersare a local FC bus, the bus supervisoris the supervisoryengine. On the local SA bus, the bus supervisoris a field controller.

5 On the RemoteFieldBus, the bus supervisoris the BACnetIP to BACnetMS/TPRouter(hereaftercalledthe BACnetRouter),whichworkswith the supervisoryenginewhena RemoteFieldBus is TechnicalBulletinNote:Whenyou installa BACnetRouterfor addinga RemoteFieldBus to the job site, you needa site-level,uniqueMS/TPnetworknumberand deviceobjectID (if it containsa deviceobject)for the BACnetRouter. In addition,it is criticalthat you determineif a BACnetBroadcastManagementDevice(BBMD)is requiredfor the BACnetRouter. If you configurethe BACnetRouteras a BBMD,assigna staticIP addressto both the routerand theNxM or ODSwhereyou are configuringthe MS/TPbus. For an existinginstallation,contactthe BAS Manager,BuildingManager, or IT departmentfor informationon availablenetworknumbers,deviceobjectIDs, andexistingBBMD sfor crossingIP configuringa BBMDin a BACnetRouter(if it supportstheminternally)is availablefrom the bus supervisorcommunicateswith deviceson the supervisedbus and with deviceson the next (higherlevel)bus on the bus supervisortypicallystartsthe communicationon the FC bus, remoteFC bus, or SAbus.

6 If an SA bus, FC bus, or RemoteFieldBus doesnot havea bus supervisor, the masterdevicewith the lowestdeviceaddressvalueon the bus and a specificbaudrate selectedstartsthe ZFR1800 SeriesWirelessFieldBus Systemenableswirelesscommunicationon an MS/TPbus, allowingyouto createwirelessconnectionsbetweenAdvanced ApplicationFieldEquipmentControllers(FAC s),FieldEquipmentControllers(FECs),or VAV ModularAssemblies(VMAs),Input/OutputModu les(IOMs),and NetworkAutomationEngines(NAEs)or NetworkControlEngines(NCEs).SeeEnablingF ield Controllersfor WirelessOperationandRelatedDocumentation for detailedinformationaboutthe ZFR1800 SeriesWirelessFieldBus :The ZFR1800 SeriesWirelessFieldBus Systemis notsupportedon the TechnicalBulletinFC BusAn FC bus connectsaMetasys systemNAE or NCEto FACs,FECs,VMA16s,IOMs,and also be connectedto the FC : Exampleof an MS/TPCommunicationsBusOn an FC bus, the NAE or NCEis the bus supervisor.

7 An FC bus supportsup to threebus segmentsthat areconnectedwith networkrepeaters(Figure9). SeeLocal FC Bus Rules and Specificationsfor BusThe SA bus connectsNCEs,FACs,FECs,and VMA16s(fieldcontrollers)to endpointdevices,such as IOMs,networkthermostats,networksensors,a nd JohnsonControlsVariableSpeedDrives(VSDs) .On an SA bus, an NCE,FAC, FEC,or VMA16is the bus supervisor. The SA bus is a privateMS/TPbus that onlysupportsthosedevicesthat can be definedusingthe CCT programmingtool. The bus doesnot supportbus segments(Figure13). SeeSA Bus Rules and Specificationsfor TechnicalBulletinRemoteField BusThe RemoteFieldBus uses a BACnetRouterto connectremoteBACnetMS/TPdevicessuch as FECsand VMA16sto ,FECs,VMA16s,IOMs,TEC26xxSeriesthermosta ts,andotherBACnetMS/TPfield differentmanufacturersare available,therecommendeddeviceis the LIP-ME201 BACnetRouterfrom Loytec notuse anyUSB-poweredMS/TPto IP converter, includingthe JohnsonControls BACnetto MS/TPRouter(TL-BRTRP-0).

8 Use a RemoteFieldBus for applicationswhereroutingan RS-485networkdirectlyto an NxE supervisoryengineis not practicalbecauseof distance,cost,or poor accessibility. In manycases,an IP networkconnectionis availableat both the NxE supervisoryengineand at somepointnear the leveragingtheMetasysRemoteFieldBus capabilitywith installingthe BACnetRouternear the BACnetMS/TPdevices,you can ,whenyou chooseMS/TPdeviceintegrationwith a routerratherthan BACnetIntegration,accessto proprietaryattributes,messagetypes,and objectsfromMetasysfield controllersis functionalityprovidesyou with moreinformationand morecapabilitythan the standardBACnetattributes,services,and example,at the Site ManagementPortalyou can view proprietaryattributessuchas communicationstatisticsfrom mappedFEC.

9 RemoteMS/TPdeviceintegrationsupportsthe CCT Passthroughoptionfor downloadingdevicesdirectlyconnectedto the RemoteFieldBus (but not to devicesconnectedto thesensorbus).Figure2showsan exampleof aMetasysnetworkwith a : Exampleof a RemoteField Bus6MS/TPCommunicationsBus TechnicalBulletinThe RemoteFieldBus is definedat aMetasysNxE supervisoryengineor OpenDataServer(ODS)Workstation(Figure3) throughfield bus integration,similarto how a local MS/TPfield bus is RemoteFieldBusappearson the All ItemsNavigationtree in the Site ManagementPortalUI. You can also providea customnameto clearlyidentifythe type of :To ensureacceptablesystemperformance,makesu re that you map all devicesand objectsthat originatefrom a RemoteFieldBus to a singlesupervisoryengine,for example,if you havetwo NAEs(NAE-1andNAE-2),eachwith a separateRemoteFieldBus.

10 Device1 is definedunderNAE-1,and Device2 is this arrangement,makesure you do not map Device1 to NAE-2or map Device2 to you mix remotefield devicemappingbetweensupervisoryengines,t heMetasyssystemmay start veryslowly, and devicesmay : Exampleof a RemoteField Bus with ODSA pplicationsfor the RemoteFieldBus include: Any intra-building,inter-building,or remotelocationthat has IP networkconnectionsreadilyavailable Locationswhereit is cost prohibitiveor difficult to run MS/TPwiringbetweendevicesand the NxEs,due todistance,cost,accessibility, or customerfactors Locationswherefield controllersare segregatedfrom the NxEs Intra-buildingapplicationsthat connectsegregatedlocationswithina building(for example,connectingpenthousesto mechanicalrooms)7MS/TPCommunicationsBus TechnicalBulletin Remotebuildingswherean MS/TPbus is not alreadyavailable,but an EthernetBACnet/IPnetworkis (forexample,universityor hospitalcampuses)