1

00:00:00,256  -->  00:00:02,304
So

2

00:00:02,560  -->  00:00:04,352
Welcome my friends

3

00:00:04,864  -->  00:00:06,912
The current chapter

4

00:00:07,168  -->  00:00:11,520
In this motion training now we're talkin about the 13

5

00:00:12,288  -->  00:00:15,616
Trace technology object trace

6

00:00:16,128  -->  00:00:20,224
and sinamics simotion Trace editor

7

00:00:22,784  -->  00:00:27,648
As you remember in lately

8

00:00:27,904  -->  00:00:34,048
At the other chapters we have already reduced used this kind of functionality

9

00:00:35,072  -->  00:00:37,120
Trace System trace

10

00:00:37,376  -->  00:00:40,192
Technology object race

11

00:00:40,960  -->  00:00:45,824
So let's see again quick overview

12

00:00:47,872  -->  00:00:52,992
Now working on offline mode I'm going to start simosim

13

00:00:53,248  -->  00:00:55,296
Yes

14

00:00:58,880  -->  00:01:02,208
Let's set it and go online

15

00:01:06,560  -->  00:01:08,608
i will download

16

00:01:09,376  -->  00:01:11,680
Program and device

17

00:01:26,528  -->  00:01:32,672
after sinamics firmwarre 2.6 is possible make an endless recording

18

00:01:32,928  -->  00:01:37,792
Isochronous recording trace

19

00:01:38,048  -->  00:01:40,096
In your computer

20

00:01:40,352  -->  00:01:46,496
Before the older cu's with older firmwares is not possible to make an

21

00:01:46,752  -->  00:01:48,032
endless recording

22

00:01:48,288  -->  00:01:49,056
So

23

00:01:50,592  -->  00:01:55,200
You see here device trace and function generator

24

00:02:00,064  -->  00:02:06,208
You can go into more detail with using mathematical processing is possible to

25

00:02:06,464  -->  00:02:11,584
create here some mathematical equations to calculate

26

00:02:11,840  -->  00:02:14,656
More than one variable and

27

00:02:15,424  -->  00:02:18,496
The output as the final curve

28

00:02:19,520  -->  00:02:25,664
There are here some bit trace settings

29

00:02:25,920  -->  00:02:27,968
You said it so

30

00:02:28,224  -->  00:02:29,760
Single here

31

00:02:30,784  -->  00:02:32,320
About

32

00:02:32,576  -->  00:02:36,160
System variable

33

00:02:36,416  -->  00:02:41,024
for instance One controller

34

00:02:41,280  -->  00:02:42,560
Setting

35

00:02:43,584  -->  00:02:47,936
Which bit you want to monitor in your trace diagram

36

00:02:48,192  -->  00:02:50,496
Like the curve

37

00:02:52,032  -->  00:02:57,920
You get some information about the memory utilization

38

00:02:58,176  -->  00:03:00,736
Connect to describe and so on...

39

00:03:02,784  -->  00:03:05,856
So you can use help in this case

40

00:03:07,904  -->  00:03:14,048
There's a function generator window you can select your signal it can be

41

00:03:15,584  -->  00:03:18,400
sinamics or simotion variable

42

00:03:20,960  -->  00:03:27,104
Let's say device specific variables is possible or on the other hand techno

43

00:03:27,360  -->  00:03:29,920
Object variables is possible

44

00:03:32,992  -->  00:03:34,528
Normally

45

00:03:37,856  -->  00:03:44,000
we use this function on the sinamics side

46

00:03:45,536  -->  00:03:50,656
To test our motor we give the signal

47

00:03:50,912  -->  00:03:52,704
Set point speed

48

00:03:53,216  -->  00:03:55,008
During

49

00:03:55,264  -->  00:03:57,312
motor tuning

50

00:03:57,568  -->  00:04:03,712
But this is the topic of another training so I don't want to go they don't sinamics side

51

00:04:06,272  -->  00:04:11,392
So you see here different choices that are two trays

52

00:04:11,648  -->  00:04:13,184
on sinamics side

53

00:04:13,696  -->  00:04:17,791
There are 1 trace

54

00:04:18,047  -->  00:04:22,399
For simotion sites that are two function generators

55

00:04:23,935  -->  00:04:25,471
could be run

56

00:04:25,983  -->  00:04:27,775
At the same time

57

00:04:28,031  -->  00:04:32,895
You can control here switch on switch off

58

00:04:33,407  -->  00:04:37,247
Start the function generator is possible

59

00:04:38,527  -->  00:04:44,671
so Measurements you see old measurements you can load from your hard drive you can save

60

00:04:45,951  -->  00:04:46,719
and

61

00:04:47,743  -->  00:04:49,279
Go into detail

62

00:04:51,583  -->  00:04:53,119
after you Come to office

63

00:04:54,399  -->  00:04:56,959
we used diagram for

64

00:04:57,215  -->  00:04:59,007
Monitoring traces

65

00:05:00,287  -->  00:05:05,663
FFT or BODE diagram is a topic of sinamics training

66

00:05:06,175  -->  00:05:10,271
So basically this is the device that trace

67

00:05:10,527  -->  00:05:16,415
You shall see here also the system trace available after firmware simotion

68

00:05:16,927  -->  00:05:18,207
4.2

