1
00:00:01,290 --> 00:00:08,430
In this lecture, I'm going to show you how to use the R b injured or returned by exception, the RPG

2
00:00:08,460 --> 00:00:11,520
note is available down here under functions.

3
00:00:11,670 --> 00:00:18,900
What it does is that it will only pass changes to its output, changes of its input to its output.

4
00:00:19,450 --> 00:00:21,760
Its input does not change.

5
00:00:21,780 --> 00:00:24,380
Then it will not forward it to the output.

6
00:00:24,870 --> 00:00:34,770
So it's easier to demonstrate, deploy this flow and of God and inject note here, sending a one and

7
00:00:34,770 --> 00:00:38,380
another inject node, sending a two to my Arby node.

8
00:00:38,850 --> 00:00:47,880
So first I'm going to click on the one on the first debug node and you can see that its value did pass

9
00:00:47,880 --> 00:00:49,170
through to the output.

10
00:00:49,680 --> 00:00:54,210
Now I'm going to click on the same node again and again and again.

11
00:00:54,210 --> 00:00:57,570
You can see up here it says that this node is injected with trigged.

12
00:00:58,620 --> 00:01:04,230
But nothing reaches the output, and that's because and that's because there is no change between the

13
00:01:04,770 --> 00:01:11,910
existing value and the new value that is held inside the RV inhered, and therefore it does not pass

14
00:01:11,910 --> 00:01:12,240
through.

15
00:01:12,600 --> 00:01:18,080
But if I send it a two to different value, you can see that that is passing through.

16
00:01:19,320 --> 00:01:22,020
Can you send a few more twos again?

17
00:01:22,020 --> 00:01:23,790
And none of them passes through?

18
00:01:23,790 --> 00:01:27,300
I can go back to one and that is now passing through.

19
00:01:27,780 --> 00:01:33,690
And because I've got different values coming through the RBA, you know, those are being passed through.

20
00:01:34,830 --> 00:01:37,530
So it's pretty simple the way that it works.

21
00:01:37,940 --> 00:01:42,360
There's not that much configuration wise, at least in these properties.

22
00:01:42,750 --> 00:01:48,930
You can see that you've got a few choices of how you would like this node to handle change.

23
00:01:49,500 --> 00:01:54,280
The simplest one is to just block change unless the value actually changes.

24
00:01:54,750 --> 00:02:06,000
So I am actually using this specific node in my project so that my flow terrarium controller will only

25
00:02:06,000 --> 00:02:15,330
tell the ADENHART to start and stop the pump motor if its previous instruction was opposite to the current

26
00:02:15,330 --> 00:02:16,100
instruction.

27
00:02:16,380 --> 00:02:21,480
So that way I'm just saving a little bit of bandwidth there and making the process a bit more efficient.
