Xinyuan-LilyGO / LilyGO-T-A76XX

LilyGo A7670X A7608X SIM7670G series
MIT License
117 stars 49 forks source link

Deepsleep problem #105

Closed PontiuspilatusNL closed 3 weeks ago

PontiuspilatusNL commented 4 months ago

I have tried five different boards. Version 1.1 and 1.2. 7670E, all the same problem; Works perfect when Board is always on. With deepsleep every board has the same problem; sometimes it runs for a few days, sometimes even three weeks, but most of the time after a few days board is hanging. Doesn't matter running on battery or powersupply, same problem. looks like modem is not starting up properly. Even with the new sketch to turn of modem in deepsleep still the same problem. Anybody any idea?

lewisxhe commented 4 months ago

After running for several days, the modem cannot be woken up using battery or USB?

PontiuspilatusNL commented 3 months ago

Excactly, Modem-Led is blinking, like it is connected, but program stops. Nothing goes, untill i reset or power off the board.

br4593 commented 3 months ago

I have the same issue. I couldn't find a solution yet. It works fine when connected via USB but on battery it sometimes wont wake up.

Rikests commented 3 months ago

This sounds exactly like the problem I was having with my A7670E LilyGO boards, they would run for months before hanging, sometimes a few days. You should try to read the serial output through UART pins of the board, without using USB cable and see if the ESP32 chip is getting brownouts or restarts when the modem is starting up after LONG (more than 1hour) deep sleep periods. When you use USB to monitor the serial connection the power to the modem is delivered in a different manner, this is why this only happens on battery power. I use CP2102 based USB to UART converter to monitor the serial through Boards UART pins.

HarrisonPace commented 3 months ago

Is this happening just on the A7670E variant or the A7670G modem as well?

br4593 commented 2 months ago

It happens to me with the A7670G with GPS variant.

github-actions[bot] commented 1 month ago

This issue is stale because it has been open for 30 days with no activity.

github-actions[bot] commented 3 weeks ago

This issue was closed because it has been inactive for 14 days since being marked as stale.