1
00:00:00,060 --> 00:00:05,790
So now let's start developing an application rate, so we'll just go through some of the functions that

2
00:00:05,790 --> 00:00:08,800
we have and then try to find for our velocity of.

3
00:00:09,140 --> 00:00:13,460
So this is used to check whether Vostok timer is expired and washed off more.

4
00:00:13,980 --> 00:00:20,970
Similarly, we have a function to check that the watchdog timer is expiring the timer rate, then we

5
00:00:20,970 --> 00:00:23,670
have a function to restart our Vostok table, right?

6
00:00:24,300 --> 00:00:31,950
So this is useful when we want to restart our account for watchdog time, right?

7
00:00:32,310 --> 00:00:34,260
Then we have a load washed off timer.

8
00:00:34,260 --> 00:00:37,080
So insistent point during the value that we need to specify.

9
00:00:37,170 --> 00:00:39,810
OK, then we have a moved rate.

10
00:00:39,810 --> 00:00:47,460
So first thing that we could do is to set the rate, so to set the world up temporarily washed up.

11
00:00:47,700 --> 00:00:55,900
We just need to specify an instance structure what here again, this will by default enable Vostok time

12
00:00:55,900 --> 00:01:01,200
local operating, then washed up more similarly to a user washed off camera any time remote.

13
00:01:01,200 --> 00:01:02,530
We have this function, right?

14
00:01:02,550 --> 00:01:04,320
So this will be our first step.

15
00:01:04,320 --> 00:01:08,430
Then we'll be losing a value, OK, and then we'll be starting.

16
00:01:08,430 --> 00:01:10,410
I washed off name, right?

17
00:01:10,410 --> 00:01:13,650
So we also have to reload that we'll be considering next.

18
00:01:14,040 --> 00:01:18,090
So we have EPA to start and stop our time, right?

19
00:01:18,090 --> 00:01:22,630
So usually what we do is first, we will be setting up the mole over here.

20
00:01:22,650 --> 00:01:24,900
We want to utilize the Vostok model here.

21
00:01:25,310 --> 00:01:27,550
They then we specify a couple.

22
00:01:27,570 --> 00:01:36,240
Now, this depends on the time for which you want to check your application over time, for which this

23
00:01:36,240 --> 00:01:40,470
will be the maximum time bound that you have for your application, right?

24
00:01:40,860 --> 00:01:44,850
So you will be needing a thousand value and then that value will be lower, right?

25
00:01:44,910 --> 00:01:52,080
Then usually we first stop the watchdog timer and then purposefully start it right and then we'll be

26
00:01:52,080 --> 00:01:53,910
writing some application launches, right?

27
00:01:53,910 --> 00:01:55,020
So let it just go ahead.

28
00:01:55,020 --> 00:02:01,620
And plus try to add an EPA that could be used to say OK, I of Cameroonian washed up more so we just

29
00:02:01,620 --> 00:02:03,070
required to utilize Disney.

30
00:02:03,360 --> 00:02:06,720
We just need to pass an instance structure, right?

31
00:02:07,170 --> 00:02:10,710
So we will go ahead, and this is the first thing that we do.

32
00:02:10,710 --> 00:02:13,920
So we'll be setting our watchdog timer in its war stuff.

33
00:02:14,050 --> 00:02:14,430
All right.

34
00:02:14,430 --> 00:02:22,600
So the instance for assists w d d, right, this is an instance of what we get right now.

35
00:02:23,370 --> 00:02:28,380
Let's assume you want the delay of five second rate, so delay of five.

36
00:02:28,380 --> 00:02:32,120
Second, you need to count the value for that, right?

37
00:02:32,130 --> 00:02:38,130
So we know that our watchdog timer operate at a frequency of three, three, three megawatts.

38
00:02:38,400 --> 00:02:39,390
This we already know.

39
00:02:39,900 --> 00:02:43,400
So to calculate the period, we just need to take the reverse off, right?

40
00:02:43,410 --> 00:02:49,770
So it will be simply one divide by one divide by three 368.

41
00:02:49,800 --> 00:02:52,890
This will be the duration for our single operate.

42
00:02:53,100 --> 00:03:00,540
Now we want if we want the delay of one second, we just need to multiply with the count so that this

43
00:03:00,540 --> 00:03:02,760
entire equation we're really going to want.

44
00:03:03,000 --> 00:03:06,840
So we just need to add three three, three e six now when we do this.

45
00:03:06,840 --> 00:03:13,170
So what will happen is one divide by three three three six and if we multiply, so design, this will

46
00:03:13,170 --> 00:03:16,080
cancel out and we'll be getting a delay of one second, right?

47
00:03:16,440 --> 00:03:21,930
So to get the delay of five second, what we need to do is we just need to multiplied by five, right?

