LabVIEW
combine 4 stops for 4 case structure
@Mayur_VIenthusiast wrote:
Hey
I just understood. You want the output of those OR gates to go into that stop switch. You can use a compound arithmetic.
you really want to AND the 4 cases once they ALL complete and OR the stop control to exit any time....batteries have unique characteristics: charge and discharge rates, internal resistances, etcetera....so depending on the acquisition from each battery will determine whether to charge or discharge independently. this is not a simple thing to implement. batteries can be overcharged causing heat issues and the breakdown of the materials, shortening life. complex charging/discharging algorithms need to apply depending on the types of battery being used. this is a simple dirty simulation that does not consider the rate of change in a charge/discharge acquisition. this example is like powering a bicycle with a rubber band as opposed to using human muscles or better yet a gas engine...i wonder if you truly considered all the specifications and requirements,? it can be done...but at what cost? could'nt you buy an "off the shelf" $10 charger/discharger...
edit: tried to upload the VI and zipping it.... no bueno!
The main problem is code architecture. Once you fix this, your current problem will vanish automatically. 😄
You seem to be spending way too much time rewriting basically the same code over and over. You need to modularize the code and make it scalable. You have four instances of basically the same code. Are you planning to later scale this up for a few hiundred batteries? Would you then simply make it a diagram that is millions of pixels hight? Once you combine all the functionality for one battery into scalable code, you can scale it up for an arbitrary number of instances.
Same for the front panel. Make the controls for one battery into a cluster and then make a 2D array of such cluster (2x2 in your case). Suddenly, the entire code will be the size of a postage stamp and easy to maintain. If you currently want to change an error in the algorithm, you need to make identical changes in four different places. If you forget one place, bugs will be very had to find.
