@Revital Maroko @Revital Maroko good question — and honestly this is exactly the kind of real-world deployment scenario where the Power/Program Kit starts to make a lot more sense.
I don't have a published combined draw spec to point you at right now, but here's what I can tell you from what I know about the setup: the GNSS at 18Hz is doing the heavy lifting on the power side since it's running the positioning engine continuously, and the BLE module adds its own draw on top depending on your transmission interval. If you're pushing position fixes out at every fix cycle rather than batching them, the BLE is essentially always active too, so you're not getting any idle headroom on either side.
The Power/Program Kit's supercapacitor system was designed with exactly this kind of sustained dual-module load in mind — the 24-hour runtime spec is based on powering the full module stack, so that's your cleaner baseline to work from rather than trying to calculate individual module draw and add them yourself.
My suggestion would be to post your specific transmission interval in the thread and tag it in the Dev Hub — Moamen or someone who's done a similar continuous-tracking build might be able to give you actual measured numbers from their setup, which will be way more useful than theoretical specs for this use case.
