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
Equipment Discussions
LabRadar question
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: 1643179" data-attributes="member: 104268"><p>The version I have is capable of controlling all the features that the buttons will do. It's still pretty terrible, and you can't revisit strings, name them, or add notes. It's still better than pushing the buttons though.</p><p></p><p></p><p>I don't think it should cause any trouble, and I haven't noticed any issues. It takes 10-15 milliseconds after the shot to trigger and start receiving data, so the bullet has traveled 10-12 yds before it receives the first tracking data. V0, and any distance you set inside that, is calculated by extrapolation from wherever it starts tracking the bullet.</p><p></p><p>This is why you can sometimes get really wonky data for V0, but good data for the rest of your set distances. If the unit has bad tracking for the first couple of milliseconds, it will extrapolate a nonsense velocity from those first few points. Once the tracking settles in, it does fine from there on out.</p><p></p><p>I have a data culling spreadsheet setup, which regresses a line through ALL of the data. It can use the equation for the regression to calculate the velocity at any distance, and greatly reduces the influence of a few bad data points.</p></blockquote><p></p>
[QUOTE="entoptics, post: 1643179, member: 104268"] The version I have is capable of controlling all the features that the buttons will do. It's still pretty terrible, and you can't revisit strings, name them, or add notes. It's still better than pushing the buttons though. I don't think it should cause any trouble, and I haven't noticed any issues. It takes 10-15 milliseconds after the shot to trigger and start receiving data, so the bullet has traveled 10-12 yds before it receives the first tracking data. V0, and any distance you set inside that, is calculated by extrapolation from wherever it starts tracking the bullet. This is why you can sometimes get really wonky data for V0, but good data for the rest of your set distances. If the unit has bad tracking for the first couple of milliseconds, it will extrapolate a nonsense velocity from those first few points. Once the tracking settles in, it does fine from there on out. I have a data culling spreadsheet setup, which regresses a line through ALL of the data. It can use the equation for the regression to calculate the velocity at any distance, and greatly reduces the influence of a few bad data points. [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
Rifles, Reloading, Optics, Equipment
Equipment Discussions
LabRadar question
Top