commit

data/json/DLP/355909.json

@@ -0,0 +1,23 @@
+{
+  "ticketNumber" : "355909",
+  "reporterName" : "RE",
+  "rankPoints" : "21045",
+  "resolutionStatus" : "",
+  "ticketName" : "[FAQ] I want to use Hall Effect Sensors - where do I start?",
+  "rankName" : "Mastermind",
+  "replies" : " 1",
+  "views" : " 13831",
+  "queryText" : "I need contactless position measurement, angle measurements, switching and latching digital outputs with magnets. How do I choose a part? How do I choose a magnet? Help me get started!",
+  "partNumber" : "NA",
+  "allResponseList" : [ {
+    "contentId" : "2664186",
+    "userName" : "Mitch M",
+    "rankPoints" : "4825",
+    "rankName" : "Expert",
+    "date" : "Aug 24, 2018 9:10 PM",
+    "userId" : "4910879",
+    "content" : "This E2E forum is the place to ask TI's experts questions about Hall Sensors: Latches: DRV5011, DRV5012, DRV5013, DRV5015 Automotive: DRV5013-Q1, DRV5015-Q1 Switches: DRV5021, DRV5023, DRV5032, DRV5033 Automotive: DRV5021-Q1, DRV5023-Q1, DRV5033-Q1 Linear: DRV5053, DRV5055, DRV5056, DRV5057 Automotive: DRV5053-Q1, DRV5055-Q1, DRV5056-Q1 _____________________________________________________ Videos: Getting Started with Hall Effect Sensors Jump start your Hall effect sensor expertise _____________________________________________________ Blogs: Center stage with Hall sensors Rediscover the Hall sensor Measuring wheels in motion Hall Effect sensor bandwidth in BLDC motors Meter anti-tampering _____________________________________________________ White Papers: Achieve greater precision, reliability with magnetic sensing technology Sub-Microamp, Intelligent Hall-Effect Sensing Delivers 20-Year Battery Life _____________________________________________________ Tech Notes & Application Reports: Linear Hall Effect Sensor Angle Measurement Theory, Implementation, and Calibration Understanding & Applying Hall Effect Sensor Datasheets Power Gating Systems with Magnetic Sensors Sensored 3-Phase BLDC Motor Control Using MSP430 Incremental Rotary Encoder Design Considerations _____________________________________________________ Evaluation Modules: DRV5032-SOLAR-EVM HALL-ADAPTER-EVM DRV5055-ANGLE-EVM DRV5055EVM DRV5055-5057EVM DRV5011-5012EVM _____________________________________________________ Calculators & Design Tools: CAD files for DBZ (.bxl and Altium files) Online magnetic field calculator _____________________________________________________company Reference Designs with Hall sensors: Ultra-low Power Fault Monitoring for Overhead Power Lines Sunroof Motor Module Wireless Low-Power Window Sensor Automotive 48V 1kW Motor Drive Automotive 12V 200W (20A) BLDC Motor Magnetic Tamper Detection using Low-Power Hall Effect Sensors Speed-Controlled 24V Brushless DC Outrunner Motor 12V and 24V Brushless DC Outrunner Motor Incremental Rotary Encoder 3D Printer Controller (12V) Foot Controller Reference Design using Analog Hall Sensor Contactless AC-Current Sensing Current Controlled Driver for 24V DC Solenoid Current Controlled Driver for 230V AC Solenoids Hall-Effect Proximity Sensor with PNP or NPN Output Variable threshold Hall proximity Sensor with PNP/NPN Proximity and Temperature Multi-Variable Transmitter Hall Sensor Proximity Sensor w/Fixed Threshold and Temp Sensing Refrigerator Fan drive control Single Phase BLDC with Brushed Motor Driver _____________________________________________________ Various Magnet suppliers: http://www.acm-magnetics.com http://www.sgtec.com http://www.ysm-magnet.com http://www.nbvsmagnetic.com http://www.magmamagnets.com http://www.adamsmagnetic.com http://www.kjmagnetics.com http://www.magnete.de http://www.thyssenkrupp-magnettechnik.com http://www.mceproducts.com _____________________________________________________ last updated 8/24/2018"
+  } ],
+  "tags" : [ "/support/sensors/f/1023/tags/DRV5032", "/support/sensors/f/1023/tags/DRV5033", "/support/sensors/f/1023/tags/DRV5053", "/support/sensors/f/1023/tags/DRV5023_2D00_Q1", "/support/sensors/f/1023/tags/DRV5053_2D00_Q1", "/support/sensors/f/1023/tags/DRV5033_2D00_Q1", "/support/sensors/f/1023/tags/DRV5055_2D00_Q1", "/support/sensors/f/1023/tags/DRV5013_2D00_Q1", "/support/sensors/f/1023/tags/HALL_2D00_ADAPTER_2D00_EVM", "/support/sensors/f/1023/tags/DRV5032_2D00_SOLAR_2D00_EVM", "/support/sensors/f/1023/tags/DRV5012", "/support/sensors/f/1023/tags/DRV5013", "/support/sensors/f/1023/tags/DRV5023", "/support/sensors/f/1023/tags/DRV5011" ],
+  "fourmType" : "TI"
+}

data/json/DLP/748143.json

@@ -0,0 +1,23 @@
+{
+  "ticketNumber" : "748143",
+  "reporterName" : "Akeem Whitehead",
+  "rankPoints" : "21215",
+  "resolutionStatus" : "Resolved",
+  "ticketName" : "[FAQ] Ultrasonic Sensors",
+  "rankName" : "Mastermind",
+  "replies" : " 1",
+  "views" : " 7530",
+  "queryText" : "Ultrasonic sensing uses the propagating sound waves at a frequency above the range of human hearing (>20kHz) that can travel through a wide variety of mediums (air, fluid, or solid) to detect objects, measure distance, or track disturbances. Ultrasonic sensors can be used to detect a wide variety of materials regardless of shape, transparency, or color. For an overview on ultrasonic sensing fundamentals,company recommends you begin by reading the Ultrasonic Sensing Basics application note.company offers a variety of ultrasonic sensing ICs. The objective of this FAQ is to help recommend a specificcompany ultrasonic sensing device based on the application use-case and system requirements. Ultrasonic Sensing Application Measure Distance and Proximity Measure Level or Height of Liquid or Solid Measure Flow Rate and Direction of Liquid, Gas, or Heat Measure Concentration and Material Identification Object Tracking and Mapping Material Thickness and Flaw Detection Monitor Changes to Environment Description Use a single sensor to both generate and capture a round-trip time-of-flight echo to measure the distance between the sensor and the targeted object. Use a single sensor to both generate and capture a round-trip time-of-flight echo to measure the distance between the sensor and the targeted object. Use two sensors to capture the difference of transit time propagating in and against the flow direction as an independent upstream and downstream measurement. Use a single sensor to both generate and capture a round-trip time-of-flight echo to measure the changes in the speed of sound based on a fixed-known distance. Use at least two transducers with a fixed-known distance between on another. One transducer must always be used to generate and capture a round-trip time-of-flight echo, while the other transducers must only capture the round-trip time-of-flight echo. By comparing the resulting time of flight differences through triangulation. Use a single sensor to both generate and capture a round-trip time-of-flight to measure the thickness of a solid object, and determine if there are any voids within the solid. The transducer face must be made to couple to the solid material type for direct transducer to solid contact. Use two transducers, one to continuously generate the ultrasonic echo, and the other to continuously capture the difference in return echo zero-crossing frequency (Doppler shift).company Top Device Pick PGA460 TUSS4470 MSP430FR6047 TUSS4470 TUSS4470 TUSS4440 TUSS4470 Why Top Pick The PGA460 was designed specifically to measure distance using ultrasonic time-of-flight. The integrated driver, receiver, ADC, and digital signal processing logic simplifies the steps required to capture this time-of-flight data. The TUSS4470 supports the widest range of transducer frequencies from 30kHz to 1MHz to measure height from the top pointed down through air, or from the bottom pointed up through liquid. The customer organization MSP430FR604x and MSP430FR603x family of ultrasonic sensing and measurement SoCs are powerful, highly integrated microcontrollers (MCUs) that are optimized for water and heat meters. The TUSS4470 supports the widest range of transducer frequencies from 30kHz to 1MHz to properly couple the transducer and enable this measurement through nearly all gases, liquids, or solids. Multiple TUSS4470 devices can be easily synchronized due to the device’s ability to independently enable the receiver path regardless of the driver block’s state. This means the start of the pulse generation can be used as the sole time-of-flight origin reference for all devices. To propagate sound waves through a solid, a large amount of sound pressure must be generated by using a transformer driver. The TUSS4440 is able to generate hundreds of volts to excite transducer, while normalizing the time-of-flight echo response regardless of the flaw dimensions. The TUSS4470’s built-in zero-crossing feature allows the receiver to continuously monitor the incoming echo frequency. If the object is approaching the sensor, the zero-crossing frequency will increase, while an object leaving will cause the zero-crossing frequency to decease. Recommended Evaluation Tool BOOSTXL-PGA460 BOOSTXL-TUSS4470 EVM430-FR6047 BOOSTXL-TUSS4470 BOOSTXL-TUSS4470 BOOSTXL-TUSS4440 BOOSTXL-TUSS4470 Notes Enable near 0mm detection by using a bi-static transducer pair for a separate transducer to generate the echo, and another transducer to capture the round-trip time-of-flight. For top-down level sensing, use lower frequency transducers. For bottom-up level sensing, use higher frequency transducers.company no longer recommends using the TDC1000 for flow rate application due to known stability and accuracy issues of the device’s STOP pulse generation. Enable one-way measurements by using a bi-static transducer pair facing each other for a separate transducer to generate the echo, and another transducer to capture the one-way time-of-flight As transducers are added to the receiver array, the accuracy and addition details of the object to be tracked or mapped are increased. It is important to use a contact transducer acoustic matched to the solid you are measuring the thickness of. Improper transducer face type or poor mounting will result in invalid results. Monitoring the Doppler shift of the return echo is one method of seeking changes to the environment. Capturing the echo envelope over time per time-of-flight measurement is another way to monitor environmental changes by comparing the latest record cycle to the previous record cycle.company Ultrasonic Sensing IC Device Comparison: TUSS4470 TUSS4440 PGA460 MSP430FR6047 TDC1011 / TDC1000 Device type Analog front-end Analog front-end Analog front-end + digital signal processor (integrated) Analog front-end + digital signal processor (integrated) Analog front-end Supported transducer frequencies 40 kHz – 1 MHz 40 – 440 kHz (pre-drive) 40 – 500 kHz 30 – 80 kHz & 180 – 480 kHz 50 kHz – 2.5 MHz 31.25 kHz – 4 MHz Channel count 1 Channel 1 Channel 1 Channel 2 Channel TDC1011: 1 Channel TDC1000: 2 Channel Drive topology - Direct drive (max 36 V) - Pre-drive Transformer drive - Transformer drive - Direct drive with added FETs Direct drive (max 3.3V) Direct drive (max 5V) Gain stage 86 dB logarithmic amplifier 86 dB logarithmic amplifier 6 point time-varying gain (32 to 90 dB) Fixed gain (6.5 to 30.8 dB) Fixed gain (20 to 41 dB) Outputs - Analog echo envelope - Zero crossing - Envelope threshold detect - Analog echo envelope - Zero crossing - Envelope threshold detect - DSP processed output (time-of-flight, amplitude, width) - Echo data dump (down-sampled echo envelope) - Raw digital data path (ADC, bandpass filter, rectifier, lowpass filter) - Flow rate - DSP processed output (time-of-flight) - Zero crossing - Echo start and stop pulse Temperature sensor No No On-chip temperature sensor On-chip temperature sensor Interface to RTD Diagnostics SPI diagnostics SPI diagnostics - System diagnostics (frequency, decay, excitation voltage) - Supply diagnostics (overvoltage) Programmable None Automotive qualified device N/A N/A PGA460-Q1 N/A TDC1011-Q1 TDC1000-Q1 Output interface - SPI for programming - Analog output - SPI for programming - Analog output - USART (UART + SPI) - OWU - TCI - UART - I2C - SPI SPI The following collateral will be available on E2E until officially released to the product page: TUSS44x0 E2E Content: BOOST-TUSS44x0 EVM-GUI Overview and Quick Start Video: Ultrasonic FAQ Archives: PGA460: <secret URL>/support/sensors/f/1023/t/640810 TDC1000: <secret URL>/support/sensors/f/1023/t/724028 TDC1000 no longer recommended for accurate flow metering. Please consider using the TUSS4470 as an alternative to the TDC1000 for all ultrasonic applications.",
+  "partNumber" : "NA",
+  "allResponseList" : [ {
+    "contentId" : "2762873",
+    "userName" : "Akeem Whitehead",
+    "rankPoints" : "21215",
+    "rankName" : "Mastermind",
+    "date" : "Nov 19, 2018 10:04 PM",
+    "userId" : "3766999",
+    "content" : "If you have any questions regarding this post or its linked content, start a new E2E discussion or thread."
+  } ],
+  "tags" : [ "/support/sensors/f/1023/tags/BOOSTXL_2D00_TUSS4440", "/support/sensors/f/1023/tags/PGA460%2b%2bMSP430FR6047", "/support/sensors/f/1023/tags/EVM430_2D00_FR6047", "/support/sensors/f/1023/tags/BOOST_2D00_TUSS4440", "/support/sensors/f/1023/tags/ultrasonic", "/support/sensors/f/1023/tags/TDC1011", "/support/sensors/f/1023/tags/BOOST_2D00_TUSS4470", "/support/sensors/f/1023/tags/TUSS4440", "/support/sensors/f/1023/tags/TUSS4470", "/support/sensors/f/1023/tags/TDC1011_2D00_Q1", "/support/sensors/f/1023/tags/USSC", "/support/sensors/f/1023/tags/PGA460", "/support/sensors/f/1023/tags/MSP430FR6047", "/support/sensors/f/1023/tags/TDC1000", "/support/sensors/f/1023/tags/PGA460_2D00_Q1", "/support/sensors/f/1023/tags/TDC1000_2D00_Q1", "/support/sensors/f/1023/tags/BOOSTXL_2D00_TUSS4470", "/support/sensors/f/1023/tags/TUSS", "/support/sensors/f/1023/tags/BOOSTXL_2D00_PGA460", "/support/sensors/f/1023/tags/time_2D00_of_2D00_flight", "/support/sensors/f/1023/tags/energia" ],
+  "fourmType" : "TI"
+}

data/json/DLP/753020.json

@@ -0,0 +1,23 @@
+{
+  "ticketNumber" : "753020",
+  "reporterName" : "Bill Johns",
+  "rankPoints" : "46985",
+  "resolutionStatus" : "Resolved",
+  "ticketName" : "[FAQ] BQ24040 and BQ2404X family Charge Complete Pin Behavior, /CHG",
+  "rankName" : "Mastermind",
+  "replies" : " 1",
+  "views" : " 2396",
+  "queryText" : "The BQ2404X family of charger has a charge complete pin, /CHG to indicate charge in progress or complete. But under some conditions the battery charge has stopped (no current to battery) but /CHG indicates charge. In other case the battery is charging (current to battery) but /CHG does not indicate charge in progress.",
+  "partNumber" : "NA",
+  "allResponseList" : [ {
+    "contentId" : "2781522",
+    "userName" : "Bill Johns",
+    "rankPoints" : "46985",
+    "rankName" : "Mastermind",
+    "date" : "Dec 5, 2018 10:34 PM",
+    "userId" : "244698",
+    "content" : "This also applies to BQ21040, BQ24050, BQ24090 and BQ25100 family of devices. The /CHRG pin in an open drain output used to indicate that a battery charge cycle is in progress. The pin will go low when the device detects a valid power supply and starts charging the battery. The pin will go high impedance when the device detects that the battery is fully charged (Change Complete/ Termination). In order to optimize end user experience the charger behavior under the particular cases below is as follows: 1.) If TS (NTC) pin indicates an over temp condition charge is suspended, but the /CHG pin will remain low since termination or charge complete has not been detected. Charge will resume when temp is reduced and the /CHG pin will remain low. 2.) The BQ2404X will automatically restart charge if after termination/charge complete the battery voltage drops to Recharge (V-RCH). This is done to maintain the battery fully charged. In this case the /CHG pin will remain high-Z after termination even if the recharge has started. 3.) During OVP shutdown or Charge Timer Fault /CHG is high –Z Note on First Charge Cycle-- will start when power is applied, disable / enable using TS pin or detect battery insertion, /CHG is low. Start charge cycle but not First charge cycle exiting TTDM mode or battery voltage below V-RCH. Additional info see BQ24040 Data Sheet Charge Complete Data Sheet section 8.3.7 also see Table in section 8.4.1. Note -- Updated section 2 May 20, 2019 -- To remain high-Z"
+  } ],
+  "tags" : [ "/support/power-management/f/196/tags/BQ24040" ],
+  "fourmType" : "TI"
+}

data/json/DLP/762756.json

@@ -0,0 +1,23 @@
+{
+  "ticketNumber" : "762756",
+  "reporterName" : "Bill Johns",
+  "rankPoints" : "46985",
+  "resolutionStatus" : "Resolved",
+  "ticketName" : "[FAQ] BQ24040 and BQ2404X family TS pin configuration of NTC and TTDM mode",
+  "rankName" : "Mastermind",
+  "replies" : " 1",
+  "views" : " 2731",
+  "queryText" : "The TS pin has multiple ways that it can be configured. What is the best way to connect it and how?",
+  "partNumber" : "NA",
+  "allResponseList" : [ {
+    "contentId" : "2819315",
+    "userName" : "Bill Johns",
+    "rankPoints" : "46985",
+    "rankName" : "Mastermind",
+    "date" : "Jan 14, 2019 3:52 PM",
+    "userId" : "244698",
+    "content" : "Hello This also applies to BQ21040, BQ24050 and BQ24090 family of devices. The TS pin options and configurations, the best arrangement will depend on the system requirements. Below is a summary of the modes and configurations. Normal battery Charge -- Connected to NTC thermistor in battery pack to monitor battery temp. 50uA current source will develop a voltage that is monitored by internal voltage comparators. Charge is suspended above 1230mV and below 178mV. If NTC is not used a 10k resistor will enable normal operation. Shutdown – Pull TS pin low to will disable charge. Termination and Timer Disable Mode (TTDM) – Float or drive high to enter TTDM. This mode is similar to a power supply mode. After charge is complete the voltage will remain applied to battery. TTDM Disable – Connect a 237k resistor to ground to disable the TTDM mode. Intended for battery pack removed and TTDM mode in not needed. In this condition charge is suspended and no voltage present. The typical configuration is to connect an NTC / 10k resistor to TS. If the battery pack is removable then TTDM mode to power the device is an option. For additional information see section 8.4.8 and 8.4.9 in data sheet."
+  } ],
+  "tags" : [ "/support/power-management/f/196/tags/BQ24040" ],
+  "fourmType" : "TI"
+}

data/json/DLP/763227.json

@@ -0,0 +1,23 @@
+{
+  "ticketNumber" : "763227",
+  "reporterName" : "Bill Johns",
+  "rankPoints" : "46985",
+  "resolutionStatus" : "Resolved",
+  "ticketName" : "[FAQ] BQ24040 and BQ2404X family Trouble Shooting Tips, No Output, Charge Current Low, Early Termination and Others.",
+  "rankName" : "Mastermind",
+  "replies" : " 1",
+  "views" : " 3987",
+  "queryText" : "What are some trouble shooting recommendation if we are seeing problems with the BQ24040 or similar devices.",
+  "partNumber" : "NA",
+  "allResponseList" : [ {
+    "contentId" : "2821311",
+    "userName" : "Bill Johns",
+    "rankPoints" : "46985",
+    "rankName" : "Mastermind",
+    "date" : "Jan 15, 2019 9:25 PM",
+    "userId" : "244698",
+    "content" : "This also applies to BQ21040, BQ24050 and BQ24090 family of devices. Some Trouble Shooting tip for the device family If the device does not start charge, no current to battery check: TS pin voltage needs to be between 278mV and 790mV for normal operation Check that input voltage is below OVP, 6.6V. Double check ISET and PRETERM resistors, low charge current could cause problems. Charge will start but current to battery is low of target: TS pin voltage needs to be in the normal range. At low temp half charge will reduce current TS between 790mV and 1230mV ISET2 pin, Float will limit current to 100mA Input voltage low, need 700mV to 1000mV drop across the device for full output current. Internal thermal limit, if the die temp reaches 125C output current is reduced to control thermal rise. The Charge May Terminate Early or at lower voltage: TS pin voltage needs to be in normal range. At hot temp charge voltage is reduce to 4.06V TS between 278mV and 178mV. Resistance between the battery and charger will increase voltage at BAT terminal and appear as higher battery voltage. Also: Battery or battery simulator required for test standard load will not work. CHG and PG pin will give some insight into condition of device. Check the voltage at ISET, it should be proportional to output current reduced by 400. Iout/400 * R-ISET. Voltage at ISET represents output current and voltage at PRETERM represents termination point. Battery voltage for normal charge current needs to be between 2.5V and 4.1V. Below or above and current is reduced."
+  } ],
+  "tags" : [ "/support/power-management/f/196/tags/BQ24040" ],
+  "fourmType" : "TI"
+}

data/json/DLP/787791.json

@@ -0,0 +1,23 @@
+{
+  "ticketNumber" : "787791",
+  "reporterName" : "Bill Johns",
+  "rankPoints" : "46985",
+  "resolutionStatus" : "Resolved",
+  "ticketName" : "[FAQ] BQ24040: BQ2404X Family Devices Schematic and Layout Review",
+  "rankName" : "Mastermind",
+  "replies" : " 1",
+  "views" : " 3375",
+  "queryText" : "Part Number: BQ24040 Hello Team I have completed my design and layout can someone review it for me?",
+  "partNumber" : " BQ24040",
+  "allResponseList" : [ {
+    "contentId" : "2913174",
+    "userName" : "Bill Johns",
+    "rankPoints" : "46985",
+    "rankName" : "Mastermind",
+    "date" : "Mar 29, 2019 6:36 AM",
+    "userId" : "244698",
+    "content" : "BQ24040 and BQ2404X family Checklist for Schematic and Layout Review. This also applies to BQ21040, BQ24050 and BQ24090 family of devices. Below items are good points to check during schematic and layout review for device. Note that some points may not apply to your specific device. Schematic / Layout: Pin 1 – IN, input filter capacitor 1uF to 10uF range required. Locate close to the device. Should be ceramic (MLCC) with good high frequency response. Voltage on the input may have a wide range size to match possible voltage range. Pin 2 – ISET, Resistor to ground to set output current should be located near the device with good return back to thermal pad. Pin 3 – VSS, Ground to thermal pad Pin 4 – PRETERM, Resistor to ground to set pre-charge and termination current should be located near the device with good return back to thermal pad. Pin 5 -- /PG, Open collector output pull up required. OK to float if not used. Pin 6 – NC (No Connect) – Open Pin 7 – ISET2, USB100/500 select pin pull high, low or float. Pin 8 -- /CHG, Open collector output pull up required. OK to float if not used. Pin 9 – TS, Connect to NTC resistor in battery pack or on board to limit temperature range of charge. Ground with 10k if not used. Note if used with removable battery pack protection from ESD or additional filtering is recommended. Pin 10 -- OUT, output filter capacitor 1uF to 10uF range required. Locate close to the device. Should be ceramic (MLCC) with good high frequency response. Voltage will be regulated to 4.2V lower voltage rating than input can be used. Thermal Pad – Linear regulators can have high power dissipation. Connect to thermal plane with mult vias. Power dissipation on ISET and PRETERM resistor is very low and can be small package. Also see layout section of Data Sheet, section 11."
+  } ],
+  "tags" : [ "/support/power-management/f/196/tags/BQ24040" ],
+  "fourmType" : "TI"
+}

data/json/DLP/815766.json

@@ -0,0 +1,23 @@
+{
+  "ticketNumber" : "815766",
+  "reporterName" : "Alex Bhandari-Young",
+  "rankPoints" : "15670",
+  "resolutionStatus" : "Resolved",
+  "ticketName" : "[FAQ] OPT3101: What are the resourcescompany provides for developing with OPT3101?",
+  "rankName" : "Genius",
+  "replies" : " 1",
+  "views" : " 3447",
+  "queryText" : "Part Number: OPT3101",
+  "partNumber" : " OPT3101",
+  "allResponseList" : [ {
+    "contentId" : "3019009",
+    "userName" : "Alex Bhandari-Young",
+    "rankPoints" : "15670",
+    "rankName" : "Genius",
+    "date" : "Jun 28, 2019 7:47 PM",
+    "userId" : "4691324",
+    "content" : "Getting started Training videos: <secret URL>/zero-hero-time-flight-training-series Device datasheet: <secret URL>/lit/ds/symlink/opt3101.pdf Evaluation OPT3101EVM is available here: <secret URL>/tool/OPT3101EVM Device is pre-calibrated and ready for use. EVM demonstrates using OPT3101 for long range single channel ToF distance measurements. TIDA010021 is a reference design demonstrating OPT3101 used for wide field-of-view with multiple zones of detection. It is available here: <secret URL>/tool/TIDA-010021 System level design (component selection and board design) System design involves optical component selection and board design and layout. The system design guide provides all the necessary theory and instructions for this process. The estimator tool helps with selecting optical emitters and photodiodes and estimating performance, range, and accuracy for these components. system design guide: <secret URL>/lit/ug/sbau305b/sbau305b.pdf system estimator tool: <secret URL>/tool/OPT3101ESTIMATOR-SW Calibration Tools The SDK tool provides all C++ functions needed for calibration. This can be integrated to an existing system or run on any host with C++ compiler (microprocessor, linux PC, windows, etc.). It can also be used in calibration tool mode on acompany MSP430 launchpad to speed calibration process which requires no coding and simply commenting a line of code per calibration step and compiling the code in Code Composer Studio. Details of this method are run through step-by-step in the SDK user guide document included in the SDK. SDK: <secret URL>/tool/OPT3101-SDK The configurator tool is a graphical interface for selecting the OPT3101 settings to use for the design. It generates an SDK configuration file with register settings that can be imported to the SDK and eliminates the need to select individual register settings. Configurator tool: <secret URL>/tool/OPT3101CONFIG-SW Documents How to calibrate doc: <secret URL>/lit/pdf/slau791 Register level calibration doc: <secret URL>/lit/pdf/sbau310 App notes We have a number of app notes that give more details on a variety of topics. These are available here: <secret URL>/product/OPT3101/technicaldocuments#doctype1 Overview of collateral <secret URL>/product/OPT3101#design-resources-for-you"
+  } ],
+  "tags" : [ "/support/sensors/f/1023/tags/OPT3101" ],
+  "fourmType" : "TI"
+}

data/json/DLP/816332.json

@@ -0,0 +1,31 @@
+{
+  "ticketNumber" : "816332",
+  "reporterName" : "Akash Gondalia",
+  "rankPoints" : "39385",
+  "resolutionStatus" : "Resolved",
+  "ticketName" : "[FAQ] IWR6843 Antenna-on-Package (AoP) Frequently Asked Questions",
+  "rankName" : "Mastermind",
+  "replies" : " 2",
+  "views" : " 4941",
+  "queryText" : "Hello Everyone, Please see the below Frequently Asked Questions on the IWR6843 AoP Device and IWR6843AOPEVM. Cheers, Akash",
+  "partNumber" : "NA",
+  "allResponseList" : [ {
+    "contentId" : "3022091",
+    "userName" : "Nitin Sakhuja",
+    "rankPoints" : "21725",
+    "rankName" : "Mastermind",
+    "date" : "Jul 2, 2019 3:23 PM",
+    "userId" : "1602842",
+    "content" : "Thanks for the information. -Nitin"
+  }, {
+    "contentId" : "3233422",
+    "userName" : "Akash Gondalia",
+    "rankPoints" : "39385",
+    "rankName" : "Mastermind",
+    "date" : "Jan 20, 2020 7:27 PM",
+    "userId" : "4768107",
+    "content" : "Frequently Asked Questions on the IWR6843AoPEVM: Antenna Questions: Q: How deep in the chip is the antenna located (in order to find proper distance for cover placement)? Is there any material interface (through which waves are passing) on the top of the chip that should be taken in account? A: Antenna is located on the Top side of the Package itself. There is no material interface, Antennas are located on the top surface of the package. Hence for the distance measurement you could consider top side of the package. Q: Is it possible to place cover directly in contact with the chip front? Or should there be at least half wavelength gap? A: It's recommended to keep at-least multiple of half wavelength distance. Please refer to this app-note section 5. Q: How does Angular Resolution compare from AoP to ISK antenna? A: IWR6843AOP has different antenna configuration, hence it has equal angular resolution both in Azimuth and Elevation direction. Q: What is the antenna pattern for IWR6843AoPEVM? A: Rx Pattern: Tx Pattern: Q: What is the arrangement of Transmitters and Receivers on IWR6843AOPEVM? Below diagram has the antenna placement and positions of virtual Antenna pairs. Schematics: Q: Are schematics of the IWR6843AOPEVM available? A: Yes they are! You can find schematic, assembly, and BOM on the IWR6843AOP Landing Page under the Design Files Section. Visualizer Error: Q: When I am trying to connect send config to mmWave device, then it is showing an error \"Selected Platform [xWR68xx_AOP] not matching that reported by target [xWR68xx]\". A: This error occurs when the AoP EVM has been flashed with binaries from the Non-AoP SDK. You should instead flash the EVM with 64xx_AoP binary from the appropriate AoP SDK. EVM Questions: Q: Do I need to purchase an MMWAVEICBOOST Carrier card with my AoP EVM? A: The MMWAVEICBOOST is highly recommend for development and debug purposes. The board provides debug, raw data capture connectivity, SPI and interface to the antenna board peripherals etc. whereas in standalone mode you have access to UART, you can flash the EVM and get data out of the UART port. Q: Is Heat Sink necessary for IWR6843AoPEVM? A: Heat sink is not a mandatory requirement for the EVM. However, EVM comes with the example heat sink option for the EVM, Heat sink helps in reducing the junction temperature. Below curve shows duty-cycle vs temperature in deg centigrade. There are four curves two of them shows temperature difference with and without heat sink options. Other two curves are best fit linear trend lines for the with and without heat sink options. Below graph is specific example of heat sink and customers could choose to design their own heat sink depending upon their application needs. Also customers could choose to operate different duty-cycle options depending upon the application requirements.care need to be taken not to exceed the junction temperature beyond 105 deg C. Q: What other boards do I need to use IWR6843AoPEVM AoPEVM could be used standalone configuration, in this case one could flash the EVM and run demo applications. Extended section of the EVM allows connectivity to other chipsets such as Bluetooth, 9-Axis sensor, LCD interfaces. Note that some of these components are not pre-mounted along with the EVM, customer need to mount these components. 60Pin connector on the back side of the board allows connectivity to MMWAVEICBOOST from which customers could connect to XDS110 interface/14 pin/60 pin MIPI connector for JTAG and other advanced debugging options. With the help of Carrier board (MMWAVEICBOOST, DCA1000 and IWR6843AoPEVM) raw ADC data could be captured using mmWave studio application. For more details please refer to EVM user-guide. Q: How can I use the break out board part of the IWR6843AoPEVM and implications? EVM is designed for form-factor usage, Customers could choose to breakout section to separate the EVMs into two pieces. Once EVMs are separated it cannot be joined together. After the break-away EVM module would be 23 x 22 mm size. This section offers one USB connector and slide switch for flashing mode and default functional mode options. Care need to be taken on the thermal heat dissipation, at higher duty-cycle heat sink option need to be considered so that junction temperature should not exeeded 105 deg C. Q: What Demos are available for IWR6843AoPEVM ? The following demos are available for IWR6843AOPEVM MMWAVE SDK Demo - 68xx AOP 68xx - Area Scanner ROS Point Cloud Visualizer Autonomous Robotics with ROS for mmWave Multiple Gesture and Motion Detection Lab - 68xx Q: Can I run IWR6843ISK code on IWR6843AoPEVM ? How? Compared to the IWR6843ISK, the IWR6843AOPEVM has a different antenna design and this requires modifications to the angle of arrival computation corresponding to the IWR6843AOPEVM virtual antenna array. To develop basic understanding of virtual antenna arrays and angle of arrival estimation concepts, refer to the following resources mmWave Training Series training video: Intro to mmWave Sensing – Angle Estimation MIMO Radar app note The IWR6843AOPEVM is supported by mmWave SDK 3.2.0.x_AOP which provides the 2D AoA DPU (Data Processing Unit) for angle of arrival estimation on the AOP device. This AoA technique is not supported in mmWave SDK 3.2.0.x for IWR6843ISK so the user will need to modify/replace the angle of arrival code in the ISK based application according to the AoA technique demonstrated in the 2D AoA DPU used in the IWR6843AOP out of box demo. Please refer to the following documentation resources included in mmWave SDK 3.2.0.x_AOP to understand the IWR6843AOP out of box demo and the 2D AoA technique. MMWAVE-SDK 3.2.0.6 Module Documentation. AOP Out of box demo: xwr64xx mmw Demo (for IWR6xxx ISK and AOP platforms) 2D AoA DPU: AoA (angle of arrival) using 2D FFT method"
+  } ],
+  "tags" : [ "/support/sensors/f/1023/tags/IWR6843", "/support/sensors/f/1023/tags/MMWAVE_2D00_SDK", "/support/sensors/f/1023/tags/IWR6843AOPEVM", "/support/sensors/f/1023/tags/IWR6843ISK", "/support/sensors/f/1023/tags/MMWAVEICBOOST" ],
+  "fourmType" : "TI"
+}

data/json/DLP/837889.json

@@ -0,0 +1,31 @@
+{
+  "ticketNumber" : "837889",
+  "reporterName" : "Charles-Chen",
+  "rankPoints" : "5435",
+  "resolutionStatus" : "Resolved",
+  "ticketName" : "[FAQ] CCS/LP5036: How to master LP50xx device within five minutes? Please provide the quick start guide of LP5009, LP5012, LP5018, LP5024, LP5030, LP5036 device.",
+  "rankName" : "Expert",
+  "replies" : " 2",
+  "views" : " 2800",
+  "queryText" : "Part Number: LP5036 Tool/software: Code Composer Studio Q1: What’s the right direction when USB2ANY module is connected to the LP50xx EVM? Q2: What is the purpose of color mixing? Is it similar with brightness control? Why there is no individual brightness control for each output channel? Q3: How to achieve a user-defined dynamic lighting pattern with LP50xx device? Q4: How to control the color temperature of RGB- LEDs using LP50xx device? Q5: How to estimate the junction temperatures of LP50xx device?",
+  "partNumber" : " LP5036",
+  "allResponseList" : [ {
+    "contentId" : "3098584",
+    "userName" : "Charles-Chen",
+    "rankPoints" : "5435",
+    "rankName" : "Expert",
+    "date" : "Sep 10, 2019 12:56 PM",
+    "userId" : "6102657",
+    "content" : "Q1: What’s the right direction when USB2ANY module is connected to the LP50xx EVM? Fig.1 shows the right direction when the USB2ANY module is connected to the LP50xx EVM. Please pay attention to the part marked in the blue block. For more details concerning hardware setup of LP50xx EVM, please refer to the corresponding user’s guide. I provide a link here to download the user’s guide of LP5024. Fig.1 Q2: What is the purpose of color mixing? Is it similar with brightness control? Why there is no individual brightness control for each output channel? Color-mixing means that different color can be decomposed of different proportions of RGB. You can configure the proportions of RGB to get desired colors. The proportions of RGB are controlled by configuring the brightness of each R,G and B LEDs. The PWM duty ratio control is related to the brightness of each channel. As shown in Fig.2, PWM duty cycle is defined as the product obtained by multiplying the color-mixing register value (Outx_color) by the related intensity-control register value (LEDx_Brightness). Actually brightness of each output channel can be controlled by the register OUTx_Color individually. However, the value of OUTx_Color will affect the proportions of RGB. When color is fixed, the independent intensity control (LEDx_Brightness) is used to achieve accurate and flexible dimming control for every RGB LED module. Besides, OUTx_Color register can be used to adjust the brightness independently for single color LEDs. Fig.2 Q3: How to make a user-defined dynamic lighting pattern with LP50xx device? Can you provide the sample code and Linux driver? Actually, you have two choices to achieve user-defined dynamic lighting pattern with LP50xx device. Choice A: You can use micro controller, such as MCU or DSP, to control the LP50XX to achieve a user-defined dynamic lighting pattern. I provide the links here to download the sample code and Linux driver. Choice B: You can initialize, set up and play with the LEDs from a C program through USB2ANY SDK. For more details concerning USB2ANY SDK, such as code example, please refer to this thread."
+  }, {
+    "contentId" : "3103488",
+    "userName" : "Charles-Chen",
+    "rankPoints" : "5435",
+    "rankName" : "Expert",
+    "date" : "Sep 15, 2019 7:28 AM",
+    "userId" : "6102657",
+    "content" : "Q4: How to control the color temperature of RGB- LEDs using LP50xx device? Fig.3 Let (xi, yi, i=R, G, B) denote the CIE 1931 chromaticity coordinates and (Φi, i=R, G, B) denote the luminous flux of the light emitted by the ith LEDs. (x, y) represents the color coordinates of light synthesized by RGB-LEDs. CCT means correlated color temperature. Since variations of the (xi, yi, i=R, G, B) are relatively small, the CCT synthesized by RGB-LEDs can be expressed as a function of the flux ratios Φi/ ΦB. Hence, you can control the color temperature by adjusting the proportions of RGB by OUTx_color according to the formulas shown in Fig.3. Q5: How to estimate the junction temperatures of LP50xx device? Since there is only a very small percentage of heat energy in a typical plastic package is convected and radiated off the top surface of the package. Hence, if one assumes the entire power is dissipated by the top surface, the junction temperature calculated by RθJC is higher than reality. This limitation of RθJC is overcome by the new thermal metric, ΨJT. ΨJT is recommended to estimate the junction temperatures. For calculation of Pd (power dissipation), please refer to the training video here. For more details about ΨJT, You can refer to the application report of \"Semiconductor and IC Package Thermal Metrics\"."
+  } ],
+  "tags" : [ "/support/power-management/f/196/tags/LP5009", "/support/power-management/f/196/tags/LP5024", "/support/power-management/f/196/tags/LP5036", "/support/power-management/f/196/tags/code%2bComposer%2bstudio", "/support/power-management/f/196/tags/usb2any", "/support/power-management/f/196/tags/LP5030", "/support/power-management/f/196/tags/LP5018", "/support/power-management/f/196/tags/LP5012" ],
+  "fourmType" : "TI"
+}

