This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

IWR1443: IWR1443 steady state power

Part Number: IWR1443
Other Parts Discussed in Thread: IWR1642, AWR1642, TEST2

Hi TI team, 

What is the official power consumption for the IWR1443 before sensorStart and after sensorStop ? Same question for the IWR1642. 

Thanks

  • Hello,

    Given that there are different radar - mmwave sensor configurations, there is no specific "official power consumption", there are several references:

    a) In section 5.2 of the datasheet there is a maximum current and voltage by rail.   

    b) there is a power spreadsheet for specific parameters, this is downloadable from the TI web page.

    c) in the datasheet for AWR1642, there is a specific power vs use case table in section 5.

    d) if you have a specific industrial use case, you will have a specific power, TIDEP 0091 for level sensing has some values in the design guide.

    We are working to reduce the 1443 power for Level Sensing.   Related to (d) you could measure the EVM 5v input current, or PMIC rail currents with a wireloop

    in series with the PMIC output inductor, 

    Regards,

    Joe Quintal

  • Thanks Joe, 

    But I wanted the power consumption number before "sensorStart" command is sent - and after "sensorStop" has been issued - which to me represents a less-than-active mode. I can measure but wanted to understand what the official number is and if this state can be referred to as 'standby' ? 

  • Hello,
    This is application specific.
    The boot time depending on the code size, and the 1642 or 1443, and if the BSS is in ROM or loaded from the application, affect the power.
     
    If you add the use of GPIO-0 to your code, and trigger the oscilloscope
    nRST – shows start of boot time 0->1
    GPIO-0 first MSS instruction force one (end of boot)
    GPIO-0 force zero at first CLI instruction (start of application)
    GPIO-0 force one at end CLI instruction (end of CLI)
    GPIO-0 force zero at end of application
    Measure 5v current (there is a resistor on EVM, you would need a current probe, or two voltage probes)
     
    In the TIDEP 91 application, where the IWR1443 has BSS in ROM (smaller QSPI load 83KB vs 275KB).
    This has a truncated software tool chain. 
    In our current results for reduced power, Level Sensing application, the booting process nRST release, to GPIO0 0->1, 14mj.
     
    After the mmwave Sensor stop, you need to process the Radar Rx data into an output.  In our Level Sensing application, the
    Post processing and SPI data transfer takes 3mj.
     
    The hardware power tool, and datasheet power estimates, are not as accurate as instrumenting the EVM listed above.

    Regards,
    Joe Quintal
     
     
     
     
    Regards,
    Joe Quintal
     
     
  • Thanks Joe, I will make the measurements. 

    Am more interested in the current draw after boot and before the RF is switched on and then after it is switched off. Understand the implications of BSS location during boot, as well as the application boot/copy itself.

    Thanks

  • Hello In our Level Sensing testing, we find there is a base current with SOC resources. This increases during step two read QSPI, and push to internal mmwave sensor RAM. Another increase occurs as the operating system, mmwave SDK functions are started. The RF Calibration, and RF chirp are high utilization of the analog rails. After this step we have the calculation and output of data.
    As an example, this is our 36ms / 1000ms cycle, sampled b the osciloscope, and software does averaging and integration.

    Test num Duration starttime GPIOm 5v cur 5v pow
    Test# 1 0.007 0.00025 1 0.080917 0.002832
    Test# 2 0.01505 0.00725 5 0.132769 0.009991
    Test# 3 0.0107 0.0223 7 0.172793 0.009244
    Test# 4 0.0018 0.033 5 0.253395 0.002281

    TotalDuration 5v total pwr
    0.03455 0.024348

    Test1 - is the mmwave sensor hardware init.
    Test2 - is the MSS Rom QSPI read
    Test3 - is the MSS start, sending commands to BSS
    Test4 - is the special calibration (abbreviated), chirp/measuerment/data output

    Regards
    Joe Quintal