... I don’t want to just know what my da is when I zero, I want my kestrel to know what the DA was WHEN I zeroed ...
Exactly !!!
==
Two points on this ...
01 - What I've been calling "device 01" ... i.e. "Real AB" ... i.e. the stand alone AB app which does not connect to the kestrel ... DOES separately record the DA when we zero ... and then when we adjust the DA for a given shot, still uses the original DA as part of the process of computing a solution. It uses both DA's. I can tell this, because sometimes the trajectory will show the 100yd zero with an elevation offset of other than zero ! Which is fine and correct under some conditions.
02 - I am not in the "truing" school. I've tried to read everything I can find that Brian Litz (BL) has written ... on the subject at hand ... and some of it multiple times .. the mantra of "remove variables" sticks hard in my head. I want setting up a gun in any of these devices, 01, 02, 03, or 04 to be fast and easy with the fewest possible variables. The whole idea of a "truing" process is a big variable. And adding such a variable is not something I want to do. I'm looking to minimize the variables. Conditions can be different from day to day ... and what was "true" one day will not be on another.
==
Also, while this thread is 100% focused on the kestrel, I'm trying to use 4 devices separately and together to compute shooting solutions to the extent possible ...
01 - Real AB
02 - RAPTAR S
03 - Kestrel 5700
04 - Kestrel AB LINK
and so my activity is really "out of scope" for this thread.