Jump to content
Brian Enos's Forums... Maku mozo!

Stuntman

Members
  • Posts

    43
  • Joined

  • Last visited

Posts posted by Stuntman

  1. 17 hours ago, Speedwagon said:

    I always had problems trying to connect with Bluetooth so just used the SD card. I just installed the update and it connects fine now. Now just need to see it it'll connect at the range. You know how that goes. 

    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.

  2. 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 

     

  3. 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.

  4. 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? 

     

  5. 22 hours ago, ChuckS said:

    Lost an argument last weekend? 

    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".

  6. 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.

     

     

  7. On 2/9/2021 at 11:36 PM, looking4reloadingdeals said:

    When I started doing load development for my PCC I read reports of this to people before. IIRC Hi Point (or some other manufacturer) made a video about “load development for a PCC” where they showed a cross section of a barrel that had ~15 Bullets stuck in the barrel stacked against each other. Said its was With a heavy Bullet and slow powder. As Ranger said, it’s because all of the powder gets burnt up, and the bullet is no longer accelerating, but actually decelerating. 
     

    in my PCC I never had this problem using coated Bullets, possibly because they have a more slippery surface? But I still only got 5-10pf higher than my 4-5” pistol barrels. 

     

    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

  8. 22 hours ago, moonshoxx said:

    Can anyone give me a load for a 135 moly with WST.  I am loading at 1.135 in 16inch G9.  Thanks.

     

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

  9. 2 hours ago, StealthyBlagga said:

     

    We have no minimum power factor requirement, but bear in mind that a 147gr 9mm at 850fps (125PF) zeroed at 25-yards would drop about 80-inches at 200 yards - that is more than the height of an industry standard Don Bednorz 🤣

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

  10. On 8/9/2019 at 5:58 PM, terrydoc said:

    What was the no shoot doing 3 ft away from the shot array? was it next to other targets?

     

    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

     

     

  11. 6 hours ago, mreed911 said:

    One clarifying question: Had the NS been previously hit and pasted or was it pristine?

     

    And a geometry question: There's NO PLACE in the stage that the no-shoot would have been behind any other target from the shooter's perspective?

     

    And a math question: Is the hole the same diameter as the shooter's bullet?

     

    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.

     

    1 hour ago, HCH said:

    And was one of the alpha hits missing a grease ring, or look different than all the other holes in targets from that shooter?

     

    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.

     

    11 hours ago, DKorn said:

    I’d say it’s most likely that I’d give the shooter a reshoot - how do I know whether  the unposted hole was the one in the no shoot or one of the alphas? Unless I have another way to know for sure (different caliber holes, other evidence, etc.), if the shooter only fired 2 rounds that could’ve caused those 3 holes, I’m unable to determine an accurate score and therefore the shooter must reshoot. 

     

    Now that I understand 9.1.4 applies to both targets and no-shoots, I'm coming around to this.

×
×
  • Create New...