1

00:00:00,256  -->  00:00:04,608
Song ladies and gentlemen welcome on board

2

00:00:06,144  -->  00:00:12,288
Our current chapter number is 12

3

00:00:12,544  -->  00:00:18,688
So in my opinion this is one of the most important topics of this course

4

00:00:19,712  -->  00:00:20,992
So

5

00:00:21,504  -->  00:00:22,784
Attention please!

6

00:00:23,296  -->  00:00:29,440
Topic is Central operations gearing and camming

7

00:00:30,208  -->  00:00:33,536
Now let's get started

8

00:00:34,816  -->  00:00:40,448
I will continue with simotion system

9

00:00:40,704  -->  00:00:44,032
Lecture notes you see

10

00:00:44,288  -->  00:00:46,592
Related chapter

11

00:00:47,360  -->  00:00:49,664
So

12

00:00:49,920  -->  00:00:56,064
Contents are structure of operation

13

00:00:56,320  -->  00:00:57,856
For simotion

14

00:00:58,368  -->  00:01:01,184
camming for simotion

15

00:01:01,440  -->  00:01:03,488
Creating Cams

16

00:01:04,512  -->  00:01:06,816
Creating synchronous axis

17

00:01:07,328  -->  00:01:11,936
Assigning leading axis and cams

18

00:01:12,704  -->  00:01:15,776
Settings for synchronous operation

19

00:01:16,800  -->  00:01:22,944
parameterizing default settings for synchronous operation

20

00:01:23,200  -->  00:01:26,016
gearingi in MCC

21

00:01:26,528  -->  00:01:29,600
Absolute and relative gearing

22

00:01:31,648  -->  00:01:33,696
Another example

23

00:01:34,208  -->  00:01:40,352
Synchronization relative to the leading axis and time

24

00:01:41,632  -->  00:01:46,240
Reference points for synchronization

25

00:01:47,008  -->  00:01:50,080
deactivating gearing with gear off

26

00:01:50,336  -->  00:01:53,920
System variables for synchronization

27

00:01:54,688  -->  00:01:57,760
absolute synchronous Operation

28

00:01:58,784  -->  00:02:01,344
Relative synchronous operation

29

00:02:02,112  -->  00:02:07,744
structure of superimposed synchronous operation

30

00:02:08,512  -->  00:02:12,864
Example about this chapter

31

00:02:14,144  -->  00:02:18,752
How do you insert a superimposed synchronous objects

32

00:02:19,776  -->  00:02:24,640
Structure of distributed sync operation

33

00:02:24,896  -->  00:02:26,688
That's it

34

00:02:26,944  -->  00:02:27,968
So...

35

00:02:28,224  -->  00:02:30,272
First page

36

00:02:30,528  -->  00:02:36,672
here You see the structure of sync operation for Simotion

37

00:02:38,464  -->  00:02:44,608
At the center this is our technology object as sync operation

38

00:02:44,864  -->  00:02:47,936
there are Several items

39

00:02:48,960  -->  00:02:52,800
Possible to make an interconnection together

40

00:02:53,056  -->  00:02:55,872
For instance a leading axis

41

00:02:56,384  -->  00:03:00,736
Or virtual access or external encoder is possible

42

00:03:00,992  -->  00:03:04,320
Masters or sync Operation

43

00:03:05,600  -->  00:03:09,440
And also your see here

44

00:03:09,952  -->  00:03:13,792
And the settings should be Master value

45

00:03:14,048  -->  00:03:17,888
Gear ratio between two system

46

00:03:18,144  -->  00:03:19,680
Master slave

47

00:03:19,936  -->  00:03:25,568
Centralized and decentralized profile you see here

48

00:03:26,336  -->  00:03:29,408
The master value and slave value chart

49

00:03:30,688  -->  00:03:36,576
So for followin axis technology object is possible to switch

50

00:03:37,600  -->  00:03:41,440
servo cycle or IPO cycle

51

00:03:41,952  -->  00:03:46,048
There are some restrictions here or monitoring functions

52

00:03:47,840  -->  00:03:49,376
So...

53

00:03:51,424  -->  00:03:57,568
A leading axis generates a master value which is processed by the sync object

54

00:03:57,824  -->  00:04:00,128
According to the specific criteria

55

00:04:00,640  -->  00:04:01,920
Parameters

56

00:04:02,176  -->  00:04:08,320
The master value Source can be a position axis or sync axis

57

00:04:08,576  -->  00:04:14,720
From firmware 3.0 as axis as a master value source is set point or actually

58

00:04:18,303  -->  00:04:24,447
For an actual dead time composition of the master value is possible

59

00:04:25,983  -->  00:04:28,287
As mechanical model

60

00:04:28,543  -->  00:04:34,687
The sync object represents the gearbox with Drive-In drive-out or in

61

00:04:34,943  -->  00:04:37,503
conJunction Cam

62

00:04:38,015  -->  00:04:42,111
The cam with mechanical Cam and Sensing system

63

00:04:48,767  -->  00:04:50,303
The next page

64

00:04:50,815  -->  00:04:53,375
camming for simotion

65

00:04:54,655  -->  00:04:57,215
you see

66

00:04:57,727  -->  00:05:03,871
Your relationship between master and slave value is not linear here that means

67

00:05:04,127  -->  00:05:07,967
Your gear ratio is not constant

68

00:05:08,223  -->  00:05:11,039
That's why you will see here

69

00:05:12,063  -->  00:05:13,343
a curve

70

00:05:14,367  -->  00:05:18,207
Let's say a cam profile

71

00:05:18,463  -->  00:05:19,231
So

72

00:05:20,511  -->  00:05:26,655
Master value can position axis synchronous axis external...

73

00:05:26,911  -->  00:05:31,263
Axis possible to make an interconnection

74

00:05:32,287  -->  00:05:37,151
First of all we have to select

75

00:05:37,407  -->  00:05:43,551
If there's some possibility after that we can use run time this interconnection

76

00:05:43,807  -->  00:05:44,831
Later on

77

00:05:46,367  -->  00:05:49,951
So sync operation

78

00:05:50,207  -->  00:05:51,487
Controls

79

00:05:51,743  -->  00:05:53,791
All of these

80

00:05:54,559  -->  00:05:57,119
Necessary

81

00:05:58,143  -->  00:06:04,287
Settings should be Master value a cam profile scale or offsets

82

00:06:05,055  -->  00:06:08,639
scaling at the synchronizing settings

83

00:06:09,919  -->  00:06:13,247
It's similar to gear so

84

00:06:15,039  -->  00:06:17,087
coupling via cam

85

00:06:17,855  -->  00:06:19,903
Is characterized

86

00:06:20,159  -->  00:06:26,303
by a variable that should be in the master and following axes is designed so users

87

00:06:26,559  -->  00:06:29,631
can program with cam

88

00:06:30,655  -->  00:06:32,703
In additional

89

00:06:33,471  -->  00:06:39,615
Adaptations for scaling at offset during system running in runtime system

90

00:06:40,639  -->  00:06:46,783
From firmware 3.0 and higher distributor as well as superimpose sync

91

00:06:47,039  -->  00:06:49,855
Operation are possible

92

00:06:51,135  -->  00:06:57,279
For distributed synchronous operation leading axis synchronous operation

93

00:06:57,535  -->  00:07:03,679
Go on the following axis you are not on the same simotion device

94

00:07:03,935  -->  00:07:07,263
That means an external synchronous operation

95

00:07:08,543  -->  00:07:11,615
Distributed over several controls

96

00:07:13,407  -->  00:07:19,551
For camming several Cams can be used changeover to another

97

00:07:19,807  -->  00:07:23,135
can be in user program at runtime

98

00:07:24,671  -->  00:07:26,207
There are some rules

99

00:07:27,231  -->  00:07:32,095
sync object and following axis are on the same run time system

100

00:07:32,863  -->  00:07:35,423
That means if you

101

00:07:35,935  -->  00:07:39,519
select IPO task for sync objects

102

00:07:40,031  -->  00:07:42,335
following axis

103

00:07:42,591  -->  00:07:45,407
Has to be processed in the IPO cycle

104

00:07:46,175  -->  00:07:52,319
Synchronous object and the following access are permanently assigned to each other during configuration

105

00:07:55,135  -->  00:07:56,159
Yep.

106

00:07:56,415  -->  00:07:58,207
The master value object

107

00:07:58,975  -->  00:08:02,047
can be connected with several objects

108

00:08:02,815  -->  00:08:08,959
And sync object may be interconnected with several master values or cams

109

00:08:11,007  -->  00:08:12,287
It's possible

110

00:08:15,103  -->  00:08:16,639
so next page

111

00:08:17,663  -->  00:08:23,807
There are some charts and images about creating cams with simotion

112

00:08:24,063  -->  00:08:30,207
On the left side that are basic to that cam tool is already integrated in our systems called cam edit

113

00:08:30,719  -->  00:08:35,839
You can Define according to vdi standards

114

00:08:37,119  -->  00:08:39,679
Is possible to use polynomial or

115

00:08:39,935  -->  00:08:44,287
Interpolation Point able to create the cam profile

116

00:08:45,567  -->  00:08:47,359
The horizontal axis

117

00:08:47,871  -->  00:08:52,223
Afterwards can be the master value

118

00:08:52,479  -->  00:08:58,623
Or the time diagram vertical axis value

119

00:09:01,183  -->  00:09:05,535
On the right side you'll see the Cam tool

120

00:09:08,095  -->  00:09:09,631
with new  versions

121

00:09:09,887  -->  00:09:12,703
It's already integrated

122

00:09:12,959  -->  00:09:18,335
In older versions We have to set up by yourself

123

00:09:18,847  -->  00:09:20,127
And

124

00:09:20,383  -->  00:09:24,223
camtool requires also additional license

125

00:09:26,527  -->  00:09:31,903
For just note you see here the green curve as position

126

00:09:32,927  -->  00:09:38,303
Blue curve as velocity and red curve as acceleration

127

00:09:38,559  -->  00:09:43,423
If you drag and drop or used toolbox for

128

00:09:43,679  -->  00:09:45,471
To do some changes

129

00:09:46,239  -->  00:09:48,799
you see online

130

00:09:49,055  -->  00:09:50,335
Difference

131

00:09:51,615  -->  00:09:56,735
Both graphics for

132

00:09:57,247  -->  00:10:03,135
all of the curves Acceleration ...

133

00:10:03,391  -->  00:10:04,671
At the same time

134

00:10:04,927  -->  00:10:08,255
So that you can easily

135

00:10:08,767  -->  00:10:11,583
Make your changes and see how do

136

00:10:11,839  -->  00:10:15,167
It's effect to

137

00:10:15,423  -->  00:10:16,447
Your

138

00:10:16,959  -->  00:10:18,239
Relationship

139

00:10:18,495  -->  00:10:20,799
Between master and slave.

140

00:10:24,127  -->  00:10:30,271
so cams that were created with cam edit can be converted to Camtool

141

00:10:31,295  -->  00:10:33,855
And vice-versa is possible

142

00:10:34,111  -->  00:10:37,183
cams can be exported and imported

143

00:10:39,487  -->  00:10:41,279
Two methods

144

00:10:41,535  -->  00:10:45,375
cannot be combine at same time for same cam

145

00:10:46,143  -->  00:10:52,031
But you can use that camedit and camtool for another cam

146

00:10:54,079  -->  00:10:58,687
Segments can be created from a fixed point in camtool

147

00:10:58,943  -->  00:11:01,503
Straight lines sine curves

148

00:11:02,271  -->  00:11:04,063
Interpolation points

149

00:11:04,575  -->  00:11:06,623
can becombined here

150

00:11:07,135  -->  00:11:08,927
On the left site

151

00:11:10,207  -->  00:11:15,583
You can just use polynomial function or interpolation table that's all

152

00:11:15,839  -->  00:11:19,167
On the right side you can create your segments

153

00:11:20,191  -->  00:11:25,567
That means camtool is a little bit Advance value compared to camedit

154

00:11:26,847  -->  00:11:30,687
Users can immediately see effect on real estate

155

00:11:31,199  -->  00:11:32,735
When changing the cam settings

156

00:11:32,991  -->  00:11:34,015
Okay

157

00:11:35,295  -->  00:11:38,623
Creating a Sync access

158

00:11:39,135  -->  00:11:44,767
See here there's an operation object under your axis

159

00:11:49,631  -->  00:11:52,447
there are some

160

00:11:52,703  -->  00:11:55,007
Assignments you have to do

161

00:11:55,775  -->  00:12:01,919
Assigning leading access and you'll see here in interconnection section

162

00:12:03,199  -->  00:12:05,759
following axis

163

00:12:06,527  -->  00:12:08,575
is filler red

164

00:12:09,087  -->  00:12:13,695
and master value can be blue axis

165

00:12:17,279  -->  00:12:18,559
Next

166

00:12:19,583  -->  00:12:23,423
There are some settings for sync operation

167

00:12:23,935  -->  00:12:28,287
In configuration screen use some parameters

168

00:12:32,639  -->  00:12:38,783
Bi-directional related Dynamic parameters taken into account a direction Independence or Direction indepented

169

00:12:39,039  -->  00:12:40,319
it effected

170

00:12:41,343  -->  00:12:44,671
here the system variable

171

00:12:47,231  -->  00:12:53,375
For absolute sync with a yes jerk is taken into account

172

00:12:54,399  -->  00:13:00,543
It's no jerk will not be applied over simplifier

173

00:13:00,799  -->  00:13:02,335
smooth via selection

174

00:13:03,615  -->  00:13:09,759
overshoot factor for adapter time to catch up a compensate

175

00:13:10,015  -->  00:13:11,807
remaining path differents

176

00:13:12,063  -->  00:13:15,135
Is important during sync

177

00:13:16,159  -->  00:13:18,207
As percentage

178

00:13:18,975  -->  00:13:23,583
Refers to the actual Master velocity start Of synchronization

179

00:13:24,607  -->  00:13:29,727
Think about that you just executed your gear on command

180

00:13:29,983  -->  00:13:32,287
Your master velocity released it

181

00:13:33,567  -->  00:13:39,455
The best case scenario is constant for instance 100mm/s

182

00:13:40,223  -->  00:13:45,343
But when your synchronizing as slave to your master

183

00:13:45,855  -->  00:13:47,135
It's possible

184

00:13:47,391  -->  00:13:53,535
To do some change on your Master velocity and you have to

185

00:13:53,791  -->  00:13:59,679
Recalculate your sync length or formula

186

00:13:59,935  -->  00:14:01,471
Simultaneously

187

00:14:01,983  -->  00:14:06,079
and over Short factor is related with this case

188

00:14:07,359  -->  00:14:13,503
tolerance for Directions revalsal operation for

189

00:14:13,759  -->  00:14:17,343
Direction reversal of Master values

190

00:14:18,111  -->  00:14:22,719
Position value in the user unit of Master values

191

00:14:24,767  -->  00:14:26,303
You see here

