Too much powder or is my barrel really fast
- Thread starter whatsupdoc
- Start date
Damn, that's a nice setup you have. I have a POS chrony that works sometimes.
One of the issues it has is that it'll throw out some crazy numbers like that from time to time.
The way these things operate is that they use the mean value theorem in order to find the max between two points on a curve (in this case the curve is the change in velocity). It's very fast and very minute but this is how all radar guns and Chrono's work.
What happens, and I'm reaching here it's been a while since I looked into this problem, but on mine the bullet passes through two gates and the shadow of the bullet is what trips the sensor. It's supposed to measure the time it takes to go from one gate to another and display that as rate, the velocity, distance/time. I'm assuming yours does something similar, it's really the only way to do it.
On mine, it has to do with light. Improper light, shade, overcast, too much light --I'm lucky when it works. And yeah, I get the 8000fps crap too.
At least it's far off enough you know it's not a proper reading.
I'd call the mfg. and see what solutions they recommend. Positive they're familiar with it.
One of the issues it has is that it'll throw out some crazy numbers like that from time to time.
The way these things operate is that they use the mean value theorem in order to find the max between two points on a curve (in this case the curve is the change in velocity). It's very fast and very minute but this is how all radar guns and Chrono's work.
What happens, and I'm reaching here it's been a while since I looked into this problem, but on mine the bullet passes through two gates and the shadow of the bullet is what trips the sensor. It's supposed to measure the time it takes to go from one gate to another and display that as rate, the velocity, distance/time. I'm assuming yours does something similar, it's really the only way to do it.
On mine, it has to do with light. Improper light, shade, overcast, too much light --I'm lucky when it works. And yeah, I get the 8000fps crap too.
At least it's far off enough you know it's not a proper reading.
I'd call the mfg. and see what solutions they recommend. Positive they're familiar with it.
Haha! That's FAAASSSTTT! but must have a pretty bad BC! Joking...
It's likely due to signal reflection off the sound barriers in front of you. Radar works on reflected signals and my guess is the accoustic signature (V0 trigger) and the reflection noise made it difficult for the radar to determine exact time of shot. The downrange signals will be correct (or at least more so) because they are using actual bullet reflection in the radar field.
The accoustic echo from the panels would make the sound occur longer/later and time to enter radar field shorter therefore higher MV calculation. The downrange signals are pulse to pulse so they would not be affected as they would be raw data/velocity.
I don't work for LabRadar but have working knowledge of radar based velocity systems.
It's likely due to signal reflection off the sound barriers in front of you. Radar works on reflected signals and my guess is the accoustic signature (V0 trigger) and the reflection noise made it difficult for the radar to determine exact time of shot. The downrange signals will be correct (or at least more so) because they are using actual bullet reflection in the radar field.
The accoustic echo from the panels would make the sound occur longer/later and time to enter radar field shorter therefore higher MV calculation. The downrange signals are pulse to pulse so they would not be affected as they would be raw data/velocity.
I don't work for LabRadar but have working knowledge of radar based velocity systems.
Same thing happened to me once. My LR showed 7004 FPS from a 223 firing 75gr amaxs. The es/sd were laughable. I just deleted the odd shot from the string and moved on. Hasn’t happened since.
Must be the point I was using that day as it happened twice, first time it gave me a 3711 then later the 8004.
I have used it many times at this range without issue, usually I move further down away from the crowd but on this day the place was empty.
I have used it many times at this range without issue, usually I move further down away from the crowd but on this day the place was empty.
I had a round of 77 grain 5.56 show up as over 7900 FPS. There are better responses above but I was told at the time that the expanding gasses from the muzzle brake can interfere with the reading it takes.
Yes that is true. It can distort the signal and cause it to appear like a velocity spike. Hard to describe without showing raw data but basically it's kind of like the was of a shotgun but if the wad was traveling at Mach 10 and the lead was only Mach 3-4... Easy to notice the difference most of the time and ignore the"wadding" but algorithms can make mistakes too.
Similar threads
Gunsmithing
25 creed reamer and smith
