Stuntman

I hear that! I've also installed the latest firmware and seems LabRadar has gotten a little better with each release but this has been going on for YEARS! In my view LabRadar has done nothing to generate customer good will and I have to admit I'm quite chuffed to see Garmin come out with their own chrono. It would appear they are eating LabRadar's lunch.

I just noticed LabRadar posted another firmware update in September; 2.0.0 They've been slow to post updates but I have seen noticeable improvements over the past few updates. Not perfect but less buggy Bluetooth with each update.

The suspense is killing me! Ever find an solution that didn't require buying a new frame?

NROI responded it is one procedural for failing to follow the stage procedure and not being a significant advantage (shooting targets from further away with non-movement).

Shot classifier "We Play Games". Timer goes off, shooter engages targets, reloads but forgets to move to next box and engages the remaining targets for the string. Single procedure or procedure per shot? We initially settled on single procedure but this seems like it could be exploited. Does this rise to a significant advantage? Course description: String 1: On the audible start signal, from shooting box A, engage each target with only one round each freestyle, perform a mandatory reload, and engage each target with only one round each from shooting box B, strong hand only. String 2: On the audible start signal, from shooting box B, engage each target with only one round each freestyle, perform a mandatory reload, and engage each target with only one round each from shooting box C, weak hand only

Android. From my research, it seems the IOS devices are more reliable but not completely immune where Android devices seem more hit & miss. I'm using a cheap phone that could be part of my issue but it's reliable with every other Bluetooth device I have. Edited to add.. I've forgotten how long I've been chasing this issue! I've tested using several past phones as well as tablets and have experienced this issue across all devices.

Bah! The 1.3.3 firmware doesn't seem noticeably better than the 1.2.7 firmware. I still have periods where connectivity is lost and unable to establish communication. Usually takes a power cycle of LabRadar or toggling Bluetooth on phone to correct. And the mobile app is baffling! Why do I have to perform a search for available LabRadar units each time I'm attempting to connect? I understand the app is not in constant communication with the LabRadar but can't it cache my device's identity and automatically reconnect as needed?

Heh, no. For years I've seen stage descriptions written as "Loaded gun lying flat, unpropped on table". It's redundant, I get it. Just wanted to make sure I wasn't missing anything. Admittedly, I can't stand seeing redundant instructions in stage descriptions like "gun loaded with safety engaged".

WSB says "Loaded gun lying flat on table." Based on this would propping be allowed?

New firmware (1.2.7) and mobile apps (IOS & Android) have been released. User interface on app seems better, more intuitive. Connectivity is hit and miss so far on two Android phones, one seems to work well, other won't connect at all.

The latest firmware allows you to use their phone/tablet app over a Bluetooth connection. When it works, I find the phone app more intuitive and easier to navigate than the buttons on the unit itself.

App published on Play store in 2018. Require latest firmware on unit.

I picked up a LabRadar chrono about a year ago. I generally like it but find the connectivity issues with the mobile app are making me despise it. The user interface on the app is much easier to use and navigate, plus being able to arm unit and review shot data without having to break shooting position make it much preferable over the unit's display and nav buttons. I've tried all the cockamamie solutions I could find on the Internet; reinstalling app, clearing app cache & memory, rebooting phone & chrono and others I can't recall at moment. None have worked. The LabRadar folks have been promising an updated app for YEARS so I'm not confident a fix is forthcoming. Through continual scab picking at this problem I've discovered a technique (hack) that has been 100% effective although my sample size so far is small. Fix Install "BLE Scanner" on phone/tablet. This a Bluetooth network scanner I installed to troubleshoot connectivity issue. Put it into scan mode and find the LabRadar unit in the list of found devices. Select the "Connect" option for the LabRadar. It will display some Bluetooth details for the unit that is not relevant to our issue That's it! Now launch your LabRadar app, it should find and connect to unit. I have no idea why first establishing a connection with the BLE Scanner app fixes this issue and I've only been able to confirm this with Android devices. Hope this works for others.

Still watching for reviews. Single review on MidwayUSA isn't promising either. https://www.midwayusa.com/product/1023624730

<silly dup post>

<silly dup post>

<silly dup post>

JP posted this cautionary video about using heavy bullets loaded just above minor. Maybe this was it. Don't Trash Your PCC With The Wrong Ammo

They seem to have gotten these out to the press for reviews but not so much to the retail channels.

The post by SWprotected just above yours is exactly what you're looking for and an excellent load to start with.

I use ceramic media as indicated here. The 3/16 diameter media will pass through a Dillon sifter yet won't get jammed in 9mm case. It works about 90% as well as SS pins.

Yes, but could an industry standard Bednorz take down steel calibrated for factory loads from a 16" barrel? That is the question!!

From matchbook: So what power factor is everyone loading to?

Just sitting there but not next to any other targets. By locating no-shoot uprange from shoot target, very little of shoot target was visible from start position, maybe only D zone. Shooter had to move down range and laterally for A zone of shoot target to became available. Again, in this scenario there is no debate where the shoot target was engaged and no pass-through occurred. While I think everyone knows the no-shoot was caused by a previous shooter I'm not sure it's sufficiently obvious to not require a reshoot per 9.1.4

Probably not pristine, don't recall exactly except there were no other taped penalty shots within several inches of this one. There were locations where the NS would have obscured the shoot target in question. Yes, NS hit same diameter as shooters. Not missing grease ring nor looked different. And keep in mind no one believes or asserts a pass-through the NS occurred. The location where the target was engaged was known and there was no way to make a pass-through line up, nor did the round ricochet off lath or anything else. Now that I understand 9.1.4 applies to both targets and no-shoots, I'm coming around to this.