192

00:14:28,351  -->  00:14:31,167
Normally is 20%

193

00:14:32,447  -->  00:14:35,263
Permit velocity change

194

00:14:36,287  -->  00:14:39,103
of the master value

195

00:14:46,783  -->  00:14:52,159
Parameterizing default settings for synchronous operation

196

00:14:53,183  -->  00:14:55,487
Is on the default section

197

00:15:02,655  -->  00:15:08,799
And so are you just answer here

198

00:15:13,151  -->  00:15:17,759
So for activating gering in MCC

199

00:15:19,039  -->  00:15:23,391
You and use this commands the first one here enable

200

00:15:25,183  -->  00:15:26,975
You just select

201

00:15:27,231  -->  00:15:29,279
The following axes

202

00:15:29,535  -->  00:15:33,375
It's sync operation objects

203

00:15:34,399  -->  00:15:36,703
At the parameter tab

204

00:15:36,959  -->  00:15:43,103
Leading access encoder and external Master value must be selected

205

00:15:44,127  -->  00:15:48,223
Specification of leading and following axes

206

00:15:49,759  -->  00:15:53,343
gear direction from sign of the gear ratio

207

00:15:55,391  -->  00:16:01,535
You see here numerator is one denominator is one that means

208

00:16:02,303  -->  00:16:08,447
45 degree in your XY coordinate system when your

209

00:16:08,703  -->  00:16:09,727
Master

210

00:16:12,031  -->  00:16:15,359
Takes 100 mini meter of distance

211

00:16:17,407  -->  00:16:23,551
Also you'll slave will take 150 milimetres because your gear ratio is one

212

00:16:26,623  -->  00:16:30,719
It's possible to change type of gear ratio from fraction

213

00:16:30,975  -->  00:16:32,767
Two floating points

214

00:16:34,047  -->  00:16:40,191
So here you just said it's your gearing reference point it could be absolute or

215

00:16:40,447  -->  00:16:41,983
Relative

216

00:16:45,567  -->  00:16:50,431
If you said it here in takes place relative to axis zero

217

00:16:53,247  -->  00:16:59,391
Then if you select it didn't take place relative to start position

218

00:17:00,415  -->  00:17:05,535
That means relative gearing the first one means

219

00:17:06,303  -->  00:17:08,095
Absolute

220

00:17:08,351  -->  00:17:10,143
axis zero

221

00:17:10,399  -->  00:17:13,215
point is use your reference

222

00:17:14,751  -->  00:17:18,079
you can use last program setting or default

223

00:17:18,591  -->  00:17:20,895
actually that I only just

224

00:17:21,151  -->  00:17:22,431
Choices

225

00:17:22,687  -->  00:17:28,831
I'm transition Behavior and the delay program execution is similar with other program

226

00:17:35,999  -->  00:17:40,351
Reference points type of sync operation selected here

227

00:17:42,911  -->  00:17:47,775
For example angle or position sync operation

228

00:17:50,079  -->  00:17:55,711
relative synchronous operation you should set it to start position

229

00:17:56,223  -->  00:17:59,039
set new master value

230

00:18:01,087  -->  00:18:03,903
reset master value setting

231

00:18:04,927  -->  00:18:10,559
Using this checkbox relationship is set again

232

00:18:11,071  -->  00:18:17,215
The checkbox has not been activated a previous Master resetting steps

233

00:18:23,615  -->  00:18:29,247
Yep it's also a detail but important

234

00:18:30,271  -->  00:18:35,391
What's the difference between absolute and relative gearing you see

235

00:18:37,183  -->  00:18:43,327
Position or angle synchronization when you set a gearing absolute

236

00:18:43,583  -->  00:18:47,935
That means gearing is realized refer to axis zero

237

00:18:49,215  -->  00:18:55,359
you see the master value at the slave value that are the different

238

00:18:56,639  -->  00:19:02,783
so if it is Defined respite order system function call sync

239

00:19:04,575  -->  00:19:06,111
On the other hand

240

00:19:07,391  -->  00:19:13,535
If you want to use speed gearing or relative gearing you should select

241

00:19:13,791  -->  00:19:15,839
Start position

242

00:19:16,607  -->  00:19:22,751
and phi is undefined at this case

243

00:19:24,543  -->  00:19:27,103
slave value

244

00:19:27,359  -->  00:19:28,383
should be G

245

00:19:28,639  -->  00:19:34,783
I mean gratio equation

246

00:19:37,343  -->  00:19:39,391
There are two options here

247

00:19:42,719  -->  00:19:48,863
Activating gear in MCC second TAB synchronisation

248

00:19:50,399  -->  00:19:55,007
select here Synchronisation reference

249

00:19:55,263  -->  00:19:59,359
It's possible to use leading axis Master axis

250

00:19:59,615  -->  00:20:00,895
Or time

251

00:20:01,663  -->  00:20:07,551
According to your choice start of synchronization settings are changed

252

00:20:08,575  -->  00:20:11,135
There are several options here

253

00:20:13,439  -->  00:20:17,535
Start of synchronization

254

00:20:18,047  -->  00:20:21,631
Synchronized method in this case

255

00:20:21,887  -->  00:20:25,471
Synchronization is initiated

256

00:20:26,751  -->  00:20:27,775
ASAP

257

00:20:28,543  -->  00:20:34,687
When should I get it takes place relative to access zero

258

00:20:36,223  -->  00:20:42,367
Is performed it's not possible to specify and additional phase offset

259

00:20:44,671  -->  00:20:50,815
It's leading axis position means synchronization start if the axis

260

00:20:51,071  -->  00:20:53,631
Reached a certain position

261

00:20:55,167  -->  00:20:57,983
You use this setting with

262

00:20:58,239  -->  00:21:02,335
flying saw application for example you wait

263

00:21:03,103  -->  00:21:05,151
For some material length

264

00:21:05,663  -->  00:21:11,807
After your axis has reached at certain points your slave cutters

265

00:21:12,063  -->  00:21:17,952
realised by slave for instance

266

00:21:20,512  -->  00:21:25,632
When selecting gearing takes place where

267

00:21:25,888  -->  00:21:31,264
Absolute sand composition performed it's not possible to specify phase offsets

268

00:21:32,800  -->  00:21:36,384
During sync op of course

269

00:21:36,640  -->  00:21:42,784
It leading access position with offsets sync starts if the leading axis

270

00:21:43,040  -->  00:21:45,088
reached starting position

271

00:21:45,856  -->  00:21:47,904
So in this case

272

00:21:48,160  -->  00:21:54,048
An additional phase offset on the specified between leading and following axes

273

00:21:58,144  -->  00:22:01,472
sync immediate with offset

274

00:22:02,240  -->  00:22:06,592
Is the same thing at first one but you can Define here additional offset

275

00:22:06,848  -->  00:22:11,968
Start immediately and sync at Master position

276

00:22:14,784  -->  00:22:20,928
At the specified leading axis position following axis is in synchronizing with

277

00:22:21,184  -->  00:22:26,560
Leading axis it's not possible to specify an additional phase offset

278

00:22:28,096  -->  00:22:32,704
selecting using version 4.0

279

00:22:32,960  -->  00:22:34,496
Is not supported

280

00:22:40,896  -->  00:22:43,968
At the following axis position

281

00:22:44,736  -->  00:22:48,576
Is the following axis has reached a certain position

282

00:22:53,184  -->  00:22:55,232
Synchronization start

283

00:22:56,000  -->  00:23:00,096
That means you're following axis must be rotating

284

00:23:00,352  -->  00:23:01,376
If this case

285

00:23:01,632  -->  00:23:02,912
To catch

286

00:23:03,168  -->  00:23:06,752
following axis position and execute command

287

00:23:07,008  -->  00:23:10,592
It depends on your application actually

288

00:23:12,128  -->  00:23:14,176
If you select

289

00:23:14,432  -->  00:23:18,016
Leading axis as reference you have to

290

00:23:18,272  -->  00:23:21,344
Define synchronization length

291

00:23:22,880  -->  00:23:25,696
That's according to this length

292

00:23:26,208  -->  00:23:29,536
The function at the background in IPO cycle

293

00:23:29,792  -->  00:23:35,936
calculated Set points to following Axis

294

00:23:37,984  -->  00:23:40,544
as position and 1st and so on

295

00:23:44,640  -->  00:23:49,504
So you can specify sync Direction

296

00:23:49,760  -->  00:23:52,320
Positive or negative

297

00:23:54,880  -->  00:23:58,464
That's setting also with Look ahead

298

00:24:01,280  -->  00:24:03,840
And next page

299

00:24:04,096  -->  00:24:05,632
New here

300

00:24:06,400  -->  00:24:10,752
When you select relative to Leading access and time

301

00:24:11,776  -->  00:24:15,360
Relative syn and time

302

00:24:17,152  -->  00:24:19,200
so here

303

00:24:20,224  -->  00:24:26,368
The horizontal axis is time axis vertical axis is position

304

00:24:27,648  -->  00:24:33,792
Blue curve is position actual position of leading axis and green curve

305

00:24:35,072  -->  00:24:38,656
Is actual position of the following axis

306

00:24:42,240  -->  00:24:45,568
Anyway you executed your command

307

00:24:48,384  -->  00:24:52,224
You selected leading axis

308

00:24:55,552  -->  00:24:58,368
So here the following axis

309

00:24:58,624  -->  00:25:03,744
Is Standstill just waiting some certain point

310

00:25:04,512  -->  00:25:07,328
Use leading axis value

311

00:25:07,584  -->  00:25:08,864
after that

312

00:25:11,680  -->  00:25:13,728
The following axis

313

00:25:14,496  -->  00:25:16,288
Should be catch up

314

00:25:17,056  -->  00:25:22,176
It's specified synchronization length according to our settings

315

00:25:27,040  -->  00:25:28,320
So

316

00:25:28,832  -->  00:25:31,392
All calculations are made

317

00:25:31,904  -->  00:25:35,232
Leading axis velocity is constant

318

00:25:36,000  -->  00:25:40,352
This is the start point and this is end point of synchronization

319

00:25:40,608  -->  00:25:46,752
I'm during this area you will see under System variable of sync

320

00:25:47,008  -->  00:25:50,848
Object State and Motion State

321

00:25:51,360  -->  00:25:52,896
At this point

322

00:25:54,176  -->  00:25:57,504
slave axis is sync to master

323

00:26:05,440  -->  00:26:11,584
During synchronization operation is not permissible leading access reverses

324

00:26:11,840  -->  00:26:17,216
Otherwise gearing on, interrupted with the error message

325

00:26:18,496  -->  00:26:24,640
error while activating and deactivating sync operation

326

00:26:28,736  -->  00:26:30,528
there is a system parameter

327

00:26:31,552  -->  00:26:37,696
So it depends on your application that are so many possible

328

00:26:37,952  -->  00:26:43,584
next page

329

00:26:44,352  -->  00:26:47,424
Reference point for sync

330

00:26:49,472  -->  00:26:52,032
you will see here

331

00:26:52,288  -->  00:26:54,848
as keft Blue Line

332

00:26:55,104  -->  00:26:56,896
sync pos

333

00:26:59,712  -->  00:27:03,808
We have here a leading axis and following axis

334

00:27:05,344  -->  00:27:07,392
as setting

335

00:27:07,648  -->  00:27:10,208
symmetrical sync

336

00:27:12,512  -->  00:27:16,864
sync position

337

00:27:17,120  -->  00:27:20,448
Will be done in the middle of

338

00:27:22,496  -->  00:27:24,288
slave axis

339

00:27:24,544  -->  00:27:26,592
During sync

340

00:27:28,384  -->  00:27:34,528
When was select the gear on command your settings sync

341

00:27:34,784  -->  00:27:38,880
before synchronisation position

342

00:27:39,392  -->  00:27:42,464
then you are sure

343

00:27:43,232  -->  00:27:44,512
Before

344

00:27:44,768  -->  00:27:49,632
You're leading axis reached sync position

345

00:27:50,400  -->  00:27:56,032
For example 1 mm of before your slave axes will be

346

00:27:56,800  -->  00:28:01,152
Started movements from Standstill

347

00:28:01,408  -->  00:28:06,528
It's right here at the sync position your slave axis

348

00:28:06,784  -->  00:28:08,320
will be synchronized

349

00:28:11,648  -->  00:28:16,000
You can see here the reference settings

350

00:28:22,912  -->  00:28:27,776
Activating gearing you just use the second command

351

00:28:29,824  -->  00:28:32,640
There are some similar parameters

352

00:28:32,896  -->  00:28:37,760
You said it following axes and sync operation objects

353

00:28:38,528  -->  00:28:42,880
You have to enter here synchronisation reference

354

00:28:43,648  -->  00:28:47,232
It's the leading axis actual position

355

00:28:49,536  -->  00:28:55,424
You can select the synchronization position with leading axis value

356

00:28:56,704  -->  00:28:58,496
Then you have to

357

00:28:58,752  -->  00:29:01,824
Describe the synchronization length

358

00:29:02,336  -->  00:29:08,224
end the reference points of position can be symmetrical

359

00:29:08,480  -->  00:29:11,552
Stop after the sync position

360

00:29:11,808  -->  00:29:15,392
Or other options are possible

361

00:29:17,184  -->  00:29:21,536
So almost for same gearing off parameters

362

00:29:24,352  -->  00:29:27,168
It's the similar operation

363

00:29:27,424  -->  00:29:33,568
Or if it's not important for you you can just use the stop axis command

364

00:29:33,824  -->  00:29:36,384
Instead of gearing off

365

00:29:38,688  -->  00:29:39,968
Yeah

366

00:29:40,224  -->  00:29:41,248
Possible

367

00:29:44,576  -->  00:29:48,672
There are some system variables for this operation

368

00:29:49,696  -->  00:29:53,792
You see here the blue

369

00:29:54,048  -->  00:30:00,192
Show us leading access actual position access

370

00:30:00,448  -->  00:30:02,496
axis position

371

00:30:05,312  -->  00:30:09,664
So start of the syn operation

372

00:30:10,944  -->  00:30:16,064
You can read system variable state is right there

373

00:30:16,576  -->  00:30:20,160
following motion states should be active

374

00:30:22,976  -->  00:30:24,000
Right here

375

00:30:24,256  -->  00:30:28,864
Your slave axis must be syn because

376

00:30:29,888  -->  00:30:31,168
you see

377

00:30:31,936  -->  00:30:35,776
Angle under the 2 curves are the same

378

00:30:36,800  -->  00:30:39,360
sync state

379

00:30:39,616  -->  00:30:44,736
it's active and sync monitoring and sync States must be active

380

00:30:46,528  -->  00:30:52,672
So in the background or after executive gear on command, you can check this variable

381

00:30:52,928  -->  00:30:59,072
How to program or build up your structure for programming

382

00:31:03,424  -->  00:31:05,472
So...

383

00:31:08,288  -->  00:31:09,824
next thing is

