Replies: 34 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. |
Beta Was this translation helpful? Give feedback.
-
|
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. |
Beta Was this translation helpful? Give feedback.
-
|
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. |
Beta Was this translation helpful? Give feedback.
-
|
In terms of integration, I'm wondering about simply renaming the original I could copy both to Thoughts? |
Beta Was this translation helpful? Give feedback.
-
|
There won't be any file conflicts or duplicates. |
Beta Was this translation helpful? Give feedback.
-
|
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. |
Beta Was this translation helpful? Give feedback.
-
|
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 |
Beta Was this translation helpful? Give feedback.
-
|
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. |
Beta Was this translation helpful? Give feedback.
-
|
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. |
Beta Was this translation helpful? Give feedback.
-
|
ISO 2982-1/2 is a very bad choice for testing. These items are used to lock bearing, wheels ect. on the shaft. Typical lock washer is DIN 6798 A for example, Nord-lock, Schnorr, just didn't add them do DB. If you are talking about spring washer, ISO standard doesn't have them and DIN standard is withdrawn but you can still buy them. 
Don't know how much more work do you have with v2025.4 but you can release it with annotation that fastener stack won't work with DB2019 for now. And don't worry about your babble, each info from you is precious. |
Beta Was this translation helpful? Give feedback.
-
|
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. |
Beta Was this translation helpful? Give feedback.
-
|
Still working on integration of your data set with fastener stacks. I took the liberty of adding my variables to a couple of your files. It worked one time, so far. I'm still finding bugs, so haven't posted anything to Google Drive yet. 
.
|
Beta Was this translation helpful? Give feedback.
-
|
I have spent some time with my DB I can say that adjusting it to work with fastener stack should not be a problem. I will have to add 3rd row in excel to keep my old variables as drawing references and change model variable formulas. 
ThreadDescription (fastener, nut) - was already there, no change needed NominalDiameter (all components) - I'm not sure about this one. Is it variable that change model or is it as a reference? For example washer model needs only 3 variables, inside/outside diameter and thickness. But ND is as a 4th variable. |
Beta Was this translation helpful? Give feedback.
-
|
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. |
Beta Was this translation helpful? Give feedback.
-
|
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. |
Beta Was this translation helpful? Give feedback.
-
|
I wasn't initializing the Materials List. See if this helps. |
Beta Was this translation helpful? Give feedback.
-
|
@rmcanany Make sure you delete all the old files before you use this release. Check my version of 2025-09-28 update release
known issues
https://drive.google.com/file/d/1Uw40H5VMebQur5GSolDPigMuSpOrDYib/view?usp=sharing |
Beta Was this translation helpful? Give feedback.
-
|
I was testing patterning fastener stacks with your data today. If the top stack includes a flat washer, it works with hex head cap screws, but not socket head cap screws. I tracked it down to the replace part command when updating the temporary fastener stack assembly file. For some reason, the relationships between the flat washer and shcs get broken. For somewhat complicated reasons, that screws up my accounting of fastener stack parts when dispersed into the assembly. Not sure you want to mess with it, but it would be nice if the relationships were maintained. That breakage also means the replace part function can cause headaches for users. I included a few notes about custom template creation in the Readme. It was added after you were already underway with your data set, unfortunately. Please note, my write up tries to emphasize that any suggestions are only suggestions -- it's completely up to the creator to do it as they see fit. |
Beta Was this translation helpful? Give feedback.
-
|
Were you testing fastener stack on my or your templates? My templates are untested. Because you are hard coding im not able to test it. Edting json wont help, all changes are reverted back. The other problem with FS is that user can't change washer or nut. I can only use the one you hard coded. In this release i added DIN 127 as lock washer. |
Beta Was this translation helpful? Give feedback.
-
|
I was testing on your data set. Except for the patterning issue, it was working great. Did you try it on the preview I most recently uploaded? I thought I fixed the issue of not finding the flatwasher and nut. Could you provide some details of what's going wrong? I'll check about the *.json reverting back. I think I know where that's happening. You're right about the fixed stack configurations. I plan on making that customizable eventually, but wanted to get something out there sooner rather than later. |
Beta Was this translation helpful? Give feedback.
-
|
Overwriting the fastener stack I also added a locale fix for decimal separators. I needed that to be able to use your Thickness variables in my locale. In one case, it was unhelpfully converting https://drive.google.com/file/d/1H0Y2FGiRWPNgUb3xLkW4SxdO0ej7Eaai/view?usp=sharing |
Beta Was this translation helpful? Give feedback.
-
|
A few tweaks, mostly having to do with dealing with illegal Xml characters. Not sure it affects you, but you might as well have the latest... https://drive.google.com/file/d/1YZI1khzlr3og6B1f3oI47iauH2SQZAHi/view?usp=sharing |
Beta Was this translation helpful? Give feedback.
-
|
Original SE standard parts breaks relationships as well when you change from hexagon to socket. Some screws have additional faces and can be impossible to keep relationships unbroken for all of them. Are your all screws maintain relationships? |
Beta Was this translation helpful? Give feedback.
-
|
I haven't tested them all, but I think so. Well, not for flat heads, of course. And, by the way, it's not the end of the world if a user has to fix some relationships and pattern the stack themselves. Anyway, the way I did it was to start with the socket head cap screw. I first modeled the shank, then the head, then everything else. When it was time to make the next fastener, I did a Save As of that one and modified it as needed, keeping the shank and head intact, except for dimensional changes. An example would be going from a socket head to a hex head. I first deleted the socket cutout. Next I adjusted the head height and diameter. Finally I cut a flat and rotated the cut to make the hex. 
|
Beta Was this translation helpful? Give feedback.
-
|
I think this is getting close, unless you are still tweaking things. If you're ready, I would need your latest data set. The link to the latest preview is below. The program should now hopefully trap/report errors without crashing. I also added a new |
Beta Was this translation helpful? Give feedback.
-
|
@rmcanany Make sure you delete all the old files before you use this release. You keep old files which I don't use anymore and it can be confusing. For DB as well as for templates. 
2025-10-24 update release
added to data base ISO 7045 - Pan head screws with cross recess known issues ISO 2982-2 Locknuts: some threads are generated incorrectly, no thread texture https://drive.google.com/file/d/1TpTm9Alydhot9xdz21eeYOArsrRrJjqc/view?usp=sharing |
Beta Was this translation helpful? Give feedback.
-
|
That looks great. Nice job! I got a little busy all of a sudden. I'll play with it next week hopefully. I'm pretty sure you said that auto patterning didn't work in SE2019 or SE2021. Please confirm and I'll update the documentation. I will emphasize that it's not because of your dataset; it's a Solid Edge problem. Auto pattern works fine with your dataset on SE2024. |
Beta Was this translation helpful? Give feedback.
-
|
Im still waiting for the video from you to confirm it. |
Beta Was this translation helpful? Give feedback.
-
|
Didn't mean to make you wait, sorry. I just made a new preview with your updated data and templates. I didn't test anything. I didn't change anything else, either. Hopefully it's OK. Here's the link: |
Beta Was this translation helpful? Give feedback.
-
|
Hey @TeeVar I released V2025.4 today. Here's the SE Forum post. You should take a look -- your name is everywhere! Thank you for all your efforts. The program is a lot better because of you! Closing as complete. |
Beta Was this translation helpful? Give feedback.
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
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/1Uw40H5VMebQur5GSolDPigMuSpOrDYib/view?usp=sharing
Beta Was this translation helpful? Give feedback.
All reactions