Modbus TCP/IP Integration Guide - Carrier

1y ago
16 Views
4 Downloads
1.39 MB
20 Pages
Last View : 21d ago
Last Download : 21d ago
Upload by : Albert Barnett
Transcription

Modbus TCP/IPIntegration GuideCARRIER CORPORATION 2010A member of the United Technologies Corporation family · Stock symbol UTX · Catalog No. 11-808-399-01 · 4/21/2010

Table of ContentsBefore-you-begin checklist . 1Overview . 1The integration process. 21 Create custom equipment in ApplicationBuilder .2To format a Modbus TCP/IP address . 4To format a CCN address . 5Optional Modbus TCP/IP IP addressing method . 7To edit an integration or CCN point address. 72 Assign and download custom equipment in i-Vu CCN .7Configure integration and CCN points. 83 Connect the i-Vu Link to the third-party device.94 Set up the Modbus TCP/IP driver properties .95 Verify the i-Vu Link is set up correctly .9To get a diagnostic capture . 10Appendix Modbus TCP/IP Protocol Conformance Statement . 12Modbus TCP/IPi

Before-you-begin checklistYou need the following items, information, and skills for the integration process. A points list for each Modbus TCP/IP device that includes register addresses and read/writecapabilities. Points lists are usually available from the third-party manufacturer’srepresentative or website. The IP addresses and unit ID's of the Modbus TCP/IP devices. Verification that all communication properties have been set on the Modbus TCP/IP devicesModbus TCP/IP Verification of communications through the port that the i-Vu Link will connect to Experience creating custom control programs with ApplicationBuilder Experience installing, wiring, setting up, and downloading custom control programs to the i-VuLink The latest version of Ethereal from the Ethereal website (http://www.ethereal.com/),downloaded and installed. Use this network analysis tool for troubleshooting.1

OverviewModbus TCP/IP Integration with the i-Vu LinkYou can integrate Modbus TCP/IP devices into an i-Vu CCN system with a i-Vu Link acting as a client device.i-Vu LinkModbus portE110/100 BaseT EthernetModule driverModbus:drv ivulink modbus latest version .driver *Read/write capabilityCan read from and write to the third-party equipmentIntegration points supported500Third partySupported equipmentAny device that supports the Modbus TCP/IP protocolNetwork media typeEthernetQuantity of devices you canphysically connect to i-Vu Link'sEthernet portUp to 30 Modbus TCP/IP connections. Connections couldbe to a Modbus TCP/IP server device or to a ModbusTCP/IP server device that is acting as a Gateway to otherModbus serial devices. Each Modbus TCP/IP servergateway can have one serial modbus slave connected overEIA-232, or up to 247 modbus slaves connected over EIA485.* The i-Vu Link driver supports Modbus devices connected to Port S2 and BACnet or Modbus devicesconnected on the Ethernet port simultaneously. The third-party point count for the i-Vu Link is the total of the2 ports.Modbus TCP/IP1

The integration processThe integration processFollow the steps in this document to integrate one or more third party Modbus TCP/IP devices into an i-VuCCN system using an i-Vu Link. To install and network the i-Vu Link, see the i-Vu Link Installation and Start-upGuide.1 Create custom equipment in ApplicationBuilder1Start ApplicationBuilder.2Select equipment type: CCN Values Only - to read and write values on the CCN network and to display those points on agraphic Integration Values Only - to read and write values from the third party network and to display thosepoints on a graphic CCN Link Integration - to share values from the third party network with the i-Vu Link on the CCNnetwork and to display those points on a graphic3Click Next.4Type a name for the custom equipment (i.e., Hot Water System).NOTE The name must not exceed 21 characters!5Enable English or Metric units.6Choose engineering options for your application (Schedule and Setpoint, Runtime, etc.)7Click Next.8Add Elements to your application.NOTE Elements are a collection of input/output points that perform a specific operation. Theinput/output point that is reading or writing to the Modbus TCP/IP network is called an integration point.Integration points may be used in conjunction with CCN points to share data between the ModbusTCP/IP network and the CCN network.The available Elements that you can add to your custom equipment in ApplicationBuilder are:Point typeUsed forRead CCN PointReading an analog or binary value from the CCN networkIn: CCN Values, Link IntegrationCarrier Text PointReading Text value from a CCN deviceIn: CCN Values, Link IntegrationSetpoint WriteAllows CCN setpoint value to be “edited” directly fromgraphicIn: CCN Values, Link Integration2Modbus TCP/IP

