-
Notifications
You must be signed in to change notification settings - Fork 686
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
Rimowa tsa006 too small #22
Comments
Interesting to get a lead on the elusive 006, but honestly can't do much with these pictures. We really need the numbers from a decent set of calipers to do anything with accuracy. Since I'm guessing that's not something you have access to, it would probably be more effective if you can take a closeup of the printed key lined up with the opening, that way we could at least make an estimate visually on what the difference is. Off the top of your head, how much bigger do you think it needs to be? A lot, a little? |
This is good info. If you can get some precise measurements, I can push a beta key to my repo here: https://github.com/johnnyxmas/TSA-Travel-Sentry-master-keys/blob/master/TSA006_stubby.stl The 006 I have in there now seems like the width might be correct, but not the height. You're welcome to print it out and try. More interesting is the row of pins. If what you say is true (I understand it's just speculation), I'd look into adding the rows of 4 dimples on each side of the top of the key, at the very least making a potential rake out of it. |
Hi Johnnyxmas, As I said before, the luggage is still traveling and will be back in a little while. I'll be able to give better measurements of the keyway then. I did print out the xyl2k_stubby_006 stl and my comments above reflect my initial experiences with it. Your stubby006 stl fork seems to be the same exact dimensions as xyl3k's. So without scaling up a bit there's no real reason to print and test yours also. The pin layout is not so much speculation, as much as a cursory inspection. I could not identify any pins for the lower half of the keyway. As such, a minimized bump key should only need 7 dimples, but can only be inserted one way. If you are going to go though the trouble of making a bump key, why not just do all 14 dimples so it can be symmetrical? Then you could use it by feel when you have to bump luggage locks in the dark... :) But why make a bump key at all? TSA locks of the same type should never be keyed differently. i.e. when you have a TSA key, you have the key to open all TSA locks of the same type. Bumping need not apply. I'll come back with some numbers or a solution when the wife gets back. -m |
Sorry, Q3 & Q4 are nuts in my profession, so I haven't been in the repos in a few months. I'll get back to it soon as a few of us are putting a panel together for the Hope conference in NYC next summer. |
Heya Johnnyxmas, Hope your job lets up soon. after all, the holidays are almost upon us. Raking is still along the same lines...why rake if we already have pin placement and depth? A rake (or alternatively, a bump key) would only be useful if the locks are keyed differently. As we know, all the locks for a particular key type are keyed the same. So I am not sure when you expect to run into a case where you have the same keyway but not the same pins. The tolerances on the Rimowa lock seem more than adequate for a luggage level theft deterrent. If you didn't know the dimple depths, I think it might be not all that easy to rake...though I haven't tried. -m |
FYI new versions of 006 have been uploaded to my testing repo here: https://github.com/johnnyxmas/TSA-Travel-Sentry-master-keys |
My wife doesn't know how to operate her luggage and decided to spin the number wheels and set a new code.
I printed out the current stl on my prusa using PLA and also on a DLP resin printer.
I found that the key was too small.
I know my wife is going to pull the same stunt again, so I am committed to drafting a working key.
I believe if I scale the current key, it should have a good chance of opening the lock.
Enclosed are rudimentary pictures of the keyway.
-m
The text was updated successfully, but these errors were encountered: