Modbus Applications For PanelView Plus and PanelView Plus CE Terminals 2711P User Manual
Important User Information Solid state equipment has operational characteristics differing from those of electromechanical equipment. Safety Guidelines for the Application, Installation and Maintenance of Solid State Controls (publication SGI-1.1 available from your local Rockwell Automation sales office or online at http://literature.rockwellautomation.com) describes some important differences between solid state equipment and hard-wired electromechanical devices.
Table of Contents Preface Topics Covered. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 Software Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 Additional Resources. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 Chapter 1 Installing Software Objectives. . . . . . . . . . . . . . Install RSView Studio . . . . . Install KEPServer Enterprise. Firmware Upgrade Wizard. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table of Contents Chapter 6 Installing KEPServer Drivers on Terminal Objectives. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Firmware Upgrade Wizard. . . . . . . . . . . . . . . . . . . . . . . . . Preparing Terminal for Firmware Upgrade . . . . . . . . . . Copy FUP Files to Development Computer . . . . . . . . . . . . Upgrade Firmware using a Compact Flash Card . . . . . . . . . Upgrade Firmware using a Network (Ethernet) Connection. . . . . . . 41 41 41 42 42 46 .. .. .
Table of Contents 5 Appendix E Modbus (RTU) Serial Address Definitions Output Coils . . . . . . . . . . . . . . . . . . . . . . . Input Coils . . . . . . . . . . . . . . . . . . . . . . . . . Internal Registers . . . . . . . . . . . . . . . . . . . . Holding Registers . . . . . . . . . . . . . . . . . . . . Magnetek Address Descriptions . . . . . . . . . . Elliott Flow Computer Address Descriptions . Omni Address Descriptions . . . . . . . . . . . . . Daniel S500 Address Descriptions . . . . . . . .
Table of Contents Publication 2711P-UM002B-EN-P - March 2007
Preface For communication with controllers, RSView Machine Edition products are configured with: • RSLinx Enterprise for most Rockwell Automation networks or • KEPServer Enterprise for RSView OPC servers. The KEPServer OPC server expands PLC and device connectivity options by incorporating 26 communication drivers for the PanelView Plus and PanelView Plus CE platforms, and over 31 communication drivers for RSView Machine Edition running on a desktop.
• Chapter 7 Compiling, Downloading, and Running Application Shows how to compile a runtime .mer file, connect your PanelView Plus/PanelView Plus CE terminal to a Modbus network, download the .mer file to the terminal, and run the application. • Chapter 8 Troubleshooting - Covers common error types that occur during runtime and how you can correct these errors. Software Requirements The following software must be installed on the development desktop: • RSView Studio 3.
Chapter 1 Installing Software Objectives To develop RSView ME applications, configure KEPServer drivers, and use these drivers with applications that run on PanelView Plus/PanelView Plus CE terminals, the following software must be loaded on your development computer: • RSView Studio for ME or RSView Enterprise • KEPServer Enterprise • Firmware Upgrade Wizard Refer to the installation information provided with RSView Studio and KEPServer Enterprise for the latest details on installation requirements.
Installing Software Install KEPServer Enterprise KEPServer Enterprise is used to: • configure the KEPServer driver • create tags • test communications on the desktop. KEPServer Enterprise is included with RSView Studio and can be installed from: • a CD or • downloaded from the Rockwell Software web site at www.software.rockwell.com. KEPServer runs as a service and an icon will display in the toolbar.
Chapter 2 Modbus KEPServer Drivers Objectives This chapter provides an overview of MODBUS KEPServer drivers available in the RSView Enterprise software. • Modbus Master/Slave – Modbus (RTU) Serial – Modbus Unsolicited Serial • Modbus ASCII • 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 devices.
Modbus KEPServer Drivers Modbus Master/Slave Networks See Chapter 7 for cable information.
Modbus KEPServer Drivers 13 Modbus ASCII Modbus ASCII protocol is typically used to connect to other ASCII devices that support the Modbus ASCII protocol. KEPServer support includes: • Modbus ASCII compatible devices • Flow Computers using Daniels/Omni/Elliott register addressing Modbus/TCP Modbus/TCP is a Modbus messaging protocol over Ethernet TCP/IP and is intended for supervision and control of automation equipment.
Modbus KEPServer Drivers Refer to the MSTR instruction in your Modicon documentation for details on sending unsolicited requests to the Modbus Ethernet driver. PanelView Plus PanelView Plus Ethernet Ethernet Switch Switch Master Controller PanelView Plus Guidelines for Developing Modbus Applications The section provides general guidelines for creating and running Modbus applications on PanelView Plus/PanelView Plus CE terminals.
Chapter 3 Configuring KEPServer Drivers for Modbus Objectives This chapter shows how to use KEPServer Enterprise software to configure KEPServer drivers for Modbus protocols including Ethernet TCP/IP, RTU Serial, Unsolicited Serial, and ASCII Serial. You will: • create a project (.
Configuring KEPServer Drivers for Modbus 2. Create a new KEPServer project (.pfe) file. From the menu, select File>Save As and save the project as a .pfe file. Select the Default Project File (.pfe) The steps in this section ensure that the correct project file is used in your RSView Studio application. When RSView Studio creates a runtime application and the application contains the KEPware OPC server, RSView Studio will merge the KEPware project file (.pfe) into the runtime file (.mer).
Configuring KEPServer Drivers for Modbus 17 You should now see the following: 4. Click the the default. TIP Configure Drivers for Modbus Protocols button and OK to accept the new project as The KEPServer configuration is not archived with the RSView Studio application backup (.apa) file. If you need to reuse the project configuration file on another computer, copy the .pfe file.
Configuring KEPServer Drivers for Modbus Step 3 -Select a Device Driver Select a driver from the drop down list. The table below lists the correct driver for each Modbus protocol.
Configuring KEPServer Drivers for Modbus 19 Modbus RTU Serial Modbus Unsolicited Serial Publication 2711P-UM002B-EN-P - March 2007
Configuring KEPServer Drivers for Modbus Modbus ASCII Step 6 - Set the Optimization Method for Data Requests The New Channel - Write Optimization dialog sets the optimization method for data requests. Select the best optimization for your application and click Next. For more information on KEPServer read and write optimization options refer to the online Driver help.
Configuring KEPServer Drivers for Modbus 21 Step 7 -Select Socket Usage (Applies to Modbus/TCP only) The New Channel - Socket Usage dialog controls how the Modbus Ethernet driver will utilize Windows sockets when establishing a connection to the target device. For a normal Modbus Ethernet enabled device, the default Use Multiple Sockets for device connection (checked) mode of operation is designed to give the best performance from the driver.
Configuring KEPServer Drivers for Modbus Step 8 - View and Verify Channel Summary The New Channel - Summary dialog provides a summary of the new channel settings. Verify the settings below and click Finish.
Configuring KEPServer Drivers for Modbus 23 Modbus Unsolicited Serial Modbus ASCII Serial TIP The red X next to the channel name will disappear when a destination device is added under this driver. Step 9 - Save Project File From the Menu bar, select File>Save or click the Save button.
Configuring KEPServer Drivers for Modbus Add A Device Now that a new channel is defined, you need to add a new device to the channel. In most cases, selecting the default settings will allow you to quickly configure and connect to a device. Step 1 - Add a Device Add a device by clicking on the Click to add a device hypertext or the New Device icon. This will bring up the new device wizard. Here you’ll add the information pertinent to the controller that you are going to communicate with.
Configuring KEPServer Drivers for Modbus 25 Step 4 - Select a Device ID The device you are defining may be multidropped as part of a network of devices. To communicate with the device, it must be assigned a unique ID. In the New Device - ID dialog, enter a unique Device ID (decimal address) to identify the controller on the network. Enter the Device ID and click Next. For this Protocol: Device ID Range Data Format Modbus/TCP (1) xxx.xxx.xxx.
Configuring KEPServer Drivers for Modbus Step 6 - Configure Tag Database Options (Doesn’t apply to Unsolicited Serial or ASCII Protocols) In the New Device - Database Creation dialog, click Next to accept the default tag database configuration options. The automatic OPC tag database generation features of the server have been designed to make the setup of your OPC application a Plug and Play operation.
Configuring KEPServer Drivers for Modbus 27 Step 7 - Enter Device Settings In the New Device - Settings dialog, accept the default settings by clicking Next Modbus/TCP Modbus RTU Serial Publication 2711P-UM002B-EN-P - March 2007
Configuring KEPServer Drivers for Modbus Modbus Unsolicited Serial and Modbus ASCII Step 8 - Set the Block Size for Reading Data from Device (Doesn’t apply to Unsolicited Serial Protocol) The New Device - Block Sizes dialog sets the largest block size for reading I/O (coils) and data tables (Registers). Click Next.
Configuring KEPServer Drivers for Modbus 29 Reasons to Change the Default Block Sizes include: • The device may not support block read/write operations of the default size. Smaller Modicon PLCs and non-Modicon devices may not support the maximum data transfer lengths supported by the Modbus Ethernet network. • The device may contain non-contiguous addresses. If this is the case and the driver attempts to read a block of data that encompasses undefined memory, the device will probably reject the request.
Configuring KEPServer Drivers for Modbus Step 10 - View and Verify the Device Summary Information The New Device - Summary dialog provides a summary of the new device settings. Verify the information and click Finish.
Configuring KEPServer Drivers for Modbus 31 Modbus Unsolicited Serial Modbus ASCII Step 11 - Save Project File From the Menu bar, select File>Save or click the Save button.
Configuring KEPServer Drivers for Modbus Create Tags With a channel and device defined, you are ready to create tags within the KEPServer software. These tags are used to link to the controller addresses. The procedure is similar to creating an HMI tag database. For details on valid data types and addressing, see Appendices A - E. 1. In the right hand pane, click on the Click to add a static tag text.
Configuring KEPServer Drivers for Modbus 33 Replace the ’xx with your table number. For example, the Address for table #1 would be 40101. KEPServer allows you to validate the address based on the device you will be talking to. Your project configuration should now list the tags in the right pane. 3. From the Menu bar, select File>Save or click the Save button.
Configuring KEPServer Drivers for Modbus Publication 2711P-UM002B-EN-P - March 2007
Chapter 4 Testing KEPServer Communications Objectives This chapter shows how to test KEPServer communications on a development computer to verify your project configuration and tags. Use the OPC Quick Client Included with the KEPServer server installation is a simple tool for testing OPC tags called the OPC Quick Client. When you create a new KEPServer configuration, there are several system and communications tags that are also created.
Testing KEPServer Communications The resulting window not only allows you to write new data to the controller, but it also displays the current value of the tag.
Chapter 5 Making KEPServer Drivers and Tags Available in RSView Studio Objectives Now that you’ve configured and tested KEPServer communications, you are ready to make the KEPServer driver and tags available in RSView Studio. This chapter will show you how to add an OPC data server to the RSView Studio project. Create an OPC Data Server KEPServer is an OPC data server. You need to add this server to the RSView Studio project. 1.
Making KEPServer Drivers and Tags Available in RSView Studio 5. Select KEPServerEnterprise and click OK. 6. Enter a name for the KEPServer driver and click OK. Informational messages appear at the bottom of your RSView Studio window indicating that the Server has started and is available on the computer. Any tags created earlier in the KEPServer software are now available for the HMI using the standard RSView Studio tag browser.
Making KEPServer Drivers and Tags Available in RSView Studio 39 Browse KEPServer Tags TIP For additional information on working with tags, see Chapter 6 of the RSView Machine Edition User’s Guide (ViewME-UM003) available under the RSView Studio help menu. 1. Double click or right-click on an object to open its Properties dialog. 2. On the Connections tab, click the Value's the FactoryTalk Tag Browser. button to open 3.
Making KEPServer Drivers and Tags Available in RSView Studio Publication 2711P-UM002B-EN-P - March 2007
Chapter 6 Installing KEPServer Drivers on Terminal Objectives If you plan to run the Machine Edition project on a PanelView Plus or PanelView Plus CE terminal, the corresponding CE-based KEPServer components must be installed. This chapter will show you how to use the Firmware Upgrade Wizard (FUW) utility to install the KEPServer drivers on the terminals. Firmware Upgrade Wizard The Firmware Upgrade Wizard (FUW) will add the necessary KEPServer components to the terminal firmware.
Installing KEPServer Drivers on Terminal Copy FUP Files to Development Computer Download the Firmware Upgrade (FUP) files with the KEPServer drivers to your development computer before using the FUW. The FUP files are available on the Firmware Upgrade Media Kit (Cat. No. 2711P-RU31O) which you can order through your local Allen-Bradley distributor. Run the *.exe file to unzip the files.
Installing KEPServer Drivers on Terminal 43 3. From the Firmware source folder list, select the location of the firmware files. The default location is C:\Program Files\Rockwell Software\RSView Enterprise\FUPs. From the Upgrade firmware version list, select the version of the firmware you want to upgrade to, then press Next. 4. Select the appropriate KEPServer drivers and press Next. If the selected FUP file does not support the KEPServer drivers, this dialog will not appear.
Installing KEPServer Drivers on Terminal 5. Select Finish to copy the firmware source files to the location specified in step 2. TIP If the files were created in a separate folder on a local hard drive, copy the files to the root directory of the compact flash card. 2. Upgrade Firmware in Terminal using Firmware Upgrade Card 1. Insert the compact flash card into the card slot of a powered PanelView Plus terminal. A dialog appears indicating the firmware upgrade is about to occur. 2.
Installing KEPServer Drivers on Terminal 45 3. If other PanelView Plus terminals exist on the same Ethernet network, the following error may display: Error registering name on network (may be duplicate). Change in system Control Panel and try again. Ignore this error. It will be corrected during the upgrade. Press OK to acknowledge error and wait for terminal to reset. TIP If a USB mouse is available you can acknowledge this error by selecting OK. 4.
Installing KEPServer Drivers on Terminal Upgrade Firmware using a Network (Ethernet) Connection You can upgrade the firmware in a terminal that is connected to a desktop computer using a Serial, Ethernet or Network (using RSLinx Enterprise) connection. • Network connection requires RSLinx Enterprise where you select the terminal on an existing network. • Serial connection requires a RAS connection to be set up on computer. During the RAS setup, you select the COM port.
Installing KEPServer Drivers on Terminal 47 2. Select Upgrade firmware on terminal and press OK. 3. Select Network connection and press Next. Use the Ethernet and Serial connections only if the firmware upgrade is unsuccessful. 4. Locate the PanelView Plus terminal on your Ethernet network via its IP address. Skip to Step 6 if you found the terminal. If you do not see the terminal, right click on the Ethernet driver and add the device to the browse tree.
Installing KEPServer Drivers on Terminal 5. Double-click on EthernetIP Devices. Select the appropriate terminal and press OK. PanelView Plus CE 700 PanelView Plus CE 1000 PanelView Plus CE 1250 6. Enter the IP address for the terminal and press OK. 7. Select the terminal to be upgraded and press OK.
Installing KEPServer Drivers on Terminal 49 8. From the Firmware source folder text box, select the location of the firmware files. The default location is C:\Program Files\Rockwell Software\RSView Enterprise\FUPs. From the Upgrade firmware version list, select the version of the firmware you want to upgrade to, then select Next. PanelView Plus 700 9. Select the appropriate KEPServer drivers and select Next. If the selected FUP file does not support the KEPServer drivers, this dialog will not appear.
Installing KEPServer Drivers on Terminal 10. Press Finish to start the upgrade. 11. Press Yes to continue the upgrade process. If the terminal was properly prepared for the upgrade, no applications should be running. 12. Firmware files are downloaded to the terminal. This may take several minutes to 15 minutes. When the download is complete, press OK to reset the terminal.
Installing KEPServer Drivers on Terminal 51 13. On touch or touch/screen terminals, you must calibrate the touch screen by selecting pointers in all four corners of the screen and pressing the middle of the screen when prompted. 14. Ignore the following message if it appears. It means RSView ME is being installed. Do not touch the two buttons that appear with the message. Machine edition may be corrupted. Do you want to download firmware? 15.
Installing KEPServer Drivers on Terminal Publication 2711P-UM002B-EN-P - March 2007
Chapter 7 Compiling, Downloading, and Running Application Objectives This chapter shows how to: • compile a runtime RSView ME application file • download and load application on terminal. • connect terminal to a Modbus network • run application. Compile a Runtime Application File You are now ready to build the Machine Edition runtime (.mer) file to be downloaded to a PanelView Plus/PanelView Plus CE terminal. TIP B Before compiling the .mer file, verify that the correct .pfe project file is selected.
Compiling, Downloading, and Running Application Download Application to Terminal Typically, downloading an application to a terminal is accomplished using the RSLinx Enterprise File Transfer Utility. You can download an application using a Compact Flash card, a serial connection, or an Ethernet connection. Refer to the RSView Machine Edition User Manual (ViewME-UM003). 1. From the menu bar, select Tools>Transfer Utility… 2. On the Download tab, click the button. 3. Select the .
Compiling, Downloading, and Running Application 6. When the download is complete, click 55 and turn your attention to the terminal. Load Application [F1] button 7. Click the Load Application [F1] Button. 8. Select the .mer file and click the Load [F2] button. 9. Click Yes [F7] to replace the terminal's current RSLinx Enterprise communication configuration with the one stored in the application file.
Compiling, Downloading, and Running Application Connect Terminal to Modbus Network Before running your application, you need to connect the PanelView Plus/PanelView Plus CE terminal to a Modbus network using either: • Modbus serial cables or • Modbus Ethernet cables Modbus Serial Cables The serial port on a PanelView Plus/PanelView Plus CE terminal is different than a desktop computer. Typically, you just need to add a null modem adapter to a cable that works with a desktop computer.
Compiling, Downloading, and Running Application 57 Null Modem Cable To construct a null modem cable, refer to the following pinout: Terminal Controller 9-pin 25-pin 9-pin 3 3 3 2 2 2 5 7 5 1 8 1 4 20 4 6 6 6 8 5 8 7 4 7 Modbus Ethernet Cables The RJ45 connector pinout for the PanelView Plus or VersaView Terminal is shown below.
Compiling, Downloading, and Running Application Run Application Now that your PanelView Plus/PanelView Plus CE terminal contains the loaded application and is connected to a Modbus network, you can run the application. 1. Click the Run Application [F2] button to launch application.
Chapter 8 Troubleshooting Objectives This chapter lists common errors that occur during application development as well as errors that occur during runtime. To diagnose error messages that are generated while developing the KEPServer driver, refer to the KEPServer online help for the appropriate driver and refer to the error description. Common Errors Some of the most common errors made during application development are listed below: • The .mer file was compiled with the wrong .pfe file.
Troubleshooting Error Error Type Possible Cause Solution Bad address in block [x to y] on device ’’ Fatal addresses failing in this block This error is reported when the driver attempts to read a location in a PLC that does not exist. For example, in a PLC that only has holding registers 40001 to 41400, requesting address 41405 would generate this error. Once this error is generated, the driver will not request the specified block of data from the PLC again.
Appendix A Data Types This appendix describes valid data types for creating tags. This information is also available in the Modbus driver online help in KEPServer Enterprise.
Data Types Publication 2711P-UM002B-EN-P - March 2007
Appendix B Modbus/TCP Address Definitions This appendix describes valid tag addressing for Modbus/TCP communications. This information is also available in the Modbus/TCP driver online help in KEPServer Enterprise. KEPServer drivers use decimal addressing.
Modbus/TCP Address Definitions Internal Registers Defaults are shown in bold. Internal Registers Decimal Addressing Type Word, Short, BCD Format 3xxxxx Security Read only (1) Range 300001 - 365536 Type Boolean Format 3xxxxx.bb Security Read only (1) Range 3xxxxx.0 - 3xxxxx.15 Type Float, DWord, Long, LBCD Format 3xxxxx Security Read only (1) Range 300001 - 365535 (1) Hexadecimal Addressing H3yyyyy H300001 - H31000 H3yyyyy.c 3yyyyy.0 - 3yyyyy.
Modbus/TCP Address Definitions Holding Registers 65 Default types are shown in bold. Holding Registers Decimal Addressing Type Word, Short, BCD Format 4xxxxx Security Read/Write Range 400001 - 465536 Type Boolean Format 4xxxxx.bb Security Read/Write Range 4xxxxx.0 - 4xxxxx.15 Type Float, DWord, Long, LBCD Format 4xxxxx Security Read/Write Range 400001 - 465535 Type String HiLo Byte Order Format 400001.2H - 465536.240H .
Modbus/TCP Address Definitions String Support The Modbus model supports reading and writing holding register memory as an ASCII string. When using holding registers for string data, each register will contain two bytes of ASCII data. The order of the ASCII data within a given register can be selected when the string is defined. The length of the string can be 2 to 240 bytes and is entered in place of a bit number. The length must be entered as an even number.
Modbus/TCP Address Definitions Mailbox Addressing 67 Default types are shown in bold. Mailbox Addressing Decimal Addressing Type Word, Short, BCD Format 4xxxxx Security Read/Write Range 1 - 65536 Type Boolean Format 4xxxxx.bb Security Read/Write Range xxxxx.0 - xxxxx.15 Type Float, DWord, Long, LBCD Format 4xxxxx Security Read/Write Range 1 - 65535 Hexadecimal Addressing H4yyyyy 1 - 10000 H4yyyyy.c yyyyy.0 - yyyyy.
Modbus/TCP Address Definitions Instromet Addressing Decimal Addressing Area Short Word Registers (16 Bit) Type Word, Short Range 400000 - 400199 Security Read only Area Short Word Registers (32 Bit) Type DWord, Long Range 400200 - 400399 Security Read only Area Floating Point Registers (32 Bit) Type Float Range 400400 - 400599 Security Read only TIP Publication 2711P-UM002B-EN-P - March 2007 The normal Instromet addressing does not include the 40xxx.
Appendix C Modbus ASCII Address Definitions This appendix describes valid tag addressing for Modbus ASCII communications. This information is also available in the Modbus driver online help in KEPServer Enterprise. KEPServer drivers use decimal addressing. Output Coils Output Coils Decimal Addressing Type Boolean Format 0xxxxx Security Read/Write Range 000001 - 065535 Example: The 255th output coil would be addressed as ’0255’ using decimal addressing or ’H0FF’ using hexadecimal addressing.
Modbus ASCII Address Definitions Internal Registers Defaults are shown in bold. Internal Registers Decimal Addressing Type Word, Short, BCD Format 3xxxxx Security Read only (1) Range 300001 - 365535 Type Boolean Format 3xxxxx.bb Security Read only (1) Range 3xxxxx.0 - 3xxxxx.15 Type Float, DWord, Long, LBCD Format 3xxxxx Security Read only Range 300001 - 365534 (1) For unsolicited device 127.0.0.1.0, these locations are Read/Write.
Modbus ASCII Address Definitions Holding Registers 71 Default types are shown in bold. Holding Registers Decimal Addressing Type Word, Short, BCD Format 4xxxxx Security Read/Write Range 400001 - 465535 Type Boolean Format 4xxxxx.bb Security Read/Write Range 4xxxxx.0 - 4xxxxx.
Modbus ASCII Address Definitions Publication 2711P-UM002B-EN-P - March 2007
Appendix D Modbus Unsolicited Serial Address Definitions This appendix describes valid tag addressing for Modbus Unsolicited ASCII communications. This information is also available in the Modbus driver online help in KEPServer Enterprise. KEPServer drivers use decimal addressing.
Modbus Unsolicited Serial Address Definitions Internal Registers Defaults are shown in bold. Internal Registers Decimal Addressing Type Word, Short, BCD Format 3xxxxx Security Read only (1) Range 300000 - 309999 Type Boolean Format 3xxxxx.bb Security Read only (1) Range 3xxxxx.0 - 3xxxxx.15 Type Float, DWord, Long, LBCD Format 3xxxxx Security Read only (1) Range 300001 - 309998 (1) For unsolicited device 127.0.0.1.0, these locations are Read/Write.
Modbus Unsolicited Serial Address Definitions Holding Registers 75 Default types are shown in bold. Holding Registers Decimal Addressing Type Word, Short, BCD Format 4xxxxx Security Read/Write Range 400001 - 409999 Type Boolean Format 4xxxxx.bb Security Read/Write Range 4xxxxx.0 - xxxxx.15 Type Float, DWord, Long, LBCD Format 4xxxxx Security Read/Write Range 400001 - 409998 Type String HiLo or LoHiByte Order Format 400001.2H - 409999.240H .
Modbus Unsolicited Serial Address Definitions String Support The Modbus model supports reading and writing holding register memory as an ASCII string. When using holding registers for string data, each register will contain two bytes of ASCII data. The order of the ASCII data within a given register can be selected when the string is defined. The length of the string can be 2 to 240 bytes and is entered in place of a bit number. The length must be entered as an even number.
Appendix E Modbus (RTU) Serial Address Definitions This appendix describes valid tag addressing for Modbus (RTU) Serial communications. This information is also available in the Modbus driver online help in KEPServer Enterprise. KEPServer drivers use decimal addressing.
Modbus (RTU) Serial Address Definitions Internal Registers Defaults are shown in bold. Internal Registers (Function Code 04) Decimal Addressing Type Word, Short, BCD Format 3xxxxx Security Read only (1) Range 300001 - 365536 Type Boolean Format 3xxxxx.bb Security Read only (1) Range 3xxxxx.0 - 3xxxxx.15 Type Float, DWord, Long, LBCD Format 3xxxxx Security Read only (1) Range 300001 - 365535 (1) Hexadecimal Addressing H3yyyyy H300001 - H310000 H3yyyyy.c H3yyyyy.0 - H3yyyyy.
Modbus (RTU) Serial Address Definitions Holding Registers 79 Default types are shown in bold. Holding Registers (Function Codes: 03, 06(1), 16) Decimal Addressing Type Word, Short, BCD Format 4xxxxx Security Read/Write Range 400001 - 465536 Type Boolean Format 4xxxxx.bb Security Read/Write Range 4xxxxx.0 - 4xxxxx.15 Type Float, DWord, Long, LBCD Format 4xxxxx Security Read/Write Range 400001 - 465535 Type String HiLo Byte Order Format 400001.2H - 465536.240H .
Modbus (RTU) Serial Address Definitions String Support The Modbus model supports reading and writing holding register memory as an ASCII string. When using holding registers for string data, each register will contain two bytes of ASCII data. The order of the ASCII data within a given register can be selected when the string is defined. The length of the string can be 2 to 240 bytes and is entered in place of a bit number. The length must be entered as an even number.
Modbus (RTU) Serial Address Definitions Magnetek Address Descriptions 81 The following table provides the general ranges of data available for a Magnetek GPD 515 Drive. Consult the Magnetek Modbus RTU Technical Manual, part number TM4025, for information on how specific drive parameters can be accessed using Modbus RTU addressing. In all cases, the letter H (used to signify Hex addressing) should precede the desired address.
Modbus (RTU) Serial Address Definitions Elliott Flow Computer Address Descriptions Default data types for dynamically defined tags are shown in bold where appropriate. Elliott Flow Computer Addressing Address Range Data Type Access Output Coils 000001 - 065536 Boolean Read-Write Input Coils 100001 - 165536 Boolean Read Only Internal Registers 300001 - 365536 300001 - 365535 3xxxxx.0 - 3xxxxx.
Modbus (RTU) Serial Address Definitions Omni Address Descriptions 83 Default data types for dynamically defined tags are shown in bold where appropriate.
Modbus (RTU) Serial Address Definitions OMNI Addressing - 16 Bit Integer Data Addresses Address Range Data Type Access Custom Data Packet #1 3001 - 3040 Short, Word, BCD Read-Write Custom Data Packet #2 3041 - 3056 Short, Word, BCD Read-Write Custom Data Packet #3 3057 - 3096 Short, Word, BCD Read/Write Misc.
Modbus (RTU) Serial Address Definitions 85 OMNI Addressing - 8 Character ASCII String Data Address Range Data Type Access Meter Run ASCII Data 4n01 - 4n39 n=Number of Meter Run String Read-Write Scratch Pad ASCII Data 4501 - 4599 String Read-Write User Display Definition Variables 4601 - 4640 String Read/Write Station Auxiliary Input Variables 4707 - 4710 String Read/Write Meter Station ASCII Data 4801 - 4851 String Read/Write Meter Run 16-Bit Integer Data 4707 - 4710 String Rea
Modbus (RTU) Serial Address Definitions OMNI Addressing - 32 Bit IEEE Floating Point Data Address Range Data Type Access Reserved Data 6001 - 7000 Float, Long, DWord, LBCD Read-Write Digital to Analog Outputs 7001 - 7024 Float, Long, DWord, LBCD Read-Write User Variables 7025 - 7088 Float, Long, DWord, LBCD Read-Write Programmable Accumulator 7089 - 7099 Float, Long, DWord, LBCD Read-Write Meter Run Data 7n01 - 7n99 n=Number of Meter Run Float, Long, DWord, LBCD Read-Write Scrat
Modbus (RTU) Serial Address Definitions 87 OMNI Addressing - 16 Bit Integer Configuration Data Address Range Data Type Access Meter Run #1 13001 - 13013 Short, Word, BCD Read-Write Meter Run #2 13014 - 13026 Short, Word, BCD Read-Write Meter Run #3 13027 - 13039 Short, Word, BCD Read-Write Meter Run #4 13040 - 13052 Short, Word, BCD Read-Write Prover Configuration 13053 - 13073 Short, Word, BCD Read-Write General Flow Configuration 13074 - 13084 Short, Word, BCD Read-Write Seria
Modbus (RTU) Serial Address Definitions Daniel S500 Address Descriptions Default data types are dynamically defined tags are shown in bold where appropriate.
Index Symbols .mer file 53 .
Index MODBUS/TCP 13 address definitions 63 holding registers 65 input coils 63 Instromet addressing 65 internal registers 64 mailbox addressing 65 output coils 63 N network connections 56 O OMNI address definitions 83 OPC Data Server 37 OPC Quick Client 35 P project .
Rockwell Automation Support Rockwell Automation provides technical information on the web to assist you in using its products. At http://support.rockwellautomation.com, you can find technical manuals, a knowledge base of FAQs, technical and application notes, sample code and links to software service packs, and a MySupport feature that you can customize to make the best use of these tools.
