EG800K-EU-LC QuecPython firmware: device does not charge or stay powered on via USB after replacing OEM firmware

Hi,

I am using an EG800K-EU-LC tracker board with QuecPython OCPU firmware.

With the original OEM firmware, the tracker stayed powered on when the battery was fitted and USB/wall power was connected. After flashing QuecPython firmware and running my own Python app, the device no longer behaves the same:

  • With battery fitted + USB power: device runs only until the battery drains. It does not appear to charge/sustain from USB.

  • Without battery + USB power: device powers off after a period of time.

  • This happens even when my app disables autosleep and holds a wakelock.

  • AT+CBC returns ERROR.

  • Power.getVbatt() works.

  • pm.autosleep(0) returns 0.

  • pm.get_wakelock_num() shows wakelock active.

  • Current firmware reports:

AT+CGMR:
CRANE_CAT1_CP_SDK_1.010.146X_CPONLY__A01602_PS_LTE_Only_SDK_20250208...

Firmware used:

EG800KEULCR07A05M04_OCPU_QPY

My questions:

  1. Does EG800K-EU-LC QuecPython firmware support battery charging management directly, or is charging fully handled by an external charger/power-path IC on the tracker PCB?

  2. Is USB_VBUS only a USB detection pin on EG800K, meaning the module must always be powered through VBAT?

  3. Does the OEM tracker firmware normally configure a board-specific GPIO for charger enable, VBAT enable, power-hold, or USB power-path control?

  4. If yes, which QuecPython GPIO/API or AT command should be used to keep the tracker powered and charging while USB power is present?

  5. Is there any known setting such as AT+QCFG="fast/poweroff" or another PM/charging configuration that affects this behavior?

  6. Can EG800K QuecPython firmware run reliably from USB power with no battery fitted, or is a battery/external VBAT supply required?

I can provide logs showing VBAT, USB status, wakelock count, power-on reason and power-down reason if needed.

Thanks.

Dear Customer:

  1. The QuecPython firmware does not support battery charging management by default. it is handled by the power management circuit.
  2. Yes, you are right.
  3. No, it depends on the hardware for the GPIO configuration. The modules support GPIO, and the customers need to refer to their hardware to configure them.
  4. For GPIO usage, please refer to the link below. Pin - Control I/O Pins - QuecPython
  5. Battery charging management is implemented by the application. QuecPython does not support most AT commands, such as AT+QCFG=“fast/poweroff” .But this command can be implemented by API. You can use a GPIO interrupt and power-off API to achieve it
  6. EG800K needs to be powered via VBAT