Sabroe UniSAB III Profibus DP Extended Operating instructions

Version 6.5

Unisab III Probus DP Extended

Probus manualen



Unisab III Profibus DP Extended

Control system for refrigerating compressors

Version 6.5

Unisab III Profibus specification Ext. 6.5

005261 en 2014.10 1/75

Preface

This manual describes how to establish data connection to Unisab III by using the Profibus DP

Extended interface in Unisab III.

This manual is produced by:

Johnson Controls Denmark ApS

Christian X's Vej 201

8270 Højbjerg, Denmark

Phone +45 87 36 70 00

Fax +45 87 36 70 05

CVR No 19 05 61 71

www.sabroe.com

This manual must not be copied without the written permission of Johnson Controls Denmark

and the contents must not be imparted to any third parties nor be used for any unauthorised

purposes. Contravention will be prosecuted.

Please read the manual carefully so that you fully understand the Unisab III control system

and know how to operate it correctly. Damage occurring as a result of incorrect operation is

not covered by Johnson Controls Denmark's guarantee.

Disclaimer

Johnson Controls Denmark makes no representation or warranties with respect to the content

of this document and can under no circumstances be made responsible for possible damages,

neither direct nor indirect, which may arise due to the use of this documentation or the use of

the product described herein.

Furthermore, Johnson Controls Denmark reserves the right to revise this document and to

make changes in it without previous notice.

Important note

It is the programmer's (user's) responsibility to ensure that all values written from an exter-

nal controller to Unisab III through this Profibus DP Extended interface are legal and validated

up against the maximum and minimum limits defined in the Unisab III Engineering manual.

Contents

1. Introduction 7

2. Protocol in detail 8

2.1. What is PPO 8

2.2. List of data input from Unisab III 8

2.2.1 *1) Status Word 9

2.3. Data Outputs for Unisab III 10

2.3.1 *2) Control bits 11

3. Data structure of telegram 12

3.1. Placement of asynchronous data 12

3.2. PKE 13

3.3. Error codes 14

3.4. PKW points in Unisab III 14

3.5. Database 15

3.6. Datapoints 16

3.6.1 Data points in MEASUREMENTS DATA 16

3.6.2 Data points in TIMER DATA 19

3.6.3 Data points in CONFIG DATA 23

3.6.4 Data points in EXTENDED CONFIG DATA 24

3.6.5 Data structure of EEPROM DATA 25

3.6.6 Data points in SHUTDOWN LOG DATA 25

3.6.7 Data points in RANDOM DATA 26

4. Examples 35

4.1. Example 1: Reading a process out setp1. 35

4.2. Example 2: Reading Running hours 38

4.3. Example 3: Reading shutdowns 39

4.4. Example 4: Write Capacity Setpoint 43

4.5. Example 5: Writing timer for prelub. 47

5. Appendix A: Unisab III protocol common

details 52

5.1. Introduction 52

5.1.1 Control MODE 52

5.1.2 Compressor STATE 52

5.1.3 Multisab STATE 52

5.1.4 Digital inputs 53

5.1.5 Digital outputs 53

Unisab III Profibus specification Ext. 6.5

005261 en 2014.10 3/75

5.2. Data points in CONFIGURATION 54

5.2.1 MECHANICAL_ZERO 0 54

5.2.2 REFRIGERANT_TYPE 1 54

5.2.3 COMPRESSOR_TYPE 2 54

5.2.4 OIL_PUMP 3 57

5.2.5 RUNNING_AS_BOOSTER 4 57

5.2.6 FULL_FLOW_PUMP 5 57

5.2.7 MOUNTED_WITH_AUTO_VI 6 57

5.2.8 MOUNTED_WITH_HLI_BLI 7 57

5.2.9 MOUNTED_WITH_ECO 8 58

5.2.10 HIGH_SUCT_LIM_FOR_ECO 9 58

5.2.11 LOW_CAP_LIM_FOR_ECO 10 58

5.2.12 SWEPT_VOLUME 11 58

5.2.13 COMMON_EVAP_COND 12 58

5.2.14 AUXILIARY_OUTPUT_TYPE 13 58

