Home
Главная
ABB
Преобразователь Частоты
ACH550-01-03A3-4+B055
Управление встроенной полевой шиной Страница: 37

ABB ACH550-01-03A3-4+B055 [37/62] Abb control profiles technical data

ABB Control Profiles Technical Data

REF1 COMM*AI1 COMM (%) * (AI (%) / 0.5*REF1 MAX (%))

REF2

COMM+AI1 COMM (%) + (AI (%) - 0.5*REF2 MAX (%))

REF2

COMM*AI1 COMM (%) * (AI (%) / 0.5*REF2 MAX (%))

ABB Drives and DCU Profiles

Reference

Value

Setting

AI Reference Scaling

50%

200%

(100 - 0.5 * (par. 1105))%

100%

AI1 Input Signal

Fieldbus Reference

Correction Coefficient

50%

(100 + 0.5 * (Par. 1108)%

(100 - 0.5 * (par. 1108)%

100%

AI1 Input Signal

Fieldbus Reference

Correction Coefficient

50%

200%

100%

AI1 Input Signal

Fieldbus Reference

Correction Coefficient

Содержание

Low voltage ac drives 1
Ach550 drive manuals 2
Table of contents 3
Embedded fieldbus 4
Overview 4
Control interface 5
In general the basic control interface between the fieldbus system and the drive consists of 5
Network planning should address the following questions 5
Note the words output and input are used as seen from the fieldbus controller point of view for example an output describes data flow from the fieldbus controller to the drive and appears as an input from the drive point of view 5
Planning 5
What control information must be sent down to the drives 5
What feedback information must be sent from the drives to the controlling system 5
What types and quantities of devices must be connected to the network 5
Are for rs485 communications 6
As always the grounding wires should not form any closed loops and all the devices should be earthed to a common ground 6
Communication set up efb below activate drive control functions efb on page 9 the appropriate efb protocol specific technical data for example modbus protocol technical data on page 19 6
Connect the rs485 link in a daisy chained bus without dropout lines 6
Connect the shield at each end of the cable to a drive on one end connect the shield to terminal 28 and on the other end connect to terminal 32 do not connect the incoming and outgoing cable shields to the same terminals as that would make the shielding continuous 6
Do not directly ground the rs485 network at any point ground all devices on the network using their corresponding earthing terminals 6
Drive terminals 2 6
For configuration information see the following 6
Mechanical and electrical installation efb 6
To reduce noise on the network terminate the rs485 network using 120 ω resistors at both ends of the network use the dip switch to connect or disconnect the termination resistors see following diagram and table 6
Use belden 9842 or equivalent belden 9842 is a dual twisted shielded pair cable with a wave impedance of 120 ω 6
Use one of the wires in the other pair for the logical ground terminal 31 leaving one wire unused 6
Use one of these twisted shielded pairs for the rs485 link use this pair to connect all a terminals together and all b terminals together 6
Warning connections should be made only while the drive is disconnected from the power source 6
Communication set up efb 7
Note if you cannot see the desired selection on the panel your drive does not have that protocol software in the application memory 7
Serial communication configuration 7
Serial communication selection 7
Setting 9802 automatically sets the appropriate default values in parameters that define the communication process these parameters and descriptions are defined below in particular note that the station id may require adjustment 7
To activate the serial communication set parameter 9802 7
Communication set up efb 8
Note after any changes to the communication settings protocol must be reactivated by either cycling the drive power or by clearing and then restoring the station id 5302 8
Activate drive control functions efb 9
Controlling the drive 9
Define as a fieldbus input any drive data required for control 9
Define as a fieldbus output any control data required by the drive 9
Drive parameter values set as defined below 9
Fieldbus control of various drive functions requires configuration to 9
Fieldbus controller supplied command s in the appropriate location the location is defined by the protocol reference which is protocol dependent 9
Start stop direction control 9
Tell the drive to accept fieldbus control of the function 9
The following sections describe at a general level the configuration required for each control function for the protocol specific details see the document supplied with the fba module 9
Using the fieldbus for start stop direction control of the drive requires 9
Activate drive control functions efb 10
Can be scaled see the following as appropriate 10
Drive parameter values set as defined below 10
Fieldbus controller supplied reference word s in the appropriate location the location is defined by the protocol reference which is protocol dependent 10
Input reference select 10
Modbus register 40002 in the modbus protocol technical data section 10
N2 analog output objects in the n2 protocol technical data section 10
Reference scaling 10
Reference scaling in the abb control profiles technical data section 10
The slope of points 60 and 61 in the fln protocol technical data section 10
Using the fieldbus to provide input references to the drive requires 10
Where required 10
Activate drive control functions efb 11
Drive parameter values set as defined below 11
Fieldbus controller supplied reference word s in the appropriate location the location is defined by the protocol reference which is protocol dependent 11
Miscellaneous drive control 11
Using the fieldbus for miscellaneous drive control requires 11
Activate drive control functions efb 12
And 1402 12
Drive parameter values set as defined below 12
Fieldbus controller supplied reference word s in the appropriate location the location is defined by the protocol reference which is protocol dependent 12
For example to control relays 1 and 2 using serial communication set parameters 1401 12
Note relay status feedback occurs without configuration as defined below 12
Relay output control 12
Then for example using n2 12
To turn both relay 1 and 2 on force objects b07 and b08 on 12
To turn relay 1 on force object b07 to on 12
To turn relay 2 on force object b08 to on 12
Using the fieldbus for relay output control requires 12
Activate drive control functions efb 13
Analog output control 13
Communication fault 13
Drive parameter values set as defined below 13
Fieldbus controller supplied reference word s in the appropriate location the location is defined by the protocol reference which is protocol dependent 13
Pid control setpoint source 13
Use the following settings to select the fieldbus as the setpoint source for pid loops 13
Using the fieldbus for analog output control requires 13
When using fieldbus control specify the drive s action if serial communication is lost 13
Feedback from the drive efb 14
Inputs to the controller drive outputs have pre defined meanings established by the protocol this feedback does not require drive configuration the following table lists a sample of feedback data for a complete listing see input word point object listings in the technical data for the appropriate protocol starting on page 19 14
Mailbox read write 14
Note with modbus any parameter can be accessed using the format 4 followed by the parameter number 14
Pre defined feedback 14
The ach550 provides a mailbox function to access parameters that have not been pre defined by the protocol using mailbox any drive parameter can be identified and read mailbox can also be used to adjust parameter settings by writing a value to any parameter identified the following table describes the use of this function 14
Actual value scaling 15
Although actual value scaling could differ from the above for the n2 and fln protocols it currently does not to confirm see the following sections as appropriate 15
Feedback from the drive efb 15
N2 analog input objects in the n2 protocol technical data section 15
Scaling drive feedback values in the fln protocol technical data section 15
The scaling of actual values can be protocol dependent in general for actual values scale the feedback integer using the parameter s resolution see parameter descriptions section in ach550 user s manual for parameter resolutions for example 15
Where parameters are in percent the parameter descriptions section specifies what parameter corresponds to 100 in such cases to convert from percent to engineering units multiply by the value of the parameter that defines 100 and divide by 100 for example 15
Diagnostic situations 16
Diagnostics efb 16
Fault queue for drive diagnostics 16
Serial communication diagnostics 16
Feature summary 19
Modbus is a serial asynchronous protocol transactions are half duplex featuring a single master controlling one or more slaves while rs232 can be used for point to point communication between a single master and a single slave a more common implementation features a multi drop rs485 network with a single master controlling multiple slaves the ach550 features rs485 for its modbus physical interface 19
Modbus protocol technical data 19
Overview 19
The following modbus function codes are supported by the ach550 19
The modbus protocol was introduced by modicon inc for use in control environments featuring modicon programmable controllers due to its ease of use and implementation this common plc language was quickly adopted as a de facto standard for integration of a wide variety of master controllers and slave devices 19
The modbus specification defines two distinct transmission modes ascii and rtu the ach550 supports rtu only 19
Modbus addressing 20
Additional relay outputs are added sequentially 21
For the 0xxxx registers 21
Forcing is allowed by user configuration of the drive for fieldbus control 21
Modbus protocol technical data 21
Status is always readable 21
The following table summarizes the 0xxxx reference set 21
Bit wise map of the 22
Discrete hardware inputs numbered sequentially beginning with input 33 22
Modbus protocol technical data 22
Selected using parameter 5305 22
The ach550 supports the following modbus function codes for coils 22
The first 32 inputs are reserved for this purpose 22
The following table summarizes the 1xxxx reference set 22
Xxxx mapping modbus discrete inputs the drive maps the following information to the 1xxxx modbus set called modbus discrete inputs 22
40001 40099 map to drive control and actual values these registers are described in the table below 23
40101 49999 map to drive parameters 0101 9999 register addresses that do not correspond to drive parameters are invalid if there is an attempt to read or write outside the parameter addresses the modbus interface returns an exception code to the controller 23
Additional discrete inputs are added sequentially 23
Any user defined analog inputs 23
For the 1xxxx registers 23
Modbus protocol technical data 23
The ach550 supports the following modbus function codes for 3xxxx registers 23
The ach550 supports the following modbus function codes for discrete inputs 23
The following table summarizes the input registers 23
Xxxx mapping modbus inputs the drive maps the following information to the 3xxxx modbus addresses called modbus input registers 23
Xxxx register mapping the drive maps its parameters and other data to the 4xxxx holding registers as follows 23
Modbus protocol technical data 24
The following table summarizes the 4xxxx drive control registers 40001 40099 for 4xxxx registers above 40099 see the drive parameter list e g 40102 is parameter 0102 24
Except where restricted by the drive all parameters are available for both reading and writing the parameter writes are verified for the correct value and for a valid register addresses 25
For the modbus protocol drive parameters in group 53 report the parameter mapping to 4xxxx registers 25
Modbus protocol technical data 25
Note parameter writes through standard modbus are always volatile i e modified values are not automatically stored to permanent memory use parameter 1607 25
The ach550 supports the following modbus function codes for 4xxxx registers 25
To save all altered values 25
16 bit words containing a sign bit and a 15 bit integer 26
Actual values 26
And are 26
Exception codes 26
Exception codes are serial communication responses from the drive the ach550 supports the standard modbus exception codes defined below 26
Modbus protocol technical data 26
Read only values containing information on the operation of the drive 26
Scaled as described earlier in actual value scaling 26
Specified using parameters 5310 5317 26
The contents of the register addresses 40005 40012 are 26
When negative values written as the two s complement of the corresponding positive value 26
Abb control profiles technical data 27
Overview 27
Abb control profiles technical data 28
Abb drives profile 28
Content for the abb drives profile 28
The following table and the state diagram later in this sub section describe the 28
Abb control profiles technical data 29
Content for the dcu profile 29
Dcu profile 29
The following tables describe the 29
Abb control profiles technical data 30
Is status information sent by the drive to the master station 30
Status word 30
The contents of the 30
Abb control profiles technical data 31
Abb drives profile 31
The following table and the state diagram later in this sub section describe the status word content for the abb drives profile 31
Abb control profiles technical data 32
Content for the dcu profile 32
Dcu profile 32
The following tables describe the 32
Abb control profiles technical data 33
Abb control profiles technical data 34
Abb drives profile 34
First the requirements for using the 34
Implementation of the abb drives profile uses the control word to start the drive 34
Must be met see above 34
State diagram 34
State is reached meaning that the drive is running and follows the given reference see table below 34
To illustrate the operation of the state diagram the following example 34
To step through the state machine states until the 34
Use the 34
When the power is first connected the state of the drive is not ready to switch on see dotted lined path in the state diagram below 34
Abb control profiles technical data 35
Cw and 35
Sw bits for the abb drives profile 35
The state diagram below describes the start stop function of 35
Abb control profiles technical data 36
Abb drives and dcu profiles 36
And 1107 36
Has no effect on the scaling of references 36
Is set to 36
Note the setting of parameter 1104 36
Or 1106 36
Reference scaling 36
Scaling for the abb drives profile 36
The following table describes 36
The reference is scaled as follows 36
When parameter 1103 36
Abb control profiles technical data 37
Abb control profiles technical data 38
Note fieldbus references are bipolar that is they can be positive or negative 38
Reference handling 38
The following diagrams illustrate how group 10 parameters and the sign of the fieldbus reference interact to produce 38
Use group 10 parameters to configure for control of rotation direction for each control location 38
Values 38
N2 protocol technical data 39
Overview 39
Drive device type 41
For the metasys and metasys companion products the device type for the ach550 drive is vnd 41
N2 analog input objects 41
N2 protocol technical data 41
On one n2 fieldbus segment there can be up to 32 nodes while integrating ach550 drives with johnson controls metasys 41
On the n2 fieldbus each ach550 drive can be accessed by the full complement of metasys fms features including change of state cos monitoring alarm notification scheduling trend and totalization 41
The following diagram shows the drives integration to the johnson controls metasys companion system 41
The following table lists the n2 analog input objects defined for the ach550 drive 41
N2 binary input objects 42
N2 protocol technical data 42
The following table lists the n2 binary input objects defined for the ach550 drive 42
N2 analog output objects 43
N2 protocol technical data 43
The following table lists the n2 analog output objects defined for the ach550 drive 43
Abb drives ach 550 variable frequency drive csmodel ach_550 vnd 44
Aititle analog_inputs bititle binary_inputs aotitle analog_outputs botitle binary_outputs 44
Below is the ach550 ddl file listing 44
Ddl file for ncu 44
N2 binary output objects 44
N2 protocol technical data 44
The following table lists the n2 binary output objects defined for the ach550 drive 44
The listing below is the data definition language ddl file for ach550 drives used with the network control units 44
This listing is useful when defining drive i o objects to the network controller units 44
Abb ach550 47
Fln protocol technical data 47
Overview 47
Reports 47
Startup 47
Supported features 47
The ach550 provides seven pre defined reports using a report request generated from the fln fieldbus controller select one of the following sets of points by providing views of selected points these reports are often easier to work with than views of the full point database 47
The ach550 supports all required fln features 47
The fln fieldbus connection to the ach550 drives is based on an industry standard rs 485 physical interface the fln floor level network fieldbus protocol is a serial communication protocol used by the siemens apogee system the ach550 interface is specified in siemens application 2734 47
Drive i o 48
Fln protocol technical data 48
Overview 48
Drive config 49
Fln protocol technical data 49
External pid 50
Feedback values are provided with units of percent where 0 and 100 correspond to the range of the sensor being used to measure the control variable these points have default units in hz if other units are required 50
Fln protocol technical data 50
Process pid 50
Scaling drive feedback values 50
The new intercept equals the lowest value of the desired range 50
Unbundle these points with appropriate slopes and intercepts 50
Calculate the new slope as follows 51
Example you are controlling water temperature from a cooling tower using the ach550 to control a fan the temperature sensor has a range of 30 to 250 degrees fahrenheit 51
Fln protocol technical data 51
Loop gains 51
Prc pid gain point 50 and prc pid itim point 51 are pid parameters similar to the p and i gains in the apogee tecs because the abb pi loop and the siemens loop are structured differently there is no a one to one correspondence between the gains the following formulas allow translation from abb gains to siemens gains and vice versa 51
To convert from abb pi gains to siemens p and i gains 51
To convert from siemens p and i gains to abb pi gains 51
To unbundle the feedback prc pid fbck for monitoring in degrees fahrenheit 51
To unbundle the set point input ref 2 for commanding in degrees fahrenheit where 0 60 hz is equal to 30 25 51
Fln protocol technical data 52
Point database 52
The following table lists the point database for fln ach550 application 2734 52
Fln protocol technical data 53
Fln protocol technical data 54
Detailed point descriptions 55
Fln protocol technical data 55
Fln protocol technical data 56
Fln protocol technical data 57
Fln protocol technical data 58
Fln protocol technical data 59
Fln protocol technical data 60

ABB ACH550-01-03A3-4+B055 [37/62] Abb control profiles technical data

Содержание

Похожие устройства