Page History

...

• Totalflow Applications
  • These 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. 
• Array-Register Definitions (Device)
  • These are a subset of the global Array-Register definition files that apply to a specific device.
• Array-Register Templates
  • Array-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.
• Poll Groups
  • Poll 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.

There are six basic steps to getting all of the data available from a ABB Totalflow into Ignition

1. Define/upload the global Array-Register definitions available for all Totalflow devices in this Ignition instance
2. Define/upload the EFM Mappings for all Totalflow devices in this Ignition Instance
3. Create the base device connection to the ABB Totalflow unit.
4. If device is configured with the 'Enable auto-discovery' option turned on, wait for auto-discovery to complete. The device status will change from 'Auto-discovery' to 'Connected'. Go to the 'Totalflow Applications' configuration panel and verify that applications are there. Note that polling on all meter applications (i.e. TUBE applications) will be enabled by default. If device is configured with auto-discovery disabled, import application information from 'applications' CSV file that contains correct information on applications that run on a Totalflow device the driver is connected to. En example of such CSV file is shown below.
5. If device is configured with the 'Add All Array-Register Definitions' option turned on, navigate to the 'Array-Register Definitions' configuration panel and verify that all global Array-Register definitions are added to this device definition automatically. If this configuration option turned off, manually add global Array-Register definitions that apply.
6. Navigate to the 'Array-Register Templates' configuration panel and verify that default Array-Register templates have been created. Note that there are a few important points to note here:
   1. 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.
   2. If there are no enabled applications at the time auto-discovery runs for the first time, no Array-Register templates will be created.
   3. 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.

...

1. 1. If applicable Array-Register definitions are added later, templates will be populated. 
2. TODO Note that  On the other hand,    

1. Specify the subset of TLP definitions that this specific ROC uses
2. Create TLP Template(s) which define groups of TLPs should be polled as a logical group
3. Create TLP Poll Group(s) which specify the logical parameters associated with a given TLP Template
4. Use Ignition Designer to pull tags into a tag provider