data/json/DLP/871078.json

@@ -0,0 +1,23 @@
+{
+  "ticketNumber" : "871078",
+  "reporterName" : "Joel Hernandez II",
+  "rankPoints" : "25800",
+  "resolutionStatus" : "Resolved",
+  "ticketName" : "[FAQ] BQ25710, BQ25713, BQ25713B, BQ25700A, BQ25703A, BQ25708 - Schematic Review Design Tips",
+  "rankName" : "Mastermind",
+  "replies" : " 1",
+  "views" : " 807",
+  "queryText" : "The following document shows key considerations when choosing external components for your BQ25710, BQ25713, BQ25713B, BQ25700A, BQ25703A, BQ25708 design, as well as the tradeoffs. The BQ257xx family of devices are 1-4 cell buck-boost charge controllers that require a host via SMBus or I2C to operate. The attached document is a checklist for reviewing the design of this particular family of devices. It details the external component selection and pin connections, as well as minimum requirements for proper operation of the charger. Components are numbered to match the BQ25710EVM and BQ25713EVM reference design schematic component designators. The component selection is details in the following four categories: Required - Absolutely required for proper operation Recommended - Recommended to optimize performance Recommended-DNP - Recommend as a non-populated component footprints to improve performance post-fabrication Optional - Optional componetns Using this information, customer can reduce external components based on their application, as well as use this document to help in assisting with schematic reviews. Regards, Joel H",
+  "partNumber" : "NA",
+  "allResponseList" : [ {
+    "contentId" : "3222422",
+    "userName" : "Joel Hernandez II",
+    "rankPoints" : "25800",
+    "rankName" : "Mastermind",
+    "date" : "Jan 9, 2020 12:09 AM",
+    "userId" : "4615895",
+    "content" : "6712.BQ2571X_SchematicChecklist_CalculationTool.pdf"
+  } ],
+  "tags" : [ "/support/power-management/f/196/tags/BQ25700A", "/support/power-management/f/196/tags/review", "/support/power-management/f/196/tags/BQ25713B", "/support/power-management/f/196/tags/4%2bcell", "/support/power-management/f/196/tags/buck%2bboost", "/support/power-management/f/196/tags/schematic", "/support/power-management/f/196/tags/power%2bpath", "/support/power-management/f/196/tags/buck_2D00_boost", "/support/power-management/f/196/tags/BQ25713", "/support/power-management/f/196/tags/BQ25710EVM", "/support/power-management/f/196/tags/BQ25710", "/support/power-management/f/196/tags/BQ25703A", "/support/power-management/f/196/tags/BQ25703AEVM", "/support/power-management/f/196/tags/NVDC", "/support/power-management/f/196/tags/BQ25700AEVM", "/support/power-management/f/196/tags/bq25713EVM", "/support/power-management/f/196/tags/BQ25708" ],
+  "fourmType" : "TI"
+}

data/json/DLP/872937.json

@@ -0,0 +1,23 @@
+{
+  "ticketNumber" : "872937",
+  "reporterName" : "Brett Colteaux",
+  "rankPoints" : "1795",
+  "resolutionStatus" : "Resolved",
+  "ticketName" : "[FAQ] TPS23882: Is the TPS23882 Type-3 2-pair IEEE 802.3bt (30W/15.4W) compliant? Where can I find TPS23882 passing Sifos conformance test reports to be certain?",
+  "rankName" : "Intellectual",
+  "replies" : " 1",
+  "views" : " 566",
+  "queryText" : "Part Number: TPS23882 Is the TPS23882 Type-3 2-pair IEEE 802.3bt (30W/15.4W) compliant? Where can I find TPS23882 passing Sifos conformance test reports to be certain?",
+  "partNumber" : " TPS23882",
+  "allResponseList" : [ {
+    "contentId" : "3229274",
+    "userName" : "Brett Colteaux",
+    "rankPoints" : "1795",
+    "rankName" : "Intellectual",
+    "date" : "Jan 15, 2020 6:48 PM",
+    "userId" : "4406190",
+    "content" : "The TPS23882 is Type-3 2-pair IEEE 802.3bt (30W/15.4W) compliant and has received an interoperability score of 100% on Sifos IEEE 802.3bt 2-pair conformance test suite version 5.1.company has passing Sifos test reports for the TPS23882 under various configurations. The configuration of the TPS23882 when these reports were generated is shown in the table below: Report Name 2-Pair Allocated Power Device Mode of Operation Memory Utilization: ROM or SRAM Version Hardware Required GUI Used for Configuration PSA_report_T3_15W_x82_P5_AUTO.xlsm 15.4W Autonomous ROM TPS23882EVM-008 + BOOST-PSEMTHR8-097 N/A – Autonomous operation resistor for 15.4W ( = 124 kΩ) utilized. PSA_report_T3_30W_x82_P5_AUTO.xlsm 30W Autonomous ROM TPS23882EVM-008 + BOOST-PSEMTHR8-097 N/A - Autonomous operation resistor for 30W ( = 62 kΩ) utilized. PSA_report_T3_15W_x82_P5_ROM.xlsm 15.4W Auto ROM TPS23882EVM-008 + BOOST-PSEMTHR8-097 TPS2388x EVM GUI PSA_report_T3_30W_x82_P5_ROM.xlsm 30W Auto ROM TPS23882EVM-008 + BOOST-PSEMTHR8-097 TPS2388x EVM GUI PSA_report_T3_15W_x82_P5_FWv0x03.xlsm 15.4W Auto SRAM version 0x03 TPS23882EVM-008 + BOOST-PSEMTHR8-097 TPS2388x EVM GUI PSA_report_T3_30W_x82_P5_FWv0x03.xlsm 30W Auto SRAM version 0x03 TPS23882EVM-008 + BOOST-PSEMTHR8-097 TPS2388x EVM GUI PSA_report_T3_15W_P1_x82_FirmPSE_v00.01.33.00.xlsm 15.4W Semi-Auto SRAM version 0x03 FIRMPSEEVM2P-BDL (TPS23882EVM-084 + PSEMCUDAUEVM-082 + PSEMTHR24EVM-081 bundle) TI’s FirmPSE PSE system firmware version 00.01.33.00 PSA_report_T3_30W_P1_x82_FirmPSE_v00.01.33.00.xlsm 30W Semi-Auto SRAM version 0x03 FIRMPSEEVM2P-BDL (TPS23882EVM-084 + PSEMCUDAUEVM-082 + PSEMTHR24EVM-081 bundle) TI’s FirmPSE PSE system firmware version 00.01.33.00 The above mentioned reports can be found in the following zip file for reference: 1212.TPS23882 Sifos Test Reports.zip IEEE 802.3bt Interoperability Note IEEE 802.3bt compliant devices are backwards compatible with IEEE 802.3at and IEEE 802.3af compliant devices. For example, an IEEE 802.3at compliant PD and/or IEEE 802.3af compliant PD will interoperate with an IEEE 802.3bt compliant PSE.company believes it is advantageous to design with IEEE 802.3bt compliant devices moving forward for 4-Pair and 2-Pair operation due to the benefits that the .bt standard offers over previous standards such as the new MPS signature, autoclass, power demotion, and more. Additional Resources Get started on your 2-Pair Ethernet Switch design with TI’s 24-Port (2-pair) power sourcing equipment reference design for multi-port applications and FirmPSE PSE system firmware. For 4-pair Ethernet Switch designs, consider TI’s 24-Port (4-pair) power sourcing equipment reference design for multi-port applications and FirmPSE PSE system firmware. Check out TI’s PoE Training Portal to learn about PoE fundamentals and the new .bt standard. Watch the training video IEEE 802.3btcompany PSE New Features to learn about PSE features introduced in the .bt standard."
+  } ],
+  "tags" : [ "/support/power-management/f/196/tags/PoE", "/support/power-management/f/196/tags/interoperability", "/support/power-management/f/196/tags/Sifos", "/support/power-management/f/196/tags/TPS23882", "/support/power-management/f/196/tags/COMPLIANCE" ],
+  "fourmType" : "TI"
+}

data/json/DLP/875388.json

@@ -0,0 +1,23 @@
+{
+  "ticketNumber" : "875388",
+  "reporterName" : "Ning T",
+  "rankPoints" : "15365",
+  "resolutionStatus" : "",
+  "ticketName" : "[FAQ] BQ24190: BQ2419x/BQ2429x FAQs",
+  "rankName" : "Genius",
+  "replies" : " 1",
+  "views" : " 504",
+  "queryText" : "Part Number: BQ24190 Please refer to below for BQ2419x/BQ2429x top frequently asked questions. BQ2419x_29x_ FAQ.pdf",
+  "partNumber" : " BQ24190",
+  "allResponseList" : [ {
+    "contentId" : "3238421",
+    "userName" : "Ning T",
+    "rankPoints" : "15365",
+    "rankName" : "Genius",
+    "date" : "Jan 25, 2020 2:46 AM",
+    "userId" : "145100",
+    "content" : "Thanks, Ning."
+  } ],
+  "tags" : [ "/support/power-management/f/196/tags/BQ24296", "/support/power-management/f/196/tags/BQ24295", "/support/power-management/f/196/tags/BQ24298", "/support/power-management/f/196/tags/bq2429x", "/support/power-management/f/196/tags/BQ24192", "/support/power-management/f/196/tags/bq24292i", "/support/power-management/f/196/tags/BQ24190", "/support/power-management/f/196/tags/BQ2419x", "/support/power-management/f/196/tags/bq24297", "/support/power-management/f/196/tags/bq24195" ],
+  "fourmType" : "TI"
+}

data/json/DLP/879951.json

@@ -0,0 +1,95 @@
+{
+  "ticketNumber" : "879951",
+  "reporterName" : "Revanth A1",
+  "rankPoints" : "170",
+  "resolutionStatus" : "TI Thinks Resolved",
+  "ticketName" : "PTD08D210W: UCD9248 controled by PTD08D210 problem",
+  "rankName" : "Prodigy",
+  "replies" : " 11",
+  "views" : " 95",
+  "queryText" : "Part Number: PTD08D210W Hi, I found that PTD08D210 is generating a voltage of 5.9V even when the UCD9248 is not configured. PTD08D210 has two power output and this problem is seen only in one channel, I even erased the UCD Flasmemory and confirmed that no PWM is going to PTD08D210 but still i see 5.9V in one of the channel. Note: My evel board has 4 PTD08D210 which means 8 o/p voltage channels and 2 UCD9248 to control it , out of which in only one channel i have this problem. Is it the problem with the PTD08D210 , it was working fine only suddenly in one day this problem happened.",
+  "partNumber" : " PTD08D210W",
+  "allResponseList" : [ {
+    "contentId" : "3255942",
+    "userName" : "iAlejandro",
+    "rankPoints" : "2390",
+    "rankName" : "Intellectual",
+    "date" : "Feb 13, 2020 6:44 PM",
+    "userId" : "5259049",
+    "content" : "Hi Revanth, If comfortable, can you provide more information about your application? Application conditions: Input and Output voltage, output current? (the device is rated to provide an output range from 0.7 V to 3.6 V) Perhaps we can take a look at your circuit schematic? Thanks, Alejandro"
+  }, {
+    "contentId" : "3256424",
+    "userName" : "Revanth A1",
+    "rankPoints" : "170",
+    "rankName" : "Prodigy",
+    "date" : "Feb 14, 2020 4:59 AM",
+    "userId" : "5998636",
+    "content" : "Hi, Alejandro Kindly look into thje attached pdf zc702_Schematic_xtp185_rev1_0.pdfPage 43, U19 The output is rated at 1.5V and 3.3V for this particular PTD in which the 1.5V channel is having the problem"
+  }, {
+    "contentId" : "3264169",
+    "userName" : "iAlejandro",
+    "rankPoints" : "2390",
+    "rankName" : "Intellectual",
+    "date" : "Feb 21, 2020 5:35 PM",
+    "userId" : "5259049",
+    "content" : "Hi Revanth, I reviewed your schematic and everything seems okay. You mentioned that it was working before and eventually something happened; Can you tell me more details about that? Did it involve updating anything on the UCD? Regards, Alejandro"
+  }, {
+    "contentId" : "3264611",
+    "userName" : "Revanth A1",
+    "rankPoints" : "170",
+    "rankName" : "Prodigy",
+    "date" : "Feb 22, 2020 9:50 AM",
+    "userId" : "5998636",
+    "content" : "Hi, Alejandro One sudden day we noticed our DDR Not working, then when we checked the voltage going to DDR section from PTD it was 2.5 V instead of 1.5 V, then when we isolated the DDR , WE found that the voltage from PTD IS 5.6 V half of the input voltage to PTD AND UCD., We earsed the UCD Flash memory to and even when no PWM IS going to PTD it generates 5.9 V. I just thinking to change the PTD and see."
+  }, {
+    "contentId" : "3268794",
+    "userName" : "Jimmy Hua",
+    "rankPoints" : "17640",
+    "rankName" : "Genius",
+    "date" : "Feb 27, 2020 12:28 AM",
+    "userId" : "4798049",
+    "content" : "Hi Revanth, Is there an update on this? If you were to swap out the PTD08D210 for a new one, does the problem still occur? How many of these failures have you seen occur in your application? Regards, Jimmy"
+  }, {
+    "contentId" : "3271366",
+    "userName" : "Revanth A1",
+    "rankPoints" : "170",
+    "rankName" : "Prodigy",
+    "date" : "Feb 29, 2020 4:16 AM",
+    "userId" : "5998636",
+    "content" : "Hi, Jimmy Just now received the components and will update the status once the rework has been done. In our application we have faced these issue two times (at rail 1.5V and at Rail 3.3V)."
+  }, {
+    "contentId" : "3272477",
+    "userName" : "Jimmy Hua",
+    "rankPoints" : "17640",
+    "rankName" : "Genius",
+    "date" : "Mar 2, 2020 4:02 PM",
+    "userId" : "4798049",
+    "content" : "Hi Revanth, Please keep Alejandro and I updated on your additional testing at your earliest convenience. Regards, Jimmy"
+  }, {
+    "contentId" : "3292983",
+    "userName" : "Jimmy Hua",
+    "rankPoints" : "17640",
+    "rankName" : "Genius",
+    "date" : "Mar 20, 2020 8:12 PM",
+    "userId" : "4798049",
+    "content" : "Hi Revanth, Do you have any updates for both Alejandro and I? Regards, Jimmy"
+  }, {
+    "contentId" : "3293174",
+    "userName" : "Revanth A1",
+    "rankPoints" : "170",
+    "rankName" : "Prodigy",
+    "date" : "Mar 21, 2020 5:28 AM",
+    "userId" : "5998636",
+    "content" : "Hi, Jimmy we tried replacing the IC which was available in the PTD , instead of replacing the whole PTD but it dint workout, now we have sent our board to remove the whole PTD (Since the ground thermal pads are thick it difficult to remove easily). but now due the situation due to COVID-19 , most of the companies are shutdown now and it will take some time to receive our board. I will let yu know once we receive and test it. Thanks!"
+  }, {
+    "contentId" : "3297251",
+    "userName" : "Jimmy Hua",
+    "rankPoints" : "17640",
+    "rankName" : "Genius",
+    "date" : "Mar 25, 2020 10:05 PM",
+    "userId" : "4798049",
+    "content" : "Hi Revanth, Sorry I missed your reply and thank you for the update. It is unfortunate that we are in the COVID-19 predicament and I hope all is well on your end. I will keep this thread up on place it under \"Waiting for Customer\" status and will ping me when you reply back with more information on this. Regards, Jimmy"
+  } ],
+  "tags" : [ "/support/power-management/f/196/tags/PTD08D210W", "/support/power-management/f/196/tags/UCD9248", "/support/power-management/f/196/tags/PTD08D210%2bUCD9248%2b%2b%2bOVP" ],
+  "fourmType" : "TI"
+}

data/json/DLP/881174.json

@@ -0,0 +1,95 @@
+{
+  "ticketNumber" : "881174",
+  "reporterName" : "Tommy Tzeng",
+  "rankPoints" : "1320",
+  "resolutionStatus" : "TI Thinks Resolved",
+  "ticketName" : "BQ30Z554-R1: bq30z55DBTRRR3 DFW issue",
+  "rankName" : "Expert",
+  "replies" : " 23",
+  "views" : " 177",
+  "queryText" : "Part Number: BQ30Z554-R1 Hi Team, i have a problem,cusotmer use BQ30Z55DBTR-R3 for battery pack solution has been M/P,but DFW issue occur random. was started by DFW, we have reset IC to clear the PF flag but DFW still happen, how can i avoid this problem? or have any idea and suggestion for us. attachment is schematic. JM2SP068PPV600A_schematic (003).pdf",
+  "partNumber" : " BQ30Z554-R1",
+  "allResponseList" : [ {
+    "contentId" : "3259316",
+    "userName" : "Kang Kang",
+    "rankPoints" : "17055",
+    "rankName" : "Genius",
+    "date" : "Feb 18, 2020 5:11 AM",
+    "userId" : "3528441",
+    "content" : "Hello Tommy, Sorry, can you clarify, what is DFW?"
+  }, {
+    "contentId" : "3262365",
+    "userName" : "Tommy Tzeng",
+    "rankPoints" : "1320",
+    "rankName" : "Expert",
+    "date" : "Feb 20, 2020 8:51 AM",
+    "userId" : "5169797",
+    "content" : "Hi Kang Kang, FYI."
+  }, {
+    "contentId" : "3268858",
+    "userName" : "Tommy Tzeng",
+    "rankPoints" : "1320",
+    "rankName" : "Expert",
+    "date" : "Feb 27, 2020 2:05 AM",
+    "userId" : "5169797",
+    "content" : "Hi Kang Kang, have any idea or suggestion?"
+  }, {
+    "contentId" : "3271218",
+    "userName" : "Kang Kang",
+    "rankPoints" : "17055",
+    "rankName" : "Genius",
+    "date" : "Feb 28, 2020 10:23 PM",
+    "userId" : "3528441",
+    "content" : "Hello Tommy, Can you check the cycle count and attach the gg file? The DF flash write not successful may mean that the flash is worn out. If this is the case, we should see a high cycle count number in the gg file."
+  }, {
+    "contentId" : "3279909",
+    "userName" : "Tommy Tzeng",
+    "rankPoints" : "1320",
+    "rankName" : "Expert",
+    "date" : "Mar 9, 2020 2:04 PM",
+    "userId" : "5169797",
+    "content" : "Hi Kang Kang, but will this this complete charge and discharge increase once? does this have anything to do with the number of write? because we have confirmed that the cycle count of the PACK returned by DFW is more 100 and more than 200,but there are also less than 100, so i don't see this kind of problem appear in the datasheet after using DF flash write many times, so could you help confirm this issue?or is there any way to avoid this kind of problem."
+  }, {
+    "contentId" : "3280601",
+    "userName" : "Kang Kang",
+    "rankPoints" : "17055",
+    "rankName" : "Genius",
+    "date" : "Mar 9, 2020 9:54 PM",
+    "userId" : "3528441",
+    "content" : "Hello Tommy, This most likely means a dataflash is worn out. I am just wondering how many times this has been out in the field. I'll check the conditions for this bit setting."
+  }, {
+    "contentId" : "3280672",
+    "userName" : "Kang Kang",
+    "rankPoints" : "17055",
+    "rankName" : "Genius",
+    "date" : "Mar 9, 2020 11:30 PM",
+    "userId" : "3528441",
+    "content" : "Hello Tommy, During firmware operation, the gauge will try to update Ra tables or Qmax or lifetimes or some other impedance tracking parameter. The bit is set because when the gauge writes to flash, it will try to read back what it wrote. In this case, if the read back is different, the DFW bit is set. The most likely reason would be dataflash is worn out. Can you provide more information on how many packs are experiencing this failure? It could be that some of these packs may have been subject to multiple host side writes and caused the flash to wear out and gauge to unable to write to flash. Who is the end customer?"
+  }, {
+    "contentId" : "3282589",
+    "userName" : "Tommy Tzeng",
+    "rankPoints" : "1320",
+    "rankName" : "Expert",
+    "date" : "Mar 11, 2020 10:17 AM",
+    "userId" : "5169797",
+    "content" : "Hi Kang Kang, Can you provide more information on how many packs are experiencing this failure? ans:11/55000 failure rate 0.02%, end custimer is Pegatron. if have DFW problem issue, will it cause IC damage? ic function be normal? as attached is customer the gg file, please reference. JS4HS002P1542000101.txt"
+  }, {
+    "contentId" : "3284723",
+    "userName" : "Kang Kang",
+    "rankPoints" : "17055",
+    "rankName" : "Genius",
+    "date" : "Mar 12, 2020 7:41 PM",
+    "userId" : "3528441",
+    "content" : "Hello Tommy, This does look like a potential flash corruption. Are you able to still communicate with the \"DFW bit set packs\"?"
+  }, {
+    "contentId" : "3293615",
+    "userName" : "Tommy Tzeng",
+    "rankPoints" : "1320",
+    "rankName" : "Expert",
+    "date" : "Mar 23, 2020 4:09 AM",
+    "userId" : "5169797",
+    "content" : "Hi Kang Kang, if DFW is turn off(n/a), what other offect will it have?"
+  } ],
+  "tags" : [ "/support/power-management/f/196/tags/BQ30Z554_2D00_R1" ],
+  "fourmType" : "TI"
+}

data/json/DLP/882868.json

@@ -0,0 +1,95 @@
+{
+  "ticketNumber" : "882868",
+  "reporterName" : "user5392072",
+  "rankPoints" : "330",
+  "resolutionStatus" : "Resolved",
+  "ticketName" : "IWR6843ISK: Unable to connect to Demo Visualizer using IWR6843ISK",
+  "rankName" : "Intellectual",
+  "replies" : " 32",
+  "views" : " 206",
+  "queryText" : "Part Number: IWR6843ISK Hi there， I am unable to connect my IWR6843ISK to the demo visualizer.I am able to use uniflash to flash the pplcount lab xwr68x.bin file of iwr6843isk in the lab, and then use the pplcount gui.exe program to get the point cloud map.During the setup of the IWR6843ISK i have correctly using the correct serial port. But whenever i press \"send config to the mmwave device\" it will show that com port 50 and com port 51 is \"waiting for data\". I hope I can get help, thank you very much, looking forward to your reply. Thanks.",
+  "partNumber" : " IWR6843ISK",
+  "allResponseList" : [ {
+    "contentId" : "3265441",
+    "userName" : "Justin Curewitz",
+    "rankPoints" : "23615",
+    "rankName" : "Mastermind",
+    "date" : "Feb 24, 2020 3:02 PM",
+    "userId" : "5118664",
+    "content" : "Hi, You are using the wrong visualizer. Please read the manual. Regards, Justin"
+  }, {
+    "contentId" : "3266434",
+    "userName" : "user5392072",
+    "rankPoints" : "330",
+    "rankName" : "Intellectual",
+    "date" : "Feb 25, 2020 8:40 AM",
+    "userId" : "5392072",
+    "content" : "Hi,Justin . I am able to use uniflash to flash the 3D_people_count_68xx_demo.bin file of iwr6843isk in the lab, and then run the mmWave_People_Counting_GUISetup.exe program.But when I successfully connected to the serial port and pressed \"send configuration\", nothing happened to 3d plot.Even as I walked around the sensor's detection area, he still had no data changes.I sincerely hope to get your advice and reply. Thank you very much."
+  }, {
+    "contentId" : "3266443",
+    "userName" : "user5392072",
+    "rankPoints" : "330",
+    "rankName" : "Intellectual",
+    "date" : "Feb 25, 2020 8:46 AM",
+    "userId" : "5392072",
+    "content" : "Hi,Justin . I am able to use uniflash to flash the 3D_people_count_68xx_demo.bin file of iwr6843isk in the lab, and then run the mmWave_People_Counting_GUISetup.exe program.But when I successfully connected to the serial port and pressed \"send configuration\", nothing happened to 3d plot.Even as I walked around the sensor's detection area, he still had no data changes.I sincerely hope to get your advice and reply. Thank you very much. thanks !"
+  }, {
+    "contentId" : "3266951",
+    "userName" : "Justin Curewitz",
+    "rankPoints" : "23615",
+    "rankName" : "Mastermind",
+    "date" : "Feb 25, 2020 4:26 PM",
+    "userId" : "5118664",
+    "content" : "Hi, Your device is probably not responding to the configuration file. First, lets confirm that is true without the gui: Connect you device to an application like Tera Term (tera term works well on windows for this) Connect to the UART Com port, set baud rate to 115200 If you reset the device, you should see output similar to this: If you do get output, you can try sending the config to the device using tera term. Set the newline delay to be 100 msec Open another tera term terminal on the DATA Com port - if you see random data coming across, then the device is sending data LED on the device should blink if it is tracking someone. If you get to step 3 and do not see any message in tera term the device is not booting properly. It is usually one of these issues: Power Supply is not compatible (need 5V 3A) - values too high or too low can cause the board to function improperly Device is not set to functional mode (make sure to remove SOP2 and hit the reset button) Device is ES1 - see the user's guide to determine revision Let me know if you need more help. Regards, Justin"
+  }, {
+    "contentId" : "3267720",
+    "userName" : "user5392072",
+    "rankPoints" : "330",
+    "rankName" : "Intellectual",
+    "date" : "Feb 26, 2020 7:16 AM",
+    "userId" : "5392072",
+    "content" : "Hi,Justin . First, I determined that my power supply was 5V 3A and my device was ES2. 1. I used uniflash to put 3d_people_count_68xx_demo.bin file flash into iwr6843isk evm, and removed the sop2 jumper and clicked reset button to enter function mode.Start the Tera Term program to connect to the UART COM port, set the baud rate to 115200, press the reset button of the device, and there is no response in the display window of Tera Term. 2. In order to eliminate the problem of the device itself, I burned down the previous pplcount_lab_xwr68xx.bin file and did the same operation as above, and found that the Tera Term display window responded. thanks!"
+  }, {
+    "contentId" : "3267764",
+    "userName" : "user5392072",
+    "rankPoints" : "330",
+    "rankName" : "Intellectual",
+    "date" : "Feb 26, 2020 8:09 AM",
+    "userId" : "5392072",
+    "content" : "Hi, Justin. I really need your help. How do you configure a device to use tera or other serial port tool terms?Are there any relevant documents and codes for reference? I sincerely hope to get your advice and reply. Thank you very much. thanks."
+  }, {
+    "contentId" : "3268253",
+    "userName" : "Justin Curewitz",
+    "rankPoints" : "23615",
+    "rankName" : "Mastermind",
+    "date" : "Feb 26, 2020 4:06 PM",
+    "userId" : "5118664",
+    "content" : "Hi, Tera term is really just a serial port utility - you can use it to send or receive data - its useful for debugging. You can configure the device with it if you want to, just paste the configuration file into it. Back to your problem - the prebuilt binary should work since the device is ES2 and has the correct power supply. I would recommend using Code Composer Studio to rebuild the binary incase there was some corruption during the install process of the toolbox. Regards, Justin"
+  }, {
+    "contentId" : "3270482",
+    "userName" : "user5392072",
+    "rankPoints" : "330",
+    "rankName" : "Intellectual",
+    "date" : "Feb 28, 2020 9:58 AM",
+    "userId" : "5392072",
+    "content" : "Hi,Justin . I really need your help. I tried to rebuild the.bin file using Code Composer Studio 8.1.0 or reinstall the toolkit, but still could not get the image data correctly. This time I chose the configuration document, but every time I pressed the \"send configuration\" button, the visualizer failed to respond. thanks！"
+  }, {
+    "contentId" : "3270486",
+    "userName" : "user5392072",
+    "rankPoints" : "330",
+    "rankName" : "Intellectual",
+    "date" : "Feb 28, 2020 10:03 AM",
+    "userId" : "5392072",
+    "content" : "Hi,Justin . I really need your help. I want to use IWR6843ISK EVM flash tida-010022 pc_lab_xwr68xx.bin file and run it successfully on the device, hoping to solve the following two problems. 1. Which visualizer should I use to observe the trajectory and point cloud map of the human body? When I used mmwave_people_counting_guisetu.exe, the result was the same as before, even without the GUI. 2. Can use serial port tool to send commands, configure relevant parameters, start sensors and read data. Is there any relevant document for reference? I am currently using: IWR6843ISK (ES2.0) + MMWAVEICBOOST Code Composer Studio 8.1.0 mmwave_industrial_toolbox_4_1_0 mmwave_industrial_toolbox_4_2_0 mmwave_sdk_03_03_00_03 uniflash_5.2.0 mmWave_Demo_Visualizer 3.3.0 MATLAB Runtime 2017a(9.2) I sincerely hope to get your advice and reply. Thank you very much. thanks！"
+  }, {
+    "contentId" : "3270882",
+    "userName" : "Justin Curewitz",
+    "rankPoints" : "23615",
+    "rankName" : "Mastermind",
+    "date" : "Feb 28, 2020 4:40 PM",
+    "userId" : "5118664",
+    "content" : "Hi, I can think of a few potential issues: The com ports you have entered may be flipped. The computer is blocking access to the com ports, so that the gui application cannot use them. This is common with unregistered software, and can usually be fixed by running as admin. The wrong configuration is being sent (I think you already confirmed you were using the correct configuration and setup) To use the TIDA-01022, please download an older version of the toolbox. Version 4.0.0 is best. You can select different version of the toolbox from thecompany Resource Explorer page. Once you have this, run lab \"68xx_people_counting\" - this is the same software used in TIDA-01022. This comes with a Matlab gui - see if this one works for you. Regards, Justin"
+  } ],
+  "tags" : [ "/support/sensors/f/1023/tags/UniFlash", "/support/sensors/f/1023/tags/IWR6843ISK" ],
+  "fourmType" : "TI"
+}

data/json/DLP/883046.json

@@ -0,0 +1,95 @@
+{
+  "ticketNumber" : "883046",
+  "reporterName" : "user5844861",
+  "rankPoints" : "110",
+  "resolutionStatus" : "Resolved",
+  "ticketName" : "UCC28600: TINA example model setup, changing the transformer to a coupled inductor",
+  "rankName" : "Prodigy",
+  "replies" : " 22",
+  "views" : " 109",
+  "queryText" : "Part Number: UCC28600 Hi, I would like to design a multi-ouput flyback converter based on UCC28600 controller IC. I would also like to simulate the circuit, therefore I was trying to change the transformer to a coupled inductor (because later I will need more than one output) in the given TINA example model to see if it is even possible to simulate the same system but with a coupled inductor with the same properties used with the transformer. Unfortunately, if I use a coupled inductor, the simulation result is completely different than before. Is there any way to change the transformer to component with which I would be able to simulate successfully a multi-output flyback topology? Thank you in advance! Bálint",
+  "partNumber" : " UCC28600",
+  "allResponseList" : [ {
+    "contentId" : "3266782",
+    "userName" : "Hong Huang",
+    "rankPoints" : "18085",
+    "rankName" : "Mastermind",
+    "date" : "Feb 25, 2020 2:56 PM",
+    "userId" : "616779",
+    "content" : "I suggest you simulate just with single output. Then you use cross regulation to understand other output. It is mainly a transformer simulation which you need to build your own model. Basically just to find out the leakages and coupling factors"
+  }, {
+    "contentId" : "3295935",
+    "userName" : "user5844861",
+    "rankPoints" : "110",
+    "rankName" : "Prodigy",
+    "date" : "Mar 24, 2020 8:30 PM",
+    "userId" : "5844861",
+    "content" : "Hey, First, I really appreciate your answer, thank you very much! I took your advice and I was trying to simulate the circuit only with one output. Right now, all of the component values have been calculated but the circuit either works in a really weird way, or I get the infamous convergence problem. For example, the weird thing is that voltage top of the current sense resistor has a waveform which is far from ideal, it doesn't have the ramp increase, instead the voltage changes instantly. If the current source is around 4 A, than the duty cycle of the OUT pin looks strange as well. It has a kind of a normal cycle, after that some really thin pulses and it keeps repeating. I attached the current version. Do you have an idea why is it working like this? Edit.: I left the given transformer model in the simulation, I just changed its values based on my calculations. mine.TSC"
+  }, {
+    "contentId" : "3295958",
+    "userName" : "Hong Huang",
+    "rankPoints" : "18085",
+    "rankName" : "Mastermind",
+    "date" : "Mar 24, 2020 8:50 PM",
+    "userId" : "616779",
+    "content" : "It looks some setup not good. Can you start with the TINA design (attached here, \"slum608.TSC\") fromcompany web and change one thing at a time to see which change causing the convergence problem? I just ran \"slum608.TSC\" and it worked ok. slum608.TSC"
+  }, {
+    "contentId" : "3315616",
+    "userName" : "user5844861",
+    "rankPoints" : "110",
+    "rankName" : "Prodigy",
+    "date" : "Apr 14, 2020 4:44 PM",
+    "userId" : "5844861",
+    "content" : "Hi, Since then I did what you suggested, and the main reason why the circuit was not working is the incorrect secondary diode I've chosen. My problem now is the following: The attached simulation works as expected until 1.4A of load. The problem is, if I go higher than this value, the controller is unable to hold the output voltage on the desired 12V, even though all the values (OVP, current sense etc) have been calculated for 197W output power with 85% efficiency, therefore if the output current would be around 16A, it still should be able to work. Now I'm a bit stucked. I think the chosen OVP resistor values and current sense protection (Rcs and Rpl) have been calculated correctly, I don't really see why the controller stops the operation. Unfortunately, I don't know TINA that well, but my first thought was maybe the diode on the output causes some problems, as the current one is able to handle 1A maximum forward current, but changing that value doesn't help. Maybe somehow the state machine starts to work incorrectly? May I ask your help in this regard? Thank you in advance!step_by_step.tsc"
+  }, {
+    "contentId" : "3315779",
+    "userName" : "Hong Huang",
+    "rankPoints" : "18085",
+    "rankName" : "Mastermind",
+    "date" : "Apr 14, 2020 7:12 PM",
+    "userId" : "616779",
+    "content" : "Can you probe each node to see if any hint? Also, when 12V is not held, does it drop or shutdown? If it drops, which means some setup is likely saturated. If shutdown, it means some fault triggered. You need to check one at time."
+  }, {
+    "contentId" : "3316413",
+    "userName" : "user5844861",
+    "rankPoints" : "110",
+    "rankName" : "Prodigy",
+    "date" : "Apr 15, 2020 8:45 AM",
+    "userId" : "5844861",
+    "content" : "12V slowly drops, it is quite clear that the controller doesn't put energy from the primary side, so the capacitor on the secondary side just loses its charges and the voltage drops in the same ratio. This is how it looks the drop after the load reaches the problematic level. And there are weird spikes in the current signal after the 2ms mark if I zoom in. This happens at 2A of load. This thing goes even more weird, if I change the load to 16A. In that case the controller keeps the primary side transistor open, and although the voltage on the output drops, the waveforms look really strange after the load goes on."
+  }, {
+    "contentId" : "3317031",
+    "userName" : "Hong Huang",
+    "rankPoints" : "18085",
+    "rankName" : "Mastermind",
+    "date" : "Apr 15, 2020 5:14 PM",
+    "userId" : "616779",
+    "content" : "Can you compare your simulation circuit and the original? My review of your circuit looks you removed the feedback loop compensation components on TL431 so your circuit cannot make correct loop compensation."
+  }, {
+    "contentId" : "3320318",
+    "userName" : "user5844861",
+    "rankPoints" : "110",
+    "rankName" : "Prodigy",
+    "date" : "Apr 18, 2020 4:03 PM",
+    "userId" : "5844861",
+    "content" : "I added the loop compensation as you suggested by following the steps in the \"Compensation Design With TL431 for UCC28600\" (SLUA671) document. The circuit unfortunately still doesn't work as expected. I can go a bit higher with the current up to around 4A (you can see a picture about a simulation with 1.6A load below), but it is still far from the final 16A. A was also trying to add the Zener network later before Rled, but it didn't help either. Based on the transfer characteristics, the compensation network should do the work, I changed the crossover frequency to 3kHz of Vo/Vcomp, it also meets with all the stability conditions. The other really weird thing for me (although maybe I just misunderstood something) is the switching frequency. Shouldn't it work with at least 40kHz bursts? Right now, depending on the load, the switching frequency varies between ~3kHz - 7kHz. And the pictures: Unfortunately it is quite hard to figure out if it reaches 12V or not, because the simulation stops with convergence problem a lot of times. Sometimes pressing 'retry' works, but I don't know how accurate the result going to be after this error. Also if I don't change anything in the example simulation, but I change the simulation time to 30ms, it doesn't run. It quits with convergence error. So back to my circuit: It reaches the target output voltage @1.6A, but during the simulation I had to press 'retry' on the convergence error once. At 3.5A at the start it looks like the system operates in CCM, but the controller is a DCM one, so it shouldn't happen right? The Bode of Vo/Vcomp I also attached the updated simulation circuit. 5824.step_by_step.tsc"
+  }, {
+    "contentId" : "3320346",
+    "userName" : "Hong Huang",
+    "rankPoints" : "18085",
+    "rankName" : "Mastermind",
+    "date" : "Apr 18, 2020 6:18 PM",
+    "userId" : "616779",
+    "content" : "How did you decide the loop compensation? How did you design your converter parameter values?"
+  }, {
+    "contentId" : "3320453",
+    "userName" : "user5844861",
+    "rankPoints" : "110",
+    "rankName" : "Prodigy",
+    "date" : "Apr 19, 2020 11:16 AM",
+    "userId" : "5844861",
+    "content" : "For the loop compensation as I said I followed the method presented in SLUA671. The following MATLAB code shows my implementation s = tf('s'); Rd = 8; ESR = 50e-3; Rcs = 151e-3; Vtl431min = 2.5; Vdd = 5; Vcesat = 0.3; Vf = 0.7; Ibias = 1e-3; CTRmin = 0.4; Rpullup = 20e3; Rledmax = (Vout-Vf-Vtl431min)/(Vdd-Vcesat+Ibias*CTRmin*Rpullup)*CTRmin*Rpullup; R1 = 10e3; Vsample = 2.5; Rlower = R1*Vsample/(Vout-Vsample); Vin = 325; Voutmax = 13; Nps = 15.27; D = Nps*Voutmax/(Vin+Nps*Voutmax); H = Nps*D/(5*Rcs)*Rd*(ESR+1/(s*Co))/(Rd+ESR+1/(s*Co)); %transfer function of Vo/Vcomp bode(H); Gmid = 10^(12.65/20); %to have 3kHz as cross-over frequency Rled = 499; R2 = Gmid*R1*Rled/(Rpullup*CTRmin); [z,p,k] = zpkdata(H); p = cell2mat(p); fz = abs(p(2,1)); fp1 = 40e3; %suggested pole fp2 = fp1; C2 = 1/(2*pi*R2*fz); C1 = 1/(2*pi*R2*fp1); C3 = 1/(2*pi*Rpullup*fp2); Copto = 2e-9; F = (s*R2*C2+1)/(s*R1*C2*(s*R2*C1+1))*(1/(1+s*Rpullup*(C3*Copto/(C3+Copto))))*Rpullup/Rled*CTRmin; %transfer function of compensation network bode(F); bode(H*F); Are you curious about all the converter parameters (transformer parameters etc), or only the ones which needed for the controller (OVP, current sense, Css etc)?"
+  } ],
+  "tags" : [ "/support/power-management/f/196/tags/TINA%2bucc28600", "/support/power-management/f/196/tags/UCC28600" ],
+  "fourmType" : "TI"
+}

