• State
  • Locked Locked
  • Replies 5 replies
  • Subscribers 79 subscribers
  • Views 205 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

MSP-EXP430G2ET: Energy trace Mean Current Calculation

demetrio pitasi
Prodigy 20 points
Part Number: MSP-EXP430G2ET
Other Parts Discussed in Thread: ENERGYTRACE

Good Morning,
We are using MSP-EXP430G2ET together with code Composer Energy Trace technology, to compare two different FW Release of our product.

Performing two different sessions of 300 seconds we gathered the attached traces

EnergyTrace_2022_06_21_175707
EnergyTrace_2022_06_21_174859

EnergyTrace_2022_06_21_175707 shows 88.837mJ  over 300 seconds with e mean Current consumption of 127uA
EnergyTrace_2022_06_21_174859 shows a greatly reduced Energy consumption of 30,177 over 300 seconds but a similar current consumption of 124uA

We'd expect less then half in term of mean current consumption, what we are missing?

Thank you very much for your support.
Kind Regards,
Demetrio PItasi
EnergyTrace_2022_06_21_174859.zipEnergyTrace_2022_06_21_175707.zip

  • 0
    TI__Genius 9970 points

    Hi,

    Please confirm these are the numbers you are seeing. I will assign it to our CCS team to get clarity on how these calculations are performed.

    Thanks,

    Evan

  • 0 in reply to demetrio pitasi
    TI__Guru**** 420720 points

    I will need to escalate this issue to the engineering team responsible for ET. I will pass on any updates as I get them

  • 0 in reply to Ki
    TI__Guru**** 420720 points

    I do not have an update yet. As soon as I have one I will let you know.

  • 0 in reply to Ki
    TI__Guru**** 420720 points

    I received an update from engineering. See below:

    By looking at the summary data in the forum, the display values appar to be reflecting the data. Doesn’t seem like a bug on the plugin side.

    Some more notes:

    • The energy value is a real measurement by XDS110.
    • The current & voltage values are just samples at a relative low frequency: less than 2K samples/second. They do not have full details along the timeline. Note that the energy value is not calculated by the current & voltage samples.
    • So it is possible to have discrepancy between measured energy and sampled current/voltage. If this is the case, energy measurement is more thrust worthy.
    • The bottom line is: I/V samples are for reference only.
    • Note that using an HDR ET pod will allow for higher I/V sampling frequency

**Attention** This is a public forum