2

EnergyPro 6.5 Performance Compliance

Hello All; Has any one attempted or had success using EnergyPro 6.5 to demonstrate Performance Path Compliance with California Title 24? Would be curious to hear from those who have done this, and learn basics of the project [Retail, Packaged Dx/Gas, etc].

dradair's avatar
2.5k
dradair
asked 2015-05-05 14:54:59 -0500
__AmirRoth__'s avatar
4.4k
__AmirRoth__
updated 2015-07-10 20:28:57 -0500
edit flag offensive 0 remove flag close merge delete

Comments

1

In searching for additional information, I came across the meeting notes from the latest IBPSA-San Francisco Chapter meeting. This appears to have been a discussion on approaches to the Title 24 requirements. Interesting read:

https://ibpsasf.files.wordpress.com/2...

dradair's avatar dradair (2015-05-06 16:29:16 -0500) edit
add a comment see more comments

1 Answer

2

Personally, I've chosen to steer away from EnergyPro v6.5. CBECC-Com as it stands is a rather buggy tool and not all that user friendly with it's error logging, but it is getting better. EnergyPro's implementation of the CBECC-Com API is also rather buggy adding another layer of complexity for the user to try and debug. While CBECC-Com error messages appear in the log file (available with any third party CBECC-Com vendor) the errors encountered that are internal to the EnergyPro implementation of the CBECC-com engine are not accessible making debugging a real nightmare at times. Moreover, there is a time lag between when newer versions of CBECC-Com are released with added functionality/bug fixes and when third party vendors are able to release a stable version with the updated engine so it is limited in this sense too.

My suggestion is to become comfortable with manipulating the SDDXML file that CBECC-Com uses as an input. That said, you're still limited to the available HVAC systems in CBECC-Com and I imagine exceptional compliance will be a necessary pathway fairly frequently - it is for me.

pflaumingo's avatar
1.9k
pflaumingo
answered 2015-05-11 22:59:48 -0500
edit flag offensive 0 remove flag delete link

Comments

add a comment see more comments