Description

The DeviceNet Slave stack has implemented the required state machines and services to build a DeviceNet Slave Device.
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.

Cyclic data

The stack offers an interface to access the cyclic data as well as a packet based interface for configuration, acyclic services and diagnostic.

Acyclic services

Acyclic services requested by an DeviceNet Master indicated to a registered application via the mailbox interface. If no application is registered at the stack all acyclic requests for none-standardized objects will be responded with an error by the stack automatically.

Key Features

Full cyclic data exchange supported (Poll, Change of State, Cyclic, Bitstrobe)
Diagnostic
- Common and extended diagnostic via dual port memory
- Stack diagnosis via packet API
Configuration
- Packet API based configuration by host application
- Data base configuration by configuration tool Sycon.net (only netX 90 use case C with external flash memory)
Acyclic service supported
Fragmentation supported
Module Network Status Objects
Multiple assembly support
Baudrate and node-ID over network configuration supported
Rotary switch support
Attribute change indication support
Semiconductor device profile supportable by host application

Technical Data

Feature	Description
Maximum number of cyclic input data	255 bytes
Maximum number of cyclic output data	255 bytes
Acyclic communication	Get_Attribute_Single/All max. 240 bytes per request Set_Attribute_Single/All max. 240 bytes per request
Baud rates	125 kBits/s, 250 kBit/s, 500 kBit/s Auto-detection mode is not supported
Connections	Poll Change-of-state Cyclic Bit-strobe
Explicit messaging	supported
Fragmentation	Explicit and I/O
Message body format	8/8
Data transport layer	CAN
UCMM	not supported
Quick Connect	not supported

Firmware Functions

The DeviceNet Slave 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	TBD		TBD
Host Interface	Dual Port Memory interface with following channels: Channel 0 - DeviceNet Slave Protocol API exchange cyclic IO data use acyclic protocol services
Diagnostic Interface	netX Diagnostic and Remote Access is supported via netX90 COM UART
Integrated Flash File System	N/A	N/A	Power-fail safe flash file system on external SPI flash is used
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:
Device Data	netX90 internal flash		netX90 internal flash
Firmware Transfer	via Host Interface (DPM, SPM) 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	N/A	to netX flash file system located on external SPI Flash
Firmware Update	Firmware check and installation supported through calling the Maintenance Firmware Note: netX90 Use Case C firmware requires Maintenance Firmware v1.3.0.0 or later.
Firmware Update	from internal netX90 flash	N/A	from Flash File System located on external SPI Flash
Configuration	by sending configuration packets to the firmware via Host Interface
Configuration	N/A		or by using Communication Studio configuration database file from local flash file system
Tag List Options	Firmware supports certain modification of the functionality via Tag List, in particular: UART Diagnosis Interface
HW Sync Signal	N/A
Protocol Specific LED Indicators	Network specific status indicators with COM0 / COM1 LEDs: NS: Network Status MS: Module Status
Secure Boot	supported by DeviceNet Slave V5.2.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

Browser not supported