menami pb 06 · 2019. 9. 19. · gsd file the profibus system requires a description of the device...

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 HinwilSwitzerlandInternet: www.swan.chE-mail: [email protected]

Document Status

Title: AMI PROFIBUS Operator’s Manual

ID: A-96.250.731Revision Issue00 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


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

http://www.swan.chhttp://www.swan.ch


1.1. Cyclic Data TelegramThe 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 TelegramYou 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 FormatsEach 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


Status Byte Details

1.4. Information at Transmitter LevelInformation 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 0Quality 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

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

8 A-96.250.731 / 140212


1.4.1 Status InformationMeaning of status

informationThe 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


1.4.2 ConfigurationDevice 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 CommunicationAcyclic 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


1.5. Application ExampleThe 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 inputB Data base containing the Measuring valuesC Process values Byte 1–4, see Table 1-1 on page 8D 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


1.6. OperationNormally 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 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 /

2 Select 3 Press

4 Select 5 Press

6 Select 7 Press

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


ID ManufacturerLocal Operation Enabled

Enabled

Local OperationDisabled

5.5.1Interface


ID ManufacturerLocal Operation Disabled

No

Save ?Yes

12 A-96.250.731 / 140212


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


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. 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.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 TelegramInput 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 Temperature3 Main Flow4 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

http://www.swan.chhttp://www.swan.chhttp://www.swan.chhttp://www.swan.ch


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


0x42, 0x84, 0x08, 0x05 or 0x42, 0x84, 0x81, 0x81 or 0x94

10–14 Analog Input block 3 Main Flow


0x42, 0x84, 0x08, 0x05 or 0x42, 0x84, 0x81, 0x81 or 0x94

15–19 Analog Input block 4 2nd Process Value


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 data0–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 2–7: not used

Byte 1 Bit 0: Hold

Bit 1: Control Off

Bit 2–7: not used

16 A-96.250.731 / 070813


2.2.1 Data FormatsFor further information see chapter 1 Data Formats, p. 7

Tab. 2-3 Status Code Byte



bad

0 1 uncertain

1 0 good

0 0 ok

0 1 low limited

1 0 high limited

1 1 constant


Status code







0x640x67


OK CONST

0x80 GOOD ok OK

0x890x8A


LOW_LIM HIGH_LIM

0x8D0x8E


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


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


Byte 5 is reserved for future extensions.

Tab. 2-7 The diagnosis extension object consists of 6 Bytes.

Byte Bit Meaning when “1” Abbreviation0 0 -

1 -2

3

4 DIS. high DIA_MEASUREMENT5

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 defective DIA_MEASUREMENT7 - -

2 0 Control Timeout -1 Reagent Pump DIA_MAINTENANCE2 Photometer not connected DIA_MAINTENANCE3 Photometer dirty DIA_MAINTENANCE4 DIS. invalid DIA_MEASUREMENT5 Reagent Empty DIA_MAINTENANCE6 Cleaning Reagent 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 Reagent low DIA_MAINTENANCE1 - -2 - -3 - -4 - -5 - -6 - -7 - -

A-96.250.731 / 070813 19


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



GSD File for AMICodes II CC


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 Temperature8 Flow9 ph Value10 Diagnostic Values (3 values)

– Remaining DPD / Buffer– Remaining Potassium / Iodide– Remaining Cleaning Solution

A-96.250.731 / 150513 21



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



0–4 Analog Input block 1 Free available chlo-rine


0x42, 0x84, 0x08, 0x05 or 0x42, 0x84, 0x81, 0x81 or 0x94

5–9 Analog Input block 2 Total chlorine 1


0x42, 0x84, 0x08, 0x05 or 0x42, 0x84, 0x81, 0x81 or 0x94



0x42, 0x84, 0x08, 0x05 or 0x42, 0x84, 0x81, 0x81 or 0x94

15–19 Analog Input block 4 Calculated mono-chloramine


0x42, 0x84, 0x08, 0x05 or 0x42, 0x84, 0x81, 0x81 or 0x94

20–24 Analog Input block 5 Calculated com-bined chlorine


0x42, 0x84, 0x08, 0x05 or 0x42, 0x84, 0x81, 0x81 or 0x94

25–29 Analog Input block 6 Calculated dichlora-mine


0x42, 0x84, 0x08, 0x05 or 0x42, 0x84, 0x81, 0x81 or 0x94

30–34 Analog Input block 7Temperature


0x42, 0x84, 0x08, 0x05 or 0x42, 0x84, 0x81, 0x81 or 0x94

35–39 Analog Input block 8Flow


