Power Consumption Test — Q&A

2025-11-14

This Q&A summarizes common issues encountered during power-consumption testing, quick troubleshooting steps, and suggested fixes. When reporting an issue, please follow the diagnostic order below and record key information (firmware version, serial logs, power-monitor settings).

Q1 — Measured current is higher or unstable. How do I troubleshoot?

A:

  1. Check wiring
    • Verify VBAT and GND are correctly connected and that the power monitor shares a common ground with the DUT.
  2. Check range and sampling settings
    • If readings are near the range limit, increase the range. If readings are noisy, increase averaging or lower bandwidth.
    • For peak capture use higher sampling (e.g., 10 kHz); for averaged values use lower sampling or sliding average.
  3. Power supply current-limiting and voltage drop
    • Ensure the power supply is not in current-limit mode and that output voltage remains stable.

If the above checks pass, collect logs and contact the test owner.

Q2 — The module does not enter Deep Sleep or is unresponsive to AT commands. What should I do?

A:

  1. Verify serial settings
    • Common settings: 115200 8N1. Confirm correct port and baud rate are used.
  2. Confirm firmware and AT command set
    • Different firmware releases may use different commands; check the firmware release notes or AT manual.
  3. Verify hardware pins and jumpers
    • Ensure BOOT/mode pins and jumpers are set according to the test instructions and the module is not in download/debug mode.

Tip: Send a simple query (e.g., version command) over serial and log the response for reproduction information.

Q3 — I don’t see peak currents during active tests. How to confirm peaks are present?

A:

  1. Increase sample rate or enable peak capture
    • Enable peak/peak-hold on the power monitor or increase sampling rate to capture short spikes.
  2. Confirm test traffic is running
    • Check iperf/traffic tools on both DUT and peer; verify network and serial logs show actual data transmission.

Q4 — Results vary between runs or between devices. How to ensure reproducibility?

A:

  1. Record and freeze test conditions
    • Record firmware version, AT settings, DTIM/connection state, antenna connection, and environment (e.g., nearby Wi‑Fi activity).
  2. Rerun with identical firmware and settings
    • If differences persist, repeat measurements on the same power monitor and fixture to exclude platform variation.

Q5 — Exported log file cannot be opened or appears corrupted. What should I check?

A:

  1. Re-export using vendor tools
    • Some power monitors require vendor tools or specific encoding options for reliable export.
  2. Increase buffer or change export format
    • Try CSV/TXT export; stop real-time displays before exporting to reduce concurrent write issues.

Q6 — Standby current is unexpectedly high after OTA/firmware update. How to handle it?

A:

  1. Reboot and retest
    • OTA may leave background services running; rebooting often restores expected behavior.
  2. Check background services and configuration
    • Confirm no extra services or telemetry are active and that DTIM/BLE advertising parameters are correct.

If the issue cannot be resolved, collect the following and escalate to the firmware or test-lab owner:

  • DUT serial logs (including steps to reproduce),
  • Firmware version and build info,
  • Power-monitor settings (range, sampling, averaging, peak settings),
  • Short reproduction steps and related data files (CSV/screenshots).