TR-Electronic LMP-30, Руководство пользователя

Страница: 128 / 167

Parameterization and Configuration
 TR-Electronic GmbH 2018, All Rights Reserved Printed in the Federal Republic of Germany
Page 128 of 167 TR - ELA - BA - DGB - 0027 - 03 11/12/2019
6.3.4 Acyclic parameter access (Base Mode Parameter Access - Local)
The measuring system parameters in the parameter number range 9xx, 600xx (PROFIdrive specific
parameters) and 650xx (Encoder Profile specific parameters) are written or read via the acyclic Data
Exchange Service using the standardized data exchange format "Base Mode Parameter Access -
Local". Implementation was in accordance with the PROFIdrive drive profile.
The parameters are accessed using the client-server principle via the record data object with index
0xB02E.
In the record data request the IO controller specifies which parameter is to be read or written, and in
the record data response the IO device transmits the read data, or confirms the write command.
The record data request is triggered via a write command by means of the system function block SFB
53 "WRREC" (write record) provided by SIEMENS. The record data response must be requested
separately via a read command by means of the system function block SFB 52 "RDREC" (read
record).
The exact mode of operation of the system function blocks can be taken e.g. from the SIEMENS
description "6ES7810-4CA08-8AW1, System Software for S7-300/400 System and Standard Functions
for Volume 1/2" .
Declaration of input parameters SFB52 / SFB53:
IN parameter Type Description
REQ BOOL REQ = 1: Perform data record transmission
ID DWORD Logical address of DP slave/PROFINET IO component (unit or
module diagnostic address according to configuration)
INDEX INT 0xB02E, valid for all 9xx and 6xxxx parameters
MLEN INT
Maximum length of the data record information to be read in
bytes or maximum length of the data record to be transmitted in
bytes for a write command.
RECORD (IN/OUT) ANY
The actual record data request or record data response must be
specified here, see following tables Table 1: Record Data
Request and Table 2: Record Data Response
Only one command can be processed at a time
The initiative always comes from the IO controller
Only one parameter can be processed in a command