Thread Content
The specifications purchased by the company aren’t very suitable, so we had to create our own database. I worked on part of it, but during preliminary testing it turned out that when two vertical pipes meet, a tee connection cannot be generated automatically; however, this can be done using the specifications from the accompanying GB database. I compared the tees and pipe connections in our custom database with those in the GB database, and their properties are basically the same. Even if there are some differences, they are of a descriptive nature and should not have any impact. I tested and found that 90-degree bends can be generated automatically – they appear right away. I also checked the data: the two vertical pipes are in the same plane, so there’s no issue with misalignment. The red pipeline lines after connection show that they are indeed connected, and it’s possible to select components for additional connections as well. But the problem is that a tee connection cannot be generated automatically. It’s quite frustrating. Although using the tees and pipes from the GB database could solve this issue, it would result in an incomplete database of our own, which would make future modifications difficult. Additionally, I was wondering if it’s possible to copy components from one database to another existing database – not by creating a new database based on the original directory, but rather by moving a component family from Database A to another existing database in a different directory. Please give some advice.
The branch table needs to be created
The tee component might not be able to be added automatically because there isn’t a suitable one in the library you created; you can take a screenshot so I can take a closer look.
The tee cannot be added because it isn’t specified in the branch pipe table; simply add it in the branch pipe table settings of the specification editor