Question-and-Answer Resource for the Building Energy Modeling Community
 | 1 | initial version |
Currently, a Meter:Custom cannot reference other Meter:Custom objects. We recently addressed an issue in EnergyPlus (see 5118 and 5942) that no longer outputs zero when nested Meter:Custom objects are used and instead issues a warning message and does not produce any output. In addition, the input output reference was updated to make it more explicit that a Meter:Custom cannot reference another Meter:Custom object.
I agree with @mdahlhausen solution, and list all the meters in each custom meter instead.
| | 2 | No.2 Revision |
Currently, a Meter:Custom cannot reference other Meter:Custom objects. We recently addressed an issue in EnergyPlus (see 5118 and 5942) that no longer outputs zero when nested Meter:Custom objects are used and instead issues a warning message and does not produce any output. In addition, the input output reference was updated to make it more explicit that a Meter:Custom cannot reference another Meter:Custom object.object. This fix will be part of the spring 2017 release of EnergyPlus.
I agree with @mdahlhausen solution, and list all the meters in each custom meter instead.
| | 3 | No.3 Revision |
Currently, a Meter:Custom Meter:Custom cannot reference other Meter:Custom Meter:Custom objects. We recently addressed an issue in EnergyPlus (see 5118 and 5942) that no longer outputs zero when nested Meter:Custom Meter:Custom objects are used and instead issues a warning message and does not produce any output. In addition, the input output reference was updated to make it more explicit that a Meter:Custom Meter:Custom cannot reference another Meter:Custom Meter:Custom object. This fix will be part of the spring 2017 release of EnergyPlus.
I agree with @mdahlhausen solution, and list all the meters in each custom meter instead.
