Helpdesk

Good day,


 


I am doing a project with a Raspberry Pi 4B, StromPi V3 revision 1.1, 1000mAh battery Pack, Lte hat with gps module, and a CAN module. My StromPi configuration is so:



###########################################################################
StromPi V3 Serial Config Script (PYTHON3)
###########################################################################


---------------------------------------------------------------------------
  Main Configuration
---------------------------------------------------------------------------
[StromPi-Mode: 3 (mUSB -> Battery)]


Setting the StromPi mode
(1 = mUSB -> Wide, 2 = Wide -> mUSB, 3 = mUSB -> Battery, 4 = Wide -> Battery, 5 = mUSB -> Wide -> Battery, 6 = Wide -> mUSB -> Battery)


Mode (1-6): 3


--------------------------------------
[Raspberry Pi Shutdown: Disabled]


Enabling or disabling the Raspberry Pi shutdown (0 = disable, 1 = enable)


Shutdown enable/disable (0 - 1): 1


--------------------------------------
[Shutdown-Timer: 15 seconds]


Setting shutdown timer (seconds)


Seconds (0 - 65535): 15


--------------------------------------
[Battery-Level Shutdown: Disabled]


Setting battery level shutdown (0 = disable, 1 = below 10%, 2 = below 25%, 3 = below 50%)


Battery level shutdown (0 - 3): 0


--------------------------------------
[Serial-Less Mode: Disabled]


Enabling or disabling serialless-mode (0 = disable, 1 = enable)


Serialless mode (0 - 1): 0


--------------------------------------
[Power Save Mode: Disabled]


Enabling or disabling the Power Save mode (0 = disable, 1 = enable)


Power Save mode (0 - 1): 0


--------------------------------------
[Powerfail Warning: Disabled]


Enabling or disabling the Powerfail-Warning (instead of a shutdown) through the serial interface  (0 = disable, 1 = enable)


Warning enable/disable (0 - 1): 0


--------------------------------------
[PowerOn-Button: Disabled]


Enabling or disabling the PowerOn-Button Feature (0 = disable, 1 = enable)


PowerOn-Button enable/disable (0 - 1): 0


---------------------------------------------------------------------------
 Time&Date-Configuration
---------------------------------------------------------------------------
[Actual Raspberry Pi Time&Date]
[Time: 16:11:20]
[Date: Monday 18.03.24]


Do you want to change the Time&Date-Configuration? (Y) Yes | (N) No:N


---------------------------------------------------------------------------
 Alarm-Configuration
---------------------------------------------------------------------------
[Actual Raspberry Pi Time&Date]
 Alarm-Mode: Time-Alarm
 Alarm-Time: 00:00
 Alarm-Date: 01.01
 WakeUp-Alarm: Monday


PowerOff-Alarm: Disabled
 PowerOff-Alarm-Time: 00:00


Interval-Alarm: Disabled
 Interval-On-Time: 00 minutes
 Interval-Off-Time: 00 minutes


Do you want to change the Alarm-Configuration? (Y) Yes | (N) No:N


----------------------------------------------
 Configuration Successful
 Transfer new Configuration to the StromPi 3


###Please Wait###
-----------------------------------------------


----------------------------------------------
 Transfer Successful
-----------------------------------------------


 


Everything is working fine, when I remove the microUSB supply, the setup is still powered up for 15 seconds before shutting down. The problem is, I require the RTC funtionality from StromPi.


 


The script to sync the time with Raspberry Pi is executed every boot up. I charge the StromPi battery to 100%, I expect in a couple of days, the StromPi RTC to be actual, and sync with Raspberry Pi (update Raspberry Pi) upon boot up, but instead I always get the date from StromPi: 2018-05-01 00:00:00, and my battery is depleted to 10% (upon running adc-output). 

what is draining my battery? It is just over a weekend, so i expect a 1000mAh battery pack to be able to handle powering only the RTC.

RukasuRi

18.03.24 16:21

Hello RukasuRi,


Unfortunately, this is the normal behavior, since no real RTC is installed on the StromPi, but the microcontroller takes over this task.
Even when it is switched off, the StromPi still consumes a small amount of power in order to be able to react quickly to events like the powerOnButton, returning primary power supply or a set alarm, this drains the battery within 1 or 2 days.


Best regards


Tim (Joy-IT)

Tim

19.03.24 08:55

Hello Tim, 


 


thank you for your swift reply. Is there any way to turn off events like powerOnButton, alarm, etc? As there is no use case for me in this section. All I will need is the Raspberry Pi Shutdown in this case is 15 seconds.


 


Thank you

RukasuRi

19.03.24 11:25

Hello RukasuRi,


there is no other way than to rewrite the firmware for this. Unfortunately, we cannot provide a customized firmware for this. However, the firmware is open source and available on Github, so you can make special customizations yourself.


Best regards 


Tim (Joy-IT)

Tim

19.03.24 13:39

Hey Tim, would it actually not be a good idea to implement this? To be able to configure under strompi_config.py to choose whether or not to save battery during only battery mode during power down? I would understand all of these events to be useful when plugged in, where power on button needs to react as quickly as possible, or wake up alarm every interval. But all of these will be useless, if the battery deplets so quickly anyways.


 


It would be nice to be able to further configure what is needed during only battery mode, to be able to apply my application more consistently.


 


cheers

RukasuRi

21.03.24 08:29

Hello RukasuRi,


unfortunately, we are already at the memory limit of the microcontroller and therefore cannot add any larger functions like this.


Best regards


Tim (Joy-IT)

Tim

21.03.24 08:53

Ah okay, that is good to know. Thank you very much for you swift replies.Ah okay, that is good to know. Thank you very much for you swift replies.

Is there any contact person I could contact, if I have any trouble in customising my firmware?

RukasuRi

21.03.24 08:57

You can ask questions about the basic functions here in the helpdesk or contact our service team.


But please undestand, that we cannot guide you step by step through the development of the firmware.


Best regards


Tim (Joy-IT)

Tim

21.03.24 12:00