This model was intentionally captured with ports showing.

 

 

1) Make sure the circuit breaker has a test port and it's output function is filtered to see the bidirectional port only (Does not see power input).Note: In modeling, over voltages on power supplies must be detected by other means not by a tripped circuit breaker. This is usually done with a manual test point test of the voltage. (Same as the real system)

 

2) Do not use an inspection test to test the breaker as this will show only the Breaker or fuse is bad. Use a path based test (User initiated or Probe) so bad current will show the "Item under power" as well as showing the breaker could be bad (Ambiguitry of 2 items only. Cable should be discounted) . Also note this test point is normally non-hierarchical (Local IO flag). It's test can then be inhierited to the top.

 

3) Filter the Bidectional port output function on the Item under power with no dependency at all. This will make it appear as too much current when diagnostics marks it as bad in refinement. (With this filtering no other object that this item is connected to will be in ambiguity. A blue error on the error checker will be caused by this filtering which can be ignored.)

 

4) Use a Class attribute that is setup for Functions with Non-operational to mark left Bidirectional port on cable as Non-Operational (Conveying information of current and not a failure item).  In the opposite direction, since right cable bidirectional port has default filtering for voltage, it is a failure item when voltage to the Item under power is marked as bad in diagnostics. The cable will be in ambiguity with both the circuit breaker and item under power in this instance.