384

00:31:10,080  -->  00:31:14,944
When you select relative to leading axis

385

00:31:15,456  -->  00:31:20,320
How do absolute sync operation work

386

00:31:21,600  -->  00:31:24,672
This is the output of a Trace

387

00:31:27,232  -->  00:31:29,024
The orange color is

388

00:31:29,280  -->  00:31:31,584
Set point of axis

389

00:31:32,352  -->  00:31:34,912
Set point position of master

390

00:31:37,216  -->  00:31:41,056
You should see your the brown one

391

00:31:42,336  -->  00:31:45,152
Set point position of other axis

392

00:31:48,224  -->  00:31:51,040
You see slave Axis position

393

00:31:52,064  -->  00:31:55,904
So green one is sync States

394

00:31:56,160  -->  00:31:57,184
Available

395

00:31:58,464  -->  00:32:01,536
and the dark blue one is

396

00:32:02,304  -->  00:32:04,096
master axis velocity

397

00:32:04,352  -->  00:32:06,656
Light blue one is

398

00:32:07,936  -->  00:32:13,568
Slave setpoint vel gear in settings gear ratio is 1:1

399

00:32:14,080  -->  00:32:19,968
sync immediately and length is 30 millimeters

400

00:32:20,224  -->  00:32:20,992
Absolute

401

00:32:21,504  -->  00:32:23,808
Relative to axis zero

402

00:32:27,904  -->  00:32:30,464
so at this case...

403

00:32:31,488  -->  00:32:35,584
Actual position of slave axis is 0

404

00:32:36,864  -->  00:32:42,496
And the actual position of Master axis is rising

405

00:32:42,752  -->  00:32:45,056
Right here

406

00:32:48,384  -->  00:32:52,480
You see the synchronization procedure has started

407

00:32:54,272  -->  00:32:55,808
There's a

408

00:32:56,320  -->  00:32:58,880
overshoot of slave velocity

409

00:32:59,136  -->  00:33:01,440
Third degree polynomial

410

00:33:02,976  -->  00:33:06,560
Slave axis is trying to catch up

411

00:33:07,328  -->  00:33:11,168
That's why the slave vel it is

412

00:33:12,448  -->  00:33:14,240
1l box

413

00:33:15,520  -->  00:33:17,056
multiply 2

414

00:33:17,824  -->  00:33:21,152
25 mm/s

415

00:33:21,920  -->  00:33:23,200
at top

416

00:33:23,456  -->  00:33:29,600
After that you see here the slave vel at this point is the same with

417

00:33:29,856  -->  00:33:32,416
 master vel 10 mm/s

418

00:33:32,928  -->  00:33:37,792
At this point you see the statsu sync is set

419

00:33:39,584  -->  00:33:40,608
sync state

420

00:33:41,632  -->  00:33:43,936
As velocity of course

421

00:33:51,360  -->  00:33:53,152
Synchronization

422

00:33:53,664  -->  00:33:55,200
For leading axis

423

00:33:57,504  -->  00:34:00,320
Should be under 20

424

00:34:01,088  -->  00:34:07,232
What you see here the setting is immediately your at this point you just executed your comment

425

00:34:09,024  -->  00:34:14,144
When you want to measure the distance here

426

00:34:15,168  -->  00:34:16,960
You can see the timeline

427

00:34:17,984  -->  00:34:21,824
sync length must be 30 millimeters

428

00:34:22,080  -->  00:34:28,224
Let's say you're a master and 20 they say here in almost

429

00:34:28,480  -->  00:34:33,344
50 so 30mm

430

00:34:34,624  -->  00:34:35,648
Correct

431

00:34:41,792  -->  00:34:45,120
So think about that

432

00:34:45,632  -->  00:34:51,008
Right now or slave axis actual position is zero i assume

433

00:34:52,800  -->  00:34:58,688
What will happen when slave axis actual position

434

00:34:58,944  -->  00:35:01,248
What's difference for instance

435

00:35:01,504  -->  00:35:04,832
100mm or -100 mm

436

00:35:05,856  -->  00:35:09,952
Maybe you will try as an example

437

00:35:10,464  -->  00:35:13,024
So

438

00:35:13,280  -->  00:35:18,144
abs sync operation relative to time

439

00:35:21,472  -->  00:35:25,056
The settings are here gearing absolute

440

00:35:26,336  -->  00:35:32,480
Directions shortest distance that mean it's possible

441

00:35:32,736  -->  00:35:38,880
Rotational axis positive or negative system will automatically detect

442

00:35:39,136  -->  00:35:40,416
Shortest distance

443

00:35:40,672  -->  00:35:46,816
sync from the leading axis position not before from

444

00:35:50,656  -->  00:35:56,800
vel 200% using acceleration and jerk setting

445

00:35:57,056  -->  00:36:01,408
when you select relative the time you have to define the

446

00:36:01,664  -->  00:36:05,248
Dynamic parameters what is the acceleration vel jerk...

447

00:36:05,504  -->  00:36:08,320
So let's see

448

00:36:10,880  -->  00:36:15,232
Orange curve you see the slave velocity

449

00:36:17,024  -->  00:36:22,144
master velocity constant with light blue 100%

450

00:36:24,960  -->  00:36:28,032
You see here the set position.

451

00:36:28,544  -->  00:36:34,688
master set position and purple one is slave set position

452

00:36:34,944  -->  00:36:35,712
at this point

453

00:36:35,968  -->  00:36:38,528
This is our sync state curve

454

00:36:43,136  -->  00:36:45,184
At the beginning

455

00:36:46,464  -->  00:36:50,048
Actual pos of slave is 0

456

00:36:52,608  -->  00:36:58,752
And sync from leading axis position 150mm

457

00:37:15,136  -->  00:37:19,744
so The movement of slave axis is started here according to

458

00:37:20,512  -->  00:37:25,120
Parameters and maximum velocity reached 200 millimeters per second

459

00:37:26,400  -->  00:37:28,448
and there is a ramp down

460

00:37:29,472  -->  00:37:31,008
At this point

461

00:37:31,264  -->  00:37:33,824
Our slave velocity

462

00:37:34,080  -->  00:37:36,384
Is 100%

463

00:37:37,152  -->  00:37:40,480
You can Define and calculate the time

464

00:37:43,040  -->  00:37:44,064
It's

465

00:37:45,600  -->  00:37:47,136
Nearly

466

00:37:47,392  -->  00:37:48,672
3 seconds

467

00:37:54,048  -->  00:37:56,352
If you want to measure the

468

00:37:57,376  -->  00:37:58,912
actual position

469

00:38:03,008  -->  00:38:06,336
It should be 150 mm

470

00:38:06,592  -->  00:38:09,408
We just see here to velocity only

471

00:38:12,480  -->  00:38:13,760
So

472

00:38:16,320  -->  00:38:22,464
Sequence from specified vel and acceleration following axis constant vel

473

00:38:22,720  -->  00:38:28,864
sync operation following axis calculated profile relative to time

474

00:38:29,120  -->  00:38:35,264
Synchronization of the following actions is start at the beginning of 

475

00:38:35,520  -->  00:38:36,544
his position of 150mm

476

00:38:38,080  -->  00:38:42,944
It should be 150 mm right here

477

00:38:52,672  -->  00:38:58,816
After the jerk phase following axes acc at the program with acc ramp and vel

478

00:38:59,072  -->  00:39:02,656
after const vel phase possible

479

00:39:02,912  -->  00:39:08,032
If it's possible sometimes when your jerks are too much

480

00:39:08,288  -->  00:39:14,432
You couldn't reach on slave axis to set velocity phase to so

481

00:39:14,688  -->  00:39:19,296
slave vel could be like this

482

00:39:21,344  -->  00:39:24,672
Like and hill or the top

483

00:39:25,952  -->  00:39:30,304
dynamics response values specified parameters okay

484

00:39:31,072  -->  00:39:33,632
Another possibility

485

00:39:34,912  -->  00:39:40,800
The relative synchronous operation relative to Leading axis

486

00:39:41,056  -->  00:39:43,872
The parameters are gear ratio 1:1

487

00:39:44,384  -->  00:39:46,688
Relative gearing

488

00:39:46,944  -->  00:39:52,064
sync immediate and length 30mm

489

00:39:52,832  -->  00:39:58,208
Let's try orange color is set point of

490

00:39:58,976  -->  00:40:00,256
Master

491

00:40:00,512  -->  00:40:01,536
Axis

492

00:40:08,448  -->  00:40:14,592
yes brown curve is set point position of slave axis

493

00:40:14,848  -->  00:40:18,176
At the beginning it's zero

494

00:40:18,432  -->  00:40:24,576
Master is nearly zero I assume it's zero dark blue

495

00:40:24,832  -->  00:40:30,976
Is set point speed of Master axis and the light blue is

496

00:40:31,232  -->  00:40:33,792
Setpoint velocity of

497

00:40:34,304  -->  00:40:40,448
slave axis you see here the Green curve as sync States

498

00:40:40,704  -->  00:40:45,568
red curve state under your access system variables

499

00:40:46,080  -->  00:40:51,456
At this point the gearing, executed and states

500

00:40:51,712  -->  00:40:52,736
Changed

501

00:40:53,248  -->  00:40:55,552
immediately to active

502

00:40:56,064  -->  00:41:01,184
At this point sync State is active and axis sync

503

00:41:01,952  -->  00:41:05,792
each velocity equals to each other

504

00:41:08,608  -->  00:41:12,960
So you see here trapezoidal velocity profile

505

00:41:15,520  -->  00:41:16,800
at this case

506

00:41:20,640  -->  00:41:26,272
You're just entered the sync length of 30 millimeters

507

00:41:32,416  -->  00:41:35,744
So you can see on the vertical axis

508

00:41:36,256  -->  00:41:38,048
It's nearly

509

00:41:38,304  -->  00:41:40,352
15 millimeters

510

00:41:40,608  -->  00:41:46,752
At the start and it's and it's near 45 45 - 15 = 30mm

511

00:41:47,008  -->  00:41:53,151
Iand slave vel listed calculated according to

512

00:41:53,407  -->  00:41:55,711
These parameters

513

00:42:03,903  -->  00:42:08,511
linear acceleration ramp is used to ramp up the velocity

514

00:42:12,607  -->  00:42:14,911
Yeah at this case

515

00:42:15,935  -->  00:42:20,287
What's the difference when you compare at the

516

00:42:20,799  -->  00:42:22,079
Example

517

00:42:26,687  -->  00:42:31,039
This is the absolute sync operation

518

00:42:38,463  -->  00:42:40,767
This is the

519

00:42:41,023  -->  00:42:43,583
relative sync Operation

520

00:42:48,447  -->  00:42:52,799
if You want to use jerk your maybe you should set it

521

00:42:53,311  -->  00:42:54,591
This case

522

00:42:58,175  -->  00:43:01,247
Okay

523

00:43:01,759  -->  00:43:07,391
Structure of superimposed sync operation

524

00:43:08,927  -->  00:43:15,071
there are 2 Synchronous object at this case it's possible to connect different cams

525

00:43:15,327  -->  00:43:17,631
leading axis

526

00:43:18,143  -->  00:43:20,959
followin axis

527

00:43:21,215  -->  00:43:24,543
sholud Be calculated together

528

00:43:25,055  -->  00:43:31,199
Basic sync object is standard superimposed sync object is

529

00:43:31,455  -->  00:43:32,735
The other one

530

00:43:32,991  -->  00:43:35,807
from version 3.0

531

00:43:36,063  -->  00:43:37,855
Is possible to do that

532

00:43:38,623  -->  00:43:44,767
Only one relationship can be configured to leading axis it's not permissible to configure a

533

00:43:45,791  -->  00:43:51,167
Relationships to the same leading axes from the basis of superimposed

534

00:43:57,823  -->  00:44:03,455
so There's an example filling chocolate molds on the conveyor belt

535

00:44:05,759  -->  00:44:09,855
so There's a sensor for detection of product

536

00:44:10,111  -->  00:44:14,975
Those are external encoder to calculate the actual position

537

00:44:15,231  -->  00:44:20,095
conveyor axis 1 rotating Direction

538

00:44:20,863  -->  00:44:22,911
in Horizontal

539

00:44:23,167  -->  00:44:26,751
From left to right 

540

00:44:27,775  -->  00:44:29,823
Axis 2 Movement Direction

541

00:44:30,079  -->  00:44:32,639
Is positive from

542

00:44:32,895  -->  00:44:36,479
That way and otherwise negative

543

00:44:36,991  -->  00:44:43,135
conveyor belt is not traversed from simotion so we can detect that position of

544

00:44:43,391  -->  00:44:45,439
With external encoder

545

00:44:50,303  -->  00:44:52,607
In that case

546

00:44:54,911  -->  00:44:56,959
Filled chocolate molds

547

00:44:58,751  -->  00:44:59,775
Forward

548

00:45:00,031  -->  00:45:04,127
and backward during conveyor belt movement

549

00:45:04,383  -->  00:45:06,431
With different shapes

550

00:45:11,039  -->  00:45:13,855
So at this case

551

00:45:15,647  -->  00:45:19,743
Maybe you should superimpose sync operation

552

00:45:26,143  -->  00:45:32,031
Because your conveyor is running constantly it doesn't stop

553

00:45:32,287  -->  00:45:35,359
At the meantime you have to

554

00:45:36,383  -->  00:45:38,175
Synchronize

555

00:45:39,199  -->  00:45:40,479
Your axes

556

00:45:41,503  -->  00:45:43,551
Actually to the conveyor

557

00:45:44,575  -->  00:45:46,879
On the other hand

558

00:45:47,391  -->  00:45:50,975
You have to move to create your shapes here

559

00:46:00,703  -->  00:46:04,799
How do you insert a superimposed sync subject

560

00:46:05,567  -->  00:46:07,103
Just right. click

561

00:46:07,871  -->  00:46:10,175
on axes on expert list

562

00:46:10,431  -->  00:46:14,783
Context you inserta oject

563

00:46:15,039  -->  00:46:17,599
Let's Check

564

00:46:20,671  -->  00:46:24,255
I'm going to delete this CPU

565

00:46:40,639  -->  00:46:42,943
Okay

566

00:46:43,711  -->  00:46:48,063
And my axis Master is

567

00:46:50,111  -->  00:46:52,159
Positioning axis

568

00:46:53,695  -->  00:46:56,511
Let's try right click export

569

00:46:58,047  -->  00:47:03,167
Insert external synchronous operation is possible but its position axis

570

00:47:04,703  -->  00:47:10,335
Let's select following axes sync operation right here

571

00:47:11,615  -->  00:47:13,407
So...

572

00:47:14,175  -->  00:47:15,199
The object

573

00:47:17,247  -->  00:47:20,831
following axis when I click export list

574

00:47:21,087  -->  00:47:25,183
Is possible to insert superimpose sync object

575

00:47:26,719  -->  00:47:29,023
Can you see here

576

