Emerson Exchange 365

OPC Mirror transfer OPC array items

I would like to transfer OPC array items, mapping each item independant.

The mappings validated in the OPC Mirror Configuration as VALID, however the types at the array item are empty.

Saved and applied to the pipe, using OPC Mirror Diagnostics the pipe reports an error:

It seams as OPC Mirror is unable to convert the data type of the array element to the DeltaV OCP Items.

DeltaV version used: 9.3.1

How to configure this mapping?

thks,

Werner

Werner Van de Vijver

• 12 Dec 2012 2:13 PM
• Cancel

5 Replies

• Youssef.El-Bahtimy

  

  • 12 Dec 2012 4:42 PM

  How do you have the items specified?  Module/Parameter[ x ][ y ].CV  where x and y are the array indices?

  • Cancel
• Werner Van de Vijver

  

  • 13 Dec 2012 6:52 AM

  In reply to Youssef.El-Bahtimy:

  I am first trying to transfer an OPC array item from a non-DeltaV OPC Server:

  TagName(1) ---> Module/Parameter

  Maybe I have found a workaround to transfer the OPC Value using the Options, scale the input 0 - 1 to the output 0 - 1.0

  • Cancel
• AdrianOffield

  

  • 13 Dec 2012 7:13 AM

  You state transferring an array item from non-DV server, but where are you transferring to, what is the item path defined as the destination?

   

  Do you want to keep the data in an array format inside DV, if so it should look something like MODULE/SPLTR1/IN_ARRAY[1][1].CV

   

  I’m not with you on how scaling will help with your problem; scaling doesn’t change how or where data is written to the DV OPC server.

   

  From: Werner Van de Vijver [mailto:bounce-WVan_de_Vijver@community.emerson.com]
  Sent: Thursday, December 13, 2012 10:53 AM
  To: DeltaV@community.emerson.com
  Subject: RE: [EE365 DeltaV Track] OPC Mirror transfer OPC array items

   

  I am first trying to transfer an OPC array item from a non-DeltaV OPC Server:

  TagName(1) ---> Module/Parameter

  Maybe I have found a workaround to transfer the OPC Value using the Options, scale the input 0 - 1 to the output 0 - 1.0

  • Cancel
• Werner Van de Vijver

  

  • 13 Dec 2012 7:29 AM

  In reply to AdrianOffield:

  In this test at the DV side I don't use a array, as I am only transferring one element of the array at the non-DV Server.

  In the error message it states the OPC Mirror is unable to convert the mapping defined, so to assist the conversion I tried the approach to scale the input to the output tag.

  Using this approach the error message has been cleared.

  If you say the scaling doesn't change how or where data is written to the DV OPC Server, maybe you are right about the last statement but on the first this implementation is done by the developer and convertion could be forced.

  • Cancel
• AdrianOffield

  

  • 13 Dec 2012 8:19 AM

  The tools I use to check for OPC mapping issues is OPCWatchit, try pointing OPCWatchit at the non-DV OPC server and browse to the tag in question, if you can read the value correctly use ‘Typepath’ and copy the item path string, this can then be inserted into the OPC Mirror data item mapping.

   

  It could also be an issue with datatype conversion, OPC Mirror does a good job of normally determining the dataype on both sides of the pipe (if omitted from mapping configuration), however, an array may present a problem for default dataypes; check this using Mirror diagnostics and correct if necessary (manually set datatype in the mapping configuration).

   

   

  From: Werner Van de Vijver [mailto:bounce-WVan_de_Vijver@community.emerson.com]
  Sent: Thursday, December 13, 2012 11:30 AM
  To: DeltaV@community.emerson.com
  Subject: RE: [EE365 DeltaV Track] OPC Mirror transfer OPC array items

   

  In this test at the DV side I don't use a array, as I am only transferring one element of the array at the non-DV Server.

  In the error message it states the OPC Mirror is unable to convert the mapping defined, so to assist the conversion I tried the approach to scale the input to the output tag.

  Using this approach the error message has been cleared.

  If you say the scaling doesn't change how or where data is written to the DV OPC Server, maybe you are right about the last statement but on the first this implementation is done by the developer and convertion could be forced.

  • Cancel