So we'll allow transmissions between the use grid and the use battery states by connecting them. After we've collected some solar energy in the battery, we should then consider switching to the use battery state. So the default transmission will go into the use grid state. We'll start out by drawing power from the grid. We also need to tell Stateflow which state to enter at the start of our simulation by adding a default transition. We'll represent these two operation modes using two states called use grid and use battery. The energy system within our building can switch between using the grid and the battery for power. And inside we can use all the signals we just connected. Now we're ready to build our decision logic. Last, we'll rename this chart block to Building Manager. It's starting to get a little crowded, so we'll resize the chart block. And the port names will be set to the signal names.Īs we drag the other two signals onto the chart, two more ports will be added. Since our signals have names already, we can drag them onto the chart block. Now let's connect our signals to the chart so we can use them inside. We'll start by dragging a chart block from the Stateflow library into our model. How can we do that? We can do this by adding a Stateflow chart to represent our decision logic. But we need to make decisions about when to use the battery and when to use the grid. OK, so that covers everything that was already built. But for decision logic like this, it will usually be discrete time. You can use Stateflow with continuous systems. Last, we've set the solver to a fixed step solver to match the sampling rate of our solar data. So we have a plan model for the battery, and we monitor the stored energy with a scope. We'll make decisions based on the battery level. We'll use this data to determine if it's sunny with our weather detector. So that's how long our simulation will be. The model's input data is the power in watts coming from the solar panels sampled every 15 minutes. The hardware is already modeled in Simulink, so we can just load the model and add to it. We're going to model our finite state machine with a state flow chart. Only one operating mode will be active at any time. If the battery gets drained, we'll fall back to using the grid.
We'll either be using the grid or the battery if it has enough charge. We can represent this as two separate states using a finite state machine. The battery will save us the most money if we can use it to avoid the highest prices.īased on what time it is, we want to be in one of the two operating modes. Electricity is priced differently throughout the day. We need to represent all these operating modes and make decisions about when to transition between them.įortunately, we have Stateflow, which can do all of this and more. Now we need to decide when to use the grid and when to use the battery so we can reduce the electricity bill. This acts as a buffer to power the building when it's not sunny. Let's assume our building uses 200 kilowatts and the panels will charge a 3 megawatt hour battery.
This makes it difficult to find the best way to use the energy collected. The energy produced by these solar panels varies throughout each day. Pairing the solar panels with a battery lets us collect solar energy and then use it when we want. In fact, they provide about 8% of the MathWorks energy needs. These solar panels can help to reduce our electricity costs and dependence on fossil fuels. MathWorks has roof mounted solar panels at our headquarters in Natick, Massachusetts. At the end, we'll show you where to go next to learn more about Stateflow and start using it today.
#MATLAB SIMULINK PRICE HOW TO#
This video will show you the basics of Stateflow and give you an idea of how to use it to model decision logic. Stateflow is a graphical environment that allows you to design and simulate decision logic for supervisor control, task scheduling, and fault management applications.
0 kommentar(er)