69

00:05:18,463  -->  00:05:21,279
We have already tested once

70

00:05:22,303  -->  00:05:28,447
There is only one system trace year but it's possible to combine signals from

71

00:05:28,703  -->  00:05:31,263
Different CPUs together

72

00:05:33,311  -->  00:05:37,407
measuring function and automatic controller setting

73

00:05:37,919  -->  00:05:39,455
Normally

74

00:05:40,479  -->  00:05:43,551
we use for position control

75

00:05:44,575  -->  00:05:47,391
or circular test here

76

00:05:48,927  -->  00:05:55,071
Maybe we will make an example on real Hardware in simulation system

77

00:05:55,583  -->  00:05:58,143
It's not so logical to do that here

78

00:05:58,655  -->  00:06:00,447
So is the similar

79

00:06:04,543  -->  00:06:06,847
This button is for take the control

80

00:06:07,103  -->  00:06:09,919
After that you're able to run your tests

81

00:06:10,687  -->  00:06:12,735
final controlling element jump

82

00:06:12,991  -->  00:06:16,831
Position ramp to test axis position controller

83

00:06:17,087  -->  00:06:18,623
and

84

00:06:19,391  -->  00:06:25,535
Automatic controller setting is for adjusting your gain or

85

00:06:25,791  -->  00:06:29,119
The PID controller for position

86

00:06:31,935  -->  00:06:37,311
So basically these are traces you're going to use

87

00:06:37,823  -->  00:06:39,871
Both of the sites

88

00:06:40,383  -->  00:06:42,687
Drive and simotion

89

00:06:45,247  -->  00:06:46,271
You have used

90

00:06:47,295  -->  00:06:51,135
target system technology object trace

91

00:06:51,903  -->  00:06:58,047
This possible to select different technology objects and there are some parameters

92

00:06:58,303  -->  00:06:59,839
for recording

93

00:07:00,863  -->  00:07:07,007
It's you can set up a trigger to start the trace you can try

94

00:07:07,263  -->  00:07:09,823
view here recoreded data  as log file

95

00:07:11,359  -->  00:07:16,479
Settings will be made here in event selection

96

00:07:17,503  -->  00:07:23,647
Which command, will be monitored which configuration data or which system variable

97

00:07:23,903  -->  00:07:24,415
Logged

98

00:07:25,183  -->  00:07:27,743
Which alarms do you want to log...

99

00:07:27,999  -->  00:07:31,071
In your trace this is the technology object trace

100

00:07:32,607  -->  00:07:38,751
Used is also possible to configure download and monitor via web server

101

00:07:43,615  -->  00:07:44,639
Okay

102

00:07:48,479  -->  00:07:52,575
And another thing is let's see

103

00:08:01,791  -->  00:08:05,631
Real Hardware later on

104

00:08:06,143  -->  00:08:07,679
And other chapter

105

00:08:07,935  -->  00:08:14,079
You'll see the actual motor current in power and actual speed curves

106

00:08:14,335  -->  00:08:16,895
Time to time

107

00:08:18,943  -->  00:08:20,735
with experience

108

00:08:20,991  -->  00:08:23,295
You can do and

109

00:08:25,087  -->  00:08:30,207
Develop some ideas about what's going on in real machine

110

00:08:30,975  -->  00:08:34,559
You can see the curves and you can say that all

111

00:08:34,815  -->  00:08:38,143
Your maybe the motor is overloaded

112

00:08:38,911  -->  00:08:40,447
Or here

113

00:08:40,703  -->  00:08:43,263
There's an synchronisation problem

114

00:08:45,567  -->  00:08:51,711
And when we are using the camtool to create Cams you see the relationship

115

00:08:51,967  -->  00:08:54,271
Between the

116

00:08:54,527  -->  00:08:57,855
Position acceleration and jerk

117

00:09:01,183  -->  00:09:05,279
for motion control these are the fundamentals

118

00:09:08,095  -->  00:09:11,167
Processing the set points and PID loops

119

00:09:11,679  -->  00:09:16,031
Calculating the output from following errors

120

00:09:17,567  -->  00:09:20,383
There are so many details

121

00:09:20,895  -->  00:09:23,455
We have to discuss or talk about

122

00:09:24,735  -->  00:09:28,319
But basically for the trace view

123

00:09:28,575  -->  00:09:29,599
I think

124

00:09:29,855  -->  00:09:32,671
At the beginning it's enough for you

125

00:09:34,719  -->  00:09:37,023
If you're going to

126

00:09:37,535  -->  00:09:40,351
Do or want to do more

127

00:09:40,863  -->  00:09:44,959
you can Do your exercises

128

00:09:46,239  -->  00:09:47,775
it will be Take some time

129

00:09:50,079  -->  00:09:54,175
But it's also be useful for you

130

00:09:54,687  -->  00:09:55,711
I guess

131

00:10:00,831  -->  00:10:01,855
So

132

00:10:04,927  -->  00:10:05,951
Basically

133

00:10:06,207  -->  00:10:09,791
The traces are we are using in commonly

134

00:10:11,327  -->  00:10:12,607
These

135

00:10:14,655  -->  00:10:15,935
So

136

00:10:20,031  -->  00:10:22,591
see you at Next chapter