5.2.15 COMMUNICATIONS_SPEED 14 58

5.2.16 PRESS_MEASURING_UNIT 15 59

5.2.17 PREFERRED_MASTER_CONT 16 59

5.2.18 UNLOAD 17 59

5.2.19 RANGE_MOTOR_CURRENT 18 59

5.2.20 CONTROLLING_ON 19 59

5.2.21 EXT_SIGNAL_USED_FOR 20 59

5.2.22 EXT_SIGNAL_MIN_VALUE 21 59

5.2.23 EXT_SIGNAL_MAX_VALUE 22 59

5.2.24 COLD_STORE 23 60

5.2.25 AUTO_START 24 60

5.2.26 AUTO_STOP 25 60

5.2.27 OIL_COOLING 26 60

5.2.28 WATER_COOLING 27 60

5.2.29 HP_ON_TWO_STAGE 28 60

5.2.30 CLIMA_CONTROL 29 60

5.2.31 OIL_RECTIFIER 30 61

5.2.32 MANUAL_ZERO 31 61

5.2.33 MOTOR_SIZE 32 61

5.2.34 MOTOR_MEASURING_UNIT 33 61

5.2.35 COP_ACTIVE 34 61

5.2.36 COP_FLOW_FACTOR 35 61

5.2.37 SUBCOOLING_COP 36 61

4/75

Unisab III Profibus specification Ext. 6.5

005261 en 2014.10

5.2.38 MARTYR_AND_TAKE_OVER 37 61

5.2.39 CHILLER 38 61

5.2.40 CONDENSOR 39 61

5.3. Data Points in EXTENDED CONFIG DATA 62

5.3.1 LANGUAGE 0 (NA) 62

5.3.2 CONTRAST 1 62

5.3.3 SUCT_PRESS_OFFSET 2 62

5.3.4 DISCH_PRESS_OFFSET 3 62

5.3.5 INTERM_PRESS_OFFSET 4 62

5.3.6 LUB_PRESS_OFFSET 5 62

5.3.7 DIFF_PRESS_OFFSET 6 62

5.3.8 PROCESS OUT_TEMP_OFFSET 7 63

5.3.9 CAP_ZERO_OFFSET 8 63

5.3.10 CAP_100_OFFSET 9 63

5.3.11 OFFSET_OF_PARALLEL_CAP 10 63

5.3.12 CAP_FOR_VI_MAX 11 63

5.3.13 QUANTUM 12 63

5.3.14 PORT1_BAUD_RATE 13 63

5.3.15 PORT2_BAUD_RATE 14 63

5.3.16 PORT1_USED_FOR 15 63

5.3.17 PORT2_USED_FOR 16 64

5.3.18 PORT1_NODE_NO 17 64

5.3.19 PORT2_NODE_NO 18 64

5.3.20 BRAKE_DELAY 19 64

5.3.21 PRESS_25_59_BAR 20 64

5.3.22 ROTATUNE 21 64

5.3.23 MOTOR_INPUT_4_20 22 64

5.3.24 RANGE_MOTOR_POWER 23 64

5.3.25 CAP_SIGNAL 24 64

5.3.26 VI_ZERO_OFFSET 25 64

5.3.27 VI_100_OFFSET 26 64

5.3.28 PROFIBUS 27 65

5.3.29 PROFIBUS_BAUD_RATE 28 65

5.3.30 PROFIBUS_ADR 29 65

5.3.31 FREQ_ZERO_OFFSET 30 65

5.3.32 FREQ_100_OFFSET 31 65

5.3.33 5.3.33 MIN_FREQ 32 65

5.3.34 MAX_FREQ 33 65

Unisab III Profibus specification Ext. 6.5

005261 en 2014.10 5/75

5.3.35 PID_CONTROLLER 34 65

5.3.36 SHUTDOWN_OUTPUT_FOR_LOW_SUCT. 35 65

5.3.37 DANBUSS_VERSION 36 66

5.3.38 GSD_FILE_NUMBER 37 66

5.3.39 DIG_IN_1_VIA_PROFIBUS 38 66

5.3.40 DIG_IN_2_VIA_PROFIBUS 39 66

