Canadian Association of Consulting Energy Advisors (CACEA)

  • Home
  • ERROR: A window type has been defined but the R-Value or SHGC is out of range

ERROR: A window type has been defined but the R-Value or SHGC is out of range

  • 21 Oct 2024 2:47 PM
    Message # 13421573

    Losing my mind!

    I'm working in V11 on this file but I've had this happen more recently in V13 where a previously working file is now throwing this error. 

    "A window type has been defined but the R-Value or SHGC is out of range". 


    I have shortened the name but it still is not working. How does everyone else deal with this?


    Code breakdown attached as well. Thanks!


    2 files
  • 5 Nov 2024 12:41 AM
    Reply # 13427245 on 13421573
    Anonymous

    Hi Chelsah

    Workaround guide 1.1.13 might help though it looks pretty clunky

    First save a copy of the file, and use it

    to verify the issue by deleting windows

    from the smallest dimension to the

    largest, running the calculations after

    each deletion until the error goes

    away (note, the error is repetitive but

    pressing and holding the enter key will

    get past them quickly).

    Once the problematic windows are

    identified the issue can be resolved in

    one of two ways.

    1. If a precise window area is not

    critical (e.g. window to wall ratio is not

    close to a limit for code compliance

    files) iteratively increase the window

    dimensions by small increments and

    run the calculations each time until the

    error goes away.

    2. Where window area is critical,

    determine the area of the problematic

    window and combine it with another

    window of similar characteristics,

    including orientation, to get the same

    total area. As lintels and effective wall

    R-values are dependent on window

    width, adjust only the window height

    when possible. Delete the problematic

    window.

  • 6 Nov 2024 10:05 AM
    Reply # 13427740 on 13421573

    Thank you! I'll give it a go!

  • 17 Dec 2024 3:04 PM
    Reply # 13441881 on 13421573

    I just ran into this issue, and after a lot of experimenting, it seems H2K is acting funny with the Code Labels in the code editor.  Try renaming the code label to something more generic and then try reloading it in H2K.  Seems to be some odd combination of characters/numbers that triggers it for me with no real pattern.  Super frustrating!

  • 18 Dec 2024 7:45 AM
    Reply # 13442113 on 13421573

    I’ve had success getting rid of this by just changing the glazing type. Try entering it as 3 glazed 1 coat, there appear to be specific acceptable ranges for each selection under that menu that throw these errors. Do your code names always have slashes in them? Maybe that’s to blame but if that’s your standard and it hasn’t caused other issues then probably not. 

  • 18 Dec 2024 9:28 AM
    Reply # 13442151 on 13421573

    The fix is to shorten the custom name.  Max 22 characters but NRCan recommends 15.

    (This is a known issue and is documented in the workaround document.)

© 2020 CACEA - Canadian Association of Consulting Energy Advisors. All Rights Reserved.
Powered by Wild Apricot Membership Software