Basic Operation 14 (258)
3.4.2 Process Data
Mapping an ADI to Write Process Data results in PROFINET input data, and mapping an ADI to
Read Process Data results in PROFINET output data. Consistency over all I/O data mapped on
PROFINET is guaranteed.
See also...
• Real Identification (RI), p. 19
The order in which ADIs are mapped to Process Data is significant and must be
replicated in the IO Controller when setting up the network communication (i.e.
modules must be set up in the same order, size and direction, as the mapped
ADIs).
3.4.3 Caveats
The length parameter in the Record Data request specifies the number of bytes to read/write.
• When reading more data than the actual size of the ADI, the response will only contain the
actual ADI data, i.e. no padding on the data is performed by the module.
• When writing to an ADI, the length parameter is not checked by the module, i.e. the host
application must respond with an error if the length differs from the actual size of the re-
quested ADI.
See also..
• Application Process Instances (API), p. 18
3.5 Web Interface
The built-in web server can be used to provide rich, dynamic content, by means of JSON and
SSI scripting. This enables access to information and configuration settings within the file
system.
Web server content resides within the module’s file system. This means that it can be accessed
and customized as needed using a standard FTP client.
See also...
• File System, p. 16
• FTP Server, p. 36
• Web Server, p. 38
• Server Side Include (SSI), p. 45
• JSON, p. 65
Anybus
®
CompactCom
™
40 PROFINET IRT Network Guide SCM-1202-023 EN 1.8
To Next Page
Loading...
Need help?
General