The integration processPoint typeUsed forLink Integration Point toCCN PointReading an analog or binary value from the third partydevice and then writing that value to the CCN networkIn: Link IntegrationLink CCN Passive Point toIntegration PointExposing an analog or binary value to the CCN network sothat it can be written to the third party networkIn: Link IntegrationRead Integration PointReading an analog or binary value from the third partydeviceIn: Read Integration, Link IntegrationLink CCN Point toIntegration PointReading an analog or binary value from a CCN device andthen writing it to the third party networkIn: Link IntegrationLink Integration Point toCCN Passive PointReading an analog or binary value from the third partydevice and then exposing that value to the CCN networkIn: Link IntegrationLink BACnet variable toCCN PointAllows an analog or binary value from BACnet to writethat value to the CCN networkIn: Link Integration9As you add Elements, enter the requested information for the integration or CCN points: Display Text - the name of the point as it will appear in i-Vu CCN (i.e., Frequency) Reference Base - the name that will be added to each point that makes up the Element, so that allpoints have a unique identifier (i.e.,input Freq, trendFreq, output Freq) - this name must be unique(do not copy and paste) Input Address - enter the Modbus TCP/IP or CCN addressDefine the Modbus TCP/IP or CCN address string using the syntax for each point in the list, asdescribed below: Input Scaling - enter variablesNOTE Use Scaling when the value you are reading from the Modbus TCP/IP or CCN device needs tobe scaled before showing the value on a graphic or trend. Scaling information can be found in thethird party points list.Example: You have an integration point set up to read the motor temperature of a variable speeddrive. The third party points list shows that this value will be given in degrees C, but you want todisplay it in degrees F on a graphic. Therefore, using the formula F 9/5( C) 32, the scaling/unitconversion fields for the integration point would be filled out as follows: ([value read] 0) x 1.8 32 Output Address - enter the Modbus TCP/IP or CCN address, as described below. Output Scaling - enter variablesContinuing the example above, if you wanted the graphic to display values in F, but then youwanted to share that value with the CCN network in C, the scaling for the CCN Passive Point wouldbe:([value read] 0) x1 0Modbus TCP/IP3

The integration process10 Click Next.11 Equipment Name - type a new equipment name if desired.12 Save Location - browse to a location where you would like to save the new custom equipment.13 Click Save.To format a Modbus TCP/IP addressUse the information below to format a valid address in each integration point that you use to read or write to aModbus TCP/IP device.CAUTION!When integrating third-party devices into an i-Vu CCN system, most communication problems are caused byincorrect data or typos in the integration point's Address 8.168.1this kind ofvalue.use this type ofintegrationpoint.with thisregister type.0 to 65,535Unsigned 16-bit integerInput registerHolding registerANIUint0 to 4,294,967,296Unsigned, 32-bit –32,768 to 32,767Signed 16-bit integerInput registerHolding 483,648 to2,147,483,647Signed, 32-bit Value with decimal pointInput registerHolding registerANIFloat30001–39999 2or40001–49999 2(not Unit)and a Modbus registeraddress in this range.130001–39999or40001–49999Modbus TCP/IP