48
00:03:22,230 --> 00:03:22,740
And.

49
00:03:23,790 --> 00:03:29,460
This will give us a delay of five second, right, so we'll just be declaring one very few 32.

50
00:03:29,580 --> 00:03:34,140
And this will be for a daily call rate.

51
00:03:35,240 --> 00:03:40,690
So to get the relief quite sick and we just need to multiply three three, three six by three.

52
00:03:41,000 --> 00:03:46,310
And when we multiply this, the single up will simply be getting a legal fight second, right?

53
00:03:46,340 --> 00:03:47,410
This is speaking.

54
00:03:47,420 --> 00:03:48,740
Let's send it right.

55
00:03:48,740 --> 00:03:55,730
So the frequency at which I washed off camera operators deleted three megapixel inverse of it will be

56
00:03:55,940 --> 00:04:02,720
giving us a period and then we just need to multiply by account to get the respective time that use

57
00:04:02,720 --> 00:04:02,990
of one.

58
00:04:03,080 --> 00:04:03,380
Right?

59
00:04:03,410 --> 00:04:04,580
This makes sense.

60
00:04:05,090 --> 00:04:09,590
So let it just go ahead and try to specify three three three eight.

61
00:04:09,950 --> 00:04:13,980
Then again, three three three three three three.

62
00:04:14,270 --> 00:04:18,980
So this is basically three three three megahertz into flight.

63
00:04:19,250 --> 00:04:21,230
This will give us a delay of five second.

64
00:04:21,260 --> 00:04:28,250
Now remember here the clock is six six.

65
00:04:29,620 --> 00:04:32,630
Seven Mega Hot, Right?

66
00:04:33,080 --> 00:04:40,420
And if you just stick the reverse of it, OK, if we just divide by two, we'll be getting 350 megahertz.

67
00:04:40,840 --> 00:04:46,480
That is the frequency of operation of all washed up and to get the delay of five.

68
00:04:46,510 --> 00:04:53,440
Second, we just need to specify the count value to be this right now will go ahead and we will be looking

69
00:04:53,440 --> 00:04:56,800
for an API that allow us to lower the rate.

70
00:04:56,800 --> 00:04:59,230
So we have this will just be copying.

71
00:04:59,230 --> 00:05:01,210
This will be adding it over here.

72
00:05:02,200 --> 00:05:06,130
So first, be required to specify the instant structure and then the value.

73
00:05:06,130 --> 00:05:08,830
So the value for our counter is.

74
00:05:10,390 --> 00:05:10,690
Right.

75
00:05:11,410 --> 00:05:19,240
So once we do this now, if you just look for any API, so we have a reset and then we a counter and

76
00:05:19,240 --> 00:05:27,640
timer expired this we do not require right, then we will proceed with stopping purposefully stopping

77
00:05:27,640 --> 00:05:29,110
our watch dog name, right?

78
00:05:29,710 --> 00:05:36,610
So let it just go ahead and stop our timer and then we will be starting.

79
00:05:37,890 --> 00:05:39,260
Normal operations, right?

80
00:05:40,840 --> 00:05:45,940
So these are the series of steps that you'll be doing, right, so we said the more we said the crowd,

81
00:05:46,210 --> 00:05:47,220
we lowered the count.

82
00:05:47,230 --> 00:05:53,240
We perpetually stop our camera and then we are starting a new fresh start for us.

83
00:05:53,680 --> 00:06:02,290
Right now, we know that if within the five second, if we do not refresh, I buy stock time or if we

84
00:06:02,290 --> 00:06:07,450
do not restart our watch, then in that case it will apply a risk for our system, right?

85
00:06:07,450 --> 00:06:15,400
So we'll just be adding the logic where we've sort of lost off timer within the maximum limit that we

86
00:06:15,400 --> 00:06:16,120
have specified.

87
00:06:16,120 --> 00:06:17,640
So here limit is five second.

88
00:06:17,740 --> 00:06:19,750
So we'll just be adding one.

89
00:06:20,320 --> 00:06:25,480
Let me just add a temporary variable temp, OK, and we'll just be counting.

90
00:06:26,760 --> 00:06:29,400
Dale Ho, okay, so this is purely random count.

91
00:06:30,450 --> 00:06:32,310
Just for a demonstration purpose.

92
00:06:33,280 --> 00:06:40,550
So here we declare one variable rate, so while temp is less than 100, no, this hundred is purely

93
00:06:40,550 --> 00:06:41,200
a random count.

94
00:06:41,230 --> 00:06:46,640
We are just incrementing at them and then we are waiting for the two second rate.

95
00:06:46,700 --> 00:06:53,110
No, this is within the maximum limit for our watchdog timer, which is five second, OK, and then

