Accuracy of Garmin Xero chronograph.

Marbles

WKR
Classified Approved
Joined
May 16, 2020
Messages
5,039
Location
AK
An interesting anadote, perhaps a difference in pressure, perhaps an issue with the Garmin chronograph.

Yesterday morning for a zero check, I shot 10 rounds over @Marty Garmin, got a velocity of 2858 fps for 10 shots. Historically that load has gotten my 2700-2740 fps in temps very similar.

At the end of the day, and about 95 rounds later, I shot 14 rounds over my Garmin, average 2761 fps, max was 2826 fps.

I turned off my chrono, then Marty wanted to shoot a few rounds, so I turned it back on and he put 4 rounds over it (less than 5 minutes in between). These 4 averaged 2856 fps with a minimum velocity of 2830.

So, the 100 fps was not a difference between the chronographs.

My suspicion is that positioning of the Garmin made the difference, I need to go back and play with it.

All rounds were loaded in the same go a few weeks ago. It is a slightly compressed load, so no way to double fill and adding even 0.5 gr of powder takes it to very crunchy and needing a drop tube to avoid nose deformation. Plus, every powder charge is measured with the draft cover over the scale and rejected if off by 0.1 of a gr. So, I don't think it was the load.

But, it does have me wondering. I think what I really need to do is true velocity on the range and stop treating the chronograph as definitive. I've not done the math, but a doppler only measures movement towards or away from the source, so a slight angle will result in a slower reading. This is what I suspect caused the difference. But, does a few degrees of offset actually result in a 3-4% error?

I had better luck at extend range with the 2858 fps in my ballistics calculator, but with the variation in wind it is hard to say if that was actually due to elevation or just the little 77 TMK getting pushed around, I mean it was sub sonic prior to getting to the target in some cases.

I will get out to the range at some point and play with it, but probably not in the next month due to family obligations.
 
Interesting. And guys seemed to be so put off by the single sample results of S&S testing of the athlon unit.

I'm looking forward to seeing if you can reproduce the results and determine the cause
 
  • Like
Reactions: BLJ
Interesting. And guys seemed to be so put off by the single sample results of S&S testing of the athlon unit.

I'm looking forward to seeing if you can reproduce the results and determine the cause
Yeah, I had to go catch up on that thread.
The issue with trueing is you also have drag, what is inaccurate, the velocity or the drag calculation? Hard to say with certainty if the issue was really one or the other, but trueing corrects for either.
 
Yeah, I had to go catch up on that thread.
The issue with trueing is you also have drag, what is inaccurate, the velocity or the drag calculation? Hard to say with certainty if the issue was really one or the other, but trueing corrects for either.
Yes, I figured whether Garmin or Athlon I'd still be trueing at distance, but at least I'll be able to get velocity easier and in more places than using my Caldwell Chrony.

I at least hope that whatever error there is within the Athlon measurements that they are consistent without much influence from weather or device position.
 
So, a 3 degree change in the angle between the hypotenuse and adjacent sides results in a greater tha 5% change in the length of the adjacent.

The hypotenuse would represent true velocity, angle would represent the off set of the chrono from parallel. The reason this works is distance traveled (hypotenuse) vs distance traveled at a 90 degree angle to the chrono (adjacent).

So, it is probable the difference is do to how far from parallel the doppler radar signal is from the path of flight.

This lines up with the only obvious change being that I had picked up, then put back down the chronograph.

20250504_182000.jpg
 
So, a 3 degree change in the angle between the hypotenuse and adjacent sides results in a greater tha 5% change in the length of the adjacent.

The hypotenuse would represent true velocity, angle would represent the off set of the chrono from parallel. The reason this works is distance traveled (hypotenuse) vs distance traveled at a 90 degree angle to the chrono (adjacent).

So, it is probable the difference is do to how far from parallel the doppler radar signal is from the path of flight.

This lines up with the only obvious change being that I had picked up, then put back down the chronograph.

View attachment 875692
3 degrees would be alot.

I ran the 22 creed with a garmin each side yesterday. (My one and the one the range leaves setup) was 15fps difference without being critical in aligning either of them (MV 3150-3250)
 
I always set mine directly below the barrel if possible, and try to point it right at the target, it's been extremely consistent that way and I use it a lot
 
I always set mine directly below the barrel if possible, and try to point it right at the target, it's been extremely consistent that way and I use it a lot
I have always put mine off to the side, the high readings came from closer to under the barrel. I'm not sure how that would make a difference, but it is something I need to play with.
 
Here's a guy shooting with 5 on either side, varying distances from center.

One of the units (2nd in from outside) read 100fps slower than the rest. 100fps is a big difference, so I'm curious if 10% may be off by that much, or if it's a 0.1% chance and this guy just got one in his batch. Doesn't really address your issue about the same chronograph reading differently on different days, but likely shows that the distance from the center is likely not the issue. Perhaps it was placed facing slightly off-angle as suggested.

I'm out of central Oklahoma and have the Xero. If anyone wants to meet up with their Xero's or Athlon for a comparison just hit me up.
 
Back
Top