In an unreleased version of the GUFx defs, I have the "X" in the MAF conversion formula replaced with "KG" and this works to convert the MAF curve from kg/hr to lb/min. However it and the MAF payload are the only entities in the def file that are KG in the def file.

I'd like to make the formula native to lb/min so I know the conversion being done on the MAF transfer and MAF payload is the same formula used on every other number in the def file that is lb/min. At the moment, I don't have confidence that the conversion is being done exactly the same. Differences in the conversions, even slight differences, could make comparing BE-converted values in the def directly to the datalogged MAF value more difficult/invalid.

In the released GUFB def, the formula is:

Code: Select all

`X/0.0000024*3600/2.20463/2^31`

Simplifying all that math, I'm getting:

Code: Select all

`X/3.156261228`

Conversion from lb/min to kg/hr, I calculate to:

Code: Select all

`1 lb/min * 60 min/1hr * .45359237 kg/lb = 27.2155422`

So I thought I would post the dilemma here, get some thoughts & possibly some history as how the formula was devised, and ultimately to get a "cleaner" conversion formula for the MAF curve/payload that results in lb/min.

Now I realize that if I change the formula, this will alter everybody's MAF curve values as they see them (actual values in the tune won't change at all). I'll be sure to point this out when I post the latest defs. If this is a big-enough deal, I'll put 2 views of the MAF curve/payload in the def...one with the original conversion formula and one with the newer one.