96
00:06:53,410 --> 00:06:57,460
we'll just be restarting the worst of them.

97
00:06:57,460 --> 00:06:57,760
All right.

98
00:06:58,030 --> 00:07:07,020
We'll also be bringing the value of them looking so damp and then we are printing it in a decimal format,

99
00:07:07,030 --> 00:07:07,360
right?

100
00:07:08,080 --> 00:07:10,540
And then we are calling a restart washed off time.

101
00:07:10,570 --> 00:07:14,730
So we do have an API to restart our rolling stock, namely.

102
00:07:15,790 --> 00:07:24,060
OK, so this is that so we have restarted watchdog timer and we just need to specify an instance structure,

103
00:07:24,070 --> 00:07:25,420
which is now.

104
00:07:26,670 --> 00:07:33,900
This will continuously right, even though you'll be finding them count will implement in an interval

105
00:07:33,900 --> 00:07:34,620
of second.

106
00:07:34,860 --> 00:07:36,990
But since we are calling a restart.

107
00:07:37,110 --> 00:07:38,370
OK, so what?

108
00:07:39,180 --> 00:07:45,960
It will never allow our watchdog timer to reach the delay of five seconds again and will be continuously.

109
00:07:47,240 --> 00:07:52,670
Seeing the temporal lobe in increment, the rate, so this is what we're going to analyze and then we'll

110
00:07:52,680 --> 00:07:59,780
just be disabling this restart watchdog timer and then you could possibly guess that within.

111
00:08:00,950 --> 00:08:05,570
The time when our value reaches two three will be applying a.

112
00:08:06,200 --> 00:08:12,230
This makes sense because for the first time, value will be consuming two second, then for next we

113
00:08:12,230 --> 00:08:13,730
will be continuing to move second.

114
00:08:14,090 --> 00:08:17,300
And then in the third iteration will give them value.

115
00:08:17,300 --> 00:08:21,320
Valuations to three will all already be causing the delay of five seconds.

116
00:08:21,320 --> 00:08:27,440
So this will automatically reset the watchdog timer and this will automatically reset our system, right?

117
00:08:27,470 --> 00:08:28,940
This is what we want to analyze.

118
00:08:29,780 --> 00:08:31,530
So let it just go and see.

119
00:08:31,630 --> 00:08:39,200
Our application will be clearing up our pencil and then performing relaunch off our debug session.

120
00:08:40,670 --> 00:08:46,970
So now if you also so after an interval of two, second, we have them one, then 10, two and three

121
00:08:47,510 --> 00:08:52,130
Game four -- by Game six.

122
00:08:52,160 --> 00:08:57,030
Now here you would see you already consume 12 chicken, 14 seconds 16.

123
00:08:57,470 --> 00:09:03,770
But since we are calling that was the timer, you would be able to see the system in resetting, right?

124
00:09:04,130 --> 00:09:09,710
And this we will be continuously going till Hydra and then we will be coming out.

125
00:09:09,710 --> 00:09:12,720
And since we do not call reset was famous.

126
00:09:12,730 --> 00:09:19,010
So as soon as we come out of this loop automatically within the five second, it will restart our process.

127
00:09:19,160 --> 00:09:19,440
Right.

128
00:09:19,460 --> 00:09:24,160
So you purposefully do this now here you will see since we are calling the restart.

129
00:09:24,170 --> 00:09:29,310
So this is not restarting our application, that is our application, which is incrementing the temp

130
00:09:29,310 --> 00:09:32,630
value by two and then waiting for to block it.

131
00:09:32,880 --> 00:09:36,720
OK, this is just working fine within the maximum specified time.

132
00:09:36,740 --> 00:09:37,970
That is five second rate.

133
00:09:38,300 --> 00:09:46,010
So if we just forget to call this restart node, what this will do is within an interval of use, it

134
00:09:46,010 --> 00:09:47,990
will again be incrementing and printing the value.

135
00:09:48,290 --> 00:09:51,530
But since we are not calling a restart, so within the five second.

136
00:09:52,600 --> 00:09:55,330
This will automatically restart our system.

137
00:09:55,540 --> 00:10:01,830
So let it just change this delay to one second to be able to see few more strings from our team.

138
00:10:02,150 --> 00:10:06,280
So let me just go over and try to perform a relaunch simulation.

139
00:10:07,030 --> 00:10:09,520
We'll just be clearing up our previous output.

140
00:10:10,010 --> 00:10:18,880
OK, so you could see Templin came to demo in full and then we visited a system so you won't be able

141
00:10:18,880 --> 00:10:20,730
to find anything after this, right?

142
00:10:21,220 --> 00:10:29,320
To be able to successfully these same system after and delay of quite sick.
