1

00:00:02,560  -->  00:00:04,608
Chapter 23

2

00:00:04,864  -->  00:00:08,960
about project version and upgrade and downgrades

3

00:00:09,728  -->  00:00:15,872
We had already this some examples in earlier chapters so

4

00:00:16,128  -->  00:00:18,944
i will make its really quick at this time

5

00:00:21,248  -->  00:00:25,344
What we learn during this course?

6

00:00:26,368  -->  00:00:29,440
Let's say it's possible to

7

00:00:30,208  -->  00:00:34,304
save as project as a project olf format

8

00:00:36,096  -->  00:00:36,864
So

9

00:00:37,120  -->  00:00:42,240
That means if we are using old Hardware it's possible to open with

10

00:00:42,496  -->  00:00:45,056
Older version of simotions

11

00:00:47,360  -->  00:00:52,480
On the other hand if we are using their own CPUs

12

00:00:52,736  -->  00:00:54,016
Sometimes

13

00:00:55,040  -->  00:00:57,088
Old project format save

14

00:00:58,112  -->  00:00:59,392
Is that possible

15

00:00:59,648  -->  00:01:04,512
And that's why I here there's a check the project downward compatibility

16

00:01:05,792  -->  00:01:08,096
For project format

17

00:01:08,864  -->  00:01:11,168
4.5 lets say

18

00:01:12,704  -->  00:01:14,240
We are here

19

00:01:14,496  -->  00:01:17,824
Two different CPUs with 4.5

20

00:01:18,336  -->  00:01:20,640
And 5.2 for example

21

00:01:22,176  -->  00:01:27,552
It's scout checking for download compatibility

22

00:01:29,088  -->  00:01:35,232
At first that we should do that before we save as our function so it says

23

00:01:35,488  -->  00:01:37,792
consistency check Successful

24

00:01:38,048  -->  00:01:40,608
All the libraries everything's checked

25

00:01:43,936  -->  00:01:45,472
This is the one thing

26

00:01:46,496  -->  00:01:52,384
So another thing we learnd all right click open at Hardware

27

00:01:53,408  -->  00:01:59,552
Let's say it's possible to convert device or replace

28

00:01:59,808  -->  00:02:00,832
Object

29

00:02:01,600  -->  00:02:06,208
With different kind of CPUs and versions is possible

30

00:02:06,976  -->  00:02:13,120
Yep after all sinamics Library

31

00:02:13,376  -->  00:02:15,680
We have already talked about

32

00:02:16,704  -->  00:02:18,752
right click properties

33

00:02:19,008  -->  00:02:25,152
You seetechnology packages device-specific version and Compilation

34

00:02:25,408  -->  00:02:27,712
versioning

35

00:02:34,112  -->  00:02:40,256
by the way made an example and migrated classic Scout project to

36

00:02:40,512  -->  00:02:42,048
TIA Scout

37

00:02:44,096  -->  00:02:48,192
tia portal version 15.1

38

00:02:50,496  -->  00:02:54,848
And there are several things you should consider

39

00:02:55,360  -->  00:03:00,480
Before you start to migrate your project to TIA

40

00:03:00,736  -->  00:03:04,576
There are also several restrictions

41

00:03:05,344  -->  00:03:07,904
Your project must be consistant

42

00:03:09,440  -->  00:03:14,048
Do you have to compile all of your CPU in project

43

00:03:14,304  -->  00:03:20,448
In your Hardware configuration the devices models everything must be recognizable by TIA

44

00:03:21,984  -->  00:03:23,008
And so on

45

00:03:29,664  -->  00:03:32,224
We are using same Hardware

46

00:03:33,248  -->  00:03:35,552
Right now the same CPU

47

00:03:36,576  -->  00:03:37,856
In the real world

48

00:03:38,880  -->  00:03:45,024
What is possible to program with simotion scout classic or similar to Scout TIA

49

00:03:48,864  -->  00:03:50,656
In that case

50

00:03:50,912  -->  00:03:56,544
CF card files and templates are almost the same so

51

00:03:58,848  -->  00:04:01,664
At some point it's usable

52

00:04:02,176  -->  00:04:03,712
It's possible

53

00:04:03,968  -->  00:04:07,296
If you create your project to TIA portal

54

00:04:08,320  -->  00:04:11,136
You can just

