Filter

2025 BigJimFish Review / Article blog: More 350L, Garmin and Athlon Chronos, Leopold Mark 4HD, BurstFire, Field Optics Research, videos and visits

Update 9–12-2025

I did an all day range day at the long-range facility Wednesday. Part of this was slated to be tripod shooting practice with the 350L to get a better handle on what I think is reasonable for ethical deer kill distance all factors, including myself, considered. Since I brought my dad along, I also planned to get a lot of photo and video for upcoming 350 articles including as much through the lens trace video as possible though the Vector X binos. Boy did we get some good video of that. There aren’t many trace videos on YouTube and the ones I have seen are generally so bad that you can’t make anything out. We got some good ones though and I plan on making up a good compilation video. People are always asking me what trace looks like and how to spot it. This should be of help both for that and for seeing the bullet itself as many of the videos show the fat, fairly slow, 350L bullet pretty clearly whereas other show the trace disturbance from a faster, smaller, .223 as well. I also got some video of .223, .308, and 350L on the same targets under the same lighting conditions. It’s pretty interesting to see the trace difference and the huge difference in splash on the target.

2025 9 12 vector x and calypso wind dad shooting.jpg

Syncing up the Calypso AB mini ultrasonic wind meter and the Vectronix Vector X binos to base the windage calculations in applied ballistics on live wind readings

In a big surprise, when I was setting up software for the range trip, I updated the Vectronix Vector X, the AB Quantum app, and the Calypso AB ultrasonic wind meter and found that the wind meter now pairs with the Vector X binos and works as more than a stand alone wind meter. When paired with the binos the Calypso wind readings are used as the basis for the windage calculation and the output updates each time you range the target. I have had this wind meter for around a year now as I was sent one in beta. It was a while before the first iterations of the supporting software (early april for AB Quantum with that functionality) were released and I did not have luck in getting the AB meter to work at that time with any of my AB binos though I recall it saying it paired with the Sig binos at that time. That pairing didn’t seem to actually work to produce calculations based on active wind readings and the wind meter didn’t even pair with the Vectronix or Leica binos at that time. Every once and a while I have tried it out wind meter again but this was the first time all the software and hardware clicked. Not only did it work, but it was also seamless and easy. The binoculars ever re-acquired the calypso wind meter without issue each time they were awakened from sleep mode. It was pretty exciting. Now I need to dig into the specifics of exactly if/how all of this works with multi-target range cards for competitive shooters. For someone looking to range a target with an AB equipped rangefinder and then shoot it using AB calculated data based a wind reading captured at the time of ranging, the system is very easy and simple to use though.

2025 9 11 tts 367yd vector x CLPS.jpg

The view through the Vectronix Vector X binos while connected to the Calypso AB miniultrasonic wind meter. The binoculars display “CLPS” for the wind source.
  • Like
Reactions: flogxal and aam

Maggie’s Man's Best Friend Thread

View attachment 8765637
This is our Hank, he left us last week after 15 years... he was the BEST Boy!

Young Oscar is now the furry man of the house at just over a year old.
View attachment 8765639
He's coming into his own nicely. Maybe after a bit we'll find a furry buddy for him


What a kind and gentle face.
Fifteen years together, I'll bet you have some great memories
My condolences on your loss

Sidearms & Scatterguns If you had $2000 to spend for a range pistol…

Sig P320 Legions should be getting pretty cheap these days… LoL

I do actually have one, and it’s a very nice shooting pistol…and I even almost trust it after confirming the slide attachment and trigger are gtg. That said, my vote for your budget would be a used CZ Shadow 2 and send it to Cajun Gun Works…you’ll have a great gun and some $ left over for other gear, some extra training ammo, and maybe some professional instruction.

You might be able to find a well-used STI/Staccato at that price if the seller is motivated, but that CZ is a very nice shooting pistol and a known commodity.

Edit: That DWX looks really nice, but I have zero experience with it.

