Model Electrical

[Odon Irving]

TheEnergy Code Board is resuming meetings to develop the Model Low Energy and Carbon Code, pursuant to House Bill 22-1362. Updated information about meetings, meeting materials, and public comments can be found in the accordion dropdown sections below. A description of the model low energy and carbon code can be found in the Building Energy Codes Legislation section below.

The Energy Code Board is soliciting comments from the public to inform its development of the model low energy and carbon code. The Board is seeking diverse perspectives from Coloradans across the state about their top priorities for future buildings in their communities. The Board is also soliciting any proposals for technical language to include in the low energy and carbon code.

The final Model Electric Ready and Solar Ready Code package was published on June 1, 2023. The package includes the final code language, an explanatory version with annotated notes for various sections of the code, and a final code report that outlines the statutory requirements for the code and an overview of the process and discussions of the Energy Code Board.

The Energy Code Board (ECB) created in the Building Energy Codes law was selected and seated by October 1, 2022. The Energy Code Board and its executive committee were jointly selected by the Directors of CEO and DOLA. The Board consists of 21 members representing specific interest groups and are listed by their appointments as follows:

Additionally, HB22-1362 required the appointment of a 5-member Executive Committee, which includes the Directors of CEO and DOLA, as well as the Board's building code expert and one representative each from the county representatives and municipal representatives. The Executive Committee members that have been appointed are:

The full Energy Code Board met 15 times between October 2022 and March 2023 to develop the model electric ready and solar ready code. Additionally, the Executive Committee of the Energy Code Board met three times in April and May 2023 to consider and vote on remaining elements of the model electric ready and solar ready code that failed to reach 2/3rds support from the full Energy Code Board. To comply with Open Meetings laws, the Energy Code Board recorded and livestreamed all meetings and deliberations. All Energy Code Board and Executive Committee meeting materials are publicly available through the link below. The recording of each meeting is available on CEO's Youtube Channel.

I want to model the function of Avionics 1, Avionics 2 and the Standby bus, as well as the main bus (driven by all batts and generators). I had the idea of setting the number of buses to 4 in plane maker, and then assign each instrument to their respective bus. For example:

What I don't know that well is the X-plane part of things. I was more wondering if it is at all possible, and if so what datarefs I should read from and write to in order to simulate the system correctly.

The functionality I want boils down to "selective cross-tie". Right now there is a dataref that controls a very agressive cross-tie, which simply ties ALL buses together. So bus 1, 2, 3, 4, 5 are either all connected, or all seperate. I am looking for the ability to selectively tie different buses. For example I may have batt 1 and 2 on bus 1 and 2, gen 1 and 2 on bus 1 and 2, and then have three groups of avionics on bus 3 4 5. Then as I turn on the standby power switch, this will tie bus 1 to bus 3. It's seems like the current X-plane way of doing things only really models smaller aircraft like the 172.

Exception: For combustion equipment dedicated to space or water heating, the electrical receptacle or junction box shall be located not more than 6 feet from the combustion equipment or the dedicated physical space for future electric equipment.

Low sloped roofs (2% slope or less) or a roof with not less than 600 square feet of roof area oriented between 110 degrees and 270 degrees of true north shall have an identified solar-ready zone and the construction document shall indicate the solar-ready zone.

Townhouse exception: The solar-ready zone for townhouses three stories or less in height above grade plane and with a total floor area less than or equal to 2,000 square feet of conditioned space per townhouse unit shall have a solar-ready zone area of not less than 150 square feet.

Construction documents shall designate the EV ready space and indicate the locations of raceway and/or conduit and the termination points serving them. The circuits or spaces reserved in the electrical panel for EV ready spaces shall be clearly identified in the panel or subpanel directory.

Do you fancy a workaround? Create a model in-place and choose Conduit Fittings category, or basically any category that is not half-toned under Electrical Discipline, then you can draw model lines freely and when you are done, they will show as full toned.

Underlay elements? The model lines are the focus of the view. Why are model lines exclusive to Arch & Struc? That does not solve the fact that model lines grayed out in MEP views. How am I supposed to draw my grounding wires, lighting zone lines, & Fire alarm zone areas? Don't even think to tell me to use Annotation lines, they only show up on the view they are drawn on.

Contains a matrix of frequency based data. These models are extremely versatile and can be used in time-domain transforms to generate impedance, crosstalk, propagation delay and eye-patterns, or they can be used in frequency-domain simulations for throughput and crosstalk. All files are provided in Touchstone format, which is compatible with many simulation software packages.

A SPICE compatible representation of several lines of the connector, and includes the contact components, contact to contact couplings, and where applicable, includes contact to shield couplings, and inter-pad couplings. This results in a detailed model that can be used for simulating crosstalk and ground bounce in addition to the parameters analyzed with the Single Line Model (SLM).

Represents the effects of one line of a connector wired appropriately for high speed signal transmission (typically near-by contacts grounded). The model includes the lumped elements representing the series resistance, "effective" inductance and the total capacitance for one line. It also includes the impedance (Z0 ) and propagation delay (tpd ) for the transmission line equivalent. This simplified model can be used for simulating reflections, time delays and skew, attenuation and signal transmission quality.

Although we currently do not natively support IBIS models. Our models have been successfully converted into IBIS models or used in IBIS based tools. For help with IBIS models, visit he ANSI/EIA-656-A homepage.

I am aware that the Electrical Model is Partitioned, but I am trying to replicate somehow the Circuits within the Distribution Tier the same as they were modelled in a previous GN Model of a client, where for example a Service Point could have two Feeders (CB), belonging this way to two different circuits. So, when trying to replicate same behavour into the UN, this obviously creates only one Subnetwork feeded by two Subnetwork Controllers (CB). Then, I try to Modify Controller and change the Subnetwork Name to see if the field Subnetwork Name of the Assets downstream changes to both of them (This way behavour would be kind of replicated) and when I Update Subnetworks it works just fine. Here you see the field Subnetwork Name of an Asset downstream of the CB with different Subnetwork Names, both from the Distribution Tier:

Until now, everything works as expected, I even inserted an extra Directional Switch under the CB in order to prevent the flow from one CB reaching the other one. So, now when I try to check the Subnetwork Controllers feeding this Asset using the Trace tool, the error 001890: Invalid subnetwork connectivity, multiple subnetwork controllers with different subnetwork names found is populated.

My question then is:

If the tool Update Subnetwork worked just fine and populated the right attributes in the right fields , giving the two subnetwork Names to the Asset (Circuit1::Circuit2) but also, it correctly created the two features into the ElectricSubnetLine with its geometry. Why the Subnetwork Controllers or Subnetwork Trace Tool doesn't do it as well? I understand that, if this is not possible in the UN because in reallity is like that, the Update Subnetwork shouldn't work as well, should it?

Thanks for your help

Assuming this is not a mesh network, but two separate circuits, then normally you would have an switch that connects to both circuits just before the service. It is typically called a Source Selectable Switch or Automatic Throw Over Switch. This switch would have three terminals (two upstream). Then the terminal path on the switch would set to only provide a path to one source or circuit at a time. Then the service is only part of one subnetwork at any time.

It sounds like this is a case where you have multiple wires you want to represent as a single line, which is going to be an issue in the Utility Network, as the UN is designed to model physical assets. So, to accomplish this you could create a container feature, like an aerial span, where it contains the two lines from the two different circuits. The other option is to make all your lines containers and make all wires non-spatial content, but I would not suggest that, as it would be a bit more complex to edit.

3a8082e126