2 structure of the parameter set file, 1 file header, File header – Lenze i700 User Manual

Page 310: Structure of the parameter set file, 11 appendix

Advertising
background image

11

Appendix

11.2

Structure of the parameter set file

310

Lenze · i700 servo inverter · Reference manual · DMS 1.5 EN · 03/2014 · TD05

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

11.2

Structure of the parameter set file

The parameter set file is designed as an extendable file. This means that it is possible to add header

components later on without interrupting previous algorithms. Therefore the file is divided into

three sections:

1.

File header

• The file header contains important information on the file as a whole, including its size, the

checksum, the file header type, the number of data headers, and their position from the start

of the file.

2.

Data header

• The data header contains information on a specific part of the data within the data area.

These are for instance the data type and data interpretation and thus the type of data header,

the data offset in the file, and the size of the data packet.

3. Data

• The data is a densely packed arrangement of data, the sense of which only becomes clear

when the type of data header specified is known.

11.2.1

File header

Byte offset

0

4

8

12

16

20

24

28

32

Type

Version

Size

Manufactu

rer

Product

Version

Data

start

Data

size

CRC

Byte

offset

Meaning

Info

0

File type

File identification

Currently only the following values are defined:

• 2: Storage parameter set (the file exclusively contains

parameters provided for persistence).

• 3: Complete parameter set (the file contains all

parameters).

4

File version

Version number of the file

8

File size

Total size of the file in [bytes]

12

Manufacturer's identification mark

according to object directory

Identification of the device which this parameter set file

belongs to. If the values do not comply with those of the

object directory during the import, an attempt to

execute the import is nevertheless carried out.

Parameters which could not be imported can be

identified later by means of the parameter set error

report.

16

Product ID according to object directory

20

Version identifier of the object directory

24

Start of the data description area

Offset of the data description area in [bytes]

(offset from the start of the file).

28

Size of the data description area

Size of the data description area in [bytes]

32

CRC32 (as defined in IEEE 802.3)

Cyclic Redundancy Check (CRC32) across the entire file; 0

must be entered in the checksum field at the time of

calculation.

Cyclic redundancy check (CRC) - parameter set

comparison on the basis of the checksum ( 21)

Advertising