Sunteți pe pagina 1din 5

LITERATURE SURVEY Why Co-simulation:

For real-time assessment, validation and verification of the Smart Grid, simulation of the interdependent power and communication networks is necessary. The challenge in co-simulation is to develop an accurate synchronization of the simulator worlds, one operating by discrete event mechanism and the other by continuous time. One of the early projects on combined simulation systems is the EPOCHS (Electric Power and Communication Synchronizing Simulator) which employs a Runtime Infrastructure (RTI) to synchronize the simulation clocks of its components. This is also known as federation. Opposed to this approach is the ADEVS which requires that requires a new modeling of the power system rather than making use of the already available power simulators. An example is the use of OMNeT++. Most of the problems defined for co-simulation in the papers on Smart Grid integrate renewable energy sources. They are the call of the future and tackling their intermittent is itself one of the major challenges of the Smart Grid Project. Also, electric plug-in vehicles seem to be an important aspect of the Smart Grid and thus provisions must be made for their changing energy demands.

Co-Simulation Frameworks:
Most basic approach is the intuitive one on the lines of the one used in EPOCHS, where it is referred to as a time-stepped model. Why an intuitive synchronization fails can be reasoned thus :When we have equally spaced Synchronization points (points at which data exchanges occurs via a mediator software), an error that occurs between two synchronization points in either the communication or the power network goes undetected till the next point. Thus, selection of a time step size is a trade-off between the simulation speed and error minimization. In the NS2/ PSLF co-simulation, the framework encompasses a Global Scheduler (taken to be NS2s in-built network simulator) which prepares an event list of the normal communications events and the discretized power system rounds. As per their timestamp orders, the power system dynamic simulation round or communication network event is processed. Any requirement of interaction between the two simulators is taken care of by the global scheduler. My inference is that a predefined event list does not echo the non deterministic nature of the communications networks.

Another technique that has been explored in the NS2/Modelica Co-simulation is enslaving one simulator to another. Which will serve as the primary simulator is answered by the nature of the processes they handle. Power grid simulator is characterized by a continuum of discretized small time steps whereas events in the communication network are rather random and we can use this to determine our implicit synchronization points. This has been explained in detail later in this report.

Co-Simulation Options Features:


NS2/Open DSS:
OpenDss is an open source dedicated simulator for utility distribution systems provided by the Electric Power Research Institute. It can be driven entirely from a MS Office tool through VBA, for example, or from any other 3rd party analysis program (e.g., Matlab Interface) that can handle COM. One way to think of the DSS is as an object-oriented database of power system circuit data that can perform various common distribution system analysis tasks. Platform: Windows Programming Language: Delphi/Kylix, Free Pascal User Interface: Command, Console/Terminal, Win32 (MS Windows) Modeling Platform:

SourceForge.NetLinks for OpenDSS OpenDSS Download Files: http://sourceforge.net/projects/electricdss/files/ Source Code http://electricdss.svn.sourceforge.net/viewvc/electricdss/Source/

Ns2/Modelica:
Open Modelica is open source. It resembles object oriented programming. It consists of a library SPOT for steady state and transient state analysis of power systems. In the federation, Ns2 and modelica run as two separate processes: challenge lies in synchronizing their clocks. Implementing real time synchronization is rather wasteful in nature. Thus, the internal events of Modelica are neglected i.e. Modelica is enslaved inside ns2 Communication networks happen to be more nondeterministic and unpredictable as opposed to Power grids The time instants that modelica has to deliver data to ns-2 can be coded for in ns2. Ns-2 to modelica communication on the other hand is affected by random delays Communication between the two simulators is mediated via a LINUX named pipe. Simulation begins at the same time for both the simulators. However modelica pauses initially, NS 2 runs till it encounters an event that requires data from modelica or requires sending data to modelica.Then NS2 pauses. Now depending on the event, Modelica acts: Incase data must be delivered from NS2 to modelica, it is written onto the named pipe by NS2 and modelica must read this in this period. Incase data is required from Modelica, at this instant it writes this to the named pipe so that NS2 can retrieve it later. Thus clearly NS-2 determines the time and type of communication with Modelica must take place. Documentation Support for Modelica: https://www.modelica.org/documents

NS2/PSLF:

PSLF is not open-source. It is distributed by GE Power. Positive Sequence Load Flow software (PSLF) is designed to provide comprehensive and accurate load flow, dynamic simulation and short circuit analysis. It is one of the commercial off-the-shelf simulators used in the EPOCHS approach. Programming language: Java, EPCL User Interface: Command Line Console Platform: Windows

Integrated Simulation of both the communication and power networks on one


simulator eliminates the need for synchronization, but at the same time, power system models are not predefined and must be developed by us.

OMNeT++: Programming language: C++ Platform: Windows/LINUX For Communication systems, OMNeT++ offers models like INET.The INET Framework
contains models for several wired and wireless networking protocols, including UDP, TCP, SCTP, IP, IPv6, Ethernet, PPP, 802.11, MPLS, OSPF, and many others.

A layered architecture is employed for the Smart Grid simulation environment design: APPLICATION MIDDLEWARE SUPPORT electrical network

Every smart grid component or Node must have two interfaces:

Electrical interface-------------NODE----------communication interface (INET model/s) (Essentially a MATLAB module linked to OMNeT++) Power Network Features: Radial networks are supported Fast Harmonic Simulation method o Backward sweep determines currents with known voltages and forward sweep determines voltages. In case the discrepancy in voltage exceeds a minimum, simulation is suspended.

Documentation Support for OMNeT++: http://www.omnetpp.org/documentation

Scope of Network Simulator 3:


NS3 scores over NS2 in that it is more flexible and user friendly. Also, since it is currently under development, it is an ideal research platform.Currently Ns3 does not have a power network model.On the lines of OMNeT++, an interfacing of a MATLAB or Simulink model could be an option. SimPowerSystems in Simulink Power System Analysis Toolbox (PSAT) in MATLAB Alternatively, Scilab (open source) provides API enabling and could be explored.

S-ar putea să vă placă și