LP-AM243: How to send explict message using the Enthernet/IP adapter example.

Hi Hang,

We explicitly do not have a implementation for sending error message in our example. In my opinion neither does there is any recommendation from ODVA in EIP spec.

Hang Yang said:

 My customer would like to send some error messages from Ethernet/IP adapter to scanner, they would like to send it through tcp, or explicit message

Taking up on the same recommendation, it will be easier to implement it by sending a TCP packet. For sending the TCP packet you can directly use LWIP APIs and send the packet. 

Apart from that I have some questions regarding: how will scanner come to know about that a particular packet needs to be treated as error message packet,

Could you please ask customer if they have some prior implementation around it.

Hi  Nilabh and Hang,

As you know,the O->T ENIP messages carry datas output from plc to EIP card.

In our application,those datas will be written into inverters' funcodes by EIP card.

There is a situation that some data exceeds the limitation of the written funcodes and the EIP card will receive the abnormal information from inverter.

In this case,there should be a mechanism transmitting error messages to EIP scanner from adapter.The aim is to inform plc that some O->T data is written failed. 

so,how can we realize the mechanism utilizing the current EIP stack?

Hi  sigong 

Allow me sometime to discuss this internally and see if we can suggest some way to do it.

As per what I read in this odva document it recommends:EtherNet/IP Quick Start for Vendors Handbook (odva.org)

Additional protocols: Do you need to support additional TCP/IP protocols? Many devices have found an embedded web server to be valuable mechanism to provide diagnostic information. DHCP is the recommended mechanism for initial IP address configuration out-of-box. You should consider additional protocol support when evaluating development platforms. It is necessary to ensure that prioritization within the node assumes that handling of the additional protocols (such as HTTP or SNMP) does not interfere with the prompt handling of EtherNet/IP I/O connections

Hi  Nilabh,

Accroding to the statement,it seems that realizing the machanisim needs another way than just the EIP stack.

This is not our original intention and we'll review this request.

Thank you.