00:47:29,535  -->  00:47:32,095
To sync operation

577

00:47:47,199  -->  00:47:53,343
You can use the first one and my interconnection to axis master and

578

00:47:53,599  -->  00:47:58,975
Use the second one make interconnection to convert for example

579

00:47:59,231  -->  00:48:03,327
I'm in yourMSSy program or structure text

580

00:48:03,583  -->  00:48:06,655
when you use ger on off commands

581

00:48:07,423  -->  00:48:11,775
You should select it which synchronization you want to make

582

00:48:12,799  -->  00:48:14,335
You can also

583

00:48:14,591  -->  00:48:16,639
Used 2 gear on comments 1 for this 1 for that

584

00:48:19,967  -->  00:48:23,039
Is possible to calculate on superimpose

585

00:48:23,551  -->  00:48:28,415
Set position and velocity for slave axis axis virtual

586

00:48:31,487  -->  00:48:37,631
It's special cases that kind of function simotion will provide for you

587

00:48:40,191  -->  00:48:46,335
So another thing structure of distributed sync operation

588

00:48:46,591  -->  00:48:47,871
you will see here

589

00:48:49,151  -->  00:48:52,479
 profibus slave

590

00:48:53,503  -->  00:48:54,527
Another unit

591

00:48:56,063  -->  00:48:58,623
And another profibus slave

592

00:48:59,135  -->  00:49:01,951
profibus master

593

00:49:02,207  -->  00:49:08,351
consider about this is in machine this is another machine

594

00:49:08,607  -->  00:49:10,911
Another CPU

595

00:49:11,935  -->  00:49:14,239
One master with 2 slave

596

00:49:15,263  -->  00:49:19,871
from version 3.0 and higher it's possible

597

00:49:22,687  -->  00:49:28,831
This function allows a Master value Source and synchronous axes to be created on different devices

598

00:49:29,087  -->  00:49:35,231
coupling between leading access or encoder and the leading

599

00:49:35,487  -->  00:49:38,047
leading axis realize profibus DP

600

00:49:38,559  -->  00:49:39,839
or profinet

601

00:49:40,351  -->  00:49:46,495
Using distributive sync operation function groups can be formed in project modular machine

602

00:49:49,311  -->  00:49:53,151
Especially in printing industrial because there are a lot of

603

00:49:54,175  -->  00:49:55,455
servo axes

604

00:49:56,223  -->  00:50:01,855
when axes running is sync that no longer have to be counted on

605

00:50:02,111  -->  00:50:04,159
Central system

606

00:50:04,415  -->  00:50:08,511
It's can be to distribute or several models

607

00:50:14,655  -->  00:50:17,215
so that way You can just sync 

608

00:50:17,471  -->  00:50:20,543
CPUs together

609

00:50:21,567  -->  00:50:23,615
via communication Network

610

00:50:23,871  -->  00:50:27,455
And here there's a leading axis

611

00:50:28,479  -->  00:50:31,551
there are following axes here

612

00:50:33,855  -->  00:50:37,439
The following axis on the profibus slave

613

00:50:37,695  -->  00:50:43,327
could synchronize two leading axis on a profibus master

614

00:50:45,887  -->  00:50:48,703
This is the idea

615

00:50:49,983  -->  00:50:52,287
So how do we do that

616

00:50:53,311  -->  00:50:59,455
This the right college and expertise and insult external synchronous operation

617

00:51:03,039  -->  00:51:07,135
at this case we have to Define

618

00:51:08,415  -->  00:51:14,559
The coupling type of input output address for the other CPUs

619

00:51:15,583  -->  00:51:16,607
it is possible

620

00:51:21,215  -->  00:51:23,519
You see here the conflagration

621

00:51:25,055  -->  00:51:30,943
And you should use some system functions to synchronize your profinet network

622

00:51:31,711  -->  00:51:33,503
To do that

623

00:51:50,399  -->  00:51:56,031
At the same way for master axis your master axis will be slave

624

00:52:04,223  -->  00:52:05,247
Okay

625

00:52:20,351  -->  00:52:21,887
Next topic

626

00:52:23,935  -->  00:52:28,799
External encoder Cam outputs and measuring inputs

627

00:52:31,871  -->  00:52:32,895
Yep

628

00:52:33,151  -->  00:52:36,479
Contents are here

629

00:52:38,271  -->  00:52:42,367
Example project is mechanical press

630

00:52:43,903  -->  00:52:45,183
Which options

631

00:52:45,439  -->  00:52:50,559
Order for connecting an external encoder configuration steps

632

00:52:51,583  -->  00:52:56,191
Parameterizing mechanics actually and homing

633

00:52:57,215  -->  00:53:00,543
Continues

634

00:53:01,311  -->  00:53:06,687
Measuring inputs and outputs on the other side

635

00:53:10,271  -->  00:53:12,063
lets begin

636

00:53:15,647  -->  00:53:20,511
outputCams high speeds output cams so

637

00:53:22,303  -->  00:53:28,191
Here you see an application example that are some picker

638

00:53:28,959  -->  00:53:31,007
pick some parts

639

00:53:32,287  -->  00:53:36,127
From the bunker or the destack puts

640

00:53:37,151  -->  00:53:40,223
2D Cartesian whatever

641

00:53:40,991  -->  00:53:47,135
after picker puts on Parts with this conveyor

642

00:53:47,391  -->  00:53:51,999
there is an electrical motor maybe it's controlled by another system

643

00:53:52,511  -->  00:53:56,863
So there is an external encoder the for position feedback

644

00:53:57,887  -->  00:54:00,703
Our system

645

00:54:00,959  -->  00:54:05,055
You'll see here the light barrier to detecting parts

646

00:54:05,567  -->  00:54:08,639
And there is a glue application

647

00:54:08,895  -->  00:54:13,247
after glue a cartoons or whatever

648

00:54:13,503  -->  00:54:15,039
There's a ram

649

00:54:15,551  -->  00:54:19,903
To shape up or parts and

650

00:54:20,159  -->  00:54:22,463
Pushes parts

651

00:54:22,719  -->  00:54:26,303
down sites into another conveyor beltl here

652

00:54:26,815  -->  00:54:29,887
And process will continiue afterwards

653

00:54:30,655  -->  00:54:32,447
This is our case

654

00:54:32,703  -->  00:54:37,823
for developer program to run the application

655

00:54:40,639  -->  00:54:41,919
So...

656

00:54:43,455  -->  00:54:45,247
In that case

657

00:54:45,759  -->  00:54:49,599
we use measuring inputs and outputs cams

658

00:54:50,367  -->  00:54:52,927
Because there's a really fast

659

00:54:53,951  -->  00:54:56,511
Application running conveyor

660

00:54:57,535  -->  00:55:03,679
specially on cartooners maybe over 400 metres per minute

661

00:55:03,935  -->  00:55:07,263
So if you have to glue it really fast

662

00:55:07,775  -->  00:55:09,567
Specific points

663

00:55:09,823  -->  00:55:14,175
Why are parts running under your nozzle

664

00:55:15,199  -->  00:55:21,343
So ligt barrier is connected to our measuring inputs

665

00:55:21,599  -->  00:55:23,647
CPU

666

00:55:23,903  -->  00:55:29,791
And glue nozzle outputs are connected to fast outputs

667

00:55:30,047  -->  00:55:32,607
The name as output cams

668

00:55:33,375  -->  00:55:36,703
of modules of simotion integrated IOs

669

00:55:39,519  -->  00:55:42,079
Next page

670

00:55:42,847  -->  00:55:46,687
External encoder on a mechanical press

671

00:55:47,455  -->  00:55:49,247
There's a main driver

672

00:55:50,271  -->  00:55:54,623
in conventional systems there's a big flywheel

673

00:55:54,879  -->  00:55:57,439
belt controlled

674

00:55:57,695  -->  00:56:03,583
On the other sites that are some Clutch and Brake system

675

00:56:05,631  -->  00:56:10,751
with couple of rotation on the motor side there is a 1 stroke

676

00:56:11,775  -->  00:56:16,639
And here encoder to sense the position

677

00:56:17,407  -->  00:56:19,199
and stRock number

678

00:56:19,455  -->  00:56:21,247
As degrees

679

00:56:21,759  -->  00:56:25,855
To convert into actual position or

680

00:56:26,111  -->  00:56:27,647
actual stroke rate

681

00:56:28,159  -->  00:56:30,463
There's a roll feeder here

682

00:56:31,743  -->  00:56:34,559
There's a decoiler here maybe

683

00:56:35,327  -->  00:56:36,863
It should be a loop

684

00:56:37,631  -->  00:56:38,399
perhaps

685

00:56:39,167  -->  00:56:40,959
So

686

00:56:41,215  -->  00:56:42,495
die setup

687

00:56:44,031  -->  00:56:50,175
this image belongs to a standard Progressive press especially high speed presses

688

00:56:50,431  -->  00:56:51,455
progressive presses

689

00:56:54,527  -->  00:56:56,831
So this is my idea

690

00:56:57,599  -->  00:57:03,743
As you can see here an example of options for connecting external encoder

691

00:57:03,999  -->  00:57:06,047
possible directly

692

00:57:06,559  -->  00:57:08,095
via drive cliq

693

00:57:08,863  -->  00:57:12,447
simotion or sinamics control units

694

00:57:13,215  -->  00:57:19,359
You can use control based smotion that are for external encoders

695

00:57:19,871  -->  00:57:21,919
 it's possible

696

00:57:22,175  -->  00:57:24,223
There's another special device

697

00:57:24,479  -->  00:57:29,087
analog digital interface for looks like this

698

00:57:31,391  -->  00:57:37,535
There's an Old module looks like a simatic model interface mode

699

00:57:37,791  -->  00:57:40,607
IM174

700

00:57:43,167  -->  00:57:45,983
Nearly the same functionality

701

00:57:47,519  -->  00:57:51,871
on simodrive 611 Universal

702

00:57:52,383  -->  00:57:56,991
It's possible to connect One external encoder to your drive

703

00:57:58,015  -->  00:58:03,391
Also there are some other profibus or profiNets sensors

704

00:58:03,647  -->  00:58:07,231
on siemens sites on TR electronic or whatever

705

00:58:10,559  -->  00:58:13,375
TTL HTL or SSI

706

00:58:14,143  -->  00:58:16,959
It depends on your configuration

707

00:58:18,751  -->  00:58:22,335
And if it's possible you should isochronous

708

00:58:22,847  -->  00:58:25,407
Sensors that means

709

00:58:25,663  -->  00:58:30,783
Supporting message frame 81 or 83

710

00:58:32,063  -->  00:58:33,343
It could be

711

00:58:34,111  -->  00:58:36,927
Better for you than you can easily

712

00:58:37,183  -->  00:58:39,999
Adapt external encoder

713

00:58:40,511  -->  00:58:43,327
To your technology object and

714

00:58:43,839  -->  00:58:45,631
You should select

715

00:58:46,143  -->  00:58:48,959
The IRT type

716

00:58:49,983  -->  00:58:51,519
The next page

717

00:58:51,775  -->  00:58:53,823
When your insert

718

00:58:54,079  -->  00:58:57,151
click insert external encoder here

719

00:58:58,431  -->  00:58:59,967
For instance

720

00:59:00,991  -->  00:59:03,295
You're just you a name

721

00:59:03,551  -->  00:59:05,343
okay

722

00:59:06,879  -->  00:59:09,951
You select encoder type

723

00:59:11,231  -->  00:59:15,327
Which way do you want to use linear or rotary

724

00:59:15,583  -->  00:59:17,119
linear type

725

00:59:18,655  -->  00:59:19,935
And here

726

00:59:20,191  -->  00:59:21,983
You have to decide

727

00:59:22,239  -->  00:59:26,079
You can make your assignment later

728

00:59:26,847  -->  00:59:31,711
Or you can select the input address your module

729

00:59:32,479  -->  00:59:34,783
Or is there is some encoder

730

00:59:35,295  -->  00:59:39,391
On your drive cliq on your sinamics side is possible to connect

731

00:59:39,647  -->  00:59:41,695
simotion d

732

00:59:42,207  -->  00:59:45,279
There is no integrated encoder port

733

00:59:45,535  -->  00:59:49,119
D425 you use

734

00:59:49,887  -->  00:59:53,215
Control the bass motion you should see here

735

00:59:54,239  -->  00:59:57,567
4 different encoder is possible to connect

736

00:59:57,823  -->  00:59:59,103
So...

737

01:00:03,711  -->  01:00:06,015
Define assignment later

738

01:00:06,783  -->  01:00:11,647
You have to choose your encoder if type absolute or incremental

739

01:00:13,695  -->  01:00:15,743
So basically

740

01:00:15,999  -->  01:00:17,023
That's it.

741

01:00:22,399  -->  01:00:28,543
rotary type should always be selected if position detected in angular

742

01:00:28,799  -->  01:00:32,895
Units for example rotary table

743

01:00:33,151  -->  01:00:37,503
indexing table or in this case mechanical process

744

01:00:40,063  -->  01:00:46,207
If you say linear you should consider the conveyor or transport sistem or...

745

01:00:49,535  -->  01:00:54,655
So that you can configure your needs as millimeter or centimeter

746

01:00:54,911  -->  01:00:56,447
Blah blah blah...

747

01:00:58,239  -->  01:01:01,055
at the last step you assign an actor

748

01:01:01,311  -->  01:01:02,591
to your encoder

749

01:01:02,847  -->  01:01:04,895
select type

750

01:01:05,151  -->  01:01:07,711
Then it's finished

751

01:01:09,503  -->  01:01:15,391
That you have your external and colder if your Click in configuration

752

01:01:18,719  -->  01:01:24,607
You see that are some parameters under your encoder to configuration

753

01:01:26,143  -->  01:01:31,519
And it has its own expert list it similar to your axes

754

01:01:32,799  -->  01:01:36,895
But much more simple

755

01:01:37,663  -->  01:01:40,479
In mechanics you define

756

01:01:41,759  -->  01:01:43,551
Your encoder is there

757

01:01:43,807  -->  01:01:47,647
And when run your motor

758

01:01:47,903  -->  01:01:50,207
Rotates once

759

01:01:50,975  -->  01:01:53,023
How many rotations your

760

01:01:53,279  -->  01:01:54,303
Both sides

761

01:01:54,559  -->  01:01:59,423
load here for your encoder to calculate

762

01:02:00,703  -->  01:02:02,751
The lead screw pitch value for

763

01:02:03,007  -->  01:02:06,335
The distance from spindle Revolution together

764

01:02:07,103  -->  01:02:09,919
Is possible to use modulo more than one

765

01:02:10,175  -->  01:02:14,015
with Rotary encoders specially used

766

01:02:14,527  -->  01:02:16,319
So...

767

01:02:31,167  -->  01:02:33,727
Actual value tab is

768

01:02:35,007  -->  01:02:37,823
Important at some application

769

