Forums
New posts
Search forums
What's new
Articles
Latest reviews
Author list
Classifieds
Log in
Register
What's new
Search
Search
Search titles and first posts only
Search titles only
By:
New posts
Search forums
Menu
Log in
Register
Install the app
Install
Forums
Rifles, Reloading, Optics, Equipment
Rifles, Bullets, Barrels & Ballistics
Calculating B.C. with LabRadar. Tutorial on my method.
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
<blockquote data-quote="entoptics" data-source="post: 2618694" data-attributes="member: 104268"><p>Based on the piles of replies so far, I think you're way off on the interest level...<img class="smilie smilie--emoji" loading="lazy" alt="🤣" title="Rolling on the floor laughing :rofl:" src="https://cdn.jsdelivr.net/joypixels/assets/8.0/png/unicode/64/1f923.png" data-shortname=":rofl:" /></p><p></p><p>Funny enough though, I think your method of pulling the pre-programmed values might be just as much work as mine, as I'm assuming you'd have to manually record the near/far from the LabRadar menu or App, unless you're using the shot report file generated on the memory card. My method, once you have it down, involves a couple of mouse clicks, and then it provides the near/far in the spreadsheet.</p><p></p><p>As mentioned, I'm guessing my good tracking is a result of my excellent shooting location, though some credit probably goes to my aiming/stabilization scheme.</p><p></p><p>I've not yet done an experiment on tracking distance vs B.C. My thought is that the further the bullet has to decay, the more any local errors will be averaged out. If there's a 0.1% error in velocity associated with the LabRadar, then a 50 yard tracking file would compound the errors twice as much as a 100 yard tracking file. That said, it sounds like your method is very good if you're only getting 3 in the 3rd variation. I see far more than that with my method.</p><p></p><p>Regarding the pre-calculated velocity settings from LabRadar, you might check out this post #4 in this thread again (it appears I was actually replying to your comments back in 2018 <img class="smilie smilie--emoji" loading="lazy" alt="🤨" title="Face with raised eyebrow :face_with_raised_eyebrow:" src="https://cdn.jsdelivr.net/joypixels/assets/8.0/png/unicode/64/1f928.png" data-shortname=":face_with_raised_eyebrow:" />)...</p><p></p><p>[URL unfurl="true"]https://www.longrangehunting.com/threads/calculating-bc-with-labradar-it-works.202475/post-1438957[/URL]</p><p></p><p>Firmware updates since that post have improved the issue a fair amount, but as I mentioned in the recent tutorial video, it still happens too often for my taste. For someone that collects a lot of data like you, it's probably less of an issue, as it's rare enough to average out over the long haul. For those that only shoot a few 3 shot groups to develop a load (or worse, those that fire 1 shot ladders looking for "nodes" <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite11" alt=":rolleyes:" title="Roll Eyes :rolleyes:" loading="lazy" data-shortname=":rolleyes:" /> ), it might end up being problematic.</p></blockquote><p></p>
[QUOTE="entoptics, post: 2618694, member: 104268"] Based on the piles of replies so far, I think you're way off on the interest level...🤣 Funny enough though, I think your method of pulling the pre-programmed values might be just as much work as mine, as I'm assuming you'd have to manually record the near/far from the LabRadar menu or App, unless you're using the shot report file generated on the memory card. My method, once you have it down, involves a couple of mouse clicks, and then it provides the near/far in the spreadsheet. As mentioned, I'm guessing my good tracking is a result of my excellent shooting location, though some credit probably goes to my aiming/stabilization scheme. I've not yet done an experiment on tracking distance vs B.C. My thought is that the further the bullet has to decay, the more any local errors will be averaged out. If there's a 0.1% error in velocity associated with the LabRadar, then a 50 yard tracking file would compound the errors twice as much as a 100 yard tracking file. That said, it sounds like your method is very good if you're only getting 3 in the 3rd variation. I see far more than that with my method. Regarding the pre-calculated velocity settings from LabRadar, you might check out this post #4 in this thread again (it appears I was actually replying to your comments back in 2018 🤨)... [URL unfurl="true"]https://www.longrangehunting.com/threads/calculating-bc-with-labradar-it-works.202475/post-1438957[/URL] Firmware updates since that post have improved the issue a fair amount, but as I mentioned in the recent tutorial video, it still happens too often for my taste. For someone that collects a lot of data like you, it's probably less of an issue, as it's rare enough to average out over the long haul. For those that only shoot a few 3 shot groups to develop a load (or worse, those that fire 1 shot ladders looking for "nodes" :rolleyes: ), it might end up being problematic. [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
Rifles, Reloading, Optics, Equipment
Rifles, Bullets, Barrels & Ballistics
Calculating B.C. with LabRadar. Tutorial on my method.
Top