You lose, fella. The EMTP logic has detected an error condition, and is now going to terminate program execution. The following! t! G. X' Z" I, V' b
message summarizes the circumstances leading to this situation. Where an otherwise-unidentified data card is referred to, or where6 }& O8 u, v6 t) O( ~
the "last" card is mentioned, it is the most recently read card of the input data that is meant. The 80-column image of this card3 Z i0 c6 ]' \; ~- |
is generally the last one printed out prior to this termination message. But possibly this last-read card has not yet been * [7 K* F. U' |2 @2 K+ D/ j0 v" u1 Pdisplayed, so a copy follows: " M; A% o$ N) f1 N/ c$ o "14X0184A 0 2.2E5 50. -1. 1." # V/ ~9 e \1 Q( N! |) c KILL code number Overlay number Nearby statement number+ x s' m+ T+ Z h- X6 _ N! a
12 5 4246 + |0 H" [& S9 A4 `1 |0 H1 E0 p* v! KKILL = 12. The bus name that was read from columns 3-8 of the last source card is unrecognizable, not having been previously - r2 n e; x% k+ [$ hdefined by a branch card or a switch card. The name read from the data card is "X0184A". The user is not allowed to connect ( Z9 J9 r4 X8 q0 N2 qsources to network nodes that are not a part of the network that was previously defined by branch and switch cards of this data ! @% A t& p8 Z! x% K7 b1 ~case. Any such new node would be completely disconnected from the network, so could not affect the solution. Most probably, one or) b! d2 ?( |# U' \
more spelling errors (including the positioning of imbedded blanks) have been made in the keying of one or more node names on EMTP data cards.