01:02:38,847  -->  01:02:44,991
you see you're actually an extrapolation used as master value

770

01:02:45,247  -->  01:02:47,039
in sync group

771

01:02:47,807  -->  01:02:50,111
Actual value sometimes

772

01:02:50,623  -->  01:02:56,767
It is required to be smooth or extrapolated with the extrapolation

773

01:02:57,023  -->  01:03:01,375
Is used to compensate the dead times which are when

774

01:03:01,887  -->  01:03:08,031
Acquiring the actual as result of bus communication in the system

775

01:03:08,287  -->  01:03:11,871
When you don't use the IRT support encoders

776

01:03:12,383  -->  01:03:16,735
Extrapolation is set on leading axis encoder

777

01:03:16,991  -->  01:03:21,343
There's a small calculation program in your folder

778

01:03:23,135  -->  01:03:27,231
So filtering exposition

779

01:03:27,743  -->  01:03:30,303
From version 

780

01:03:30,559  -->  01:03:31,839
4.0

781

01:03:32,095  -->  01:03:38,239
Actual position value for sync operation can be filter separately for extrapolation using

782

01:03:38,495  -->  01:03:40,031
pt1 filter

783

01:03:40,543  -->  01:03:45,663
The filter of position actual value of axis set using the option

784

01:03:46,431  -->  01:03:49,247
with 2 time constants

785

01:03:50,783  -->  01:03:54,111
Sometimes it's necessary

786

01:03:54,623  -->  01:04:00,767
The position is extrapolated based on filter or average velocity

787

01:04:01,023  -->  01:04:05,887
actual velocity

788

01:04:08,703  -->  01:04:13,311
It depends on your Hardware on your system

789

01:04:15,871  -->  01:04:22,015
Sometimes you have to adjust the parameters here to do a proper sync

790

01:04:22,271  -->  01:04:23,295
Transition

791

01:04:24,063  -->  01:04:28,415
Because your encoder is going to be a master

792

01:04:28,671  -->  01:04:31,231
For another slave axis

793

01:04:31,999  -->  01:04:37,119
If you have some problem in your master actual value

794

01:04:37,631  -->  01:04:43,775
Then it influences your set point position and velocity to your slaves

795

01:04:44,799  -->  01:04:46,335
Your slaves then

796

01:04:47,871  -->  01:04:51,711
Will be work out properly

797

01:04:52,223  -->  01:04:54,015
perhaps

798

01:04:55,295  -->  01:05:00,415
parameterizing external encoder homing tab

799

01:05:03,487  -->  01:05:06,047
default settings at homming

800

01:05:08,095  -->  01:05:09,887
As default

801

01:05:11,167  -->  01:05:13,983
With or without encoder the zero Max selected

802

01:05:15,263  -->  01:05:19,103
External zero marks pos Direction homing cam input

803

01:05:19,615  -->  01:05:21,151
It's possible to select

804

01:05:26,015  -->  01:05:32,159
Ye simotional support various centralizing for external encoders

805

01:05:32,415  -->  01:05:36,511
direct passive flying homing...

806

01:05:38,815  -->  01:05:41,119
when your encoder rotates

807

01:05:41,887  -->  01:05:45,983
sets executive Home passive homing

808

01:05:46,495  -->  01:05:48,543
It's is done

809

01:05:49,055  -->  01:05:53,151
when your sensor logic level is high

810

01:05:56,479  -->  01:06:00,319
So it depends on your application also

811

01:06:04,159  -->  01:06:09,279
You just take a feedback of actual at this case

812

01:06:12,095  -->  01:06:14,911
External encoder as leading value

813

01:06:17,727  -->  01:06:20,799
When it's homing necessary

814

01:06:21,055  -->  01:06:23,615
For external encoder is possible

815

01:06:23,871  -->  01:06:26,687
Similar way with axis

816

01:06:28,223  -->  01:06:34,367
next page display of the encoder signal flow

817

01:06:39,231  -->  01:06:42,303
signal flow

818

01:06:44,863  -->  01:06:47,935
You can monitor the actual you

819

01:06:48,703  -->  01:06:50,239
There are some

820

01:06:51,007  -->  01:06:55,359
In what setting normalization positioning filter

821

01:06:55,871  -->  01:06:58,943
Adjust T1 T2

822

01:06:59,199  -->  01:07:02,783
This is the same to you enter here

823

01:07:03,551  -->  01:07:05,343
Position actuator

824

01:07:05,599  -->  01:07:07,903
T1 T2

825

01:07:10,207  -->  01:07:11,999
This is a flow chart

826

01:07:13,023  -->  01:07:19,167
you see here actualvelocity value smoothing filter or velocity filter

827

01:07:20,191  -->  01:07:24,031
Extrapolation and fine interpolation

828

01:07:24,543  -->  01:07:26,591
there is a tolerence windows

829

01:07:27,359  -->  01:07:29,663
so on...

830

01:07:29,919  -->  01:07:32,735
on velocity filter or position filter

831

01:07:36,575  -->  01:07:39,391
In real life

832

01:07:40,415  -->  01:07:41,951
during  commissioning

833

01:07:42,463  -->  01:07:46,815
You just test your program and Trace the

834

01:07:47,071  -->  01:07:51,167
Actual position speed master and slave

835

01:07:51,423  -->  01:07:54,495
Arrange you some parameters to

836

01:07:56,287  -->  01:07:58,847
Set your machine running properly

837

01:07:59,615  -->  01:08:01,919
Sometimes you have to adjust

838

01:08:06,783  -->  01:08:12,927
Sistem commands for external encoders you'll see here the first 3

839

01:08:14,207  -->  01:08:20,351
External encoder on or off and synchronize external encoder you just select it here

840

01:08:20,607  -->  01:08:22,143
Technology objects

841

01:08:22,911  -->  01:08:26,751
Which synchronize means do the homming

842

01:08:27,007  -->  01:08:32,127
similar to do homing of an axis

843

01:08:34,175  -->  01:08:40,063
If you select passive homing for next axis motion according to set things on the homing tab

844

01:08:41,087  -->  01:08:44,671
axis synchronize to work first wait for homing mark

845

01:08:45,439  -->  01:08:47,487
axis means external encoder

846

01:08:47,743  -->  01:08:51,071
Setting of position value

847

01:08:51,583  -->  01:08:57,727
You just enter home position coordinate is transferred into current axis coordinates

848

01:08:59,263  -->  01:09:05,407
when use absolute encoder adjustment the selection is available for only absolute encoders

849

01:09:05,663  -->  01:09:06,431
Of course.

850

01:09:07,455  -->  01:09:13,599
I've been configured with absolute in this case of state

851

01:09:13,855  -->  01:09:16,415
When you execute the comment

852

01:09:17,951  -->  01:09:24,095
So next topic measuring input and measuring length of cutouts

853

01:09:28,447  -->  01:09:34,591
Measuring input means on the positive or negative Edge

854

01:09:34,847  -->  01:09:36,383
Of the sensor

855

01:09:36,895  -->  01:09:41,503
we will take a snapshot of an encoder

856

01:09:43,039  -->  01:09:45,855
That's fine you will see

857

01:09:46,111  -->  01:09:49,695
measuring inputs and output camp under

858

01:09:50,207  -->  01:09:53,791
The folder of Technology object external encoder

859

01:09:54,047  -->  01:09:58,143
So that means there's a relationship between

860

01:09:58,399  -->  01:10:01,215
This objects

861

01:10:01,727  -->  01:10:02,751
encoder

862

01:10:03,007  -->  01:10:05,567
axes similar way

863

01:10:06,079  -->  01:10:08,127
So...

864

01:10:11,711  -->  01:10:17,855
It's not possible or meaningless used measuring input by itself

865

01:10:24,255  -->  01:10:28,863
So a measuring input save the actual axis position

866

01:10:29,119  -->  01:10:35,263
value can be for the process in user program after take a snapshot

867

01:10:36,031  -->  01:10:40,895
We can do with this value whatever we want

868

01:10:41,407  -->  01:10:43,455
maybe we will

869

01:10:43,967  -->  01:10:47,807
Make a buffer and add the

870

01:10:48,575  -->  01:10:51,135
Positions of the

871

01:10:51,391  -->  01:10:52,159
Parts

872

01:10:52,415  -->  01:10:54,975
Running on the conveyor

873

01:10:55,487  -->  01:10:59,839
and after 10 meters that is a kicker

874

01:11:00,095  -->  01:11:04,447
pnomatical control device to

875

01:11:04,959  -->  01:11:06,495
kick some part

876

01:11:07,263  -->  01:11:12,127
Maybe the part is defective so that way we can spare

877

01:11:16,223  -->  01:11:22,111
Let's see which global and local measuring input connection option

878

01:11:24,415  -->  01:11:27,231
So here you see

879

01:11:27,999  -->  01:11:31,327
Some terminal modules is connected via Drive.

880

01:11:32,095  -->  01:11:38,239
And when we just use the measuring input it should be.global

881

01:11:43,871  -->  01:11:47,199
when we use simotion or sinamics

882

01:11:48,479  -->  01:11:54,623
it should be the local or Global measuring inputs

883

01:11:55,647  -->  01:11:57,439
Here you see

884

01:11:58,719  -->  01:12:03,583
Which number of measuring impulse can be connected to simotion CPU

885

01:12:05,375  -->  01:12:08,959
On the right side on controller-based

886

01:12:09,727  -->  01:12:14,079
2 or 4 input possible to connect

887

01:12:15,615  -->  01:12:21,503
ADI4 and interface module 174 there are 2 measuring input

888

01:12:22,015  -->  01:12:26,879
On the old sinamics drive system there is only one input

889

01:12:27,135  -->  01:12:30,975
These are local measuring Inputs

890

01:12:31,743  -->  01:12:37,887
That's means processed in drive or in modul itself

891

01:12:39,423  -->  01:12:42,495
After with a Time step

892

01:12:43,007  -->  01:12:47,615
The controller takes into account over communication line

893

01:12:51,711  -->  01:12:52,735
Yep.

894

01:12:58,367  -->  01:13:04,511
Local measurements fast Response input of encoder system will be used

895

01:13:05,791  -->  01:13:11,935
when al appropriate edge is detected encoder value saved and transferred

896

01:13:12,191  -->  01:13:13,727
via message frame

897

01:13:15,263  -->  01:13:19,615
Options are available fast input of sinamics

898

01:13:20,383  -->  01:13:22,943
Controller base simotion

899

01:13:28,319  -->  01:13:30,111
Other modules on the right side

900

01:13:30,367  -->  01:13:32,671
For Global measurement

901

01:13:34,463  -->  01:13:38,815
Initially the position is not acquired but at timestamp

902

01:13:39,583  -->  01:13:42,143
The timestamp

903

01:13:42,399  -->  01:13:43,423
signal

904

01:13:43,679  -->  01:13:48,287
simotion using a special message frame and Telegram

905

01:13:48,543  -->  01:13:54,687
From this time stamp and cyclic transfer actual positions simotion calculus

906

01:13:54,943  -->  01:13:56,223
Interpolation

907

01:13:56,479  -->  01:14:01,087
So simotion calculate everything when we use Global input

908

01:14:06,975  -->  01:14:13,119
With global measurements position of axes can be determined which supply cyclic actual values

909

01:14:13,375  -->  01:14:15,679
overall system

910

01:14:16,191  -->  01:14:20,031
For example external encoder connected sinamics profibus

911

01:14:20,543  -->  01:14:21,823
so

912

01:14:22,591  -->  01:14:27,199
Global measurements are supported on the following models

913

01:14:27,967  -->  01:14:30,527
On the leftside

914

01:14:33,087  -->  01:14:34,623
So...

915

01:14:36,927  -->  01:14:41,279
measuring input at

916

01:14:42,047  -->  01:14:45,631
D425 - 2 local measurements

917

01:14:46,655  -->  01:14:49,471
We are going to create

918

01:14:52,031  -->  01:14:53,567
Like this

919

01:14:53,823  -->  01:14:56,127
go in configuration

920

01:14:56,639  -->  01:15:00,223
Let's say IPO cycle

921

01:15:00,479  -->  01:15:02,527
Axis number 1

922

01:15:03,295  -->  01:15:04,575
Is the

923

01:15:05,599  -->  01:15:07,903
Motor encoder usually

924

01:15:08,159  -->  01:15:09,439
The first one

925

01:15:10,719  -->  01:15:15,327
Correction value for timestamp is a parameter can be

926

01:15:16,351  -->  01:15:17,631
Definable

927

01:15:18,143  -->  01:15:24,031
When you select your drive related that means local measuring input

928

01:15:24,287  -->  01:15:27,359
and say number one

929

01:15:31,455  -->  01:15:33,759
so in our case

930

01:15:34,271  -->  01:15:40,159
Use the virtual axis so you have to look and real axes

931

01:15:45,535  -->  01:15:50,143
So I want to open the

932

01:15:51,679  -->  01:15:53,215
Other projects

933

01:15:55,263  -->  01:15:57,055
This is the first project

934

01:15:58,847  -->  01:16:01,407
Yes

935

01:16:08,063  -->  01:16:11,135
For we have an example project

936

01:16:13,951  -->  01:16:18,559
test no simotion sys prog

937

01:16:19,071  -->  01:16:22,911
right here let's open it.

938

01:16:29,311  -->  01:16:31,103
it's pgen test

939

01:16:57,727  -->  01:16:59,007
So

940

01:16:59,263  -->  01:17:01,823
Let's take a look on the drive side

941

01:17:02,335  -->  01:17:05,407
That is 2 drives

942

01:17:05,663  -->  01:17:07,967
conveyor and Ejector

943

01:17:10,527  -->  01:17:15,903
conveyor belt is attached with the drive

944

01:17:16,671  -->  01:17:20,255
measuring input lets create a new one

945

01:17:21,279  -->  01:17:22,303
Okay

946

01:17:26,655  -->  01:17:31,519
The drive related measuring input

947

01:17:31,775  -->  01:17:37,663
When you select Global measuring input you have to assign an input

948

01:17:38,431  -->  01:17:39,455
AS Global

949

01:17:39,967  -->  01:17:45,599
When you selected drive related you just answered the number of measuring input

950

01:17:45,855  -->  01:17:47,135
Because

951

01:17:47,647  -->  01:17:50,975
It will be already taken via message frame

952

01:17:55,071  -->  01:18:00,703
localmeasuring input are axis related and mainly implemented in Drive

953

01:18:01,471  -->  01:18:05,311
The number one or number two of measuring input

954

01:18:05,823  -->  01:18:11,967
Use as well as the number of encoder system of 3 and go to create

955

01:18:13,247  -->  01:18:19,391
The assignment of measuring input actually use drive is realized

956

01:18:19,647  -->  01:18:22,719
assigned drive IO

957

01:18:22,975  -->  01:18:26,559
Parameter 488

958

01:18:26,815  -->  01:18:29,375
On the drive

959

01:18:33,983  -->  01:18:35,519
Right here

