Metadata

Metadata are additional information you can download with the project into the PLC. Metadata are verified during the following actions:

Online > Online mode
Online > Download program code changes to PLC
Project > Save as > Project on PLC...
Project > New > From PLC...

Metadata especially consist of:

Project IDs and project version number which can be entered in the metadata compile options by the user
Control FPWIN Pro7 version number, project object CRCs and project object time and date information which are generated by Control FPWIN Pro7

Metadata can be activated in Extras > Options > Compile options > Metadata

Activating metadata provides the following features:

User-defined metadata can be entered in the compile options
System-defined metadata are generated
Special program code to set the metadata after switching the PLC to RUN mode is downloaded

When you go online, the following checks are performed:

The project IDs set in the Control FPWIN Pro7 metadata compile options are checked to ensure that the connection has been established to the expected PLC
The program code and configuration CRCs are checked for relevant differences to be downloaded
If the PLC is in RUN mode, project object CRCs are checked to determine whether it is possible to continue with monitoring and downloading changes
The user can get the following additional information:
- The used Control FPWIN Pro7 versions
- The last change dates

Description and memory layout of the metadata

Assuming the most upper registers in the DT hold area which are used by the metadata are DDT10000:

Categories	Types	Description	Size	Range/value	Offsets from above	Address
Header		Begin of metadata marker	32 bits	16#4D657441	0	DDT10000
		Size of metadata content in bytes	16 bits	76	-1	DT9999
	Version number	Metadata version number	32 bits	1.0.0.0	-3	DDT9997
User data¹⁾	IDs	Company/user ID	32 bits	0–4294967295	-5	DDT9995
		Application ID			-7	DDT9993
		PLC project ID			-9	DDT9991
	Version number	PLC project version number		0.0.0.0–255.255.255.255	-11	DDT9989
System data²⁾	Version number	Control FPWIN Pro7 version number	32 bits	0.0.0.0–255.255.255.255	-13	DDT9987
	Last change dates³⁾	Last change date of configuration	32 bits	DT#2001-01-01- 00:00:00	-15	DDT9985
		Last change date of POUs		-	-17	DDT9983
		Last change date of user libraries		DT#2099-12-31- 23:59:59	-19	DDT9981
	Compile options⁷⁾	Code generation	16 bits	16#0–16#FFFF	-20	DT9980
	Compile options⁷⁾	CRC-16 of address ranges	16 bits	16#0–16#FFFF	-21	DT9979
	CRC-32^{4), 5 )}	CRC of relevant program code	32 bits	16#0–16#FFFFFFFF	-23	DDT9977
		CRC of configuration			-25	DDT9975
		CRC of positioning			-27	DDT9973
		CRC of data recording			-29	DDT9971
		CRC of POUs			-31	DDT9969
		CRC of user libraries' POUs			-33	DDT9967
		CRC of SFC structure			-35	DDT9965
		CRC of user addresses, variable names, data types, i.e. only global variables with explicit user addresses			-37	DDT9963
		CRC of system addresses, variable names, data types without addresses of global variables with explicit user addresses without addresses of external variables without addresses of function variables⁶⁾			-39	DDT9961
Tail	CRC-16^{8 )}	CRC-16 of metadata content	16 bits	16#0–16#FFFF	-40	DT9960

¹⁾	User data can be entered by the user in Extras > Options.
²⁾	System data are generated by the compiler.
³⁾	Last change dates are expressed in seconds after 1.1.2001
⁴⁾	CRC values are characteristic for certain data: If two CRC values are equal, then the data they represent are equal
⁵⁾	All CRC value calculations are based on the text information of the according objects. CRC values are affected by the following user actions: Adding or removing comments, inserting or deleting spaces in header or bodies of the POUs Renaming variable names or changing the data types. These changes affect the CRC values of the addresses, variable names, and data types so that addresses, variable names, and data typs are indicated as different from the PLC. The option Download program code changes to PLC is preselected as long as critical changes to the program code can be excluded. Critical changes can be excluded if there are for example changes either only to the program code or only to addresses, variable names or data types.
⁶⁾	Please consider that there can be different addresses from the same project depending on incremental compile or compile all. To be sure that all addresses are kept, always use Project > Compile all... or
⁷⁾	Compile options, code generation Bits 0, 1: Initialization of retain data: 0: Initialize all retain data by Control FPWIN Pro7 after program download 1: Keep values of global retain variables which have been assigned an explicit address. Initialize all other retain variables by program code 2: Initialize all retain variables by program code Bit 4: Indexed function block instances
⁸⁾	Metadata tail CRC-16 is used to check whether the metadata are valid. The generator polynomial is CRC-16 Modbus RTU x16+x15+x2+1

NOTE

Metadata require 42 registers in the uppermost DT hold area just below the cold-start-detection registers.
The number of cold-start-detection registers in the uppermost DT hold area depend on the PLC type:

Number of requested cold-start-detection registers	PLC types
2	FP0R, FP-X, FP-XH, FP0H, FPS
4	FP2SH-120k (because of additional task Programs 2)
4	FP7 (because of additional task Periodic interrupt)