So now let's start developing an application rate, so we'll just go through some of the functions that
we have and then try to find for our velocity of.
So this is used to check whether Vostok timer is expired and washed off more.
Similarly, we have a function to check that the watchdog timer is expiring the timer rate, then we
have a function to restart our Vostok table, right?
So this is useful when we want to restart our account for watchdog time, right?
Then we have a load washed off timer.
So insistent point during the value that we need to specify.
OK, then we have a moved rate.
So first thing that we could do is to set the rate, so to set the world up temporarily washed up.
We just need to specify an instance structure what here again, this will by default enable Vostok time
local operating, then washed up more similarly to a user washed off camera any time remote.
We have this function, right?
So this will be our first step.
Then we'll be losing a value, OK, and then we'll be starting.
I washed off name, right?
So we also have to reload that we'll be considering next.
So we have EPA to start and stop our time, right?
So usually what we do is first, we will be setting up the mole over here.
We want to utilize the Vostok model here.
They then we specify a couple.
Now, this depends on the time for which you want to check your application over time, for which this
will be the maximum time bound that you have for your application, right?
So you will be needing a thousand value and then that value will be lower, right?
Then usually we first stop the watchdog timer and then purposefully start it right and then we'll be
writing some application launches, right?
So let it just go ahead.
And plus try to add an EPA that could be used to say OK, I of Cameroonian washed up more so we just
required to utilize Disney.
We just need to pass an instance structure, right?
So we will go ahead, and this is the first thing that we do.
So we'll be setting our watchdog timer in its war stuff.
All right.
So the instance for assists w d d, right, this is an instance of what we get right now.
Let's assume you want the delay of five second rate, so delay of five.
Second, you need to count the value for that, right?
So we know that our watchdog timer operate at a frequency of three, three, three megawatts.
This we already know.
So to calculate the period, we just need to take the reverse off, right?
So it will be simply one divide by one divide by three 368.
This will be the duration for our single operate.
Now we want if we want the delay of one second, we just need to multiply with the count so that this
entire equation we're really going to want.
So we just need to add three three, three e six now when we do this.
So what will happen is one divide by three three three six and if we multiply, so design, this will
cancel out and we'll be getting a delay of one second, right?
So to get the delay of five second, what we need to do is we just need to multiplied by five, right?
And.
This will give us a delay of five second, right, so we'll just be declaring one very few 32.
And this will be for a daily call rate.
So to get the relief quite sick and we just need to multiply three three, three six by three.
And when we multiply this, the single up will simply be getting a legal fight second, right?
This is speaking.
Let's send it right.
So the frequency at which I washed off camera operators deleted three megapixel inverse of it will be
giving us a period and then we just need to multiply by account to get the respective time that use
of one.
Right?
This makes sense.
So let it just go ahead and try to specify three three three eight.
Then again, three three three three three three.
So this is basically three three three megahertz into flight.
This will give us a delay of five second.
Now remember here the clock is six six.
Seven Mega Hot, Right?
And if you just stick the reverse of it, OK, if we just divide by two, we'll be getting 350 megahertz.
That is the frequency of operation of all washed up and to get the delay of five.
Second, we just need to specify the count value to be this right now will go ahead and we will be looking
for an API that allow us to lower the rate.
So we have this will just be copying.
This will be adding it over here.
So first, be required to specify the instant structure and then the value.
So the value for our counter is.
Right.
So once we do this now, if you just look for any API, so we have a reset and then we a counter and
timer expired this we do not require right, then we will proceed with stopping purposefully stopping
our watch dog name, right?
So let it just go ahead and stop our timer and then we will be starting.
Normal operations, right?
So these are the series of steps that you'll be doing, right, so we said the more we said the crowd,
we lowered the count.
We perpetually stop our camera and then we are starting a new fresh start for us.
Right now, we know that if within the five second, if we do not refresh, I buy stock time or if we
do not restart our watch, then in that case it will apply a risk for our system, right?
So we'll just be adding the logic where we've sort of lost off timer within the maximum limit that we
have specified.
So here limit is five second.
So we'll just be adding one.
Let me just add a temporary variable temp, OK, and we'll just be counting.
Dale Ho, okay, so this is purely random count.
Just for a demonstration purpose.
So here we declare one variable rate, so while temp is less than 100, no, this hundred is purely
a random count.
We are just incrementing at them and then we are waiting for the two second rate.
No, this is within the maximum limit for our watchdog timer, which is five second, OK, and then
we'll just be restarting the worst of them.
All right.
We'll also be bringing the value of them looking so damp and then we are printing it in a decimal format,
right?
And then we are calling a restart washed off time.
So we do have an API to restart our rolling stock, namely.
OK, so this is that so we have restarted watchdog timer and we just need to specify an instance structure,
which is now.
This will continuously right, even though you'll be finding them count will implement in an interval
of second.
But since we are calling a restart.
OK, so what?
It will never allow our watchdog timer to reach the delay of five seconds again and will be continuously.
Seeing the temporal lobe in increment, the rate, so this is what we're going to analyze and then we'll
just be disabling this restart watchdog timer and then you could possibly guess that within.
The time when our value reaches two three will be applying a.
This makes sense because for the first time, value will be consuming two second, then for next we
will be continuing to move second.
And then in the third iteration will give them value.
Valuations to three will all already be causing the delay of five seconds.
So this will automatically reset the watchdog timer and this will automatically reset our system, right?
This is what we want to analyze.
So let it just go and see.
Our application will be clearing up our pencil and then performing relaunch off our debug session.
So now if you also so after an interval of two, second, we have them one, then 10, two and three
Game four -- by Game six.
Now here you would see you already consume 12 chicken, 14 seconds 16.
But since we are calling that was the timer, you would be able to see the system in resetting, right?
And this we will be continuously going till Hydra and then we will be coming out.
And since we do not call reset was famous.
So as soon as we come out of this loop automatically within the five second, it will restart our process.
Right.
So you purposefully do this now here you will see since we are calling the restart.
So this is not restarting our application, that is our application, which is incrementing the temp
value by two and then waiting for to block it.
OK, this is just working fine within the maximum specified time.
That is five second rate.
So if we just forget to call this restart node, what this will do is within an interval of use, it
will again be incrementing and printing the value.
But since we are not calling a restart, so within the five second.
This will automatically restart our system.
So let it just change this delay to one second to be able to see few more strings from our team.
So let me just go over and try to perform a relaunch simulation.
We'll just be clearing up our previous output.
OK, so you could see Templin came to demo in full and then we visited a system so you won't be able
to find anything after this, right?
To be able to successfully these same system after and delay of quite sick.