Emerson Exchange 365

• Not Answered

Devicenet Explicit Messaging

I have a device whose assembly object class does not include the information I desire.   From what I can gather, when adding devicenet signals in Explorer, it uses the assembly object based on the EDS file and signal direction specified.  However, I would love to be able to add signals/ device tags here for other object class items.  

I found that there was supposed to be explicit messaging via external references to particular parameters, however this did not work for me.   I can give details, but at this point I'm looking for a more general or better solution.  I decided to try accessing the device diagnostic data that was already being made available through Diagnostics.. at least then I had proof of data.  However, this data did not come across in the module either.  I confirmed the class ID, instance and attribute IDs with the device's programming manual. I have confidence I'm not at fault there.

Any suggestions?

Thanks

TreyB

• 12 Dec 2017 8:59 PM
• Cancel

5 Replies

• Tinh Phan

  

  • 12 Dec 2017 10:22 PM

  Hi Trey, I don’t believe DeltaV support explicit messages. It only support the available bytes/bits that are specified in the EDS file.

  • Cancel
• TreyB

  

  • 12 Dec 2017 10:30 PM

  In reply to Tinh Phan:

  Explicit messaging must be capable, as this must be how the information is accessed by Diagnostics.
  
  See, the BOL topic "Access Intelligent Field Device Diagnostic Data". It lays out how this is done within a control module. There is even default module templates that are supplied, so it's intended to be used.
  
  Thanks

  • Cancel
• Tinh Phan

  

  • 12 Dec 2017 11:03 PM

  In reply to TreyB:

  There should be a input byte that has the diagnostic that you can map to the external reference module then use a Boolean fan out to get the represent diagnostic information of the device.

  • Cancel
• TreyB

  

  • 13 Dec 2017 1:20 AM

  In reply to Tinh Phan:

  That is the problem with using an input byte through the device net signal creation in explorer under the device IO. It seems that the default for IO in deltaV is the assembly object. There is no indication of how to offset bytes to find the correct object class. Hence, the need to use explicit messaging. Which apparently is not an option from explorer and the devicenet signal creation.

  • Cancel
• TreyB

  

  • 20 Dec 2017 9:43 PM

  Does anybody else have some advice? The information is referencing BOL --Accessing Intelligent Field Device Diagnostic Data

  • Cancel