Consequences

Potential Problems

WARNING

UNEXPECTED APPLICATION BEHAVIOR

Take care when an application is migrating from Concept to Control Expert.

Failure to follow these instructions can result in death, serious injury, or equipment damage.

NOTE:

Because of this architectural change, when an application is migrated from Concept to Control Expert you have to evaluate the consequences of the migration, and specially in the following cases:

Multi assignment of connected output variables:

In Concept there are function blocks, mainly in the closed-loop-control area, which do not write their output values to the connected variables in special operating modes (manual mode).

In these special modes it was possible to write the variables from other locations inside the application.

This will work in Control Expert only, if the variables are written after the function block call.

If they are written before the function block call, the copy process from the instance data to the connected variables will overwrite this value with the old value from the instance data.
Controlling output variables by animation table or HMI:

If a block doesn't write his outputs in special operating modes (like manual mode, see above), it was possible to modify the connected output variables by animation tables or HMI.

This will no longer work in Control Expert, since the copy process from the instance data to the connected variables of the function block will overwrite the modified value with the old value from the instance data.

Changed EFB Layout

To avoid major problems, a lot of function blocks (mainly in the Motion and CLC area) were changed in their layout from Concept to Control Expert to ensure a correct mode of operation in the intended way for the function blocks.

The concerned pins were changed from type OUT to IN/OUT.

In nearly all cases the modification meets better the reality, since it is read from the concerned output pins and so they are in fact IN/OUTs.

The following tables summarize the EFBs, where at least one pin was changed from OUT to IN/OUT during migration from Concept to Control Expert.

Library CONT_CTL:

Family	Function Block	Concerned Pin
Controller	PI_B	OUT
Controller	PIDFF	OUT
Output Processing	MS	OUT
Setpoint Management	SP_SEL	SP

Library Motion:

Family	Function Block	Concerned Pin
MMF Start	CFG_CP_F	MFB, CFG_BLK
	CFG_CP_V	MFB, CFG_BLK
	CFG_CS	MFB, CFG_BLK
	CFG_FS	MFB, CFG_BLK
	CFG_IA	MFB, CFG_BLK
	CFG_RA	MFB, CFG_BLK
	CFG_SA	MFB, CFG_BLK
	DRV_DNLD	MFB
	DRV_UPLD	MFB
	IDN_CHK	MFB
	IDN_XFER	MFB
	MMF_BITS	MFB
	MMF_ESUB	MFB
	MMF_INDX	MFB
	MMF_JOG	MFB
	MMF_MOVE	MFB
	MMF_RST	MFB
	MMF_SUB	MFB
	MMF_USUB	MFB

Library Obsolete Lib:

Family	Function Block	Concerned Pin
CLC_PRO	ALIM	Y
	COMP_PID	Y, YMAN_N, OFF_N, SP_CAS_N
	DERIV	Y
	INTEG	Y
	LAG	Y
	LAG2	Y
	LEAD_LAG	Y
	PD_OR_PI	Y
	PI	Y
	PID	Y
	PID_P	Y
	PIP	Y
	PPI	Y
	VLIM	Y
Extensions/Compatibility	R2T	OFF
	SRCH	INDEX
	T2T	OFF

Concept Converter Behavior

The Concept Converter normally handles the layout change in the following way, when a Concept application is imported into Control Expert:

Case 1: A variable is connected to the output pin in Concept:

The Concept Converter keeps the variable at the output side of the IN/OUT pin and adds the variable additionally at the input side of the pin.
Case 2: A link is connected to the output pin in Concept:

The Concept Converter removes the link, creates a new variable of the needed type and writes this new variable to the start and end position of the removed link. Additionally the variable is added to the input side of the pin.

Further Potential Problems

The following tables contain blocks, where also some consequences of the architectural change from Concept to Control Expert may arise in case of multi-assignment, because in Concept:

The blocks do not write their listed output pin in case of errors inside the block.
The blocks do not write their listed output pin in COLD or WARM INIT scan.
The blocks write their listed output pin conditionally depending from internal mode of operation.

Library CONT_CTL:

Family	Function Block	Concerned Pin
Conditioning	DTIME	OUT
	SCALING	OUT
	TOTALIZER	OUT, INFO
Controller	AUTOTUNE	TRI, INFO
	PI_B	OUT_D, DEV
	PIDFF	OUT_D, INFO
	STEP2	DEV
	STEP3	DEV
Output Processing	MS	OUTD, STATUS
	MS_DB	OUTD, STATUS
	SPLRG	OUT1, OUT2
Setpoint Management	RAMP	SP
	RATIO	KACT, SP
	SP_SEL	LSP_MEM

Library I/O Management:

Family	Function Block	Concerned Pin
Analog I/O Configurationj	I_SET	CHANNEL
Analog I/O Configurationj	O_SET	CHANNEL
Analog I/O Scaling	I_NORM_WARN	WARN
	I_PHYS_WARN	WARN
	I_SCALE_WARN	WARN
Quantum I/O Configurationj	ACI040	CHANNL1..16
	ACO130	CHANNEL1..8
	AII330	CHANNEL1..8, INTERNAL
	AII33010	CHANNEL1..8
	AIO330	CHANNEL1..8
	ARI030	CHANNEL1..8

Library Motion:

Family	Function Block	Concerned Pin
MMF Start	CFG_CP_F	Q, ERROR
	CFG_CP_V	Q, ERROR
	CFG_CS	Q, ERROR
	CFG_FS	Q, ERROR
	CFG_IA	Q, ERROR
	CFG_RA	Q, ERROR
	CFG_SA	Q, ERROR
	DRV_DNLD	Q, ERROR, IDN_CNT
	DRV_UPLD	Q, ERROR, REG_CNT, DATA_B, LK
	IDN_CHK	Q, ERROR, NOT_EQ
	IDN_XFER	Q, ERROR, OUT_RAW, OUTCONV
	MMF_ESUB	Q, ERROR, RET1, RET2, RET§
	MMF_INDX	Q, ERROR
	MMF_JOG	Q, ERROR
	MMF_MOVE	Q, ERROR
	MMF_RST	Q
	MMF_SUB	Q, ERROR, RET1, RET2, RET§
	MMF_USUB	Q, ERROR, RET1, RET2, RET§

Library Obsolete Lib:

Family	Function Block	Concerned Pin
CLC	DELAY	Y
	PI1	ERR
	PID1	ERR
	PIDP1	ERR
	THREE_STEP_CON1	ERR_EFF
	THREEPOINT_CON1	ERR_EFF
	TWOPOINT_CON1	ERR_EFF
CLC_PRO	COMP_PID	STATUS, ERR
	DEADTIME	Y
	FGEN	Y, N
	INTEG	STATUS
	PCON2	ERR_EFF
	PCON3	ERR_EFF
	PD_OR_PI	ERR, STATUS
	PDM	Y_POS, Y_NEG
	PI	ERR, STATUS
	PID	ERR, STATUS
	PID_P	ERR, STATUS
	PIP	ERR, SP2, STATUS
	PPI	ERR, SP2, STATUS
	PWM	Y_POS, Y_NEG
	QPWM	Y_POS, Y_NEG
	SCON3	ERR_FF
	VLIM	STATUS
Extensions/Compatibility	FIFO	EMPTY, FULL
Extensions/Compatibility	LIFO	EMPTY, FULL

NOTE: The pins were not changed, because in normal operation mode of the blocks this has no influence.