Emerson Exchange 365

What causes this error? DV Version 12.3.1

What causes this and how can I fix it? This error started after a migration and is happening on multiple graphics.  

Lucky

• 10 Mar 2016 1:52 PM
• Cancel

10 Replies

• wiwin84

  

  • 10 Mar 2016 2:37 PM

  Hi Lucky,
  
  Make sure that the control module "LI407" is assigned and downloaded.

  • Cancel
• Lucky

  

  • 10 Mar 2016 3:08 PM

  In reply to wiwin84:

  It is. Everything is working with that module.

  • Cancel
• JustinGaudry

  

  • 10 Mar 2016 3:09 PM

  One possible cause is using an analog bar dynamo(For example on a tank level), and setting its fill animation to “Get limit values at runtime”
  
  Hardcoding the limits is a work around, but there is probably a more elegant solution.

   

  Justin

   

  • Cancel
• Maarten van der Waal

  

  • 10 Mar 2016 3:57 PM

  Some KB (can't find it back...) states that this problem is known, but not (yet?) solved.
  The advise is given to use LI407/AI1/OUT.F_CVPCT[OUT_SCALE].
  Also you could use LI407/AI1/FIELD_VAL_PCT.F_CV.

  Both work for me.

  • Cancel
• mcswab01

  

  • 10 Mar 2016 7:52 PM

  I am experiencing the same issue with regards to a DI module that has been deleted from the database. The Warning appears even before operate is fully loaded. There are no references to the module on the main graphic. If the module is re-created in the database and downloaded, the error does not occur. There are no alarms for the module active. If the module is then unassigned and deleted from the database the warning starts coming up again. This started occurring after moving from v12.3 to v12.3.1

  • Cancel
• Ben Bishop

  

  • 10 Mar 2016 9:17 PM

  Can you both (Lucky and mcswab01) please confirm that all of the nodes on the system have been upgraded from v12.3 to v12.3.1? All workstations should be running DeltaV v12.3.1 and all control network hardware should be running v12.3.1 firmware. I have seen similar errors when the ProPlus has been migrated to v12.3.1 and an Operator Station is still running v12.3.

  • Cancel
• Ben Bishop

  

  • 10 Mar 2016 9:31 PM

  In reply to mcswab01:

  After you delete the module assignment from the controller and delete it from the offline database, are you downloading Changed Setup Data to the workstations? I think you may be having a separate issue since DI's don't have engineering units in their dynamos. Can you post the entire error message?

  • Cancel
• Ben Bishop

  

  • 10 Mar 2016 9:33 PM

  In reply to Maarten van der Waal:

  I believe the KBA is AK-1300-0050 "Tips for Addressing the DeltaV Operate EGU Error Message"

  • Cancel
• MPHymel

  

  • 10 Mar 2016 9:40 PM

  In reply to Ben Bishop:

  This may not be the prescribed solution, but in a pinch we make these go away by filtering them out by following these notes:
  1. Close DeltaV Operate.
  2. Go to D:\DeltaV\DVData\Graphics-iFix\Local directory and open filterederrors.ini in notepad.
  3. Add another Error code with the customer's error number: Example: ERROR9 = 570425352
  4. Update the Count number: Example: Count = 9
  5. Save it and restart DV Operate.
  6. Verify.
  
  They serve no purpose to an operator, and cause issues when opening a graphic. If there is a real problem with a configured point, we will come to find out about it without needing the graphic display to tell us.

  • Cancel
• Jason.Brumfield

  

  • 28 Mar 2016 2:21 PM

  When you do the search for that particular tag on the graphic, make sure you include scripts. I have found that sometimes when copy & paste was utilized, you will have a link to an obsolete module parameter buried down in the animation somewhere.

  • Cancel