![]() |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Overview EMTP-RV is the end result of the "EMTP Restructuring project" undertaken by the DCG in 1998 for modernizing the EMTP96 software. EMTP-RV is the enhanced computational engine and EMTPWorks its new graphical user interface (GUI). The package is a sophisticated computer program for the simulation of electromagnetic, electromechanical and control systems transients in multiphase electric power systems. It features a wide variety of modeling capabilities encompassing electromagnetic and electromechanical oscillations ranging in duration from microseconds to seconds. Examples of its use include switching and lightning surge analysis, insulation coordination, shaft torsional oscillations, ferroresonance and power electronics applications in power systems.
EMTP-RV computational engine is driven by EMTPWorks. The bulk data transmission from EMTPWorks to EMTP-RV is performed using a Netlist file. EMTP-RV reads the Netlist file, decodes the simulated network topology, finds all required device models and computation functions, builds the system matrix and performs the simulation. The simulation results are saved into binary and ASCII files. The main binary file is used for showing simulation waveforms from a stand-alone waveform visualization application named ScopeView. Some of such output files are HTML files and can be viewed only through the Internet Explorer Program. EMTPWorks can also start a data translator function which is designed to convert old EMTP96 (previous version of EMTP) data files into a translated file format which can be decoded and simulated by EMTP-RV. The Data Translator is used only as a temporary transition option and has a limited compatibility with old data cases. There is no direct mapping between the old EMTP-V3 models and the new EMTP-RV models and there is no schematic generated by the translator. Simulation options EMTP-RV accepts several simulation options which are performed for arbitrary network configurations. All options are applicable to all devices within documented rules of device behavior. These are:
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||