Technical Data - V5
- Former user (Deleted)
- Yuriy Zavgorodniy
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
Set_Attribute_Single/All
|
| 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 |
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
| same as Use Case A, but netX90 APP CPU
| full featured firmware for highest function requirements
|
| netX support |
|
|
|
| FW structure | TBD | TBD | |
| Host Interface | Dual Port Memory interface with following channels:
| ||
| 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: | ||
|
| ||
Firmware Transfer |
due to limited size (max. 380KB) of FW update area in internal flash, only following files can be transfered:
| to netX flash file system located on external SPI Flash | |
| Firmware Update | Firmware check and installation supported through calling the Maintenance Firmware
| ||
| N/A |
| |
| Configuration | by sending configuration packets to the firmware via Host Interface | ||
| 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:
| ||
| HW Sync Signal | N/A | ||
| Protocol Specific LED Indicators | Network specific status indicators with COM0 / COM1 LEDs:
| ||
| Secure Boot | supported by DeviceNet Slave V5.2.0.0 and later, see Support of Secure Boot with netX90 for more details | ||
| Limitations |
|
| |
Note: netX90 Use Case C firmware requires Maintenance Firmware v1.3.0.0 or later.