data/json/DLP/885747.json

@@ -0,0 +1,87 @@
+{
+  "ticketNumber" : "885747",
+  "reporterName" : "y gu",
+  "rankPoints" : "190",
+  "resolutionStatus" : "TI Thinks Resolved",
+  "ticketName" : "The question of function(clusteringDBscan_findNeighbors2Fixed) parameters",
+  "rankName" : "Prodigy",
+  "replies" : " 9",
+  "views" : " 92",
+  "queryText" : "Hello,TI's engineers.I use ti's IWR1642BOOST and want to develop SRR radar, so i read the demo of short_range_radar(SRR).When i read the clusteringDBscanRun, and see the function of clusteringDBscan_findNeighbors2Fixed(this function is first time appear in clusteringDBscan.c file, line 124),one parameter is confused me. neighCount = clusteringDBscan_findNeighbors2Fixed( detObj2D, point, neighLast, numPoints, epsilon2fixed, epsilonfixed, weight, vFactorfixed,inst->scope, &newCount, inst->dBScanNeighbourLim); The third parameter of neighLast whether the correct?I think this parameter should be neighCurrent.I don't know whether my understanding is wrong, so askcompany engineers can you help me to answer? Can you give me some clusteringDBscan data to better learn. Thanks a lot!!!",
+  "partNumber" : "NA",
+  "allResponseList" : [ {
+    "contentId" : "3275972",
+    "userName" : "Cesar",
+    "rankPoints" : "52960",
+    "rankName" : "Guru",
+    "date" : "Mar 4, 2020 8:24 PM",
+    "userId" : "20288",
+    "content" : "Hi, For this question we need to check with algorithm developer. We should be able to get a response by early next week thank you Cesar"
+  }, {
+    "contentId" : "3288950",
+    "userName" : "zigang Yang",
+    "rankPoints" : "7975",
+    "rankName" : "Expert",
+    "date" : "Mar 17, 2020 6:41 PM",
+    "userId" : "44611",
+    "content" : "HI, neighCurrent is a pointer pointing to the beginning of the neighbor list for the current scan. And neightLast is a pointer pointing to the end of neighbor list for the current scan. So, neighCurrent is not moving and neightLast is kept moving. And the delta is used to calculate the length of the neighbors founded for the current scan. Hope it helps, Zigang"
+  }, {
+    "contentId" : "3304992",
+    "userName" : "y gu",
+    "rankPoints" : "190",
+    "rankName" : "Prodigy",
+    "date" : "Apr 2, 2020 2:54 PM",
+    "userId" : "4085724",
+    "content" : "Hi，ti’ engineer！the function of clusteringDBscan_findNeighbors2Fixed is appear twice，first is find original point’s neighbor, the second is find neighbor’ s neighbor.When we find the neighbor’s neighbor, According to code comments we should compared neighbor’s neighbor’s speed with original point’s speed.If less than vfactor, so we think they are the same class.However, in srr code,your code still use original point’s speed compared with its neighbor’s speed,this compared is finished in the first function of clusteringDBscan_findNeighbors2Fixed, According to your code, the neighbors' neighbors will must be in the same class，This should not be the intent of your code itself.Can you check the function of clusteringDBscanRun，I think there is a logical problem with this function？"
+  }, {
+    "contentId" : "3324129",
+    "userName" : "Cesar",
+    "rankPoints" : "52960",
+    "rankName" : "Guru",
+    "date" : "Apr 22, 2020 11:31 AM",
+    "userId" : "20288",
+    "content" : "Hi, I have talked with algorithm developer. We have reviewed the code but we did not see any bug. Could you please provide more information with the code lines you are analyzing? Please provide the code lines you have question about. This will help us understand if there is a bug thank you Cesar"
+  }, {
+    "contentId" : "3326592",
+    "userName" : "y gu",
+    "rankPoints" : "190",
+    "rankName" : "Prodigy",
+    "date" : "Apr 24, 2020 3:56 AM",
+    "userId" : "4085724",
+    "content" : "Hello,Cesar! I think my previous question was not clearly stated.and i think the function of clusteringDBscanRun has some problem not clusteringDBscan_findNeighbors2Fixed .In clusteringDBscanRun.c file and the 167~175 lines,you find the original obj's neibor,then you should find original obj's neibor's neibor.if find it,we should take the original obj's neibor's neibor's speed compare with the original obj's speed,but the demo code still use the obj's neibor's speed compare with the original obj's speed.So the neighbors' neighbors and original obj's will must be in the same class.Please check it again. the code is in clusteringDBscanRun.c file and the 167~175 lines: if(neighCount >= inst->minPointsInCluster) { int32_t speed = (int32_t) detObj2D[point].speed; /* Check if the new point's velocity is the same velocity as the * clusterOriginator. */ if (_abs(detObj2D[member].speed - speed) < vFactorfixed) { for (ind = 0; ind < newCount; ind ++) { member = neighLast[ind]; inst->scope[member] = POINT_VISITED; } neighLast += newCount; /* Member is a core point, and its neighborhood is added to the cluster */ } } Thanks a lot!"
+  }, {
+    "contentId" : "3327282",
+    "userName" : "zigang Yang",
+    "rankPoints" : "7975",
+    "rankName" : "Expert",
+    "date" : "Apr 24, 2020 4:13 PM",
+    "userId" : "44611",
+    "content" : "HI, Within the while loop, we will find all the neighbor's neighbor, neighbor's neighbor's neighbor and etc. Every time, when the function clusteringDBscan_findNeighbors2Fixed is called inside the \"while Loop\", the neighLast will grow longer and the new neighbor's neighbor will become member to be checked. Therefore, the if condition you mentioned below if (_abs(detObj2D[member].speed - speed) < vFactorfixed) will check all the neighbor, neighbor's neighbor and neighbor's neighbor's neighbor with the clusterOriginator. Best, Zigang"
+  }, {
+    "contentId" : "3327798",
+    "userName" : "y gu",
+    "rankPoints" : "190",
+    "rankName" : "Prodigy",
+    "date" : "Apr 25, 2020 7:22 AM",
+    "userId" : "4085724",
+    "content" : "hi,Zigang! The demo code's purpose is compare neighbor's neighbor's speed with the clusterOriginator's speed,and if in the vFactorfixed then think it is in the same clusterId.And your code comment is also point that:\"/* Check if the new point's velocity is the same velocity as the clusterOriginator. */\" However, in code the member is still the clusterOriginator's neighbor's index, i think it should be clusterOriginator's neighbor's neighbor's index.So the clusterOriginator's neighbor's neighbor must be in the same clusterId,even thought Within the while loop we will find all the neighbor's neighbor, neighbor's neighbor's neighbor and etc as you said.Please check it again.Thanks!"
+  }, {
+    "contentId" : "3328909",
+    "userName" : "zigang Yang",
+    "rankPoints" : "7975",
+    "rankName" : "Expert",
+    "date" : "Apr 27, 2020 2:34 PM",
+    "userId" : "44611",
+    "content" : "HI, In this following if condition: if (_abs(detObj2D[member].speed - speed) < vFactorfixed) speed is the speed of the clusterOriginator. detObj2D[member].speed is the speed of new points, including: the neighbor, neighbor's neighbor and neighbor's neighbor's neighbor and etc. Therefore, we are checking the new points's velocity with the velocity of the clusterOrginator. Please let me know where did I misunderstand. Best, Zigang"
+  }, {
+    "contentId" : "3330089",
+    "userName" : "y gu",
+    "rankPoints" : "190",
+    "rankName" : "Prodigy",
+    "date" : "Apr 28, 2020 8:33 AM",
+    "userId" : "4085724",
+    "content" : "Hello,zigang Yang! In function of clusteringDBscanRun,you call the function of clusteringDBscan_findNeighbors2Fixed twice.First time you want to find the clusterOrginator's neibor,and the second time you want to find clusterOrginator's neibor's neibor and clusterOrginator's neighbor's neighbor's neighbor and etc.And you will put the neibor in the inst->neighbors in turn.We look the code behind: while (neighCurrent != neighLast) // neigh shall be at least minPoints in front of neighborhood pointer { // Explore the neighborhood member = *neighCurrent++; // Take point from the neighborhood output->IndexArray[member] = clusterId; // All points from the neighborhood also belong to this cluster inst->visited[member] = POINT_VISITED; neighCount = clusteringDBscan_findNeighbors2Fixed( detObj2D, member, neighLast, numPoints, epsilon2fixed, epsilonfixed, weight, vFactorfixed, inst->scope, &newCount, inst->dBScanNeighbourLim); if(neighCount >= inst->minPointsInCluster) { int32_t speed = (int32_t) detObj2D[point].speed; /* Check if the new point's velocity is the same velocity as the * clusterOriginator. */ if (_abs(detObj2D[member].speed - speed) < vFactorfixed) { for (ind = 0; ind < newCount; ind ++) { member = neighLast[ind]; inst->scope[member] = POINT_VISITED; } neighLast += newCount; /* Member is a core point, and its neighborhood is added to the cluster */ } } } The member is clusterOrginator's neibor,and then you take it compare with the clusterOriginator's speed,this is compared in the first call the function of clusteringDBscan_findNeighbors2Fixed,so the condition: if (_abs(detObj2D[member].speed - speed) < vFactorfixed) will must established, and then you take the new points(clusterOrginator's neibor's neibor) add in the inst->neighbors. I think the member in if condition(if (_abs(detObj2D[member].speed - speed) < vFactorfixed)) should be the clusterOrginator's neibor's neibor, not the clusterOrginator's neibor. Please check it again. Thanks a lot!"
+  } ],
+  "tags" : [ "/support/sensors/f/1023/tags/IWR1642BOOST", "/support/sensors/f/1023/tags/_2300_%2b%2b%2b%2bIWR1642BOOS", "/support/sensors/f/1023/tags/awr20_5F00_a_5F00_swa20_5F00_tirex", "/support/sensors/f/1023/tags/_2300_%2b%2b%2b%2b%2bBUG" ],
+  "fourmType" : "TI"
+}

data/json/DLP/886080.json

@@ -0,0 +1,87 @@
+{
+  "ticketNumber" : "886080",
+  "reporterName" : "Maxim Fiodorov",
+  "rankPoints" : "70",
+  "resolutionStatus" : "TI Thinks Resolved",
+  "ticketName" : "BQ40Z80: 7th cell calibration problem.",
+  "rankName" : "Prodigy",
+  "replies" : " 9",
+  "views" : " 91",
+  "queryText" : "Part Number: BQ40Z80 Hi everyone. I have a problem with cell calibration by battery management studio 1.3.86. I set each of 7 cells to 4V on resistors voltage divider. I eter the values for calibration (see attached picture). But I always get 7th cell near 3940mV ad not near 4000mV. All other cells are near 4000mV. Only if I manually adjust VC7 Sense Gain I achieve desired 4000mV at 7th cell. Does anyone had the same problem with calibration by battery management studio 1.3.86.??? Is there any solution to this? I attache 2 gg files with manual and battery studio calibration. bq studio calibration.gg.csv manual calibration.gg.csv",
+  "partNumber" : " BQ40Z80",
+  "allResponseList" : [ {
+    "contentId" : "3277767",
+    "userName" : "Kang Kang",
+    "rankPoints" : "17055",
+    "rankName" : "Genius",
+    "date" : "Mar 6, 2020 3:07 AM",
+    "userId" : "3528441",
+    "content" : "Hello Maxim I'm assigning this to device expert. Expecta response within 2 days."
+  }, {
+    "contentId" : "3279217",
+    "userName" : "Maxim Fiodorov",
+    "rankPoints" : "70",
+    "rankName" : "Prodigy",
+    "date" : "Mar 8, 2020 6:53 AM",
+    "userId" : "4479536",
+    "content" : "I forgot to mention when I adjust manually VC7 Sense Gain the BAT pin voltage get adjusted correspondingly but it still inside 1% battery voltage error range. I get the same phenomenon on my design and on evaluation board."
+  }, {
+    "contentId" : "3283550",
+    "userName" : "Andy Liu (BMS)",
+    "rankPoints" : "42410",
+    "rankName" : "Mastermind",
+    "date" : "Mar 11, 2020 10:18 PM",
+    "userId" : "1864278",
+    "content" : "The Cell 7 voltage is handled differently from the voltage of other cells. Let me try my EVM and see if there is a way to help you."
+  }, {
+    "contentId" : "3287665",
+    "userName" : "Kang Kang",
+    "rankPoints" : "17055",
+    "rankName" : "Genius",
+    "date" : "Mar 16, 2020 8:53 PM",
+    "userId" : "3528441",
+    "content" : "Please try on the test version (1.3.100), I believe this issue should be resolved. Thanks!"
+  }, {
+    "contentId" : "3293422",
+    "userName" : "Maxim Fiodorov",
+    "rankPoints" : "70",
+    "rankName" : "Prodigy",
+    "date" : "Mar 22, 2020 1:52 PM",
+    "userId" : "4479536",
+    "content" : "I have tried 1.3.100 version of bq Studio. The problem still exist."
+  }, {
+    "contentId" : "3302415",
+    "userName" : "Andy Liu (BMS)",
+    "rankPoints" : "42410",
+    "rankName" : "Mastermind",
+    "date" : "Mar 31, 2020 5:42 PM",
+    "userId" : "1864278",
+    "content" : "Hi Maxim, I guess what you try is to follow the steps in Section 2.2 of the following app note and see if you can have better calibration results. <secret URL>/lit/an/slua868/slua868.pdf Andy"
+  }, {
+    "contentId" : "3313090",
+    "userName" : "Maxim Fiodorov",
+    "rankPoints" : "70",
+    "rankName" : "Prodigy",
+    "date" : "Apr 12, 2020 12:51 PM",
+    "userId" : "4479536",
+    "content" : "slua868.pdf describe how to calculate the calibration coefficients. I am doing it myself to correct wrong calibration by Battery Management Studio program. My problem is the wrong calibration by Battery Management Studio."
+  }, {
+    "contentId" : "3322042",
+    "userName" : "Andy Liu (BMS)",
+    "rankPoints" : "42410",
+    "rankName" : "Mastermind",
+    "date" : "Apr 20, 2020 10:28 PM",
+    "userId" : "1864278",
+    "content" : "I will report this issue to my software team so that they can double-check if it is necessary to update their existing code. Andy"
+  }, {
+    "contentId" : "3323099",
+    "userName" : "Shirish",
+    "rankPoints" : "2420",
+    "rankName" : "Intellectual",
+    "date" : "Apr 21, 2020 3:50 PM",
+    "userId" : "28063",
+    "content" : "Do you get the same result in bqStudio if you uncheck \"Calibrate Pack Voltage\"?"
+  } ],
+  "tags" : [ "/support/power-management/f/196/tags/bq40z80" ],
+  "fourmType" : "TI"
+}

data/json/DLP/886270.json

@@ -0,0 +1,95 @@
+{
+  "ticketNumber" : "886270",
+  "reporterName" : "Iurii Hlotov",
+  "rankPoints" : "190",
+  "resolutionStatus" : "TI Thinks Resolved",
+  "ticketName" : "BQ35100: BQ35100",
+  "rankName" : "Prodigy",
+  "replies" : " 31",
+  "views" : " 176",
+  "queryText" : "Part Number: BQ35100 Hi, There is a customed board with BQ35100 and MCU. I setup BQ35100 in EOS mode (reg. 0x41b1), and modified R Data Seconds (reg. 0x4255) setup 1 second. To get data (voltage, current, temperature) the following sequence is used: 1. Enable BQ; 2. Start BQ (send start command); 3. Read data(voltage or current or temperature); 4. Stop BQ (send stop command); 5. wait for timeout specified in R Data Seconds (expected 1 s) wait until G_DONE bit is set; 6. Disable BQ; The problem is that actually it takes about 4 min (instead of expected 1 s) to wait G_DONE is set. Do I need to send some other command to activate the setting? thanks",
+  "partNumber" : " BQ35100",
+  "allResponseList" : [ {
+    "contentId" : "3277783",
+    "userName" : "Kang Kang",
+    "rankPoints" : "17055",
+    "rankName" : "Genius",
+    "date" : "Mar 6, 2020 3:20 AM",
+    "userId" : "3528441",
+    "content" : "I've pinged the device expert, please expect a response within two business days."
+  }, {
+    "contentId" : "3277834",
+    "userName" : "Eric Vos24",
+    "rankPoints" : "3585",
+    "rankName" : "Expert",
+    "date" : "Mar 6, 2020 4:15 AM",
+    "userId" : "3440231",
+    "content" : "Lurii, I have not seen this and programmed a value of 1 myself to test. Are you sure the gauge is receiving the [Gauge Stop] command? The [GA] bit should clear if so. I also don't recommend a value of 1 second. the gauge needs time to fill in the voltage sampling buffer to accurately calculate the measuredZ. Thanks, Eric Vos"
+  }, {
+    "contentId" : "3277982",
+    "userName" : "Iurii Hlotov",
+    "rankPoints" : "190",
+    "rankName" : "Prodigy",
+    "date" : "Mar 6, 2020 8:10 AM",
+    "userId" : "6278035",
+    "content" : "Thanks for reply. Regarding \"the gauge is receiving Stop command\" i'm not sure, i need to verify this with logic analyzer. 1. As far as, I get it the GA bit should be cleared after Stop command is received properly (correct me if I'm wrong). So, should I check GA bit instead of G_DONE in the Control_Status? What is the purpose of G_DONE bit? 2. What is the minimum value of R data seconds reg. to get accurate value of voltage, current and temperature? This is quite weird behavior, because at the first i used the default value of R Data Seconds (15 sec) and the following sequence: - enable BQ; - start BQ (send command and wait until bit GA is set); - stop BQ (send command and wait until bit G_DONE is set); - read data form BQ; - disable BQ; In this case it takes around 15 sec. to read data from BQ (as expected according to datasheet). Then I tried to reduce R Data Seconds to less value (1 sec, 5 sec, 10 sec), but instead of reducing response time it takes unexpected ~4 min to read data (to wait until G_DONE is set). Perhaps the right sequence should be the following: - enable BQ; - start BQ (send command and wait until bit GA is set); - stop BQ (send command and wait until bit GA is clear); - read data (); - disable BQ; Please, provide me a feedback. Thanks."
+  }, {
+    "contentId" : "3278409",
+    "userName" : "Eric Vos24",
+    "rankPoints" : "3585",
+    "rankName" : "Expert",
+    "date" : "Mar 6, 2020 3:16 PM",
+    "userId" : "3440231",
+    "content" : "1) yes sending Gauge_Stop should set GA =0 if it was received properly by the gauge. 2) The minimum we recommend is 15Sec which is why it is our default. If it needs to be lower testing should be done on your side to make sure results are consistent. Both procedures should work, but since measuredZ and SOH are updated after GDone. I would follow - enable BQ; - start BQ (send command and wait until bit GA is set); - stop BQ (send command and verify bit GA is clear); -Wait until GDONE = 1 - read data (); - disable BQ;"
+  }, {
+    "contentId" : "3278864",
+    "userName" : "Iurii Hlotov",
+    "rankPoints" : "190",
+    "rankName" : "Prodigy",
+    "date" : "Mar 6, 2020 9:26 PM",
+    "userId" : "6278035",
+    "content" : "hi, followed the recommendation of Eric Vos24 and figured out that after sending STOP command the [GA] bit is still set and furthermore waiting for bit [G_DONE] to be set never happens (it is 0 for a very long time). It seems that there is a problem with STOP command. I tried to set R Data Seconds reg. to different values (1 sec, 5 sec, 15 sec), but the result is the same (wait bit [G_DONE] set for a very long time). What might be the problem with STOP command (other command seems to work properly)?"
+  }, {
+    "contentId" : "3280588",
+    "userName" : "Kang Kang",
+    "rankPoints" : "17055",
+    "rankName" : "Genius",
+    "date" : "Mar 9, 2020 9:44 PM",
+    "userId" : "3528441",
+    "content" : "Hello Iurii, Can you wait for a while longer prior to sending STOP? Say 2 more seconds?"
+  }, {
+    "contentId" : "3281096",
+    "userName" : "Iurii Hlotov",
+    "rankPoints" : "190",
+    "rankName" : "Prodigy",
+    "date" : "Mar 10, 2020 9:45 AM",
+    "userId" : "6278035",
+    "content" : "Hi, yes I tried this, but result is the same (bit GA is still set after STOP command has been sent). After START has been sent MCU waits for [GA] bit is set (first line on the Logic analyzer log: 0x81) then MCU wait for 2000 ms and sends STOP command (0x12 line 5), then MCU check [GA] bit, but it is still 1 (last but one line 0x81)"
+  }, {
+    "contentId" : "3281098",
+    "userName" : "Iurii Hlotov",
+    "rankPoints" : "190",
+    "rankName" : "Prodigy",
+    "date" : "Mar 10, 2020 9:45 AM",
+    "userId" : "6278035",
+    "content" : "Hi, yes I tried this, but result is the same (bit GA is still set after STOP command has been sent). After START has been sent MCU waits for [GA] bit is set (first line on the Logic analyzer log: 0x81) then MCU wait for 2000 ms and sends STOP command (0x12 line 5), then MCU check [GA] bit, but it is still 1 (last but one line 0x81)"
+  }, {
+    "contentId" : "3281101",
+    "userName" : "Iurii Hlotov",
+    "rankPoints" : "190",
+    "rankName" : "Prodigy",
+    "date" : "Mar 10, 2020 9:49 AM",
+    "userId" : "6278035",
+    "content" : "Hi, yes I tried this, but result is the same (bit GA is still set after STOP command has been sent). After START has been sent MCU waits for [GA] bit is set (first line on the Logic analyzer log: 0x81) then MCU wait for 2000 ms and sends STOP command (0x12 line 5), then MCU check [GA] bit, but it is still 1 (last but one line 0x81)"
+  }, {
+    "contentId" : "3282079",
+    "userName" : "Kang Kang",
+    "rankPoints" : "17055",
+    "rankName" : "Genius",
+    "date" : "Mar 11, 2020 1:06 AM",
+    "userId" : "3528441",
+    "content" : "It most likely might be that your voltage is not stable yet. Can you provide us a bqStudio log file?"
+  } ],
+  "tags" : [ "/support/power-management/f/196/tags/BQ35100", "/support/power-management/f/196/tags/BQ35100%2bEOS%2bmode%2bR%2bData%2bSeconds" ],
+  "fourmType" : "TI"
+}

data/json/DLP/886577.json

@@ -0,0 +1,95 @@
+{
+  "ticketNumber" : "886577",
+  "reporterName" : "Jiju Chacko24",
+  "rankPoints" : "170",
+  "resolutionStatus" : "Resolved",
+  "ticketName" : "BQ27Z561: BQ27z561 - Battery SOC suddenly jumps from 100 to 0 in few seconds",
+  "rankName" : "Prodigy",
+  "replies" : " 12",
+  "views" : " 107",
+  "queryText" : "Part Number: BQ27Z561 Hi, We are using BQ27z561 for battery management in our product. Recently we have seen instances where in the battery SOC suddenly jumps from 100 to 50 and sometimes from 100 to 0 within 1 seconds. After this, this the fuel gauge reports LOW battery warning. When the device is kept for charging, the SOC suddenly jumps to 100% within 10 minutes. Regards, JIju Chacko",
+  "partNumber" : " BQ27Z561",
+  "allResponseList" : [ {
+    "contentId" : "3278920",
+    "userName" : "Andy Liu (BMS)",
+    "rankPoints" : "42410",
+    "rankName" : "Mastermind",
+    "date" : "Mar 6, 2020 11:13 PM",
+    "userId" : "1864278",
+    "content" : "Hi JIju, Did you guys choose a proper chemistry id to match your battery? Did you successfully run the learning cycle? Andy"
+  }, {
+    "contentId" : "3281017",
+    "userName" : "Jiju Chacko24",
+    "rankPoints" : "170",
+    "rankName" : "Prodigy",
+    "date" : "Mar 10, 2020 8:28 AM",
+    "userId" : "3923954",
+    "content" : "Hi Andy, Yes. the configuration are proper and the device works as expected in our testing environment. The issue reported is from the field testing. With the help of few field engineers we got the know the root cause of the issue. The battery is getting disconnected temporarily and this reboots the device. On the next boot the SOC reading get jumbled up. Currently we have BQFS, GMFS and SREC files generated from the Battery Management Studio application. Do we need to write these files again? What will be the process to calibrate the fuel gauge when connecting and new battery?"
+  }, {
+    "contentId" : "3281867",
+    "userName" : "Andy Liu (BMS)",
+    "rankPoints" : "42410",
+    "rankName" : "Mastermind",
+    "date" : "Mar 10, 2020 7:55 PM",
+    "userId" : "1864278",
+    "content" : "The files can be used for mass production. Basically, you program one of these files to a fresh device. Regarding the calibration process, please see the Calibration section of bq27z561 TRM."
+  }, {
+    "contentId" : "3282266",
+    "userName" : "Jiju Chacko24",
+    "rankPoints" : "170",
+    "rankName" : "Prodigy",
+    "date" : "Mar 11, 2020 5:23 AM",
+    "userId" : "3923954",
+    "content" : "Hi Andy, I think there is a confusion in understanding the issue. We have followed the steps of calibration from the TRM as you stated. And the device with the battery connected works perfectly as per requirement. In our design, the battery gauge is directly powered from battery. In this case, if the battery is removed for some reason. then on connecting the battery again we see a difference in the battery SOC. I understand there will be some difference as the battery gets relaxed in removal of load. But still the difference of ~70% capacity is not expected. My question is, in case of new battery connection or intermediate battery removal and insertion, do we need to perform any steps in the fuel gauge ?"
+  }, {
+    "contentId" : "3283528",
+    "userName" : "Andy Liu (BMS)",
+    "rankPoints" : "42410",
+    "rankName" : "Mastermind",
+    "date" : "Mar 11, 2020 9:52 PM",
+    "userId" : "1864278",
+    "content" : "Try sending a RESET command to the gauge device. The SoC should be updated again. Andy"
+  }, {
+    "contentId" : "3283823",
+    "userName" : "Jiju Chacko24",
+    "rankPoints" : "170",
+    "rankName" : "Prodigy",
+    "date" : "Mar 12, 2020 6:19 AM",
+    "userId" : "3923954",
+    "content" : "Hi Andy, We are using below commands from the driver. We added a custom SYSFS entry which will reset the device after power cycle or during battery replacement. case POWER_SUPPLY_PROP_ENABLE_IT: { if(val->intval){ fg_enable_gauge_it(bq); fg_reset(bq); } break; } Just want to confirm if these are the only required steps and we don't need to perform any other operation. Regards, Jiju Chacko"
+  }, {
+    "contentId" : "3284853",
+    "userName" : "Andy Liu (BMS)",
+    "rankPoints" : "42410",
+    "rankName" : "Mastermind",
+    "date" : "Mar 12, 2020 10:52 PM",
+    "userId" : "1864278",
+    "content" : "Unfortunately, there is no way for me to verify your code. Here is my suggestion. Basically, make sure that the gauge device is NOT in the SEALED mode before sending the RESET command."
+  }, {
+    "contentId" : "3291439",
+    "userName" : "Jiju Chacko24",
+    "rankPoints" : "170",
+    "rankName" : "Prodigy",
+    "date" : "Mar 19, 2020 2:28 PM",
+    "userId" : "3923954",
+    "content" : "Hi Andy, As you can see below. Even in cases where the battery is not removed, we see difference in the battery SOC reported by the fuel gauge. As per our conversation earlier, we added command to set GAUGE_EN=1 and then send a reset command. [ 20.760000] [bq27z561] fg_irq_thread: RSOC:7, Volt:3704, Current:0, Temperature:371 [ 20.770000] [bq27z561] fg_irq_thread: VOLT_HI clear [ 20.780000] [bq27z561] fg_irq_thread: TEMP_HI set [ 20.780000] [bq27z561] fg_irq_thread: VOLT_LOW clear [ 20.790000] [bq27z561] fg_irq_thread: TEMP_LOW clear [ 20.790000] [bq27z561] fg_interrupt_event_provider: status = 4, bq->cache_hi_temp = 0x0, bq->high_temp_threshold_status = 0x0 [ 20.800000] [bq27z561] fg_interrupt_event_provider: Low temperature interrupt received via high temperature threshold set [ 20.820000] [bq27z561] fg_interrupt_event_provider: Low temp condition is cleared, setting current to 960mA [ 20.830000] bq25601_set_charge_current called via fuel gauge= 0x10 [ 22.530000] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 28.620000] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready [ 32.030000] IPv6: ADDRCONF(NETDEV_UP): usb0: link is not ready [ 34.160000] [bq27z561] fg_unseal_complete_access: FG is unsealed [ 34.160000] [bq27z561] fg_enable_gauge_it: Data flash unsealed [ 34.470000] power_supply bms: driver failed to report `voltage_now' property: -1 [ 34.510000] power_supply bms: driver failed to report `voltage_now' property: -1 [ 36.960000] Battery charging disabled [ 36.990000] Battery charging enabled [ 43.740000] [bq27z561] fg_irq_thread: RSOC:14, Volt:3869, Current:960, Temperature:359 [ 43.740000] [bq27z561] fg_irq_thread: VOLT_HI clear [ 43.750000] [bq27z561] fg_irq_thread: TEMP_HI clear [ 43.750000] [bq27z561] fg_irq_thread: VOLT_LOW clear [ 43.760000] [bq27z561] fg_irq_thread: TEMP_LOW clear Regards, Jiju Chacko"
+  }, {
+    "contentId" : "3294620",
+    "userName" : "Andy Liu (BMS)",
+    "rankPoints" : "42410",
+    "rankName" : "Mastermind",
+    "date" : "Mar 23, 2020 8:21 PM",
+    "userId" : "1864278",
+    "content" : "Hi Jiju, If the battery hasn't been removed, I will suggest you NOT send the RESET command to the gauge device. Here is my suggestion. After the battery is connected to the gauge and your system, don't power on your system. Instead, let the battery relax for two hours and then power on. I believe you will read back accurate RSOC readings. The purpose of the 2-hour relaxation time is to let the gauge take an OCV measurement and update the FCC, RemCap, and RSOC. Andy"
+  }, {
+    "contentId" : "3297820",
+    "userName" : "Jiju Chacko24",
+    "rankPoints" : "170",
+    "rankName" : "Prodigy",
+    "date" : "Mar 26, 2020 11:02 AM",
+    "userId" : "3923954",
+    "content" : "Hi Andy, 2 hours is too long. I was expecting this time to be in seconds. Can you tell me if there is procedure to forcefully calculate battery OCV. Regards, Jiju Chacko"
+  } ],
+  "tags" : [ "/support/power-management/f/196/tags/BQ27Z561", "/support/power-management/f/196/tags/fuel%2bgauge" ],
+  "fourmType" : "TI"
+}

data/json/DLP/887030.json

