Liberty556

Update: Unfortunately, the Kidd kit is not totally compatible with the PC Carbine. The hammer appears to tend to follow the bolt rather than reset, and so you get some burst fire every other trigger pull or so.... I think the disconnector may be jumping the engagement on the hammer. If you use the factory hammer, though, the problem stops. For the money, I would still recommend the upgrade if you want to shorten up trigger overtravel / reset. Just don't use the Kidd hammer. Hopefully they will come out with a more robust hammer for the PCC.

Here's one for the KIDD, which I just installed. Outstanding trigger. I also got their trigger spring tuning kit: https://coolguyguns.com/KIDD-Pull-Weight-Tuning-Spring-Kit_p_120.html I installed it along with the green 3.25 trigger return spring. I made no adjustments to the overtravel or sear set screws. Now the trigger has No pretravel, No overtravel, and a super short trigger reset. Trigger is rock-solid with a clean/crisp break. These two items from Kidd (trigger kit and springs) are all you need to upgrade the PC Carbine trigger, and nothing you don't need. As of this writing, including shipping, I paid $117.50

It is usb powered. We paired it with an Anker 2nd-Gen Astro E5 High-Capacity 16750mAh, which seems to hold it's charge for literally months at a time. I actually think I have used it for a year without recharging. We don't run the router for the whole match, just when synching before and after. Once we did forget to unplug the router from the battery, but 7 hours later the battery still showed full charge.... so who knows how many hours you would get out of it. Probably overkill for this little router. As backup batteries for each of the Kindle 7's, we got an Anker PowerCore+ mini, 3350mAh Lipstick-Sized battery which would probably be more than adequate for the router. The router comes with an A/C adapter as well as a mini usb connector. (the Anker batteries also come with usb connectors.) I don't think you can go wrong with this setup. https://www.amazon.com/gp/product/B00N2T7U90/ref=od_aui_detailpages01?ie=UTF8&psc=1 https://www.amazon.com/gp/product/B005X1Y7I2/ref=od_aui_detailpages01?ie=UTF8&psc=1

We use a ZyXEL Wireless N 3-in-1 Travel Router and have had up to 9 devices on the LAN. There is no limitation to the number of connected devices that I can find (other than the ip range of course...) just like a regular router. $28 at Amazon. https://www.amazon.com/gp/product/B005WKIKA0/ref=ask_ql_qh_dp_hza

Been using Stripe for nearly 2 years with no complaints. We are hopeful that they will support tiered payments soon.... Also, personally I will not use Paypal for anything. They are anti-gun. Will not allow the sale of any firearm parts, or ammo. Screw them.

Me: How does this work regarding Stripe? Does it automatically adjust the amount charged to the credit card (reduce the match fee paid at the time of registration)? Ken: It does. It just changes match fee for that competitor. You can use it to cut price for whatever reason or to raise it if , for instance, the person is late registration or bought t shirt ------------------------------- Cheers!

I did, thanks. I'll post what I learn.

How does the approval with discount work? After they have paid the full fee at registration, does it adjust what Stripe charges their credit card?

Thanks for the info. I'll shoot an email to support as well.

At our club, we would like to take advantage of online payments on a regular basis. Currently, we only do so with "special" matches, where all competitors pay the same fee. At our regular monthly matches, members pay $10, and guests pay $20.... Are there plans to allow for tiered fee schedules for online registration, at some point in the future? We had considered trying to use the "down payment" as a work-around, but feel it would be too "messy". Does anybody have any ideas or suggestions? I briefly searched around, but did not see any relevant posts. Thanks.

The 6 Fire tablets were off (not sleeping). I turned on / booted up / restarted each one, then had to manually reconnect to the pocket router, as they don't auto reconnect if no internet connection... After they all restarted I ran PS on each and started syncing.

Ok... Powered on all the Fire Tablets, connected to the pocket router. Samsung master already on pocket network. 4 of the 6 Fires listed all devices, 2 Fires had partial lists. The Samsung did not find any of the 6 Fire tablets. Multiple manual refresh did not find additional devices for either the Fires or the Samsung. Tried this for maybe 3 minutes. The Samsung master was listed in all 6 Fire tablets, so I pulled a match to each Fire. After doing the pulls, all the Fire tablets showed all devices in the sync list, and the Samsung now found all the Fire tablets.

1.3.9 (on all devices)

I'll have to verify, but IIRC manual refresh while on the pocket router network finds some but not all devices, or at least it doesn't find them all at once. It either takes some minutes or additional manual refreshes to find all devices. While on the home network (with internet access) all devices are found immediately. My recollection is somewhat muddied from between the two different network connections. As I cycled the power, the Fire's would auto reconnect to the home network, not the pocket router.... At the end of my troubleshooting session I ended up "forgetting" the home network from the Fire tablets to avoid future confusion, and also prevent any auto updating of the Fire tablets ( such as the annoying Wall Street Journal app push ). I'll experiment some more tonight and see what the refresh behavior is like.

