I like the idea of attaching a scope or red dot. We've been using a square and eyeballing the alignment to the target. LabRadar dropped the ball with their dinky alignment system.
My barrel position in relation to the unit has varied between sessions. Initially, we had trouble getting the chrono to trigger on any shots at all, and this was with bare muzzle .223 AR-15's. Muzzles had to be within a few inches of the unit, and this was when set at the most sensitive. We had to turn the Tx power down to low to get velocity readings.
Later I attached an A2 flash hider, and my buddy put on a muzzle brake. With the flash hider I need to keep the muzzle slightly behind the unit, and within 4-5 inches or it won't trigger. We have it set on the 6" muzzle distance setting. My friend's muzzle brake allows a little more leeway than the A2 flash hider, but not by much, and the sideways bark from that thing is substantial. This is at the most senstive triggering setting. I don't understand how others are having their LabRadars triggered by nearby shooters at any setting. We have to deliberately give this one the most blast possible for it to pick up a shot at all. Maybe it has a problem.
We'll chrono again next shooting session, this time shooting from a table instead of from the ground. I'll do my best to measure and record my muzzle position in relation to the chrono. Will then try to repeat with the same positioning the following time and compare results. I'll save some rounds from the same reloading batch to run the next session.
If consistent position increases repeatability, it still won't say very much about accuracy.
Speaking of chronograph accuracy/precision, I encountered an odd situation a couple years ago that provided some interesting information.
I had been shooting through my ProChrono from the bed of a pickup. I moved the chrono, still on its tripod, several feet to the side when my friend shot his rifle. I noticed the ProChono was registering his shots and velocities. Bullets were not passing through the chrono. It picked up the shockwaves.
Here is the e-mail I sent him about the results:
The chrono was registering about 1180 FPS during your shots. It was picking up the shockwave at the speed of sound.
Sound speed at different temps:
80 degrees: 1139 FPS
100 degrees: 1160 FPS
120 degrees: 1180 FPS
The air temperature wasn't 120, probably more like 85. The readings are slightly off because the chrono wasn't perfectly lined up with the origin of the sound. It was rotated a little, reducing the distance between the sensors, which caused the velocity readings to be calculated higher than actual.
Similar happens with bullets, which is why it is important to keep the chrono lined up so bullets travel parallel with the top of the chrono. If the bullet goes through at an angle, it travels more distance between the sensors than is being calculated. If shooting through at an angle, readings will be lower than actual bullet speed.
Since the speed of sound is constant at a given temperature, this was a good measure of the chronograph's precision. 12 shots were recorded.
high: 1192
low: 1180
avg: 1186
es: 12
sd: 4
Specs for the ProChrono say accuracy is "+/-1% of measured velocity, or better." I can't vouch for accuracy, but precision was better, at least this time for a single string of 12 "shots". The ES of 12 is a total variation of 1.01% (+/-.505%).
If the error is linear, which it may be, 1.01% would be an extreme spread of 27.3 FPS at 2700 FPS.
Based on the collected data, that's what the chrono would show if you could fire shots all going at the same exact speed. It's not capable of measuring super tight extreme spreads. Sure, it will occasionally report some low extreme spreads in strings of small sample size, but they don't mean anything. It's akin to reading ten-thousandths on calipers only precise to .001".