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

Support for battery charging profiles #158

Open
sorlok72 opened this issue Aug 20, 2017 · 8 comments
Open

Support for battery charging profiles #158

sorlok72 opened this issue Aug 20, 2017 · 8 comments

Comments

@sorlok72
Copy link

Would like to see charging of different battery types, sizes and charging power.
Like LiPo, NiMH, LiFe, etc. Or perhaps make it with profile, no new battery types can be supported
without new firmware needed.?
Thanks for a great product

@sorlok72 sorlok72 changed the title Feature Request: Support for battery charking profiles Feature Request: Support for battery charging profiles Aug 20, 2017
@prasimix
Copy link
Member

Thanks for that. It will be nice if you or someone else can provide instructions for charging various battery types. In the mean time I hope you can manage it by using simple list with just one or two steps:

  1. Charging time with max. charging voltage and charging current
  2. "float" time with voltage limit and small current
    If second step is not needed you can define that channel output is disabled on the list end.

@mvladic: this is a first good case for implementing "program" infrastructure. Such program should be uploaded from EEZ Studio and include instructions and own set of GUI pages for displaying and entering program parameters, etc. If we provide that "program" can also store and retrieve data from SD card (what could be beneficial for battery models, charge logging, etc.) then we should first to address #88.

@prasimix prasimix changed the title Feature Request: Support for battery charging profiles Support for battery charging profiles Aug 20, 2017
@DwaineGarden
Copy link

+1. I would love to see battery profiles based of the data sheets specs for different batteries. Even up to a vehicle 12volt battery.

@sorlok72
Copy link
Author

Alter researching a bit on the subject, there are 3 ways to charge LIPO, LiFo etc.
Balanced charging, individual measuring and charging each cell
Charging all celle at once, monitoring individual cells
Just charging all cell at once, not nice/safe

So to do this would require allot of channels and sens lines.
I dont think this is doable without HW changes,

@prasimix prasimix reopened this Aug 30, 2017
@prasimix
Copy link
Member

Thanks for comment, but this issue is still valid for some older type of batteries like Pb, NiCd, NiHm or that is not interesting nowadays to anyone?

@sorlok72
Copy link
Author

sorlok72 commented Aug 30, 2017 via email

@momo-aux
Copy link

To load a NiMh battery there should be some kind of trigger that can be used to detect a -5mV voltage drop and if that occurs stop the charging process.

So would it be possible to have a programm in the firmware that I could activate to make this happen?

Like: Set the PSU to 11.6V with 150mA, connect the 9.6V NiMh 1500mAh Battery pack and start charging. If the Voltage raises all is ok. If Voltage starts dropping after some time, the NiMh Battery is fully charged and the PSU should power off.

@prasimix
Copy link
Member

prasimix commented Feb 28, 2018

Currently it's not possible to do that in firmware, i.e. without external agency, that is PC connected via USB or Ethernet. In that case it's possible to write a simple script that will measure voltage change tendency and stop the charging process when mentioned criteria is met. We are currently working on EEZ Studio that has SCPI console that can be used for communication using SCPI commands. In next step we'll add "macros" or simple language such as Blockly, etc. for performing tasks like one that you asked for.

@momo-aux
Copy link

Great news, thank you.

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

No branches or pull requests

5 participants