welcome my friends 2
Another day another topic 3
current chapter is 28 4
and topic is camming in simotion 5
with camming functions you are able to do different 6
application 7
So let's start 8
On the contents of this topic are 9
camming difference between gearing and camming 10
making assignment the leading axis and cams 11
Default settings 12
Master 13
And slave relationship 14
non-cyclic and cyclic processing of cam 15
Enable disable offset 16
Reference point selection for synchronization 17
Set master point set scaling on Camming 18
There are some examples in notes 19
Monitoring functions during sync operation 20
sync with velocity reduction 21
Reporting a sync Operation error to leading access and so on... 22
let's start 23
It's the first page you see here 24
The relationship 25
Of the sync operation to there's a master value there is a slave value 26
classical gearing function in simotion 27
here the additional cam profiles to 28
calculate The gear ratio time to time in IPO cycle 29
Let's say our current gear ratio is 30
Related to this profile 31
will create an access with synchronous operation it is required 32
to do Cam operation 33
After that we make an assignment to leading axis select the set point or actual value 34
How we have to set it? 35
cams and interconnect them to sync operation 36
Let's say 37
At the last example i will Switch back to scout site 38
You'll see here a MCC program for Axis Blue 39
Axis Blue is our Master access at this case 40
And let's say axis red 41
axis red is our slave axis 42
Before I go and use 43
camming function in interconnection 44
I have to say 45
Which are possible cams 46
Interconnected 47
by Scout let's say 1 2 3 48
I'm in runtime I can say I'm going to use the cam 2 49
with cam on function later on 50
So 51
Next page 52
Settings for sync Operation are the same 53
Default settings are camming 54
direction Master mode slave mode cam mode and the starting point 55
cam for relative camming 56
For enable camming I need to use cam on 57
And after that cam off function 58
Let's go back to our 59
Axis red control MCC program and insert our function here 60
cam on 61
our slave or following axis is blue sync of operation is this 62
Our Master is cam red 63
use cam 1 cam direction 64
Should be positive 65
evaluation of leading axis let's say relative 66
and following axis relative processing 67
cam processing Just for one cycle 68
And after that 69
i should enter parameters for sync phase 70
Reference to the time 71
Or leading aksis 72
For the camming 73
It's commonly used by leading axis is because we don't want to 74
make A strange behavior on the slave 75
You have to think about 76
2 axes or independently rotatable but 77
There's an imaginable a 78
Camshaft or some mechanical Part between two axes 79
If you want to 80
Run 81
Both of your axes with cam I think you should use sync with 82
position based 83
and standart of 84
Synchronization 85
maybe should be sync immediately 86
And after that I have to end of the length 87
Starting point for relative camming it is position dependent 88
For the first time practice let's select time based sync. 89
And the starting point 90
should be zero maybe. 91
Direction... 92
Maintain direction of following axes 93
lets say it is positive 94
and when i select time 95
i have to enter dynamics response 96
This the higher velocity is possible 97
It's smooth 98
i will enter constant values 99
okay velocity maybe 15 100
And this is the information message 101
The cam one is answered as possible Master set point 102
in the configuration 103
of axis blue operation 104
So I should set up the cam as my slave axis 105
Who is my master? axis blue 106
okay it was 107
editor message with the new version of scout 108
At the background interconnections are made by automatic 109
I'm int the settings for the older versions We have to do it by manual 110
ourselves 111
So I need to use another available for cam on 112
GBO CAM ON 113
In my program red axis control 114
red axis is controlled and cam on 115
and for 116
Next Step 117
Why would you cam off function? 118
following axis is red 119
sync reference maybe time based again 120
And position immediately 121
It's possible to use following axis value 122
then you need to enter the reference points for the sync 123
and following axis position 124
You may select at end of the cam cycle 125
Maintain the direction od following axis the same way 126
reference Point for the desync position 127
You'll set here the dynamic response because we're setting time 128
Maybe it's a little bit higher velocity 129
smooth profile same constant value 130
And okay 131
Another if branch 132
with cam off bit 133
there are some 134
Error message about 135
type conflict expression example of position reference 136
real to ENUM is not possible 137
When I double-clicked I couldn't see the location because MCC is already open then 138
close And click again 139
Maybe no not possible again 140
Then I have to go to right click the MCC unit organized 141
compile it again and see the same message after I double click 142
I'm able to go to location of the error 143
sync of position reference should be ENUM 144
Let's say after sync position 145
Let's continiue with notes 146
I don't use delay program execution at this case just for testing 147
so evaluation a master and slave as absolute 148
non cyclic processing that means only one profile will be executed 149
Absolute camming for both sides it depends on the 150
axis zero points at the current action position value of 151
Both of axes 152
This is the start and end point for sync 153
You'll see here length of sync given by user 154
green curve 155
These are cam profile 156
And the red curve is actual slave position 157
we assumed right now our master 158
velocity is constant and our master 159
Position 160
it's Rising 161
as you can see Start of synchronization parameters selected at leading axis position 162
Let's say 163
at here some point 164
Because the reference point from sync position selected 165
There is some kind of delay 166
The movements maybe the command executed at this point at this point 167
your Synchronization started here 168
and Finally 169
At this point your sync to your Master axis with this cam profile 170
so It's case you lost some position here 171
Maybe it is crucial for application that's why maybe you should 172
Use to before from synchronizing position 173
At the leading axis position or 174
You have to synchronize before start of the movement of your Master axis 175
Maybe you should do the sync while your Master axis is 176
Standstill 177
It depends on your application of course 178
so with noncyclic cam processing and processed only once 179
with Leading access after your profile finished 180
The slave position 181
Is should be 182
same Constant velocity 183
and What happens 184
After your profile finished 185
You're running as absolute 186
From here you will see 187
The 188
Master axis master pos 189
at Horizontal 190
and Has vertical here the slave pos 191
You should think about what would happen 192
If your master pos is already 193
100mm as actual pos for instance 194
then you executed your cam and master pos is rising 195
Your range is here 196
And master actual position is out of range and the set point for slave 197
Position is this value 198
When you use cam off function and its Constant it is case 199
A similar on the negative side 200
If your master actual value is lower than 0mm 201
Then 202
Your set point for slave position according to this cam profile and should be 203
10mm for instance constant 204
If you are running as absolute 205
for relative synchronization 206
Your access zero is not so important 207
Start points 208
Used as your reference zero. 209
so That's why it's important to try with different parameters 210
There are so many possibilities to do 211
The synchronization 212
there are Different parameters for cover all of the applications 213
required by 214
Machine or customer needs 215
For another case 216
evaluation Master as absolute and slave as relative 217
You see here the relation between Green curve 218
as cam profile and red curve as slave position 219
It just looks like there's an offset 220
For slave position 221
Maybe 222
So slave position most by a precise difference between in Y coordinates 223
The beginning and the end 224
Syncronization parameters are the same before as before 225
and Only one difference is following axis as relative 226
so After the cam on command executed the actual position of 227
slave axis used as access point or axis home points 228
you think. 229
On the next case Master is relative 230
slave is absolute 231
And after you executed cam on comments 232
The master position actual position maybe 100 mm is used 233
zero point for the cam 234
Your slave point 235
Used 236
Or considered as absolute position 237
So at this list it looks like there is an offset 238
for the Horizontal axis 239
Start position of cam x coordinate is set equal to Leading access position at the 240
Time of starting Syncronization task 241
if the following setting is immediately 242
With the setting start of synchronization at leading access position plus offset 243
is set equal to leading axis position. 244
So it's also some influence in our 245
Synchronization settings because 246
With consider the master as relative so 247
here the relationship on the master axis 248
Master relative mode must be selected if after one Cam cycle has been completed 249
You want the system the Syncronization as with the nature of the basis of 250
Syncronization condition at end of the cam cycle 251
and the last case master is relative and slave is relative 252
You'll see with the blue 253
Interval or arrows 254
There are some offset in our both of axes in Y direction 255
And the X Direction 256
So with these settings 257
Interpreted for a cam 258
The start position of Cam in X Direction set equal to leading axis position at time 259
Starting of synchronization task 260
If the following axis selected Syncronization immediately 261
With the setting start of synchronization with offset 262
It set equal 263
Leading axis position entered 264
So difference 265
Behavior 266
The start position of Cam in Y coordinate is set to equal to following axis position at the time of 267
Starting the synchronization task 268
so next page 269
Three different type of processing 270
non cyclic processing here 271
You should think about all both of our axes as absolute 272
and our cam profile 273
Just for one cycle 274
Executed 275
cyclic absolute 276
you see here one cycle finished 277
but At the start and at the end of the cam profile you see here 278
For the setpoint position of slave Axis or different 279
so thats why there is a jump 280
And after that are cam processing still continuous 281
And if you select the cyclic relative 282
We will consider the following Axis or slave as relative 283
At this case master position is still Rising 284
And it's going to process 285
In the next cycle on and the next cycle and next cycle 286
but you see the difference here 287
Set points shifted 288
For our slave position 289
So at this case 290
cam to Continue is 291
still Possible 292
That's why before the we creat a cam 293
Or interpolation setting we select 294
Which way we are going to use the cam profile 295
so if you'r Going to use the same as cyclic absolute 296
At this case at the beginning and the at the end point of the cam profile 297
Automatic the interpolated 298
If the select create cam with cyclic attitudes or interpolate cam with cyclic absolute 299
Yes next page enable Camming in 300
MCC program synchronisation tab 301
And example 302
Reference selected as leading axis 303
From synchronization position 304
and lengths answers 100 mm leading axis position 200mm shortest path 305
About time related synchronisation here you see blue dashed curve 306
constant speed 307
The Greee curve is cam profile slave position is reddish 308
And all parameters for cam on command leading axis Syncronization 309
profile 310
length entered 311
Position is clearly defined 312
Dynamic parameters 313
are not active 314
If I choose to use time-related Syncronization profile I have answered dynamic parameters 315
But the Syncronization position is of course difficult to determine 316
it depend our settings 317
so Maybe the system will finish to synchronize at this point of cam profile 318
Or maybe it should be Syncronization at this point it depends on your setting 319
leading axis Synchronisation it's not allowed to reverse 320
Synchronization procedure 321
otherwise aborted It's an error message 322
next page start of synchronization 323
You should come once or come with executed Start points and points 324
immediately with offset setting 325
And leading access position plus offset 326
here or Master position at the Slave position 327
When you enter and offsets 328
and Signs your cam curve for slave set point is shifted on your 329
Y axis 330
I'm setting reference point for Syncronization that are three option before 331
Position symmetrically 332
from position 333
So this is your leading axes position 334
there are 3 Different red colored curves 335
at this picture 336
when you select Before synchronization position you are sure 337
At this point your slave axis is Syncronization to your Master axis 338
Of course you can shift also left or right 339
You're leading axes position maybe you should set it at the beginning of your cam profile 340
so if you select Synchronize symetrically 341
You can see it this red curve 342
At this point leading access position 343
It's in the middle of your symmetrical 344
and you Syncronization here 345
The last setting from Syncronization position your movement of 346
slave axes will be started at this reference Syncronization position 347
And after the length 348
Your slave axis 349
State is 350
Syncronized 351
It is possible to set an offset for cam starting points 352
So you see here the settings are leading axis relative 353
following axis is Absolute 354
Start of synchronization at leading axis position 355
Reference point from sync position 356
your slave axis at this case inn some value at the minus range 357
Leading axis position here 358
and the offset 359
for cam Starting point 360
at the left Direction here 361
and now when use cam relative 362
You see here 363
The green curve as cam profile 364
Is shifted by offset 365
On the leftsite 366
dynamics response settings for enable camming you have already checked 367
and the last tab for expert for enable camming comments 368
able to give command ID for 369
Maybe the return value of set master set point on Camming on 370
You can track with other comments 371
I'm for disabled camming that are similar for my test need to be entered 372
by User 373
Reference 374
Position 375
DeSyncronization position 376
length Direction and So on... 377
enabling command looks like this in structured 378
Text 379
Disabling comments it's looks like this 380
and for gearing also used set master set point Commons 381
Master value for the following axes 382
And the transition Behavior 383
will be the programmable Dynamic values should be a smooth transition 384
It's direct there might be some jumps 385
On your position or velocity 386
and another comment set scaling on camming 387
This function scale of the master of slave range 388
relative cam 389
parameter can be used to define the time when scaling is to be applied 390
this cam or Next cam weather selection function affect just active cam 391
or Subsequent commands 392
scaling Operation that act on the active command as well as scaling operation 393
But that also stored and act on the subsequent command can be read from 394
camming Adjustment system variable 395
Sometimes there is a requirement to set an offset and cam 396
during system is running 397
correct something 398
On your machine 399
Next page 400
Examples to understand whether the set on Syncronization is object 401
So when was set it 402
It's next cycle 403
And set scale comments 404
Is executed here 405
For the slave axis 406
You see your cycle processing cam 407
There's a scaling for slave axis 408
After the cam profile and and the next cycle 409
you see with the blue curve 410
Relationship between master and slave your comment is 411
Active 412
If you select immediately on active Command 413
execute set scaling right this point 414
And cam profile is activated and executed by scaling 415
Immediately 416
after any other enable Camming command executed 417
Because of You selected on active come with only and the next time scaling is 418
Ignored 419
And the last setting is 420
On active comments and the following comments with immediately means 421
when you Execute your set scale command once it is active on your running cam 422
This cycle and next cycle 423
and after you reenable or reused again the camming command 424
You're see it's always 425
active with following comments 426
You can see and monitor 427
The currentstate under camming adjustment 428
master scale 429
Slave scale 430
Set offset on camming 431
You just enter here your following axes 432
and range slave or master range 433
enter the offsets 434
You select the mode absolute or relative 435
At the command will be effective immediately or at the end of the next cycle 436
There are some examples about scaling and offset on Syncronization objects 437
It is possible to make your scale with 438
coefficients or factor 2.0 439
On the master leading axis your see your cam profile is 440
Adjusted and scaled 441
Another 442
Example you see the scale with Factor 2.0 on slave range 443
This is on the left side are origin of Cam profile 444
And at this case we are running with 445
Cyclic slave cam 446
As relative 447
There's a compensated motion here 448
For instance we executed are offset common for slave range with 20 mm 449
It's offset to up on the slave Range 450
If you use offset command for the master range 451
with 452
20 mm There's a compensating motion 453
On the leading site 454
There are some monitoring functions during Syncronization operation 455
Here at this picture will see sync TO leading access and following 456
axis 457
so there are some parameters like current master. 458
data value current slave data value 459
That you see here the relationship 460
Between two objects during system running 461
Sometimes at the following axis 462
Some error may occur like alarm 463
40201 Syncronization Operation tolerance exceeded on gear axis 464
That means 465
current slave data value 466
Is greater than 467
gearing pos tolereance command value tol. 468
It depends on your cam profile 469
Or other Chase 470
40202 Dynamic response of the Syncronization op setpoints 471
can not be achieved that means 472
current slave data value is 473
Greater than maximum velocity of the following axes 474
Yep 475
I'm the Syncronization Operation to controls 476
The phase 477
There's a system variable 478
gearingpostolerance 479
Enable error reporting 480
If it is selected properly than another alarm will be triggered on 481
leading axis 482
error triggered on slave during Syncronization operation 483
Add some case it is good to know during your machine running Syncronization several 484
Axis 485
Maybe there is a failure occurred in your following axis so 486
Syncronization 487
Operation to 488
Is possible to 489
Control leading axis and trigger an alarm 490
On the other hand if you close these Diagnostics or select the other way 491
You'll have to write your own program to control all of the axis during your 492
Synchronization or sync of operation 493
You can select Monitor and function 494
Syncronization operation of Axes 495
That are some parmenters here 496
Activate setpoint monitoring without jerk 497
Setpoint tolerance 498
Activate actually monitoring yes or no 499
Report error to master 500
Set points 501
actual points 502
all errors or no 503
If you're faced with this kind of errors 504
For example 505
error 40201 Syncronization operation monitoring 506
Dialog box can be used to enable setpoint monitoring 507
At the end of the synchronization procedure calculate by the Syncronization operation to 508
sync state said yes and configured operation and function enabled 509
axes reports in dynamic responsible 510
setpoint operation can not here set 511
The response to this are also depends on the configuration of course 512
And the next error 40110 513
In addition you can make a setting to specify whether or not an error should be reported to the leading axis to 514
Here 515
This message is disabled no notifications is sent to leading master 516
and leading axis carry on moving 517
It's quite a place I want to go following access has been stopped 518
So if the report error axis 519
Function is enabled 520
Syncronization Operation error report to the leading axis triggers an alarm 521
error on slave 522
The response to this also depends on your configuration 523
and after that leading axis maybe stopped 524
So next page 525
Syncronization with velocity reduction 526
Here you see the trace of the Scout system 527
The orange curve here and the 528
Y axis is actual Master position 529
You will see here the Syncronization state is synchronized here 530
There is brown axis the set point position of the slave 531
You see here the slave velocity 532
And another thing another curve with purple color 533
Setpoint difference between master and slave 534
Position 535
Okay 536
And the light blue is the set point 537
speed for slave 538
there is a vel limitation at this case with 20 millimeter per second 539
so normally During Syncronization your slave velocity profile and actual slave should be like this 540
But at this case there's limitation at your slave still couldn't reach 541
Maybe the 15mm/s so it's limited right here 542
It's going like this 543
So that's why you see there's a lack 544
Or there are some delay 545
due to following error as curve 546
you see Set point difference 547
gearing set to absolute ratio is 1:1 Syncronization immediately 548
next page 549
So you can read about the detail 550
The reduction in the velocity of the following axis leads to 551
Error Dynamic response cannot be achieved 552
no response configured for this alarm as default 553
That's why system will continue to catch up 554
The Master axis 555
tihs reduction Result in a discrepancy between slave profile 556
calculated by Syncronization op and actual set position of following axis 557
You can monitor the difference commadn value with system variable 558
At the end of the Syncronization procedure calculated by synchronous operation 559
after Syncronization State is set to yes 560
master and slave axis are not Syncronization at the point 561
time 562
Syncronization operation monitoring functions as enabled 563
You'll see it right here 564
Status 565
Syncronization is set to yes 566
but Actually 567
It's not the Syncronization do to velocity limits 568
You have to keep it in your mind 569
due to that set point actually monitoring is disabled for Syncronization operation 570
There's no response at this time restrictions 571
That's the only Syncronization later 572
Actually at this point 573
or right here okay 574
next page with another case setpoint 575
Monitoring during Syncronization 576
And this is also related with gearing and of course for camming 577
as green curve you'll see the here the actual Master position 578
and blue curve actual slave position as a light 579
Blue 580
Set point speeds of the axes 581
And is it 582
brown color slave velocity 583
And the purple is the same 584
Set point difference between slave 585
Synchronization slave position 586
From our equation or cam profile or whatever 587
So let's see what's going on gearing is absolute 588
ratio 1:1 589
command Executives right here as immediately should be 590
30mm so... 591
Maximum slave velocity 592
Sets here 593
With different values 594
So... 595
normally vel of slave axis it should be like this 596
at this case is limited to here 597
and after your sync state set to true 598
Normally 599
Without any speed reduction or limitation 600
slave axis and master should be Syncronization right here 601
So unfortunately it couldn't happened 602
And system stop procedure 603
Then trigger and alarm right here 604
so Let's see 605
In this case Syncronization operation monitoring functions activated 606
setpoint monitoring without jerk. 607
and option report error to leading axis. 608
For the procedure 609
Syncronization TO uses position of leading axis to calculate 610
Corresponding position or velocity profile for following axis 611
As in the previous example velocity reduce 612
By following axis and trigger an alarm in slave axis TO 613
At the end of Syncronization procedure calculated by Syncronization TO 614
when sync state set to yes 615
after that monitoring 616
Enabled 617
following axis detects duration between position 618
Calculate the sync TO 619
IPO exceeds specific performance as a result 620
following Access to to triggers an error 621
Syncronization operation tolerence exceed on gearing axes 622
Because motion emergency about has been set as default 623
following axis motion is stoped and synchronous operation is aborted 624
To outputs info simple message, that aborted 625
Because of report error on leading access is disabled 626
This stop doesn't affect leading axis 627
If you said it all errors also the master access will be stopped 628
or Depends on your choice 629
It's maybe carry on traveling at defined velocity 630
So several cases on the next one reporting 631
Syncronization operation error to leading access 632
by The way you see here Motion emergency abort as default 633
It should be located in your axis 634
As default values 635
or In any case of error 636
maybe check later on 637
and next case similar curves with same colors 638
Master position in green curve 639
And the slave position as dark blue 640
And light blue limited following access velocity 641
As a purple curve the set point difference between synchronously position and slave position 642
At this case 643
due to velocity limitation on following axis 644
After sync. States set to True 645
Both of axis has stopped 646
That's the difference 647
and so after that exercises 648
Let's try on some practice with Scout example program 649
So let's start 650
simosim 651
and go online 652
And download our program 653
Maybe we should try with different cam profile 654
Yes 655
Let's see our cam1 656
Looks like this 657
cam 2 is empty 658
Are going to enter some value 659
Like this 660
cyclic Relative maybe 661
So with new firmware version it is possible to download the to modification during runtime 662
After that 663
You should select permit restart on technology objects 664
to be Effective 665
Because that are some parameters has changed during the modification of the cam profile 666
Such as restart 667
Okay 668
Let's start a trace 669
On the 1st 670
Set control enable 671
Enable 672
For the Red axis 673
During both of us I want to use the cam on 674
Okay 675
here you see a little Movement 676
actual position of slave set 25 677
Why? 678
Because 679
Master axis position is 0 680
And corresponding value 681
He's right here is 25 682
According to our synchronization setting in our program 683
with immediate time profile 684
You can measure the ramp-up and the speed we have answered here on the velocity 685
of slave axis 686
50 mm/s 687
Now our axis is synchronized right here 688
and cam on command executed standstill accelerate constant move decelerate 689
Standstill 690
Are function states on following objects 691
Change from inactive to camming 692
After you see it this point our access synchronized 693
So... 694
Right now I want to start my Master axis blue with 695
jog Positive function 696
So there's some alarm Syncronization operation tolerence has exceeded 697
gearing axis 698
and 699
For the axis blue error Triggers on the slave 700
both of my axes 701
Stop this case 702
You see here there's a movement 703
Actual speed of my Axis Blue 704
and Actual velocity it is in the negative Direction 705
why ? According to my parameters 706
Under the settings 707
On the leftsite 708
master axis and red axis 709
Default 710
Not default 711
Configuration 712
Let's say monitoring 713
Syncronization operation you see here 714
all errors 715
without jerk and set point difference so 716
That's what triggers an alarm let's change and see what will happen 717
red axis 718
Normally i should do that in offline mode 719
So let's switch 720
Reports of master axis no 721
And let's say no 722
I thought I would try again with this parameter 723
And set the thoughts 724
download again. set to start 725
restart trace. Enable 726
Enable 727
Let's say 728
At this case the variable jog positive that's why it's 729
Let's stop 730
let's set true to cam on bit 731
slave axis 732
May the movements and now lets start Again the jog positive 733
Right now there's no alarm 734
And our slave axis 735
Processed 736
The cam profile for one cycle 737
You may see here 738
And still running 739
velocity of Master axis is too low 740
It should reach 741
Plus 350 mm 742
Okay at this point or 743
cam profile processing is finished and you see 744
Syncronization status set to false 745
camming and inactive 746
Status of access motion Standstill 747
Accelerating decelerating 748
You see here the actual velocity of axis 749
Is really 750
it's 2 mm/s nearly -2 mm/s 751
Or actual position 752
If I Syncronization here it was 25 753
After I restart my 754
Blue Master axis 755
It goes to zero 756
and 78 757
19 + so on... 758
At this point it's zero again 759
Okay 760
According to axis setting 761
in axis red control 762
following Access is red master blue 763
cam direction 764
Positive 765
Relative for both axes no cycling processing 766
Start points for relative caming 767
According to the settings 768
And let's try again with a different sample 769
with cam2 maybe 770
Direction should be positive 771
cyclic processing 772
That's means cyclic relative so Syncronization is the same 773
immediately by time profile 774
The direction should be the shortest path 775
At this case I didn't used 776
cam off command 777
Because my profile is already ended 778
and Executed so 779
Normally we use cam on comments 780
when its required to stop the slave axis in the middle of processing cycle 781
Let's start with different curve enable both of axis 782
And I will start the trace 783
Let's say for the red axis cam on 784
Okay 785
There's a little movement now Exposition is - 0 786
why? 787
Because 788
Normally 789
Let's say 790
Actual position of Master aksis is 791
0 right here 792
Let's say 793
To start the Master axis 794
to cam on 795
already executed okay 796
I have to jog positive for the master 797
Now both of axes are running 798
It will take some time 799
And if you continue with the next time cycle 800
cyclically actual position is reached to 801
1500 802
In cam profile 803
The value is minus 804
1000 + 12000 805
So all synchronization still running 806
We are almost at the middle of the cam profile 807
Yes 808
and now after that 809
here slave axis is going back 810
And processing 811
cam profile this is the first cycle 812
Maybe I should change or Master Axis velocity to a little bit 813
with 20 perhaps 814
our cam profile still processing 815
It is both of axes are a little bit 816
Faster 817
So we are coming end of the first cycle of cam profile 818
Yes 819
And after that as you can see the next cycle of cam processing started 820
and you see the 821
same Profile of our cam 822
Here are change the activity of the master that's why 823
System automatically adopted 824
Set points to the slave 825
So it should be going on and on again 826
until i executive of cam off comments or any kind of other comments 827
In my case according to cam off setting 828
I said time profile I supposed to at the end of the same cycle 829
You can set it may be the leading access here 830
Stop after this Syncronization position 831
Or stop before the synchronization position 832
You should see some length 833
Some length of the current cam profile perhaps maybe 100mm 834
lets try system int running mode 835
So with the settings maybe I want to be sure 836
the Endpoint 837
Or the deSyncronization length of the cam 838
Usually it's a need in the real machines 839
Okay it's downloaded 840
Let's change the speed a little bit 841
That's your position is rising of the master and slave 842
Actual velocity of the slave is really low due to cam profile 843
Is divided by 10 844
perhaps 845
So let's try to cam off 846
for axis red 847
control cam off 848
then 849
now i Executed my comments and 850
at end of the cam cycle I'm expecting my slave axis 851
deSynchronized 852
400 millimeters 853
And as you can see right here 854
slave axis Stopped 855
At the -5mm 856
And synchronization status 857
You may go and zoom 858
you can measure 859
At this point and at this point 860
and 861
Let's say the actual position of the Master axis 862
You'll see here or deSyncronization length 863
It was camming 864
right here and camming is inactive 865
At this point 866
Axes were synchronized yes 867
and after 868
DeSyncronization started his immediately is set to no 869
So with the system variables you are able to determine or understand the first 870
current Situation of the axis 871
And this is basically how it works 872
You can try with the different setting and see how the system works according to your 873
Requirements 874
Let's try 875
With the 876
time Profile 877
immediately 878
okay for the cam on with 879
Same perimeter 880
time immediately 881
Now our Master blue axis is running at the positive let's try the cam on command 882
And see what will happen to our slave axis position 883
and see the trace 884
For diagnose 885
Are blue axis is running 886
Let's cam on axis 887
And our slave is trying to catch up 888
now Syncronization at this point 889
By given Dynamic borders that's why it's 890
Not predictable which position 891
Axis is Syncronized so 892
Is going up 893
It all takes 894
Take the two seconds 895
Nearly 896
So let's try the cam off 897
And after I set the logic one with cam off bit and executed command 898
So you see in the middle of cam processing command executed 899
And the speed is 900
Also really low 901
velocity of slave axis was 902
4 mm/s 903
It's right here it's executed according to Dynamic values 904
constant zero 905
System is deSyncronized 906
It's right here 907
Is inactive and status is motion as standstill 908
There's a little bit difference access tested and cam inactive so maybe that is 909
IPO cycle or servo cycle 910
3 or 911
4 milliseconds 912
It's 6 miliseconds nearly 913
The twice time of servo cycle 914
Should be 915
Okay 916
So what we learn about simotion camming at this chapter 917
how do we Use cams? 918
how do we make assignments and interconnection to 919
Make configuration 920
But also several options to 921
Satisfying customer needs 922
I think 923
With your own you should try with different parameters of a cam on and cam off 924
Functions 925
According to our notes 926
As you can see 927
and Already learned 928
A little bit about that are also other comments s scaling on cam 929
And set offset switch Master set point 930
parameterize cam 931
Maybe you should try yourself to check 932
online with simulation of CPU 933
and learn into more detail 934
In the future you might need 935
Some kind of information 936
It's always good to know 937
Thank you for watching. 938
See you next chapter