The Dynamic Stability Message Log informs you of particular model behavior. There is not enough room on the one-line to present the number of messages that can be generated by a large case, so a message log provides a convenient chronology of the simulation performed as well as particular model behavior in the simulation. The message log is essential to fully document a simulation. Due to the real-time nature of the simulation and the complexity of even a few dynamic models running together, there is a need for a clear and concise chronology of events.
The message log supplies you with the necessary feedback on the condition of the models during a simulation. We encourage you to always review the message log after each simulation, as a condition may need attention so that your simulation is performed correctly. For example, if the following warning is generated: "Gas Turbine Gov1 on Max Limit," you need to determine why this generator’s governor is on a limit, then fix the issue and re-run the simulation. Review the Message Log again to see if the warning has been eliminated. Without a correction, in this example, the system will not be in steady-state before running the simulation. As soon as the simulation is run, the system model will be trying to satisfy system power balance, since this generator was unable to meet its requirement.
Messages are broken down into four basic types:
Messages also have a status. The five major status conditions reported are:
|
|