-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Maybe move trigger pin up a little? #4
Comments
Considering new defects with the trigger pin switch, best to get rid of it altogether. How about replacing it with a piece of spring that goes across the PCB gap like this... To load the TSL, you have to insert the pin unto the end cap and then insert the PCB into the end cap slot. The pin pushes the spring off of the contact point as you slide it in. When the user pulls the pin, the spring returns back to the contact, closing the circuit and starting the count. Nice side effect is that after the pin is pulled once, the spring is completely out of the way and never touches the pin again when the pin is taken out and reinserted later. The user never even sees the spring unless they disassemble the unit and unscrew the PCB from the endcap. The end of the spring and the contact could be gold plated where they touch for extra protection. But remember that this switch only has to close once! |
i love this solution! So if we go with this trigger, we would load the firmware with the pin already loaded? or do we assemble the cap with the pin inserted after loading the firmware? |
We would want to test that both opened and closed states work, and probably the easiest way to do this is from the firmware. So maybe...
Note that these steps can have long delays between them. See any problems with this workflow? |
this should work! |
Current location just seems wrong and prone to having the pin break off. Maybe a little higher would be better?
The text was updated successfully, but these errors were encountered: