Emerson Exchange 365

little experience with profibus communicating with Delta V I need some assistance

I am trying to use an LDT module, I have included a screenshot, can anyone tell me the relevance with the Input/Output/Configuration Instance? 

Tom Light

• 14 Jun 2024 11:49 AM
• Cancel

4 Replies

• Matt Forbis

  

  • 14 Jun 2024 1:10 PM

  The subject mentions Profibus, but this looks like an Ethernet/IP configuration screen? Traditional Profibus is done with a dedicated card and not the ethernet port. If you are trying to do Profinet, you would need to change the protocol type at the Port level.
  
  All that being said, if you are trying to do Ethernet/IP, the Instance parameters tells the device what type of format the data is in. For somethings like a VFD, 1,2,6 are common because the device itself has a configurable data layout. For other devices such as Overload relays, you might have a few fixed formats to choose from and the number that is put in here comes from the Device Manual in most cases.
  
  If you have a more specific example you need help with, please reply back with that, and I'll see what I can do to help.

  • Cancel
• Andre Dicaire

  

  • 14 Jun 2024 3:23 PM

  In reply to Matt Forbis:

  This is an EtherentIP configuration dialog. As Matt points out, this is not Profibus.
  
  Profinet is only supported on the PK controller starting at V15FP1. It is an additional protocol that will run along with EthernetIP OR ModbusTCP. It does not use the same data structure we have become accustomed to in the EIOC and PK P01 ports. I recently explored this protocol. Some interesting features in this protocol, including the ability to provisioning the end device's IP address. Also, in v15 the configuration of the PK controller's IOP ports has been revamped, and now allows subnets to be predefined on the ports for the protocols you will be using. A big feature is the bonding of a primary and secondary port so that they can be used on a single subnet. This is primarily for the Profinet MRP topology, but it is also allows for EtherentIP or ModbusTCP, and allows the PK controller to have a redundant connection to a simplex IO bus.
  
  As for your question on the instance assemblies, they would be documented in the device literature and you can choose which one suits your needs (data they provide). In some cases, you might want to configure a second LDT to another set of assemblies if the data you seek is not available in a single assembly.
  
  Once you've defined the Data structure and content of the LDT, you will configure "signals" based on the data contained: booleans, integers, Floats. BOL will provide help there. The signal configuration is very similar to DeviceNet card and also Profibus. Each data value has a starting register and start bit with the length defined by the data type. The device's documentation lays out the content or map of the data and you can expose the data to DeltaV as per the documentation or however you want. Typically, the data is exposed based on the device documentation for consistency.
  
  If you have Profibus, you are in the wrong configuration screen.

  Andre Dicaire

  • Cancel
• Andre Dicaire

  

  • 14 Jun 2024 3:26 PM

  In reply to Andre Dicaire:

  PS, The input and output size refer to the number of bytes each instance assembly contains. This needs to match the size of the selected Instances as per the device documentation. I'm not sure the Configuration Assembly is used in DeltaV. If it is used, I don't know where or for what.

  Andre Dicaire

  • Cancel
• Matt Forbis

  

  • 14 Jun 2024 5:27 PM

  In reply to Andre Dicaire:

  The Configuration Assembly is just passed to the device. DeltaV does not have the capabilities to configure the device remotely using it, but certain devices will not function if the value is not passed, so that's why it was added in late v13 / early v14 timeframe.

  • Cancel