960

01:18:40,639  -->  01:18:42,175
488

961

01:18:43,199  -->  01:18:46,527
Hey did you see hear the measuring input 1

962

01:18:46,783  -->  01:18:48,319
and 2

963

01:18:49,599  -->  01:18:53,183
The encoder 1-2-3

964

01:18:54,207  -->  01:18:57,791
Then you have to assign your digital input

965

01:18:58,559  -->  01:19:00,607
Of the control units

966

01:19:01,119  -->  01:19:04,191
Terminal connection for instance

967

01:19:05,983  -->  01:19:12,127
If you remember I told you before the bidirectional configurable

968

01:19:12,383  -->  01:19:16,223
Digital input output terminals or

969

01:19:16,479  -->  01:19:17,759
Fast

970

01:19:18,271  -->  01:19:24,415
And used for measuring input and cam outputs so if you want to use

971

01:19:25,695  -->  01:19:27,487
Digital input 8

972

01:19:27,743  -->  01:19:30,303
Then you have to say that here

973

01:19:33,887  -->  01:19:35,167
For instance

974

01:19:36,191  -->  01:19:38,751
You have to go

975

01:19:44,127  -->  01:19:50,271
to your control unit input and outputs to find the bidirection of IOs

976

01:19:54,623  -->  01:19:58,463
Then you have to change the setting

977

01:19:59,743  -->  01:20:01,791
For digital input 8

978

01:20:06,655  -->  01:20:10,751
Right now is input okay if you create you switch to output

979

01:20:12,287  -->  01:20:15,104
Then you can here connect

980

01:20:17,152  -->  01:20:18,944
Something

981

01:20:23,552  -->  01:20:25,088
Okay

982

01:20:36,352  -->  01:20:42,496
For the correction stamp here. Are data transferred dead times or filter smoothing times

983

01:20:42,752  -->  01:20:46,336
measuring input can be compensated

984

01:20:47,872  -->  01:20:51,968
The enter is significant for global measurement

985

01:20:54,528  -->  01:20:58,880
because simotion calculates everything

986

01:20:59,136  -->  01:21:02,208
Maybe there's some delay on your bus system

987

01:21:04,000  -->  01:21:09,888
So at this case I think drive related local music input

988

01:21:10,400  -->  01:21:13,728
Works faster than the global mission inputs

989

01:21:18,592  -->  01:21:24,736
monitoring actual status if the checkbox is activated short pulses are suppressed

990

01:21:24,992  -->  01:21:31,136
If the input is activated and if under edge

991

01:21:31,392  -->  01:21:37,536
rising Edge was selected result is only signaled if the measuring input

992

01:21:37,792  -->  01:21:39,840
had a State of one

993

01:21:40,352  -->  01:21:46,496
 for a min 1 basic cycle servo cycle

994

01:21:47,520  -->  01:21:49,824
here current status

995

01:21:56,480  -->  01:21:58,528
mointor current status

996

01:22:00,576  -->  01:22:02,880
Is preventing some

997

01:22:03,136  -->  01:22:03,904
clips

998

01:22:04,928  -->  01:22:07,744
Or you no disturbances

999

01:22:08,768  -->  01:22:14,912
Activation time of the measuring input range another setting

1000

01:22:23,616  -->  01:22:28,224
so Nice picture. What should we do on Drive side

1001

01:22:30,528  -->  01:22:34,624
For Activation time you can Define a measuring input range

1002

01:22:35,136  -->  01:22:37,952
For command distance could be

1003

01:22:38,464  -->  01:22:43,072
Restricted or unrestricted by start and end position

1004

01:22:43,328  -->  01:22:49,472
when axis reached to start position or range specific configuration

1005

01:22:49,728  -->  01:22:54,592
depend Transmission time is elapsed on measuring input is activated

1006

01:22:55,104  -->  01:23:01,248
and so on transmission time could be compensated by activation time

1007

01:23:02,272  -->  01:23:08,416
Which transmission type of profibus internal processing in drive system

1008

01:23:08,672  -->  01:23:14,816
Usually simotion will sent activation command  to the drive system

1009

01:23:15,072  -->  01:23:21,216
Before the axis has actually reached stop and position of the measuring range

1010

01:23:21,472  -->  01:23:24,800
This is also another deep note

1011

01:23:25,568  -->  01:23:29,152
For parameterizing on the driver side

1012

01:23:30,176  -->  01:23:33,760
measuring inputs 1 or 2 used

1013

01:23:34,016  -->  01:23:39,392
encoder system actual digital input driver parameters

1014

01:23:42,464  -->  01:23:45,536
You're just select from the drop-down list

1015

01:23:46,304  -->  01:23:52,192
terminal X122 or X132

1016

01:23:52,448  -->  01:23:55,264
The inputs connector

1017

01:23:55,776  -->  01:23:59,872
X142 only simotion can 

1018

01:24:00,384  -->  01:24:03,456
Used for Global measurements

1019

01:24:03,968  -->  01:24:05,504
Another deep note

1020

01:24:06,016  -->  01:24:08,064
And next page

1021

01:24:09,088  -->  01:24:15,232
Measuring input at simotion for Global measurement

1022

01:24:15,744  -->  01:24:17,536
And this case

1023

01:24:17,792  -->  01:24:20,096
First of all on the drive sites

1024

01:24:20,608  -->  01:24:26,752
You have to choose the

1025

01:24:27,776  -->  01:24:29,824
Input of control units

1026

01:24:31,616  -->  01:24:33,664
At this case

1027

01:24:34,176  -->  01:24:37,248
For controlled by simotion measuring input

1028

01:24:39,808  -->  01:24:42,368
And after that

1029

01:24:45,184  -->  01:24:47,232
At the second step

1030

01:24:49,792  -->  01:24:52,096
You will have to assign

1031

01:24:52,864  -->  01:24:55,424
In your measuring input configuration

1032

01:24:57,216  -->  01:25:00,288
You said a standard global measuring input

1033

01:25:00,800  -->  01:25:02,592
And you can easily

1034

01:25:02,848  -->  01:25:07,456
Go to control units and select your

1035

01:25:14,112  -->  01:25:19,488
free digital input so simotion will use Drive telegram 390 and automatically

1036

01:25:20,256  -->  01:25:26,400
Calculate adjusted telegrams between sinamics control unit and

1037

01:25:26,656  -->  01:25:31,008
simotion CPU and this is possible

1038

01:25:31,520  -->  01:25:34,848
After firmware version 4.2

1039

01:25:35,360  -->  01:25:38,944
With older versions you have to do it yourself

1040

01:25:39,200  -->  01:25:40,992
By manual

1041

01:25:45,600  -->  01:25:50,208
So you see your something's going on on the background

1042

01:25:51,232  -->  01:25:57,376
after compile when I go to

1043

01:25:57,888  -->  01:26:03,264
Communication site of sinamics and check what just happened

1044

01:26:04,288  -->  01:26:09,920
you will see here at the telegram configuration for control unit

1045

01:26:10,944  -->  01:26:15,808
Siemens telegram 391 is

1046

01:26:16,320  -->  01:26:17,600
Adjusted

1047

01:26:18,368  -->  01:26:22,208
If you want to go interconnections and Diagnostics

1048

01:26:26,816  -->  01:26:29,376
for transmit Direction

1049

01:26:30,656  -->  01:26:36,800
You see here an additional Central measuring probe parameter

1050

01:26:37,056  -->  01:26:38,080
is Attached

1051

01:26:39,104  -->  01:26:41,664
profidrive telegram

1052

01:26:41,920  -->  01:26:43,456
when i click

1053

01:26:43,968  -->  01:26:47,296
Status word of measuring input probes

1054

01:26:47,552  -->  01:26:51,392
You see here possible 8 probes there

1055

01:26:54,720  -->  01:26:58,816
So it is adjusted as automatically

1056

01:27:01,120  -->  01:27:05,216
And other possibility to use

1057

01:27:06,752  -->  01:27:08,800
X142

1058

01:27:09,824  -->  01:27:11,616
with simotion

1059

01:27:14,176  -->  01:27:15,712
Let's go there

1060

01:27:16,480  -->  01:27:19,040
You have to set it

1061

01:27:20,320  -->  01:27:21,856
Which way

1062

01:27:22,112  -->  01:27:24,672
Do you want to use your terminal connections

1063

01:27:27,232  -->  01:27:33,120
Digital input input output or output measuring input

1064

01:27:33,376  -->  01:27:39,264
you can define filtering time here 1 microsec

1065

01:27:40,800  -->  01:27:43,872
Your can invert here

1066

01:27:44,640  -->  01:27:48,224
Also that you can just select

1067

01:27:48,480  -->  01:27:52,832
Your input here as Global Inputs

1068

01:27:54,112  -->  01:27:57,184
Under your new device here

1069

01:27:59,744  -->  01:28:04,096
This is also another possibility

1070

01:28:09,984  -->  01:28:11,264
So...

1071

01:28:13,056  -->  01:28:15,104
It's looks like this

1072

01:28:19,968  -->  01:28:25,088
The correction time evaluate timestamp

1073

01:28:25,600  -->  01:28:30,464
In the real world sometimes it is necessary to calculate the timestamp

1074

01:28:30,720  -->  01:28:33,024
Because there's some delay

1075

01:28:33,536  -->  01:28:38,400
hardware delay times at measuring input can be taken from

1076

01:28:38,912  -->  01:28:40,448
Device manuals

1077

01:28:40,960  -->  01:28:47,104
Or values shorter than 125 microsec can neglected

1078

01:28:51,200  -->  01:28:56,832
hardware delay times with a positive sign

1079

01:28:58,624  -->  01:29:04,768
Measurements are performed it real axes done for this timestamp technique

1080

01:29:05,024  -->  01:29:11,168
Time TI must also be taken into account the time interval TI define time

1081

01:29:11,424  -->  01:29:17,568
Sometime before start of dp cycle which the drive system latch up

1082

01:29:17,824  -->  01:29:22,944
axis position to simotion

1083

01:29:23,456  -->  01:29:26,784
This time time must be answered with a negative sign

1084

01:29:28,576  -->  01:29:33,696
So when you said I drive related later than you have to

1085

01:29:33,952  -->  01:29:38,048
You should answer here correction values as minus

1086

01:29:39,072  -->  01:29:40,608
For instance

1087

01:29:41,632  -->  01:29:43,680
at our case

1088

01:29:43,936  -->  01:29:46,752
It's too low as Microsec

1089

01:29:50,848  -->  01:29:52,640
Maybe

1090

01:29:54,688  -->  01:29:57,248
Like this

1091

01:30:00,832  -->  01:30:06,976
And this page configure and measuring input monitoring a measuring input

1092

01:30:07,232  -->  01:30:08,000
so...

1093

01:30:13,120  -->  01:30:17,216
There's a third option here monitoring measuring inputs

1094

01:30:17,472  -->  01:30:19,520
Must be connected

1095

01:30:19,776  -->  01:30:23,616
to an original measuring input in interconnection

1096

01:30:41,536  -->  01:30:47,680
Interconnectable input interface of the technology object or listed following you can enter the interconnection

1097

01:30:47,936  -->  01:30:53,312
Output interface of other technology objects in the TO

1098

01:30:55,104  -->  01:30:58,176
For reference and Acceptance

1099

01:31:10,976  -->  01:31:12,768
at Project

1100

01:31:16,864  -->  01:31:20,192
Let's create another measuring input

1101

01:31:25,568  -->  01:31:27,104
It should be

1102

01:31:31,712  -->  01:31:34,528
Global measuring input

1103

01:31:38,624  -->  01:31:40,160
Okay

1104

01:31:40,672  -->  01:31:43,232
Describe another one

1105

01:31:45,792  -->  01:31:50,400
you will see here just monitoring measuring input

1106

01:31:52,448  -->  01:31:58,080
Actual value reference that are three options here with consideration of TI

1107

01:31:58,336  -->  01:31:59,616
Should be better

1108

01:32:02,176  -->  01:32:03,712
and...

1109

01:32:04,224  -->  01:32:07,040
In your interconnections

1110

01:32:07,552  -->  01:32:09,344
You have to select

1111

01:32:10,880  -->  01:32:16,768
It's already interconnected at your new device

1112

01:32:17,024  -->  01:32:19,072
measuring input 1 or 2

1113

01:32:19,328  -->  01:32:22,400
2 event transfer

1114

01:32:22,912  -->  01:32:24,960
So that's it

1115

01:32:38,784  -->  01:32:42,368
next page selected event transfer

1116

01:32:43,392  -->  01:32:46,464
monitoring meas Function

1117

01:32:48,256  -->  01:32:54,400
from version 4.0 using this function a global measuring input event

1118

01:32:54,656  -->  01:33:00,800
can also be Detected at the same time from several TO measuring inputs

1119

01:33:03,104  -->  01:33:05,408
evaluated For example

1120

01:33:05,664  -->  01:33:08,224
when an original measuring input have and effect

1121

01:33:12,832  -->  01:33:18,208
you can Snapshot several ext encoders or several axis at measuring input at the same time

1122

01:33:19,232  -->  01:33:24,352
This functionality is only possible with Global inputs

1123

01:33:30,496  -->  01:33:35,360
only these input Support necessary timestamp functionality

1124

01:33:36,640  -->  01:33:42,784
In the first step you should have the original to measuring input interconnected

1125

01:33:43,552  -->  01:33:49,696
is usual at this origin input the measuring operation is activated using commands

1126

01:33:51,744  -->  01:33:53,280
ok

1127

01:33:54,560  -->  01:34:00,704
Activation at deactivation commands are not executed

1128

01:34:02,496  -->  01:34:04,800
Or return with an error

1129

01:34:07,872  -->  01:34:11,200
You can just monitor this measuring input

1130

01:34:12,736  -->  01:34:18,880
In the Second Step additional to measuring inputs are configured as monitoring are interconnected

1131

01:34:19,136  -->  01:34:21,440
With the original TO

1132

01:34:21,952  -->  01:34:24,000
in event interconnection

1133

01:34:25,536  -->  01:34:27,584
uunder the entry event transfer

1134

01:34:31,168  -->  01:34:32,960
So we have already did

1135

01:34:34,752  -->  01:34:36,288
Some notes

1136

01:34:38,080  -->  01:34:44,224
Activating and deactivating measuring input process only possible original TO

1137

01:34:44,480  -->  01:34:45,248
ok

1138

01:34:46,528  -->  01:34:51,136
These comments are not effective monitoring measuring inputs

1139

01:34:51,392  -->  01:34:57,536
measuring input area and edge selection are only possible at origin TO yes

1140

01:34:58,560  -->  01:35:04,704
monitoring TO measuring input must have been correctly configured at instant

1141

01:35:04,960  -->  01:35:07,264
At the measurements

1142

01:35:08,032  -->  01:35:14,176
measuring input does not have its own inputs cannot perform measurement

1143

01:35:15,968  -->  01:35:16,992
Yes

1144

