Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Scheduled charging on Power cut #332

Open
Aylaas opened this issue Jul 1, 2024 · 3 comments
Open

Scheduled charging on Power cut #332

Aylaas opened this issue Jul 1, 2024 · 3 comments

Comments

@Aylaas
Copy link

Aylaas commented Jul 1, 2024

Hi @matth-x,

I have a test case scenario where there is an existing schedule for a charger, and power goes off.
In this case, I expect my charger to retain the schedule profiles and start charging on power on, if the scheduled profile still holds good(schedule duration is valid and within the bounds).
But, while testing this case, I don't see the charger starting to charge on its own on the power on and the schedule still active.

Can you please provide feedback on this test case, if valid please provide the insights on the same.

Thanks,
Ayla.

@matth-x
Copy link
Owner

matth-x commented Jul 1, 2024

Hi @Aylaas, by default, MicroOcpp stores all charging schedules locally and resumes transactions after a power loss. Is there any hint that the flash access doesn't work properly?

@Aylaas
Copy link
Author

Aylaas commented Jul 17, 2024

Hi @matth-x ,
After Power loss, only the latest schedule is retained.
Suppose I set two profiles, one with "ChargePointMaxProfile" the next one with "TxDefaultProfile", there is power loss, on next power regain, only "TxDefaultProfile" is retained and the charge profile count is 1.

How do I retain all the schedules and read back on next power cycle.
Please consider priority

Thanks

@matth-x
Copy link
Owner

matth-x commented Jul 28, 2024

This implementation normally keeps all schedules. I assume that something with the flash memory goes wrong, for example the flash goes out of memory. In this case MicroOCPP would show error messages on the log. Any suspicious messages there?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants