PAconfigurator Database Structure

Create and configure the content for all tests in the PAtools database using PAconfigurator. A test in the battery application consists of the following items:

  • Global database groups provided by the PAlibrary. For example, base modules like the message system.
  • Database groups describing the test station. For example, measuring equipment or a DC cycler.
  • Database groups describing the DUT. For example, DUT monitoring or setpoint limitation.
  • Database groups defining the specific test run. For example, a test procedure.
  • Additional configuration options depending on the application type and your specific implementation.

In principle, it is possible to change the structure of the database folders and the database groups. However, NI recommends keeping the database structure as defined by NI. The recommendation is due to the structure of the database having certain dependencies on drivers and on future updates.

Note NI cannot provide standard updates if you:
  • Change the database structure.
  • Implement changes in the signal flow.
  • Implement changes between the modularity of the battery application.
Supporting this specific installation in the future becomes challenging due to increased complexity.

Naming Conventions

Elements in the battery application follow a set of naming conventions.

Use the following general conventions for variable names.

  • Name variables in English.
  • Select unambiguous names.
  • Use complete words except where an abbreviation or acronym is a known standard.
  • Use the module name as a prefix for module variable names. For example, a variable name for a TCC module can be TCC_init.ACT.
  • Use camel case or underscores (_) to separate multiple words within a name.
  • Do not use a period as a separator in the variable name. Only use periods to delineate the suffix. The following example illustrates an incorrect and a correct use of a period.
    • Incorrect: Modulename_I_am.a.normname.SP
    • Correct: Modulename_I_am_a_normname.SP

Use the following conventions for suffixes of variable names.

Table 4. Suffix Conventions
Suffix Description
.A Action in an action table
.ACT Action to be executed or triggered
.AV Actual value
.CFF Format coding with numbers
.CFFS Format coding with strings
.CH Channel
.CHV Channel value
.CTL Control
.CV Calculated value
.F Function or task
.G PAbasic graphical programming
.gcN Global PAscript class. N corresponds to the main version of the class.
.ID Identifier
.libN Global PAscript library. N corresponds to the main version of the library.
.LL Lower switch-off limit. LL = Minimum - Tolerance
.LV Last value
.MAX Maximum limit
.MIN Minimum limit
.MV Measured value
.P PAbasic
.POI Pointer
.PS PAscript or PAscript graphical programming
.SP Setpoint
.STS Status
.SV Set value
.TAB Tables
.TOL Tolerance
.TXT Text
.UL Upper switch-off limit. UL = Maximum + Tolerance

Refer to Naming Conventions in the PAtools User Manual for more information about names in PAconfigurator.