CADmep 2022 Product Listed Converted 3D Models (CID 1175)

[edvance0108]

Greetings.

I have encountered an issue with CID 1175 that appears to be specific to CADmep 2022. When creating a 3D Model List of multiple Pipework 928s, the Diameter fields only read from the first 928 ITM in the product list and seem to be detached from any others. Performing the same operation with the same files in 2020 & 2021 the diameter fields all read properly to the reference 928. This is quite problematic as there is often a need to manage pipework components that cannot be represented by a typical CID.

I'm not sure the Idea board is the appropriate place to bring attention to this quirk. However with the work around being to revert to a previous release, the issue should be resolved so it does not make its way into future releases.

[Jason_Sherwood_]

I have been fighting this for a while, have you written a ticket on this? If not I will do so.

[edvance0108]

@Jason_Sherwood_ 

No I unfortunately haven't written a ticket so I'd be super appreciative if you would.

I assumed that was a thing that was possible but I don't know the proper channels to do so.

Out of curiosity how have you been managing this issue? Shortly we won't have licensing for 2021 so my work around might soon fail.

[Jason_Sherwood_]

We use Revit Families.

[gmurphy]

We use Families for for some items also but when we want to do Tracking and need Labor attached we need them as this CID 1175.  So currently we do them as single size items as CID 1175.  The issues with that is to change them out with a different size you have to delete and replace.  If they were Product Listed then we would be able to swap them for size.

[Jason_Sherwood_]

I wrote a ticket,  it was functional albeit tedious work to build.

This works in Revit 2022 and newer (2023 has not been tested by me).

The Steps to getting it to work are as follows.

1. For each size of Model item you need to use the Convert3dmodel command which will give you a pattern 928 use the connector block to identify the connector shape and size. 
2. Set all the item properties and connectors 
3. Right Click in the white space of the folder where your 928's are and select the new 3d model item command to turn each of the 928's into 1175's. 

    

   
4.  Once you have all the sizes of the 1175 built make sure all the item properties and connectors are what you want with those by repeating step 2 again, they will default to ductwork and also some bizarre materials etc. I don't know why they don't inherit the properties of the 928..... I think I'll write a ticket on that because this is a tedious process.
5. In the folder where the 1175's are right click and create a new 3d Model list of the 1175's, use Ctrl to select mutiples once you have browsed to the folder.
6. Once all are selected and you hit open you will once again get to repeat setting all the properties in step 2, have fun with that.
7. After setting the item properties you need to open the product list and add and define the Diameter #1, and Diameter #2 Sizes.
   
8. You now have a Model listed part, you can add fields to the product List along with any Custom data you may have in your database.
   

   I hope this helps 

[Jason_Sherwood_]

Testing

[edvance0108]

@Jason_Sherwood_ 

Thank you so much for making a ticket and looking into this further.

I didn't even consider product listing the diameter fields since previously it was always just tied to the diameter of the source 928, also doing so would make Revit throw a fit pre-2022.

I just ran a brief test with this in 2023 and it seems you can skip your steps 3-4 of creating individual 1175s and just Create New Model List directly from a selection of 928s, and then product list the diameters. Then you only have to go back and set all the item properties one more time lol.

I have not tested the behavior in Revit, but CADmep side all seems well.

However, depending on your application, it may be better from a performance perspective to only keep one 1175 per 928 source anyway. I recently learned each model instance of an 1175 carries the cumulative memory requirements of each Model Listed entry, which I guess makes sense. That sure makes it difficult to manage database side though, just thought I'd mention it since we're on the topic.

PSS. New for 2023 connectors with setback values no longer double said values when wrapped into 1175. So the same part when viewed pre-2023 will draw the connector in a different location than it would when viewed in 2023.

[Polk_Matt]

So for pre 2023 connector setback being doubled, what is everyone doing to make the setbacks right?  i would like to be able to create the itm's once and not have to have a version for pre 2023 then have to make them again for 2023.  Thanks.

[edvance0108]

@Polk_Matt 

The biggest problem with this is that they only implemented the fix in 2023 and didn't in any earlier releases.

That becomes a real problem if you or your department are working out of multiple release years, because the same ITM's connector will appear in a different location depending on which version that user is using.

I have not found a good solution for this, it is pretty damaging.

The only real way would be to have 2023+ users working out of a separate database configuration that supports the connector setback 'fix', which would be ridiculous.

However, If you are only concerned with how to manage the connectors and the multiple versions issue doesn't apply to you, I would just update the affected connectors' setbacks after you have moved on to 2023, which was probably their train of thought.