Quote:
Originally posted by gmat
What i had in mind (still need refinements, take note):
- Place elements in a GUI or a XML input file
- Solve the flow rate (by correlating backpressure vx flow data of each element)
- then solve the heat with flow / heat data
- finally with add up heat transfer coefficients and solve the temperature
|
gmat,
I look forward to hearing what you come up with as an architecture. I sent a PM to Joe today, about setting up a category for simulator discussions.
Quote:
Originally posted by gmat
Adding tubing is quite easy, it will be treated as strict equivalent height. Actually, one will just have to input approx. total length, # of elbows, tees and other fittings. All fittings will be treated has having a flat backpressure vs flow response (= constant backpressure) but if anyone has more data about this, it will be no problem.
|
If I understand correctly, you're suggesting just using a constant for fitting headloss regardless of flowrate?
I think the PQ curves for fitting will generally follow the equation:
dP = Rf * Q^2
where Rf is a value I've been calling 'flow resistance'.
(If someone knows a proper name for this equation and/or more standard terminology for the value 'Rf' please let me know. 'Pipe length equivalent'? My background is electrical engineering and this equation is like a hydrodynamics equivalent to Ohm's law.)
BillA's waterblock data matches this equation very well. His rad data doesn't match so well. More complex equations will need to be determined for some rads.
In cases where the equation holds true, determining P vs Q for the loop is just a matter of adding up each component's Rf value and applying the equation to the sum.
Even if fittings don't match that equation perfectly, using that equation and an Rf value for the fitting, will yield more accurate results than a constant.
Quote:
Originally posted by gmat
Since87: i am a software engineer, that helps 
XML is just a text format. The good thing is it's universal. You can export XML files from Excel for example. And parsing XML files in Java is about my day job.
For each component i'll make a 'black box' object model in Java.
I envision releasing first the XML file format so ppl can contribute easily, by adding components. You'll just copy the file in the appropriate directory, launch the software and you'll be able to include it in a sim run.
All i have to do then is to code the simulator itself (rather quick) and the GUI (rather long)
I'll get back there to make sure my maths are all right.
|
So are you volunteering to be lead programmer?
Do you think that splitting the coding into seperate sections so that others can help is practical?
I don't understand this stuff enough to be able to picture what you are talking about. Unfortunately Excel 97 doesn't appear to support XML output. Time for me to upgrade I guess.
Can you post an example of an XML component model?