5.3.41 DIG_IN_3_VIA_PROFIBUS 40 66

5.3.42 DIG_IN_4_VIA_PROFIBUS 41 66

5.3.43 DIG_IN_5_VIA_PROFIBUS 42 66

5.3.44 DIG_IN_6_VIA_PROFIBUS 43 66

5.3.45 DIG_IN_7_VIA_PROFIBUS 44 66

5.3.46 DIG_IN_8_VIA_PROFIBUS 45 67

5.3.47 DIG_IN_9_VIA_PROFIBUS 46 67

5.3.48 DIG_IN_10_VIA_PROFIBUS 47 67

5.3.49 DIG_IN_11_VIA_PROFIBUS 48 67

5.4. Shutdowns and alarms with identification

numbers for screw compressors 68

5.4.1 Shutdown and alarm texts 68

5.4.2 Shutdowns and alarms for screw compressors 69

5.5. Shutdowns and alarms with identification

numbers for reciprocating compressors 71

5.5.1 Shutdowns and alarms for reciprocating compressors 71

6. Appendix B: DeltaV GSD file information 73

7. Document revision record 74

6/75

Unisab III Profibus specification Ext. 6.5

005261 en 2014.10

1. Introduction

This manual describes Profibus DPV0 Protocol for Unisab III in an extended version. The Ex-

tended Protocol uses GSD file 095D. A Tiny Profibus Protocol using GSD file 08AA is also avail-

able for Unisab III. Refer to separate manual “Unisab III Profibus specification_Tiny” for de-

scription of the Tiny Protocol. However, we recommend using the Extended version.

This Extended version provides all analog values, control mode, compressor state, Multisab

state, control-on-value, capacity set point, active timer number/value and digital inputs/

outputs as well as causes of shutdown and up to 2 alarms. All this is updated continuously.

Writing start/stop commands, changing control-on-value, mode, set-up for sequencing and

capacity set point are also featured using continuous updating.

All values, limits and settings in the Unisab III databases containing the measurement, timer,

configuration and shutdown log data are available using an asynchronous command/answer

function. Some of these limits and settings can be written to, also using the asynchronous

command/answer function. For safety reasons, Unisab III automatically prevents the writing

of values beyond certain limits.

GSD files, program examples and installation guides can be downloaded from

www.sabroe.com

If you need further information, please contact the Technical Support Controls office stated

below.

Johnson Controls Denmark ApS

Technical Support Controls

Christian X's Vej 201

DK-8270 Højbjerg

Denmark

Tel +45 8736 7000

E-mail: [email protected]

The transport mechanism (layer 1 and 2) is strictly according to standard Profibus DPV0 Pro-

tocol standards. The application layer (layer 7) is presented in this paper. The application lay-

er for Unisab III is based on the two papers listed below, but it does not comply with any of

those in detail.

PROFIBUS Profile

Profile for SEMI

Version 1.0

August 2002

PNO Order No. 3.152

PROFIBUS Profil

Profil für Drehzahlveränderbare Antriebe,

PROFIDRIVE Ausgabe September 1997

PNO Best.-Nr. 3.071

Introduction

Unisab III Profibus specification Ext. 6.5

005261 en 2014.10 7/75

2. Protocol in detail

2.1. What is PPO

Parameter-Prozessdaten-Objekt (Parameter-Process data-Object) is comprised of the

PKW (please see chapter 3) plus PD (Prozessdaten). PD holds the data that are changed

constantly and which should be transferred synchronously. This means that this data is trans-

ferred in each transmission from master to slave and from slave to master.

In the present version of the protocol, only PDR1 and PDR2 are implemented.

2.2. List of data input from Unisab III

Word Type Text Dec.Unit PDR1 PDR2

1 PKW1 X

2 PKW2 X

3 PKW3 X

4 PKW4 X

5 SW *1) X

6 PD1 SUCT_PRESS, *0.1 °C/R X

7 PD2 SUCT_TEMP *0.1 °C X

8 PD3 SUCT_SUPERHEAT, *0.1 °C X

9 PD4 DISCH_PRESS, *0.1 °C/R X

