Replies: 59 comments
|
That's awesome work. Thank you! I added your name to the project Contributors section of the Readme. I'll figure out how to add it into the release pipeline. That will make it readily available for the upcoming version, and thereafter. In the meantime, you might get more exposure if you repeat your announcement on the SE Forum. Most of the traffic for this project and Housekeeper come from there. |
|
This initial release is mostly for you to think of a way how to add it to the main release. As part of the main release or as a separate download. I Don't think end user should edit excel files. Generally adding new items to the database or combining more databases is pain in the ass. There are still some items that I want to add. Maybe next release I will post on siemens forum. For now I will post only here. |
|
That makes sense. I've got some vague ideas on how the integration might be done, but need to think it through. Totally agree about using Excel. It sounds good -- until you need to add/change something. Also the syntax around property mapping, formula creation, etc. is cumbersome. |
|
In terms of integration, I'm wondering about simply renaming the original I could copy both to Thoughts? |
|
There won't be any file conflicts or duplicates. |
|
Yes, please post your updated data and templates. We have some work to do on fastener stacks. To get a sense how it is implemented, here's the Documentation. Here's how the pre-configured files are named. (They are stored in
Legend: F = Fastener, FW = Flat Washer, LW = Lock Washer, N = Nut. To create Part of the process to find the corresponding components involves moving up and down the Xml tree, searching for component names. For example, to find the flat washer for a given fastener, the program moves up up three nodes, then searches that collection for a node named "Washer_Flat". It then opens that and searches for a matching NominalDiameter. I'll have to create a mapping between our data structures. That shouldn't be too hard. The program uses these variables.
While I can deal with different data structures, I'd rather not try to accommodate different variable names. They're literally everywhere in the code. I don't think it would be impossible to reconcile our two naming conventions. I'm mostly thinking what happens with a growing number of contributions from others. If that's a big pain for you, let's talk about it. I really appreciate your contributions and continued interest in the project. I want to keep that going. |
|
First I need working version to see what I can do with it. 2025-09-14 update release
ISO 2982-2 Rolling bearings - Locknuts DIN 7984 - Hexagon socket head cap screws with low head with reduced loadability AN315 - Blind rivet nut knurled - flat head known issues
https://drive.google.com/file/d/1uzYTruREdZ2awtm_qbNW85p9zXqQo3Kx/view?usp=drive_link |
|
Wow. That's awesome! I'll adapt my fastener stack code to be compatible with your data structure. I'll let you know when it's ready to test. |
|
I was able to create a fastener stack from your dataset today. I seriously doubt it's bug free. Let me know what you run across. There are several things I should mention. First off, I renamed DefaultData to DefaultDataSE2024 and added DefaultDataSE2019. I did the same for templates. As I mentioned, some variables have to be renamed. There are four of them; they're listed in my previous post. As you know, the variables occur in many places -- the templates, storekeeper.xls (like in the filename and description formulas), companion spreadsheets, and possibly more I forgot. NominalDiameter is required in the spreadsheets and templates, even if it's not used (like with flat washers and lock washers). I need it so I can match the component size to the fastener. Speaking of lock washers, in my testing I used ISO 2982-2. Those do not appear to be for fasteners. I don't know if ISO-Land uses lock washers. If not, there are several stack configurations that don't apply. As I mentioned, there are templates for the various top and bottom stack assemblies. I would give you mine, but they're in SE2024 which won't help. Here's a couple examples of what they look like.
In the fastener stack dialog, any component should show a file name. If instead it says Flat washer (or whatever) it means the file was not found. In my testing, that usually meant I forgot to update some variable name in one of the spreadsheets. Missing variables or other mismatches can lead to seemingly unrelated errors. I had one where it was complaining about the Anyway, sorry to babble on like that. Here's the link. |
|
Oh, got it. I'm working on error catching/reporting right now. Depending on how much time I can dedicate, it might be a week or two before a new release could be ready. I'll check in with you then. |
|
Good deal. Yes, you need NominalDiameter is the spreadsheets and templates, even if it isn't used in the model. That's how I find the components that match the fastener. |
|
I just uploaded a new preview to Google Drive. It has much improved error checking and reporting for fastener stacks. One thing it doesn't have is the correct location for your lock washers. The first time you run the program, it will create a file By the way, I noticed a few entries in your Anyway, here's the link. |
|
Yeah, seeing the same on V2025. |
|
2026-08-14 update release
Polish data base
https://drive.google.com/file/d/1gJ6GALZaPmWaF98wjR2xatNDPEMi_wrK/view?usp=drive_link |
|
Good deal. I should have a chance to get everything integrated starting tomorrow. Quick question -- what does "override required" mean exactly? Is that something users have to worry about, or are you just noting that I need to replace the old with the new? Also, you previously mentioned adding split pins. Didn't you also add some structural items, too? I want to make sure I get everything captured in the release notes. |
|
Since your release is official, all the information are mostly for you. You can assume that you have to replace With this release I didn't add any new items. Last time I added only split pins. I'm tracking changes in |
|
Sorry for the delay. I got interrupted. I'm back now. Got your new data. Looks good. I especially like the Polish version. I'm going to add a screenshot of that to the release notes. Once I get everything integrated, I think I'll make one final preview. That will give us both a chance to do a quick check before release. How's that sound? |
|
I found one issue with fastener stacks using the Polish dataset. I have some hard-coded XML node names from your English version. I may be able to fix it. Could you translate the following for me? (I just need the text following |
|
Never mind. I keyed off of the part numbers and found what I needed. Please double-check if you don't mind. |
|
Uploaded a new preview just now. I did a quick test and it worked for me. Let me know if you run into anything. The main changes were to integrate your new dataset, and add return-to-accept in Here's the link: |
|
No rush at all, but I was waiting for your "OK" before finalizing the release. I can see now that I didn't make that clear in my last message. |
|
Sounds good. Hope you had fun on vacation! |
|
You can prepare stable release. No issues so far. I would add info in the release note about replacing all templates as this is required. |
|
Good point about the templates. I'll add that to the release notes and get it going. I missed your earlier comment about fastener stacks. I need to check the readme; I thought for some reason those didn't work in SE2019 or SE2020. Sounds like they do, is that right? And, yeah I fixed how stack components are searched in PB6. The previous method was probably responsible for that PB5 error you got. |
|
Fastener stack had some issues at the beginning. The problem is with auto patterning due to API. We discussed it here #12 |
|
Oh, got it. I was mixed up. I'm working on the release now, and hope to get it out today. |











Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Hi everyone
My custom database for "SE storekeeper". This version does not include any of the items created by Robert.
Standards in database
Change log
2026-08-14
update release
#16 (comment)
2026-05-16
update release
#16 (comment)
2026-01-06
update release
#16 (comment)
2025-10-24
update release
#16 (comment)
2025-09-28
update release
#16 (comment)
2025-09-14
update release
#16 (comment)
2025-08-17
Initial release
https://drive.google.com/file/d/1gJ6GALZaPmWaF98wjR2xatNDPEMi_wrK/view?usp=drive_link
All reactions