R07 Ind780 PLC en
R07 Ind780 PLC en
R07 Ind780 PLC en
Terminal
PLC Interface Manual
www.mt.com
64057518 (05/2012) R07
METTLER TOLEDO 2012 No part of this manual may be reproduced or transmitted in any form or by any means, electronic or mechanical, including photocopying and recording, for any purpose without the express written permission of METTLER TOLEDO. U.S. Government Restricted Rights: This documentation is furnished with Restricted Rights. Copyright 2012 METTLER TOLEDO. This documentation contains proprietary information of METTLER TOLEDO. It may not be copied in whole or in part without the express written consent of METTLER TOLEDO. METTLER TOLEDO reserves the right to make refinements or changes to the product or manual without notice. COPYRIGHT METTLER TOLEDO is a registered trademark of Mettler-Toledo, LLC. All other brand or product names are trademarks or registered trademarks of their respective companies.
Copyright (c) 2003, Dr. Brian Gladman, Worcester, UK. All rights reserved. AES SOFTWARE LICENSE TERMS The free distribution and use of this software in both source and binary form is allowed (with or without changes) provided that: 1. Distributions of this source code include the above copyright notice, this list of conditions and the following disclaimer; 2. Distributions in binary form include the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other associated materials; 3. The copyright holders name is not used to endorse products built using this software without specific written permission. ALTERNATIVELY, provided that this notice is retained in full, this product may be distributed under the terms of the GNU General Public License (GPL), in which case the provisions of the GPL apply INSTEAD OF those given above. DISCLAIMER This software is provided as is with no explicit or implied warranties in respect of its properties, including, but not limited to, correctness and/or fitness for purpose. METTLER TOLEDO RESERVES THE RIGHT TO MAKE REFINEMENTS OR CHANGES WITHOUT NOTICE.
FCC Notice This device complies with Part 15 of the FCC Rules and the Radio Interference Requirements of the Canadian Department of Communications. Operation is subject to the following conditions: (1) this device may not cause harmful interference, and (2) this device must accept any interference received, including interference that may cause undesired operation. This equipment has been tested and found to comply with the limits for a Class A digital device, pursuant to Part 15 of FCC Rules. These limits are designed to provide reasonable protection against harmful interference when the equipment is operated in a commercial environment. This equipment generates, uses, and can radiate radio frequency energy and, if not installed and used in accordance with the instruction manual, may cause harmful interference to radio communications. Operation of this equipment in a residential area is likely to cause harmful interference in which case the user will be required to correct the interference at his or her expense. Declaration of conformity is located on the documentation CD, part number 64057241.
Your feedback is important to us! If you have a problem with this product or its documentation, or a suggestion on how we can serve you better, please fill out and send this form to us. Or, send your feedback via email to: quality_feedback.mtwt@mt.com. If you are in the United States, you can mail this postpaid form to the address on the reverse side or fax it to (614) 438-4355. If you are outside the United States, please apply the appropriate amount of postage before mailing. Your Name: Organization Name: Address: Date: METTLER TOLEDO Order Number: Part / Product Name: Part / Model Number: Serial Number: Company Name for Installation: Contact Name: Phone Number:
CUSTOMER FEEDBACK
Fax Number: ( )
Please check the appropriate box to indicate how well this product met your expectations in its intended use? Met and exceeded my needs Met all needs Met most needs Met some needs Did not meet my needs Comments/Questions:
DO NOT WRITE IN SPACE BELOW; FOR METTLER TOLEDO USE ONLY Retail Light Industrial Heavy Industrial Custom
POSTAGE WILL BE PAID BY ADDRESSEE Mettler-Toledo, LLC Quality Manager - MTWT P.O. Box 1705 Columbus, OH 43216
USA
PRECAUTIONS
READ this manual BEFORE operating or servicing this equipment and FOLLOW these instructions carefully. SAVE this manual for future reference.
WARNING!
FOR CONTINUED PROTECTION AGAINST SHOCK HAZARD CONNECT TO PROPERLY GROUNDED OUTLET ONLY. DO NOT REMOVE THE GROUND PRONG.
CAUTION
BEFORE CONNECTING/DISCONNECTING ANY INTERNAL ELECTRONIC COMPONENTS OR INTERCONNECTING WIRING BETWEEN ELECTRONIC EQUIPMENT ALWAYS REMOVE POWER AND WAIT AT LEAST THIRTY (30) SECONDS BEFORE ANY CONNECTIONS OR DISCONNECTIONS ARE MADE. FAILURE TO OBSERVE THESE PRECAUTIONS COULD RESULT IN DAMAGE TO OR DESTRUCTION OF THE EQUIPMENT AND/OR BODILY HARM.
CAUTION
OBSERVE PRECAUTIONS FOR HANDLING ELECTROSTATIC SENSITIVE DEVICES.
WARNING!
NOT ALL VERSIONS OF THE IND780 ARE DESIGNED FOR USE IN HAZARDOUS (EXPLOSIVE) AREAS. REFER TO THE DATA PLATE OF THE IND780 TO DETERMINE IF A SPECIFIC TERMINAL IS APPROVED FOR USE IN AN AREA CLASSIFIED AS HAZARDOUS BECAUSE OF COMBUSTIBLE OR EXPLOSIVE ATMOSPHERES.
WARNING!
WHEN THIS EQUIPMENT IS INCLUDED AS A COMPONENT PART OF A SYSTEM, THE RESULTING DESIGN MUST BE REVIEWED BY QUALIFIED PERSONNEL WHO ARE FAMILIAR WITH THE CONSTRUCTION AND OPERATION OF ALL COMPONENTS IN THE SYSTEM AND THE POTENTIAL HAZARDS INVOLVED. FAILURE TO OBSERVE THIS PRECAUTION COULD RESULT IN BODILY HARM AND/OR PROPERTY DAMAGE.
Contents
Chapter 1 A-B RIO Kit Option ............................. 1-1
Overview ................................................................................... 1-1
Communications ..............................................................................1-2 Node/Rack Address ...........................................................................1-2 Data Formats ...................................................................................1-3
Chapter 2
IND780 PLC Interface Manual Controlling Discrete I/O Using a PLC Interface ......................................2-28
Chapter 3
Troubleshooting ..................................................................... 3-106 ControlNet Option Kit .............................................................. 3-106 Programming Examples .......................................................... 3-108
Chapter 4
IND780 PLC Interface Manual Byte Order ........................................................................................4-8 Message Slots ..................................................................................4-8 Integer and Division ........................................................................4-15 Floating Point .................................................................................4-17 Controlling the Discrete I/O Using a PLC Interface.................................4-27
Chapter 5
Preface ..................................................................................... 5-1 Overview ................................................................................... 5-1 DeviceNet Characteristics ............................................................ 5-1
Communications ..............................................................................5-2 Node Address ...................................................................................5-3 Data Formats ...................................................................................5-3 Network Topology .............................................................................5-3 Network Power and Current ................................................................5-3
Troubleshooting ....................................................................... 5-23 DeviceNet Option Kit ................................................................. 5-24 DeviceNet Commissioning and Configuration Examples ................ 5-24
Configuring the IND780 Terminal with RSNetworx for DeviceNet ............5-24 PLC Programming...........................................................................5-38
Chapter 6
Modbus TCP Option Kit ............................................................. 6-32 Modbus TCP Configuration Example ........................................... 6-32
Integer Logic Examples ....................................................................6-38
Chapter 7
Specifications ............................................................................ 7-1 Analog Output Operation ............................................................. 7-2 Installation ................................................................................ 7-3 Wiring ...................................................................................... 7-4 Setup in the IND780 Terminal ...................................................... 7-5
Analog Output Setup Sub-Block ...........................................................7-5
Status LEDs ............................................................................... 7-8 Analog Output Option Kit ............................................................. 7-9
Chapter 1
Overview Data Definition Hardware Setup Software Setup Troubleshooting Allen-Bradley RIO Option Kit Programming Examples
The A-B RIO Kit option enables the IND780 terminal to communicate to Allen-Bradley Programmable Logic Controllers (PLCs) through direct connection to the A-B RIO network. The option consists of a backplanecompatible I/O module, and software that resides in the IND780 terminal to implement the data exchange. Figure 1-1 shows an A-B Rio interface module.
The A-B RIO Kit option has the following features: A-B RIO Node Adapter Chip Set (licensed from Allen-Bradley) and termination for the A-B network cable (blue hose) on a three-position removable terminal block. User-programmable RIO communication parameters that are configured in software set up through the terminal keyboard/display. The parameters are: 57.6K, 115.2K, or 230.4K baud rate 1/4, 1/2, 3/4, full rack (depends upon the number of scales/interface) Rack address Starting quarter Last rack designation 1-1
IND780 PLC Interface Manual Capability for bi-directional discrete mode communications of weight, display increments, status, and control data between the PLC and the terminal. Capability for bi-directional block transfer communication of many IND780 terminal data variables.
Communications
The IND780 terminal utilizes component parts that are provided by Allen-Bradley to ensure complete compatibility with the Allen-Bradley RIO network. An IND780 terminal is recognized as a RIO (Allen-Bradley) device by the PLC. Each option connected to the Allen-Bradley RIO network represents a physical node. The connection is facilitated by a three-position removable terminal block on the option card. These terminals correspond to the terminals on the A-B PLC RIO connector. The wiring between the PLC and the RIO connector uses the standard RIO cable used by Allen-Bradley (Figure 1-4). This cable is often referred to as the blue hose. The cable installation procedures and specification including distance and termination requirements are the same as recommended by Allen-Bradley for the RIO network refer to the A-B RIO scanner card documentation for further information. The IND780 terminals baud rate is programmed via setup at Communication > PLC Interface > A-B RIO.
Node/Rack Address
Although each RIO option represents one physical node, the addressing of the node is defined as a logical rack address. This address is chosen by the system designer, and then programmed into the IND780 terminal and PLC. The IND780 terminals address is programmed through Communication > PLC Interface > A-B RIO in the setup menu. IND780 address entry can be in either decimal or octal, while most PLC address entry is in octal. The IND780 terminals setup capabilities allow selection of the logical rack address, starting quarter, and designation of the last rack and the number of quarters (Message Slots). Quarters must be contiguous in a single, logical rack, so the starting quarter must be low enough to accommodate all of the required data for the scales in a single, logical rack. The IND780 will determine the number of quarters needed for the chosen data format and number of configurable Message Slots. It only allows selection of the possible starting quarters and maximum Message Slots. Note that floating point data format uses a complete rack address regardless of the number of message slots used (max. 2).
1-2
Data Formats
The A-B RIO Kit option has two types of data exchanges: discrete data and block transfer data. Discrete data is continuously available. The A-B RIO Kit option has its own logical rack address to send and receive information to and from the PLC. Discrete data is always sent even when the optional block transfer data is used. Block transfer data is available when the option is enabled through the IND780 Communication > PLC Interface > A-B RIO setup menu. This data is used to pass information that cannot be sent by the discrete data because of size or process speed limitations. See the Data Definition section for more information.
Up to 20 terminals can be connected in the cluster. However, the number of message slots available for communications depends on the type of PLC interface. All available PLC message slots can be configured to send or receive data to or from the remote terminals via the cluster. Refer to the appropriate PLC chapters in the IND780 PLC Interface Manual for further details on message slots limitations. To allow bridging of the PLC interface, first a cluster network must be set up among the IND780 terminals. Once the cluster is established, configure the PLC interface on the bridge terminal, set up its data format and assign the required local or remote scales data to the message slots. Figure 1-3 shows an example of two message slots, the first being allocated to scale 1 of the local bridge terminal and 1-3
IND780 PLC Interface Manual a second slot to scale 1 of the remote terminal node 6. For details on configuring the PLC interface in a cluster terminal, refer to the Software Setup section, below. The use of PLC interface sharing is not recommended when real time weight or rate information is required by the PLC for fast process control. The determinism of the terminals PLC interface data update rate is influenced and limited by the characteristics of Ethernet TCP/IP communications used in the cluster network.
Data Definition
The A-B RIO Kit option uses two types of data for its communication with PLCs: discrete data and block transfer data. Discrete data is always available. The data transfer is accomplished via the PLCs I/O messaging. Block transfer data is only available if this data option is enabled through the Communication > PLC Interface > A-B RIO setup menu. If the block transfer data option is enabled, it is provided in addition to the discrete data. Block transfer data requires block transfer ladder sequence programming to accomplish the data transfer between the IND780 and PLC.
Data Integrity
The IND780 has specific bits to allow the PLC to confirm that data was received without interrupt and the IND780 is not in an error condition. It is important to monitor these bits. Any PLC code should use them to confirm the integrity of the data received from the IND780. Refer to the data charts for specific information regarding the Data OK, Update in Progress, Data Integrity bits and their usage.
Discrete Data
Five formats of discrete data are available with the A-B RIO Kit option: Integer, divisions, floating point, template and application. Only one type of data format may be selected and used by IND780s sharing the same A-B RIO logical rack address.
1-4
IND780 PLC Interface Manual The integer and division formats allow bi-directional communication of discrete bit encoded information or 16 bit binary word (see Table 1-7 and Table 1-8 for explanation) numerical values. The IND780 provides one quarter rack of data per Message Slot. The floating-point format allows bi-directional communication of discrete bit encoded information or numeric data encoded in IEEE 754, single precision floating point format. The IND780 provides one-half rack of data per Message Slot. In floating point format, the IND780 will populate a complete rack of data regardless if one or two Message Slots are used. The format of discrete data will affect the amount of rack space required. Integer and division formats require one-quarter rack per IND780 (two 16-bit words of input and two 16-bit words of output data) Message Slot. One IND780, with 1 Message Slot, would use a quarter rack; two IND780s, with 1 Message Slot, would use a half rack; three IND780s, with 1 Message Slot, would use three-quarters of a rack; and four IND780s, with 1 Message Slot, would use a full rack. The floating-point format requires more space per IND780 because floating point data uses two 16-bit words of data to represent just the numeric data alone. The floating point format uses one-half rack per IND780 (four 16-bit words of input and four 16-bit words of output data) Message Slot. Selection of the appropriate format depends on issues such as the range or capacity of the scale used in the application. The integer format can represent a numerical value up to 32,767. The division format can represent a value up to 32,767 scale divisions (increments). The floating-point format can represent a value encoded in IEEE 754, single precision floating point format. Floating point is the only data format that includes decimal point information. All other formats ignore decimal points. Accommodation of decimal point location must take place in the PLC logic, when it is needed with these formats. Another issue is the type of information communicated between the IND780 and PLC for the application. Because the floating point format has more space for its data, it has additional information that can be sent or received without using the optional block transfer data. Please see each formats detailed description of the data available, to determine which is most suitable for the specific application. Changing the Data Format to be used by the IND780 will cause all Message Slots to be cleared. Data format is set up in the Communication > PLC Interface > Data Format screen.
1-5
The integer format could not be used because it would send a negative value once the weight exceeded 32,767.
150 x .001 scale IND780 Displays: Integer Division Floating Point 0 0 0 0 2.100 Format sent: 2100 2100 2.1 (13929) (13929) 51.607 18928 18928 150.0 51.607 150.000
The integer and division formats could not be used because they would send a negative value once the weight exceeded 32.767.
Byte Order
Word Swap takes the IEE 754 single-precision floating point format and swaps the two words in the 32-bit double word. This format is compatible with RSLogix 5000 processors. Byte Swap makes the floating point format compatible with S7 PROFIBUS. Historic makes the floating point format compatible with PLC 5.
Message Slots
The integer and division formats provide one-quarter rack (two 16-bit words of input and two 16-bit words of output data) per Message Slot. Each message slot 1-6
IND780 PLC Interface Manual is assigned to a local or remote scale and scales may be repeated in additional message slots. Remote scales must reside in an IND780 Ethernet TCP clustered to the IND780 containing the A-B RIO interface. Depending upon the starting quarter there may be up to four Message Slots provided. Each Message Slots first input word provides scale weight data and the input weight data may be selected by the PLC using the Message Slots second output word bit 0, bit 1 and bit 2. Table 1-1 and Table 1-2 provide input and output words and word usage information.
Table 1-1: PLC Input Words and Word Usage (Integer and Division), BT Disabled
Word Usage Start Quarter 1 (Group 0) Message Slot 1 Weight Data Message Slot 1 Scale Status Message Slot 2 Weight Data Message Slot 2 Scale Status Message Slot 3 Weight Data Message Slot 3 Scale Status Message Slot 4 Weight Data Message Slot 4 Scale Status
Word Usage Start Quarter 2 (Group 2) Message Slot 1 Weight Data Message Slot 1 Scale Status Message Slot 2 Weight Data Message Slot 2 Scale Status Message Slot 3 Weight Data Message Slot 3 Scale Status
Word Usage Start Quarter 3 (Group 4) Message Slot 1 Weight Data Message Slot 1 Scale Status Message Slot 2 Weight Data Message Slot 2 Scale Status
Word Usage Start Quarter 4 (Group 6) Message Slot 1 Weight Data Message Slot 1 Scale Status
Table 1-2: PLC Output Words and Word Usage (Integer and Division), BT Disabled
Word Usage Start Quarter 1 (Group 0) Message Slot 1 Weight Data Message Slot 1 Scale Command Message Slot 2 Weight Data Message Slot 2 Scale Command
Word Usage Start Quarter 2 (Group 2) Message Slot 1 Weight Data Message Slot 1 Scale Command
1-7
The floating point format provides one-half rack (four 16-bit words of input and up to four 16-bit words of output data) per Message Slot. See Table 1-5 and Table 1-6 for details. The number of Message Slots is setup in Communications > PLC Interface > Data Format setup menu (Figure 1-8).
Table 1-3: PLC Input Words and Word Usage (Integer and Division), BT Enabled
Word Usage Start Quarter 1 (Group 0) Not Valid Not Valid Not Valid Not Valid Not Valid Not Valid Not Valid Not Valid
Word Usage Start Quarter 2 (Group 2) Reserved Reserved Message Slot 1 Weight Data Message Slot 1 Scale Status Message Slot 2 Weight Data Message Slot 2 Scale Status Message Slot 3 Weight Data Message Slot 3 Scale Status
Word Usage Start Quarter 3 (Group 4) Reserved Reserved Message Slot 1 Weight Data Message Slot 1 Scale Status Message Slot 2 Weight Data Message Slot 2 Scale Status
Word Usage Start Quarter 4 (Group 6) Reserved Reserved Message Slot 1 Weight Data Message Slot 1 Scale Status
1-8
Word Usage Start Quarter 1 (Group 0) Not Valid Not Valid Not Valid Not Valid Not Valid Not Valid Not Valid Not Valid
Word Usage Start Quarter 2 (Group 2) Reserved Reserved Message Slot 1 Weight Data Message Slot 1 Scale Command Message Slot 2 Weight Data Message Slot 2 Scale Command Message Slot 3 Weight Data Message Slot 3 Scale Command
Word Usage Start Quarter 3 (Group 4) Reserved Reserved Message Slot 1 Weight Data Message Slot 1 Scale Command Message Slot 2 Weight Data Message Slot 2 Scale Command
Word Usage Start Quarter 4 (Group 6) Reserved Reserved Message Slot 1 Weight Data Message Slot 1 Scale Command
Bits 0 - 7 Message Slot 1, Reserved Message Slot 1 Floating Point data Message Slot 1 Floating Point data Message Slot 1, Scale Status, See Message Slot Table Message Slot 2, Reserved Message Slot 2 Floating Point data Message Slot 2 Floating Point data Message Slot 2, Scale Status, See Message Slot Table
Bits 8 - 15 Message Slot 1, Command Response, See Message Slot Table Message Slot 1 Floating Point data Message Slot 1 Floating Point data Message Slot 1, Scale Status, See Message Slot Table Message Slot 2, Command Response, See Message Slot Table Message Slot 2 Floating Point data Message Slot 2 Floating Point data Message Slot 2, Scale Status, See Message Slot Table
4 5 6 7
1-9
Usage Reserved Message Slot 1 Command Message Slot 1 Floating Point data Message Slot 1 Floating Point data Message Slot 2 Command Message Slot 2 Floating Point data Message Slot 2 Floating Point data Not Used
1-10
WORD 1 IN Feed
2 2 3 4
Bit number 0 1 2 3 4 5 6 7 8 9 10 11 12
4
Fast Feed
Tolerance OK
Under low tolerance Over high tolerance Comparator 3 Comparator 2 Comparator 1 ENTER key Input 1 Input 2 Input 3 Motion
7 7 7 6 5 5 5
8 9 10
13 14 15
Update in progress
11
2 3 4
5. Bits 5, 6 and 7 provide Comparators 1, 2 and 3 statuses. If the comparator is active, the respective bit is set to 1. 6 7 8 9 Bit 8 is set to a 1 when the ENTER key is pressed on the keypad of the terminal. The bit remains on for 30 seconds then resets to 0. Bit 9, bit 10, and Bit 11 mirror the state of the first three discrete inputs on the internal I/O board slot 5 (0.5.1, 0.5.2 and 0.5.3). If the input is ON then the bit is set to a 1. Bit 12 is set to a 1 when the scale is in motion (unstable). Bit 13 is set to a 1 when the scale is in net mode (a tare has been taken).
10 Bit 14 is set to a 1 when the terminal is in the process of updating its data for the PLC scanner. The PLC should ignore ALL of the data in this case and simply re-scan it. 11 Bit 15 is set to a 1 when the scale is operating properly (NOT over capacity, under capacity, in power-up, in expanded mode, or in setup mode).The PLC program should continuously monitor this bit and the PLC processor rack fault bit (see A-B RIO PLC documentation) to determine the validity of the discrete and/or explicit data transfer. While in the setup mode word 0 data may be present; do not use the data under this condition as the communication connection may stop at any time. 12 When number is negative, word 0 Bit 15 is high and is the least significant bit. Otherwise, when the number is positive, Bit 15 is the most significant bit.
1-11
Bit number 0 1 2 3 4 5 6 7
8
Load Tare
5 6
8 9 10 11 12 13 14 15
Display mode
Load Target
3 4 5 6 7 8
9 Bits 9-11 control Display Mode. A command is written to pd0119. Note that pd0119=0 for normal display mode, 1 = display message 1 (aw0101), 2 = display message 2 (aw0102), 3 = display message 3 (aw0103), 4 = display message 4 (aw0104), 5 = display message 5 (aw0105), 6 = Start ID1 sequence, 7 = display message that is written into pd0118. Note: Until these bits are used pd0119 will be set at 0. Change of state of any of these bits resets PLC input word, Bit 8, Enter Key. 10 Bit 12, Bit 13, and Bit 14 can be used to control the state of the first three discrete outputs on the terminals internal I/O board in slot 5. These are addressed as 0.5.1, 0.5.2, and 0.5.3. Setting the bit to a 1 state causes the output to be turned ON. This action will occur regardless of the discrete output assignment within the IND780. 11 When Bit 15 is changed from 0 to 1 the value in WORD 0 is loaded into the target register in the terminal and transferred into the target logic.
1-12
Floating Point
Operational Overview
The IND780 uses integer commands from the PLC to select the floating point weight output data. The IND780 recognizes a command when it sees a new value in the Message Slot command word. If the command has an associated floating point value (for example: loading a target value), it must be loaded into the floating point value words before the command is issued. Once the IND780 recognizes a command, it acknowledges the command by setting a new value in the command acknowledge bits of the scales command response word. The IND780 also tells the PLC what floating point value is being sent (via the floating point input indicator bits of the command response word). The PLC should wait until it receives the command acknowledgment from the IND780 before sending another command. The IND780 can report two types of values to the PLC: real-time and static. When the PLC requests a real-time value, the IND780 acknowledges the command from the PLC once but sends and updates the value at every interface cycle update. Note that PLC RIO scanner baud rate and the number of racks in the scanner configuration will have an impact on the PLC input data update rate. If the PLC requests a static value, the IND780 acknowledges the command from the PLC once and updates the value once. The IND780 will continue to send this value until it receives a new command from the PLC. Gross weight and net weight are examples of real-time data. Tare weight, target, feed, and tolerance values are examples of static data. The IND780 can send a rotation of up to nine different real-time values. The PLC sends commands to the IND780 to add a value to the rotation. Once the rotation is established, the PLC must instruct the IND780 to begin its rotation automatically, or the PLC may control the pace of rotation by instructing the IND780 to advance to the next value. Note that once the rotation is established the rotation will be present on all message slots. If the IND780 is asked to automatically alternate its output data, it will switch to the next value in its rotation at the next Interface cycle update. (The Interface cycle update has an update rate of up tp 17 Hz or 60 milliseconds.) Note that PLC RIO scanner baud rate and the number of racks in the scanner configuration will have an impact on the PLC input data update rate. The PLC may control the rotation by sending alternate report next field commands (1 and 2). When the PLC changes to the next command the IND780 switches to the next value in the rotation order. Each message slot can be controlled separately. The IND780 stores the rotation in its shared data so the rotation does not have to be re-initialized after each power cycle. When the PLC does not set up an input rotation, the default input rotation consists of gross weight only. See the floating-point command examples in Table 1-11 through Table 1-14 for additional information. The method of handling string and floating point data varies between Allen-Bradley PLC generations. The IND780 provides floating point data in the order entered in Data Format setup.
1-13
IND780 PLC Interface Manual Table 1-9 to Table 1-12 provide detailed information on the floating-point data format. Read data refers to the PLCs input data and write data refers to the PLCs output data.
Table 1-9: Discrete Read Floating Point IND780 >> PLC
Octal Address 0 1 2 3 4 5 6 7 10 11 12 13 14 15 16 17 1 FP Input Ind 1 FP Input Ind 2 FP Input Ind 3 FP Input Ind 4 FP Input Ind 5 Data integrity1 Cmnd Ack 1 Cmnd Ack 2
7 7 7 7 7
WORD 1 FP value X X X X X X X X X X X X X X X X
WORD 2 FP value X X X X X X X X X X X X X X X X
Bit number 0 1 2 3 4 5 6 7 8 9 10 11 12 13
11 4
Fast Feed
Tolerance OK
RESERVED
Under Negative Tolerance Over Positive Tolerance Selected scale Custom Bit Custom Bit ENTER key Input 1 Input 2 Input 3 Motion
9 9 9 6 6 5
10 12
11
13 13
Data integrity 2
14
14 15
2 3 4 6
5 Bit 5 will be set to a 1 when the associated scale is selected on the IND780 console panel.
10 Bit 12 is set to a 1 when the scale is in motion (unstable). 11 The Data Integrity bit in WORD 0 - bit 13 is used in conjunction with the bit in WORD 3 - bit 14 to insure that the floating point data is valid. For the data to be valid both bits must have the same polarity. These bits will change to the opposite state every interface update cycle. If they do not have the same value the data is invalid and the PLC should ignore ALL of the data in this case and re-scan it.
1-14
Dec
0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 1928 29 30 31 Gross Weight* Net Weight* Tare Weight* Fine Gross Weight* Fine Net Weight* Fine Tare Weight* Rate
Data
ALxx01 SDV, instance by scale ** ALxx02 SDV, instance by scale ** AJxx01 SDV, instance by scale ** AJxx02 SDV, instance by scale ** Low-pass filter frequency, instance by scale Notch filter frequency, instance by scale Target value, instance by scale Target positive tolerance value, instance by scale Target Fine Feed value, instance by scale Target negative tolerance value, instance by scale Target spill value, instance by scale Primary units, low increment size, instance by scale Not used Last IND780 error code, instance by scale No data response command successful No data response command failed
* **
These are real-time fields that the PLC may request either through an input rotation or a report command. All other fields may only be requested through a report command. SDV means Shared Data Variable.
1-15
WORD 7
Bit number
X X X X X X X X X X X X X X X X
X X X X X X X X X X X X X X X X
X X X X X X X X X X X X X X X X Not Used
0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
2 3
Not all commands will require a value in the floating point load value words.
1-16
SDName PD0119
ALxx016 ALxx026
CPxx017 CPxx027
Disable LCD display Enable LCD display 7 Set normal display mode 7,9 Display message 1 7,9 Display message 2 7,9 Display message 3 7,9 Display message 4 7,9 Display Message 5 7,9 Start ID1 sequence 7,9 Display SDV PD0118 7,9 Disable weight display 7 Enable weight display 7 Set discrete output 0.5.1 ON 7 Set discrete output 0.5.2 ON 7 Set discrete output 0.5.3 ON 7 Set discrete output 0.5.4 ON 7 Set discrete output 0.5.1 OFF 7 Set discrete output 0.5.2 OFF 7 Set discrete output 0.5.3 OFF 7 Set discrete output 0.5.4 OFF 7 Master control relay OFF7, 12 Master control relay ON7, 12 Set target value 4,10, 13 Set target fine feed value 4,10 Set - tolerance value 4,10 Set target value and apply4, 10, 14 Start target logic 7,10 Abort target logic 7,10 Target use gross weight 7,10 Target use net weight 7,10 Target use rate 7,10 Target, absolute weight 1 speed 7,10 Target, absolute weight 2 speed 7,10 Enable target latching 7,10 Disable target latching 7,10 Reset target latch 7 Set target spill value4, 10 Set + tolerance value 4,10 Apply scale setup 7 Write Calibration to EEProm 7 Disable Tare on IND780 console 7,11 Enable Tare on IND780 console 7 Disable push button Tare on IND780 console 7,11 Enable push button Tare on IND780 console 7 Disable numeric Tare on IND780 console 7,11 Enable numeric Tare on IND780 console 7 Select scale 3 7 Select scale 4 7
SPxx05
SPxx04 SPxx04 SPxx04 SPxx08 SPxx08 SPxx06 SPxx06 SPxx07 SPxx11 QC0149
1-17
4. 5. 6. 7. 8. 9.
10. Target, Fine Feed, Tolerances, Restart, Abort and other Target variables are relative to each scale. Note: Restart of an active Target will cause the associated outputs to cycle off then back on. 11. Does not disable the PLC tare functions. 12. Setting the master control relay OFF turns off all outputs and stops target logic. The target logic must be restarted after the master control relay is turned ON. 13. Target logic must be restarted to apply the new target value. 14. New target value is applied when command is sent.
1-18
1-19
1 (PLC sends command to IND780 terminal to report net weight) 2 (IND780 terminal sees new command)
none required
As long as the PLC leaves the 11 (dec) in the command word, the IND780 terminal will update the net value every interface update cycle.
Table 1-14: Data Requirement: Load Target Value = 21.75 for Scale 1
Step # Scale command (from PLC) Scale Floating Point Value Command response from terminal Floating Point Value
1 (PLC loads floating point value first) 2 (PLC sends command to set target 1 cutoff value) 3 (IND780 terminal sees new command , loads the value into the target and ends a return message to indicate the new target value) 4 (PLC instructs IND780 terminal to start using new target value) 5 (IND780 terminal sees new command) 114 (dec) loaded into command word O 110 (dec) loaded into command word O
(null value)
The PLC should always wait to receive a command acknowledgment before sending the next command to the IND780 terminal. After the PLC finishes loading its target value, it can resume monitoring the weight information required by sending a command to report some type of weight or set up a rotation of reported data.
1-20
1 (PLC clears out any previous rotation with reset) 2 (IND780 terminal sees new command) 3 (PLC adds gross weight to rotation) 4 (IND780 terminal sees new command) 5 (PLC adds rate to the rotation) 6 (IND780 terminal sees new command)
3 (dec) loaded into command word O Command ack.= 1 F.P. ind = 30 40 (dec) loaded into command word O
0.0
(null value)
Command ack. = 2 F.P. ind = 30 46 (dec) loaded into command word O Command ack. = 3 F.P. ind = 30
0.0
0.0
At this point, the rotation has been set up. Now the PLC needs to command the IND780 terminal to begin the rotation. 7 (PLC sends the command to begin the rotation at next interface update) 8 (IND780 terminal sends gross weight at Interface cycle update ~ 60 msec) 9 (PLC leaves 0 in its command word and the IND780 terminal sends the rate value at next interface update) 10 (PLC leaves 0 in its command word and IND780 terminal sends the gross value next interface update) 0 (dec) loaded into command word O Command ack. = 0 F.P. ind = 0 Floating point value = gross wt. 0 (dec) loaded into command word O Command ack. = 0 F.P. ind = 6 Floating point value = rate Command ack. = 0 F.P. ind = 0 Floating point value = gross wt. 0 (dec) loaded into command word O
1-21
11 (PLC leaves 0 in command word and IND780 terminal sends the rate value at next interface update) 0 (dec) loaded into command word O Command ack. = 0 F.P. ind = 6 Floating point value = rate
This rotation continues until the PLC sends a different command. At approximately every 60 msec the IND780 terminal updates its data with the next field in its rotation. The PLC must check the floating point indication bits to determine which data is in the floating point value.
Table 1-16: Data Requirement: Rotation of Net Weight and Rate Updated on PLC Command
Step # Scale command (from PLC) Scale Floating Point Value Command response from terminal Floating Point Value
1 (PLC clears out any previous rotation with reset) 2 (IND780 terminal sees new command) 3 (PLC adds net weight to rotation) 4 (IND780 terminal sees new command) 5 (PLC adds rate to the rotation) 6 (IND780 terminal sees new command)
3 (dec) loaded into command word O Command ack.= 1 F.P. ind = 30 41 (dec) loaded into command word O
0.0
(null value)
Command ack. = 2 F.P. ind = 30 46 (dec) loaded into command word O Command ack. = 3 F.P. ind = 30
0.0
0.0
At this point, the rotation has been set up. Now the PLC needs to send commands to the IND780 terminal to begin the rotation and advance to the next value when required. 7 (PLC sends the command to report the first field in the rotation.) 8 (IND780 terminal acknowledges the command and sends net weight at every Interface cycle update until the PLC gives the command to report the next rotation field.) 1 (dec) loaded into command word O
1-22
9 (PLC sends the command to report the next field.) Note: if the PLC leaves the 1 (dec) in the command, the IND780 terminal does NOT see this as another command to report the next rotation field. 10 (IND780 terminal acknowledges the command and sends rate at every Interface cycle update until the PLC gives the command to report the next rotation field.) 11 (PLC sends the command to report the next field in the rotation.) 12 (IND780 terminal acknowledges the command and sends net weight at every Interface cycle update until the PLC gives the command to report the next rotation field.) 13 (PLC sends the command to report the next field.) 14 (IND780 terminal acknowledges the command and sends rate at every Interface cycle update until the PLC gives the command to report the next rotation field.)
At approximately every 60 msec the IND780 terminal updates its data with new data, but it does not advance to the next field in the rotation until the PLC sends it the command to report the next field. The PLC should check the floating point indication bits to determine which data is in the floating point value
1-23
Block Transfer
Block Transfer mode is much less efficient than the discrete data modes, which are optimized for real time communications of weight and status data. Block Transfer mode accesses the IND780 Shared Data directory structure each time a data item is accessed. By contrast, the discrete mode communications has a direct interface to a limited number of real time terminal data fields. Do not use Block Transfer mode for real-time communications. When Block Transfer is enabled in integer and divisions, the first quarter (Word0, Word1) is reserved.
1-24
Field Code
Wtxx10 Wtxx11 Wtxx12 Wtxx13 Wsxx02 Wsxx04 Spxx05 Wxxx31 Wxxx32 Wxxx33 Wxxx34 Wxxx35 Wsxx01 Wsxx02 Wsxx04 Wsxx05 Wsxx06 Csxx04 Spxx04 Xpxx01
Description
Gross Weight Net Weight Auxiliary Gross Weight Auxiliary Net Weight Tare Weight Auxiliary Tare Weight Target Coincidence Value Scale Motion (0 or 1) Center of Zero (0 or 1) Over Capacity (0 or 1) Under Zero (0 or 1) Net Mode (0 or 1) Current Scale Mode Tare Weight Auxiliary Tare Weight Current Units Tare Source Auxiliary Weight Units Target Data Stream Type Transaction Counter
Read/Write
R R R R R R R/W R R R R R R R R R R R/W R/W R/W
Length
4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4
Field Code
wtxx01 wtxx02 wtxx03 wtxx04 wtxx05 wtxx06 csxx12 csxx03 spxx01 xdxx03 xdxx04 csxx03 ptxx01 ptxx11
Description
Gross Weight Net Weight Weight Units Auxiliary Gross Weight Auxiliary Net Weight Auxiliary Weight Units Custom Units Name Scale ID (Target) Descriptor Name Current Date Time of Day Software Part Number Print Template 1 Print Literal 1
Read/Write
R R R R R R R/W R/W R/W R R R R/W R/W
Length
13 13 4 13 13 7 13 21 21 12 12 15 40 40
Refer to the IND780 Shared Data Reference provided on the IND780 documentation CD, part number 64057241.
1-25
<<Floating Point Write Field Code: shows where next value will be loaded
<<40 Byte String Data. Note: if string is shorter than 40 bytes it must be left justified and null-terminated >> << 40 Byte String Data. Note: if string is shorter than 40 bytes it must be left-justified (and null-terminated)>> <<Floating Point Read Field Code: requests FP value for BTR 8 Byte (ASCII) String Read Field Code: requests string value for BTR Reserved Reserved 8 Byte>> ASCII
* Display Mode: The integer value of this word determines how the IND780 display operates: 0 = reset display to normal mode, 1 = display until overwritten by PLC or ENTER is pressed, 2 = display for 30 seconds, 3 = display for 60 seconds, any value > 3 = reserved. All Field Codes are six right-justified bytes expanded to eight with two leading spaces. Example SD = wt0101 . Hex value of field code = 2020 7774 3031 3031
1-26
Hardware Setup
Wiring
The IND780 terminals A-B RIO option card uses a three-position removable terminal strip to connect to the A-B RIO network interface (Figure 1-4). Cable distance, type, and termination are specified by Allen-Bradley (See Allen-Bradley documentation for reference on cable design guidelines for the various PLCs). Mettler-Toledo recommends Belden 9463 cable. The connector comes with the RIO option kit.
1-27
Software Setup
The IND780 terminal automatically detects the presence of an A-B RIO Kit option board if one is installed. When an A-B Rio PLC module is detected, the IND780 enables the Allen-Bradley parameters at Setup > Communication > PLC Interface > A-B RIO. Figure 1-5 shows the A-B RIO program block and Figure 1-6 the PLC data format setup block. Default settings are indicated with an asterisk.
1-28
A. Select the Node Address (059 Dec or 0-73 Octal) B. Select Start Quarter (1-4) C. Select Last Rack (Enabled, Disabled). D. Select Data Rate (57.6K, 115.2K, 230.4K). E. Select Block Transfer (Enabled, Disabled).
1-29
A. Select the Format (Integer, Divisions, Floating Point, Template or Application): [default Integer] Changing the Format will delete any existing Message Slots. Integer reports scale weight as a signed 16 bit integer ( 32767). Divisions reports scale weight in display divisions ( 32767). The PLC multiplies the reported divisions by the increment size to calculate the weight in display units. Floating Point displays weight in floating point data format Template Allows the end-user to customize PLC communications input and output data by allowing them to set up input and output templates with shared data variables. This format is fixed and cannot be changed on the fly by the PLC program. The template editor also calculates the input and output sizes upon exit of the editor. In order to populate the data fields, consult the Shared Data Reference Manual (document number 64059110) provided on the CD-ROM supplied with your terminal. Application Allows a TaskExpert program to interact with the PLC input and output data. The TaskExpert program is responsible for setting up all input and output data from the IND780 and to control the data length of the input and output assemblies. For application commands used in TaskExpert, refer to the TaskExpert Reference Manual (document number 64060431). B. Select Byte Order (see Table 1-21): [default Word Swap]
1-30
Word Swap Takes the IEE 754 single-precision floating point format and swaps the two words in the 32-bit double word. This format is compatible with RSLogix 5000 processors. Byte Swap Makes the floating point format compatible with S7 PROFIBUS. Historic Makes the floating point data format compatible with PLC 5 C. Set the Time Interval in milliseconds. (Only when the Format is Template) D. The bottom of this screen (Figure 1-8) displays the number of bytes that will be sent by the IND780 and the number of bytes expected from the PLC. E. Use the Configure drop-down list to select the direction of data flow IND780 >> PLC or PLC >> IND780. (Only when the Format is Template) F. Depending on which format is selected, press the VIEW TABLE softkey to set up the number of Message Slots (1, 2, 3, or 4. In Block Transfer mode, maximum number is 3.) [default is 0], or to configure the Template for communications between the IND780 and the PLC. Figure 1-9 shows the Message Slots View, which is viewed whenever the Format is not Template.
Figure 1-10 shows the Template View, accessed when Format is set to Template. Each message slot will be a Shared Data Variable, entered by the user. These entered message slots are associated only to the Shared Data Variable entered and not to a scale.
1-31
Press the EXIT softkey Press the EDIT softkey Press the NEW softkey Press the DELETE softkey Press the CLEAR softkey
to exit the view screen. to edit an existing slot. to enter a new slot. to delete an existing slot. to delete all existing slots.
Figure 1-11 shows the screen that opens when NEW is selected from the Message Slots View screen (Figure 1-9).
Scale Enter the scale number to be associated with the new Message Slot. Terminal Default is Local; remote terminals 1 through 20 may be selected if remote PLC interface sharing is used.
1-32
IND780 PLC Interface Manual Figure 1-12 shows a series of Template New screens, as accessed from the Template View screen (Figure 1-10).
Figure 1-12: New Template Screens, PLC to IND780 and IND780 to PLC
Slot Automatically assigned. SDName An alphabetic entry field used to define the Shared Data variable associated with the slot. Length (Bytes) and Data Type Automatically displayed once the SDName has been entered. The maximum length of a Shared Data variable cannot exceed 16 bytes when Block Transfer is disabled, or 14 bytes when Block transfer is enabled. Terminal Default is Local; remote terminals 1 through 20 may be selected if remote PLC interface sharing is used.
Refer to the Table 1-7 (Discrete Read) and Table 1-8 (Discrete Write) in this manual for additional information on mapping of discrete read data to the PLC.
Troubleshooting
If the IND780 does not communicate with PLC do the following: Check wiring and network termination. Confirm that the IND780 settings for data type and rack assignment match those in the PLC. Replace the RIO interface kit if the problem persists.
1-33
IND780 PLC Interface Manual If the communication kit was changed from another type, like PROFIBUS, ControlNet or EtherNet I/P, a master reset of the IND780 must be performed.
Status LEDs
The RIO card has an LED indicator to indicate communication status of the card. Figure 1-13 indicates the location of the LED, and Table 1-22 explains its indications.
STATUS LED
Figure 1-13: A-B RIO Card Status LED Table 1-22: A-B RIO Status LED Indications LED Indications No LED Solid Green Blinking LED Meaning Bad card or no power. Check cable wiring or PLC power. Online and communicating Power to network but node not communicating to PLC. Check for rack size or data size mismatch.
Qty. 1 1 3 3
1-34
Programming Examples
The following five Figures show sample screen images from ladder logic programming examples for RSLogix 5000 software (version 13). These examples only demonstrate scanner and adapter configuration, plus conversion of data to real numbers. The floating point example includes Block Transfer functions. Note: The Utilities folder of the documentation CD (part number 64057241) contains complete versions of the examples. These screen images are provided for illustrative purposes only.
1-35
1-36
1-37
1-38
Chapter 2
Overview Communications Node/Rack Address Data Definition Hardware Setup Software Setup Troubleshooting
The PROFIBUS option card enables the IND780 terminal to communicate to a PROFIBUS DP master according to DIN 19 245. It consists of an IND780 terminal backplane-compatible module and software that resides in the terminal, which implements the data exchange. The PROFIBUS option card interfaces to programmable logic controllers (PLCs) such as Texas Instruments 505 series, Siemens S5 series and Siemens S7 series PLCs. The PROFIBUS appears as a block of I/O on the PROFIBUS network. The size and mapping of the I/O depends on the setup of the PROFIBUS card at the IND780. Figure 2-1 shows examples of PROFIBUS interface modules used in the IND780 Panel Mount and Harsh Enclosures.
Figure 2-1: PROFIBUS Interface Module: Panel Mount (top) and Harsh (bottom)
2-1
IND780 PLC Interface Manual The data mapped within the I/O block is defined as Discrete or Shared Data Variables. Based upon the IND780 setup, discrete data is either Integer, Division or Floating Point. Discrete data is sent in groups defined as message blocks. The number of message blocks (1 to 12) is set up within the IND780. While the format of each message block is the same, the data received and displayed within a message block depends on the commands within the block. The Texas Instruments (TI) 505 PLCs interface to the PROFIBUS via an I/O processor called a Field Interface Module (FIM). The FIM bus master recognizes a fixed set of PROFIBUS slave devices, all of which are viewed by it as some sort of remote I/O rack. On power up, the FIM queries each PROFIBUS slave node to determine which of the recognized types a device might be. The FIM then configures itself accordingly. The PROFIBUS option appears to the FIM as a small ET200U I/O rack. The Siemens S5-115 series PLC also interfaces to the PROFIBUS using an IM-308 I/O processor. This device must be locally programmed with the terminal interface type files. Newer Siemens S7 PLCs have the PROFIBUS option on their main controller card.
Communications
PROFIBUS is based on a variety of existing national and international standards. The protocol architecture is based on the Open Systems Interconnection (OSI) reference model in accordance with the international standard ISO 7498. The IND780 terminal supports the PROFIBUS-DP. DP stands for Distributed Peripherals, and is designed for high-speed data transfer at the sensor actuator level. At this level, controllers such as PLCs use a fast serial link to exchange data with their distributed peripherals. Data exchange with these distributed devices is mainly cyclic. The central controller (master) reads the input information from the slaves and sends the output information back to them. It is important that the bus cycle time is shorter than the program cycle time of the controller, which is approximately 10 ms in most applications. The following is a summary of the technical features of the PROFIBUS-DP communications protocol: Transmission Technique: PROFIBUS DIN 19 245 Part 1 EIA RS 485 twisted pair cable or fiber optic 9.6 kbit/s up to 12 Mbit/s, max distance 200 m at 1.5 Mbit/s extendable with repeaters 12 megabaud maximum rate Mono-Master or Multi-Master systems supported Master and Slave Devices, max 126 stations possible
IND780 PLC Interface Manual Cyclic Master-Slave user data transfer and acyclic Master-Master data transfer Operate: Cyclic transfer of input and output data Clear: Inputs are read and outputs are cleared Stop: Only master-master functions are possible
Operation Modes:
Synchronization: Enables synchronization of the inputs and/or outputs of all DP-Slaves Sync-Mode: Outputs are synchronized Freeze-Mode: Inputs are synchronized Cyclic user data transfer between DP-Master(s) and DP-Slave(s) Activation or deactivation of individual DP-Slaves Checking of the configuration of the DP-Slaves Powerful diagnosis mechanisms, three hierarchical levels of the diagnosis Synchronization of inputs and/or outputs Address assignment for the DP-Slaves over the bus Configuration of the DP-Master (DPM1) over the bus Maximum 246 byte input and output data per DP-Slave, typical 32 byte Maximum total bytes (input bytes + output bytes) 358 All messages are transmitted with Hamming Distance HD=4 Watch-Dog Timer at the DP-Slaves Access protection for the inputs/outputs at the DP-Slaves Data transfer monitoring with configurable timer interval at the DP-Master (DPM1) DP-Master Class 2 (DPM2) for example, programming/configuration device DP-Master Class 1 (DPM1) for example, central controller like PLC, CNC, or RC DP-Slave for example, Input/Output device with binary or analog inputs/outputs, drives Coupling or uncoupling of stations without affecting other stations Proven and easy to handle two conductor transmission technique
Functionality:
Device-Types:
2-3
Node/Rack Address
Each IND780 PROFIBUS option card represents one physical node. The node address is chosen by the system designer and then programmed into the IND780 and PLC using the Setup/ Communications/PLC Interface/PROFIBUS tree, accessible through the IND780 front panel user interface. The node address and number of input and output words used to communicate between the terminal and the PLC are programmed into the PLC by using its PROFIBUS network configuration software and the IND780s PROFIBUS GSD-type files. The IND780 setup allows selection of the logical rack (node) address, the option of sending and receiving shared data (Explicit Messages Enabled/Disabled), data format (Integer/Divisions/Floating Point/Template/Application), Byte Order (Byte Swap/Word Swap), and the number of message slots or data assigned to the node. The number of input and output words required and the mapping of I/O data is dependent on these selections. The IND780 appears as a block of I/O data on the PROFIBUS bus. The IND780 terminal will determine the number of input and output words needed for the number of configured message slots and/or the chosen data format. The number of words required is displayed on the PLC Data Format screen of the IND780. The IND780 PROFIBUS GSD has 25 different blocks of I/O defined. Blocks are defined for the various Integer/Division/Floating Point modes. Each block is identified as the number of input and output words configured within the block.
2-4
IND780 PLC Interface Manual Up to 20 terminals can be connected in the cluster. However, the number of message slots available for communications depends on the type of PLC interface. All available PLC message slots can be configured to send or receive data to or from the remote terminals via the cluster. Refer to the appropriate PLC chapters in the IND780 PLC Interface Manual for further details on message slots limitations. To allow bridging of the PLC interface, first a cluster network must be set up among the IND780 terminals. Once the cluster is established, configure the PLC interface on the bridge terminal, set up its data format and assign the required local or remote scales data to the message slots. Figure 2-3 shows an example of two message slots, the first being allocated to scale 1 of the local bridge terminal and a second slot to scale 1 of the remote terminal node 6. For details on configuring the PLC interface in a cluster terminal, refer to the Software Setup section, below. The use of PLC interface sharing is not recommended when real time weight or rate information is required by the PLC for fast process control. The determinism of the terminals PLC interface data update rate is influenced and limited by the characteristics of Ethernet TCP/IP communications used in the cluster network.
Data Definition
Data Formats
The terminals PROFIBUS option card has five types of data exchanges that may be selected. The data types are: Integer, Divisions, Floating Point, Template and Application. In Integer/Divisions/Floating Point mode, each message slot selected to pass data through the terminals PROFIBUS option has its own assigned input and output words for continuous communication to and from the PLC. In these modes, Shared data access is only available when the Setup/ Communications/PLC Interface/PROFIBUS Explicit Messages option is Enabled. This data is used to pass information that cannot be sent in the discrete data because of its size or due to process speed limitations. It uses additional input and output word space. The 2-5
IND780 PLC Interface Manual length of shared data value and data type depends on the type of shared data field requested. In no case does it exceed 10 words (20 bytes). In Template mode, the designer selects the types of data and, in case of string data, the length of the data contained within each data slot. In Application mode, a Task Expert program is written to determine the information contained within the input and output messages to the PLC. The formatting of the data is set up within the application program.
Data Integrity
The terminal has specific bits to allow the PLC to confirm that the data was received without interruption, and the scale is not in an error condition. It is important to monitor these bits. The PLC code must use them to confirm the integrity of the data received for the scale. Refer to the detailed data charts for specific information regarding the Data OK, update in progress, and data integrity bits and their usage.
Discrete Data
Three formats of discrete data are available with the PROFIBUS option card: Integer, division, and floating point. The integer and division formats allow bi-directional communication of discrete bit encoded information or 16-bit binary word (signed integer) numerical values. The floating-point format allows bi-directional communication of discrete bit-encoded information or numeric data encoded in IEEE 754, single-precision floating-point format. The discrete data format affects the input/output word space required per message slot and the amount of input/output words used by the PROFIBUS option card. Integer and division formats require two 16-bit words of input and two 16-bit words of output data per message slot. One slot uses two 16-bit words of input and two 16-bit words of output; two slots use four 16-bit words of input and four 16-bit words of output; three slots use six 16-bit words of input and six 16-bit words of output; and four slots use eight 16-bit words of input and eight 16-bit words of output. The floating-point format requires more space per messages slot because floating point data uses two 16-bit words of data to represent the numeric data alone. The floating-point format requires four 16-bit words of input and four 16-bit words of output data per slot. Four scales using the floating-point format would use 16 words of input and 16 words of output data. Selection of the appropriate format depends on different issues. The range or capacity of the scale used in the application should be considered. The integer format can represent a numerical value of up to 32,767; the division format can represent a numerical value of up to 32,767 divisions (or increments); and, the 2-6
IND780 PLC Interface Manual floating-point format can represent a numerical value encoded in IEEE 754, single precision floating-point format. Floating point is the only format that includes decimal point information as a part of its data. All other formats ignore decimal points in their data. Accommodation of decimal point location must take place in the PLC logic, when it is needed with these formats.
Examples
250 x .01 scale
Scale Reads: 0 2.00 Format sent: Int Div FLT 0 0 0 200 200 2.00 5167 5167 51.67 25000 25000 250.00 51.67 250.00
The integer format could not be used because it would send a negative value once the weight exceeded 32,760.
150 x .001 scale
Scale Reads: 0 2.100 Format sent: Int Div FLT 0 0 0 2100 2100 2.100 (xxxxx) (xxxxx) 51.607 (xxxxx) (xxxxx) 150.000 51.607 150.000
The integer and division formats could not be used because they would send a negative value once the weight exceeded 32,767. Please see the detailed description of data available for each format to determine which is most suitable.
2-7
SETUP
The sequence for setting up the IND780 to communicate on a PROFIBUS Network is detailed in the PROFIBUS Setup section, below.
Integer/Divisions Format
The IND780 supports up to 12 scale slots that it places into one larger Integer Assembly. Scales may be assigned to Scale Slot Assemblies in any combination using the PLC Data Format menus. A scale can be assigned to multiple slots to get different data from the scale, such as weight and rate, reported concurrently to the PLC. The commands are typically single-bit. When the Integer or Division format is selected, each message slot will have two 16-bit words for Read data and two 16-bit words for Write data. Read data refers to the data sent from the IND780 to the PLC (PLC Read). Write Data refers to data sent from the PLC to the IND780 (PLC Write). The Read data consists of one 16-bit word for the IND780s weight information (Word 0 IN) and one 16-bit word for bit-encoded status information (Word 1 IN). The IND780 selects the type of data that is placed in Word 0 IN based on the selection contained in Word 1 OUT, Bits 0, 1 and 2. The PLCs output words Word 0 OUT and Word 1 OUT consist of one 16-bit integer value, which may be used to download a tare or target (Word 0 Out) and one 16-bit word for bit-encoded command information (Word 1 OUT).
2-8
IND780 PLC Interface Manual Table 2-1 and Table 2-2 provide detailed information on the integer and division data formats. Note that the functions of Word 1 IN, Bits 0, 1 and 2 depend on the application setup of OVER/UNDER or Material Transfer. Tables 2-3 and 2-4 are memory maps of the Input and Output Assemblies The IND780 writes the PLC Display command to pd0119 and the Display buffer to pd0118. In order to display this data, the system integrator must write a Task Expert application.
Discrete Read INTEGER or Division Word 0 IN
WORD 0 is a 16-bit, signed integer that may represent the scales gross, net, tare, rate, target, or displayed weight. Three bits, set by the PLC in the Discrete Write Word 1, Bits 0, 1, and 2, designate what data is represented in Discrete Word 0.
Discrete Read INTEGER or Division Word 1 IN Table 2-1: Discrete Read Integer (weight) or Division (div) IND780 >> PLC
Octal Address 0 1 2 3 4 5 6 7 10 11 12 13 14 15 16 17 WORD 0 IN X X X X X X X X X X X X X X X X
12 1
WORD 1 IN Feed
2 2 3 4
Bit number 0 1 2 3 4 5 6 7 8 9 10 11 12
4
Fast Feed
Tolerance OK
Under low tolerance Over high tolerance Comparator 3 Comparator 2 Comparator 1 ENTER key Input 1 Input 2 Input 3 Motion
7 7 7 6 5 5 5
8 9 10
13 14 15
Update in progress
11
2 3 4
5. Bits 5, 6 and 7 provide Comparators 1, 2 and 3 statuses. If the comparator is active, the respective bit is set to 1. 6 Bit 8 is set to a 1 when the ENTER key is pressed on the keypad of the terminal. The bit remains on for 30 seconds then resets to 0.
2-9
10 Bit 14 is set to a 1 when the terminal is in the process of updating its data for the PLC scanner. The PLC should ignore ALL of the data in this case and simply re-scan it. 11 Bit 15 is set to a 1 when the scale is operating properly (NOT over capacity, under capacity, in power-up, in expanded mode, or in setup mode).The PLC program should continuously monitor this bit and the PLC processor rack fault bit (see A-B RIO PLC documentation) to determine the validity of the discrete and/or explicit data transfer. While in the setup mode word 0 data may be present; do not use the data under this condition as the communication connection may stop at any time. 12 When number is negative, word 0 Bit 15 is high and is the least significant bit. Otherwise, when the number is positive, Bit 15 is the most significant bit.
Discrete Write INTEGER or Division Word 1 OUT Table 2-2: Discrete Write Integer (weight) or Division (div)PLC >> IND780
Octal Address 0 1 2 3 4 5 6 7 10 11 12 13 14 15 16 17 WORD 0 OUT X X X X X X X X X X X X X X X X
1
Bit number 0 1 2 3 4 5 6 7
8
Load Tare
5 6
8 9 10 11 12 13 14 15
Display mode
Load Target
3 4 5 6 7 8
2-10
display mode, 1 = display message 1 (aw0101), 2 = display message 2 (aw0102), 3 = display message 3 (aw0103), 4 = display message 4 (aw0104), 5 = display message 5 (aw0105), 6 = Start ID1 sequence, 7 = display message that is written into pd0118. Note: Until these bits are used pd0119 will be set at 0. Change of state of any of these bits resets PLC input word, Bit 8, Enter Key.
10 Bit 12, bit 13, and bit 14 can be used to control the state of the first three discrete outputs on the terminals internal I/O board in slot 5. These are addressed as 0.5.1, 0.5.2, and 0.5.3. Setting the bit to a 1 state causes the output to be turned ON. This action will occur regardless of the discrete output assignment within the IND780. 11 When bit 15 is changed from 0 to 1 the value in WORD 0 is loaded into the target register in the terminal and loaded into the target logic.
Short Name
SelectMode
Data Type
16 Binary
* A transition from 0 to 1of the "enable setpoint" bit causes the PLC Messaging to issue a "restart setpoint" command to the setpoint. Then, the setpoint logic temporarily disables its discrete outputs while it reloads the setpoint values from Shared Data and restarts the setpoint. If the setpoint was running at the time of the restart command, this disabling and restarting causes the setpoint's discrete outputs to temporarily shutoff and turn back on. A transition from 1 to 0 of the "enable setpoint" bit causes the PLC Messaging to issue an "abort setpoint" command to the setpoint.
Offset #
0 2 4 6 8 10 12 14 16 18 20
2-11
Scale slots can be assigned to any combination of scales, including replicating the same scale in multiple slots, in order to get different data such as weight and rate from the same scale concurrently. The length of shared data value depends on the type of shared data field requested. However, it cannot exceed 10 words (20 bytes).
Table 2-5: Integer Output Assembly Map, PLC >> IND780 Offset#
0 2 4 6 8 10 12 14 16 18 20 22 24 26 28 30 32
2-12
* Scale slots can be assigned to any combination of scales, including replicating the same
scale in multiple slots in order to get different data such as weight and rate from the same scale concurrently. ** The length of shared data value is dependent on the type of shared data field. However, it cannot exceed 10 words (20 bytes).
Floating Point
Operational Overview
When the Floating Point format is selected at the IND780, each message slot configured will have four 16-bit words for Read data and three 16-bit words for Write data. Read data refers to the data sent from the IND780 to the PLC (PLC Read). Write Data refers to data sent from the PLC to the IND780 (PLC Write). The first word of the Write data memory map is reserved. The terminal uses integer commands from the PLC to select the floating point weight output data. The terminal recognizes a command when it sees a new value in the scale slot command word. If the command has an associated floating point value (for example, loading a target value), it must be loaded into the floating point value words before the command is issued. Once the terminal recognizes a command, it acknowledges the command by setting a new value in the command acknowledge bits of the scales command response word. It also tells the PLC what floating point value is being sent (via the floating point input indicator bits of the command response word). The PLC should wait until it receives the command acknowledgment from the terminal before sending another command.
2-13
IND780 PLC Interface Manual The terminal has two types of values that it can report to the PLC: real-time and static. When the PLC requests a real-time value, the terminal acknowledges the command from the PLC once but sends and updates the value at every interface update cycle. If the PLC requests a static value, the terminal acknowledges the command from the PLC once and updates the value once. The terminal will continue to send this value until it receives a new command from the PLC. Gross weight and net weight are examples of real-time data. Tare weight, target, feed, and tolerance values are examples of static data. The terminal can send a rotation of up to nine different real-time values for each message slot. The PLC sends commands to the terminal to add a value to the rotation. Once the rotation is established, the PLC must instruct the terminal to begin its rotation automatically, or the PLC may control the pace of rotation by instructing the terminal to advance to the next value. If the terminal is asked to alternate its output data automatically, it will switch to the next value in its rotation at the next interface update cycle. (The interface update cycle has an update rate of up to 17 Hz or 60 milliseconds.) The PLC may control the rotation by sending alternate report next field commands (1 and 2). When the PLC changes to the next command, the terminal switches to the next value in the rotation. The terminal stores the rotation in its shared data so the rotation does not have to be re-initialized after each power cycle. When the PLC does not set up an input rotation, the default input rotation consists of gross weight only. See the floating-point rotation examples for additional information. Table 2-5 through Table 2-8 provide detailed information on the floating-point data format. Read data refers to the PLCs input data and write data refers to the PLCs output data. The IND780 supports up to 12 scale slots that it places into one large Floating Point Assembly. Scales can be assigned to Scale Slot Assemblies in any combination, using the IND780 Setup menus. One scale can be assigned to multiple scale slots to get different data for a scale, such as weight and rate, reported concurrently to the PLC. Commands are byte-oriented.
Table 2-6: Discrete Read Floating Point (float) IND780 >> PLC
Octal Address 0 1 2 3 4 5 6 7 10 11 12 FP Input Ind 1 FP Input Ind 2 FP Input Ind 3
7 7 7
WORD 1 FP value X X X X X X X X X X X
WORD 2 FP value X X X X X X X X X X X
Bit number 0 1 2 3 4 5 6 7 8 9 10
4
Fast Feed
Tolerance OK
RESERVED
Under Negative Tolerance Over Positive Tolerance Selected scale Custom Bit Custom Bit ENTER key Input 1 Input 2
9 9 6 6 5
2-14
WORD 1 FP value X X X X X
WORD 2 FP value X X X X X
Bit number 11 12 13 14 15
11
13 13
Data integrity 2
14
2 3 4 6
5 Bit 5 will be set to a 1 when the associated scale is selected on the IND780 console panel.
10 Bit 12 is set to a 1 when the scale is in motion (unstable). 11 The Data Integrity bit in WORD 0 - bit 13 is used in conjunction with the bit in WORD 3 - bit 14 to insure that the floating point data is valid. For the data to be valid both bits must have the same polarity. These bits will change to the opposite state every interface update cycle. If they do not have the same value the data is invalid and the PLC should ignore ALL of the data in this case and re-scan it. 12 Bit 13 is set to a 1 when the scale is in net mode (a tare has been taken). 13 Bit 14 and Bit 15 (Command Acknowledge bits) are used by the terminal to inform the PLC that it has received a new, valid command. The terminal rotates sequentially among values 1, 2, 3, 1, 2, 3, 1, 2, to acknowledge it has processed a new command. 14 Bit 15 is set to a 1 when the scale is operating properly (NOT over capacity, under capacity, in power-up, or in setup mode). The PLC program should continuously monitor this bit and the PLC processor rack fault bit (see A-B RIO PLC documentation) to determine the validity of the discrete and/or explicit data transfer. While in the setup mode the input floating data will be set to 0; additionally the communication connection may stop at any time.
Dec
0 1 2 3 4 Gross Weight* Net Weight* Tare Weight* Fine Gross Weight* Fine Net Weight*
Data
2-15
Data
Fine Tare Weight* Rate ALxx01 SDV, instance by scale** ALxx02 SDV, instance by scale** ALxx01 SDV, instance by scale** ALxx02 SDV, instance by scale** Low-pass filter corner frequency, instance by scale Notch filter frequency, instance by scale Target value, instance by scale Target positive tolerance value, instance by scale Target fine feed value, instance by scale Target negative tolerance value, instance by scale Target spill value, instance by scale Primary units, low increment size Reserved Last terminal error code No data response-command successful No data response-command failed
These are real-time fields that the PLC may request either through an input rotation or a report command. All other fields may only be requested through a report command. Replace xx with the scale instance e.g. 01 for scale 1.
WORD 01 OUT
WORD 1 OUT
Reserved
Scale command
X X X X X X X
2-16
IND780 PLC Interface Manual WORD 01 OUT WORD 2 OUT3 FP load value
X X X X
WORD 12 OUT
SDName PD0119
Disable LCD display Enable LCD display 7 Set normal display mode 7,9 Display message 1 7,9 Display message 2 7,9 Display message 3 7,9 Display message 4 7,9 Display Message 5 7,9 Start ID1 sequence 7,9 Display SDV PD0118 7,9 Disable weight display 7 Enable weight display 7 Set discrete output 0.5.1 ON 7 Set discrete output 0.5.2 ON 7 Set discrete output 0.5.3 ON 7 Set discrete output 0.5.4 ON 7 Set discrete output 0.5.1 OFF 7 Set discrete output 0.5.2 OFF 7 Set discrete output 0.5.3 OFF 7 Set discrete output 0.5.4 OFF 7 Master control relay OFF7, 12 Master control relay ON7, 12 Set target value 4,10, 13 Set target fine feed value 4,10 Set - tolerance value 4,10 Set target value and apply4, 10, 14 Start target logic 7,10 Abort target logic 7,10 Target use gross weight 7,10 Target use net weight 7,10
SPxx05
SPxx04 SPxx04
2-17
4. 5. 6. 7. 8. 9.
10. Target, Fine Feed, Tolerances, Restart, Abort and other Target variables are relative to each scale. Note: Restart of an active Target will cause the associated outputs to cycle off then back on. 11. Does not disable the PLC tare functions. 12. Setting the master control relay OFF turns off all outputs and stops target logic. The target logic must be restarted after the master control relay is turned ON. 13. Target logic must be restarted to apply the new target value. 14. New target value is applied when command is sent.
2-18
Offset #
0 2 4 6 8 10 12 14 16 18 20 22 24 26 28 30 32 34 36 38 40 42 44 46 48 50 52 54 56 58 60 62 64 66 68 70 72 Reserved
2-19
You can assign scale slots to any combination of scales, including replicating the same scale in multiple slots, in order to get different data, such as weight and rate, from the same scale concurrently.
** The length of shared data value is dependent on the type of shared data field. However, it cannot exceed 10 words (20 bytes).
2-20
Offset #
54 56 58 60 62 64 66 68 70 72 74 76 78 80 82 84 86 88 90 92 94 96 98 100 102 ~ 116
th th th th th th th th th
You can assign scale slots to any combination of scales, including replicating the same scale in multiple slots, in order to get different data, such as weight and rate, from the same scale concurrently.
** The length of shared data value is dependent on the type of shared data field requested. However, it cannot exceed 10 words (20 bytes).
2-21
As long as the PLC leaves the 11 (dec) in the command word the IND780 will update the net value every interface update cycle.
2-22
The PLC should always wait to receive a command acknowledgment before sending the next command to the IND780. After the PLC finishes loading its target value, it can resume monitoring the weight information it requires by sending a command to report some type of weight or set up a rotation of reported data.
Table 2-14: Data Requirement: Rotation of Gross Weight and Rate Updated on interface Update Cycle
Step # 1 Action PLC clears out any previous rotation with reset IND780 sees new command PLC adds gross weight to rotation IND780 sees new command PLC adds rate to the rotation IND780 sees new command 46 (dec) loaded into command word QW OR WY:11 RESERVED for Future Use Command ack. = 3 F.P. ind = 30 (null value) 40 (dec) loaded into command word QW OR WY:11 (null value) Command ack. = 2 F.P. ind = 30 Scale Command (from PLC) 3 (dec) loaded into command word QW OR WY:11 Command ack.= 1 F.P. ind = 30 Scale Floating Point Value Command Response from IND780 Floating Point Value
At this point, the rotation has been set up. Now the PLC needs to command the IND780 to begin the rotation.
2-23
10
11
This rotation continues until the PLC sends a different command. At approximately every 60 msec the IND780 updates its data with the next field in its rotation. The PLC must check the floating point indication bits to determine which data is in the floating point value.
Refer to the IND780 Terminal Shared Data Reference (document 64059110), provided on the IND780 documentation CD (part number 64057241).
Table 2-15: Data Requirement: Rotation of Net Weight and Rate Updated on PLC Command
Step # 1 Action PLC clears out any previous rotation with reset IND780 sees new command PLC adds net weight to rotation 41 (dec) loaded into command word Scale command (from PLC) 3 (dec) loaded into command word Command ack.= 1 F.P. ind = 30 Scale Floating Point Value Command response from terminal Floating Point Value
(null value)
2-24
IND780 sees new command PLC sends the command to report the first field in the rotation
(null value)
At this point, the rotation has been set up. Now the PLC needs to send commands to the IND780 to begin the rotation and advance to the next value when required. IND780 acknowledges the command and sends net weight at every interface update cycle until the PLC gives the command to report the next rotation field PLC sends the command to report the next field.) Note: if the PLC leaves the 1 (dec) in the command, the IND780 does NOT see this as another command to report the next rotation field IND780 acknowledges the command and sends rate at every interface update cycle until the PLC gives the command to report the next rotation field PLC sends the command to report the next field in the rotation IND780 acknowledges the command and sends net weight at every interface update cycle until the PLC gives the command to report the next rotation field 1 (dec) loaded into command word
10
11
12
2-25
13
14
At approximately every 60 msec the IND780 updates its data with new data, but it does not advance to the next field in the rotation until the PLC sends it the command to report the next field. The PLC should check the floating point indication bits to determine which data is in the floating point value.
Shared Data
Operational Overview
PROFIBUS PLCs can access the terminals Shared Data. Since PROFIBUS communication supports up to 244-byte messages at speeds typically in the range of 1.5 to 12 megahertz, there is no need for two separate modes of communication, unlike Allen-Bradley and its block transfer. PROFIBUS PLCs can read IND780 Shared Data variables, write new values to IND780 Shared Data variables, and write operator messages on the terminals lower display. For PROFIBUS, the PLC output data has additional fields for accessing Shared Data. The PLC must specify the Shared Data command and variable name in the PLC output message. If the command is a write command, then the PLC output message must also contain the write field value. The maximum length of the value is 20 bytes. When the Shared Data command is a read command, the PLC input message will have a read field containing the data from the Shared Data variable specified in the output message. The maximum length of the data reported in the read field is 20 bytes. The Shared Data variables are self-typing. The IND780 2-26
IND780 PLC Interface Manual terminal determines the type of any valid data field in the message from the variables name and definition in Shared Data. The terminal will not allow string data to be written in a floating point variable or vice versa.
The shared data read field value contains the value of the shared data variable specified in the shared data output (from the PLC to the terminal). It is only present when the command from the shared data output requests read shared data. This value is self-typing; for example, it could be a floating point number or a string variable. The length is determined by the variable selected but will not exceed 20 bytes. See the tables following the Shared Data Output for a list of possible variables and their contents.
The terminal processes a shared data command on demand by the PLC. When a new value is placed in the shared data command word, the terminal performs the command issued. The terminal does not provide real time information to the PLC; it supplies a snapshot of the data, not an automatic update of new values of the same shared data command. Instead, the PLC must request the information again by setting a new value in the shared data command word. To do successive reads, for example, the PLC must alternate between a null command and a read command in the shared data command word. For the 2-27
IND780 PLC Interface Manual most efficient processing, the PLC should set up the terminal name, the variable name, and the write value (if any) while it is setting the null command. Once that is completed, the PLC can then set the shared data command to read or write. For a complete listing of Shared Data Fields, refer to the IND780 Shared Data Reference provided on the IND780 documentation CD, part number 64057241
Hardware Setup
Wiring
The IND780 terminals PROFIBUS option card has a DB-9 connector to connect to the PROFIBUS network interface (Figure 2-5). Cable distance, type, and termination are specified by PROFIBUS. (See the PLC documentation for cable design guidelines for the various PLCs.)
PROFIBUS CONNECTOR WIRING PIN 1 2 3 4 5 6 7 8 9 SIGNAL None None RxD/TxD + RTS Gnd BUS +5V BUS None RxD/TxD None
2-28
IND780 PLC Interface Manual The IND780 harsh unit requires a right angle connector, Siemens part number 6ES7 972-0BA12-0XA0. The panel mount can use the right angle connector, or a straight connector, METTLER TOLEDO part number 64054361.
Software Setup
When the IND780 terminal detects the presence of a PROFIBUS option card, the PROFIBUS screen is enabled in Setup at Communication > PLC Interface > PROFIBUS (Figure 2-6). To format PLC data, access Communication > PLC Interface > Data Format (Figure 2-7). Default settings are indicated with an asterisk. You must enter setup and configure each scale that is interfaced with the PROFIBUS network.
2-29
2-30
PROFIBUS Setup
PROFIBUS Setup:
The PLC Setup block lets you specify how the PROFIBUS interface is used. Several options are available to correspond with your system setup. 1. Select Communication > PLC Interface > PROFIBUS (Figure 2-8).
2. Enter the Node Address (0125). 3. Select Shared Data Enabled or Disabled. Refer to the Discrete Read and Discrete Write tables in this manual for additional information on mapping of Discrete read data to the PLC.
2-31
IND780 PLC Interface Manual 4. Figure 2-10 shows the screen with Template selected as the format, revealing the Time Interval, Configure, and directional displays. When Application format is selected, only the Format box appears on this screen.
A. Select the Format (Integer, Divisions, Floating Point, Template or Application): [default Integer] Changing the Format will delete any existing Message Slots. Integer reports scale weight as a signed 16 bit integer ( 32767). Divisions reports scale weight in display divisions ( 32767). The PLC multiplies the reported divisions by the increment size to calculate the weight in display units. Floating Point displays weight in floating point data format Template Allows the end-user to customize PLC communications input and output data by allowing them to set up input and output templates with shared data variables. This format is fixed and cannot be changed on the fly by the PLC program. The template editor also calculates the input and output sizes upon exit of the editor. In order to populate the data fields, consult the Shared Data Reference Manual (document number 64059110) provided on the CD-ROM supplied with your terminal. Application Allows a TaskExpert program to interact with the PLC input and output data. The TaskExpert program is responsible for setting up all input and output data from the IND780 and to control the data length of the input and output assemblies. For application commands used in TaskExpert, refer to the TaskExpert Reference Manual (document number 64060431). Word Swap Takes the IEE 754 single-precision floating point format and swaps the two words in the 32-bit double word. This format is compatible with RSLogix 5000 processors. Byte Swap Makes the floating point format compatible with S7 PROFIBUS.
C. Set the Time Interval in milliseconds. (Only when the Format is Template) 2-32
IND780 PLC Interface Manual D. The bottom of this screen (Figure 2-9) displays the number of bytes that will be sent by the IND780 and the number of bytes expected from the PLC. E. Use the Configure drop-down list to select the direction of data flow IND780 >> PLC or PLC >> IND780. (Only when the Format is Template) F. Depending on which format is selected, press the VIEW TABLE softkey to set up the number of Message Slots (1, 2, 3, 4, 12) [default is 0], or to configure the Template for communications between the IND780 and the PLC. Figure 2-11 shows the Message Slots View, which is viewed whenever the Format is not Template.
Figure 2-12 shows the Template View, accessed when Format is set to Template. Each message slot will be a Shared Data Variable, entered by the user. These entered message slots are associated only to the Shared Data Variable entered and not to a scale.
Press the EXIT softkey Press the EDIT softkey Press the NEW softkey Press the DELETE softkey
to exit the view screen. to edit an existing slot. to enter a new slot. to delete an existing slot. 2-33
IND780 PLC Interface Manual Press the CLEAR softkey to delete all existing slots.
Figure 2-13 shows the screen that opens when NEW is selected from the Message Slots View screen (Figure 2-11).
Scale Enter the scale number to be associated with the new Message Slot. Terminal Default is Local; remote terminals 1 through 20 may be selected if remote PLC interface sharing is used. Figure 2-14 shows a series of Template New screens, as accessed from the Template View screen (Figure 2-12).
Figure 2-14: New Template Screens, PLC to IND780 and IND780 to PLC
Slot Automatically assigned. SDName An alphabetic entry field used to define the Shared Data variable associated with the slot.
2-34
IND780 PLC Interface Manual Length (Bytes) and Data Type Automatically displayed once the SDName has been entered. The maximum length of a Shared Data variable cannot exceed 16 bytes when Block Transfer is disabled, or 14 bytes when Block transfer is enabled. Terminal Default is Local; remote terminals 1 through 20 may be selected if remote PLC interface sharing is used. For a complete listing of Shared Data Fields, refer to the IND780 Shared Data Reference. Refer to Table 2-6 (Discrete Read) and Table 2-8 (Discrete Write) in this manual for additional information on mapping of discrete read data to the PLC.
If the IND780 is set up for the Template or Application Mode, the programmer may have to build a custom PLC Block using the GSD module type Universal Module. When building this Block the Input/Output Unit Parameter must be set for Word. A slot within the block should not be greater than 16 words. If more than 16 words are required, add another slot.
2-35
The PROFIBUS GSD files for the IND780 are available free of charge. They are included on the documentation CD (part number 64057241).
Troubleshooting
If the IND780 does not communicate with PLC do the following: Check wiring and network termination. Confirm that the IND780 settings for data type and rack assignment match those in the PLC. Replace the PROFIBUS interface kit if the problem persists. If the communication kit was changed from another type, like A-B RIO, ControlNet or EtherNet I/P, a master reset of the IND780 must be performed.
2-36
Qty. 1 1 3 3
2-37
Chapter 3
Overview Data Definition Hardware Setup Software Setup Troubleshooting ControlNet Option Kit Programming Examples
The ControlNet Kit option enables the IND780 terminal to communicate to ControlNet Programmable Logic Controllers (PLCs) through direct connection to the ControlNet network. The kit consists of a backplanecompatible I/O module and software that resides in the IND780 terminal to implement the data exchange. Figure 3-1 shows two views of the module, and Figure 3-2 points out its components.
3-1
IND780 PLC Interface Manual Do not plug an EtherNet cable into the RJ-45 connector shown at left in Figure 3-2. It is for diagnostic use only. The ControlNet Kit option has the following features: User-programmable node (MAC ID) address. Capability for bi-directional discrete mode communications (Class 1 Messaging) of weight or display increments, status, and control data between the PLC and the IND780.
Definition of Terms
Some terms (such as Target) used by the ControlNet PLC application have a different sense from their use by the IND780 terminal. Table 3-1 offers definitions specific to ControlNet.
Table 3-1: ControlNet Definition of Terms
Definition An Adapter Class product emulates functions provided by traditional rack-adapter products. This type of node exchanges real-time I/O data with a Scanner Class product. It does not initiate connections on its own. In ControlNet communication protocol scheduled (cyclic) message transfer between a PLC and CIP Adapter Class device. In ControlNet communication protocol unscheduled message transfer between a PLC and CIP Adapter Class device. This is used by the IND780 for explicit messaging. A connection is a relationship between two or more application objects on different nodes. The connection establishes a virtual circuit between end points for transfer of data. Node resources are reserved in advance of data transfer and are dedicated and always available. Connected messaging reduces data handling of messages in the node. Connected messages can be Implicit or Explicit. See also Unconnected Messaging. Source for I/O connection or message requests. Initiates an I/O connection or explicit message connection. Explicit Messages can be sent as a connected or unconnected message. CIP defines an Explicit Messaging protocol that states the meaning of the message. This messaging protocol is contained in the message data. Explicit Messages provide a onetime transport of a data item. Explicit Messaging provide the means by which typical request/response oriented functions are performed (e.g. module configuration). These messages are typically point-to-point.
Connected Messaging
Connection Originator
Explicit Messaging
3-2
IND780 PLC Interface Manual Term Definition Implicit Messages are exchanged across I/O Connections with an associated Connection ID. The Connection ID defines the meaning of the data and establishes the regular/repeated transport rate and the transport class. No messaging protocol is contained within the message data as with Explicit Messaging. Implicit Messages can be point-to-point or multicast and are used to transmit applicationspecific I/O data. This term is used interchangeably with the term I/O Messaging. Function that uses the I/O messaging services of another (I/O Server) device to perform a task. Initiates a request for an I/O message to the server module. The I/O Client is a Connection Originator. Used interchangeably with the term Implicit Messaging. Function that provides I/O messaging services to another (I/O Client) device. Responds to a request from the I/O Client. I/O Server is the target of the connection request. Function that uses the Explicit messaging services of another (Message Server) device to perform a task. Initiates an Explicit message request to the server device. Function that provides Explicit messaging services to another (Message Client) device. Responds to an Explicit message request from the Message Client. A Scanner Class product exchanges real-time I/O data with Adapter Class and Scanner Class products. This type of node can respond to connection requests and can also initiate connections on its own. Destination for I/O connection or message requests. Can only respond to a request, cannot initiate an I/O connection or message. Provides a means for a node to send message requests without establishing a connection prior to data transfer. More overhead is contained within each message and the message is not guaranteed destination node resources. Unconnected Messaging is used for non-periodic requests (e.g. network Who function). Explicit messages only. See also Connected Messaging.
Implicit Messaging
Message Client
Message Server
Scanner Class
Target
Unconnected Messaging
Communications
The IND780 terminal utilizes component parts to ensure complete compatibility with the Allen-Bradley ControlNet network. An IND780 terminal is recognized as a generic ControlNet device by the PLC. Each ControlNet option connected to the ControlNet network represents a physical node. The connection is facilitated by BNC connectors on the option card. The wiring between the PLC and the IND780 ControlNet connection uses RG-6 CATV cable and 75 ohm impedance matching transformer tap for each node. The 3-3
IND780 PLC Interface Manual cable is commonly referred to as coaxial cable. The cable installation procedures and specification including distance and termination requirements are the same as recommended by Allen-Bradley for the ControlNet network. The normal connection is to the channel A connector, the channel B connector is only used for redundant connection networks. The IND780 terminals communication update rate is setup by the use of Allen Bradley software Networx for ControlNet. The IND780 only uses Class 1 cyclic data for discrete data and explicit messages for access to the IND780 Shared Data Variables. Explicit message blocks may be connected or unconnected; the PLC programmer must make this choice.
Node Address
Each ControlNet option represents one physical node. This address is chosen by the system designer, and then programmed into the IND780 terminal and PLC. The IND780 terminals address is programmed through Communication > PLC Interface > ControlNet in the setup menu. IND780 address entry is in decimal.
Data Formats
The ControlNet Kit option provides discrete data transfer, Class 1 messaging. Discrete data is continuously available. The ControlNet option has its own logical node address to send and receive information to and from the PLC. There are five data formats: Integer, Divisions, Floating Point, Template and Application.
3-4
Up to 20 terminals can be connected in the cluster. However, the number of message slots available for communications depends on the type of PLC interface. All available PLC message slots can be configured to send or receive data to or from the remote terminals via the cluster. Refer to the appropriate PLC chapters in the IND780 PLC Interface Manual for further details on message slots limitations. To allow bridging of the PLC interface, first a cluster network must be set up among the IND780 terminals. Once the cluster is established, configure the PLC interface on the bridge terminal, set up its data format and assign the required local or remote scales data to the message slots. Figure 3-4 shows an example of two message slots, the first being allocated to scale 1 of the local bridge terminal and a second slot to scale 1 of the remote terminal node 6. For details on configuring the PLC interface in a cluster terminal, refer to the Software Setup section, below. The use of PLC interface sharing is not recommended when real time weight or rate information is required by the PLC for fast process control. The determinism of the terminals PLC interface data update rate is influenced and limited by the characteristics of Ethernet TCP/IP communications used in the cluster network.
3-5
Data Definition
The ControlNet Kit option uses discrete data for its communication with PLCs. Data transfer is accomplished via the PLCs cyclic messaging.
Data Integrity
The IND780 has specific bits to allow the PLC to confirm that data was received without interrupt and the IND780 is not in an error condition. It is important to monitor these bits. Any PLC code should use them to confirm the integrity of the data received by the IND780. Refer to the data charts for specific information regarding the Data OK, Update in Progress, Data Integrity bits and their usage.
3-6
Discrete Data
Five formats of discrete data are available with the ControlNet Kit option: Integer, divisions, floating point, template and application. Only one type of data format may be selected and used by the IND780. The integer and division formats allow bi-directional communication of discrete bit encoded information or 16 bit binary word numerical values(see Table 3-6 and Table 3-7). The floating-point format allows bi-directional communication of discrete bit encoded information and numeric data encoded in IEEE 754, single precision floating point format. The data format of discrete data will affect the data size required in the configuration of the PLC. The IND780 console PLC message slot setup screen provides data size requirements in bytes, except for the Application data format. Selection of the appropriate format depends on issues such as the range or capacity of the scale used in the application. The integer format can represent a numerical value up to 32,767. The division format can represent a value up to 32,767 scale divisions or increments. The floating-point format can represent a value encoded in IEEE 754, single precision floating point format. Floating point is the only data format that includes decimal point information. Integer and division formats ignore decimal points. Accommodation of decimal point location must occur in the PLC logic, when it is needed with these formats. Changing the Data Format to be used by the IND780 will clear all Message Slots. Data format is set up in the Communication > PLC Interface > Data Format screen.
Examples
250 x .01 scale IND780 Displays: Integer Division Floating Point 0 0 0 2.00 Format sent: 200 200 2.00 5167 5167 51.67 25000 25000 250.00 51.67 250.00
50,000 x 10 scale IND780 Displays: Integer Division Floating Point 0 0 0 200 Format sent: 200 20 200 5160 516 5160 -(15536) 5000 50000 5160 50000
The integer format could not be used because it would send a negative value once the weight exceeded 32,767.
3-7
The integer and division formats could not be used because they would send a negative value once the weight exceeded 32.767.
Byte Order
Word Swap takes the IEE 754 single-precision floating point format and swaps the two words in the 32-bit double word. This format is compatible with RSLogix 5000 processors. Byte Swap makes the floating point format compatible with S7 PROFIBUS.
Message Slots
There may be up to 12 message slots for discrete data transfer, Class 1 messaging, in Integer, Divisions and Floating Point Data Formats. Each message slot is assigned to a local or remote scale and scales may be repeated in additional message slots. Remote scales must reside in an IND780 Ethernet TCP clustered to the IND780 containing the ControlNet interface. The integer and division formats provide (two 16-bit words of input and two 16-bit words of output data) per Message Slot. Each Message Slots first input word provides scale weight data and the input weight data may be selected by the PLC using the Message Slots second output word bit 0, bit 1 and bit 2. Table 3-2 and Table 3-3 provide input and output usage information.
Table 3-2: ControlNet PLC Input Data and Data Usage (Integer and Division)
PLC Input Bytes 0 1 2 3 4 5 6 7 8 9 10 11 5 4 3 2 1 PLC Input Words 0 Reserved Reserved Reserved Reserved Message Slot 1 Weight Data Message Slot 1 Weight Data Message Slot 1 Scale Status Message Slot 1 Scale Status Message Slot 2 Weight Data Message Slot 2 Weight Data Message Slot 2 Scale Status Message Slot 2 Scale Status Usage
3-8
3-9
3-10
The floating point format provides four 16-bit words of input data and three 16-bit words of output data) per Message Slot. See Table 3-4 and Table 3-5 for details. The number of Message Slots is setup in Communication > PLC Interface > Data Format setup screen (Figure 3-11, Figure 3-12).
Table 3-4: ControlNet PLC Floating Point Input Words
PLC Output Words 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 Reserved Reserved Message Slot 1, Reserved Message Slot 1 Floating Point data Message Slot 1 Floating Point data Message Slot 1, Scale Status, See Message Slot Table Message Slot 2, Reserved Message Slot 2 Floating Point data Message Slot 2 Floating Point data Message Slot 2, Scale Status, See Message Slot Table Message Slot 3, Reserved Message Slot 3 Floating Point data Message Slot 3 Floating Point data Message Slot 3, Scale Status, See Message Slot Table Message Slot 4, Reserved Message Slot 4 Floating Point data Message Slot 4 Floating Point data Message Slot 4, Scale Status, See Message Slot Table Message Slot 5, Reserved Message Slot 5 Floating Point data Bits 0 7 Reserved Reserved Message Slot 1, Command Response, See Message Slot Table Message Slot 1 Floating Point data Message Slot 1 Floating Point data Message Slot 1, Scale Status, See Message Slot Table Message Slot 2, Command Response, See Message Slot Table Message Slot 2 Floating Point data Message Slot 2 Floating Point data Message Slot 2, Scale Status, See Message Slot Table Message Slot 3, Command Response, See Message Slot Table Message Slot 3 Floating Point data Message Slot 3 Floating Point data Message Slot 3, Scale Status, See Message Slot Table Message Slot 4, Command Response, See Message Slot Table Message Slot 4 Floating Point data Message Slot 4 Floating Point data Message Slot 4, Scale Status, See Message Slot Table Message Slot 5, Command Response, See Message Slot Table Message Slot 5 Floating Point data Bits 8 - 15
3-11
3-12
3-13
In the template data format a message slot is a shared data variable. The number of message slots is limited to 496 bytes (I/O), including the 4 bytes of reserve in the IND780 output (PLC input) data.
3-14
WORD 1 IN
WORD 2 IN X X X X X X X X X X X X X X X X
13
WORD 3 IN Feed
3 3 4 5
Bit number 0 1 2 3 4 5 6 7 8 9 10 11 12 13
11 5
Fast Feed
Tolerance OK
Under low tolerance Over high tolerance Comparator 3 Comparator 2 Comparator 1 ENTER key Input 1 Input 2 Input 3 Motion
8 9 9 7 6 6 6
9 10
Update in progress
12
14 15
Bit 0 and Bit 1 are used only in material transfer mode. Bit 2 indicates that tolerance is OK in both material transfer mode and over/under mode. When equal to 1, Bit 3 and Bit 4 indicate that target is under negative tolerance or over positive tolerance, respectively.
4 5
6. Bits 5, 6 and 7 provide Comparators 1, 2 and 3 statuses. If the comparator is active, the respective bit is set to 1. 7 Bit 8 is set to a 1 when the ENTER key is pressed on the keypad of the terminal. The bit remains on for 30 seconds then resets to 0.
3-15
10 Bit 13 is set to a 1 when the scale is in net mode (a tare has been taken). 11 Bit 14 is set to a 1 when the terminal is in the process of updating its data for the PLC scanner. The PLC should ignore ALL of the data in this case and simply re-scan it. 12 Bit 15 is set to a 1 when the scale is operating properly (NOT over capacity, under capacity, in power-up, in expanded mode, or in setup mode).The PLC program should continuously monitor this bit and the PLC processor rack fault bit (see PLC documentation) to determine the validity of the discrete and/or explicit data transfer. While in the setup mode Word 2 data may be present; do not use the data under this condition as the communication connection may stop at any time. 13 When number is negative, Word 2 Bit 15 is high and is the least significant bit. Otherwise, when the number is positive, Bit 15 is the most significant bit.
Table 3-7: Discrete Write Integer or Division PLC (ControlNet) >> IND780, per Message Slot
Octal Address WORD 0 OUT
1
WORD 1 OUT
Bit number
0 1 2 3 4 5 6 7 10 11 12 13 14 15 16 17
Notes for Table 3-7:
1
X X X X X X X X X X X X X X X X
Select 12 Select 22 Select 32 Load Tare3 Clear4 Tare5 Print6 Zero7 Abort/Start Target8 Display mode9 Display mode9 Display mode9 Output 110 Output 210 Output 310 Load Target11
0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
WORD 0 is a 16-bit, signed integer value that may represent the scales tare or target value to be downloaded. Bit 3 or bit 15 is then triggered to instruct the terminal to load the value into either the tare or target register. A binary value in bit 0, bit 1, and bit 2 select the data that will be sent by the terminal in Discrete Read WORD 0. 0 = gross weight, 1 = net weight, 2 = displayed weight, 3 = tare weight, 4 = target, 5 = rate, 6 or 7 = reserved. Any value greater than 7 will cause gross weight to be sent. A transition from 0 to 1 loads the value from WORD 0 into the tare register of the IND780; the IND780 will use the loaded value as the tare. A transition from 0 to 1 initiates a CLEAR command. A transition from 0 to 1 initiates a TARE command.
3 4 5
3-16
display mode, 1 = display message 1 (aw0101), 2 = display message 2 (aw0102), 3 = display message 3 (aw0103), 4 = display message 4 (aw0104), 5 = display message 5 (aw0105), 6 = Start ID1 sequence, 7 = display message that is written into pd0118. Note: Until these bits are used pd0119 will be set at 0. Change of state of any of these bits resets PLC input word, Bit 8, Enter Key.
10 Bit 12, bit 13, and bit 14 can be used to control the state of the first three discrete outputs on the terminals internal I/O board in slot 5. These are addressed as 0.5.1, 0.5.2, and 0.5.3. Setting the bit to a 1 state causes the output to be turned ON. This action will occur regardless of the discrete output assignment within the IND780. 11 When bit 15 is changed from 0 to 1 the value in WORD 0 is loaded into the target register in the terminal and loaded into the target logic.
Floating Point
Operational Overview
The IND780 uses integer commands from the PLC to select the floating point weight input data. The IND780 recognizes a command when it sees a new value in the Message Slot command word. If the command has an associated floating point value (for example: loading a target value), it must be loaded into the floating point value words before the command is issued. Once the IND780 recognizes a command, it acknowledges the command by setting a new value in the command acknowledge bits of the scales command response word. The IND780 also tells the PLC what floating point value is being sent (via the floating point input indicator bits of the command response word). The PLC should wait until it receives the command acknowledgment from the IND780 before sending another command. The IND780 can report two types of values to the PLC: real-time and static. When the PLC requests a real-time value, the IND780 acknowledges the command from the PLC once but sends and updates the value at every Interface update cycle. If the PLC requests a static value, the IND780 acknowledges the command from the PLC once and updates the value once. The IND780 will continue to send this value until it receives a new command from the PLC. Gross weight and net weight are examples of real-time data. Tare weight, target, feed, and tolerance values are examples of static data. The IND780 can send a rotation of up to nine different real-time values. The PLC sends commands to the IND780 to add a value to the rotation. Once the rotation is established, the PLC must instruct the IND780 to begin its rotation automatically, or the PLC may control the pace of rotation by instructing the IND780 to advance to the next value. If the IND780 is asked to automatically alternate its output data, it will switch to the next value in its rotation at the next Interface update cycle. (The Interface update cycle has an update rate of up to 17 Hz or 60 milliseconds.) The PLC may control the rotation by sending alternate report next field commands (1 and 2). When the PLC changes to the next command, the IND780 switches to the next value in the rotation order. The IND780 stores the rotation in its shared 3-17
IND780 PLC Interface Manual data so the rotation does not have to be re-initialized after each power cycle. When the PLC does not set up an input rotation, the default input rotation consists of gross weight only. See the floating-point command examples in Table 3-12 through Table 3-15 for additional information. The method of handling string and floating point data varies between Allen-Bradley PLC generations. The IND780 provides floating point data in the order entered in Data Format setup. Table 3-8 to Table 3-11 provide detailed information on the floating-point data format. Read data refers to the PLCs input data and write data refers to the PLCs output data.
Table 3-8: Discrete Read Floating Point IND780 >> PLC Input, per Message Slot
Octal Address WORD 0
0
WORD 1
WORD 1 3 FP value
WORD 1 4 FP value
WORD 5 Status
Bit number
0 1 2 3 Reserved
X X X X
X X X X
Feed2 Fast Feed2 Tolerance OK3 Under Negative Tolerance4 Over Positive Tolerance4 Selected scale5 Custom Bit6 Custom Bit6 ENTER key8 Input 19 Input 29 Input 39 Motion10 Net mode12
0 1 2 3
X X X X
X X X X X X X X X X
4 5 6 7 8 9 10 11 12 13
FP Input Ind 17 FP Input Ind 27 FP Input Ind 37 FP Input Ind 47 FP Input Ind 57 Data integrity111
X X X X X X
WORD 0
WORD 1
16 17
Notes for Table 3-8:
0 1
X X
X X
14 15
WORD 0 and WORD 1 are reserved 16 bit words, only present in message slot 1. The bits in WORD 3 and WORD 4 are a single-precision floating point value that may represent the scales gross, tare, net, target, fine gross, fine tare, fine net, or filter setting data. The PLC command in the respective scales output word determines what data will be sent. Bit 0 and Bit 1 are used only in material transfer mode. Bit 2 indicates that tolerance is OK in both material transfer and over/ under modes. Bit 3 and Bit 4 are active in both material transfer and over/under modes. Bit 5 will be set to a 1 when the associated scale is selected on the IND780 console panel. Bit 6 and Bit 7 are user defined, and correspond to users Task Expert Application usage. Bit 6 is associated to Shared Data Variable ASxx01, instance by scale. Bit 7 is associated with Shared Data Variable ASxx02, instance by scale. The Floating Point Input Indication bits (WORD 2, Bits 8-12) are used to determine what type of data is being sent in the floating point value (WORD 3 and WORD 4). These bits correspond to a decimal value of 0-31 that represents a particular type of data. See the Floating Point Input Indication Table to determine what type of data. Bit 8 is set to a 1 when the ENTER key is pressed on the terminals keypad. The bit clears to 0 when the PLC sends floating point command 75 to the IND780 terminal or after 30 seconds of no ENTER key activity. Bit 9, Bit 10, and Bit 11 mirror the state of the first three discrete inputs of the internal I/O board in slot 5 (0.5.1, 0.5.2 and 0.5.3). If the input is ON then the bit is set to a 1.
2 3 4 5 6
10 Bit 12 is set to a 1 when the scale is in motion (unstable). 11 The Data Integrity bit in WORD 2 - bit 13 is used in conjunction with the bit in WORD 5 - bit 14 to insure that the floating point data is valid. For the data to be valid both bits must have the same polarity. These bits will change to the opposite state every interface update cycle. If they do not have the same value the data is invalid and the PLC should ignore ALL of the data in this case and re-scan it. 12 Bit 13 is set to a 1 when the scale is in net mode (a tare has been taken). 13 Bit 14 and Bit 15 (Command Acknowledge bits) are used by the terminal to inform the PLC that it has received a new, valid command. The terminal rotates sequentially among values 1, 2, 3, 1, 2, 3, 1, 2, to acknowledge it has processed a new command. 14 Bit 15 is set to a 1 when the scale is operating properly (NOT over capacity, under capacity, in power-up, or in setup mode). The PLC program should continuously monitor this bit and the PLC processor rack fault bit (see A-B RIO PLC documentation) to determine the validity of the discrete and/or explicit data transfer. While in the setup mode the input floating data will be set to 0; additionally the communication connection may stop at any time.
Dec
Data
0 1 2
3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 28 29 30 31
* **
Fine Gross Weight* Fine Net Weight* Fine Tare Weight* Rate ALxx01 SDV, instance by scale ** ALxx02 SDV, instance by scale ** AJxx01 SDV, instance by scale ** AJxx02 SDV, instance by scale ** Low-pass filter frequency Notch filter frequency Target value, instance by scale Target positive tolerance value, instance by scale Target Fine Feed value, instance by scale Target negative tolerance value, instance by scale Target spill value, instance by scale Primary units, low increment size Not used Last IND780 error code No data response command successful No data response command failed
These are real-time fields that the PLC may request either through an input rotation or a report command. All other fields may only be requested through a report command. SDV means Shared Data Variable.
3-20
WORD 1
Bit number
0 1 2 3 4 5 6 7 10 11 12 13 14 15 16 17
Notes for Table 3-10:
0 1
X X X X X X X X X X X X X X X X
0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
WORD 0 is a reserved 16 bit word, only present in message slot 1. The Bits in WORD 2 and WORD 3 are a single-precision floating point value. This value is used with the command in WORD 1 to instruct the terminal to download the floating point value into the field specified in the command. The command Word 1 is used to instruct the IND780 what data to send in the discrete read data, to load the floating point data in the write command, and to control the IND780 discrete outputs or display. See Table 3-11, the PLC Output Command Table, for a list of the available commands and their respective decimal or hex value.
Not all commands will require a value in the floating point load value words.
3-21
00
Report next rotation field @ next Interface update 1 cycle Report next rotation field
1,2
76
4c
PD01 19
1 2 3 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 27 28 29
01 02 03 0a 0b 0c 0d 0e 0f 10 11 12 13 14 15 16 17 18 19 1b 1c 1d
78 79 80
4e 4f 50 51 52 53 54 55 56 57 58 59 5a 5b 5c 5d 64 65 66 67 68 69
Reset rotation Report gross weight Report net weight Report tare weight
1,3 1,3
81 82 83 84 85 86 87
Display message 1 Display message 2 Display message 3 Display message 4 Display Message 5 Start ID1 sequence
1,3
7,9
1,3
7,9
7,9
Report fine net weight Report fine tare weight Report Rate
1,3
7,9
1,3
7,9
7,9
6 6
88 89 90 91 SPxx05 SPxx11
6
7 7
Report low-pass filter 3 frequency Report notch filter 3 frequency Report Target value
3,10 3,10
Set discrete output 0.5.1 7 ON Set discrete output 0.5.2 7 ON Set discrete output 0.5.3 7 ON Set discrete output 0.5.4 7 ON Set discrete output 0.5.1 7 OFF Set discrete output 0.5.2 7 OFF Set discrete output 0.5.3 7 OFF Set discrete output 0.5.4 7 OFF Master control relay OFF
12 7,
Report (-) Tolerance 3,10 value Report spill value Report AJxx01 Report AJxx02
3,10
3,5,,6
3,5,,6
7,
3-22
30 40 41 42 43 44 45 46 47 48 60 61 62 63 64 65 66 67 68 69 70 71 72 73
1e 28 29 2a 2b 2c 2d 2e 2f 30 3c 3d 3e 3f 40 41 42 43 44 45 46 47 48 49
Report primary increment 3 size Add gross weight to 7 rotation Add net weight to rotation
7
110 111 112 113 114 115 116 117 ALxx01 ALxx02
6
6e 6f 70 71 72 73 74 75 76 77 78 79 7a 7b 7c 83 a0 a1 a2 a3 a4 A5 a6 a7
SPxx0 5
Add tare weight to 7 rotation Add fine gross weight to 7 rotation Add fine net weight to 7 rotation Add fine tare weight to 7 rotation Add rate to rotation
5,6,7 7
Set target value and 4, 10, 14 apply Start target logic Abort target logic
7,10 7,10
7,10
7,10
Target, absolute weight 1 7,10 speed Target, absolute weight 2 7,10 speed Enable target latching Disable target latching Reset target latch Set target spill value
7 7,10
Load numeric tare value Pushbutton tare 7 command Clear command Print command Zero command Select scale 1 Select scale 2
7
7,10
4, 10
4,10
SPxx1 1 QC01 49
Select next scale Custom print 1 Custom print 2 Custom print 3 Custom print 4 Custom print 5
7
Write Calibration to 7 EEProm Disable Tare on IND780 7,11 console Enable Tare on IND780 7 console Disable push button Tare 7,11 on IND780 console Enable push button Tare 7 on IND780 console Disable numeric Tare on 7,11 IND780 console Enable numeric Tare on
3-23
frequency 74 75 4a 4b
4
4. 5. 6. 7. 8. 9.
10. Target, Fine Feed, Tolerances, Restart, Abort and other Target variables are relative to each scale. Note: Restart of an active Target will cause the associated outputs to cycle off then back on. 11. Does not disable the PLC tare functions. 12. Setting the master control relay OFF turns off all outputs and stops target logic. The target logic must be restarted after the master control relay is turned ON. 13. Target logic must be restarted to apply the new target value. 14. New target value is applied when command is sent.
3-24
3-25
1 (PLC sends command to IND780 terminal to report net weight) 2 (IND780 terminal sees new command)
none required
As long as the PLC leaves the 11 (dec) in the command word, the IND780 terminal will update the net value every interface update cycle.
Table 3-13: Data Requirement: Load Target Value = 21.75 for Scale 1
Step # Scale command (from PLC) Scale Floating Point Value Command response from terminal Floating Point Value
1 (PLC loads floating point value first) 2 (PLC sends command to set target 1 cutoff value) 3 (IND780 terminal sees new command , loads the value into the target and ends a return message to indicate the new target value) 4 (PLC instructs IND780 terminal to start using new target value) 5 (IND780 terminal sees new command) 114 (dec) loaded into command word O 110 (dec) loaded into command word O
0.0
The PLC should always wait to receive a command acknowledgment before sending the next command to the IND780 terminal. After the PLC finishes loading its target value, it can resume monitoring the weight information required by sending a command to report some type of weight or set up a rotation of reported data.
3-26
1 (PLC clears out any previous rotation with reset) 2 (IND780 terminal sees new command) 3 (PLC adds gross weight to rotation) 4 (IND780 terminal sees new command) 5 (PLC adds rate to the rotation) 6 (IND780 terminal sees new command)
3 (dec) loaded into command word O Command ack.= 1 F.P. ind = 30 40 (dec) loaded into command word O 0.0
(null value)
Command ack. = 2 F.P. ind = 30 46 (dec) loaded into command word O Command ack. = 3 F.P. ind = 30
0.0
0.0
At this point, the rotation has been set up. Now the PLC needs to command the IND780 terminal to begin the rotation. 7 (PLC sends the command to begin the rotation at interface update cycle) 8 (IND780 terminal sends gross weight at interface update cycle ~ 60 msec) 9 (PLC leaves 0 in its command word and the IND780 terminal sends the rate value at the next interface update cycle) 10 (PLC leaves 0 in its command word and IND780 terminal sends the gross value at next interface update cycle) 11 (PLC leaves 0 in command word and IND780 terminal sends the rate value at the next interface update cycle) 0 (dec) loaded into command word O RESERVED for Future Use 0 (dec) loaded into command word O Command ack. = 0 F.P. ind = 0 Floating point value = gross wt. 0 (dec) loaded into command word O RESERVED for Future Use Command ack. = 0 F.P. ind = 6 Floating point value = rate 0 (dec) loaded into command word O Command ack. = 0 F.P. ind = 0 Floating point value = gross wt.
This rotation continues until the PLC sends a different command. At approximately every 60 msec the
3-27
IND780 terminal updates its data with the next field in its rotation. The PLC must check the floating point indication bits to determine which data is in the floating point value.
Table 3-15: Data Requirement: Rotation of Net Weight and Rate Updated on PLC Command
Step # Scale command (from PLC) Scale Floating Point Value Command response from terminal Floating Point Value
1 (PLC clears out any previous rotation with reset) 2 (IND780 terminal sees new command) 3 (PLC adds net weight to rotation) 4 (IND780 terminal sees new command) 5 (PLC adds rate to the rotation) 6 (IND780 terminal sees new command)
3 (dec) loaded into command word O Command ack.= 1 F.P. ind = 30 41 (dec) loaded into command word O (null value) Command ack. = 2 F.P. ind = 30 46 (dec) loaded into command word O RESERVED for Future Use Command ack. = 3 F.P. ind = 30
0.0
0.0
0.0
At this point, the rotation has been set up. Now the PLC needs to send commands to the IND780 terminal to begin the rotation and advance to the next value when required. 7 (PLC sends the command to report the first field in the rotation.) 8 (IND780 terminal acknowledges the command and sends net weight at every Interface update cycle until the PLC gives the command to report the next rotation field.) 9 (PLC sends the command to report the next field.) Note: if the PLC leaves the 1 (dec) in the command, the IND780 terminal does NOT see this as another command to report the next rotation field. 10 (IND780 terminal 1 (dec) loaded into command word O
Command ack. = 2
Floating point
3-28
acknowledges the command and sends rate at every Interface update cycle until the PLC gives the command to report the next rotation field.) 11 (PLC sends the command to report the next field in the rotation.) 12 (IND780 terminal acknowledges the command and sends net weight at every Interface update cycle until the PLC gives the command to report the next rotation field.) 13 (PLC sends the command to report the next field.) 14 (IND780 terminal acknowledges the command and sends rate at every Interface update cycle until the PLC gives the command to report the next rotation field.) 2 (dec) loaded into command word O 1 (dec) loaded into command word O
F.P. ind = 6
value = rate
At approximately every 60 msec the IND780 terminal updates its data with new data, but it does not advance to the next field in the rotation until the PLC sends it the command to report the next field. The PLC should check the floating point indication bits to determine which data is in the floating point value
IND780 PLC Interface Manual should be aware that the IND780 terminals discrete I/O updates are synchronized with the terminals interface update rate and not with the PLC I/O scan rate. This may cause a noticeable delay in reading inputs or updating outputs as observed from the PLC to real world signals. Consult the IND780 Terminal Technical Manual for discrete I/O wiring.
Hardware Setup
Wiring
The IND780 terminals ControlNet option card uses one BNC coaxial connector, channel A or two BNC coaxial connectors for redundant ControlNet configurations, one for each channel (Figure 3-6). Cable distance, type, and termination are specified by Allen-Bradley (See Allen-Bradley documentation for reference on cable design guidelines for the various PLCs).
ControlNet Signal Shield
Figure 3-7 shows the array of status indicator LEDs on the ControlNet card (see also Table 3-1). Table 3-16 explains the meaning of the indicators.
Module Status Module Owned
1 4
2 3
Channel A Channel B
Figure 3-7: ControlNet Status Indicator LEDs Table 3-16: ControlNet Status Indications
LED # Indication LED State Description
Green 1 Module Status Green, flashing Red Red, flashing Off 2 Channel A Red Alternating red/green Red, flashing Off
Connection in Run state Connecting Connection Idle Major fault Minor fault Module not initialized Major fault Self test Node configuration error; duplicate MAC ID, etc. Channel disabled
an d
3 2 3-30
And
Channel B Channel
or
3
or
Channel B
Normal operation of channel Temporary error (node will self-correct) or not configured No other nodes, or media fault Network configuration error No connection has been opened A connection has been opened towards the module
Module Owned
Off Green
3-31
Software Setup
The IND780 terminal automatically detects the presence of a ControlNet Kit option board if one is installed. When the IND780 detects that a ControlNet board is present, it enables the ControlNet parameters in a program block under Setup > Communication > PLC Interface > ControlNet. Figure 3-8 shows the ControlNet program block and Figure 3-9 the PLC data format setup block at Communication > PLC Interface > Data Format, with default settings indicated by an asterisk.
3-32
3-33
IND780 PLC Interface Manual 1. Figure 3-10 shows the screen with Template selected as the format, revealing the Time Interval, Configure, and directional displays. When Application format is selected, only the Format box appears on this screen.
A. Select the Format (Integer, Divisions, Floating Point, Template or Application): [default Integer] Changing the Format will delete any existing Message Slots. Integer reports scale weight as a signed 16 bit integer ( 32767). Divisions reports scale weight in display divisions ( 32767). The PLC multiplies the reported divisions by the increment size to calculate the weight in display units. Floating Point displays weight in floating point data format Template Allows the end-user to customize PLC communications input and output data by allowing them to set up input and output templates with shared data variables. This format is fixed and cannot be changed on the fly by the PLC program. The template editor also calculates the input and output sizes upon exit of the editor. In order to populate the data fields, consult the Shared Data Reference Manual (document number 64059110) provided on the CD-ROM supplied with your terminal. Application Allows a TaskExpert program to interact with the PLC input and output data. The TaskExpert program is responsible for setting up all input and output data from the IND780 and to control the data length of the input and output assemblies. For application commands used in TaskExpert, refer to the TaskExpert Reference Manual (document number 64060431). B. Select Byte Order: [default Word Swap] Word Swap Takes the IEE 754 single-precision floating point format and swaps the two words in the 32-bit double word. This format is compatible with RSLogix 5000 processors. Byte Swap Makes the floating point format compatible with S7 PROFIBUS. 3-34
IND780 PLC Interface Manual C. Set the Time Interval in milliseconds. (Only when the Format is Template) D. Use the Configure drop-down list to select the direction of data flow IND780 >> PLC or PLC >> IND780. (Only when the Format is Template) E. The bottom of this screen (Figure 3-12) displays the number of bytes that will be sent by the IND780 and the number of bytes expected from the PLC. F. Depending on which format is selected, press the VIEW TABLE softkey to set up the number of Message Slots (maximum number is 12, default is 0), or to configure the Template for communications between the IND780 and the PLC. Figure 3-13 shows the Message Slots View, which is viewed whenever the Format is not Template.
Figure 3-14 shows the Template View, accessed when Format is set to Template. Each message slot will be a Shared Data Variable, entered by the user. These entered message slots are associated only to the Shared Data Variable entered and not to a scale.
Press the EXIT softkey Press the EDIT softkey Press the NEW softkey
to exit the view screen. to edit an existing slot. to enter a new slot. 3-35
IND780 PLC Interface Manual Press the DELETE softkey Press the CLEAR softkey to delete an existing slot. to delete all existing slots.
Figure 3-15 shows the screen that opens when NEW is selected from the Message Slots View screen (Figure 3-13).
Scale Enter the scale number to be associated with the new Message Slot. Terminal Default is Local; remote terminals 1 through 20 may be selected if remote PLC interface sharing is used. Figure 3-16 shows a series of Template New screens, as accessed from the Template View screen (Figure 3-14).
Figure 3-16: New Template Screens, PLC to IND780 and IND780 to PLC
3-36
IND780 PLC Interface Manual SDName An alphabetic entry field used to define the Shared Data variable associated with the slot. Length (Bytes) and Data Type Automatically displayed once the SDName has been entered. Terminal Default is Local; remote terminals 1 through 20 may be selected if remote PLC interface sharing is used. For a complete listing of Shared Data Fields, refer to the IND780 Shared Data Reference. Refer to Table 3-6 (Discrete Read) and Table 3-7 (Discrete Write) in this manual for additional information on mapping of discrete read data to the PLC.
Troubleshooting
If the IND780 does not communicate with PLC, do the following: Check wiring and network termination. Confirm that the IND780 settings for data type and node assignment match those in the PLC and that each IND780 has a unique node assignment. Replace the ControlNet interface kit if the problem persists. If the communication kit was changed from another type, like PROFIBUS or Remote I/O or EtherNet I/P, a master reset of the IND780 must be performed.
Qty. 1 1 1 3
3-37
Programming Examples
The following Figures show screen images of ladder logic programming examples for RSLogix 5000 software (version 13). Note: The Utilities folder of the documentation CD (part number 64057241) contains complete versions of the examples. These screen images are provided for illustrative purposes only.
The following RSLogix 5000 screens for Integer, Division and Floating Point data formats only show an example of a particular Input and Output size configuration. The Connection Parameters I/O sizes must be appropriately configured with reference to the number of slots assigned in the IND780 PLC Data Format Message Slots settings. Table 3-18 and Table 3-19 show the relationship between the IND780 message slots and the RSLogix 5000 I/O sizing for Integer, Division and Floating Point data formats.
Table 3-18: Message Slot and PLC I/O Sizes (Integer/ Division) IND780 Integer/ Division Data
Message Slots Bytes (8 Bit)
1 2 3-38
8 12
4 8
4 6
2 4
3 4 5 6 7 8 9 10 11 12
16 20 24 28 32 36 40 44 48 52
12 16 20 24 28 32 36 40 44 48
8 10 12 14 16 18 20 22 24 26
6 8 10 12 14 16 18 20 22 24
Table 3-19: Message Slot and PLC I/O Sizes (Floating Point) IND780 Floating Point Data
Message Slots Bytes (8 Bit) IND780 >> PLC Input PLC Output >> IND780 Input
1 2 3 4 5 6 7 8 9 10 11 12
12 20 28 36 44 52 60 68 76 84 92 100
8 14 20 26 32 38 44 50 56 62 68 74
6 10 14 18 22 26 30 34 38 42 46 50
4 7 10 13 16 19 22 25 28 31 34 37
3-39
3-40
3-41
3-42
Chapter 4
Overview Data Definition Software Setup Troubleshooting EtherNet / IP Option Kit Programming Examples
EtherNet / IP, short for "EtherNet Industrial Protocol," is an open industrial networking standard that takes advantage of commercial, off-the-shelf EtherNet communication chips and physical media. This networking standard supports both implicit messaging (real-time I/O messaging) and explicit messaging (message exchange). The protocol is supported by ControlNet International (CI), the Industrial Ethernet Association (IEA) and the Open DeviceNet Vendor Association (ODVA).
EtherNet / IP utilizes commercial, off-the-shelf EtherNet hardware (for example, switches and routers) and is fully compatible with the Ethernet TCP/IP protocol suite. It uses the proven Control and Information Protocol (CIP) to provide control, configuration, and data collection capability.
The kit enables the IND780 terminal to communicate to EtherNet / IP Programmable Logic Controllers (PLCs) through direct connection to the EtherNet / IP network at either 10 or 100 MBPS speed. The kit consists of a backplane-compatible I/O module, mounting hardware, and a ferrite. Software to implement the data exchange resides in the IND780 terminal. The EtherNet / IP Kit option has the following features: User-programmable IP addressing. Capability for bi-directional discrete mode communications (Class 1 Messaging) of weight or display increments, status, and control data between the PLC and the IND780.
4-1
IND780 PLC Interface Manual Figure 4-1 and Figure 4-2 show an EtherNet / IP module and its components. Note that the modules address is set in software (see Figure 4-8), and the DIP switches indicated in Figure 4-2 must all be set to OFF.
Definition of Terms
Some terms (such as Target) used by the EtherNet / IP PLC application have a different sense from their use by the IND780 terminal. Table 4-1 provides definitions specific to EtherNet / IP.
Table 4-1: EtherNet / IP Definition of Terms Term Adapter Class Class 1 Messaging Class 3 Messaging Definition An Adapter Class product emulates functions provided by traditional rackadapter products. This type of node exchanges real-time I/O data with a Scanner Class product. It does not initiate connections on its own. In EtherNet / IP communication protocol scheduled (cyclic) message transfer between a PLC and CIP Adapter Class device. In EtherNet / IP communication protocol unscheduled message transfer between a PLC and CIP Adapter Class device. This is used by the IND780 for explicit messaging. A connection is a relationship between two or more application objects on different nodes. The connection establishes a virtual circuit between end points for transfer of data. Node resources are reserved in advance of data transfer and are dedicated and always available. Connected messaging reduces data handling of messages in the node. Connected messages can be Implicit or Explicit. See also Unconnected Messaging.
Connected Messaging
4-2
Explicit Messaging
Implicit Messaging
I/O Client I/O Messaging I/O Server Message Client Message Server Scanner Class Target
Unconnected Messaging
Communications
The IND780 terminal utilizes component parts to ensure complete compatibility with the Allen-Bradley EtherNet / IP network. An IND780 terminal is recognized as a generic EtherNet / IP device by the PLC.
4-3
IND780 PLC Interface Manual Each EtherNet / IP option connected to the EtherNet / IP network represents a physical IP Address. The connection is made via a RJ-45 connector on the option card (see Figure 4-2). The wiring between the PLC and the IND780 EtherNet / IP connection uses EtherNet twisted pair cable. The cable installation procedures and specification including distance and termination requirements are the same as recommended by AllenBradley for the EtherNet / IP network. The IND780 only uses Class 1 cyclic data for discrete data and explicit messages for access to the IND780 Shared Data Variables. Explicit message blocks may be connected or unconnected; the PLC programmer must make this choice.
IP Address
Each EtherNet / IP option represents one physical IP Address. This address is chosen by the system designer, and then programmed into the IND780 terminal and PLC. There is also a DHCP client feature for EtherNet / IP to use a host server to assign addresses. The IND780 terminals address is programmed through Communication > PLC Interface > EtherNet / IP in the setup menu. IND780 IP Address entry must be unique for each IND780.
Data Formats
The EtherNet / IP Kit option provides discrete data transfer, Class 1 messaging. Discrete data is continuously available. The EtherNet / IP option has its own logical IP address to send and receive information to and from the PLC. There are five data formats: Integer, Divisions, Floating Point, Template and Application.
4-4
Up to 20 terminals can be connected in the cluster. However, the number of message slots available for communications depends on the type of PLC interface. All available PLC message slots can be configured to send or receive data to or from the remote terminals via the cluster. Refer to the appropriate PLC chapters in the IND780 PLC Interface Manual for further details on message slots limitations. To allow bridging of the PLC interface, first a cluster network must be set up among the IND780 terminals. Once the cluster is established, configure the PLC interface on the bridge terminal, set up its data format and assign the required local or remote scales data to the message slots. Figure 4-4 shows an example of two message slots, the first being allocated to scale 1 of the local bridge terminal and a second slot to scale 1 of the remote terminal node 6. For details on configuring the PLC interface in a cluster terminal, refer to the Software Setup section, below. The use of PLC interface sharing is not recommended when real time weight or rate information is required by the PLC for fast process control. The determinism of the terminals PLC interface data update rate is influenced and limited by the characteristics of Ethernet TCP/IP communications used in the cluster network.
4-5
IND780 PLC Interface Manual Figure 4-5 shows a typical EtherNet/IP network arrangement, with IND780 terminals connected directly to a Logix controller without the use of the terminals PLC interface sharing.
Data Definition
The EtherNet / IP Kit option uses discrete data for its communication with PLCs. Data transfer is accomplished via the PLCs cyclic messaging.
Data Integrity
The IND780 has specific bits to allow the PLC to confirm that data was received without interruption and that the IND780 is not in an error condition. It is important to monitor these bits. Any PLC code should use them to confirm the integrity of the data received by the IND780. Refer to the data charts for specific information regarding the Data OK, Update in Progress and Data Integrity bits and their usage.
4-6
IND780 PLC Interface Manual The EDS file provided on the Documentation CD has no Assembly Instance or data size limitations. The IND780 programming controls the Assembly Instance and data size limitations.
Discrete Data
Five formats of discrete data are available with the EtherNet / IP Kit option: Integer, divisions, floating point, template and application. Only one type of data format may be selected and used by the IND780. The integer and division formats allow bi-directional communication of discrete bit encoded information or 16 bit binary word (see Table 4-6 and Table 4-7 for an explanation) numerical values. The floating-point format allows bi-directional communication of discrete bit encoded information and numeric data encoded in IEEE 754, single precision floating point format. The data format of discrete data will affect the data size required in the configuration of the PLC. The IND780 console PLC message slot setup screen provides data size requirements in bytes, except for the Application data format. Selection of the appropriate format depends on issues such as the range or capacity of the scale used in the application. The integer format can represent a numerical value up to 32,767. The division format can represent a value up to 32,767 scale divisions or increments. The floating-point format can represent a value encoded in IEEE 754, single precision floating point format. Floating point is the only data format that includes decimal point information. Integer and division formats ignore decimal points. Accommodation of decimal point location must take place in the PLC logic, when it is needed with these formats. Changing the Data Format to be used by the IND780 will clear all Message Slots. Data format is set up in the Communication > PLC Interface > Data Format screen.
Examples
250 x .01 scale
IND780 Displays: Integer Division Floating Point 0 0 0 0 2.00 Format sent: 200 200 2.00 5167 5167 51.67 25000 25000 250.00 51.67 250.00
50,000 x 10 scale
IND780 Displays: 0 200 Format sent: 5160 50000
4-7
The integer format could not be used because it would send a negative value once the weight exceeded 32,767.
The integer and division formats could not be used because they would send a negative value once the weight exceeded 32.767.
Byte Order
Word Swap takes the IEE 754 single-precision floating point format and swaps the two words in the 32-bit double word. This format is compatible with RSLogix 5000 processors. Byte Swap makes the floating point format compatible with S7 PROFIBUS.
Message Slots
There may be up to 12 message slots for discrete data transfer, Class 1 messaging, in Integer, Divisions and Floating Point Data Formats. Each message slot is assigned to a local or remote scale and scales may be repeated in additional message slots. Remote scales must reside in an IND780 Ethernet TCP clustered to the IND780 containing the Ethernet I/P interface. The integer and division formats provide (two 16-bit words of input and two 16-bit words of output data) per Message Slot. Each Message Slots first input word provides scale weight data and the input weight data may be selected by the PLC using the Message Slots second output word bit 0, bit 1 and bit 2. The following two Tables provide input and output usage information.
Table 4-2: EtherNet / IP PLC Input Data and Data Usage (Integer and Division) PLC Input Bytes
0 1 2 3 4 5 6 7 3 2 1
Usage
Message Slot 1 Weight Data Message Slot 1 Weight Data Message Slot 1 Scale Status Message Slot 1 Scale Status Message Slot 2 Weight Data Message Slot 2 Weight Data Message Slot 2 Scale Status Message Slot 2 Scale Status
4-8
Usage
Message Slot 3 Weight Data Message Slot 3 Weight Data Message Slot 3 Scale Status Message Slot 3 Scale Status Message Slot 4 Weight Data Message Slot 4 Weight Data Message Slot 4 Scale Status Message Slot 4 Scale Status Message Slot 5 Weight Data Message Slot 5 Weight Data Message Slot 5 Scale Status Message Slot 5 Scale Status Message Slot 6 Weight Data Message Slot 6 Weight Data Message Slot 6 Scale Status Message Slot 6 Scale Status Message Slot 7 Weight Data Message Slot 7 Weight Data Message Slot 7 Scale Status Message Slot 7 Scale Status Message Slot 8 Weight Data Message Slot 8 Weight Data Message Slot 8 Scale Status Message Slot 8 Scale Status Message Slot 9 Weight Data Message Slot 9 Weight Data Message Slot 9 Scale Status Message Slot 9 Scale Status Message Slot 10 Weight Data Message Slot 10 Weight Data Message Slot 10 Scale Status Message Slot 10 Scale Status Message Slot 11 Weight Data Message Slot 11 Weight Data Message Slot 11 Scale Status Message Slot 11 Scale Status Message Slot 12 Weight Data Message Slot 12 Weight Data Message Slot 12 Scale Status Message Slot 12 Scale Status
4-9
Usage
Message Slot 1 Weight Data Message Slot 1 Weight Data Message Slot 1 Scale Command Message Slot 1 Scale Command Message Slot 2 Weight Data Message Slot 2 Weight Data Message Slot 2 Scale Command Message Slot 2 Scale Command Message Slot 3 Weight Data Message Slot 3 Weight Data Message Slot 3 Scale Command Message Slot 3 Scale Command Message Slot 4 Weight Data Message Slot 4 Weight Data Message Slot 4 Scale Command Message Slot 4 Scale Command Message Slot 5 Weight Data Message Slot 5 Weight Data Message Slot 5 Scale Command Message Slot 5 Scale Command Message Slot 6 Weight Data Message Slot 6 Weight Data Message Slot 6 Scale Command Message Slot 6 Scale Command Message Slot 7 Weight Data Message Slot 7 Weight Data Message Slot 7 Scale Command Message Slot 7 Scale Command Message Slot 8 Weight Data Message Slot 8 Weight Data Message Slot 8 Scale Command Message Slot 8 Scale Command Message Slot 9 Weight Data Message Slot 9 Weight Data Message Slot 9 Scale Command Message Slot 9 Scale Command Message Slot 10 Weight Data Message Slot 10 Weight Data Message Slot 10 Scale Command Message Slot 10 Scale Command
4-10
Usage
Message Slot 11 Weight Data Message Slot 11 Weight Data Message Slot 11 Scale Command Message Slot 11 Scale Command Message Slot 12 Weight Data Message Slot 12 Weight Data Message Slot 12 Scale Command Message Slot 12 Scale Command
The floating point format provides four 16-bit words of input data and three 16-bit words of output data) per Message Slot. See Table 4-4 and Table 4-5 for details. The number of Message Slots is set up in Communication > PLC Interface > Data Format setup menu (Figure 4-9).
Table 4-4: EtherNet / IP PLC Floating Point Input Words PLC Output Words
0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17
Bits 0 7
Message Slot 1, Reserved Message Slot 1 Floating Point data Message Slot 1 Floating Point data Message Slot 1, Scale Status, See Message Slot Table Message Slot 2, Reserved Message Slot 2 Floating Point data Message Slot 2 Floating Point data Message Slot 2, Scale Status, See Message Slot Table Message Slot 3, Reserved Message Slot 3 Floating Point data Message Slot 3 Floating Point data Message Slot 3, Scale Status, See Message Slot Table Message Slot 4, Reserved Message Slot 4 Floating Point data Message Slot 4 Floating Point data Message Slot 4, Scale Status, See Message Slot Table Message Slot 5, Reserved Message Slot 5 Floating Point data
Bits 8 15
Message Slot 1, Command Response, See Message Slot Table Message Slot 1 Floating Point data Message Slot 1 Floating Point data Message Slot 1, Scale Status, See Message Slot Table Message Slot 2, Command Response, See Message Slot Table Message Slot 2 Floating Point data Message Slot 2 Floating Point data Message Slot 2, Scale Status, See Message Slot Table Message Slot 3, Command Response, See Message Slot Table Message Slot 3 Floating Point data Message Slot 3 Floating Point data Message Slot 3, Scale Status, See Message Slot Table Message Slot 4, Command Response, See Message Slot Table Message Slot 4 Floating Point data Message Slot 4 Floating Point data Message Slot 4, Scale Status, See Message Slot Table Message Slot 5, Command Response, See Message Slot Table Message Slot 5 Floating Point data
4-11
Bits 0 7
Message Slot 5 Floating Point data Message Slot 5, Scale Status, See Message Slot Table Message Slot 6, Reserved Message Slot 6 Floating Point data Message Slot 6 Floating Point data Message Slot 6, Scale Status, See Message Slot Table Message Slot 7, Reserved Message Slot 7 Floating Point data Message Slot 7 Floating Point data Message Slot 7, Scale Status, See Message Slot Table Message Slot 8, Reserved Message Slot 8 Floating Point data Message Slot 8 Floating Point data Message Slot 8, Scale Status, See Message Slot Table Message Slot 9, Reserved Message Slot 9 Floating Point data Message Slot 9 Floating Point data Message Slot 9, Scale Status, See Message Slot Table Message Slot 10, Reserved Message Slot 10 Floating Point data Message Slot 10 Floating Point data Message Slot 10, Scale Status, See Message Slot Table Message Slot 11, Reserved Message Slot 11 Floating Point data Message Slot 11 Floating Point data Message Slot 11, Scale Status, See Message Slot Table Message Slot 12, Reserved Message Slot 12 Floating Point data Message Slot 12 Floating Point data Message Slot 12, Scale Status, See Message Slot Table
Bits 8 15
Message Slot 5 Floating Point data Message Slot 5, Scale Status, See Message Slot Table Message Slot 6, Command Response, See Message Slot Table Message Slot 6 Floating Point data Message Slot 6 Floating Point data Message Slot 6, Scale Status, See Message Slot Table Message Slot 7, Command Response, See Message Slot Table Message Slot 7 Floating Point data Message Slot 7 Floating Point data Message Slot 7, Scale Status, See Message Slot Table Message Slot 8, Command Response, See Message Slot Table Message Slot 8 Floating Point data Message Slot 8 Floating Point data Message Slot 8, Scale Status, See Message Slot Table Message Slot 9, Command Response, See Message Slot Table Message Slot 9 Floating Point data Message Slot 9 Floating Point data Message Slot 9, Scale Status, See Message Slot Table Message Slot 10, Command Response, See Message Slot Table Message Slot 10 Floating Point data Message Slot 10 Floating Point data Message Slot 10, Scale Status, See Message Slot Table Message Slot 11, Command Response, See Message Slot Table Message Slot 11 Floating Point data Message Slot 11 Floating Point data Message Slot 11, Scale Status, See Message Slot Table Message Slot 12, Command Response, See Message Slot Table Message Slot 12 Floating Point data Message Slot 12 Floating Point data Message Slot 12, Scale Status, See Message Slot Table
4-12
Usage
Message Slot 1 Command Message Slot 1 Command Message Slot 1 Floating Point data Message Slot 1 Floating Point data Message Slot 1 Floating Point data Message Slot 1 Floating Point data Message Slot 2 Command Message Slot 2 Command Message Slot 2 Floating Point data Message Slot 2 Floating Point data Message Slot 2 Floating Point data Message Slot 2 Floating Point data Message Slot 3 Command Message Slot 3 Command Message Slot 3 Floating Point data Message Slot 3 Floating Point data Message Slot 3 Floating Point data Message Slot 3 Floating Point data Message Slot 4 Command Message Slot 4 Command Message Slot 4 Floating Point data Message Slot 4 Floating Point data Message Slot 4 Floating Point data Message Slot 4 Floating Point data Message Slot 5 Command Message Slot 5 Command Message Slot 5 Floating Point data Message Slot 5 Floating Point data Message Slot 5 Floating Point data Message Slot 5 Floating Point data Message Slot 6 Command Message Slot 6 Command Message Slot 6 Floating Point data Message Slot 6 Floating Point data Message Slot 6 Floating Point data Message Slot 6 Floating Point data Message Slot 7 Command Message Slot 7 Command
4-13
Usage
Message Slot 7 Floating Point data Message Slot 7 Floating Point data Message Slot 7 Floating Point data Message Slot 7 Floating Point data Message Slot 8 Command Message Slot 8 Command Message Slot 8 Floating Point data Message Slot 8 Floating Point data Message Slot 8 Floating Point data Message Slot 8 Floating Point data Message Slot 9 Command Message Slot 9 Command Message Slot 9 Floating Point data Message Slot 9 Floating Point data Message Slot 9 Floating Point data Message Slot 9 Floating Point data Message Slot 10 Command Message Slot 10 Command Message Slot 10 Floating Point data Message Slot 10 Floating Point data Message Slot 10 Floating Point data Message Slot 10 Floating Point data Message Slot 11 Command Message Slot 11 Command Message Slot 11 Floating Point data Message Slot 11 Floating Point data Message Slot 11 Floating Point data Message Slot 11 Floating Point data Message Slot 12 Command Message Slot 12 Command Message Slot 12 Floating Point data Message Slot 12 Floating Point data Message Slot 12 Floating Point data Message Slot 12 Floating Point data
In the template data format a message slot is a shared data variable. The number of message slots is limited to 496 bytes (I/O).
4-14
WORD 1 IN Feed
2 2 3 4
Bit number 0 1 2 3 4 5 6 7 8 9 10 11 12
4
Fast Feed
Tolerance OK
Under low tolerance Over high tolerance Comparator 3 Comparator 2 Comparator 1 ENTER key Input 1 Input 2 Input 3 Motion
7 7 7 6 5 5 5
8 9 10
13 14 15
Update in progress
11
2 3 4
5. Bits 5, 6 and 7 provide Comparators 1, 2 and 3 statuses. If the comparator is active, the respective bit is set to 1. 6 7 Bit 8 is set to a 1 when the ENTER key is pressed on the keypad of the terminal. The bit remains on for 30 seconds then resets to 0. Bit 9, bit 10, and Bit 11 mirror the state of the first three discrete inputs on the internal I/O board slot 5 (0.5.1, 0.5.2 and 0.5.3). If the input is ON then the bit is set to a 1.
4-15
10 Bit 14 is set to a 1 when the terminal is in the process of updating its data for the PLC scanner. The PLC should ignore ALL of the data in this case and simply re-scan it. 11 Bit 15 is set to a 1 when the scale is operating properly (NOT over capacity, under capacity, in power-up, in expanded mode, or in setup mode).The PLC program should continuously monitor this bit and the PLC processor rack fault bit (see A-B RIO PLC documentation) to determine the validity of the discrete and/or explicit data transfer. While in the setup mode word 0 data may be present; do not use the data under this condition as the communication connection may stop at any time. 12 When number is negative, word 0 Bit 15 is high and is the least significant bit. Otherwise, when the number is positive, Bit 15 is the most significant bit.
Table 4-7: Discrete Write Integer or Division PLC >> IND780, per Message Slot
Octal Address 0 1 2 3 4 5 6 7 10 11 12 13 14 15 16 17 WORD 0 OUT X X X X X X X X X X X X X X X X
1
Bit number 0 1 2 3 4 5 6 7
8
Load Tare
5 6
8 9 10 11 12 13 14 15
Display mode
Load Target
3 4 5 6 7 8 9
4-16
Floating Point
Operational Overview
The IND780 uses integer commands from the PLC to select the floating point weight input data. The IND780 recognizes a command when it sees a new value in the Message Slot command word. If the command has an associated floating point value (for example: loading a target value), it must be loaded into the floating point value words before the command is issued. Once the IND780 recognizes a command, it acknowledges the command by setting a new value in the command acknowledge bits of the scales command response word. The IND780 also tells the PLC what floating point value is being sent (via the floating point input indicator bits of the command response word). The PLC should wait until it receives the command acknowledgment from the IND780 before sending another command. The IND780 can report two types of values to the PLC: real-time and static. When the PLC requests a real-time value, the IND780 acknowledges the command from the PLC once but sends and updates the value at every interface update cycle. If the PLC requests a static value, the IND780 acknowledges the command from the PLC once and updates the value once. The IND780 will continue to send this value until it receives a new command from the PLC. Gross weight and net weight are examples of real-time data. Tare weight, target, feed, and tolerance values are examples of static data. The IND780 can send a rotation of up to nine different real-time values. The PLC sends commands to the IND780 to add a value to the rotation. Once the rotation is established, the PLC must instruct the IND780 to begin its rotation automatically, or the PLC may control the pace of rotation by instructing the IND780 to advance to the next value. If the IND780 is asked to automatically alternate its output data, it will switch to the next value in its rotation at the next interface update cycle. (The interface update cycle has an update rate of up to 17 Hz or 60 milliseconds.) The PLC may control the rotation by sending alternate report next field commands (1 and 2). When the PLC changes to the next command, the IND780 switches to the next value in the rotation order. The IND780 stores the rotation in its shared data so the rotation does not have to be re-initialized after each power cycle. When the PLC does not set up an input rotation, the default input rotation consists of gross weight only. See the floating-point command examples in Table 4-12 through Table 4-15 for additional information. The method of handling string and floating point data varies between Allen-Bradley PLC generations. The IND780 provides floating point data in the order entered in Data Format setup. 4-17
IND780 PLC Interface Manual Table 4-8 through Table 4-11 provide detailed information on the floating-point data format. Read data refers to the PLCs input data and write data refers to the PLCs output data.
Table 4-8: Discrete Read Floating Point IND780 >> PLC Input, per Message Slot
Octal Address 0 1 2 3 4 5 6 7 10 11 12 13 14 15 16 17 1 FP Input Ind 1 FP Input Ind 2 FP Input Ind 3 FP Input Ind 4 FP Input Ind 5 Data integrity1 Cmnd Ack 1 Cmnd Ack 2
7 7 7 7 7
WORD 1 FP value X X X X X X X X X X X X X X X X
WORD 2 FP value X X X X X X X X X X X X X X X X
Bit number 0 1 2 3 4 5 6 7 8 9 10 11 12 13
11 4
Fast Feed
Tolerance OK
RESERVED
Under Negative Tolerance Over Positive Tolerance Selected scale Custom Bit Custom Bit ENTER key Input 1 Input 2 Input 3 Motion
9 9 9 6 6 5
10 12
11
13 13
Data integrity 2
14
14 15
2 3 4 6
5 Bit 5 will be set to a 1 when the associated scale is selected on the IND780 console panel.
10 Bit 12 is set to a 1 when the scale is in motion (unstable). 11 The Data Integrity bit in WORD 0 - bit 13 is used in conjunction with the bit in WORD 3 - bit 14 to insure that the floating point data is valid. For the data to be valid both bits must have the same polarity. These bits will change to the opposite state every interface update cycle. If they do not have the same value the data is invalid and the PLC should ignore ALL of the data in this case and re-scan it.
4-18
Dec
0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 1928 29 30 31
* **
Data
Gross Weight* Net Weight* Tare Weight* Fine Gross Weight* Fine Net Weight* Fine Tare Weight* Rate ALxx01 SDV, instance by scale ** ALxx02 SDV, instance by scale ** AJxx01 SDV, instance by scale ** AJxx02 SDV, instance by scale ** Low-pass filter frequency Notch filter frequency Target value, instance by scale Target positive tolerance value, instance by scale Target Fine Feed value, instance by scale Target negative tolerance value, instance by scale Target spill value, instance by scale Primary units, low increment size Not used Last IND780 error code No data response command successful No data response command failed
These are real-time fields that the PLC may request either through an input rotation or a report command. All other fields may only be requested through a report command. SDV means Shared Data Variable.
4-19
WORD 0
WORD 1
Bit Number
0 1 2 3 4 5 6 7 8 9 10 11 12 13 14
Not all commands will require a value in the floating point load value words.
4-20
SDName PD0119
Disable LCD display 7 Enable LCD display 7 Set normal display mode 7,9 Display message 1 7,9 Display message 2 7,9 Display message 3 7,9 Display message 4 7,9 Display Message 5 7,9 Start ID1 sequence 7,9 Display SDV PD0118 7,9 Disable weight display 7 Enable weight display 7 Set discrete output 0.5.1 ON 7 Set discrete output 0.5.2 ON 7 Set discrete output 0.5.3 ON 7 Set discrete output 0.5.4 ON 7 Set discrete output 0.5.1 OFF 7 Set discrete output 0.5.2 OFF 7 Set discrete output 0.5.3 OFF 7 Set discrete output 0.5.4 OFF 7 Master control relay OFF7, 12 Master control relay ON7, 12 Set target value 4,10, 13 Set target fine feed value 4,10 Set - tolerance value 4,10 Set target value and apply4, 10, 14
SPxx05
114 72 Start target logic 7,10 115 73 Abort target logic 7,10 116 74 Target use gross weight 7,10 117 75 Target use net weight 7,10 ALxx016 118 76 Target use rate 7,10 ALxx026 119 120 121 122 123 124 131 160 161 77 78 79 7a 7b 7c 83 a0 a1 Target, absolute weight 1 speed 7,10 Target, absolute weight 2 speed 7,10 Enable target latching 7,10 Disable target latching 7,10 Reset target latch 7 Set target spill value4, 10 Set + tolerance value 4,10 Apply scale setup 7 Write Calibration to EEProm 7
SPxx04 SPxx04 SPxx04 SPxx08 SPxx08 SPxx06 SPxx06 SPxx07 SPxx11 QC0149
CPxx017 162 a2 Disable Tare on IND780 console 7,11 CPxx027 163 a3 Enable Tare on IND780 console 7 Disable push button Tare on IND780 CPxx037 164 a4 console 7,11 Enable push button Tare on IND780 CPxx047 165 A5 console 7 Disable numeric Tare on IND780 console CPxx057 166 a6 7,11 167 a7 Enable numeric Tare on IND780 console 7 168 a8 Select scale 3 7 169 a9 Select scale 4 7
4-21
4. 5. 6. 7. 8. 9.
10. Target, Fine Feed, Tolerances, Restart, Abort and other Target variables are relative to each scale. Note: Restart of an active Target will cause the associated outputs to cycle off then back on. 11. Does not disable the PLC tare functions. 12. Setting the master control relay OFF turns off all outputs and stops target logic. The target logic must be restarted after the master control relay is turned ON. 13. Target logic must be restarted to apply the new target value. 14. New target value is applied when command is sent.
4-22
4-23
1 (PLC sends command to IND780 terminal to report net weight) 2 (IND780 terminal sees new command)
none required
As long as the PLC leaves the 11 (dec) in the command word, the IND780 terminal will update the net value every interface update cycle.
Table 4-13: Data Requirement: Load Target Value = 21.75 for Scale 1
Step # Scale command (from PLC) Scale Floating Point Value Command response from terminal Floating Point Value
1 (PLC loads floating point value first) 2 (PLC sends command to set target 1 cutoff value) 3 (IND780 terminal sees new command , loads the value into the target and ends a return message to indicate the new target value) 4 (PLC instructs IND780 terminal to start using new target value) 5 (IND780 terminal sees new command) 114 (dec) loaded into command word O 110 (dec) loaded into command word O
0.0
The PLC should always wait to receive a command acknowledgment before sending the next command to the IND780 terminal. After the PLC finishes loading its target value, it can resume monitoring the weight information required by sending a command to report some type of weight or set up a rotation of reported data.
4-24
1 (PLC clears out any previous rotation with reset) 2 (IND780 terminal sees new command) 3 (PLC adds gross weight to rotation) 4 (IND780 terminal sees new command) 5 (PLC adds rate to the rotation) 6 (IND780 terminal sees new command)
3 (dec) loaded into command word O Command ack.= 1 F.P. ind = 30 40 (dec) loaded into command word O 0.0
(null value)
Command ack. = 2 F.P. ind = 30 46 (dec) loaded into command word O Command ack. = 3 F.P. ind = 30
0.0
0.0
At this point, the rotation has been set up. Now the PLC needs to command the IND780 terminal to begin the rotation. 7 (PLC sends the command to begin the rotation at interface update cycle) 8 (IND780 terminal sends gross weight at interface update cycle ~ 60 msec) 9 (PLC leaves 0 in its command word and the IND780 terminal sends the rate value at the next interface update cycle) 10 (PLC leaves 0 in its command word and IND780 terminal sends the gross value at next interface update cycle) 11 (PLC leaves 0 in command word and IND780 terminal sends the rate value at the next interface update cycle) 0 (dec) loaded into command word O RESERVED for Future Use Command ack. = 0 Floating point value = rate F.P. ind = 6 0 (dec) loaded into command word O Command ack. = 0 Floating point value = F.P. ind = 0 gross wt. 0 (dec) loaded into command word O RESERVED for Future Use Command ack. = 0 Floating point value = rate F.P. ind = 6 0 (dec) loaded into command word O Command ack. = 0 Floating point value = F.P. ind = 0 gross wt.
This rotation continues until the PLC sends a different command. At approximately every 60 msec the IND780 terminal updates its data with the next field in its rotation. The PLC must check the floating point indication bits to determine which data is in the floating point value.
4-25
1 (PLC clears out any previous rotation with reset) 2 (IND780 terminal sees new command) 3 (PLC adds net weight to rotation) 4 (IND780 terminal sees new command) 5 (PLC adds rate to the rotation) 6 (IND780 terminal sees new command)
3 (dec) loaded into command word O Command ack.= 1 F.P. ind = 30 41 (dec) loaded into command word O (null value) Command ack. = 2 F.P. ind = 30 46 (dec) loaded into command word O RESERVED for Future Use Command ack. = 3 F.P. ind = 30 0.0 0.0
0.0
At this point, the rotation has been set up. Now the PLC needs to send commands to the IND780 terminal to begin the rotation and advance to the next value when required. 7 (PLC sends the command to report the first field in the rotation.) 8 (IND780 terminal acknowledges the command and sends net weight at every interface update cycle until the PLC gives the command to report the next rotation field.) 9 (PLC sends the command to report the next field.) Note: if the PLC leaves the 1 (dec) in the command, the IND780 terminal does NOT see this as another command to report the next rotation field. 10 (IND780 terminal acknowledges the command and sends rate at every interface update cycle until the PLC gives the command to report the next rotation field.) 1 (dec) loaded into command word O
4-26
11 (PLC sends the command to report the next field in the rotation.) 12 (IND780 terminal acknowledges the command and sends net weight at every interface update cycle until the PLC gives the command to report the next rotation field.) 13 (PLC sends the command to report the next field.) 14 (IND780 terminal acknowledges the command and sends rate at every interface update cycle until the PLC gives the command to report the next rotation field.)
At approximately every 60 msec the IND780 terminal updates its data with new data, but it does not advance to the next field in the rotation until the PLC sends it the command to report the next field. The PLC should check the floating point indication bits to determine which data is in the floating point value
Software Setup
When the IND780 terminal detects the presence of a EtherNet / IP Kit option board, the EtherNet / IP parameters are enabled in a Setup program block at Communication > PLC Interface > EtherNet / IP. Figure 4-6 shows the EtherNet / IP setup block, and Figure 4-7 graphs the Communication > PLC Interface > Data Format setup block. Default values are marked with an asterisk.
4-28
2. Select the Format (Integer, Divisions, Floating Point, Template or Application): [default Integer] Changing the Format will delete any existing Message Slots. Integer reports scale weight as a signed 16 bit integer ( 32767).
4-29
IND780 PLC Interface Manual Divisions reports scale weight in display divisions ( 32767). The PLC multiplies the reported divisions by the increment size to calculate the weight in display units. Floating Point displays weight in floating point data format Template Allows the end-user to customize PLC communications input and output data by allowing them to set up input and output templates with shared data variables. This format is fixed and cannot be changed on the fly by the PLC program. The template editor also calculates the input and output sizes upon exit of the editor. In order to populate the data fields, consult the Shared Data Reference Manual (document number 64059110) provided on the CD-ROM supplied with your terminal. Application Allows a TaskExpert program to interact with the PLC input and output data. The TaskExpert program is responsible for setting up all input and output data from the IND780 and to control the data length of the input and output assemblies. For application commands used in TaskExpert, refer to the TaskExpert Reference Manual (document number 64060431). 3. Select Byte Order: [default Word Swap] Word Swap Takes the IEE 754 single-precision floating point format and swaps the two words in the 32-bit double word. This format is compatible with RSLogix 5000 processors. Byte Swap Makes the floating point format compatible with S7 PROFIBUS. 4. Set the Time Interval in milliseconds. (Only when the Format is Template) 5. Use the Configure drop-down list to select the direction of data flow IND780 >> PLC or PLC >> IND780. (Only when the Format is Template) 6. The bottom of this screen (Figure 4-9) displays the number of bytes that will be sent by the IND780 and the number of bytes expected from the PLC.
4-30
IND780 PLC Interface Manual 7. Depending on which format is selected, press the VIEW TABLE softkey to set up the number of Message Slots (maximum number is 12; default is 0), or to configure the Template for communications between the IND780 and the PLC. Figure 4-10 shows the Message Slots View, which is viewed whenever the Format is not Template.
Figure 4-11 shows the Template View, accessed when Format is set to Template. Each message slot will be a Shared Data Variable, entered by the user. These entered message slots are associated only to the Shared Data Variable entered and not to a scale.
Press the EXIT softkey Press the EDIT softkey Press the NEW softkey Press the DELETE softkey Press the CLEAR softkey
to exit the view screen. to edit an existing slot. to enter a new slot. to delete an existing slot. to delete all existing slots.
4-31
IND780 PLC Interface Manual Figure 4-12 shows the screen that opens when NEW is selected from the Message Slots View screen (Figure 4-10).
Scale Enter the scale number to be associated with the new Message Slot. Terminal Default is Local; remote terminals 1 through 20 may be selected if remote PLC interface sharing is used. Figure 4-13 shows a series of Template New screens, as accessed from the Template View screen Figure 4-11.
Figure 4-13: New Template Screens, PLC to IND780 and IND780 to PLC
Slot Automatically assigned. SDName An alphabetic entry field used to define the Shared Data variable associated with the slot.
4-32
IND780 PLC Interface Manual Length (Bytes) and Data Type Automatically displayed once the SDName has been entered. Terminal Default is Local; remote terminals 1 through 20 may be selected if remote PLC interface sharing is used. For a complete listing of Shared Data Fields, refer to the IND780 Shared Data Reference. Refer to Table 4-6 (Discrete Read) and Table 4-7 (Discrete Write) in this chapter for additional information on mapping of discrete read data to the PLC.
Troubleshooting
If the IND780 does not communicate with PLC, do the following: Check wiring and network termination. Confirm that the IND780 settings for data type and IP Address assignment match those in the PLC and that each IND780 has a unique address. Replace the EtherNet / IP interface kit if the problem persists. If the communication kit was changed from another type, like PROFIBUS, ControlNet or Remote I/O, a master reset of the IND780 must be performed.
Status LEDs
The EtherNet/ IP interface card has four status LEDs indicators to indicate communication and fault status of the card. Figure 4-2 indicates the location of these LEDs, and Figure 4-14 shows the array of the LEDs on the card. Table 4-16 explains the meaning if the indicators.
Link Activity Activity
1 4
2 3
Figure 4-14: Ethernet / IP Status Indicator LEDs Table 4-16: EtherNet/ IP LEDs Status Indications
LED # 1 - Link Activity State Off Green Off Green 2 - Module Status Green, flashing Red Red, flashing Alternating Red/Green 3 - Network Status Off Green Status No link (or no power) Connected to an Ethernet network No power Normal operation Stand by, not initialized Major fault Minor fault Self test No IP address (or no power) EtherNet/ IP connection(s) established
4-33
Qty. 1 1 1 3
Programming Examples
The following Figures show sample screen images of ladder logic programming examples for RSLogix 5000 software (version 13). Note: The Utilities folder of the documentation CD (part number 64057241) contains complete versions of the examples. These screen images are provided for illustrative purposes only.
The following RSLogix 5000 screens for Integer, Division and Floating Point data formats only show an example of a particular Input and Output size configuration. The Connection Parameters I/O sizes must be appropriately configured with reference to the number of slots assigned in the IND780 PLC Data Format Message Slots settings. Table 4-18 and Table 4-19 show the relationship between the IND780 message slots and the RSLogix 5000 I/O sizing for Integer, Division and Floating Point data formats.
4-34
Output
2 4 6 8 10 12 14 16 18 20 22 24
Table 4-19: Message Slot and PLC I/O Sizes (Floating Point) IND780 Floating Point Data Message Slots
1 2 3 4 5 6 7 8 9 10 11 12
Output
4 7 10 13 16 19 22 25 28 31 34 37
4-35
4-36
4-37
4-38
4-39
Chapter 5
Overview DeviceNet characteristics Data definition Hardware setup Software setup Troubleshooting DeviceNet Option Kit DeviceNet commissioning and conifiguration examples
Preface
Users should note that the DeviceNet option is used in both the Mettler Toledo IND560 and IND780 terminals. There are minor differences in the Floating Point polled data between the two terminals. The terminals share the same EDS file and Icon file for use in a DeviceNet network configuration tool.
Overview
DeviceNet is an RS-485-based network utilizing CAN chip technology. This network was created for bit and byte-level devices. The network can be configured to run up to 500Kbits per second depending on cabling and distances. Messages are limited to 8 un-fragmented bytes. Any larger message must be broken up and sent in multiples. The IND780 implementation of DeviceNet does not support fragmented messages all messages are 8 bytes or shorter. The network is capable of 64 nodes including the master, commonly called the scanner.
DeviceNet Characteristics
DeviceNet-specific (twisted pair) cable Access to intelligence present in low-level devices Master/Slave and Peer-toPeer capabilities Trunkline-dropline configuration Support for up to 64 nodes Node removal without severing the network Simultaneous support for both network-powered (sensors) and self-powered (actuators) devices Use of sealed or open style connectors Protection from wiring errors Selectable baud rates of 125k baud, 250k baud, and 500k baud. Maximum trunk distance 500 meters and drop length of 156 meters at 125k baud Adjustable power configuration to meet individual application needs High current capability (up to 8 amps per supply) Operation with off-the-shelf power supplies 5-1
IND780 PLC Interface Manual Power taps that allow the connection of several power supplies from multiple vendors that comply with DeviceNet standards Built-in overload protection Power available along the bus: both signal and power lines contained in the trunkline Provisions for the typical request/response-oriented network communications Provisions for the efficient movement of I/O data Fragmentation (anything in excess of 8 bytes) for moving larger bodies of information Note: Mettler Toledo terminals do not support fragmented messaging. Duplicate MAC ID detection
Consult http://www.odva.org/ to obtain additional information on DeviceNet. Figure 5-1 shows a view of the DeviceNet Option Board, with its connector at lower left. Figure 5-2 indicates the boards connector and status lights.
CONNNECTOR
Communications
The IND780 utilizes polled messages. This type of message may be referred to as scheduled or cyclic messages. It does not support explicit or unscheduled messaging.
5-2
Node Address
The IND780 can be assigned any valid DeviceNet node address. Typically 0 is reserved for scanner cards and address 63 is reserved for new devices out of the box. The IND780s default MAC ID is 63.
Data Formats
While being polled, the IND780 supports floating point, integer, and divisions data formats. The Application data format is also available to allow a custom TaskExpert program to control the PLC input and output data. Shared Data cannot be accessed directly using DeviceNet.
Network Topology
The following example (Figure 5-3) shows a typical DeviceNet network topology with IND780 terminals connected directly to a Logix controller.
5-3
Data Definition
Data Integrity
The IND780 Terminals have specific bits to allow the PLC to confirm that data was received without interruption and the IND780 Terminal is not in an error condition. It is important to monitor these bits. Any PLC code should use them to confirm the integrity of the data received for the IND780 Terminal. Refer to the data charts for specific information regarding the Data OK, Update in Progress and Data Integrity bits and their usage.
Discrete Data
Four formats of discrete data are available with the DeviceNet Kit option: integer, division, floating point and application. Only one type of data format may be selected and used by IND780 Terminals sharing the same DeviceNet logical node address. The integer and division formats allow bi-directional communication of discrete bitencoded information or 16 bit binary word numerical values. The IND780 Terminal provides four bytes per message slot. Two slots are available in integer and division mode while only one eight byte slot is available via floating point mode. The floating-point format allows bi-directional communication of discrete bit encoded information or numeric data encoded in IEEE 754, single precision floating point format. The floating-point format requires more space per IND780 Terminal because floating point data uses two 16-bit words of data to represent just the numeric data alone. Selection of the appropriate format depends on issues such as the range or capacity of the scale used in the application. The integer format can represent a numerical value up to 32,767. The division format can represent a value up to 32,767 scale divisions or increments. The floating-point format can represent a value encoded in IEEE 754, single precision floating point format. Changing the Data Format to be used by the IND780 will clear all Message Slots. Data format is set up in the Communication > PLC Interface > Data Format screen.
Examples
250 x .01 scale IND780 Displays: Int Div FLT 0 0 0 0 2.00 Format sent: 200 200 2.00 5167 5167 51.67 25000 25000 250.00 51.67 250.00
5-4
The integer format could not be used because it would send a negative value once the weight exceeded 32,767.
150 x .001 scale IND780 Displays: Int Div FLT 0 0 0 0 2.100 Format sent: 2100 2100 2.100 (13929) (13929) 51.607 18928 18928 150.000 51.607 150.000
The integer and division formats could not be used because they would send a negative value once the weight exceeded 32.767.
Byte Order
Word Swap takes the IEE 754 single-precision floating point format and swaps the two words in the 32-bit double word. This format is compatible with RSLogix 5000 processors. Byte Swap makes the floating point format compatible with S7 PROFIBUS.
Message Slots
There may be up to 2 message slots for discrete data transfer, in Integer and Divisions Data Formats and maximum 1 message slot in Floating Point Data Format. Each message slot is assigned to a local scale and scales may be repeated in additional message slots. The integer and division formats provide (two 16-bit words of input and two 16-bit words of output data) per Message Slot. Each Message Slots first input word provides scale weight data and the input weight data may be selected by the PLC using the Message Slots second output word bit 0, bit 1 and bit 2. The following two Tables provide input and output usage information.
Table 5-3: DeviceNet PLC Input Data and Data Usage (Integer and Division) PLC Input Bytes
0 1 2 3 4 2 1
Usage
Message Slot 1 Weight Data Message Slot 1 Weight Data Message Slot 1 Scale Status Message Slot 1 Scale Status Message Slot 2 Weight Data
5-5
Usage
Message Slot 2 Weight Data Message Slot 2 Scale Status Message Slot 2 Scale Status
Table 5-4: DeviceNet PLC Output Words and Word Usage (Integer and Division) PLC Output Bytes
0 1 2 3 4 5 6 7 3 2 1
Usage
Message Slot 1 Weight Data Message Slot 1 Weight Data Message Slot 1 Scale Command Message Slot 1 Scale Command Message Slot 2 Weight Data Message Slot 2 Weight Data Message Slot 2 Scale Command Message Slot 2 Scale Command
The floating point format provides four 16-bit words of input data and three 16-bit words of output data per Message Slot. See Table 5-5 and Table 5-6 for details.
Table 5-5: DeviceNet PLC Floating Point Input Words PLC Output Words
0 1 2 3
Bits 0 7
Message Slot 1, Reserved Message Slot 1 Floating Point data Message Slot 1 Floating Point data Message Slot 1, Scale Status, See Message Slot Table
Bits 8 15
Message Slot 1, Command Response, See Message Slot Table Message Slot 1 Floating Point data Message Slot 1 Floating Point data Message Slot 1, Scale Status, See Message Slot Table
Table 5-6: DeviceNet PLC Floating Point Output Words PLC Output Bytes
0 1 2 3 4 5 6 7 3 2 1
Usage
Message Slot 1 Command Message Slot 1 Command Message Slot 1 Floating Point data Message Slot 1 Floating Point data Message Slot 1 Floating Point data Message Slot 1 Floating Point data
5-6
WORD 1 IN Feed
2 2 3 4
Bit number 0 1 2 3 4 5 6 7 8 9 10 11 12
4
Fast Feed
Tolerance OK
Under low tolerance Over high tolerance Comparator 3 Comparator 2 Comparator 1 ENTER key Input 1 Input 2 Input 3 Motion
7 7 7 6 5 5 5
8 9 10
13 14 15
Update in progress
11
2 3 4
5. Bits 5, 6 and 7 provide Comparators 1, 2 and 3 statuses. If the comparator is active, the respective bit is set to 1. 6 Bit 8 is set to a 1 when the ENTER key is pressed on the keypad of the terminal. The bit remains on for 30 seconds then resets to 0.
5-7
10 Bit 14 is set to a 1 when the terminal is in the process of updating its data for the PLC scanner. The PLC should ignore ALL of the data in this case and simply re-scan it. 11 Bit 15 is set to a 1 when the scale is operating properly (NOT over capacity, under capacity, in power-up, in expanded mode, or in setup mode).The PLC program should continuously monitor this bit and the PLC processor rack fault bit (see A-B RIO PLC documentation) to determine the validity of the discrete and/or explicit data transfer. While in the setup mode word 0 data may be present; do not use the data under this condition as the communication connection may stop at any time. 12 When number is negative, word 0 Bit 15 is high and is the least significant bit. Otherwise, when the number is positive, Bit 15 is the most significant bit.
Table 5-8: Discrete Write Integer or Division PLC >> IND780, per Message Slot
Octal Address 0 1 2 3 4 5 6 7 10 11 12 13 14 15 16 17 WORD 0 OUT X X X X X X X X X X X X X X X X
1
Bit number 0 1 2 3 4 5 6 7
8
Load Tare
5 6
Abort/Start Target Display mode Display mode Display mode Output 1 Output 2 Output 3
10 10 10 11 9 9 9
8 9 10 11 12 13 14 15
Load Target
3 4 5 6 7 8
5-8
display mode, 1 = display message 1 (aw0101), 2 = display message 2 (aw0102), 3 = display message 3 (aw0103), 4 = display message 4 (aw0104), 5 = display message 5 (aw0105), 6 = Start ID1 sequence, 7 = display message that is written into pd0118. Note: Until these bits are used pd0119 will be set at 0. Change of state of any of these bits resets PLC input word, Bit 8, Enter Key.
10 Bit 12, bit 13, and bit 14 can be used to control the state of the first three discrete outputs on the terminals internal I/O board in slot 5. These are addressed as 0.5.1, 0.5.2, and 0.5.3. Setting the bit to a 1 state causes the output to be turned ON. This action will occur regardless of the discrete output assignment within the IND780. 11 When bit 15 is changed from 0 to 1 the value in WORD 0 is loaded into the target register in the terminal and loaded into the target logic.
Floating Point
Operational Overview
The IND780 terminal uses integer commands from the PLC to select the floating point weight output data. The terminal recognizes a command when it sees a new value in the scales command word. If the command has an associated floating point value (for example: loading a target value), it must be loaded into the floating point value words before the command is issued. Once the terminal recognizes a command, it acknowledges the command by setting a new value in the command acknowledge bits of the scales command response word. It also tells the PLC what floating point value is being sent (via the floating point input indicator bits of the command response word). The PLC waits until it receives the command acknowledgment from the terminal before sending another command. The terminal has two types of values that it can report to the PLC: real-time and static. When the PLC requests a real-time value, the terminal acknowledges the command from the PLC once but sends and updates the value at every interface update cycle. If the PLC requests a static value, the terminal acknowledges the command from the PLC once and updates the value once. The terminal will continue to send this value until it receives a new command from the PLC. Gross weight and net weight are examples of real-time data. Tare weight, target, fine feed, and tolerance values are examples of static data. The terminal can send a rotation of up to nine different real-time values for each scale. The PLC sends commands to the terminal to add a value to the rotation. Once the rotation is established, the PLC must instruct the terminal to begin its rotation automatically, or the PLC may control the pace of rotation by instructing the terminal to advance to the next value. If the terminal is asked to automatically alternate its output data, it will switch to the next value in its rotation at the next interface update cycle. (The interface update cycle has an update rate of up to 17 Hz or 60 milliseconds.) The PLC may control the rotation by sending alternate report next field commands (1 and 2). When the PLC changes to the next command, the terminal switches to the next value in the rotation. The terminal stores the rotation in its shared data so the rotation does not have to be re-initialized after each power cycle. When the PLC does not set up an input rotation, the default input rotation consists of gross weight only. See the floating-point rotation command examples in Table 5-13 and Table 5-16 for additional information. The IND780 provides floating point data in the 5-9
IND780 PLC Interface Manual byte order entered in Data Format setup. The byte order follows the convention of the Controllogix platform. Note that this is word swapped compared to PLC5 and SLC500 processors. Table 5-9 through Table 5-12 provide detailed information on the floating-point data format. Read data refers to the PLCs input data and write data refers to the PLCs output data.
Table 5-9: Discrete Read Floating Point (float) IND780 >> PLC (DeviceNet)
Octal Address 0 1 2 3 4 5 6 7 10 11 12 13 14 15 16 17 1 FP Input Ind 1 FP Input Ind 2 FP Input Ind 3 FP Input Ind 4 FP Input Ind 5 Data integrity1 Cmnd Ack 1 Cmnd Ack 2
7 7 7 7 7
WORD 1 FP value X X X X X X X X X X X X X X X X
WORD 2 FP value X X X X X X X X X X X X X X X X
Bit number 0 1 2 3 4 5 6 7 8 9 10 11 12 13
11 4
Fast Feed
Tolerance OK
RESERVED
Under Negative Tolerance Over Positive Tolerance Selected scale Custom Bit Custom Bit ENTER key Input 1 Input 2 Input 3 Motion
9 9 9 6 6 5
10 12
11
13 13
Data integrity 2
14
14 15
2 3 4 6
5 Bit 5 will be set to a 1 when the associated scale is selected on the IND780 console panel.
5-10
Dec
0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 1928 29 30 31
* **
Data
Gross Weight* Net Weight* Tare Weight* Fine Gross Weight* Fine Net Weight* Fine Tare Weight* Rate ALxx01 SDV, instance by scale ** ALxx02 SDV, instance by scale ** AJxx01 SDV, instance by scale ** AJxx02 SDV, instance by scale ** Low-pass filter frequency Notch filter frequency Target value, instance by scale Target positive tolerance value, instance by scale Target Fine Feed value, instance by scale Target negative tolerance value, instance by scale Target spill value, instance by scale Primary units, low increment size Not used Last IND780 error code No data response command successful No data response command failed
These are real-time fields that the PLC may request either through an input rotation or a report command. All other fields may only be requested through a report command. SDV means Shared Data Variable.
5-11
WORD 1
Bit number 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
Not all commands will require a value in the floating point load value words.
5-12
SDName
Dec 76 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 100 101 102 103 104 105 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 131 160 161 162 163 164 165 166 167 168 169
Hex 4c 4e 4f 50 51 52 53 54 55 56 57 58 59 5a 5b 5c 5d 64 65 66 67 68 69 6e 6f 70 71 72 73 74 75 76 77 78 79 7a 7b 7c 83 a0 a1 a2 a3 a4 A5 a6 a7 a8 a9
SDName PD0119
ALxx016 ALxx026
CPxx017 CPxx02
7
Disable LCD display Enable LCD display 7 Set normal display mode 7,9 Display message 1 7,9 Display message 2 7,9 Display message 3 7,9 Display message 4 7,9 Display Message 5 7,9 Start ID1 sequence 7,9 Display SDV PD0118 7,9 Disable weight display 7 Enable weight display 7 Set discrete output 0.5.1 ON 7 Set discrete output 0.5.2 ON 7 Set discrete output 0.5.3 ON 7 Set discrete output 0.5.4 ON 7 Set discrete output 0.5.1 OFF 7 Set discrete output 0.5.2 OFF 7 Set discrete output 0.5.3 OFF 7 Set discrete output 0.5.4 OFF 7 Master control relay OFF7, 12 Master control relay ON7, 12 Set target value 4,10, 13 Set target fine feed value 4,10 Set - tolerance value 4,10 Set target value and apply4, 10, 14 Start target logic 7,10 Abort target logic 7,10 Target use gross weight 7,10 Target use net weight 7,10 Target use rate 7,10 Target, absolute weight 1 speed 7,10 Target, absolute weight 2 speed 7,10 Enable target latching 7,10 Disable target latching 7,10 Reset target latch 7 Set target spill value4, 10 Set + tolerance value 4,10 Apply scale setup 7 Write Calibration to EEProm 7 Disable Tare on IND780 console
7,11
SPxx05
SPxx04 SPxx04 SPxx04 SPxx08 SPxx08 SPxx06 SPxx06 SPxx07 SPxx11 QC0149
Custom print 37 Custom print 47 Custom print 57 Set low-pass filter corner frequency 4 Set notch filter frequency 4 Reset ENTER key 7
Enable Tare on IND780 console 7 Disable push button Tare on IND780 console 7,11 Enable push button Tare on IND780 console 7 Disable numeric Tare on IND780 console 7,11 Enable numeric Tare on IND780 console 7 Select scale 3 7 Select scale 4 7
5-13
A command that requests real-time fields from the terminal. The terminal updates this input data to the PLC at the cycle update rate of the PLC interface. A command used by the PLC to select the next field from the input rotation. The PLC must alternate between these two commands to tell the terminal when to switch to the next field of the input rotation. A command requiring the terminal to report a specific value in the PLC input message. As long as one of these commands is sent in the Scale Command, the terminal will respond with the requested data and not data from an input rotation. The data reported in the PLC input message is the data when the command was issued. A command that requires a floating point value output from the PLC to the terminal. The terminal reflects back this value in the floating point data of the input message to the PLC. A command used between the PLC and a Task Expert application. This data has a four-byte length and is defined by the application. Instance is by scale. PLC input Message Slot floating point value will be 0 as long as command is present. IND780 discrete output will be turned on or off regardless of assignment within the IND780. A command is written to pd0119. Note that pd0119==0 for normal display, 1 = display message 1
(aw0101), 2 = display message 2 (aw0102), 3 = display message 3 (aw0103), 4 = display message 4 (aw0104), 5 = display message 5 (aw0105), 6 = Start ID1 sequence, 7 = display message that is written into pd0118, 8 = Start ID2 sequence. Note: Until these commands are used pd0119 will be set at 0.
3.
4. 5. 6. 7. 8. 9.
10. Target, Fine Feed, Tolerances, Restart, Abort and other Target variables are relative to each
scale. Note: Restart of an active Target will cause the associated outputs to cycle off then back on.
11. Does not disable the PLC tare functions. 12. Setting the master control relay OFF turns off all outputs and stops target logic. The target logic
13. Target logic must be restarted to apply the new target value. 14. New target value is applied when command is sent.
IND780 PLC Interface Manual terminal. Allen-Bradley SLC programs always read valid floating-point data from the terminal and do not have to make special checks to guarantee the validity of the floating-point data. The two integrity bits function as follows when communicating with the Allen-Bradley PLC-5 DeviceNet scanner card. One bit is in the beginning word of the data; the second is in the ending byte of the data for a scale slot. The PLC program must verify that both data integrity bits have the same polarity for the data in the scale slot to be valid. There is a possibility that the PLC program will see several consecutive invalid reads when the terminal is freely sending weigh updates to the PLC-5 program detects this condition, it should send a new command to the terminal. The Allen-Bradley SLC PLC programs do not have to make special checks to guarantee the validity of the floating-point data.
As long as the PLC leaves the 11 (dec) in the command word the IND780 terminal will update the net value every interface update cycle.
Table 5-14: Data Requirement: Load Target Value = 21.75 for Scale 1
Step # 1 (PLC loads floating point value first) 2 (PLC sends command to set target 1 cutoff value) 3 (IND780 terminal sees new command , loads the value into the target and ends a return message to indicate the new target value) 110 (dec) loaded into command word O:XX1 Scale command (from PLC) Scale Floating Point Value floating point value = 21.75 Command response from terminal Floating Point Value
5-15
4 114 (dec) loaded (PLC instructs IND780 into command terminal to start using word O:XX1 new target value) 5 (IND780 terminal sees new command) Command ack. = 2 F.P. ind = 30 (null value)
The PLC should always wait to receive a command acknowledgment before sending the next command to the IND780 terminal. After the PLC finishes loading its target value, it can resume monitoring the weight information required by sending a command to report some type of weight or set up a rotation of reported data.
Table 5-15: Data Requirement: Rotation of Gross Weight and Rate Updated on Interface Update Cycle
Step # 1 (PLC clears out any previous rotation with reset) 2 (IND780 terminal sees new command) 3 (PLC adds gross weight to rotation) 4 (IND780 terminal sees new command) 5 (PLC adds rate to the rotation) 6 (IND780 terminal sees new command) 46 (dec) loaded into command word O:XX1 Command ack. = 3 F.P. ind = 30 (null value) 40 (dec) loaded into command word O:XX1 Command ack. = 2 F.P. ind = 30 Scale Command (from PLC) 3 (dec) loaded into command word O:XX1 Command ack.= 1 F.P. ind = 30 Scale Floating Point Value Command Response from Terminal Floating Point Value
At this point, the rotation has been set up. Now the PLC needs to command the IND780 terminal to begin the rotation. 7 (PLC sends the command to begin the rotation at interface update cycle) 8 (IND780 terminal sends gross weight at interface update cycle ~ 60 msec) 0 (dec) loaded into command word O:XX1
5-16
This rotation continues until the PLC sends a different command. At approximately every 60 msec the IND780 terminal updates its data with the next field in its rotation. The PLC must check the floating point indication bits to determine which data is in the floating point value.
Table 5-16: Data Requirement: Rotation of Net Weight and Rate Updated on PLC Command
Step # 1 (PLC clears out any previous rotation with reset) 2 (IND780 terminal sees new command) 3 (PLC adds net weight to rotation) 4 (IND780 terminal sees new command) 5 (PLC adds rate to the rotation) 6 (IND780 terminal sees new command) 46 (dec) loaded into command word O:XX1 Command ack. = 3 F.P. ind = 30 (null value) 41 (dec) loaded into command word O:XX1 Command ack. = 2 F.P. ind = 30 Scale command (from PLC) 3 (dec) loaded into command word O:XX1 Command ack.= 1 F.P. ind = 30 Scale Floating Point Value Command response from terminal Floating Point Value
At this point, the rotation has been set up. Now the PLC needs send commands to the IND780 terminal to begin the rotation and advance to the next value when required.
5-17
At approximately every 60 msec the IND780 terminal updates its data with new data, but it does not advance to the next field in the rotation until the PLC sends it the command to report the next field. The PLC should check the floating point indication bits to determine which data is in the floating point value
5-18
Hardware Setup
Wiring
The IND780 wiring is shown below. Consult http://www.odva.org/ for additional DeviceNet wiring information.
1 2 3 4 5
Figure 5-4: DeviceNet Connector Pin Numbering
Pin Number
1 2 3 4 5
Description
V CAN L Drain CAN H V+
Wire Color
Black Green White Red
5-19
Software Setup
The IND780 terminal automatically detects the presence of a DeviceNet Kit option board if one is installed. When the option is detected, the IND780 terminal enables the DeviceNet parameters in a Setup program block under Communication > PLC Interface > DeviceNet. Figure 5-5 graphs the DeviceNet and PLC Data Format program blocks. Default values are indicated with an asterisk (*).
Figure 5-5: The DeviceNet Program Block and Data Format Setup Block
5-20
2. Select the Format (Integer, Divisions, Floating Point or Application): [default Integer] Changing the Format will delete any existing Message Slots. Integer reports scale weight as a signed 16 bit integer ( 32767).
5-21
IND780 PLC Interface Manual Divisions reports scale weight in display divisions ( 32767). The PLC multiplies the reported divisions by the increment size to calculate the weight in display units. Floating Point displays weight in floating point data format Application Allows a TaskExpert program to interact with the PLC input and output data. The TaskExpert program is responsible for setting up all input and output data from the IND780 and to control the data length of the input and output assemblies (8 bytes i/O maximum). For application commands used in TaskExpert, refer to the TaskExpert Reference Manual (document number 64060431). 3. Select Byte Order: [default Word Swap] Word Swap Takes the IEE 754 single-precision floating point format and swaps the two words in the 32-bit double word. This format is compatible with RSLogix 5000 processors. Byte Swap Makes the floating point format compatible with S7 PROFIBUS. 4. The bottom of this screen (Figure 5-7) displays the number of bytes that will be sent by the IND780 and the number of bytes expected from the PLC. 5. Press the VIEW TABLE softkey to set up the number of Message Slots (maximum number is 2 if integer or Division data format is selected; default is 0), for communications between the IND780 and the PLC. Figure 5-8 shows the Message Slots View.
Press the EXIT softkey Press the EDIT softkey Press the NEW softkey Press the DELETE softkey Press the CLEAR softkey
to exit the view screen. to edit an existing slot. to enter a new slot. to delete an existing slot. to delete all existing slots
6. Figure 5-9 shows the screen that opens when NEW is selected from the Message Slots View screen (Figure 5-8). 5-22
Figure 5-9: New Message Slot Screen Scale Enter the scale number to be associated with the new Message
Troubleshooting
All DeviceNet nodes are required to have 2 status LEDs. These LEDs (labeled in Figure 5-2) indicate module and network status. See definitions below.
If the module status LED indicates anything after powering up the unit and attaching the DeviceNet cable, the IND780 Terminal must be powered down and restarted. If the LED continues to show a condition other than solid green, replace the board.
5-23
Description
Installation Instructions PCB Package Cylindrical ferrites M3 x 8 screws
Qty.
1 1 3 3
5-24
5-25
IND780 PLC Interface Manual Click Next to begin the registration process. In the Options screen, make sure the Register an EDS file(s) radio button is selected.
Click Next, then Browse to select a file to register. Browse to the appropriate location and select the file MT_IND-DNET.eds. (The EDS file is located on the CD-ROM.) Click the Open button.
5-26
IND780 PLC Interface Manual Confirm that the correct file is showing in the Named: field, then click Next.
Acknowledge the error applet. This error is generated due to the EDS file being generic for other MT devices. The IO sizes will be configured later in the process.
This window appears after the OK button is clicked. Click the Yes button to continue
5-27
IND780 PLC Interface Manual Note: RSNetWorx for DeviceNet will not be able to find the icon unless it is in the same directory as the EDS file.
The Final Task Summary screen (Figure 5-16) will appear. Click Next.
5-28
5-29
IND780 PLC Interface Manual 2. Select the appropriate network path. In this case (Figure 5-18), 1756DNB/A DeviceNet Scanner is selected.
3. Click OK to continue. A dialog box like the one shown in Figure 5-19 will appear. Note that you may be asked to upload or download, depending on the version of software used.
5-30
IND780 PLC Interface Manual 4. Click OK in the dialog box. A Browsing network box will display with a progress meter indicating that the process is underway.
5. Once the scanner has browsed the entire network, add IND Terminal to the 1756-DNB/As scanlist by right-clicking on the scanner icon in the Graph window (note the tab at the bottom of Figure 5-21), and choosing Properties
Pick the Scanner Module, right click, and select Properties to get the scan list and I/O size setup
5-31
IND780 PLC Interface Manual 6. The scanners properties dialog box will appear, as in Figure 5-22.
5-32
IND780 PLC Interface Manual 7. Click the Scanlist tab in the properties dialog box. The view shown in Figure 5-23 will appear.
5-33
IND780 PLC Interface Manual 8. Highlight the IND Terminal (MT IND-DNET) and left-click to add it to the Scanlist. Once the IND Terminal is added, it will appear in the right pane (Figure 5-24). Click OK.
5-34
IND780 PLC Interface Manual 9. The next step is to edit the I/O parameters of the IND terminal. The I/O size depends on the data type and the number of slots selected in the terminal. Note that slots is a terminal phrase that isnt used in typical DeviceNet terms; it was derived from previous PLC memory mapping. It is used in the terminal setup to remain consistent across the Mettler Toledo terminal line. Integer or Divisions with one slot will be 4 bytes/in 4 bytes out. Integer or Division with 2 slots is 8 bytes in/8 bytes out. Float is always 8 bytes in and out.
10. Download the configuration to the scanner card, in order to commission the network. In the prompt that appears (Figure 5-26), click Yes to continue. Note that some scanner cards may require power down for changes to take effect.
5-35
IND780 PLC Interface Manual 11. Once the IND Terminal has been added to the scanlist, access the Properties dialog to verify its I/O mapping (Figure 5-27 and Figure 5-28) within the scanner card. Note that auto or manual mapping can be used. Consult the masters documentation for advance I/O mapping options. If manual mapping is used. Be sure to start with an unused section of memory for offset.
5-36
IND780 PLC Interface Manual 12. Verify that I/O mapping is complete by choosing the summary tab. Note that the Mapped columns show Yes for the IND Terminal.
5-37
PLC Programming
The IND Terminal is now ready to communicate to the master or DeviceNet scanner. You must configure the PLC or other master with DeviceNet scanner to send and receive data via polled messaging. For this example the RSLogix5000 software is used in conjunction with the Controllogix5000 processor with DeviceNet scanner card. Note that these examples may or may not be applicable depending upon whether you have an existing program or different version of software. Create a new project.
5-38
IND780 PLC Interface Manual Configure scanner card. Refer to Rockwell software documentation for more information.
Create User-Defined tags. These are under data type. In this example the Integer Data Format is being used; create these tags in order to get the data from the scanners memory location into a useable/readable format. Create 2 tags. One is for the weight data (single 16 bit integer) that can be read in decimal format and the other is for the status information (16 bit value) this is read in binary. UserDefined tags will be different for the Floating Point Data Format.
Create an unconditional rung of logic that activates the command register run bit. This bit is required to activate the DeviceNet scanner card. Then create another
5-39
IND780 PLC Interface Manual unconditional rung that activates the copy command. Copy the scanners I/O mapped data into the user defined tags.
At this point you can download the program and run it and, provided the wiring and configuration are correct, you will receive weight and status information back from the IND780 Terminal. Note that examples, and the EDS and IND Terminal icon files, are located on the IND780 documentation CD that comes with every unit.
5-40
Chapter 6
Overview Modbus TCP characteristics Sharing a PLC Interface Data definition Software Setup Troubleshooting
Users should note that the Modbus TCP option uses the Ethernet / IP board (P/N: 64058677) described in chapter 4 of this manual. For use with the Modbus TCP protocol, the Ethernet / IP board must be revision 1.32 or higher.
Overview
Modbus protocol is a messaging structure developed by Modicon in Modbus TCP Option Kit 1979. It is used to establish master-slave/client-server communication between intelligent devices. It is an open standard network protocol, Modbus TCP widely used in the industrial manufacturing environment. Modbus can be Programming Example used in multiple master-slave applications to monitor and program devices; to communicate between intelligent devices and sensors and instruments; and to monitor field devices using PCs and HMIs. Modbus is also an ideal protocol for RTU applications where wireless communication is required. TCP/IP is an Internet transport protocol of that consists of a set of layered protocols, providing a reliable data transport mechanism between machines. The open Modbus TCP/IP specification was developed in 1999. The ModbusTCP protocol takes the Modbus instruction set and wraps TCP/IP around it.
Specifications
Network Type Topology Ethernet-TCP/IP based simple Client/Server network. Star, tree or line structures; all topologies that can be implemented with standard Ethernet technology, including switched networks, are applicable. Standard 10, 100 or 1000 Mbit/s Ethernet technology based on copper cables, fiber optic or wireless standards can be used. The IND780 Modbus TCP option provides an RJ-45 Ethernet port connection 10, 100, 1000 Mbit/s. The IND780 Modbus TCP option only supports 10 or 100 Mbit/s Nearly unlimited.
6-1
6-2
Communications
The IND780 terminal utilizes component parts to ensure complete compatibility with the Modbus TCP network. An IND780 terminal is recognized as a generic Modbus TCP device by the PLC. Each Modbus TCP option connected to the network represents a physical IP Address. The connection is made via a RJ-45 connector on the option card (see Figure 6-2). The wiring between the PLC and the IND780 Modbus TCP connection uses EtherNet twisted pair cable. The cable installation procedures and specification including distance and termination requirements are the same as recommended by Schneider Electric (Modicon) for the Modbus TCP network. The IND780 uses cyclic data for discrete data messaging and the template data format for access to the IND780 Shared Data Variables. It does not support explicit or unscheduled messaging with the Modbus TCP interface.
IP Address
Each Modbus TCP interface option represents one physical IP Address. This address is chosen by the system designer, and then programmed into the IND780 terminal and PLC. There is also a DHCP client feature for the Modbus TCP interface to use a host server to assign addresses. The IND780 terminals address is programmed through Communication > PLC Interface > Modbus TCP in the setup menu. IND780 IP Address entry must be unique for each IND780.
Data Formats
The Modbus TCP Kit option provides discrete data transfer, cyclic messaging. Discrete data is continuously available. The option has its own logical IP address to send and receive information to and from the PLC. There are five data formats: Integer, Divisions, Floating Point, Template and Application.
6-3
Up to 20 terminals can be connected in the cluster. However, the number of message slots available for communications depends on the type of PLC interface. All available PLC message slots can be configured to send or receive data to or from the remote terminals via the cluster. Refer to the appropriate PLC chapters in the IND780 PLC Interface Manual for further details on message slots limitations. To allow bridging of the PLC interface, first a cluster network must be set up among the IND780 terminals. Once the cluster is established, configure the PLC interface on the bridge terminal, set up its data format and assign the required local or remote scales data to the message slots. Figure 6-4 shows an example of two message slots, the first being allocated to scale 1 of the local bridge terminal and a second slot to scale 1 of the remote terminal node 6. For details on configuring the PLC interface in a cluster terminal, refer to the Software Setup section, below. The use of PLC interface sharing is not recommended when real time weight or rate information is required by the PLC for fast process control. The determinism of the terminals PLC interface data update rate is influenced and limited by the characteristics of Ethernet TCP/IP communications used in the cluster network.
6-4
Data Definition
Data Integrity
The IND780 has specific bits to allow the PLC to confirm that data was received without interruption and that the IND780 is not in an error condition. It is important to monitor these bits. Any PLC code should use them to confirm the integrity of the data received by the IND780. Refer to the data charts for specific information regarding the Data OK, Update in Progress and Data Integrity bits and their usage.
Discrete Data
Five formats of discrete data are available with the Modbus TCP Kit option: Integer, divisions, floating point, template and application. Only one type of data format may be selected and used by the IND780. The integer and division formats allow bi-directional communication of discrete bit encoded information or 16 bit binary word (see Table 6-5 and Table 6-6 for explanation) numerical values. The floating-point format allows bi-directional communication of discrete bit encoded information and numeric data encoded in IEEE 754, single precision floating point format. The data format of discrete data will affect the data size required in the configuration of the PLC. The IND780 console PLC message slot setup screen provides data size requirements in bytes, except for the Application data format. Selection of the appropriate format depends on issues such as the range or capacity of the scale used in the application. The integer format can represent a numerical value up to 32,767. The division format can represent a value up to 32,767 scale divisions or increments. The floating-point format can represent a value encoded in IEEE 754, single precision floating point format. Floating point is the only data format that includes decimal point information. Integer and division formats ignore decimal points. Accommodation of decimal point location must take place in the PLC logic, when it is needed with these formats. Changing the Data Format to be used by the IND780 will clear all Message Slots. Data format is set up in the Communication > PLC Interface > Data Format screen.
6-5
Examples
250 x .01 scale IND780 Displays: Int Div FLT 0 0 0 0 2.00 Format sent: 200 200 2.00 5167 5167 51.67 25000 25000 250.00 51.67 250.00
The integer format could not be used because it would send a negative value once the weight exceeded 32,767.
150 x .001 scale IND780 Displays: Int Div FLT 0 0 0 0 2.100 Format sent: 2100 2100 2.100 (13929) (13929) 51.607 18928 18928 150.000 51.607 150.000
The integer and division formats could not be used because they would send a negative value once the weight exceeded 32.767.
Byte Order
Double Word Swap takes the IEE 754 single-precision floating point format and swaps the two words plus byte swaps in the 32-bit double word. This format makes floating point data compatible with Modicon Quantum processors. Byte Swap makes the integer mode compatible with Modicon Quantum processors Word Swap takes the IEE 754 single-precision floating point format and swaps the two words in the 32-bit double word.
6-6
Message Slots
There may be up to 12 message slots for discrete data transfer, in Integer, Divisions and Floating Point Data Formats. Each message slot is assigned to an internal local or remote scale and scales may be repeated in additional message slots. Remote scales must reside in an IND780 Ethernet TCP clustered to the IND780 containing the Modbus TCP interface. The integer and division formats provide (two 16-bit words of input and two 16-bit words of output data) per Message Slot. Each Message Slots first input word provides scale weight data and the input weight data may be selected by the PLC using the Message Slots second output word bit 0, bit 1 and bit 2. The following two Tables provide input and output usage information. 4000, 40001 and 400001 are PLC processor memory-dependent. Refer to PLC documentation for I/O mapping. Any scale can be configured as any slot.
Table 6-1: Modbus TCP PLC Input Data and Data Usage (Integer and Division) PLC Input Bytes
0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 400014 400013 400012 400011 400010 400009 400008 400007 400006 400005 400004 400003 400002
Register Address
400001
Usage
Message Slot 1 Weight Data Message Slot 1 Weight Data Message Slot 1 Scale Status Message Slot 1 Scale Status Message Slot 2 Weight Data Message Slot 2 Weight Data Message Slot 2 Scale Status Message Slot 2 Scale Status Message Slot 3 Weight Data Message Slot 3 Weight Data Message Slot 3 Scale Status Message Slot 3 Scale Status Message Slot 4 Weight Data Message Slot 4 Weight Data Message Slot 4 Scale Status Message Slot 4 Scale Status Message Slot 5 Weight Data Message Slot 5 Weight Data Message Slot 5 Scale Status Message Slot 5 Scale Status Message Slot 6 Weight Data Message Slot 6 Weight Data Message Slot 6 Scale Status Message Slot 6 Scale Status Message Slot 7 Weight Data Message Slot 7 Weight Data Message Slot 7 Scale Status
6-7
Register Address
Usage
Message Slot 7 Scale Status Message Slot 8 Weight Data Message Slot 8 Weight Data Message Slot 8 Scale Status Message Slot 8 Scale Status Message Slot 9 Weight Data Message Slot 9 Weight Data Message Slot 9 Scale Status Message Slot 9 Scale Status Message Slot 10 Weight Data Message Slot 10 Weight Data Message Slot 10 Scale Status Message Slot 10 Scale Status Message Slot 11 Weight Data Message Slot 11 Weight Data Message Slot 11 Scale Status Message Slot 11 Scale Status Message Slot 12 Weight Data Message Slot 12 Weight Data Message Slot 12 Scale Status Message Slot 12 Scale Status
Table 6-2: Modbus TCP PLC Output Words and Word Usage (Integer and Division) PLC Output Bytes
0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 401033 401032 401031 401030 401029 401028 401027 401026
Register Address
401025
Usage
Message Slot 1 Weight Data Message Slot 1 Weight Data Message Slot 1 Scale Command Message Slot 1 Scale Command Message Slot 2 Weight Data Message Slot 2 Weight Data Message Slot 2 Scale Command Message Slot 2 Scale Command Message Slot 3 Weight Data Message Slot 3 Weight Data Message Slot 3 Scale Command Message Slot 3 Scale Command Message Slot 4 Weight Data Message Slot 4 Weight Data Message Slot 4 Scale Command Message Slot 4 Scale Command Message Slot 5 Weight Data Message Slot 5 Weight Data
6-8
Register Address
401034
Usage
Message Slot 5 Scale Command Message Slot 5 Scale Command Message Slot 6 Weight Data Message Slot 6 Weight Data Message Slot 6 Scale Command Message Slot 6 Scale Command Message Slot 7 Weight Data Message Slot 7 Weight Data Message Slot 7 Scale Command Message Slot 7 Scale Command Message Slot 8 Weight Data Message Slot 8 Weight Data Message Slot 8 Scale Command Message Slot 8 Scale Command Message Slot 9 Weight Data Message Slot 9 Weight Data Message Slot 9 Scale Command Message Slot 9 Scale Command Message Slot 10 Weight Data Message Slot 10 Weight Data Message Slot 10 Scale Command Message Slot 10 Scale Command Message Slot 11 Weight Data Message Slot 11 Weight Data Message Slot 11 Scale Command Message Slot 11 Scale Command Message Slot 12 Weight Data Message Slot 12 Weight Data Message Slot 12 Scale Command Message Slot 12 Scale Command
6-9
IND780 PLC Interface Manual The floating point format provides four 16-bit words of input data and three 16-bit words of output data per Message Slot. See Table 6-3 and Table 6-4 for details. The number of Message Slots is set up in Communication > PLC Interface > Data Format setup menu. 4000, 40001 and 400001 are PLC processor memory-dependent. Refer to PLC documentation for I/O mapping Any scale can be configured as any slot.
Table 6-3: Modbus TCP PLC Floating Point Input Words Register Address
400001 400002 400003 400004 400005 400006 400007 400008 400009 400010 400011 400012 400013 400014 400015 400016 400017 400018 400019 400020 400021 400022 400023
Bits 0 7
Message Slot 1, Reserved Message Slot 1 Floating Point data Message Slot 1 Floating Point data Message Slot 1, Scale Status, See Message Slot Table Message Slot 2, Reserved Message Slot 2 Floating Point data Message Slot 2 Floating Point data Message Slot 2, Scale Status, See Message Slot Table Message Slot 3, Reserved Message Slot 3 Floating Point data Message Slot 3 Floating Point data Message Slot 3, Scale Status, See Message Slot Table Message Slot 4, Reserved Message Slot 4 Floating Point data Message Slot 4 Floating Point data Message Slot 4, Scale Status, See Message Slot Table Message Slot 5, Reserved Message Slot 5 Floating Point data Message Slot 5 Floating Point data Message Slot 5, Scale Status, See Message Slot Table Message Slot 6, Reserved Message Slot 6 Floating Point data Message Slot 6 Floating Point data
Bits 8 15
Message Slot 1, Command Response, See Message Slot Table Message Slot 1 Floating Point data Message Slot 1 Floating Point data Message Slot 1, Scale Status, See Message Slot Table Message Slot 2, Command Response, See Message Slot Table Message Slot 2 Floating Point data Message Slot 2 Floating Point data Message Slot 2, Scale Status, See Message Slot Table Message Slot 3, Command Response, See Message Slot Table Message Slot 3 Floating Point data Message Slot 3 Floating Point data Message Slot 3, Scale Status, See Message Slot Table Message Slot 4, Command Response, See Message Slot Table Message Slot 4 Floating Point data Message Slot 4 Floating Point data Message Slot 4, Scale Status, See Message Slot Table Message Slot 5, Command Response, See Message Slot Table Message Slot 5 Floating Point data Message Slot 5 Floating Point data Message Slot 5, Scale Status, See Message Slot Table Message Slot 6, Command Response, See Message Slot Table Message Slot 6 Floating Point data Message Slot 6 Floating Point data
6-10
Bits 0 7
Message Slot 6, Scale Status, See Message Slot Table Message Slot 7, Reserved Message Slot 7 Floating Point data Message Slot 7 Floating Point data Message Slot 7, Scale Status, See Message Slot Table Message Slot 8, Reserved Message Slot 8 Floating Point data Message Slot 8 Floating Point data Message Slot 8, Scale Status, See Message Slot Table Message Slot 9, Reserved Message Slot 9 Floating Point data Message Slot 9 Floating Point data Message Slot 9, Scale Status, See Message Slot Table Message Slot 10, Reserved Message Slot 10 Floating Point data Message Slot 10 Floating Point data Message Slot 10, Scale Status, See Message Slot Table Message Slot 11, Reserved Message Slot 11 Floating Point data Message Slot 11 Floating Point data Message Slot 11, Scale Status, See Message Slot Table Message Slot 12, Reserved Message Slot 12 Floating Point data Message Slot 12 Floating Point data Message Slot 12, Scale Status, See Message Slot Table
Bits 8 15
Message Slot 6, Scale Status, See Message Slot Table Message Slot 7, Command Response, See Message Slot Table Message Slot 7 Floating Point data Message Slot 7 Floating Point data Message Slot 7, Scale Status, See Message Slot Table Message Slot 8, Command Response, See Message Slot Table Message Slot 8 Floating Point data Message Slot 8 Floating Point data Message Slot 8, Scale Status, See Message Slot Table Message Slot 9, Command Response, See Message Slot Table Message Slot 9 Floating Point data Message Slot 9 Floating Point data Message Slot 9, Scale Status, See Message Slot Table Message Slot 10, Command Response, See Message Slot Table Message Slot 10 Floating Point data Message Slot 10 Floating Point data Message Slot 10, Scale Status, See Message Slot Table Message Slot 11, Command Response, See Message Slot Table Message Slot 11 Floating Point data Message Slot 11 Floating Point data Message Slot 11, Scale Status, See Message Slot Table Message Slot 12, Command Response, See Message Slot Table Message Slot 12 Floating Point data Message Slot 12 Floating Point data Message Slot 12, Scale Status, See Message Slot Table
6-11
Register Address
401025 Reserved Reserved
Usage
Message Slot 1 Command Message Slot 1 Command Message Slot 1 Floating Point data Message Slot 1 Floating Point data Message Slot 1 Floating Point data Message Slot 1 Floating Point data Message Slot 2 Command Message Slot 2 Command Message Slot 2 Floating Point data Message Slot 2 Floating Point data Message Slot 2 Floating Point data Message Slot 2 Floating Point data Message Slot 3 Command Message Slot 3 Command Message Slot 3 Floating Point data Message Slot 3 Floating Point data Message Slot 3 Floating Point data Message Slot 3 Floating Point data Message Slot 4 Command Message Slot 4 Command Message Slot 4 Floating Point data Message Slot 4 Floating Point data Message Slot 4 Floating Point data Message Slot 4 Floating Point data Message Slot 5 Command Message Slot 5 Command Message Slot 5 Floating Point data Message Slot 5 Floating Point data Message Slot 5 Floating Point data Message Slot 5 Floating Point data Message Slot 6 Command Message Slot 6 Command Message Slot 6 Floating Point data Message Slot 6 Floating Point data Message Slot 6 Floating Point data Message Slot 6 Floating Point data Message Slot 7 Command Message Slot 7 Command
6-12
Register Address
401045
Usage
Message Slot 7 Floating Point data Message Slot 7 Floating Point data Message Slot 7 Floating Point data Message Slot 7 Floating Point data Message Slot 8 Command Message Slot 8 Command Message Slot 8 Floating Point data Message Slot 8 Floating Point data Message Slot 8 Floating Point data Message Slot 8 Floating Point data Message Slot 9 Command Message Slot 9 Command Message Slot 9 Floating Point data Message Slot 9 Floating Point data Message Slot 9 Floating Point data Message Slot 9 Floating Point data Message Slot 10 Command Message Slot 10 Command Message Slot 10 Floating Point data Message Slot 10 Floating Point data Message Slot 10 Floating Point data Message Slot 10 Floating Point data Message Slot 11 Command Message Slot 11 Command Message Slot 11 Floating Point data Message Slot 11 Floating Point data Message Slot 11 Floating Point data Message Slot 11 Floating Point data Message Slot 12 Command Message Slot 12 Command Message Slot 12 Floating Point data Message Slot 12 Floating Point data Message Slot 12 Floating Point data Message Slot 12 Floating Point data
In the template data format a message slot is a shared data variable. The number of message slots is limited to 256 bytes (I/O).
IND780 PLC Interface Manual will send specific weight data to the PLC input data based on the data it receives from the PLCs output data. The PLCs output words consist of one 16-bit integer value, which may be used to download a tare or target, and one 16-bit word for bit encoded command information. Table 6-5 and Table 6-6 provide detailed information on the integer and division data formats. Read data refers to the PLCs input data and write data refers to the PLCs output data.
Table 6-5: Discrete Read Integer or Division IND780 >> PLC, per Message Slot
Octal Address 0 1 2 3 4 5 6 7 10 11 12 13 14 15 16 17 WORD 0 IN X X X X X X X X X X X X X X X X
12 1
WORD 1 IN Feed
2 2 3 4
Bit number 0 1 2 3 4 5 6 7 8 9 10 11 12
4
Fast Feed
Tolerance OK
Under low tolerance Over high tolerance Comparator 3 Comparator 2 Comparator 1 ENTER key Input 1 Input 2 Input 3 Motion
7 7 7 6 5 5 5
8 9 10
13 14 15
Update in progress
11
2 3 4
5. Bits 5, 6 and 7 provide Comparators 1, 2 and 3 statuses. If the comparator is active, the respective bit is set to 1. 6 7 8 9 Bit 8 is set to a 1 when the ENTER key is pressed on the keypad of the terminal. The bit remains on for 30 seconds then resets to 0. Bit 9, bit 10, and Bit 11 mirror the state of the first three discrete inputs on the internal I/O board slot 5 (0.5.1, 0.5.2 and 0.5.3). If the input is ON then the bit is set to a 1. Bit 12 is set to a 1 when the scale is in motion (unstable). Bit 13 is set to a 1 when the scale is in net mode (a tare has been taken).
10 Bit 14 is set to a 1 when the terminal is in the process of updating its data for the PLC scanner. The PLC should ignore ALL of the data in this case and simply re-scan it. 11 Bit 15 is set to a 1 when the scale is operating properly (NOT over capacity, under capacity, in power-up, in expanded mode, or in setup mode).The PLC program should continuously monitor
6-14
Table 6-6: Discrete Write Integer or Division PLC >> IND780, per Message Slot
Octal Address 0 1 2 3 4 5 6 7 10 11 12 13 14 15 16 17 WORD 0 OUT X X X X X X X X X X X X X X X X
1
Bit number 0 1 2 3 4 5 6 7
8
Load Tare
5 6
8 9 10 11 12 13 14 15
Display mode
Load Target
3 4 5 6 7 8 9
10 Bit 12, bit 13, and bit 14 can be used to control the state of the first three discrete outputs on the terminals internal I/O board in slot 5. These are addressed as 0.5.1, 0.5.2, and 0.5.3. Setting the bit to a 1 state causes the output to be turned ON. This action will occur regardless of the discrete output assignment within the IND780.
6-15
Floating Point
Operational Overview
The terminal uses integer commands from the PLC to select the floating point weight output data. The terminal recognizes a command when it sees a new value in the scales command word. If the command has an associated floating point value (for example: loading a target value), it must be loaded into the floating point value words before the command is issued. Once the terminal recognizes a command, it acknowledges the command by setting a new value in the command acknowledge bits of the scales command response word. It also tells the PLC what floating point value is being sent (via the floating point input indicator bits of the command response word). The PLC waits until it receives the command acknowledgment from the terminal before sending another command. The terminal has two types of values that it can report to the PLC: real-time and static. When the PLC requests a real-time value, the terminal acknowledges the command from the PLC once but sends and updates the value at every interface update cycle. If the PLC requests a static value, the terminal acknowledges the command from the PLC once and updates the value once. The terminal will continue to send this value until it receives a new command from the PLC. Gross weight and net weight are examples of real-time data. Tare weight, target, fine feed, and tolerance values are examples of static data. The terminal can send a rotation of up to nine different real-time values for each scale. The PLC sends commands to the terminal to add a value to the rotation. Once the rotation is established, the PLC must instruct the terminal to begin its rotation automatically, or the PLC may control the pace of rotation by instructing the terminal to advance to the next value. If the terminal is asked to automatically alternate its output data, it will switch to the next value in its rotation at the next interface update cycle. (The interface update cycle has an update rate of up to 17 Hz or 60 milliseconds.) The PLC may control the rotation by sending alternate report next field commands (1 and 2). When the PLC changes to the next command, the terminal switches to the next value in the rotation. The terminal stores the rotation in its shared data so the rotation does not have to be re-initialized after each power cycle. When the PLC does not set up an input rotation, the default input rotation consists of gross weight only. See the floating-point rotation examples in Table 6-11 through Table 6-14 for additional information. The method of handling string and floating point data may vary between different PLCs. The IND780 provides floating point data in the byte order entered in the Data Format setup.
6-16
IND780 PLC Interface Manual Table 6-7 through Table 6-10 provide detailed information on the floating-point data format. Read data refers to the PLCs input data and write data refers to the PLCs output data. The byte order follows the convention of the Modicon Quantum platform. Note that this is Double Word Swapped.
Table 6-7: Discrete Read Floating Point IND780 >> PLC Input, per Message Slot
Octal Address 0 1 2 3 4 5 6 7 10 11 12 13 14 15 16 17 1 FP Input Ind 1 FP Input Ind 2 FP Input Ind 3 FP Input Ind 4 FP Input Ind 5 Data integrity1 Cmnd Ack 1 Cmnd Ack 2
7 7 7 7 7
WORD 1 FP value X X X X X X X X X X X X X X X X
WORD 2 FP value X X X X X X X X X X X X X X X X
Bit number 0 1 2 3 4 5 6 7 8 9 10 11 12 13
11 4
Fast Feed
Tolerance OK
RESERVED
Under Negative Tolerance Over Positive Tolerance Selected scale Custom Bit Custom Bit ENTER key Input 1 Input 2 Input 3 Motion
9 9 9 6 6 5
10 12
11
13 13
Data integrity 2
14
14 15
2 3 4 6
5 Bit 5 will be set to a 1 when the associated scale is selected on the IND780 console panel.
10 Bit 12 is set to a 1 when the scale is in motion (unstable). 11 The Data Integrity bit in WORD 0 - bit 13 is used in conjunction with the bit in WORD 3 - bit 14 to insure that the floating point data is valid. For the data to be valid both bits must have the same polarity. These bits will change to the opposite state every interface update cycle. If they do
6-17
Dec
0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 1928 29 30 31
* **
Data
Gross Weight* Net Weight* Tare Weight* Fine Gross Weight* Fine Net Weight* Fine Tare Weight* Rate ALxx01 SDV, instance by scale ** ALxx02 SDV, instance by scale ** AJxx01 SDV, instance by scale ** AJxx02 SDV, instance by scale ** Low-pass filter frequency Notch filter frequency Target value, instance by scale Target positive tolerance value, instance by scale Target Fine Feed value, instance by scale Target negative tolerance value, instance by scale Target spill value, instance by scale Primary units, low increment size Not used Last IND780 error code No data response command successful No data response command failed
These are real-time fields that the PLC may request either through an input rotation or a report command. All other fields may only be requested through a report command. SDV means Shared Data Variable.
6-18
WORD 1
Bit number 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
Not all commands will require a value in the floating point load value words.
6-19
4c Start ID2 sequence 7,9 4e 4f 50 51 52 53 54 55 56 57 58 59 Disable LCD display Enable LCD display 7 Set normal display mode 7,9 Display message 1 7,9 Display message 2 7,9 Display message 3 7,9 Display message 4 7,9 Display Message 5 7,9 Start ID1 sequence 7,9 Display SDV PD0118 7,9 Disable weight display 7 Enable weight display 7
7
5a Set discrete output 0.5.1 ON 7 5b 5c 5d 64 65 66 67 68 69 6e 6f 70 71 Set discrete output 0.5.2 ON Set discrete output 0.5.3 ON 7 Set discrete output 0.5.4 ON 7 Set discrete output 0.5.1 OFF 7 Set discrete output 0.5.2 OFF 7 Set discrete output 0.5.3 OFF 7 Set discrete output 0.5.4 OFF 7 Master control relay OFF7, 12 Master control relay ON7, 12 Set target value 4,10, 13 Set target fine feed value 4,10 Set - tolerance value 4,10 Set target value and apply4, 10, 14
7
SPxx05
72 Start target logic 7,10 73 74 75 76 77 78 79 7a 7b 7c 83 a0 a1 a2 a3 a4 A5 a6 a7 a8 a9 Abort target logic 7,10 Target use gross weight 7,10 Target use net weight 7,10 Target use rate 7,10 Target, absolute weight 1 speed 7,10 Target, absolute weight 2 speed 7,10 Enable target latching 7,10 Disable target latching 7,10 Reset target latch 7 Set target spill value4, 10 Set + tolerance value 4,10 Apply scale setup 7 Write Calibration to EEProm 7 Disable Tare on IND780 console 7,11 Enable Tare on IND780 console 7 Disable push button Tare on IND780 console 7,11 Enable push button Tare on IND780 console 7 Disable numeric Tare on IND780 console 7,11 Enable numeric Tare on IND780 console 7 Select scale 3 7 Select scale 4 7 SPxx04 SPxx04 SPxx04 SPxx08 SPxx08 SPxx06 SPxx06 SPxx07 SPxx11 QC0149
ALxx016 ALxx026
CPxx017 CPxx027
46 Custom print 37 47 Custom print 47 48 Custom print 57 49 Set low-pass filter corner frequency 4 4a Set notch filter frequency 4 4b Reset ENTER key 7
6-20
4. 5. 6. 7. 8. 9.
10. Target, Fine Feed, Tolerances, Restart, Abort and other Target variables are relative to each scale. Note: Restart of an active Target will cause the associated outputs to cycle off then back on. 11. Does not disable the PLC tare functions. 12. Setting the master control relay OFF turns off all outputs and stops target logic. The target logic must be restarted after the master control relay is turned ON. 13. Target logic must be restarted to apply the new target value. 14. New target value is applied when command is sent.
In Floating Point Message mode, the PLC and IND780 terminal exchange weight, target, and tare data in single-precision floating point format. The IEEE Standard for Binary Floating-Point Arithmetic, ANSI/IEEE Standard 754-1985, specifies the format for single-precision floating point numbers. It is a 32-bit number that has a 1-bit sign, an 8-bit signed exponent, and a 23-bit mantissa. The 8-bit signed exponent provides scaling of weight and rate data. The 23-bit mantissa allows representation of 8 million unique counts. Although the single-precision floating point number provides greater numerical precision and flexibility than integer weight representations, it has limitations. The weight representation may not be exact, particularly for the extended-resolution weight fields for high-precision bases. Some PLCs require special integrity checking to communicate floating point numbers. There are two data integrity bits that the IND780 uses to maintain data integrity when communicating with the PLC. One bit is in the beginning word of the data; the second is in the ending byte of the data for a scale slot. The PLC program must verify that both data integrity bits have the same polarity for the data in the scale slot to be valid. There is a possibility that the PLC program will see several consecutive invalid reads when the terminal is freely sending weigh updates to the PLC, if the PLC program detects this condition, it should send a new command to the terminal.
6-21
IND780 PLC Interface Manual The method of handling string and floating point data varies between PLCs platforms. The IND780 provides floating point data in the word order set up by the user.
As long as the PLC leaves the 11 (dec) in the command word the IND780 terminal will update the net value every interface update cycle.
Table 6-12: Data Requirement: Load Target Value = 21.75 for Scale 1
Step # 1 (PLC loads floating point value first) 2 (PLC sends command to set target 1 cutoff value) 3 (IND780 terminal sees new command , loads the value into the target and ends a return message to indicate the new target value) 4 114 (dec) loaded (PLC instructs IND780 into command terminal to start using word O:XX1 new target value) 5 (IND780 terminal sees new command) Command ack. = 2 F.P. ind = 30 (null value) 110 (dec) loaded into command word O:XX1 Scale command (from PLC) Scale Floating Point Value floating point value = 21.75 Command response from terminal Floating Point Value
The PLC should always wait to receive a command acknowledgment before sending the next command to the IND780 terminal. After the PLC finishes loading its target value, it can resume monitoring the weight information required by sending a command to report some type of weight or set up a rotation of reported data.
6-22
At this point, the rotation has been set up. Now the PLC needs to command the IND780 terminal to begin the rotation. 7 (PLC sends the command to begin the rotation at interface update cycle) 8 (IND780 terminal sends gross weight at interface update cycle ~ 60 msec) 9 (PLC leaves 0 in its command word and the IND780 terminal sends the rate value at the next interface update cycle) 10 (PLC leaves 0 in its command word and IND780 terminal sends the gross value at next interface update cycle) 11 (PLC leaves 0 in command word and IND780 terminal sends the rate value at the next interface update cycle) 0 (dec) loaded into command word O:XX1 0 (dec) loaded into command word O:XX1 Command ack. = 0 F.P. ind = 0 Floating point value = gross wt.
This rotation continues until the PLC sends a different command. At approximately every 60 msec the IND780 terminal updates its data with the next field in its rotation. The PLC must check the floating point indication bits to determine which data is in the floating point value.
6-23
At this point, the rotation has been set up. Now the PLC needs send commands to the IND780 terminal to begin the rotation and advance to the next value when required. 7 (PLC sends the command to report the first field in the rotation.) 8 (IND780 terminal acknowledges the command and sends net weight at every interface update cycle until the PLC gives the command to report the next rotation field.) 9 (PLC sends the command to report the next field.) Note: if the PLC leaves the 1 (dec) in the command, the IND780 terminal does NOT see this as another command to report the next rotation field. 2 (dec) loaded into command word O:XX1 1 (dec) loaded into command word O:XX1
6-24
At approximately every 60 msec the IND780 terminal updates its data with new data, but it does not advance to the next field in the rotation until the PLC sends it the command to report the next field. The PLC should check the floating point indication bits to determine which data is in the floating point value
Software Setup
The IND780 terminal automatically detects the presence of a Modbus TCP Kit option board if one is installed. When the option is detected, the IND780 terminal enables the Modbus TCP parameters in a program block under Communications > PLC Interface > Ethernet / IP Modbus/TCP. Figure 6-5 shows the Modbus TCP setup block and Figure 6-6 graphs the Communication > PLC Interface > Data Format setup block. Default values are indicated with an asterisk (*).
6-25
IND780 PLC Interface Manual Alternatively, DHCP client can be enabled if the IP address is to be assigned automatically by the network server.
2. Select the Format (Integer, Divisions, Floating Point, Template or Application): [default Integer] Changing the Format will delete any existing Message Slots. Integer reports scale weight as a signed 16 bit integer ( 32767). Divisions reports scale weight in display divisions ( 32767). The PLC multiplies the reported divisions by the increment size to calculate the weight in display units. Floating Point displays weight in floating point data format Template Allows the end-user to customize PLC communications input and output data by allowing them to set up input and output templates with shared data variables. This format is fixed and cannot 6-27
IND780 PLC Interface Manual be changed on the fly by the PLC program. The template editor also calculates the input and output sizes upon exit of the editor. In order to populate the data fields, consult the Shared Data Reference Manual (document number 64059110) provided on the CD-ROM supplied with your terminal. Application Allows a TaskExpert program to interact with the PLC input and output data. The TaskExpert program is responsible for setting up all input and output data from the IND780 and to control the data length of the input and output assemblies. For application commands used in TaskExpert, refer to the TaskExpert Reference Manual (document number 64060431).
Table 6-15: PLC Data Byte-Ordering Byte Swap Integer Float String 12 1234 ABCD Word Swap 21 4321 ABCD Double Word Swap 12 3412 ABCD
Word Swap Takes the IEE 754 single-precision floating point format and swaps the two words in the 32-bit double word. This format is compatible with RSLogix 5000 processors. Byte Swap Makes the floating point format compatible with S7 PROFIBUS. Double Word Swap Makes the data format compatible with the Modicon Quantum PLC for Modbus TCP networks.
4. Set the Time Interval in milliseconds. (Only when the Format is Template) 5. Use the Configure drop-down list to select the direction of data flow IND780 >> PLC or PLC >> IND780. (Only when the Format is Template) 6. The bottom of this screen (Figure 6-8) displays the number of bytes that will be sent by the IND780 and the number of bytes expected from the PLC.
6-28
IND780 PLC Interface Manual 7. Depending on which format is selected, press the VIEW TABLE softkey to set up the number of Message Slots (maximum number is 12; default is 0), or to configure the Template for communications between the IND780 and the PLC. Figure 6-9 shows the Message Slots View, which is viewed whenever the Format is not Template.
Figure 6-10 shows the Template View, accessed when Format is set to Template. Each message slot will be a Shared Data Variable, entered by the user. These entered message slots are associated only to the Shared Data Variable entered and not to a scale.
Press the EXIT softkey Press the EDIT softkey Press the NEW softkey Press the DELETE softkey Press the CLEAR softkey
to exit the view screen. to edit an existing slot. to enter a new slot. to delete an existing slot. to delete all existing slots.
6-29
IND780 PLC Interface Manual Figure 6-11 shows the screen that opens when NEW is selected from the Message Slots View screen (Figure 6-9).
Scale Enter the scale number to be associated with the new Message Slot. Terminal Default is Local; remote terminals 1 through 20 may be selected if remote PLC interface sharing is used. Figure 6-12 shows a series of Template New screens, as accessed from the Template View screen (Figure 6-10).
Figure 6-12: New Template Screens, PLC to IND780 and IND780 to PLC
Slot Automatically assigned. SDName An alphabetic entry field used to define the Shared Data variable associated with the slot.
6-30
IND780 PLC Interface Manual Length (Bytes) and Data Type Automatically displayed once the SDName has been entered. Terminal Default is Local; remote terminals 1 through 20 may be selected if remote PLC interface sharing is used. For a complete listing of Shared Data Fields, refer to the IND780 Shared Data Reference Manual. Refer to the Table 6-5 (Discrete Read) and Table 6-6 (Discrete Write) in this chapter for additional information on mapping of discrete read and write data to the PLC.
Troubleshooting
If the IND780 does not communicate with PLC, do the following: Check wiring and network termination. Confirm that the IND780 settings for data type and IP Address assignment match those in the PLC and that each IND780 has a unique address. Replace the EtherNet / IP Modbus TCP interface kit if the problem persists. If the communication kit was changed from another type, like PROFIBUS, ControlNet or Remote I/O, a master reset of the IND780 must be performed.
Status LEDs
The EtherNet/ IP Modbus TCP interface card has four status LEDs indicators to indicate communication and fault status of the card. Figure 6-2 indicates the location of these LEDs, and Figure 6-13 shows the array of the LEDs on the card. Table 6-16 explains the meaning
Link Activity Activity
1 4
2 3
Figure 6-13: EtherNet / IP Modbus TCP Board Status LED Array Table 6-16: EtherNet / IP LEDs Status Indications
LED # 1 - Link Activity State Off Green Off Green (1 Hz flash) 2 - Module Status Red (1 Hz flash) Red (2 Hz flash) Red (4 Hz flash) Red No link (or no power) Connected to an Ethernet network No power IP address not set via switch Invalid MAC address (internal error) Failed to load Ethernet configuration Fatal internal error Duplicate IP address detected Status
6-31
This LED indicates the number of established Modbus/TCP connections to the terminal. The number of established connections is equal to the number of blinks or flashes on this LED. Off No Ethernet activity (or no power) Flashes green each time a packet is received or transmitted
4 - Activity
Green, flashing
Description
Installation Instructions PCB Package Clamp-on ferrite M3 x 8 screws
Qty.
1 1 1 3
6-32
IND780 PLC Interface Manual Open a project by accessing the file menu and selecting OPEN, then selecting the project. In this example, the project is named MT_INT.PRJ (Figure 6-15).
Once the project is open, the project browser should appear; if it does not appear, click on to display it. Next the Network card must be configured. Double click on your project in the project browser. In this example, click on the blue highlighted (Figure 6-16) item to open the PLC Configuration window.
6-33
IND780 PLC Interface Manual The PLC Configuration window (Figure 6-17) will open.
Click on the Config Extensions Folder in the center pane, above. The branch will expand to show Ethernet / I/O Scanner. Double click on the Ethernet / I/O Scanner to bring up the details of the Ethernet card (Figure 6-18). Here, the IP addresses must be configured the PLCs, that of the IND780 with which it communicates. The data communicated to and from the IND780 is also configured in this window.
6-34
IND780 PLC Interface Manual For a more detailed description of each column in the configuration window, click on the Help button (at lower right in Figure 6-18). The following elements must be configured:
Slave IP Address: IP Address of the IND780 terminals Modbus TCP interface. This value is configured in the IND780 Setup tree at Communication > PLC Interface > Ethernet/IP - Modbus/TCP. This value is typically 0
Unit ID: Health Timeout: Rep Rate: Read Ref Master: Read Ref Slave:
The start of PLC registers to which the IND780s information is written. This address ALWAYS is 400001 The start of IND780 register where the scale data is stored. This address can be any value 4XXXXX PLC address. * NOTE, data in the Read Ref Slave is read and then stored in the Read Ref Master. This is determined by the IND780 settings, and is determined by # of scales, Mode of operation etc. In our example we are using 4 scales in INTEGER Mode. In the IND780 we are reading 16 bytes and writing 16 bytes. When configuring the PLC each 4XXXX register address word consists of 2 bytes of information. This gives a total of 16 bytes / 2 bytes per word, or 8 for Read Length and 8 for Write Length.
6-35
IND780 PLC Interface Manual Both the PLC and the IND780 IP address and address settings must be configured refer to Figure 6-19. The Ethernet card used on the configuration shown is the 140-NOE-771-00
Figure 6-19: PLC and IND780 Values for Ethernet / I/O Scanner
Examples of how to configure the Modicon Ethenet I/O scanner for various scale configurations are provided below.
Figure 6-20: INT or DIV Mode Configuration Table 6-18: Configuration for Four Scales, INT or DIV Mode Description Slot / Scale* Address in IND780 Format
Read by PLC from 780: Weight Data Status Data Weight Data Status Data Slot 1 Slot 1 Slot 2 Slot 2 400001 400002 400003 400004 Int Int Int Int
6-36
The PLC will write to: Data Value to be written Command Word Data Value to be written Command Word Data Value to be written Command Word Data Value to be written Command Word * Slot 1 Slot 1 Slot 2 Slot 2 Slot 3 Slot 3 Slot 4 Slot 4 401025 401026 401027 401028 401029 401030 401031 401032 Int Int Int Int Int Int Int Int
Note that any scale can be configured to correspond with any slot number. 4001, 40001, 400001 PLC Memory Dependent.
Figure 6-21: FLP Mode Configuration Table 6-19: Configuration for Four Scales, FP Mode Description Slot / Scale* Address in IND780 Read by PLC from 780: Weight Data Command Ack Register Status Register Weight Data Command Ack Register Status Register Weight Data Slot 1 Slot 1 Slot 1 Slot 2 Slot 2 Slot 2 Slot 3 400002-400003 400001 400004 400006-400007 400005 400008 400010-400011 Float Int Int Float Int Int Float Format
6-37
* Note that any scale can be configured to correspond with any slot number. 4001, 40001, 400001 PLC Memory Dependent.
Read Logic
The 400001 weight data can be read directly by the PLC. However, to understand the 400002 Status data fully some basic logic is needed to break the data Word into Bits. In concept the use of an INT_TO_WORD instruction will first read the INT value from the IND780 in a form that can be broken into bits. Then once the data is in a word format, a WORD_TO_BIT instruction will complete the process of extracting the individual bits. Figure 6-22 and Figure 6-23 show an example of logic that can be used to read the status word.
6-38
6-39
Write Logic
The 401025 Data Value can be written directly by the PLC. However, to utilize the 401026 command Word fully some basic logic is needed to convert the command bits into a data Word. In concept, the use of a BIT_TO_WORD instruction will first get the command bits into a WORD value. Next the use of a WORD_TO_INT instruction will complete the process of packing the individual command bits into an INTEGER format that can be written to the IND780. Figure 6-24 shows an example of logic that can be used control the command word.
6-40
Chapter 7
Specifications
Maximum Cable Length Max Load Resistance Outputs Resolution Error Indication 300 m (1000 ft.) 500 maximum 2 channels capable of supplying 4-20 mA 16 bit resolution 65536 levels across entire range Two open collector discrete output error signals per channel to indicate out-of-range conditions of the terminal, labeled Under and Over.
Note that if the maximum load resistance value is exceeded, the analog output will not operate properly.
7-1
IND780 PLC Interface Manual Figure 7-1 shows the Analog Output Option Board with its connector at top right.
7-2
IND780 PLC Interface Manual Table 7-1 summarizes the function of the analog output under zero and over the high limit, and the operation of the Under and Over discrete output error signals.
Table 7-1: Analog Signal Operation
Installation
WARNING!
DISCONNECT ALL POWER TO THIS UNIT BEFORE SERVICING. DO NOT APPLY POWER TO THE TERMINAL UNTIL INSTALLATION OF COMPONENTS AND EXTERNAL WIRING HAVE BEEN COMPLETED.
CAUTION
OBSERVE PRECAUTIONS FOR HANDLING ELECTROSTATIC SENSITIVE DEVICES.
WARNING!
THE ANALOG OUTPUT BOARD KIT NUMBER 72230302 MUST NOT BE USED IN AN IND780 TERMINAL INSTALLED IN AN AREA CLASSIFIED AS DIVISION 2 OR ZONE 2/22. FAILURE TO COMPLY WITH THIS WARNING COULD RESULT IN BODILY HARM AND/OR PROPERTY DAMANGE.
The analog output option for all enclosure types can be installed at the factory or it can be ordered as a kit and installed in the field. The option kit includes detailed 7-3
IND780 PLC Interface Manual drawings to assist in the installation. The analog output option board can only be installed in slot locations 2 thru 6 on the terminals main board. The recommended wiring for the analog output is 2-conductor, 20 GA cable available from METTLER TOLEDO (part number 510220190). It is equivalent to Belden #8762.
Wiring
WARNING!
DISCONNECT ALL POWER TO THIS UNIT BEFORE SERVICING. DO NOT APPLY POWER TO THE TERMINAL UNTIL INSTALLATION OF COMPONENTS AND EXTERNAL WIRING HAVE BEEN COMPLETED.
WARNING!
IF THIS DEVICE IS USED IN AN AUTOMATIC OR MANUAL FILLING CYCLE, ALL USERS MUST PROVIDE A HARD-WIRED EMERGENCY STOP CIRCUIT OUTSIDE THE DEVICE. FAILURE TO OBSERVE THIS PRECAUTION COULD RESULT IN BODILY INJURY.
The maximum recommended cable length for the 4-20 mA output is 1,000 feet (300 meters). The recommended cable for use with the analog output is shielded two-conductor stranded 20-gauge cable (Belden #8762 or equivalent), which is available from METTLER TOLEDO using part number 510220190. Refer to Figure 7-2 for connection and termination information.
NOTES: 1. ERROR OUTPUTS MUST BE MONITORED TO DETERMINE WHEN WEIGHT SIGNAL IS VALID. 2. ERROR SIGNALS ARE OPEN COLLECTOR, CURRENT SINKING OUTPUTS. 3. VOLTAGE: 5-30 VDC, 200 mA MAXIMUM CURRENT. 4. USE TWO-CONDUCTOR SHIELDED CABLE FOR SIGNAL LINES. 5. MAXIMUM RESISTANCE OF DEVICE LOAD IS 500 OHMS. 6. THE VOLTAGE SOURCE FOR THE ERROR OUTPUTS MUST BE A CLASS 2 MARKED OR A LIMITED POWER SOURCE (LPS) COMPLIANT POWER SUPPLY. 7. Pin 5 Common 1 is the return path for Channel 1 (4-20mA output). Pin 6 Common 2 is the return path for Channel 2 (4-20mA output). Pin 5 and Pin 6 are not the same as the GND of Pin 3 and Pin 8. 2 8. WIRE SIZE: 14 AWG (2.1 mm ) MAXIMUM 2 22 AWG (0.3 mm ) MINIMUM.
7-4
Figure 7-3: Setup Procedures for Configuring the Analog Output Option Card
7-5
4. Figure 7-4: Analog Output 1 Screen 5. The following settings are made in this screen:
Parameter Explanation and Settings Choices are None, Displayed Weight (the default), Gross Weight, Rate and Application. None disables the analog output. Displayed Weight outputs an analog signal based on the displayed net or gross weight. When Gross Weight is selected, the analog signal is based on the gross weight regardless of what the net weight might be. In order to be available as a source, Rate must be configured at Scale > Rate. The Application selection allows a TaskExpert program to assign an application variable as the source and to control the operation of the analog output. Refer to the TaskExpert Reference Manual (64060431) for details.
Source
Channel
Options are Scale 1, Scale 2, Scale 3, Scale 4, or Sum Scale (if they are enabled). This selection refers to the source channel. Enter the desired source value at which the analog output should be at 4 mA (zero) level. Typically this would be 0 in most applications; however, any valid value below the Full Scale value can be used. Enter the desired source value at which the analog output should be at its 20 mA (high limit) level. For sources of weight, this would typically be scale capacity, but it could be lower. For rate, this should be the rate value that should provide a full analog output signal. Since up to two Analog Output option boards can be installed in the IND780, the Option Location selection specifies which of the option board slot locations to apply to the currently selected Analog Output channel. Choices include None, 2, 3, 4, 5 and 6.
Zero Value
Option Location
7-6
IND780 PLC Interface Manual 6. After all these parameters have been entered, the analog output signal can be adjusted to meet the customers specific requirements using the CAPTURE ZERO softkey and the CAPTURE SPAN softkey . 7. To adjust the zero reference analog signal, press the CAPTURE ZERO softkey . Note that a display message is shown warning that during the adjustment, the analog output signal will change value indicating that it will not represent the source value. Press the ESCAPE softkey to exit the zero adjustment process or press the OK softkey to continue the adjustment process. 8. At the Analog Output - Calibrate Zero screen (Figure 7-5), use the softkeys to adjust the analog output signal to be exactly zero on the attached device. The available softkeys are described in Table 7-2.
Figure 7-5: Analog Output Calibrate Zero Screen Table 7-2: Analog Output Calibrate Softkey Descriptions Coarse Down Fine Down Fine Up Coarse Up Decreases the analog signal level in large steps. Decreases the analog signal level in small steps. Increases the analog signal level in small steps. Increases the analog signal level in large steps.
9. When the zero adjustment is complete, press the EXIT softkey the Analog Output screen.
to return to
10. Now, the full scale analog output value can be adjusted by pressing the CAPTURE SPAN softkey . A similar warning message will be shown indicating the analog output will change and will not monitor changes in the source. Press the ESCAPE softkey to exit the span adjustment process or press the OK softkey to continue the adjustment process. 11. At the Analog Output - Calibrate Full screen (Figure 7-6), use the softkeys to adjust the analog output signal to be exactly what the customers device requires for its high limit. The available softkeys are described in Table 7-2.
7-7
12. When the full scale adjustment is complete, press the EXIT softkey to the Analog Output screen.
to return
Status LEDs
The Analog Output option board has four LEDs to indicate status of the card for troubleshooting purposes. Figure 7-7 indicates the location of the LEDs and Table 7-3 explains its indications.
LED 3 LED 4 LED 2 LED 1
Figure 7-7: Analog Output LEDs Table 7-3: Analog Output Status LED Indications LEDs LED 1: USB LED 2: Channel 1 LED 3: Channel 2 LED 4: Board OK Color Green Green Green Green Meaning Solid ON: USB communicating with IND780 main board Solid ON: Channel 1 is functioning Solid ON: Channel 2 is functioning Slow blink: checking board communication and function Fast blink: board communicating and functioning
7-8
Description
Installation Instructions PCB Package Installation Kit
Qty.
1 1 1
7-9
METTLER TOLEDO
1900 Polaris Parkway Columbus, Ohio 43240
METTLER TOLEDO is a registered trademark of Mettler-Toledo, LLC 2012 Mettler-Toledo, LLC