10 PD5 DISCH_TEMP, *0.1 °C X

11 PD6 LUB_PRESS, *0.1 Bar X

12 PD7 OIL FILTER DIFF_PRESS, *0.1 Bar X

13 PD8 OIL_TEMP, *0.1 °C X

14 PD9 MOTOR_CURR, *1 Amp X

15 PD10 PROCESS OUT_TEMP, *0.1 °C X

16 PD11 INTERM_PRESS, *0.1 °C/R X

17 PD12 INTERM_TEMP, *0.1 °C X

18 PD13 EXT_INPUT, *0.1 X

19 PD14 CAPACITY, *0.1 % X

20 PD15 CAP_POSITION, *0.1 % X

21 PD16 VI_POSITION, *0.1 % X

22 PD17 DISCH_SUPERHEAT, *0.1 °C X

23 PD18 VOL FLOW COP *1 m3/h X

24 PD19 MOTOR REVS *1 RPM X

25 PD20 MOTOR POWER *1 kW X

26 PD21 SUCT_PRESS_BAR, *0.1 Bar X

27 PD22 DISCH_PRESS_BAR, *0.1 Bar X

28 PD23 INTERM_PRESS_BAR, *0.1 Bar X

29 PD24 YIELD, ** *0.1 % X

30 PD25 Control Mode (0=stopped, 1=manual, 2=auto,

3=remote)

X

31 PD26 Compressor State X

32 PD27 Control On (0=Suct, 1=Process out, 2=Disch,

3=Hot Water, 4=Ext.Cool, 5=Ext.H or

6=Capacity Set Point)

X

33 PD28 Multisab (Sys No/Controller/Start No/Multisab

state) (4 bit each)

X

34 PD29 Capacity Actual Set point X

Protocol in detail

8/75

Unisab III Profibus specification Ext. 6.5

005261 en 2014.10

Word Type Text Dec.Unit PDR1 PDR2

35 PD30 Active timer number X

36 PD31 Active timer value Sec X

37 PD32 Digital Inputs (see subsection 5.1.4.) X

38 PD33 Digital Outputs (see subsection 5.1.5.) X

39 PD34 Digital Outputs (see subsection 5.1.5.) X

40 PD35 Shutdown (see section 5.4.) X

41 PD36 Alarm 1 (see section 5.4.) X

42 PD37 Alarm 2 (see section 5.4.) X

** YIELD value varies depending on compressor type (rotatune, screw, reciprocating)

2.2.1 *1) Status Word

The SW holds some bits with useful information

Bit Text Description

0 Common shutdown

1 Common alarm

2 Running

3 Ready

4 Capacity remote control mode

5

6

7

8

9

10

11

12

13

14

15

Protocol in detail

Unisab III Profibus specification Ext. 6.5

005261 en 2014.10 9/75

2.3. Data Outputs for Unisab III

Word Type Text Unit PDW1 PDW2

1 PKW1 X

2 PKW2 X

3 PKW3 X

4 PKW4 X

5 CW *2) X

6 PD1 Start/Stop command (High byte = 55h / Low

byte = 55h) Remote only

X

7 PD2 Control On (0=Suct, 1=Process out, 2=Disch,

3=Hot Water, 4=Ext.Cool, 5=Ext.Heat or 6=Ca-

pacity Set Point(Remote only)) Write active while

CW bit 12 is set

X

8 PD3 Control mode (0=Stopped, 1=Manual, 2=Auto,

3=Remote) Write active while CW bit 13 is set

X

9 PD4 Multisab (Sys No/ - /Start No/ - ) ( 4 bit each )

Write active while CW bit 14 is set

X

10 PD5 Capacity Set Point (Active for SP > -100) Do

write with value less than -100 in order to return

to Multisab or local control Write active while CW

bit 15 is set

X

Please note:

Through the Extended Protocol you can:

1. Start and stop the compressor. Only possible if Unisab is in Remote.

To start the compressor, write “55h” in the high byte and “00” in low byte.

To stop the compressor, write “00” in the high byte and “55h” in low byte.

The start and stop commands must be sent as pulses with duration of approximate 1

