Guessing he’s just looking at the pics. Definitely appears larger in the pics in this thread.May I ask...where did you see any size information on the LR unit?
Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
To enter, all you need to do is add an image of yourself at the range below!
Join the contestGuessing he’s just looking at the pics. Definitely appears larger in the pics in this thread.May I ask...where did you see any size information on the LR unit?
My customer service experience with labradar told me everything I need to know about that company. Broken port, that they tried to tell me was not broken. They absolutely refused to fix it until I got nasty.
I don't care what product they come out with in the future, or what the capabilities of that product are claimed to be, I will not buy from them. I feel Infinition and everything they touch will be tainted. I contacted that company no less than 10 times over the course of 3 months trying to buy one of their "big boy" radar units. No call backs, sometimes for weeks on end. I was prepared to spend $75k to get what I wanted... and they had no time for me.
I feel that they are clearly making their revenue from somewhere other than civilian sales and don't care about us at all.
They will never see another dime from me.
Er....and where did this pic come from, please?
The "marketeering" associated with this photo is impressive. The LR-LX is full bright, shows a high velocity, has a full(er) battery, shows Bluetooth connected, and is displayed from the front where size is similar vs. the side where size is a huge disadvantage for the LX. The Garmin Xero is displayed with virtually no backlight, no registered velocity or statistics, a half-full battery, no Bluetooth connection icon, and displayed from the front where the LR-LX doesn't look like a shoe-box to Garmin's match-box size. It's like every sales display for a clock or watch, where the time is always 10:08 ... so the hands look like a "smile" and make you feel better about buying the clock. Bravo to whoever took this photo ... they obviously passed "Marketing 101" in their undergrad work.
It's accurate enough. The slight errors fall well within the normal distribution (over a larger sample size) and the average velocity derived is accurate enough for 99.9% of practical uses in the shooting sports. Anything else is just academic and mental masturbation.You are not getting away with it , as folk from Andyscan have explained there are consequences to misalignment as in slight errors in velocity shown, all of these units will suffer the similar due to misalignment.
The "marketeering" associated with this photo is impressive. The LR-LX is full bright, shows a high velocity, has a full(er) battery, shows Bluetooth connected, and is displayed from the front where size is similar vs. the side where size is a huge disadvantage for the LX. The Garmin Xero is displayed with virtually no backlight, no registered velocity or statistics, a half-full battery, no Bluetooth connection icon, and displayed from the front where the LR-LX doesn't look like a shoe-box to Garmin's match-box size. It's like every sales display for a clock or watch, where the time is always 10:08 ... so the hands look like a "smile" and make you feel better about buying the clock. Bravo to whoever took this photo ... they obviously passed "Marketing 101" in their undergrad work.
Well here’s the thing. Academically I’m sure you’re right. But I think what the other guy is getting at is that the velocity isn’t going to vary super significantly.You can smart ass all you want but a dude that is smarter than both of us and made first rifle mounted radar years before Garmin and Labradar, explained in a post how and why both offset and orientation can influence measurements.
Looking for most consistent measurement you need constant offset and angle , best facilitated by rifle mount
There is no magic compensation going on by Garmin or Labradar its just inept users inducing errors and thinking the magic box does magic things
View attachment 8327751
What I saw is Garmin screen size larger while total unit size more compact.The "marketeering" associated with this photo is impressive. The LR-LX is full bright, shows a high velocity, has a full(er) battery, shows Bluetooth connected, and is displayed from the front where size is similar vs. the side where size is a huge disadvantage for the LX. The Garmin Xero is displayed with virtually no backlight, no registered velocity or statistics, a half-full battery, no Bluetooth connection icon, and displayed from the front where the LR-LX doesn't look like a shoe-box to Garmin's match-box size. It's like every sales display for a clock or watch, where the time is always 10:08 ... so the hands look like a "smile" and make you feel better about buying the clock. Bravo to whoever took this photo ... they obviously passed "Marketing 101" in their undergrad work.
I have an idea for a LR modification that makes it useful in a world where the Garmin just became Emperor ... I wonder if there's a way to "reverse measure" so that I can put my Labradar near, say, a 1,000 yard target, aimed at the firing line, and figure out how to get an actual measurement of velocity at distance. You know ... trick it into thinking the oncoming bullet is really from the muzzle, just going the wrong way. Don't laugh ... I'm serious here ... (sort of, maybe, OK, probably not).We have been lazy, but have been meaning to hollow out our labradar and turn it into a case for the Garmins.
Does this experiment end with the bullet striking the LR? hahaI have an idea for a LR modification that makes it useful in a world where the Garmin just became Emperor ... I wonder if there's a way to "reverse measure" so that I can put my Labradar near, say, a 1,000 yard target, aimed at the firing line, and figure out how to get an actual measurement of velocity at distance. You know ... trick it into thinking the oncoming bullet is really from the muzzle, just going the wrong way. Don't laugh ... I'm serious here ... (sort of, maybe, OK, probably not).
Users have put the Garmin downrange next to their target to get a velocity. Works well. Use a berm or steel target in front to protect the unit, or just shoot accurately.I have an idea for a LR modification that makes it useful in a world where the Garmin just became Emperor ... I wonder if there's a way to "reverse measure" so that I can put my Labradar near, say, a 1,000 yard target, aimed at the firing line, and figure out how to get an actual measurement of velocity at distance. You know ... trick it into thinking the oncoming bullet is really from the muzzle, just going the wrong way. Don't laugh ... I'm serious here ... (sort of, maybe, OK, probably not).
Probably ... eventually. I might send mine to Scott at Kentucky Ballistics and have him shoot it with one of his elephant guns. That would be fun ... probably more fun than the $30 I'd get for it now on GunBroker.Does this experiment end with the bullet striking the LR? haha
Also came from the Yanick Sab Facebook page (same as pic below) although the original photo (of the Garmin vs LX size comparison pic)I think came from Ryan Cheney ELR's Facebook page. This is probably the last pic I'll post unless I can find more size comparison pics between the Garmin (or other units) and the LX. I think most of us got a general idea of what the size/form factor of this new LX is.Er....and where did this pic come from, please?
Garmin at least reminds the user on the screen at the start of every series of optimal placement .You can smart ass all you want but a dude that is smarter than both of us and made first rifle mounted radar years before Garmin and Labradar, explained in a post how and why both offset and orientation can influence measurements.
Looking for most consistent measurement you need constant offset and angle , best facilitated by rifle mount.
There is no magic compensation going on by Garmin or Labradar its just inept users inducing errors and thinking the magic box does magic things
View attachment 8327751
Still looking for a 360-degree view to tell where the charger plugs in, whether there's a SD Card slot, and if they included a port for an external trigger (or not).Also came from the Yanick Sab Facebook page (same as pic below) although the original photo (of the Garmin vs LX size comparison pic)I think came from Ryan Cheney ELR's Facebook page. This is probably the last pic I'll post unless I can find more size comparison pics between the Garmin (or other units) and the LX. I think most of us got a general idea of what the size/form factor of this new LX is.
Yanik said it got leaked early. Probably months away from actual in hand user testing. If it’s anything like LR of the past, more frustration incoming. I’ve tried other’s LR units. Royal pain in the ass to use with Rimfire.Still looking for a 360-degree view to tell where the charger plugs in, whether there's a SD Card slot, and if they included a port for an external trigger (or not).
I think it's on the bottom. The last pic I posted has a grey cable (power? data cable?) and a trap door on the bottom. If I can find a clear pic of it though, I'll post it up.Still looking for a 360-degree view to tell where the charger plugs in, whether there's a SD Card slot, and if they included a port for an external trigger (or not).
If the App still sucks, and they no longer have a SD card ... that would be an even worse combination than they have right now. At least on my existing LR I could always get good data off the SD card, even if the App was useless.Yanik said it got leaked early. Probably months away from actual in hand user testing. If it’s anything like LR of the past, more frustration incoming. I’ve tried other’s LR units. Royal pain in the ass to use with Rimfire.
Fucking gold.So you feel the way about LabRadar the way I feel about you and your products? That's interesting.
It's still thereI think one guy just left it at a range on purpose.
It definitely would have been a game changer had it beat the garmin to market though.
Er....and where did this pic come from, please?
That's because you didn't speak in French to them.My customer service experience with labradar told me everything I need to know about that company. Broken port, that they tried to tell me was not broken. They absolutely refused to fix it until I got nasty.
I don't care what product they come out with in the future, or what the capabilities of that product are claimed to be, I will not buy from them. I feel Infinition and everything they touch will be tainted. I contacted that company no less than 10 times over the course of 3 months trying to buy one of their "big boy" radar units. No call backs, sometimes for weeks on end. I was prepared to spend $75k to get what I wanted... and they had no time for me.
I feel that they are clearly making their revenue from somewhere other than civilian sales and don't care about us at all.
They will never see another dime from me.
You can smart ass all you want but a dude that is smarter than both of us and made first rifle mounted radar years before Garmin and Labradar, explained in a post how and why both offset and orientation can influence measurements.
Looking for most consistent measurement you need constant offset and angle , best facilitated by rifle mount.
There is no magic compensation going on by Garmin or Labradar its just inept users inducing errors and thinking the magic box does magic things
View attachment 8327751
And 6 months from now the px could be littered with garmins being replaced by owners with the LR units. I doubt it but you never knowIn theory anyway. The old Lab Radar unit wasn't exactly the easiest thing in the world to purchase. Production and marketing wise, even if Infinition had a year's head start, i think Garmin would have quickly caught up and passed them.
I'd be interested to see the resolution when the seen is shining on the screen. I know the Garmin screen sucks and is hard to see when the sun is behind me, shining right at it.
More likely than not it doesn't have any correction for it as you have seen correction factor its in 3rd decimal if radar is placed at close to recomended position.this is interesting.
Do you know that Garmin doesn't take angle into account? Seems theoretically possible, to determine the angle of the projectile relative to the line of site of the radar by simply having data points on two points in space of the projectile, then being able to use that data to make a calculation that takes into account the angle.
I don't know that they do this. But I do remember the Garmin EE talking about an algorythm they use to normalize the calculated velocity which takes a few seconds - which is why you see the delay in the display.
Do you have any information that indicates Garmin doesn't take this into account?
More likely than not it doesn't have any correction for it as you have seen correction factor its in 3rd decimal if radar is placed at close to recomended position.
But same problem happens when you place it a different lenghts. to the muzzle or in elevation difference its a 3 dimensional error
Labradar LX having a sight is probably related.
These are problems unique to super short-range radars ,as the measurement zone is short and angular differences can be larger
But like said these errors are likely of no concern to most users.
that is up to you ,how much garbage in, garbage out you are comfortable withAh, so it doesn't matter at all and the placement differences are irrelevant to the results.
More likely than not it doesn't have any correction for it as you have seen correction factor its in 3rd decimal if radar is placed at close to recomended position.
But same problem happens when you place it a different lenghts. to the muzzle or in elevation difference its a 3 dimensional error
Labradar LX having a sight is probably related.
These are problems unique to super short-range radars ,as the measurement zone is short and angular differences can be larger
But like said these errors are likely of no concern to most users.
View attachment 8328052
that 2% was from a 10cm shift to the side on an andiscan that is 1m behind the barrel and 20cm from bore line, its not the most error you can have its just one sampleAt most a 2% error that is constant in the same direction for a data gathering session.
LOL
You can't even read the offsets correctlythat 2% was from a 10cm shift to the side on an andiscan that is 1m behind the barrel and 20cm from bore line, its not the most error you can have its just one sample
Lets remember posters that went bananas when chrono manufacturer advertised error less than 1%
Like said garbage in garbage out , its up to you.
I doubt they would waste the code on it…in any realistic scenario it’s inconsequential, IMOthis is interesting.
Do you know that Garmin doesn't take angle into account? Seems theoretically possible, to determine the angle of the projectile relative to the line of site of the radar by simply having data points on two points in space of the projectile, then being able to use that data to make a calculation that takes into account the angle.
I don't know that they do this. But I do remember the Garmin EE talking about an algorythm they use to normalize the calculated velocity which takes a few seconds - which is why you see the delay in the display.
Do you have any information that indicates Garmin doesn't take this into account?
Educate meYou can't even read the offsets correctly
LOL
Might as well pack up if the MV is 15 FPS off what the screen says.Educate me
error went to 2% from 0.5% in 20cm vs 10cm offset from bore line.
So your true MV that Garmin was showing at 3000fps was either 3060fps or 3015 fps depending on 10cm difference in lateral position.
Garbage in garbage out.
the error remains constant,SD and ES differences will still be recorded right , just the baseline is slighty skewed. Like i said that is why these small radars predating Garmin were designed to be rifle-mounted to reduce these errors .Might as well pack up if the MV is 15 FPS off what the screen says.
Hell most people buying the damn things probably have an SD higher than 15.
Also I'm still not clear what is a better option? The Magnetospeed that screws with barrel harmonics?
The original Labradar, which is the most accurate and precise chronograph ever tested by Litz. And while 15fps may not matter to most people, it really does for me.Also I'm still not clear what is a better option?
It's not accurate at all if it only captures 5% of the time.The original Labradar, which is the most accurate and precise chronograph ever tested by Litz. And while 15fps may not matter to most people, it really does for me.
Fair, our standards are different.The original Labradar, which is the most accurate and precise chronograph ever tested by Litz. And while 15fps may not matter to most people, it really does for me.
Yup, I went on a tangent about that in an earlier post!the error remains constant,SD and ES differences will still be recorded right , just the baseline is slighty skewed. Like i said that is why these small radars predating Garmin were designed to be rifle-mounted to reduce these errors .
Now that LR are so cheap, one can just tape over that dataset hole by using 10 LabRadars in a large circle. An orange ring of fire.Fair, our standards are different.
My largest gripe is that I don't care how great the LR is when half of the data points are missing. Sort of like crap in crap out, except there isn't even crap in, it's just a hole in the dataset. I won't bother belaboring the additional issues with customer support and the apps. I haven't personally owned one so I can't speak as much to those aspects. I was sufficiently scared off by what I saw to just wait. Glad I did.
Now that LR are so cheap, one can just tape over that dataset hole by using 10 LabRadars in a large circle. An orange ring of fire.
Would be amusing if they all miss the same shots.
The original Labradar, which is the most accurate and precise chronograph ever tested by Litz. And while 15fps may not matter to most people, it really does for me.
I think I said this in the Xero thread, but I would rather have more consistency over a little bit less accuracy another words I don't care if a chronograph thinks 2900 FPS is actually 2910 FPS as long as it always thinks 2910 FPS is 2900 FPS consistently that will make the ES, SD, and the AVG more accurate. I am not saying the Xero is not accurate just using that as an example, but I do feel like it is very consistent I have yet to have any "crazy" fps shots like I have gotten with other chronographs in the past.There is a post somewhere buried deep in the Xero thread of someone who posted a video taking shots pointing it all over the place at varying distances from the muzzle. It was never that far off compared to when it was set at the recommended distance. If I remember, it was well within the ES. Basically, me and those who saw the post, felt that it didn't matter one damn bit if it was not exactly where Garmin suggests, as long as it got the shot.
As a matter of fact, I can't wait to see someone test both side by side doing the same exact test.