Lenze Drive PLC Developer Studio 9300 Servo PLC (V8.x) - Manual (Page 20)

2.1 AIF1_IO_AutomationInterface (node number 41)
9300 Servo PLC
System blocks
2−6
L
9300 Servo PLC EN 5.0
System variables
Variable Data type Signal type Address Display
code
Display
format
Note
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
Bool Binary
%QX41.2.0
C0151/4 hex
Display code in hex
as double word
.. ...
AIF1_bFDO15_b %QX41.2.15
AIF1_bFDO16_b %QX41.3.0
.. ...
AIF1_bFDO31_b %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 to via several variables of different data types
simultaneously. Thus the data can be transferred by the PLC program as
·
binary information (1 bit)
·
status word/quasi−analog value (16 bits)
·
phase information (32 bits)
according to the requirements.
Byte Variable (1 bit) Variable (16 bits) Variable (32 bits)
1, 2
AIF1_wDctrlStat
Notes: Drive PLC:
All variables assigned to byte 1/2 can be written to by the PLC program.
9300 Servo PLC:
Bytes 1 and 2 can be used to transfer the status word from the SB DCTRL_DriveControl.
·
To do this, connect the variable DCTRL_wStat of the SB DCTRL_DriveControl with the variable AIF1_wDctrlStat.
·
In addition to signals such as IMP and CINH, the SB DCTRL_DriveControl status word contains some freely
assignable signals which can be written to 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
Tip!
Avoid simultaneous overwriting via different variable types to ensure data consistency.
·
Thus bytes 5 and 6 should only be written to
– by the variable AIF1_dnOutD1_p,
– by the variable AIF1_nOutW2_a or
– by the variables AIF1_bFDO0_b ... AIF1_bFDO15_b.