The integration processTo.Writethis kind ofvalue.use this type ofintegrationpoint.with thisregister type.0 or 1CoilDiscrete (binary) outputBNIDo1–99990 or 1Discrete (binary) inputBNIDi10001–199990 or 1Input registerHolding registerBNIBITn (where n is avalue 0-15 definedin points list)30001–39999or40001–499990 to 65,535Unsigned 16-bit integerHolding registerANOUint40001–49999–32,768 to 32,767Signed 16-bit integerHolding registerANOSint40001–49999Value with decimal pointHolding registerANOFloat40001–49999 20 or 1CoilDiscrete (binary) outputBNODo1–99990 or 1Holding registerBNOBITn (where n is avalue 0-15 definedin points list)40001–49999(not Unit)and a Modbus registeraddress in this range.11The Modbus register address must be a decimal value. If you see the letters A–F in register addressesanywhere in a points list, use a scientific calculator to convert these hexadecimal values to decimalvalues.If the Modbus register address (sometimes called register, address, code, or parameter) is not in thisrange, take the number given, then add 1 to coils; add 10,001 to discrete inputs; add 30,001 to inputregisters (sometimes given as 3X); and add 40,001 to holding registers (sometimes given as 4X).In rare cases, the number given is not in the range shown above and is greater than 9999. Type a 4(function code) at the beginning of an input register or a 3 at the beginning of a holding register. Forexample, to read holding register number 313567, type 413568. (Add 1 as described in the paragraphabove.)2Each Float has 2 consecutive Modbus register addresses. Use the lower number in the integration pointaddress.To format a CCN addressThere are three different methods for defining the CCN address strings.1They can be manually typed in ApplicationBuilder.2You can use Copy table point in i-Vu CCN's table interface to copy CCN point information directly from aCCN table to ApplicationBuilder's "ccn://" address field.3You can use Map to Point in i-Vu CCN's table interface to map the CCN points from your customequipment file directly to CCN table data.NOTE Your custom equipment must already be downloaded in the i-Vu Link to use this method. (Proceedto Assign and download custom equipment in i-Vu CCN (page 7) first).Modbus TCP/IP5

The integration processMethod 1: Type the address manually in ApplicationBuilder1If you are actively reading or writing a point on a CCN device, then manually type in the CCN device'saddress, Table Name, and Point Name that you wish to read or write.ccn://link/ Table Name / Point Name ("link" indicates the CCN device that the custom equipmenthas been mapped to)orccn:// bus, element / Table Name / Point Name 2/TEMP2If the point is a CCN passive point (i.e, it's just being exposed to the CCN network), then type:ccn://passive/ point name , where point name is the name that you have chosen for this CCN point.Example: ccn://passive/freqMethod 2: Copy table point in i-Vu CCN1Launch i-Vu CCN.2Select the desired equipment in the navigation tree.3Expand the tables underneath that equipment.4Find the specific table and point that you want to read or write.5Click Copy in the table interface.6Inside of ApplicationBiuilder, hit CTRL-V to copy the CCN address from the table to the "ccn://" addressfield.Method 3: Map to point in i-Vu CCN61Launch i-Vu CCN.2Select the desired equipment in the navigation tree.3Expand the tables underneath that equipment.4Find the specific table and point that you want to read or write.5In the table interface, navigate to the Map to Point column.6From the drop-down menu, select the point in the custom equipment that should be mapped.7Click OK.Modbus TCP/IP

The integration processOptional Modbus TCP/IP IP addressing methodIf the unit ID of every third-party device in the system is unique, but they all use the same IP address, you cansave time by omitting the IP addresses from the individual integration point addresses and mapping the unitID's to their IP address in i-Vu CCN. See example below.1On i-Vu CCN's navigation tree, right-click on the custom equipment that you created in ApplicationBuilder.Select Driver Properties.2Select Protocols Modbus TCP/IP IP Addressing.To edit an integration or CCN point addressYou can edit an integration or CCN point address in the following places: In ApplicationBuilder In i-Vu CCN on the custom equipment's Properties page Equipment tab In i-Vu CCN on the custom equipment's Properties page Network Points tab2 Assign and download custom equipment in i-Vu CCNModbus TCP/IP1Click the menu button in i-Vu CCN, then select System Setup.2In the navigation tree, right-click the area where you want to place the custom equipment. Select AddEquipment from the drop-down menu.7

The integration process3Make the following entries:FieldNotesDisplay NameType an equipment name (i.e. ABB Drive).Associate withIf your i-Vu Link is connected to CCN devices: Enable CCN Device and fill in the bus and elementnumber of the CCN device that this customequipment will be linked to.NOTE This "association" is what allows you to use theterm "link" in CCN address strings for this customequipment rather than manually typing in the bus,element number into each CCN address string.If your i-Vu Link is NOT connected to CCN devices (onlyModbus TCP/IP devices):Equipment Enable CCN Link and pick the i-Vu Link that isphysically connected to the Modbus TCP/IP network.1.Click Add.2.Browse to the .equipment file that was generated inApplicationBuilder.3.Click Continue.4.When message appears "File uploaded successfully",click Close.4If you have already created a custom equipment graphic for this third party device in ViewBuilder, youcan also add that graphic from this screen. Under Views, click Add and browse to your .view file. ClickContinue. When message appears File added successfully, click Close. The custom equipment shouldnow appear in the navigation tree.5Click Exit Setup and the custom equipment will be downloaded to the i-Vu Link.Configure integration and CCN pointsYou can now configure the integration and CCN points.NOTE If you have already done this in ApplicationBuilder, skip this section.81In the navigation tree, select the desired custom equipment.2Click Properties page Equipment tab to see a list of all integration points.3Define the Modbus TCP/IP or CCN address string using the syntax for each point in the list, as describedin Formatting a Modbus TCP/IP address or Formatting a CCN address in this document.4Apply unit conversion and scaling in the remaining fields, if applicable.5After configuring each integration point, click OK to download the changes.Modbus TCP/IP