01:35:18,272  -->  01:35:24,416
The IPO cycles of the TO machine input on monitor to measure input can be different

1145

01:35:25,184  -->  01:35:28,768
This is done have a negative impact on accuracy

1146

01:35:29,536  -->  01:35:33,888
So this is very detailed information

1147

01:35:35,168  -->  01:35:39,264
In some rare cases you have to use this way

1148

01:35:41,568  -->  01:35:47,712
next page you see the to the calculate the activation time for measuring inputs

1149

01:35:47,968  -->  01:35:50,016
You can find the

1150

01:35:50,272  -->  01:35:52,576
Excel file in your

1151

01:35:52,832  -->  01:35:55,392
Application utilities folder

1152

01:35:56,416  -->  01:35:59,488
You have to fill the input

1153

01:36:00,000  -->  01:36:02,304
DP cycle as milliseconds

1154

01:36:02,560  -->  01:36:04,864
servo cycle IPO cycle

1155

01:36:05,632  -->  01:36:08,192
Processing cycle clock and edge type

1156

01:36:09,472  -->  01:36:10,496
and

1157

01:36:11,520  -->  01:36:15,360
time TO set point transfer in your Hardware configuration

1158

01:36:15,872  -->  01:36:19,200
As a result you will see here

1159

01:36:19,456  -->  01:36:22,016
measuring input range and activation time

1160

01:36:23,808  -->  01:36:29,952
Then you can answer this one as ms within your measuring input

1161

01:36:35,072  -->  01:36:36,352
Correction value

1162

01:36:37,376  -->  01:36:42,496
or Activation time for measuring range on the measuring inputs

1163

01:36:50,688  -->  01:36:52,480
So this one when use measuring range

1164

01:37:08,608  -->  01:37:14,752
For activating and deactivating measuring input commands that are

1165

01:37:16,800  -->  01:37:18,080
Activate

1166

01:37:18,336  -->  01:37:23,456
You're just select here axis or encoder related measuring input

1167

01:37:24,992  -->  01:37:30,368
Is possible to activate cyclic measuring or just once

1168

01:37:30,624  -->  01:37:36,256
You can take your Rising edge or falling edge or both ages

1169

01:37:36,768  -->  01:37:42,912
If you're setting activate measuring range as measuring in specific range you can define

1170

01:37:45,472  -->  01:37:50,080
range starts of a measuring range and end of a measuring range

1171

01:37:50,336  -->  01:37:53,920
Otherwise you just detect the

1172

01:37:54,176  -->  01:37:56,480
Edge of your sensor

1173

01:37:56,992  -->  01:38:01,344
And there is a comment for the deactivating measuring inputs

1174

01:38:04,160  -->  01:38:10,304
With this, you just select your axes encoder and the related

1175

01:38:10,816  -->  01:38:12,352
measuring inputs

1176

01:38:19,264  -->  01:38:25,152
so when measuring input events received the measuring input position is saved in the system variable

1177

01:38:25,408  -->  01:38:27,456
of measuring input

1178

01:38:29,248  -->  01:38:35,136
You see here at the state variable trigger occured

1179

01:38:35,904  -->  01:38:40,768
You should using wizard

1180

01:38:41,536  -->  01:38:46,144
settings for range

1181

01:38:50,496  -->  01:38:52,800
If you select

1182

01:38:53,056  -->  01:38:57,152
activate measuring input range and only Rising edges

1183

01:39:06,368  -->  01:39:10,208
The state variable is set to trigger occured

1184

01:39:10,464  -->  01:39:13,536
 first measuring input value is acquired

1185

01:39:13,792  -->  01:39:19,936
Additionally each new measuring input event could be result from a system variable actual input step

1186

01:39:21,216  -->  01:39:21,984
Because

1187

01:39:23,008  -->  01:39:27,360
For the second and third even is not possible to

1188

01:39:28,384  -->  01:39:31,200
I understand from the state variable

1189

01:39:31,712  -->  01:39:35,552
You have to look at the actual infostud as level

1190

01:39:37,600  -->  01:39:38,880
It's

1191

01:39:39,392  -->  01:39:42,976
can set to be positive or negative

1192

01:39:43,744  -->  01:39:49,888
after a Successful measurement performed it was saved to system variables

1193

01:39:52,448  -->  01:39:58,592
these are linked with counter variable about 1 and 2

1194

01:40:01,664  -->  01:40:06,016
Automatically incremented at each measurement entry

1195

01:40:07,552  -->  01:40:13,696
Measurement task is active until it's terminated using deactivate measuring input command

1196

01:40:13,952  -->  01:40:16,512
So...

1197

01:40:17,024  -->  01:40:23,168
You have to make an array or some buffer to get the values

1198

01:40:23,424  -->  01:40:29,312
When you're using active cyclic measuring because

1199

01:40:29,568  -->  01:40:33,920
For the next cycle for the second edge Rising Edge

1200

01:40:35,200  -->  01:40:40,832
overwritten values

1201

01:40:41,344  -->  01:40:43,648
If you don't want to miss

1202

01:40:44,160  -->  01:40:49,024
you have to make your own program to detect

1203

01:40:49,792  -->  01:40:51,584
The values cyclically

1204

01:40:54,912  -->  01:40:59,776
Next page synchronizing measuring system

1205

01:41:00,288  -->  01:41:02,592
the 3rd command for measuring input

1206

01:41:02,848  -->  01:41:05,408
You just said it to your axes

1207

01:41:07,200  -->  01:41:12,832
and you will select here number of measuring system to be synchronized

1208

01:41:14,624  -->  01:41:18,720
You can use current measuring input system as reference

1209

01:41:21,536  -->  01:41:26,400
Then you enter here differential variable

1210

01:41:28,960  -->  01:41:35,104
For using this command 2 measuring systems can be synchronized with one another

1211

01:41:37,408  -->  01:41:43,552
Or difference of specified measuring system results read out and saved with new user varible

1212

01:41:44,064  -->  01:41:50,208
during sync is only possible to change the value of measuring input system if it's

1213

01:41:50,464  -->  01:41:53,280
not currently used for position control

1214

01:41:57,120  -->  01:42:03,264
That means maybe the other system should be not enabled and standstill

1215

01:42:12,224  -->  01:42:17,856
it's Rarely used but sometimes you need this kind of functionality

1216

01:42:19,392  -->  01:42:20,672
So...

1217

01:42:25,024  -->  01:42:30,656
Next topic output cam control application

1218

01:42:31,424  -->  01:42:36,800
You'll see here at external encoder detecting actually of

1219

01:42:38,592  -->  01:42:44,736
Running material Metal Sheets or cartoon for example and there are four different type

1220

01:42:44,992  -->  01:42:46,528
of gluers

1221

01:42:47,040  -->  01:42:49,088
we want to

1222

01:42:49,600  -->  01:42:51,392
Make it glue tracks

1223

01:42:53,696  -->  01:42:57,024
Glue should be applied to wooden boards

1224

01:42:57,280  -->  01:42:58,304
For instance

1225

01:42:58,816  -->  01:43:01,888
controller based simotion

1226

01:43:04,704  -->  01:43:10,848
Shows cams for output cams like this

1227

01:43:12,640  -->  01:43:14,432
Four controller side

1228

01:43:16,224  -->  01:43:19,808
Does a 8 high speed output cams on board

1229

01:43:21,088  -->  01:43:24,416
conventional DP slave

1230

01:43:26,976  -->  01:43:33,120
4 drive based simotion there are 8 high speed output cams on board

1231

01:43:38,752  -->  01:43:40,032
Yep

1232

01:43:44,128  -->  01:43:50,272
high speed output cams can be following digital outputs...

1233

01:43:51,552  -->  01:43:53,088
you will see here

1234

01:44:00,768  -->  01:44:05,888
output cam types can be position based cam

1235

01:44:06,144  -->  01:44:09,728
time based cam or unidirectional output cam

1236

01:44:10,240  -->  01:44:13,568
According to access actual position

1237

01:44:18,688  -->  01:44:24,832
how do we configure a output cam and insert an output

1238

01:44:25,088  -->  01:44:29,184
in your Configuration you select cycle clock

1239

01:44:30,208  -->  01:44:33,280
default IPO can to change type

1240

01:44:33,536  -->  01:44:35,584
That case acm is time-based

1241

01:44:36,352  -->  01:44:41,216
set points or actual points

1242

01:44:42,240  -->  01:44:46,080
then you can activate the output than

1243

01:44:46,336  -->  01:44:51,712
Connect the cam output to a real hard wire digital output

1244

01:44:52,992  -->  01:44:59,136
or fast digital output or standard digital output is possible

1245

01:45:01,440  -->  01:45:06,816
You can just set it

1246

01:45:07,584  -->  01:45:08,864
linking output cams to logical OR AND gate

1247

01:45:09,632  -->  01:45:13,728
hard gate maybe. So lets see...

1248

01:45:14,240  -->  01:45:15,008
for

1249

01:45:17,056  -->  01:45:19,360
here

1250

01:45:23,968  -->  01:45:25,504
So let's see

1251

01:45:28,064  -->  01:45:32,160
in IPO config

1252

01:45:32,416  -->  01:45:36,512
IPO position Based cam

1253

01:45:37,792  -->  01:45:40,352
Type of output cam values can be

1254

01:45:40,608  -->  01:45:43,424
also actual value of axis

1255

01:45:44,192  -->  01:45:46,240
Set point reference

1256

01:45:47,776  -->  01:45:52,896
set point interpolator set point on Drive

1257

01:45:53,152  -->  01:45:59,296
Before the fine point interpreter that are so minor changes but it depends

1258

01:45:59,552  -->  01:46:01,856
On your application

1259

01:46:02,368  -->  01:46:05,440
for gluer or maybe it's not so important

1260

01:46:06,208  -->  01:46:08,768
What when you're cutting some glass

1261

01:46:09,024  -->  01:46:13,632
Is micromilimeters are this is important so maybe you should select the

1262

01:46:13,888  -->  01:46:16,192
reference to set point on the drive

1263

01:46:17,984  -->  01:46:20,032
You have to test it

1264

01:46:20,800  -->  01:46:24,640
After you activate the output there are three choices

1265

01:46:26,688  -->  01:46:29,760
So logical AND

1266

01:46:31,296  -->  01:46:33,856
logical or

1267

01:46:34,112  -->  01:46:36,416
You have to assign the output

1268

01:46:36,928  -->  01:46:41,024
it can be cam output is here

1269

01:46:41,280  -->  01:46:45,888
Or the standard output here this is the fast output

1270

01:46:46,912  -->  01:46:48,960
So...

1271

01:47:00,224  -->  01:47:06,368
Logical operation if several output cams are switched to the same output using two logical

1272

01:47:06,624  -->  01:47:09,696
Operation parameter example

1273

01:47:09,952  -->  01:47:11,744
and gates

1274

01:47:12,000  -->  01:47:18,144
Or gate so that means if I insert a additional output cam 2

1275

01:47:22,752  -->  01:47:27,360
Then I considered the same output for this job

1276

01:47:27,616  -->  01:47:29,664
With different configuration

1277

01:47:33,248  -->  01:47:35,040
After I actiavte with output

1278

01:47:35,296  -->  01:47:37,344
i can select the same output

1279

01:47:38,112  -->  01:47:39,904
This one

1280

01:47:40,160  -->  01:47:45,280
It's possible that when I select logical AND

1281

01:47:46,560  -->  01:47:52,704
Two outputs must be logic level high

1282

01:47:52,960  -->  01:47:54,752
set the real output to

1283

01:47:55,008  -->  01:47:56,800
Logic level high

1284

01:48:00,128  -->  01:48:04,992
when I've changed here it's been automatically

1285

01:48:05,760  -->  01:48:07,808
I have to do as manual

1286

01:48:10,368  -->  01:48:13,952
So you can configure your system

1287

01:48:14,208  -->  01:48:16,768
Depending on your requirements

1288

01:48:18,048  -->  01:48:22,144
lets compile

1289

01:48:36,992  -->  01:48:43,136
Of course over years technology objects developed

1290

01:48:43,392  -->  01:48:44,416
and

1291

01:48:44,672  -->  01:48:50,304
Getting advance and Advance day by day with new firmware versions

1292

01:48:50,560  -->  01:48:52,352
At the beginning

1293

01:48:52,608  -->  01:48:53,632
Maybe

1294

01:48:53,888  -->  01:48:57,984
It was not so complicated but by the time passing

1295

01:48:58,496  -->  01:49:04,640
According to customer an application needs and requirements

1296

01:49:05,152  -->  01:49:08,992
Research and development team

1297

01:49:10,528  -->  01:49:11,808
Is

1298

01:49:12,320  -->  01:49:15,136
added some new features so...

1299

01:49:15,904  -->  01:49:21,792
These days there are so many possibilities you have to just select

1300

01:49:22,816  -->  01:49:25,632
which feature 

1301

01:49:26,400  -->  01:49:27,424
you need

1302

01:49:29,728  -->  01:49:35,872
So high speed output cams for simotion we'll select here cam output

1303

01:49:37,664  -->  01:49:43,040
You can write here TM timer or terminal modules

1304

01:49:44,576  -->  01:49:46,112
it is possible

1305

01:49:48,160  -->  01:49:49,952
It should be

1306

01:49:50,208  -->  01:49:51,488
cam output

1307

01:49:52,000  -->  01:49:54,560
According to choice

1308

01:49:54,816  -->  01:49:59,168
It should be the cam output it's not standard digital output

1309

01:50:01,216  -->  01:50:03,776
Yep

1310

01:50:06,592  -->  01:50:11,200
You can see here in already to do this steps

1311

01:50:12,992  -->  01:50:16,064
After that we have to download the project

1312

01:50:17,600  -->  01:50:21,696
when you select fast digital output

1313

01:50:22,976  -->  01:50:28,608
Then you're going to use your sinamics based outputs

1314

01:50:29,120  -->  01:50:31,168
Settings

1315

01:50:33,216  -->  01:50:33,984
First

1316

01:50:34,752  -->  01:50:39,104
The output of the control unit in sinamics integrated

1317

01:50:40,640  -->  01:50:42,944
On bidirectional tab

1318

01:50:50,368  -->  01:50:51,648
you can choose

1319

01:50:52,160  -->  01:50:54,208
For instance this one

1320

01:50:56,000  -->  01:50:58,560
Output as output

1321

01:50:58,816  -->  01:51:03,168
And it will be used by simotion as digital output

1322

01:51:04,960  -->  01:51:06,496
Digital output

1323

01:51:07,776  -->  01:51:09,312
Okay

1324

01:51:11,872  -->  01:51:14,944
It's really fast digital outputs

1325

01:51:22,368  -->  01:51:28,512
from firmware version 4.2 and higher this configuration is automatically executed as I said

1326

01:51:29,280  -->  01:51:33,120
High-speed onboard output cams initially

1327

01:51:33,376  -->  01:51:34,656
require high speed

