DeltaV Operate for Provox - HMI Warnings

I'm assisting with a DVOP conversion and we occasionally get OPC Warning Messages in Operate "The value of the handle is invalid", for some of our dynamos.  The warnings continue after "skip all" is selected and render the display unusable to the operator.  Has anyone seen this issue before?  

More details....

This is a v11.3.1 new system, 1 PP, 2 Pro, 1 POC.   This problem is not persistent and isn't isolated to specific tags or dynamos.  Sometimes they work...sometimes some of them don't.  I've tried changing the syntax by drilling down with browse in the animation expert, but today this proved to be only a temporary solution.  This is an OPC warning, but the tags appear to be communicating because we don't see @@@@ or *****. .  Has anyone seen this before or have an idea what problem is causing this to happen?  

Thanks in advance for any response:)

Kathy Pate

Toray Carbon Fibers America

Decatur, AL 35601

[email protected]

6 Replies

  • There's an old Emerson KBA (AUS1-198-000512080235) that documents typical errors encountered when accessing DeltaV OPC servers.  Yours is not in the list I am afraid.   The message should also come with an error code.  Might be worth indicating that in your post as well.  Cheers.

  • In reply to fabuid:

    Thanks for the response:)  The error code was (c004001).  

    Kathy Pate

    Toray Carbon Fibers America

    Decatur, AL 35601

    [email protected]

  • When you say conversion, are you upgrading from an older version of DVOP or are you converting Provox to DVOP 11.3.1?
     
    From: kathrynpate [mailto:[email protected]]
    Sent: Friday, August 02, 2013 6:22 AM
    To: [email protected]
    Subject: [EE365 DeltaV Track] DeltaV Operate for Provox - HMI Warnings
     

    I'm assisting with a DVOP conversion and we occasionally get OPC Warning Messages in Operate "The value of the handle is invalid", for some of our dynamos.  The warnings continue after "skip all" is selected and render the display unusable to the operator.  Has anyone seen this issue before?  

    More details....

    This is a v11.3.1 new system, 1 PP, 2 Pro, 1 POC.   This problem is not persistent and isn't isolated to specific tags or dynamos.  Sometimes they work...sometimes some of them don't.  I've tried changing the syntax by drilling down with browse in the animation expert, but today this proved to be only a temporary solution.  This is an OPC warning, but the tags appear to be communicating because we don't see @@@@ or *****. .  Has anyone seen this before or have an idea what problem is causing this to happen?  

    Thanks in advance for any response:)

  • In reply to AdrianOffield:

    Converting from Provox to DVOP.  The system has been running for over a month to allow for operator training and they just started getting these intermittent HMI errors.  The new DVOP displays were not automatically generated due to complexity.  Instead dynamos were developed from another systems DVOP displays that WERE automatically generated (created groups of objects instead of dynamos).  The new system also has an S-Series Controller to support CHARMS but this part hasn't been commissioned yet.  

    Kathy Pate

    Toray Carbon Fibers America

    Decatur, AL 35601

    [email protected]

  • Regarding the other DVOP system dynamos, are they of the same revision?  Is this a redundant set of HDL’s?
     
    DVOP uses a separate data server from that of DVSYS, and it uses different sets of fxg files than the traditional DeltaV ones.  To eliminate uncertainty, try using a standard DVOP faceplate (form the POC directory) and dynamo for a Provox module, does the same problem exist?
     
    The last time I used DVOP was on DV8, but I remember there were some settings in the Console servers (especially users) that could affect data being displayed on Operate.
     
    From: kathrynpate [mailto:[email protected]]
    Sent: Friday, August 02, 2013 7:36 AM
    To: [email protected]
    Subject: RE: [EE365 DeltaV Track] DeltaV Operate for Provox - HMI Warnings
     

    Converting from Provox to DVOP.  The system has been running for over a month to allow for operator training and they just started getting these intermittent HMI errors.  The new DVOP displays were not automatically generated due to complexity.  Instead dynamos were developed from another systems DVOP displays that WERE automatically generated (created groups of objects instead of dynamos).  The new system also has an S-Series Controller to support CHARMS but this part hasn't been commissioned yet.  

  • In reply to AdrianOffield:

    Thank you for your reply, Adrian:)  

    The other DVOP system graphics were created by Emerson from a Provox to DVOP conversion utility which generated groups of animated objects instead of dynamos.  We were unable to use the utility for this system because the complexity of the Provox graphics.  So the new dynamos were built from the "groups" that the utility generated for the other system.  We've tried browsing to the tag/attributes in the POC server, which initially seems to fix the problem, but the following day we received similar warning messages on these datalinks as well.  Also ran refresh rate expert, looked at usersettings.  Since the messages appear sporatically, it is hard to know what fixes it.

    The redundant POC server is getting set up next week by the LBP next week.  I'm hoping they will have some insight into this issue.

    Kathy Pate

    Toray Carbon Fibers America

    Decatur, AL 35601

    [email protected]