LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Coulomb Counting for battery Management System

Good Evening,

I am using coulomb counting method for SOC estimation. It is working Properly. But In this VI, I used Global variable, File path to save in Text. I made it very Complex. Can we make it Simple in which i dont want to use project, just a VI can do this.

I am attaching Project.

 

Thank you in advance

0 Kudos
Message 1 of 5
(868 Views)

@AlienVi6789 wrote:

Good Evening,

I am using coulomb counting method for SOC estimation. It is working Properly. But In this VI, I used Global variable, File path to save in Text. I made it very Complex. Can we make it Simple in which i dont want to use project, just a VI can do this.

I am attaching Project.

 

Thank you in advance


Hello, @Prabhash26.  Here are some comments and suggestions.

  • When attaching a Project, do not compress it with "RAR".  Instead, right-click the Project file, choose "Send to:", then "Compressed (zipped) folder".  This ensures that all users of Windows can open your compressed folder.
  • I am not sure what you are asking.  Your VI isn't "very complex", but it is very "messy and hard to read and understand".  
  • Some suggestions.  Try very hard to have all of your wires running without bends (or as few, like 1, as possible).  Keep the wires short.
  • (Almost) Always use the Error Line.
  • Try to keep your code "compact" (95% of all my VIs fit on a laptop screen).  When it "gets too big", it probably shows a need for "hiding messy details in a sub-VI".
  • Are there good reasons that you have many "labels" (variable names, VI names, etc.) that are very long, wordy, and almost identical to each other, making it more likely that the user/reader/teacher will get confused?  Keep It Simple.
  • I won't even mention that every VI should have an Icon (even if only text) and a Description (a month from now, even you won't remember what this code is supposed to do).  Simplifying the code by using sub-VIs to "hide details" and rely on the VI's "name" (or Icon) and it's place in the sequence of VIs "defined" by their position on the (always present) Error Line, plus a brief Description naming the Inputs and Outputs of the VI, and what it is supposed to do will be a great help, to you, as well.

Bob Schor

0 Kudos
Message 2 of 5
(843 Views)

This is the VI, i m using

0 Kudos
Message 3 of 5
(806 Views)

Hi Alien,

 

please cleanup the VI and attach again...

 

(Now you got the advice to cleanup twice!)

Best regards,
GerdW


using LV2016/2019/2021 on Win10/11+cRIO, TestStand2016/2019
0 Kudos
Message 4 of 5
(799 Views)

Your code makes no sense, so I will just toss out something I have learned in testing large scale battery systems.

 

The main problem with Coulomb Counting is you have to assume the current remains constant between measuring intervals.

 

But when your charge cycle reaches the constant voltage stage the charge current is no longer constant. 

 

So your measurement interval needs to be as short as possible to minimise this error.

========================
=== Engineer Ambiguously ===
========================
Message 5 of 5
(770 Views)