Yeah there's something in their coding that conflicts with other Bluetooth modules for some reason. I heard the same thing from them but never saw much difference even when I isolated it.after talking with cs i found the only way to get the app to work was to put it on an old phone with no other wifi/bluetooth connections.
it would still disconnect at times though
when its less than 5 ft away signal strength should not be an issueDo u guys ever check the signal strength? Mine always indicates good to best and i don’t loose connection. And its a good idea to turn off the ipad time out in settings a display….
Exactly the reason I haven't bought one. I really need a new chronograph, but am waiting for either version 2 or better yet, another company that actually gives a crap to come out with a better one.
thx I missed that one@newbieshooter see post 20
Thank you for the detailed information, but that only reinforces my point about the LadRadar. Everyone always talks about how to make it work properly by having to do this, or having to that, or having to buy this, or having to buy that. IMHO, it is total bs to have to do complicated work arounds and/or buy external equipment just to get the damn thing to function like it should. In today's world there is simply no excuse for this, the technology has been around for a long time now. I hope and pray that another company that actually gives a rats ass develops a product that will work as advertised. I realize I am in the minority on this, but I frick'n hate companies that don't respond to consumer input.That's a bit like the tail wagging the dog. Of primary importance is getting good velocity data. It does that well (and the recoil trigger gets rid of all other issues). You only need the app to do some ES and SD calculations and without confidence interval information they're pretty much useless anyway. The app, when it works, only produces SAMPLE set mean, SD and ES. It doesn't tell you what you need to know about the population you are sampling. So to have something of value, you need to copy the sample set velocity data points (you can use the Labradar's SD card to make this easier) into a calculator such as the one Adam McDonald wrote. Then based on a selected confidence level requirement you get the RANGE of POPULATION Mean and SD your sample data indicates. More info at links here: https://autotrickler.weebly.com/stats-calculator.html
Don't let the app totally drive your decision regarding the device that captures the data you need.
As an example, I randomly made up some 'velocity' numbers and put them in the calculator. 5 shots.
1234 1234 1250 1230 1240
So a sample set ES of 20, SD of 7.8 and mean of 1237.6. Seems maybe "not bad". But you can only be 95% confident that the mean velocity of that load/rifle combo is somewhere between 1227.9 and 1247.3 and only be 95% confident the SD is somewhere between 4.67 and 22.41fps. In other words it could be all over the place. The sample set SD doesn't mean much at all.
I use the recoil trigger for all my tests, it's just more reliable than the built in mics. However, depending on the rifle setup I do get false readings pretty often. These are easy to spot and delete from the series but since the app constantly disconnects I have to do this at the main unit. The ability to "clean up" a series and arm/disarm the unit from a remote device seems like a pretty simple design requirement. I could deal with the old and new app design, but the constant BT disconnect is just annoying. Again, with all the other BT devices in the world that work why hasn't this been fixed?That's a bit like the tail wagging the dog. Of primary importance is getting good velocity data. It does that well (and the recoil trigger gets rid of all other issues). You only need the app to do some ES and SD calculations and without confidence interval information they're pretty much useless anyway. The app, when it works, only produces SAMPLE set mean, SD and ES. It doesn't tell you what you need to know about the population you are sampling. So to have something of value, you need to copy the sample set velocity data points (you can use the Labradar's SD card to make this easier) into a calculator such as the one Adam McDonald wrote. Then based on a selected confidence level requirement you get the RANGE of POPULATION Mean and SD your sample data indicates. More info at links here: https://autotrickler.weebly.com/stats-calculator.html
Don't let the app totally drive your decision regarding the device that captures the data you need.
As an example, I randomly made up some 'velocity' numbers and put them in the calculator. 5 shots.
1234 1234 1250 1230 1240
So a sample set ES of 20, SD of 7.8 and mean of 1237.6. Seems maybe "not bad". But you can only be 95% confident that the mean velocity of that load/rifle combo is somewhere between 1227.9 and 1247.3 and only be 95% confident the SD is somewhere between 4.67 and 22.41fps. In other words it could be all over the place. The sample set SD doesn't mean much at all.
Well the device is setup to accommodate an external trigger from the get-go - and they're not expensive ($35) - so it was anticipated. They just decided not to sell that cheap component. The unit works very well as advertised. No complicated workarounds. (I've not had a single issue using the recoil trigger.) As far as the unit itself is concerned likely the most important rev 2 feature would be improving the alignment. The "notch" could be better designed. But again, there's always ingenious people out there who, with a few spare parts and some hot glue, can design a cheap improvement.Thank you for the detailed information, but that only reinforces my point about the LadRadar. Everyone always talks about how to make it work properly by having to do this, or having to that, or having to buy this, or having to buy that. IMHO, it is total bs to have to do complicated work arounds and/or buy external equipment just to get the damn thing to function like it should. In today's world there is simply no excuse for this, the technology has been around for a long time now. I hope and pray that another company that actually gives a rats ass develops a product that will work as advertised. I realize I am in the minority on this, but I frick'n hate companies that don't respond to consumer input.
Thank you again. I'm actually on the fence about getting one, but with my luck they or somebody else will come out with the new and improved version the week after I get purchase it. So far, with my limited exposure to them, there seems to be 2 groups of owners. One that rarely has issues and think they are great and one that has nothing but problems connecting and missed shots. I have shot with both. I'm pretty sure which group I would be in! It's not that I don't have a chronograph now, it's just old and clunky. But, it's accurate (I think) and very rarely misses a shot.Just to add, as I think most people only use the app to get the ES, SD and mean of each series in order to make comparisons...
I'd say the large proportion of people out there shoot a series of 3-5 shot groups (perhaps stopping earlier if a 'load' or whatever demonstrates itself as 'no good' earlier) so they then compare the statistics from one series to the next and draw conclusions as to how to proceed (be it in load development, ballistics calculation or whatever). "Series A had tighter velocity stats than Series B therefore the load associated with Series A is better." Etc. (You can do the same work examining group size.) But they don't realise that simply looking at one sample set's mean and SD and comparing it to another's is an invalid comparison. You may not have enough information to determine that Series A is better than Series B even though the sample set SD, for example, is better. The differences you see in the shot series data may not be statistically significant. There is a statistically correct way to do such comparisons but it isn't by a simple comparison at face value. You can explore this with the calculator I linked to above without ever having to understand the maths behind it.
So until the Labradar app (or any other calculator for that matter) provides this information it is again essentially useless. For this reason alone I wouldn't bother with it even if it didn't have the connection and other issues it already has.
It cant be fixed because every labradar issue is user error………….according to labradar.Noticed this post yesterday and was looking forward to using the new app with a buddy who needed a rough OCW test. I updated the main unit and downloaded the new app here at home to play with it a bit. Got to the range, set it all up and started recording. The app disconnected from the unit 4 times in the middle of strings, luckily the data could be manipulated on the main unit as always. (I was less than 6 feet away with the iPhone.)
I like the new interface design but the BT connection is completely unreliable, makes it unusable IMO. Why can't this be fixed? This problem has been around since early release of the product.........
Who knows. Last week it was any day now it will show up. It hasn't.Are they ever going to update the android version?
Do u guys ever check the signal strength? Mine always indicates good to best and i don’t loose connection. And its a good idea to turn off the ipad time out in settings a display….
