2711P-UM002B-EN-P, Modbus Applications - Rockwell Automation

1y ago
17 Views
2 Downloads
2.97 MB
92 Pages
Last View : 2d ago
Last Download : 2m ago
Upload by : Giovanna Wyche
Transcription

ModbusApplicationsFor PanelView Plus andPanelView Plus CE Terminals2711PUser Manual

Important User InformationSolid state equipment has operational characteristics differing from those ofelectromechanical equipment. Safety Guidelines for the Application,Installation and Maintenance of Solid State Controls (publication SGI-1.1available from your local Rockwell Automation sales office or online athttp://literature.rockwellautomation.com) describes some importantdifferences between solid state equipment and hard-wired electromechanicaldevices. Because of this difference, and also because of the wide variety ofuses for solid state equipment, all persons responsible for applying thisequipment must satisfy themselves that each intended application of thisequipment is acceptable.In no event will Rockwell Automation, Inc. be responsible or liable forindirect or consequential damages resulting from the use or application ofthis equipment.The examples and diagrams in this manual are included solely for illustrativepurposes. Because of the many variables and requirements associated withany particular installation, Rockwell Automation, Inc. cannot assumeresponsibility or liability for actual use based on the examples and diagrams.No patent liability is assumed by Rockwell Automation, Inc. with respect touse of information, circuits, equipment, or software described in this manual.Reproduction of the contents of this manual, in whole or in part, withoutwritten permission of Rockwell Automation, Inc., is prohibited.Throughout this manual, when necessary, we use notes to make you awareof safety considerations.WARNINGIMPORTANTATTENTIONIdentifies information about practices or circumstances that can causean explosion in a hazardous environment, which may lead to personalinjury or death, property damage, or economic loss.Identifies information that is critical for successful application andunderstanding of the product.Identifies information about practices or circumstances that can leadto personal injury or death, property damage, or economic loss.Attentions help you identify a hazard, avoid a hazard, and recognizethe consequenceSHOCK HAZARDLabels may be on or inside the equipment, for example, a drive ormotor, to alert people that dangerous voltage may be present.BURN HAZARDLabels may be on or inside the equipment, for example, a drive ormotor, to alert people that surfaces may reach dangeroustemperatures.

Table of ContentsPrefaceTopics Covered. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7Software Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8Additional Resources. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8Chapter 1Installing SoftwareObjectives. . . . . . . . . . . . . .Install RSView Studio . . . . .Install KEPServer Enterprise.Firmware Upgrade Wizard. . 9. 91010Objectives. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Modbus Master/Slave . . . . . . . . . . . . . . . . . . . . . . . . .Modbus (RTU) Serial . . . . . . . . . . . . . . . . . . . . . . .Modbus Unsolicited Serial . . . . . . . . . . . . . . . . . . .Modbus ASCII. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Modbus/TCP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Modbus Device Model . . . . . . . . . . . . . . . . . . . . . .MailBox. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Guidelines for Developing Modbus Applications . . . . .Create a Modbus Application . . . . . . . . . . . . . . . . .Compile, Download and Run a Modbus application.1111111113131313141414Chapter 2Modbus KEPServer DriversChapter 3Configuring KEPServer Drivers for Objectives. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15Create a Project File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15ModbusSelect the Default Project File (.pfe) . . . .Configure Drivers for Modbus Protocols.Add a Channel. . . . . . . . . . . . . . . . .Add A Device . . . . . . . . . . . . . . . . .Create Tags. . . . . . . . . . . . . . . . . . . . . .1617172432Chapter 4Testing KEPServerCommunicationsObjectives. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35Use the OPC Quick Client . . . . . . . . . . . . . . . . . . . . . . . . . . 35Chapter 5Making KEPServer Drivers andTags Available in RSView Studio3Objectives. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37Create an OPC Data Server . . . . . . . . . . . . . . . . . . . . . . . . . 37Browse KEPServer Tags. . . . . . . . . . . . . . . . . . . . . . . . . . . . 39Publication 2711P-UM002B-EN-P - March 2007

4Table of ContentsChapter 6Installing KEPServer Drivers onTerminalObjectives. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .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.414141424246.53535456565758Chapter 7Compiling, Downloading, andRunning ApplicationObjectives. . . . . . . . . . . . . . . . . . . . . .Compile a Runtime Application File . . .Download Application to Terminal . . .Connect Terminal to Modbus Network.Modbus Serial Cables . . . . . . . . . . .Modbus Ethernet Cables. . . . . . . . .Run Application . . . . . . . . . . . . . . . . .Chapter 8TroubleshootingObjectives. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59Common Errors. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59Runtime Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59Appendix AData TypesAppendix BModbus/TCP Address DefinitionsOutput Coils . . . . . . .Input Coils . . . . . . . .Internal Registers . . .Holding Registers . . .Mailbox Addressing. .Instromet Addressing.636364656768Appendix CModbus ASCII Address Definitions Output Coils . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69Input Coils . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69Internal Registers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70Holding Registers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71Appendix DModbus Unsolicited SerialAddress DefinitionsPublication 2711P-UM002B-EN-P - March 2007Output Coils . . . .Input Coils . . . . .Internal RegistersHolding Registers.73737475

Table of Contents5Appendix EModbus (RTU) Serial AddressDefinitionsOutput Coils . . . . . . . . . . . . . . . . . . . . . . .Input Coils . . . . . . . . . . . . . . . . . . . . . . . . .Internal Registers . . . . . . . . . . . . . . . . . . . .Holding Registers . . . . . . . . . . . . . . . . . . . .Magnetek Address Descriptions . . . . . . . . . .Elliott Flow Computer Address Descriptions .Omni Address Descriptions . . . . . . . . . . . . .Daniel S500 Address Descriptions . . . . . . . .IndexRockwell Automation Support . . . . . . . . . . . . . . . . . . . . . . . 93Installation Assistance . . . . . . . . . . . . . . . . . . . . . . . . . . 93New Product Satisfaction Return . . . . . . . . . . . . . . . . . . . 93.7777787981828388Publication 2711P-UM002B-EN-P - March 2007

6Table of ContentsPublication 2711P-UM002B-EN-P - March 2007

PrefaceFor communication with controllers, RSView Machine Editionproducts 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 connectivityoptions by incorporating 26 communication drivers for the PanelViewPlus and PanelView Plus CE platforms, and over 31 communicationdrivers for RSView Machine Edition running on a desktop.This guide will show you how to configure KEPServer drivers,specifically Modbus drivers, for RSView ME applications that run on: PanelView Plus CE terminals, PanelView Plus terminals, or the Windows 2000/XP environment.Using configured KEPServer drivers in your RSView ME application,the terminals will be able to communicate with devices on a Modbusnetwork.Topics Covered Chapter 1 Installing Software - Covers software installation forRSView Studio, RSView Enterprise, KEPServer Enterprise and theFirmware Upgrade Wizard. Chapter 2 Overview of Modbus Protocols - Gives an overview ofModbus Master/Slave Protocol and each of the KEPServerdrivers for Modbus communication protocols. Chapter 3 Configuring KEPServer Drivers for Modbus - Showshow to use KEPServer Enterprise software to configureKEPServer drivers for Modbus protocols. For each driver, youwill create a channel, add a device, and create tags. The driver issaved to a .pfe project file that you will set as the default project. Chapter 4 Testing KEPServer Communications - Shows how touse the OPC Quick Client to test KEPServer communications forthe driver and tags created in Chapter 3. Chapter 5 Making KEPServer Driver and Tags Available inRSView Studio - Shows how to create an OPC data server inRSView Enterprise or RSView Studio. This server will allow youto access the KEPServer driver and tags from your RSView MEapplication. Chapter 6 Installing KEPServer Drivers on Terminal - Shows howto use the Firmware Upgrade Wizard to install KEPServer driverson PanelView Plus/PanelView Plus CE terminals.7Publication 2711P-UM002B-EN-P - March 2007

8 Chapter 7 Compiling, Downloading, and Running Application Shows how to compile a runtime .mer file, connect yourPanelView Plus/PanelView Plus CE terminal to a Modbusnetwork, download the .mer file to the terminal, and run theapplication. Chapter 8 Troubleshooting - Covers common error types thatoccur during runtime and how you can correct these errors.Software RequirementsThe following software must be installed on the developmentdesktop: RSView Studio 3.0, or later KEPServer Enterprise software Firmware Upgrade WizardAdditional ResourcesYou might want to consult the following sources for additionalinformation: KEPServer Enterprise Software online help RSView Enterprise or RSView Studio online help PanelView Plus User Manual, publication no. 2711P-UM001An electronic version of the PanelView Plus user manual isavailable tion 2711P-UM002B-EN-P - March 2007

Chapter1Installing SoftwareObjectivesTo develop RSView ME applications, configure KEPServer drivers, anduse these drivers with applications that run on PanelViewPlus/PanelView Plus CE terminals, the following software must beloaded on your development computer: RSView Studio for ME or RSView Enterprise KEPServer Enterprise Firmware Upgrade WizardRefer to the installation information provided with RSView Studio andKEPServer Enterprise for the latest details on installation requirements.Install RSView StudioRSView Studio Enterprise or RSView Studio for Machine Editionsoftware is installed from: a CD or downloaded from the Rockwell Software website atwww.software.rockwell.com.IMPORTANTA current registered serial number is required to downloadsoftware from the Rockwell Software website.The installation menu with instructions will appear when inserting theCD into a computer or you can run setup.exe from the root directory.9Publication 2711P-UM002B-EN-P - March 2007

10Installing SoftwareInstall KEPServerEnterpriseKEPServer Enterprise is used to: configure the KEPServer driver create tags test communications on the desktop.KEPServer Enterprise is included with RSView Studio and can beinstalled from: a CD or downloaded from the Rockwell Software web site atwww.software.rockwell.com.KEPServer runs as a service and an icon will display in the toolbar.IMPORTANTA current registered serial number is required to downloadsoftware from the Rockwell Software website.The software can be installed by running the setup.exe file from theCD or downloaded version.IMPORTANTFirmware Upgrade WizardWhen installing KEPServer Enterprise, be sure to select theModbus drivers if you are not doing a full install.The Firmware Upgrade Wizard is used to install KEPServer drivers andupgrade firmware in the following devices: PanelView Plus PanelView Plus CEThe Firmware Upgrade Wizard is installed automatically with RSViewStudio.The Firmware Upgrade (FUP) files with the KEPServer drivers isavailable at http://support.rockwellautomation.com underDownloads.Publication 2711P-UM002B-EN-P - March 2007

Chapter2Modbus KEPServer DriversObjectivesThis chapter provides an overview of MODBUS KEPServer driversavailable in the RSView Enterprise software. Modbus Master/Slave– Modbus (RTU) Serial– Modbus Unsolicited Serial Modbus ASCII Modbus/TCPModbus Master/SlaveA Modbus master/slave network provides a protocol for data transferand programming with a single RTU master and up to 247 slavedevices. A Modbus network links distributed devices with a centralcomputer terminal or controller for supervisory control and dataacquisition. Up to 247 nodes can be connected at data rates of up to19,200 baud using media such as twisted pair cable, common carrierphone lines, or microwave transmission. This network is commonlyused in SCADA application over large areas such as the water/wastewater and oil & gas industries.Modbus (RTU) SerialModbus (RTU) Serial is the protocol for a master and includes RTSsupport for radio modems. Supported devices include: Modbus compatible devices Elliott Flow Computer Magnetek GPD 515 Drive Omni Flow Computer Daniel S500 Flow Computer Dynamic Fluid Meter (DFM) SFC3 InstrometModbus Unsolicited SerialModbus Unsolicited Serial simulates up to 247 Modbus slave devices.Supported devices include Modbus compatible devices.11Publication 2711P-UM002B-EN-P - March 2007

12Modbus KEPServer DriversModbus Master/Slave NetworksSee Chapter 7 for cable information.Direct ConnectionPanelView Plus(Modbus Serial orUnsolicited Serial Driver)RS-232/RS-485 Converter(1)(1)Controller (Master or Slave)1761-NET-AIC or Comparable DeviceMaster/Slave Network (Multiple Slave Terminals Connect to one Master Controller)(3) PanelView Plus Slave DevicesEach uses Modbus Unsolicited Serial DriverPanelView PlusPanelView PlusPanelView PlusMaster erters(1) PanelView Plus Master DeviceUses the Modbus Serial DriverPanelView PlusModbus DeviceRS-232/RS-485ConvertersModbus DeviceRS-232/RS-485ConvertersModbus DeviceRS-232/RS-485ConvertersModem ConnectionPanelView Plus(2) PanelView Plus Slave Devices ModbusEach uses the Modbus Unsolicited Serial DriverMaster ControllerModemsPanelView PlusPublication 2711P-UM002B-EN-P - March 2007

Modbus KEPServer Drivers13Modbus ASCIIModbus ASCII protocol is typically used to connect to other ASCIIdevices that support the Modbus ASCII protocol. KEPServer supportincludes: Modbus ASCII compatible devices Flow Computers using Daniels/Omni/Elliott register addressingModbus/TCPModbus/TCP is a Modbus messaging protocol over Ethernet TCP/IPand is intended for supervision and control of automation equipment.The most common use of this protocol is for Ethernet attachment ofPLCs, I/O modules, and gateways to other simple field buses or I/Onetworks.The Modbus/TCP KEPServer driver supports Modbus and Mailboxdevice models.Modbus Device ModelThe most common Modbus device model is where the driver connectsto physical devices (e.g. Modicon TSX Quantum, other Modbus OpenEthernet compatible devices) and acts as a device on the networkwith a device ID equivalent to the machine's IP address. The driveraccepts any unsolicited commands it receives and attempts to processthem as if it were another PLC.MailBoxThe Mailbox model determines the manner unsolicited requests arehandled. By defining a mailbox device, the driver does not act like aPLC on the network (as described above). Instead, it acts as a storagearea for each and every mailbox device defined. When the driverreceives an unsolicited command, the driver detects the IP address themessage came from and places the data in the storage area allocatedfor the device. If the message comes from a device with an IP addressthat has not been defined as a mailbox device, the message is notprocessed. Any client application that reads/writes to this type ofdevice, reads/writes to the storage area contained in the driver, notthe physical device.Publication 2711P-UM002B-EN-P - March 2007

14Modbus KEPServer DriversRefer to the MSTR instruction in your Modicon documentation fordetails on sending unsolicited requests to the Modbus Ethernet driver.PanelView PlusPanelView PlusEthernet EthernetSwitch SwitchMaster ControllerPanelView PlusGuidelines for DevelopingModbus ApplicationsThe section provides general guidelines for creating and runningModbus applications on PanelView Plus/PanelView Plus CE terminals.Create a Modbus ApplicationGeneral StepsDescriptionReferenceStep 1Create a .pfe project file in KEPServerEnterprise.Chapter 3Step 2Configure a KEPServer Modbus Driver. Add achannel and device to the project file.Chapter 3Step 3Enter application tags.Chapter 3Step 4Set your .pfe file as the default project file.Chapter 3Step 5Test KEPServer communications to verify yourproject file and tags.Chapter 4Step 6Create an OPC Data Server to make your tagsavailable in RSView Studio.Chapter 5Compile, Download and Run a Modbus applicationPublication 2711P-UM002B-EN-P - March 2007General StepsDescriptionReferenceStep 1Create a firmware upgrade card that containsthe KEPWare driver and upgrade the terminal.Chapter 6Step 2Compile the RSView .mer application.Chapter 7Step 3Download the .mer runtime file to terminal.Chapter 7Step 4Connect the terminal to the Modbus network.Chapter 7Step 5Run the application.Chapter 7

Chapter3Configuring KEPServer Drivers for ModbusObjectivesThis chapter shows how to use KEPServer Enterprise software toconfigure KEPServer drivers for Modbus protocols including EthernetTCP/IP, RTU Serial, Unsolicited Serial, and ASCII Serial. You will: create a project (.pfe) for the drivers set the project file as the default projectFor each Modbus driver in your project file, you will: add a channel add a device (or controller) create tagsCreate a Project FileThe first thing you need to do is create a project file.1. Double-click the KEPServer Enterprise icon in the Systray toopen the default project window below.15Publication 2711P-UM002B-EN-P - March 2007

16Configuring KEPServer Drivers for Modbus2. 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 ProjectFile (.pfe)The steps in this section ensure that the correct project file is used inyour RSView Studio application.When RSView Studio creates a runtime application and the applicationcontains the KEPware OPC server, RSView Studio will merge theKEPware project file (.pfe) into the runtime file (.mer). The project filethat RSView Studio uses is defined by the Default project field in theGeneral tab of the Tools Options menu in KEPware ServerEnterprise.TIPThis may not be the current configuration running inKEPware Server Enterprise. If you are testing theapplication on a PC, make sure the project name inthe title bar of KEPware Server Enterprise matchesthe Project default field.1. From the Menu bar, select Tools Options 2. On the General tab, click theproject textbox.button next to the Default3. Select the desired .pfe file and click thePublication 2711P-UM002B-EN-P - March 2007button.

Configuring KEPServer Drivers for Modbus17You should now see the following:4. Click thethe default.TIPConfigure Drivers forModbus Protocolsbutton and OK to accept the new project asThe KEPServer configuration is not archived with theRSView Studio application backup (.apa) file. If youneed to reuse the project configuration file onanother computer, copy the .pfe file.This section shows how to configure KEPServer drivers that will allowa PanelView Plus/PanelView Plus CE terminal to communicate on aModbus network.Add a ChannelThe first step in communicating to any device using the KEPServersoftware is to create a channel. A channel describes the protocol anddriver properties used for communication. While a single channel canbe used to communicate to multiple devices, separate channels mustbe defined for each unique driver to be used. Only one projectconfiguration file can run at a time, but it may contain multiplechannels and devices.Step 1 - Add a New ChannelClick on the New Channel icon or right-click anywhere in the leftpane. This will bring up the new channel wizard.Step 2 - Enter a Channel NameEnter a unique name for the channel.Publication 2711P-UM002B-EN-P - March 2007

18Configuring KEPServer Drivers for ModbusStep 3 -Select a Device DriverSelect a driver from the drop down list. The table below lists thecorrect driver for each Modbus protocol.For this Protocol:Select this Driver:Modbus/TCPModbus EthernetModbus RTU Serial (Master)Modbus SerialModbus Unsolicited Serial (Slave)Modbus Unsolicited SerialModbus ASCIIModbus ASCII SerialStep 4 - Select a Network Adapter (for Modbus/TCP only)The Network Adapter selection left allows you to select a specific NICcard based on either the NIC name or its currently assigned IPaddress. The list of available NICs will include either unique NIC cardsor NICs that have multiple IP addresses assigned to them.Additionally, the selection will display any WAN connections you mayhave active such as a dialup connection.For PanelView Plus/PanelView Plus CE, select Default and click Next.Step 5 - Enter Communication Settings (doesn’t apply to Modbus/TCP)In the New Channel - Communications dialog, make sure the Modiconcontroller configuration settings match those in slave controllers ordevices.Publication 2711P-UM002B-EN-P - March 2007ParameterSelectionsRecommendedData Bits5, 6, 7, 88Stop Bits1, 21ParityNone, Even, OddEvenBaud300 to 2560009600 or 19200

Configuring KEPServer Drivers for Modbus19Modbus RTU SerialModbus Unsolicited SerialPublication 2711P-UM002B-EN-P - March 2007

20Configuring KEPServer Drivers for ModbusModbus ASCIIStep 6 - Set the Optimization Method for Data RequestsThe New Channel - Write Optimization dialog sets the optimizationmethod for data requests. Select the best optimization for yourapplication and click Next.For more information on KEPServer read and write optimizationoptions refer to the online Driver help.Applies to all Modbus protocolsPublication 2711P-UM002B-EN-P - March 2007

Configuring KEPServer Drivers for Modbus21Step 7 -Select Socket Usage (Applies to Modbus/TCP only)The New Channel - Socket Usage dialog controls how the ModbusEthernet driver will utilize Windows sockets when establishing aconnection to the target device. For a normal Modbus Ethernetenabled device, the default Use Multiple Sockets for deviceconnection (checked) mode of operation is designed to give the bestperformance from the driver.Normally, the Modbus Ethernet driver will use a Windows socket foreach device on the network. When using a new socket connection foreach device, the Modbus Ethernet driver maintains that socket as anactive connection. Normally this provides a very high level ofperformance since the driver does not need to reestablish aconnection each time it needs to read or write data to a given device.For more information on using Sockets in a Modbus RTU bridgeapplication, refer to the online help.Click Next.Publication 2711P-UM002B-EN-P - March 2007

22Configuring KEPServer Drivers for ModbusStep 8 - View and Verify Channel SummaryThe New Channel - Summary dialog provides a summary of the newchannel settings. Verify the settings below and click Finish.Modbus/TCPModbus RTU SerialPublication 2711P-UM002B-EN-P - March 2007

Configuring KEPServer Drivers for Modbus23Modbus Unsolicited SerialModbus ASCII SerialTIPThe red X next to the channel name will disappearwhen a destination device is added under this driver.Step 9 - Save Project FileFrom the Menu bar, select File Save or click the Savebutton.Publication 2711P-UM002B-EN-P - March 2007

24Configuring KEPServer Drivers for ModbusAdd A DeviceNow that a new channel is defined, you need to add a new device tothe channel. In most cases, selecting the default settings will allowyou to quickly configure and connect to a device.Step 1 - Add a DeviceAdd a device by clicking on the Click to add a device hypertext or theNew Device icon. This will bring up the new device wizard. Hereyou’ll add the information pertinent to the controller that you aregoing to communicate with.Step 2 - Enter a Device NameIn the New Device - Name dialog, enter a device name that will helpyou identify the device later and click Next. In most cases, the devicewill be a logic controller.Step 3 - Select a Device ModelIf the device you are defining supports more than one model, select amodel that best describes the device.Publication 2711P-UM002B-EN-P - March 2007For this Protocol:Most Common Model:MODBIS/TCPModbusModbus RTU SerialModbusModbus Unsolicited SerialN/AModbus ASCIIModbus ASCII

Configuring KEPServer Drivers for Modbus25Step 4 - Select a Device IDThe device you are defining may be multidropped as part of anetwork of devices. To communicate with the device, it must beassigned a unique ID.In the New Device - ID dialog, enter a unique Device ID (decimaladdress) to identify the controller on the network. Enter the Device IDand click Next.For this Protocol:Device ID RangeData FormatModbus/TCP (1)xxx.xxx.xxx.xxxIP AddressModbusModbus RTU Serial0 - 255DecimalModbus Unsolicited Serial1 - 247DecimalModbus ASCII1 - 247Decimal(1)For master/slave communications, add a fifth octet to the IP address. Refer to your KEPWaredocumentation for more details on Modbus/TCP master/slave communications.Step 5 - Enter Device Communication Parameters(Doesn’t apply to Modbus Unsolicited Serial Protocol)In the New Device - Communication Parameters dialog, accept thedefault communication parameters by clicking Next.Publication 2711P-UM002B-EN-P - March 2007

26Configuring KEPServer Drivers for ModbusStep 6 - Configure Tag Database Options(Doesn’t apply to Unsolicited Serial or ASCII Protocols)In the New Device - Database Creation dialog, click Next to acceptthe default tag database configuration options.The automatic OPC tag database generation features of the serverhave been designed to make the setup of your OPC application a Plugand Play operation. For communication drivers that support thisfeature, you can configure them to automatically build a list of OPCtags within the server that correspond to device specific data. Theautomatically generated OPC tags can then be browsed from yourOPC client.Publication 2711P-UM002B-EN-P - March 2007

Configuring KEPServer Drivers for Modbus27Step 7 - Enter Device SettingsIn the New Device - Settings dialog, accept the default settings byclicking NextModbus/TCPModbus RTU SerialPublication 2711P-UM002B-EN-P - March 2007

28Configuring KEPServer Drivers for ModbusModbus Unsolicited Serial and Modbus ASCIIStep 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 forreading I/O (coils) and data tables (Registers). Click Next.Modbus/TCP, Modbus RTU Serial, Modbus ASCIIPublication 2711P-UM002B-EN-P - March 2007

Configuring KEPServer Drivers for Modbus29Reasons to Change the Default Block Sizes include: The device may not support block read/write operations ofthe default size. Smaller Modicon PLCs and non-Modicondevices may not support the maximum data transfer lengthssupported by the Modbus Ethernet network. The device may contain non-contiguous addresses. If this isthe case and the driver attempts to read a block of data thatencompasses undefined memory, the device will probablyreject the request.Step 9 - Set Location of the Variable Import FileThe New Device - Variable Import Settings dialog sets the location ofthe Concept or ProWORX variable import file the driver will use whenthe automatic tag database generation feature is enabled for thisdevice. Refer to the KEPServer Enterprise online help for details onhow to use this feature.Publication 2711P-UM002B-EN-P - March 2007

30Configuring KEPServer Drivers for ModbusStep 10 - View and Verify the Device Summary InformationThe New Device - Summary dialog provides a summary of the newdevice settings. Verify the information and click Finish.Modbus/TCPModbus RTU SerialPublication 2711P-UM002B-EN-P - March 2007

Configuring KEPServer Drivers for Modbus31Modbus Unsolicited SerialModbus ASCIIStep 11 - Save Project FileFrom the Menu bar, select File Save or click the Savebutton.Publication 2711P-UM002B-EN-P - March 2007

32Configuring KEPServer Drivers for ModbusCreate TagsWith a channel and device defined, you are ready to create tagswithin the KEPServer software. These tags are used to link to thecontroller addresses. The procedure is similar to creating an HMI tagdatabase. For details on valid data types and addressing, seeAppendices A - E.1. In the right hand pane, click on

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

Related Documents:

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 .

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

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

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(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 .

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 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 .

Abstract . The aim of this paper is to build on the Pragmatic Stochastic Reserving Working Party’s first paper (Carrato, et al., 2016) and present an overview of stochastic reserving used with a one-year view of