Documentation

Refer to the Python PCB Assembly Test Toolkit - Getting Started guide for getting started steps including installation and setup procedures, and steps to run example test sequences. Refer to the User Manual for an overview of Toolkit concepts and measurement fundamentals, including a brief overview of each library and automation sequences.

Supported Features

Library imports and migrations

In the release 2.x and above the instrument-specific measurement libraries are exposed as subpackages under the top-level nipcbatt package. Example usage:

from nipcbatt import daq
drvg = daq.DcVoltageGeneration()
drvg.initialize(analog_output_channel_expression="Sim_PC_basedDAQ/ao0")

Few classes remain accessible directly from nipcbatt (for example nipcbatt.MeasurementExecutionType). However, explicit subpackage imports are the recommended approach for all new code. To migrate existing code, update imports and references from:

# Not recommended ❌
import nipcbatt
drvg = nipcbatt.DcVoltageGeneration()

to the explicit subpackage form:

# Recommended ✅
from nipcbatt import daq
drvg = daq.DcVoltageGeneration()

See Migration Guide for nipcbatt 2.x for a complete list of class mappings, and all available subpackage classes.

Required Drivers

• NI-DCPOWER: 2025 Q4 and above

• NI-DMM: 2023 Q4 and above

• NI-SWITCH: 2023 Q4 and above

• NI-DAQmx: 2023 Q3 and above

• LabVIEW Runtime: 2022 Q3 and above (64 bit)

• NI-845x: 2022 Q3 and above

• NI-VISA: 2023 Q2 and above

• NI-Serial: 2023 Q2 and above

Visit ni.com/downloads or visit NI Package Manager to download the Required Drivers.

Supported Hardware

• PPS/SMU devices compatible with the NI-DCPOWER driver

• DMM devices compatible with the NI-DMM driver

• Switch devices compatible with the NI-SWITCH driver

• Any DAQmx devices with similar functionality and resources

• NI PC-Based DAQ

• CompactDAQ

• TestScale

Operating System Support

nipcbatt supports Windows 10 and 11 systems where the supported drivers are installed. Refer to NI Hardware and Operating System Compatibility for which versions of the driver support your hardware on a given operating system.

Python Version Support

nipcbatt supports Python 3.10 to 3.12 (64 bit)

1. Libraries

All the measurement libraries consist of three main methods which have to be used in the following order:

• Initialize:

  Used to initialize a measurement instance (for DAQmx use either physical or global virtual channels to perform the respective task).

  This is done by calling the initialize() method on the class instance.

Example code to initialize an instance of DC RMS voltage measurement:

>>> from nipcbatt import dmm
>>> dmm_voltage_measurement = dmm.DcRmsVoltageMeasurement()
>>> dmm_voltage_measurement.initialize("Sim_DMM", 50)

• Configure and Generate/Configure and Measure:

  Configures and executes measurement or generation tasks. For measurements, this method can return both raw data for custom analysis and processed results from built-in analysis functions (configurable via measurement options).

  This is done by calling the configure_and_measure()/configure_and_generate() method on the class instance.

Example code to configure and measure DC voltage using the class instance:

>>> measurement = dmm_voltage_measurement.configure_and_measure(
>>>   configuration=dmm.DEFAULT_DC_RMS_VOLTAGE_MEASUREMENT_CONFIGURATION
>>> )
... # Default voltage measurement configuration

• Close:

  Closes the measurement or generation session and releases hardware resources.

  This is done by calling the close() method on the class instance.

Example code to close the session and clear resources:

>>> dmm_voltage_measurement.close()

1. Features and Utilities

• Virtual Channels

  Virtual channels, or sometimes referred to generically as channels, are software entities that encapsulate the physical channel along with other channel specific information (e.g.: range, terminal configuration, and custom scaling) that formats the data. A physical channel is a terminal or pin at which you can measure or generate an analog or digital signal. A single physical channel can include more than one terminal, as in the case of a differential analog input channel or a digital port of eight lines. Every physical channel on a device has a unique name (for instance, cDAQ1Mod4/ai0, Dev2/ao5, and Dev6/ctr3) that follows the NI-DAQmx physical channel naming convention. Refer to NI-DAQmx Channel for more information.

• Logger

  The logger is a feature which comes along with the package as a part of PCBATT Utilities and helps in storing configuration details and results for every run of the sequences. It can be used to store results in the .txt or .csv file formats. The logger stores results for every run in the same file. Example usage of the logger can be found in the automation sequences.

• Save Traces

  This Utility works in a similar manner as the logger but it saves configuration settings and results for each run in separate files. Example usage of the save_traces module can be found in the validation examples.

1. Validation Examples

Validation examples are created as examples for testing and validating one or more libraries together, covering generation, measurement, communication, or a combination of these. The validation examples can be found in this location pcbatt_validation_examples.

The following images shows sample results for Signal Voltage Generation to Frequency Domain Voltage Measurement Validation example which is located at “/pcbatt_validation_examples/PC_Based_Examples/PC_SVG_FDVM.py”:

2. Automation Sequences

Automation sequences are examples of using libraries for real time scenarios like microphone tests, LED tests and so on. Automation sequences are tested in simulation mode.

Following is the list of Automation Sequences provided as a part of the package.

1. action_button_tests

2. audio_tests

3. communication_tests

4. digital_io_tests

5. led_tests

6. microphone_tests

7. power_supply_tests

8. sensor_tests

9. synchronization_tests

The Automation Sequences can be found in this location pcbatt_automation.

3. Functional Test Demo Sequence

FT demo sequence is an example for creating a test sequence using libraries with applying test limits on the results to determine whether the test is a pass or a fail.

Please refer to the FT Demo Sequence in the location pcbatt_ft_demo_test_sequence.