Mapping Revit Families to Fabrication Parts

Anonymous

Mapping Revit Families to Fabrication Parts

Anonymous
Not applicable

Our company is currently transitioning into Revit 2017 and making our HVAC Fabrication Database compatible with it. Our only issue is making sure specific Revit families convert to specific parts using button mapping; so if the system was designed by an engineer with short radius elbows versus full radius, the system converts cleanly with minimal amounts of gaps and failed conversions.

 

I tried to do this following these instructions:

 

http://help.autodesk.com/view/RVT/2017/ENU/?guid=GUID-DD4BE206-56AE-41AC-AB56-2AC9B8FB62C0

 

Only to get the Revit warning "Not all parts were converted. Check the fabrication service definition."

 

After playing around with it, it seems I'm limited to the default, generic design line button codes (Bend, Offset, RedInline etc) as it's the only way Revit will convert the fittings successfully.

 

Is this the case? Does the custom mapping only work for specific types of Revit families or am I missing something?

 

Kyle

 

Screenshots have been attached of current configuration.

Reply
Accepted solutions (1)
1,052 Views
3 Replies
Replies (3)

Anonymous
Not applicable

Not sure if Revit is using 100% of the logic Fabrication is, but I would assume it does.

 

You just need to have a button mapping for both versions of the elbow and put the desired (long) higher in the list than the short. If it can't fit the long and it is higher in the list, then it should use the short automatically.

0 Likes

Anonymous
Not applicable

Unfortunately, no.

 

Revit currently behaves by referencing the top button code and if that fitting won't fit, Revit removes it and courteously splashes you with a warning.

 

It also doesn't distinguish between radius and mitered elbows. It always defaults to the top button code.

Anonymous
Not applicable
Accepted solution

I submitted a help ticket with Autodesk and have now officially heard back from the Autodesk Development Team:

 

"The method described is only valid for "inline" equipment like valves and dampers and does not work for built in key components like Bend, RedInLine, RedInLineTee etc. These types are converted using the standard button code mapping. Mapping different bends to different buttons is not allowed, so in a system with a mix of mitred and radius [elbows], this will convert all to one type."

 

They're going to update their online help guide to say this method only works for In Line Equipment.

 

Their proposed work around is: "...to use the type selector after the conversion and swap out elements." I think a combination of this work around and the 'Exclude' feature (part of the last subscription) will probably create the best work flow.

0 Likes