1328

01:51:34,912  -->  01:51:37,984
bidirectional designs

1329

01:51:39,008  -->  01:51:40,544
ok

1330

01:51:45,152  -->  01:51:47,200
then we just go

1331

01:51:48,736  -->  01:51:53,344
In our output cam section and select first digital output

1332

01:51:53,600  -->  01:51:57,184
assigned interface is the wrong pipe

1333

01:51:58,464  -->  01:52:02,560
Yes I know I have changed

1334

01:52:05,120  -->  01:52:08,448
Then I have to save first

1335

01:52:08,704  -->  01:52:11,776
That maybe I can sell it from the list

1336

01:52:14,080  -->  01:52:20,224
Not possible okay let's say save and compile

1337

01:52:24,576  -->  01:52:28,672
I think the hardware telegram is updated

1338

01:52:30,976  -->  01:52:35,840
Or you can you set up communication for symbolic assignment again

1339

01:52:37,120  -->  01:52:42,752
Alignment of the drive to Hardware config updated fast IO relationships

1340

01:52:43,008  -->  01:52:46,336
Or here that is a function

1341

01:52:47,360  -->  01:52:49,152
for fast IO

1342

01:52:50,176  -->  01:52:54,272
Create new configuration or delete new configuration is related with this topic

1343

01:52:57,344  -->  01:52:59,392
After that I will try again

1344

01:53:05,536  -->  01:53:07,840
It's not possible

1345

01:53:15,264  -->  01:53:20,640
So let's try another one

1346

01:53:25,248  -->  01:53:29,344
output cams

1347

01:53:32,416  -->  01:53:38,560
Position Based cam setpoints reference points activate outputs

1348

01:53:52,384  -->  01:53:55,712
At the control units

1349

01:53:58,272  -->  01:54:00,320
new device

1350

01:54:01,088  -->  01:54:02,624
This should be the

1351

01:54:03,136  -->  01:54:04,928
cam output

1352

01:54:24,896  -->  01:54:26,688
i will select logical OR

1353

01:54:28,224  -->  01:54:30,784
So I couldn't see

1354

01:54:33,088  -->  01:54:34,880
Let's try again

1355

01:54:36,160  -->  01:54:38,720
Fast IO create new configuration

1356

01:54:41,280  -->  01:54:46,912
Still not visible

1357

01:54:54,592  -->  01:54:58,944
Read the following expected for another assignment on sinamics drive

1358

01:55:00,736  -->  01:55:06,112
sinamics inputs as outputs

1359

01:55:06,880  -->  01:55:11,744
simotion is inputs listed by continue

1360

01:55:12,256  -->  01:55:15,584
Message frames 390 up to

1361

01:55:15,840  -->  01:55:17,120
Up to 2 measuring inputs

1362

01:55:17,376  -->  01:55:19,936
 outputs

1363

01:55:21,216  -->  01:55:23,008
save compile

1364

01:55:23,520  -->  01:55:25,056
step number 3

1365

01:55:27,872  -->  01:55:29,152
Okay

1366

01:55:30,176  -->  01:55:33,248
Let's save and compile sinamics side

1367

01:55:36,832  -->  01:55:39,136
create procedure is successful

1368

01:55:45,024  -->  01:55:48,096
lets say

1369

01:55:50,400  -->  01:55:55,008
save and recompile all yes

1370

01:56:10,112  -->  01:56:14,208
fast IO telegrams notes sinamics integrated updated

1371

01:56:16,000  -->  01:56:18,048
Okay

1372

01:56:22,912  -->  01:56:29,056
So it's not possible that I have to use standard digital output

1373

01:56:30,592  -->  01:56:33,664
Then I considered my digital outputs

1374

01:56:35,200  -->  01:56:41,344
I think there's something changed during firmware versions

1375

01:56:41,600  -->  01:56:45,184
That's why is the lecture notes

1376

01:56:45,696  -->  01:56:47,232
are not consistent

1377

01:56:50,304  -->  01:56:56,448
here you can see also the output cam or normal output

1378

01:56:56,960  -->  01:57:00,032
These are really fast output cams

1379

01:57:03,616  -->  01:57:06,432
So

1380

01:57:12,320  -->  01:57:14,880
in telegram settings

1381

01:57:16,672  -->  01:57:19,488
It should be automatically adopted

1382

01:57:20,256  -->  01:57:23,328
for Terminal Port I'm not using terminal board.

1383

01:57:25,120  -->  01:57:26,400
Yes

1384

01:57:40,480  -->  01:57:43,808
Okay

1385

01:57:46,880  -->  01:57:52,000
next page activating the output cam in the user program

1386

01:57:55,584  -->  01:57:59,168
you select here axis encoder and output cam

1387

01:57:59,936  -->  01:58:05,312
You just answer here in parameter section start position and position

1388

01:58:05,824  -->  01:58:11,968
So it's a position based you can enter here minus or plus activation time

1389

01:58:14,016  -->  01:58:15,040
hysteresis

1390

01:58:15,552  -->  01:58:20,672
Sometimes the actual encoder value maybe

1391

01:58:21,952  -->  01:58:25,536
Is the opposite direction

1392

01:58:26,560  -->  01:58:32,704
Then you can just here deadbands you don't want to go

1393

01:58:32,960  -->  01:58:38,592
Your encoder high-level and low-level you don't want to blink at your output

1394

01:58:39,616  -->  01:58:42,176
And effective Direction

1395

01:58:42,432  -->  01:58:43,712
you can set

1396

01:58:44,224  -->  01:58:47,296
Then you're output is set only

1397

01:58:48,064  -->  01:58:52,416
Your access is rotated in positive direction 

1398

01:58:53,440  -->  01:58:59,584
If you use here invert your output its digital output is inverted

1399

01:58:59,840  -->  01:59:02,144
You can set a cam counter

1400

01:59:03,168  -->  01:59:06,240
For counting by technology object

1401

01:59:07,008  -->  01:59:09,056
it stored in a system variable here

1402

01:59:09,568  -->  01:59:13,152
we may see

1403

01:59:15,200  -->  01:59:17,248
tech object

1404

01:59:25,184  -->  01:59:28,256
output cam

1405

01:59:28,512  -->  01:59:30,560
control active / reactive

1406

01:59:31,584  -->  01:59:33,120
and

1407

01:59:34,656  -->  01:59:39,776
effective data cam data start value...

1408

01:59:40,544  -->  01:59:43,872
Current account and starting count

1409

01:59:45,408  -->  01:59:51,040
as parameter effective data, activation time is everything is there

1410

01:59:55,392  -->  02:00:00,000
You can read your return States is an on / off

1411

02:00:04,096  -->  02:00:10,240
So you just use here to

1412

02:00:10,496  -->  02:00:16,128
Switch output cam off comments and select axis encoder and related cam

1413

02:00:17,152  -->  02:00:20,992
If your click output cam set to  permanently on

1414

02:00:26,112  -->  02:00:32,256
If assign output cam should remain permanently on after has been disabled 

1415

02:00:32,512  -->  02:00:34,816
check box it is not activated.

1416

02:00:36,608  -->  02:00:40,192
disabled output cam.

1417

02:00:40,960  -->  02:00:42,752
Sometimes you need it

1418

02:00:45,568  -->  02:00:51,712
Setting at high speed cam from user program switch output cam 

1419

02:00:51,968  -->  02:00:53,504
signal

1420

02:00:55,040  -->  02:00:58,368
type Offset and cam status

1421

02:00:59,392  -->  02:01:05,536
command is available from version 4.1 and higher of simotion

1422

02:01:05,792  -->  02:01:09,376
command allow you switch output cam on or off

1423

02:01:10,656  -->  02:01:12,448
On or off

1424

02:01:12,704  -->  02:01:17,568
The output cam signal is available in a system variable state

1425

02:01:19,360  -->  02:01:24,480
Set the digital output this terminates cam processing was started

1426

02:01:25,504  -->  02:01:28,064
overwrite cam command

1427

02:01:29,088  -->  02:01:33,184
Is the output cam configured with a high speed of cam

1428

02:01:34,720  -->  02:01:36,512
The following applies

1429

02:01:37,024  -->  02:01:41,888
assign digital output precise times during

1430

02:01:42,400  -->  02:01:44,448
Cycle clokc of output cam

1431

02:01:44,960  -->  02:01:51,104
The type depend output relay.

1432

02:01:51,360  -->  02:01:57,504
Just use this switch output your signal to test the altered really is

1433

02:01:57,760  -->  02:01:59,040
Working or not

1434

02:02:01,088  -->  02:02:06,720
On the other hand you can use to set for time off set during

1435

02:02:07,232  -->  02:02:09,792
cam on command still processing

1436

02:02:12,864  -->  02:02:17,216
configuring TO output cam track

1437

02:02:18,752  -->  02:02:23,872
Is the next type of output cam

1438

02:02:32,064  -->  02:02:35,392
You can configure a cam track. first position or time based

1439

02:02:36,416  -->  02:02:40,256
Type of cam should set point or actual value

1440

02:02:41,792  -->  02:02:47,936
leave non cyclic activated cam track outside of track range...

1441

02:02:49,472  -->  02:02:50,240
Yep

1442

02:02:51,008  -->  02:02:56,896
Does an expert this similar to cam type that are some default parameters

1443

02:02:57,152  -->  02:03:03,296
when you use cam on cam off

1444

02:03:03,552  -->  02:03:05,344
I'm going to describe your

1445

02:03:06,112  -->  02:03:12,256
output cam data to start position and position as a table

1446

02:03:12,512  -->  02:03:17,120
32 different values

1447

02:03:17,376  -->  02:03:18,912
Cam table

1448

02:03:19,168  -->  02:03:20,448
is possible

1449

02:03:21,728  -->  02:03:27,872
If you're using the scope you can see here usually for single cam settings

1450

02:03:28,896  -->  02:03:32,992
array and validity start position and end position

1451

02:03:47,328  -->  02:03:50,400
so... At the first segment here

1452

02:03:51,168  -->  02:03:53,728
track data You can just select activation mode

1453

02:03:53,984  -->  02:03:57,056
cyclic cam track or non-cyclic cam track.

1454

02:03:59,104  -->  02:04:02,432
start mode stop mode

1455

02:04:02,944  -->  02:04:07,296
 you can set us with a track length

1456

02:04:07,808  -->  02:04:12,416
And axis reference position activation duration time

1457

02:04:12,672  -->  02:04:14,976
Hysteresis

1458

02:04:15,232  -->  02:04:19,840
You can just make a train and track data

1459

02:04:20,352  -->  02:04:24,192
For glue application with this way

1460

02:04:32,384  -->  02:04:37,760
You can enter some position here or output cam data TO

1461

02:04:38,016  -->  02:04:44,160
You can use this table also with conventional flywheel presses for electrical

1462

02:04:44,416  -->  02:04:50,560
cam outputs instead of mechanical cam discs for example

1463

02:04:50,816  -->  02:04:52,352
with high speed cam outputs Of course

1464

02:04:55,424  -->  02:05:00,544
You can just enable or disable from here on the scope

1465

02:05:08,480  -->  02:05:14,624
The last two comments or enabling and disabling for the output cam track.

1466

02:05:23,328  -->  02:05:25,120
So...

1467

02:05:25,376  -->  02:05:31,520
So far so good I think this chapter was a little bit therocal.

1468

02:05:34,848  -->  02:05:40,992
but as basically we have talked about almost

1469

02:05:41,248  -->  02:05:42,272
all of the

1470

02:05:42,528  -->  02:05:44,832
technology Objects right now

1471

02:05:45,088  -->  02:05:48,160
So it makes chapter

1472

02:05:48,416  -->  02:05:52,256
camming and gearing we will do

1473

02:05:52,512  -->  02:05:58,656
Some exercises and examples related to this topics

1474

02:05:58,912  -->  02:06:02,496
here It's important for you to understand the main logic

1475

02:06:02,752  -->  02:06:06,080
What's the measuring input and what's the cam output?

1476

02:06:06,336  -->  02:06:12,480
How do you counter a program or application here you can use cam tracks

1477

02:06:12,736  -->  02:06:14,528
For this application

1478

02:06:15,808  -->  02:06:18,368
when there is a cycle or pattern

1479

02:06:18,624  -->  02:06:23,744
You can program here in the table so that way we technology objects

1480

02:06:26,048  -->  02:06:32,192
no matter your Hardware is you can just use controller-based Siemens products

1481

02:06:32,448  -->  02:06:33,728
simotion

1482

02:06:33,984  -->  02:06:35,264
siemens drives

1483

02:06:35,776  -->  02:06:39,616
It's written scalable and flexible solution

1484

02:06:40,896  -->  02:06:44,224
The hardware is not so important

1485

02:06:45,760  -->  02:06:51,904
You can just easily configure in your system

1486

02:06:52,416  -->  02:06:56,256
with Scout and for the program site

1487

02:06:58,048  -->  02:07:01,120
It takes less time

1488

02:07:01,376  -->  02:07:05,216
It's easy to program in MCC

1489

02:07:11,616  -->  02:07:14,944
You can just use some

1490

02:07:15,200  -->  02:07:19,552
Comments from your table

1491

02:07:20,832  -->  02:07:24,160
Ready-to-use

1492

02:07:28,768  -->  02:07:30,304
At this case

1493

02:07:32,352  -->  02:07:35,424
You'll see here commands for external encoder

1494

02:07:35,680  -->  02:07:37,984
measuring input

1495

02:07:39,264  -->  02:07:41,056
cam output on off

1496

02:07:41,824  -->  02:07:43,872
cam output on

1497

02:07:46,688  -->  02:07:48,736
You're just select here

1498

02:07:49,248  -->  02:07:51,552
As described in

1499

02:07:52,064  -->  02:07:53,856
Lecture notes

1500

02:07:55,904  -->  02:07:58,464
axis and cam

1501

02:07:59,488  -->  02:08:02,816
You can create another job

1502

02:08:03,328  -->  02:08:06,400
enter parameters or leave it as default

1503

02:08:10,752  -->  02:08:12,800
You can write your own logic

1504

02:08:17,408  -->  02:08:22,272
You can use the system variables here

1505

02:08:22,528  -->  02:08:26,880
to Create your structure for program control statements

1506

02:08:28,928  -->  02:08:31,232
Everything is up to you

1507

02:08:31,744  -->  02:08:33,024
So...

1508

02:08:33,792  -->  02:08:36,352
That's all guys

1509

02:08:37,120  -->  02:08:39,680
This is the end of this chapter

1510

02:08:39,936  -->  02:08:45,568
We're completed sync operation gearing and camming

1511

02:08:52,992  -->  02:08:57,600
a little bit it Is related with this chapter

1512

02:08:58,880  -->  02:09:04,768
Next chapter continue with gearring and camming

1513

02:09:05,024  -->  02:09:09,376
cam editor creating cam disks and so on...

1514

02:09:09,632  -->  02:09:11,680
See you next time.