second, the start command must be sent as 0000h -> 5500h -> 0000h, the stop

command must be sent as 0000h -> 0055h -> 0000h.

From version 1104, Unisab III will after the first start command ignore succeeding

start commands. Also after the first stop command, succeeding stop commands are

ignored.

The start and stop commands should only be used if Control On mode is set to Ca-

pacity set point. In all other Control on modes, start and stop commands should not

be used. Use e.g. the digital input “Normal stop“ as start and stop signal in the follow-

ing modes; Suct, Process out, Disch, Hot Water, Ext.Cool or Ext.Heat.

The reason for this is to prevent the compressor from starting and stopping independ-

ent of the PLC commands when the parameters Auto Start and Auto Stop are set to

Yes.

If the compressor is started with the remote start command, but the Capacity set

point is below the stop capacity, e.g. 5% for a screw compressor, the compressor will

be stopped again on the Delay before stop timer, if Auto Stop is set to Yes.

2. Change Control On regulator mode [Suction, brine, discharge, hot water, Ext. cool,

Ext. heat].

Protocol in detail

10/75

Unisab III Profibus specification Ext. 6.5

005261 en 2014.10

Unisab III is switched into Capacity mode by writing a Capacity Set Point value > -100

when mode 6 = Capacity set point. When Unisab III is switched into Capacity mode,

the Start Number will switch to zero. It is possible to set Control On = 6 in all modes.

3. Changing Control Mode to [Stopped, Auto or Remote] is possible in all modes.

4. Changing Start and System numbers [1-14] is only possible in Remote mode.

5. Remote control of Capacity Set Point. Only possible if Unisab III is in Remote and

when CW bit 15 is set.

It is good practice when communicating from PLC to Unisab III to add some delays where you

wait for the Unisab III to reply before sending the next read/write order. If you communicate

with, e.g. four Unisab III controls, you can communicate with the first Unisab III in 1st PLC

scan, with the second Unisab III in the 2nd PLC scan, etc. In the ISAC PLC program block, we

only communicate with one Unisab III per PLC scan, also to level out the load on the PLC.

2.3.1 *2) Control bits

Control bits from master to Unisab III

Bit Text Description

0 Compressor Motor Starter Feed Back

1 External Start Permission – Normal Stop

2 External Start Permission – Instant Stop

3 Start_Request

4 Controller Set Point 1 or Set Point 2

5 Motor Current Limit 1 or Limit 2

6 Oil Pump Motor Starter Feed Back

7 Full Flow Pump Motor Starter Feed Back

8 Oil Float Switch

9 Capacity Decrease Blocked

10 Thermistor in Motor Windings

11

12 Change value (Set PD2 parameter)

13 Change value (Set PD3 parameter)

14 Change value (Set PD4 parameter)

15 Change value (Set PD5 parameter)

Please note: Bits 12, 13, 14 and 15 'Set PDx parameter' must be set only until the change of

the PD2, PD3, PD4 or PD5 Parameter has taken place. While set, this command blocks any

other means of changing the PDx Parameter.

Protocol in detail

Unisab III Profibus specification Ext. 6.5

005261 en 2014.10 11/75

3. Data structure of telegram

Using 8 bytes it is possible to transfer data to and from Unisab III in asynchronous mode. This

method is not exactly according to the profiles referred to in chapter 1 but it does not differ

much. Most notable is the database and datapoint terms which are used in place of PNU (Pa-

rameter Number).

0 1 2 3 4 5 6 7 8 9 Etc.

PKE PKE IND Res. PWE PWE PWE PWE Rest of Tele-

gram

PKE = Parameter Kennung = parameter signature

PKW = Parameter Kennung Wert = PKE + IND + PWE

IND = index in the data structure

Res = Reserved for later extensions

PWE = Parameter Wert = Parameter value (Only Byte 7 used for bytes data, byte 6 and 7 are

used for Integers and byte 4, 5, 7 and 7 are used for Longin data)

Rest of Telegram = Synchronous part of transmission

3.1. Placement of asynchronous data

0 1 2 3 4 5 6 7 8 9 Etc .

PKE PKE IND Res. PWE PWE PWE PWE Res t o f Teleg ram