55

00:04:11,648  -->  00:04:17,791
Export and import your technology objects and programs and libraries

56

00:04:18,047  -->  00:04:20,607
And you can easily

57

00:04:21,631  -->  00:04:23,935
Sometimes not so Easyly

58

00:04:24,447  -->  00:04:28,287
But you can go back to scout classical work again

59

00:04:30,079  -->  00:04:31,871
So it takes time

60

00:04:32,383  -->  00:04:33,919
But it's possible

61

00:04:42,623  -->  00:04:45,439
there are some differences

62

00:04:45,695  -->  00:04:51,839
TIA portal is still developing so some features of classical scout

63

00:04:52,095  -->  00:04:53,887
It's not working right now

64

00:04:54,911  -->  00:04:55,935
For example

65

00:04:56,191  -->  00:04:58,239
Scripting functionality

66

00:04:58,751  -->  00:05:01,567
There are some bugs in TIA

67

00:05:03,103  -->  00:05:04,895
When you are using

68

00:05:05,151  -->  00:05:11,295
other PLC like step 7 1500 in TIA

69

00:05:11,551  -->  00:05:13,599
changed Something your device Network

70

00:05:14,623  -->  00:05:20,255
scout TIA says something in your hardware is changed

71

00:05:20,511  -->  00:05:22,303
so thats why

72

00:05:22,559  -->  00:05:27,167
when you want to download your project again with TIA

73

00:05:27,423  -->  00:05:32,799
CPU has go to stop mode and Power on reset

74

00:05:33,055  -->  00:05:35,871
software reset must be executed

75

00:05:37,663  -->  00:05:43,295
but you didn't change anything in your simotions Hardware

76

00:05:44,319  -->  00:05:45,599
The reasons is

77

00:05:45,855  -->  00:05:47,135
TIA portal

78

00:05:47,391  -->  00:05:50,463
It's using the same device Network

79

00:05:50,719  -->  00:05:56,863
Hardware and communication setting so if you change something only the date

80

00:05:57,119  -->  00:05:58,911
of Compilation

81

00:05:59,679  -->  00:06:04,287
Or the last modification date will be used in Scout side

82

00:06:05,055  -->  00:06:08,127
That's why that is a BUG

83

00:06:08,383  -->  00:06:10,175
it takes time

84

00:06:11,455  -->  00:06:16,319
It's is not good for your engineering time

85

00:06:16,575  -->  00:06:19,647
You have to waste more time to

86

00:06:19,903  -->  00:06:22,975
Create and modify your programs are so

87

00:06:24,511  -->  00:06:27,071
This is one of the most

88

00:06:28,095  -->  00:06:34,239
Reason that we still use classical Scout to develop our projects

89

00:06:35,775  -->  00:06:40,639
Also you'll see here in your project manager are some items are missing

90

00:06:40,895  -->  00:06:42,943
Because the list is shorter

91

00:06:44,479  -->  00:06:47,551
Yo script folders

92

00:06:47,807  -->  00:06:51,135
It's possible to run some Scripts

93

00:06:51,647  -->  00:06:56,255
But integration is still that are something's missing

94

00:06:57,535  -->  00:06:58,815
And so...

95

00:06:59,583  -->  00:07:05,727
But it's possible after you download your CPU or example with additional data

96

00:07:05,983  -->  00:07:08,287
Store on CF card

97

00:07:08,799  -->  00:07:12,383
after that if you can go and uploads

98

00:07:12,639  -->  00:07:16,223
From real Hardware or situation whatever

99

00:07:16,479  -->  00:07:19,295
You're perfect so that way you can

100

00:07:19,551  -->  00:07:22,367
Go back to your Classical world

101

00:07:23,903  -->  00:07:25,183
keep it Your mind

102

00:07:31,071  -->  00:07:35,167
so About project version for simotion side

103

00:07:37,471  -->  00:07:38,751
These are

104

00:07:40,031  -->  00:07:43,871
Something I can say out of my mind

105

00:07:44,895  -->  00:07:51,039
there are similar topics you will see in chapter tips and tricks

106

00:07:53,599  -->  00:07:55,647
That's enough for right now

107

00:07:59,231  -->  00:08:01,023
Let's see then

108

00:08:01,791  -->  00:08:03,071
Later on