@@ -0,0 +1,87 @@
+{
+  "ticketNumber" : "887030",
+  "reporterName" : "Murthy",
+  "rankPoints" : "590",
+  "resolutionStatus" : "TI Thinks Resolved",
+  "ticketName" : "UC2526: Regulated PWM Output",
+  "rankName" : "Intellectual",
+  "replies" : " 9",
+  "views" : " 67",
+  "queryText" : "Part Number: UC2526 Dear Sir, We are using UC2526 to control the Buck output voltage as per the attached schematic. Pin no: 1 of UC2526 error amplifier is set to 5V as a fixed reference. Pin no: 2 of UC2526 error amplifier is connected to 4N35 Collector (will vary based on feedback from 0 to 5V). we are using Type II Compensator to stabilize to loop External feed back input signal pass through LM358, BC547 and 4N35 to the Pin no: 2 of UC2526 error amplifier. Output signal from 4N35 output will be square wave (not pure analog signal) will this flow of schematic attached will adjust the duty cycle to regulate the output voltage ??. Please verify the schematic and suggets the your Valued inputs to achive the regulated PWM. Regards Murthy",
+  "partNumber" : " UC2526",
+  "allResponseList" : [ {
+    "contentId" : "3280345",
+    "userName" : "Peter Meaney",
+    "rankPoints" : "29475",
+    "rankName" : "Mastermind",
+    "date" : "Mar 9, 2020 6:23 PM",
+    "userId" : "1139254",
+    "content" : "Hi Murthy, The schematic appears to be incomplete and I cant read it clearly from the post. Can you post it as a PDF. What is you end application? Thanks Peter"
+  }, {
+    "contentId" : "3281411",
+    "userName" : "Murthy",
+    "rankPoints" : "590",
+    "rankName" : "Intellectual",
+    "date" : "Mar 10, 2020 2:28 PM",
+    "userId" : "4880309",
+    "content" : "Dear Sir, please find the attached Schematic for industrial use Regards Murthy Test Schematic.pdf"
+  }, {
+    "contentId" : "3283230",
+    "userName" : "Peter Meaney",
+    "rankPoints" : "29475",
+    "rankName" : "Mastermind",
+    "date" : "Mar 11, 2020 5:36 PM",
+    "userId" : "1139254",
+    "content" : "Hi Murthy, Thanks for the pdf schematic, from what I can see there are no components on the CT or RD pins of the controller so it will not oscillate and there will be no PWM output. Have you looked at the UCC28C4x family of devices they have PSPICE and TINA models that you can use to simulate your circuit. They have variants that do 50% or 100% duty cycle and are only 8 pin devices. Regards Peter"
+  }, {
+    "contentId" : "3286229",
+    "userName" : "Murthy",
+    "rankPoints" : "590",
+    "rankName" : "Intellectual",
+    "date" : "Mar 14, 2020 6:56 AM",
+    "userId" : "4880309",
+    "content" : "Dear Sir, Please find the attached schematic.1057.Test Schematic.pdf I have checked UCC28C4x IC TINA model. Please Suggest if any changes required. I need to control step down chopper"
+  }, {
+    "contentId" : "3299193",
+    "userName" : "Peter Meaney",
+    "rankPoints" : "29475",
+    "rankName" : "Mastermind",
+    "date" : "Mar 27, 2020 1:44 PM",
+    "userId" : "1139254",
+    "content" : "Hi Murthy, When you say you want to design a step down chopper do you mean buck stage? Thecompany Webench tool will give you a complete schematic for a buck circuit. Regards Peter"
+  }, {
+    "contentId" : "3299866",
+    "userName" : "Murthy",
+    "rankPoints" : "590",
+    "rankName" : "Intellectual",
+    "date" : "Mar 28, 2020 8:28 AM",
+    "userId" : "4880309",
+    "content" : "Hi Peter, Can you share your mail ID. I will share schematic with you. As you Know i am Using PWM IC UC2526 with reference previous posts Problem No 1: My PWM Pulses are missing after certain time period. Because i am using reset pin for my closed loop control using Optocoupler. But i don't what will be the adverse effect of missing PWM pulses on Buck Converter especially Inductor. I Want to resolve this problem.so that's why i am approaching you.By using this my output regulation is good.i testes the system by continuously running for 4 hours.Nothing is happened. But i heard sound from inductor apart from switching noise from starting till 4 Hours. Sounding like tak...after 2 or 3 sec....tak....after 2 or 3 sec....tak....I think these is happened because of missing pulses.Please confirm that this is not a big problem from experts in Power Electronics people from customer organization. Actions from my side: I tried by connecting optocoupler output to Inverting PIN and Comp Pin of UC2526. I am not getting PWM pulses output from UC2526 in closed loop.i think this is happened because of Compensation.if possible can you share closed loop control of Buck Converter application circuit using UC2526. it would be helpful. I Have some queries Question No:1 Comparator output connected 0 to 5V through optocoupler can be connected Invertering pin UC2526. Here i am attaching missing PWM pulses .JPG Hope you will help in solving my problem Regards Murthy"
+  }, {
+    "contentId" : "3315501",
+    "userName" : "Peter Meaney",
+    "rankPoints" : "29475",
+    "rankName" : "Mastermind",
+    "date" : "Apr 14, 2020 3:47 PM",
+    "userId" : "1139254",
+    "content" : "Hi Murthy, I am closing this post as we have moved support to email, please respond to my last email so we continue to work on this problem. Regards Peter"
+  }, {
+    "contentId" : "3315797",
+    "userName" : "Murthy",
+    "rankPoints" : "590",
+    "rankName" : "Intellectual",
+    "date" : "Apr 14, 2020 7:34 PM",
+    "userId" : "4880309",
+    "content" : "Dear Sir, I replied to your last mail with PDF document & Schematic Regards Murthy"
+  }, {
+    "contentId" : "3323969",
+    "userName" : "Peter Meaney",
+    "rankPoints" : "29475",
+    "rankName" : "Mastermind",
+    "date" : "Apr 22, 2020 8:22 AM",
+    "userId" : "1139254",
+    "content" : "Hi Murthy, Since we are communicating by email I am going to close this post. Regards Peter"
+  } ],
+  "tags" : [ "/support/power-management/f/196/tags/UC2526", "/support/power-management/f/196/tags/LM358" ],
+  "fourmType" : "TI"
+}

data/json/DLP/887655.json

@@ -0,0 +1,95 @@
+{
+  "ticketNumber" : "887655",
+  "reporterName" : "Hongjia-Wu",
+  "rankPoints" : "390",
+  "resolutionStatus" : "TI Thinks Resolved",
+  "ticketName" : "UCC28251: Queries about PSpice Average Model",
+  "rankName" : "Prodigy",
+  "replies" : " 16",
+  "views" : " 90",
+  "queryText" : "Part Number: UCC28251 Hi Team, In UCC28251 average model (slum358.zip), the DC value of output keeps at 90.2V regardless of the change of Vin (200~800V). Is it as expected? Thanks Hongjia",
+  "partNumber" : " UCC28251",
+  "allResponseList" : [ {
+    "contentId" : "3282914",
+    "userName" : "Peter Meaney",
+    "rankPoints" : "29475",
+    "rankName" : "Mastermind",
+    "date" : "Mar 11, 2020 2:34 PM",
+    "userId" : "1139254",
+    "content" : "Hi Hongjia, The circuit has a closed loop feedback circuit U7 and U5 that should maintain a constant output voltage over the full input voltage range so I think the circuit is behaving as expected. U7 is essentially the voltage loop error amplifier, the output voltage is divided down by R33 and R34 principally. If the voltage at the REF pin of the TL431 exceed 2.5V the TL431 will start to shunt current and pull current through the diode of the opto-coupler. This in turn will demand a lower duty cycle to maintain a constant output voltage. Regards Peter"
+  }, {
+    "contentId" : "3283731",
+    "userName" : "user4103700",
+    "rankPoints" : "70",
+    "rankName" : "Prodigy",
+    "date" : "Mar 12, 2020 4:02 AM",
+    "userId" : "4103700",
+    "content" : "Hi Peter, Actually, I am the designer of this half bridge power supply, the operation conditions are as below: Switching frequency:100 kHZ Input voltage: 200~800 Vdc Output voltage: 24 Vdc Output power: 180W Rated,216W Max, XFMR turn ratio: 3.714, Primary inductance:1000uH typical, Input voltage feedward used, voltage mode, Primary side control, use diodes as secondary side rectifier, Type III compensation network with TL431B and Zener. This power supply works fine in the steady state, but when I test the load transient capability(1A to 9A,1A/us max), I find the voltage at the pin ILIM will exceed 0.5V for a certain time, the higher slew rate of load transient, the longer overcurrent lasting time; the higher load transient, the longer overcurrent lasting time.(9Amps load is still below steady state OCP setpoint).Also, during the load transient, the waveform ILIM shows imbalanced primary current, but it will recover balanced in the end. 0A to 5A load transient 0A to 5A load transient2 if the overcurrent lasting time is longer than the OC delay time set by the cap at the pin HICC, UCC28251 will shut down the output and enter into hiccup protection mode, if I want to improve the load transient capability, I have to increase the OC delay time. when I test 2A to 7.5A load transient, the output voltage fluctuation seems acceptable. My question is: 1. why does the voltage at ILIM exceed 0.5V and the imbalanced primary current happen when load transient? is it due to loop instability (phase margin and gain margin are not enough) or is it the inherent characteristics of half bridge power supply or the issue of UCC28251 or something else? 2. Cancompany provide a unencrypted transient pspice model of UCC28251 so that I run the transient simulation in the LTSpice? Best regards, Chengjun Wang"
+  }, {
+    "contentId" : "3283904",
+    "userName" : "Peter Meaney",
+    "rankPoints" : "29475",
+    "rankName" : "Mastermind",
+    "date" : "Mar 12, 2020 8:04 AM",
+    "userId" : "1139254",
+    "content" : "Hi Chengiun, It looks like a control loop instability from looking at the ch 4 which i assume is the output voltage, have you tried reducing the gain by a factor of 10 in the control loop to see what effect it has? When you say primary side control do you mean that the controller is on the primary side and that the feedback signal is been fed back through an opto-coupler from the secondary side where the voltage error amplifier is located? Regards Peter"
+  }, {
+    "contentId" : "3284192",
+    "userName" : "user4103700",
+    "rankPoints" : "70",
+    "rankName" : "Prodigy",
+    "date" : "Mar 12, 2020 1:01 PM",
+    "userId" : "4103700",
+    "content" : "Hi Peter, The CH4 is the output voltage with measured by AC coupling, so it should be the ripple voltage. why do you think it is a control loop instability? How to reduce the gain by factor 10 in the control loop and why does it help? The controller is on the primary side, the feedback signal is fed back through an opto-coupler CNY17-3 from secondary side. Best regards, Chengjun Wang"
+  }, {
+    "contentId" : "3299197",
+    "userName" : "Peter Meaney",
+    "rankPoints" : "29475",
+    "rankName" : "Mastermind",
+    "date" : "Mar 27, 2020 1:48 PM",
+    "userId" : "1139254",
+    "content" : "Hi Chengjun, Sorry for the late response here, to decrease the gain I would increase the value of R5o from 1k to 4k7 or 10k. I would also DC couple the scope probe when measuring Vout during the load transient and offset the 0V level so the signal is still displayed on the screen. Regards Peter"
+  }, {
+    "contentId" : "3300243",
+    "userName" : "user4103700",
+    "rankPoints" : "70",
+    "rankName" : "Prodigy",
+    "date" : "Mar 30, 2020 4:56 AM",
+    "userId" : "4103700",
+    "content" : "Hi Peter, Thanks for your reply. I will try to increase R50 value in the real test, but it seems no big difference from the average model simulation. R50=1K R50=4.7K R50=10K also, the load transient waveform i shared in the previous reply was captured at the load side so that we see the DC level of voltage (AC coupled) is changing. here i attach the load transient waveform (AC coupled) which is close to the power supply output, i think it is good from the perspective of loop stability. 630Vin 2A to 7.5A_P24 ripple voltage The below is P24 voltage fluctuation (DC coupled) during load transient from 1A to 9A succefully, 630Vin_1A to 9A_P24 And the next chart show the failed load transient, you can see P24 doesn't drop too much during load transient, but due to the voltage of ILIM pin exceeds 0.5 more than 7.52ms, it shuts down the gating signals. 565Vin_1A to 9A_P24_failed Best regards, Chengjun"
+  }, {
+    "contentId" : "3303272",
+    "userName" : "Peter Meaney",
+    "rankPoints" : "29475",
+    "rankName" : "Mastermind",
+    "date" : "Apr 1, 2020 10:04 AM",
+    "userId" : "1139254",
+    "content" : "Hi Chengjun The load transient wave appears to be underdamped, reducing the gain will help reduce the overshoot when recovering but it will increase the initial dip or overshoot voltage. Have you tried to change the gain on the board? Thanks Peter"
+  }, {
+    "contentId" : "3308751",
+    "userName" : "Peter Meaney",
+    "rankPoints" : "29475",
+    "rankName" : "Mastermind",
+    "date" : "Apr 7, 2020 10:57 AM",
+    "userId" : "1139254",
+    "content" : "Hi Chengiun, I hope you have made some progress in the meantime. Since there has been no reply to my last post for nearly a week I am going to close this post. Please open a new post if you have more questions. Regards Peter"
+  }, {
+    "contentId" : "3312344",
+    "userName" : "user4103700",
+    "rankPoints" : "70",
+    "rankName" : "Prodigy",
+    "date" : "Apr 10, 2020 7:00 AM",
+    "userId" : "4103700",
+    "content" : "Hi Peter, Sorry for delay reply. i have tried to change R50 to 10k, and the test results showed that this power supply will still enter into hiccup mode when load transient from 1A to 9A with 12A/ms slew rate. Also I compared the load transient result with R50 =1k versus 10k, it seemed that the voltage overshoot and undershoot at R50 = 10k was worse. 630V_2 to 7.5A_ R50=1k （please ignore the first step since it is from 0A to 7.5A and UCC28251 enters into OCP mode） 630V_2 to 7.5A_ R50 = 10K Best regards, Chengjun"
+  }, {
+    "contentId" : "3315597",
+    "userName" : "Peter Meaney",
+    "rankPoints" : "29475",
+    "rankName" : "Mastermind",
+    "date" : "Apr 14, 2020 4:35 PM",
+    "userId" : "1139254",
+    "content" : "Hi Chengjun The change in the transient response with the larger value of resistance in series with the opto-coupler is as expected. The gain will be lower and the output voltage deviation during the load transient will be higher. I was hoping that the lower gain and slower response may help the imbalance during the load transient. The OUTA and OUTB PWM should be matched to ensure equal volts-seconds across the transformer so eliminate saturation. Can you check the COMP signal, and OUTA and OUTB pulse width during the load transient when the imbalance occurs. Maybe there is noise on the COMP pin signal that is causing and issue.You will need to use a timebase of 5us/div to capture the signals with good definition. Regards Peter"
+  } ],
+  "tags" : [ "/support/power-management/f/196/tags/UCC28251" ],
+  "fourmType" : "TI"
+}

data/json/DLP/887790.json

@@ -0,0 +1,95 @@
+{
+  "ticketNumber" : "887790",
+  "reporterName" : "user6136286",
+  "rankPoints" : "60",
+  "resolutionStatus" : "TI Thinks Resolved",
+  "ticketName" : "SM72442: question of I2C write data sequence.",
+  "rankName" : "Prodigy",
+  "replies" : " 11",
+  "views" : " 60",
+  "queryText" : "Part Number: SM72442 in the datasheet of SM72442, for I2C write sequence there is 8 data bytes from frame 4 to frame 11. if frame 4 is data 1, why frame 11 is data 7(it should be data 8)? ,and one of I2C registers is 7 bytes long, why write 8 bytes data?",
+  "partNumber" : " SM72442",
+  "allResponseList" : [ {
+    "contentId" : "3282665",
+    "userName" : "Jasper Li",
+    "rankPoints" : "37445",
+    "rankName" : "Mastermind",
+    "date" : "Mar 11, 2020 11:49 AM",
+    "userId" : "3706612",
+    "content" : "Hi i think it should be a typo. the data bytes is 7 instead of 8 from frames 5 to 11. I don't have EVM as it is quite old device. do you have an IC to try?"
+  }, {
+    "contentId" : "3283646",
+    "userName" : "user6136286",
+    "rankPoints" : "60",
+    "rankName" : "Prodigy",
+    "date" : "Mar 12, 2020 1:04 AM",
+    "userId" : "6136286",
+    "content" : "thank you so much. I am writing the software , so should i think the frame 11 is no need. please check page 14 of the datasheet of SM72442, NOW the hardware is not ready ,so i cannot test on the software ,but i want to write the right sofeware."
+  }, {
+    "contentId" : "3292003",
+    "userName" : "Jasper Li",
+    "rankPoints" : "37445",
+    "rankName" : "Mastermind",
+    "date" : "Mar 20, 2020 1:10 AM",
+    "userId" : "3706612",
+    "content" : "Hi, i think you are right. the data is from frame 4~ frame 10. I will also try this after getting the EVM."
+  }, {
+    "contentId" : "3301681",
+    "userName" : "Jasper Li",
+    "rankPoints" : "37445",
+    "rankName" : "Mastermind",
+    "date" : "Mar 31, 2020 6:50 AM",
+    "userId" : "3706612",
+    "content" : "Hi User, sorry for the late, but i'm still waiting for the EVM. thanks for your understanding."
+  }, {
+    "contentId" : "3313043",
+    "userName" : "Jasper Li",
+    "rankPoints" : "37445",
+    "rankName" : "Mastermind",
+    "date" : "Apr 12, 2020 3:08 AM",
+    "userId" : "3706612",
+    "content" : "Hi User, i got the EVM, and will try the I2C. what is the status in your side?"
+  }, {
+    "contentId" : "3320752",
+    "userName" : "Jasper Li",
+    "rankPoints" : "37445",
+    "rankName" : "Mastermind",
+    "date" : "Apr 20, 2020 5:41 AM",
+    "userId" : "3706612",
+    "content" : "Hi, your understanding is correct. the data frame should be from 4 to 10. the 11 is not need. let me know you see issue."
+  }, {
+    "contentId" : "3320773",
+    "userName" : "user6136286",
+    "rankPoints" : "60",
+    "rankName" : "Prodigy",
+    "date" : "Apr 20, 2020 6:02 AM",
+    "userId" : "6136286",
+    "content" : "THANK YOU for your work, I think this problem is fixed, now I change this chip to 72445 , 72442 need so high frequency PWM ， my NMOS can not work well, MY another question ,do you have saw it?"
+  }, {
+    "contentId" : "3327910",
+    "userName" : "Jasper Li",
+    "rankPoints" : "37445",
+    "rankName" : "Mastermind",
+    "date" : "Apr 25, 2020 11:35 PM",
+    "userId" : "3706612",
+    "content" : "Hi Sorry, which question do you refer to?"
+  }, {
+    "contentId" : "3328187",
+    "userName" : "user6136286",
+    "rankPoints" : "60",
+    "rankName" : "Prodigy",
+    "date" : "Apr 27, 2020 12:57 AM",
+    "userId" : "6136286",
+    "content" : "IT is difficult to Calculate the value of inductance and capacitance, I have find the ripple of No load output Voltage achieved 20%, the inductance is 22UH capacitance is one single Electrolytic capacitor of 330uf。 the load is BLDC motor ， not charge for battery, is some problem ?? can you check for me ,of course if you have time, thank you if you have time I will send to the Schematic diagram, now I hope you just give some advice about how to select the inductance and capacitance. best regard"
+  }, {
+    "contentId" : "3329899",
+    "userName" : "Jasper Li",
+    "rankPoints" : "37445",
+    "rankName" : "Mastermind",
+    "date" : "Apr 28, 2020 5:02 AM",
+    "userId" : "3706612",
+    "content" : "could you share the schematic? also share the VIN and VOUT waveform to show that your observation."
+  } ],
+  "tags" : [ "/support/power-management/f/196/tags/SM72442", "/support/power-management/f/196/tags/_2300_%2b%2b%2b%2b%2bI2C" ],
+  "fourmType" : "TI"
+}

data/json/DLP/887810.json

@@ -0,0 +1,95 @@
+{
+  "ticketNumber" : "887810",
+  "reporterName" : "zhijain xiao",
+  "rankPoints" : "70",
+  "resolutionStatus" : "TI Thinks Resolved",
+  "ticketName" : "How to Use LOW_POWER mode of Tas2559",
+  "rankName" : "Prodigy",
+  "replies" : " 14",
+  "views" : " 97",
+  "queryText" : "Hi: 1、requirement info: system: linux , and use iic to connect tas2559,use <tas2559-android-driver> 1.1、When there is no player to play music ,and the speaker to be silence , I need to set tas2559 to be a low power mode . 1.2、When Player is playing music，I need to resume tas2559 to normal mode. 2、I read the pdf <TAS2559 5.7-W Class-D mono audio amplifier with class-H boost and speaker sense with stereo processing > 3、I get the info : \"9.6.2.35 LOW_POWER (book=0x00 page=0x00 address=0x79) [reset=0h] \" 3.1、low power mode :I set iic from user space { 0x00, 0x00 }, { 0x7f, 0x00 }, { 0x79, 0x80 }, if I set this data to tas2559 , I can not hear sound . 3.2、normal mode :I set iic from user space { 0x00, 0x00 }, { 0x7f, 0x00 }, { 0x79, 0x00 }, after I set step 3.1 , then I set this data to tas2559 ,the sound cat not resume , I can not hear sound too. So I will never Hear sound unless to reboot system; (Please help me check the step 3.1 and 3.2 , is that right ? can I use the reg to get low power mode ) 4、when I read driver source , and find \"#define TAS2559_SLEEPMODE_CTL_REG TAS2559_REG(0, 2, 7)\" then I can not find info from PDF。Can this reg set the device to be a sleep mode ?if can ,then how can i use it , set which date to tas2559 ,let it switch between low power mode and normal mode . can you give me a demo. thanks!",
+  "partNumber" : "NA",
+  "allResponseList" : [ {
+    "contentId" : "3283112",
+    "userName" : "Ivan Salazar",
+    "rankPoints" : "48155",
+    "rankName" : "Mastermind",
+    "date" : "Mar 11, 2020 4:11 PM",
+    "userId" : "4261744",
+    "content" : "Hi Zhijain, Could you try to send these commands after step 3.2? These are taken from device data sheet, power up and unmute sequence: ################### CHANNEL POWER UP #################################################### w 98 05 A3 # Power up Analog Blocks w 98 04 B8 # Power up DSP and clock dividers w 98 07 00 # Unmute Analog Blocks w 98 7f 64 # switch to book100 w 98 07 00 # Soft stepped unmute of audio playback ############################################################################################ I'll double check on my side if these are required when toggling bit 7 from register 0x79. Best regards, -Ivan Salazar Applications Engineer - Low Power Audio & Actuators"
+  }, {
+    "contentId" : "3283728",
+    "userName" : "zhijain xiao",
+    "rankPoints" : "70",
+    "rankName" : "Prodigy",
+    "date" : "Mar 12, 2020 3:49 AM",
+    "userId" : "6297976",
+    "content" : "0x4e is my iic address. and I can hear sound ,then to set regs : step 3.1: # i2cset -f -y 1 0x4e 0 0 # i2cset -f -y 1 0x4e 0x7f 0 # i2cset -f -y 1 0x4e 0x79 0x80 Now I cant not hear sound . step 3.2: # i2cset -f -y 1 0x4e 0 0 # i2cset -f -y 1 0x4e 0x7f 0 # i2cset -f -y 1 0x4e 0x79 0 # i2cset -f -y 1 0x4e 0x05 0xa3 # i2cset -f -y 1 0x4e 0x04 0xb8 # i2cset -f -y 1 0x4e 0x07 0x0 # i2cset -f -y 1 0x4e 0x7f 0x64 # i2cset -f -y 1 0x4e 0x07 0x0 but after I set these regs , There is no sound , the speaker is still silence"
+  }, {
+    "contentId" : "3285710",
+    "userName" : "Ivan Salazar",
+    "rankPoints" : "48155",
+    "rankName" : "Mastermind",
+    "date" : "Mar 13, 2020 4:21 PM",
+    "userId" : "4261744",
+    "content" : "Zhijain, Writing into register 0x79 is similar to using the software shutdown, so the device has to be re-initialized when coming back from low-power mode. For sleep mode you can use the recommendations from section 9.5.3 from the data sheet. You can also take a look at this previous post about TAS2557, but it also applies to TAS2559. Best regards, -Ivan Salazar Applications Engineer - Low Power Audio & Actuator"
+  }, {
+    "contentId" : "3286762",
+    "userName" : "zhijain xiao",
+    "rankPoints" : "70",
+    "rankName" : "Prodigy",
+    "date" : "Mar 16, 2020 8:58 AM",
+    "userId" : "6297976",
+    "content" : "Hi: 1、please help me check the script . 2、Can we save more power in the sleep mode . The sleep mode :I execute the script \"sleep.sh\", and then the device is no sound. sleep.sh: i2cset -f -y 1 0x4e 0x07 0x01 sleep 2 i2cset -f -y 1 0x4e 0x7f 0x00 i2cset -f -y 1 0x4e 0x07 0x03 i2cset -f -y 1 0x4e 0x04 0x20 i2cset -f -y 1 0x4e 0x05 0x00 i2cset -f -y 1 0x4e 0x00 0x00 i2cset -f -y 1 0x4e 0x04 0x00 i2cset -f -y 1 0x4e 0x00 0x00 i2cset -f -y 1 0x4e 0x7f 0x00 The powerup mode : I execute the script \"powerup.sh\", and then the device has sound . powerup.sh: i2cset -f -y 1 0x4e 0x00 0x00 i2cset -f -y 1 0x4e 0x7f 0x00 i2cset -f -y 1 0x4e 0x05 0xa0 i2cset -f -y 1 0x4e 0x04 0xf8 i2cset -f -y 1 0x4e 0x07 0x00 i2cset -f -y 1 0x4e 0x7f 0x64 i2cset -f -y 1 0x4e 0x07 0x00 this table is test by our hw engineer for the device in the sleep mode . In sleep mode the power of \"DVDD\" is high, Can this power be lower? we find in specifications 7.5 of <TAS2559 5.7-W Class-D mono audio amplifier with class-H boost and speaker sense with stereo processing > ,"
+  }, {
+    "contentId" : "3286764",
+    "userName" : "zhijain xiao",
+    "rankPoints" : "70",
+    "rankName" : "Prodigy",
+    "date" : "Mar 16, 2020 9:00 AM",
+    "userId" : "6297976",
+    "content" : "the table here !"
+  }, {
+    "contentId" : "3294399",
+    "userName" : "Ivan Salazar",
+    "rankPoints" : "48155",
+    "rankName" : "Mastermind",
+    "date" : "Mar 23, 2020 5:10 PM",
+    "userId" : "4261744",
+    "content" : "Hi Zhijain, I expect to be able to run some tests on the low-power mode by the end of this week. I'll provide you some updates as soon as possible. Best regards, -Ivan Salazar Applications Engineer - Low Power Audio & Actuator"
+  }, {
+    "contentId" : "3298746",
+    "userName" : "zhijain xiao",
+    "rankPoints" : "70",
+    "rankName" : "Prodigy",
+    "date" : "Mar 27, 2020 3:22 AM",
+    "userId" : "6297976",
+    "content" : "Hi Ivan : I use this device In linux system, driver file :<tas2559-android-driver>. I think I shuld modify the driver source to sw sleep mode and powerup mode instend of use \"i2cset\" cmd to set iic . So I want to know How to modify the driver source of tas2559: 1.Let the driver automatic get into the sleep mode (auto set the registers in driver ) When there is no music playing in the system . 2.Let the driver automatic get into the powerup mode (auto set the registers in driver ) while there is some music playing in the system . thanks 1"
+  }, {
+    "contentId" : "3299218",
+    "userName" : "Ivan Salazar",
+    "rankPoints" : "48155",
+    "rankName" : "Mastermind",
+    "date" : "Mar 27, 2020 2:06 PM",
+    "userId" : "4261744",
+    "content" : "Zhijain, I'm unable to answer driver related questions, please let me communicate your questions to our SW team and get back with further comments. Best regards, -Ivan Salazar Applications Engineer - Low Power Audio & Actuator"
+  }, {
+    "contentId" : "3303547",
+    "userName" : "Ivan Salazar",
+    "rankPoints" : "48155",
+    "rankName" : "Mastermind",
+    "date" : "Apr 1, 2020 1:56 PM",
+    "userId" : "4261744",
+    "content" : "Zhijain, Some comments from our software team: The sleep and powerup feature is available in TAS2562 onwards. We don’t have auto Power up and power down of amplifier based on I2S clocks. In tas2559, the only way is to explicitely powerup the device using i2c when music is available to be played. Best regards, -Ivan Salazar Applications Engineer - Low Power Audio & Actuator"
+  }, {
+    "contentId" : "3304317",
+    "userName" : "zhijain xiao",
+    "rankPoints" : "70",
+    "rankName" : "Prodigy",
+    "date" : "Apr 2, 2020 1:53 AM",
+    "userId" : "6297976",
+    "content" : "Hi Ivan: Thanks ! Count you check the messages ,I sent it to you at \"Mar 16, 2020 8:58 AM\" . 1、please help me check the script ,\"sleep.sh\" and \"powerup.sh\" . 2、Can we save more power in the sleep mode ."
+  } ],
+  "tags" : [ "/support/power-management/f/196/tags/sleep%2bmode", "/support/power-management/f/196/tags/TAS2559", "/support/power-management/f/196/tags/low%2bpower" ],
+  "fourmType" : "TI"
+}

data/json/DLP/888430.json

@@ -0,0 +1,87 @@
+{
+  "ticketNumber" : "888430",
+  "reporterName" : "J A Valina",
+  "rankPoints" : "40",
+  "resolutionStatus" : "TI Thinks Resolved",
+  "ticketName" : "LMZM23600: Output voltage too low",
+  "rankName" : "Prodigy",
+  "replies" : " 9",
+  "views" : " 85",
+  "queryText" : "Part Number: LMZM23600 We are using the LMZM23600V5SILT on a prototype to generate a 5 volt output from a 20 volt input. With an approximately 2 mA load (the minimum feasible at this time), the output on the prototype is slightly less than 3 volts; adding a 100 ohm resistor load reduces the output to around 2 volts. With the minimal load, the output voltage appears stable on the oscilloscope; with the 100 ohm load, the output is erratically varying by 250 mV. The circuit diagram is the same as Figure 37 with the exception that feedback is directly connected to the output without any resistors. Cin (C1102) is 10 uF 50 v X7R and Cout (C1101) is 47 uF 16 v X5R. The board layout is approximately the same as that shown in Figure 82 of the data sheet. The differences for the layout are: 1. Footprint pad size is 0.45 x 0.8 (recommended footprint has 0.3 x 0.65) 2. FB and OUT are both connected directly to a component side power plane 3. Under component ground plane fill has 0.225 gap to component pads. Are these differences likely to account for the problem? Are there exposed pads on the underside of the component that could be shorting to the ground fill under the component? Or does it seem more likely that either the component is bad or there is a solder bridge between pins? Thank you for your help.",
+  "partNumber" : " LMZM23600",
+  "allResponseList" : [ {
+    "contentId" : "3286184",
+    "userName" : "Jimmy Hua",
+    "rankPoints" : "17640",
+    "rankName" : "Genius",
+    "date" : "Mar 14, 2020 1:32 AM",
+    "userId" : "4798049",
+    "content" : "Hi J A Valina, Can you probe the SW node to check the switching frequency of the part? This can be done by probing the top side of the exposed inductor. Please be careful when probing the exposed terminal and make sure not to accidentally short it to GND. Doing so will damage the part. Additionally can you read out the voltage measurements on each pin? As for the PCB layout, generally I would recommend having a small thin trace connecting feedback to VOUT. The feedback pin is generally considered a sensitive node since it can couple noise if there is a large enough plane. This may result in output voltage regulation issues. Note that Figure 82 also shows the thin feedback connection to VOUT power plane. Another thing you can do is try to mechanically press on the part and check regulation. This will exercise if there is any pin connectivity issue which would point to solder voids/ no connects. You can reflow the part off your prototype board and examine both the part and your board to see if there are any solder bridges. Regards, Jimmy"
+  }, {
+    "contentId" : "3286305",
+    "userName" : "J A Valina",
+    "rankPoints" : "40",
+    "rankName" : "Prodigy",
+    "date" : "Mar 14, 2020 6:10 PM",
+    "userId" : "65707",
+    "content" : "Hi Jimmy, Here's the SW node trace: It appears to be oscillating at 754 kHz (the frequency shown in the image above is incorrect). I cannot probe most of the pins since the pads are concealed by the module, but Vin is 20.43 v and Vout is 2.94 v. Pressing down on the module had no effect. I will alter the PCB layout of the FB pin for the next prototype. Thanks for your help! Jay"
+  }, {
+    "contentId" : "3286468",
+    "userName" : "Jimmy Hua",
+    "rankPoints" : "17640",
+    "rankName" : "Genius",
+    "date" : "Mar 15, 2020 10:10 PM",
+    "userId" : "4798049",
+    "content" : "Hi Jay, If you are using a fixed output power module (LMZM23600V3 or LMZM23600V5) then the switching frequency is expected to be typical at 750kHz. However, the switch node doesn't look like a square-wave. As previously mentioned, please try to reduce the parasitic inductance on FB node by having a thin dedicated trace to VOUT for fixed output option. Let me know if you have any additional questions on this. I will close this thread for now. Regards, Jimmy"
+  }, {
+    "contentId" : "3286477",
+    "userName" : "J A Valina",
+    "rankPoints" : "40",
+    "rankName" : "Prodigy",
+    "date" : "Mar 15, 2020 11:03 PM",
+    "userId" : "65707",
+    "content" : "Hi Jimmy, Do you think that having the solid connection from FB to VOUT is the cause of the problem? It seems to me that connecting FB to VOUT by a thin trace would increase rather than decrease the inductance. Thanks for your help! Jay"
+  }, {
+    "contentId" : "3286559",
+    "userName" : "Jimmy Hua",
+    "rankPoints" : "17640",
+    "rankName" : "Genius",
+    "date" : "Mar 16, 2020 3:49 AM",
+    "userId" : "4798049",
+    "content" : "Hi Jay, Let me redact what I said previous, for some reason during the explanation I was thinking adjustable when you are using fixed. Actually when you are using the fixed version, the feedback resistors should be internal. This means the sensitive node is protected and accounted for internally. I don't think I asked this, how many of your boards experienced this failure? Also was the part hand soldered onto your prototype or did it have a control reflow profile? Again the switch node is abnormal and should be a clean square wave. Can you do a ABBA test on two prototype boards to see if the failure follows the part? Regards, Jimmy"
+  }, {
+    "contentId" : "3297258",
+    "userName" : "Jimmy Hua",
+    "rankPoints" : "17640",
+    "rankName" : "Genius",
+    "date" : "Mar 25, 2020 10:14 PM",
+    "userId" : "4798049",
+    "content" : "Hi Jay, Can I get an update on the questions above? What is the progress of the ABBA test? Does the failure move with the unit? Additionally what are you power downstream? If possible try to isolate the circuit by disconnecting the downstream system and retest troubleshooting with either a load resistor or E-LOAD to check operation of the LMZM23600 alone. Regards, Jimmy"
+  }, {
+    "contentId" : "3302485",
+    "userName" : "Jimmy Hua",
+    "rankPoints" : "17640",
+    "rankName" : "Genius",
+    "date" : "Mar 31, 2020 6:53 PM",
+    "userId" : "4798049",
+    "content" : "Hi Jay, Can you give an update to the ABBA testing? Have you tried continuity test? You can probe the voltage measurements between all pins and ground to get an understanding if there is any shorts or abnormal voltage. Also I have a few more questions about this condition: Just to reconfirm you application condition: VIN = 20V; VOUT = 5V; IOUT = ~50mA; Tambient = 25degC (room temperature) What peak temperature was the device reflowed at? Was the device hand soldered or did it go through a controlled reflow process? Can you provide the date and lot code for these parts? This information is usually detailed in the shipping label on the package. How many failures has this been observed on? I'm guessing this failure is seen on the same site on different boards? Regards, Jimmy"
+  }, {
+    "contentId" : "3306396",
+    "userName" : "Jimmy Hua",
+    "rankPoints" : "17640",
+    "rankName" : "Genius",
+    "date" : "Apr 3, 2020 6:22 PM",
+    "userId" : "4798049",
+    "content" : "Hi Jay, Any updates on the testing and feedback for my questions? Again I'd like to reiterate that the switching waveform that you measured is not characteristic of a switching converter (generally square wave). I'd like to see the same test done on a new unit on the same PCB layout to confirm issue is preserved. Regards, Jimmy"
+  }, {
+    "contentId" : "3323465",
+    "userName" : "Jimmy Hua",
+    "rankPoints" : "17640",
+    "rankName" : "Genius",
+    "date" : "Apr 21, 2020 9:05 PM",
+    "userId" : "4798049",
+    "content" : "Hi, I have not heard back from you for some time and will assume you were able to close this issue on your end. Because of this, I will be closing this thread for now. If you have any further questions on this, please reply back to this and the thread will reopen for further discussion. Regards, Jimmy"
+  } ],
+  "tags" : [ "/support/power-management/f/196/tags/LMZM23600", "/support/power-management/f/196/tags/Low%2boutput%2bVoltage" ],
+  "fourmType" : "TI"
+}

data/json/DLP/888827.json