The integration process3 Connect the i-Vu Link to the third-party deviceUse one of the following CAT5 or higher Ethernet cables: A crossover cable to connect the i-Vu Link directly to a Modbus TCP/IP server or gateway A straight-through cable to connect the i-Vu Link to a hub or switch, and a second straight-through cableto connect the hub or switch to a Modbus TCP/IP server or gatewayMaximum cable length: 328 feet (100 meters)1Turn off the i-Vu Link's power.2Check the communications wiring for shorts and grounds.3Wire the i-Vu Link's Port E1 to the third-party device.NOTE Port E1 will still be capable of BACnet communication.4Turn on the i-Vu Link's power.4 Set up the Modbus TCP/IP driver properties1On i-Vu CCN's navigation tree, right-click on your custom equipment.2Select Driver Properties.3Expand Protocols and select Modbus TCP/IP.4Under Port Configuration, select Modbus TCP/IP as the communication type.5Set the fields under Timing Configuration. These settings can typically be left at their default values.6Set the fields under Protocol Configuration using information from the third-party manufacturer'srepresentative. Select the Details checkbox for help. Click Apply to save changes.7On the navigation tree, select Protocols.8In the Protocol Status table, verify that Modbus TCP/IP shows Running on Port E1. If the status showsNot Running or the wrong port, repeat step 4.5 Verify the i-Vu Link is set up correctlyModbus TCP/IP1On i-Vu CCN's navigation tree, select the custom equipment.2On the Properties page, select the Network Points tab.9

The integration processIf.Then.You see the point value youexpect with no errors in the ErrorcolumnYou have successfully established communication with thethird-party device.A point shows question marksinstead of valuesi-Vu CCN is not communicating with the i-Vu Link. Troubleshootcommunications. See the i-Vu Link's Installation Guide.The point name is redLook in the Error column for one of the following error codesand descriptions. 1 - Communications Disabled for this MicroblockEnable the integration point's Communications Enabledfield on i-Vu CCN's Network Points tab. 3 - Address Error - Unknown Protocol SpecifiedSelect the correct port on the Modbus TCP/IP driver pagein i-Vu CCN, verify that Address in the integration point iscorrect.A value is incorrectVerify that: The Address in the integration point is correct. The retrieved value is scaled properly, if necessary. Forexample, scaled from Celsius to Fahrenheit.Refer to thethird-party manufacturer's documentation for scalinginformation.If the above solutions do not resolve the problem, gather the following information for technical support: A diagnostic capture. See To get a diagnostic capture below.A screenshot of the Driver Properties - right-click on the custom equipment in the navigation tree selectDriver Properties Properties page and the Modbus (Modicon) Properties pageA screenshot of the custom equipment's Properties page Network Points tab showing addresses anderrorsTo get a diagnostic captureUse Ethereal, a network analysis tool, to capture to a file the Ethernet communication between the i-Vu Linkand the Modbus TCP/IP device.PREREQUISITES The i-Vu Link's IP address The longest integration point or CCN point refresh time in the custom equipment that has the error youare troubleshooting. In i-Vu CCN, view the custom equipment's Properties page Network Points tab tosee all the refresh times. Download the latest release of Ethereal and WinPcap from the Ethereal website(http://www.ethereal.com/). Install WinPcap first, then Ethereal. Use the installation wizards' defaultsettings.1Connect your laptop's Ethernet port to the i-Vu Link's hub or to a separate hub on the Ethernet.NOTE If using a separate hub, the network cannot have a gateway, switch, or bridge between the laptopand the i-Vu Link.10Modbus TCP/IP