I won’t mention the other options that I prefer, but trust me when I say that if you can save up enough to double your budget it will be worth it. Sounds crazy, and TBH, I can’t shoot as well as my pistols are capable of performing, but it’s nice knowing I’m the LIMFAC vs. the machine. LoL

Someone murdered Charlie Kirk

Login to view embedded media
I can post a lot more if you wish. Zionist are a murderous pedophile blood cult.


Simon of Trent would be a good starting point.
And sadly they've deceived and manipulated many otherwise good and decent Jewish people, not to mention the bulk of 'Christians' to support them.....................
Jesus H. Christ!
How fucking stupid can they be???
Don't they even have an inkling of just how quickly this can go bad, REAL BAD... if they keep going down this road?


Seattle Central College
View attachment 8765715
No, they dont. They think they do, but theyhave no concept of the amount of violence that could be unleashed if we're pushed past the breaking point.

I've made the evil man leave my house but he's not far away and I have his address. I can bring him back at a moments notice.

Precision Rifle Gear New Athlon Rangecraft Chronograph-Garmin Xero Killer?

@Turkeytider - Addressing your 2 posts here based on the 2 posed or implied questions:

1) How has Athlon responded to these results?
2) Can the Athlon work for some shooters as it is?

I'll try to be succinct as possible here:

1) How has Athlon responded to my results? First off, reiterating, I'm not affiliated with any of these companies. I bought my first Garmin and Athlon units, and I won my LabRadar LX at Ko2M - but would have bought one if I hadn't won it. My "second unit" of each of these brands has been loaned to me either by the companies or their reps, just to help me avoid long-term borrowing units from other shooters and enable improved data capture opportunities (such as the Static vs. Gun Mounted Velocity Test I shared), really just out of good faith collaboration.

Second, and really emphasizing that reiteration, I really won't pretend I'm materially important to anything Athlon is doing, or Garmin or LabRadar. As I approached this comparison test, I reached out to each of these companies and asked if there were any ways I would fuck up and misrepresent the untis, or any ways I could unfairly bias the test, and if there were any specific features they felt made their brand/model stand out. Most companies were interested in discussing the test, but again, I'm just a peckerwood who lives in the hills with too many guns, and all I did was make a few phone calls - the companies just want to support the tribal knowledge of our universe, so they were willing to help out in good faith and loan the demo units.

With that out of the way... Regarding how I see Athlon responding to user feedback, including my own: Specifically, I contacted Athlon because 2 units I had on hand were reading incremental offsets when compared to other chronographs. Athlon offered troubleshooting processes for temporary solutions, and then within a week, I received a text that they were issuing a firmware update the next week which should fix the issue - and it DID improve the occurrence from nearly 100% of sessions down to only 1/3 or 1/4 of sessions. Equally, I had connectivity and sync issues with my 3rd Athlon unit, and their response was again, advice for immediate troubleshooting processes - which did not work - but then after about a month of manually entering hundreds of data points, a firmware update solved that problem. I do know other users are having issues, and I know Athlon is still working on some - it seems the connectivity/sync issues are solved for almost all iOS users, but still not quite ironed out for Android/Samsung phone users, so that's still work in progress. All of that is to say that I have seen firsthand that Athlon is offering CS to productively support user issues, and that they are making incremental firmware updates to their app and to their unit software to improve reliability.

I also acknowledge, as objectively critical as I am of ALL of these units, the Athlon Velocity Pro simply is younger in market and is racing to catch up. LabRadar and Garmin have the luxury of having already survived many of these growing pains because they already have years of head start in this practice - LabRadar had the V1 on the market for a decade before these others, and Garmin has had multiple Radar devices on the market for a few years before the C1, and has had dozens of bluetooth communicating devices on the market for over a decade. So it's reasonable to expect that Athlon would have more CURRENT issues as they are sprinting through their learning curve to catch up - a year or two from now, the expectation of nearly-perfect functional execution is more reasonable than it is today.