@@ -0,0 +1,95 @@
+{
+  "ticketNumber" : "888827",
+  "reporterName" : "Kubendran G1",
+  "rankPoints" : "270",
+  "resolutionStatus" : "TI Thinks Resolved",
+  "ticketName" : "LM5041: Feedback loop Compensation",
+  "rankName" : "Intellectual",
+  "replies" : " 17",
+  "views" : " 116",
+  "queryText" : "Part Number: LM5041 Hi Every one: I need to clarify LM5041 application circuit compensation design. Application circuit error opamp pole and zero placed below freq. Error op amp zero 1 placed by R35,C36 @ 1.326KHz Error op amp zero 2 placed by R32,C40 @ 22.9KHz Error op amp pole 1 placed by R42,C40 @96.7KHz Error op amp pole 2 placed by R35,C35 @279KHz My question 1) Op amp first zero placed in plant double pole L=60uH, Cout: 932uH F=673Hz? 2)Op amp second zero placed freq where should get? 3) I dint find Cout ESR value. Pole 1 placed in plant zero? I think Pole 2 placed almost in buck switching freq.LM5041..docx 3) How to compensate opto pole by error opamp in this application? 4)Kindly share any document available for compensation design for this application. (Opto coupler feedback with external opamp) 5) R11 and C11 form the opto pole? Kindly reply as soon as possible. Regards, Kubendran",
+  "partNumber" : " LM5041",
+  "allResponseList" : [ {
+    "contentId" : "3286821",
+    "userName" : "Kubendran G1",
+    "rankPoints" : "270",
+    "rankName" : "Intellectual",
+    "date" : "Mar 16, 2020 10:00 AM",
+    "userId" : "6226009",
+    "content" : "Hellocompany Team, I am expecting your valuable reply. Regards, Kubendran"
+  }, {
+    "contentId" : "3288788",
+    "userName" : "Kubendran G1",
+    "rankPoints" : "270",
+    "rankName" : "Intellectual",
+    "date" : "Mar 17, 2020 4:22 PM",
+    "userId" : "6226009",
+    "content" : "Hellocompany Team, We are facing loop compensation and buck switching node voltage oscillation issue with respect to LM 5041 application circuit design. Always i seen LM5041 related query response very delayed. Kindly reply previous query. Regards, Kubendran"
+  }, {
+    "contentId" : "3289706",
+    "userName" : "Peter Meaney",
+    "rankPoints" : "29475",
+    "rankName" : "Mastermind",
+    "date" : "Mar 18, 2020 11:12 AM",
+    "userId" : "1139254",
+    "content" : "Hi Kubendran, Sorry for the delay, the office that supports this controller was on public holiday, I have assigned an AE to this post. Regards Peter"
+  }, {
+    "contentId" : "3289716",
+    "userName" : "Kubendran G1",
+    "rankPoints" : "270",
+    "rankName" : "Intellectual",
+    "date" : "Mar 18, 2020 11:22 AM",
+    "userId" : "6226009",
+    "content" : "Hi Peter, When will i expect the reply. Regards, Kubendran"
+  }, {
+    "contentId" : "3308730",
+    "userName" : "Kubendran G1",
+    "rankPoints" : "270",
+    "rankName" : "Intellectual",
+    "date" : "Apr 7, 2020 10:24 AM",
+    "userId" : "6226009",
+    "content" : "Hellocompany team, No reply? Regards, Kubendran"
+  }, {
+    "contentId" : "3308826",
+    "userName" : "Peter Meaney",
+    "rankPoints" : "29475",
+    "rankName" : "Mastermind",
+    "date" : "Apr 7, 2020 12:16 PM",
+    "userId" : "1139254",
+    "content" : "Hi Kubendran, My mistake, there was a mistake in the email address for the AE in the system and this post did not appear on his list. I am checking if the AE assigned can support if not I will assign a new AE to help. I should have an update tomorrow. Regards Peter"
+  }, {
+    "contentId" : "3310018",
+    "userName" : "Teng Feng",
+    "rankPoints" : "9390",
+    "rankName" : "Genius",
+    "date" : "Apr 8, 2020 7:58 AM",
+    "userId" : "5617595",
+    "content" : "Hi Kubendran, Unfortunate, I didn't find any document for the compensation design of this application. In this application, the designer used much complex two stage network with two LM6132 op amps and a LM4041 reference. I guess this circuit demonstrates the flexibility that can be used in electronic circuit design. I think it can be designed simpler with only one amplifier LM6132 and one reference LM4041. Since in this application, there is no internal error amplifier used, so it relies on the designer to add the error amplifier. It is targeted at isolated designs the error amp is usually on the secondary side driving an opto-coupler through the isolation barrier to the control pin. The schematic in page 14 of the LM5041 datasheet shows such a scheme. U4A is the error amplifier. C35, R35, C36, R42, C40 and R32 make up the type III compensation network. Regards, Teng"
+  }, {
+    "contentId" : "3310048",
+    "userName" : "Kubendran G1",
+    "rankPoints" : "270",
+    "rankName" : "Intellectual",
+    "date" : "Apr 8, 2020 8:36 AM",
+    "userId" : "6226009",
+    "content" : "Hi Sir, Please read carefully my previous query. What you are said error op amp R and C value corresponding pole and zero frequency already calculated. My question how you are placed compensator pole,zero and opto coupler pole to the plant response. If i consider plant is double pole that value not matched with actually what you are used in compensator pole and zero. Actually current mode plant having one pole and one zero. In this way also checked compensator value did not matched. Kindly look this one serious and give best solution.I am facing converter output oscillating issue. Regards, Kubendran"
+  }, {
+    "contentId" : "3310118",
+    "userName" : "Teng Feng",
+    "rankPoints" : "9390",
+    "rankName" : "Genius",
+    "date" : "Apr 8, 2020 9:52 AM",
+    "userId" : "5617595",
+    "content" : "Hi Kubendaran, Did you made a measurement of the gain, phase or if you have done a load transient test and measured the response of the output voltage waveform to see if the response with well damped or under damped. I don't think we can get a final value through calculation, actually it is complected and difficult to establish the signal model. My suggestion is: please adjust the compensation according the measured transient performance. Regards, Teng"
+  }, {
+    "contentId" : "3310134",
+    "userName" : "Kubendran G1",
+    "rankPoints" : "270",
+    "rankName" : "Intellectual",
+    "date" : "Apr 8, 2020 10:07 AM",
+    "userId" : "6226009",
+    "content" : "Hi Sir, I will share the waveform to your mail. Please reply. Regards, Kubendran."
+  } ],
+  "tags" : [ "/support/power-management/f/196/tags/LM5041" ],
+  "fourmType" : "TI"
+}

data/json/DLP/889133.json

@@ -0,0 +1,39 @@
+{
+  "ticketNumber" : "889133",
+  "reporterName" : "Thomas Gati",
+  "rankPoints" : "20",
+  "resolutionStatus" : "",
+  "ticketName" : "TPS50601A-SP: TPS50601A-SP Load and Line regulation; Vsense voltage not constant, it varies",
+  "rankName" : "Prodigy",
+  "replies" : " 3",
+  "views" : " 55",
+  "queryText" : "Part Number: TPS50601A-SP Hi Test results (24 degrees C case is shown) indicate load and line regulation issues. Voltages are measured with respect to analog return. In particular, the Vsense pin voltage is expected to remain constant (within micro volts) as load current and input voltage are varied. Test results indicate undue magnitudes of voltage variation of the Vsense pin. MHP50601A TPS50601A-SP EM319 Load Vout1 Vsense Vss PG EN Vin Tsink Iin Pin Pout Ploss efficiency ch1 ch2 ch3 ch4 ch5 ch8 ch9 ch10 Test Date UNIT amp volt volt volt volt volt volt °C amp watt watt watt 2/6/2020 SN1 0.101 0.886 0.809 1.486 1.647 1.345 3.292 26.2 0.037 0.1 0.1 0.0 72.6% 2/6/2020 SN1 6.004 0.802 0.798 1.447 1.658 1.319 3.268 25.9 2.532 8.3 4.8 3.5 58.2% 2/6/2020 SN1 0.101 0.887 0.809 1.497 3.001 1.761 5.997 26.2 0.031 0.2 0.1 0.1 47.8% 2/6/2020 SN1 6.004 0.727 0.785 1.429 3.006 1.753 5.985 26.4 1.270 7.6 4.4 3.2 57.4% 2/6/2020 SN1 0.101 4.385 0.810 1.495 2.501 1.655 4.996 28.1 0.106 0.5 0.4 0.1 83.6% 2/6/2020 SN1 6.004 4.410 0.814 1.498 2.525 1.639 4.939 28.2 6.060 29.9 26.5 3.5 88.5% 2/5/2020 SN1-16 0.101 0.884 0.809 1.517 1.646 1.347 3.289 28.5 0.037 0.1 0.1 0.0 73.1% 2/5/2020 SN1-16 6.004 0.802 0.798 1.484 1.512 1.321 3.264 28.4 2.610 8.5 4.8 3.7 56.5% 2/5/2020 SN1-16 0.101 0.883 0.809 1.528 2.999 1.760 5.994 28.5 0.031 0.2 0.1 0.1 47.7% 2/5/2020 SN1-16 6.004 0.721 0.784 1.453 3.005 1.752 5.982 28.7 1.282 7.7 4.3 3.3 56.5% 2/5/2020 SN1-16 0.101 4.381 0.809 1.526 2.499 1.655 4.993 30.4 0.106 0.5 0.4 0.1 84.0% 2/5/2020 SN1-16 6.004 4.406 0.814 1.528 2.524 1.639 4.935 30.3 6.057 29.9 26.5 3.4 88.5% 2/6/2020 SN2 0.101 0.889 0.809 1.449 1.649 1.344 3.295 22.3 0.039 0.1 0.1 0.0 70.6% 2/6/2020 SN2 6.004 0.808 0.798 1.405 1.659 1.318 3.271 22.4 2.559 8.4 4.9 3.5 58.0% 2/6/2020 SN2 0.101 0.889 0.809 1.458 3.002 1.762 5.999 23.1 0.032 0.2 0.1 0.1 47.3% 2/6/2020 SN2 6.004 0.734 0.786 1.376 3.007 1.754 5.987 23.6 1.294 7.7 4.4 3.3 56.9% 2/6/2020 SN2 0.101 4.387 0.810 1.456 2.501 1.655 4.997 25.7 0.107 0.5 0.4 0.1 82.8% 2/6/2020 SN2 6.004 4.412 0.815 1.455 2.526 1.639 4.940 26.0 6.068 30.0 26.5 3.5 88.4% 2/5/2020 SN2-16 0.101 0.874 0.807 1.503 1.646 1.347 3.289 28.6 0.037 0.1 0.1 0.0 73.1% 2/5/2020 SN2-16 6.004 0.792 0.796 1.465 1.603 1.320 3.265 28.1 2.518 8.2 4.8 3.5 57.8% 2/5/2020 SN2-16 0.101 0.873 0.807 1.514 2.999 1.760 5.994 28.3 0.031 0.2 0.1 0.1 48.0% 2/5/2020 SN2-16 6.004 0.720 0.784 1.437 3.005 1.752 5.982 28.5 1.267 7.6 4.3 3.3 57.1% 2/5/2020 SN2-16 0.101 4.371 0.807 1.511 2.499 1.655 4.993 29.8 0.106 0.5 0.4 0.1 83.9% 2/5/2020 SN2-16 6.003 4.404 0.814 1.515 2.524 1.639 4.935 30.0 6.048 29.8 26.4 3.4 88.6% 2/6/2020 SN3-16 0.101 0.866 0.806 1.496 1.646 1.342 3.288 28.7 0.037 0.1 0.1 0.0 72.0% 2/6/2020 SN3-16 6.004 0.764 0.791 1.458 1.656 1.315 3.265 28.2 2.481 8.1 4.6 3.5 56.6% 2/6/2020 SN3-16 0.100 0.866 0.806 1.507 2.999 1.758 5.994 28.5 0.031 0.2 0.1 0.1 47.4% 2/6/2020 SN3-16 6.004 0.696 0.780 1.432 3.005 1.750 5.982 28.7 1.262 7.5 4.2 3.4 55.4% 2/6/2020 SN3-16 0.101 4.364 0.806 1.505 2.499 1.652 4.993 30.1 0.106 0.5 0.4 0.1 83.8% 2/6/2020 SN3-16 6.003 4.394 0.812 1.508 2.524 1.636 4.936 30.1 6.056 29.9 26.4 3.5 88.3% 2/6/2020 SN4 0.101 0.877 0.808 1.466 1.648 1.349 3.292 25.8 0.037 0.1 0.1 0.0 72.3% 2/6/2020 SN4 6.004 0.802 0.797 1.428 1.659 1.323 3.268 25.5 2.607 8.5 4.8 3.7 56.5% 2/6/2020 SN4 0.101 0.878 0.808 1.476 3.001 1.762 5.997 25.9 0.031 0.2 0.1 0.1 48.1% 2/6/2020 SN4 6.004 0.727 0.785 1.402 3.007 1.755 5.985 26.2 1.320 7.9 4.4 3.5 55.3% 2/6/2020 SN4 0.101 4.376 0.808 1.474 2.501 1.657 4.996 28.0 0.106 0.5 0.4 0.1 83.5% 2/6/2020 SN4 6.004 4.396 0.812 1.476 2.526 1.641 4.938 28.0 6.074 30.0 26.4 3.6 88.0% 2/5/2020 SN8 0.101 0.889 0.809 1.485 1.646 1.346 3.289 29.1 0.037 0.1 0.1 0.0 73.2% 2/5/2020 SN8 6.004 0.812 0.799 1.453 1.501 1.319 3.263 28.8 2.745 9.0 4.9 4.1 54.5% 2/5/2020 SN8 0.101 0.889 0.809 1.495 2.999 1.759 5.994 28.8 0.031 0.2 0.1 0.1 47.8% 2/5/2020 SN8 6.004 0.733 0.786 1.421 3.005 1.751 5.981 29.1 1.363 8.1 4.4 3.7 54.0% 2/5/2020 SN8 0.101 4.386 0.810 1.492 2.499 1.654 4.993 30.6 0.106 0.5 0.4 0.1 83.4% 2/5/2020 SN8 6.003 4.387 0.811 0.987 0.032 1.638 4.935 30.8 6.094 30.1 26.3 3.7 87.6% 2/5/2020 SN14 0.102 0.883 0.808 1.505 1.646 1.349 3.290 27.6 0.038 0.1 0.1 0.0 72.6% 2/5/2020 SN14 6.004 0.797 0.796 1.469 1.657 1.323 3.265 27.8 2.562 8.4 4.8 3.6 57.2% 2/5/2020 SN14 0.101 0.883 0.808 1.516 3.000 1.761 5.995 28.4 0.032 0.2 0.1 0.1 46.9% 2/5/2020 SN14 6.004 0.729 0.785 1.443 3.005 1.753 5.983 28.5 1.300 7.8 4.4 3.4 56.3% 2/5/2020 SN14 0.101 4.380 0.809 1.513 2.499 1.656 4.994 29.9 0.106 0.5 0.4 0.1 83.9% 2/5/2020 SN14 6.004 4.405 0.814 1.516 2.524 1.640 4.936 29.9 6.070 30.0 26.4 3.5 88.3%",
+  "partNumber" : " TPS50601A-SP",
+  "allResponseList" : [ {
+    "contentId" : "3288679",
+    "userName" : "Christian Yots",
+    "rankPoints" : "9520",
+    "rankName" : "Genius",
+    "date" : "Mar 17, 2020 3:17 PM",
+    "userId" : "32944",
+    "content" : "Hi, I can look into this but will need more information from you. The variation on the regulated output, and therefore, Vsense is highly dependent on the external circuitry of the converter. Could you please provide schematic for each scenario (target VOUT) including the ESR of the output capacitance being used. Also, please provide what regulation ripple you have designed for. You can send to me privately if you prefer not to post on this public forum. Thanks Christian"
+  }, {
+    "contentId" : "3299381",
+    "userName" : "Thomas Gati",
+    "rankPoints" : "20",
+    "rankName" : "Prodigy",
+    "date" : "Mar 27, 2020 4:01 PM",
+    "userId" : "6301225",
+    "content" : "simulation POL Hybrid 1-0.pdf"
+  }, {
+    "contentId" : "3323240",
+    "userName" : "Christian Yots",
+    "rankPoints" : "9520",
+    "rankName" : "Genius",
+    "date" : "Apr 21, 2020 5:53 PM",
+    "userId" : "32944",
+    "content" : "Hi, From the schematic provided it appears you are targeting the following applications: VIN=3.3, 5V, 6V IOUT = 100mA, 6A Fswitching = 300kHz VOUT = 2.515V Can you confirm these are the target applications. The VOUT measured is not 2.5V as it should be indicating a gross problem. The compensation circuit in the schematic does not look correct for me. I estimate the following comp circuit. R9=12kohms C3=22nF C6=650pF Thanks Christian"
+  } ],
+  "tags" : [ "/support/power-management/f/196/tags/TPS50601A_2D00_SP", "/support/power-management/f/196/tags/TPS50601A_2D00_SP%2bLoad%2band%2bLine%2bregulation", "/support/power-management/f/196/tags/Vsense%2bvoltage%2bnot%2bconstant" ],
+  "fourmType" : "TI"
+}

data/json/DLP/889708.json

@@ -0,0 +1,47 @@
+{
+  "ticketNumber" : "889708",
+  "reporterName" : "Rainer Koliwer",
+  "rankPoints" : "10",
+  "resolutionStatus" : "",
+  "ticketName" : "WEBENCH® Tools/LM3150: Customize LM3150MH/NOPB ‑ 19V-29V to 5.00V @ 7A, .......Message : Design update failed - Junction temperature is too high",
+  "rankName" : "Prodigy",
+  "replies" : " 4",
+  "views" : " 54",
+  "queryText" : "Part Number: LM3150 Tool/software: WEBENCH® Design Tools We have planned to use the LM3150 in a project. We entered our data in the Power designer. VIN 19 to 29V, 60 ° C, Vout 5V, 7A. The Power Designer issues a circuit diagram proposal. So far so good. If we press the \"Redesign\" button, the message \"Design update failed - Junction temperature is too high\" always appears. However, nothing is apparent from the FET or IC where the junction temperature is too high. What does the message refer to?",
+  "partNumber" : " LM3150",
+  "allResponseList" : [ {
+    "contentId" : "3290844",
+    "userName" : "Vishwanath Tigadi",
+    "rankPoints" : "1240",
+    "rankName" : "Intellectual",
+    "date" : "Mar 19, 2020 5:00 AM",
+    "userId" : "4786829",
+    "content" : "Hi Rainer, We're looking into this. I'll keep you posted as soon as possible. Regards, Vishwanath"
+  }, {
+    "contentId" : "3302977",
+    "userName" : "Vishwanath Tigadi",
+    "rankPoints" : "1240",
+    "rankName" : "Intellectual",
+    "date" : "Apr 1, 2020 5:05 AM",
+    "userId" : "4786829",
+    "content" : "Hi Rainer, We're still working on this. I'll keep you posted on the proceedings. Regards, Vishwanath"
+  }, {
+    "contentId" : "3311143",
+    "userName" : "Vishwanath Tigadi",
+    "rankPoints" : "1240",
+    "rankName" : "Intellectual",
+    "date" : "Apr 9, 2020 5:28 AM",
+    "userId" : "4786829",
+    "content" : "Hi Rainer, We're still working on this. I'll keep you posted on when the changes will be available on <secret URL>. Regards, Vishwanath"
+  }, {
+    "contentId" : "3325266",
+    "userName" : "Bhushan Waghmare",
+    "rankPoints" : "2245",
+    "rankName" : "Intellectual",
+    "date" : "Apr 23, 2020 5:57 AM",
+    "userId" : "4633427",
+    "content" : "Hi Rainer, Thanks for your patience. Seems this is a bug. For your case the design should be fine. We have forwarded this to concerned team. We will get back to you once we have solution on this. Best Regards, Bhushan"
+  } ],
+  "tags" : [ "/support/power-management/f/196/tags/WEBENCH_AE00_%2bDesign%2bTools", "/support/power-management/f/196/tags/LM3150" ],
+  "fourmType" : "TI"
+}

data/json/DLP/889755.json

@@ -0,0 +1,47 @@
+{
+  "ticketNumber" : "889755",
+  "reporterName" : "cheng huang chou",
+  "rankPoints" : "540",
+  "resolutionStatus" : "TI Thinks Resolved",
+  "ticketName" : "AWR1642: AWR1642 Radar Monitoring Asynchronous Events lost",
+  "rankName" : "Intellectual",
+  "replies" : " 4",
+  "views" : " 40",
+  "queryText" : "Part Number: AWR1642 I set 8 Radar monitoring items, Temperature, Rx Gain Phase, Rx Noise Figure, IF stage, Tx0 power, Tx1 power, Tx0 ballbreak, Tx1 ballbreak, In MmwDemo_mssMmwaveEventCallbackFxn, I can not get the msgId (RL_RF_AE_MON_TEMPERATURE_REPORT_SB and RL_RF_AE_MON_RX_GAIN_PHASE_REPORT) but the other I can get correctly. What's wrong with this? Should I change rlRfCalMonTimeUntConf_t.calibMonTimeUnit? My SDK is mmwave_sdk_02_00_00_04 Thank You Liang-Yu",
+  "partNumber" : " AWR1642",
+  "allResponseList" : [ {
+    "contentId" : "3289957",
+    "userName" : "Cesar",
+    "rankPoints" : "52960",
+    "rankName" : "Guru",
+    "date" : "Mar 18, 2020 2:29 PM",
+    "userId" : "20288",
+    "content" : "Hi, The monitors may not be supported in the firmware version you are using. Please refer to the documentation of the firmware release. (Radar Interface Document in the DFP release) You probably should upgrade your application to use the latest firmware provided with SDK 3.3 thank you Cesar"
+  }, {
+    "contentId" : "3300180",
+    "userName" : "cheng huang chou",
+    "rankPoints" : "540",
+    "rankName" : "Intellectual",
+    "date" : "Mar 30, 2020 2:20 AM",
+    "userId" : "4108705",
+    "content" : "Hi, I have upgraded FW to the latest version (SDK 3.3), but MmwDemo_mssMmwaveEventCallbackFxn still does not have the Temperature and Rx Gain Phase report. How to fix this? Thank you Liang - Yu"
+  }, {
+    "contentId" : "3300302",
+    "userName" : "Jitendra Gupta",
+    "rankPoints" : "33995",
+    "rankName" : "Mastermind",
+    "date" : "Mar 30, 2020 6:27 AM",
+    "userId" : "1717369",
+    "content" : "Hello Liang - Yu, Could you refer mmwavelink test application from mmWave SDK which tests these two features. control\\mmwavelink\\test Regards, Jitendra"
+  }, {
+    "contentId" : "3328905",
+    "userName" : "cheng huang chou",
+    "rankPoints" : "540",
+    "rankName" : "Intellectual",
+    "date" : "Apr 27, 2020 2:32 PM",
+    "userId" : "4108705",
+    "content" : "Hi In mmwave Demo's dss_main.c, I add these functions ( rlRfTempMonConfig, rlRfRxGainPhMonConfig, ， rlRfRxNoiseMonConfig, rlRfRxIfStageMonConfig, rlRfTxPowrMonConfig, rlRfTxBallbreakMonConfig) in MmwDemo_dssDataPathConfigCQ. I still can't get temperature and Rx gain phase, but the other items can be received by MmwDemo_mssMmwaveEventCallbackFxn in mss_main.c. Is it correct to add these functions in here? Thank You Liang-Yu"
+  } ],
+  "tags" : [ "/support/sensors/f/1023/tags/AWR1642" ],
+  "fourmType" : "TI"
+}

data/json/DLP/890211.json

@@ -0,0 +1,95 @@
+{
+  "ticketNumber" : "890211",
+  "reporterName" : "Will Brown",
+  "rankPoints" : "200",
+  "resolutionStatus" : "Resolved",
+  "ticketName" : "TPS2493EVM-002: IMON spurious output",
+  "rankName" : "Prodigy",
+  "replies" : " 27",
+  "views" : " 160",
+  "queryText" : "Part Number: TPS2493EVM-002 I am evaluating the TSP2493 using the EVM-002 board. We plan to use the part with an MCU and monitor the output current, and use the UVEN line to control the output. During my testing, using the ENA/DIS switch on the PCB, I noted that sometimes the IMON output would go to full scale for about 200uS immediately after being enabled. To speed testing and eliminate any variables due to manual switching, I connected a signal generator to the UVEN line (see attached PDF). For this testing, no load was attached to the PCB. The only circuit elements present on VOUT are C3, C9 and D2 as indicated in the EVM schematic. What I then observed, is that depending on the PRF (repetition frequency), IMON either glitches, or does not glitch, immediately after UVEN goes high. For example, at 5.0Hz PRF, IMON behaves correctly when UVEN is asserted. At 5.1Hz, IMON goes full-scale for 200uS every time UVEN is asserted. I observed this behavior from as low as 0.7Hz, to as high as 20Hz, with variations in PRF from 0.01 to 0.1Hz causing a change in IMON behavior. There are 3 scope plots in the attached PDF. The two plots that show IMON indicate a small damped hump starting about 400uS after UVEN is asserted. This is the charging current of the capacitor(s) on VOUT. The third plot shows that VOUT has not begun to turn on yet when IMON goes full scale. All other signals (FAULT, PG, TIMER), maintain a steady value throughout the ON period. In other words, no other operation anomalies are observed, it seems that the IMON output is the only affected signal. TPS2493_IMON_Glitch.pdf Thanks for any insights, Will",
+  "partNumber" : " TPS2493EVM-002",
+  "allResponseList" : [ {
+    "contentId" : "3291406",
+    "userName" : "Rakesh",
+    "rankPoints" : "39750",
+    "rankName" : "Mastermind",
+    "date" : "Mar 19, 2020 2:09 PM",
+    "userId" : "4743883",
+    "content" : "Hi Will, Thanks for reaching out! We have never observed that kind of behavior. Can you capture Vout, input current, UVEN, IMON in a single scope shot for the second test scenario where IMON pulse is observed and share it with us Thanks, Rakesh"
+  }, {
+    "contentId" : "3291417",
+    "userName" : "Will Brown",
+    "rankPoints" : "200",
+    "rankName" : "Prodigy",
+    "date" : "Mar 19, 2020 2:16 PM",
+    "userId" : "5920759",
+    "content" : "Thank you for the quick reply. I apologize that I do not have the appropriate test equipment to perform the measurement as requested. I have one additional piece of information which I dismissed but in retrospect may be important, and why you've never seen this. During my very initial tests, using just a power supply and active load, one of the two MOSFETS failed. It failed shorted Drain-Source (Gate/Source and Gate/Drain did not show a short). I desoldered the failed MOSFET, and have been testing since using the remaining MOSFET. The gate drive seems fine. I cannot explain what happened that cause the MOSFET to fail. It actually blew a blob of solder out from underneath it, when it heated quickly and then presumably failed. Part of the thermal pad appeared discolored... perhaps the part had a coating flaw or contamination causing lack of reflow to the land, and subsequent hot-spot. I assumed the TPS2493 was unaffected after this event, but perhaps whatever happened compromised the part somehow."
+  }, {
+    "contentId" : "3291513",
+    "userName" : "Will Brown",
+    "rankPoints" : "200",
+    "rankName" : "Prodigy",
+    "date" : "Mar 19, 2020 3:26 PM",
+    "userId" : "5920759",
+    "content" : "I should add that though I currently cannot capture 4 channels at once, the behavior I observe on the scope is very repeatable. For example Vout looks the same the entire time the PRF is set to cause the IMON glitch. How do you propose I measure the input current? I assume you mean a direct measurement using a current probe?"
+  }, {
+    "contentId" : "3292432",
+    "userName" : "Rakesh",
+    "rankPoints" : "39750",
+    "rankName" : "Mastermind",
+    "date" : "Mar 20, 2020 11:38 AM",
+    "userId" : "4743883",
+    "content" : "Hi Will, Thanks for the additional background details. Do you have another TSP2493 device to replace on EVM and to check whether the behavior is repeatable or not? By this, we can also rule out that partial unknown damage for the original unit is not the cause. If you have current probe, measure the input current along with the IMON voltage to check whether they follow in time Best Regards, Rakesh"
+  }, {
+    "contentId" : "3292730",
+    "userName" : "Will Brown",
+    "rankPoints" : "200",
+    "rankName" : "Prodigy",
+    "date" : "Mar 20, 2020 3:32 PM",
+    "userId" : "5920759",
+    "content" : "Hi Rakesh, I will order a few new parts, or another EVM altogether, and report back. Continued testing shows everything else works as advertised (power limiting during startup, etc) Will"
+  }, {
+    "contentId" : "3292748",
+    "userName" : "Rakesh",
+    "rankPoints" : "39750",
+    "rankName" : "Mastermind",
+    "date" : "Mar 20, 2020 3:44 PM",
+    "userId" : "4743883",
+    "content" : "Hi Will, What are your target specs and requirements. ? Can you have a look at TPS25982, TPS1663x devices and let me know what you think. Regards, Rakesh"
+  }, {
+    "contentId" : "3292778",
+    "userName" : "Will Brown",
+    "rankPoints" : "200",
+    "rankName" : "Prodigy",
+    "date" : "Mar 20, 2020 4:01 PM",
+    "userId" : "5920759",
+    "content" : "Hi Rakesh, Thanks for the recommendations. Based on our requirements, it doesn't appear either are suitable unfortunately. We are looking to run between 24-48V (surge to 50V), with up to 20A continuous current, with hardware-based fast transient overload protection, with slower MCU-based eFusing (i2t behavior). The application will have about 20 of these output channels, so keeping power dissipation low per channel is important for passive heat rejection which is also a requirement for us. I am looking at using the TPS2493 (or something equivalent) with an LM5050 ideal diode output in series (and a suitable TVS on the final output), with both controllers using NVMFS5C604NLWFAFT1G as the pass element. I am open to other topology or part number suggestions. This is what I've come up with after going through a previous design and prototype iteration, and new requirements being added (higher voltage, higher current, faster performance). Also perhaps worth mentioning, I am looking to protect the main power input using an LM5060 and 4x parallel of the above listed MOSFETs, to provide OVP shutdown and gross overcurrent protection, with 100A steady-state pass current. I just tested the LM5060 EVM and was happy with the performance. Thanks, Will"
+  }, {
+    "contentId" : "3293206",
+    "userName" : "Rakesh",
+    "rankPoints" : "39750",
+    "rankName" : "Mastermind",
+    "date" : "Mar 21, 2020 10:08 AM",
+    "userId" : "4743883",
+    "content" : "Hi Will, LM5069 would be preferred over LM5060 device. LM5069 provides accurate overload protection, FET SOA protection (power limiting feature) and fast shutdown during short circuit events. The LM5060 is intended for applications where precise current sensing is not required, but some level of fault protection is needed. Examples are applications where inductance or impedance in the power path limits the current rise in a short circuit condition. Please refer 8.1.5 Overcurrent Fault in the datasheet. Please refer <secret URL>/lit/an/snva683/snva683.pdf for configuring the device for surge support Best Regards, Rakesh"
+  }, {
+    "contentId" : "3294153",
+    "userName" : "Will Brown",
+    "rankPoints" : "200",
+    "rankName" : "Prodigy",
+    "date" : "Mar 23, 2020 2:51 PM",
+    "userId" : "5920759",
+    "content" : "Hi Rakesh, I initially downselected to the 5060 vs the 5069 to eliminate the sense resistor, at the expense of a more uncontrolled current limit. I will re-evaluate based on your recommendation. Also, I have replacement TPS2493 parts coming, in addition to a new EVM. I will post results once they arrive and I can repeat the tests. Thanks Will"
+  }, {
+    "contentId" : "3306437",
+    "userName" : "Will Brown",
+    "rankPoints" : "200",
+    "rankName" : "Prodigy",
+    "date" : "Apr 3, 2020 7:04 PM",
+    "userId" : "5920759",
+    "content" : "Hi Rakesh, Sorry for the delay in getting back. There was an issue getting the package delivered with the current state of affairs. The new EVM behaves with the same spurious IMON output. I will attach a PDF with a graph of all the parameters of interest. Since I do not have a good way to probe the input current, I inserted a 10 Ohm resistor in series with Vin, and the measurement Vin represents the power supply output, and Vin' represents the input voltage to the TPS2493EVM board. As in my original post, I can elicit this response by actuating the ENABLE switch on the PCB. For my testing, I connected a signal generator to UV(EN), adjusted the frequency until the problem arose, and then performed scope captures at each point in the circuit, at all times monitoring IMON to ensure the behavior was still present. TPS2493_EVM.pdf Also attached is the Excel file with the raw data I collected. TPS2493_EVM.xlsx Thank you for any insights, Will"
+  } ],
+  "tags" : [ "/support/power-management/f/196/tags/TPS2493", "/support/power-management/f/196/tags/TPS2493EVM_2D00_002" ],
+  "fourmType" : "TI"
+}

data/json/DLP/890514.json

@@ -0,0 +1,95 @@
+{
+  "ticketNumber" : "890514",
+  "reporterName" : "Tejasweeni Zope",
+  "rankPoints" : "90",
+  "resolutionStatus" : "TI Thinks Resolved",
+  "ticketName" : "BQ34110: initial steps to start communication with MCU",
+  "rankName" : "Prodigy",
+  "replies" : " 16",
+  "views" : " 93",
+  "queryText" : "Part Number: BQ34110 I am using BQ34110 ic for two LI-ion batteries. I am not getting any data for the commands such as DeviceType() , DeviceName() etc registers. Is there any configuration settings to be done before this. It would be helpful if I get complete step by step procedure to interface it as I wanted to have voltage, current , SOH, SOC information regarding my batteries.",
+  "partNumber" : " BQ34110",
+  "allResponseList" : [ {
+    "contentId" : "3292675",
+    "userName" : "Andy Liu (BMS)",
+    "rankPoints" : "42410",
+    "rankName" : "Mastermind",
+    "date" : "Mar 20, 2020 3:05 PM",
+    "userId" : "1864278",
+    "content" : "I would suggest you take a look at the app note below. <secret URL>/lit/an/slua790/slua790.pdf Andy"
+  }, {
+    "contentId" : "3293637",
+    "userName" : "Tejasweeni Zope",
+    "rankPoints" : "90",
+    "rankName" : "Prodigy",
+    "date" : "Mar 23, 2020 5:04 AM",
+    "userId" : "6306374",
+    "content" : "Thank you for quick reply. When I am trying to read DeviceType() data,it is showing only 0000 values than 0110. Can you send the implementation function of atleast single control command on stm32 micro controller ?"
+  }, {
+    "contentId" : "3294389",
+    "userName" : "Andy Liu (BMS)",
+    "rankPoints" : "42410",
+    "rankName" : "Mastermind",
+    "date" : "Mar 23, 2020 5:01 PM",
+    "userId" : "1864278",
+    "content" : "Sorry, we don't provide the code. I would suggest you use the bqStudio to communicate with the gauge device, capture the sequence using a logic analyzer and implement the same sequence in your microcontroller. Andy"
+  }, {
+    "contentId" : "3298261",
+    "userName" : "Tejasweeni Zope",
+    "rankPoints" : "90",
+    "rankName" : "Prodigy",
+    "date" : "Mar 26, 2020 5:08 PM",
+    "userId" : "6306374",
+    "content" : "Can I get the flowchart or any algorithm to get at least DeviceType() or DeviceName()? I had made successful communication with bq34110 ic but when i was trying to get DeviceType() , the responce should be 0x1001 in little endien format, but I don't get response like that. Also, I am confused that when I send 0X01 data to 0x00 control register address and 0x00 data to 0x01 control register address, I should get its respective DeviceType() response at 0x40 /0x41 address. Please correct me if I am wrong. This is the sequence I am following in my implementation."
+  }, {
+    "contentId" : "3298481",
+    "userName" : "Andy Liu (BMS)",
+    "rankPoints" : "42410",
+    "rankName" : "Mastermind",
+    "date" : "Mar 26, 2020 8:36 PM",
+    "userId" : "1864278",
+    "content" : "We already provided all the details in the app note I provided before. Make sure you read through that app note and make good of the Advanced Coom tab to test the sequence. To get the right response for the DeviceType() MAC Subcommand, follow the steps below. ENTER: Start Register 3E, Bytes to Write 0100 and PRESS the Write button. The I2C words occur in the following order in the data stream: AA, 3E, 01, 00. ENTER: Start Register 40, Number of Bytes to Read 2 and PRESS the Read button. The I2C words occur in the following order in the data stream: AA, 40, AB, 10, 01"
+  }, {
+    "contentId" : "3303799",
+    "userName" : "Tejasweeni Zope",
+    "rankPoints" : "90",
+    "rankName" : "Prodigy",
+    "date" : "Apr 1, 2020 4:35 PM",
+    "userId" : "6306374",
+    "content" : "Hi Andy I followed steps given by you and got response as expected 0x0110 but when I tried for another sub command that is device name response is 00 D4 0B A9 0B FF FF in hex format and C C C C C C C in char format can u tell what is exactly missing here? also I dont have BQstudio with me . I am doing all my interfacing using i2c communication. Can I get default response values when perticular subcommand is used to cross check weather we are getting correct response or not"
+  }, {
+    "contentId" : "3304099",
+    "userName" : "Andy Liu (BMS)",
+    "rankPoints" : "42410",
+    "rankName" : "Mastermind",
+    "date" : "Apr 1, 2020 8:54 PM",
+    "userId" : "1864278",
+    "content" : "I can read back the correct device name in the bqStudio, which is the same as the ASCII characters mentioned in the TRM. You would need to check your code."
+  }, {
+    "contentId" : "3304530",
+    "userName" : "Tejasweeni Zope",
+    "rankPoints" : "90",
+    "rankName" : "Prodigy",
+    "date" : "Apr 2, 2020 7:01 AM",
+    "userId" : "6306374",
+    "content" : "Hi Andy I will again check it considering your suggestions. I have some basic queries which are not cleared through TRM 1. Can we access consecutive sub commands one after other in a sequence? If yes then is there any delay to be added in between? 2. Is it mandatory to perform factory calibration before accessing any sub command also? I understood that it is important for voltage ,current , temp, SOH etc commands. 3. Without doing any setting what is default state of ic (sealed or unsealed) and mode (normal, snooze, shutdown) ? 4. How to check default configuration status in IC before writing for any command? Thanks in advance."
+  }, {
+    "contentId" : "3305154",
+    "userName" : "Andy Liu (BMS)",
+    "rankPoints" : "42410",
+    "rankName" : "Mastermind",
+    "date" : "Apr 2, 2020 4:37 PM",
+    "userId" : "1864278",
+    "content" : "See my comments below. 1. Can we access consecutive sub commands one after other in a sequence? If yes then is there any delay to be added in between? [Andy] Yes. I would suggest you add a short delay (e.g. 3ms). 2. Is it mandatory to perform factory calibration before accessing any sub command also? I understood that it is important for voltage ,current , temp, SOH etc commands. [Andy] No. However, if you want the voltage, current or temperature readings to be accurate. I would suggest you do the calibration first. 3. Without doing any setting what is default state of ic (sealed or unsealed) and mode (normal, snooze, shutdown) ? 4. How to check default configuration status in IC before writing for any command? [Andy] I would suggest you get an EV2400 and use bqStudio to check the default configurations. With the proper tool and software, it is much easier to work the gauge device. Andy"
+  }, {
+    "contentId" : "3316538",
+    "userName" : "Tejasweeni Zope",
+    "rankPoints" : "90",
+    "rankName" : "Prodigy",
+    "date" : "Apr 15, 2020 11:30 AM",
+    "userId" : "6306374",
+    "content" : "Hello Andy, Thank you . Your suggestions was very helpful. With that reference, Can you help me more in things as bq34110 I2C note don't have that details: 1. I had evaluated default values of Pin control, Operation config A and design capacity registers as per guidelines. And now I wanted to change its values as per my design. I had followed following sequence: ------- calibration start ------- Data Flash Access Commands to Change the Pin control register as per bq34110 I2C note. ------- calibration end I wanted to check weather the new value is stored accurately or not, What sequence should I follow ? 2. What I learnt from TRM is that factory calibration is necessary to read voltage value, Do I need to set Pin control, Operation config A and design capacity etc before Board Offset, temp, voltage, current calibration? 3. Minimum which registers and parameters required to get at least voltage reading? If possible, please recommend page number of document where all these details are mentioned. Thanks in Advance."
+  } ],
+  "tags" : [ "/support/power-management/f/196/tags/BQ34110" ],
+  "fourmType" : "TI"
+}

