...
Note that it is the best practice to add global Array-Register definitions before any Totalflow device connections are defined. If Array-Register definition is added later, it needs to be added to a device connection manually. If Even if device connection has the 'Add All Array-Register Definitions' option turned on, new global Array-Register definition will not be applied unless either added manually or device configuration is re-submitted.
When creating a new global Array-Register definition only a name and a Totalflow INI file(s) needs to be specified. The name can be any unique name that describes the Array-Register definitions included in submitted file(s). Totalflow INI files are configuration files for use with
PCCU and G2-G5 and NGC devices.
...
Note that multiple Totalflow INI files need to be supplied in a ZIP archive.
Image Modified
Note that definition archive file may contain lots of INI files. For example, the ArrayRegisterDefinitions.zip file shown above contains 1477 files. So it worth explaining how the ABB Totalflow driver selects which files to parse... When global Array-Register definitions are applied to a device connection, the driver uses application revision information obtained during the 'auto-discovery' process described later in this document, and selects INI file names that match application revision and variant numbers. As an example, below is application information obtained during the auto-discovery:
Image Added
Note that revision number for the AGA3-1 meter application is 2101306-006; so the INI parser will look for the 2101306-006.ini file in submitted ZIP archive. If no direct match is found it will look for the another possible match based on the revision number (i.e. 2101306) and revision variant (i.e. 005 and lower). Also note that user has a way to check what INI file was picked by the driver as a source of Array-Register definitions. This information can be obtained form default Array-Register template generated by the driver by following the 'View INI Files' link as shown below:
Image Added
Below is an example that shows a portion the 2101306-006.ini file for the AGA3 Tube Application:
[Live Analysis Data] ExtHlp 5000 Help 1171 #Columns=2,Description=300,Value=100
dsc:Last Update from THERMS;cmd:4.5.1;typ:S;rwa:1;
dsc:Last Update from Other Source;cmd:4.2.2;typ:D;rwa:1;
dsc:Heating Value Live @ Tb and Pb;cmd:4.3.45;typ:F;
dsc:Real Relative Density Live @ Tb and Pb;cmd:4.3.44;typ:F;
dsc:N2 Live;cmd:4.3.46;typ:F;
dsc:CO2 Live;cmd:4.3.47;typ:F;
dsc:Methane Live;cmd:4.3.51;typ:F;
dsc:H2S Live;cmd:4.3.48;typ:F;
dsc:H2O Live;cmd:4.3.49;typ:F;
dsc:Helium Live;cmd:4.3.50;typ:F;
dsc:Ethane Live;cmd:4.3.52;typ:F;
dsc:Propane Live;cmd:4.3.53;typ:F;
dsc:N-Butane Live;cmd:4.3.54;typ:F;
dsc:I-Butane Live;cmd:4.3.55;typ:F;
dsc:N-Pentane Live;cmd:4.3.56;typ:F;
dsc:I-Pentane Live;cmd:4.3.57;typ:F;
dsc:N-Hexane Live;cmd:4.3.58;typ:F;
dsc:N-Heptane Live;cmd:4.3.59;typ:F;
dsc:N-Octane Live;cmd:4.3.60;typ:F;
dsc:N-Nonane Live;cmd:4.3.61;typ:F;
dsc:N-Decane Live;cmd:4.3.62;typ:F;
dsc:Oxygen Live;cmd:4.3.63;typ:F;
dsc:Carbon Monoxide Live;cmd:4.3.64;typ:F;
dsc:Hydrogen Live;cmd:4.3.65;typ:F;
dsc:Argon Live;cmd:4.3.66;typ:F;
...
So the driver parses selected INI file and uses the info (i.e. Array-Register definitions) to generate Array-Register templates as shown below
...
. Note how highlighted (bold) lines shown above correlate to Array-Register Templates shown below. Let's look at the dsc:N2 Live;cmd:4.3.46;typ:F; line in more details... The point description (i.e. N2 Live) is being used as a tag name. The 'typ:F' is the data type (i.e. floating point). Finally, the '4.3.46' defines application, array, and register respectively. Note that 4 is not an application slot number, but application enumeration. As a result, a default Array-Register Template is generated by the driver for a specific application enumeration, and it contains all Array-Register points found in appropriate INI files.
Image Modified