System modules
AIF1_IO_AutomationInterface (node number 41)
Outputs_AIF1
13
265
EDBCSXA064 EN 3.2
System variables
Variable Data
type
Signal
type
Address Display
code
Display
format
Notes
AIF1_wDctrlStat Word ˘ %QW41.0 ˘ ˘
AIF1_nOutW1_a
Integer analog
%QW41.1 C0858/1
dec [%]
AIF1_nOutW2_a %QW41.2 C0858/2
AIF1_nOutW3_a %QW41.3 C0858/3
AIF1_bFDO0_b
...
AIF1_bFDO15_b
BOOL binary
%QX41.2.0
...
%QX41.2.15
˘ hex
AIF1_bFDO16_b
...
AIF1_bFDO31_b
%QX41.3.0
...
%QX41.3.15
AIF1_dnOutD1_p
Double
integer
position %QD41.1 C0859 dec [inc]
User data
The 8 bytes of user data to be sent can be written via several variables of different data
types. According to requirements, data can therefore be transferred from the PLC program
as
ƒ binary information (1 bit)
ƒ status word/quasi−analog value (16 bit)
ƒ angle information (32 bit)
Note!
Avoid simultaneous overwriting via different variable types to ensure data
consistency.
Thus, bytes 5 and 6 should only be overwritten by
ƒ variable AIF1_dnOutD1_p,
ƒ variable AIF1_nOutW2_a or
ƒ variables AIF1_bFDO0_b ... AIF1_bFDO15_b.
Byte Variable (1 bit) Variable (16 bit) Variable (32 bit)
1, 2
AIF1_wDctrlStat
Byte 1/2 can be used for transferring the status word from the SB DCTRL_DriveControl to the field bus
module.
l For this purpose, connect variable DCTRL_wStat of the SB DCTRL_DriveControl to variable
AIF1_wDctrlStat.
l In addition to signals such as IMP and CINH the SB status word DCTRL_DriveControl contains some
freely assignable signals which can be overwritten via the variables DCTRL_bStateB..._b of the
SB DCTRL_DriveControl.
3, 4
AIF1_nOutW1_a
5, 6
AIF1_bFDO0_b
...
AIF1_bFDO15_b
AIF1_nOutW2_a
AIF1_dnOutD1_p
7, 8
AIF1_bFDO16_b
...
AIF1_bFDO31_b
AIF1_nOutW3_a