0x42, 0x84, 0x08, 0x05 or 0x42, 0x84, 0x81, 0x81 or 0x94

40–44 Analog Input block 9pH Value


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


Output Data The AMI Codes II CC makes the following module available as output data for the cyclic data exchange:

1 Control AMIThe control data is transferred to the AMI Codes II CC in the following structure:




(SP_D)write Byte 0


0x82, 0x81, 0x05, 0x05 or 0x82, 0x81, 0x84, 0x82 or 0xA1


Bit 2–7: not used

Byte 1Bit 0:

Hold

Bit 1: Control Off

Bit 2–7: not used


7 6 5 4 3 2 1 0

Quality Sub-Status Limits Meaning


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



Status code


0x08 BAD Not connected (e.g. Temp Sensor not connected)


0x10 BAD Sensor failure (e.g. Temp Sensor Short Circuit)

0x40 UNCERTAIN e.g. because of Temp Sensor Error CONST


0x4B UNCERTAIN Substitute set CONST

0x4F UNCERTAIN Initial value CONST

0x50 UNCERTAIN Sensor conversion not accurate(e.g. No Flow)

OK

0x640x67


OK CONST

0x80 GOOD ok OK

0x890x8A


LOW_LIM HIGH_LIM

0x8D0x8E


LOW_LIM HICH_LIM


Byte Description

0 Status 1 Standard DP Diag-nostics

1 Status 2

2 Status 3

3 Master address



6 Header (block length incl. Header byte) = 14 Status coding according to DP/V1

7 Status Type (0x81)


9 Status Specifier

10–13 Diagnosis


24 A-96.250.731 / 150513






2 -


4 -


6 -

7 -

1 0 -

1 -

2 -

3 -

4 -


6 -

7 -

2 0 -

1 -

2 -

3 -

4 -

5 -

6 -

7 -

3 0 -

1 -

2 -

3 -

4 -

5 -

6 -


A-96.250.731 / 150513 25



Byte Bit Meaning when “1” Abbreviation0 0

1234567

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


4 0 -1 -2 -3 -4 -5 -6 -7 -

5 0 DPD / Buffer DIA_MAINTENANCE1 Potassium Iodide DIA_MAINTENANCE2 Cleaning Solution DIA_MAINTENANCE 34567

26 A-96.250.731 / 150513


3.3. Configuration




Tab. 3-8 GSD files for AMI Codes II CC:




AMI Codes II CC 1 17CAHex SW17CA.gsd

SW17-CA_D.bmp SW17-CA_N.bmp SW17CA_S.bmp


AMI Codes II CC 0 9750 Hex PA139750.gsd PA_9750n.bmp


AMI Codes II CC 3 9760 Hex PA139760.gsd PA_9760n.bmp

A-96.250.731 / 150513 27


28 A-96.250.731 / 150513

ProfibusProduct Specific Data for AMI Codes II TC

4. Product Specific Data for AMI Codes II TC



GSD File for AMICodes II TC


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 Temperature5 Flow6 pH Value7 Diagnostic Values (5 Values)

– Absorbance– Remaining DPD / Buffer– Remaining Cleaning Solution– pH in mV– Case Temperature

A-96.250.731 / 140212 29



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 AMIThe control data is transferred to the AMI Codes II TC in the following structure


Tab. 4-1 Input data structure of AMI Codes II TCIndex input data Data Access




0x42, 0x84, 0x08, 0x05 or 0x42, 0x84, 0x81, 0x81 or 0x94



0x42, 0x84, 0x08, 0x05 or 0x42, 0x84, 0x81, 0x81 or 0x94

10–14 Analog Input block 3 Calculated dichlora-mine


0x42, 0x84, 0x08, 0x05 or 0x42, 0x84, 0x81, 0x81 or 0x94

15–19 Analog Input block 4 Temperature


0x42, 0x84, 0x08, 0x05 or 0x42, 0x84, 0x81, 0x81 or 0x94

20–24 Analog Input block 5 Flow


0x42, 0x84, 0x08, 0x05 or 0x42, 0x84, 0x81, 0x81 or 0x94

25–29 Analog Input block 6 pH Value


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 0


0x82, 0x81, 0x05, 0x05 or 0x82, 0x81, 0x84, 0x82 or 0xA1


Bit 2–7: not usedByte 1Bit 0:

Hold

Bit 1: Control OffBit 2–7: not used

30 A-96.250.731 / 140212





bad

0 1 uncertain

1 0 good

0 0 ok

0 1 low limited

1 0 high limited

1 1 constant


Status code







0x640x67


OK CONST

0x80 GOOD ok OK

0x890x8A


