Series Ratings vs. Up-Over-Down "Let thru" Chartsharcflash wrote:
Easy Power. I'm sorry maybe i don't know how to utilize the function, but i know how to choose current limiting fuses. The problem is the software calculating the affects of those such fuses, for example at 30cycles the fuse should be clearly melted and there should be 0 current through the device. At 5 cycles the current limitation should be seen in the calculations, violations, etc.
For example i have a TRS80R fuse in an MCC line up feeding a control panel. in that control panel is 3 breakers with 6kA interupting max. My software has 7kA on that bus and therefore overdutys those three breakers by 17%. However, referencing the current limiting chart that from a Ferraz Shawmut TRS80 fuse, a 7kA SC will be lowered to roughly an RMS of 3kA. allowing it to be under duty.
The software doesn't seem to take this into account.
The problem is not with the software, it is with the application method for what is known as a “series rated” combination. Prior to the early 1980’s, using fuse charts often known as let thru charts, was common. This was known by many as the “up-over-and down” method because of how you draw lines on the current limiting chart to determine the limiting effect of the fuses. You draw a line “up” then “over” then back “down” on the chart / graph. The concept was that you could “predict” how much a fuse would limit the short circuit current.
Over time, it was determined that although these charts give a good prediction of how a current limiting fuse might limit the current by itself, it was not how it may respond when in series with a circuit breaker. The problem was when the breaker and fuse opened together - the whole circuit dynamic changed. Things like the arc impedance across the breaker contacts were not considered by the charts and this changed how the series rating behaved. There were many cases where using a series rating determined by the charts simply would not work as expected.
Underwriter’s Laboratories got involved to sort out the problem and the series rating “rules” were re-written. I was at Square D Company at the time and involved from the inside. Manufacturer’s were now required to physically test combinations of devices in series under short circuit conditions. i.e. a specific type/size of current limiting fuse upstream with a specific circuit breaker downstream. The fuses were UL “umbrella” value fuses that had let thru characteristics of that fuse’s size and class. That way if it passed with the umbrella fuses, any manufacturer’s fuses could be used.
As an example, perhaps a downstream breaker with a 22kA rating would be tested in series with a 200A RK5 fuse. They would place the two devices in series, and test the combination with a much greater fault current, let’s say 100 kA for example. If the combination of devices passed the tests, it would receive a 100kA series rating. No let thru charts permitted - just look up the series rating of the combination of devices and compare it to the calculated fault current.
So, EasyPower (and all the other software packages) do not account for current limitation because that keeps them in compliance with the standars defined by U.L. about 30 years ago as well as the requirements of NEC 240.86 which requires tested combinations.
In your case, you would need to see if there is a series rating between the fuse and downstream breakers. This would be obtained from the breaker manufacturer.
Article 240.86 of the NEC does allow the use of let thru charts “under engineering supervision in existing locations” but places all kinds or requirements such as the combination being selected by a licensed P.E., proper documentation, stamping by a P.E. etc. This language was added because there would be existing older locations where there were no tested combinations of equipment.
For older systems with no tested series ratings you would be “between a rock and a hard place” This NEC language permits a person to stick their neck out and come up with their own series rating in the absence of tested combination. I don’t know of anyone that would do this because of the liability involved - including the software companies.
Quite a lengthy explanation but I hope it helps.