Versions Compared

Old Version 36

changes.mady.by.user Gill Houghton

Saved on

compared with

New Version 37

changes.mady.by.user Wes Johnson

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Anchor
Definitions
Definitions
Definitions


ModuleParameterDefinition
EFM ABB Totalflow SettingsArray-Register Definitions (Global)

The global Array-Register definitions made available to the EFM ABB Totalflow module.  They are uploaded to the Ignition instance either as individual INI files or as ZIP archives that contain INI files.  Note that INI files are text files that are read by PCCU or WinCCU to determine how to display data within an application. These global Array-Register definitions can be referenced by the configurations of the individual ABB Totalflow devices that they apply to. A single Ignition Gateway may contain multiple global Array-Register definitions files that are used to configure Array-Register Templates (i.e. templates that contain array, register, access type, data type, and register name info) for available application types (enumerations)

EFM ABB Totalflow SettingsTotalflow Applications Definitions (Global)

The global Totalflow Applications Definitions are uploaded to the Ignition instance as individual CSV files and contain the following information about Totalflow applications:

    • Enumeration number
    • Name
    • Type
    • An optional flag (SU) that indicates that this is a 'Selectable Unit' application 
    • Part number(s)
EFM ABB Totalflow SettingsEFM Periodic Mappings

The periodic mapping files are used for building up EFM Periodic and Daily History records.  They map various record fields to database column names so that user can adjust those column names to match requirements.  Periodic mappings also allow to exclude certain record fields to be used. They are uploaded to the Ignition instance in the form of specifically formatted CSV files

OPC UA Device Connection

Totalflow Applications

This is a list of applications (fields include respective name, slot number, enumeration, revision and type) that are currently installed on a Totalflow device. This list is obtained either by 'auto-discovery' process that takes place on  configuration/restart or by importing specifically formatted CSV file

OPC UA Device ConnectionTotalflow Applications Definitions (Device)

These are a subset of the global Totalflow Applications Definition files that apply to a specific device

OPC UA Device Connection

Array-Register Definitions (Device)

These are a subset of the global Array-Register definition files that apply to a specific device
OPC UA Device ConnectionArray-Register TemplatesArray-Register templates are logical groupings of AARs.  Generally, Array-Register templates would be created so that instances of them can be used by specifying a poll group with application slot number
OPC UA Device ConnectionPoll GroupsPoll groups use Array-Register templates in conjunction with application slot number to create a specific groups of register sets (i.e. sets of consecutive array registers) to be polled at a specified poll rate


Tip

The Cirrus Link default Array-Register Definitions and EFM Periodic Mapping files can be used as a starting point for configuring the EFM ABB Totalflow module.

The Totalflow Application Definitions file can be used as an example if you need to add application definitions that are not known to the driver. 

...

  1. From the EFM ABB Totalflow Settings, define/upload the global Array-Register definitions available for all Totalflow devices in this Ignition instance

  2. From the EFM ABB Totalflow Settings, define/upload the global Totalflow applications definitions available for all Totalflow devices in this Ignition instance.

    Note
    This step is optional since many application definitions are provided by the driver by default.


  3. From the EFM ABB Totalflow Settings, define/upload the EFM Mappings for all Totalflow devices in this Ignition Instance

  4. From the OPC UA Device Connections, create the base device connection to the ABB Totalflow unit.

  5. Once the device is created, you should see it is listed in the devices section with a status of either 'Auto-discovery' or 'Connected' on success, or "Not Connected" or "Security Failed" on failure. If device is configured with the 'Enable auto-discovery' option turned on, wait for auto-discovery to complete. When auto-discovery is completed, the device status changes from 'Auto-discovery' to 'Connected'.

  6. Navigate to the 'Totalflow Applications' configuration panel. If 'Auto-discovery' is enabled, that applications are there. If this configuration option is disabled, manually import the application information.

  7. Navigate to the 'Totalflow Applications Definitions' configuration panel. If 'Add All Totalflow Applications Definitions' is enabled, verify that all global applications definitions are added to this device definition. If this configuration option is disabled, manually add global applications definitions that apply.

  8. Navigate to the 'Array-Register Definitions' configuration panel. If 'Add All Array-Register Definitions' is enabled, verify that all global Array-Register definitions are added to this device definition. If this configuration option id disabled, manually add global Array-Register definitions that apply.

  9. Navigate to the 'Array-Register Templates' configuration panel. If 'Auto-Generate Templates and Poll Group' is enabled, verify the default templates are added to this device definition. If this configuration option is disabled, manually import the templates that apply.

    Note
    How does the ABB Totalflow driver select which files to parse from the supplied INI file?


    Warning

    One default Array-Register template will be created per each application type (i.e. application enumeration) given that polling for at least one instance of this application type is enabled in the 'Totalflow Applications' panel.

    If there are no enabled applications at the time auto-discovery runs for the first time, no Array-Register templates will be created.

    If there are enabled applications but there are no Array-Register definitions applied to this device connection, or definitions that are applied have no applicable entries based of application enumeration; in this case, Array-Register templates will be created but those templates will have no entries. If applicable Array-Register definitions are added later, templates will be populated. 


  10. Navigate to the 'Poll Groups' configuration panel. If 'Auto-Generate Templates and Poll Group' is enabled, verify the default poll groups are added to this device definition. If this configuration option is disabled, manually import the poll groups that apply.

  11. Go to device configuration and disable all three options under the 'Auto Setup' category. Disabling 'auto-discovery' allows faster transition from connection establishment to polling. Disabling 'Auto-generate Templates and Poll Group' will allow you to delete default templates and poll groups without the driver trying to regenerate them.

  12. Navigate to the 'Poll Groups' configuration panel and follow the 'Edit Poll Group Contents' link for the 'Default Poll Group'. Check the 'Enabled' box for each default poll group entry and click the 'Save' buttons twice: one time to save poll group entries, and another time to save poll groups. The device status will shortly change from 'Connected' to 'Polling'.

...