Upload
others
View
4
Download
0
Embed Size (px)
Citation preview
Profibus
Interface Description
SCADA
SPS
R
Supervisory Control andData Acquisation
IO Server
Ethernet
Profibus DP
SCADA
A-96.250.731 / 041115
Customer SupportSWAN and its representatives maintain a fully trained staff of technical specialists around the world. For any technical question, contact your nearest SWAN representative, or the manufacturer:
SWAN ANALYTISCHE INSTRUMENTE AGStudbachstrasse 138340 HinwilSwitzerland
Internet: www.swan.ch
E-mail: [email protected]
Document Status
Title: AMI PROFIBUS Operator’s Manual
ID: A-96.250.731
Revision Issue
00 February 2012 First release
01 March 2012 Chapters AMI Phosphate-II and AMI pH/mV:pH/mV added
02 Sept. 2012 Chap. AMI Phosphate II updated
03 Jan. 2013 Chap. AMI ISE added
04 Mai 2013 Chapter AMI Hydrogen and AMI Solicon4 addedChapter AMI Oxygen splitted into AMI Oxysafe & AMI OxytraceUpdate of AMI Codes CC,
05 September 2015
AMI Phosphate HL added, AMI Phosphate removedAMI Turbiwell, Turbitrace and Turbitrack updated
06 October 2015 AMI Silitrace added
© 2015, SWAN ANALYTISCHE INSTRUMENTE AG, Switzerland, all rights reserved
subject to change without notice
Profibus
1. Profibus Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . 51.1. Cyclic Data Telegram. . . . . . . . . . . . . . . . . . . . . . . . . . . . 71.2. Customizing the Cyclic Data Telegram . . . . . . . . . . . . . . 71.3. Data Formats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71.4. Information at Transmitter Level. . . . . . . . . . . . . . . . . . . . 81.4.1 Status Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91.4.2 Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101.4.3 Acyclic Data Communication . . . . . . . . . . . . . . . . . . . . 101.5. Application Example. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111.6. Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121.7. Technical Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131.7.1 Output Characteristics . . . . . . . . . . . . . . . . . . . . . . . . . 131.7.2 Display and User Interface . . . . . . . . . . . . . . . . . . . . . . 131.8. Appendix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
2. Product Specific Data for AMI Codes II . . . . . . . . . . . . 152.1. Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152.2. Cyclic Data Telegram. . . . . . . . . . . . . . . . . . . . . . . . . . . . 152.2.1 Data Formats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172.3. Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202.3.1 Device Master Files (GSD). . . . . . . . . . . . . . . . . . . . . . 202.3.2 GSD File Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
3. Product Specific Data for AMI Codes II CC . . . . . . . . . 213.1. Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213.2. Cyclic Data Telegram. . . . . . . . . . . . . . . . . . . . . . . . . . . . 213.2.1 Data Formats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233.3. Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273.3.1 Device Master Files (GSD). . . . . . . . . . . . . . . . . . . . . . 273.3.2 GSD File Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
4. Product Specific Data for AMI Codes II TC . . . . . . . . . 294.1. Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 294.2. Cyclic Data Telegram. . . . . . . . . . . . . . . . . . . . . . . . . . . . 294.2.1 Data Formats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 304.3. Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 344.3.1 Device Master Files (GSD). . . . . . . . . . . . . . . . . . . . . . 344.3.2 GSD File Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
5. Product Specific Data for AMI Deltacon. . . . . . . . . . . . 355.1. Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 355.2. Cyclic Data Telegram. . . . . . . . . . . . . . . . . . . . . . . . . . . . 355.2.1 Data Formats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 375.3. Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 415.3.1 Device Master Files (GSD). . . . . . . . . . . . . . . . . . . . . . 415.3.2 GSD File Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
6. Product Specific Data for AMI Hydrazine. . . . . . . . . . . 436.1. Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 436.2. Cyclic Data Telegram. . . . . . . . . . . . . . . . . . . . . . . . . . . . 436.2.1 Data Formats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 456.3. Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 486.3.1 Device Master Files (GSD). . . . . . . . . . . . . . . . . . . . . . 486.3.2 GSD File Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
7. Product Specific Data for AMI Hydrogen. . . . . . . . . . . 497.1. Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 497.2. Cyclic Data Telegram. . . . . . . . . . . . . . . . . . . . . . . . . . . . 497.2.1 Data Formats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 517.3. Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 547.3.1 Device Master Files (GSD). . . . . . . . . . . . . . . . . . . . . . 547.3.2 GSD File Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
A-96.250.731 / 041115 1
Profibus
8. Product Specific Data for AMI Inducon . . . . . . . . . . . . 558.1. Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 558.2. Cyclic Data Telegram . . . . . . . . . . . . . . . . . . . . . . . . . . . . 558.2.1 Data Formats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 578.3. Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 608.3.1 Device Master Files (GSD). . . . . . . . . . . . . . . . . . . . . . 608.3.2 GSD File Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
9. Product Specific Data for AMI ISE . . . . . . . . . . . . . . . . 619.1. Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 619.2. Cyclic Data Telegram . . . . . . . . . . . . . . . . . . . . . . . . . . . . 619.2.1 Data Formats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 639.3. Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 669.3.1 Device Master Files (GSD). . . . . . . . . . . . . . . . . . . . . . 669.3.2 GSD File Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
10. Product Specific Data for AMI LineTOC. . . . . . . . . . . . 6710.1. Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6710.2. Cyclic Data Telegram . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6710.2.1 Data Formats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6910.3. Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7210.3.1 Device Master Files (GSD). . . . . . . . . . . . . . . . . . . . . . 7210.3.2 GSD File Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
11. Product Specific Data for Oxysafe . . . . . . . . . . . . . . . . 7311.1. Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7311.2. Cyclic Data Telegram . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7311.2.1 Data Formats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7511.3. Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7811.3.1 Device Master Files (GSD). . . . . . . . . . . . . . . . . . . . . . 7811.3.2 GSD File Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
12. Product Specific Data for Oxytrace . . . . . . . . . . . . . . . 7912.1. Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7912.2. Cyclic Data Telegram . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7912.2.1 Data Formats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8112.3. Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8412.3.1 Device Master Files (GSD). . . . . . . . . . . . . . . . . . . . . . 8412.3.2 GSD File Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
13. Product Specific Data for AMI Pharmacon . . . . . . . . . 8513.1. Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8513.2. Cyclic Data Telegram . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8513.2.1 Data Formats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8713.3. Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9013.3.1 Device Master Files (GSD). . . . . . . . . . . . . . . . . . . . . . 9013.3.2 GSD File Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
14. Product Specific Data for AMI Phosphate HL . . . . . . . 9114.1. Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9114.2. Cyclic Data Telegram . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9114.2.1 Data Formats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9414.3. Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9714.3.1 Device Master Files (GSD). . . . . . . . . . . . . . . . . . . . . . 9714.3.2 GSD File Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
15. Product Specific Data for AMI Phosphate II. . . . . . . . . 9915.1. Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9915.2. Cyclic Data Telegram . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9915.2.1 Data Formats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10215.3. Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10515.3.1 Device Master Files (GSD). . . . . . . . . . . . . . . . . . . . . . 10515.3.2 GSD File Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
2 A-96.250.731 / 041115
Profibus
16. Product Specific Data for AMI pH-Redox. . . . . . . . . . . 10716.1. Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10716.2. Cyclic Data Telegram. . . . . . . . . . . . . . . . . . . . . . . . . . . . 10716.2.1 Data Formats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10916.3. Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11216.3.1 Device Master Files (GSD). . . . . . . . . . . . . . . . . . . . . . 11216.3.2 GSD File Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
17. Product Specific Data for AMI pH/mV:pH/mV . . . . . . . 11317.1. Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11317.2. Cyclic Data Telegram. . . . . . . . . . . . . . . . . . . . . . . . . . . . 11317.2.1 Data Formats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11517.3. Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11817.3.1 Device Master Files (GSD). . . . . . . . . . . . . . . . . . . . . . 11817.3.2 GSD File Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
18. Product Specific Data for AMI Powercon. . . . . . . . . . . 11918.1. Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11918.2. Cyclic Data Telegram. . . . . . . . . . . . . . . . . . . . . . . . . . . . 11918.2.1 Data Formats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12118.3. Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12418.3.1 Device Master Files (GSD). . . . . . . . . . . . . . . . . . . . . . 12418.3.2 GSD File Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
19. Product Specific Data for AMI Rescon. . . . . . . . . . . . . 12519.1. Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12519.2. Cyclic Data Telegram. . . . . . . . . . . . . . . . . . . . . . . . . . . . 12519.2.1 Data Formats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12719.3. Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13019.3.1 Device Master Files (GSD). . . . . . . . . . . . . . . . . . . . . . 13019.3.2 GSD File Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
20. Product Specific Data for AMI Silica . . . . . . . . . . . . . . 13120.1. Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13120.2. Cyclic Data Telegram. . . . . . . . . . . . . . . . . . . . . . . . . . . . 13120.2.1 Data Formats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13420.3. Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13720.3.1 Device Master Files (GSD). . . . . . . . . . . . . . . . . . . . . . 13720.3.2 GSD File Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
21. Product Specific Data for AMI Silitrace . . . . . . . . . . . . 13921.1. Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13921.2. Cyclic Data Telegram. . . . . . . . . . . . . . . . . . . . . . . . . . . . 13921.2.1 Data Formats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14221.3. Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14521.3.1 Device Master Files (GSD). . . . . . . . . . . . . . . . . . . . . . 14521.3.2 GSD File Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145
22. Product Specific Data for AMI Sodium. . . . . . . . . . . . . 14722.1. Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14722.2. Cyclic Data Telegram. . . . . . . . . . . . . . . . . . . . . . . . . . . . 14722.2.1 Data Formats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14922.3. Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15222.3.1 Device Master Files (GSD). . . . . . . . . . . . . . . . . . . . . . 15222.3.2 GSD File Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152
23. Product Specific Data for AMI Soditrace . . . . . . . . . . . 15323.1. Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15323.2. Cyclic Data Telegram. . . . . . . . . . . . . . . . . . . . . . . . . . . . 15323.2.1 Data Formats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15523.3. Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15823.3.1 Device Master Files (GSD). . . . . . . . . . . . . . . . . . . . . . 15823.3.2 GSD File Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158
A-96.250.731 / 041115 3
Profibus
24. Product Specific Data for AMI Solicon4. . . . . . . . . . . . 15924.1. Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15924.2. Cyclic Data Telegram . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15924.2.1 Data Formats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16124.3. Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16424.3.1 Device Master Files (GSD). . . . . . . . . . . . . . . . . . . . . . 16424.3.2 GSD File Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164
25. Product Specific Data for AMI Trides . . . . . . . . . . . . . . 16525.1. Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16525.2. Cyclic Data Telegram . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16525.2.1 Data Formats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16725.3. Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17025.3.1 Device Master Files (GSD). . . . . . . . . . . . . . . . . . . . . . 17025.3.2 GSD File Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170
26. Product Specific Data for Turbidity . . . . . . . . . . . . . . . 17126.1. Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17126.2. Cyclic Data Telegram . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17126.2.1 Data Formats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17326.3. Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17626.3.1 Device Master Files (GSD). . . . . . . . . . . . . . . . . . . . . . 17626.3.2 GSD File Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176
4 A-96.250.731 / 041115
ProfibusProfibus Introduction
1. Profibus IntroductionThe AMI family of transmitters provides a common base for a number of analytical instruments with application specific sensor interfaces. Each instrument has a basic structure with identical functionality.This manual describes the functionality of the interface and the integration of the AMI family of transmitters into an automation system.Instruments which only uses a subset of the available data from another instrument, uses the same GSD-File. For example, the AMI Deltacon DG and the AMI Deltacon Power provide exactly the same data, but the AMI Deltacon Power does not provide any data concerning the degasser.The instruments using the same GSD-File and the belonging chapters are listed in the following table:
Instruments using the same GSD-File See chapter
AMI Deltacon DG and AMI Deltacon Power Product Specific Data for AMI Deltacon
AMI Oxysafe and AMI Oxytrace Product Specific Data for Oxygen
AMI Sodium A and AMI Sodium P Product Specific Data for AMI Sodium
AMI Turbiwell, AMI Turbitrace and AMI Turbitrack Product Specific Data for Turbidity
AMI Phosphate-II and AMI Phosphate-II B Product Specific Data for
AMI Phosphate-II
AMI pH/mV:pH/mV and AMI pH/mV:pH/mV Pool Product Specific Data for
AMI pH/mV:pH/mV
A-96.250.731 / 140212 5
ProfibusProfibus Introduction
Hardware AMI instruments can (optionally) be equipped with a PROFIBUS DP-V1 interface. The switch [A] on the PROFIBUS DP-V1 interface serves as termination resistor. Set the switch to ON: at the last instrument of the Profibus chain if only one Instrument is connected to the Profibus.
Wiring, bus terminals and connectors are not part of this manual. It should, however, be noted that the observation of the corresponding standards is of paramount importance to proper opera-tion. Setting the transmission rate to reasonable values (typical baud rate 187.5 kBit/s) will help avoid communication errors.
Profibus Profile The interface supports the PROFIBUS-PA Profile 3.0.
GSD File The PROFIBUS system requires a description of the device parameters, e. g. output data, input data, data format, data volume and supported transmission rate, so that it can integrate the field devices into the bus system. These data are contained in a Device Master File (GSD file) which is placed at the disposal of the PROFIBUS master while communication system is being commis-sioned.Device bitmaps can also be integrated. These appear as icons in the network tree.The manufacturer-specific GSD file is available for download from http://www.swan.ch
A
6 A-96.250.731 / 140212
ProfibusProfibus Introduction
1.1. Cyclic Data Telegram
The cyclic data telegram is specific for each instrument, it contains all information for measure-ment validation and diagnosis. A cyclic data telegram is built in the following structure:
Accessing the values of the cyclic telegram requires programming by a Profibus system integrator (process value format see Table 1-1 on page 8).
.gsd files supplied by SWAN facilitate integration of process values
1.2. Customizing the Cyclic Data Telegram
You can customize the cyclic telegram to better meet the requirements of a process. The tables below represent the maximum contents of the cyclic data telegram. If you do not want to use all the cyclic data of AMI Profibus, you can use the device configuration (Chk_Cfg) to eliminate indi-vidual data blocks from the cyclic telegram via the PLC software. Shortening the telegram im-proves the data throughput rate of a PROFIBUS system. You should only keep those blocks active which you process further in the system. You can do this by means of a "negative" selec-tion in the configuration tool.To achieve the correct structure of the cyclic data telegram, the PROFIBUS master must send the identification FREE_PLACE (00h) for the non-active blocks.
1.3. Data Formats
Each measured value has the same format: one four-byte (32-bit) floating-point value in IEEE 754 Short Real Number format and a status code byte referring to the measured value. There are four quality states, 16 sub-status values (not all defined) for each quality state, and four limit states for the measured value indicated in its associated status byte.(See tables 1-1,1-2, and 1-3).
1
Profibus cycle time t
Cyclic telegram of each device
Cyclic communication
Cyclic telegram of device 2
2 3 n
Process values, 4 bytes Status, 1 byte
Diagnostic values
Detail diagnostics
Quality Control (QC) values
Process value 1e.g. pH, conductivity
QC value 1e.g. Flow, Temp.
e.g. remaining resin capacity
e.g.telegram of alarm bits for detail diagnostic
Status
Status
A-96.250.731 / 140212 7
ProfibusProfibus Introduction
Status Byte Details
1.4. Information at Transmitter Level
Information available at transmitter level can be divided in 4 classes:
Process values Parameters required for control or monitoring of water chemistry (e.g. pH, conductivity, DO, Na, Si, etc). A status flag is added to each process value.
Quality Control(QC) Values
Secondary parameters required to validate process values (e.g. sample flow, temperature, re-agent availability, etc.).
Calibration history Log of calibration dates and parameters.
Diagnostic values The diagnostic values can be used for troubleshooting. They consist of error messages which oc-curs if a measuring value falls below or exceeds a programmed limit. All error messages are stored in the message list of the AMI transmitter and can be read out and displayed via profibus.
Tab. 1-1 Format of a 4 byte process value with status byte
Byte 1 Byte 2 Byte 3 Byte 4 Byte 5
Analog values in IEEE 754 Format Status
Tab. 1-2 Status code byte structure
7 6 5 4 3 2 1 0
Quality Sub-Status Limits Meaning
0 0 The sub-status has a different quality
depending on the coding
bad
0 1 uncertain
1 0 good
0 0 ok
0 1 low limited
1 0 high limited
1 1 constant
Tab. 1-3 Status codes of the measured value
Status
code
Device status Meaning Limits
0x08 BAD Not connected (Temp Sensor not connected)
0x0C BAD device failure
0x10 BAD sensor failure (Temp Sensor Short Circuit)
0x47 UNCERTAIN Last usable value (HOLD) CONST
0x50 UNCERTAIN sensor conversion not accurate (e.g. No Flow) OK
0x64
0x67
UNCERTAIN Sensor calibration
Sensor calibration, hold
OK
CONST
0x80 GOOD ok OK
0x89
0x8A
GOOD Warning Low
Warning High
LOW_LIM
HIGH_LIM
0x8D
0x8E
GOOD Alarm Low
Alarm High
LOW_LIM
HICH_LIM
8 A-96.250.731 / 140212
ProfibusProfibus Introduction
1.4.1 Status Information
Meaning of statusinformation
The status information allows the validation of a process value. Detailed information about status byte coding see Table 1-2 and able 1-3 on page 6.
Note: The symbols which indicate the status are only visible in the AQAS Toolbox.
Recommended pa-rameters to display
To be able to make a comprehensive and reliable assessment about the sample, the following parameters should be displayed: Process values (pH, conductivity, etc.) Status information
Further parameters The following parameters can be used for quality control, but are not necessarily required. Quality Control values (sample Flow, sample Temp., reagent level, etc.) Error messages
Symbol Status Meaning
STATUS GOOD
Instrument in operation, no device error
All conditions required to ensure a valid measurement are fulfilled
Measurement can be trusted. No risk of “false truths”
Any triggered process alarm is really related to the process
STATUS UNCERTAIN
Some conditions (e.g. sample flow) not in desired range or unknown
Measured values on hold due to instrument maintenance
Measurement can no be trusted. Risk of “false truths”
Instrument requires maintenance
STATUS BAD
Instrument in operation with error message (e.g. lack of reagents)
Maintenance required.
Measurement must not be used. Instrument requires urgent
maintenance
STATUS DISCONNECTED
Instrument down or not in operation Instrument not available
A-96.250.731 / 140212 9
ProfibusProfibus Introduction
1.4.2 Configuration
Device Master Files(GSD)
The device is ready for system integration once commissioning has been effected via the local display or the Class 2 master. The PROFIBUS system requires a description of the device pa-rameters, e.g. output data, input data, data format, data volume and supported transmission rate, so that it can integrate the field devices into the bus system. These data are contained in a De-vice Master File (GSD file) which is placed at the disposal of the PROFIBUS master while the communication system is being commissioned. Device bitmaps can also be integrated. These appear as icons in the network tree.The Profile 3.0 Device Master File (GSD) allows field devices from various manufacturers to be exchanged without having to reconfigure.
GSD File Types Prior to configuration, decide which GSD you want to use to operate the system.You can change the setting by means of a Class 2 master (under Physical Block-Parameter Ident_Number_Selector)The following two Device Master Files with different functionalities are available:Manufacturer-specific GSD with Profile 3.0 functionality (default setting):This GSD guarantees the unlimited functionality of the field device. Device-specific process pa-rameters and functions are therefore available.
Profile GSD's: If a system is configured with profile GSD's, it is possible to exchange devices that are supplied by various manufacturers. It is, however, essential that the cyclic process values follow the same sequence. The transmitter supports the profiles Analyzer and Multivariable (IEC 61158-2). These GSD's comprise Analog Input blocks (AI)
Working with GSDfiles
The GSDs must be integrated into the automation system. Depending on the software that is being used, the GSD files can be copied to the program-spe-cific directory or can be read into the database using the import function within the configuration software.
1.4.3 Acyclic Data Communication
Acyclic communication is used for remote configuration of instruments or for accessing specific parameters (e.g. calibration data) of an instrument. This is important for field instruments mount-ed in situ and configured for a particular application (e.g. pressure, temperature, flow and level instruments).Online water analysers are not comparable to this type of field instruments: they are located in normally accessible areas and they are calibrated against a known standard (e.g. pH, chlorine). To ensure reliability and consistency of the measurement, remote configuration has not been en-abled at this time.For online water analysers, the information available in the cyclic data/telegram (i.e. process val-ues and their associated status) is sufficient. Should your solution require the display of further information about a SWAN analyser, the AQAS toolbox from SWAN is an alternative for system integrators to display full instrument information in standardized ActiveX windows.
10 A-96.250.731 / 140212
ProfibusProfibus Introduction
1.5. Application Example
The following application example gives an overview over the hardware configuration and data processing.
HardwareConfiguration
The row 6, Free Place [A] can be used to insert diagnostic data. The GSD files are located under the tree PROFIBUS-PA [B].
Data Processing
A Measuring value at the input
B Data base containing the Measuring values
C Process values Byte 1–4, see Table 1-1 on page 8
D Status Byte, see Table 1-1 on page 8
PROFIBUS-PA
A B
Test
EN
FC41:
SFC14RET_VAL
LADDRW#16#110
...
...
W#16#115
DB41.DBW16
P#DB41DBX0.0
0
0
BYTE 5
DB41.DBW16
P#DB41DBX0.0BYTE 5
RECORD
END
Netzwerk 1:
Netzwerk 2: Test
Profibus: AMI OXYTRACE
EN
SFC14RET_VAL
LADDRRECORD
END
16#0115
A B C D
A-96.250.731 / 140212 11
ProfibusProfibus Introduction
1.6. Operation
Normally the instrument is operated via the keys on the AMI transmitter. If the instrument is con-trolled via Profibus it is possible to lock the keys on the transmitter. A locked transmitter is indicat-ed by a key symbol on the AMI transmitter display.
The keys of the AMI transmitter can be locked as follows:
To unlock the keys proceed as follows:
1 Disconnect the Profibus cable from the AMI transmitter.
The keys are accessible now.
2 Proceed according to the previous instruction and select <Enable>
3 Connect the Profibus cable to the AMI transmitter.
A Key symbol
(indicates that the keys of the
AMI transmitter are locked)
1 Navigate to the menu <Installation> / <Interface>
2 Select <Local Operation>
3 Press <Enter>
4 Select <Disabled>
5 Press <Enter>
6 Select <Yes>
7 Press <Enter>
The system reboots and the keys are locked, indicated by the key symbol [A].
RUN
23 b/s
15:20:18
15:10:38R1
R2 ppb21.5
A
5.1Installation
Signal OutputsSensors
Relay contacts
InterfaceMiscellaneous
5.5.1Interface
Device Address 18Protocol Porfibus
ID ManufacturerLocal Operation Enabled
5.5.1Interface
Device Address 18Protocol Porfibus
ID ManufacturerLocal Operation Enabled
Enabled
Local OperationDisabled
5.5.1Interface
Device Address 18Protocol Porfibus
ID ManufacturerLocal Operation Disabled
No
Save ?Yes
12 A-96.250.731 / 140212
ProfibusProfibus Introduction
1.7. Technical Data
1.7.1 Output Characteristics
1.7.2 Display and User Interface
Output signal PROFIBUS-PA according to EN 50170 Part 4, IEC 1158-2, Profile Version 3.0
PA-Function Slave
Baud rate 187.5 kBit/s
Signal coding Manchester II
Response time slave ca. 20 ms
Error signal Status- and alarm messages according to PROFIBUS PA,Profile version 3.0Display: Error code
Physical layer IEC 1158-2
Voltage supply bus 9–32 V
Power consumption 10 mA +/- 1mA
On-site operation Instrument keys (if not locked)
Bus address Configuration via user interface
communication interface PROFIBUS DP
A-96.250.731 / 140212 13
ProfibusProfibus Introduction
1.8. Appendix
Formula:
Example:
Tab. 1-4 IEEE 754 floating point number:
Byte n Byte n+1 Byte n+2 Byte n+3
Bit 7 Bit 6 ... Bit 0 Bit7 Bit 6 ... Bit 0 Bit 7 ... Bit 0 Bit 7 ... Bit 0
Sign 27 26 ... 22 21 20 2-1 2-2 ... 2-6 2-
7
2-8 2-9 ... 2-14
2-15
2-16 2-17 ... 2-
22 2-23
Exponent Mantissa Mantissa Mantissa
Value 1– sign 2 exponent 127– 1 mantissa+ =
40 F0 00 00 h 0100 0000 1111 0000 0000 0000 0000 0000 b=
Value 1– 0 2 129 127– 1 2 1– 2 2– 2 3–+ + + =
1 22 1 0.5 0.25 0.125+ + + =
1 4 1.875=
7.5=
14 A-96.250.731 / 140212
ProfibusProduct Specific Data for AMI Codes II
2. Product Specific Data for AMI Codes II
2.1. Introduction
The AMI family of transmitters provides a common base for a number of analytical instruments with application specific sensor interfaces. Each instrument has a basic structure with identical functionality.AMI instruments can (optionally) be equipped with a PROFIBUS DP-V1 interface. The interface supports the PROFIBUS-PA Profile 3.0. This part of the manual describes the functionality of the interface and the integration of the AMI family of transmitters into an automation system.
Hardware Wiring, bus terminals and connectors are not part of this manual. It should, however, be noted that the observation of the corresponding standards is of paramount importance to proper operation. Setting the transmission rate to reasonable values will help avoid communication errors.
GSD File for AMICodes II
The PROFIBUS system requires a description of the device parameters, e. g. output data, input data, data format, data volume and supported transmission rate, so that it can integrate the field devices into the bus system. These data are contained in a Device Master File (GSD file) which is placed at the disposal of the PROFIBUS master while communication system is being commissioned.
Device bitmaps can also be integrated. These appear as icons in the network tree.The manufacturer-specific GSD file SW17C1.gsd is available for download from http://www.swan.ch
2.2. Cyclic Data Telegram
Input Data The AMI Codes II makes the following modules available as input data for the cyclic data exchange:
1 Main Process Value (Disinfection)
2 Main Temperature
3 Main Flow
4 2nd Process Value (pH)
5 Diagnostic Values (5 values)
– Photometer Absorbance
– Remaining DPD/Buffer
– Remaining Cleaning Solution
– Raw Value pH in [mV]
– Case Temperature in [°C]
A-96.250.731 / 070813 15
ProfibusProduct Specific Data for AMI Codes II
The input data is transferred from AMI Codes II in the following structure:
Output Data The AMI Codes II makes the following module available as output data for the cyclic data exchange:
1 Control AMI
The control data is transferred to the AMI Codes II has the following structure:
Tab. 2-1 Input data structure of AMI Codes II
Index input data Data Access
Data format / comments Configuration data
0–4 Analog Input block 1 Main Process Value
read Measured value (32-bit floating point number) Status byte
0x42, 0x84, 0x08, 0x05 or 0x42, 0x84, 0x81, 0x81 or 0x94
5–9 Analog Input block 2 Main Temperature
read Measured value (32-bit floating point number) Status byte
0x42, 0x84, 0x08, 0x05 or 0x42, 0x84, 0x81, 0x81 or 0x94
10–14 Analog Input block 3 Main Flow
read Measured value (32-bit floating point number) Status byte
0x42, 0x84, 0x08, 0x05 or 0x42, 0x84, 0x81, 0x81 or 0x94
15–19 Analog Input block 4 2nd Process Value
read Measured value (32-bit floating point number) Status byte
0x42, 0x84, 0x08, 0x05 or 0x42, 0x84, 0x81, 0x81 or 0x94
20–39 Diagnostic Values read 5 Measured values (32-bit floating point numbers)
0x45, 0x93, 0x08, 0x08, 0x08, 0x08, 0x08, 0xD9
Tab. 2-2 Output data structure:
Index output data Data Access Data format / comments Configuration data
0–1 Control AMI
(SP_D)
write Byte 0 Bit 0: Relay 1
0 = open1 = close
0x82, 0x81, 0x05, 0x05 or 0x82, 0x81, 0x84, 0x82 or 0xA1
Bit 1: Relay 2 0 = open1 = close
Bit 2–7: not used
Byte 1 Bit 0: Hold
Bit 1: Control Off
Bit 2–7: not used
16 A-96.250.731 / 070813
ProfibusProduct Specific Data for AMI Codes II
2.2.1 Data Formats
For further information see chapter 1 Data Formats, p. 7
Tab. 2-3 Status Code Byte
7 6 5 4 3 2 1 0
Quality Sub-Status Limits Meaning
0 0 The sub-status has a different quality depending on the coding
bad
0 1 uncertain
1 0 good
0 0 ok
0 1 low limited
1 0 high limited
1 1 constant
Tab. 2-4 Status codes of the measured value
Status
code
Device status Meaning Limits
0x08 BAD Not connected (Temp Sensor not connected)
0x0C BAD device failure
0x10 BAD sensor failure (Temp Sensor Short Circuit)
0x47 UNCERTAIN Last usable value (HOLD) CONST
0x50 UNCERTAIN sensor conversion not accurate (e.g. No Flow) OK
0x64
0x67
UNCERTAIN Sensor calibration Sensor calibration, hold
OK CONST
0x80 GOOD ok OK
0x89
0x8A
GOOD Warning Low Warning High
LOW_LIM HIGH_LIM
0x8D
0x8E
GOOD Alarm Low Alarm High
LOW_LIM HICH_LIM
Tab. 2-5 DP Diagnostics
Byte Description
0 Status 1 Standard DP Diag-nostics1 Status 2
2 Status 3
3 Master address
4 Ident number (high byte)
5 Ident number (low byte)
6 Header (block length incl. Header byte) = 14 Status coding accord-ing to DP/V17 Status Type (0x81)
8 Slot Number (0x00)
9 Status Specifier
10–13 Diagnosis
14–19 Diagnosis Extension
A-96.250.731 / 070813 17
ProfibusProduct Specific Data for AMI Codes II
Tab. 2-6 The diagnosis object consists of 4 Bytes
Byte Bit Meaning when “1” Abbreviation
0 0 Hardware failure electronics DIA_HW_ELECTR
1 Hardware failure mechanics DIA_HW_MECH
2 -
3 Electronic temperature too high DIA_TEMP_ELECTR
4 -
5 Measurement failure DIA_MEASUREMENT
6 -
7 -
1 0 -
1 -
2 -
3 -
4 -
5 Maintenance required DIA_MAINTENANCE
6 -
7 -
2 0 -
1 -
2 -
3 -
4 -
5 -
6 -
7 -
3 0 -
1 -
2 -
3 -
4 -
5 -
6 -
7 Extension Available EXTENSION_AVAILABLE
18 A-96.250.731 / 070813
ProfibusProduct Specific Data for AMI Codes II
Byte 5 is reserved for future extensions.
Tab. 2-7 The diagnosis extension object consists of 6 Bytes.
Byte Bit Meaning when “1” Abbreviation
0 0 -
1 -
2
3
4 DIS. high DIA_MEASUREMENT
5
6
7
1 0 Sample Flow high DIA_MEASUREMENT
1 Sample Flow low DIA_MEASUREMENT
2 Temp. shorted DIA_HW_ELECTR
3 Temp. disconnected DIA_HW_ELECTR
4 Case Temp. high DIA_TEMP_ELECTR
5 Case Temp. low DIA_TEMP_ELECTR
6 Valve defective DIA_MEASUREMENT
7 - -
2 0 Control Timeout -
1 Reagent Pump DIA_MAINTENANCE
2 Photometer not connected DIA_MAINTENANCE
3 Photometer dirty DIA_MAINTENANCE
4 DIS. invalid DIA_MEASUREMENT
5 Reagent Empty DIA_MAINTENANCE
6 Cleaning Reagent DIA_MAINTENANCE
7 Input Active DIA_HW_ELECTR
3 0 IC MK41T56 DIA_HW_ELECTR
1 IC LM75 DIA_HW_ELECTR
2 IC PCF8574 DIA_HW_ELECTR
3 EEprom Microcon DIA_HW_ELECTR
4 EEProm Motherboard DIA_HW_ELECTR
5 EEProm Front-end DIA_HW_ELECTR
6 Cal. Recout DIA_HW_ELECTR
7 Wrong Front-end DIA_HW_ELECTR
4 0 Reagent low DIA_MAINTENANCE
1 - -
2 - -
3 - -
4 - -
5 - -
6 - -
7 - -
A-96.250.731 / 070813 19
ProfibusProduct Specific Data for AMI Codes II
2.3. Configuration
2.3.1 Device Master Files (GSD)
The device is ready for system integration once commissioning has been effected via the local display or the Class 2 master. The PROFIBUS system requires a description of the device parameters, e.g. output data, input data, data format, data volume and supported transmission rate, so that it can integrate the field devices into the bus system. These data are contained in a Device Master File (GSD file) which is placed at the disposal of the PROFIBUS master while the communication system is being commissioned. Device bitmaps can also be integrated. These appear as icons in the network tree.The Profile 3.0 Device Master File (GSD) allows field devices from various manufacturers to be exchanged without having to reconfigure.
2.3.2 GSD File Types
Prior to configuration, decide which GSD you want to use to operate the system.You can change the setting by means of a Class 2 master (under Physical Block-Parameter Ident_Number_Selector)The following two Device Master Files with different functionalities are available:Manufacturer-specific GSD with Profile 3.0 functionality (default setting):This GSD guarantees the unlimited functionality of the field device. Device-specific process parameters and functions are therefore available.Profile GSD's:If a system is configured with profile GSD's, it is possible to exchange devices that are supplied by various manufacturers. It is, however, essential that the cyclic process values follow the same sequence. The transmitter supports the profiles Analyzer and Multivariable (IEC 61158-2). These GSD's comprise Analog Input blocks (AI)
Working with GSD filesThe GSDs must be integrated into the automation system. Depending on the software that is being used, the GSD files can be copied to the program-specific directory or can be read into the database using the import function within the configuration software.
Tab. 2-8 GSD files for AMI Codes II
Device name Ident_number_
Selector
ID number GSD Bitmaps
Manufacturer specific GSD with Profile 3.0 functionality:
AMI Codes II 1 17C1Hex SW17C1.gsd SW17C1_D.bmp
SW17C1_N.bmp SW17C1_S.bmp
Profile 3.0 GSD Analyzer:
AMI Codes II 0 9750 Hex PA139750.gsd PA_9750n.bmp
Profile 3.0 GSD Multivariable:
AMI Codes II 3 9760 Hex PA139760.gsd PA_9760n.bmp
20 A-96.250.731 / 070813
ProfibusProduct Specific Data for AMI Codes II CC
3. Product Specific Data for AMI Codes II CC
3.1. Introduction
The AMI family of transmitters provides a common base for a number of analytical instruments with application specific sensor interfaces. Each instrument has a basic structure with identical functionality.AMI instruments can (optionally) be equipped with a PROFIBUS DP-V1 interface. The interface supports the PROFIBUS-PA Profile 3.0. This part of the manual describes the functionality of the interface and the integration of the AMI family of transmitters into an automation system.
Hardware Wiring, bus terminals and connectors are not part of this manual. It should, however, be noted that the observation of the corresponding standards is of paramount importance to proper operation. Setting the transmission rate to reasonable values will help avoid communication errors.
GSD File for AMICodes II CC
The PROFIBUS system requires a description of the device parameters, e. g. output data, input data, data format, data volume and supported transmission rate, so that it can integrate the field devices into the bus system. These data are contained in a Device Master File (GSD file) which is placed at the disposal of the PROFIBUS master while communication system is being commissioned.
Device bitmaps can also be integrated. These appear as icons in the network tree.The manufacturer-specific GSD file SW17CA.gsd is available for download from http://www.swan.ch
3.2. Cyclic Data Telegram
Input Data The AMI Codes II CC makes the following modules available as input data for the cyclic data exchange:
1 Free available chlorine (fac)
2 Total residual chlorine 1 (tc1)
3 Total residual chlorine 2 (tc2)
4 Calculated monochloramine (cmc)
5 Calculated combined chlorine (ccc)
6 Calculated dichloramine (cdc)
7 Temperature
8 Flow
9 ph Value
10 Diagnostic Values (3 values)
– Remaining DPD / Buffer
– Remaining Potassium / Iodide
– Remaining Cleaning Solution
A-96.250.731 / 150513 21
ProfibusProduct Specific Data for AMI Codes II CC
The input data is transferred from AMI Codes II CC in the following structure:
Tab. 3-1 Input data structure of AMI Codes II CC
Index input data Data Access
Data format / comments Configuration data
0–4 Analog Input block 1 Free available chlo-rine
read Measured value (32-bit floating point number) Status byte
0x42, 0x84, 0x08, 0x05 or 0x42, 0x84, 0x81, 0x81 or 0x94
5–9 Analog Input block 2 Total chlorine 1
read Measured value (32-bit floating point number) Status byte
0x42, 0x84, 0x08, 0x05 or 0x42, 0x84, 0x81, 0x81 or 0x94
10–14 Analog Input block 3 Total chlorine 2
read Measured value (32-bit floating point number) Status byte
0x42, 0x84, 0x08, 0x05 or 0x42, 0x84, 0x81, 0x81 or 0x94
15–19 Analog Input block 4 Calculated mono-chloramine
read Measured value (32-bit floating point number) Status byte
0x42, 0x84, 0x08, 0x05 or 0x42, 0x84, 0x81, 0x81 or 0x94
20–24 Analog Input block 5 Calculated com-bined chlorine
read Measured value (32-bit floating point number) Status byte
0x42, 0x84, 0x08, 0x05 or 0x42, 0x84, 0x81, 0x81 or 0x94
25–29 Analog Input block 6 Calculated dichlora-mine
read Measured value (32-bit floating point number) Status byte
0x42, 0x84, 0x08, 0x05 or 0x42, 0x84, 0x81, 0x81 or 0x94
30–34 Analog Input block 7Temperature
read Measured value (32-bit floating point number) Status byte
0x42, 0x84, 0x08, 0x05 or 0x42, 0x84, 0x81, 0x81 or 0x94
35–39 Analog Input block 8Flow
read Measured value (32-bit floating point number) Status byte
0x42, 0x84, 0x08, 0x05 or 0x42, 0x84, 0x81, 0x81 or 0x94
40–44 Analog Input block 9pH Value
read Measured value (32-bit floating point number) Status byte
0x42, 0x84, 0x08, 0x05 or 0x42, 0x84, 0x81, 0x81 or 0x94
45–57 Diagnostic Values read 3 Measured values (32- bit floating point numbers)
0x45, 0x8B, 0x08, 0x08, 0x08
22 A-96.250.731 / 150513
ProfibusProduct Specific Data for AMI Codes II CC
Output Data The AMI Codes II CC makes the following module available as output data for the cyclic data exchange:
1 Control AMI
The control data is transferred to the AMI Codes II CC in the following structure:
3.2.1 Data Formats
For further information see chapter 1 Data Formats, p. 7
Tab. 3-2 Output data structure:
Index output data Data Access Data format / comments Configuration data
0–1 Control AMI
(SP_D)
write Byte 0Bit 0:
Relay 1 0 = open1 = close
0x82, 0x81, 0x05, 0x05 or 0x82, 0x81, 0x84, 0x82 or 0xA1
Bit 1: Relay 2 0 = open1 = close
Bit 2–7: not used
Byte 1Bit 0:
Hold
Bit 1: Control Off
Bit 2–7: not used
Tab. 3-3 Status Code Byte
7 6 5 4 3 2 1 0
Quality Sub-Status Limits Meaning
0 0 The sub-status has a different quality depending on the coding
bad
0 1 uncertain
1 0 good
0 0 ok
0 1 low limited
1 0 high limited
1 1 constant
A-96.250.731 / 150513 23
ProfibusProduct Specific Data for AMI Codes II CC
Tab. 3-4 Status codes of the measured value
Status
code
Device status Meaning Limits
0x08 BAD Not connected (e.g. Temp Sensor not connected)
0x0C BAD device failure
0x10 BAD Sensor failure (e.g. Temp Sensor Short Circuit)
0x40 UNCERTAIN e.g. because of Temp Sensor Error CONST
0x47 UNCERTAIN Last usable value (HOLD) CONST
0x4B UNCERTAIN Substitute set CONST
0x4F UNCERTAIN Initial value CONST
0x50 UNCERTAIN Sensor conversion not accurate(e.g. No Flow)
OK
0x640x67
UNCERTAIN Sensor calibration Sensor calibration, hold
OK CONST
0x80 GOOD ok OK
0x890x8A
GOOD Warning Low Warning High
LOW_LIM HIGH_LIM
0x8D0x8E
GOOD Alarm Low Alarm High
LOW_LIM HICH_LIM
Tab. 3-5 DP Diagnostics
Byte Description
0 Status 1 Standard DP Diag-nostics
1 Status 2
2 Status 3
3 Master address
4 Ident number (high byte)
5 Ident number (low byte)
6 Header (block length incl. Header byte) = 14 Status coding according to DP/V1
7 Status Type (0x81)
8 Slot Number (0x00)
9 Status Specifier
10–13 Diagnosis
14–19 Diagnosis Extension
24 A-96.250.731 / 150513
ProfibusProduct Specific Data for AMI Codes II CC
Tab. 3-6 The diagnosis object consists of 4 Bytes
Byte Bit Meaning when “1” Abbreviation
0 0 Hardware failure electronics DIA_HW_ELECTR
1 Hardware failure mechanics DIA_HW_MECH
2 -
3 Electronic temperature too high DIA_TEMP_ELECTR
4 -
5 Measurement failure DIA_MEASUREMENT
6 -
7 -
1 0 -
1 -
2 -
3 -
4 -
5 Maintenance required DIA_MAINTENANCE
6 -
7 -
2 0 -
1 -
2 -
3 -
4 -
5 -
6 -
7 -
3 0 -
1 -
2 -
3 -
4 -
5 -
6 -
7 Extension Available EXTENSION_AVAILABLE
A-96.250.731 / 150513 25
ProfibusProduct Specific Data for AMI Codes II CC
Tab. 3-7 The diagnosis extension object consists of 6 Bytes.
Byte Bit Meaning when “1” Abbreviation0 0
1
2
3
4
5
6
7
1 0 Sample Flow high DIA_MEASUREMENT1 Sample Flow low DIA_MEASUREMENT2 Temp. shorted DIA_HW_ELECTR3 Temp. disconnected DIA_HW_ELECTR4 Case Temp. high DIA_TEMP_ELECTR5 Case Temp. low DIA_TEMP_ELECTR6 Valve 1 defective DIA_MEASUREMENT7 DIS. invalid DIA_MEASUREMENT
2 0 Control Timeout -1 Reagent Pump DIA_MAINTENANCE2 Photometer not connected DIA_MAINTENANCE3 Photometer dirty DIA_MAINTENANCE4 fc too high DIA_MEASUREMENT5 Reagent Empty DIA_MAINTENANCE6 Detergent DIA_MAINTENANCE7 Input Active DIA_HW_ELECTR
3 0 IC MK41T56 DIA_HW_ELECTR1 IC LM75 DIA_HW_ELECTR2 IC PCF8574 DIA_HW_ELECTR3 EEprom Microcon DIA_HW_ELECTR4 EEProm Motherboard DIA_HW_ELECTR5 EEProm Front-end DIA_HW_ELECTR6 Cal. Recout DIA_HW_ELECTR7 Wrong Front-end DIA_HW_ELECTR
4 0 -1 -2 -3 -4 -5 -6 -7 -
5 0 DPD / Buffer DIA_MAINTENANCE1 Potassium Iodide DIA_MAINTENANCE2 Cleaning Solution DIA_MAINTENANCE 3
4
5
6
7
26 A-96.250.731 / 150513
ProfibusProduct Specific Data for AMI Codes II CC
3.3. Configuration
3.3.1 Device Master Files (GSD)
The device is ready for system integration once commissioning has been effected via the local display or the Class 2 master. The PROFIBUS system requires a description of the device parameters, e.g. output data, input data, data format, data volume and supported transmission rate, so that it can integrate the field devices into the bus system. These data are contained in a Device Master File (GSD file) which is placed at the disposal of the PROFIBUS master while the communication system is being commissioned. Device bitmaps can also be integrated. These appear as icons in the network tree.The Profile 3.0 Device Master File (GSD) allows field devices from various manufacturers to be exchanged without having to reconfigure.
3.3.2 GSD File Types
Prior to configuration, decide which GSD you want to use to operate the system.You can change the setting by means of a Class 2 master (under Physical Block-Parameter Ident_Number_Selector)The following two Device Master Files with different functionalities are available:Manufacturer-specific GSD with Profile 3.0 functionality (default setting):This GSD guarantees the unlimited functionality of the field device. Device-specific process parameters and functions are therefore available.Profile GSD's:If a system is configured with profile GSD's, it is possible to exchange devices that are supplied by various manufacturers. It is, however, essential that the cyclic process values follow the same sequence. The transmitter supports the profiles Analyzer and Multivariable (IEC 61158-2). These GSD's comprise Analog Input blocks (AI)
Working with GSD filesThe GSDs must be integrated into the automation system. Depending on the software that is being used, the GSD files can be copied to the program-specific directory or can be read into the database using the import function within the configuration software.
Tab. 3-8 GSD files for AMI Codes II CC:
Device name Ident_number_
Selector
ID number GSD Bitmaps
Manufacturer specific GSD with Profile 3.0 functionality:
AMI Codes II CC 1 17CAHex SW17CA.gsd
SW17-CA_D.bmp SW17-CA_N.bmp SW17CA_S.bmp
Profile 3.0 GSD Analyzer:
AMI Codes II CC 0 9750 Hex PA139750.gsd PA_9750n.bmp
Profile 3.0 GSD Multivariable:
AMI Codes II CC 3 9760 Hex PA139760.gsd PA_9760n.bmp
A-96.250.731 / 150513 27
ProfibusProduct Specific Data for AMI Codes II CC
28 A-96.250.731 / 150513
ProfibusProduct Specific Data for AMI Codes II TC
4. Product Specific Data for AMI Codes II TC
4.1. Introduction
The AMI family of transmitters provides a common base for a number of analytical instruments with application specific sensor interfaces. Each instrument has a basic structure with identical functionality.AMI instruments can (optionally) be equipped with a PROFIBUS DP-V1 interface. The interface supports the PROFIBUS-PA Profile 3.0. This part of the manual describes the functionality of the interface and the integration of the AMI family of transmitters into an automation system.
Hardware Wiring, bus terminals and connectors are not part of this manual. It should, however, be noted that the observation of the corresponding standards is of paramount importance to proper operation. Setting the transmission rate to reasonable values will help avoid communication errors.
GSD File for AMICodes II TC
The PROFIBUS system requires a description of the device parameters, e. g. output data, input data, data format, data volume and supported transmission rate, so that it can integrate the field devices into the bus system. These data are contained in a Device Master File (GSD file) which is placed at the disposal of the PROFIBUS master while communication system is being commissioned.
Device bitmaps can also be integrated. These appear as icons in the network tree.The manufacturer-specific GSD file SW17CB.gsd is available for download from http://www.swan.ch
4.2. Cyclic Data Telegram
Input Data AMI Codes II TC makes the following modules available as input data for the cyclic data exchange:
1 Total residual chlorine 1 (tc1)
2 Total residual chlorine 2 (tc2)
3 Calculated dichloramine (cdc)
4 Temperature
5 Flow
6 pH Value
7 Diagnostic Values (5 Values)
– Absorbance
– Remaining DPD / Buffer
– Remaining Cleaning Solution
– pH in mV
– Case Temperature
A-96.250.731 / 140212 29
ProfibusProduct Specific Data for AMI Codes II TC
The input data is transferred from AMI Codes II TC in the following structure:
Output Data The AMI Codes II TC makes the following module available as output data for the cyclic data exchange:
1 Control AMI
The control data is transferred to the AMI Codes II TC in the following structure
4.2.1 Data Formats
For further information see chapter 1 Data Formats, p. 7
Tab. 4-1 Input data structure of AMI Codes II TC
Index input data Data Access
Data format / comments Configuration data
0–4 Analog Input block 1 Total chlorine 1
read Measured value (32-bit floating point number) Status byte
0x42, 0x84, 0x08, 0x05 or 0x42, 0x84, 0x81, 0x81 or 0x94
5–9 Analog Input block 2 Total chlorine 2
read Measured value (32-bit floating point number) Status byte
0x42, 0x84, 0x08, 0x05 or 0x42, 0x84, 0x81, 0x81 or 0x94
10–14 Analog Input block 3 Calculated dichlora-mine
read Measured value (32-bit floating point number) Status byte
0x42, 0x84, 0x08, 0x05 or 0x42, 0x84, 0x81, 0x81 or 0x94
15–19 Analog Input block 4 Temperature
read Measured value (32-bit floating point number) Status byte
0x42, 0x84, 0x08, 0x05 or 0x42, 0x84, 0x81, 0x81 or 0x94
20–24 Analog Input block 5 Flow
read Measured value (32-bit floating point number) Status byte
0x42, 0x84, 0x08, 0x05 or 0x42, 0x84, 0x81, 0x81 or 0x94
25–29 Analog Input block 6 pH Value
read Measured value (32-bit floating point number) Status byte
0x42, 0x84, 0x08, 0x05 or 0x42, 0x84, 0x81, 0x81 or 0x94
30–49 Diagnostic Values read 5 Measured values (32-bit floating point number)
0x45, 0x93, 0x08, 0x08, 0x08, 0x08, 0x08 or0xD9
Tab. 4-2 Output data structure:
Index output data Data Access Data format / comments Configuration data0–1 Control AMI
(SP_D)
write Byte 0Bit 0: Relay 1
0 = open1 = close
0x82, 0x81, 0x05, 0x05 or 0x82, 0x81, 0x84, 0x82 or 0xA1
Bit 1: Relay 2 0 = open1 = close
Bit 2–7: not used
Byte 1Bit 0:
Hold
Bit 1: Control Off
Bit 2–7: not used
30 A-96.250.731 / 140212
ProfibusProduct Specific Data for AMI Codes II TC
Tab. 4-3 Status Code Byte
7 6 5 4 3 2 1 0
Quality Sub-Status Limits Meaning
0 0 The sub-status has a different quality depending on the coding
bad
0 1 uncertain
1 0 good
0 0 ok
0 1 low limited
1 0 high limited
1 1 constant
Tab. 4-4 Status codes of the measured value
Status
code
Device status Meaning Limits
0x08 BAD Not connected (Temp Sensor not connected)
0x0C BAD device failure
0x10 BAD sensor failure (Temp Sensor Short Circuit)
0x47 UNCERTAIN Last usable value (HOLD) CONST
0x50 UNCERTAIN sensor conversion not accurate (e.g. No Flow) OK
0x64
0x67
UNCERTAIN Sensor calibration Sensor calibration, hold
OK CONST
0x80 GOOD ok OK
0x89
0x8A
GOOD Warning Low Warning High
LOW_LIM HIGH_LIM
0x8D
0x8E
GOOD Alarm Low Alarm High
LOW_LIM HICH_LIM
Tab. 4-5 DP Diagnostics
Byte Description
0 Status 1 Standard DP Diagnostics1 Status 2
2 Status 3
3 Master address
4 Ident number (high byte)
5 Ident number (low byte)
6 Header (block length incl. Header byte) = 14 Status coding accord-ing to DP/V17 Status Type (0x81)
8 Slot Number (0x00)
9 Status Specifier
10–13 Diagnosis
14–19 Diagnosis Extension
A-96.250.731 / 140212 31
ProfibusProduct Specific Data for AMI Codes II TC
Tab. 4-6 The diagnosis object consists of 4 Bytes
Byte Bit Meaning when “1” Abbreviation
0 0 Hardware failure electronics DIA_HW_ELECTR
1 Hardware failure mechanics DIA_HW_MECH
2 -
3 Electronic temperature too high DIA_TEMP_ELECTR
4 -
5 Measurement failure DIA_MEASUREMENT
6 -
7 -
1 0 -
1 -
2 -
3 -
4 -
5 Maintenance required DIA_MAINTENANCE
6 -
7 -
2 0 -
1 -
2 -
3 -
4 -
5 -
6 -
7 -
3 0 -
1 -
2 -
3 -
4 -
5 -
6 -
7 Extension Available EXTENSION_AVAILABLE
32 A-96.250.731 / 140212
ProfibusProduct Specific Data for AMI Codes II TC
Tab. 4-7 The diagnosis extension object consists of 6 Bytes.
Byte Bit Meaning when “1” Abbreviation0 0 Alarm high tc1 -
1 Alarm low tc1 -2 Alarm high tc2 -3 Alarm low tc2 -4 Alarm high cdc -5 Alarm low cdc -6 Sample Temp. high DIA_MEASUREMENT7 Sample Temp. low DIA_MEASUREMENT
1 0 Sample Flow high DIA_MEASUREMENT1 Sample Flow low DIA_MEASUREMENT2 Temp. shorted DIA_HW_ELECTR3 Temp. disconnected DIA_HW_ELECTR4 Case Temp. high DIA_TEMP_ELECTR5 Case Temp. low DIA_TEMP_ELECTR6 Valve defective DIA_MAINTENANCE7 DIS. invalid DIA_MEASUREMENT
2 0 Control Timeout -1 Reagent Pump DIA_MAINTENANCE2 Photometer not connected DIA_MAINTENANCE3 Photometer dirty DIA_MAINTENANCE4 Absorbance too high DIA_MEASUREMENT5 Reagent Empty DIA_MAINTENANCE6 Cleaning Solution DIA_MAINTENANCE7 Input Active DIA_HW_ELECTR
3 0 IC MK41T56 DIA_HW_ELECTR1 IC LM75 DIA_HW_ELECTR2 IC PCF8574 DIA_HW_ELECTR3 EEprom Microcon DIA_HW_ELECTR4 EEProm Motherboard DIA_HW_ELECTR5 EEProm Front-end DIA_HW_ELECTR6 Cal. Recout DIA_HW_ELECTR7 Wrong Front-end DIA_HW_ELECTR
4 0 Alarm high pH -1 Alarm low pH -2
3
4
5
6
7
5 0 DPD / Buffer DIA_MAINTENANCE1
2 Cleaning Solution DIA_MAINTENANCE 3 - -4 - -5 - -6 - -7 - -
A-96.250.731 / 140212 33
ProfibusProduct Specific Data for AMI Codes II TC
4.3. Configuration
4.3.1 Device Master Files (GSD)
The device is ready for system integration once commissioning has been effected via the local display or the Class 2 master. The PROFIBUS system requires a description of the device parameters, e.g. output data, input data, data format, data volume and supported transmission rate, so that it can integrate the field devices into the bus system. These data are contained in a Device Master File (GSD file) which is placed at the disposal of the PROFIBUS master while the communication system is being commissioned. Device bitmaps can also be integrated. These appear as icons in the network tree.The Profile 3.0 Device Master File (GSD) allows field devices from various manufacturers to be exchanged without having to reconfigure.
4.3.2 GSD File Types
Prior to configuration, decide which GSD you want to use to operate the system.You can change the setting by means of a Class 2 master (under Physical Block-Parameter Ident_Number_Selector)The following two Device Master Files with different functionalities are available:Manufacturer-specific GSD with Profile 3.0 functionality (default setting):This GSD guarantees the unlimited functionality of the field device. Device-specific process parameters and functions are therefore available.Profile GSD's:If a system is configured with profile GSD's, it is possible to exchange devices that are supplied by various manufacturers. It is, however, essential that the cyclic process values follow the same sequence. The transmitter supports the profiles Analyzer and Multivariable (IEC 61158-2). These GSD's comprise Analog Input blocks (AI)
Working with GSD filesThe GSDs must be integrated into the automation system. Depending on the software that is being used, the GSD files can be copied to the program-specific directory or can be read into the database using the import function within the configuration software.
Tab. 4-8 GSD files for AMI Codes II TC:
Device name Ident_number_
Selector
ID number GSD Bitmaps
Manufacturer specific GSD with Profile 3.0 functionality:
AMI Codes II TC 1 17CBHex SW17CB.gsd SW17CB_D.bmp SW17CB_N.bmp SW17CB_S.bmp
Profile 3.0 GSD Analyzer:
AMI Codes II TC 0 9750 Hex PA139750.gsd PA_9750n.bmp
Profile 3.0 GSD Multivariable:
AMI Codes II TC 3 9760 Hex PA139760.gsd PA_9760n.bmp
34 A-96.250.731 / 140212
ProfibusProduct Specific Data for AMI Deltacon
5. Product Specific Data for AMI Deltacon
5.1. Introduction
This description applies for the AMI Deltacon DG and the AMI Deltacon Power. The AMI Deltacon and Deltacon Power are microprocessor controlled systems for the conductivity measurement in power cycles.The AMI family of transmitters provides a common base for a number of analytical instruments with application specific sensor interfaces. Each instrument has a basic structure with identical functionality.AMI instruments can (optionally) be equipped with a PROFIBUS DP-V1 interface. The interface supports the PROFIBUS-PA Profile 3.0. This part of the manual describes the functionality of the interface and the integration of the AMI family of transmitters into an automation system.
Hardware Wiring, bus terminals and connectors are not part of this manual. It should, however, be noted that the observation of the corresponding standards is of paramount importance to proper operation. Setting the transmission rate to reasonable values will help avoid communication errors.
GSD File forAMI Deltacon
The PROFIBUS system requires a description of the device parameters, e. g. output data, input data, data format, data volume and supported transmission rate, so that it can integrate the field devices into the bus system. These data are contained in a Device Master File (GSD file) which is placed at the disposal of the PROFIBUS master while communication system is being commissioned.
Device bitmaps can also be integrated. These appear as icons in the network tree.The manufacturer-specific GSD file SW17D2.gsd is available for download from http://www.swan.ch
5.2. Cyclic Data Telegram
Input Data The AMI Deltacon DG and the AMI Deltacon Power make the following modules available as input data for the cyclic data exchange:
1 1st Process Value (sc) in µS/cm : Specific Conductivity
2 2nd Process Value (cc) in µS/cm : Cation Conductivity
3 3rd Process Value (dc) in µS/cm : Degassed Conductivity
4 1st Temperature in °C
5 2nd Temperature in °C
6 3rd Temperature in °C
7 Main Flow in l/h
8 1st Calculated Value (pH)
9 2nd Calculated Value (Ammonium) in ppm
10 Diagnostic Values (4 values)
– Case Temperature in °C
– Remaining Resin in %
– Degasser Temperature
– Degasser Line Voltage
A-96.250.731 / 140212 35
ProfibusProduct Specific Data for AMI Deltacon
The input data is transferred from AMI Deltacon in the following structure:
Tab. 5-1 Input data structure of AMI Deltacon
Index input data Data Access
Data format / comments Configuration data
0–4 Analog Input block 1 1st Process Value
read Measured value (32-bit floating point number) Status byte
0x42, 0x84, 0x08, 0x05 or 0x42, 0x84, 0x81, 0x81 or 0x94
5–9 Analog Input block 2 2nd Process Value
read Measured value (32-bit floating point number) Status byte
0x42, 0x84, 0x08, 0x05 or 0x42, 0x84, 0x81, 0x81 or 0x94
10–14 Analog Input block 3 3rd Process Value
read Measured value (32-bit floating point number) Status byte
0x42, 0x84, 0x08, 0x05 or 0x42, 0x84, 0x81, 0x81 or 0x94
15–19 Analog Input block 4 1st Temperature
read Measured value (32-bit floating point number) Status byte
0x42, 0x84, 0x08, 0x05 or 0x42, 0x84, 0x81, 0x81 or 0x94
20–24 Analog Input block 5 2nd Temperature
read Measured value (32-bit floating point number) Status byte
0x42, 0x84, 0x08, 0x05 or 0x42, 0x84, 0x81, 0x81 or 0x94
25–29 Analog Input block 6 3rd Temperature
read Measured value (32-bit floating point number) Status byte
0x42, 0x84, 0x08, 0x05 or 0x42, 0x84, 0x81, 0x81 or 0x94
30–34 Analog Input block 7 Main Flow in l/h
read Measured value (32-bit floating point number) Status byte
0x42, 0x84, 0x08, 0x05 or 0x42, 0x84, 0x81, 0x81 or 0x94
35–39 Analog Input block 8 1st Calc. Value (pH)
read Measured value (32-bit floating point number) Status byte
0x42, 0x84, 0x08, 0x05 or 0x42, 0x84, 0x81, 0x81 or 0x94
40–44 Analog Input block 9 2nd Calc. Value (Ammonium)
read Measured value (32-bit floating point number) Status byte
0x42, 0x84, 0x08, 0x05 or 0x42, 0x84, 0x81, 0x81 or 0x94
45–60 Diagnostic Values read 4 Measured values (32-bit floating point number)
0x44, 0x8F, 0x08, 0x08, 0x08, 0x080x9F
36 A-96.250.731 / 140212
ProfibusProduct Specific Data for AMI Deltacon
Output Data The AMI Deltacon makes the following module available as output data for the cyclic data exchange:
1 Control AMI
The control data is transferred to the AMI Deltacon in the following structure:
5.2.1 Data Formats
For further information see chapter 1 Data Formats, p. 7
Tab. 5-2 Output data structure:
Index output data Data Access Data format / comments Configuration data
0–1 Control AMI
(SP_D)
write Byte 0Bit 0:
Relay 1 0 = open 1 = close
0x82, 0x81, 0x05, 0x05 or 0x82, 0x81, 0x84, 0x82 or 0xA1
Bit 1: Relay 20 = open 1 = close
Bit 2: not used
Bit 3: not used
Bit 4: Channel Select0 = channel 11 = channel 2
Bit 5–7: not used
Byte 1Bit 0:
Hold
Bit 1: Control Off
Bit 2: AutoZero
Bit 3: Define Boiling Point
Bit 4: Degasser off
Bit 5–7: not used
Tab. 5-3 Status Code Byte
7 6 5 4 3 2 1 0
Quality Sub-Status Limits Meaning
0 0 The sub-status has a different quality depending on the coding
bad
0 1 uncertain
1 0 good
0 0 ok
0 1 low limited
1 0 high limited
1 1 constant
A-96.250.731 / 140212 37
ProfibusProduct Specific Data for AMI Deltacon
Tab. 5-4 Status codes of the measured value
Status
code
Device status Meaning Limits
0x08 BAD Not connected (e.g. Temp Sensor not connected)
0x0C BAD device failure
0x10 BAD Sensor failure (e.g. Temp Sensor Short Circuit)
0x47 UNCERTAIN Last usable value (HOLD) CONST
0x50 UNCERTAIN Sensor conversion not accurate(e.g. No Flow)
OK
0x64
0x67
UNCERTAIN Sensor calibration Sensor calibration, hold
OK CONST
0x80 GOOD ok OK
0x89
0x8A
GOOD Warning Low Warning High
LOW_LIM HIGH_LIM
0x8D
0x8E
GOOD Alarm Low Alarm High
LOW_LIM HICH_LIM
Tab. 5-5 DP Diagnostics
Byte Description
0 Status 1 Standard DP Diagnostics1 Status 2
2 Status 3
3 Master address
4 Ident number (high byte)
5 Ident number (low byte)
6 Header (block length incl. Header byte) = 14 Status coding accord-ing to DP/V17 Status Type (0x81)
8 Slot Number (0x00)
9 Status Specifier
10–13 Diagnosis
14–19 Diagnosis Extension
38 A-96.250.731 / 140212
ProfibusProduct Specific Data for AMI Deltacon
Tab. 5-6 The diagnosis object consists of 4 Bytes
Byte Bit Meaning when “1” Abbreviation
0 0 Hardware failure electronics DIA_HW_ELECTR
1 Hardware failure mechanics DIA_HW_MECH
2 -
3 Electronic temperature too high DIA_TEMP_ELECTR
4 -
5 Measurement failure DIA_MEASUREMENT
6 -
7 -
1 0 -
1 -
2 -
3 -
4 -
5 Maintenance required DIA_MAINTENANCE
6 -
7 -
2 0 -
1 -
2 -
3 -
4 -
5 -
6 -
7 -
3 0 -
1 -
2 -
3 -
4 -
5 -
6 -
7 Extension Available EXTENSION_AVAILABLE
A-96.250.731 / 140212 39
ProfibusProduct Specific Data for AMI Deltacon
Tab. 5-7 The diagnosis extension object consists of 6 Bytes.
Byte Bit Meaning when “1” Abbreviation0 0 Cond. 1 Alarm high -
1 Cond. 1 Alarm low -2 Cond. 2 Alarm high -3 Cond. 2 Alarm low -4 Cond. 3 Alarm high -5 Cond. 3 Alarm low -6 Temp. 1 high DIA_MEASUREMENT7 Temp. 1 low DIA_MEASUREMENT
1 0 Sample Flow high DIA_MEASUREMENT1 Sample Flow low DIA_MEASUREMENT2 Temp. 1 shorted DIA_HW_ELECTR3 Temp. 1 disconnected DIA_HW_ELECTR4 Case Temp. high DIA_TEMP_ELECTR5 Case Temp. low DIA_TEMP_ELECTR6 pH Error DIA_MEASUREMENT7
2 0 Control Timeout -1 Degasser disconnected DIA_HW_ELECTR2 Temp. 2 shorted DIA_HW_ELECTR3 Temp. 2 disconnected DIA_HW_ELECTR4 Temp. 3 shorted DIA_HW_ELECTR5 Temp. 3 disconnected DIA_HW_ELECTR6 Degasser Ctl Timeout DIA_HW_ELECTR7 Input Active DIA_HW_ELECTR
3 0 IC MK41T56 DIA_HW_ELECTR1 IC LM75 DIA_HW_ELECTR2 IC PCF8574 DIA_HW_ELECTR3 EEprom Microcon DIA_HW_ELECTR4 EEProm Motherboard DIA_HW_ELECTR5 EEProm Front-end DIA_HW_ELECTR6 Cal. Recout DIA_HW_ELECTR7 Wrong Front-end DIA_HW_ELECTR
4 0 pH Alarm high -1 pH Alarm low -2 Ammonia Alarm high3 Ammonia Alarm low4 Temp. 2 high DIA_MEASUREMENT5 Temp. 2 low DIA_MEASUREMENT6 Temp. 3 high DIA_MEASUREMENT7 Temp. 3 low DIA_MEASUREMENT
5 0 Degasser Line Voltage1 Degasser Temperature2 Resin depleted (less than 10% remaining) DIA_MAINTENANCE 3 - -4 - -5 - -6 - -7 - -
40 A-96.250.731 / 140212
ProfibusProduct Specific Data for AMI Deltacon
5.3. Configuration
5.3.1 Device Master Files (GSD)
The device is ready for system integration once commissioning has been effected via the local display or the Class 2 master. The PROFIBUS system requires a description of the device parameters, e.g. output data, input data, data format, data volume and supported transmission rate, so that it can integrate the field devices into the bus system. These data are contained in a Device Master File (GSD file) which is placed at the disposal of the PROFIBUS master while the communication system is being commissioned. Device bitmaps can also be integrated. These appear as icons in the network tree.The Profile 3.0 Device Master File (GSD) allows field devices from various manufacturers to be exchanged without having to reconfigure.
5.3.2 GSD File Types
Prior to configuration, decide which GSD you want to use to operate the system.You can change the setting by means of a Class 2 master (under Physical Block-Parameter Ident_Number_Selector)The following two Device Master Files with different functionalities are available:Manufacturer-specific GSD with Profile 3.0 functionality (default setting):This GSD guarantees the unlimited functionality of the field device. Device-specific process parameters and functions are therefore available.Profile GSD's:If a system is configured with profile GSD's, it is possible to exchange devices that are supplied by various manufacturers. It is, however, essential that the cyclic process values follow the same sequence. The transmitter supports the profiles Analyzer and Multivariable (IEC 61158-2). These GSD's comprise Analog Input blocks (AI)
Working with GSD filesThe GSDs must be integrated into the automation system. Depending on the software that is being used, the GSD files can be copied to the program-specific directory or can be read into the database using the import function within the configuration software.
Tab. 5-8 GSD files for AMI Deltacon
Device name Ident_number_
Selector
ID number GSD Bitmaps
Manufacturer specific GSD with Profile 3.0 functionality:
AMI Deltacon 1 17D2Hex SW17D2.gsd SW17D2_D.bmp SW17D2_N.bmp SW17D2_S.bmp
Profile 3.0 GSD Analyzer:
AMI Deltacon 0 9750 Hex PA039750.gsd PA_9750n.bmp
Profile 3.0 GSD Multivariable:
AMI Deltacon 3 9760 Hex PA039760.gsd PA_9760n.bmp
A-96.250.731 / 140212 41
ProfibusProduct Specific Data for AMI Deltacon
42 A-96.250.731 / 140212
ProfibusProduct Specific Data for AMI Hydrazine
6. Product Specific Data for AMI Hydrazine
6.1. Introduction
The AMI family of transmitters provides a common base for a number of analytical instruments with application specific sensor interfaces. Each instrument has a basic structure with identical functionality.AMI instruments can (optionally) be equipped with a PROFIBUS DP-V1 interface. The interface supports the PROFIBUS-PA Profile 3.0. This part of the manual describes the functionality of the interface and the integration of the AMI family of transmitters into an automation system.
Hardware Wiring, bus terminals and connectors are not part of this manual. It should, however, be noted that the observation of the corresponding standards is of paramount importance to proper operation. Setting the transmission rate to reasonable values will help avoid communication errors.
GSD File forAMI Hydrazine
The PROFIBUS system requires a description of the device parameters, e. g. output data, input data, data format, data volume and supported transmission rate, so that it can integrate the field devices into the bus system. These data are contained in a Device Master File (GSD file) which is placed at the disposal of the PROFIBUS master while communication system is being commissioned.
Device bitmaps can also be integrated. These appear as icons in the network tree.The manufacturer-specific GSD file SW17C6.gsd is available for download from http://www.swan.ch
6.2. Cyclic Data Telegram
Input Data The AMI Hydrazine makes the following modules available as input data for the cyclic data exchange:
1 Main Process Value
2 Main Temperature
3 Main Flow
4 Diagnostic Values (5 Values)
– Raw value in nA
– Counter Electrode Voltage in mV
– Offset in nA
– Slope in nA
– Case Temperature in °C
A-96.250.731 / 140212 43
ProfibusProduct Specific Data for AMI Hydrazine
The input data is transferred from AMI Hydrazine in the following structure:
Output Data The AMI Hydrazine makes the following module available as output data for the cyclic data exchange:
1 Control AMI
The control data is transferred to the AMI Hydrazine in the following structure:
Tab. 6-1 Input data structure of AMI Hydrazine
Index input data Data Access
Data format / comments Configuration data
0–4 Analog Input block 1 Main Process Value
read Measured value (32-bit floating point number) Status byte
0x42, 0x84, 0x08, 0x05 or 0x42, 0x84, 0x81, 0x81 or 0x94
5–9 Analog Input block 2 Main Temperature
read Measured value (32-bit floating point number) Status byte
0x42, 0x84, 0x08, 0x05 or 0x42, 0x84, 0x81, 0x81 or 0x94
10–14 Analog Input block 3 Main Flow
read Measured value (32-bit floating point number) Status byte
0x42, 0x84, 0x08, 0x05 or 0x42, 0x84, 0x81, 0x81 or 0x94
15–34 Diagnostic Values read 5 Measured values (32-bit floating point number)
0x45, 0x93, 0x08, 0x08, 0x08, 0x08, 0x080xD9
Tab. 6-2 Output data structure
Index output data Data Access Data format / comments Configuration data
0–1 Control AMI
(SP_D)
write Byte 0Bit 0:
Relay 1 0 = open1 = close
0x82, 0x81, 0x05, 0x05 or 0x82, 0x81, 0x84, 0x82 or 0xA1
Bit 1: Relay 2 0 = open1 = close
Bit 2–7: not used
Byte 1Bit 0:
Hold
Bit 1: Control Off
Bit 2–7: not used
44 A-96.250.731 / 140212
ProfibusProduct Specific Data for AMI Hydrazine
6.2.1 Data Formats
Tab. 6-3 Status Code Byte
7 6 5 4 3 2 1 0
Quality Sub-Status Limits Meaning
0 0 The sub-status has a different quality depending on the coding
bad
0 1 uncertain
1 0 good
0 0 ok
0 1 low limited
1 0 high limited
1 1 constant
Tab. 6-4 Status codes of the measured value
Status
code
Device status Meaning Limits
0x08 BAD Not connected (e.g. Temp Sensor not connected)
0x0C BAD device failure
0x10 BAD Sensor failure (e.g. Temp Sensor Short Circuit)
0x47 UNCERTAIN Last usable value (HOLD) CONST
0x50 UNCERTAIN Sensor conversion not accurate(e.g. No Flow)
OK
0x64
0x67
UNCERTAIN Sensor calibration Sensor calibration, hold
OK CONST
0x80 GOOD ok OK
0x89
0x8A
GOOD Warning Low Warning High
LOW_LIM HIGH_LIM
0x8D
0x8E
GOOD Alarm Low Alarm High
LOW_LIM HICH_LIM
Tab. 6-5 DP Diagnostics
Byte Description
0 Status 1 Standard DP Diagnostics1 Status 2
2 Status 3
3 Master address
4 Ident number (high byte)
5 Ident number (low byte)
6 Header (block length incl. Header byte) = 14 Status coding according to DP/V17 Status Type (0x81)
8 Slot Number (0x00)
9 Status Specifier
10–13 Diagnosis
14–19 Diagnosis Extension
A-96.250.731 / 140212 45
ProfibusProduct Specific Data for AMI Hydrazine
Tab. 6-6 The diagnosis object consists of 4 Bytes
Byte Bit Meaning when “1” Abbreviation
0 0 Hardware failure electronics DIA_HW_ELECTR
1 Hardware failure mechanics DIA_HW_MECH
2 -
3 Electronic temperature too high DIA_TEMP_ELECTR
4 -
5 Measurement failure DIA_MEASUREMENT
6 -
7 -
1 0 -
1 -
2 -
3 -
4 -
5 Maintenance required DIA_MAINTENANCE
6 -
7 -
2 0 -
1 -
2 -
3 -
4 -
5 -
6 -
7 -
3 0 -
1 -
2 -
3 -
4 -
5 -
6 -
7 Extension Available EXTENSION_AVAILABLE
46 A-96.250.731 / 140212
ProfibusProduct Specific Data for AMI Hydrazine
Bytes 4 and 5 are reserved for future extensions.
Tab. 6-7 The diagnosis extension object consists of 6 Bytes.
Byte Bit Meaning when “1” Abbreviation
0 0 Hyd. Alarm high -
1 Hyd. Alarm low -
2 -
3 -
4 -
5 -
6 Sample Temp. high DIA_MEASUREMENT
7 Sample Temp. low DIA_MEASUREMENT
1 0 Sample Flow high DIA_MEASUREMENT
1 Sample Flow low DIA_MEASUREMENT
2 Temp. shorted DIA_HW_ELECTR
3 Temp. disconnected DIA_HW_ELECTR
4 Case Temp. high DIA_TEMP_ELECTR
5 Case Temp. low DIA_TEMP_ELECTR
6 Counter Electrode Reference DIA_MEASUREMENT
7
2 0 Control Timeout -
1
2
3
4
5
6 Cleaning Reagent DIA_MAINTENANCE
7 Input Active DIA_HW_ELECTR
3 0 IC MK41T56 DIA_HW_ELECTR
1 IC LM75 DIA_HW_ELECTR
2 IC PCF8574 DIA_HW_ELECTR
3 EEprom Microcon DIA_HW_ELECTR
4 EEProm Motherboard DIA_HW_ELECTR
5 EEProm Front-end DIA_HW_ELECTR
6 Cal. Recout DIA_HW_ELECTR
7 Wrong Front-end DIA_HW_ELECTR
A-96.250.731 / 140212 47
ProfibusProduct Specific Data for AMI Hydrazine
6.3. Configuration
6.3.1 Device Master Files (GSD)
The device is ready for system integration once commissioning has been effected via the local display or the Class 2 master. The PROFIBUS system requires a description of the device parameters, e.g. output data, input data, data format, data volume and supported transmission rate, so that it can integrate the field devices into the bus system. These data are contained in a Device Master File (GSD file) which is placed at the disposal of the PROFIBUS master while the communication system is being commissioned. Device bitmaps can also be integrated. These appear as icons in the network tree.The Profile 3.0 Device Master File (GSD) allows field devices from various manufacturers to be exchanged without having to reconfigure.
6.3.2 GSD File Types
Prior to configuration, decide which GSD you want to use to operate the system.You can change the setting by means of a Class 2 master (under Physical Block-Parameter Ident_Number_Selector)The following two Device Master Files with different functionalities are available:Manufacturer-specific GSD with Profile 3.0 functionality (default setting):This GSD guarantees the unlimited functionality of the field device. Device-specific process parameters and functions are therefore available.Profile GSD's:If a system is configured with profile GSD's, it is possible to exchange devices that are supplied by various manufacturers. It is, however, essential that the cyclic process values follow the same sequence. The transmitter supports the profiles Analyzer and Multivariable (IEC 61158-2). These GSD's comprise Analog Input blocks (AI)
Working with GSD filesThe GSDs must be integrated into the automation system. Depending on the software that is being used, the GSD files can be copied to the program-specific directory or can be read into the database using the import function within the configuration software.
Tab. 6-8 GSD files for AMI Hydrazine:
Device name Ident_number_
Selector
ID number GSD Bitmaps
Manufacturer specific GSD with Profile 3.0 functionality:
AMI Hydrazine 1 17C6Hex SW17C6.gsd SW17C6_D.bmp SW17C6_N.bmp SW17C6_S.bmp
Profile 3.0 GSD Analyzer:
AMI Hydrazine 0 9750 Hex PA039750.gsd PA_9750n.bmp
Profile 3.0 GSD Multivariable:
AMI Hydrazine 3 9760 Hex PA039760.gsd PA_9760n.bmp
48 A-96.250.731 / 140212
ProfibusProduct Specific Data for AMI Hydrogen
7. Product Specific Data for AMI Hydrogen
7.1. Introduction
The AMI family of transmitters provides a common base for a number of analytical instruments with application specific sensor interfaces. Each instrument has a basic structure with identical functionality.AMI instruments can (optionally) be equipped with a PROFIBUS DP-V1 interface. The interface supports the PROFIBUS-PA Profile 3.0. This part of the manual describes the functionality of the interface and the integration of the AMI family of transmitters into an automation system.
Hardware Wiring, bus terminals and connectors are not part of this manual. It should, however, be noted that the observation of the corresponding standards is of paramount importance to proper operation. Setting the transmission rate to reasonable values will help avoid communication errors.
GSD File forAMI Hydrogen
The PROFIBUS system requires a description of the device parameters, e. g. output data, input data, data format, data volume and supported transmission rate, so that it can integrate the field devices into the bus system. These data are contained in a Device Master File (GSD file) which is placed at the disposal of the PROFIBUS master while communication system is being commissioned.
Device bitmaps can also be integrated. These appear as icons in the network tree.The manufacturer-specific GSD file SW17E4.gsd is available for download fromhttp://www.swan.ch
7.2. Cyclic Data Telegram
Input Data The AMI Hydrogen makes the following modules available as input data for the cyclic data exchange:
1 Main Process Value
2 Main Temperature
3 Main Flow
4 2nd Process Value (%)
5 Diagnostic Values (5 Values)
– Raw Current Temperature Compensated in nA
– Raw Current in nA
– Air Pressure in hPa
– Reserved
– Case Temperature in °C
A-96.250.731 / 150513 49
ProfibusProduct Specific Data for AMI Hydrogen
The input data is transferred from AMI Hydrogen in the following structure:
Output Data The AMI Hydrogen makes the following module available as output data for the cyclic data exchange:
1 Control AMI
The control data is transferred to the AMI Hydrogen in the following structure:
Tab. 7-1 Input data structure of AMI Hydrogen
Index input data Data Access
Data format / comments Configuration data
0–4 Analog Input block 1 Main Process Value
read Measured value (32-bit floating point number) Status byte
0x42, 0x84, 0x08, 0x05 or 0x42, 0x84, 0x81, 0x81 or 0x94
5–9 Analog Input block 2 Main Temperature
read Measured value (32-bit floating point number) Status byte
0x42, 0x84, 0x08, 0x05 or 0x42, 0x84, 0x81, 0x81 or 0x94
10–14 Analog Input block 3 Main Flow
read Measured value (32-bit floating point number) Status byte
0x42, 0x84, 0x08, 0x05 or 0x42, 0x84, 0x81, 0x81 or 0x94
15–19 Analog Input block 42nd Process Value
read Measured value(32-bit floating point number)
0x42, 0x84, 0x08, 0x05 or 0x42, 0x84, 0x81, 0x81 or 0x94
20–39 Diagnostic Values read 5 Measured values (32-bit floating point numbers)
0x45, 0x93, 0x08, 0x08, 0x08, 0x08, 0x080xD9
Tab. 7-2 Output data structure
Index output data Data Access Data format / comments Configuration data
0–1 Control AMI
(SP_D)
write Byte 0Bit 0:
Relay 1 0 = open1 = close
0x82, 0x81, 0x05, 0x05 or 0x82, 0x81, 0x84, 0x82 or 0xA1
Bit 1: Relay 2 0 = open1 = close
Bit 2–7: not used
Byte 1Bit 0:
Hold
Bit 1: Control Off
Bit 2–7: not used
50 A-96.250.731 / 150513
ProfibusProduct Specific Data for AMI Hydrogen
7.2.1 Data Formats
Tab. 7-3 Status Code Byte
7 6 5 4 3 2 1 0
Quality Sub-Status Limits Meaning
0 0 The sub-status has a different quality depending on the coding
bad
0 1 uncertain
1 0 good
0 0 ok
0 1 low limited
1 0 high limited
1 1 constant
Tab. 7-4 Status codes of the measured value
Status
code
Device status Meaning Limits
0x08 BAD Not connected (e.g. Temp Sensor not connected)
0x0C BAD device failure
0x10 BAD Sensor failure (e.g. Temp Sensor Short Circuit)
0x47 UNCERTAIN Last usable value (HOLD) CONST
0x50 UNCERTAIN Sensor conversion not accurate(e.g. No Flow)
OK
0x64
0x67
UNCERTAIN Sensor calibration Sensor calibration, hold
OK CONST
0x80 GOOD ok OK
0x89
0x8A
GOOD Warning Low Warning High
LOW_LIM HIGH_LIM
0x8D
0x8E
GOOD Alarm Low Alarm High
LOW_LIM HICH_LIM
Tab. 7-5 DP Diagnostics
Byte Description
0 Status 1 Standard DP Diagnostics1 Status 2
2 Status 3
3 Master address
4 Ident number (high byte)
5 Ident number (low byte)
6 Header (block length incl. Header byte) = 14 Status coding according to DP/V17 Status Type (0x81)
8 Slot Number (0x00)
9 Status Specifier
10–13 Diagnosis
14–19 Diagnosis Extension
A-96.250.731 / 150513 51
ProfibusProduct Specific Data for AMI Hydrogen
Tab. 7-6 The diagnosis object consists of 4 Bytes
Byte Bit Meaning when “1” Abbreviation
0 0 Hardware failure electronics DIA_HW_ELECTR
1 Hardware failure mechanics DIA_HW_MECH
2 -
3 Electronic temperature too high DIA_TEMP_ELECTR
4 -
5 Measurement failure DIA_MEASUREMENT
6 -
7 -
1 0 -
1 -
2 -
3 -
4 -
5 Maintenance required DIA_MAINTENANCE
6 -
7 -
2 0 -
1 -
2 -
3 -
4 -
5 -
6 -
7 -
3 0 -
1 -
2 -
3 -
4 -
5 -
6 -
7 Extension Available EXTENSION_AVAILABLE
52 A-96.250.731 / 150513
ProfibusProduct Specific Data for AMI Hydrogen
Byte 5 is reserved for future extensions.
Tab. 7-7 The diagnosis extension object consists of 5 Bytes.
Byte Bit Meaning when “1” Abbreviation
0 0
1
2
3
4
5
6
7
1 0 Sample Flow high DIA_MEASUREMENT
1 Sample Flow low DIA_MEASUREMENT
2 Temp. shorted DIA_HW_ELECTR
3 Temp. disconnected DIA_HW_ELECTR
4 Case Temp. high DIA_TEMP_ELECTR
5 Case Temp. low DIA_TEMP_ELECTR
6 Counter Electrode Reference DIA_MEASUREMENT
7
2 0 Control Timeout -
1
2
3
4
5
6 Cleaning Reagent DIA_MAINTENANCE
7 Input Active DIA_HW_ELECTR
3 0 IC MK41T56 DIA_HW_ELECTR
1 IC LM75 DIA_HW_ELECTR
2 IC PCF8574 DIA_HW_ELECTR
3 EEprom Microcon DIA_HW_ELECTR
4 EEProm Motherboard DIA_HW_ELECTR
5 EEProm Front-end DIA_HW_ELECTR
6 Cal. Recout DIA_HW_ELECTR
7 Wrong Front-end DIA_HW_ELECTR
A-96.250.731 / 150513 53
ProfibusProduct Specific Data for AMI Hydrogen
7.3. Configuration
7.3.1 Device Master Files (GSD)
The device is ready for system integration once commissioning has been effected via the local display or the Class 2 master. The PROFIBUS system requires a description of the device parameters, e.g. output data, input data, data format, data volume and supported transmission rate, so that it can integrate the field devices into the bus system. These data are contained in a Device Master File (GSD file) which is placed at the disposal of the PROFIBUS master while the communication system is being commissioned. Device bitmaps can also be integrated. These appear as icons in the network tree.The Profile 3.0 Device Master File (GSD) allows field devices from various manufacturers to be exchanged without having to reconfigure.
7.3.2 GSD File Types
Prior to configuration, decide which GSD you want to use to operate the system.You can change the setting by means of a Class 2 master (under Physical Block-Parameter Ident_Number_Selector)The following two Device Master Files with different functionalities are available:Manufacturer-specific GSD with Profile 3.0 functionality (default setting):This GSD guarantees the unlimited functionality of the field device. Device-specific process parameters and functions are therefore available.Profile GSD's:If a system is configured with profile GSD's, it is possible to exchange devices that are supplied by various manufacturers. It is, however, essential that the cyclic process values follow the same sequence. The transmitter supports the profiles Analyzer and Multivariable (IEC 61158-2). These GSD's comprise Analog Input blocks (AI)
Working with GSD filesThe GSDs must be integrated into the automation system. Depending on the software that is being used, the GSD files can be copied to the program-specific directory or can be read into the database using the import function within the configuration software.
Tab. 7-8 GSD files for AMI Hydrogen:
Device name Ident_number_
Selector
ID number GSD Bitmaps
Manufacturer specific GSD with Profile 3.0 functionality:
AMI Hydrogen 1 17E4Hex SW17E4.gsd SW17E4_D.bmp SW17E4_N.bmp SW17E4_S.bmp
Profile 3.0 GSD Analyzer:
AMI Hydrogen 0 9750 Hex PA039750.gsd PA_9750n.bmp
Profile 3.0 GSD Multivariable:
AMI Hydrogen 3 9760 Hex PA039760.gsd PA_9760n.bmp
54 A-96.250.731 / 150513
ProfibusProduct Specific Data for AMI Inducon
8. Product Specific Data for AMI Inducon
8.1. Introduction
The AMI family of transmitters provides a common base for a number of analytical instruments with application specific sensor interfaces. Each instrument has a basic structure with identical functionality.AMI instruments can (optionally) be equipped with a PROFIBUS DP-V1 interface. The interface supports the PROFIBUS-PA Profile 3.0. This part of the manual describes the functionality of the interface and the integration of the AMI family of transmitters into an automation system.
Hardware Wiring, bus terminals and connectors are not part of this manual. It should, however, be noted that the observation of the corresponding standards is of paramount importance to proper operation. Setting the transmission rate to reasonable values will help avoid communication errors.
GSD File forAMI Inducon
The PROFIBUS system requires a description of the device parameters, e. g. output data, input data, data format, data volume and supported transmission rate, so that it can integrate the field devices into the bus system. These data are contained in a Device Master File (GSD file) which is placed at the disposal of the PROFIBUS master while communication system is being commissioned.
Device bitmaps can also be integrated. These appear as icons in the network tree.The manufacturer-specific GSD file SW17D7.gsd is available for download from http://www.swan.ch
8.2. Cyclic Data Telegram
Input Data The AMI Inducon makes the following modules available as input data for the cyclic data exchange:
1 Main Process Value (µS/cm)
2 Main Temperature
3 Main Flow (l/h)
4 2nd Process Value (µS/cm)
5 Diagnostic Values (5 Values)
– Conc. raw Value in µS/cm
– Cell Factor
– Reserved (for internal use)
– Reserved (for internal use)
– Case Temperature in °C
The input data is transferred from AMI Inducon in the following structure:
A-96.250.731 / 140212 55
ProfibusProduct Specific Data for AMI Inducon
Output Data The AMI Inducon makes the following module available as output data for the cyclic data exchange:
1 Control AMI
The control data is transferred to the AMI Inducon in the following structure:
Tab. 8-1 Input data structure of AMI Inducon
Index input data Data Access
Data format / comments Configuration data
0–4 Analog Input block 1 Main Process Value
read Measured value (32-bit floating point number) Status byte
0x42, 0x84, 0x08, 0x05 or 0x42, 0x84, 0x81, 0x81 or 0x94
5–9 Analog Input block 2 Main Temperature
read Measured value (32-bit floating point number) Status byte
0x42, 0x84, 0x08, 0x05 or 0x42, 0x84, 0x81, 0x81 or 0x94
10–14 Analog Input block 3 Main Flow
read Measured value (32-bit floating point number) Status byte
0x42, 0x84, 0x08, 0x05 or 0x42, 0x84, 0x81, 0x81 or 0x94
15–19 Analog Input block 42nd Process Value
read Measured value (32-bit floating point number) Status byte
0x42, 0x84, 0x08, 0x05 or 0x42, 0x84, 0x81, 0x81 or 0x94
20–39 Diagnostic Values read 5 Measured values (32-bit floating point number)
0x45, 0x93, 0x08, 0x08, 0x08, 0x08, 0x080xD9
Tab. 8-2 Output data structure
Index output data Data Access Data format / comments Configuration data
0–1 Control AMI
(SP_D)
write Byte 0Bit 0: Relay 1
0 = open1 = close
0x82, 0x81, 0x05, 0x05 or 0x82, 0x81, 0x84, 0x82 or 0xA1
Bit 1: Relay 2 0 = open1 = close
Bit 2–7: not used
Byte 1Bit 0:
Hold
Bit 1: Control Off
Bit 2–7: not used
56 A-96.250.731 / 140212
ProfibusProduct Specific Data for AMI Inducon
8.2.1 Data Formats
For further information see chapter 1 Data Formats, p. 7
Tab. 8-3 Status Code Byte
7 6 5 4 3 2 1 0
Quality Sub-Status Limits Meaning
0 0 The sub-status has a different quality depending on the coding
bad
0 1 uncertain
1 0 good
0 0 ok
0 1 low limited
1 0 high limited
1 1 constant
Tab. 8-4 Status codes of the measured value
Status
code
Device status Meaning Limits
0x08 BAD Not connected (Temp Sensor not connected)
0x0C BAD device failure
0x10 BAD Sensor failure (Temp Sensor Short Circuit)
0x47 UNCERTAIN Last usable value (HOLD) CONST
0x50 UNCERTAIN Sensor conversion not accurate (e.g. No Flow) OK
0x64
0x67
UNCERTAIN Sensor calibration Sensor calibration, hold
OK CONST
0x80 GOOD ok OK
0x89
0x8A
GOOD Warning Low Warning High
LOW_LIM HIGH_LIM
0x8D
0x8E
GOOD Alarm Low Alarm High
LOW_LIM HICH_LIM
Tab. 8-5 DP Diagnostics
Byte Description
0 Status 1 Standard DP Diagnostics1 Status 2
2 Status 3
3 Master address
4 Ident number (high byte)
5 Ident number (low byte)
6 Header (block length incl. Header byte) = 14 Status coding according to DP/V17 Status Type (0x81)
8 Slot Number (0x00)
9 Status Specifier
10–13 Diagnosis
14–19 Diagnosis Extension
A-96.250.731 / 140212 57
ProfibusProduct Specific Data for AMI Inducon
Tab. 8-6 The diagnosis object consists of 4 Bytes
Byte Bit Meaning when “1” Abbreviation
0 0 Hardware failure electronics DIA_HW_ELECTR
1 Hardware failure mechanics DIA_HW_MECH
2 -
3 Electronic temperature too high DIA_TEMP_ELECTR
4 -
5 Measurement failure DIA_MEASUREMENT
6 -
7 -
1 0 -
1 -
2 -
3 -
4 -
5 Maintenance required DIA_MAINTENANCE
6 -
7 -
2 0 -
1 -
2 -
3 -
4 -
5 -
6 -
7 -
3 0 -
1 -
2 -
3 -
4 -
5 -
6 -
7 Extension Available EXTENSION_AVAILABLE
58 A-96.250.731 / 140212
ProfibusProduct Specific Data for AMI Inducon
Bytes 4 and 5 are reserved for future extensions.
Tab. 8-7 The diagnosis extension object consists of 6 Bytes.
Byte Bit Meaning when “1” Abbreviation
0 0 Cond. Alarm high -
1 Cond. Alarm low -
2 Conc. Alarm high -
3 Conc. Alarm low -
4 -
5 -
6 Sample Temp. high DIA_MEASUREMENT
7 Sample Temp. low DIA_MEASUREMENT
1 0 Sample Flow high DIA_MEASUREMENT
1 Sample Flow low DIA_MEASUREMENT
2 Temp. shorted DIA_HW_ELECTR
3 Temp. disconnected DIA_HW_ELECTR
4 Case Temp. high DIA_TEMP_ELECTR
5 Case Temp. low DIA_TEMP_ELECTR
6
7
2 0 Control Timeout -
1 Temp. out of table DIA_MEASUREMENT
2 Conc. out of table DIA_MEASUREMENT
3
4
5
6
7 Input Active DIA_HW_ELECTR
3 0 IC MK41T56 DIA_HW_ELECTR
1 IC LM75 DIA_HW_ELECTR
2 IC PCF8574 DIA_HW_ELECTR
3 EEprom Microcon DIA_HW_ELECTR
4 EEProm Motherboard DIA_HW_ELECTR
5 EEProm Front-end DIA_HW_ELECTR
6 Cal. Recout DIA_HW_ELECTR
7 Wrong Front-end DIA_HW_ELECTR
A-96.250.731 / 140212 59
ProfibusProduct Specific Data for AMI Inducon
8.3. Configuration
8.3.1 Device Master Files (GSD)
The device is ready for system integration once commissioning has been effected via the local display or the Class 2 master. The PROFIBUS system requires a description of the device parameters, e.g. output data, input data, data format, data volume and supported transmission rate, so that it can integrate the field devices into the bus system. These data are contained in a Device Master File (GSD file) which is placed at the disposal of the PROFIBUS master while the communication system is being commissioned. Device bitmaps can also be integrated. These appear as icons in the network tree.The Profile 3.0 Device Master File (GSD) allows field devices from various manufacturers to be exchanged without having to reconfigure.
8.3.2 GSD File Types
Prior to configuration, decide which GSD you want to use to operate the system.You can change the setting by means of a Class 2 master (under Physical Block-Parameter Ident_Number_Selector)The following two Device Master Files with different functionalities are available:Manufacturer-specific GSD with Profile 3.0 functionality (default setting):This GSD guarantees the unlimited functionality of the field device. Device-specific process parameters and functions are therefore available.Profile GSD's:If a system is configured with profile GSD's, it is possible to exchange devices that are supplied by various manufacturers. It is, however, essential that the cyclic process values follow the same sequence. The transmitter supports the profiles Analyzer and Multivariable (IEC 61158-2). These GSD's comprise Analog Input blocks (AI).
Working with GSD filesThe GSDs must be integrated into the automation system. Depending on the software that is being used, the GSD files can be copied to the program-specific directory or can be read into the database using the import function within the configuration software.
Tab. 8-8 GSD files for AMI Inducon
Device name Ident_number_
Selector
ID number GSD Bitmaps
Manufacturer specific GSD with Profile 3.0 functionality:
AMI Inducon 1 17D7Hex SW17D7.gsd SW17D7_D.bmp SW17D7_N.bmp SW17D7_S.bmp
Profile 3.0 GSD Analyzer:
AMI Inducon 0 9750 Hex PA039750.gsd PA_9750n.bmp
Profile 3.0 GSD Multivariable:
AMI Inducon 3 9760 Hex PA039760.gsd PA_9760n.bmp
60 A-96.250.731 / 140212
ProfibusProduct Specific Data for AMI ISE
9. Product Specific Data for AMI ISE
9.1. Introduction
The AMI family of transmitters provides a common base for a number of analytical instruments with application specific sensor interfaces. Each instrument has a basic structure with identical functionality.AMI instruments can (optionally) be equipped with a PROFIBUS DP-V1 interface. The interface supports the PROFIBUS-PA Profile 3.0. This part of the manual describes the functionality of the interface and the integration of the AMI family of transmitters into an automation system.
Hardware Wiring, bus terminals and connectors are not part of this manual. It should, however, be noted that the observation of the corresponding standards is of paramount importance to proper operation. Setting the transmission rate to reasonable values will help avoid communication errors.
GSD File forAMI ISE
The PROFIBUS system requires a description of the device parameters, e. g. output data, input data, data format, data volume and supported transmission rate, so that it can integrate the field devices into the bus system. These data are contained in a Device Master File (GSD file) which is placed at the disposal of the PROFIBUS master while communication system is being commissioned.
Device bitmaps can also be integrated. These appear as icons in the network tree.The manufacturer-specific GSD file SW17E5.gsd is available for download from http://www.swan.ch
9.2. Cyclic Data Telegram
Input Data The AMI ISE makes the following modules available as input data for the cyclic data exchange:
1 Main Process Value
2 Main Temperature
3 Main Flow (l/h)
4 Diagnostic Values (5 Values)
– Raw Value in mV
– Raw Value in mV
– deltaT 1
– deltaT 2
– Case Temperature in °C
A-96.250.731 / 011012 61
ProfibusProduct Specific Data for AMI ISE
The input data is transferred from AMI ISE in the following structure:
Output Data The AMI ISE makes the following module available as output data for the cyclic data exchange:
1 Control AMI
The control data is transferred to the AMI ISE in the following structure:
Tab. 9-1 Input data structure of AMI ISE
Index input data Data Access
Data format / comments Configuration data
0–4 Analog Input block 1 Main Process Value
read Measured value (32-bit floating point number) Status byte
0x42, 0x84, 0x08, 0x05 or 0x42, 0x84, 0x81, 0x81 or 0x94
5–9 Analog Input block 2 Main Temperature
read Measured value (32-bit floating point number) Status byte
0x42, 0x84, 0x08, 0x05 or 0x42, 0x84, 0x81, 0x81 or 0x94
10–14 Analog Input block 3 Main Flow
read Measured value (32-bit floating point number) Status byte
0x42, 0x84, 0x08, 0x05 or 0x42, 0x84, 0x81, 0x81 or 0x94
15–34 Diagnostic Values read 5 Measured values (32-bit floating point number)
0x45, 0x93, 0x08, 0x08, 0x08, 0x08, 0x080xD9
Tab. 9-2 Output data structure
Index output data Data Access Data format / comments Configuration data
0–1 Control AMI
(SP_D)
write Byte 0Bit 0: Relay 1
0 = open1 = close
0x82, 0x81, 0x05, 0x05 or 0x82, 0x81, 0x84, 0x82 or 0xA1
Bit 1: Relay 2 0 = open1 = close
Bit 2–7: not used
Byte 1Bit 0:
Hold
Bit 1: Control Off
Bit 2: Start pH Sen-sor check
To start a Sensor check, set this bit to "1" for 5 sec-onds, the reset to "0
Bit 3–7: not used
62 A-96.250.731 / 011012
ProfibusProduct Specific Data for AMI ISE
9.2.1 Data Formats
For further information see chapter 1 Data Formats, p. 7
Tab. 9-3 Status Code Byte
7 6 5 4 3 2 1 0
Quality Sub-Status Limits Meaning
0 0 The sub-status has a different quality depending on the coding
bad
0 1 uncertain
1 0 good
0 0 ok
0 1 low limited
1 0 high limited
1 1 constant
Tab. 9-4 Status codes of the measured value
Status
code
Device status Meaning Limits
0x08 BAD Not connected (Temp Sensor not connected)
0x0C BAD device failure
0x10 BAD Sensor failure (Temp Sensor Short Circuit)
0x47 UNCERTAIN Last usable value (HOLD) CONST
0x50 UNCERTAIN Sensor conversion not accurate (e.g. No Flow) OK
0x64
0x67
UNCERTAIN Sensor calibration Sensor calibration, hold
OK CONST
0x80 GOOD ok OK
0x89
0x8A
GOOD Warning Low Warning High
LOW_LIM HIGH_LIM
0x8D
0x8E
GOOD Alarm Low Alarm High
LOW_LIM HICH_LIM
Tab. 9-5 DP Diagnostics
Byte Description
0 Status 1 Standard DP Diagnostics1 Status 2
2 Status 3
3 Master address
4 Ident number (high byte)
5 Ident number (low byte)
6 Header (block length incl. Header byte) = 14 Status coding according to DP/V17 Status Type (0x81)
8 Slot Number (0x00)
9 Status Specifier
10–13 Diagnosis
14–19 Diagnosis Extension
A-96.250.731 / 011012 63
ProfibusProduct Specific Data for AMI ISE
Tab. 9-6 The diagnosis object consists of 4 Bytes
Byte Bit Meaning when “1” Abbreviation
0 0 Hardware failure electronics DIA_HW_ELECTR
1 Hardware failure mechanics DIA_HW_MECH
2 -
3 Electronic temperature too high DIA_TEMP_ELECTR
4 -
5 Measurement failure DIA_MEASUREMENT
6 -
7 -
1 0 -
1 -
2 -
3 -
4 -
5 Maintenance required DIA_MAINTENANCE
6 -
7 -
2 0 -
1 -
2 -
3 -
4 -
5 -
6 -
7 -
3 0 -
1 -
2 -
3 -
4 -
5 -
6 -
7 Extension Available EXTENSION_AVAILABLE
64 A-96.250.731 / 011012
ProfibusProduct Specific Data for AMI ISE
Bytes 4 and 5 are reserved for future extensions.
Tab. 9-7 The diagnosis extension object consists of 6 Bytes.
Byte Bit Meaning when “1” Abbreviation
0 0 Alarm high
1 Alarm low
2
3
4
5
6 Sample Temp. high DIA_MEASUREMENT
7 Sample Temp. low DIA_MEASUREMENT
1 0 Sample Flow high DIA_MEASUREMENT
1 Sample Flow low DIA_MEASUREMENT
2 Temp. shorted DIA_HW_ELECTR
3 Temp. disconnected DIA_HW_ELECTR
4 Case Temp. high DIA_TEMP_ELECTR
5 Case Temp. low DIA_TEMP_ELECTR
6
7
2 0 Control Timeout -
1
2
3
4
5
6
7 Input Active DIA_HW_ELECTR
3 0 IC MK41T56 DIA_HW_ELECTR
1 IC LM75 DIA_HW_ELECTR
2 IC PCF8574 DIA_HW_ELECTR
3 EEprom Microcon DIA_HW_ELECTR
4 EEProm Motherboard DIA_HW_ELECTR
5 EEProm Front-end DIA_HW_ELECTR
6 Cal. Recout DIA_HW_ELECTR
7 Wrong Front-end DIA_HW_ELECTR
A-96.250.731 / 011012 65
ProfibusProduct Specific Data for AMI ISE
9.3. Configuration
9.3.1 Device Master Files (GSD)
The device is ready for system integration once commissioning has been effected via the local display or the Class 2 master. The PROFIBUS system requires a description of the device parameters, e.g. output data, input data, data format, data volume and supported transmission rate, so that it can integrate the field devices into the bus system. These data are contained in a Device Master File (GSD file) which is placed at the disposal of the PROFIBUS master while the communication system is being commissioned. Device bitmaps can also be integrated. These appear as icons in the network tree.The Profile 3.0 Device Master File (GSD) allows field devices from various manufacturers to be exchanged without having to reconfigure.
9.3.2 GSD File Types
Prior to configuration, decide which GSD you want to use to operate the system.You can change the setting by means of a Class 2 master (under Physical Block-Parameter Ident_Number_Selector)The following two Device Master Files with different functionalities are available:Manufacturer-specific GSD with Profile 3.0 functionality (default setting):This GSD guarantees the unlimited functionality of the field device. Device-specific process parameters and functions are therefore available.Profile GSD's:If a system is configured with profile GSD's, it is possible to exchange devices that are supplied by various manufacturers. It is, however, essential that the cyclic process values follow the same sequence. The transmitter supports the profiles Analyzer and Multivariable (IEC 61158-2). These GSD's comprise Analog Input blocks (AI).
Working with GSD filesThe GSDs must be integrated into the automation system. Depending on the software that is being used, the GSD files can be copied to the program-specific directory or can be read into the database using the import function within the configuration software.
Tab. 9-8 GSD files for AMI ISE
Device name Ident_number_
Selector
ID number GSD Bitmaps
Manufacturer specific GSD with Profile 3.0 functionality:
AMI ISE 1 17E5Hex SW17E5.gsd SW17E5_D.bmp SW17E5_N.bmp SW17E5_S.bmp
Profile 3.0 GSD Analyzer:
AMI ISE 0 9750 Hex PA039750.gsd PA_9750n.bmp
Profile 3.0 GSD Multivariable:
AMI ISE 3 9760 Hex PA039760.gsd PA_9760n.bmp
66 A-96.250.731 / 011012
ProfibusProduct Specific Data for AMI LineTOC
10. Product Specific Data for AMI LineTOC
10.1. Introduction
The AMI family of transmitters provides a common base for a number of analytical instruments with application specific sensor interfaces. Each instrument has a basic structure with identical functionality.AMI instruments can (optionally) be equipped with a PROFIBUS DP-V1 interface. The interface supports the PROFIBUS-PA Profile 3.0. This part of the manual describes the functionality of the interface and the integration of the AMI family of transmitters into an automation system.
Hardware Wiring, bus terminals and connectors are not part of this manual. It should, however, be noted that the observation of the corresponding standards is of paramount importance to proper operation. Setting the transmission rate to reasonable values will help avoid communication errors.
GSD File forAMI LineTOC
The PROFIBUS system requires a description of the device parameters, e. g. output data, input data, data format, data volume and supported transmission rate, so that it can integrate the field devices into the bus system. These data are contained in a Device Master File (GSD file) which is placed at the disposal of the PROFIBUS master while communication system is being commissioned.
Device bitmaps can also be integrated. These appear as icons in the network tree.The manufacturer-specific GSD file SW17D8.gsd is available for download from http://www.swan.ch
10.2. Cyclic Data Telegram
Input Data The AMI LineTOC makes the following modules available as input data for the cyclic data exchange:
1 Main Process Value in ppb: TOC
2 1st Conductivity in µS/cm
3 2nd Conductivity in µS/cm
4 1st Temperature in °C
5 2nd Temperature in °C
6 Flow Check Temperature in °C
7 1st Concentration in ppb: (TIC)
8 2nd Concentration in ppb: (TC)
9 Diagnostic Values (5 Values)
– 1st Conductivity uc in µS/cm
– 2nd Conductivity uc in µS/cm
– Ambient Temp. in °C
– Sample Temp. in °C
– Case Temperature in °C
A-96.250.731 / 140212 67
ProfibusProduct Specific Data for AMI LineTOC
The input data is transferred from the AMI LineTOC in the following structure:
Output Data The AMI LineTOC makes the following module available as output data for the cyclic data exchange:
1 Control AMI
The control data is transferred to the AMI LineTOC in the following structure:
Tab. 10-1 Input data structure from AMI LineTOC
Index input data Data Access
Data format / comments Configuration data
0–4 Analog Input block 1 Main Process Value
read Measured value (32-bit floating point number) Status byte
0x42, 0x84, 0x08, 0x05 or 0x42, 0x84, 0x81, 0x81 or 0x94
5–9 Analog Input block 2 1st Conductivity
read Measured value (32-bit floating point number) Status byte
0x42, 0x84, 0x08, 0x05 or 0x42, 0x84, 0x81, 0x81 or 0x94
10–14 Analog Input block 3 2nd Conductivity
read Measured value (32-bit floating point number) Status byte
0x42, 0x84, 0x08, 0x05 or 0x42, 0x84, 0x81, 0x81 or 0x94
15–19 Analog Input block 4 1st Temperature
read Measured value (32-bit floating point number) Status byte
0x42, 0x84, 0x08, 0x05 or 0x42, 0x84, 0x81, 0x81 or 0x94
20–24 Analog Input block 52nd Temperature
read Measured value (32-bit floating point number) Status byte
0x42, 0x84, 0x08, 0x05 or 0x42, 0x84, 0x81, 0x81 or 0x94
25–29 Analog Input block 6Flow Check Tem-perature in °C
read Measured value (32-bit floating point number) Status byte
0x42, 0x84, 0x08, 0x05 or 0x42, 0x84, 0x81, 0x81 or 0x94
30–34 Analog Input block 71st Concentration
read Measured value (32-bit floating point number) Status byte
0x42, 0x84, 0x08, 0x05 or 0x42, 0x84, 0x81, 0x81 or 0x94
35–39 Analog Input block 82nd Concentration
read Measured value (32-bit floating point number) Status byte
0x42, 0x84, 0x08, 0x05 or 0x42, 0x84, 0x81, 0x81 or 0x94
40–59 Diagnostic Values read 5 Measured values (32-bit floating point number)
0x45, 0x93, 0x08, 0x08, 0x08, 0x08, 0x08 or0xD9
Tab. 10-2 Output data structure
Index output data Data Access Data format / comments Configuration data
0–1 Control AMI (SP_D)
write Byte 0Bit 0: Relay 1
0 = open1 = close
0x82, 0x81, 0x05, 0x05 or 0x82, 0x81, 0x84, 0x82 or 0xA1
Bit 1: Relay 20 = open1 = close
Bit 2–7: Not used
Byte 1Bit 0: Hold
Bit 1: Control Off
Bit 2–7: not used
68 A-96.250.731 / 140212
ProfibusProduct Specific Data for AMI LineTOC
10.2.1 Data Formats
For further information see chapter 1 Data Formats, p. 7
Tab. 10-3 Status Code Byte
7 6 5 4 3 2 1 0
Quality Sub-Status Limits Meaning
0 0 The sub-status has a different quality depending on the coding
bad
0 1 uncertain
1 0 good
0 0 ok
0 1 low limited
1 0 high limited
1 1 constant
Tab. 10-4 Status codes of the measured value
Status code
Device status Meaning Limits
0x08 BAD Not connected (Temp. Sensor not connected)
0x0C BAD device failure
0x10 BAD Sensor failure (Temp. Sensor Short Circuit)
0x47 UNCERTAIN Last usable value (HOLD) CONST
0x4F UNCERTAIN Initial value CONST
0x50 UNCERTAIN Sensor conversion not accurate (No Flow) OK
0x640x67
UNCERTAIN Sensor calibration Sensor calibration, hold
OK CONST
0x80 GOOD ok OK
0x890x8A
GOOD Warning Low Warning High
LOW_LIM HIGH_LIM
0x8D0x8E
GOOD Alarm Low Alarm High
LOW_LIM HICH_LIM
Tab. 10-5 DP Diagnostics
Byte Description
0 Status 1 Standard DP Diagnostics
1 Status 2
2 Status 3
3 Master address
4 Ident number (high byte)
5 Ident number (low byte)
6 Header (block length incl. Header byte) = 14 Status coding according to DP/V17 Status Type (0x81)
8 Slot Number (0x00)
9 Status Specifier
10–13 Diagnosis
14–19 Diagnosis Extension
A-96.250.731 / 140212 69
ProfibusProduct Specific Data for AMI LineTOC
Tab. 10-6 The diagnosis object consists of 4 Bytes
Byte Bit Meaning when “1” Abbreviation
0 0 Hardware failure electronics DIA_HW_ELECTR
1 Hardware failure mechanics DIA_HW_MECH
2 -
3 Electronic temperature too high DIA_TEMP_ELECTR
4 -
5 Measurement failure DIA_MEASUREMENT
6 -
7 -
1 0 -
1 -
2 -
3 -
4 -
5 Maintenance required DIA_MAINTENANCE
6 -
7 -
2 0 -
1 -
2 -
3 -
4 -
5 -
6 -
7 -
3 0 -
1 -
2 -
3 -
4 -
5 -
6 -
7 Extension Available EXTENSION_AVAILABLE
70 A-96.250.731 / 140212
ProfibusProduct Specific Data for AMI LineTOC
Bytes 4 and 5 are reserved for future extensions.
Tab. 10-7 The diagnosis extension object consists of 6 Bytes.
Byte Bit Meaning when “1” Abbreviation
0 0
1
2 Cond. 1 Alarm high DIA_MEASUREMENT
3 Cond. 1 Alarm low DIA_MEASUREMENT
4 Cond. 2 Alarm high DIA_MEASUREMENT
5 Cond. 2 Alarm low DIA_MEASUREMENT
6 Temp. 1 Alarm high DIA_MEASUREMENT
7 Temp. 1 Alarm low DIA_MEASUREMENT
1 0
1 Sample Flow low DIA_MEASUREMENT
2 Temp. 1 shorted DIA_HW_ELECTR
3 Temp. 1 disconnected DIA_HW_ELECTR
4 Case Temp. high DIA_TEMP_ELECTR
5 Case Temp. low DIA_TEMP_ELECTR
6 Lamp DIA_HW_ELECTR
7 Rovlave DIA_HW_ELECTR
2 0
1 Periclip disconnedted DIA_HW_ELECTR
2 Temp. 2 shorted DIA_HW_ELECTR
3 Temp. 2 disconnected DIA_HW_ELECTR
4 Temp. 2 Alarm high DIA_MEASUREMENT
5 Temp. 2 Alarm low DIA_MEASUREMENT
6 EVG DIA_HW_ELECTR
7 Input Active DIA_HW_ELECTR
3 0 IC MK41T56 DIA_HW_ELECTR
1 IC LM75 DIA_HW_ELECTR
2 IC PCF8574 DIA_HW_ELECTR
3 EEprom Microcon DIA_HW_ELECTR
4 EEProm Motherboard DIA_HW_ELECTR
5 EEProm Front-end DIA_HW_ELECTR
6 Cal. Recout DIA_HW_ELECTR
7 Wrong Front-end DIA_HW_ELECTR
A-96.250.731 / 140212 71
ProfibusProduct Specific Data for AMI LineTOC
10.3. Configuration
10.3.1 Device Master Files (GSD)
The device is ready for system integration once commissioning has been effected via the local display or the Class 2 master. The PROFIBUS system requires a description of the device parameters, e.g. output data, input data, data format, data volume and supported transmission rate, so that it can integrate the field devices into the bus system. These data are contained in a Device Master File (GSD file) which is placed at the disposal of the PROFIBUS master while the communication system is being commissioned. Device bitmaps can also be integrated. These appear as icons in the network tree. The Profile 3.0 Device Master File (GSD) allows field devices from various manufacturers to be exchanged without having to reconfigure.
10.3.2 GSD File Types
Prior to configuration, decide which GSD you want to use to operate the system. You can change the setting by means of a Class 2 master (under Physical Block-Parame-
ter Ident_Number_Selector)The following two Device Master Files with different functionalities are available: Manufacturer-specific GSD with Profile 3.0 functionality (default setting): This GSD guarantees the unlimited functionality of the field device. Device-specific pro-
cess parameters and functions are therefore available. Profile GSD's: If a system is configured with profile GSD's, it is possible to exchange devices that are
supplied by various manufacturers. It is, however, essential that the cyclic process values follow the same sequence. The transmitter supports the profiles Analyzer and Multivaria-ble (IEC 61158-2). These GSD's comprise Analog Input blocks (AI)
Working with GSD filesThe GSDs must be integrated into the automation system. Depending on the software that is being used, the GSD files can be copied to the program-specific directory or can be read into the database using the import function within the configuration software.
Tab. 10-8 GSD files for AMI LineTOC:
Device name Ident_number_
Selector
ID number GSD Bitmaps
Manufacturer specific GSD with Profile 3.0 functionality:
AMI LineTOC 1 17D8Hex SW17D8.gsd SW17D8_D.bmp
SW17D8_N.bmp SW17D8_S.bmp
Profile 3.0 GSD Analyzer:
AMI LineTOC 0 9750 Hex PA139750.gsd PA_9750n.bmp
Profile 3.0 GSD Multivariable:
AMI LineTOC 3 9760 Hex PA139760.gsd PA_9760n.bmp
72 A-96.250.731 / 140212
ProfibusProduct Specific Data for Oxysafe
11. Product Specific Data for Oxysafe
11.1. Introduction
The AMI Oxysafe is a complete monitoring system for the automatic, continuous measurement of dissolved oxygen in sewage treatment water (aeration basins), fish rearing and surface water such as lakes, rivers and ponds.The AMI Oxysafe is a Electronic transmitter/controller for the measurement of dissolved oxygen in high purity water.The AMI family of transmitters provides a common base for a number of analytical instruments with application specific sensor interfaces. Each instrument has a basic structure with identical functionality.AMI instruments can (optionally) be equipped with a PROFIBUS DP-V1 interface. The interface supports the PROFIBUS-PA Profile 3.0. This part of the manual describes the functionality of the interface and the integration of the AMI family of transmitters into an automation system.
Hardware Wiring, bus terminals and connectors are not part of this manual. It should, however, be noted that the observation of the corresponding standards is of paramount importance to proper operation. Setting the transmission rate to reasonable values will help avoid communication errors.
GSD File forAMI Oxysafe
The PROFIBUS system requires a description of the device parameters, e. g. output data, input data, data format, data volume and supported transmission rate, so that it can integrate the field devices into the bus system. These data are contained in a Device Master File (GSD file) which is placed at the disposal of the PROFIBUS master while communication system is being commissioned.
Device bitmaps can also be integrated. These appear as icons in the network tree.The manufacturer-specific GSD file SW17E2.gsd is available for download fromhttp://www.swan.ch
11.2. Cyclic Data Telegram
Input Data The the AMI Oxysafe makes the following modules available as input data for the cyclic data exchange:
1 Main Process Value (ppb)
2 Main Temperature
3 Main Flow (l/h)
4 2nd Process Value %
5 Diagnostic Values (5 values)
– Raw Current Temperature Compensated in nA
– Raw Current in nA
– Air Pressure in hPa
– Reserved
– Case Temperature in °C
A-96.250.731 / 150513 73
ProfibusProduct Specific Data for Oxysafe
The input data is transferred from AMI Oxysafe in the following structure:
Output Data The AMI Oxysafe and the AMI Oxysafe make the following module available as output data for the cyclic data exchange:
1 Control AMI
The control data is transferred to the AMI Oxysafe in the following structure:
Tab. 11-1 Input data structure from AMI Oxysafe
Index input data Data Access
Data format / comments Configuration data
0–4 Analog Input block 1 Main Process Value
read Measured value (32-bit floating point number) Status byte
0x42, 0x84, 0x08, 0x05 or 0x42, 0x84, 0x81, 0x81 or 0x94
5–9 Analog Input block 2Main Temperature
read Measured value (32-bit floating point number) Status byte
0x42, 0x84, 0x08, 0x05 or 0x42, 0x84, 0x81, 0x81 or 0x94
10–14 Analog Input block 3Main Flow
read Measured value (32-bit floating point number) Status byte
0x42, 0x84, 0x08, 0x05 or 0x42, 0x84, 0x81, 0x81 or 0x94
15–19 Analog Input block 42nd Process Value
read Measured value (32-bit floating point number) Status byte
0x42, 0x84, 0x08, 0x05 or 0x42, 0x84, 0x81, 0x81 or 0x94
20–39 Diagnostic Values read 5 Measured values (32-bit floating point number)
0x45, 0x93, 0x08, 0x08, 0x08, 0x08, 0x08, 0xD9
Tab. 11-2 Output data structure:
Index output data Data Access Data format / comments Configuration data
0–1 Control AMI
(SP_D)
write Byte 0Bit 0: Relay 1
0 = open1 = close
0x82, 0x81, 0x05, 0x05 or 0x82, 0x81, 0x84, 0x82 or 0xA1
Bit 1: Relay 2 0 = open1 = close
Bit 2–7: not used
Byte 1Bit 0: Hold
Bit 1: Control Off
Bit 2–7: not used
74 A-96.250.731 / 150513
ProfibusProduct Specific Data for Oxysafe
11.2.1 Data Formats
For further information see chapter 1 Data Formats, p. 7
Tab. 11-3 Status Code Byte
7 6 5 4 3 2 1 0
Quality Sub-Status Limits Meaning
0 0 The sub-status has a different quality depending on the coding
bad
0 1 uncertain
1 0 good
0 0 ok
0 1 low limited
1 0 high limited
1 1 constant
Tab. 11-4 Status codes of the measured value
Status
code
Device status Meaning Limits
0x08 BAD Not connected (Temp Sensor not connected)
0x0C BAD device failure
0x10 BAD sensor failure (Temp Sensor Short Circuit)
0x47 UNCERTAIN Last usable value (HOLD) CONST
0x50 UNCERTAIN sensor conversion not accurate (e.g. No Flow) OK
0x64
0x67
UNCERTAIN Sensor calibration Sensor calibration, hold
OK CONST
0x80 GOOD ok OK
0x89
0x8A
GOOD Warning Low Warning High
LOW_LIM HIGH_LIM
0x8D
0x8E
GOOD Alarm Low Alarm High
LOW_LIM HICH_LIM
Tab. 11-5 DP Diagnostics
Byte Description
0 Status 1 Standard DP Diagnostics1 Status 2
2 Status 3
3 Master address
4 Ident number (high byte)
5 Ident number (low byte)
6 Header (block length incl. Header byte) = 14 Status coding accord-ing to DP/V17 Status Type (0x81)
8 Slot Number (0x00)
9 Status Specifier
10–13 Diagnosis
14–19 Diagnosis Extension
A-96.250.731 / 150513 75
ProfibusProduct Specific Data for Oxysafe
Tab. 11-6 The diagnosis object consists of 4 Bytes
Byte Bit Meaning when “1” Abbreviation
0 0 Hardware failure electronics DIA_HW_ELECTR
1 Hardware failure mechanics DIA_HW_MECH
2 -
3 Electronic temperature too high DIA_TEMP_ELECTR
4 -
5 Measurement failure DIA_MEASUREMENT
6 -
7 -
1 0 -
1 -
2 -
3 -
4 -
5 Maintenance required DIA_MAINTENANCE
6 -
7 -
2 0 -
1 -
2 -
3 -
4 -
5 -
6 -
7 -
3 0 -
1 -
2 -
3 -
4 -
5 -
6 -
7 Extension Available EXTENSION_AVAILABLE
76 A-96.250.731 / 150513
ProfibusProduct Specific Data for Oxysafe
Byte 6 is reserved for future extensions.
Tab. 11-7 The diagnosis extension object consists of 6 Bytes.
Byte Bit Meaning when “1” Abbreviation
0 0
1
2
3
4
5
6
7
1 0 Sample Flow high DIA_MEASUREMENT
1 Sample Flow low DIA_MEASUREMENT
Temp. shorted DIA_HW_ELECTR
3 Temp. disconnected DIA_HW_ELECTR
4 Case Temp. high DIA_TEMP_ELECTR
5 Case Temp. low DIA_TEMP_ELECTR
6
7
2 0 Control Timeout
1
2
3
4
5
6
7 Input active DIA_HW_ELECTR
3 0 IC MK41T56 DIA_HW_ELECTR
1 IC LM75 DIA_HW_ELECTR
2 IC PCF8574 DIA_HW_ELECTR
3 EEprom Microcon DIA_HW_ELECTR
4 EEProm Motherboard DIA_HW_ELECTR
5 I2C Rovalve DIA_HW_ELECTR
6 Cal. Recout DIA_HW_ELECTR
7 Wrong Frontend DIA_HW_ELECTR
4 0
1
2
3
4
5
6
7
A-96.250.731 / 150513 77
ProfibusProduct Specific Data for Oxysafe
11.3. Configuration
11.3.1 Device Master Files (GSD)
The device is ready for system integration once commissioning has been effected via the local display or the Class 2 master. The PROFIBUS system requires a description of the device parameters, e.g. output data, input data, data format, data volume and supported transmission rate, so that it can integrate the field devices into the bus system. These data are contained in a Device Master File (GSD file) which is placed at the disposal of the PROFIBUS master while the communication system is being commissioned. Device bitmaps can also be integrated. These appear as icons in the network tree. The Profile 3.0 Device Master File (GSD) allows field devices from various manufacturers to be exchanged without having to reconfigure.
11.3.2 GSD File Types
Prior to configuration, decide which GSD you want to use to operate the system. You can change the setting by means of a Class 2 master (under Physical Block-Parame-
ter Ident_Number_Selector)The following two Device Master Files with different functionalities are available: Manufacturer-specific GSD with Profile 3.0 functionality (default setting): This GSD guarantees the unlimited functionality of the field device. Device-specific pro-
cess parameters and functions are therefore available. Profile GSD's: If a system is configured with profile GSD's, it is possible to exchange devices that are
supplied by various manufacturers. It is, however, essential that the cyclic process values follow the same sequence. The transmitter supports the profiles Analyzer and Multivaria-ble (IEC 61158-2). These GSD's comprise Analog Input blocks (AI)
Working with GSD filesThe GSDs must be integrated into the automation system. Depending on the software that is being used, the GSD files can be copied to the program-specific directory or can be read into the database using the import function within the configuration software.
Tab. 11-8 GSD files for AMI Oxysafe:
Device name Ident_number_
Selector
ID number GSD Bitmaps
Manufacturer specific GSD with Profile 3.0 functionality:
AMI Oxysafe 1 17E2Hex SW17E2.gsd SW17E2_D.bmp
SW17E2_N.bmp SW17E2_S.bmp
Profile 3.0 GSD Analyzer:
AMI Oxysafe 0 9750 Hex PA139750.gsd PA_9750n.bmp
Profile 3.0 GSD Multivariable:
AMI Oxysafe 3 9760 Hex PA139760.gsd PA_9760n.bmp
78 A-96.250.731 / 150513
ProfibusProduct Specific Data for Oxytrace
12. Product Specific Data for Oxytrace
12.1. Introduction
The AMI Oxytrace is a complete monitoring system for the automatic, continuous measurement of dissolved oxygen in sewage treatment water (aeration basins), fish rearing and surface water such as lakes, rivers and ponds.The AMI Oxytrace is a Electronic transmitter/controller for the measurement of dissolved oxygen in high purity water.The AMI family of transmitters provides a common base for a number of analytical instruments with application specific sensor interfaces. Each instrument has a basic structure with identical functionality.AMI instruments can (optionally) be equipped with a PROFIBUS DP-V1 interface. The interface supports the PROFIBUS-PA Profile 3.0. This part of the manual describes the functionality of the interface and the integration of the AMI family of transmitters into an automation system.
Hardware Wiring, bus terminals and connectors are not part of this manual. It should, however, be noted that the observation of the corresponding standards is of paramount importance to proper operation. Setting the transmission rate to reasonable values will help avoid communication errors.
GSD File forAMI Oxytrace
The PROFIBUS system requires a description of the device parameters, e. g. output data, input data, data format, data volume and supported transmission rate, so that it can integrate the field devices into the bus system. These data are contained in a Device Master File (GSD file) which is placed at the disposal of the PROFIBUS master while communication system is being commissioned.
Device bitmaps can also be integrated. These appear as icons in the network tree.The manufacturer-specific GSD file SW17E1.gsd is available for download from http://www.swan.ch
12.2. Cyclic Data Telegram
Input Data The the AMI Oxytrace makes the following modules available as input data for the cyclic data exchange:
1 Main Process Value (ppb)
2 Main Temperature
3 Main Flow (l/h)
4 2nd Process Value %
5 Diagnostic Values (5 values)
– Raw Current Temperature Compensated in nA
– Raw Current in nA
– Air Pressure in hPa
– Remaining Electrolyte in %
– Case Temperature in °C
A-96.250.731 / 150513 79
ProfibusProduct Specific Data for Oxytrace
The input data is transferred from AMI Oxytrace in the following structure:
Output Data The AMI Oxysafe and the AMI Oxytrace make the following module available as output data for the cyclic data exchange:
1 Control AMI
The control data is transferred to the AMI Oxytrace in the following structure:
Tab. 12-1 Input data structure from AMI Oxytrace
Index input data Data Access
Data format / comments Configuration data
0–4 Analog Input block 1 Main Process Value
read Measured value (32-bit floating point number) Status byte
0x42, 0x84, 0x08, 0x05 or 0x42, 0x84, 0x81, 0x81 or 0x94
5–9 Analog Input block 2Main Temperature
read Measured value (32-bit floating point number) Status byte
0x42, 0x84, 0x08, 0x05 or 0x42, 0x84, 0x81, 0x81 or 0x94
10–14 Analog Input block 3Main Flow
read Measured value (32-bit floating point number) Status byte
0x42, 0x84, 0x08, 0x05 or 0x42, 0x84, 0x81, 0x81 or 0x94
15–19 Analog Input block 42nd Process Value
read Measured value (32-bit floating point number) Status byte
0x42, 0x84, 0x08, 0x05 or 0x42, 0x84, 0x81, 0x81 or 0x94
20–39 Diagnostic Values read 5 Measured values (32-bit floating point number)
0x45, 0x93, 0x08, 0x08, 0x08, 0x08, 0x08, 0xD9
Tab. 12-2 Output data structure:
Index output data Data Access Data format / comments Configuration data
0–1 Control AMI
(SP_D)
write Byte 0Bit 0: Relay 1
0 = open1 = close
0x82, 0x81, 0x05, 0x05 or 0x82, 0x81, 0x84, 0x82 or 0xA1
Bit 1: Relay 2 0 = open1 = close
Bit 2–7: not used
Byte 1Bit 0: Hold
Bit 1: Control Off
Bit 2–7: not used
80 A-96.250.731 / 150513
ProfibusProduct Specific Data for Oxytrace
12.2.1 Data Formats
For further information see chapter 1 Data Formats, p. 7
Tab. 12-3 Status Code Byte
7 6 5 4 3 2 1 0
Quality Sub-Status Limits Meaning
0 0 The sub-status has a different quality depending on the coding
bad
0 1 uncertain
1 0 good
0 0 ok
0 1 low limited
1 0 high limited
1 1 constant
Tab. 12-4 Status codes of the measured value
Status
code
Device status Meaning Limits
0x08 BAD Not connected (Temp Sensor not connected)
0x0C BAD device failure
0x10 BAD sensor failure (Temp Sensor Short Circuit)
0x47 UNCERTAIN Last usable value (HOLD) CONST
0x50 UNCERTAIN sensor conversion not accurate (e.g. No Flow) OK
0x64
0x67
UNCERTAIN Sensor calibration Sensor calibration, hold
OK CONST
0x80 GOOD ok OK
0x89
0x8A
GOOD Warning Low Warning High
LOW_LIM HIGH_LIM
0x8D
0x8E
GOOD Alarm Low Alarm High
LOW_LIM HICH_LIM
Tab. 12-5 DP Diagnostics
Byte Description
0 Status 1 Standard DP Diagnostics1 Status 2
2 Status 3
3 Master address
4 Ident number (high byte)
5 Ident number (low byte)
6 Header (block length incl. Header byte) = 14 Status coding accord-ing to DP/V17 Status Type (0x81)
8 Slot Number (0x00)
9 Status Specifier
10–13 Diagnosis
14–19 Diagnosis Extension
A-96.250.731 / 150513 81
ProfibusProduct Specific Data for Oxytrace
Tab. 12-6 The diagnosis object consists of 4 Bytes
Byte Bit Meaning when “1” Abbreviation
0 0 Hardware failure electronics DIA_HW_ELECTR
1 Hardware failure mechanics DIA_HW_MECH
2 -
3 Electronic temperature too high DIA_TEMP_ELECTR
4 -
5 Measurement failure DIA_MEASUREMENT
6 -
7 -
1 0 -
1 -
2 -
3 -
4 -
5 Maintenance required DIA_MAINTENANCE
6 -
7 -
2 0 -
1 -
2 -
3 -
4 -
5 -
6 -
7 -
3 0 -
1 -
2 -
3 -
4 -
5 -
6 -
7 Extension Available EXTENSION_AVAILABLE
82 A-96.250.731 / 150513
ProfibusProduct Specific Data for Oxytrace
Byte 6 is reserved for future extensions.
Tab. 12-7 The diagnosis extension object consists of 6 Bytes.
Byte Bit Meaning when “1” Abbreviation
0 0
1
2
3
4
5
6
7
1 0 Sample Flow high DIA_MEASUREMENT
1 Sample Flow low DIA_MEASUREMENT
Temp. shorted DIA_HW_ELECTR
3 Temp. disconnected DIA_HW_ELECTR
4 Case Temp. high DIA_TEMP_ELECTR
5 Case Temp. low DIA_TEMP_ELECTR
6
7
2 0 Control Timeout
1 Faraday Efficiency DIA_MAINTENANCE
2
3
4
5
6
7
3 0 IC MK41T56 DIA_HW_ELECTR
1 IC LM75 DIA_HW_ELECTR
2 IC PCF8574 DIA_HW_ELECTR
3 EEprom Microcon DIA_HW_ELECTR
4 EEProm Motherboard DIA_HW_ELECTR
5 I2C Rovalve DIA_HW_ELECTR
6 Cal. Recout DIA_HW_ELECTR
7 Wrong Frontend DIA_HW_ELECTR
4 0 Electrolyte depleted DIA_MAINTENANCE
1
2
3
4
5
6
7
A-96.250.731 / 150513 83
ProfibusProduct Specific Data for Oxytrace
12.3. Configuration
12.3.1 Device Master Files (GSD)
The device is ready for system integration once commissioning has been effected via the local display or the Class 2 master. The PROFIBUS system requires a description of the device parameters, e.g. output data, input data, data format, data volume and supported transmission rate, so that it can integrate the field devices into the bus system. These data are contained in a Device Master File (GSD file) which is placed at the disposal of the PROFIBUS master while the communication system is being commissioned. Device bitmaps can also be integrated. These appear as icons in the network tree. The Profile 3.0 Device Master File (GSD) allows field devices from various manufacturers to be exchanged without having to reconfigure.
12.3.2 GSD File Types
Prior to configuration, decide which GSD you want to use to operate the system. You can change the setting by means of a Class 2 master (under Physical Block-Parame-
ter Ident_Number_Selector)The following two Device Master Files with different functionalities are available: Manufacturer-specific GSD with Profile 3.0 functionality (default setting): This GSD guarantees the unlimited functionality of the field device. Device-specific pro-
cess parameters and functions are therefore available. Profile GSD's: If a system is configured with profile GSD's, it is possible to exchange devices that are
supplied by various manufacturers. It is, however, essential that the cyclic process values follow the same sequence. The transmitter supports the profiles Analyzer and Multivaria-ble (IEC 61158-2). These GSD's comprise Analog Input blocks (AI)
Working with GSD filesThe GSDs must be integrated into the automation system. Depending on the software that is being used, the GSD files can be copied to the program-specific directory or can be read into the database using the import function within the configuration software.
Tab. 12-8 GSD files for AMI Oxytrace:
Device name Ident_number_
Selector
ID number GSD Bitmaps
Manufacturer specific GSD with Profile 3.0 functionality:
AMI Oxytrace 1 17E1Hex SW17E1.gsd SW17E1_D.bmp
SW17E1_N.bmp SW17E1_S.bmp
Profile 3.0 GSD Analyzer:
AMI Oxytrace 0 9750 Hex PA139750.gsd PA_9750n.bmp
Profile 3.0 GSD Multivariable:
AMI Oxytrace 3 9760 Hex PA139760.gsd PA_9760n.bmp
84 A-96.250.731 / 150513
ProfibusProduct Specific Data for AMI Pharmacon
13. Product Specific Data for AMI Pharmacon
13.1. Introduction
The AMI family of transmitters provides a common base for a number of analytical instruments with application specific sensor interfaces. Each instrument has a basic structure with identical functionality.AMI instruments can (optionally) be equipped with a PROFIBUS DP-V1 interface. The interface supports the PROFIBUS-PA Profile 3.0. This part of the manual describes the functionality of the interface and the integration of the AMI family of transmitters into an automation system.
Hardware Wiring, bus terminals and connectors are not part of this manual. It should, however, be noted that the observation of the corresponding standards is of paramount importance to proper operation. Setting the transmission rate to reasonable values will help avoid communication errors.
GSD File forAMI Pharmacon
The PROFIBUS system requires a description of the device parameters, e. g. output data, input data, data format, data volume and supported transmission rate, so that it can integrate the field devices into the bus system. These data are contained in a Device Master File (GSD file) which is placed at the disposal of the PROFIBUS master while communication system is being commissioned.
Device bitmaps can also be integrated. These appear as icons in the network tree.The manufacturer-specific GSD file SW17D1.gsd is available for download from http://www.swan.ch
13.2. Cyclic Data Telegram
Input Data The AMI Pharmacon makes the following modules available as input data for the cyclic data exchange:
1 Main Process Value (µS/cm)
2 Main Temperature
3 Main Flow (l/h)
4 2nd Process Value (µS/cm)
5 Diagnostic Values (5 values)
– USP Value
– Cell Constant in cm -1
– Reserved (for internal use)
– Reserved (for internal use)
– Case Temperature in °C
A-96.250.731 / 140212 85
ProfibusProduct Specific Data for AMI Pharmacon
The input data is transferred from the AMI Pharmacon in the following structure:
Output Data The AMI Pharmacon makes the following module available as output data for the cyclic data exchange:
1 Control AMI
The control data is transferred to the AMI Pharmacon in the following structure:
Tab. 13-1 Input data structure from AMI Pharmacon
Index input data Data Access
Data format / comments Configuration data
0–4 Analog Input block 1 Main Process Value
read Measured value (32-bit floating point number) Status byte
0x42, 0x84, 0x08, 0x05 or 0x42, 0x84, 0x81, 0x81 or 0x94
5–9 Analog Input block 2Main Temperature
read Measured value (32-bit floating point number) Status byte
0x42, 0x84, 0x08, 0x05 or 0x42, 0x84, 0x81, 0x81 or 0x94
10–14 Analog Input block 3Main Flow
read Measured value (32-bit floating point number) Status byte
0x42, 0x84, 0x08, 0x05 or 0x42, 0x84, 0x81, 0x81 or 0x94
15–19 Analog Input block 42nd Process Value
read Measured value (32-bit floating point number) Status byte
0x42, 0x84, 0x08, 0x05 or 0x42, 0x84, 0x81, 0x81 or 0x94
20–39 Diagnostic Values read 5 Measured values (32-bit floating point number)
0x45, 0x93, 0x08, 0x08, 0x08, 0x08, 0x08 or0xD9
Tab. 13-2 Output data structure:
Index output data Data Access Data format / comments Configuration data
0–1 Control AMI
(SP_D)
write Byte 0Bit 0: Relay 1
0 = open1 = close
0x82, 0x81, 0x05, 0x05 or 0x82, 0x81, 0x84, 0x82 or 0xA1
Bit 1: Relay 2 0 = open1 = close
Bit 2–7: not used
Byte 1Bit 0: Hold
Bit 1: Control Off
Bit 2–7: not used
86 A-96.250.731 / 140212
ProfibusProduct Specific Data for AMI Pharmacon
13.2.1 Data Formats
For further information see chapter 1 Data Formats, p. 7
Tab. 13-3 Status Code Byte
7 6 5 4 3 2 1 0
Quality Sub-Status Limits Meaning
0 0 The sub-status has a different quality depending on the coding
bad
0 1 uncertain
1 0 good
0 0 ok
0 1 low limited
1 0 high limited
1 1 constant
Tab. 13-4 Status codes of the measured value
Status
code
Device status Meaning Limits
0x08 BAD Not connected (Temp Sensor not connected)
0x0C BAD device failure
0x10 BAD sensor failure (Temp Sensor Short Circuit)
0x47 UNCERTAIN Last usable value (HOLD) CONST
0x50 UNCERTAIN sensor conversion not accurate (e.g. No Flow) OK
0x64
0x67
UNCERTAIN Sensor calibration Sensor calibration, hold
OK CONST
0x80 GOOD ok OK
0x89
0x8A
GOOD Warning Low Warning High
LOW_LIM HIGH_LIM
0x8D
0x8E
GOOD Alarm Low Alarm High
LOW_LIM HICH_LIM
Tab. 13-5 DP Diagnostics
Byte Description
0 Status 1 Standard DP Diagnostics1 Status 2
2 Status 3
3 Master address
4 Ident number (high byte)
5 Ident number (low byte)
6 Header (block length incl. Header byte) = 14 Status coding accord-ing to DP/V17 Status Type (0x81)
8 Slot Number (0x00)
9 Status Specifier
10–13 Diagnosis
14–19 Diagnosis Extension
A-96.250.731 / 140212 87
ProfibusProduct Specific Data for AMI Pharmacon
Tab. 13-6 The diagnosis object consists of 4 Bytes
Byte Bit Meaning when “1” Abbreviation
0 0 Hardware failure electronics DIA_HW_ELECTR
1 Hardware failure mechanics DIA_HW_MECH
2 -
3 Electronic temperature too high DIA_TEMP_ELECTR
4 -
5 Measurement failure DIA_MEASUREMENT
6 -
7 -
1 0 -
1 -
2 -
3 -
4 -
5 Maintenance required DIA_MAINTENANCE
6 -
7 -
2 0 -
1 -
2 -
3 -
4 -
5 -
6 -
7 -
3 0 -
1 -
2 -
3 -
4 -
5 -
6 -
7 Extension Available EXTENSION_AVAILABLE
88 A-96.250.731 / 140212
ProfibusProduct Specific Data for AMI Pharmacon
Bytes 4 and 5 are reserved for future extensions.
Tab. 13-7 The diagnosis extension object consists of 6 Bytes.
Byte Bit Meaning when “1” Abbreviation
0 0 Cond. Alarm high
1 Cond Alarm low
2
3
4
5
6 Sample Temp. high DIA_MEASUREMENT
7 Sample Temp. low DIA_MEASUREMENT
1 0 Sample Flow high DIA_MEASUREMENT
1 Sample Flow low DIA_MEASUREMENT
Temp. shorted DIA_HW_ELECTR
3 Temp. disconnected DIA_HW_ELECTR
4 Case Temp. high DIA_TEMP_ELECTR
5 Case Temp. low DIA_TEMP_ELECTR
6 USP Error DIA_MEASUREMENT
7
2 0 Control Timeout
1 Quality Assurance DIA_MAINTENANCE
2
3
4
5
6
7 Input Active DIA_HW_ELECTR
3 0 IC MK41T56 DIA_HW_ELECTR
1 IC LM75 DIA_HW_ELECTR
2 IC PCF8574 DIA_HW_ELECTR
3 EEprom Microcon DIA_HW_ELECTR
4 EEProm Motherboard DIA_HW_ELECTR
5 EEProm Front-end DIA_HW_ELECTR
6 Cal. Recout DIA_HW_ELECTR
7 Wrong Front-end DIA_HW_ELECTR
A-96.250.731 / 140212 89
ProfibusProduct Specific Data for AMI Pharmacon
13.3. Configuration
13.3.1 Device Master Files (GSD)
The device is ready for system integration once commissioning has been effected via the local display or the Class 2 master. The PROFIBUS system requires a description of the device parameters, e.g. output data, input data, data format, data volume and supported transmission rate, so that it can integrate the field devices into the bus system. These data are contained in a Device Master File (GSD file) which is placed at the disposal of the PROFIBUS master while the communication system is being commissioned. Device bitmaps can also be integrated. These appear as icons in the network tree. The Profile 3.0 Device Master File (GSD) allows field devices from various manufacturers to be exchanged without having to reconfigure.
13.3.2 GSD File Types
Prior to configuration, decide which GSD you want to use to operate the system. You can change the setting by means of a Class 2 master (under Physical Block-Parame-
ter Ident_Number_Selector)The following two Device Master Files with different functionalities are available: Manufacturer-specific GSD with Profile 3.0 functionality (default setting): This GSD guarantees the unlimited functionality of the field device. Device-specific pro-
cess parameters and functions are therefore available. Profile GSD's: If a system is configured with profile GSD's, it is possible to exchange devices that are
supplied by various manufacturers. It is, however, essential that the cyclic process values follow the same sequence. The transmitter supports the profiles Analyzer and Multivaria-ble (IEC 61158-2). These GSD's comprise Analog Input blocks (AI)
Working with GSD filesThe GSDs must be integrated into the automation system. Depending on the software that is being used, the GSD files can be copied to the program-specific directory or can be read into the database using the import function within the configuration software.
Tab. 13-8 GSD files for AMI Pharmacon:
Device name Ident_number_
Selector
ID number GSD Bitmaps
Manufacturer specific GSD with Profile 3.0 functionality:
AMI Pharmacon 1 17D1Hex SW17D1.gsd SW17D1_D.bmp
SW17D1_N.bmp SW17D1_S.bmp
Profile 3.0 GSD Analyzer:
AMI Pharmacon 0 9750 Hex PA139750.gsd PA_9750n.bmp
Profile 3.0 GSD Multivariable:
AMI Pharmacon 3 9760 Hex PA139760.gsd PA_9760n.bmp
90 A-96.250.731 / 140212
ProfibusProduct Specific Data for AMI Phosphate HL
14. Product Specific Data for AMI Phosphate HL
14.1. Introduction
The AMI Phosphate HL is a complete monitoring system for the automatic, continuous measurement of ortho-phosphate in boiler water, district heating, cooling water and waste water.The AMI family of transmitters provides a common base for a number of analytical instruments with application specific sensor interfaces. Each instrument has a basic structure with identical functionality.AMI instruments can (optionally) be equipped with a PROFIBUS DP-V1 interface. The interface supports the PROFIBUS-PA Profile 3.0. This part of the manual describes the functionality of the interface and the integration of the AMI family of transmitters into an automation system.
Hardware Wiring, bus terminals and connectors are not part of this manual. It should, however, be noted that the observation of the corresponding standards is of paramount importance to proper operation. Setting the transmission rate to reasonable values will help avoid communication errors.
GSD File forAMI Phosphate HL
The PROFIBUS system requires a description of the device parameters, e. g. output data, input data, data format, data volume and supported transmission rate, so that it can integrate the field devices into the bus system. These data are contained in a Device Master File (GSD file) which is placed at the disposal of the PROFIBUS master while communication system is being commissioned.
Device bitmaps can also be integrated. These appear as icons in the network tree.The manufacturer-specific GSD file SW17D9.gsd is available for download from http://www.swan.ch
14.2. Cyclic Data Telegram
The AMI Phosphate HL makes following modules available as input data for the cyclic data exchange:
1 Phosphate Channels 1–6
2 Main Flow
3 Status AMI
4 Control AMI
5 Diagnostic Values (5 values) Absorbance current channel Absorbance continuous Photometer raw value in Hz State Case Temperature in °C
A-96.250.731 / 240915 91
ProfibusProduct Specific Data for AMI Phosphate HL
The input data is transferred from the AMI Phosphate HL in the following structure:
Tab. 14-1 Input data structure from AMI Phosphate HL
Index input data Data Access
Data format / comments Configuration data
0–4 Analog Input block 1 Phosphate Channel 1
read Measured value (32-bit floating point number) Status byte
0x42, 0x84, 0x08, 0x05 or 0x42, 0x84, 0x81, 0x81 or 0x94
25–29 Analog Input block 6 Phosphate Channel 6
read Measured value (32-bit floating point number) Status byte
0x42, 0x84, 0x08, 0x05 or 0x42, 0x84, 0x81, 0x81 or 0x94
30–34 Analog Input block 7Main Flow
read Measured value (32-bit floating point number) Status byte
0x42, 0x84, 0x08, 0x05 or 0x42, 0x84, 0x81, 0x81 or 0x94
35–36 Status AMI read 0x42, 0x81, 0x05, 0x05 or0x42, 0x81, 0x83, 0x81 or0x91
37–56 Diagnostic Values read 5 Measured values (32-bit floating point number)
0x45, 0x93, 0x08, 0x08, 0x08, 0x08, 0x08 or0xD9
Tab. 14-2 The Status AMI input data is transferred from AMI Phosphate HL in the following structure:
Index input data Data Access Data format / comments Configuration data
40–41 Status AMI (OUT_D)
write Byte 0Bit 0–3:Bit 4–7:
Channel ValveChannel Meas.
0x42, 0x81, 0x05, 0x05 or 0x42, 0x81, 0x83, 0x81 or 0x91
Byte 1
Bit 0–5: Sequencer Inputs Channel 1–6
Bit 6: reserved
Bit 7: No Flow
92 A-96.250.731 / 240915
ProfibusProduct Specific Data for AMI Phosphate HL
Output Data The AMI Phosphate HL makes the following module available as output data for the cyclic data exchange:
1 Control AMI
The control data is transferred to the AMI Phosphate HL in the following structure:
Tab. 14-3 Output data structure
Index output data Data Access Data format / comments Configuration data
0–1 Control
AMI
(SP_D)
write Byte 0Bit 0: Relay 1
0 = open1 = close
0x82, 0x81, 0x05, 0x05 or 0x82, 0x81, 0x84, 0x82 or 0xA1
Bit 1: Relay 2 0 = open1 = close
Bit 2–7: not used
Byte 1Bit 0–2: Channel 0, 1–6
Bit 3–5: Reserved
Bit 6: Control Off
Bit 7: Hold
* Channel = 0: Auto Select
A-96.250.731 / 240915 93
ProfibusProduct Specific Data for AMI Phosphate HL
14.2.1 Data Formats
For further information see chapter 1 Data Formats, p. 7
Tab. 14-4 Status Code Byte
7 6 5 4 3 2 1 0
Quality Sub-Status Limits Meaning
0 0 The sub-status has a different quality depending on the coding
bad
0 1 uncertain
1 0 good
0 0 ok
0 1 low limited
1 0 high limited
1 1 constant
Tab. 14-5 Status codes of the measured value
Status
code
Device status Meaning Limits
0x08 BAD Not connected (Sensor not connected)
0x0C BAD device failure
0x10 BAD sensor failure (Sensor Short Circuit)
0x47 UNCERTAIN Last usable value (HOLD) CONST
0x4F UNCERTAIN Initial value CONST
0x50 UNCERTAIN Sensor conversion not accurate (No Flow) OK
0x64
0x67
UNCERTAIN Sensor calibration Sensor calibration, hold
OK CONST
0x80 GOOD ok OK
0x89
0x8A
GOOD Warning Low Warning High
LOW_LIM HIGH_LIM
0x8D
0x8E
GOOD Alarm Low Alarm High
LOW_LIM HIGH_LIM
Tab. 14-6 DP Diagnostics
Byte Description
0 Status 1 Standard DP Diagnostics1 Status 2
2 Status 3
3 Master address
4 Ident number (high byte)
5 Ident number (low byte)
6 Header (block length incl. Header byte) = 14 Status coding accord-ing to DP/V17 Status Type (0x81)
8 Slot Number (0x00)
9 Status Specifier
10–13 Diagnosis
14–19 Diagnosis Extension
94 A-96.250.731 / 240915
ProfibusProduct Specific Data for AMI Phosphate HL
Tab. 14-7 The diagnosis object consists of 4 Bytes
Byte Bit Meaning when “1” Abbreviation
0 0 Hardware failure electronics DIA_HW_ELECTR
1 Hardware failure mechanics DIA_HW_MECH
2 -
3 Electronic temperature too high DIA_TEMP_ELECTR
4 -
5 Measurement failure DIA_MEASUREMENT
6 -
7 -
1 0 -
1 -
2 -
3 -
4 -
5 Maintenance required DIA_MAINTENANCE
6 -
7 -
2 0 -
1 -
2 -
3 -
4 -
5 -
6 -
7 -
3 0 -
1 -
2 -
3 -
4 -
5 -
6 -
7 Extension Available EXTENSION_AVAILABLE
A-96.250.731 / 240915 95
ProfibusProduct Specific Data for AMI Phosphate HL
Tab. 14-8 The diagnosis extension object consists of 6 Bytes.
Byte Bit Meaning when “1” Abbreviation0 0
1
2
3
4 Absorbance too high DIA_MEASUREMENT5
6
7
1 0 Sample Flow high DIA_MEASUREMENT1 Sample Flow low DIA_MEASUREMENT
3
4 Case Temp. high DIA_TEMP_ELECTR5 Case Temp. low DIA_TEMP_ELECTR6 Valve defective DIA_MAINTENANCE7
2 0 Control Timeout1 Reagent Pump DIA_MAINTENANCE2 Photometer not connected DIA_MAINTENANCE3 Photometer dirty DIA_MAINTENANCE4 Sequencer DIA_HW_ELECTR5 Reagent Empty DIA_MAINTENANCE6 Detergent DIA_MAINTENANCE7 Input Active DIA_HW_ELECTR
3 0 IC MK41T56 DIA_HW_ELECTR1 IC LM75 DIA_HW_ELECTR2 IC PCF8574 DIA_HW_ELECTR3 Signal output open DIA_HW_ELECTR4 EEProm Motherboard DIA_HW_ELECTR5 EEProm Front-end DIA_HW_ELECTR6 Cal. Recout DIA_HW_ELECTR7 Wrong Front-end DIA_HW_ELECTR
4 0 Sample Flow 1 low1 Sample Flow 2 low2 Sample Flow 3 low3 Sample Flow 4 low4 Sample Flow 5 low5 Sample Flow 6 low6
7
5 0 Reagent low DIA_MAINTENANCE1
2 Cleaning Solution DIA_MAINTENANCE3
4
5
6
96 A-96.250.731 / 240915
ProfibusProduct Specific Data for AMI Phosphate HL
14.3. Configuration
14.3.1 Device Master Files (GSD)
The device is ready for system integration once commissioning has been effected via the local display or the Class 2 master. The PROFIBUS system requires a description of the device parameters, e.g. output data, input data, data format, data volume and supported transmission rate, so that it can integrate the field devices into the bus system. These data are contained in a Device Master File (GSD file) which is placed at the disposal of the PROFIBUS master while the communication system is being commissioned. Device bitmaps can also be integrated. These appear as icons in the network tree. The Profile 3.0 Device Master File (GSD) allows field devices from various manufacturers to be exchanged without having to reconfigure.
14.3.2 GSD File Types
Prior to configuration, decide which GSD you want to use to operate the system. You can change the setting by means of a Class 2 master (under Physical Block-Parame-
ter Ident_Number_Selector)
The following two Device Master Files with different functionalities are available: Manufacturer-specific GSD with Profile 3.0 functionality (default setting):
This GSD guarantees the unlimited functionality of the field device. Device-specific pro-cess parameters and functions are therefore available.
Profile GSD's:If a system is configured with profile GSD's, it is possible to exchange devices that are supplied by various manufacturers. It is, however, essential that the cyclic process values follow the same sequence. The transmitter supports the profiles Analyzer and Multivaria-ble (IEC 61158-2). These GSD's comprise Analog Input blocks (AI)
Working with GSD filesThe GSDs must be integrated into the automation system. Depending on the software that is being used, the GSD files can be copied to the program-specific directory or can be read into the database using the import function within the configuration software.
Tab. 14-9 GSD files for AMI Phosphate HL:
Device name Ident_number_
Selector
ID number GSD Bitmaps
Manufacturer specific GSD with Profile 3.0 functionality:
AMI Phosphate HL 1 17D9Hex SW17D9.gsd SW17D9_D.bmp
SW17D9_N.bmp SW17D9_D.bmp
Profile 3.0 GSD Analyzer:
AMI Phosphate HL 0 9750 Hex PA139750.gsd PA_9750n.bmp
Profile 3.0 GSD Multivariable:
AMI Phosphate HL 3 9760 Hex PA139760.gsd PA_9760n.bmp
A-96.250.731 / 240915 97
ProfibusProduct Specific Data for AMI Phosphate HL
98 A-96.250.731 / 240915
ProfibusProduct Specific Data for AMI Phosphate II
15. Product Specific Data for AMI Phosphate II
15.1. Introduction
This description applies for the AMI Phosphate-II and the AMI Phosphate-II B.The AMI Phosphate-II is a complete monitoring system for the automatic, continuous measurement of phosphate in potable water, effluents and cooling water.The AMI Phosphate-II B is a complete monitoring system for the automatic, continuous measurement of ortho-phosphate in boiler water.The AMI family of transmitters provides a common base for a number of analytical instruments with application specific sensor interfaces. Each instrument has a basic structure with identical functionality.AMI instruments can (optionally) be equipped with a PROFIBUS DP-V1 interface. The interface supports the PROFIBUS-PA Profile 3.0. This part of the manual describes the functionality of the interface and the integration of the AMI family of transmitters into an automation system.
Hardware Wiring, bus terminals and connectors are not part of this manual. It should, however, be noted that the observation of the corresponding standards is of paramount importance to proper operation. Setting the transmission rate to reasonable values will help avoid communication errors.
GSD File forAMI Phosphate-II
The PROFIBUS system requires a description of the device parameters, e. g. output data, input data, data format, data volume and supported transmission rate, so that it can integrate the field devices into the bus system. These data are contained in a Device Master File (GSD file) which is placed at the disposal of the PROFIBUS master while communication system is being commissioned.
Device bitmaps can also be integrated. These appear as icons in the network tree.The manufacturer-specific GSD file SW17C9.gsd is available for download from http://www.swan.ch
15.2. Cyclic Data Telegram
The AMI Phosphate-II and the the AMI Phosphate-II B make following modules available as input data for the cyclic data exchange:
1 Phosphate Channels 1–6
2 Main Flow
3 Status AMI
4 Diagnostic Values (5 values) Absorbance current channel Absorbance continuous Fotometer raw value in Hz State Case Temperature in °C
A-96.250.731 / 150312 99
ProfibusProduct Specific Data for AMI Phosphate II
The input data is transferred from the AMI Phosphate-II and AMI Phosphate-II B in the following structure:
Tab. 15-1 Input data structure from AMI Phosphate-II and AMI Phosphate-II B
Index input data Data Access
Data format / comments Configuration data
0–4 Analog Input block 1 Phosphate Channel 1
read Measured value (32-bit floating point number) Status byte
0x42, 0x84, 0x08, 0x05 or 0x42, 0x84, 0x81, 0x81 or 0x94
25–29 Analog Input block 6 Phosphate Channel 6
read Measured value (32-bit floating point number) Status byte
0x42, 0x84, 0x08, 0x05 or 0x42, 0x84, 0x81, 0x81 or 0x94
30–34 Analog Input block 7Main Flow
read Measured value (32-bit floating point number) Status byte
0x42, 0x84, 0x08, 0x05 or 0x42, 0x84, 0x81, 0x81 or 0x94
35–36 Status AMI read 0x42, 0x81, 0x05, 0x05 or0x42, 0x81, 0x83, 0x81 or0x91
30–56 Diagnostic Values read 5 Measured values (32-bit floating point number)
0x45, 0x93, 0x08, 0x08, 0x08, 0x08, 0x08 or0xD9
Tab. 15-2 The Status AMI input data is transferred from AMI Phosphate-II and AMI Phosphate-II B in the following structure:
Index input data Data Access Data format / comments Configuration data
40–41 Control AMI (OUT_D)
write Byte 0Bit 0–3:Bit 4–7:
Channel ValveChannel Meas
0x42, 0x81, 0x05, 0x05 or 0x42, 0x81, 0x84, 0x82 or 0x91
Byte 1
Bit 0–5: Sequencer Inputs Channel 1–6
Bit 6: reserved
Bit 7: No Flow
100 A-96.250.731 / 150312
ProfibusProduct Specific Data for AMI Phosphate II
Output Data The AMI Phosphate-II and the AMI Phosphate-II B make the following module available as output data for the cyclic data exchange:
1 Control AMI
The control data is transferred to the AMI Phosphate-II and AMI Phosphate-II B in the following structure:
Tab. 15-3 Output data structure
Index output data Data Access Data format / comments Configuration data
0–1 Control
AMI
(SP_D)
write Byte 0Bit 0: Relay 1
0 = open1 = close
0x82, 0x81, 0x05, 0x05 or 0x82, 0x81, 0x84, 0x82 or 0xA1
Bit 1: Relay 2 0 = open1 = close
Bit 2–7: not used
Byte 1Bit 0–2: Channel 0, 1–6
Bit 3–5: Reserved
Bit 6: Control Off
Bit 7: Hold
* Channel = 0: Auto Select
A-96.250.731 / 150312 101
ProfibusProduct Specific Data for AMI Phosphate II
15.2.1 Data Formats
For further information see chapter 1 Data Formats, p. 7
Tab. 15-4 Status Code Byte
7 6 5 4 3 2 1 0
Quality Sub-Status Limits Meaning
0 0 The sub-status has a different quality depending on the coding
bad
0 1 uncertain
1 0 good
0 0 ok
0 1 low limited
1 0 high limited
1 1 constant
Tab. 15-5 Status codes of the measured value
Status
code
Device status Meaning Limits
0x08 BAD Not connected (Sensor not connected)
0x0C BAD device failure
0x10 BAD sensor failure (Sensor Short Circuit)
0x47 UNCERTAIN Last usable value (HOLD) CONST
0x4F UNCERTAIN Initial value CONST
0x50 UNCERTAIN Sensor conversion not accurate (No Flow) OK
0x64
0x67
UNCERTAIN Sensor calibration Sensor calibration, hold
OK CONST
0x80 GOOD ok OK
0x89
0x8A
GOOD Warning Low Warning High
LOW_LIM HIGH_LIM
0x8D
0x8E
GOOD Alarm Low Alarm High
LOW_LIM HICH_LIM
Tab. 15-6 DP Diagnostics
Byte Description
0 Status 1 Standard DP Diagnostics1 Status 2
2 Status 3
3 Master address
4 Ident number (high byte)
5 Ident number (low byte)
6 Header (block length incl. Header byte) = 14 Status coding accord-ing to DP/V17 Status Type (0x81)
8 Slot Number (0x00)
9 Status Specifier
10–13 Diagnosis
14–19 Diagnosis Extension
102 A-96.250.731 / 150312
ProfibusProduct Specific Data for AMI Phosphate II
Tab. 15-7 The diagnosis object consists of 4 Bytes
Byte Bit Meaning when “1” Abbreviation
0 0 Hardware failure electronics DIA_HW_ELECTR
1 Hardware failure mechanics DIA_HW_MECH
2 -
3 Electronic temperature too high DIA_TEMP_ELECTR
4 -
5 Measurement failure DIA_MEASUREMENT
6 -
7 -
1 0 -
1 -
2 -
3 -
4 -
5 Maintenance required DIA_MAINTENANCE
6 -
7 -
2 0 -
1 -
2 -
3 -
4 -
5 -
6 -
7 -
3 0 -
1 -
2 -
3 -
4 -
5 -
6 -
7 Extension Available EXTENSION_AVAILABLE
A-96.250.731 / 150312 103
ProfibusProduct Specific Data for AMI Phosphate II
Tab. 15-8 The diagnosis extension object consists of 6 Bytes.
Byte Bit Meaning when “1” Abbreviation0 0
1
2
3
4 Absorbance too high DIA_MEASUREMENT5
6
7
1 0 Sample Flow high DIA_MEASUREMENT1 Sample Flow low DIA_MEASUREMENT
3
4 Case Temp. high DIA_TEMP_ELECTR5 Case Temp. low DIA_TEMP_ELECTR6 Valve defective DIA_MAINTENANCE7
2 0 Control Timeout1 Reagent Pump DIA_MAINTENANCE2 Photometer not connected DIA_MAINTENANCE3 Photometer dirty DIA_MAINTENANCE4 Sequencer DIA_HW_ELECTR5 Reagent Empty6 Detergent DIA_MAINTENANCE7 Input Active DIA_HW_ELECTR
3 0 IC MK41T56 DIA_HW_ELECTR1 IC LM75 DIA_HW_ELECTR2 IC PCF8574 DIA_HW_ELECTR3 EEprom Microcon DIA_HW_ELECTR4 EEProm Motherboard DIA_HW_ELECTR5 EEProm Front-end DIA_HW_ELECTR6 Cal. Recout DIA_HW_ELECTR7 Wrong Front-end DIA_HW_ELECTR
4 0 Sample Flow 1 low1 Sample Flow 2 low2 Sample Flow 3 low3 Sample Flow 4 low4 Sample Flow 5 low5 Sample Flow 6 low6
7
5 0 Reagent low DIA_MAINTENANCE1
2
3
4
5
6
104 A-96.250.731 / 150312
ProfibusProduct Specific Data for AMI Phosphate II
15.3. Configuration
15.3.1 Device Master Files (GSD)
The device is ready for system integration once commissioning has been effected via the local display or the Class 2 master. The PROFIBUS system requires a description of the device parameters, e.g. output data, input data, data format, data volume and supported transmission rate, so that it can integrate the field devices into the bus system. These data are contained in a Device Master File (GSD file) which is placed at the disposal of the PROFIBUS master while the communication system is being commissioned. Device bitmaps can also be integrated. These appear as icons in the network tree. The Profile 3.0 Device Master File (GSD) allows field devices from various manufacturers to be exchanged without having to reconfigure.
15.3.2 GSD File Types
Prior to configuration, decide which GSD you want to use to operate the system. You can change the setting by means of a Class 2 master (under Physical Block-Parame-
ter Ident_Number_Selector)The following two Device Master Files with different functionalities are available: Manufacturer-specific GSD with Profile 3.0 functionality (default setting): This GSD guarantees the unlimited functionality of the field device. Device-specific pro-
cess parameters and functions are therefore available. Profile GSD's: If a system is configured with profile GSD's, it is possible to exchange devices that are
supplied by various manufacturers. It is, however, essential that the cyclic process values follow the same sequence. The transmitter supports the profiles Analyzer and Multivaria-ble (IEC 61158-2). These GSD's comprise Analog Input blocks (AI)
Working with GSD filesThe GSDs must be integrated into the automation system. Depending on the software that is being used, the GSD files can be copied to the program-specific directory or can be read into the database using the import function within the configuration software.
Tab. 15-9 GSD files for AMI Phosphate-II:
Device name Ident_number_
Selector
ID number GSD Bitmaps
Manufacturer specific GSD with Profile 3.0 functionality:
AMI Phosphate-II 1 17C9Hex SW17C9.gsd SW17C9_D.bmp
SW17C9_N.bmp SW17C9_S.bmp
Profile 3.0 GSD Analyzer:
AMI Phosphate-II 0 9750 Hex PA139750.gsd PA_9750n.bmp
Profile 3.0 GSD Multivariable:
AMI Phosphate-II 3 9760 Hex PA139760.gsd PA_9760n.bmp
A-96.250.731 / 150312 105
ProfibusProduct Specific Data for AMI Phosphate II
106 A-96.250.731 / 150312
ProfibusProduct Specific Data for AMI pH-Redox
16. Product Specific Data for AMI pH-Redox
16.1. Introduction
The AMI family of transmitters provides a common base for a number of analytical instruments with application specific sensor interfaces. Each instrument has a basic structure with identical functionality.AMI instruments can (optionally) be equipped with a PROFIBUS DP-V1 interface. The interface supports the PROFIBUS-PA Profile 3.0. This part of the manual describes the functionality of the interface and the integration of the AMI family of transmitters into an automation system.
Hardware Wiring, bus terminals and connectors are not part of this manual. It should, however, be noted that the observation of the corresponding standards is of paramount importance to proper operation. Setting the transmission rate to reasonable values will help avoid communication errors.
GSD File forAMI pH-Redox
The PROFIBUS system requires a description of the device parameters, e. g. output data, input data, data format, data volume and supported transmission rate, so that it can integrate the field devices into the bus system. These data are contained in a Device Master File (GSD file) which is placed at the disposal of the PROFIBUS master while communication system is being commissioned.
Device bitmaps can also be integrated. These appear as icons in the network tree.The manufacturer-specific GSD file SW17E0.gsd is available for download from http://www.swan.ch
16.2. Cyclic Data Telegram
Input Data The AMI pH-Redox makes the following modules available as input data for the cyclic data exchange:
1 Main Process Value (pH or Redox)
2 Main Temperature
3 Main Flow (l/h)
4 Diagnostic Values (5 values)
– Raw Value in mV
– Offset
– Slope
– Sensor Impedance
– Case Temperature in °C
A-96.250.731 / 041115 107
ProfibusProduct Specific Data for AMI pH-Redox
The input data is transferred from the AMI pH-Redox in the following structure:
Output Data The AMI pH-Redox makes the following module available as output data for the cyclic data exchange:
1 Control AMI
The control data is transferred to the AMI pH-Redox in the following structure:
Tab. 16-1 Input data structure from AMI pH-Redox
Index input data Data Access
Data format / comments Configuration data
0–4 Analog Input block 1 Main Process Value
read Measured value (32-bit floating point number) Status byte
0x42, 0x84, 0x08, 0x05 or 0x42, 0x84, 0x81, 0x81 or 0x94
5–9 Analog Input block 2Main Temperature
read Measured value (32-bit floating point number) Status byte
0x42, 0x84, 0x08, 0x05 or 0x42, 0x84, 0x81, 0x81 or 0x94
10–14 Analog Input block 3Main Flow
read Measured value (32-bit floating point number) Status byte
0x42, 0x84, 0x08, 0x05 or 0x42, 0x84, 0x81, 0x81 or 0x94
15–34 Diagnostic Values read 5 Measured values (32-bit floating point number)
0x45, 0x93, 0x08, 0x08, 0x08, 0x08, 0x08 or0xD9
Tab. 16-2 Output data structure
Index output data Data Access Data format / comments Configuration data
0–1 Control AMI
(SP_D)
write Byte 0Bit 0: Relay 1
0 = open1 = close
0x82, 0x81, 0x05, 0x05 or 0x82, 0x81, 0x84, 0x82 or 0xA1
Bit 1: Relay 2 0 = open1 = close
Bit 2–7: not used
Byte 1Bit 0: Hold
Bit 1: Control Off
Bit 2: Start pH Sensor check
To start a Sensor check, set this bit to "1" for 5 sec-onds, the reset to "0"
Bit 3–7: not used
108 A-96.250.731 / 041115
ProfibusProduct Specific Data for AMI pH-Redox
16.2.1 Data Formats
For further information see chapter 1 Data Formats, p. 7
Tab. 16-3 Status Code Byte
7 6 5 4 3 2 1 0
Quality Sub-Status Limits Meaning
0 0 The sub-status has a different quality depending on the coding
bad
0 1 uncertain
1 0 good
0 0 ok
0 1 low limited
1 0 high limited
1 1 constant
Tab. 16-4 Status codes of the measured value
Status
code
Device status Meaning Limits
0x08 BAD Not connected (Temp Sensor not connected)
0x0C BAD device failure
0x10 BAD sensor failure (Temp Sensor Short Circuit)
0x40 UNCERTAIN e.g. because of Temp Sensor Error CONST
0x47 UNCERTAIN Last usable value (HOLD) CONST
0x50 UNCERTAIN sensor conversion not accurate (e.g. No Flow) OK
0x64
0x67
UNCERTAIN Sensor calibration Sensor calibration, hold
OK CONST
0x80 GOOD ok OK
0x89
0x8A
GOOD Warning Low Warning High
LOW_LIM HIGH_LIM
0x8D
0x8E
GOOD Alarm Low Alarm High
LOW_LIM HICH_LIM
Tab. 16-5 DP Diagnostics
Byte Description
0 Status 1 Standard DP Diagnostics1 Status 2
2 Status 3
3 Master address
4 Ident number (high byte)
5 Ident number (low byte)
6 Header (block length incl. Header byte) = 14 Status coding accord-ing to DP/V17 Status Type (0x81)
8 Slot Number (0x00)
9 Status Specifier
10–13 Diagnosis
14–19 Diagnosis Extension
A-96.250.731 / 041115 109
ProfibusProduct Specific Data for AMI pH-Redox
Tab. 16-6 The diagnosis object consists of 4 Bytes
Byte Bit Meaning when “1” Abbreviation
0 0 Hardware failure electronics DIA_HW_ELECTR
1 Hardware failure mechanics DIA_HW_MECH
2 -
3 Electronic temperature too high DIA_TEMP_ELECTR
4 -
5 Measurement failure DIA_MEASUREMENT
6 -
7 -
1 0 -
1 -
2 -
3 -
4 -
5 Maintenance required DIA_MAINTENANCE
6 -
7 -
2 0 -
1 -
2 -
3 -
4 -
5 -
6 -
7 -
3 0 -
1 -
2 -
3 -
4 -
5 -
6 -
7 Extension Available EXTENSION_AVAILABLE
110 A-96.250.731 / 041115
ProfibusProduct Specific Data for AMI pH-Redox
Bytes 4 and 5 are reserved for future extensions.
Tab. 16-7 The diagnosis extension object consists of 6 Bytes.
Byte Bit Meaning when “1” Abbreviation
0 0 Alarm high
1 Alarm low
2
3
4
5
6 Sample Temp. high DIA_MEASUREMENT
7 Sample Temp. low DIA_MEASUREMENT
1 0 Sample Flow high DIA_MEASUREMENT
1 Sample Flow low DIA_MEASUREMENT
Temp. shorted DIA_HW_ELECTR
3 Temp. disconnected DIA_HW_ELECTR
4 Case Temp. high DIA_TEMP_ELECTR
5 Case Temp. low DIA_TEMP_ELECTR
6
7
2 0 Control Timeout
1
2
3
4
5
6
7 Input Active DIA_HW_ELECTR
3 0 IC MK41T56 DIA_HW_ELECTR
1 IC LM75 DIA_HW_ELECTR
2 IC PCF8574 DIA_HW_ELECTR
3 EEprom Microcon DIA_HW_ELECTR
4 EEProm Motherboard DIA_HW_ELECTR
5 EEProm front-end DIA_HW_ELECTR
6 Cal. Recout DIA_HW_ELECTR
7 Wrong Front-end DIA_HW_ELECTR
A-96.250.731 / 041115 111
ProfibusProduct Specific Data for AMI pH-Redox
16.3. Configuration
16.3.1 Device Master Files (GSD)
The device is ready for system integration once commissioning has been effected via the local display or the Class 2 master. The PROFIBUS system requires a description of the device parameters, e.g. output data, input data, data format, data volume and supported transmission rate, so that it can integrate the field devices into the bus system. These data are contained in a Device Master File (GSD file) which is placed at the disposal of the PROFIBUS master while the communication system is being commissioned. Device bitmaps can also be integrated. These appear as icons in the network tree. The Profile 3.0 Device Master File (GSD) allows field devices from various manufacturers to be exchanged without having to reconfigure.
16.3.2 GSD File Types
Prior to configuration, decide which GSD you want to use to operate the system. You can change the setting by means of a Class 2 master (under Physical Block-Parame-
ter Ident_Number_Selector)The following two Device Master Files with different functionalities are available: Manufacturer-specific GSD with Profile 3.0 functionality (default setting): This GSD guarantees the unlimited functionality of the field device. Device-specific pro-
cess parameters and functions are therefore available. Profile GSD's: If a system is configured with profile GSD's, it is possible to exchange devices that are
supplied by various manufacturers. It is, however, essential that the cyclic process values follow the same sequence. The transmitter supports the profiles Analyzer and Multivaria-ble (IEC 61158-2). These GSD's comprise Analog Input blocks (AI)
Working with GSD filesThe GSDs must be integrated into the automation system. Depending on the software that is being used, the GSD files can be copied to the program-specific directory or can be read into the database using the import function within the configuration software.
Tab. 16-8 GSD files for AMI pH-Redox:
Device name Ident_number_
Selector
ID number GSD Bitmaps
Manufacturer specific GSD with Profile 3.0 functionality:
AMI pH-Redox 1 17E0Hex SW17E0.gsd SW17E0_D.bmp
SW17E0_N.bmp SW17E0_S.bmp
Profile 3.0 GSD Analyzer:
AMI pH-Redox 0 9750 Hex PA139750.gsd PA_9750n.bmp
Profile 3.0 GSD Multivariable:
AMI pH-Redox 3 9760 Hex PA139760.gsd PA_9760n.bmp
112 A-96.250.731 / 041115
ProfibusProduct Specific Data for AMI pH/mV:pH/mV
17. Product Specific Data for AMI pH/mV:pH/mV
17.1. Introduction
This description applies for the AMI pH/mV:pH/mV and the AMI pH/mV:pH/mV PoolThe AMI pH/mV:pH/mV is a complete monitoring system for continuous measurement of pH and redox (ORP) in potable water and effluents. The AMI pH/mV:pH/mV Pool is a complete monitoring system for continuous measurement of pH and redox (ORP) potential in pool water.The AMI family of transmitters provides a common base for a number of analytical instruments with application specific sensor interfaces. Each instrument has a basic structure with identical functionality.AMI instruments can (optionally) be equipped with a PROFIBUS DP-V1 interface. The interface supports the PROFIBUS-PA Profile 3.0. This part of the manual describes the functionality of the interface and the integration of the AMI family of transmitters into an automation system.
Hardware Wiring, bus terminals and connectors are not part of this manual. It should, however, be noted that the observation of the corresponding standards is of paramount importance to proper operation. Setting the transmission rate to reasonable values will help avoid communication errors.
GSD File forAMI pH/mV:pH/mV
The PROFIBUS system requires a description of the device parameters, e. g. output data, input data, data format, data volume and supported transmission rate, so that it can integrate the field devices into the bus system. These data are contained in a Device Master File (GSD file) which is placed at the disposal of the PROFIBUS master while communication system is being commissioned.
Device bitmaps can also be integrated. These appear as icons in the network tree.The manufacturer-specific GSD file SW17E3.gsd is available for download from http://www.swan.ch
17.2. Cyclic Data Telegram
Input Data The AMI pH/mV:pH/mV and the AMI pH/mV:pH/mV Pool make the following modules available as input data for the cyclic data exchange:
1 Main Process Value 1 (pH or Redox)
2 Main Process Value 1 (pH or Redox)
3 Main Temperature 1
4 Main Temperature 2
5 Main Flow (l/h)
6 Difference (pH)
7 Diagnostic Values (5 values)
– Raw Value 1 in mV
– Raw Value 2 in mV
– Raw Temp 1 in Ohm
– Raw Temp 2 in Ohm
– Case Temperature in °C
A-96.250.731 / 150312 113
ProfibusProduct Specific Data for AMI pH/mV:pH/mV
The input data is transferred from the AMI pH/mV:pH/mV and the AMI pH/mV:pH/mV Pool in the following structure:
Output Data The AMI pH/mV:pH/mV and the AMI pH/mV:pH/mV Pool make the following module available as output data for the cyclic data exchange:
1 Control AMI
The control data is transferred to the AMI pH/mV:pH/mV and the AMI pH/mV:pH/mV Pool in the following structure:
Tab. 17-1 Input data structure from AMI pH/mV:pH/mV and AMI pH/mV:pH/mV Pool
Index input data Data Access
Data format / comments Configuration data
0–4 Analog Input block 1 Main Process Value 1
read Measured value (32-bit floating point number) Status byte
0x42, 0x84, 0x08, 0x05 or 0x42, 0x84, 0x81, 0x81 or 0x94
5–9 Analog Input block 1 Main Process Value 1
read Measured value (32-bit floating point number) Status byte
0x42, 0x84, 0x08, 0x05 or 0x42, 0x84, 0x81, 0x81 or 0x94
10–14 Analog Input block 2Main Temperature 1
read Measured value (32-bit floating point number) Status byte
0x42, 0x84, 0x08, 0x05 or 0x42, 0x84, 0x81, 0x81 or 0x94
15–19 Analog Input block 2Main Temperature 1
read Measured value (32-bit floating point number) Status byte
0x42, 0x84, 0x08, 0x05 or 0x42, 0x84, 0x81, 0x81 or 0x94
20–24 Analog Input block 5Main Flow
read Measured value (32-bit floating point number) Status byte
0x42, 0x84, 0x08, 0x05 or 0x42, 0x84, 0x81, 0x81 or 0x94
25–29 Analog Input block 6Difference
read Measured value (32-bit floating point number) Status byte
0x42, 0x84, 0x08, 0x05 or 0x42, 0x84, 0x81, 0x81 or 0x94
30–49 Diagnostic Values read 5 Measured values (32-bit floating point number)
0x45, 0x93, 0x08, 0x08, 0x08, 0x08, 0x08 or0xD9
Tab. 17-2 Output data structure
Index output data Data Access Data format / comments Configuration data
0–1 Control AMI
(SP_D)
write Byte 0Bit 0: Relay 1
0 = open1 = close
0x82, 0x81, 0x05, 0x05 or 0x82, 0x81, 0x84, 0x82 or 0xA1
Bit 1: Relay 2 0 = open1 = close
Bit 2–7: not used
Byte 1Bit 0: Hold
Bit 1: Control Off
Bit 2–7: not used
114 A-96.250.731 / 150312
ProfibusProduct Specific Data for AMI pH/mV:pH/mV
17.2.1 Data Formats
For further information see chapter 1 Data Formats, p. 7
Tab. 17-3 Status Code Byte
7 6 5 4 3 2 1 0
Quality Sub-Status Limits Meaning
0 0 The sub-status has a different quality depending on the coding
bad
0 1 uncertain
1 0 good
0 0 ok
0 1 low limited
1 0 high limited
1 1 constant
Tab. 17-4 Status codes of the measured value
Status
code
Device status Meaning Limits
0x08 BAD Not connected (Temp Sensor not connected)
0x0C BAD device failure
0x10 BAD sensor failure (Temp Sensor Short Circuit)
0x47 UNCERTAIN Last usable value (HOLD) CONST
0x50 UNCERTAIN sensor conversion not accurate (e.g. No Flow) OK
0x64
0x67
UNCERTAIN Sensor calibration Sensor calibration, hold
OK CONST
0x80 GOOD ok OK
0x89
0x8A
GOOD Warning Low Warning High
LOW_LIM HIGH_LIM
0x8D
0x8E
GOOD Alarm Low Alarm High
LOW_LIM HICH_LIM
Tab. 17-5 DP Diagnostics
Byte Description
0 Status 1 Standard DP Diagnostics1 Status 2
2 Status 3
3 Master address
4 Ident number (high byte)
5 Ident number (low byte)
6 Header (block length incl. Header byte) = 14 Status coding accord-ing to DP/V17 Status Type (0x81)
8 Slot Number (0x00)
9 Status Specifier
10–13 Diagnosis
14–19 Diagnosis Extension
A-96.250.731 / 150312 115
ProfibusProduct Specific Data for AMI pH/mV:pH/mV
Tab. 17-6 The diagnosis object consists of 4 Bytes
Byte Bit Meaning when “1” Abbreviation
0 0 Hardware failure electronics DIA_HW_ELECTR
1 Hardware failure mechanics DIA_HW_MECH
2 -
3 Electronic temperature too high DIA_TEMP_ELECTR
4 -
5 Measurement failure DIA_MEASUREMENT
6 -
7 -
1 0 -
1 -
2 -
3 -
4 -
5 Maintenance required DIA_MAINTENANCE
6 -
7 -
2 0 -
1 -
2 -
3 -
4 -
5 -
6 -
7 -
3 0 -
1 -
2 -
3 -
4 -
5 -
6 -
7 Extension Available EXTENSION_AVAILABLE
116 A-96.250.731 / 150312
ProfibusProduct Specific Data for AMI pH/mV:pH/mV
Bytes 4 and 5 are reserved for future extensions.
Tab. 17-7 The diagnosis extension object consists of 6 Bytes.
Byte Bit Meaning when “1” Abbreviation
0 0
1
2
3
4
5
6
7
1 0 Sample Flow high DIA_MEASUREMENT
1 Sample Flow low DIA_MEASUREMENT
Temp. shorted DIA_HW_ELECTR
3 Temp. disconnected DIA_HW_ELECTR
4 Case Temp. high DIA_TEMP_ELECTR
5 Case Temp. low DIA_TEMP_ELECTR
6
7
2 0 Control Timeout
1
2 Temp. 2 shorted DIA_HW_ELECTR
3 Temp. 2 disconnected DIA_HW_ELECTR
4
5
6
7 Input Active DIA_HW_ELECTR
3 0 IC MK41T56 DIA_HW_ELECTR
1 IC LM75 DIA_HW_ELECTR
2 IC PCF8574 DIA_HW_ELECTR
3 EEprom Microcon DIA_HW_ELECTR
4 EEProm Motherboard DIA_HW_ELECTR
5 EEProm front-end DIA_HW_ELECTR
6 Cal. Recout DIA_HW_ELECTR
7 Wrong Front-end DIA_HW_ELECTR
A-96.250.731 / 150312 117
ProfibusProduct Specific Data for AMI pH/mV:pH/mV
17.3. Configuration
17.3.1 Device Master Files (GSD)
The device is ready for system integration once commissioning has been effected via the local display or the Class 2 master. The PROFIBUS system requires a description of the device parameters, e.g. output data, input data, data format, data volume and supported transmission rate, so that it can integrate the field devices into the bus system. These data are contained in a Device Master File (GSD file) which is placed at the disposal of the PROFIBUS master while the communication system is being commissioned. Device bitmaps can also be integrated. These appear as icons in the network tree. The Profile 3.0 Device Master File (GSD) allows field devices from various manufacturers to be exchanged without having to reconfigure.
17.3.2 GSD File Types
Prior to configuration, decide which GSD you want to use to operate the system. You can change the setting by means of a Class 2 master (under Physical Block-Parame-
ter Ident_Number_Selector)The following two Device Master Files with different functionalities are available: Manufacturer-specific GSD with Profile 3.0 functionality (default setting): This GSD guarantees the unlimited functionality of the field device. Device-specific pro-
cess parameters and functions are therefore available. Profile GSD's: If a system is configured with profile GSD's, it is possible to exchange devices that are
supplied by various manufacturers. It is, however, essential that the cyclic process values follow the same sequence. The transmitter supports the profiles Analyzer and Multivaria-ble (IEC 61158-2). These GSD's comprise Analog Input blocks (AI)
Working with GSD filesThe GSDs must be integrated into the automation system. Depending on the software that is being used, the GSD files can be copied to the program-specific directory or can be read into the database using the import function within the configuration software.
Tab. 17-8 GSD files for AMI pH/mV:pH/mV:
Device name Ident_number_
Selector
ID number GSD Bitmaps
Manufacturer specific GSD with Profile 3.0 functionality:
AMI pH/mV:pH/mV 1 17E0Hex SW17E3.gsd SW17E3_D.bmp
SW17E3_N.bmp SW17E3_S.bmp
Profile 3.0 GSD Analyzer:
AMI pH/mV:pH/mV 0 9750 Hex PA139750.gsd PA_9750n.bmp
Profile 3.0 GSD Multivariable:
AMI pH/mV:pH/mV 3 9760 Hex PA139760.gsd PA_9760n.bmp
118 A-96.250.731 / 150312
ProfibusProduct Specific Data for AMI Powercon
18. Product Specific Data for AMI Powercon
18.1. Introduction
The AMI family of transmitters provides a common base for a number of analytical instruments with application specific sensor interfaces. Each instrument has a basic structure with identical functionality.AMI instruments can (optionally) be equipped with a PROFIBUS DP-V1 interface. The interface supports the PROFIBUS-PA Profile 3.0. This part of the manual describes the functionality of the interface and the integration of the AMI family of transmitters into an automation system.
Hardware Wiring, bus terminals and connectors are not part of this manual. It should, however, be noted that the observation of the corresponding standards is of paramount importance to proper operation. Setting the transmission rate to reasonable values will help avoid communication errors.
GSD File forAMI Powercon
The PROFIBUS system requires a description of the device parameters, e. g. output data, input data, data format, data volume and supported transmission rate, so that it can integrate the field devices into the bus system. These data are contained in a Device Master File (GSD file) which is placed at the disposal of the PROFIBUS master while communication system is being commissioned.
Device bitmaps can also be integrated. These appear as icons in the network tree.The manufacturer-specific GSD file SW17D0.gsd is available for download from http://www.swan.ch
18.2. Cyclic Data Telegram
Input Data The AMI Powercon makes the following modules available as input data for the cyclic data exchange:
1 Main Process Value (µS/cm)
2 Main Temperature
3 Main Flow (l/h)
4 2nd Process Value (µS/cm)
5 Diagnostic Values (5 Values)
– Contamination
– Cell Constant in cm-1
– Reserved (for internal use)
– Reserved (for internal use)
– Case Temperature in °C
A-96.250.731 / 041115 119
ProfibusProduct Specific Data for AMI Powercon
The input data is transferred from AMI Powercon in the following structure:
Output Data The AMI Powercon makes the following module available as output data for the cyclic data exchange:
1 Control AMI
The control data is transferred to the AMI Powercon in the following structure:
Tab. 18-1 Input data structure from AMI Powercon
Index input data Data Access
Data format / comments Configuration data
0–4 Analog Input block 1 Main Process Value
read Measured value (32-bit floating point number) Status byte
0x42, 0x84, 0x08, 0x05 or 0x42, 0x84, 0x81, 0x81 or 0x94
5–9 Analog Input block 2 Main Temperature
read Measured value (32-bit floating point number) Status byte
0x42, 0x84, 0x08, 0x05 or 0x42, 0x84, 0x81, 0x81 or 0x94
10–14 Analog Input block 3 Main Flow
read Measured value (32-bit floating point number) Status byte
0x42, 0x84, 0x08, 0x05 or 0x42, 0x84, 0x81, 0x81 or 0x94
15–19 Analog Input block 4 2nd Process Value
read Measured value (32-bit floating point number) Status byte
0x42, 0x84, 0x08, 0x05 or 0x42, 0x84, 0x81, 0x81 or 0x94
20–39 Diagnostic Values read 5 Measured values (32-bit floating point number)
0x45, 0x93, 0x08, 0x08, 0x08, 0x08, 0x080xD9
Tab. 18-2 Output data structure
Index output data Data Access Data format / comments Configuration data
0–1 Control AMI
(SP_D)
write Byte 0Bit 0: Relay 1
0 = open1 = close
0x82, 0x81, 0x05, 0x05 or 0x82, 0x81, 0x84, 0x82 or 0xA1
Bit 1: Relay 2 0 = open1 = close
Bit 2: not used
Bit 3: not used
Bit 4–7: not used
Byte 1Bit 0: Hold
Bit 1: Control Off
Bit 2–7: not used
120 A-96.250.731 / 041115
ProfibusProduct Specific Data for AMI Powercon
18.2.1 Data Formats
For further information see chapter 1 Data Formats, p. 7
Tab. 18-3 Status Code Byte
7 6 5 4 3 2 1 0
Quality Sub-Status Limits Meaning
0 0 The sub-status has a different quality depending on the coding
bad
0 1 uncertain
1 0 good
0 0 ok
0 1 low limited
1 0 high limited
1 1 constant
Tab. 18-4 Status codes of the measured value
Status
code
Device status Meaning Limits
0x08 BAD Not connected (Temp Sensor not connected)
0x0C BAD device failure
0x10 BAD sensor failure (Temp Sensor Short Circuit)
0x40 UNCERTAIN e.g. because of Temp Sensor Error CONST
0x47 UNCERTAIN Last usable value (HOLD) CONST
0x50 UNCERTAIN sensor conversion not accurate (e.g. No Flow) OK
0x64
0x67
UNCERTAIN Sensor calibration Sensor calibration, hold
OK CONST
0x80 GOOD ok OK
0x89
0x8A
GOOD Warning Low Warning High
LOW_LIM HIGH_LIM
0x8D
0x8E
GOOD Alarm Low Alarm High
LOW_LIM HICH_LIM
Tab. 18-5 DP Diagnostics
Byte Description
0 Status 1 Standard DP Diagnostics1 Status 2
2 Status 3
3 Master address
4 Ident number (high byte)
5 Ident number (low byte)
6 Header (block length incl. Header byte) = 14 Status coding accord-ing to DP/V17 Status Type (0x81)
8 Slot Number (0x00)
9 Status Specifier
10–13 Diagnosis
14–19 Diagnosis Extension
A-96.250.731 / 041115 121
ProfibusProduct Specific Data for AMI Powercon
Tab. 18-6 The diagnosis object consists of 4 Bytes
Byte Bit Meaning when “1” Abbreviation
0 0 Hardware failure electronics DIA_HW_ELECTR
1 Hardware failure mechanics DIA_HW_MECH
2 -
3 Electronic temperature too high DIA_TEMP_ELECTR
4 -
5 Measurement failure DIA_MEASUREMENT
6 -
7 -
1 0 -
1 -
2 -
3 -
4 -
5 Maintenance required DIA_MAINTENANCE
6 -
7 -
2 0 -
1 -
2 -
3 -
4 -
5 -
6 -
7 -
3 0 -
1 -
2 -
3 -
4 -
5 -
6 -
7 Extension Available EXTENSION_AVAILABLE
122 A-96.250.731 / 041115
ProfibusProduct Specific Data for AMI Powercon
Bytes 4 and 5 are reserved for future extensions.
Tab. 18-7 The diagnosis extension object consists of 6 Bytes.
Byte Bit Meaning when “1” Abbreviation
0 0 Cond. 1 Alarm high -
1 Cond. 1 Alarm low -
2 -
3 -
4 -
5 -
6 Sample Temp. high DIA_MEASUREMENT
7 Sample Temp. low DIA_MEASUREMENT
1 0 Sample Flow high DIA_MEASUREMENT
1 Sample Flow low DIA_MEASUREMENT
2 Temp. shorted DIA_HW_ELECTR
3 Temp. disconnected DIA_HW_ELECTR
4 Case Temp. high DIA_TEMP_ELECTR
5 Case Temp. low DIA_TEMP_ELECTR
6
7
2 0 Control Timeout -
1
2
3
4
5
6
7 Input Active DIA_HW_ELECTR
3 0 IC MK41T56 DIA_HW_ELECTR
1 IC LM75 DIA_HW_ELECTR
2 IC PCF8574 DIA_HW_ELECTR
3 EEprom Microcon DIA_HW_ELECTR
4 EEProm Motherboard DIA_HW_ELECTR
5 EEProm Front-end DIA_HW_ELECTR
6 Cal. Recout DIA_HW_ELECTR
7 Wrong Front-end DIA_HW_ELECTR
A-96.250.731 / 041115 123
ProfibusProduct Specific Data for AMI Powercon
18.3. Configuration
18.3.1 Device Master Files (GSD)
The device is ready for system integration once commissioning has been effected via the local display or the Class 2 master. The PROFIBUS system requires a description of the device parameters, e.g. output data, input data, data format, data volume and supported transmission rate, so that it can integrate the field devices into the bus system. These data are contained in a Device Master File (GSD file) which is placed at the disposal of the PROFIBUS master while the communication system is being commissioned. Device bitmaps can also be integrated. These appear as icons in the network tree.The Profile 3.0 Device Master File (GSD) allows field devices from various manufacturers to be exchanged without having to reconfigure.
18.3.2 GSD File Types
Prior to configuration, decide which GSD you want to use to operate the system.You can change the setting by means of a Class 2 master (under Physical Block-Parameter Ident_Number_Selector)The following two Device Master Files with different functionalities are available:Manufacturer-specific GSD with Profile 3.0 functionality (default setting):This GSD guarantees the unlimited functionality of the field device. Device-specific process parameters and functions are therefore available.Profile GSD's:If a system is configured with profile GSD's, it is possible to exchange devices that are supplied by various manufacturers. It is, however, essential that the cyclic process values follow the same sequence. The transmitter supports the profiles Analyzer and Multivariable (IEC 61158-2). These GSD's comprise Analog Input blocks (AI)
Working with GSD filesThe GSDs must be integrated into the automation system. Depending on the software that is being used, the GSD files can be copied to the program-specific directory or can be read into the database using the import function within the configuration software.
Tab. 18-8 GSD files for AMI Powercon
Device name Ident_number_
Selector
ID number GSD Bitmaps
Manufacturer specific GSD with Profile 3.0 functionality:
AMI Powercon 1 17D0Hex SW17D0.gsd SW17D0_D.bmp
SW17D0_N.bmp SW17D0_S.bmp
Profile 3.0 GSD Analyzer:
AMI Powercon 0 9750 Hex PA039750.gsd PA_9750n.bmp
Profile 3.0 GSD Multivariable:
AMI Powercon 3 9760 Hex PA039760.gsd PA_9760n.bmp
124 A-96.250.731 / 041115
ProfibusProduct Specific Data for AMI Rescon
19. Product Specific Data for AMI Rescon
19.1. Introduction
The AMI family of transmitters provides a common base for a number of analytical instruments with application specific sensor interfaces. Each instrument has a basic structure with identical functionality.AMI instruments can (optionally) be equipped with a PROFIBUS DP-V1 interface. The interface supports the PROFIBUS-PA Profile 3.0. This part of the manual describes the functionality of the interface and the integration of the AMI family of transmitters into an automation system.
Hardware Wiring, bus terminals and connectors are not part of this manual. It should, however, be noted that the observation of the corresponding standards is of paramount importance to proper operation. Setting the transmission rate to reasonable values will help avoid communication errors.
GSD File forAMI Rescon
The PROFIBUS system requires a description of the device parameters, e. g. output data, input data, data format, data volume and supported transmission rate, so that it can integrate the field devices into the bus system. These data are contained in a Device Master File (GSD file) which is placed at the disposal of the PROFIBUS master while communication system is being commissioned.
Device bitmaps can also be integrated. These appear as icons in the network tree.The manufacturer-specific GSD file SW17D3.gsd is available for download from http://www.swan.ch
19.2. Cyclic Data Telegram
Input Data The AMI Rescon makes the following modules available as input data for the cyclic data exchange:
1 Main Process Value (µS/cm; M Ohm)
2 Main Temperature
3 Main Flow (l/h)
4 Diagnostic Values (5 Values)
– Meas. Value uncompensated
– Cell Constant in cm-1
– Reserved (for internal use)
– Reserved (for internal use)
– Case Temperature in °C
A-96.250.731 / 140212 125
ProfibusProduct Specific Data for AMI Rescon
The input data is transferred from AMI Rescon in the following structure:
Output Data The AMI Rescon makes the following module available as output data for the cyclic data exchange:
1 Control AMI
The control data is transferred to the AMI Rescon in the following structure:
Tab. 19-1 Input data structure from AMI Rescon
Index input data Data Access
Data format / comments Configuration data
0–4 Analog Input block 1 Main Process Value
read Measured value (32-bit floating point number) Status byte
0x42, 0x84, 0x08, 0x05 or 0x42, 0x84, 0x81, 0x81 or 0x94
5–9 Analog Input block 2 Main Temperature
read Measured value (32-bit floating point number) Status byte
0x42, 0x84, 0x08, 0x05 or 0x42, 0x84, 0x81, 0x81 or 0x94
10–14 Analog Input block 3 Main Flow
read Measured value (32-bit floating point number) Status byte
0x42, 0x84, 0x08, 0x05 or 0x42, 0x84, 0x81, 0x81 or 0x94
15–34 Diagnostic Values read 5 Measured values (32-bit floating point number)
0x45, 0x93, 0x08, 0x08, 0x08, 0x08, 0x080xD9
Tab. 19-2 Output data structure
Index output data Data Access Data format / comments Configuration data
0–1 Control AMI
(SP_D)
write Byte 0Bit 0: Relay 1
0 = open1 = close
0x82, 0x81, 0x05, 0x05 or 0x82, 0x81, 0x84, 0x82 or 0xA1
Bit 1: Relay 2 0 = open1 = close
Bit 2: not used
Bit 3: not used
Bit 4–7: not used
Byte 1Bit 0: Hold
Bit 1: Control Off
Bit 2–7: not used
126 A-96.250.731 / 140212
ProfibusProduct Specific Data for AMI Rescon
19.2.1 Data Formats
For further information see chapter 1 Data Formats, p. 7
Tab. 19-3 Status Code Byte
7 6 5 4 3 2 1 0
Quality Sub-Status Limits Meaning
0 0 The sub-status has a different quality depending on the coding
bad
0 1 uncertain
1 0 good
0 0 ok
0 1 low limited
1 0 high limited
1 1 constant
Tab. 19-4 Status codes of the measured value
Status
code
Device status Meaning Limits
0x08 BAD Not connected (Temp Sensor not connected)
0x0C BAD device failure
0x10 BAD sensor failure (Temp Sensor Short Circuit)
0x47 UNCERTAIN Last usable value (HOLD) CONST
0x50 UNCERTAIN sensor conversion not accurate (e.g. No Flow) OK
0x64
0x67
UNCERTAIN Sensor calibration Sensor calibration, hold
OK CONST
0x80 GOOD ok OK
0x89
0x8A
GOOD Warning Low Warning High
LOW_LIM HIGH_LIM
0x8D
0x8E
GOOD Alarm Low Alarm High
LOW_LIM HICH_LIM
Tab. 19-5 DP Diagnostics
Byte Description
0 Status 1 Standard DP Diagnostics1 Status 2
2 Status 3
3 Master address
4 Ident number (high byte)
5 Ident number (low byte)
6 Header (block length incl. Header byte) = 14 Status coding accord-ing to DP/V17 Status Type (0x81)
8 Slot Number (0x00)
9 Status Specifier
10–13 Diagnosis
14–19 Diagnosis Extension
A-96.250.731 / 140212 127
ProfibusProduct Specific Data for AMI Rescon
Tab. 19-6 The diagnosis object consists of 4 Bytes
Byte Bit Meaning when “1” Abbreviation
0 0 Hardware failure electronics DIA_HW_ELECTR
1 Hardware failure mechanics DIA_HW_MECH
2 -
3 Electronic temperature too high DIA_TEMP_ELECTR
4 -
5 Measurement failure DIA_MEASUREMENT
6 -
7 -
1 0 -
1 -
2 -
3 -
4 -
5 Maintenance required DIA_MAINTENANCE
6 -
7 -
2 0 -
1 -
2 -
3 -
4 -
5 -
6 -
7 -
3 0 -
1 -
2 -
3 -
4 -
5 -
6 -
7 Extension Available EXTENSION_AVAILABLE
128 A-96.250.731 / 140212
ProfibusProduct Specific Data for AMI Rescon
Byte 5 is reserved for future extensions.
Tab. 19-7 The diagnosis extension object consists of 6 Bytes.
Byte Bit Meaning when “1” Abbreviation
0 0 Cond. 1 Alarm high -
1 Cond. 1 Alarm low -
2 -
3 -
4 -
5 -
6 Sample Temp. high DIA_MEASUREMENT
7 Sample Temp. low DIA_MEASUREMENT
1 0 Sample Flow high DIA_MEASUREMENT
1 Sample Flow low DIA_MEASUREMENT
2 Temp. shorted DIA_HW_ELECTR
3 Temp. disconnected DIA_HW_ELECTR
4 Case Temp. high DIA_TEMP_ELECTR
5 Case Temp. low DIA_TEMP_ELECTR
6 USP Error DIA_MEASUREMENT
7
2 0 Control Timeout -
1
2 Sensor shorted DIA_HW_ELECTR
3 Sensor disconnected DIA_HW_ELECTR
4
5
6
7 Input Active DIA_HW_ELECTR
3 0 IC MK41T56 DIA_HW_ELECTR
1 IC LM75 DIA_HW_ELECTR
2 IC PCF8574 DIA_HW_ELECTR
3 EEprom Microcon DIA_HW_ELECTR
4 EEProm Motherboard DIA_HW_ELECTR
5 EEProm Front-end DIA_HW_ELECTR
6 Cal. Recout DIA_HW_ELECTR
7 Wrong Front-end DIA_HW_ELECTR
4 0 Transmitter check DIA_MAINTENANCE
1
2
3
4
5
6
7
A-96.250.731 / 140212 129
ProfibusProduct Specific Data for AMI Rescon
19.3. Configuration
19.3.1 Device Master Files (GSD)
The device is ready for system integration once commissioning has been effected via the local display or the Class 2 master. The PROFIBUS system requires a description of the device parameters, e.g. output data, input data, data format, data volume and supported transmission rate, so that it can integrate the field devices into the bus system. These data are contained in a Device Master File (GSD file) which is placed at the disposal of the PROFIBUS master while the communication system is being commissioned. Device bitmaps can also be integrated. These appear as icons in the network tree.The Profile 3.0 Device Master File (GSD) allows field devices from various manufacturers to be exchanged without having to reconfigure.
19.3.2 GSD File Types
Prior to configuration, decide which GSD you want to use to operate the system.You can change the setting by means of a Class 2 master (under Physical Block-Parameter Ident_Number_Selector)The following two Device Master Files with different functionalities are available:Manufacturer-specific GSD with Profile 3.0 functionality (default setting):This GSD guarantees the unlimited functionality of the field device. Device-specific process parameters and functions are therefore available.Profile GSD's:If a system is configured with profile GSD's, it is possible to exchange devices that are supplied by various manufacturers. It is, however, essential that the cyclic process values follow the same sequence. The transmitter supports the profiles Analyzer and Multivariable (IEC 61158-2). These GSD's comprise Analog Input blocks (AI)
Working with GSD filesThe GSDs must be integrated into the automation system. Depending on the software that is being used, the GSD files can be copied to the program-specific directory or can be read into the database using the import function within the configuration software.
Tab. 19-8 GSD files for AMI Rescon
Device name Ident_number_
Selector
ID number GSD Bitmaps
Manufacturer specific GSD with Profile 3.0 functionality:
AMI Rescon 1 17D3Hex SW17D3.gsd SW17D3_D.bmp
SW17D3_N.bmp SW17D3_S.bmp
Profile 3.0 GSD Analyzer:
AMI Rescon 0 9750 Hex PA039750.gsd PA_9750n.bmp
Profile 3.0 GSD Multivariable:
AMI Rescon 3 9760 Hex PA039760.gsd PA_9760n.bmp
130 A-96.250.731 / 140212
ProfibusProduct Specific Data for AMI Silica
20. Product Specific Data for AMI Silica
20.1. Introduction
The AMI family of transmitters provides a common base for a number of analytical instruments with application specific sensor interfaces. Each instrument has a basic structure with identical functionality.AMI instruments can (optionally) be equipped with a PROFIBUS DP-V1 interface. The interface supports the PROFIBUS-PA Profile 3.0. This part of the manual describes the functionality of the interface and the integration of the AMI family of transmitters into an automation system.
Hardware Wiring, bus terminals and connectors are not part of this manual. It should, however, be noted that the observation of the corresponding standards is of paramount importance to proper operation. Setting the transmission rate to reasonable values will help avoid communication errors.
GSD File forAMI Silica
The PROFIBUS system requires a description of the device parameters, e. g. output data, input data, data format, data volume and supported transmission rate, so that it can integrate the field devices into the bus system. These data are contained in a Device Master File (GSD file) which is placed at the disposal of the PROFIBUS master while communication system is being commissioned.
Device bitmaps can also be integrated. These appear as icons in the network tree.The manufacturer-specific GSD file SW17C8.gsd is available for download from http://www.swan.ch
20.2. Cyclic Data Telegram
Input Data The AMI Silica makes the following modules available as input data for the cyclic data exchange:
1 Silica channels 1 to 6
2 Main Temperature
3 Main Flow
4 Status AMI
5 Diagnostic Values (5 values)
– Absorbance last value
– Absorbance continuous
– Transmission in V
– State
– Case Temperature in °C
A-96.250.731 / 041115 131
ProfibusProduct Specific Data for AMI Silica
The input data is transferred from AMI Silica in the following structure:
The Status AMI input data is transferred from AMI Silica in the following structure
Tab. 20-1 Input data structure from AMI Silica
Index input data Data Access
Data format / comments Configuration data
0–4 “““
25–29
Analog Input block 1Silica Channels 1
Analog Input block 6Silica Channel 6
read Measured value (32-bit floating point number) Status byte
Measured value (32-bit floating point number) Status byte
0x42, 0x84, 0x08, 0x05 or 0x42, 0x84, 0x81, 0x81 or 0x94
0x42, 0x84, 0x08, 0x05 or 0x42, 0x84, 0x81, 0x81 or 0x94
30–34 Analog Input block 7 Main Temperature
read Measured value (32-bit floating point number) Status byte
0x42, 0x84, 0x08, 0x05 or 0x42, 0x84, 0x81, 0x81 or 0x94
35–39 Analog Input block 8 Main Flow
read Measured value (32-bit floating point number) Status byte
0x42, 0x84, 0x08, 0x05 or 0x42, 0x84, 0x81, 0x81 or 0x94
40–41 Status AMI read 0x42, 0x81, 0x05, 0x05 or0x42, 0x81, 0x83, 0x81 or0x91
42–61 Diagnostic Values read 5 Measured values (32-bit floating point number)
0x45, 0x93, 0x08, 0x08, 0x08, 0x08, 0x08 or0xD9
Index input data Data Access Data format / comments Configuration data
40–41 Control AMI (OUT_D)
write Byte 0Bit 0–3:Bit 4–7:
Channel ValveChannel Meas
0x42, 0x81, 0x05, 0x05 or 0x42, 0x81, 0x84, 0x82 or 0x91
Byte 1
Bit 0–5: Sequencer Inputs Channel 1–6
Bit 6: reserved
Bit 7: No Flow
132 A-96.250.731 / 041115
ProfibusProduct Specific Data for AMI Silica
Output Data The AMI Silica makes the following module available as output data for the cyclic data exchange:
1 Control AMI
The control data is transferred to the AMI Silica in the following structure:
Tab. 20-2 Output data structure
Index output data Data Access Data format / comments Configuration data
0–1 Control AMI (SP_D)
write Byte 0Bit 0: Relay 1
0 = open1 = close
0x82, 0x81, 0x05, 0x05 or 0x82, 0x81, 0x84, 0x82 or 0xA1
Bit 1: Relay 20 = open1 = close
Bit 2–7: Not used
Byte 1
Bit 0–2: Channel 0*, 1–6
Bit 3–5: reserved
Bit 6: Control Off
Bit 7: Hold * Channel = 0: Auto Select
A-96.250.731 / 041115 133
ProfibusProduct Specific Data for AMI Silica
20.2.1 Data Formats
For further information see chapter 1 Data Formats, p. 7
Tab. 20-3 Status Code Byte
7 6 5 4 3 2 1 0
Quality Sub-Status Limits Meaning
0 0 The sub-status has a different quality depending on the coding
bad
0 1 uncertain
1 0 good
0 0 ok
0 1 low limited
1 0 high limited
1 1 constant
Tab. 20-4 Status codes of the measured value
Status
code
Device status Meaning Limits
0x08 BAD Not connected (Temp Sensor not connected)
0x0C BAD device failure
0x10 BAD sensor failure (Temp Sensor Short Circuit)
0x47 UNCERTAIN Last usable value (HOLD) CONST
0x4F UNCERTAIN Initial value CONST
0x50 UNCERTAIN sensor conversion not accurate (e.g. No Flow) OK
0x64
0x67
UNCERTAIN Sensor calibration Sensor calibration, hold
OK CONST
0x80 GOOD ok OK
0x89
0x8A
GOOD Warning Low Warning High
LOW_LIM HIGH_LIM
0x8D
0x8E
GOOD Alarm Low Alarm High
LOW_LIM HICH_LIM
Tab. 20-5 DP Diagnostics
Byte Description
0 Status 1 Standard DP Diagnostics1 Status 2
2 Status 3
3 Master address
4 Ident number (high byte)
5 Ident number (low byte)
6 Header (block length incl. Header byte) = 14 Status coding accord-ing to DP/V17 Status Type (0x81)
8 Slot Number (0x00)
9 Status Specifier
10–13 Diagnosis
14–19 Diagnosis Extension
134 A-96.250.731 / 041115
ProfibusProduct Specific Data for AMI Silica
Tab. 20-6 The diagnosis object consists of 4 Bytes
Byte Bit Meaning when “1” Abbreviation
0 0 Hardware failure electronics DIA_HW_ELECTR
1 Hardware failure mechanics DIA_HW_MECH
2 -
3 Electronic temperature too high DIA_TEMP_ELECTR
4 -
5 Measurement failure DIA_MEASUREMENT
6 -
7 -
1 0 -
1 -
2 -
3 -
4 -
5 Maintenance required DIA_MAINTENANCE
6 -
7 -
2 0 -
1 -
2 -
3 -
4 -
5 -
6 -
7 -
3 0 -
1 -
2 -
3 -
4 -
5 -
6 -
7 Extension Available EXTENSION_AVAILABLE
A-96.250.731 / 041115 135
ProfibusProduct Specific Data for AMI Silica
Tab. 20-7 The diagnosis extension object consists of 6 Bytes.
Byte Bit Meaning when “1” Abbreviation0 0
1
2
3
4
5
6 Sample Temp. high7 Sample Temp. low
1 0 Sample Flow high DIA_MEASUREMENT1 Sample Flow low DIA_MEASUREMENT2
3 Temp. disconnected DIA_HW_ELECTR4 Case Temp. high DIA_TEMP_ELECTR5 Case Temp. low DIA_TEMP_ELECTR6 Valve defective DIA_MAINTENANCE7
2 0 Control Timeout1 Reagent Pump DIA_MAINTENANCE2 Photometer not connected DIA_MAINTENANCE3 Photometer dirty DIA_MAINTENANCE4
5 Reagent Empty DIA_MAINTENANCE6 Sequencer DIA_HW_ELECTR7 Input Active DIA_HW_ELECTR
3 0 IC MK41T56 DIA_HW_ELECTR1 IC LM75 DIA_HW_ELECTR2 IC PCF8574 DIA_HW_ELECTR3 EEprom Microcon DIA_HW_ELECTR4 EEProm Motherboard DIA_HW_ELECTR5 Rovalve DIA_HW_ELECTR6 Cal. Recout DIA_HW_ELECTR7 Wrong Front-end DIA_HW_ELECTR
4 0 Sample Flow 1 low1 Sample Flow 2 low2 Sample Flow 3 low3 Sample Flow 4 low4 Sample Flow 5 low5 Sample Flow 6 low6
7
5 0 Reagents low DIA_MAINTENANCE1
2
3 - -4 - -5 - -6 - -7 - -
136 A-96.250.731 / 041115
ProfibusProduct Specific Data for AMI Silica
20.3. Configuration
20.3.1 Device Master Files (GSD)
The device is ready for system integration once commissioning has been effected via the local display or the Class 2 master. The PROFIBUS system requires a description of the device parameters, e.g. output data, input data, data format, data volume and supported transmission rate, so that it can integrate the field devices into the bus system. These data are contained in a Device Master File (GSD file) which is placed at the disposal of the PROFIBUS master while the communication system is being commissioned. Device bitmaps can also be integrated. These appear as icons in the network tree. The Profile 3.0 Device Master File (GSD) allows field devices from various manufacturers to be exchanged without having to reconfigure.
20.3.2 GSD File Types
Prior to configuration, decide which GSD you want to use to operate the system. You can change the setting by means of a Class 2 master (under Physical Block-Parame-
ter Ident_Number_Selector)The following two Device Master Files with different functionalities are available: Manufacturer-specific GSD with Profile 3.0 functionality (default setting): This GSD guarantees the unlimited functionality of the field device. Device-specific pro-
cess parameters and functions are therefore available. Profile GSD's: If a system is configured with profile GSD's, it is possible to exchange devices that are
supplied by various manufacturers. It is, however, essential that the cyclic process values follow the same sequence. The transmitter supports the profiles Analyzer and Multivaria-ble (IEC 61158-2). These GSD's comprise Analog Input blocks (AI)
Working with GSD filesThe GSDs must be integrated into the automation system. Depending on the software that is being used, the GSD files can be copied to the program-specific directory or can be read into the database using the import function within the configuration software.
Tab. 20-8 GSD files for AMI Silica:
Device name Ident_number_
Selector
ID number GSD Bitmaps
Manufacturer specific GSD with Profile 3.0 functionality:
AMI Silica 1 17C8Hex SW17C8.gsd SW17C8_D.bmp
SW17C8_N.bmp SW17C8_S.bmp
Profile 3.0 GSD Analyzer:
AMI Silica 0 9750 Hex PA139750.gsd PA_9750n.bmp
Profile 3.0 GSD Multivariable:
AMI Silica 3 9760 Hex PA139760.gsd PA_9760n.bmp
A-96.250.731 / 041115 137
ProfibusProduct Specific Data for AMI Silica
138 A-96.250.731 / 041115
ProfibusProduct Specific Data for AMI Silitrace
21. Product Specific Data for AMI Silitrace
21.1. Introduction
The AMI family of transmitters provides a common base for a number of analytical instruments with application specific sensor interfaces. Each instrument has a basic structure with identical functionality.AMI instruments can (optionally) be equipped with a PROFIBUS DP-V1 interface. The interface supports the PROFIBUS-PA Profile 3.0. This part of the manual describes the functionality of the interface and the integration of the AMI family of transmitters into an automation system.
Hardware Wiring, bus terminals and connectors are not part of this manual. It should, however, be noted that the observation of the corresponding standards is of paramount importance to proper operation. Setting the transmission rate to reasonable values will help avoid communication errors.
GSD File forAMI Silitrace
The PROFIBUS system requires a description of the device parameters, e. g. output data, input data, data format, data volume and supported transmission rate, so that it can integrate the field devices into the bus system. These data are contained in a Device Master File (GSD file) which is placed at the disposal of the PROFIBUS master while communication system is being commissioned.
Device bitmaps can also be integrated. These appear as icons in the network tree.The manufacturer-specific GSD file SW17CC.gsd is available for download from http://www.swan.ch
21.2. Cyclic Data Telegram
Input Data The AMI Silitrace makes the following modules available as input data for the cyclic data exchange:
1 Silica channels 1 to 6
2 Main Flow 1
3 Main Flow 2
4 Status AMI
5 Diagnostic Values (5 values)
– Absorbance last value
– Signal Period in Sec
– Transmission in V
– State
– Case Temperature in °C
A-96.250.731 / 191015 139
ProfibusProduct Specific Data for AMI Silitrace
The input data is transferred from AMI Silitrace in the following structure:
The Status AMI input data is transferred from AMI Silitrace in the following structure
Tab. 21-1 Input data structure from AMI Silitrace
Index input data Data Access
Data format / comments Configuration data
0–4 “““
25–29
Analog Input block 1Silica Channels 1
Analog Input block 6Silica Channel 6
read Measured value (32-bit floating point number) Status byte
Measured value (32-bit floating point number) Status byte
0x42, 0x84, 0x08, 0x05 or 0x42, 0x84, 0x81, 0x81 or 0x94
0x42, 0x84, 0x08, 0x05 or 0x42, 0x84, 0x81, 0x81 or 0x94
30–34 Analog Input block 7 Main Flow 1
read Measured value (32-bit floating point number) Status byte
0x42, 0x84, 0x08, 0x05 or 0x42, 0x84, 0x81, 0x81 or 0x94
35–39 Analog Input block 8 Main Flow 2
read Measured value (32-bit floating point number) Status byte
0x42, 0x84, 0x08, 0x05 or 0x42, 0x84, 0x81, 0x81 or 0x94
40–41 Status AMI read 0x42, 0x81, 0x05, 0x05 or0x42, 0x81, 0x83, 0x81 or0x91
42–61 Diagnostic Values read 5 Measured values (32-bit floating point number)
0x45, 0x93, 0x08, 0x08, 0x08, 0x08, 0x08 or0xD9
Index input data Data Access Data format / comments Configuration data
40–41 Status AMI (OUT_D)
write Byte 0Bit 0–3:Bit 4–7:
Channel ValveChannel Meas
0x42, 0x81, 0x05, 0x05 or 0x42, 0x81, 0x83, 0x81 or 0x91
Byte 1
Bit 0–5: Sequencer Inputs Channel 1–6
Bit 6: reserved
Bit 7: No Flow
140 A-96.250.731 / 191015
ProfibusProduct Specific Data for AMI Silitrace
Output Data The AMI Silitrace makes the following module available as output data for the cyclic data exchange:
1 Control AMI
The control data is transferred to the AMI Silitrace in the following structure:
Tab. 21-2 Output data structure
Index output data Data Access Data format / comments Configuration data
0–1 Control AMI (SP_D)
write Byte 0Bit 0: Relay 1
0 = open1 = close
0x82, 0x81, 0x05, 0x05 or 0x82, 0x81, 0x84, 0x82 or 0xA1
Bit 1: Relay 20 = open1 = close
Bit 2–7: Not used
Byte 1
Bit 0–2: Channel 0*, 1–6
Bit 3–5: reserved
Bit 6: Control Off
Bit 7: Hold * Channel = 0: Auto Select
A-96.250.731 / 191015 141
ProfibusProduct Specific Data for AMI Silitrace
21.2.1 Data Formats
For further information see chapter 1 Data Formats, p. 7
Tab. 21-3 Status Code Byte
7 6 5 4 3 2 1 0
Quality Sub-Status Limits Meaning
0 0 The sub-status has a different quality depending on the coding
bad
0 1 uncertain
1 0 good
0 0 ok
0 1 low limited
1 0 high limited
1 1 constant
Tab. 21-4 Status codes of the measured value
Status
code
Device status Meaning Limits
0x08 BAD Not connected (Sensor not connected)
0x0C BAD Device failure
0x10 BAD Sensor failure (Sensor Short Circuit)
0x47 UNCERTAIN Last usable value (HOLD) CONST
0x4F UNCERTAIN Initial value CONST
0x50 UNCERTAIN Sensor conversion not accurate (e.g. No Flow) OK
0x64
0x67
UNCERTAIN Sensor calibration Sensor calibration, hold
OK CONST
0x80 GOOD ok OK
0x89
0x8A
GOOD Warning Low Warning High
LOW_LIM HIGH_LIM
0x8D
0x8E
GOOD Alarm Low Alarm High
LOW_LIM HICH_LIM
Tab. 21-5 DP Diagnostics
Byte Description
0 Status 1 Standard DP Diagnostics1 Status 2
2 Status 3
3 Master address
4 Ident number (high byte)
5 Ident number (low byte)
6 Header (block length incl. Header byte) = 14 Status coding accord-ing to DP/V17 Status Type (0x81)
8 Slot Number (0x00)
9 Status Specifier
10–13 Diagnosis
14–19 Diagnosis Extension
142 A-96.250.731 / 191015
ProfibusProduct Specific Data for AMI Silitrace
Tab. 21-6 The diagnosis object consists of 4 Bytes
Byte Bit Meaning when “1” Abbreviation
0 0 Hardware failure electronics DIA_HW_ELECTR
1 Hardware failure mechanics DIA_HW_MECH
2 -
3 Electronic temperature too high DIA_TEMP_ELECTR
4 -
5 Measurement failure DIA_MEASUREMENT
6 -
7 -
1 0 -
1 -
2 -
3 -
4 -
5 Maintenance required DIA_MAINTENANCE
6 -
7 -
2 0 -
1 -
2 -
3 -
4 -
5 -
6 -
7 -
3 0 -
1 -
2 -
3 -
4 -
5 -
6 -
7 Extension Available EXTENSION_AVAILABLE
A-96.250.731 / 191015 143
ProfibusProduct Specific Data for AMI Silitrace
Tab. 21-7 The diagnosis extension object consists of 6 Bytes.
Byte Bit Meaning when “1” Abbreviation0 0 Si 1 Alarm high DIA_MEASUREMENT
1 Si 1 Alarm low DIA_MEASUREMENT2 Si 2 Alarm high DIA_MEASUREMENT3 Si 2 Alarm low DIA_MEASUREMENT4 - -5 - -6 SilTrace Temp. high DIA_HW_ELECTR7 SilTrace Temp. low DIA_HW_ELECTR
1 0 Sample Flow high DIA_MEASUREMENT1 Sample Flow low DIA_MEASUREMENT2 Absorbance too high DIA_MEASUREMENT3 Temp. Timeout DIA_HW_ELECTR4 Case Temp. high DIA_TEMP_ELECTR5 Case Temp. low DIA_TEMP_ELECTR6 Pump Speed high DIA_MAINTENANCE7 Pump Speed low DIA_MAINTENANCE
2 0 Control Timeout -1 Reagent Pump DIA_HW_ELECTR2 SilTrace DIA_HW_ELECTR3 Photometer dirty DIA_MAINTENANCE4 Signal Timeout DIA_MEASUREMENT5 Reagent Empty DIA_MAINTENANCE6 Sequencer DIA_HW_ELECTR7 Input Active DIA_HW_ELECTR
3 0 Rovalve DIA_HW_ELECTR1 IC LM75 DIA_HW_ELECTR2 IC PCF8574 DIA_HW_ELECTR3 Signal output open DIA_HW_ELECTR4 EEProm Motherboard DIA_HW_ELECTR5 EEProm Frontend DIA_HW_ELECTR6 Cal. Recout DIA_HW_ELECTR7 Wrong Front-end DIA_HW_ELECTR
4 0 Sample Flow 1 low -1 Sample Flow 2 low -2 Sample Flow 3 low -3 Sample Flow 4 low -4 Sample Flow 5 low -5 Sample Flow 6 low -6 - -7 - -
5 0 Reagents low DIA_MAINTENANCE1 - -2 - -3 - -4 - -5 - -6 - -7 - -
144 A-96.250.731 / 191015
ProfibusProduct Specific Data for AMI Silitrace
21.3. Configuration
21.3.1 Device Master Files (GSD)
The device is ready for system integration once commissioning has been effected via the local display or the Class 2 master. The PROFIBUS system requires a description of the device parameters, e.g. output data, input data, data format, data volume and supported transmission rate, so that it can integrate the field devices into the bus system. These data are contained in a Device Master File (GSD file) which is placed at the disposal of the PROFIBUS master while the communication system is being commissioned. Device bitmaps can also be integrated. These appear as icons in the network tree. The Profile 3.0 Device Master File (GSD) allows field devices from various manufacturers to be exchanged without having to reconfigure.
21.3.2 GSD File Types
Prior to configuration, decide which GSD you want to use to operate the system. You can change the setting by means of a Class 2 master (under Physical Block-Parame-
ter Ident_Number_Selector)The following two Device Master Files with different functionalities are available: Manufacturer-specific GSD with Profile 3.0 functionality (default setting):
This GSD guarantees the unlimited functionality of the field device. Device-specific pro-cess parameters and functions are therefore available.
Profile GSD's:If a system is configured with profile GSD's, it is possible to exchange devices that are supplied by various manufacturers. It is, however, essential that the cyclic process values follow the same sequence. The transmitter supports the profiles Analyzer and Multivaria-ble (IEC 61158-2). These GSD's comprise Analog Input blocks (AI)
Working with GSD filesThe GSDs must be integrated into the automation system. Depending on the software that is being used, the GSD files can be copied to the program-specific directory or can be read into the database using the import function within the configuration software.
Tab. 21-8 GSD files for AMI Silitrace:
Device name Ident_number_
Selector
ID number GSD Bitmaps
Manufacturer specific GSD with Profile 3.0 functionality:
AMI Silitrace 1 17CCHex SW17CC.gsd SW17CC_D.bmp
SW17CC_N.bmp SW17CC_S.bmp
Profile 3.0 GSD Analyzer:
AMI Silitrace 0 9750 Hex PA139750.gsd PA_9750n.bmp
Profile 3.0 GSD Multivariable:
AMI Silitrace 3 9760 Hex PA139760.gsd PA_9760n.bmp
A-96.250.731 / 191015 145
ProfibusProduct Specific Data for AMI Silitrace
146 A-96.250.731 / 191015
ProfibusProduct Specific Data for AMI Sodium
22. Product Specific Data for AMI Sodium
22.1. Introduction
This description applies for the AMI Sodium A and the AMI Sodium P.The AMI Sodium A and P are complete monitoring systems for the continuous determination of dissolved sodium in the ppb-range for steam, condensate and high purity water.The AMI family of transmitters provides a common base for a number of analytical instruments with application specific sensor interfaces. Each instrument has a basic structure with identical functionality.AMI instruments can (optionally) be equipped with a PROFIBUS DP-V1 interface. The interface supports the PROFIBUS-PA Profile 3.0. This part of the manual describes the functionality of the interface and the integration of the AMI family of transmitters into an automation system.
Hardware Wiring, bus terminals and connectors are not part of this manual. It should, however, be noted that the observation of the corresponding standards is of paramount importance to proper operation. Setting the transmission rate to reasonable values will help avoid communication errors.
GSD File forAMI Sodium
The PROFIBUS system requires a description of the device parameters, e. g. output data, input data, data format, data volume and supported transmission rate, so that it can integrate the field devices into the bus system. These data are contained in a Device Master File (GSD file) which is placed at the disposal of the PROFIBUS master while communication system is being commissioned.
Device bitmaps can also be integrated. These appear as icons in the network tree.The manufacturer-specific GSD file SW17C3.gsd is available for download from http://www.swan.ch
22.2. Cyclic Data Telegram
Input Data The AMI Sodium A and the AMI SodiumP make the following modules available as input data for the cyclic data exchange:
1 Main Process Value (Sodium Channel 1 in ppb)
2 Main Temperature
3 Sample Monitoring (Flow or pH Control)
4 2nd Process Value (pH)
5 3rd Process Value (Sodium Channel 2 in ppb)
6 Diagnostic Values (5 values)
– Raw value Sodium in mV
– Raw Flow / % pH Control
– Raw Value pH in mV
– Channel Switch State (Channel * 65536 + TimeOut)
– Case Temperature in °C
A-96.250.731 / 140212 147
ProfibusProduct Specific Data for AMI Sodium
The input data is transferred from AMI Sodium A and P in the following structure:
Output Data The AMI Sodium A and P make the following module available as output data for the cyclic data exchange:
1 Control AMI
The control data is transferred to the AMI Sodium A and P in the following structure:
Tab. 22-1 Input data structure from AMI Sodium A and P
Index input data Data Access
Data format / comments Configuration data
0–4 Analog Input block 1 Main Process Value
read Measured value (32-bit floating point number) Status byte
0x42, 0x84, 0x08, 0x05 or 0x42, 0x84, 0x81, 0x81 or 0x94
5–9 Analog Input block 2Main Temperature
read Measured value (32-bit floating point number) Status byte
0x42, 0x84, 0x08, 0x05 or 0x42, 0x84, 0x81, 0x81 or 0x94
10–14 Analog Input block 3 Sample Monitoring
read Measured value (32-bit floating point number) Status byte
0x42, 0x84, 0x08, 0x05 or 0x42, 0x84, 0x81, 0x81 or 0x94
15–19 Analog Input block 4 2nd Process Value
read Measured value (32-bit floating point number) Status byte
0x42, 0x84, 0x08, 0x05 or 0x42, 0x84, 0x81, 0x81 or 0x94
20–24 Analog Input block 5 3rd Process Value
read Measured value (32-bit floating point number) Status byte
0x42, 0x84, 0x08, 0x05 or 0x42, 0x84, 0x81, 0x81 or 0x94
25–44 Diagnostic Values read 5 Measured values (32-bit floating point number)
0x45, 0x93, 0x08, 0x08, 0x08, 0x08, 0x08 or0xD9
Tab. 22-2 Output data structure
Index output data Data Access Data format / comments Configuration data
0–1 Control AMI
(SP_D)
write Byte 0Bit 0: Relay 1
0 = open1 = close
0x82, 0x81, 0x05, 0x05 or 0x82, 0x81, 0x84, 0x82 or 0xA1
Bit 1: Relay 2 0 = open1 = close
Bit 2–3: not used
Bit 4: Channel Select0 = Channel 11 = Channel 2
Bit 5–7: not used
Byte 1Bit 0: Hold
Bit 1: Control Off
Bit 2–7: not used
148 A-96.250.731 / 140212
ProfibusProduct Specific Data for AMI Sodium
22.2.1 Data Formats
For further information see chapter 1 Data Formats, p. 7
Tab. 22-3 Status Code Byte
7 6 5 4 3 2 1 0
Quality Sub-Status Limits Meaning
0 0 The sub-status has a different quality depending on the coding
bad
0 1 uncertain
1 0 good
0 0 ok
0 1 low limited
1 0 high limited
1 1 constant
Tab. 22-4 Status codes of the measured value
Status
code
Device status Meaning Limits
0x08 BAD Not connected (Temp Sensor not connected)
0x0C BAD device failure
0x10 BAD sensor failure (Temp Sensor Short Circuit)
0x47 UNCERTAIN Last usable value (HOLD) CONST
0x50 UNCERTAIN sensor conversion not accurate (e.g. No Flow) OK
0x64
0x67
UNCERTAIN Sensor calibration Sensor calibration, hold
OK CONST
0x80 GOOD ok OK
0x89
0x8A
GOOD Warning Low Warning High
LOW_LIM HIGH_LIM
0x8D
0x8E
GOOD Alarm Low Alarm High
LOW_LIM HICH_LIM
Tab. 22-5 DP Diagnostics
Byte Description
0 Status 1 Standard DP Diagnostics1 Status 2
2 Status 3
3 Master address
4 Ident number (high byte)
5 Ident number (low byte)
6 Header (block length incl. Header byte) = 14 Status coding accord-ing to DP/V17 Status Type (0x81)
8 Slot Number (0x00)
9 Status Specifier
10–13 Diagnosis
14–19 Diagnosis Extension
A-96.250.731 / 140212 149
ProfibusProduct Specific Data for AMI Sodium
Tab. 22-6 The diagnosis object consists of 4 Bytes
Byte Bit Meaning when “1” Abbreviation
0 0 Hardware failure electronics DIA_HW_ELECTR
1 Hardware failure mechanics DIA_HW_MECH
2 -
3 Electronic temperature too high DIA_TEMP_ELECTR
4 -
5 Measurement failure DIA_MEASUREMENT
6 -
7 -
1 0 -
1 -
2 -
3 -
4 -
5 Maintenance required DIA_MAINTENANCE
6 -
7 -
2 0 -
1 -
2 -
3 -
4 -
5 -
6 -
7 -
3 0 -
1 -
2 -
3 -
4 -
5 -
6 -
7 Extension Available EXTENSION_AVAILABLE
150 A-96.250.731 / 140212
ProfibusProduct Specific Data for AMI Sodium
Bytes 4 and 5 are reserved for future extensions.
Tab. 22-7 The diagnosis extension object consists of 6 Bytes.
Byte Bit Meaning when “1” Abbreviation
0 0 Sodium 1 Alarm high
1 Sodium 1 Alarm low
2 pH Alarm high
3 pH Alarm low
4 Sodium 2 Alarm high
5 Sodium 2 Alarm low
6 Sample Temp. high DIA_MEASUREMENT
7 Sample Temp. low DIA_MEASUREMENT
1 0 Sample Flow high DIA_MEASUREMENT
1 Sample Flow low DIA_MEASUREMENT
Temp. shorted DIA_HW_ELECTR
3 Temp. disconnected DIA_HW_ELECTR
4 Case Temp. high DIA_TEMP_ELECTR
5 Case Temp. low DIA_TEMP_ELECTR
6
7
2 0 Control Timeout
1 Reagent Empty DIA_MAINTENANCE
2 No Sample DIA_MEASUREMENT
3
4
5
6 Cleaning Reagent DIA_MAINTENANCE
7 Input Active DIA_HW_ELECTR
3 0 IC MK41T56 DIA_HW_ELECTR
1 IC LM75 DIA_HW_ELECTR
2 IC PCF8574 DIA_HW_ELECTR
3 EEprom Microcon DIA_HW_ELECTR
4 EEProm Motherboard DIA_HW_ELECTR
5 EEProm Front-end DIA_HW_ELECTR
6 Cal. Recout DIA_HW_ELECTR
7 Wrong Front-end DIA_HW_ELECTR
A-96.250.731 / 140212 151
ProfibusProduct Specific Data for AMI Sodium
22.3. Configuration
22.3.1 Device Master Files (GSD)
The device is ready for system integration once commissioning has been effected via the local display or the Class 2 master. The PROFIBUS system requires a description of the device parameters, e.g. output data, input data, data format, data volume and supported transmission rate, so that it can integrate the field devices into the bus system. These data are contained in a Device Master File (GSD file) which is placed at the disposal of the PROFIBUS master while the communication system is being commissioned. Device bitmaps can also be integrated. These appear as icons in the network tree. The Profile 3.0 Device Master File (GSD) allows field devices from various manufacturers to be exchanged without having to reconfigure.
22.3.2 GSD File Types
Prior to configuration, decide which GSD you want to use to operate the system. You can change the setting by means of a Class 2 master (under Physical Block-Parame-
ter Ident_Number_Selector)The following two Device Master Files with different functionalities are available: Manufacturer-specific GSD with Profile 3.0 functionality (default setting): This GSD guarantees the unlimited functionality of the field device. Device-specific pro-
cess parameters and functions are therefore available. Profile GSD's: If a system is configured with profile GSD's, it is possible to exchange devices that are
supplied by various manufacturers. It is, however, essential that the cyclic process values follow the same sequence. The transmitter supports the profiles Analyzer and Multivaria-ble (IEC 61158-2). These GSD's comprise Analog Input blocks (AI)
Working with GSD filesThe GSDs must be integrated into the automation system. Depending on the software that is being used, the GSD files can be copied to the program-specific directory or can be read into the database using the import function within the configuration software.
Tab. 22-8 GSD files for AMI Sodium:
Device name Ident_number_
Selector
ID number GSD Bitmaps
Manufacturer specific GSD with Profile 3.0 functionality:
AMI Sodium 1 17C3Hex SW17C3.gsd SW17C3_D.bmp
SW17C3_N.bmp SW17C3_S.bmp
Profile 3.0 GSD Analyzer:
AMI Sodium 0 9750 Hex PA139750.gsd PA_9750n.bmp
Profile 3.0 GSD Multivariable:
AMI Sodium 3 9760 Hex PA139760.gsd PA_9760n.bmp
152 A-96.250.731 / 140212
ProfibusProduct Specific Data for AMI Soditrace
23. Product Specific Data for AMI Soditrace
23.1. Introduction
The AMI family of transmitters provides a common base for a number of analytical instruments with application specific sensor interfaces. Each instrument has a basic structure with identical functionality.AMI instruments can (optionally) be equipped with a PROFIBUS DP-V1 interface. The interface supports the PROFIBUS-PA Profile 3.0. This part of the manual describes the functionality of the interface and the integration of the AMI family of transmitters into an automation system.
Hardware Wiring, bus terminals and connectors are not part of this manual. It should, however, be noted that the observation of the corresponding standards is of paramount importance to proper operation. Setting the transmission rate to reasonable values will help avoid communication errors.
GSD File forAMI Soditrace
The PROFIBUS system requires a description of the device parameters, e. g. output data, input data, data format, data volume and supported transmission rate, so that it can integrate the field devices into the bus system. These data are contained in a Device Master File (GSD file) which is placed at the disposal of the PROFIBUS master while communication system is being commissioned.
Device bitmaps can also be integrated. These appear as icons in the network tree.The manufacturer-specific GSD file SW17C7.gsd is available for download from http://www.swan.ch
23.2. Cyclic Data Telegram
Input Data The AMI Soditrace makes the following modules available as input data for the cyclic data exchange:
1 Main Process Value (Sodium in ppb)
2 Main Temperature
3 Conductivity in µS
4 Diagnostic Values (5 values)
– Raw value Sodium in mV
– Conductivity Control in %
– Raw Value Conductivity in µS
– Conductivity unfiltered
– Case Temperature in °C
A-96.250.731 / 140212 153
ProfibusProduct Specific Data for AMI Soditrace
The input data is transferred from AMI Soditrace in the following structure:
Output Data The AMI Soditrace makes the following module available as output data for the cyclic data exchange:
1 Control AMI
The control data is transferred to the AMI Soditrace in the following structure:
Tab. 23-1 Input data structure from AMI Soditrace
Index input data Data Access
Data format / comments Configuration data
0–4 Analog Input block 1 Main Process Value
read Measured value (32-bit floating point number) Status byte
0x42, 0x84, 0x08, 0x05 or 0x42, 0x84, 0x81, 0x81 or 0x94
5–9 Analog Input block 2 Main Temperature
read Measured value (32-bit floating point number) Status byte
0x42, 0x84, 0x08, 0x05 or 0x42, 0x84, 0x81, 0x81 or 0x94
10–14 Analog Input block 4 Conductivity
read Measured value (32-bit floating point number) Status byte
0x42, 0x84, 0x08, 0x05 or 0x42, 0x84, 0x81, 0x81 or 0x94
15–34 Diagnostic Values read 4 Measured values (32-bit floating point number)
0x45, 0x93, 0x08, 0x08, 0x08, 0x08, 0x08 or0xD9
Tab. 23-2 Output data structure
Index output data Data Access Data format / comments Configuration data
0–1 Control AMI (SP_D)
write Byte 0Bit 0: Relay 1
0 = open1 = close
0x82, 0x81, 0x05, 0x05 or 0x82, 0x81, 0x84, 0x82 or 0xA1
Bit 1: Relay 20 = open1 = close
Bit 2–7: Not used
Byte 1Bit 0: Hold
Bit 1: Control Off
Bit 2: Start Regeneration
Bit 3: Start Calibration
Bit 4–7: Not used
154 A-96.250.731 / 140212
ProfibusProduct Specific Data for AMI Soditrace
23.2.1 Data Formats
For further information see chapter 1 Data Formats, p. 7
Tab. 23-3 Status Code Byte
7 6 5 4 3 2 1 0
Quality Sub-Status Limits Meaning
0 0 The sub-status has a different quality depending on the coding
bad
0 1 uncertain
1 0 good
0 0 ok
0 1 low limited
1 0 high limited
1 1 constant
Tab. 23-4 Status codes of the measured value
Status
code
Device status Meaning Limits
0x08 BAD Not connected (Temp Sensor not connected)
0x0C BAD device failure
0x10 BAD sensor failure (Temp Sensor Short Circuit)
0x47 UNCERTAIN Last usable value (HOLD) CONST
0x50 UNCERTAIN sensor conversion not accurate (e.g. No Flow) OK
0x64
0x67
UNCERTAIN Sensor calibration Sensor calibration, hold
OK CONST
0x80 GOOD ok OK
0x89
0x8A
GOOD Warning Low Warning High
LOW_LIM HIGH_LIM
0x8D
0x8E
GOOD Alarm Low Alarm High
LOW_LIM HICH_LIM
Tab. 23-5 DP Diagnostics
Byte Description
0 Status 1 Standard DP Diagnostics1 Status 2
2 Status 3
3 Master address
4 Ident number (high byte)
5 Ident number (low byte)
6 Header (block length incl. Header byte) = 14 Status coding accord-ing to DP/V17 Status Type (0x81)
8 Slot Number (0x00)
9 Status Specifier
10–13 Diagnosis
14–19 Diagnosis Extension
A-96.250.731 / 140212 155
ProfibusProduct Specific Data for AMI Soditrace
Tab. 23-6 The diagnosis object consists of 4 Bytes
Byte Bit Meaning when “1” Abbreviation
0 0 Hardware failure electronics DIA_HW_ELECTR
1 Hardware failure mechanics DIA_HW_MECH
2 -
3 Electronic temperature too high DIA_TEMP_ELECTR
4 -
5 Measurement failure DIA_MEASUREMENT
6 -
7 -
1 0 -
1 -
2 -
3 -
4 -
5 Maintenance required DIA_MAINTENANCE
6 -
7 -
2 0 -
1 -
2 -
3 -
4 -
5 -
6 -
7 -
3 0 -
1 -
2 -
3 -
4 -
5 -
6 -
7 Extension Available EXTENSION_AVAILABLE
156 A-96.250.731 / 140212
ProfibusProduct Specific Data for AMI Soditrace
Bytes 4 and 5 are reserved for future extensions.
Tab. 23-7 The diagnosis extension object consists of 6 Bytes.
Byte Bit Meaning when “1” Abbreviation
0 0 Sodium Alarm high
1 Sodium Alarm low
2 Cond. Alarm high
3 Cond. Alarm low
4 No Reagent DIA_MAINTENANCE
5 No Sample DIA_MEASUREMENT
6 Sample Temp. high DIA_MEASUREMENT
7 Sample Temp. low DIA_MEASUREMENT
1 0
1
Temp. shorted DIA_HW_ELECTR
3 Temp. disconnected DIA_HW_ELECTR
4 Case Temp. high DIA_TEMP_ELECTR
5 Case Temp. low DIA_TEMP_ELECTR
6 Reagent high DIA_MEASUREMENT
7
2 0 Control Timeout
1 Sodium Offset DIA_MEASUREMENT
2 Sodium Slope DIA_MEASUREMENT
3 High Background DIA_MEASUREMENT
4 Sodium Stability DIA_MEASUREMENT
5 Regeneration Agent DIA_MAINTENANCE
6
7 Input Active DIA_HW_ELECTR
3 0 IC MK41T56 DIA_HW_ELECTR
1 IC LM75 DIA_HW_ELECTR
2 IC PCF8574 DIA_HW_ELECTR
3 EEprom Microcon DIA_HW_ELECTR
4 EEProm Motherboard DIA_HW_ELECTR
5 EEProm Front-end DIA_HW_ELECTR
6 Cal. Recout DIA_HW_ELECTR
7 Wrong Front-end DIA_HW_ELECTR
A-96.250.731 / 140212 157
ProfibusProduct Specific Data for AMI Soditrace
23.3. Configuration
23.3.1 Device Master Files (GSD)
The device is ready for system integration once commissioning has been effected via the local display or the Class 2 master. The PROFIBUS system requires a description of the device parameters, e.g. output data, input data, data format, data volume and supported transmission rate, so that it can integrate the field devices into the bus system. These data are contained in a Device Master File (GSD file) which is placed at the disposal of the PROFIBUS master while the communication system is being commissioned. Device bitmaps can also be integrated. These appear as icons in the network tree. The Profile 3.0 Device Master File (GSD) allows field devices from various manufacturers to be exchanged without having to reconfigure.
23.3.2 GSD File Types
Prior to configuration, decide which GSD you want to use to operate the system. You can change the setting by means of a Class 2 master (under Physical Block-Parame-
ter Ident_Number_Selector)The following two Device Master Files with different functionalities are available: Manufacturer-specific GSD with Profile 3.0 functionality (default setting): This GSD guarantees the unlimited functionality of the field device. Device-specific pro-
cess parameters and functions are therefore available. Profile GSD's: If a system is configured with profile GSD's, it is possible to exchange devices that are
supplied by various manufacturers. It is, however, essential that the cyclic process values follow the same sequence. The transmitter supports the profiles Analyzer and Multivaria-ble (IEC 61158-2). These GSD's comprise Analog Input blocks (AI)
Working with GSD filesThe GSDs must be integrated into the automation system. Depending on the software that is being used, the GSD files can be copied to the program-specific directory or can be read into the database using the import function within the configuration software.
Tab. 23-8 GSD files for AMI Soditrace:
Device name Ident_number_
Selector
ID number GSD Bitmaps
Manufacturer specific GSD with Profile 3.0 functionality:
AMI Soditrace 1 17C7Hex SW17C7.gsd SW17C7_D.bmp
SW17C7_N.bmp SW17C7_S.bmp
Profile 3.0 GSD Analyzer:
AMI Soditrace 0 9750 Hex PA139750.gsd PA_9750n.bmp
Profile 3.0 GSD Multivariable:
AMI Soditrace 3 9760 Hex PA139760.gsd PA_9760n.bmp
158 A-96.250.731 / 140212
ProfibusProduct Specific Data for AMI Solicon4
24. Product Specific Data for AMI Solicon4
24.1. Introduction
The AMI family of transmitters provides a common base for a number of analytical instruments with application specific sensor interfaces. Each instrument has a basic structure with identical functionality.AMI instruments can (optionally) be equipped with a PROFIBUS DP-V1 interface. The interface supports the PROFIBUS-PA Profile 3.0. This part of the manual describes the functionality of the interface and the integration of the AMI family of transmitters into an automation system.
Hardware Wiring, bus terminals and connectors are not part of this manual. It should, however, be noted that the observation of the corresponding standards is of paramount importance to proper operation. Setting the transmission rate to reasonable values will help avoid communication errors.
GSD File forAMI Solicon4
The PROFIBUS system requires a description of the device parameters, e. g. output data, input data, data format, data volume and supported transmission rate, so that it can integrate the field devices into the bus system. These data are contained in a Device Master File (GSD file) which is placed at the disposal of the PROFIBUS master while communication system is being commissioned.
Device bitmaps can also be integrated. These appear as icons in the network tree.The manufacturer-specific GSD file SW17C2.gsd is available for download from http://www.swan.ch
24.2. Cyclic Data Telegram
Input Data The AMI Solicon4 makes the following modules available as input data for the cyclic data exchange:
1 Main Process Value (µS/cm)
2 Main Temperature
3 Main Flow
4 2nd Process Value (µS/cm)
5 Diagnostic Values (5 values)
– Contamination
– Cell Constant in cm-1
– Cond. Raw Value in µS/cm
– Reserved
– Case Temperature in °C
A-96.250.731 / 150513 159
ProfibusProduct Specific Data for AMI Solicon4
The input data is transferred from AMI Solicon4 in the following structure:
Output Data The AMI Solicon4 makes the following module available as output data for the cyclic data exchange:
1 Control AMI
The control data is transferred to the AMI Solicon4 in the following structure:
Tab. 24-1 Input data structure from AMI Solicon4
Index input data Data Access
Data format / comments Configuration data
0–4 Analog Input block 1 Main Process Value
read Measured value (32-bit floating point number) Status byte
0x42, 0x84, 0x08, 0x05 or 0x42, 0x84, 0x81, 0x81 or 0x94
5–9 Analog Input block 2 Main Temperature
read Measured value (32-bit floating point number) Status byte
0x42, 0x84, 0x08, 0x05 or 0x42, 0x84, 0x81, 0x81 or 0x94
10–14 Analog Input block 3 Main Flow
read Measured value (32-bit floating point number) Status byte
0x42, 0x84, 0x08, 0x05 or 0x42, 0x84, 0x81, 0x81 or 0x94
15–19 Analog Input block 4 2nd Process Value
read 4 Measured values (32-bit floating point number) Status byte
0x42, 0x84, 0x08, 0x05 or 0x42, 0x84, 0x81, 0x81 or 0x94
20–39 Diagnostic Values read 5 Measured values (32-bit floating point number)
0x45, 0x93, 0x08, 0x08, 0x08, 0x08, 0x08 or0xD9
Tab. 24-2 Output data structure
Index output data Data Access Data format / comments Configuration data
0–1 Control AMI (SP_D)
write Byte 0Bit 0: Relay 1
0 = open1 = close
0x82, 0x81, 0x05, 0x05 or 0x82, 0x81, 0x84, 0x82 or 0xA1
Bit 1: Relay 20 = open1 = close
Bit 2–7: Not used
Byte 1Bit 0: Hold
Bit 1: Control Off
Bit 2–7: Not used
160 A-96.250.731 / 150513
ProfibusProduct Specific Data for AMI Solicon4
24.2.1 Data Formats
For further information see chapter 1 Data Formats, p. 7
Tab. 24-3 Status Code Byte
7 6 5 4 3 2 1 0
Quality Sub-Status Limits Meaning
0 0 The sub-status has a different quality depending on the coding
bad
0 1 uncertain
1 0 good
0 0 ok
0 1 low limited
1 0 high limited
1 1 constant
Tab. 24-4 Status codes of the measured value
Status
code
Device status Meaning Limits
0x08 BAD Not connected (Temp Sensor not connected)
0x0C BAD device failure
0x10 BAD sensor failure (Temp Sensor Short Circuit)
0x47 UNCERTAIN Last usable value (HOLD) CONST
0x50 UNCERTAIN sensor conversion not accurate (e.g. No Flow) OK
0x64
0x67
UNCERTAIN Sensor calibration Sensor calibration, hold
OK CONST
0x80 GOOD ok OK
0x89
0x8A
GOOD Warning Low Warning High
LOW_LIM HIGH_LIM
0x8D
0x8E
GOOD Alarm Low Alarm High
LOW_LIM HICH_LIM
Tab. 24-5 DP Diagnostics
Byte Description
0 Status 1 Standard DP Diagnostics1 Status 2
2 Status 3
3 Master address
4 Ident number (high byte)
5 Ident number (low byte)
6 Header (block length incl. Header byte) = 14 Status coding accord-ing to DP/V17 Status Type (0x81)
8 Slot Number (0x00)
9 Status Specifier
10–13 Diagnosis
14–19 Diagnosis Extension
A-96.250.731 / 150513 161
ProfibusProduct Specific Data for AMI Solicon4
Tab. 24-6 The diagnosis object consists of 4 Bytes
Byte Bit Meaning when “1” Abbreviation
0 0 Hardware failure electronics DIA_HW_ELECTR
1 Hardware failure mechanics DIA_HW_MECH
2 -
3 Electronic temperature too high DIA_TEMP_ELECTR
4 -
5 Measurement failure DIA_MEASUREMENT
6 -
7 -
1 0 -
1 -
2 -
3 -
4 -
5 Maintenance required DIA_MAINTENANCE
6 -
7 -
2 0 -
1 -
2 -
3 -
4 -
5 -
6 -
7 -
3 0 -
1 -
2 -
3 -
4 -
5 -
6 -
7 Extension Available EXTENSION_AVAILABLE
162 A-96.250.731 / 150513
ProfibusProduct Specific Data for AMI Solicon4
Byte 5 is reserved for future extensions.
Tab. 24-7 The diagnosis extension object consists of 4 Bytes.
Byte Bit Meaning when “1” Abbreviation
0 0
1
2
3
4
5
6
7
1 0 Sample Flow high DIA_MEASUREMENT
1 Sample Flow low DIA_MEASUREMENT
Temp. shorted DIA_HW_ELECTR
3 Temp. disconnected DIA_HW_ELECTR
4 Case Temp. high DIA_TEMP_ELECTR
5 Case Temp. low DIA_TEMP_ELECTR
6
7
2 0 Control Timeout
1 Temp. out of table DIA_MEASUREMENT
2 Conc. out of table DIA_MEASUREMENT
3
4
5
6
7 Input Active DIA_HW_ELECTR
3 0 IC MK41T56 DIA_HW_ELECTR
1 IC LM75 DIA_HW_ELECTR
2 IC PCF8574 DIA_HW_ELECTR
3 EEprom Microcon DIA_HW_ELECTR
4 EEProm Motherboard DIA_HW_ELECTR
5 EEProm Front-end DIA_HW_ELECTR
6 Cal. Recout DIA_HW_ELECTR
7 Wrong Front-end DIA_HW_ELECTR
A-96.250.731 / 150513 163
ProfibusProduct Specific Data for AMI Solicon4
24.3. Configuration
24.3.1 Device Master Files (GSD)
The device is ready for system integration once commissioning has been effected via the local display or the Class 2 master. The PROFIBUS system requires a description of the device parameters, e.g. output data, input data, data format, data volume and supported transmission rate, so that it can integrate the field devices into the bus system. These data are contained in a Device Master File (GSD file) which is placed at the disposal of the PROFIBUS master while the communication system is being commissioned. Device bitmaps can also be integrated. These appear as icons in the network tree. The Profile 3.0 Device Master File (GSD) allows field devices from various manufacturers to be exchanged without having to reconfigure.
24.3.2 GSD File Types
Prior to configuration, decide which GSD you want to use to operate the system. You can change the setting by means of a Class 2 master (under Physical Block-Parame-
ter Ident_Number_Selector)The following two Device Master Files with different functionalities are available: Manufacturer-specific GSD with Profile 3.0 functionality (default setting): This GSD guarantees the unlimited functionality of the field device. Device-specific pro-
cess parameters and functions are therefore available. Profile GSD's: If a system is configured with profile GSD's, it is possible to exchange devices that are
supplied by various manufacturers. It is, however, essential that the cyclic process values follow the same sequence. The transmitter supports the profiles Analyzer and Multivaria-ble (IEC 61158-2). These GSD's comprise Analog Input blocks (AI)
Working with GSD filesThe GSDs must be integrated into the automation system. Depending on the software that is being used, the GSD files can be copied to the program-specific directory or can be read into the database using the import function within the configuration software.
Tab. 24-8 GSD files for AMI Solicon4:
Device name Ident_number_
Selector
ID number GSD Bitmaps
Manufacturer specific GSD with Profile 3.0 functionality:
AMI Solicon4 1 17C2Hex SW17C2.gsd SW17C2_D.bmp
SW17C2_N.bmp SW17C2_S.bmp
Profile 3.0 GSD Analyzer:
AMI Solicon4 0 9750 Hex PA139750.gsd PA_9750n.bmp
Profile 3.0 GSD Multivariable:
AMI Solicon4 3 9760 Hex PA139760.gsd PA_9760n.bmp
164 A-96.250.731 / 150513
ProfibusProduct Specific Data for AMI Trides
25. Product Specific Data for AMI Trides
25.1. Introduction
The AMI family of transmitters provides a common base for a number of analytical instruments with application specific sensor interfaces. Each instrument has a basic structure with identical functionality.AMI instruments can (optionally) be equipped with a PROFIBUS DP-V1 interface. The interface supports the PROFIBUS-PA Profile 3.0. This part of the manual describes the functionality of the interface and the integration of the AMI family of transmitters into an automation system.
Hardware Wiring, bus terminals and connectors are not part of this manual. It should, however, be noted that the observation of the corresponding standards is of paramount importance to proper operation. Setting the transmission rate to reasonable values will help avoid communication errors.
GSD File forAMI Trides
The PROFIBUS system requires a description of the device parameters, e. g. output data, input data, data format, data volume and supported transmission rate, so that it can integrate the field devices into the bus system. These data are contained in a Device Master File (GSD file) which is placed at the disposal of the PROFIBUS master while communication system is being commissioned.
Device bitmaps can also be integrated. These appear as icons in the network tree.The manufacturer-specific GSD file SW17C0.gsd is available for download from http://www.swan.ch
25.2. Cyclic Data Telegram
Input Data The AMI Trides makes the following modules available as input data for the cyclic data exchange:
1 Main Process Value (Disinfection)
2 Main Temperature
3 Main Flow
4 2nd Process Value (pH/Redox)
5 Diagnostic Values (5 Values)
– Raw value Disinfection in µA
– Counter Electrode Voltage in mV
– Raw Value pH/Redox in mV
– HoCL in ppm
– Case Temperature in °C
A-96.250.731 / 140212 165
ProfibusProduct Specific Data for AMI Trides
The input data is transferred from AMI Trides in the following structure:
Output Data The AMI Trides makes the following module available as output data for the cyclic data exchange:
1 Control AMI
The control data is transferred to the AMI Trides in the following structure:
Tab. 25-1 Input data structure of AMI Trides
Index input data Data Access
Data format / comments Configuration data
0–4 Analog Input block 1 Main Process Value
read Measured value (32-bit floating point number) Status byte
0x42, 0x84, 0x08, 0x05 or 0x42, 0x84, 0x81, 0x81 or 0x94
5–9 Analog Input block 2 Main Temperature
read Measured value (32-bit floating point number) Status byte
0x42, 0x84, 0x08, 0x05 or 0x42, 0x84, 0x81, 0x81 or 0x94
10–14 Analog Input block 3 Main Flow
read Measured value (32-bit floating point number) Status byte
0x42, 0x84, 0x08, 0x05 or 0x42, 0x84, 0x81, 0x81 or 0x94
15–19 Analog Input block 42nd Process Value
read Measured value (32-bit floating point number) Status byte
0x42, 0x84, 0x08, 0x05 or 0x42, 0x84, 0x81, 0x81 or 0x94
20–39 Diagnostic Values read 5 Measured values (32-bit floating point number)
0x45, 0x93, 0x08, 0x08, 0x08, 0x08, 0x080xD9
Tab. 25-2 Output data structure
Index output data Data Access Data format / comments Configuration data
0–1 Control AMI
(SP_D)
write Byte 0Bit 0: Relay 1
0 = open1 = close
0x82, 0x81, 0x05, 0x05 or 0x82, 0x81, 0x84, 0x82 or 0xA1
Bit 1: Relay 2 0 = open1 = close
Bit 2–7: not used
Byte 1Bit 0: Hold
Bit 1: Control Off
Bit 2–7: not used
166 A-96.250.731 / 140212
ProfibusProduct Specific Data for AMI Trides
25.2.1 Data Formats
For further information see chapter 1 Data Formats, p. 7
Tab. 25-3 Status Code Byte
7 6 5 4 3 2 1 0
Quality Sub-Status Limits Meaning
0 0 The sub-status has a different quality depending on the coding
bad
0 1 uncertain
1 0 good
0 0 ok
0 1 low limited
1 0 high limited
1 1 constant
Tab. 25-4 Status codes of the measured value
Status
code
Device status Meaning Limits
0x08 BAD Not connected (Temp Sensor not connected)
0x0C BAD device failure
0x10 BAD sensor failure (Temp Sensor Short Circuit)
0x47 UNCERTAIN Last usable value (HOLD) CONST
0x50 UNCERTAIN sensor conversion not accurate (e.g. No Flow) OK
0x64
0x67
UNCERTAIN Sensor calibration Sensor calibration, hold
OK CONST
0x80 GOOD ok OK
0x89
0x8A
GOOD Warning Low Warning High
LOW_LIM HIGH_LIM
0x8D
0x8E
GOOD Alarm Low Alarm High
LOW_LIM HICH_LIM
Tab. 25-5 DP Diagnostics
Byte Description
0 Status 1 Standard DP Diagnostics1 Status 2
2 Status 3
3 Master address
4 Ident number (high byte)
5 Ident number (low byte)
6 Header (block length incl. Header byte) = 14 Status coding accord-ing to DP/V17 Status Type (0x81)
8 Slot Number (0x00)
9 Status Specifier
10–13 Diagnosis
14–19 Diagnosis Extension
A-96.250.731 / 140212 167
ProfibusProduct Specific Data for AMI Trides
Tab. 25-6 The diagnosis object consists of 4 Bytes
Byte Bit Meaning when “1” Abbreviation
0 0 Hardware failure electronics DIA_HW_ELECTR
1 Hardware failure mechanics DIA_HW_MECH
2 -
3 Electronic temperature too high DIA_TEMP_ELECTR
4 -
5 Measurement failure DIA_MEASUREMENT
6 -
7 -
1 0 -
1 -
2 -
3 -
4 -
5 Maintenance required DIA_MAINTENANCE
6 -
7 -
2 0 -
1 -
2 -
3 -
4 -
5 -
6 -
7 -
3 0 -
1 -
2 -
3 -
4 -
5 -
6 -
7 Extension Available EXTENSION_AVAILABLE
168 A-96.250.731 / 140212
ProfibusProduct Specific Data for AMI Trides
Bytes 4 and 5 are reserved for future extensions.
Tab. 25-7 The diagnosis extension object consists of 6 Bytes.
Byte Bit Meaning when “1” Abbreviation
0 0 DIS. Alarm high -
1 DIS. Alarm low -
2 pH/Redox Alarm high -
3 pH/Redox Alarm low -
4 -
5 -
6 Sample Temp. high DIA_MEASUREMENT
7 Sample Temp. low DIA_MEASUREMENT
1 0 Sample Flow high DIA_MEASUREMENT
1 Sample Flow low DIA_MEASUREMENT
2 Temp. shorted DIA_HW_ELECTR
3 Temp. disconnected DIA_HW_ELECTR
4 Case Temp. high DIA_TEMP_ELECTR
5 Case Temp. low DIA_TEMP_ELECTR
6 TRIDES Reference DIA_MEASUREMENT
7
2 0 Control Timeout -
1
2
3
4
5
6 Cleaning Ragent DIA_MAINTENANCE
7 Input Active DIA_HW_ELECTR
3 0 IC MK41T56 DIA_HW_ELECTR
1 IC LM75 DIA_HW_ELECTR
2 IC PCF8574 DIA_HW_ELECTR
3 EEprom Microcon DIA_HW_ELECTR
4 EEProm Motherboard DIA_HW_ELECTR
5 EEProm Frontend DIA_HW_ELECTR
6 Cal. Recout DIA_HW_ELECTR
7 Wrong Frontend DIA_HW_ELECTR
A-96.250.731 / 140212 169
ProfibusProduct Specific Data for AMI Trides
25.3. Configuration
25.3.1 Device Master Files (GSD)
The device is ready for system integration once commissioning has been effected via the local display or the Class 2 master. The PROFIBUS system requires a description of the device parameters, e.g. output data, input data, data format, data volume and supported transmission rate, so that it can integrate the field devices into the bus system. These data are contained in a Device Master File (GSD file) which is placed at the disposal of the PROFIBUS master while the communication system is being commissioned. Device bitmaps can also be integrated. These appear as icons in the network tree.The Profile 3.0 Device Master File (GSD) allows field devices from various manufacturers to be exchanged without having to reconfigure.
25.3.2 GSD File Types
Prior to configuration, decide which GSD you want to use to operate the system.You can change the setting by means of a Class 2 master (under Physical Block-Parameter Ident_Number_Selector)The following two Device Master Files with different functionalities are available:Manufacturer-specific GSD with Profile 3.0 functionality (default setting):This GSD guarantees the unlimited functionality of the field device. Device-specific process parameters and functions are therefore available.Profile GSD's:If a system is configured with profile GSD's, it is possible to exchange devices that are supplied by various manufacturers. It is, however, essential that the cyclic process values follow the same sequence. The transmitter supports the profiles Analyzer and Multivariable (IEC 61158-2). These GSD's comprise Analog Input blocks (AI).
Working with GSD filesThe GSDs must be integrated into the automation system. Depending on the software that is being used, the GSD files can be copied to the program-specific directory or can be read into the database using the import function within the configuration software.
Tab. 25-8 GSD files for AMI Trides
Device name Ident_number_
Selector
ID number GSD Bitmaps
Manufacturer specific GSD with Profile 3.0 functionality:
AMI Trides 1 17C0Hex SW17C0.gsd SW17C0_D.bmp
SW17C0_N.bmp SW17C0_S.bmp
Profile 3.0 GSD Analyzer:
AMI Trides 0 9750 Hex PA039750.gsd PA_9750n.bmp
Profile 3.0 GSD Multivariable:
AMI Trides 3 9760 Hex PA039760.gsd PA_9760n.bmp
170 A-96.250.731 / 140212
ProfibusProduct Specific Data for Turbidity
26. Product Specific Data for Turbidity
26.1. Introduction
This description applies for the AMI Turbiwell, AMI Turbitrace and AMI Turbitrack.The AMI Turbiwell, Turbitrace and Turbitrack are Nephelometric systems for the automatic and continuous measurement of turbidity in water.The AMI family of transmitters provides a common base for a number of analytical instruments with application specific sensor interfaces. Each instrument has a basic structure with identical functionality.AMI instruments can (optionally) be equipped with a PROFIBUS DP-V1 interface. The interface supports the PROFIBUS-PA Profile 3.0. This part of the manual describes the functionality of the interface and the integration of the AMI family of transmitters into an automation system.
Hardware Wiring, bus terminals and connectors are not part of this manual. It should, however, be noted that the observation of the corresponding standards is of paramount importance to proper operation. Setting the transmission rate to reasonable values will help avoid communication errors.
GSD File forAMI Turbiwell
The PROFIBUS system requires a description of the device parameters, e. g. output data, input data, data format, data volume and supported transmission rate, so that it can integrate the field devices into the bus system. These data are contained in a Device Master File (GSD file) which is placed at the disposal of the PROFIBUS master while communication system is being commissioned.
Device bitmaps can also be integrated. These appear as icons in the network tree.The manufacturer-specific GSD file SW17C5.gsd is available for download from http://www.swan.ch
26.2. Cyclic Data Telegram
Input Data The AMI Turbiwell, Turbitrace and Turbitrack make the following modules available as input data for the cyclic data exchange:
1 Main Process Value (Turbidity in FNU)
2 Main Temperature (fix @ 25°C, for future expansion)
3 Main Flow (l/h)
4 Control AMI
5 Diagnostic Values (5 Values)
– Raw Value
– Quotient
– V-Signal
– V-Ref
– Case Temperature in °C
A-96.250.731 / 240915 171
ProfibusProduct Specific Data for Turbidity
The input data is transferred from AMI Turbiwell, Turbitrace and Turbitrack in the following structure:
Output Data The AMI Turbiwell, Turbitrace and Turbitrack make the following module available as output data for the cyclic data exchange:
1 Control AMI
The control data is transferred to the AMI Turbiwell, Turbitrace and Turbitrack in the following structure:
1) To start a calibration, set this bit to "1" for 5 seconds, then reset to "0”
Tab. 26-1 Input data structure of AMI Turbiwell, Turbitrace and Trubitrack
Index input data Data Access
Data format / comments Configuration data
0–4 Analog Input block 1 Main Process Value
read Measured value (32-bit floating point number) Status byte
0x42, 0x84, 0x08, 0x05 or 0x42, 0x84, 0x81, 0x81 or 0x94
5–9 Analog Input block 2 Main Temperature
read Measured value (32-bit floating point number) Status byte
0x42, 0x84, 0x08, 0x05 or 0x42, 0x84, 0x81, 0x81 or 0x94
10–14 Analog Input block 3 Main Flow
read Measured value (32-bit floating point number) Status byte
0x42, 0x84, 0x08, 0x05 or 0x42, 0x84, 0x81, 0x81 or 0x94
15–34 Diagnostic Values read 5 Measured values (32-bit floating point number)
0x45, 0x93, 0x08, 0x08, 0x08, 0x08, 0x080xD9
Tab. 26-2 Output data structure
Index output data Data Access Data format / comments Configuration data
0–1 Control AMI
(SP_D)
write Byte 0Bit 0: Relay 1
0 = open; 1 = close
0x82, 0x81, 0x05, 0x05 or 0x82, 0x81, 0x84, 0x82 or 0xA1
Bit 1: Relay 2 0 = open; 1 = close
Bit 2–7: not used
Byte 1Bit 0: Hold
Bit 1: Control Off
Bit 2: Start Calibration 1)
Bit 3–7: not used
172 A-96.250.731 / 240915
ProfibusProduct Specific Data for Turbidity
26.2.1 Data Formats
For further information see chapter 1 Data Formats, p. 7
Tab. 26-3 Status Code Byte
7 6 5 4 3 2 1 0
Quality Sub-Status Limits Meaning
0 0 The sub-status has a different quality depending on the coding
bad
0 1 uncertain
1 0 good
0 0 ok
0 1 low limited
1 0 high limited
1 1 constant
Tab. 26-4 Status codes of the measured value
Status
code
Device status Meaning Limits
0x08 BAD Not connected (Temp Sensor not connected)
0x0C BAD device failure
0x10 BAD sensor failure (Temp Sensor Short Circuit)
0x47 UNCERTAIN Last usable value (HOLD) CONST
0x50 UNCERTAIN sensor conversion not accurate (e.g. No Flow) OK
0x64
0x67
UNCERTAIN Sensor calibration Sensor calibration, hold
OK CONST
0x80 GOOD ok OK
0x89
0x8A
GOOD Warning Low Warning High
LOW_LIM HIGH_LIM
0x8D
0x8E
GOOD Alarm Low Alarm High
LOW_LIM HIGH_LIM
Tab. 26-5 DP Diagnostics
Byte Description
0 Status 1 Standard DP Diagnostics1 Status 2
2 Status 3
3 Master address
4 Ident number (high byte)
5 Ident number (low byte)
6 Header (block length incl. Header byte) = 14 Status coding accord-ing to DP/V17 Status Type (0x81)
8 Slot Number (0x00)
9 Status Specifier
10–13 Diagnosis
14–19 Diagnosis Extension
A-96.250.731 / 240915 173
ProfibusProduct Specific Data for Turbidity
Tab. 26-6 The diagnosis object consists of 4 Bytes
Byte Bit Meaning when “1” Abbreviation
0 0 Hardware failure electronics DIA_HW_ELECTR
1 Hardware failure mechanics DIA_HW_MECH
2 -
3 Electronic temperature too high DIA_TEMP_ELECTR
4 -
5 Measurement failure DIA_MEASUREMENT
6 -
7 -
1 0 -
1 -
2 -
3 -
4 -
5 Maintenance required DIA_MAINTENANCE
6 -
7 -
2 0 -
1 -
2 -
3 -
4 -
5 -
6 -
7 -
3 0 -
1 -
2 -
3 -
4 -
5 -
6 -
7 Extension Available EXTENSION_AVAILABLE
174 A-96.250.731 / 240915
ProfibusProduct Specific Data for Turbidity
Byte 5 is reserved for future extensions.
Tab. 26-7 The diagnosis extension object consists of 6 Bytes.
Byte Bit Meaning when “1” Abbreviation
0 0 - -
1 - -
2 - -
3 - -
4 - -
5 - -
6 - -
7 - -
1 0 Sample Flow high DIA_MEASUREMENT
1 Sample Flow low DIA_MEASUREMENT
2 Temp. shorted (not implemented) DIA_HW_ELECTR
3 Temp. disconnected (not implemented) DIA_HW_ELECTR
4 Case Temp. high DIA_TEMP_ELECTR
5 Case Temp. low DIA_TEMP_ELECTR
6 - -
7 Zero Offset too high DIA_MEASUREMENT
2 0 Control Timeout -
1 Turbi disconnected DIA_HW_ELECTR
2 Turbi overflow DIA_MEASUREMENT
3 Lamp off DIA_HW_ELECTR
4 EEProm Turbi DIA_HW_ELECTR
5 - -
6 Cleaning Reagent DIA_MAINTENANCE
7 Input Active DIA_HW_ELECTR
3 0 IC MK41T56 DIA_HW_ELECTR
1 IC LM75 DIA_HW_ELECTR
2 IC PCF8574 DIA_HW_ELECTR
3 Signal output open DIA_HW_ELECTR
4 EEProm Motherboard DIA_HW_ELECTR
5 EEProm Front-end DIA_HW_ELECTR
6 Cal. Recout DIA_HW_ELECTR
7 Wrong Front-end DIA_HW_ELECTR
4 0 Photometer dirty DIA_MAINTENANCE
1 Filter congested DIA_MAINTENANCE
2 Check humidity absorber DIA_MAINTENANCE
3 - -
4 - -
5 - -
6 - -
7 - -
A-96.250.731 / 240915 175
ProfibusProduct Specific Data for Turbidity
26.3. Configuration
26.3.1 Device Master Files (GSD)
The device is ready for system integration once commissioning has been effected via the local display or the Class 2 master. The PROFIBUS system requires a description of the device parameters, e.g. output data, input data, data format, data volume and supported transmission rate, so that it can integrate the field devices into the bus system. These data are contained in a Device Master File (GSD file) which is placed at the disposal of the PROFIBUS master while the communication system is being commissioned. Device bitmaps can also be integrated. These appear as icons in the network tree.The Profile 3.0 Device Master File (GSD) allows field devices from various manufacturers to be exchanged without having to reconfigure.
26.3.2 GSD File Types
Prior to configuration, decide which GSD you want to use to operate the system. You can change the setting by means of a Class 2 master (under Physical Block-Parame-
ter Ident_Number_Selector)
The following two Device Master Files with different functionalities are available: Manufacturer-specific GSD with Profile 3.0 functionality (default setting):
This GSD guarantees the unlimited functionality of the field device. Device-specific pro-cess parameters and functions are therefore available.
Profile GSD's:If a system is configured with profile GSD's, it is possible to exchange devices that are supplied by various manufacturers. It is, however, essential that the cyclic process values follow the same sequence. The transmitter supports the profiles Analyzer and Multivaria-ble (IEC 61158-2). These GSD's comprise Analog Input blocks (AI).
Working with GSD filesThe GSDs must be integrated into the automation system. Depending on the software that is being used, the GSD files can be copied to the program-specific directory or can be read into the database using the import function within the configuration software.
Tab. 26-8 GSD files for AMI Turbiwell:
Device name Ident_number_
Selector
ID number GSD Bitmaps
Manufacturer specific GSD with Profile 3.0 functionality:
AMI Turbiwell 1 17C5Hex SW17C5.gsd SW17C5_D.bmp
SW17C5_N.bmp SW17C5_S.bmp
Profile 3.0 GSD Analyzer:
AMI Turbiwell 0 9750 Hex PA039750.gsd PA_9750n.bmp
Profile 3.0 GSD Multivariable:
AMI Turbiwell 3 9760 Hex PA039760.gsd PA_9760n.bmp
176 A-96.250.731 / 240915