hilscher netX 90, Production Manual

Page: 29 / 70

Software architecture 29/70
FDL Content: OEM identification
The following table shows the section of the FDL that holds the OEM
identification ; i.e. the OEM-specific product identification data. The OEM
can use these fields for his purpose.
Note:
Usage of these data fields by the OEM is optional. If used, the OEM
has to define appropriate values for this data. The application
firmware can (indirectly) read this data from the FDL during start-up
of the device by means of the
Device Data Provider Get
service offered by the communication firmware.
Offset Relative
offset Size
(bytes) Data type Name Description/comments/values
256 0 4
UINT32 OEM data
option flags This bit field enables the evaluation of the OEM
identification data by the communication firmware.
0
The COM FW does not evaluate the
OEM identification data. The APP FW
can read (and use) this data via
Device Data Provider Get
service of the COM FW.
All other
values reserved
Note : Current COM firmware versions do not
evaluate these parameters anyway, but we still
advise you to set this field to
0
in order to avoid
conflicts with upcoming firmware versions that
might be able to evaluate this section.
260 4 28
CHAR[28] OEM serial
number Serial number of the device as string (e.g.
20053
or
SC-D5SF5005
). Null-terminated c string
288 32 32
CHAR[32] OEM order
number Order number of the device as string (e.g.
1544.100
or
6ES7 511-1AK00-0AB0
). Null-
terminated c string
320 64 16
CHAR[16] OEM hardware
revision Hardware revision as string (e.g.
3
or
V1.5
). Null-
terminated c string
336 80 32
CHAR[32] OEM
production
date/time Production date/time.
UTC (Universal Time Coordinated) without TZD
(time zone designator, always 'Z') and no fraction
of a second, e.g.
2012-10-24T07:36:17Z
Null-terminated c string
368 112 12
UINT8[12] OEM reserved
fields Reserved fields.
Note : Currently not used, set to
0
380 124 112
UINT8[112] OEM specific
data Vendor specific data. This field can be used to
store any kind of information defined by the OEM.
If used, OEM has to define content, structure,
values and their meaning.
Table 15: FDL Content: OEM identification
netX 90 | Production guide
DOC190101PG03EN | Revision 3 | English | 2019-07 | Released | Public © Hilscher 2019