• Not Answered

Batch Units with History Data Points

Hi All,

Batch Unit Classes are not supporting History Data Points. Due to that it's only possible to deploy them in the instances. For many other cases (control module instances) we are using FHX merge to add History Data Points. But for the Batch Units I'm not able to find the correct spelling... any idea?

What we use for Control Modules.. I tried some different thinks changing "MODULE_VALUES" to something else, but without success.

Maybe it's possible to bulk it?

Any idea is very welcome.

Thanks, Manuel

MODULE_VALUES TAG="R540_UNIT" merge=T
{
  HISTORY_DATA_POINT_INSTANCE NAME="U_CHARGE_COMPL"
  {
    HISTORY_DATA_POINT FIELD="CV"
    {
      DATA_CHARACTERISTIC=CONTINUOUS
      ENABLED=T
      SAMPLE_PERIOD_SECONDS=1
      COMPRESSION_ENABLED=T
      RECORD_AT_LEAST_EVERY_MINUTES=1440
      DEVIATION_LIMIT_FOR_COMPRESSION=0.01
      DATA_REPRESENTATION=AUTOMATIC
      EXPOSED=T
      ENTERPRISE_COLLECTION=F
    }
  }

}

1 Reply

  • My first thought is why would you want to capture discrete events like this in the Continuous Historian? That creates a significant license cost.

    Batch events would be captured in the Batch Historian, or you could trigger a LogEvent record in the EJournal. That records these events for free, and you can create a filtered PHV file to show relative information.

    I've also been playing with the SQL Data source in DeltaV Live to extract data from Ejournal to provide it in a Table Object in context within the HMI environment.

    Curious why you want this type of data captured in DVCH,

    Andre Dicaire