The integration process2On your desktop, select Start All Programs Ethereal Ethereal.3Select Capture Options.4In the Interface field, select the laptop's Ethernet card that is connected to the hub.5Verify that the IP address that appears below the Interface field is the IP address of the laptop that isconnected to the i-Vu CCN system.6Create a filter that tells Ethereal to capture just the i-Vu Link's communication:a)Click Capture Filter.b)Click New.c)In the Filter name field, type a name for the filter. For example, i-Vu Link module 39d)In the Filter string field, type host i-Vu Link's IP address . For example, host192.168.168.39e)Click OK.7Under Display Options, select Update list of packets in real time.8Click Start or Capture.9Turn the i-Vu Link's power off, then on, using the Power switch or i-Vu CCN's restartmodule manualcommand.10 Run the capture for one of the following periods of time: If all integration point refresh times are one minute or less, run the capture for 5 minutes from thetime you turn the i-Vu Link's power back on. If any integration point refresh time is longer than 1 minute, run the capture for 5 times the longestmicroblock refresh time.11 In Ethereal, verify that the Protocol column shows some Modbus or TCP entries. If not, stop the captureand make sure the network has only the hub(s) between your laptop and the i-Vu Link, then repeat steps3 through 8.12 On the menu bar, select Capture Stop.13 Select File Save As to save your capture file.NOTE Save in the default folder or clicknext to Browse for other folder to select a different folder.14 Send this file, the integration point's IP address, and the third-party device's IP address to TechnicalSupport.Modbus TCP/IP11

Appendix Modbus TCP/IP Protocol Conformance StatementAppendix Modbus TCP/IP Protocol Conformance StatementThe following Modbus TCP/IP features and commands are supported by the i-Vu Link. See the Modbus TCP/IPwebsite (http://www.modbus.org) for complete Modbus TCP/IP protocol information.ModesMedia typeBaud RateData BitsParityStop bitsRTU*EIA-23212007None*1*ASCIIEIA-485, 2-wire24008*Odd24800Even96001920038400*Most commonly used value12Function codes - commandFunction code purpose01 - Read Coil StatusRead discrete outputs02 - Read Input StatusRead discrete inputs03 - Read Holding RegistersRead holding registers04 - Read Input RegistersRead input registers05 - Force Single CoilWrite discrete outputs, one at a time06 - Preset Single RegisterWrite holding registers, one at a time15 - Force Multiple CoilsWrite discrete outputs16 - Preset Multiple RegistersWrite holding registersModbus TCP/IP

CARRIER CORPORATION 2010A member of the United Technologies Corporation family · Stock symbol UTX · Catalog No. 11-808-399-01 · 4/21/2010

Any device that supports the Modbus TCP/IP protocol : Network media type . Ethernet : Quantity of devices you can physically connect to i-Vu Link's Ethernet port . Up to 30 Modbus TCP/IP connections. Connections could be to a Modbus TCP/IP server device or to a Modbus TCP/IP server device that is acting as a Gateway to other Modbus serial devices.

Related Documents:

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 .

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 .

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 .

The complete Modbus TCP/IP Application Data Unit is embedded into the data field of a standard TCP frame and sent via TCP to well-known system port 502, which is specifically reserved for Modbus applications. Modbus TCP/IP clients and servers listen and receive Modbus data via port 502. We can see that the operation of Modbus over Ethernet is .

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

ABOUT THIS GUIDE 2 Modbus/TCP Protocol Guide The groov EPIC processor (GRV-EPIC-PR1) acts as a Modbus slave, and this guide covers how to use EPIC as a Modbus slave. However, groov View running on the EPIC processor acts as a Modbus master; for instructions on using Modbus/TCP devices with a groov View master, see the groov View User's Guide. For energy monitoring units, this guide is only a .

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

Pendidikan Akuntansi FKIP Universitas Sebelas Maret. Penetapan profil dan learning outcome ini dimaksudkan untuk membantu pemerintah dalam menyiapkan guru akuntansi yang bermutu menurut persepsi mahasiswa, alumni, dosen, pengguna lulusan, Asosiasi Profesi, dan pengambil keputusan. Sumber data penelitian ini adalah 96 orang mahasiswa, 248 orang alumni, 15 orang dosen, 15 orang pengguna lulusan .