Allen-Bradley PanelBuilder 1400e Configuration Software for Windows (Cat. No.
Important User Information Because of the variety of uses for the products described in this publication, those responsible for the application and use of this control equipment must satisfy themselves that all necessary steps have been taken to assure that each application and use meets all performance and safety requirements, including any applicable laws, regulations, codes and standards.
Preface About this Manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Registering Your Copy of PanelBuilder 1400e . . . . . . . . . . . . . . . . Other Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . What’s in This Manual? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Who Should Read This Manual . . . . . . . . . . . . . . . . . . . . . . . . . Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
toc–ii Table of Contents Defining Communications Chapter 4 Configuring Communications . . . . . . . . . . . . . . . . . . . . . . . . . . . . Setting up Terminal Communications . . . . . . . . . . . . . . . . . . . . . Setting the Driver Parameters . . . . . . . . . . . . . . . . . . . . . . . . Configuring Nodes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuring Scan Classes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table of Contents Configuring the PanelView Terminal for Modbus Communications Chapter 7 Transferring Applications Chapter 8 Configuring the Modbus Communication Interface Card . . . . . . . . . Installing Modbus Firmware in the PanelView Terminal . . . . . . . . . . Configuring the Terminal Network Setup Screen . . . . . . . . . . . . . . . Validating Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About Application File Transfers and Modbus . . . . . . . . . . . . . .
About this Manual This manual is designed to supplement the regular set of PanelBuilder and PanelView manuals, listed under “Other Documentation,” below. This manual contains information specific to creating PanelBuilder applications for Modbus, and running them on PanelView 1000e and 1400e terminals equipped with Modbus-capable hardware and software. " Registering Your Copy of PanelBuilder 1400e Note: PanelView 1200 and 1200e terminals do not support Modbus communications.
P–2 Preface • Context-sensitive Help provides a quick reference for any procedures or commands you need explained, or problems you may encounter. To get help, press F1 or choose the Help button if you’re in a dialog box. • The PanelBuilder 1400e Readme file is a Microsoft Windows Notepad file that is copied to your hard disk when you install PanelBuilder 1400e. The Readme file informs you of any software changes after the manuals were printed.
Preface P–3 Chapter 6, Defining Tags, provides information about using the Tag Database editor to define tags. This chapter supplements information in the PanelBuilder 1400e Configuration Software for Windows User Manual, publication 2711E-819. Chapter 7, Configuring the PanelView Terminal for Modbus Communications, provides instructions for configuring the firmware in PanelView terminals for use with the Modbus network.
P–4 Preface Terminology The term PanelBuilder refers to PanelBuilder 1400e Configuration Software for Windows. Where confusion may arise between the current and previous versions of the software, the current release of the software is “PanelBuilder 1400e, Version 3.” Similarly, the terms terminal and PanelView terminal refer to a PanelView 1000e or 1400e terminal. Where confusion may arise between the 1000e and 1400e terminals and previous revisions, specific series and revision names will be used.
Preface P–5 Selection Conventions in Dialog Boxes Dialog boxes contain standard Windows fields that require different selection conventions. Refer to your Windows user documentation for information on the selection conventions. The following shortcut keys allow you to complete dialog boxes faster: This key or key combination Does this Tab Moves the cursor to the next field, option, or command button. Shift+Tab Moves the cursor to the previous field, option, or command button.
P–6 Preface Before You Begin Before you begin, you should already have installed and know how to operate this equipment and software: • a personal computer with at least a 486, 25-MHz microprocessor and at least 8 MB Random Access Memory (RAM) (16 MB recommended), and SVGA monitor with 256 colors (recommended). For users working with imported .dxf files, at least 16 MB RAM is required. If you want to resize graphic images in PanelBuilder, set your display adapter to 65,536 colors. • Microsoft Windows 3.
Preface P–7 Please have the serial number for your software ready when you call, or include it on your fax. You can find this number in three places: • on the Software Registration card that was shipped with your software • on the screen that appears when you start up PanelBuilder • in the main Help menu, when you choose “About” If you have questions about your Modbus controller or device, contact the manufacturer directly. Publication 2711E-6.
Overview of PanelBuilder 1400e with Modbus Connectivity This chapter provides an overview of PanelBuilder 1400e. It describes these topics: • what PanelBuilder is • how PanelBuilder interacts with the PanelView terminal and the controller or other Modbus slave device • important new PanelBuilder features About PanelBuilder 1400e PanelBuilder 1400e is a software package that runs under Microsoft Windows 3.1 and Windows 95.
1–2 Overview of PanelBuilder 1400e with Modbus Connectivity " Note: The development computer doesn’t need to be connected to the controller or the PanelView terminal to run the process. It must be connected only when you’re installing or upgrading firmware in the PanelView terminal, using the PanelView Serial Firmware Upgrade Utility, or when downloading or uploading the application serially.
Overview of PanelBuilder 1400e with Modbus Connectivity " 1–3 Note: To communicate over a Modbus network, you must use a PanelView 1000e or 1400e terminal that has been upgraded to include a supported Modbus ISA communications card and Version 3 firmware with the Modbus communications driver. The PanelView Serial Firmware Upgrade Utility must be used to install Modbus-capable firmware in the terminal.
1–4 Overview of PanelBuilder 1400e with Modbus Connectivity Touch Screen Terminals PanelView 1000e Terminals PanelView 1400e Terminals Publication 2711E-6.
Overview of PanelBuilder 1400e with Modbus Connectivity 1–5 The Controller or Other Modbus Slave Device When communicating over a Modbus network, the controller can respond to queries from the PanelView terminal and other input or output devices. Modicon Controller 24762 The PanelView terminal can be connected to a controller, or other slave device on the Modbus network. The terminal can control and monitor coils, inputs, and registers in these devices on the network.
1–6 Overview of PanelBuilder 1400e with Modbus Connectivity The application is created in PanelBuilder on the personal computer, and downloaded to the PanelView operator terminal. Development Computer Serial Connection PanelView The PanelView terminal queries the controller for process or machine status information. PanelView 1000e/1400e Terminal (Touch Screen) Operator input to the terminal is sent to the controller. The controller uses this information to control the machine or process.
Planning an Application for Modbus This chapter provides information about planning a Modbus application, including defining nodes. For details about assigning scan classes and assigning tags, refer to Chapter 2, “Planning Applications,” in the PanelBuilder 1400e Configuration Software for Windows User Manual, publication 2711E-819. To plan a Modbus application, use the Modbus Communications Worksheet and the Device Tags Worksheet (included in Appendix A).
2–2 Planning an Application for Modbus Defining the Nodes A node is a Modbus slave device with which your application will be communicating on a network. For each node, you must identify the type of addressing the device uses (5- or 6-digit addressing), its station address, and the timeout value. Each node must be given a name to be used when defining tags. Recording Node Information " " For each node, fill in: • Node Name: A user-defined node name.
Planning an Application for Modbus " 2–3 Note: The PanelView terminal communicates with local Modbus stations or with remote, bridged devices if a BM85 module is connected and configured for the network. • Enabled: If a node is enabled, the terminal will communicate with the device at the node. If the node is not enabled, the terminal will not communicate with the device. Instead, the PanelView terminal stores values to be written to the device.
Basic Application Operations This chapter supplements the information in the PanelBuilder 1400e Configuration Software for Windows User Manual, publication 2711E-819. It describes only changes to basic application operations for the Modbus network. For detailed information about other basic application operations, consult Chapter 3, “Working with Applications,” in the PanelBuilder 1400e Configuration Software for Windows User Manual, publication 2711E-819.
3–2 Basic Application Operations Additional Report on Options You can generate a PLC Communications report for a Modbus application that will display the following information: • communications setup information • node and scan class definitions Publication 2711E-6.
Defining Communications To define communications for a Modbus application, use these three editors: • Communication Setup editor—to specify the driver information for connecting a PanelView terminal to a Modbus device. • Nodes editor—to identify the types and addresses of the controllers the application will communicate with. • Scan Classes editor—to define the speed at which tags used in an application will be scanned for new values.
4–2 Defining Communications Setting up Terminal Communications In the Terminal Communications tab you can set the driver parameters. Setting the Driver Parameters You must configure the driver parameters to correspond with the communication settings of the device to which the PanelView terminal is most immediately connected (whether a controller, modem, BM85 module, or other Modbus device).
Defining Communications " 4–3 Note: A node configuration can be changed at any time during application development. At application or screen validation, or download, the nodes used by the tags in the application must be defined. If you change the node’s device type, the tags that use this node may have invalid addresses. If you change the node name, you can automatically update your tags at the same time.
4–4 Defining Communications " Tip: Use a name that will help you to identify your controllers when you are assigning tags later in your application. For example, you could name your controllers according to their locations or according to the machine or part of the process they will be controlling or monitoring. Device Select the type of device you are using from the drop-down list. The type of device determines the addressing syntax and range for all the tags with addresses on this node.
Defining Communications Configuring Scan Classes 4–5 Any tag that has Device as its data source must be assigned to a scan class. At runtime, the PanelView terminal periodically updates its tag information by scanning the device addresses. You determine how often a tag value is updated by assigning the tag to a scan class that you have configured in the Scan Classes editor.
4–6 Defining Communications Foreground and Background Period The period specifies, in seconds, how often the device address will be scanned. A foreground period applies to tags used on the current screen, to the alarm and information window tags, and to the tags under the PLC Controlled tab in the PLC I/O Control dialog. The background scan period applies to tags used in all other screens in the system. The valid range of values is 0 to 86,400 seconds (24 hours), with a 0.1 second resolution.
Changing the Network Type When you create an application, you specify the type of network it is to run on, and set up the communication parameters accordingly. You can change the network type of an existing application to run it on another network. You do this using the Change Network Type dialog box. " Note: When you change the network type to Remote I/O, all communication specifications, including node definitions and scan classes, will be lost.
5–2 Changing the Network Type 4. Choose Yes to change your DH+ application to Modbus. Choose No if you do not wish to continue with the conversion. " Note: When converting to a Modbus application, the device type defined for each node will be incompatible with the Modbus network type. The following message will appear, prompting you to convert the incompatible nodes. 5. Select Yes or No.
Changing the Network Type 5–3 " Note: If you convert shared tags, this may make them invalid for the other applications that are using them. Unused tags are not converted and remain as Remote I/O tags. " Note: If you convert an application from Remote I/O to Modbus, or vice-versa, the tag addresses will be invalid for the network to which you are converting. Change the tag addresses to match the network type. 4. Specify a node name and scan class if required.
5–4 Changing the Network Type 5. Choose OK. The following message will appear: 6. Choose Yes to confirm that you want to continue. Converting from ControlNet to Modbus To change the network type from ControlNet to Modbus: Important: When you change an application from ControlNet to Modbus, you will have to add valid Modbus device tag addresses. 1. Choose Change Network Type from the Tools menu. 2. In the Target Network field, choose Modbus. 3. Choose OK.
Changing the Network Type 5–5 4. Choose Yes to change your ControlNet application to Modbus. Choose No if you do not wish to continue with the conversion. " Note: When converting to a Modbus application, the device type defined for each node will be incompatible with the Modbus network type. The following message will appear, prompting you to convert the incompatible nodes. 5. Select Yes or No.
5–6 Changing the Network Type 4. Choose Yes to change your Modbus application to DH+. Choose No if you do not wish to continue with the conversion. " Note: PanelBuilder checks that the station numbers and device types of all Modbus nodes are valid when the network type is converted to DH+. For example, station number 8 is an invalid octal number. The following message will appear, prompting you to convert incompatible nodes: 5. Select Yes or No.
Changing the Network Type " 5–7 Note: If you convert an application from Modbus to Remote I/O, or vice-versa, the tag addresses will be invalid for the network to which you are converting. Change the tag addresses to match the network type. 4. Choose OK. The following message appears: 5. Choose Yes to confirm that you want to continue. 6.
5–8 Changing the Network Type 4. Choose Yes to change your Modbus application to ControlNet. Choose No if you do not wish to continue with the conversion. " Note: If a Modbus node is defined as station 1, or station 64 through 247 (inclusive), it will be invalid for a ControlNet application. The following message will appear, prompting you to convert the station number. The device types defined for all nodes will also have to be changed when the application is converted to ControlNet. 5.
Defining Tags Use tags to name controller addresses for easy reference. For more information about tags and their role, the tag database editor, and how to create tags, see Chapter 6, “Defining Tags,” in the PanelBuilder 1400e Configuration Software for Windows User Manual.
6–2 Defining Tags " Data Sources Note: You can use Expressions to perform calculations, logical, and conditional operations to manipulate the values of tags. See Chapter 7, “Creating Expressions” in the PanelBuilder 1400e Configuration Software for Windows User Manual. The other two data sources you can see in the Tag Database editor, Memory and DDE, are used only by RSView. Device When you create tags for a Modbus application, select Device as the data source.
Defining Tags 6–3 Configuring an Analog Tag 1. If the tag is part of a folder, select that folder in the folder hierarchy. The folder name appears in the Name field and is the first part of the tag name. 2. Type a tag name. If the tag is part of a folder, type the name after the backslash (\). 3. For Type, select Analog. 4. Fill in the fields as outlined below: Security This field is reserved for RSView databases. You cannot enter anything in the Security field.
6–4 Defining Tags Scale and Offset Type a number. For the scale, do not use 0. Scale and offset together transform raw controller data into meaningful units for the operator. At runtime, all data read from the controller into an analog tag will be scaled using the formula: y = (mx) + b where m = scale x = raw PLC data b = offset y = scaled value The terminal displays the scaled value.
Defining Tags 6–5 Data Type Select the data type that matches the format of the data stored in the controller. The default entry in the data type field is Default. In Modbus applications, the Default data type is Unsigned Integer with an address length of 16 bits. Unless special data is expected, Default should be acceptable. The following data types are supported for Analog tags in a Modbus application: Data Type Description Default Unsigned 16-bit value. Byte Unsigned 8-bit value.
6–6 Defining Tags 5. To fill in the fields for data source, see Specifying a Data Source” later in this chapter. Modbus Address Space Modbus devices can contain four distinct address spaces. Two spaces are reserved for Coil data and two are reserved for Register data. The PanelView terminal can only write to one of the two Coil address spaces but can read from both spaces. The same is true for the two Register address spaces.
Defining Tags 6–7 Reference Address Type Data Access Description 4 Output Holding Register word read and write Use to store numerical (decimal or binary) information or to send the information to an output module. 6 Extended Memory Register access through Logic Program only Use to store information in an extended memory area. Only available in controllers with 24 bit CPUs that support extended memory such as the 984B, E984-785, and Quantum series of controllers.
6–8 Defining Tags Important: Because analog tags with References 1 or 3 are read only, they can only be assigned to display objects (e.g. Numeric Data Display). An error will be generated when you validate the application, if a tag with Reference 1 or 3 has been assigned to an input object. For more information about types of objects, see Chapter 9, “Creating Objects,” in the PanelBuilder 1400e Configuration Software for Windows User Manual, Publication Number 2711E-819.
Defining Tags 6–9 4. Fill in the fields as outlined below: Security This field is reserved for RSView databases. You cannot enter anything in the Security field. Description Type a description of this tag up to 128 characters long. Off Label and On Label These fields are reserved for RSView databases. You cannot enter anything in them. Initial Value Enter an initial value of 0 or 1 for the digital tag.
6–10 Defining Tags Addressing Syntax for Devices Using 6-digit Addressing: " Reference Operations Addressing Syntax 3 word read only 3wwwww/bb where wwwww = word offset 00001 to 65535 (decimal) /bb = bit offset in word 01 to 16 (decimal) 4 word read only 4wwwww/bb where wwwww = word offset 00001 to 65535 (decimal) /bb = bit offset in word 01 to 16 (decimal) Note: Digital tags support only bit addresses.
Defining Tags 6–11 2. Type a tag name. If the tag is part of a folder, type the name after the backslash (\). 3. For Type, select String. 4. Fill in the fields as outlined below: Security This field is reserved for RSView databases. You cannot enter anything in the Security field. Description Type a description of this tag up to 128 characters long. Length Type a number between 1 and 82 to specify the length of the string tag in bytes. The length must be a multiple of 2.
6–12 Defining Tags Addressing Syntax For string tags, the addressing syntax is as follows: Addressing Syntax for Devices Using 5-digit Addressing: Reference Operations Addressing Syntax 0 bit read and write 0bbbb where bbbb = bit 0001 to 9999 (decimal) and bbbb must align on word boundaries (e.g. 00001, 00017, 00033) 1 bit read only 1bbbb where bbbb = bit 0001 to 9999 (decimal) and bbbb must align on word boundaries (e.g.
Defining Tags 6–13 Configuring a Block Tag Use the following procedure to configure a block tag: Important: Block tags are used only for the Alarm Control and the Alarm Acknowledge Value control when multiple, simultaneous alarms need to be monitored. For more information, see Chapter 11, “Configuring Alarms,” in the PanelBuilder 1400e Configuration Software for Windows User Manual. 1. If the tag is part of a folder, select the folder in the folder hierarchy.
6–14 Defining Tags 4. Fill in the fields as outlined below: Security This field is reserved for RSView databases. You cannot enter anything in the Security field. Description Type a description of this tag up to 128 characters long. Number of Bits Enter a number from 1 to 1024 to define the length of the block. The tag’s address must start on a word boundary, e.g. 00001, 00017, 00033, and the number of bits must be a multiple of 16. Initial Value Enter a 1 or 0 to initialize the entire block to 1 or 0 (i.
Defining Tags 6–15 Addressing Syntax for Devices Using 6-digit Addressing: Reference Operations Addressing Syntax 3 word read-only 3wwwww where wwwww = word offset 00001 to 65535 (decimal). No bit offsets are supported. 4 word read and write 4wwwww where wwwww = word offset 00001 to 65535 (decimal). No bit offsets are supported. Important: Specifying a Data Source Because block tags with References 1 or 3 are read only, they can only be assigned to display objects (e.g. Numeric Data Display).
6–16 Defining Tags Important: For Modbus analog tags, the entire controller data file element assigned to the tag’s address is used in determining the tag’s value. This is true regardless of the tag’s data type. For example, a Byte data type assigned with the address 30001 will still look at the entire 16 bits of the integer element, even though the tag is interested only in the lower 8 bits.
Defining Tags 6–17 2. The node is the controller that this tag addresses. In the Node Name field, do one of the following: • type a node name. • double-click in the Node Name field to open the Add Node or Edit Node dialog box. If the field is empty you can create a new node definition; if the field contains the name of an existing node, you can edit that node’s definition. • choose to open a selection list and select a node name.
6–18 Defining Tags • Taylor ProWORXPLUS database • MODSOFT database in flat text format " Note: To import information from an A.I. Series database, you must first export the database in text format using the A.I. software. PanelBuilder imports this text file. To import a Logic 5 database, export it to a text file and import this into A.I. software. You can then export the text file from A.I. as you would any other A.I. database, and import it to PanelBuilder.
Defining Tags 6–19 4. To make the import faster, select the Skip Existing Tags button. To update existing tags from the tags being imported, select the Update Existing Tags button. 5. Select Next. 6. If you are importing a tag database, as opposed to a .csv format file, specify a Tag Database Data Source, or select the Down Arrow to display the list of sources, and choose one from it. If you are importing a .csv tag file or a text database, specify the file or choose the ...
6–20 Defining Tags 7. Select Next. If you are importing a Taylor ProWORXPLUS database, you can choose to include the symbol file (*.fis). This file contains only the tag addresses, and their corresponding names. The symbol file must have the same name as the database file, and must be located in the same directory. 8. Select Next. If you are importing a Taylor ProWORXPLUS database, ensure the tags are imported as Device Tags, since Remote I/O tags are not supported for Modbus applications.
Defining Tags 6–21 9. When you choose Done, a summary dialog is displayed. It contains the following fields: • Source—this is the file from which you are importing tags. • Intermediate Files—the PanelBuilder .csv file is the file which is imported into PanelBuilder as a result of the tag conversions from the source database. The Tag Name Conversion File shows how tag names were converted from the Taylor or MODSOFT symbols to PanelBuilder. Check this file if you want to check tag name conversions.
6–22 Defining Tags " Note: Choose Print from the File menu, to print the contents of the Database Import information window. The log file is also saved at the location and file name specified on the status bar. " Note: Choose Exit from the File menu to close this window and complete the import. The Database menu item on the Application Window menu bar remains grayed, and cannot be selected, until the Database Import information window is closed.
Defining Tags 6–23 " Note: When exporting a PanelBuilder database in Taylor ProWORXPLUS or MODSOFT format, tags with duplicate addresses are not exported. Only the first instance of the tag address is exported. " Note: For Taylor ProWORXPLUS databases, lines containing short comments, long comments or page titles are not imported or exported. Important: When exporting a PanelBuilder database to Taylor ProWORXPLUS, a ‘Z’ is added to any tag name that begins with a number.
6–24 Defining Tags Column Description S On Label Digital Digital on label: use blank Creating a New Tag Database Publication 2711E-6.
Configuring the PanelView Terminal for Modbus Communications This chapter is intended to supplement the information in the PanelView 1000e, 1200e, and 1400e Operator Terminals User Manual, Publication Number 2711E-821. Please refer to it for information about the PanelView terminal’s power-up and online tests, and for more detailed information about configuring the PanelView terminal.
7–2 Configuring the PanelView Terminal for Modbus Communications " Tip: For pinout information and signal levels, see the documentation supplied with your serial communications interface card and your Modbus device. Once you have installed the serial communications card in your PanelView terminal, press the Terminal Information button on the Terminal Configuration Screen to verify that the card is detected correctly. This indicates that the Modbus hardware is installed and detected.
Configuring the PanelView Terminal for Modbus Communications Installing Modbus Firmware in the PanelView Terminal 7–3 Use the PanelView Serial Firmware Upgrade Utility to install Modbus firmware on a PanelView terminal. For information about installing the Serial Firmware Upgrade Utility, see Appendix D, “Installing the PanelView Serial Firmware Upgrade Utility,” in the PanelView 1000e, 1200e, and 1400e Operator Terminals User Manual, Publication Number 2711E-821.
7–4 Configuring the PanelView Terminal for Modbus Communications Once you have installed Modbus firmware in your PanelView terminal, press the Terminal Information button on the Terminal Configuration Screen to verify that the firmware is installed correctly. This indicates that Modbus firmware is installed. This indicates that the Modbus hardware is installed and detected.
Configuring the PanelView Terminal for Modbus Communications Configuring the Terminal Network Setup Screen 7–5 To view the terminal settings of the current Modbus application file, press the Terminal Network Setup button on the Terminal Configuration screen. Terminal and PLC information is displayed as shown in the screen representation below. Important: For information to be displayed on the screen, an application must be made current (selected).
Transferring Applications Validating Applications Before you can transfer an application to a PanelView terminal, you will need to validate the application to ensure that it can be compiled for use on the terminal. For information about validating applications, see Chapter 3, “Working with Applications,” in the PanelBuilder 1400e Configuration Software for Windows User Manual.
Troubleshooting for Modbus Applications This section describes how to diagnose and solve Modbus communication problems. To help solve PanelBuilder software problems, refer to your PanelBuilder 1400e Configuration Software for Windows User Manual. Refer to the Modbus equipment documentation for Modbus-specific troubleshooting information. PanelView terminals on a Modbus network may communicate with controllers or other devices made by manufacturers other than Allen-Bradley.
9–2 Troubleshooting for Modbus Applications Problem Cause What to do: Remote station Exception Response—failure in associated device The controller did not respond because of an error within the controller. Consult the documentation for the controller or device being used. Contact the controller or device manufacturer to determine the cause of the error. Remote station Exception Response—Acknowledge The controller accepted the command, but it needs some time to complete the command.
Sample Worksheets The worksheets in this appendix are designed to help you plan your application. To complete these worksheets, see Chapter 2, Planning an Application for Modbus. Make copies of the worksheets as you need them and save the originals for future use. This Appendix contains the following worksheets: • Modbus Communications Worksheet Use this worksheet to record details of the devices the terminal will be communicating with.
Modbus Communications Worksheet Application File Name: PanelView Station Number: Node Definitions Node Name Modbus Slave Device Station Address Timeout (sec) Note: For more node definitions, use additional copies of this worksheet. Scan Class Definitions Name Foreground (sec) Background (sec) Name Foreground (sec) Background (sec) Note: The default foreground and background rates are 0.000 seconds and 5.000 seconds, respectively.
Device Tags Worksheet Application File Name: Screen Number: Object Ref No. Type Initial State Value Tag Analog Tag Only Name Type Scale Offset Initial Range Data Type Value of Values Address Address Number of characters (string tag only) Tag Start Value Notes: Initial State Value: Objects such as Multistate Push Buttons have a user-configurable initial state whose value will supersede the tag’s initial value when the application is first run. This is called the tag’s Start Value.
Symbols .csv file, 6–18 and column ordering, 6–23 importing a database, 6–18 Numbers 24-hour support, P–6 A A.I.
I–2 Index F from Remote I/O to Modbus, 5–2 Fax Back, technical support services, P–6 Node, name, valid characters, 4–3 Flow Control. See Driver Help, online, P–2 Nodes configuring, 4–2, 4–3 defining, 2–1, 2–2 enabled, 4–4 PLC type, 4–4 station address, 4–4 timeout, 4–4 Hot keys. See Shortcut keys Nodes editor, about, 4–1 Folders, digital tags, 6–10, 6–13 H I Importing, tag database, 6–17 from A.I.
Index S Scan classes configuring, 4–5–4–6 for Device data source tags, 4–5 defining, 2–1, 2–3 Scan Classes editor, using, 4–5–4–6 Scan classes editor, about, 4–1 Scanning about, 2–3 scan classes, configuring, 4–5 scan period background, 4–6 foreground, 4–6 Screens, application, about, 1–3 Selection conventions, P–4 Serial number, software, P–7 Setting up, terminal communications, 4–2 Shortcut keys, P–5 Software, registration, P–1 Station address, 4–4 Station numbers converting from DH+ to Modbus, 5–2, 5–5
Publication 2711E-6.12 – November 1997 Supersedes Publication 2711E-6.12 – August 1997 41061-033-01(B) Copyright 1997 Allen-Bradley Company, Inc.
