Conduit Itc Tt Bold Download
Martial Salleh
In the pic below the wire coming out of the ground is not rated. There is no conduit and it enters the box without cable clamp. Is it necessary to have conduit run the entire way or is UF wire sufficient. This goes partly under asphalt lot.
Thanks
[FONT=TimesNewRoman][size=2]Here is the reference. . .
**[FONT=TimesNewRoman,Bold][size=2][size=2][FONT=TimesNewRoman,Bold][size=2][FONT=TimesNewRoman,Bold]
300.5 Underground Installations.
[/FONT][/size][/size][/size][/FONT]**[size=2][FONT=TimesNewRoman,Bold]
(D) Protection from Damage. **[/size][/FONT]**Direct-buried conductors and cables shall be protected from damage in accordance with (1) through (5).
****(1) Emerging from Grade. ****Direct-buried conductors and enclosures emerging from grade shall be protected by enclosures or raceways extending from the minimum cover distance required by 300.5(A) below grade to a point at least 2.5 m (8 ft) above finished grade. In no case shall the [FONT=TimesNewRoman][size=2]protection be required to exceed 450 mm (18 in.) below finished grade.[/size][/FONT]
[/FONT][/size][/FONT]
When as a generalist do we call out wiring that is not in some type conduit?
I see Romex non metallic wire ran from sub panels in garages for example that is attached to the framing and ran along to plugs, switches etc. often more than not. If permits were pulled is this not a code issue?
The only thing is it needs to be protected from physical damage. If run on the surface of studs that would generally need protection. If on the side of studs then this is common and not usually a problem.
As mentioned non-metallic cable in residential installation does not need further protection or conduit as per code. (I use canadian code and am an electrician by trade - but NEC does not vary much in most areas)
There may be some conditions where protection is required - as mentioned where physical damage is possible (exposed and prone to damage) or when buried as examples. However, there are even solutions here which do not necessarily require conduit.
If you did require conduit, you would not normally pull NM cable into it. Adds costs, adds conduit fill, makes using code for conduit fill calculations incorrect, etc. I can not recall anywhere it says to not pull into conduit, but can not imagine why anybody would.
**[FONT=Times-Bold]ARTICLE 334 Nonmetallic-Sheathed Cable: Types NM, NMC, and NMS
**
334.15 Exposed Work. **[/FONT][/size][/FONT][FONT=Times-Roman][size=2]In exposed work, except as provided in 300.11(A), cable shall be installed as specified in 334.15(A) through .[/size][/FONT]
Mercury Display is a modern serif typeface based on classic serif typefaces like Times, but paired with contemporary details. The oblique serifs, or edges, are unique and eye-catching, giving the new style distinction. Contemporary yet classic, this typeface was designed for headlines and subheadings and should only be used for these as the details are lost at smaller scales.
Mercury Text is a modern serif typeface based on geometric proportions, making it a nice contrast to the headline typefaces. It has sharp corners and tightly coiled curves and is flexible, complete with a full range of weights and italics, making it an ideal choice for body copy and longer documents that may need subtleties in hierarchy.
Pill Gothic is industrious and assertive, with unconventional details that differentiate it from other geometric sans serifs. Though various widths are available, the condensed 300mg width is preferred. This font should be used for headlines and subheadings only.
Aktiv Grotesk is a compact, geometric sans serif designed to speak with authority and neutrality. This family offers a variety of weights and widths, making it a versatile choice for body copy requiring a well-defined hierarchy.
This headline style mixes type in a way that adds emphasis and impact to portions of the headline. The pieces set in Mercury or Capitolium 2 jump out first, while the Conduit or Pill Gothic portions sit back and support the structure. An optional outline box can be added around the secondary type to add weight and visual interest to the headline, making this headline style a more graphic and expressive variation that works well for large communication moments where high impact is desired.
Here are some examples of setting up headlines with additional copy. Style contrast will offer the most distinction between headline and subhead. The style of subhead will be dictated by the chosen headline style. If the headline is set in Mercury Display Bold or Capitolium 2 Bold, the subhead should contrast that and be set in Conduit Bold or Pill Gothic 300mg Bold.
Size contrast is also important to explore. The size of headline in relation to the subhead and body copy should have a clear hierarchy. Larger headlines set with smaller sub heads and even smaller body copy work best. Headlines should always be set in the bold weight.
Headlines are always set larger than the body copy and in the bold weight, which provides the most contrast from body copy. Subheads should be closer to the paragraph that follows than the paragraph above.
Barlow Condensed, a slightly rounded, low-contrast grotesk type family, is space efficient and clear. This font is perfect for headlines, as it shares qualities with highway signs and public signage. Any head style in Barlow Condensed should always use the semi-bold weight in all caps.
System fonts should only be used if no other identity fonts are available for print or web. An example of their use is in HTML emails, where font options are limited, or in general communications such as letters and email signatures.
Look at the screenshot from my original post- THE CONDUIT SIZE SETTING IS NOT BEING APPLIED TO THE CONDUIT SEGMENT SYSTEM FAMLIY !! That problem has nothing to do with any Conduit Fittings. I just showed the Conduit Fitting next to the Conduit Segment to highlight the issue.
If all of this is correct there may be something in the family we are not seeing, or it could just be a display error. Try PDF'ing the view and see how it looks when printed if this is even an issue worth pursuing.
Oh I followed you, and I've also been working with Revit long enough to realize some things just display odd at times, IE a display error. You have provide screen shots but that only tells part of the picture.
No one here is getting upset or being rude. I've used italic, bold, and ALL CAP text to emphasize some points, because communicating through text on a screen is difficult. You don't need to take offense at emphasis.
As for 'gone through some stuff and not told anyone' / 'provide screen shots but that only tells part of the picture', the first screenshot I posted showed (highlighted!) 2 numbers that should match, but didn't -- that cannot possibly be caused by a display error. That IS the whole picture, and I DID tell you about it (hence the current discussion). There was enough information there for @smbrennan to figure it out (without taking offense, I might add).
This is actually a rounding thing that Revit did. Conduit sizes are rounded to the nearest 1/32". The original size was entered in as 2 25/128" which is where that number is coming from. You can either modify your family to be the exact measurements of the conduit, or you can modify the EMT sizes of the conduit to the rounded values.
The discrepancy is between the rounding applied to the display of the OD value in the Properties panel vs the rounding applied to the display of the OD value in the Conduit Settings dialog (in other words, the display of the OD value in the Conduit Settings dialog is rounded to the nearest 1/32" (= 2 3/16"), even though the true value of the field is 2 25/128") ?
That sounds correct. With how Revit works if you just type in the same value it displays it does not correct it from the true value to the new value. It needs to be a big enough change (at least the rounded value) for it to take affect.
Where I work we didn't concern enough with the small variance when making objects since when they are in PDF form with line weights it is not noticeable most times. We also usually print with conduit and conduit fitting at Low Detail Level so there is only one thick line for the conduit and just tag it for sizes.
You're right that it doesn't make a difference when printed out, but as I work I am constantly doing little visual checks to make sure the model is doing what I expect. One of these is looking for solid lines that should be broken, or broken lines that should be solid. This conduit size discrepancy tripped that red flag, so I had to stop and dig.
The plug-in uses the DisplayConduit to render a HUD to the specified viewports. What has started to happen in V6 is that in the perspective view objects flicker when rotating and zooming, which severely limits the plug-ins versatility. Several of our customers use Conduit regularly as part of their workflow, and are finding that GH definitions that they had relied on for quick feedback for design or for data visualization in client meetings are no longer viable.
@stevebaer, yes the same issue. It appears that the issue above (re: clipping, flickering) we are experiencing with Display Conduit continues to persist in the most recent builds of Rhino. We have a Grasshopper plugin (Conduit) that makes use of Display Conduits. Many of them still have to rely on Rhino 5 for their work with these tools because of the issue described in this thread. We are unsure of how to proceed.
7fc3f7cf58