Technical Data - V5

Description

The PROFINET IO Device stack V5 has implemented the required state machines and services to build a PROFINET IO Device. It can be used to build a complete PROFINET IO Device which requires a correctly behaving application.
The stack on its own just provides services that neet to be handled correctly by an application for certification and correct behaviour in the field, e. g. remanent storing of NameOfStation.

Configuration

The stack offers a mailbox interface for configuration. A basic configuration has to be set using a Set Configuration packet first. Afterwards at runtime it is possible to change the submodule configuration by using services to plug or pull submodules.
During connection establishment to an IO Controller the stack compares its current submodule configuration to the expected one of the IO Controller. Differences are indicated to a registered application so that the application is able to adjust the stacks submodule configuration, if the application model allows such a handling.

Cyclic data and I/O state

The stack offers an interface to access the cyclic data as well as a packet based interface for configuration, acyclic services and diagnostic.
The cyclic data is available in the dual-port memory which can be accessed by a host application.

The stack supports different ways of handling the submodul related IO status bytes IOPS (Input Output Object Provider State) and IOCS (Input Output Object Consumer State). Either they are completely handled by the stack or handled by the application. In case the stack handles these IO status bytes they are always set to "good".
This IOxS is part of the cyclic data and not set/get by packets but by the mechanisms for cyclic data.

Acyclic services

Acyclic services requested by an IO Controller with a Read Record or Write Record are indicated to a registered application via the mailbox interface. If no application is registered at the stack all acyclic requests for none-standardized datasets will be responded with an error by the stack automatically.
The stack offers automatic handling of I&M functionality (read and write). However it is possible for application to disable this automatic handling and handle I&M on its own if required.

Alarms and diagnosis

The stack offers a mailbox interface for the application to generate alarms and add diagnosis entries to the stack.

Key Features

• Cyclic communication
• Acyclic communication
• Shared Device
• Fast Startup
• Runtime adjustment of submodule configuration
• IRT (for most firmwares)

Detailed technical data

Protocol Technical Data

Restrictions

• RT over UDP not supported
• Multicast communication not supported
• Only one device instance is supported
• DHCP is not supported
• The amount of configured IO-data influences the minimum cycle time that can be reached.

• Only 1 Input-CR and 1 Output-CR per AR are supported

• The amount of usable submodules is reduced by 1 for each used different API (in case more than 2 APIs are used in parallel).

• Little endian byte order for cyclic process data is not supported

• System Redundancy (SR-AR) and Dynamic Reconfiguration (formerly known as Configuration-in-Run, CiR) are not supported. (*)

• The usage of PROFINET CombinedObjectContainer
  • is not supported at all (for standard firmware)

  • is not supported for user application parameters (for SystemRedundancy enabled firmware) (*)

• SharedInput is not supported
• MRPD is not supported

• DFP and other HighPerformance-profile related features are not supported

• NXLOM is not available
• The stack does not support usage of PDEV submodules (InterfaceSubmodule or PortSubmodule) outside of slot 0. In addition the InterfaceSubmodule is only supported in subslot 0x8000 and the PortSubmodules are only supported in subslots 0x8001 and 0x8002.

• In case of using a firmware including the feature System Redundancy, the combination of the features “System Redundancy” and “Shared Device” is not supported. Recommendation: Set “NumberOfAdditional IO ARs” in tag list to 1.x

(*) A separate PROFINET IO-Device firmware is available that support the features System Redundancy and Dynamic Reconfiguration. To use the firmware requires a separate license agreement.

Firmware Functions

The real-time protocol stack is fully integrated into a netX firmware for specific use case in order to provide a common set of netX firmware functions accross different protocol variants:

Firmware Variants	Use Case A	Use Case B	Use Case C
Use Case summary	netX90 COM CPU firmware for small footprint, low cost and function optimized slave devices no external SPI / SQI Flash required for COM CPU no external SDRAM required for COM CPU	same as Use Case A, but netX90 APP CPU uses external SPI Flash may use external SDRAM	full featured firmware for highest function requirements external SDRAM is required for COM CPU external SPI Flash is required for COM CPU
netX support	netX90	netX90 with ext FLASH	netX90 with ext SDRAM and ext FLASH
FW structure
Host Interface	Dual Port Memory interface with following channels: Channel 0 - Real-Time Ethernet Protocol API exchange cyclic IO data use acyclic protocol services Channel 1 - Network Services Socket API - Enables opening a communication socket using the integrated TCP/IP stack resources, i.e. same MAC address Ethernet (NDIS) API - Enables sending and receiving Ethernet frames using a separate MAC address, i.e. application host with its own TCP/IP stack Web API - Enables forwarding specific URL (HTTP GET/POST) requests to user applications, e.g. to build custom webpage contents
Diagnostic Interface	netX Diagnostic and Remote Access is supported via COM UART
Integrated Flash File System	N/A	N/A	power-fail safe flash file system on external SPI flash
Remanent Data Storage	Power-fail safe storage of up to 16KB of protocol remanent data in netX90 internal flash		Power-fail safe storage of protocol remanent data in dedicated partition in extenal SPI flash. Size and position of remanent storage area shall be configured in FDL.
Device Data	device production data (Serial number, MAC address, production data etc.) shall be stored in FDL in netX90 internal flash
Firmware Transfer	to internal netX90 flash ... via integrated web server via Host Interface (DPM, SPM) Note: due to limited size (max. 380KB) of FW update area in internal flash, only following files can be transfered: individual firmware files (i.e. comfw.nxi or appfw.nai) if the size of the a file is less that 380KB max. 380KB big FWUPDATE.zip file with predefined structure	to the host application... via integrated webserver and Web API  (DPM Channel 1) host application need to handle storage of the firmware in external SPI flash	to netX flash file system located on external SPI Flash
Firmware Update	Firmware check and installation supported through calling the Maintenance Firmware
	from internal netX90 flash	from external SPI flash	from Flash File System located on external SPI Flash
Configuration	by sending configuration packets to the firmware via Host Interface
	N/A	N/A	or by using Communication Studio configuration database file from local flash file system
Integrated Basic Webserver	The basic web server has the following features: \netx  - Provides a graphical user interface to other functions (diag, firmware, reset, etc.)       \netx\diag  - Provides information on the netX device (current uptime, MAC address, device   number, serial number, etc. \netx\firmware  - Enables uploading a new firmware update file to netX flash \netx\reset  - Initiates a netX reset cycle, i.e. to install a newly uploaded firmware \  - URL requests are forwarded to the user application via DPM (web interface API)
Webserver extension	N/A	N/A	Basic web server is extended with functions that provide access to the content files on a local Flash file system (SQI Flash). \netx\files  - Enables streaming of custom web content according to media types (i.e. txt, js, xhtml, jpeg, json, etc.) located in the Flash file system
Tag List Options	Firmware supports certain modification of the functionality via Tag List, in particular: Webserver port number or deactivation Activation of Ethernet Interface in DPM Channel1 Selection of target for remanent data storage (netX local or external host) Profinet protocol stack configuration parameters
HW Sync Signal	supported via netX signal XC_TRIGGER0/1
Protocol Specific LED Indicators	Network specific status indicators with COM0 / COM1 LEDs: SF: System Failure BF: Bus Failure
Secure Boot	supported by PROFINET IO-Device V5.5.0.0 and later, see Support of Secure Boot with netX90 for more details
Limitations	FW functions are limited by available internal RAM / Flash COM firmware size is limited to max. 500KB	FW functions are limited by available internal RAM / Flash COM firmware size is limited  to max. 880KB