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

Alan Adamson

Classifieds
  • Posts

    680
  • Joined

  • Last visited

Everything posted by Alan Adamson

  1. I got this autodrive from Sean at powerfactorshooting.com. It said it was in stock and it shipped really fast to me. Just got it up and functional with my CasePro. I rigged it for now so that I could pull a casefeeder from one of my 1050's and with no additional changes just set that feeder onto the AutoDrive and CasePro. In this video it's doing .40 SW, and is running about 24/min or approx 1400 an hour. ... I also have dies for 9 and .45 (although I should sell/trade the later, as I don't reload .45 ...) I know this pushes the extreme of laziness, but hey, it's what I wanted... and It works great. It did take a bit to get adjusted right. I broke probably 3 or 4 of the little nylon shear bolt/feed mechanism bolts on the Casepro before I got wise and *really* loosened the clutch on the Autodrive.... Now it doesn't slip, only when it needs to, which actually isn't very often.
  2. As a quick follow up on the DropBox thing... And one NOTE, I *DO* have an 2g SD card in my nook... I just leave it there all the time as you never know that they are dirt cheap. Anyway, put the .apk file in your DB, click it on the listing on your nook, it will download and install. but again, note, that is with an SD card installed in the nook... but it's still simpler than using andexplorer and still needing an SD card to install it. Alan
  3. Keyboard issue fixed in 1.0.16 NOT! The 1.2.1 firmware changes the keyboard. 1.0.16 and 1.1.0 firmware had the right keyboard, 1.0.16 and 1.2.1 does not. Here is a picture. If I remember right, and I spent a good bit of time going over this with Josh (the prior programmer on PS)... the nice keyboard is a custom one (or at least not the default one). An application can put up whatever keyboard it wants to. it's not per-se a function of the OS (or os version). The 10 keypad keyboard is the Phone one actually if memory serves me right, it has the period and the - etc. Josh I believe had to assign (can't remember the correct android parlance) that keyboard to that activity/screen etc. In order to get it to function. The way this picture shows is the the way it was originally until Josh changed it sometime back on the 0.9.x days...So I suspect with the 1.2 update, something changed either removing the keyboard, or the root kit could have removed it as well where it is a phone option and there isn't a phone in a NST.... Just a guess, but we've been down this road before...
  4. Where do you find the dropbox directory in andexplorer? I don't see it. Are you able to use dropbox on your nooks without a microsd card in the slot? No please, go right ahead and brag! You all have developed so many different utilities and procedures to make this work, there's no reason in the world other than just breaking down and buying the devices that ANY club couldn't go to electronic scoring. (A written treatise on how we make all this come together would be nice just in case one of us gets run over by a truck on the way to our respective ranges!) Bill, you don't even need to use andexplorer... but now you are going to make me go figure out how to do it from dropbox... I know I don't open it in andexplorer, I just select it from dropbox and it will load it.... but I'll have to verify the exact steps. Alan
  5. I believe that is going to change real soon... They have or are implementing a much improved sync process for both apple and android. From all accounts, it should solve the issue of needing an IOS device as the master, but we'll see.... We as well do the same, having Bonjour find all the devices vs. needing to know the ID codes on android is soooo much nicer at the moment...
  6. Late on this response, but don't bother with phones, White paper NST's (Nook Simple Touch's) are the way to good for now... the only issue is rain, but that would be true of a phone too. In bright daylight however, they are the bomb...
  7. For quick updates for the application, you guys need to start using Dropbox on all your Nooks... Then just copy the .APK file to DB, open it in the file manager (you do have a file manager on your Nooks right?), and install it from the single sync'd DropBox directory. Not to mention we use DB for all kinds of other things. And while I had to take a little break due to real work... We've been scoring matches with PS not for almost a year... Haven't gone to paper one time since. Next to Ken, I'm betting that Chris and I have score more matches with PS than just about anyone. At one time we were scoring 10 matches a month and in most cases we score at least 6 and usually 8. 2 weekly clubs and 2 sometimes 3 outdoor monthly matches... Not bragging, but I don't know what we'd do if we had to go back to paper. And Thanks To Chris (JCWREN to some of you), he's created all kinds of little tools to make the integration with SSI functional and solve some issues even with EZWS.... Ken, and team just keep up the good work and as you know we put good words in with you with area and section all the time from this part of the US... Alan
  8. Thanks for the comments. Yes, we learned that there were two primary issues with the way we did the paper version. a) it didn't leave enough room for any RO comments as might be required for things like procedurals, etc. it didn't leave enough room for any specifics that an RM might need to include, say a target under despute, etc. We went back and forth prior to the match of doing the individual sheets that you all see traditionally at a paper scored match, and elected to go the way we did (8-9 shooters on one legal sized sheet of paper), post the stage, the shooters would cut up the sheets with provided scissors to get their copy. Ideally, I think over the next year, we are going to work seriously hard to come up with a way to *print* live final *strips* for each shooter... I don't know how we are going to do it, but we are... There was one huge advantage to how we did do it however... it made confirmation of squad by paper easy, if I know I had 20 squads out shooting on a day, at the end of the day, by stage, I should have 20 sheets of paper. All in all however it worked as it should have and we had a solid paper trail if we needed it... In the end, we did not. It was such a good conversation point during that match that Bill Noyes even designed a *new* single sheet version that mirrored the way that PS readback results, in hopes that maybe that would make it easier for the next time... But hey, we have a year to figure that part out .... Unless of course Mark drafts us to go help him with the AL Sectional, then my year just got cut in half! ... hehe... Alan Hell, I already have J.C.'s commitment to help. Just waiting on you...... Mark K hehe, somehow I knew that was going on... he pinged me today asking if I was going to shoot your sectional.... I figured you musta been twisting his arm. Thanks Mark for your NOOKS, and your support! Couldn't have done it without a *bunch of people* Alan
  9. Thanks for the comments. Yes, we learned that there were two primary issues with the way we did the paper version. a) it didn't leave enough room for any RO comments as might be required for things like procedurals, etc. it didn't leave enough room for any specifics that an RM might need to include, say a target under despute, etc. We went back and forth prior to the match of doing the individual sheets that you all see traditionally at a paper scored match, and elected to go the way we did (8-9 shooters on one legal sized sheet of paper), post the stage, the shooters would cut up the sheets with provided scissors to get their copy. Ideally, I think over the next year, we are going to work seriously hard to come up with a way to *print* live final *strips* for each shooter... I don't know how we are going to do it, but we are... There was one huge advantage to how we did do it however... it made confirmation of squad by paper easy, if I know I had 20 squads out shooting on a day, at the end of the day, by stage, I should have 20 sheets of paper. All in all however it worked as it should have and we had a solid paper trail if we needed it... In the end, we did not. It was such a good conversation point during that match that Bill Noyes even designed a *new* single sheet version that mirrored the way that PS readback results, in hopes that maybe that would make it easier for the next time... But hey, we have a year to figure that part out .... Unless of course Mark drafts us to go help him with the AL Sectional, then my year just got cut in half! ... hehe... Alan
  10. For the past 6 months, we have worked very closely with Kens team at Practiscore and the fruits of that paid off this past weekend. After much nay-saying, some significant push back, and lots of thought and practice, we ran 220 shooters in 4 5.5hr sessions with 10 stages (including Chrono) all with Android devices and all using PractiScore as the primary scoring method. When the dust settled (or in this case the skys cleared). Within 10 minutes of the last shot fired, we had *ALL* 220 shooters scored, *ZERO* missing score sheets and most importantly, *ZERO* issues. Yes, we backed everything up on Paper, but only needed to resort to those ONE TIME to gather DQ's and deal with one shooter that had their scored entered under the wrong shooters name (which we had addressed in about 30 seconds). In fact, the longest wait was due to having to print out the required paper sheets for the final review and wait period, which was promptly waived. Did we have some small issues, yes, but I'd dare say no worse than any other typical L2 match. But what we didn't have was any manual entry of scores from paper, having to translate chicken scratches to scores, and the associated wear and tear on the data entry personnel etc. I suppose we need to hold a postmortem and set down and document what/how we did this in the hopes that others can try it. We used 20 nooks, swapped them at session turn over, had ZERO of them give us any issue the entire match. We did learn what we like and don't like about how to do paper backup. And we all *wished* we could electronically generate (print) competitor stage results at the end of their run to hand them directly in place of the paper backup carbons.... But all in all, to the best of my knowledge, this was the first 100% successful match scored completely with Practiscore, the way it should be. And for those nay-sayers.... We took RO's, some that had little PS experience, some with lots of PS experience and after a few minutes of education, they were off and running. We used 2 Stats people, one rover with Ipad doing backup syncs over a rage Wifi (without internet) at 30-45 minute increments, and one doing the registration/ezws/ps postings and changes. We ran EZWS and PS side by side, and we used SSI as the registration tool. One could say we used every form of digital tool we had at our fingertips to pull this off - AND lessen the amount of manual data entry and pen to paper impacts. We even pushed frequent updates to both the USPSA website and the practiscore website and on more than one occasion I heard people say they couldn't believe that they had updates on their phone as frequently as they did. Who knows, next year we may try a "jumbo tron" with live updates and sponsor crawls , don't laugh, we've already talked about it and it's easily within the realm of possibilities. Now remember, for the prior 6 months, we've run 100+ shooter monthly matches and have done each and every one of those completely with PS. To the point where we had match results ready and published before we left the range for the day... ... Many thanks to Peter Oliver the MD for letting us try this (actually, I think he wanted it more than we did). To our Section coordinator - Bill Noyes for putting up with us and watching over our shoulders, and mostly to Phil Strader, Prez at USPSA for granting us permission, even though he still had a bad taste in his mouth from some prior attempts. Oh, yeah, we aren't going back....it's electronic scoring or BUST! For those that attended, thanks, hope you had a good time and for those that missed stage 8.... ya never know, it may be back at a future time ... Alan Adamson Atlanta, GA
  11. All, it's pretty easy to install the SDK, and then I use the adb-wireless way of doing it, just turn it on on the nook, and type what it tell you to connect to it and then it's adb install <whatever>.apk. I downloaded the es file explorer and installed that on all my nooks, via wireless, then you can either install PS that way, or you can put it on sdcard. Alan
  12. Mark, here's the fix for both. a) it's a known issue that PS brings people back to EZWS as unclassified, it's an issue with the legacy interface that is used from the Palm days. So just update the classifications on EZWS and all fixed. If you post to PS.com from an IOS device (and soon from an android device) you can update the classifications there in the sync tab and everything is happen as well. On the second issue, I know what the problem is. The NOOKS use an IR mechanism to sense touch, it's not a capacity of Resistive displays, it actually has a very thin plane of IR that is directed across the screen from a thin light pipe that sets out in that recessed area at the edges of the display. If you get *any* debris, dust, sand, a hair etc out there, the device will detect that as touch and all kinds of strange things will happen.... Usually an early sign is that things that you press (primarily buttons) don't do what you expect, or the screen will just start to act strangely. The simple fix is to take a damp Q-tip and run around the edge of the recess. And take a wide canvas type paintbrush and sweep all the debris out of that area (do the two things in the reverse order ). That should fix it.... I did see one bug yesterday that I need to report.... but it was so strange and I remedied it so quickly that I doubt anyone else has seen it. Alan
  13. Chris is going to clean it up and maybe *webize* it such that you just give it the file from SSI and it will give you back the files fixed, both competitors and squad info. You then just import stuff into EZWS and go from there. Don't want to put any pressure on him as I know he has a million work/work projects, but we'll see... If it looks like a long pole, I'll send you the existing perl script. Alan
  14. I've got what they call a 3.5 moa round dot and side by side, you'd be hard pressed to tell any difference between it and a 6moa cmore module at the distances away from your eye that we shoot. To that point, watch for a classified from me. It's brand new and never been shot on a Arredondo mount. I'll be posting a whole bunch of mounts and scopes in the next day or so... Alan
  15. Ended up being 95 shooters in 7 squads, and 160 rounds 10 stage match. We used 10 devices, all NOOK Simple Touch's. Yes, I solved the what feels like a device gets sluggish and then starts to act strangely, it's dust getting on the IR sensors housing right at the flat of the display, but on the sides. After cleaning them all and brushing off the dust, all 10 devices ran just fine all day. We had zero issues, sync'd via wifi at the range to an Ipad (actually 2 of them) each time after I shot my slot in squad 7. Needless to say, we had the match scored, and uploaded before tear down was complete. We also used the PC basedup helper app from PS and had the EZWS file uploaded within 5 minutes of the PS upload .. Our integration was as follows. - Used Shoot-n-Scoreit.com to do online registrations - exported SSI's file for EZWS - use a small translator perl script to fix some things because import of competitors from SSI isn't fully baked (an SSI issue) - import the competitors, stages, and squads from SSI to EZWS - do any juggle of squads, and walk up registrations in EZWS at the range - export from EZWS, and import into PS - Shoot and score the match with PS - The post processing is pretty straight forward and what you do all the time if using PS. It was all the above that we tried new. It worked so well, that we got a standing applause at the shooters meeting for doing it! We even juggled 8 shooters from an 8th squad back into the other 7 squads due to people who registered and didn't show up. That only took a small effort and while a manual effort it paid off in not having to create an 8th squad and make sure it had RO's on it. We've still got a couple of tweaks to work through, but this was by far and away our simplest match to pull together and score with the PS way of doing things. About the only thing that was noteworthy.... We (practiscore) need to abandon the Palm legacy interface with EZWS, it's time now to get them to create the interface that is really needed between the 2. There are just too many things you *cant* do because of the palm interface ... But man is it nice to have that large of a match done, scored and scores out to shooters *before* teardown was complete! Alan
  16. It's not possible.... yet. We've got the request on the feature list as well as the ability to replicate the club db on a device to a second, third or nth device. Right now that club db is stored in an internal database and it's never used to update anything. But we'll get there I'm sure... Alan
  17. To add insult to injury ... I too find this annoying... We even have it with Practiscore... We've been using ShootnScoreit.com to register and let people squad... And this next math (saturday). I'm putting my foot down. A) Friday I'll be moving a few people to balance squads on SSI, the export the files, import them to EZWS in prep for the Match on Saturday and *NO* moves that day, you shoot with where you put yourself..... Tough beans, you've had 3 weeks to coordinate this if you can't get it right... Tough ... We'll see how far that gets me .... (yeah, I'm probably going to cave a bit, but not a lot, it's tough to talk walk up registrations and then have to juggle squads *AND* get devices out to score. Jim, (what follows is practiscore related) Most of us on the East coast are using Nook Simple Touchs. They are Approx $50-60 for a refurb on ebay, and they take all of about 5-10 mins to root and get ready for use. They are white paper readable in bright light (outdoors) and once you get over the refresh of the eink display, knock on wood, they've worked great. We had our very first match (107 shooters, 7 squads - big squads) have an issued with one unit, but we follow the rule of backing up with a simple paper strip sheet (yes, even on level 1 matches - good training for our state match upcoming). So even with the problem that we had, we had the match scored, and pushed out about 2 hours after everyone left the range. Normally, we have it done *before* setup is complete If I can help with the hardware, or rooting in anyway, just let me know. Lately, people have been buying units, sending them to me, I root them and get them back to you, all configured and ready to go. Alan
  18. Canned air is *really* bad however, it will lift the layers and blow the dust under the laminations so I would stay away from that at all costs... A small wide paint brush (artist type) works the best followed by a damp tipped Q-tip and then a dry one, all you are trying to do it get the dust and debris off the inset section of the surround around the display, there the bezel is inset. Alan
  19. So between stages, the squad takes the unit back to synch with either the master or a roving stats guy. Same concept as bringing scoresheets back to stats after you finish one stage and go on to the next. If you go the whole day without synching back to SOMEWHERE, you're booking one! First Law of Systems Programming: Back it up before you screw with it! And to Bills point... With the largish matches that we are working with (so far 107 shooters, 7 stages, 7 squads), all scored with PS. We are working to have the following - bay wide wifi (does not have to have internet) - 1 master unit, usually an IPAD because it has a feature that the Android platform doesn't at the moment, you can load the scores direct to the PS.com site - at least 2 backup units incase of equipment challenges - these can be swapped in at anytime as needed. - 2 of us doing backups (syncs) and it works as follows. - we use a Wifi device that will allow us to assign a specific IP address to a specific mac address (device). This allows the device to have the same sync code - always - at the original sync of shooters, stages, etc. We write down each devices sync code. - now when one or the other of us finishes shooting a stage, we walk back to our Sync device, and go through the list, syncing the other devices, this is a back ground task on the devices so they don't even know it's happening - now we have all the devices synced and a snapshot of the match overall on our sync devices. - we repeat the above after each time we finish shooting a stage. We are also in the process of trying a slight change. It used to be that we handed out a device and it stayed with the squad, but this last match, we had the squads leave the devices in the stages. This allows one advantage.... If for some reason you have change the definition of the stage, you only have to do that on one device.... However it adds a challenge if you had a walk up shooter that is shooting in one of the squads, you'd have to enter them on each of the devices as you moved through the match.... We'll have to see which outweighs the other. Alan
  20. The HUGE advantage over paper... Limited entry errors, Instant results.... And of course no trying to translate one persons chicken scratches into the correct values to then have to enter in to EZWS. In a word PRICELESS from a stats perspective. And yes, I know Ken is fond of the Ipod touches, but if you've seen one of the Nooks all your issues with screen, color, contrast go away, it's white paper in electronic bits in your hands and just as readable... Alan
  21. I guess I'll let the cat out of the bag.... AND THIS IS NO DING ON KEN's TEAM.... But until they roll out their web version, I used SSI (Shootnscoreit.com) to online register, squad and then import to PS and EZWS (including squads). Then PS to score, push to PS.com and bring back into EZWS for uspsa. It was actually much easier than I thought it would be. NOTE, it did take me to create one perl script to build the EZWS squad import file from the SSI data, but it was actually easier than I thought. And now with the IOS version supported classification updates, this is getting even easier. I'll try to document that process as well, and the associated, "ok, you have it in SSI, what do you do with it now", from a process standpoint the day of match. There was some learning that we identified that should make the next even flow even faster. As a note, it was a 40+ match and I had 33 of them registered online by the night before the match!!! Looking back on it, it worked awesome...and with some process tweaks during the *sign the waiver, and take the money* process, we know we can streamline even more. Alan
  22. Opps, I never meant my *simple* instructions to be the correct ones, and if you read the rooting instructions from top to bottom it will tell you a 2G SD is needed at a minimum. But yes there are nuances. If I get some time in the next couple of days, I'll try to give you a blow by blow.... Or if you like, I'm happy to root anyones that wants one... Just let me know and you can either have a refurb shipped to me or send me yours. It takes me about 20 mins to do one. (darn reboots and all) Alan
  23. let me chime in here before anyone gets the wrong idea... go read Ken's summary in the match scoring, practiscore section... My take, from all accounts with the exception of the memory issue that they found, identified and are fixing asap in a release, PS on this size of match given what it was tasked to do performed exactly as expected (with the one noted exception). Certainly they learned a few things on how to do this again, but all in all, it appears to be a raving success and it actually found a buglet in EZWS it appears at first blush ... Alan
  24. Way ahead of you there... Got Antutu CPUMaster installed and it set for 300-600mhz (down from 300-800). Will test it for awhile in that mode before making that permanent on reboot. Also spent some time researching this issue and guess what... It's a *well known* issue and actually not related to either hardware or software! Actually it is hardware related, but not how you'd think. It appears that these Nook Simple Touchs don't use a Capacitive or Resistive touch screen, they use something that uses IR and also has some way to sense pressure. It's a patented application made by neonode and called a zforce display... This is also why using a baggie to protect them from rain will not work. Here's the issue. What's actually happening is that there is dust and debris that gets on the display and as you use the device outside, it migrates to the edge of the screen. Well, it so happens that the IR TX/RX is also at the edge of the display and the debris refracts the signal and there by renders the touch sense ineffective, or sporadic. Because this plane of touch exists right immediately above the flat panel of the display itself, putting a baggie over the NST causes the IR to miss the touch because the thickness of the baggie raises the finger off the display by just that much and poof, no touch sense. As it relates to this debris issue, taking a fine brush, or Q-tip with the tip slight moist and running it along the edge of the display where it meets the bezel will remedy the problem. Now I've still got to prove this out, but I put my NST in my truck today let it set out of the sun, but in the warm interior of the car, for a few hours, it was nice and warm when I picked it up, it worked perfectly... so then I threw it in the dash with the display up and let it set... it was rather hot when I picked it up again and yet it still worked perfectly. Once in good light I looked at the edge of the display where the bezel meets it and could see how debris could be trapped there or pressed them from use. I took a wide soft bristled paint brush and brushed all the debris away... some of it has a static charge so perhaps using the Qtip *and* the brush is the best way to remedy this problem. I'll clean up the 2 suspect devices and see what happens, but from all indications this solves the problem, basically you just need to keep the display clean.... I so hope this is the fix... if so, then life will be good again! Alan
  25. As some of you know, we jumped on this bandwagon a few months ago, no regrets.... however, we may have found an issue, not with PS on the Nook, but with the device itself. I'm looking for feedback from people who use the NST regularly, in temps ranging from 70+, primarily for outdoor matches. I'd also like to know if the units that you are using are *new* or refurbs? Here's why. We have probably 12 of these things scattered between 3 clubs. What we are seeing is that as the devices are used in direct sunlight, and used to score 10-14 shooter squads, across 6 stages, that they are either developing a temperature sensitivity issue, or a screen issue. What happens is that they start to loose the registration on the display, they start to become sluggish (more so than normal with the e-ink display), and they will start to not register screen touches To the extreme, they will feel like they have locked up. However, if you get them out of the sun, cool them off by moving them back and forth in the air, and only touch them on the sides with your finger tips while holding (as opposed to cupping them in the palm of your hand), they will recover and continue to work. For some reason out of the 12 or so that we have, a couple seems to be more prone to this than any others. Those 2 happen to be refurbs. I'm about to make some tests with my personal NST and see if I can recreate the issue, mine is a *new* device and so far, I've never seen it act this way. It's either a hardware problem with a couple of devices or an endemic issue with a device being used in a way that it wasn't intended. And it's either heat or sunlight that's causing the problem. I figured I'd see if others have seem this symptom? I really don't want to debug the worlds problems with this tread, so please try to keep it on topic. We also use a set of refurbs in an indoor range, one that scores 16+ shooters on 4 stages, this range isn't exactly cool as we head into the summer, and yet we've never seen this problem with the devices in that scenario (which would be high usage in the 70+ degree category). However, remember, the black back and black bezel, will generate more heat to the device in direct sunlight, that it will indoors, so that may be the issue.... I guess I'll get my IR Thermo out and see how hot the device is when it gets this way. They don't feel uncomfortable to the touch I know that part. So, let me know, Alan
×
×
  • Create New...