Modbus Configuration Guide - ABB
—ABB M EA SUR E M E NT & AN A LYT IC S 2 106 280 MN AAModbus configuration guideXSeriesG4Accurate, reliable, capable of measurementand monitoring gas flow to AGA, it isAPI and ISO standard.Measurement made easy.
—ContentsContents . 2List of figures . 4List of tables . 5Additional information . 6Cyber security . 6Safety . 7Safety symbol conventions .71 Overview . 81.1Modbus background.81.2Totalflow Modbus protocol format .91.3Totalflow Modbus implementation.92 How to use this guide . 102.1Procedure overview . 102.2Assumptions . 112.3Requirements . 113 Scenario 1: XFCG4 to XFCG4 with RS-485 link . 113.1XFC to XFC scenario overview . 113.2Assumptions . 113.3Connect components (wiring) . 123.4Connect using PCCU . 133.5Configure master Setup tab . 133.6Configure the master Advanced tab . 143.7Create the master Request Block. 153.8Configure the master Holding Registers. 163.9Configure the slave Setup tab . 173.10 Configure the slave Advanced tab. 183.11 Create the slave register map . 183.12 Monitor Statistics . 203.13 View Packet Log . 204 Scenario 2: XFCG4 to fixed slave device . 214.1XFCG4 to fixed slave device overview. 214.2Assumptions . 214.3Connect components (wiring) . 214.4Connect using PCCU . 224.5Configure the master Setup tab . 234.6Configure the master Advanced tab . 254.7Create the master Request Block. 254.8Configure master Holding Registers . 264.9Monitor statistics . 284.10 View Packet Log . 292 XS ERI ES 2106280 MN AA
5 Scenario 3: Modbus TCP server to client . 295.1Modbus TCP server to client overview . 295.2Assumptions . 305.3Connect components (wiring) . 315.4Connect using PCCU . 315.5Configure XFCG4 network connections . 325.6Configure server Setup tab . 345.7Create the server Register Maps. 345.8Configure the client Setup tab. 365.9Create client write block . 365.10 Verify client write to master. 385.11 Monitor statistics . 395.12 View Packet Log . 396 XSeriesG4 Modbus device parameters . 406.1Modbus protocol parameter definitions . 402106280 MNAA XS ERI ES 3
—List of igureFigureFigureFigure1 Basic Modbus components.82 MRB and MRM .93 XFC to XFC . 114 Comm2 XFC (master) to XFC (slave) wiring . 125 Expert view setup . 136 Master setup tab . 147 Advanced setup . 148 Master MRB . 159 Master holding registers. 1610 Slave setup tab . 1711 Slave advanced tab . 1812 Slave register map . 1913 Statistics . 2014 Packet log . 2015 XFC to fixed slave. 2116 Comm2 XFC (Master) wiring . 2217 Expert view setup. 2318 Master setup tab . 2419 Master advanced tab . 2520 Master request block . 2621 Master holding registers . 2722 Statistics . 2823 Packet log . 2924 Modbus TCP site . 3025 XFC onboard Ethernet port . 3126 Expert view setup. 3227 Communication Setup . 3228 Network connection configuration . 3329 XFC onboard reset button. 3330 Server setup tab . 3431 Server register map. 3532 Client setup tab . 3633 Client MRB . 3734 Verify writes . 3835 Statistics . 3936 Packet log . 394 XS ERI ES 2106280 MN AA
—List of eTableTableTableTableTableTableTableTableTable1 Related documentation.62 Modbus RTU message frame format .93 Modbus ASCII message frame format .94 Gould Modbus defined functions .95 Read query . 106 Read response . 107 Set query . 108 Set response. 109 Set multiple query . 1010 Set multiple response . 1011 Exception response . 1012 Legend for Comm2 wiring . 1213 Legend for Comm2 Master wiring. 2214 Slave registers . 2615 Address reference . 3416 Modbus communications parameters . 4017 Protocol parameters . 4018 Typographical conventions . 432106280 MNAA XS ERI ES 5
—Additional informationAdditional information pertaining to ABB G4 Modbus Communications can be found atwww.abb.com/totalflow. The following table has links to documents that may be helpful with Modbus.Table 1 Related documentationItemDescriptionDocument numberABB DownloadCenterLocation for all documents available for downloadABB Documentdownload centerDocumentTotalflow Modbus protocol document2017384Technical Bulletin180TFIO Communication Interface Module (2100421BD) (CIM) and Modbus ProtocolTekbul 180Technical Bulletin182NGC Modbus Registers assignments in the NGC8200Tekbul 182User DrawingXFCG4 Com 1 to ABB Coriolis Meter using HartModbus Converter2104918User DrawingXRCG4 Adapting K-TEK for Modbus RS-485/COM2on a 12 V System2104955User DrawingTFIO Communication Interface Module (2100421BD) to XMV Modbus with RTD (RS-485)2102345User DrawingXRCG4 (2100355 BD) COM1 (RS-485) to XMVModbus with RTD2102347User DrawingNGC 8200 Port 2 (RS-485) to XMV Modbus withRTD2102350—Cyber securityThis product is designed to be connected, and communicate information and data, via a networkinterface, which should be connected to a secure network. It is the customer's sole responsibility toprovide and continuously ensure a secure connection between the product and the customer networkor any other network (as the case may be). The customer shall establish and maintain appropriatemeasures (such as, but not limited to, the installation of firewalls, application of authenticationmeasures, encryption of data, installation of antivirus programs, etc.) to protect the product, thenetwork, its system and interfaces against any kind of security breaches, unauthorized access,interference, intrusion, leakage and/or theft of data or information. ABB Inc. and its affiliates are notliable for damages and/or losses related to such security breaches, any unauthorized access,interference, intrusion, leakage and/or theft of data or information.Although ABB provides functionality testing on the products and updates that it releases, the customershould institute its own testing program for any product updates or other major system updates (toinclude, but not limited to, code changes, configuration file changes, third party software updates orpatches, hardware change out, etc.) to ensure that the security measures that the customer hasimplemented have not been compromised and that system functionality in the customer'senvironment is as expected.6 XS ERI ES 2106280 MN AA
—SafetyRead these instructions carefully prior to installation and commissioning. For reasons of clarity, theinstructions do not contain all details on all types of product and, therefore, not consider everyconceivable assembly, operating, or maintenance scenario. For further information or if specificproblems arise which are not addressed in the instructions, please ask the manufacturer for thenecessary information. The content of these instructions is neither part of nor provided for changing aprevious or existing agreement, promise, or legal relationship. All obligations on ABB result from therespective sales contract, which also contains the full and solely valid warranty clauses. These areneither limited nor extended by the content of these instructions.Observe warning signs on packaging and on the device, etc.Only qualified and authorized specialists are to be employed for the assembly, electrical connection,commissioning, and maintenance of the device, since they have the appropriate experience and thenecessary qualifications for such work. For example: Training or instruction and/or authorization to operate and maintain devices or systemsaccording to safety engineering standards for electrical circuits, high pressures, andaggressive mediaTraining or instruction in accordance with safety engineering standards regarding maintenanceand use of adequate safety systemsWARNING: According to EN 60 900, only sufficiently insulated tools may be used for theelectrical connection.The following regulations must also be considered:The applicable standards and safety regulations concerning the construction and operation ofelectrical installations, e.g., the regulation on technical working materials (safety guidelinesfor tools) The regulations and recommendations relating to explosion protection if devices withexplosion protection are to be installed The recommendations for safe working in the case of installation in an SIL loopThe device can be operated at high levels of pressure and with aggressive media. Serious injuryand/or considerable material damage can, therefore, be caused if the device is handled incorrectly.Ensure compliance with the regulations applicable in the country of use. Safety symbol conventionsThe following convention is used throughout this document to bring attention to importantinformation:IMPORTANT NOTE: This symbol indicates operator tips, particularly useful information, orimportant information about the product or its further uses.2106280 MNAA XS ERI ES 7
—1OverviewABB Totalflow Modbus implementation within the XSeries Generation 4 (G4) hardware architectureallows the use of Modbus protocol on all communication ports. Modbus protocol uses the master/slavecommunication concept. Slave devices respond only when commanded by the master. Each slave isidentified by an unsigned, one-byte number ranging from 1 to 247. A slave must send a singleresponse to a master’s request for data. The Modbus protocol is generally seen in two forms, RTU andASCII. Masters are configured in the G4 by the setup of an MRB (Master Request Block). Slaves areconfigured by the setup of an MRM (Modbus Register Map). These will be discussed in greater detaillater in this document.Totalflow PCCU software is required to interface to the Totalflow G4 hardware for setup andconfiguration of Modbus on communication ports.Figure 1 indicates the basic components required to implement Modbus in the Totalflow G4.Figure 1 Basic Modbus components1.1Modbus backgroundThe Modbus protocol is described in the document "Gould Modbus Protocol Reference Guide" publishedJanuary 1985 by Gould Inc., Programmable Control Division, Andover, Massachusetts.Modbus communications will always have devices designated as either masters or slaves. Only onemaster can exist on any system at one time, while multiple units can be designated as slaves. Thismaster-slave relationship is at the core of how Modbus communications work.Masters perform the role of requesting the slaves to report data to them or they write data into theregisters of the slaves. This requesting or writing of data is determined by the MRB (Master RequestBlock) set up within the master device communication port. Slave devices have a similar setup butdiffer in that they only respond to master requests and do not initiate any communications. In theslave device, an MRM (Modbus Request Map) is configured that builds a lookup table that matchesModbus addresses to Totalflow AAR (Application Array Registers). The Master can only request orwrite data to registers that the slave has mapped in its MRM.8 XS ERI ES 2106280 MN AA
Figure 2 MRB and MRM1.2Totalflow Modbus protocol formatThis information describes the format of Modbus communications protocol implemented by ABBTotalflow. Modbus messages may be one of two formats: RTU or ASCII.Table 2 Modbus RTU message frame formatPacketCRCN x 8 bitsThe packet field is the Modbus packet that is sentor received. Packet format varies with the functionperformed and the register group accessed.16-bitsThe error check field is a 16 bit cyclic redundancycheck calculated over the length of the packetfield.Table 3 Modbus ASCII message frame formatBOF:PacketLRC2 x Number of bytes in Modbus 8-bitspacketA colon (:)The packet field consists ofThe error check fieldcharacter is used hexadecimal ASCII characters is an 8 bitto indicaterepresenting the Modbuslongitudinalbeginning of apacket being sent or received. redundancy checkcalculated over theframe.The number of characters islength of the packettwice the number of bytes infield before it isthe Modbus packet becauseeach packet byte is converted converted tohexadecimal ASCII.into two hexadecimal ASCIIcharacters (0-9, A-F.)EOFCRReadyLFA carriagereturn and linefeed are usedto delineateend of frame.A carriagereturn and linefeed are usedto delineateend of frame.IMPORTANT NOTE: The total message frame length cannot exceed 256 bytes.1.3Totalflow Modbus implementationTotalflow Modbus supports RTU or ASCII mode. Support has also been added for long integer, floatingpoint, and archive record registers. Totalflow Modbus supports the following subset of the GouldModbus defined functions:Table 4 Gould Modbus defined functionsCode0103050616128-143FunctionRead BooleanRead RegistersSet Single BooleanSet Single RegisterSet Multiple RegisterException ResponseDescriptionReads group of Boolean registersReads group of 16/32 bit registersSet or clear a Boolean registerSet a 16/32 bit register to specified valueSet multiple 16/32 bit registersUsed in FCU response packets to indicate errors inprocessing function codes 1-16.2106280 MNAA XS ERI ES 9
Table 5 Read ntity16-bitsFunction8-bitsByte Count8-bitsDataN x 8 bitsFunction8-bitsRegister16-bitsDataN x 8 bitsFunction8-bitsRegister16-bitsDataN x 8 bitsTable 6 Read responseAddress8-bitsTable 7 Set queryAddress8-bitsTable 8 Set responseAddress8-bitsTable 9 Set multiple ntity16-bitsByte Count8-bitsDataN x 8 bitsTable 10 Set multiple Quantity16-bitsTable 11 Exception ss: the slave address of the FCU intended to receive the packet. Each FCU must beassigned a unique address in the range of 1 to 247. Function: a code which tells the FCU what to do or what data to send. The high order bit inthis field may be set by the FCU in the response packet to indicate an error response. Register: the register number of the FCU data item to fetch or set. For read functions, this isthe starting register number. Code: an error value for the exception response. Currently there are three values used; 1indicates that the function code is unsupported, 2 indicates the register number requested isinvalid, 3 indicates that too many data values were requested and that the maximum packetsize was exceeded. The maximum packet size for ASCII is 122 bytes and for RTU themaximum packet size is 250. Quantity: the number of consecutive registers to fetch or set. This field is not present in allpackets (only read and set multiples queries) Byte Count: the number of bytes of data being transferred. This field is not present in allpackets (only read and set multiple queries). Data: the actual data values being transferred. This field is not present in all packets. The sizeand format of the data values depend on the register group being accessed. The byte order ofdata items is high to low (MSB first, LSB last). 2How to use this guideThis document will instruct how to set up and operate Modbus in the ABB Totalflow G4 environmentincluding the basic steps required to configure three (3) different Modbus scenarios.2.1Procedure overviewThe following general steps are needed from a system perspective for a Modbus communication to beset up properly. The actual components required will depend on the specific scenario. Connect components to Totalflow Device (wiring)Connect Totalflow devices using PCCU10 XS ERI ES 2106280MN AA
2.2Configure communication ports in devicesProgram MRB/MRM blocksVerify Modbus communicationAssumptionsThis guide focuses on the initial configuration of Modbus in Totalflow G4. It is intended to give a basicunderstanding and instruction to implement Modbus communication in the G4 environment. Moreadvanced instructions are included in separate documents provided in Additional information at thebeginning of this document.The following is assumed:All components are installed correctlyEnd devices are calibratedAll components are wired correctly to provide or receive signalsPower is provided, and all the devices are connectedMinimal verification has been performed to ensure the devices are drawing the correct powervoltages for their operation. Proper grounding has been performed PCCU software is installed on the machine used to set up Modbus communications and isconfigured properly to communicate locally with the XSeries G4 hardware. 2.3RequirementsThe procedures described in this document require the following: PCCU software version 7.31 and later PCCU interface cable (serial, USB or IP) XRC (G4) Part 2103329-001 software version 2103132-039 and later XFC (G4) Part 2103328-001 software version 2102861-045 and later3Scenario 1: XFCG4 to XFCG4 with RS-485 link3.1XFC to XFC scenario overviewIn this scenario, use an XFCG4 as a master and an additional XFCG4 as a slave. The master will begiven the task of monitoring flow data from the slave. This will be accomplished via an RS-485hardwire communication link on Com 2 between both units. The link will use Modbus (RTU) as theprotocol and a register format of 32 bit Totalflow. Flow data from the slave needs to be read(updated) to the master every 3 seconds. Specific registers for flow rate, differential pressure, staticpressure, and temperature are required in the slave for this scenario. The master will assign theregisters to read from the slave in its Holding Registers interface for viewing updates.Figure 3 XFC to XFC3.2AssumptionsThis example makes the following installation assumptions: An XFCG4 flow computer will interface to another XFCG4 flow computer via a hardwire RS-485link on Com 2. See section 3.3 Connect components (wiring).Each XFCG4 has an RS-485 com module (part 2015193) installed in the Com port 2 position onthe board.2106280 MNAA XS ERI ES 11
The distance between the XFCs is less than 4000 feet. Modbus RTU protocol and 32 bit Totalflow Register format will be used. Master XFCG4 requires flow data from slave XFCG4. PCCU software is available for connections to both master and slave devices.3.3Connect components (wiring)IMPORTANT NOTE: The wiring of Com 2 depends on the XSeries device used and whetherthese are direct connections (onboard) or use extension modules. Wire the terminationswith the device powered off.The example used in this basic configuration illustrates the connections required to use an XFC toconnect to another XFC to create a hardwire RS-485 connection. The diagram for this scenario showsdirect connections to the board.1.2.3.Connect the XFCs together via an RS-485 cable on J4 pin 12 (Bus ) and pin 13 (Bus-).After completing connections, power on the devices.Verify that the power on sequence is correct.Figure 4 Comm2 XFC (master) to XFC (slave) wiringJ113911J123181011COMM 1COMM 21BJ41213141516XA2A234BUS 5BUS -17678XA111XFCTable 12 Legend for Comm2 ATTXD/BUS BUS RXD/BUSBUSRTSCTSDTRCDTXD/BUS RXD/BUSRTSCTSOPERItem17Another XFC18RS-485 Commmodule12 XS ERI ES 2106280MN AACommRS-23212 OUTRS-485IN
3.4Connect using PCCUVerify that the devices can connect using PCCU and change the view to prepare for configuration.1.2.3.Connect a laptop with PCCU software to the device.Click Entry on the top menu bar and verify that PCCU establishes a connection with the device.Click View at the top menu, then choose Expert from the drop-down list.Figure 5 Expert view setup3.5Configure master Setup tabThis instruction sets up the master XFCG4 first. The master Setup tab will provide for necessary setupof the com port on the master.1.2.Go to TOTALFLOW Spare-com2 Setup an
Adapting K-TEK for Modbus RS-485/COM2 on a 12 V System 2104955 User Drawing TFIO Communication Interface Module (2100421 BD) to XMV Modbus with RTD (RS-485) 2102345 User Drawing XRC G4 (2100355 BD) COM1 (RS-485) to XMV Modbus with RTD 2102347 User Drawing NGC 8200 Port 2 (RS-485) to XMV Modbus with
NP ModBus TCP N System Configuration Example 8 Add a ModBus Master Port and Node Expand the "MB NP Modbus TCP" branch on the I/O Configuration Form by clicking on the . Expand the Modbus TCP by clicking on the . Expand the "ModBus Port NP ModBus TCP Master Port" branch on the I/O Configuration Form by clicking on the . Expand the Nodes branch on the I/O Configuration Toolbox by .
3. System description 5 3.1 Modbus 5 3.2 CIM 200 Modbus RTU 5 3.3 CIM 260 3G/4G cellular Modbus 5 3.4 CIM 500 Modbus TCP 5 4. Specifications 6 4.1 CIM module 6 4.2 CIM 200 Modbus RTU 6 4.3 CIM 260 3G/4G cellular 7 4.4 CIM 500 Modbus TCP 7 5. CIM 200 Modbus RTU setup 8 5.1 Setting the Modbus transmission speed 8 5.2 Setting the stop bits and the .
Modbus/TCP Modbus Master/Slave A Modbus master/slave network provides a protocol for data transfer and programming with a single RTU master and up to 247 slave . The Modbus/TCP KEPServer driver supports Modbus and Mailbox device models. Modbus Device Model. Publication 2711P-UM002B-EN-P - March 2007 Modbus Applications PanelView Plus
2.2 Modbus RTU connection to the SIMOCODE pro device SIMOCODE pro Modbus RTU 12 Configuration Manual, 04/2015, A5E33498234002A/RS-AA/001 2.2 Modbus RTU connection to the SIMOCODE pro device Connecting Modbus RTU to the SIMOCODE pro V Modbus basic unit Modbus RTU can be connected to the SIMOCODE pro V basic unit both viathe connectingFile Size: 1MB
User Guide: FAAST XT Fire Alarm Aspiration Sensing Technology Modbus Protocol Schema 10 5 Rev A Modbus Resources 1. Modbus Application Protocol Specification, Version 1.1b3, Modbus Organization, Hopkinton, MA, 2012 2. Modbus over Serial Line Specification and Implementation Guide, Version 1.02, Modbus Organization, Hopkinton, MA, 2006
Advantech WebAccess Device Driver Guide Modicon Modbus TCP/IP Version 4.5 rev 0 Advantech Corp., Ltd. page 3 1. Modbus TCP/IP Device Communications 1.1 Introduction to Modbus Ethernet /TCPIP Advantech WebAccess SCADA Node provides a Modbus master interface using Modbus RTU protocol for communicating with Modbus slave devices. Slave
Modbus(2) AirTF . Modbus(3) RH . Modbus(4) WS_mph . Modbus(5) WindDir . Modbus(6) SlrW . Modbus(7) Rain_in . NextScan . EndProg . Near the end of the program are several lines that copy values from measurements to values within an array. For example, this line copies the air temperature measurement into the second value of an array called .
Modbus TCP Ethernet EN . Version 0.14 . MODBUS TCP ETHERNET EN - V0.14 Modbus TCP Ethernet EN RapidoScan, Modbus TCP and Ethernet, EN.docx Preface . But because of the master - slave principle of Modbus a controlled polling by a master unit is necessary. Therefore, to transmit a measurement result via Modbus an additional query .
