Technical Data - V3
- Kai Michel
Description
The EtherNet/IP Scanner firmware implements all CIP objects and services to build an EtherNet/IP Scanner device that can pass ODVA's conformance test.
This in addition requires a correctly behaving host application that interfaces to the firmware through the Dual Port Memory (DPM) interface.
Configuration
The EtherNet/IP Scanner firmware can be configured via data base files (generated with Hilscher's Sycon.net or Communication Studio) or via the DPM's mailbox interface (refer to the corresponding API manual).
Implicit Messaging (Cyclic Data)
Through the DPM the host application has access to the process data that is consumed and produces by the firmware.
Explicit Messaging (Acyclic Data)
Acyclic services received from the network and addressing 'build in' CIP objects (CIP objects that are part of the firmware's default CIP object model) are handled by the firmware itself.
There is the possibility to extend the default object model by additional CIP objects, e.g. to support CIP profiles or vendor specific CIP objects.
Key Features
- Cyclic I/O data (Implicit Messaging): class 0 / class 1
- The EtherNet/IP Scanner firmware can be configured to be Target and/or Originator of an IO connection
- Acyclic data (Explicit Messaging): Unconnected / Connected (class 3)
- The EtherNet/IP Scanner firmware can be Messaging Server and Client
- Connection Application Types: Exclusive Owner, Input Only, Listen Only
- Trigger Types: Cyclic, Change of State, Application Triggered
- Device Level Ring (DLR) - Media Redundancy
- Address Conflict Detection (ACD)
- Quality of Service (QoS)
- CIP Sync
- QuickConnect (Fast Startup)
- NULL-ForwardOpen
- CIP Safety "Ready" (provides all necessary features and interfaces to attach a CIP Safety stack on top)
- Firmware built-in CIP Object model can be extended by additional CIP objects (e.g. to support CIP profiles)
Supported Protocols
- TCP/IP, UDP/IP
- DLR
- DHCP / BOOTP
- IEEE 802.3
- IEEE 802.1Q
- LLDP
- SNMP
- PTP (Precision Time Protocol)
Technical Data
The technical data of the individual available firmwares may differ slightly. Therefore, the below table only provides a rough overview of the supported features.
Note: For a detailed listing of the technical data, please refer to the data sheet of the individual firmware. You can find them in the "Resources" section in the specific firmware version page.
| Feature | Description |
|---|---|
| Maximum number of input data per assembly instance | 504 bytes |
| Maximum number of output data per assembly instance | 504 bytes |
| Maximum number of assemblies (firmware dependent) | 128 |
| IO Connection Types (implicit) | Exclusive Owner, Listen Only, Input only |
| IO Connection Trigger Types | Cyclic, minimum 1 ms* |
| Explicit Messages | Connected (class 3) and unconnected |
| Unconnected Message Manager (UCMM) | supported |
| Number of Target Class 1 connections | 32 |
| Number of Target Class 3 connections | 8 |
| Number of Originator Class 1 connections | 64 |
| Number of Originator Class 3 connections | 64 |
| UCMM Client Connections | 10 |
| UCMM Server Connections | 10 |
| Max. number of user specific objects (firmware dependent) | 20 |
| Predefined standard objects | Identity Object (0x01) |
| DHCP | supported |
| BOOTP | supported |
| Baud rates | 10 and 100 MBit/s |
| Duplex modes | Half Duplex, Full Duplex, Auto-Negotiation |
| MDI modes | MDI, MDI-X, Auto-MDIX |
| Data transport layer | Ethernet II, IEEE 802.3 |
| Address Conflict Detection (ACD) | supported |
| DLR (ring topology) | supported |
| Integrated switch | supported |
| CIP Reset services | Identity Object Reset Service of Type 0 and 1 |