Welcome to the AUGI Revit MEP forums!
Within these forums you will find a vibrant, community of Revit MEP users who will be more than willing to help you with your hair-pulling, absolutely aggravating Revit problem! Feel free to post whatever questions you may be having, regardless of how simple it may be, however please post in accordance with the following guidelines:
1. Like all AUGI forums, please post in accordance with the AUGI Forum Rules & Guidelines
2. Play Nice! We all know that Reviting can put you in a bad mood from time to time (to say the least), but remember that everyone on the forums are here to help! Be considerate in your posts and everyone will be more likely to help you with your problem.
3. Use the Appropriate Forum - Please use the appropriate forum under the "Revit MEP Support" category.
4. Don't post or ask about confidential information, specifically information held under an NDA (non-disclosure agreement)! As a general rule of thumb, if you cannot find information on a new Autodesk product through a simple Google search, you probably aren't supposed to know it yet.
5. Read the FAQ - Please read the FAQ under this post and check if your question has already been answered. I will try to keep it as updated as possible as I see more common questions.
If you have any additional questions or concerns, please feel free to PM me!
Informative Links:
Inside the System - The blog of Kyle Berhardt, Revit MEP Project Manager. Contains many informative videos and articles on different functions of Revit MEP.
Revit MEP Resource Center - Autodesk's official resource center with tutorials and guides.
Revit MEP Download Page - Where you can find content extensions, web updates and product downloads.
Key Terms and Acronyms:
BIM: Building Information Modeling (Link)
Element: An element is a single piece of the Revit Model, such as a single light fixture, receptacle, duct fitting, or pipe. Sometimes referred to as an instance.
Family: A family is a mid-level organizational element which is the closest relative to a block in AutocCAD. Usually a family is a separate file from your project, and usually represents different types of geometry. Families are usually made up of many different types.
Model: In Revit, the model is that which you are actually building. It represents both the 3D geometry, and the parameterized of information behind it.
Parameter: A parameter is the basic building block of all things Revit. In parameters you keep dimensions, loads, calculations and designations for all of your model. Parameters come in 4 different varieties; System, Project, Shared and Family.
System: A system in Revit is that which represents a logical link between different elements. Systems include electrical circuits, an HVAC supply line or a chilled water supply for an air handling unit.
Type: A type in Revit represents a different set of parameters under a family. Different types are generally used when you have a large number of elements with similar properties which you want to define within its own group. A good example of this are lighting fixtures, information for a type "A" lighting fixture will always be the same for all of its type.
View: A view is that which pulls information from a model to create perspectives, analysis and presentation of a model. Views include floor plans, ceiling plans, elevations, part plans and even schedules.
Common Errors:
Line Too Short: This error occurs when you essentially try to squish something into nothingness. For a good example on why you get this error, go into Revit and make an "H" with three detail lines, drawing the center "connecting line" last. Revit will automatically constrain that center line to the outer two, so if you move one of the outer vertical lines, the center line will extend or shorten itself accordingly. Now take the right vertical line and drag it right on top of the left vertical line. When you do this you will get the "line too short" error because that center line has nowhere to go and you are essentially making it disappear, hence the delete option. You will generally hit this error a lot when dealing with constraints. If you get it after changing the dimension parameters of a family in a project, check to make sure you didn't accidentally constrain something which would cause this problem.
Flow Direction Mismatch: Oh boy, my favorite error! You get this when dealing with either piping and/or HVAC duct systems and are trying to correctly connect two mechanical or plumbing elements. The cause of this error is because a connector on one side of the system does not coordinate with a connector on the other end. Within your HVAC or plumbing connector, there is a nice little parameter called "Flow Direction" which can be set to either "out" or "in." This parameter must be coordinated with all the connectors in the system or you will get this error. Flow usually goes from out -> in in general scope of a system. If you have two pieces of equipment with "out" and no equipment with "in," it will error. Though it seems easy, it is pretty easy to get confused with this. The one thing to remember is that the flow direction is in relation to the connector from the system. A perfect example of where this can be confusing is with an exhaust air terminal. An exhaust terminal will exhaust air out of the family making you think that it should be set to "out," however the connector is receiving air from the system and therefore should be set to "in." It takes a while for this to become second nature, but even then on complex systems it can get a little frustrating. The best way to avoid it is to make simple sample systems when you first create your families to make sure everything is set correctly. It is a lot easier to do it then way then when you have 30 things connected to it.
Duplicate Mark Values: Every time you place an element into the model, that element is assigned an incremental "mark" value under a parameter of the same name. When you have a worksharing enabled model with two or more people working in it, elements are placed by each user with similar mark values because each user is unaware of the other users actions. There is really no way to avoid this, and the only way to make the error go away is to manually rename every element, which is unrealistic.