ACS_DRIVES_CTRL_ENG Engineering Interface for ACS Drives with ABB-Drives Profile¶
Function Block ACS_DRIVES_CTRL_ENG is used as an engineering interface for ACS Drives with ABB Drives profile.
Function Block Information
| Available as of PLC runtime system: | V1.3.2 |
| Available as of PLC runtime system: | ACSDrivesBase_AC500_V20.lib |
| Block type | Function Block with historical values |
Block Description
Function Block ACS_DRIVES_CTRL_ENG is used as an engineering interface for ACS Drives with ABB Drives profile.
Inputs REF_VALUE1 and REF_VALUE2 and the generated Control Word are written to the DRIVE_DATA variable which transfers these values to a communication Function Block, e.g. ACS3XX_MOD-MAST_RTU. That communication Function Block writes them to the drive. In the same way ACT_VALUE1, ACT_VALUE2 and the Status Word are transferred from the communication Function Block to the ACS_DRIVES_CTRL_ENG block where they are written to the outputs.
As long as EN=FALSE no values are read nor written to the DRIVE_DATA variable.
The Control Word can be generated in 2 ways. First way is to set the single bits of the Control Word separately at the inputs OFF1 … CW_BIT15 while the input USE_CW=FALSE. Second way is to set the input USE_CW=TRUE and write the Control Word as a whole word directly to the input CW. The generated Control Word is written to the DRIVE_DATA variable and for diagnosis purpose also available at output USED_CW.
PRECONDITIONS
The data transfer to the ACS drive is realized via the IN_OUT variable DRIVE_DATA, which must be connected to an ACS3XX_COM_MOD_RTU ACS3XX_COM_MOD_RTU Communication for ACS3XXwrite one bit/ACX550 Drives via MODBUS RTU, ACS_COM_MOD_RTU ACS_COM_MOD_RTU Communication for ACS / DCS Drives via MODBUS RTU, ACS_COM_MOD_RTU_ENHANCED ACS_COM_MOD_RTU_ENHANCED Communication for ACS Drives via MODBUS RTU using ABB Drives Profile Enhanced, ACS_COM_MOD_TCP ACS_COM_MOD_TCP Communication for ACS / DCS Drives via MODBUS TCP or ACS_COM_MOD_TCP_ENHANCED ACS_COM_MOD_TCP_ENHANCED Communication for ACS / DCS Drives via MODBUS TCP, ACS_COM_MOD_TCPx ACS_COM_MOD_TCPx Communication for ACS / DCS Drives via MODBUS TCP or ACS_COM_MOD_TCPx_ENHANCED ACS_COM_MOD_TCPx_ENHANCED Communication for ACS / DCS Drives via MODBUS TCP.
For the necessary configuration of parameters in the drive see table below.
| Drive Parameter | ACS3XX, ACX550 | ACS850, ACQ810 embedded | ACS850, ACQ810 | ACSM1 | ACS580, ACS880 | ACS800 | Comment |
|---|---|---|---|---|---|---|---|
| EXT1 COMMANDS | 10.01 = COMM | 10.01 = FBA | 10.01 = FB | 10.01 = FBA | 20.01 = Fieldbus A | 10.01 = COMM.CW | Fieldbus interface as source for start and stop. |
| EXT1/EXT2 SEL | 11.02 = COMM | 12.01 = P.02.36 bit 15 | 12.01 = P.02.22 bit 15 | 34.01 = P.02.12 bit 15 | 19.11 = MCW Bit11 (06.01) | 11.02 = COMM.CW | Fieldbus interface as source to switch to EXT2 control place. |
| REF1 SELECT | 11.03 = COMM | 21.01 = EFB REF1 | 21.01 = FBA REF1 | 24.01 = FBA Ref1 | 22.11 = FBA ref1 | 11.03 = COMM.REF | Fieldbus interface as source for speed reference. |
| FAULT RESET SEL | 16.04 = COMM | 10.10 = P.02.36 bit 8 | 10.10 = P.02.22 bit 8 | 10.08 = P.02.12 bit 8 | 31.11 = P.06.01 bit 7 | 16.04 = COMM.CW | Fieldbus interface as source for fault reset. |
| PROFILE | 53.05 = ABB DRV FULL | 58.06 = ABB Drives classic/enhanced | 51.02 = ABB Drives classic/enhanced | 51.02 = ABB Drives classic/enhanced | 51.02 = ABB Drives classic/enhanced | 98.07 = ABB DRIVES | Control Profile to ABB Drives Profile classic or enhanced. |
Note
Only one of the Function Blocks ACS3XX_DRIVES_CTRL_BASIC, ACS_DRIVES_CTRL_STANDARD or ACS_DRIVES_CTRL_ENG must be enabled (EN=TRUE) at the same time.
The data transfer to the ACS drive is realized via the IN_OUT variable DRIVE_DATA, which must be connected to an ACS3XX_COM_MOD_RTU or an ACS_COM_xxx Function Block.
The input and output names of the bits of the Control Word and Status Word reflect the functions used with ABB Drive Profile. So the block should be used with ABB Drives profile setting in the drive.
The Function Block does not execute any functionality expect data transfer to and from the DRIVE_DATA variable. So there is no special drive parameter setting necessary to use this block.
The programmer using this block should have a detailed understanding of how to set the Control Word according to the Status Word and the description of the used drive.
For standard speed & torque control application it is recommended to the use the ACS_DRIVES_CTRL_STANDARD instead.