Download Full User Guide ACT350 Transmitter English (30MB)

User's Guide
ACT350
Transmitter
ACT350 Transmitter
Essential Services for Dependable Performance of Your ACT350 Transmitter
Congratulations on choosing the quality and precision of METTLER TOLEDO. Proper use of your
new equipment according to this Manual and regular calibration and maintenance by our factorytrained service team ensures dependable and accurate operation, protecting your investment.
Contact us about a service agreement tailored to your needs and budget. Further information is
available at www.mt.com/service.
There are several important ways to ensure you maximize the performance of your investment:
1.
Register your product: We invite you to register your product at
www.mt.com/productregistration so we can contact you about enhancements, updates and
important notifications concerning your product.
2.
Contact METTLER TOLEDO for service: The value of a measurement is proportional to its
accuracy – an out of specification scale can diminish quality, reduce profits and increase
liability. Timely service from METTLER TOLEDO will ensure accuracy and optimize uptime and
equipment life.
a. Installation, Configuration, Integration and Training: Our service representatives are factorytrained, weighing equipment experts. We make certain that your weighing equipment is
ready for production in a cost effective and timely fashion and that personnel are trained for
success.
b. Initial Calibration Documentation: The installation environment and application
requirements are unique for every industrial scale so performance must be tested and
certified. Our calibration services and certificates document accuracy to ensure production
quality and provide a quality system record of performance.
c. Periodic Calibration Maintenance: A Calibration Service Agreement provides on-going
confidence in your weighing process and documentation of compliance with requirements.
We offer a variety of service plans that are scheduled to meet your needs and designed to
fit your budget.
d. GWP® Verification: A risk-based approach for managing weighing equipment allows for
control and improvement of the entire measuring process, which ensures reproducible
product quality and minimizes process costs. GWP (Good Weighing Practice), the sciencebased standard for efficient life-cycle management of weighing equipment, gives clear
answers about how to specify, calibrate and ensure accuracy of weighing equipment,
independent of make or brand.
© METTLER TOLEDO 2015
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 2015 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.
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.
RoHS Compliance Statement.

The majority of our products fall within categories 8 and 9. Those categories currently do not fall
within the scope of the Directive 2002/95/EG (RoHS) of January 27, 2003. If our products are
intended for use in other products which themselves fall within the scope of the RoHS Directive,
compliance requirements have to be separately negotiated contractually.

Those products which fall within categories 1-7 and 10 will be in compliance with the EU RoHS
Directive from no later than July 1, 2006.