data/json/DLP/890598.json

@@ -0,0 +1,79 @@
+{
+  "ticketNumber" : "890598",
+  "reporterName" : "Sajin M1",
+  "rankPoints" : "70",
+  "resolutionStatus" : "TI Thinks Resolved",
+  "ticketName" : "BQ27441-G1: Average current and SOC measured by BQ27441 is not accurate",
+  "rankName" : "Prodigy",
+  "replies" : " 8",
+  "views" : " 60",
+  "queryText" : "Part Number: BQ27441-G1 Hi, I have a power section which is using BQ27441 as the fuel gauge to measure the status of a LiPo battery that has 4400 mAh capacity in total. The 4400 mAh capacity is achieved by connecting two identical 2200 mAh batteries in parallel. By the datasheet of the battery, the Maximum voltage is about 4.2V, the nominal voltage is 3.7V and the discharge cutoff voltage is 2.7V. The system parameters are listed below: Maximum charging current: 2.4A Maximum discharge current: 2A Minimum running voltage: 3.4V Maximum battery voltage: 4.2V Cutoff current: 160 mA the current sense resistor is 10 mOhm For this system we configured the following parameters in the fuel guage: BATTERY_CAPACITY = 4400 //4400 mAh battery will be connected TERMINATE_VOLTAGE = 3400 // 3400mV terminate voltage DESIGN_ENERGY = 16280 //16280 mWh design energy TAPER_RATE =275 FC set = 92% full charge set FC clear = 90% full charge clear TAPER_VOLTAGE =4160 Fortunately, the fuel gauge is measuring battery voltage and temperature at much better accuracy but it is not for average current and capacity. I am listing my issues and questions below: Issue 1: The current (Both Discharging and charging) measured by the fuel gauge was having an error of more than 8% (more than 200 mA), but after manually changing the CC gain from0.237 to 0.205 it is working properly now. but in the case of the remaining capacity and percentage of charge the there is a huge margin of error is there. Issue 2: The fuel gauge is showing 100 % of charge while charging even it is only at 3881 mAh and 0% before it is reaching the Terminate voltage (3.4V) Question1: I need to measure the capacity of the battery with much accuracy(less 1% error), what is the step for setting up the proper configuration for the fuel gauge to get the proper remaining capacity and percentage of charge?",
+  "partNumber" : " BQ27441-G1",
+  "allResponseList" : [ {
+    "contentId" : "3293106",
+    "userName" : "Andy Liu (BMS)",
+    "rankPoints" : "42410",
+    "rankName" : "Mastermind",
+    "date" : "Mar 20, 2020 11:31 PM",
+    "userId" : "1864278",
+    "content" : "Hi Sanjin, I guess you should have received a report from the GPCCHEM. Could you share it with me? Thanks. Andy"
+  }, {
+    "contentId" : "3293164",
+    "userName" : "Sajin M1",
+    "rankPoints" : "70",
+    "rankName" : "Prodigy",
+    "date" : "Mar 21, 2020 4:49 AM",
+    "userId" : "6275925",
+    "content" : "Hi Andy, Thank you for the reply. I am attaching the report with this mail please have a look4380.GPC_report.txt"
+  }, {
+    "contentId" : "3293338",
+    "userName" : "Kang Kang",
+    "rankPoints" : "17055",
+    "rankName" : "Genius",
+    "date" : "Mar 22, 2020 12:16 AM",
+    "userId" : "3528441",
+    "content" : "Hello Sajin, This is a ROM based gauge. There is no method to change the chemID. Are you able to upgrade to a bq27z561 flash based gauge that supports chemID programming?"
+  }, {
+    "contentId" : "3293356",
+    "userName" : "Sajin M1",
+    "rankPoints" : "70",
+    "rankName" : "Prodigy",
+    "date" : "Mar 22, 2020 3:31 AM",
+    "userId" : "6275925",
+    "content" : "Hi kang, Thank you for your reply and sorry to say that we can't change the fuel gauge right now, we already manufactured some large quantities of boards. Is there any other way to optimize the SOC?"
+  }, {
+    "contentId" : "3293657",
+    "userName" : "Sajin M1",
+    "rankPoints" : "70",
+    "rankName" : "Prodigy",
+    "date" : "Mar 23, 2020 5:44 AM",
+    "userId" : "6275925",
+    "content" : "By the datasheet, the total capacity of the battery is 4400 mAh, 16280 mWh and the cut off voltage is 2.7V and we are setting the same for the configuration of BQ27441, but for our design, we can't go up to 2.7V, we are stoping the discharge when the voltage reaches only 3.4V thereby we are not using the total 4400mAh or 16280 mWh. Will it be the cause for the issue?"
+  }, {
+    "contentId" : "3295974",
+    "userName" : "Kang Kang",
+    "rankPoints" : "17055",
+    "rankName" : "Genius",
+    "date" : "Mar 24, 2020 9:10 PM",
+    "userId" : "3528441",
+    "content" : "Hello Sajin, You will need to look at the Qpass register during the discharge. If it is not even 90% of the discharge vs. design capacity, I would recommend setting the terminate voltage to 3.4 volts if that's your system shutdown voltage."
+  }, {
+    "contentId" : "3316372",
+    "userName" : "Sajin M1",
+    "rankPoints" : "70",
+    "rankName" : "Prodigy",
+    "date" : "Apr 15, 2020 8:01 AM",
+    "userId" : "6275925",
+    "content" : "Hi Kang, We will test that thing that you have said about the Qpass register and update it with you. I have one more doubt is there, It is about the CC_GAIN. We had a current measurement accuracy issue previously and it was solved by altering the value in CC_GAIN register. But by going through the datasheet I got to know that CC_GAIN is no for customer usage and it is only for debugging purposes, so is that mean we can't alter the CC_GAIN value? Is it not the proper way to tackle the error in current sensing? If so what is the proper method?"
+  }, {
+    "contentId" : "3321955",
+    "userName" : "Dominik Hartl11",
+    "rankPoints" : "35875",
+    "rankName" : "Mastermind",
+    "date" : "Apr 20, 2020 8:54 PM",
+    "userId" : "9849",
+    "content" : "You can change CC_GAIN. It is not restricted to debugging only. About gauge accuracy: The gauge uses the built in ChemID to run discharge simulations. You must complete a successful learning cycle where the gauge can measure QMax and cell impedance. This requires accurate current measurements. A learning cycle is basically a series of controlled charge/relax/discharge/relax sequences. See <secret URL>/how-perform-successful-learning-cycle-gauges Once the gauge learned these properties, it will be as accurate as the built-in ChemID allows for the cell that you use. Make sure that you configure charge termination correctly (you use C/27.5 but a C/25 with a taper rate of 250 is more appropriate for your taper current - the guideline is 15% more current than your taper current to make sure that the gauge detects charge termination reliably). Also verify that the discharge/charge and quit current thresholds are compatible with your application. The gauge must be in the correct state (charge/discharge/relax) for this to work."
+  } ],
+  "tags" : [ "/support/power-management/f/196/tags/BQ27441_2D00_G1" ],
+  "fourmType" : "TI"
+}

data/json/DLP/890620.json

@@ -0,0 +1,23 @@
+{
+  "ticketNumber" : "890620",
+  "reporterName" : "Alex Bhandari-Young",
+  "rankPoints" : "15670",
+  "resolutionStatus" : "Resolved",
+  "ticketName" : "[FAQ] Ambient Light Sensors: List of all FAQs",
+  "rankName" : "Genius",
+  "replies" : " 1",
+  "views" : " 404",
+  "queryText" : "",
+  "partNumber" : "NA",
+  "allResponseList" : [ {
+    "contentId" : "3293072",
+    "userName" : "Alex Bhandari-Young",
+    "rankPoints" : "15670",
+    "rankName" : "Genius",
+    "date" : "Mar 20, 2020 10:16 PM",
+    "userId" : "4691324",
+    "content" : "Comparing Devices [FAQ] OPT3004: OPT3001 vs OPT3004, what is the difference? [FAQ] OPT3001: OPT3001 vs OPT3002 Optics [FAQ] OPT3001: OPT300X Family Parts: Industrial design of light sensor with cover glass/window opening [FAQ] OPT3001: What is the f1' value of the OPT3001? [FAQ] OPT3001: What is important and what are some key care-abouts when I design a light-sensitive user interface? Electrical [FAQ] OPT3001: Is there leakage on SDA and SCL if the pull-up supply is active and the power supply is not? Software [FAQ] OPT300X Family Parts: What are the available drivers for TI's family of ambient light sensors? [FAQ] OPT3001: Is there example raspberry pi code for the OPT3001? [FAQ] OPT3001: Do Linux/Android drivers exist for the OPT3001? [FAQ] OPT3001: Is there MSP430 code for use with the OPT3001? Mechanical/Assembly ALS OPT300x Handling Instructions [FAQ] OPT3001: Where is the STEP model (.STP) for the OPT3001? Performance/Accuracy [FAQ] OPT3001: What is the performance under flickering LED Light [FAQ] OPT3001: What is the accuracy of an OPT300x part? [FAQ] OPT3001: Why does the OPT3001 not have any data taken outside, under sunlight? [FAQ] OPT3001: Why does the OPT3001 not have a range that measures full sunlight at 130Klux? EVM [FAQ] OPT3001: Are the OPT3001EVM PCB files available? [FAQ] OPT3001: Debugging connection issues with the OPT3001EVM"
+  } ],
+  "tags" : [ "/support/sensors/f/1023/tags/OPT3001EVM", "/support/sensors/f/1023/tags/OPT3001", "/support/sensors/f/1023/tags/OPT3006", "/support/sensors/f/1023/tags/OPT3004", "/support/sensors/f/1023/tags/OPT3002", "/support/sensors/f/1023/tags/OPT3007" ],
+  "fourmType" : "TI"
+}

data/json/DLP/890626.json

@@ -0,0 +1,23 @@
+{
+  "ticketNumber" : "890626",
+  "reporterName" : "Ning T",
+  "rankPoints" : "15365",
+  "resolutionStatus" : "Resolved",
+  "ticketName" : "[FAQ] BQ25606: Schematic Review and PCB Layout Design Tips",
+  "rankName" : "Genius",
+  "replies" : " 1",
+  "views" : " 197",
+  "queryText" : "Part Number: BQ25606 Please refer to the document below for Schematic Review and PCB Layout Design Tips for BQ25606. The selection of an external component can be either Required or Optional: Required - Absolutely required for proper operation Optional - Optional components Using this information, customer can reduce external components based on their application, as well as use this document to help in assisting with schematic reviews.",
+  "partNumber" : " BQ25606",
+  "allResponseList" : [ {
+    "contentId" : "3293092",
+    "userName" : "Ning T",
+    "rankPoints" : "15365",
+    "rankName" : "Genius",
+    "date" : "Mar 20, 2020 11:00 PM",
+    "userId" : "145100",
+    "content" : "BQ25606_SchematicChecklist V1p0.pdf Thank you very much, Ning."
+  } ],
+  "tags" : [ "/support/power-management/f/196/tags/BQ25606" ],
+  "fourmType" : "TI"
+}

data/json/DLP/890672.json

@@ -0,0 +1,63 @@
+{
+  "ticketNumber" : "890672",
+  "reporterName" : "reza nouriyan",
+  "rankPoints" : "100",
+  "resolutionStatus" : "TI Thinks Resolved",
+  "ticketName" : "BQ25713: Charger can’t charge continuously",
+  "rankName" : "Prodigy",
+  "replies" : " 6",
+  "views" : " 75",
+  "queryText" : "Part Number: BQ25713 Hi dear I am using BQ25713 in order to charge 4 cell battery with 5v USB power banks All default values of registers are fine to me. I just want to charge cells with 1.2 ampere and be able to charge again when adapter is removed and plugged again. I just set my desired current to 0x02 and 0x03 and charger starts to charge but after less than a second charger stops charging. Here are my questions: 1) i was not able to do previously described procedure with 5v USB power bank and i did it with power supply. Why is that ? As i understood charger had to set all offsets and initializes with respect to input voltage without help of host. So why it didn’t charge cells with 5v? 2) did i something wrong to charge with 1.2A ? And why charger stops charging fast",
+  "partNumber" : " BQ25713",
+  "allResponseList" : [ {
+    "contentId" : "3293324",
+    "userName" : "reza nouriyan",
+    "rankPoints" : "100",
+    "rankName" : "Prodigy",
+    "date" : "Mar 21, 2020 9:26 PM",
+    "userId" : "5241641",
+    "content" : "When i put charge current at almost 100mA it works but for greater currents charger stops charging in less than a second"
+  }, {
+    "contentId" : "3293350",
+    "userName" : "reza nouriyan",
+    "rankPoints" : "100",
+    "rankName" : "Prodigy",
+    "date" : "Mar 22, 2020 2:47 AM",
+    "userId" : "5241641",
+    "content" : "Please take into account that i didn’t change any register after POR and just updated charge current register. I assumed that charger will update input voltage and current limit registers automatically when an adapter plugged vmax charge and vmin sys default values are ok to me. Is there a way to disable DPM mode that decrease charge current to give priority to system load. Because i think problem is related to this issue. But on the other hand i am testing IC at no load so there is no load to draw current from VSYS. I am completely confused Please help"
+  }, {
+    "contentId" : "3294086",
+    "userName" : "Joel Hernandez II",
+    "rankPoints" : "25800",
+    "rankName" : "Mastermind",
+    "date" : "Mar 23, 2020 2:05 PM",
+    "userId" : "4615895",
+    "content" : "Hey Reza, We need a register dump the moment before and the moment after the charger stops charging. A waveform is also necessary, showing VBUS, IBUS, SW2, and VSRN. Regards, Joel H"
+  }, {
+    "contentId" : "3295242",
+    "userName" : "reza nouriyan",
+    "rankPoints" : "100",
+    "rankName" : "Prodigy",
+    "date" : "Mar 24, 2020 10:17 AM",
+    "userId" : "5241641",
+    "content" : "Dear Joel hi, thanks for reply unfortunately i am not able to check waveform and share with you but i have found out that when i write some values to charge current register BQ doesn't charge batteries but for some other values it starts charging but also in this way charging current is not same as i wrote it. which registers do you want to know before and after. just let me know thanks again best regards"
+  }, {
+    "contentId" : "3298018",
+    "userName" : "Joel Hernandez II",
+    "rankPoints" : "25800",
+    "rankName" : "Mastermind",
+    "date" : "Mar 26, 2020 2:15 PM",
+    "userId" : "4615895",
+    "content" : "Hey reza, I would like to see all charger registers before an after. Regards, Joel H"
+  }, {
+    "contentId" : "3322715",
+    "userName" : "Peter Sammer",
+    "rankPoints" : "10",
+    "rankName" : "Prodigy",
+    "date" : "Apr 21, 2020 12:31 PM",
+    "userId" : "3983126",
+    "content" : "Hi! Check the watchdog timer in ChargeOption0 register (I2C address = 01/00h) - WDTMR_ADJ. The default setting stops charging after 175s without repeatedly sending the charge current. You can disable the watchdog by setting 00 for bits 6-5 - then the charging will not stop when you don't send the current register. Best, P"
+  } ],
+  "tags" : [ "/support/power-management/f/196/tags/BQ25713" ],
+  "fourmType" : "TI"
+}

data/json/DLP/890769.json

@@ -0,0 +1,95 @@
+{
+  "ticketNumber" : "890769",
+  "reporterName" : "Dmitry Sinyukov",
+  "rankPoints" : "80",
+  "resolutionStatus" : "TI Thinks Resolved",
+  "ticketName" : "BQ24070: BQ24070: No charge termination status is activated and interference with step-up converter on payload side",
+  "rankName" : "Prodigy",
+  "replies" : " 14",
+  "views" : " 88",
+  "queryText" : "Part Number: BQ24070 Hello! 1. Please can you help me to check my schematic and understand BQ24070 behavior in charge termination mode? The problem is charge termination status is not activated for hours (checked for 10h at least) on fully charged battery or w/o battery connected. I didn't ever saw any other status than STAT1=ON and STAT2=OFF. Control resistors are adjusted to the values: Rdppm=37k, Rset=3.54k, Rtmr=50k. Voltage at ISET1 pin and battery charge current are goes to zero at the end of charge and Vbat is 4.21V if no load connected (as red cross on the drawing show). 2. When I add a payload with a step-up converter (U2 L6920D) I also faced with a sort of interference on BQ24070. I get a voltage drop about 0.4V at BQ24070 OUT pin at each step-up converter cycle (see the diagram below). In that case, I have a noise about 50mV at ISET1 pin and battery final voltage increase on 0.01V. And I have no idea how to handle with that voltage drops caused by step-up converter. Please give me a guess. Best regards, Dmitry",
+  "partNumber" : " BQ24070",
+  "allResponseList" : [ {
+    "contentId" : "3294275",
+    "userName" : "Anthony P Pham",
+    "rankPoints" : "1890",
+    "rankName" : "Intellectual",
+    "date" : "Mar 23, 2020 3:56 PM",
+    "userId" : "6169362",
+    "content" : "Hi Dmitry, Just to get a better understanding of your problem, is the information you provided for when ISET2 and MODE are HIGH or LOW?"
+  }, {
+    "contentId" : "3294352",
+    "userName" : "Dmitry Sinyukov",
+    "rankPoints" : "80",
+    "rankName" : "Prodigy",
+    "date" : "Mar 23, 2020 4:43 PM",
+    "userId" : "4895097",
+    "content" : "Hi Anthony, thank you for reply! ISET2 and MODE are both HIGH for my setup. Best regards, Dmitry"
+  }, {
+    "contentId" : "3294369",
+    "userName" : "Raheem",
+    "rankPoints" : "16655",
+    "rankName" : "Genius",
+    "date" : "Mar 23, 2020 4:49 PM",
+    "userId" : "4697250",
+    "content" : "Hello, WHat is the state of MOde and ISET2?"
+  }, {
+    "contentId" : "3294498",
+    "userName" : "Dmitry Sinyukov",
+    "rankPoints" : "80",
+    "rankName" : "Prodigy",
+    "date" : "Mar 23, 2020 6:24 PM",
+    "userId" : "4895097",
+    "content" : "Hi Raheem, thank you for reply! ISET2 and MODE are both HIGH for my setup. Best regards, Dmitry"
+  }, {
+    "contentId" : "3301210",
+    "userName" : "Anthony P Pham",
+    "rankPoints" : "1890",
+    "rankName" : "Intellectual",
+    "date" : "Mar 30, 2020 7:30 PM",
+    "userId" : "6169362",
+    "content" : "Hi Dmitry, Just to check that the device is operating correctly, as I don't think I see any problems with your schematic, does the device show proper current when in fast charge mode (for instance when the battery is a 3.5V)?"
+  }, {
+    "contentId" : "3304040",
+    "userName" : "Dmitry Sinyukov",
+    "rankPoints" : "80",
+    "rankName" : "Prodigy",
+    "date" : "Apr 1, 2020 8:14 PM",
+    "userId" : "4895097",
+    "content" : "Hi Anthony, yes it is. I have discharge my battery down to 3.4V, switch on DC supply, and check battery charge current. It was constant 0.3A as it should be for my Rset value, till ~4V at the battery. I left my setup switched on during the night and have found at the next morning both status LEDs are off, so finally charging was stopped by timer for the first time. But I still had a small charging current about 1mA at my battery and voltage was about 4.3V. Then I made just an off-on cycle at DC supply and have got STAT1=ON signal again for a whole day as usual. But charge current is zero now. It looks like completely broken logic, but I can't understand why. I'm continue some more experiments... Best regards, Dmitry"
+  }, {
+    "contentId" : "3304126",
+    "userName" : "Anthony P Pham",
+    "rankPoints" : "1890",
+    "rankName" : "Intellectual",
+    "date" : "Apr 1, 2020 9:26 PM",
+    "userId" : "6169362",
+    "content" : "Dmitry, Would you be able to monitor the voltage TMR pin and see how that is operating as the current drops below 30mA (calculated termination current)? Do you also see the same behavior with higher RSET values?"
+  }, {
+    "contentId" : "3305262",
+    "userName" : "Dmitry Sinyukov",
+    "rankPoints" : "80",
+    "rankName" : "Prodigy",
+    "date" : "Apr 2, 2020 6:05 PM",
+    "userId" : "4895097",
+    "content" : "Anthony, I repeated a charge cycle today (but disconnected a payload from BQ24070 now, pure charger). Voltage at TMR pin was 2.51V from the beginning of current regulation phase till Vbat rised about 4.1V and then it began to drop down to 722mV on fully charged battery. V_TMR was 725mV when charge current dropped below 30mA. In this cycle STAT1 signal stalled again, I waited 12 hours and it still show charging, but charge current is zero now. I will increase charge current from 0.3A to 0.6A tomorrow and test it again. UPDATE: I have increased charge current twice to 0.6A - absolutely the same voltage at TMR pin as I described above. STAT1 signal went OFF after 10 hours indicating charge time is out. Charge current is zero. No indication of finished charge by STAT2. Best Regards, Dmitry"
+  }, {
+    "contentId" : "3309334",
+    "userName" : "Raheem",
+    "rankPoints" : "16655",
+    "rankName" : "Genius",
+    "date" : "Apr 7, 2020 5:25 PM",
+    "userId" : "4697250",
+    "content" : "Hello, Can you swap out the battery and use a sourcemeter instead on BAT pin WHat voltage do you measure on ISET1 pin when the battery voltage is around 4.2V? Also, can you try removing the C4 capacitor and see if that makes a difference? From the schematic, can you have the LEDs be pulled up to OUT instead of IN"
+  }, {
+    "contentId" : "3310751",
+    "userName" : "Dmitry Sinyukov",
+    "rankPoints" : "80",
+    "rankName" : "Prodigy",
+    "date" : "Apr 8, 2020 7:19 PM",
+    "userId" : "4895097",
+    "content" : "Hello, Raheem! Can you swap out the battery and use a sourcemeter instead on BAT pin Sorry, I don't have this type of tool. But I checked charge cycle with two different batteries: 1000mAh flat LiPo protected cell and 18650 2200mAh unprotected NCM cell. In both cases BQ behaves absolutely same. WHat voltage do you measure on ISET1 pin when the battery voltage is around 4.2V? 0V (zero) Also, can you try removing the C4 capacitor and see if that makes a difference? No difference. From the schematic, can you have the LEDs be pulled up to OUT instead of IN I just performed this modification: nothing changed. Best regards, Dmitry"
+  } ],
+  "tags" : [ "/support/power-management/f/196/tags/BQ24070" ],
+  "fourmType" : "TI"
+}

data/json/DLP/891022.json

@@ -0,0 +1,95 @@
+{
+  "ticketNumber" : "891022",
+  "reporterName" : "Mark Ackerson",
+  "rankPoints" : "9465",
+  "resolutionStatus" : "Resolved",
+  "ticketName" : "BQ20Z655-R1: Voltage Error",
+  "rankName" : "Genius",
+  "replies" : " 10",
+  "views" : " 46",
+  "queryText" : "Part Number: BQ20Z655-R1 Customer is bringing up 4S1P battery pack design using BQ20Z655-R1. They are seeing the voltage reading on each of the 4 cells droop in software (BQ Evaluation Software). Each cell is at 3.43V (all within 5mV). When they do a software reset (Manuf Access Code 0x41), then SW will read the appropriate voltage, but quickly droop to something like 2V on an exponential decay. Even when overriding FETs to allow 1A charge, they still see the individual cell voltages drop after a reset. They confirmed cell measurements (and at input to IC) are all consistent with 3.43V (under rest) and >3.5V charging. Customer is using BQ20Z655-R1 on 3S1P pack and it works fine. To note, they have not written the GG file yet, but am working on that now. Any guidance you can provide would be greatly appreciated! Regards, Mark",
+  "partNumber" : " BQ20Z655-R1",
+  "allResponseList" : [ {
+    "contentId" : "3294704",
+    "userName" : "Andy Liu (BMS)",
+    "rankPoints" : "42410",
+    "rankName" : "Mastermind",
+    "date" : "Mar 23, 2020 10:11 PM",
+    "userId" : "1864278",
+    "content" : "Hi Mark, Did the customer use an EVM? Did they do the calibration? Andy"
+  }, {
+    "contentId" : "3294713",
+    "userName" : "Mark Ackerson",
+    "rankPoints" : "9465",
+    "rankName" : "Genius",
+    "date" : "Mar 23, 2020 10:22 PM",
+    "userId" : "1823646",
+    "content" : "Hi Andy, Apparently EVMs are no longer available. That was our first thought. What’s the easiest method for doing the calibration? Regards, Mark"
+  }, {
+    "contentId" : "3295980",
+    "userName" : "Andy Liu (BMS)",
+    "rankPoints" : "42410",
+    "rankName" : "Mastermind",
+    "date" : "Mar 24, 2020 9:16 PM",
+    "userId" : "1864278",
+    "content" : "Hi Mark, See Section 9 of the bq20z655EVM User's Guide. Andy"
+  }, {
+    "contentId" : "3297025",
+    "userName" : "Mark Ackerson",
+    "rankPoints" : "9465",
+    "rankName" : "Genius",
+    "date" : "Mar 25, 2020 5:38 PM",
+    "userId" : "1823646",
+    "content" : "Thanks Andy!"
+  }, {
+    "contentId" : "3297032",
+    "userName" : "Mark Ackerson",
+    "rankPoints" : "9465",
+    "rankName" : "Genius",
+    "date" : "Mar 25, 2020 5:43 PM",
+    "userId" : "1823646",
+    "content" : "Hi Andy, The customer tried calibrating albeit with cells attached and monitoring the overall voltage (each cell is pretty tightly balanced). And immediately after calibration, voltages seemed okay, but again drifted apart. I’m curious how calibration might resolve the voltage decay issue. What else should we try? BQ20Z655EVM is EOL. Please advise. Thanks, Mark"
+  }, {
+    "contentId" : "3297066",
+    "userName" : "Kang Kang",
+    "rankPoints" : "17055",
+    "rankName" : "Genius",
+    "date" : "Mar 25, 2020 6:10 PM",
+    "userId" : "3528441",
+    "content" : "Hello Mark, Can the customer send a log file of the voltage drift after calibration?"
+  }, {
+    "contentId" : "3297152",
+    "userName" : "Mark Ackerson",
+    "rankPoints" : "9465",
+    "rankName" : "Genius",
+    "date" : "Mar 25, 2020 7:34 PM",
+    "userId" : "1823646",
+    "content" : "Hi Kang, Attached is the log from immediately after calibrating. Regards, Mark voltage testing.log"
+  }, {
+    "contentId" : "3297198",
+    "userName" : "Andy Liu (BMS)",
+    "rankPoints" : "42410",
+    "rankName" : "Mastermind",
+    "date" : "Mar 25, 2020 8:19 PM",
+    "userId" : "1864278",
+    "content" : "Hi Mark, I would suggest your customer try a resistor cell simulator instead of battery cells and see if the same issue still occurs. See the screenshot below. Andy"
+  }, {
+    "contentId" : "3317221",
+    "userName" : "Mark Ackerson",
+    "rankPoints" : "9465",
+    "rankName" : "Genius",
+    "date" : "Apr 15, 2020 8:11 PM",
+    "userId" : "1823646",
+    "content" : "Hi Andy, Sorry for the delay in responding. The customer tested using 10K resistors, but guessing that shouldn’t matter. What else can they try? Do you notice anything unusual in the logs? Regards, Mark"
+  }, {
+    "contentId" : "3321965",
+    "userName" : "Dominik Hartl11",
+    "rankPoints" : "35875",
+    "rankName" : "Mastermind",
+    "date" : "Apr 20, 2020 9:02 PM",
+    "userId" : "9849",
+    "content" : "I also checked the log file. Besides the voltages that drop, there isn't anything in the log that sticks out. But yes, these voltages are troublesome. Is that just on one board or is that a problem with several boards/gauges?"
+  } ],
+  "tags" : [ "/support/power-management/f/196/tags/bq20z655_2D00_r1" ],
+  "fourmType" : "TI"
+}

data/json/DLP/891082.json

