1
00:00:00,300 --> 00:00:08,940
We created a robot infusion 360, which was a CAG software when we extracted files from our CAD software.

2
00:00:09,060 --> 00:00:16,470
We had in this order the base first and then the caster and the V.

3
00:00:17,970 --> 00:00:24,270
Now all of these were and still file, which is a format for a mesh 3D file.

4
00:00:24,840 --> 00:00:29,910
All of these are going to be exported one by one, as I have shown you.

5
00:00:30,540 --> 00:00:32,940
Then to bring it into wrath.

6
00:00:33,630 --> 00:00:38,040
If you don't have a street, but there are plug ins that export directly to RDF.

7
00:00:38,280 --> 00:00:45,390
But I want you to understand the basic concept of creating a robot accustomed to RDF.

8
00:00:45,570 --> 00:00:51,900
So you can take a look into people's idea of the packages provided online and you can learn from them.

9
00:00:51,900 --> 00:00:55,860
You can use their models and edit them and add your files in to them.

10
00:00:55,870 --> 00:01:02,940
So the basic concept is you must know the idea of creating your own you ideas, coming to the point

11
00:01:02,940 --> 00:01:06,130
of using an SDL file in your view RDF.

12
00:01:06,150 --> 00:01:15,010
We are going to face some issues when we extract our model from a CAD software and bring it into wrath.

13
00:01:15,030 --> 00:01:22,560
The first issue that we face is the size issue I always faces when I work with this deal with a lot

14
00:01:22,560 --> 00:01:23,700
of other don't face it.

15
00:01:23,880 --> 00:01:31,320
We have options in cross to solve this by using a tag a size deck, but we are not going to do that.

16
00:01:31,330 --> 00:01:37,710
We are going to use blend it to solve this issue and resize it into a smaller part.

17
00:01:38,010 --> 00:01:45,720
For example, if a body is this big, we are going to reduce it into this size because simulation requires

18
00:01:45,720 --> 00:01:51,810
physical properties and smaller bodies are going to be a better representation for view solving robot.

19
00:01:52,260 --> 00:01:58,860
Otherwise, we have to create a huge, huge, huge maze to be solved and simulation is going to get

20
00:01:58,860 --> 00:01:59,950
heavy on our system.

21
00:02:00,030 --> 00:02:07,470
So we are going to avoid that coming to the next thing you are d of creation is going to be very easy

22
00:02:07,470 --> 00:02:12,570
for us when we are defining the links and the joints with the help of blender using parent and child

23
00:02:12,570 --> 00:02:19,500
concept in Blender, using the meshes that we have created, we will bring them in blender, create

24
00:02:19,500 --> 00:02:23,760
parent and child relations offset them and things are going to get easy.

25
00:02:24,120 --> 00:02:35,940
But how it is going to work, if this is a box which is set to be updated and we have a child V currently

26
00:02:35,940 --> 00:02:40,620
when we set parent and child, both of them were at zero zero origin.

27
00:02:40,620 --> 00:02:42,930
Okay, X, Y, Z, whatever, zero.

28
00:02:43,320 --> 00:02:45,780
But this was the parent, this was the child.

29
00:02:45,810 --> 00:02:58,260
When I move the parent from zero zero to let's say zero one, one and X, Y, Z, the child also moves.

30
00:02:58,580 --> 00:02:58,860
Okay.

31
00:02:59,040 --> 00:03:04,950
This relation that is being created with each ADD that is going to affect the movement from each child

32
00:03:04,950 --> 00:03:05,580
and parent.

33
00:03:05,850 --> 00:03:07,590
When the parent moves, child moves.

34
00:03:07,590 --> 00:03:16,940
But for the child there has not any translation because parent was moved, child was not move.

35
00:03:16,950 --> 00:03:21,960
They had a relation that caused the movement of the child, but child itself did not move.

36
00:03:22,230 --> 00:03:29,310
So this is the basic concept we need when we are building our parent and child relation in Blender.

37
00:03:29,310 --> 00:03:30,270
So let's take a look.