2) Can the Athlons work for some users as is? As I mentioned above - We're 7 pages deep into this thread, so I know my post was kind of lost in the depths at this point, but I did acknowledge in this thread, the Athlons can be fruitfully deployed by a great percentage of shooters. Who would be at risk, in my opinion, and how?

--> With the intermittent high/low offset issue: ELR shooters would be sensitive to the ~30fps spread of potential results I've seen. This is roughly +/-0.5% error from truth, so as good or better than any common optical chronograph from history, but still looser than we want. But an ELR shooter would sail above or sink below targets. A PRS shooter can likely honestly be just fine with this error, and a shooter with a careful sense of attention might simply restart their Athlon when they notice a marked high or low result for a known load.

--> Shooters watching closely velocity as a means of tracking barrel life or watching for carbon ring indicators might be tricked by the offset. Again, simply resetting the unit would correct or confirm the change, but this would be an extra step.

--> Someone trying to compare multiple loads spread over multiple days, where +/-0.5% might represent the difference between each load could be mislead into trusting incorrect relative results. Does that difference of 30fps really matter? eh, probably not. But if I'm trying to compare, say, two primers, or two lots of powder, or two different brands of cases, or worst of all, looking at one set of charge weights one day against any of the other parameters on the next day, that intermittent offset issue could bite me in the ass. BUT, if a shooter is sure to shoot both comparative samples on the same day, they'd be just fine.

--> An extension of the latter, but an incredibly small niche, if a shooter is trying to test for temperature sensitivity of their load, the intermittent offset issue could lead to false results in the correlation curve.

I don't think that the higher volatility I've seen with the units (inherent noise between readings of a string) is really of consequence for anyone. Over large sample sets, the SD's (strangely) seem to end up very similar, but when you look at the results as a trendline, the volatility is visibly higher... Inconsequential, overall, maybe I guess a guy with a Garmin could post online that display picture with 5 shots and an ES of 7 but the Athlon might read that same string with an ES of 10, but other than bragging online, that's really an inconsequential difference. It looks ugly to a data hound, but an application/field engineer recognizes noise as noise, and signal as signal.

I also don't think even the guys riding the ragged edge of Power Factors or velocity speed limits could get themselves in hot water, because the maximum offsets I'm seeing are in the 20's fps... Maybe if the absolutely unlikely coincidence of a guy measuring their load velocity at home and reading 20fps LOW then going to a match and being checked by a different Athlon which intermittently measured 20fps HIGH that day, they could swing 40fps and end up above the speed limit, but restarting EITHER unit would bring them both within 20fps of each other, so I really don't see that as a REAL issue.

And again, I do think the offset issue will be resolved by future firmware updates. It has been partially solved already. The volatility is still very tight, set up is fast and easy, nothing downrange, so they're always going to be superior to any optical chronograph, and most folks will find them easier to set up than Magnetospeeds, so ultimately, at sub $300, with a little higher volatility and some quirks compared to the $500 Garmin or LabRadar, it's still a great unit.

Maybe another statement which might mean a lot to folks - I'd rather buy an Athlon than a LabRadar V1 at the same price today.
I have also been running the Garmin side by side with the Athlon and would like to pick your brain on a couple of things. I am still using release firmware on the Athlon BTW, I will be updating it before my next range session but was initially hesitant based on the fact Garmin had updates where their unit operated quite poorly relative to the release firmware. Last range session I had a few mis-reads though so I'm going to update now.

1) Do your Athlon units operate well in the 4"-10" distance from the muzzel range the directions indicate? Mine misses shots when its that close and seems to want to be 20+ inches behind and to the side. I have not mounted mine to the rifle, are you getting good results in that configuration?

2) When you say the Athlon is not showing as good of an SD and ES and that the data is more volatile, are you seeing something like 1-2 shots out of 50 that are off by 100fps and the rest of the shots fall in a similar pattern to the Garmin or does the overall spread look wider? How much difference are you seeing between Garmin and Athlon SD and ES numbers in a data set? Do you think were are talking random individually misread shots, systematically less precision, or both?