@@ -0,0 +1,95 @@
+{
+  "ticketNumber" : "891082",
+  "reporterName" : "Alain Roger",
+  "rankPoints" : "60",
+  "resolutionStatus" : "",
+  "ticketName" : "BQ25703A: Reinitialization impossible to 1S-4S cell default values",
+  "rankName" : "Prodigy",
+  "replies" : " 10",
+  "views" : " 73",
+  "queryText" : "Part Number: BQ25703A Hello, I had an electronic module bq25703a working fine, but some days ago the charger would not start and no adc measurement are possible. I used to initialize the module by resetting all registers by 0x35[6] = 1, and then setting 0x05/04[15…0] = 0 to reset MaxChargeVoltage to 4S default value. After initialization, I used to charge the battery by setting 0x05/04[15…0] = 7680mV. Now everytime I send 0x05/04[15…0] = 0, the register remains at previous value non-null value set. There is no way to get 4S cell default value that is 16800 mV. I have the same problem with MinSystemVoltage 0x0D/0C which should be 12288 mV at the end of initialization. I join an history of the I2C register. During init I send one time 0x05/04[15…0] = 0 and just before end of init, 0x05/04[15…0] = 7680mV whereas it should be 16800mV. Please can you tell me if a register value may prevent the reinitialization to 4S default values after POR ? Thank you, The history of the I2C register is the following I2C register listing. From first line to «EndInit … Endinit» is the register state before entering repeatitive task. The register state is displayed another time and then only modifications are listed. At t=23:58:05.939, Vadapter is set at 5V and input is open at 23:58:52.919. 23:57:53.505 -> 0 : 1110 23:57:53.550 -> 1 : 10 23:57:53.550 -> 2 & 3 ChargeCurrentRqst : 0 mA 23:57:53.550 -> 4 & 5 ChargeVoltageRqst: 7680 mV 23:57:53.550 -> 6 : 0 23:57:53.550 -> 7 : 0 23:57:53.550 -> 8 : 0 23:57:53.550 -> 9 : 0 23:57:53.550 -> A & B minInVoltRqst: 3200 mV 23:57:53.550 -> A & B minInVoltRqst: 3200 mV 23:57:53.550 -> C & D minSystVoltRqst: 0 mV 23:57:53.550 -> C & D minSystVoltRqst: 0 mV 23:57:53.550 -> E & F maxInputCurrent: 3300 mA 23:57:53.550 -> E & F maxInputCurrent: 3300 mA 23:57:53.550 -> 20 : 0 23:57:53.550 -> 21 : 100000 23:57:53.550 -> 22 : 1 23:57:53.550 -> 23 : 0 23:57:53.550 -> 24 : 0 23:57:53.550 -> 25 inputCurrentDPM: 3300 mA 23:57:53.550 -> 26 : 0 23:57:53.550 -> 27 inputVoltMeas: 3200 mV 23:57:53.550 -> 28 dischrgCurrentMeas: 0 mA 23:57:53.550 -> 29 chrgCurrentMeas: 0 mA 23:57:53.550 -> 2A : 0 23:57:53.550 -> 2B inputCurrentMeas: 0 mA 23:57:53.550 -> 2C battVoltMeas: 2880 mV 23:57:53.550 -> 2D systVoltMeas: 3200 mV 23:57:53.550 -> 2E : 1000000 23:57:53.550 -> 2F : 1111000 23:57:53.550 -> 30 : 0 23:57:53.550 -> 31 : 10 23:57:53.550 -> 32 : 1110010 23:57:53.550 -> 33 : 10 23:57:53.550 -> 34 : 0 23:57:53.550 -> 35 : 0 23:57:53.550 -> 36 : 111100 23:57:53.550 -> 37 : 1001010 23:57:53.550 -> 38 : 0 23:57:53.550 -> 39 : 10000001 23:57:53.550 -> 3A : 11111111 23:57:53.550 -> 3B : 10100000 23:57:53.550 -> bq25703a digout: not_proc_hot/ChrgOK : 0 23:57:53.550 -> EndInit EndInit EndInit EndInit EndInit EndInit EndInit 23:57:53.781 -> 0 : 1110 23:57:53.781 -> 1 : 10 23:57:53.781 -> 2 & 3 ChargeCurrentRqst : 0 mA 23:57:53.781 -> 4 & 5 ChargeVoltageRqst: 7680 mV 23:57:53.781 -> 6 : 0 23:57:53.781 -> 7 : 0 23:57:53.781 -> 8 : 0 23:57:53.781 -> 9 : 0 23:57:53.781 -> A & B minInVoltRqst: 3200 mV 23:57:53.781 -> A & B minInVoltRqst: 3200 mV 23:57:53.781 -> C & D minSystVoltRqst: 0 mV 23:57:53.781 -> C & D minSystVoltRqst: 0 mV 23:57:53.781 -> E & F maxInputCurrent: 3300 mA 23:57:53.781 -> E & F maxInputCurrent: 3300 mA 23:57:53.781 -> 20 : 0 23:57:53.781 -> 21 : 100000 23:57:53.781 -> 22 : 0 23:57:53.781 -> 23 : 0 23:57:53.781 -> 24 : 0 23:57:53.781 -> 25 inputCurrentDPM: 3300 mA 23:57:53.781 -> 26 : 0 23:57:53.781 -> 27 inputVoltMeas: 3200 mV 23:57:53.781 -> 28 dischrgCurrentMeas: 0 mA 23:57:53.781 -> 29 chrgCurrentMeas: 0 mA 23:57:53.781 -> 2A : 0 23:57:53.781 -> 2B inputCurrentMeas: 0 mA 23:57:53.781 -> 2C battVoltMeas: 2880 mV 23:57:53.781 -> 2D systVoltMeas: 3200 mV 23:57:53.781 -> 2E : 1000000 23:57:53.781 -> 2F : 1111000 23:57:53.781 -> 30 : 0 23:57:53.781 -> 31 : 10 23:57:53.781 -> 32 : 1110010 23:57:53.781 -> 33 : 10 23:57:53.781 -> 34 : 0 23:57:53.781 -> 35 : 0 23:57:53.781 -> 36 : 111100 23:57:53.781 -> 37 : 1001010 23:57:53.781 -> 38 : 0 23:57:53.781 -> 39 : 10000001 23:57:53.781 -> 3A : 11111111 23:57:53.781 -> 3B : 10100000 23:58:05.839 -> 31 : 10 23:58:05.839 -> 32 : 1110010 23:58:05.839 -> 33 : 10 23:58:05.839 -> 34 : 0 23:58:05.839 -> 35 : 0 23:58:05.839 -> 36 : 111100 23:58:05.839 -> 37 : 1001010 23:58:05.839 -> 38 : 0 23:58:05.839 -> 39 : 10000001 23:58:05.839 -> 3A : 11111111 23:58:05.839 -> 3B : 10100000 23:58:05.839 -> 31 : 10 23:58:05.839 -> 32 : 1110010 23:58:05.839 -> 33 : 10 23:58:05.839 -> 34 : 0 23:58:05.839 -> 35 : 0 23:58:05.839 -> 36 : 111100 23:58:05.839 -> 37 : 1001010 23:58:05.839 -> 38 : 0 23:58:05.839 -> 39 : 10000001 23:58:05.839 -> 3A : 11111111 23:58:05.839 -> 3B : 10100000 23:58:05.939 -> 21 : 10100000 23:58:05.939 -> bq25703a digout: not_proc_hot/ChrgOK : 1 23:58:06.072 -> C & D minSystVoltRqst: 1280 mV 23:58:06.105 -> E & F maxInputCurrent: 1150 mA 23:58:06.105 -> 25 inputCurrentDPM: 1150 mA 23:58:06.837 -> 3B : 11100000 23:58:12.359 -> 2 & 3 ChargeCurrentRqst : 64 mA 23:58:15.560 -> 2 & 3 ChargeCurrentRqst : 128 mA 23:58:52.919 -> 21 : 100000 23:58:52.919 -> 25 inputCurrentDPM: 3300 mA 23:58:52.919 -> bq25703a digout: not_proc_hot/ChrgOK : 0 23:58:53.085 -> 2 & 3 ChargeCurrentRqst : 0 mA 23:58:53.085 -> E & F maxInputCurrent: 3300 mA",
+  "partNumber" : " BQ25703A",
+  "allResponseList" : [ {
+    "contentId" : "3295810",
+    "userName" : "Joel Hernandez II",
+    "rankPoints" : "25800",
+    "rankName" : "Mastermind",
+    "date" : "Mar 24, 2020 6:07 PM",
+    "userId" : "4615895",
+    "content" : "Hey Alain, Does this happen on every charger you have, or just on this single device? Does it no longer respond to any of your I2C commands? Or can you still write a sequence, but all subsequent commands are ignored? Regards, Joel H"
+  }, {
+    "contentId" : "3296065",
+    "userName" : "Alain Roger",
+    "rankPoints" : "60",
+    "rankName" : "Prodigy",
+    "date" : "Mar 24, 2020 11:39 PM",
+    "userId" : "6152039",
+    "content" : "Hello, The problem happens on my prototype, it is a single device before producing some more. All commands sent to the bq25703a seem to be correctly set when they are read back, except the commands that should get default values according 1S-4S cell configuration : MinSystemVoltage 0x0D/0x0C and MaxChargeVoltage 0x05/0x04 after POR. Also when I command 0x05/0x04 = 0, it should « set REG0x05/04() to default value on CELL_BATPRESZ pin» but in fact the register keeps previous value. Then there is no charging whereas 21[7] gets to 1 as Vbus get above 3.2V, 0x0F/0x0E is set to 1150 mA and 0x05/0x04 is set to 7680 mV. Also 0x3B[6] set to 1 does not start any adc measurement. I am wondering if there are some register commands that force to ignore CELL_BATPRESZ pin, so no reinitialization to CELL_BATPRESZ default values are possible ?"
+  }, {
+    "contentId" : "3298023",
+    "userName" : "Joel Hernandez II",
+    "rankPoints" : "25800",
+    "rankName" : "Mastermind",
+    "date" : "Mar 26, 2020 2:20 PM",
+    "userId" : "4615895",
+    "content" : "Hey Alain, If you write the RESET_REG bit in ChargeOption3() bit 6, do the values return to their default state? I also wonder if any functions of the charger are operating. Do you have as schematic you can provide of your board? What do you do to POR the charger? Do you remove both VBUS and VBAT? Regards, Joel H"
+  }, {
+    "contentId" : "3298376",
+    "userName" : "Alain Roger",
+    "rankPoints" : "60",
+    "rankName" : "Prodigy",
+    "date" : "Mar 26, 2020 6:53 PM",
+    "userId" : "6152039",
+    "content" : "Hello, In order to perform a POR, I remove first VBUS and then VBAT. Then when I want to use again the converter, I start to plug VBAT and I wait a little before plugging in VBUS. I did try to restart the bq25703a and then 13s later I plug VBUS and then I sent a RESET_REG 1 minute later. I did also another test : I restart the bq25703a and then 1 minute and a half later I send a RESET_REG. In both cases, register 0x01, 0x30, 0x32, 0x36, 0x38, 0x3A and 0x3B get updated to default values. But 0x05/04[15…0] MaxChargeVoltage and 0x0D/0x0C MinSystemVoltage do not get default values. I join you the I2C evolution of both experiments, and also a schematic I did for the module. I hope it may help, Vincent ResetWhileNotCharging.txtResetWhileCharging.txt"
+  }, {
+    "contentId" : "3299335",
+    "userName" : "Joel Hernandez II",
+    "rankPoints" : "25800",
+    "rankName" : "Mastermind",
+    "date" : "Mar 27, 2020 3:23 PM",
+    "userId" : "4615895",
+    "content" : "hey Alain, I noticed in your register dumps that you set VSYSMIN to 0mV during your initialization. And I also notice you don't read 0x20 later in the register dump, only 0x21. I have a suspicion that your 0mV is tripping the SYS SHORT protection, and preventing those two reigsters from being set. Additionally, I would have you compare your schematic against our checklist here in this FAQ: Regards, Joel H"
+  }, {
+    "contentId" : "3299506",
+    "userName" : "Alain Roger",
+    "rankPoints" : "60",
+    "rankName" : "Prodigy",
+    "date" : "Mar 27, 2020 5:49 PM",
+    "userId" : "6152039",
+    "content" : "Hello, Thanks for your remark. I was not initializing at all VSYSMIN at start but now I tried to set it to 4352mV and also to 12544mV (batteries are at 6.3 V, 5 NIMH cells). The charger did not start, I join the register dumps for 4352mV. It is the same sequence for 12544 mV. I could see that when a RESET_REG is done, the VSYSMIN is set to 0V. After initialization I read once all registers, then I display every register changes. 0x21 changes as soon as CHRG_OK 0x21[7] is set to 1 or reset to 0. No status error appear so 0x20 remain to latest display value, 0. ResetWhileChargingMinSys4352.txt"
+  }, {
+    "contentId" : "3310681",
+    "userName" : "Alain Roger",
+    "rankPoints" : "60",
+    "rankName" : "Prodigy",
+    "date" : "Apr 8, 2020 5:56 PM",
+    "userId" : "6152039",
+    "content" : "Hello, I write back because I do not understand why the charger is not working. I do not know why the ADC measurement does not start after I set register 3B : 0b11100000, and 3A : 11111111. I know that could happen if I was in low power mode (REG0x01[7] = 1), but my register 0x01 is 0b00000010. Do anyone would have a reason why the measurement ADC is not launched ? Thank you,"
+  }, {
+    "contentId" : "3316168",
+    "userName" : "Tiger Zhou",
+    "rankPoints" : "610",
+    "rankName" : "Prodigy",
+    "date" : "Apr 15, 2020 4:00 AM",
+    "userId" : "1451791",
+    "content" : "Hi, Alain, This is weird, especially it worked previously. I checked your register settings, didn't see any unusual. Could you check if Vin, REGN, ILIM-HIZ and CELL-BATPRESZ voltage in the range?"
+  }, {
+    "contentId" : "3328060",
+    "userName" : "Alain Roger",
+    "rankPoints" : "60",
+    "rankName" : "Prodigy",
+    "date" : "Apr 26, 2020 10:29 AM",
+    "userId" : "6152039",
+    "content" : "Hello, I could perform measurements on REGN and CELL-BATPRESZ, with 4 NiMH batteries plugged via Batfet. Then I set Vin to 4.98V, so I get pin CHRG_OK turning on. At that moment, no measurement are launched while I have registers 3A : 11111111 & 3B : 11100000. In those conditions, I measure REGN pin voltage and I get less than 50mV, far from the 6V LDO announced in the datasheet. Then I measure CELL-BATPRESZ and I get nearly 0V, very lower with regards to the Vdda voltage that should be a few volts. This Vdda is also near 0V. The register 0x32[7] is set to 1 in order to disable ILIM_HIZ pin, so I use to set it to GND. Even when I set it higher than 4.0V, the adc converters do not start and I still have same voltage values for REGN, CELL-BATPRESZ and Vdda. I suppose the LDO is blown out, what do you think ? Vincent,20200426_RegisterHistory.txt"
+  }, {
+    "contentId" : "3329519",
+    "userName" : "Tiger Zhou",
+    "rankPoints" : "610",
+    "rankName" : "Prodigy",
+    "date" : "Apr 27, 2020 9:15 PM",
+    "userId" : "1451791",
+    "content" : "Hi, Alain, That is what I worried. REGN is the most important voltage for the function of BQ25703A. It provides the gate drive current as well as the power for VDDA rail. It looks to me the part was damaged during the troubleshooting. Please replace the IC or work on a new prototype."
+  } ],
+  "tags" : [ "/support/power-management/f/196/tags/BQ25703A" ],
+  "fourmType" : "TI"
+}

data/json/DLP/891226.json

@@ -0,0 +1,31 @@
+{
+  "ticketNumber" : "891226",
+  "reporterName" : "James Zhan",
+  "rankPoints" : "1755",
+  "resolutionStatus" : "TI Thinks Resolved",
+  "ticketName" : "BQ24773: BATPRES PIN connection",
+  "rankName" : "Intellectual",
+  "replies" : " 2",
+  "views" : " 28",
+  "queryText" : "Part Number: BQ24773 Hi team, According to the datasheet, the PIN 15 of BQ24773 \"BATPRES\" is input signal PIN, but in the EVM I've found it seems to be output PIN. If customer want to connect this pin to the MCU to indicate whether if the battery is present, how should they do? Thanks.",
+  "partNumber" : " BQ24773",
+  "allResponseList" : [ {
+    "contentId" : "3295447",
+    "userName" : "Steve Preissig",
+    "rankPoints" : "4610",
+    "rankName" : "Expert",
+    "date" : "Mar 24, 2020 1:53 PM",
+    "userId" : "8914",
+    "content" : "Hello James, The /BATPRES signal on BQ2477x is always an input signal. The reason that it behaves like an output signal on the EVM is because there is an external comparator (U2) that generates a /BATPRES signal from the battery voltage. If the battery pack your customer is using does not have a signal that can be connected to the MCU for this purpose, then an external comparator such as used on the EVM can be used. Note that the BQ2477x also has an independent comparator that can be used to detect battery presence as well. You can refer to the BQ24780s EVM for an example of how the independent comparator can be used instead of an external comparator, saving cost and board space. (BQ24780s EVM has an external comparator as well, but there are jumper options to select between using the external comparator or independent comparator for /BATPRES) Regards, Steve"
+  }, {
+    "contentId" : "3323912",
+    "userName" : "James Zhan",
+    "rankPoints" : "1755",
+    "rankName" : "Intellectual",
+    "date" : "Apr 22, 2020 7:27 AM",
+    "userId" : "5039519",
+    "content" : "Hi Steve, Thanks for the comments. I have more questions as below: 1. Is PIN 15 BATPRES the only way to detect if battery present in BQ24773? could we just read one of the register and get this information? 2. Could we left BATPRES PIN open, not connecting to anything? Would this has any risk? Please let me know if you have any ideas, thanks!"
+  } ],
+  "tags" : [ "/support/power-management/f/196/tags/BQ24773" ],
+  "fourmType" : "TI"
+}

data/json/DLP/891261.json

@@ -0,0 +1,39 @@
+{
+  "ticketNumber" : "891261",
+  "reporterName" : "Michiaki Tanii",
+  "rankPoints" : "1600",
+  "resolutionStatus" : "TI Thinks Resolved",
+  "ticketName" : "TL494: Frequency configuration",
+  "rankName" : "Intellectual",
+  "replies" : " 3",
+  "views" : " 27",
+  "queryText" : "Part Number: TL494 Hi Referring 9.3.2 Oscillator, the equation is f = 1/(RT x CT) but TYP frequency is 10kHz at CT = 0.01uF, RT = 12k ohm in the 7.6 Electrical Characteristics, Oscillator Section. Could you kindly advise how customer should consider the frequency configuration ? Thank you and best regards, Michiaki",
+  "partNumber" : " TL494",
+  "allResponseList" : [ {
+    "contentId" : "3296841",
+    "userName" : "John Griffin1",
+    "rankPoints" : "32175",
+    "rankName" : "Mastermind",
+    "date" : "Mar 25, 2020 3:45 PM",
+    "userId" : "1693693",
+    "content" : "Hello Michiaki, This is some anomaly in the datasheet that goes all through revisions from Rev A to the present Rev H. Please use the curves in Figure 1 or the equation 3 in the datasheet to calculate the oscillator frequency. Thank you for pointing out this anomaly and I will try to find out why the test circuit uses a 12k resistor for Rt instead of a 10k. Regards John"
+  }, {
+    "contentId" : "3320709",
+    "userName" : "Michiaki Tanii",
+    "rankPoints" : "1600",
+    "rankName" : "Intellectual",
+    "date" : "Apr 20, 2020 4:12 AM",
+    "userId" : "6119109",
+    "content" : "Hi John, > I will try to find out why the test circuit uses a 12k resistor for Rt instead of a 10k. Regarding on the above, could you kindly update latest situation ? Thank you and best regards, Michiaki"
+  }, {
+    "contentId" : "3322914",
+    "userName" : "John Griffin1",
+    "rankPoints" : "32175",
+    "rankName" : "Mastermind",
+    "date" : "Apr 21, 2020 2:12 PM",
+    "userId" : "1693693",
+    "content" : "Hello Michiaki, I will let you know when I have an update Regards John"
+  } ],
+  "tags" : [ "/support/power-management/f/196/tags/TL494" ],
+  "fourmType" : "TI"
+}

data/json/DLP/891457.json

@@ -0,0 +1,95 @@
+{
+  "ticketNumber" : "891457",
+  "reporterName" : "Igor Leal",
+  "rankPoints" : "100",
+  "resolutionStatus" : "TI Thinks Resolved",
+  "ticketName" : "TPS62745: TPS62745",
+  "rankName" : "Prodigy",
+  "replies" : " 19",
+  "views" : " 85",
+  "queryText" : "Part Number: TPS62745 Hello, We are facing similar situation. Vsel was connected to Vin (design error), powered by batteries higher than 6V and some devices are damaged. Would be possible to share the squematic internally and go deeper on the severity of this problem? Thanks in advance. BRs,",
+  "partNumber" : " TPS62745",
+  "allResponseList" : [ {
+    "contentId" : "3296082",
+    "userName" : "JohnTucker",
+    "rankPoints" : "189830",
+    "rankName" : "Guru",
+    "date" : "Mar 25, 2020 12:11 AM",
+    "userId" : "24596",
+    "content" : "Igor, It is probably difficult at this time. We can only recommend that teh abs max rating be observed. I will contact our design team about internal details. For sure it will require an NDA to share any details."
+  }, {
+    "contentId" : "3297026",
+    "userName" : "JohnTucker",
+    "rankPoints" : "189830",
+    "rankName" : "Guru",
+    "date" : "Mar 25, 2020 5:39 PM",
+    "userId" : "24596",
+    "content" : "Igor, These pins connect two to pieces of internal circuitry: 5V ESD clamp, and inputs of 5V CMOS logic gates running on an internal rail. The obvious mechanisms of damage that I can foresee from over-voltage on these pins include: · Damage to pin metallization or ESD clamp due to triggering of ESD cell. This could cause functional issues with the VSEL signaling, as well as other possible issues if reflowed metal shorts to nearby circuitry. This type of failure would be immediate when the overstress occurs. In my estimation the risk of this kind of failure is low if the pin voltage stays below 7V, since the nominal trigger point for the ESD clamp is above 11V. · Damage to the gate oxide of the ESD cell or the CMOS logic gates. This could cause functional issues with the VSEL signaling, as well as other possible issues if the high current flowing through the failed oxide loaded down the internal rail or caused reflowed metal shorts to nearby circuitry. This type of failure has increasing probability of occurring as the time of exposure to over-stress increases. The risk for this failure is also low if the pin voltage stays below 7V. Our model for this kind of failure mechanism predicts less than 1 failed unit per billion after 100k operating hours at the worst case temp of 150C as long as the voltage never exceeds 7V (including transients, ringing, etc). Of course, this assessment should not be taken as any kind of guarantee of results for the customer. I have considered the most apparent mechanisms of failure under this application’s conditions, but this kind of analysis isn’t foolproof. It’s possible that there could be another mechanism or issue that I have not caught, which is why we qualify and specify the components and circuits within a given range. That more rigorous process yielded the abs max specs that are being violated."
+  }, {
+    "contentId" : "3297782",
+    "userName" : "Igor Leal",
+    "rankPoints" : "100",
+    "rankName" : "Prodigy",
+    "date" : "Mar 26, 2020 10:11 AM",
+    "userId" : "4146277",
+    "content" : "Thanks for your complete and so deep reply John. It seems that our board don´t have to face many problems working below 7V (maximum 1 per billion). After your answer, we have tested today 200 boards, just connecting 6,3 V Lithium battery, and 28 units are damaged, so current consumption increases 10-100 times. After changing TPS62745 regulator it works fine returning to the normal current consumption. So, do you think there is another possible problem, maybe on our schematic? Or could be possible to be a batch problem on these regulator, I don´t think so, but do you have any information about it? Thanks in advance."
+  }, {
+    "contentId" : "3302378",
+    "userName" : "JohnTucker",
+    "rankPoints" : "189830",
+    "rankName" : "Guru",
+    "date" : "Mar 31, 2020 5:09 PM",
+    "userId" : "24596",
+    "content" : "Igor, There are no lot quality issues that I am aware of."
+  }, {
+    "contentId" : "3303352",
+    "userName" : "Igor Leal",
+    "rankPoints" : "100",
+    "rankName" : "Prodigy",
+    "date" : "Apr 1, 2020 11:35 AM",
+    "userId" : "4146277",
+    "content" : "Hello John, Thanks for your answer. So, if we are working under any probed specifications, there is no explanation for having to replace your regulators on some of our devices in order to work properly. If you are able we can share our schematic with you, maybe there is something wrong that we cannot detect. BRs,"
+  }, {
+    "contentId" : "3303424",
+    "userName" : "JohnTucker",
+    "rankPoints" : "189830",
+    "rankName" : "Guru",
+    "date" : "Apr 1, 2020 12:48 PM",
+    "userId" : "24596",
+    "content" : "Igor, if you post your schematic, I will review it."
+  }, {
+    "contentId" : "3303792",
+    "userName" : "Igor Leal",
+    "rankPoints" : "100",
+    "rankName" : "Prodigy",
+    "date" : "Apr 1, 2020 4:31 PM",
+    "userId" : "4146277",
+    "content" : "Hello John, Attached you can find schematic referred to TPS62745. Where D1, D2 and T4 are not mounted. So J2-battery power go directly to R2 0 ohm. 6V lithium battery is connected to J2 in normal activity (initially 6,5 V). In parallel 3V3 are applied to Vout from TC1 connector when device is programming. Sometimes could be 3,4 - 3,5 V. Can you see any issue on that schematic? Thanks in advance. BRs,"
+  }, {
+    "contentId" : "3303826",
+    "userName" : "JohnTucker",
+    "rankPoints" : "189830",
+    "rankName" : "Guru",
+    "date" : "Apr 1, 2020 4:51 PM",
+    "userId" : "24596",
+    "content" : "Igor, If you apply an external 3.3 V to the output of the TPS62745, and the battery is not connected the high side body diode can conduct and you may possibly have enough voltage at the input to allow the device to start switching. Can you check it in that condition?"
+  }, {
+    "contentId" : "3315097",
+    "userName" : "Igor Leal",
+    "rankPoints" : "100",
+    "rankName" : "Prodigy",
+    "date" : "Apr 14, 2020 10:40 AM",
+    "userId" : "4146277",
+    "content" : "Hello John, I have checked what you said and there are 0,25 V on the high side body diode along the range of 2-4V applied externally on Vout / SW pins. So, in normal situation, when we apply external 3,3 V at the V output we have 3,05 V at Vin pin. If we apply external 3,4 --> 3,15 V at Vin If we apply external 3,5 --> 3,25 V at Vin So, it could be a problem to damage the chip? Thanks BRs, Igor"
+  }, {
+    "contentId" : "3315245",
+    "userName" : "JohnTucker",
+    "rankPoints" : "189830",
+    "rankName" : "Guru",
+    "date" : "Apr 14, 2020 1:13 PM",
+    "userId" : "24596",
+    "content" : "Igor, Do you see any switching activity on the SW pin? Is EN tied low?"
+  } ],
+  "tags" : [ "/support/power-management/f/196/tags/TPS62745" ],
+  "fourmType" : "TI"
+}

data/json/DLP/891745.json

@@ -0,0 +1,23 @@
+{
+  "ticketNumber" : "891745",
+  "reporterName" : "Brett Colteaux",
+  "rankPoints" : "1795",
+  "resolutionStatus" : "Resolved",
+  "ticketName" : "[FAQ] Do you have any guidance as to how I should choose my PoE PD IC?",
+  "rankName" : "Intellectual",
+  "replies" : " 1",
+  "views" : " 152",
+  "queryText" : "Do you have any guidance as to how I should choose my PoE PD IC?",
+  "partNumber" : "NA",
+  "allResponseList" : [ {
+    "contentId" : "3296902",
+    "userName" : "Brett Colteaux",
+    "rankPoints" : "1795",
+    "rankName" : "Intellectual",
+    "date" : "Mar 25, 2020 4:20 PM",
+    "userId" : "4406190",
+    "content" : "Great question! Please see the below flowchart that provides general guidance as to how to choose one of TI's PoE PD ICs: Best Regards, Brett Colteaux PoE Product Marketing Engineer"
+  } ],
+  "tags" : [ "/support/power-management/f/196/tags/PoE" ],
+  "fourmType" : "TI"
+}

data/json/DLP/892345.json

@@ -0,0 +1,95 @@
+{
+  "ticketNumber" : "892345",
+  "reporterName" : "Daniel Matterson",
+  "rankPoints" : "30",
+  "resolutionStatus" : "TI Thinks Resolved",
+  "ticketName" : "LM5066IEVM-626: UVLO Gate Masking Behaviour",
+  "rankName" : "Prodigy",
+  "replies" : " 10",
+  "views" : " 66",
+  "queryText" : "Part Number: LM5066IEVM-626 Hi, We seem to be experiencing some unexpected behaviour with the above part: We have tied UVLO/EN to GND to ensure the mosfet defaults off when the device is powered up. In order to turn on the mosfet, we are gate masking the UVLO which works as expected. However, we are now seeing that the OC/OP protection is not latching off. We do not believe the culprit is !RETRY since we have it tied to VCC and the device is configured to use pin cfg for RETRY. Mosfet switches off when there is a short or OC, but immediately turns back on when short or load is removed. Can anyone explain this behaviour? Is the masking of UVLO and connecting it to GND causing faults to be unintentionally reset and the mosfet switched back on? Daniel",
+  "partNumber" : " LM5066IEVM-626",
+  "allResponseList" : [ {
+    "contentId" : "3299116",
+    "userName" : "Rakesh",
+    "rankPoints" : "39750",
+    "rankName" : "Mastermind",
+    "date" : "Mar 27, 2020 12:35 PM",
+    "userId" : "4743883",
+    "content" : "Hi Daniel, Thanks for reaching out! I will go through the above one and get back early next week. Hope this is fine for you. Best Regards, Rakesh"
+  }, {
+    "contentId" : "3300051",
+    "userName" : "Rakesh",
+    "rankPoints" : "39750",
+    "rankName" : "Mastermind",
+    "date" : "Mar 29, 2020 11:03 AM",
+    "userId" : "4743883",
+    "content" : "Hi Daniel, Masking the GATE for any fault event will reset the GATE. It should be avoided in normal operation. Caution: Enabling gate masking may result in pass FET damage during fault conditions. Gate masking should only be used during system debugging. Let us know if there are any followup questions. Best Regards, Rakesh"
+  }, {
+    "contentId" : "3308659",
+    "userName" : "Daniel Matterson",
+    "rankPoints" : "30",
+    "rankName" : "Prodigy",
+    "date" : "Apr 7, 2020 8:56 AM",
+    "userId" : "6127359",
+    "content" : "Hi Rakesh, Just to confirm what you mean: By masking the GATE for any fault event - will this reset the gate repeatedly or only once when masked? The reason I ask is because we are experiencing some undocumented behaviour. By keeping UVLO tied low and gate masking the fault, the LM5066I repeatedly retries to turn on the mosfet after 1 timer timeout (20ms period on the EVAL board). This leads to what I said earlier - any fault condition is not latched (i.e. OC or OP). A completely different set of behaviour is experienced when using the OLVO fault to ensure the mosfet is off at power up, by connecting OVLO to Vcc. In this case, when the OVLO fault is masked, OC and OP faults thereafter are in fact latched and the mosfet is not repeatedly turned on. I have attached scope traces showing the gate and timer pin behaviour for both cases during a short circuit. Can you explain to me why there is a difference in behaviour between masking UVLO and OVLO, and why when masking the UVLO fault, it repeatedly resets all faults and prevents latching? Kind Regards Daniel UVLO Gate Masked (and tied low), Retries set to 0: UVLO Gate Masked (and tied low), Retries set to Infinite: OVLO Gate Masked (and tied high), Retries set to 0:"
+  }, {
+    "contentId" : "3309824",
+    "userName" : "Rakesh",
+    "rankPoints" : "39750",
+    "rankName" : "Mastermind",
+    "date" : "Apr 8, 2020 3:18 AM",
+    "userId" : "4743883",
+    "content" : "Hi Daniel, This is not the common use case in general. Can you help us understand the purpose of GATE masking in your system. This would help our designers to analyze the issue as we don't have much validation details for this rare use case. Best Regards, Rakesh"
+  }, {
+    "contentId" : "3310178",
+    "userName" : "Daniel Matterson",
+    "rankPoints" : "30",
+    "rankName" : "Prodigy",
+    "date" : "Apr 8, 2020 10:53 AM",
+    "userId" : "6127359",
+    "content" : "Hi Rakesh, We are trying to ensure that the mosfet is off at power up. To do so we tie UVLO low, then when configuring the LM5066I, the UVLO fault can be gate masked and the rest of the hotswap functionality is as expected. But by doing it this way we lose the latching functionality of the OC and OP faults. An alternative method is to tie OVLO high and gate mask it. This does not prevent the OC and OP fault from latching and the hotswap controller functions as expected. Is this the best way to achieve our requirement of ensuring the mosfet is off at power up? Can you recommend another method? Kind Regards Daniel"
+  }, {
+    "contentId" : "3310477",
+    "userName" : "Rakesh",
+    "rankPoints" : "39750",
+    "rankName" : "Mastermind",
+    "date" : "Apr 8, 2020 3:21 PM",
+    "userId" : "4743883",
+    "content" : "Hi Daniel, One way is to pull the UVLO/EN pin LOW as shown in Figure-16 in the datasheet The other method is to issue OPERATION command 00h immediately after powerup (before the insertion time expires, refer Figure 13) to keep the system in disable state. These two are widely used and proven methods. Best Regards, Rakesh"
+  }, {
+    "contentId" : "3313416",
+    "userName" : "Rakesh",
+    "rankPoints" : "39750",
+    "rankName" : "Mastermind",
+    "date" : "Apr 13, 2020 7:46 AM",
+    "userId" : "4743883",
+    "content" : "Hi Daniel, Do you have any followup questions.? Best Regards, Rakesh"
+  }, {
+    "contentId" : "3315105",
+    "userName" : "A John",
+    "rankPoints" : "10",
+    "rankName" : "Prodigy",
+    "date" : "Apr 14, 2020 10:51 AM",
+    "userId" : "6324258",
+    "content" : "Hi Rakesh, Background: I can provide a bit more background. We are using the LM5066 to provide soft-start, short circuit protection, & diagnostic functionality on several power outputs (16 outputs). As Daniel mentioned we want these outputs to be off on startup. Hence artificially causing a lockout with UVLO/EN then masking the error once we have software control. An additional complication is these LM5066 are on different electrically isolated sections. I2C control is very convenient as it only requires 2 signals to cross isolation. Finally we are using the dV/dT startup configuration to allow large capacitance to be turned ON but with a fast fault timer in case of problems (Fault = 0.5ms) Problem: The fault mask register provides the ability to mask individual errors. Table 33 list all the errors which can be individually masked. It has undocumented effect on the UVLO/EN pin, this pin affects ALL faults including the overcurrent AND circuit breaker faults. Internally it appears to clear the fault in a way that makes the system detect an EN toggle (which clears all faults). e.g the mask affects both UVLO and EN part of the UVLO/EN signal internally. OVLO fault masking appears to work more as intended and only affects itself. Keeping MOSFET OFF at TurnON Optionscompany Suggestion: One way is to pull the UVLO/EN pin LOW as shown in Figure-16 in the datasheet Our Comment: We are doing that by keeping UVLO tied low. Unfortunately we cannot release it as per figure 16 since that would require an additional signal to cross electrical isolation, for each LM5066. (we are using 16).company Suggestion:The other method is to issue OPERATION command 00h immediately after powerup. Our Comment: Good idea, we did not consider this. Timing constraints will very tight as our 10nF timer capacitor would give us about 7.8ms startup time. Realistically i dont think we can guarantee having communicated to all LM5066 with-in that time 7ms. Follow Up Question: 1. Would you be in a position to confirm the exact behaviour of the UVLO/EN mask and how it affects all other faults? 2. With UVLO masked it appears to clear ALL faults either every ~100ms or ~20ms depending on the retry setting(retry, or not) but we have been unable to relate either time to the timer capacitor setting. Is it a hard-coded internal retry period? 3. Able to confirm this issue is confined to the UVLO/EN fault and that OVLO will work as documented?"
+  }, {
+    "contentId" : "3316856",
+    "userName" : "Rakesh",
+    "rankPoints" : "39750",
+    "rankName" : "Mastermind",
+    "date" : "Apr 15, 2020 3:18 PM",
+    "userId" : "4743883",
+    "content" : "Hi Daniel, John, I understood the challenges in using the UVLO/EN pin for control or the OPERATION command 00h in your system. I need to verify the behavior and discuss with our design team to find the root-cause. Please allow some time. Best Regards, Rakesh"
+  }, {
+    "contentId" : "3325222",
+    "userName" : "Rakesh",
+    "rankPoints" : "39750",
+    "rankName" : "Mastermind",
+    "date" : "Apr 23, 2020 4:57 AM",
+    "userId" : "4743883",
+    "content" : "Hi Daniel, John, I am yet to visit lab for bench verification. How critical is it at your end ? Have you explored any alternate ways to realize this function at your system level ? I just want to inform you that I can make some progress in the next week. Best Regards, Rakesh"
+  } ],
+  "tags" : [ "/support/power-management/f/196/tags/LM5066IEVM_2D00_626" ],
+  "fourmType" : "TI"
+}

data/json/DLP/892352.json

@@ -0,0 +1,47 @@
+{
+  "ticketNumber" : "892352",
+  "reporterName" : "Betty Guo",
+  "rankPoints" : "3070",
+  "resolutionStatus" : "Resolved",
+  "ticketName" : "TPS23755: start current of TPS23755",
+  "rankName" : "Expert",
+  "replies" : " 4",
+  "views" : " 31",
+  "queryText" : "Part Number: TPS23755 Hi team, we want to check how much the startup current? I find that TPS23755 use advance startup, and integrate the current source.",
+  "partNumber" : " TPS23755",
+  "allResponseList" : [ {
+    "contentId" : "3299730",
+    "userName" : "Michael Pahl",
+    "rankPoints" : "4915",
+    "rankName" : "Expert",
+    "date" : "Mar 27, 2020 10:27 PM",
+    "userId" : "6102321",
+    "content" : "Hello Betty, The EVM has a startup waveform that shows the input current on page 6: That will include the current used in advanced startup. If this post answers your question, please indicate so by marking this thread as resolved. Thank you. Regards, Michael P. Applications Engineer customer organization"
+  }, {
+    "contentId" : "3300156",
+    "userName" : "Betty Guo",
+    "rankPoints" : "3070",
+    "rankName" : "Expert",
+    "date" : "Mar 30, 2020 1:35 AM",
+    "userId" : "5039529",
+    "content" : "hi Michael, I sitll not clear about the startup current. In the page 6, the Iin is the startup current,right? And, why it have a step and then spike? The startup current is less than 50mA?"
+  }, {
+    "contentId" : "3301057",
+    "userName" : "Michael Pahl",
+    "rankPoints" : "4915",
+    "rankName" : "Expert",
+    "date" : "Mar 30, 2020 5:21 PM",
+    "userId" : "6102321",
+    "content" : "Betty, The current shown in page 6 is the input current for the board. This will include the current in the startup circuit. Or, are you needing the specific current associated with the internal current source? If so, why is that number needed versus the overall input current required? The large current spike is inrush, which is limited by the IC. If this post answers your question, please indicate so by marking this thread as resolved. Thank you. Regards, Michael P. Applications Engineer customer organization"
+  }, {
+    "contentId" : "3324520",
+    "userName" : "Michael Pahl",
+    "rankPoints" : "4915",
+    "rankName" : "Expert",
+    "date" : "Apr 22, 2020 3:30 PM",
+    "userId" : "6102321",
+    "content" : "Hello, This thread has been inactive for many weeks now. I am going to close it, but feel free to reopen it or start a new thread. Thank you. Regards, Michael Pahl"
+  } ],
+  "tags" : [ "/support/power-management/f/196/tags/TPS23755" ],
+  "fourmType" : "TI"
+}

data/json/DLP/892440.json

