Delved deep in the issue, Pejsa was not clear about it. However on page 76 in his book he stated that he adjusted his A function to equal the Mayevski a function at 2600fps.

this means that he uses the Ingalls conditions P=30inchHg, T=60F, humidity=67%.

The (ICAO air density)/(Ingals air density)=1.00371. Although the effects will be minor to the point of being neglible, I will adapt Pejsa's drag calculations in BfX to ICAO. Furthermore, I will add Mayevski Ingalls (under ICAO conditions) drag functions.

Lapua has radar measurements for many of its bullets. From this their specific drag functions has been calculated. I downloaded the free Lapua QuickTarget ballistic calculator from www.lapua.com and made a quick comparision of its output for the Lapua GB478 Scenar 6,8 gram (105 gr) 6mm NormaBR bullet. Later, after I have sorted out things with Pejsa's calculations (did he use US Army Standard Metro or ICAO conditions plus 78% humidity?) I will do a more elaborate calculation. I think the results are pretty good. The question is how well the QuickTarget calculations match the exact trajectory? Ideally one wants to compare calculations with the actual path properties too!

it works with my excel2007 on a 32 bit machine:

can you show me your =bfx_help(1)?

yes, bfx_u allows that the user can specify his/her own units for in and output. This is not only handy for the metric/imperial units, but also if MoA or a distance is desired.

Nice!

have look at =bfx_u(output_unit, value, input_unit)

... delving deeper in the book of Pejsa, he has used Ingalls, Us Standard Metro and ICAO data / tables. Which one he used to compute the (de)acceleration has to be reverse engineered...

BfX_C works as it should!

Bug in BfX_C is fixed

Dear all,
Lately I was confused which atmospheric conditions I used in BfX - it was too long ago to remember and it seemed I also forgot the physics behind the drag functions.

Okay. Drag functions are independend of atmospheric conditions.


In the calculation of drag you have to use a density of air. In BfX the ICAO conditions are used (15 degrees C and 101324,6 Pascal 0% humidity), which are common for present day ballistic programs. Just checked the code - I am sure again - it holds for any BfX drag function

There is also the US Army standard meteo conditions (15 degrees C and 99991,6 Pascal), frequently used in the past. BFX_C which is used to convert ballistic coefficients, contains a bug thatI will soon fix. It incorrectly converts the ballistic coeficient as it assumes that BfX uses the US Army standard meteo conditions. if you enter
=BfX_C() and you  see the output BfX_C(T=15 [Celcius]; P=99999.76 [Pascal] []) then this is erronuous.

The new version will show BfX_C(T=15 [Celcius]; P=101324,6 [Pascal])

Expect the correction soon.

I have added, inspired by a posting of jrmy_1, the iphy (inch per hundred yards) and cphm (cm per hundred meter) units of angle  iphy=tan(angle)*100*0,9144/2,54) and cphm=10000*tan(angle)

e.g. =bfx_u("iphy";1;"moa")

to install the update you can use the setup or simply replace the .xll file

by the way, one of the most commonly ignored issue to achieve a one shot one kill setup is the calibration of the sights. Is the scope according to the specs?

I have a scope - 230 euros - that has a reasonable optical quality, and has an excelent mechanical quality. I see the black dot in the sight and that is good enough for me. Anyhow, the optical quality was good enough to become 1st in the Dutch 2008 300-500-600 yards (yes yards in the Netherlands too!) F-Class championship and third in 2009. In 2010 the beautiful military shooting range was (probably temporary) closed for us  .  Mechanically the scope is very constant in its moa/click and has no hysterises I know of. But instead of being 1/4 moa per click it is 0,21 or so. And that is an issue if you have to depend on calculations (the rifle was zeroed at 100m and I shot a lot at 500m).

I have a workbook illustrating a scope calibration.

regarding humidity, I did not capture its effects in BfX_C.

Welcome, in principle you want a fire control system for a hunting rifle. For target shooters BfX does the job, mostly because the elevations are never in excess of 15 degrees and we are allowed to sight in.
In some  hunting situations (which do not exist in our almost flat Netherlands) you have to shoot up/downhill and the elevations are such that BfX becomes too inaccurate. Furthermore BfX does indeed not include the effects of spin drift and the Coriolis force. They would complicate the BfX-interface and I found  their practical influence, compared to those of wind, negligible. I you would, you can add some formulas to Excel and compute their effect. To release software which has all the capabilities you mention is entirely possible, but I will not do that. There are people who shoot something else than paper targets, use other launchers then rifles and who aim at our soldiers in the mountains of Afganistan.

The last time I checked I found that Excel on Windows mobile does not support add-ins. In my experience the use of tables printed on paper (covered with plastic if you like) is much easier than the use of electronic devices during matches.  I simply do not have the ability to think when there is time pressure.

In the spreadsheet GettingStarted with Excel you will learn everything about generating such tables, including the effects of temperature and pressure. I am not sure if I have still included the effects of humidity, since they are so small for rifle bullets. It will also educate on the use of G1 versus G7 drag functions.

Brian Litz sells a pocket calculator that might help you http://www.appliedballisticsllc.com/index_files/Products.htm

Because I develop with Dutch as the locale (e.g. 2.000.000,3 in Dutch means 2,000,000.3 in the USA, Australia and a lot of other "Imperial" countries) I have to delimit cell formula's with semicolons e.g. bfx_d(740;30;0,5). In Australia one would enter bfx_d(740,30,0.5). Please note that in VBA only the imperial notation is used, the issue is only with the cells themselves.

Luckely, for downloads this is not an issue.

Excel does convert automatically to the active locale, and I checked that. This means that my downloads should be able to run without conversion. Indeed, I run the SA-Fclass spreadsheet without problems and even didn't note that it was converted (and vice versa from English Australian locale to Dutch)

Remains only the issue with "unwarned" persons following my screenshot examples (typing ; instead of ,).

I will put some remarks on the website.