LOW_LIM HIGH_LIM

0x8D0x8E


LOW_LIM HICH_LIM


Byte Description

0 Status 1 Standard DP Diagnostics1 Status 2

2 Status 3

3 Master address





9 Status Specifier

10–13 Diagnosis


A-96.250.731 / 140212 31






2 -


4 -


6 -

7 -

1 0 -

1 -

2 -

3 -

4 -


6 -

7 -

2 0 -

1 -

2 -

3 -

4 -

5 -

6 -

7 -

3 0 -

1 -

2 -

3 -

4 -

5 -

6 -


32 A-96.250.731 / 140212



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


4 0 Alarm high pH -1 Alarm low pH -234567

5 0 DPD / Buffer DIA_MAINTENANCE12 Cleaning Solution DIA_MAINTENANCE 3 - -4 - -5 - -6 - -7 - -

A-96.250.731 / 140212 33


4.3. Configuration




Tab. 4-8 GSD files for AMI Codes II TC:




AMI Codes II TC 1 17CBHex SW17CB.gsd SW17CB_D.bmp SW17CB_N.bmp SW17CB_S.bmp


AMI Codes II TC 0 9750 Hex PA139750.gsd PA_9750n.bmp


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


GSD File forAMI Deltacon


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 TelegramInput 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 Conductivity2 2nd Process Value (cc) in µS/cm : Cation Conductivity3 3rd Process Value (dc) in µS/cm : Degassed Conductivity4 1st Temperature in °C5 2nd Temperature in °C6 3rd Temperature in °C7 Main Flow in l/h8 1st Calculated Value (pH)9 2nd Calculated Value (Ammonium) in ppm10 Diagnostic Values (4 values)

– Case Temperature in °C– Remaining Resin in %– Degasser Temperature– Degasser Line Voltage

A-96.250.731 / 140212 35



The input data is transferred from AMI Deltacon in the following structure:

Tab. 5-1 Input data structure of AMI Deltacon



0–4 Analog Input block 1 1st Process Value


0x42, 0x84, 0x08, 0x05 or 0x42, 0x84, 0x81, 0x81 or 0x94

5–9 Analog Input block 2 2nd Process Value


0x42, 0x84, 0x08, 0x05 or 0x42, 0x84, 0x81, 0x81 or 0x94

10–14 Analog Input block 3 3rd Process Value


0x42, 0x84, 0x08, 0x05 or 0x42, 0x84, 0x81, 0x81 or 0x94

15–19 Analog Input block 4 1st Temperature


0x42, 0x84, 0x08, 0x05 or 0x42, 0x84, 0x81, 0x81 or 0x94

20–24 Analog Input block 5 2nd Temperature


0x42, 0x84, 0x08, 0x05 or 0x42, 0x84, 0x81, 0x81 or 0x94

25–29 Analog Input block 6 3rd Temperature


0x42, 0x84, 0x08, 0x05 or 0x42, 0x84, 0x81, 0x81 or 0x94

30–34 Analog Input block 7 Main Flow in l/h


0x42, 0x84, 0x08, 0x05 or 0x42, 0x84, 0x81, 0x81 or 0x94

35–39 Analog Input block 8 1st Calc. Value (pH)


0x42, 0x84, 0x08, 0x05 or 0x42, 0x84, 0x81, 0x81 or 0x94

40–44 Analog Input block 9 2nd Calc. Value (Ammonium)


0x42, 0x84, 0x08, 0x05 or 0x42, 0x84, 0x81, 0x81 or 0x94


0x44, 0x8F, 0x08, 0x08, 0x08, 0x080x9F

36 A-96.250.731 / 140212


Output Data The AMI Deltacon makes the following module available as output data for the cyclic data exchange:

1 Control AMIThe control data is transferred to the AMI Deltacon in the following structure:




(SP_D)write Byte 0

Bit 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


7 6 5 4 3 2 1 0

Quality Sub-Status Limits Meaning


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



Status code







OK

0x640x67


OK CONST

0x80 GOOD ok OK

0x890x8A


LOW_LIM HIGH_LIM

0x8D0x8E


LOW_LIM HICH_LIM


Byte Description


2 Status 3

3 Master address





9 Status Specifier

10–13 Diagnosis


38 A-96.250.731 / 140212




0 0 Hardware failure electronics DIA_HW_ELECTR1 Hardware failure mechanics DIA_HW_MECH

2 -


4 -


6 -

7 -

1 0 -1 -

2 -

3 -

4 -


6 -

7 -

2 0 -1 -

2 -

3 -

4 -

5 -

6 -

7 -

3 0 -1 -

2 -

3 -

