AdamM

Hi Zack, Thanks for the feedback. I confirmed this and we will fix this soon. I also checked for an email and didn't see it, so it must have gone to the Junk/Spam folder. When you email us, please use the product name in the Subject line so it will not accidentally go to spam. e.g. "Chronograph Log display error".

Exactly my point. The SDK is supplied without the source code and unless you are deep into knowing exact communication protocol between timer and Android BT interface, you can't really do much. All my android devices are working just fine with all BT microphones I've tried, yet most of them having issues to communicate with SM timer. It all started after the changes in 3085 firmware and corresponding SDK changes when transmission rate was increased. So, after realizing that I'm spending more time trying to make communication with timer work than implementing user-facing features of my Android app, I dropped the project. It is just not worth it for me. PS: don't think any of that would have been an issue if timer used a real digital BT interface instead of trying to simulate it over audio aux. I am aware that it is practically the first device of this kind and it is not possible to use raw digital data over BT with Apple devices, yet obviously it is not working too well for Android devices... You can always do what we did. Take the Java libraries and disassemble them. That's how we based our iOS SDK. There is a big difference between what you "hear" with a BT device (mic) and what the waveforms actually *should* look like. Your ears will not be able to perceive some of the differences that will completely trash the waveform on these devices. Yes, it's a toss up with the new protocol. It certainly made it much faster. That really helps when transmitting "All" times. Unfortunately it does make it a bit less reliable, especially when the SM watch is further from the receiving Device. We wish it had a digital communication too. Unfortunately when you develop things you pretty much have to pick the best available hardware out there and go with it. Don't forget that the development started years before the product was available. I have a friend who makes professional quality video camera/recorders for race cars. It took him THREE years to finally get a chipset that actually worked. He spent over $100K in hardware development kits from various manufactures until finally one was "good". It's really tough being a small company and trying to develop hardware like this. It is possible to do digital with Apple devices, just not with some of the very old ones (which it doesn't even work with for Analog -- e.g. iPad I).

Hmm. Shouldn't it be updated in SM SDK?.. I can't make the demo app from SDK work on 4 out of my 5 devices and only one of them has Android 5. I guess it depends on the device. For OS 5, it would not be an SDK fix. Google had changed it so that unless you were doing the exact right calls it was switching to the internal microphone instead of the BT headset. The only way you can tell what is going on with those non-working devices would be to dump the raw waveforms out and look at them. They should all be consistent (same amplitude and shape). For example on the Samsung S5's, you could clearly see that the longer the waveform was playing, the greater the amplitude of the waveform. We had to write a compressor/limiter to deal with that. My guess is that there are other scenario's that are also causing issues with some devices.

What Android device do you have? Have you tried rebooting it? Also make sure that the SM watch is flashed to 3085. To sort of soft reset the SM, plug it into the USB charger for at least 30 seconds. To hard reset it reflash it with the 3085 firmware. The issue that we've seen on the Android platform is that there are thousands of different devices, different manufactures, different Bluetooth (BT) hardware, etc. Unlike Apple iOS where everything works exactly the same, the Android BT can vary significantly between manufactures/devices. Some devices just will not work because of their BT hardware is not very good or that they are doing something very odd software wise on the BT. We had to write our own API on the Android platform to make the Samsung S5's work. We had to "undo" what Samsung was doing (trying to be too smart and running DSP on the waveforms) to the BT waveforms. That fix would also work for any other manufactures were doing the same thing as Samsung. Unfortunately it would be impossible for us to have every device out there for testing and trying to make it work, so there are going to be some devices that it just may not work with.

If you have upgraded to Android OS 5, you must make sure that you are running ShotMaxx Trainer v1.3.2. Google broke the Bluetooth and we had to modify the app so it would work again with OS 5.

If it is "recording" (e.g. you pressed the Start button somehow) the left and top right buttons won't do anything until you press the REV button. If it still doesn't work after you press the REV, just plug it into a charging source with the USB cable for at least 30 seconds. After you unplug it it should reset. Also, make sure to let it charge for several hours as the battery indicator can sometimes be incorrect.

They seem to have been deleted. I re-added them. Let's see if they stick?

As promised. The shrouds we use for indoor USPSA and Steel matches.

At my club we often use some steel for indoor USPSA matches and also winter Steel matches. We have metal shrouds that surround each steel target (sometimes two). They are basically 3 1/8" plates. Two tall ones on each side and one on the top. It's kind of hard to explain, but there are rails on the top where the side slip into and hold it kind of like a A Frame. The front edges are bent around about 160 degrees in case a round hits it.

If anyone in the continental US still needs one, PM me. I still have a few for sale. I update them with the latest firmware before I send them out!

That is what the new "Batch" mode is for. You just shoot and it records repetitions w/o needing to score. You can go back and add in a score for each repetition if you want, but not required. DAA added the new "SEnd" mode for us that allows you to either send the "Last Shot / Number of Shots" or "ALL" shots when you press the REV button. You need to set "SEnd" to "ALL". Then in the repetition screen tap on "Batch".

I stopped using the FCD on lead bullets. I think they only work for jacketed. For me with 9 mm bullets, it would "swage" the lead down (crushes it) and the bullets will be loose in the brass as it "springs" back. Also caused leading issues as the bullets were no longer wide enough to seal the barrel correctly. I went back to the Dillion crimp die. That's my 2 cents worth...

The ShotMaxx Trainer app for iOS and Android are now available (v1.2.4 and 1.2.7 respectively) What's new: - REQUIRES ShotMaxx firmware v3085 or greater. - Added new Batch mode, for batch capturing without scoring. - Added IDPA support. Drills will have a type of IPSC (USPSA) or IDPA. - Repetitions Calculators will now remember values for a repetition. - Disallow changing drill parameters once they are part of a session to prevent bad scoring.

We are happy to announce that we now have a Registration website for our Steel Scoring iPad app. It can be used for Steel Challenge events, Custom Steel (your own divisions, stages, runs and more) or Knockdown Steel events! If you are a Club admin, please use the Contact Us link if you are interested in trying it out. Website: http://steelscoring.com The Steel Scoring iOS app is very flexible and easy to use. Best of all it’s free, thanks to our sponsors! It is also the first app to work directly with the Double-Alpha Shotmaxx Timer (iPad 2 or newer required), so times can be transmitted directly into the app. We've had a few requests for custom penalty time and it is now in the latest version of this app. You want 5 seconds per missed plate? You can now do that! https://itunes.apple...91767?ls=1&mt=8 We’d like to hear your feedback? Thanks. Cheers, Adam.

Zack, I had also emailed them the full crash report. I don't need it for this weekend (fortunately), but will need it for the next weekend. They should have time to submit another version before that.

Great. The new version no longer runs on first generation iPads. Launches and quits. Practiscore[622] <Error>: *** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '-[uILabel setAdjustsLetterSpacingToFitWidth:]: unrecognized selector sent to instance 0x57b870' *** First throw call stack: (0x3559088f 0x331b4259 0x35593a9b 0x35592915 0x354ed650 0x334dc9 0x1d843f 0x32cf0efb 0x32ceffd9 0x32cef763 0x32c93f37 0x354ef1fb 0x326baaa5 0x326ba6bd 0x326ba5c9 0x32e128ef 0x32d7499b 0x32e05fa7 0x32e05f37 0x32cd4a01 0x32cbbcff 0x32cd50c7 0x349aa4ff 0x3555c547 0x354e8097 0x3491e3eb 0x32c95deb 0x32cc2b03 0x32c90ac3 0x32c90567 0x32c8ff3b 0x3328222b 0x35564523 0x355644c5 0x35563313 0x354e64a5 0x354e636d 0x32cc186b 0x32cbecd5 0xb54b7 0xa9788)

Hey Jim, it runs on my 1st gen iPads (that is use for our Steel Scoring), so I certainly wouldn't buy a new one at full price. Let me know if you need some help?

I decided to load up some of these and chrono them just over a week ago. Unfortunately I forgot to have the non-Ammoload of all the same brass manufacturer, so that probably skewed the results of those somewhat. I loaded up 5 Ammoload, 2-FC, 2 Blazer and 1-other (forgot what it was, since I decided I'll have to rerun the test again some time with all the same headstamp). The amazing thing is that the Ammoload Standard Deviation was much smaller than the other brass and was amazingly consistent. Note the first column "3.3" is the "mixed" brass, the second column, while labeled 3.4 is really 3.3 in the Ammoload brass. All rounds were loaded on a Dillion XL650 letting it "drop" the power as normal. I did *not* measure the power manually. Throwing out the two really out high readings, you can see that the Ammoload was really only about 7 FPS faster than the mixed brass. Can't imaging that that is all that bad at all?!?!?

Rich, yes I have had the same problem. The easiest way to fix it is to Reflash it again. You can reflash it with the most current version (3049 at the time of this post), even if that is what you already have on it. They are working on fixing the way that the commands are sent from the device to the SM and should be more robust with the next update. It needs more "error correction" when transmitting to the SM and I think that on occasion the data to the SM gets corrupted and then the SM acts oddly. Reflashing will fix that for now.

Hy Raylan, At the movement no. We would have to see a lot more sales of the iOS app before taking the time to port this to the Android platform. We only see about 1 Android sale per every 4 on iOS for the same app. Unless we see a huge increase in the iOS apps (or we have a lot of time to kill) we won't be doing it in the near future.

Hi Zack, We looked at the program and it is not really possible to Sort by date (which I thought might be a good work-around). It's set to sort by Caliber as the primary sort and we do not have a sort controller. As far as the Filters go, it doesn't have a "picker", so you wouldn't be able to choose dates there. We will add your request to our "wish list" if we can come up with some hack in the future, but cannot make any promises. Thanks for all the feedback!

Hey Zack, 1-Thanks! We identified the issue and will be submitting the v1.3 update shortly. 2-The reason why we don't do this is that we do not want to enforce any specific amount of digits. For example, someone may want to put 3.05 grains for some pistol loads, or for rifle shooters they will only want whole numbers. They would not want to see something like 24.0, 25.0, etc. 3-I'm not exactly sure why you'd care about date, per se. What your loads and values are are the most important things. I wouldn't think that you'd really care a few years from now to have stuff sorted by date? What do you mean by "only dates where you made chronograph runs"? Hopefully they are all logged.

Hey Scott, older firmware would have no effect on what you are trying to do. The current issue only makes it more sensitive when the Bluetooth is on. I found that some of my guns just didn't make enough noise to pick up all shots, while others did. Do you have any others that you can try?

Hey Zack, Thanks for the feedback. We will certainly keep that in mind and add it to our "wish list".

Agreed. I don't let them stack up. I'm not sure if they are sensitive to moisture, but I always get them stored away or recycled back into the tube quickly. It's funny as I do the same thing a JMorris. I will put a couple bullets inverted into the brass with powder in them in between sessions.