Description
The EtherNet/IP Adapter firmware implements all CIP objects and services to build an EtherNet/IP Adapter device that can pass ODVA's conformance test. This also requires a correctly behaving host application in addition.
Configuration
The stack can be configured via data base files (generated with Hilscher's Sycon.net or Communication Studio) or via the mailbox interface (refer to the corresponding API manual).
During connection establishment to an EtherNet/IP Scanner (Master) it is possible to pass configuration data to the application. Depending on the configuration data the application can reject the incoming connection.
Implicit Messaging (Cyclic data)
The stack offers an interface to access the cyclic data.
The cyclic data is is available in the dual-port memory (DPM) which can be accessed by a host application.
Explicit Messaging (Acyclic services)
Acyclic services to 'build in' CIP objects (CIP objects that belong to the dafault object set supported by the EtherNet/IP Adapter stack) are handled by the stack itself. If the application needs to store remanent paramters related to those object, this will be indicated by an appropriate indication packet.
In addition to the 'build-in' CIP objects other CIP objects or vendor specific objects can be registered at the stack, e.g. to support special CIP profiles. In that case all acyclic services need to be handled by the application.
Restrictions
- CIP Motion is not supported
- CIP Safety is not supported
- CIP TAGs are not supported
Key Features
- Device Level Ring (DLR) - Media Redundancy
- Address Conflict Detection (ACD)
- Connection Classes: 1, 3
- Connection Application Types: Exclusive Owner, Input Only, Listen Only Connections
- Explicit Messaging
- Quality of Service
- Object model can be extended by implementing own CIP objects (necessary to support CIP profiles)
- CIP Sync
- QuickConnect (Fast Startup)
- NULL-ForwardOpen
Supported Protocols
- TCP/IP, UDP/IP
- DLR
- DHCP / BOOTP
- IEEE 802.3
- IEEE 802.1Q
- LLDP
- SNMP
Technical Data
| Feature | Description |
|---|---|
| Maximum number of input data | 504 bytes per assembly instance |
| Maximum number of output data | 504 bytes per assembly instance |
| Maximum number of assemblies | 10 |
| IO Connection Types (implicit) | Exclusive Owner, Listen Only, Input only |
| IO Connection Trigger Types | Cyclic, minimum 1 ms* |
| Explicit Messages | Connected and unconnected |
| Unconnected Message Manager (UCMM) | supported |
| Max. number of connections | Class 1: 5 Class 3: 10 UCMM: 10 |
| Max. number of user specific objects | 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 |
Configuration
Configuration is done by sending packets to the stack or by using SYCON.net configuration database.
Diagnostic
The stack supports common diagnostic in the dual-port-memory for loadable firmware.