Topic: DMD0498 EtherNet/IP Server / Adapter Configuration |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
The EtherNet/IP Server / Adapter Configuration dialog sets up the EtherNet/IP Explicit Server / Implicit Adapter in any DM1E CPU. The EtherNet/IP Server / Adapter can use either the on-board Ethernet port or a BX-P-ECOMEX POM. The EtherNet/IP Server /Adapter can support up to 16 concurrent sessions with Explicit Unconnected EtherNet/IP Clients An explicit unconnected message client initiates request/response oriented communications with other devices. Message rates and latency requirements are typically not too demanding. Examples of explicit message clients are HMI devices, programming tools, or PC-based applications that gather data from control devices. and / or Implicit scanners - the default configuration allows 4 concurrent connections.
Note: configuring a Connected Implicit Scanner is done in the I/O Configuration.
The Enable EtherNet/IP Server / Adapter option completely enables and completely disables the CPU's EtherNet/IP Server /Adapter device driver. If this option is unchecked the CPU will not respond to any EtherNet/IP Client requests. Once this Server has been enabled, runtime status of the EtherNet/IP Server / Adapter can be monitored through the built-in structure $IntEIPServer which has the following members:
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Once the EtherNet/IP service is enabled, clicking the EtherNet/IP Settings... button will open the following dialog to configure the EtherNet/IP Server / Adapter's operating parameters.
Server Settings are selections that control how the EtherNet/IP Server /Adapter handles connections from Explicit Message clients and Implicit Scanners :
When Used by EtherNet/IP Explicit ClientsThere can be up to 8 Data Blocks made available to EtherNet/IP Explicit Message Clients. This section specifies the which of those 8 data blocks are available, the read and / or write access for each block, and then configures which type and location of the CPU's memory each of the blocks will be mapped to. A Block can be accessible by both an Explicit Message client and an Implicit Scanner.
Check Enable for a block to make it accessible to either the EtherNet/IP Explicit Message Clients.
When Used by EtherNet/IP Implicit Scanners (BRX CPUs only)There are 4 available I/O Adapters. Each of the 4 I/O Adapters consumes two of the 8 available blocks. The first block for each I/O Adapter is the Input (Target to Originator), the second block is the Output (Originator to Target).
Do-more Mapped Memory specifies the memory location that contains the data that will be accessed when requests for this Block's Class / Instance / Attribute / Connection Point are received.
Select Memory Block if this Block's data resides in one of the predefined Numeric or Bit memory blocks.
Select Heap Item if this Block's data resides in a Heap Item. The primary use of this selection is with User Data Types. Select one of the existing Heap Items from the drop-down list of available Heap Items.
The Mapped Range & Size fields display the currently selected range of Elements the size of the selected Element range in Bytes. Click OK to save the configuration changes that have been made and return to the main CPU Configuration, or Cancel to discard any changes that have been made and return to the main CPU Configuration.
Click the Generate EDS File button to create an EDS (Electronic Data Sheet) file that is appropriate for the Blocks that are enabled and the configuration of those blocks.
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
EtherNet/IP Supported PathsThe EtherNet/IP Explicit Message Server supports the following Paths: (Class / Instance / Attribute)
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
EtherNet/IP Error CodesThe following charts show the error responses that will be returned by the EtherNet/IP Server (Adapter) / Adapter:
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
See Also:
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Related Topics:EIPMSG - Send EtherNet/IP Message
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|