Byte s

data

(8 bit)

Integer data

(16 bit)

Long Integer da ta (32 bit)

PWE_6 -> PWE_7

PWE_4 -> PWE_7

P WE_7

Data structure of telegram

12/75

Unisab III Profibus specification Ext. 6.5

005261 en 2014.10

The 8 PKW bytes to Unisab III will be exchanged via the output buffer (send) and the input

buffer (receive), as specified by the dynamic data index address (defined by user).

0 1 2 3 4 5 6 7 8 9 Etc.

PKE PKE IND Res. PWE PWE PWE PWE Re st of Tele g ram

Type Tex t

Unit

PDR1

PDR2

PKW1 X

PKW2 X

PKW3 X

PKW4 X

S W *1) X

PD1 SUC T_P RESS, X

PD2 SUC T_TEMP X

PD3 SUC T_S UP ERHEAT, X

PD4 DIS CH_PR ES S , X

PD5 DIS CH_TEMP , X

PD35 Alarm X

PD36 Warning1 X

PD37 Warning2 X

PKE - Byte 0

PKE - Byte 1

IND - Byte 2

Res - Byte 3

PWE - Byte 4

PWE - Byte 5

PWE - Byte 6

PWE - Byte 7

Rest o f

te le g ram

(cyc lic data )

~

~~

~

3.2. PKE

The 2 first bytes hold the PKE word. Please see the bitwise description below.

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

AK SPM Database Data Point Number in the database

AK = instruction / response signature

SPM = Spontan Meldung = Spontaneous Message (Not implemented In Unisab III)

Database + Data Point Number = PNU = Parameter Nummer = Parameter Number

Data structure of telegram

Unisab III Profibus specification Ext. 6.5

005261 en 2014.10 13/75

AK

Instruction

signature

Response required

Response

signature

Result OK

Response

signature

Result not

OK

0 None 0

1 Read Parameter Value 1,2 11 7

2 Write Parameter Value (integer) 1 7

3 Write Parameter Value (Long int) 2 7

4-9 Not used in Unisab III

10 Write Parameter value (byte) 11 7

Response value will be returned in PWE 6 and 7 for integers and in PWE 7 for bytes. Response

signature will be returned in the AK field.

To make sure the Unisab III response matches the request, check that the header

content is identical for the answer and the request.

3.3. Error codes

If Unisab III cannot return the wanted data or write the wanted settings, an error code is re-

turned in the PWE field byte no. 6 and 7 as one integer.

0 Undefined PNU

1 Parameter cannot be written into

2 Value outside low or high limit

3 Index error

3.4. PKW points in Unisab III

PKW (PARAMETER-KENNUNG-WERT)

Data in Unisab III is stored in simple databases using structures. This makes tables and ad-

dressing simpler than having one long numbered array of data. Furthermore, it makes later

extensions of these databases and their structures possible without compromising compatibili-

ty towards newer or older versions. If master indexes too far in an old slave, the slave will

respond with an error message stating that this point is not defined. (Error code 0). This de-

mands that the numbering of existing points and indexes must never be changed in Unisab III

versions to come.

HOW TO:

There are several databases, each with data points of different structure. The database is ad-

dressed with bit 8, 9 and 10 of the PKE. The 8 LSB of the PKE is the actual data point number

in the database in question. With IND (Index) of the PKW the structure is indexed into.

Please note that index 0 in MEASUREMENTS DATA is all transferred in the PZD (Prozessdaten)

field of the PPO (Parameter-Prozessdaten-Objekt) using synchronous transfer. This might be

useful for testing.

Please note that all data is transferred as integers. Data structures which are not composed of

integers must nevertheless be accessed as arrays of integers.

Data structure of telegram

14/75

Unisab III Profibus specification Ext. 6.5

005261 en 2014.10

3.5. Database

DATABASE NO.

MEASUREMENTS DATA 0

TIMER DATA 1

CONFIG DATA 2

EXTENDED CONFIG DATA 3

EEPROM DATA 4

SHUTDOWN LOG DATA 5

RANDOM DATA 6

Data structure of telegram