4 -

5 -

6 -


A-96.250.731 / 140212 39



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


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


5.3. Configuration




Tab. 5-8 GSD files for AMI Deltacon




AMI Deltacon 1 17D2Hex SW17D2.gsd SW17D2_D.bmp SW17D2_N.bmp SW17D2_S.bmp


AMI Deltacon 0 9750 Hex PA039750.gsd PA_9750n.bmp


AMI Deltacon 3 9760 Hex PA039760.gsd PA_9760n.bmp

A-96.250.731 / 140212 41


42 A-96.250.731 / 140212

ProfibusProduct Specific Data for AMI Hydrazine

6. Product Specific Data for AMI Hydrazine



GSD File forAMI Hydrazine


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 TelegramInput Data The AMI Hydrazine makes the following modules available as input data for the cyclic data

exchange:

1 Main Process Value2 Main Temperature3 Main Flow4 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



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 AMIThe control data is transferred to the AMI Hydrazine in the following structure:

Tab. 6-1 Input data structure of AMI Hydrazine





0x42, 0x84, 0x08, 0x05 or 0x42, 0x84, 0x81, 0x81 or 0x94



0x42, 0x84, 0x08, 0x05 or 0x42, 0x84, 0x81, 0x81 or 0x94



0x42, 0x84, 0x08, 0x05 or 0x42, 0x84, 0x81, 0x81 or 0x94


0x45, 0x93, 0x08, 0x08, 0x08, 0x08, 0x080xD9

Tab. 6-2 Output data structure


(SP_D)write Byte 0


0x82, 0x81, 0x05, 0x05 or 0x82, 0x81, 0x84, 0x82 or 0xA1


Bit 2–7: not used

Byte 1Bit 0:

Hold

Bit 1: Control Off

Bit 2–7: not used

44 A-96.250.731 / 140212


6.2.1 Data Formats




bad

0 1 uncertain

1 0 good

0 0 ok

0 1 low limited

1 0 high limited

1 1 constant


Status code







OK

0x640x67


OK CONST

0x80 GOOD ok OK

0x890x8A


LOW_LIM HIGH_LIM

0x8D0x8E


LOW_LIM HICH_LIM


Byte Description


2 Status 3

3 Master address



6 Header (block length incl. Header byte) = 14 Status coding according to DP/V17 Status Type (0x81)


9 Status Specifier

10–13 Diagnosis


A-96.250.731 / 140212 45



Byte Bit Meaning when “1” Abbreviation0 0 Hardware failure electronics DIA_HW_ELECTR

1 Hardware failure mechanics DIA_HW_MECH2 -3 Electronic temperature too high DIA_TEMP_ELECTR4 -5 Measurement failure DIA_MEASUREMENT6 -7 -

1 0 -1 -2 -3 -4 -5 Maintenance required DIA_MAINTENANCE6 -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


Bytes 4 and 5 are reserved for future extensions.


Byte Bit Meaning when “1” Abbreviation0 0 Hyd. Alarm high -

1 Hyd. Alarm low -2 -3 -4 -5 -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 Counter Electrode Reference DIA_MEASUREMENT7

2 0 Control Timeout -1

2

3

4

5

6 Cleaning Reagent DIA_MAINTENANCE7 Input Active DIA_HW_ELECTR


A-96.250.731 / 140212 47


6.3. Configuration




Tab. 6-8 GSD files for AMI Hydrazine:



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



GSD File forAMI Hydrogen


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 TelegramInput Data The AMI Hydrogen makes the following modules available as input data for the cyclic data

exchange:

1 Main Process Value2 Main Temperature3 Main Flow4 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

http://www.swan.chhttp://www.swan.ch


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 AMIThe control data is transferred to the AMI Hydrogen in the following structure:

Tab. 7-1 Input data structure of AMI Hydrogen





0x42, 0x84, 0x08, 0x05 or 0x42, 0x84, 0x81, 0x81 or 0x94



0x42, 0x84, 0x08, 0x05 or 0x42, 0x84, 0x81, 0x81 or 0x94



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


(SP_D)write Byte 0


0x82, 0x81, 0x05, 0x05 or 0x82, 0x81, 0x84, 0x82 or 0xA1


Bit 2–7: not used

Byte 1Bit 0:

Hold

Bit 1: Control Off

Bit 2–7: not used

50 A-96.250.731 / 150513


7.2.1 Data Formats




bad

0 1 uncertain

1 0 good

0 0 ok

0 1 low limited

1 0 high limited

1 1 constant


Status code





menami pb 06 · 2019. 9. 19. · gsd file the profibus system requires a description of the device...

Documents