Emerson Exchange 365

• Not Answered

Removing parameters from Continuous Historian

Today we discovered that we cannot download the continuous historian. We will be purchasing a scale-up. In the interim, I would like to remove historized parameters from CH for a unit that is down to make room for a couple tags that I do need historized.

I see a delete button next to the modify button on the dialog box for a module's CH, but the delete is grayed out. 

Does anyone know how to delete a tag from CH? 

• CH
• Continuous Historian
• Delete from Historian

MPHymel

• 18 Nov 2022 5:25 PM
• Cancel

5 Replies

• jpuumala

  

  • 18 Nov 2022 6:33 PM

  If it's a class-based module, it looks like you can't remove a point from the historian from within Control Studio - you need to do it from DeltaV Explorer.
  
  Right-click on the module in DeltaV Explorer, select "History Collection...", select the point and the Delete button should highlight.
  
  If the module isn't class-based, you should be able to delete the historian point from within Control Studio though.
  
  Cheers,
  
  Jamie

  • Cancel
• MPHymel

  

  • 18 Nov 2022 7:10 PM

  In reply to jpuumala:

  Thanks for the response, Jamie, it is a class based module, and your right click method is precisely how I expected to delete it (as we do for adding), except "delete" is grayed out.

  • Cancel
• Matt Forbis

  

  • 18 Nov 2022 8:52 PM

  In reply to MPHymel:

  For a class based module, I don't believe you can remove historian items that are part of the class, only additional ones you add at the instance. You can modify the collection parameters, but that doesn't help in your scenario. I was at a customer's site with a similiar issue and the only feasible work around we found was to remove an entire parameter from the class (They trended MODE.TARGET and MODE.ACTUAL on their modules, and so we could remove MODE.TARGET from some classes until they purchased the license.)

  • Cancel
• MPHymel

  

  • 18 Nov 2022 9:01 PM

  In reply to Matt Forbis:

  That makes sense, most of our modules are classes. We'll likely have to wait for the license scale up. What was odd, is that it let us exceed the historized parameters by 216 over many weeks before this issue ever came up. And now we cant even d/l setup data to the app station because of this problem. Thanks for your thoughts on the matter.

  • Cancel
• Jim Ellis

  

  • 18 Nov 2022 9:06 PM

  I believe that you can move the module to a new area, and not assign the area to the historian.

   

  Phoenix Paper Wickliffe LLC

  Cell: 270.559.2426

   

  STATEMENT OF CONFIDENTIALITY The contents of this e-mail message and any attachments are confidential and are intended solely for the addressee. The information may also be legally privileged. This transmission is sent in trust, for the sole purpose of delivery to the intended recipient. If you have received this transmission in error, any use, reproduction, or dissemination of this transmission is strictly prohibited. If you are not the intended recipient, please immediately notify the sender by reply e-mail or at (270) 335-4000 and delete this message and its attachments, if any.

   

  • Cancel