SBOU241E April   2020  – August 2022 INA228 , INA229 , INA237 , INA238 , INA239

 

  1.   SBOU241 Abstract
  2. 1Trademarks
  3.   General Texas Instruments High Voltage Evaluation (TI HV EVM) User Safety Guidelines
  4. 2Overview
    1. 2.1 Kit Contents
    2. 2.2 Related Documentation From Texas Instruments
  5. 3Hardware
    1. 3.1 Features
  6. 4Operation
    1. 4.1 Quick Start Setup
    2. 4.2 EVM Operation
      1. 4.2.1 Setup
        1. 4.2.1.1 Driver Installation
        2. 4.2.1.2 Firmware
          1. 4.2.1.2.1 Firmware Debug
        3. 4.2.1.3 GUI Setup and Connection
          1. 4.2.1.3.1 Initial Setup
          2. 4.2.1.3.2 GUI to EVM Connection
      2. 4.2.2 GUI Operation
        1. 4.2.2.1 Homepage Tab
        2. 4.2.2.2 Configuration Tab
        3. 4.2.2.3 Registers Tab
        4. 4.2.2.4 Results Data Tab
      3. 4.2.3 Current Sensing Operation
        1. 4.2.3.1 Detailed Setup
      4. 4.2.4 Direct EVM USB Communication
        1. 4.2.4.1 Standard USB Read and Write Operations
        2. 4.2.4.2 Collect Data Through the USB BULK Channel
      5. 4.2.5 PAMB Compatibility
  7. 5Circuitry
    1. 5.1 Current Sensing IC
    2. 5.2 Input Signal Path
    3. 5.3 Digital Circuitry
      1. 5.3.1 I2C (INA228, INA237, INA238)
      2. 5.3.2 SPI (INA229, INA239)
  8. 6Schematics, PCB Layout, and Bill of Materials
    1. 6.1 Schematics
      1. 6.1.1 SENS063 (INA228EVM, INA237EVM, INA238EVM)
      2. 6.1.2 SENS064 (INA229EVM, INA239EVM)
    2. 6.2 PCB Layout
      1. 6.2.1 SENS063 (INA228EVM, INA237EVM, INA238EVM)
      2. 6.2.2 SENS064 (INA229EVM, INA239EVM)
    3. 6.3 Bill of Materials
      1. 6.3.1 SENS063 (INA228EVM, INA237EVM, INA238EVM)
      2. 6.3.2 SENS064 (INA229EVM, INA239EVM)
  9. 7Revision History

Collect Data Through the USB BULK Channel

The Collect Data function reads the desired result registers and sends the data based on the specified settings. This function works best with continuous conversion mode and does not configure the EVM or associated register settings for you. Collect mode started and stopped via the serial COM port, however the results will be sent over the USB BULK channel. To use this mode, use the following format:

  • Start collecting data format: collect timerPeriod collectFlags channelAddressIDs numDevices
    • Where collect is always lower case, and each parameter is the decimal representation of the value in the following format:
      • timerPeriod
        • The timer delay used in the MCU to allow data collection sample sets (in µs, unsigned 32-bit value).
      • collectFlags
        • a byte of data that has a 1 to collect and a 0 to not collect each register value type, according to the following definitions (note to only use energy and charge flags when the device supports that, otherwise set to 0):
          • VSHUNT = 0b1000000
          • VBUS = 0b0100000
          • DIETEMP = 0b0010000
          • CURRENT = 0b0001000
          • POWER = 0b0000100
          • ENERGY = 0b0000010
          • CHARGE = 0b0000001
      • channelAddressIDs
        • SPI
          • Each 4 bits is the chip select (CS) value for each EVM chained together starting with the LSBs (each CS can either be 1, 2, 3 or 4).
            • For example, if EVM 1 is on channel 1 and EVM 2 is on channel 3, the value here would be 0b00110001.
        • I2C
          • This is the 4 LSBs of each address chained together, starting with the LSBs.
            • For example, if EVM 1 is on channel 0x41 and EVM 2 is on ox43, the value here would be 0b00110001
      • NumDevices
        • The number of EVMs chained together (1-4).
    • For example, to start data collection for VSHUNT, VBUS, and DIETEMP every 3.156 ms, for two INA229s with EVM 1 CS = 1 and EVM 2 CS = 3, you would send: collect 3156 112 49 2
      • For this example, the EVM would return the acknowledgment and state in JSON format:
        • {"acknowledge":"collect 3156 112 49 2"}
        • {"evm_state":"collecting"}
    • The USB BULK channel receives data in the format: frameID deviceNumID address registerSize data
      • Where each parameter is the decimal representation of the value in the following format:
        • frameID (1 byte)
          • Always reads 0. Used to ensure data is aligned.
        • deviceNumID (1 byte)
          • An ID number corresponding to the EVM number.
            • From the above example, this will be 1 if reading from EVM 1 which had CS set to 1, and 2 if reading from EVM 2 which had a CS set to 3.
        • address (1 byte)
          • The register address that was read from the device.
        • registerSize (1 byte)
          • The number of bytes that the following data will have.
        • data (1 byte at a time)
          • The register data value, given in bytes with the most significant byte first.
  • Stop collecting data format: stop
    • Where stop is always lower case.
    • The EVM will return the acknowledgment and state in JSON format:
      • {"acknowledge":"stop"}
      • {"evm_state":"idle"}