If it is not possible for technical reasons to replace any non-RoHS-compliant substances in any of
the above products as required, we plan to inform our customers in a timely manner
Statement regarding harmful substances
We do not make direct use of harmful materials such as asbestos, radioactive substances or
arsenic compounds. However, we purchase components from third party suppliers, which may
contain some of these substances in very small quantities.
Warnings and Cautions
•
READ this manual BEFORE operating or servicing this equipment and FOLLOW these
instructions carefully.
•
SAVE this manual for future reference.
WARNING
THE ACT350 IS INTENDED TO BE USED FOR PROCESS CONTROL AND IS NOT APPROVED AS
A SAFETY COMPONENT. WHEN USED AS A COMPONENT PART OF A SYSTEM, ANY SAFETY
CIRCUITS MUST BE INDEPENDENT OF THE ACT350 AND REMOVE POWER FROM THE ACT350
OUTPUTS IN THE EVENT OF AN EMERGENCY STOP OR EMERGENCY POWER DOWN.
WARNING
ONLY USE RECOMMENDED 12-24 VDC POWER SUPPLY APPROVED AS NEC Class 2 OR
RATED AS LIMITED POWER PER IEC60950-1.
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.
WARNING
ONLY THE COMPONENTS SPECIFIED ON THE ACT350 DOCUMENTATION MEDIA CAN BE
USED IN THIS TRANSMITTER. ALL EQUIPMENT MUST BE INSTALLED IN ACCORDANCE WITH
THE INSTALLATION INSTRUCTIONS DETAILED IN THE USER’S GUIDE. INCORRECT OR
SUBSTITUTE COMPONENTS AND/OR DEVIATION FROM THESE INSTRUCTIONS CAN IMPAIR
THE SAFETY OF THE TRANSMITTER AND COULD RESULT IN BODILY HARM AND/OR PROPERTY
DAMAGE.
WARNING
BEFORE CONNECTING/DISCONNECTING ANY INTERNAL OR EXTERNAL ELECTRONIC
COMPONENTS, LOAD CELLS, HARNESSES 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 BODILY HARM AND/OR PROPERTY
DAMAGE.
WARNING
NOT ALL VERSIONS OF THE ACT350 ARE DESIGNED FOR USE IN HAZARDOUS (EXPLOSIVE)
AREAS. REFER TO THE DATA PLATE OF THE ACT350 TO DETERMINE IF A SPECIFIC
TRANSMITTER IS APPROVED FOR USE IN AN AREA CLASSIFIED AS HAZARDOUS BECAUSE OF
COMBUSTIBLE OR EXPLOSIVE ATMOSPHERES.
WARNING
THE ACT350 IS NOT INTRINSICALLY SAFE! DO NOT USE IN HAZARDOUS AREAS CLASSIFIED
AS DIVISION 1, ZONE 0, ZONE 20, ZONE 1 OR ZONE 21 BECAUSE OF COMBUSTIBLE OR
EXPLOSIVE ATMOSPHERES.
Warnings and Cautions
WARNING
INSTALLATION AND ANY SERVICE ON THIS EQUIPMENT MUST BE DONE ONLY AFTER THE
AREA IS SECURED AS NON-HAZARDOUS BY THE RESPONSIBLE PERSON ON-SITE
AUTHORIZED TO DO SO.
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.
NOTICE
DO NOT ACTIVATE POWER OVER ETHERNET (PoE) ON ETHERNET SWITCHES ON THE ACT350
NETWORK. ACTIVATING PoE MAY RESULT IN DAMAGE TO THE ACT350 TRANSMITTER.
NOTICE
IN ORDER TO ENSURE PROPER DISSIPATION OF HEAT FROM THE TRANSMITTER’S PCBS,
AND TO AVOID DAMAGE TO THE EQUIPMENT, THE ACT350 MUST BE MOUNTED VERTICALLY,
ON A HORIZONTAL DIN RAIL.
NOTICE
OBSERVE PRECAUTIONS FOR HANDLING ELECTROSTATIC SENSITIVE DEVICES.
Disposal of Electrical and Electronic Equipment
In conformance with the European Directive 2002/96/EC on Waste Electrical and Electronic
Equipment (WEEE) this device may not be disposed of in domestic waste. This also applies
to countries outside the EU, per their specific requirements.
Please dispose of this product in accordance with local regulations at the collecting point
specified for electrical and electronic equipment.
If you have any questions, please contact the responsible authority or the distributor from
which you purchased this device.
Should this device be passed on to other parties (for private or professional use), the
content of this regulation must also be related.
Thank you for your contribution to environmental protection.
Contents
30303895 | 00 | 11/2015
1
Introduction ................................................................................. 1-1
1.1.
ACT350 Overview ......................................................................... 1-1
1.1.1.
Standard ACT350 Features ................................................................................... 1-1
1.2.
Specifications ............................................................................... 1-2
1.3.
Use in Hazardous Areas................................................................. 1-4
1.4.
Inspection and Contents Checklist ................................................... 1-4
1.5.
Model Identification ....................................................................... 1-5
1.6.
Physical Dimensions ..................................................................... 1-6
1.7.
PCBs ........................................................................................... 1-8
1.7.1.
1.7.2.
Main .................................................................................................................. 1-8
PLC Interface....................................................................................................... 1-8
1.8.
Scale Bases ................................................................................. 1-8
1.9.
Versions ...................................................................................... 1-8
1.9.1.
PLC Interfaces ..................................................................................................... 1-8
1.9.1.1.
1.9.1.2.
1.9.1.3.
EtherNet/IP ...................................................................................................................... 1-9
PROFIBUS DP .................................................................................................................. 1-9
PROFINET ....................................................................................................................... 1-9
1.10.
Setup+ Configuration and Monitoring Tool ...................................... 1-9
1.11.
Display and Keyboard ................................................................. 1-10
1.11.1.
1.11.2.
Display Layout .................................................................................................. 1-10
Front Panel Keys ............................................................................................... 1-10
2
Operation .................................................................................... 2-1
2.1.
Overview...................................................................................... 2-1
2.2.
Device Menu Access...................................................................... 2-1
2.3.
Basic Functionality ........................................................................ 2-1
2.3.1.
Zero ................................................................................................................... 2-1
2.3.1.1.
2.3.1.2.
Pushbutton ...................................................................................................................... 2-2
Power Up ........................................................................................................................ 2-2
2.3.2.
2.3.3.
2.3.4.
2.3.5.
2.3.6.
2.3.7.
2.3.8.
2.3.9.
2.3.10.
2.3.11.
Tare ................................................................................................................... 2-2
Clearing Tare ...................................................................................................... 2-3
Information Recall ............................................................................................... 2-3
x10 ................................................................................................................... 2-3
Comparators ....................................................................................................... 2-3
Calibration .......................................................................................................... 2-4
Error Messages ................................................................................................... 2-4
Setup ................................................................................................................. 2-6
CalFree™ ........................................................................................................... 2-6
Setup+ ............................................................................................................... 2-6
2.4.
Display Operation ......................................................................... 2-7
METTLER TOLEDO ACT350 Transmitter User's Guide
1
Contents
2
2.5.
Keypad Operation ......................................................................... 2-7
2.6.
ACT350 Front Panel Operation ........................................................ 2-8
2.6.1.
Device Menu ....................................................................................................... 2-8
2.6.1.1.
2.6.1.2.
2.6.1.3.
2.6.1.4.
2.6.1.5.
2.6.1.6.
2.6.1.7.
2.6.1.8.
2.6.1.9.
Language Selection .......................................................................................................... 2-8
Accessing the Device Menu ............................................................................................... 2-9
Navigating the Device Menu ............................................................................................ 2-10
Numerical Data Entry ...................................................................................................... 2-11
Information Recall .......................................................................................................... 2-12
Comparators ................................................................................................................. 2-14
Calibration .................................................................................................................... 2-15
Error Message ............................................................................................................... 2-21
Setup Access ................................................................................................................. 2-21
2.6.2.
Password Security ............................................................................................. 2-21
2.7.
ACT350 Operation: Setup+........................................................... 2-21
2.7.1.
2.7.2.
Connecting to Setup+ ........................................................................................ 2-21
Scale ............................................................................................................... 2-22
2.7.2.1.
2.7.2.2.
2.7.2.3.
2.7.2.4.
Type ............................................................................................................................. 2-22
Capacity and Increment .................................................................................................. 2-23
Calibration .................................................................................................................... 2-24
Zero Options .................................................................................................................. 2-31
2.7.3.
Application ....................................................................................................... 2-32
2.7.3.1.
Comparators ................................................................................................................. 2-32
2.7.4.
Communication ................................................................................................ 2-33
2.7.4.1.
Information Recall .......................................................................................................... 2-33
2.7.5.
Terminal ........................................................................................................... 2-33
2.7.5.1.
Language ...................................................................................................................... 2-33
2.7.6.
Maintenance ..................................................................................................... 2-34
2.7.6.1.
Errors ........................................................................................................................... 2-34
3
Configuration .............................................................................. 3-1
3.1.
Overview...................................................................................... 3-1
3.2.
Weights and Measures .................................................................. 3-1
3.3.
Setup+ Settings ............................................................................ 3-2
3.4.
Saving and Loading Files ............................................................... 3-2
3.4.1.
3.4.2.
Saving New File .................................................................................................. 3-2
Loading Existing File ............................................................................................ 3-3
3.5.
Scale ........................................................................................... 3-5
3.5.1.
3.5.2.
3.5.3.
Stability .............................................................................................................. 3-5
Filter .................................................................................................................. 3-5
Reset ................................................................................................................. 3-6
3.6.
Application ................................................................................... 3-7
3.6.1.
Reset ................................................................................................................. 3-7
3.7.
Terminal ...................................................................................... 3-8
3.7.1.
3.7.2.
Device................................................................................................................ 3-8
Display .............................................................................................................. 3-8
METTLER TOLEDO ACT350 Transmitter User's Guide
30303895 | 00 | 11/2015
30303895 | 00 | 11/2015
3.7.3.
3.7.4.
3.7.5.
3.7.6.
Region ............................................................................................................... 3-9
User ................................................................................................................... 3-9
Pushbutton ....................................................................................................... 3-10
Reset ............................................................................................................... 3-10
3.8.
Communication .......................................................................... 3-11
3.8.1.
3.8.2.
RS-232 ............................................................................................................ 3-11
PLC Interface..................................................................................................... 3-11
3.8.2.1.
3.8.2.2.
Data Format .................................................................................................................. 3-11
PROFIBUS, PROFINET, EtherNet/IP .................................................................................... 3-12
3.8.3.
Reset ............................................................................................................... 3-13
3.9.
Maintenance .............................................................................. 3-13
3.9.1.
3.9.2.
3.9.3.
3.9.4.
3.9.5.
Load Cell Output ............................................................................................... 3-13
Calibration Values ............................................................................................. 3-14
Statistics........................................................................................................... 3-14
Faults ............................................................................................................... 3-15
Reset ............................................................................................................... 3-16
3.10.
Reset Configuration and Master Reset ............................................ 3-17
3.10.1.
3.10.2.
Reset Configuration ........................................................................................... 3-17
Master Reset ..................................................................................................... 3-17
4
Installation .................................................................................. 4-1
4.1.
Overview...................................................................................... 4-1
4.2.
Mounting ..................................................................................... 4-1
4.3.
Connections ................................................................................. 4-3
4.3.1.
4.3.2.
Analog Load Cell ................................................................................................. 4-3
RS-232 Serial Connection .................................................................................... 4-4
4.4.
DIP Switches ................................................................................ 4-4
5
EtherNet/IP Version ...................................................................... 5-1
5.1.
Preface ........................................................................................ 5-1
5.2.
EtherNet/IP Interface ...................................................................... 5-1
5.3.
Overview of EtherNet/IP .................................................................. 5-2
5.3.1.
5.3.2.
5.3.3.
5.3.4.
5.3.5.
Standard Automation Interface .............................................................................. 5-2
EtherNet/IP Characteristics .................................................................................... 5-2
Definition of Terms .............................................................................................. 5-2
Communications ................................................................................................. 5-4
IP Address .......................................................................................................... 5-4
5.4.
Data Formats ............................................................................... 5-4
5.4.1.1.
5.4.1.2.
Assembly Instances of Class 1 Cyclic Communications ........................................................ 5-5
Cyclic Data Format ........................................................................................................... 5-5
5.5.
Software Setup .............................................................................. 5-6
5.5.1.
EtherNet/IP and Data Format Setup Blocks ............................................................. 5-7
5.5.1.1.
5.5.1.2.
EtherNet/IP Setup.............................................................................................................. 5-7
Data Format Setup............................................................................................................ 5-8
METTLER TOLEDO ACT350 Transmitter User's Guide
3
Contents
4
5.6.
Troubleshooting ............................................................................ 5-9
5.7.
Programming Example .................................................................. 5-9
5.7.1.
Cyclic and Acyclic Sub-routines ............................................................................ 5-9
5.7.1.1.
5.7.1.2.
Cyclic Data Subroutine .................................................................................................... 5-11
Acyclic Data .................................................................................................................. 5-15
6
PROFINET .................................................................................... 6-1
6.1.
Preface ........................................................................................ 6-1
6.2.
PROFINET Interface ....................................................................... 6-1
6.3.
Overview...................................................................................... 6-2
6.4.
Standard Automation Interface ........................................................ 6-2
6.5.
PROFINET Characteristics ............................................................... 6-2
6.5.1.
6.5.2.
6.5.3.
Definition of Terms .............................................................................................. 6-3
Communications ................................................................................................. 6-4
IP Address .......................................................................................................... 6-4
6.6.
Data Formats ............................................................................... 6-4
6.6.1.1.
6.6.1.2.
Cyclic Communications .................................................................................................... 6-4
Cyclic Data Format ........................................................................................................... 6-5
6.7.
Software Setup .............................................................................. 6-6
6.7.1.
PROFINET and Data Format Setup Blocks .............................................................. 6-6
6.7.1.1.
6.7.1.2.
PROFINET Setup ............................................................................................................... 6-6
Data Format Setup............................................................................................................ 6-7
6.8.
Troubleshooting ............................................................................ 6-7
6.9.
Programming Examples ................................................................ 6-8
6.9.1.
6.9.2.
Cyclic Data Sub–routine ....................................................................................... 6-8
Acyclic Data Sub-routine .................................................................................... 6-21
7
PROFIBUS ................................................................................... 7-1
7.1.
Preface ........................................................................................ 7-1
7.2.
PROFIBUS Interface ....................................................................... 7-1
7.3.
Overview...................................................................................... 7-2
7.3.1.
Node Address ..................................................................................................... 7-2
7.4.
Standard Automation Interface ........................................................ 7-2
7.5.
Hardware Setup ............................................................................ 7-3
7.5.1.
Wiring ................................................................................................................ 7-3
7.5.1.1.
NOTES: ........................................................................................................................... 7-3
7.6.
Data Formats ............................................................................... 7-3
7.6.1.
7.6.2.
7.6.3.
Floating Point...................................................................................................... 7-4
Cyclic Communications ....................................................................................... 7-4
Cyclic Data Format .............................................................................................. 7-4
7.6.3.1.
7.6.3.2.
One Block Operation ......................................................................................................... 7-4
Two Block operation ......................................................................................................... 7-4
METTLER TOLEDO ACT350 Transmitter User's Guide
30303895 | 00 | 11/2015
30303895 | 00 | 11/2015
7.7.
Software Setup .............................................................................. 7-5
7.8.
Troubleshooting ............................................................................ 7-6
7.8.1.
Procedure ........................................................................................................... 7-6
7.9.
Programming Examples ................................................................ 7-7
7.9.1.
7.9.2.
Cyclic Data Sub-routine ........................................................................................ 7-7
Acyclic Data Sub-routine .................................................................................... 7-18
A
Parameter Values and Access....................................................... A-1
A.1.
Connection ................................................................................... A-1
A.2.
Commands .................................................................................. A-1
A.2.1.
Individual Variables ............................................................................................. A-2
A.3.
Variables List ................................................................................ A-2
B
Standard Automation Interface...................................................... B-1
B.1.
Overview...................................................................................... B-1
B.2.
General Structure .......................................................................... B-2
B.2.1.
B.2.2.
Cyclic Data ......................................................................................................... B-2
Two Types of Cyclical Blocks ................................................................................ B-2
B.2.2.1.
B.2.2.2.
Floating Point Block.......................................................................................................... B-3
Status Block .................................................................................................................... B-4
B.2.3.
Asynchronous Data (Explicit or Acyclic Messaging) ................................................ B-4
B.3.
Data Format ................................................................................. B-5
B.3.1.
1 Block Format ................................................................................................... B-5
B.3.1.1.
Cyclic Data Operation ....................................................................................................... B-5
B.3.2.
2 Block Format ................................................................................................. B-12
B.3.2.1.
B.3.2.2.
Cyclic Data Operation ..................................................................................................... B-12
Command Word (Block 2, Word 7) ................................................................................. B-19
B.4.
Byte and Word Order of Data ........................................................ B-21
B.4.1.
B.4.2.
Little Endian (Byte Swap = No / Word Swap = No) ............................................... B-21
Big Endian (Byte Swap = Yes / Word Swap = Yes) ............................................... B-21
B.5.
Floating Point Numbers ............................................................... B-22
B.6.
Test Mode .................................................................................. B-23
B.6.1.
B.6.2.
B.6.3.
B.6.4.
B.6.5.
Floating Point Test Commands for "Report" values ................................................ B-24
Floating Point Test Commands for Scale Status bits .............................................. B-24
Status Block Test Commands ............................................................................. B-24
Test Variables for Acyclic and Variable Block Test Commands ................................ B-24
Performance Test Commands ............................................................................. B-24
B.7.
Asynchronous Format .................................................................. B-25
B.7.1.1.
Direct Access Level 1 ...................................................................................................... B-25
B.7.2.
Control System Parameters for Direct Access ........................................................ B-26
B.7.2.1.
B.7.2.2.
Profibus/ProfiNet Acyclic Messages .................................................................................. B-26
EIP/ControlNet/DeviceNet Acyclic Messages ....................................................................... B-26
METTLER TOLEDO ACT350 Transmitter User's Guide
5
Contents
6
C
Cyclic Commands ........................................................................ C-1
C.1.
Floating Point Block Commands ..................................................... C-5
C.1.1.
Floating Point Report Commands .......................................................................... C-5
C.1.1.1.
Valid Command Response ................................................................................................ C-5
C.1.2.
Floating Point Write Commands ............................................................................ C-5
C.1.2.1.
Valid Command Response ................................................................................................ C-6
C.1.3.
Floating Point Operation Commands ..................................................................... C-6
C.1.3.1.
Valid Command Response ................................................................................................ C-6
C.2.
Status Block Commands ................................................................ C-7
C.2.1.
Valid Command Response ................................................................................... C-7
C.3.
Other Responses ........................................................................... C-7
C.3.1.
C.3.2.
C.3.3.
C.3.4.
C.3.5.
C.3.6.
C.3.7.
C.3.8.
Invalid Command Response ................................................................................. C-7
Unknown Command Response ............................................................................. C-7
Invalid Command data Response.......................................................................... C-8
Timeout Command Response ............................................................................... C-8
Aborted Command Response................................................................................ C-8
Step Successful Command Response .................................................................... C-9
Step Successful / Next Value Command Response .................................................. C-9
Step Failed Command Response ........................................................................... C-9
C.4.
Commands ................................................................................ C-10
C.4.1.
C.4.2.
C.4.3.
Special Commands ........................................................................................... C-10
General System Commands ............................................................................... C-10
Floating Point block Commands ......................................................................... C-11
C.4.3.1.
C.4.3.2.
C.4.3.3.
C.4.3.4.
C.4.3.5.
C.4.3.6.
C.4.3.7.
Weight Report Commands ............................................................................................... C-11
Comparator Report Commands ........................................................................................ C-11
Miscellaneous Report Command ...................................................................................... C-11
Weight Write Immediate Commands ................................................................................. C-11
Comparator Write Immediate Commands .......................................................................... C-11
Weight Operation Immediate Commands .......................................................................... C-12
Floating Point Status Bit Test Commands .......................................................................... C-12
C.4.4.
Status/Command block Commands .................................................................... C-12
C.4.4.1.
Status Commands .......................................................................................................... C-12
D
Acyclic Commands ...................................................................... D-1
D.1.
ACT350 Level 1 Variable List .......................................................... D-1
D.1.1.
D.1.2.
D.1.3.
PROFIBUS........................................................................................................... D-1
Ethernet/IP .......................................................................................................... D-3
PROFINET ........................................................................................................... D-4
D.2.
ACT350 Level 2 Variable List .......................................................... D-6
D.2.1.
D.2.2.
D.2.3.
PROFIBUS........................................................................................................... D-6
Ethernet/IP .......................................................................................................... D-7
PROFINET ........................................................................................................... D-7
E
GEO Codes .................................................................................. E-1
E.1.
Original Site Calibration ................................................................. E-1
METTLER TOLEDO ACT350 Transmitter User's Guide
30303895 | 00 | 11/2015
E.2.
30303895 | 00 | 11/2015
New Site GEO Code Adjustment ...................................................... E-1
METTLER TOLEDO ACT350 Transmitter User's Guide
7
1
Introduction
WARNING!
NOT ALL VERSIONS OF THE ACT350 ARE DESIGNED FOR USE IN HAZARDOUS (EXPLOSIVE) AREAS. REFER TO
THE DATA PLATE OF THE ACT350 TO DETERMINE IF IT IS APPROVED FOR USE IN AN AREA CLASSIFIED AS
HAZARDOUS BECAUSE OF COMBUSTIBLE OR EXPLOSIVE ATMOSPHERES.
This chapter covers
•
•
•
•
ACT350 Overview
•
•
•
•
•
•
Model Identification
Specifications
Use in Hazardous Areas
Inspection and Contents
Checklist
The ACT350 represents the latest in METTLER TOLEDO technology and is one of the
most versatile weighing transmitters available today for conventional strain gauge
weighing technology. The factory pre-configured PLC communication interface in a DIN
rail mounting scheme makes the ACT350 a perfect match for basic industrial process
weighing applications including:
• Filling
• Dosing
• Sorting
• Checkweighing
Enhance measurement or control applications with an ultra-fast A/D-D/A conversion rate
of 1200 Hz, patented TraxDSP™ digital filtering technology and a PLC update rate of
600 Hz. The ACT350 delivers fast, precise measurement data from milligrams to tons in
a single cost-effective package that easily integrates into control panel systems.
Physical Dimensions
PCBs
Scale Bases
Versions
Setup+ Configuration and
Monitoring Tool
• Display and Keyboard
The versatile ACT350 excels in controlling simple filling and dosing applications
delivering best-in-class performance for fast, precise, accurate results in fully automatic
operations. Utilize the control capabilities of the ACT350 to effectively manage project
costs.
To communicate weight data to a PLC, the ACT350 is available in three discrete versions. These
support PROFIBUS DP, PROFINET IO and EtherNet/IP PLC fieldbus types. A serial RS-232 port is
available as standard for interface with PC-based Setup+ Configuration tool.
1.1.
ACT350 Overview
1.1.1.
Standard ACT350 Features
30303895 | 00 | 11/2015
•
24 VDC (12-30 VDC) basic weighing transmitter for use in safe areas
•
DIN-mount ABS plastic enclosure with analog load cell connection
•
Front panel or Setup+™ PC Tool-based setup
•
Single analog scale connection
•
Supports a network of up to (8) 350-ohm or (20) 1000-ohm load cells; 1-3 mV/V
•
128 x 32 dot-matrix graphic OLED display with 5.6 mm (0.22 in) high weight display
METTLER TOLEDO ACT350 Transmitter User's Guide
1-1
Introduction
1.2.
•
Display, receipt and transmission of information in multiple languages
•
Comparators – (5) simple coincidence set points for comparison of weight
•
CalFree™ calibration without test weights
•
Support for the following PLC interfaces by model:
o
EtherNet/IP
o
PROFIBUS DP
o
PROFINET
Specifications
The ACT350 transmitter conforms to the specifications listed in Table 1-1.
Table 1-1: IND570 Specifications
ACT350 Specifications
1-2
Enclosure Type
35 mm DIN rail-mount plastic housing with setup interface
Dimensions (l × w × d)
110 mm × 40 mm × 100 mm
(4.3 in. × 1.6 in. × 3.9 in.)
Shipping Weight
Transmitter/Product package
PROFIBUS DP version
EtherNet/IP and PROFINET versions
Environmental Protection
IP20, Type 1
Legal for Trade Environment
The transmitter will maintain legal for trade approved performance in the
range −10° to 40° C (14° to 104° F) at 10% to 90% relative humidity
non-condensing
Operating Environment
Operating temperatures range from −10° to 50° C (14° to 122° F) at 10%
to 90% relative humidity non-condensing
Storage Environment
The transmitter can be stored at temperatures from −40° to 60° C (-40° to
140° F) at 10% to 90% relative humidity non-condensing
Hazardous Areas
Not all versions of the ACT350 can be operated in areas classified as
Hazardous by the National Electrical Code (NEC) or in Zone 2/22 areas as
classified by ATEX and IECEx because of the combustible or explosive
atmospheres in those areas. Contact an authorized METTLER TOLEDO
representative for information about the ACT350xx model for hazardous
applications.
DC Input Power
Operates at 24 VDC nominal, -50% - +25%
Only use recommended 12-30 VDC Power Supply approved as NEC Class
2 or rated as Limited Power per IEC60950-1.
Power Consumption
Refer to Table 1-2
Scale Types & Update Rates
Analog load cells, up to (8) 350Ω or (20) 1000Ω load cells; 1 to 3 mV/V
Number of Scales
1
METTLER TOLEDO ACT350 Transmitter User's Guide
225g/482g
222g/479g
30303895 | 00 | 11/2015
ACT350 Specifications
Number of Scale Ranges
1
Analog Load Cell Excitation
Voltage
5 VDC
Minimum Sensitivity / Approved 0.1 microvolts / 0.5 microvolts
Calibration Types
Independent Zero and Span; 5-point linearization; Step; CalFree; local
gravity compensation for mobile scales
Internal and Interface Update
Rates (max)
Internal Analog/Digital: 1200 Hz
PLC cyclic and acyclic data: 600 Hz
Keypad
4 keys (Up/Down/Left/Enter); 0.9mm polyester overlay (PET) with
0.178mm thick polycarbonate display lens
Display Type
Green OLED including weight display, weight units, gross/net indication
and graphic symbols for motion, center of zero
Character Height
5.6 mm / 0.22 in
Displayed Resolution
Maximum displayed resolution 100,000 divisions
Status LEDs
4 – Scale (SCL), Power (PWR), Network (NW), Device (DEV)
Target Comparators
5
Communication
Standard Interfaces
Serial Port: RS-232, 300 to 115,200 baud for Service
PLC Interfaces
®
A single interface supported: EtherNet/IP, PROFIBUS DP or PROFINET
Approvals
®
Weights and Measures
USA: NTEP; Class III 10,000d; in process
Canada: Class III 10,000d; in process
Europe: OIML R76 Class III 6,000e; in process
Product Safety
UL, cUL, CE
Table 1-2: ACT350 Analog Basic and Premium Power Consumption (DC Source)
1-350Ω
4-350Ω
8-350Ω
Load Cell
Load Cell
Load Cell
Input Voltage
I (mA)
P (W)
I (mA)
P (W)
I (mA)
P (W)
PROFIBUS DP
Ethernet/IP and
PROFINET
320
3.84
342
4.10
370
4.44
367
4.40
395
4.74
426
5.11
160
3.84
173
4.15
187
4.49
184
4.42
195
4.68
212
5.09
12VDC
24 VDC
PROFIBUS DP
Ethernet/IP and
PROFINET
30303895 | 00 | 11/2015
METTLER TOLEDO ACT350 Transmitter User's Guide
1-3
Introduction
Input Voltage
30 VDC (max)
PROFIBUS DP
Ethernet/IP and
PROFINET
1.3.
1-350Ω
4-350Ω
8-350Ω
Load Cell
Load Cell
Load Cell
I (mA)
P (W)
I (mA)
P (W)
I (mA)
P (W)
131
3.93
141
4.23
154
4.62
152
4.56
160
4.8
171
5.13
Use in Hazardous Areas
Standard versions of ACT350 transmitters are not certified for use within hazardous (explosive)
areas. Specially marked transmitters (model ACT350xx) are agency certified and carry FM, ATEX
and IECEx approvals for use in hazardous areas classified as Division 2 or Zone 2/22.
WARNING
DO NOT USE THE STANDARD ACT350 TRANSMITTERS IN AREAS CLASSIFIED AS HAZARDOUS
BECAUSE OF COMBUSTIBLE OR EXPLOSIVE ATMOSPHERES. SPECIAL ACT350xx MODELS ARE
AVAILABLE FOR THESE APPLICATIONS. CONTACT AN AUTHORIZED METTLER TOLEDO
REPRESENTATIVE FOR INFORMATION ABOUT HAZARDOUS AREA APPLICATIONS.
1.4.
Inspection and Contents Checklist
Verify the contents and inspect the package immediately upon delivery. If the shipping container is
damaged, check for internal damage and file a freight claim with the carrier if necessary. If the
container is not damaged, remove the ACT350 transmitter from its protective package, noting how it
was packed, and inspect each component for damage.
If it is necessary to ship the transmitter, it is best to use the original shipping container. The ACT350
transmitter must be packed correctly to ensure its safe transportation.
The package should include:
•
ACT350 transmitter
•
•
Bag of parts for installation. May include ferrites, connectors, load cell connector protection
sleeve etc.
Safety warnings in multiple languages
All relevant documentation, software, fieldbus files and sample code can be downloaded at
www.mt.com/ind-act350-downloads.
1-4
METTLER TOLEDO ACT350 Transmitter User's Guide
30303895 | 00 | 11/2015
1.5.
Model Identification
The ACT350 model number is located on the data plate on the back of the transmitter along with
the serial number. Refer to Figure 1-1 to verify the ACT350 that was ordered.
Figure 1-1: ACT350 Model Identification Numbers
30303895 | 00 | 11/2015
METTLER TOLEDO ACT350 Transmitter User's Guide
1-5
Introduction
1.6.
Physical Dimensions
The physical dimensions of the DIN rail-mount ACT350 enclosure are shown in Figure 1-2 in
millimeters and [inches].
Figure 1-2: ACT350 Panel Mount Enclosure Dimensions
1-6
METTLER TOLEDO ACT350 Transmitter User's Guide
30303895 | 00 | 11/2015
Note: Keep A and B surfaces free for heat dissipation
Figure 1-3: ACT350 PROFIBUS DIN Mount Overall Dimensions, in mm
Figure 1-4: ACT350 EtherNet/IP and PROFINET DIN Mount Overall Dimensions, in mm
30303895 | 00 | 11/2015
METTLER TOLEDO ACT350 Transmitter User's Guide
1-7
Introduction
1.7.
PCBs
1.7.1.
Main
The ACT350 transmitter’s main printed circuit board (PCB) provides the interface for analog
scales/load cell(s).
The main board also contains the power input connection for the DC supply and internal bus
connectors to the communication interface board for the PLC.
1.7.2.
PLC Interface
The ACT350 transmitter has a separate PCB that supports communication with the PLC. This
communication PCB is electrically connected to the device's main PCB via bus connectors.
The PLC interface PCB supports a serial port for connection to a PC for configuration, monitoring,
system backup, restore and firmware updating purposes. The single standard serial port provides
bidirectional RS-232 communication interface with Setup+ PC-based configuration and InSite CSL
Service tool.
The PCB also supports interface to the OLED display, front panel keypad and a 2-position DIP
switch for Legal-for-trade weights and measures setting and resetting parameters.
Four LEDs are provided to indicate the operational status of the transmitter.
The ACT350 ships from the factory as a sealed unit. The ACT350 is not field-serviceable.
1.8.
Scale Bases
The ACT350 main PCB includes an analog load cell interface. The transmitter can drive up to eight
350-ohm, or twenty 1000-ohm, 1, 2 or 3mV/V analog load cells.
1.9.
Versions
The ACT350 is available in three Programmable Logic Control (PLC) interface versions, including:
PROFIBUS DP
1.9.1.
EtherNet/IP™
PROFINET
PLC Interfaces
The ACT350 comes factory-configured with PLC interface options including PROFIBUS DP,
EtherNet/IP and PROFINET IO. Each product version is specific to the PLC interface and cannot be
configured to a different fieldbus type.
Additional details about each of the PLC interfaces, together with programming guidance, can be
found in the chapters 5, 6 and 7 in this document. Sample codes and device description files can
be found at www.mt.com/ind-act350-downloads.
1-8
METTLER TOLEDO ACT350 Transmitter User's Guide
30303895 | 00 | 11/2015
1.9.1.1.
EtherNet/IP
EtherNet / IP utilizes commercial, off-the-shelf EtherNet hardware (for example, switches and
routers). It uses the proven Control and Information Protocol (CIP) to provide control, configuration
and data collection capability.
The internally installed EtherNet/IP PCB module enables the ACT350 transmitter to communicate to
EtherNet/IP Programmable Logic Controllers (PLCs) through direct connection to the EtherNet/IP
network at either 10 or 100 MBPS speed. Both implicit messaging (cyclic real-time I/O messaging)
and explicit messaging (acyclic message exchange) are supported by the ACT350 software.
1.9.1.2.
PROFIBUS DP
The transmitter communicates to a PROFIBUS-DP master according to DIN 19 245. PROFIBUS is
an open, RS-485 digital communication system with a wide range of applications, particularly in
the fields of factory and process automation. PROFIBUS is designed for use in fast, time-critical
applications. Additional specifications can be found in PROFIBUS International documents.
The PROFIBUS version of the ACT350 transmitter enables cyclic and acyclic data exchange with
programmable logic controllers such as the Siemens S7 series. A maximum of 126 devices
(primaries or secondaries) can be connected to a bus.
1.9.1.3.
PROFINET
PROFINET is an open industrial networking standard that was developed by Siemens as an Ethernet
replacement for its widely popular PROFIBUS Network. PROFINET utilizes commercial, off-the-shelf
EtherNet hardware (for example, switches and routers) and is fully compatible with the Ethernet
TCP/IP protocol suite.
The ACT350 PROFINET version supports both cyclic messaging and acyclic messaging.
1.10.
Setup+ Configuration and Monitoring Tool
Figure 1-5: Setup+ Splash Screen
Setup+ PC tool is available to users of ACT350 transmitters. The ACT350 transmitter can connect to
a PC running Setup+ via the standard RS-232 serial port to provide the following functions:
30303895 | 00 | 11/2015
•
Saving transmitter configuration to a local PC
•
Loading a saved configuration to other transmitters performing similar applications
•
Restoring to a ‘last known good state’ for service purposes
METTLER TOLEDO ACT350 Transmitter User's Guide
1-9
1.11.
Display and Keyboard
Introduction
The ACT350 transmitter has an organic LED (OLED) display, 128 × 32 dot matrix graphic type
display. An example of the ACT350 front panel is shown in Figure 1-6.
Display
UP key
DOWN key
LEFT key
ENTER key
Power
connector
LED indicators
Analog scale
interface
connector
PLC interface
connector
(PROFIBUS DP
shown)
Figure 1-6: ACT350 Front Panel Layout
1.11.1.
Display Layout
The display is reserved for scale weight, units, Net/Gross indicator and error messages.
1.11.2.
Front Panel Keys
Four dedicated function keys are located on the front panel to support manual setup configuration
purpose. These provide the interface to navigate setup menu hierarchy, data entry, and to make
setup selections within data entry and drop down selection boxes.
The transmitter’s 4 navigation keys enable the technician to navigate through setup options in the
menu tree and within setup screens to enter numeric data and make selections. The keys are
located under the display window on the transmitter's front panel. Refer to Chapter 2, Operation, for
additional details about the entry of numeric data.
1-10
METTLER TOLEDO ACT350 Transmitter User's Guide
30303895 | 00 | 11/2015
2
Operation
2.1.
Overview
This chapter provides information about the basic functionality of the ACT350 Transmitter
including display operation, keypad functions and menu navigation.
This chapter covers
•
•
•
•
•
•
Overview
Device Menu Access
Operation of the transmitter depends on functions and parameters that are configured in setup,
as described in Chapter 3, Configuration. Navigation and basic functionality are covered in the
following sections.
Basic Functionality
Display Operation
Keypad Operation
Device Menu
2.2.
Device Menu Access
Access to ACT350 device menu can be accomplished from the device's front panel or via the PCbased Setup+™ Configuration Tool. Device menus can be accessed from the front panel using a
long key press of the ENTER
key. Not all menus can be accessed from the device front panel.
2.3.
Basic Functionality
This section provides information about the ACT350’s basic functionality. Functions addressed in
this section include:
•
Zero
•
x10
•
Comparators
•
Tare
•
Information Recall
•
Calibration
•
Clearing Tare
•
Error Messages
•
CalFree
Refer to Chapter 3, Configuration, for further information about programming all the functionality
described in this section.
2.3.1.
Zero
The Zero function is used to set or reset the initial zero reference point of the transmitter. There are
two types of zero setting modes:
30303895 | 00 | 11/2015
•
Pushbutton
•
Power Up
METTLER TOLEDO ACT350 Transmitter User's Guide
2-1
2.3.1.1.
Pushbutton
Operation
The pushbutton zero function can be accomplished by a short press of the ENTER
function key or by using a PLC command.
scale
The Pushbutton Zero range selections include Disabled, 2% [default] or 20% plus or minus from
the calibrated zero point. A change to the default setting is done via the PC-based Setup+
Configuration Tool.
If the current scale weight is outside the zero range when a pushbutton zero is commanded, the
transmitter will display a message:
Figure 2-1: Pushbutton Zero Failure Message
Remote initiation of the semi-automatic Zero command is possible via a command initiated by the
PLC interface.
2.3.1.2.
Power Up
The Power Up mode setting determines if at power up, the transmitter will restart with the most
recent zero reference point it had before power down or if it will reset to the calibrated zero
reference.
The selections include Reset [default] and Restart.
2.3.1.2.1.
Reset
With the setting on Reset, the last zero calibration value will be used as the zero reference point.
The Power Up Zero capture range selections include Disabled [default], 2% or 10% plus or minus.
If the range setting is enabled, the Power Up Zero is applied only when the weight reading on the
scale is within the selected range around the originally calibrated zero reference. For example, if the
range setting for Power Up Zero is set at +/- 2%, Power Up Zero will only occur when the weight
reading on the scale is within +/- 2% of scale capacity above the original calibrated zero reference.
If the weight on the scale is outside of the zero range, the display will indicate EEE until the weight
is adjusted to be within this range and zero is captured.
2.3.1.2.2.
Restart
A setting of Restart enables the transmitter to reuse the most recent zero reference weight after a
power cycle so it returns to the same, previously-displayed gross weight value.
The Power Up Zero setting is configured using the PC-based Setup+ Configuration Tool.
2.3.2.
Tare
Tare is the weight of an empty container. The tare value is subtracted from the gross weight
measurement, providing the computation of the net weight (material without the container). The tare
function can also be used to track the net amount of material being added to or removed from a
2-2
METTLER TOLEDO ACT350 Transmitter User's Guide
30303895 | 00 | 11/2015
vessel or container. In the second case, the weight of the material in the container is included with
the tare weight of the container and the display then reflects the net amount being added to or
removed from the vessel.
Tare is captured by PLC command.
2.3.3.
Clearing Tare
Tare is cleared by PLC command.
2.3.4.
Information Recall
A limited number of data fields are made available for easy recall on the transmitter display. These
fields include data such as model, serial number, unit firmware version, PLC fieldbus type, device
name, IP address and MAC address.
This data is accessed by pressing the ENTER key
accessed and the
icon is displayed on screen.
2.3.5.
when the transmitter’s device menu has been
x10
NOTE
THE x10 DISPLAY RESOLUTION SETTING IS THE ONLY PARAMETER THAT CANNOT BE CONFIGURED USING SETUP+.
THE x10 DISPLAY IS A DIAGNOSTIC TOOL THAT AFFECTS THE DISPLAY TEMPORARILY.
The weight display can be set to a finer weight resolution using the transmitter’s device menu.
When performing diagnostic work on a weighing system, it is sometimes useful to expand the
weight display resolution by 10 so that a finer weight increment can be seen. The function is
intended for diagnostic purposes only. The transmitter should not be used in the x10 expanded
mode for normal operation. The Data Ok bit is set to zero when in x10 display mode to indicate that
the ACT350 is not in normal operating mode. The PLC should continuously monitor the Data Ok bit
in the ACT350 communication to determine the validity of data received by the PLC.
This function can be enabled by pressing the ENTER key
when the transmitter’s device menu
has been accessed and the
icon is displayed on screen:
Figure 2-2: x10 Indication
A press of the LEFT
the weighing screen.
2.3.6.
key restores the normal weight value resolution and returns the display to
Comparators
Comparators are simple configurable targets. They are controlled by coincidence with the scale
weight. The device supports a total of five comparators. One, two or all five comparators may be
30303895 | 00 | 11/2015
METTLER TOLEDO ACT350 Transmitter User's Guide
2-3
used. The limit of each Comparator may be modified by accessing the Comparator menu in the
setup menu.
Operation
Access to the Comparator menu using the device's front panel is accomplished by pressing the
ENTER key
when the transmitter’s device menu has been accessed and the
icon is
displayed on the device.
The Comparator menu can also be accessed using the PC-based Setup+ Configuration Tool.
Comparator values are limited to 7 digits, and can be written to the device or read from it by the
PLC.
2.3.7.
Calibration
Calibration is the process of adjusting the display of the transmitter so that when the scale is empty,
the display shows zero gross weight and, with a specific amount of weight on the scale, shows an
accurate weight value.
The ACT350 transmitter calibration menu enables entry of a geo code adjustment value, setting
selection for linearity adjustment – none [default], three, four or five point, perform traditional zero
calibration and three different types of span calibration:
•
Traditional span calibration - using test weights
•
Step Adjust Calibration - using a build-up or substitution method of calibration (for large
vessels where only a portion of the required test weights can be placed on the scale)
•
CalFree calibration – once certain load cell criteria have been entered manually, the transmitter
will automatically calculate the span; no test weights are required
Access to the Calibration menu using the device's front panel is accomplished with a key press of
the ENTER key
when the
icon is displayed on the device. The Calibration menu can also be
accessed using the PC-based Setup+ Configuration Tool.
2.3.8.
Error Messages
Error messages related to the possible error conditions are displayed on the device. Error messages
are accessed by pressing the ENTER key
when the transmitter’s device menu has been
accessed and the
icon is displayed on the device menu. Table 2-1 lists and explains errors
that may be observed.
Table 2-1: ACT350 Faults
Error
002
ACT350 Display
Local calib. in process
or
Setup+ calib. in process
005
006
2-4
NW Module init.fail
NW connection disconnected
METTLER TOLEDO ACT350 Transmitter User's Guide
Description
Action
Calibration in process.
Distinguishes between
calibration performed in the
ACT350, and calibration
performed from Setup+
Wait for calibration to finish
SAI initialize fail
Cycle power; call service if
issue persists
Lose connection to network
Check cable or connector
30303895 | 00 | 11/2015
Error
009
010
011
ACT350 Display
Cycle power; call service if
issue persists
Calib. err
Calibration block data error;
block data is lost
Perform master reset
Re-calibrate
Scale err
Scale block data error; block
data is lost
Perform master reset
Perform setup for scale block
Term. err
Transmitter block data error;
block data is lost
Perform master reset
Perform setup for transmitter
block
APP. err
Application block data error;
block data is lost
Perform master reset
Perform setup for application
block
NW. err
Communication block data
error; block data is lost
Perform master reset
Perform setup for
communication block
Maint. err
Statistics block data error;
block data is lost
Perform master reset
Perform setup for maintenance
block
Lost analog signal; abnormal
functioning of scale
Call service
Scale in motion when Zero
attempted
Zero when scale is stable
Scale in net mode when Zero
attempted
Clear tare before zeroing
Zero failed out of range
Weight out of Zero range
Unload scale and zero
Zero failed Zero disabled
Zero attempted when function
disabled in setup
Enable Zero function in Setup
Tare failed as scale is in
motion
Tare when scale is stable
Preset tare value not in display
increment size
The preset tare value must be
rounded to the same increment
Tare value too small
The preset tare value must be
minimum of 1 display
increment
Power-up zero not captured;
Zero not captured after power
cycle (with Zero capture
enabled) then tare was
attempted
Disable zero capture at powerup or unload scale and powerup again, then tare
Tare was attempted while scale
was over capacity
Remove weight and tare within
weighing range
013
014
015
018
019
020
021
022
027
Analog system A/D fail
Zero failed Motion
Zero failed net mode
Tare failed Motion
Tare failed Not rounded value
028
Tare failed Value too small
029
Tare failed Zero not captured
030
30303895 | 00 | 11/2015
Action
Hardware information error
Board info. err
012
016
Description
Tare Failed, Scale Over
capacity
METTLER TOLEDO ACT350 Transmitter User's Guide
2-5
Error
Operation
031
ACT350 Display
Tare failed Negative value
035
2.3.9.
Description
Analog saturation
Action
Tare value under zero
The preset tare value must be
positive
A/D converter in overload
Reprogram Scale Capacity
Setup
To access setup, press the ENTER key
when the transmitter’s device menu has been accessed
and the
icon is displayed on the device menu.
2.3.10.
CalFree™
The ACT350 transmitter provides a method to calibrate a scale without using test weights. This is
based on manual entry of capacity and performance data from the load cell or load cell platform.
This method of calibration can be used for initial check-out and testing of systems or when a large
structure is used as the weighing vessel and it is not possible to apply test weights to the structure.
METTLER TOLEDO highly recommends that test weights be used whenever possible as this provides
the most accurate method of calibration.
The Rated Cell Output and Cell Capacity values cannot be zero, and are limited to 7 digits.
Scale calibration using CalFree wil not be accurate when using Zener Diode barriers (such as
METTLER TOLEDO ISB05 and ISB05x) between the transmitter and the scale. DO NOT use CalFree
when barriers are installed.
2.3.11.
Setup+
All features of the ACT350 device menu (except x10 expanded resolution) can be viewed and
configured using the PC-based Setup+ Tool. This includes access to the PLC communication and
maintenance sub-menus and the save/load feature, for saving and restoring transmitter settings.
Refer to section 2.7 for further details.
Figure 2-3: Setup+ Home Screen
2-6
METTLER TOLEDO ACT350 Transmitter User's Guide
30303895 | 00 | 11/2015
2.4.
Display Operation
When the transmitter is in weighing mode, the display is used to indicate the weight value and
other types of information related to the weight. The other information provided includes:
•
Weight unit (lb, kg, g)
•
Motion / no-motion condition
•
Center of zero
•
Gross or net mode
An example of the display format for the weighing mode data is shown in Figure 2-4.
Unit of measure
indication
Weight display
Center of Zero
indication
Gross mode
indication
Figure 2-4: Display in Weighing Mode
When accessing the device menu, the display is also used to display icons, parameters and
settings. This operation is explained in the following sections and a display of the Comparator value
entry is shown in Figure 2-5.
Icon for
Comparator
Bar indicates
more menu
selections above
and below
Figure 2-5: Display in Operator Entry Mode, Comparator Icon Showing
Focus is indicated by reverse video.
Figure 2-6: Reverse Video Indicating Focus – Parameter Label (left) and Parameter Value (right)
2.5.
Keypad Operation
The front panel keys are used to navigate within the ACT350 device menu and also configure the
transmitter as described later in this chapter.
Figure 2-7 shows the four keys on the front panel of the IND331. The IND131 is equipped with
smaller versions of the same keys. Table 2-2 shows the function of each of the four keys during
normal operation.
30303895 | 00 | 11/2015
METTLER TOLEDO ACT350 Transmitter User's Guide
2-7
Operation
UP
DOWN
LEFT
ENTER
Figure 2-7: ACT350 Keys
Table 2-2: Keypad Functions – Normal Operation
UP
Press the UP key to scroll within the device menu and sub-menus. The UP key is also
used for incrementing numerals in the numeric data entry field.
DOWN Press the DOWN key to scroll within the device menu and sub-menus. The DOWN key is
also used for decrementing numerals in the numeric data entry field.
LEFT
Press the LEFT key to navigate up one step on the device menu tree. The LEFT key is also
used to scroll to the numeral to the left in a data entry field. With the left most numeric
character highlighted the next key press will wrap around to the right most numeral.
ENTER Press the ENTER key for 3 seconds to access the device menu. A press of the ENTER key
will make a selection from the device menu and sub-menus. When in a data entry field
press the ENTER key to accept the numeric value entered.
When the display is in weighing mode, briefly pressing the ENTER key will execute the
zero operation if the scale weight is within the Pushbutton zero range specified in Setup+.
The Zero function will not operate when the scale is in motion. If the ENTER key is pressed while the
scale is in motion, the command will be retained for 3 seconds while the transmitter waits for nomotion. If a no-motion condition is not detected within the 3 seconds, the request is cancelled and
discarded.
2.6.
ACT350 Front Panel Operation
Many functions can be performed by accessing the transmitter’s device menu from the front panel.
These include information recall, x10 function, comparator value entry, the display of error
messages, and access to calibration and setup. An explanation of how to access these functions
follows.
2.6.1.
Device Menu
2.6.1.1.
Language Selection
The ACT350 supports a device menu in English [default] and in Chinese. Refer to Table 2-3 and
Figure 2-8 for information on how to set this parameter.
2-8
METTLER TOLEDO ACT350 Transmitter User's Guide
30303895 | 00 | 11/2015
2.6.1.2.
Accessing the Device Menu
To access the device menu from the front panel, the ENTER key must be pressed and held for
approximately 2 seconds. At the end of the 2 seconds, the display will change from showing the
normal weight display to showing the Information recall
icon. Press the UP
or DOWN
keys on the front panel to display icons for the various functions listed in Table 2-3.
Table 2-3: Device Menu Icons
Information
Recall
Recall mode for most transmitter information fields.
Resolution
Temporary expanded weight display resolution for diagnostic purposes
Comparators Access to the limit value for all comparators.
Calibration
Error
Message
Access to list of current error messages
Language
Selects between English and Chinese
Setup
30303895 | 00 | 11/2015
Access to calibration menu including zero and span adjustment (in nonapproved mode only).
Access to all setup parameters for the transmitter.
METTLER TOLEDO ACT350 Transmitter User's Guide
2-9
2.6.1.3.
Navigating the Device Menu
Operation
The key functions used to navigate the device menu are the same as those indicated in Figure 2-7.
To access the device menu, press and hold the ENTER key for 2 seconds. Once the menu is
displayed, it can be navigated, parameters viewed and changes made using the four keypad keys.
Figure 2-8 shows an overview of the device menu.
Figure 2-8: Device Menu Overview
2-10
METTLER TOLEDO ACT350 Transmitter User's Guide
30303895 | 00 | 11/2015
2.6.1.4.
Numerical Data Entry
An engineer or technician may be required to change a value in the device menu such as a
comparator value for instance. The four keys on the keypad are also used to make selections and
for data entry.
When one of the operator menu icons is selected (by pressing ENTER), a list of parameters
associated with that function will be shown. Two items will be shown on the display at a time. One
of the items will be in “focus” indicated by reverse video.
Figure 2-9 shows an example of how to access and modify the value of a parameter. The currently
selected item (in focus) is indicated by reverse video.
Figure 2-9: Numerical Data Entry Example
30303895 | 00 | 11/2015
METTLER TOLEDO ACT350 Transmitter User's Guide
2-11
Operation
With the parameter’s value in focus, the arrow keys are used to select a digit and increase or
decrease it. The buttons behave as indicated in Figure 2-10.
Figure 2-10: Numerical Data Entry: Setting a Value
Once focus is in a value field, as in Figure 2-10, repeated presses of the UP, DOWN or LEFT key
will cycle back to the beginning, so that if the LEFT key is pressed when focus is in the left-most
position, focus returns to the right-most position. In the case of the UP and DOWN keys, the
numerical value will cycle through numerical values and the decimal point as follows:
0>1>2>3>4>5>6>7>8>9>.0>1>…
0>.>9>8>7>6>5>4>3>2>1>.>…
When the value has been accepted with the press of the ENTER key and the focus moves to the
parameter description, the LEFT key can be pressed to exit to the next higher level of the menu.
Pressing the LEFT multiple times will exit the device menu.
In the flow charts that follow, steps that involve value editing are indicated by the arrow keys:
2.6.1.5.
Information Recall
Information recall is the first function displayed in the device menu. Once the Information Recall
icon
appears, press the ENTER key to recall specific information about the transmitter. In this
menu, items are viewed in sequence by pressing the DOWN or ENTER keys, or the UP key. Figure
2-11 shows the elements of the Information Recall menu in the sequence in which they occur. Note
that some items may not appear, depending on the configuration of the transmitter.
2-12
METTLER TOLEDO ACT350 Transmitter User's Guide
30303895 | 00 | 11/2015
Figure 2-11: Information Recall Menu
30303895 | 00 | 11/2015
METTLER TOLEDO ACT350 Transmitter User's Guide
2-13
Operation
2.6.1.6.
Comparators
2.6.1.6.1.
Setting Comparators
When using the front panel, once the Comparator icon
the limit setting screen for the first comparator.
appears press the ENTER key to access
Figure 2-12: Setting Comparator Values
If the operator is a single value, only one limit value can be set for the comparator, and pressing
the PRINT key again returns to the list of comparators. If the operator is a range, then the Limit
screen is followed by the High Limit screen, from which the PRINT key exits back to the list of
comparators. To edit parameters other than limits, Comparator configuration must be accessed in
setup. Refer to the Numerical Data Entry section on page 2-11 for the method used to modify
numerical values.
2-14
METTLER TOLEDO ACT350 Transmitter User's Guide
30303895 | 00 | 11/2015
2.6.1.7.
Calibration
With the Calibration icon
in view, press the ENTER key to access the calibration procedures. The
following four sections and flow charts describe calibration options and procedures. Refer to section
2.6.1.4, above, for the method used to modify numerical values.
Figure 2-13: Calibration Menu – Overview
2.6.1.7.1.
Setting Geo Code
The Geo code, which sets the appropriate adjustment value for the current geographical location, is
selected here. Geo codes are numbered 0–31. See Figure 2-13 for Geo code setting using the
transmitter’s front panel buttons, and refer to Appendix E, Geo Codes to find the appropriate Geo
Code for the installation location.
2.6.1.7.2.
Setting Linearity
To set the Linearity Adjustment value, see Figure 2-13. Choose the number of linearity points from
the selection box. Options are
None [default], 3 point, 4 point, 5 point
30303895 | 00 | 11/2015
METTLER TOLEDO ACT350 Transmitter User's Guide
2-15
Points are distributed as follows:
Operation
None
2.6.1.7.3.
Linearity is disabled
3
Zero, midpoint and highpoint
4
Zero, lowpoint, midpoint and highpoint
5
Zero, lowpoint, midpoint, mid-highpoint, highpoint
Zero Calibration
Scale zero is set simply by emptying the scale and running the “Set Zero” calibration routine, as
shown in Figure 2-14.
Figure 2-14: Zero Calibration
If the transmitter detects scale motion during the calibration process, it will retry the start of
calibration several times and then proceed, displaying a motion indication. In this case, when
calibration is complete the transmitter will present two options – accept or reject the value.
Figure 2-15: Zero Calibration with Motion
2-16
METTLER TOLEDO ACT350 Transmitter User's Guide
30303895 | 00 | 11/2015
2.6.1.7.4.
Span Calibration
The scale’s span calibration can be determined either with or without a linearity adjustment. With
linearity disabled, a single reference point is used to calibrate the scale. This is the normal method
of span calibration. In Figure 2-16, the transmitter is configured with three-point linearity – low, mid
and high. The low point is set during zero calibration, the mid and high points during this
procedure.
Figure 2-16: Span Calibration
If linearity is enabled, additional mid-range weight reference points are added to the adjustment
procedure. Linearity can be enabled or disabled in the Calibration branch of the device menu. Refer
to the Numerical Data Entry section on page 2-11 for the method used to modify numerical values.
30303895 | 00 | 11/2015
METTLER TOLEDO ACT350 Transmitter User's Guide
2-17
2.6.1.7.5.
Step Adjust
Operation
Step adjustment is an iterative process in which a build-up or material substitution method of
calibration is used to calibrate the span. Each step calibrates a portion of the full span.
This method is typically used with large vessels where only a portion of the required calibration test
weights can be placed on the scale at one time. Figure 2-17 shows the logic of the procedure using
a simple, two-step example. When sufficient steps have been calibrated, pressing the LEFT button
returns the view to the calibration menu.
First, a test load is defined by entering its weight
Confirm the value entry by pressing ENTER
The ACT350 prompts for the addition of the test load
Press ENTER to start the first step
The ACT350 indicates its progress
Once the first step is calibrated, the ACT350 sets a
temporary zero point, and prompts for the removal of the
test load. A live weight display indicates that the scale
has been cleared
Press ENTER to confirm the scale is empty
The ACT350 now prompts to add the test load again
The live weight indicates that the test load is on the scale
Press ENTER to start the second step
The ACT350 indicates its progress
Press LEFT to complete calibration and exit the procedure
The ACT350 indicates that the calibration has succeeded
Press either LEFT or ENTER to return to the calibration
menu
Figure 2-17: Step Adjustment
2-18
METTLER TOLEDO ACT350 Transmitter User's Guide
30303895 | 00 | 11/2015
2.6.1.7.6.
CalFree™
CalFree allows the scale to be calibrated without the use of test weights. It requires the total load
cell capacity, unit and output in mV/V to be entered. The system then calculates correct calibration
for the scale. Figure 2-18 provides a visual representation of the CalFree calibration procedure.
Notes on Load Cell Capacity and Rated Cell Output
•
For load cell capacity, enter the sum of all load cell capacities. For example, for three 50t load
cells, enter 150,000 kg.
•
For systems with passive dummy load cells, enter the value as if all legs have live load cells.
For example, for a system with two 50t live load cells and two passive supports, enter
200,000.
•
For Rated Cell Output, enter the sensitivity of each live load cell in mV/V – for example, 2.0000.
Do not sum the sensitivity values of the load cells.
NOTE
SCALE CALIBRATION USING CALFREE WIL NOT BE ACCURATE WHEN USING ZENER DIODE BARRIERS (SUCH AS
METTLER TOLEDO ISB05 AND ISB05X) BETWEEN THE TRANSMITTER AND THE SCALE. DO NOT USE CALFREE WHEN
BARRIERS ARE INSTALLED.
30303895 | 00 | 11/2015
METTLER TOLEDO ACT350 Transmitter User's Guide
2-19
Operation
Figure 2-18: CalFree
2-20
METTLER TOLEDO ACT350 Transmitter User's Guide
30303895 | 00 | 11/2015
2.6.1.8.
Error Message
With the Errors icon
in view, press the ENTER key to access a listing of current error messages.
For a list of errors that may appear here, refer to Chapter 3, Configuration.
2.6.1.9.
Setup Access
NOTE
THE SETUP+ CONFIGURATION TOOL PROVIDES ACCESS TO A FULL RANGE OF CONFIGURATION OPTIONS FOR THE
ACT350. SOME OF THESE PARAMETERS CANNOT BE VIEWED ON OR CHANGED FROM THE FRONT PANEL OF THE
TRANSMITTER.
The last icon displayed in the device menu from the front panel is SETUP
, where many of the
transmitter’s programming parameters can be viewed and modified. Details of the setup mode, and
the features only accessible using Setup+, are described in Chapter 3, Configuration.
It is not intended that operators enter the setup mode. After a weighing system is installed and is
operational, it should not be necessary for an operator to access setup.
2.6.2.
Password Security
Note that a security password can be enabled in setup from the PC-based Setup+ Configuration
Tool. When a password is set, it must be entered in order to access setup. This protects the setup
parameters from inadvertent changes.
Figure 2-19: Password Entry Screen
2.7.
ACT350 Operation: Setup+
This section shows the Setup+ features and functions that correspond to those accessible from the
transmitter’s Device Menu (Table 2-3, Figure 2-8).Other parameters, accessible only through
Setup+, are described in Chapter 3, Configuration. The screens shown below the follow the
sequence in which they appear in Setup+, which does not always match the order in which they
are visible in the transmitter.
2.7.1.
Connecting to Setup+
The Setup+ software must be configured to communicate correctly when it is connected to an
ACT350. First, the Connection Settings must be configured. Click on the Settings icon in the Setup+
toolbar.
30303895 | 00 | 11/2015
METTLER TOLEDO ACT350 Transmitter User's Guide
2-21
Operation
Figure 2-20: Setup+ Toolbar, Settings and Connect Icons
Figure 2-21 shows the settings configured. The COM port number will differ from this example.
Figure 2-21: Setup+ Communication Settings
With the settings established, matching the settings configured in the ACT350 (refer to Chapter 3,
Configuration) click on the Connect icon to start communicating with the transmitter.
2.7.2.
Scale
2.7.2.1.
Type
The scale’s name, type and approval (if any) is configured at Scale | Type. Approval options are
shown in Figure 2-23.
Figure 2-22: Scale Type and Approval
2-22
METTLER TOLEDO ACT350 Transmitter User's Guide
30303895 | 00 | 11/2015
Figure 2-23: Approval Options
2.7.2.2.
Capacity and Increment
Capacity and Increment are set at Scale | Capacity & Increment.
Figure 2-24: Capacity and Increment
Figure 2-25: Increment Options Drop-Down List
30303895 | 00 | 11/2015
METTLER TOLEDO ACT350 Transmitter User's Guide
2-23
2.7.2.3.
Calibration
2.7.2.3.1.
GEO and Linearity
Operation
The Geo code and Linearity settings can be configured at Scale | Calibration.
Figure 2-26: Geo Code and Linearity
Refer to sections 2.6.1.7.1 and 2.6.1.7.2 for further information about these settings.
2.7.2.3.2.
Set Zero
The zero value is set at Scale | Calibration | Set Zero, and follows the same steps as described in
section 2.6.1.7.3.
Figure 2-27: Zero Calibration Process, 1 – Start
2-24
METTLER TOLEDO ACT350 Transmitter User's Guide
30303895 | 00 | 11/2015
Figure 2-28: Zero Calibration Process, 2 – In Progress
Figure 2-29: Zero Calibration Process, 3 – Complete
30303895 | 00 | 11/2015
METTLER TOLEDO ACT350 Transmitter User's Guide
2-25
2.7.2.3.3.
Set Span
Operation
The Span value, including any linearity calibration points, is set at Scale | Calibration | Set Span,
and follows the same sequence as described in section 2.6.1.7.4. In the example shown here,
Linearity is set to None.
Figure 2-30: Span Calibration Process, 1 – Set Test Load
Figure 2-31: Span Calibration Process, 2 – Complete
2.7.2.3.4.
Step Calibration
The step calibration procedure, accessed at Scale | Calibration | Step Calibration, is performed in
the same as in the transmitter (described in section 2.6.1.7.5).
The process can be ended after the completion of any step by clicking on the Done button. In the
example shown below, two steps are used.
1. First, a test load is defined and the test weight placed on the scale. The process is then started
by clicking OK.
2-26
METTLER TOLEDO ACT350 Transmitter User's Guide
30303895 | 00 | 11/2015
Figure 2-32: Step Calibration 1 – Ready
2. Setup+ indicates that the calibration adjustment is in process.
Figure 2-33: Step Calibration 2 – In Process
3. When Setup+ indicates that the adjustment has been successful, either press Continue to move
to a new step, or Done to save the calibration and exit the procedure.
30303895 | 00 | 11/2015
METTLER TOLEDO ACT350 Transmitter User's Guide
2-27
Operation
Figure 2-34: Step Calibration 3 – Step 1 Complete
4. In this case, Continue was pressed, and Setup+ prompts to remove the test load from the
scale.
Figure 2-35: Step Calibration 4 – Removing the Load for Step 1
5. Press Continue to run the next step. Setup+ prompts for the addition of the test weight to the
scale.
2-28
METTLER TOLEDO ACT350 Transmitter User's Guide
30303895 | 00 | 11/2015
Figure 2-36: Step Calibration 5 – Ready for Step 2
6. Setup+ is now ready for step 2. Press OK to continue.
Figure 2-37: Step Calibration 6 – Ready
7. When the step completes, it is again possible to continue with another step, or click Done to
complete the process.
30303895 | 00 | 11/2015
METTLER TOLEDO ACT350 Transmitter User's Guide
2-29
Operation
Figure 2-38: Step Calibration 7 – Step 2 Complete
8. When Done is clicked, Setup+ indicates that the calibration values have been saved.
Figure 2-39: Step Calibration 8 – Procedure Complete
2-30
METTLER TOLEDO ACT350 Transmitter User's Guide
30303895 | 00 | 11/2015
2.7.2.3.5.
CalFree
CalFree is run at Scale | Calibration | CalFree. As in the transmitter (2.6.1.7.6), it requires the entry
of the total load cell capacity, unit and rated cell output. Cell Capacity and Rated Cell Output cannot
be zero, and are limited to 7 digits.
Figure 2-40: CalFree
Once the procedure has been started, Setup+ will indicate that it is in progress, and then confirm
that the adjustment was successful.
2.7.2.4.
Zero Options
Zero options are set at Scale | Zero.
Figure 2-41: Scale – Zero Options
30303895 | 00 | 11/2015
METTLER TOLEDO ACT350 Transmitter User's Guide
2-31
Operation
Figure 2-42: Scale – Power Up Zero Settings
2.7.3.
Application
2.7.3.1.
Comparators
The number of comparators used, and a limit value for each comparator, is set at Application |
Comparator. Each comparator limit value is limited to 7 digits.
Figure 2-43: Comparators Setup, 1
Figure 2-44 shows the display with all five comparators used, but not yet configured.
Figure 2-44: All Comparators Displayed
2-32
METTLER TOLEDO ACT350 Transmitter User's Guide
30303895 | 00 | 11/2015
2.7.4.
Communication
2.7.4.1.
Information Recall
The model-specific information displayed in the Information Recall menu 2.3.4in the ACT350 is not
shown in Setup+. Information about the PLC network is displayed in Stup+ at Communication I
Connection | PLC Interface | Profinet (or Profibus or EtherNet/IP, depending on the ACT350 model).
Figure 2-45: PLC Information Display
2.7.5.
Terminal
2.7.5.1.
Language
The Language selection menu can be accessed via the Setup+ Tool at Terminal | Region. A dropdown box allows English or Chinese to be selected.
Figure 2-46: Language Selection
30303895 | 00 | 11/2015
METTLER TOLEDO ACT350 Transmitter User's Guide
2-33
Operation
2.7.6.
Maintenance
2.7.6.1.
Errors
The transmitter’s error list can be viewed in Setup+ at Maintenance | Diagnostics | Faults. For a list
of errors, their meanings and recovery methods, refer to Table 2-1, in section 2.3.8, above.
Figure 2-47: Faults List
2-34
METTLER TOLEDO ACT350 Transmitter User's Guide
30303895 | 00 | 11/2015
3
Configuration
3.1.
Overview
This chapter covers
•
•
•
•
•
•
•
•
•
•
Overview
Weights and Measures
Setup+ Settings
Saving and Loading Terminal Files
This chapter provides information about configuration of the ACT350 Transmitter
using the PC-based Setup+ software. It does not include information about
settings that can be changed by the operator. These are described in Chapter 2,
Operation, along with information about menu navigation and the transmitter’s
features and functionality.
Scale
Application
Terminal
Communication
Maintenance
Reset Configuration and Master Reset
Figure 3-1: Setup+ Home Screen (Connected)
3.2.
Weights and Measures
When the transmitter is certified as legal for trade, the DIP switch 1, accessible on the underside of
the housing, must be set to ON.
Figure 3-2: DIP Switches
30303895 | 00 | 11/2015
METTLER TOLEDO ACT350 Transmitter User's Guide
3-1
Configuration
A metrological seal must be placed over the DIP switch array in order to prevent this setting from
being changed. When the terminal is in approved mode (refer to chapter 2, Operation, section
2.7.2.1), metrologically significant settings cannot be accessed through the terminal’s interface or
in Setup+. These include approval, unit, capacity, increment size, calibration, zero and stability
settings.
3.3.
Setup+ Settings
Refer to section 2.7.1, Connecting to Setup+, in Chapter 2, Operation. All the procedures described
in this chapter assume that Setup+ is connected to the ACT350 transmitter.
3.4.
Saving and Loading Files
Setup+ allows ACT350 configurations to be saved and restored, simplifying the configuration of
multiple new transmitters, and recovery from errors.
3.4.1.
Saving New File
To save the transmitter’s current configuration including calibration values, expand the Save
Terminal File menu at the left of the Setup+ screen, and click on Save All. Setup+ will display a
dialog asking whether to save the configuration settings. Click Start to begin the process or Esc to
abandon it.
Figure 3-3: Saving Files from the Transmitter
When Start is pressed, a file browser dialog appears, permitting the selection of a save location
either on the local PC running Setup+ or in a network location. Choose a location, enter a name for
the configuration file, and click Save.
3-2
METTLER TOLEDO ACT350 Transmitter User's Guide
30303895 | 00 | 11/2015
Figure 3-4: Browsing to Saved File Location
For ready identification, the file will be saved as .ipz.
When the save operation is complete, a dialog will indicate that the action has succeeded. Click OK
to complete the action and exit the dialog
Figure 3-5: Confirmation Dialog
3.4.2.
Loading Existing File
Loading a configuration file into the ACT350 provides additional options when browsing for the
configuration file. The file includes software and application revision information as well as the
model name of the transmitter. The selections shown in Figure 3-6 allow configuration files to be
chosen that match the transmitter’s hardware and software.
30303895 | 00 | 11/2015
METTLER TOLEDO ACT350 Transmitter User's Guide
3-3
Configuration
Figure 3-6: File Load Selection Options
Table 3-1: Load Selection Options
Load Selection
InSite Check
Match All
Transmitter firmware revision, application, & module settings must match
Match Terminal / Application
Transmitter & application settings must match, but revision & module
may be different
Match Terminal only
Only the transmitter type must match
No match required
No match is required
With the correct option selected, click the browse button
file.
and locate the desired configuration
Figure 3-7: Browsing for Saved Configuration File
When the file is found, double click on it, or select it and click Open. The file will be loaded into the
transmitter. A “Load Completed” dialog will indicate that the procedure has succeeded.
Finally, restart the transmitter to use the new settings.
3-4
METTLER TOLEDO ACT350 Transmitter User's Guide
30303895 | 00 | 11/2015
3.5.
Scale
Scale Type, Capacity & Increment, and Calibration setting screens are described in Chapter 2,
Operation.
3.5.1.
Stability
The ACT350’s stability settings are accessible only in Setup+.
Figure 3-8: Stability
The Stability screen offers three settings. Note that each of these settings can have only one digit
after the decimal point.
3.5.2.
Motion Range
Sets the maximum permissible range of motion, in scale divisions, before a
motion indication will be triggered.
No-motion Interval
Sets the time, in seconds, for which the scale must be stable before a
weight reading will be taken.
Timeout
Sets the time, in seconds, between attempts to perform a weighment after
the motion has been detected
Filter
The ACT350’s filter settings are accessible only in Setup+.
30303895 | 00 | 11/2015
METTLER TOLEDO ACT350 Transmitter User's Guide
3-5
Configuration
Figure 3-9: Filter Settings
The Filter screen offers three settings:
3.5.3.
Limit Frequency
Selections from 1 to 20 in this drop-down box set the cut-off frequency, in
Hertz, above which the filter actively attenuates the signal.
Weighing Mode
Sets the type of weighing, Normal or Dynamic, for which the ACT350 is being
used in the current application.
Environment
Sets the type of environment in which the ACT350 is working, depending on
how stable the scale is likely to be. Options are shown in the drop-down list:
Reset
To reset the scale settings, click on Reset. A warning screen will appear. To continue with the
operation, click OK. Otherwise, click on a different option in the menu tree at left to exit the screen
without resetting the scale configuration.
3-6
METTLER TOLEDO ACT350 Transmitter User's Guide
30303895 | 00 | 11/2015
Figure 3-10: Scale Type Reset
3.6.
Application
The Application menu includes only two items – Comparators, and Reset. Comparator configuration
is described in Chapter 2, Operation.
3.6.1.
Reset
To reset the Comparators, click on Reset. A warning screen will appear. To continue with the
operation, click OK. Otherwise, click on a different option in the menu tree at left to exit the screen
without resetting the scale configuration.
Figure 3-11: Application Reset
30303895 | 00 | 11/2015
METTLER TOLEDO ACT350 Transmitter User's Guide
3-7
Configuration
3.7.
Terminal
Several transmitter-specific settings are available only in Setup+. These are described in the
following sections.
3.7.1.
Device
The Device screen displays the factory serial number of the connected ACT350 Transmitter.
Figure 3-12: Terminal Device Screen
3.7.2.
Display
The ACT350’s display can be set to turn off after a period of activity. This screen is used to set this
period. Choices are Disabled (screen never turns off when transmitter is powered), 1, 10 and 30
minutes.
Figure 3-13: Terminal Display Screen
3-8
METTLER TOLEDO ACT350 Transmitter User's Guide
30303895 | 00 | 11/2015
3.7.3.
Region
The only Region option is Language. The language setting – English and Chinese – is described in
Chapter 2, Operation.
3.7.4.
User
The initial Terminal | User screen allows Protection (to make setup password-protected) to be
Disabled or Enabled.
Figure 3-14: Terminal User – Security
When Protection is Enabled, access to Setup and Calibration screens from the device menu is
restricted.
Figure 3-15: Terminal User Passwords
Enter a password, confirm it, and click OK. Be sure to make a note of the password -- if the
password is lost, it can be reset using Setup+.
30303895 | 00 | 11/2015
METTLER TOLEDO ACT350 Transmitter User's Guide
3-9
3.7.5.
Pushbutton
Configuration
The pushbutton zero can be Enabled or Disabled. When it is enabled and the scale is within the
Pushbutton Zero range configured at Scale | Zero (refer to Chapter 2, Operation), a brief press on
the transmitter’s ENTER
key will set the measured weight to zero.
Figure 3-16: Terminal Pushbutton Screen
3.7.6.
Reset
To reset the scale settings, click on Reset. A warning screen will appear. To continue with the
operation, click OK. Otherwise, click on a different option in the menu tree at left to exit the screen
without resetting the scale configuration.
Figure 3-17: Terminal Reset
3-10
METTLER TOLEDO ACT350 Transmitter User's Guide
30303895 | 00 | 11/2015
3.8.
Communication
3.8.1.
RS-232
The transmitter’s own connection settings are configured here. The Baud Rate, Data Bits and Parity
settings must match those made from the Settings screen in Setup+.
Figure 3-18: Communication RS-232
3.8.2.
PLC Interface
This menu includes two items – Data Format and PROFINET (or PROFIBUS, or EtherNet/IP).
3.8.2.1.
Data Format
Data Format settings are the same for PROFIBUS, PROFINET or EtherNet/IP versions of the ACT350.
The screen shown in Figure 3-19 is for a PROFIBUS model.
30303895 | 00 | 11/2015
METTLER TOLEDO ACT350 Transmitter User's Guide
3-11
Configuration
Figure 3-19: ACT350 Data Format
The Data Format screen offers three settings:
3.8.2.2.
FieldBus Assignment
Automatically set to Standard Automation Interface (SAI)
FieldBus Format
Options are 1-Block Format, 2-Block Format. 2-Block format is the default
in the ACT350
Byte Order
Options are Automatic, Little Endian, Big Endian. The default setting is
Automatic
PROFIBUS, PROFINET, EtherNet/IP
This screen simply indicates which of the three types of ACT350 is currently connected. This value
cannot be modified.
Figure 3-20: PLC Interface
3-12
METTLER TOLEDO ACT350 Transmitter User's Guide
30303895 | 00 | 11/2015
3.8.3.
Reset
To reset the scale settings, click on Reset. A warning screen will appear. To continue with the
operation, click OK. Otherwise, click on a different option in the menu tree at left to exit the screen
without resetting the scale configuration.
Figure 3-21: Communication Reset
3.9.
Maintenance
3.9.1.
Load Cell Output
The load cell output screen displays the current value being output by the load cell. This value is
updated in real time until the Esc button is clicked.
Figure 3-22: Load Cell Output
30303895 | 00 | 11/2015
METTLER TOLEDO ACT350 Transmitter User's Guide
3-13
3.9.2.
Calibration Values
Configuration
This screen displays the values generated by the most recent calibration, in scale units and in
counts.
Figure 3-23: Calibration Values
Figure 3-23 shows counts for Zero and Span calibration. These can be edited. Enabling linearity
and performing span calibration will populate the remaining fields.
3.9.3.
Statistics
Setup+ accumulates information about transmitter activity. The Statistics screen includes three
editable fields, and five Reset buttons.
Figure 3-24: Statistics
3-14
METTLER TOLEDO ACT350 Transmitter User's Guide
30303895 | 00 | 11/2015
This screen has three editable fields, which accept only integer values.
3.9.4.
Start Threshold
Expressed as a percent of the scale span
Reset Threshold
Expressed as a percent of the scale span
Zero Drift Threshold
Expressed as a percent of the scale span
Faults
The Faults, or errors, screen is described in Chatter 2, Operation. Table 3-2 lists and explains errors
that may be observed.
Table 3-2: ACT350 Faults
Error
002
ACT350 Display
Wait for calibration to finish
SAI initialize fail
Cycle power; call service if
issue persists
Lose connection to network
Check cable or connector
Hardware information error
Cycle power; call service if
issue persists
Calib. err
Calibration block data error;
block data is lost
Perform master reset
Re-calibrate
Scale err
Scale block data error; block
data is lost
Perform master reset
Perform setup for scale block
Term. err
Terminal block data error;
block data is lost
Perform master reset
Perform setup for terminal
block
Application block data error;
block data is lost
Perform master reset
APP. err
Communication block data
error; block data is lost
Perform master reset
NW. err
Perform master reset
Maint. err
Statistics block data error;
block data is lost
Lost analog signal; abnormal
functioning of scale
Call service
Scale in motion when Zero
attempted
Zero when scale is stable
Setup+ calib. in process
006
009
010
011
NW Module init.fail
NW connection disconnected
Board info. err
012
013
014
015
016
018
30303895 | 00 | 11/2015
Action
Calibration in process.
Distinguishes between
calibration performed in the
ACT350, and calibration
performed from Setup+
Local calib. in process
or
005
Description
Analog system A/D fail
Zero failed Motion
Perform setup for application
block
Perform setup for
communication block
Perform setup for maintenance
block
METTLER TOLEDO ACT350 Transmitter User's Guide
3-15
Error
Configuration
019
020
021
022
027
ACT350 Display
Description
Scale in net mode when Zero
attempted
Clear tare before zeroing
Zero failed out of range
Weight out of Zero range
Unload scale and zero
Zero failed Zero disabled
Zero attempted when function
disabled in setup
Enable Zero function in Setup
Tare failed as scale is in
motion
Tare when scale is stable
Preset tare value not in display
increment size
The preset tare value must be
rounded to the same increment
Tare value too small
The preset tare value must be
minimum of 1 display
increment
Power-up zero not captured;
Zero not captured after power
cycle (with Zero capture
enabled) then tare was
attempted
Disable zero capture at powerup or unload scale and powerup again, then tare
Tare was attempted while scale
was over capacity
Remove weight and tare within
weighing range
Tare value under zero
The preset tare value must be
positive
A/D converter in overload
Reprogram Scale Capacity
Zero failed net mode
Tare failed Motion
Tare failed Not rounded value
028
Tare failed Value too small
029
Tare failed Zero not captured
030
031
035
3.9.5.
Action
Tare Failed, Scale Over
capacity
Tare failed Negative value
Analog saturation
Reset
To reset the scale settings, click on Reset. A warning screen will appear. To continue with the
operation, click OK. Otherwise, click on a different option in the menu tree at left to exit the screen
without resetting the scale configuration.
Figure 3-25: Maintenance Reset
3-16
METTLER TOLEDO ACT350 Transmitter User's Guide
30303895 | 00 | 11/2015
3.10.
Reset Configuration and Master Reset
3.10.1.
Reset Configuration
To reset all configured items except calibration data:
1. Remove power from the transmitter.
2. Locate the DIP switches, accessible from the underside of the housing.
3. Set both DIP switches, 1 and 2, to ON (up, in Figure 3-26), and restore power to the
transmitter.
Figure 3-26: DIP Switches
4. Set both DIP switches to OFF.
3.10.2.
Master Reset
A master reset restores all settings to their factory default values:
1. Remove power from the transmitter.
2. Set switch 2 to its ON position and restore power to the transmitter. The ACT350 will prompt for
confirmation.
Figure 3-27: Master Reset Confirmation
3. Press ENTER on the front panel to perform the master reset.
4. Set Switch 2 to OFF.
Table 3-3: DIP Switch Functions
30303895 | 00 | 11/2015
Legal for Trade
Reset
Switch 1
Switch 2
OFF
OFF
Normal operation
ON
OFF
Legal-for-trade mode; calibration data protected
Function
METTLER TOLEDO ACT350 Transmitter User's Guide
3-17
Configuration
3-18
Legal for Trade
Reset
Switch 1
Switch 2
OFF
ON
Master reset of all data during transmitter power-up
ON
ON
Reset of all except calibration data during transmitter power-up
Function
METTLER TOLEDO ACT350 Transmitter User's Guide
30303895 | 00 | 11/2015
4
Installation
4.1.
Overview
This chapter covers
•
•
•
•
Overview
Mounting
Physical installation of the ACT350 is extremely simple, since it functions as a standard DIN
rail-mounted component. Chapters 2, Operation and 3, Configuration, describe all other
information about setting up a new ACT350.
Connections
DIP Swtiches
4.2.
Mounting
NOTICE
IN ORDER TO ENSURE PROPER DISSIPATION OF HEAT FROM THE TRANSMITTER’S PCBS, AND TO AVOID DAMAGE TO
THE EQUIPMENT, THE ACT350 MUST BE MOUNTED VERTICALLY, ON A HORIZONTAL DIN RAIL.
The ACT350’s DIN mount includes a green latch, visible in Figure 4-1.
Upper mounting tabs
Sliding latch
Figure 4-1: DIN-Mount Latch
To mount the ACT350 on a rail, open this latch by pulling down on it, then position the transmitter
so that its upper tabs rest on the DIN rail.
30303895 | 00 | 11/2015
METTLER TOLEDO ACT350 Transmitter User's Guide
4-1
Installation
Then use a screwdriver to close the latch and secure the transmitter in position.
Figure 4-2: Latch Closure
To remove the ACT350, simply put the blade of a screwdriver in the latch and press it downward.
Figure 4-3: Latch Closure
4-2
METTLER TOLEDO ACT350 Transmitter User's Guide
30303895 | 00 | 11/2015
4.3.
Connections
Figure 4-4 and Figure 4-5 indicate the ACT350’s connectors and their functions. Note that some
EtherNet/IP and PROFINET transmitters may have a single network port, or dual ports as shown at
right in Figure 4-4
Power connector
Fieldbus connection
Analog scale interface
PROFIBUS connection
Figure 4-4: ACT350s – PROFIBUS (left) and PROFINET or EtherNet/IP (right)
The top of the transmitters includes a serial COM port for RS-232 communication, for service
purposes.
RS-232 connection
Figure 4-5: ACT350, Top View
4.3.1.
Analog Load Cell
For ESD protection, cabling for the analog load cell must include a ferrite and a silicone protection
sleeve, included with the transmitter.
Analog load cell connector
Power connector
Silicone sleeve
Ferrite
Figure 4-6: Cabling Components
30303895 | 00 | 11/2015
METTLER TOLEDO ACT350 Transmitter User's Guide
4-3
Installation
Install the ferrite by passing it through the ferrite and wrapping it around once, as indicated here.
Figure 4-7: Ferrite Installed on Analog Load Cell Cable
To accommodate the ferrite, it may be necessary to cut the silicone sleeve to size.
Figure 4-8: Silicone Sleeve, Trimmed to Fit
4.3.2.
RS-232 Serial Connection
The serial connection on top of the transmitter is used to connect ACT350 to the PC-based Setup+
Configuration Tool. Refer to chapters 2, Operation and 3, Configuration.
4.4.
DIP Switches
Two DIP switches, 1 and 2, are accessible from the underside of the ACT350’s housing. Table 4-1
summarizes their functions.
Table 4-1: DIP Switch Functions
4-4
Legal for Trade
Reset
Switch 1
Switch 2
OFF
OFF
Normal operation
ON
OFF
Legal-for-trade mode; calibration data protected
OFF
ON
Master reset of all data during transmitter power-up
ON
ON
Reset of all except calibration data during transmitter power-up
Function
METTLER TOLEDO ACT350 Transmitter User's Guide
30303895 | 00 | 11/2015
5
EtherNet/IP Version
5.1.
Preface
This chapter covers
•
•
•
•
•
•
•
Preface
EtherNet/IP Interface Board
This chapter describes connections, setup and programming sample specific to the
EtherNet/IP version of the ACT350. The formats of the data that is transferred between the
ACT350 and the PLC are described in Appendix B, Standard Automation Interface.
Overview of EtherNet/IP
Data Formats
Software Setup
Troubleshooting
Programming Examples
5.2.
EtherNet/IP Interface
Figure 5-1 shows the ACT350 with EtherNet/IP interface. Note that the device’s address can be set
from unit front panel or the PC-based Setup+ configuration tool.
EtherNet
(RJ45) port
Figure 5-1: EtherNet/IP Version of ACT350 Transmitter
30303895 | 00 | 11/2015
METTLER TOLEDO ACT350 Transmitter User's Guide
5-1
5.3.
Overview of EtherNet/IP
EtherNet/IP
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.
Good industrial networking practices as recommended by the PLC equipment manufacturer must be
observed to ensure the best possible performance and to maintain deterministic network behavior.
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 ACT350's factory pre-configured EtherNet/IP interface enables the device to communicate to
EtherNet/IP Programmable Logic Controllers (PLCs) through direct connection to the EtherNet/IP
network at either 10 or 100 MBPS speed. Software to implement the data exchange resides in the
ACT350 Transmitter.
5.3.1.
Standard Automation Interface
The ACT350 uses the METTLER TOLEDO Standard Automation Interface (SAI) protocol. This data
protocol is supported over fieldbus interfaces specifically for control system use. The SAI protocol
provides a common data format for multiple devices over multiple fieldbus types allowing for easier
integration via common data content and organization.
Both cyclic and acyclic data are supported via SAI.
For asynchronous or acyclic data communications the ACT350 supports Direct Access Level 1
format. This method of data communication uses the acyclic parameter access method provided
through the automation interface to read and write specific internal variables.
See Appendix B for detailed information on Standard Automation Interface (SAI), and Appendix C
and Appendix D, respectively, for Cyclic and Acyclic communications.
5.3.2.
EtherNet/IP Characteristics
The EtherNet/IP version of the ACT350 has the following features:
5.3.3.
•
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 ACT350.
•
Acyclic or explicit unscheduled message transfer between the PLC and the ACT350
Definition of Terms
Table 5-1 provides definitions specific to EtherNet/IP.
5-2
METTLER TOLEDO ACT350 Transmitter User's Guide
30303895 | 00 | 11/2015
Table 5-1: EtherNet/IP Definition of Terms
Term
Definition
An Adapter Class product emulates functions provided by traditional rackAdapter Class 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.
Class 1 In EtherNet/IP communication protocol scheduled (cyclic) message transfer
Messaging between a PLC and CIP Adapter Class device.
In EtherNet/IP communication protocol unscheduled message transfer between
Class 3
a PLC and CIP Adapter Class device. This is used by the ACT350 for
Messaging
asynchronous or acyclic messaging.
A connection is a relationship between two or more application objects on
different nodes. The connection establishes a virtual circuit between end points
Connected for transfer of data. Node resources are reserved in advance of data transfer
Messaging 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.
Connection Source for I/O connection or message requests. Initiates an I/O connection or
Originator explicit message connection.
Explicit Messages (also known as Discrete, or Class 3, or Acyclic 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
Explicit
protocol is contained in the message data. Explicit Messages provide a oneMessaging
time 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.
Implicit
Messaging
Implicit Messages (also called Class 1, or cyclic 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 application-specific 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
I/O Client perform a task. Initiates a request for an I/O message to the server module.
The I/O Client is a Connection Originator.
I/O Messaging Used interchangeably with the term Implicit or Cyclic Messaging.
Function that provides I/O messaging services to another (I/O Client) device.
I/O Server 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
Message Client Server) device to perform a task. Initiates an Explicit message request to the
server device.
30303895 | 00 | 11/2015
METTLER TOLEDO ACT350 Transmitter User's Guide
5-3
Term
Definition
EtherNet/IP
Function that provides Explicit messaging services to another (Message
Message Server 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 Scanner Class products. This type of node can respond to connection requests
and can also initiate connections on its own.
Target
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
Unconnected
message and the message is not guaranteed destination node resources.
Messaging
Unconnected Messaging is used for non-periodic requests (e.g. network
“Who” function). Explicit messages only. See also Connected Messaging.
5.3.4.
Communications
The ACT350 transmitter utilizes component parts to ensure complete compatibility with the AllenBradley EtherNet/IP network. An ACT350 terminal is recognized as a generic EtherNet/IP device by
the PLC.
Each EtherNet/IP device connected to the EtherNet/IP network represents a physical IP Address. The
connection is made via a RJ-45 connector on the ACT350 front panel (see Figure 5-1).
The wiring between the PLC and the ACT350 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 Allen-Bradley for the EtherNet/IP network.
The ACT350 only uses Class 1 cyclic data for discrete data and Class 3 explicit messages for
access to the ACT350 Variables. Explicit message blocks may be connected or unconnected; the
PLC programmer must make this choice.
5.3.5.
IP Address
Each EtherNet/IP option represents one physical IP Address. This address is chosen by the system
designer, and then programmed into the ACT350 transmitter and PLC either from the device front
panel or via the PC-based Setup+ Configuration Tool. The ACT350's IP Address entry must be
unique for each ACT350 transmitter. The ACT350 transmitter’s address is programmed at Setup >
PLC > EtherNet/IP in the transmitter’s setup menu accessed from the device's front panel. Once the
device is configured to work on the fieldbus network (MAC address, IP address, Subnet mask etc.)
and the control system is configured to add the device to its network, the device will begin sending
gross weight data.
5.4.
Data Formats
The ACT350 EtherNet/IP interface provides discrete data transfer, Class 1 and Class 3 messaging.
Data transfer is accomplished via the PLC’s cyclic and explicit messaging respectively. Discrete
5-4
METTLER TOLEDO ACT350 Transmitter User's Guide
30303895 | 00 | 11/2015
data is continuously available. The EtherNet/IP interface has its own logical IP address to send and
receive information to and from the PLC continuously. Only floating point format of discrete data is
supported on the ACT350 EtherNet/IP version.
Note: The ACT350 does not support Integer or Divisions data formats.
The ACT350 EtherNet/IP version also supports asynchronous data transfer and class 3 acyclic
messaging. The SAI protocol provides a read and a write message block that contains parameters
to refer to the device's internal variables. The method employs the acyclic message itself to select
the variable (index or class/instance attribute) using a fieldbus specific parameter in its message
block.
5.4.1.1.
Assembly Instances of Class 1 Cyclic Communications
Class 1 cyclic communications is used for transfer of Discrete Data between the PLC and the
ACT350.
The PLC Input Assembly Instance is 101 (decimal). This instance is used for all data size
requirements.
The PLC Output Assembly Instance is 100 (decimal). This instance is used for all data size
requirements.
The ACT350 uses data only. Configuration data is not used or required. Within the PLC EtherNet / IP
Interface setup set the Configuration Instance to 1 and the data size to zero.
The provided EDS file has no Assembly Instance or data size limitations. The ACT350 programming
controls the Assembly Instance and data size limitations.
Refer to chapter on Standard Automation Interface (SAI)
5.4.1.2.
Cyclic Data Format
For cyclic data communication, SAI supports 1-Block and 2-Block formats on the ACT350. 2-Block
format is the default data format on the ACT350. Refer to chapter on Standard Automation Interface
(SAI) for details.
The data block types include floating point and status.
5.4.1.2.1.
One Block Operation
The cyclic data of the 1-Block Format should be sent with minimal device configuration and
minimal control system integration. Once the device is successfully added to the control system
network, it should immediately begin sending its default cyclic data (typically gross weight
information). The 1-Block Format always consists of a single Read Floating Point Data Block and a
single Write Floating Point Data Block.
30303895 | 00 | 11/2015
METTLER TOLEDO ACT350 Transmitter User's Guide
5-5
Data Read into PLC or DCS
Data Written from PLC or DCS
Floating Point Data (Block 1)
EtherNet/IP
Floating Point Data (Block 1)
Word 0
Word 1
Word 2
Word 3
32 bit Floating point value – optionally used with
Command & Channel Indicator
16 bit Channel Mask
16 bit Command & Channel Indicator (Command)
Word 0
Word 1
Word 2
Word 3
32 bit (requested) Floating point value
16 bit Scale/Command status
16 bit Field Value & Channel Indicator (Response)
1-Block Data Format Layout
Figure 5-2: 1-Block Data Format Layout
5.4.1.2.2.
Two Block Operation
The SAI 2-Block Format builds on the format structure used by the 1-Block Format to provide
support for two blocks of input data and two blocks of output data. This fixed format requires no
configuration. This format was designed for applications where the device supports additional
status information.
The cyclic data of the 2-Block Format supports two read blocks and two write blocks - a single
Floating Point Data Block and a single Status Block for each. Status groups provide the means for
the PLC to monitor the status of RedAlert Alarms and comparators. Like the 1-Block Format, the 2Block Format provides a default configuration that immediately begins to send default cyclic data
(with little to no coding).
Data Read into PLC or DCS
Data Written from PLC or DCS
Floating Point Data (Block 1)
Floating Point Data (Block 1)
Word 0
Word 1
Word 2
Word 3
32 bit Floating point value – optionally used with
Command & Channel Indicator
Word 0
Word 1
32 bit (requested) Floating point value
16 bit Channel Mask
Word 2
Word 3
16 bit Scale/Command status
Word 4
Word 5
Word 6
Word 7
Status Group 1
16 bit Command & Channel Indicator (Command)
Word 4
Word 5
Word 6
Word 7
Reserved
Reserved
Reserved
Command Word
16 bit Field Value & Channel Indicator (Response)
Status (Block 2)
Status (Block 2)
Status Group 2
Status Group 3
Response Word
2-Block Data Format Layout
Figure 5-3: 2-Block Data Format Layout
5.5.
Software Setup
On the ACT350 EtherNet/IP version, the EtherNet / IP parameters are enabled in the Setup block at
Communication > Connection > PLC Interface > EtherNet / IP. Figure 5-4 shows the PLC and
EtherNet/IP setup blocks in the PC-based Setup+ Configuration Tool.
5-6
METTLER TOLEDO ACT350 Transmitter User's Guide
30303895 | 00 | 11/2015
Figure 5-4: PLC and EtherNet/IP Setup Blocks
5.5.1.
EtherNet/IP and Data Format Setup Blocks
5.5.1.1.
EtherNet/IP Setup
The EtherNet/IP setup block at Setup > Communication > Connection > PLC Interface > EtherNet /
IP is where the IP Address, Enable/Disable DHCP, Subnet Mask and Gateway Address of the
EtherNet/IP interface are specified. If DHCP is selected, the ACT350 will carry out a power cycle and
will automatically populate the IP Address, Subnet Mask and Gateway Address fields with
information received from the DHCP server.
The MAC address is displayed, but cannot be modified.
5.5.1.1.1.
Mac ID
The Mac ID of the EtherNet/IP internal factory integrated interface PCB can be viewed.
5.5.1.1.2.
DHCP Client
This setting determines if the address information for the transmitter will be automatically assigned
by the DHCP server when connected or if a static address will be used. The DHCP can either be
Enabled [1] or Disabled [0] (the default) for the interface.
30303895 | 00 | 11/2015
METTLER TOLEDO ACT350 Transmitter User's Guide
5-7
5.5.1.1.3.
IP Address
EtherNet/IP
The IP address for the transmitter can be viewed (if DHCP is Enabled) or entered (if DHCP is
Disabled). The default value is 192-168-000-002.
5.5.1.1.4.
Subnet Mask
The Subnet Mask address for the transmitter can be viewed (if DHCP is Enabled) or entered (if
DHCP is Disabled). The default value is 255-255-255-000.
5.5.1.1.5.
Gateway Address
The Gateway address for the transmitter can be viewed (if DHCP is Enabled) or entered (if DHCP is
Disabled). The default value is 192.168.000.001.
5.5.1.2.
Data Format Setup
In Setup, navigate to Setup > Communication > Connection > PLC Interface > Data Format. The
following fields are available for EtherNet/IP.
5.5.1.2.1.
SAI
The Standard Automation Interface is the default communication protocol to exchange data between
the ACT350 and the control system.
5.5.1.2.2.
Fieldbus Format
Select the format - 1-Block or 2-Block format. 2-Block format is the default data format on the
ACT350. The cyclic data of the 1-Block Format should selected where minimal device configuration
and minimal control system integration is sufficient. This fixed format requires no configuration. The
2-Block format supports data from the 1-Block format and supports additional status information.
Refer to chapter on Standard Automation Interface (SAI) for more information.
5.5.1.2.3.
Byte Order
Select Byte Order from available selections - Automatic, Big Endian (Byte and Word Swap) and
Little Endian (No Word or Byte Swap).
The Automatic selection is the default. When Automatic is selected, the byte and word order is
determined by two possible methods – first, EtherNet/IP has a known default (Little Endian) that is
used until the test command is sent from the control system and second, a test command can be
sent from the control system to put the device into a test state which checks for a specific floating
point value and determines the order based on the way the data is received. The current state of the
byte order is shown as the Current Order.
Refer to chapter on Standard Automation Interface (SAI) for more information.
5-8
METTLER TOLEDO ACT350 Transmitter User's Guide
30303895 | 00 | 11/2015
5.6.
Troubleshooting
If the ACT350 does not communicate with PLC, do the following:
5.7.
•
Power cycle the ACT350 to reestablish communications.
•
A solid green NW LED on the front panel implies that the ACT350 is on the network. A blinking
NW LED indicates that the ACT350 is not on the fieldbus network.
•
Check LED status of the RJ-45 connection socket. The top LED should be solid green. If the top
LED is not solid green then this implies that no hardware connection is being seen by the
device -check cabling and connector insertions. The bottom LED will blink amber if data is
being transferred. If the top LED is solid green, but the bottom LED is not blinking then this
implies a configuration issue either in the ACT350 or the PLC.
•
Confirm that the ACT350 can respond to a Ping on the Network. If it doesn’t, then check the
wiring and network connections.
•
Diagnose and correct specific Network error conditions such as IP Address conflicts.
•
Confirm that the ACT350 settings for data type, I/O size and IP Address assignment match
those in the PLC and that each ACT350 has a unique address.
•
Check the Electronic Keying from in the PLC program. Confirm that the firmware revision of the
Ethernet/IP module in the ACT350 greater than or equal to the firmware revision specified in the
ACT350’s communication module in the PLC. Change the firmware revision being looked for in
the PLC’s communication module if necessary.
•
Contact METTLER TOLEDO for replacement of the ACT350 transmitter.
Programming Example
The following Figures show sample screen images of ladder logic programming examples for
RSLogix 5000 software (version 20).
Note: A zip file containing complete versions of the examples can be downloaded from
www.mt.com/ind-act350-downloads. The screen images below are provided for illustrative
purposes only.
The Ethernet/IP interface of the ACT350 is capable of communicating at either 10 or 100 Mbps. It
communicates using Full Duplex mode, and is compatible with the Auto Negotiate setting used by
many PLC’s and Ethernet Switches.
At this time an Add On Profile (AOP) does not exist for the ACT350. The sample PLC logic included
in this chapter uses the Generic Ethernet Module included with the ControlLogix Programming
software to define the ACT350's communication module. For convenience, the sample module
shown below can be copied into your own program, which will in turn copy their associated
descriptors. The below example covers both Cyclic and Acyclic data formats.
5.7.1.
Cyclic and Acyclic Sub-routines
The following Figures show steps for getting data into a PLC.
30303895 | 00 | 11/2015
METTLER TOLEDO ACT350 Transmitter User's Guide
5-9
EtherNet/IP
1. Define a Generic Ethernet Module under the Ethernet Bridge
Figure 5-5: Defining a Generic Ethernet Module
Define a Name
for the Device
Define the I/O
Assembly
instance sizes
Select “Data-INT”
Enter the IP
address
Figure 5-6: 2-Block Format
2. Create tags for Cyclic Data exchange. Copy the "SAI" Data Type to create more instrument tags
as needed –one tag for each device on the network.
Copy the
User-Defined
Data Types
from the
Sample
program
Define a new
tag that uses
the “SAI”
Data Type
Figure 5-7: Creating Tags for Cyclic Data Exchange
3. The main routine is split into two sub-routines:
5-10
METTLER TOLEDO ACT350 Transmitter User's Guide
30303895 | 00 | 11/2015
•
Part 1 handles Cyclic Data.
•
Part 2 handles Acyclic (Discrete or Explicit messages) Data.
Part 1
Part 2
Figure 5-8: Data-Handling Sub-Routines
5.7.1.1.
Cyclic Data Subroutine
1. Rung 1 initializes the command Ack and data displayed variable on first scan. The first rung
also initializes all of the command tags with the proper values for use in the program.
Figure 5-9: Cyclic Data Subroutine, Rung 1
2. Cyclic data Subroutine Rung 2 executes the following
a. Copying of raw input data to the SAI Device tag Structure
b. Uses the Data_OK bit and the Heartbeat status to indicate a possible bad value in the
Floating Point Input Value
c. Copies the data in the Device Tag Output Structure to the Raw Output Data Area
30303895 | 00 | 11/2015
METTLER TOLEDO ACT350 Transmitter User's Guide
5-11
EtherNet/IP
a
b
c
Figure 5-10: Cyclic Data Subroutine, Rung 2
3. Cyclic data Subroutine Rung 3 executes the Heartbeat Monitor. The Heartbeat monitor is a timer
that is constantly being reset by the changing state of the device's heartbeat. The timer never
times-out and the Heartbeat_OK bit stays ON as long as the heartbeat continues to change
state.
Heartbeat monitor
Heartbeat OK bit
Figure 5-11: Heartbeat Monitor
4. With Byte Order set to Automatic, cyclic data Subroutine Rung 4 directs the instrument to match
the PLC's byte order without the PLC program needing additional code to decipher the data
from the ACT350. This sequence is optional and may not be needed in many cases. The
following steps enable this Standard Automation Interface capability:
a. First send the "TestMode" command with a floating point argument of 2.76.
b. Introduce a short delay.
c. Then issue an "Exit TestMode" command to resume normal operation.
The ACT350 is ready to continue when the state of the Data_OK bit is true.
5-12
METTLER TOLEDO ACT350 Transmitter User's Guide
30303895 | 00 | 11/2015
TestMode command
FP Argument 2.76
Short delay
Exit TestMode command
Data_OK bit true
Figure 5-12: Implementing Test Mode
5. Cyclic data Subroutine Rung 5 monitors the floating point value returned to the PLC for
monitoring purpose for programmer convenience, and may be omitted from the program.
6. Rung 6 handles the Command Acknowledge by:
a) Using the command acknowledged sequence bits to generate a value between 0 and 3.
b) When a new CMD_Ack value comes in, the timer holds the Command_Acked bit on long
enough for the following rungs to see it.
Rung 5
Rung 6
a
b
Figure 5-13: Cyclic Data Subroutine, Rungs 5 and 6
7. Rung 7 monitors for new commands. When a new command is found, it is moved to the
Output structure, which will cause it to be sent to the ACT350 in the next scan. Copying a
30303895 | 00 | 11/2015
METTLER TOLEDO ACT350 Transmitter User's Guide
5-13
EtherNet/IP
command to the Output Structure only when a new command is present allows for manual
manipulation of the Output Structure for troubleshooting and other purposes.
Monitor for new
commands
Command Structure
Figure 5-14: Cyclic Data Subroutine, Rung 7
8. Cyclic data Subroutine Rung 8 shows the various sample commands that can be issued from
the PLC by triggering uniquely mapped command bits.
a. Each command bit initiates a move that transfers a Command Value into the "Command"
tag processed in the Rung 7.
b. The command is acknowledged on Rung 6 and the Command Acknowledge bit
(Command_Acked) turns true long enough for Rung 8 to see the status.
c. With the Command_Acked bit true, the command bit that triggered the command sequence
on Rung 8 is cleared.
a
c
b
Initiates transfer of
Command value
Figure 5-15: Cyclic Data Subroutine, Rung 8
5.7.1.1.1.
General Programming Notes
The data being read from the ACT350 should be filtered with the Data_OK bit and the Heartbeat
status in the PLC program. Doing so makes sure that the ACT350 is in a valid operational state and
that the Analog Update from the scale has properly completed before the data was read. Using the
5-14
METTLER TOLEDO ACT350 Transmitter User's Guide
30303895 | 00 | 11/2015
Data_OK bit and the Heartbeat status guarantees the validity of the data before using it in a process
and prevents use of a possible bad value in the Floating Point Input Value.
5.7.1.2.
Acyclic Data
Acyclic commands are listed in the Standard Automation Interface chapter.
The following Figures show steps for handling explicit message instructions to the ACT350.
1. The sample routine has two basic parts
a. Sample commands (Rung 2).
b. Message Instruction blocks on rungs 3, 4 and 5. Note that each message
instruction is for a different class of command.
a
Floating Point Read
b
Byte Command
Floating Point Command
Figure 5-16: Basic Parts of the Acyclic Data Subroutine
30303895 | 00 | 11/2015
METTLER TOLEDO ACT350 Transmitter User's Guide
5-15
EtherNet/IP
2. Rung 2 includes typically used explicit commands
a. Each command bit initiates a move that transfers a Command Attribute into the Attribute tag
of the appropriate message instruction. Note that each message instruction is for a different
class of command (Floating Point Read, byte Write and Floating Point Command).
b. A bit is set to trigger the correct message instruction.
c. The command bit that triggered the command sequence is then cleared.
a
b
c
Figure 5-17: Acyclic Data Subroutine, Rung 2
3. Rung 3 sets up an explicit message instruction to read floating point values.
Set from Rung 2
MOV for display
purposes only
Figure 5-18: Acyclic Data Subroutine, Rung 3
5-16
METTLER TOLEDO ACT350 Transmitter User's Guide
30303895 | 00 | 11/2015
4. Rung 4 sets up an explicit message instruction to write a Byte Command. Byte commands
typically send a byte long flag (0x01) to trigger a command, such as Clear, Tare or Zero.
Set from Rung 2
Figure 5-19: Acyclic Data Subroutine, Rung 4
30303895 | 00 | 11/2015
METTLER TOLEDO ACT350 Transmitter User's Guide
5-17
EtherNet/IP
5. Rung 5 sets up an explicit message instruction to write a Floating Point Command. Floating
Point Commands send a command in the form of an attribute and include a Floating Point
value. Examples would be a Preset Tare or a comparator value.
Set from Rung 2
Figure 5-20: Acyclic Data Subroutine, Rung 5
5-18
METTLER TOLEDO ACT350 Transmitter User's Guide
30303895 | 00 | 11/2015
6
PROFINET
6.1.
Preface
This chapter describes connections, setup and programming sample specific to the PROFINET
version of the ACT350. The formats of the data that is transferred between the ACT350 and the PLC
are described in chapter on Standard Automation Interface.
6.2.
PROFINET Interface
This chapter covers
•
•
•
•
•
•
•
•
•
Preface
PROFINET Interface
Overview
Standard Automation Interface
Figure 6-1 shows the ACT350 with PROFINET interface. Note that the device’s
address can be set from unit front panel or by using the PC–based Setup+
configuration tool.
Note: The transmitter provides no access to the communication board DIP
switches. They are all set to OFF within the sealed device.
PROFINET Characteristics
Data Formats
Software Setup
Troubleshooting
Programming Examples
EtherNet
(RJ45) port
Figure 6-1: ACT350 PROFINET version
30303895 | 00 | 11/2015
METTLER TOLEDO ACT350 Transmitter User's Guide
6-1
6.3.
Overview
PROFINET
PROFINET is an open industrial networking standard that was developed by Siemens as an Ethernet
replacement for its widely popular PROFIBUS Network. The network supports Cyclic and Acyclic
messaging, both of which are supported on the ACT350. The PROFINET Standard is supported and
Maintained by the PROFINET and PROFINET International (PI) Organization.
PROFINET utilizes commercial, off–the–shelf EtherNet hardware (for example, switches and routers)
and is fully compatible with the Ethernet TCP/IP protocol suite. Good industrial networking practices
as recommended by the PLC equipment manufacturer must be observed to ensure the best possible
performance and to maintain deterministic network behavior.
The ACT350's factory pre–configured PROFINET interface implements PROFINET IO for cyclic Data
exchange with the PLC, and uses Acyclic messages for variable access by the PLC.
Communication with PROFINET enabled Programmable Logic Controllers (PLCs) takes place
through direct connection to the PROFINET network at 10 or 100 MBPS speed. Software to
implement the data exchange resides in the ACT350 Transmitter.
The ACT350 appears as a block of I/O data on the PROFINET bus. The number of input and output
words needed for the configured message slots are determined by the chosen data format. The
choices are 1–Block or 2–Block formats.
The ACT350 PROFINET GSDML file supports 2 different data formats for the defined I/O. Both 1 and
2–Block data formats support Floating Point modes. Each block is identified as the number of input
and output words configured within the block.
6.4.
Standard Automation Interface
The ACT350 uses the METTLER TOLEDO Standard Automation Interface (SAI) protocol. This data
protocol is supported over fieldbus interfaces specifically for control system use. The SAI protocol
provides a common data format for multiple devices over multiple fieldbus types allowing for easier
integration via common data content and organization.
Both cyclic and acyclic data are supported via SAI.
For asynchronous or acyclic data communications the ACT350 supports Direct Access Level 1
format. This method of data communication uses the acyclic parameter access method provided
through the automation interface to read and write specific internal variables.
Refer to Appendix B for detailed information on Standard Automation Interface (SAI) Cyclic and
Acyclic communications.
6.5.
PROFINET Characteristics
The PROFINET version of the ACT350 has the following features:
•
6-2
User–programmable IP addressing.
METTLER TOLEDO ACT350 Transmitter User's Guide
30303895 | 00 | 11/2015
6.5.1.
•
Capability for bi–directional discrete mode communications (Cyclic Messaging) of weight or
display increments, status, and control data between the PLC and the ACT350.
•
Acyclic or unscheduled message transfer between the PLC and the ACT350
Definition of Terms
Table 6–1 provides definitions specific to PROFINET.
Table 6–1: PROFINET Definition of Terms
Term
30303895 | 00 | 11/2015
Definition
DAP
Device Access Point
DCP
Discovery and basic Configuration Protocol. Used for IP configuration over PROFINET.
DHCP
De–facto standard for dynamic IP address management
GSDML
XML–based descriptive language for GSD–files
Initial Record Data
Record Data write–requests destined for a sub–module. Comparable to PROFIBUS–DP
User Parameter Data.
IOCS
IO Consumer Status
IOPS
IO Provider Status
IO Controller
Controlling device, which acts as a client for several IO devices. Usually a PLC.
Comparable to a PROFIBUS–DP Class 1 master.
IO Device
Field device assigned to an IO Controller. Comparable to a PROFIBUS DPV1 slave.
IO Supervisor
Programming device with commissioning and diagnostic functions. Comparable to a
PROFIBUS–DP Class 2 master.
Module
Hardware or logical component of a network device.
Submodule
Hardware or logical component of a module
PDEV
Physical DEVice. From specification version 2.0 it is possible to describe the physical
Ethernet interface and its ports (PDEV, or Physical Device) with a special mechanism.
This is done with special submodules at slot 0 (the module at slot 0 is the access
point for the device).
PNIO
Short for PROFINET IO
PROFINET IO
PROFINET IO is a communication concept for the implementation of modular,
decentralized applications.
Comparable to Profibus–DP, where I/O data of field devices are cyclically transmitted
to the process image of a PLC. The real time capabilities of PROFINET IO are further
divided into RT and IRT (see below).
PROFINET IO RT
PROFINET IO with Real Time capabilities. Optimized real time communication channel
for time critical I/O data and Alarms. Implemented in software.
PROFINET IRT
PROFINET IO with Isochronous Real Time capabilities. Necessary for motion control
applications which require an update rate of 1ms, or less, with no jitter. Implemented
in hardware.
PROFINET CBA
PROFINET Component Based Automation. Comparable to PROFIBUS FMS.
Record Data
Comparable to PROFIBUS DPV1 acyclic Read/Write
METTLER TOLEDO ACT350 Transmitter User's Guide
6-3
6.5.2.
Communications
PROFINET
The ACT350 transmitter utilizes component parts to ensure complete compatibility with Siemens
PROFINET network. An ACT350 terminal is recognized as a generic PROFINET device by the PLC.
Each ACT350 PROFINET version device connected to the PROFINET network represents one
physical IP Address. This address is chosen by the system designer, and then programmed into the
ACT350 via Setup+ or front panel and the PLC, or the address can be assigned by the PLC using
DHCP and MAC Address association.
The connection is made via a RJ–45 connector on the ACT350 front panel (see Figure 6-1).
6.5.3.
IP Address
Each ACT350 PROFINET version device connected to the PROFINET network represents one
physical IP Address. This address is chosen by the system designer, and then programmed into the
ACT350 via Setup+ or front panel and the PLC, or the address can be assigned by the PLC using
DHCP and MAC Address association.
The ACT350's IP Address entry must be unique for each ACT350 transmitter. The ACT350
transmitter’s address is programmed at Setup > PLC > PROFINET in the transmitter’s setup menu
accessed from the device's front panel or on Setup+. Once the device is configured to work on the
fieldbus network (MAC address, IP address, Subnet mask, Gateway) and the control system is
configured to add the device to its network, the device will begin sending gross weight data.
6.6.
Data Formats
The ACT350 PROFINET interface provides discrete data transfer. Data transfer is accomplished via
the PLC’s cyclic (UDP) messaging respectively. Discrete data is continuously available. The
PROFINET interface has its own logical IP address to send and receive information to and from the
PLC continuously. Only floating point format of discrete data is supported on the ACT350 PROFINET
version.
Note: The ACT350 does not support Integer or Divisions data formats.
The ACT350 PROFIBUS version also supports acyclic (TCP/IP) messaging. The SAI protocol
provides a read and a write message block that contains parameters to refer to the device's internal
variables. The method employs the acyclic message itself to select the variable (slot, sub slot and
index value) using a fieldbus specific parameter in its message block.
6.6.1.1.
Cyclic Communications
Cyclic communications is used for transfer of Discrete Data between the PLC and the ACT350.
Ensure that the ACT350 shows up in the Hardware Catalog and is defined in the Network Hardware
configuration.
Refer to section 6.9, Programming Examples, for more details.
6-4
METTLER TOLEDO ACT350 Transmitter User's Guide
30303895 | 00 | 11/2015
6.6.1.2.
Cyclic Data Format
For cyclic data communication, SAI supports 1–Block and 2–Block formats on the ACT350. Refer to
chapter on Standard Automation Interface (SAI) for details.
The data block types include floating point and status.
6.6.1.2.1.
One Block Operation
The cyclic data of the 1–Block Format should be sent with minimal device configuration and
minimal control system integration. Once the device is successfully added to the control system
network, it should immediately begin sending its default cyclic data (typically gross weight
information). The 1–Block Format always consists of a single Read Floating Point Data Block and a
single Write Floating Point Data Block.
Data Written from PLC or DCS
Data Read into PLC or DCS
Floating Point Data (Block 1)
Word 0
Word 1
Word 2
Word 3
Floating Point Data (Block 1)
32 bit Floating point value – optionally used with
Command & Channel Indicator
16 bit Channel Mask
16 bit Command & Channel Indicator (Command)
Word 0
32 bit (requested) Floating point value
Word 1
Word 2
Word 3
16 bit Scale/Command status
16 bit Field Value & Channel Indicator (Response)
1-Block Data Format Layout
Figure 6-2: 1–Block Data Format Layout
6.6.1.2.2.
Two Block Operation
The SAI 2–Block Format builds on the format structure used by the 1–Block Format to provide
support for two blocks of input data and two blocks of output data. This fixed format requires no
configuration. This format was designed for applications where the device supports additional
status information.
The cyclic data of the 2–Block Format supports two read blocks and two write blocks – a single
Floating Point Data Block and a single Status Block for each. Status groups provide the means for
the PLC to monitor status of RedAlert Alarms and comparators. Like the 1–Block Format, the 2–
Block Format should provide a default configuration that immediately begins to send default cyclic
data (with little to no coding).
Data Written from PLC or DCS
Data Read into PLC or DCS
Floating Point Data (Block 1)
Floating Point Data (Block 1)
Word 0
Word 1
Word 2
Word 3
16 bit Command & Channel Indicator (Command)
Word 4
Word 5
Word 6
Word 7
Reserved
Reserved
Reserved
Command Word
32 bit Floating point value – optionally used with
Command & Channel Indicator
16 bit Channel Mask
Word 0
Word 1
Word 2
Word 3
16 bit Field Value & Channel Indicator (Response)
Word 4
Word 5
Word 6
Word 7
Status Group 1
Status Group 2
Status Group 3
Response Word
Status (Block 2)
32 bit (requested) Floating point value
16 bit Scale/Command status
Status (Block 2)
2-Block Data Format Layout
Figure 6-3: 2–Block Data Format Layout
30303895 | 00 | 11/2015
METTLER TOLEDO ACT350 Transmitter User's Guide
6-5
6.7.
Software Setup
PROFINET
On the ACT350 PROFINET version, the PROFINET parameters are enabled in Setup at
Communication > Connection > PLC Interface > PROFINET. Figure 6-4 shows the PLC and
PROFINET setup blocks in the PC–based Setup+ Configuration Tool.
Figure 6-4: PROFINET Setup Block
6.7.1.
PROFINET and Data Format Setup Blocks
6.7.1.1.
PROFINET Setup
The PROFINET setup block at Setup > Communication > Connection > PLC Interface > PROFINET is
where the Device Name, IP Address, Subnet Mask and Gateway Address of the PROFINET interface
are specified.
The MAC address is displayed, but cannot be modified.
6.7.1.1.1.
Device Name
Each ACT350's descriptive name that is on the network can be input and viewed
6.7.1.1.2.
Mac ID
The Mac address of the PROFINET internal factory integrated interface PCB can be viewed.
6.7.1.1.3.
IP Address
The IP address for the transmitter can be input and viewed. The default value is 192.168.000.002.
6-6
METTLER TOLEDO ACT350 Transmitter User's Guide
30303895 | 00 | 11/2015
6.7.1.1.4.
Subnet Mask
The Subnet Mask address for the transmitter can be input and viewed. The default value is
255.255.255.000.
6.7.1.1.5.
Gateway Address
The Gateway address for the transmitter can be input and viewed. The default value is
192.168.000.001.
6.7.1.2.
Data Format Setup
In Setup, navigate to Setup > Communication > Connection > PLC Interface > Data Format. The
following fields are available for PROFINET.
6.7.1.2.1.
SAI
The Standard Automation Interface is the default communication protocol to exchange data between
the ACT350 and the control system.
6.7.1.2.2.
Fieldbus Format
Select the format – 1-Block or 2-Block format. 2-Block format is the default data format on the
ACT350. The cyclic data of the 1-Block Format should selected where minimal device configuration
and minimal control system integration is sufficient. This fixed format requires no configuration. The
2-Block format supports data from the 1-Block format and supports additional status information.
Refer to chapter on Standard Automation Interface (SAI) for more information.
6.7.1.2.3.
Byte Order
Select Byte Order from available selections – Automatic, Big Endian (Byte and Word Swap) and
Little Endian (No Word or Byte Swap).
The Automatic selection is the default. When Automatic is selected, the byte and word order is
determined by two possible methods – first, PROFINET has a known default (Big Endian) that is
used until the test command is sent from the control system and second, a test command can be
sent from the control system to put the device into a test state which checks for a specific floating
point value and determines the order based on the way the data is received. The current state of the
byte order is shown as the Current Order.
Refer to chapter on Standard Automation Interface (SAI) for more information.
6.8.
Troubleshooting
If the ACT350 does not communicate with PLC, do the following:
30303895 | 00 | 11/2015
•
Power cycle the ACT350 to reestablish communications
•
A solid green NW LED on the front panel implies that the ACT350 is on the network. A blinking
NW LED indicates that the ACT350 is not on the fieldbus network.
•
Check LED status of the RJ-45 connection socket. The top LED should be solid green. If the top
LED is not solid green then this implies that no hardware connection is being seen by the
device -check cabling and connector insertions. The bottom LED will blink amber if data is
METTLER TOLEDO ACT350 Transmitter User's Guide
6-7
PROFINET
being transferred. If the top LED is solid green, but the bottom LED is not blinking then this
implies a configuration issue either in the ACT350 or the PLC.
6.9.
•
Confirm that the ACT350 can respond to a Ping on the Network. If it doesn’t, then check the
wiring and network connections.
•
Diagnose and correct specific Network error conditions such as IP Address conflicts.
•
Confirm that the ACT350 settings for data type, PROFINET slot, sub slot, index value and IP
Address assignment match those in the PLC and that each ACT350 has a unique address.
•
Check the Electronic Keying from in the PLC program. Confirm that the firmware revision of the
PROFINET module in the ACT350 is greater than or equal to the firmware revision specified in
the ACT350’s communication module in the PLC. Change the firmware revision being looked
for in the PLC’s communication module if necessary.
•
Contact METTLER TOLEDO for replacement of the ACT350 transmitter.
Programming Examples
The following Figures show sample screen images of ladder logic programming examples for
Siemens Step 7 software (version 5.5).
Note: A zip file containing complete versions of the examples can be downloaded from
www.mt.com/ind-act350-downloads. The screen images below are provided for illustrative
purposes only.
The PROFINET interface of the ACT350 is capable of communicating at 10 or 100 Mbps. It
communicates using Full Duplex mode, and is compatible with the Auto Negotiate setting used by
many PLC’s and Ethernet Switches.
For convenience, the sample module shown below can be copied into your own program, which
will in turn copy their associated descriptors. The below example covers both Cyclic and Acyclic
data formats.
6.9.1.
Cyclic Data Sub–routine
The following figures show steps for getting data into a PLC.
1. Install the GSDML file, so that the ACT350 shows up in the Hardware Catalog.
6-8
METTLER TOLEDO ACT350 Transmitter User's Guide
30303895 | 00 | 11/2015
Figure 6-5: GSD File
2. Place the device in the PROFINET Network Hardware configuration. Note that the default I/O size
on the ACT350 is 2-Block.
Drag the “RT” Standard
object to the network and
select the I/O size
Figure 6-6: PROFINET Network Hardware Configuration
3. Set up the device name and IP configuration in the Hardware Configuration.
a. Bring up the context menu by right clicking on the device and select Object Properties.
b. Configure the Device Name and Device Number.
30303895 | 00 | 11/2015
METTLER TOLEDO ACT350 Transmitter User's Guide
6-9
PROFINET
c. Configure IP settings.
a
b
c
Figure 6-7: PROFINET Network Hardware Configuration
4. Use DCP to assign a physical device in the Hardware Configuration using the "Edit Ethernet
Node" selection.
6-10
METTLER TOLEDO ACT350 Transmitter User's Guide
30303895 | 00 | 11/2015
Figure 6-8: Editing the Ethernet Node
30303895 | 00 | 11/2015
METTLER TOLEDO ACT350 Transmitter User's Guide
6-11
PROFINET
5. Compile, save and download the configuration to PLC
Figure 6-9: Configuration Dowloaded to PLC
6. Verify that the configuration is working online with the PLC.
Indication
when PLC
can see
device
Indication
when PLC
cannot see
device
Figure 6-10: Confirming Function of Configuration
7. Configure Tags by creating Data Block for Cyclic Data Exchange. Use the "FP_Block_Read" and
"FP_Block_Write" data Types to create more instrument tags as needed for each device on the
network.
6-12
METTLER TOLEDO ACT350 Transmitter User's Guide
30303895 | 00 | 11/2015
Figure 6-11: Creating Instrument Tags
8. Sample Program: OB1 – Cycle Execution
Note: The "Cyclic Data" and the "Acyclic data" routines show different ways to do the same
things. Both may not be needed in a typical program.
Part 1 to handle Cyclic Data
Part 2 to handle Acyclic Messages
“SAI_Init” is a flag set in OB100 to
let all other routines know when the
first scan after a restart is running,
which allows for initialization. The
flag is cleared at the end of OB1.
Figure 6-12: Sample Program OB1
30303895 | 00 | 11/2015
METTLER TOLEDO ACT350 Transmitter User's Guide
6-13
PROFINET
9. Cyclic Data Subroutine: Network 1 – initialize on first scan. Network 1 initializes the command
Ack, Data Displayed variables and all of the Command tags with proper values for use in the
program.
Auto Byte Order
request is set
here
Figure 6-13: Cyclic Nature Subroutine: Network 1
10. Cyclic Data Subroutine: Network 2 and 3 – Automatic Byte Order.
Automatic Byte Order tells the ACT350 to match the PLC's byte order so that the program does
not need additional code to make the data understandable to the PLC. Note that that this
sequence is optional, and may not be needed in many cases.
To initiate the Auto Byte Order feature, send a test command with a Floating Point argument of
2.76, followed by a short delay.
6-14
METTLER TOLEDO ACT350 Transmitter User's Guide
30303895 | 00 | 11/2015
“TestMode” command
FP Argument 2.76
Short delay
Figure 6-14: Test Mode
11. Cyclic Data Subroutine: Network 4 Automatic Byte Order continued. Resume normal operation
by issuing an "Exit TestMode" command. The ACT350 is ready to continue when the Data_OK
bit is true.
“Exit Test Mode”
Data_OK bit
Figure 6-15: Exit Test Mode
12. Cyclic Data Subroutine: Network 5: Map I/O.
Network 5 does the following:
a. Using the Input addresses specified in the Hardware Configuration Tool, copies the Raw
Input data into the ACT350's Tag Structure
30303895 | 00 | 11/2015
METTLER TOLEDO ACT350 Transmitter User's Guide
6-15
PROFINET
b. Uses the Data_OK and the Heartbeat status to indicate a possible bad value in the Floating
Point Input value
c. Copies the data in the ACT350 Tag Output Structure to the Raw Output Data Area. The
output address is taken from the Hardware Configuration tool
d. Copies the Command response to an integer value for easy comparison later
d
a
c
b
Figure 6-16: Mapping I/O
13. Cyclic Data Subroutine: Networks 6-8: Heartbeat Monitor. The Heartbeat Monitor is a timer that
is constantly being reset by the changing state of the device's heartbeat. As long as the
heartbeat continues to change state, the timer never times out and the Heartbeat_OK bit stays
ON.
Timer
Figure 6-17: Heartbeat Monitor
14. Cyclic Data Subroutine: Network 9-11: Command Acknowledge
a. The Sequence Bits are used to generate a value between 0 and 3
6-16
METTLER TOLEDO ACT350 Transmitter User's Guide
30303895 | 00 | 11/2015
b. MW6 is used to convert the Sequence Bits to an integer value
c. The Command_Acked bit will stay on as long as CMD_Ack and the History do not match.
Once the rest of the program has had the chance to see the acknowledgement, the timer on
Network 10 will cause the History to match the CMD_Ack which shuts off the Command_Acked
bit.
a
b
c
d
Figure 6-18: Command Acknowledge
30303895 | 00 | 11/2015
METTLER TOLEDO ACT350 Transmitter User's Guide
6-17
PROFINET
15. Cyclic Data Subroutine: Network 12: Command Output
Upon monitoring for new commands, when a new command is found, it is moved to the
Output Structure and sent to the ACT350 on the next scan. Copying a command to the Output
Structure only when a new command is present allows for manual manipulation of the Output
Structure for trouble shooting and other purposes
Output structure
Monitor for new commands
6-18
Figure 6-19: Command Output
METTLER TOLEDO ACT350 Transmitter User's Guide
30303895 | 00 | 11/2015
16. Cyclic Data Subroutine: Network 13-14: Sample Commands
a. Each command bit initiates a move that transfers a Command value into the "Command"
tag, which is processed on Network 12
b. The command is acknowledged on Network 9
c. The bit that triggered the command is cleared
b
c
a
Figure 6-20: Sample Commands
17. Cyclic Data Subroutine: Network 15: Sample Commands.
The Enter_TestMode and Exit_TestMode commands are special cases where the command bits
are cleared without waiting for the command acknowledge bits to toggle.
30303895 | 00 | 11/2015
METTLER TOLEDO ACT350 Transmitter User's Guide
6-19
PROFINET
Figure 6-21: Entering and Exiting Test Mode
18. The Cyclic Data Sample program can be exercised using the Cyclic_Command Variable Access
Table (VAT)
a.
b.
c.
d.
e.
f.
g.
h.
i.
6-20
Triggers the Auto Byte Order sequence
Indicates when the Auto Byte Order Sequence is complete (ON = Complete)
Command value echoed back from ACT350
Command Ack combined bit value (0 thru 3)
Current Command being sent
Current Command mask being sent
Current Command Floating Point data being sent
New Command Acked Flag
Sample Commands – set the bit (one at a time) to send the corresponding command
METTLER TOLEDO ACT350 Transmitter User's Guide
30303895 | 00 | 11/2015
a
b
c
d
e
f
g
h
i
Figure 6-22: Cyclic Command
6.9.2.
Acyclic Data Sub-routine
The Acyclic routine handles acyclic message instructions to the ACT350. The routine has two basic
parts – Sample Commands (Network 2) and (SFB) Message System Function Blocks (Networks 4
for floating point read, 7 for floating point command and 10 for byte command).
Acyclic commands are listed in Appendix D.
1. Acyclic Data Subroutine: Network 2 – Sample Commands.
a. Each command bit initiates a move that transfers a Command Index into the "Index" tag of
the appropriate SFB instruction
30303895 | 00 | 11/2015
METTLER TOLEDO ACT350 Transmitter User's Guide
6-21
PROFINET
b. Then set a bit to trigger the correct SFB message instruction (Floating Point Read, Byte
Write, Floating Point Command)
c. Lastly, the bit that triggered the command sequence is cleared
a
c
b
Figure 6-23: Acyclic Data Sub-Routine, Network 2
2. Acyclic Data Subroutine: Network 3. Network 3 triggers the correct SFB message function based
on flags set in Network 2
a. Network 2 maps the sample command to the SFB type and sets the correct Message Type
bit
b. The Request to run the message SFB can only be ON for one scan so a Positive Edge Pulse
is used to filter the request bits
6-22
METTLER TOLEDO ACT350 Transmitter User's Guide
30303895 | 00 | 11/2015
a
b
Figure 6-24: Acyclic Data Sub-Routine, Network 3
3. Acyclic Data Subroutine: Network 4. Network 4 is used for floating point reads of floating point
value such as a Weight or a Tare value from ACT350.
a.
b.
c.
d.
e.
f.
30303895 | 00 | 11/2015
Set from Network 2
Request set from Network 3 (ON for one scan)
Lowest address converted to Hex (256 (Dec) = 0x0100 (Hex)
Floating Point Word size in Bytes and 4 byte array where returned value will be placed
Status Flags monitored in following network
Returned status and number of bytes actually returned
METTLER TOLEDO ACT350 Transmitter User's Guide
6-23
PROFINET
a
Hardware
Configuration
c
b
e
a
d
f
Figure 6-25: Acyclic Data Sub-Routine, Network 4
4. Acyclic Data Subroutine: Network 5. Network 5 sets the Result flags for the Floating Point
Read. These flags are displayed in the Acyclic Variable Access table, and can be used
elsewhere in the program.
Figure 6-26: Acyclic Data Sub-Routine, Network 5
5. Acyclic Data Subroutine: Network 6. Network 6 processes the Floating Point result:
a. If a valid read has taken place, then copy the raw byte data into a Floating Point tag for use
in the program
b. If there was a problem with the read, then flag it by moving -9999.0 into the floating point
tag
6-24
METTLER TOLEDO ACT350 Transmitter User's Guide
30303895 | 00 | 11/2015
Regardless of the result, clear the request when the message function has completed.
c
a
b
Figure 6-27: Acyclic Data Sub-Routine, Network 6
6. Acyclic Data Subroutine: Network 7. Network 7 is used for writing a floating point value such as
Preset Tare value to the ACT350.
a.
b.
c.
d.
Set from Network 2 including variable index
Request set from Network 3 (ON for one scan)
Lowest address converted to Hex (256 (Dec) = 0x0100 (Hex)
Floating Point Word size in Bytes and 4 byte array where value to be sent was placed in
Network 2
e. Status Flags monitored in following network
f. Returned status
30303895 | 00 | 11/2015
METTLER TOLEDO ACT350 Transmitter User's Guide
6-25
PROFINET
Hardware
Configuration
a
c
b
e
a
d
f
Figure 6-28: Acyclic Data Sub-Routine, Network 7
7. Acyclic Data Subroutine: Network 8. Network 8 sets the Results flags for the Floating Point
Write. These flags are displayed in the Acyclic Variable Access Table and can be used
elsewhere in the program
Figure 6-29: Acyclic Data Sub-Routine, Network 8
6-26
METTLER TOLEDO ACT350 Transmitter User's Guide
30303895 | 00 | 11/2015
8. Acyclic Data Subroutine: Network 9. Use Network 9 to process floating point result to clear the
request when the message function has completed regardless of whether a valid write has
taken place or if an error was encountered.
Figure 6-30: Acyclic Data Sub-Routine, Network 9
9. Acyclic Data Subroutine: Network 10. Use Network 10 to send a byte long flag (0x01) to
trigger a command such as Tare, Clear or Zero
a.
b.
c.
d.
e.
f.
30303895 | 00 | 11/2015
Set from Network 2 including variable index
Request set from Network 3 (ON for one scan)
Lowest address converted to Hex (256 (Dec) = 0x0100 (Hex)
Value to be sent in Bytes. 1 Byte array where value to be sent was placed in Network 1
Status Flags monitored in following network
Returned status
METTLER TOLEDO ACT350 Transmitter User's Guide
6-27
PROFINET
Hardware
Configuration
a
c
b
e
a
d
f
Figure 6-31: Acyclic Data Sub-Routine, Network 10
10. Acyclic Data Subroutine: Network 11. Network 11 sets the Results flags for the 1 Byte Write.
These flags are displayed in the Acyclic Variable Access Table and can be used elsewhere in
the program.
Figure 6-32: Acyclic Data Sub-Routine, Network 11
6-28
METTLER TOLEDO ACT350 Transmitter User's Guide
30303895 | 00 | 11/2015
11. Acyclic Data Subroutine: Network 12. Use Network 12 to process 1 Byte Write result to clear the
request when the message function has completed regardless of whether a valid write has
taken place or if an error was encountered.
Figure 6-33: Acyclic Data Sub-Routine, Network 12
12. The ACyclic Data Sample program can be exercised using the Acyclic_Command Variable
Access Table (VAT)
a.
b.
c.
d.
e.
f.
g.
30303895 | 00 | 11/2015
Any Floating Point Read data is displayed here
Floating Point data to be sent by Preset_Tare command
Index values sent for all commands are displayed here
Sample Commands – set the bit (one at a time) to send the corresponding command
Floating Point Read message status
Floating Point Write message status
Byte Command message status
METTLER TOLEDO ACT350 Transmitter User's Guide
6-29
PROFINET
a
b
c
d
e
f
g
Figure 6-34: Acyclic_Command Variable Access Table
6-30
METTLER TOLEDO ACT350 Transmitter User's Guide
30303895 | 00 | 11/2015
7
PROFIBUS
7.1.
Preface
This chapter describes connections, setup and programming sample specific to the
PROFIBUS version of the ACT350. The formats of the data that is transferred between the
ACT350 and the PLC are described in Appendix B, Standard Automation Interface.
This chapter covers
•
•
•
•
•
•
•
•
•
•
Preface
Overview
Communications
Data Definition
Floating Point
Shared Data
Software Setup
Troubleshooting
Interfacing Examples
Sample PLC Program
7.2.
PROFIBUS Interface
Figure 7-1 shows the ACT350 with PROFIBUS interface. Note that the device’s node address can be
set from unit front panel or the PC-based Setup+ configuration tool.
Note: PLC communication board is not accessible because this is a sealed device.
Figure 7-1: ACT350 PROFIBUS Version
30303895 | 00 | 11/2015
METTLER TOLEDO ACT350 Transmitter User's Guide
7-1
7.3.
Overview
PROFIBUS
The ACT350 PROFIBUS DP factory pre-configured version enables the ACT350 transmitter to
communicate to a PROFIBUS DP master according to DIN 19245. 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 ACT350 Weight Transmitter implements PROFIBUS-DPV1, which supports cyclic and acyclic
data exchange, diagnostics, and process alarm handling.
The ACT350 appears as a block of I/O data on the PROFIBUS bus. The number of input and output
words needed for the configured message blocks are determined by the chosen data format. The
choices are 1 Block or 2 Block formats.
The ACT350 PROFIBUS GSD file supports 2 different data formats for the defined I/O. 1 Block format
exchanges 8 bytes (4 words) of cyclic data in both directions. 2 Block format exchanges 16 bytes
(8 words) of cyclic data in both directions. Either format will work with Acyclic messaging.
7.3.1.
Node Address
Each ACT350 PROFIBUS version device represents one physical node. The node address is chosen
by the system designer and then programmed into the ACT350 and the PLC. The ACT350’s node
address is programmed in setup at Setup > PLC > PROFIBUS. 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 ACT350’s PROFIBUS
.GSD files.
7.4.
Standard Automation Interface
The ACT350 uses the METTLER TOLEDO Standard Automation Interface (SAI) protocol. This data
protocol is supported over fieldbus interfaces specifically for control system use. The SAI protocol
provides a common data format for multiple devices over multiple fieldbus types allowing for easier
integration via common data content and organization.
Both cyclic and acyclic data are supported via SAI.
For asynchronous or acyclic data communications the ACT350 supports Direct Access Level 1
format. This method of data communication uses the acyclic parameter access method provided
through the automation interface to read and write specific internal variables.
Refer to Appendix B for detailed information on Standard Automation Interface (SAI), and Appendix
C and Appendix D, respectively, for Cyclic and Acyclic communications.
7-2
METTLER TOLEDO ACT350 Transmitter User's Guide
30303895 | 00 | 11/2015
7.5.
Hardware Setup
7.5.1.
Wiring
The ACT350 PROFIBUS version has a DB-9 connector to connect to the PROFIBUS network
interface. The wiring termination is listed in Table 7-1: . Cable distance, cable type, and termination
are specified by PROFIBUS. (Refer to the PLC documentation for cable design guidelines for the
various PLCs.)
7.5.1.1.
NOTES:
•
Use mating connectors and cable recommended for PROFIBUS connections.
•
Refer to PROFIBUS International documentation for other considerations.
Figure 7-2: ACT350 PROFIBUS DB-9 Connector
Table 7-1: PROFIBUS Wiring Termination
Pin
7.6.
Signal
1
Not used
2
Not used
3
TxD + and RxD +
4
RTS
5
Bus Ground
6
Bus +5V
7
Not used
8
TxD – and RxD –
9
Not used
Data Formats
The ACT350 PROFIBUS interface provides discrete data transfer. Data transfer is accomplished via
the PLC’s cyclic (priority on timing) messaging respectively. Discrete data is continuously
available. The PROFIBUS interface has its own logical node address to send and receive
information to and from the PLC continuously.
30303895 | 00 | 11/2015
METTLER TOLEDO ACT350 Transmitter User's Guide
7-3
PROFIBUS
The ACT350 PROFIBUS version also supports acyclic (priority on robustness) messaging. The SAI
protocol provides index numbers, which refer to the ACT350's internal variables, so that the PLC's
Read and Write System Function Blocks can access them.
Only floating point format of discrete data is supported on the ACT350 PROFIBUS version.
Note: The ACT350 does not support Integer or Divisions data formats.
7.6.1.
Floating Point
Some older Siemens PLC's (S5) do not inherently support the IEEE-format Floating Point number
format, but use their own unique Floating Point format. In those cases, the Auto-Byte Order function
of SAI may not work as intended without first converting the Floating Point arguments to the IEEE
standard using a software function block in the PLC.
7.6.2.
Cyclic Communications
Cyclic communications is used for transfer of Discrete Data between the PLC and the ACT350.
Ensure that the ACT350 shows up in the Hardware Catalog and is defined in the Network Hardware
configuration.
Refer to section 7.9, Programming Examples, for more details.
7.6.3.
Cyclic Data Format
For cyclic data communication, SAI supports 1 Block and 2 Block formats on the ACT350. Refer to
chapter on Standard Automation Interface (SAI) for details.
The data block types include floating point and status.
7.6.3.1.
One Block Operation
The cyclic data of the 1 Block Format should be sent with minimal device configuration and
minimal control system integration. Once the device is successfully added to the control system
network, it should immediately begin sending its default cyclic data (typically gross weight
information). The 1 Block Format always consists of a single Read Floating Point Data Block and a
single Write Floating Point Data Block.
Data Read into PLC or DCS
Data Written from PLC or DCS
Floating Point Data (Block 1)
Floating Point Data (Block 1)
Word 0
Word 1
Word 2
Word 3
32 bit Floating point value – optionally used with
Command & Channel Indicator
Word 0
Word 1
32 bit (requested) Floating point value
16 bit Channel Mask
Word 2
Word 3
16 bit Scale/Command status
16 bit Command & Channel Indicator (Command)
16 bit Field Value & Channel Indicator (Response)
1-Block Data Format Layout
Figure 7-3: 1-Block Data Format Layout
7.6.3.2.
Two Block operation
Two Block operation is the default data format on the ACT350. The SAI 2 Block Format builds on
the format structure used by the 1 Block Format to provide support for two blocks of input data and
7-4
METTLER TOLEDO ACT350 Transmitter User's Guide
30303895 | 00 | 11/2015
two blocks of output data. This fixed format requires no configuration. This format was designed for
applications where the device supports additional status information.
The cyclic data of the 2 Block Format supports two read blocks and two write blocks - a single
Floating Point Data Block and a single Status Block for each. Status groups provide the means for
the PLC to monitor status of RedAlert Alarms and comparators. Like the 1 Block Format, the 2 Block
Format provides a default configuration that immediately begins to send default cyclic data (with
little to no coding).
Data Written from PLC or DCS
Data Read into PLC or DCS
Floating Point Data (Block 1)
Floating Point Data (Block 1)
32 bit Floating point value – optionally used with
Command & Channel Indicator
Word 0
Word 1
Word 2
Word 3
16 bit Channel Mask
Word 2
Word 3
16 bit Field Value & Channel Indicator (Response)
Word 4
Reserved
Word 4
Status Group 1
Word 5
Word 6
Word 7
Reserved
Word 5
Word 6
Word 7
Status Group 2
Word 0
Word 1
16 bit Command & Channel Indicator (Command)
16 bit Scale/Command status
Status (Block 2)
Status (Block 2)
Reserved
Command Word
32 bit (requested) Floating point value
Status Group 3
Response Word
2-Block Data Format Layout
Figure 7-4: 2-Block Data Format Layout
7.7.
Software Setup
On the ACT350 PROFIBUS version, the PROFIBUS parameters are enabled in the Setup block at
Communication > Connection > PLC Interface > PROFIBUS. Figure 7-5 shows the PROFIBUS setup
block on the PC-based Setup+ Configuration Tool.
30303895 | 00 | 11/2015
METTLER TOLEDO ACT350 Transmitter User's Guide
7-5
PROFIBUS
Figure 7-5: PROFIBUS Setup Block
7.8.
Troubleshooting
7.8.1.
Procedure
If the ACT350 does not communicate with PLC, do the following:
7-6
•
Power cycle the ACT350 to reestablish communications
•
A solid green NW LED on the front panel implies that the ACT350 is on the network. A blinking
NW LED indicates that the ACT350 is not on the fieldbus network.
•
Check wiring and network termination.
•
Confirm that the ACT350 settings for address, format and byte order match those in the PLC
and that each ACT350 has a unique address.
•
If neither of the checks above resolves the issue, contact an authorized METTLER TOLEDO
service location.
METTLER TOLEDO ACT350 Transmitter User's Guide
30303895 | 00 | 11/2015
7.9.
Programming Examples
The following Figures show sample screen images of ladder logic programming examples for
Siemens Step 7 software (version 5.5).
Note: A zip file containing complete versions of the examples can be downloaded from
www.mt.com/ind-act350-downloads. The screen images below are provided for illustrative
purposes only.
For convenience, the sample modules shown below can be copied into your own program, which
will in turn copy the associated descriptors. The example below covers both Cyclic and Acyclic data
formats.
7.9.1.
Cyclic Data Sub-routine
The following figures show steps for getting data into a PLC.
1. Install the GSD file to have the ACT350 show up in the Hardware Catalog.
2) Place the device in the PROFIBUS Network Hardware configuration. Note that the default I/O
size on the ACT350 is 2 Block.
a. Drag the ACT350 object to the network
b. Select the PROFIBUS node address
c. Select the I/O size. 2 Block format is the default for the ACT350.
30303895 | 00 | 11/2015
METTLER TOLEDO ACT350 Transmitter User's Guide
7-7
PROFIBUS
2. Compile, save and download the configuration to PLC.
Click on the “Offline/Online” tool
7-8
METTLER TOLEDO ACT350 Transmitter User's Guide
30303895 | 00 | 11/2015
30303895 | 00 | 11/2015
METTLER TOLEDO ACT350 Transmitter User's Guide
7-9
PROFIBUS
3. Verify that the configuration is working online with the PLC.
4. Configure Tags by creating Data Block for Cyclic Data Exchange. Use the "FP_Block_Read" and
"FP_Block_Write" data Types to create more instrument tags as needed for each device on the
network.
5. Sample Program: OB1 – Cycle Execution
Note: The "Cyclic Data" and the "Acyclic data" routines show different ways to do the same
things. Both may not be needed in a typical program.
7-10
METTLER TOLEDO ACT350 Transmitter User's Guide
30303895 | 00 | 11/2015
6. Cyclic Data Subroutine: Network 1 – initialize on first scan. Network 1 initializes the command
Ack, Data Displayed variables and all of the Command tags with proper values for use in the
program.
7. Cyclic Data Subroutine: Network 2 and 3 – Automatic Byte Order. Automatic Byte Order tells the
ACT350 to match the PLC's byte order so that the program does not need additional code to
make the data understandable to the PLC. Note that that this sequence is optional, and may not
be needed in many cases.
To initiate the Auto Byte Order feature, send a test command with a Floating Point argument of
2.76, followed by a short delay.
30303895 | 00 | 11/2015
METTLER TOLEDO ACT350 Transmitter User's Guide
7-11
PROFIBUS
8. Cyclic Data Subroutine: Network 4 Automatic Byte Order continued. Resume normal operation
by issuing an "Exit TestMode" command. The ACT350 is ready to continue when the Data_OK
bit is true.
7-12
METTLER TOLEDO ACT350 Transmitter User's Guide
30303895 | 00 | 11/2015
9. Cyclic Data Subroutine: Network 5: Map I/O.
Network 5 does the following:
a. Using the Input addresses specified in the Hardware Configuration Tool, copies the Raw
Input data into the ACT350's Tag Structure.
b. Uses the Data_OK and the Heartbeat status to indicate a possible bad value in the Floating
Point Input value.
c. Copies the data in the ACT350 Tag Output Structure to the Raw Output Data Area. The
output address is taken from the Hardware Configuration tool.
d. Copies the Command response to an integer value for easy comparison later.
10. Cyclic Data Subroutine: Networks 6-8: Heartbeat Monitor. The Heartbeat Monitor is a timer that
is constantly being reset by the changing state of the device's heartbeat. As long as the
heartbeat continues to change state, the timer never times out and the Heartbeat_OK bit stays
ON.
30303895 | 00 | 11/2015
METTLER TOLEDO ACT350 Transmitter User's Guide
7-13
PROFIBUS
11. Cyclic Data Subroutine: Network 9-11: Command Acknowledge.
a. The Sequence Bits are used to generate a value between 0 and 3.
b. MW6 is used to convert the Sequence Bits to an integer value.
c. The Command_Acked bit will stay on as long as CMD_Ack and the History do not match.
d. Once the rest of the program has had the chance to see the acknowledgement, the timer on
Network 10 will cause the History to match the CMD_Ack which shuts off the
Command_Acked bit.
7-14
METTLER TOLEDO ACT350 Transmitter User's Guide
30303895 | 00 | 11/2015
12. Cyclic Data Subroutine: Network 12: Command Output. Upon monitoring for new commands,
when a new command is found, it is moved to the Output Structure and sent to the ACT350 on
the next scan. Copying a command to the Output Structure only when a new command is
present allows for manual manipulation of the Output Structure for trouble shooting and other
purposes.
13. Cyclic Data Subroutine: Network 13-14: Sample Commands.
a. Each command bit initiates a move that transfers a Command value into the "Command"
tag, which is processed on Network 12.
b. The command is acknowledged on Network 9.
c. The bit that triggered the command sequence is cleared.
30303895 | 00 | 11/2015
METTLER TOLEDO ACT350 Transmitter User's Guide
7-15
PROFIBUS
14. Cyclic Data Subroutine: Network 15: Sample Commands.
7-16
METTLER TOLEDO ACT350 Transmitter User's Guide
30303895 | 00 | 11/2015
The Enter_TestMode and Exit_TestMode commands are special cases where the command bits
are cleared without waiting for the command acknowledge bits to toggle.
15. The Cyclic Data Sample program can be exercised using the Cyclic_Command Variable Access
Table (VAT).
a. Triggers the Auto Byte Order sequence.
b. Indicates when the Auto Byte Order Sequence is complete (ON = Complete).
c. Command value echoed back from ACT350.
d. Command Ack combined bit value (0 thru 3).
e. Current Command being sent.
f.
Current Command mask being sent.
g. Current Command Floating Point data being sent.
h. New Command Acked Flag.
i.
30303895 | 00 | 11/2015
Sample Commands – set the bit (one at a time) to send the corresponding command.
METTLER TOLEDO ACT350 Transmitter User's Guide
7-17
PROFIBUS
7.9.2.
Acyclic Data Sub-routine
The Acyclic routine handles acyclic message instructions to the ACT350. The routine has two basic
parts – Sample Commands (Network 2) and (SFB) Message System Function Blocks (Networks 4
for floating point read, 7 for floating point command and 10 for byte command).
Acyclic commands are listed in Appendix D.
1. Acyclic Data Subroutine: Network 2 – Sample Commands.
a. Each command bit initiates a move that transfers a Command Index into the "Index" tag of
the appropriate SFB instruction.
b. Then set a bit to trigger the correct SFB message instruction (Floating Point Read, Byte
Write, Floating Point Command).
c. Lastly, the bit that triggered the command sequence is cleared.
7-18
METTLER TOLEDO ACT350 Transmitter User's Guide
30303895 | 00 | 11/2015
2. Acyclic Data Subroutine: Network 3. Network 3 triggers the correct SFB message function based
on flags set in Network 2.
a. Network 2 maps the sample command to the SFB type and sets the correct Message Type
bit.
b. The Request to run the message SFB can only be ON for one scan so a Positive Edge Pulse
is used to filter the request bits.
30303895 | 00 | 11/2015
METTLER TOLEDO ACT350 Transmitter User's Guide
7-19
3. Acyclic Data Subroutine: Network 4. Network 4 is used for floating point reads of floating point
value such as a Weight or a Tare value from ACT350.
PROFIBUS
a. Set from Network 2.
b. Request set from Network 3 (ON for one scan).
c. Lowest address converted to Hex (256 (Dec) = 0x0100 (Hex).
d. Floating Point Word size in Bytes and 4 byte array where returned value will be placed.
e. Status Flags monitored in following network.
f.
Returned status and number of bytes actually returned.
4. Acyclic Data Subroutine: Network 5. Network 5 sets the Result flags for the Floating Point
Read. These flags are displayed in the Acyclic Variable Access table, and can be used
elsewhere in the program.
7-20
METTLER TOLEDO ACT350 Transmitter User's Guide
30303895 | 00 | 11/2015
5. Acyclic Data Subroutine: Network 6. Network 6 processes the Floating Point result:
a. If a valid read has taken place, then copy the raw byte data into a Floating Point tag for use
in the program.
b. If there was a problem with the read, then flag it by moving -9999.0 into the floating point
tag.
c. Regardless of the result, clear the request when the message function has completed.
6. Acyclic Data Subroutine: Network 7. Network 7 is used for writing a floating point value such as
Preset Tare value to the ACT350.
a. Set from Network 2 including variable index.
b. Request set from Network 3 (ON for one scan).
c. Lowest address converted to Hex (256 (Dec) = 0x0100 (Hex).
d. Floating Point Word size in Bytes and 4 byte array where value to be sent was placed in
Network 2.
e. Status Flags monitored in following network.
f.
30303895 | 00 | 11/2015
Returned status.
METTLER TOLEDO ACT350 Transmitter User's Guide
7-21
PROFIBUS
7. Acyclic Data Subroutine: Network 8. Network 8 sets the Results flags for the Floating Point
Write. These flags are displayed in the Acyclic Variable Access Table and can be used
elsewhere in the program.
8. Acyclic Data Subroutine: Network 9. Use Network 9 to process floating point result to clear the
request when the message function has completed regardless of whether a valid write has
taken place or if an error was encountered.
7-22
METTLER TOLEDO ACT350 Transmitter User's Guide
30303895 | 00 | 11/2015
9. Acyclic Data Subroutine: Network 10. Use Network 10 to send a byte long flag (0x01) to
trigger a command such as Tare, Clear or Zero.
a. Set from Network 2 including variable index.
b. Request set from Network 3 (ON for one scan).
c. Lowest address converted to Hex (256 (Dec) = 0x0100 (Hex).
d. Value to be sent in Bytes. 1 Byte array where value to be sent was placed in Network 1.
e. Status Flags monitored in following network.
f.
Returned status.
10. Acyclic Data Subroutine: Network 11. Network 11 sets the Results flags for the 1 Byte Write.
These flags are displayed in the Acyclic Variable Access Table and can be used elsewhere in (e)
the program.
30303895 | 00 | 11/2015
METTLER TOLEDO ACT350 Transmitter User's Guide
7-23
PROFIBUS
11. Acyclic Data Subroutine: Network 12. Use Network 12 to process 1 Byte Write result to clear the
request when the message function has completed regardless of whether a valid write has
taken place or if an error was encountered.
12. The Acyclic Data Sample program can be exercised using the Acyclic_Command Variable
Access Table (VAT)
a. Any Floating Point Read data is displayed here
b. Floating Point data to be sent by Preset_Tare command
c. Index values sent for all commands are displayed here
d. Sample Commands – set the bit (one at a time) to send the corresponding command
e. Floating Point Read message status
f.
Floating Point Write message status
g. Byte Command message status
7-24
METTLER TOLEDO ACT350 Transmitter User's Guide
30303895 | 00 | 11/2015
30303895 | 00 | 11/2015
METTLER TOLEDO ACT350 Transmitter User's Guide
7-25
A
Parameter Values and
Access
This appendix covers
• Connection
• Commands
• Variables List
A.1.
The COM serial interface allows access to all the setup parameters when a PC Client runs a
program such as HyperTerminal.
Connection
In order to access the variables in the ACT350, the COM Service port must be used.
Make sure the serial port of the PC matches the parameters selected for the COM port. This includes
the baud rate, data bits, parity bit, and 1 stop bit.
Connect an RS-232 cable between the remote client PC and the COM Service port of the ACT350.
Open a program to communicate with the terminal (such as HyperTerminal). Refer to the
Commands section to understand how the commands should be structured.
A.2.
Commands
The ACT350 supports two commands - Read and Write. Some variables are read only and some
can be both read and written. A response is always sent after a Read request or a Write command.
If a valid format and variable are requested in a Read, Response 1 from below will be sent. If the
format is incorrect or a bad variable name is requested, an error like Response 2 will be sent. A
Write command will receive either an acknowledge (ASCII <ACK> - 06xh) for an accepted
command or a negative acknowledgement (ASCII <NAK> - 15xh) for an invalid command or data.
A Space character is required between the index number and data that is being sent. This
characters is shown as <SP> (20xh) in the examples. All commands and responses are
terminated with a Carriage Return and a Line Feed character. These characters are shown as
<CR>< LF> (0Dxh, 0Axh).
30303895 | 00 | 11/2015
METTLER TOLEDO ACT350 Transmitter User's Guide
A-1
A.2.1.
Individual Variables
Parameter Values and Access
The PC program can connect with the ACT350 to read and write specific variables per the following
examples. The list of index numbers is given in the next section.
Read request:
R(index#)<CR><LF>
Read filter value: R117<CR><LF>
Response 1 (valid): R117<SP>1<CR><LF>
Read filter value: R177<CR><LF>
Response 2 (error): R177<SP> Error: Invalid Request<CR><LF>
Write request:
W(index#)<SP>xxxxx<CR><LF>
Write Comparator Limit 1
value : W202<SP>42.75<CR><LF>
Response 1 (valid): <ACK><CR><LF> (data is accepted)
Response 2 (error): <NAK><CR><LF> (data or variable is invalid)
A.3.
Variables List
Table A-1 lists each of the setup parameters shown when the Setup mode is programmed. A
descriptive name is included, followed by a list of the selections with corresponding selection
values.
Table A-1: ACT350 Setup Parameters
Index
Descriptive Name
Selections and Values
Scale (Read and Write)
100
Entire Scale Block
101
Name 0000000
[Default]
102
Type A: Analog
[Default]
103
0: None
1: Canada
Approval
2: OIML
3: USA
[Default]
Capacity and Increment
104
105
A-2
METTLER TOLEDO ACT350 Transmitter User's Guide
0: g
Units 1: kg
2: lb
[Default]
Capacity 1-100000 Range
30303895 | 00 | 11/2015
Index
Descriptive Name
Selections and Values
60
106
0: 0.0001
1: 0.0002
2: 0.0005
3: 0.001
4: 0.002
5: 0.005
6: 0.01
7: 0.02
8: 0.05
9: 0.1
Increment Size
10: 0.2
11: 0.5
12: 1
13: 2
14: 5
15: 10
16: 20
17: 50
18: 100
19: 200
107
Over Capacity 0-99 Divisions
Blanking 5 Divisions
GEO
109
Preset Tare -1.0
110
Power-up Mode 0: Restart
(Zero) 1: Reset
111
[Default]
[Default]
[Default]
[Default]
0-98 Divisions
Under Zero Blanking 5 Divisions
[Default]
99
Function Disabled
[Default]
112
0: Disabled
Power Up Zero 1: ±2%
2: ±10%
[Default]
113
0: Disabled
Pushbutton Zero 1: ±2%
2: ±20%
114
30303895 | 00 | 11/2015
0-31
16
108
[Default]
1-30 Range per definition below
Motion Range 1: 0.1 Division
2: 0.2 Division
METTLER TOLEDO ACT350 Transmitter User's Guide
A-3
Parameter Values and Access
Index
Descriptive Name
Selections and Values
3: 0.3 Division
10: 1 Division
30: 3.0 Divisions
[Default]
115
0-10 Range per definition below
0: Disabled
1: 0.1 Seconds
No-motion Interval
2: 0.2 Seconds
3: 0.3 Seconds
[Default]
10: 1.0 Seconds
116
0-99 Seconds Range
0: No waiting
Timeout
[Default]
3: 3 Seconds
99: Waiting until no motion
117
Limit Frequency
0.40 Hz to 20.00 Hz Range
1.0 Hz
[Default]
118
Weighing Mode
0: Normal
1: Dynamic
119
[Default]
0: Very Stable
1: Stable
Environment 2: Standard
3: Unstable
4: Very Unstable
[Default]
Application (Read and Write)
200
Entire Application
Block
201
0: None
[Default]
1: Use Comparator 1
2: Use Comparators 1&2
Comparator Used 3: Use Comparators 1, 2 & 3
4: Use Comparators1, 2. 3 & 4
5: Use Comparators 1, 2, 3, 4
&5
202
Comparator 1 Limit 0
203
Comparator 2 Limit 0
204
Comparator 3 Limit 0
205
Comparator 4 Limit 0
206
Comparator 5 Limit 0
207
A-4
METTLER TOLEDO ACT350 Transmitter User's Guide
Input 1 Polarity
0: + True
1: - True
[Default]
30303895 | 00 | 11/2015
Index
Descriptive Name
Selections and Values
208
0: None
1: Clear tare
Input 1 Assignment
2: Tare
3: Zero
[Default]
209
Input 2 Polarity Same as Input 1 Polarity
210
Input 2 Assignment Same as Input 1 Assignment
211
Input 3 Polarity Same as Input 1 Polarity
212
Input 3 Assignment Same as Input 1 Assignment
213
214
215
216
217
218
Output Polarity
0: + True
1: - True
0: None
1: Center of Zero
2: Comparator 1
3: Comparator 2
4: Comparator 3
5: Comparator 4
Output 1 Assignment
6: Comparator 5
7: Fault
8: Motion
9: Net
10: Over Capacity
11: Under Zero
[Default]
[Default]
Output 2 Assignment
Same selections and default as
Output 1
Output 3 Assignment
Same selections and default as
Output 1
Output 4 Assignment
Same selections and default as
Output 1
Output 5 Assignment
Same selections and default as
Output 1
Terminal (Read and Write)
300
301
302
303
30303895 | 00 | 11/2015
Entire terminal Block
Serial Number NULL
0: Disabled
1: 1 Minute
Disable Display
2: 10 Minutes
3: 30 minutes
Language
0: English
1: Chinese
[Default]
[Default]
METTLER TOLEDO ACT350 Transmitter User's Guide
A-5
Index
Parameter Values and Access
304
305
306
Password Protect
Selections and Values
0: Disabled
1: Enabled
[Default]
Password "000000"
Pushbutton
[Default]
0: Disabled
1: Enabled
[Default]
Communication (Read and Write)
400
401
Entire
Communication
Block
COM Assignment 0: None
0: 300
402
1: 600
2: 1200
3: 2400
COM Baud Rate 4: 4800
5: 9600
6: 19200
7: 38400
8: 57600
9: 115200
403
404
405
406
407
408
409
A-6
Descriptive Name
[Default]
0: 8 Bits
1: 7 Bits
[Default]
0 – None
COM Parity 1 – Even
2 – Odd
[Default]
COM Data Bits
Fieldbus Assignment 0: SAI
Fieldbus Format
0 – 1 Block Format
1 – 2 Block Format
0 – Automatic
Byte Order 1 – Big Endian
2 – Little Endian
Node Address
DHCP Client
[Default]
PROFIBUS DP : 1- 125
1
[Default]
0: Disabled
1: Enabled
[Default]
410
IP Address 192.168.000.002
411
Subnet Address 255.255.255.000
412
Gateway Address 192.168.000.001
METTLER TOLEDO ACT350 Transmitter User's Guide
[Default]
30303895 | 00 | 11/2015
Index
413
414
415
Descriptive Name
Selections and Values
Station Name "ACT350"
MAC Address
18 byte string
"xx:xx:xx:xx:xx:xx"
Fieldbus Acyclic 0: Enabled
Maintenance (Read only)
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
Entire Maintenance
Block
Calibration Changes
0-200 Range
0
[Default]
Weighment Counter
0-50000 Range
0
[Default]
Weighment Start 0-100% of Span
Threshold 90%
[Default]
0-100% of Span
Weighment Reset 10%
[Default]
Threshold Should be less than Start
Threshold
Zero Commands 0-50000 Range
Counter 0
[Default]
Zero Failures 0-50000 Range
Counter 0
[Default]
Zero Drift Counter 0
[Default]
0-100% of Span
5
[Default]
A/D Overload 0-50000 Range
Counter 0
[Default]
A/D Underload 0-50000 Range
Counter 0
[Default]
Scale Overload 0-50000 Range
Counter 0
[Default]
Scale Underload 0-50000 Range
Counter 0
[Default]
Watchdog Failures 0-50000 Range
Counter 0
[Default]
Zero Drift Threshold
Target Achieved 0x0 – 0x70000000
Counter 0
[Default]
Calibration (Read and Write)
600
30303895 | 00 | 11/2015
Entire Calibration
METTLER TOLEDO ACT350 Transmitter User's Guide
A-7
Index
Descriptive Name
Selections and Values
Parameter Values and Access
Block
601
602
603
[Default]
Zero Counts 0
[Default]
Very Low Calibration 25.0
Weight Available for 5 point linearity
604
[Default]
Very Low Calibration 400000
Counts Available for 5 point linearity
605
25.0
[Default]
Low Calibration
Weight Available for 4 & 5 point
linearity
606
400000
[Default]
Low Calibration
Available for 4 & 5 point
Counts
linearity
607
25.0
[Default]
Mid Calibration
Weight Available for 3, 4 & 5 point
linearity
608
400000
[Default]
Mid Calibration
Counts Available for 3, 4 & 5 point
linearity
609
50.0
[Default]
High Calibration
Available for all linearity
Weight
selections
610
800000
[Default]
High Calibration
Counts Available for all linearity
selections
611
CalFree Total Cell 60.0
Capacity
612
0: g
CalFree Unit 1: kg
2: lb
614
A-8
0: None
1: 3 Point
Linearity
2: 4 Point
3: 5 Point
METTLER TOLEDO ACT350 Transmitter User's Guide
CalGEO Code
0 – 31 Range
16
[Default]
[Default]
[Default]
30303895 | 00 | 11/2015
B
Standard Automation
Interface
B.1.
Overview
This appendix covers
•
•
•
•
•
•
•
Overview
General Structure
Data Format
Byte and Word Order of Data
Floating Point Numbers
Test Mode
The Standard Automation Interface (SAI) is a protocol designed to exchange data
between METTLER TOLEDO devices and automation systems. The goals of this
interface are to provide: 1) a common data layout for load cells, terminals, and other
devices regardless of the physical interface or automation network used, 2) a single
protocol for the convenience of automation integrators, control system programmers,
and our automation customers, and 3) a tiered approach to create a flexible protocol
for diverse devices.
Asynchronous Format
Figure B-1: Overview of a Control System
30303895 | 00 | 11/2015
METTLER TOLEDO ACT350 Transmitter User's Guide
B-1
Standard Automation Interface
B.2.
General Structure
The protocol has two primary data types – cyclic data and asynchronous data (also known as
acyclic or explicit messaging).
B.2.1.
Cyclic Data
Figure B-2: Controller/Device Read-Write Overview
The cyclic data is broken in sections of data called blocks. Each block of data is 4 words (16 bits
each) in length. The data within these blocks can express numeric values, string values, or
individual bits that represent state/command depending on the type of block specified. Two fixed
formats (1 Block and 2 Block) are provided for ACT350. The ACT350 supports 4 words in and 4
words out in the 1 Block format and 8 words in and 8 words out in the 2 Block format. The number
of input words (data sent from the device to the process controller) and output words (data sent
from the process controller to the device) always match. This limits the number of configurations to
a reasonable amount.
•
1 Block format - 1 Block In & 1 Block Out
•
2 Block format - 2 Blocks In & 2 Blocks Out
The two types of cyclic blocks supported on the ACT350 are floating point and status/command.
Numeric values will be sent via floating point blocks as opposed to integer or other types because
the decimal point and sign are included and do not require special data handling. Status/command
data is grouped together in 16 bit words to conserve space.
B.2.2.
B-2
Two Types of Cyclical Blocks

Floating Point

Status / Command
METTLER TOLEDO ACT350 Transmitter User's Guide
30303895 | 00 | 11/2015
Figure B-3: Combinations of possible cyclical data types by block data format
B.2.2.1.
Floating Point Block
The floating point blocks are used to exchange numeric data such as weight and its associated
scale status. The floating point block consists of a 32 bit floating point value and two 16 bit words.
The use of this block is slightly different depending on the source of the data (the device or the
control system).
A single block of data sent by the device to the control system is mapped as follows:
Floating Point Data Block (Read)
Word 0
32 bit (requested) Floating point value
Word 1
Word 2
16 bit Device status
Word 3
16 bit Response value
Figure B-4: Minimum Floating Point Data Block (Read)
The device’s Read Floating Point Data Block contains the floating point value requested by the
control system from its Write Floating Point Data Block. It uses 16 bits in the third word to provide
status bit information based on the command (for example, scale status such as motion or center
of zero). The last the 16 bit Response value is used to inform the control system what the contents
of the floating point value are (example: gross weight of scale 1).
A single block of data sent by the control system to the device is mapped in a similar manner:
Floating Point Data Block (Write)
Word 0
Word 1
32 bit Floating point value - optionally used with Command &
Channel Indicator
Word 2
16 bit Channel Mask
Word 3
16 bit Command value
Figure B-5: Minimum Floating Point Data Block (Write)
The control system’s Write Floating Point Data Block is used to issue commands to the device.
These commands can be as simple as the request for specific data to be reported in the Read
30303895 | 00 | 11/2015
METTLER TOLEDO ACT350 Transmitter User's Guide
B-3
Standard Automation Interface
Floating Point Data Block - for example, report net weight. It can also contain commands to write a
value into the device's data – for example, set Comparator Limit 1 = 100. In this case, the optional
floating point value is used to send the value with the command. The Channel Mask provides a
method to issue the same command to multiple channels in the device. The ACT350 is a single
channel device. The last word contains the 16 bit Command value to instruct the device what
command is issued.
Both the Read Floating Point Block and the Write Floating Point Block have a similar structure for
their Response Value and Command Value words. The Write block sends its commands and the
device responds with the same value when the command is successful. Details about the use of
these words is described in section B.3, Data Format.
B.2.2.2.
Status Block
The status blocks are used to provide state (on/off) data. The status blocks are structured to support
three sets of status words. Examples of data provided through status blocks include alarms,
physical I/O, target control, comparator state, or application specific states.
The status data sent by the device to the control system is similar to the layout used to provide the
status information in the floating point block. Because there is available space, three sets of status
data and 1 word to indicate what data is provided are included in this type of block:
Status Block - Read
Word 0
Status Group 1
Word 1
Status Group 2
Word 2
Status Group 3
Word 3
Response value
Figure B-6: Status Block (Read)
The command data sent by the control system to the device requires less space. In order to
maintain a consistent layout (input vs. output block size), words 1 - 3 are currently reserved
until/unless these words are needed to provide information from the control system in the future:
Status Block - Write
Word 0
Reserved
Word 1
Reserved
Word 2
Reserved
Word 3
Command value
Figure B-7: Status Block (Write)
B.2.3.
Asynchronous Data (Explicit or Acyclic Messaging)
The asynchronous data does not have the same size/layout restrictions as cyclic data due to its
negative impact on network performance (bandwidth and speed). This format uses special
message instructions in the control system to immediate execute the command specified within its
B-4
METTLER TOLEDO ACT350 Transmitter User's Guide
30303895 | 00 | 11/2015
configuration. These messages and their instructions are control system dependent. Within the
configuration of the instruction, a variable or memory space is defined for the data exchanged
through the execution of the message. The ACT350 supports the Direct access data format for
Asynchronous data.
The Direct access data does not require the variable name within the data. The layout for direct
access data is shown Figure B-8
Figure B-8: Explicit Messaging Direct data format
B.3.
Data Format
The formats of the data available in the protocol have been designed to provide sets of data based
on ACT350 functionality. Data type and space required is dependent on the selected format. The
Act350 can use either the 1 block format or the 2 block format.
B.3.1.
1 Block Format
The SAI 1 Block Format is the basic format in the SAI protocol. The user selection of this format
supports three typical use cases
•
Some control network interfaces have limited space
•
Some devices have limited data
•
Some customers want limited data
In order to insure that less complex applications are capable of using/providing this data, advanced
features like user-defined data mapping are not included in this format.
The objective is to provide basic data with little to no special coding. In addition, data size is limited
to insure good communication performance and to comply with as many automation networks as
possible.
B.3.1.1.
Cyclic Data Operation
The cyclic data of the 1 Block Format should be sent with minimal device configuration and
minimal control system integration. Once the device is successfully added to the control system
network, it should immediately begin sending its default cyclic data (typically gross weight
30303895 | 00 | 11/2015
METTLER TOLEDO ACT350 Transmitter User's Guide
B-5
Standard Automation Interface
information). The 1 Block Format always consists of a single Read Floating Point Data Block and a
single Write Floating Point Data Block.
Figure B-9: The 1 Block Format data layout
B.3.1.1.1.
Device to Control System Operations (Read Data)
The 1 Block Format requires the device to repeatedly send a 4 word block of input data to the
control system. This data is sent automatically as part of the automation network’s update of cyclic
data (scan). The structure of the data provided is based on the Floating Point Block:
Figure B-10: Floating Point Read Block
This block contains three parts: 2 words for the floating point value (word 0-1), 1 word to provide
device status bits (word 2), and1 word for the individual status bits that are used to identify the
source and type of data being sent in the floating point value (word 3).
By default, if the control system sends no data in its Write Floating Point Data Block (the output
data is all zeroes), the device will send its gross weight data for channel 1, the scale status word
for this channel, and a response value word with all bits set to 0.
B.3.1.1.2.
Floating Point Value (Word 0 & 1)
The floating point value is single precision. The order of the data in the floating point value will
generally be determined by configuration of the byte swap and word swap parameters. The default
setting of these parameters is typically based on the type of automation interface used. Refer to
section B.3, Data Format, for additional details.
B.3.1.1.3.
Scale Status Group (Word 2)
The device status is a composite status word that contains individual bits to indicate the state of
various scale or device specific binary (on/off) values. These include error and data validation bits
to make it possible to determine when the data received is good and can be safely used. It also
contains command status bits to provide some information on the state of a command issued in
the floating point write block.
B-6
METTLER TOLEDO ACT350 Transmitter User's Guide
30303895 | 00 | 11/2015
Bit 0,1
Sequence bits: These are used as sequence toggle bits. As commands are sent by the control
system (and seen by the device), the device increments their value as an indication that a
command has been seen and acted on
These bits can be used during a sequence of commands to insure that there have been no
sequencing errors in the request and the response of data. They are updated on every NEW
command
Bit 2
30303895 | 00 | 11/2015
Heart Beat: To insure that the device is working as expected and updating data in Words 0, 1
and 2, this heart beat bit is toggled between off and on states. The frequency is dependent on
the specific device’s ability to cycle this bit. For example, a 1 second heart beat would be
sufficient for most applications
Bit 3
Data Okay: This bit is used to indicate that the data being reported is OK. This bit gets set to 0
when the device is still operational but the scale has a critical error (for example over
capacity) and the value being reported cannot be guaranteed to be valid.
Bit 4
Alarm Condition: This bit is true when there is an application fault, predictive diagnostics alarm,
or command received cannot be executed as requested. If this bit is true the control system
should use a Field Value command to determine the nature of the failure.
Bit 5
Center of Zero: This bit is true when the gross weight value is at a value of zero +/- one quarter
of a weights and measures verification interval denoted as "e"
Bit 7
Net Mode: This bit is true when the weight reported by the device has had a tare taken and the
net weight is different than the gross.
Bit 8
Alternate weight unit: This bit indicates when a weight unit other than the primary weight unit is
being used by the device … if this bit is set to a “1” an alternate weight unit is in use
Bit 9 -15
Device Specific bits: These bits are used to provide device specific status information (such I/O
or application status)
METTLER TOLEDO ACT350 Transmitter User's Guide
B-7
Standard Automation Interface
B.3.1.1.4.
Response Word (Word 3)
The Response Word is used to provide feedback on the state of the command issued in the Write
Floating Point Data Block. Depending on what type of command has been sent, this response may
be used to indicate that the command failed, it succeeded, or it was seen and the data requested is
being sent in the floating point value.
The structure of the Response Word is identical to the structure of the Command Word. It consists of
two sets of bits: bits 11-14 which are used to indicate the channel value and bits 0-10 which are
used to indicate the response value. Bit 15 is used to indicate an error condition. It is set to "0" if
the device can provide the desired data or comply with the requested command. If it cannot, then
this bit is set to a "1" to indicate an error. A full description of the possible error codes are described
in Commands section.
The channel indicator bits are intended for devices which support multiple sensors or scales,
allowing an individual device to support up to a maximum of 16 channels. Single channel (scale
or load cell) devices such as the ACT350 will always use 0000 as their default channel value.
Bit #
Data
0000
Channel 1
15
MSB always 0
0001
n/a
14
MSB of channel
0010
n/a
13
0011
n/a
12
0100
n/a
11
LSB of channel
0101
n/a
10
MSB of response value
0110
n/a
9
0111
n/a
8
1000
n/a
7
1001
n/a
6
1010
n/a
5
1011
n/a
4
1100
n/a
3
1101
n/a
2
1110
n/a
1
1111
n/a
0
LSB of response value
Figure B-11: Response Word Layout
The Response bits have values to indicate the current state of the command sent by the control
system in its request for data or in its attempt to trigger a particular device function. The structures
of the Command Word and Response Word match so that any command issued in the Write will
have the same exact value in the Read response when the device successfully recognizes and
completes the command.
B-8
METTLER TOLEDO ACT350 Transmitter User's Guide
30303895 | 00 | 11/2015
For example, if the control system requests that gross weight of scale 1 be sent in its command
data, the device places this weight information in its floating point and places a response value
equal to the command value into its response word.
Additional details of possible responses are provided in Appendix C, Cyclic Commands, and
Appendix D, Acyclic Commands.
B.3.1.1.5.
Control System to Device Operations (Write Data)
The 1 Block Format provides a single 4 word block of output data from the control system. The
structure of the data provided is based on the Floating Point Write Block.
Figure B-12: Floating Point Write Block
This block contains three parts: 2 words for an optional floating point value (word 0-1), 1 word to
provide the ability to send a single command to multiple channels scale via the Channel mask
(word 2), and 1 command word for the command & channel indicator bits used to identify the data
desired by the control system (word 3).
B.3.1.1.6.
Floating Point Value (Word 0 & 1)
The floating point value is single precision. Layout of FP value bits are described in the Byte Order
section of this document.
B.3.1.1.7.
Channel Mask (Word 2)
The Channel Mask only applies to devices that support multiple channels and is not typically
available for all commands. The command's channel is identified by bits 11-14 in the Command
Word. If a device only has a single channel, such as the ACT350, the channel mask should not be
used since the default device channel will be used in all cases and would be selected from the
command word. The Channel Mask should be set to all zeroes when not in use.
Bit#
0
30303895 | 00 | 11/2015
Data
1 = Apply command to channel 1
1
n/a
2
n/a
3
n/a
4
n/a
5
n/a
6
n/a
7
n/a
METTLER TOLEDO ACT350 Transmitter User's Guide
B-9
Standard Automation Interface
B-10
B.3.1.1.8.
Bit#
Data
8
n/a
9
n/a
10
n/a
11
n/a
12
n/a
13
n/a
14
n/a
15
n/a
Command Word (Word 3)
The Command Word consists of two sets of bits: bits 11-14 which are used to indicate which
channel value and bits 0-10 which are used to indicate the command value. Bit 15 is always set to
0 to keep the overall value of the word positive when evaluated as an integer.
The channel indicator bits are intended for devices which support multiple sensors or scales,
allowing an individual device to support up to a maximum of 16 channels. Single channel (scale
or load cell) devices will always use 0000 as their default channel value. These bits indicate which
channel the command should be applied to.
METTLER TOLEDO ACT350 Transmitter User's Guide
30303895 | 00 | 11/2015
Word 3
Channel Indicator
Bit #
Data
0000
Channel 1
15
MSB always 0
0001
n/a
14
MSB of channel
0010
n/a
13
0011
n/a
12
0100
n/a
11
LSB of channel
0101
n/a
10
MSB of command value
0110
n/a
9
0111
n/a
8
1000
n/a
7
1001
n/a
6
1010
n/a
5
1011
n/a
4
1100
n/a
3
1101
n/a
2
1110
n/a
1
1111
n/a
0
LSB of command value
Figure B-13: Command Word Layout
The Command bits 0-10 are used by the control system to select the reported data from the device
data in the Floating Point Read Block, change device data values, or issue operational commands
such as tare, zero, etc. Details of available commands are provided in Appendix B, Cyclic
Commands, and Appendix C, Acyclic Commands.
The value used in the Command Word is a combination of the command value and the channel
value. This combination creates a specific command to a targeted channel, for example report
gross weight of channel 2.
To calculate the word’s complete integer value, the command value should be added to the channel
value:
Command Word = Channel Value + Command Value
Channel #
Bit value
Integer value
1
0000
0
Figure B-14: Channel Value
30303895 | 00 | 11/2015
Command
Bit value
Integer value
Report Default Data (gross wt)
000 0000 0000
0
METTLER TOLEDO ACT350 Transmitter User's Guide
B-11
Standard Automation Interface
Command
Bit value
Integer value
Report Rounded Gross Weight
000 0000 0001
1
Report Rounded Tare Weight
000 0000 0010
2
Report Rounded Net Weight
000 0000 0011
3
Report raw counts
000 0000 1010
10
Figure B-15: Command Value
Command
Command value
Channel value
Word value
Report Gross Weight, Channel 1
0
0
0
Report Net Weight, Channel 1
3
0
3
Report raw counts, Channel 1
10
0
10
Figure B-16: Command Word Values
By default, if the control system has no data (all "0") in its write block, the device will see this as a
command to report its default data (typically gross weight) for the first channel.
B.3.2.
2 Block Format
The SAI 2 Block Format builds on the format structure used by the 1 Block Format; however it
provides support for two blocks of input data and two blocks of output data. This fixed format
requires no configuration. This format was designed for applications where the device supports
additional status information. Status groups provide the means for the PLC to monitor status of
RedAlert Alarms and comparators.
B.3.2.1.
Cyclic Data Operation
The cyclic data of the 2 Block Format supports two read blocks and two write blocks - a single
Floating Point Data Block and a single Status Block for each. Like the 1 Block Format, the 2 Block
Format should provide a default configuration that immediately begins to send default cyclic data
(with little to no coding).
Figure B-17: 2 Block Data Format Layout
B.3.2.1.1.
Device to Control System Operations (Read Data)
The 2 Block Format requires the device to repeatedly send two (4 word) blocks of input data to the
control system. This data is sent automatically as part of the automation network’s update of cyclic
data (scan). The structure of the data provided consists of one Floating Point Read Block and one
Status Read Block:
B-12
METTLER TOLEDO ACT350 Transmitter User's Guide
30303895 | 00 | 11/2015
Figure B-18: 2 Block Format Read
Block 1 contains three parts: 2 words for the floating point value (word 0-1), 1 word for the scale
status bits (word 2), and 1 response word for the individual status bits that are used to identify the
source and type of data being sent in the floating point value (word 3).
By default, if the control system sends no data in its Write Floating Point Data Block (the output
data is all zeroes), the device will typically send its gross weight data for channel 1, the scale
status word for this channel, and a response word that indicates that the floating point value in
words 0 & 1 is the gross weight for channel 1 (all bits set to 0).
Block 2 contains four parts: 3 separate status group words (words 4-6) and a response word
(word 7) for the individual status bits that are used to identify the source and type of data being
sent in the status words.
B.3.2.1.2.
Floating Point Value (Word 0 & 1), Scale Status Group (Word 2) and Response Word (Word 3)
Words 0, 1, 2 and 3 are identical to what has been described under the 1 block section above.
B.3.2.1.3.
Status Group 1, Status Group 2 or Status Group 3 (Word 4 – Word 6)
The Status Group 1, Status Group 2, and Status Group 3 words can contain specially group bits of
status information. The Command Word in the Write Status Block is used by the control system to
tell the device what data is desired in these words. Each command used to request status data in
these words represents a particular combination (refer to the status block commands in the
Commands section) of the following status words:
B.3.2.1.4.
Status Group 1 Alarms (Default, word 4)
The critical alarm status bits are sent as part of the default status block when a status block
command "0" is sent. If the control system does not place any data in the Write Command word,
the device will send this data in word 4.
Bit #
30303895 | 00 | 11/2015
RedAlert Alarms
0
n/a
1
Out of A/D range over/under
METTLER TOLEDO ACT350 Transmitter User's Guide
B-13
Standard Automation Interface
Bit #
B-14
RedAlert Alarms
2
Checksum failure
3
Weight blocked
4
n/a
5
Customer-defined overload
6
Customer-defined underload
7
n/a
8
Zero out of range
9
n/a
10
n/a
11
Weights and measures failure
12
n/a
13
Test mode
14
Open (always 0)
15
Open (always 0)
Bit 0
n/a
Bit 1
Out of A/D range over/or under: A "1" state occurs when all bits in the A/D buffer equal "1" or
when all the bits in the A/D buffer equal "0". In the product a timer will be necessary to prevent
against (meaningless) instantaneous alarm indications
Bit 2
Checksum Failure: A checksum analysis of memory does not yield the expected result.
Bit 3
Weight Blocked: The weight data does not change appreciably over a defined period of time.
The assumption is that all scales have drift and noise from the environment, a non-changing
condition would indicate that the scale is not moving as expected because it is either blocked
or is not responding to the MCU (under conditions when there are no proactive diagnostics
available to discover the root cause.
Bit 4
n/a
Bit 5
Overload: The weight is equal to or greater than a "customer-programmed" limit either on the
scale or individual sensor's capacity (in a multi-sensor system). Overload is a conditional
limit but in many cases can lead to catastrophic errors such as mechanical breakage or
personal injury
Bit 6
Under load: The weight is under the "customer-programmed" limit on the scale / sensor (under
zero but still within A/D range)
Bit 7
n/a
Bit 8
Zero Out of Range – A control system, or an operator attempts a zero command and the
device does not accept the command because the weight is outside of the specified (setup)
limits or the weights and measures limits. This typically occurs when the customer
inadvertently attempts to zero the scale when the object being measured has not been
removed.
Bit 9
n/a
METTLER TOLEDO ACT350 Transmitter User's Guide
30303895 | 00 | 11/2015
Bit 10
Bit 11
B.3.2.1.5.
n/a
Weights and Measures failure – An algorithm in the sensor or scale detects that the product is
no longer in compliance with weights and measures regulations
Bit 12
n/a
Bit 13
Test Mode – This bit is set to 1 when the device is in a mode in which live data is replaced
with special test data.
Bits 14-15
Unused at this time (always 0)
Status Group 2 Alarms (Default, word 5)
These status bits are sent as part of the default status block when a status block command "0" is
sent. If the control system does not place any data in the Write Command word, the device will
send this data in word 5.
Bit #
Bits 0-3
30303895 | 00 | 11/2015
Scale Group 2 Status
0
Unit bit 1
1
Unit bit 2
2
Unit bit 3
3
Unit bit 4
4
MinWeigh Error
5
Range bit 1 (always 0)
6
Range bit 2 (always 0)
7
In Set Up
8
Power Up Zero Failure
9
n/a
10
Always 1
11
Open (always 0)
12
Open (always 0)
13
Open (always 0)
14
Open (always 0)
15
Open (always 0)
Unit bits 1-4 are used to indicate the weight unit based on the values shown
Bit 3
Bit 2
Bit 1
Bit 0
Value
0
0
0
0
g
0
0
0
1
kg
0
0
1
0
lb
0
1
1
1
Special/custom
METTLER TOLEDO ACT350 Transmitter User's Guide
B-15
Standard Automation Interface
B.3.2.1.6.
Bit 4
MinWeigh Error is used to indicate when scale is below acceptable minimum weighing
range
Bit 5 & 6
Range bits 1 & 2 are always 0, because the ACT350 is single range device
Bit 7
In Setup: Used to indicate when scale is in setup mode
Bit 8
Power up zero failure: Used to indicate when scale has not been able to complete its
power-up restore/reset of zero
Bit 9
n/a
Bit 10
Always 1
Bit 11-15
Unused (always 0)
Comparator Status Group 2
The comparator application status bits are sent when a status block command that contains this
status word in its combination is sent in the Write Command word. There are two groups of these
comparator bits. A total of 5 comparators are supported on the ACT350 and bits 0-4 are assigned
within the first group. Bits 5-15 are not supported on the ACT350 within the first group. Bits 0-4 in
the second group are not supported on the ACT350.
Bit #
Data
0
Comparator 1
1
Comparator 2
2
Comparator 3
3
Comparator 4
4
Comparator 5
5
n/a
6
n/a
7
n/a
8
n/a
9
n/a
10
n/a
11
n/a
12
n/a
13
n/a
14
n/a
15
n/a
Figure B-19: Comparator Group 1 Status Bits
B-16
METTLER TOLEDO ACT350 Transmitter User's Guide
30303895 | 00 | 11/2015
Bit #
Data
0
n/a
1
n/a
2
n/a
3
n/a
4
Open
Figure B-20: Comparator Group 2 Status Bits
The comparator status bits turn ON for the listed comparator when the assigned comparison logic is
true. For example, if a comparator is configured for coincidence with 100 kg, when the weight
value is 100 kg the bit would be ON.
B.3.2.1.7.
I/O Status Groups (Default, word 6)
There are multiple commands for input and output status words. On ACT350 versions where
physical I/O are supported the I/O status groups are used to contain a combination of input and
output status bits for I/O. Devices which have no physical I/O can still have variables and logic to
virtually represent inputs and outputs within the device. The ACT350 will provide an invalid
command response to a command for any unsupported I/O groups. The status bits for group 1 are
sent as part of the default status block (in word 6).
Bit #
Data
0
In 1
1
In 2
2
In 3
3
n/a
4
n/a
5
n/a
6
n/a
7
n/a
8
Out 1
9
Out 2
10
Out 3
11
Out 4
12
Out 5
13
n/a
14
n/a
15
n/a
Figure B-21: I/O Group 1 Status Bits
30303895 | 00 | 11/2015
METTLER TOLEDO ACT350 Transmitter User's Guide
B-17
The Input status bits reflect the state of the associated input (ON when ON, OFF when OFF). The
output status bits reflect the state of the associated output (ON when ON, OFF when OFF).
Standard Automation Interface
B.3.2.1.7.1.
Response Word (Word 7)
The Response Word is used to provide feedback on the state of the command issued in the Write
Status Block. Like the Floating Point Response Word, this response may be used to indicate that the
command failed, it succeeded, or it was seen and the data requested is being sent in the status
words of this block.
The structure of this Response Word is identical to the Floating Point Response Word and the
Command Word structures. It consists of two sets of bits: bits 11-14 which are used to indicate the
channel value and bits 0-10 which are used to indicate the response value. Bit 15 is used to
indicate an error condition. It is set to "0" if the device can provide the desired data or comply with
the requested command. If it cannot, then this bit is set to a "1" to indicate an error. A full
description of the possible error codes are described in Commands section.
The channel indicator bits are intended for devices which support multiple sensors or scales,
allowing an individual device to support up to a maximum of 16 channels. Single channel (scale
or load cell) devices will always use 0000 as their default channel value.
Word 7
Channel Indicator
Bit #
Data
0000
Channel 1
15
MSB always 0
0001
n/a
14
MSB of channel
0010
n/a
13
0011
n/a
12
0100
n/a
11
LSB of channel
0101
n/a
10
MSB of response value
0110
n/a
9
0111
n/a
8
1000
n/a
7
1001
n/a
6
1010
n/a
5
1011
n/a
4
1100
n/a
3
1101
n/a
2
1110
n/a
1
1111
n/a
0
LSB of response value
Figure B-22: Status Response Word Layout
The Response bits have values to indicate the current state of the command sent by the control
system in its request for data. The structures of the Command Word and Response Word match so
B-18
METTLER TOLEDO ACT350 Transmitter User's Guide
30303895 | 00 | 11/2015
that any command issued in the Write will have the same exact value in the Read response when
the device successfully recognizes and completes the command.
Additional details of possible responses are provided in the Commands section of this document.
B.3.2.1.8.
Control System to Device Operations (Write Data)
The 2 Block Format requires the control system to send two blocks of output data (one floating
point and one status) to the device automatically as part of the automation network’s update of
cyclic data (scan). The structure of the data provided is fixed as shown in Figure B-23.
Figure B-23: 2 Block Format Write
Block 1 contains three parts: 2 words for an optional floating point value (word 0-1), 1 word to
provide the ability to send a single command to multiple channels scale via the Channel mask
(word 2, always 0000 for ACT350), and 1 command word for the command & channel indicator
bits used to identify the data desired by the control system (word 3).
Block 2 contains two parts: 3 reserved words (in order to maintain a 4 word layout similar to all
other blocks), and 1 command word for the command & channel indicator bits used to identify the
data desired by the control system (word 7). The Status Block Command Word is similar to
Floating Point Block Command Word, however one command is used to request the combination
of three different status words in the read block.
B.3.2.1.9.
Floating Point Value (Block 1, Word 0 & 1), Channel Mask (Block 1, Word 2) and Command Word (Block
1, Word 3)
Words 0, 1, 2 and 3 are identical to what has been described under the 1 Block section earlier.
B.3.2.1.10.
Status reserved (Block 2, Word 4-6)
The Write Status Block only needs the Command Word (word 7) to request the data for the Read
Status Block. These words have been reserved and should be set to "0".
B.3.2.2.
Command Word (Block 2, Word 7)
This Command Word is used to request data for the corresponding Read Status Block. It consists of
two sets of bits: bits 11-14 which are used to indicate which channel value and bits 0-10 which
30303895 | 00 | 11/2015
METTLER TOLEDO ACT350 Transmitter User's Guide
B-19
Standard Automation Interface
are used to indicate the command value. Bit 15 is always set to 0 to keep the overall value of the
word positive when evaluated as an integer.
The channel indicator bits are intended for devices which support multiple sensors or scales,
allowing an individual device to support up to a maximum of 16 channels. Single channel (scale
or load cell) devices will always use 0000 as their default channel value. These bits indicate which
channel the command should be applied to.
Word 7
Channel Indicator
Bit #
Data
0000
Channel 1
15
MSB always 0
0001
n/a
14
MSB of channel
0010
n/a
13
0011
n/a
12
0100
n/a
11
LSB of channel
0101
n/a
10
MSB of command value
0110
n/a
9
0111
n/a
8
1000
n/a
7
1001
n/a
6
1010
n/a
5
1011
n/a
4
1100
n/a
3
1101
n/a
2
1110
n/a
1
1111
n/a
0
LSB of command value
Figure B-24: Command Word Layout
The Command bits 0-10 are used by the control system to select the reported data from the device
data in the Status Read Block. Details of available status block commands are provided in the
Commands section of this document.
Like the Command Word for the Floating Point Block, the value used in the Status Block Command
Word is a combination of the command value and the channel value. To calculate the word’s
complete integer value, the command value should be added to the channel value:
Command Word = Channel Value + Command Value
By default, if the control system has no data (all "0") in its write block, the device will see this as a
command to report its default data for the status block. This is typically RedAlert, Scale Group 2,
and I/O Group 1 status data.
B-20
METTLER TOLEDO ACT350 Transmitter User's Guide
30303895 | 00 | 11/2015
B.4.
Byte and Word Order of Data
Device data order is configurable as part of the PLC interface setup parameters provided in data
format type selection. The default data format selection is "Automatic". With the selection as
Automatic, the byte and word order defaults to a known default based on fieldbus type. The data
format selection allows selection of Little Endian and Big Endian data format selections. These
selections must be made prior to communication operation between the control system and the
device. The Byte Swap and Word Swap selections determine the data order expected during the
communication exchange.
For example, the device may be sending a 4 byte (2 Word) hex data message to the control
system, represented numerically as 0A0B0C0D.
B.4.1.
Little Endian (Byte Swap = No / Word Swap = No)
4 byte hex value …
Memory/ register order
0A 0B 0C 0D
MSD … … LSD
B.4.2.
Data
n
0D
n+1
0C
n+2
0B
n+3
0A
Word 0
Byte 2 = 0C
Byte 1 = 0D
Word 1
Byte 4 = 0A
Byte 3 = 0B
Word 0
Byte 2 = 0A
Byte 1 = 0B
Word 1
Byte 4 = 0C
Byte 3 = 0D
Big Endian (Byte Swap = Yes / Word Swap = Yes)
4 byte hex value …
Memory/ register order
Data
0A 0B 0C 0D
n
0A
n+1
0B
n+2
0C
n+3
0D
MSD … … LSD
Word 0
Byte 2 = 0B
Byte 1 = 0A
Word 1
Byte 4 = 0D
Byte 3 = 0C
The default setting for the Byte Swap and Word Swap parameters is automation interface type
specific.
30303895 | 00 | 11/2015
METTLER TOLEDO ACT350 Transmitter User's Guide
B-21
Standard Automation Interface
Memory Address (A = MSB)
SAI Name
M+3
M+2
M+1
M+0
Native Control System
Fieldbus
Little Endian
A
B
C
D
Rockwell
Ethernet/IP
Siemens
PROFINET,
PROFIBUS
Big Endian
D
C
B
A
Figure B-25: PLC Data Format Options
The Byte / Word Swap configuration step is used to support differences in control system hardware.
This selection allows the device to switch the order of words and bytes within each word so that it
can match the order expected by the control system. There are three possible choices:
•
Automatic
•
No swap
•
Byte & Word swap
The Automatic selection is the default. When Automatic is selected, the byte and word order is
determined by two possible methods – first, each fieldbus type has a known default that is used
until the test command is sent from the control system and second, a test command can be sent
from the control system to put the device into a test state which checks for a specific floating point
value and determines the order based on the way the data is received. The current state of the byte
order is shown as the Current Order.
B.5.
Floating Point Numbers
The floating point numbers exchanged by the Floating Point Blocks follow the IEEE 784 -1985
convention for single precision (32 bit) floating point values.
Word 0
Word 1
B-22
METTLER TOLEDO ACT350 Transmitter User's Guide
00000000
00111110
00000000
00100000
30303895 | 00 | 11/2015
The order of the bytes / words may be affected by the setting of the Byte Swap / Word Swap
parameters. Integers (whole numbers) sent through the floating point blocks should always have
zeroes to the right of the decimal point location (5.00000, for example).
B.6.
Test Mode
If the ACT350 transmitter is put in the automatic byte/word swap mode, a special floating point
command can be sent from the control system to test the communications and make sure the byte
and word order are set to match what it expects. This special command contains data that is byte
and word order independent (the same in every byte).
The control system must place the value 2.76 (0x4030a3d7) in the floating point write value and
send 80h in all four bytes of word 2 and word 3:
Word 0
Word 1
FP value = 2.76
Word 2
Byte 2 = 80
Byte 1 = 80
Word 3
Byte 4 = 80
Byte 3 = 80
The ACT350 will see the special command and then read the data in the floating point bytes to
determine which order the control system is using. Once it determines the order, it changes its
configuration to match and should then respond to the command in same order as the command
data. The response will include the sent value (2.76) so that the control system can verify that the
device is sending data in the expected order.
This test mode can also be used to confirm that the ACT350 is communicating with the control
system even when other parts of the ACT350 may not be configured or operational (for example,
the scale not yet calibrated). If the ACT350 is not in the automatic mode when the test command is
sent, it will use the order specified in its configuration.
The Test Mode bit (13) of the RedAlert status bits will turn on when the ACT350 is in the test mode.
In this state, the ACT350 will also accept the other test commands and respond with pre-defined
test data instead of normal operational data. For example, when in test mode, the ACT350 will
respond with an expected fixed weight value instead of the actual weight so that test scripts can be
written against these known values. This also provides methods for the control system to force
status bits to a specific state for the same reason.
Until the ACT350 is told to exit test mode or power is cycled on the ACT350, it will remain in test
mode (Test Mode = 1) and indicate that data is invalid (Data OK = 0). Once the command to exit
test mode is received or the ACT350's power is cycled, it will revert to sending operational data
instead of test data. To exit test mode, the control system must send the Exit Test Mode command
by sending 88h in both bytes of Word 3. If the Custom Format is used and there is no Floating
Point Block, the Test Command can be sent through the Write Status Block. If both block types are
present, only one command in one of the blocks is required to place the device in or out of test
mode.
Word 3
30303895 | 00 | 11/2015
Byte 2 = 88
Byte 1 = 88
METTLER TOLEDO ACT350 Transmitter User's Guide
B-23
Standard Automation Interface
B.6.1.
Floating Point Test Commands for "Report" values
If the control system sends a floating point command to report a value when in test mode, the
ACT350 will respond with fixed data instead of valid data (it may be unable to provide valid data
during the test). A simple formula will be used to calculate what this fixed value should be:
5000.11 + Command Value = Reported data value for command
For example, if the command to report gross weight is sent after the ACT350 is placed in test mode,
the ACT350 should provide the proper response value and its floating point value for gross weight
should be 5000.11 (5000.11 + 0 = 5000.11). If Net weight is requested, the ACT350 should
send 5003.11 (5000.11 + 3 = 5003.11).
B.6.2.
Floating Point Test Commands for Scale Status bits
Special test commands are available to turn on and off the scale status bits provided in the floating
point blocks when the ACT350 has been placed in test mode. Refer to the list provided in this
document. The responses for these commands will also follow the formula above – if a trigger
command of "1" is sent, the response value in the floating point will be "5001.11". If the command
value "0" is sent the response value will be "5000.11".
B.6.3.
Status Block Test Commands
Special test commands are available to turn on and off the status bits provided in the status blocks
when the device has been placed in test mode. A special error response is provided when a test
command is sent for status bits that have not been requested. Refer to the list provided in
Commands section.
B.6.4.
Test Variables for Acyclic and Variable Block Test Commands
Acyclic and variable block test commands do not require the ACT350 to be in test mode. To test the
acyclic Direct Access Level 1 variables, a reserved index or class/instance/attribute is used for each
type of variable (See Commands section). Each read variable always returns the same value and
does not permit a new value to be written to it. Each write variable expects a specific value to be
sent and will return an error state if any other value is sent. No special test command is assigned
for Direct Access Level 2 variables.
For Indirect Access and Variable Block tests, two reserved variable names are assigned (refer to the
Commands section). These variables have no other functional purpose except to respond to test
read and test write commands. Each read variable always returns the same value and does not
permit a new value to be written to it. Each write variable expects a specific value to be sent and
will return an error state if any other value is sent.
B.6.5.
Performance Test Commands
The floating point data block provides a special command to permit performance testing of
ACT350's data update through the fieldbus interface. This command (1912) switches the device
into a special mode to send a timer count at the rate specified by the value in the floating point write
(0 = at A/D rate, 1 = at 1 msec rate, n = n msec rate). If the device is generally not capable of
providing this data, or of providing data at a particular speed, it will return a response of ‘invalid
B-24
METTLER TOLEDO ACT350 Transmitter User's Guide
30303895 | 00 | 11/2015
command.’ It is also possible that the device will be unable to reach the desired speed due to other
system activity.
Once in this mode, the device will report the updated count value in the floating point read block at
the specified rate.
B.7.
Asynchronous Format
SAI Asynchronous Format is for one-time read or write data that occurs outside of the normal scan
cycle. This is typically used for setup data before the operation “starts” or other special information
that is not needed as frequently. Acyclic messaging is typically not used for "real-time" activities
and is generally used for non-repetitive or low repetition requests, from a control system; simply
stated, the control system sends a request and the device responds to the request.
Asynchronous Format provides no cyclic data. However, a device can support this format along
with one or more of the cyclic data formats in this specification.
This format uses special message instructions in the control system to immediate execute the
command specified within its configuration. These messages and their instructions are control
system dependent. Within the configuration of the instruction, several parameters are used to
define: 1) the command type, 2) the device variable that the command applies to, and 3) the
control system memory space or variable used with the instruction (for write value or read
response).
There are two methods of sending/receiving data through acyclic messages: 1) direct access to the
variable through a unique name or number defined by the control system's acyclic message block
and 2) indirect access through a variable name provided in the data structure of two generic
message blocks reserved for this purpose (one for read, one for write). Within the Asynchronous
Format, the specification covers two levels of direct access and one level of indirect access. When
the Asynchronous Format is supported by a device, it must support Direct Access Level 1. All other
methods are optional and not interdependent so a device can choose to provide Direct Level 1 only;
Direct Level 1 and Indirect Access, but not Direct Level 2; Direct Level 1 and Level 2 but not Indirect;
or all three. Variable names are exclusive within the Direct Access Levels – meaning that a variable
in Level 1 will not be renamed in Level 2. However variables available in the Direct Access Levels
may also be found in Indirect Access method.
B.7.1.1.
Direct Access Level 1
The ACT350 supports the Asynchronous Format via Direct Access Level 1.
This group uses the acyclic parameter access method provided through the automation interface to
read and write specific internal variables. Each variable is assigned its own unique parameter;
either an index number, or class/instance/attribute which will differ depending on the automation
bus type. This group would likely include weight data but not application-specific data; for example,
it would not include counting variables like average piece weight or count.
In the Direct Levels, the control system variable's memory space shares a similar structure with the
variable block data only since it does not require the words reserved for the command and variable
name. Its space is reserved based on the type of data requested and the type of command used:
30303895 | 00 | 11/2015
METTLER TOLEDO ACT350 Transmitter User's Guide
B-25
Standard Automation Interface
Figure B-26: Asynchronous Direct Command / Response
Figure B-27: Asynchronous Direct Command / Response
B.7.2.
Control System Parameters for Direct Access
Because control systems use different methods for providing acyclic messages, the parameter used
in the message block may also differ and is based on their requirements.
B.7.2.1.
Profibus/ProfiNet Acyclic Messages
For most control systems using Profibus or ProfiNet networks, there are two types of commands
that can be used to execute acyclic messages: RDREC (SFB52) and WRREC (SFB53). The index
and length parameters within these blocks are used to specify what variable (for Direct Access) or
what command (for Indirect Access) is required. To read a variable, a combination of RDREC and
WRREC commands are used. To write a value to a variable, the WRREC command is used. Index
numbers used are interface dependent due to the restrictions of the particular network type.
B.7.2.2.
EIP/ControlNet/DeviceNet Acyclic Messages
For control systems using EthernetIP, ControlNet or DeviceNet networks, there are two types of
commands that can be used to execute asynchronous messages: CIP Generic Message Instruction
for Get Attribute Single ("e") or CIP Generic Message Instruction for Set Attribute Single ("10"). These
commands use parameters called class code, instance number, attribute number and length to be
configured in the message block in order to specify what variable for Direct Access) or what
command (for Indirect Access) is required.
B-26
METTLER TOLEDO ACT350 Transmitter User's Guide
30303895 | 00 | 11/2015
C
Cyclic Commands
This appendix covers
•
•
•
•
Floating Point Block Commands
Status Block Commands
Other Responses
Commands
The commands available for the control system to use in Write blocks are grouped
according to block type and command type. All commands are considered "oneshot" – meaning that the command is only triggered once even if it remains in the
command word for multiple scans until another command is sent. In order to permit
a command to be issued a second time, a no-op command is provided.
No more than one command per block is permitted (the only exception is a cancel
operation command to abort the previously sent command). All other commands to
this block will be ignored until its active command is completed (either successfully or not).
Specifically additional commands sent before completion are not "stored" to be acted upon
completion of the prior command. When multiple block commands are sent, the order of
completion should be lowest word block to highest and it will be the control system's responsibility
to make sure command conflicts do not exist when multiple blocks are assigned to the same
channel.
All responses to commands for the cyclic data blocks are provided in the same manner – through
the response word value. During the process of receiving and executing the operation required for a
command, the device will follow a defined sequence, as shown in Figure C-1.
30303895 | 00 | 11/2015
METTLER TOLEDO ACT350 Transmitter User's Guide
C-1
Cyclic Commands
Command
received by device
through cyclic data
Device puts
“in process”
status in
field
indicator
Device begins
processing
command
Is command
valid?
No
Yes
Device executes
command
Does
command
execute
successfully
No
Device does not
execute command
Yes
Device puts
command value
into field indicator
(as ack command
complete)
Device puts
failure status in
field indicator
Device
increments
sequence
bits
Figure C-1: Receiving and Executing a Command
C-2
METTLER TOLEDO ACT350 Transmitter User's Guide
30303895 | 00 | 11/2015
If a command is aborted, it will follow the sequence shown in Figure C-2.
Command
received by device
through cyclic data
Device puts “in
process” status in field
indicator & begins
processing command
Control System
sends second
command to
cancel prior
command
Is cancel
command
valid?
No
Yes
Device changes response
to “abort in process” (2004)
& begins cancellation
process of first command
Device ignores command,
leaves “in process” status in
response and continues to
execute initial command
Once command is aborted,
device changes status to
Command Failed Aborted (16) and increments
sequence bits
Figure C-2: Aborted Command Sequence
For multi-step commands, special commands are used to advance to the next step, to retry a failed
step, or to abort the entire process. There are also corresponding status values to indicate when the
device is ready to execute the next step or when the step has failed.
30303895 | 00 | 11/2015
METTLER TOLEDO ACT350 Transmitter User's Guide
C-3
Cyclic Commands
During a stepped procedure, the commands follow the procedure shown in Figure C-3.
Multi-step
command received
by device through
cyclic data
Device puts
“in process”
status in
field
indicator
Device puts original
Command value in the field
indicator and increments
the sequence bits
Yes
Yes
1
Device begins
processing
command step
Is this the last
step
No
Yes
Does next step
need value
from control
system
Does
command step
execute
successfully
Device does not
execute command
step
No
No
Device puts step failure
status in field indicator
and increments the
sequence bits
Device puts step
succeeded, next step/value
status into field indicator
and increments the
sequence bits
Device puts step
succeeded, next step
status into field indicator
and increments the
sequence bits
Control system sends Next step
command with value (alternates
between 2002 & 2003)
Control system sends Next
step command (alternates
between 2002 & 2003)
How does
control system
handle error
Abort command
Device executes
command cancellation
process
Skip Step
Retry Step
Go to
Device does not advance to
next step
1
Abort completes
Device puts Command Failed
Aborted status in the field
indicator and increments the
sequence bits
Figure C-3: Stepped Command Procedure
C-4
METTLER TOLEDO ACT350 Transmitter User's Guide
30303895 | 00 | 11/2015
C.1.
Floating Point Block Commands
There are five types of floating point commands: report, write (immediate), write (sequence),
operation (immediate), or operation (sequence). Each type is based on the command use and the
expected response from the device. Refer to the Commands section for the full list of possible
commands.
C.1.1.
Floating Point Report Commands
Floating Point Report Commands are used to request the data that is sent by the device in its read
floating point block. These commands are used to get continuously updated data for information
such as gross weight, net weight, raw weight, rate, or other application numeric data values that
are time critical.
Command
C.1.1.1.
Description
Value
Report Default value
Reports Gross weight data in displayed resolution
0
Report Rounded Tare Weight
Tare weight data in displayed resolution
2
Report Rounded Net Weight
Net weight data in displayed resolution
3
Valid Command Response
When a valid floating point report command is received, the ACT350 does the following:
1. Places the "in process" response in the field indicator value and begins processing the
command…
2. Reports the requested data in the floating point words of the floating block
3. Updates the Response word to indicate what data is present in the floating point value. This
should match what the command & channel value were in the command request of the write
block.
4. Increments and updates the sequence bits in the status word.
5. Continues to update the floating point value and status bits until another command is received.
The Timeout and Invalid command data responses should not occur in report commands (no data
should be sent with command and any provided should be ignored).
C.1.2.
Floating Point Write Commands
Floating Point Write Commands are used to write a value provided by the floating point write block
to some device function. These commands are used to set common process values such as tare,
target, tolerance, or other application numeric data values that can be user-specified during
operation. These commands may or may not execute immediately so the in process response may
be seen by the control system in the cyclic data before the command completes.
Command
30303895 | 00 | 11/2015
Description
Value
Write Preset Tare Weight
Sets Preset Tare to Value provided
201
Write Comparator 1 Limit
Sets comparator 1 limit to value provided
240
METTLER TOLEDO ACT350 Transmitter User's Guide
C-5
Command
Description
Cyclic Commands
Write Filter Mode
C.1.2.1.
Value
Sets filter to value provided
290
Valid Command Response
When a valid floating point write command is received, the ACT350 does the following:
1. Places the "in process" response in the field indicator value and begins processing the
command…
2. Loads the supplied value into the ACT350's internal variable. Reports the value stored in the
floating point words of the floating block.
3. Updates the Response word to indicate what command was received. This should match what
the command & channel value were in the command request of the write block.
4. Increment and update the sequence bits in the status word.
The Timeout command data response should not occur in write commands.
C.1.3.
Floating Point Operation Commands
Floating Point Operation Commands are used to trigger an operation. These commands may or
may not require a sequence of responses. Simple operations may execute immediately and require
no additional sequence steps. More complex operations may take multiple steps to execute and
require additional commands from the control system to continue through the entire process.
Command
C.1.3.1.
Description
Value
Tare Immediate
Motion not checked, tare executed
400
Zero Immediate
Motion not checked, zero executed
401
Clear Tare
Motion not checked, clear tare executed
402
Valid Command Response
When a valid floating point operation command is received, the ACT350 does the following:
1. Places the "in process" response in the field indicator value and begins processing the
command…
2. Triggers the operational function requested by the command.
3. Wait for the response from the ACT350, if the process takes multiple steps, report "step
complete" when current step is finished successfully. Report "step failed" when current step is
unsuccessful. Wait for Continue or Abort command from control system to start next step.
Repeat as many times as required. If the process is complete, continue to step 4.
4. Updates the Response word to indicate what command was received. This should match what
the command & channel value were in the command request of the write block.
5. Increments and updates the sequence bits in the status word.
C-6
METTLER TOLEDO ACT350 Transmitter User's Guide
30303895 | 00 | 11/2015
C.2.
Status Block Commands
Status block commands are only report type. They are used to request the data that is sent by the
ACT350 in its Status blocks. These commands are used to get continuously updated status data for
scale, target, or physical discrete input/output information. See Commands section for the full list
of possible commands.
Command
C.2.1.
Description
Value
Report Default Status
RedAlert Alarm, I/O Group 1, and Scale Group 2 status bits
0
Report I/O mix 1
I/O group 2, I/O group 3, I/O group 4
9
Valid Command Response
When a valid Status report command is received, the ACT350 does the following:
1. Places the "in process" response in the field indicator value and begins processing the
command…
2. Reports the requested data in the status group word of the Status block
3. Updates the Response word to indicate what data is present in the status group word. This
should match what the command & channel value were in the command request of the write
block.
4. Continues to update the status bits until another command is received.
The Timeout and Invalid command data responses should not occur in report commands.
C.3.
Other Responses
In addition to the valid response, there may be other possible responses:
C.3.1.
Invalid Command Response
An invalid command response is sent when the ACT350 determines that the command is known
but cannot be executed. This might occur due state restrictions – for example attempting to zero
when the scale is outside of acceptable zero range. When an invalid command is received, the
ACT350 does the following:
1. Places the "in process" response in the field indicator value and begins processing the
command…
1. Updates the Response word to indicate invalid command (Bit 15 = 1, error value = 1)
2. Increments and updates the sequence bits in the status word.
C.3.2.
Unknown Command Response
An unknown command response is sent when the ACT350 does not support this information (for
example requesting rate values from ACT350). When an unsupported command is received, the
ACT350 does the following:
30303895 | 00 | 11/2015
METTLER TOLEDO ACT350 Transmitter User's Guide
C-7
1. Places the "in process" response in the field indicator value and begins processing the
command…
Cyclic Commands
2. Updates the Response word to indicate unsupported command (Bit 15 = 1, error value = 4)
3. Increments and updates the sequence bits in the status word.
C.3.3.
Invalid Command data Response
An invalid command data response is sent when a valid write command is received with an invalid
value (for example one that is smaller or larger than the allowed value). When invalid command
data is received, the ACT350 does the following:
1. Places the "in process" response in the field indicator value and begins processing the
command…
2. Updates the Response word to indicate invalid command value (Bit 15 = 1, error value = 8)
3. Increments and updates the sequence bits in the status word.
C.3.4.
Timeout Command Response
A timeout command response is sent when the valid command that is received by the ACT350 is
unable to execute within a pre-determined time. This might occur for commands that require no
motion or stable weight before execution, for example. When the command timeout occurs, the
ACT350 does the following:
1. Places the "in process" response in the field indicator value and begin processing the
command…
2. Updates the Response word to indicate command timeout failure value (Bit 15 = 1, error value
= 2)
3. Increments and updates the sequence bits in the status word.
If the control system chooses to abort the previous command, it can issue a special command to
cancel operation of this previous command as long as its status is in process or during any step of
a multiple step sequence. After the cancel command is acknowledged through the use of its value
as an abort in process response, ACT350 will provide a response to indicate the initial command
has been aborted.
C.3.5.
Aborted Command Response
A command failed - aborted response is sent once a second command to cancel the prior
command has been received and processed. This can only occur if the original command 1)
permits cancellation, 2) has not already completed successfully, and 3) has already failed. When
the command abort occurs, the ACT350 does the following:
1. Places the "abort in process" response (2004) in the field indicator value and begin processing
the command…
2. Updates the Response word to indicate command abort failure value (Bit 15 = 1, error value =
16)
3. Increments and updates the sequence bits in the status word.
Refer to Commands section for a flow chart of the abort process.
C-8
METTLER TOLEDO ACT350 Transmitter User's Guide
30303895 | 00 | 11/2015
C.3.6.
Step Successful Command Response
A step successful command response is sent when ACT350 determines that the command's current
step has been successfully executed and requires acknowledgement to start the next step in the
process. When a previous step completes and the next step in the sequence must be "started", the
ACT350 does the following:
1. Places the "in process" response in the field indicator value and begins processing the
command…
2. Updates the Response word to indicate step successful when ready to execute next step (value
= 2046)
3. Increments and updates the sequence bits in the status word.
The control system should send one of the next step commands to continue with the next step in
the process.
C.3.7.
Step Successful / Next Value Command Response
A step successful / next value command response is sent when ACT350 determines that the
command's current step has been successfully executed and requires the next value and
acknowledgement to start the next step in the process. When a previous step completes and the
next step in the sequence requires another value to execute the next step in the process, the
ACT350 does the following:
1. Places the "in process" response in the field indicator value and begin processing the
command…
2. Updates the Response word to indicate step successful and next value is needed when ready to
execute next step (value = 2045)
3. Increments and updates the sequence bits in the status word.
The control system should send one of the next step commands with the required value in the
floating point words to continue with the next step in the process.
C.3.8.
Step Failed Command Response
A step failed command response is sent when ACT350 determines that the command's current step
has failed. Once the current step executes and fails, the ACT350 does the following:
1. Places the "in process" response in the field indicator value and begin processing the
command…
2. Updates the Response word to indicate step failed (Bit 15 = 1, error value = 32)
3. Increments and updates the sequence bits in the status word.
At this point the control system will need to decide whether to abort the sequence (command =
2004), to retry the step (command = 2005), or to skip this step (command = 2006) and try to
perform the next step. Not all processes will allow all three of these options – those not permitted
will have an invalid command response when the next step command is sent.
30303895 | 00 | 11/2015
METTLER TOLEDO ACT350 Transmitter User's Guide
C-9
Commands
C.4.1.
Special Commands
Cyclic Commands
C.4.
For all block types, there are some reserved commands used for unique status or command
sequencing.
Command
Test Command
Description
Value
Used to determine communication works and byte/word
order & enter test mode
FP
=
2.76
Mask
=
80h, 80h
Cmd
=
80h, 80h
Bit 15
=
1+…
2185 for both words
Exit Test Mode
FP & Mask = 0
Used to return to normal operation
Cmd = 88h, 88h
Bit 15 = 1 + …
6553
C.4.2.
= 1+…
These are used to indicate failed command status
through the floating point field … each of these
responses turns on bit 15 and the bit value shown in ()
Response only
Command Failed Invalid
(1)
Response only
Command Failed Timeout
(2)
Response only
Command Failed Unknown
(4)
Response only
Command Failed Value Invalid
(8)
Response only
Command Failed Aborted
(16)
Response only
Command Step Failed
(32)
Response only
Test Command Failed
(64)
General System Commands
Command
C-10
Bit 15
Response only
Description
Value
Response only
Command has been received and is being evaluated (in process)
2047
Response only
Step Successful
2046
Response only
Step Successful, Next Value
2045
NOOP 1
No operation command – used to test command response, clear prior
command, etc.
2000
Next step 1
Continue to next step in sequence
2002
Next step 2
Continue to next step in sequence
2003
Cancel operation
Abort sequence … response value means abort in process
2004
Retry Step
After step failure, retries previous step in sequence
2005
METTLER TOLEDO ACT350 Transmitter User's Guide
30303895 | 00 | 11/2015
Command
Skip Step
Description
After step failure, skips step and advances to next in sequence
C.4.3.
Floating Point block Commands
C.4.3.1.
Weight Report Commands
Command
C.4.3.2.
Description
Report Default Data
Report Rounded Gross Weight
Gross Weight data in displayed resolution
1
Report Rounded Tare Weight
Tare weight data in displayed resolution
2
Report Rounded Net Weight
Net weight data in displayed resolution
3
Rate (change in gross weight over time) in displayed
resolution
4
Report Rounded Rate
Report Gross Weight
Gross weight data in internal resolution
5
Report Tare Weight
Tare weight data in internal resolution
6
Report Net Weight
Net weight data in internal resolution
7
Comparator Report Commands
Description
40
Report Comparator 2 Limit
42
Report Comparator 3 Limit
44
Report Comparator 4 Limit
46
Report Comparator 5 Limit
48
Miscellaneous Report Command
Description
Value
100
Weight Write Immediate Commands
Command
Write Preset Tare Weight
Description
Sets Preset Tare to Value provided
Value
201
Comparator Write Immediate Commands
Command
30303895 | 00 | 11/2015
Value
Report Comparator 1 Limit
Report Last Error Code
C.4.3.5.
Value
0
Command
C.4.3.4.
2006
For ACT350 this is the Gross weight data in displayed
resolution
Command
C.4.3.3.
Value
Description
Value
Write Comparator 1 Limit
240
Write Comparator 2 Limit
242
METTLER TOLEDO ACT350 Transmitter User's Guide
C-11
Cyclic Commands
Command
C.4.3.6.
Description
Write Comparator 3 Limit
244
Write Comparator 4 Limit
246
Write Comparator 5 Limit
248
Weight Operation Immediate Commands
Command
C.4.3.7.
Description
Value
Tare
Tare executed with motion check
400
Zero
Zero executed with motion check
401
Clear Tare
Motion not checked, clear tare executed
402
Floating Point Status Bit Test Commands
Command
Alarm Bit
Motion Bit
Net Mode bit
C.4.4.
Value
Description
Value
Turn on or off bit in scale status word when in test mode
…
FP = 1 to set ON or
FP = 0 to set OFF
1900
1901
1902
Center of zero bit
1903
Alt weight bit
1904
Device bit 1
1905
Device bit 2
1906
Device bit 3
1907
Device bit 4
1908
Device bit 5
1909
Device bit 6
1910
Device bit 7
1911
Status/Command block Commands
Status/Command block commands are unique to this block type and not ALL block types. So for
example, a command value of 0 in the status/command block will report the default status words
(RedAlert, I/O Group 1, Scale Group 2 Status bits).
C.4.4.1.
Status Commands
Command
C-12
Description
Value
Report Default Status words
Default status words (see below)
0
Report RedAlert Alarm, Scale
Group 2, I/O group 1
RedAlert Alarm, Scale group 2, I/O group 1
1
Report Target / Comparator Status
Target 1, Comparator group 1, Comparator group 2
2
METTLER TOLEDO ACT350 Transmitter User's Guide
30303895 | 00 | 11/2015
Command
Description
Value
Report Comparator mix 1
Comparator group 1, comparator group 2, I/O group 1
16
Report Alarms & Scale Group 2
RedAlert Alarm, Alarm, Scale Group2
21
The default for ACT350 is the same as command 1.
30303895 | 00 | 11/2015
METTLER TOLEDO ACT350 Transmitter User's Guide
C-13
D
Acyclic Commands
D.1.
ACT350 Level 1 Variable List
This appendix covers
• ACT350 Level 1 Variable List
• ACT350 Level 2 Variable List
D.1.1.
PROFIBUS
Command
Description
Read/Write
Data
Type
PROFIBUS
Slot (hex)
PROFIBUS
Index (hex)
Default
Gross weight data in defined
resolution
Read
Float, 4
1
14
Report Rounded Gross Weight
Gross weight data in defined
resolution
Read
Float, 4
1
15
Report Rounded Tare Weight
Tare weight data in defined
resolution
Read
Float, 4
1
16
Report Rounded Net Weight
Net weight data in defined
resolution
Read
Float, 4
1
17
Report Unrounded Gross Weight
Gross weight data in internal
resolution
Read
Float, 4
1
18
Report Unrounded Tare Weight
Tare weight data in internal
resolution
Read
Float, 4
1
19
Report Unrounded Net Weight
Net weight data in internal
resolution
Read
Float, 4
1
1A
Write Tare Register (Preset Tare)
Example after power fail restart
(read is handled through tare
weight variable above)
Write
Float, 4
1
1B
Tare Command
T command of CPTZ
Write
Byte, 1
1
1C
Clear Tare Command
C command of CPTZ
Write
Byte, 1
1
1D
Zero Command
Z command of CPTZ (executed
with motion check)
Write
Byte, 1
1
22
Report Zero Operation Status
Example after power fail restart
Read
Short, 2
1
24
Turn All Outputs OFF
Forces all outputs OFF
Write
Float, 4
1
26
Alarm Status Group
Report alarm status group
Read
Short, 2
1
28
30303895 | 00 | 11/2015
METTLER TOLEDO ACT350 Transmitter User's Guide
D-1
Acyclic Commands
D-2
Read/Write
Data
Type
PROFIBUS
Slot (hex)
PROFIBUS
Index (hex)
Report RedAlert status
Read
Short, 2
1
29
Scale Status Group 2
Scale status group
Read
Short, 2
1
2A
Report Scale Status Group 1
Reports scale status bits (group
1)
Read
Short, 2
1
27
Report Tare Operation Status
Report Tare operation status
Read
Short, 2
1
1F
Report ID1
Device identification information
#1
Read
Byte, 21
1
2B
Report ID2
Device identification information
#2
Read
Byte, 21
1
2C
Report ID3
Device identification information
#3
Read
Byte, 21
1
2D
Report Software version
Device software OS version
Read
Byte, 21
1
2E
Report Fieldbus version
Device fieldbus stack version
Read
Byte, 21
1
2F
Report SAI version
Device supported SAI version
Read
Byte, 21
1
31
Read Floating Point
Test floating point variable –
always reads 123.45 – no write
permitted
Read
Float, 4
1
A
Write Floating Point
Test floating point variable – no
usage in device except for test
Write
Float, 4
1
B
Read Integer
Test integer variable – always
reads 9876
Read
Short, 2
1
C
Write Integer
Test integer variable – no usage
in device except for test
Write
Short, 2
1
D
Read String
Test string variable – always
read "ABCD"
Read
Byte, 21
1
E
Write String
Test string variable – no usage
in device except for test
Write
Byte, 21
1
F
Read Long
Test long integer variable –
always reads 98765
Read
Int, 4
1
10
Write Long
Test long integer variable – no
usage in device except for test
Write
Int, 4
1
11
Read Byte
Test byte variable – always
reads 56h
Read
Byte, 1
1
12
Write Byte
Test byte variable – no usage in
device except for test
Write
Byte, 1
1
13
Command
Description
ReadAlert Status Group
METTLER TOLEDO ACT350 Transmitter User's Guide
30303895 | 00 | 11/2015
D.1.2.
Ethernet/IP
Command
Description
Read/
Write
Data Type
EIP Class
Code
EIP
Instance
Values
EIP
Attribute #
Default
Gross weight data in defined
resolution
Read
Float, 4
300
01
01
Report Rounded Gross
Weight
Gross weight data in defined
resolution
Read
Float, 4
300
01
02
Report Rounded Tare
Weight
Tare weight data in defined
resolution
Read
Float, 4
300
01
03
Report Rounded Net
Weight
Net weight data in defined
resolution
Read
Float, 4
300
01
04
Report Unrounded Gross
Weight
Gross weight data in internal
resolution
Read
Float, 4
300
01
05
Report Unrounded Tare
Weight
Tare weight data in internal
resolution
Read
Float, 4
300
01
06
Report Unrounded Net
Weight
Net weight data in internal
resolution
Read
Float, 4
300
01
07
Write Tare Register
(Preset Tare)
Example after power fail restart
(read is handled through tare
weight variable above)
Write
Float, 4
300
01
08
Tare Command
T command of CPTZ
Write
Byte, 1
300
01
09
Clear Tare Command
C command of CPTZ
Write
Byte, 1
300
01
11
Zero Command
Z command of CPTZ (executed
with motion check)
Write
Byte, 1
300
01
14
Report Zero Operation
Status
Example after power fail restart
Read
Short, 2
300
01
17
Turn All Outputs OFF
Forces all outputs OFF
Write
Float, 4
301
01
02
Alarm Status Group
Report alarm status group
Read
Short, 2
302
01
02
RedAlert Status Group
Report RedAlert status
Read
Short, 2
302
01
03
Scale Status Group 2
Scale status group
Read
Short, 2
302
01
04
Report Scale Status
Group 1
Reports scale status bits (group
1)
Read
Short, 2
302
01
1
Report Tare Operation
Status
Report Tare operation status
Read
Short, 2
300
01
16
Report ID1
Device identification information
#1
Read
Byte, 21
303
1
1
Report ID2
Device identification information
#2
Read
Byte, 21
303
1
2
Report ID3
Device identification information
#3
Read
Byte, 21
303
1
3
30303895 | 00 | 11/2015
METTLER TOLEDO ACT350 Transmitter User's Guide
D-3
Acyclic Commands
Command
Description
Data Type
EIP Class
Code
EIP
Instance
Values
EIP
Attribute #
Report Software version
Device software OS version
Read
Byte, 21
303
1
4
Report Fieldbus version
Device fieldbus stack version
Read
Byte, 21
303
1
5
Report SAI version
Device supported SAI version
Read
Byte, 21
303
1
7
Read Floating Point
Test floating point variable –
always reads 123.45 – no write
permitted
Read
Float, 4
30F
01
01
Write Floating Point
Test floating point variable – no
usage in device except for test
Write
Float, 4
30F
01
02
Read Integer
Test integer variable – always
reads 9876
Read
Short, 2
30F
01
03
Write Integer
Test integer variable – no usage
in device except for test
Write
Short, 2
30F
01
04
Read String
Test string variable – always read
"ABCD"
Read
Byte, 21
30F
01
05
Write String
Test string variable – no usage in
device except for test
Write
Byte, 21
30F
01
06
Read Long
Test long integer variable –
always reads 98765
Read
Int, 4
30F
01
07
Write Long
Test long integer variable – no
usage in device except for test
Write
Int, 4
30F
01
08
Read Byte
Test byte variable – always reads
56h
Read
Byte, 1
30F
01
09
Write Byte
Test byte variable – no usage in
device except for test
Write
Byte, 1
30F
01
10
D.1.3.
PROFINET
Command
D-4
Read/
Write
Description
Read/Write
Data
Type
PROFINET
Slot +
Sub Slot
PROFINET
Index Value
Default
Gross weight data in defined
resolution
Read
Float, 4
1, 1
2000
Report Rounded Gross Weight
Gross weight data in defined
resolution
Read
Float, 4
1, 1
2001
Report Rounded Tare Weight
Tare weight data in defined
resolution
Read
Float, 4
1, 1
2002
Report Rounded Net Weight
Net weight data in defined resolution
Read
Float, 4
1, 1
2003
Report Unrounded Gross Weight
Gross weight data in internal
resolution
Read
Float, 4
1, 1
2004
METTLER TOLEDO ACT350 Transmitter User's Guide
30303895 | 00 | 11/2015
Command
Description
Read/Write
Data
Type
PROFINET
Slot +
Sub Slot
PROFINET
Index Value
Report Unrounded Tare Weight
Tare weight data in internal
resolution
Read
Float, 4
1, 1
2005
Report Unrounded Net Weight
Net weight data in internal resolution
Read
Float, 4
1, 1
2006
Write Tare Register (Preset
Tare)
Example after power fail restart (read
is handled through tare weight
variable above)
Write
Float, 4
1, 1
2020
Tare Command
T command of CPTZ
Write
Byte, 1
1, 1
2010
Clear Tare Command
C command of CPTZ
Write
Byte, 1
1, 1
2012
Zero Command
Z command of CPTZ (executed with
motion check)
Write
Byte, 1
1, 1
2013
Report Zero Operation Status
Example after power fail restart
Read
Short, 2
1, 1
2009
Turn All Outputs OFF
Forces all outputs OFF
Write
Float, 4
1, 1
2031
Alarm Status Group
Report alarm status group
Read
Short, 2
1, 1
2041
RedAlert Status Group
Report RedAlert status
Read
Short, 2
1, 1
2042
Scale Status Group 2
Scale status group
Read
Short, 2
1, 1
2043
Report Scale Status Group 1
Reports scale status bits (group 1)
Read
Short, 2
1, 1
2040
Report Tare Operation Status
Report Tare operation status
Read
Short, 2
1, 1
2008
Report ID1
Device identification information #1
Read
Byte, 21
1
2050
Report ID2
Device identification information #2
Read
Byte, 21
1
2051
Report ID3
Device identification information #3
Read
Byte, 21
1
2052
Report Software version
Device software OS version
Read
Byte, 21
1
2053
Report Fieldbus version
Device fieldbus stack version
Read
Byte, 21
1
2054
Report SAI version
Device supported SAI version
Read
Byte, 21
1
2056
Read Floating Point
Test floating point variable – always
reads 123.45 – no write permitted
Read
Float, 4
1, 1
5000
Write Floating Point
Test floating point variable – no
usage in device except for test
Write
Float, 4
1, 1
5001
Read Integer
Test integer variable – always reads
9876
Read
Short, 2
1, 1
5002
Write Integer
Test integer variable – no usage in
device except for test
Write
Short, 2
1, 1
5003
Read String
Test string variable – always read
"ABCD"
Read
Byte, 21
1, 1
5004
Write String
Test string variable – no usage in
device except for test
Write
Byte, 21
1, 1
5005
30303895 | 00 | 11/2015
METTLER TOLEDO ACT350 Transmitter User's Guide
D-5
Acyclic Commands
Command
Read/Write
Data
Type
PROFINET
Slot +
Sub Slot
PROFINET
Index Value
Read Long
Test long integer variable – always
reads 98765
Read
Int, 4
1, 1
5006
Write Long
Test long integer variable – no
usage in device except for test
Write
Int, 4
1, 1
5007
Read Byte
Test byte variable – always reads
56h
Read
Byte, 1
1, 1
5008
Write Byte
Test byte variable – no usage in
device except for test
Write
Byte, 1
1, 1
5009
D.2.
ACT350 Level 2 Variable List
D.2.1.
PROFIBUS
Command
D-6
Description
Description
Read/Write
Data
type
PROFIBUS
Slot
PROFIBUS
Index
2
0x04
2
0x05
2
0x06
2
0x07
2
0x08
2
0x03
Report Comparator 1 limit
Read value for comparator #1
Read
Float, 4
Write Comparator 1 limit
Write value for comparator #1
Write
Float, 4
Report Comparator 2 limit
Read value for comparator #2
Read
Float, 4
Write Comparator 2 limit
Write value for comparator #2
Write
Float, 4
Report Comparator 3 limit
Read value for comparator #3
Read
Float, 4
Write Comparator 3 limit
Write value for comparator #3
Write
Float, 4
Report Comparator 4 limit
Read value for comparator #4
Read
Float, 4
Write Comparator 4 limit
Write value for comparator #4
Write
Float, 4
Report Comparator 5 limit
Read value for comparator #5
Read
Float, 4
Write Comparator 5 limit
Write value for comparator #5
Write
Float, 4
Report # of Comparators used
Read how many comparators
used
Read
Byte, 1
Write # of Comparators used
Write how many comparators
used
Write
Byte, 1
Apply Parameters
Apply parameters, reinitialize
Write
Byte, 1
2
0x1E
Comparator Status Group 1
Comparator Status Group 1
Read
Short, 2
1
D0
Display – Energy Saving Mode
Time value for the display to
turn off
Read/Write
Float, 4
1
78
METTLER TOLEDO ACT350 Transmitter User's Guide
30303895 | 00 | 11/2015
D.2.2.
Ethernet/IP
Command
Description
Read/Write Data type
EIP Class
Code
EIP
Instance
Values
EIP
Attribute #
0x411
1
0x05
0x411
1
0x06
0x411
1
0x07
0x411
1
0x08
0x411
1
0x09
0x411
1
0x04
Report Comparator 1 limit
Read value for comparator #1
Read
Float, 4
Write Comparator 1 limit
Write value for comparator #1
Write
Float, 4
Report Comparator 2 limit
Read value for comparator #2
Read
Float, 4
Write Comparator 2 limit
Write value for comparator #2
Write
Float, 4
Report Comparator 3 limit
Read value for comparator #3
Read
Float, 4
Write Comparator 3 limit
Write value for comparator #3
Write
Float, 4
Report Comparator 4 limit
Read value for comparator #4
Read
Float, 4
Write Comparator 4 limit
Write value for comparator #4
Write
Float, 4
Report Comparator 5 limit
Read value for comparator #5
Read
Float, 4
Write Comparator 5 limit
Write value for comparator #5
Write
Float, 4
Report # of Comparators
used
Read how many comparators
used
Read
Byte, 1
Write # of Comparators
used
Write how many comparators
used
Write
Byte, 1
Apply Parameters
Apply parameters, reinitialize
Write
Byte, 1
0x411
1
0x1F
Comparator Status Group 1
Comparator Status Group 1
Read
Short, 2
0x411
1
0x01
Display Energy Saving
Mode
Time value for the display to
turn off
Read/Write
Float, 4
0x416
1
0x09
D.2.3.
PROFINET
Command
Description
Read/Write
Data type
Report Comparator 1 limit
Read value for comparator #1
Read
Float, 4
Write Comparator 1 limit
Write value for comparator #1
Write
Float, 4
Report Comparator 2 limit
Read value for comparator #2
Read
Float, 4
Write Comparator 2 limit
Write value for comparator #2
Write
Float, 4
Report Comparator 3 limit
Read value for comparator #3
Read
Float, 4
Write Comparator 3 limit
Write value for comparator #3
Write
Float, 4
Report Comparator 4 limit
Read value for comparator #4
Read
Float, 4
Write Comparator 4 limit
Write value for comparator #4
Write
Float, 4
Report Comparator 5 limit
Read value for comparator #5
Read
Float, 4
Write Comparator 5 limit
Write value for comparator #5
Write
Float, 4
30303895 | 00 | 11/2015
PROFINET
Slot + Sub
Slot
PROFINET
Index Value
1, 1
0x4055
1, 1
0x4056
1, 1
0x4057
1, 1
0x4058
1, 1
0x4059
METTLER TOLEDO ACT350 Transmitter User's Guide
D-7
Acyclic Commands
Command
D-8
Description
Read/Write
Data type
Byte, 1
PROFINET
Slot + Sub
Slot
PROFINET
Index Value
1, 1
0x4054
Report # of Comparators used
Read how many comparators
used
Read
Write # of Comparators used
Write how many comparators
used
Write
Byte, 1
Apply Parameters
Apply parameters, reinitialize
Write
Byte, 1
1, 1
0x406F
Comparator Status Group 1
Comparator Status Group 1
Read
Short, 2
1, 1
0x4051
Display – Energy Saving Mode
Time value for the display to turn
off
Read/Write
Float, 4
1, 1
0x4309
METTLER TOLEDO ACT350 Transmitter User's Guide
30303895 | 00 | 11/2015
E
GEO Codes
The GEO code feature provided in the ACT350 transmitter permits calibration readjustment due to
changes in elevation or latitude without reapplying test weights. This adjustment assumes a
previously accurate calibration was done with the GEO code set properly for that original location
and that the GEO code for the new location can be accurately determined. The procedure for using
this feature is as follows.
E.1.
Original Site Calibration
1. Use the GEO code chart (Table E-1) on the following pages to determine the GEO code for the
current altitude and location at which the scale will be calibrated.
2. Enter that GEO value into the GEO code parameter in setup at Scale > Calibration.
3. Immediately after entering the GEO code, perform a zero and span adjustment using accurate
test weights.
4. Exit the setup menu tree.
5. The scale can now be used in its new location.
E.2.
New Site GEO Code Adjustment
When a terminal is to be reinstalled at a different geographic location, gravitational and altitude
changes can be accounted for by following these steps. Note that this procedure is not necessary if
an on-site recalibration is performed.
1. Use the GEO code chart (Table E-1) on the following pages to determine the GEO code for the
new altitude and location at which the scale will be used.
2. Enter that GEO value into the GEO code parameter in Setup at Scale > Calibration.
3. Immediately after entering the GEO code, exit the setup menu tree. DO NOT perform a normal
calibration.
The calibration has now been adjusted for the differences in gravity from the original site of
calibration to the new site of use.
Using the GEO code value for calibration adjustment is not as accurate as re-applying certified
test weights and re-calibrating the scale in a new location.
30303895 | 00 | 11/2015
METTLER TOLEDO ACT350 Transmitter User's Guide
E-1
Table E-1: GEO Adjustment Values
GEO Codes
Height Above Sea Level, in Meters
E-2
Latitude North
or South,
in Degrees and
Minutes
0
325
650
975
1300
1625
1950
2275
2600
2925
3250
325
650
975
1300
1625
1950
2275
2600
2925
3250
3575
Height Above Sea Level, in Feet
0
1060
2130
3200
4260
5330
6400
7460
8530
9600
10660
1060
2130
3200
4260
5330
6400
7460
8530
9600
10660
11730
0° 0'–5° 46'
5
4
4
3
3
2
2
1
1
0
0
5° 46'–9° 52'
5
5
4
4
3
3
2
2
1
1
0
9° 52'–12° 44'
6
5
5
4
4
3
3
2
2
1
1
12° 44'–15° 6'
6
6
5
5
4
4
3
3
2
2
1
15° 6'–17° 0'
7
6
6
5
5
4
4
3
3
2
2
17° 10'–19° 2'
7
7
6
6
5
5
4
4
3
3
2
19° 2'–20° 45'
8
7
7
6
6
5
5
4
4
3
3
20° 45'–22° 22'
8
8
7
7
6
6
5
5
4
4
3
22° 22'–23° 54'
9
8
8
7
7
6
6
5
5
4
4
23° 54'–25° 21'
9
9
8
8
7
7
6
6
5
5
4
25° 21'–26° 45'
10
9
9
8
8
7
7
6
6
5
5
26° 45'–28° 6'
10
10
9
9
8
8
7
7
6
6
5
28° 6'–29° 25'
11
10
10
9
9
8
8
7
7
6
6
29° 25'–30° 41'
11
11
10
10
9
9
8
8
7
7
6
30° 41'–31° 56'
12
11
11
10
10
9
9
8
8
7
7
31° 56'–33° 9'
12
12
11
11
10
10
9
9
8
8
7
33° 9'–34° 21'
13
12
12
11
11
10
10
9
9
8
8
34° 21'–35° 31'
13
13
12
12
11
11
10
10
9
9
8
35° 31'–36° 41'
14
13
13
12
12
11
11
10
10
9
9
36° 41’–37° 50’
14
14
13
13
12
12
11
11
10
10
9
37° 50’–38° 58’
15
14
14
13
13
12
12
11
11
10
10
38° 58’–40° 5’
15
15
14
14
13
13
12
12
11
11
10
40° 5’–41° 12’
16
15
15
14
14
13
13
12
12
11
11
41° 12’–42° 19’
16
16
15
15
14
14
13
13
12
12
11
42° 19’–43° 26’
17
16
16
15
15
14
14
13
13
12
12
43° 26’–44° 32’
17
17
16
16
15
15
14
14
13
13
12
44° 32’–45° 38’
18
17
17
16
16
15
15
14
14
13
13
METTLER TOLEDO ACT350 Transmitter User's Guide
30303895 | 00 | 11/2015
Height Above Sea Level, in Meters
Latitude North
or South,
in Degrees and
Minutes
0
325
650
975
1300
1625
1950
2275
2600
2925
3250
325
650
975
1300
1625
1950
2275
2600
2925
3250
3575
Height Above Sea Level, in Feet
0
1060
2130
3200
4260
5330
6400
7460
8530
9600
10660
1060
2130
3200
4260
5330
6400
7460
8530
9600
10660
11730
45° 38’–46° 45’
18
18
17
17
16
16
15
15
14
14
13
46° 45’–47° 51’
19
18
18
17
17
16
16
15
15
14
14
47° 51’–48° 58’
19
19
18
18
17
17
16
16
15
15
14
48° 58’–50° 6’
20
19
19
18
18
17
17
16
16
15
15
50° 6’–51° 13’
20
20
19
19
18
18
17
17
16
16
15
51° 13’–52° 22’
21
20
20
19
19
18
18
17
17
16
16
52° 22’–53° 31’
21
21
20
20
19
19
18
18
17
17
16
53° 31’–54° 41’
22
21
21
20
20
19
19
18
18
17
17
54° 41’–55° 52’
22
22
21
21
20
20
19
19
18
18
17
55° 52’–57° 4’
23
22
22
21
21
20
20
19
19
18
18
57° 4’–58° 17’
23
23
22
22
21
21
20
20
19
l9
18
58° 17'–59° 32'
24
23
23
22
2\2
21
21
20
20
19
19
59° 32'–60° 49'
24
24
23
23
22
22
21
21
20
20
19
60° 49'–62° 9'
25
24
24
23
23
22
22
21
21
20
20
62° 9'–63° 30'
25
25
24
24
23
23
22
22
21
21
20
63° 30'–64° 55'
26
25
25
24
24
23
23
22
22
21
21
64° 55'–66° 24'
26
26
25
25
24
24
23
23
22
22
21
66° 24'–67° 57'
27
26
26
25
25
24
24
23
23
22
22
67° 57'–69° 35'
27
27
26
26
25
25
24
24
23
23
22
69° 5'–71° 21'
28
27
27
26
26
25
25
24
24
23
23
71° 21'–73° 16'
28
28
27
27
26
26
25
25
24
24
23
73° 16'–75° 24'
29
28
28
27
27
26
26
25
25
24
24
75° 24'–77° 52'
29
29
28
28
27
27
26
26
25
25
24
77° 52'–80° 56'
30
29
29
28
28
27
27
26
26
25
25
80° 56'–85° 45'
30
30
29
29
28
28
27
27
26
26
25
85° 45'–90° 00'
31
30
30
29
29
28
28
27
27
26
26
30303895 | 00 | 11/2015
METTLER TOLEDO ACT350 Transmitter User's Guide
E-3
To protect your METTLER TOLEDO product’s future:
Congratulations on choosing the quality and
precision of METTLER TOLEDO. Proper use
according to these instructions and regular
calibration and maintenance by our factory-trained
service team ensure dependable and accurate
operation, protecting your investment. Contact us
about a METTLER TOLEDO service agreement
tailored to your needs and budget.
We invite you to register your product at
www.mt.com/productregistration so we can contact
you about enhancements, updates and important
notifications concerning your product.
www.mt.com
Mettler-Toledo, LLC
1900 Polaris Parkway
Columbus, OH 43240
Phone 800 438 4511
Fax 614 438 4900
© 2015 Mettler-Toledo, LLC
30303895 Rev. 00, 11/2015
Document version -
For more information