Emerson Exchange 365

• Not Answered

Establishing a communication netTAP NT 100 from Hilscher with DeltaV

Hello everyone,

 

I have Problems with connecting a gateway netTAP NT 100 from Hilscher into DeltaV. The communication will be established through EtherNet/IP. Communication is configured, and working properly (I see the good status in Diagnostics). But if I configure the exchangable data, it shows me Bad status and not comunicating anymore.

 

Does anyone has experience with gateways netTAP NT 100 from Hilscher? Can anyone help me with configuration of TCP IP?

 

We have tryed different options but the device doesnt want to communicate. The data set is set up as per gateway settings with matching on both sides. 

KoBriZo

• 27 Jul 2022 4:20 PM
• Cancel

7 Replies

• Matt Forbis

  

  • 28 Jul 2022 3:54 PM

  I haven't used one of these gateways, however I have quite a bit of experience with Ethernet/IP interfacing to DeltaV. Can you give me a bit more information as to how you are planning to use the gateway? I suspect there is a mismatch, but with the manual I found, without knowing the details of which protocols and your intended use case, I won't be able to offer much help. If there is an EDS file you have from the gateway as well, that could also be helpful and I can look directly at it to figure out some of the DeltaV communication parameters also.

  • Cancel
• KoBriZo

  

  • 28 Jul 2022 4:14 PM

  In reply to Matt Forbis:

  Hi Matt,

  I have a Wireshark File. It can probably help you to analyse what is going on in network. WiresharkDaten.zip

  • Cancel
• Matt Forbis

  

  • 28 Jul 2022 4:53 PM

  In reply to KoBriZo:

  Hi,
  
  It looks like your EIOC is 0.111 and your gateway is at .0.1. The error message the gateway is returning is an "Invalid Target to Originator size" (That's the Input Bytes in DeltaV). It looks like the device is returning a max value of 8, however it looks like your connection was asking for 4 bytes. That however does not align with the 105 that I see in the screenshot you posted. Can you upload a screenshot of the deltav for the wireshark capture you attached to make sure I'm interpreting correctly. In any case, I think there might be something on your gateway not configured quite correctly as either 4 or 8 bytes is probably not going to contain all the data you would be passing through this, though I'm not familiar with this device.

  • Cancel
• KoBriZo

  

  • 29 Jul 2022 5:54 AM

  In reply to Matt Forbis:

  

  I am forwarding actual configuration screenshots to you which is matching to Wireshark Data. We desided to start with small ammount of data in order to analyze how it works.

  • Cancel
• Matt Forbis

  

  • 29 Jul 2022 1:41 PM

  In reply to KoBriZo:

  Hi!
  
  Can you confirm that this is setup as the DeltaV EIOC/PK as the master talking through this device to a Profinet Slave device? I think that's what I'm seeing, but want to confirm that piece of the setup as well.

  • Cancel
• KoBriZo

  

  • 2 Aug 2022 3:58 PM

  In reply to Matt Forbis:

  Hello,
  we have found the Problem. The Gateway (Slave device) has got the predefined set of data (4 bytes), which needs to be defined in Master Device as an Input signal. For example, if you need to exchange 500 Bytes, you have to define in master confoguration 504 bytes. At the same time this offset is not required to be configured in slave device.
  
  With that solution we have got Good Status of each Dataset configured in DeltaV.

  • Cancel
• Matt Forbis

  

  • 2 Aug 2022 6:58 PM

  In reply to KoBriZo:

  Glad to hear you got it working!

  • Cancel