Unisab III Profibus specification Ext. 6.5

005261 en 2014.10 15/75

3.6. Datapoints

3.6.1 Data points in MEASUREMENTS DATA

SUCT_PRESS 0

SUCT_TEMP 1

SUCT_SUPERHEAT 2

DISCH_PRESS 3

DISCH_TEMP 4

LUB_PRESS 5

DIFF_PRESS 6

OIL_TEMP 7

MOTOR_CURR 8

PROCES OUT_TEMP 9

INTERM_PRESS 10

INTERM_TEMP 11

EXT_INPUT 12

CAPACITY 13

CAP_POSITION 14

VI_POSITION 15

DISCH_SUPERHEAT 16

VOL_FLOW_COP 17

MOTOR_REVS 18

MOTOR_POWER 19

SUCT_PRESS_BAR 20

DISCH_PRESS_BAR 21

INTERM_PRESS_BAR 22

YIELD 23

OIL_SEP_TEMP 24

INTERNAL_SUCT_PRESS 25

PRESSURE_RATIO 26

EVAPORATOR_LEVEL 27

PROCESS_IN_TEMP 28

CHILLER_SUPERHEAT 29

INTERNAL_PRESSURE 30

ECO_PRESSURE (NA) 31

OIL_PUMP_PRESSURE 32

Data structure of telegram

16/75

Unisab III Profibus specification Ext. 6.5

005261 en 2014.10

Data structure of each MEASUREMENTS DATA point

int value; 0

int shutdownHIlim; 1

int shutdownHIlimmin; 2

int shutdownHIlimmax; 3

int shutdownLOlim; 4

int shutdownLOlimmin; 5

int shutdownLOlimmax; 6

int alarmHIlim; 7

int alarmHIlimmin; 8

int alarmHIlimmax; 9

int alarmLOlim; 10

int alarmLOlimmin; 11

int alarmLOlimmax; 12

int actualSP; 13

int setp1; 14

int setp1min; 15

int setp1max; 16

int setp2; 17

int setp2min; 18

int setp2max; 19

int neutralzone; 20

int neutralzonemin; 21

int neutralzonemax; 22

int pband; 23

int pbandmin; 24

int pbandmax; 25

int tsample; 26

int tsamplemin; 27

int tsamplemax; 28

int tint; 29

int tintmin; 30

int tintmax; 31

int tdiff; 32

int tdiffmin; 33

int tdiffmax; 34

int p_part; 35

int i_part; 36

int d_part; 37

int minpulse; 38

int minpulsemin; 39

int minpulsemax; 40

int actuatortime; 41

int actuatortimemin; 42

int actuatortimemax; 43

int mv_saved; 44

int sample_timer; 45

int reg_output; 46

float gam_int_del;

unsigned char non-inverted;

unsigned char symmetric;

unsigned char shutdownHIcode;

Data structure of telegram

Unisab III Profibus specification Ext. 6.5

005261 en 2014.10 17/75

unsigned char shutdownLOcode;

unsigned char alarmHIcode;

unsigned char alarmLOcode;

unsigned char type;

unsigned char exp;

MENU_FLAG_REC menuflag;

LIMIT_CHECK_REC limitflag;

SHUTDOWN_FLAG_REC shutdownflag;

unsigned char it_was_MAN;

The same data structure is shared for all data points, even though for some data it does not

make sense. If an entry is read where the value would be undefined, the returned value will

be 0.

If you try to write to an undefined value, the error code “out of range” will be returned for all

values (exception: If you write 0, no error code will be returned).

Addressing beyond index 46 is not considered to be relevant. If you want to do so anyway,

you must transfer the data needed as integers and figure out which way to unpack data.

Later definitions may be added about substructures MENU_FLAG_REC etc. This is not consid-

ered relevant yet, as this information is of no use outside Unisab III except for debugging

software internally to Unisab III.

Data structure of telegram

18/75

Unisab III Profibus specification Ext. 6.5

005261 en 2014.10

Page is loading ...

Sabroe UniSAB III Profibus DP Extended Operating instructions

Sabroe UniSAB III Profibus DP Extended Operating instructions

Related papers

Other documents