@@ -0,0 +1,63 @@
+{
+  "ticketNumber" : "892440",
+  "reporterName" : "Maulin Lodhia",
+  "rankPoints" : "380",
+  "resolutionStatus" : "TI Thinks Resolved",
+  "ticketName" : "BQ35100: Flash stream file parsing fails on a comapare, resulting in bricked bq35100 chip",
+  "rankName" : "Intellectual",
+  "replies" : " 6",
+  "views" : " 55",
+  "queryText" : "Part Number: BQ35100 Hello, We have implemented flash stream parser based on the code described in slua801. we tested the parser and it parses the flash stream file as per specifications (flash stream specification file attached1856.Flash Stream File Format.pdf). During our tests with the bq35100 device we found that firmware revision that was read and compared against a known value was failing. When using bqstudio reading of ID and version was working correctly. In order to do the same with flash streamer file to read id and fimware version, we had to add 100ms delay after i2cwrite command (see below routine). char *BQ35100_execute_fs(char *pFS)\n{\n\tint nLength = strlen(pFS);\n\tint nDataLength;\n\tchar pBuf[16];\n\tchar pData[32];\n\tint n, m;\n\tchar *pEnd = NULL;\n\tchar *pErr;\n\tbool bWriteCmd = false;\n\tbool bReadCmd = false;\n\tbool bCompareCmd = false;\n\tunsigned char nRegister;\n\n\tm = 0;\n\tfor (n = 0; n < nLength; n++)\n\t\tif (pFS[n] != ' ') pFS[m++] = pFS[n];\n\tpEnd = pFS + m;\n\tpEnd[0] = 0;\n\n\tdo\n\t{\n\t\tswitch (*pFS)\n\t\t{\n\t\t\tcase ';':\n\t\t\t\tbreak;\n\t\t\tcase 'W':\n\t\t\tcase 'C':\n\t\t\tcase 'R':\n\t\t\t\tbWriteCmd = *pFS == 'W';\n\t\t\t\tbReadCmd = *pFS == 'R';\n\t\t\t\tbCompareCmd = *pFS == 'C';\n\t\t\t\tpFS++;\n\t\t\t\tif ((*pFS) != ':') goto exit_parse;\n\t\t\t\tpFS++;\n\t\t\t\tn = 0;\n\t\t\t\twhile ((pEnd - pFS > 2) && (n < sizeof(pData) + 2) &&(*pFS != '\\n'))\n\t\t\t\t{\n\t\t\t\t\tpBuf[0] = *(pFS++);\n\t\t\t\t\tpBuf[1] = *(pFS++);\n\t\t\t\t\tpBuf[2] = 0;\n\t\t\t\t\tm = strtoul(pBuf, &pErr, 16);\n\t\t\t\t\tif (*pErr) return (pFS - 2);\n\t\t\t\t\tif (n == 0)  deviceAddress = m;\n\t\t\t\t\tif (n == 1) nRegister = m;\n\t\t\t\t\tif (n > 1) pData[n - 2] = m;\n\t\t\t\t\tn++;\n\t\t\t\t}\n\t\t\t\tif (n < 3) goto exit_parse;\n\t\t\t\tnDataLength = n - 2;\n\t\t\t\tif (bWriteCmd)\n\t\t\t\t{\n\t\t\t\t\tBQ35100_dump_data(\"Write\", nRegister, pData, nDataLength);\n\t\t\t\t\ti2cWriteBytes(nRegister, (uint8_t *)pData, nDataLength);\n\t\t\t\t\t/* Adding a delay giving bq35100 device sometime to put register value on I2C bus before we read it. */\n\t\t\t\t\tDelayMs(100);\n\t\t\t\t}\n\n\t\t\t\tif (bCompareCmd || bReadCmd)\n\t\t\t\t{\n\t\t\t\t\tchar pDataFromGauge[nDataLength];\n\t\t\t\t\ti2cReadBytes(nRegister, (uint8_t *)pDataFromGauge, nDataLength);\n\t\t\t\t\tif (bCompareCmd)\n\t\t\t\t\t{\n\t\t\t\t\t\tBQ35100_dump_data(\"Read\", nRegister, pDataFromGauge, nDataLength);\n\t\t\t\t\t\tBQ35100_dump_data(\"Compare\", nRegister, pData, nDataLength);\n\t\t\t\t\t\tif (memcmp(pData, pDataFromGauge, nDataLength))\n\t\t\t\t\t\t{\n\t\t\t\t\t\t\tDEBUG_PRINTF(\"%s: Memory comparison action failed, exiting...\\r\\n\", __func__);\n\t\t\t\t\t\t\tgoto exit_parse;\n\t\t\t\t\t\t}\n\t\t\t\t\t}\n\t\t\t\t\telse\n\t\t\t\t\t\tBQ35100_dump_data(\"Read\", nRegister, pDataFromGauge, nDataLength);\n\t\t\t\t}\n\t\t\t\tbreak;\n\t\t\tcase 'X':\n\t\t\t\tpFS++;\n\t\t\t\tif ((*pFS) != ':') goto exit_parse;\n\t\t\t\tpFS++;\n\t\t\t\tn = 0;\n\t\t\t\twhile ((pFS != pEnd) && (*pFS != '\\n') &&(n <sizeof(pBuf) - 1))\n\t\t\t\t{\n\t\t\t\t\tpBuf[n++] = *pFS;\n\t\t\t\t\tpFS++;\n\t\t\t\t}\n\t\t\t\tpBuf[n] = 0;\n\t\t\t\tn = atoi(pBuf);\n\t\t\t\tDEBUG_PRINTF(\"%s: Delaying %u ms\\r\\n\",__func__, n);\n\t\t\t\tDelayMs(n);\n\t\t\t\tbreak;\n\t\t\tdefault: goto exit_parse;\n\t\t}\n\t\twhile ((pFS != pEnd) && (*pFS != '\\n')) pFS++; //skip to next line\n\t\tif (pFS != pEnd) pFS++;\n\n\t} while (pFS != pEnd);\n\nexit_parse:\n\tdeviceAddress = BQ35100_I2C_ADDRESS;\n\treturn pFS;\n}\n Now when we tried to use overall configuration flash streamer (see attached files), the parsing failed at compare after X: 2ms, We tried increasing the delay to 200 ms from 2 ms. This time it went further in flash stream file but failed at a different point in compare command ;-------------------------------------------------------- ;Data Block ;-------------------------------------------------------- W: 16 00 03 00 00 W: 16 64 03 00 X: 200 C: 16 66 00 W: 16 00 02 00 00 00 E2 FF 33 03 D7 33 BB D6 33 E0 D6 33 09 D6 33 FF FF 3F 00 01 00 FF FF 3F FF FF 3F FF FF 3F FF FF 3F FF FF 3F FF FF 3F FF FF 3F FF FF 3F FF FF 3F FF FF 3F FF FF 3F 03 01 3D 00 01 3D 02 01 3D 0A 00 3D 0A 00 3D 80 03 3D 00 00 3D 00 00 3D 35 80 3D 11 02 3D 49 00 3D 20 2A 0E DF FA 0E E2 FF 32 W: 16 64 60 2B X: 200 C: 16 66 00 W: 16 00 02 01 00 00 FF AA 0E FB A7 0E FF A6 0E F5 ED 3A 06 D7 3A FF 1C 0E C7 FF 36 FF A1 0E FF A0 0E FD A3 0E F2 A2 0E C2 FF 3A FF A1 0E 7F A0 0E FF A3 0E 7F A2 0E BC A5 0E FF A4 0E BB FF 3A FD A1 0E F2 A0 0E FD A3 0E F2 A2 0E BB FF 3A 07 D7 3A 9E FF 3A E2 FF 33 FF AF 0E 01 4F 03 3F 11 0C BF FF 32 2F 10 0C W: 16 64 22 31 X: 200 At this point the parser exited and any subsequent attempts to access the chip failed. Note that the delay command were 2ms originally and we changed it to 200ms thinking additional delay would help. We have now bricked ~3 chips this way. We need help to get this flash streamer mechanism in order to calibrate and configure bq35100 device in factory. Thank you in advance. Regards, Maulin Lodhia Flash stream files used for the test flash_stream_files.7z",
+  "partNumber" : " BQ35100",
+  "allResponseList" : [ {
+    "contentId" : "3301310",
+    "userName" : "Andy Liu (BMS)",
+    "rankPoints" : "42410",
+    "rankName" : "Mastermind",
+    "date" : "Mar 30, 2020 9:42 PM",
+    "userId" : "1864278",
+    "content" : "Hi Maulin, We will check your df.fs file and get back to you. Regarding the bricked devices, I would suggest you use the bqStudio and program the default srec file to them. Andy"
+  }, {
+    "contentId" : "3305165",
+    "userName" : "Maulin Lodhia",
+    "rankPoints" : "380",
+    "rankName" : "Intellectual",
+    "date" : "Apr 2, 2020 4:42 PM",
+    "userId" : "594282",
+    "content" : "Thank you Andy, Any update on this ? Maulin"
+  }, {
+    "contentId" : "3305540",
+    "userName" : "Andy Liu (BMS)",
+    "rankPoints" : "42410",
+    "rankName" : "Mastermind",
+    "date" : "Apr 2, 2020 11:37 PM",
+    "userId" : "1864278",
+    "content" : "I have been a bit busy this week. I would need some time to prepare some C code to verify your flash stream file. I think I should be able to provide my results early next week. Andy"
+  }, {
+    "contentId" : "3319570",
+    "userName" : "Maulin Lodhia",
+    "rankPoints" : "380",
+    "rankName" : "Intellectual",
+    "date" : "Apr 17, 2020 2:51 PM",
+    "userId" : "594282",
+    "content" : "Hello Andy, Any update on the flash stream file verification on BQ35100 ? Thanks Maulin"
+  }, {
+    "contentId" : "3327735",
+    "userName" : "Eric Vos24",
+    "rankPoints" : "3585",
+    "rankName" : "Expert",
+    "date" : "Apr 25, 2020 2:38 AM",
+    "userId" : "3440231",
+    "content" : "Maulin, Unfortunately i am not a software coder so i cannot comment on your code provided. Are you able to attached a Saleae or I2C sniffer on your line when using bqStudio vs your own method to check for differences? This is what i would recommend you do do next. Thanks, Eric Vos"
+  }, {
+    "contentId" : "3329548",
+    "userName" : "Rob Sizeland",
+    "rankPoints" : "20",
+    "rankName" : "Prodigy",
+    "date" : "Apr 27, 2020 9:56 PM",
+    "userId" : "4209741",
+    "content" : "Hi there, I've attached the flash instruction file BQ studio produces, as well as an i2c capture from when BQ studio does the same operation. I notice the delays that BQ studio are larger than the ones specified in the flash instruction file. Also, long writes are split up into multiple smaller writes. Are these differences important? Also, do you see anything else? Thanks, Rob. Battery-Cal.zip"
+  } ],
+  "tags" : [ "/support/power-management/f/196/tags/BQ35100", "/support/power-management/f/196/tags/_2300_%2b%2b%2b%2b%2b%2b%2b%2bBQ35100", "/support/power-management/f/196/tags/_2300_%2b%2b%2b%2b%2b%2b%2bBQstudio", "/support/power-management/f/196/tags/bqStudio" ],
+  "fourmType" : "TI"
+}

data/json/DLP/892627.json

@@ -0,0 +1,55 @@
+{
+  "ticketNumber" : "892627",
+  "reporterName" : "user777540",
+  "rankPoints" : "550",
+  "resolutionStatus" : "TI Thinks Resolved",
+  "ticketName" : "BQ25898D: about the Charging Safety Timer count",
+  "rankName" : "Intellectual",
+  "replies" : " 5",
+  "views" : " 44",
+  "queryText" : "Part Number: BQ25898D hello, I have three questions about the Charging Safety Timer count. It is stated that the Charging Safety Timer count becomes half clock rate in the following cases. 1.Is the half clock rate during \"the status register bits VDPM_STAT (VINDPM) and / or IDPM_STAT (IINDPM) is / are set high\"? 2.Is half clock rate in supplement mode? 3.For example, is the half clock rate when the ILIM pin is limited at 500mA and the setting of the ICHG register is Default: 2048mA? Excerpt from data sheet During input voltage, current or thermal regulation, the safety timer counts at half clock rate as the actual charge current is likely to be below the register setting. For example, if the charger is in input current regulation (IDPM_STAT = 1) throughout the whole charging cycle, and the safety time is set to 5 hours, the safety timer willr expire in 10 hours. best regards",
+  "partNumber" : " BQ25898D",
+  "allResponseList" : [ {
+    "contentId" : "3301228",
+    "userName" : "Ning T",
+    "rankPoints" : "15365",
+    "rankName" : "Genius",
+    "date" : "Mar 30, 2020 7:54 PM",
+    "userId" : "145100",
+    "content" : "Hi, 1. Yes. 2. Depending on if DPM or thermal regulation is in effective. 3. Yes as long as DPM or thermal regulation is in effective. Thanks, Ning."
+  }, {
+    "contentId" : "3309680",
+    "userName" : "user777540",
+    "rankPoints" : "550",
+    "rankName" : "Intellectual",
+    "date" : "Apr 8, 2020 12:11 AM",
+    "userId" : "777540",
+    "content" : "hello, In the following example, how many hours does the timeout take? For example, the charger is in the input current regulation state (IDPM_STAT = 1) for the entire charging cycle and the safety time is set to 5 hours. TMR2X_EN is enabled. The period during which the DPM function does not work and can be charged normally is 2 hours. After that, the DPM function is activated and a portion of the charging current is distributed to the system for an hour. After that, the DPM function does not work, and the period of time when it can charge normally is 4 hours. best regards"
+  }, {
+    "contentId" : "3314716",
+    "userName" : "Ning T",
+    "rankPoints" : "15365",
+    "rankName" : "Genius",
+    "date" : "Apr 14, 2020 4:19 AM",
+    "userId" : "145100",
+    "content" : "Hi, The safety timer only counts at half clock rate in the time frame when the device is in the listed conditions (DPM etc). The problem statement is not very clear. It is better to test on the charger to understand the safety timer behavior. Thanks, Ning."
+  }, {
+    "contentId" : "3322333",
+    "userName" : "user777540",
+    "rankPoints" : "550",
+    "rankName" : "Intellectual",
+    "date" : "Apr 21, 2020 5:51 AM",
+    "userId" : "777540",
+    "content" : "hello, In the following example, how many hours does the timeout take? During the following period, the conditions for charging termination are not satisfied. best regards"
+  }, {
+    "contentId" : "3329861",
+    "userName" : "Ning T",
+    "rankPoints" : "15365",
+    "rankName" : "Genius",
+    "date" : "Apr 28, 2020 4:10 AM",
+    "userId" : "145100",
+    "content" : "Hi, It is better to test on the charger for the specific case and understand the safety timer behavior. Thanks, Ning."
+  } ],
+  "tags" : [ "/support/power-management/f/196/tags/BQ25898D" ],
+  "fourmType" : "TI"
+}

data/json/DLP/892735.json

@@ -0,0 +1,55 @@
+{
+  "ticketNumber" : "892735",
+  "reporterName" : "BAKE KI",
+  "rankPoints" : "80",
+  "resolutionStatus" : "TI Thinks Resolved",
+  "ticketName" : "LM5176-Q1: Is there a way to charge 3A CC-mode? -LM5176-Q1",
+  "rankName" : "Prodigy",
+  "replies" : " 5",
+  "views" : " 35",
+  "queryText" : "Part Number: LM5176-Q1 I will design a battery charging circuit with the LM5176. I want to charge 3A CC-mode, is it possible? If Hiccup or Average Current Limit is off, the current will flow over 3A without limitation. And if I turn on the two functions, I think that the current will rise and the charging will end at 3A. In general, the battery will be charged by CC-CV, so the cut-off time will be very short. I cannot use Chager IC because I have to use AEC-Q100 certified product. As far as I know, BQ24616 etc. do not have AEC-Q100. Is there a way to charge 3A CC-mode? Vin: 10 ~ 16V, Vout: 14.6V / 3A, and there is an immutable fuse in the Vin line, so you must limit the current.",
+  "partNumber" : " LM5176-Q1",
+  "allResponseList" : [ {
+    "contentId" : "3301123",
+    "userName" : "Garrett Roecker",
+    "rankPoints" : "18240",
+    "rankName" : "Mastermind",
+    "date" : "Mar 30, 2020 6:09 PM",
+    "userId" : "3456925",
+    "content" : "Hi BAKE KI, Thank you for reaching out with your question and for considering the LM5176 in your design. The LM5176 can be configured to output a constant current using the average current limiting feature. Placing a resistor between the ISNS+ and ISNS- pin will limit the current when the voltage drop across the resistor is 50mV. Please let me know if you have any other questions. Thanks, Garrett"
+  }, {
+    "contentId" : "3301627",
+    "userName" : "BAKE KI",
+    "rankPoints" : "80",
+    "rankName" : "Prodigy",
+    "date" : "Mar 31, 2020 5:59 AM",
+    "userId" : "1929261",
+    "content" : "Thank you so much for answering. The battery capacity is 7.2 Ah. What resistance should I use for 3A CC charging? If you use 0.015 ohm for the sensing resistance between ISNS + and ISNS -... Is 45mV when charging at 3A, and 51mV at 3.4A to cut off the current? If it is correct ... I think that as soon as the charging starts, the current will flow more than 3.4A, and the charging will end within a few seconds."
+  }, {
+    "contentId" : "3304170",
+    "userName" : "Garrett Roecker",
+    "rankPoints" : "18240",
+    "rankName" : "Mastermind",
+    "date" : "Apr 1, 2020 10:15 PM",
+    "userId" : "3456925",
+    "content" : "Hi BAKE KI, It is possible to add multiple resistors in parallel to set a static current limit for the average output current. 17mOhm will set the typical output current to 3A Please let me know if you have any questions. Thanks, Garrett"
+  }, {
+    "contentId" : "3328570",
+    "userName" : "BAKE KI",
+    "rankPoints" : "80",
+    "rankName" : "Prodigy",
+    "date" : "Apr 27, 2020 10:02 AM",
+    "userId" : "1929261",
+    "content" : "3.3A CC-Mode operation was confirmed by applying a 15mΩ resistor. All thanks to you. Can the input current be maintained at 3A by changing the 15mΩ resistor position to Input?"
+  }, {
+    "contentId" : "3329580",
+    "userName" : "Garrett Roecker",
+    "rankPoints" : "18240",
+    "rankName" : "Mastermind",
+    "date" : "Apr 27, 2020 10:36 PM",
+    "userId" : "3456925",
+    "content" : "BAKE KI, Yes moving the resistor to the input voltage rail will be used to limit the input current. Thanks, Garrett"
+  } ],
+  "tags" : [ "/support/power-management/f/196/tags/bq24616", "/support/power-management/f/196/tags/LM5176", "/support/power-management/f/196/tags/LM5176_2D00_Q1" ],
+  "fourmType" : "TI"
+}

data/json/DLP/892774.json

@@ -0,0 +1,95 @@
+{
+  "ticketNumber" : "892774",
+  "reporterName" : "Y.Ottey",
+  "rankPoints" : "3030",
+  "resolutionStatus" : "TI Thinks Resolved",
+  "ticketName" : "TPS61087: Output voltage of TPS61087",
+  "rankName" : "Genius",
+  "replies" : " 12",
+  "views" : " 63",
+  "queryText" : "Part Number: TPS61087 Dear all, I would like to ask about TPS61087. When the output voltage is set from 9V to 8V (setting the values of R1 and R2 to match the output voltage of 8V) using the same circuit as the data sheet Figure.16 (the following circuit), the output voltage only increases to 5V. (At this time, 330Ω is connected to the load.) The output voltage remains at 5V even if the following measures (measures to increase the ON time) are taken. ・Lower input voltage than 3.3V ・Try a load of 330Ω or more. ・Replaced the inductor at 4.7, 10, 18, 27uH. If there are any conceivable factors, please let me know. When I check the datasheet, it seems that Rcomp and Ccomp need to be set to 8V, but I would like to know if there are other possible factors. Best Regards, Y.Ottey",
+  "partNumber" : " TPS61087",
+  "allResponseList" : [ {
+    "contentId" : "3300617",
+    "userName" : "Helen chen",
+    "rankPoints" : "32965",
+    "rankName" : "Mastermind",
+    "date" : "Mar 30, 2020 12:48 PM",
+    "userId" : "4197150",
+    "content" : "Dear Sir, I think there has some soldering issue on the board, please remove the feedback resistor and solder it again. By the way, what is R1 and R2 value you soldered on the board?"
+  }, {
+    "contentId" : "3300778",
+    "userName" : "Y.Ottey",
+    "rankPoints" : "3030",
+    "rankName" : "Genius",
+    "date" : "Mar 30, 2020 2:42 PM",
+    "userId" : "6052437",
+    "content" : "Dear Helen Thank you for your reply. \"I think there has some soldering issue on the board, please remove the feedback resistor and solder it again.\" Does the \"feedback resistor\" shown above refer to R1 and R2 on the circuit? Also, could you tell me why you think that the output voltage only goes up to 5V due to \"some soldering issue on the board\"? \"By the way, what is R1 and R2 value you soldered on the board?\" The above is currently being confirmed. Is the above question to check if R1 and R2 are set as calculated below? Regards, Y.Ottey"
+  }, {
+    "contentId" : "3302324",
+    "userName" : "Brigitte",
+    "rankPoints" : "25960",
+    "rankName" : "Mastermind",
+    "date" : "Mar 31, 2020 4:28 PM",
+    "userId" : "24231",
+    "content" : "Dear Y. Ottey, Please check if the output voltage changes when you start with no load on the output. Would you please share the resistor values you are using for R1 and R2?"
+  }, {
+    "contentId" : "3302855",
+    "userName" : "Helen chen",
+    "rankPoints" : "32965",
+    "rankName" : "Mastermind",
+    "date" : "Apr 1, 2020 1:56 AM",
+    "userId" : "4197150",
+    "content" : "Thanks Brigitte :) Hi Ottey, Yes, R1 and R2 should be the value calculated by the below equation: if Vo=8V, R2=17.8k, then R1=97.6k . By the way, what kind of board did you use? Is it TPS61087 EVM board?"
+  }, {
+    "contentId" : "3317829",
+    "userName" : "Y.Ottey",
+    "rankPoints" : "3030",
+    "rankName" : "Genius",
+    "date" : "Apr 16, 2020 9:44 AM",
+    "userId" : "6052437",
+    "content" : "Dear Helen and Brigitte Thank you for your reply. There are additional things to check. When the circuit is confirmed, it is a circuit in which the operational amplifier is connected to the wiring of the FB terminal as shown in the figure below. The reason is that I want to change the output of TPS61087 by injecting the voltage from the operational amplifier. In this case, will the IC be damaged if voltage is injected from the output of the operational amplifier while the TPS61087 is not started? (Detailed circuits can be sent to you in a private message.) Regards, Y.Ottey"
+  }, {
+    "contentId" : "3319221",
+    "userName" : "Helen chen",
+    "rankPoints" : "32965",
+    "rankName" : "Mastermind",
+    "date" : "Apr 17, 2020 9:44 AM",
+    "userId" : "4197150",
+    "content" : "Hi Ottey, Will not be damaged. But I'm wondering this kind of connection may leads to error. It should decoupling the output of amp and the FB. a RC filter is needed before connecting to the FB. And the amp should be connected as a voltage follower."
+  }, {
+    "contentId" : "3320779",
+    "userName" : "Y.Ottey",
+    "rankPoints" : "3030",
+    "rankName" : "Genius",
+    "date" : "Apr 20, 2020 6:08 AM",
+    "userId" : "6052437",
+    "content" : "Dear Helen Thank you for your reply. \"It should decoupling the output of amp and the FB. a RC filter is needed before connecting to the FB. And the amp should be connected as a voltage follower.\" When I checked the circuit, it was as follows ・ There is no RC filter between the FB terminal and the output of the amplifier. ・ The part with the amplifier is a non-inverting amplifier circuit (calculated the amplification factor is 5.1V / V) What kind of error is possible in this case? (If all goes well, I'll send you a detailed circuit in a private message.) Regards, Y.Ottey"
+  }, {
+    "contentId" : "3322664",
+    "userName" : "Y.Ottey",
+    "rankPoints" : "3030",
+    "rankName" : "Genius",
+    "date" : "Apr 21, 2020 11:32 AM",
+    "userId" : "6052437",
+    "content" : "Dear Helen I have an additional question for you. \"And the amp should be connected as a voltage follower.\" Please explain the reason why the peripheral circuit of the amplifier is used as a voltage follower as described above. In addition to my previous post, I would be happy if you could answer. Regards, Y.Ottey"
+  }, {
+    "contentId" : "3322806",
+    "userName" : "Helen chen",
+    "rankPoints" : "32965",
+    "rankName" : "Mastermind",
+    "date" : "Apr 21, 2020 1:08 PM",
+    "userId" : "4197150",
+    "content" : "Hi Ottey, The part with the amplifier is a non-inverting amplifier circuit (calculated the amplification factor is 5.1V / V)? could you please send the related circuit to me?"
+  }, {
+    "contentId" : "3322808",
+    "userName" : "Helen chen",
+    "rankPoints" : "32965",
+    "rankName" : "Mastermind",
+    "date" : "Apr 21, 2020 1:10 PM",
+    "userId" : "4197150",
+    "content" : "To decoupling the circuit, or its hard to get the target voltage. But anyway, I need the exact circuit for a study."
+  } ],
+  "tags" : [ "/support/power-management/f/196/tags/TPS61087" ],
+  "fourmType" : "TI"
+}

data/json/DLP/892931.json

@@ -0,0 +1,63 @@
+{
+  "ticketNumber" : "892931",
+  "reporterName" : "Saumil Shah60",
+  "rankPoints" : "365",
+  "resolutionStatus" : "Resolved",
+  "ticketName" : "BQ24192: BQ24192 default register settings and Charging functionality when battery is fully discharged",
+  "rankName" : "Intellectual",
+  "replies" : " 6",
+  "views" : " 35",
+  "queryText" : "Part Number: BQ24192 Hicompany Team, We are using BQ24192 as a charger and BQ27542 as Fuel Gauge and ABLIC 8211C as a Protection IC. We are facing one issue - For Ex - Battery is Fully discharged and reached the 3.1V when we Power ON the Unit then Battery charger apply 4.208V by default and ABLIC IC's charging Mosfet gets Off which is connected with CHG Pin and that may be because of Charge overcurrent condition detected because we have used 10mE resistor on Fuel gauge circuit in the series. Now I have a few questions - 1. How can we change pre-charge to fast charge threshold from 3V to 3.3V in the case of Battery charger BQ24192? 2. When we are changing the register settings and making the fast charge current to 100mA by setting up the 20 Percent bit then we are not facing this issue but how can we ensure that Battery charger is up by our set register settings? 3. Basically, what we have seen is that when Battery charger initially applies 4.2V and 2A fast charge current then this condition occurs but what we shall do to prevent this condition and battery charger applies less voltage and less current initially up to 3.3V and then gradually increase the voltage and current? 4. Is it possible that we shall change the default register settings at the time of initialization? Thanks Saumil",
+  "partNumber" : " BQ24192",
+  "allResponseList" : [ {
+    "contentId" : "3302043",
+    "userName" : "Ning T",
+    "rankPoints" : "15365",
+    "rankName" : "Genius",
+    "date" : "Mar 31, 2020 1:52 PM",
+    "userId" : "145100",
+    "content" : "Saumil, The threshold is fixed internally. Disable watchdog timer by setting WATCHDOG bits REG07[5:4]=00 /CE pin can be pulled high to disable charge initially then pull low to charge when ready. Default values can’t be changed. Thanks, Ning."
+  }, {
+    "contentId" : "3303344",
+    "userName" : "Saumil Shah60",
+    "rankPoints" : "365",
+    "rankName" : "Intellectual",
+    "date" : "Apr 1, 2020 11:27 AM",
+    "userId" : "5392575",
+    "content" : "Hi Ning, Ok, thanks for your response. Sr No - 1,3 and 4 are Ok. Now for Sr No 2, Regarding the Watchdog timer for Host Mode and default autonomous mode, 1. If I disable the Watchdog timer then Host needs to control the charger for the entire charging cycle? for example - If the host writes certain registers for fast charge current but when the Battery voltage reaches near to the charge voltage then transition from CC mode to CV mode and reduces the current gradually decides by charger or Host need to control that entire cycle? 2. While during the write cycle of I2C register, if charger enters into the Host mode then and the Watchdog time expiration occurs then, the registers that host has written been again set to default or it will remain the same? 3. At the Power ON/OFF state, host initialized the charger with the register settings and then host goes into sleep mode then what will be the register settings? Thanks Saumil"
+  }, {
+    "contentId" : "3309600",
+    "userName" : "Ning T",
+    "rankPoints" : "15365",
+    "rankName" : "Genius",
+    "date" : "Apr 7, 2020 9:41 PM",
+    "userId" : "145100",
+    "content" : "Saumil, 1. The device has built-in control loops to determine the transition from CC to CV. The host does not need to do anything. 2. Referring to Figure 25. Watchdog Timer Flow Chart on the d/s, if watchdog timer expires, the device will be in default mode and all the registers are in the default settings. 3. Please refer to Figure 25. Watchdog Timer Flow Chart. If the user would like to keep the register settings unchanged while the host is inactive, it is better to disable watchdog timer by setting REG05[5:4] = 00 before the host goes to inactive. Thanks, Ning."
+  }, {
+    "contentId" : "3310532",
+    "userName" : "Saumil Shah60",
+    "rankPoints" : "365",
+    "rankName" : "Intellectual",
+    "date" : "Apr 8, 2020 3:59 PM",
+    "userId" : "5392575",
+    "content" : "Hi Ning, Ok, It seems to resolved my issue. Thanks Saumil"
+  }, {
+    "contentId" : "3322290",
+    "userName" : "Saumil Shah60",
+    "rankPoints" : "365",
+    "rankName" : "Intellectual",
+    "date" : "Apr 21, 2020 4:48 AM",
+    "userId" : "5392575",
+    "content" : "Hi Ning, I have tricky questions on this Watchdog functionality. 1. We are successfully able to run the charging cycle by Host and for that, we are using the Watchdog Timer disable functionality and we are selecting the Charging current by our Own. 2. We have created Some Voltage loops in that we are reading the Voltage from Fuel gauge and we are deciding on the charging current for the Battery charger. 3. For 2.8V to 3.2V, we are supplying the 140mA current for charging. 4. We have one Power ON/OFF button as well that can turn off the Host but battery can still remain present and connected with the Battery Charger. 5. Now, my query is that if the Charger is in 140mA charging current state and we are disabling the Watchdog timer also and if the user has turned off the host via Power ON/OFF button, then Charger may remain present in this 140mA state only or is there any way such that charger may start functioning with the fast charge current as well automatically? Thanks Saumil"
+  }, {
+    "contentId" : "3324606",
+    "userName" : "Saumil Shah60",
+    "rankPoints" : "365",
+    "rankName" : "Intellectual",
+    "date" : "Apr 22, 2020 4:14 PM",
+    "userId" : "5392575",
+    "content" : "Hi Ning, I have tricky questions on this Watchdog functionality. 1. We are successfully able to run the charging cycle by Host and for that, we are using the Watchdog Timer disable functionality and we are selecting the Charging current by our Own. 2. We have created Some Voltage loops in that we are reading the Voltage from Fuel gauge and we are deciding on the charging current for the Battery charger. 3. For 2.8V to 3.2V, we are supplying the 140mA current for charging. 4. We have one Power ON/OFF button as well that can turn off the Host but battery can still remain present and connected with the Battery Charger. 5. Now, my query is that if the Charger is in 140mA charging current state and we are disabling the Watchdog timer also and if the user has turned off the host via Power ON/OFF button, then Charger may remain present in this 140mA state only or is there any way such that charger may start functioning with the fast charge current as well automatically? Thanks Saumil"
+  } ],
+  "tags" : [ "/support/power-management/f/196/tags/BQ24192" ],
+  "fourmType" : "TI"
+}

data/json/DLP/893085.json

@@ -0,0 +1,95 @@
+{
+  "ticketNumber" : "893085",
+  "reporterName" : "Hector Chen",
+  "rankPoints" : "190",
+  "resolutionStatus" : "Resolved",
+  "ticketName" : "TPS23758: Power consumption on the DC-DC controller",
+  "rankName" : "Prodigy",
+  "replies" : " 12",
+  "views" : " 64",
+  "queryText" : "Part Number: TPS23758 Hi, Do we have a power consumption number of TPS23758 when an output load is 5V/13W for reference? Do we have a recommended max ambient operating temp of TPS23758? or a curve showing ambient temp vs TPS23758 PD Thanks.",
+  "partNumber" : " TPS23758",
+  "allResponseList" : [ {
+    "contentId" : "3302229",
+    "userName" : "Michael Pahl",
+    "rankPoints" : "4915",
+    "rankName" : "Expert",
+    "date" : "Mar 31, 2020 3:26 PM",
+    "userId" : "6102321",
+    "content" : "Hello Hector, The TPS23758EVM-080 shows the load regulation and efficiency. The load regulation shows the specific output voltage at the related output current, so you can calculate the exact output power. Then you can use the efficiency to calculate the input power and the power lost in the system. The datasheet specifies a max temperature before thermal shutdown on page 9. Can you list a specific metric you want graphed against temperature? Pages 10-13 show graphs that list different parameters tested against temp. If this post answers your question, please indicate so by marking this thread as resolved. Thank you. Regards, Michael P. Applications Engineer customer organization"
+  }, {
+    "contentId" : "3302866",
+    "userName" : "Hector Chen",
+    "rankPoints" : "190",
+    "rankName" : "Prodigy",
+    "date" : "Apr 1, 2020 2:07 AM",
+    "userId" : "5910362",
+    "content" : "Hi Michael, Thanks for your information. I can estimate power loss by input power and efficiency. However, the power loss includes other components in the PD like transformer. What I want is to get power loss on TPS23758 only so that I can use thermal resistance to estimate Tj. Our system consumes 7.9W input power, the case temp of TPS23758 is 101C and ambient temp is around 80C. Do you suggest TPS23758 operates when Tj is over 125C but lower than Turnoff temperature? In other words, we can use TPS23758 without encountering the reliability issue or damages if Tj is lower than Turnoff temp (I know parameters will be affected by temp)? Thanks."
+  }, {
+    "contentId" : "3302872",
+    "userName" : "Hector Chen",
+    "rankPoints" : "190",
+    "rankName" : "Prodigy",
+    "date" : "Apr 1, 2020 2:11 AM",
+    "userId" : "5910362",
+    "content" : "Hi Michael, Thanks for your information. I can estimate power loss by input power and efficiency. However, the power loss includes other components in the PD like transformer. What I want is to get power loss on TPS23758 only so that I can use thermal resistance to estimate Tj. Our system consumes 7.9W input power, the case temp of TPS23758 is 101C and ambient temp is around 80C. Do you suggest TPS23758 operates when Tj is over 125C but lower than Turnoff temperature? In other words, we can use TPS23758 without encountering the reliability issue or damages if Tj is lower than Turnoff temp (I know parameters will be affected by temp)? Thanks."
+  }, {
+    "contentId" : "3303746",
+    "userName" : "Michael Pahl",
+    "rankPoints" : "4915",
+    "rankName" : "Expert",
+    "date" : "Apr 1, 2020 4:03 PM",
+    "userId" : "6102321",
+    "content" : "Hector, I understand now you want Tj. The following application note details how to calculate Tj and other thermal parameters for our IC's: <secret URL>/lit/an/spra953c/spra953c.pdf As specified in the datasheet, –40°C to 125°C is the Junction temperature range. If this post answers your question, please indicate so by marking this thread as resolved. Thank you. Regards, Michael P. Applications Engineer customer organization"
+  }, {
+    "contentId" : "3308503",
+    "userName" : "Hector Chen",
+    "rankPoints" : "190",
+    "rankName" : "Prodigy",
+    "date" : "Apr 7, 2020 5:45 AM",
+    "userId" : "5910362",
+    "content" : "Michael, I understand how to calculate Tj using thermal resistance. Is it diffcult to know TPS23758 power consumption becasue of internal MOS ? Thanks Hector"
+  }, {
+    "contentId" : "3309031",
+    "userName" : "Michael Pahl",
+    "rankPoints" : "4915",
+    "rankName" : "Expert",
+    "date" : "Apr 7, 2020 2:28 PM",
+    "userId" : "6102321",
+    "content" : "Hello Hector, The power consumption of the IC is discussed in this other post. Since they already discuss it, I just attach the link: <secret URL>/support/power-management/f/196/t/820034?TPS23755-TPS23755-IC-Power-Dissipation-Calculation The calculation includes an assumption about the power loss through the internal FET gate because the direct gate capacitance cannot be measured. However, we can estimate the power loss through there because all the power for the gate is coming from VCC so that is how we calculate it. If this post answers your question, please indicate so by marking this thread as resolved. Thank you. Regards, Michael P. Applications Engineer customer organization"
+  }, {
+    "contentId" : "3311324",
+    "userName" : "Hector Chen",
+    "rankPoints" : "190",
+    "rankName" : "Prodigy",
+    "date" : "Apr 9, 2020 10:14 AM",
+    "userId" : "5910362",
+    "content" : "Hi Michael, The calculation shown in <secret URL>/support/power-management/f/196/t/820034?TPS23755-TPS23755-IC-Power-Dissipation-Calculation The power dissipated by the IC will be the power at the pass FET (IRTN*IRTN*RDSon) and the power to drive the gate of the switching FET (VCC*ICC) and conduction loss of the switching FET (RDSonFET*Irms*Irms). Can we ignore switching loss of the switching FET ?"
+  }, {
+    "contentId" : "3315981",
+    "userName" : "Michael Pahl",
+    "rankPoints" : "4915",
+    "rankName" : "Expert",
+    "date" : "Apr 14, 2020 11:14 PM",
+    "userId" : "6102321",
+    "content" : "Hello Hector, Yes that is correct. If this post answers your question, please indicate so by marking this thread as resolved. Thank you. Regards, Michael P. Applications Engineer customer organization"
+  }, {
+    "contentId" : "3322528",
+    "userName" : "Hector Chen",
+    "rankPoints" : "190",
+    "rankName" : "Prodigy",
+    "date" : "Apr 21, 2020 9:00 AM",
+    "userId" : "5910362",
+    "content" : "Hi Michael, Here is current measurment of the switching MOS in TPS23758. Calculated conduction loss of the MOS is 0.08W. Total power loss of TPS23758 would be too low to match case temperture measurment on TPS23758 itself. Why can we ignore switching loss of the switching MOS ? Thanks."
+  }, {
+    "contentId" : "3323039",
+    "userName" : "Michael Pahl",
+    "rankPoints" : "4915",
+    "rankName" : "Expert",
+    "date" : "Apr 21, 2020 3:23 PM",
+    "userId" : "6102321",
+    "content" : "Hello Hector, The switching loss is estimated by the power to drive the gate of the switching FET (VCC*ICC). The traditional way to calculate the switching loss is not possible with the FET internal to the part. If this post answers your question, please indicate so by marking this thread as resolved. Thank you. Regards, Michael P. Applications Engineer customer organization"
+  } ],
+  "tags" : [ "/support/power-management/f/196/tags/TPS23758" ],
+  "fourmType" : "TI"
+}