Versions Compared

Old Version 8

changes.mady.by.user Kai Michel

Saved on

compared with

New Version Current

changes.mady.by.user Kai Michel

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.


toc
Section


Column
width70%

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 in addition requires a correctly behaving host application that interfaces to the firmware through the Dual Port Memory (DPM) interface.

Configuration

The stack 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).
During connection establishment to an EtherNet/IP Scanner (PLC), it is possible to pass configuration data to the host application.

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

Excerpt
  • Cyclic I/O data (Implicit Messaging): class 0
or
  • / class 1
Explicit Messaging 
  • Acyclic data (Explicit Messaging): Unconnected / Connected (class 3)
  • Connection Application Types: Exclusive Owner, Input Only, Listen Only
  • Trigger Types: Cyclic, Change of State, Application Triggered
  • Device Level Ring (DLR) - Media
RedundancyCIP Sync
  • Redundancy 1)
  • Address Conflict Detection (ACD)
  • Quality of Service (QoS)
  • Object model can be extended by implementing own CIP objects (necessary to support CIP profiles)
    • CIP Sync 1)
    • QuickConnect (Fast Startup)
    • NULL-ForwardOpen
    • CIP Safety "Ready"
    for CIP Safety
    • (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
    • DLRDLR 1)
    • DHCP / BOOTP
    • IEEE 802.3
    • IEEE  802.1Q
    • LLDP
    • SNMP
    • PTP (Precision Time Protocol) 1)

    Technical Data

    The technical data of the individual available firmwares differ slightly. Therefore, the below table only provides a rough overview of the supported features.

    Info

    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 on the specific firmware version page.

    Firmware data sheets are available for version V3.8.0.0 and higher.


    FeatureDescription
    Maximum number of input data per assembly instance

    504 bytes

    Maximum number of output data per assembly instance504 bytes
    Maximum number of assemblies
    (firmware dependent)    		10
    IO Connection Types (implicit)

    Exclusive Owner, Listen Only,

    Input only
    IO Connection Trigger Types

    Cyclic, minimum 1 ms*
    Application Triggered, minimum 1 ms*
    Change Of State, minimum 1 ms*

    Explicit MessagesConnected (class 3) and unconnected
    Unconnected Message Manager (UCMM)supported
    Max. number of connections
    (firmware dependent)

    Class 0 / Class 1: 5

    Class 3: 10

    UCMM: 10

    Max. number of user specific objects
    (firmware dependent)    		20
    Predefined standard objects

    Identity Object (0x01)
    Message Router Object (0x02)
    Assembly Object (0x04)
    Connection Manager (0x06)
    DLR Object (0x47) 1)
    QoS Object (0x48)
    TCP/IP Interface Object (0xF5)
    Ethernet Link Object (0xF6)
    LLDP Management Object (0x109)
    Time Sync (0x43) 1)

    DHCPsupported
    BOOTPsupported
    Baud rates10 and 100 MBit/s
    Duplex modesHalf Duplex, Full Duplex, Auto-Negotiation
    MDI modesMDI, MDI-X, Auto-MDIX
    Data transport layerEthernet II, IEEE 802.3
    Address Conflict Detection (ACD)supported
    DLR (ring topology)
    supported
    supported 1)
    Integrated switch
    supported
    supported 1)
    CIP Reset servicesIdentity Object Reset Service of Type 0 and 1



    Column
    width30%


    Panel
    titleOn this page

    Table of Contents

    Panel
    titleOn this page




    1) Supported by 2 port firmware variants only