Ahh, That must be what I was mismembering...

Success! Forgetting the network on the Samsung, then re--connecting, reset the sync code. All devices have unique 4 digit sync codes, and all sync with one another successfully. I went ahead and then gave all devices static ip's, just in case.... I cycled the power on all 6 Fire tablets, reconnected to the network, and a few had old sync codes, but eventually the correct codes for all the Fire tablets appeared. It is nice to now be able to remove (old) devices ( or in my case, duplicate listings with bad sycn codes ) from the sync list of devices - is this new in 1.3.9? The refresh is still a little slow / spotty, but updating the list manually works fine. Also noticed PS now rotates to either portrait orientation on my Samsung tablet - so now I don't have to "flip" the tablet 180 every time I launch PS It seems I am good to go for the next match. Thanks for all the help. -Doug

Ok. I got the short sync code on the Samsung master, but one of the 6 stage tablets shows the same code. Killing PS from the app manager on either stage tablet or master tablet does not resolve the duplicate sync codes. Also restarting the master tablet did not work. Dropping the Samsung master tablet off of the network leaving only the Fire tablets, I was able to easily set up a match on one of the Fire's, and sync them all up without a hitch. It appears that for some reason, the Samsung tablet does not play nice with the Fire tablets unless the network connection has internet access...? Looks like I'll be needing to use a Fire tablet for the master.

Updated all devices to Practiscore 1.3.9 Powered up the pocket router. 3 of 6 Fire tablets sync'd to the Samsung master without a hiccup. The other 3 failed. The sync code of the Samsung prior to this latest attempt was 6465. After 1.3.9 update and logging onto pocket router network (no internet access) practiscore appended the code to 6465E7A1. It assigned 6465 to one of the Fire tablets. The Fire tablet with 6465 showed the master tablet as having sync code 6465..... After 5 or 10 minutes some of the failed tablets refreshed and showed the master tablet with the correct (new) sync code of 6465E7A1, but would still fail "Connection Failed". In fact, now one of the original 3 Fire tablets that did succeed now fails to connect to the master - so only 2 of the 6 Fire tablets are able to connect with the master. After typing the above, I am down to only one Fire successfully making the connection. After refreshing a failing Fire, it now succeeds.... It appears to be a constantly varying condition of alternating success/failure, unfortunately with a minority of tablets finding fleeting success. After switching all devices over to home network (with internet access), and manually entering new master tablet sync code, all devices synced immediately. With a refresh, all devices promptly listed one another in the sync list. (on the pocket router network refresh rate was slow, device listings were incomplete, and varied from tablet to tablet). It appears that internet access on the network is the key. Otherwise at first glance, v. 1.3.9 looks excellent. Liking the sync feature on the main screen. Also when you delete a shooter, they immediately are removed from the listing, rather than needing to leave and come back to the screen to see the change. Haven't read the change log yet.... looking forward to doing so and giving it a proper shake out at the next match. Cheers!

Will do that, too I thought I had, but probably "edited" it out in the process of re-writing the post in the attempt to articulate my issue... Good to know regardless. Thanks.

Will do, thanks.

We are running 1.3.8 on all devices. 1.3.9 not yet available, no?

I apologize up front for some fuzzy reccolections of what exactly happened.... "heat of battle" and all.... Just upgraded from Nooks to Fire 7's. First time running Fires. Created match and imported registration on Samsung tablet while on home network. Following (match) day went to range, finalized match registration on master tablet, and used different network (pocket router) to sync stage tablets to master. Only one out of 6 Fire's would sync the new match from the master. ( IIRC the other 5 tablets saw the master tablet, but not the current match - i.e. "no changes" message. Also, the sync code(s) may have been off). Had to sync remaining 5 stage tablets to first stage tablet. At end of match, had issues syncing back to master. Not sure exactly... pretty chaotic trying to get it to work. Returned home, to home network, and was able to get everything to sync successfully. Noticed the sync codes were more "alpha-numeric" than previously... Are the sync codes created in such a way that changing networks during the whole process can create issues for syncing? By creating the match on the master tablet on one network, then on a different network syncing up the stage tablets cause problems? Also, I noticed the the Fire tablets will not auto re-connect to a network that does not have internet access. Maybe somewhere down in the code this could affect things...? On the Nooks we had issues during initial syncing of stage tablets to master where we had to reboot and reacquire the wifi network (pocket router), but once wifi was reestablished, we had no syncing problems (manually entering sync codes - refresh/discovery was never very good with the Nooks). Thanks. -Doug