Latest activity
6gt
- By Niles Coyote
- Reloading Depot
- 2416 Replies
2 inches gets you a little deeper... ur... closer to target 
Maggie’s Funny & awesome pics, vids and memes thread (work safe, no nudity)
- By Lawless
- The Bear Pit
- 111607 Replies
I have some in the freezer
PortaJohn
- By whiskeytower
- The Bear Pit
- 152132 Replies
Hey MTG, hows that genius Palantir stock doing? Heard it was a great time to buy a few days ago..... #stonks #daytrader
Maggie’s Funny & awesome pics, vids and memes thread (work safe, no nudity)
- By sandhiller
- The Bear Pit
- 111607 Replies
That little Chinee band saw will last you your lifetime!
a little work and she’ll be back in the fight.I bought one new maybe 30 years ago when that was the best I could afford.
I've done a little to it, like new motor and stiffened up the frame and new wheels on back but damn it's been a good little saw.
It's cut tons of iron and still cuts true and square.
Thing I like about it is you can set, say a 3x3x1/4 square tube in it and flip the switch and walk away. It will be cutting whily I am working on something else.
Like having your own little helper monkey in the shop!
Good score!
Precision Rifle Gear New Athlon Rangecraft Chronograph-Garmin Xero Killer?
- By Varminterror
- The Armory
- 266 Replies
I use iOS.
When opening the "manage tab" of each Athlon Velocity Pro in the app - on iOS - the units generally automatically sync sessions into the phone. When this doesn't happen automatically, typically there is a "sync sessions" button at the bottom of the app interface page. One of my Athlons will readily do that transfer, or will accept the instruction to sync. My second unit cannot be made to sync - it spins the wheel of death for hours without syncing. I'm going to do another hard reboot and reinstall the updated firmware and hope it clears, now that I have extracted the data manually, but I have not had luck so far.
I can't speak to the mac based App, but once sessions are synced from the unit to the phone, they can be exported as .csv, at which point the iOS interface allows the destination of the export to be an email (or any of a dozen other options, such as opening with specific spreadsheet apps or saving as pdf, or opening with other apps), so I simply export to email and then open the .csv's in Excel. Other than the fact they all export as individual files without descriptive filenames, this works quickly and easily.
I'm not terribly certain at this point if the Athlon is actually worse than "other devices" or not. The "other devices" I have tested include 3 brand/models which are acoustic or recoil trigger only, which means they would only exhibit bad behavior AFTER a shot has been fired. The Athlons, alternatively, are radar triggered, so comparatively, their triggers are always open. So when I have known interfering units operating (such as my LabRadar V1 and my first Athlon, or the Caldwell VelociRadar I have and my second Athlon), the Athlon will trigger repeatedly, non-stop, as if it were constantly receiving shots, even if there is no gun on the firing line. However, the VelociRadar will SEEM as if it is not experiencing interference, but ONLY because it has not been actively triggered. However, once it "hears" a shot with the acoustic trigger, it will experience the same co-channel interference and remains at risk of reading a false echo (the echo from the OTHER co-channel unit rather than their own) and displaying a false velocity. Both LabRadar V1 and LabRadar LX work this same way - acoustic or recoil trigger only, so they too would also SEEM to be operating normally until the shot is fired, but then once triggered, they'd accept the false echo and report a false velocity.
I've seen false echo receipt a few times with Garmins - sometimes we'll see shots reporting over 4,000fps, which indicates they received a false echo from another unit, but I have NEVER seen the Garmins be triggered by Radar, AND it has been very rare to see Garmins interfering. We end up with a bunch of Garmins on the same firing line at PRS match zero boards, and it is exceedingly rare to see interference indicators, whereas 3 out of 3 of the Athlons I have used have fallen into constant feedback loops where they are being triggered and displaying "analyzing" and even reporting velocities for shots which did not happen.
So I'm suspicious but have not yet confirmed that Athlons are accepting NEAR-channel interference rather than simply accepting co-channel interference (which cannot be avoided by ANY of the radar units on the market).
BUT I WILL OFFER A WARNING TO VIEWERS - I believe it will be common for people to see video of folks using LabRadars or VelociRadars to show a lopsided and false representation that the Athlons are unilaterally accepting co-channel interference because we can make them spaz out by turning on the co-channel units. The Athlon will go into a continuous loop, whereas the LabRadar and VelociRadar will APPEAR to be fine... but ONLY because they have not yet been triggered to read, whereas the Athlon IS getting triggered by radar. The LabRadars and VelociRadar will still experience the false velocity output once they are triggered - but it's easy to make a video which seems very, very one sided. I have this kind of video myself, but I'm not yet sharing them until I can properly demonstrate the bi-directional interference instead of making the Athlon look like it is failing.
Not sure what to tell you, other than to describe that by the end of that preliminary interference test pictured above (a test conducted to evaluate the validity experimental design for future tests), I fired a 100 round string with 6 units operating, removing the LabRadar V1 and the Caldwell VelociRadar, which demonstrated to interfere with the 2 Athlons. I'm compiling that information to share in threads like this around the internet and in a forthcoming video (series of videos maybe), but here's an example of the alignment of results when the interferences are eliminated - all 6 units, 2 Athlons, 2 Garmins, and 2 LabRadar LX's agree within 3 fps 1165fps to 1168fps (left side LX was not updated for firmware and was displaying only whole integer velocities, rather than the updated LX on the right side which displays decimal value velocities.
This has been my consistent experience when interference is not happening - observationally, the units are reading within a few fps of each other overall, and within each brand, typically the variance is less than 1fps. As the rain subsides in the next days and weeks, I will share more data to confirm or correct this observation, knowing now which units can and cannot be operated concurrently.
The test pictured was a preliminary operability test to determine interferences for the Radar units to let me determine the volume of sampling I will have to do in order to capture the necessary dataset for this comparison. I want to be able to display data from concurrent operation, but I knew the opportunity for co-channel interference existed, so the test above was the opportunity to test which units can be concurrently operated and which units would interfere. I have to trade out the interfering units one at a time to enable the future testing. Not pictured there, as they were not included in the preliminary radar interference test, are my Magnetospeed V3, MacDonald 2 Box, and CE ProChrono Digital. Since these 3 units aren't radars, I did not include them in the radar interference test.
