Platform MEP2012 update 2.
We're experiencing an issue when circuiting VAV boxes that are part of a mechanical system. When adding more than one VAV to a circuit all the VAVs on the mechanical system are added to the circuit. The same family when not on a system allows circuiting more than one to a circuit. Anyone experience this. Want to avoid work around of placing j-box for each VAV.
Solved! Go to Solution.
I haven't tried to recreate the situation, but can you edit the circuit and remove one of the VAV boxes from it?
When using remove from circuit it works but when the next circuit is created it grabs the previously circuited objects on the system.
So, as a momentary work-around method, can you create a new circuit from a "dummy" device, edit the circuit and add one of the VAV boxes, and then delete the dummy device?
We ended having to put a connector element family on the VAV and duplicate the type mark. Any mech object that is on a system will not circuit individually. I even happens with pluumbing systems. Tried to circuit a water heater and it grabbed all the plubming fixtures on the system even tho they don't have elecrtical connector. This happend because the water lines were part of the system. Seems like another bug.
Thanks for answer.
This is a known issue that is logged with our Development group. Basically, the physical connection is winning, so anything physically connected to an element (via pipes, and ducts) will be added to the same circuit if one element on the system is moved to another circuit.
As I mentioned this is an issue we are actively working to fix.
One workaround we have found, is to remove unwanted VAVs from the circuit before finishing the circuit. We understand that this may not be the preferred workflow, but we are actively working to fix this issue.
We were able to reproduce this in 2012, but unable to using the same steps in 2013 with Update 1. This video shows 2012 on the left, and 2013 on the right: http://screencast.com/t/KVYMqJtK6el If you are still seeing this issue in 2013, please provide more information so we can identify the problem. Thanks,