SLAU880C December   2022  – May 2024 ULC1001

 

  1.   1
  2.   Abstract
  3.   Trademarks
  4. 1General Texas Instruments High Voltage Evaluation (TI HV EVM) User Safety Guidelines
  5. 2Introduction
  6. 3Getting Started
    1. 3.1 Evaluation Kit Contents
    2. 3.2 Connection Procedure
    3. 3.3 GUI Setup
  7. 4System Overview
    1. 4.1 System ISR Period
    2. 4.2 System Drive Voltage
    3. 4.3 System Calibration
      1. 4.3.1 DC Bias Calibration
      2. 4.3.2 Temperature Calibration
      3. 4.3.3 Auto Sense Calibration
      4. 4.3.4 Cleaning and Power Calibration
    4. 4.4 System Cleaning
    5. 4.5 System Diagnostics
  8. 5GUI Overview
    1. 5.1 GUI Top Level Layout
      1. 5.1.1 North Pane
      2. 5.1.2 South Pane
      3. 5.1.3 Center Pane
    2. 5.2 High Level Page
      1. 5.2.1 Burst Parameters
      2. 5.2.2 Calibration Settings
        1. 5.2.2.1 Voltage and Current Sense Circuitry
      3. 5.2.3 Cleaning Mode Settings
        1. 5.2.3.1 Auto-Cleaning
        2. 5.2.3.2 Water Cleaning
        3. 5.2.3.3 Deice Cleaning
        4. 5.2.3.4 Mud Cleaning Mode
      4. 5.2.4 Power and Diagnostic Settings
    3. 5.3 Register Map Page
    4. 5.4 I2C Configuration Page
    5. 5.5 GUI Functions
      1. 5.5.1 Monitor Communication Status
      2. 5.5.2 Load and Save Configuration Files
        1. 5.5.2.1 MSP430 Firmware Programming
      3. 5.5.3 Re-initialize System
      4. 5.5.4 Fault and Flag Monitoring and Clearing
      5. 5.5.5 Run Calibration
      6. 5.5.6 Run Cleaning Modes
      7. 5.5.7 Run Diagnostic Mode
      8. 5.5.8 Run Abort
      9. 5.5.9 Script Recording
  9. 6Hardware Design Files
    1. 6.1 Schematics
    2. 6.2 PCB Layouts
    3. 6.3 Bill of Materials (BOM)
  10. 7Revision History

System Overview

ULC1001 has many settings to be configured for good cleaning performance. These settings are separated into three main tabs: Calibration, Cleaning Modes, and Power and Diagnostics. At a high level, ULC1001 invokes modes for calibration, cleaning, power monitoring, and fault protection. Each of these nine modes contains up to 30 bursts that can be configured for a wide range of frequencies. Bursts are enumerated from 0-23 and each burst has eight configurable parameters. The GUI is very useful for setting up the system and exporting configuration files for system integration. When a mode is enabled, the ULC1001-DRV290x EVM drives each burst in the order shown in Figure 4-1 for a given mode.

ULC1001 DRV2901 ULC1001-DRV-FL-EVM ULC1001-DRV290XEVM System Configuration Matrix
Figure 4-1 System Configuration Matrix

There are two types of bursts: Active bursts enable the IV sense path (bursts 0 to 5 and 19 to 23) and Passive bursts do not enable the IV sense path (bursts 6 to 17). Each burst contains the following eight configurable parameters: Amp, Delay, and Duration, Freq_Start, Freq_Stop, Num_Freq, Delta_Freq, and Modulation.

Note:

Burst 18 is an Idle burst, which is returned to automatically at the end of each mode; this burst is never set by the user. Burst 18 must not be placed in the mode sequences. Burst 23 is the Temperature burst, which can be enabled to run continuously. For information on adding Burst 23 to a sequence, refer to Section 5.2.3.1.

All Active burst frequency settings, except burst 0, must follow the following: Delta_Freq*n = (Fs/N)*n = (ULC_RX_mode_cfg bits [0-4]/USER_Params_numSamples)*n, where n is an integer multiplier. Freq_start ≤ Freq_stop. Freq_start and Freq_stop must be integer multiples of Delta_Freq. Refer to Table 5-2.

All Passive bursts must have Num_Freq = 0. Refer to Table 5-3.

There are two types of registers to be programmed. Hardware (HW) registers, which are 8-bits, setup the hardware configurations such as the ADC sample rate. Firmware (FW) registers, which are 32-bits and follow a Q-point notation, setup the firmware inside the DSP. FW registers' Q-point notation is defined by the suffix of each register; if no suffix exists, then the register is a normal 32-bit register. FW registers are stored in an I2C buffer and are not used by the firmware until the re-initialization command is invoked. Refer to Section 5.5.3 for running the re-initialization command.